I have flashed twrp Treble recovery and treble ROM with Android 8 can I now go back to simple original twrp and non - treble roms ?
And am I still be able to switch back to miui !??
Aditya Telange said:
I have flashed twrp Treble recovery and treble ROM with Android 8 can I now go back to simple original twrp and non - treble roms ?
And am I still be able to switch back to miui !??
Click to expand...
Click to collapse
Yes you can follow this steps to switch treble to non-treble build..
Reboot into recovery select install image now select non-treble recovery then wipe -advanced wipe-select system,data,dalvik-cache,cache then flash non-treble build that's it if uh facing bootloop then wipe again and flash any custom kernel then flash your rom that's it..
Yes. You can use the Treble supported recovery for non Treble ROMs and you can switch back to miui
Related
I am currently in MM, i want to go back to MIUI to try MIUI8 Global beta. I have one twrp back for MIUI7, but when i flash that from recovery (twrp 3.0.2), it shows error. Then i tried with twrp 2.8.7. but same error.
Now when i go back to MM by restoring the MM roms from TWRP recovery, phone is not unlocking even if i am entering the correct pattern. First i flashed revert back to TWRP 3.0.2, then tried to restore the back up MM roms.
I also tried to flash new MM roms, but the SIM and Wifi is not detecting.
Is there anyway that i can flash ROM. I don't think my phone is bricked, but somehow there was some error happened while i flashed MIUI backup from TWRP 2.8.7.
Device name Redmi2 2014818
You have to do Fastboot Update.
Persizi said:
You have to do Fastboot Update.
Click to expand...
Click to collapse
So will the MM recovery ROMs will work now if i again move to MM based on CM13.
rkpg said:
So will the MM recovery ROMs will work now if i again move to MM based on CM13.
Click to expand...
Click to collapse
Exactly. Just flash the TWRP recovery and you will good to go.
you may try flashing miui 7 rom from fastboot then install miui 8 from recovery ( from update > choose update package)
Flash phillz recovery by jav team and boot up in recovery then-clean to install a new rom-and flash miui 8 kk ROM it will successfully flash the ROM and will restore original firmware and ur good to go...phillz recovery will give no error while flashing...
Some times twrp gives an error by saying that its a ROM for 2014811 and u cannot install it on 2014818 better use phillz for flashing miui ROMs...
I hope this method will help u.
A GUIDE TO FLASH LATEST TREBLE ROMS, OLDER TREBLE ROMS OR NON-TREBLE ROMS ROMS
UPDATE: A guide to rename our /factory partition as /vendor so that you can flash OLDER Android Oreo treble builds! We do not need this guide on Android Pie custom ROMs or for Stock ZUI WE ONLY NEED THIS FOR ANDROID OREO TREBLE BUILDS REQUIRING /factory renamed as /vendor
for Lenovo Zuk Z2 Plus
Latest Treble : /factory renamed i.e switched to /vendor
Older Treble:/factory mounted as /vendor
Non-Treble: Nothing to do with Vendor, Factory stuff lol
INTRO
As you all know that we now have TREBLE, and Zuk-devs are working hard to improve it further so that when the time comes we can move to GSI builds of future Android versions.
Recently, Zuk-devs have renamed the /factory partition into /vendor partition previously we were mounting /factory as /vendor but now it has been converted(renamed) to /vendor partition with this you'll be able to use a Proper Magisk zip, and you don't need a modded/edited Magisk, etc and lotta other kinds of stuff that we will discuss and come to know in the future.
rootdir: fstab: Use the right label for our vendor partition.
TUTORIAL:
What you want to do:
** Flash OLD TREBLE ROMS /factory is renamed to /vendor - NOTE NOT NEEDED FOR NEWER ROMS! **
Instructions:
* Flash "Factory2Vendor_plus.zip",
*Flash below linkedTWRP,
*Reboot To TWRP,
*Flash ROM,
+ GApps / + Magisk etc
* Reboot.
*Enjoy :fingers-crossed:
Downloads:
Factory2Vendor_plus: https://androidfilehost.com/?fid=962187416754475515
treble-TWRP 3.2.2 v2: https://www.androidfilehost.com/?fid=5862345805528044154
** REVERTING BACK to NORMAL aka renaming /vendor back to/factory **
Instructions:
*Flash "Vendor 2Factory_plus.zip",
*Flash LATEST OFFICIAL TWRP,
*Reboot TWRP,
*Flash ROM,
(+ GApps)
*Reboot.
*Enjoy :fingers-crossed:
Downloads:
Vendor2Factory_plus: https://androidfilehost.com/?fid=962187416754475514
https://twrp.me/zuk/zukz2.html
3. Flashing a Non-Treble RoM which has nothing to do with /factory /vendor partition etc.
Instructions:
*Coming from the above procedure, no need to do anything! the new OFFICIAL TWRP will work for Non Treble roms as well and No patches need to be flashed*
*Flash ROM,
+ GApps / + Magisk etc
*Reboot.
*Enjoy :fingers-crossed:
Notes:
This 'New TWRP' will work for both Latest Treble and Non-Treble ROMs
For ZUI also no need to flash any patch, New TWRP shall work (Needs to be tested)
You can flash Non-Treble ROMs and Nougat Builds or other builds with the new TWRP and no patches need to be flashed
Once you flash "factory2vendor" or "vendor2factory" you do not need to flash again unless mentioned in the build
or if you want to revert back to Old Treble ROMs where /factory was mounted as /vendor
CREDITS
Zuk-devs - Davidevinavil, DD3Boh and Cosmedd (https://github.com/zuk-devs)
@Fedor917 for giving the idea
And all others who have contributed in any manner! :highfive:
Team win recovery project - 3.2.2 - treble [unofficial]
Treble supported TWRP 3.2.2 ONLY FOR ROMS with /factory renamed as /vendor
CHANGELOGS:
V1-
Device Specific:-
- Persist option
- Download Mode (edl)
- Fixed Partition Size
- Update the kernel image to get the latest commits for ext4, f2fs etc (cosmedd)
- Default brightness to 40%
General:
- adb backup fixes
- OTA style update zips will now install automatically without prompting for decrypt
- minor tweaks to handling date/time on Qualcomm devices
- updates to some language translations
V2-
- Vendor Wiping option
- Persist Backup/Restore
- Splash backup/restore and now can be flashed via img
DOWNLOAD:
https://androidfilehost.com/?fid=5862345805528044154
Source Code:
Device: https://github.com/kubersharma001/twrp_device_zuk_z2_plus
Kernel : https://github.com/cosmedd/android_kernel_zuk_msm8996/tree/twrp[/url]
SPECIAL THANKS TO
Alvaro
DD3Boh
Cosmedd
DavideVinavil
Pavan & Starman for testing!
FOR ANYTHING ELSE OR NORMAL TREBLE BUILDS (aka just using /factory) or NON TREBLE BUILDS USE ONLY FROM:
https://forum.xda-developers.com/le...-official-teamwin-recovery-project-3-t3899166
Reserved
So we'll have an updated TWRP for this full treble now? Is it still backward compatible with non treble rom like the partial one?
pipyakas said:
So we'll have an updated TWRP for this full treble now? Is it still backward compatible with non treble rom like the partial one?
Click to expand...
Click to collapse
New TWRP is for New Treble ROMs where /factory partition has been renamed to /vendor partition and It is for all the Non Treble Builds
Old TWRP is for Partial/Full Treble ROMs where /factory partition is mounted as /vendor partition
Thanks for the detailed instructions!
I was before on non treble builds and as instructed on AEX thread (Davide recommendation) I flashed Zuk stock ZUI rom (Oreo)
Than I flashed partial treble rom with new TWRP he instructed, and also future full treble roms.
Now I'm on latest 5.4
I once did revert to 5.2 but before that I wiped everything and installed old TWRP and made come back to 5.2
But as new build came out fast with fixes I flashed again TWRP with treble support and flashed 5.4 rom
My question is do I need to do any step here explained or not?
Everything working fine here, TWRP saw and flashed vendor partition.
Thanks for answer in advance
I couldn't understand completely
Im on latest AEX With developers twrp
Should i flash New Twrp first and then the factory package
Or its the opposite
And which factory zip should i flash
To be on the next AEX version
The steps mentioned above applies for the new builds that are going to come.
Now I'm on AEX 5.4 with the treble TWRP from #2...
So with the next build I should flash the Factory2Vendor.zip then a new (official?) TWRP img and then (after a recovery reboot) clean install the new build as usual? @kubersharma
frozenfirevr said:
Now I'm on AEX 5.4 with the treble TWRP from #2...
So with the next build I should flash the Factory2Vendor.zip then a new (official?) TWRP img and then (after a recovery reboot) clean install the new build as usual? @kubersharma
Click to expand...
Click to collapse
Yes
Does New Twrp (#1) can Be used for Non Treble ROMs.?
--------
Please clarify, which zip should be flashed first, vendor zip or twrp zip.
Moto-B said:
Please clarify, which zip should be flashed first, vendor zip or twrp zip.
Click to expand...
Click to collapse
+1
Moto-B said:
Please clarify, which zip should be flashed first, vendor zip or twrp zip.
Click to expand...
Click to collapse
First flash,factory2vender zip....
And then flash new twrp.img
I am on bootleggers ROM
Can anyone explain sequence of flashing the files??
Dhinesh1999 said:
Does New Twrp (#1) can Be used for Non Treble ROMs.?
Click to expand...
Click to collapse
Yes you may. Already mention by Kuber somewhere in the first page.
---------- Post added at 01:37 PM ---------- Previous post was at 01:29 PM ----------
vuckovic_stefan said:
Thanks for the detailed instructions!
I was before on non treble builds and as instructed on AEX thread (Davide recommendation) I flashed Zuk stock ZUI rom (Oreo)
Than I flashed partial treble rom with new TWRP he instructed, and also future full treble roms.
Now I'm on latest 5.4
I once did revert to 5.2 but before that I wiped everything and installed old TWRP and made come back to 5.2
But as new build came out fast with fixes I flashed again TWRP with treble support and flashed 5.4 rom
My question is do I need to do any step here explained or not?
Everything working fine here, TWRP saw and flashed vendor partition.
Thanks for answer in advance
Click to expand...
Click to collapse
I suggest you follow steps in part 1 again so that you can clean flash AEX 5.4 04/16 build.
Further can you advice best way to flash Oreo zui and revert back to latest AEX? I assume bootloader gets locked when you flash back to Oreo zui? Do advice.
Will flashing the mentioned zips on AEX 5.4 do any harm ? It's official one and treble TWRP only.
lokendra17 said:
First flash,factory2vender zip....
And then flash new twrp.img
Click to expand...
Click to collapse
Naveenjain said:
+1
Click to expand...
Click to collapse
need to do full wipe before flash rom?
ERHAN53 said:
need to do full wipe before flash rom?
Click to expand...
Click to collapse
No need to full wipe...you can dirty flash aex rom over 11/04 built
---------- Post added at 09:50 AM ---------- Previous post was at 09:44 AM ----------
ashwath230 said:
Will flashing the mentioned zips on AEX 5.4 do any harm ? It's official one and treble TWRP only.
Click to expand...
Click to collapse
No...it will not do any harm....it only rename /factory partition to /vendor partition..By factory2vendor.zip
Thinking of buying one of these. Has anyone flashed a Pie GSI on it?
I tried. But none are working. Just bootloops. But i only tried in twrp. Havent tried flasing in fastboot
ebautista said:
I tried. But none are working. Just bootloops. But i only tried in twrp. Havent tried flasing in fastboot
Click to expand...
Click to collapse
Should be working with fastboot, since the TWRP doesn't have treble necessary add one to flash treble ROMs.
champagne66601 said:
Should be working with fastboot, since the TWRP doesn't have treble necessary add one to flash treble ROMs.
Click to expand...
Click to collapse
You sure? Have you tried? One of the dev here in forum tried to compile a rom but failed. As the dev observed, the problem is rn7 system partition is in system_root/system and not in /system. This might cause major issue
UPDATE: I tried installing GSI images Pixel Experience and PHH's GSI through fastboot. No go. Now I am wondering , what's the point of treble in this device?
champagne66601 said:
Should be working with fastboot, since the TWRP doesn't have treble necessary add one to flash treble ROMs.
Click to expand...
Click to collapse
Yea, why would you say that? You just need to factory reset and then flash a system image to the system partition.
Is the system partition not listed when you switch over to the image installer section?
Sucessfully Flashed 4-5 GSI ROMS and working on my phone.But there are quite a few bugs in it.
letsmakecakes said:
Sucessfully Flashed 4-5 GSI ROMS and working on my phone.But there are quite a few bugs in it.
Click to expand...
Click to collapse
Can you share your procedure, twrp if not flashed in fastboot rom version, device storage and ram? I have tried few gsi images but not successful.
Can you also share bugs you encountered?
Any updates?
Download A/AB GSI and follow procedure on XDA
Thanhbat said:
Download A/AB GSI and follow procedure on XDA
Click to expand...
Click to collapse
And or install dm-verity disabler coz some gain requires decrypted.
I ended up buying a Redmi Note 7 Pro (Chinese variant). I'm unlocking the bootloader in about 3 hours here.
Successfully installed ASOP GSI on my redmi note 7 pro
Steps:
1)Install TWRP
2)Wipe Cache , Data , Dalvik Cache
3) Reboot to recovery
4) Install GSI
5) Reboot to recovery
6) Format Data
7) Reboot to system.
NOOB FRIENDLY? yea I guess so!
Thanks to @erfanoabdi for porting Android Q GSIs, OEM GSIs, etc......
NB: I don't know if other developer's GSIs would work or not.. Or even this would work for you.. It did for me for Q.. Try at your own risk.. Don't blame anyone if you made a mess! And i'm not a dev.. so.. there's no use of reporting bugs to me... although you can comment it so that someone might just maybe knowing how to help you!
Things You'll need
1. Unlocked bootloader
2. Custom Recovery (TWRP preferably)
3. Total backup (in case something goes wrong)
4. Treblized ROM(Most ROMs for Tulip are basically Treble Supporting)
5. Vendor(I strongly recommend Xiaomi.eu Android 9 Vendor! LINK: https://sourceforge.net/projects/xi...eu_multi_HMNote6Pro_9.4.25_v10-9.zip/download )
6. GSI of your Choice from https://mirrors.lolinet.com/firmware/gsi/
(PLEASE NOTE THAT TULIP ONLY SUPPORTS ARM64 A ONLY GSIs)
7. IF AND ONLY IF YOU'RE FLASHING ERFAN'S GSI THEN YOU NEED TO FLASH PERMISSIVERv2 AFTER FLASHING ANY GSI BE IT P OR Q.. AND IF YOU'RE FLASHING ANDROID Q GSI YOU NEED TO FLASH FIXZYGOTEv2 AS WELL
Q: How to make vendor Lonely? / How to install vendor alone?
A: Flash the Xiaomi.EU pie ROM and wipe dalvik,cache, system.. Don't wipe Vendor!!
Steps To Follow
1. Flash the ROM [Xiaomi.eu Based on Android 9 PIE]
2. Wipe Dalvik, Cache, System. DO NOT WIPE VENDOR
3. Now Flash the Genric System Image /GSI/ of your choice.
4. If and only if you're flashing Erfan's GSIs, FLASH PERMISSIVERv2 AFTER FLASHING ANY GSI BE IT P OR Q.. AND IF YOU'RE FLASHING ANDROID Q GSI YOU NEED TO FLASH FIXZYGOTEv2 AS WELL
5. Although in some cases when GSIs did not boot i flashed the latest Genom Kernel 4.4.180 and it seemed to boot up properly!
6. Reboot!
NB: There are bugs.. a lot... so you'll probably need the backup you previously created... Just sayin'....
Simply hit the thanks button..
No no no... pleaseeee...:good::angel:
Aha
Hi, one question, what recovery need?. I try some but when flash permisiver= error dont mount system. Good guide and thanks
fratletimac said:
Hi, one question, what recovery need?. I try some but when flash permisiver= error dont mount system. Good guide and thanks
Click to expand...
Click to collapse
Um... I used the twrp_v6 from the telegram group and it did work! Hope this helps!
https://t.me/tulip_updates/1014
Is this vendor can boot Irfan oxygen os GSI?
Anyone using any GSIs?
Thanks, goo help!
Probably not for me ??
Hi guys
Anyone able to boot PHH AOSP Treble A10 with Oxygen OS Stock vendor?*( tried unable to boot,since our device have treble support)
can anyone let me know the procedure?
roshan2989 said:
Hi guys
Anyone able to boot PHH AOSP Treble A10 with Oxygen OS Stock vendor?*( tried unable to boot,since our device have treble support)
can anyone let me know the procedure?
Click to expand...
Click to collapse
Wipe /data, /system, flash ROM, reboot to bootloader, wipe /data and reboot to system. Do not be encrypted.