guys, do you know when there will be TWRP for Mi 11 Lite 5G? Or maybe there's someone here who will do it?
I've been trying to build one but I failed. I need a device tree ..so I was trying to create one from the boot.img using an automated script ..
The script fails because AIK image kitchen fails to extract the boot.img because it uses header V3 which is too new for tool
The maintainers of the tool tried it using a newer version of AIK & it extracted but it didn't create the tree successfully ..
If it had I could have used that tree to build a recovery . I'm not a pro developer but wanted to try ...
Other than that I haven't seen anything around indicating that any specific experienced dev or other is busy or intending to build one.
Having said that asking for a date is pretty cocky .. It's not a new car that you can order and buy with release dates ....
You can still flash EU rom & root with Magisk for now without a recovery
KevMetal said:
I've been trying to build one but I failed. I need a device tree ..so I was trying to create one from the boot.img using an automated script ..
The script fails because AIK image kitchen fails to extract the boot.img because it uses header V3 which is too new for tool
The maintainers of the tool tried it using a newer version of AIK & it extracted but it didn't create the tree successfully ..
If it had I could have used that tree to build a recovery . I'm not a pro developer but wanted to try ...
Other than that I haven't seen anything around indicating that any specific experienced dev or other is busy or intending to build one.
Click to expand...
Click to collapse
So have u found out anything to create renoir tree?
If not, I guess u may check out the alioth (Redmi K40/POCO F3) tree (as what make that tree), the alioth also use the header V3 (which is same as Pixel 5 & this renoir)
DumbHokage said:
So have u found out anything to create renoir tree?
If not, I guess u may check out the alioth (Redmi K40/POCO F3) tree (as what make that tree), the alioth also use the header V3 (which is same as Pixel 5 & this renoir)
Click to expand...
Click to collapse
I haven't found anything yet.. I'm not experiences enough to make a tree myself and I only know one tool to make it ..the maintainers of that tool didn't say anything to me about updating tool to allow extraction and creation of the boot.img ..
the only possibility is to wait for more pro dev or another phone with same chipset and screen to come out and for another dev to build one twrp for that device
Here you can see the conversation .. Other people are trying to get tree for Poco F3 and Pixel 5 also ...
KevMetal said:
I've been trying to build one but I failed. I need a device tree ..so I was trying to create one from the boot.img using an automated script ..
The script fails because AIK image kitchen fails to extract the boot.img because it uses header V3 which is too new for tool
The maintainers of the tool tried it using a newer version of AIK & it extracted but it didn't create the tree successfully ..
If it had I could have used that tree to build a recovery . I'm not a pro developer but wanted to try ...
Other than that I haven't seen anything around indicating that any specific experienced dev or other is busy or intending to build one.
Click to expand...
Click to collapse
Thank for you hard work, hope the tree could be build ASAP
No news?
.... are good news?
TWRP makes life easier.
Thanks in advance.
Just fund a first twrp by Nebrassy:
not found | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Peterpaulmarie said:
Just fund a first twrp by Nebrassy:
not found | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Click to expand...
Click to collapse
You have to specify that it's for 4G version....
rayman95 said:
You have to specify that it's for 4G version....
Click to expand...
Click to collapse
No, I don't think so. Nickname for 4G is courbet and 5G is renoir.
But I haven't had time to try it....
Maybe tomorrow...
Update: works, but touch not working (see above) thanks to devs
rayman95 said:
You have to specify that it's for 4G version....
Click to expand...
Click to collapse
It is for 5G (renoir) please stop saying in threads it's for 4G version.
dannejanne said:
It is for 5G (renoir) please stop saying in threads it's for 4G version.
Click to expand...
Click to collapse
Have you tried it?
Peterpaulmarie said:
Just fund a first twrp by Nebrassy:
Click to expand...
Click to collapse
Is there some more information about this? Has anybody tried this? Does this TWRP support Nandroid Backup?
kestrelv2 said:
Have you tried it?
Click to expand...
Click to collapse
No not yet. Probably won't until I get a reason for it. When xiaomi eu begins with TWRP instead of fastboot ROM's.
Rainman67 said:
Is there some more information about this? Has anybody tried this? Does this TWRP support Nandroid Backup?
Click to expand...
Click to collapse
Touchscreen is not working after reboot recovery, you have to re flash it again via fastboot every time.
I tried flash magisk 23 zip on PE Plus but while didn't get any error on twrp, magisk was not installed at all.
I believe it's rom fault and not twrp I guess.
Didn't tried any other option twrp offer.
I'm care more of getting root on pe plus or see more custom rom development rather than twrp.
It's welcome of course but not mandatory for me, after all on OnePlus 8 Pro don't have twrp for Android 11 but we have rich custom roms and development and can live without twrp.
I tested on Xiaomi EU 21.7.7
Touchscreen not working, Backup not tested
Flashing Magisk works, Safetynet passed
Thanks to devs
On newer PE build no need twrp to installed magisk, just flashing the patched boot IMG via fastboot mode and all ok.
paatha13 said:
On newer PE build no need twrp to installed magisk, just flashing the patched boot IMG via fastboot mode and all ok.
Click to expand...
Click to collapse
Some people on telegram have issue, what exactly yo do to flash it???
Thanks
C:\tools>fastboot flash recovery C:\tools\twrp-3.5.2_10-0-renoir-Nebrassy.img
Sending 'recovery' (196608 KB) OKAY [ 4.671s]
Writing 'recovery' FAILED (remote: '(recovery_b) No such partition')
fastboot: error: Command failed
Related
At the moment we have rather dfficult situation because custom ROMs based on AOSP (such as my AD which is not yet public) require previous OOS LP firmware, while OOS 3.0 includes new MM firmware which breaks both older recoveries and custom ROMs.
As I need to switch between OOS 3.0 and my AD quite frequently, I created two helpful flashable zips so I can do that easily, and because it's useful for me, perhaps it'll be useful for you too.
Download: MM | LP
Instructions:
- Download the firmware you want (or both, if you want easy switching)
- Unpack downloaded zip, you'll find firmware-update.zip and recovery.img inside
- Put both of those files on your phone, in appropriately named directory such as "firmware-LP" or "firmware-MM"
- When you will need to do a switch, simply firstly flash firmware-update.zip, then flash recovery.img as recovery image via "flash image" option in TWRP
- Reboot to load new firmware
That's it, this way you firstly flash chosen firmware version, and then TWRP recovery that works with it.
So if you have two TWRP backups - one of OOS 3.0 and one of CM13.0, make sure that you have proper firmware (and recovery) after restoring backup - LP for CM13.0, and MM for OOS 3.0.
Situation should soon improve (when OnePlus pushes kernel sources, and MM-based ROMs will rebase), but until then it's wise to keep both of those firmware + recovery combos on your sd card, so you can do a switch without any problem on as-needed basis.
Hope it helps. Try to be careful with those, if you mix up wrong recovery with wrong firmware you'll need to flash proper recovery.img variant via fastboot. You can't hard brick anything by using those files, in worst case soft-brick if both your recovery and your ROM will be for wrong firmware you have.
Have fun.
We are waiting for AD release. At least a beta?
mido25 said:
We are waiting for AD release. At least a beta?
Click to expand...
Click to collapse
Don't you know how to use the JustArchi's github?
Wow, really helps. I wish I have my OnePlus2 now.
Guihardrock said:
Don't you know how to use the JustArchi's github?
Click to expand...
Click to collapse
No sir. I do not know. Once I tried downloading a build from the below location and tried flashing it but recovery didn't allow me to flash it.
https://t.co/96EZIl6dJJ
I don't know why is it failed. My knowledge about github and making builds are limited.
mido25 said:
No sir. I do not know. Once I tried downloading a build from the below location and tried flashing it but recovery didn't allow me to flash it.
https://t.co/96EZIl6dJJ
I don't know why is it failed. My knowledge about github and making builds are limited.
Click to expand...
Click to collapse
ok so i will explain you when you download that file you have to unzip it and then you will have a folder with another folder (if you choosed unzip in archidreoid etc.zip so inside that folder you will have the necesary files (view the attached screenshot) you will have to pack them in a zip file
hope it helps but try to download the latest file to do that cause last time i tried the oneplus2 archidroid there were things that dint work such as ad filter
Guihardrock said:
ok so i will explain you when you download that file you have to unzip it and then you will have a folder with another folder (if you choosed unzip in archidreoid etc.zip so inside that folder you will have the necesary files (view the attached screenshot) you will have to pack them in a zip file
hope it helps but try to download the latest file to do that cause last time i tried the oneplus2 archidroid there were things that dint work such as ad filter
Click to expand...
Click to collapse
Thanks a lot for your guidance. Appreciate if you can give a link to his latest build.
Sent from my ONE A2003 using Tapatalk
mido25 said:
Thanks a lot for your guidance. Appreciate if you can give a link to his latest build.
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
Here you go https://github.com/ArchiDroid/ArchiDroid/archive/oneplus2-cm-experimental.zip but its experimental so you can expect bugs
Lost recovery
Hi sir,
I have flashed MM using the TWRP recovery as normal. But now I have lost my recovery. I am not able to boot into any recovery. Pls help.
JustArchi said:
At the moment we have rather dfficult situation because custom ROMs based on AOSP (such as my AD which is not yet public) require previous OOS LP firmware, while OOS 3.0 includes new MM firmware which breaks both older recoveries and custom ROMs.
As I need to switch between OOS 3.0 and my AD quite frequently, I created two helpful flashable zips so I can do that easily, and because it's useful for me, perhaps it'll be useful for you too.
Download: MM | LP
Instructions:
- Download the firmware you want (or both, if you want easy switching)
- Unpack downloaded zip, you'll find firmware-update.zip and recovery.img inside
- Put both of those files on your phone, in appropriately named directory such as "firmware-LP" or "firmware-MM"
- When you will need to do a switch, simply firstly flash firmware-update.zip, then flash recovery.img as recovery image via "flash image" option in TWRP
- Reboot to load new firmware
That's it, this way you firstly flash chosen firmware version, and then TWRP recovery that works with it.
So if you have two TWRP backups - one of OOS 3.0 and one of CM13.0, make sure that you have proper firmware (and recovery) after restoring backup - LP for CM13.0, and MM for OOS 3.0.
Situation should soon improve (when OnePlus pushes kernel sources, and MM-based ROMs will rebase), but until then it's wise to keep both of those firmware + recovery combos on your sd card, so you can do a switch without any problem on as-needed basis.
Hope it helps. Try to be careful with those, if you mix up wrong recovery with wrong firmware you'll need to flash proper recovery.img variant via fastboot. You can't hard brick anything by using those files, in worst case soft-brick if both your recovery and your ROM will be for wrong firmware you have.
Have fun.
Click to expand...
Click to collapse
Your ll recovery is in chinese. How to change it?
EDIT: Forget it. I found where to change the language! Thanks.
eswa1068 said:
Hi sir,
I have flashed MM using the TWRP recovery as normal. But now I have lost my recovery. I am not able to boot into any recovery. Pls help.
Click to expand...
Click to collapse
Use fastboot to flash the recovery
Guihardrock said:
Here you go https://github.com/ArchiDroid/ArchiDroid/archive/oneplus2-cm-experimental.zip but its experimental so you can expect bugs
Click to expand...
Click to collapse
Thank you Sir
Tierri said:
Your ll recovery is in chinese. How to change it?
EDIT: Forget it. I found where to change the language! Thanks.
Click to expand...
Click to collapse
Hi,
Can u let me know where to change the language of twrp ?
Sent from my ONE A2003 using Tapatalk
amit_sen said:
Hi,
Can u let me know where to change the language of twrp ?
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
Yes. See the images to help you.
Guihardrock said:
Here you go https://github.com/ArchiDroid/ArchiDroid/archive/oneplus2-cm-experimental.zip but its experimental so you can expect bugs
Click to expand...
Click to collapse
It's around 900 mb zip..?
And did anyone try that build..?
Mohit31 said:
It's around 900 mb zip..?
And did anyone try that build..?
Click to expand...
Click to collapse
Its because of the aroma you can choose the gapps of your choice...
Guihardrock said:
Its because of the aroma you can choose the gapps of your choice...
Click to expand...
Click to collapse
OK... Thanks
Btw Are you on this build..
A quick feedback on the ROM would be great
This thing should be STICKY
Finally was able to install CM13 properly using this recovery without Google Services crashing.
Mohit31 said:
OK... Thanks
Btw Are you on this build..
A quick feedback on the ROM would be great
Click to expand...
Click to collapse
Now i am in oos3 but when justarchi release archidroid i wont use any other rom, i had so great experience with this on my s3
Edit: i am gonna try it :3 yo made me do it
Mohit31 said:
OK... Thanks
Btw Are you on this build..
A quick feedback on the ROM would be great
Click to expand...
Click to collapse
rom is smooth as h*ll and battery is better than in normal cm13 but as i said the backed dont work yet :3 and aroma is not fully functional with the bootanimation and root (but the rom has the cm superuser)
I patched the kernel for 7.1.1 on Qualcomm Moto E4 Plus. This is useful to get Magisk fully working with modules and settings that can be saved.
I compiled the fix from the released kernel source: MMI-NPR26.58-25
Here are the unsigned boot.img and zImage, use whichever one suits your fancy to patch the kernel.
Download boot.img
Download zImage
Edit: I've uploaded a build for the regular Qualcomm Moto E4 here.
Installation:
You should backup your Boot in TWRP before installing, that way you can restore if something goes wrong.
If you have Magisk installed, you'll want to patch the boot.img using Magisk Manager. Just tap install, and patch boot rom image. Then copy the patched file back to your computer to flash it.
Easiest way is to flash the boot.img while in fastboot:
Code:
>fastboot flash boot /path/to/downloaded/boot.img
Did not work, phone would not boot after flash, had to restore stock kernel.
TheJAYpoop said:
Did not work, phone would not boot after flash, had to restore stock kernel.
Click to expand...
Click to collapse
Hmm, having tried it myself, I see that without patching the image with magisk from inside magisk manager, it seems the rebuilt boot image does not work. But it does work after it's been patched in magisk, so you can try that.
Here's a link that's already been patched with Magisk 14.6 beta: https://drive.google.com/open?id=13vaUgq22fNnVnWqq5ai9kGC1KsO3ZEmJ
SeanStar said:
Hmm, having tried it myself, I see that without patching the image with magisk from inside magisk manager, it seems the rebuilt boot image does not work. But it does work after it's been patched in magisk, so you can try that.
Here's a link that's already been patched with Magisk 14.6 beta: https://drive.google.com/open?id=13vaUgq22fNnVnWqq5ai9kGC1KsO3ZEmJ
Click to expand...
Click to collapse
That worked perfectly, awesome!
TheJAYpoop said:
That worked perfectly, awesome!
Click to expand...
Click to collapse
Merry Christmas! Enjoy the full Magisk experience, it was really bothering me when I got this phone about half a week ago.
Nice, I was planning on doing this after Christmas. Saved me the trouble. Merry Christmas to you too! It worked fine just flashing the patched img with TWRP. Want to save me the trouble of doing one for the regular E⁴ also?
GetOffMyLawn&!+¢#{$ said:
Nice, I was planning on doing this after Christmas. Saved me the trouble. Merry Christmas to you too! It worked fine just flashing the patched img with TWRP. Want to save me the trouble of doing one for the regular E⁴ also?
Click to expand...
Click to collapse
If you point me to the kernel source you specifically want patched, I can make it. You'll have to test it for me though, as I don't own the regular E^4.
SeanStar said:
If you point me to the kernel source you specifically want patched, I can make it. You'll have to test it for me though, as I don't own the regular E^4.
Click to expand...
Click to collapse
That would be great. I'll pm you a link since I can't post links yet. I've been spending all my spare time trying to get data working properly on both devices. I have no problem testing it.
Sent from my Moto E (4) Plus using XDA Labs
Qualcomm Moto E4 f2fs fix for perry 7.1.1 (Built and patched from NCQ26.69-48 source) kernel boot image for anyone that wants it is linked below. Thanks to GetOffMyLawn&!+¢#{$ for testing. See the OP for installation instructions, and please remember to make backups of your stock Boot.
Download:
unsigned boot.img
zImage
SeanStar said:
Qualcomm Moto E4 f2fs fix for perry 7.1.1 (Built and patched from NCQ26.69-48 source) kernel boot image for anyone that wants it is linked below. Thanks to GetOffMyLawn&!+¢#{$ for testing. See the OP for installation instructions, and please remember to make backups of your stock Boot.
Download:
unsigned boot.img
zImage
Click to expand...
Click to collapse
Thank you very much for taking the time to do this! Especially today. Just to point out how I installed the kernel, I simply flashed it as an img with TWRP, flashed the no dmverity/forceencrypt zip, then flashed Magisk V15.0 that was just released. It stayed on the n/a screen a minute then bootlooped a couple times, but it eventually booted just fine, so be patient with it. I had the latest Boost firmware installed and Magisk v14.6 at the time. Enjoy!
Sent from my Moto E (4) Plus using XDA Labs
Thanks @SeanStar for the regular e4 boot.img. you rock bro. Works great. Tested, successful
@SeanStar would you mind uploading the source to your kernel, like maybe on a GitHub repo or something? I'm working with a friend who has the owens and I'm trying to see if we can get a more functioning Lineage 14.1 on here
jasonmerc said:
@SeanStar would you mind uploading the source to your kernel, like maybe on a GitHub repo or something? I'm working with a friend who has the owens and I'm trying to see if we can get a more functioning Lineage 14.1 on here
Click to expand...
Click to collapse
Though the kernel I am currently working on is slightly modified more than what is provided here, the OP only has the fix for the f2fs loopback issue, as described here: https://forum.xda-developers.com/showpost.php?p=70492947&postcount=8793
You can download the stock kernel build source from Motorola's own repository here: https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-NPR26.58-25
Also, I admit that I'm currently in the process of porting Lineage 14.1 to this phone, but it may take more time than I had originally planned for. It's not a priority for me at the moment, especially considering how much I like the stock rom.
SeanStar said:
Though the kernel I am currently working on is slightly modified more than what is provided here, the OP only has the fix for the f2fs loopback issue, as described here: https://forum.xda-developers.com/showpost.php?p=70492947&postcount=8793
You can download the stock kernel build source from Motorola's own repository here: https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-NPR26.58-25
Also, I admit that I'm currently in the process of porting Lineage 14.1 to this phone, but it may take more time than I had originally planned for. It's not a priority for me at the moment, especially considering how much I like the stock rom.
Click to expand...
Click to collapse
Well dang, I'm working on porting lineage 14.1 to this thing too. Maybe we should join forces.
And moto's source is in a zip file, I was hoping I could get one that was unzipped and in a github repo already, for easy syncing when trying to build Lineage 14.1
Thank you for your work. I agree that stock isn't too bad with root magisk and Xposed working fine. But lineage is pretty tasty! I will shoot you both a PM if I can assist in any way
@SeanStar check out these screenies everyone:
Sent from my Moto E (4) Plus using XDA Labs
GetOffMyLawn&!+¢#{$ said:
@SeanStar check out these screenies everyone:
Click to expand...
Click to collapse
I'm not sure if they're still doing updates for this phone from what I've heard, but if they do this would be very nice.
SeanStar said:
I'm not sure if they're still doing updates for this phone from what I've heard, but if they do this would be very nice.
Click to expand...
Click to collapse
That sucks to hear, but although I do actually like stock on this device, that's why I build custom ROMs. Budget Motorola's never get updated more then a few times. Hopefully it will get added for future devices and ones that don't get abandoned at least.
Sent from my Moto E (4) Plus using XDA Labs
SeanStar said:
Qualcomm Moto E4 f2fs fix for perry 7.1.1 (Built and patched from NCQ26.69-48 source) kernel boot image for anyone that wants it is linked below. Thanks to GetOffMyLawn&!+¢#{$ for testing. See the OP for installation instructions, and please remember to make backups of your stock Boot.
Download:
unsigned boot.img
zImage
Click to expand...
Click to collapse
Hey @SeanStar would it be possible for you to do this on the latest update for the kernel on the E4 Perry please?? The reason being is this one can't be used on the latest update of the firmware, it fails to boot all the way up.
EDIT: The latest is NCQ26.69-56
PimpMy5Ton said:
Hey @SeanStar would it be possible for you to do this on the latest update for the kernel on the E4 Perry please?? The reason being is this one can't be used on the latest update of the firmware, it fails to boot all the way up.
EDIT: The latest is NCQ26.69-56
Click to expand...
Click to collapse
Considering there is no kernel source for NCQ26.69-56 on MotorolaMobilityLLC github, you're SOL, there's no easy way to patch it without the source. Sorry bud.
EDIT: I wouldn't try to downgrade either, I'm sure they updated the baseband. You'll probably knockout your service if you even try.
Duplicate of post on the honor 9 forums, because no one looks on there for stuff anymore
lets make this very clear:
I HAVE NOT DEVELOPED THIS, IT WAS LINKED IN ANOTHER FORUM BY ANOTHER MEMBER WHO ALSO DID NOT DEVELOP IT
this is actually developed by a member over at the Chinese website '7to' http://www.7to.cn, so its a recovery based on TWRP 3.2.1 but seems to have its own UI and feature set.
WORKING
Code:
[COLOR="Black"][LIST]
[*]Boots to TWRP!
[*]Can flash images to system (MUST BE ON SD CARD!!!!)
[*]ADB
[*]Mount system R/W
[/LIST][/COLOR]
NOT WORKING
Code:
[COLOR="Black"][LIST]
[*]Decryption
[*]Data backup
[*]Flash from internal storage (since it cant be decrypted)
[/LIST][/COLOR]
I am not responsible if you brick your device, flash with caution and ONLY on an 8.1 GSI where your current TWRP doesn't work.
This does not do anything to capacitive keys, if they work before flashing they will work after flashing
INSTALLATION
'fastboot flash recovery_ramdisk recovery.img
DOWNLOAD
https://drive.google.com/file/d/1RgerdkXY-B-8XV5buloeCyKYrA2B3Bvf/view?usp=sharing
Credit to whoever the creator of this is!
ambitiousButRubbish said:
Duplicate of post on the honor 9 forums, because no one looks on there for stuff anymore
lets make this very clear:
I HAVE NOT DEVELOPED THIS, IT WAS LINKED IN ANOTHER FORUM BY ANOTHER MEMBER WHO ALSO DID NOT DEVELOP IT
this is actually developed by a member over at the Chinese website '7to' http://www.7to.cn, so its a recovery based on TWRP 3.2.1 but seems to have its own UI and feature set.
WORKING
Code:
[COLOR="Black"][LIST]
[*]Boots to TWRP!
[*]Can flash images to system (MUST BE ON SD CARD!!!!)
[*]ADB
[*]Mount system R/W
[/LIST][/COLOR]
NOT WORKING
Code:
[COLOR="Black"][LIST]
[*]Decryption
[*]Data backup
[*]Flash from internal storage (since it cant be decrypted)
[/LIST][/COLOR]
I am not responsible if you brick your device, flash with caution and ONLY on an 8.1 GSI where your current TWRP doesn't work.
This does not do anything to capacitive keys, if they work before flashing they will work after flashing
INSTALLATION
'fastboot flash recovery_ramdisk recovery.img
DOWNLOAD
https://drive.google.com/file/d/1RgerdkXY-B-8XV5buloeCyKYrA2B3Bvf/view?usp=sharing
Credit to whoever the creator of this is!
Click to expand...
Click to collapse
YunLin85 developed i think
YazumiWuHung said:
YunLin85 developed i think
Click to expand...
Click to collapse
And do you know if he developed/published newer version?
Thanks.
very nice, i'll take a look into this
thanks!
I just want to use the magisk,and then i will try it on treble-rom.
couple of bugs
1. screen brightness is somehow set to 182%
2. cannot turn the screen off, it just sets it to a lock screen where it makes it slide to unlock, but the screen is not off, still on
3. its in chinese, i got to change it to engish, but some users arent smart enough to do that
crayonicle said:
2 bugs
1. screen brightness is somehow set to 182%
2. cannot turn the screen off, it just sets it to a lock screen where it makes it slide to unlock, but the screen is not off, still on
3. its in chinese, i got to change it to engish, but some users arent smart enough to do that
Click to expand...
Click to collapse
I have this installed on my honor 9, and those bugs don't seem to occur, and, I know it's in Chinese, but it's easy enough to go into the settings and change it. If the users aren't smart enough to click 2 buttons they shouldn't have an unlocked bootloader.
I did actually try looking for a newer version in the 7to forums, but since it was all in Chinese (and Google translate wasn't too helpful) and the fact that the website is rubbishly designed, I couldn't find anything, but, this works for now, at least it can flash stuff and boots, that ls really all that's needed.
Actually, in chinese forums, its not hard to find this.
Here I share the latest twrp, which could be used in all kirin services and support treble roms in theory, and its develoler is "残芯此生不换".
drive.google.com/file/d/17h0LRPXpWu_dZtFxLEpFGz2Oheh8K8mq/view?usp=drivesdk
741543825 said:
Actually, in chinese forums, its not hard to find this.
Here I share the latest twrp, which could be used in all kirin services and support treble roms in theory, and its develoler is "残芯此生不换".
drive.google.com/file/d/17h0LRPXpWu_dZtFxLEpFGz2Oheh8K8mq/view?usp=drivesdk
Click to expand...
Click to collapse
Did you tried it?
I have a P10, this should be flashed in this way? fastboot flash recovery_ramdisk xxxxxx.img
Thanks a lot! Thanks to this i was able to flash gapps on Android 9.0 on Honor 9
streetu said:
Thanks a lot! Thanks to this i was able to flash gapps on Android 9.0 on Honor 9
Click to expand...
Click to collapse
Android 9 . Which rom for H9 ?
k1ks said:
Android 9 . Which rom for H9 ?
Click to expand...
Click to collapse
For me PHH AOSP works fine Just flashlight and probably NFC aren't working
streetu said:
For me PHH AOSP works fine Just flashlight and probably NFC aren't working
Click to expand...
Click to collapse
Thanks , will test after Havoc.
Anyone know if there have been any updates for this
Why not update the system, ？
My device is Huawei honor v9
Anytime tested this on the p20 Pro?
赛文 to的广告太多了。。。
working on p smart
741543825 said:
Actually, in chinese forums, its not hard to find this.
Here I share the latest twrp, which could be used in all kirin services and support treble roms in theory, and its develoler is "残芯此生不换".
drive.google.com/file/d/17h0LRPXpWu_dZtFxLEpFGz2Oheh8K8mq/view?usp=drivesdk
Click to expand...
Click to collapse
Hi, can you or anybody upload this TWRP please?
The Link is not working (Google Drive say: The owner moved the file to recycle bin)
Thanks
LATEST TWRP FOR ONEPLUS 2, PORTED FROM NEXUS 6P.
WORKS WELL WITH ANDROID 11.
Latest VS Official 3.2:
Official TWRP 3.2 is built with OnePlus 2 by TWRP official and should be stable.
This unofficial TWRP 3.5.2 is ported from Nexus 6P's official one. The newer version means better support to new ROMs, especially Android 11 and higher. But please notice I can't promise that it is stable and everything works properly.
Installation:
Boot your phone into fastboot, connect it to your computer (or any other device that could run fastboot commands), make sure the driver is installed correctly.
Code:
# For flashing to recovery partition
fastboot flash recovery PATH/FILENAME.img
# For booting into TWRP temporarily
fastboot boot PATH/FILENAME.img
Known Issue(s):
Chinese Language XMLs currently not working.
Download:
Android File Host
Hello, and thanks for posting this! Can you explain what files were replaced, also where is the original source?
bitpushr said:
Hello, and thanks for posting this! Can you explain what files were replaced, also where is the original source?
Click to expand...
Click to collapse
Here is the source of the file:
Download twrp-3.5.0_9-0-angler.img
Download page for twrp-3.5.0_9-0-angler.img
dl.twrp.me
I unpacked it and replaced kernel.gz, recovery.fstab (in /initrd/etc/) and keys (in /initrd/res) and modified some values in /initrd/default.prop
What kernel.gz did you replace it with?
bitpushr said:
What kernel.gz did you replace it with?
Click to expand...
Click to collapse
from the oneplus2 twrp 3.4.0:
Download mukul2259 from SourceForge.net
Maybe stupid question, but what are benefits of this one over official 3.2?
dankovac1999 said:
Maybe stupid question, but what are benefits of this one over official 3.2?
Click to expand...
Click to collapse
It's much more friendly to Android 11 ROMs, though sadly we don't have one usable yet : (
Can I treblize my device with this recovery?
Missignal_Dev said:
It's much more friendly to Android 11 ROMs, though sadly we don't have one usable yet : (
Click to expand...
Click to collapse
It changed yesterday! Im moving to this recovery. But Im just wondering why isnt this device officially supported, when lot of older devices are.
dankovac1999 said:
It changed yesterday! Im moving to this recovery. But Im just wondering why isnt this device officially supported, when lot of older devices are.
Click to expand...
Click to collapse
Because it is old and not that popular. BTW. thank you for telling me this, I'm going to flash LOS 18.1. FINALLY AN USABLE ANDROID 11!!
Jaiwantn said:
Can I treblize my device with this recovery?
Click to expand...
Click to collapse
No.
**THIS WILL BE DISCONTINUED, INSTEAD I BUILT ORANGEFOX RECOVERY USING OP2 DEVICE TREE WHICH SUPPORTS ANDROID 11 PRETTY WELL.
Missignal_Dev said:
**THIS WILL BE DISCONTINUED, INSTEAD I BUILT ORANGEFOX RECOVERY USING OP2 DEVICE TREE WHICH SUPPORTS ANDROID 11 PRETTY WELL.
Click to expand...
Click to collapse
Pls provide download link of that
Jaiwantn said:
Pls provide download link of that
Click to expand...
Click to collapse
I'm writing the post, wait a minute
Jaiwantn said:
Pls provide download link of that
Click to expand...
Click to collapse
[RECOVERY][UNOFFICIAL] OrangeFox Recovery Project [R11.1][BETA v3]
Note: This is still a beta stage, I need your help in testing, thank you very much! (If you find a problem, please let me know) /* * Your warranty is now void. * * We're not responsible for bricked devices, dead SD cards, * thermonuclear war...
forum.xda-developers.com
After some effort I have rebased the twrp tree for merlin to twrp 3.6.2_11-0 and after some builds and revisions I have it fully working
Credits:
Me (rebased tree)
Val (built for me as I have potato pc)
Cane (tested for me I literally don't own merlin lol)
method to install:
fastboot flash recovery (insert path to downloaded twrp here)
Device tree:
GitHub - halal-beef/twrp_device_xiaomi_merlin
Contribute to halal-beef/twrp_device_xiaomi_merlin development by creating an account on GitHub.
github.com
areallydumbperson said:
After some effort I have rebased the twrp tree for merlin to twrp 3.6.2_11-0 and after some builds and revisions I have it fully working
Credits:
Me (rebased tree)
Val (built for me as I have potato pc)
Cane (tested for me I literally don't own merlin lol)
method to install:
fastboot flash recovery (insert path to downloaded twrp here)
Device tree:
GitHub - halal-beef/twrp_device_xiaomi_merlin
Contribute to halal-beef/twrp_device_xiaomi_merlin development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
hi i want to install shrp or twrp and I'm currently on miui 12.0.1 and android 10. Which ver. of shrp or twrp should I install.
Just for general knowledge can you tell me whether I should be concerned about the twrp and the android version on which I'm installing it?
For twrp you should be able to install this twrp and other twrp but shrp I'm not too sure of
My phone isnt detected in sideload, is that because of the TWRP or have I done something wrong?
TheEpicFlame said:
My phone isnt detected in sideload, is that because of the TWRP or have I done something wrong?
Click to expand...
Click to collapse
May be your drivers
areallydumbperson said:
May be your drivers
Click to expand...
Click to collapse
Used a twrp from the messenger group and it worked fine.
Does it work on the M2003J15SG model with the MIUI 12.5.5 RJOEUXM? (1st April 2022 Patch)
It has an unlocked bootloader and I'm trying to escape the MIUI.
Mineplayerminer said:
Does it work on the M2003J15SG model with the MIUI 12.5.5 RJOEUXM? (1st April 2022 Patch)
It has an unlocked bootloader and I'm trying to escape the MIUI.
Click to expand...
Click to collapse
you can try shrp its great download the latest version from their official site
Mineplayerminer said:
Does it work on the M2003J15SG model with the MIUI 12.5.5 RJOEUXM? (1st April 2022 Patch)
It has an unlocked bootloader and I'm trying to escape the MIUI.
Click to expand...
Click to collapse
Most likely yes
Manjotbenipal said:
you can try shrp its great download the latest version from their official site
Click to expand...
Click to collapse
Yeah, I saw this recovery earlier. Will it wipe my phone and internal storage after flashing this? What, if the flash fails or something happens during that? I've heard, that MediaTek phones are harder to unbrick. I just need a root to get rid of the MIUI apps. Unless there will be another daily driver ROM like the Project Elixir that is in the beta. The only thing I would miss will be the Redmi Buds 3 Pro pop-up message, or the Mi Band 5 proximity unlock. It's wonderful that someone is still trying to develop something better for that phone.
Edit: Ignore my broken grammar.
Mineplayerminer said:
Yeah, I saw this recovery earlier. Will it wipe my phone and internal storage after flashing this? What, if the flash fails or something happens during that? I've heard, that MediaTek phones are harder to unbrick. I just need a root to get rid of the MIUI apps. Unless there will be another daily driver ROM like the Project Elixir that is in the beta. The only thing I would miss will be the Redmi Buds 3 Pro pop-up message, or the Mi Band 5 proximity unlock. It's wonderful that someone is still trying to develop something better for that phone.
Edit: Ignore my broken grammar.
Click to expand...
Click to collapse
You can rest easy my friend i have used shrp for android 11 and it's great
It will not wipe your data
And my phone was rooted while flashing shrp
Just don't forget to disable avb before flashing both magisk patched boot.img and
shrp(fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img)
Coz I have faced the aftermath of not doing it which got me stuck in a bootloop.
It A12 supported ???
muerto_parao said:
It A12 supported ???
Click to expand...
Click to collapse
I don't know I'm kinda scared too as i have downgraded to android 10 and now finding it difficult to get a suitable version of twrp!
Manjotbenipal said:
I don't know I'm kinda scared too as i have downgraded to android 10 and now finding it difficult to get a suitable version of twrp!
Click to expand...
Click to collapse
It doesn't support A12, I flashed it already
muerto_parao said:
It doesn't support A12, I flashed it already
Click to expand...
Click to collapse
It'd take some effort for A12 support
areallydumbperson said:
It'd take some effort for A12 support
Click to expand...
Click to collapse
That's would be great , man
areallydumbperson said:
After some effort I have rebased the twrp tree for merlin to twrp 3.6.2_11-0 and after some builds and revisions I have it fully working
Credits:
Me (rebased tree)
Val (built for me as I have potato pc)
Cane (tested for me I literally don't own merlin lol)
method to install:
fastboot flash recovery (insert path to downloaded twrp here)
Device tree:
GitHub - halal-beef/twrp_device_xiaomi_merlin
Contribute to halal-beef/twrp_device_xiaomi_merlin development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
Does this twrp support installation of custom roms and have close avb2.0 option?
Custom ROM installs should be supported but avb2.0 patching isn't included in the recovery as this is a clean unmodified twrp
doesn't boot from recovery.img not from fastboot boot either
whyem1x said:
doesn't boot from recovery.img not from fastboot boot either
Click to expand...
Click to collapse
worked after returning to android 10