Develop Bugs

[Q] Trying to flash back to Stock rom with ODIN. Need some help.

Heya people.
I have a weird issue.
First some history.
I bought this phone years ago as a backup and soon after I decided I did not like it and got another phone. Meanwhile I fiddled with custom roms. This was back in 2012 probably so im pretty sure the rom that is on the phone now is Cyanogenmod unofficial android 4.0.
Phone boots fine but is quite unstable. random reboots etc when using it to its fullest.
I litterally threw it in a box, and forgot about it. until my mom called me needing an emergency phone. I remember I had it and offered it. Saying it could be there in about a day or 2. She needs a phone for a couple off weeks till her current phone gets replaced by Huawei since it broke. She specificly needed a simlock free phone. Mine is unlocked so that would have been great.
So I read up about Odin and how you are supposed to reflash to stock firmware. Downloaded the stock firmware from Samfirmwares. Dutch firmware. I downloaded 2 versions since there is a vanilla one and a vodafone branded one.(my phone is the vodafone branded one so I tried that one first)
First I used the newest Odin version and it didnt work. Got stuck on setup connection for about 5 minutes and then timesout with a fail.....
Ok so I went back to browsing and found that using a older version of Odin might work. Been there done that. tried 4-5 different lower numbered Odin versions. All the same issues. Switched USB ports multiple times and also doesnt work.
I am currently at a loss.
PS I also tried the Samsung Kies method.. Initialize firmware and upgrade. type model number(succes) type serial number(succes) then it tells me my device is unsupported for this method.

Process crash and random reboots!

Hello everyone I'm Italian and I have problems with my stock galaxy tab 3 7.0 T211.
Often when I turn on the tablet the process systemui crash, then while using, many other app randomly lock, and I must open them 2-3 times to be used in normal way.
It happens also that the tablet will block for a couple of seconds and restart it automatically, but restart is not normal but is much faster.
I tried to do a factory reset from recovery, I installed with odin before the stock firmware 4.1.2 (XXAMK6) and then the 4.4.2 (XXBNI1), but in all cases nothing, the tablet gave me the same problems, particularly the problem of the process are terminated .
It also happened that during the first configuration (language, time, wifi network password, etc.) the configuration process crash, and I had to start all over again. All this even though I had just installed the firmware with odin.
I do not know what to do, it seems to me absurd that despite I start from a clean base and I use odin to flash a stock rom the tablet gives these problems, I do not understand what could depend.
I hope you can help me, any help or advice is welcome.
Many thanks to all!

Been there, done that
midnighteight said:
Hello everyone I'm Italian and I have problems with my stock galaxy tab 3 7.0 T211.
Often when I turn on the tablet the process systemui crash, then while using, many other app randomly lock, and I must open them 2-3 times to be used in normal way.
It happens also that the tablet will block for a couple of seconds and restart it automatically, but restart is not normal but is much faster.
I tried to do a factory reset from recovery, I installed with odin before the stock firmware 4.1.2 (XXAMK6) and then the 4.4.2 (XXBNI1), but in all cases nothing, the tablet gave me the same problems, particularly the problem of the process are terminated .
It also happened that during the first configuration (language, time, wifi network password, etc.) the configuration process crash, and I had to start all over again. All this even though I had just installed the firmware with odin.
I do not know what to do, it seems to me absurd that despite I start from a clean base and I use odin to flash a stock rom the tablet gives these problems, I do not understand what could depend.
I hope you can help me, any help or advice is welcome.
Many thanks to all!
Click to expand...
Click to collapse
This happened with me too but only after updating to KitKat 4.4.2 with Odin, I tried a couple of times and even used firmwares for other regions (mine is international version unlocked so it should work with no problems), I then Initialized the device using Kies 3 to the latest firmware available for my region for the SM-T211, it went OK, I still get crashes, I mean the problem hasn't totally been solved, but it's much much less crashes now than before when device was flashed with Odin (may I say that it was the same stock rom with the same build number from both Odin and Kies 3, still the one from Kies 3 was much more stable)

OEM Refurbished TMO S4 Boot Loop / Boot Lockup / Intermittent Sound / Sound Crashes

I troll here a lot for information, as I fix devices for friends for free, so if I'm posting up for help here it means I've run out of internet solutions and energy. Mods, I've spent a week searching and reading through threads, no single thread solved my issue which is why I'm posting up; please move the post if it better fits elsewhere.
The Phone: T-Mobile Samsung Galaxy S4 SGH-M919
Current Firmware: M919UVUFNK2 Stock T-Mobile (M919UVUFNK2_M919TMBFNK2_M919UVUFNK2_HOME.tar.md5)
Current Bootloader: M919UVUFNK2 (also verified with getprop ro.bootloader)
Current Baseband: M919UVUFNK2
PDA: M919UVUFNK2
Hardware Revision: REV0.7
Current Android Version: 4.4.4
Current Kernel: 3.4.0-2437203 [email protected] #1 Mon Nov 17 19:20:38 KST 2014
Current Build: KTU84P.M919UVUFNK2
Device/Product: jfltetmo
CSC Code: TMB
Firmware CSC: (blank)
Active CSC: TMB
Product Code: SGH-M919XXXTMB
GPS Works: Yes, verified
BT Works: Yes, verified
WiFi Works: Yes, verified (all bands, secure and unsecure)
Sound Works: Randomly, causes issues. When it does work it is crystal clear
Network Radio Works: Yes, verified
Battery: 2 new batteries, one OEM and one Rav
IMEI/ESN: Free and clear, verified to be a TMO device by TMO
Error Messages Seen (if any): "Process system isn't responding"
Odin Versions Used: All 3.x up through 3.10.6
Alternate ROM Tries: Candy5 v2.1.0 jfltetmo
Alternate Recovery: TWRP 2.8.4
Odin "Double-Flash w/o Auto-Reboot" Used: Yes, multiple times (even triple and quadruple times)
FSCK Used: Yes, no issues detected
The Story:
I was presented with a challenge, fix a phone which just came back from the manufacturer. Sadly, not the first time I've had to clean their mess up. It was sent in under warranty because of screen bubbles, and returned with an OEM LCD, and a new battery. And, before anyone asks, the manufacturer refuses to take a look at it again. It's now out of warranty (by a month or so) and they said it worked fine when it left their hands. Yes it did, but only for a few weeks. From the time they shipped it back out until it crashed, nothing had changed on the user's end, no software additions or anything.
Appeared to only need re-flashing. After it booted and reached the unlock screen it seemed fine. If you unlocked the phone, it would immediately freeze up. When it did this it would usually be frozen for about a minute or two and then reset itself. Most of the time it would return to the lock screen, sometimes it would hang on the T-Mobile flash screen. One time I was able to get in but once it started syncing messages it locked up again. It had the latest firmware (M919UVUFNK2).
I used OEM recovery to wipe the cache and return it to factory fresh. It quickly booted up to the lock screen and everything seemed fine, I swiped and moved around the menus like normal. Sound was random though, sometimes it would work, sometimes not. Wifi, Bluetooth, Data .. everything worked like it should. I began to notice, however, that anytime something tried to use sound (ringer, notification, changing the volume) the system would lock up and stutter somewhat. Eventually it got to the point where it would just hard-lock every time sound was used. So I wiped it fresh and clean again--I wiped it several times in a row infact, just to be sure.
Again, everything seemed fine but sound would be random, and sound always seems to trigger issues. A few times I immediately muted all audio as soon as I factory-reset and rebooted the phone, in order to see if that mattered. One of those times it locked up within 2 minutes of use, and the other times it locked up eventually. It seems to last longer when audio is muted, but I wouldn't correlate that directly because it's not easy to scientifically prove.
In order to see what might be going on I went to install CatLog from the sdcard, but that needs root to work properly. I tried using SuperSU and CF-Auto-Root (jfltetmo/sghm919) to no avail. What happens when either of these methods are used: They run flawlessly and say everything is good, but upon rebooting the phone locks up at the Tmo flash screen. No matter what I do, rooting causes it to lock, and when it's locked the phone gets ultra hot as if the CPU is stuck in a loop.
After re-flashing the stock rom umpteen times and getting the same issues, I tried finding a PIT file to no avail. Gave up on that. For giggles I tried previous TMO stock roms. I realize that you normally can't do this, and some advise against it, but when you're up a creek it sometimes doesn't hurt to try, and I've had this work on other phones in the past. I tried ll of them actually, in chronological order of release so as to simulate upgrading:
These wouldn't flash to the phone at all:
M919UVUEMK2
M919UVUAMDL
These flashed/took and actually worked without an issue, they just all eventually locked up like NK2:
M919UVUFNH7
M919UVUFNB4
M919UVUAMDB
I re-flashed NK2 another 20 times or so, still producing the same problem. Decided to try 5.x out in case that might solve something. So far I've only tried 1 rom for it, Candy5. Several times I was able to get it to boot and use it just fine. One time it actually lasted almost 2 days. Since I'm talking about Candy, the folks did a fine job with it, I really like the layout/aesthetics. Free plug there.
Sadly, it crashes under Candy as well. Same problem as with NK2. Boot crashes, boot loops, sound issues. I've since sucessfully reverted to NK2. Presently it's sitting on my desk receiving emails, downloading apps and working just fine. I have all audio disabled. It's been going for about an hour. (edit, right as I posted this it crashed and rebooted itself)
My Theory:
Theory 1: The reason I want to re-PIT is because I theorize something in the filesystem, somewhere, has taken an epic dump. The more the phone is used the quicker it crashes--this happens almost every single time, and battery/CPU temps are normal. After a certain amount of use/time, the phone craps itself. Storage use isn't always sequential, so something is mapped as good when it isn't, and when it's put to use it dies. One way I correlate this with sound is that perhaps the system doesn't cache the soundbyte, so when it goes to read the file it craps.
Theory 2: Same as above, but instead of storage, the problem is bad RAM causing the same data corruption/issue. No easy way to solve this. I will be stress-testing the RAM chips tonight. Update: I stress-tested the CPU and RAM using some available apps, and ran it for quite a long time. Didn't seem to cause or exacerbate the issue any.
Closing:
Anyone have any ideas? I thought maybe re-PITing the thing may help, but couldn't find any files on it. The only other TMO S4 I have access to is a friend's who doesn't want it rooted (a requirement to read a PIT file I've been told). I appreciate any advice/input on this matter. Would be nice to get this thing going.

Did you pay for the repairs using a credit card? If so call the card company and contest the charge since it wasn't fixed properly.

It's not my device, and as stated in the post, it was repaired under warranty at no cost to the consumer.

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.

Phone reboots all the time - N975F

Hi there,
Last week, I get the OTA from my OWO CSC, it get updated to ZTO and the PDA version is CTCA. Not sure if this is newer or have a big difference from CTC9.
Does anybody here from OWO CSC and with this update experience some issues?.
I have already tried everything, also have received some help in this forum and it helps for few hours and then the problem appears again.
Regarding few points I have tried:
-I have already flashed again CTCA ZTO CSC using odin.
-I have already flashed the previous one, CTC9 ARO CSC using odin.
-I have done a factory reset with the CTCA ZTO CSC using the recovery menu.
Once i finished to reset the phone, i downloaded all appss and configured the phone from 0. Just restored some settings that i have backed up using samsung cloud. The phone works super perfectly for 48 hours and this morning it started again with the constant reboot.
Regarding few points i do have a question first, do you know or does it exist any software that can detect what reboots the phone or any log that track the error that can cause the phone to reboot?
I came from ZTO BTB9 that was from march security patch and till now it never happen to me before with this phone and Odin updates. I did not do and touch anything during update period, did it till the end. IT was just plugged into the charger. The phone finished the process completely normal, after it ends, i start it using and checking the new features. I configured the camera, the keyboard and not much. Not installed any software, just update all apps to the latest from store (samsung and google). The reboot is just random, the first one i detect while running app booster from samsung, but then it reboots without running that app (just reboot again). It looks like a softt reboot or a quick reboot because it get quickly back again but i should put the pin and it loads all again (notification from 0). It does not show the screen that say "samsung galaxy note 10+ powered by androird", just the "Samsung" logo screen and then lock screen. I did not reboot it as soon as it ends updating. The cache wipe did it just this morning after i detect it reboot over the night. It reboots like 6 time already. Since the previous one to last one have passed 3 hours but the very first reboots occurs between 20 or 10 minuts from each other. Now the reboot happen every 1 minute.
It looks like there is a problem somewhere and it sounds like a software problem. But i'm trying to know if it is a build problem or personal problem.
Now i have the phone running in SAFE MODE and it is fine, so for sure is something in system that try to synch, update or w hatever in background that crash the phone. I have the same apps as always installed, no new apps added so far
Thanks for the time.
Regards.
Yamil.