Hi, please help me. My Samsung Focus 1.3 doesn't boot, only starts and gets stuck on samsung blinking screen. I've tryed to make hard reset, but keys don't work. It only accept download mode. What can I do?
Try either restoring a Zune update, or re-flashing the stock ROM. There should be downloads and instructions for the latter in the device-specific part of the forum.
Alternatively, make sure the SD card (if you use one) is seated correctly. However, I think the most likely problem is just hardware failure, in which case you probably need to get the phone replaced (I assume it's under warranty).
Hi, it's impossible to start on MAGLDGR mode. This phone only accept Download mode, the yellow triangle. There is another way to re-flash from download mode?
After flashing with Focus 1.3 i917 AT&T USA and i917R ROGERS CANADA RETAIL ROMs, using WP7 downloader v. 7.21, it's stucked and just displays SAMSUNG.
Sorry, almost forget, Zune doesn't recognize my device.
I re-flash using I917UCK3 with similar results. This are the processes on WP7:
Open Phone image at : c:\users\nsc3\documents\jm\wp7\samsung-i917-focus-firmware-ucjk2-att-usa\signed_phone_cetus_att.bin
Open Eboot image at : c:\users\nsc3\documents\jm\wp7\samsung-i917-focus-firmware-ucjk2-att-usa\signed_eboot_cetus_att.eb0
Open PDA image at : c:\users\nsc3\documents\jm\wp7\samsung-i917-focus-firmware-ucjk2-att-usa\signed_pda_cetus_att.nb0
Open CSC image at : c:\users\nsc3\documents\jm\wp7\samsung-i917-focus-firmware-ucjk2-att-usa\signed_csc_cetus_att_i917attjk2.csc
Detect COM17 Port
[Channel 0] Confirm Model Name
[Channel 0] FLASH UNLOCK
[Channel 0] FLASH UNLOCK Success!!!
[Channel 0] Send Partition Table
[Channel 0] Partition Table is correct
[Channel 0] Erase MIBIB Region
[Channel 0] Write MIBIB Data
[Channel 0] MIBIB Download Success!!
[Channel 0] Erase FSBL Region
[Channel 0] Write FSBL Data
[Channel 0] FSBL Download Success!!
[Channel 0] Erase OSBL Region
[Channel 0] Write OSBL Data
[Channel 0] OSBL Download Success!!
[Channel 0] Erase AMSS Region
[Channel 0] Write AMSS Data
[Channel 0] AMSS Download Success!!
[Channel 0] Erase DSP1 Region
[Channel 0] Write DSP1 Data
[Channel 0] DSP1 Download Success!!
[Channel 0] Erase APPSBL Region
[Channel 0] Write APPSBL Data
[Channel 0] APPSBL Download Success!!
[Channel 0] Erase CSC Region
[Channel 0] Write CSC Data
[Channel 0] CSC Download Success!!
[Channel 0] Erase PDA Region
[Channel 0] Write PDA Data
[Channel 0] PDA Download Success!!
[Channel 0] FLASH LOCK
Detect COM17 Port
Samsung Focus doesn't boot
jmweb said:
I re-flash using I917UCK3 with similar results. This are the processes on WP7:
Open Phone image at : c:\users\nsc3\documents\jm\wp7\samsung-i917-focus-firmware-ucjk2-att-usa\signed_phone_cetus_att.bin
Open Eboot image at : c:\users\nsc3\documents\jm\wp7\samsung-i917-focus-firmware-ucjk2-att-usa\signed_eboot_cetus_att.eb0
Open PDA image at : c:\users\nsc3\documents\jm\wp7\samsung-i917-focus-firmware-ucjk2-att-usa\signed_pda_cetus_att.nb0
Open CSC image at : c:\users\nsc3\documents\jm\wp7\samsung-i917-focus-firmware-ucjk2-att-usa\signed_csc_cetus_att_i917attjk2.csc
Detect COM17 Port
[Channel 0] Confirm Model Name
[Channel 0] FLASH UNLOCK
[Channel 0] FLASH UNLOCK Success!!!
[Channel 0] Send Partition Table
[Channel 0] Partition Table is correct
[Channel 0] Erase MIBIB Region
[Channel 0] Write MIBIB Data
[Channel 0] MIBIB Download Success!!
[Channel 0] Erase FSBL Region
[Channel 0] Write FSBL Data
[Channel 0] FSBL Download Success!!
[Channel 0] Erase OSBL Region
[Channel 0] Write OSBL Data
[Channel 0] OSBL Download Success!!
[Channel 0] Erase AMSS Region
[Channel 0] Write AMSS Data
[Channel 0] AMSS Download Success!!
[Channel 0] Erase DSP1 Region
[Channel 0] Write DSP1 Data
[Channel 0] DSP1 Download Success!!
[Channel 0] Erase APPSBL Region
[Channel 0] Write APPSBL Data
[Channel 0] APPSBL Download Success!!
[Channel 0] Erase CSC Region
[Channel 0] Write CSC Data
[Channel 0] CSC Download Success!!
[Channel 0] Erase PDA Region
[Channel 0] Write PDA Data
[Channel 0] PDA Download Success!!
[Channel 0] FLASH LOCK
Detect COM17 Port
Click to expand...
Click to collapse
Hello, i have got the same probleme, please how did you resolve the problème ?
Hi, I'm using i8350XXKK4_PLSKK4
CSC_I8350PLSKK4.csc
EBOOT_I8350XXKK4_REV0.eb0
PDA_I8350XXKK4_REV0.nb0
PHONE_WEMBLEY_16002402_open_KK1_rev00_RC1.bin
Flasher:
WP7_Downloader_Ver_3.8_for_Secure_and_SMD_change_Parttiton_and_Support_Retail_binary
Then I made this steps:
- Phone into Download Mode: ( Volume Up Key + Camera Key + Power ).
- Connect USB cable to Phone
- Click Start button to update the phone.
But after a second there is an error message:
APPSBL WRITE FLASH Failed!
Open PDA image at : C:\Users\mtavares\Downloads\i8350XXKK4_PLSKK4\PDA_I8350XXKK4_REV0.nb0
Open CSC image at : C:\Users\mtavares\Downloads\i8350XXKK4_PLSKK4\CSC_I8350PLSKK4.csc
Open Phone image at : C:\Users\mtavares\Downloads\i8350XXKK4_PLSKK4\PHONE_WEMBLEY_16002402_open_KK1_rev00_RC1.bin
Open Eboot image at : C:\Users\mtavares\Downloads\i8350XXKK4_PLSKK4\EBOOT_I8350XXKK4_REV0.eb0
Detect COM3 Port
[Channel 0] Confirm Model Name
[Channel 0] FLASH UNLOCK
[Channel 0] FLASH UNLOCK Success!!!
[Channel 0] CheckSum Data set TRUE
[Channel 0] Send Partition Table
[Channel 0] Partition Table is correct
[Channel 0] Ask the device type.
[Channel 0] Erase APPSBL Region
[Channel 0] Write APPSBL Data
[Channel 0] Write APPSBL Data Fail!!!
Any help please?
Presently this flashing tool is not working with omnia w.
Some background:
My rooted Atrix 2 started going into reboot every few seconds. I tried a factory reset, but that didn't help. I then attempted to flash to the original ROM using RSD Lite. At step 7/21, RSD Lite fails. I have pasted the output of SWDL.txt, below, but the jist of it is "Phone returned FAIL".
Does this mean I have a hardware problem?
11/10/13 11:31:41 --------------------------------------------------------------------------------
11/10/13 11:31:41 New Log Started For Software Download.
11/10/13 11:31:53 The FlashLog key is turned off.
11/10/13 11:32:09 Multi upgrade started for 1 phones
11/10/13 11:32:09 [Device ID: 0] 1/21 reboot-bootloader
11/10/13 11:32:14 [Device ID: 0] 2/21 flash mbm "allow-mbmloader-flashing-mbm.bin"
11/10/13 11:32:15 [Device ID: 0] 3/21 reboot-bootloader
11/10/13 11:32:20 [Device ID: 0] 4/21 flash mbm "mbm.bin"
11/10/13 11:32:21 [Device ID: 0] 5/21 flash mbmloader "mbmloader.bin"
11/10/13 11:32:22 [Device ID: 0] 6/21 reboot-bootloader
11/10/13 11:32:27 [Device ID: 0] 7/21 flash cdt.bin "cdt.bin"
11/10/13 11:32:28 ERROR: 7/21 flash cdt.bin "cdt.bin" -> Phone returned FAIL. - on device ID 0.
11/10/13 11:32:28 [Device ID: 0] 7/21 flash cdt.bin "cdt.bin" -> Phone returned FAIL.
11/10/13 11:32:28 ERROR: Failed flashing process. - on device ID 0.
11/10/13 11:32:28 Multi upgrade finished.
Hi all, still a newbie here - so i cannot post this in Development forum
i would like to share the following file:
'VZW_XT926_4.4.2-KDA20.62-10_1FF.xml.zip'
@SamuraiHL i'm sure youve been waiting for this.
special thanks to @zachariahpope for asking me for it. otherwise i wouldve completely forgotten i had it.
link is here: be sure to remove the 4 spaces (still a noob; someone can repost below with a proper link)
https: //drive. google. com /file/d/0Byyu7DY1fJ31YjJ4bWpjQ2x0Yk0/edit?usp=sharing
stras1234 said:
Hi all, still a newbie here - so i cannot post this in Development forum
i would like to share the following file:
'VZW_XT926_4.4.2-KDA20.62-10_1FF.xml.zip'
@SamuraiHL i'm sure youve been waiting for this.
special thanks to @zachariahpope for asking me for it. otherwise i wouldve completely forgotten i had it.
link is here: be sure to remove the 4 spaces (still a noob; someone can repost below with a proper link)
https: //drive. google. com /file/d/0Byyu7DY1fJ31YjJ4bWpjQ2x0Yk0/edit?usp=sharing
Click to expand...
Click to collapse
OMG yes we needed this so bad. I wish you had spelled my username correctly so I'd have seen this sooner. LMAO! THANK YOU!
Thanks stras1234!
The above is the FXZ for the 182.46.10 version. At least it is something, but I will be watching for the 183.46.10 FXZ.
BBB
Crack for Crackers
realbbb said:
Thanks stras1234!
The above is the FXZ for the 182.46.10 version. At least it is something, but I will be watching for the 183.46.10 FXZ.
BBB
Crack for Crackers
Click to expand...
Click to collapse
What is the difference?
realbbb said:
Thanks stras1234!
The above is the FXZ for the 182.46.10 version. At least it is something, but I will be watching for the 183.46.10 FXZ.
BBB
Crack for Crackers
Click to expand...
Click to collapse
jldr said:
What is the difference?
Click to expand...
Click to collapse
The version number and release signing keys used. That's IT. I don't much care as those who are bricked now (and I have a bunch of people who attempted to downgrade to JB cause they "didn't like KK" ) can fix their phones. if they want the "official" FXZ later, it's a matter of using my RSD Script Generator and flashing it. They won't even lose data in the process.
Virtually nothing. BUT, I ran OTA to 182.46.10. It was problematic. Factory wipe did not fix the battery drain, random crashes, audio hiss. Went to OTA 183.46.10. Issues have gone away.
BBB
Lost in Code.
Oh awesome. So I'll be able to flash from rooted, unlocked CM11 straight to stock KitKat now?
Yup, you can.
Outstanding. Eagerly awaiting your awesome instructions!
I know I asked that same damn question 5 times, I think I'm done now!
http://www.droidrzr.com/index.php/topic/45494-how-to-xt926-upgrade-to-kitkat-ota/
I've updated my thread on droidrzr. Thanks again, Stras! Really appreciated!
@stras1234 thank you so much!
@SamuriHL what the hell would this forum do without us? And yet still no SS backup of a rooted stock system lol
LOL I know, right? Hopefully someone will be able to provide that. Am curious if the idea will work.
SamuriHL said:
http://www.droidrzr.com/index.php/topic/45494-how-to-xt926-upgrade-to-kitkat-ota/
I've updated my thread on droidrzr. Thanks again, Stras! Really appreciated!
Click to expand...
Click to collapse
I gave that a try with my bricked Maxx HD and it failed when writing the system image
You need to post the exact error you're getting if you want me to help. It definitely works, so, it's something in your environment preventing it.
SamuriHL said:
You need to post the exact error you're getting if you want me to help. It definitely works, so, it's something in your environment preventing it.
Click to expand...
Click to collapse
Where can I find the info you need? I was rooted and unlocked when OTA forced hit me. In the AP Fastboot menu I am showing locked now with status code 0.
qqjjz said:
Where can I find the info you need? I was rooted and unlocked when OTA forced hit me. In the AP Fastboot menu I am showing locked now with status code 0.
Click to expand...
Click to collapse
In your RSD folder, look for an SWDL txt file and post it here so I can look at it. Do not worry about the locked status. It's only a temporary thing until we fix the failed flash. Don't panic. This can be fixed.
I think it's because you used the universal script which doesn't update the GPT partitioning. If you're going from JB to KK for the first time, you probably need it to do that.
Basically your partitions are hosed now and you need to find a way to fix them.
EDIT: Never mind, SamuraiHL knows what he's talking about, ignore me.
killrhythm09 said:
I think it's because you used the universal script which doesn't update the GPT partitioning. If you're going from JB to KK for the first time, you probably need it to do that.
Basically your partitions are hosed now and you need to find a way to fix them.
Click to expand...
Click to collapse
Naw, you don't have to flash gpt. I've had others not flash it and it worked fine for them.
SamuriHL said:
In your RSD folder, look for an SWDL txt file and post it here so I can look at it. Do not worry about the locked status. It's only a temporary thing until we fix the failed flash. Don't panic. This can be fixed.
Click to expand...
Click to collapse
Oh no man I am good. I've been poking around my phones and rooting for a few years but I've never encountered anything like this. I am glad I did though because I need to know all this stuff. I'm running on my backup phone right now so what we're repairing here is just to let me have a dev phone and another backup phone
If there is one thing I know about Motorola, they're very sneaky with backdoors and tools when it comes to software. I've worked with them for several years in software testing.
I really appreciate all you guys help btw. Here is the data.
05/22/14 19:11:02 --------------------------------------------------------------------------------
05/22/14 19:11:02 New Log Started For Software Download.
05/22/14 19:11:39 The FlashLog key is turned off.
05/22/14 19:12:49 Multi upgrade started for 1 phones
05/22/14 19:12:49 [Device ID: 0] 1/15 flash sbl1 "sbl1.mbn"
05/22/14 19:12:50 [Device ID: 0] 2/15 flash sbl2 "sbl2.mbn"
05/22/14 19:12:51 [Device ID: 0] 3/15 flash sbl3 "sbl3.mbn"
05/22/14 19:12:52 [Device ID: 0] 4/15 flash rpm "rpm.mbn"
05/22/14 19:12:53 [Device ID: 0] 5/15 flash aboot "emmc_appsboot.mbn"
05/22/14 19:12:54 [Device ID: 0] 6/15 flash modem "NON-HLOS.bin"
05/22/14 19:13:09 [Device ID: 0] 7/15 flash fsg "fsg.mbn"
05/22/14 19:13:10 [Device ID: 0] 8/15 erase modemst1
05/22/14 19:13:11 [Device ID: 0] 9/15 erase modemst2
05/22/14 19:13:12 [Device ID: 0] 10/15 flash logo "logo.bin"
05/22/14 19:13:14 [Device ID: 0] 11/15 flash boot "boot.img"
05/22/14 19:13:21 [Device ID: 0] 12/15 flash recovery "recovery.img"
05/22/14 19:13:27 [Device ID: 0] 13/15 flash system "system.img"
05/22/14 19:14:04 ERROR: 13/15 flash system "system.img" -> Phone returned FAIL. - on device ID 0.
05/22/14 19:14:04 [Device ID: 0] 13/15 flash system "system.img" -> Phone returned FAIL.
05/22/14 19:14:04 ERROR: Failed flashing process. - on device ID 0.
05/22/14 19:14:04 Multi upgrade finished.
05/22/14 19:14:48 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:48 00001388 Phone.cpp 1700 0 ERROR GetTechnology failed: ERROR.
05/22/14 19:14:48 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:48 00001388 Phone.cpp 1700 0 ERROR GetTechnology failed: ERROR.
05/22/14 19:14:48 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:48 00001388 Phone.cpp 1700 0 ERROR GetTechnology failed: ERROR.
05/22/14 19:14:48 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:48 00001388 Phone.cpp 1768 0 ERROR GetSoftwareVersion failed: SendTC failed: ERROR.
05/22/14 19:14:48 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:48 00001388 Phone.cpp 1926 0 ERROR GetSoftwareFlexVersion failed: ReadSeemElement failed: ERROR.
05/22/14 19:14:48 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:48 00001388 Phone.cpp 1896 0 ERROR GetBootVerFlashMode failed: SendTC failed: ERROR.
05/22/14 19:14:48 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:48 00001388 Phone.cpp 1815 0 ERROR GetDRMVersion failed: SendTC failed: ERROR.
05/22/14 19:14:57 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:57 00001388 Phone.cpp 1700 0 ERROR GetTechnology failed: ERROR.
05/22/14 19:14:57 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:57 00001388 Phone.cpp 1700 0 ERROR GetTechnology failed: ERROR.
05/22/14 19:14:57 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:57 00001388 Phone.cpp 1700 0 ERROR GetTechnology failed: ERROR.
05/22/14 19:14:57 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:57 00001388 Phone.cpp 1768 0 ERROR GetSoftwareVersion failed: SendTC failed: ERROR.
05/22/14 19:14:57 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:57 00001388 Phone.cpp 1926 0 ERROR GetSoftwareFlexVersion failed: ReadSeemElement failed: ERROR.
05/22/14 19:14:57 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:57 00001388 Phone.cpp 1896 0 ERROR GetBootVerFlashMode failed: SendTC failed: ERROR.
05/22/14 19:14:57 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:57 00001388 Phone.cpp 1815 0 ERROR GetDRMVersion failed: SendTC failed: ERROR.
05/22/14 19:14:58 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:58 00001388 Phone.cpp 1700 0 ERROR GetTechnology failed: ERROR.
05/22/14 19:14:58 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:58 00001388 Phone.cpp 1700 0 ERROR GetTechnology failed: ERROR.
05/22/14 19:14:58 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:58 00001388 Phone.cpp 1700 0 ERROR GetTechnology failed: ERROR.
05/22/14 19:14:58 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:58 00001388 Phone.cpp 1768 0 ERROR GetSoftwareVersion failed: SendTC failed: ERROR.
05/22/14 19:14:58 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:58 00001388 Phone.cpp 1926 0 ERROR GetSoftwareFlexVersion failed: ReadSeemElement failed: ERROR.
05/22/14 19:14:58 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:58 00001388 Phone.cpp 1896 0 ERROR GetBootVerFlashMode failed: SendTC failed: ERROR.
05/22/14 19:14:58 00001388 Phone.cpp 468 0 ERROR Generic failure when sending command.
05/22/14 19:14:58 00001388 Phone.cpp 1815 0 ERROR GetDRMVersion failed: SendTC failed: ERROR.
I'm guessing you have one of the following problems that you need to resolve:
o) Latest Moto USB driver must be installed
o) Must be a USB 2 port, *NOT* a USB 3 port
o) Must be original OEM cable that came with the phone (yes, it matters)
Basically it failed to send system to your phone...and it's a large freaking file so the transfer failed.
Hi i installed ColorOS12 c.11 and was working but with too much unstability and bloatware.
Wanted to install OOS12 but Local upgrade option from ColorOS12 didnt detect the zip files as valid.
then I tried the FASTBOOTROM to go back to OOS11 but it formatted the data partition but didnt load the OOS11
I tried the MSM tool but it doesnt detect the OP8 device .
Please help me.
FASTBOOT ROM gives error as below:
Do you wish to flash OOS on your OP8? (ALL DATA WILL BE WIPED) [Y/N]?y
Flashing OOS on both slots !!
Erase successful, but not automatically formatting.
File system type f2fs not supported.
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
erasing 'userdata'...
OKAY [ 0.127s]
erasing 'cache'...
FAILED (remote: Check device console.)
finished. total time: 0.132s
fastboot: unknown option -- slot
target reported max download size of 805306368 bytes
sending 'recovery' (102400 KB)...
OKAY [ 2.457s]
writing 'recovery'...
OKAY [ 0.279s]
finished. total time: 2.741s
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
fastboot: unknown option -- slot
fastboot: unknown option -- slot
fastboot: unknown option -- slot
fastboot: unknown option -- slot
fastboot: unknown option -- slot
fastboot: unknown option -- slot
fastboot: unknown option -- slot
fastboot: unknown option -- slot
fastboot: unknown option -- slot
fastboot: unknown option -- slot
fastboot: unknown option -- slot
fastboot: unknown option -- slot
fastboot: unknown option -- slot
fastboot: unknown option -- slot
fastboot: unknown option -- slot
fastboot: unknown option -- slot
fastboot: unknown option -- slot
fastboot: unknown option -- slot
fastboot: unknown option -- slot
fastboot: unknown option -- slot
fastboot: unknown option -- slot
fastboot: unknown option -- slot
fastboot: unknown option -- slot
fastboot: unknown option -- slot
fastboot: unknown option -- slot
fastboot: unknown option -- slot
fastboot: unknown option -- slot
fastboot: unknown option -- slot
fastboot: unknown option -- slot
fastboot: unknown option -- slot
fastboot: unknown option -- slot
fastboot: unknown option -- slot
Done flashing!!
Do you wish to root with magisk (M), or leave (E)??e
Done!! Enjoy OOS again!
Rebooting! Please come again!!
rebooting...
Click to expand...
Click to collapse
EDIT : MSM Tool worked after 2 hours of struggle. OOS11 now booted.
If some MODERATOR can DELETE this THREAD please...