Develop Bugs

[Q] flashed stock 4.3 (rooted) with ODIN, can only connect to EDGE data.

Hi everyone, this is somewhat complicated and il try my best to describe what happened.
My device is a i747m (rogers).
I was running CM10.1 (running gapps-jb-20130812 and CWM recovery 6.0.4.3) for a long time, tried to update to 10.2.
(i messed up on 2 things.I don't think i cleared neither of the cache or data and also didn't have proper gapps which would be 20130813).
After installing 10.2 through recovery, it would just stay in the boot Cynogen booting logo.
i restarted into recovery, since my old CM10.1 zip was still there, i installed that instead, but same thing happened, it would just stay at booting logo.
I had made a nandroid back up from before all of this, and so i wiped data, dalvik cache, cache, formatted system, and i recovered into that, which was a stock 4.1.2 rooted (rogers).
However, nothing worked, only WiFi. I couldn't make any phone calls, send/receive messages, or get data.
I then used ODIN 3.07 to flash the new stock 4.3 rooted (rogers). WiFi worked as before, but i still couldn't make any phone calls, send/receive messages, or get data.
i then re-installed the latest recover 6.0.4.5, and installed paranoid android 4.4.2 and gapps for this version. But still nothing, so i went back to the stock 4.3 rooted.
4 months ago, when i made the nandroid back up, i also made an IMEI back up as well (i did not do a full imei/NV/EFS/IMSI/data backup) , i only had my IMEI backup, so i wrote using "NV items reader writer" the IMEI back onto my phone, and now i can recieve/send messages, and get phone calls and make phone calls. wifi also works.
But my data is stuck in Edge, its extremely slow, takes 10min to download a 15mb file.
so far:
-The APN settings are correct
-my IMEI number in settings menu, matches the one on the back of my phone.
-network mode is GSM/HSPA/LTE
-i have installed the latest modem for i747m through CWM recovery and also tried slightly older versions.
i am pretty much lost and i dont know what i should do.
-rogers has told me to use kies and perform backup and then recovery, apparently that will factory reset my phone.
-should i simply use kies to install the latest 4.3?
-does anyone have the imei/NV/EFS/IMSI/data files? or the full NV file?
-should i install CWM recovery and wipe everything that i can? and re-install stock rooted 4.3?
-should i use QPST to fix my IMEI? <-- dont know anything about this, noticed a few threads.
i have used these threads in all my rooting and so forth.
http://forum.xda-developers.com/showthread.php?t=2179330
http://forum.xda-developers.com/showthread.php?t=1831898
http://forum.xda-developers.com/showthread.php?t=2129993
please someone help me out, I dont know how to fix this.
thank you for reading this long and complicated problem.

same problem, ive spent every minute working on it for a week

Stock rom problem ... is there a fix?

Hi guys. I am stuck at an impasse here and I know someone here will be able to help.
My wife and I just bought two Samsung Galaxy 2 Epics (refurbished) from the retailer Glyde. I purchased from them because they are partnered with my new carrier, Ting.
My phone activated and ported my number with no issues. Everything works perfectly.
Her phone appeared to activate and then rebooted. It will not go past the Sprint 4G animated opening. I have rebooted, wiped cache, and done factory reset. Still ... 4G logo animation appears and the screen either goes black (appears to shut down) or it just stays on the 4G logo without moving on and then a few minutes later goes black. The phone worked fine before we tried to activate it. It logged in her gmail and connected to wifi.
I am able to get to recovery mode. I was probably going to root and cyanogenmod mine. In your opinion, would this type of action possibly correct the problem with her phone? Is it possible to root and flash the original stock rom in a situation like this? Would that even work seeing that factory reset did no good?
I have contacted Glyde and am waiting - they may or may not replace. If they do replace that is a 2-3 week turn-around. I would rather work some magic here, if possible.
Thoughts and help are appreciated!
Brian

You might have to Odin a stock rom most likely
? Powered By My Moga Pro ?

9/10 Times if you can Odin it, you can fix it. BUT, restoring to stock via Odin will break your flash.
Chances are your flash is already cracked up a little.
A simple cricket nv gen google search combined with Odin, drivers, and DFS Tool. You'll be able to get it back up and running smoothly.
And if your device was on a stock rooted ROM, and you have a custom recovery, then flash a 4.1.2 Custom touchwiz ROM. That way, no programming will be lost.
If you decide to flash an AOSP/AOKP ROM like Cyanogen you could possibly break your flash.
2 cents.

fixed
Would you guys believe it was the battery? It was. I swapped batteries and the other phone started doing the same thing. Battery replaced and problem solved. I guess I panicked, but it sure seemed like a software issue. Thanks for the advice.

[Q] Help! What have I done to my Pro 10.1

Here's the story. I purchased a factory refurb'd Tab Pro 10.1 (SM-T520NZKAXAR) on Woot a few weeks back. I live in Canada, but it is a USA tablet, if that matters. It came with a 90-day Samsung warranty. As soon as I got it, I started looking at custom ROMs. I have experience with custom ROMs on my HTC One m8 (and old m7), but not with any Samsung devices. I wish I had kept it stock for a few weeks first to check it out, but here we are.
I created a nandroid backup of the stock firmware, however I quickly deleted it during a wipe when flashing my first custom ROM, which was GraveD's v3.0. It seemed to go OK, but then it would start to freeze up and reboot on it's own. This seemed to happen mostly under load, and especially when trying to install apps from the Play store. I tried going back to the stock kernel, thinking that could be the problem. It stopped the crashing, but then wifi wouldn't work. So I could choose between having a tablet that crashes all the time, and has difficulty installing apps, or one without wifi. Both were basically useless.
I tried installing another custom ROM, GigaWatts Pro. Again, flashing seemed to go well, and the ROM also seemed to work very nicely for a couple of days. No random reboots, and wifi worked great. I spent a few days downloading all of my apps and getting things set up the way I like, when yesterday something went wrong. Perhaps the tablet lost its root (is that possible?). All of a sudden, apps are crashing all over the place (Unfortunately, [insert app name] has stopped). Titanium backup hangs at "Asking for root...". Installing apps is also difficult again. The tab doesn't reboot on it's own, but Play Services crashes constantly. Whenever I try to get into developer options, the Settings app crashes. I'm not even 100% sure USB debugging is enabled right now, although I'm still able to flash using ODIN.
I tried doing a factory reset and re-installing GigaWatts. Same problems. Tried making sure the root was OK. Same problems. I've tried using twrp 2.8.0.0 as well as 2.7.1.0 with no luck.
Right now, I've downloaded the stock firmware for Canada T520UEUANI1 4.4.2 (although the tab was bought from a USA site). I assume this also installs it's own Kernel. It shows Kernel version:
3.4.39-2776001
[email protected] #1
Mon Sep 15 17:44:40 KST 2014
I'm experiencing the same problems. Google Play Newsstand crashes every 10 minutes or so. Settings is almost useless. Installing apps is problematic.
Can anybody tell me if there's something I'm missing? Anything left to try? Does it sound like a hardware/ROM/kernel problem? If it's hardware, can I still utilize the Samsung warranty after trying to flash custom ROMs? I'm going to try to download another Cellular South stock ROM, but it seems like the problems are persisting regardless of which ROM i have installed, so I think it's something else (kernel or hardware-related).
Any help is GREATLY appreciated. My new tablet is basically useless, and I've run out of ideas.

Try this latest firmware since you mentioned your tablet is the XAR model the firmware should be cellular south (wifi)
http://www.sammobile.com/firmwares/download/39630/T520UEUANK1_T520XARANK1_XAR.zip/
If that doesn't help then it could just be a bad tablet .
(btw when you flashed a custom rom you probably tripped the hardware knox flag and voided any warranty it had, I guess you could play dumb if they ask and say it came like that since it was refurbished, and hope they still repair/replace it)

I just tried the USA cellular south firmware. Still experiencing the exact same issues. I'm completely out of ideas. Does anyone else have any ideas? Otherwise I'm going to have to try warranty service and hope for the best. Is there anything I can do to restore the Knox flag before I send it in?
Also, in download mode the tab is recognizing the system as custom. Is this normal after flashing a stock image?

So do a factory reset in recovery, and clear the cache also. Then load the cellular South file thru Odin. Then factory reset again. See if this clears your problems.

k8108 said:
So do a factory reset in recovery, and clear the cache also. Then load the cellular South file thru Odin. Then factory reset again. See if this clears your problems.
Click to expand...
Click to collapse
I've tried the Cellular South firmware to no avail. I'll be trying to warranty the tablet now. Fingers crossed!

OH1 recovery image -or- help getting back to stock firmware

Hi folks. Admitted Noob here asking for help.
[backstory]
After many years resistance I finally decided to get a phone. Freedompop's free plan was enough to push me over the fence. Found a nice S3 (L710VPUDOH1) on ebay and bought it. Everything was fine...except the stock rom had so much crap in it I was about to have a seizure. Back in the day I had put CM on a nookcolor so I thought that was the way to go. I consulted with a friend who assured me that CM played nicely with freedompop so down the rabbit hole I went.
[the first sign of trouble]
Installing CM went fine. Odin. Heimdall. I installed the latest clockwork mod touch recovery (6.0.4.5). Then I installed the latest CM snapshot (cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2spr.zip) and the appropriate gapps. Worked great. Nice and fast, good configuration options, no bloat....but it couldn't connect up to the 3g/4g network. Freedompop worked as long as WiFi was on and would not otherwise. Crap. What's the point of a cell phone if I have to have a WiFi hotspot???
Some googling revealed that the APNs were wrong so I tried that route. I was able to get LTE working but never got 3G. I live out in the boonies, so 3G is kinda important. Also found that CM breaks Sprint's PRL auto update which doesn't seem too happy.
[^H^H^H^H^H]
So, I decided to go back to the factory ROM and see how FP worked as I dutifully made a backup before installing CM. Now the SHTF. When I restore from backup in CWM (followed by a factory wipe data and cache to avoid the boot loop) the ROM cannot connect to Sprint's network. Doesn't know its IEMI or much of anything. It does connect up to wifi, log into my google account, get my paid apps, etc....but still no phone.
I installed Kies and attempted to restore/upgrade firmware (non-emergency mode). Kies got to about 66% and said there was an unexpected error. I'm guessing it didn't like the custom recovery and just plain quit on me. Was worried that I'd made a brick but alas I could still get to download mode. </bullet dodged>
I would like to put the phone back to stock (including recovery) but I have no factory recovery image. Does anyone have a recovery image for L710VPUDOH1? Alternatively, is there any harm in flashing the full ND8 onto the phone even though it had OH1 running before? I seem to remember reading things about bricking phones when trying to downgrade....which is in effect what I would be doing.
Any other suggestions about how to get back to stock would be most appreciated.
TIA

You can flash nd8. Nj2 is newer though. I don't think anyone has captured the oh1 tar yet. The only thing you should not do is flash anything before nd8 (pre Knox) like mk3 or older. Which is jellybean anyways so....
Hope this helps.

Yes, thank you; that was exactly what I needed to know.
I have a working phone at the moment so stock is not necessary required. For others that may be interested I flashed in Wicked X 8.2. From there the phone once again knew its IMEI and I was able to carrier reset and get it activated with Freedom Pop.

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.