Database Users

A2017G Bootloader mode on 7.1.1?

EDIT: Fixed! Big thanks to @S0wL , @bkores , @tamahouse02 and @tron1 for the help. I made a guide to help other people with the same problem:
Guide to get TWRP again HERE
Okay, it seems to me that I messed up kinda badly. The phone is fully operational, but after I got to 7.0 the stock recovery replaced good ol' TWRP... which left me with an unlocked bootloader and an useless recovery. I have no root, and that's pretty much the only thing that matters to me. I downloaded @bkores 's Axon7Toolkit but there is NO way to get fastboot on the damned thing. After the program tries to get to bl mode (I assume adb reboot bootloader?) the ZTE logo flashes and the unlocked BL image appears, then the phone starts as normal.
Same thing with the leaked 7.1.1, no difference.
I tried EDL, recovery, that shady factory test mode thing, no one gives fastboot... Any ideas as to why I can't get there??+
I suspect it may be something related to the OEM unlocking option in the dev options, but it is set to ON and greyed out. so no idea

Try the menu on the boot screen.

Choose an username... said:
Okay, it seems to me that I messed up kinda badly. The phone is fully operational, but after I got to 7.0 the stock recovery replaced good ol' TWRP... which left me with an unlocked bootloader and an useless recovery. I have no root, and that's pretty much the only thing that matters to me. I downloaded @bkores 's Axon7Toolkit but there is NO way to get fastboot on the damned thing. After the program tries to get to bl mode (I assume adb reboot bootloader?) the ZTE logo flashes and the unlocked BL image appears, then the phone starts as normal.
Same thing with the leaked 7.1.1, no difference.
I tried EDL, recovery, that shady factory test mode thing, no one gives fastboot... Any ideas as to why I can't get there??+
I suspect it may be something related to the OEM unlocking option in the dev options, but it is set to ON and greyed out. so no idea
Click to expand...
Click to collapse
Sounds like the issue is with the ROM like it is somehow blocking you from accessing bootloader mode. It's definitely not my toolkit.

Choose an username... said:
Okay, it seems to me that I messed up kinda badly. The phone is fully operational, but after I got to 7.0 the stock recovery replaced good ol' TWRP... which left me with an unlocked bootloader and an useless recovery. I have no root, and that's pretty much the only thing that matters to me. I downloaded @bkores 's Axon7Toolkit but there is NO way to get fastboot on the damned thing. After the program tries to get to bl mode (I assume adb reboot bootloader?) the ZTE logo flashes and the unlocked BL image appears, then the phone starts as normal.
Same thing with the leaked 7.1.1, no difference.
I tried EDL, recovery, that shady factory test mode thing, no one gives fastboot... Any ideas as to why I can't get there??+
I suspect it may be something related to the OEM unlocking option in the dev options, but it is set to ON and greyed out. so no idea
Click to expand...
Click to collapse
Feel the same, 7.1.1 stock recovery is evil, it keep coming back after flash twrp. LOL
Here what I didi to get twrp on 7.1.1:
1. Use axon7tool -w recovery (twrp of couse)
2. Watch closely the cmd, when it said "Successful!","Reboot in 5 second" - unplug your phone
3. Use Volume Up + Power to get to recovery (twrp)
4. Mount > Mount System (dont check read only)
5. Flash something - I don't know - But I get the feeling that it stop stock recovery coming back - I personally flash Chinese Modem (because I have to ))
6. Reboot system

@bkores Yeah I'm pretty sure it's not your toolkit since I can't access it even with key comb, adb, option on the unl bl page...
@lafester Nope, tried many times. It just boots to normal whenever I select fastboot
@tamahouse02 Well I believe that should work, but I can't get axon7tool not to crash... I'll keep trying, maybe it's a driver or sth.

Choose an username... said:
@bkores Yeah I'm pretty sure it's not your toolkit since I can't access it even with key comb, adb, option on the unl bl page...
@lafester Nope, tried many times. It just boots to normal whenever I select fastboot
@tamahouse02 Well I believe that should work, but I can't get axon7tool not to crash... I'll keep trying, maybe it's a driver or sth.
Click to expand...
Click to collapse
Have you restart after install zadig driver?
1. From system: adb reboot edl
2. Install zadig driver
3. Hold "Volume Up + Power"
4. Enter system again: adb reboot edl
5. axon7tool -w recovery

tamahouse02 said:
Have you restart after install zadig driver?
1. From system: adb reboot edl
2. Install zadig driver
3. Hold "Volume Up + Power"
4. Enter system again: adb reboot edl
5. axon7tool -w recovery
Click to expand...
Click to collapse
yes, like 4 times already. I even used the stock Qualcomm COM3 drivers... no dice.
the thing is that I had to do the same when I did the stuff on android 6 and it worked after some time. I even wrote the procedure on another thread xd

Choose an username... said:
yes, like 4 times already. I even used the stock Qualcomm COM3 drivers... no dice.
the thing is that I had to do the same when I did the stuff on android 6 and it worked after some time. I even wrote the procedure on another thread xd
Click to expand...
Click to collapse
Not same my axon7tool. I use this https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254

Bootloader Mode is Disable/strip in G variant, and if this is how ZTE is headed to future updates it seems like U will have a Disable Bootloader Mode as well.
If you guy can rollback to MM , you can Unlock there using @bkores tool.

DrakenFX said:
Bootloader Mode is Disable/strip in G variant, and if this is how ZTE is headed to future updates it seems like U will have a Disable Bootloader Mode as well.
If you guy can rollback to MM , you can Unlock there using @bkores tool.
Click to expand...
Click to collapse
I was thinking about that, but does mifavor let you roll back from an SD update? I'll try later, but i doubt it.
Besides from that is there any way to flash stuff from the stock recovery? It tells me that ZIPs have to be signed only

tamahouse02 said:
Feel the same, 7.1.1 stock recovery is evil, it keep coming back after flash twrp. LOL
Here what I didi to get twrp on 7.1.1:
1. Use axon7tool -w recovery (twrp of couse)
2. Watch closely the cmd, when it said "Successful!","Reboot in 5 second" - unplug your phone
3. Use Volume Up + Power to get to recovery (twrp)
4. Mount > Mount System (dont check read only)
5. Flash something - I don't know - But I get the feeling that it stop stock recovery coming back - I personally flash Chinese Modem (because I have to ))
6. Reboot system
Click to expand...
Click to collapse
In step 1, which TWRP version did you use? The latest 3.1.0.-0 ?

dnlilas said:
In step 1, which TWRP version did you use? The latest 3.1.0.-0 ?
Click to expand...
Click to collapse
Official 3.0.4.1

@tamahouse02
The latest "official" TWRP is at TWRP site https://twrp.me/devices/zteaxon7.html , version 3.1.0-0.
Is there any problem using it instead of the previous "official" 3.0.4.1 ?
Edit: I also read on TWRP site:
"Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."
This is in sync with your information requiring to reboot immediately to TWRP (step 2 and 3).

dnlilas said:
@tamahouse02
The latest "official" TWRP is at TWRP site https://twrp.me/devices/zteaxon7.html , version 3.1.0-0.
Is there any problem using it instead of the previous "official" 3.0.4.1 ?
Edit: I also read on TWRP site:
"Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."
This is in sync with your information requiring to reboot immediately to TWRP (step 2 and 3).
Click to expand...
Click to collapse
I use 3.0.4.1 because I flash plenty things before without any issue, so I keep using it.
After write recovery by axon7tool, it's reboot automatically and override the recovery, that why I have to unplug to stop the reboot, and also flash all I can - fortunaeally​ it also stop recovery be overrided

@tamahouse02 sorry to ask, but is the a7tool of the link a fixed version? how does it differ from the one i have?

I've been in the same situation like you @Choose an username... Updated to nougat on G model and I had not bootloader. This is what I did :
1. Downloaded the tool from here https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
2. Installed the driver using the install driver option that you can choose once you connect you phone to your computer
3. Use the tool to perform the unlock bootloader command again even though you have unlocked it before
4. Use the tool to install twrp, it will boot the phone in twrp
5. Flash Supersu before you boot the system first time after flashing twrp
5. Install whatever version of android want after

@S0wL Funny, I had to use Zadig to make it work. I'll try r n, thx

Choose an username... said:
@S0wL Funny, I had to use Zadig to make it work. I'll try r n, thx
Click to expand...
Click to collapse
Use Zadig then and let me know if it worked

@S0wL I can't use bootloader unlock on it, says "This option does not support your device!"
How did you do this??

Choose an username... said:
@tamahouse02 sorry to ask, but is the a7tool of the link a fixed version? how does it differ from the one i have?
Click to expand...
Click to collapse
I try your version once, but it seems not work for me, so I keep using the old one.
---------- Post added at 03:42 AM ---------- Previous post was at 03:39 AM ----------
Choose an username... said:
@S0wL I can't use bootloader unlock on it, says "This option does not support your device!"
How did you do this??
Click to expand...
Click to collapse
I thought you had already unlocked bootloader? Why have you done it twice?

Please help! ZTE Axon 7 won't boot after deleting Lineage and TRWP

Hi,
don't know if this problem has already occurred before.
I had lineage and TRWP installed on my Axon 7 (EU version) and wanted to go back to the stock a2017g.
Therefore I deleted the ROM and wiped everything with TWRP.
Then I deleted TWRP and now i'm stuck at the the bootloader (which is unlocked), but TWRP seems to be gone.
The main problem is, whenever I try to flash a new stock rom (via recovery), I get the error "signature verification failed" and the process is aborted with no change to the system whatsoever.
Is there anything I can do at this point or is my phone practically dead?
Thanks in advance for any help.

tempest89 said:
Hi,
don't know if this problem has already occurred before.
I had lineage and TRWP installed on my Axon 7 (EU version) and wanted to go back to the stock a2017g.
Therefore I deleted the ROM and wiped everything with TWRP.
Then I deleted TWRP and now i'm stuck at the the bootloader (which is unlocked), but TWRP seems to be gone.
The main problem is, whenever I try to flash a new stock rom (via recovery), I get the error "signature verification failed" and the process is aborted with no change to the system whatsoever.
Is there anything I can do at this point or is my phone practically dead?
Thanks in advance for any help.
Click to expand...
Click to collapse
Try to boot into bootloader interface, and issue command "fastboot flash recovery TWRP.img" on your computer( the current working directory should contain the TWRP.img file) . If your bootloader is unlocked, you should see no error of this command. Then press up/down button to select recovery mode. You should see the familiar TWRP again. Good luck!

tempest89 said:
Hi,
don't know if this problem has already occurred before.
I had lineage and TRWP installed on my Axon 7 (EU version) and wanted to go back to the stock a2017g.
Therefore I deleted the ROM and wiped everything with TWRP.
Then I deleted TWRP and now i'm stuck at the the bootloader (which is unlocked), but TWRP seems to be gone.
The main problem is, whenever I try to flash a new stock rom (via recovery), I get the error "signature verification failed" and the process is aborted with no change to the system whatsoever.
Is there anything I can do at this point or is my phone practically dead?
Thanks in advance for any help.
Click to expand...
Click to collapse
Did you try flashing an official full zip, like B10? That's another thing you can try, since you're going to lose TWRP after you flash a stock rom anyways

If you dont have recovery, flash it from edl mode, you can flash twrp or stock.
Once you install it, performa a full wipe from stock recovery, and flash a full zip.
I have similar problems, I dont loose recovery, but stock dont boot after coming back from aosp, a factory reset did the job. I think is because different filesystems in data partition

Choose an username... said:
Did you try flashing an official full zip, like B10? That's another thing you can try, since you're going to lose TWRP after you flash a stock rom anyways
Click to expand...
Click to collapse
Hi, the B10 ROM from the ZTE homepage did the trick.
Worked out nicely.
Thank you so much.
One final question remains for myself: How can I relock the bootloader (so that the 5 second screen won't show up at the start).
Tried different ways with adb and fastload, but nothing seemed to have an effect here.
So what to do?
Thank you again for your help.

tempest89 said:
Hi, the B10 ROM from the ZTE homepage did the trick.
Worked out nicely.
Thank you so much.
One final question remains for myself: How can I relock the bootloader (so that the 5 second screen won't show up at the start).
Tried different ways with adb and fastload, but nothing seemed to have an effect here.
So what to do?
Thank you again for your help.
Click to expand...
Click to collapse
you shouldn't. Fastboot should do the trick, by doing fastboot oem lock, but many people reported bricking and bad stuff...
Actually that screen comes very handy in case of a brick or if you want to enter a specific mode.l, you just select the mode and voila
Do you have fastboot? I don't know if B10 still has it, but 7.0 hasn't got it

Choose an username... said:
you shouldn't. Fastboot should do the trick, by doing fastboot oem lock, but many people reported bricking and bad stuff...
Actually that screen comes very handy in case of a brick or if you want to enter a specific mode.l, you just select the mode and voila
Do you have fastboot? I don't know if B10 still has it, but 7.0 hasn't got it
Click to expand...
Click to collapse
Hi,
I tried adb and fastboot via pc and with the axon toolkit.
The adb worked fine, but no sign of effect by the fastboot commands.
So I guess I don't have it.
Is there any other solution to at least bypass the 5 second screen?
Thanks

tempest89 said:
Hi,
I tried adb and fastboot via pc and with the axon toolkit.
The adb worked fine, but no sign of effect by the fastboot commands.
So I guess I don't have it.
Is there any other solution to at least bypass the 5 second screen?
Thanks
Click to expand...
Click to collapse
Lol fastboot is not something like EDL, it looks similar to the 5 sec screen...
When you get the 5 sec screen, use the vol keys and pwr to get to the Fastboot option and enter - it should reboot and get to fastboot after some time
You should look up what fastboot, EDL, ADB and DFU are before doing all this stuff - you can mess up badly, and by not knowing you're complicating everything - my explanation and your understanding

[Brick?] How to solve problem with A2017G (every mode available)

Good evening, guys,
I'm at a loss as to what is happening with my A2017G.
I had TWRP 3.1.0-2, B04 and SuperSU, but the SU wasn't working properly (the message that root privileges were given to my root apps kept popping up but the actual apps didn't work as intended, so to flash the alternative file that I found somewhere in the forums here.
After that, I could not pass the ZTE logo in order to boot the system.
Went back to TWRP, flashed bootstack and stock system by tron again, SuperSU - and the same result.
Without knowing what else to do, I grabbed the full stock B04 file and tried to flash it.
Now, I have a phone whith stock recovery working, without fastboot, with FTM mode, with EDL mode all working, but I can't seem to use one of those in order to restore my phone that, when I try to boot to system, keeps stuck at the screen with the message that the bootloader has been unlocked.
I tried flashing twrp and the update.zip through Mi Flash, but I get a syntax error (my device shows as COM3);
In recovery, when I choose to apply upgrade through SD, a message appears "You can't upgrade from SD card, sorry";
FTM mode works and my phone loads as an adb device (seeing in Axon 7 tool), but if I try to sideload the update.zip through the Windows 10 cmd it crashes with a message saying "bad alloc", or something.
So, I'm at a loss here. I have every modes working, and I still cannot flash anything to my device?
Or am I doing it wrong?
Thank you.

I'm almost sure you can't just flash an official update zip with MiFlash, so do this:
Download this zip, comes from djkuz. It is the full A2017G system with fbop and fastboot
https://mega.nz/#!ZhwR1BAD!PuIWa5Viv...iR-j1U8wZZidTw
After that unpack it and use MiFlash to get it flashed nicely on your device. When you finish, you'll have B10 I think. I experienced random reboots without any thermal problems (even rebooted while it was in my pocket) so you might be better off going to RR but be real careful if/when going back to stock if you decide to do this (i had a DFU brick )

Choose an username... said:
I'm almost sure you can't just flash an official update zip with MiFlash, so do this:
Download this zip, comes from djkuz. It is the full A2017G system with fbop and fastboot
https://mega.nz/#!ZhwR1BAD!PuIWa5Viv...iR-j1U8wZZidTw
After that unpack it and use MiFlash to get it flashed nicely on your device. When you finish, you'll have B10 I think. I experienced random reboots without any thermal problems (even rebooted while it was in my pocket) so you might be better off going to RR but be real careful if/when going back to stock if you decide to do this (i had a DFU brick )
Click to expand...
Click to collapse
Flashing the extracted B10 package solved it, thanks!
Until now, everything's smooth, running B04.
Thank you.

Phone bricked, Recovery Tool not working, bootloader stuck locked, help???

Hi guys...
So my OnePlus 2 was having some issues yesterday, and I flashed the stock ROM. This was completely fine and dandy, but I also wanted to put the stock recovery on it. I made sure OEM unlocking was on, went into fastboot, and typed in "fastboot oem unlock" like normal. It finished in like a tenth of a second which I thought was a little strange. The phone rebooted and I put it back into fastboot. I tried to flash the recovery and it said (remote device is locked. Cannot flash images). So at this point I was frustrated. I went into TWRP and installed the SuperSU binary. Then, I went to the Play Store, downloaded Flashify, and flashed the recovery onto my phone. I restarted my phone.... and bam. Recovery wouldn't work anymore. And then when I tried to boot into normal Android it still wouldn't work, just stuck on the OnePlus and Android screen, as if there was no /system/ partition. I can still get it into Fastboot, and I put it in EDL mode and installed the Qualcomm 9008 driver, and flashed OxygenOS 3.0.2 through the MSM downloader from https://forums.oneplus.net/threads/updated-28-06-2016-mega-unbrick-guide-for-a-hard-bricked-oneplus-2.347607/ and the MSM downloader just gave me an error that, in garbage text, said something about Sahara and Firehouse or something like that. I did get it to go successfully by downloading a different recovery package (I believe it was Color OS 2.0) but I have a ONE A2005 and I belive that was meant for ONE A2001 and it caused my phone to constantly flash rapidly at the Oneplus and Android screen (it would start to boot then immediately shut off). Fastboot still works but it still says the bootloader is locked so I can't really do anything. Any help would be much appreciated!
Jack

Update: I finally got Recovery to work. However, it still gets stuck on the OnePlus & Android screen, even after sideloading a stock ROM and installing it via the stock recovery. I fear my boot.img is corrupted. Does anyone happen to know where I can find a stock ROM that comes with recovery.img, boot.img, system.img, et cetera?

Actually, nevermind. It says oem unlock is disabled, and I can't even get into the OS to enable it.

superblox02 said:
Actually, nevermind. It says oem unlock is disabled, and I can't even get into the OS to enable it.
Click to expand...
Click to collapse
You should be able to unlock it in fastboot or adb
OEM unlock or something like that
Check this thread https://forums.oneplus.net/threads/...wrp-root-nandroid-efs-backup-and-more.345478/

How to use EDL cable to flash stock/custom firmware on ZTE Trek 2

I found the instructions on how to successfully use the jasminetool to flash my Trek 2 tablet which worked great and had TWRP installed on my device. Even though I was running B15 I still wanted try out B17 so I used the *.zip TWRP-flashable file to install, and performed a cache/dalvik wipe as well. Immediately after performing this, my tablet stopped booting up completely except for booting into the new recovery menu giving me the option to choose fastboot, adb, factory reset, recovery, power off, or reboot. No matter which option I choose now the tablet always either goes back to this screen or loads the AT&T logo and will not ever boot and remains stuck on this screen. I can no longer even turn off the tablet's screen, and when I try to mount the SD card using the menus it says "SD card not mountable." I'm aware that I can purchase an EDL cable for the Qualcomm 9008 port and possibly flash the stock recovery back on to the unit and then flash either Marshmellow or possibly Nougat back on to the tablet, but I have absolutely no idea how to do this.
Will the EDL cable allow me to actually reboot the tablet back into EDL mode to perform this flash using zadig and/or the jasminetool app? Are there any guides out there that explain how to use the EDL cable in Windows or Linux in order to flash my stock recovery image back on to the tablet? I feel that if I can flash it back on to the stinking thing that I can figure out the rest from there, but I'm hoping that an actual EDL cable will allow me to unbrick this tablet and at least get me back to MM or Nougat and leave well enough alone. Originally I tried flashing the stock B17 image but it kept freezing at the AT&T logo but still allowed me access to TWRP, but after trying the latest builds of AOKP and Lineage none of the firmwares would allow me to boot into Android at all, and after the last B17 flash is when I started to lose access to TWRP or any functionality at all. Some quick instructions on how to use an EDL cable with this particular tablet would be great and highly appreciated. I've RTFM'd but haven't found any solid instructions on how to use the cable to put the stock recovery back on to the tablet.

bmurphr1 said:
I found the instructions on how to successfully use the jasminetool to flash my Trek 2 tablet which worked great and had TWRP installed on my device. Even though I was running B15 I still wanted try out B17 so I used the *.zip TWRP-flashable file to install, and performed a cache/dalvik wipe as well. Immediately after performing this, my tablet stopped booting up completely except for booting into the new recovery menu giving me the option to choose fastboot, adb, factory reset, recovery, power off, or reboot. No matter which option I choose now the tablet always either goes back to this screen or loads the AT&T logo and will not ever boot and remains stuck on this screen. I can no longer even turn off the tablet's screen, and when I try to mount the SD card using the menus it says "SD card not mountable." I'm aware that I can purchase an EDL cable for the Qualcomm 9008 port and possibly flash the stock recovery back on to the unit and then flash either Marshmellow or possibly Nougat back on to the tablet, but I have absolutely no idea how to do this.
Will the EDL cable allow me to actually reboot the tablet back into EDL mode to perform this flash using zadig and/or the jasminetool app? Are there any guides out there that explain how to use the EDL cable in Windows or Linux in order to flash my stock recovery image back on to the tablet? I feel that if I can flash it back on to the stinking thing that I can figure out the rest from there, but I'm hoping that an actual EDL cable will allow me to unbrick this tablet and at least get me back to MM or Nougat and leave well enough alone. Originally I tried flashing the stock B17 image but it kept freezing at the AT&T logo but still allowed me access to TWRP, but after trying the latest builds of AOKP and Lineage none of the firmwares would allow me to boot into Android at all, and after the last B17 flash is when I started to lose access to TWRP or any functionality at all. Some quick instructions on how to use an EDL cable with this particular tablet would be great and highly appreciated. I've RTFM'd but haven't found any solid instructions on how to use the cable to put the stock recovery back on to the tablet.
Click to expand...
Click to collapse
1. forgot to remove dm-verity
2. There is a specific guide to return stock rom and undo warning menu, but it has flashing stock recovery b15 with jasminetool and install update.zp b17
stock recovery
stock rom
edit.

this is what appears if I am right?

juniorgerman said:
this is what appears if I am right?
Click to expand...
Click to collapse
That's correct. The guide I followed mentioned nothing about noverity so it seems that's where my problem is. It boots to that screen and then will either show the AT&T logo or you press a button and it goes into the menu where you can restart, bootloader, adb, reset/power off/etc. and none of the options work. Access to TWRP is completely gone and any option I choose makes the tablet reboot and go right back to that screen. Whoever wrote the guide I used missed a huge step, but I do have the stock recovery file from jasminetool and an EDL cable on the way just in case it's needed since I can't even get the tablet to be recognized in adb when plugged in.

bmurphr1 said:
That's correct. The guide I followed mentioned nothing about noverity so it seems that's where my problem is. It boots to that screen and then will either show the AT&T logo or you press a button and it goes into the menu where you can restart, bootloader, adb, reset/power off/etc. and none of the options work. Access to TWRP is completely gone and any option I choose makes the tablet reboot and go right back to that screen. Whoever wrote the guide I used missed a huge step, but I do have the stock recovery file from jasminetool and an EDL cable on the way just in case it's needed since I can't even get the tablet to be recognized in adb when plugged in.
Click to expand...
Click to collapse
it happens that dm-verity is from android marshmallow and also the developer that created the guide thinks he will use the rom, because the rom of LineageOS and AOKP remove dm-verity without using the file already mentioning, but if he will use stock rom with root you must use the file that you mention
Enviado desde mi SM-S337TL mediante Tapatalk

juniorgerman said:
it happens that dm-verity is from android marshmallow and also the developer that created the guide thinks he will use the rom, because the rom of LineageOS and AOKP remove dm-verity without using the file already mentioning, but if he will use stock rom with root you must use the file that you mention
Enviado desde mi SM-S337TL mediante Tapatalk
Click to expand...
Click to collapse
That makes more sense to me than just not including it in the guide. When my EDL cable comes in, I should be able to force the tablet into EDL mode and use jasminetool to return the tablet to the stock recovery image I backed up, and then use fastboot to push the original firmware on to the device or re-install TWRP and attempt to flash a working custom ROM. That makes me feel better about not knowing about the no-verity situation. I've seen the video of someone using a piece of copper and plugging the tablet into their computer and removing it about 5 seconds after plugged in, which forces the tablet into EDL mode just like a physical EDL cable does, and use jasminetool to restore the stock recovery. I will probably do it in Linux this next time around since you need to do some rather wonky things in Windows 10 to run jasminetool and zadig, including booting Win10 into Test Mode to remove driver signature reinforcement.