Database Info

twrp & Root & Mod for Ulefone Mix

Support page for ulefone Mix User-
we Need Some files to Root Ulefone Mix.
1. SP flash tools- https://spflashtool.com/
2. twrp Recovery- https://romprovider.com/2017/11/ulefone-support-twrp/
3. SuperSU- https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
other Support File-
Official Firmware- mod edit - link removed
no-verity-opt-encrypt-5.1.zip - https://androidfilehost.com/?fid=673368273298927206
Instructions-
First of all Flash twrp using SP flash tool
Don't Switch on phone flash no-verity-opt-encrypt-5.1.zip
then flash SuperSu.zip
Reboot System Now.

Is the 1st step not disabling oem lock in developer settings?

HypoTurtle said:
Is the 1st step not disabling oem lock in developer settings?
Click to expand...
Click to collapse
you can unlock with fastboot-
For new devices (2015 and later):
Code:
fastboot flashing unlock
For older devices (2014 and earlier):
Code:
fastboot oem unlock

XN Logos said:
you can unlock with fastboot-
For new devices (2015 and later):
For older devices (2014 and earlier):
Click to expand...
Click to collapse
For some reason no need to oem unlock (bootloader not locked properly??) so have twrp without needing to wipe data, but now remains the encryption problem as this trwp doesn't support it, I have compiled twrp for mtk in the past with encryption support but doubt I can recall what needed to be done

TWRP not working
When I install the TWRP recovery and start the phone with this mode to install the two files
1) no-verity-opt-encrypt-5.1
2) SuperSU-v2.82-201705271822
the phone does not see them and it is impossible to proceed further.
Furthermore, the operating system does not even start, so the original firmware must be replaced with the flash tool.
Has anyone found a solution to this inconvenience?
Thank you

mingariedd said:
When I install the TWRP recovery and start the phone with this mode to install the two files
1) no-verity-opt-encrypt-5.1
2) SuperSU-v2.82-201705271822
the phone does not see them and it is impossible to proceed further.
Furthermore, the operating system does not even start, so the original firmware must be replaced with the flash tool.
Has anyone found a solution to this inconvenience?
Thank you
Click to expand...
Click to collapse
1. Userdata is encrypted, and the TWRP here isn't compiled to be able to decrypt it. So you'll need an sdcard with those zips on it
2. The os won't start if it deems its been altered - that's partly what zip 1 is for.

Is there any custom roms for Ulefone Mix?

Qaaqqu said:
Is there any custom roms for Ulefone Mix?
Click to expand...
Click to collapse
No custom ROMs - I think there is a clone device [Panasonic Eluga C] so we have another stock ROM from them.
I haven't attempted porting anything yet, let alone building anything from source [a source built twrp should be trivial] - i've lost yet another hard-drive recently so light on diskspace & sdcards so not able to do much atm.
For completeness: stock ROM > http://ulefone.com/download/mix.html [newer than the one on needrom]
OTA > http://hwfotadown.mayitek.com/ota/r...NE_N_V0.6.9.1_S1712221514261911507/update.zip

Is this root method working?
Stock rom is located here Stock Ulefone Mix 4G Rom

when (android 8) Oreo for ulefone mix?

twrp and now?
Hello,
i have an old ulefone mix mt6750t with the screen damaged but still 90% working, i thought i would use it on android auto but i needed rooting.
So I informed myself a bit, go unlocked developer mode and usb, downloaded adb and twrp and magisk etc ...
I unlocked the bootloader from the settings then used adb and installed twrp which starts but asks me for the pass to decrypt, then I swipe and delete the encrypted data.
Then with adb sideload I install magisk 20 and check opt encript, but the phone always goes to twrp, it does not restart ... mmm and the orange mode message comes out but it should be normal ... someone knows how to go on to restart it normally and not with twrp?
Thank you

Is there a root for the ulefone Armor 9?

I have been looking for some sort of root for the ulefone armor 9, and I can't seem to find anything apart from sketchy websites. Can anyone help?

I found the scatterfile, but i still need to find the authentication file, and a download agent? I don't recall ever having to do any of this to root a phone before. Where do I get these files for a ulefone armor 9?

Look inside here:
Systemless Rooting with MagiskSU - Download APK
MagiskSU is an all-in-one Android rooting solution that is developed by topjohnwu. With Magisk Manager, users can easily root Android smartphones in a fastest and effective way. You can download MagiskSU, Magisk Root, Magisk Manager latest versions here.
magisksu.com

jwoegerbauer said:
Look inside here:
Systemless Rooting with MagiskSU - Download APK
MagiskSU is an all-in-one Android rooting solution that is developed by topjohnwu. With Magisk Manager, users can easily root Android smartphones in a fastest and effective way. You can download MagiskSU, Magisk Root, Magisk Manager latest versions here.
magisksu.com
Click to expand...
Click to collapse
there isn't a twrp for this phone.

M8E1 said:
there isn't a twrp for this phone.
Click to expand...
Click to collapse
TWRP isn't needed at all. Look inside here:
[Guide][Root] Magisk without TWRP on Android P
Via Magisk Manager: This method does not need root, and also does not require a custom recovery. However, you MUST have a stock boot image dump beforehand, and you also have to be able to flash the patched boot image, either through fastboot mode...
forum.xda-developers.com

jwoegerbauer said:
TWRP isn't needed at all. Look inside here:
[Guide][Root] Magisk without TWRP on Android P
Via Magisk Manager: This method does not need root, and also does not require a custom recovery. However, you MUST have a stock boot image dump beforehand, and you also have to be able to flash the patched boot image, either through fastboot mode...
forum.xda-developers.com
Click to expand...
Click to collapse
I did this, and I got a "red state" boot loop

M8E1 said:
I did this, and I got a "red state" boot loop
Click to expand...
Click to collapse
Am I missing something? The phone is apparently locked in fastboot mode, and will not accept downloads.

M8E1 said:
I did this, and I got a "red state" boot loop
Click to expand...
Click to collapse
Then report this issue in the related XDA-thread.

jwoegerbauer said:
Then report this issue in the related XDA-thread.
Click to expand...
Click to collapse
What thread would that be? This is for support and questions, isn't it?

M8E1 said:
What thread would that be? This is for support and questions, isn't it?
Click to expand...
Click to collapse
Of course this one:
[Guide][Root] Magisk without TWRP on Android P
Via Magisk Manager: This method does not need root, and also does not require a custom recovery. However, you MUST have a stock boot image dump beforehand, and you also have to be able to flash the patched boot image, either through fastboot mode...
forum.xda-developers.com

Is there anyone who can help? Fastboot does not respond to commands, and patching the boot.img and vbmeta.img via sp flash tool only puts my phone in a "red state". I have tried so many methods for rooting this phone, i'm starting to become convinced that it doesn't exist.

M8E1 said:
Is there anyone who can help? Fastboot does not respond to commands, and patching the boot.img and vbmeta.img via sp flash tool only puts my phone in a "red state". I have tried so many methods for rooting this phone, i'm starting to become convinced that it doesn't exist.
Click to expand...
Click to collapse
i rooted this phone on the first day i got,, i now trying to get proper working twrp so,, search on the google this,, ulefone armor 9 root hovatek and follow the guide there, thats how i did it.

kanadali said:
i rooted this phone on the first day i got,, i now trying to get proper working twrp so,, search on the google this,, ulefone armor 9 root hovatek and follow the guide there, thats how i did it.
Click to expand...
Click to collapse
Hello,
I tried to root my Armor 9E using Magisk but I ended with a bootloop. after a moment of stress (I'm a noob) I was able to put the original boot.img thanks to Fastboot,
I found your thread on Hovatek, how do you patch vbmeta.img ? in my case it's a Armor 9E
About TWRP, do you have any update ? will it be compatible with 9E also ?
Thanks
EDIT : I had to flash the vbmeta.img , I took it from hovatek here https://forum.hovatek.com/thread-36629.html

Totem95d said:
Hello,
I tried to root my Armor 9E using Magisk but I ended with a bootloop. after a moment of stress (I'm a noob) I was able to put the original boot.img thanks to Fastboot,
I found your thread on Hovatek, how do you patch vbmeta.img ? in my case it's a Armor 9E
About TWRP, do you have any update ? will it be compatible with 9E also ?
Thanks
EDIT : I had to flash the vbmeta.img , I took it from hovatek here https://forum.hovatek.com/thread-36629.html
Click to expand...
Click to collapse
Ok guys, don't stress out. I've been dealing with Ulefone for awhile now. I have about 20 of their phones and I have the Armor 9. I just rooted the Armor x7. To start with, Ulefone has the stock system files for download right there on their website for every model they sell.
You are going to need the SP flash tool. I think they even include it in their mega download page.
3086 Armor 9 - Google Drive
drive.google.com
Now these are Mediatek so they do things differently. You turn the phone off and start the flash on SP Flash tool and plug it in. You use the All-in-one authorization for it that's included. Find the special empty vbmeta file on hovatek and use it in place of the other one. Remove the checksum.ini file.
But before all this when you got the boot off of there put it on your sdcard and install Majisk manager. Tell it to install magisk and to patch your boot. Pick the boot file. Then adb pull that file onto your computer and name it boot.img
put all of them back together in place of the old ones with all the stuff you downloaded from the ulefone link and run the checksum generator that it comes with which will produce a checksum.ini file. And if you have that empty vbmeta also you can use SP flash to flash it to your phone and it'll take it. You'll be left with a yellow or orange state then relock your bootloader and you'll be back to normal with magisk installed and root. So...you know, Friggin Mediatek
The reason for your bootloop was because you didn't put the empty vbmeta file in the mix.

MurdochPizgatti said:
Ok guys, don't stress out. I've been dealing with Ulefone for awhile now. I have about 20 of their phones and I have the Armor 9. I just rooted the Armor x7. To start with, Ulefone has the stock system files for download right there on their website for every model they sell.
You are going to need the SP flash tool. I think they even include it in their mega download page.
3086 Armor 9 - Google Drive
drive.google.com
Now these are Mediatek so they do things differently. You turn the phone off and start the flash on SP Flash tool and plug it in. You use the All-in-one authorization for it that's included. Find the special empty vbmeta file on hovatek and use it in place of the other one. Remove the checksum.ini file.
But before all this when you got the boot off of there put it on your sdcard and install Majisk manager. Tell it to install magisk and to patch your boot. Pick the boot file. Then adb pull that file onto your computer and name it boot.img
put all of them back together in place of the old ones with all the stuff you downloaded from the ulefone link and run the checksum generator that it comes with which will produce a checksum.ini file. And if you have that empty vbmeta also you can use SP flash to flash it to your phone and it'll take it. You'll be left with a yellow or orange state then relock your bootloader and you'll be back to normal with magisk installed and root. So...you know, Friggin Mediatek
The reason for your bootloop was because you didn't put the empty vbmeta file in the mix.
Click to expand...
Click to collapse
Trying this method works fine for me until I try to relock the bootloader. Once I do that, I end up with a red state again.
Any advice? I am relocking the bootloader via fastboot flashing lock - is that correct?

MurdochPizgatti said:
Ok guys, don't stress out. I've been dealing with Ulefone for awhile now. I have about 20 of their phones and I have the Armor 9. I just rooted the Armor x7. To start with, Ulefone has the stock system files for download right there on their website for every model they sell.
You are going to need the SP flash tool. I think they even include it in their mega download page.
3086 Armor 9 - Google Drive
drive.google.com
Now these are Mediatek so they do things differently. You turn the phone off and start the flash on SP Flash tool and plug it in. You use the All-in-one authorization for it that's included. Find the special empty vbmeta file on hovatek and use it in place of the other one. Remove the checksum.ini file.
But before all this when you got the boot off of there put it on your sdcard and install Majisk manager. Tell it to install magisk and to patch your boot. Pick the boot file. Then adb pull that file onto your computer and name it boot.img
put all of them back together in place of the old ones with all the stuff you downloaded from the ulefone link and run the checksum generator that it comes with which will produce a checksum.ini file. And if you have that empty vbmeta also you can use SP flash to flash it to your phone and it'll take it. You'll be left with a yellow or orange state then relock your bootloader and you'll be back to normal with magisk installed and root. So...you know, Friggin Mediatek
The reason for your bootloop was because you didn't put the empty vbmeta file in the mix.
Click to expand...
Click to collapse
Hi!
I'm having the same issue as MulBe039.
Device: UleFone Armor 9E (Android 10)
My steps so far:
0.0 Get boot.img, scatter file, checksum generator (from ulefone), magisk.apk (from github), vbmeta.img, drivers, SP Tool (from Hovatek)
0.1 Install magisk on my phone and patch boot.img.
0.2 Enable developer options on my phone
0.3 Enable OEM unlocking and USB debugging on my phone.
0.4 Install drivers on my PC
0.5 Copy scatterfile, boot.img, vbmeta.img into checksum generator's folder and get checksum.ini.
1.0 Connect phone
> adb devices
> adb reboot bootloader
> fastboot devices
> fastboot oem unlock
> fastboot reboot
Phone boots in orange state.
2.0 Re-enable dev opts, (phone shows as already unlocked), USB debugging and turn off the phone.
2.1 Start SP Flashtool
2.2 Select scatter file
2.3 Check only vbmeta.img
2.4 Start download
2.5 Connect phone
2.6 Download completes successfully.
2.7
> fastboot devices
> fastboot reboot
Orange state.
2.8 Factory reset from phone
3. Repeat 2., except at 2.3 check only the patched boot.img
Still orange state.
Magisk app is installed.
4.0 Turn the phone on, enable dev opts and USB debugging, connect to PC
> adb devices
> adb reboot bootloader
> fastboot devices
> fastboot oem lock
> fastboot reboot
Red state - boot loop.
5.0 Hold power button until it turns off abruptly
5.1 Hold volume up until load some sort of boot selector menu.
5.2 Select fastboot mode with vol up button.
5.3 Vol down to boot selected mode
5.4
> fastboot devices
> fastboot oem unlock
> fastboot reboot
Orange state - everything else is working.
What am I missing / doing wrong? How do I re-lock the bootloader?
Thanks in advance!

I have been able to root my Ulefone armor 9 using the method described here https://github.com/bkerler/mtkclient
1 - download boot partition from your device using mtkclient
2 - patch it with magisk manager
3 - flash it again with mtkclient
4 - flash an empty vbmeta (not really sure if this is necessary)
5 - boot your device
I'm not really sure if it is needed to have the bootloader unlocked, but I had it

0xf331dead said:
I have been able to root my Ulefone armor 9 using the method described here https://github.com/bkerler/mtkclient
1 - download boot partition from your device using mtkclient
2 - patch it with magisk manager
3 - flash it again with mtkclient
4 - flash an empty vbmeta (not really sure if this is necessary)
5 - boot your device
I'm not really sure if it is needed to have the bootloader unlocked, but I had it
Click to expand...
Click to collapse
And remember that you cannot lock your bootloader after modifying stuff because signatures will not match and so on

I had to press volume up + volume down while connecting the usb to get mtkclient working

How To Guide Pad 11 (TB-J606F) Unlock! Magisk! RoooooT !!!

Lenovo Tab P11 (2021г.) - Обсуждение - 4PDA
Lenovo Tab P11 (2021г.) - Обсуждение, Планшет, 11"
4pda.to
Translator from Russian: https://www.deepl.com/translator

Basically
1. Enable OEM Unlock in Developers Settings
2. (Your host PC should have LMSA installed) Open command window, and go to where ADB is
3. Turn your tablet off. Press and hold volume down and power buttons to enter bootloader
4. Enter the following in command window
Code:
fastboot flashing unlock
. Answer yes to unlock bootloader
warning: your tablet is wiped during the process!!![/B]
5. Reboot

To root, patch boot with Magisk
You can use LMSA to download matching ROM, and use rescue to update ROM if necessary. You can get needed boot at c:/program data/LMSA/download/romfiles/
Copy boot.img to your phone and use Magisk to patch, and copy patched_boot.img back to host computer.
Turn your tablet off and enter bootloader
Switch to fastbootd
Code:
fastboot reboot fastboot
Flash the patched boot
Code:
fastboot flash boot
Press spacebar once and drag and drop the patched boot onto command window, and press enter
Reboot

does this work with Lenovo Pad Pro 2021 (SD870) ?

Thanks for the guide, I've successfully unlocked the bootloader and rooted with Magisk.
I also installed the unofficial TWRP from here: https://unofficialtwrp.com/twrp-3-4-2-root-lenovo-tb-j606f/
However I didn't flash the provided vbmeta.img and everything still seems to be working fine, including booting into TWRP.
Anyone know if not flashing it may cause issues to appear?
The reason I didn't flash it is because someone else on another thread here said they got stuck in a boot loop after flashing it and that after restoring they decided not to flash it and everything worked fine, which seems to be my experience too, but maybe there are implications I'm not aware of with not flashing it.

I had this issue too, I had to run the command:
Code:
fastboot flashing unlock

aurelienlux said:
Thanks for the guide, I've successfully unlocked the bootloader and rooted with Magisk.
I also installed the unofficial TWRP from here: https://unofficialtwrp.com/twrp-3-4-2-root-lenovo-tb-j606f/
However I didn't flash the provided vbmeta.img and everything still seems to be working fine, including booting into TWRP.
Anyone know if not flashing it may cause issues to appear?
The reason I didn't flash it is because someone else on another thread here said they got stuck in a boot loop after flashing it and that after restoring they decided not to flash it and everything worked fine, which seems to be my experience too, but maybe there are implications I'm not aware of with not flashing it.
Click to expand...
Click to collapse
I flashed vbmeta.img and now I can't boot into system/fastboot/recovery. Do you know how to restore ? I also tried LMSA, device cannot be detected.

cyatsl said:
I flashed vbmeta.img and now I can't boot into system/fastboot/recovery. Do you know how to restore ? I also tried LMSA, device cannot be detected.
Click to expand...
Click to collapse
DO IT ON YOUR OWEN RISK! I HAVE NOT TESTED ON A LENOVO TAB P11 YET!
These are the steps for rooting a Lenovo Tab M8 FHD!
I think essential are the points 19 to 21, to flash the boot.img ONCE AGAIN after vbmeta.img.
It discribes ... this part is key, otherwise you'll bootloop!
Fully charge tablet
Turn tablet on
Skip as much of the initial setup process as possible, however you MUST be connected to the WiFi in order to allow unlocking of your bootloader (Start -> More/Accept -> no wifi/Set-Up Offline -> skip setting current time set -> Choose reporting options / Hit Accept -> Skip Pin -> Skip Lenovo ID -> Lenovo User Experience Program (choose if you want to skip or not) -> Choose navigation etc) Get to the home screen
Swipe down from top of screen and open Settings
Developer Tools (enable dev tools if you don't yet have access) -> Enable USB Debugging
Developer Tools -> Enable OEM Unlocking (again, if you're not on WiFi, it may not allow you to do this)
Connect tablet usb and usb to computer (Click "allow" when the usb debugging popup comes up)
./adb devices (Make sure the computer can see the tablet)
./adb reboot bootloader
./fastboot devices (Make sure the computer can see the tablet)
./fastboot flashing unlock then press volume-up on the device
./fastboot reboot`
On the Lenovo loading splash screen, you should now get the Orange State alert that the device is unlocked. It may take a bit to reboot as you've just wiped all data again and it must do initial setup
Device boots up normally. Now you can do real setup steps if you like, or you can ignore everything like in Step 3 above.
Enable USB Debugging again (Step 4-5)
Grab the boot.img and vbmeta.img from the LMSA TB_8505FS_S300025_201015_BMP update. Copy the boot.img to the tablet, taking note of the location (e.g., ./adb push boot.img /sdcard/)
Install latest version of Magisk Manager (doesn't need to be the Canary version, can be the regular version) and patch the boot image.
Clicked on "Install" on the righthand top in magisk manager
Clicked on "Next" Righthand top.
Selected "Select and Patch a File".
picked the boot.img file I had copied in step 1. Take note of the location of the patched image (magisk_patched.img), and copy it to your PC.
Reboot into bootloader again (./adb reboot bootloader)
Flashed the magisk patched boot.img ./fastboot flash boot path/to/magisk_patched.img
Flash the VB meta with the disable-verification flag ./fastboot --disable-verification flash vbmeta path/to/vbmeta.img
Flashed the magisk patched boot.img AGAIN!!!!!! (this part is key, otherwise you'll bootloop) ./fastboot flash boot path/to/magisk_patched.img
Reboot, you should now be rooted (can confirm in Magisk Manager) ./fastboot reboot

Is it ok/safe to flash this to TB-J606L?
It is the same model but with sim card and 4G.
Sometimes WiFi vs 4G models have the same software and detect differences on startup and sometimes not... Not sure about this model. I would prefer to not (soft)brick it.

Hi there. First time boot-unlocker needing help. I also have the P11 TB-J606F and would like to root it. I believe I need to do this first. I cannot seem to get any response from the tablet when doing this. In "regular tablet" mode I can connect and do ADB-commands, but in this "bootloader" mode I cannot seem to connect. I just get "Waiting for any device"
Could it be a driver issue? In device manager there is an Android device with an exclamation mark? I have no clue how to update this? Automatic doesn't work and I can't seem to find any drivers that work. I am not sure if this indeed is the problem, but you know - help needed, please.

skodkassen said:
Hi there. First time boot-unlocker needing help. I also have the P11 TB-J606F and would like to root it. I believe I need to do this first. I cannot seem to get any response from the tablet when doing this. In "regular tablet" mode I can connect and do ADB-commands, but in this "bootloader" mode I cannot seem to connect. I just get "Waiting for any device"
Could it be a driver issue? In device manager there is an Android device with an exclamation mark? I have no clue how to update this? Automatic doesn't work and I can't seem to find any drivers that work. I am not sure if this indeed is the problem, but you know - help needed, please.
Click to expand...
Click to collapse
Not sure if it helps. I had a similar issue with my Lenovo Tab M8 FHD.
The big issue was to get the android driver for win10, fastboot was not working. I found it under win10 update >> optional updates >>driver updates >> there was a medi.... as installable update. Afterthem fastboot was working fine.

sc00ter98 said:
Not sure if it helps. I had a similar issue with my Lenovo Tab M8 FHD.
The big issue was to get the android driver for win10, fastboot was not working. I found it under win10 update >> optional updates >>driver updates >> there was a medi.... as installable update. Afterthem fastboot was working fine.
Click to expand...
Click to collapse
And thus my problems were solved. It took me a few hours going nowhere and thanks to you everything is now cool

sc00ter98 said:
Not sure if it helps. I had a similar issue with my Lenovo Tab M8 FHD.
The big issue was to get the android driver for win10, fastboot was not working. I found it under win10 update >> optional updates >>driver updates >> there was a medi.... as installable update. Afterthem fastboot was working fine.
Click to expand...
Click to collapse
Solution
Download and install LMSA and use Motorola ADB driver Device Manager
You should see P11 with no driver. Update driver > Let me choose > Android ADB > choose Motorola ADB driver

aurelienlux said:
Thanks for the guide, I've successfully unlocked the bootloader and rooted with Magisk.
I also installed the unofficial TWRP from here: https://unofficialtwrp.com/twrp-3-4-2-root-lenovo-tb-j606f/
However I didn't flash the provided vbmeta.img and everything still seems to be working fine, including booting into TWRP.
Anyone know if not flashing it may cause issues to appear?
The reason I didn't flash it is because someone else on another thread here said they got stuck in a boot loop after flashing it and that after restoring they decided not to flash it and everything worked fine, which seems to be my experience too, but maybe there are implications I'm not aware of with not flashing it.
Click to expand...
Click to collapse
Be aware: The link above is not the right TWRP for the P11 Pro. I lost two days an bricked my tablet to find out that. The TWRP for P11 Pro is at https://unofficialtwrp.com/twrp-3-4-2-root-lenovo-tb-j706f/

37_ said:
does this work with Lenovo Pad Pro 2021 (SD870) ?
Click to expand...
Click to collapse
Did you try it ? I think this method can work on Pad Pro 2021 SD870

mingkee said:
Basically
1. Enable OEM Unlock in Developers Settings
2. (Your host PC should have LMSA installed) Open command window, and go to where ADB is
3. Turn your tablet off. Press and hold volume down and power buttons to enter bootloader
4. Enter the following in command window
Code:
fastboot flashing unlock
. Answer yes to unlock bootloader
warning: your tablet is wiped during the process!!![/B]
5. Reboot
Click to expand...
Click to collapse
does work with me . it repeat the same error:
C:ladb>adb reboot bootloader
error: device '(null)' not found

Two questions:
1. Did anyone lose their Widevine level when unlocking, installing Magisk and/or rooting? I currently have L1 and would hate to lose that (to L3).
2. Is it possible to use the TWRP version for the TB-J706F for the TB-J716F as well? Basically, they are very similar devices, but the screen (90 Hz OLED) and processor (Snapdragon 870 instead of Snapdragon 730G) are different, but I don't know what is relevant for TWRP. Otherwise, could I also root without TWRP?
Thanks in advance!

HANN1860BAL said:
Two questions:
1. Did anyone lose their Widevine level when unlocking, installing Magisk and/or rooting? I currently have L1 and would hate to lose that (to L3).
2. Is it possible to use the TWRP version for the TB-J706F for the TB-J716F as well? Basically, they are very similar devices, but the screen (90 Hz OLED) and processor (Snapdragon 870 instead of Snapdragon 730G) are different, but I don't know what is relevant for TWRP. Otherwise, could I also root without TWRP?
Thanks in advance!
Click to expand...
Click to collapse
1. Yes you will lose L1 when unlock bootloader
2. No , TWRP with very different hardware so don't hope so much .
I see there is no reason to root TB-J716F now, current firmware is stable and smooth

luizkun said:
1. Yes you will lose L1 when unlock bootloader
2. No , TWRP with very different hardware so don't hope so much .
I see there is no reason to root TB-J716F now, current firmware is stable and smooth
Click to expand...
Click to collapse
Thanks for the fast reply!
Is it possible to lock bootloader after rooting again and gaining L1 back with keeping device rooted?
That's true, but I want to use some rooted apps, like Titanium Backup and AdAway ;-)

HANN1860BAL said:
Thanks for the fast reply!
Is it possible to lock bootloader after rooting again and gaining L1 back with keeping device rooted?
That's true, but I want to use some rooted apps, like Titanium Backup and AdAway ;-)
Click to expand...
Click to collapse
you can root after unlock bootloade by patching boot.img from stock rom (by magisk ) and install magisk without TWRP

How To Guide [ALL IN ONE] How to Unlock/Lock Bootloader & Root/Unroot Nord 2T

Hello everyone hope you are all keeping well.
Here is a little guide on how to Unlock/Lock the Bootloader and Root/Unroot our Nord2T.
I cannot be responsible if you brick your device. Your phone, your choices, your responsibility!​
Unlock The Bootloader;​
If you haven't done it already...beware that this will erase all of your user data. To do so, you must:
Enable developer options
Enable the "OEM unlocking" option
Enable USB debugging
Have both adb and fastboot, from SDK Platform Tools available on your PC
Connect your phone to your PC using the USB cable and run the following commands:
Code:
adb devices
(just to make sure that your phone is, in fact, recognized by your PC and that you're able to run adb commands)
Code:
adb reboot bootloader
(so your phone will reboot into fastboot mode)
Code:
fastboot flashing unlock
(device should now unlock)
Code:
fastboot reboot
(device reboots with an unlocked bootloader and data partition wiped so set up the device from scratch again)
Rooting Guide;​
Unlocking the Bootloader is necessary before continuing
1 - Download Nord2T stock boot.img that you may find later on this post, that matches your current build.
Copy the boot.img to your devices internal memory
Leave a copy of it on your PC (on the same folder you have adb and fastboot...you never know if you will need to use it again in the future...to restore the stock boot.img, aka revert to stock...)
Spoiler: Global Build boot.img's
Stock boot CPH2399_11_A.07 (did not extract it and can't find the firmware file to be able to download and extract, if someone could please upload a link to it on this thread I would sincerely appreciate it)
Stock Boot CPH2399_11_A.09
Stock Boot CPH2399_11_A.11
Stock Boot CPH2399_11_A.14
Stock Boot CPH2399_11_A.15
Stock Boot CPH2399_11_A.16
Stock Boot CPH2399_11_A.17
Stock Boot CPH2399_11_A.19
Stock Boot CPH2399_11_C.24
Stock Boot CPH2399_11_C.26
Stock Boot CPH2399_11_C.27
Spoiler: IND Build boot.img's
Stock Boot CPH2401_11_A.11
Stock Boot CPH2401_11_A.13
Stock Boot CPH2401_11_A.14
Stock Boot CPH2401_11_A.15
Stock Boot CPH2401_11_A.16
Stock Boot CPH2401_11_A.17
Stock Boot CPH2401_11_A.18
Stock Boot CPH2401_11_A.19 (I didn't capture the download for this, if anyone has it please send me a link to the official OTA)
Stock Boot CPH2401_11_C.23
Stock Boot CPH2401_11_C.24
Stock Boot CPH2401_11_C.26
Stock Boot CPH2401_11_C.27
2 - Download latest Magisk Manager from HERE and install it on your phone
3 - Open Magisk Manager App and press:
Install
Select and Patch a File
Browse to the path where you saved stock boot.img and select it
Magisk Manager will now patch the boot image and store it in [Internal Storage]/Download/magisk_patched.img
4 - Copy the patched boot image from your device to your PC (Store it on the same folder where you have adb and fastboot)
5 - Flash the patched boot image to your phone by running these commands (remember, you must have patched boot image on the same folder you have adb and fastboot and, of course, your device must be connected to your PC...)
Code:
adb reboot bootloader
​
Code:
fastboot flash boot magisk_patched.img
​
Code:
fastboot reboot
​6 - After the phone boots up, hopefully with a normal boot (almost feels like nothing happened....), install/open Magisk Manager App again and watch Magisk doing it's magic!
7 - Enjoy!
All credits goes to topjohnwu and his incredible work with Magisk.
System Updates;​
For system updates. Just apply the OTA update as normal.
Once updated you will have no root and you must follow steps above again with the new boot.img that corresponds to the firmware version you are on.
Unroot;​
To unroot simply flash the stock boot.img.
Relock Bootloader;​
If you have TWRP installed flash the stock boot.img (same as your firmware version from earlier in this post)
This is so as you can access fastboot properly.
1 - To relock Bootloader first download Oxygen Updater app from the Playstore.
2 - Download the firmware which corresponds to the firmware which you have currently installed.
3 - Move/copy this firmware.zip to your PC and extract it. (inside you will see a folder and a couple files. The only file we need is payload.bin)
4 - Download/install Fastboot Enhance on your PC
5 - Reboot phone to bootloader mode so it gets detected by Fastboot Enhance, from there boot to fatsbootd.
6 - Flash payload.bin in Fastboot Enhance
7 - Wipe data in fastbootd from your Nord 2T, reboot and finish phone setup.
8 - Enable developer options, enable USB debugging from developer options.
9 - Reboot to bootloader and run the command;
Code:
fastboot flashing lock
The device will be now successfully locked.
Hope this helps out

Thank you so much

Thanks so much. Going to try this weekend with my daughter phone.

Thanks a lot!
There is a new update available for Nord 2T:
CPH2399_11_A.11
Do you have the stock boot.img for this version by any chance?

jolaviska said:
Thanks a lot!
There is a new update available for Nord 2T:
CPH2399_11_A.11
Do you have the stock boot.img for this version by any chance?
Click to expand...
Click to collapse
No I still haven't received the ota. Did you get updated to this version already?

I received the update but refusing to apply it

jolaviska said:
I received the update but refusing to apply it
Click to expand...
Click to collapse
It will show up again.
Don't worry.

Rooted my Nord 2T successfully. Thanks once again

Download Nord2T stock boot.img
Click to expand...
Click to collapse
I was wondering... How can I extract the boot.img by myself without relying upon anyone? With the oxygen updater app I've the full firmware (~4 GB), would that be useful to extract the boot.img?

luke! said:
I was wondering... How can I extract the boot.img by myself without relying upon anyone? With the oxygen updater app I've the full firmware (~4 GB), would that be useful to extract the boot.img?
Click to expand...
Click to collapse
By using THIS software. I will always update this thread with the latest boot.img files in the future but this is the software I used

Thank you.
And what is the procedure to OTA update, once we have magisk_patched_boot.img installed.
OTA won't install, so need to revert somehow install new update and root again?

garylawwd this device is prone to bricking if you patch the inactive slot after an OTA within the Magisk app as I experienced first hand. I have never had such issues with my Redmi K40 Gaming despite their similarity with the MediaTek processor. After an OTA I would simply patch the inactive slot, reboot and enjoy permanent root.. topjohnwu made rooting simple for us...

Stock Global boot CPH2399_11_A.11 added to OP. Sorry for the delay, only received the update today

nielsync said:
garylawwd this device is prone to bricking if you patch the inactive slot after an OTA within the Magisk app as I experienced first hand. I have never had such issues with my Redmi K40 Gaming despite their similarity with the MediaTek processor. After an OTA I would simply patch the inactive slot, reboot and enjoy permanent root.. topjohnwu made rooting simple for us...
Click to expand...
Click to collapse
Ya I didnt do it this way at all because my device updated while i was asleep and i was unrooted, so I had to patch the new boot using the method in the OP.
I would definitely advise restoring the stock boot.img before proceeding with an update, then install the update normally and just patch the new image with magisk and then flash.
For a while the 'install to inactive slot' option only works on certain devices, the Nord 2T obviously is'nt one of those devices.
I'm sure the magisk documentation recommends restoring stock images before an update.

Thanks for the Stock Boot CPH2399_11_A.11, could you please also link the related img patched?
On my first Nord I have always updated with the patched boot img on it without problem, but I was on old Oxigen OS 11, not the 12 Oxigen (color) os...

cioce said:
Thanks for the Stock Boot CPH2399_11_A.11, could you please also link the related img patched?
On my first Nord I have always updated with the patched boot img on it without problem, but I was on old Oxigen OS 11, not the 12 Oxigen (color) os...
Click to expand...
Click to collapse
I didn't want to share any of the magisk images because there is a new version of magisk every other week and people may like to be on the beta branch or canary branch of magisk or whatever.
It's very easy to patch the image though. Just download magisk.apk and use it to patch the boot.img's I've provided above. Then move the patched.img to your pc and flash.
But anyways here is the magisk patched.img for CPH2399_11_A.11 using magisk 25.2 stable

Stock Boot for Indian variant CPH2401_11_A.13 added to OP

can u post the latest update boot.img for indian unit CPH2401_11_A.14

Stock boot for Indian CPH2401_11_A.14 added to OP

Stock boot for Global CPH2399_11_A.14 added to OP

[GUIDE] Gigaset GS5 (rephone) root with Magisk + unlock bootloader

hello I'm not sure if this is the right place to post this in but I'll be putting together a small guide on how to root the Gigaset GS5​the phone I own is called "rephone" it's apparently a sustainable version of the Gigaset GS5 with a removable battery recycled plastic etc etc. But specs wise it is the same as the Gigaset GS5
anyways I did this yesterday so it's possible that I forgot some steps, if you encounter issues feel free to leave a comment and I'll try to assist you
prerequisites:​- make sure you actually have this device
- make sure you are on Android 12 (ota update)
- make sure you back up your data
- make sure you read this guide carefully
UNLOCKING BOOTLOADER WILL WIPE ALL YOUR DATA!!! MAKE SURE TO BACK EVERYTHING UP​Proceed with caution, I am not responsible for anything that may happen to your phone, you are doing it at your own risk
Easy method (flashing pre-made boot.img) :​I would not recommend this method because I extracted the kernel from my rephone and I don't know if the firmware/kernel for that is 1:1 with the GS5, ideally you want to extract the boot.img of your own device but that takes way more time so only proceed with this if you're at a pinch or are too lazy to extract your own boot.img
Also please download CPU-Z on your device and check your Build ID under the System tab, if it matches with mine then feel to proceed with this method, if not then do not proceed and instead extract your own boot.img and patch that
Build ID for my rephone is: 2000_000170_00_12.0_V06_20221025
Set up adb&fastboot on your computer (google 15 second adb installer)
Grab the patched boot.img from my GitHub and copy it to C:/adb or wherever you installed adb&fastboot: https://github.com/astolfoaddict/GigasetGS5-Magisk
Unlock developer options in your phone and enable OEM Unlocking
Power off your device and hold volume up+power until you boot into bootloader
Select and boot into Fastboot Mode, connect device to your computer
At this point you're in fastboot, open CMD in C:/adb
Your bootloader is probably locked, to check run this command: fastboot getvar unlocked if the result is no, your bootloader is locked
To unlock your bootloader run this command and follow the instructions on your device: fastboot flashing unlock (THIS WILL WIPE YOUR DATA)
Once you unlock your bootloader, wipe your vbmeta partition. Follow Method 3 in this guide: https://www.hovatek.com/forum/thread-32719.html
Now flash the boot.img: fastboot flash boot boot.img
Reboot, set up the device, install Magisk Manager and enjoy!
Advanced method (extracting and patching your own boot.img) :​In this method we'll be extracting the boot partition from your device so you can patch it with Magisk and flash
Proceed with caution!
Install Mediatek VCOM drivers, follow this guide: https://www.hovatek.com/forum/thread-440.html
Dump your boot_a partition with MTK Client by running python mtk r boot_a boot.img follow this guide: https://www.hovatek.com/forum/thread-40865.html
Install Magisk Manager and patch your boot.img
Unlock bootloader, flash empty vbmeta and boot by following the method above
Important:
- Make sure you run python mtk r boot_a boot.img in MTK Client
- If you don't see Mediatek VCOM drivers in Device Manager after using the auto installer, try installing the drivers manually (check guide)
- Also booting into BROM mode is tricky, what usually works for me is:
Power off device and connect to PC
As it starts up and shows you the battery charge, wait until the screen goes out
At this point you should run the python command in MTK Client
Hold volume down+power and check the terminal
If you want to extract the entire firmware follow this guide: https://www.hovatek.com/forum/thread-21970.html
Be aware that your chipset will not be listed in WwR MTK so what you do is open Template.ini with Notepad++ and add MT6768 under the CPU section, don't worry about the chipset not matching what this phone has (MT6769), adding MT6769 to CPU and exporting scatter file will not let you import it in SP flash tool
Special thanks to axonasif and supremegamers for the guide I pulled most of the stuff out of: https://github.com/supremegamers/mt6769​Also thanks to hovatek for their helpful resources regarding MTK flashing/drivers/etc. <3​

Hy
Ubuntu Touch with Waydroid works fine with Gigaset GS5......only Unlock Bootloader and flash with UB Port Installer..........
and you can flash Sailfish Port per Fastboot .............

yeah you can install GSIs too like lineage os and other stuff

astolfoaddict said:
yeah you can install GSIs too like lineage os and other stuff
Click to expand...
Click to collapse
Hy
have you some flashable files from lineage os...........??????? im searching found nothing............would be great
Thanks

astolfoaddict said:
yeah you can install GSIs too like lineage os and other stuff
Click to expand...
Click to collapse
its only a fake to install GSI image!!!!!! Dont work!!!!!!

hugolight said:
its only a fake to install GSI image!!!!!! Dont work!!!!!!
Click to expand...
Click to collapse
what do you mean?

astolfoaddict said:
what do you mean?
Click to expand...
Click to collapse
i have found no one GSI img file to flash my gigaset gs5!!!!!!

hugolight said:
i have found no one GSI img file to flash my gigaset gs5!!!!!!
Click to expand...
Click to collapse
[GSI][12] LineageOS 19.x GSI (A64B/64B)
Background: This is a natural continuation/extension of the LineageOS 18.x GSIs I've been making since 2020. LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and...
forum.xda-developers.com
try this one, boots and works just fine on my device.

astolfoaddict said:
[GSI][12] LineageOS 19.x GSI (A64B/64B)
Background: This is a natural continuation/extension of the LineageOS 18.x GSIs I've been making since 2020. LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and...
forum.xda-developers.com
try this one, boots and works just fine on my device.
Click to expand...
Click to collapse
Hello dont work
fastboot flash system lineage.img
Invalid sparse file format at header magic
Sending sparse 'system' 1/16 (131060 KB) OKAY [ 4.278s]
Writing 'system' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed

astolfoaddict said:
[GSI][12] LineageOS 19.x GSI (A64B/64B)
Background: This is a natural continuation/extension of the LineageOS 18.x GSIs I've been making since 2020. LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and...
forum.xda-developers.com
try this one, boots and works just fine on my device.
Click to expand...
Click to collapse
hy can you post the direct link for correct image (gigaset gs5)........thanks

astolfoaddict said:
hello I'm not sure if this is the right place to post this in but I'll be putting together a small guide on how to root the Gigaset GS5​the phone I own is called "rephone" it's apparently a sustainable version of the Gigaset GS5 with a removable battery recycled plastic etc etc. But specs wise it is the same as the Gigaset GS5
anyways I did this yesterday so it's possible that I forgot some steps, if you encounter issues feel free to leave a comment and I'll try to assist you
prerequisites:​- make sure you actually have this device
- make sure you are on Android 12 (ota update)
- make sure you back up your data
- make sure you read this guide carefully
UNLOCKING BOOTLOADER WILL WIPE ALL YOUR DATA!!! MAKE SURE TO BACK EVERYTHING UP​Proceed with caution, I am not responsible for anything that may happen to your phone, you are doing it at your own risk
Easy method (flashing pre-made boot.img) :​I would not recommend this method because I extracted the kernel from my rephone and I don't know if the firmware/kernel for that is 1:1 with the GS5, ideally you want to extract the boot.img of your own device but that takes way more time so only proceed with this if you're at a pinch or are too lazy to extract your own boot.img
Also please download CPU-Z on your device and check your Build ID under the System tab, if it matches with mine then feel to proceed with this method, if not then do not proceed and instead extract your own boot.img and patch that
Build ID for my rephone is: 2000_000170_00_12.0_V06_20221025
Set up adb&fastboot on your computer (google 15 second adb installer)
Grab the patched boot.img from my GitHub and copy it to C:/adb or wherever you installed adb&fastboot: https://github.com/astolfoaddict/GigasetGS5-Magisk
Unlock developer options in your phone and enable OEM Unlocking
Power off your device and hold volume up+power until you boot into bootloader
Select and boot into Fastboot Mode, connect device to your computer
At this point you're in fastboot, open CMD in C:/adb
Your bootloader is probably locked, to check run this command: fastboot getvar unlocked if the result is no, your bootloader is locked
To unlock your bootloader run this command and follow the instructions on your device: fastboot flashing unlock (THIS WILL WIPE YOUR DATA)
Once you unlock your bootloader, wipe your vbmeta partition. Follow Method 3 in this guide: https://www.hovatek.com/forum/thread-32719.html
Now flash the boot.img: fastboot flash boot boot.img
Reboot, set up the device, install Magisk Manager and enjoy!
Advanced method (extracting and patching your own boot.img) :​In this method we'll be extracting the boot partition from your device so you can patch it with Magisk and flash
Proceed with caution!
Install Mediatek VCOM drivers, follow this guide: https://www.hovatek.com/forum/thread-440.html
Dump your boot_a partition with MTK Client by running python mtk r boot_a boot.img follow this guide: https://www.hovatek.com/forum/thread-40865.html
Install Magisk Manager and patch your boot.img
Unlock bootloader, flash empty vbmeta and boot by following the method above
Important:
- Make sure you run python mtk r boot_a boot.img in MTK Client
- If you don't see Mediatek VCOM drivers in Device Manager after using the auto installer, try installing the drivers manually (check guide)
- Also booting into BROM mode is tricky, what usually works for me is:
Power off device and connect to PC
As it starts up and shows you the battery charge, wait until the screen goes out
At this point you should run the python command in MTK Client
Hold volume down+power and check the terminal
If you want to extract the entire firmware follow this guide: https://www.hovatek.com/forum/thread-21970.html
Be aware that your chipset will not be listed in WwR MTK so what you do is open Template.ini with Notepad++ and add MT6768 under the CPU section, don't worry about the chipset not matching what this phone has (MT6769), adding MT6769 to CPU and exporting scatter file will not let you import it in SP flash tool
Special thanks to axonasif and supremegamers for the guide I pulled most of the stuff out of: https://github.com/supremegamers/mt6769​Also thanks to hovatek for their helpful resources regarding MTK flashing/drivers/etc. <3​
Click to expand...
Click to collapse
I’d put the devicees in fastboot mode and run:
fastboot getvar product
Gigaset k69v1_64
Rephone k69v1_64_k419
GS5 and Rephone not the same!!!!!!

astolfoaddict said:
[GSI][12] LineageOS 19.x GSI (A64B/64B)
Background: This is a natural continuation/extension of the LineageOS 18.x GSIs I've been making since 2020. LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and...
forum.xda-developers.com
try this one, boots and works just fine on my device.
Click to expand...
Click to collapse
Hy
Mobile Data work with this image?

Hy,
my bootloader is unloock.......cant flash any image......
FAILED (remote: 'Not enough space to resize partition')
what can i do????

Hi
i have the same rephone with Build like yours astolfoaddict : 2000_000170_00_12.0_V06_20221025
and did the easy UNLOCKING method.
then i flashed "fastboot flash system lineage-19.1-20230418-UNOFFICIAL-a64_bvS.img"
an now my phone hangs in a bootloop.
did i missed something like the recovery.img cause i dont have that or what i have done wrong ?

Hi everybody,
is this a working method for installing lineage 19 on a rephone? w2273 and hugolight do you had success?
In other words, should i try or not ;-)
thanks.....