Could anybody explain how to flash GSi on treble. i will describe what steps i did
1) Flashed Project_Treble_v1.1-Axon7-by-NFound
2)Flashed Havoc GSI Arm64 Aonly.img as system image
3)before reboot an error showed , NO OS DETECTED but after reboot stuck on a Tiny penguin logo . Waited for 10 minutes nothing happened
What i have to do to get it work
I'm not sure with this one.
I've read and reread posts here regarding this, I've seen other people in your position with the "No Os detected" after the install, I need to delve into this more.
From what I've read, did you add vendor partition?
I read through the steps here
https://forum.xda-developers.com/axon-7/development/nf-t3826885
steps
Requirements:
- Unlock bootloader
- Installed patch EDL to add /vendor part. 800Mb
- Installed TWRP 3.2.1-8 - TREBLE
How to install:
- Format /system, /data and /cache, wipe /vendor
- Install Treble flashable zip package Project_Treble_v1.0-by-NFound
- Install GSI .img in /system part.
- Reboot
I hope this helps
Instructions are from NFounds post
Thank you NFound
alwynjoshy said:
3)before reboot an error showed , NO OS DETECTED but after reboot stuck on a Tiny penguin logo . Waited for 10 minutes nothing happened
Click to expand...
Click to collapse
NO OS DETECTED is normal on GSI.
You flashing filesystem image (.img) over system partition and twrp won't be aware of changes to partitions until reboot.
alwynjoshy said:
What i have to do to get it work
Click to expand...
Click to collapse
Try LOS15.1 base and flash it again.
I tried HavocOS Oreo GSI 08/19 and it's working for now.
I didn't try Pie version of Havoc on LOS15.1.
Please, report, if you still have a call bug (not receiving incoming calls) . VoLTE may not work on GSI, I'm not even sure if it's working on LOS15.1.
xerocopy said:
NO OS DETECTED is normal on GSI.
You flashing filesystem image (.img) over system partition and twrp won't be aware of changes to partitions until reboot.
Try LOS15.1 base and flash it again.
I tried HavocOS Oreo GSI 08/19 and it's working for now.
I didn't try Pie version of Havoc on LOS15.1.
Please, report, if you still have a call bug (not receiving incoming calls) . VoLTE may not work on GSI, I'm not even sure if it's working on LOS15.1.
Click to expand...
Click to collapse
On Treble havoc i have call issue, What if try HavocOS Oreo GSI 08/19 with Los 15.1 base, would be that free from call bug
Syberclone said:
From what I've read, did you add vendor partition?
I read through the steps here
https://forum.xda-developers.com/axon-7/development/nf-t3826885
steps
Requirements:
- Unlock bootloader
- Installed patch EDL to add /vendor part. 800Mb
- Installed TWRP 3.2.1-8 - TREBLE
How to install:
- Format /system, /data and /cache, wipe /vendor
- Install Treble flashable zip package Project_Treble_v1.0-by-NFound
- Install GSI .img in /system part.
- Reboot
I hope this helps
Instructions are from NFounds post
Thank you NFound
Click to expand...
Click to collapse
Actually i am stuck in tiny Penguin ? logo, Tried the all steps you said, do i have to do any specific steps in Mount partition?
alwynjoshy said:
On Treble havoc i have call issue, What if try HavocOS Oreo GSI 08/19 with Los 15.1 base, would be that free from call bug
Click to expand...
Click to collapse
I don't know, you need to try. If you will have same problem like on PT 1.1 (you receiving calls on first boot and VoLTE works, but loosing ability to receive calls and VoLTE doesn't work after reboot), we could blame IMS service/VoLTE.
Current LOS 15.1 is capable to use GSI roms and it's better to use it because Project Treble made by NFound may not be updated anymore. It has also a fix for AK4490.
Try with LOS15.1 or change GSI rom.
Before you start, make sure that your vendor partition is created from the end of the system partition and it has 512mb size.
Use Party 0.5 tool by OKI in TWRP by flashing his zip or flash TWRP Labs by Oki which contain Party tool.
Thanks Oki for such a wonderful tools.
xerocopy said:
I don't know, you need to try. If you will have same problem like on PT 1.1 (you receiving calls on first boot and VoLTE works, but loosing ability to receive calls and VoLTE doesn't work after reboot), we could blame IMS service/VoLTE.
Current LOS 15.1 is capable to use GSI roms and it's better to use it because Project Treble made by NFound may not be updated anymore. It has also a fix for AK4490.
Try with LOS15.1 or change GSI rom.
Before you start, make sure that your vendor partition is created from the end of the system partition and it has 512mb size.
Use Party 0.5 tool by OKI in TWRP by flashing his zip or flash TWRP Labs by Oki which contain Party tool.
Thanks Oki for such a wonderful tools.
Click to expand...
Click to collapse
Actually i was on NFound's 800Mb partition and i flashed oki's version and its showed updating partition table after when i verify i saw 500mb Partition, Would that steps cause any issues?
alwynjoshy said:
Actually i was on NFound's 800Mb partition and i flashed oki's version and its showed updating partition table after when i verify i saw 500mb Partition, Would that steps cause any issues?
Click to expand...
Click to collapse
Not sure about Project Treble 1.0, it may not install on 512mb vendor. 1.1 should install w/o problems.
512mb vendor is required for LOS15.1 or LOS16.0.
Edit: If you had any files on data partition, they are probably lost.
In NFounds post there is this
"Our Axon 7 is an A-only device. This means that regarding the GSI images (GSI = Generic System Image) to be used, you need to get ARM64 and A-Only system images"
It looks like 2 imgs are required? Arm64 and A-only, unless these 2 are integrated?
Syberclone said:
In NFounds post there is this
"Our Axon 7 is an A-only device. This means that regarding the GSI images (GSI = Generic System Image) to be used, you need to get ARM64 and A-Only system images"
It looks like 2 imgs are required? Arm64 and A-only, unless these 2 are integrated?
Click to expand...
Click to collapse
You need arm64 A-only image. It is one .img file and it need to installed on system partition. It's similar to updating TWRP from recovery.
A/B is for devices which have two /system partitions and in case of problems, you could go back from B to A system if device won't boot. Cool feature, sadly, not for us.
xerocopy said:
You need arm64 A-only image. It is one .img file and it need to installed on system partition. It's similar to updating TWRP from recovery.
A/B is for devices which have two /system partitions and in case of problems, you could go back from B to A system if device won't boot. Cool feature, sadly, not for us.
Click to expand...
Click to collapse
I have question, by manufacturer we don't have the vendor partition, the developer created the partition for vendor then couldn't they create A, B partitions also?
alwynjoshy said:
I have question, by manufacturer we don't have the vendor partition, the developer created the partition for vendor then couldn't they create A, B partitions also?
Click to expand...
Click to collapse
I'm not sure, Seamless-update is really low-level feature, deeper than bootstack, kernel etc. Repartitioning doesn't make a sense.
Because Axon 7 was made before the feature was introduced by Google, we won't get it.
Did you try LOS15.1? Someone mention VoLTE is working LOS.
Here is Installation guide for LOS 15.1 made by Oki
xerocopy said:
I'm not sure, Seamless-update is really low-level feature, deeper than bootstack, kernel etc. Repartitioning doesn't make a sense.
Because Axon 7 was made before the feature was introduced by Google, we won't get it.
Did you try LOS15.1? Someone mention VoLTE is working LOS.
Here is Installation guide for LOS 15.1 made by Oki
Click to expand...
Click to collapse
No Volte label on status bar but on caller screen HD symbol shows. I flashed custom kernal and went to boot loop. Bro thanks for your reply
xerocopy said:
I'm not sure, Seamless-update is really low-level feature, deeper than bootstack, kernel etc. Repartitioning doesn't make a sense.
Because Axon 7 was made before the feature was introduced by Google, we won't get it.
Did you try LOS15.1? Someone mention VoLTE is working LOS.
Here is Installation guide for LOS 15.1 made by Oki
Click to expand...
Click to collapse
Where did you get all that bull?
A-B updates are as simple as a secondary system partition, and all that's needed is a fastboot command to select the active patrtition, which is present in B12 (not in previous N builds though). Of course if the system partition is still 5gb then you'll have like 10.5 gb used by vendor and system, plus all the other small partitions like bt and stuff.
Why exactly is a low level feature, deeper than bootstack?? It's a damn partition
I talked to djkuz before and he told me all this. At least I have a source.
"Because Axon 7 was made before the feature was introduced by Google, we won't get it."
Then what about Treble?
Related
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
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 PRO
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 belowTWRP,
*Reboot To TWRP,
*Flash ROM,
+ GApps / + Magisk etc
* Reboot.
*Enjoy :fingers-crossed:
Downloads:
Factory2Vendor_pro: https://androidfilehost.com/?fid=746010030569969371
TWRP for /factory renamed as /vendor roms https://github.com/cosmedd/android_...eases/download/20180413/20180413_recovery.img
** REVERTING BACK to NORMAL aka renaming /vendor back to/factory **
Instructions:
*Flash "Vendor 2Factory_plus.zip",
*Flash OFFICIALTWRP,
*Reboot TWRP,
*Flash ROM,
+ GApps / + Magisk etc
*Reboot.
*Enjoy :fingers-crossed:
Downloads:
Vendor2Factory_pro: https://androidfilehost.com/?fid=673956719939835215
https://twrp.me/zuk/zukz2row.html
** REVERTING BACK to NORMAL aka renaming /vendor back to/factory **
Instructions:
*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:
Reserved
You'll be able to use above method for Latest AEX coming soon by Davidevinavil and all the ROMs compiled using the latest sources as per by Zuk-devs
Links added, enjoy
thx
Can we make this procedure opposite? i.e. flash first twrp and than that zip? I normally flash twrp with official twrp app
1 or 2 should I do if I want to flash from the latest zui to AEX5.4 ,thx
thanks
Thanks zuk developer
I just tryed to flash Vendor 2Factory_pro..zip but I get following error "failed to mount '/vendor' (invalid argument)". I was in previous version 5.4 (1104). After restart, it does not load the rom but the bootloader. problem is the devices is not recognized under "adb devices" when in bootloader. Any ideas will be very welcome
darquesp said:
I just tryed to flash Vendor 2Factory_pro..zip but I get following error "failed to mount '/vendor' (invalid argument)". I was in previous version 5.4 (1104). After restart, it does not load the rom but the bootloader. problem is the devices is not recognized under "adb devices" when in bootloader. Any ideas will be very welcome
Click to expand...
Click to collapse
In bootloader (fastboot) you must use
fastboot -i 0x2b4c
ADB works in twrp or with system . Just follow this guide .
mar.ur said:
In bootloader (fastboot) you must use
fastboot -i 0x2b4c
ADB works in twrp or with system . Just follow this guide .
Click to expand...
Click to collapse
I installed the vendor, but the twrp is only black.
Any solution?
JustBr said:
I installed the vendor, but the twrp is only black.
Any solution?
Click to expand...
Click to collapse
Did you install latest twrp after flashing f2v
mar.ur said:
In bootloader (fastboot) you must use
fastboot -i 0x2b4c
ADB works in twrp or with system . Just follow this guide .
Click to expand...
Click to collapse
Thanks. I flashed last rom and after that updated twrp with twrp app and now I get no error about partitions.
I thought that to flash a twrp image with adb, I should do into fastboot mode. Can I also do it into recovery or system just with command : fastboot -i 0x2b4c flash recovery twrp.img?
Which guide do you mean? I checked on this thread and could not find a guide about adb.
Many thanks!
You can install twrp.img in any twrp .Just go to install/ install image and choose new twrp.img , then mark recovery and flash it .
mar.ur said:
Did you install latest twrp after flashing f2v
Click to expand...
Click to collapse
my twrp and 3.1, downloaded a recovered image(new twrp ), select image, recover and flash .. and the screen continues black, do not start twrp ... !!!!
JustBr said:
my twrp and 3.1, downloaded a recovered image(new twrp ), select image, recover and flash .. and the screen continues black, do not start twrp ... !!!!
Click to expand...
Click to collapse
I test a lot of systems . Last I was on mokee 7.1.2 with redwolf twrp with vendor partition ( not the latest ) . I install f2v.zip then twrp https://github.com/cosmedd/android_...eases/download/20180413/20180413_recovery.img . After that restart to recovery . Finally install to the latest Aex . No problems at all . First of all start with 2018.03.11 twrp , then install f2v.zip , 2018.04.13 twrp , restart to recovery and install aex or rr . That's all
Hy bro,
Can you send me the twrp version 2018.03.11 link?
failed to mount 'vendor'
After following the previous steps. TRWP start to show "failed to mount 'vendor' (invalid argument)'" message. I'm able to install the AEX 5.4, but the google apps do not crashes.
Any help?
Solved: wrong TWRP.
Nice boot animation
JustBr said:
Hy bro,
Can you send me the twrp version 2018.03.11 link?
Click to expand...
Click to collapse
https://github.com/cosmedd/android_...eases/download/20180311/20180311_recovery.img
mar.ur said:
https://github.com/cosmedd/android_...eases/download/20180311/20180311_recovery.img
Click to expand...
Click to collapse
Last help, I do everything by the pc, in fasboot mode ? or last twrp by his flash (twrp).
Firstly, my phone isn't hard-bricked. I'm able to load different versions of the TWRP recovery and access Fastboot without any problems. I'm also pretty comfortable using adb to push, sideload, access fastboot, recovery , etc. so please feel free to throw out any suggestions that might help me resolve my issue. (Note:I'm unable to find the stock recovery on OnePlus's support page anymore, I recall they always had the option to download the stock recovery just below the download option for the stock ROM, so I haven't been able to try sideloading after formatting with the stock recovery.)
My OnePlus 5 was running stock Oreo and I'd been meaning to upgrade to Lineage 16.0 (Pie) or any other Pie ROM really. I booted into TWRP (3.2.3-0 - Oreo firmware) and wiped everything other than USB storage and formatted data too as my previous Oreo installation was encrypted. Then, I downloaded codeworkxx's 9.0.3 firmware for OnePlus 5 and pushed it to my phone using adb. I flashed the firmware successfully, rebooted into Bootloader/fastboot; and flashed the Android Pie version of TWRP recovery ( https://sourceforge.net/projects/cheeseburgerdumplings/files/16.0/cheeseburger/ ) and was able to successfully boot back into the recovery. Since then, I've tried to flash multiple different Pie ROMs (Pixel Experience, Lineage 16.0, stock OOS official build - 9.0.3 , Beta OOS build OpenBeta26) (clean flashing always) but always ended up with a bootloop with the boot animations in all the ROMs. I've even tried flashing them with Magisk-v18.0 but that doesn't help either. I've waited for 15 min with each boot for the different ROM's (ending up in bootloops) and on rebooting back to TWRP, I've always found that irrespective of ROMs, the only folder that's created in Internal Storage is 'obb' and it is an empty folder. I've even tried sideloading OOS 9.0.3 (official build) via TWRP and that still ends up in a bootloop with the obb folder in Internal Storage being the only thing created. Also, flashing the boot.img recovery in the stock ROM zip files leads to a blank screen with a white LED that tries to install Qualcom drivers, so I just reflashed TWRP and am back to where I started.
That pretty much sums up my problem here. Kindly throw suggestions at me to help fix my problem' I've searched the forums but most of the bootloop issues I've found and read are about unsuccessful firmware flashes (not the case with me as I've explained above) or dirty flashes (again, not the case with me as I always cleanflash).
Thanks!
You should be focusing on getting stock OOS back on before trying custom rom. Have you tried rolling back to 5.1.7 Oreo? Sometime it better to go back to square 1 and try again.
Z-Blade said:
You should be focusing on getting stock OOS back on before trying custom rom. Have you tried rolling back to 5.1.7 Oreo? Sometime it better to go back to square 1 and try again.
Click to expand...
Click to collapse
Thank you for replying!
I successfully flashed the 5.1.7 firmware and Oreo-TWRP-recovery and was able to install Lineage OS 15.1 and boot it up properly. I'm unable to find a link for previous versions of OOS to test whether or not 5.1.7 would work. Do you know where I can find a link?
Thanks again!
BigTurboSkipper said:
Thank you for replying!
I successfully flashed the 5.1.7 firmware and Oreo-TWRP-recovery and was able to install Lineage OS 15.1 and boot it up properly. I'm unable to find a link for previous versions of OOS to test whether or not 5.1.7 would work. Do you know where I can find a link?
Thanks again!
Click to expand...
Click to collapse
It's within the guides section https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190
strongst said:
It's within the guides section https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190
Click to expand...
Click to collapse
Thanks!
So the Lineage 15.1 flash worked fine but OOS 5.1.7 still leaves me with a bootloop and the obb folder as detailed in my first post. I'm unsure as to how to proceed.
BigTurboSkipper said:
Thanks!
So the Lineage 15.1 flash worked fine but OOS 5.1.7 still leaves me with a bootloop and the obb folder as detailed in my first post. I'm unsure as to how to proceed.
Click to expand...
Click to collapse
What was your LAST stock oxygenOS version that was installed your device prior to 5.1.7?
strongst said:
What was your LAST stock oxygenOS version that was installed your device prior to 5.1.7?
Click to expand...
Click to collapse
I can't recall exactly, but it was most probably OB23/24 (Oreo)
BigTurboSkipper said:
I can't recall exactly, but it was most probably OB23/24 (Oreo)
Click to expand...
Click to collapse
Can you please try to flash 5.1.4 stock oxygenOS rom and the 5.1.7 after it, then magisk and reboot to the os?
Make sure you have an old Oreo compatible recovery like this https://drive.google.com/file/d/1DrEMydZfQxC_eWx1W-OlASo8H7okXNTQ/view?usp=drivesdk
strongst said:
Can you please try to flash 5.1.4 stock oxygenOS rom and the 5.1.7 after it, then magisk and reboot to the os?
Make sure you have an old Oreo compatible recovery like this https://drive.google.com/file/d/1DrEMydZfQxC_eWx1W-OlASo8H7okXNTQ/view?usp=drivesdk
Click to expand...
Click to collapse
Successfully flashed but still results in a bootloop
BigTurboSkipper said:
Thanks!
So the Lineage 15.1 flash worked fine but OOS 5.1.7 still leaves me with a bootloop and the obb folder as detailed in my first post. I'm unsure as to how to proceed.
Click to expand...
Click to collapse
Lineage 15.1 (official) boots successfully but without radios working... I tried reflashing Firmware-5.1.7 but that does not help; not sure how to fix this. Could it be a firmware issue with installing Pie ROMs? But then again, OOS Oreo doesn't boot either - still ends up in a bootloop
My only suggestion ...
BigTurboSkipper said:
Lineage 15.1 (official) boots successfully but without radios working... I tried reflashing Firmware-5.1.7 but that does not help; not sure how to fix this. Could it be a firmware issue with installing Pie ROMs? But then again, OOS Oreo doesn't boot either - still ends up in a bootloop
Click to expand...
Click to collapse
Greetings! I got your private message, but I haven't read it yet. Sorry, very busy today. However, I can make the following suggestion to get your device back into original working order.
Have a look at this link on xda. It's for an unbrick tool, which I've used numerous times with great success.
https://forum.xda-developers.com/oneplus-5/how-to/unbrick-tool-oneplus-5-t3648169
This tool will put your device back into its original condition, with original OOS.
Let me know if it works for you.
Peter
BigTurboSkipper said:
Lineage 15.1 (official) boots successfully but without radios working... I tried reflashing Firmware-5.1.7 but that does not help; not sure how to fix this. Could it be a firmware issue with installing Pie ROMs? But then again, OOS Oreo doesn't boot either - still ends up in a bootloop
Click to expand...
Click to collapse
OxygenOS also needs a formatted internal storage, otherwise bootloop will pop up
strongst said:
OxygenOS also needs a formatted internal storage, otherwise bootloop will pop up
Click to expand...
Click to collapse
Definitely! I've always been clean flashing ROMs (Wiping Internal Storage, Data, System, Dalvik Cache, Cache + Wiping/Formatting Data to factory reset ) for each trial!
BigTurboSkipper said:
Definitely! I've always been clean flashing ROMs (Wiping Internal Storage, Data, System, Dalvik Cache, Cache + Wiping/Formatting Data to factory reset ) for each trial!
Click to expand...
Click to collapse
Wiping system, data, cache, Installing 5.1.4, then magisk, then format internal storage, then boot os should not cause a bootloop
What's your twrp recovery? Did you tried mine?
strongst said:
Wiping system, data, cache, Installing 5.1.4, then magisk, then format internal storage, then boot os should not cause a bootloop
What's your twrp recovery? Did you tried mine?
Click to expand...
Click to collapse
That's exactly what I'm doing. I've tried using codeworkxx 's versions, blu_spark TWRP versions and yours too!
PeterGuru said:
Greetings! I got your private message, but I haven't read it yet. Sorry, very busy today. However, I can make the following suggestion to get your device back into original working order.
Have a look at this link on xda. It's for an unbrick tool, which I've used numerous times with great success.
https://forum.xda-developers.com/oneplus-5/how-to/unbrick-tool-oneplus-5-t3648169
This tool will put your device back into its original condition, with original OOS.
Let me know if it works for you.
Peter
Click to expand...
Click to collapse
Thank you for replying!
The tool doesn't detect my device whatsoever - I have system-wide adb & fastboot set up (to use from any folder or path) yet the device is not detected in fastboot mode or recovery mode.
How do you use it?
Thanks!
BigTurboSkipper said:
Thank you for replying!
The tool doesn't detect my device whatsoever - I have system-wide adb & fastboot set up (to use from any folder or path) yet the device is not detected in fastboot mode or recovery mode.
How do you use it?
Thanks!
Click to expand...
Click to collapse
You need to put your device into MSM Download mode. It's simple. Power off your device. Press and hold the Volume UP key for about 8-10 seconds and, while continuing to hold the Volume UP key, plug in your device to your computer via USB. Open the MSM Tool and press Start.
That's it.
It takes about 3-5 minutes for the tool to complete the unbrick process.
Peter
Thank you! I was able to successfully use the unbrick tool to reset to OOS 4.5.8 Nougat. I'm going to try stepping all the way up to Pie now!
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 ??