Database Users

[FIX] Cannot make calls or receive them and no sound on I9505

Hi all,
If you change ROM quite often and baseband too, most of the time everything goes smoothly, however, if you choose the wrong combination, you might encounter a very annoying issue: lost of the system sound, no ability of calling nor receiving phone calls.
I finally found a way to make my mobile sound working again (as it should) and I am able to call and receive phone calls as well. No reboots either.
When I started my investigation I had the following on my mobile:
ROM: [AOSP] Official 4.4.2 - S4 Google Edition - Final-R1.1 by jamal2367
Baseband: baseband XXUFNA1
Recovery: TWRP
Let me make the point. It is not because of the above settings that I had problems, but because of a combination of changing ROMs and baseband, probably only baseband.
When I was receiving a phone call only the vibration was working, no sounds, I couldn't slide the screen to answer properly, which means that I was able to slide, but the round icon of the slide could not catch the phone green icon. I could play no sound at all on videos, spotify, alarm, etc.; at the beginning I thought it was the current ROM, then
- I add to install Kies to try to restore the original firmware
- I changed it to another one
- I changed to CyanogenMod (and changed recovery to the default that comes with it: CWM)
- I rolled back to Samsung Stock edition (thank God I made a backup with TWRP months ago, before rooting)
Same damn issue and since I was there, I kept changing baseband with what I thought was the best for that particular (current) ROM. It is easy, you ask Mr. Google and he will tell you or you can try with http://www.sammobile.com/firmwares/2/
How can you fix it?
a. Download I9505XXUEMKF_I9505OXXEMK3_I9505XXUEMKF_HOME.tar.md5 and I9505XXUEMK8_I9505OXAEMK8_I9505XXUEMK8_HOME.tar.md5
b. Untar them in different directories
c. Use Heimdall - http://glassechidna.com.au/heimdall/ to flash all files in I9505XXUEMKF_I9505OXXEMK3_I9505XXUEMKF_HOME
c1. On Heimdal, click on the second tab _flash_, then browse your pit file, click on the button _add_ and choose the right partition. Do this for all the files inside the directory. Inside the _partitions (files)_ window you will have as many items as you have in the directory, in the example I put only 3, but you should have 12 of them in total (see image below)
- Under the partition ID, there is also a label/text that suggest you what file to choose.
- A note, MDM is for the modem, do not use MODEMST1 or MODEMST2
- If you do not have a pit, you can google it or as I did, use the forth tab _Utilities_, detect your device, and save as...under Download PIT.
c2. Then click on start to flash.
d. reboot in recovery and let CWM install unrecognized packages if asked. You might also find some red lines on the top left of the screen, but do not worry too much.
You might also find other red text _unable to unmount this or that_, after pressing start, but do not worry.
I tried to restart my mobile, but I was not able to restart it; in case you can, your stock Samsung ROM still has no sound. So
e. reboot in download and flash NON-HLOS.bin from the other folder I9505XXUEMK8_I9505OXAEMK8_I9505XXUEMK8_HOME. Use Partition Name _APNHLOS_ from partition Details in Heimdall.
f. the sounds is back
g. re-install your favourite recovery back
h. re-install your favourite ROM
I put back TWRP and [AOSP] Official 4.4.2 - S4 Google Edition - Final-R1.1 by jamal2367
Current baseband XXUEMKF. I will leave it as it is for a while, without changing it.
You can use Heimdall on windows too, but in case of driver problems use this to resolve the issue http://zadig.akeo.ie/
LTE and WiFi will work too.
You can get the two folders from this zip file: https://mega.co.nz/#!GARWHLDY!d2hrbCaVMKMLOXdNG6VfgkFMcjZclXJHTxe6amz0TNM
Note:
- When you flashed NON-HLOS.bin it might get the message stuck on _Rebooting device..._ and it does not give the impression that it finished. If you manual reboot and sometimes it means _remove the battery_, it will work.
- At the reboots note how the text on the top left changes during and after flashing.
At the booting now I get a warning text on the top-left (small text), it is something I can cope with or fix it later.
You can read in some posts that if _my phone number_ in unknown, under _status_ then you have problems with phone calls. I always had that one and still have it and it is working, so I wouldn't pay too much attention.
- if you have problems with heimdall, remove Kies (actually you can just remove it directly) and on mac, to remove some dependencies, run
sudo sh -
kextunload -b com.devguru.driver.SamsungComposite
kextunload -b com.devguru.driver.SamsungACMData
kextunload -b com.devguru.driver.SamsungACMControl
the uninstaller seems like it is working ok, so you might not need the above lines.

Or just flash the right non-hlos/wifi fix and that should fix your problem ...if you have a newbootloader just flash any latest non-hlos, but if you are still in oldbootloader feel free to flash a BMH1 non-hlos/wifi fix.. have a nice day.
Sent feom Hell ?

haven't really understood Step c1 Please @racoonlab

I cant find The pit File

Hi m_beek,
m_beek said:
I cant find The pit File
Click to expand...
Click to collapse
Have you tried the 4th tab of heimdall, utilities?
a. detect
b. save as
c. download
If you do not detect it, use the Zadig drivers first.
You can also try to have a look at http://forum.xda-developers.com/showthread.php?t=999097

What about getting "ERROR: Claiming interface failed!" after Clicking Start ?

m_beek said:
What about getting "ERROR: Claiming interface failed!" after Clicking Start ?
Click to expand...
Click to collapse
Do you have the Kies software installed? If yes, uninstall it and see also the last few lines of my post, to remove potential dependencies.
EDIT
Restart your machine too after the uninstall
R

Since I'm on W8 , I have never Installed Kies

m_beek said:
Since I'm on W8 , I have never Installed Kies
Click to expand...
Click to collapse
i. did you manage to get the pit?
ii when did you get that message, when flashing?
R

I couldn't get my Pit from _Utilities_ because of that, So I Googled "GT I9505 Pit" and download a Pit file, The After Managing Pit and Start flashing That What it's sayed
"This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
ERROR: Claiming interface failed!"

m_beek said:
I couldn't get my Pit from _Utilities_ because of that, So I Googled "GT I9505 Pit" and download a Pit file, The After Managing Pit and Start flashing That What it's sayed
"This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
ERROR: Claiming interface failed!"
Click to expand...
Click to collapse
Have you tried the Zadig drivers? To me it helped to:
- start the program
- see the list of the usb in used
- while the program was showing me the list, I unplugged the cable from one usb and attached to another one.
- run the program.
R

racoonlab said:
i. did you manage to get the pit?
ii when did you get that message, when flashing?
R
Click to expand...
Click to collapse
Ps. Odin Works, Can I Flash it with Odin ?

m_beek said:
Ps. Odin Works, Can I Flash it with Odin ?
Click to expand...
Click to collapse
probably with the latest yes.
http://www.xda-developers.com/android/mobile-odin-updated-to-version-4-new-features-and-devices/

racoonlab said:
probably with the latest yes.
http://www.xda-developers.com/android/mobile-odin-updated-to-version-4-new-features-and-devices/
Click to expand...
Click to collapse
Finally works
Ps. Its normal to get "Invalid Percent of Drawing progress Bar1"

Repulsa said:
Or just flash the right non-hlos/wifi fix and that should fix your problem ...if you have a newbootloader just flash any latest non-hlos, but if you are still in oldbootloader feel free to flash a BMH1 non-hlos/wifi fix.. have a nice day.
Sent feom Hell
Click to expand...
Click to collapse
Currently I have this one instaled I9505VJUHOK1. It was working fine with the stock ROM from SamMobile (http://www.sammobile.com/firmwares/download/61139/I9505VJUHOK1_I9505ZTOHOK1_ZTO/).
There is no sound at all on calls when using CM13.
What would you recommend?

[Q] Hemidall cannot read PIT file

Hi,
I updated my galaxy note 3 from 4.3 to 4.4.2 (both stock) using heimdall and that went without a hitch, I forgot to wipe all my data so ended up flashing 4.4.2 on top of 4.3 but it works fine with the only difference I see is that my battery leak problem got worse.
I then wanted to install CWM in order to eventually install a custom rom but that got cut short when heimdall (both GUI and on terminal) failed to read my PIT file.
Please note that the phone works and I can go into download mode without a problem and heimdall detects the device but once it starts downloading the PIT i get this:
[email protected]$ heimdall download-pit --output pit4.4.pit
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
I am not sure how to proceed, my device is unusable with the horrible battery leak right now.
Thanks

Got this issue too: looks like heimdall can't handle device running 4.4.2. Solution for you is to find Windows PC and use Odin.

back to odin i suppose
ivzave said:
Got this issue too: looks like heimdall can't handle device running 4.4.2. Solution for you is to find Windows PC and use Odin.
Click to expand...
Click to collapse
thanks for the heads up! I got my hands on a windows pc and used odin to reflash 4.4.2 and then flashed CWM with odin as well. all went well but its a bit concerning that heimdall does not support 4.4.2

OMG this sucks I don't have a windows PC
:0(

[Q] Downloading Pit file with heimdall Galaxy S5

Hi im am using a mac osx 10.9.4 and running the program heimdall. i am trying to download my pit file off of my Samsung Galaxy S5 but i keep getting this error
nitialising connection...
Detecting device...
Claiming interface...
Setting up interface...
InitialisinERROR: Protocol initialisation failed!
Releasing device interface...
Help!!

Luca518 said:
Hi im am using a mac osx 10.9.4 and running the program heimdall. i am trying to download my pit file off of my Samsung Galaxy S5 but i keep getting this error
nitialising connection...
Detecting device...
Claiming interface...
Setting up interface...
InitialisinERROR: Protocol initialisation failed!
Releasing device interface...
Help!!
Click to expand...
Click to collapse
Is your phone root? If so, you can extract the Pit file directly right on your phone.

vndnguyen said:
Is your phone root? If so, you can extract the Pit file directly right on your phone.
Click to expand...
Click to collapse
No its not i need the pit file to flash it back to a earlier version so i can root it

..

fffft said:
You didn't give us enough context to discern the nature of your problem. But at a guess it's a Mac configuration issue.
In any event, you need to give us a lot more information. Or root your phone and extract your PIT file directly. Or perhaps find it in the forums here - again impossible to say as you gave us no particulars as to what S5 model you have, your carrier or anything else.
http://forum.xda-developers.com/showthread.php?t=2737448
.
Click to expand...
Click to collapse
I have a Galaxy S5 Verizon 9000v model

..

I have this same problem. I can't root my s5 because I dont have windows in PC. Why? I wana use JOdin but we dont have any pit file working with it. I wana use heimdall but it doesn't work with S5. So...
Somebody find working Method of root S5 without windows OS.?

fffft said:
That still isn't nearly enough information. To start, there is no 9000v model. But assuming that you really meant a sm-g900v model. Yes details do matter there is a 9006v model as well and other very similar model numbers. And further assuming that your phone is a 16 GB, then the PIT file you need has long been posted in this forum. Look in my post history or do a search.
Cheers
.
Click to expand...
Click to collapse
yes i do have a sm-g900v model sorry i wasn't clear i will check your post history thanks for your help

..

Luca518 said:
Hi im am using a mac osx 10.9.4 and running the program heimdall. i am trying to download my pit file off of my Samsung Galaxy S5 but i keep getting this error
nitialising connection...
Detecting device...
Claiming interface...
Setting up interface...
InitialisinERROR: Protocol initialisation failed!
Releasing device interface...
Help!!
Click to expand...
Click to collapse
most likely related to this problem:
https://github.com/Benjamin-Dobell/Heimdall/pull/225
https://github.com/Benjamin-Dobell/Heimdall/issues/209

Can't Install CWM with Heimdall

I recently got a Samsung Galaxy S5 (SM-G900T) and rooted it with Towelroot. I also wanted to remove a bunch of the bloatware that came with it, but before doing that I wanted to back it up. On my old phone, I had CWM for backups and restores, and installing it was trivial. Not so on this phone, apparently. From the tutorials I've been reading, it seems like I need Odin or Heimdall to install it. I'm using Heimdall because I have Linux. After downloading the image required for my phone model, I attempted to install it according to the directions I found. Instead, I got a bunch of errors:
Code:
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
Re-attaching kernel driver...
I have no idea what a PIT file is, and I don't know why it can't download it, but apparently this is an issue that a lot of Heimdall users are having. Any suggestions on how I can fix this? Will I have to wait until Heimdall gets upgraded?

fajrero said:
I recently got a Samsung Galaxy S5 (SM-G900T) and rooted it with Towelroot. I also wanted to remove a bunch of the bloatware that came with it, but before doing that I wanted to back it up. On my old phone, I had CWM for backups and restores, and installing it was trivial. Not so on this phone, apparently. From the tutorials I've been reading, it seems like I need Odin or Heimdall to install it. I'm using Heimdall because I have Linux. After downloading the image required for my phone model, I attempted to install it according to the directions I found. Instead, I got a bunch of errors:
Code:
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
ERROR: Failed to send request to end PIT file transfer!
ERROR: Failed to download PIT file!
Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...
Re-attaching kernel driver...
I have no idea what a PIT file is, and I don't know why it can't download it, but apparently this is an issue that a lot of Heimdall users are having. Any suggestions on how I can fix this? Will I have to wait until Heimdall gets upgraded?
Click to expand...
Click to collapse
Check the github, theres some forks you can try, i have a thread about this you can check.
Sent from my SM-G900A using Tapatalk

Rakuu said:
Check the github, theres some forks you can try, i have a thread about this you can check.
Sent from my SM-G900A using Tapatalk
Click to expand...
Click to collapse
Where's the thread? I'm a bit worried about trying to use beta software to install recovery. What happens if recovery gets corrupted or something?

fajrero said:
Where's the thread? I'm a bit worried about trying to use beta software to install recovery. What happens if recovery gets corrupted or something?
Click to expand...
Click to collapse
EDIT: I appologize, i didnt reread my reply, heres the link to thread i waa referring to http://forum.xda-developers.com/galaxy-s5/help/unofficial-linux-support-thread-t2832106
Sent from my SM-G900A using Tapatalk

I downloaded Rom Manager from the Google Store, and it says that it can install CWM Recovery for me. Is there any benefit to using Heimdall instead of Rom Manager?

fajrero said:
I downloaded Rom Manager from the Google Store, and it says that it can install CWM Recovery for me. Is there any benefit to using Heimdall instead of Rom Manager?
Click to expand...
Click to collapse
Not sure honestly. Seeing as heimdall is an odin port, if you brick, heimdall is really your only option to fix it unless you can get to a windows computer. I personally am not sure about how compatible that app is since i have a locked bootloader and dont really mess with any of that, give it a shot though if you feel like it and let us know what happens for future refrence.
Sent from my SM-G900A using Tapatalk

Rakuu said:
Not sure honestly. Seeing as heimdall is an odin port, if you brick, heimdall is really your only option to fix it unless you can get to a windows computer. I personally am not sure about how compatible that app is since i have a locked bootloader and dont really mess with any of that, give it a shot though if you feel like it and let us know what happens for future refrence.
Sent from my SM-G900A using Tapatalk
Click to expand...
Click to collapse
When you go to install CWM with Rom Manager, you first have to pick your phone model out of a list of supported devices. GS5 is not one of them, so I'm thinking I run the risk of bricking it this way. This is probably why whenever I search for ways to install CWM on GS5, Odin or Heimdall is recommended, not Rom Manager.
However, TWRP also has an installer available, and GS5 is supported. I don't have any experience with TWRP, though. I guess my best options are to either try to wrestle with Heimdall some more or install TWRP.

fajrero said:
When you go to install CWM with Rom Manager, you first have to pick your phone model out of a list of supported devices. GS5 is not one of them, so I'm thinking I run the risk of bricking it this way. This is probably why whenever I search for ways to install CWM on GS5, Odin or Heimdall is recommended, not Rom Manager.
However, TWRP also has an installer available, and GS5 is supported. I don't have any experience with TWRP, though. I guess my best options are to either try to wrestle with Heimdall some more or install TWRP.
Click to expand...
Click to collapse
Same as my last post, havent used it so i wouldnt know. Also if you do softbrick youll need to get heimdall working or find a windows computer, which honestly, you can beat around the bush sith apps and stuff but at the end of the day i think youll need to use heimdall or odin.
Sent from my SM-G900A using Tapatalk

I went through the TWRP installation with the installer from the Play store, installing the latest version of TWRP. Just as it got to the step for the actual installation, it crashed...
So, I try to reboot into recovery, and I'm greeted by these words: "RECOVERY IS NOT SEANDROID ENFORCING. Set Warranty Bit: recovery". My heart sinks, but then I see the Team Win splashscreen come up, and I'm in TWRP. I tap the Reboot button, and it boots back into Android. Everything seems to be fine, aside from the crash during installation and this mysterious error.
I'd like to install Cyanogen, but I prefer deciphering this error first. From what I've been reading, most of the people getting this error have bricked their phones. Maybe I just got lucky? What is this error, and should I worry about it?

[Q] Galaxy S4 - Heimdall gets stuck at "Initialising protocol..."

Hi
Phone: Samsung Galaxy GT-i9500 (International). Currently sitting on stock everything.
Years ago, I was able to successfully flash my Galaxy S2 with Cyanogenmod. I really don't know what else to try now with this S4.
Please bear with me. I know this question has been asked before but I've tried all the solutions that have been posted and I've also spent a lot of time trying other methods of rooting my phone with no success.
I started off following the instructions on wiki.cyanogenmod.org/w/Install_CM_for_i9500 to install Cyanogenmod. I have also tried other instructions for using ODIN.
Things that have been posted as solutions that I've tried:
Plugging the phone in the back USB ports instead of front USB
Plugging the phone into different USB ports
Using a different USB cable
Both Heimdall 1.4RC2 and 1.4.0-win32
Tried the various combinations of upper/lowercase --recovery --RECOVERY etc
WinUSB, libusb0 and libusbk drivers provided by Heimdall's zadig.exe
Using Odin3 v1.85
Using Odin3 v3.07
Tried KingoApp
When I tried using KingoApp it sat for about half an hour running through various exploits and not succeeding. Then eventually it said that the final thing it could try was to reboot into Download mode. I let it do that and the phone got stuck in exactly the same place that Heimdall and ODIN gets stuck. Namely the screen shows the following but no blue bar ever appears or fills up:
ODIN MODE
PRODUCT NAME: GT-I9500
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX WARRANTY VOID: 0
RP SWREV: A3
Downloading...
Do not turn off target!!
Click to expand...
Click to collapse
cygwin md5 check said:
$ md5sum recovery.img
4fbc482479f4d91c619be8dbb79cdb84 *recovery.img
Click to expand...
Click to collapse
cmd log said:
C:\Temp\FLASHING\Heimdall-Suite-1.4.0-win32>heimdall.exe version
v1.4.0
C:\Temp\FLASHING\Heimdall-Suite-1.4.0-win32>heimdall flash --RECOVERY recovery.img --no-reboot
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
--urlsnip--
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
--urlsnip--
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Click to expand...
Click to collapse
I really don't know what else to try at this point. Can someone please give some suggestions or point in me in the right direction?

Hi
Thanks for writing to us at XDA assist. Please standby while we have your thread/question moved to the appropriate sub-forum for your device.
For future reference you can find your device sub-forum here (bookmark/subscribe this):
http://forum.xda-developers.com/galaxy-s4
Within that section you will find a dedicated q&a sub-forum (this is where your thread is going to be moved to):
http://forum.xda-developers.com/galaxy-s4/help
Good luck!

So what are you trying to do? Flash a recovery?
I see you are running Windows. Just use Odin for it or you can even use jOdin3 (web Odin).
https://builds.casual-dev.com/jodin3/
You don't need Kingoroot. It doesnt even work anymore anyway.

Lennyz1988 said:
So what are you trying to do? Flash a recovery?
I see you are running Windows. Just use Odin for it or you can even use jOdin3 (web Odin).
You don't need Kingoroot. It doesnt even work anymore anyway.
Click to expand...
Click to collapse
Yeah I'm trying to flash Clockworkmod Recovery so that I can then install Cyanogenmod. So far every attempt to load CWM has failed because the process in download mode never begins.
I have tried Odin and it had the same problem as Heimdall. I previously used Heimdall to flash Cyanogenmod onto my Galaxy S2, which is why I tried it again for the S4. When that didn't work I tried Odin.

Nobody Hates Firemen said:
Yeah I'm trying to flash Clockworkmod Recovery so that I can then install Cyanogenmod. So far every attempt to load CWM has failed because the process in download mode never begins.
I have tried Odin and it had the same problem as Heimdall. I previously used Heimdall to flash Cyanogenmod onto my Galaxy S2, which is why I tried it again for the S4. When that didn't work I tried Odin.
Click to expand...
Click to collapse
Odin should work though.

Lennyz1988 said:
Odin should work though.
Click to expand...
Click to collapse
It doesn't though. I don't get any error message which makes this very difficult to investigate. It just doesn't start transferring the recovery.
I just tried using towelroot v3 and got a message, "This phone isn't currently supported" - even though Galaxy S4 is supposedly supported. I wonder if I have some weird variant model.
It says the following in the about screen:
Model number: GT-I9500
Android version: 4.4.2
Baseband version: I9500XXUGNF6
Kernel version: 3.4.5-2434847 / [email protected] #1 / Wed Aug 6 16:24:19 KST 2014
Build number: KOT49H.I9500XXUGNH2
SE for Android status: Enforcing / SEPF_GT-I9500_4.4.2_0024 / Wed Aug 6 16:24:19 KST 2014

You are trying outdated root methods. The only root method that will work is cf-root, though you need to flash it. Are you running a virtual machine or something?
You should delete every driver related to the s4 from your pc and try from scratch.

Lennyz1988 said:
You are trying outdated root methods. The only root method that will work is cf-root, though you need to flash it. Are you running a virtual machine or something?
You should delete every driver related to the s4 from your pc and try from scratch.
Click to expand...
Click to collapse
CF-root worked, thank you! Used the one at download.chainfire.eu/326/CF-Root1/CF-Auto-Root-ja3g-ja3gxx-gti9500.zip?retrieve_file=1
I'm not running VM or anything. It frikken sucks that the instructions on Cyanogenmod aren't up to date And also sucks that every other site I went to with instructions doesn't mention that they're outdated root methods. The price of being a noob...
Thanks for showing me the way.