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.
Related
Guys, what would be the latest TWRP for our SM-G920T, and where would I find an Odin-flashable TWRP file? (Somehow I do not trust TWRP Manager with the task of flashing TWRP.)
Just in case it matters, I am currently rooted on the latest DOI1 FW.
Aqua1ung said:
Guys, what would be the latest TWRP for our SM-G920T, and where would I find an Odin-flashable TWRP file? (Somehow I do not trust TWRP Manager with the task of flashing TWRP.)
Just in case it matters, I am currently rooted on the latest DOI1 FW.
Click to expand...
Click to collapse
https://dl.twrp.me/zeroflte/
datdirtyscrew said:
https://dl.twrp.me/zeroflte/
Click to expand...
Click to collapse
Thank you! One of the things that I find irritating about TWRP Manager is that it asks me to confirm/verify the partition where TWRP gets flashed to. Now how can I possibly know if dev/block/platform/15570000.ufs/by-name/RECOVERY is the right place for my device? (Is it?) The second thing that bothers me about TWRP Manager is that it doesn't correctly detect the latest TWRP version, and often it offers to install an older version.
Did twrp-2.8.7.2-zeroflte.img.tar work for you?
After updating to DOI1, I get boot loops after trying to flash TWRP.
I can get into recovery and download mode just fine, but it won't boot to the OS.
RiskPrime said:
Did twrp-2.8.7.2-zeroflte.img.tar work for you? After updating to DOI1, I get boot loops after trying to flash TWRP. I can get into recovery and download mode just fine, but it won't boot to the OS.
Click to expand...
Click to collapse
I bit the bullet eventually (sesing as flashing TWRP via ODIN is a PITA), and flashed TWRP using TWRP Manager. I got an error message upon flashing, though it looks like TWRP flashed just fine. (Go figure!) Anyway, TWRP Manager flashes TWRP 2.8.7.1. It may be that TWRP people didn't consider TWRP 2.8.7.2 safe enough to flash, which is why TWRP Manager doesn't offer the option. That may be your explanation for your troubles.
Oneplus has Screwed a lot of things between 3.5.2 AND 3.2.6..!! I wanted to try newest version of RR released by Blackjubel. But had issues.
Took me 5 minutes figure out things and decided to share it here:
IMPORTANT POST..!!! READ..!!! Credit for firmware files to @davidxantos
For people coming from 3.5.2 or 3.2.6
I am making a very important post. This is meant for all those who are using latest community build of Oneplus 3 and want to try another rom. You will not be able to do so as the twrp you are using will not flash roms completely and the firmware of community build will not let you flash the latest build of twrp. So here is what you need to do.
READ CAREFULLY:
STEP 1 : Grab firmware for 3.2.6 from this link and flash. flashing this will BREAK your fingerprint sensor. WAIT read on.
https://drive.google.com/…/0ByD3oqJ_...0;/view…
STEP 2: Now flash latest twrp 3.0.2.1 . Now you are on the latest twrp.
STEP 3: Now Flash firmware for 3.2.4 from this link. YOU HAVE your finger print sensor back..!
https://drive.google.com/…/0ByD3oqJ_...0;/view…
Now you have the latest twrp again and also can flash anything you want to..!!
Thanks to Oneplus for screwing this..!
Thanks but 3. 2.6 files do not found
No link works!
Just go find another link if these here don't work ...
There is a thread with all official firmwares. Or just use Google.
Sent from my OnePlus 3 using Tapatalk
3.2.4 https://drive.google.com/file/d/0ByD3oqJ_uj0VWjVMbmZoZS1kejg/view
3.2.6 https://drive.google.com/file/d/0ByD3oqJ_uj0VZUFjblBSbEVNRGs/view?usp=sharing
XDA app screwed the links
I tried but i bricked the phone. I cani only restore with the Qualcomm tool but now im stuck on the oxygen 3.1.2 and every time that flash any rom or OTA i brick the phone
gelomc said:
I tried but i bricked the phone. I cani only restore with the Qualcomm tool but now im stuck on the oxygen 3.1.2 and every time that flash any rom or OTA i brick the phone
Click to expand...
Click to collapse
This is strange..
gelomc said:
I tried but i bricked the phone. I cani only restore with the Qualcomm tool but now im stuck on the oxygen 3.1.2 and every time that flash any rom or OTA i brick the phone
Click to expand...
Click to collapse
Could it be that your bootloader is now locked again after using the unbrick tool?
DavidXanatos said:
Could it be that your bootloader is now locked again after using the unbrick tool?
Click to expand...
Click to collapse
No it's unlocked i checked
---------- Post added at 08:39 PM ---------- Previous post was at 08:38 PM ----------
geekynoob said:
This is strange..
Click to expand...
Click to collapse
I know...
I was on 3.2.6 after the OTA. I installed TWRP 3.0.2.1 and re-rooted it. I then took a backup and proceeded to flash RR 5.7.4. Broken fingerprint scanner/home button.
First, does anyone know why this happens? Can it be fixed?
In the meantime, do we need to revert to 3.2.4 to be able to install other roms and not break the the fps/hb?
Can anyone point me to a TWRP flashable version of 3.2.4? <-- Got this, Thanks.
Thanks in advance.
Edit to add below
I did what was detailed in the OP from stock rooted 3.2.6. I flashed the 3.2.6 firmware from TWRP. Rebooted to bootloader. Flashed TWRP 3.0.2.1 via fastboot. Flashed 3.2.4 firmware from TWRP. FPS/HB broken.
Did I miss something?
Reflashed 3.2.6 firmware on a hunch. FPS/HB working again.
My goal is to get to RR 5.7.4 with a working FPS/HB. Any ideas?
Thanks again.
EdHicks said:
I was on 3.2.6 after the OTA. I installed TWRP 3.0.2.1 and re-rooted it. I then took a backup and proceeded to flash RR 5.7.4. Broken fingerprint scanner/home button.
First, does anyone know why this happens? Can it be fixed?
In the meantime, do we need to revert to 3.2.4 to be able to install other roms and not break the the fps/hb?
Can anyone point me to a TWRP flashable version of 3.2.4? <-- Got this, Thanks.
Thanks in advance.
Edit to add below
I did what was detailed in the OP from stock rooted 3.2.6. I flashed the 3.2.6 firmware from TWRP. Rebooted to bootloader. Flashed TWRP 3.0.2.1 via fastboot. Flashed 3.2.4 firmware from TWRP. FPS/HB broken.
Did I miss something?
Reflashed 3.2.6 firmware on a hunch. FPS/HB working again.
My goal is to get to RR 5.7.4 with a working FPS/HB. Any ideas?
Thanks again.
Click to expand...
Click to collapse
It's easy mate..
Flash rr and then flash the 3.2.4 fw.. As u have a good twrp now.. Simple..
geekynoob said:
Oneplus has Screwed a lot of things between 3.5.2 AND 3.2.6..!! I wanted to try newest version of RR released by Blackjubel. But had issues.
Took me 5 minutes figure out things and decided to share it here:
IMPORTANT POST..!!! READ..!!! Credit for firmware files to @davidxantos
For people coming from 3.5.2 or 3.2.6
I am making a very important post. This is meant for all those who are using latest community build of Oneplus 3 and want to try another rom. You will not be able to do so as the twrp you are using will not flash roms completely and the firmware of community build will not let you flash the latest build of twrp. So here is what you need to do.
READ CAREFULLY:
STEP 1 : Grab firmware for 3.2.6 from this link and flash. flashing this will BREAK your fingerprint sensor. WAIT read on.
https://drive.google.com/â?¦/0ByD3oqJ_...0;/viewâ?¦
STEP 2: Now flash latest twrp 3.0.2.1 . Now you are on the latest twrp.
STEP 3: Now Flash firmware for 3.2.4 from this link. YOU HAVE your finger print sensor back..!
https://drive.google.com/â?¦/0ByD3oqJ_...0;/viewâ?¦
Now you have the latest twrp again and also can flash anything you want to..!!
Thanks to Oneplus for screwing this..!
Click to expand...
Click to collapse
In short, we cannot flash official twrp via modified twrp? Can't we just flash 3.2.4 without flashing 3.2.6 firmware?
z31416 said:
In short, we cannot flash official twrp via modified twrp? Can't we just flash 3.2.4 without flashing 3.2.6 firmware?
Click to expand...
Click to collapse
Nice u will get a black screen..
geekynoob said:
Nice u will get a black screen..
Click to expand...
Click to collapse
Thanks for this. I'm about to flash 3.2.4 fw only.
Good thing I saw this thread.
So step by step procedure if we wamt to flash other roms are:
-reboot to recovery (modifoed twrp)
-wipe
-flash 3.2.6 fw via modified twrp
-flash/install official twrp.img
-flash 3.2.4 fw
-flash rom etc
-finally reboot?
i'm using multi rom with FOS 1.5.1 as primary and whenever i flash RR(Flashing 3.2.4 firmware before and after too) and custom rom, FPS/home button not recognised.
what am i doing wrong, although multirom does have individual space why cant the older firmware doesnt work. everything except the home button is working fine.
can anyone explain how it works.
z31416 said:
Thanks for this. I'm about to flash 3.2.4 fw only.
Good thing I saw this thread.
So step by step procedure if we wamt to flash other roms are:
-wipe
-flash 3.2.6 fw via modified twrp
-flash/install official twrp.img
-flash 3.2.4 fw
-flash rom etc
-finally reboot?
Click to expand...
Click to collapse
Modded twrp can be used to flash 3.2.6 or 3.5.2 oos.. Now if u want to go back.. Using the modded twrp flash the 3.2.4 files.. Just reboot recovery now flash non modded twrp as u have 3.2.4 files official twrp will work.. And then flash any rom u want..
green. said:
i'm using multi rom with FOS 1.5.1 as primary and whenever i flash RR(Flashing 3.2.4 firmware before and after too) and custom rom, FPS/home button not recognised.
what am i doing wrong, although multirom does have individual space why cant the older firmware doesnt work. everything except the home button is working fine.
can anyone explain how it works.
Click to expand...
Click to collapse
Multi rom cannot distinguish firmware files.. They are core files.. So fp won't work..
geekynoob said:
Multi rom cannot distinguish firmware files.. They are core files.. So fp won't work..
Click to expand...
Click to collapse
okay, so the developer have to include the firmware in their roms in future build, thats how it works, right?
and while experimenting i flashed OOS 3.2.4 firmware but FPS working fine in FOS 1.5.1. how come it is?
z31416 said:
Thanks for this. I'm about to flash 3.2.4 fw only.
Good thing I saw this thread.
So step by step procedure if we wamt to flash other roms are:
-reboot to recovery (modifoed twrp)
-wipe
-flash 3.2.6 fw via modified twrp
-flash/install official twrp.img
-flash 3.2.4 fw
-flash rom etc
-finally reboot?
Click to expand...
Click to collapse
This will do it. It's how I got going. I went from stock rooted 3.2.6 OOS to RR 5.7.4.
Thanks for putting to words for others.
green. said:
okay, so the developer have to include the firmware in their roms in future build, thats how it works, right?
and while experimenting i flashed OOS 3.2.4 firmware but FPS working fine in FOS 1.5.1. how come it is?
Click to expand...
Click to collapse
I've done a bit of Dev.. But i am not sure about ur statement.. .. And cm based roms don't have fw files.. Feel like a noob lol..
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
Last update: 17.10.2017
Introduction
This is a small flashable script that will add the device signature for z00a, z008 or z00x devices to boot and recovery image. This function is part of my Zenfone 2 toolkit which primary supports stock rom users, but could be useful for any other custom rom user too.
It will fix any kind of missing signatures on boot or recovery that could happen, e. g. if you updated magisk within magisk manager, installed anything that modified boot image with proper device signatures or flashed a new twrp recovery. If you want to patch the recovery image, you should temporary boot a (probably older but) properly signed twrp recovery first of course.
I hope you find it useful. I appreciate any kind of code improvement, just leave me a note.
Usage instructions
[SIZE=+1]Just flash attached zip in custom recovery[/SIZE]
Downloads
Main: Downloads tab (see above)
Thanks to/Credits
Code:
:: > topjohnwu
:: > ggrandou
:: > gerasiov
XDA:DevDB Information
Image signature tool for Zenfone 2, Tool/Utility for the Asus ZenFone 2
Contributors
rummsbumms
Version Information
Status: Beta
Beta Release Date: 2017-10-17
Created 2017-10-18
Last Updated 2018-09-11
Attachments
Most current version:
Great work! This is awesome!
Now I can update OTA LineageOS and keep Magisk without the need of a computer.
rummsbumms said:
Most current version:
Click to expand...
Click to collapse
HI,
I have lineageos 14.1 with twrp 3.03, if i want update to the last twrp 3.2
1) I copy the "twrp zip" and "fix signature zip" to my zenfone2
2) I boot into recovery mode with twrp
3) I choose install and select "the twrp zip", I don't reboot
4) I choose install the "fix signature zip", and I reboot
am i right ?
Big thx for your works, finally i can use lineageos easily
Big thanks for this great tool bro. :good:
drixse said:
HI,
I have lineageos 14.1 with twrp 3.03, if i want update to the last twrp 3.2
1) I copy the "twrp zip" and "fix signature zip" to my zenfone2
2) I boot into recovery mode with twrp
3) I choose install and select "the twrp zip", I don't reboot
4) I choose install the "fix signature zip", and I reboot
am i right ?
Big thx for your works, finally i can use lineageos easily
Click to expand...
Click to collapse
Did you succeed with installing twrp 3.2?
sushuguru said:
Did you succeed with installing twrp 3.2?
Click to expand...
Click to collapse
I don't try yet. I would like to be sure how to proceed first.
drixse said:
I don't try yet. I would like to be sure how to proceed first.
Click to expand...
Click to collapse
Well, i don't think you should, twrp is not released yet for our device.
thanks a lot bro..really very helpful :good:
Very useful，but I still don't know why bootloader already unlocked，it still need the signature to boot
Thanks a lot man! Worked like a charm!
Thanks m8! Works like a charm!
Ok, before I do something wrong.
I have stock Z00A, latest stock, with TWRP, I want to install Magisk latest beta (16.3 I think), I know that flashing magisk will cause bootloop because the Zenfone 2 needs a signed boot, so, flashing magisk and then this script will fix the problem and I'll have a working magisk?
marcossanches said:
Ok, before I do something wrong.
I have stock Z00A, latest stock, with TWRP, I want to install Magisk latest beta (16.3 I think), I know that flashing magisk will cause bootloop because the Zenfone 2 needs a signed boot, so, flashing magisk and then this script will fix the problem and I'll have a working magisk?
Click to expand...
Click to collapse
Yes
Sent from my ASUS_Z00A using XDA Labs
can you add boot signature for z00d?
Then after installing Magisk...
- I have to flash this ZIP to make the system boot?
- Or just leave it?
Pls make signature fix for z00d?
Nothing to do for z00d?
@rummsbumms, have you got something for z00d?
Thanks in advance
towerman said:
@rummsbumms, have you got something for z00d?
Thanks in advance
Click to expand...
Click to collapse
sorry for the confusion, this script doesn't support the z00d as I don't know anything about this device. i've fixed the typo in the first post.
have you already tried the verified boot signer from chainfire? that tool is the best way to sign boot images! my script just adds a signature, which is a signature generated with oem keys but for an older boot image, to the current boot image. so the signature is valid but doesn't fit to the boot image. this way you can boot but get a red exclamation mark on each boot. if you use the verified boot signer, a signature with a custom key will be generated and added to the installed boot image. that signature is valid and fits to the boot image, but isn't created with oem keys from asus. this way you can boot too but get a orange (or yellow? i don't remember) exclamation mark on each boot.
Originally I was using the MiMixTWRPSmarty.img for my recovery. It works but I wanted to try the TWRP 3.1.1 from twrp.me. I flash the img file and then try booting to the recovery but gives a warning about the partition and then whenever i select an option it doesn't respond. Did I miss something?
TWRP has issues if the wrong firmware is installed.
You can either install a matching firmware first or use one of the patched TWRP builds that works on all of them.
I personally use MrRaines patched TWRP build.
Sure, it's older, but it works and does what it has to do.
MrColdbird said:
I personally use MrRaines patched TWRP build.
Sure, it's older, but it works and does what it has to do.
Click to expand...
Click to collapse
+1 Always using that one, works ok. Why would quit using the working one though eh?