Related
Hello, i am running full stock and trying to update to 7.1.1 via sideload, i have had no issues in the past when i done my monthly update.
i get the following error:
C:\Users\*\AppData\Local\Android\Sdk\platform-tools>adb sideload bullhead-ota-nmf26f-27b4075c.zip
loading: 'bullhead-ota-nmf26f-27b4075c.zip'
* cannot read 'bullhead-ota-nmf26f-27b4075c.zip' *
i can open the zip file with winrar and have no issues extracting it, i have downloaded android studio and am using the latest adb and running cmd as admin, also the sha-256 match
Are you certain the zip file is in "C:\Users\*\AppData\Local\Android\Sdk\platform-tools>" ??
Make sure the zip is in the same folder as adb.exe
kirkgbr said:
Are you certain the zip file is in "C:\Users\*\AppData\Local\Android\Sdk\platform-tools>" ??
Make sure the zip is in the same folder as adb.exe
Click to expand...
Click to collapse
I have also problem updating to 7.1.1 final version from DP2. It says updating aborted. Can't update over newer build. But I'm in Developer Preview 2 of 7.1.1, how is this possible. Finally in order to update to android 7.1.1 official I had to opt out of beta to get Android 7.0 and then I sideloaded the update with success!Now I have the latest update of our beloved Nougat with December 5 security patch!
Billys20 said:
I have also problem updating to 7.1.1 final version from DP2. It says updating aborted. Can't update over newer build. But I'm in Developer Preview 2 of 7.1.1, how is this possible. Finally in order to update to android 7.1.1 official I had to opt out of beta to get Android 7.0 and then I sideloaded the update with success!Now I have the latest update of our beloved Nougat with December 5 security patch!
Click to expand...
Click to collapse
The final release version appears to have been made before the developer preview 2 build. Developer Preview 1 was very stable in my opinion and they went ahead and made a final version based on developer preview 1 soon after releasing it. You can just flash the factory image to get to the final version
yep its in there
https://img42.com/VcsxN
kenpachizero said:
Hello, i am running full stock and trying to update to 7.1.1 via sideload, i have had no issues in the past when i done my monthly update.
i get the following error:
C:\Users\*\AppData\Local\Android\Sdk\platform-tools>adb sideload bullhead-ota-nmf26f-27b4075c.zip
loading: 'bullhead-ota-nmf26f-27b4075c.zip'
* cannot read 'bullhead-ota-nmf26f-27b4075c.zip' *
i can open the zip file with winrar and have no issues extracting it, i have downloaded android studio and am using the latest adb and running cmd as admin, also the sha-256 match
Click to expand...
Click to collapse
I am having exactly the same thing. ADB reboot to recovery detects and reboots the phone. But from ADB SIDELOAD, same thing.
Already tried USB troubleshooting (having only the phone connected), and multiple downloads of the OTA file that matches the SHA-256. Tried everything from the net, doesn't fix/work.
anyone encountered and fixed this issue?
I got Windows 10 Pro x64, tried both USB 2.0 and USB3.0 sockets, and still the same.
run command prompt as admin?
Primal1031 said:
run command prompt as admin?
Click to expand...
Click to collapse
yes, i did run as admin in my first post
Same issue here: I firstly tried with Nexus Root Toolkit but with no fortune (some missing stock files), then tried with ADB Sideload. Always KO with error * cannot read 'bullhead-ota-nmf26f-27b4075c.zip' *
Same Issue here on 5x. Just spent a few hours trying to figure this one out to no avail.
Windows 10 64bit
Latest ADB Drivers
multiple downloads of OTA update file
matching SHA-256 checksum
cmd as admin
plenty of space on device
same setup as every other sideload I've done
Always getting "cannot read 'bullhead-ota-nmf26f-27b4075c.zip"
And if you try to put the update file on the SDCard and issue the "Apply update from SD Card" you get:
"E:unknown volume for path [/sdcard]
-- Couldn't mount /sdcard
Installation aborted."
Trying to find any solution before having to flash a full factory image.
Billys20 said:
I have also problem updating to 7.1.1 final version from DP2. It says updating aborted. Can't update over newer build. But I'm in Developer Preview 2 of 7.1.1, how is this possible. Finally in order to update to android 7.1.1 official I had to opt out of beta to get Android 7.0 and then I sideloaded the update with success!Now I have the latest update of our beloved Nougat with December 5 security patch!
Click to expand...
Click to collapse
hi guys just info, you can't install nmf26f ota file just because its older than npf26f, so in this case you downgrade the rom via sideload and you can't do that. I know because I doing same thing like you do before
adytprayoga said:
hi guys just info, you can't install nmf26f ota file just because its older than npf26f, so in this case you downgrade the rom via sideload and you can't do that. I know because I doing same thing like you do before
Click to expand...
Click to collapse
I can't speak for everyone else, but I was trying to go from n5d91l TO nmf26f which should work just fine going from the 7.0.0 to 7.1.1 version.
USB debugging enabled in developer settings?
I just side loaded ota from 7.0 to 7.1.1 in under 20 minutes. Following directions only on ota Google developers instructions. https://developers.google.com/android/ota
Using minimal adb and fastboot only, no SDK, did it for you. http://forum.xda-developers.com/showthread.php?t=2317790
scariola said:
USB debugging enabled in developer settings?
I just side loaded ota from 7.0 to 7.1.1 in under 20 minutes. Following directions only on ota Google developers instructions. https://developers.google.com/android/ota
Using minimal adb and fastboot only, no SDK, did it for you. http://forum.xda-developers.com/showthread.php?t=2317790
Click to expand...
Click to collapse
i have downloaded the one in that thread but no success, same result, i confirm usb debugging via settings and going adb devices before i start
Just out of curiosity, are the successful sideloaders using Linux? I set ADB_TRACE=1 and got a memory allocation message (when I get to my PC, I'll post the message). It seems that the adb that is in the sdk has issues with large OTA files.
EDIT: While I **thought** I tried this, I just tried to install the OTA using an admin mode command prompt, no error message, and I see the update coming over on my phone... I also see FAR too many trace messages in my command prompt window, but that's not all that important... Just have to wait for the update to finish "patching system image unconditionally"...
Sent from my Nexus 5X using Tapatalk
I'm having problems with the update too. I haven't tried adb sideload yet.
I tried only the built-in option. The update is downloaded and verified. After pressing the button for reboot and installation the phone starts into the recovery and then doesn't do anything anymore.
Anyone an idea what might be the problem?
EDIT: Now i tried the method stated in https://developers.google.com/android/ota but all i get is the error message "error:closed". I tried it with adb devices and with adb usb before but nothing works.
found my issue, BitDefender was stopping it, something as simple as antivirus....
Can anyone tell me how to do a manual update without loosing my personal app data?
@flattervieh: save them with TitaniumBackup.
Hi All,
I have a bit of a "complicated" situation on my hands.
Pre-Story:
I bought an Honor 8 Pro device over a year ago.
My device model, according to my box and my device's back panel back-print is "DUK-AL20", but in my Settings -> About menu it's "DUK-L09".
Pre-Problem:
Anyway, I was stuck with Nought OS for a very long time and want to upgrade OTA but no upgrade was available.
I tried several time to manually install Oreo OS manually with using getdroidtips guides and builds that supposed to match my "about" version (DUK-L09) and my back panel-print version (DUK-AL20) but no lock. Each time I got an error that incompatible version or something similar.
This is happening over several months now.
The-Problem:
A few hours ago, I decides to to erase everything on my device (using TWRP) and install a new stock OS on my device - hoping that it will solve the upgrade issues and problems.
After erasing, I can't find a good guide or info on how to install a new OS either by:
1. Trying to install update.app file throught TWRP -> I get "Updated process ended with ERROR: 1"
2. Trying to use DUK_FullOTA_ROM_flasher.zip file -> I get "Updated process ended with ERROR: 9"
3. I try to extracted update.app to a dload folder in my root device and force-upgrade the device -> I get an failure to update.
4. Furthermore. eRecovery failed to download (or even find) a suitable OS to download.
I'm pretty suck in pretty much everything I do is not working.
I would appreciate any help I could get.
Thank you!!!
"forum.xda-developers.com/honor-7x/how-to/getting-to-stock-emui-super-easily-t3804722"
try this one.
(remove the quotes!)
Android 13 Developer Preview 1 horror story: If you can't unlock your bootloader, you shouldn't run especially so early in development versions of Android, because there's nothing you can do to fix it once you've "upgraded" to a newer version of Android, except wait for the next Developer Preview or Beta (or closer to release, Stable).
Deep Dive on Twitter:
Lughnasadh said:
Here's a little deeper dive into Tiramisu DP1...
https://twitter.com/i/web/status/1491838098161819679
Click to expand...
Click to collapse
Deep Dive in BLOG format:
Lughnasadh said:
Another deep dive by Mishaal Rahman in blog form...
Android 13 changelog: A deep dive by Mishaal Rahman
This is everything you need to know about new Android 13 features, its release date, and API changes for developers.
blog.esper.io
Click to expand...
Click to collapse
Here there be dragons. I am not responsible for anything at all.
Note the warning in the article:
Warning: The preview releases are intended for developers only, so don’t install them on your daily driver. You might encounter showstopper bugs or other system instabilities. It is highly recommended that you back up your data before proceeding. Users are advised to exercise caution.
Click to expand...
Click to collapse
TL;DR:
For supported Google Pixels: Sideload Android 13 via Recovery and ADB
For supported Google Pixels: Flashing full Factory Image via Fastboot
Any Project Treble-compatible Android device: Install Android 13 GSI
The recommended way to flash Android 13 to a Pixel device is to use the Android Flash Tool.If you'd rather flash your device manually, you can get an Android 13 system image for your device on the Pixel downloads page. See the general instructions on the downloads page for how to flash a system image to your device. This approach can be useful when you need more control over testing, such as for automated testing or regression testing.Be sure you're using the latest SDK Platform Tools and Google USB Driver.For eligible Google Pixel devices, you can download the first Developer Preview build of Android 13 from the links below:
DeviceOTAFactory ImageGoogle Pixel 4Download LinkDownload LinkGoogle Pixel 4 XLDownload LinkDownload LinkGoogle Pixel 4aDownload LinkDownload LinkGoogle Pixel 4a 5GDownload LinkDownload LinkGoogle Pixel 5Download LinkDownload LinkGoogle Pixel 5aDownload LinkDownload LinkGoogle Pixel 6Download LinkDownload LinkGoogle Pixel 6 ProDownload LinkDownload Link
How to install Android 13 on Google Pixel and other Android devices:
February 10, 2022 1:00pm Skanda Hazarika
How to install Android 13 on Google Pixel and other Android devicesAndroid 13 is making its first appearance today. The flashaholics will be delighted to know that Google has already made the system images available for download. You can give it a shot right now if you’ve got the right hardware, but there aren’t as many supported devices this time around. All you’ve got to choose from are the Google Pixel 4, Pixel 4 XL, Pixel 4a, Pixel 4a 5G, Pixel 5, Pixel 5a, Pixel 6, and the Pixel 6 Pro.
The first developer preview of Android 13 is, of course, rough around the edges, so Google doesn’t want to make it too easy to install it on your daily driver. You’ll need an eligible Pixel smartphone with an unlocked bootloader to flash the system image using your computer. There are also OTA files, which update your Pixel to the Developer Preview without an unlocked bootloader. However, you still need to manually sideload the OTA package.
Apart from device-specific firmware packages, Google has also published the first Developer Preview build of Android 13 as a Generic System Image (GSI) that can be flashed on a much wider range of devices. Google validated them on the aforementioned Pixel smartphones, but they should technically boot on any Project Treble-compatible device.
Warning: The preview releases are intended for developers only, so don’t install them on your daily driver. You might encounter showstopper bugs or other system instabilities. It is highly recommended that you back up your data before proceeding. Users are advised to exercise caution.
The three methods to install the update are:
For supported Google Pixels: Sideload Android 13 via Recovery and ADB
For supported Google Pixels: Flashing full Factory Image via Fastboot
Any Project Treble-compatible Android device: Install Android 13 GSI
Method 1: Sideload Android 13 via Recovery and ADBTo install the Developer Preview, you need to sideload the appropriate OTA package for your device from Recovery through ADB. This method will also work for Google Pixel devices with a locked bootloader.
Download the update .zip file on your computer from here. For convenience, you can rename this file to a simpler name and place the file in the directory where ADB is located on your computer.
Optional, but recommended: Verify the SHA-256 checksum of the file you have downloaded to ensure that the file has been downloaded completely and correctly.
Enable USB Debugging on your phone — Go to Settings > About Phone > Tap Build Number 7 times, (optionally) enter your pattern, PIN or password to enable Developer Options, and then navigate to Settings > Developer Options > Enable USB Debugging.
Connect your phone to your computer. Authorize your computer connection on your phone when the prompt comes up on your phone, if this is the first time you are connecting with the ADB instance of this computer.
On your computer, run the command:adb reboot recovery
Your phone should now be in Recovery mode.
On your phone, select the option Apply Update from ADB.
On your computer, run the command:adb devices
This should return a device serial with the “sideload” next to its name, indicating that your device is connected to the computer in sideload mode.
On your computer, run the command:adb sideload "filename".zip
The “filename” part is to be replaced with the name of the file downloaded in Step 1.
The update should install on your phone. Once the installation is complete, choose Reboot system now on your phone to reboot into Android 13.
Method 2: Flashing full Factory Image via FastbootIf you have an unlocked bootloader on a Google Pixel device, you need to flash the factory image of the Android 13 Developer Preview via Fastboot. Usually, this is done through a flash-all.sh or flash-all.bat script file that is included in the downloaded file, but its default configuration also wipes the device completely. You can, however, retain your data by deleting the “-w” wipe attribute from the command within the script.
Download the factory image .zip file on your computer from here.
Optional, but recommended: Verify the SHA-256 checksum of the file you have downloaded to ensure that the file has been downloaded completely and correctly.
Extract the .zip file, and copy and paste the resultant files onto your ADB and fastboot folder on your computer for convenience.
Optional: The resultant files would contain a flash-all.sh or flash-all.bat script file. Using a text editor, open the flash-all.sh if you’re on macOS/Linux or the flash-all.bat script file if you’re on Windows. Find and remove/delete the -w flag in the fastboot update command. This will skip the data wipe for your phone. To avoid compatibility issues, a data wipe is recommended though.
Enable USB Debugging on your phone — Go to Settings > About Phone > Tap Build Number 7 times, (optionally) enter your pattern, PIN or password to enable Developer Options, and then navigate to Settings > Developer Options > Enable USB Debugging.
Connect your phone to your computer. Authorize your computer connection on your phone when the prompt comes up on your phone, if this is the first time you are connecting with the ADB instance of this computer.
On your computer, run:adb reboot bootloader
This will reboot your phone into Fastboot mode.
On your Mac/Linux PC, run:flash-all
This command executes the flash-all.sh script file, which will then install the necessary bootloader, baseband firmware, and operating system. If you are on Windows, you can simply double click the flash-all.bat file.
Once the script finishes, your device will reboot into the new OS.
Method 3: Install Android 13 GSIEven if you don’t own a compatible Pixel smartphone, you can still install Google’s official GSI binaries to test Android 13, provided your device is compatible with Project Treble. You also need an unlocked bootloader. The last thing that we need to say is that flashing a GSI will require you to factory reset your device, so be sure you’re prepared to lose app data before you proceed with this! We recommend you make an off-device backup (such as on your PC or an SD Card) in case anything goes wrong.
Download links for the official Android 13 Developer Preview GSIs can be found here. You should download the appropriate version based on your device’s architecture. To see which architecture your device has, run the following command:adb shell getprop ro.product.cpu.abi
Optional but recommended: Verify the SHA-256 checksum of the file you have downloaded to ensure that the file has been downloaded completely and correctly.
Extract the .zip file, and copy and paste the resultant files (system.img and vbmeta.img) onto your ADB and fastboot folder on your computer for convenience.
Enable USB Debugging on your phone — Go to Settings > About Phone > Tap Build Number 7 times, (optionally) enter your pattern, PIN or password to enable Developer Options, and then navigate to Settings > Developer Options > Enable USB Debugging.
Connect your phone to your computer. Authorize your computer connection on your phone when the prompt comes up on your phone, if this is the first time you are connecting with the ADB instance of this computer.
On your computer, run:adb reboot bootloader
This will reboot your phone into Fastboot mode.
As mentioned earlier, the bootloader of the target device must be unlocked beforehand.
Next, we need to disable Android Verified Boot (AVB). To do that, run the following command:fastboot flash vbmeta vbmeta.img
Optional but recommended: Enter the following to wipe the system partition:fastboot erase system
Flash the Android 13 GSI:fastboot flash system system.img
Allow the image to flash, it could take a few minutes. Once that’s done, wipe the userdata partition:fastboot -w
Finally, reboot your device:fastboot reboot
Hopefully, your device should boot into the new build of Android.
Click to expand...
Click to collapse
How to download Android 13 for Google Pixel and other Android devices:
February 10, 2022 1:07pm Skanda Hazarika
How to download Android 13 for Google Pixel and other Android devicesGet ready to dig into Android 13! While we are still waiting for Android 12L to be officially released via stable channel, the next major release of Google’s OS is now available starting today in the form of the first Android 13 Developer Preview. For lucky owners of the Google Pixel 6, Pixel 6 Pro, Pixel 5a, Pixel 5, Pixel 4a 5G, Pixel 4a, Pixel 4, or Pixel 4 XL, you’ll be among the first users to see what Android 13 “Tiramisu” has to offer.
Notably, existing Android beta participants won’t automatically get the first Android 13 Developer Preview as an over-the-air update. The preview release must be manually sideloaded. You can learn how to install Android 13 on Google Pixel smartphones and other devices by visiting our dedicated guide here.
Keep in mind that the initial build won’t give you the full Android 13 experience as it’s very much a work-in-progress. This first preview is aimed solely at developers, since they need to test their apps against new Android platform APIs months before the next Android version becomes available for the general public. Installing the Developer Preview on your daily driver isn’t recommended, as you might face various system instabilities. Do back up your data before proceeding.
This page will serve as a one-stop download index for every Android 13 build released by Google. We will keep the page updated with the latest OTAs and factory images for the supported Pixel smartphones.
Navigate this page:
Download Android 13:
Developer Preview 1
Download Android 13 for Google Pixel devicesAndroid 13 Developer Preview 1For eligible Google Pixel devices, you can download the first Developer Preview build of Android 13 from the links below:
DeviceOTAFactory ImageGoogle Pixel 4Download LinkDownload LinkGoogle Pixel 4 XLDownload LinkDownload LinkGoogle Pixel 4aDownload LinkDownload LinkGoogle Pixel 4a 5GDownload LinkDownload LinkGoogle Pixel 5Download LinkDownload LinkGoogle Pixel 5aDownload LinkDownload LinkGoogle Pixel 6Download LinkDownload LinkGoogle Pixel 6 ProDownload LinkDownload Link
Additionally, Google offers ready-to-use Android 13 Developer Preview system images under the Android Emulator in Android Studio.
Click to expand...
Click to collapse
Three separate branches in a single week. Wow.
Time to check the modem again lol. Probably older than 12L and we flash on top.
LLStarks said:
Three separate branches in a single week. Wow.
Time to check the modem again lol.
Click to expand...
Click to collapse
Good luck! As always, please let us know your thoughts (goes for anyone who tries it). I'll likely be sticking to regular 12, at least until closer to when 13 releases, unless I hear about some stupendous new feature that I want to try.
Edit: Maybe I misremembered which release was going to be Android T (so great, both 12 and 12L are S). Old: Now, I thought I heard reference to 12L being Android T (as it should be since it's a new API level), so 13 should be U. My wife suggests Upside-down Cake. Any other better ideas? I'm sure someone's got to have a better idea.
Modem is newer than Feb but older than 12L. Bootloader is version 1.2 compared to 1.1 in 12L and 1.0 in Feb.
Mixed bag. Need to see what 13 modem is capable of (i.e. VoNR, C-Band, etc).
VoNR and C-Band are present. Rooting works as expected.
Edit: This update adds 3 carrier 5G aggregation?!?! n41-n71-n71 and n41-n41 looks to be present with the latter also appearing in 12L.
Here's a little deeper dive into Tiramisu DP1...
https://twitter.com/i/web/status/1491838098161819679
LLStarks said:
VoNR and C-Band are present. Rooting works as expected.
Edit: This update adds 3 carrier 5G aggregation?!?! n41-n71-n71 and n41-n41 looks to be present with the latter also appearing in 12L.
Click to expand...
Click to collapse
Are you using the latest stable Magisk?
As for root, just flashing a patched boot image?
I always use the latest alphas for Magisk and patch my own files.
Lughnasadh said:
Here's a little deeper dive into Tiramisu DP1...
Click to expand...
Click to collapse
Another deep dive by Mishaal Rahman in blog form...
Android 13 changelog: A deep dive by Mishaal Rahman
This is everything you need to know about new Android 13 features, its release date, and API changes for developers.
blog.esper.io
Lughnasadh said:
Another deep dive by Mishaal Rahman in blog form...
Android 13 changelog: A deep dive by Mishaal Rahman
This is everything you need to know about new Android 13 features, its release date, and API changes for developers.
blog.esper.io
Click to expand...
Click to collapse
Thanks! Adding to the OP.
So I guess their is no GSI version available as 2_12_20? Or did I get that wrong.
hooutoo said:
So I guess their is no GSI version available as 2_12_20? Or did I get that wrong.
Click to expand...
Click to collapse
Good question or observation. Indeed, it appears XDA's article references things that don't seem to be available, or at least their link to where it claims it is available doesn't lead to anything obvious. But I think it's just confusing, at least to this non-developer (me).
I think they're merely reflecting the official information Google gives, which also leads to a dead-end regarding GSI versions:
This search https://www.google.com/search?q=and...69i57j0i390.4224j0j7&sourceid=chrome&ie=UTF-8
led me to the 3rd or 4th search result "The first developer preview of Android 13" at https://android-developers.googleblog.com/2022/02/first-preview-android-13.html#:~:text=For even broader testing, GSI images are available, and their statement is the same:
If you don’t have a Pixel device, you can use the 64-bit system images with the Android Emulator in Android Studio. For even broader testing, GSI images are available.
When you’re set up, here are some of the things you should do:
Click to expand...
Click to collapse
The link at "set up" leads to Set up the Android 13 SDK, which includes the step of using Android Studio.
Since at the first search I give above, the 2nd or 3rd search result Generic System Image releases doesn't have anything for Android 13 (but it does mention 12L), in the end I believe that one or both of the following are true:
GSIs are only available for Android 13 through the Android Studio - i.e. to emulate a device running the Android 13 GSI.
and/or
They goofed up and included language that made it sound like GSIs are available to actually download and flash on physical devices, perhaps in preparation for when they do intend to have the GSIs available later in the development process - maybe once it progresses from Developer Preview 2 to Beta 1?
Ya, I was thinking the same thing. A lot what was mentioned in the OP is just copy/paste material for when the gsi rom drops.
https://twitter.com/i/web/status/1493335334125379586
Already got dp1 running on my lg v60.
Need some info. On my lg v60, after installing Pixel-Pixel4a-DP1-A13-AB-Tiramisu-20220211-NipponGSI.img, I checked settings>system>system update. I'm getting Android 12 on the dialog screen.
What does it show on an actual pixel phone?
hooutoo said:
Need some info. On my lg v60, after installing Pixel-Pixel4a-DP1-A13-AB-Tiramisu-20220211-NipponGSI.img, I checked settings>system>system update. I'm getting Android 12 on the dialog screen.
What does it show on an actual pixel phone?
Click to expand...
Click to collapse
I wish I knew what to tell you. Perhaps someone else can help. I know nothing about GSIs, much less GSIs on LG devices, and I'm not stepping into the Android 13 (or even 12L) pool just yet.
Have you asked about this aspect in the LG V60 section?
Teclast M40 Pro DiscoveriesVarious 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%.
Sorry for my English. I have Xiaomi mi8 with last LineageOS. Into root folder of phone I put zip gapps file. But when I turn my phone to fastboot and than to TWRP, I can not find my zip file with gapps. The structure of folders is different than when phone is connected to PC. Maybe you know what to do with it please?
As far as I remember you can/must select the storage, including sdcard (which I prefer to use).
PS: Ahoi
Phone does not have external storage card extension. No, prostě když ten telefon připojím k počítači, je tam určitá struktura složek. nahraju tam zip. Pak dám fastboot, dostanu se do TWRP a dám install a už tam je úplně jiné složení složek a zip nemůžu najít
oh, actually I know only 3 czech words: ahoi, knedliki and staropramen
anyway, in TWRP you can select the storage (bottom left, i think). (gtranslate: v TWRP si můžete vybrat úložiště (myslím vlevo dole).)
I know I can select the storage. But, it is impossible to find my zip file The structure of folders is diffrent than the structure I can see when phone is connected to PC for file transfer
A) Maybe a fast workaround: Use an USB OTG adapter and plug-in some USB stick with the files?
OR
B) In modern Android, there are several partitions and my guess is, that you have the files on another.
So you could study some search results for "android partition layout" like p.e. https://source.android.com/docs/core/architecture/bootloader/partitions/system-as-root
FRQD75 said:
A) Maybe a fast workaround: Use an USB OTG adapter and plug-in some USB stick with the files?
OR
B) In modern Android, there are several partitions and my guess is, that you have the files on another.
So you could study some search results for "android partition layout" like p.e. https://source.android.com/docs/core/architecture/bootloader/partitions/system-as-root
Click to expand...
Click to collapse
I will try it and inform you here I have to order usb otg. Thanks
OK, I installedMindTheGapps-12.1.0-arm64-20220605_112439.zipfrom USB otg adapter. But Gapps are falling. They are in phone, but I can not start them.
Hello guys,
I believe that I faced a similar case.
I am using MI8 pro, and I installed lineageos 20 with mindthegapps for Android 13. The Google services keep stopping.
Then I tried lineageos 19 with mindgapps 12.1 arm64. The same failure is reported.
I am totally confused. I used adb sideload way to install the os image and gapps without interrupt.
Is there any idea in my case?
Regards,
illidanpc said:
Hello guys,
I believe that I faced a similar case.
I am using MI8 pro, and I installed lineageos 20 with mindgapps for Android 13. The Google services keep stopping.
Then I tried lineageos 19 with mindgapps 12.1 arm64. The same failure is reported.
I am totally confused. I used adb sideload way to install the os image and gapps without interrupt.
Is there any idea in my case?
Regards,
Click to expand...
Click to collapse
Today, I tried LiteGapps Nano arm64 13.0 v2.8 official version, based on LineageOS 20. However, it still didn't work on my MI 8 pro. (For the people didn't fimilar with LiteGapps, it's another popular Gapps version, as well. )
But if I only sideload the LineageOS 20, it's perfect running.
So the issue could be related with the compatible of Gapps.
illidanpc said:
Today, I tried LiteGapps Nano arm64 13.0 v2.8 official version, based on LineageOS 20. However, it still didn't work on my MI 8 pro. (For the people didn't fimilar with LiteGapps, it's another popular Gapps version, as well. )
But if I only sideload the LineageOS 20, it's perfect running.
So the issue could be related with the compatible of Gapps.
Click to expand...
Click to collapse
Today i tried a new gapps named BiTGApps, which works fine with LineageOS20. The url of BiTGApps homepage is bitgapps.github.io. The "works fine" means the google login service in setting menu, and google play works fine. There's no more gapps installed which is a minimal setup, i believed.
I used adb sideload way to install bitgapps, even the powershell terminal shows error, but it seems didn't affect the result.
I hope this one would help you, either.