Related
UPDATE: Please read the updated information at the bottom of this post, on my new recommendation to use the easier method, SuperSU systemless, to patch your original boot.img. This is in my quick start guide at the end of it, also. You still need to read my info on getting setup, also.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have started this thread as a place to post a working root solution for this tablet.
https://www.walmart.com/ip/Nextbook...-System/122137749?variantFieldId=actual_color
This is a great Android tablet for the price. It features an updated Intel Cherry Trail quad core 1.92 GHz processor, 1gb RAM, 16gb internal storage. and Android 6.0.1 Marshmallow.
UPDATE: There is a newer version of the tablet with a manufacturing sticker date of September, 2017. Despite retaining the 8A model number, it has a slower, ARM processor and Android Nougat 7.1.1. Although it is quite snappy, It shows much slower benchmarks in AnTuTu and has a much smaller battery, about half the size. Also the boxes are about 2/3 the thickness of the older, 6.0.1 tablets.
The chances of rooting it are very slim. My solution will not work for it. Fastboot mode appears to be disabled on this and one other Nougat tablet that I own. I am returning the one I tested.
UPDATE: I now have root, a custom TWRP recovery and modified boot images for the Android 6.0.1 version of this device.
I would like to thank @vampirefo for his TWRP and original boot images, for without his work, this would not be possible.
PLEASE DO NOT CONTACT HIM ABOUT THIS HE WILL NOT PROVIDE ANY SUPPORT FOR IT, THAT WILL BE PROVIDED BY ME AND OTHER GENEROUS FORUM MEMBERS.
I strongly recommend, though that you donate to him, in his signature, for all of his hard work on this, even if it is a small amount. I asked him twice about this and he never responded, so please donate to him.
His original boot.imgs are modified to remove encryption and make the kernel permissive.
I unpacked them and removed dm_verity to remove the failed verification message, on boot then repacked them.
FILES ARE UP ON ANDROID FILE HOST
https://www.androidfilehost.com/?w=files&flid=197521
Choose the version of the tablet that you own. Go to settings, about tablet and scroll to the bottom and look at the first few numbers of the build number. For example: V1.2.0.
Do not use this on the 1.0.8 version of the tablet or you will loose sound, wifi and maybe bluetooth. If you have this version of the tablet and can provide me a twrp, backed up, original boot.img, I can modify it to work with your tablet. You can temp boot twrp, to do this (see below). As of yet no one has provided one to me for the 1.0.8 tablet version.
UPDATE 10/24/2017: I now have a I now have a 1.0.8 modified boot.img up on android file host:
https://www.androidfilehost.com/?fid=962021903579487577
Here is a twrp backup of the 1.2.0 rom, with userdata deleted to start fresh. It will boot to the Android setup screen. If you have any major, unexplained problems, I recommend starting fresh with this. It works great on either tablet version: 1.1.1 and 1.2.0.
https://www.androidfilehost.com/?fid=673368273298970542
UPDATE 12/15/2017: I have uploaded a pre-rooted TWRP backup of my original V1.1.1 tablet
https://www.androidfilehost.com/?w=files&flid=235141
TO PREPARE YOUR DEVICE:
UPDATED 12/3/2017: I now have found a Version 2.1.5 of the tablet and have uploaded an unrooted, TWRP backed up version of it. It also contains the original recovery so do not check that box when flashing it in TWRP unless you intend to replace TWRP with the stock recovery
https://www.androidfilehost.com/?fid=673791459329065002
This will be long and thorough, because I see so many people who have trouble with this because they don't have their computer setup properly from the get go.
This will help you get ready to be successful in applying this.
First and foremost, unlocking your bootloader will delete all userdata on the tablet so you need a good backup of important files. If you backup to an external sd card, I strongly recommend also copying the files to an external source such as your computer. You can do that through mtp or remove the card and place it in an sd card adapter and insert it into an sd card reader. I did not do this, even though I knew better and my sd card was corrupted in the process, so I lost the original twrp backup of the virgin, untouched system partition.
Secondly, if you are on windows you need the proper drivers for adb and fastboot installed on your system. Proper drivers are the number one issue I see with windows users. For this Intel device get them here:
https://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
Here are the steps to install adb and Intel drivers, in the proper order:
The best way to to set up adb and fastboot in windows is to install it system wide. Here is an installer to do this that works well:
https://forum.xda-developers.com/showthread.php?t=2588979
Install process for 15 sec adb:
1. Run it (Require administrator privileges)
2. Press Y/Yes to install ADB and Fastboot
3. Press Y/Yes to install ADB system-wide
4. Press N/No to skip installing Drivers
5. 15 seconds passed - finished!
6. Now install the Intel drivers listed above and here, again:
https://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
Third, enable developer options by going to settings, about tablet, and tap on the build number seven times to enable it.
Then go to developer options and make sure usb debugging is enabled. watch on the tablet screen for a popup dialog the approve usb debugging. check the box to always allow for this computer and hit ok.
Now, with the proper drivers installed, adb and fastboot properly installed, You need to test that it is functioning properly. This is done with the tablet booted into Android. If you used the adb I recommended, go to my computer, C drive and open the newly created adb folder. Left click in an open area of the folder to select it. then shift right click to open a contextual menu, then select: open a command prompt here. Once the command window is open, type:
Code:
adb devices
and hit enter:
you should see the device serial number listed. I am now doing this from linux, so it may differ,slightly:
adb devices
List of devices attached
YFGV1216059870 device
Sometimes you get starting daemon on port... and you have to type it again to see the device listed. If you don't see this, then your drivers or adb/fastboot aren't properly installed.
If you see your device, then type:
Code:
adb reboot bootloader
and hit enter. your device should now reboot to bootloader mode. once in bootloader mode, type:
Code:
fastboot devices
enter and you device should once again be listed.
the next step, is to unlock your bootloader. Warning: ALL OF YOUR USERDATA WILL BE DELETED, HENCE THE BACKUP CREATED EARLIER. YOU HAVE BEEN WARNED!
It has come to my attention that this is not clear: after unlocking the bootloader, all userdata will be deleted, like doing a factory reset.
Go into developer options and select OEM unlocking. This does not unlock your bootloader, it only enables the ability to do it from a fastboot prompt.
Now jump to the Quick Start guide for updated instructions:
Older, system mode method hidden, please use the instructions in the Quick Start Guide
Now, while still booted into bootloader mode, type:
Code:
fastboot flashing unlock
and hit enter to unlock your bootloader. All data will be deleted and the tablet will be re-encrypted upon boot, without encryption option removed from the bootloader. Now type
Code:
fastboot reboot
t, to reboot the tablet and you should reboot to the android setup screen, You can set it up again if you want, but you will be deleting userdata later when you flash the modified boot.img, so keep this in mind.
So you may want to wait to unlock until I release twrp and the boot.img, so you can continue using the tablet.
UPDATE: The files are now live.
To summarize, the above steps are to prepare you for the next exciting adventure to come and to realize the full potential that a rooted device offers..................
To be continued.
THE FILES ARE NOW ON ANDROID FILE HOST. DOWNLOAD HERE:
https://www.androidfilehost.com/?w=files&flid=197521
Boot or flash TWRP Recovery and flash boot.img
These instructions are for Windows, for Linux you must type sudo before fastboot commands
Instructions: first make sure you read the instructions above to be sure you have the proper drivers and adb and fastboot are installed and tested before proceeding. Unlock your bootloader per above instructions. WARNING! DANGER WILL ROBINSON! THIS PROCEDURE WILL DELETE ALL USERDATA ON YOUR TABLET SO BE SURE YOU HAVE A BACKUP OF ANY IMPORTANT DATA.
First, unzip the files to a directory. I usually do it in C:\adb, and leave the SR2-SuperSU-v2.82-SYSTEMMODE.zip, zipped.
Now, left click in that folder in an empty spot, or where ever you unzipped it and select it. Now right click and choose open a command prompt here from the contextual menu. once the command window is open type
Code:
adb devices
, hit enter, to confirm your device is listed. Now type
Code:
adb reboot bootloader
and it should reboot to bootloader mode.
I recommend booting into twrp temp first so you can backup your original boot, recovery and system.
now:
Code:
fastboot boot Ares8A_recovery_twrp.img
enter and it should reboot to twrp temp. Don't choose read only after it boots. Once in twrp choose backup and hit select storage and choose micro sdcard. now swipe to backup. You can later install twrp permanently if you want to. To flash permanently:
From bootloader mode:
Code:
fastboot flash recovery Ares8A_recovery_twrp.img
UPDATE: See the the end of my updated quick start guide for updated info on a simpler method to patch your original boot.img with either systemless SuperSU or Magisk. I no longer recommend flashing my patched boot.imgs, but instructions are still provided here for historical reference and for the few who still want SuperSu in the unofficial, system mode.
I have hidden the older method here, but is still here for those who still want system mode SuperSU:
Now
Code:
fastboot flash boot Ares8A_111_boot.img
enter, for the 1.1.1 version, or
Code:
fastboot flash boot Ares8A_120_boot.img
enter, for the 1.2.0 version, to flash the appropriate boot.img
For the newer 2.1.5 version of the table:
Code:
fastboot flash boot unsigned-new.img
hit the enter key, to flash.
Next, again in bootloader mode issue:
Code:
fastboot format userdata
enter, and wait for a successful message in the command window and on the tablet. it will take a little while.
Next
Code:
fastboot format cache
enter, wait. Now
Code:
fastboot reboot
hit enter, and the tablet should reboot to the android setup screen where you can set it up. It will take some extra time to reboot, so be patient. You may see the boot animation for awhile. This will be booted unencrypted now without root. I recommend doing a backup again in twrp before rooting.
There has been some misunderstanding about the above. Your data is encrypted and will not be accessible it twrp, hence, the backup before you do anything with this tablet.
You must wipe the userdata, so a new, clean data partition can be created that is unencrypted. A factory reset is not enough. You will have problems if you don't format userdata in the above step to created a decrypted data partition.
Flashing SuperSu for root
For the v1.1.1 and v1.2.0 tablets:
Make sure you have the SR1-SuperSU-v2.82-SYSTEMMODE.zip on your ext sd card.
For the newer 2.1.5 you need a systemless version of SuperSU:
SuperSU-v2.82-201705271822.zip Get it at:
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip Copy it to your external SD card.
When flashed, this systemless version will also patch your boot image for sytemless mode.
Furthermore, to install SR1-SuperSU-v2.82-SYSTEMMODE.zip, or SuperSU-v2.82-201705271822.zip, either boot twrp temp again, from bootloader mode issue:
Code:
fastboot boot Ares8A_recovery_twrp.img
, or if you already have it installed permanently and you are booted normally, issue
Code:
adb reboot recovery
enter to boot to it.
Next hit the install button in twrp and choose SR1-SuperSU-v2.82-SYSTEMMODE.zip or SuperSU-v2.82-201705271822.zip and swipe to confirm flash. after it is complete, go back to the main menu and choose reboot system. I choose not to install the twrp app before reboot.
Once rebooted, open the supersu app, making sure the following are selected in settings enable superuser, default access prompt or grant, enable su during boot, trust system user and enable pro, then go back and enable full content in logging. Next download a root check app to confirm root.
congratulations you should now be rooted! Now download a desired app that requires root and test to confirm you have no problems with root.
If you want an app that makes it easy to reboot in the various modes, I recommend Simple Reboot by Francisco Franco. It works great with this device and android version.
I was using Easy Reboot [ROOT] by Simone Luconi with my older, ares 8 with 5.1.1 and it had worked well.
Apparently it is not compatible with this device or rom. when I rebooted to recovery with it, I was not able to mount my external sd card and the card was corrupted on reboot. That is why I don't have a virgin, unrooted, copy of my system image now.
Good luck!
Here is a quick start guide for the already initiated:
https://forum.xda-developers.com/showpost.php?p=72970060&postcount=82
Here is a link to my post for some apps I personally find useful:
https://forum.xda-developers.com/showpost.php?p=72995672&postcount=112
Please report successes and problems on this thread, not to @vampirefo.
Thanks
@vampirefo has a solution, but has not released it. I'm not sure if it needs more work or testing before release? He has been quiet in this regard. It is my hope that he will reply with more relevant information about this.
I and maybe others, would be willing to give a donation, if that would help.
Thanks
Bootloader unlocking
WARNING! UNLOCKING THE BOOTLOADER WILL DELETE ALL OF YOUR DATA!
DON'T DO THE UNLOCKING UNTIL WE CAN REMOVE ENCRYPTION AND HAVE TWRP FOR BACKUP. YOU HAVE BEEN WARNED!
You can enable the ability for the bootloader to be unlocked with a setting in the developer options. Like I stated, it enables the ability to unlock it, but does not unlock it. On must use the command in adb, through a computer. make sure usb debugging is enabled in the developer options. In a command prompt issue adb devices to make sure your device is showing up. There will be a prompt on your tablet to allow this. Confirm this.
Now with the tablet off, boot into fastboot by hold the volume key down button and the power button at the same time. Also, you can type: adb reboot bootloader then hit enter to get into bootloader or fastboot mode.
Once in fastboot mode, open a command prompt in windows and type fastboot devices to confirm your device is still showing up. If my memory serves me correctly there will also be a security confirmation on the tablet, to approve.
To unlock the bootloader type: fastboot flashing unlock. All data will be deleted and (I believe,) the tablet will be re-encrypted upon boot, without encryption option removed from the bootloader.
I HAVE NOT TESTED THIS, AS I DON'T WANT TO DELETE DATA, UNTIL WE HAVE TWRP TO BACKUP AND ROOT.
6/7/2017 UPDATE: I HAVE UPDATED THE UNLOCK COMMAND. I HAVE UNLOCKED MY BOOTLOADER. AS I THOUGHT, ALL USER DATA IS DELETED (FACTORY RESET). I USED THE FIRST:
"fastboot flashing unlock" Unlocks the device. Allows flashing any
partition except bootloader-related
partitions
"flashing unlock_critical" Enables flashing bootloader-relate partitions.
all fastboot commands are listed by just typing fastboot, while booted into bootloader mode. My tablet is still running great with my bootloader unlocked. One more tiny step toward gaining root, however, there is still a long way to go.
Please post any additional info if I have something wrong, or left out any important steps.
Thanks
Geenify: How to grant permissions required by some features on non-root device?
I am currently using Greenify on my non-rooted device and it is working very well.
By using adb, one can grant it additional permission so it performs almost as well on an unrooted device. Here is a link for this:
https://greenify.uservoice.com/know...o-grant-permissions-required-by-some-features
I copied and pasted each command, one at a time, in the command prompt then hit enter, to enable each one.
In Greenify settings, I also have aggressive doze enabled, Automated hibernation enabled, Wakeup Tracker enabled and Quick action Notification enabled.
How to boot into stock recovery mode
To boot to the stock recovery through adb:
adb reboot recovery
You will see "no command" on the tablet.
Hold the power button and volume up for about 4sec then release the volume up, where you should go to the stock recovery screen.
You can also get to it without a computer. With the tablet shut down, hold the volume down power button until it boots to bootloader or fastboot mode.
Use the volume up or down button to toggle through the options: normal boot, restart bootloader, recovery mode, reboot, power off and ftm mode. Choose recovery and use the volume up and power button as before.
In addition you can get to the efi bootmanager by holding the volume up, power button when the device has been shutdown first.
adb security confirmation
Unlike my Nextbook Ares 8 with 5.1.1, with this newer tablet which has 6.0.1, I have to reaffirm the security prompt on the device each time, despite checking the box: "Always allow from this computer".
Maybe this is because of the tightened security in Android Marshmallow? I'm not sure.
If there is a way around this each time, please let me know
Thanks
UPDATE: After I unlocked the bootloader and the tablet was factory reset, I no longer have to re-approve each time after checking the box: "Always allow from this computer"
Would love to see some break throughs with this device aswell. Cheers to any one working in it.
Is this relevant? It would seem they are the same device. twitter.com/srsroot/status/846663673645010944?lang=en
Giftlift said:
Is this relevant? It would seem they are the same device. twitter.com/srsroot/status/846663673645010944?lang=en
Click to expand...
Click to collapse
Don't try any of these one click root solutions. none work to my knowledge on android 6.01, (at least on this device) , and may install malware or pups on your host computer.
martyfender said:
Don't try any of these one click root solutions. none work to my knowledge on android 6.01, (at least on this device) , and may install malware or pups on your host computer.
Click to expand...
Click to collapse
:good::good:
This requires a lot of work.
1. Google kernel source.
2. Build bootable kernel
3. Unlock bootloader
4. Boot kernel with 5.1 ramdisk.
5. Use adb to pull boot.img and recovery.img
6. Download TWRP source modify source for intel
7. Make device tree
8. Unpack recovery.img use that kernel in your TWRP.
9. Make boot.img permissive, remove encryption repack and flash.
10. Flash TWRP.
11. Flash system mode SuperSU for root.
Sent from my LIFE X8 using Tapatalk
vampirefo said:
This requires a lot of work.
1. Google kernel source.
2. Build bootable kernel
3. Unlock bootloader
4. Boot kernel with 5.1 ramdisk.
5. Use adb to pull boot.img and recovery.img
6. Download TWRP source modify source for intel
7. Make device tree
8. Unpack recovery.img use that kernel in your TWRP.
9. Make boot.img permissive, remove encryption repack and flash.
10. Flash TWRP.
11. Flash system mode SuperSU for root.
Sent from my LIFE X8 using Tapatalk
@vampirefo Thanks for taking the time to post this.
To familiarize myself with Linux, I created a persistent linux Mint 17.2 Mate 64 bit on a 32 gb usb thumb drive before I decide to commit my windows machine for a linux install.
I installed oracle jdk and android studio thinking this was the build environment needed to do this. the twrp compile forum makes no mention of what to do in this case. I must have been wrong? I don't think I need this to download and build android kernel sources and twrp source?
I'm now very doubtful about even tempting to do this. Yes, a lot of work just learning the basics of linux, let alone following the steps you give in your basic outline. I don't want to give up so easily, but the learning curve is steep.
So one just uses terminal commands to setup and download aosp and twrp git repositories and to make them? Also, is there any way to backup my device system, boot and recovery without root in linux or windows? I have used the adb pull command to backup the system directories to my windows computer, but don't know how to do it for other partitions, if possible.
I found this kernel building guide for arm and mediatek devices. would this be similar for Intel using the right repositories?
https://forum.xda-developers.com/android/software/guide-easy-kernel-building-tutorial-t3581057
Thanks
Click to expand...
Click to collapse
martyfender said:
vampirefo said:
This requires a lot of work.
1. Google kernel source.
2. Build bootable kernel
3. Unlock bootloader
4. Boot kernel with 5.1 ramdisk.
5. Use adb to pull boot.img and recovery.img
6. Download TWRP source modify source for intel
7. Make device tree
8. Unpack recovery.img use that kernel in your TWRP.
9. Make boot.img permissive, remove encryption repack and flash.
10. Flash TWRP.
11. Flash system mode SuperSU for root.
Sent from my LIFE X8 using Tapatalk
@vampirefo Thanks for taking the time to post this.
To familiarize myself with Linux, I created a persistent linux Mint 17.2 Mate 64 bit on a 32 gb usb thumb drive before I decide to commit my windows machine for a linux install.
I installed oracle jdk and android studio thinking this was the build environment needed to do this. the twrp compile forum makes no mention of what to do in this case. I must have been wrong? I don't think I need this to download and build android kernel sources and twrp source?
I'm now very doubtful about even tempting to do this. Yes, a lot of work just learning the basics of linux, let alone following the steps you give in your basic outline. I don't want to give up so easily, but the learning curve is steep.
So one just uses terminal commands to setup and download aosp and twrp git repositories and to make them? Also, is there any way to backup my device system, boot and recovery without root in linux or windows? I have used the adb pull command to backup the system directories to my windows computer, but don't know how to do it for other partitions, if possible.
Thanks
Click to expand...
Click to collapse
All work is done in terminal, root is required to make backups.
Sent from my LIFE X8 using Tapatalk
Click to expand...
Click to collapse
vampirefo said:
martyfender said:
All work is done in terminal, root is required to make backups.
Sent from my LIFE X8 using Tapatalk
Click to expand...
Click to collapse
So I could uninstall android studio. Should I also revert back to openjdk? I see it mentioned in google docs on setting up a build environment.
UPDATE: I think I have now setup properly. Reverted to openjdk 8
I downloaded this: git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/x86/x86_64-linux-android-4.8
I found this: https://github.com/CM-CHT/android_device_intel_cherrytrail-common Would this be useful?
Thanks
Click to expand...
Click to collapse
martyfender said:
vampirefo said:
So I could uninstall android studio. Should I also revert back to openjdk? I see it mentioned in google docs on setting up a build environment.
UPDATE: I think I have now setup properly. Reverted to openjdk 8
I downloaded this: git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/x86/x86_64-linux-android-4.8
I found this: https://github.com/CM-CHT/android_device_intel_cherrytrail-common Would this be useful?
Thanks
Click to expand...
Click to collapse
No ideal, try it and see.
Sent from my LIFE X8 using Tapatalk
Click to expand...
Click to collapse
What would it take to interest @vampirefo in rooting this tablet and providing a nice clean ROM for the Ares 8A???
cjhudson101 said:
What would it take to interest @vampirefo in rooting this tablet and providing a nice clean ROM for the Ares 8A???
Click to expand...
Click to collapse
For me to root and provide TWRP recovery, I would need the tablet.
Sent from my Life Max using Tapatalk
vampirefo said:
For me to root and provide TWRP recovery, I would need the tablet.
Sent from my Life Max using Tapatalk
Click to expand...
Click to collapse
My bad, I guess I misunderstood one of your posts where you said you successfully rooted the tablet, but were withholding the method...
What if I sent you one?
cjhudson101 said:
My bad, I guess I misunderstood one of your posts where you said you successfully rooted the tablet, but were withholding the method...
What if I sent you one?
Click to expand...
Click to collapse
You didn't misread, I rooted my son's, he doesn't live near me, he is in college. He is using my laptop that I used, so all my source files are with him.
I need tablet to start over, I already know what to do but without tablet, I can't do it.
Sent from my Life Max using Tapatalk
Check your zip in the link, lets get vamp an 8a!
I just got one of these for $35, but now the closest walmart with it in stock is an hour away. Ill totaly send you one if I drive that way for any reason. Check your zip on brickseek ..... anyone?
slickdeals.net/f/10189248-nextbook-ares-8a-16gb-tablet-android-6-ymmv-35-bm?src=SiteSearchV2_SearchBarV2Algo1
it came with 6.0.1 on it
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've been successful at porting over TWRP (Team Win Recovery Project) Recovery to the Pioneer XDP-300R Digital Audio Player! The recovery can be flashed directly over the stock recovery using Fastboot, or you can temporarily boot into it using fastboot.
First off, TWRP, replaces the stock recovery and allows users to backup and restore system, data, boot and other partitions on their player onto their storage or sdcards. It also can install superuser (root) access if you want that feature to allow editing and modifying of the system folder. That opens the door for additional mods.
You can also install Magisk, which is a systemless root feature that is a little safer since it does not touch your system folder, but instead patches the bootloader and then creates a layer above system that stores the mods and changes within the Magisk system in.
First off, I made system image, bootloader and recovery images of the stock 300R prior to going into this full swing. I had already rooted my device using Kingoroot but this is no longer needed and is much more safe now.
So you'll want to get the recovery first.
https://drive.google.com/open?id=1diqQ8LE-yG4b-WZFB_OPcQp2rDUp9BbV
The link in my google drive will take you to a folder where I have backups of my images. The TWRP recovery is located in the Recovery folder, along with the stock Recovery image.
Tools Needed:
Android USB drivers for ADB and Fastboot
ADB and Fastboot
Terminal or Command Prompt
Some basic knowledge on how to use these tools
Pre-Installation:
In android, go to Settings, and turn on Developer Mode. To do this, click Settings, then Device Information, then scroll to Build Number. Tap this several times until you unlock Developer Options.
Now, go back to the Settings Menu and go to the new Developer Options menu. Check the OEM Unlocking option to allow the bootloader to be unlocked.
Installation of TWRP:
1. Download the TWRP image and place it in the same folder as ADB/Fastboot tools.
2. Open a terminal or cmd prompt window and go to the folder in (1)
Code:
EXAMPLE: cd /android
3. Turn off the 300R. Then hold next track (the button closest to SD slots) and press power and let go while holding the next track button. A Penguin will appear on screen. Then let go, and plug device into computer.
4. In terminal, check to see if fastboot works.
Code:
fastboot devices
5. If it does not show a device, check your drivers! If you see a device, let's go forward!
6. Now we will install the recovery.
First we need to unlock bootloader:
Code:
fastboot oem unlock
If you are nervous, and want to verify it works, you can do a temporary test by typing the command:
Code:
fastboot boot TWRP-XDP-300R.img
This will boot directly into the TWRP recovery and will go away when you restart. But you can see if it works this way and mounts each folder correctly.
If you're ready to take the plunge, use this command:
Code:
fastboot flash recovery TWRP-XDP-300R.img
7. Once it flashes, you can always reboot into recovery by powering off. Then holding PREV TRACK (button closest to power) and power on. It'll show the penguin, and then load recovery soon after.
8. Once you see the TWRP screen youre good to go! I recommend making a System, Data, and Boot backup immediately so you have it ready. I also have the stock recovery in the folder for backup purposes too!
Root Access
When you exit TWRP, you have the option of installing SuperUser (root) access. You're welcome to install or decline it. I recommend using Magisk at this point, by looking up Magisk Manager and loading that onto your device. It'll also provide root access along with other goodies like Xposed, some adblocking stuff, and if you like, Viper4Android, and other mods.
To first start the process of Magisk, you need to unlock the bootloader. Go into Fastboot mode again on the phone, as described above, and go to command prompt:
Code:
fastboot oem unlock
This command will unlock the bootloader. In the future, you can lock it by replacing unlock with lock: fastboot oem lock
Magisk only installs correctly when you use the magisk zip file that can be downloading through Magisk Manager. This zip file needs to be flashed in TWRP Recovery. Once you do that, it'll patch the bootloader and allow Magisk to work correctly. You can verify by opening Magisk Manager in Android, and seeing if it is activated.
Once activate, you can click the menu on the left side of the Manager app, and click DOWNLOADS to find a list of modules available for use. Not all are compatible with the older Android Lollipop that is on XDP-300R, so be careful of that.
Magisk Modules
Some modules I use are:
Xposed Framework - another modding system - see below
LKT - tweaks to the kernel for battery management
Magisk Manager for Recovery Mode - Recovery command line manager (seems buggy)
SafeMode4Magisk - Boots into safe mode for disabling bad modules
Swap Torpedo - Optimizes Swap files for RAM management
Youtube Vanced - Themes and removes ads from Youtube
Greenify - adds additional features to Greenify app
Xposed Framework (now systemless using Magisk!)
Some modules I use are:
Amplify - Standalone app that needs Xposed for disabling or reducing amount of system wakelocks and alarms which greatly save battery life
Greenify - Standalone app that hibernates unused apps to save battery life and uses Xposed for additional features
Youtube AdAway - Removes ads from Youtube
BUILD.PROP MODS
The Drive Link at the top of this page has my modified build.prop in it. You can replace your existing build.prop with this if you want. Make sure you make a backup just in case!
Diverting sound away from Android OS to the DAC:
Open up BUILD.PROP in /System in your android device and look for PCM Offload
There are two lines there, that start with audio.offload...
Remove the Hash in front of each of them if they are present and that's it!
it should read:
Code:
#PCM offload
audio.offload.pcm.16bit.enable=true
audio.offload.pcm.24bit.enable=true
Also verify that this is enabled:
Code:
av.offload.enable=true
Hi ! Thank your for your work ! There are a version for the XDP-100R please ?
(sorry for my bad english)
HI, I'm thankful for your development. But is there any chances to reflash the firmware if something goes wrong?
A few days ago on my xdp300r part of the system spilled out and actually are system applications. Nothing can be installed on it, is there any possibility of restoring the original state? Restarting and recovery mode unfortunately did not help.
Thanks alot. I needed this so bad. A long time after I bought XDP300R I can only dare to use superSU to get root access and that's it. And now xposed and magisk are possible, Thank you soo much.
Hi thanks. I managed it fine. I used su as majisk would not install. Luckily I followed your advice and made a backup(I don't usually bother). I installed your build.prop and the pioneer would not boot. I have restored using twrp and changed my own build.prop so alright now. Thanks.
HI GUYS.
I am trying to unlock my 300R.
When I execute 'fastboot oem unlock' I got DENIED message.
I am stuck. Is there any hope for my player?
Daniel
gavroche33 said:
HI GUYS.
I am trying to unlock my 300R.
When I execute 'fastboot oem unlock' I got DENIED message.
I am stuck. Is there any hope for my player?
Daniel
Click to expand...
Click to collapse
have you enabled the OEM unlock in the developer setting?
I do not have option like that. My player was cleared from data, but it is still locked. I cannot OEM unlock it
Any other way?
Daniel
Grazie mille per il tuo lavoro
gavroche33 said:
I do not have option like that. My player was cleared from data, but it is still locked. I cannot OEM unlock it
Any other way?
Daniel
Click to expand...
Click to collapse
Go to setting, to Device Information, to Build Number. Tap 7 times. You get Developer Options
Back up go to Developer Iptions, select OEM Unlocking.
Re-do OEM unlocking as described in OP
Hi,
I tried to follow this tutorial but my device is not show I checked the drivers!
But still the same, is it possible to had any help ?
Since we already have an open bootloader, is there a chance to make a newer android, I propose version 9 because in newer ones you lose the ability to play some formats, it would certainly give a second life for this model
Dear XDA forum readers/members,
I have an issue with my Pioneer XDP-300R. At this stage I can only boot into it with the TWRP (TWRP-XDP-300R.img) image provided in the first post. I also have downloaded the recovery files, including the (stock?) system image (system-noxposed.img).
When I try to flash the same image from within TWRP, I can only select the "boot" or "recovery" partitions. In this screen, there is no option to boot towards a "system" partition.
If I boot from a ZIP file containing the system-noxposed.img file, I obtain either a different error which complains about a META-INF and binary not found? , or I obtain an error which (of course) writes there is too little space to write a system image in a boot or recovery partition.
My question(s) is/are: Is there any method to flash a system image towards the system partition from within TWRP, and/or how to solve the "unknown chunk type" error?
Any help would be greatly appreciated.
EDIT: The issue has been solved, but there is another problem now. When the device would not boot TWRP anymore (as in: froze at TWRP logo) I decided to look at the partitions (with dd): Now, I had made the mistake of overwriting the very first boot partition, and now the device will not power up anymore. By all means and purposes, he is hard bricked now If there is anyone who would like to help, I'd be very grateful, assuming there are still options left.
Greetings from a new member in need of help
Before doing anything to device, keep a copy of Stock ROM from here in your PC or SD Card.
Rooting with Magisk
Tutorial:
The procedure is the same whether you're on the stock RealmeUI Rom or on a custom GSI (treble) one or on a custom ROM.
Step 0 - Go to extracted platform tools folder in your PC and Shift + Right Click and choose Open Command Window here and connect the device to PC.
Step 1 - Boot to Recovery with adb reboot recovery and run below commands in command prompt by connecting the device to PC
Code:
adb root
adb pull /dev/block/by-name/boot boot.img
adb reboot
After running after commands you will get boot.img in your platform tools folder of PC. Copy the boot.img to mobile.
Note:- Above commands won't work if you are on GSI/custom ROM rom with stock recovery. So flash TWRP and follow above to get boot.img or use root debugging in ROM if available.
Step 2 - Download and install the latest Magisk app from here on your phone.
Click on the latest Magisk-vX.Y.apk you see in the list to start the download, open the file and install.
Step 3 - On your phone, open up Magisk app.
Click the Magisk Install button as shown below.
Then Select and Patch a File.
Go look for your boot.img you previously copied to your phone and pick it.
Click Let's go! and wait for Magisk to complete the process!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step 4 - Link your phone to your PC, and grab the file the Magisk app created. It's located in your downloads folder, called magisk_patched_blAh.img.
Step 5 - Paste it where your ADB & Fastboot (Platform Tools) are located, along with the vbmeta.img by downloading from here.
You should now have a folder like this with:
adb(.exe)
fastboot(.exe)
magisk_patched.img
vbmeta.img
Extra files from the platform tools
Step 6 - Link your phone to your PC with the USB cable if not done already.
Step 7 - Shift + Right click in an empty space inside the folder we prepared in Step 7, and click Open Command window here.
Inside the Command window, input the following commands line by line, in order.
Code:
adb reboot bootloader
fastboot devices
And make sure your device shows up, should be a bunch of numbers and letters, a couple spaces, and fastboot.
If nothing does, go back to Step 7 and try again.
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot magisk_patched_blAh.img
fastboot reboot
You're done! Your phone will reboot, hopefully, without a hitch! Open up Magisk app, and check that it's installed.
That said, you will have issues leaving it like this. You need to hide the fact that your phone is rooted, there's no downside to doing it.
Check out the Passing SafetyNet tutorial further down below, it's quick and easy.
For more info, see official Magisk installation instructions at https://topjohnwu.github.io/Magisk/install.html
Passing SafetyNet (Only possible with Magisk. Not with SuperUser on GSI's)
Tutorial:
Enable Magisk Hide inside Magisk app's settings and Install Universal SafetyNet Fix module.
Reboot and enjoy! You're all set and SafetyNet should pass just fine.
Q: Hey, I rooted/edXposed my phone, and now Netflix won't even open, or doesn't work properly, what's up with that?
A:
Well, fortunately, there's an easy fix if you have Magisk. Install the liboemcrypto disabler Magisk module, activate it and reboot.
Credits:-
@Akitake for his guide at here
Now we have root.
We can uninstall system apps with below command in Termux
Code:
su
pm uninstall --user 0 <package_name>
We can use Package Viewer app to know package names.
Getting EDXposed
Spoiler: Click to Show content
Tutorial:
I very much discourage to EdXposed your phone unless you have a very good reason for it.
It's a pain to pass SafetyNet.
It doesn't get updated often.
It has very niche use cases for which it's actually worth it.
That said, I explain it here for people who know what they're getting into and want instructions on how to do it.
This procedure requires to be rooted with Magisk.
Step 1
Inside Magisk app, go to the Modules tab.
Click the search button (bottom right) and search Riru.
Install the Riru module by Rikka.
Activate it and Reboot.
Step 2
Download and install the latest EdXposed Manager, the same way you did with Magisk app when rooting.
Step 3
Open it up, go to the ALPHA tab and click install/update.
It'll start a file download.
Step 4
Go back to Magisk app, Modules tab, except this time click Install from Storage.
Point to the .zip file you just got, located in the Downloads folder of your phone.
At the end of the installation, click reboot.
Step 5
Let's double check your installation is operational.
Go to EdXposed Manager, first tab.
It should say EdXposed Framework is active.
You're done!
You should now be able to install EdXposed modules.
That said, you will have issues with certain apps leaving it like this.
You should to hide the fact that your phone is EdXposed.
Check out the Passing SafetyNet tutorial further down below!
For more info, see https://forum.xda-developers.com/t/...or-of-xposed-oreo-pie-q-r-2020-07-19.4070199/
Passing SafetyNet With EDXposed installed
Tutorial:
Again, I highly recommend not EdXposing your phone and sticking to just Magisk if you can help it.
You should also know that this method will show you're passing SafetyNet inside Magisk but it's a pain to do and isn't as well hidden as Magisk alone.
Step 1 - Do the step for Rooted phones listed above if not done already.
Step 2 - In EdXposed Manager, get the HiddenCore Module and activate it.
Step 3 - Now, in the side-menu: Compat List > tick HiddenCore Module.
Step 4 - Then, go to Settings > Framework > Enable "App List mode".
Step 5 - Finally, Applications(Black List) and tick: Android Services Library, Chrome, Google Play services, Google Play Store, Google Services Framework
Reboot and enjoy! You're all set and SafetyNet should pass.
Sir thank you so much for the instruction i want to a custom rom for My realme C12 how to installed it thank you for Response
Randymem said:
Sir thank you so much for the instruction i want to a custom rom for My realme C12 how to installed it thank you for Response
Click to expand...
Click to collapse
For now, custom ROMs have some issues.
Try flashing GSI using https://forum.xda-developers.com/t/gsi-phh-q-r-gsi-flashing-for-realme-c12.4244979/
Thanks
HemanthJabalpuri said:
For now, custom ROMs have some issues.
Try flashing GSI using https://forum.xda-developers.com/t/gsi-phh-q-r-gsi-flashing-for-realme-c12.4244979/
Thanks
Click to expand...
Click to collapse
Thank you sir
How do you update to latest firmware without losing root, data, settings?
immortal_jerk said:
How do you update to latest firmware without losing root, data, settings?
Click to expand...
Click to collapse
I didn't tried this before, but flashing Magisk-patched boot.img after update may revive root with all previous modules.
If you got any other method, then let me know here.
Thanks
sir newbie here when i enter command (adb root)
it say access denied you dont have confimation.
wow thanks dude i succesfully rooted my phone.
Will this work for realme ui 2.0 android 11?
immortal_jerk said:
Will this work for realme ui 2.0 android 11?
Click to expand...
Click to collapse
Yes, but see the note in red colour of Step 2.
Thanks
HemanthJabalpuri said:
Yes, but see the note in red colour of Step 2.
Thanks
Click to expand...
Click to collapse
i installed THAT magisk and rooted my phone ui2.0.. but theres no magisk hide option in settings and i cant install safetynetfix module, it asks for a file called riru... and also i cant search for modules in the magisk app
immortal_jerk said:
i installed THAT magisk and rooted my phone ui2.0.. but theres no magisk hide option in settings and i cant install safetynetfix module, it asks for a file called riru... and also i cant search for modules in the magisk app
Click to expand...
Click to collapse
Can you please send screenshots of settings screen and module section of Magisk app so that I can better understand what's going wrong.
HemanthJabalpuri said:
Can you please send screenshots of settings screen and module section of Magisk app so that I can better understand what's going wrong.
Click to expand...
Click to collapse
as you can see theres no magisk hide option in settings, only the option to hide the app, tried that too but nothing works, turning Enforce DenyList on/off dont work neither... and nothing comes up when i search for modules
HemanthJabalpuri said:
Can you please send screenshots of settings screen and module section of Magisk app so that I can better understand what's going wrong.
Click to expand...
Click to collapse
i was able to manually install riru and safetynet fix modules in magisk, but i still cant pass safetynet
immortal_jerk said:
as you can see theres no magisk hide option in settings, only the option to hide the app, tried that too but nothing works, turning Enforce DenyList on/off dont work neither... and nothing comes up when i search for modules
Click to expand...
Click to collapse
Ah, got the culprit.
Magisk hide and Official Modules Repo are no longer part of Magisk from the developer.
To get those back, we can use older version of Magisk.
I have updated the Magisk apk link for UI 2.0. Uninstall Magisk by choosing 'Uninstall Magisk' in main screen and root again with the updated link.
Also, Universal SafetyNet fix older versions will just work without Riru. You can try https://github.com/kdrag0n/safetynet-fix/releases/download/v1.2.0/safetynet-fix-v1.2.0.zip
Thanks
HemanthJabalpuri said:
Ah, got the culprit.
Magisk hide and Official Modules Repo are no longer part of Magisk from the developer.
To get those back, we can use older version of Magisk.
I have updated the Magisk apk link for UI 2.0. Uninstall Magisk by choosing 'Uninstall Magisk' in main screen and root again with the updated link.
Also, Universal SafetyNet fix older versions will just work without Riru. You can try https://github.com/kdrag0n/safetynet-fix/releases/download/v1.2.0/safetynet-fix-v1.2.0.zip
Thanks
Click to expand...
Click to collapse
magisk worked but i couldn't pass CTSprofile so i installed safetynet fix v2.1.0 and Riru, now everything's fine.. thank you again Sir
i have a question. The vbmeta is "empty" or you extract it from fastboot file?
GoldenEye17 said:
i have a question. The vbmeta is "empty" or you extract it from fastboot file?
Click to expand...
Click to collapse
I took that from our device stock rom ozip
I bought a cracked version of the 4/64 version of Xiaomi Qin F21 Pro unlocked bootloader, rooted, and with preinstalled fully working Google Playstore and Play services running on the official firmware 2.0.8.
But lately there's a very nice update development from 4PDA website for the device! It took me a while before I made it work and a lot of trial and error.
I will make a full detailed easy to follow step by step tutorials on how to do it with all the links for the files required.
The results will be:
A fully converted v1.1.1 custom firmware without the chinese apps
TWRP Recovery
fully rooted
certified playstore and google services fully working
THE PROCESS COULD ALSO UNBRICKED THE PHONE
Requirements:
PC
UNLOCKED BOOTLOADER Xiaomi Qin F21 Pro (MTK soc) V1.0+ V2.0+ (4/64gb ONLY)
Files (will be provided)
working brain
CREDITS:
4PDA FORUMS device thread
Telegram Group
DEVS for the unlock bootloader tool
DEVS for the Custom Firmware
DEVS for porting TWRP
testers
many more I probably forgot
...........TUTORIALS SOON
TUTORIAL UPDATE!
MY DEVICE IS 4/64 with unlocked bootloader
Unofficial Qin F21 Pro (MTK chipset) firmware, version 1.1.1 multilanguage.
Thanks to @redsat, @gaguga and the whole 4pda community.
Install at your own risk and responsibility.
For testing purposes only, will be updated or changed if necessary.
Use SP flash tool for flashing, bootloader should be unlocked on the phone (via @mlgmxyysd tool or Ubuntu boot image). Having the full own ROM dump is highly recommended in advance.
Changes:
-Removed chinese applications
-Decrypted data partition
-APK installer with no restrictions
-System partitions are writable
TWRP recovery 3.6.0_11-0 is added
(In TWRP the phone memory is accessible via path: /data/media/0)
WARNING: FLASHING THE FIRMWARE WILL WIPE EVERYTHING! I SUGGEST BACKUP IMPORTANT FILES BEFORE DOING THIS. I WILL NOT BE HELD RESPONSIBLE IF YOUR PHONE DONT BOOT, SOFT/HARD BRICKED! THIS TUTORIAL IS TO DO AT YOUR OWN RISK!
ALL FILES REQUIRED FOR WINDOWS https://www.mediafire.com/file/tl8hv77gl0vo6sd/qin_f21_pro_mtk.zip/file
download and extract zip
extract "F21PRO_1.1.1 (2).zip" (the firmware)
extract "SP_Flash_Tool_V5.zip" (flash tool)
install drivers
open "flash_tool.exe"
select scatter file from the firmware folder
click download
turn phone off
hold back button then plug usb cable to pc. It should start flashing
after download complete, unplug then boot to TWRP then reset factory
Congrats! You now have chinese free apps firmware with TWRP Installed
If it wont boot "DEVICE ENCRYPTED", just go to TWRP and FORMAT DATA then reboot (it should boot to system now)
transfer "boot_2.img" phone or transfer it to a USB Flashdrive (more easier to locate) (FOR 3/32 VARIANTS TRY TO USE THIS BOOT IMAGE BOOT.IMG 3/32)
boot to TWRP once again
go to device path /data/media/0 or USB storage path using OTG
FLASH IMAGE "boot_2.img" to boot partition to fix the device twrp path to /sdcard (IMPORTANT! boot is an IMAGE FILE not ZIP FILE. by default, TWRP is set to check for zip file and will n0t se IMAGE FILES in the directories. YOU NEED TO TAP THE INSTAL IMAGE BUTTON so image files will appear)
reboot and proceed to installing ROOT and Google services
HOW TO BOOT TWRP:
* + heart button (upper left) + power on. once douqin logo appears press up button + power on immediately. TWRP first boot is in Russian language. just change it to english change twrp language
HOW TO ROOT + GAPPS with playstore certified + fix keypad annoying issue
transfer all the app APK from the "APK" folder youve download
install everything (QinPad be a more stable keypad input)
open gboard and enabled both gboard and QinPad (this should give you a quick switch of input in the notification bar everytime you will type something)
open MAgisk app and update the apps to 22.1. phone reboots (DO NOT UPDATE TO VERSION 24.3)
Open magisk again then Install Magisk > Select a patch file > choose "boot_2.img" in your directory (path where you transfer it)
transfer "open_gapps-arm64-11.0-pico-20211217.zip" to device
boot to TWRP
FLASH IMAGE "boot_2.img_patch" IN THE BOOT PARTITION. then reboot. should be found in download path in TWRP
go TWRP again and flash "open_gapps-arm64-11.0-pico-20211217.zip"
reboot > SYSTEM
you will see playstore. you will have an annoying message "device isnt playstore certified" just ignore it
open MAGISK app go to settings and enable MAGISK HIDE, search module and install "Busybox for NDK" then reboot
open MAGISK app, search module and install "MagiskHide Props Config" then reboot
open Terminal emulator app
type "su" enter (grant permission)
type "props" enter
type "1" enter
type "F" enter
type "30" enter
type "25" enter
type "2" enter
type "y" enter
type "y" enter (phone reboots)
after reboot wait gapps to update (around 5-10 mins) then sign in to playstore
you've now enter Playstore
go to playstore settings > about > click update playstore
wait for it to update the version and keep checking in playstore settings > about > IF DEVICE IS CERTIFIED
If the updated playstore still said " DEVICE IS NOT CERTIFIED", proceed to manual
install device id apps from playstore and copy your GSF ID
register it manually here > https://www.google.com/android/uncertified/?pli=1
go settings ~ apps and look for playstore and play services and clear data. reboot phone and Playstore should be certified!
Congats! your phone now is rooted with twrp, no more chinese apps, and with fully working google services. I suggest perform a TWRP backup and store it somewhere safe for future use.
HOW TO FIX NO/DELAYED INSTALLED APPS NOTIFICATIONS
Thanks for JawadEly for the info, it works!
1. Install all your apps
2. Install terminal emulator app and system app remover app from playstore (this will give you the apk path you want to systemize)
3. open magisk, search and intall "APP SYSTEMIZER" module then reboot.
4. open terminal emulator app
6. type "su" and grant the permission
7. type "systemize"
8. You need to set Selinux = TRUE by choosing "s"
9. once its set to TRUE, you can now systemize any app provided you know the apk path of the apps installed.
10. enter "3", here is where you put the apk path of the app you want to systemize
11. to get the apk path of installed app open the "system app remover" app you installed.
12. go to user apps and LONG PRESS an app you wish to systemize.
13. copy the apk path then go to terminal emulator and paste it. Type "1" to confirm.
14. Go to settings > apps list > clear storage of that app you transfer as system app
15. done! just repeat the proceedure for each app you wish to fix the notifications.
BEWARE! Be careful using system app remover. Don't uninstall system apps required for the android system. You might end up in a bootloop. This app is also used to remove bloatwares of OEM firmwares.
I made this tutorial as DETAILED and as EASY TO FOLLOW as posible. Credits to 4pda community group and for individuals who contributed that made all this posible. Sorry if my English bad. Not my native language. If you lke the tutorial, you can buy me a beer.
paypal > [email protected]
gcash > 09912293147
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello, I have an F21PRO I am looking for a custom firmware, saw your tutorial, but only saw the directory, there is no specific tutorial, so when you update, please notify me. Thank you，I am using a translator to talk to you, please understand
keep us posted, looking forward to this!
really looking forward to this, mostly about having custom recovery for this phone!
Any updates for that? It's been 2 months since this was posted.
sorry just got too busy but here it is now! enjoy
Can I change qinpad language? or duoqin IME language? I want to change Korean, but I can't find the way.
Thanks a bunch bro, Followed all the steps and somehow I managed to get it working. M a d
Cheers!
thank you, will this recognise uk area codes?
please help I can not install qinpad, it says app not installed?
Jbazt_katuforzs said:
UPDATE! MY DEVICE IS 4/64 with unlocked bootloader (must)
Unofficial Qin F21 Pro (MTK chipset) firmware, version 1.1.1 multilanguage.
Thanks to @redsat, @gaguga and the whole 4pda community.
Install at your own risk and responsibility.
For testing purposes only, will be updated or changed if necessary.
Use SP flash tool for flashing, bootloader should be unlocked on the phone (via @mlgmxyysd tool or Ubuntu boot image). Having the full own ROM dump is highly recommended in advance.
Changes:
-Removed chinese applications
-Decrypted data partition
-APK installer with no restrictions
-System partitions are writable
TWRP recovery 3.6.0_11-0 is added
(In TWRP the phone memory is accessible via path: /data/media/0)
Separate TWRP as boot.img attached as well (thanks to 4pda comrade @yurxxl)
Also you can install Magisk and GAPPS as zip packages via TWRP.
WARNING: FLASHING THE FIRMWARE WILL WIPE EVERYTHING! I SUGGEST BACKUP IMPORTANT FILES BEFORE DOING THIS
ALL FILES NEEDED for WINDOWS https://www.mediafire.com/file/tl8hv77gl0vo6sd/qin_f21_pro_mtk.zip/file
download and extract zip
extract "F21PRO_1.1.1 (2).zip" (the firmware)
extract "SP_Flash_Tool_V5.zip" (flash tool)
install drivers
open "flash_tool.exe"
select scatter file from the firmware folder
click download
turn phone off
hold back button then plug usb cable to pc. It should start flashing
after download complete, unplug then boot to TWRP then reset factory
Congrats! You now have chinese free apps firmware with TWRP Installed
If it wont boot "DEVICE ENCRYPTED", just go to TWRP and FORMAT DATA then reboot (it should boot to system now)
transfer "boot_2.img" phone or transfer it to a USB Flashdrive (more easier to locate)
boot to TWRP once again
go to device path /data/media/0 or USB storage path using OTG
FLASH IMAGE "boot_2.img" to boot partition to fix the device twrp path to /sdcard
reboot and proceed to installing ROOT and Google services
HOW TO BOOT TWRP:
* + heart button (upper left) + power on. once douqin logo appears press up button + power on immediately. TWRP first boot is in Russian language. just change it to english change twrp language
HOW TO ROOT + GAPPS with playstore certified + fix keypad annoying issue
transfer all the app APK from the "APK" folder youve download
install everything (QinPad be a more stable keypad input)
open gboard and enabled both gboard and QinPad (this should give you a quick switch of input in the notification bar everytime you will type something)
open MAgisk app and update the apps to 22.1. phone reboots (DO NOT UPDATE TO VERSION 24.3)
Open magisk again then Install Magisk > Select a patch file > choose "boot_2.img" in your directory
transfer "open_gapps-arm64-11.0-pico-20211217.zip" to device
boot to TWRP
FLASH IMAGE "boot_2.img_patch" should be in download path
flash "open_gapps-arm64-11.0-pico-20211217.zip"
reboot THE CURRENT SLOT
you will see playstore. you will have an annoying message "device isnt playstore certified" just ignore it
open MAGISK app go to settings and enable MAGISK HIDE, search module and install "Busybox for NDK" then reboot
open MAGISK app, search module and install "MagiskHide Props Config" then reboot
open Terminal emulator app
type "su" enter (grant permission)
type "props" enter
type "1" enter
type "F" enter
type "30"
type "25"
type "2"
type "y" enter
type "y" enter (phone reboots)
after reboot wait gapps to update (around 5-10 mins) then sign in to playstore
you've now enter Playstore
go to playstore settings > about > click update playstore
wait for it to update the version and keep checking in playstore settings > about > IF DEVICE IS CERTIFIED
If the updated playstore still said " DEVICE IS NOT CERTIFIED", proceed to manual
install device id apps from playstore and copy you GSF ID
manual register it here > https://www.google.com/android/uncertified/?pli=1
go settings ~ apps and look for playstore and play services and clear data. reboot phone and Playstore should be certified!
Congats! your phone now is rooted with twrp, no more chinese apps, and with fully working google services. I suggest perform a TWRP backup and store it somewhere safe for future use.
I made this tutorial as DETAILED and as EASY TO FOLLOW as posible. Credits to 4pda community group and for individuals who contributed to made this posible. Sorry if my English bad. Not my native language. If you lke the tutorial, you can buy me a beer. paypal > [email protected]
Click to expand...
Click to collapse
Thank you for this! I managed to get everything installed and running. Will be testing it out in the meantime! Thanks again bro! No more bloatware!
If you have a 32GB model, when using Flash Tool, uncheck the tickbox saying "userdata" as leaving this on will completely brick your device.
jason24589 said:
If you have a 32GB model, when using Flash Tool, uncheck the tickbox saying "userdata" as leaving this on will completely brick your device.
Click to expand...
Click to collapse
thanks for the heads up. but can you confirm too that it can still be re-flash again by holding back button if it got bricked?
Jbazt_katuforzs said:
thanks for the heads up. but can you confirm too that it can still be re-flash again by holding back button if it got bricked?
Click to expand...
Click to collapse
I'm not sure. I found that warning from a Telegram group 3 days ago as someone already bricked their 32GB model when they flashed it with userdata option left being checked
harahaum1 said:
Can I change qinpad language? or duoqin IME language? I want to change Korean, but I can't find the way.
Click to expand...
Click to collapse
I'd suggest to use Traditional T9 IME app. Not sure if this supports Korean as most of the languages supports English, French, Russian, etc.
jason24589 said:
I'm not sure. I found that warning from a Telegram group 3 days ago as someone already bricked their 32GB model when they flashed it with userdata option left being checked
Click to expand...
Click to collapse
i think its in the buildprop. anyways 3/32gb variants, DONT TRY THIS TO YOUR PHONE. TUTORIAL ONLY FOR 4/64.
Pixel launcher. Nice alternative launcher i confirmed works! Install using magisk
https://forum.xda-developers.com/t/magisk-pixel-launcher-for-android-11.4213619/
hello, I can't extract "F21PRO_1.1.1 (2).zip" (the firmware). the zip is corrupted. can you re-upload the firmware please?
thanx
Chabanda said:
hello, I can't extract "F21PRO_1.1.1 (2).zip" (the firmware). the zip is corrupted. can you re-upload the firmware please?
thanx
Click to expand...
Click to collapse
Try to use 7zip
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.