Related
I tried to root my phone today by using the Nexus 4 toolkit. In the process of rooting the phone, the use connection is physically disconnect by myself well it was an accident. After that, I only got unlocked bootloader, but I am not be able to get the recovery and the SU in the phone. When I try to repeat the steps, it is stucking at " cannot connect device" or sometimes "failed ... unknown error" or even "protocol error"(if I remember correctly. It seems that the connection is gone between the phone and the desktop under the fastboot mode. But under the normal Android OS, I am able to connect my phone to desktop to do the data transfer things.
I am seeking for help here. I hope I explain my problem properly that you guys can understand. Here is error I got sometime when I connect my phone to PC.
The button is OK in the pic.
hilts425 said:
I tried to root my phone today by using the Nexus 4 toolkit. In the process of rooting the phone, the use connection is physically disconnect by myself well it was an accident. After that, I only got unlocked bootloader, but I am not be able to get the recovery and the SU in the phone. When I try to repeat the steps, it is stucking at " cannot connect device" or sometimes "failed ... unknown error" or even "protocol error"(if I remember correctly. It seems that the connection is gone between the phone and the desktop under the fastboot mode. But under the normal Android OS, I am able to connect my phone to desktop to do the data transfer things.
I am seeking for help here. I hope I explain my problem properly that you guys can understand. Here is error I got sometime when I connect my phone to PC.
The button is OK in the pic.
Click to expand...
Click to collapse
Accidently hit the thanks button
The phone`s bootloader is allready unlocked.
- Is the phone recognized in adb and fastboot mode? If not install the 0.72 usb naked drivers.
- Flash CWM recovery in fastboot mode from here http://clockworkmod.com/rommanager, choose touche or non touch.
- flash superSU 1.20 from here http://forum.xda-developers.com/showthread.php?t=1538053 in CWM recovery.
- Install BusyBox from Google Play.
- Done.
gee2012 said:
Accidently hit the thanks button
The phone`s bootloader is allready unlocked.
- Is the phone recognized in adb and fastboot mode? If not install the 0.72 usb naked drivers.
- Flash CWM recovery in fastboot mode from here http://clockworkmod.com/rommanager, choose touche or non touch.
- flash superSU 1.20 from here http://forum.xda-developers.com/showthread.php?t=1538053 in CWM recovery.
- Install BusyBox from Google Play.
- Done.
Click to expand...
Click to collapse
how do I flash cwm in fastboot?
hilts425 said:
how do I flash cwm in fastboot?
Click to expand...
Click to collapse
Install the android sdk platform-tools and once installed:
- open cmd terminal and type: adb reboot bootloader
- type: fastboot devices and you should see a serial number if the usb drivers are nstalled correctly
- then type: fastboot flash recovery recovery-(name of the recovery).img
Read some threads to get familiar with your phone and to learn how to flash, root, use adb and it`s commands etc etc.
gee2012 said:
Accidently hit the thanks button
The phone`s bootloader is allready unlocked.
- Is the phone recognized in adb and fastboot mode? If not install the 0.72 usb naked drivers.
- Flash CWM recovery in fastboot mode from here http://clockworkmod.com/rommanager, choose touche or non touch.
- flash superSU 1.20 from here http://forum.xda-developers.com/showthread.php?t=1538053 in CWM recovery.
- Install BusyBox from Google Play.
- Done.
Click to expand...
Click to collapse
the official recovery does not work now! Any ideas?
hilts425 said:
the official recovery does not work now! Any ideas?
Click to expand...
Click to collapse
Yes it works, but it will not flash the SU zip. You need a custom recovery for that.
gee2012 said:
Yes it works, but it will not flash the SU zip. You need a custom recovery for that.
Click to expand...
Click to collapse
OK when I choose the recovery I only appears the android robot with a "!" and I can not do nothing there. Is this a bad sign?
hilts425 said:
OK when I choose the recovery I only appears the android robot with a "!" and I can not do nothing there. Is this a bad sign?
Click to expand...
Click to collapse
ok when i flash the recovery in the cmd
it says
failed (command write failed unknown error.)
So I've bought this phone a year ago and I've found out recently that its rooted.
I was trying to update to 4.4.3 and stuck at (entering recovery now)..
I even tried factory reset several times and stuck at the same screen, and as a result I can't hear in-call sound and I don't know what to do anymore.
At the boot loader screen it says
*Tampered*
*unlocked*
And S-on
Any chance I can get it updated and working?? :angel:
Sam087 said:
So I've bought this phone a year ago and I've found out recently that its rooted.
I was trying to update to 4.4.3 and stuck at (entering recovery now)..
I even tried factory reset several times and stuck at the same screen, and as a result I can't hear in-call sound and I don't know what to do anymore.
At the boot loader screen it says
*Tampered*
*unlocked*
And S-on
Any chance I can get it updated and working?? :angel:
Click to expand...
Click to collapse
Flash stock recovery and try again only stock recovery can flash update not twrp,philz,cmw
sayad1 said:
Flash stock recovery and try again only stock recovery can flash update not twrp,philz,cmw
Click to expand...
Click to collapse
and how to flash stock recovery? I'm all new to this.. thanks in advance.
Sam087 said:
and how to flash stock recovery? I'm all new to this.. thanks in advance.
Click to expand...
Click to collapse
Which veriant of you mean at&t,Verizon,sprint or other ??
Do you have done setting up and&fastboot already on your desktop or laptop??
sayad1 said:
Which veriant of you mean at&t,Verizon,sprint or other ??
Do you have done setting up and&fastboot already on your desktop or laptop??
Click to expand...
Click to collapse
I have zain netwok on Unlocked HTC m8.
and yes I have adb fastboot already on my laptop
Sam087 said:
I have zain netwok on Unlocked HTC m8.
and yes I have adb fastboot already on my laptop
Click to expand...
Click to collapse
1.Put the recovery file (*. img) into a fastboot / adb folder, and open Windows Command prompt (CMD) from there.
2.Make sure the M8 drivers already installed on your computer.
3.Connect the phone into computer via USB.
Now put your phone into fastboot mode, by turning it off first, then press and hold Volume down and power button. After that, choose Fastboot mode.
5.Run the following command to CMD window:
fastboot flash recovery FileName.img
You should change the “FileName” to match with your own.
6.Now reboot system.
fastboot reboot
7.Once fully boots up, your HTC One M8 should have stock recovery, now take an OTA then apply it.
https://mega.nz/#!aAxWWTCY!TLjZ-Q9NQVGFj0GQ7AHCSxtKG-9yS5LtKsvvbS3ExBM
sayad1 said:
1.Put the recovery file (*. img) into a fastboot / adb folder, and open Windows Command prompt (CMD) from there.
2.Make sure the M8 drivers already installed on your computer.
3.Connect the phone into computer via USB.
Now put your phone into fastboot mode, by turning it off first, then press and hold Volume down and power button. After that, choose Fastboot mode.
5.Run the following command to CMD window:
fastboot flash recovery FileName.img
You should change the “FileName” to match with your own.
6.Now reboot system.
fastboot reboot
7.Once fully boots up, your HTC One M8 should have stock recovery, now take an OTA then apply it.
https://mega.nz/#!aAxWWTCY!TLjZ-Q9NQVGFj0GQ7AHCSxtKG-9yS5LtKsvvbS3ExBM
Click to expand...
Click to collapse
Thanks it worked just fine.. updating to marshmallow now
Hello all, I have a Lenovo a6000 smartphone. It was owned by my friend. She had a problem with the android os, so she went to a local store and the there it got hard bricked. Now if I turn it on it only vibrates once. no backlight or any picture. If I press and hold vol- and power buttons together LCD backlight turns on but no display. then it goes off and then again turns on. PC does not detect it. Can anyone help me getting it out from this state?
arnab8820 said:
Hello all, I have a Lenovo a6000 smartphone. It was owned by my friend. She had a problem with the android os, so she went to a local store and the there it got hard bricked. Now if I turn it on it only vibrates once. no backlight or any picture. If I press and hold vol- and power buttons together LCD backlight turns on but no display. then it goes off and then again turns on. PC does not detect it. Can anyone help me getting it out from this state?
Click to expand...
Click to collapse
Try qfil method
JovanSijacki said:
Try qfil method
Click to expand...
Click to collapse
Can you give the link please..... please note the phone is no longer detected in pc
arnab8820 said:
Can you give the link please..... please note the phone is no longer detected in pc
Click to expand...
Click to collapse
You need to have adb and fastboot drivers for your phone to correctly get detected.
Here's the LINK FOR QFIL TUTORIAL. You'll need another set of drivers called as the QCOM drivers which are mentioned in the tutorial from the above link.
Hope this helps.
I already have installed the drivers. Still not detected. Even the device manager does not show a device is connected
sasukay said:
You need to have adb and fastboot drivers for your phone to correctly get detected.
Here's the LINK FOR QFIL TUTORIAL. You'll need another set of drivers called as the QCOM drivers which are mentioned in the tutorial from the above link.
Hope this helps.
Click to expand...
Click to collapse
Here the phone connects in Qualcomm hs-USB...... mode. But in case of mine, it does not even show up in the device manager.
arnab8820 said:
Here the phone connects in Qualcomm hs-USB...... mode. But in case of mine, it does not even show up in the device manager.
Click to expand...
Click to collapse
You should try changing the usb cable you are using. Or maybe that guy in the local repair shop didn't put the sub PCB board back correctly.
sasukay said:
You should try changing the usb cable you are using. Or maybe that guy in the local repair shop didn't put the sub PCB board back correctly.
Click to expand...
Click to collapse
There is only one pcb in it. Changing the cable does not make a difference
One update. I can get into the fastboot mode. But the bootloader is locked. What to do?
arnab8820 said:
One update. I can get into the fastboot mode. But the bootloader is locked. What to do?
Click to expand...
Click to collapse
Lenovo A6000 doesn't come with a locked bootloader B-l
If you can boot into fastboot then you should flash twrp from it depending on the current android version of the device. If it had been on kitkat flash this TWRP v2.8.6.0 or if it has been updated to lollipop then flash the latest TWRP v3.1.0.
For this you need to first have the fastboot drivers installed and also the minimal adb and fastboot tool. Then place the required TWRP in that folder, better rename the file to 'recovery.img' and then in the CMD window which you open by Shift + Right Click first type
Code:
fastboot devices
To check whether your device is detected by the tool and haa got drivers installed correctly.
Later, if successful, type in
Code:
fastboot flash recovery recovery.img
Then you'll have TWRP recovery installed.
Then flash any ROM on the device using it.
sasukay said:
Lenovo A6000 doesn't come with a locked bootloader B-l
If you can boot into fastboot then you should flash twrp from it depending on the current android version of the device. If it had been on kitkat flash this TWRP v2.8.6.0 or if it has been updated to lollipop then flash the latest TWRP v3.1.0.
For this you need to first have the fastboot drivers installed and also the minimal adb and fastboot tool. Then place the required TWRP in that folder, better rename the file to 'recovery.img' and then in the CMD window which you open by Shift + Right Click first type
To check whether your device is detected by the tool and haa got drivers installed correctly.
Later, if successful, type in
Then you'll have TWRP recovery installed.
Then flash any ROM on the device using it.
Click to expand...
Click to collapse
Thanks! I will try it and post the results.
Btw are you sure it does not come with a locked bootloader? I tried to flash the stock recovery and got an error saying "unknown command or device is lock"
arnab8820 said:
Thanks! I will try it and post the results.
Btw are you sure it does not come with a locked bootloader? I tried to flash the stock recovery and got an error saying "unknown command or device is lock"
Click to expand...
Click to collapse
Yeah bro I'm 100% positive. I think unknown command is displayed when you flash the wrong version of recovery.
You can also try
Code:
fastboot boot recovery.img
Sometimes only this works which temporarily boots into the custom recovery.
sasukay said:
Yeah bro I'm 100% positive. I think unknown command is displayed when you flash the wrong version of recovery.
You can also try
Sometimes only this works which temporarily boots into the custom recovery.
Click to expand...
Click to collapse
Ok friend i will post the results tonight
sasukay said:
Lenovo A6000 doesn't come with a locked bootloader B-l
If you can boot into fastboot then you should flash twrp from it depending on the current android version of the device. If it had been on kitkat flash this TWRP v2.8.6.0 or if it has been updated to lollipop then flash the latest TWRP v3.1.0.
For this you need to first have the fastboot drivers installed and also the minimal adb and fastboot tool. Then place the required TWRP in that folder, better rename the file to 'recovery.img' and then in the CMD window which you open by Shift + Right Click first type
Code:
fastboot devices
To check whether your device is detected by the tool and haa got drivers installed correctly.
Later, if successful, type in
Code:
fastboot flash recovery recovery.img
Then you'll have TWRP recovery installed.
Then flash any ROM on the device using it.
Click to expand...
Click to collapse
Tried the above method but no luck it gives an error: "unknown command or device is lock".
arnab8820 said:
Tried the above method but no luck it gives an error: "unknown command or device is lock".
Click to expand...
Click to collapse
Try this with the CWM recovery too.
BTW does your device gets detected by fastboot devices command? Also, have you tried the QPST method?
sasukay said:
Try this with the CWM recovery too.
BTW does your device gets detected by fastboot devices command? Also, have you tried the QPST method?
Click to expand...
Click to collapse
Device gets detected by fastboot devices command. I cant try qpst because the device is not detected in any other mode except fastboot. I hv all the drivers installed
arnab8820 said:
Device gets detected by fastboot devices command. I cant try qpst because the device is not detected in any other mode except fastboot. I hv all the drivers installed
Click to expand...
Click to collapse
You've tried booting into Download mode? It requires you to press the VOL UP + POWER KEY, then you need to select the Download mode in it to perform flashing through QPST.
Also, you never mentioned what android version was the device on, earlier.
sasukay said:
You've tried booting into Download mode? It requires you to press the VOL UP + POWER KEY, then you need to select the Download mode in it to perform flashing through QPST.
Also, you never mentioned what android version was the device on, earlier.
Click to expand...
Click to collapse
If i press and hold vol up and power key together the phone only vibrates once and shows nothing. And i think my friend applied the lollipop update on it. She is not sure.
arnab8820 said:
If i press and hold vol up and power key together the phone only vibrates once and shows nothing. And i think my friend applied the lollipop update on it. She is not sure.
Click to expand...
Click to collapse
Try fastboot oem unlock
arnab8820 said:
Tried the above method but no luck it gives an error: "unknown command or device is lock".
Click to expand...
Click to collapse
I think you are missing something (maybe).
The command is "fastboot flash recovery recovery.img"
If the recovery files name is twrp.img then command will be "fastboot flash recovery twrp.img".
hi guys, my computer ( wins10) donset read adb device.
but i i use fastboot commands its able to list my devices, but ' adb devices' shows none listed? i am suck, might have soft brick it, able to boot into stock recocery. any suggestions?
oneplus 5 phone.
What are you trying to do?
Rhoban said:
What are you trying to do?
Click to expand...
Click to collapse
Was trying to update , but got stuck at boot screen .
Just flash the stock ROM with the stock recovery.
I can’t sideload it, “ adb not working “
Rhoban said:
Just flash the stock ROM with the stock recovery.
Click to expand...
Click to collapse
Files all courupted
With stock recovery you can't use adb sideload in windows 10.
If you're unlocked i would flash Codeworkx TWRP, download the OOS 5.0.1 Full Rom Zip, boot into TWRP, copy the zip to your phone or sideload the zip.
If you're not unlocked (and thus being unable to flash twrp) use windows 7 and sideload the zip.
You can download ADB drivers here
Can you boot? Turn on USB debugging , make sure that you allow the device when booted.
Do an advanced devices when in the OS make sure it's there.
Then you can install a TWRP recovery and do what you need to.
maikvitesse said:
With stock recovery you can't use adb sideload in windows 10.
If you're unlocked i would flash Codeworkx TWRP, download the OOS 5.0.1 Full Rom Zip, boot into TWRP, copy the zip to your phone or sideload the zip.
If you're not unlocked (and thus being unable to flash twrp) use windows 7 and sideload the zip.
You can download ADB drivers here
Click to expand...
Click to collapse
Hi bro, I am unlocked ! I mange to find a win7 pc. I ran both commands “adb devices” and “Fastboot devices”
Both shows me my devices number hence drivers are working fine.
Now do I flash twrp and sidleload? Because I can’t sideload in stock “error: *cant read zip*”. Do advice me!
PS: can boot into OS, no OS in system only recovery . USB debugging was on before boot loop happens! Thanks for all advices !
maikvitesse said:
With stock recovery you can't use adb sideload in windows 10.
If you're unlocked i would flash Codeworkx TWRP, download the OOS 5.0.1 Full Rom Zip, boot into TWRP, copy the zip to your phone or sideload the zip.
If you're not unlocked (and thus being unable to flash twrp) use windows 7 and sideload the zip.
You can download ADB drivers here
Click to expand...
Click to collapse
dladz said:
Can you boot? Turn on USB debugging , make sure that you allow the device when booted.
Do an advanced devices when in the OS make sure it's there.
Then you can install a TWRP recovery and do what you need to.
Click to expand...
Click to collapse
Hi ! USB debugging was turn on before boot loop happened. Can’t boot into OS , only recovery
lolitsryan96 said:
Hi bro, I am unlocked ! I mange to find a win7 pc. I ran both commands “adb devices” and “Fastboot devices”
Both shows me my devices number hence drivers are working fine.
Now do I flash twrp and sidleload? Because I can’t sideload in stock “error: *cant read zip*”. Do advice me!
PS: can boot into OS, no OS in system only recovery . USB debugging was on before boot loop happens! Thanks for all advices !
Click to expand...
Click to collapse
be sure your bootloader is unlocked
turn your phone into fastboot
open command prompt to the folder your twrp is in.
rename the twrp image file to recovery.img
do the following command: fastboot flash recovery recovery.img
after that boot into recovery
press adb sideload
on the computer, open command prompt to the folder where your zip file is in.
rename the rom zip file to rom.zip
do the following command: adb sideload rom.zip
done!
Thanks bro, I shall update you on the situation once I done, at work now.
Do I need to “open command promt “ at my sdk folder/plat-form tools?
maikvitesse said:
be sure your bootloader is unlocked
turn your phone into fastboot
open command prompt to the folder your twrp is in.
rename the twrp image file to recovery.img
do the following command: fastboot flash recovery recovery.img
after that boot into recovery
press adb sideload
on the computer, open command prompt to the folder where your zip file is in.
rename the rom zip file to rom.zip
do the following command: adb sideload rom.zip
done!
Click to expand...
Click to collapse
hi bro, sideload failed i think, i cant find sideload file. when the sideload end. its gave x1.00 something like that.
maikvitesse said:
be sure your bootloader is unlocked
turn your phone into fastboot
open command prompt to the folder your twrp is in.
rename the twrp image file to recovery.img
do the following command: fastboot flash recovery recovery.img
after that boot into recovery
press adb sideload
on the computer, open command prompt to the folder where your zip file is in.
rename the rom zip file to rom.zip
do the following command: adb sideload rom.zip
done!
Click to expand...
Click to collapse
attach image, successfully sideload but phone still in bootloop?
lolitsryan96 said:
attach image, successfully sideload but phone still in bootloop?
Click to expand...
Click to collapse
you need to wipe everything before flashing
maikvitesse said:
you need to wipe everything before flashing
Click to expand...
Click to collapse
just wipe, now re-sideloading. how it works. bloody nightmare dude.
maikvitesse said:
you need to wipe everything before flashing
Click to expand...
Click to collapse
still stuck at the boot loop, any advice
maikvitesse said:
you need to wipe everything before flashing
Click to expand...
Click to collapse
hi brother finally did it!
my oneplus 5 was encrypted totally forgot about hence need to wipe full back to factory stage, learn my lesson the hard way really grateful for your help!
ps; i am going to Holland on may-june for my euro trip! any places of interest in Holland?
lolitsryan96 said:
hi brother finally did it!
my oneplus 5 was encrypted totally forgot about hence need to wipe full back to factory stage, learn my lesson the hard way really grateful for your help!
ps; i am going to Holland on may-june for my euro trip! any places of interest in Holland?
Click to expand...
Click to collapse
nice good to hear!
haha, well tourists like Amsterdam so do visit that and visit The Hague/Scheveningen. I like these 3 places the most I think. Look up TripAdvisor for good attractions once you're there. do visit 'The Amsterdam Dungeon' don't miss that, I liked it very very much!
how to install the drivers?
maikvitesse said:
With stock recovery you can't use adb sideload in windows 10.
If you're unlocked i would flash Codeworkx TWRP, download the OOS 5.0.1 Full Rom Zip, boot into TWRP, copy the zip to your phone or sideload the zip.
If you're not unlocked (and thus being unable to flash twrp) use windows 7 and sideload the zip.
You can download ADB drivers here
Click to expand...
Click to collapse
Cannot adb to the phone in FASTBOOT. adb devices shows nothing when in FASTBOOT, but shows the device when in normal boot.
Hence I cannot upgrade TWRP from 3.2.1-1 to 3.2.3-0. Was trying this so to upgrade from beta23 to the beta 26, now 27 with which 3.2.1-1 seems to have problems.
A 2nd approach, just re-installing beta23 without Magisk18 gives the stock recovery which manages the beta27 install. But then I'm blocked from a Magisk18 install and still cannot use FASTBOOT mode to put TWRP back on.
Thought the adb drives could be old and sought new drivers, even assuming your link is to the most current I don't know how to get my Windows7 to use the zip file. Can you assist? This would let me put the latest TWRP, hence install Magisk18 and be rooted again!
Hello, I was curious if anyone could help me with unbricking my phone, my phone has no custom recovery installed, the bootloader is apparently unlocked (OEM unlocking is disabled), FRP lock is enabled, I cannot flash anything (Command not allowed), relock bootloader (Root type is at risk), Unlock bootloader (Command not allowed), any help would be appreciated.
Edit: I also cannot boot a from a recovery img locally using fastboot (Command not allowed)
EDIT: Fixed it using DC Pheonix and flashing VNS-L22C636B140 OEMINFO and flashing B160
Hi, try my way. https://forum.xda-developers.com/showpost.php?p=77307223&postcount=30 Just pick CxxxBxxx that suits your model. Try to unlock bootloader again via SRKTool, I think FRP must be unlocked too...
Check this also: https://forum.xda-developers.com/huawei-p9lite/help/p9-lite-bricked-please-help-t3415275
4uvak91 said:
Hi, try my way. https://forum.xda-developers.com/showpost.php?p=77307223&postcount=30 Just pick CxxxBxxx that suits your model. Try to unlock bootloader again via SRKTool, I think FRP must be unlocked too...
Check this also: https://forum.xda-developers.com/huawei-p9lite/help/p9-lite-bricked-please-help-t3415275
Click to expand...
Click to collapse
I cannot flash anything, so any of these do not help, thanks for trying I guess
wheellzzz said:
I cannot flash anything, so any of these do not help, thanks for trying I guess
Click to expand...
Click to collapse
Are you sure you run from inside the folder where adb.exe and fastboot.exe is? Boot to bootloader and use terminal pointed to fastboot.exe. Shift+right click -> open command line here. Make sure your devices is listed: adb devices. If device is shown: adb reboot bootloader, to reboot to bootloader. If not, install adb drivers / huawei drivers.
4uvak91 said:
Are you sure you run from inside the folder where adb.exe and fastboot.exe is? Boot to bootloader and use terminal pointed to fastboot.exe. Shift+right click -> open command line here. Make sure your devices is listed: adb devices. If device is shown: adb reboot bootloader, to reboot to bootloader. If not, install adb drivers / huawei drivers.
Click to expand...
Click to collapse
Yes I am sure, also, I have no way to access ADB since there is no recovery on the phone.
Only thing I can do is boot to that eRecovery screen with the option to download, reboot or shutdown. (Automatticly goes to here), or boot to bootloader
wheellzzz said:
Yes I am sure, also, I have no way to access ADB since there is no recovery on the phone.
Only thing I can do is boot to that eRecovery screen with the option to download, reboot or shutdown. (Automatticly goes to here), or boot to bootloader
Click to expand...
Click to collapse
Well if you can access to bootloader then you able to use fastboot commands. ADB is not related to recovery anyhow, you use windows command prompt to use adb and fastboot. IF FRP is locked, unlock bootloader again. I quiet don't understand how the command are not allowed or so. You are definitely doing something wrong.
4uvak91 said:
Well if you can access to bootloader then you able to use fastboot commands. ADB is not related to recovery anyhow, you use windows command prompt to use adb and fastboot. IF FRP is locked, unlock bootloader again. I quiet don't understand how the command are not allowed or so. You are definitely doing something wrong.
Click to expand...
Click to collapse
The problem is I cannot unlock bootloader again, flash anything or boot into any image in fastboot mode, I always get "ERROR: (Command not allowed)", attempting to relock the bootloader shows "ERROR: (Root type is at risk)"
EDIT: I have done some research for the dload method, If I want to dload to hopefully fix it, I'll need VNS-L22C636B381, but the official link from the hicloud is dead, if anyone could help me with that, that'd be great.
Last EDIT: Ended up scratching the above idea as it didn't work, gritted my teeth as I bought DC Phoenix and will update if it works out with the .APP from the latest package I found on firmware finder.