Related
Hey guys,
just wanted to share my built TWRP for the Alldocube iPlay 8 china tablet here real quick.
Instructions:
Download and unzip attachment.
Unlock fastboot
Boot into fastboot
Use "fastboot boot *image*" for initial kickstart.
Install magisk to disable dm-verity and auto-recovery re-flashing.
Flash TWRP to recovery partition optionally.
Source and binary are attached to this post.
Please note that I will not give extended support as I just created this for fun and myself. Use it as you wish.
Enjoy!
Best regards,
Jan
PS: This is only tested on the U78E version. No idea if it works on the other versions floating around.
can i use the file and method to Alldocube iplay 8 Pro?
buzzmarz said:
can i use the file and method to Alldocube iplay 8 Pro?
Click to expand...
Click to collapse
If they have mostly the same specs, yes
Can I ask what drivers, if any, you all were using to get this going?
I cannot get my iPlay 8 talking to platform tools on either windows or osx...
BlueFlame4 said:
Unlock fastboot
Click to expand...
Click to collapse
How do you unlock iPlay 8? My device (also U78E) throws
Unlock failed...return to fastboot in 3s
on either of
fastboot oem unlock
or
fastboot flashing unlock
Any advice?
Thanks
BlueFlame4 said:
Hey guys,
just wanted to share my built TWRP for the Alldocube iPlay 8 china tablet here real quick.
Instructions:
Download and unzip attachment.
Unlock fastboot
Boot into fastboot
Use "fastboot boot *image*" for initial kickstart.
Install magisk to disable dm-verity and auto-recovery re-flashing.
Flash TWRP to recovery partition optionally.
Source and binary are attached to this post.
Please note that I will not give extended support as I just created this for fun and myself. Use it as you wish.
Enjoy!
Best regards,
Jan
PS: This is only tested on the U78E version. No idea if it works on the other versions floating around.
Click to expand...
Click to collapse
Thanks for the work!! I have an iplay 8 E78 and this gives me hope that I will not end up with the ROM that started and Android 6. Do you think an Android 7 or 8 ROM can be created?? What is the point of releasing the annealing with the process you describe? Did you do it on your tablet? Thanks again!!
Here was a Guide. Someone said people don't care about Me or My Work so...
Thank you
Hello,
I'm going into boot loop when I'm trying this :
Code:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
fastboot continue
I have downloaded your img for Xperia 1
Can you help please ?
After multiple tentative your image was woking
But when I install your module in Magisk and restart, I get Pixel Launcher Stopped message (with rest pixel laucher or go to info) and I can do nothting : the message appears every time I click somewhere.
Thanks
kelly669 said:
After multiple tentative your image was woking
But when I install your module in Magisk and restart, I get Pixel Launcher Stopped message (with rest pixel laucher or go to info) and I can do nothting : the message appears every time I click somewhere.
Thanks
Click to expand...
Click to collapse
when you say "module" what you reffer? pixel launcher or boot image? it's seems that the author posted here only boot image.
Is bettwer to build your own image instead to use one build by others;
The pixel launcher problem may be from not installing proper magisk module; check download section in magisk for necessary modules and also search on forums for pixel launcher prerequisites.
kelly669 said:
After multiple tentative your image was woking
But when I install your module in Magisk and restart, I get Pixel Launcher Stopped message (with rest pixel laucher or go to info) and I can do nothting : the message appears every time I click somewhere.
Thanks
Click to expand...
Click to collapse
Thats due to the Gesture Navigation. Please enable 3 Button Navigation To fix it... :angel:
daphix said:
when you say "module" what you reffer? pixel launcher or boot image? it's seems that the author posted here only boot image.
Is bettwer to build your own image instead to use one build by others;
The pixel launcher problem may be from not installing proper magisk module; check download section in magisk for necessary modules and also search on forums for pixel launcher prerequisites.
Click to expand...
Click to collapse
It was about My Work. There are No other Modules for the Pixel Launcher...
Since My Threads got moved from the Development Section am i No longer contributing Images Myself. Thanks to XDA and the Moderators!
Guide overhauled like promised to some <3 Let Me know if i missed something
Updated the Guide
Updated the Thread again with more exactly Instructions and a typo fix
Attempting to flash the vbmeta.img I have this problem:
unknown option fastboot --disable-verity
Any idea why fastboot can't figure this command? adb version 30.0.5
Also, what exactly is the reason to flash the vbmeta.img? Is this to allow the phone to boot with the patched image..?
I was still able to boot into android but I can't confirm if the devices is rooted or not.. all programs just hang with no confirmation if root access is granted or denied...
Will this work with android 11?
I get a boot loop when trying to flash magisk img on android 11 with magisk 20.3
Miustone said:
Updated the Thread again with more exactly Instructions and a typo fix
Click to expand...
Click to collapse
jt23738 said:
I get a boot loop when trying to flash magisk img on android 11 with magisk 20.3
Click to expand...
Click to collapse
20.3 is totally outdated: https://github.com/topjohnwu/Magisk/releases
jt23738 said:
I get a boot loop when trying to flash magisk img on android 11 with magisk 20.3
Click to expand...
Click to collapse
Sorry I meant 22.1 magisk
Miustone said:
20.3 is totally outdated: https://github.com/topjohnwu/Magisk/releases
Click to expand...
Click to collapse
Any news on this ? I used the latest Magisk 23.0
My Xperia 5 is dead so i can't Test anymore... Sorry
Thank you @Miustone, your post has been a helpful reference. Some things change over time so it's good to have this guide that is current.
In your guide, I have been looking at the Flashing Firmwares and re-locking the Bootloader... section.
Miustone said:
If You want to relock Your Bootloader...
-Just go into fastboot mode any type in the command prompt (like before in this Guide):
Code:
cd\
cd platform-tools
fastboot oem lock
-Wait for Your Device and disconnect it from USB
-Download and Install the "Xperia Companion" from SONY
-Open the Xperia Companion and select Software Repair
-Select that Your Device can't get recognized (or is a Smartwatch 3 lol)
-Go to the next Page and select the Xperia Smartphone Option
-Continue and wait for the Initialization
-Press and hold Volume DOWN while connecting to USB (You will see the Green Flashmode LED again)
-Continue once Your Device gets recognized and let the Xperia Companion do his work...
Done. Your Bootloader is locked again and most of Your DRMs are restored. But please Note, that unlocking Your Bootloader erases Your unique Device Key FOREVER. That will flag Your Device as "it was unlocked". This can be checked by SONY and everyone else who has this Device in his Hands... (SONY knows it anyways).
Click to expand...
Click to collapse
Please can you advise, confirm that while rooted with Magisk (v23.0), I can relock the bootloader so as to be able to get Sony OTA updates for my Xperia 1?
I had to download firmware with XperiFirm anyway, to get the boot img for Magisk to patch. And because it is newer firmware I just went and flashed it - also because I needed to fix the broken camera/torch caused by rooting with Magisk. So now everything is working again.
So I lose root but I can just root again with Magisk. At that point can I relock the bootloader so that I can receive OTAs, and still be rooted?
OutOfSync said:
Thank you @Miustone, your post has been a helpful reference. Some things change over time so it's good to have this guide that is current.
In your guide, I have been looking at the Flashing Firmwares and re-locking the Bootloader... section.
Please can you advise, confirm that while rooted with Magisk (v23.0), I can relock the bootloader so as to be able to get Sony OTA updates for my Xperia 1?
I had to download firmware with XperiFirm anyway, to get the boot img for Magisk to patch. And because it is newer firmware I just went and flashed it - also because I needed to fix the broken camera/torch caused by rooting with Magisk. So now everything is working again.
So I lose root but I can just root again with Magisk. At that point can I relock the bootloader so that I can receive OTAs, and still be rooted?
Click to expand...
Click to collapse
You need to choose.
Unlocked = Magisk/Root, Freedom, Control
Locked = No Magisk/Root, Freedom, Control
I do also recommend to wait for Pixel Experience. It will come soon with Mainline Kernels for many Xperias... Including OTAs
Hi guys, I cannot watch Netflix after unlock bootloader my J9110, it shows error 5.8. Tried many workarounds but none of them work.
I'm on Android 12 beta 5. Please help!
Thread Updates coming soon including Android 12 GSI flashing + Magisk
1. Unlock bootloader via MI Flash Tool
2. Install ADB and Fastboot Drivers
3. Downloader Latest Platform Tools
4. Open command prompt window in platform tools folder
5. Take phone to fastboot mode (Adb reboot bootloader)
6. Flash the given boot image (Fastboot flash boot boot.img)
7. Flash the given vbmeta (Fastboot flash vbmeta vbmeta.img)
8. Reboot (Fastboot reboot)
9. Download, install and open latest magisk manager in phone. It will reboot phone.
10. Done. You have root now. Verify via root checker.
Credits: @Tigrouzen
is there any bug or issue with miui rom after root? and how to install twrp or any other custom recovery?
ji-r47 said:
is there any bug or issue with miui rom after root? and how to install twrp or any other custom recovery?
Click to expand...
Click to collapse
Some games will start to crash, and some apps wont work because they will detect root and close down. You can flash stock boot and vbmeta image to unroot and they will work.
Unofficial TWRP (compiled by @Tigrouzen) is attached. Flash in fastboot mode and then flash vbmeta from above.
ahsan.ey.ca said:
Some games will start to crash, and some apps wont work because they will detect root and close down. You can flash stock boot and vbmeta image to unroot and they will work.
Unofficial TWRP (compiled by @Tigrouzen) is attached. Flash in fastboot mode and then flash vbmeta from above.
Click to expand...
Click to collapse
Thank you very much
ahsan.ey.ca said:
Some games will start to crash, and some apps wont work because they will detect root and close down. You can flash stock boot and vbmeta image to unroot and they will work.
Unofficial TWRP (compiled by @Tigrouzen) is attached. Flash in fastboot mode and then flash vbmeta from above.
Click to expand...
Click to collapse
Do you have source code for it?
VD171 said:
Do you have source code for it?
Click to expand...
Click to collapse
Not my work, ask @Tigrouzen .
It's working. I don't have to install any ROM to root the phone. Thanks.
This can be done with any version of ROM? I have India version 12.0.9
@sakeyo i dont think region is important for this process, the only diference is the bloatware inside the rom,
if it doesnt works, you can just flash back the stock boot.img and vbmeta.img
or if you want, you can change the ROM to Global
I used XiaomiToolv2 https://www.xiaomitool.com/V2/
It works perfectly on my device. Thanks!
Hi Sakeyo. Please tell me what version of Magisk did you use?
Thanks in advance
asia559571 said:
Hi Sakeyo. Please tell me what version of Magisk did you use?
Thanks in advance
Click to expand...
Click to collapse
Im using the latest magisk version, it works flawlessly
its the version 23
yoshijulas said:
Im using the latest magisk version, it works flawlessly
its the version 23
Click to expand...
Click to collapse
Thank You yoshijulas for your reply and Kind Regards
asia559571 said:
Hi Sakeyo. Please tell me what version of Magisk did you use?
Thanks in advance
Click to expand...
Click to collapse
Hello. I am currently not rooted. I removed Magisk and closed the bootloader. But when I was rooted I always used the latest versions of Magisk.
sakeyo said:
Hello. I am currently not rooted. I removed Magisk and closed the bootloader. But when I was rooted I always used the latest versions of Magisk.
Click to expand...
Click to collapse
To be honest, I only wanted root for the sake of having ViPER4Android. I tried the rootless version, but it failed on my phone... got stuck in a boot loop. I'm using Black Player Ex, the equalizer in tandem with the Mi Sound Enhancer works like a charm. One thing I noticed, is that the sound level on the Global Rom is very low compared to the Chinese version, so I'm sticking to the Chinese Rom. If You come across ViPER that can be installed on our device without the need for root, Please let me know. It's a shame that Xiaomi wouldn't/don't have ViPER pre-installed as a system app?
Best Regards
ahsan.ey.ca said:
Some games will start to crash, and some apps wont work because they will detect root and close down. You can flash stock boot and vbmeta image to unroot and they will work.
Unofficial TWRP (compiled by @Tigrouzen) is attached. Flash in fastboot mode and then flash vbmeta from above.
Click to expand...
Click to collapse
@ahsan.ey.ca I know you just need boot.img and vbmeta.img to get root, but when you installed recovery.img did you get the frozen screen where you can't swipe to unlock twrp?
I'm paranoid, will this boot and vbmeta work on any MiUI version?
Reyproject said:
I'm paranoid, will this boot and vbmeta work on any MiUI version?
Click to expand...
Click to collapse
Not sure.
Probably boot can works.
But the vbmeta certainly works on any version.
Where can I find the boot.img for flashing recovery?
criza said:
Where can I find the boot.img for flashing recovery?
Click to expand...
Click to collapse
Try here:
[IMG][ROOT][PATCHED] Magisk Patched Boot: ROOTED Images Partitions for DANDELION (Redmi 9A / Redmi 9AT)
Magisk Patched BOOT.IMG for DANDELION ROOT / PREROOT ROOTED / PREROOTED Works with: - Xiaomi Redmi 9A - Xiaomi Redmi 9AT Does NOT work with: - Xiaomi Redmi 10A Firmware Versions: - (Engineering) 246 - (Engineering) 440 - (Indonesia)...
forum.xda-developers.com
hey guys!
I recently bought a phone name Micromax in2b. in my country this phone name is symphony z33. I want to root it. I tried every single methods I found on Google/xda/hovatek. By mygisk method my phone got bootloop!
I tried my best! but I can't root it!
so I need help of any expert developers!
I can provide you any type of files!
please can anyone help me?
Thanks in advance!
Basic Information- It's cpu is Unisoc T610
so many phones
use this soc!
so
we need this soc devolopment
Saifulsumaiya71 said:
hey guys!
I recently bought a phone name Micromax in2b. in my country this phone name is symphony z33. I want to root it. I tried every single methods I found on Google/xda/hovatek. By mygisk method my phone got bootloop!
I tried my best! but I can't root it!
so I need help of any expert developers!
I can provide you any type of files!
please can anyone help me?
Thanks in advance!
Basic Information- It's cpu is Unisoc T610
Click to expand...
Click to collapse
Hey... Have you been able to Root Your Device? If not I Can Help You Rooting. You can contact me over telegram using the user name @trippyadive
Saifulsumaiya71 said:
hey guys!
I recently bought a phone name Micromax in2b. in my country this phone name is symphony z33. I want to root it. I tried every single methods I found on Google/xda/hovatek. By mygisk method my phone got bootloop!
I tried my best! but I can't root it!
so I need help of any expert developers!
I can provide you any type of files!
please can anyone help me?
Thanks in advance!
Basic Information- It's cpu is Unisoc T610
Click to expand...
Click to collapse
Hey bro I am using In 2B as well you getting into bootloop make me feel u have bootloader oem unlock & at the same time you were trying to apply custom recovery & you got stuck in boot loop was that the case? Because in that case you will be needing a stock recovery with scatter file & sp flash tool.
Exactly same thing happened with me yesterday when I was trying to root my Micromax Canvas Tab p681 at evening i got into bootloop & till night I fix it by flashing stock recovery & reflashing custom from after factory reset but in my case my rom was stock & boot.img was stock only recovery file was messed up & I had stock recovery handy.
Before getting stuck in bootloop I had did below silly mistake:
1) perform oem unlock
2) flash recovery right after performing oem unlock
What actually happens after performing oem unlock (in lay man's language), when you perform oem unlock a factory reset is performed from your stock recovery, before performing factory reset bootloader verify previous version of recovery before booting to recovery. When you perform oem unlock you instruction bootloader to perform factory reset but when you flash custom recovery immediately after performing oem unlock (without allowing factory reset) your bootloader verify your previous recovery when it detect previous version is different than that of current version you end up in bootloop. Solution is to flash stock recovery via sp flash tool but your scatter file should be correct. There are step I can guide you.
I had been root my Android seens Android 1.6 I have plenty of experience with bootloops .
But before suggesting you any further & try anything out of desperation answer my questions point wise in detail:
1) What were you exactly doing when you stuck in bootloop?
2) Do you have stock recovery file?
3) From which site you downloaded your resources for flashing (link)
4) Does your hardware specs match with my hardware specifications attached?
Unisoc root is easy and there is no need to unlock the bootloader.
You need to sign boot.img if you have applied the Magisk patch and custom vbmeta.img, flash with SPD Research Tool.
straightcore said:
Unisoc root is easy and there is no need to unlock the bootloader.
You need to sign boot.img if you have applied the Magisk patch and custom vbmeta.img, flash with SPD Research Tool.
Click to expand...
Click to collapse
satanic666 said:
plenty of experience with bootloops .
But before suggesting you any further & try anything out of desperation answer my questions point wise in detail:
1) What were you exactly doing when you stuck in bootloop?
2) Do you have stock recovery file?
3) From which site you downloaded your resources for flashing (link)
4) Does your hardware specs match with my hardware specifications attached?
Click to expand...
Click to collapse
Hey my device is also Micromax in 2b...I have rooted the device and flashed a gsi.. but there is a problem I have tried almost 4-5 gsi ROM but 3.5mm headset it's not getting detected like when I plug-in the headset sounds not coming from the headset but coming from phone speaker did you also faced this issue if yes, do you have a solution?
Crayon Shin-chan said:
Hey my device is also Micromax in 2b...I have rooted the device and flashed a gsi.. but there is a problem I have tried almost 4-5 gsi ROM but 3.5mm headset it's not getting detected like when I plug-in the headset sounds not coming from the headset but coming from phone speaker did you also faced this issue if yes, do you have a solution?
Click to expand...
Click to collapse
Hey I'm also using Micromax in 2b. I tried to root my device by flashing patched magisk boot.img via fastboot but I'm unable to root my device it was saying 'read write error' can you tell me the perfect method to root my Micromax in2b?
Praveen999 said:
Hey I'm also using Micromax in 2b. I tried to root my device by flashing patched magisk boot.img via fastboot but I'm unable to root my device it was saying 'read write error' can you tell me the perfect method to root my Micromax in2b?
Click to expand...
Click to collapse
Do you have an unlocked bootloader?
Did I boot into fastboot "adb reboot-fastboot" or bootloader "adb reboot-bootloader" ?
You need to flash in fastbootd, not bootloader.
If you sign magisk patched boot.img and create a signed custom vbmeta, you can flash via the SPD Research Tool without an unlocked bootloader.
straightcore said:
Do you have an unlocked bootloader?
Did I boot into fastboot "adb reboot-fastboot" or bootloader "adb reboot-bootloader" ?
You need to flash in fastbootd, not bootloader.
If you sign magisk patched boot.img and create a signed custom vbmeta, you can flash via the SPD Research Tool without an unlocked bootloader.
Click to expand...
Click to collapse
Thank you so much, now I find my mistake. I tried in bootloader
straightcore said:
Do you have an unlocked bootloader?
Did I boot into fastboot "adb reboot-fastboot" or bootloader "adb reboot-bootloader" ?
You need to flash in fastbootd, not bootloader.
If you sign magisk patched boot.img and create a signed custom vbmeta, you can flash via the SPD Research Tool without an unlocked bootloader.
Click to expand...
Click to collapse
Can u show me how to create a signed custom vbmeta
How to extract public keys from a vbmeta image
How to extract public keys from a vbmeta image
This is a step by step guide showing how to extract public signing keys from a vbmeta image. This will come handy if you plan to make a vbmeta image and still retain the public keys for certain partit
www.hovatek.com
How to create a custom signed vbmeta.img for Unisoc using AVBtool
How to create a custom signed vbmeta.img for Unisoc using AVBtool
If you're into rooting and flashing custom recoveries then Android Verified Boot (AVB) or dmverity is something you should be aware of. We'd dropped a blog post on why dmverity could be causing your p
www.hovatek.com
How to use AVBtool and a private key to sign a Unisoc (SPD) image
How to use AVBtool and a private key to sign a Unisoc (SPD) image
This guide will explain how to sign Unisoc / Spreadtrum (SPD) images (e.g boot, recovery, system etc) using a private key and AVBtool. This guide is ideal for those with vbmeta-sign.img in their firmw
www.hovatek.com
C
Crayon Shin-chan said:
Hey my device is also Micromax in 2b...I have rooted the device and flashed a gsi.. but there is a problem I have tried almost 4-5 gsi ROM but 3.5mm headset it's not getting detected like when I plug-in the headset sounds not coming from the headset but coming from phone speaker did you also faced this issue if yes, do you have a solution?
Click to expand...
Click to collapse
Can you tell me how to root that device? I'm also using same device but I'm unable to root my device.
Praveen999 said:
C
Can you tell me how to root that device? I'm also using same device but I'm unable to root my device.
Click to expand...
Click to collapse
Contact me on telegram. Mod edit: TG link removed as per XDA's TG Chat Rules.
boot.img magisk patched, signed
custom vbmeta, signed
"no unlock bootloader needed"
"Micromax/E7544/E7544:11/RP1A.201005.001/50:user/release-keys"
File on MEGA
mega.nz
straightcore said:
boot.img magisk patched, signed
custom vbmeta, signed
"no unlock bootloader needed"
Click to expand...
Click to collapse
This is old version man don't use it it's have some bugs and I used Canary version the file you gave link from hovatek https://www.hovatek.com/forum/thread-42955.html is mine ...it is my post
straightcore said:
boot.img magisk patched, signed
custom vbmeta, signed
"no unlock bootloader needed"
"Micromax/E7544/E7544:11/RP1A.201005.001/50:user/release-keys"
File on MEGA
mega.nz
Click to expand...
Click to collapse
You no need to worry I have sent him everything he needed to do his work
Canary:
File on MEGA
mega.nz
straightcore said:
Canary:
File on MEGA
mega.nz
Click to expand...
Click to collapse
Ohh are you Gargoyle? From hovatek?
Latest Magisk v25.0 Micromax IN 2b
File on MEGA
mega.nz
Changelog
Magisk Changelog
The Magic Mask for Android
topjohnwu.github.io
straightcore said:
Latest Magisk v25.0 Micromax IN 2b
File on MEGA
mega.nz
Changelog
Magisk Changelog
The Magic Mask for Android
topjohnwu.github.io
Click to expand...
Click to collapse
not working bro!
can u patch my boot.img and vbmeta ?
plz bro
https://drive.google.com/file/d/1cV3o3suLcq4TnfJrOMpaIwzd8vJTW0Ce/view?usp=drivesdk here is my files
Hi all,
I come from an old RN 4x (mido) to the RN 11 Pro 5G (veux) and a little bit lost
What steps should I absolutely do?
- ask for unlock bootloader : I have to wait 168h on miflash screen <=> I will wait
- download firmware : already with V13.0.5.0.SKCEUXM
- install firmware ?
- download TWRP or Orangefox ?
[SHARED][RECOVERY][UNOFFICIAL] TWRP 3.7.0_12 for VEUX/PEUX
Hello everyone, one user under the nickname yurxxl from the site 4 PDA, at my request, will assemble a recovery for us, it was his assembly that I posted in the topic...
forum.xda-developers.com
OrangeFox Recovery Downloads
OrangeFox Recovery is one of the most popular custom recoveries in android ecosystem, with amazing additional features that are not present in other recoveries. We support a host of devices
orangefox.download
- Install TWRP or OrangeFoxx
- download Custom ROM (which one? I was on lineageOS on my RN 4x)
- Install Custom ROM
- download Gapps (which one?)
- Install Gapps
- Install magisk manager and Magisk Fox
Restore all my data.. and that's all folks ?
Do not remenber about that :
Recovery File
vendor_boot File
Thanks for all
It all depends on what you want to install.
In general the mode of installation is explained in the OP.
If it doesn't, browse the thread or ask.
Firmware is important.
In any case for a first installation you will have to format the data.
Restoring your data is not possible from MIUI to AOSP and vice versa (or maybe with a third party app).
Difficult to answer precisely on relative questions.
I thought I was clear in my request
Do not know what means OP !
My RN 11 Pro 5G is new and would like to know what steps I had to follow in order to be roooted as today on my RN 4x.
I have done it on my old RN 4x but 7 years ago.
The goal is to be roooted and instal a custom ROM but sure that I need to do many steps before !
Do not care to format it because it is brand new... I am still on my RN 4x...
All my datas will be restored by SwiftBackup so don't care about that !
So the installation will be from scratch => just need the steps in order to do it properly
No need for Twrp/O.f to root.
Use this method with the img corresponding to your device.
O.P=first post.
but first:
Unlock bootloader
Xiaomi Community
new.c.mi.com
Apply for unlocking Mi devices
en.miui.com
u_no_fr said:
Do not know what means OP !
Click to expand...
Click to collapse
"OP" on XDA is usually meant in TWO different meanings:
In this context and @NOSS8's post, it's the Opening Post of a thread i.e. its post #1.
The second meaning is that a thread owner is also called the OP, the opening poster.
Oswald Boelcke said:
"OP" on XDA is usually meant in TWO different meanings:
In this context and @NOSS8's post, it's the Opening Post of a thread i.e. its post #1.
The second meaning is that a thread owner is also called the OP, the opening poster.
Click to expand...
Click to collapse
Third and final meaning is "Original poster"
NOSS8 said:
No need for Twrp/O.f to root.
Use this method with the img corresponding to your device.
O.P=first post.
but first:
Unlock bootloader
Xiaomi Community
new.c.mi.com
Apply for unlocking Mi devices
en.miui.com
Click to expand...
Click to collapse
Ok guy,
Still 25h for unlock with miflash
ok for root with magisk but if I want to try Custom ROM before, I will need to Patch Boot Image File ....
But with TWRP and magisk installed I just have to choose the ROM and it will be done ;o)
u_no_fr said:
Ok guy,
Still 25h for unlock with miflash
ok for root with magisk but if I want to try Custom ROM before, I will need to Patch Boot Image File
with TWRP and magisk installed I just have to choose the ROM and magisk will do it alone ;o)
Click to expand...
Click to collapse
"I will need to Patch Boot Image File
with TWRP"
Fastboot command
NOSS8 said:
"I will need to Patch Boot Image File
with TWRP"
Fastboot command
Click to expand...
Click to collapse
It was not a mistake but forgot the point at the end of my sentence
u_no_fr said:
It was not a mistake but forgot the point at the end of my sentence
Click to expand...
Click to collapse
forgetting a point at the end of a sentence is an error that leads to errors.