Related
Hey guys,
I've been working on rooting the new Captivate Glide, and unfortunately my kernel flash with ODIN failed (inexplicably). Now the device is complaining I need to perform an emergency recovery, but of course the device isn't listed in the KIES panel.
Apologies if this is covered elsewhere, but I searched and didn't find anything.
Can anyone explain how KIES works? What is a recovery code? Do I need to get one from Samsung? Is there any other way to force it to perform the recovery on my semi-bricked phone?
Wrong forum ...
There isn't a forum for him yet, so this is the best he could do.
Try going to download mode and flashing again! Try again, until it works, redownload the kernel.
Sent from my SGH-I897 using xda premium
Actually, strangely enough ... I entered 3e recovery (out of desperation) and rebooted, and it cleared the flag, allowing it to boot up normally.
I checked the kernel timestamp (cat /proc/version) and it appears to still be the stock kernel, so the NAND update completely failed.
I still would like to figure out how to force a KIES recovery, but at least for the moment I'm back up and running (till I take my next shot ).
Kies is garbage, don't worry about it.
It's just like Odin only there are a retarded amount of checks to make sure it's a supported phone...which usually fail if you're on anything other than stock or your imei has changed to a generic one, or any other reason it wants to make up to fall.
To root you should be able to flash the fugu kernel, which will cause a bootloop, then flash that stock kernel again, then once that boots you should have root.
studacris said:
Kies is garbage, don't worry about it.
It's just like Odin only there are a retarded amount of checks to make sure it's a supported phone...which usually fail if you're on anything other than stock or your imei has changed to a generic one, or any other reason it wants to make up to fall.
To root you should be able to flash the fugu kernel, which will cause a bootloop, then flash that stock kernel again, then once that boots you should have root.
Click to expand...
Click to collapse
Frustrating. The n900 flashing tool was so excellent (and cross-platform). Wonder why Samsung would release such a piece of junk.
Anyway, I'm back in business now and still working on it.
I'd love to try one of the other kernels, but since I don't have any recovery path (stock kernel / image / firmware), I'm really nervous now.
Ok.. So I got my S3 (Sprint version) in November. After I upgraded to JB (Android v4.1.1) I rooted my device. Played aroubd with some ROM's, had the TWRP recovery installed. Everything worked fine, and the phone actually still works great. A couple of weeks ago it told me there was a system update available. I didn't know of it was safe to allow it to happen or not since I was rooted so I used TWRP recovery to flash a stock rom that would unroot my s3 and reset the flash counter to zero and make it all stock in one bang. So I did that, went and cleared the data in Google Services Framework so I could redownload the update, I restart to let the update install and it shows the android guy with the blue thing in his belly, but only goes about half way through the process and just stops, the android guy quickly dissapears and another pic of him pops up of him laying on his back with a red triangle over his belly, then the phone quickly reboots and goes back to my lockscreen.
As seen in the pic, I must be getting some of the upgrade as the baseband version shows MA6, but the build number still shows LJ7 and the Android Version still shows 4.1.1. Also I went to the camera and can take burst shots by holding dowb the camera button, which is a new feature.
But with things the way they are, I can continue to clear out the data from google services framework and still get notified of the 157mb update download. But every time I do it, it does the same thing as explained above. I have also tried to download the update in a .zip file and flash it in recovery mode. There it seems like it goes through the entire process but I still get the same result as seen in the pic. I also tried downloading the stock recovery and flashing that with Odin just in case. So basically I have a sprint galaxy s3, unrooted, 4.1.1 android software with a bit of 4.1.2 in there. Does anyone have an idea how to fix this?
Any help is greatly appreciated.
Mike
Sent from my SPH-L710 using xda app-developers app
I really hope someone helps with this, because oddly enough, I just had the exact same problem!
rmstorms said:
Ok.. So I got my S3 (Sprint version) in November. After I upgraded to JB (Android v4.1.1) I rooted my device. Played aroubd with some ROM's, had the TWRP recovery installed. Everything worked fine, and the phone actually still works great. A couple of weeks ago it told me there was a system update available. I didn't know of it was safe to allow it to happen or not since I was rooted so I used TWRP recovery to flash a stock rom that would unroot my s3 and reset the flash counter to zero and make it all stock in one bang. So I did that, went and cleared the data in Google Services Framework so I could redownload the update, I restart to let the update install and it shows the android guy with the blue thing in his belly, but only goes about half way through the process and just stops, the android guy quickly dissapears and another pic of him pops up of him laying on his back with a red triangle over his belly, then the phone quickly reboots and goes back to my lockscreen.
As seen in the pic, I must be getting some of the upgrade as the baseband version shows MA6, but the build number still shows LJ7 and the Android Version still shows 4.1.1. Also I went to the camera and can take burst shots by holding dowb the camera button, which is a new feature.
But with things the way they are, I can continue to clear out the data from google services framework and still get notified of the 157mb update download. But every time I do it, it does the same thing as explained above. I have also tried to download the update in a .zip file and flash it in recovery mode. There it seems like it goes through the entire process but I still get the same result as seen in the pic. I also tried downloading the stock recovery and flashing that with Odin just in case. So basically I have a sprint galaxy s3, unrooted, 4.1.1 android software with a bit of 4.1.2 in there. Does anyone have an idea how to fix this?
Any help is greatly appreciated.
Mike
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
I suggest you should go check out the Sprint Samsung s3 forum under the Android development section the check out for the stock rom, try using the 1 click Odin or check out in there the proper way to restore your device, then continue reading the forums to check out when or how is the proper way to apply that update it could be that its bugged or that your device lost some permissions so best way to solve it should be to restore it to its original state.
Sent from my SPH-D710 using xda app-developers app
rmstorms said:
Ok.. So I got my S3 (Sprint version) in November. After I upgraded to JB (Android v4.1.1) I rooted my device. Played aroubd with some ROM's, had the TWRP recovery installed. Everything worked fine, and the phone actually still works great. A couple of weeks ago it told me there was a system update available. I didn't know of it was safe to allow it to happen or not since I was rooted so I used TWRP recovery to flash a stock rom that would unroot my s3 and reset the flash counter to zero and make it all stock in one bang. So I did that, went and cleared the data in Google Services Framework so I could redownload the update, I restart to let the update install and it shows the android guy with the blue thing in his belly, but only goes about half way through the process and just stops, the android guy quickly dissapears and another pic of him pops up of him laying on his back with a red triangle over his belly, then the phone quickly reboots and goes back to my lockscreen.
As seen in the pic, I must be getting some of the upgrade as the baseband version shows MA6, but the build number still shows LJ7 and the Android Version still shows 4.1.1. Also I went to the camera and can take burst shots by holding dowb the camera button, which is a new feature.
But with things the way they are, I can continue to clear out the data from google services framework and still get notified of the 157mb update download. But every time I do it, it does the same thing as explained above. I have also tried to download the update in a .zip file and flash it in recovery mode. There it seems like it goes through the entire process but I still get the same result as seen in the pic. I also tried downloading the stock recovery and flashing that with Odin just in case. So basically I have a sprint galaxy s3, unrooted, 4.1.1 android software with a bit of 4.1.2 in there. Does anyone have an idea how to fix this?
Any help is greatly appreciated.
Mike
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
You cant install an OTA update unless you have the official stock rom and the stock recovery because custom recoveries will install it and I believe im correct when I say that to flash an OTA update you have to odin to stock and then do the update.
There is absolutely no need to go back to stock to take the update. If you head over to freezas stock rooted thread, you can flash the updated firmware there and thats really all you need
Most roms have already updated their bases to MB1 (4.1.2), so I suggest you either wait till your rom is updated or flash an updated rom, you're not missing out on huge changes either way
Most custom touchwiz roms will allow updates, but you have to flash stick recovery 1st. The 157mb update is for mb1. You could just change your build prop to get the notification nag to go away
sent from my GS3 using XDA app
If you're on stock rooted with no apps removed, do what I did. Plug phone into odin, flash stock recovery, update, flash custom after update done, re root, done.
Sent From My Rooted, S-OFF'd Blackberry Curve using the iOS XDA Application for Android.
Just flash a updated rom issue should go away there is a flashable I can't seem to find right now that stops the nag. I think it is a build prop mod.
tazfanatic said:
Just flash a updated rom issue should go away there is a flashable I can't seem to find right now that stops the nag. I think it is a build prop mod.
Click to expand...
Click to collapse
Yup, if you just wanna make it go away, go into your build.prop and change all instances of "LJ7" (or "MA6" ) to "MB1"
CNexus said:
There is absolutely no need to go back to stock to take the update. If you head over to freezas stock rooted thread, you can flash the updated firmware there and thats really all you need
Most roms have already updated their bases to MB1 (4.1.2), so I suggest you either wait till your rom is updated or flash an updated rom, you're not missing out on huge changes either way
Click to expand...
Click to collapse
That's all I do. Once an update comes out I just head over to Freezas page and update my rom. Stock look and feel with the root in place.
Sent from my stock rooted Galaxy S3
Any update on this? I have the same issue.
Thanks
coderaja said:
Any update on this? I have the same issue.
Thanks
Click to expand...
Click to collapse
There's several ways to fix this issue posted on the other page. Use one of them.
D
Hi there guys of XDA,
I have a major problem with my NOTE 2, after playing around with some ROMs, Cyanogenmod 11 4.4 NIGHTLY, 10.2 4.3 and Omni 4.4.1 NIGHTLY. I used CWM to load these ROMs with SUPERsu?. This is the first time i have flashed any ROMs onto my phone.
CM 11 was the first ROM i flashed on my NOTE 2 and that's when it started it couldn't detect my sim, It doesn't show me my IMEI number and my Baseband version. I didn't make a back-up of the stock because i didn't need one.
Now i'm stuck with a phone i can only use on Wifi is there anyone that can help? or if its happened to someone else? how did you sort it out?
Also can i restore this through KIES?
shirazi15 said:
Hi there guys of XDA,
I have a major problem with my NOTE 2, after playing around with some ROMs, Cyanogenmod 11 4.4 NIGHTLY, 10.2 4.3 and Omni 4.4.1 NIGHTLY. I used CWM to load these ROMs with SUPERsu?. This is the first time i have flashed any ROMs onto my phone.
CM 11 was the first ROM i flashed on my NOTE 2 and that's when it started it couldn't detect my sim, It doesn't show me my IMEI number and my Baseband version. I didn't make a back-up of the stock because i didn't need one.
Now i'm stuck with a phone i can only use on Wifi is there anyone that can help? or if its happened to someone else? how did you sort it out?
Also can i restore this through KIES?
Click to expand...
Click to collapse
I had this exact issue last week when flashing Kitkat AOSP ROM. Even restoring back to 4.3.1 no network connection was available, except for WiFi. Restoring your EFS will not even work. You just have to re-root your phone.
Not to worry, your phone is OK, perfectly OK. But just quite a bit of work needs to be done. Here: http://forum.xda-developers.com/showthread.php?t=2032849
1. Download original stock firmware for your country and telco
2. Download mode that firmware back to your phone using Odin
3. Download mode to install recovery, this will re-root your phone above steps will un-root your phone
4. Re-flash ROM of your choice, not Kitkat for now
After all i've gone through, and as much as i want to try Kitkat, i think this issue is recovery-related. Both TWRP and CWM needs updating for Android 4.4. I will wait until then.
All the best!
Gandicela said:
I had this exact issue last week when flashing Kitkat AOSP ROM. Even restoring back to 4.3.1 no network connection was available, except for WiFi. Restoring your EFS will not even work. You just have to re-root your phone.
Not to worry, your phone is OK, perfectly OK. But just quite a bit of work needs to be done. Here: http://forum.xda-developers.com/showthread.php?t=2032849
1. Download original stock firmware for your country and telco
2. Download mode that firmware back to your phone using Odin
3. Download mode to install recovery, this will re-root your phone above steps will un-root your phone
4. Re-flash ROM of your choice, not Kitkat for now
After all i've gone through, and as much as i want to try Kitkat, i think this issue is recovery-related. Both TWRP and CWM needs updating for Android 4.4. I will wait until then.
All the best!
Click to expand...
Click to collapse
Thanx for getting back to me at least someone can help. After i followed the things you told me to do. It didn't put the stock ROM back on there so i'm stuck with omni.
After Odin loaded everything to the phone it just keeps going into recovery mode? is that normal or am i doing it wrong because the link you posted up doesn't mention anything about that :-s and i followed everything that link said to do.
shirazi15 said:
Thanx for getting back to me at least someone can help. After i followed the things you told me to do. It didn't put the stock ROM back on there so i'm stuck with omni.
After Odin loaded everything to the phone it just keeps going into recovery mode? is that normal or am i doing it wrong because the link you posted up doesn't mention anything about that :-s and i followed everything that link said to do.
Click to expand...
Click to collapse
Mate, firstly this is the hard way of recovering from "Unknown Baseband" issue. Finally the simple solution was only to download and install an app called SELinux Mode Changer from PlayStore. Then using that app, change SELinux from Enforcing to Permissive resolved everything related to IMEI, EFS, and Unknown Baseband. So hard way I did; i didn't know any better then.
By the way the link is correct. Start from the procedure from the line that says "Installation Instruction [Mobile odin is now have support for NOTE2]"
You must be in download mode (Vol Down, Home, & Power button all pressed together) to flash the Stock ROM using Odin. But where is your status now? If in recovery, can you re-install a ROM? If u r able to reboot back up to OMNI, just install the SELinux app and u will be good to go.
Cheers!
shirazi15 said:
Hi there guys of XDA,
I have a major problem with my NOTE 2, after playing around with some ROMs, Cyanogenmod 11 4.4 NIGHTLY, 10.2 4.3 and Omni 4.4.1 NIGHTLY. I used CWM to load these ROMs with SUPERsu?. This is the first time i have flashed any ROMs onto my phone.
CM 11 was the first ROM i flashed on my NOTE 2 and that's when it started it couldn't detect my sim, It doesn't show me my IMEI number and my Baseband version. I didn't make a back-up of the stock because i didn't need one.
Now i'm stuck with a phone i can only use on Wifi is there anyone that can help? or if its happened to someone else? how did you sort it out?
Also can i restore this through KIES?
Click to expand...
Click to collapse
can you try what i did? http://forum.xda-developers.com/showthread.php?t=2567862&nocache=1
good luck.
"Just sharing my experience in solving this issue. Hopefully it will help solve those who have similar issues.
I flashed a file which messed up my EFS partition. I had a backup and tried to use the available programs to restore my EFS using my backup. None worked. I even brought it to the samsung store, but they said they would change the motherboard and reprogram, and replacement and service would cost more than half the cost of a new N7105. I purchased the phone in another country. The people who had stores to repair phones gave up on my phone. They also offered to replace the motherboard for US$175.00.
My phone was originally under a DMB2 rom (from Singapore I think). I flashed a DMC3 rom, and used this for five months, until i encountered the problem.
I initially gave up and got a note 3. But i could not believe the phone was junk and people in XDA (as I observed) do not seem to give up.
After two weeks, i found the solution below, which brought my phone to working condition.
1. I flashed the stock rom N7105ZHDMI2_N7105ZZHDMI2_TGY from sammobile.
2. I flashed a pit file using Odin. The pit file is found here:
http://forum.xda-developers.com/show....php?t=2137008
This restored the baseband. But IMEI was no longer NULL. However, it was still 0.
3. I downloaded and used the EFS Pro from this link:
http://forum.xda-developers.com/show....php?t=1308546
Before using EFS Pro, make sure you dial *#7284# and change the setting of Qualcomm USB Settings to
"RMNET + DM + MODEM"
I will not hurt your phone if you do, but EFS Pro will just not work. If you don't do this, the EFS Pro will display "Phone not responding" or something similar.
NOTE: I couldn't find the option with RMNET, but i used the option that also had an "RM*** + DM + MODEM".
After the phone is read, change back the IMEI to what it was originally.
Dial *#7284# again to change back to "MTP+ADB".
It's all working now.
Hope this is able to help someone. Now i have two working versions of Note.
Thanks to the authors of the program i used, and the people who uploaded the files used.
Cheers!
shirazi15 said:
Thanx for getting back to me at least someone can help. After i followed the things you told me to do. It didn't put the stock ROM back on there so i'm stuck with omni.
After Odin loaded everything to the phone it just keeps going into recovery mode? is that normal or am i doing it wrong because the link you posted up doesn't mention anything about that :-s and i followed everything that link said to do.
Click to expand...
Click to collapse
karlonicolas said:
can you try what i did? http://forum.xda-developers.com/showthread.php?t=2567862&nocache=1
good luck.
"Just sharing my experience in solving this issue. Hopefully it will help solve those who have similar issues.
I flashed a file which messed up my EFS partition. I had a backup and tried to use the available programs to restore my EFS using my backup. None worked. I even brought it to the samsung store, but they said they would change the motherboard and reprogram, and replacement and service would cost more than half the cost of a new N7105. I purchased the phone in another country. The people who had stores to repair phones gave up on my phone. They also offered to replace the motherboard for US$175.00.
My phone was originally under a DMB2 rom (from Singapore I think). I flashed a DMC3 rom, and used this for five months, until i encountered the problem.
I initially gave up and got a note 3. But i could not believe the phone was junk and people in XDA (as I observed) do not seem to give up.
After two weeks, i found the solution below, which brought my phone to working condition.
1. I flashed the stock rom N7105ZHDMI2_N7105ZZHDMI2_TGY from sammobile.
2. I flashed a pit file using Odin. The pit file is found here:
http://forum.xda-developers.com/show....php?t=2137008
This restored the baseband. But IMEI was no longer NULL. However, it was still 0.
3. I downloaded and used the EFS Pro from this link:
http://forum.xda-developers.com/show....php?t=1308546
Before using EFS Pro, make sure you dial *#7284# and change the setting of Qualcomm USB Settings to
"RMNET + DM + MODEM"
I will not hurt your phone if you do, but EFS Pro will just not work. If you don't do this, the EFS Pro will display "Phone not responding" or something similar.
NOTE: I couldn't find the option with RMNET, but i used the option that also had an "RM*** + DM + MODEM".
After the phone is read, change back the IMEI to what it was originally.
Dial *#7284# again to change back to "MTP+ADB".
It's all working now.
Hope this is able to help someone. Now i have two working versions of Note.
Thanks to the authors of the program i used, and the people who uploaded the files used.
Cheers!
Click to expand...
Click to collapse
Nice, thanks!
For all others that might face "unknown baseband" with 4.3 to 4.4 flashing of ROMS, SELinux Mode Changer app from Playstore will fix that problem. Install the app and set SELinux from Enforcing to Permissive.
i hope your problem is fixed.
i'm not too familiar with CM roms, as i have been using stock since gingerbread. but you have to first do a full wipe before flashing from CM to stock. did you do that? perhaps you can go to recovery, do a full wipe, include Dalvik and Cache. Then go to bootloader and flash your rom.
by the way, my chipset is qualcomm yours may be exynos. if so, then i'm not confident about this solution because i have tried this several times, but only on note 2 LTE.
good luck!
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
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.