[Q] PLS Help: Warranty safe Firmware settings - Galaxy S I9000 Q&A, Help & Troubleshooting

I am going to return my Galaxy Samsung S to get a refund - it's originally from Belgium and it has printed on the back - Samsung - With google tm - Movistar.
What firmware settings do i have to have to be able for them to accept my phone under it's warranty and to give me a refund or repair the phone.
I flashed to every opp system and kernel I could ... and none of them worked ... please could someone who has a phone from Belgium tell me their settings?? so i can flash them back
This would be a great help.
I also suggest that the settings i have now are the best - most stable firmware settings - and they are:
Firmware: 2.2.1
Baseband: I9000XXJPU
Kernel: 2.6.32.9 hardcore (AT) speedmod-k13c-500hz #24
Build: FROYO - XXJPU
THANKS SO MUCH
(i can't post this as apparently i have outside links in my post - clearly you can see your auto link checking software in this forum is wrong)

What is wrong with your phone in the first place?

Oh well - it freezes every 5 minutes
then it started to have kernel panics every 5 minutes after upgrading to ginerbread
then i went back to 2.2.1 and it's only freezing every 10 minutes
it would freeze when ever i opened any task for the first time ... and also randomly ...
it have been stuck in boot up loops
sometimes the screen just goes blank with no response
the first time it froze was when i was trying to write a text message ... and the phone would immediately just crash ...
perhaps it's me! i don't know but i've tried every setup i know ... and nothing was good enough to call my phone a usable functioning piece of electronics

this gets said way too many times.
the way to fix a broken phone, is a firmware with all 3 files, 512PIT and re-partition checked.
guaranteed to fix you up

azzledazzle said:
this gets said way too many times.
the way to fix a broken phone, is a firmware with all 3 files, 512PIT and re-partition checked.
guaranteed to fix you up
Click to expand...
Click to collapse
Thanks this is great - but yes i have tried this ... and it didn't change anything
however what i need to know ... is what firmware settings will be accepted by the belgian supplier so that they will not disagree to fix my phone (basically replace it)
out of interest - i also noted that it doesn't happen when the sim card is not in .... however what use is a phone without a sim card

Related

[Q] Phone stuck in reboot loop.

So my brand new 7 day old vibrant is not working now. yesterday i was surfing the droid store, and looking for new apps, and installed a text editor, afterwards i made a text file. and saved it, that's when things went awry, I got a force close message, so i figured no big deal, i'll just reboot the phone. Well after cycling the power, now all i get is the initial splash screen saying samsung galaxy s gt-i9000m and it blanks out, then continues an endless loop. Only way to stop it is to pull the battery. the 3 button combo for force downloading works, but the 3button combo to get the recovery menu doesnt.
Question is can my phone be fixed? is it possible to recover the data ie pics/videos i had on it? or is it borked and i need to take it to exchange it.
Technical information
Virgin Mobile Canada gt-i9000m
Hardware Revision 10.11
running Froyo from box, jp6 i believe was the version.
any help/insight you can offer would be appriciated.
I hope i didnt get one with a bad internal SD card.
i doubt that the app you downloaded had anything to do with it. I hade the same prob. kept rebooting, 3button download mode works. 3 button recovery mode didnt, you need to call bell and get it sent away basically.
out of curiosity, did you do a big file dump onto your phone prior to the dead phone issue? like put on a ton of music or movies or images?
call bell. good luck. i am still waiting for mine.
haha.. don't worry!
just reflash using Odin. for details check this out...
http://androidspin.com/2010/08/09/h...oidSPIN+|+Your+No.1+source+for+Android+news.)
oh yeah, i forgot to mention i tried that too.no go!
SD card fail. You're done.
Your Internal SD Card has failed like many other Bell Phones. Use the Search option to find for possible solutions.
Try downloading a JH2 which includes SBL and flash it (stock 2.1 for your i9000M). I believe you should also check the "Phone Bootloader Update" in Odin.
http://www.multiupload.com/EZF1IEZ34H
If that doesn't work, call it in to Bell and do me a fav and report this failure in the i9000M hardware fail poll. This is the first 10.11 fail I've seen.
Good luck.
Well after searching all over the forums, and finding some similar situations and methods used to correct them.
I've flashed my phone probably 12 times, today and nomatter whatrevision or options i use with odin, it always hangs, in some cases, I'd get past the gt-i9000m black screen, to the galaxy s splash screen, but not past there, i9000ugjh2 seems to get me the furthest along @ the boot screen.
Anyone looking to reflash to a different version, before returning i suggest using the i9000ugjh2 image since it resets the model number to gt-i9000m which, maybe be changed by some of the other firmwares/roms
anyways back to the store tomorrow, since i got snowed in today.
Good luck to anyone else, I will post information on the new hardware tomorrow, If it's 10.11 again i'll have to try and force a failure. But we'll see what we see.
This guy seemed to have been lucky and got is supposed dead I9000m working again. Here's his procedure:
http://forum.xda-developers.com/showthread.php?t=905975
Worth a shot.
update
I received my new handset yesterday, it's another 10.11
I'm going to be treating it with kid gloves for the next few days while I'm at work.
Once I get home I will again begin taxing/loading the internal memory with a large amount of data to test it's stability.
New phone details,
Virgin mobile canada (AKA Bell canada)
Hardware 10.11
Model GT-I9000M
Firmware 2.2
Baseband version I9000UGJL2
Kernel Version 2.6.32.9 - [email protected] #3
Build number FROYO.UGJL2
As for his guide, My previous phone was unable to enter recovery mode, not until i flashed the nutz outta it.
even then his guide was unable to achieve usable results.
i got the same problem , my Phone stuck in reboot loop . its happen when i use some voodoo apps in the market that change the screen i think.
i brought my phone from malaysia.
my Firmware DXJPE.

[Q] Only one soft / Signal without sim card

Hi forum
I have a very unusual problem with SGS. Well, from the beginning.
My mobile operator, has given me the SGS (with Android 2.2).
So I decided to upgrade to version 2.2.1, possibly Cyanomod / draky's. I plugged the phone to the PC and step by step according to the tutorial:
- downloaded Odin3 1.7
- pitting 512
- Keis with drivers
- And of course the latest 2.2.1 I9000XWJS3
Fleshed this soft thanks odin. Telephone, everything installed, Odin wrote "PASS" and there was a reboot. There was a samsung logo and then black screen and light vibration from time to time. Zero response.
I learned about the "Recovery Mode " did reset the cache, etc. Reboot ... NOTHING. So stweirdziƂem that you need to return to the previous firmware ... Now all my flash's finished in the same way: a black screen and a slight vibration.
I tried reaaaaly a lot of versions and nothing. I tried it once cyanonmod, darky's mod. And nothing. Somewhere on this forum, I found versions: Froyo (2.2) That does not bricks. Worked.
But, this is the ONLY version that can be installed and running.
But it is not so big problem. The problem arises when I put the SIM card. Phone lying on the table (in a place where I always had coverage in other phones) to lose coverage. To one or zero bars. Neither I can not get anywhere else, nor to call me you can not reach you.
But when I stretch out my SIM card, coverage remains. At least in the form of dashes. Of course, nowhere is this possible calling, but the phone displays one or sometimes four lines.
My question:
Could this be the fault of soft? What should I do if I can not change it? Return to factory settings is not possible because they get a black screen and a slight vibration. I have tried:
- changing soft to 2.2.1
- 3 button recovery
- flashed with the kernel
- w8 for over an hour! to give SGS time to install everything right
- reupdating soft for hundreds ways
- read all FAQs on forums...
I didn't "root"
althou I tried to ":update.zip" in recovery mode but it gives only new errors.
Anyone have any idea? Or I am doomed for Samsung service?
thx
And how about getting back to factory soft. I mean, the soft that come to me with the new phone?
Or these soft has been overwritten by the all flashe's I tried to install, and is unbeckupable?
maybe this will solve the signal problem?
swiechu said:
And how about getting back to factory soft. I mean, the soft that come to me with the new phone?
Not unless you saved it .
Or these soft has been overwritten by the all flashe's I tried to install, and is unbeckupable?
But off course .
http://forum.xda-developers.com/showthread.php?t=818556
Flash via Odin to Eclair then update to 2.2 via Kies and you should get original as the download .
jje
Click to expand...
Click to collapse
thx, I will try it tooday
JJEgan said:
swiechu said:
And how about getting back to factory soft. I mean, the soft that come to me with the new phone?
Not unless you saved it .
Or these soft has been overwritten by the all flashe's I tried to install, and is unbeckupable?
But off course .
http://forum.xda-developers.com/showthread.php?t=818556
Flash via Odin to Eclair then update to 2.2 via Kies and you should get original as the download .
jje
Click to expand...
Click to collapse
I downgrade to 2.1-upadate1 (I9000XXJM4). Still no signal with SIM card. But when I try to upgrade to 2.2 via Kies 2.0 and didn't have info about possible upgrade to 2.2. So I downloaded old version of Kies (1.5.1) and try to again with regedit tweek and now I get information: "This software verios you cannot update"
Tryied "Test mode ON" "Test mode OFF", still nothing....
Click to expand...
Click to collapse
You will have to continue and flash the stock rom 2,2,1 as per the posted link .
Sim card have you checked it works on another phone .
jje
Yes SIM card is working perfectly on another iphone 3gs and nokia c5-00.
Now I don't have time to do all these steps, but tomorrow I will contact my operator to service it or maybe change to new one.
And do you think the signal problem might be the soft foulty? I think it is somenthink more...
And thank you for all the help.

[Q] how to upgrade from eclair to froyo (this version of device cannot be upgraded)

I bought my SGS in the Middle East, particularly in Bahrain. Can someone please help me on how to upgrade my SGS. I already have samsung kies and this is what appears when i connect from keis and try to upgrade my phone:
This version of the device cannot be updated.
current firmware version: PDA:JG8 / PHONE:JG2 / CSC:JG9 (CPW)
OS Eclair 2.1
I really don't know what the problem is. I don't have the android market app, I can't use my video call for skype and yahoo messenger, and this really sucks. I searched for solutions, and i'd really like to try to flash and unroot, but i don't like to brick my phone if something goes wrong, because this is what happened the last time i tried to fix my phone with this method:
1- Backup all your files and apps (after this, the device will be just like new)
2- Set the watch to 24 hours mode
3- Dial this code: *#272*HHMM* (HH for the current Hour MM for the current min)
4- Then chose xsg
I get the market app and it works but my problem is, my simcard isn't working at all; I cant send sms or call, so in short, the network simcard became unavailable. Luckily, i still have warranty, so i returned it to the shop were I bought it, and they can't fix it unless they pay 30$ for the repair, so they just replaced it with a new one.
please help , thanks in advance
This version of the device cannot be updated.
current firmware version: PDA:JG8 / PHONE:JG2 / CSC:JG9 (CPW)
OS Eclair 2.1
Usually means the phones network has not yet upgraded to Froyo .
Alternative is to flash your phone via Odin .
Or rom Kitchin
http://forum.xda-developers.com/showthread.php?t=817703
http://forum.xda-developers.com/showthread.php?t=810686
http://forum.xda-developers.com/showthread.php?t=846913
http://forum.xda-developers.com/showthread.php?t=723596
jje
thanks, i already flash it with odin and im really happy with the result
I suggest tol all other noobs like me, just make a little more research b4 you ask, its already available in the internet,

Galaxy S i9000 - Upgrading & KIES - Not happening!

Hey all,
I have a wierd problem - and was wondering if you can help. I have tried searching the forums for a solution - but could not find one (maybe I didn;t look hard enough) - so apologies...
My Galaxy S (GT-I9000) has the following spec:
Firmware - 2.1-Update1
BaseBand - i9000XXJF3
Kernal - 2.6.29 root SE-S602 #2
Build - Eclair
Over time have had the usual problem os on-going lag etc etc. But recently I started having the problem where the built in Media player and You Tube application refused to recognise and play any media. Trying to play DivX file comes back with error message: "Sorry this video cannot be played" - and the same for You Tube. The only solution is to restart the phone.
I tried to connect it to KIES to upgrade but it wouldn't have it - so after speaking to T-Mobile tech(?) ended up doing a factory reset. Now when trying to connect onto KIES - the connection is made but thats it. No indication of upgraded firmware etc etc. This I tried on several computers at work and the same result. Than when I tried on my own computer at home - it came back with the following message:
"This version of the device cannot be updated"
T-mobile have advised its a Samsung problem and have refused to help any further - and Samsung have not replied at all.
Any ideas guys?
Also - will installing Darkys ROM be a good move? Will it retain the TouchWiz UI or will that be blitzed?
Many Thanks guys
~LK~
well kies will only update the firmware you currently have...
example, if your phone is t mobile firmware, then tmobile will have to release a updated version, with their add-ons included, so i dont think its a samsung problem as we are almost upto 2.3.3 never mind 2.2 lol.
if you really want to up date your firmware you are going to have to do this 'unofficially' using www.samfirmware.com - to get the latest firmware release.
if you want to go custom, be sure to read up properly and know the ins and outs incase you have troubles,
the choice of which rom to go for is entirely down to you, we cannot say 'this rom is better than that rom'
so whatever you decide to do, be sure to read the instructions that come with it exactly as they are shown
Hi azzledazzle
I have spoken to t-mobile, and they inform me that they are shipping out 2.2 - and soon to be 2.3. Where the phone is not communicating with KIES or KIES not reporting any new firmware or KIES not updating IS a problem for SAMSUNG and not them. So you see I'm kinda stuck.
I can get the latest Samsung firmware from samfirmware.com but to be honest the long winded procedure of using ODIN etc kinda scares me. I knwo for many this is a simply process, but I don;t want to get it wrong.
Just one question - whats the advantage of having custom over original?
Thanks
~LK~
kies works for a lot of us, so i dont know whats happening where you are
anyway ODIN is relatively simple, providing you follow instrctions, in total there is only about 10 steps and you have nice new firmware
anyway there are many advantages over custom rom / original roms/
custom roms give you more speed, many more features, allow you to customise every feature of the phone and get rid of 'network branded' stuff.
you can also install funky fresh themes and completely revolutionise your device
but there are also downsides, Its possible to brick the phone (this can be fixed 99% of time), you lose your warranty, (this can be replaced by going back to stock) and i cant think of anymore lol
there are more positives than negatives, but it lies down to you..
not every android user runs a custom rom ya know lol
Hahah - so Custom wins
I'm in London - just down south of you...so not sure why KIES is saying that this device cannot be updated???
If I put a custom rom onto the device - would I be able to upgrade it to offical Gingerbread(when it comes out) with ease - or will it pose a problem?
~LK~
no, kies will not detect a custom rom
but however you can flash back to a stock rom and then it will find it
Kies requires two critical components to be in place to update .
One is a later version of the firmware to have been uploaded by the phone provider . In your case TMobile they have uploaded 2.2 or 2.2.1 you can proceed .
TMobile in your post say shipping out does that actually mean its on the servers .
Two Kies requires the correct identification of product code hardware id etc to locate the new TMobile firmware if thats not correct it fails .That usually apply to custom/stock roms .
If you have an untouched TMobile phone and cannot update its nothing to do with Samsung Kies and TMobile are your update path not Samsung .
jje
Hi
Just been on the phone to T-mob...and GAWD my ears burning...but anyway - their "THIRD LINE" support person told me that they do updates OTA, and if my phone is not getting it than there must be somethign wrong with the handset. He has advised me to either visit a local Samsung repair centre to have the phone flashed with the latest firmware or T-mob can do a handset swap...
lets see what the repair centre say - and how long it'll take.
Guys - rather than taking it to teh Repair centre - is flashing a new firmware something I can do? Is it easy?
Many Thanks for all your help.
~LK~
it is somewhat easy providing you take your time and read the instructions 2 - 3 times.
flashing your new firmware will take less than 30mins to download the required software / firmware - read the instructions and flash... it will take longer than this to send it to samsung.
BUT and this is a big BUT (like my gf's ) if you feel confused or scared... DO NOT DO IT, the chances of getting it wrong under pressure is high and if you dont know how to fix a brick, your doomed.
if in doubt..... do nout

Need some advice with i9000M

Hi guys, I know I need to make this short but I want it to be clear anyway. This is crazy I wanted nothing to do with smartphones 3-4 days ago because all the carriers rip us off with huge bills to get them. But low and behold when my cheap flip phone died after 3 years of loyal daily work a friend of mine offered me his Galaxy S i9000m for a good price. Started playing with the device and having a strong software/computer background started having a lot of fun with all the applications and was amazed with the possibilities (Networking, ipcam whatever) that just kept multiplying until I fell upon applications that needed something called gingerbread... Anyways I can tell you I learned a ****load in 48hours...
So I installed Samsung Kies, it found me the update and put it on for me.. (2.3.3 Gingerbread) then the nightmare started. The phone would boot, and would randomly reboot a random number of times until it could finally stay on and this could last from 2-30 minutes. So I thought, I'll just do a factory reset, to realise that its "STUCK" in 2.3.3 once its updated no going back to 2.1 or 2.2 easily.
Started looking around for ways to downgrade, and EVERY SINGLE LINK redirects to these 'mass download' sites that end up saying the firmwares were taken down for copyright issues. So desperate to find something, I fell upon a multiple CSC FROYO 2.2 firmware for the i9000 and was able to flash that in download mode the phone worked fine, except for me being very curious about the fact that I lost the "M" in my model description...
So started reading this thread(Mostly because I had already realised that with this non i9000m rom I had lost the 3 button DOWNLOAD MODE which i Had before) **** : http://androidforums.com/galaxy-s-a...flashing-darky-v9-gt-i9000m-minimal-risk.html
Got it rooted, got clockwork on, never managed to get the voodoo kernel working had errors in CWM.. so I was ready to give up until my eyes caught the
"*#*#2663#*#*
Then click Touch key FW update"
Which I thought would be neat to try.
NIGHTMARE, now BACK and MENU are dead, I understand that this is because I am running a non i9000m ROM and that updating the firmware rendered them unusable.
I came accross a post : http://forum.xda-developers.com/showthread.php?t=869492
Where this problem is adressed, I pretty much understand everything that should be done to get this back on its feet (right now the phone is still working I can use it at least 75% of its functions work except no back and menu)
Where I need your help : I'm not too sure how to attack this the right way, since I can't get into download mode I understand flashing is now more complicated to accomplish and now that I know that I need a i9000m firmware how can I find that...
Sorry for the long post I know I'm a noob here but I wanted to prove I had done all my homework to get where I'm at now seeking help from you guys!
Thanks a lot
Mat
By the way : Galaxy S GT i9000m currently on a 2.2 i9000 rom, my carrier is BELL. (Canada)
So there's no way of updating to 2.3.3 using Kies?
The only thing I can think of is getting a USB jig from ebay, which makes the i9000 go to download mode instantly. Good luck!
Alright, so I used CHECK FUS, and was able to get the i9000m stock BELL firmware YAY
now the help I need is to flash it correctly and find a way to get past the no download mode problem, would be very appreciated,
thanks guys
No, similar minds Sepharite, I also thought of redoing the Kies method, and then going back again if I needed to but now Samsung Kies says "Your device does not support firmware updates through Kies" Wow.. useful app, a samsung native app can't even detect it's own fricking hardware.
Thanks
UPdate : Was able to restore the 3 button "DOWNLOAD MODE" with a little tutorial online. Now I tried flashing my i9000m with ODIN, it flashed all the way and I get a i9000M logo now but it gets to the splash S logo and keeps rebooting never gets into the actual android setup is there something I did wrong?
In Odin all I put was the "BELL i19000m stock ROM" under PDA and wrote it. The device rebooted after flash but there still seems to be something I haven't done right.
Thanks guys
Please help guys, I know some of you out there have got this stuff nailed down!
Did you flash with a 1 file ROM or a 3 file ROM?
Using the UGKG3 ROM that you can fine here:
http://forum.xda-developers.com/showthread.php?t=1102881
Place the 3 files in their respective places (PDA, PHONE, CSC), for the PIT file, select the 512 pit file that should have come with ODIN, connect the phone, wait for ID:COM to turn yellow, and press Start.
That should get you going again. You may get apps that force close, so you'll need to delete the apps data and then reinstall them.
Hey thanks a lot man ya my flash was a SINGLE FILE, I bricked it yesterday trying to flash a different ROM since I had nothing to lose, I just got it working again on the old 9000 ****ty version that my back and menu keys don't work...
Now for some reason the USB JIG doesn'T work anymore after a couple of uses... could something have been damaged by doing it many times?
And your original roms section they are all unavailable due to copyright did you check the links before sending them?
When you say get the stock roms, I was able to get the UGKG3 file, but what about the versions? When I look at the north american section of the 2.2 version
UGKC1/UGKC1/BMCKC1/Sbl
UGJL2/UGJL2/BMCJL2/Sbl
UGJK3/UGJK3/BMCJK3
which one of the three suits me?
Thanks for your help, and if I get this running and go back and update my touch key firmwares with the right "Vibrant / 9000M" roms I should get them working again?
PS : I'm also very preoccupied by the fact that the USB JIG fix doesn'T seem to pop download mode anymore because this version of the ROM that I have has Download mode not working with the 3 button method. :S I wonder whats going on, but basically if I get your ROMS working the first time It'll fix everything but if it crashes then I lose the galaxy haha
Not sure why the USB jig doesn't work anymore. I have a couple and have only tested them on my phone to make sure they work, but they did not work on a Galaxy S II that I tried it on.
I just checked and the download link for the UGKG3 ROM at multiupload (downloading from multiupload), still works (you need to enter the captcha phrase).
The site megaupload was shut down by the US gov't, so that one won't work.
EDIT: UGKC1/UGKC1/BMCKC1/Sbl is the latest Froyo release from Bell. That's what mine and my wife's gt-i9000m phones came with.
She's still running it on hers.
Ok sorry for all these posts, basically when you said UGKG3 you want me to get the 2.3.3 ROM on ? Is that right? What if I Want to put on 2.2 to be sure I have no trouble with it since I'm in all this mess because the Kies update to Gingerbread had my phone in a bad state.
Thanks a lot by the way!
Sorry your post refreshed right after I did mine. Alright cool so I'll try the one you say your wife is running, I had made myself a JIG with a stock Samsung wire, it was working fine with a 300K resistor and I decided to solder it on and then it stopped working after that.... maybe the actual "usb plug" is damaged from the soldering heat I guess I'd have to try another wire, but anyway I'll try to download the 2.2 I just got the UGKG3 3 FILE rom downloaded one of the links did work!
But I'm a little worried about 2.3.3
I'll try to see if i can download the 2.2 first.
I mean basically... these roms shouldn't jam during transfer i Guess
One other thing I see different confusing information, is it important for me to click 'update bootloader" with these stock roms since these files contain an 'SBL' ? Because both times I bricked it was with an "update bootloader checked" firmware update trying to put the ARIES 3 button method fix as a boot.bin and sbl.bin
Fanks..
Files with SBL in the name already have the bootloader included in the PDA file, so "update bootloader" should NOT be checked.
That reassures me, because the only times it did jammed was when the bootloader was checked! THanks a lot blackrose i'll go out and buy another usb cable because I destroyed mine making my JIG. And I'll try yours out. I was reading a lot on another thread and found this one guy who flashed the JL2 one to save his keys instead of the C1 you said your wife was running, whats the main difference between those two and which one should I start with?
Update : I got a new wire, flashed the KC1 version of the firmware, everything goes fine, I did a repartition with the 512 PIT, it reboots the phone, loads all files in a prompt in yellow and there are no errors that appear, the phone reboots after writing 'successful update' and then goes to the galaxy logo and jams there and does the ONE vibrate, PAUSE, 2 vibrate on a black screen forever. The advantage of having successfully flashed a 9000M ROM allows me to have access to my DOWNLOAD MODE 3 button method, but ever since I flashed that 2.2 i9000 XXJP2 (seems its a euro version) off a torrent I found on the web (When I was desperate to find a functioning 2.2 working version) it seems as though it doesn'T want to boot with any other rom than that one, because all the 9000M roms that I've tried so far flash correctly, and the logo actually changed from i9000 to i9000M on the startup, but they just don't boot.. what could be missing it doesn't seem to be much???
Thanks Mat
If any of this can help, the device was rooted, I was following the darky's mod i9000M guide so I had previously installed the CLOCKWORK MOD and that's as far as I got because my eyes caught the FIRMWARE TOUCH KEY UPDATE which ruined my keys.
Could any of this have screwed something that stops my other roms from booting?
Thanks guys I really want to get this phone up and working again as I don't have much money and am afraid I'll have to cancel with my phone company if I just can'T get this running. I am also willing to make a significant donation to whoever can help me.
You in Canada right? Where abouts?
Sent from my GT-I9000 using xda premium
Quebec province
Alright, if this can help anybody my whole problme is solved.
I flashed the ****JL2**** the KC1 did not boot, the JL2 did.
Once inside JL2, I was able to update my TOUCH KEY FIRMWARE *#*#2663#*#* and everything went back to normal
I have no idea why the KC1 does not work, bugs me out.

Categories

Resources