There is an official twrp for zl1(x720), some people here say you can use it on zl0(x722) as well. Can someone confirm?
And what about CrisbalGreece and codeworkx versions? How do they differ from the official twrp for x720, any specific x722 modifications? I tried, but couldn't find their git repos for this.
I mean no disrespect to anyone, but I think we should focus more on having source code and easy build instructions. Otherwise we're just tolerating flying binaries and not helping people to develop their knowledge, turning them into mere consumers.
Sorry for bumping but this thread is really important.
Codeworkx:
Can you please tell us why did you make a 3.2.1 x722 version of twrp?(x720 3.1.1 seems to work on x722)
Also can you provide the source code/modifications?
btw I tried it and the touch screen did not work with it.
Everyone:
Is the x720 3.1.1 version ok to use?
Tried booting it and it seemed to work fine, touch screen and everything.
PS.
We can boot twrp without flashing it via "fastboot boot twrp.img" and then backup whatever we want.
So you can use twrp without flashing it and also backup stock recovery if you want to.
Why aren't more people aware of this?
randxor said:
Sorry for bumping but this thread is really important.
PS.
We can boot twrp without flashing it via "fastboot boot twrp.img" and then backup whatever we want.
So you can use twrp without flashing it and also backup stock recovery if you want to.
Why aren't more people aware of this?
Click to expand...
Click to collapse
Hi, I just read your thread.... I explored that path here..... https://forum.xda-developers.com/showpost.php?p=75451375&postcount=81
Lemme see what you think 'bout it.
It's quite easy to do a full backup or a partial one.
You can use adb while in twrp, just do fastboot boot twrp.img. Afterwards while in twrp, do adb pull /dev/recovery_partition.
To find the exact recovery partition you will nees to look around in dev. Ie. ls, df,lsblk.
I can provide a step by step tutorial.
But all of this has nothing to do with why are there many different twrp versions?
Ie. I know codeworkx supports encryption, but what about his older version? And CrisbalGreece?
ctrl-alt-del
Related
Hello,
I've unlocked my bootloader and subsequently had installed TWRP (months ago).
Not long after, I decided to go back to stock for a while, and went back to CM a month ago.
However, I realized back then that I was loading into stock recovery even after taking the steps to install TWRP (http://forum.xda-developers.com/honor-5x/development/root-kiw-l24-usa-kiwi-t3305190)
During these steps, there were no errors (fastboot/adb logs show all things were done successfully).
However, some funky quirk (that I don't remember) got me loaded with TWRP once, which gave me the window to install CM (I remember it involving having to be connected to the PC).
Now I'm trying to install a new CM build, but I can't get it loading TWRP.
I've downloaded the TWRP Manager App, which tells me that I have TWRP 3.0.0.0, but when I reboot to recovery, I am given the stock EMUI recovery.
Does anyone know what is happening in this case? Has anyone experienced a similar issue?
Thank you!
undesputed said:
Hello,
I've unlocked my bootloader and subsequently had installed TWRP (months ago).
Not long after, I decided to go back to stock for a while, and went back to CM a month ago.
However, I realized back then that I was loading into stock recovery even after taking the steps to install TWRP (http://forum.xda-developers.com/honor-5x/development/root-kiw-l24-usa-kiwi-t3305190)
During these steps, there were no errors (fastboot/adb logs show all things were done successfully).
However, some funky quirk (that I don't remember) got me loaded with TWRP once, which gave me the window to install CM (I remember it involving having to be connected to the PC).
Now I'm trying to install a new CM build, but I can't get it loading TWRP.
I've downloaded the TWRP Manager App, which tells me that I have TWRP 3.0.0.0, but when I reboot to recovery, I am given the stock EMUI recovery.
Does anyone know what is happening in this case? Has anyone experienced a similar issue?
Thank you!
Click to expand...
Click to collapse
Reinstallt it try this TWRP http://www.mediafire.com/download/15g5i63gke9ddgp/kiwi_twrp_3-21_recovery.img its version 3.0.2.0 (Most recent)
The most recent is 5-14 (also based on v3.0.2.0 ).
TWRP 5.14
3-21 was built on March 21, and 5-14 on May 14.
mooms said:
The most recent is 5-14 (also based on v3.0.2.0 ).
TWRP 5.14
3-21 was built on March 21, and 5-14 on May 14.
Click to expand...
Click to collapse
Just for the record I'm using a even newer one than the 5-14 posted above
@yuweng posted a version of 3.0.2.0 that will make images of many partitions on the phone that even 5-14 ignores
you can download it here >> https://www.androidfilehost.com/?fid=24588212152305793
please note it was discovered early on that you cannot share the oeminfo partition on the phone, it's locked to your device and can / will brick a phone it's not from. just be careful what you restore with such a powerful version of TWRP.
@undesputed
I have seen this before where flashing TWRP does not seem to stick.
boot to the bootloader and see if frp is unlocked ... if not you need to
boot to your OS and remove your google account from the device
reboot to the bootloader and attempt the flash again. if it still fails to stick you can always just use
fastboot boot twrp.img and it will work just fine... just not installed
Arobase40 said:
Do you mean 3.0.2.0 is newer and supports more partitions than 5-14 ???
Click to expand...
Click to collapse
Their both 3.0.2.0 the one I just posted has more features
Sent from my SM-N920T using Tapatalk
clsA said:
Just for the record I'm using a even newer one than the 5-14 posted above
@yuweng posted a version of 3.0.2.0 that will make images of many partitions on the phone that even 5-14 ignores
you can download it here >> https://www.androidfilehost.com/?fid=24588212152305793
please note it was discovered early on that you cannot share the oeminfo partition on the phone, it's locked to your device and can / will brick a phone it's not from. just be careful what you restore with such a powerful version of TWRP.
@undesputed
I have seen this before where flashing TWRP does not seem to stick.
boot to the bootloader and see if frp is unlocked ... if not you need to
boot to your OS and remove your google account from the device
reboot to the bootloader and attempt the flash again. if it still fails to stick you can always just use
fastboot boot twrp.img and it will work just fine... just not installed
Click to expand...
Click to collapse
@clsA
frp is labeled as "UNLOCK" as oppsed to bootloader labeled as "UNLOCKED".
If it's just about removing my google account, will this be resolved the next time I do a factory reset?
Nevertheless, thank you so much for the command fastboot boot twrp.img, I realized that that was what I had used the last time.
I'm currently able to boot into TWRP this way. Awesome!
@clsA
Thanks for the link & infos.
Can you tell which features are added in this new TWRP ? name of the partitions ?
Thanks.
mooms said:
@clsA
Thanks for the link & infos.
Can you tell which features are added in this new TWRP ? name of the partitions ?
Thanks.
Click to expand...
Click to collapse
it would be much easier to just install it and test it for yourself
I did find a bug it would not backup to my OTG stick
clsA said:
it would be much easier to just install it and test it for yourself
I did find a bug it would not backup to my OTG stick
Click to expand...
Click to collapse
I don't use all the features, so i will maybe miss the changes.
Never used OTG to made a backup (I use ext_SD), I don't know if it works with other builds of TWRP.
mooms said:
I don't use all the features, so i will maybe miss the changes.
Never used OTG to made a backup (I use ext_SD), I don't know if it works with other builds of TWRP.
Click to expand...
Click to collapse
USB-OTG works flawlessly on the 5-14 version I was not able to use it with the newer one @yuweng posted in his guide
the screen shots show all the partitions it's able to work with
Arobase40 said:
I thought 3.0.2.0 was just an interim version between twrp_2-27 and twrp_5-14... ^^
Click to expand...
Click to collapse
your confusing TWRP versions with TWRP release dates
2-27 and 5-14 are release dates where as 3.0.2.0 is the version of TWRP not the date
the first version of TWRP for this device was actually 2.8.7.0 and was released on 2-16-2016
Same issue
Hey so I have the same exact issue umm did you ever resolve this problem becuSe I can't seem to crack it and it's a bit frustrating cuz by no means am I a pro but coming from using the OnePlus one the OnePlus 2 the OnePlus x and the Nexus 6 rooting them and restoring them after many failed attempts resulting in bricking my phone and even eventually unbrick them I do know a thing or two and I am stumped please help you are the only other person in this world other then my self that seems to be having this issue if you don't mind would you be so kind and email gmail me cuz I don't use or check this forum often thanks millerfamily805
clsA said:
Just for the record I'm using a even newer one than the 5-14 posted above
@yuweng posted a version of 3.0.2.0 that will make images of many partitions on the phone that even 5-14 ignores
you can download it here >> https://www.androidfilehost.com/?fid=24588212152305793
please note it was discovered early on that you cannot share the oeminfo partition on the phone, it's locked to your device and can / will brick a phone it's not from. just be careful what you restore with such a powerful version of TWRP.
@undesputed
I have seen this before where flashing TWRP does not seem to stick.
boot to the bootloader and see if frp is unlocked ... if not you need to
boot to your OS and remove your google account from the device
reboot to the bootloader and attempt the flash again. if it still fails to stick you can always just use
fastboot boot twrp.img and it will work just fine... just not installed
Click to expand...
Click to collapse
Can it be used with other honor devices?
Got my answer... Thanks...
Sent from my PLK-L01 using XDA Labs
It depend on the device
Beginner question
I've already rooted the Redmi using a none-TWRP guide.
But for every other guide there is a mention of: making a custom boot.img either by using Android Image Kitchen, flashing something called Universal boot.img, or flashing different versions of TWRP (alka, cofface) that solves the boot.img problem.
However I haven't found an article that explains what boot.img is and why it's a problem for this phone, since flashing my moto only required TWRP + Supersu. Also, it wasn't mentioned at all in the guide I followed.
Sorry if this is pretty obvious, I'm wondering if I missed a pretty big post somewhere.
UniAyeDee said:
Beginner question
I've already rooted the Redmi using a none-TWRP guide.
But for every other guide there is a mention of: making a custom boot.img either by using Android Image Kitchen, flashing something called Universal boot.img, or flashing different versions of TWRP (alka, cofface) that solves the boot.img problem.
However I haven't found an article that explains what boot.img is and why it's a problem for this phone, since flashing my moto only required TWRP + Supersu. Also, it wasn't mentioned at all in the guide I followed.
Sorry if this is pretty obvious, I'm wondering if I missed a pretty big post somewhere.
Click to expand...
Click to collapse
+99 points for asking this question .
As per my knowledge the main problem lies in the boot.img file of MIUI roms because when you are flashing the TWRP you are messing with phone's orignal partition pattern,the boot.img's of MIUI rom checks evrytime if there is any tampering in phone's partition and as you know by flashing TWRP you tampered already , so as result your phone won't boot and gets in bootloop.
So to solve this problem devs developed some methods either you can make a cooked boot.img and flash it evrytime you get a new update to prevent bootloop,
Or you can flash lazyflasher.zip via twrp evrytime after installing new MIUI rom which will patch boot.IMG itself,
Or you can use cofface based recoveries which have lazyflash patch inbuilt and will patch the boot.IMG file evrytime you flash a MIUI rom.
NVDX11 said:
+99 points for asking this question .
As per my knowledge the main problem lies in the boot.img file of MIUI roms because when you are flashing the TWRP you are messing with phone's orignal partition pattern,the boot.img's of MIUI rom checks evrytime if there is any tampering in phone's partition and as you know by flashing TWRP you tampered already , so as result your phone won't boot and gets in bootloop.
So to solve this problem devs developed some methods either you can make a cooked boot.img and flash it evrytime you get a new update to prevent bootloop,
Or you can flash lazyflasher.zip via twrp evrytime after installing new MIUI rom which will patch boot.IMG itself,
Or you can use cofface based recoveries which have lazyflash patch inbuilt and will patch the boot.IMG file evrytime you flash a MIUI rom.
Click to expand...
Click to collapse
Thanks, clears things up. I think I've heard of tampering before but for some reason it wasn't a problem on the moto.
Is there an article or something I can read?
UniAyeDee said:
Thanks, clears things up. I think I've heard of tampering before but for some reason it wasn't a problem on the moto.
Is there an article or something I can read?
Click to expand...
Click to collapse
Yea i know what you are saying,previously i had xperia devices there wasn't a problem too but xiaomi phones have some diff. Methods i think,actually there is not an article about this thing but i am sure i had read that in some developer's post.
UniAyeDee said:
Beginner question
I've already rooted the Redmi using a none-TWRP guide.
But for every other guide there is a mention of: making a custom boot.img either by using Android Image Kitchen, flashing something called Universal boot.img, or flashing different versions of TWRP (alka, cofface) that solves the boot.img problem.
However I haven't found an article that explains what boot.img is and why it's a problem for this phone, since flashing my moto only required TWRP + Supersu. Also, it wasn't mentioned at all in the guide I followed.
Sorry if this is pretty obvious, I'm wondering if I missed a pretty big post somewhere.
Click to expand...
Click to collapse
Update:
The system is known as "dm-verity"
Which enables verfying boot partiton evrytime a system boots if there is any modification.
It is included after 4.4 kitkat for security purpose.
Miui is using Boot.img with enabled dm-verity check.
So after rooting or flashing twrp phone won't boot.
So,what lazyflasher does is disables it.which is inbuilt part of cofface based recoveries.
Read more on dm-verity:
https://source.android.com/security/verifiedboot/
Custom super su from somewhere which roots boot via patch. Flash with twrp
Hello guys, I'm Leonardo and I'm new on XDA. I own this device since July 2016, and throughout 1 year and a half I tried a lot of roms. I've seen a few roms based on Oreo and I'd like to try them, but every time i flash one of those roms, the device bootloops. I think the cause might be the Cofface TWRP I have installed on the but I haven't found a guide on how to switch from a recovery to another. Can you please link me a guide or, if someone already switched recovery, tell me the way to do that?
Thanks in advance
Leo
Just select install from twrp menu select image and choose the file of recovery then select the recovery partition
leoalbore said:
Hello guys, I'm Leonardo and I'm new on XDA. I own this device since July 2016, and throughout 1 year and a half I tried a lot of roms. I've seen a few roms based on Oreo and I'd like to try them, but every time i flash one of those roms, the device bootloops. I think the cause might be the Cofface TWRP I have installed on the but I haven't found a guide on how to switch from a recovery to another. Can you please link me a guide or, if someone already switched recovery, tell me the way to do that?
Thanks in advance
Leo
Click to expand...
Click to collapse
download Redworlf recovery (check if you have 2GB or 3GB variant) Select install from twrp menu select image and choose the file of recovery, then select the recovery partition and swipe bar.
I don't suggest using Red Wolf recovery since it is closed source and the code hasn't been properly audited, the same goes for ZCX, comes from some unknown china user (but so far it has been safe), it's up to you if you want to risk your phone and/or data, you have to ask why they are hiding the source code and for what reason, it could just be they are bad coders and don't want people to see messy code....who knows.
anyways I suggest using the official twrp, you might have to use the lazyflasher thing but at least you know you are getting a safe recovery and its great our device is getting official twrps we really don't need to use hacked ones.
if you want to use the OTA update feature I suggest just sticking with ZCX, or if you need access to additional partitions.
I don't understand the need to build a custom recovery? Can't someone just flash using just fastboot?
Does anyone know any instructions on how to flash A/B devices with custom rom using fastboot? Also I see now there is a fastbootd?
nexuspb said:
I don't understand the need to build a custom recovery? Can't someone just flash using just fastboot?
Does anyone know any instructions on how to flash A/B devices with custom rom using fastboot? Also I see now there is a fastbootd?
Click to expand...
Click to collapse
Unless ive been living under a rock or something has radically changed, fastboot will only ever flash ROM's in img format, not ROM's in zip format like most custom ROM's....that said custom GSI's (based off Google GSI's) come in .img format (sometimes zipped first)
Your best bet is to find your devices home section on XDA and work from there....as usually if youve thought it, someone else has before you, and so checking to see if its already been done before in the much more focused section where your device is discussed is a faster resolve than post in a general Q&A thread...
Official TWRP is now available: https://twrp.me/asus/zenfone9.html
IMPORTANT NOTES:
CleanSlate custom kernel is not currently compatible with TWRP for this device (Kirisakura is compatible as of v2.0.6).
This device has a recovery partition (2, in fact), and fastboot boot is disabled in the bootloader. Flashing TWRP to the recovery partition is the only way to use it.
If you attempt to fastboot boot the TWRP image, your device may end up unbootable. YOU'VE BEEN WARNED.
Any questions, comments, feedback, or concerns should always be accompanied by logs (recovery log, logcat, dmesg)
TWRP Trees
Common: https://github.com/TeamWin/android_device_asus_sm84xx-common
Device: https://github.com/TeamWin/android_device_asus_AI2202
Thanks for your work!
Installed as on twrp.me described wont boot (https://twrp.me/asus/zenfone9.html)
Had to flash stock recovery again.
Rooted device on 32.2050.2050.29 with kirisakura-kernel.
Any idea what im doing wrong?
Hermann2306 said:
Thanks for your work!
Installed as on twrp.me described wont boot (https://twrp.me/asus/zenfone9.html)
Had to flash stock recovery again.
Rooted device on 32.2050.2050.29 with kirisakura-kernel.
Any idea what im doing wrong?
Click to expand...
Click to collapse
If you're not on stock kernel, then that's probably the problem. I know the custom kernel situation is different on this device than previous ones. This may be something that @Freak07 & I have to look into together. In the meantime, can you restore back to stock kernel and confirm that TWRP works, and then install Kirisakura and see if everything still works?
Restored stock kernel with kernelflasher but now it wont boot. Tried to change the slot to a but isnt allowed in fastboot.
Have to find out now how to change the slot or install stock kernel via fastboot...
Hermann2306 said:
Restored stock kernel with kernelflasher but now it wont boot. Tried to change the slot to a but isnt allowed in fastboot.
Have to find out now how to change the slot or install stock kernel via fastboot...
Click to expand...
Click to collapse
It doesn't sound like you followed the procedure in the Kirisakura thread FAQ to fully return to stock. Can you confirm exactly what you did?
just restored the backup i made with kernelflasher befor i installed the custom kernel and rebooted.
Hermann2306 said:
just restored the backup i made with kernelflasher befor i installed the custom kernel and rebooted.
Click to expand...
Click to collapse
I'm not familiar with that app, sorry. I just know that's not the process mentioned in his thread, so until you do that, I can't really confirm what the problem could be.
ok, im back on stock. flashing following files helped. i will test twrp again later and report. thanks for your replies.
fastboot flash boot boot.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash dtbo dtbo.img
fastboot reboot fastboot
fastboot flash vendor_dlkm vendor_dlkm.img
fastboot reboot
With stock kernel twrp works. Just installed as described on twrp.me. The official twrp app from playstore crashes after root allowing.
For everyone who comes from custom kernel flash the files from your actual firmware (payload-dumper) as described in the post above.
Are you working on custom kernel support?
Hermann2306 said:
With stock kernel twrp works. Just installed as described on twrp.me. The official twrp app from playstore crashes after root allowing.
For everyone who comes from custom kernel flash the files from your actual firmware (payload-dumper) as described in the post above.
Are you working on custom kernel support?
Click to expand...
Click to collapse
From stock, I just flashed the Kirisakura zip in TWRP and my device booted up fine.
EDIT: While the above is true, TWRP no longer functions after installing the kernel, and the device won't reboot again after installing it. So something is definitely wrong somewhere.
For now, I can only suggest not using it with a custom kernel until we figure this out.
Ok, flashing with EXKernelManager works also.
update
I can do reboots but twrp doesnt work anymore
Hermann2306 said:
Ok, flashing with EXKernelManager works also.
update
I can do reboots but twrp doesnt work anymore
Click to expand...
Click to collapse
Yes, there seems to be an issue in the kernel that's preventing TWRP from working. I'm not sure what the issue is, unfortunately.
So every time I restore a back up, do I have to delete all lock screen requirements ?
If that's the case, I would have to redo my fingerprints every time
c19932 said:
So every time I restore a back up, do I have to delete all lock screen requirements ?
If that's the case, I would have to redo my fingerprints every time
Click to expand...
Click to collapse
Yes.
Quick PSA for anyone using this TWRP that also wants to use a custom kernel:
As of Kirisakura 2.0.6, the custom kernel and TWRP can now co-exist. This is due to the changes that allowed a monolithic kernel build. Presently, CleanSlate has not adopted those changes, but if/when it does, I will remove that disclaimer from the OP.
Thanks to @arter97, @Freak07, & @tbalden for supporting this device!
Is the twrp compatible with android 13?
NisseGurra said:
Is the twrp compatible with android 13?
Click to expand...
Click to collapse
There's a really easy way to find out...
Captain_Throwback said:
There's a really easy way to find out...
Click to expand...
Click to collapse
I getting decrypt errors that why the q
NisseGurra said:
I getting decrypt errors that why the q
Click to expand...
Click to collapse
Then you should post some logs
Will do