Database Users

Stock Eclair Rom (I9000UGJH2)

Long story short, I lost my IMEI. After reading a lot and trying a lot of thing, I was able to restore the product code but still, my IMEI is a generic one.
I can still access network and make calls, but it bugs me so I have yet one last thing to try; revert to stock eclair rom.
Only thing, I can't find any of those...
Actually, I "found" I9000UGJH2 but when I push it with Odin, I get a boot loop (with the samsung logo)
So, doest anyone can provide me with a stock Eclair rom?
IE:
-I9000UGJH2
-I9000DTJG4
-I9000UGJG8
Thanks!

Get a GB stock ROM and flash it via Odin...

FYI: If I ask for a specific version I have already tried those easely available, from JL2 to KG3 to JL2 then upgrade via kies to KG3.
as stated on the original request, I want to test eclair as it was the original rom on it.

Then try FroYo. It's better than Eclair.

Bro, you have to learn to read...
JL2=froyo
KG3=GB
ALL ALREADY TRIED...
I specificaly asked for those rom FOR A REASON!

Hey.
Take a look at samfirmware, a quick search told me they have it there. You need to register (think it's still free, i haven't gone there in a while)
http://www.sammobile.com/
I've seen there:
Android 2.1 I9000HVJH1
Android 2.1 I9008ZMJG1
Android 2.1 I9000DXJG4
Android 2.1 I9000DDJF2
so pick your poison and good luck.
Also, since your chances of actually recovering imei that way are 50% at this point (it'll either work or not ), i'll also leave a document that tells you how to rebuild the /efs folder. Sorry, portuguese was the only language i found this (picked from another forum). I guess you can always use google translate if you need or shoot me a pm if you have any trouble understanding the language at some point, i'll be glad to help.
https://docs.google.com/document/d/...NQ__7Xmy7vS7KTxY/edit?authkey=CL3S_f8M&pli=1#
Again, good luck with that. I'm guessing if you ever recover your imei, an /efs backup will be the first thing you'll do

None of them actually works when you click on "download" on samfirmware.com
Thanks for the guide, I'll check this out!

t1mman said:
None of them actually works when you click on "download" on samfirmware.com
Thanks for the guide, I'll check this out!
Click to expand...
Click to collapse
Listen carefully;
The reason why you got a boot loop while flashing eclair,that could happen if you're flashing ONE FILE ROM (which is same as rooting,onnly PDA)..
I %100 recommend that;
Flash a rom that HAS 3 FILES ,and with that , also PIT file which makes it 4 files BASE flashing...
Roms that are containing 4 files..
XXJVU (2.3.6 GB)
XXJVQ(2.3.4 GB)
JVQ could looks like older but belive me flash JVQ then you can GET JW4 latest offical european Value Pack firmware FROM KIES!.
All you have to do ;
https://docs.google.com/file/d/0B_UDv0VHoyaRak95b0NSX3Q1Tlk/edit?pli=1 download this (this is my recovery rom )
in zip file,there are 4 files and they are;
s1_odin_20100512.pit (which goes to PIT in odin)
CODE.tar (which goes to PDA in odin)
MODEM.tar (which goes to PHONE in odin)
CSC.tar (which goes to CSC in odin)
MAKE SURE RE PARTITION is CHECKED.Then flash it .)
After that when you get your imei back,
type *#272*imeinumber# in dialer then change CSC to XEU (united kingdom).. Then connect to kies and voila!!!!!! You 'll get JW4

Again, thanks for the heads up but I NEED an eclair rom for a SPECIFIC reason, a specific test, I have already tested GB and Froyo and it doesn't work.
I don't need it for JW4 or any other already available rom out there, I can already flash them with Odin or flash with CWM.
So, if anyone has the 3 files for I9000UGJH2 and can provide it, please let me know! I can provide an FTP for you to drop it.
BTW, I've tested the portugeese walktrough to no result.

Hmm.Okey then but ,if gb/froyo flashing didn't get your imei back..I dont think eclair wont get that too
Is it must be UGJH2? Or any other eclair roms.. ?
Sorry for your imei bro btw...i hope you can get it back... Did you ever take a backup of your efs folder on any custom roms before this thing happened?
GT-I9000 cihazımdan Tapatalk 2 ile gönderildi

try to flash any eclair rom you find,preferably stock

I would think that, since the IMEI and Product number are "related" (in the /efs folder), it would need to, at least, have the product code (sell code, with *#272*IMEI#), that's why I'm looking for thoses specific roms.
And no, I didn't made a backup prior to this... :S

snchep drgs
t1mman said:
Long story short, I lost my IMEI. After reading a lot and trying a lot of thing, I was able to restore the product code but still, my IMEI is a generic one.
Click to expand...
Click to collapse
Would you mind to tell me how? because i lost my generic imei too. Thanks...

zakrilex said:
Would you mind to tell me how? because i lost my generic imei too. Thanks...
Click to expand...
Click to collapse
Wow, that was long ago!
I think you can change your product code this way:
To change the CSC (otherwise known as product code) dial *#06# to get your imei and write it down carefully.
Then dial *#272*your imei# (replace "your imei" with the 15 digit code you just wrote down) and you will get to the CSC selection screen.
Choose the one you want then hit "install".
Be aware that changing the CSC will effectively do a 'wipe data' on your phone.
Click to expand...
Click to collapse
But for the IMEI, you'll have to get it reprogrammed by a provider or something similar.

[Q] Hong Kong 32GB n9005 and PIT

I want to flash an Aussie ROM on my HK 32GB n9005. I've been doing some reading and what I think I need to do is as follows...
ghibli3's thread at http://forum.xda-developers.com/showthread.php?t=2550823 specifically addresses this issue and thanks to those contributing there and elsewhere.
Now to check I understand what they are saying before I brick my phone.
I have these:
CSB_signed_HLTE_EUR_OPEN_32G_0718.pit
CSB_signed_HLTE_EUR_OPEN_32G_0805.pit
ghibli3-N9005.pit
ratcom-N9005.pit
I also used ghibli3's N9005-SaveMyPit from http://forum.xda-developers.com/attachment.php?attachmentid=2426123&d=1385903491 to get a copy of my current pit.
I have my original HK MI7 stock, a HK stock MK2 (used to root my phone originally using RDLV) and both an MI7 and MJ7 Aussie ROMs.
So... here is what I think I need to do... Please let me know if this is correct or tell me how to do it better.
Using Odin and with phone in DL mode, USB Debugging on, Samsung drivers and ADB setup on PC...
1. Load a PIT file in [PIT] in Odin and tick [Re-Partition] then [Start]
(1st question, do I reboot the phone or just go to the next step?)
2. Follow RDLV steps to flash the Aussie MJ7 to root the phone.
(2nd question, should I drop back to the MI7 version for the root operation? I don't think it is needed as when I rooted my phone with HK version, I had HK MI7 on the phone and used HK MK2 to root it)
(3rd question, I have Kies 3 on my PC - should I uninstall it before doing any of this or might it be helpful to have it still installed?)

OK, so no comments so far... let's try a slightly different approach.
(4th question, Can I load the PIT into Odin, tick [Re-Partition] and add in the VEGA version of the AP (from RDLV) and then flash them as one?

Journyman16 said:
OK, so no comments so far... let's try a slightly different approach.
(4th question, Can I load the PIT into Odin, tick [Re-Partition] and add in the VEGA version of the AP (from RDLV) and then flash them as one?
Click to expand...
Click to collapse
For using PIT file, you need to add the PIT to Odin when you flash so it'll repartition as it's flashing. However, don't take that as a solid cause I am not 100% sure myself as I haven't messed with PIT files (yet) - but from what I have read that is how it is done. - Have a scan through the HK bricked (solved) threads to be doubley sure cause yeah, it's easy to end up with a brick

Thanks for that. Kinda what I was planning to do but I'm not sure if I do the PIT flash first then do the rest or if I do it all as one process. I'll check out that thread... been looking anywhere I could find a PIT reference.

Well, that was fun... not.
I tried the PIT files with NAND erase all, re-partition f. reset time and Auto reboot all ticked - it failed - I got a systemconnection error. I tried again with each of the PITs listed above except ratcom's - his is from an MJ7 build and I was unsure if that would trip Knox or not.
2 hours pass, with me looking all around XDA and trying a variety of things. Incidentally I think maybe the systemconnect thing might be related to not restarting the phone to get the error screen. It seems Odin can do things when that screen is on that it can't do in plain Download mode. At least, on mine, the eventual fix worked only AFTER I had the error screen (shows the hone pic and a PC pic)
I didn't try flashing CWM. Nor doing anything that might add an MJ7 or KK bootloader. If I trip Knox I want it to be by my choice, not because I can't fix something.
But clearly I am doing something wrong in trying to repartition my phone - none of the PIT flashes worked. None of the flash ROM's worked. I looked around for a MJ3 or less ROM with the 4 files - figured I could get that I could try using a PIT for the right CSC and those files and solve both issues at once.
I tried my MK1 HK Vega image and no go. So I sat and thought it through and realised that last time I had problems I had the error screen NOT download mode so I rebooted the phone and Voila! up popped the error screen. Odin promptly flashed my HK MK1 version and now I am restoring my apps from the extSDcard. Got a bit of setup work to do but it's up and running again.
But I will have to trip Knox now - I'm sick of not having a Nandroid backup that could just restore everything where it was instead of me having to manually put things back as they were.
Any ideas as to what I did wrong?

Journyman16 said:
Well, that was fun... not.
I tried the PIT files with NAND erase all, re-partition f. reset time and Auto reboot all ticked - it failed - I got a systemconnection error. I tried again with each of the PITs listed above except ratcom's - his is from an MJ7 build and I was unsure if that would trip Knox or not.
2 hours pass, with me looking all around XDA and trying a variety of things. Incidentally I think maybe the systemconnect thing might be related to not restarting the phone to get the error screen. It seems Odin can do things when that screen is on that it can't do in plain Download mode. At least, on mine, the eventual fix worked only AFTER I had the error screen (shows the hone pic and a PC pic)
I didn't try flashing CWM. Nor doing anything that might add an MJ7 or KK bootloader. If I trip Knox I want it to be by my choice, not because I can't fix something.
But clearly I am doing something wrong in trying to repartition my phone - none of the PIT flashes worked. None of the flash ROM's worked. I looked around for a MJ3 or less ROM with the 4 files - figured I could get that I could try using a PIT for the right CSC and those files and solve both issues at once.
I tried my MK1 HK Vega image and no go. So I sat and thought it through and realised that last time I had problems I had the error screen NOT download mode so I rebooted the phone and Voila! up popped the error screen. Odin promptly flashed my HK MK1 version and now I am restoring my apps from the extSDcard. Got a bit of setup work to do but it's up and running again.
But I will have to trip Knox now - I'm sick of not having a Nandroid backup that could just restore everything where it was instead of me having to manually put things back as they were.
Any ideas as to what I did wrong?
Click to expand...
Click to collapse
2nd link in my signature.
Follow it to step 6. Then flash whatever ROM you want. Make sure your phone is 32 gigs or more. Won't work on 16 gb version.

So this gets a bit strange now... I downloaded Phone Info from Play Store and ran it. I did that because I noticed I was having Wifi issues - it was working but kept thinking it was off - I'd click it to turn it on and the button wouldn't go green, but I had signal in the Notification bar. Going to Recovery to clear cache showed it was now applying CSC-code as BTU instead of TGY, so SOMETHING worked when I was doing the PITs.
So, Phone Info shows my Region Code as BTU, my CSC country as UK/IRE and my CSC Country ISO as GBBut I have a mix of ROM info:
Bootloader: ZHUBMI7
Baseband: ZHUDMJ9
PDA: XXUDMK2
CSC: OXADMK2
So, PDA and CSC are from a UK MK2 I tried to use early on and failed with, while BL and BB are from the original HK MI7 (BL) and the HK MK1 I rooted with.
So my question is now, can I now flash a BTU or other normal ROM onto my phone, using the RDLV process to make sure I get root and don't trip Knox?
IIRC I think the process works up to MK2 (and certainly does to MK1 as that what I used originally) so I should be able to DL (say) XXUBMJ1 to use for the BL and use XXUDMK2 for the root process. (i.e. the same as I did using HK MI7 for the BL and HK MK1 for the root process)
3 questions:
1. Is it the PDA that determines the partition Hong Kong users have such problems with? Or is it the Bootloader?
2. Can anyone think of a reason why this would not work? (now my CSC is BTU)
3. Could I now use an Aussie ROM to run the RDLV process?

FeralFire said:
2nd link in my signature.
Follow it to step 6. Then flash whatever ROM you want. Make sure your phone is 32 gigs or more. Won't work on 16 gb version.
Click to expand...
Click to collapse
Thanks for the Reply.
For now I'd prefer to stay away from KK ROMs - too many people having issues, and the prevention of returning to 4.3 is, to me, a killer until Samsung get the bugs out. Given that many people are doing OK with KK, I think it is unlikely Samsung will do much about the bugs until a larger number of people have problems and start bombarding their support lines.
Plus, on 4.3 I have a very fast phone that gives more than 2 days use even with fairly heavy use (for me) and up to 4 days for light use. Why make an irreversible change when the phone is doing well already? For me the next step is custom recovery - I don't like not having a Nandroid BU and several times now after restoring apps I find I need to fix permissions - without custom recovery that means a laborious uninstall/reinstall from Play Store, one app at a time. Pisses me off...
I find it interesting that Samsung are clearly using users such as XDA members as their testing area, while at the same time shutting down the activities we like to do. (Custom ROMs etc) I say clearly using us because otherwise there is no excuse for the regularity of leaked ROMs - Samsung pass it on to us to try and I would bet, have staff watching us to see what issues we have.
So it seems a bit counter-productive to work so hard to lock the phones so we can't play with them.

Journyman16 said:
Thanks for the Reply.
For now I'd prefer to stay away from KK ROMs - too many people having issues, and the prevention of returning to 4.3 is, to me, a killer until Samsung get the bugs out. Given that many people are doing OK with KK, I think it is unlikely Samsung will do much about the bugs until a larger number of people have problems and start bombarding their support lines.
Plus, on 4.3 I have a very fast phone that gives more than 2 days use even with fairly heavy use (for me) and up to 4 days for light use. Why make an irreversible change when the phone is doing well already? For me the next step is custom recovery - I don't like not having a Nandroid BU and several times now after restoring apps I find I need to fix permissions - without custom recovery that means a laborious uninstall/reinstall from Play Store, one app at a time. Pisses me off...
I find it interesting that Samsung are clearly using users such as XDA members as their testing area, while at the same time shutting down the activities we like to do. (Custom ROMs etc) I say clearly using us because otherwise there is no excuse for the regularity of leaked ROMs - Samsung pass it on to us to try and I would bet, have staff watching us to see what issues we have.
So it seems a bit counter-productive to work so hard to lock the phones so we can't play with them.
Click to expand...
Click to collapse
You need the international pit file in your phone. Flashing the CSC file will put that pit in your phone. It won't touch the bootloader or the system files.

FeralFire said:
You need the international pit file in your phone. Flashing the CSC file will put that pit in your phone. It won't touch the bootloader or the system files.
Click to expand...
Click to collapse
Unfortunately, PIT's don't seem to come easy. As above I have about 4 of them I tried. There seems a bit of a disconnect between what the AP/CP/CSC are and what the files in a ROM are e.g. in XXUBMH1 there's boot.img, recovery.img, system.img.ext4, userdata.img.ext4, persdata.img.ext4, persist.img.ext4 and in XXUBMI7 there's sbl1.mbn, aboot.mbn, rpm.mbn, tz.mbn, sdi.mbn, NON-HLOS.bin, boot.img, recovery.img, system.img.ext4, modem.bin, cache.img.ext4, hidden.img.ext4
While I've been around a while now, this seems to be a blank spot for me at present - how do I flash a CSC? From reading it seems some ROM.s come with 4 or 5 files, e.g. see attachment - but I haven't been able to find one yet. (the one in the pic was hosted on Hotfiles which is now defunct thanks to the Almighty USA draconian control freaks. )
Update: I think I have found a copy of it so I can try that when it finishes DL'ing.
Other than that, anyone know of where there might be another such ROM to DL? Also if I am flashing a CSC file do I flash the PIT as well (i.e. at the same time) or do the PIT first?
Which Odin options get ticked for a PIT? I tried [F. Reset Time] [Re-Partition] [Auto Reboot] [Nand Erase All] previously and it didn't seem to work. I saw a recovery type post that suggested ticking [Phone EFS Clear] but seems to me that is a tick towards Brick - and the Recovery being offered was to a KK ROM anyway.

FeralFire said:
2nd link in my signature.
Follow it to step 6. Then flash whatever ROM you want. Make sure your phone is 32 gigs or more. Won't work on 16 gb version.
Click to expand...
Click to collapse
FeralFire said:
You need the international pit file in your phone. Flashing the CSC file will put that pit in your phone. It won't touch the bootloader or the system files.
Click to expand...
Click to collapse
I just looked at your post again - I realise I might have a wrong idea. Although the leaked ROM is KK, I was assuming flashing the CSC would upgrade my phone - is that the case or can I use your 6 steps just to change my PIT and then do the 4.3 RDLV process to have a root 4.3 phone?
Downloading it now - started with the torrent but that's running slow; I will let it run to completion to maybe help some others get it faster but I've got the Storage Cow one running as well. We'll see which one arrives first Either way I'll leave it seeding.

Journyman16 said:
I just looked at your post again - I realise I might have a wrong idea. Although the leaked ROM is KK, I was assuming flashing the CSC would upgrade my phone - is that the case or can I use your 6 steps just to change my PIT and then do the 4.3 RDLV process to have a root 4.3 phone?
Downloading it now - started with the torrent but that's running slow; I will let it run to completion to maybe help some others get it faster but I've got the Storage Cow one running as well. We'll see which one arrives first Either way I'll leave it seeding.
Click to expand...
Click to collapse
Yeah, you should be able to.
I tried flashing the MK2 ROM after flashing that CSC. It worked perfectly. But then I upgraded to kitkat. So I can't test JB stuff anymore.

FeralFire said:
Yeah, you should be able to.
I tried flashing the MK2 ROM after flashing that CSC. It worked perfectly. But then I upgraded to kitkat. So I can't test JB stuff anymore.
Click to expand...
Click to collapse
Well, it let me flash the vega BTU MK2 ROM but now there's a wifi problem. Still waiting for cygwin to download so I can RDLV on the XSA ROM. There seems to be some kind of conflict between BTU and Australian settings. Says to turn on wireless and actually finds my SSID's but then doesn't connect properly. le sigh...

Well it's been coming up to 24 hours with no phone but I seem to have found my way.
The problem seems to have been a mismatch between BL, CSC and PIT. In trying to get off the Hong Kong set up I wound up with a ZHU BL, BTU CSC and XSA CP and AP. It worked but I had no wifi. tried a few things to get it working and in trying to flash an XSA CSC (I think it was XSA) I got the Knox bit change. With no wifi I thought maybe the problem was the BUT-based CP needed changing. In trying to fix that, somehow I triggered Knox
I tried DL & Install of Omega 6 (it's a 4.3 - not ready to go KK yet) but although it completed nicely (so many ROM's got hidden or system errors in Odin) the phone didn't start. I tried installing Philz so I could run things from the extSDcard but an XSA wouldn't work nor would anything I had below MJ7. Last Phone Info view I had I still had a ZHU CP, even though AP and CSC were XSA-based.
Finally I got the MJ7 ROM from http://forum.xda-developers.com/sho...9005xxudmj7-pre-rooted-knox-free-odex-bl-free and it did the trick.
It's been a learning experience but I'd be happier if I knew for sure both what triggered the Knox bit (I was being very careful about it) and why some of the other ROM installs simply didn't work.

Resurrecting this one because I'm looking for info on flashing my 32G HK Note 3, but it came with KK pre-installed. So I'm not sure what differences I have to be aware of. Any tips?

For whoever still experiences issues with HK 32GB n9005 devices, After wasting half a day on that crap, i was able to flash N9005ZSUGOK2_N9005OZSGOK2_TGY from sammobile coupled with the PIT attached.

sm-n900
sm-900 and pit

S5 Debranding

Ok i have tried to de brand the firmware worked but still said the OLD CSC
I have tried the XDA File info CSC changer and it says there is a file missing
The firmware is a Multi CSC but i can not find any way to change this
Help !!!

Flash unbranded firmware in Odin, until auto reboot, go into recovery and factory reset. Backup all your important data first, though!

Northern.dj said:
Help !!!
Click to expand...
Click to collapse
Unfortunately you didn't provide any information about your situation making it impossible to tell if the majority of possible options would be viable in your case. You didn't even tell us which S5 model, firmware version or carrier you have, let alone anything else.
Given the lack of crucial details, all I can suggest is that you look at debloating threads or consider installing a custom ROM.
.

fffft said:
Unfortunately you didn't provide any information about your situation making it impossible to tell if the majority of possible options would be viable in your case. You didn't even tell us which S5 model, firmware version or carrier you have, let alone anything else.
Given the lack of crucial details, all I can suggest is that you look at debloating threads or consider installing a custom ROM.
.
Click to expand...
Click to collapse
The S5 Model is SM-G900F
the Carrier is Vodafone
and they have just rolled out another 4.4.2 Variation and its not on sammobile yet
just dumps more apps eg the RCS
why the XDA CSC changer will not help is strange as it has on other phones
I don't want a custom rom on as I am passing this down to my son so I don't want super user root on

Then use Odin to install the generic 900F European Open firmware, which is unbranded.
If you have any ongoing issues, backup any files important to you and do a factory data reset as well.
.

fffft said:
Then use Odin to install the generic 900F European Open firmware, which is unbranded.
If you have any ongoing issues, backup any files important to you and do a factory data reset as well.
.
Click to expand...
Click to collapse
Hello,
Rather than start a new thread, I think I might get help here. I'll also say sorry in advance since I have searched through almost the entire forum since last Thrusday, but havent figured out how to fix this.
I have a carrier unlocked G900F (CSC:XFV, South Africa, using latest ANG2 FW) with Vodacom branding. No amount of data resets and flashing with the generic BTU firmware seems to remove the Vodacom boot animations and its bloatware.
Some facts:
(1) The boot and shut down animation seem hardcoded or deodexed or something in the nand. I have tried replacing the files in the system/media folder but no avail. Using offshelf programs was no help.
(2) The Vodacom bloatware deleted with Titanium Backup comes back with with every flash, data or cache reset.
(3) I am already rooted using the Towelroot method and Knox is 0x0.
(A) Is there a way to permanently clean up the above and start off with a fresh clean phone?
(B) Can a 'generic' bootloader be flashed through Odin?
Again I apologize for hogging the thread.
Cheers.

turborrr said:
Rather than start a new thread, I think I might get help here.
Click to expand...
Click to collapse
It's customary to start your own thread, rather than piggyback or hijack someone else's. And you should probably do that if you have any follow up questions.
The boot animations are not hard coded and there are a number of existing threads that elaborate on the format. The files are in /system/media e.g. bootsamsung.qmg, bootsamsungloop.qmg, shutdown.qmg. You said that you replaced the files here, but unfortunately gave no specifics or details thereof, making it impossible to discern where you went awry. Perhaps you have a cached copy extant. Try booting to recovery mode and wipe the system cache. In the alternative, did you install any utilities or a custom kernel that may be using the generic Android bootanimation.zip format, instead of the default Samsung .qmg?
Bloatware is a plague. Most firmware, including multi-CSC and probably Open_Eur (ope) (unconfirmed) have carrier specific apps and bloatware. In multi-CSC configurations the apps are triggered by your CSC sales code. you can either change your CSC or simply freeze or debloat your ROM by renaming, moving or deleteing bloatware apps. Or migrate to a custom ROM as they have typically been debloated by the developer in advance.
The goal of a "clean" ROM, devoid of carrier specific apps or bloatware is an elusive one that you probably can't do simply by installing an alternate stock firmware. You generally have to debloat firmware yourself or avail yourself of a custom ROM to the same effect.
Odin is a software package made by Samsung. You are more likely to see flying unicorns than before Odin will freely write third party bootloaders. But it's a moot point as first you'd have to find such a bootloader.
Bootloaders are hardware specific and written by hardware vendors for a given hardware platform. The bootloader is outside Android, it boots the device into Android. Even "open source" Android projects like CM or ASOP use the proprietary bootloader of necessity. Given the proprietary hardware interfaces and drivers it is a daunting task to write a bootloader from scratch for undocumented hardware.
Open source Android bootloaders exist e.g. the Little Kernel bootloader but they do not support most hardware.
.

Northern.dj said:
why the XDA CSC changer will not help is strange as it has on other phones
Click to expand...
Click to collapse
Did you try this one: Phone INFO ★Samsung★ --> Menu --> Other Tools --> CSC Changer?
P.S. This tool needs ROOT permission to work.

vndnguyen said:
Did you try this one: Phone INFO ★Samsung★ --> Menu --> Other Tools --> CSC Changer?
P.S. This tool needs ROOT permission to work.
Click to expand...
Click to collapse
The XDA App does not work it reports a file missing But i have some success
I will post a method as soon as i get it down
But it only works on "F" models with unlocked Bootloaders

Northern.dj said:
The XDA App does not work it reports a file missing But i have some success
I will post a method as soon as i get it down
But it only works on "F" models with unlocked Bootloaders
Click to expand...
Click to collapse
Please try the Phone INFO app I have mentioned above. I should work.

vndnguyen said:
Please try the Phone INFO app I have mentioned above. I should work.
Click to expand...
Click to collapse
Nope it does not work reports in yellow that a file is missing from the internals SD
It does work on other devices but so does CSC Changer but that says it may need root Accses

Northern.dj said:
Nope it does not work reports in yellow that a file is missing from the internals SD
It does work on other devices but so does CSC Changer but that says it may need root Accses
Click to expand...
Click to collapse
Yes it need ROOT permission to change the CSC.

vndnguyen said:
Yes it need ROOT permission to change the CSC.
Click to expand...
Click to collapse
well I have managed to change the CSC from VOD to BTU with No root
I have just repeated the same with a O2 Network Phone and even reversed the proses but its only for the S5 and Note 3
I will put a Link up soon when I have wrote the instructions but the app is still handy to confirm one point of the excises

fffft said:
It's customary to start your own thread, rather than piggyback or hijack someone else's. And you should probably do that if you have any follow up questions.
Click to expand...
Click to collapse
I suppose this was my first post at XDA. You could cut some slack here.
Anyway, issue sorted. The trick is to go directly into recovery (unchecking auto-reboot in Odin helps) after flashing a clean FW, and wipe data and cache. Rinse and repeat if you want.
CSC successfully changed from XFV to BTU. Surprisingly also gained quite a bit of disk space but I can not confirm the exact amount. All the bloat is gone with no sign of it.
Thanks anyway.

Help Pleaseeeee!

Hi all,
Right i used to flash custom roms on my phone all the time but haven't done it in a while i've kept it as stock....Last night i flashed a stock rom to my phone and lost the use of my menu and back soft keys? Now i haven't got a clue what to do i did read through a thread but that's just confued me even more...
I tried to flash a touch recovery on my phone but i don't think i can do that as i haven't rooted my phone yet? (is that correct)
Model Number: GT-i9505
And Ver:5.0.1
BB [email protected] I9505XXUHOJ2
Build Num: LRX22X.I9505XXUHOJ2
Any help is greatly appreciated

Recovery and root are different things. They can work independent of each other.
And rooting the phone is just as simple as flashing the recovery. Both processes are done via Odin.
You will be looking at TWRP recovery if you are to flash one. Odin install instructions can be found on their site.
As far as your keys go, I don't know what to suggest, other than flashing a different rom. Official roms shouldn't even cause such problems.

Thanks for the reply, I don't know what has happened but there is a thread full of it here http://forum.xda-developers.com/galaxy-s4/help/problems-official-update-signal-soft-t3250132

It definitely appears to be an error on Samsung's part. Or something went bad during the installation.
So basically the keys have the wrong "drivers" installed, or they were corrupted somehow.
The solution would be to try and update them using the menu posted in your reference thread.
Or try flashing a newer version stock rom, hopefully also updating the key firmware and fixing your problem.

GDReaper said:
It definitely appears to be an error on Samsung's part. Or something went bad during the installation.
So basically the keys have the wrong "drivers" installed, or they were corrupted somehow.
The solution would be to try and update them using the menu posted in your reference thread.
Or try flashing a newer version stock rom, hopefully also updating the key firmware and fixing your problem.
Click to expand...
Click to collapse
I initially installed a stock rom i donwloaded from sammobile. ( 2015-12-08 United Kingdom (Black Edition) 5.0.1
I9505XXUHOJ2 I9505YXYHOK1) Which was that one. and that would be the lastest one for my phone wouldn't it?

jacko_oafc said:
I initially installed a stock rom i donwloaded from sammobile. ( 2015-12-08 United Kingdom (Black Edition) 5.0.1
I9505XXUHOJ2 I9505YXYHOK1) Which was that one. and that would be the lastest one for my phone wouldn't it?
Click to expand...
Click to collapse
You can install firmware from other countries if your phone is not carrier locked.
Or check for OTAs, I know there have been other updates since then. For instance, my baseband is UHOJ4, which is newer than yours.
If you can't force update the key firmware then you have two other options:
1) Send it to Samsung, as it is their fault.
2) Root it and use on-screen navigation keys. The problem with this option is the risk of screen burns, due to the long-term static image (the navbar) display.

GDReaper said:
You can install firmware from other countries if your phone is not carrier locked.
Or check for OTAs, I know there have been other updates since then. For instance, my baseband is UHOJ4, which is newer than yours.
If you can't force update the key firmware then you have two other options:
1) Send it to Samsung, as it is their fault.
2) Root it and use on-screen navigation keys. The problem with this option is the risk of screen burns, due to the long-term static image (the navbar) display.
Click to expand...
Click to collapse
Ahh right okay thanks! i thought that i had to download a specific one for my phone, Will have a try now.

Samsung Galaxy 8 rooting problem

Hi Forum users
have a problem in attempting to ROOT my phone
SAMSUNG GALAXY S8
been a novice user made a mistake
hopping I can still win.
will give very brief Description for the moment hoping to get some help
Basically phone booted into Standard ROM b4 I had finished (last step applying ROOT)
I now get an Error that boots and reboots) the error is
"Only official released binaries are allowed to be flashed"
can still get into Download screen, but cannot get to recovery (TWRP)
Oden can still connect to download screen.
I think what I need to do is a Factory reset again, and hopefully get back into RECOVERY
any suggestions or help would be gratefully received
thanks
PS
happy to give full description if needed

RANXzerox said:
Hi Forum users
have a problem in attempting to ROOT my phone
SAMSUNG GALAXY S8
been a novice user made a mistake
hopping I can still win.
will give very brief Description for the moment hoping to get some help
Basically phone booted into Standard ROM b4 I had finished (last step applying ROOT)
I now get an Error that boots and reboots) the error is
"Only official released binaries are allowed to be flashed"
can still get into Download screen, but cannot get to recovery (TWRP)
Oden can still connect to download screen.
I think what I need to do is a Factory reset again, and hopefully get back into RECOVERY
any suggestions or help would be gratefully received
thanks
PS
happy to give full description if needed
Click to expand...
Click to collapse
You will need to flash firmware via odin.
You can download firmware with updato.com or sammobile.com

Thanks for reply
Thanks for the reply
Ok just to be clear
I have already flashed TWRP
SO I have a bootloader installed
but cannot access RECOVERY MODE
SO I can access Oden in download mode
which Firmware are you suggesting I Flash
Just had a browse of those sites seem to be mainly Northern hemisphere
I am in Australia
But from what I understand we have the same CPU as the European ones

RANXzerox said:
Thanks for the reply
Ok just to be clear
I have already flashed TWRP
SO I have a bootloader installed
but cannot access RECOVERY MODE
SO I can access Oden in download mode
which Firmware are you suggesting I Flash
Just had a browse of those sites seem to be mainly Northern hemisphere
I am in Australia
But from what I understand we have the same CPU as the European ones
Click to expand...
Click to collapse
1. Flashing firmware will delete twrp.
2. Being from Australia myself all firmware are on the website. You will have to filter out for Australian firmware.
3. Do you know what firmware you are on.

Ranx
Hmm didn't take note of that B4 starting
but I think my Model numbers is SM-G950F if that helps
SM-G950F Exynos 8895 9 - just done a quick Google
one other thing that might be relevant i also managed top install
no-verity-opt-encrypt-5.1.zip
before stuffing up
will this affect things or will that be overwritten

RANXzerox said:
Hmm didn't take note of that B4 starting
but I think my Model numbers is SM-G950F if that helps
SM-G950F Exynos 8895 9 - just done a quick Google
one other thing that might be relevant i also managed top install
no-verity-opt-encrypt-5.1.zip
before stuffing up
will this affect things or will that be overwritten
Click to expand...
Click to collapse
Flashing stock rom will restore you phone to it's original state. So you will have to install twrp and root again.
For information about firmware and Odin maybe this may be of some help.
https://forum.xda-developers.com/galaxy-s8/help/method-downgrade-pie-to-oreo-t3916432/post79233602
If you are not sure about your firmware install the latest version.
On the website they will also have dates of when the firmwares are released.
You can use also samfirm or frija ( PC applications ) to download latest firmware.

OK will follow that info
and do the Firmware update
As I don't know the firmware number, will have to try the latest version
will do a bit more reading when I have a some time and give it a go
thanks for the links.
Will let you know how it turns out
THANKS

Few more Questions
OK done some reading
filtered out some relevent Files, (I hope)
one file took 16 hours to download (they where feeding it at 50kbs).
So have two files which where listed as XSA carrier,
others where Telstra and Optus.
As I am not aware of XSA carrier was hopping that it was some sort of generic carrier firmware
Is that correct ??
One is version 8
the other is version 9
So should I go with the version 9 ?
Sorry for all the questions, just want to make sure I get it right
THANKS

RANXzerox said:
OK done some reading
filtered out some relevent Files, (I hope)
one file took 16 hours to download (they where feeding it at 50kbs).
So have two files which where listed as XSA carrier,
others where Telstra and Optus.
As I am not aware of XSA carrier was hopping that it was some sort of generic carrier firmware
Is that correct ??
One is version 8
the other is version 9
So should I go with the version 9 ?
Sorry for all the questions, just want to make sure I get it right
THANKS
Click to expand...
Click to collapse
XSA is unbranded firmware ( it's what I have installed on my phone).
If you are locked into a carrier flashing other firmware will not unlock you from that carrier.
Not knowing what firmware you had before and because of download speeds you may have to use version 9 ( PIE ) firmware.
To check software version no. ( bootloader ) you can check in download mode. It should have a line saying AP SWREV: B : * - the star is your bootloader version. So you will have to use this version or higher when flashing firmware.
Make sure of your model number when searching for firmware. S8 = SM-G950f

Im having a similar problem, had to install stock july patch im using latest odin version then, i install recovery but when the phone reboots there is no recovery, tried to downgrade to february patch but odin dont allow it

hasablack said:
Im having a similar problem, had to install stock july patch im using latest odin version then, i install recovery but when the phone reboots there is no recovery, tried to downgrade to february patch but odin dont allow it
Click to expand...
Click to collapse
Are you talking about stock or custom recovery and what is the issues you are having with it.
Depending on you bootloader version number you can not down grade firmware.

I tried to install stock recovery, the problem is: odin installs sucessfully recovery but when i try to go to recovery is not installed

spawnlives said:
XSA is unbranded firmware ( it's what I have installed on my phone).
If you are locked into a carrier flashing other firmware will not unlock you from that carrier.
Not knowing what firmware you had before and because of download speeds you may have to use version 9 ( PIE ) firmware.
To check software version no. ( bootloader ) you can check in download mode. It should have a line saying AP SWREV: B : * - the star is your bootloader version. So you will have to use this version or higher when flashing firmware.
Make sure of your model number when searching for firmware. S8 = SM-G950f
Click to expand...
Click to collapse
Thanks will do a check on firmware
PS
I am on NBN ,
fake NBN that is,
wireless,
but download speed was set at the other end

spawnlives said:
XSA is unbranded firmware ( it's what I have installed on my phone).
If you are locked into a carrier flashing other firmware will not unlock you from that carrier.
Not knowing what firmware you had before and because of download speeds you may have to use version 9 ( PIE ) firmware.
To check software version no. ( bootloader ) you can check in download mode. It should have a line saying AP SWREV: B : * - the star is your bootloader version. So you will have to use this version or higher when flashing firmware.
Make sure of your model number when searching for firmware. S8 = SM-G950f
Click to expand...
Click to collapse
Hi Spawnlives
ok have installed Firmware version 9 all ok
THANKS
have my phone working again
My phone was Ver 5
"on a different matter having real trouble signing into this forum
pretty much had to reset my pass word every time"

RANXzerox said:
Hi Spawnlives
ok have installed Firmware version 9 all ok
THANKS
have my phone working again
My phone was Ver 5
"on a different matter having real trouble signing into this forum
pretty much had to reset my pass word every time"
Click to expand...
Click to collapse
Glad you got it sort out.
Not sure about the signing in. I use mobile app which is logged it to my Google account. I do have some issues with the PC ( without logging into Google ) but don't use it much. All I can suggest is to try a search on XDA or ask the moderators for assistance

Retry installing Recovery
hasablack said:
Im having a similar problem, had to install stock july patch im using latest odin version then, i install recovery but when the phone reboots there is no recovery, tried to downgrade to february patch but odin dont allow it
Click to expand...
Click to collapse
Try to install TWRP again via Odin.