Database Info

[GUIDE] How to install any A1 rom into the 5X.

I'm not a native english speaker, so my grammar may not be perfect. Corrections are highly appreciated.
In this guide I will explain step by step how you can install almost any A1 rom into the 5X. You will need a PC, no matter if it's running Windows, Linux, or OSX.
Step 0. Unlock your bootloader.
Step 1. Download Android Platform Tools. Extract it somewhere, and then add them to the path (If you dont know how: https://www.computerhope.com/issues/ch000549.htm Just remember to add the correct path to where you extracted APT).
Step 2. Download and flash modded TWRP.
Step 3. Download A1 ROM. Extract it and open the folder. You will see lots of scripts and another folder called images. Just stay on the main folder (Where all the scripts are placed).
Step 4. Download correspondent flash script and place it among the other scripts.
Windows: https://pastebin.com/raw/g3HTtVHs (Save it as flash_5x.bat)
Linux: https://pastebin.com/raw/2cvRb3gn (Save it as flash_5x.sh)
Step 5. Put your phone into fastboot mode (While powered off, keep pressed vol down button and power button. Connect your phone to the computer using your USB cable. Execute the downloaded script.
Step 6. When it finishes flashing the rom, you will be prompted to press a key to continue. Hold volume up button on the phone, and then press any key on the computer to continue and reboot the phone. Holding vol up will make your phone to boot into recovery.
Step 7. Once on TWRP, swipe to allow modifications if prompted. Then, go to wipe > advanced wipe and wipe dalvik and cache. If this is your first time installing the rom (not updating) you should wipe data partition too. Once wiped, go back to Advanced tab, then press on Terminal. Write "a1to5x" and tap on Enter. Wait until it finishes.
Thats all, just reboot and enjoy your updated ROM.
You can also flash modded roms, for doing so, you will need to extract payload.bin (which is inside the rom zip file) using this script and manually flash correspondent partitions. Then skip to step 7.

extracting the payload.bin doesn't work with the payload_dumper.py script for me. (copied script into bat). Can you help please?

Could you make a guide to install cuatom rom from mi a1 step by step? Tank

Is this method works with A1 custom kernels too?

please guide us also. thanks
---------- Post added at 02:36 AM ---------- Previous post was at 01:49 AM ----------
dumper for windows not working; already installed python

Successfully flash the latest A1 rom on my new bought 5X.
Thanks a lot!

sorry, I did not understand how to use this script to extract the custom roms, can you help me?

Hi, you have two guides to flash mia1 roms in 5x:
this one: https://forum.xda-developers.com/mi-5x/how-to/guide-how-to-install-a1-rom-5x-t3777139
and other one: https://forum.xda-developers.com/mi-5x/development/rom-android-one-mi5x-t3760048
wich are de differences between both?

nogard_ said:
Hi, you have two guides to flash mia1 roms in 5x:
this one: https://forum.xda-developers.com/mi-5x/how-to/guide-how-to-install-a1-rom-5x-t3777139
and other one: https://forum.xda-developers.com/mi-5x/development/rom-android-one-mi5x-t3760048
wich are de differences between both?
Click to expand...
Click to collapse
This thread guides you how to flash the official A1 rom to X5. So with this guidance, you can always flash the latest A1 rom to X5 without waiting for a ported rom made by other guys.
The another thread is regarding how to flash a ported rom. And the rom mentioned in that thread has already been out of dated.

@Aex12, do you have payload_dumper.py for windows, tried the above script but it got "Module not Found error", thank you.

Aex12 said:
Step 1. Download Android Platform Tools. Extract it somewhere, and then add them to the path (if you don't know how to do this, just google it).
Click to expand...
Click to collapse
What's the meaning of "add them to the path"?!
I googled it but nothing found!

>Step 0. Unlock your bootloader.
Is this necessary, I can't do it.

will i get OTA updates ?

tuhi009 said:
will i get OTA updates ?
Click to expand...
Click to collapse
OTA updates won't install, you have download the new ROM from mi.com and install.

I also want to know this! Please someone explain.
bandicout said:
sorry, I did not understand how to use this script to extract the custom roms, can you help me?
Click to expand...
Click to collapse

All process was successful, but i have problems with 4g. there are any problem with this type of connection and this method to convert 5x to a1? or it's a configuration problem?

Scorpion70 said:
What's the meaning of "add them to the path"?!
I googled it but nothing found!
Click to expand...
Click to collapse
Aex12 said:
Step 1. Download Android Platform Tools. Extract it somewhere, and then add them to the path (if you don't know how to do this, just google it).
Click to expand...
Click to collapse
Can you please just explain how it's done? Have googled it but didn't see anything. And after doing the whole installation can I install Gcam on it?

please help me how to extract payload.bin (which is inside the rom zip file) using this script. tks bro.

datkieu96 said:
please help me how to extract payload.bin (which is inside the rom zip file) using this script. tks bro.
Click to expand...
Click to collapse
U need to run script in linux machine with phyton installed.
Comand:./payload_dumper.py payload.bin

Please port the latest pixel experience ?

[ROOT]Root Guide for Huawei MediaPad M5

DISCLAIMER: I'm not responsible for anything that happens to your device. Use the steps below at your own risk . Be mindful of the facts unlocking bootloader voids your warranty and also hard resets your device - ALL YOUR DATA, SETTINGS, FILES AND APPS WILL BE DELETED. Rooting your device voids warranty as well. I own the Chinese SHT-AL09 8.4" LTE device and tested this root procedure ONLY WITH THIS MODEL. However, I believe there is a good chance the steps below will work for all other models of MediaPad M5, including WiFi only variants and 10" models. You MUST unlock your bootloader first. Do NOT use ramdisk image I provide in the steps below for any other model besides SHT-AL09 - doing so is guaranteed to render your device unusable. Ramdisk I provided is ONLY for SHT-AL09. You will need to extract your own ramdisk from stock firmware, specific to your device model
Credits:
@Wirmpolter - this root method largely based on his Magisk guide for Mate 9
@topjohnwu for creating the awesome Magisk Manager, which was used to patch ramdisk image with superuser binary
People, who created HuaweiUpdateExtractor
@magnumlove who pointed me in the right for developing root method in this post
This site, for hosting stock firmware for Huawei MediaPad M5
1. First, you will need to unlock the bootloader of your M5. Follow this guide
2. Transfer this patched ramdisk image to your device
Note for users with version of M5 other than SHT-AL09: Do NOT use the above ramdisk image. Download the full stock rom (update.zip) from the site I linked in the credits. Extract UPDATE.APP file from the zip. Then use HuaweiUpdateExtractor to extract ramdisk.img specific to your device. If you get errors in HuaweiUpdateExtractor - uncheck first 2 checkboxes for checksum verification on Settings tab and try again
3. Once bootloader is unlocked, install latest Magisk Manager from the official Magisk thread
4. Once Magisk Manager gives you a pop-up prompt to either download Magisk zip or patch the boot image file - chose to patch the boot image, but instead of boot.img select ramdisk.img from step 2. Magisk Manager should give you a message the image was successfully patched. It will be saved as patched_boot.img in MagiskManager folder on your sdcard. If it does not say success - do NOT proceed
5. Transfer the newly created patched_boot.img back to your PC
6. If you already have ADB and Fastboot tools installed on your PC you can just use what you've got. If not - get them from here
7. Connect your M5 to PC via USB cable
8. Run command prompt. If your ADB and Fastboot are installed as system app - you can do this from any path in CMD. If not - you need to switch in CMD to your ADB and Fastboot folder. Either way, the patched ramdisk patched_boot.img file must be in the same path, from which you will be running commands below in CMD window
9. Type "adb " in CMD window to start android debug bridge
10. Type "adb reboot-bootloader" and wait until your device restarts in Download mode
11. Once in Download mode, type "fastboot flash ramdisk patched_boot.img" - you should see some output from flash procedure, indicating successful flash
12. Once patched ramdisk is flashed, type "fastboot reboot"
That is it - you're done. Once your device reboots it will be rooted.
Note 1: Magisk Manager has it's own built-in superuser app and uses Systemless root, which works completely differently - you will not see external, standalone app like SuperSU or SU you might be familiar with in your App Drawer. The way to control the superuser app is from Magisk Manager itself: Settings->Superuser section
Note 2: I don't do tech support via PM, so don't PM me for help or with questions. Use the thread instead, and some other XDA members or myself will probably help you. Good luck!
Note 3: You may find some links to Huawei stock firmware in the 2nd post
UPDATE - August 6, 2018
Huawei officially approved 8.0.0.171 firmware with GPU Turbo for installation on SHT-AL09 devices. If you're doing first time root - just follow the original steps above. If you are already rooted and want to upgrade to 8.0.0.171 - follow the steps below:
1. Boot into download mode:
Code:
adb reboot-bootloader
from CMD window
2. Flash stock recovery from 8.0.0.171 to your device in fastboot:
Code:
fastboot flash recovery_ramdisk recovery_ramdis.img
3. Download and install the official OTA through Settings (full or just the update)
4. Boot into download mode again and flash patched ramdisk from 8.0.0.171
Code:
fastboot flash ramdisk patched_boot.img
5. OPTIONAL: If you were using TWRP or any custom recovery - you will need to reflash it back
Code:
fastboot flash recovery_ramdisk twrp.img
or whatever you named your custom recovery image
REMINDER: Do NOT use ramdisk image I provided for any other model besides SHT-AL09 - doing so is guaranteed to render your device unusable. This patched ramdisk is ONLY for SHT-AL09. You will need to extract your own ramdisk from stock firmware, specific to your device model
Needless to say, all the images you are going to flash must reside in the same directory, from which you are going to be running the CMD commands. If your ADB/Fastboot folder is not in your WIndows' PATH environmental variable - the images must be placed in the same folder where ADB/Fastboot binaries are, and CMD commands must be run from that folder.

C5Longhorn said:
Yes, they still work. I have the same model and build as you and I'm rooted.
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
I'm considering buying an SHT-W09 with firmware version 8.0.0.200 (C567), but I'd like to know if I can root it first. I do not know if the bootloader has been unlocked. Since you have the same version, can you confirm that it's possible to unlock and root, and if so, sketch out how it's done? I'm confused about whether it's possible with this firmware.

samiller said:
I'm considering buying an SHT-W09 with firmware version 8.0.0.200 (C567), but I'd like to know if I can root it first. I do not know if the bootloader has been unlocked. Since you have the same version, can you confirm that it's possible to unlock and root, and if so, sketch out how it's done? I'm confused about whether it's possible with this firmware.
Click to expand...
Click to collapse
Unlocking is possible *only* if you've gotten already your unlock code. As this service was suspended about 2 years ago there is no easy way to get it unlocked.

Small request to developers, or people with access to reliable file hosting: I don't have a developer account, so all the files I linked or referenced in the OP are hosted on free hosting sites. That file hosting has expiration date and max downloads limit, so the files will become inaccessible sooner rather than later. Please upload these files to reliable hosting and create a post with the links. I will link your post in the OP as a mirror.
In the meantime, mirror for SHT-W09 firmware: https://mega.nz/#!asVjmZrR!bW2OmXgTjnyVN4pqb9fA7OzAJ4bzil7YZxNW14qoCmk

I can confirm that this works on the 10.8" wifi model using the devices relevant ramdisk.img.

Hello, can somebody test sixaxis controller tool with root and magisk? There is a Trial in Google Play Store, that is called sixaxis compatibility checker without purchise the App. Maybe i want to buy the Tablet, but only with Dualshock 4 Support...

Just a heads up, been following threads on this forum for flashing a GSI. Now that you guys can root, you can also make backups of your own stock system image if you can't find one from Firmware Finder. Then you can safely try flashing the GSI.

@MishaalRahman well it's bit like chicken egg dilemma. As we do not have a stock system image for e.g. SHT-W09 we cannot patch the ramdisk.img and so we cannot get the stock system image ...

Thanks Apo11on, great to have root so soon for the M5! Do you know if there's a way to get Xposed working? I tried the Xposed Framework SDK 26 from inside Magisk, but it put me in a boot loop.

Question is, for those of us with the Non Pro version, can this still be done.

@OHP Yes. The OP did it with the 8.4" version which has no pro option.
I'm looking to buy the Chinese 10" wifi version myself but need Google Play Store + Services on it which I'm guessing the Chinese version doesn't have. Is one of the firmwares at the website you link to a global version of the firmware that will work on this model?

OHP said:
Question is, for those of us with the Non Pro version, can this still be done.
Click to expand...
Click to collapse
Doesn't matter what version you have as long as you have access to your device firmware and the ramdisk.img. You really need to reread the guide.

magnumlove said:
Doesn't matter what version you have as long as you have access to your device firmware and the ramdisk.img. You really need to reread the guide.
Click to expand...
Click to collapse
Problem I have is :
CMR-W09C432B123 (8.0.0.123) from download headlines.
notice the Bold letter.
my Firmware on device:
CMR-W09C432123 (8.0.0.123)
obliviously it could be nothing but I wouldn't want to brick my tablet :fingers-crossed:

OHP said:
Problem I have is :
CMR-W09C432B123 (8.0.0.123) from download headlines.
notice the Bold letter.
my Firmware on device:
CMR-W09C432123 (8.0.0.123)
obliviously it could be nothing but I wouldn't want to brick my tablet :fingers-crossed:
Click to expand...
Click to collapse
I have exactly the same tablet/firmware as you and it was fine. The additional letter also threw me a little. But if you are unsure, download Huawei Firmware Finder from Google play and it will automatically detect your tablets firmware (which you can download if you wish).

magnumlove said:
I have exactly the same tablet/firmware as you and it was fine. The additional letter also threw me a little. But if you are unsure, download Huawei Firmware Finder from Google play and it will automatically detect your tablets firmware (which you can download if you wish).
Click to expand...
Click to collapse
I took the plunge, and I am sucessfully rooted now :silly:

struggling with this part
2. Transfer this patched ramdisk image to your device
Note for users with version of M5 other than SHT-AL09: Do NOT use the above ramdisk image. Download the full stock rom (update.zip) from the site I linked in the credits. Extract UPDATE.APP file from the zip. Then use HuaweiUpdateExtractor to extract ramdisk.img specific to your device. If you get errors in HuaweiUpdateExtractor - uncheck first 2 checkboxes for checksum verification on Settings tab and try again
I have a CMR-W09 :s i can got the files downloaded and the huwai software not sure how i make a img

The good news is I followed these instructions yesterday and they worked perfectly (SHT-AL09).
The bad news is, I seem to have lost root overnight.
---------- Post added at 06:41 AM ---------- Previous post was at 06:22 AM ----------
And I figured out why I lost root; I was playing around with Developer options and switched the default GPU renderer from 'default' to 'Skia.' Apparently, this disables root access until you switch back. I regained root access on a reboot, lost it again after switching back to Skia, and then regained it after switching back to default.

I got the right image file from the site and huwai extract. I have googled how to use this app but what files do I extract as there appears to be. Alot ? I extracted all of them ? I don't have a ramdisk.img
Also thanks for writting this up. Without it I would be lost

Thanks for the efforts making this thread. Unfortunately my device is SHT-W09 and I'm still waiting for the right firmware. Is there anything I can help, considering I have the device?

@dkk6 I am in the same boat as you. Unfortunately I installed the update to 8.0.0 123 without having the Firmware Finder installed on the device. Do you have installed already the update to 8.0.0 123?
If not, you could install Firmware Finder and provide us with the ota url ...

This works perfectly no issues. i had some how maanged to download the wrong rom first. AND thankfully it did not have a ramdisk in. it is important that your firmware matches the firmware present on the site as explained. This was easy guide to follow now to flash it with somthing other then andriod

AndDiSa said:
@dkk6 I am in the same boat as you. Unfortunately I installed the update to 8.0.0 123 without having the Firmware Finder installed on the device. Do you have installed already the update to 8.0.0 123?
If not, you could install Firmware Finder and provide us with the ota url ...
Click to expand...
Click to collapse
I'm on 8.0.0.101

[Guide] How to install a GSI treble rom on our Daisy - Updated [5.11.18] - More easy.

This guide lets you install any GSI treble roms on our Daisy.
Read carefully and go step by step!
Update: Since Havoc OS doesn´t need permissive Kernel, I just installed the latest stock rom (9.6.9.0), flashed Havoc, set everything up and ended with sh...t... Camera´s not working, Opera freezes, everything sucks. It was a waste of time... So it´s still the situation:
If you want to use a custom GSI-Rom Only use this combination: Stock rom before flashing GSI: 9.6.4.0 and Kernel: Unofficial TWRP by Yshalsager - this combination works like a charm​
Let´s get started: Be sure you are on Stock 9.6.4.0 (july security patch) if not, your wifi will not work in treble rom!
1) Download latest AB arm 64 gsi build. - ONLY ARM 64 AB GSI WILL WORK!
2) If you don´t have fastboot and adb download it from here: https://forum.xda-developers.com/sho....php?t=2588979 and install it!
3) Extract gsi64-ab-image to adb folder and rename it to system.img
4.a) Windows 7: right klick on white space in your adb-folder: open command prompt here
4.b) Windows 10: open command prompt as admin and navigate to your adb folder
5.) Power off your Smartphone and press pwr and vol- together -> your screen will show FASTBOOT - connect your phone to your PC
6.) type in your command prompt
Code:
fastboot oem unlock
Important: this will format your SD - All data will be lost If you perform that step! -> Backup before!​7.) Phone will reboot, erase data and boot up. Power off again after boot up. Power + vol- to enter fastboot.
Now you have to decide: If you want to use Android 9 roms and TWRP together, you have to decrypt your data - else TWRP will not be able to read data! If you don´t care continue on step 11​
8.) Download a patched_boot.img and place it in your fastboot folder - since only 9.6.4.0 works without bugs, you have to choose the patched 9.6.4.0 boot
9)
Code:
fastboot boot patched_boot.img
10) Connect to internet and update Magisk manager, download a root explorer - you could use this and go to
/vendor/etc/ and open the file fstab.qcom in editor​replace the text "forceencryption=footer with "encryptable=footer" and reboot to bootloader​
11) Download this, rename it to boot.img and copy it to your fastboot folder
Code:
fastboot flash boot boot.img
12) Install official TWRP
13) After installing official TWRP reboot to TWRP agian and go to "wipe" -> "format data" and type "yes". Reboot to bootloader
14.) Download your GSI AB Image and place it in your fastboot folder
Code:
fastboot flash system [imagename].img
If you want, you can boot now to twrp and install magisk and/or gapps whatever - everything will work. Else you boot up your new system - Sometimes your GSI-rom will not boot up without a rooted kernel.
So if you stay in bootloop, just install magisk.zip!
Violla - Now you have a treble gsi rom on your Mi A2 Lite!

theres working twrp out for daisy, does this change anything refering to your first line:
"1) Download latest AB arm 64 gsi build. I would always use the gappsed version - twrp still not running for daisy... - ONLY ARM 64 AB GSI WILL WORK!"

thanks for the guide!
i really want to try this but im not sure which rom fully works. Also i'm not sure to do this without TWRP cause i'd like to have a complete backup of my device.

i'm in 9.6.9 version now with locked bootloader and unrooted
any suggests for me to try this rom

tutankpusch said:
theres working twrp out for daisy, does this change anything refering to your first line:
"1) Download latest AB arm 64 gsi build. I would always use the gappsed version - twrp still not running for daisy... - ONLY ARM 64 AB GSI WILL WORK!"
Click to expand...
Click to collapse
Updated: I removed that line...

merlin.berlin said:
thanks for the guide!
i really want to try this but im not sure which rom fully works. Also i'm not sure to do this without TWRP cause i'd like to have a complete backup of my device.
Click to expand...
Click to collapse
No problem - meanwhile there´s a official twrp here - and you can still use this guide
If you want to flash havoc 2.0 - I think it´s the best rom on earth , you will need to change your kernel to permissive that it will boot. To do that, read the thread there´s a vivid discussion how to do it...
elkhshap said:
i'm in 9.6.9 version now with locked bootloader and unrooted
any suggests for me to try this rom
Click to expand...
Click to collapse
If you like to have more features and/or pie (Android 9), then I would suggest to flash a custom gsi rom. If you can live with stock, I wouldn´t touch it.

Voodoojonny said:
No problem - meanwhile there´s a official twrp here - and you can still use this guide
If you want to flash havoc 2.0 - I think it´s the best rom on earth , you will need to change your kernel to permissive that it will boot. To do that, read the thread there´s a vivid discussion how to do it...
Click to expand...
Click to collapse
i want havoc OS but as i understand i can't use the fastboot method because i need the permissive fix, which only can be installed via TWRP, correct?
i would prefer fastboot over TWRP because all the problems with sdcard reading, encrypting etc.

merlin.berlin said:
i want havoc OS but as i understand i can't use the fastboot method because i need the permissive fix, which only can be installed via TWRP, correct?
i would prefer fastboot over TWRP because all the problems with sdcard reading, encrypting etc.
Click to expand...
Click to collapse
Hi,
there are so many reasons for havoc not to boot... and so less to boot...
BUT... If you won´t mind to use an unencrypted phone or no twrp, you can use (as I think) the best Android OS, havoc.
So think about, what is more important for you: TWRP or encryption.
1. With encryption: (Quite easy)
a) Go to stock 9.6.4.0 - July patch with mi flash and choose clean all (yes you will loose all your data -> back up everything) - Important: don´t install any ota after that!​b) Download latest havoc and place it in your fastboot folder​c) Download this TWRP and place it in your fastboot folder - you need this as Kernel​d) As lazy person, I would rename the havoc file to havoc.img and the twrp file to twrp.img​e) copy userdata.bin from stock to fastboot​
Code:
fastboot flash system havoc.img
Code:
fastboot flash boot twrp.img
Code:
fastboot flash userdata userdata.bin
Code:
fastboot reboot
Wait and wait and wait and violla, you have havoc!
f) Gapps: download gapps, copy it to your fastboot folder and rename it to gapps.zip. Boot to recovery - twrp will not be able to read your data -> skip and allow modifications​
Code:
adb push ./gapps.zip /sdcard
- Now you see gapps in your zip and you can install it!
g) Magisk: for magisk you need to download my patched twrp and place it in your fastboot folder​
Code:
fastboot boot patched_twrp.img
- After booting up, you can go to magisk manager (yes: upgrade first etc.... and install magisk using the "direct method"
2. If you want to remove encryption - then you can use twrp fully, use this guide: here
Important: If you use another stock rom than 9.6.4.0 or do an ota, you will loose wifi!​after doing all the steps:​
Code:
fastboot flash system havoc.img
- that´s it!
Now you can use havoc

Voodoojonny said:
Hi,
there are so many reasons for havoc not to boot... and so less to boot...
BUT... If you won´t mind to use an unencrypted phone or no twrp, you can use (as I think) the best Android OS, havoc.
So think about, what is more important for you: TWRP or encryption.
1. With encryption: (Quite easy)
a) Go to stock 9.6.4.0 - July patch with mi flash and choose clean all (yes you will loose all your data -> back up everything) - Important: don´t install any ota after that!​b) Download latest havoc and place it in your fastboot folder​c) Download this TWRP and place it in your fastboot folder - you need this as Kernel​d) As lazy person, I would rename the havoc file to havoc.img and the twrp file to twrp.img​e) copy userdata.bin from stock to fastboot​
Code:
fastboot flash system havoc.img
Code:
fastboot flash boot twrp.img
Code:
fastboot flash userdata userdata.bin
Code:
fastboot reboot
Wait and wait and wait and violla, you have havoc!
f) Gapps: download gapps, copy it to your fastboot folder and rename it to gapps.zip. Boot to recovery - twrp will not be able to read your data -> skip and allow modifications​
Code:
adb push ./gapps.zip /sdcard
- Now you see gapps in your zip and you can install it!
g) Magisk: for magisk you need to download my patched twrp and place it in your fastboot folder​
Code:
fastboot boot patched_twrp.img
- After booting up, you can go to magisk manager (yes: upgrade first etc.... and install magisk using the "direct method"
2. If you want to remove encryption - then you can use twrp fully, use this guide: here
Important: If you use another stock rom than 9.6.4.0 or do an ota, you will loose wifi!​after doing all the steps:​
Code:
fastboot flash system havoc.img
- that´s it!
Now you can use havoc
Click to expand...
Click to collapse
Please explain by video

thank you so much for this guide:good:
i'll try it later when im home:fingers-crossed:

Where do I find a userdata.bin file?

monzer said:
Where do I find a userdata.bin file?
Click to expand...
Click to collapse
In the Images-Folder of your stockrom after extracting...
- download fastboot stock rom
- extract archive
- look inside "images"
update: it´s userdata.img

Voodoojonny said:
In the Images-Folder of your stockrom after extracting...
- download fastboot stock rom
- extract archive
- look inside "images"
update: it´s userdata.img
Click to expand...
Click to collapse
Please post a video for ease of action

monzer said:
Please post a video for ease of action
Click to expand...
Click to collapse
Sorry, that will not happen!

Updated: view first post. This guide will definitely work well - and it´s easy! At least more easy than the other guides .

Voodoojonny said:
Updated: view first post. This guide will definitely work well - and it´s easy! At least more easy than the other guides .
Click to expand...
Click to collapse
No idea why you're useless taking pot-shots at other people, especially when you keep spreading lies about stock roms because you use a broken recovery. But have it your way.
Just keeping telling people to use a broken/untested recovery and bricking their phones, that forces them to reflash boot images. Can't wait until the bricks pile up.
I'm done with this website.

KezraPlanes said:
No idea why you're useless taking pot-shots at other people, especially when you keep spreading lies about stock roms because you use a broken recovery. But have it your way.
Just keeping telling people to use a broken/untested recovery and bricking their phones, that forces them to reflash boot images. Can't wait until the bricks pile up.
I'm done with this website.
Click to expand...
Click to collapse
If you would read, you would have noticed, that that broken and untested recovery is used as kernel, becouse it works great as kernel for gsi roms. Within the process it will be upgreaded by official twrp.
I spend a lot time, testing how to install custom roms on this phone, becouse I don't like like stock and I share my experience with others. Noone will break his phone with this! Perhaps you can try before complaining.

KezraPlanes said:
No idea why you're useless taking pot-shots at other people, especially when you keep spreading lies about stock roms because you use a broken recovery. But have it your way.
Just keeping telling people to use a broken/untested recovery and bricking their phones, that forces them to reflash boot images. Can't wait until the bricks pile up.
I'm done with this website.
Click to expand...
Click to collapse
Voodoojonny said:
If you would read, you would have noticed, that that broken and untested recovery is used as kernel, becouse it works great as kernel for gsi roms. Within the process it will be upgreaded by official twrp.
I spend a lot time, testing how to install custom roms on this phone, becouse I don't like like stock and I share my experience with others. Noone will break his phone with this! Perhaps you can try before complaining.
Click to expand...
Click to collapse
Lol, this site has gone way down hill... It's almost a joke now.
So many people asking for the 'easy' way and want answers to easily searchable questions. Sooo many multiple posts, and people not wanting to do the research themselves. How many threads need to be created on bricked devices because you didn't heed the warnings or follow the directions...
I wonder if xda even cares? This place use to be a great tool for the ones who like to tinker.
There are definitely a few folks keeping the spirit alive, but so many unnecessary posts - like what I'm writing right now...
Anyway thanks to anyone who puts time and effort for the greater good, we should all understand that tinkering with our devices can potentially have adverse effects.

Thanks for this noob friendly guide! a massive thanks! But hotspot still not working. Haven't tried the gcam but the stock camera is working but has no portrait and other features. The havoc os 2.0 looks snappy and buggy. Ill try other treble roms in few days
Any suggestions?

Bokoko006 said:
Thanks for this noob friendly guide! a massive thanks! But hotspot still not working. Haven't tried the gcam but the stock camera is working but has no portrait and other features. The havoc os 2.0 looks snappy and buggy. Ill try other treble roms in few days
Any suggestions?
Click to expand...
Click to collapse
You're welcome. Don't have problems with bugs and havoc 2.0... Interesting to test would be arrow pie! Benzo had problems with camera and flashlight... All the 8.1 can't handle the notch and overlay!

Alcatel Tetra AIO (start here)

Alcatel Tetra (5041C) All In One Thread
##############################################################################
UPDATE: 4-20 2020 added direct link to folder with free tools for linux and windows
new Url for our site with the tools and roms:
https://a-team-solutions-downloads.myddns.rocks/Site/ UPDATED 4-20 2020
this is active as of 2/26/20
OUR TG Chat Group for all our best advice and where our book of development Notes live,
Check it out.
https://t.me/Android_General_Chat UPDATE: still live on 4-20 2020
UPDATE:
direct shortcut to free version of our AIOtoolkit tools
Live on 4-20 2020
https://a-team-solutions-downloads.myddns.rocks/Free/AIO-ToolKit/
###############################################################################
This is where you want to start for the Alcatel tetra,
Here you will get root ,
You will get the latest fastboot fix to get a custom recovery and bootloader unlock,
Learn how to flash a gsi on the tetra and get it working correctly.
You will see our tool to get magisk working correctly on a pie gsi 's
You may find gsi images here that are modded to be device specific for the tetra.
You will find links to a device support group where u can get help with trouble shooting if you get into a jam.
And you will find access to a factory tool to unbrick a tetra in the last resort.
There will be no disrespectful language in this thread.
It will not be tolerated here you will be reported to the moderation team if you post
disrespectful/flame-war comments here.
This is not a general discussion thread.
This is The place to find everything you need for your tetra :
ROMs
Recovery
Mods/flashable zips
And precise correct instructions for the use of these.
Disclaimer :
I nor anyone at XDA nor any of the devs who's work you find here are responsible for your actions in choosing to use the tools and methods laid out in this thread.
If you follow the instructions here ,
you do so at
You're Own Risk.....
Bricks and loss of data may happen to your device as a result
You have been warned.
This thread is a work in progress please be patient.
Credits go to :
@diplomatic for mtk-su and his awesome kernel exploitation work which allowed me write access to the device partitions ! Thanks Man!
@clcombs262 for opening the old root question thread that got my associates and I together to work on this device!
@PizzaG for his work on this device, his trick for SugarMTK to get lk downgrade in the beginning. and giving us Sugar MTK login so we can use it to restore the countless times we bricked developing all of this stuff. You're Awesome Bro !
@Spades99 for tinkering and getting hotspot working without a plan on oreo roms , good Idea Bro!
@topjohnwu for magisk and all the wonderful things we get from that!
@AndyYan for the LOS 16 build I modified to be my daily driver rom.
@phhusson For his excellent work on the treble-project and for giving us gsi's to play with. Thanks Man You Rule!
@LgPWN'd For Fastboot-fix, Magisk-Gsi-Helper.zip, porting P.B.R.P and Red-wolf custom recoveries, fixing adb (kinda) in twrp.
and just about everything else...
Special thanks to a lady called Alexandria and @clcombs262 for getting me access to a server to build roms/recoveries for these devices . Hey Thanks A Million You are the Stuff !!!
Twrp Builder for the fist port of twrp for tetra

Fastboot fix:
Fastboot fix:
So most users don't have fastboot access
We have a fix for this.
Ok the very first thing you're going to want to do is gain some type of temporary root shell so that we can downgrade the bootloader by writing directly to the partition so that we can then issue a command to reboot to bootloader and use fastboot to unlock your bootloader and we're going to want to do that without using sugar mtk so that we don't end up with our unlocked device from eBay being relocked like a brand-new Tetra from Walmart.
So we are going to be using a kernel exploit called mtk-su to gain the temp root access.
Here is the kit
https://drive.google.com/open?id=1JfLzT6F66yBj6Qor_t4P9340CwLz5Y18
Instructions For Windows Users:
Instructions from a booted Tetra that has no reboot to fastboot functionality:
Extract this zip.
open the folder location in a terminel/CMD/Powershell window...
enable developers options.> enable OEM unlocking.>enable USB debugging
make sure the drivers are installed for your phone on windows {likely they are }
first get device recognized by adb
./adb devices
accept the prompt on the device.
after this move on
copy paste these commands one by one into terminal...
Code:
./adb push exploit /data/local/tmp/exploit
Code:
./adb push U8M8Y0Y0CT00.mbn /data/local/tmp/lk.bin
Code:
./adb shell chmod +x /data/local/tmp/exploit
Code:
./data/local/tmp/exploit
NOTE: the file exploit is just Mtk-SU renamed to " exploit "
Wait for it to say new UID 0
should now see # instead of $ in the prompt...
then type this command
Code:
dd if=/data/local/tmp/lk.bin of=/dev/block/platform/bootdevice/by-name/lk
after that completes type this...
Code:
reboot bootloader
Now you should see the fastboot prompt...
ENJOY
Instructions For Linux Users:
instructions for linux are the same except,
remove the
Code:
./
from each adb command...

Unlocking the bootloader
Unlock bootloader:
WARNING THIS WILL ERASE ALL OF YOUR DATA
Well this is done the same as any other device with fastboot.
here's how for the neewbz out there.
Code:
fastboot oem unlock
then confirm by pressing the volume-up key on the device
and then type this code to reboot...
Code:
fastboot continue
Let your device fully boot up then go through the setup wizard again {I always skip through it} and re-enable developers options and adb debugging.
Your bootloader should now be unlocked and you will see a warning message each time it boots. this warning can safely be ignored, In fact it can also be removed completely but that's a subject for a different topic.
NOTE:
though your bootloader is unlocked there are 2 files inside the device that will replace your recovery with the stock one on boot if you don't remove them, but you also have to disable dm-varity in the fstab before you remove the files or you'll get a soft brick.
Fstab lives in /vendor/etc partition
the easiest way for most users to fix this is to follow the instructions in this gsi prep package by @PizzaG ,
https://drive.google.com/file/d/1ir_S_fEX3SU3G-Fk7-YFl2z5NXfsIJ5l/view
the thing to remember is that you only need the backup to restore from his package, and DO NOT DO the LK DOWNGRADE from his package it's old and uses sugar MTK to replace LK and it messes up network stuff in the process.
You already completed the LK downgrade if you followed my instructions in the last post.
You should be ready to flash the recovery of your choice, do a backup from that recovery and then follow PizzaG's instructions on how to replace your backup with his one.
then if you wanted cricket-rom restore it all if not just restore /vendor and /system to get gsi working and fstab fixes and to auto remove the files that are in stock system to replace recovery on booting

Flashing the custom recovery
Flashing recovery and choices of recovery:
You can use any recovery that yourself or anyone else ports to the Tetra.
The TWRP images in the pizzaG package work but adb is broken in those.
So if you want TWRP that has ADB functionality "sideload etc."
grab the version here:
https://forum.xda-developers.com/showpost.php?p=79815342&postcount=253
Other Better Alternatives:
Pitch Black Recovery Project Ported By LgPWN'd:
https://forum.xda-developers.com/android/development/unoficial-pitchblack-recovery-alcatel-t3946122
Red-Wolf recovery ported by LgPWN'd:
https://forum.xda-developers.com/android/development/red-wolfrecovery-alcatel-tetra-5041c-t3946121
So Choose your recovery, and flash it in fastboot...
Code:
fastboot flash recovery recovery-file-name
Example :
Code:
fastboot flash recovery TWRP.Tetra.img
after this to get to recovery without booting all the way back to system
Code:
fastboot oem reboot-recovery
You should now be in a custom recovery environment .
Remember if u want to use userdata partition u need to disable variety in fstab mentioned earlier, and u need to format data to f2fs to
Kill the encryption and then reboot to recovery to be able to use data partition.
Also there is a file that will cause the stock recovery to over write your custom one.
/system/bin/install-recovery.sh
Rename it or delete it from custom recovery before rebooting
Also some people have had errors using the menu to format data
From the p.b.r.p port.
If it happens to you, try it from one of the twrp images in pizzaG prep package
The older version works when the newer ones don't sometimes
Enjoy !

ROMs:
Most of the ones listed Here are good :
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
the thing to remember is that you need an image for an Arm A-only Device

How to root the Tetra
Reserved
To root or not to root....?
How to root the Tetra.
To root the tetra, follow up instructions to unlock Bootloader flash recovery
then flash your choice of root.zip
When using LOS roms I prefer to use the addon-su from LiniageOS extras
{google search that ^^^} which works out of box just flash and reboot
or you can also use Magisk which is many peoples favorite.
But to get magisk to work you'll need a few things,
first the latest magisk zip to flash, secondly to get it to show you a root prompt in gsi's you'll need to add back some missing library files.
Luckily Myself and @PizzaG have made a flashable zip that can be flashed from custom recovery to do just that.
It'll be in the attachments to this post.
AND NO THIS MAGISK FIXER WILL NOT WORK FOR ANYTHING BUT A TETRA 5041C !!!
so to get magisk running:
first flash :
Magisk_17.2+(GSI_Android_9-Helper)[7-12-2019].zip
then reboot back to recovery,
then flash magisk latest zip
reboot and enjoy root

Gapps to flash or not to flash....?
This is solely up to personal preference.
some users like google and the convenience of google apps,
some users Absolutely abhor Google and all of it's policies and data collection.
Where to get Google apps.
https://opengapps.org/
How to make them work with custom rom/GSI .
there's a great article on it already here:
https://www.xda-developers.com/how-to-fix-device-not-certified-by-google-error/

Support Group
Device support:
Where to get help FAST if you're stuck.
We are doing most of our development work on a telegram group, here's the links for that, come ask questions, grab latest updates before they are released here on XDA etc.
https://t.me/Android_General_Chat
EDIT: URL FIXED TO POINT TO CORRECT PLACE 03/08/2020

A word about Carriers and networks
lock/unlock status:
Carriers or other third parties that have unlocked your tetra have done so by manipulating the data contained in your NVRAM and NVCONFIG and Simlock partitions....
so you can factory reset , flash boot.img or system.img or vendor.img and still retain your unlock, though you may need to adjust your APN settings depending on your choice of ROM.
How to keep from accidentally re-locking your network:
The only way this happens is when you flash those protected OEM partitions or corrupt the data in said partitions.
The sure-fire way to relock a tetra to At&t is to flash / upgrade it using SugarMTK tool
as it flashes EVERY partition with the latest stock released from the server in china or where-ever.
What you can do if it happens to you....
There's not a lot you can do about it. Your carrier will likely refuse to help, at least thats what other users have reported to me.
What you can do is contact any reputable Unlocking service and most times they can re-un-lock it for you.
BUT NOTE: you want to use someone that has the cable-unlocks via pc and usb cable, not the ones who offer some code as your device likely will never ask for the code if you changed things to get this far.
And
Why we can't discuss it further here...
WELP, the big deal here is liability and the Forum rules of XDA.
We are not to discus these things because they actively seek to bypass Carrier Network Restrictions
and as such it's against XDA rules.
However if you find yourself in this position, you might want to contact someone at our device support group for help/advice as we have had to fix this situation before.
we can at least point you in the right direction,
since here on XDA i'm not allowed to Promote/recommend anyone to help fix this because it'll cost you money PERIOD and that's basically considered advertising.

Bricked Devices
Bricked Devices.
Un-bricking.....
FIRST-OFF WHY HAVE YOU NOT MADE A COMPLETE BACKUP TO STORE SOMEWHERE OFF THE DEVICE TO HELP YOU IN THESE SITUATIONS?
that will be your saving grace in most soft-brick situations, where you can still get to recovery Via button combo or via
Code:
fastboot flash recovery recovery.img && fastboot oem reboot-recovery
To unbrick from a hard brick our only choice for now is SugarMTK.
you can find it in @PizzaG Gsi Prep package...
NOTE:
flashing with sugar restores ALL partitions of the device to factory stock release...
what this means is that even if your carrier or some service unlocked your device to use on networks other than At&t you will NOW be stuck with At&t or cricket or it's MVNO's
SUGAR MTK WILL LOCK THE NETWORK ON YOUR TETRA EVERY TIME

Reserved.
Tools
Miscellaneous

Reserved
Discussion of dual boot and other stuff
We are currently working on.

I there an updated easy way for root yet preferably without pc

Thanks for the guide and fastboot fix. I'm running the LineageOS gsi based on pie, but along the way I have lost the ability to turn on wifi and bluetooth. I'm new to mtk roms, so I was wondering where the firmware for the radios is living.

Idealxtra

Pureindica said:
Idealxtra
Click to expand...
Click to collapse
??

So anybody struggling along here can ask about help or other devices such as Idealxtra on our support group on telegram
https://t.me/Android_General_Chat
Is there an updated easy way for root yet preferably without pc ?
Nope, you can however use mtk-su with a terminal emulator to get tmp root then u could use DD to make a copy of your boot.img
then u can use magisk manager apk to patch said boot.img, and then u can write that back to the device using mtk-su and terminal emulator. but this still requires you to have the device bootloader unlocked i believe or you'll brick
Thanks for the guide and fastboot fix. I'm running the LineageOS gsi based on pie, but along the way I have lost the ability to turn on wifi and bluetooth. I'm new to mtk roms, so I was wondering where the firmware for the radios is living.
i think its in vendor partition

The link for the gsi prep package does not work. Anyone have a new link?

sazechman said:
The link for the gsi prep package does not work. Anyone have a new link?
Click to expand...
Click to collapse
Visit our Website, TeleGram and get AIO ToolKit

Website Down
PizzaG said:
Visit our Website, TeleGram and get AIO ToolKit
Click to expand...
Click to collapse
I have tried to get to your website "http://a-team-solutions.dynu.net/" to no avail. I have tried from many different sources both with and without vpn. I have posted in the thread for the site but have not received a reply. Is the site still available? I would gladly pay for the registered version if it solves my bricked phone problem.
Thanks

How To Guide [Pixel 7 Pro] [TD1A.220804.031] Root guide + Extracted Images + How to

How to root:
You have two options for this, 1 is the recommended way and 2 is the lazy but works way.
Option 1 (RECOMMENDED):
Download the latest factory image from: https://developers.google.com/android/images#cheetah (at the time of writing this, it's TD1A.220804.031
Unlock bootloader (If you don't know how to do this, do not proceed further)
From the downloaded image file, extract the init_boot.img file and copy it to your phone (directory shouldn't matter)
Install the Magisk apk from: https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-release.apk
Launch the app, select install, patch a file, select the init_boot file you placed in your phone
After it's done, it should place a file in your phone's download folder called magisk_patched-<VERSION>_<XYXYXYXYXY>.img
Copy that over to your PC and now boot to bootloader
Run the following commands from Powershell/commandline:
Code:
fastboot flash init_boot magisk_init_patched-25205_EfWOu.img
And then reboot, you'll be rooted
Option 2 (LAZY BUT WORKS):
I'm sharing my magisk patched init_boot from the TD1A.220804.031 build (post 73MB update). Instructions are:
Unlock bootloader (If you don't know how to do this, do not proceed further)
Boot to bootloader
Download the patched init_boot from: https://sourceforge.net/projects/ag.../magisk_init_patched-25205_EfWOu.img/download
Run the following commands from Powershell/commandline:
Code:
fastboot flash init_boot magisk_init_patched-25205_EfWOu.img
And then reboot, you'll be rooted
Install Magisk apk from here: https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-release.apk
To get SafteyNet working:
Open the Magisk app
Open the settings from top right, Enable Zygisk
Reboot
Flash the MODIFIED SafteyNet fix module by @kdrag0n from the attached files on this thread from within Magisk Modules
Clear Play store data and you should be good!
Voila!
FASTBOOT IMAGES:
I'm sharing the stock extracted images of the TD1A.220804.031 build, should be a good reset point from fastboot incase any of you get stuck somehwere:
DO NOT MIRROR THIS PLEASE!!!!
VERIFY THE MD5 OF THE FILE AFTER DOWNLOADING!!!!!!!
Mirror 1 | Mirror 2
MD5: 43613f520697722840ded6a15eb27459
Massive shoutout to @Some_Random_Username for Mirror 1 and @akhilnarang for Mirror 2 since SourceForge was facing issues!
Now documentation on how to do it yourself (which I'd highly recommend since you should never trust any file given, always try to do it yourself!):
How to dump your own device:
1. Download a GSI which is userdebug/eng and equal/newer Security Patch of the current build on your device from any of the unofficial community builds here: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
2. Install the DSU Sideloader app from: https://github.com/VegaBobo/DSU-Sideloader/releases/latest
3. Follow instructions in the DSU sideloader app readme here: https://github.com/VegaBobo/DSU-Sideloader/blob/master/README.md
I'd recommend enabling the userdata toggle and typing 32GB as the size
4. Reboot into the DSU from the notification
5. When the device boots up, type the following in the terminal:
Code:
adb root
adb shell
mkdir -p /sdcard/dump
for file in /dev/block/bootdevice/by-name/*; do
if [ "${file##*/}" != "userdata" ]
then
echo Dumping "${file##*/}"
dd if=$file of=/sdcard/dump/"${file##*/}".img
fi
done
6. Once the dump is done, you'll have files in /sdcard/dump/
7. Copy those over to a PC
8. Voila

A massive thanks to @AndyYan @Some_Random_Username for their help (well hand holding) throughout the entire process <3
Also thanks to @OmkarTheAndroid for the re-brush up of the Android basics I forgot

Reserved

Thanks!

Have you had any luck with SafetyNet yet? People on another thread are saying that even the Modded version by @Displax isn't working on P7P with Canary Magisk

I'd like to remind all that, 1) the DSU method requires some Android/shell knowledge to correctly carry out, and 2) you're discouraged from actually flashing/using those GSIs (TD-based Android 13 GSIs are still in early phase, and P7/P will almost certainly get proper, fully functional device-specific ROMs shortly anyway).

Thanks for the dump! Could you maybe mirror it yourself to be sure? At least until Google's facory images are up Sourceforge is incredibly slow for me (and probably for others too).

so looks like vendor_dlkm has been replaced by vendor_kernel_boot and the init_boot is just the first-stage init. This will be interesting moving forward with AVB and custom images. I will start working on something when source drops. I will likely need to have some testers to see how much this requires to get a custom image up and running.
EDIT: vendor_boot is actually the one that has been separated out a bit between vendor_boot (holding modules) and vendor_kernel_boot, which has some ramdisk stuff like the vendor_boot has on Pixel 6 devices.
Kernel now consists of 6 images. init_boot, vendor_boot, vendor_kernel_boot, vendor_dlkm, dtbo and boot.img

I downloaded the init_boot.img file then got a big problem bricked my pixel 7 oro

mrteii1 said:
I downloaded the init_boot.img file then got a big problem bricked my pixel 7 oro
Click to expand...
Click to collapse
this is a soft brick, just flash the correct partition back using the stock image

Tahnks forbyour reply. How to get the stock image? Now it brickes. Im panicking

I think i'll hold fire on rooting until things are a little clearer. unlocking the bootloader in the usual fashion should be ok tho right?

whatsisnametake2 said:
I think i'll hold fire on rooting until things are a little clearer. unlocking the bootloader in the usual fashion should be ok tho right?
Click to expand...
Click to collapse
Yes, unlocking the bootloader is still the same and will wipe data.

Current SafetyNet Status (with modded universal SafetyNet Fix + Magisk Props):
Play Integrity API Checker:
MEETS_DEVICE_INTEGRITY: fail
MEETS_BASIC_INTEGRITY: pass
MEETS_STRONG_INTEGRITY: fail
YASNAC:
Basic integrity: pass
CTS profile match: fail
Edit: GPay does work on the Pixel Watch, even though it doesn't on the phone (when rooted).
Make sure to add your cards there if you're using the Pixel Watch and can't use GPay on your phone.

zetsumeikuro said:
Yes, unlocking the bootloader is still the same and will wipe data.
Click to expand...
Click to collapse
If you can boot to recovery try a factory reset from there or you will have to power it off and wait until Google releases the image.

mrteii1 said:
Tahnks forbyour reply. How to get the stock image? Now it brickes. Im panicking
Click to expand...
Click to collapse
In the OP, the part with:
"FASTBOOT IMAGES:
I'm sharing the stock extracted images of the TD1A.220804.031 build, should be a good reset point from fastboot incase any of you get stuck somehwere:
DO NOT MIRROR THIS PLEASE!!!!"

Misterxtc said:
If you can boot to recovery try a factory reset from there or you will have to power it off and wait until Google releases the image.
Click to expand...
Click to collapse
? unlocking is just going to do a data wipe/factory reset anyway. not sure why I would need the factory image for that? or to do an additional factory reset from recovery?

Misterxtc said:
If you can boot to recovery try a factory reset from there or you will have to power it off and wait until Google releases the image.
Click to expand...
Click to collapse
Maybe you replied to the wrong user?

Hey everyone, a slight update on the website for the image dump, SourceForge was giving people incomplete files so @Some_Random_Username is generously hosting it on his servers <3
please verify the MD5 of the downloaded zip before trying to modify any parititons using the following commands:
On windows:
Code:
certutil -hashfile cheetah-TD1A.220804.031-compressed.zip MD5
On Linux/MacOS:
Code:
md5sum cheetah-TD1A.220804.031-compressed.zip
The MD5 should be: 43613f520697722840ded6a15eb27459

whatsisnametake2 said:
? unlocking is just going to do a data wipe/factory reset anyway. not sure why I would need the factory image for that? or to do an additional factory reset from recovery?
Click to expand...
Click to collapse
I was thinking the reset would force it to boot off the other slot.