Database Info

simlock.ta problem ignored by flashtool

I lost my network i.e signal after instaling a rom, so now i am trying to flash stock rom (also i flashed with seus and pc copmanion but didnt fixed)
and i have a problem while flashing the simlock.ta file is ignored by the flash tool u can see http://prntscr.com/y2nx3
i guess thats the problem why i dont have network
i already tried many roms and kernels and nothing helped
i hope someone knows how to fix this problem

flash tool always ignores my simlock ta. sin and my phone is ok bro it might not be that

well so why my phone doesnt have network and doesnt recognizing any sim card

cipjanin said:
well so why my phone doesnt have network and doesnt recognizing any sim card
Click to expand...
Click to collapse
i have the same problem, so i asked Alejandrissimo he said that i should reunlock simlock and it costs 10$.

I flashed stock ROM's some times and simlock file was ignored but my phone worked and works.
Why lock yourself to one carrier when your phone can work on many ?
Simlock as I think has nothing to do with your problem.

Relock your bootloader and flash that you want...
Sent from my Xperia Tipo using xda app-developers app

check proper baseband is installed......

Unlocking the Simlock
Hello everyone, After attempting to upgrade Gingerbread to ICS on my Xperia Play I used the Testpoint to unblock the bootloader..it turns out that it is now bricked...brilliant of me, I know..using the testpoint it did allow me to use the S1tool and it finds it, however it says that it gives me the Not recognized simlock certificate error message. I used the Sony Bootloader unlock page and ran it with fastboot and it tells me that the phone is already unlocked and using *#*#7378423#*#* it says the bootloader unlock YES... I have already tried flashing the OS, it says that it´s done it but it ignores the simlock.ta and it still wont boot. All I get is a brief vibration and no led. I managed to install the ADB drivers and could enter Fastboot mode, I flashed the kernel and it recognizes it when I open Flashboot but still no boot. What can I do??
In this thread named "simlock.ta problem ignored by flashtool" it says that Mr Alejandrissimo told someone how to unlock it for 10.00, I´m not sure if that may be the solution. Can someone tell me please how to contact him so I can get that information? I´m really lost here I would definitely appreciate the help.
Thank you for your time and I apologize for the long message, I just wanted to provide as much information as I could.

Solution
Brother Flash this file it solve your problem your device will alive
but other sim problem I don't know
I have same problem......
Good Luck.........!
Play_v1.01_TA brick fix UPDATE.ftf

lorddraps said:
Hello everyone, After attempting to upgrade Gingerbread to ICS on my Xperia Play I used the Testpoint to unblock the bootloader..it turns out that it is now bricked...brilliant of me, I know..using the testpoint it did allow me to use the S1tool and it finds it, however it says that it gives me the Not recognized simlock certificate error message. I used the Sony Bootloader unlock page and ran it with fastboot and it tells me that the phone is already unlocked and using *#*#7378423#*#* it says the bootloader unlock YES... I have already tried flashing the OS, it says that it´s done it but it ignores the simlock.ta and it still wont boot. All I get is a brief vibration and no led. I managed to install the ADB drivers and could enter Fastboot mode, I flashed the kernel and it recognizes it when I open Flashboot but still no boot. What can I do??
In this thread named "simlock.ta problem ignored by flashtool" it says that Mr Alejandrissimo told someone how to unlock it for 10.00, I´m not sure if that may be the solution. Can someone tell me please how to contact him so I can get that information? I´m really lost here I would definitely appreciate the help.
Thank you for your time and I apologize for the long message, I just wanted to provide as much information as I could.
Click to expand...
Click to collapse
It's completely normal for the flashtool to ignore the "simlock.ta". Now when you search in the service menu you have the possibility to unlock your bootloader "bootloader unlock YES". When you do it it's going to be: "bootloader unlocked YES".
You must put the device in fastboot mode by pressing the volume down button then connecting the micro USB to your phone (the USB part should already be in). Then you have a blue led notification. try using adb and search for this file "twrp2.4.3-mint" in the forum. extract the boot.img then flash it using fastboot flash boot boot.img (do a little search how to do it manually). Now you should have the touch version of
TWRP recovery. Put the zip image of any ROM on a sim card then use the TWRP to flash it and get you phone running fingers-crossed.
For the SIM card, i did have another pb related to the SIM card holder pins (contact pbs)...
Anyway, good luck.

Thank You
Jalalben said:
It's completely normal for the flashtool to ignore the "simlock.ta". Now when you search in the service menu you have the possibility to unlock your bootloader "bootloader unlock YES". When you do it it's going to be: "bootloader unlocked YES".
You must put the device in fastboot mode by pressing the volume down button then connecting the micro USB to your phone (the USB part should already be in). Then you have a blue led notification. try using adb and search for this file "twrp2.4.3-mint" in the forum. extract the boot.img then flash it using fastboot flash boot boot.img (do a little search how to do it manually). Now you should have the touch version of
TWRP recovery. Put the zip image of any ROM on a sim card then use the TWRP to flash it and get you phone running fingers-crossed.
For the SIM card, i did have another pb related to the SIM card holder pins (contact pbs)...
Anyway, good luck.
Click to expand...
Click to collapse
I greatly appreciate your information, Alejandrissimo helped me fix my phone. Apparently Im having HW trouble with my touchpads and the front camera but other than that the phone boots ok and works good.

lorddraps said:
I greatly appreciate your information, Alejandrissimo helped me fix my phone. Apparently Im having HW trouble with my touchpads and the front camera but other than that the phone boots ok and works good.
Click to expand...
Click to collapse
I too have this problem.Who is Alejandrissimo? How can I contact and get a help from him? Pls help

LT26i Bootloader unlockable - No
COPIED FROM OTHER THREAD " I used the Sony Bootloader unlock page and ran it with fastboot and it tells me that the phone is already unlocked and using *#*#7378423#*#* it says the bootloader unlock YES.."
But i have met another state which couldn't be found on any website.
My phone bootloader unlock = NO (Using LT26i on Android 4.1.2)
Help on rooting and bootloader unlocking (Everything on internet has already been tried).

xperia arc s lt18i booting
i flashed my xperia sony arc s lt18i with 4.1.B.0.431 official stock firmware. but its taken ages in booting. like how many hours it will take to boot finish

simlock.ta
Hi there,
I flashed stock rom using the Flashtool but didnt exclude simlock .ta (on the xperia M2). since then my phone has been simlocked.
When I connect to Flashtool it shows that the phone is unlocked also I am able to flash ftf firmwares but when I try to flassh a .img file it gives me Failure message. The same thing happens when I try to flash using the fastboot.
Emma also shows that the phone is locked!
now everything except the simcard works ok.
could you please help me to solve this problem?
cheers

Questioner
Can someone exactly explain what is simlock.ta?

ModiF said:
Hi there,
I flashed stock rom using the Flashtool but didnt exclude simlock .ta (on the xperia M2). since then my phone has been simlocked.
When I connect to Flashtool it shows that the phone is unlocked also I am able to flash ftf firmwares but when I try to flassh a .img file it gives me Failure message. The same thing happens when I try to flash using the fastboot.
Emma also shows that the phone is locked!
now everything except the simcard works ok.
could you please help me to solve this problem?
cheers
Click to expand...
Click to collapse
Any solution for this? I have the same problem with my xperia C5. Everthing works except de simcard, the phone always asks for Simlock code.

lonboy said:
Any solution for this? I have the same problem with my xperia C5. Everthing works except de simcard, the phone always asks for Simlock code.
Click to expand...
Click to collapse
lonboy said:
Hi, my phone got locked after flashing ftf as yours, I read your post... So is simlocked, I've tried many methods but nothing works, have you find any solution? Thank You
I have 1.ta and 2.ta files but don't know how to restore.
Click to expand...
Click to collapse
Unfortunately no,
It seems that the developers who already know the solution prefer to watch us!
Also I didnt have a good response from Sony Service!
The only way that I didnt try is to send your phone to the Sony repair center.

I ALSO HAVE THE SAME PROBLEM WITH MY XPERIA V T25I
I just updated my Xperia V to latest android 4.3 via flashtool.
log file said
This file is ignored : simlock.ta
and now my xperia V Sim / network services stopped and it started asking network unlock PIN.
before update , it was perfectly working and was unlocked
if anybody finds solution , pls let me know

Can't unlock bootloader, boots into TWRP

New Problem:
i want to sell the phone and bring it back to Stock (to OxygenOS) but the problem is, that the phone won't unlock the bootloader, everytime i use "fastboote oem unlock" it boots into TWRP recovery?!?! And device status says "...locked"
Solved problem:
[problem 2]
I got my OPO back to life but i only can install CM11 on the phone, when i try to install cm12/13 it stucks at the cyanogen Logo?! Any suggestions? Is there anything i missed? I am upgrading via Fasboot.
[problem 1]
Hello,
i have a problem with a OPO, it wont start and dont give any signs when i try to charge it. When i connect it to the computer it will be recognized as "unknown usb device" (Failed to get Deviceinformation). Do someone have any solutions?

Spacket said:
Hello,
i have a problem with a OPO, it wont start and dont give any signs when i try to charge it. When i connect it to the computer it will be recognized as "unknown usb device" (Failed to get Deviceinformation). Do someone have any solutions?
Click to expand...
Click to collapse
Can you boot into fastboot mode? It doesn't take much battery to boot into fastboot mode and can might even boot if you have 0% battery.

Tried, the problem is, that the display won't get on, even when i try to charge it. It only gives some living signs when i connect it to the computer (after 18-20secs) Windows tell me, the device can't be recocnized properly
EDIT: Fixed via QFIL

New Problem:
I got my OPO back to life but i only can install CM11 on the phone, when i try to install cm12/13 it stucks at the cyanogen Logo?! Any suggestions? Is there anything i missed? I am upgrading via Fasboot.

Spacket said:
New Problem:
I got my OPO back to life but i only can install CM11 on the phone, when i try to install cm12/13 it stucks at the cyanogen Logo?! Any suggestions? Is there anything i missed? I am upgrading via Fasboot.
Click to expand...
Click to collapse
Follow this and you should be good.
If that does not work follow this and use the tools provided there instead of QFIL.

Stjinchan said:
Follow this and you should be good.
If that does not work follow this and use the tools provided there instead of QFIL.
Click to expand...
Click to collapse
Thanks for the links, i managed to Install CM13 with one code line from this thread: https://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
BUT, i want to sell the phone and bring it back to Stock (to OxygenOS) but the problem is, that the phone won't unlock the bootloader, everytime i use "fastboot oem unlock" it boots into TWRP recovery?!?! And device status says "...locked"
It worked some time, as you can see i installed TWRP and CM, so i dont know why it's not working now
GOOOOOD fails after fails hahaha

No one have an idea?

Spacket said:
No one have an idea?
Click to expand...
Click to collapse
Why not just flash oxygen os 3.1.4 port (its pretty much bugless) and sell? You don't need to have locked boot loader for that.

need bootloop help please

So far I always found answers to all my questions here without ever asking. This forum is awsome! Thanks to everyone here doing good work!
My problem: I have the European version of the Honor View 10. I opened bootloader, I installed the Magisk correctly with the 15.4 version, worked all fine. (thank you topjohnwu)
Then MY mistake ... I wanted to install Xposed Installer. I was not concentrated that moment and took the wrong version! From my other Honor phone (android 6.0, version 89, arm64). Absolutely stupid!
Phone restarted ... bootloop ... and goes into eRecovery. I tried everything I could there, clear dalvik cache, factory reset. > no change!
Then I thought ok, connect to PC, safe mode ... adb ... but no success. adb devices brings no result. PC does not find my phone anymore. I hoped I could get into my phone by connecting with PC, but it seems I am unable. So I can not help myself this way.
Next try was to force the phone to update with SD card. I only found asian update software, but I already did not care. I want to save my phone. Update starts, but after 5% it stops, update fail.
Now I hope that someone here can help. I have no idea what else I could do. Best regards, Markus

mark_at said:
So far I always found answers to all my questions here without ever asking. This forum is awsome! Thanks to everyone here doing good work!
My problem: I have the European version of the Honor View 10. I opened bootloader, I installed the Magisk correctly with the 15.4 version, worked all fine. (thank you topjohnwu)
Then MY mistake ... I wanted to install Xposed Installer. I was not concentrated that moment and took the wrong version! From my other Honor phone (android 6.0, version 89, arm64). Absolutely stupid!
Phone restarted ... bootloop ... and goes into eRecovery. I tried everything I could there, clear dalvik cache, factory reset. > no change!
Then I thought ok, connect to PC, safe mode ... adb ... but no success. adb devices brings no result. PC does not find my phone anymore. I hoped I could get into my phone by connecting with PC, but it seems I am unable. So I can not help myself this way.
Next try was to force the phone to update with SD card. I only found asian update software, but I already did not care. I want to save my phone. Update starts, but after 5% it stops, update fail.
Now I hope that someone here can help. I have no idea what else I could do. Best regards, Markus
Click to expand...
Click to collapse
Did you already try ro flash ramdisk and system sith stock images via fastboot?

alohahe3000 said:
Did you already try ro flash ramdisk and system sith stock images via fastboot?
Click to expand...
Click to collapse
I would flash anything ... if I could! That is my problem at the moment and I can not solve it.
When I start phone I get into Huawei eRecovery after two tries to boot > does not help!
When I connect to PC > phone gets not detected! (during boot try it gets connected shortly ... but then gets disconnected after some seconds, in between I can not get into phone via PC)
So when I would want to use fastboot .... not possible because of that issue. I tried to connect in fastboot mode ... but no difference. Actually I do not understand why I can not connect to PC anymore!
The only way I can imagine now is flash or update something via SD card. I tried with asian update.zip, but it will only go to 5% .... and then ends.
But to be honest ... I am not very optimistic about finding any solution. I think only some very smart pro from this site might have an idea. But not sure if these guys read questions about bootloops.

mark_at said:
Next try was to force the phone to update with SD card.
Click to expand...
Click to collapse
Try to flash via Fastboot the stock rom... do a full wipe and reboot.
here the link to the stock ROM:
https://mega.nz/#!W9hjiTgZ!_ZGq7V83bkWPF_Ue7_c41wVXNrQ_YjnsQUxRS0_MevU

Taobaibai said:
Try to flash via Fastboot the stock rom... do a full wipe and reboot.
Click to expand...
Click to collapse
Thanks for the link. But how can I flash via fastboot when my phone is not detected from the PC? That is my main problem at the moment!
That is why I wrote about all things I had tried already. And being unable to connect to the computer is really worrying me!
"adb devices" will not find my phone!

mark_at said:
Thanks for the link. But how can I flash via fastboot when my phone is not detected from the PC? That is my main problem at the moment!
That is why I wrote about all things I had tried already. And being unable to connect to the computer is really worrying me!
"adb devices" will not find my phone!
Click to expand...
Click to collapse
You have to boot into fastboot modus. When booting, push power and Volume down button. A white screen appears if device is connected with PC.
Then try "fastboot devices". If your device is displayed, you can flash with "fastboot flash" system image. Stock system.img download link can be found in AOSP thread, second post.

alohahe3000 said:
You have to boot into fastboot modus. When booting, push power and Volume down button. A white screen appears if device is connected with PC.
Then try "fastboot devices". If your device is displayed, you can flash with "fastboot flash" system image.
Click to expand...
Click to collapse
Exactly
alohahe3000 said:
Stock system.img download link can be found in AOSP thread, second post.
Click to expand...
Click to collapse
Or just use my link. I copied it from the AOSP Thread

I managed to get my phone displayed when I entered fastboot devices.
And I managed to flash the img!! Hurra !!
Thank you very very much to everyone here helping me ...
I thought that nothing would work because when I typed "abd devices" nothing happened. But when I typed "fastboot devices" the phone was there.

mark_at said:
I managed to get my phone displayed when I entered fastboot devices.
And I managed to flash the img!! Hurra !!
Thank you very very much to everyone here helping me ...
I thought that nothing would work because when I typed "abd devices" nothing happened. But when I typed "fastboot devices" the phone was there.
Click to expand...
Click to collapse
It wasn't so difficult.
Viel Spaß mit dem Smartphone!!!

one more thing I have to add:
after flashing the system.img from the link above .... I have FRP lock .... that was not before.
does it mean I have to relock my bootloader and then unlock it once again? In some other thread I found that information.

mark_at said:
one more thing I have to add:
after flashing the system.img from the link above .... I have FRP lock .... that was not before.
does it mean I have to relock my bootloader and then unlock it once again? In some other thread I found that information.
Click to expand...
Click to collapse
and now I relocked bootloader .... and guess what? bootloop again ... and I can not unlock it again, because I did not think about enable OEM unlock! It says necessary to unlock FRP before.
I am terribly sorry for being such an idiot!!

mark_at said:
and now I relocked bootloader .... and guess what? bootloop again ... and I can not unlock it again, because I did not think about enable OEM unlock! It says necessary to unlock FRP before.
I am terribly sorry for being such an idiot!!
Click to expand...
Click to collapse
Never ever relock bootloader untill you have a backup plan. We have dload method till emui 7 buut not sure on EMUI 8 so can't suggest you anything at the moment. Someone played with EMUI 8 can guide you through it.

I understand that I was not allowed to relock bootloader! I feel awful and stupid about it ... believe me!

I was able to erase FRP with HCU client from DC Phoenix.
After that I was in phone again
And afterwards I could open the bootloader again.
Halleluja!!
Thanks for everyone's help here ...

Help - Bricked (accidentally locked bootloader with TWRP installed)

It was late and I was cleaning up my old OP5T, getting it ready to sell. I thought I had plugged in my OP5T, but I still had my OP6 plugged in when I ran "fastboot oem lock". Now it won't boot and I can't unlock it (I'm assuming because I can't get into the OS and "enable OEM unlocking" anymore).
Is there anything I can do?

try using search next time because its already been talked abput here https://forum.xda-developers.com/oneplus-6/help/relock-bootloader-t3798135

Actually, I DID read that. I didn't just roll off the cabbage truck. If you have time to post snippy replies (I also searched YOUR post history), then maybe you can point out where in that thread the answer to my question is. I could see if there was a thread where this specifically happened, or if it had been talked about over and over, but I couldn't find one. You do know this is a fairly new device, right? TBH, you're just being rude. To count on someone to hit the right search terms for a single thread where the info exists is just asinine.
1) I have not seen anyone with this situation on the OP6 yet
2) The OP5T had an unbrick tool
3) Most phones have a way to restore the OS to factory
If it can't be restored without calling OnePlus, then why not just say so? I'll answer for you, it's because you actually enjoy replying in such a manner. Grow up.

Have you tried the mega unbrick guide?
https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051

Flapjack said:
It was late and I was cleaning up my old OP5T, getting it ready to sell. I thought I had plugged in my OP5T, but I still had my OP6 plugged in when I ran "fastboot oem lock". Now it won't boot and I can't unlock it (I'm assuming because I can't get into the OS and "enable OEM unlocking" anymore).
Is there anything I can do?
Click to expand...
Click to collapse
I don't think relocking your bootloader will disable the "enable OEM unlock" toggle in the OS. You may just be able to unlock your bootloader as normal again. You should be able to use the fastboot recovery method to restore your OS.

[email protected] said:
Have you tried the mega unbrick guide?
https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
Click to expand...
Click to collapse
I did, but I got the "software image does not exist" error. Does it matter whether I downloaded the 5.13 or 5.15 vesion?
mikex8593 said:
I don't think relocking your bootloader will disable the "enable OEM unlock" toggle in the OS. You may just be able to unlock your bootloader as normal again. You should be able to use the fastboot recovery method to restore your OS.
Click to expand...
Click to collapse
I tried several times. It throws the following error, which when searched for, always seemed to be someone forgetting to enable OEM unlocking in settings:
Code:
FAILED (remote: oem unlock is not allowed)

Success! I was able to get it to work with the drivers from this post. No other drivers worked. I also forced the COM port to the first available (in my case, COM1) vs the one it popped up on. Until I did that, I would just get a huge list of ports that had no device attached. Once I had it on COM1, it was the only device that showed up in the list. The first time after that, I got a "Sahara Communication Failed" error, but it went away after rebooting the phone back into EDL mode again.
Thanks for the help!

Flapjack said:
Success! I was able to get it to work with the drivers from this post. No other drivers worked. I also forced the COM port to the first available (in my case, COM1) vs the one it popped up on. Until I did that, I would just get a huge list of ports that had no device attached. Once I had it on COM1, it was the only device that showed up in the list. The first time after that, I got a "Sahara Communication Failed" error, but it went away after rebooting the phone back into EDL mode again.
Thanks for the help!
Click to expand...
Click to collapse
Hi buddy,
I tired to relock the bootloader and success in that but the phone stuck at fastboot mode, neither restarting to system nor to anything. Kindly help me if i can flash the stock rom in locked bootloader is so how.
THanks in adv

Did you try msm download tool ?

My OnePlus was bricked and it's bootloader is locked too, I have tried most of the steps like msm and those Bat files etc. But error is coming
"Remote : Flashing is not allowed in locked state"
Even tried that all in one tool that also can't unlock my bootloader
Now plz someone show me steps it will be a great help

Fastboot, Samsung Galaxy A51

Hello, i wanted to ask how to fix the fastboot mode.
Everytime when i try to access it, it just says "Entering Fastboot..."and thats all.
I dont want to close it, thats not my problem, i just wanna flash a recovery.img, and the fastboot seems not working. Any ideas?

M3DUS4 said:
Hello, i wanted to ask how to fix the fastboot mode.
Everytime when i try to access it, it just says "Entering Fastboot..."and thats all.
I dont want to close it, thats not my problem, i just wanna flash a recovery.img, and the fastboot seems not working. Any ideas?
Click to expand...
Click to collapse
this could be because the galaxy A51 wasnt built with fastboot, and the code to launch this option was just reused from a different device, or because something isnt connecting properly.

Hello, I have the same ... Android 11 (and currently 12) (from Frija). So it is not the fault of incorrect configuration or with connecting. Only something is wrong with this phone ...

I have this device and this solved it for me:
Enable OEM unlocking in developer settings
Shut down the phone
Hold volume up and volume down
Plug in a USB cable connected to a computer (the computer being turned on)
Keep holding
You're in download mode!
Side note: This might not work in USA or Canada, I am from europe and it works here. I have no idea if it works in another region. Also, you can't just flash a recovery.img on Samsung since there is no real "fastboot", you have to use download mode and Odin.

But I know how to enter download mode... Problem is Fastboot mode...

There is no fastboot mode on a modern Samsung device. If there is, it's fake and you cannot flash anything with it. As you can see even from Wikipedia, Odin is the Samsung replacement of fastboot.
So no fastboot, only download mode.
If a guide is saying to use fastboot, it is not compatible with Samsung.
If you would tell me why you specifically need fastboot, I'll be happy to tell you how you can do it with Odin, if possible.

Because I have Samsung Galaxy A51 5G (A516B) with new Android 12 and I can't do a root! Because I can't upload TWRP (custom recovery) because I haven't OEM unlock option in Deveoper Option. I tried trick with set back date by 7days but not succes. Everything I;ve metioned here - I did at my phone with Android 11.
And... I have read that I can turn this fu**ing OEM option by comend at ADB: fastboot oem unlock.
Phew ...
So this fastboot method is the last method to do a root with my phone.

Upload TWRP by Odin in download mode -ends red warning - of corse...
Have you any ideas?
I would be grateful for help...

I have read this fastboot method at:
How to Unlock Bootloader On Samsung Galaxy Phones [EASY GUIDE]
Are you looking for a Complete tutorial on How To Unlock Bootloader on Samsung Galaxy Phones? If yes, then you have come to the right place.
www.guidetoroot.com

Yeah, that guide is not relevant on any modern Samsung device. Besides, even if it was, which it isn't, you would first need to enable OEM unlocking from the Developer Settings.
But the fact that you don't have an option for OEM unlock is weird, since I have the exact same device model and it is there for me.
May I ask what is your region and is your phone locked to a telephone carrier?

My region is PLS - Poland. And not - phone is not locked. Have you the newest system Android 12?

Yes, I do. It's weird that there isn't even an option for you.
I'll try to come up with some new ideas if I have time...

I'll be glad for it...

Hej, do you have any idea?

stanwin said:
Hej, do you have any idea?
Click to expand...
Click to collapse
Have you tried everything listed here?

BloodyFruitDestroyer said:
Have you tried everything listed here?
Click to expand...
Click to collapse
Yes, I did. Evething exept the last one...

You could try it. It might be risky, but it's the only option I personally can come up with right now.

I've tried this option but Odin stuck on "files verification". Any help?

have any of you encountered this problem?
And how did you solve it?

You can also try searching for combination firmware for your device online