[GUIDE] FIX N950F efs failed to mount and dm-verify fail (unbrick) - Samsung Galaxy Note 8 Guides, News, & Discussion

The following is a guide for repairing failed to mount efs and dm-verify fail (drk error)
We finally did it ~~~
Warning - We will not take any responsibility for your device. Follow the steps at your own risk. If your device is Knox 0, This guide would convert it into Knox 1 due to TWRP. For solutions that does not convert to knox 1 check out payed remote solutions. Everything on your device will be reset, including efs partition. You will need backup of efs.
Test on N950F binary 4 may work on other exynos models comment below if it worked for other samsung devices.
Problem Detail -
Bootloop with samsung stock firmware boot logo.
Recovery error E:Failed to mount /efs (Invalid argument) or dm-verity verification failed...
Device cannot boot into Factory binary or Stock Rom​
Actions that could cause this problem -
Flashing a non-signed efs.img by odin
Corrupt flash of efs partition.​
Note - Must have efs backup for device to work (very important)
Any error that cause bootloop would show in recovery required if
Files Required
Latest Odin (recommend 3.13)
Working Stock firmware and Combination file (same binary as bootloader)
PC
Winrar or 7zip etc
Solution for efs failed bootloop-
Extract Stock firmware AP file (rename .md5 to .tar)
Rename dqmdbg.img to efs.img (or smallest image must be smaller than 8000 KB). Extract Dqmdbg.img.lz4 so it’s just “Dqmdbg.img” and then rename it to efs.img and put that one in a tar. Other option is downloading a file that’s already made this way if your bootloader is binary 4, Saves you trouble of extracting / renaming: http://www.mediafire.com/file/589wucja9rk2v8f/efs.tar/file (if you download this file just move onto number 3)
Add file new efs.img into tar archive.
Flash tar as AP file in odin + download mode
Reboot download mode
Flash Combination with odin + nand erase option on Edit: suggest you to flash stock rom first and oem unlock, don't need to wait for 7 days if imei is 0000 skip combination step
Device Should boot into Factory binary
Use IME to restore imei using *#06# (or imei 0000 in stock rom) Edit: This step is not required if efs backup is restored successful
Your device should have dm-verify failed in recovery due to drk error
Continue drk bypass for dm verify error below to continue
Solution for dm-verify error (also known as drk bypass - but temporary read note)-
Extract Stock firmware AP file
Make a copy of boot.img and delete recovery.img
Note - if files is boot.img.lz4 format change name to recovery.img.lz4
Rename boot.img copy to recovery.img
Add all the files (including other files extracted) to tar.
Flash Modded AP file with BL, CP, CSC (nand erase not required)
The phone will boot into stock firmware
Note- cannot reboot, will stuck at dm-verify error again and need to flash modded AP again.
Wait 7 days to oem unlock phone or use 7 day bypass by changing dates (not always work, keep trying, don’t reboot, worked for Samsunguser932 Edit: Imei must be 0000)
Edit: oem unlock will fix drk - if not you must follow next step
Once oem unlock flash TWRP and restore efs backup Edit: if you haven't fixed imei fix now by *#06# with combination file
Flash stock firmware once again by odin (stock, not modded)
Done - phone is back to normal
If you cannot be bothered doing by yourself you can pay https://www.facebook.com/gsm.xraxxx/ to do this.
(after he used plexihub to fix phone, i believe he is using similar method. It doesn’t seem fair to post this guide as i’ll be damaging his income but it seemed also unfair to keep this as a secret. If you want to donate to me please donate to him and his team instead at https://spacial-file.com/ or paypal [email protected] Thx)
Special Thanks to -
Samsunguser932 - testing this guide you can see his post on https://forum.xda-developers.com/galaxy-note-8/help/note-8-phone-booting-efs-restore-t3830209
Ravi Kumar - for his help in giving me clues how to fix.
Resources: (where i got most my info)
https://forum.xda-developers.com/galaxy-note-8/help/unbrick-methods-t3703767
https://forum.xda-developers.com/galaxy-note-8/help/to-fix-efs-secondary-note-8-t3785600
https://forum.xda-developers.com/galaxy-note-8/help/note-8-phone-booting-efs-restore-t3830209
http://forum.gsmhosting.com/vbb/f453/samsung-s8-g955f-2426383/​
Comment below for help.
Give me a thanks if you find this guide very/extremely helpful. :angel:
Share it with those in need.
edit: not all images were able to upload
update: to skip 7 day oem unlock imei must be 0000

The best method for bypassing oem unlock for 7 days.
Requirements - clean phone with stock firmware, samsung account logged in, imei 0000
Go to setting and check for manual update. This will fail/stuck and oem unlock would appear in development settings

Reserved

hello , i have samsung j737t with bad efs ,
Recovery error E:Failed to mount /efs (Invalid argument)
any help please ,i have cert in hand

maxpatri9 said:
hello , i have samsung j737t with bad efs ,
Recovery error E:Failed to mount /efs (Invalid argument)
any help please ,i have cert in hand
Click to expand...
Click to collapse
Try the above guide. This guide isn't just designed for the note 8.

from what file i need to create efs.img for s8+ g955F?

ditternation said:
from what file i need to create efs.img for s8+ g955F?
Click to expand...
Click to collapse
You do not need an efs.img to repair efs failed to mount. It is only required for the functionality of the phone (sim). This guide would work without an efs.img, it is recommended to install a custom rom after the guide. Even though this guide can allow you phone to work, but due to drk/dm-verify errors, it is currently impossible to restore the phone to the original state.
Note - you'll need to find someone that is kind enough to share a copy/backup of their efs.img g955F. Most people think it is illegal to share as the efs.img contain imei, but with cpid devices, the imei would be overridden by your current device. Most importantly you need to change the serial number in the SVC (or else you will have the same serial number as the person sharing.

plz my problem is oem lock on, frp on and drk error. i have combination file and stock can your guide work for me?

soundn said:
plz my problem is oem lock on, frp on and drk error. i have combination file and stock can your guide work for me?
Click to expand...
Click to collapse
This would only work if you're still on binary 3. Follow the steps for DM verity fix with 7.1.1 firmware. Flash stock 7.1.1 with replaced boot.img using Odin and fix frp using adb (guides online to enable adb). Wait for 7 day OEM unlock (no method to skip do not restart). Flash twrp and use twrp to flash custom ROM or DM verify fix.
Note - this method would fix function ability of the phone only if efs is not corrupted. (If you had paid someone to fix efs, this would not work). Finally the phone will become Knox 1 and normal update functions might not work. Practically makes the phone unable to resell as a working phone.

Hello. My efs partition was erased by a z3x box. Or an octopus, I do not know. I followed your instructions. The IME combination is empty. I install a modified firmware, it works but I can not enter the Samsung account (crashing), I can not check the system updates (infinite device registration). Should I wait 7 days before the OEM unlock? Will it work?

@Alarg read post 2 to skip 7 days. Infinite device registration should make OEM unlock show with samsung account logged in. OEM unlock must be first done before installing modified firmware (suggest kernel). You must have backup of efs, a backup from another phone will not work.

bluecub1st said:
@Alarg read post 2 to skip 7 days. Infinite device registration should make OEM unlock show with samsung account logged in.
Click to expand...
Click to collapse
I can't log in Samsung account (processing failure). Imei unknown, s/n 0000000000 This method does not work for me.

@Alarg Which firmware ver are you using?
Have you tried nand flash combination file and then flash firmware (before boot, hold download mode buttons so the phone won't boot to factory mode). I do not see a reason why Samsung account would not work, try another ver maybe the version you downloaded is corrupted.

bluecub1st said:
The following is a guide for repairing failed to mount efs and dm-verify fail (drk error)
We finally did it ~~~
Warning - We will not take any responsibility for your device. Follow the steps at your own risk. If your device is Knox 0, This guide would convert it into Knox 1 due to TWRP. For solutions that does not convert to knox 1 check out payed remote solutions. Everything on your device will be reset, including efs partition. You will need backup of efs.
Test on N950F binary 4 may work on other exynos models comment below if it worked for other samsung devices.
Problem Detail -
Bootloop with samsung stock firmware boot logo.
Recovery error E:Failed to mount /efs (Invalid argument) or dm-verity verification failed...
Device cannot boot into Factory binary or Stock Rom​
Actions that could cause this problem -
Flashing a non-signed efs.img by odin
Corrupt flash of efs partition.​
Note - Must have efs backup for device to work (very important)
Any error that cause bootloop would show in recovery required if
Files Required
Latest Odin (recommend 3.13)
Working Stock firmware and Combination file (same binary as bootloader)
PC
Winrar or 7zip etc
Solution for efs failed bootloop-
Extract Stock firmware AP file (rename .md5 to .tar)
Rename dqmdbg.img to efs.img (or smallest image must be smaller than 8000 KB). Extract Dqmdbg.img.lz4 so it’s just “Dqmdbg.img” and then rename it to efs.img and put that one in a tar. Other option is downloading a file that’s already made this way if your bootloader is binary 4, Saves you trouble of extracting / renaming: http://www.mediafire.com/file/589wucja9rk2v8f/efs.tar/file (if you download this file just move onto number 3)
Add file new efs.img into tar archive.
Flash tar as AP file in odin + download mode
Reboot download mode
Flash Combination with odin + nand erase option on Edit: suggest you to flash stock rom first and oem unlock, don't need to wait for 7 days if imei is 0000 skip combination step
Device Should boot into Factory binary
Use IME to restore imei using *#06# (or imei 0000 in stock rom) Edit: This step is not required if efs backup is restored successful
Your device should have dm-verify failed in recovery due to drk error
Continue drk bypass for dm verify error below to continue
Solution for dm-verify error (also known as drk bypass - but temporary read note)-
Extract Stock firmware AP file
Make a copy of boot.img and delete recovery.img
Note - if files is boot.img.lz4 format change name to recovery.img.lz4
Rename boot.img copy to recovery.img
Add all the files (including other files extracted) to tar.
Flash Modded AP file with BL, CP, CSC (nand erase not required)
The phone will boot into stock firmware
Note- cannot reboot, will stuck at dm-verify error again and need to flash modded AP again.
Wait 7 days to oem unlock phone or use 7 day bypass by changing dates (not always work, keep trying, don’t reboot, worked for Samsunguser932 Edit: Imei must be 0000)
Once oem unlock flash TWRP and restore efs backup Edit: if you haven't fixed imei fix now by *#06# with combination file
Flash stock firmware once again by odin (stock, not modded)
Done - phone is back to normal
If you cannot be bothered doing by yourself you can pay https://www.facebook.com/gsm.xraxxx/ to do this.
(after he used plexihub to fix phone, i believe he is using similar method. It doesn’t seem fair to post this guide as i’ll be damaging his income but it seemed also unfair to keep this as a secret. If you want to donate to me please donate to him and his team instead at https://spacial-file.com/ or paypal [email protected] Thx)
Special Thanks to -
Samsunguser932 - testing this guide you can see his post on https://forum.xda-developers.com/galaxy-note-8/help/note-8-phone-booting-efs-restore-t3830209
Ravi Kumar - for his help in giving me clues how to fix.
Resources: (where i got most my info)
https://forum.xda-developers.com/galaxy-note-8/help/unbrick-methods-t3703767
https://forum.xda-developers.com/galaxy-note-8/help/to-fix-efs-secondary-note-8-t3785600
https://forum.xda-developers.com/galaxy-note-8/help/note-8-phone-booting-efs-restore-t3830209
http://forum.gsmhosting.com/vbb/f453/samsung-s8-g955f-2426383/​
Comment below for help.
Give me a thanks if you find this guide very/extremely helpful. :angel:
Share it with those in need.
edit: not all images were able to upload
update: to skip 7 day oem unlock imei must be 0000
Click to expand...
Click to collapse
thanx! for your guide but i have this problem after taking an official OTA!
DM-Verity ERRor!
any help will be greatly appreciated!

Can someone explain me what is this EFS ?? I'm flashing roms many many times and I hadn't such problems etc

klisza1993 said:
Can someone explain me what is this EFS ?? I'm flashing roms many many times and I hadn't such problems etc
Click to expand...
Click to collapse
Just Google "EFS android"

pixel989 said:
thanx! for your guide but i have this problem after taking an official OTA!
DM-Verity ERRor!
any help will be greatly appreciated!
Click to expand...
Click to collapse
Follow
Solution for dm-verify error (also known as drk bypass - but temporary read note)-
Extract Stock firmware AP file
Make a copy of boot.img and delete recovery.img
Note - if files is boot.img.lz4 format change name to recovery.img.lz4
Rename boot.img copy to recovery.img
Add all the files (including other files extracted) to tar.
Flash Modded AP file with BL, CP, CSC (nand erase not required)
The phone will boot into stock firmware
Note- cannot reboot, will stuck at dm-verify error again and need to flash modded AP again.
Wait 7 days to oem unlock phone or use 7 day bypass by changing dates (not always work, keep trying, don’t reboot, worked for Samsunguser932 Edit: Imei must be 0000)
Once oem unlock flash TWRP and restore efs backup Edit: if you haven't fixed imei fix now by *#06# with combination file
Flash stock firmware once again by odin (stock, not modded)
Done - phone is back to normal
Click to expand...
Click to collapse
Note -
dm verify cannot be completely fixed, it can only be bypassed (in the system by flashing no dm verify).
You will need to wait for 7 days for oem unlock (there is no method to skip oem unlock)
Warranty will be voided (KNOX 1) - don't think there is a method to avoid tripping knox.
Suggest installing a custom rom after oem unlock (many reports that no dm verify on latest oreo does not work without root)

klisza1993 said:
Can someone explain me what is this EFS ?? I'm flashing roms many many times and I hadn't such problems etc
Click to expand...
Click to collapse
EFS partition is not touched when flashing roms (they actually do but in a safe way), only retards like I would try to mod efs partition.

Hi guys, will it work in my case? https://ibb.co/mJRcHK
Device is SM-N950N FRP ON and OEM ON.
What kind of solution should I follow?

@Anvar2005 - This looks like a drk verify error. Which binary are you on? frp bypass only works with binary 3. You will not find anything for frp unlock on this forum. Same steps for drk verify but use nougat.

Related

Need help with unbricking/resetting acer liquid Z330

I've downloaded the stock ROM from the acer site, put it on my SD card and went into recovery to apply the update from the sdcard. When trying to update I got the following error:
e: footer is wrong
e: signature verification failed
Installation aborted.
Now, I've searched everywhere and tried at least 20 different things without anything working. I've unlocked the bootloader and flashed the boot.img which was inside the update file I downloaded from the acer site, I've tried flashing certain files seperatly etc. Another problem is, there is no system.img or recovery.img or any other img file in the stock rom from acer which doesn't allow me to flash it via the fastboot. So either I need to find those img files, or I need a fix for the error above.
Any suggestions?
(One more thing, I really can't try using a custom recovery to disable signature verification because the Liquid Z330 is such an unsupported phone, there is no cwm or twrp recovery for it. I also don't wanna risk trying another phone's cwm or twrp on the Z330 because I don't have the stock recovery.img file in case it doesn't work.)
UPDATE: I found an older version of twrp for the phone and I was able to disable signature verification but when trying to install the zip I get this error log:
Updating partition details...
*in red* E: Unable to mount '/system'
...done
Full SELinux support is present.
MTP Enabled
Installing '/sdcard/update.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Error flashing zip '/sdcard/update.zip'
Any new suggestions as to what might be the problem?
Update2:
So after Ysfzone posted this tutorial:
http://forum.xda-developers.com/general/general/acer-liquid-z330-unbrick-unlock-t3520952
I was able to restore my acer liquid z330.
I did actually run into some trouble with Ysfzone's instructions, and found a way around it, it should be the second comment on the post.
My only problem now is that the system is restored it's booting into demo mode. When I try to update it downloads the update and reboots into TWRP and when I then reboot to the system it says that the install failed. I think it would automatically install the update with the stock recovery but because I have TWRP installed I have to find the downloaded update file and install it manually.
So I have two options:
Either someone tells me where the update download folder is, or someone provides me with the stock recovery.
Any help?
Exactly same issues
Hey there!
I have the exact same issues. I have been trying to unbrick my phone, but nothing has actually worked. My phone is still stuck on the white screen with the acer logo.
Did you make any progress?
Were you able to find out anything that works??
Any help will be appreciated.
Thanks
MK
markendeyk said:
Hey there!
I have the exact same issues. I have been trying to unbrick my phone, but nothing has actually worked. My phone is still stuck on the white screen with the acer logo.
Did you make any progress?
Were you able to find out anything that works??
Any help will be appreciated.
Thanks
MK
Click to expand...
Click to collapse
(If you don't want to read the story, read the last sentence.)
I actually was able to get rid of the MD5 check error by creating a MD5 file myself. You basically have to download an application that gets you the MD5 sum. I used this: http://www.fast-files.com/getfile.aspx?file=127067 (just reuploaded it because I forgot where I got it from). Using the exe file in there I generated the MD5 file in this format: d2a862b7c1a8f66b6d1be32f400dc73e *update.zip. After that I tried installing the zip again, this time I got the same error except with the MD5 error missing. After contacting Acer support, I was basically told that I needed to send my info back so I could get contacted for a repair. But since I flashed the recovery it probably wouldn't fall under warranty.
So basically try emailing Acer support and try and get them to repair it. I havent found a way to fix it myself.
One more thing. It wasn't my phone to begin with, I just tried to fix it for someone. That person already has a new phone and I won't be trying anything anymore to fix the phone since I don't have it anymore.
Hello everyone,
I've been in the same situation as you until few hours.
I've also tried a lot of things which doesn't work at all ( like extracting system.img from the Acer update.zip ).
I've seen that every time I tried to install an update.zip package I get the same error:
E: footer is wrong.
E: signature verification failed
And I solved it by unzipping and zipping it again.
Then when I was able to flash it and get my phone back.
if it still doesn't work with the stock recovery, you may try with a custom recovery ( like twrp, you can easily find it on google )
If you have any questions about it, I can try to answer them.
Hope it'll help !
pxie said:
Hello everyone,
I've been in the same situation as you until few hours.
I've also tried a lot of things which doesn't work at all ( like extracting system.img from the Acer update.zip ).
I've seen that every time I tried to install an update.zip package I get the same error:
E: footer is wrong.
E: signature verification failed
And I solved it by unzipping and zipping it again.
Then when I was able to flash it and get my phone back.
if it still doesn't work with the stock recovery, you may try with a custom recovery ( like twrp, you can easily find it on google )
If you have any questions about it, I can try to answer them.
Hope it'll help !
Click to expand...
Click to collapse
Thanks for the suggestion. Just out of curiousity I guess I'll ask the phone back and try it.
I've tried it again, but the problem isn't because the signature verification fails, its something else. Idk what.
Hello Mounir9912,
Have you try to re-download the file from acer website, or/and to check the zip file with winzip or winrar ?
I've read that you created a md5 file, for my part I just disable md5 verification from TWRP.
It seems like you've got a system mount error, do you still get it if you wipe all partition on your phone (system, cache, data, dalvik cache) ?
Finally, I don't know if it can be useful, but I have a TWRP backup of my z330
I'll stay available if you still have trouble.
pxie said:
Hello Mounir9912,
Have you try to re-download the file from acer website, or/and to check the zip file with winzip or winrar ?
I've read that you created a md5 file, for my part I just disable md5 verification from TWRP.
It seems like you've got a system mount error, do you still get it if you wipe all partition on your phone (system, cache, data, dalvik cache) ?
Finally, I don't know if it can be useful, but I have a TWRP backup of my z330
I'll stay available if you still have trouble.
Click to expand...
Click to collapse
You might just be the godsend I needed. I've already tried everything you said including wiping and disabling the verification. Could you upload the twrp backup somewhere? It might be the only thing that can save this phone aside from paying way too much money to acer because of a voided warrantee.
Hello Mounir9912,
Here the link to download the twrp backup of my z330:
mega.nz/#!idICgLAZ!uJo_EvbMHAyVju9qo_uWY7d7aVLkpqxmZAWSd8jtmkk
Hope it'll help.
I'll stay available if you still need help.
pxie said:
Hello Mounir9912,
Here the link to download the twrp backup of my z330:
mega.nz/#!idICgLAZ!uJo_EvbMHAyVju9qo_uWY7d7aVLkpqxmZAWSd8jtmkk
Hope it'll help.
I'll stay available if you still need help.
Click to expand...
Click to collapse
Thanks, I'll try it when I get home (in a few hours)
damn, mega is being an asshole. I downloaded it but while downloading I accidentally unplugged the power cable from my laptop and it shut down so I had to redownload. When I downloaded again it cut me off at like 90% because of exceeding the bandwidth quota of 5GB. Now I have to either pay a monthly fee or wait 5 hours...
Hey pixie,
I've actually restored it via twrp, but it still isn't booting past the logo. Could you maybe make a backup of all the partitions except the boot, system and data partitions? The problem is probably in one of those partitions since restoring the boot or system didn't fix it.
more specifically, the ones I could backup are:
Modem, Aboot, pad, modemst1, modemst2, misc, splash, fsg, persist, cache, devinfo, oem
Hi, i'm in the same problem can you give me the link of official rom ? Plz
Ysfzone said:
Hi, i'm in the same problem can you give me the link of official rom ? Plz
Click to expand...
Click to collapse
https://www.acer.com/ac/en/GB/content/support-product/6358?b=1
Its under "OS"
Or direct download link:
http://global-download.acer.com/GDF...30&Step3=Z330&OS=ALL&LC=en&BC=ACER&SC=EMEA_27
Done Done Done !!!!!!
i fixed this problem wooow !!!!!!
This is how to unbrick Acer Liquid Z330
1- Download Official Rom from here : https://www.acer.com/ac/en/GB/content/support-product/6358?b=1
2- Download this tool from : http://www.stupdroid.com/2016/10/tool-systemnewdat-into-flashable-img.html
3- Download python (required for tool in step 2) : https://www.python.org/downloads/
4- Download Drivers the link on step 1
5- Download and install Fastboot (Search for it)
6- Create new Folder and put into all files on tool (step2) and file_contexts + system.new.dat + system.patch.dat + system.transfer.list from the Official rom
7- now launch "system.new.dat 2 flashable img converter" and tap any key and wait... after you got 2 files.. you need just the file called system.new.img
8- move system.new.img to fastboot/adb folder and rename it to system.img
9- enter phone to fastboot mode and type this command :
fastboot -w
fastboot flash system system.img
10- now just wait and don't worry about messages from fastboot...
11- after you finishing type: fastboot reboot
and wait between 5/10 mins for phone booting..
and DONE !!
Sorry for my bad english
Now my phone stuck on demo mode.. i want the stock recovery.img
hello,
first sorry for the delay.
As far as i remember, I've checked all when I backup the phone. But all that things you list are not unknown, I've seen them when the phone was still bricked. By the way, I even made a backup at this moment, so if you think that it can be useful..
Ysfzone, have you try to use qfil to get you're stock recovery ?

(SOLVED) android 7.0 stuck at boot loop after rooting, any way to rescue my data

Hi
I have a samsung S7 running on android 7.0.
After running TWRP on phone the phone is on boot loop.
I can access the phone database and did a full copy with adb but the user data it seems to be encrypted.
Is there any way to salvage my information?
TWRP doesn't ask my password so is there another way to open the image.dd that I have
maybe try to flash the same original samsung 7.0 HOME SW (which was installed before trying to root).
Home SW shouldn't erase user data, and maybe will fix this, but I don't tried it on encrypted device.
legacik said:
maybe try to flash the same original samsung 7.0 HOME SW (which was installed before trying to root).
Home SW shouldn't erase user data, and maybe will fix this, but I don't tried it on encrypted device.
Click to expand...
Click to collapse
Thanks for the quick reply!!
I have downloaded the original firmware package and as I can understand flashing home_csc file doesn't erase data at all.
Any Idea do I have to install the other packages also or just the home_CSC?
l00p3r said:
Thanks for the quick reply!!
I have downloaded the original firmware package and as I can understand flashing home_csc file doesn't erase data at all.
Any Idea do I have to install the other packages also or just the home_CSC?
Click to expand...
Click to collapse
I think on Sammobile/Samfirmware you can get full package AP+CP+CSC in one. For example "G935FXXU1DQB7_G935FUUB1DQB7_ARO" but I'm not sure if there should be the same CSC as previously installed on your phone to NOT erase all data.
I don't test it so you're flashing this on your own risk Maybe someone else can confirm this. Few years ago I had similar issue with my galaxy note3 (stucked on boot after trying to root) and this solution works for me
SOLVED
I downloaded the same stock firmware that I had on the phone before flashing with TWPR.
Extracted the zip file to c:/ odin
I edited the HOME_CSC with Cygwin and used the following commands
cd /cygdrive/c/odin
file=HOME_CSC_PHN_G935FPHN1APBD_CL7162483_QB8754029_REV00_user_low_ship.tar.md5
tar xvf "${file}" cache.img hidden.img
tar -H ustar -cf "${file%.md5}" cache.img hidden.img
md5sum -t "${file%.md5}" >> "${file%.md5}"
mv "${file%.md5}" "${file}"
After that flashed all packages with odin
BL - Bootloader
AP
CP
HOME_CSC
None of my data was erased and all worked out well
After flashing the knox indicated that my phone was hacked .. maybe full factory reset would bring it back
l00p3r said:
After flashing the knox indicated that my phone was hacked .. maybe full factory reset would bring it back
Click to expand...
Click to collapse
As soon as the knox flag is broken its gone forever. Flashing root breaks knox.

[TWRP][RECOVERY] Asus ZenPad 8.0 Z380M (locked bootloader ok)

This is for real, folks. The first working custom recovery for Asus ZenPad 8.0 Z380M and a method to flash it under a locked bootloader. This took quite a bit of work to make, partly due to having to find a way to bypass the locked bootloader. And because of a kernel configuration issue that limited the size of the initial ramdisk, which took some serious effort to weed out. @lss1977 helped to port it to this device. And of course, credits to TeamWin for TWRP.
In addition to this thread, the current Z300M/Z301M TWRP thread and the the old Z300M recovery/rooting thread may be helpful. These models share the same hardware and software base, so most things that apply to one tablet also apply to the other.
DISCLAIMER
As usual, you do anything described in this post at your own risk. No one but you is responsible for any data loss, bricking or damage of your device.
REQUIREMENTS
Windows PC
SP Flash Tool version 5.1532 (only this version will bypass security checks)*
MediaTek VCOM drivers (available through Windows Update)
Z380M scatter file, attached
Recovery image, attached
Z380M preloader file (optional), available inside the stock firmware download
ZenPad Z380M tablet upgraded to Android N
* If you prefer to use a more recent SP Flash Tool, check out the special image file below.
This won't be a guide on how to use SP Flash Tool. There are plenty of good guides out there like this one on how to set up drivers, load scatter files, flash and make backups with SP Flash Tool. If you're not familiar with this software or how to flash MediaTek devices in general, please do your research before attempting this. I will just get straight to the specifics about the ZenPad 8.
FIRST TIME INSTALLATION
For a locked bootloader:
At this point you should have your tablet powered off, the drivers installed, all of your data backed up, and SP Flash Tool v5.1532's Download tab open and loaded with the tablet's scatter file. Open the download agent file DA_PL.bin, replacing the default MTK_AllInOne_DA.bin. (You can use the AllInOne DA if you want, but the procedure involves extra steps as described below.) Load the extracted TWRP recovery image (twrp-3.2.1-0-z380m.img) under the recovery partition line in the partition table. Click the Download button inside SPFT. Now just connect the USB cable to your tablet and your computer's USB port. It should start the download process automatically and disconnect when finished.
Alternative Method:
If you're using MTK_AllInOne_DA.bin, you have to hold the Volume Up key as you insert the cable, which puts the device into an emergency download mode. In addition, you will need to have the stock preloader*.bin file loaded inside SPFT for it to be able to communicate with your tablet. The preloader is available inside the official zip file download. Do not flash the preloader (untick the box) or any partitions other than recovery. You just need to have a valid bin file selected under the Preloader line.
For an unlocked bootloader:
If you have used the Asus unlock tool to unlock your device, you will still not be able to use fastboot flash to install a custom recovery. However, you can do a "hot boot" or a tethered boot of TWRP. This method doesn't require SP Flash Tool. Download the TWRP image, put your tablet in fastboot mode and connect to PC. Then run this command to boot TWRP dynamically:
fastboot boot twrp-3.2.1-0-z380m.img
Once inside TWRP, flash twrp-3.2.1-0-z380m.img to Recovery using Install -> Install Image. Then reboot to recovery. You may be able to use TWRP in the tethered boot mode, but that could result in glitches due to different parameters passed by the bootloader to the kernel. That's why flashing is recommended.
To update from your installed TWRP version to a new one, just transfer the image to your tablet, then boot to TWRP and install it by going to Install -> Install Image and flashing to Recovery.
START RECOVERY
With the tablet powered off, hold the Volume Up and Power keys together until you get to a menu where you can select "recovery". Use Vol. Up to scroll and Vol. Dn to select. If you have a locked bootloader, it will show a Yellow State message because the recovery is not signed by the OEM. Just press volume up to boot it. On the welcome screen of TWRP it will ask you about modifying the system partition, I suggest you go with Keep System Read-only. Doing otherwise will complicate your OTA updates.
WARNING: Never start the stock recovery from the bootloader menu on this device. It is programmed by the bootloader to instantly wipe your data without any warning. Also, be aware that Android installs the stock recovery at every normal boot cycle. So you either have to flash the TWRP every time you want to run it, or disable the automatic recovery installation in the stock firmware. Any kind of mod to the boot image will prevent the automatic recovery installation. If you're not sure which recovery you have installed, you can always do a 'adb reboot recovery' from Android without risk of data loss.
What works: Basically everything... access to major partitions, decrypted userdata partition, decrypted adoptable storage, external SD card, ADB, USB-OTG, touch interface, splash screen, installing stock Asus OTA/web FW updates
What doesn't work: (no known problems yet, but please report any)
Not guaranteed to work: factory reset
DOWNLOAD
(Updated February 3, 2018: updated kernel to firmware 5.3.18; up-to-date TWRP 3.2.1 sources)
SP Flash Tool v5.1532
Z380M Scatter file for all storage sizes (right click, Save link as...)
Recovery image
Signed image for Flash Tool only -- may be flashed with recent SP Flash Tool versions -- DO NOT INSTALL USING ANY OTHER METHOD -- tested with SPFT 5.1736.
Development and experimental files
Source code
P.S. The thanks button doesn't bite.
Nice one now lets get some custom roms done.
Has anyone installed this yet? I see the file has been downloaded a few times. Any feedback is welcome.
If you want the recovery to stick after reboot either rename or remove system/bin/install_recovery.sh.
lss1977 said:
If you want the recovery to stick after reboot either rename or remove system/bin/install_recovery.sh.
Click to expand...
Click to collapse
The way I did it was to edit the init.rc file inside the boot ramdisk and comment out the service block that calls install_recovery.sh. I used the MTK boot image unpack/repack tools. I don't know, it seems like changing anything on the system partition will break OTA updates because of dm-verity. Because that depends on verifying each block of the file system. I have never even mounted the system as R/W in recovery.
how to create scater file from text posted? I copied all text to MT8163_Android_scatter.txt file but when open with splash tools give error "scatter file is invalid"
please atach your working scatter file to other atachments
PxYra said:
how to create scater file from text posted? I copied all text to MT8163_Android_scatter.txt file but when open with splash tools give error "scatter file is invalid"
please atach your working scatter file to other atachments
Click to expand...
Click to collapse
OK, I added the scatter file as a download. It was a pain in the ass to copy & paste. (But it did work.)
Problem fixed downloaded new version of flashtool 5.16 and scatter working
Ok I installed TWRP on Z380M P00A, and wanna say to other
1. Use VCOM drivers only from splash tool official site
2. To install VCOM drivers first need enter chinese recovery tablet, then in windows device manager you see USB device, install manualy drivers (don forget in windows disable driver signature)
3. Use only SP-Flash-Tool-v5.1532.00, newer or older version not properly working with this phone
Ok, thanks for the update, PxYra. Just to let you know, there are signed versions of VCOM drivers floating around so you don't need to mess with signature enforcement. Here's one: https://www.androidfilehost.com/?fid=24591000424943663. They are also updated by Windows so you can just let Windows Update install them.
Thanks for your work.
Flashing procedure works only with "MTK_AllInOne_DA.bin" method for me. But this is OK!
(Updated May 6, 2017: added kernel from firmware 5.3.7, source code cleanup)
Click to expand...
Click to collapse
is it possible to get the older versions? I need Android 6.x, because of xposed-Framework for my Zenpad 8.0 Z380M.
Greets Freisei
Hey freisei...
I never posted a version for Android 6. There was just one based on the 5.3.6 kernel, practically the same as the current one. That's why I didn't keep it. I could try to build one for you if you want, but I can't test it of course. Does this recovery not boot at all on the old firmware?
It's strange that the DA_PL.bin method didn't work for you. What happened when you tried it? I suppose the old preloader doesn't allow it(?).
hello guys, you think lineage os official version for asus z380kl (p024) will work on our z380m ?
---------- Post added at 08:19 PM ---------- Previous post was at 08:05 PM ----------
Can anyone help me? after selecting recovery img, pressing download and inserting usb cable, nothing happens. Thanks in advance
lss1977 said:
If you want the recovery to stick after reboot either rename or remove system/bin/install_recovery.sh.
Click to expand...
Click to collapse
hello friend, can you please upload that file? I deleted it, but now I need it to revert to official recovery, as my zenpad is bricked! It would be of great help! thanks!
Pires_7 said:
hello friend, can you please upload that file? I deleted it, but now I need it to revert to official recovery, as my zenpad is bricked! It would be of great help! thanks!
Click to expand...
Click to collapse
Your ZenPad didn't brick because you deleted install_recovery.sh. It's because you modified the system partition. Making any mods to system is bad advice unless you know exactly what you're doing. Even mounting it in r/w mode can break it. That's because dm-verity has tripped and is blocking access to changed blocks of the file system. So you have 3 options: mod your boot image fstab file to disable dm-verity, restore the original system image block-for-block (either from backup or official firmware converted to an img file), or wipe userdata (lss reported that to work).
Pires_7 said:
hello guys, you think lineage os official version for asus z380kl (p024) will work on our z380m ?
Click to expand...
Click to collapse
Nope, no chance.
diplomatic said:
Your ZenPad didn't brick because you deleted install_recovery.sh. It's because you modified the system partition. Making any mods to system is bad advice unless you know exactly what you're doing. Even mounting it in r/w mode can break it. That's because dm-verity has tripped and is blocking access to changed blocks of the file system. So you have 3 options: mod your boot image fstab file to disable dm-verity, restore the original system image block-for-block (either from backup or official firmware converted to an img file), or wipe userdata (lss reported that to work).
Nope, no chance.
Click to expand...
Click to collapse
Ok. I made some real s*it, I think I deleted every partition except recovery. Can you provide me a twrp backup or some way around my problem?
What do you mean you deleted every partition except recovery? There's like 28 partitions. You would have to work hard to accomplish that.
My first suggestion is to extract a system.img from the Asus stock firmware zip using this. Then flash it with SP Flash Tool. You might also try to install a full firmware zip from TWRP. Although I have no idea if that will work or if it's even safe to try.
diplomatic said:
What do you mean you deleted every partition except recovery? There's like 28 partitions. You would have to work hard to accomplish that.
My first suggestion is to extract a system.img from the Asus stock firmware zip using this. Then flash it with SP Flash Tool. You might also try to install a full firmware zip from TWRP. Although I have no idea if that will work or if it's even safe to try.
Click to expand...
Click to collapse
i was able to extract system.new.dat from stock firmware zip, but it extracts to a system folder. How do I flash this through sp flash tool?
OK, the system folder you don't need. It should have produced a system.img file also. That's the file you need to flash. Just select it for the system partition row in the partition list and then Download. Hopefully that will be enough.
EDIT: I just looked at the script, and realized the system.img.img file gets deleted in the process. So what you need to do is start the extraction, then after it makes system.img.img, when it starts extracting individual files, hit Ctrl+C. Then you'll end up with the img file.
Thank you very much! it works! YOU are the BEST!
please tell me, in your scatter file, address partition_name: frp (0x80a5000) is correct? if i format this partition (frp), google account remove?

TWRP errors when trying to restore boot - bricked phone

I've bricked my phone and am in need of help!
What I've done:
Unlocked bootloader with a code from DC-Unlocker then using minimal ADB and Fastboot to unlock
Flashed TWRP 3.1.1
Installed Magisk
Took TWRP backup - but I was unable to backup Data (I believe this was due to encryption - recovery.log shwed errors initially on Bluedorid files)
Wiped data with TWPR to try and do a factory reset
This is where my problems started and now I cant restore boot with TWPR the error is "No such file or directory"
I can ADB pull my recovery.log which says
Read info file, restore size is 12444160
Restoring 6 partitions...
Total restore size is 4512MB
I:Restore filename is: /external_sd/TWRP/BACKUPS/L5NDU17B18000539/Stock V7 2018-06-23--16-58-45/boot.emmc.win
I:Restore file system is: 'emmc'.
I:Restore file system is: 'emmc'.
Restoring Boot...
Error opening: '' (No such file or directory)​
I can restore OEM recovery and do a factory reset but it hangs at 99%
power down then it goes back to factory reset and goes to 100% - message "Reset Successful!"
but... then it gets stuck in a boot loop
I've tried downloading other stock ROMS and extracting and flashing images via fastboot (Boot, cust, product, recovery, system, vendor, version)
I've tried Huawei Multi-tool but I lack the Userdata.img disk image
I've tried flashing Resurrection Remix N v5.8.5 For Honor 9 (STF) but without success, although the TWRP install says it is successful and the vendor.img flashes fine.
I've tried extracting UPDATE.app files and putting them in sd_card/dload and then 3 button resetting
I've tried the above in external_sd/dload (not sure why - desperation)
I've tried looking on as many threads as I can find on XDA but with no luck
I can always get to fastboot, flash TWRP or OEM recovery, I can also run ADB commands via Putty (in command line they display strangely)
Any suggestions would be greatly appreciated! I am at a loss an quite frustrated, and have been working on this for maybe 15 hours now.:crying:
LOL, Stop your mumbo-jumbos.
I guess you'r still with nougat partitioning because you're using a pretty much outdated twrp.
So just dload flash a nougat 'service repair firmware' from the same region you're firmware is actually, and not any random update.app you 'made' yourself.
For this you'll need a micro-sdcard (or usb-otg) exfat formated :
https://forum.xda-developers.com/honor-9/development/firmware-huawei-honor-9-stf-l09-stock-t3696892
Fixed!
Thank you, I think I even saw this thread but for some reason did not download the file, also the exfat formatting tip was excellent. I owe you a beer!
Can I always use this method to go back if I totally destroy things again even If I update to Oreo?
oslo83 said:
LOL, Stop your mumbo-jumbos.
I guess you'r still with nougat partitioning because you're using a pretty much outdated twrp.
So just dload flash a nougat 'service repair firmware' from the same region you're firmware is actually, and not any random update.app you 'made' yourself.
For this you'll need a micro-sdcard (or usb-otg) exfat formated :
https://forum.xda-developers.com/honor-9/development/firmware-huawei-honor-9-stf-l09-stock-t3696892
Click to expand...
Click to collapse
Unfortunatly, there only nougat 'service repair firmware' available publicly as far I know.
So, for now, you can only use this when on nougat.
When on oreo, you should use HuRUpdater with oreo's Twrp.
Or if you're oreo device is really messed badly, a paying app called DC-Phoenix then HuRUpdater.

Any root galaxy a10s

Is there any way to work root for galaxy a10s i tried all the methods and didn't work with me ... even the boot.img method via odin didn't work with me .... is there any other way ?????
Galaxy a10s Mediatek MT6762 Helio P22 (12 nm)
CPU Octa-core 2.0 GHz Cortex-A53
Any helps please
Good morming,
This link worked for me: https://www.full-repair-firmware.com/2019/10/how-to-root-a107m-9.0.html
Although I didn't use the BL from the (in my case TELCEL SM-A107M) firmware, I downloaded this Boot file (I don't remember from where ), it is for A107MUBU3ASI4:
https://mega.nz/#!tRgXgCTI!dHdQPB-MSQ7Znpm7d-Nme7lwwc_w2-im75putNHxgtM
SO I copied the boot file to the sdcard, ran magisk manager on the phone, selected patch boot image and selected the boot image on the sdcard for patching, after the patching is done, I copied the image back to the PC, started Odin, booted the phone to download mode (turn it off, connect the phone to the usb cable press power button to start the phone, then release the power button and press both volume buttons until it boots to download mode), then when Odin detected the phone I clicked the AP button on Odin, selected the patched boot file that I copied from the phone and then clicked on the Start button to flash the image, then when Odin finished, the phone booted automatically ... the tutorial says that the phone will ask for a factory reset and delete all the phone info, but in my case it didn't asked for nothing nor deleted my data, so I got root without losing information, as soon as the phone booted it was already rooted an root was working witout me having to do anything.
The first time I rooted my phone I installed xposed framework, then had some troubles with the beta version, got a bootloop and had to re-flash the original firmware, BUT when I tried to reflash the patched boot image I got the PreNormal message and had to wait a week to root again my phone .
So I googled and then found some info about the KG/RMM problem, but couldn't find a zip that worked for the SM-A107M, also since there is no TWRP available to this model, I wouldn't be able to flash the zip anyway, but I found that deleting this files:
libvkjni.so
libvkmanager.so
libvkservice.so
KnoxGuard.apk/Rlc.apk
will disable the service.
The first 3 are in the system/lib directory, the knoxGuard apk is in the priv-app/knoxGuard directory.
So I rooted the phone again (after waiting 7 day to prenormal to end) and in the first boot I
installed "Root Explorer" from the play store (Any file manager with root privileges will work) and deleted 4 of those files (the RLC.apk I couldn't find) and after 2 weeks of rebooting, reinstalling xposed, getting the bootloop problem again , re-flashing original firmware (without the KG/RMM prenormal state), re-rooting, and finally installing xposed without problems (in my phone the 4.6.0 beta version didn't work so I inistalled the 4.5.1 beta) I am happy with my rooted, xposed phone.
I would really like if somebody created/xported a TWRP for this model, but in the interim all is good the ends good.
Regards
:good: Thanks for the wonderful information .... But the problem I have is KGG / RM PRENORMAL STATE .... must do cancellation of the first ...
If you have already Prenormal state, then you have to wait 7 days, dont turn off your phone, don't restart and don't disconnect from the internet, then after the 7 days (168 hrs) the prenormal state should disappear!
Check this link:
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
Best Regards
I did not find prenormal state or normal.....
I found : KG status : checking
OEM unlock : off
Then, if not in prenormal, you should be able to flash and root your phone!
cheveguerra said:
Then, if not in prenormal, you should be able to flash and root your phone!
Click to expand...
Click to collapse
Good night
Unfortunately .... this root method did not work for me .... via Magisk ... I don't know what the problem is .... but this method did not work for me which is in many websites and it is the same way .... As follows my device info :
Ap: A107FXXU3ASJ5
CP: A107FXXU3ASJ1
CSC: A107FOJM3ASJ5
Model: sm- A107F / DS
The same method is used by everyone via Magisk ...
My device have no problem:
Unlocking the device bootloader
OEM unlock: off
Kg status: checking
I have no prenormal state
I followed all the steps on the sites
1- I downloaded Galaxy A10S Firmware
2- I downloaded and installed the latest Magisk Manager app.
3- Copied only the boot.img file from the extracted folder to a device storage.
4- opened the Magisk Manager app then clicked on on “Patch Boot Image File”.
5- when patched boot img finished from Magisk .... I renamed to boot.img and used 7zip and archived it to .tar format ....
6- I flashed via Odin in download mode but I got on fail .....
I don't know what problem ...
But this is what happened !!!!
Did you use the boot image (BL) I posted on the second post??
Download the file, copy it to your phone, use magisk manager to patch it, copy patched image to pc, flash via Odin to your phone.
Regards
No, I didn't use that boot img .... It the same : A107F .... A107M.. ???
I will try later.
I used that boot in your post .... for A107m.... l flashed via Odin in my A107F ... It's flashed in my device.... but when I boot to Magisk..... no root........ for that I think will wait someone to create twrp for galaxy A10s then I flash root.... Thanks for everything....
anybody with A107F firmware pls. i need to try to root mine.
raymihsenior said:
anybody with A107F firmware pls. i need to try to root mine.
Click to expand...
Click to collapse
You can go to sammobile there you can find it:good:
Try this for A107F
drive.google.com/file/d/1-5G6FDEzfT2oJ86aOneYGU1er7hbORIA/view?usp=drivesdk
DangVN said:
Try this for A107F
drive.google.com/file/d/1-5G6FDEzfT2oJ86aOneYGU1er7hbORIA/view?usp=drivesdk
Click to expand...
Click to collapse
....
This is TWRP 3.3.1.0 beta for galaxy A107F.... It's working????
.... Are you tested that ????
It is in img format and not in tar ... do we have to convert it to tar to flash it via odin?.
....
What do i need to do to make the oem unlock option appear again?
I've already tried the turning off updates and changing dates thing.
And I waited out the 7 days ( Which was difficult since my IP doesnt have a stable connection.)
I've started doubting if it even exists at all.
I only got my A10s for free from a carrier plan.
KG Status is Normal
OEM is still locked and nowhere to be seen
Helios007 said:
What do i need to do to make the oem unlock option appear again?
I've already tried the turning off updates and changing dates thing.
And I waited out the 7 days ( Which was difficult since my IP doesnt have a stable connection.)
I've started doubting if it even exists at all.
I only got my A10s for free from a carrier plan.
KG Status is Normal
OEM is still locked and nowhere to be seen
Click to expand...
Click to collapse
......
If you made all the attempts and didn't succeed with you ... Install the stock firmware for your country ... and you delay the date a few months earlier ... then go to update the program .... then you should have an OEM unlock
Hastoma said:
......
If you made all the attempts and didn't succeed with you ... Install the stock firmware for your country ... and you delay the date a few months earlier ... then go to update the program .... then you should have an OEM unlock
Click to expand...
Click to collapse
And how does one Install a "different/new" firmware?
I remember doing it once or twice with Odin with a firmware I got from sammobile SMA-107f.
Succeeded. Although I don't know if it actually worked, since it booted up just like the first time I got it, with the carriers default wallpaper and pre-loaded apps.
I've been trying to root the SM-A107F for weeks now but no luck.. Any help will be appreciated
cheveguerra said:
Good morming,
This link worked for me: https://www.full-repair-firmware.com/2019/10/how-to-root-a107m-9.0.html
Although I didn't use the BL from the (in my case TELCEL SM-A107M) firmware, I downloaded this Boot file (I don't remember from where ), it is for A107MUBU3ASI4:
https://mega.nz/#!tRgXgCTI!dHdQPB-MSQ7Znpm7d-Nme7lwwc_w2-im75putNHxgtM
SO I copied the boot file to the sdcard, ran magisk manager on the phone, selected patch boot image and selected the boot image on the sdcard for patching, after the patching is done, I copied the image back to the PC, started Odin, booted the phone to download mode (turn it off, connect the phone to the usb cable press power button to start the phone, then release the power button and press both volume buttons until it boots to download mode), then when Odin detected the phone I clicked the AP button on Odin, selected the patched boot file that I copied from the phone and then clicked on the Start button to flash the image, then when Odin finished, the phone booted automatically ... the tutorial says that the phone will ask for a factory reset and delete all the phone info, but in my case it didn't asked for nothing nor deleted my data, so I got root without losing information, as soon as the phone booted it was already rooted an root was working witout me having to do anything.
The first time I rooted my phone I installed xposed framework, then had some troubles with the beta version, got a bootloop and had to re-flash the original firmware, BUT when I tried to reflash the patched boot image I got the PreNormal message and had to wait a week to root again my phone .
So I googled and then found some info about the KG/RMM problem, but couldn't find a zip that worked for the SM-A107M, also since there is no TWRP available to this model, I wouldn't be able to flash the zip anyway, but I found that deleting this files:
libvkjni.so
libvkmanager.so
libvkservice.so
KnoxGuard.apk/Rlc.apk
will disable the service.
The first 3 are in the system/lib directory, the knoxGuard apk is in the priv-app/knoxGuard directory.
So I rooted the phone again (after waiting 7 day to prenormal to end) and in the first boot I
installed "Root Explorer" from the play store (Any file manager with root privileges will work) and deleted 4 of those files (the RLC.apk I couldn't find) and after 2 weeks of rebooting, reinstalling xposed, getting the bootloop problem again , re-flashing original firmware (without the KG/RMM prenormal state), re-rooting, and finally installing xposed without problems (in my phone the 4.6.0 beta version didn't work so I inistalled the 4.5.1 beta) I am happy with my rooted, xposed phone.
I would really like if somebody created/xported a TWRP for this model, but in the interim all is good the ends good.
Regards
Click to expand...
Click to collapse
This is very interesting. KG State has been non existent on my device, I can flash modified firmware since day 1. I'll try this, I tried patching the whole AP_ file and there are problems with the signal, I did not try only patching the boot.img
Thanks!
ShaDisNX255 said:
This is very interesting. KG State has been non existent on my device, I can flash modified firmware since day 1. I'll try this, I tried patching the whole AP_ file and there are problems with the signal, I did not try only patching the boot.img
Thanks!
Click to expand...
Click to collapse
when you flash the patched AP.tar you should also be flashing it with the rest of the firmware.. tjw even says somewhere on his github you shouldnt flash the patched AP by itself

Categories

Resources