[Q] Stuck on JF3 Firmware - No Kies Update - Galaxy S I9000 Q&A, Help & Troubleshooting

Hi there,
I successfully upgraded my SGS to 2.2.1 (JPY) via the Kies Registry Patcher in January. All seems well however I just tried doing exactly the same trick with my sister-in-laws SGS and no luck. Successfully got her rooted and unlocked, but for some reason I cannot get the registry spoof working.
I know I have not done things in exactly the same order for her phone, but it is bugging me. I tried with Kies 1.5(?) but when the phone was plugged into Kies it flashed up the "You can update your firmware" but when the actual process kicked off no firmware was available. She's on JF3.
Her SGS is from the same company, locked to the same network. The only thing I can think of is that the original spoof I did is still in my system registry and that her values do not match up in the same way? I have no idea...
I have now updated to Kies 2.0 to see if I can just get a normal 2.2 update for the T-Mobile firmware, but if her experience is like mine, that firmware has to go! So 2.2.1 XEU is the goal.
Any ideas?
As a side issue, now that OTA is enabled for 2.2.1, does that mean I will never have to fight Kies for an update?

http://forum.xda-developers.com/showthread.php?t=959806, as well you could also use Odin/Heimdall (? spelling) to flash a 2.2.1 ROM. OTA is not currently activated.

OTA at Samsung end? As the option is there on my phone and when i run it is says "no updates available".
Anyway - yeh. I saw that link. Will check it out when I next get my mitts on her phone.
What I don't know is what has changed? Has ?Samsung wised up to the previous spoof in some way?

skinfreak said:
OTA at Samsung end? As the option is there on my phone and when i run it is says "no updates available".
Anyway - yeh. I saw that link. Will check it out when I next get my mitts on her phone.
What I don't know is what has changed? Has ?Samsung wised up to the previous spoof in some way?
Click to expand...
Click to collapse
You can spoof by patching a file to make Kies2.0 believe that another firmware is connected, but when the update starts, another check is made directly to the phone, which is new as of Kies2.0. This is where we get stuck in patching Kies2.0. The module that checks this is encrypted which makes is impossible to patch it.
This is why I went for another approach and spoofed the firmware that the device is reporting, to fool Kies2.0 in every moment

Related

[Q] Need to get Kies working again

Hi all,
When I bought my phone it shipped with I9000XWJFB/I9000OXXJF5/I9000XXJF5/I9000XWJF5.
Shortly after I flashed to I9000XWJM2/I9000OXXJM1/I9000XXJM1/I9000XWJM2, through Kies with Test Mode On.
When the JPC firmware came out, I flashed it onto my phone using Kies (with the registry fix and Test Mode On).
I later found out it was causing problems with the SalesCode (ie. nv_data.bin/md5),
so I deleted mv_data.bin/md5 and eventually restored to JM7 (using ODIN)
and was back to the original SalesCode and seemingly had everything back.
Now, out of curiosity I wanted to see if I could make Kies flash JM1/JM2 back as it did previously,
but I've found that no matter what I do to the registry, Kies will always tell me: This device's version cannot be updated.
Is there something I'm missing, or will Kies simply no longer function after I flashed JPC,
even though I reverted, restoring my old nv_data.bin/md5 in the process.
Motjida said:
Hi all,
When I bought my phone it shipped with I9000XWJFB/I9000OXXJF5/I9000XXJF5/I9000XWJF5.
Shortly after I flashed to I9000XWJM2/I9000OXXJM1/I9000XXJM1/I9000XWJM2, through Kies with Test Mode On.
When the JPC firmware came out, I flashed it onto my phone using Kies (with the registry fix and Test Mode On).
I later found out it was causing problems with the SalesCode (ie. nv_data.bin/md5),
so I deleted mv_data.bin/md5 and eventually restored to JM7 (using ODIN)
and was back to the original SalesCode and seemingly had everything back.
Now, out of curiosity I wanted to see if I could make Kies flash JM1/JM2 back as it did previously,
but I've found that no matter what I do to the registry, Kies will always tell me: This device's version cannot be updated.
Is there something I'm missing, or will Kies simply no longer function after I flashed JPC,
even though I reverted, restoring my old nv_data.bin/md5 in the process.
Click to expand...
Click to collapse
Samsung seems to have removed all firmwares that were available in test mode. As far as I know the only working codes are those that have been officially released.
Sent using my personal Dis-organizer GT-I9000
mickeko said:
Samsung seems to have removed all firmwares that were available in test mode. As far as I know the only working codes are those that have been officially released.
Sent using my personal Dis-organizer GT-I9000
Click to expand...
Click to collapse
I hope you're right
Though I've seen plenty of posts suggesting JM1/JM2 was still available, i dunno.
Yeah, the engineering mode is now disabled on Kies.
I think it has something to do with the fact that thousands of request were made in engineering mode during one day.... The script on Samsung update server has been modified to reject proto requests and only show official updates.

[Q] Samsung Kies "Device not Supported" error

Hey guys. I have had my Captivate since the beginning of September. I downloaded Samsung KIES and was able to download the update back in Sept. I have checked periodicially for any updates, was able to sync contacts, and all that. Yesterday, I went to check for an update, and there was one available. After downloading the update, KIES could no longer recognize my phone. I shut down my computer and the phone. When I reconnected, KIES told me that the "device was not supported." I have redownloaded it several times, but to no avail. I am trying it again, using advice I found on another forum service, hoping it will work. However, has anyone else had this issue, or is this an issue that seems to be plaguing the new update? I thought I was downloading a new firmware update for the phone, however, It may have been a KIES update...
What update did you install on your phone? Post your firmware, baseband, and kernel versions, along with the build number.
Also, this probably doesn't belong in the development section. You should post this in the general board.
[Update] I downloaded KIES again (the newest version) and it still says my device is not supported. My computer recognizes the phone, just not KIES...Is it still possible to download an older version of KIES, because the issue seems to be the version of KIES, and not my phone...?
kegobeer said:
What update did you install on your phone? Post your firmware, baseband, and kernel versions, along with the build number.
Also, this probably doesn't belong in the development section. You should post this in the general board.
Click to expand...
Click to collapse
This info would really help...
I didn't actually update my phone. KIES was downloading the update, and once the update was downloaded, my phone was not recognizable. I will move the forum to the general discussion and post the info there... Thanks!
Sent from my SAMSUNG-SGH-I897 using XDA App
i have the same problem on my i897. i m running latest cognition rom on mine that could be the issue?
I have the same issue with Kies. I downloaded an update for Kies and now Kies no longer sees my Captivate. My computer sees the Captivate no problem. I have been looking for an older version of Kies to go back to.
Kies update issue
I had the same problem once my version of Kies updated last week. I tired everything, cleared user setting and cache, formated the INT SD card.
Did a ODIN one click restore to the original firmware and tried the above steps again... Nothing...
I had to uninstall the full version of Kies and go back to the MINI version of Kies, then all was fine...
I'm suspecting that they updated the full version of Kies to exclude certain versions of the Galaxy S (Captivate in my case)...
I had the same thing happen after I let Kies update, tried everything I could think of, it would not link to the phone. I uninstalled the new version and reinstalled the older version I first had, all is good again. I suspect it was a deliberate move, as Samsung now says the Captivate can only be updated with Kies mini.
Sent from my SAMSUNG-SGH-I897 using XDA App
jth747 said:
I suspect it was a deliberate move, as Samsung now says the Captivate can only be updated with Kies mini.
Click to expand...
Click to collapse
I concur, since AT&T has removed all native tethering and WiFi AP ability from the captivate, I think they pushed Samsung to remove captivate support from Kies. I don't have time to look around, but perhaps Kies has a config file that can be updated/changed to re-add captivate support.
Same here. I just updated Kies to 1.5.3.10103_100 just now before doing research on the adverse affects (Who'da thunk it that I would need to). Turns out that after Kies installed the update, it can no longer recognize my Samsung Captivate. I am running Cognition 2.1.6 ROM but that shouldnt matter. Just last week I was able to connect to Kies and back up my calendars and messages. Now....I am getting the "connecting the device..." message. That message has been up for the past 40 minutes. I have not reflashed my phone for at least 2 weeks now.
Seems like the Kies update to 1.5.3.10103_100 did something bad.
Same Problem
Its the Kies new version bug !
need a solution
I went back to the older version kies (1.5.3.10075_17)
and it works very well now .. i think new version kies have some bug or problem
djdk80 said:
I went back to the older version kies (1.5.3.10075_17)
and it works very well now .. i think new version kies have some bug or problem
Click to expand...
Click to collapse
Have you read this thread? It's not looking like a bug - more like Samsung doesn't want the full Kies to work with US Captivates. Kies mini still works, and that's what Samsung wants people to use.
In case anyone is looking for an older version of kies, I found one at turbobit.net/i8v2c4oixldz.html
Thread moved to Q&A.
chernomorez said:
Have you read this thread? It's not looking like a bug - more like Samsung doesn't want the full Kies to work with US Captivates. Kies mini still works, and that's what Samsung wants people to use.
actually mind is samsung vibrant , anyhow still same problem
Click to expand...
Click to collapse
Remember you have to be in TWLauncher for Kies to work.
Also if you search for Kies you will find many prior versions.
I happened to have 1.5.3.10093_82 and reverted from the update.
Everything works fine.
I installed a previous version of Kies and it works just fine. If anyone needs a older version you can find it at samfirmware.com
They list all the versions that Samsung has made under the Samsung Kies link
encountered same issue.
here's another alternative link to older version 1.5.3.10092_2_1 that seems to work.
http;//org.downloadcenter.samsung.com/downloadfile/ContentsFile.aspx?CDSite=DE&CttFileID=3203268&CDCttType=SW&ModelType=N&ModelName=GT-S5250&VPath=SW/201009/20100914110209343/Kies_1.5.3.10092_2_1.exe

[Q] Trouble going back to Stock

From what I have gathered... this seems to be a problem that only I have encountered, or at the very least something that I have deemed annoying enough that now I have to solve it... but I recently threw Gingerbread onto my i9000, quite successfully I might add, but I decided I wanted to go back to Froyo until the official release of 2.3 comes out of Samsung, since I am a big fan of "stock".
Problem is, every single ROM (I am at ten and counting) always results in Kies telling me that there is no update available. I have been loading only stock ROMs onto my device, so I am a little confused by this, since even the 2.1 firmwares have given me the same message. I know that, when I had Froyo loaded on stock, the message read that everything was up to date or something along those lines. Having that knowledge just means I won't be able to stop trying to put things back to stock until I see that same message again.
Anyone able to shed some light on what is happening here and how to fix it? Ideally I would love to load up 2.1 Eclair, update to Froyo using Kies and then just call it a day.
(PS. on Gingerbread I am getting some weird "static" screen popping up every time I restart... is that normal? I will take a picture and post it into the Gingerbread review forum if I can capture it.)
i was in a similar boat as you, loading 2.3 was no problem but going back is a pain in the ass.
BE WARNED! I spent nearly a day and i know a fair amount about what im doing, i even had to make the USB jig to force download mode at one point (testing different ideas) so be prepared for some issues.
what i did was use odin to flash stock JL2 (9000M bell version here), with 512 pit and a CSC file from another build (sorry i forget), bootloader update repartition clear efs checked. Thats the ONLY thing i could find to get me back to stock without any internal SD error messages.
IF YOU FLASH THE WRONG THING OR THE FLASHING PROCESS SCREWS UP YOU CAN BRICK YOUR PHONE. Read twice, do once.
See if you can find a stock rom for your area, what your phone came with, with the proper pit file and csc file.
Best of luck, you are not alone. I will definately be waiting for a less buggy leak before i switch back to gingerbread.
Kies reads and looks for the correct software for your product code and firmware tied to the supplying network .Once you install different roms you may change those details and Kies cannot find the correct details on your phone to recognise and match it to a firmware .
Spoof product keys and Kies registry patcher posts may help .
jje
Thanks for the quick answers guys... I shall plug-and-chug a bit more tonight and see if I cannot get something to work... then I will be back to post of my success (or failure).
You can use SpoofFw to trick Kies think you are on an official fw, the let Kies do the stock upgrade for you.
Having quite a bit of trouble getting Busybox installed properly, apparently... SpoofFW always starts up with "BusyBox not found. Spoof not possible." I have installed BusyBox a couple of different times from different sources and different versions... nothing seems to work. Am I missing something?
Also, when loading certain ROMs... the phone doesn't seem to register the modem anymore. There is a 2.2 ROM (forgot which) and the 2.3.3 ROM (without Bootloader) which, unusually enough, are the only ones WITH a working modem. Just tried loading up the 2.3.3 ROM w/Bootloader but the modem file from the non-bootloader version, and that seems to work... weirdly enough.
Since I am betting that there will be a "official" update through Kies to 2.3.x at some point, perhaps I will stick with this... since I am using an official ROM, will Kies recognize my phone properly and offer me an update, or has my product code become screwed up?
Wirebrook. I already replied to one of these today. Same happened to me. flashed back to jpu with a view to using kies to upgrade me to jpy but it wouldn't. So flashed eclair jm1 and kies upgraded me to jpy so I suggest that. You'll have to flash bootloader afterwards though as you'll lose 3 button reboot. But don't panic
Sent from my GTI9000 using XDA App, gingerbread 2.2.3 rooted, ADW launcher + gingerbread theme
I am using an official ROM, will Kies recognize my phone properly and offer me an update, or has my product code become screwed up?
Its not an official rom its a Samsung stock rom not the rom that was supplied with your phone . Kies might update it or might not .
You have firmware provided by the original phone seller and product codes hardware id firmware id for that . Kies will see that and update .
But its going to show not the firmware supplied by the original phone seller and tied to product code etc . Then requires you to Spoof Kies for an update .
jje
@Mossy1963
I'll give it a shot this evening... I have the JM1 firmware glaring at me in the face on my desktop right now, though... not sure that worked right the first time.
@JJEgan
As long as it is all "stock" I am pretty much fine with it at the moment. Not too bothered with having it tied to it's specific product code so much, although that would be nice.
wirebook said:
Having quite a bit of trouble getting Busybox installed properly, apparently... SpoofFW always starts up with "BusyBox not found. Spoof not possible." I have installed BusyBox a couple of different times from different sources and different versions... nothing seems to work. Am I missing something?
Also, when loading certain ROMs... the phone doesn't seem to register the modem anymore. There is a 2.2 ROM (forgot which) and the 2.3.3 ROM (without Bootloader) which, unusually enough, are the only ones WITH a working modem. Just tried loading up the 2.3.3 ROM w/Bootloader but the modem file from the non-bootloader version, and that seems to work... weirdly enough.
Since I am betting that there will be a "official" update through Kies to 2.3.x at some point, perhaps I will stick with this... since I am using an official ROM, will Kies recognize my phone properly and offer me an update, or has mys product code become screwed up?
Click to expand...
Click to collapse
That error message its actually wrong, you get it because nv_data.bin could not be found in /efs folder.
This could be due to a faulty flash where Csc was not applied correctly in recovery on the first boot.
Reflash with Odin is the solution.
Sent from my GT-I9000 using XDA Premium App
@Mossy1963
No cigar whatsoever... Kies simply stated there was no update to be done. Oh well.
@LuffarJoh
Tried reflashing... didn't work either.
Aaaaand to make things weird, that sometimes-working Antenna suddenly started working with an Eclair ROM that it hadn't worked before. Then after a reboot... nothing anymore. And now I have flashed the thing back to Gingerbread and what do you know... no more antenna. I would much rather have a working phone as opposed to a "perfect-stock" phone, so it looks like I might have to get an exchange... and perhaps acquire what I was after in the first place at the beginning of this thread anyways.
Hi, I was wondering exactly the same thing after flashing 2.3.3 today. I just like the idea of being able to plug the phone into kies to get a proper release although, I've no doubt the exact same version will be available for download. Has anyone got any useful info ?

My gnote issue

hey all,
i'm new to the forums here at xda-developers but i'm in ire need of some advice/help if you would not mind sharing your experience.
Okay the issue.
I have a galaxy note gt-n7000, it will not update via kies or via the phone itself at all for months. I'm from England and i purchased it on contract from carphone warehouse; some vital information about the phone are as follows:
Android version - 2.3.6
Baseband version - N7000XXLPT
Kernel Version - 2.6.35.7-N7000LA6-CL907341 [email protected] #2
Build bumber - GINGERBREAD.XXLA6
CSC - XEU
I have tried several things to fix this such as:
Factory restting everything - the sd card, the phone... No eval.
Attempting to change the CSC to a different one from XEU
Waiting to see if any more updates are as followed
reconnecting/rebotting my phone to ensure the connection is okay to Kies
Another issue of this phone is that it will not download anything from the website such as bus timetable PPFs in which it used to be beforehand, i am completely stumped by it
thanks for your time to read this and hopefully help,
Nozz.
P.S I don't really want to root my phone cause my warranty will void otherwise.
have you updated the kies? use latest version of kies to update it should work.
Since youre factory resetting, i presume you dont care for any data loss... You can go to recovery (turn off phone then press and hold volume up+power+home until the phone turns on) then do the factory reset there... (this is not touch interface.. You have to use volume buttons and the power button to select your option):highfive:
I entrust you to do this since you said youre running 2.3.6 but DONT DO THIS if you manage to get to Ice cream sandwich!!! We can never stop reminding people of this... DONT EVEN DARE to factory reset under settings on a stock Ice cream sandwich n7000..
londoneye said:
have you updated the kies? use latest version of kies to update it should work.
Click to expand...
Click to collapse
+1
This method should work if your phone is still a "virgin"
londoneye said:
have you updated the kies? use latest version of kies to update it should work.
Click to expand...
Click to collapse
Yeah, according to Kies it is the updated version, and i also updated a galaxy s2 with it to ICS the other day...
Will going into recovery mode then factory resetting it work ?
thanks for your help,
Nozz.
Just factory resetted it, and once again it is coming up with it saying it is not possible tp update Via Kies :/
And Kies is fully updated
Also another thing i forgot to mention, the phone wants an update has it says new firmware is available through downloading from the phone then installing that way, however when i try this, it all goes okay, reboots, comes up with the little andriod symbol then it stops at roughly 20%, reboots and says it was unsuccessful, try updating via samsung kies.
thinking of just getting rid of it, but it's a contract.... Sigh.
nozz.
somebody made a program that you can use instead of KIES, it is called Checkfus.
google for it, or search the forum, i am sure you will find it.
Nozz360 said:
Also another thing i forgot to mention, the phone wants an update has it says new firmware is available through downloading from the phone then installing that way, however when i try this, it all goes okay, reboots, comes up with the little andriod symbol then it stops at roughly 20%, reboots and says it was unsuccessful, try updating via samsung kies.
thinking of just getting rid of it, but it's a contract.... Sigh.
nozz.
Click to expand...
Click to collapse
Hi there,
I would suggest not to update more on Kies as Kies sometimes KIES(OTA OR the PC one) is quite not more reliable sometimes, sometimes you can upgrade sometimes you can't.(Just like a woman on her monthly periods )
Anyway, I would you recommend by just flashing it thru PC ODIN. Download your stock ICS software from this page -> www.samfirmware.com and look for the firmware on your region. Flash it and you should be good to go.
:good:
i'm quite new to flashing phones, i've flashed computer motherboard bios, but i can get inside them and change the mobo if it goes wrong however i cannot do that with a phone :/
Which one is safe for my phone, considering it's current build etc?
Advice would be appreciated.
I can't seem to find firmware that is suited for my PDA, CSC and Phone codes... Or will any UK firmware work?
Nozz.
Nozz360 said:
i'm quite new to flashing phones, i've flashed computer motherboard bios, but i can get inside them and change the mobo if it goes wrong however i cannot do that with a phone :/
Which one is safe for my phone, considering it's current build etc?
Advice would be appreciated.
I can't seem to find firmware that is suited for my PDA, CSC and Phone codes... Or will any UK firmware work?
Nozz.
Click to expand...
Click to collapse
Here you go bud ->http://forum.xda-developers.com/showthread.php?t=1424997 (courtesy of Doc Ketan, of course)
If you narrow down a bit, there's a firmware for UK there(Carphone Warehouse to be exact)
According to CheckFus there is no such ICS update for my specific phone, aka pda/phone/csc.... hmm... and also i can't seem to find any roms for my specific phone either...
I really don't know what to do now
Could someone take alook at my numbers in my first post and help me, as i'm pretty much at the end of my tether with this phone
i'll relist my phones information:
PDA: N7000XXLA6
PHONE: N7000XXLPT
CSC: N7000XEULP4
Build Info: Friday, January 20 05:38:08 KST 2012
That build info looks slightly dodgy considering this is supposed to uk phone, and i'm pretty sure UK gingerbread didn't come out at that point... hmmm.. got me thinking.
anyhow
Thanks,
Nozz

[Q] Updating AT&T S4 Active to Android 4.3+

Hello,
in my company we are developing an android app. The lowest android version this app supports is android 4.3.
The company bought several testing devices including a AT&T branded Samsung Galaxy S4 Active. With Android 4.2.2 (Buid Number: JDQ39.I9295UCUAMF3)
I tried it for a while now, but I can't get the OTA Update to work. It says "Software update interrupted. Try again in 24 hours".
I can bypass the 24h lock by changing the date of the phone. But even after ~30 tries the phone is not updating.
There is no SIM Card in the phone. Is a AT&T SIM Card needed to update the device? I am not able to get one, because I am located in Germany.
Can I update the phone manually with Kies or something?
I don't have admin right on my machine so I need to know what to do, before I contact the admin to install a required software.
Could a blocked port be an issue? I do have access to the internet, but if Samsung (or AT&T) uses some non standard port, my company could be blocking it.
(Root is not an option.)
Kind regards
Cliff
Cliff666 said:
Hello,
in my company we are developing an android app. The lowest android version this app supports is android 4.3.
The company bought several testing devices including a AT&T branded Samsung Galaxy S4 Active. With Android 4.2.2 (Buid Number: JDQ39.I9295UCUAMF3)
I tried it for a while now, but I can't get the OTA Update to work. It says "Software update interrupted. Try again in 24 hours".
I can bypass the 24h lock by changing the date of the phone. But even after ~30 tries the phone is not updating.
There is no SIM Card in the phone. Is a AT&T SIM Card needed to update the device? I am not able to get one, because I am located in Germany.
Can I update the phone manually with Kies or something?
I don't have admin right on my machine so I need to know what to do, before I contact the admin to install a required software.
Could a blocked port be an issue? I do have access to the internet, but if Samsung (or AT&T) uses some non standard port, my company could be blocking it.
(Root is not an option.)
Kind regards
Cliff
Click to expand...
Click to collapse
Hi Cliff. I can't say for sure, but my guess is you can't access the OTA because you're not in the right region (someone correct me if I'm wrong). As far as I know, you shouldn't need a SIM to update, again could be wrong. More importantly, there are other ways to update. You could probably try Kies, but I wouldn't recommend it, it seems like users always have issues with Kies. I would strongly recommend you try updating the phone with Odin, a tool by Samsung that let's you change around your phone's firmware (among other things) when the phone is in download mode.
There is an exhaustive guide linked to here that thoroughly explains how to go from any version of android (official, for this phone) to any other version. In simpler terms, that link shows you how to manually update, which is what I think you're looking for. Also the files you'll need to download are located here. Hope I've helped, and good luck updating! :good:
Oh, just re-read your caveats: you almost certainly don't need a SIM for Odin to work, and you definitely don't need root either.
thisisapoorusernamechoice said:
Hi Cliff. I can't say for sure, but my guess is you can't access the OTA because you're not in the right region (someone correct me if I'm wrong). As far as I know, you shouldn't need a SIM to update, again could be wrong. More importantly, there are other ways to update. You could probably try Kies, but I wouldn't recommend it, it seems like users always have issues with Kies. I would strongly recommend you try updating the phone with Odin, a tool by Samsung that let's you change around your phone's firmware (among other things) when the phone is in download mode.
There is an exhaustive guide linked to here that thoroughly explains how to go from any version of android (official, for this phone) to any other version. In simpler terms, that link shows you how to manually update, which is what I think you're looking for. Also the files you'll need to download are located here. Hope I've helped, and good luck updating! :good:
Oh, just re-read your caveats: you almost certainly don't need a SIM for Odin to work, and you definitely don't need root either.
Click to expand...
Click to collapse
Thank you for your answer. Yes, maybe AT&T does region lock the update -.-
I've used Odin on my old Galaxy S2 some years ago.
I'll have a look into it and decide if this is the way to go.
Odin will do it as long as there are full install files for you to use.
Cliff666 said:
Thank you for your answer. Yes, maybe AT&T does region lock the update -.-
I've used Odin on my old Galaxy S2 some years ago.
I'll have a look into it and decide if this is the way to go.
Click to expand...
Click to collapse
You need an AT&T SIM card in the phone in order to install AT&T OTA updates. You can't use Kies to update because AT&T won't let Samsung post AT&T firmware on Kies. So your only option is to use Odin and the guide posted above.

Categories

Resources