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.
Related
I've been working off and on for a week on this and I'm guessing I'm out of luck but figured I'd ask just in case I missed something on here.
I've been attempting to resurrect my father's GNex. He had it working fine -- stock 4.2.2 via OTA updates - it's never even been unlocked -- and then suddenly it gets stuck in a bootloop. He tried resetting it back to factory settings but it continued the loop -- would get as far as the language selection screen and then would reboot.
I attempted to unlock/reflash using the toolkit and it would get stuck on flashing the CDMA radio -- will hang for hours if I let it. I've tried the current 4.2.2 build, the original 4.0.4 using the GalazyNexusRestore utility, and everything in between. I've tried flashing the radios via CWM as well.
Of course I only attempted this myself (I've been rooting and installing ROMs since the G1) because the warranty ran out in August. Is there anything else I can try before giving him the bad news?
first of all have you tried odin? (basically its samsungs flashing tool)
second of all is a verizon gnex or sprint? (both are cdma)
for verizon try this- http://www.galaxynexusforum.com/forum/rescue-squad/4707-how-return-stock-using-odin-vzw-lte-only.html
for sprint try googling for "sprint galaxy nexus stock odin files" (mainly all you need are the correct files for sprint and the guide in the verizon post should work)
Finally got around to trying Odin. Just gave it a go (I've got a verizon phone) and it failed on radio.img.
I assume that there's nothing else that can be done?
Good day,
I'm wondering if anyone has gone through this; it goes like this, last night I flashed my n7100 Note 2 with a stock rom 4.1.2 XEF (France)(the same exact rom I used to flash my phone with for 10ths of times) nothing went wrong as Odin completed the processes successfully (apparently) rebooting the phone to finalize the installation, however it booted into the previously installed system, including all of the apps I installed earlier, in other words nothing's changed at all, I hope I'm making sense, I tried two different computers ending with the same result, how come it worked like charm before and now it does not? Thanks again for any advice.
After browsing the internet all day yesterday I never did see an actual fix for this issue for this specific model. I did see a lot of random ones for different carriers which would probably work. But not for Sprint specifically.
Problem? My Sprint Galaxy Tab 3 7" failed at 27% whenever I attempted to update it.
Issue: The Tab was Rooted by my brother - who then Un-Rooted and returned it back to Factory before giving it to me. Then failed to mention he had rooted the thing to begin with.
Fix: Re-Flash using Odin and stock 4.2 image.
So I tried getting Kies installed and working. Tab would NEVER connect no matter what I did. I tried installing the USB drivers again (though the computer recognized the damn thing), reinstalling Kies, trying to put Kies into Compatibility mode (since I'm on Windows 8.1)
After ALL that I finally called my brother who gave it to me as a gift. Found out the thing may or may not have been Rooted. But he thought he had reverted it back to stock and un-rooted it.
So back to searching on the internet. Finally found this article: http://theunlockr.com/2014/03/21/unroot-samsung-galaxy-tab-3-7-0-sprint/ which suggested I try re-flashing using Odin to get rid of Root on the device.
I followed the steps in the article (Tip: Do a search on Google for the correct image zip for your model tablet and download it from androidhostfiles) Example for my specific model T217SVPUANB8: http://www.androidfilehost.com/?fid=23329332407579787
Was able to restore it back to "true stock" and was able to update to KitKat. Kies started working finally. And all was well with the world again.
Oh, and I uninstalled Kies immediately after I was done with that POS software. :silly:
Hopefully this will help the I dunno the two other people that still have one of these that they received for free from Sprint.
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.
So like many of you, I have been really frustrated with T Mobile that they are the only carrier not to upgrade their Note 2 to Android 4.4, and they probably never will. There are more an more apps that I cannot run, some of which are important to me. So I gave up with calling T Mobile, and struck out on the custom ROM trail, seeing that CM has a 4.4 mod for this phone. After rooting and attempting to unlock (not necessary) and changing to custom recovery, I managed to get the CM mod loaded and running, after many hours of learning by trying everything, I got the phone running on the CM 4.4 mod, only to find that I could not make any calls, as there are no mods, anywhere, that support T Mobiles WiFi calling. I guess T Mobile uses that because their network is weak, but hey, I have used Sprint, AT&T and Verizon over the years, and every network has holes, especially inside buildings. It so happens that both where I work and at my home is spotty, so I cannot survive as a phone without WiFi calling. After all, for all of the bells and whistles, a Smart Phone is first and foremost a Phone. So after all that, I started on a new trail, unrooting and installing a stock mod.
There are lots of help out here that tell how to unroot and go back to stock, and they are all trash, every one of them. I tried stock mods from several sources (SAMMOBILE and others) and only found two out of six update versions that even functioned on my phone, and only one of those actually worked like it should, and that was the very first 4.1.1 version T889UVALJ1 that came with my phone years ago. No LTE and more apps that would not install at this level. I was hoping to at least get to the T889UVCOH4 version of 4.3, which is the current latest version from T Mobile.So here I was, an older version of ROM on my phone, no LTE, Flash counter not at zero, and Knox telling the world the phone was modified, excluding any chance of help. Why in the world did I even step into these problems. And then I made a startling discovery.
As I tried to at least restore the data backup I did before this whole thing started by using Smart Switch from Samsung, I found that not even that would recognize my phone because of the older version of android so I could not even get to my backups. When I got the phone it used Kies, but with the 4.3 version of android, Samsung changed over to Smart Switch. So at that moment I felt I was completely screwed. Then I saw the little "More" button on the Smart Switch dialog that was telling me my phone was not supported, and I clicked it. It brought me to some other options, and one was emergency recovery, which allowed for an initialization after a failed upgrade. I did not expect much, as my phone was not supported anymore, but I could not see any other option, so I chose to initialize the phone for recovery.
Well guess what, everything ran perfect, and when the process was completed, my phone was just like new, no flash record, no Knox report, a completely authorized phone. It was if I had never rooted it at all, and I had flashed a dozen ROMs. So for everyone that has a bricked or soft bricked Samsung phone or find out the custom ROMs are not what you were hoping for, all you need to do to get it back is install Samsung's Smart Switch on your computer and click the little "more" button on the screen and reinitialize your phone. It will be like the whole rooting and ROM experience was a bad dream, And yes, the backup did load when I was finished. It is that simple. This should work for any Samsung with Android 4.3 or higher on any carrier.