OK, clearly I missed something when I did all my reading. I've got an SM-N9005, LTE, 32GB.
I downloaded an XSA ROM from Sammobile, N9005XXUBMI7_N9005XSABMI1_XSA.zip then unpacked it and ran Odin to flash it. My plan was to have an AU ROM before I tried RDLV root process.
Instead I got an Odin error on system.img.ext4 followed by the error screen. (phone - yellow exclamation - PC. The list there says:
Current Binary: Samsung Official
System Status: Official
Reactivation Lock: Off
Knox Kernal: 0x0
Knox Warranty Void: 0x0
Qualcomm Secure Boot: Enable
RP SWREV:S1, T1, R1, A1, P1
Write Protection: Enable
Nothing I have been able to do since then has helped. Even tried DL'ing Heimdall but it uses tar.gz packages and I don't have one. I downloaded Kies3 and it tells me my phone is not supported by v3. Clicking Confirm doesn't help nor does the 'Checking' link. The other Kies give a connection error and the Troubleshoot Connection option doesn't help.
The only thing I can think I might have got wrong is trying to install an Aussie package over a TGY (Hong Kong) system, but there are plenty of comments saying that is OK.
I found a PIT file that is supposed to be OK, (CSB_signed_HLTE_EUR_OPEN_32G_0718) but I am not sure a pit is the answer, and if that was the cause, I think I'd need a PIT to match my ROM... right?
By preference I'd like to keep under the level where I trip Knox, but if I have to use a Recovery or CF-Root to get my phone working I'll do it.
Any advice please? Also, any ideas on what went wrong?
With some difficulty in downloading (I have a PC problem where it just seizes up for no traceable reason - going back to shop as soon as I can get it to Melb) with it taking 4 times to DL, and after some dismay that XDA'ers hadn't responded to my problem (how dare you lot sleep when my phone isn't working! :laugh I tried the Hong Kong version this morning and it ran beautifully. :victory: Not only that, my phone set up is intact.
So, what did I just learn?
Was it that, on an unrooted phone you cannot flash a stock from a different country?
Is it that HK ROM's are just different?
Or was it that some ROM's, even from Sammobile, don't run?
I am fairly sure it wasn't just a corrupt DL; IIRC Odin checks the MD5 number before flashing - pretty sure I saw that in a thread while I was trying to work out what had gone wrong. And my PC problem didn't happen when I was DL'ing the XSA version.
On a brighter note, I have my RDLV setup mostly ready to go. RDLV was going to be the next thing I tried to fix the problem so I have CYGWIN and the files all set up. Better not tell the missus I am about to do it - she's already upset enough with me for bricking my brand new phone. :laugh:
I'd like some advice if you don't mind. In the future I may have to unroot my phone, either for warranty purposes or to sell it. I'd like to be able to put the XSA stock version on it at that point. I'm presuming I could run it over a rooted phone (& lose root) to produce an Aussie phone? But was it reasonable to expect the XSA version to run on my phone while it was not rooted?
Journyman16 said:
With some difficulty in downloading (I have a PC problem where it just seizes up for no traceable reason - going back to shop as soon as I can get it to Melb) with it taking 4 times to DL, and after some dismay that XDA'ers hadn't responded to my problem (how dare you lot sleep when my phone isn't working! :laugh I tried the Hong Kong version this morning and it ran beautifully. :victory: Not only that, my phone set up is intact.
So, what did I just learn?
Was it that, on an unrooted phone you cannot flash a stock from a different country?
Is it that HK ROM's are just different?
Or was it that some ROM's, even from Sammobile, don't run?
I am fairly sure it wasn't just a corrupt DL; IIRC Odin checks the MD5 number before flashing - pretty sure I saw that in a thread while I was trying to work out what had gone wrong. And my PC problem didn't happen when I was DL'ing the XSA version.
On a brighter note, I have my RDLV setup mostly ready to go. RDLV was going to be the next thing I tried to fix the problem so I have CYGWIN and the files all set up. Better not tell the missus I am about to do it - she's already upset enough with me for bricking my brand new phone. :laugh:
I'd like some advice if you don't mind. In the future I may have to unroot my phone, either for warranty purposes or to sell it. I'd like to be able to put the XSA stock version on it at that point. I'm presuming I could run it over a rooted phone (& lose root) to produce an Aussie phone? But was it reasonable to expect the XSA version to run on my phone while it was not rooted?
Click to expand...
Click to collapse
1st step, exit Kies... It will stuff up an ODIN flash...
2nd, what was the original rom on the HK phone? If it's MJ3 or above it had the new bootloader on it that won't allow you to go back to an earlier version...
ultramag69 said:
1st step, exit Kies... It will stuff up an ODIN flash...
2nd, what was the original rom on the HK phone? If it's MJ3 or above it had the new bootloader on it that won't allow you to go back to an earlier version...
Click to expand...
Click to collapse
I may have written it wrong but I wasn't running Kies and Odin at the same time; they were alternative ways to try to get things going.
MI7 was the original and also the one I used to finally get things working again. Then I figured I'd try the RDLV process but still had issues with files - I posted all that on the RDLV thread.
Currently I am all working but unrooted, Knox = )x) and I am waiting for an updated HK version to DL.
I eventually got root on my Note. Had to DL the same country version of an update (MK1) and run RDLV process on that, then it all worked flawlessly. I'm still puzzled as to why I couldn't do the equivalent on an Aussie ROM version and use that. Only thing I can think of is the partition size is different for Hong Kong versions so it give the errors as you try to flash a different version.
Annoying but it doesn't appear to have happened to others - maybe they are content to use ROMs from the country their CSC is set to?
Related
I'm looking for a download of an older ROM. I want to try the RDLV root method but I want my original (or close to it) ROM ready in case of problems. Sammobile seems to only have MJ7 or thereabouts. Unless there's an older ROM link I am missing?
I am currently on MI7 and in download mode it's a TGY (Hong Kong) CSC. Ideally I'd like Australian or UK CSC and MI7 or less ROM.
Then I can try the root method and if I have a problem I am not reduced to using a ROM that will prevent me from trying again unless I want to break Knox.
As a side issue, when going into DL mode, I get the android bot, then a smaller one, on its back with a red exclamation above the open chest. Is that a usual picture or is it indicating something wrong?
NVM on the older ROM issue - I was looking at a post by brangalm re rooting and s/he mentioned entering the CSC in the search box. (I had tried puting in SM-N9005. I also found an older XSA version.
But I am still curious as to the sick android/exclamation mark in Download.
it's normal, it's recovery mode after all, normally used to upload firmware when things go belly up, wipe cache when it doesn't work right etc.
I'm not even sure it was intended for user access, more likely service centers.
Well things went belly up and that mode isn't there anymore. All I get now is the error screen - phone -- yellow exclamation -- PC picture. And Odin will not go past a system.img.ext4 error.
I've made a bit of a mess and I need help please. My s4 is softbricked, but as softbricks go, it's rather hard.
I have an early S4 i9505 bought from Carphone Warehouse (UK, unlocked, pre knox). I rooted it, installed TBackup, greenify and got it how I wanted it. Then I downloaded a stock firmware from Sammobile and tested to see if I could get it back to 'warranty' condition, which was a success.
Confident that I could obtain warranty if I needed it, I re-rooted it, installed TB and greenify, and it ran sweetly for months from that point onwards.
I read about the arrival of updates (and knox) and concluded I didn't need them. It was working, leave it alone.
Then out of the blue, my nice stable machine broke. I didn't change anything I was aware of to cause it.
No normal boot.
No recovery.
Download only.
Using Odin, I tried allsorts, eventually getting the same Sammobile firmware to run.
2 days later, it broke again, same as before, but worse!?
Then I tried all sorts of stuff downloading no end of things trying to get it to boot or even go into recovery. The most promising approach was to reload the firmware along with a .pit file, but still no joy. I've lost track of the other things I tried, but I've been doing it for a week, so a lot has been done. In desperation, I even tried downloading the latest firmware, so I now have signs of knox of the odin page.
I now have the following symptoms:
Booting into recovery brings up the blue 'booting recovery' message then just blackness.
Normal boot is exactly the same as above.
Unpowered conection to my laptop gives a 5 second boot loop featuring the buzz only.
I can reliably boot into download and download stuff with Odin and change the little Odin page status messages. After (foolishly) trying the latest firmware, these messages say
ODIN MODE
PRODUCT NAME GT-I9505
CURRENT BINARY Samsung Official
SYSTEM STATUS Official
KNOX KERNEL LOCK 0x0
KNOX WARRANTY VOID 0x0
CSB-CONFIG-LSB 0x30
WRITE PROTECTION: enable
eMMC BURST MODE enabled
Please can anyone give me some advice on what else I could try?
Thanks
Steve
Wrinklespots said:
ODIN MODE
PRODUCT NAME GT-I9505
CURRENT BINARY Samsung Official
SYSTEM STATUS Official
KNOX KERNEL LOCK 0x0
KNOX WARRANTY VOID 0x0
CSB-CONFIG-LSB 0x30
WRITE PROTECTION: enable
eMMC BURST MODE enabled
Please can anyone give me some advice on what else I could try?
Thanks
Steve
Click to expand...
Click to collapse
If anything else is not working (especially, if you're unable to go to recovery) I'd call sammy service center. Your download mode says that you did not rooted your phone, and knox is untouched either.
spamtrash said:
If anything else is not working (especially, if you're unable to go to recovery) I'd call sammy service center. Your download mode says that you did not rooted your phone, and knox is untouched either.
Click to expand...
Click to collapse
Thanks for looking spamtrash.
I was wondering if I could get away with that. It does look good from the Odin display, but the flash counter must have a pretty high number in it by now! Won't that show up somewhere?
Do you think it does actually have a fault on it, rather than just some software that's messed up and needs tweaking?
Thanks
Steve
Wrinklespots said:
Thanks for looking spamtrash.
I was wondering if I could get away with that. It does look good from the Odin display, but the flash counter must have a pretty high number in it by now! Won't that show up somewhere?
Do you think it does actually have a fault on it, rather than just some software that's messed up and needs tweaking?
Thanks
Steve
Click to expand...
Click to collapse
1. Are you able to go to recovery mode?
2. Assuming that your previous communicates were taken from the screen in download mode - you're clean.
If answer for 1 is: NO, and assuming 2: do not bother the flash counter. Flash counter does not means you messed with custom ROMs, it just means amount of the ROM update tries. As they are unable to prove that the counter was not increased by failed KIES updates, you're safe.
To go deeper, service will have to flash and wipe your phone.
One thing: remove your sd card prior to giving/sending it out.
Try a different usb cable.I was in same boat as you (after stupidly thinking mobile odin pro liked modems).
Luckily I had an unused cable off my tab 3.
I rooted my phone two weeks ago with towelroot and disabled Knox with supersu.Note: my device status said official I'm still running stock firmware. Have to send my phone back for warranty problem so I unrooted with supersu and reset my phone. So now when I look at my device status it says custom (never flashed any roms or nothing) so I factory reset and notice unlock padlock and custom on my reboot startup screen. I also put phone in Odin mode the binary still said Samsung official but now the other say custom. And Knox says 0×0. I was told to use Odin so I installed odin3v3.09, drivers, stock firmware on the PC tried to flash it but got a Auth: Fail in the left lower box.
My replacement phone will be here today and will send the old back Monday to give me a couple more days to figure this out. What did I do wrong?
PLEASE HELP!
UPDATE
I just notice when I was using Odin I tried to flash G900AUCU1ANCE stock firmware. My phone says I'm running G900AUCU2AND3. I wonder if that's why I've been getting that auth: Fail
Where can I get the G900AUCU2AND3 stock firmware from?
Try going to the sammobile website (cant post link because I'm a new member). It should be there
Sent from my SM-G900F using XDA Premium 4 mobile app
tmadekush said:
I just notice when I was using Odin I tried to flash G900AUCU1ANCE stock firmware. My phone says I'm running G900AUCU2AND3. I wonder if that's why I've been getting that auth: Fail
Where can I get the G900AUCU2AND3 stock firmware from?
Click to expand...
Click to collapse
Your warranty should be honoured because it still shows Knox 0x0. But it would be prudent to resolve the custom message as you are trying to do. It's showing custom because you disabled Knox. Flashing a full stock firmware should restore Knox and resolve the custom message.
Odin flashes can fail for many reasons e.g. trying to flash non-Odin versions of firmware, bad signatures, poor quality USB cables, wrong firmware version e.g. one meant for a different phone, et cetera.
Back up your files, then do a full system reset from the settings menu. Then put your phone into download mode and use Odin to flash a full stock firmware. Ideally use the latest firmware version for carrier that the phone originally came from (i.e. it should match the baseband). Google will find many firmware repositories e.g. sammobile, samsung-updates and this site.
.
hi i was updating my phone from cm11 m8 to m9 when things went bad e.g. F.C. and there was no way around it so i formatted eveything via cwm (i mean everything) i normally do this when flashing and i flashed EE 4.4.2 NC4 stock firmware which first failed but installed 2nd time. then i tried my root file which again failed and passed 2nd time. last i tried flashing my standard cwm which kept failing so when i powered up my phone and it keeps saying no os installed. odin has always flashed first time round for me but today i dunno what happened. i've been flashing phones for years and i just dont know what i have done wrong today. i have tried odin 3.09, 1.87. tried flashing with pit file and two difernet usb cables. xda fourms seems like theres no soloution or thye links in the threads are removed. cant get into recovery only download mode. atm im on another pc downloading another firmware which is going to take 2.3 hours which is mental. (free registered)
on odin it says "complete write failed"
and in download mode on left corner says "
ODIN MODE,
PRODUCT NAME - GT I9505
CURRENT BINARY CUSTOM
SYSTEM STATUS CUSTOM
KNOX KERNERL LOCK 0X0
KNOX WARRANTY VOID 0X1
CSB-CONFIG-LSB 0X30
write protection enable
eMMc BURST enabled
tried keys which failed me ( no suprise there anyway)
please please is there anyone outthere to help me or atleast give me a link where i can download btu 4.4.2 firmware for free. many thanks
189cutter said:
hi i was updating my phone from cm11 m8 to m9 when things went bad e.g. F.C. and there was no way around it so i formatted eveything via cwm (i mean everything) i normally do this when flashing and i flashed EE 4.4.2 NC4 stock firmware which first failed but installed 2nd time. then i tried my root file which again failed and passed 2nd time. last i tried flashing my standard cwm which kept failing so when i powered up my phone and it keeps saying no os installed. odin has always flashed first time round for me but today i dunno what happened. i've been flashing phones for years and i just dont know what i have done wrong today. i have tried odin 3.09, 1.87. tried flashing with pit file and two difernet usb cables. xda fourms seems like theres no soloution or thye links in the threads are removed. cant get into recovery only download mode. atm im on another pc downloading another firmware which is going to take 2.3 hours which is mental. (free registered)
on odin it says "complete write failed"
and in download mode on left corner says "
ODIN MODE,
PRODUCT NAME - GT I9505
CURRENT BINARY CUSTOM
SYSTEM STATUS CUSTOM
KNOX KERNERL LOCK 0X0
KNOX WARRANTY VOID 0X1
CSB-CONFIG-LSB 0X30
write protection enable
eMMc BURST enabled
tried keys which failed me ( no suprise there anyway)
please please is there anyone outthere to help me or atleast give me a link where i can download btu 4.4.2 firmware for free. many thanks
Click to expand...
Click to collapse
Hi mate ,
For the firmware go here:
http://www.sammobile.com/firmwares/
in case you softbricked the phone:
http://forum.xda-developers.com/showthread.php?t=2265477
ive read that link before and thats like a newbie guide but i did try but no luck. the problem i think is at the end of flashing odin it says complete (write) failed. im guessing the transferring files are not sticking on the phone thus installion isnt possible. ive tried 2 different pit files for gt i9505 and its still not working. im running out f ideas and really dont want to spend 200-300 pounds on a new phone. i have tried 3 differnt firmware one ee and two btu ones but same problem
yes yes! i done it. simple or maybe pure luck...i re installed usb driver and flashed btu and pit file and vola!!. thaks for your help btw
189cutter said:
yes yes! i done it. simple or maybe pure luck...i re installed usb driver and flashed btu and pit file and vola!!. thaks for your help btw
Click to expand...
Click to collapse
Great man!!
Glad you did it.
First off thanks for this forum and its plethora off information.
My problem:
1. Bought a brand new GT-I9505.
2. Installed cm-12.1-20151117-SNAPSHOT-YOG7DAO1JN-jfltexx with this guide (https://wiki.cyanogenmod.org/w/Install_CM_for_jfltexx)
3. Everything went smooth but the next day starting to get "Sim Card Removed" errors
4. Search the internets and saw that it was a know problem to some batches of S4 phones (https://www.google.nl/search?q=sams....69i57j0l5.15789j0j7&sourceid=chrome&ie=UTF-8)
5. Called customer support of where I bought the phone. Told me I could return it because of the Dead On Arrival support that they give for these cases.
6. Tried to reset to stock but that didn't work because, as I came to discover, knox Warranty Void got triggered to 0x1.
7. Did a factory reset with CM and send the phone back to the company.
8. They sent the phone back to me saying they could not remove CM and that they wanted me to reinstall the OS which came with the phone.
From my past knowledge (installing CM on a galaxy S2) I remembered that my warranty ony would be voided when I would root my device.
I felt supported in that assumption by the text on the install page for my phone which stated:
"The preferred method of installing a custom recovery is through this boot mode. Rooting the stock firmware is neither recommended nor necessary"
So I thought I was doing the installation correctly in terms of warranty voiding.
Clearly that assumption was false because meanwhile Knox got implemented and I should have read upfront before installing CM obviously on my new phone. My bad.
However I am now in a stiuation where I have bought a phone with a hardware defect (Sim card is randomly not being detected) but I cannot return it because Samsung has set a flag which cannot be reset (http://omegadroid.co/wanted-knox-void-warranty-0x1/).
I have read some posts (e.g. http://forum.xda-developers.com/showthread.php?t=2568450) about that it is possible to return to stock but either the posts are relatively old or they are about other devices and/or Android versions.
So I am confused about what my options are at the moment and before I go into the process of trying to bring back my phone to stock I wanted to ask help from some better informed people about this situation.
My questions are:
1. Can I go back to stock firmware from CM 12.1 while knox got triggered.
2. If so, do I need to root my phone?
3. If succeeded is there a way to hide the Warranty Void message while booting. I am talking about hiding here and not removing/resetting the flasg to 0x0 as that is not possible.
Thanks in advance,
Undersound
undersound said:
First off thanks for this forum and its plethora off information.
My problem:
1. Bought a brand new GT-I9505.
2. Installed cm-12.1-20151117-SNAPSHOT-YOG7DAO1JN-jfltexx with this guide (https://wiki.cyanogenmod.org/w/Install_CM_for_jfltexx)
3. Everything went smooth but the next day starting to get "Sim Card Removed" errors
4. Search the internets and saw that it was a know problem to some batches of S4 phones (https://www.google.nl/search?q=sams....69i57j0l5.15789j0j7&sourceid=chrome&ie=UTF-8)
5. Called customer support of where I bought the phone. Told me I could return it because of the Dead On Arrival support that they give for these cases.
6. Tried to reset to stock but that didn't work because, as I came to discover, knox Warranty Void got triggered to 0x1.
7. Did a factory reset with CM and send the phone back to the company.
8. They sent the phone back to me saying they could not remove CM and that they wanted me to reinstall the OS which came with the phone.
From my past knowledge (installing CM on a galaxy S2) I remembered that my warranty ony would be voided when I would root my device.
I felt supported in that assumption by the text on the install page for my phone which stated:
"The preferred method of installing a custom recovery is through this boot mode. Rooting the stock firmware is neither recommended nor necessary"
So I thought I was doing the installation correctly in terms of warranty voiding.
Clearly that assumption was false because meanwhile Knox got implemented and I should have read upfront before installing CM obviously on my new phone. My bad.
However I am now in a stiuation where I have bought a phone with a hardware defect (Sim card is randomly not being detected) but I cannot return it because Samsung has set a flag which cannot be reset (http://omegadroid.co/wanted-knox-void-warranty-0x1/).
I have read some posts (e.g. http://forum.xda-developers.com/showthread.php?t=2568450) about that it is possible to return to stock but either the posts are relatively old or they are about other devices and/or Android versions.
So I am confused about what my options are at the moment and before I go into the process of trying to bring back my phone to stock I wanted to ask help from some better informed people about this situation.
My questions are:
1. Can I go back to stock firmware from CM 12.1 while knox got triggered.
2. If so, do I need to root my phone?
3. If succeeded is there a way to hide the Warranty Void message while booting. I am talking about hiding here and not removing/resetting the flasg to 0x0 as that is not possible.
Thanks in advance,
Undersound
Click to expand...
Click to collapse
1) Yes, of course.
2) No.
3) Don't know what you are talking about.
Odin is used to flash stock roms on Samsung devices. That is the only way.
There are links to guides in the help thread in the Q&A section.
Yes u can go back to stock. Just download the firmware from sammobile.com then download odin now put ur phone in download mode and start odin as admin.
Next in pda select the file u downloaded from sammobile and flash.
Thats all
Sent from my GT-I9505 using Tapatalk
jimmyoh said:
Yes u can go back to stock. Just download the firmware from sammobile.com then download odin now put ur phone in download mode and start odin as admin.
Next in pda select the file u downloaded from sammobile and flash.
Thats all
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
Thanks both for your answers.
Should have been more clear in point 6 where I write I tried to reset to stock.
I tries resetting to stock with Odin 3.10.7 (also tried 3.09 and 3.07) and a firmware image from sammobile.com
Unfortuanetely I got an error relating to my pit file.
Used heimdall to create one from my phone.
Tried to go back to stock again via pda and pit file options (re-partition checked this time)
Unfortuanetely it still didn't work. Don't have access to the exact error messages here from that process but will post back the error messages once I do.
Thanks again for your time and support on this
undersound said:
Thanks both for your answers.
Should have been more clear in point 6 where I write I tried to reset to stock.
I tries resetting to stock with Odin 3.10.7 (also tried 3.09 and 3.07) and a firmware image from sammobile.com
Unfortuanetely I got an error relating to my pit file.
Used heimdall to create one from my phone.
Tried to go back to stock again via pda and pit file options (re-partition checked this time)
Unfortuanetely it still didn't work. Don't have access to the exact error messages here from that process but will post back the error messages once I do.
Thanks again for your time and support on this
Click to expand...
Click to collapse
Such errors are usually related to the USB cable, USB port on the pc (back ports are recommended) and Windows version.
Edit: You might be able to use FlashFire to flash the stock rom if Odin doesn't work.
GDReaper said:
Such errors are usually related to the USB cable, USB port on the pc (back ports are recommended) and Windows version.
Click to expand...
Click to collapse
That's good to know, thanks. I was trying this with an extended usb cable so it can be the definitely the case.
Will try later today with a direct connection to a backport.
GDReaper said:
Such errors are usually related to the USB cable, USB port on the pc (back ports are recommended) and Windows version.
Edit: You might be able to use FlashFire to flash the stock rom if Odin doesn't work.
Click to expand...
Click to collapse
Managed to return to stock firmware, yay!
In case it helps someone else, here are my steps:
1. By dialing *#1234# on a similar phone I checked what ap/cp/csc version I needed
Code:
AP: I9505XXUHOF2
CP: I9505XXUHOF2
CSC: I9505OXAHOF2
2. Downloaded the correct firmware image (http://www.sammobile.com/firmwares/download/50091/I9505XXUHOF2_I9505YHNHOF2_PHN/)
3. Extracted the firmware file
4. Opened Odin v3.10.7
5. Rebooted Phone in Download Mode (press and hold Home + Power + Volume Down buttons)
6. Connected phone and waited until I got a blue sign in Odin
7. Added the firmware file to AP / PDA
8. Made sure re-partition was NOT ticked
9. Clicked the start button
10. Then I got a PASS!
So I guess there can be 2 reasons my first attempt of flashing stock firmware did not worked:
1. The firmware I used the first time was not correct for this phone (http://www.sammobile.com/firmwares/download/64897/I9505XXUPOL1_I9505PHNPOL1_PHN)
I did not know at that time about checking my ap/cp/csc described in Step 1 above so I was just downloading the firmware which seemed the most appropiate according to the country / provider.
What helped me a lot was when I found the explanation of the parts of the version number:
Code:
I9505XXUHOF2
I9505 = phone model
XX = country/region code
UHOH2 = modem
2. The second attempt I followed GDReaper suggestion and I used the usb cable directly on of the backports of my pc so that could have helped as well.
Another thing that was not clear to me at first were the providers code. Or well, they were clear to me that they were abbreviations for telecom providers but I did not bought these phones from a provider so I was not sure which one to pick. After a while I came to discover that I needed PHN which means Unbranded
Code:
---------------------
PHN = unbranded
TNL = Tmobile
VDF = Vodafone
Thanks all for the help