Hey, I'm new to android modding and I decided to reinstall lineage os by doing wipe and flashing the rom again, and now it still asks for password, when I enter it, it's stuck in bootloop.
EDIT: Ok, I managed to flash stock but, I'm still interested, when I'll use Lineage OS, how can I reinstall it if I see a problem?
Long story short, all you really need to fully wipe your device according to the instructions. Did you flash GApps before booting System? You should also read through the dedicated LOS thread here.
I have recently noticed the potential of the A/B partition system in Mi A1. Is it possible to flash the rom only on one partition? Is the rom flashed onto both the partitions(via TWRP)?
I've installed two systems long time ago, LAOS 14.1 and Stock December Oreo, i can see both bootanimations (with a Slot change from TWRP), LAOS can boot normally, Android One can boot BUT you can only see a black screen with a lot of errors (like, Android System Stopped etc.), So at least you can use just one System, maybe there's a workaround, i don't know.
Sent from my Mi A1 using XDA Labs
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?
My first install is success but after I setting all and add fingerprint and pin code, after few reboot, it show my pin code is wrong and can't fix it, dont know where is the problem :crying:
Second time I reinstall the official 9.0.17, then when I wipe darik cache and install havoc 3.0 + twrp, when reboot to system, it is oxygen os also, why? It works at first time
So have anyone can give me the step for installation?
Based on 9.0.17 op6t international
ArlenCheng said:
My first install is success but after I setting all and add fingerprint and pin code, after few reboot, it show my pin code is wrong and can't fix it, dont know where is the problem :crying:
Second time I reinstall the official 9.0.17, then when I wipe darik cache and install havoc 3.0 + twrp, when reboot to system, it is oxygen os also, why? It works at first time
So have anyone can give me the step for installation?
Based on 9.0.17 op6t international
Click to expand...
Click to collapse
Same thing happened to me except that I didn't change the pin code that was there before I flashed it. It just went bad and then things went downhill from there.
What did you end up using?
ArlenCheng said:
Second time I reinstall the official 9.0.17, then when I wipe darik cache and install havoc 3.0 + twrp, when reboot to system, it is oxygen os also, why? It works at first time
Click to expand...
Click to collapse
iconoclasthero said:
What did you end up using?
Click to expand...
Click to collapse
Fair warning, up front, I don't use Havoc. To the OP, the 6T is a A/B device, since it booted back into OOS, it means you didn't have Havoc on both slots. Havoc was only on one, OOS on the other. Havoc failed to boot, so the Phone booted the other slot, which was OOS. Having different operating systems on the two slots generally will cause issues. Different versions is not an issue (But they should both be OOS, or both Havoc).
This is how I flash ROMs.
Hey, I have a Delaware TJ!
OhioYJ said:
Fair warning, up front, I don't use Havoc. To the OP, the 6T is a A/B device, since it booted back into OOS, it means you didn't have Havoc on both slots. Havoc was only on one, OOS on the other. Havoc failed to boot, so the Phone booted the other slot, which was OOS. Having different operating systems on the two slots generally will cause issues. Different versions is not an issue (But they should both be OOS, or both Havoc).
This is how I flash ROMs.
Click to expand...
Click to collapse
Thanks for the tip on the A/B. I was eventually walked through it by someone very helpful...and sent me some files.
Hey y'all, I've been away from the development community and tinkering with this device, work and life got in the way. I've been running a custom rom (sky dragon) and I believe it's based off 9.013 Android for over a year now. It's a great custom rom but it's time for something different.
I'd like to flash the latest and greatest stock oxygen OS which is now Android v10. Being a longtime pixel user, I'm very comfortable updating via fastboot. I was wondering if I downloaded the full ROM from oneplus' website and used the flash-all. bat method if that would be a smooth way to cleanflash the device. I'll make sure to back up everything I need so wiping the device entirely is no issue.
Thanks!
I personally prefer the Fastboot ROMs it will do both slots at once.
OhioYJ said:
I personally prefer the Fastboot ROMs it will do both slots at once.
Click to expand...
Click to collapse
can I flash the latest stock fastboot ROM coming from Android 9 though?
You'll have to choose reset everything option in the factory recovery for it to boot (under advanced IIRC) to get it to boot. Otherwise it will most likely just keep booting to recovery. Thats what happens when you go from a custom ROM to a OOS too.
OhioYJ said:
You'll have to choose reset everything option in the factory recovery for it to boot (under advanced IIRC) to get it to boot. Otherwise it will most likely just keep booting to recovery. Thats what happens when you go from a custom ROM to a OOS too.
Click to expand...
Click to collapse
I figured it wouldn't be a smooth process!!! So if I fastboot flash the latest Android 10 build from a custom Android 9, I'll boot loop into recovery but choosing "reset everything" should allow me to boot into the OS? I'll give it a shot! thanks.