Related
Based on our official TWRP with some fixes and features
Changelog: 7-13
Add USB-OTG support
Brightness setting persists through reboots
EFS Backup and restore
Double tap to wake
Code:
Install:
In fastboot mode
fastboot flash recovery recovery.img
Download
Recovery flashable version here
Credits: Dees_Troy
dr87 said:
Based on our official TWRP with some fixes and features
Changelog: 7-13
Add USB-OTG support
Brightness setting persists through reboots
EFS Backup and restore
Double tap to wake
Mount and unmount issues *may* be fixed (I haven't been able to reproduce them)
Code:
Install:
In fastboot mode
fastboot flash recovery recovery.img
Download
Credits: Dees_Troy
Click to expand...
Click to collapse
Awesome job bro! Running like a champ!!
Sent from my One using XDA Premium 4 mobile app
Thanks a lot!
Now I can run Mahdi without problems!
thanks for this- but it's still not working- will i need to reflash madhi? i just fastbooted the recovery across and it boots into the recovery no worries and recognises all partitions but rom won't boot...
***edit*** it just booted up, about 5th attempt.. no boot animation though...ignore me...
Flashed recovery.img, bootet into recovery, no partitions..
Klarooo said:
Flashed recovery.img, bootet into recovery, no partitions..
Click to expand...
Click to collapse
Which rom were you running when you rebooted into recovery?
Stock, so CM11s.
mine still is not good. i treid to reboot to get it to hold the no hardware buttons. didn't reboot. tried about 10 times. eventually booted intot this new recovery and reflashed rom and booted it up. it's a bloody weird looking boot- no boot animation- made me think it was screwed again.
did you have to do anything to get it working again? Wipe entire device or just data partition?
Working good here, but I had no issues with the official build. I have an international version, 64GB OPO.
It's nice to see some additional features added, though.
Just helping out, packaged in a flashable zip for those with current CWM or TWRP recoveries, tested and working, enjoy everyone.
Flashed with the zip in the post above, worked flawlessly, was able to backup my EFS partition which is what I was looking to do. Thanks!
Chris123NT said:
Flashed with the zip in the post above, worked flawlessly, was able to backup my EFS partition which is what I was looking to do. Thanks!
Click to expand...
Click to collapse
Guys i wonder when you press efs restore is it
fastboot format modemst1 & st2
or
fastboot erase modemst1 & st2
or may be both? in that case in what order?
I flashed the one in OP, but the system does not see any partition ?
Can I flash 15th without bricking the phone
[EDIT] I tried a second time, and now it´s ok, partitions are there and backup is currently running
Any chance at adding F2FS support direct for this recovery for the ONE Plus?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Looks like the official .img version has been incremented to 2.7.1.1
More here: http://techerrata.com/browse/twrp2/bacon
A flashable zip for v2.7.1.1 would be nice.
Changelog? Hopefully they fixed those Partitions issues
2.7.1.1-Bacon Recovery Flashable zip
Mikey said:
2.7.1.1-Bacon Recovery Flashable zip
Click to expand...
Click to collapse
Question - now I ask this to see how you may do this and possibly help others from waiting for a zip. Now are you simply renaming the image file from TWRP to recovery.img and placing it inside an already created zip file for flashing. A zip file that of course was created for an earlier version of TWRP lets say
playya said:
Question - now I ask this to see how you may do this and possibly help others from waiting for a zip. Now are you simply renaming the image file from TWRP to recovery.img and placing it inside an already created zip file for flashing. A zip file that of course was created for an earlier version of TWRP lets say
Click to expand...
Click to collapse
Correct, easy huh
Delete the twrp.img......drag and drop the new img into the zip......dont uncompress the zip and compress it again.
I am going to do an experiment(flashing TWRP.img on boot partition and trying to root.) to backup stock recovery.img of Lollipop 5.1. To do this, I need stock boot.img(Kernel Version: 3.4.42-gccbac57) of system version 23.26.2. If there's someone who rooted system version 23.26.2 then take backup of boot.img using Rashr App(Download from here forum.xda-developers.com/showthread.php?t=2334554 ) and post that stock boot.img here.
If this experiment succeed then I will post stock recovery.img of lollipop 5.1.
UPDATE: I'm not going to do this experiment because temporary booting of twrp is now working on moto e. We can root device by temporary booting twrp and backup stock recovery.img
isn't there anyone who rooted 23.26.2 ?
I have 23.21.34 version i can give you if you want...
cksup said:
I have 23.21.34 version i can give you if you want...
Click to expand...
Click to collapse
It's simple, you just have to extract the boot.img from any ota zip (suggested the official OTA zip)
Do that and give him then.......it will be very good if he can make the 5.1 stock recovery
cksup said:
Do that and give him then.......it will be very good if he can make the 5.1 stock recovery
Click to expand...
Click to collapse
First of all, you must clarify who is referred to as 'him'?
Secondly, there is no method(according to me) by which you can make a stock recovery from a stock kernel. There are two files namely the boot.img and the recovery.img.
First one is the kernel and the second one is the recovery.
Use the ones you like.
Him meant the op
I don't know if one can make recovery from boot.img.......The op didn't say that either....He said and i quote "I am going to do an experiment to backup stock recovery.img of Lollipop 5.1. To do this, I need stock boot.img(Kernel Version: 3.4.42-gccbac57) of system "
So i thought by using some process he may be able to back up stock recovery....that is why i said like that
and BTW where are those .img files available @Rohitagni
cksup said:
Him meant the op
I don't know if one can make recovery from boot.img.......The op didn't say that either....He said and i quote "I am going to do an experiment to backup stock recovery.img of Lollipop 5.1. To do this, I need stock boot.img(Kernel Version: 3.4.42-gccbac57) of system "
So i thought by using some process he may be able to back up stock recovery....that is why i said like that
and BTW where are those .img files available @Rohitagni
Click to expand...
Click to collapse
U can find them in any zipped firmware files. By zipped firmware files, I mean the zips for stock firmware, or the update zips that many XDA users capture here from their rooted phones to help users who haven't received the OTA, enjoy the new OS, simply by sideloading.
cksup said:
I have 23.21.34 version i can give you if you want...
Click to expand...
Click to collapse
Thanks, but I want 23.26.2 version boot.img.
Rohitagni said:
It's simple, you just have to extract the boot.img from any ota zip (suggested the official OTA zip)
Click to expand...
Click to collapse
I think, we can't extract boot.img from ota zip.
Rohitagni said:
First of all, you must clarify who is referred to as 'him'?
Secondly, there is no method(according to me) by which you can make a stock recovery from a stock kernel. There are two files namely the boot.img and the recovery.img.
First one is the kernel and the second one is the recovery.
Use the ones you like.
Click to expand...
Click to collapse
I'm not making recovery.img from boot.img. I will use boot.img to make my device functional again because I'm going to flash TWRP.img on boot partition and try to root. If device gets root access then I can backup stock recovery.img because stock recovery.img is not over written in process of rooting.
I hope you succeed.........I try to get it from someone
And no @Rohitagni you can't extract boot.img from uploaded update zips but from full firmware zips,yes which is not available
I just saw in general section someone uploaded twrp backup of stock latest 5.1......I can flash that and give the boot.img tomorrow @EthicalHacker
cksup said:
I hope you succeed.........I try to get it from someone
And no @Rohitagni you can't extract boot.img from uploaded update zips but from full firmware zips,yes which is not available
I just saw in general section someone uploaded twrp backup of stock latest 5.1......I can flash that and give the boot.img tomorrow @EthicalHacker
Click to expand...
Click to collapse
I am extremely sorry, for misleading you guys! I just found out that the fsg.bin and the gpt.bin (with logo.bin, etc) are the only things that are available in those zips. So yes, @cksup, you are correct. Please provide him with the kernel, so that miracles can happen
cksup said:
I hope you succeed.........I try to get it from someone
And no @Rohitagni you can't extract boot.img from uploaded update zips but from full firmware zips,yes which is not available
I just saw in general section someone uploaded twrp backup of stock latest 5.1......I can flash that and give the boot.img tomorrow @EthicalHacker
Click to expand...
Click to collapse
That's fine.
I think, the twrp backup; you're talking about is Brazilian. So be careful.
any one found the way to flash twrp on stock 5.1 lollipop previous method don't work.
Ansh2000 said:
any one found the way to flash twrp on stock 5.1 lollipop previous method don't work.
Click to expand...
Click to collapse
Use latest twrp.img and SuperSU zip to root.
And if you have 23.26.2 version then you may help me by posting stock boot.img here.
check out #1st post of this thread.
EthicalHacker said:
Use latest twrp.img and SuperSU zip to root.
And if you have 23.26.2 version then you may help me by posting stock boot.img here.
check out #1st post of this thread.
Click to expand...
Click to collapse
Yes I am on 23.26.2 version but unable to flash. twrp, tried all version of twrp but result is same.
Ansh2000 said:
Yes I am on 23.26.2 version but unable to flash. twrp, tried all version of twrp but result is same.
Click to expand...
Click to collapse
Use twrp 2.8.7 recovery
forum.xda-developers.com/moto-e/orig-development/recovery-twrp-2-8-6-0-touch-recovery-t3100879
with following root guide
forum.xda-developers.com/showthread.php?t=2755336
Ansh2000 said:
Yes I am on 23.26.2 version but unable to flash. twrp, tried all version of twrp but result is same.
Click to expand...
Click to collapse
Hey before you flash TWRP can you do something ....... can you dump for recovery partition and save it in sd card and post it here ....
hey i have a XT1025 on the 5.1 ota update, untouched, and how can i root my device?
cksup said:
Hey before you flash TWRP can you do something ....... can you dump for recovery partition and save it in sd card and post it here ....
Click to expand...
Click to collapse
We can't dump stock recovery without root access and moto e has only one rooting method which is flashing custom recovery on recovery partition. It means we lose stock recovery when we get root access.
That's why I'm taking risk of above mentioned experiment to backup stock recovery.
lnasc256 said:
hey i have a XT1025 on the 5.1 ota update, untouched, and how can i root my device?
Click to expand...
Click to collapse
Check out post no. #16 of this thread.
I have a backup of stock 5.1( 23.26.2) kernel and recovery, I took backup from rashr app after rooting my moto e, and I didnt flash twrp for rooting I boot into twrp, should I upload stock kernel or recovery?
Sent from my Xperia E3 using XDA Free mobile app
I unlocked bootloader (critical aswell) today and installed twrp on my A3. The device is NOT rooted
Weird thing is I can't use my wifi anymore, anytime I try to toggle it on it just jumps back.
Anyone knows what caused this and how I can fix it?
felloguard123 said:
I unlocked bootloader (critical aswell) today and installed twrp on my A3. The device is NOT rooted
Weird thing is I can't use my wifi anymore, anytime I try to toggle it on it just jumps back.
Anyone knows what caused this and how I can fix it?
Click to expand...
Click to collapse
Did you flash any boot.img when installing twrp? Or after you installed twrp?
If you did that is more than likely the problem. Flash original stock boot.img from the same security patch date as your firmware and flash it in twrp and then flash twrp installer afterwards
It seems your boot.img corrupted. If you format data and wipe dalvik cache data and flash stock rom you will succeed i think
---------- Post added at 10:22 PM ---------- Previous post was at 10:18 PM ----------
https://c.mi.com/oc/miuidownload/detail?device=1900372
download official xiaomi mi a3 rom here. and flash it via pc and you will have brand new stock rom. Try it if you fail i will help you when i have free time
garylawwd said:
Did you flash any boot.img when installing twrp? Or after you installed twrp?
If you did that is more than likely the problem. Flash original stock boot.img from the same security patch date as your firmware and flash it in twrp and then flash twrp installer afterwards
Click to expand...
Click to collapse
I was stupid and thought I did it without a boot image untill I checked all of my commands again.
I used fastboot flash boot twrp-3.3.1-15-laurel_sprout-mauronofrio.img .
My phone was on V10.3.9.0 EUropean. But that image file is for twrp or is it also a boot.img? Not sure if this caused the problem? I'm very new to all of this so how can I find a stock boot.img of that version and how do I flash it again? I feel kinda lost right now.
Anyone can help me out with this?
felloguard123 said:
Anyone can help me out with this?
Click to expand...
Click to collapse
This phone has the recovery inside the boot partition, this is why you need to flash the boot partition, you do not need to flash it again normally, you just flash it to the other slot, boot twrp, go back on the original slot, flash twrp using the .zip file, idk where you should get the boot.img file, but lok online for it, maybe you will find it.
EDIT: https://github.com/AndroidDumps/xia...KQ1.190416.001-V10.3.9.0.PFQMIXM-release-keys
antoine62 said:
This phone has the recovery inside the boot partition, this is why you need to flash the boot partition, you do not need to flash it again normally, you just flash it to the other slot, boot twrp, go back on the original slot, flash twrp using the .zip file, idk where you should get the boot.img file, but lok online for it, maybe you will find it.
EDIT: https://github.com/AndroidDumps/xia...KQ1.190416.001-V10.3.9.0.PFQMIXM-release-keys
Click to expand...
Click to collapse
But what was the my fault here? What did I wrong? Was it the .img file of the twrp or did I install it wrongly? I am very new to this and don't understand why there are 2 slots etc. Sorry for the confusion.
felloguard123 said:
But what was the my fault here? What did I wrong? Was it the .img file of the twrp or did I install it wrongly? I am very new to this and don't understand why there are 2 slots etc. Sorry for the confusion.
Click to expand...
Click to collapse
You installed it uncorrectly, you need to switch slot (because this device have an A/B partition type), flash twrp, boot it, switch to the og slot, flash twrp using the .zip file (so it modify your current boot.img), and done.
This phone will be my first A/B phone, i cant wait to receive it.
But what you didnt is still correct, just not perfect.
antoine62 said:
You installed it uncorrectly, you need to switch slot (because this device have an A/B partition type), flash twrp, boot it, switch to the og slot, flash twrp using the .zip file (so it modify your current boot.img), and done.
This phone will be my first A/B phone, i cant wait to receive it.
But what you didnt is still correct, just not perfect.
Click to expand...
Click to collapse
So twrp has to be installed on both partitions?
I'm not sure if really twrp installed on only one partition could cause Wifi problems.
I would assume that my .img for twrp was faulty.
a
garylawwd said:
Did you flash any boot.img when installing twrp? Or after you installed twrp?
If you did that is more than likely the problem. Flash original stock boot.img from the same security patch date as your firmware and flash it in twrp and then flash twrp installer afterwards
Click to expand...
Click to collapse
and how to do that:{?
i have same problem as yours and searched too many videos on youtube but then i have decided to remove the twrp from the device and no one yet has told me that how to flash twrp in another partition rather i dont know what is the another partition
Hi using latest updated stock rom with root..
Magisk
New August update doesn’t install..
Before i used to install updates in root..
Now cant..
Help..
Do you have twrp installed and if so did you flash any mods to the system?
If no mods were installed just flash the stock boot.img for your firmware version using fastboot and reboot and apply the update
garylawwd said:
Do you have twrp installed and if so did you flash any mods to the system?
If no mods were installed just flash the stock boot.img for your firmware version using fastboot and reboot and apply the update
Click to expand...
Click to collapse
I have only magisk.. I got no mods.. Only by magisk i installed everything... How to get stock boot img? U mean unroot?
I have twrp sharp installed.on slot...
Sami Devo said:
I have only magisk.. I got no mods.. Only by magisk i installed everything... How to get stock boot img? U mean unroot?
I have twrp sharp installed.on slot...
Click to expand...
Click to collapse
Custom recovery that's why you cant install. Ota updates don't usually work with a custom recovery installed. You will have to flash stock boot.img there is a whole thread about this and all versions of the stock boot.img here https://forum.xda-developers.com/mi-a3/how-to/guide-how-to-root-mi-a3-magisk-t3958509/page43
You were even the last person to comment on that thread
My build..
garylawwd said:
Custom recovery that's why you cant install. Ota updates don't usually work with a custom recovery installed. You will have to flash stock boot.img there is a whole thread about this and all versions of the stock boot.img here https://forum.xda-developers.com/mi-a3/how-to/guide-how-to-root-mi-a3-magisk-t3958509/page43
You were even the last person to comment on that thread
Click to expand...
Click to collapse
But i had custom recovery and it installed before..the boot.img have to match with current build? For fastboot flash?? And which slot i have to flash the boot?
This might help (as long as you really read it and follow instructions): https://forum.xda-developers.com/mi-a3/how-to/guide-failed-ota-update-installation-t4041291
_mysiak_ said:
This might help (as long as you really read it and follow instructions): https://forum.xda-developers.com/mi-a3/how-to/guide-failed-ota-update-installation-t4041291
Click to expand...
Click to collapse
This link u give is for flash fastboot rom
Should i uninstall magisk and try?
Sami Devo said:
This link u give is for flash fastboot rom
Click to expand...
Click to collapse
Maybe try to read it at least one more time..
same but different problem.
I'm having somewhat similar problem here, but the thing is, I'm using stock mi a3, without any custom bootloader, twrp, rom, etc.
currently in version 11.0.17.0.QFQMIXM
trying to install the august security update that was supposed to be version 11.0.20.0
updater showed the august update as 464mb, which is weird as its supposed to be 34mb or so.
any help from the experts here are kindly appreciated.
I have no custom recovery, or magisk but have same problem
So I solved the problem as I love root .. I had to loose recovery sharp... Now I have no recovery . I flashed stock ROM of Build 19 and installed the latest OTA . After then I extracted the boot image of stock ROM then I patch stock boot image of latest build.i got now root with magisk with no recovery . I hope I can install future OTA with the method..
If u can't install u must have to flash fastboot..
I have tried restoring stock boot.img of build 19.. but doesn't installed.. although I removed custom recovery but still couldn't install OTA..
Sami Devo said:
So I solved the problem as I love root .. I had to loose recovery sharp... Now I have no recovery . I flashed stock ROM offer BL 19 and installed the latest OTA . After then I extracted the boot image of stock ROM then I patch stock boot image of latest build.i got now root with magisk with no recovery . I hope I can install future OTA with the method..
If u can't install u must have to flash fastboot..
I have tried restoring boot.img of build 19.. but doesn't installed.. although I removed custom recovery but still couldn't install OTA..
Click to expand...
Click to collapse
thanks for the great advice. anyone willing to do the needful, might as well do as suggested. but i kind of trying to keep things stock as much as i can, dont have the time to fiddle around as much. this phone is buggy enough as it is
decided to backup everything and reset for now. might root if resetting didnt fix the issue. cheers mate! :good:
weeeeeeeb said:
thanks for the great advice. anyone willing to do the needful, might as well do as suggested. but i kind of trying to keep things stock as much as i can, dont have the time to fiddle around as much. this phone is buggy enough as it is
decided to backup everything and reset for now. might root if resetting didnt fix the issue. cheers mate! :good:
Click to expand...
Click to collapse
???Yah.. i have some apps which i must use! Such as greenify , titanium backup.. those r core of root..
Am looking forward to meet another update challenge. Am ready.
weeeeeeeb said:
I'm having somewhat similar problem here, but the thing is, I'm using stock mi a3, without any custom bootloader, twrp, rom, etc.
currently in version 11.0.17.0.QFQMIXM
trying to install the august security update that was supposed to be version 11.0.20.0
updater showed the august update as 464mb, which is weird as its supposed to be 34mb or so.
any help from the experts here are kindly appreciated.
Click to expand...
Click to collapse
No its not weird. Becoz july update n also August both have to installed by u...thats y its not only 35mb.ur build is too old. It ought to be a big update
Tyrese117 said:
I have no custom recovery, or magisk but have same problem
Click to expand...
Click to collapse
Then u need to flash fastboot rom
Sami Devo said:
Then u need to flash fastboot rom
Click to expand...
Click to collapse
I have installed July patch without any problem
I have solved this problem
Download recovery rom and flash from stock recovery: APPLY UPDATE FROM SD CARD
Tyrese117 said:
I have solved this problem
Download recovery rom and flash from stock recovery: APPLY UPDATE FROM SD CARD
Click to expand...
Click to collapse
this is very hard work.. i cant do that in every month and retaining root again!
Official TWRP is now available: https://twrp.me/asus/zenfone9.html
IMPORTANT NOTES:
CleanSlate custom kernel is not currently compatible with TWRP for this device (Kirisakura is compatible as of v2.0.6).
This device has a recovery partition (2, in fact), and fastboot boot is disabled in the bootloader. Flashing TWRP to the recovery partition is the only way to use it.
If you attempt to fastboot boot the TWRP image, your device may end up unbootable. YOU'VE BEEN WARNED.
Any questions, comments, feedback, or concerns should always be accompanied by logs (recovery log, logcat, dmesg)
TWRP Trees
Common: https://github.com/TeamWin/android_device_asus_sm84xx-common
Device: https://github.com/TeamWin/android_device_asus_AI2202
Thanks for your work!
Installed as on twrp.me described wont boot (https://twrp.me/asus/zenfone9.html)
Had to flash stock recovery again.
Rooted device on 32.2050.2050.29 with kirisakura-kernel.
Any idea what im doing wrong?
Hermann2306 said:
Thanks for your work!
Installed as on twrp.me described wont boot (https://twrp.me/asus/zenfone9.html)
Had to flash stock recovery again.
Rooted device on 32.2050.2050.29 with kirisakura-kernel.
Any idea what im doing wrong?
Click to expand...
Click to collapse
If you're not on stock kernel, then that's probably the problem. I know the custom kernel situation is different on this device than previous ones. This may be something that @Freak07 & I have to look into together. In the meantime, can you restore back to stock kernel and confirm that TWRP works, and then install Kirisakura and see if everything still works?
Restored stock kernel with kernelflasher but now it wont boot. Tried to change the slot to a but isnt allowed in fastboot.
Have to find out now how to change the slot or install stock kernel via fastboot...
Hermann2306 said:
Restored stock kernel with kernelflasher but now it wont boot. Tried to change the slot to a but isnt allowed in fastboot.
Have to find out now how to change the slot or install stock kernel via fastboot...
Click to expand...
Click to collapse
It doesn't sound like you followed the procedure in the Kirisakura thread FAQ to fully return to stock. Can you confirm exactly what you did?
just restored the backup i made with kernelflasher befor i installed the custom kernel and rebooted.
Hermann2306 said:
just restored the backup i made with kernelflasher befor i installed the custom kernel and rebooted.
Click to expand...
Click to collapse
I'm not familiar with that app, sorry. I just know that's not the process mentioned in his thread, so until you do that, I can't really confirm what the problem could be.
ok, im back on stock. flashing following files helped. i will test twrp again later and report. thanks for your replies.
fastboot flash boot boot.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash dtbo dtbo.img
fastboot reboot fastboot
fastboot flash vendor_dlkm vendor_dlkm.img
fastboot reboot
With stock kernel twrp works. Just installed as described on twrp.me. The official twrp app from playstore crashes after root allowing.
For everyone who comes from custom kernel flash the files from your actual firmware (payload-dumper) as described in the post above.
Are you working on custom kernel support?
Hermann2306 said:
With stock kernel twrp works. Just installed as described on twrp.me. The official twrp app from playstore crashes after root allowing.
For everyone who comes from custom kernel flash the files from your actual firmware (payload-dumper) as described in the post above.
Are you working on custom kernel support?
Click to expand...
Click to collapse
From stock, I just flashed the Kirisakura zip in TWRP and my device booted up fine.
EDIT: While the above is true, TWRP no longer functions after installing the kernel, and the device won't reboot again after installing it. So something is definitely wrong somewhere.
For now, I can only suggest not using it with a custom kernel until we figure this out.
Ok, flashing with EXKernelManager works also.
update
I can do reboots but twrp doesnt work anymore
Hermann2306 said:
Ok, flashing with EXKernelManager works also.
update
I can do reboots but twrp doesnt work anymore
Click to expand...
Click to collapse
Yes, there seems to be an issue in the kernel that's preventing TWRP from working. I'm not sure what the issue is, unfortunately.
So every time I restore a back up, do I have to delete all lock screen requirements ?
If that's the case, I would have to redo my fingerprints every time
c19932 said:
So every time I restore a back up, do I have to delete all lock screen requirements ?
If that's the case, I would have to redo my fingerprints every time
Click to expand...
Click to collapse
Yes.
Quick PSA for anyone using this TWRP that also wants to use a custom kernel:
As of Kirisakura 2.0.6, the custom kernel and TWRP can now co-exist. This is due to the changes that allowed a monolithic kernel build. Presently, CleanSlate has not adopted those changes, but if/when it does, I will remove that disclaimer from the OP.
Thanks to @arter97, @Freak07, & @tbalden for supporting this device!
Is the twrp compatible with android 13?
NisseGurra said:
Is the twrp compatible with android 13?
Click to expand...
Click to collapse
There's a really easy way to find out...
Captain_Throwback said:
There's a really easy way to find out...
Click to expand...
Click to collapse
I getting decrypt errors that why the q
NisseGurra said:
I getting decrypt errors that why the q
Click to expand...
Click to collapse
Then you should post some logs
Will do