Database Develop

Bricked phone, can't access download mode. Please HELP!

OK So,
I recieved a Galaxy S today, and having some experience with a HTC Desire HD I knew how rooting/flashing roms work. But this is different.
I have flashed twice so far. Once trying to get to CM7 MIUI but that failed, leaving me in a recovery loop. So I panicked. I then used someones one click odin restore on these forums, however being the idiot I am didn't read that that was vibrant firmware and not i9000 firmware. Download mode was working 100% before I did this, and now I can't get it to work for the life of me. Can someone please help? I am stuck at the AT&T boot logo and I can't do anything. I have the correct firmware from my carrier, I know how to flash it back to stock, but I can't get into the freaking download mode. Why is this? Is it disabled for good?
Please don't tell me my phone is a brick now....

Try the jig method. You can make your own or plenty on eBay. But I think you are in the 'not good ' realm. But usually you don't get to the boot screen either so there is some hope.
Sent from my GT-I9000M using XDA Premium App

I've bought a jib off ebay so I will see if that works. What I am trying to understand is why would doing what I did somehow disable download mode? That makes no sense to me. And the phone isn't fully bricked since the boot screen comes up.

Download mode is software based and you flashed new software on the wrong hardware. It's on the bootloader I believe. The jig tries to get it forced as I think there is a backup bootloader but not at all sure on the details.
Sent from my GT-I9000M using XDA Premium App

I see. Well I will try the jig and see what happens. If that doesn't work I will send back to Samsung and blame Kies for the problem. Which will be a bit sus since I have an at&t bootlogo and I live in Australia but oh well
One other question I have is if I do get into download mode, I have all the stock firmware files from SAMfirmware, however the files are only a pda file and a 512 pit file. I was under the impression I needed a csc file and something else? Or is it all included in the .tar PDA file?
Thank you for all your help I really appreciate it!

Usually what you need is in the tar for the pda spot. The others are more for mix and match. Just be aware that some firmware does not have all the files as they aren't meant to be flashed with pit. You will want to flash a pit so you'll need a complete one. My stock has no dbdata.rfs for example and if you use a pit then you get a mounting error as no partition is created.
Sent from my GT-I9000M using XDA Premium App

I had a look inside the .tar file which is for I9000DTJP5 (exact firmware that I had on stock) and there is no dbdata.rfs like you said. So you are saying this firmware that I got from samfirmware.com is incomplete? And if I flash with the PDA + 512.pit I will get mounting errors? So do I just flash the PDA firmware by itself and tick re-partition?
Thanks.
PS I used this http://forum.xda-developers.com/showthread.php?t=731989
So I'm guessing this changed my kernal and modem? I beleive the kernel does not come included in the pda .tar... or does it?

The pda will have the zImage in it (which is the kernel).
But try to find one with the dbdata.rfs file. For some reason I think jpy is one people use (anyone else following this thread). There are some roms that people describe as 'working everytime' and I think that its because they are complete roms. I'd also look at ezboot thread as you will want to make sure that any capivate bootloader gets removed and updated with an i9000 one but stock roms usually have the bootloader I believe.
Have you (out of curiousity) tried the captivate download sequence (vol down and power - I think - maybe while battery is inserted)?
Also might try the ADB method of prompting download for captivate.

Yeah none of samfirmware comes with the dbdata.rfs file. Other option would be to flash to something like Darky's rom. I must have screwed the boot loader since I came from froyo > CM7 bootloader and that's when things went wrong. What file removes & affects the bootloader from Odin?
Yes I've tried the captivate download mode which is Volume Down + Power like you said. ADB is impossible since the phone isn't operational.
So that easy one click odin that I used flashed the modem, the bootloader, and the rom. This is going to be hard to fix.
I need to use firmwares from my country... and JPU isn't listed under australia on samfirmware website

Well the bootloader for froyo and cm7 are the same but the problem was the file system was not (cm7 uses yaffs or something - not a linux person...) so you had to do a full flash with pit (and of course not with captivate rom in retrospect) which did screw up the bootloader and more.
You can also get a service (professional shops) called JTAG that opens up the phone and reflashes just the bootloader from point on the motherboard. Some information here on XDA. Its a specialized deep hardware fix but it solves even hard bricks that won't turn on (unless there is physical damage of course). Might cost $100 or so though.... Might be worth a search for local shops that do that.

found this post (and it references another thread).
http://forum.xda-developers.com/showthread.php?t=749641
But its not good news... These are from last year but it looks like people were hooped in similar situations though i think the JTAG method has been formalized since then.

OK! The Jig works!!!!!!!!!! SO happy. However I am facing the problem of flashing now. Odin gets stuck at cache.rfs for about 20 minutes until I disconnect the phone and try again.
The files I am using with a 512.pit with re-partition checked are...
Phone:MODEM_I9000DTJP3.tar.md5
PDA:CODE_I9000DTJP5.tar.md5
CSC:CSC_I9000XSAJP4.tar (my countries correct csc file)
Here is my log:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> Enter CS for MD5..
<ID:0/004> Check MD5.. Do not unplug the cable..
<ID:0/004> Please wait..
<ID:0/004> Checking MD5 finished Sucessfully..
<ID:0/004> Leave CS..
<ID:0/004> Enter CS for MD5..
<ID:0/004> Check MD5.. Do not unplug the cable..
<ID:0/004> Please wait..
<ID:0/004> Checking MD5 finished Sucessfully..
<ID:0/004> Leave CS..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> zImage
<ID:0/004> dbdata.rfs
<ID:0/004> factoryfs.rfs
<ID:0/004> param.lfs
<ID:0/004> modem.bin
<ID:0/004> cache.rfs
What am I doing wrong?
Thanks

Try another version of odin? Or another rom I've had bad versions of both.
Looks like more lines about md5 stuff than I recall too.
Sent from my GT-I9000M using XDA Premium App

Found the culprit... the csc file which I obtained from XDA was corrupt... so I used a different one. My phone is now up and running. I just want to say a big thanks for your time and advice. Thanks

Stuck at Sbl.bin

I recently upgraded from MIUI to WeUI, but decided I didn't like it.
So to get a fresh new start I tried flashing back to stock with Odin3 One-Click Downloader. However it froze so I pulled out the USB and tried again. Now I've been spending the last 6 hours looking up and trying different things like roger's, GB one clicks, etc.
My phone won't even start, but I can make it go into download mode with my USB jig. Only problem is that I keep freezing at Sbl.bin when using Odin.
Am I screwed or what?
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> Sbl.bin

You're going to end up hard bricking if you keep trying

b-eock said:
You're going to end up hard bricking if you keep trying
Click to expand...
Click to collapse
I think I already have. I mean it's not even turning on. Only time it turns on is when I stick my USB jig into it to go into download mode. But that's it. No 3-button either.

If it still turns on with a jig then your not hard bricked luckily
Sent from my SGH-I897 using xda premium

Try another package without bootloader. Remember to run odin as admin and use a mobo usb port.
Sent from my ICS powered Captivate using Tapatalk

read this thread then before you try and use odin again go get a stock package WITHOUT bootloaders, that way if it still looses connection you can't hard brick, good luck.
edit: ninja'd lol

Can't downgrade from XXLB2?

Hi, i tried to downgrade from XXLB2 to KJ1 with Odin, but it didn't work. NAND write error. Now i am stuck. What can i do?

Hi, where is download link of your new Rom ?
facepalms

Blackflip said:
Hi, i tried to downgrade from XXLB2 to KJ1 with Odin, but it didn't work. NAND write error. Now i am stuck. What can i do?
Click to expand...
Click to collapse
you can start by posting in the correct place... this should go in Q and A not development...
Here this may help you
http://forum.xda-developers.com/showthread.php?t=1318423
or maybe this might
http://forum.xda-developers.com/showthread.php?t=1321268

Moved To Q&A​
Please post all questions in the Q&A section​

sorry for posting in the wrong forum.
So i have tried everything:
- downloaded and tried flashing 2 different stock ROM's from Switzerland XXKK5 and XXLA4 with odin. no avail:
<ID:0/004> Firmware update start..
<ID:0/004> cache.img
<ID:0/004> NAND Write Start!!
<ID:0/004> factoryfs.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
tried installing the AbyssNotekernel42CWTouchOriginalLogo.tar
got into the menu and installed Superuser-3.0.6-efgh-signed.zip
but my SGN still won't boot.
Can someone PLEASE tell me what i am doing wrong?
I just want to go back to stock ROM now since this has been a rotten experience for me.
I know that my SGN is only Soft-bricked, i can still go into Download mode, but Odin will just not take any ROM that i throw at it.
Thank you for your help!

Would be really great if someone could help! Please!

anyone here?

I'm kinda having a similar issue. If i find a way around it I'll tell you.

Blackflip said:
sorry for posting in the wrong forum.
So i have tried everything:
- downloaded and tried flashing 2 different stock ROM's from Switzerland XXKK5 and XXLA4 with odin. no avail:
<ID:0/004> Firmware update start..
<ID:0/004> cache.img
<ID:0/004> NAND Write Start!!
<ID:0/004> factoryfs.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
tried installing the AbyssNotekernel42CWTouchOriginalLogo.tar
got into the menu and installed Superuser-3.0.6-efgh-signed.zip
but my SGN still won't boot.
Can someone PLEASE tell me what i am doing wrong?
I just want to go back to stock ROM now since this has been a rotten experience for me.
I know that my SGN is only Soft-bricked, i can still go into Download mode, but Odin will just not take any ROM that i throw at it.
Thank you for your help!
Click to expand...
Click to collapse
Right click odin and run as administrator
Sent from my GT-N7000 using xda premium

I finally found a way... I downloaded the 3 Part KJ1 Firmware (N7000OXAKJ1)
then i put into Odin (run as Admin of course)
- KERNEL_N7000XXKJ1_CL627135_REV02_eng_mid_ship.tar.md5
into the "Bootloader"
- MODEM_N7000XXKJ1_REV_05_CL1067428.tar.md5
into the "Phone"
- GT-N7000-MULTI-CSC-OXAKJ1.tar.md5
into "CSC"
and flashed my SGN.
Then i did it again but this time i also put the
- CODE_N7000XXKJ1_CL627135_REV02_user_low_ship.tar.md5
or the
- N7000XXKKA_N7000OXXKK5_N7000XXKK5_HOME.tar.md5
into "PDA"
finally my phone booted up again.
after that it was pretty straightforward with updating to ICS Stunner.

N7000 xxlb2 problem
how to root n7000 xxlb2? SuperUser will not install at all.
Can man say what or how to do it? i'll be pleased to hear from you guys.
Thx a lot.

How to restore stock

My rooted T-mobile Note did not like the OTA update it received today (hung at the samsung logo). I reflashed the rooted UVLG3 firmware image, following the instructions at http://androidlegend.com/how-to-root-t-mobile-galaxy-note-sgh-t879/. This worked, and I'm ignoring the OTA update for now.
I don't need root anymore, i didn't really use it anyways, I would like to get back to stock.
How do i get back to the stock/factory image? From http://forum.xda-developers.com/showthread.php?t=1837907, I see items B (T879-STOCK RECOVERY IMAGE) and D (T879-STOCK BOOT IMAGE). In ODIN, do I need to load one or both of these in one the sections (Bootloader, PDA, Phone, CSC, or UMS) and would i then hit the "Start" button?
Thanks for any help.

Just go to Samfirmware.com and download the tar file for the T879. Put it in the PDA section and start.
Sent from my SAMSUNG-SGH-I717 using xda premium

Thanks Charlie, that worked! In case any other newbie like me wants to know what to do, this is what i did:
Downloaded/installed Samsung Kies
Downloaded Odin 3.07 from www __ android __ gs
From samfirmware __ com, i searched for T879 and downloaded the file for "SGH-T879 USA (T-Mobile) 2013 January Android 4.0.4 T879UVMA1 T879TMBMA1". The ZIP file "T879UVMA1_T879TMBMA1_TMB.zip" has a large file called "HOME_T879UVMA1_CL892179_REV02_user_mid_ship.tar.md5", which I renamed to .tar
Powered off the phone, removed battery, connected USB cable to computer and phone, inserted battery, press power/vol-up/vol-down then hit vol-up to get into download mode
Started ODIN3 v3.07 (the box read 0:[COM4], message window read "<ID:0/004> Added!!")
Pressed PDA button, loaded the TAR file
Pressed START
Took about 4 minutes, then the green status bar finished, box above says RESET!, phone resets.
Message window:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> amss.bin
<ID:0/004> cache.img.ext4
<ID:0/004> mdm.bin
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
The phone automatically reset and started the boot sequence, took a few minutes to load updates, and everything was groovy again. When i connect the phone to Samsung Kies on my computer, it now reads "This is the latest firmware" (used to read something like "we don't what firmware is loaded").

How can i rooting the phone if i want to keep stock rom?
Do i have to do same as regular root?
Thank you.
Sent from my SGH-T879 using xda premium

I got it
Sent from my SAMSUNG-SGH-T879 using xda premium

bigape-revamped said:
Thanks Charlie, that worked! In case any other newbie like me wants to know what to do, this is what i did:
Downloaded/installed Samsung Kies
Downloaded Odin 3.07 from www __ android __ gs
From samfirmware __ com, i searched for T879 and downloaded the file for "SGH-T879 USA (T-Mobile) 2013 January Android 4.0.4 T879UVMA1 T879TMBMA1". The ZIP file "T879UVMA1_T879TMBMA1_TMB.zip" has a large file called "HOME_T879UVMA1_CL892179_REV02_user_mid_ship.tar.md5", which I renamed to .tar
Powered off the phone, removed battery, connected USB cable to computer and phone, inserted battery, press power/vol-up/vol-down then hit vol-up to get into download mode
Started ODIN3 v3.07 (the box read 0:[COM4], message window read "<ID:0/004> Added!!")
Pressed PDA button, loaded the TAR file
Pressed START
Took about 4 minutes, then the green status bar finished, box above says RESET!, phone resets.
Message window:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> amss.bin
<ID:0/004> cache.img.ext4
<ID:0/004> mdm.bin
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
The phone automatically reset and started the boot sequence, took a few minutes to load updates, and everything was groovy again. When i connect the phone to Samsung Kies on my computer, it now reads "This is the latest firmware" (used to read something like "we don't what firmware is loaded").
Click to expand...
Click to collapse
I did the same but the phone still hangs at the Samsung logo after I get the TMo Galaxy Note logo.
I had CyanogenMod on it with TWRP and tried to do a restore (bad idea) that's when it bricked.
I got a USB jig to get me to download mode so Odin would see it. All was installed just great but still the logo..

Just remember to flash the flash counter zip if u need to send it over to repairs with Samsung cus if they know ur phone is rooted they won't fix it cus rooting a device voids ur warranty... I flashcounter.zip everything I flash a rom... I usually flash that file last...
Sent from my SGH-T879 using xda premium

thanks all I just learn something from this:good:

Problem solved
JessSayin said:
I did the same but the phone still hangs at the Samsung logo after I get the TMo Galaxy Note logo.
I had CyanogenMod on it with TWRP and tried to do a restore (bad idea) that's when it bricked.
I got a USB jig to get me to download mode so Odin would see it. All was installed just great but still the logo..
Click to expand...
Click to collapse
Got it going. Had to jump on a Windows XP 32 bit PC to get the USB drivers to see the phone. Thanks for the help.
Running great on stock.

I have the update on my status bar but I'm wondering what did the update do for u? Can u post a screen shot of ur about phone info? Thnx
Sent from my SGH-T879 using xda premium

I'm curious, can I flash the stock everything of t879 on my at&t note? I have the i717 switched fully to t-mobile with twrp. I want the ota to upgrade from 4.04
Sent from my SGH-T879 using Tapatalk 2

JessSayin said:
I did the same but the phone still hangs at the Samsung logo after I get the TMo Galaxy Note logo.
I had CyanogenMod on it with TWRP and tried to do a restore (bad idea) that's when it bricked.
I got a USB jig to get me to download mode so Odin would see it. All was installed just great but still the logo..
Click to expand...
Click to collapse
I had to flash TWRP temporarily and wipe the phones emmc and flash the stock ROM again above instruction and worked. I guess before doing anything you should wipe/factory reset your phone first before flashing the stock ROM, this I can't test but just based on logical explanation.

My solution for being stuck on the Samsung logo
I know the last post was done a year earlier, but I thought I'd share this information I learned yesterday. After numerous flashing attempts My Note was stuck on the samsung logo.
I had soft bricked my Note by not clearing out the data on my phone. The previous post here gave me a clue and not being really good at this, I wasn't able to install and get TWRP to play nice with my non-working stock rom image. But I was still able to get the the Samsung Recovery and Download modes.
The working solution (borrowed from a post by andersbot on another thread) was:
1. Go to Recovery mode. Do a "clear cache" and next a "wipe data". Then reboot.
2. Go to Download mode and then connect to a XP PC and start up Odin. Be sure to use the latest Samsung USB drivers.
3. Flash with Odin using ther stock firmware downloaded from sammobile.com. Only tick the boxes for f.reset time and autoreboot (Odin default). Click PDA and load the downloaded file renamed with .tar at the end instead of .tar.md 5.
I dont know if this was the easiest way to clear the data on my SGH-T879, but it worked, and my Note started up correctly with the stock rom.

Please help, I hope its not dead :(

Hi guys,
I bought a S3 mini not so long ago. Full official, no root etc. One day my son launched a game then it crashed and rebooted. But its looping on the Galaxy S3 mini screen.
What I've tried:
-i8190wipe
-param
-restore with Kies
-flashed official rom with Odin
-flashed Lafleur service rom
I have Odin mode but no recovery, even if I flash a custom one. If i want to get to recovery, it freezes on the first screen (Galaxy S3 mini sign), bottom light flash once then its rebooting again.
I need to get it work, I really love it, please help me!

ricsi30 said:
Hi guys,
I bought a S3 mini not so long ago. Full official, no root etc. One day my son launched a game then it crashed and rebooted. But its looping on the Galaxy S3 mini screen.
What I've tried:
-i8190wipe
-param
-restore with Kies
-flashed official rom with Odin
-flashed Lafleur service rom
I have Odin mode but no recovery, even if I flash a custom one. If i want to get to recovery, it freezes on the first screen (Galaxy S3 mini sign), bottom light flash once then its rebooting again.
I need to get it work, I really love it, please help me!
Click to expand...
Click to collapse
Sounds like downloaded firmware corrupted or wrong version
Download original firmware that came with the device (model/region). Maybe hardware as you cannot flash a recovery. You tried TWRP recovery?

Try it https://www.androidfilehost.com/?fid=24499762636004166
is a full firmware (csc,original rom and pit file)
If your not 8190, look for yours here http://www.tsar3000.com/Joomla/inde...ader-csc-pit-files&catid=55:samsung&Itemid=82

Sidebandit said:
Sounds like downloaded firmware corrupted or wrong version
Download original firmware that came with the device (model/region). Maybe hardware as you cannot flash a recovery. You tried TWRP recovery?
Click to expand...
Click to collapse
Tried, but thanks. Sorry but i dont know what was the exact FW

danilisilva7 said:
Try it https://www.androidfilehost.com/?fid=24499762636004166
is a full firmware (csc,original rom and pit file)
If your not 8190, look for yours here http://www.tsar3000.com/Joomla/inde...ader-csc-pit-files&catid=55:samsung&Itemid=82
Click to expand...
Click to collapse
Thanks, trying, will post results
Edit: That full fw stuck on system.img, cant flash it. Lafleur service rom is ok. But in the meantime I saw videos like my problem, and they're repairing power button???? I will spit up and below it if thats the problem
Edit: was not the power button. Reflowed with hot air the whole mainboard. no success. Im getting angry now :/

Odin log
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> STE_boot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> STE_boot1.img
<ID:0/003> STE_boot2.img
<ID:0/003> ipl.bin
<ID:0/003> modem.bin
<ID:0/003> ssgtest.img
<ID:0/003> normal.bin
<ID:0/003> normal2.bin
<ID:0/003> param.lfs
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
Flashing is ok, but i see now it writes movi_write card status=2
It means my emmc is dead?

The same problem as mine, I looked for days solutions, but just found for the galaxy s3
https://forum.xda-developers.com/showthread.php?t=1840030
http://www.joker-soft.com/2015/05/i9300-i9500n7100.html
I'm sorry to say, but our device is dead.
Try to find it on the web, but spent several days and nights looking for it and no solution ... good luck

danilisilva7 said:
The same problem as mine, I looked for days solutions, but just found for the galaxy s3
https://forum.xda-developers.com/showthread.php?t=1840030
http://www.joker-soft.com/2015/05/i9300-i9500n7100.html
I'm sorry to say, but our device is dead.
Try to find it on the web, but spent several days and nights looking for it and no solution ... good luck
Click to expand...
Click to collapse
Anyways, thanks for the help
I'm looking now for a crashed one for a good motherboard

Had i look round for you no joy. The general consensus is hardware failure. One thing though, if your fond of this device buy a real cheap one and put it in the lafluer housing. Apparently the lafluer is a limited addition S3 mini. I did it with mine. I had mine since release and the screen was broken. i bought a new one a few years back and it turned out to be a GT-18200 version was rubbish - over heating, forever charging. I took the circuit board out and replaced it from the old. Worked fine.

Sidebandit said:
Had i look round for you no joy. The general consensus is hardware failure. One thing though, if your fond of this device buy a real cheap one and put it in the lafluer housing. Apparently the lafluer is a limited addition S3 mini. I did it with mine. I had mine since release and the screen was broken. i bought a new one a few years back and it turned out to be a GT-18200 version was rubbish - over heating, forever charging. I took the circuit board out and replaced it from the old. Worked fine.
Click to expand...
Click to collapse
Yes, will trade a rubbish one ,) thanks for thre help

@ricsi30 any joy getting hold of another? I took a 'punt' & managed to get a La Fleur through Amazon, 2nd hand waiting delivery...

Sidebandit said:
@ricsi30 any joy getting hold of another? I took a 'punt' & managed to get a La Fleur through Amazon, 2nd hand waiting delivery...
Click to expand...
Click to collapse
Waiting delivery too, bought a white, working one in good condition. I will use that, but looking for another one for parts

ricsi30 said:
Waiting delivery too, bought a white, working one in good condition. I will use that, but looking for another one for parts
Click to expand...
Click to collapse
Nice one!
Mine fell through but i will still keep an eye open for one.