Ulefone Armor X6 - mt6580, 720x1280 5-inch, 2/16 ram/rom Android 9. There is a full rom, ulefone site (Support > Software Download). I use EU version.
Rom is with "-sign.img"s, system/build.prop: "ro.treble.enabled=true", "ro.expect.recovery_id=0xb4248...", boot-sign.img without ramdisk.
Used tools: Linux - IMG-SIGN Extractor (signimg2img), simg2img/img2simg, mount, SP Flash Tool, Carliv Image Kitchen, Windows - Miracle.
Tests for modification:
Fastoboot flashing unlock - ok.
SPFT - before connection - hold volume down - is possible to flash full rom. Single img - error.
Patching recovery-sign.img in magisk, recovery mode. Fastboot flash recovery magisk_patched.img = bootloop.
System-sign.img - unsign, unsparse, mount, remove bootanimation.zip and apps (Duo, YTMusic), edit build.prop: "ro.treble.enabled=false", remove "ro.expect.recovery_id=0xb4248...". Umount, sparse, flash system via fastboot. Fastboot say "ok". After start - stil stock system, without modification.
For the upper rom exist update ~400mb. Update, dump with Miracle - img's are unsigned.
System.img - unsparse, mount, remove bootanimation.zip and apps (Duo, YTMusic), edit build.prop: "ro.treble.enabled=false", remove "ro.expect.recovery_id=0xb4248...". Umount, sparse, flash system via Miracle = bootloop.
Also, I make a few ports of TWRP via Carliv Image Kitchen. Always bootloop (I never had trouble with a previous ports, for other phones, especially for this cpu)
Any other ideas? Or links to the right treads. This is my first rom with treble / "-sign.img"s.
Root
Tested on "GQ3085DH1_KSP2E_Ulefone_EEA_20200312_V01（Eu）" (Baseband version MOLY.WR8.W1449.MD.WG.MP.V237.4,2019/10/28 09:26, Kernel version 4.9.117 #2 Mon Oct 28 09:48:24 CST 2019)
Unlocking bootloader and disable verification (fastboot - min. version 1.8, vbmeta.img from stock rom):
fastboot flashing unlock
(volume up)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot reboot
On Android - Mtk-easy-su-v1.1.3.apk & MagiskManager-v7.5.1.apk.
Mtk-easy-su:
1. Run on boot
2. Magisk.v20.4.zip (assets-r22) - install
3. "Activate bootless root"
Restart phone. After start, wait to see "Success" on screen (bottom). Magisk work.
After root, if adb is needed:
adb shell
su
mount -o rw,remount /
Do you have made any progress?
Im sitting here on my armor x6 and have the same problems.
ahaff said:
Ulefone Armor X6 - mt6580, 720x1280 5-inch, 2/16 ram/rom Android 9. There is a full rom, ulefone site (Support > Software Download). I use EU version.
Rom is with "-sign.img"s, system/build.prop: "ro.treble.enabled=true", "ro.expect.recovery_id=0xb4248...", boot-sign.img without ramdisk.
Used tools: Linux - IMG-SIGN Extractor (signimg2img), simg2img/img2simg, mount, SP Flash Tool, Carliv Image Kitchen, Windows - Miracle.
Tests for modification:
Fastoboot flashing unlock - ok.
SPFT - before connection - hold volume down - is possible to flash full rom. Single img - error.
Patching recovery-sign.img in magisk, recovery mode. Fastboot flash recovery magisk_patched.img = bootloop.
System-sign.img - unsign, unsparse, mount, remove bootanimation.zip and apps (Duo, YTMusic), edit build.prop: "ro.treble.enabled=false", remove "ro.expect.recovery_id=0xb4248...". Umount, sparse, flash system via fastboot. Fastboot say "ok". After start - stil stock system, without modification.
For the upper rom exist update ~400mb. Update, dump with Miracle - img's are unsigned.
System.img - unsparse, mount, remove bootanimation.zip and apps (Duo, YTMusic), edit build.prop: "ro.treble.enabled=false", remove "ro.expect.recovery_id=0xb4248...". Umount, sparse, flash system via Miracle = bootloop.
Also, I make a few ports of TWRP via Carliv Image Kitchen. Always bootloop (I never had trouble with a previous ports, for other phones, especially for this cpu)
Any other ideas? Or links to the right treads. This is my first rom with treble / "-sign.img"s.
Click to expand...
Click to collapse
Yo, can you send me the port of TWRP for this phone please?
Related
Hello.
I am attempting to root blu c4 (c050L), which has spreadtrum sc7731e board.
Kingroot from PC won't root the device.
While trying to port TWRP, I discovered I am unable to even pack / repack the original recovery.img
I can flash the original one, but after packing/repacking with Android Image kitchen by osmosis, I can no longer flash that file through spd research tool.
I also tried [Hovatek] Spreadtrum (SPD) Auto TWRP Recovery Porter V1.2 by Team Hovatek, but I can't flash the resulting img files, either.
https://my.pcloud.com/publink/show?code=XZVYsG7Z3jU6r8JLVU44JTeKYjac0zH6OpwV
recovery.img file, in case anybody can help me
Blu C4 is running oreo go 8.1
Stock Recovery says: "supported API:3 // 8.1.0/OPM2.171019.012/30512"
Fastboot doesn't support unlocking (already set oem unlock on developer settings)
So far
In order to flash modified boot.img and recovery.img, I had to switch the original fdl1-sign.bin and fdl2-sign.bin for ones I extracted from an A140 stock rom (another SC7731e device)
I attached them to this post
However, the boot is probably signed. You can read:
https://forum.xda-developers.com/showpost.php?p=65443271&postcount=844
In that case, a signing would be required - out of luck.
Any luck. I have the same unit and want to root it. Any kind of help will be appreciated.
Thanks
Kashutu
Hi,
I'm trying to root the tablet. Unfortunately so far without success. I have tried several rooting tools (Desktop and Tablet App).
What promised most success is Magisk. It is also known that it works with Android 9. I copied the bootimage on the tablet from the stock-ROM, patched the image with the latest Magisk-APP (7.5.1) (Magisk 20.3 (20300)). Then back to the PC, and with fastboot written to the boot partition. After unlock the partition, this was possible. After a restart, however, the tablet will remain on the boot logo. Original stock-ROM on it again, tablet runs again (no boot loop).
Then I looked at the image sizes. The original is 16,385 kB. However, the patched Magisk file is only 7,148 kB. That can't really be, can it?
Does anyone have an idea of what this can be, or what I'm wrong about?
Thank you for your help.
hw-schrauber said:
Hi,
I'm trying to root the tablet. Unfortunately so far without success. I have tried several rooting tools (Desktop and Tablet App).
What promised most success is Magisk. It is also known that it works with Android 9. I copied the bootimage on the tablet from the stock-ROM, patched the image with the latest Magisk-APP (7.5.1) (Magisk 20.3 (20300)). Then back to the PC, and with fastboot written to the boot partition. After unlock the partition, this was possible. After a restart, however, the tablet will remain on the boot logo. Original stock-ROM on it again, tablet runs again (no boot loop).
Then I looked at the image sizes. The original is 16,385 kB. However, the patched Magisk file is only 7,148 kB. That can't really be, can it?
Does anyone have an idea of what this can be, or what I'm wrong about?
Thank you for your help.
Click to expand...
Click to collapse
Seems like Magisk Manager is not able to patch the boot.img properly.
The size of patched image is never lesser than the original boot image.
Try patching your boot image using an older version of Magisk Manager.
HIT THANKS IF FOUND USEFUL
Augustoandro said:
Seems like Magisk Manager is not able to patch the boot.img properly.
The size of patched image is never lesser than the original boot image.
Try patching your boot image using an older version of Magisk Manager.
HIT THANKS IF FOUND USEFUL
Click to expand...
Click to collapse
Thank you Augustoandro, but unfortunately I can't use an older version. Since I want to run my device with magic, I only have to install the apk. If I take an older one here, I will only get to the patch buttons when the app is updated.
So this proposal does not help.
Perhaps it is also because the 7305F does not seem to have the partitions set up as usual. If I want to make a BackUp using the tool "MTKdroidTools 2.5.3" (screenshot), it means that the partition structure does not fit and no backup is possible. A root with the tool is also not possible.
Is there another idea?
For more information:
CPU MT8321 (32bit), Memory 1/16GB, kernel 4.9.117+ (#25.10.2019)
I was able to patch the file with magisk and flash the
boot, but no root. Were you able to find a solution to your problem?
macgajos said:
I was able to patch the file with magisk and flash the
boot, but no root. Were you able to find a solution to your problem?
Click to expand...
Click to collapse
You have to root by means of Magisk: Magisk itself doesn't root the Android.
jwoegerbauer said:
You have to root by means of Magisk: Magisk itself doesn't root the Android.
Click to expand...
Click to collapse
Thank you for your reply. Sorry for not being clear here: I get "Magisk is not installed" info in magisk manager after flashing the magisk patched boot img in fastboot mode.
I have found the way to install MAGISK. You have to install MAGISK to the recovery.img. Then start in Recovery-mode and the system will boot to the normal System with installed MAGISK. Works perfect to me.
Some more information. There is an update named TB-7305F_100049_200508_ROW. After you have update to this release, you haven't MAGISK installed and you are not able to reinstall MAGISK. Also, when you get the original recovery from the version it is not possible. As well, I have tested to use the working recovery from the prerelease with the newest release, this also don't possible. For me the only working release is the TB-7305F_100043_200223.
If someone flash a later version that woks, please let know here!
hw-schrauber said:
I have found the way to install MAGISK. You have to install MAGISK to the recovery.img. Then start in Recovery-mode and the system will boot to the normal System with installed MAGISK. Works perfect to me.
Some more information. There is an update named TB-7305F_100049_200508_ROW. After you have update to this release, you haven't MAGISK installed and you are not able to reinstall MAGISK. Also, when you get the original recovery from the version it is not possible. As well, I have tested to use the working recovery from the prerelease with the newest release, this also don't possible. For me the only working release is the TB-7305F_100043_200223.
If someone flash a later version that woks, please let know here!
Click to expand...
Click to collapse
Yes, recovery is the way to go. I have figured it after reading this:
topjohnwu - install.html#boot-image-patching
As I have X model, TB-7305X_S100043_200224_ROW and TB_7305X_S100062_200610_ROW was the ROM that worked. Cool thing is that you can get roms from lenovo with "Rescue and smart assistant" app.
The trick that makes magisk rooted all the time is to choose 'reset phone' after rooting. This would cause the tablet to start with root each time.
macgajos said:
Yes, recovery is the way to go. I have figured it after reading this:
topjohnwu - install.html#boot-image-patching
As I have X model, TB-7305X_S100043_200224_ROW and TB_7305X_S100062_200610_ROW was the ROM that worked. Cool thing is that you can get roms from lenovo with "Rescue and smart assistant" app.
The trick that makes magisk rooted all the time is to choose 'reset phone' after rooting. This would cause the tablet to start with root each time.
Click to expand...
Click to collapse
What do you mean with reset? When MAGISK is in recovery, the only way to start is in the recovery-mode. Then you have ever MAGISK working when it is installed!?!
Today I have seen, that there is a new version for the "F" model. TB_7305F_S100055_200703_ROW. I will test and report!
How do I pull the Recovery.img from this tablet in the first place? Please help. Thanks.
Hi. I am trying to manage root without twrp for a couple of days. I picked up the solution with recovery.
I've tried to flash root to recovery with magisk patched recovery.img via fastboot. But the .img size is to large (is texted in fastboot). By the way i was curious after magisk patching cause the patched .img file has the same size as the original .img file. I downloaded twrp port tool and ported recovery.img and got a recovery.img with a smaller size so i was able to flash it via fastboot. Fastboot flash recovery recovery.img
Fastboot reboot.
Device is booting to Lenovo splash screen with the warning that the device is unlocked and boot in 5s. Could wait forever. After 2min pushed vol+, Lenovo Banner starts to flip and it booted to system.
But no root.
Reboot.
Boot with key combo
Hold Vol+ and power, released as lenovo splash with the warning appears. Nothing happend.
Pushed vol+. Nothing happened. It stuck at splash.
After that i could not boot the device with power key anymore. It stays at splash every time i rebooted.I had to reboot to recovery and do rebooting to system from recovery.
From bootloader i was able to boot to system also.
I like to flash magisk patched boot.img via fastboot but magisk doesn't make the .img file smaller.
I tried with sp flash tool but after patching the img is not signed anymore soflash tool doesn't flash it.
So that is my state for now.
_
_
Hi all,
I want to remove all of the google apps from my tablet 7305F in a bid to save ram, adb does most of the trick. can even uninstall play store, but the google play services com.google.android.gms is very hard to disable, keeps popping a "play services has stopped" message frequently.
till now I was able to free upto 50 % ram using this trick only its annoying that the play services message keeps popping.
PART HO said:
Hi all,
I want to remove all of the google apps from my tablet 7305F in a bid to save ram, adb does most of the trick. can even uninstall play store, but the google play services com.google.android.gms is very hard to disable, keeps popping a "play services has stopped" message frequently.
till now I was able to free upto 50 % ram using this trick only its annoying that the play services message keeps popping.
Click to expand...
Click to collapse
.....Install twrp and root rights, it's not difficult. You can then do whatever is needed
I rooted my Lenovo M7 (TB-7305X) the folling way
On a PC Get and Install LMSA "Lenovo Rescue and Smart Assistan"
* Using LMSA do a recovery, this way you are sure you have al the drivers working and that you have a correct rom
On the Tabled enabled developer mode
* enable remote debugging
* enable oem unlocking
Unlock the bootloader using fastboot
(you will find adb and fastboot in the location where LMSA was installed)
P.S. this will erase of data on your tablet
* adb reboot-bootloader
* fastboot flashing unlock
* fastboot reboot
PS tablet well be in orange state (because the bootloader is unlocked)
* android boots
On the tablet create a rooted boot.img using magisk
* download and install the latest magisk.apk
* look for boot.img (boot.img_verified) the ROW downloaded by LMSA (some where in c:\programdata)
* uplad the boot.img to the tablet
* start magisk and patch the boot.img file
* download the patched boot.img
On the PC start MTK_Flash tool
P.S. this will erase of data on your tablet
* open the download tab
* the download agent should be set by default (MTK_AllInOne_DA.bin)
* select the scater file (from the LMSA rom directory)
* deselct all files except BOOTIMG
* change the location of the BOOTIMG and select the pached boot.img
Flash boot.img by clicking download
Rooting instructions for TB_7305X (Should be the same for TB_7305F using TB-7305X_S100043_200223_ROW)
Install Rescue and Smart Assistant from Lenovo
Start Rescue and download latest ROM
Replace the latest ROM files from C:\ProgramData\RSA\Download\RomFiles\TB_7305X_S1000xx_xxxxxx_ROW with the ones from TB-7305X_S100043_200224_ROW
Can be downloaded from:
https://mirrors.lolinet.com/firmware/lenovo/Tab_M7/TB-7305X/
Rescue the device as per the RSA instructions
Install latest Magisk
Upload recovery-verified.img from the TB-7305X_S100043_200224_ROW ROM to the Internal Shared Storage of the device in Download directory
Run Magisk Manager
Patch the recovery-verified.img with magisk
Copy the newly created magisk_patched-xxxxxxxx.img file in Downloads to C:\Program Files (x86)\Rescue and Smart Assistant and rename to magisk_patched.img
It will later be used to flash the device after unlocking
Enable developer mode on the device
From developer options enable:
OEM Unlocking (needs Internet connection)
USB Debugging
Start cmd and navigate to C:\Program Files (x86)\Rescue and Smart Assistant directory
adb reboot bootloader
Wait for reboot. You will see “=> FASTBOOT mode …” message when ready
fastboot.exe flashing unlock
Press volume up key to confirm
fastboot flash recovery magisk_patched.img
disconnect USB cable
press volume-up+volume-down+power buttons to switch off the tablet
press volume-up+volume-down+power buttons to switch on the tablet in Recovery mode
When Lenovo logo appears release the buttons.
Wait several minutes. Do not give up, do not restart. It takes time.
Reconfigure device
Enable USB Debugging
Disable System updates
Reinstall Magisk
Your device is rooted.
Whenever you want to use it in rooted mode you have to switch to recovery mode
The normal mode calls boot.img where magisk is not installed and the device will not be rooted.
You may proceed with removing Orange mode 5 sec wait message. Instructions available on the Internet.
If at some point the device writs back the original Recovery mode just reflash with magisk patch recovery-verified.
Hi,
I would like to root my Lenovo TB-7305F as well. The file I have leased from Magisk generates "size is too large" in fastboot. This problem has been written by others. I have compared the original filesize and the patched filesize. They are identical. Exactly to the byte. I did it exactly as greenbul describes. However, he uses the 7305X and I use the 7305F.
Also the SP tool cannot upload this patched file.
I have the 1GB 7305F model.
Do you have any idea?
Many thanks
Andreas
Skylon5000 said:
Hi,
I would like to root my Lenovo TB-7305F as well. The file I have leased from Magisk generates "size is too large" in fastboot. This problem has been written by others. I have compared the original filesize and the patched filesize. They are identical. Exactly to the byte. I did it exactly as greenbul describes. However, he uses the 7305X and I use the 7305F.
Also the SP tool cannot upload this patched file.
I have the 1GB 7305F model.
Do you have any idea?
Many thanks
Andreas
Click to expand...
Click to collapse
Lenovo Tab M7 - Обсуждение - 4PDA
Lenovo Tab M7 - Обсуждение, Планшет, 7"
4pda.to
Lenovo 7 tb-7305f
Root and TWRP
Lenovo Tab M7 - Обсуждение - 4PDA
Lenovo Tab M7 - Обсуждение, Планшет, 7"
4pda.to
Please read this guide fully before attempting to follow it. It requires some knowledge of how to use a Terminal and basic ADB/Fastboot operation. I don't think this guide is thorough enough for a person who's modifying their phone for the very first time. Feel free to ask for help though!
I am not reliable for any adverse effects this guide might have on your phone. If something breaks, that's your responsibility. However: if your phone doesn't boot anymore, but you can still get into fastboot, you should be able to flash the Stock Firmware OFP using the Realme Flash Tool. To get into fastboot, power off your phone, wait a few seconds, and hold power and volume down until you see the fastboot logo.
This guide was cobbled together using various other tutorials and my own attempts. I've used it on my RMX2075. It should also work for the RMX2076. The files Realme provides for the RMX2075 are named "RMX2076", so I assume they're the same device. I have no idea how the RMX2071 fits into this. Curiously, the TWRP version used here is intended for the RMX2071, although it works flawlessly on my RMX2075. However: if you're using it on an RMX2075/2076 TWRP thinks you're using an RMX2071, so it won't flash packages intended for the RMX2075/2076. Hence the following warning:
!!! YOU WON'T BE ABLE TO INSTALL OTA UPDATES AFTER INSTALLING TWRP !!!
If you attempt to install an OTA Update downloaded from within the Settings.app, the phone will reboot, TWRP will attempt to install the OTA Update and fail with an error. This does not break anything, it just doesn't update.
DOWNLOADS:
- Realme Flash Tool
- Stock Firmware OFP
- OTA Update OZIP
- TWRP 3.4.1b for RMX2071 by wzsx150 and LR. Team
Spoiler: further details
The licensing of this TWRP is pretty unclear, so I can't provide a download link. If you search for it Online, make sure to find a version that includes both "recovery.img" and "misc.bin"
- Realme DeepTesting App
- Magisk Manager by topjohnwu
- oppo ozip decrypt
PREPARATION:
- install ADB & Fastboot on your computer
- enable "USB debugging" on your phone
- install the oppo ozip decryption tool by following the instruction on the GitHub page
UNLOCKING
- follow the unlock instructions provided by the official Realme Tutorial
RESTORING AND UPDATING - if you're on firmware A42, skip this step
- follow the restore instructions provided by the official Realme Tutorial
- go to the Realme Software Update page, click on "How to update?" and follow the instructions
FLASH TWRP
- open a Terminal window and cd into the folder that holds recovery.img and misc.bin
cd /path/to/folder
- enter the following commands and hit enter after each
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot flash misc misc.bin
fastboot reboot recovery
- your phone should now reboot into TWRP
- enter your phones unlock code if you have one
- go to "Advanced" -> "Disable Replace TWRP"
- reboot phone
ROOTING
DO NOT use "Install Root" in TWRP, it'll "destroy" the bootloader and you'll have to flash the stock firmware
Follow this instead:
- decrypt the OTA .ozip using the oppo ozip decrypt tool (instructions on its GitHub page)
- unzip the resulting decrypted file
- copy "boot.img" onto your phone
- copy "/firmware-update/vbmeta.img" into a folder of your choice
- install Magisk Manager on your phone
- open Magisk Manager, tap on "Install" followed by "Select and Patch a File"
- select the "boot.img" you've previously copied onto your phone and let Magisk do its thing
- the patched "boot.img" is called "magisk_patched_XXXX.img" or something similar. Make note of the resulting file name which is specific to you.
- copy the patched "magisk_patched_XXXX.img" into the same folder that holds your "vbmeta.img"
- open a terminal and cd into the folder that holds the patched "boot.img" and "vbmeta.img"
- enter the following commands and hit enter after each
adb reboot bootloader
in the following step, replace "magisk_patched_XXXX.img" with whatever your patched "boot.img" is called
fastboot flash boot magisk_patched_XXXX.img/ICODE]
[ICODE]fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot reboot
- your phone should now be rooted
I have also uploaded the stock boot.img along with the rooted version as well as vbmeta.img here. They were created using the method described above with OTA update A42. I would recommend creating your own though, since this has a higher chance of success.
Another method to get the stock boot.img and vbmeta.img is creating a TWRP backup, renaming "boot.emmc.win" to "boot.img", and "vbmeta.emmc.win" to "vbmeta.img". I have NOT TESTED this method.
I don't know if this will work for Android 11 / ColorOS 2.0. My theory is that if you can get the RMX2076PU_11.C.16.ozip somewhere, you could just follow this guide using it instead of the A42 one. Again, I have NOT TESTED this method.
Unfortunately does not work with Android 11. The result is that the phone stays in the fastboot. The Realme flash tool doesn't work anymore. The phone is now bricked. Let's see if I can reach the service now. Isn't the first time they haven't answered. Now actually needs the MSM tool. But haven't found a working one yet.
corneo said:
Unfortunately does not work with Android 11. The result is that the phone stays in the fastboot. The Realme flash tool doesn't work anymore. The phone is now bricked. Let's see if I can reach the service now. Isn't the first time they haven't answered. Now actually needs the MSM tool. But haven't found a working one yet.
Click to expand...
Click to collapse
Android 11twrp brush Android 10, and then brush Android 10twrp, you can boot
can u using volte with stock ofp eu version?
Any guide on unlock/rooting Xiaomi Mi Pad 5 Pro from China? I need root access + english. If there is HD Netflix, it would be great.
Go through the regular Xiaomi unlock process (register device, connect to unlocking tool, wait 7 days, unlock). Unlocking will wipe (factory reset) the device. Choose English when setting up the device after unlocking.
Download Magisk and install.
Download Fastboot enuma ROM from Xiaomi. (Fastboot is easier than recovery)
Extract boot image from ROM zipfile.
Copy boot image file to device and use Magisk to patch the file. Copy file back to PC.
Reboot into fastboot. Fastboot flash patched boot image (possibly best to flash A & B, but if something goes wrong then its a long process to recover).
Reboot. Rooted.
There is another thread with details on getting HD Netflix & Amazon working if it does not by default.
Sorry, I have no knowledge of software.
Magisk download from playstore and install on phone?
Any link to download the fastboot enuma rom?
What is Fastboot flash patched boot image? What is A and B?
While everyone must admittedly start from somewhere, I will need to caution you that blindly following instructions from the internet may end up with you having an un-usable device. Having some idea of what the instructions are doing is a far safer option.
Secondly, rooting is not a magical solution for everything, you indicated you *need* root, yet you also seem unfamiliar with Magisk. So are you sure you really need root? Root will not magically make the system native English UI if that is what you were hoping. You would need to use the Chinese ROM in English, or wait until a Global rom is released or 3rd party roms.
Unlocking Xiaomi / Mi devices is well documented you can follow any of those guides.
Once unlocked:
Download Magisk apk from here: https://github.com/topjohnwu/Magisk copy to the device and install.
Download the ROM for your device. Preferably the same version that is already on the device. Also preferably the "fastboot" type. Fastboot type has the individual files you need inside the zipfile, plus this will be a good backup to have in case something goes wrong as the fastboot ROM can be used to re-install.
You can try xiaomirom.com for the rom files, check that the download comes from the official xiaomi site though. "enuma" is the model name for the Pro 5G version.
Unzip the rom file and copy the boot.img file to the device
Open magisk on the device and choose install, select and patch a file, choose the boot.img file.
Copy the patched file back to a PC, reboot the tablet into fastboot mode and connect to the PC
On the PC make sure you have the right drivers installed and the fastboot program (no idea how to do this on windows).
In a command shell window type fastboot flash boot <name of patched file>
Reboot the tablet. Open Magisk and it should say installed and you should have root access
Heard of bricking and unbricking solutions.
I rrequire root access to system files or app files inaccessible normally.
I am ok with China rom as long as most of its UI is in English with Google Playstore.
"Download the rom for your device"? Any website link to do so? Hmmm... I am so confused. Any YouTube videos to show step by step? The first part to signing into xiaomi account to unlock device is ok. But the rooting part sounds so complicated.
Pardon me for my inexperience.
Check in Magisk manager if Mi Pad 5 Pro uses A/B partition. If so, flashing a patched boot.img to both partition is required.
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
I cant this working with 'https://hackmd.io/@EdwardWu/ArrowOS_elish'
can anyone help please?
here it is for g530fz devices :
used : twrp 1.1.1-1
lk2nd (postmarketos): 0.12.0 msm916
a/ pmos "works" (not so well) on that device
b/ unfortunately, few "bugs" "maybe related" to hardware persists, mainly in the reactivity on touchscreen when locked on inactive since a while.
c/ perf is highly to low (paradox for pmos ;-) ) to use it as a "common daily smartphone", mean : if you want to escape gafamnt, mount your server on a phone, or specific usages : it would be perfect. But dont expect it to run netflix everyday in firefox or falkon, it might freeze for "not only" a while.
d/ my documentation/software related to it :
samsung_g520fz
Partagé avec kDrive, le Cloud Éthique.
kdrive.infomaniak.com
[lien noveart/tabdigital]
[lien noveart/free]
[lien noveart/androidfilehost]
see for each link, normally a .img file. Unforunately, only 1 was able to host a gigabyte-sized, .img file.
Please note, without the following bug being not solved, that device could NOT get postmarketos installed through twrp with zip file :
Fail to sideload recovery.zip (#1962) · Issues · postmarketOS / pmbootstrap · GitLab
Phone: motorola-harpia (Moto G4 Play XT1607) Recovery: tool: TWRP version: 3.2.1-0 Zip built...
gitlab.com
In addition : Don't know what is the exact issue, but I found a case, where it was fixed: https://gitlab.com/postmarketOS/pmbootstrap/-/issues/1962 , sadly they didn't document how to solve it properly.
e/ im going on something else now.. if you want ungoogled/ungafamnted android, take lineageos14.1 (gprimeltexx), the fastest/best choice for that device, for common usage
==roll back to androstock/lineageos?==
for G530FZ :
used : twrp 1.1.1-1
lk2nd (postmarketos): 0.12.0 msm916
android stock :
**download mode :
simply use odin with a tar ROM
lineageos :
**download mode :
use heimdall or odin to flash the twrp
used : twrp 1.1.1-1
**twrp/recovery mode :
use twrp to flash the lineageos zip file (install button)
I really advise you to use lineageos14.1 (andro7) for better compatibility/performance
postmarketos :
you have to use heimdall with lk2nd in download mode
**download mode :
use heimdall to flash lk2nd, then reboot in lk2nd (power+volDown at bootup)
**lk2nd screen :
fastboot erase system && fastboot erase userdata && fastboot flash userdata /home/koala/.local/var/pmbootstrap/chroot_native/home/pmos/rootfs/samsung-gprimeltexx.img &&fastboot reboot
[unfortunately because of a bug, twrp can't flash .zip files of postmarketos, on that device - .img, heavier, are the only way I had]
well tested :
lineage 14.1, but you *might* have to odin it, regarding this :
Hi guys
regarding the G530fz to solve the problem I had to be oriented to Lineage 14.
Why the cell data was not detected? I don't know, but I discovered a way to fix it :
I was used before to install Lineage by just injecting the image file into the phone, then format the /data partition by simple wipe.
And for others phone, it was working.
Looks like on samsung models, it's requiring steps differently :
1/ use odin to reinstall stock firmware regarding all four files : BL, AP, CP, CSC. In the downloaded archive of the stock firmware, all files matchs with those option with odin. It's necessary to add these four files.
Flash it
2/ The phone will start. After finished, you can restart it, but in download mode.
3/ then use again odin, but flash it with only three files, excluding AP. Replace BL by the twrp bootloader.
4/ If at reboot, it's stuck on a recovery start, even without pushing the vol buttons, reflash it again with only BL.
5/ proceed normally to install lineage : download correct image plus arm (it's arm32 if Im right) pico or nano opengapps, copy them to the phone by usb, flash it then wipe /data.
6/ it should work.
If not, I remember I had to firstly flash by stock factory with all four files of stock archive, then only three including twrp instead of factory BL, then only BL if it's booting in loop into recovery instead normal mode.
Normally, it should, with lienage, detect sim cards.
If you just flash it with twrp by BL/odin, twrp will be installed, lineage can be installed too, but GSM/3G/LTE modules might never work (in my case, it happened like it)