Related
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface 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.
TWRP 3.2.1 Changelog: https://twrp.me/site/update/2017/12/09/twrp-3.2.1-0-released.html
Installation instructions: Use the official TWRP app (requires root), available here and here. If you already have TWRP installed, you can also download the latest available img and flash it from recovery.
DOWNLOAD (palman): https://dl.twrp.me/palman/
DOWNLOAD (v500): https://dl.twrp.me/v500/
More info: https://twrp.me/devices/lggpad83.html
Warning: builds for v500 require kitkat bootloader. If you are stuck on Lollipop bootloader, check this post.
Device source (palman): https://github.com/TeamWin/android_device_lge_palman
* The kernel in palman source is from 5.1 official build (source found here).
Device source (v500): https://github.com/TeamWin/android_device_lge_v500
* The kernel in v500 source is based on cm-14.1 sources.
XDA:DevDB Information
Team Win Recovery Project, Tool/Utility for the LG G Pad 8.3
Contributors
fefifofum, Dees_Troy, bigbiff
Source Code: https://github.com/omnirom/android_bootable_recovery
Version Information
Status: Stable
Created 2015-06-15
Last Updated 2017-12-10
Thanks very much for this! Great work! That is really nice that there is now official support for awifi/v500.
I assume the images are bumped?
Are the kernel sources for official twrp using your kernel sources?
Sources
This is the device repo for awifi/v500: https://github.com/TeamWin/android_device_lge_v500
The kernel in awifi/v500 repo was compiled from here, which is V50030A based.
This is the device repo for palman/v510: https://github.com/TeamWin/android_device_lge_palman
The kernel in palman/v510 repo is from 5.1 official build.
So, now we should be able to just flash the .img file directly within TWRP to update.
Deltadroid said:
So, now we should be able to just flash the .img file directly within TWRP to update.
Click to expand...
Click to collapse
Yes!
The repo for v510 is going to be renamed since it doesn't need to follow the "cyanogen" way, which is using the model name instead of the device name. That's why there is a little confusion with the names v500/awifi and v510/palman. The GPE repo will be named palman (which is the correct way) and the non GPE repo will stay as v500 (it should be called awifi), since almost every custom rom uses "cyanogen" way. If we wanted the non GPE to be named correctly we would need the devs of every custom rom to add an assert to their boardconfig so both, v500 and awifi, would be valid at installation time. It's just one line change.
Do we need to have TWRP recovery already flashed or can I just flash this recovery in the stock 20D with root?
Do we only need root access and flash the recovery using the TWRP manager from Play Store in stock 20D?
fefifofum, firstly, thanks for making an official TWRP for the V510.
Secondly, can you please enable backup of recovery partition?
luisbraz said:
Do we need to have TWRP recovery already flashed or can I just flash this recovery in the stock 20D with root?
Do we only need root access and flash the recovery using the TWRP manager from Play Store in stock 20D?
Click to expand...
Click to collapse
There are three ways to install TWRP explained at the installation details. Two of them require root and the third one requires twrp >= 2.8.4.0. Choose the one that is easier for you, they all should work.
aidfarh said:
fefifofum, firstly, thanks for making an official TWRP for the V510.
Secondly, can you please enable backup of recovery partition?
Click to expand...
Click to collapse
I could try, but it needs to go through gerrit. Why would you need to backup recovery partition?
fefifofum said:
Why would you need to backup recovery partition?
Click to expand...
Click to collapse
It's not strictly needed, but good to have for completeness. For example, if I flash a new version of TWRP and then find that's there a bug, I could just restore the previous version from backup. Of course, I could always just use fastboot or flashify to flash the old version, but it's nice to have the option.
fefifofum said:
There are three ways to install TWRP explained at the installation details. Two of them require root and the third one requires twrp >= 2.8.4.0. Choose the one that is easier for you, they all should work.
I could try, but it needs to go through gerrit. Why would you need to backup recovery partition?
Click to expand...
Click to collapse
I know, but I just want to be shure that this time I don't brick the tablet.
So you confirm that when we are stock with version 20D we just need root access? It's not necessary anymore a loky exploitable aboot?
Sorry for being a pain in the ass!
EDIT: Thank you @fefifofum for your work
I have installed the TWRP manager and selected install TWRP. Which version should I flash? The latest 2.8.1.0? And the twpr - awifi. img or the openrecovery - twrp - awifi. img?
I'm on stock 20d version with root. Thanks in advance.
aidfarh said:
It's not strictly needed, but good to have for completeness. For example, if I flash a new version of TWRP and then find that's there a bug, I could just restore the previous version from backup. Of course, I could always just use fastboot or flashify to flash the old version, but it's nice to have the option.
Click to expand...
Click to collapse
Old versions will still be available to download, so if a new version had issues you could always download and install an older version. No need to backup recovery I guess...
luisbraz said:
I know, but I just want to be shure that this time I don't brick the tablet.
So you confirm that when we are stock with version 20D we just need root access? It's not necessary anymore a loky exploitable aboot?
Sorry for being a pain in the ass!
EDIT: Thank you @fefifofum for your work
Click to expand...
Click to collapse
We don't need loki anymore, you just need to be on kitkat bootloader.
luisbraz said:
I have installed the TWRP manager and selected install TWRP. Which version should I flash? The latest 2.8.1.0? And the twpr - awifi. img or the openrecovery - twrp - awifi. img?
I'm on stock 20d version with root. Thanks in advance.
Click to expand...
Click to collapse
It looks like TWRP manager didn't update the images for the gpad. I will talk to them so they fix it and remove the old images, there should only be one version available: 2.8.6.0. Until then, please use the "dd" installation method.
fefifofum said:
It looks like TWRP manager didn't update the images for the gpad. I will talk to them so they fix it and remove the old images, there should only be one version available: 2.8.6.0. Until then, please use the "dd" installation method.
Click to expand...
Click to collapse
Thanks.
I think I'll wait for the TWRP manager update.
EDIT: Couldn’t wait and tried the dd method. For the first time, after thousands of attempts, I have the TWRP installed in the tablet!
luisbraz said:
Thanks.
I think I'll wait for the TWRP manager update.
EDIT: Couldn’t wait and tried the dd method. For the first time, after thousands of attempts, I have the TWRP installed in the tablet!
Click to expand...
Click to collapse
Glad to hear that! It seems the app TWRP manager cannot reach the new servers where official builds of TWRP are, so it's better not to use the app installation method to avoid installing old versions.
@fefifofum thanks a lot!!! I'm using slim alpha 4, what bootloader should I flash to solve the backlight problem? Thanks again
Pd: use rashr app to flash twrp, download .img and flash from internal memory, no problems. Don't use twrp manager.
bokoy said:
@fefifofum thanks a lot!!! I'm using slim alpha 4, what bootloader should I flash to solve the backlight problem? Thanks again
Pd: use rashr app to flash twrp, download .img and flash from internal memory, no problems. Don't use twrp manager.
Click to expand...
Click to collapse
I guess V50010B bootloader is what you need, but then you will probably have brightness issues while using this recovery.
New version
TWRP 2.8.7.0 released.
fefifofum said:
TWRP 2.8.7.0 released.
Click to expand...
Click to collapse
Hi all!
I have now TWRP 2.8.6.0 taken from here: http://forum.xda-developers.com/lg-g-pad-83/orig-development/recovery-twrp-2-8-2-0-v500-t2968472
Which are the differences between these recoverys? Which is the better to install?
Thanks!
Hey Guys! How to upgrade from this version? http://forum.xda-developers.com/lg-g-pad-83/orig-development/recovery-twrp-2-8-2-0-v500-t2968472
I have a v50020d model.
D4xel said:
Hi all!
I have now TWRP 2.8.6.0 taken from here: http://forum.xda-developers.com/lg-g-pad-83/orig-development/recovery-twrp-2-8-2-0-v500-t2968472
Which are the differences between these recoverys? Which is the better to install?
Thanks!
Click to expand...
Click to collapse
This one is official (without the quotes), doesn't require loki and is adapted to kitkat bootloader backlight. The other one you mention is adapted to jellybean bootloader backlight and requires loki. Just install the one that fits your needs.
cianz94 said:
Hey Guys! How to upgrade from this version? http://forum.xda-developers.com/lg-g-pad-83/orig-development/recovery-twrp-2-8-2-0-v500-t2968472
I have a v50020d model.
Click to expand...
Click to collapse
You have the install instructions on the first post. You can also download the image and flash it with THIS APP.
Hello Chainfire,
I have smartphone LG G3 32GB (D855), as custom rom I just installed the CM13. I tried to flash through recovery TWRP SuperSU-v2.62-3-20151211162651.zip, but when I restarted the device went into boot loop.
Can you tell me if I should try another version, or you have to wait ??
I have the same question
...
Currently the replacement kernel needs to be bumped (searching the beta thread will give you the instructions for this). I may have a different (easier) solution in a few days, though.
Chainfire said:
Currently the replacement kernel needs to be bumped (searching the beta thread will give you the instructions for this). I may have a different (easier) solution in a few days, though.
Click to expand...
Click to collapse
Same problem here with my ONEPLUS One... Updated to the latest CM 13.0 nightly everything was perfect. Installed SuperSU "UPDATE -SuperSU v2.46. System hang at the Android character during logon. I have reloaded the CM13.0 and Gapps, reflashed those two to restore system operation. Found SU v2.62-3 I'll hold off on flashing that SuperSU until a ".. different (easier) solution..." is available. Thanks Chainfire!!!
Happy to wait!
Sent from my LG G3 running cm 12.1
Same problem...
There are news? :crying:
Boot Error
@Chainfire
I've also got an Boot Error after flashing SuperSU 2.65 on my D855 using CandySIX with the 777Kernel for MM. I'l try it now with 2.52 and 2.63-3 maybe it works with them.
SkyDriver11 said:
@Chainfire
I've also got an Boot Error after flashing SuperSU 2.65 on my D855 using CandySIX with the 777Kernel for MM. I'l try it now with 2.52 and 2.63-3 maybe it works with them.
Click to expand...
Click to collapse
well! have you a news about this way?
ps. happy new year to everybody!!
Use SuperSU 2.52
Drago76 said:
well! have you a news about this way?
ps. happy new year to everybody!!
Click to expand...
Click to collapse
Yeah i've got it running with root access and also permissions to /system
Just use the SuperSU 2.52. What i think is that SuperSU 2.52 doesn't patches the boot.img. And thats the point of why 2.52 works.
Our LG G3 hates it when somebody touches the boot.img
SkyDriver11 said:
Yeah i've got it running with root access and also permissions to /system
Just use the SuperSU 2.52. What i think is that SuperSU 2.52 doesn't patches the boot.img. And thats the point of why 2.52 works.
Our LG G3 hates it when somebody touches the boot.img
Click to expand...
Click to collapse
I've tried to flash SuperSU 2.52 but the phone go to loop on the cm animation boot.. :crying:
CM12 & CM13 based roms don't need SuperSU. The su support is built into CyanogenMod. You have to enable developer options and find the included root under developer options.
gimli4711 said:
CM12 & CM13 based roms don't need SuperSU. The su support is built into CyanogenMod. You have to enable developer options and find the included root under developer options.
Click to expand...
Click to collapse
Everyone knows this, thanks..
the problem is that with cm13 root, some apps like Leandroid doesn't work, cause it wants only supersu.
for example, my friend with Nexus 5 cm13, has installed supersu 2.62 and he enjoys Leandroid perfectly.
nothing? :crying:
The way I got SuperSU to work on my phone was to use the SharpeningMod zip, which bumps the sytem img back for you. Just tried it on latest Cyanogenmod nightly and BETA-SuperSU-v2.66.zip.
Download the mod from http://forum.xda-developers.com/lg-g3/orig-development/fix-sharpening-mod-script-1-0-beta-t2957648
Latest version is 3.5
Boot into TWRP perform a back up of your curent system just incase,
flash the latest supersu zip then flash the sharpening modzip, I selected disabled in the list and then let it do its thing.
Rebooted and Cyanogen booted with no loops.
Hope this helps anyone who wants an easy way to install.
great solution!!! it's wonderful!!!
thanks!!
Inviato dal mio LG-D855 utilizzando Tapatalk
superSU 2.66 beta on lg g2 d802...
stoneblade said:
The way I got SuperSU to work on my phone was to use the SharpeningMod zip, which bumps the sytem img back for you. Just tried it on latest Cyanogenmod nightly and BETA-SuperSU-v2.66.zip.
Download the mod from http://forum.xda-developers.com/lg-g3/orig-development/fix-sharpening-mod-script-1-0-beta-t2957648
Latest version is 3.5
Boot into TWRP perform a back up of your curent system just incase,
flash the latest supersu zip then flash the sharpening modzip, I selected disabled in the list and then let it do its thing.
Rebooted and Cyanogen booted with no loops.
Hope this helps anyone who wants an easy way to install.
Click to expand...
Click to collapse
it worked perfectly on lg g2 d802 ...no bootloops !thanks a lot
stoneblade said:
The way I got SuperSU to work on my phone was to use the SharpeningMod zip, which bumps the sytem img back for you. Just tried it on latest Cyanogenmod nightly and BETA-SuperSU-v2.66.zip.
Download the mod from http://forum.xda-developers.com/lg-g3/orig-development/fix-sharpening-mod-script-1-0-beta-t2957648
Latest version is 3.5
Boot into TWRP perform a back up of your curent system just incase,
flash the latest supersu zip then flash the sharpening modzip, I selected disabled in the list and then let it do its thing.
Rebooted and Cyanogen booted with no loops.
Hope this helps anyone who wants an easy way to install.
Click to expand...
Click to collapse
Awesome!!! That was so painless...lol. Thank You! NOTE: I downloaded and installed a nightly update afterwards and ran into binary update problem again. I simply opened SuperSu settings, hit the cleanup option for new install, reboot to recovery, repeated flash of both and all went smooth. I now have SuperSu 2.62 on CM 13 NIGHTLY 01-19-16. Thanks again :cyclops:
jhtrades1 said:
Awesome!!! That was so painless...lol. Thank You! NOTE: I downloaded and installed a nightly update afterwards and ran into binary update problem again. I simply opened SuperSu settings, hit the cleanup option for new install, reboot to recovery, repeated flash of both and all went smooth. I now have SuperSu 2.62 on CM 13 NIGHTLY 01-19-16. Thanks again :cyclops:
Click to expand...
Click to collapse
You also can manually install update from TWRP, after than reinstall xposed Framework (if have it), supersu 2.66 and last reinstall "Sharpening-Mod-3.5".. now reboot.
enjoy!
Inviato dal mio LG-D855 utilizzando Tapatalk
stoneblade said:
The way I got SuperSU to work on my phone was to use the SharpeningMod zip, which bumps the sytem img back for you. Just tried it on latest Cyanogenmod nightly and BETA-SuperSU-v2.66.zip.
Download the mod from http://forum.xda-developers.com/lg-g3/orig-development/fix-sharpening-mod-script-1-0-beta-t2957648
Latest version is 3.5
Boot into TWRP perform a back up of your curent system just incase,
flash the latest supersu zip then flash the sharpening modzip, I selected disabled in the list and then let it do its thing.
Rebooted and Cyanogen booted with no loops.
Hope this helps anyone who wants an easy way to install.
Click to expand...
Click to collapse
It works thanks for this nice solution
stoneblade said:
The way I got SuperSU to work on my phone was to use the SharpeningMod zip, which bumps the sytem img back for you. Just tried it on latest Cyanogenmod nightly and BETA-SuperSU-v2.66.zip.
Download the mod from http://forum.xda-developers.com/lg-g3/orig-development/fix-sharpening-mod-script-1-0-beta-t2957648
Latest version is 3.5
Boot into TWRP perform a back up of your curent system just incase,
flash the latest supersu zip then flash the sharpening modzip, I selected disabled in the list and then let it do its thing.
Rebooted and Cyanogen booted with no loops.
Hope this helps anyone who wants an easy way to install.
Click to expand...
Click to collapse
It works on my LG G3 D855! Thank you! :victory::highfive:
Hi,,
I'm on OOS 4.1.3 running Nougat 7.1.1.I flashed TWRP ,unlocked Bootloader and Flashed TWRP BluSparks version.
I flashed SuperSU thro TWRP only..But Still SUPERSU says I'm not rooted ?
What may be the reason behind??
Regards
Did you flash the latest 2.79 service release 3 SuperSu zip?
Could you suggest any link for that ?? or Will Magisk be good ??
I tried but nothing is fruitful!?!!
vettayyan said:
Could you suggest any link for that ?? or Will Magisk be good ??
I tried but nothing is fruitful!?!!
Click to expand...
Click to collapse
I suggest Magisk. It is more battery-friendly than superSU.
Here's the link:https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Credits: @topjohnwu
Make sure to install Magisk manager also.
Hey,
TWRP 3.1.1 Touch Recovery beta version is released for Xiaomi Mi A1.
Download - Go to downloads tab
Update:
1. Magisk v13.4 is working fine.
Workaround for Xposed:
Xposed is not installing through TWRP and when tried with App, still it's giving errors. So below is the temporary solution till we get a permanent one.
1. Don't flash TWRP. Just boot into it from bootloader by using command - fastboot boot recovery_name.img
2. Flash latest SuperSU zip.
3. Reboot to System.
4. Your phone will be rooted now and install Xposed through app.
Important:
1. Don't flash it, just boot into it.
2. If flashed, re-flash the latest stock boot image.
Instructions:
1. Download the twrp image and twrp installer zip
2. fastboot boot twrp-3.1.1-tissot-beta.img
3. Flash twrp-installer-tissot-3.1.1.zip
4. Reboot to recovery
Flash Magisk v13.4 built for Pixel devices by @Goodwin_c. Available in the downloads tab.
Issues:
1. Flashing SuperSU will break TWRP. SuperSU will work, but TWRP will be gone.
2. Xposed won't flash without modification.
Future update:
1. Make TWRP and SuperSU to co-exist
2. Compatibility with Xposed and Latest Magisk
Disclaimer:
We are not responsible for anything that may happen to your phone as a result of installing custom recoveries, roms and/or kernels. you do so at your own risk and take the responsibility upon yourself.
XDA:DevDB Information
TWRP 3.1.1 for Mi A1, Tool/Utility for the Xiaomi Mi A1
Contributors
mahefooz4u, ravinder0003, Thanks to @Dees_Troy and TWRP Team
Source Code: https://github.com/mahefooz/android_device_xiaomi_tissot
Version Information
Status: Beta
Current Beta Version: 1.0
Beta Release Date: 2017-10-15
Created 2017-10-13
Last Updated 2017-10-16
good work bro waiting for development to start
Great work!
Celebrations
The first step towards the good community has been taken
Great were all waiting for devs to take a look at this devices ! Will it be official when you've fixed the boot issue ? thanks
great work!! thanks guys :good: Will I be able to flash Aroma Uninstaller to debloat?
deepakmohank said:
great work!! thanks guys :good: Will I be able to flash Aroma Uninstaller to debloat?
Click to expand...
Click to collapse
Yes, Aroma installer is working
thank-you. Have you tried the way Pixel devices boot twrp, send twrp zip to internal, then flash?
---------- Post added at 11:28 AM ---------- Previous post was at 11:01 AM ----------
Sorry for asking too many questions, one more to add, which s the partition that mounts when we mount System from twrp? Is it a or b?
Coolio
lakyman said:
Great were all waiting for devs to take a look at this devices ! Will it be official when you've fixed the boot issue ? thanks
Click to expand...
Click to collapse
Don't expect too much from now.
Wait for sometime as this is ported
Great work waiting for stable version... ?
great, thank you very much!!!
deepakmohank said:
Sorry for asking too many questions, one more to add, which s the partition that mounts when we mount System from twrp? Is it a or b?
Click to expand...
Click to collapse
yea good question, I'd like to know about it too..
marhensa said:
great, thank you very much!!!
yea good question, I'd like to know about it too..
Click to expand...
Click to collapse
I could see in Pixel forums about flashing twrp. It has options to back up a, b partitions or even both. Atm no access to computer, will need to check whether urs allow us the same.
Pixel twrp a/b link:
https://forum.xda-developers.com/pixel-xl/development/twrp-alpha1-pixel-devices-t3500312
Surprise!!!
Booted TWRP? But isn't temporary? Sad ?.
But don't worry, I have created a zip, ahh actually ported a zip ?, to flash TWRP permanently ?.
But please do note that I haven't tested this personally yet, as I'm in a bus, traveling right now.
But if guys have guts, then go ahead, & try this, & please report back .
Instructions:
Boot TWRP & just flash this zip from TWRP. That's all...
Link:
https://www.androidfilehost.com/?fid=962021903579484616
Update Test 2: https://www.androidfilehost.com/?fid=962021903579484804
If it works, please don't forget to hit thanks...
deepakmohank said:
I could see in Pixel forums about flashing twrp. It has options to back up a, b partitions or even both. Atm no access to computer, will need to check whether urs allow us the same.
Pixel twrp a/b link:
https://forum.xda-developers.com/pixel-xl/development/twrp-alpha1-pixel-devices-t3500312
Click to expand...
Click to collapse
No support for a/b system. Only active system can be reached
Thanks for great effort by devs
thanks for sharing~
hope it works~
Hi!
I just want to post my experiences so far.
TWRP booted up fine, also backup and MTP works.
I tried flashing magisk v14.2, which's installer told me the B slot is currenly active etc. Flashed without any problem. But rebooting the device I got bootloop.
Restoring the boot image from the backup made the device back to booting state.
ghpranav said:
Booted TWRP? But isn't temporary? Sad ?.
But don't worry, I have created a zip, ahh actually ported a zip ?, to flash TWRP permanently ?.
But please do note that I haven't tested this personally yet, as I'm in a bus, traveling right now.
But if guys have guts, then go ahead, & try this, & please report back .
Instructions:
Boot TWRP & just flash this zip from TWRP. That's all...
If it works, please don't forget to hit thanks...
Click to expand...
Click to collapse
unfortunately it does not work
h**p://kephost-image.tk/files/64k6re0jfsp4zmienhkr.png
TaRsY said:
Hi!
I just want to post my experiences so far.
TWRP booted up fine, also backup and MTP works.
I tried flashing magisk v14.2, which's installer told me the B slot is currenly active etc. Flashed without any problem. But rebooting the device I got bootloop.
Restoring the boot image from the backup made the device back to booting state.
Click to expand...
Click to collapse
Somehow Magisk is not yet working in Mi A1. Either flashed through recovery or other method, getting bootloop and other issues.
TaRsY said:
Hi!
I just want to post my experiences so far.
TWRP booted up fine, also backup and MTP works.
I tried flashing magisk v14.2, which's installer told me the B slot is currenly active etc. Flashed without any problem. But rebooting the device I got bootloop.
Restoring the boot image from the backup made the device back to booting state.
Click to expand...
Click to collapse
If you know then Magisk is not supported officially for A/B partitons devices including Pixel
HIi xda's,
I am in wait for Xiaomi to unchain my BL .....after so...
Can you please link me to a guide, to safely and easily root the mentioned phone ? (redmi 4x 32gb 3gb. with "miui 8.5.2.0 stable" global version ROM).
Is there any issues with MIUI rooted ROM, except to problems with OTA ?
( i just want to root that device safely so i can edit some system files like HOST etc...) at this moment, i want to stay with the original ROM.)
Thank you.
and sorry for my English in advanced.
Hello.
If it can help you.
I 'm running this rom, i've rooted it with magiksk V14.
you must install twrp before root.
Good luck.
I have just got the permission from Xiaomi and unlocked my BL :good:
most of the new guides of how to install twrp and root, are old or in Hindi, can you please link me to an english tutorial that will work on the relevant version ?
Thank you.
Xpresso38 said:
Hello.
If it can help you.
I 'm running this rom, i've rooted it with magiksk V14.
you must install twrp before root.
Good luck.
Click to expand...
Click to collapse
root and twrp
x2, can't delete, sorry.
at this video, he is using magiksk V12, is it ok ?
https://www.youtube.com/watch?v=mWpJtT8ZPoU
inCider said:
I have just got the permission from Xiaomi and unlocked my BL :good:
most of the new guides of how to install twrp and root, are old or in Hindi, can you please link me to an english tutorial that will work on the relevant version ?
Thank you.
Click to expand...
Click to collapse
This tutorial is what I used for getting twrp on my device
https://www.reddit.com/r/Xiaomi/wiki/flashing/flashtwrp
Did you install the official twrp or Cofface ?
i want to stay with the original rom, what is the best method not to lose twrp after rebooting into system, if i install the official twrp ?
thank you.
Mew2ian said:
This tutorial is what I used for getting twrp on my device
https://www.reddit.com/r/Xiaomi/wiki/flashing/flashtwrp
Click to expand...
Click to collapse
inCider said:
Did you install the official twrp or Cofface ?
i want to stay with the original rom, what is the best method not to lose twrp after rebooting into system, if i install the official twrp ?
thank you.
Click to expand...
Click to collapse
I originally went with the cofface version since I also wanted to use the stock rom
Eventually I flashed a few custom roms and decided to update to the official twrp later on
If it helps someone,
i flashed TWRP on redmi 4x with "miui 8.5.2.0 stable" global version ROM following that link : https://twrp.me/xiaomi/xiaomiredmi4x.html.
don't forget to root, right after you flash TWRP
inCider said:
If it helps someone,
i flashed TWRP on redmi 4x with "miui 8.5.2.0 stable" global version ROM following that link : https://twrp.me/xiaomi/xiaomiredmi4x.html.
don't forget to root, right after you flash TWRP
Click to expand...
Click to collapse
Hi,
If i understood correctly;
1) You flashed official TWRP by "fastboot install method", right?
2) Which root method and version did you use? Supersu or magisk or..?
3) You are still on official global stable v8.5.2.0, and official Twrp is still installed (not replaced), right?
And also, i wonder if i can boot to official TWRP recovery temporarily (without installing to the device) and flash Magisk v14.0 afterwards, still on official global stable v8.5.2.0. Will try soon.
[Tools, Tips & Tutorials] How to root Redmi 3S with TWRP temporarily
http://en.miui.com/forum.php?mod=viewthread&tid=430179&highlight=TWRp+Redmi+3s
[2017.10.15] Magisk v14.0 - Root & Universal Systemless Interface [Android 5.0+]
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
yes, you understand correctly the twrp flash method.
i flashed first magisk v12 and then update it to v14. you can flash v14 right away, no probs. now i have changed to 8.5.4.0 global stable(nougat...), and i flashed latest ver of supersu and everything works just great.
Be-Mine said:
Hi,
If i understood correctly;
1) You flashed official TWRP by "fastboot install method", right?
2) Which root method and version did you use? Supersu or magisk or..?
3) You are still on official global stable v8.5.2.0, and official Twrp is still installed (not replaced), right?
And also, i wonder if i can boot to official TWRP recovery temporarily (without installing to the device) and flash Magisk v14.0 afterwards, still on official global stable v8.5.2.0. Will try soon.
[Tools, Tips & Tutorials] How to root Redmi 3S with TWRP temporarily
http://en.miui.com/forum.php?mod=viewthread&tid=430179&highlight=TWRp+Redmi+3s
[2017.10.15] Magisk v14.0 - Root & Universal Systemless Interface [Android 5.0+]
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse