Develop Bugs

Google apps on Motorola Xoom running cm-10.1-20131007

Last week I brought a Morotola Xoom on ebay, it had 4.0 installed but I wasn't that impressed with it having got used to stock 4.1 on my phone.
I came across the great guide at http://forum.xda-developers.com/showthread.php?t=1477024 and used this along with http://wiki.cyanogenmod.org/w/Install_CM_for_wingray to unlock, root and install cyanogenmod 10.1 on it.
It was mostly a stress free install (although I managed to miss renaming the stock files that the post says causes Stock Recovery to overwrite CWM but it seems to still work OK.
My issue now is that I don't seem to have all the Google apps. It has gmail but not maps or market. I assumed that gmail isn't part of cyanogenmod so the 'gapps-jb-20130812-signed' file has installed (I think that file is the correct version).
It's not too clear from the instructions they read to me that you install the main CM zip and then Google apps without needing to re-boot in between, is this correct? I've tried a completely fresh install and also wiping the cache partition but no luck. But have not tried re-booting after installing the CM then installing Google Apps in a second boot, worth a try I guess.
Am I just making a simple noob error here? Thanks in advance for any advice.

A update, I've just tried formatting and re-installing again, only this time allowing a reboot into android prior to trying to install Google apps. One thing I've learnt is that the gmail app is part of the base install. Installing google apps appears to go ok but upon rebooting they aren't there. My next test is to try yet another clean install and an old version of gapps (gapps-jb-20120719-signed).
Chris

Motorola Xoom issues with 'Motorola fast-boot' replacing 'clockwork-recovery'
A further update... It's not gone well, it'd defaulted back to Motorola fast-boot protocol support not clockwork-recovery (after me initially forgetting to rename the files even though it's worked for many re-boots until now).
I've then tried to run back through the guidance at http://forum.xda-developers.com/showthread.php?t=1477024 to re-unlock and re-install clockwork-recovery.
However, it's not gone great, for a start it took me a while to work out to turn on usb debugging in Cyanogenmod 10.1 (see http://wiki.cyanogenmod.org/w/Doc:_developer_options) so adb can see it. After a couple of hours of messing about I've managed to get clockwork-recovery back on it.
However when booted into clockwork-recovery I got a 'error: device not found' from 'adb remount'. So I was not able to rename the files to prevent the Motorola fast-boot overwrite of clockwork-recovery eventually happening. When android is booted and it isn't in recovery I get a 'remount failed: Operation not permitted' response to adb remount. Is there another way to rename '/system/recovery-from-boot.p' and '/system/etc/install-recovery.sh' without having to do it do it at that first boot, it is interesting that clockwork-recovery survived several boots.
I've decided not to risk the install of a potentially unsupported zip of Google apps when my recovery situation isn't solid.

Hmm a fun morning, I've lost times now at how many times I've had to reroot it. I've managed to get the Google play store apk and have tried using that (in addition to installing the gapps zip) it is loading but complaining of no network connection.
With regard to renaming the files ' /system/recovery-from-boot.p' and 'system/etc/install-recovery.sh' I've not managed this, when the tablet reboots into clockwork recordery its connection with adb is dropped. I've also tried doing them in terminal when booted and they don't seem to be there.
There doesn't seem to be anyone else commenting on this so I'll just plod along blindly :silly:
c_dunne said:
A further update... It's not gone well, it'd defaulted back to Motorola fast-boot protocol support not clockwork-recovery (after me initially forgetting to rename the files even though it's worked for many re-boots until now).
I've then tried to run back through the guidance at http://forum.xda-developers.com/showthread.php?t=1477024 to re-unlock and re-install clockwork-recovery.
However, it's not gone great, for a start it took me a while to work out to turn on usb debugging in Cyanogenmod 10.1 (see http://wiki.cyanogenmod.org/w/Doc:_developer_options) so adb can see it. After a couple of hours of messing about I've managed to get clockwork-recovery back on it.
However when booted into clockwork-recovery I got a 'error: device not found' from 'adb remount'. So I was not able to rename the files to prevent the Motorola fast-boot overwrite of clockwork-recovery eventually happening. When android is booted and it isn't in recovery I get a 'remount failed: Operation not permitted' response to adb remount. Is there another way to rename '/system/recovery-from-boot.p' and '/system/etc/install-recovery.sh' without having to do it do it at that first boot, it is interesting that clockwork-recovery survived several boots.
I've decided not to risk the install of a potentially unsupported zip of Google apps when my recovery situation isn't solid.
Click to expand...
Click to collapse

Well, I'm with this problem too. I'm trying to solve this problem by myself, but no success at all. It do FC on google play every time it try to update. Every Google App (besides GMail) is doing FC with this CM build.
I tried to:
- Reinstall google apps
- Install another version (compatible with Android 4.2.2)
- Do the wipes again
- Install google play from an outside source (it doen't come with it).
But no success.
Any ideas?

miraidensetsu sorry for my delay in responding, I'm surprised that no other responses to this tread have been made. An update I've now resorted back to the stable release cm-10.0.0. Given it's nearly a year old I'd hope there'll be a stable release of 4.2 out soon.
Initially I had issues with the stock keyboard crashing all the time. But after searching about this I've installed the Google keyboard app and disabled the stock one.

[Q] Play Store

I have the Nokia N1. Is it there any way to install the Google Play Store (and Play Services) in it?

cisoprogressivo said:
I have the Nokia N1. Is it there any way to install the Google Play Store (and Play Services) in it?
Click to expand...
Click to collapse
haven't found a method yet so far,just wait till international version rom release

Same here. Couldn't find a way to install Play Store yet >_<

The only way for now, is either to wait for a miracle on a root method on the tablet, or wait for the official international release for their ROM.
My N1 is back into its box, as it's pretty much useless now, since over 80% of the apps these days requires Google Service Framework.

It's fine to be a MP4 player now.Install MX player, some comics reader, and some China online games. Hope official GSF come out asap.

LeignHan said:
haven't found a method yet so far
Code:
,just wait till international version rom release[/QUOTE]
I tried several times also. I noticed the model at GMC was had the chinese version info on the back of the device but was running Play Store. Tried a few versions but it exited after a breif pinwheel. The N1 device is listed on googles accepted device list pdf with no specific model information. Maybe the next version of Play store ? IDK how it works. Anyway device is not useless for me - I found most apps I require on Amazon Store or APKs. The Nokia zlaunch is excellent and waking up with screen double touch I like also. I owned apple ipad mini and prefer the build of this. Feels very sturdy - well built.
Click to expand...
Click to collapse

I also got my N1 yesterday. I tried to install the Play Store, yet no success. I also tried the method used to install it on Xiaomi devices, but the offered Play Store there is not compatible with 5.0 (permission READ_LOGS seems to be required, thus the apps crash)
I thought also about flashing the PA Gapps via the "stock" recovery. I tried following:
- Put gapps zip in /mnt/sdcard/ and renamed it to update.zip
- reboot into recovery using adb (adb works fine so far)
I hoped that the recovery would flash the zip as an update, but the error screen appeared. Knows somebody if the zip name and location are correct?

crys_ said:
I also got my N1 yesterday. I tried to install the Play Store, yet no success. I also tried the method used to install it on Xiaomi devices, but the offered Play Store there is not compatible with 5.0 (permission READ_LOGS seems to be required, thus the apps crash)
I thought also about flashing the PA Gapps via the "stock" recovery. I tried following:
- Put gapps zip in /mnt/sdcard/ and renamed it to update.zip
- reboot into recovery using adb (adb works fine so far)
I hoped that the recovery would flash the zip as an update, but the error screen appeared. Knows somebody if the zip name and location are correct?
Click to expand...
Click to collapse
I think the GAPPS zip file is not signed officially. Unless 3rd party recovery is installed, the un-signed gapps is no way to get into N1.

How did you get adb working? It doesnt seem to work for me with the Google USB drivers
EDIT: Nvm I figured it out, I needed to manually install the Google USB driver

Hello,
Has anyone of you checked if fastboot is available? Is the bootloader finally locked or not?
What have you actually checked/tested? At least could save some other guy sometime avoiding non-working retries ...
---------- Post added at 09:29 PM ---------- Previous post was at 09:19 PM ----------
Just in case it gives someone some idea. Latest nexus player came with a 64bit Atom. Could gapps be obtained from there? Just in case architecture is the problem ...

inakipaz said:
What have you actually checked/tested?
Click to expand...
Click to collapse
Okay, so I am far from an expert, here's what I found:
1. You can boot into fastboot by pressing power + vol. down when the device is off. See the attachment how it looks. I've tried a few oem commands: fastboot oem unlock, fastboot oem ?, fastboot oem command list, they don't work.
2. AFAIK there is no root method. I've tried Kingo root, others tried Root Genius, both fail to root it. Looking at chinese forums with Google translate looks like they're waiting for an international ROM with Google stuff to flash.
3. You can install Google play services. It will just crash each time something tries to use it. I've made a sample app that tries to use it, I see these exceptions in Logcat:
Code:
java.lang.SecurityException: attempting to read gservices without permission: Neither user 10060 nor current process has com.google.android.providers.gsf.permission.READ_GSERVICES.
java.lang.RuntimeException: Unable to start activity ComponentInfo{com.google.android.gms/com.google.android.gms.app.settings.GoogleSettingsActivity}: java.lang.SecurityException: caller uid 10060 lacks any of android.permission.INTERACT_ACROSS_USERS
java.lang.RuntimeException: Unable to create service com.google.android.gms.gcm.GcmService: java.lang.SecurityException: attempting to read gservices without permission: Neither user 10060 nor current process has com.google.android.providers.gsf.permission.READ_GSERVICES.
If you are interested in anything else I can try it (unless its some dangerous stuff)

Thanks syddd,
As you say i would not flash anything. I'm not an expert either.
In other ocassions a command useful to me was to boot (not flash) into custom recovery. For recovery I would try one working on similar hardware ... And from there, install superuser to root. If it is simply a clean android, that should do it.
As I said previously on other posts, I will start doing this works on mine once I got one by mid-april.
Remember, It is always important to backup current status!

As I first step I will test something like it appears on this guide for the nexus 7:
http://forum.xda-developers.com/showthread.php?t=2415668
Adapting things to similar hardware ...
Trying fastboot boot with custom recovery to know if the device is locked. If it is it should not allow this operation.
Something like method 1 in this other guide
http://forum.xda-developers.com/nexus-player/orig-development/root-google-adt-1-android-tv-t2962905
Guide on how to port CWM
http://xda-university.com/as-a-developer/porting-clockworkmod-recovery-to-a-new-device
Similar guide on twrp
http://forum.xda-developers.com/showthread.php?p=32965365#post32965365

Thanks for the guide!
I tried to follow the clockworkmod recovery one, but could not dump the boot partition. I am thinking of extracting it from the official ROM, I just dont know where those are... We could find out by snooping on the connection while the device gets a new update.
EDIT: Also "fastboot boot test.img" results in:
C:\>fastboot boot test.img
creating boot image...
creating boot image - 2048 bytes
downloading 'boot.img'...
OKAY [ 2.521s]
BUT the device does not reboot and I see the following for a split second:
"boot command stubbed in this platform!"
where test.img is just an emty file. Does this mean that the boolloader is locked?
EDIT2: I've managed to get 2 update files by clicking the "check for update" button and snooping with Wireshark what happens. It makes a POST request to http://www.fc811.com/OTA/GetOTAFirm...&fw_id=A5CN30B&serial_no=XXXXXXXX&version=1.0 , where serial_no is the serial of your device (found in the about menu) and fw_id is your current firmware. I could download 2 firmwares with this method A5CN30B and A5CN315B. Both are minor updates, if someone has the fw version from the initial release it would be useful because we could get the 5.0.2 update.
I've put these in my dropbox: https://dl.dropboxusercontent.com/u/9186429/nokia_n1/A5CN30B_update.zip https://dl.dropboxusercontent.com/u/9186429/nokia_n1/A5CN315_update.zip
Both have a droidboot.img file inside them, which is a RAMdisk boot image.

Really really nice advances!!
Thanks! You`ve been able to download I think a valid ROM for the device! Now it should be explored ...
And yes, I suppose the boot is locked which means it will not be easy to make changes.
We will need more expert hands to guide on what's next ...
In my opinion I would try to open the Image you have downloaded.

I've opened it, as you can see they are simple .zip files. But they are not ROMs. Part of them are Android patchfiles which contain just binary diffs. The bootloader is a RAMDisk which can be opened and patched with the methods you linked. The big question is whether they can be installed or not.
EDIT: see my other post, one of the older updates contains a full system image

I've been using for about 2 months. And had it repaired once, 'coz of screen issues. They sent me a new one. Very nice! Just the color changed from silver, originally, to grey, otherwise is fine.
The battery is good. It could last longer, if very much, when compared with N7.2013.LTE. The new Intel Atom looks very promising. But as you all know, there's no google play store. So I left it sleeping in the drawer.

New Play Store APK available. Just in case can anyone test it on the device?
http://forum.xda-developers.com/showthread.php?t=1996995
Hope it now works ...

It does not work.
It installs normally, but closes when I open it, just like previous versions. The problem is that play store/Google play services need some special permissions that need root. So no root = no play store.

Just need to wait for the international ROM to leak for this thing. The problem is Nokia is taking it's sweet time to release this thing anywhere else....

Downloadling applications with custom Rom

So I am pretty new to this, but here goes....
About a month ago I got some help from a friend and downloaded lineage OS 15.1 to my Lenovo p2a42 device. Very happy with everything, until yesterday when the phone began to vibrate and then proceed to shut down with a blue indicator light showing. After some fiddling and attempts to get the latest update of lineage, I got stuck in my first boot loop. After all my various attempts to solve the problem, I decided to do a clean wipe and reinstall lineage. Which I've done successfully I believe, no crashes yet. What I am having trouble with now is remembering how to download the first applications since I don't have the Gsuite or Gapps downloaded. I remember my friend mentioning a problem with the stock file manager for lineage and I believe that is one of the first applications we downloaded along with the apk pure app store.
If anyone can help this newbie figure out how to download the apk mirror to my device without an appstore, I would appreciate it.
>maybe the answer is to download to my laptop first and then use adb to flash it to my device?
Thanks for the help!!

If you want to have Google apps on your phone, search for Open GApps and download for ARM64 devices (nano package is recommended). Then flash it alongside LOS in TWRP. You will have Google Play Store installed.
But, if you only want APKPure store then you must download the APK from their website (either via computer then move it to your phone, or by using default LOS browser). Navigate to your downloaded APK using file manager and open it, you will have a prompt to install it or not. That's pretty much it though.

XDAquareis said:
If you want to have Google apps on your phone, search for Open GApps and download for ARM64 devices (nano package is recommended). Then flash it alongside LOS in TWRP. You will have Google Play Store installed.
But, if you only want APKPure store then you must download the APK from their website (either via computer then move it to your phone, or by using default LOS browser). Navigate to your downloaded APK using file manager and open it, you will have a prompt to install it or not. That's pretty much it though.
Click to expand...
Click to collapse
I downloaded apk pure directly on my mobile from the website (not interested in GApps). It opens in the LOS default file manager and there are basically no options to run it. I think this is because the root may be disabled, my boot loader is unlocked, but it says adb only in my developer options settings. I am new to using adb to flash an apk. I was able to flash lineage, but not sure how to install the apk. For instance, should my phone be on when I enter command install xxx.apk or should it be in recovery mode or boot mode? I tried once already and the apk install failed, not sure what I am doing wrong here. Thanks for the response above.

LineageP2newb said:
I downloaded apk pure directly on my mobile from the website (not interested in GApps). It opens in the LOS default file manager and there are basically no options to run it. I think this is because the root may be disabled, my boot loader is unlocked, but it says adb only in my developer options settings. I am new to using adb to flash an apk. I was able to flash lineage, but not sure how to install the apk. For instance, should my phone be on when I enter command install xxx.apk or should it be in recovery mode or boot mode? I tried once already and the apk install failed, not sure what I am doing wrong here. Thanks for the response above.
Click to expand...
Click to collapse
Answered my own question. Was able to download a file manager using adb, this allowed me download apk mirror.

How To Guide [Guide] Xiaomi Mi Pad 5 MIUI12/13 ROOT Step-by-step - Pass SafetyNet, Widevine L1

Everything you do, you do at your own risk. I'm not responsible for all damages, this can also lead to loss of warranty.
Hi,
Probably many of you know how to do a Magisk install without TWRP, but this guide is for people who don't know and don't want to mess things up.
I will try to show you step by step how to do it.
Many thanks to:
kdrag0n
topjohnwu
Leave them a nice feedback
!!! Before we start make sure your device is unlocked, if you don't know how to do it below is link to official Xiaomi guide !!!
https://c.mi.com/thread-2262302-1-0.html
Requirement
Xiaomi Mi Flash ver. =>3-14-0 - Needed to install all adb drivers Download
ADB & Fastboot tools - Could be the one built into Mi Flash tool I'll use this to make it simple
Magisk =>24.2 - This software is base of our rooting process Download
SafetyNet Fix => 2.2.1 (Zygisk) - Needed to backdoor SafetyNet fail check, at the moment it is only working method for Mi Pad 5 Download Make sure you download the Zygisk version!
Boot.img - You can download from official MIUI website full flashable rom and separate boot.img file from there, or use my if your Miui version is China 13.0.5, EEA 13.0.3, Global 13.0.1
China 13.0.5​EEA 13.0.3​Global 13.0.1​​​Installation
To make it easier, Green color mean what you need to do on Tablet, Orange on PC
Unzip Mi Flash tool
Open folder and run XiaoMiFlash.exe, if window "Driver" won't pop-up click on the Driver tab and then "Install" button and close all windows.
Connect your tablet to computer, when your tablet ask how you want use USB, choose File Transfer/Android Auto
Copy to internal storage Magisk-v****.apk, safetynet-fix-v****.zip and boot.img
Open File Manager on your tablet find a folder where you copied all files, and install Magisk
Open Magisk app, and click on Install in section Magisk, then select "Select and Path a File", after that find your boot.img file and click on it
Click "LET'S GO" button on the right side and wait until process will be finished
On your computer in the tablet's storage window, go to the file specified in the application probably /Download/magisk_patched-*****
Copy this file to a subfolder of Mi Flash on your computer, exactly to MiFlash2020-3-14-0\Source\ThirdParty\Google\Android and change the name of this file to boot.img
Open PowerShell/Windows Terminal in this folder (Hold Shift + Right click -> Open PowerShell window here)
Make sure your tablet have enabled USB debugging in Developer options Setting -> Additional settings -> Developer options -> USB debugging
Turn off your tablet, then hold down Power and VOL- until the screen lights up, then release power button, if Fastboot appears, everything went fine
Go back to your Terminal window and type to check if your computer see your tablet
Code:
./fastboot.exe devices
If you see answer "******** fastboot" it mean there is communication between PC and Tablet
Next type this command to flash patched boot image
Code:
./fastboot.exe flash boot boot.img
Next type this command to reboot your device
Code:
./fastboot.exe reboot
Restart can take a longer time than normal
Open Magisk app and check status of Magisk, if you see for exaple "Installed 24.2 (24200)" everything went fine
Open Settings in right corner of app and in section App click on Hide the Magisk app then type name for hidden app, it will ask to install new app so do it
Open again Magisk app and open Settings in section Magisk enable Zygisk (Beta) and Enforce DenyList
Click on Configure DenyList than click on three dots in right corner and uncheck Show system apps
Search for all the apps in the list below and check them. It is important to click on their name to see all modules, once you have done this click on the box to activate all of them
Code:
Google
Google Assistant (I have two)
Google Pay
Google Play services
Google Play Store
After that reboot your tablet, and open again Magisk app
On the bottom click on Modules
Click on Install from storage button and find file safetynet-fix-v*******.zip, than click on it
After that reboot your device one more time
After reboot open Android Settings go to Apps and Unhide system services than find and clear all data of Google Play services and Google Play Store
Reboot tablet last time
If you have reached this point it means that everything has gone correctly, probably for about 3 hours you will still not be able to install Netflix and some banking applications but after this time everything will be back to normal, this is because Google's servers have detected that Magisk has been installed but that the application has been changed and Zygisk has been enabled so at the next check it notices that everything is Ok and gives access back.
Quick explaination what happend here:
Magisk has been installed and device is Rooted
The application has been changed and hidden
Zygisk has been activated and hidden from Google services
SafetyNet-fix was installed, which restores the functionality of SafetyNet and Widevine L1, which is blocked after the installation of Magisk and unlocked Bootloader

Hello,
(I use google translate).
Thanks for your method. Before using it, I would like to ask you a few questions.
I have already rooted a few devices (mipad 1, mi phone, htc...) with my macbook and twrp.
The adb files are already installed on my mac.
1) once the pad 5 is rooted, should I, like on my phone, patch the new boot.img file with each update?
2) Could I install the twrp application afterwards to be able to do a complete backup of the system and possibly install a version of lineageos later?
3) Is there a version of miflash unlock tool for mac os x?
4) Should I register or register on the xioami site before unlocking the boot?
Thank you in advance for your method and your answers.
Nux01

Nux01 said:
Hello,
(I use google translate).
Thanks for your method. Before using it, I would like to ask you a few questions.
I have already rooted a few devices (mipad 1, mi phone, htc...) with my macbook and twrp.
The adb files are already installed on my mac.
1) once the pad 5 is rooted, should I, like on my phone, patch the new boot.img file with each update?
2) Could I install the twrp application afterwards to be able to do a complete backup of the system and possibly install a version of lineageos later?
3) Is there a version of miflash unlock tool for mac os x?
4) Should I register or register on the xioami site before unlocking the boot?
Thank you in advance for your method and your answers.
Nux01
Click to expand...
Click to collapse
Hi Nux01,
1. Unfortunately yes, TWRP isn't supported for Pad 5 yet.
2. It won't work, TWRP app is only making a request to TWRP custom recovery, until it doesn't exist you can't even install custom ROM
3. It is, but i didn't test it yet on Pad 5, and I don't know if it will work with new decides because last release is from 20.07.2020.
https://github.com/francescotescari/XiaoMiToolV2/releases
4. Yes, you need Xiaomi account, also your device has to be logged in, and registered to unlock, Xiaomi made complete guide how to do this, link is on the top of this post.

Hello,
Thank you for your quick reply.
The latest version of Mitool does not work. On the other hand, with regard to version 20.7.21, it's OK.
What does it mean: "I do not know if it will work with new decides".
And to unlock the bootloader, I have to use the Xiaomitool V2 application?
Thanks again.
NUX01

Nux01 said:
Hello,
Thank you for your quick reply.
The latest version of Mitool does not work. On the other hand, with regard to version 20.7.21, it's OK.
What does it mean: "I do not know if it will work with new decides".
And to unlock the bootloader, I have to use the Xiaomitool V2 application?
Thanks again.
NUX01
Click to expand...
Click to collapse
I mean it's quite old release so it may not work with current unlock bootloader process on new devices like a Xiaomi 12, Xiaomi Pad 5 etc. I can't promise it won't brick your device, only confirmed method is by official Xiaomi tool.

Thank you
I'll wait a little bit before rooting my tablet.
Have a nice day.

Followed the instruction, worked like a charm. Although I had unknown "chinese sings" errors with the driver install it worked. By the way there is a newer version of the flashing tool.
Thanks for the effort of writing this down!

Hello,
I just managed to unlock the bootloader of my tablet "Pad 5".
I tried under Mac and Linux with Xiaomitool V2 without success (error 20036 and 20045).
I also tried with VirtualBox who did not recognize the tablet.
I succeeded with VMware and Windows 7 by testing different drivers and it worked.
I just root the tablet with Magisk.
On the other hand, is there the equivalent of TWRP to make a complete system backup. Apart from Titanium and MyBackup.
Thanks for your help.

thanks dude.
didn't try this yet, just wondering.
can't i just flash recovery and then flash magisk.apk?
thanks

Can i update ota to 13.0.2 after rooted? Just update and root again?

Cpanel10x said:
Can i update ota to 13.0.2 after rooted? Just update and root again?
Click to expand...
Click to collapse
You can update, but after that you need root again but with boot.img from 13.0.2

How to get the boot.img 13.0.2? I checked the 3GB Firmware and only found vendor_boot.img. Is it the same thing?

Never mind. I got the boot.img from here: https://miuirom.org/tablets/xiaomi-pad-5

Thomas Brown 99 said:
Never mind. I got the boot.img from here: https://miuirom.org/tablets/xiaomi-pad-5
Click to expand...
Click to collapse
boot.img for miui global 13.0.3(RKXINXM) isn't available there. Plz help...

Thanks for this awesome guide. Do you have some suggest about the magisk modules to install?

thanks, it just worked perfectly and your step by step guide is very handy and helpful. thanks so so much.

vjsaini00 said:
boot.img for miui global 13.0.3(RKXINXM) isn't available there. Plz help...
Click to expand...
Click to collapse
Today evening, I'll add more boot.img

kisielec said:
Today evening, I'll add more boot.img
Click to expand...
Click to collapse
eagerly waiting, Thanks

Hey there.
I have done everything above and i MIGHT have some problem. The problem with my problem is that its not really reproducable easily even for me.... Weird, I know!
Lets go into details:
Issue description: When I reboot my tablet it goes into "MIUI Recovery" window, on which I am offered to reboot the device or clean.... And when I reboot it goes back to the recovery screen again. Like a loop-hole.
....
But then if I leave it untouched for several minutes it reboots itself and launches the system properly finally...
When did it start: It first started after I performed this step:
24. Click on Install from storage button and find file safetynet-fix-v*******.zip, than click on it
25. After that reboot your device one more time
Click to expand...
Click to collapse
When I finally landed in the system I of course continued and performed further steps. After another reboot in step 27 the same thing happened but much, much longer.
I thought it somehow self fixed and works - once I am in the system. Right? So I did a reboot to test it. And no... recovery screen again for another 20 or so minutes until finally MIUI loaded fully.
Now I am afraid to turn off / reboot my tablet... I am afraid it might never finish booting next time.
Any ideas whats wrong and how to fix this weird and irregular behaviour?
My details:
Device: Xiaomi Pad 5 6/256gb
Original system was Chinese. I have reinstalled to Global one a version ago.
MIUI version currently running: 13.0.3(RKXMIXM)
Android version: 11 RKQ1.200826.002
Magisk version: 25.1 (25100) (32)
Magisk Modules: Universal SafetyNet Fix v2.2.1 (yes I made sure to download around Zygisk section)
Anything else I shall provide?

cysmaster said:
Hey there.
I have done everything above and i MIGHT have some problem. The problem with my problem is that its not really reproducable easily even for me.... Weird, I know!
Lets go into details:
Issue description: When I reboot my tablet it goes into "MIUI Recovery" window, on which I am offered to reboot the device or clean.... And when I reboot it goes back to the recovery screen again. Like a loop-hole.
....
But then if I leave it untouched for several minutes it reboots itself and launches the system properly finally...
When did it start: It first started after I performed this step:
When I finally landed in the system I of course continued and performed further steps. After another reboot in step 27 the same thing happened but much, much longer.
I thought it somehow self fixed and works - once I am in the system. Right? So I did a reboot to test it. And no... recovery screen again for another 20 or so minutes until finally MIUI loaded fully.
Now I am afraid to turn off / reboot my tablet... I am afraid it might never finish booting next time.
Any ideas whats wrong and how to fix this weird and irregular behaviour?
My details:
Device: Xiaomi Pad 5 6/256gb
Original system was Chinese. I have reinstalled to Global one a version ago.
MIUI version currently running: 13.0.3(RKXMIXM)
Android version: 11 RKQ1.200826.002
Magisk version: 25.1 (25100) (32)
Magisk Modules: Universal SafetyNet Fix v2.2.1 (yes I made sure to download around Zygisk section)
Anything else I shall provide?
Click to expand...
Click to collapse
I also have this module installed without problems, as there is no recovey for Pad5, it is a good idea to install in magisk the module Magisk Bootloop Protector, which serves exactly to prevent what you are afraid that happen with your tablet

Teclast M40 Pro Discoveries

Teclast M40 Pro Discoveries​Various helpful points of knowledge to unlock your bootloader, to root, and use your tablet.
Problem: Where can I obtain the official firmware?
Solution: Teclast Website
Usage: type M1A3 in search
Problem How can I unpack "pac" files?
Solution: Build C utility divinebird / pacextractor
Solution: Download pre built Linux executable pacextractor.zip
Usage: >./pacextractor Firmware.pac
Bash:
git clone https://github.com/divinebird/pacextractor
cd pacextractor
make
Problem: I need tools to flash my device
Solution: Download the latest SPD Upgrade Flash Tool SPD_Upgrade_Tool
Problem: msvcr100.dll missing error in Windows whilst running SPD (Factory/Research/Upgrade) Tools
Solution: Download and install 2010 Visual C++ Distribution
Problem: I want to unlock my bootloader. (Window and Linux kit)
Solution: Download TeclastM40Pro_Unisoc_UnlockTools.zip
Usage: Read readme file.
Problem: How can I remove the dm_verify warning on boot up after unlocking the bootloader?
Untested Solution: digitally sign the vbmeta partition and write it back. See [Tutorial] How to create a custom signed vbmeta.img
Problem: I want to root my device.
Solution: Modify boot.img with Magisk, then sign.
Usage: Upload to your device's download directory, the current boot.img read from your device, or from the same version firmware. Then install Magisk app from here. Use Magisk to patch the boot.img. Sign the partition. Then flash back the signed magisk version of boot.img to "boot_a" partition. Guide to flashing single partition at Hovatek Website
Problem: I need to emergency flash my device?
Solution: Currently only from Windows, use SPD Upgrade Tools to reflash firmware.
Usage: From the tablet powered off, or if boot looping. Hold down the power-button and volume-down for five seconds, release the power-button, and keep the volume-down button still held for another five seconds, then release or release if the detected earlier. Windows and SPD tools should then detect your device to flash.
Problem: I want to improve my Telcast M40 Pro
Solution: List of suggested apps below;
FDroid App Store F-Droid Website
Aurora > via FDroid. App store allowing the direct download from Google Playstore, without your own account.
Lawnchair > via FDroid. Fast open source sophisticated launcher.
AdAway > via FDroid. Removes adverts whilst using apps.
TrackerControl > via FDroid. Manages apps access to internet, and blocks spyware and trackers.
.

Problem: I want root mode without the effort of hacking a rom partition.
Solution: For those with World version Teclast M40 Pro device, here is a signed rooted boot partition I created. Read the readme file inside the zip. You will require an unlocked device, windows setup with USB drivers for Teclast, the complete firmware from Teclast website, and SPD Update Tools installed. If you're successful, then on rooting you will need to install Magisk app to get root active. Magisk will reboot once to finalise.
Download : TeclastM40Pro_ROW__v1p0_signedboot_magiskrooted.zip
Download : TeclastM40Pro_ROW__v1p2_signedboot_magiskrooted.zip

SPD Upgrade Tools is closing while trying to flash stock firmware, both with M40 Pro locked and unlocked bootloader. What should i do?

laurorual said:
SPD Upgrade Tools is closing while trying to flash stock firmware, both with M40 Pro locked and unlocked bootloader. What should i do?
Click to expand...
Click to collapse
Sorry for replying late. I got no indication of the response. To the problem, I can only suggest getting a different version of SPD or m aking sure your computer system is properly updated. I hope you've already solved the issue!
Maybe you're experiencing, "Problem: msvcr100.dll missing error in Windows whilst running SPD (Factory/Research/Upgrade) Tools" See above for solution.

I've noticed a new ROM for world edition, "M40 Pro(M1A3)_Android 11.0_ROW V1.02_20220525", but not getting any system update options for OTA. People flashing their systems may want the latest firmware!

Thanks to your Magisk file I was able to root my tablet, but when updating to the latest version it goes into bootloop, I have tried updating the original firmware image again, but it also goes into bootloop.
Is there any way to install Magisk modules?
Thanks for your post, it helped me a lot to unlock my tablet.
Edit: My version is the M1A1 firmware V1.03_20210804
Edit 2: Finally, when updating my tablet with the root file that is in the post, it did not allow me to install any Magisk module, the solution is to download version 24.3, and update automatically, without changing to a higher version of Magisk

Glad you worked it out Miny !!! Sorry the warning emails for new posts have been going to a gmail account I no longer use.
Also your hardware maybe different and require it's own unique firmware and boot images. It seems the cracking in similar though.

Some questions:
Do I need to unlock my bootloader in order to be able to get root with magisk?
The tools for unlocking the bootloader uses
Code:
fastboot flashing unlock_bootloader
. My version of fastboot (33.0.3p1-android-tools) doesn't have that command. The included one (0.0.0-09219) does, but I wan't to be careful about running softwar from untrusted sources. Where is that version of fastboot from?
Does any of the steps necessary to get root access delete my data?

Hi there.
I have a m40pro (M1A1) running android 11, do you know if I can install firmware Z3A1 to get android 12? Or will be bricked?
Thanks in advance

rubsbcn said:
I have a m40pro (M1A1) running android 11, do you know if I can install firmware Z3A1 to get android 12? Or will be bricked? Thanks in advance
Click to expand...
Click to collapse
To tell you the truth, not sure. Most SoC are impossible or near impossible to brick. They usually allow for an injection or have a read only boot section. Other words you could test. Also research difference in hardware between models, and that may indlicate if something may not work. The kernel/drivers are the improtant aspect.

jorkusjorkus said:
Some questions:
Do I need to unlock my bootloader in order to be able to get root with magisk?
The tools for unlocking the bootloader uses
Code:
fastboot flashing unlock_bootloader
. My version of fastboot (33.0.3p1-android-tools) doesn't have that command. The included one (0.0.0-09219) does, but I wan't to be careful about running softwar from untrusted sources. Where is that version of fastboot from?
Does any of the steps necessary to get root access delete my data?
Click to expand...
Click to collapse
What OS are you using? Google is constantly changing Android Studio and the added modules. Then others may build with options removed. Personally I use Archlinux and load up standalone android-tools from the community repository. Currently v33.0.3-3
Try fastboot --help
Your version may have
Code:
fastboot flashing unlock_critical

minyfriki said:
Thanks to your Magisk file I was able to root my tablet, but when updating to the latest version it goes into bootloop, I have tried updating the original firmware image again, but it also goes into bootloop.
Click to expand...
Click to collapse
What I found works, is when using SPD Research Tool, load up the firmware.pac and then go into settings and click "Select All Files" and again to unselect, which leaves the default required items.
Then manually change BOOT to the Magisk img. Then click on all VBMETA types, and UBOOT_LOADER (may not be required though). Then flash.
You should get bootable tablet (no looping). Warning: UserData partition is written over.
I'll share my Magisk image for v1.2

e8hffff said:
What OS are you using? Google is constantly changing Android Studio and the added modules. Then others may build with options removed. Personally I use Archlinux and load up standalone android-tools from the community repository. Currently v33.0.3-3
Try fastboot --help
Your version may have
Code:
fastboot flashing unlock_critical
Click to expand...
Click to collapse
I'm using the same version as you on the same OS. After some research it seems like unlock_bootloader was removed in this commit from 2018. From what I can tell, unlock_critical does something else (unlock_bootloader runs
Code:
fb_queue_download("unlock_message", data, sz); fb_queue_command("flashing unlock_bootloader", "unlocking bootloader");
while unlock_critical runs
Code:
do_oem_command("flashing", "unlock_critical" and doesn't take the signature argument);
)
I'll see if I can compile the older version with the needed command.
What about my other questions?

Issue: Android not starting. I had the infinite restart when plugged in the usb. I tried to reload the installation package (succeeded), but didn't fixed the issue. Battery was not charging yet. When I started the Teclast M40 pro, the logo showed up, but the tablet turned off again.
Solution: I have disassembled the cover, unplugged the 5 pin plug from the battery for half hour and plugged again. When I tried to turn it on, everything was fine.

dougcwb said:
Solution: I have disassembled the cover, unplugged the 5 pin plug from the battery for half hour and plugged again. When I tried to turn it on, everything was fine.
Click to expand...
Click to collapse
Wow that's weird Doug. Remember this, if you don't already know, that you can do a cold start by holding down the power button for over 10 seconds, on most devices.
I guess you're running now on rooted tablet !!!

e8hffff said:
Wow that's weird Doug. Remember this, if you don't already know, that you can do a cold start by holding down the power button for over 10 seconds, on most devices.
I guess you're running now on rooted tablet !!!
Click to expand...
Click to collapse
I did the installation package process that the Teclast sent me. The last thing they told me to do was keep trying to install the package (wft?). Well, I just open the tablet, unplugged the battery for a while and after that it worked.
Maybe this resolved 2 things:
1-the battery was not properly connected in the first place, so when I plugged the 5 pin to the board it connected as it should.
2- Maybe there is a "memory" in the board attached to the battery that was bricked (or something like that) when I pulled off the plug, this memory was reseted.
BTW, when the tablet came to life again, the battery was at 87%.