I want to reflash the stock firmware, where can I find it? - Galaxy Note II Q&A, Help & Troubleshooting

I bought my N7100 used. Plugging the phone in while turned off wouldn't lead to it displaying a battery bar that shows how much it's charged, but rather a loading circle that's crashed. Now it has developed some other oddities like Wifi not being able to be turned on in this one Deep Impact ROM, and I figured I'd finally get this stuff over with by just reflashing the stock firmware, then putting a custom ROM on it.
Only problem is, where can I find the stock firmware? And which tool could I flash it with? Are there any linux-based ones? Just to be clear, I don't want to return to the stock ROM, I want to actually reflash the firmware, including the bootloader and everything else stored on the phone's memory I suppose. On my old Motorola Droid/Milestone that used to be an .sbf file, not sure what it would be like here.
I hope someone can help me, that would be really cool.

Grus said:
I bought my N7100 used. Plugging the phone in while turned off wouldn't lead to it displaying a battery bar that shows how much it's charged, but rather a loading circle that's crashed. Now it has developed some other oddities like Wifi not being able to be turned on in this one Deep Impact ROM, and I figured I'd finally get this stuff over with by just reflashing the stock firmware, then putting a custom ROM on it.
Only problem is, where can I find the stock firmware? And which tool could I flash it with? Are there any linux-based ones? Just to be clear, I don't want to return to the stock ROM, I want to actually reflash the firmware, including the bootloader and everything else stored on the phone's memory I suppose. On my old Motorola Droid/Milestone that used to be an .sbf file, not sure what it would be like here.
I hope someone can help me, that would be really cool.
Click to expand...
Click to collapse
1. Stock firmware and stock ROM are one and the same thing.
2. Flashing stock rom/firmware might erase data on your internal SD card. So backup the data for safekeeping.
3. Go to sammobile.com --> firmware section and search for N7100
4. You will find latest 4.4.2 firmwares in the list. Choose one from your region. If you are from India, the firmware should be N7100XXUFNI1
4. Use ODIN 3.09 to flash d firmware. Put your firmware in AP tab and start. Sit back and let Odin do the rest.
5. After flashing, your phone should boot to a language selection screen and Odin should convey PASS message.
6. After that you can follow the link given here for root procedure: http://www.ibtimes.co.uk/root-galax...d-4-4-2-kitkat-install-philz-recovery-1447891
7. Your wifi and battery icon should work fine. But you will have a kitkat bootloader. Which means downgrading below 4.4.2 would not be possible anymore.
Hit thumps up if you found this suggestion helpful.
Sent from my GT-N7100 using Tapatalk

Related

[Q] Stock rom question

Hey guys,
So my GS3 (with Rogers) has the WiFi connection issue. Considering that I'd eventually like to flash CM9 and such on my phone, and I heard that I can't access the service menu to disable the WiFi power save in custom roms (not yet, anyway) and that I'd like to have a fully functioning phone, I'm getting a replacement from Samsung (Rogers refused because I was outside the 30 days of warranty!)
So my problem is this: my phone is rooted. I still have the stock rom, but I have CWM installed and such. Thankfully I made sure I didn't trip the flash counter when rooting and such so when I boot into download mode there's no indication that I flashed anything.
So I want to flash the stock rom. Simple! Oh wait, Samsung-updates.com is DOA, they're restoring stuff but I have no idea when it'll be fully back, and as it seems to be the only safe place to grab stock roms, what can I do?
I found this place called Stockroms.net and got the stock rom for my phone, but I have no idea if it's 100% legit or not, as I've never heard of that site. Does anyone have the correct md5 of the Rogers stock rom so I can at least check it against what I downloaded?
Inside the archive I downloaded, there's a file called KIES_HOME_I747MVLALE8_I747MOYAALE8_20120523.225040_REV04_user_low_ship.tar.md5, and a DLL (why is there a DLL in there, I have no clue!) . It sure looks legit, but I can't know for sure until I can actually double-check it against the proper file from Samsung-updates.com...
Can anybody help?

[SOLVED] [Q] Help - getting stuck on boot screen after trying to revert from JB to GB

Hi guys.. I tried installing jelly bean on this device (i8160p and it's not mine) using odin and a stock 4.1 rom I got from samsung updates(I have no root and I went from a never-touched stock)... All went fine, It's working and has all the features. Except that now its owner is asking me constantly to revert back to the original os, since he did find 4.1.2 very slow. So I went back the same path as in the first place in an attempt to get the original gingerbread : I downloaded a stock 2.3 from the site and then tried flashing it.. All again went smooth, with no problems, until I got stuck on the bootscreen and noticed that there was no way to access recovery(download mode working fine though)... So what I'm left with now is a non-booting gingerbreak or the possibility to stay in jellybean(flashing it still works), I'd prefer if I could go back to GB; I think the problem is that there was some conflict caused by jellybean which will require a reset that I can't of course do since I can't boot into recovery, and I don't see any way to install a custom recovery. So can this be done any other way, I'm afraid I'll break this phone before I'll even come up with anything since this is my first experience with roms and boot on an android;
info : as I mentioned There is no root (for now. I might however get into that from jellybean, but I'd rather not if it's possible) and the model is i8160P . an emphasis on the P here since it's the reason I can't find any custom roms, and all I'm left with is the stuff in here
Edit : got gingerbread back after following what angrybb has suggested
Flash the working JB, and after that root your phone like here: http://forum.xda-developers.com/showthread.php?t=2139263 Reboot to recovery and after that follow the howto: http://forum.xda-developers.com/showthread.php?t=2352064 just in step 8 use original gb firmware.
If you can't get adb root access from stock recovery then flash kernel with cwm, for jb for example this: http://forum.xda-developers.com/showthread.php?t=2304432 or this http://forum.xda-developers.com/showthread.php?t=2171054
After flashing one of those kernel, again follow: http://forum.xda-developers.com/showthread.php?t=2352064 , again in step 8 use gb fw
Ok I'll see
Thanks man I'll try what you suggested as soon a I can...
I have a question though: now I noticed that some people fixed this issue by dowloading some other parts (.pit and something else), but of course I'm unable to find these for the model with the P... Now If someone can please tell me if these files have anything to do with the re-partion option in odin(I heard that it does format everything and not just put things on top of things).... Is using it safe given that I don't mind losing data, or should I stay away from it ?
For angrybb : the phone still shows as i8160p in the about section and has access to network...
Here there is a lot talking about pit files, some tehniques with flashing one fw after another, but with no real explanation why this should be done this way. I dont like doing things like that, i want to understand what i am doing. I still haven found some in depth info about pit files.
Anyway, i upgraded from GB to JB with kies, after that i compared some parts of fw and pit file is not changed. Pit from GB and JB have same md5 in my phone, so it is the exactly same file.
I know that method i suggested is not short and plain easy but it is tested and working.
Thanks
Sorry for the delay... For anyone with same problem just follow what angrybb has suggested, but do not under any circumstances ignore backing-up CSPSA_FS and MODEM_FS if you care about your phone's ability to make calls !
hey, maybe you guys could also help me out? i came from a custom ROM that i was having problems with so I wanted to go to an official ROM instead. Originally i came from a GB stock ROM, then i went straight to CM 10.1 but i didnt have any signal on my phone so i tried flashing original stock 4.1.2, now im stuck on the boot screen and i cant access recovery mode. please help?
P.S. my phone is i8160

Hardbricked S3, would like to verify options

Hi,
I'm fully aware of how silly it is to be in this situation. I opened a thread thinking it was in the T-Mobile S3 forum and flashed the downloaded ROM. But regardless, I made an unfortunate mistake.
The ROM was Stockdroid 4.4.2 from the i9300 forum on this site. My phone is a T999v S3. Before beginning any flashing, I rooted and ran Odin to install Philz Touch 6 recovery and "T999VVLUEML2_T999VYVLEML2_T999VVLUEML2_HOME.tar.md5". I was bouncing around firmwares looking for something that could fix the "Camera Failed" error (front camera works when charging but not anywhere else, any advice on that would be greatly appreciated), and I guess I lost track of exactly what I was downloading.
Anyway, after flashing the ROM the phone will not boot, and is almost completely unresponsive. The only life I can get out of it is when I connect it to the computer before taking the battery out, then putting it back in. A red light will shine at some point during that. In device manager the S3 is listed as QHSUSB_DLOAD. This leads me to think I can make use of one of the debricking tutorials on this site for the t999v.
The phone is a 16gb model, but I don't have a 16gb card. Before I go out and buy it, I want to know if buying it should solve the problem. I've read the debrick solution will not work with a 2gb card, but I tried anyway with no luck.
If it does work, great. If not, is my only other solution sending the device in for JTAG?
Thanks in advance for any and all help. I know this problem has been an impossible amount of times, but I wanted to pose the issue specifying the exact scenario I'm dealing with.
Yes the De-Brick thread under Developement will/should work. Make sure there is an image for your variant on that thread, before you buy the SD Card.
Once you successfully De-Brick, I will help with the Camera issue. Its pretty easy to fix in most cases.
Great, thank you!
I'll get back today on whether or not the method ends up working. The debrick image I've been using on my 4.4.2 T999v (on Windmobile) was from this thread:
http://forum.xda-developers.com/showthread.php?t=2439367
As for the Camera issue, should I start a new thread, or can I go ahead and post here?
That's correct thread for your Image. Just be sure you grab for T999V. There are other T-Mo variants too.
For the Camera, continue here when done De-Bricking.
Hi, I just got back and loaded the image on a 32GB microsd. The phone booted up just fine!
I followed the rest of the guide and attempted to reinstall the "T999VVLUEML2_T999VYVLEML2_T999VVLUEML2_HOME.tar.md5" file using ODIN, but it failed during the process. What do I do from here? I would like to be able to use the phone without the 32gb card being taken up like this. Should I try installing a 4.3 ROM of some sort?
Edit: Tried it again and the flash was successful. Just about to install a recovery image, but assuming the install went well I'm guessing I am brick-free? Thank you for the help, Perseus71.
I'll update my post if I run into any other problems regarding the brick, but for now what should I be doing with the camera issue?
I've tinkered a bit with the camera firmware with no luck, and have flashed 4.3 stock again with no luck. What should I do to resolve this issue?
Good to have it back from Brick.
As to Camera, do you still see the Camera Failed issue ? Particularly on the Stock Camera from the 4.3 you just flashed ?
DO NOT use 3rd Party Camera apps until this issue is resolved.
Perseus71 said:
Good to have it back from Brick.
As to Camera, do you still see the Camera Failed issue ? Particularly on the Stock Camera from the 4.3 you just flashed ?
DO NOT use 3rd Party Camera apps until this issue is resolved.
Click to expand...
Click to collapse
Good to know, I'll refrain from using third party camera apps. And even after flashing the above firmware it says Camera Failed.
The problem started on stock 4.3 before any ROM installing/rooting occurred. I tried the obvious clearing app cache, factory reset and wiping dalvik cache, but no luck. Since then I've been installing different ROMs and Camera Firmwares (ZDFE02, ZDFI02, etc), and moving around and setting permissions for SlimISP bin files. I know the rear works when it's being charged, and that the front camera works just fine. I just don't know what I can do to get it working. I've read that replacing the camera itself may not even fix the problem.
Yes I'd say wrong firmware is the Cause. Typically when you do Factory Reset, wipe /data and then Flash the complete firmware image in Odin, it should work. Usually it will contain the correct firmware.
So even though you flashed the image as part of De-Brick process, I suggest do the Odin Flash again. Make sure to do Factory Reset first. When finished, boot to Stock Recovery and wipe Dalvik and Cache.
When phone boots, try Camera by itself before you enter your Google account.
Perseus71 said:
Yes I'd say wrong firmware is the Cause. Typically when you do Factory Reset, wipe /data and then Flash the complete firmware image in Odin, it should work. Usually it will contain the correct firmware.
So even though you flashed the image as part of De-Brick process, I suggest do the Odin Flash again. Make sure to do Factory Reset first. When finished, boot to Stock Recovery and wipe Dalvik and Cache.
When phone boots, try Camera by itself before you enter your Google account.
Click to expand...
Click to collapse
Alright. I flashed the 4.3 image mentioned above with Odin, no problems there. Before flashing I did a dalvik/cache wipe and Factory Reset. When finished, I booted to Stock Recovery, but there was only an option to wipe Cache. Instead I opted to both wipe Cache and do another Factory Reset.
Unfortunately I booted the phone up again, skipping the connect to Internet and Google options, and went directly for the Camera App. I still receive the Camera Failed error.
What should I do from here? Does this mean the Camera itself is faulty? And will replacing it actually solve the problem (or could it be a mainboard issue)?
Also the Camera Firmwares currently on are as follows:
Rear
Camera - ZDFE02
Phone - ZDFI02
Front
Camera & Phone - S5K6A3
Probably a firmware issue, but could be hardware. ZDFE02 is the version your rear cam is currently using. ZDFI02 is what is included with the firmware build you are currently on. Back on ICS, we could update this ourselves, but Samsung has since locked that down. If you could find a way to write the newer version from Phone to Cam it might help, but i don't know of any way to do this anymore.
You said you've been installing different roms and cam firmwares. How were you going about that?
Sent from my SM-N900T using Tapatalk
DocHoliday77 said:
Probably a firmware issue, but could be hardware. ZDFE02 is the version your rear cam is currently using. ZDFI02 is what is included with the firmware build you are currently on. Back on ICS, we could update this ourselves, but Samsung has since locked that down. If you could find a way to write the newer version from Phone to Cam it might help, but i don't know of any way to do this anymore.
You said you've been installing different roms and cam firmwares. How were you going about that?
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
For ROMs I would simply boot into a custom recovery and flash them, along with kernels, heeding any warning signs in threads. I wouldn't run into any errors, and could swap between 4.3 and 4.4.2 without issues. I didn't extensively test out the ROMs, but it seemed fine.
For Camera Firmware, on a StockMOD 4.3 ROM I dialed *#34971539# to get into the CameraFirmware menu. From there I could write new firmware depending on the SlimISP bin file transferred to the internal root. I can't remember thinking back if the Camera firmware actually changed when I did this, but the Phone firmware did (or maybe vice versa, I'll try again -- I know there was a change after writing).
So I do remember reading you can't downgrade lower than 4.3, that must be true then? If I could go down to ICS I could force the Camera Firmware to change?
What's the target Camera Firmware here? Does it need to be the same as the Phone Firmware (i.e. ZDFI02)?
ZDFI02 is newer. You'd need to do the Phone to Cam F/W Write operation.
I also wondering if maybe the files in /system/etc/cameradata folder are the wrong ones. Been a while, but I think that's where you should find some camera files that should match the name if the firmware versions mentioned above.
Maybe some one can confirm this....
I not sure if you flash an ICS rom if it'll work. Might be worth a shot though.
Sent from my SM-N900T using Tapatalk
DocHoliday77 said:
ZDFI02 is newer. You'd need to do the Phone to Cam F/W Write operation.
I also wondering if maybe the files in /system/etc/cameradata folder are the wrong ones. Been a while, but I think that's where you should find some camera files that should match the name if the firmware versions mentioned above.
Maybe some one can confirm this....
I not sure if you flash an ICS rom if it'll work. Might be worth a shot though.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Could I use the ZDFI02 firmware from this thread?
http://forum.xda-developers.com/galaxy-s3/general/jb-4-1-2-camera-driver-t2006128
I'll find a way to get the Camera Firmware to ZDFI02 and get back to your both.
I going to guess that using that would be ok, but I cannot say for sure since it is for the I9300, which is a very different device from ours.
Sent from my SM-N900T using Tapatalk
Well, I loaded StockMOD 4.3 back on, and while it enables me to write Camera Firmware (no longer greyed out), the Camera Firmware will not change from ZDFE02 to ZDFI02. Do you have any suggestions as to what I can do to get around this? Will downgrading to ICS lead me to another brick?
It shouldn't brick. Can't think of any reason it would. Stability might be more of an issue though.
Sent from my SM-N900T using Tapatalk
Alright, I've loaded on a 4.0.4 ICS ROM. When I input the *#34971539# code, I get the error "Unfortunately factory test has stopped."
Now that an ICS ROM has been loaded, what is the method for flashing the ZDFI02 firmware to CAM?
It was using the dialer code. I guess that since it's an ICS app trying to make changes to your 4.3 firmware it's running into compatibility issues. It sounds like you are doing it correctly, just the versions must be too far apart....apologies for putting you through the hassle of doing all that. It was the best thing I could think to try though. If I think of any other ideas I will certainly let you know. There might be a way to load it using terminal emulator, but I've no idea how you would go about that.
Only other thing would be to try and edit the code of the Factory Test app on 4.3 to enable the Phone to Cam F/W Write option. I had looked into it briefly back on 4.1.2, but Im too much of a novice when it comes to java. I'd still love to know if it's even possible though. We were able to enable JB camera features before the official release by doing the F/W write, so you never know when that could happen again!
Sent from my SM-N900T using Tapatalk
---------- Post added at 09:34 PM ---------- Previous post was at 09:32 PM ----------
It's another sort of shot in the dark, but you could try replacing the camera module. Find a YouTube video showing the S3 disassembly, it really not that difficult, and you can find the camera module online fairly cheap.
Sent from my SM-N900T using Tapatalk
t999
hi friends
my s3 sgh-T999 is bricked:crying:
i can access downloading mode but when i try to put phone in recovery mode phone just show robot logo for a second then restart
i tried every solutions(flash recovery,flash stock or any other roms and ...) here but nothing changed
sometime phone boot and some chines words appear with one button !!
*odin 307 detect phone
http://forum.xda-developers.com/attachment.php?attachmentid=2668840&stc=1&d=1396652278
thanks
If you can get in download mode and it is seen by odin, flash the latest firmware.
Sent from my SM-N900T using Tapatalk

Frustrating In-Call Audio/Modem Issue

To anyone more of an expert than myself on these matters (which I presume to be a large portion of users here), I'd greatly appreciate any help that can be provided. I'd also like for this thread to be a central collection of baseband/modem functions, behaviors, troubleshooting, etc...
I've had a T-Mobile S4 (SGH-M919) for a while now and have mostly used CyanogenMod derived ROM's and as of lately, more Google Play Edition/Nexus type ROM's (which generally appear to be written for the international i9505 and hence show the model number of my phone to be such; this may or may not be relevant). All of the sudden, the other day during a phone call I received, there was no audio on either end of the call. I couldn't hear the caller nor could the caller hear me. This also happens if I initiate the call. I know for a fact that the media speakers (speakers used during speakerphone) as well as the earpiece speaker are perfectly functional so it's not a case of hardware failure where it works on Bluetooth or speakerphone only. As soon as a call initiates, you hear no ringing or audio once the caller answers other than the tone when the call ends/disconnects. First thing I tried was switching from ART back to Dalvik just for the sake of troubleshooting. Second, I tried clearing the cache (and Dalvik, just for the hell of it). Still no success. So next I try a completely different ROM. I was presently on a GPE ROM with the Samsung kernel so I switched to plain CyanogenMod with a custom kernel. I even went back to a stock ROM! No success either way!!
It was at this point I decided that it had to be a hardware/firmware issue since the issue remained when changing ROM's so I naturally assumed baseband/modem. I don't understand why this issue just magically occurred one day when I hadn't changed anything, but I thought that if I reflashed a clean modem image or and updated one, then maybe it would fix it... I was on MDL so I reflashed the MDL modem. No success. Then (and here's where I f****d up), I tried flashing what I THOUGHT was a stock NB4 firmware file in ODIN. Turns out that despite being labeled as stock, it had a custom kernel built-in and tripped my KNOX counter (FFFFFUUUUUUCCCCCKKKK!!!) Well, since I really only intend to use AOSP/CM based ROM's, it's not such a huge deal for me but still, it sucks.
Here's where I had a break: Yesterday, I tried flashing the MDL modem again, then that didn't work so I tried flashing the MK2 modem. I booted up, made a call, and it worked! First time! Well, that was short lived success because I tried another call immediately after to verify and it started all over again. Now, even reflashing MK2 won't get it to work even once like it did this one time.
Does ANYone who understands baseband and modem firmware much better than I do have any insight or instruction on what I can do? Because of this one issue, I have an otherwise perfectly good S4 that I can't use just lying around. I've had a Nexus 5 for almost a year and love it but I just destroyed the screen after a drop the other day and wanted to switch to the S4 temporarily until the Nexus 6 comes out. ANY IDEAS????
Loss of call audio occurs when your rom and firmware versions dont match. Since you've tripped your knox counter, you have some more freedom now. I think you should (after someone confirms) use the samsung pc software to do a full restore of your phone. It will blow away everything you have and install the latest firmware and matching rom as if you were stock and accepted all otas. Then you can root, flash recovery, flash rom, restore backed up apps. You'll have the cleanest possible setup. Just wait for someone to confirm because i haven't been following closely in the past few months. Alternatively you can find the latest firmware and do it with odin but in your position theres no advantage to doing it piece-meal like that (unless i've missed something in the past few months) because you've already tripped knox
faiyo said:
Loss of call audio occurs when your rom and firmware versions dont match. Since you've tripped your knox counter, you have some more freedom now. I think you should (after someone confirms) use the samsung pc software to do a full restore of your phone. It will blow away everything you have and install the latest firmware and matching rom as if you were stock and accepted all otas. Then you can root, flash recovery, flash rom, restore backed up apps. You'll have the cleanest possible setup. Just wait for someone to confirm because i haven't been following closely in the past few months. Alternatively you can find the latest firmware and do it with odin but in your position theres no advantage to doing it piece-meal like that (unless i've missed something in the past few months) because you've already tripped knox
Click to expand...
Click to collapse
Thanks for the response! This was actually the approach I initially wanted to take when reflashing just the modem didn't work; that is, using Samsung Kies to do a complete Samsung official firmware download and restore. Unfortunately, every time ibtry and do the "emergency recovery" as they call it, once I type in my serial number and model like the app requires, it always tells me that the device is not supported! It's like the device's firmware has been programmed as another that isn't recognized by Samsung. At first I thought it was because I was on a custom ROM and it didn't recognize the software. I remember a while back I needed to do an official restore and I had to get the phone boot loader to read status "Samsung Official" and not just official. I actually put stock everything back on manually and got those status fields to read Samsung Official for the binary and kernel but it still won't restore with Samsung's software. It's my estimation that Samsung has now integrated the Knox counter into their software support. I'm assuming that with that sensor tripped, I can never be "official" and therefore supported again. That's why I've been doing everything Odin. With all of this in mind, do you have any other recommendation? I'll look a little further into the problems I've had with Kies and maybe why I can't restore in the meantime but otherwise, why do you think flashing MK2 modem worked for just ONE call and then stopped again? And why do you think that the issue just suddenly happened in the first place without a software change?
thair7391 said:
Thanks for the response! This was actually the approach I initially wanted to take when reflashing just the modem didn't work; that is, using Samsung Kies to do a complete Samsung official firmware download and restore. Unfortunately, every time ibtry and do the "emergency recovery" as they call it, once I type in my serial number and model like the app requires, it always tells me that the device is not supported! It's like the device's firmware has been programmed as another that isn't recognized by Samsung. At first I thought it was because I was on a custom ROM and it didn't recognize the software. I remember a while back I needed to do an official restore and I had to get the phone boot loader to read status "Samsung Official" and not just official. I actually put stock everything back on manually and got those status fields to read Samsung Official for the binary and kernel but it still won't restore with Samsung's software. It's my estimation that Samsung has now integrated the Knox counter into their software support. I'm assuming that with that sensor tripped, I can never be "official" and therefore supported again. That's why I've been doing everything Odin. With all of this in mind, do you have any other recommendation? I'll look a little further into the problems I've had with Kies and maybe why I can't restore in the meantime but otherwise, why do you think flashing MK2 modem worked for just ONE call and then stopped again? And why do you think that the issue just suddenly happened in the first place without a software change?
Click to expand...
Click to collapse
A few notes: i have a similar problem in the last few months. After about 12 hours of uptime i cannot hear the other caller. I thought it's because im using ****ty roms from these forums so i was about to go to the international forums and flash theirs. I only use touchwiz roms so far. And it manifests about a week after flashing the rom. And i have to reboot twice a day to keep it functioning So yeah.. i get it too even tho i had a matching baseband
I think the reason you tripped knox wasnt because of the kernel. It's because a stock firmware package will upgrade your bootloader, while you should have actually been pursuing a modem-only package to flash with odin (which preserves the MDL bootloader and prevents tripping knox).
Anyways, im not sure what you have done with the "Samsung offical" status or modifying the identifiers of the phone but i was pretty sure kies would restore it. If not, then you should be trying to flash stock firmware (full) for NH7 firmware which was released recently. Not just modem only, which is what some of the packages here contain (meant for people with MDL bootloaders who dont want to trip knox). Try to pursue the full firmware odin flash. Im pretty sure that would do it for you. It should be the full-on samsung stock.
About kies: i haven't used it but i've experienced weird things happen with adb and specific usb cables and usb ports on the computer, even with nexus devices. I hate to suggest this but try a different computer and different usb cable. Its an actual solution thats worked before. It messed me up before and a number of other people. Make sure its up to date too i kinda recall old versions had a compatibility issue
faiyo said:
A few notes: i have a similar problem in the last few months. After about 12 hours of uptime i cannot hear the other caller. I thought it's because im using ****ty roms from these forums so i was about to go to the international forums and flash theirs. I only use touchwiz roms so far. And it manifests about a week after flashing the rom. And i have to reboot twice a day to keep it functioning So yeah.. i get it too even tho i had a matching baseband
I think the reason you tripped knox wasnt because of the kernel. It's because a stock firmware package will upgrade your bootloader, while you should have actually been pursuing a modem-only package to flash with odin (which preserves the MDL bootloader and prevents tripping knox).
Anyways, im not sure what you have done with the "Samsung offical" status or modifying the identifiers of the phone but i was pretty sure kies would restore it. If not, then you should be trying to flash stock firmware (full) for NH7 firmware which was released recently. Not just modem only, which is what some of the packages here contain (meant for people with MDL bootloaders who dont want to trip knox). Try to pursue the full firmware odin flash. Im pretty sure that would do it for you. It should be the full-on samsung stock.
About kies: i haven't used it but i've experienced weird things happen with adb and specific usb cables and usb ports on the computer, even with nexus devices. I hate to suggest this but try a different computer and different usb cable. Its an actual solution thats worked before. It messed me up before and a number of other people. Make sure its up to date too i kinda recall old versions had a compatibility issue
Click to expand...
Click to collapse
So quick update/reply, I just stumbled upon a stock, lightly modified MK2 ROM flashable through recovery that I had buried on my microSD and decided to give it a go (since the MK2 modem was the only one that every gave me any success even though it was just one time, and even though the ROM I was using was custom so couldn't have really matched ANY Samsung baseband). Even though I really already knew and understood everything you told me, you were brilliant to remind me about the need for the modem to match the OS when it initializes. After booting up the Stock MK2, calls are now working, and consistently!!! Now I'm making a backup (just in case, even though I really don't want to use stock) and then I'm going to go for a custom ROM again, probably CM based. Thanks again for your help!
I know exactly how I tripped the Knox counter. I downloaded a firmware file that was LABELED as a stock NB4 ROM and that wasn't correct. It was a stock NB4 ROM with a MODIFIED CUSTOM KERNEL! That would have been a useful detail beforehand...
I'm also familiar with using adb and it's selectivity with USB cables. They need to be "fastboot" cables which usually only is the case with manufacturer included cables. Using Kies to restore firmware to a phone though should have nothing to do with fastboot or adb. First off, you don't need the adb Runtime or SDK to use Kies nor does Samsung include it in the installation. Second, when you're using Download mode, that's Samsung's proprietary software using their own proprietary API's and commands to communicate and interface directly with their hardware so I think the issues I've had with Kies is something else. I appreciate the suggestion though.
As far as the matching modem and software goes, I'm a bit confused... Why is it that you can use custom ROM's non-related to Samsung after updating your baseband if the custom ROM isn't matching that firmware? Perfect example, just now... I tried the stock MK2 and it worked. Now I just finished loading clean CyanogenMOd, and it worked! BUT - only one and a half times... It went through once, I tried again, and then it stopped mid ringing of the call, now doesn't work. AHHHH!!! How am I supposed to do this? And why did I never have trouble in the past? Once I get a stock ROM and matching, working modem installed, what am I supposed to do from there if I want to switch to a CM based ROM?
thair7391 said:
So quick update/reply, I just stumbled upon a stock, lightly modified MK2 ROM flashable through recovery that I had buried on my microSD and decided to give it a go (since the MK2 modem was the only one that every gave me any success even though it was just one time, and even though the ROM I was using was custom so couldn't have really matched ANY Samsung baseband). Even though I really already knew and understood everything you told me, you were brilliant to remind me about the need for the modem to match the OS when it initializes. After booting up the Stock MK2, calls are now working, and consistently!!! Now I'm making a backup (just in case, even though I really don't want to use stock) and then I'm going to go for a custom ROM again, probably CM based. Thanks again for your help!
I know exactly how I tripped the Knox counter. I downloaded a firmware file that was LABELED as a stock NB4 ROM and that wasn't correct. It was a stock NB4 ROM with a MODIFIED CUSTOM KERNEL! That would have been a useful detail beforehand...
I'm also familiar with using adb and it's selectivity with USB cables. They need to be "fastboot" cables which usually only is the case with manufacturer included cables. Using Kies to restore firmware to a phone though should have nothing to do with fastboot or adb. First off, you don't need the adb Runtime or SDK to use Kies nor does Samsung include it in the installation. Second, when you're using Download mode, that's Samsung's proprietary software using their own proprietary API's and commands to communicate and interface directly with their hardware so I think the issues I've had with Kies is something else. I appreciate the suggestion though.
As far as the matching modem and software goes, I'm a bit confused... Why is it that you can use custom ROM's non-related to Samsung after updating your baseband if the custom ROM isn't matching that firmware? Perfect example, just now... I tried the stock MK2 and it worked. Now I just finished loading clean CyanogenMOd, and it worked! BUT - only one and a half times... It went through once, I tried again, and then it stopped mid ringing of the call, now doesn't work. AHHHH!!! How am I supposed to do this? And why did I never have trouble in the past? Once I get a stock ROM and matching, working modem installed, what am I supposed to do from there if I want to switch to a CM based ROM?
Click to expand...
Click to collapse
I really have no idea about aosp roms for this device because i only used touchwiz to keep samsung features.. so i have no knowledge about firmware compatibility. I would think the creator of the rom should specify any firmware requirements.
On the thought of hardware failure, and i know you said the speakers work, but did you test the sim card slot? Perhaps it needs to be cleaned? Maybe the sim card is partially failing so try a different card? Maybe you cut it and it's loose (you wont believe the crooked sim cards i've seen). I think it's worth pursuing since you said it worked once and not again.. maybe you had just taken the cover off while flashing stuff and touched/pressed it but it's losing contact again after flexing during use. I dunno dude, the kind of call audio issues i've had were always resolved with a reboot & making sure the modem matches the touchwiz build.
Please make sure you are running a full stock firmware package & keep the touchwiz rom consistent with it. Some firmware packages are partial components
So now I've just updated to a FULL STOCK NH7 firmware package. My build number and baseband are matching. NO CALL AUDIO!!
For starters, up until a few days ago, I ran all types of ROM with an MK5 boot loader and 3 different modems and never had a call issue. After that said, I read a few months ago about a guy had your same issue. He ended up getting a new sim card and he got is audio back. He also had reception issues before getting the no audio issue.
thair7391 said:
So now I've just updated to a FULL STOCK NH7 firmware package. My build number and baseband are matching. NO CALL AUDIO!!
Click to expand...
Click to collapse
Try flashing the firmware again, some have to flash it twice for the bootloader to update, which may the trouble. If that doesn't work try a new sim like it was suggested before me
I know it's been a while but I basically gave up and just recently came back to it. I've since bought a Nexus 6 so it's not a priority issue anymore however I would still like to fix this otherwise perfectly fine Galaxy S4 that I have lying around! I seemed to believe that there was a special combination of custom ROM and specifically the MK2 modem that would sometimes cause the audio to intermittently work but it appears I was wrong. I flashed the full stock NH7 firmware/baseband etc back to my phone twice as suggested and NY audio worked! For a few calls that is... Then it stopped working again. Sometimes I could clear cache and reboot and it would work! Once or twice anyways before crapping out again... The bottom line is that there isn't a pattern aside from a cleared cache that makes the audio work again before it stops soon after which unfortunately leads me to believe it's a deep rooted hardware issue in the baseband itself. Anyone else have ideas?
Other than trying a new sim, I can't really think of anything else except to make sure the bootloader really did update. Download Samsung phone info from play store and check bootloader info to make sure it was updated to NH7
Unfortunately it is completely updated. I tried a new SIM and everything works still except audio in phone calls, including ringing. I guess it's hardware... Guess now I just have an internet browsing MP3 player with web browsing capabilities.

[Q] Bricked my phone... Need Help.

Like I'm sure this topic hasn't come up before, but I've searched for hours and I'm probably just making things worse. I also just accidentally deleted this post halfway through. It's too late and I'm too tired and I have no working phone.
Bought an SGH-I747 on E-Bay. Got a Straight Talk SIM card kit, activated it, so far so good.
Rooted it with CF-Auto-Root. Worked pretty well, took a lot of reboots, upgraded the SU from the Play Store and it got rid of Knox. So far so good. Got everything all set up the way I like it. Happy.
It was running 4.4.2. I'm assuming it was the release prior to the November 12th OTA release, but I can't say for sure.
Phone downloaded and installed an upgrade automatically. Now, it won't boot. I get the SAMSUNG logo, then the Samsung Galaxy S III logo then nothing.
I retried the CF-Auto-Root, no change.
I booted into recovery (volume up, home and power on), did factory reset, no change.
Started looking around for a way to return it to stock. Found an upgrade43.zip file somewhere (I'm sorry I can't find where I got that now). Put it on the sdcard card and tried installing it with the recovery and it fails part way through.
At this point, I think I probably need to completely overwrite everything with something stock. I just don't know how to do that. I see posts on such subjects but they all have warnings that make me think I'm going to totally brick the phone, so I'm hoping someone can point me the right way. I'm not all that Android savvy, as you can tell.
Help.
Since your phone was running 4.4.2, do not attempt to flash any ROMs using that attempt to downgrade your bootloader to anything prior to 4.4.2.
Try this to get your phone up and running:
download the latest CM11 for the d2lte and save it to an external SD card: https://download.cyanogenmod.org/?device=d2lte
dowload the latest tar.md5 version of Philz Touch for the d2lte from here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
boot phone in download mode, open Odin 3.07, do not check anything except f.reset.time, flash Philz via PDA box, remove USB cable when you see the word Reset appear in the status window, remove battery, replace battery, boot into recovery, format system, Dalvik, data, and cache, flash cm11, and reboot.
Thank you for your reply. There are a few things in there I don't quite understand, but I think I can figure it out.
I was going to attempt this...
http://forum.xda-developers.com/showthread.php?t=2658486
In fact, I did attempt it with TWRP last night after I posted here and new I still wasn't going to sleep. I kept getting an error about a bad ZIP file.
Is that stock restore a bad idea?
Do not attempt to flash an older bootloader. The mjb bootloader is from 4.3 and attempting to flash it could hard brick your phone.
I suggest doing what I suggested so you can confirm the bootloader and modem installed on your phone.
OK. Thanks. Probably a good thing I couldn't get it to work then.
Thank you so much. I have a working phone again. Now I just have to get it all set back up the way I like it.
I have to say, and it's probably words straight from the devils mouth, that I kind of wish I could have restored the Samsung stock software. It's just what I'm used to. But I will take what I can get.
A few questions. I like having root. But root is what got me in trouble in the first place. Is this going to be rooted now, or will I have to do that or am I better off just leaving it alone.
Second, I'm probably going to have questions since this is so different than what I'm used to (like I already can't find the Play store). Where is the best place to ask?
If you want root, one of the easiest ways to get it is to flash supersu from your custom recovery. Most ROMs are pre-rooted.
Many custom ROMs do not include Gapps. Just download and install the Gapps version for your ROM.
If you like the TW look, flash a TW-based ROM. Check out the development threads for different ROMs.
here is a thread for Q's that has some pretty good/friendly helpers on it if you need.
http://forum.xda-developers.com/showthread.php?t=2257421
"all i can really do , is stay out of my own way and let the will of heaven be done"
How to save in to external SD card
How do you save the file into the external SD card? I am having the same brick issue with my GS3.
To save a file to an external SD card, just put the card into a card reader and save the ROM to the SD card.

Categories

Resources