Hi,
I need to put my device in Emergency Download Mode (EDL) in order to recover the boot and fix the bootloop (fastboot not working).
Where is the test points, or how to figure them out?
See the phone schemas below:
Redmi Note 10 Pro 5G (chopin)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Solved without using EDL test points. see The Solution below.
BIG Thanks goes to @NOSS8 for his help.
ramiro2016 said:
Hi,
I need to put my device in Emergency Download Mode (EDL) in order to recover the boot and fix the bootloop (fastboot not working).
Where is the test points, or how to figure them out?
See the phone schemas below:
Redmi Note 10 Pro 5G (chopin)
Click to expand...
Click to collapse
this phone did not need edl or test point.
https://forum.xda-developers.com/t/...-after-flashing-gsi-rom.4448229/post-86995731
@NOSS8 I've tested this method out. The USB serial device drive shows for about 3 seconds and MTK META UTILITY only detects it when I uninstall the driver for the USB serial device. Then it didn't succeed due to the driver I guess. Look at the result in the following image.
Note:
I'm using Windows 11. For this, I will install Windows 7. I will redo the process. When I finish, I will provide you with the results.
ramiro2016 said:
@NOSS8 I've tested this method out. The USB serial device drive shows for about 3 seconds and MTK META UTILITY only detects it when I uninstall the driver for the USB serial device. Then it didn't succeed due to the driver I guess. Look at the result in the following image.
Note:
I'm using Windows 11. For this, I will install Windows 7. I will redo the process. When I finish, I will provide you with the results.
Click to expand...
Click to collapse
https://xiaomitools.com/sp-flash-tool-en/
there is also this tool (new not tested).
https://forum.xda-developers.com/t/tool-rom2box-all-in-one-frp-flashing-unlocking-tool.4477349/
https://gearupwindows.com/how-to-disable-driver-signature-enforcement-on-windows-11-10/
check for program update
@NOSS8 Not working neither in windozs 11 nor in windows 7, I've tested a lot of MediaTek drivers with no luck. Even the new app (Rom2Box) is not detecting the USB serial at all.
Look at the attached images of test I've done.
ramiro2016 said:
@NOSS8 Not working neither in windozs 11 nor in windows 7, I've tested a lot of MediaTek drivers with no luck. Even the new app (Rom2Box) is not detecting the USB serial at all.
Look at the attached images of test I've done.
Click to expand...
Click to collapse
This is not the latest version(V52).
https://mega.nz/file/H0MW3BST#PfzzmSwbncT5aV7A1ZhWztQonLj4CgJLDHbXoRtCu54
Maybe useful
https://www.bypassfrpfiles.com/2021...h_Secure_Boot_Disable_Tool_V52_Latest_Version
BTW: I don't have and would never have a xiaomi Mediatek and therefore never use these tools for Mediatek, that's why I can help you for the links but not for the use of these tools.
If it still doesn't work post the latest log.
Unfortunately, even the latest version v52 doesn't work, but this tool helped me solve the problem.
https://github.com/bkerler/mtkclient (You need to follow the readme document).
I've used the mtk_gui, and after it got connected, I sent my original firmware boot.img that is currently installed on my mobile after renaming it to boot.bin to the device partitions boot_a and boot_b
Rebooting the device got me the original recovery mode and the fastboot mode.
Then I used the MiFlash tool to flash my phone using flash_all.bat
Every thing is working fine know.
BIIIIIIIIIIIG Thanks goes to @NOSS8 for helping me all the way to the solution .
Related
Hey, so my device is unanble to boot and the only solution possible is using MSM but I didn´t find a version for 7T Pro only 7Pro, 7T and 8Pro.
Is there a possibilty to use the MSM tool with the software provided by oneplus website or is there are MSMTool for 7T Pro. I read many forums but didn´t find something there. Please help if you can
nikiwithstyle said:
Hey, so my device is unanble to boot and the only solution possible is using MSM but I didn´t find a version for 7T Pro only 7Pro, 7T and 8Pro.
Is there a possibilty to use the MSM tool with the software provided by oneplus website or is there are MSMTool for 7T Pro. I read many forums but didn´t find something there. Please help if you can
Click to expand...
Click to collapse
This thread should help. Just use the BA version if you need the EU firmware. I used it on my 7T Pro HD1910 (AA firmware) the other day downgrading from OOS 11 and it worked fine.
Hello I m Try TO Flash But Show Error
any have solution please suggestion
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
___kuldeepsharma said:
Hello I m Try TO Flash But Show Error
any have solution please suggestion
View attachment 5361211
Click to expand...
Click to collapse
Entering EDL mode can be tricky if you've never done it. Two ways that I know of:
First using button combo:
1. Power off phone with USB cable disconnected from PC
2. Hold Power UP + Power Down and plug in USB cable
3. Nothing shows up on the phone screen, but the MSM Downloader's Status of Connection should change to "CONNECTED". This is also assuming you have the correct drivers installed.
3b. EDL mode is short lived, so if you don't press Start in time, you will miss it.
Second using adb:
adb reboot edl
Personally, I've only used the button combo and it works.
Hw4ng3r said:
Entering EDL mode can be tricky if you've never done it. Two ways that I know of:
First using button combo:
1. Power off phone with USB cable disconnected from PC
2. Hold Power UP + Power Down and plug in USB cable
3. Nothing shows up on the phone screen, but the MSM Downloader's Status of Connection should change to "CONNECTED". This is also assuming you have the correct drivers installed.
3b. EDL mode is short lived, so if you don't press Start in time, you will miss it.
Second using adb:
adb reboot edl
Personally, I've only used the button combo and it works.
Click to expand...
Click to collapse
Thank you very much for telling me but I have lived everything still it has been there and this is not an Indian phone this is a dense country phone is there any other solution for this
i think the file is wrong can you give me the correct file
___kuldeepsharma said:
Thank you very much for telling me but I have lived everything still it has been there and this is not an Indian phone this is a dense country phone is there any other solution for this
i think the file is wrong can you give me the correct file
Click to expand...
Click to collapse
MSM downloader is in the link in second post of this thread.
Hi, I've recently hardbricked my redmi k40 pro when trying to flash some custom roms and custom recoveries. I managed to get it into EDL mode hoping to flash a working recovery from there. However when I try to use the miflash tool it gets stuck on "ping target via firehose", or goes to "write time out, maybe device was disconnected" and I cannot get anything to work. I realized that even if i get past that part that I still require an authorized xiaomi account to flash in EDL mode. So I thought i'd try it using QFiL, however that requires the programmer file for the phone, and from my understanding that's a proprietary file that only xiaomi has and you can only get from leaks and such.
I was wondering if anyone knew where to get the programmer file or if you knew how I could get an EDL authorized xiaomi account so i could use the miflash tool to fix my phone.
Also does anyone know how to fix the "write timeout, maybe device was disconnected"? I have tried different usb ports and different usb cables and I can' get anything to work.
Also is any snapdragon 888 programmer file usable? Or do I have to have one specific to my phone?
Any help would be greatly appreciated as I am very new to EDL mode.
froggydood said:
Hi, I've recently hardbricked my redmi k40 pro when trying to flash some custom roms and custom recoveries. I managed to get it into EDL mode hoping to flash a working recovery from there. However when I try to use the miflash tool it gets stuck on "ping target via firehose", or goes to "write time out, maybe device was disconnected" and I cannot get anything to work. I realized that even if i get past that part that I still require an authorized xiaomi account to flash in EDL mode. So I thought i'd try it using QFiL, however that requires the programmer file for the phone, and from my understanding that's a proprietary file that only xiaomi has and you can only get from leaks and such.
I was wondering if anyone knew where to get the programmer file or if you knew how I could get an EDL authorized xiaomi account so i could use the miflash tool to fix my phone.
Also does anyone know how to fix the "write timeout, maybe device was disconnected"? I have tried different usb ports and different usb cables and I can' get anything to work.
Also is any snapdragon 888 programmer file usable? Or do I have to have one specific to my phone?
Any help would be greatly appreciated as I am very new to EDL mode.
Click to expand...
Click to collapse
UNBRICK XIAOMI PHONES WITH EDL
DOWNLOAD MODIFIED MIFLASHAND Qualcomm HS-USB QDLoader 9008 DRIVER
The following actions :
1) Connect phone to pc in EDL mode
2) Open Miflash and specify the path to the firmware
3) Click on flash
4) A window will appear where you will need to register the keys
5) On the second line you will need to write the password -
Code:
055F4BBD62228C3E55433D11D59BB445
6) On line 3, write "answer" -
Code:
jL6N48NekgtUZ/3ubbjqXi5RPllB+MoM6Rwqvrvz62jIPQLAVtekYtBxTumF0G95xEAJn2GDsT4G
iMByr/jp5HgtMMsF01DckdGctz7TfddXJ5XDT1Ki/IqQYFZf79M7z+3vFPuVsAL8muq4HBsMYFnm
A5jWj1zaFBtZ+N9VX/0QfRBUcZamyVsWv7X7hd8zVX6MY86eyb6H6EbLaQRueI8j71TcyUaVkUS5
FOyTJ4J1g+XQVeTTNd7Ht9qkfsOkbMha1SPVdLSCHwpI0kc2GXVz/noIv7PatXNQ7II1Sddmo2pn
qNYMfKqpEttJxfVg0No9KBuyzWBNf/sE/W3EBw==
actually don’t know if this still works, but it was a major loophole found.
Kenora_I said:
UNBRICK XIAOMI PHONES WITH EDL
DOWNLOAD MODIFIED MIFLASHAND Qualcomm HS-USB QDLoader 9008 DRIVER
The following actions :
1) Connect phone to pc in EDL mode
2) Open Miflash and specify the path to the firmware
3) Click on flash
4) A window will appear where you will need to register the keys
5) On the second line you will need to write the password -
Code:
055F4BBD62228C3E55433D11D59BB445
6) On line 3, write "answer" -
Code:
jL6N48NekgtUZ/3ubbjqXi5RPllB+MoM6Rwqvrvz62jIPQLAVtekYtBxTumF0G95xEAJn2GDsT4G
iMByr/jp5HgtMMsF01DckdGctz7TfddXJ5XDT1Ki/IqQYFZf79M7z+3vFPuVsAL8muq4HBsMYFnm
A5jWj1zaFBtZ+N9VX/0QfRBUcZamyVsWv7X7hd8zVX6MY86eyb6H6EbLaQRueI8j71TcyUaVkUS5
FOyTJ4J1g+XQVeTTNd7Ht9qkfsOkbMha1SPVdLSCHwpI0kc2GXVz/noIv7PatXNQ7II1Sddmo2pn
qNYMfKqpEttJxfVg0No9KBuyzWBNf/sE/W3EBw==
Click to expand...
Click to collapse
I still get the write time out, maybe device was disconnected error.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Does that work with redmi k40 ???
+1
I am facing the same issue with the bricked device. Mi Flash won't let me install anything using EDL mode without authorization. Anyone can help?
Kenora_I said:
actually don’t know if this still works, but it was a major loophole found.
Click to expand...
Click to collapse
It doesn't work anymore.
I have an Oppo A51w (Oppo Mirror 5) that I just reset to factory settings, out of nowhere when I restared the phone after that it shows encryption unsuccessful, and a reset phone button, which I couldn't press.
Going into ColorOS recovery mode, I tried wiping data and cache, but wiping data doesn't work because it says I have no space it needs at least 250mb, but I remember the phone does have plenty of space, more than 7gbs, so I don't get why it shows that.
As for fastboot mode it doesn't really do anything other than show its starting logo and text and it turns off? Is there anything else I'm supposed to do I'm not sure?
Anything I could do to get past the encryption screen? I don't mind having to fully reset the phone or flash it but I might need a guide.
There is also an install from sd option in the recovery mode, if somehow it can be fixed from there then please help me with that.
The android version is 5.1.1 and ColorOS 2.1.0i
The version that shows on the ColorOS recovery is 1.2
Android 5.1 is too old. I am not sure which fastboot commands are supported for this version but you can try this even if Fastboot works for few seconds.
fastboot -w
fastboot erase userdata
If the fastboot method does not work then you need to find a MSM Download tool and correct firmware for your device model and flash it.
NextGenMagisk said:
Android 5.1 is too old. I am not sure which fastboot commands are supported for this version but you can try this even if Fastboot works for few seconds.
fastboot -w
fastboot erase userdata
If the fastboot method does not work then you need to find a MSM Download tool and correct firmware for your device model and flash it.
Click to expand...
Click to collapse
Does this need USB debugging? I don't have it enabled and can't enable it because I can't get past the encryption screen.
I tried using MSM download tool but for some reason it won't detect my phone and I'm not sure which usb driver to use and how to install it.
The phone also isn't rooted.
Update:
The phone is now stuck on boot loop. I tried to flash it from sd card using stock rom from the official website, without wiping data first because it wasn't possible (needs 250mb of storage space even though there IS enough free space). It said it was successful, but after rebooting it just gets stuck on boot loop.
- for adb I'd need usb debugging? Which can't be enabled
- the phone isn't rooted, so no cwm
- msm download tool I tried, v4 and v5 doesn't work it says "Packed image not exist" but v1.6.7 does? except even it won't detect the phone, and the rom that i downloaded for that from a different source had different phone model options which i do not recognize (oppo15008.bin etc and rawprogram0_MSM_15070.xml) so I'm not sure which one to choose. Maybe I haven't installed the driver but I don't know which to install and how to.
I really have no experience with this and just tried different guides on the internet to get the phone working. For now I don't know what to do. Any help is appreciated.
Your device seems to have Qualcomm chipset so it can be repaired in the EDL mode (9008). Search google "unbrick oppo a51w". It will give you all info you need to fix this.
If your device is not detected even after installing correct drivers, then you need to use Test Point method (shorting JTAG pins) to access EDL mode. This step needs expertise to short correct pins, if your attempts fail then your best option is the Oppo service center.
NextGenMagisk said:
Your device seems to have Qualcomm chipset so it can be repaired in the EDL mode (9008). Search google "unbrick oppo a51w". It will give you all info you need to fix this.
If your device is not detected even after installing correct drivers, then you need to use Test Point method (shorting JTAG pins) to access EDL mode. This step needs expertise to short correct pins, if your attempts fail then your best option is the Oppo service center.
Click to expand...
Click to collapse
I searched and I seem to have tried following steps like this before and it didn't detect my phone even with Qualcomm driver installed, also didn't know which phone model mine is and I'm supposed to choose between these, how do I know?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
southeeast said:
I searched and I seem to have tried following steps like this before and it didn't detect my phone even with Qualcomm driver installed, also didn't know which phone model mine is and I'm supposed to choose between these, how do I know?
Click to expand...
Click to collapse
Sorry, I cannot help with selection of firmware.
Is there any reason why you can't get this repaired in the Oppo service center?
Hi Folks,
I have a Xiomi Note 10 (camellian), unlocked and has USB Debugging switched on.
No matter what I do, I can't install TWRP or Orangefox because it fails with "FAILED: Too Many Links"
I've followed so many guides on how to fix this and they all fail. I tried to flash the stock rom with Mi Flash and that failed too (Constant "Unhandled exception" error as it doesnt seem to want to install drivers and wont continue without them). I've manually updated the ADB drivers for the Note and that worked fine. Mi Pc Suite doesnt recognise my phone unless i "Update your phone before you connect" (The phone is fully updated)
Please, for the love of the baby jesus and the little donkey, tell me what I can do to try and figure out what the smeg is going wrong
EDIT:
Ive changed ports/cables, tried compatibilty on programs, reinstalled ADB drivers
trying "fastboot flash boot recovery.img" (for orange fox) throws up "FAILED: remote: size too large"
hellfirehound said:
Hi Folks,
I have a Xiomi Note 10 (camellian), unlocked and has USB Debugging switched on.
No matter what I do, I can't install TWRP or Orangefox because it fails with "FAILED: Too Many Links"
I've followed so many guides on how to fix this and they all fail. I tried to flash the stock rom with Mi Flash and that failed too (Constant "Unhandled exception" error as it doesnt seem to want to install drivers and wont continue without them). I've manually updated the ADB drivers for the Note and that worked fine. Mi Pc Suite doesnt recognise my phone unless i "Update your phone before you connect" (The phone is fully updated)
Please, for the love of the baby jesus and the little donkey, tell me what I can do to try and figure out what the smeg is going wrong
EDIT:
Ive changed ports/cables, tried compatibilty on programs, reinstalled ADB drivers
trying "fastboot flash boot recovery.img" (for orange fox) throws up "FAILED: remote: size too large"
Click to expand...
Click to collapse
i see none TWRP and O.F for camellian, can you post the links +Miflash log?
The TWRP is unofficial https://forum.xda-developers.com/t/unofficial-twrp-camellia-camellian.4304717/
There is no MiFlash log anywhere. Sorry im new to this
I think I need to flash the original rom before trying to install a recovery rom
hellfirehound said:
The TWRP is unofficial https://forum.xda-developers.com/t/unofficial-twrp-camellia-camellian.4304717/
There is no MiFlash log anywhere. Sorry im new to this
Click to expand...
Click to collapse
The Mi Flash logs are in the Miflash Log folder (post the last + or - 20/22ko
This twrp seems not to work (closed thread).
Try the command: fastboot boot twrp.img
The phone will reboot in TWRP after that go to Advanced > Flash Current TWRP
And what do you want to do with the TWRP, your device has a Mediatek soc and there is little or no development for Xiaomi with a Mediatek soc.
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It looks like a mediatek device.
Never Mind, ill keep the phone as is. Thanks for trying to help
Download and extract to the root of the disk.C:/platform....
https://developer.android.com/studio/releases/platform-tools
rename the Twrp to twrp.img
Put it in the Platform tools folder
Execute the command from this folder
Since no custom is available for your phone I guess you want to update or downgrade for these 2 cases use Miflash not TWRP.
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
this error
is frequent with certain version of W10.
Disable driver verification.
.
Hello. I recently brought back my x820 to life. I need a phone.
It had TWRP and a custom rom. I tried to wipe and I actually wiped too much. So I had to install stock rom again because for some reason, lineage gave me an error at install (like it wasn't the right rom but it really was since I found it here https://download.lineageos.org/x2).
So I try to install TWRP again: twrp-3.7.0_9-0-x2.img found here: https://eu.dl.twrp.me/x2/
I launch ADB on a cmd prompt
- adb devices (List of devices attached e816a730 device). Super it's working and recognized
- adb reboot bootloader (phone miraculousely reboots in fastboot mode - YAY)
- fastboot devices ....... goes back to c:\ADB .... no devices found
So I reinstall ADB (from here: https://forum.xda-developers.com/t/...vers-15-seconds-adb-installer-v1-4-3.2588979/). Y to all, reinstall drivers and everything. Reboot PC. Do everything again.....still the same weird fastboot < waiting for devices >.
Devloper options are enabled.
OEM is unlocked.
USB debugging is ON.
Cable has been changed.
Cables have been plugged on USB 2.0 ports (in the back), on 2 different computers.....still the same thing.
*#*#76937#*#* typed in and AT ports enabled.
Could someone have the kindness to help me figure out what's wrong with what I'm doing? I'm usually pretty comfortable with rooting, flashing etc....but I'm clueless here.
Thanks for any help or input.
First off, please install the Android SDK Platform Tools [instead of 15 seconds ADB installer]
Once done, install the Fastboot Drivers on your PC.
The ADB Tools [Platform Tools, 15 seconds installer, etc] don't have Fastboot binaries, so you will only be able to execute ADB-related commands and not the Fastboot ones.
Thanks.
I downloaded the fastboot drivers. But I can't seem to install them. In fastboot mode, I see this in my device manager:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I follow instructions from here: https://www.droidwin.com/how-to-install-fastboot-drivers-in-windows-11/ (your link). Although I'm on windows 10.
When I try to update driver, whatever I do, I get this error:
Which means "the folder doesn't contain any compatible driver for your device. If it contains a driver, make sure it can work for x64 computers".
So I'm pretty sure it's a driver problem. Is there a way to completely uninstall previous drivers and go from scratch again? Or any cleverer solution?
Try removing the faulty device then disable driver signature enforcement and install drivers.
https://avalonsciences.com/wp-conte...Signature-Verification-on-Windows-8-or-10.pdf
Thanks to both of you. Especially to you binary who pointed me on the right tutorial. I was doing something wrong when updating drivers in fastboot mode. I chose a device before locating the .inf file.
YES
NOOOOOOOOOOOOOOOOOOO
The bottom screen was taken from here: https://forum.xda-developers.com/t/...vers-15-seconds-adb-installer-v1-4-3.2588979/
"Show all devices" MUST be selected before going a step further apparently. All 3 drivers were installed flawlessly. TWRP was flashed successfully. I just need to figure out why it's still the old stock recovery showing up when I VOL+ and POWER start.
Cheers guys.
lucky24i said:
I just need to figure out why it's still the old stock recovery showing up when I VOL+ and POWER start.
Click to expand...
Click to collapse
Glad that you were able to rectify the driver issue. As far as TWRP is concerned, as soon as you flash it, boot straight to it [without booting to the system] and then check out the result.
In some instances, the device tends to replace TWRP with stock recovery upon boot. So avoid booting to the OS and use fastboot reboot recovery to straightaway boot to TWRP after flashing it.
Thanks. Working great