Hi all,
I've made my work on AOSP Phh-Treble as modular as possible, so that it can be reused on other ROMs.
As part of this effort, I'm releasing GSIs of LineageOS
This is a GSI, and true to the GSI spirit. It aims at supporting a maximum number of devices, but only with AOSP-available hardware features.
All credits obviously goes to LineageOS developers
v5: (2018-06-27)
Image for ARM64 A-only device with gapps
Image for ARM64 A-only device vanilla
Image for ARM64 A/B device with gapps
Image for ARM64 A/B device vanilla
Image for ARM32 A-only device with Android Go gapps
Image for ARM32 A-only device vanilla
v4: (2018-05-19)
Image for ARM64 A-only device
Image for ARM64 A/B device
Image for ARM32 A-only device
Image for ARM32 A-only devices, with Android Go gapps
V3: (2018-04-05)
Image for ARM64 A-only device
Image for ARM64 A/B device
Image for ARM32 A-only device
ChangeLog:
v4 (2018-05-19):
- Blackview A20 edition! Thanks to blackview for giving me this Android Go test device
- Fix Accents
- Update to latest AOSP Phh-Treble patches
- New Android Go variant with gapps
v3 (2018-04-05):
- Fix Galaxy S9 backlight control
- Support exfat sdcards on devices with exfat support in kernel
- Resize /system to maximum size on first boot
v2 (2018-03-26):
- Fix Galaxy S9 backlight control
How to build:
Code:
git clone https://github.com/phhusson/treble_experimentations
mkdir Lineage; cd Lineage
bash ../treble_experimentations/build-rom.sh android-8.1 lineage
Great Work!
Thanks for your work. I'll try this rom this weekend (I had problems with your other AOSP roms, I can't boot except the v9 one. I hope this version will boot).
iBen68 said:
Thanks for your work. I'll try this rom this weekend (I had problems with your other AOSP roms, I can't boot except the v9 one. I hope this version will boot).
Click to expand...
Click to collapse
I doubt it will boot.
What device is this? Could you get logs?
phhusson said:
I doubt it will boot.
What device is this? Could you get logs?
Click to expand...
Click to collapse
Huawei Mate 10 Pro BLA-L09. I will try to get logs when I try this rom.
Great work
bootloop on xperia xz1
i flashed it on stock rom and wipe userdata,cache on fastboot and also tried on twrp factory reset and cache,cache dalvik(i tried your aosp v9 v10 v11 it also doesn't work)
phhusson said:
I doubt it will boot.
What device is this? Could you get logs?
Click to expand...
Click to collapse
How can I get logs at this point?
eggimong said:
bootloop on xperia xz1
i flashed it on stock rom and wipe userdata,cache on fastboot and also tried on twrp factory reset and cache,cache dalvik(i tried your aosp v9 v10 v11 it also doesn't work)
Click to expand...
Click to collapse
Can you try this?
https://www.google.fr/amp/s/forum.x...l/how-to/treble-roms-pixel-2-xl-t3764851/amp/
What's the precise behaviour you're witnessing?
Do you get the White Android bootanimation, or only sony's logo?
Does it actually reboot when looping? You see the sony logo reappearing?
Does the device reboot to bootloader mode?
phhusson said:
I doubt it will boot.
What device is this? Could you get logs?
Click to expand...
Click to collapse
When I try
Code:
adb logcat
I got this:
Code:
PS C:\ADB> adb logcat
- waiting for device -
The adb daemon seems not to be started while the bootloop. When I go back to the AOSP v9 rom, I can see logs with the same command but it's pointless since this rom is booting well.
iBen68 said:
When I try
Code:
adb logcat
I got this:
Code:
PS C:\ADB> adb logcat
- waiting for device -
The adb daemon seems not to be started while the bootloop. When I go back to the AOSP v9 rom, I can see logs with the same command but it's pointless since this rom is booting well.
Click to expand...
Click to collapse
Does adb devices -l sees it?
phhusson said:
Can you try this?
https://www.google.fr/amp/s/forum.x...l/how-to/treble-roms-pixel-2-xl-t3764851/amp/
What's the precise behaviour you're witnessing?
Do you get the White Android bootanimation, or only sony's logo?
Does it actually reboot when looping? You see the sony logo reappearing?
Does the device reboot to bootloader mode?
Click to expand...
Click to collapse
Only sony's logo and it reappearing until I turn off the phone
eggimong said:
Only sony's logo and it reappearing until I turn off the phone
Click to expand...
Click to collapse
And did you try what's in the link I've given you?
phhusson said:
And did you try what's in the link I've given you?
Click to expand...
Click to collapse
can't flash on vbmeta partition with error
fastboot flash vbmeta vbmeta.img
FAILED <remote: Flashing is not allowed for partition>
Is it possible to build this w/ MicroG?
LiveDisplay and LED while charging do not work on Mido everything else work just fine
NadavCE said:
Is it possible to build this w/ MicroG?
Click to expand...
Click to collapse
Assume you're asking due to the news about Gapps and 'Uncertified Device' problems.
Seems like a lot more is riding on MicroG now ...
Also, pretty sad that Google have done this ... Treble was probably the best thing they've done for Android since its inception, both for custom ROM development and potentially speeding up software updates for those who don't tinker with their phones.
mudnightoil said:
Assume you're asking due to the news about Gapps and 'Uncertified Device' problems.
Seems like a lot more is riding on MicroG now ...
Also, pretty sad that Google have done this ... Treble was probably the best thing they've done for Android since its inception, both for custom ROM development and potentially speeding up software updates for those who don't tinker with their phones.
Click to expand...
Click to collapse
Well custom ROMs are whitelisted and so far I have not reported any issue with the Uncertified Device stuff on this GSI nor on RR GSI either, both by phhusson of course
patrick395x said:
Well custom ROMs are whitelisted and so far I have not reported any issue with the Uncertified Device stuff on this GSI nor on RR GSI either, both by phhusson of course
Click to expand...
Click to collapse
I don't think that is expected to remain the status quo. In fact if you read the screen / article, people running custom ROMs are expected to manually register their devices with Google ... and whether that is just a registration or additional tracking is unclear.
mudnightoil said:
I don't think that is expected to remain the status quo. In fact if you read the screen / article, people running custom ROMs are expected to manually register their devices with Google ... and whether that is just a registration or additional tracking is unclear.
Click to expand...
Click to collapse
I know, I read the article, but until we receive the Android ID registration we can keep using custom ROMs in an uncertified manner, once we are required to registrate our device we will see what happens
Related
Hi all,
Please consider using official Resurrection Remix GSI instead of this!
I've made my work on AOSP Phh-Treble as modular as possible, so that it can be reused on other ROMs.
As part of this effort, I'm releasing GSIs of Resurrection Remix.
This is a GSI, and true to the GSI spirit. It aims at supporting a maximum number of devices, but only with AOSP-available hardware features.
All credits obviously goes to Resurrection Remix developers
v5: (2018-06-27)
Image for ARM64 A-only device with gapps
Image for ARM64 A-only device vanilla
Image for ARM64 A/B device with gapps
Image for ARM64 A/B device vanilla
Image for ARM32 A-only device with Android Go gapps
Image for ARM32 A-only device vanilla
v4: (2018-05-19)
Image for ARM64 A-only device
Image for ARM64 A/B device
Image for ARM32 A-only device
Image for ARM32 A-only devices, with Android Go gapps
V3: (2018-04-05)
Image for ARM64 A-only device
Image for ARM64 A/B device
Image for ARM32 A-only device
ChangeLog:
v4 (2018-05-19):
- Update to latest AOSP Phh-Treble patches
- New Android Go variant with gapps
v3 (2018-04-05):
- Fixed S9 backlight control
- Resize /system to maximum size on first boot
v2 (2018-03-26):
- Failed build
How to build:
Code:
git clone https://github.com/phhusson/treble_experimentations
mkdir RR; cd RR
bash ../treble_experimentations/build-rom.sh android-8.1 rr
I'm assuming that this build works with the G965F now?
Keep up the good work!
Woaw...thanks a lot for the Rom...
Savoury said:
I'm assuming that this build works with the G965F now?
Keep up the good work!
Click to expand...
Click to collapse
Well, this RR hasn't been tested much, and even AOSP hasn't been tested on G965F as far as I know.
But it's supposed to work.
Feel free to report your results
does this include gapps for a/b devices
Feel free to PM me, and we'll test AOSP if you want to.
thanks for your work, A-only version running smooth on S9+. GAPPS and if possible root would be nice.
Great Work!
Thanks! Working fine in Xiaomi Mi5 but some small bugs
Ohhhh man @phhusson this ROM is pure love, was desperately waiting for this, thankyou so much
Any idea how to flash Gapps onto the rom?
chen8894 said:
Any idea how to flash Gapps onto the rom?
Click to expand...
Click to collapse
Reboot Recovery after you flashed the Image, then install Opengapps of your choice. (Depends on free space on /System for some Devices, for Mido the Micro Gapps are to big)
panchovix said:
Thanks! Working fine in Xiaomi Mi5 but some small bugs
Click to expand...
Click to collapse
How many bugs?
ohwarumbloss said:
Reboot Recovery after you flashed the Image, then install Opengapps of your choice. (Depends on free space on /System for some Devices, for Mido the Micro Gapps are to big)
Click to expand...
Click to collapse
Sorry... didn't clarify. My device is mate 10 pro.
GerWonder said:
thanks for your work, A-only version running smooth on S9+. GAPPS and if possible root would be nice.
Click to expand...
Click to collapse
I guess the cameras don't work as with stock ROM? thinking of example the 2x zoom.
rafizulhasan said:
How many bugs?
Click to expand...
Click to collapse
Backlight buttons, VolTE and home fp button, well i mean they are not vital at all except maybe for VolTE (here in Chile at least VolTE isn't implemented yet, so no worries)
Just wondering tho, the GSI LOS and AOSP have backlight buttons since it has the options in the "buttons option", but not on RR GSI
panchovix said:
Backlight buttons, VolTE and home fp button, well i mean they are not vital at all except maybe for VolTE (here in Chile at least VolTE isn't implemented yet, so no worries)
Just wondering tho, the GSI LOS and AOSP have backlight buttons since it has the options in the "buttons option", but not on RR GSI
Click to expand...
Click to collapse
Yeah the button backlight patches don't apply on RR, and patch fails are ignored at the moment (because ROMs might already include patches. For instance lineage already has this button backlight patch.
I'll try to fix it, but that's quite low on my product priority list.
phhusson said:
Yeah the button backlight patches don't apply on RR, and patch fails are ignored at the moment (because ROMs might already include patches. For instance lineage already has this button backlight patch.
I'll try to fix it, but that's quite low on my product priority list.
Click to expand...
Click to collapse
No problem man! i'm just thankful of your work, it is just a minor thing for me at least
Thanks!Working on the mi 6 but can't set the password.
Great!
This is a GSI (generic system image) for AOKP for devices with treble support...
this requires fastboot to flash the system image, if you dont know how to use fastboot, you shouldnt be here...
Downloads
https://www.androidfilehost.com/?w=files&flid=261339 - a/b-only system.img (for pixel devices also download vbmeta.img)
https://www.androidfilehost.com/?w=files&flid=264729 - a-only system.img
MAKE SURE YOU ARE ON A STOCK AOSP ROM OR A PREVIOUS TREBLE BUILD
commands:
FOR A-ONLY
$: fastboot flash system system.img
$: fastboot boot twrp.img
wipe data and reboot
FOR A/B ONLY
$: fastboot flash system_a system.img
(FOR PIXEL DEVICES)
$: fastboot flash vbmeta_a vbmeta.img
$: fastboot boot twrp.img
wipe data and reboot.
tested on the Pixel 2 XL
credit goes to the AOKP gang and @phhusson who without i wouldnt have been able to compile this
screenshots:
https://ibb.co/dBnFPn
https://ibb.co/kvGEH7
https://ibb.co/hOLVqS
has GApps and root, you just need phh-su from the play store
Can port to a-only support
support a/ab or only ab?
lmentor said:
support a/ab or only ab?
Click to expand...
Click to collapse
A/B only devices
masara59 said:
Can port to a-only support
Click to expand...
Click to collapse
I will port this to an a only device today
sixohtew said:
I will port this to an a only device today
Click to expand...
Click to collapse
Good idea
cannot get passed the unicorn screen that could be because i cannot fully boot into twrp and ideas on pixel 2 xl fixed twrp now bootloops
sixohtew said:
I will port this to an a only device today
Click to expand...
Click to collapse
can't hardly wait ...
Will give this a try when its more polished/has root!
Was so close I thought when I seen the unicorn but never fully booted..?
Format data usually fixes no boot, just remember it wipes internal storage.
Any advance on A-only devices.?
I used to flashed one of your roms on my moto x pure edition. Now I switched to huawei mate 9.
osk4rin said:
Any advance on A-only devices.?
I used to flashed one of your roms on my moto x pure edition. Now I switched to huawei mate 9.
Click to expand...
Click to collapse
I'm building a new a/b build and a only build..I had to make a lot of changes to get it this far and it's at 90% on the ab build and a should take a lot less time since it doesn't need as much.. the only thing is I'm not positive I've got su working yet. I need to test it, but it's coming....
And thanks for using my roms on the Moto x pure...I loved that phone...if someone didn't steal it I'd prolly still be building for that phone
sixohtew said:
I'm building a new a/b build and a only build..I had to make a lot of changes to get it this far and it's at 90% on the ab build and a should take a lot less time since it doesn't need as much.. the only thing is I'm not positive I've got su working yet. I need to test it, but it's coming....
And thanks for using my roms on the Moto x pure...I loved that phone...if someone didn't steal it I'd prolly still be building for that phone
Click to expand...
Click to collapse
Wow, great!
I'll wait for your new A-only build.
By the way, My favorite Rom on moto x pure, was your resurrection remix.
Thank you!
[UPDATE] new a/b build and finally a new a-only build with the most recent commits, including rom control app/setting. updating OP now with new links
$: fastboot boot twrp.img ????? Why?
No only flash system???
aureliomilitao said:
$: fastboot boot twrp.img ????? Why?
No only flash system???
Click to expand...
Click to collapse
you need to wipe the data and twrp is the best at it.. fastboot boot wont flash twrp to the recovery partition, just boot into it.. some devices cant flash twrp
A-Only up and running on Mate 10 Pro
no gapps?
Does this have the no sound during calls?
sixohtew said:
[UPDATE] new a/b build and finally a new a-only build with the most recent commits, including rom control app/setting. updating OP now with new links
Click to expand...
Click to collapse
Thank you!
This is an unofficial and experimental build of lineage-16.0.
Please do feel free to try and report bugs on this thread (Logcats must be provided)
I will upload subsequent variants later on.
arm64 A-only Non-SU [no gapps] : https://drive.google.com/file/d/1A9kphkHJbRm1eL-6jh2-AuQABBvISOrz/view?usp=drivesdk
For future updates download links will be available at post 2.
You can join our telegram group for more help or discussion https://t.me/lineagegsi
This build has been tested and boots on Honor 7x.
Bugs noticed on the device:
Not full resolution
No torch
No hotspot
USB mtp mode has to be changed manually from dev settings.
Screenshots can be checked here, https://imgur.com/a/4GWQuQ4
Bugs may vary from device to device.
I am not the developer of this Gsi credit goes to @m_vaisakh
Thanks to @phhusson
Built using phhusson's build script.
Downloads:
ARM64 A-ONLY NO-GAPPS
ARM64-A-ONLY WITH GAPPS
Update 31/08/2018
ARM64 A/B NO-GAPPS (Thanks a lot to @eminem5055 , he built this)
You can also join telegram to support better with logcats:
Telegram Group
It's not booting on the Huawei Y6 (2018)
It is like every pie gsi everything works fine but no incall sound
iDecrypt said:
It's not booting on the Huawei Y6 (2018)
Click to expand...
Click to collapse
aljoscha81 said:
It is like every pie gsi everything works fine but no incall sound
Click to expand...
Click to collapse
Can you guys provide logs to check the issue?
Hey @avirk is volte with jio sim working???
Lucciferr said:
Hey @avirk is volte with jio sim working???
Click to expand...
Click to collapse
Haven't tested VoLTE yet. Should work, if it worked for you in los-15.1 treble build.
avirk said:
Can you guys provide logs to check the issue?
Click to expand...
Click to collapse
Yes i will send you a log file but i think it is a vendor issue cause every 9 gsi rom got that on my device
avirk said:
Can you guys provide logs to check the issue?
Click to expand...
Click to collapse
How should I provide logs when it's not booting.
iDecrypt said:
How should I provide logs when it's not booting.
Click to expand...
Click to collapse
By using adb... you can take logs as it's booting.
crayonicle said:
By using adb... you can take logs as it's booting.
Click to expand...
Click to collapse
It stucks in the bootloader so adb isn't working.
iDecrypt said:
It stucks in the bootloader so adb isn't working.
Click to expand...
Click to collapse
Huh, what the heck. You can try factory resetting? In stock recovery.
crayonicle said:
Huh, what the heck. You can try factory resetting? In stock recovery.
Click to expand...
Click to collapse
Already tried that, no Pie ROM is working on this phone :/
iDecrypt said:
Already tried that, no Pie ROM is working on this phone :/
Click to expand...
Click to collapse
Something must be broken on that side if you are at bootanimation then 90% chances that adb will work. Are you sure that you have treble supported twrp and already on a treble build?
bootloop on xiaomi mi6x
avirk said:
Something must be broken on that side if you are at bootanimation then 90% chances that adb will work. Are you sure that you have treble supported twrp and already on a treble build?
Click to expand...
Click to collapse
I don't have any TWRP but all Oreo GSIs are working fine, just the Pie GSIs aren't working, and i wont even get to the bootanimation.
Boots on P20-Lite but stuck on a Pixel configuration stopped working prompt loop.
mchtt said:
Boots on P20-Lite but stuck on a Pixel configuration stopped working prompt loop.
Click to expand...
Click to collapse
Delete SetupWizard in /system/priv-app via recovery and reboot. If you want a working Setup, use the vanilla variant an flash unofficial GApps by @Nezorflame.
Hi, Just flashed to my Umidigi A1 Pro - I am seemingly having the same issue with every Android 9 Pie GSI, everything flashes without issue, system starts and everything looks fine, then as soon as I open app drawer, or enter settings, the system freezes and screen becomes unresponsive, then phone reboots to lockscreen. I am new to flashing treble GSI's, but 8.1 Oreo GSI's don't seem to be affected. I have provided a logcat if this will be of any assistance.
https://drive.google.com/file/d/1vci1GXP9bGqWl1Pdnn9dMCloBYmVFIWf/view?usp=sharing
why cant i flash it ...it says size of image is larger than target device
Project treble for Xperia X [ android 10]
Based on Sony Open Devices
Based on Pavel's works
I am not responsible for bricked devices, dead SD cards,.
This is built as dual model, but it could also work on F5121.
Required files:
[OEM file:] Download link
Recommend: V9
[Treble files:] Download link
[Twrp-Q] Download link
How to flash::
First: Flash Twrp I built which supports a Vendor Partition
Code:
fastboot flash recovery < Path of recovery.img >
Second:Format Data and Cache in twrp
Flash treble images in fastboot mode:
Code:
fastboot flash:raw boot < Path of boot.img >
Code:
fastboot flash cache < Path of vendor.img >
Third: flash SW_binaries provided by Sony.
You can also download it from Sony official website.
Code:
fastboot flash oem < Path of OEM.img >
Fourth: Flash a GSI compatible System image and boot! Notice: GSI should be arm64 A/B type
Code:
fastboot flash system < Path of GSI-System.img >
Source Codes
Kernel
Contributors
Sjll @Cubbins
ROM OS Version: 10.0 Q
ROM Kernel: Linux 4.9
Version Information
Status: Testing
Donation:
Paypal
Created 2020-10-25
Last Updated 2020-10-25
Res
Thanks for sharing that
it's working on my F5121
but there's no sound on calls.
HTML:
Duronsoft said:
Thanks for sharing that
it's working on my F5121
but there's no sound on calls.
Click to expand...
Click to collapse
Tested on LineageOS 17.1 GSI, sound is fine when calling.
Duronsoft said:
Thanks for sharing that
it's working on my F5121
but there's no sound on calls.
Click to expand...
Click to collapse
this is a known issue, I will fix it soon
pls help me, i flashed my phone ok but at home sreen notice "
There's an internal problem with your device. Contact your manufacturer for details."
how to fix it?
thank you bro
Tested on F5122 ( Dual ), confirmed Lineage, Havoc and PE, AOSP can be used daily/
However if anyone planning to listen some music on it, use .flac format, .mp3 give you no sound, also Viper not working
---------- Post added at 08:28 AM ---------- Previous post was at 08:24 AM ----------
Noname_90 said:
pls help me, i flashed my phone ok but at home sreen notice "
There's an internal problem with your device. Contact your manufacturer for details."
how to fix it?
thank you bro
Click to expand...
Click to collapse
did you flashed an OEM system image
did you flashed an OEM system image
=> yes, i did it
and no sound for call
my device is f5122
Noname_90 said:
did you flashed an OEM system image
=> yes, i did it
and no sound for call
my device is f5122
Click to expand...
Click to collapse
only a few chance that OEM image would fully functional, i recommend using Official phhusson GSI, currently running Havoc 3.8 and calling have sound
no in-call sound is not an oem or blobs issue, but audio HAL.
I would be glad if someone opened all the issues in the bug tracker, then I will not forget about anything and it will be easier for you to track their current status. Thanks.
Best regards,
Pavel
Phone doesn't awake from deep sleep. I was put it on my desk than pressed power button 10 minutes later and phone waited with black screen than rebooted itself. Anyone has this issue?
Cubbins said:
no in-call sound is not an oem or blobs issue, but audio HAL.
I would be glad if someone opened all the issues in the bug tracker, then I will not forget about anything and it will be easier for you to track their current status. Thanks.
Best regards,
Pavel
Click to expand...
Click to collapse
I've created an issue in bug tracker and i will update all of them there ( in future )
TechnoHT said:
I've created an issue in bug tracker and i will update all of them there ( in future )
Click to expand...
Click to collapse
I noticed it. Thanks. Will see what I can do
Hello, thanks for the amazing work :victory:. The only issue is that I cannot add any fingerprint, tried with descendant x and havoc 3.8.
Other than that, everything is working for me, thank you
for anyone getting .mp3 crashing/no audio, please try to install Viper4Android and turn on Legacy mode in settings
( for further bug + fix just visit bug tracker )
@Sjll
Boot and vendor are cross-compatible for X-Compact (vendor at least is)? Please advise, or port and I will test (when you have a moment).
&(*) said:
@Sjll
Would you be willing to do a Kugo (X-Compact) port (when you have a moment, if possible)?
Click to expand...
Click to collapse
Pretty sure the vendor.img in cache will boot with X-Compact as the partitions are identical. I have a modified boot with the path set for vendor in kernel (hardcoded). Please advise.
&(*) said:
@Sjll
Boot and vendor are cross-compatible for X-Compact (vendor at least is)? Please advise, or port and I will test (when you have a moment).
Click to expand...
Click to collapse
Some things are different. You need another build. Otherwise you can damage your hardware.
If you are interested, I can make a build. But it will be Android 11
Cubbins said:
Some things are different. You need another build. Otherwise you can damage your hardware.
If you are interested, I can make a build. But it will be Android 11
Click to expand...
Click to collapse
That'd be nice (AOSP 11); I think devs like @Sjll don't consider requests or the reasons why || are too busy with other devices. Currently, my hardware is not capable of producing builds or I already would have done it on my own. I attempted to produce the vendor.img and always got a soong 21 error without reasonable debug info leading me to believe RAM is the issue. Regardless, X-Compact needs some attention as everything available is not up to date. I think the kernel and AOSP 10 dev's device bit the dust and the tree is no longer being maintained.
&(*) said:
That'd be nice (AOSP 11); I think devs like @Sjll don't consider requests or the reasons why || are too busy with other devices. Currently, my hardware is not capable of producing builds or I already would have done it on my own. I attempted to produce the vendor.img and always got a soong 21 error without reasonable debug info leading me to believe RAM is the issue. Regardless, X-Compact needs some attention as everything available is not up to date. I think the kernel and AOSP 10 dev's device bit the dust and the tree is no longer being maintained.
Click to expand...
Click to collapse
I have the kernel, device tree, everything. So soon you will get a build. But I only have Xperia X, so you will be my eyes and ears
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