Develop Bugs

[Q] Where do I start?

I bought this Xperia ARC LT15a on Friday and have been having LOTS of trouble figuring out what to do with it. I came on here and I can say the tutorials aren't very noob-friendly because you have your own "lingo" that I dont understand whatsoever.
Now, for you guys to understand my frustration, I am coming from IOS, and was told "rooting" an Android phone is a much simpler process then jailbreaking an iPone. Well, that sure as hell has proven to be wrong since I can't even figure out how to UPDATE my phone >_>
First off, what I'm trying to do is update it to ICS. Sony says you can do it using the PC Companion, but it says I'm up to date. Same thing with the SEUS or whatever you call it...says I'm up to date. I am running Android Ver. 2.3.4 so I'm pretty sure I am NOT up to date...my IM number (or whatever) is listed as compatible with ICS so it should just update via seus or pc companion...but no...
So someone linked me to tutorials on how to FLASH ics to it... but all of the tutorials have dead links and are completely useless to me now...
Can someone PLEASE tell me what to do... I just want to update to ICS and root it, but I can't even f***ing update.........!!!! very frustrating

i felt exactly the same mate haha
but this was my first smartphone full stop lol
is it the tutorial links in general that are dead?
but do some searching, i found pretty much everything i needed on here
and now i can change ROMS, kernels, baseband etc in minutes
im sure someone more helpful will be along soon lol

Right - I haven't posted much but having been pretty much under the same level of noob frustration before I'll try to help....
First - Often, during updates you can be driven mad with reboots and reboot cycles..... hopefully, what is outlined below can be a guide to sorting out any problems you might have.
1. Backup everything.
- go to play store and search for "backup" and you'll find what you need. I use Astro File Manager for application backup and sms backup for messages. I'm not bothered about backing up anything else.
2. Unlock the Bootloader.
- download sdk starter package
Code:
://developer.android.com/sdk/index.html
- so far as I can figure this will facilitate communications between your pc and phone. CyanogenMod Wiki guides you through this process:
Code:
://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK
- download latest version of fastboot. Now, you'll never double click on this program to run it. Instead you'll run commands from your command tool which will use the program to do the work.
- record your IMEI - in dialer type in *#06# for your IMEI & write it down.
- get your phone attached in fastboot mode. to do this you turn off your phone and hold the menu button while you attach it via USB to your computer.
- see if you're connected properly. Look for command prompt (Windows Key - All Programs - Accessories). Right click on this and run as administrator. Type in the following: fastboot -i 0x0fce getvar version . It will give an obviously positive message if you are correctly connected - if not, ensure you've attached in properly.
- get code to unlock bootloader - go here:
Code:
://unlockbootloader.sonymobile.com/
and go through the process to get an unlock key. Once you have this, go back to your command prompt and type fastboot -i 0x0fce oem unlock 0xUNLOCKKEY (where UNLOCKKEY is the number you have gotten from Sony website. You should get a confirming message.
Now that you've unlocked the bootloader you need to decide what kind of kernel and ROM you want. You can regard the ROM as software whereas the kernel links the software to the hardware. This is my limited understanding anyway.
3. Now, sometimes people make standalone kernels and sometimes they are kept with the ROM.
This leaves a couple of options
- you can flash a stand-alone kernel using flashtool (
Code:
://androxyde.github.com/
). The process is pretty simple.
- Now, if you download a ROM which advises that you need to extract and flash a file called "boot.img" there is a different method. In this case your ROM zip file can be extracted to find the boot.img file.
When you get the boot.img file you can place it in C:\. Now, all advice will be to place it in the platform-tools folder which is created in step 1. It doesn't matter really so long as you point at the right place when flashing.
(I also think that you can use flashtool in flashmode to do this job....)
4. Now you have a kernel on your Xperia and seeing as you've got the bootloader unlocked you can now unplug the phone and turn it on. While the phone is booting up, keep toggling the volume button and it should go into bootloader. This is a text-based interface that allows you several functions.
Somewhere in there is an option to mount the SD card (for which you need to plug into your comp again)
5. You'll see the phone's SD card in Windows explorer and will be able to put your ROM onto it (NOT the extracted stuff from earlier but the original zip file).
6. You can now install this ROM but first clear all data and the dalvik cache. I also always to the battery stats here too. It might take a little bit of exploring to find these.
7. Now you can go to "install zip from SD Card". Step through and you will find where you put the ROM zip file. Select it and install the ROM.
At this point, you may get a bit frustrated - because it's here that you find things like:
The ROM sucks
Bits don't work or
You can't get it to work
For any of the above try again....
Currently I'm on Paranoid Android ICS ROM which I like but if I can't get the Wi-Fi working there's no way I'll be sticking to it. Another that I really liked and will return to is Boost HD RC4
I hope it works out for you.....
Tony

Canned30 said:
Right - I haven't posted much but having been pretty much under the same level of noob frustration before I'll try to help....
First - Often, during updates you can be driven mad with reboots and reboot cycles..... hopefully, what is outlined below can be a guide to sorting out any problems you might have.
1. Backup everything.
- go to play store and search for "backup" and you'll find what you need. I use Astro File Manager for application backup and sms backup for messages. I'm not bothered about backing up anything else.
2. Unlock the Bootloader.
- download sdk starter package
Code:
://developer.android.com/sdk/index.html
- so far as I can figure this will facilitate communications between your pc and phone. CyanogenMod Wiki guides you through this process:
Code:
://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK
- download latest version of fastboot. Now, you'll never double click on this program to run it. Instead you'll run commands from your command tool which will use the program to do the work.
- record your IMEI - in dialer type in *#06# for your IMEI & write it down.
- get your phone attached in fastboot mode. to do this you turn off your phone and hold the menu button while you attach it via USB to your computer.
- see if you're connected properly. Look for command prompt (Windows Key - All Programs - Accessories). Right click on this and run as administrator. Type in the following: fastboot -i 0x0fce getvar version . It will give an obviously positive message if you are correctly connected - if not, ensure you've attached in properly.
- get code to unlock bootloader - go here:
Code:
://unlockbootloader.sonymobile.com/
and go through the process to get an unlock key. Once you have this, go back to your command prompt and type fastboot -i 0x0fce oem unlock 0xUNLOCKKEY (where UNLOCKKEY is the number you have gotten from Sony website. You should get a confirming message.
Now that you've unlocked the bootloader you need to decide what kind of kernel and ROM you want. You can regard the ROM as software whereas the kernel links the software to the hardware. This is my limited understanding anyway.
3. Now, sometimes people make standalone kernels and sometimes they are kept with the ROM.
This leaves a couple of options
- you can flash a stand-alone kernel using flashtool (
Code:
://androxyde.github.com/
). The process is pretty simple.
- Now, if you download a ROM which advises that you need to extract and flash a file called "boot.img" there is a different method. In this case your ROM zip file can be extracted to find the boot.img file.
When you get the boot.img file you can place it in C:\. Now, all advice will be to place it in the platform-tools folder which is created in step 1. It doesn't matter really so long as you point at the right place when flashing.
(I also think that you can use flashtool in flashmode to do this job....)
4. Now you have a kernel on your Xperia and seeing as you've got the bootloader unlocked you can now unplug the phone and turn it on. While the phone is booting up, keep toggling the volume button and it should go into bootloader. This is a text-based interface that allows you several functions.
Somewhere in there is an option to mount the SD card (for which you need to plug into your comp again)
5. You'll see the phone's SD card in Windows explorer and will be able to put your ROM onto it (NOT the extracted stuff from earlier but the original zip file).
6. You can now install this ROM but first clear all data and the dalvik cache. I also always to the battery stats here too. It might take a little bit of exploring to find these.
7. Now you can go to "install zip from SD Card". Step through and you will find where you put the ROM zip file. Select it and install the ROM.
At this point, you may get a bit frustrated - because it's here that you find things like:
The ROM sucks
Bits don't work or
You can't get it to work
For any of the above try again....
Currently I'm on Paranoid Android ICS ROM which I like but if I can't get the Wi-Fi working there's no way I'll be sticking to it. Another that I really liked and will return to is Boost HD RC4
I hope it works out for you.....
Tony
Click to expand...
Click to collapse
I should have mentioned that the only thing I was successful doing was unlocking the bootloader...but then I was told to re-lock it so I could update using the PC companion.......... very annoying
thanks for the detailed reply..
I'm thinking now I wont bother with ICS and ill just root my current version 2.3.4 but yet again ive run into problems with dead links since most have not been updated since this time last year..
*EDIT*
I've tried DooMLords app thing to root, and all I get is a bunch of errors
trying to post a pic with all the errors but im not allowed...............................frustration after frustration after frustration

Try downloading some custom kernels n Roms from this site to see which version of ICS suits not best
There are threads with very explicit details on how to do so, you just need to look
I used to be a noob, on longer the case now.
Currently running acronium 2.4 with doomkernel v04 with WiFi modules, learned how to do all this from here
I'll figure out a site to upload all that I've downloaded so you have access to them with instructions cause some links don't work in other threads
Sent from my LT15i using xda app-developers app

google pixel xl wont update to android 8.0

hello - ive got a google pixel xl on android 7.1.2 i can see from the system update that i can update to Android oreo 8.0, when i click to "download and install" it downloads the 950.7MB file, starts to install , but then stops with message "coouldnt update - installation problem"..any ideas ? ta

goofy gorilla said:
hello - ive got a google pixel xl on android 7.1.2 i can see from the system update that i can update to Android oreo 8.0, when i click to "download and install" it downloads the 950.7MB file, starts to install , but then stops with message "coouldnt update - installation problem"..any ideas ? ta
Click to expand...
Click to collapse
Is your storage near full?

sliding_billy said:
Is your storage near full?
Click to expand...
Click to collapse
no mate...i have nothing on my phone as i recently got it...its about 23GB free

goofy gorilla said:
no mate...i have nothing on my phone as i recently got it...its about 23GB free
Click to expand...
Click to collapse
Sounds like the download is getting a corrupted file. I would either DL and install the factory image (if BL unlocked) with the -w removed from the flashall file or sideload the OTA (if not unlocked).

sorry mate - im not that techy but knowing me ill probaly brick my phone..what is bl, and -w ????? ...sorry not techy

https://developers.google.com/android/images
Straight from the source with detailed instructions.

Since he is not unlocked, he should sideload the full OTA from here
https://developers.google.com/android/ota

I would recommend a full system install given that you purchased the phone from someone. Wouldn't want anything malicious on the phone that the previous owner might have left in.

yes i would do that but not very techy, its still under warranty for another 15 days i think as i have the receipt, but the back glass is cracked , hence google say warranty is void..seems to reboot all by itself and sometimes just switches off..

richii0207 said:
I would recommend a full system install given that you purchased the phone from someone. Wouldn't want anything malicious on the phone that the previous owner might have left in.
Click to expand...
Click to collapse
i would do that but i dont have a clue as to where and how to do this ?

ok found this site to reflash to factory settings..HERE
ive downloaded the files but dont understand where to put the files, the instructions are below but not sure what they mean..it says "computer’s system partition" ???..is that drive C ?
where do i put the image that ive downloaded...into the folder called " Platform-tools folder"
what about the google usb drivers ?....do i put the actual usb folder or its contents into the "platform-tools folder"?
its confusing ..
what do they mean by this "Go to Platform-tools folder. Here you need to launch a Command Prompt / Terminal window with administrative rights."
how do i do that ?
Here’s how to do it:
Download the Platform-Tools zip corresponding to your computer’s operating system:
– for Windows PC click here.
– for Mac OS click here.
– for Linux click here.
unzip the file after the download is complete.
you will obtain the Platform-Tools files, save them all on your computer’s system partition.
– make sure to leave the Platform-Tools name as the default folder name.
next, download the Google USB drivers from here.
Next you can continue to the tutorial and learn how to flash a factory image for your device.
How to install Android 7.1.2 Factory Image for Google Pixel XL:
Download the Android 7.1.2 Nougat factory image file from here.
Extract the archived contents and save them on your PC.
Place all the extracted files in the Platform-tools folder.
– that’s the folder obtained using the steps above the tutorial.

well..somehow it managed to update to android oreo 8.0......after trying all day, will see how the phone performs...its rebooted byitself once already, dont know if that was because it was installling something but update has been done....still think this phone has some hardware problem as the screen froze when i was entering my google play details.....weird phone...

HD and WiFi Voice and Video Calling on XT2041-4 with Verizon

Prerequisites:
You must bootloader unlock your XT2041-4.
Unlocking the Bootloader | Motorola Support US
Visit the customer support page to view user guides, FAQs, bluetooth pairing, software downloads, drivers, tutorials and to get repair and contact us information.
motorola-global-portal.custhelp.com
As far as I'm aware, this only applies to XT2041-4 on Verizon Wireless.
To be clear, the XT2041-4 is the "US Retail" or "Unlocked" (carrier unlocked) version of the Moto G Power. It's available from Best Buy, Amazon, etc. If you bought your Moto G Power from a Verizon store (or the Verizon website) you have the XT2041-7 and you should already have WiFi and HD Voice and Video calling. It's found here:
Settings -> Network & Internet -> Advanced Calling
The XT2041-4 does not have this menu available, so we're going to flash the Verizon ROM onto the Retail phone. Here we go.
Download and install the latest Motorola drivers:
Where can I download the USB drivers for my device?| Motorola Support US
Visit the customer support page to view user guides, FAQs, bluetooth pairing, software downloads, drivers, tutorials and to get repair and contact us information.Where can I download the USB drivers for my device?
support.motorola.com
Plug your phone into your PC with the factory USB cable and make sure you get all the necessary drivers installed. From your phone, select "Android System - Charging" in the notifications bar and change to "File Transfer". This should prompt Windows to install another driver.
Make sure you have the latest platform tools. This includes the latest adb.exe and fastboot.exe for use with fastbootd:
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Download the latest Verizon image for the XT2041-7 from Lolinet:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Once downloaded, extract the zip file, so you're left with a file folder something like ths:
XT2041-7_SOFIA_VZW_10_[version]_subsidy-VZW_RSU_QCOM_regulatory-DEFAULT_CFC.xml
We'll call it your rom folder.
To make life easy, lets copy the required android utilities into this folder for flashing. Open up your platform-tools folder and copy the following to your rom folder:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
With your rom folder open, grab the entire folder location from the address bar and copy to your clipboard.
Click your start menu and type cmd, and open up Command Prompt.
Once you have the command prompt open, change directory to your rom folder:
Code:
cd [rom folder location]
All you have to do is type "cd", then space, then right click your mouse button to paste the folder location that you copied in the last step.
Hit enter to change directory.
Now your Command Prompt can call files from within your rom directory.
Now type:
Code:
adb devices
Watch your phone for the authorization dialog. Check the box and grant authorization. If it doesn't work, try unplugging your phone and plugging back in to get the drivers installed, then try again. The Command Prompt should return the serial number of your Moto G Power.
Now type:
Code:
adb reboot bootloader
And make sure your device reboots into bootloader mode.
Now type:
Code:
fastboot reboot fastboot
Make sure your device reboots into fastbootd. If this command doesn't work, you don't have the latest version of android platform tools.
Now type:
Code:
fastboot reboot bootloader
Your device should reboot back to bootloader mode. If everything is working so far, proceed to this thread and follow steps 4-7.
Moto G Power flashing guide
This guide also applies on other Moto phones shipping with Android 10 (not compatible with phone updated from Android 9) Requirements: * Adb must be up to date. You will use new fastbootd interface. You can toggle between bootloader and...
forum.xda-developers.com
Ignore steps 1-3 since you're using a different rom. Wiping userdata is optional - this will reset your phone to factory settings. Follow step 8 at your own risk - this resulted in a boot loop for me.
That's it! Once your phone boots up, you should have Advanced Calling in the Network & Internet settings menu. To gain root access, it seems as though Magisk doesn't work properly on the Moto G Power (someone correct me if I'm wrong). When attempting to patch the boot image, Magisk says "Downloading" then "Download Complete" instead of the typical "Flashing...". It still outputs some kind of image file, but flashing this file resulted in a bootloop for me. Maybe I'll try to patch the boot image from another device at some point, but for now I have WiFi Voice and Video calling on my (my wife's) XT2041-4. And she probably doesn't need root access anyway...

@clevertrevor777
Thank you for the guide. Is it possible to relock the bootloader afterwards or does this brick it?

Good question. Someone else would have to chime in on that. Why lock it anyway?

@nu_ninja
I got a Moto G Power from Google Fi and I was able to relock the bootloader right after following this guide. I did so before I booted it up initially. OEM Unlocking was still checked in developer options even after I locked the bootloader, so I can unlock it again later as needed.
Thank you Mr. Clever Trevor for figuring this out and sharing.

I have unlocked bootloader for my 2041-4. I have tried several VZW roms but it says boot failed each time. My question is when I type adb devices it says listing devices, but says "List of devices attached ___" and nothing happens with my phone. Thanks for the guide I hope I can get it working. Should I be using android 10 or 11 ROMs??

You really don't need to flash another rom just to enable volte and wifi calling, there just a few build.prop edits if you have root or this twrp flashabe zip: https://github.com/khrj/volte-fix
For manual method root or no root, open up /system/build.prop with root explorer or adb pull it to your pc add this snippet to the end and save it or adb push back making sure it has read/write permissions and voila volte and wifi calling will be enabled in the settings, works for custom roms as well.
Code:
# volte
persist.dbg.ims_volte_enable=1
persist.dbg.volte_avail_ovr=1
persist.dbg.vt_avail_ovr=1
persist.dbg.wfc_avail_ovr=1
persist.data.iwlan.enable=true (disable if problems with wifi calls)
persist.radio.rat_on=combine
persist.radio.data_ltd_sys_ind=1
persist.radio.data_con_rprt=1
persist.radio.calls.on.ims=1
Reboot the phone and check the settings or you can then dial *#*#4636#*#* and under phone information see if you have VOLTE provisioned.

How To Guide Installing OneUI 4 Beta / Android 12 on US Galaxy Z Fold 3 F926U/1

Updated with more compatible adb link!
This is what I did to get the new beta. Feel free to tell me how dumb I am for allowing noobies to try the beta, but the more the merrier and they should know the risks....
RISKS: Phone may not be as stable as before and you will lose all your apps and data. Camera is bugged for me
1. BACK UP YOUR CURRENT BUILD USING SMART SWITCH. THIS WILL WIPE DALVIK/CACHE/DATA. Get SmartSwitch for PC HERE
2. Download Samsung Drivers for ADB/ODIN HERE
3. If you are on firmware ending in AUI5 for the CSC version XAA then skip to step #6 . If you are not, then download the respective firmware HERE
Also Download Patched ODIN (Patched version will be less scrutinous) HERE
4. Unzip the firmware you just downloaded as well as the Patched Odin. Run ODIN and add the BL, AP, CP, Home_CSC from the unzipped firmware to the corresponding locations in ODIN
5. Turn off phone and boot into "Download Mode" by first holding Volume +/- buttons and then hold the Power button. Now plug in your phone to your PC and you will see the first small grey square in the upper left side of ODIN turn light blue (if it does not, you have issues with either the cable or drivers).
Proceed in flashing the device by simply clicking the "Start" button.
Once it is done and your phone has rebooted... Make sure that you complete the setup process just in case of authentication issues if the phone isn't already set up
6. Download the OneUI 4 Beta HERE and then follow the guide to install adb https://www.xda-developers.com/install-adb-windows-macos-linux/
7. Follow the XDA adb install guide and make sure to allow adb systemwide when asked by the program.
8. Turn off phone. Boot into device by holding Volume Up and then holding Power. This will take you into recovery mode, where you will see the option to "update via ADB sideload".
Use the volume down key to navigate down to that option and press power to initiate the adb sideload function
9. Open command prompt by pressing the Windows key and typing "cmd" (no quotes) and press ENTER.
10. Type into the command prompt (of course remove the quotes) "adb sideload C:\path\to\your\oneui4\zip\file" . For example if I download that file into my Downloads folder, I would then type "adb sideload C:\Users\MyPC\Downloads\949981470b3948c3aa05a19e8a2edbd3.zip"

Bro I have SM-F926B, I downloaded the correct CSC but can't install the beta, I got a message on smd says can't read. Any help please?

shadi90 said:
Bro I have SM-F926B, I downloaded the correct CSC but can't install the beta, I got a message on smd says can't read. Any help please?
Click to expand...
Click to collapse
This is for US Fold 3 models f926U/1. Sorry brotha. Basically you need to change the beta file you downloaded to this http://fota-secure-dn.ospserver.net...48:16&px-unum=&px-nb=UGtezEZ854jbmFcvWGxLEA== as well as flash AUJ7 firmware first. I hear UK with CSC BTE works fine. Get it at https://samfw.com/firmware/SM-F926B/BTE/F926BXXU1AUJ7 . After you replaced those files, just follow the instructions again

Thanks for this Guide. But i have issue with Adb sideload update.zip
I downgrade to AUI5 and been using XAA firmware since i bought T-mobile Zfold3.
And since beta was released, I'd been trying to register for OneUI4 in Samsung Memeber app but No Banner or under rBenefit tab.
So saw your guide here and tried to followed your direction but adb sideload fails i get CANNOT READ message.
when i typed adb Devices it shows my device so adb is working but cannot sideload.
when i downloaded the update it was .bin 949981470b3948c3aa05a19e8a2edbd3.bin so i renamed it to .zip, i got the CANNOT READ message then renamed it to update.zip still the same Cannot Read.
I am using windows 11.

Haven't logged in to XDA in years. Just wanted to say THANK YOU.

mha1021 said:
Thanks for this Guide. But i have issue with Adb sideload update.zip
I downgrade to AUI5 and been using XAA firmware since i bought T-mobile Zfold3.
And since beta was released, I'd been trying to register for OneUI4 in Samsung Memeber app but No Banner or under rBenefit tab.
So saw your guide here and tried to followed your direction but adb sideload fails i get CANNOT READ message.
when i typed adb Devices it shows my device so adb is working but cannot sideload.
when i downloaded the update it was .bin 949981470b3948c3aa05a19e8a2edbd3.bin so i renamed it to .zip, i got the CANNOT READ message then renamed it to update.zip still the same Cannot Read.
I am using windows 11.
Click to expand...
Click to collapse
Don't rename the file.
What I always do with adb related stuff is put it in the root of my C drive. So it would be
Code:
C:\adb\platform-tools\
Then put the .bin file in here as well.
After that open cmd and do
Code:
cd C:\adb\platform-tools\
and hit enter.
After that do adb sideload 94 and hit tab so it should autofill the name of the update file.
Let me know if you have any questions.

Thanks for the instructions as they worked for me. I did receive an error before it finished at "(~94%) adb: failed to read command: No error". Phone booted and the system is showing One UI version 4.0, Android Version 12.
QUESTION though. What is up with the difference in Baseband version? I am seeing the official release having the last 2 digits of "JF" but on the phone just flashed, it is showing "JH".
For reference, complete Baseband version: F929U1UEU1ZUJH after flashing. Might just be my ignorance but thought I would ask.
Thoughts? And thank you again!

AlexMartin00 said:
Thanks for the instructions as they worked for me. I did receive an error before it finished at "(~94%) adb: failed to read command: No error". Phone booted and the system is showing One UI version 4.0, Android Version 12.
QUESTION though. What is up with the difference in Baseband version? I am seeing the official release having the last 2 digits of "JF" but on the phone just flashed, it is showing "JH".
For reference, complete Baseband version: F929U1UEU1ZUJH after flashing. Might just be my ignorance but thought I would ask.
Thoughts? And thank you again!
Click to expand...
Click to collapse
The baseband is just something that gets updated, so ZUJH is the Android 12 beta firmware. Every time you update your firmware the baseband gets updated as well.
More technical: Baseband is firmware that controls all radio devices on the phone, including GPS, Wi-Fi, Bluetooth, NFC, cellular data, and more.

Will this work on att Galaxy fold 3 since I can't get update cause att blocks it.

Hero_is_Over said:
This is what I did to get the new beta. Feel free to tell me how dumb I am for allowing noobies to try the beta, but the more the merrier and they should know the risks....
RISKS: Phone may not be as stable as before and you will lose all your apps and data. Camera is bugged for me
1. BACK UP YOUR CURRENT BUILD USING SMART SWITCH. THIS WILL WIPE DALVIK/CACHE/DATA. Get SmartSwitch for PC HERE
2. Download Samsung Drivers for ADB/ODIN HERE
3. If you are on firmware ending in AUI5 for the CSC version XAA then skip to step #6 . If you are not, then download the respective firmware HERE
Also Download Patched ODIN (Patched version will be less scrutinous) HERE
4. Unzip the firmware you just downloaded as well as the Patched Odin. Run ODIN and add the BL, AP, CP, Home_CSC from the unzipped firmware to the corresponding locations in ODIN
5. Turn off phone and boot into "Download Mode" by first holding Volume +/- buttons and then hold the Power button. Now plug in your phone to your PC and you will see the first small grey square in the upper left side of ODIN turn light blue (if it does not, you have issues with either the cable or drivers).
Proceed in flashing the device by simply clicking the "Start" button.
Once it is done and your phone has rebooted... Make sure that you complete the setup process just in case of authentication issues if the phone isn't already set up
6. Download the OneUI 4 Beta HERE and then download the "15 Second ADB Installer" HERE
7. Install the 15 second adb installer and make sure to allow adb systemwide when asked by the program.
8. Turn off phone. Boot into device by holding Volume Up and then holding Power. This will take you into recovery mode, where you will see the option to "update via ADB sideload".
Use the volume down key to navigate down to that option and press power to initiate the adb sideload function
9. Open command prompt by pressing the Windows key and typing "cmd" (no quotes) and press ENTER.
10. Type into the command prompt (of course remove the quotes) "adb sideload C:\path\to\your\oneui4\zip\file" . For example if I download that file into my Downloads folder, I would then type "adb sideload C:\Users\MyPC\Downloads\949981470b3948c3aa05a19e8a2edbd3.zip"
Click to expand...
Click to collapse
hi I'm getting a status 1 error with my sideload

erneyone said:
hi I'm getting a status 1 error with my sideload
Click to expand...
Click to collapse
What does the error say?

I keep getting cannot read '949981470b3948c3aa05a19e8a2edbd3.bin and I do have the file on my ADB folder which is on the C drive i don't know if it matter but I'm using a windows 11 laptop

zimgir124 said:
What does the error say?
Click to expand...
Click to collapse
Status 1

Is there a mirror for the beta download anywhere? It looks like the link isn't working for me.

ElGuyarc said:
I keep getting cannot read '949981470b3948c3aa05a19e8a2edbd3.bin and I do have the file on my ADB folder which is on the C drive i don't know if it matter but I'm using a windows 11 laptop
Click to expand...
Click to collapse
was getting the cannot read error too.. the problem is the outdated adb version installed from the 15 second adb link in the op
download this:
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com

Dick_Stickitinski said:
was getting the cannot read error too.. the problem is the outdated adb version installed from the 15 second adb link in the op
download this:
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com
Click to expand...
Click to collapse
thank you so much...

I updated my SM-F926U1 with the Beta 4 its really buggy for me
Just want to get my facts straight. Can I just flash back to non-beta ?
What will happen to my Beta status will I still be able to OTA update when the next beta comes out ?

I have updated this with the newer adb binary install guide. I use the latest binaries from Android Studio and add them to path manually so I didnt know the 15 second installer was that outdated
Also yes you can downgrade by flashing the AUI5 that I posted in the guide

Hero_is_Over said:
I have updated this with the newer adb binary install guide. I use the latest binaries from Android Studio and add them to path manually so I didnt know the 15 second installer was that outdated
Also yes you can downgrade by flashing the AUI5 that I posted in the guide
Click to expand...
Click to collapse
Is it a good idea to wipe my data when doing an downgrade like this ?

Hero_is_Over said:
I have updated this with the newer adb binary install guide. I use the latest binaries from Android Studio and add them to path manually so I didnt know the 15 second installer was that outdated
Also yes you can downgrade by flashing the AUI5 that I posted in the guide
Click to expand...
Click to collapse
I thought you can't flash a previous version of Android once you're on the higher version?

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%.