For Android Q beta's root, I’ve tried with different methods but failed, finally I find the solution!
Here is the instruction:
1.unlocked your device.
2.reboot to the bootloader mode (adb reboot booloader)
3.flash the patched boot.img file I supported via PC, link: https://drive.google.com/open?id=1brp5k-wW4X6nwP6qU6Nxid5h1owfK875 (fastboot flash boot beta5.img *or you can rename it)
4.install Magisk canary from this link: https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337 and then install the app which name is app-release.apk
*if something is wrong, plz download the Magisk manager again from the manager app you have installed yet (I don’t know why, but I guess something wrong when OP uploaded the file.)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5.enjoy!
Please....... just stop with these pre-patched boot images.
There is ZERO reason to use these pre-patched boot images. If you can't get root via the normally accepted Magisk root methods, it is because you are not following instructions - it's not because the method is flawed.
This is a thread I started that walks people through the normally accepted Magisk root methods in great detail so that even the most rank beginner should be able to follow them to success. Feel free to follow it, or any of the other instructions found on how to root using Magisk without using these dumb pre-patched boot image files that users want you to download and flash. I'm not posting this in a effort to push people to my thread, but I am posting this in a effort to keep people from using these pre-patched boot images. Like really....... stop using them.......
There is also a section in the thread I created that talks about the shortcomings of using this pre-patched boot image method. At the very least, make sure you read that and understand the faults of using this root method prior to using it. It will save you a lot of time and heartache in the future when it comes time to update your phone.
sic0048 said:
Please....... just stop with these pre-patched boot images.
There is ZERO reason to use these pre-patched boot images. If you can't get root via the normally accepted Magisk root methods, it is because you are not following instructions - it's not because the method is flawed.
This is a thread I started that walks people through the normally accepted Magisk root methods in great detail so that even the most rank beginner should be able to follow them to success. Feel free to follow it, or any of the other instructions found on how to root using Magisk without using these dumb pre-patched boot image files that users want you to download and flash. I'm not posting this in a effort to push people to my thread, but I am posting this in a effort to keep people from using these pre-patched boot images. Like really....... stop using them.......
There is also a section in the thread I created that talks about the shortcomings of using this pre-patched boot image method. At the very least, make sure you read that and understand the faults of using this root method prior to using it. It will save you a lot of time and heartache in the future when it comes time to update your phone.
Click to expand...
Click to collapse
Useing Magisk Manager to root and unroot is only one way. It is neither "normal" or "the correct way". Many of us never do OTAs, we sideload or flash factory images to update. Please stop trashing other people's threads because you have a simple narrow personal idea of what is correct or not. Be helpful and kind or be silent.
12paq said:
Useing Magisk Manager to root and unroot is only one way. It is neither "normal" or "the correct way". Many of us never do OTAs, we sideload or flash factory images to update. Please stop trashing other people's threads because you have a simple narrow personal idea of what is correct or not. Be helpful and kind or be silent.
Click to expand...
Click to collapse
No.
I realize there are different ways of doing things, but there is ZERO reason for people to be pushing this method of sharing pre-patched boot images.
ZERO.....
PS - I am being helpful when I steer people away from this root method.
@sic0048 My apologies, I guess you didn't understand my comment. It's not just about your personal version of being correct and forcing it on others, it's your bad attitude and lack of good forum etiquette. Being correct, wether it be your personal version of correct or not, does not excuse bad behavior. You have been warned and called out in the past by moderators and users. I am not a moderator currently, and I do not go back in forth with arguments on forums, so this will be my last comment here. Good day.
Are you sure this even works? "Error Boot Prepare" shows when booting. Unable to boot
Related
Dear All,
1) I have update my Acer A500 to the latest possible version via Acer
2) I have followed the steps provided by Mlopik <Click Here> to root my A500
3) After following through, I realise there is no options for me to install a new ROM. I used Goo.Im -> Flash ROMS, I get the following picture
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Anyone in this forum with a A500 staying in Singapore?? Can you please PM me so at least I can talk to someone for help....
Thanks alot ...
Vipe.teo said:
Dear All,
1) I have update my Acer A500 to the latest possible version via Acer
2) I have followed the steps provided by Mlopik <Click Here> to root my A500
3) After following through, I realise there is no options for me to install a new ROM. I used Goo.Im -> Flash ROMS, I get the following picture
Anyone in this forum with a A500 staying in Singapore?? Can you please PM me so at least I can talk to someone for help....
Thanks alot ...
Click to expand...
Click to collapse
You need to unlock your bootloader and flash a recovery
blackthund3r said:
You need to unlock your bootloader and flash a recovery
Click to expand...
Click to collapse
Thanks for your reply, can you recommend threads to teach me how to go about doing it?
I believe Mlopik page did mention if I follow correctly, I would have already unlocked my bootloader, am I right?
First off, my or anybody's PM is not tech support. Sorry to be strict about this, but people with issues should post in the forums.
As with your issue, the reason you get the "dead android" is because you still have the stock recovery installed. It's looking for an Acer Signed update.zip, and there's not one there. Hence the dead android.
3 reasons this happened.
1. You didn't install a CWM recovery
2. You installed a CWM Recovery, but, booted directly into your stock Operating system which still contained the 2 files "boot.recovery.p" and "install.recovery.sh". When you boot with especially the 2nd file (sh) still there, it immediately installs the stock recovery, overwriting your CWM recovery. Do this enough times, and you might corrupt your recovery partition.
3. which is bad, is that your recovery partition is physically corrupt, and won't allow the new CWM recovery to install.
Number 2 is usually the most common when coming off an OTA. People just get in a hurry and don't read all the instructions, or search the issue.
Best thing is to make sure you have the Skrilax_cz V8 unlocked bootloader installed. This is the number one thing. You can tell because the first screen you see on boot is the V8 bootloader
If you do, you can then fastboot a CWM recovery via a command prompt window.
or
you can use one of the tool packages available to install the CWM recovery, like AfterOTA, blackthunders tool, or use a command window NVFlash.
There's no need for anybody to post a step by step instructions, as there already are. You can check Civato's guide in the sticky at the top of the forum.
MD
Moscow Desire said:
First off, my or anybody's PM is not tech support. Sorry to be strict about this, but people with issues should post in the forums.
As with your issue, the reason you get the "dead android" is because you still have the stock recovery installed. It's looking for an Acer Signed update.zip, and there's not one there. Hence the dead android.
3 reasons this happened.
1. You didn't install a CWM recovery
2. You installed a CWM Recovery, but, booted directly into your stock Operating system which still contained the 2 files "boot.recovery.p" and "install.recovery.sh". When you boot with especially the 2nd file (sh) still there, it immediately installs the stock recovery, overwriting your CWM recovery. Do this enough times, and you might corrupt your recovery partition.
3. which is bad, is that your recovery partition is physically corrupt, and won't allow the new CWM recovery to install.
Number 2 is usually the most common when coming off an OTA. People just get in a hurry and don't read all the instructions, or search the issue.
Best thing is to make sure you have the Skrilax_cz V8 unlocked bootloader installed. This is the number one thing. You can tell because the first screen you see on boot is the V8 bootloader
If you do, you can then fastboot a CWM recovery via a command prompt window.
or
you can use one of the tool packages available to install the CWM recovery, like AfterOTA, blackthunders tool, or use a command window NVFlash.
There's no need for anybody to post a step by step instructions, as there already are. You can check Civato's guide in the sticky at the top of the forum.
MD
Click to expand...
Click to collapse
Hi, thanks for coming to my aid, sorry for PM-ing U asking for help.... but I'm a super noob for this....:silly:
1) I have a boot screen by Skrilax_cz, but how do I fastboot a CWM recovery via a command prompt window?
2) A few min ago, I tried to use AfterOTA it got stuck at [3/4 flashing recovery] for a long time..... (Force restart)
3) I saw a solution <Click Here> then after downloading the recovery.img and running the code... It say done but after i restart nothing happen.
4) I continue using AfterOTA, again it got stuck at [3/4 flashing recovery] for a long time.....(Force restart)
I out of option....
erm... Help ???
Use fastboot to do a complete wipe.
Run ICSROOT. Zip to get rid of the boot.p file.
Reflash the v8 and cwm using apxflash tool
Boot straight to cwm and flash yr rom.
Do not use any type of rom manager apps to flash roms
Sent from my GT-I9300 using Tapatalk 2
FIXED !!!
Yeah !!! Got It to work !!!
Big THANKS to all who have help and spend time answering my noob questions...
THANK !!!!
Install CM14 for OnePlus X (The Unofficial)
** How to Install TWRP for the 3.1.0 version you installed Oxygen.
B1: Starting Fastboot mode by turning off the power on. Then hold down + to the source.
Step 2: Install the driver and connect to the computer (HD drivers installed on the network to find it)
B3: Run cmd (run -> cmd) command fastboot boot attachments and enter this download Mod edit link removed
B4: boot into TWRP Self.
** The Stock 2.2.2 ROM you are using the network attempt to open up the OEM and then down Flashfy unbootloader install TWRP on CM ROMs directly or similar 13 and then into TWRP always offline.
** Note: Back up your data before doing us avoid errors arising restore offline.
** Download ROM CM 14: Mod edit link removed
** Link Download Grapps:Mod edit link removed
** Conducted into TWRP and wipe data, cache partitioning, Dalvik Cache. Flash ROM + Grapps and restart.
This is an experiment with me what errors arise not responsible. For those you love to dabble and discourage those you do not know and do not understand anything. People are already getting a bit bored Android does not dabble to dabble like new. : D
Path: Mod edit link removed
Vietnamses : Mod edit link removed
downloading, will report back soon.
Cam on
Thanks much
Post some screenshots.
failed to flash twrp ox 3.1 (https://www.fshare.vn/file/8AH9KRVS4URW). I tried flash it using twrp 3.0.2.0, but failed too
Well, this is interesting.. The step-by-step guide is a bit confusing though. I will download and try the 'ol good method of flashing ROM, gapps and supersu. Hope it works!
namquang93 said:
failed to flash twrp ox 3.1 (https://www.fshare.vn/file/8AH9KRVS4URW). I tried flash it using twrp 3.0.2.0, but failed too
Click to expand...
Click to collapse
can u mirror it? litle bit confusing
Sent from my ONE E1003 using XDA-Developers mobile app
be_are said:
can u mirror it? litle bit confusing
Sent from my ONE E1003 using XDA-Developers mobile app
Click to expand...
Click to collapse
here you go: https://drive.google.com/file/d/0B_Km0FbYnea1aDdIaTEydElhUkk/view?usp=sharing
twrp has not made it to 3 ox you have to use a downgrade to get a fresh start using unbrick method, (keep flashable backup via flashify) get twrp installed with the new (old) boot loader, flash cm14+ext. and you are done.
if you had cm13 or the likes, please confirm if you CAN upgrade to 14 before ox people start trying to install without knowing if it even has android 6 (last update i saw on the branch was from june 7 so idk)
teamwin does not have twrp for the ox 3 on oneplus x yet (on their releases anyway) so you have to follow some other process to downgrade to a twrp'able os (and a backup) before trying yo install this
if i see any info from people who have been able to update (and if it has android 7) i'll try to make a video on the process (in white, Texan english)
Please remove this page.
namquang93 said:
failed to flash twrp ox 3.1 (https://www.fshare.vn/file/8AH9KRVS4URW). I tried flash it using twrp 3.0.2.0, but failed too
Click to expand...
Click to collapse
Did you try boot into it:
> fastboot boot twrp_for_ox_3.1.0.img
Seems like the guide says you have to boot into it, not flash it.
ksigit said:
Did you try boot into it:
> fastboot boot twrp_for_ox_3.1.0.img
Seems like the guide says you have to boot into it, not flash it.
Click to expand...
Click to collapse
You're right. I tried fastboot boot twrp_for_ox_3.1.0.img instead of fastboot flash recovery twrp_for_ox_3.1.0.img and it booted into twrp_for_ox_3.1.0. But it still return an error when flash CM14, the same of twrp 3.0.2.0.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
namquang93 said:
You're right. I tried fastboot boot twrp_for_ox_3.1.0.img instead of fastboot flash recovery twrp_for_ox_3.1.0.img and it booted into twrp_for_ox_3.1.0. But it still return an error when flash CM14, the same of twrp 3.0.2.0.
Click to expand...
Click to collapse
Looks like a successful install to me. Could you provide twrp logs?
With whose permission did you post this build here ? Don't you think there was a reason that even after a complete build of CM14 it was still not posted to the forums ?
I am asking you, as politely as possible, to remove the links and this fake procedure, when N is ready, it will be shared, you might find phony builds or legit but non working ones on the interweebz, that doesn't mean it gives you the right to share it just because you think its cool, because its not.
Take it down.
EDIT: Sure, if you build yourself and want to share it then you're more than welcome.
And then they will cry if things are broken !! Take it down folk !
Sent from my ONE E1003 using XDA-Developers mobile app
This Build was just a test build, what made u think that i will not post it here on xda if the rom booted? We, the team are working to make it work but yeah dont post the builds from afh here, will update u all for sure when its done. I think it was my mistake to not to make that build private. -_-
It flashes successfully but doesn't boot, goes back into recovery. Still, great work.
congrats for succesfull starter build
hats off !!!!! to you guys ([/B]developers off this rom) :good:
Flashed with/without gapps. Doesn't boot - goes back 2 recovery
foster095 said:
Flashed with/without gapps. Doesn't boot - goes back 2 recovery
Click to expand...
Click to collapse
Kindly refer to the developer's post, POST #16
Sorry for the post, my question didn't really get answered on the General Q&A Nood Friendly Thread:
Xenophoresis said:
I have Android 9 and August 1, 2020 security patch on it (YouTube was mentioning security patches? dunno why).
I would like TWRP and a future goal of changing to Lineage OS/Tissot.
Which rooting guide can I follow?
( I got confused with the available threads.)
Click to expand...
Click to collapse
After posting, I tried follow this guide thread
I was able to do step 1 which is to unlock but, I don't know if I should still be flashing a Stock Fastboot ROM?
Also there is no link for TWRP, or which version of TWRP I should get...
The last time I rooted something was a Galaxy Note 2 back in 2012-ish so my relevant knowledge is definitely expired.
Please give me a lead on where to find the correct TWRP file and further instructions.
you want step by step guide to flash custom rom?
- You have unlocked bootloader?
- what OS version you are on at the moment ?
Dont worry i will help you in best of my knowledge i have been through what you are going after some time i learned answer question and we will begin
Yes, my bootloader is already unlocked and fastboot was enabled.
OS is stock Android 9, Aug 2020 security patch:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
No Fastboot ROM (if that is necessary) or TWRP is installed yet.
PS: I do not know where or which TWRP I should be getting for this phone
Xenophoresis said:
Yes, my bootloader is already unlocked and fastboot was enabled.
OS is stock Android 9, Aug 2020 security patch:
No Fastboot ROM (if that is necessary) or TWRP is installed yet.
PS: I do not know where or which TWRP I should be getting for this phone
Click to expand...
Click to collapse
There is a tutorial u can follow on youtube by Vikram, for Pie with August 2020 patch. N u can download what it needs in the description. Its in Indian language but u can follow what he do. Should be okay n safe
Good luck
Lost149ers said:
There is a tutorial u can follow on youtube by Vikram, for Pie with August 2020 patch. N u can download what it needs in the description. Its in Indian language but u can follow what he do. Should be okay n safe
Good luck
Click to expand...
Click to collapse
I was hoping to get instructions or help in English; I've watched his YouTube tutorial in Indian but I was afraid that I'd do something wrong because I didn't understand what he said.
You can follow the instructions provided for LOS:
https://wiki.lineageos.org/devices/tissot/install
Simply exchange the LOS installing part with the ROM of your choice.
Xenophoresis said:
I was hoping to get instructions or help in English; I've watched his YouTube tutorial in Indian but I was afraid that I'd do something wrong because I didn't understand what he said.
Click to expand...
Click to collapse
timeo78 said:
You can follow the instructions provided for LOS:
https://wiki.lineageos.org/devices/tissot/install
Simply exchange the LOS installing part with the ROM of your choice.
Click to expand...
Click to collapse
Thank you, I'm done with the custom rom and root
Sorry for late reply i couldn't login because of xda forum migration process
steps i used:
- install Twrp (download latest version details below)
- download custom rom and gapps (and transfer it into sdcard or internal storage or your phone)
- download Adb/fastboot tool and drivers (download it in windows pc install it details below)
- Install Twrp (download it from https://dl.twrp.me/tissot/) there are 2 files .zip and .img you would need fastboot and adb drivers https://androiddatahost.com/uq6us install adb minimal in location where of your choice copy twrpX.XXXX.img file beside adb/fastboot.exe , from start menu open command prompt right click run as administrator locate to adb/fastboot folder .
Power off your mi a1 when its powerd off hold down volume down and power button until you see fastboot mode on the phone connect it to pc wait for drivers to install let me know if you need in this regard. Inside command prompt run " fastboot devices " if you see device with bunch of numbers below than it means your phone is connected and drivers are working than enter this command " fastboot boot twrpXX.XXXX.img " it will take no more than 5 seconds your phone will turn on into twrp recovery there you can copy twrpxx.xxx.zip file to your internal storage or sd card flash it when its done restart -> Recovery.
Warning: After flashing twrp zip dont restart to system if you do your phone will show you message that phone has been destroyed so dont restart .
- Installing custom roms: download custom rom of your choice transfer it into internal or sd card from twrp install-locate to custom rom .zip file and flash it also keep in mind lots of roms didn't include gapps so you have to download it from opengapps(for android 8-10) and nikgapps(android 11). Flash gapps . Keep in mind after installing custom roms you will lose twrp recovery so if you want twrp at this stage go ahead and install it
- If you want root access download and flash magisk
Its always good practice to keep stock rom and xiaomi flash tool with you just in case if something goes wrong you can reflash stock rom and boot normally.
Let me know if you need help
Cheers
Hi there,
I've recently taken the plunge and decided to root my phone. I followed all the instructions and everything went fine except I can't get Magisk to install. When I run root checker it confirms my phone is successfully rooted, see screenshot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But when I go into Magisk it fails the installation saying 'Unable to check signature'. See screenshots below
Looking at the installation instructions here https://topjohnwu.github.io/Magisk/install.html I believe as Ramdisk is 'Yes', then my phone is ready to install Magisk. I believe that if I patch my phone with a boot.img file then I should be able to successfully install Magisk. However, 1) I'm not sure it will given the error I'm getting and 2) wherever I search I cannot seem to download the correct firmware for my phone to be able to get the correct boot.img file that I need. Here are the screenshots showing the installed software version.
I'd be super appreciative to anyone that can advise me as to what to do next to try and resolve the installation issues so that I can benefit from the wonders of Magisk.
Thank you
f19fox said:
Hi there,
I've recently taken the plunge and decided to root my phone. I followed all the instructions and everything went fine except I can't get Magisk to install. When I run root checker it confirms my phone is successfully rooted, see screenshot.
View attachment 5290275
But when I go into Magisk it fails the installation saying 'Unable to check signature'. See screenshots below
View attachment 5290281View attachment 5290283
Looking at the installation instructions here https://topjohnwu.github.io/Magisk/install.html I believe as Ramdisk is 'Yes', then my phone is ready to install Magisk. I believe that if I patch my phone with a boot.img file then I should be able to successfully install Magisk. However, 1) I'm not sure it will given the error I'm getting and 2) wherever I search I cannot seem to download the correct firmware for my phone to be able to get the correct boot.img file that I need. Here are the screenshots showing the installed software version.
View attachment 5290293View attachment 5290297
I'd be super appreciative to anyone that can advise me as to what to do next to try and resolve the installation issues so that I can benefit from the wonders of Magisk.
Thank you
Click to expand...
Click to collapse
Flash magisk zip in via recovery
Austinredstoner said:
Flash magisk zip in via recovery
Click to expand...
Click to collapse
Hi. Thank you for your reply and advice. I flashed Magisk using TWRP recovery but it still won't install. Here is the screenshot. I also uninstalled the App and re-downloaded as per these instructions https://bit.ly/32P3Z9z but I still get the same error
Do you or anyone else have any more suggestions please?
Thanks!
@f19fox: Apologies to be hijacking your thread.
Build Number: NMF26X.J510FNXXU2BRJ4
Android Running Version: 7.1.1
I downloaded the IMG file of the BRJ4 raw boot image from firmware.mobi, successfully patched it via the Magisk app, and subsequently flashed the patched boot image via TWRP (selecting the boot partition within TWRP).
However, the Magisk card within the app still displays N/A within the app.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch-driven user interface, with no more volume rocker or power buttons to mash. The GUI is also fully XML-driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen-driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout and true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
Source Code:GitHub: https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance: http://gerrit.twrp.me
Hello, this is TWRP, for Xiaomi Mi Note 10 Lite (toco)
Touch and ADB work
Sideload
Fastbootd
MTP
USB OTG is working
Decryption IS NOT yet supported for A12
Send me a beer: PayPal
Kernel source: https://bigota.d.miui.com/V13.0.1.0.SFNMIXM/miui_TOCOGlobal_V13.0.1.0.SFNMIXM_b856dc7481_12.0.zip
Telegram group: https://t.me/ahq254chat
Downloadhttps://bit.ly/3t197EP
InstallationPrerequisites: ADB & Fastboot platform-tools
1. Download the recovery from the link above
2. Boot your device into bootloader mode (Power + Volume Up)
3. Open a command window in the folder containing the downloaded recovery
4. Type the following command and hit Enter
fastboot flash recovery TWRP-3.6.2-12-0530-toco-DennisMurimi.img
Click to expand...
Click to collapse
5. Type this command and hit Enter to boot into recovery
fastboot reboot recovery
Click to expand...
Click to collapse
6. Confirm successful installation when you boot into the new TWRP
Reserved
Download links please . . .
cyned said:
Download links please . . .
Click to expand...
Click to collapse
The link is literally right there in the post. Take your time and read through
AndroidHQ254 said:
The link is literally right there in the post. Take your time and read through
Click to expand...
Click to collapse
At time of post all links reverted to a blog, I don't even remember it. Maybe browser issue, my bad.
cyned said:
At time of post all links reverted to a blog, I don't even remember it. Maybe browser issue, my bad.
Click to expand...
Click to collapse
Could have been a derp
hi, after flashing this update the data became encrypted. i was in twrp 3.5.0 before flashing this.
ZeA_Quin said:
hi, after flashing this update the data became encrypted. i was in twrp 3.5.0 before flashing this.
Click to expand...
Click to collapse
A12 data decrytion is not yet supported. Wait for TWRP team to implement that
Great Work Thank you for keeping this Device up to date almost singlehandedly. Really appreciate the work !
Hi, can you suggest me please a video tutorial? (It has not to be toco, but with the same steps). i tried lots of tutorials and nothing worked. I booted to your twrp, but could not flash it.
Any plans to port TWRP 3.7.0 (Android 12.1 branch)?
This new version finally supports Android 12 decryption.
Chris7375 said:
Great Work Thank you for keeping this Device up to date almost singlehandedly. Really appreciate the work !
Click to expand...
Click to collapse
This is possible because of the users coming in to support the work. So if you can join the supporters team, it will help the work continue even for longer
Gloter125 said:
Hi, can you suggest me please a video tutorial? (It has not to be toco, but with the same steps). i tried lots of tutorials and nothing worked. I booted to your twrp, but could not flash it.
Click to expand...
Click to collapse
A video will come on my youtube channel so ensure that you are subscribed
Hello, is it possible to flash SuperSU with this on MIUI 13.0.2.0 even tough the (de-/)encryption is not supported on A12?
ROOT_Neko said:
Hello, is it possible to flash SuperSU with this on MIUI 13.0.2.0 even tough the (de-/)encryption is not supported on A12?
Click to expand...
Click to collapse
Im sorry but im really nervous since i have bad experiences with the sm-a750fn that also had unofficial TWRP and i just want to root my phone but as far as i noticed i cannot access adb in the stock recovery, thus unable to sideload SuperSU.