yashsingh1/xdaforums huggingface dataset:
[Magisk] Dreamer(3MF):
Do The Next Steps:

- Disable All Modules Except ClearDalvikCache4Magisk From

Magisk Manager (Modules)

& Also Disable All Apps Except Terminal Emulator From

Magisk Manager (SuperUser)

Then Reboot

- Terminal Emulator --> Write

su

--> Write

getenforce

(Most Devices) Or

sestatus

(Some Devices) --> Click On Enter --> Write

setenforce 0

(For Permissive Mode) Or

setenforce 1

(For Enforcing Mode) --> Click On Enter --> Write

getenforce

(Most Devices) Or

sestatus

(Some Devices) --> Click On Enter --> Send The Screenshot Of Terminal Emulator

- Download The Test Module Of SELinuxModeInverter4Magisk [

SELinuxModeInverter4Magisk-v1.0.5AW1(Test)

] From This Link https://androidfilehost.com/?w=files&flid=274655 & Flash It Thru Magisk Manager Then Reboot

- Wait About 20 Min.

- Terminal Emulator --> Write

su

--> Write

getenforce

(Most Devices) Or

sestatus

(Some Devices) --> Click On Enter --> Send The Screenshot Of Terminal Emulator

- Reboot & Wait About 20 Min.

- Terminal Emulator --> Write

su

--> Write

getenforce

(Most Devices) Or

sestatus

(Some Devices) --> Click On Enter --> Send The Screenshot Of Terminal Emulator

- Send A Copy Of

debug-SELinux.txt

&

debug-SELinux-BU.txt

(Their Paths Are Root -->

/data/debug-SELinux.txt

,

/data/debug-SELinux-BU.txt

& For Copying These Files, Use Any Root File Explorer Such As MiXplorer)

-

Magisk Manager --> Modules --> Send Its Screenshot

&

Magisk Manager --> SuperUser --> Send Its Screenshot

- Send Full Logcat (

Download Logcat Extreme From PlayStore

) & Magisk Log (

Magisk Manager --> Log --> Magisk

&

Magisk Manager --> Log --> SuperUser

)
[Magisk] Dodgexander:
Not being able to change from permissive to enforcing in terminal right now, I think due to lack of current kernel support. I'll have to revisit this again when it's reinstated.
[Magisk] Dodgexander:
Just wanted to add the module seems to be working fine now. There has since been an update to the kernel I use to fix it. Sorry for wasting your time with this and thanks for your work.
[Magisk] kamilmirza:
thank you for support this module @OP

works perfectly on Pie with Magisk 18 :good:
[Magisk] ParanoidVisitor:
This module doesn't work on my device (lineage-16.0-j5-20190102-NIGHTLY-j5xnlte, open_gapps-arm-9.0-mini-20190209, Magisk v18.1).

Switching to enforcing mode with Terminal Emulator is ok..

When i flash SELinuxModeInverter4Magisk-v1.0.5AW(v18000)(3MF).zip thru Magisk Manager, box in module list stays afer reboot unchecked.

And when i tried to use SELinuxModeInverter4Magisk-v1.0.5A(v18000)(3MF).zip after reboot facing Blackscreen.

Any Ideas? :confused:
[Magisk] Dreamer(3MF):
Do The Next Steps:

- Disable All Modules From

Magisk Manager (Modules)

& Also Disable All Apps Except Terminal Emulator From

Magisk Manager (SuperUser)

Then Reboot

- Download ClearDalvikCache4Magisk From This Thread https://xdaforums.com/apps/magisk/module-dalvik-cache-t3787264 & Flash It Thru Magisk Manager Then Reboot

- Terminal Emulator --> Write

su

--> Click On Enter --> Write

getenforce

(Most Devices) Or

sestatus

(Some Devices) --> Click On Enter --> Write

setenforce 0

(For Permissive Mode) Or

setenforce 1

(For Enforcing Mode) --> Click On Enter --> Write

getenforce

(Most Devices) Or

sestatus

(Some Devices) --> Click On Enter --> Send The Screenshot Of Terminal Emulator

- Download The Test Module Of SELinuxModeInverter4Magisk [

SELinuxModeInverter4Magisk-v1.0.5AW1(Test)

] From This Link https://androidfilehost.com/?w=files&flid=274655 & Flash It Thru Magisk Manager Then Reboot (N.B. SELinuxModeInverter4Magisk-v1.0.5AW1(Test)(v17000)(3MF).zip Could Be Used For Magisk v18.x)

- Wait About 20 Min.

- Terminal Emulator --> Write

su

--> Click On Enter --> Write

getenforce

(Most Devices) Or

sestatus

(Some Devices) --> Click On Enter --> Send The Screenshot Of Terminal Emulator

- Reboot & Wait About 20 Min.

- Terminal Emulator --> Write

su

--> Click On Enter --> Write

getenforce

(Most Devices) Or

sestatus

(Some Devices) --> Click On Enter --> Send The Screenshot Of Terminal Emulator

- Send A Copy Of

debug-SELinux.txt

&

debug-SELinux-BU.txt

(Their Paths Are Root -->

/data/debug-SELinux.txt

,

/data/debug-SELinux-BU.txt

& For Copying These Files, Use Any Root File Explorer Such As MiXplorer)

-

Magisk Manager --> Modules --> Send Its Screenshot

&

Magisk Manager --> SuperUser --> Send Its Screenshot

- Send Full Logcat (

Download Logcat Extreme From PlayStore

) & Magisk Log (

Magisk Manager --> Log --> Magisk

&

Magisk Manager --> Log --> SuperUser

)

P.S. In-Case Of Facing A Bootloop/Bootscreen/Blackscreen Issue Due To Flashing A Module,

- For Magisk Users, Download CoreOnlyMode4Magisk From This Thread https://xdaforums.com/apps/magisk/module-core-mode-bootloop-solver-modules-t3817366 Then Flash It Thru TWRP Recovery

- For Non-Magisk Users (Unity), Reflash The Module Thru TWRP Recovery To Uninstall The Module
[Magisk] ParanoidVisitor:
(Deleted)
[Magisk] Dreamer(3MF):
Do The Following

- Enable SELinuxModeInverter4Magisk From Magisk Manager Then Reboot

- Terminal Emulator --> Write

su

--> Click On Enter--> Write

getenforce

(Most Devices) Or

sestatus

(Some Devices) --> Click On Enter --> Send The Screenshot Of Terminal Emulator

- Wait About 30 Minutes

- Terminal Emulator --> Write

su

--> Click On Enter --> Write

getenforce

(Most Devices) Or

sestatus

(Some Devices) --> Click On Enter --> Send The Screenshot Of Terminal Emulator

- Send A Copy Of

debug-SELinux.txt

&

debug-SELinux-BU.txt

(Their Paths Are Root -->

/data/debug-SELinux.txt

,

/data/debug-SELinux-BU.txt

& For Copying These Files, Use Any Root File Explorer Such As MiXplorer)

-

Magisk Manager --> Modules --> Send Its Screenshot

&

Magisk Manager --> SuperUser --> Send Its Screenshot

- Send A Copy Of Magisk Log (

Magisk Manager --> Log --> Magisk

&

Magisk Manager --> Log --> SuperUser

)
[Magisk] Dreamer(3MF):
Kindly Be Informed That The Required Mentioned Logs & Screenshots Are For 2 Main Reasons

- To Help Me To Figure Out Where The Issue Is

- To Enhance/Modify The Module

According To The Last Sent Logs, The Module Changed The SELinux Mode From Permissive To Enforcing But Referring To The Mentioned Info About Facing The Issue Of Blackscreen After Using The Version Of SELinuxModeInverter4Magisk-v1.0.5A, It Means The Flashed Rom/Kernel Hasn't The Ability To Switch Between Permissive Mode & Enforcing Mode During Startup So You Have 2 Choices

- Using The Version Of SELinuxModeInverter4Magisk-v1.0.5AW To Change The SELinux Mode Within 5 Min. After Rebooting

- Flashing Another Rom/Kernel Which Supports The Ability Of Changing SELinux Mode At Booting

P.S. One Of The Functionalities Of Magisk Hide Is Hiding The Device Is In Permissive Mode To Pass The SafetyNet
[Magisk] mahmoudsaeedo:
thank you .

The thread succeeded in solving the problem in application. I did not know the solution. But I searched using the keyword selinux and the problem was solved. my device is Glaxy Not 3. Use a custom ROM .

thank you very much
[Magisk] Dreamer(3MF):
Updated SELinuxModeInverter4Magisk To 1.0.6.0!

Changelog: Rewriting The Script & Adding Extra Options

>>>To Ensure That The Module Will Work Properly, Kindly Do What Are Mentioned In The General Steps<<<

- For The Module Which Is Ended Its Name With v1300, It Supports Magisk v13.1(1310) To v13.6(1360)

- For The Module Which Is Ended Its Name With v1400, It Supports Magisk v14.0(1400) To v15.3(1531)

- For The Module Which Is Ended Its Name With v1500, It Supports Magisk v15.0(1500) To v17.3(17300)

- For The Module Which Is Ended Its Name With v17000, It Supports Magisk v17.0(17000) To v17.3(17300)

- For The Module Which Is Ended Its Name With v18000, It Supports Magisk v18.0(18000) To v18.1(18100)

- For The Module Which Is Ended Its Name With v19000, It Supports Magisk v19.0(19000) To The Latest Version

- For The Module Which Is Ended Its Name With Unity, It Supports Any-Rooting-Tool Such As SuperSU, Lineage-AddOnSU & Magisk

Kindly Be Informed That

- Some Issues Which Are Related To Magisk/Rom/Kernel Itself Can Be Solved By Using A Different Modes [Where The Wait Mode (The Default One) Can Be Used For Resolving The Issue Of Bootloop/Bootscreen/Blackscreen Which Changes The SELinux Mode Within 5 Min. After Rebooting & The Fast Mode Can Be Used For Changing The SELinux Mode At Booting But You Need Firstly To Do What Are Mentioned In The General Steps]

- For The Fast Mode, Use Any File Explorer --> Internal Storage --> DreamerMods --> The Module --> Copy The File Of Disable To

The Folder Of Wait

--> Reboot

- For The Wait Mode, Use Any File Explorer --> Internal Storage --> DreamerMods --> The Module --> Delete The File Of Disable From

The Folder Of Wait

--> Reboot
[Magisk] :
1.0.6.0 v19000 doesn't switch my selinux. Flashed the 1.0.5.0A v18000 on magisk 19.0 and selinux mode changed and my rom was shipped with permissive as default mode, so can I change to enforcing?
[Magisk] Ps24u:
After I install 1.0.6.0, I get an error in Magisk log when the phone boots:

If I revert to 1.0.5.A, clear log, reboot, this error never appears in the log.

When I use 1.0.6.0 again, it comes back.

Reproduced multiple times to be sure.

Using Magisk 18.1 on nougat.
[Magisk] Dreamer(3MF):
Updated SELinuxModeInverter4Magisk To 1.0.6.0A!

Changelog: A Tiny Fix

>>>To Ensure That The Module Will Work Properly, Kindly Do What Are Mentioned In The General Steps<<<

- For The Module Which Is Ended Its Name With v1300, It Supports Magisk v13.1(1310) To v13.6(1360)

- For The Module Which Is Ended Its Name With v1400, It Supports Magisk v14.0(1400) To v15.3(1531)

- For The Module Which Is Ended Its Name With v1500, It Supports Magisk v15.0(1500) To v17.3(17300)

- For The Module Which Is Ended Its Name With v17000, It Supports Magisk v17.0(17000) To v17.3(17300)

- For The Module Which Is Ended Its Name With v18000, It Supports Magisk v18.0(18000) To v18.1(18100)

- For The Module Which Is Ended Its Name With v19000, It Supports Magisk v19.0(19000) To The Latest Version

- For The Module Which Is Ended Its Name With Unity, It Supports Any-Rooting-Tool Such As SuperSU, Lineage-AddOnSU & Magisk

Kindly Be Informed That

- Some Issues Which Are Related To Magisk/Rom/Kernel Itself Can Be Solved By Using A Different Modes [Where The Wait Mode (The Default One) Can Be Used For Resolving The Issue Of Bootloop/Bootscreen/Blackscreen Which Changes The SELinux Mode Within 5 Min. After Rebooting & The Fast Mode Can Be Used For Changing The SELinux Mode At Booting But You Need Firstly To Do What Are Mentioned In The General Steps]

- For The Fast Mode, Use Any File Explorer --> Internal Storage --> DreamerMods --> The Module --> Copy The File Of Disable To

The Folder Of Wait

--> Reboot

- For The Wait Mode, Use Any File Explorer --> Internal Storage --> DreamerMods --> The Module --> Delete The File Of Disable From

The Folder Of Wait

--> Reboot

- For More Details, Check This Post https://xdaforums.com/apps/magisk/selinux-mode-inverter-t3775271/post76381334

-----------------------------------------------------------------------------------------

Check This Post https://xdaforums.com/apps/magisk/selinux-mode-inverter-t3775271/post76381334 & Send All The Required Files.
[Magisk] :
used 1.0.6.0A, selinux mode changed using fast mode. works now!!
[Magisk] Ps24u:
Same, if I use "Fast mode" ( put Disable inside Wait folder), then it seems to work ok.

But I think it should be better as fast mode by default, without the need for folders.

So I'll stick to 1.05A (18000), it works great even on Magisk 19.1 and I don't have to see unnecessary folder in my file explorer..

Or better for the future, maybe you can provide 2 builds instead, one Fast and one Wait..
[Magisk] mistermojorizin:
Where can I download 1.05A 18000? Seems to be deleted from AFH.
[Magisk] Ps24u:
You can grab it here :

http://videoff7.free.fr/SELinuxModeInverter4Magisk-v1.0.5A(v18000)(3MF).zip
[Magisk] mistermojorizin:
thanks!

Also, wanted to ask. If I do use the 106 version, what does the "disable" file need to be. Is it just a blank file without an extension named "disable"?
[Magisk] Ps24u:
Yes, there's a sample of it in the DreamerMods folder.
[Magisk] Dreamer(3MF):
Updated MultiFunctions4Magisk To 1.0.3.3!

Changelog: SELinuxModeInverter Is A Sub-Module Of The Main Module Of MultiFunctions Which Supports Currently The Following Functions [Clearing DalvikCache-PlayStoreWithServices-MagiskHideList, Changing The SELinux Mode, Booting The Android Into Safe Mode & Opening Magisk In Core Only Mode]

>>>To Ensure That The Module Will Work Properly, Kindly Do What Are Mentioned In The General Steps<<<

- For The Module Which Is Ended Its Name With v1300, It Supports Magisk v13.1(1310) To v13.6(1360)

- For The Module Which Is Ended Its Name With v1400, It Supports Magisk v14.0(1400) To v15.3(1531)

- For The Module Which Is Ended Its Name With v1500, It Supports Magisk v15.0(1500) To v17.3(17300)

- For The Module Which Is Ended Its Name With v17000, It Supports Magisk v17.0(17000) To v17.3(17300)

- For The Module Which Is Ended Its Name With v18000, It Supports Magisk v18.0(18000) To v18.1(18100)

- For The Module Which Is Ended Its Name With v19000, It Supports Magisk v19.0(19000) To The Latest Version

- For The Module Which Is Ended Its Name With Unity, It Supports Any-Rooting-Tool Such As SuperSU, Lineage-AddOnSU & Magisk

Kindly Be Informed That

- For Magisk Users, Disable Magisk Core Only Mode From The Section Of Settings In Magisk Manager

- For Activating The Functionality Of SELinuxModeInverter, Use Any Root File Explorer Such MiXplorer -->

Root

-->

data

--> DreamerMods --> MultiFunctions --> SELinuxModeInverter --> Copy The File Of Disable To

The Folder Of Inactive

--> Reboot

- Some Issues Which Are Related To Magisk/Rom/Kernel Itself Can Be Solved By Using A Different Modes [Where The Wait Mode (The Default One) Can Be Used For Resolving The Issue Of Bootloop/Bootscreen/Blackscreen Which Changes The SELinux Mode Within 5 Min. After Rebooting & The Fast Mode Can Be Used For Changing The SELinux Mode]

- For Activating The Fast Mode, Use Any Root File Explorer Such MiXplorer -->

Root

-->

data

--> DreamerMods --> MultiFunctions --> SELinuxModeInverter --> Copy The File Of Disable To

The Folder Of Wait

--> Reboot

- For Activating The Wait Mode, Use Any Root File Explorer Such MiXplorer -->

Root

-->

data

--> DreamerMods --> MultiFunctions --> SELinuxModeInverter --> Delete The File Of Disable From

The Folder Of Wait

--> Reboot

- For More Details, Check This Post https://xdaforums.com/apps/magisk/selinux-mode-inverter-t3775271/post76381334
[Magisk] Kocane:
I'm on Magisk V19 and OxygenOS Pie - I install this and I boot straight into "Safe Mode" although the phone never gets past "Phone is starting" What gives? Not using core mode btw
[Magisk] YiPing_Huang:
Because every submodule is on BY DEFAULT.

I really do think the logic should be reversed.
[Magisk] mrastroboy:
Where is the download linnk
[Magisk] Dreamer(3MF):
Some Users Don't Read Carefully The General Steps Which Increases The Possibility Of Facing The Issue Of Bootloop/Bootscreen/Blackscreen (

The Safety Is The 1st Priority

) So We Need To Activate The Function Of SELinuxModeInverter & Use Fast Mode If Applicable After Reading The General Steps.

Some Magisk Users Uninstall Magisk Manager So The Module Of MultiFunctions Offers The Ability To Control Any Function From The Folder Of MultiFunctions (

/data/DreamerMods/MultiFunctions

).

==============================================​

After The Installation [Flashing/Re-Flashing] & 1st Reboot, Some Functions [DalvikCache Cleaner, MagiskHideList Cleaner, SafeMode Enabler & MagiskCoreOnlyMode Enabler] Are Activated To Resolve Some Problems & Disabling Themselves After Doing Their Functionalities. And For More Details, Check The Thread Of MultiFunctions https://xdaforums.com/apps/magisk/module-multifunctions-bootloop-t3933386.

==============================================​

It Is Now A Part Of The Main Module Of MultiFunctions & Its Thread https://xdaforums.com/apps/magisk/module-multifunctions-bootloop-t3933386.

==============================================​

Updated MultiFunctions4Magisk To 1.0.3.4.1.2!

Changelog: Adding More Functions [Swap Controller & Swappiness Changer]

- For The Module Which Is Ended Its Name With v1300, It Supports Magisk v13.1(1310) To v13.6(1360)

- For The Module Which Is Ended Its Name With v1400, It Supports Magisk v14.0(1400) To v15.3(1531)

- For The Module Which Is Ended Its Name With v1500, It Supports Magisk v15.0(1500) To v17.3(17300)

- For The Module Which Is Ended Its Name With v17000, It Supports Magisk v17.0(17000) To v17.3(17300)

- For The Module Which Is Ended Its Name With v18000, It Supports Magisk v18.0(18000) To v18.1(18100)

- For The Module Which Is Ended Its Name With v19000, It Supports Magisk v19.0(19000) To The Latest Version

- For The Module Which Is Ended Its Name With Unity, It Supports Any-Rooting-Tool Such As SuperSU, Lineage-AddOnSU & Magisk
[Magisk] edmund321:
where is the download link of the selinux mode inverter. i don't know if it is only me but i have opened up so many pages and links but couldn't find the download button. sorry, not so techie.
[Magisk] Ps24u:
You can grab it here

https://androidfilehost.com/?fid=1395089523397891352
[Magisk] edmund321:
thanks Ps24u. yur d man!
[LeEco Le Max 2 Questions & Answers] ausmomo:
I've been through every Setting option, and it's simply not there. Am I going mad?

Where the heck is it?

Brand new Max2. Android 6.0.1.

Found it.. it's under "Finger Print and Password"....
[HTC 10 Guides, News, & Discussion] wapem:
I use LeeDroid Nougat rom on my HTC 10 and the latency was killing me in MOBA games , jumping all around from 30 to 600 ping , then i started searching for some apps to fix that , and stumbled across a few , but only one actually does its thing , called sEFix , check for it on playstore , i been testing different moba games for about 3 hours now and the ping is rock solid ! Heroes Evolved has 30 ms constantly , Arena of Valor has 50 - 70 ms constantly , if LeeDroid sees this by any chance , would be nice for you to do some research on that app and implement whatever that sorcery code is and implement it in the ROM itself.
[Samsung Galaxy S8+ Questions & Answers] Adam40090:
Hey guys

I'm new here and was wondering if anyone could help me! I have just downloaded and followed the instructions to install and use Substratum & Andromeda for my S8 plus.

I followed all of the steps up to getting myself a theme. Once the theme was installed my screen went black. I wasn't too bothered at first but now my phone is unusable! The only thing I am able to access is the camera by double tapping the lock button. The phone still vibrates if I get a call etc but I can't unlock it.

I get a message that pops up over and over again saying 'System UI has stopped' And the only option is to 'Close app'

I'm not gonna lie guys, I'm an absolute noob when it comes to this stuff. Is my phone gone forever or can I fix this?!

Cheers!:):)
[Samsung Galaxy S8+ Questions & Answers] ch@k75:
Perhaps some help?

Need some more information to help identify what you have installed last, or more specifically the offending overlay perhaps that does not agree with the "SYS UI"??? Next will be to ask if you understand or have any knowledge working with "ADB" as this will be needed to remove the offending "APP" installed you installed? Having asked this and having been in your shoes, I will tell you that if you have not ever given permission on a connected computer for "ADB" to have access to this phone you have put yourself in a place that a FACTORY RESET is going to be your best solution. I have found other ways to get into my phone using Bixby, as it can uninstall APPS but you would need to again know specifically the name of the offending APP.

My final thought/suggestion would be to spare yourself any further headache and just commit to the FRESET and then Google/Learn your way into an understanding with ADB - it can save you a ton of time while you learn about moding your phone:good:
[Samsung Galaxy S9+ Guides, News, & Discussion] bboii86:
For the G965U1 unlocked model S9+ stock Oreo G965U1UEU1ARBG Odin files.

Model: SM-G965U1

Model Name: Galaxy S9+

Country: USA

Version: Android Oreo 8.0

Security Patch Level: February 1st, 2018

Product Code: XAA

PDA: G965U1UEU1ARBG

CSC: G965U1OYN1ARBG

Download here: G965U1UEU1ARBG
[Samsung Galaxy S9+ Guides, News, & Discussion] DLD23:
Thanks
[Samsung Galaxy S9+ Guides, News, & Discussion] randallwaydemartin:
I did this trying to go from a Verizon to Unlocked. Also, tried going to T-Mobile. I left off User Data on the unlocked variant, but nothing changed even though it showed successful. Any help?!

I am having to drive to a friend's to do this on a Windows computer because I can't figure it out on my Mac. $10 if anyone can simplify how to do it on a Mac. I'm use to using ADB, not Odin.
[Samsung Galaxy S9+ Guides, News, & Discussion] SantinoInc:
Can this be flashed on the ATT version?
[Samsung Galaxy S9+ Guides, News, & Discussion] monsterlag:
Why didn't you flash Userdata? Thats what contains the carrier bloat. Flash the U1 userdata and see if that works.
[Samsung Galaxy S9+ Guides, News, & Discussion] randallwaydemartin:
Tried that too
[Samsung Galaxy S9+ Guides, News, & Discussion] kevindevonwilliams:
What exactly are you trying to achieve? You have a Verizon brand Samsung?
[Samsung Galaxy S9+ Guides, News, & Discussion] Rootuser3.0:
Those of us on the Verizon network with the old unlimited data plan can't tether without paying an extra $30 a month. If we can successfully load the unlocked firmware on the Verizon variant we can bypass the tether subscription.....
[Samsung Galaxy S9+ Guides, News, & Discussion] yeltrah123:
does anyone know when will the U1 bootloader will be updated to V2?
[Samsung Galaxy S9+ Guides, News, & Discussion] Nickdroid86:
Will this unlock any g965u?
[Samsung Galaxy S9+ Guides, News, & Discussion] todd3835:
No

This will not unlock the bootloader if that's your question.
[Samsung Galaxy S9+ Guides, News, & Discussion] Nickdroid86:
I meant sim/network unlock. Sorry.
[Samsung Galaxy S9+ Guides, News, & Discussion] bboii86:
The U1 firmware doesn't unlock your device.
[Samsung Galaxy S9+ Guides, News, & Discussion] Nickdroid86:
It was already unlocked but the dude that did it was kinda sloppy. It seemed to have quite a lot of compatibility issues. Original carrier info was listed under the settings. All seems great now.
[Samsung Galaxy S9+ Guides, News, & Discussion] Nickdroid86:
Stupid question. So I did the firmware flash, originally had the 965u. So now when we are finally able to root(if ever) do I have to look for roms(or any other hacks) for the 965u or the 965u1 since that's what I flashed? Also I received the June update the other day. Hopefully that doesn't screw anything up for me.
[Android Head-Units] E46_F:
Hi, I’m wondering if anyone can help me I want to upgrade my android head unit firmware from 6.0.1 to the latest version available.

About Device

Processor Type: QuadCore-T3

Android Version: 6.0.1

MCU Version: T5.3.19-94-10-E03101-170818

System Version: V8.2.3_20170818. 160847_HC1-N6502

Thanks
[ZTE Axon 7 Mini Questions & Answers] SyTexs:
Just unlocked my bootloader using Tuliptool. When tried booting to bootloader to flash TWRP to recovery. It just restarted my phone. I also tried getting to the bootloader by using the ADB command ADB boot bootloader and it also just restarted my phone.

Do you guys have any idea on how to fix this?

Any assistance in this matter is greatly appreciated.

Edit: Figured it out. I had tried to flash TWRP using Tuliptool without having the TWRP img in the correct folder. At least that's what I think caused the problem.

I fixed it by reattempting to flash TWRP using Tuliptool this time with it in the correct spot.

Not sure, if I can delete thread or not... I'm a complete newb here ヽ(ヅ)ノ