Hi,
Does anyone have any idea or suggestion, on how to unlock the bootloader for the Chuwi HiPad Pro?
Or anyone that has unlock for another similar device, could please share how you were able to do it? maybe can help.
Thank you for your attention.
Which hipad pro? Mtk or Qualcomm?
I have MTK .
Contact Chuwi at [email protected] requesting the key to unlock your bootloader.
They will reply with your 16 bit encryption key and then proceed to unlock bootloader as usual via abd fastboot commands.
There are several different commands to try.
I was successful with
fastboot flashing critical unlock
Then entered the encryption key
Fastboot will then ask the tablet in fastboot mode if you would like to unlock the bootloader. Vol - to selected Y/N and Vol + to enter selection.
Try this at least worked on my CHUWI SurPad, Android 10 CPU: MT6771 (MediaTek) and should work on most MediaTek (mt2601, mt6261, mt6572,... check https://github.com/bkerler/mtkclient/tree/main/mtkclient/payloads )
This will work only on MediaTek and you can achieve this:
- Unlock bootloader (it allows you to modify boot partition) without factory wipe (this would happen using fastboot method)
- Modify boot partition via Magick app
1) Unlock bootloader + backup flash partitions
Get familiar with mtkclient (https://github.com/bkerler/mtkclient)
It is tool that can read/write content of flash. Compile it on your linux or windows. FYI Im describing steps in GUI mode but if you have only working ./mtk binary you can do the same but need to read documentation.
Shutdown your tablet, disconenct USB cable from PC to tablet.
Run ./mtk_gui tool and follow its instruction in console you need to get into BROM mode (it is not fastboot mode nor recovery mode, it is special mode that works only MediaTek chips and usually cannot be used. Anyway this program mtkclient using some exploit to get there due to some bugs). It also means most likely that even bricked devices could be "restored" if someone tried modify recovery partition and bricked by replacing it with original one due to dm_verity protection [you can ask me I dumped my device])
Power off the phone before connecting.
For brom mode, press and hold vol up, vol dwn, or all hw buttons and connect usb.
For preloader mode, don't press any hw button and connect usb.
If it is already connected and on, hold power for 10 seconds to reset.
at this stage you should be in this MTK GUI connected and navigate to read tab and save all yourflash partitions. or at least boot.bin, vbmeta.bin, recovery.bin - you can restore them later if any failure.
Also navigate last tab and click unlock bootloader (this wont erase your data at all)
reboot your device (either with ./mtk reset) or holding 10 sec power button and boot back to android 10. In boot screen you will see some warning that device has bootloader unlocked and 5 sec delay before boot.
2) Modify extracted boot.bin with latest Magisk
Download apk here https://themagisk.com/magisk-app/ and install to your andriod (you can use adb push from laptop via connecetd usb cable [need enabled developer mode), or simply copy to sd card and install from there) also copy boot.bin you dumped from previous step 1)
Run Magisk click to install in Magisk section (and select your boot.img file on sdcard or anywhere where you stored it inside your tabled device) and click "Let's go" - this will do some magic inside boot image which enables Magisk to be your root provider for the apps (something like sudo or su). So patched image is stored my location was /storage/emulated/0/Download/magisk_patched-25205.img
Copy this file back to your laptop somewhere
Shutdown your tablet again and unplug usb cable
3) Disable dm_verity + rewrite boot partition using mtk
Boot your laptop to BROM mode again as described in step 1)
to install patched boot.img (now magisk_patched-25205.img) you can use that mtk_gui and same for overwriting vbmeta partition
for disabling dm_verity you need use vbmeta_empty.bin (it is inside mtkclient directory)
No you can reboot your device and should boot.
Run magisk again and you should see now that choices "Superuser" and "modules" are available.
DONE..
you can also patch recovery.bin with your favority TWRP or another (i havent done this)
you can get root access by installing any sshd client and accesing to it, or simply in adb shell type su and magisk will ask you to grant it
MTK UNIVERSAL V5 can unlock.
HELLO I HAVE THE SAME PROBLEM BUT IS QUALCOMM .ITS EXIST SAME PROG FOR QUALCOMM ?
artaos said:
HELLO I HAVE THE SAME PROBLEM BUT IS QUALCOMM .ITS EXIST SAME PROG FOR QUALCOMM ?
Click to expand...
Click to collapse
[Tool] Ultimate Read write flash mtk, Spd, Qualcomm unlock, Lock network, sim, Frp
******************Miracle Box ******************* This Is only for Personal use, I am Not a Developer of This Box, this is Developed By a miracle Team Hit Thanks:good: For This Crack- Features- Features for MTk[all Devices]- Read info...
forum.xda-developers.com
Related
Warning: this device
(Build: LW_X325_APR_2017_V2748_01_FINAL
Build fingerprint: 'alps/Z22/Z22:4.4.2/KOT49H/1492164051:user/test-keys')
contains the com.adups.fota and com.data.acquisition malware. Use at your own risk!
Credit: All credit goes to:
yuweng for Easy Magic TWRP Installer for all MediaTek Devices
out386 for [MTK] Rooting a device (kind of) manually
koush for Universal ADB drivers
Chainfire for adbd Insecure
bovirus and rua1 for MTK Droid Root & Tools
Hovatek for [Tutorial] How to manually install MT65xx (MediaTek) USB VCOM drivers on Windows
Alternate download links:
https://mega.nz/#!UAl2HYoR!jUgMi_YkrrQ3CBhjMSCRcZat1QGEhbnOiJ6XjQV8yEw
OR
http://www.mediafire.com/file/a2eqra3fpzxpy88/recovery.img
Pre-setup:
You will need:
Universal ADB drivers
MTK Droid Root & Tools
SP Flash Tool
MediaTek PreLoader USB VCOM: I used this method from Hovatek which works on Windows 7 x64 but I can't vouch for other OS/architectures
Setup Instructions:
1. Install the Universal ADB drivers.
2. With your phone turned on, connect your phone via USB. USB debugging must be enabled and the phone must be connected as Camera (PTP) for any tools to access it.
3. Use MTK Droid Root & Tools to generate a scatter file.
4. Disconnect the USB cable. Turn your phone off and remove the battery. Reconnect the USB cable, keeping the phone turned off.
5. Open SP Flash Tool. Optional but highly recommended: use the Readback tab to backup your current ROM. Root is NOT required for readback backup. Load the scatter file generated in step 3. The download agent should be MTK_AllInOne_DA.bin by default, select it if it isn't.
6. Browse and select the recovery.img if it isn't already. Make sure that ONLY the checkbox to the left of RECOVERY is checked! The dropdown menu should be set to "Download Only", select it if it isn't. Click Download and wait for a green check mark to appear. Now it's safe to disconnect the USB, put the battery back in, start the phone, and reconnect the USB.
7. The fastest way to get to recovery is to boot normally, then open adb and type and enter adb reboot recovery to reboot directly into recovery. Holding volume up + power from the off state works too. Volume down + power enters factory test mode which isn't very interesting.
Notes:
The bootloader is unlocked. It appears that there's no easy way for a non-root user to tell that though, fastboot oem commands will silently hang indefinitely, fastboot getvar all only returns partition names and sizes, stock recovery doesn't show lock status...
All images must be flashed. fastboot boot will silently hang on 'booting...' indefinitely.
fastboot flash can be used to flash boot.img but not recovery.img, some sort of permissions issue
End:
Let me know if I forgot something.
This post appears to be intended to refer to SMT TELECOMM HK LIMITED X325 devices that use Life Wireless (mobile virtual operator) branding (There is also a Social Mobile Telecommunications branded version of X325).
The title refers to the device as "BPX325", but BPX325 is the model code of the battery, not the device.
Thanks for the recovery. It would also be good to state what version of TWRP the recovery is based on.
Ascii3 said:
This post appears to be intended to refer to SMT TELECOMM HK LIMITED X325 devices that use Life Wireless (mobile virtual operator) branding (There is also a Social Mobile Telecommunications branded version of X325).
The title refers to the device as "BPX325", but BPX325 is the model code of the battery, not the device.
Thanks for the recovery. It would also be good to state what version of TWRP the recovery is based on.
Click to expand...
Click to collapse
Oops, fixed. This uses TWRP 2.8.2.0. I only know for sure that it works on my device, maybe this will help determine compatibility?
[ro.mediatek.chip_ver]: [S01]
[ro.mediatek.platform]: [MT6572]
[ro.mediatek.version.branch]: [KK1.MP7]
[ro.mediatek.version.release]: [ALPS.KK1.MP7.V1]
I'm not sure. I'm no Android developer, I learned all this the hard (trial and error) way after finding adups.fota in the system partition and not trusting rooting apps to do the job for me.
Hi everyone,
First post here. I purchased a Cubot Kingkong. I liked the toughness and the price. Has Android Nougat, 2gb of Ram, 16gb ROM, MT 6580 quad core processor.
What I don't like is that it's slow, in my opinion. I tried to find a custom ROM, but couldn't find one.
Do you a custom ROM that can work? Thought about Android go, but it would need to be updated to Oreo first.
Thanks for your help.
Slow? I have this phone and I find it very reasonably snappy for its specs. The MT6580 is a 2016 entry-level processor. Not any great performer and no firmware will do miracles.
Besides, its Nougat Android is 100% bloat-free (a good surprise I must say). And the 2 Gb of RAM are enough to run it correctly. Don't think Android One would make much of a change here.
Your expectations might be too high for a sub-100€ phone.
does anyone have a scatter file or custom recovery for this phone? how did you root?
CUBOT KING KONG B-1 (X511) Android 7.0 quick TWRP + rooting guide
WARNING: You do a factory reset! all data lost! unlocking - warranty lost!
edit: With locked bootloader, you can not flash from fastboot. BUT - Yippee! - SP Flash Tool is able to flash twrp.img for encrypted device with locked bootloader (and FRP / OEM lock!) without data loss. TWRP is then able to decrypt data with default_password. Before you unlock bootloader, flash TWRP, Back up your /data from TWRP and manually copy Internal Storage (/data/media/0) via USB-MTP (not included in TWRP Backup). Backup is not described in this Tutorial, but feel free to ask
- first you need adb and fastboot, in Windows represented as adb.exe and fastboot.exe which run in command line terminal (cmd.exe) - (for adb and fastboot Windows XP click here)
- install MediaTek MT65xx USB VCOM Preloader USB Drivers for Windows
- this phone is locked. to unlock the bootloader, enable usb-debugging:
Settings -> About Phone -> tap Build number seven (7) times
Settings -> Developer options -> OEM unlocking -> Turn on
Settings -> Developer options -> USB debugging -> Ok
WARNING: You do a factory reset! all data lost!
- connect the phone to pc and type in command console:
- confirm with Yes (Volume UP)
Code:
adb reboot bootloader
fastboot oem unlock
Phone is now in Orange State - warranty lost!
(if you wanna get rid of the waiting time flash the 'Orange State disabler' see below)
- reboot the phone:
Code:
fastboot reboot
i have created a scatter file using this very cool program WwR MTK v2.30 from Ilya Aleksandrovich
then i have ported this TWRP v3.2.2-0 from S. M. Nahid Emon Generic TWRP v3.3.1-0 from Samad Segmane meanwhile
- on Phone, download SR3-SuperSU-v2.79-SR3-20170114223742.zip flashable zip
- on PC, download the scatter file and the twrp-3-3-1-0-recovery from this thread
flash recovery with MediaTek SP Flash Tool
- in SP Flash Tool, go to Download and select the following files:
Download-Agent: MTK_AllInOne_DA.bin
Scatter-loading File: MT6580_cubot_king_kong_7081c_scatter.txt
Flash Mode: Download Only
- uncheck all checkboxes
- double click on recovery.img and select twrp.img
- press Download
- type in command console:
Code:
adb reboot bootloader
(flashing starts as soon as phone is connected in download mode)
- after successfully flashing, press and hold Volume UP, disconnect the phone, connect again, wait until you see the Orange State message appears, then release the Volume UP Button
- you can start TWRP each time from command console:
Code:
adb reboot recovery
edit: Fixed! unfortunately, when flashed and booted from recovery, touch screen is not working unless someone will fix the kernel (Patryk did with IDA Pro but this tutorial drives me crazy) - at moment you can only boot as boot.img
- boot into TWRP recovery from fastboot without flashing recovery (working touch screen)
Code:
adb reboot bootloader
fastboot boot "C:\Download\twrp.img"
<-- see here
- from TWRP you can now install SuperSU.zip flashable zip
- if you want install Busybox binary, download Busybox-1.29.0-YDS-UNIVERSAL.zip from github and install this flashable zip from TWRP
- if you don't like SuperSU better use Magisk i have tested successfully too, it is easy to install, no TWRP required. MediaTek SP Flash Tool has a readback mode where you can make a backup of boot.img and copy to phone (or use the one attached). Then, all you have to do is install the Magisk Manager apk and patch the boot image, then flash the patched_boot.img and you are rooted
- this phone is encrypted by default - disable encryption may increase performance
WARNING: You do a factory reset! all data lost!
first install adb and fastboot, connect the phone and unlock the bootloader,
then follow instructions for disable encryption (do everything in TWRP):
- on Phone, download Disable Force Encrypt zip and SuperSU zip files
- boot into TWRP recovery from fastboot without flashing recovery (see above)
- copy Disable Force Encrypt zip to cache partition
Advanced -> File Manager
navigate to /data/media/0/Download
select file Disable_Dm-Verity_ForceEncrypt_v1.4.zip
press Copy File
navigate to /cache
confirm blue check mark on the right bottom
Swipe to Confirm
- repeat this copy SR3-SuperSU-v2.79-SR3-20170114223742.zip to /cache
go back to main menu
- Wipe -> Format Data -> type yes
if Format Data fails, reboot TWRP and try again:
go back to main menu
- Reboot -> Bootloader
- boot into TWRP recovery from fastboot without flashing recovery (see above)
- Wipe -> Format Data -> type yes
go back to main menu
- flash Disable Force Encrypt zip and SuperSU zip files
Install -> (Up A Level) -> /cache
select file Disable_Dm-Verity_ForceEncrypt_v1.4.zip
uncheck all checkboxes
Swipe to confirm Flash
go back
select file SR3-SuperSU-v2.79-SR3-20170114223742.zip
uncheck all checkboxes
Swipe to confirm Flash
Reboot System
- finish the initial android setup assistant
- enable usb-debugging (see above unlock bootloader)
- boot into TWRP recovery from fastboot without flashing recovery (see above)
- clear cache partition
Wipe -> Advanced Wipe -> Cache -> Swipe to Wipe
instead of SuperSU you can flash Magisk after Disable Force Encrypt. The SuperSU v2.79 is the latest release from Chainfire and it is Pro-Version. Do not update to V2.82 from Coding Code (it is the same version)
- new: 'Orange State' disabler
if you wanna get rid of the waiting time flash the 'Orange State disabler'
WARNING: experts only! do not try this if you don't know how to unbrick your device
- make a backup of lk.bin (bootloader)
- install orange_state_disabler_v0.3.zip from TWRP
- flash lk.bin from SP Flash Tool (in case you bricked your device)
--- 'Orange State' disabler v0.3 ---
##### Created by XopmoH97 : ) #####
source: orange_state_disabler_v0.3.zip
aIecxs said:
Patryk did with IDA Pro but this tutorial drives me crazy
Click to expand...
Click to collapse
Please post here:
Result of:
Code:
echo 0 > /proc/sys/kernel/kptr_restrict
cat /proc/kallsyms | grep tpd_i2c_probe
Dump of:
Code:
cat /proc/kallsyms
Code:
CUBOT_KING_KONG:/ # echo 0 > /proc/sys/kernel/kptr_restrict
CUBOT_KING_KONG:/ # cat /proc/sys/kernel/kptr_restrict
0
CUBOT_KING_KONG:/ # cat /proc/kallsyms | grep tpd_i2c_probe
c07d2970 t tpd_i2c_probe
CUBOT_KING_KONG:/ #
see attachment
https://drive.google.com/file/d/1YmOF9IRJhOEHLFHXgjBcBi74kvKrna0s
What is the kernel architecture? (you can check that in CPU-Z) nevermind
Try this:
twrp-3.2.2.0-cubot_king_kong_7081c-20180831-2340.img (updated)
If it'll not work then this:
twrp-3.2.2.0-cubot_king_kong_7081c-20180831-2356.img
i have tested, both not booting. i think we should just give up. maybe this method does not working for MT6580. i have requested kernel source code from Cubot but they denied
Lannig said:
Besides, its Nougat Android is 100% bloat-free (a good surprise I must say).
Click to expand...
Click to collapse
Cubot King Kong has data mining spy app in OTA updater
https://www.xda-developers.com/report-android-phones-transmit-data-to-adups-a-chinese-firm
dont expect any firmware updates (they wont provide Oreo for sure) - better disable OTA updater instead:
Code:
pm disable --user 0 com.adups.fota
pm disable --user 0 com.adups.fota.sysoper
edit: do not update to V24 battery drain increases dramatically. Just stay at V16
Whats the touch driver here?
1. *#*#3646633#*#*
2. Other extra
3. Device info <-- result
LosTigeros said:
Whats the touch driver here?
1. *#*#3646633#*#*
2. Other extra
3. Device info <-- result
Click to expand...
Click to collapse
the code in dialer did not work, but i could enter Service Mode with MTK Engineering Mode apk. unfortunately there is no device info in Others. is there another way to check, maybe dump some file?
Use an app from google play called Device Info HW
Hey,
thanks for your support and time! I have downloaded this app and this are the results. it shows Touchscreen gt1x (i2c 1-005d)
Will it boot up after just decompressing and compressing it again? Try: twrp-3.2.2.0-cubot_king_kong_7081c-20180902-2017.img (not patched).
Thanks a lot for providing a usable TWRP, even if only one you can boot from fastboot and not flash. It serves its purpose of installing SuperSU or Magisk, good enough for me.
I'm no Android kernel wizard but I fail to see how booting from a flashed partition or in-memory through fastboot makes a difference as far as the touch driver is concerned?
EDIT : wanted to provide the requested information but it's been done already.
In gt1x its because of this:
So get_boot_mode() returns a different value depending on how TWRP was started, from the recovery partition or in-memory from fastboot? and the touchscreen driver basically disables itself in the former case? I've learned something new today, thanks for enlightening us (and I'm impressed by your knowledge of this source code BTW).
EDIT: @aIecxs: unfortunately you're right. Dr. Web has spotted them as the infamous Downloader adware. Guess I'll have to take care of these once I have root.
And what about custom ROMs? Is it possible to build Lineage OS for this device?
I'm thinking of buying one, but if there won't be any OS updates it'll be much worse than I expected.
aIecxs said:
CUBOT KING KONG B-1 (X511) Android 7.0 quick TWRP + rooting guide
- boot into TWRP recovery from fastboot without flashing recovery (working touch screen)
Code:
adb reboot bootloader
fastboot boot "C:\Android\Backup\Cubot King Kong\twrp-3-2-2-0-recovery-for-MT6580_cubot_king_kong_7081c.img"
Click to expand...
Click to collapse
I unlocked the bootloader and tried booting the recovery using this method, but the TWRP logo shows up and the phone is stuck in a bootloop (TWRP logo shows up and disappears over and over again) .
I have tried flashing with SPFlash tool with no results. Every other recovery in this thread simply does not boot at all. What can I do to debug it? I have tried every possible method to root this phone with no success (neither TWRP nor "one click root" apps work). If anyone knows something, please help. I really want to root this phone in order to remove the malware that is preinstalled on it (adups fota). Note that I am not a developer and don't know much about these things beyond flashing custom ROMs. Thank you in advance
please do a read back for boot.img and recovery.img with SP Flash Tool
Actual Firmware https://onedrive.live.com/?authkey=!APMSxpd_UoEEQBY&id=A120532B51026BDA!1816&cid=A120532B51026BDA
Unlock Bootloader https://rootwrp.com/unlock-teclast-t20-bootloader/
and flash with
fatboot flash boot +file
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
This is for the new teclast t30 tablet? can you make a video?
Yes Brand New
https://www.youtube.com/watch?v=G4uuLCjBWrs&feature=youtu.be
Video is About Patch/flashing Bootimage with Magisk Manager(Tablet is already rooted)
hello
successfully root new T30 with patched boot.img (with magisk).
I have unlocked bootloader with "fastboot flashing unlock" but now, have a message on boot screen and have to wait 5s more for boot
is there any way to bypass this message and 5s pause ?
there is a TWRP 3.3.1 on 4pda by nemo-nemo and helpers, but touchscreen don't work for me
Unlocked Bootloader cause this warning on Boot(Power Button should override the 5 secs Pause)
Dont using the recovery i dont know
Here is TWRP 3.3.1 for T1P2 (T30):
https://drive.google.com/file/d/1RW5ek_FIAMe_8KvRWpNE_l7wi8qNxmUS/view?usp=sharing
Thx to nemo-nemo on 4pda.ru
Hello,
I can confirm TWRP work fine but you have to use a USB-OTG mouse
The 1st time you boot on TWRP, you have a encryption code request, choose "cancel"
To disable force encryption, flash "DisableForceEncryption_treble" zip with TWRP
When you unlock bootloader of this T30, you have warning message and 5s wait to boot
There is a tweak to bypass this:
download script "orange_state_disabler" zip and flash it with TWRP
this script is fully safe, there is a compatibility test and don't flash if it can't.
Thx to XopmoH97 from 4pda.ru
Download from here: https://drive.google.com/drive/folders/1tSInU_vOFZAfpdbc1bETAuIJsniQqjUd?usp=sharing
edit*
TechGuru123 said:
there is a newer firmware for this tablet
T30(T1P1)_Android 9.0_V1.04_E43D.rar
https://pan.baidu.com/s/1sjEt1jxEOz...arentPath=/sharelink491465238-972273915700760
password
1f9r
Click to expand...
Click to collapse
What's your source ?
Have you verify this firmware ?
T30 is T1P2, not T1P1.
Look at your ID on tablet's backside: T1P2
Go to Teclast website firmware and search for
T1P1: unknown
T1P2 -> T30
Verify and test before publish, please
edit*
My PC can't find any T30 fastboot devices... which drivers use ??
Search for "MTK_USB_All_v1.0.8" on google
Is there no way to root without unlocking the bootloader first?
kestrelv2 said:
Is there no way to root without unlocking the bootloader first?
Click to expand...
Click to collapse
Unlocking bootloader is useless for 90% of users
Why ?:
- Only for fastboot commands
- Unlocking bootloader avoid warranty
You can do lot of things without unlock:
- Install TWRP (with Upgradetool)
- Install custom system, logo, boot, etc ... with upgradetool
and
You can root without unlock:
- Download firmware (T1P2) from teclast website and unpack in PC folder, ex: "T30_firm".
- Download and install "MTK_USB_All_v1.0.8" for MTK drivers (search on google)
- Connect your T30 to PC with usb
- In "T30_firm/firmware" folder, copy "boot-verified.img" to you T30
- Install magisk manager on your T30 an launch it
- Choose install magisk by "patch a file", choose your "boot-verified.img" and wait
- Now, you have a "magisk-patched.img" file in download folder
- Copy "magisk-patched.img" on your "T30_firm" folder PC
- Launch "Upgrade tools.exe" in "T30_firm/upgrade tool" folder
- Unselect all "img" files
- Select only "boot" line and choose your "magisk-patched.img" (click on same line, "location" column)
- Shutdown your T30 (allways connected to pc)
- Clic on "download" in upgrade tool and wait for big popup with green "V"
You can disconnect you T30 and boot.
Open magisk manager, "tada !" magisk is ready
murigny64 said:
Unlocking bootloader is useless for 90% of users
Why ?:
- Only for fastboot commands
- Unlocking bootloader avoid warranty
You can do lot of things without unlock:
- Install TWRP (with Upgradetool)
- Install custom system, logo, boot, etc ... with upgradetool
and
You can root without unlock:
- Download firmware (T1P2) from teclast website and unpack in PC folder, ex: "T30_firm".
- Download and install "MTK_USB_All_v1.0.8" for MTK drivers (search on google)
- Connect your T30 to PC with usb
- In "T30_firm/firmware" folder, copy "boot-verified.img" to you T30
- Install magisk manager on your T30 an launch it
- Choose install magisk by "patch a file", choose your "boot-verified.img" and wait
- Now, you have a "magisk-patched.img" file in download folder
- Copy "magisk-patched.img" on your "T30_firm" folder PC
- Launch "Upgrade tools.exe" in "T30_firm/upgrade tool" folder
- Unselect all "img" files
- Select only "boot" line and choose your "magisk-patched.img" (click on same line, "location" column)
- Shutdown your T30 (allways connected to pc)
- Clic on "download" in upgrade tool and wait for big popup with green "V"
You can disconnect you T30 and boot.
Open magisk manager, "tada !" magisk is ready
Click to expand...
Click to collapse
Ill give it a try thanks.
It worked, thanks a bunch!!!
When I turn off the T30 and press download, nothing happens anymore. I tried it on both Windows 7 and Windows 10. Just nothing. I'm waiting 10 minutes, then I'll put a stop and i'm done. No change. Does the tablet really have to turn off? Otherwise it's very well described, I think I'm making a mistake somewhere, I just don't know where.
Zuzzana
Try press "download" first and then, power off
zuzzana said:
When I turn off the T30 and press download, nothing happens anymore. I tried it on both Windows 7 and Windows 10. Just nothing. I'm waiting 10 minutes, then I'll put a stop and i'm done. No change. Does the tablet really have to turn off? Otherwise it's very well described, I think I'm making a mistake somewhere, I just don't know where.
Zuzzana
Click to expand...
Click to collapse
For me these mtk tools only do anything when i plug into a certain usb port. I couldnt find one that worked on my desktop pc but on my laptop its the usb 2.0 slot that worked and not either of the usb 3 slots. Turn it off click download and then plug in the tablet and it should start assuming you have properly installed the needed drivers.
Thank you, thank you, thank you. It just wanted to press download first and then plug it into USB. Thanks again.
Zuzzana
WARNING !!
Don't flash chinese firmware mentioned above by @TechGuru123
This firmware erase all your partitions,your NVRAM and IMEI
You will lose IMEI and it's hard to recover !
ROOT (ALMOST) EVERY DEVICE WITH MAGISK + FASTBOOT
As an Android user, I understand how frustrating it will be when you desperately look for an exact rooting tutorial for your device but end up finding nothing, all one-click root tools do not work, or no custom recovery made for yours.
So, this tutorial shows you how to root a wide range of Android devices (not all, because there will be exceptions, I guess) with Magisk. First, we should take a look at the pros and cons, so that you can generally acknowledge this method.
---------------------------------------------------------------------------
PROS
- No custom recovery (TWRP, ClockworkMod,etc.) needed
- Easy to find prerequisites
- Successful root attempt CONFIRMED on my 10 devices (including popular devices, rare devices, and devices with OS based on Android)
- Support recent Android versions, including Android 10 (tested on Google Pixel XL).
CONS
- Phone brick might occur
- You might not find your device's firmware in .zip format, which will stop you from using this method.
- Not being able to unlock the bootloader (only on some device) will stop you from using this method, too.
That's about the pros and cons. I hope you guys all understand these points before going to read my tutorial and start your attempt.
---------------------------------------------------------------------------
REQUIREMENTS & STEPS
I. REQUIREMENTS
- Your device's Android version is 5.0 or up. If it's below 5.0, then you can root your device easily with any one-click tool.
- A computer & USB cable.
On your phone
- Download & install Magisk
- Download the exact firmware version (in .zip format) of your device and only extract the boot.img to any directory.
On your computer
- Download & install Fastboot, extract the folder to "Downloads" directory
- Download & install Android USB driver for Windows
(I am not sure if XDA allows inserting links in threads or not, so please search for these prerequisites on the internet, it is easy)
II. STEPS
1. Unlocking your phone's bootloader
- Open Settings > About phone > Tap on Build number about 7 times till you see a notification "You are now a developer"
- Now in the About phone tab, you can see the "Developer option". Tap on it and make sure:
+ the OEM unlocking is turned ON
+ The USB Debugging is turned On
- Plug your phone on your computer (with Fastboot & driver fully installed). Allow the USB Debugging notification on your phone
- Open Command Prompt on your computer. Enter commands below steps by steps:
cd Downloads
cd fastboot
adb reboot bootloader
(press Enter after each line to proceed)
- Your phone will reset to the bootloader menu after these commands. Next, enter this:
fastboot oem unlock
- A message asking you to make sure you want to unlock the bootloader. Use the volume and power button to choose "Yes". Your phone will reset data and reboot right after.
*Note: This method works on many Android devices, but doesn't on many devices. You might have to google a method for your own phone
2. Patching the boot.img file
After you extracted the boot.img from your device, use the Magisk app installed on your device to patch it up.
- Click the "Install" button on the first line
- Click "Select and Patch a file"
- Choose the boot.img file extracted. The patching progress will start right after.
- You will receive a file named "magisk_patched.img" after finished.
3. Flashing the "magisk_patched.img"
- Copy the "magisk_patched.img" into the Fastboot folder
- Reboot your phone to Bootloader mode by powering off and then hold Power + Volume down button simultaneously
- Open Command Prompt again, and type:
cd Downloads
cd fastboot
fastboot flash boot magisk_patched.img
- The flashing progress will begin. Wait until it finishes, and type the last command:
fastboot reboot
- Your phone will restart once again, and of course, with root access gained
---------------------------------------------------------------------------
UNROOT DEVICE
- If you want to unroot your device, you just have to flash the original boot.img file, with the same steps with flashing the magisk_patched.img!
---------------------------------------------------------------------------
This instruction is not truly detailed, so maybe you might encounter some difficulties at some point. If any, please feel free to leave your question below.
It is also the first time I create an instruction post, therefore I appreciate all of your comments. Thanks a lot <3
richarshub said:
ROOT (ALMOST) EVERY DEVICE WITH MAGISK + FASTBOOT
As an Android user, I understand how frustrating it will be when you desperately look for an exact rooting tutorial for your device but end up finding nothing, all one-click root tools do not work, or no custom recovery made for yours.
So, this tutorial shows you how to root a wide range of Android devices (not all, because there will be exceptions, I guess) with Magisk. First, we should take a look at the pros and cons, so that you can generally acknowledge this method.
---------------------------------------------------------------------------
PROS
- No custom recovery (TWRP, ClockworkMod,etc.) needed
- Easy to find prerequisites
- Successful root attempt CONFIRMED on my 10 devices (including popular devices, rare devices, and devices with OS based on Android)
- Support recent Android versions, including Android 10 (tested on Google Pixel XL).
CONS
- Phone brick might occur
- You might not find your device's firmware in .zip format, which will stop you from using this method.
- Not being able to unlock the bootloader (only on some device) will stop you from using this method, too.
That's about the pros and cons. I hope you guys all understand these points before going to read my tutorial and start your attempt.
---------------------------------------------------------------------------
REQUIREMENTS & STEPS
I. REQUIREMENTS
- Your device's Android version is 5.0 or up. If it's below 5.0, then you can root your device easily with any one-click tool.
- A computer & USB cable.
On your phone
- Download & install Magisk
- Download the exact firmware version (in .zip format) of your device and only extract the boot.img to any directory.
On your computer
- Download & install Fastboot, extract the folder to "Downloads" directory
- Download & install Android USB driver for Windows
(I am not sure if XDA allows inserting links in threads or not, so please search for these prerequisites on the internet, it is easy)
II. STEPS
1. Unlocking your phone's bootloader
- Open Settings > About phone > Tap on Build number about 7 times till you see a notification "You are now a developer"
- Now in the About phone tab, you can see the "Developer option". Tap on it and make sure:
+ the OEM unlocking is turned ON
+ The USB Debugging is turned On
- Plug your phone on your computer (with Fastboot & driver fully installed). Allow the USB Debugging notification on your phone
- Open Command Prompt on your computer. Enter commands below steps by steps:
cd Downloads
cd fastboot
adb reboot bootloader
(press Enter after each line to proceed)
- Your phone will reset to the bootloader menu after these commands. Next, enter this:
fastboot oem unlock
- A message asking you to make sure you want to unlock the bootloader. Use the volume and power button to choose "Yes". Your phone will reset data and reboot right after.
*Note: This method works on many Android devices, but doesn't on many devices. You might have to google a method for your own phone
2. Patching the boot.img file
After you extracted the boot.img from your device, use the Magisk app installed on your device to patch it up.
- Click the "Install" button on the first line
- Click "Select and Patch a file"
- Choose the boot.img file extracted. The patching progress will start right after.
- You will receive a file named "magisk_patched.img" after finished.
3. Flashing the "magisk_patched.img"
- Copy the "magisk_patched.img" into the Fastboot folder
- Reboot your phone to Bootloader mode by powering off and then hold Power + Volume down button simultaneously
- Open Command Prompt again, and type:
cd Downloads
cd fastboot
fastboot flash boot magisk_patched.img
- The flashing progress will begin. Wait until it finishes, and type the last command:
fastboot reboot
- Your phone will restart once again, and of course, with root access gained
---------------------------------------------------------------------------
UNROOT DEVICE
- If you want to unroot your device, you just have to flash the original boot.img file, with the same steps with flashing the magisk_patched.img!
---------------------------------------------------------------------------
This instruction is not truly detailed, so maybe you might encounter some difficulties at some point. If any, please feel free to leave your question below.
It is also the first time I create an instruction post, therefore I appreciate all of your comments. Thanks a lot <3
Click to expand...
Click to collapse
It's different for a/b devices where root has to be accessed by booting into the phone from recovery to boot with root
([emoji3590]09-09-18[emoji3590])
PoochyX said:
It's different for a/b devices where root has to be accessed by booting into the phone from recovery to boot with root
([emoji3590]09-09-18[emoji3590])
Click to expand...
Click to collapse
Hi PoochyX,
Thanks for your reply, could you be more specific, please? Does it mean that this method cannot work on a/b devices?
I will edit my instruction again if needed.
Thanks for your suggestions!
to moderators: this is my first thread ever, and thought a complete guide like this really has to be done. if it's not right or not in the right place, do what is right
Click to expand...
Click to collapse
Since there are only 3 useful guides about modifying this specific phone, and some really don't answer a few barriers placed in our way by HMD Global and its ridiculous OEM unlocking restrictions (-_-), and also Google probably dropped making OTA updates for it (which was very important to me, because Android 9 and 10 had bugs), I decided to mix them all up (I will give credits, obv) and add some more info I found and create a thread which will work on Android 11, which worked on my phone, not tested on another Nokia 2.2.
Hope it helps y'all!!
Part 0: Preparations
WARNING: Your storage will be wiped completely!! so make sure to back everything you need up before doing anything. Unless you have bricked/soft locked your phone, then in that case you can use MTK Client app to backup userdata.bin (more info on Part 1-2, marked with a )
Requirements:
A good computer
Obviously a network connection on your computer for downloading files, and on your phone if you wanna update thru OTA
USB cable, capable of transferring data, and without any annoying repeated disconnections or "has to be put in the right angle and position". Just use a fresh one
VCOM and adb drivers, which can be a little annoying getting them to work. Best option is to install 15 seconds minimal ADB and make sure you say Yes when it asks if you want to install device drivers.
Android SDK Platform tools, which can be downloaded from here (NOTE: You have to use Platform tools. minimal adb will NOT work with fastboot on this device. So go to C:\adb and delete everything in there, then extract platform tools in that folder instead)
and the most important of them all: MTK Client by Bkerler which can be downloaded from here. Follow the installation instructions in the link, install Git and Python and also usbdk installer featured in the Github instructions for MTK Client
All done? Great! moving to the next part
Part 1: Unlocking the bootloader
The most annoying part. Thanks to hikari_calyx for their awesome guide on how to unlock the bootloader for this phone. We will follow it step by step until we reach step 6, where we are about to flash all those backed up img's back using mtk-su. Here's the problem, you can use mtk-su only on Android 9. it doesn't work on Android 11 sadly. so we just make sure we have unlocked sec1.img and seccfg.img in a safe place, then install a fresh stock Android 9 rom om our phone with any method we are most comfortable with, like SP Flash tool like in the guide, or booting into recovery and sideloading thru adb or from sdcard. just search the net and I'm sure you will find a loooot of sites explaining how you can flash a stock android on your phone. Just make sure you won't mess IMEI and Serial Number up!!!
**There is a "unlock bootloader" option in the flash tools tab of MTK Client. haven't tried it out myself but you can give it a try**
Extra: Booting into stock recovery
There is another detailed guide on how to enter recovery mode, by foobar1123321 which you can see in here. You might need it to apply updates to your phone
After flashing and updating your OS to latest version of Android 11, it's time for Unlocking the bootloader again. but sadly, Unlocked OEM doesn't let OTA updates to be received, and trying to flash sec1.img and seccfg.img on Android 11 is not possible without root, and root is not possible without OEM unlocking :\
So here comes the neat part, MTK Client
Part 1-2: Unlocking the bootloader again
Go to the folder where you installed MTK Client (hopefully you know how git works and got it cloned and working, if no, then read Installation instructions carefully in their Github page), and open a CMD window there by typing in cmd in the address bar. then write python mtk_gui and hit enter. Do not use mtk_gui.bat since it will close the cmd and not work. Do NOT close this cmd tab. After a while, the app will start and asks you to connect your phone.
Shut down the phone, and after 5 seconds, press and hold both volume up and down keys (without the power button) and connect the phone to your computer via cable while still holding the volume buttons. If you have installed the drivers successfully, then you'll see some texts generate in the cmd window, and will (probably) wait for the Preloader VCOM.
you can let go of the volume keys.... but not for so long. Disconnect the USB cable, hold volume keys, and connect the phone again and you'll see that MTK Client successfully gets access to your phon. YAAAY!!
now you can let go of the volume keys
Go to "Read partitions" tab, and select Boot_a, Boot_b, sec1, and seccfg (make sure you wouldn't mistake them with unlocked sec1 and seccfg)
And then click on Read partitions button in the right side, and choose a location to save these partitions
You can also check userdata, if you have bricked/soft locked your phone and wanna backup your Internal storage data. You can flash it again with this app after you have fixed your phone. and if the problem wasn't caused by your data, you can use them again like you never wiped your phone
After everything is backed up, go to "Write partitions" tab, and find sec1 and seccfg, click on "set", browse and select the respective unlocked partitions we got in Part 1 (you may need to change their extension from .img to .bin for them to show up)
Click on "Write partitions", and done! You have unlocked your OEM on Android 11!! and if everything is done correctly, you'll see
Orange state Your device is unlocked and cannot be trusted Your device will boot in 5 seconds...
Click to expand...
Click to collapse
or something like this when powering it on, congrats!!
Part 2: Installing TWRP
from the official TRWP page for Nokia 2.2, download the latest TWRP image file and move it to c:\adb on your computer and rename it to twrp.img
you will also need to download a stock vbmeta image, which can be found here or simply by reading it from your phone via MTK Client (there will be two A/B partitions, any of them works) and rename the downloaded/grabbed file into vbmeta.img and move it to c:\adb
power off your phone, then boot into fastboot by holding Volume down + Power for a few seconds, until it says FASTBOOT MODE => then connect the phone to a PC, and write:
fastboot –disable-verity –disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
and then
fastboot flash boot twrp.img
Click to expand...
Click to collapse
Now we have the latest TWRP on our Nokia 2.2 , but seems like accessing TWRP is only possible by either rebooting to recovery when the phone is powered on, via Magisk, Termux, or any other app with power options (after rooting the phone), or writing this when the phone is in fastboot mode:
fastboot reboot recovery
Click to expand...
Click to collapse
You can use TWRP and all of its awesome features now, except for MTP, backup, reading userdata partition, etc. to fix that, you gotta wipe internal storage, so make a backup of your files before processing.
**IMPORTANT: Do not flash TWRP after rooting the phone or it will unroot it**
Part 3: Rooting via Magisk
I'm gonna use Magisk because... it's better than other SU apps. Get it from here and install it on your phone. Now that you have your OEM unlocked and boot partitions too, you just have to copy the partitions we got via MTK Client on your device, launch Magisk app, select Install Magisk, then choose a file, which is gonna be Boot_a.
Wait until patching is finished, and after it's done, go into downloads folder and rename it to Boot_a or you will get confused later
After that you can choose Boot_b to be patched, and after it's done, rename it to Boot_b too
Copy them both to C:\adb from your phone to your pc, and power off your phone
after you get sure device is not connected to the computer via cable, and is powered off, hold down the volume down key with power button, until your phone boots into fastboot mode
Now open a cmd in C:\adb, and write
fastboot flash boot_a boot_a.img
fastboot flash boot_b boot_b.img
Click to expand...
Click to collapse
when done, disconnect your device, and restart. You can check the Magisk app, and realize you now have superuser permissions!!!
**UPDATE** Part 3-2: Hiding Magisk
Hiding Magisk and bypassing SafetyNet is another challenging problem on this phone. Cause when you try to Hide the Magisk app, you'll come to a simple "Failed!" error which is most probably caused by SELinux status. To fix this we gotta install some modules
First of all, install Busybox from Google Play or any other source. It's not necessary, but it's good to have. simply just install it, no need to restart
Then we need to install a module called SELinux permissive (wow, how unique ;w; ) by evdenis, which can be found here. download the zip in your phone, open the Magisk app, and in the modules tab browse for our newly downloaded zip and wait until the operation is done. Reboot your phone, and you are now able to hide Magisk app without any problem.
So do so, open Magisk -> settings -> hide the Magisk app. Choose a name (settings by default) and wait until app launches itself, asking you to add a shortcut to your home screen (optional). This way, your Magisk app now has a random package name and signature and can't be detected by other apps. Now moving to the next part
Bypassing the SafetyNet:
First, in Magisk settings, enable Systemless hosts. it will add its module to the modules tab. check if it's enabled
Then toggle Zygisk in Magisk settings, and restart your phone again (2 restarts? alright no problem)
Once your phone booted up, on the main screen of Magisk, check if it says Yes in front of Zygisk. if yes, than congrats! we are not down yet tho
Go to Magisk settings and toggle Enforce DenyList, don't reboot for now (yes, there is a 3rd one coming ), but go to Configure DenyList and choose the following apps
Google Play Service
Google Play Store
Google Service Framework
Google Play Protect Service (which is probably not present, but wrote it just in case it is on your phone)
Click to expand...
Click to collapse
and also you can choose your banking apps, or any app that prevents you from using them like Netflix or some games. Now you gotta restart (third time is the charm )
Now we gotta install another module which is Universal SafetyNet fix by kdrag0n which can be found here. Download it to your phone, choose it in Magisk module browser, wait for it to finish, and restart (I'm losing my control!!! Hmph!)
Now that we did all this, we have to clear data of apps in our DenyList so they would never remember if we ever had root or no
Go to settings (the actual settings, not our now hidden Magisk app) -> Apps -> all apps -> tap the 3 dots on top -> show system apps, then find all the apps you added to your DenyList and clear their data (not cache, data itself)
Now that this is down, restart your phone ((╯°□°)╯︵ ┻━┻) it's the last time, so you can stop raging now (┬─┬ノ( º _ ºノ))
Now we can install an app like YASNAC and run SafetyNet attestation, if the results showed two pass checks, Congratulations, you bypassed SafetyNet!!!
Totally worth the restarts. (Thanks to Droidwin for their article)
And that's it!! Hope you enjoy your now rooted Nokia 2.2 phone with Android 11
Great guide, and yes mtkclients unlock will work but it may put Ur device into verity eio mode
¿Can I use the Part 3-2 to hide Magisk in Android 9 instead of 11?, I find stock Android 11 very laggy and unstable on my phone (using the camera on any app can take from 1 to 3 or 4 tries to get it working, for example), and Android 9 has served me waaaaay better. However, my banking app refuses to work with root.