Database Develop

KFHD7 Tate Bootloop

Hi,
I updated my good old Kindle Fire HD 7 (tate) to cm 12.1 and because of problems with the Play store I made a factory reset. Since then it is in a bootloop showing only the blue teamwin screen with some flickering about every 5-6 seconds.
As I read here (http://forums.androidcentral.com/sa...p-after-factory-reset-cyanogenmod-12-1-a.html), I need to use fastboot.exe to start a new recovery but... fastboot does not recognize the device.
What is working?
adb status-window shows
...Android Debug Bridge
State: unknown (or recovery)
adb reboot revovery - reboots the device
adb reboot bootloader - reboots the device showing a "fastboot logo"
fastboot devices
< waiting for device > / or just no reaction
fastboot -i 0x1949 getvar product
TATE-PUT-08
Okay, after some research I updated my driver (as seen here http://forum.xda-developers.com/showthread.php?t=2271909) and they seem to be installed properly but nothing changes to the behaviour shown above.
What to do?
And thanks a lot!
My systems: Windows 7 Professional 64 bit or Windows 7 Home Premium 64 Bit

..getting creative, I tried
fastboot -i0x1949 boot philz_touch_6.48.4-tate.img
creating boot image...
creating boot image - 8343552 bytes
downloading 'boot.img'...
OKAY [ 2.817s]
booting...
OKAY [ -0.000s]
finished. total time: 2.817s
..and it reboots into the same teamwin splash screen boot loop
...with adb status-window saying "recovery"

Ok, I had the courage to flash and tate is working again:
1. adb reboot bootloader (then in Fastboot mode)
2. fastboot -i0x1949 flash recovery philz_touch_6.48.4-tate.img
3. fastboot -i0x1949 boot philz_touch_6.48.4-tate.img
4. two reboots and cm 12.1 is working

Same problem! PLEASE HELP!
I'm stuck with THE EXACT same problem.
Please tell me how to go about this step-by-step?
I hope you reply asap..
TIA.

Diplominformatiker said:
Ok, I had the courage to flash and tate is working again:
1. adb reboot bootloader (then in Fastboot mode)
2. fastboot -i0x1949 flash recovery philz_touch_6.48.4-tate.img
3. fastboot -i0x1949 boot philz_touch_6.48.4-tate.img
4. two reboots and cm 12.1 is working
Click to expand...
Click to collapse
can you please do a step by step write-up please?

1. start windows command prompt (cmd.exe) in Administrator Mode
2. type "adb reboot bootloader"
3. type "fastboot -i0x1949 flash recovery philz_touch_6.48.4-tate.img"
4. type "fastboot -i0x1949 boot philz_touch_6.48.4-tate.img"
reboot (perhaps several times)
preparations (if not yet done):
- install Android development kit or download adb somewhere
- download philz_touch_6.48.4-tate.img, copy to same folder as adb
- connect kindle via usb
Good Luck

Diplominformatiker said:
1. start windows command prompt (cmd.exe) in Administrator Mode
2. type "adb reboot bootloader"
3. type "fastboot -i0x1949 flash recovery philz_touch_6.48.4-tate.img"
4. type "fastboot -i0x1949 boot philz_touch_6.48.4-tate.img"
reboot (perhaps several times)
preparations (if not yet done):
- install Android development kit or download adb somewhere
- download philz_touch_6.48.4-tate.img, copy to same folder as adb
- connect kindle via usb
Good Luck
Click to expand...
Click to collapse
I bricked my kindle by using FireFlash to get into recovery, and I didn't check the box for the bootloader. Now I am stuck in a boot loop. Every time I use a command in adb, it says it can't find a device. I have tried with a factory cable and with a regular USB. I tried updating the driver through the Device Manager, but it can't find a driver for my kindle. I found a few drivers to choose from on a website (I would post the link, but it won't let me), but none of them seemed to work. Is there something I am doing wrong?

whether the tablet says fastboot or teamwin, it will not start fastboot -i0x1949 flash recovery philz_touch_6.48.4-tate.img, it will just say waiting for device...

hiii
Same situation , no solution until now

unimoose said:
I bricked my kindle by using FireFlash to get into recovery, and I didn't check the box for the bootloader. Now I am stuck in a boot loop. Every time I use a command in adb, it says it can't find a device. I have tried with a factory cable and with a regular USB. I tried updating the driver through the Device Manager, but it can't find a driver for my kindle. I found a few drivers to choose from on a website (I would post the link, but it won't let me), but none of them seemed to work. Is there something I am doing wrong?
Click to expand...
Click to collapse
In device managment, set to see the hidden devices, must appear as TATE-PVT-8, depending the version of Windows you're using must set the signed drivers to disable.
Then update the driver to tate with this controllers.
And use fatbootmode, can use: KFHD_SRTool_v1.2 to revert to completly stock.
Hopes works for you.

Enomaly said:
whether the tablet says fastboot or teamwin, it will not start fastboot -i0x1949 flash recovery philz_touch_6.48.4-tate.img, it will just say waiting for device...
Click to expand...
Click to collapse
Are you saying that the above mentioned method will not work? So what is the possible solution?

error during installing TwRp

I have unlocked my bootloader and when I try to install TWRP recovery and open a cmd write the commands 'adb devices' and "fastboot devices" to check whether connected or not it shows connected then reboot to to bootloader but when I put command "fastboot flash recovery recovery. img" I get " cannot load recovery. Img" . I also downloaded the latest TWRP victara and adb, fastboot aswell but can't get what problem is please Help guys!!!

Vedang V said:
I have unlocked my bootloader and when I try to install TWRP recovery and open a cmd write the commands 'adb devices' and "fastboot devices" to check whether connected or not it shows connected then reboot to to bootloader but when I put command "fastboot flash recovery recovery. img" I get " cannot load recovery. Img" . I also downloaded the latest TWRP victara and adb, fastboot aswell but can't get what problem is please Help guys!!!
Click to expand...
Click to collapse
So you got the latest ADB and Fastboot:
https://developer.android.com/studio/releases/platform-tools.html
You got the latest TWRP Victara:
https://twrp.me/motorola/motorolamotox2014.html
Extract ADB and Fastboot, and put the TWRP img file in the same folder, start command prompt as Admin and Change Directory to where the files are:
cd C:\Users\User\Downloads\platform-tools (this is just an example)
fastboot flash recovery twrp-3.2.1-0-victara.img
Boot into recovery immediately.

Vedang V said:
I have unlocked my bootloader and when I try to install TWRP recovery and open a cmd write the commands 'adb devices' and "fastboot devices" to check whether connected or not it shows connected then reboot to to bootloader but when I put command "fastboot flash recovery recovery. img" I get " cannot load recovery. Img" . I also downloaded the latest TWRP victara and adb, fastboot aswell but can't get what problem is please Help guys!!!
Click to expand...
Click to collapse
Did you install the Motorola USB Drivers?
https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/79106/p/30,75,27,
Did you type the full name of the img file, including .img

You must write fasstboot flash recovery (full name of the file ot rename it).img.
When is finished not take off the cable and run recovery from device bootloader.
Thats it.

No Command TWRP

Original: 7.1.1 Nougat
I unlocked Bootloader
I rooted
Installed TWRP
Wiped
Installed 8.1 rom
installed gapps
Installed Magisk 16
reboot to recovery -> No command
When i go back to bootloader and re install twrp via wugs, it works and loads. If I reboot into recovery again, even from twrp, it gives me the no command error.
Any solutions on how to permanently get twrp running

Yes. Stop using the toolkit.
You need to actually see the messages fastboot generates. To do that, you're going to need to use ADB and Fastboot directly, without the toolkit. Get Minimum ADB and Fastboot from the forums (search for it) and install it. Make sure USB debugging is enabled in settings, then open up a command prompt to the directory where you installed Minimum ADB & Fastboot. In that command prompt type the following commands.
"adb devices" - lists the connected devices. If you see a device, continue.
"adb reboot bootloader" - self explanatory. The equivalent of pressing power and volume down.
"fastboot flash recovery recovery.img" - self explanatory. Replace "recovery.img" with the actual name of the file.
"adb reboot recovery" - should take you directly to the recovery. "adb reboot bootloader" and the volume keys should also work as an alternative.

Mi A2 Can't flash anything via fastboot (bootloader unlocked, oem critical too)

When I flash TWRP
It shows me this
Code:
PS C:\adb> fastboot devices
******** fastboot
PS C:\adb> fastboot boot recovery.img
downloading 'boot.img'...
FAILED (command write failed (Invalid argument))
finished. total time: -0.000s
PS C:\adb>
and my mi a2 turned in to black screen and shows "press anything to shutdown" on the upper left corner
if I didn't use fastboot device first it shows me this
Code:
PS C:\adb> fastboot boot recovery.img
downloading 'boot.img'...
FAILED (command write failed (Too many links))
finished. total time: 0.003s
PS C:\adb>
I try to use another way
Code:
PS C:\adb> fastboot devices
******** fastboot
PS C:\adb> fastboot getvar current-slot
getvar:current-slot FAILED (command write failed (No such file or directory))
finished. total time: 0.000s
PS C:\adb>
But without fastboot devices
Code:
PS C:\adb> fastboot getvar current-slot
current-slot: a
finished. total time: -0.000s
PS C:\adb> fastboot flash boot_b recovery.img
sending 'boot_b' (41314 KB)...
FAILED (remote: unknown command)
finished. total time: 0.000s
already changed 3 different cable and try 8 usb port on my computer
tried adb installer 1.3 and 1.4.3
updated my Mi Usb Driver
I have never flash any a/b slot device before I have no idea what's going on
any my mi a2 still can boot into system and stock recovery
any solution please
sorry for my bad English.
-------------------------------------------------------------
UPDATE!!
I just use a USB2.0 Port (USB HUB)
and I got the problem solved!!!!

You are using the wrong recovery....check if developer op is on & usb debugging is enabled....also try to unlock you bootloader again......

bladehunter said:
You are using the wrong recovery....check if developer op is on & usb debugging is enabled....also try to unlock you bootloader again......
Click to expand...
Click to collapse
I'm using the TWRP For jasmine from this thread
also tried this too
I have my usb debugging on already and I also tried to lock my bootloader then unlock it again
the problem still there
(

same problem here , please help anyone

cs853120 said:
I'm using the TWRP For jasmine from this thread
also tried this too
I have my usb debugging on already and I also tried to lock my bootloader then unlock it again
the problem still there
(
Click to expand...
Click to collapse
reset your phone once then try........also try to unlock your boot loader & see if you can flash the stock rom from the official website......make sure that the entire rom file is in a folder on your desktop.......for some reason MI flash does not like long system paths.....

cs853120 said:
When I flash TWRP
It shows me this
and my mi a2 turned in to black screen and shows "press anything to shutdown" on the upper left corner
if I didn't use fastboot device first it shows me this
I try to use another way
But without fastboot devices
already changed 3 different cable and try 8 usb port on my computer
tried adb installer 1.3 and 1.4.3
updated my Mi Usb Driver
I have never flash any a/b slot device before I have no idea what's going on
any my mi a2 still can boot into system and stock recovery
any solution please
sorry for my bad English.
Click to expand...
Click to collapse
Hi there.
I have the same problem. Can't do anything with my phone on any USB 3.0/3.1-Port on my Ryzen desktop (works neither on Win10 nor Linux Mint). I have to use my old Win8.1 Intel laptop and there everything works flawlessly but only on the USB 2.0 port. I used the same tools/commands/Mi-drivers but it only works on the laptop. Tried different drivers for MB/USB-host controller and different cables but to no avail... Connecting the phone and mtp works but no adb/fastboot.
I read on different threads that other people have the same problem with other hardware setups but most of them were able to fix it with MB drivers from the manufacturer instead of the Windows ones. Maybe that could work for you.
For now I keep the laptop around for flashing my A2....

whenever you get "press any key to shutdown" on fastboot it's because of the usb port, use usb 2.0

I have the same problem , and change to 2.0 USB Ports works! Thanks!

Did you found a solution?

Please help. Facing exact same issue. Tried all USB ports on my PC. Switched between Ubuntu and Win10. All to no avail.

It's a USB 3 problem. I had it too in my laptop. You gotta find a USB 2 port, maybe in another PC. Good luck.
Sent from my Mi A2 using XDA Labs

i was also fasing same problem so what is did is
fastboot flashing unlock_critical
then
fastboot oem edl
and flashed stock

Mi A2 Boot loop
The first thing you'll want to do here is extract the factory images archive that you downloaded from your manufacturer's website. For that part, I'd recommend using 7-Zip, as it's free and works with most archive formats , move all of the contents of the archive to the platform-tools folder inside of your ADB installation directory, then open an ADB Shell window in this folder.
Flash the system images individually. This method takes some extra work, but it can be used to un-root, update, or un-brick your device without losing existing data.
Start by extracting any additional archives from the factory images package. Sometimes, factory images packages can contain a series of three or four nested archives, so make sure to unzip all of them. From there, copy all of the image files to the main platform-tools folder—in other words, don't leave them in any sub-folders.
there are two images that you can get rid of: cache.img and userdata.img. These are the images that will overwrite your data and cache with blank space, so if you don't flash them, your existing data will remain intact.
Of the remaining images, six make up the core elements of Android: boot, bootloader, radio, recovery, system, and vendor.
The boot image contains the kernel, so if you just want to get rid of a custom kernel that's causing issues with your device, you only have to flash this one. To do that, type the following command into the ADB shell window:
//
fastboot flash boot <boot image file name>.img
//
Next is the bootloader image—this is the the interface that you're using to flash images with Fastboot commands. So to update your bootloader, type:
fastboot flash bootloader <bootloader image file name>.img
//
Once you've done that, you should reload the bootloader so that you can continue flashing images on the newer version. To do that, type:
fastboot reboot-bootloader
//
After that, we have the radio image. This one controls connectivity on your device, so if you're having problems with Wi-Fi or mobile data, or if you just want to update your radio, type:
fastboot flash radio <radio image file name>.img
//
Then there's recovery. This is something you may or may not want to flash, depending on the modifications you've made. For example, if you've installed TWRP custom recovery, flashing this image will overwrite your modification and replace it with the stock recovery interface. So if you're just updating your modded device, you should skip this one. Otherwise, if you plan to keep your phone stock and want the newer version of stock recovery, type:
fastboot flash recovery <recovery file name>.img
//
Next up is the big one: The system image. This one contains all of the files that make up the actual Android OS. As such, it's the most essential part of any update.
However you may not be updating your phone. You may just be re-flashing the stock firmware to recover from a soft brick. If this is the case, the system image is often the only image you need to flash in order to fix everything, because it contains the entirety of Android. In other words, if you flash this image and nothing else, it will undo any changes you made with root access and put everything back the way it was.
So as a cure-all in most soft brick situations, or as a method for getting the core part of an Android update, type:
fastboot flash system <system file name>.img
//
Finally, there's the vendor image. This is only present on newer phones, so don't worry if it's not in your factory images package. But if it's there, it contains a few important files, so type the following line to get this partition updated:
fastboot flash vendor <vendor file name>.img
//
After you've sent any or all of the above commands, you'll be ready to restart your device and boot into Android. To do that, type:
fastboot reboot
/
Thanks to Android gadget hacks .
P.S : Including today , it was 22nd time that i rooted , enabled camera2api .. but i think till know its useless .

After dealing with this issue for a long time I found that using a USB hub solved it for me.
This is the one I'm using: https://es.aliexpress.com/item/USB-...342.html?spm=a2g0s.9042311.0.0.1d6e63c04tJJe6
Hope this helped!

the same problem
have tried all USB port, unfortunately, no success

Hi everyone,
Today I have a big problem
I install jasmine__V10.0.8.0.PDIMIXM and after I set "fastboot oem lock" but Now my MI A2 Can't enter in OS.
I have this message on screen
"Your device has loaded a different operation system"
and another page says
"Your device software can'tbe checked for corruption. Plese lock the bootlader.
But when I check in fastboot I have bootloader locked.
Any suggestion to unlock ? I can't enter in OS.
Thanks

HELP
bladehunter said:
You are using the wrong recovery....check if developer op is on & usb debugging is enabled....also try to unlock you bootloader again......
Click to expand...
Click to collapse
Can you help me with my thread?? Thank you!

Same error.

Download TWRP and TWRP installer
DONT CONNECT YOUR PHONE!!
Put your phone in Fastboot
in cmd type
fastboot boot twrp.img (twrp name instead of twrp.img)
Then when you see <Waiting for Device> connect your phone !
Check if it's working.
This was fix for me, when I was unable to even boot into recovery.
Once you boot into recovery, wipe everything, flash twrp zip, and error should be gone

Hey guys,
same issue here but i don't have any usb2.0 port on my laptop now. Any workaround? Totally sure that i used fastboot + usb3.0 on Sony, LG, Samsung ROMs with no hassles whatsoever. Is this only happening with Xiaomi?
Cheers

Help me recover my motorola g5s plus Android phone

Hi All,
I need help from you experts to recover my phone moto g5s plus
Type : M271C Model : XT1806
The phone was working without any issues but suddenly got restarted and now i's stuck in the "Fast Boot Flash" Mode.
It cannot boot and the "Boot Loader Log" screen says below.
"Start Up Failed:
Your Device did not startup successfully.
Use the software repair assistant on computer to repair your device.
Connect your device to your computer to get the software repair assistant.
AP Fastboot Flash Mode (Secure)
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Fastboot reason : Fall Through from normal boot mode
USB Connected"
1. I installed the "Rescue and Smart Assistant" software and tried to recover from there but unfortunately it does not recognize my phone model.
2. Tried to install Install TWRP Custom Recovery tool. But I cannot do it because the "USB debugging " is not enabled on the phone.
3. 'USB debugging"and "OEM Unlock" on my Android device is not enabled so I cannot Unlock Bootloader
Is there any way that I can boot into recovery or install a custom ROM without having the "USB Debugging" and "OEM Unlock" Enabled in my phone?
Thanks

Are you using adb for recovery?

andres_vacal said:
Are you using adb for recovery?
Click to expand...
Click to collapse
No. ADB cannot be used since my device is not enabled "USB Debugging"

USB debugging should not be required to unlock the bootloader as you are using fastboot commands to unlock the bootloader rather than ADB commands.
Try "fastboot reboot recovery"

andres_vacal said:
USB debugging should not be required to unlock the bootloader as you are using fastboot commands to unlock the bootloader rather than ADB commands.
Try "fastboot reboot recovery"
Click to expand...
Click to collapse
I get following error when I run that command.
Rebooting into recovery FAILED (remote: 'Unknown command')
fastboot: error: Command failed

dharshana1 said:
I get following error when I run that command.
Rebooting into recovery FAILED (remote: 'Unknown command')
fastboot: error: Command failed
Click to expand...
Click to collapse
Okay, I think I untherstand whats happening. Its probable that any way or another you deleted your recovery or directly your ROM.
So i´ll recommend you to download and run TWRP(You can look out on the internet for your specific device)
If it runs correctly, go to reboot and check out if in the top part says "No OS installed", if it says that, then you will have to lock out for a compatible ROM and instal it.
If you have any thoughts let me know how it goes..

andres_vacal said:
Okay, I think I untherstand whats happening. Its probable that any way or another you deleted your recovery or directly your ROM.
So i´ll recommend you to download and run TWRP(You can look out on the internet for your specific device)
If it runs correctly, go to reboot and check out if in the top part says "No OS installed", if it says that, then you will have to lock out for a compatible ROM and instal it.
If you have any thoughts let me know how it goes..
Click to expand...
Click to collapse
Hello,
Thanks for the reply, I tried to install the TWRP tool that is for my specific device, but it won't allow me to install since "USB debugging" is not enabled in my device.
Is there any other way to install that without USB debugging enabled?
Thanks

Okay, so i´ll try to explain in detail how to install TWRP via Fastboot commands (No usb debugging needed since you are using fastboot)
1. Make sure you have all the specific drivers for using fastboot.
2. Type "fastboot devices" and make sure your device appears on the command prompt
(it should apper something like "5f684fe2").
3. Type "fastboot erase recovery" to make sure the old recovery is no longer avaiable in your device.
4. Send the TWRP.img file that you already have to the adb folder you are using on the command prompt
5. Type "fastboot flash recovery TWRP.img" ("TWRP" is the recovery´s name you have saved)
6. Tyoe "fastboot reboot recovery" and see if TWRP is now installed.
Important note: Make sure you have saved all the important files from your phone.
If this doesn´t fuction, after you make step 2 succesfully:
Type these 3 commands:
"fastboot erase system"
"fastboot erase data"
"fastboot erase cache"
and "fastboot reboot"
Then repeat the instalation process.

andres_vacal said:
Okay, so i´ll try to explain in detail how to install TWRP via Fastboot commands (No usb debugging needed since you are using fastboot)
1. Make sure you have all the specific drivers for using fastboot.
2. Type "fastboot devices" and make sure your device appears on the command prompt
(it should apper something like "5f684fe2").
3. Type "fastboot erase recovery" to make sure the old recovery is no longer avaiable in your device.
4. Send the TWRP.img file that you already have to the adb folder you are using on the command prompt
5. Type "fastboot flash recovery TWRP.img" ("TWRP" is the recovery´s name you have saved)
6. Tyoe "fastboot reboot recovery" and see if TWRP is now installed.
Important note: Make sure you have saved all the important files from your phone.
If this doesn´t fuction, after you make step 2 succesfully:
Type these 3 commands:
"fastboot erase system"
"fastboot erase data"
"fastboot erase cache"
and "fastboot reboot"
Then repeat the instalation process.
Click to expand...
Click to collapse
Hi,
Thank you so much for the reply. I can see a device when I run the "fastboot devices" command. But when I tried above other commands (fastboot erase ...) they failed with below error.
Erasing 'recovery' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
Erasing 'system' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
Erasing 'data' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
when I run the fastboot erase cache command below error throws
Erasing 'cache' (bootloader) Failed to erase partition
FAILED (remote: '')
fastboot: error: Command failed
Thank you for your time helping me resolve this issue, anything else that I can try out?

Okay so I think your phone´s bootloader is locked.
So try this out: https://forum.xda-developers.com/t/...der-root-and-recovery-for-the-moto-g.3418432/ (Unloock bootloader section)
Hopefully it will get your bootloader unlocked and then you will be ready to do the process I posted before.
This is going harder than I thought.

dharshana1 said:
Hi All,
I need help from you experts to recover my phone moto g5s plus
Type : M271C Model : XT1806
The phone was working without any issues but suddenly got restarted and now i's stuck in the "Fast Boot Flash" Mode.
It cannot boot and the "Boot Loader Log" screen says below.
"Start Up Failed:
Your Device did not startup successfully.
Use the software repair assistant on computer to repair your device.
Connect your device to your computer to get the software repair assistant.
AP Fastboot Flash Mode (Secure)
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Fastboot reason : Fall Through from normal boot mode
USB Connected"
1. I installed the "Rescue and Smart Assistant" software and tried to recover from there but unfortunately it does not recognize my phone model.
2. Tried to install Install TWRP Custom Recovery tool. But I cannot do it because the "USB debugging " is not enabled on the phone.
3. 'USB debugging"and "OEM Unlock" on my Android device is not enabled so I cannot Unlock Bootloader
Is there any way that I can boot into recovery or install a custom ROM without having the "USB Debugging" and "OEM Unlock" Enabled in my phone?
Thanks
Click to expand...
Click to collapse
Just got the same issue..
Did you get it resolved?

andres_vacal said:
Okay so I think your phone´s bootloader is locked.
So try this out: https://forum.xda-developers.com/t/...der-root-and-recovery-for-the-moto-g.3418432/ (Unloock bootloader section)
Hopefully it will get your bootloader unlocked and then you will be ready to do the process I posted before.
This is going harder than I thought.
Click to expand...
Click to collapse
Well this guy has given same steps , but while unlocking bootloader
fastboot oem get_unlock_data
is not working at all, its giving same error which @dharshana1 has mentioned before.
I'm using this cell last three years, it started acting slow all of a sudden and then this thing has happened.

smandar said:
Well this guy has given same steps , but while unlocking bootloader
fastboot oem get_unlock_data
is not working at all, its giving same error which @dharshana1 has mentioned before.
I'm using this cell last three years, it started acting slow all of a sudden and then this thing has happened.
Click to expand...
Click to collapse
I worked with this model 3 weeks ago, and the thing is that in order to unlock bootloader you will need to go to motorola´s web page for getting a password. in this thread you will find how it goes. I untherstand that amazon's versions are unable to unlock bootloader so if you are into that version, bad luck.