Related
Hi
I have problems to install LineageOS on my new OnePlus6. I tried to install LineageOS with the guide on https://wiki.lineageos.org/devices/enchilada/install. If I follow the guide exactly step by step no OS is starting and I can't boot into recovery because (I think) twrp isn't installed (just black screen with blue led). But also if I first boot twrp with fastboot boot 'twrp.img' and after install the twrp.zip, no OS is starting after sideload or flash the 'lineageos.zip'. I think, the install doesn't finish correct. In the terminal on my debian I can see, that the installprocess ends at 47%. But I'm not really shure if this is the problem and if it is, how I can solve it. Probably in this thread the same problem is described: https://forum.xda-developers.com/oneplus-6/help/lineage-doesnt-boot-black-screen-light-t3958351 Unfortunately no solution is available in the thread.
Now I flashed the stockrom (https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665) and have done all updates but don't know how I can install twrp and after LineageOS. I hope somebody can help me. Thanks
Do you have the latest ADB version? Instead of sideloading you can try just transferring the zip files (with e.g. "adb push lineageos.zip /sdcard/") and then installing directly from TWRP.
Make sure you do all the wipes / formats mentioned in the guide. Transfer and flash the lineageos.zip. Then directly after you should flash the twrp.zip Then reboot back into recovery and flash Magisk / Gapps etc if needed. Then finally reboot to system.
Also read this guide if you haven't already as it explains a lot about how flashing ROMs on OnePlus 6 is different to many other older phones.
Hi and thank you makeyourself
I tried the following steps:
1. starting fastboot
2. fastboot boot twrp-3.3.1-2-enchilada.img -> twrp starting up
3. adb push twrp-installer-3.3.1-2-enchilada.zip /sdcard/ -> transfer ok
4. adb push lineage-16.0-20190922-nightly-enchilada-signed.zip /sdcard/ -> transfer ok
5. in twrp Wipe -> Format Data
6. in twrp Advanced Wipe -> System
7. in twrp install lineage-16.0-20190922-nightly-enchilada-signed.zip
8. in twrp install twrp-installer-3.3.1-2-enchilada.zip
9. reboot to recovery
After this steps I got the same problem as before. Before the reboot to recovery, twrp showed the message "no OS installed". So I think, the zip weren't installed correctly. Now, I have the black screen with the blue led. Can you find out what I did wrong?
Edit: Now, I can't also boot twrp. Also if I do a fastboot boot twrp-3.3.1-2-enchilada.img nothing happens.
Fastboot to twrp (newest blu spark should be fine, or black twrp)
Flash twrp zip
Reboot to twrp
Wipe data, cache.
Flash recommended oos
Flash twrp
Reboot to twrp
Flash recommended twrp (yes...... Again)
Flash twrp (yes... Again, recovery is lost after rom Flash ALWAYS)
Reboot to twrp
Flash LOS or any other custom rom
Flash twrp (rom Flash, so twrp is lost like I said)
Reboot to twrp
Flash magisk (IF ypu want magisk)
Flash gapps (IF ypu want gapps)
Flash kernel (IF I like to run another custom kernel)
Boot
Enjoy
Thank you whizeguy, I'll try this. But just one question about "Flash recommended oos". Which OxygenOS can I flash (this full OTA? https://www.xda-developers.com/oneplus-6-oneplus-6t-oxygenos-9014-906/) and why I have to do this? Sorry if it is a bad question.
You Flash The oxygen OS version that is recommended in Los thread, simple as that.
You have an a/b device, vendor partition (could be other files needed aswell, not 100 % sure) is needed to Flash custom, IF you did Amy research you'd finns some good info. Also for faster answers in The future: post your issue in the thread for LOS, that way you would get help from People Who uses it, knows The exact version you should use and what not
Hey whizeguy, thank you very much. Everything works perfect now. But why for heaven's sake do I have to flash oos and why the guide on the LineageOS site don't tell me this way?
Wow idk what happened here. Mistakenly replied to this thread. Apologies.
Hello!
I'm having quite a hard time figuring out what is happening on my new Oneplus 6.
The first time i flashed LineageOS 16 microg edition it booted but since i tried to restore stock ROM backup with TWRP it all went to hell.
Device immediately bricked, only booting to fastboot.
Had to use msm tool to unbrick. ( the first of so many times.... )
Then updated from settings to latest OOS 9.0.9.
unnlocked bootloader
and flashed again.
NO OS INSTALLED.
phone boots only in fastboot.
can't boot any recovery from fastboot. gives error.
if reboot to recovery blue led and black screen is all that i see.
only fix is msm.
From that point onwards i tried EVERY guide I could find (and recognize as valid of interest) here on xda, youtube, google.
Multiple times per guide.
here's an example of a "last resort" guide from https://forum.xda-developers.com/oneplus-6/how-to/guide-microg-oneplus-6-source-ligthway-t3874469
INSTALLATION TUTORIAL
Italic = recommended, but not mandatory. Do it if something doesn't work properly
0) DON'T RESTORE your apps until everything is set up, otherwise you'll have issues with GCM (getting instant notifications from messaging apps for example)
1) Reboot to blu spark TWRP
2) step deleted
3) Flash OOS
4) Flash TWRP
5) Reboot to recovery
6) Flash OOS
7) Flash TWRP
8) Reboot to recovery
9) Flash your custom ROM + TWRP + reboot to TWRP
10) Flash again your custom ROM + TWRP
11) Reboot to recovery
11 bis) Wipe data ("factory reset")
12) Flash Magisk
13) Reboot to system. It's just to make sure the installation worked.
... more on link
Click to expand...
Click to collapse
Tried also official lineage, SyberiaOS. Different previous version of the two (since I read in the lineage official thread others have this issue)
Basically at the point after flashing any of these roms results immediately in TWRP warning "no os is installed" at reboot attempt with or without re-flashing twrp after.
Then if rebooted just hangs on blue led. can't boot anything.
Meanwhile flashing OTAs + twrp results in bootable system.
Other things that i tried:
before unlocking BL update to latest OTA_34 -> 9.0.9, reboot, install again.
using mauronofrio twrp version https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3860815
Any ideas?
[SOLUTION]
If you're bricked follow this: https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
1 - Have last OOS installed in both slots
- update from settings, local update, latest OTA (Pie) from oneplus support site.- reboot, let it complete- apply again2 - Enable OEM Unlock in Developer options
3 - Boot to Fastboot and unlock bootloader:
Code:
fastboot oem unlock
4 - Once in OOS reboot to fastboot and boot twrp:
Code:
fastboot boot <twrp-img-name>.img
5 - Push twrp + custom rom:
Code:
adb push <custom-rom-name>.zip <twrp-zip-name>.zip /sdcard
6 - Flash twrp in twrp
7 - Reboot to recovery
8 - Wipe system and Data
9 - flash ROM
10 - flash twrp
[IMPORTANT]
11 - Tap Reboot to recovery then if it says No OS installed! tap home button! Don't reboot! reboot = brick = msmdownloadtool
12 - Go in advanced menu and select Fix Recovery Bootloop and swipe
13 - THEN TRY TO MOUNT /system.
IF YOU'RE UNABLE TO MOUNT /system APPLY AGAIN THE FIX AND REPEAT FROM STEP 714 - Reboot to recovery
It WILL stil say No OS installed but now you'll be able to reboot to recovery[/IMPORTANT]
15 - Once in recovery reboot to system.
If you've done everything correctly it won't complain again about no OS being installed and you'll get your rom up and running.16 - Let it reboot to system and complete first configuration
17 - Now you can reboot and flash every module you like from twrp.
That's it. Hope this'll spare nightmares and storage write life.
This is a bad phone .. I have it too
تم الإرسال من ONEPLUS A6003 باستخدام Tapatalk
But you seem (from post history) to be able to install ROMs :crying:
As most of those who try i guess.
Maybe my phone is somehow damaged
What some guides miss out is that you have to install everything twice. Once on slot A and once on slot B and after each install, verify what slot you are on before reboot and then check what slot you are on after reboot. I ran into issues flashing Havoc OS onto my phone too and figured it out in the end after so many times that I was in fact installing stuff twice on the same slot because it never switched over. I'll run you through the order I did things so hopefully you can follow.
-Use MSM Tool to revert everything back to stock and once the phone is booted, update to 9.0.9 either by downloading the update through the phone or by local upgrade if you have the file to hand. (remember to only have the OOS file present as any other OS in zip form crashes the local updater). You don't need to do this if you are already rocking stock Oxygen OS.
-Once the phone has restarted after the upgrade, let the post update procedure finish before continuing.
-Enter developer mode and enable OEM unlocking, Advanced Restart and USB Debugging. From here, reboot to bootloader.
-Plug your phone into the PC now and assuming you have fastboot setup ready on your PC, type 'fastboot oem unlock' and use the volume keys to select the option to unlock and press the power button to select.
-After the phone has completed it's wipe cycle, re-enable Advanced Restart and USB Debugging. The OEM unlock option should be greyed out as it's already been enabled. Make sure you don't add a pin code or password just yet as you will enable encryption which will make the next steps harder than it should be.
-Boot back to bootloader and type 'fastboot boot twrp.img' (or whatever you named it. Make sure that the image file is in the same folder you initiated cmd or powershell)
-Once booted into TWRP, flash blu_spark TWRP as that supports encryption apparently and is more stable than any other. To make sure that the script executed on both slots, hit reboot and check what slot you are on and tap the button for the other slot. Now reboot back to recovery, check you are on the other slot and flash it again.
-Now flash your 9.0.9 OOS zip followed by TWRP once on slot A and once on slot B while making sure you are on the other slot when doing it a second time. Remember that you have to re-flash TWRP after any flashable file that alters the boot partition before you reboot or you will undo all your work. Just make it habit that you re-flash it every time and you should be good.
-Once OOS and TWRP have been flashed on BOTH slots, reboot back to recovery and do the whole process again with your custom ROM (Remembering to flash TWRP before you reboot and checking which slot you are one before and after each flash).
-Once that has completed, reboot back to recovery and flash Magisk on each slot and GApps or MicroG if your ROM supports it. You don't need to re-flash TWRP after this but I do anyway to keep the habit lol.
-Entirely up to you, but before you reboot to your fresh new OS, you can wipe internal storage ONLY if you want all traces of your previous OS gone, but this will also remove personal files etc. I generally just head into TWRP file manager and delete the Android folder and keep the rest.
If you run into issues like crashes on your new OS, reboot to recovery and do a factory reset, but you will also need to re-flash Magisk again. GApps installs itself to system, so you won't need to re-flash that. MicroG does not and will need setting up again. One thing that took me a while to realise is that if you try rebooting while your USB is plugged into your PC, you will sometimes enter download mode, so only keep it plugged in when you need it for MSM Tool or to transfer files across.
I'm pretty sure I put everything down the way I did it and didn't miss anything, but it is late and I am half asleep. Will check back in the morning and double check with a fresh brain.
Many thanks for your exhaustive reply!
Will follow this tomorrow morning with a fresh brain
Fixed!
Now I'll write a guide for those in the same situation.
franticboe said:
Hello!
I'm having quite a hard time figuring out what is happening on my new Oneplus 6.
The first time i flashed LineageOS 16 microg edition it booted but since i tried to restore stock ROM backup with TWRP it all went to hell.
Device immediately bricked, only booting to fastboot.
Had to use msm tool to unbrick. ( the first of so many times.... )
Then updated from settings to latest OOS 9.0.9.
unnlocked bootloader
and flashed again.
NO OS INSTALLED.
phone boots only in fastboot.
can't boot any recovery from fastboot. gives error.
if reboot to recovery blue led and black screen is all that i see.
only fix is msm.
From that point onwards i tried EVERY guide I could find (and recognize as valid of interest) here on xda, youtube, google.
Multiple times per guide.
here's an example of a "last resort" guide from https://forum.xda-developers.com/oneplus-6/how-to/guide-microg-oneplus-6-source-ligthway-t3874469
Tried also official lineage, SyberiaOS. Different previous version of the two (since I read in the lineage official thread others have this issue)
Basically at the point after flashing any of these roms results immediately in TWRP warning "no os is installed" at reboot attempt with or without re-flashing twrp after.
Then if rebooted just hangs on blue led. can't boot anything.
Meanwhile flashing OTAs + twrp results in bootable system.
Other things that i tried:
before unlocking BL update to latest OTA_34 -> 9.0.9, reboot, install again.
using mauronofrio twrp version https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3860815
Any ideas?
[SOLUTION]
If you're bricked follow this: https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
1 - Have last OOS installed in both slots
- update from settings, local update, latest OTA (Pie) from oneplus support site.- reboot, let it complete- apply again2 - Enable OEM Unlock in Developer options
3 - Boot to Fastboot and unlock bootloader:
Code:
fastboot oem unlock
4 - Once in OOS reboot to fastboot and boot twrp:
Code:
fastboot boot <twrp-img-name>.img
5 - Push twrp + custom rom:
Code:
adb push <custom-rom-name>.zip <twrp-zip-name>.zip /sdcard
6 - Flash twrp in twrp
7 - Reboot to recovery
8 - Wipe system and Data
9 - flash ROM
10 - flash twrp
[IMPORTANT]
11 - Tap Reboot to recovery then if it says No OS installed! tap home button! Don't reboot! reboot = brick = msmdownloadtool
12 - Go in advanced menu and select Fix Recovery Bootloop and swipe
13 - THEN TRY TO MOUNT /system.
IF YOU'RE UNABLE TO MOUNT /system APPLY AGAIN THE FIX AND REPEAT FROM STEP 714 - Reboot to recovery
It WILL stil say No OS installed but now you'll be able to reboot to recovery[/IMPORTANT]
15 - Once in recovery reboot to system.
If you've done everything correctly it won't complain again about no OS being installed and you'll get your rom up and running.16 - Let it reboot to system and complete first configuration
17 - Now you can reboot and flash every module you like from twrp.
That's it. Hope this'll spare nightmares and storage write life.
Click to expand...
Click to collapse
i tried all the mentioned steps, nothing worked for me. Even i tried all the guides, here on xda and on youtube i am not able to boot my 1+6 it is getting booted to fastboot mode, after installing custom rom. But if i flash only OOS then it boots back properly.
But in case of a custom rom it boots back to fastboot mode, and then in the end msm tool is the last resort to lock bootloader and make it stock.
i tried all the mentioned steps, nothing worked for me. Even i tried all the guides, here on xda and on youtube i am not able to boot my 1+6 it is getting booted to fastboot mode, after installing custom rom. But if i flash only OOS then it boots back properly.
But in case of a custom rom it boots back to fastboot mode, and then in the end msm tool is the last resort to lock bootloader and make it stock.
Click to expand...
Click to collapse
If you are stuck on fastboot try
fastboot set_active other
then try rebooting recovery if fails try
fastboot boot pc-stored-twrp
I found changing the active slot via fastboot may unbrick it without msm. It all depends on what steps you actually take during installation.
For installing LOS try not flashing twrp after installation. Los comes with its own recovery. Anyway if it says no OS installed you HAVE to fix recovery bootloop.
So I have decided to create a Thread to share with you- all the Custom ROM GSI that I have tried till now. First off, let's begin with Pixel Experience. It has managed to retain the same smooth UI and user experience. Furthermore, it actually comes with a Dark Mode and not that dark grey hue that our device has to offer. Apart from that, there are few other features as well. However, since we are already running an Android One device, you wouldn't find much difference. With that said, check out the screenshots to experience this ROM in detail
How to Flash GSI ROM on Moto One Action
There are two methods for that, the fastboot command method and the TWRP Recovery method. I will be discussing the latter because via the fastboot commands Bootloader wouldn't even allow formatting the system for some strange reasons SO here is what needs to be done (and yes I won't be responsible for your bricked devices, if that happens :silly
Notes:
Download the Pixel Experience GSI ROM. A huge thanks to turbolukex5 for this GSI ROM.
Do remember to always download an ARM64 CPU architecture ROM with AB partition for Moto One Action.
Transfer this ROM to SDCard. Although we won't be formatting Internal Storage, yet it is always advisable to keep it in external storage like SD Card or Pendrive.
Steps to Follow:
Boot to TWRP and go to Wipe > Dalvik, Data and System.
Head over to SD Card and tap on Install Image (the bottom right button on your recovery).
Now flash the GSI ROM.
Once it gets flashed (2-3mins at max), go to Reboot and tap Recovery. You will get a message that NO OS is installed. IGNORE it and proceed with the reboot. You should NOT reboot to the system otherwise bootloop is guaranteed from my end
Reason for bootloop: WIth A/B partition devices like ours, there is no separate recovery partition. It is handled by the boot partition itself (that is why we boot the recovery rather than actually flashing itself). Now we will have to refresh the boot [partiton and for that, you will have to reboot the TWRP recovery. If you don't do so, system won't be able to recognize the boot partition (personal experience: tried many times and ended up in bootloop each time ).
Once you reboot to recovery, again head over to Reboot > System. This time you won't notice the NO OS message. The first time the device might reboot once or twice, that is completely normal.
That's it. Enjoy the New Pixel Experience on your Moto One Action
Next Up: Flashing the HavocOS GSI ROM.
Thank for sharing. Which gsi do you recommend? I mean based on stability and battery life. Also what camera app are you using?
I was waiting for something like this to appear! I've had many problems flashing GSIs I kinda just gave up LOL.
How can you install it with fastboot? And what can be done for the statusbar to accomodate the camera cutout?
mymagicmyhero said:
Thank for sharing. Which gsi do you recommend? I mean based on stability and battery life. Also what camera app are you using?
Click to expand...
Click to collapse
On stability and battery life, Pixel is the go-to ROM. I am saying this from my previous experience of using custom ROMs. I have tried many custom ROMs and Pixel always took the first position in battery life and stability. The main reason for that could be attributed to the fact that it is a trimmed down ROM with just the basic functionalities.
As far as camera goes, I tried a bunch of GCams but unfortunately have to give up on all as none of them worked. There is a GCam channel on the Telegram for Action/Vision and there are a lot of discussions going on and Gcams being shared over there. Check it out.
nztcs said:
I was waiting for something like this to appear! I've had many problems flashing GSIs I kinda just gave up LOL.
How can you install it with fastboot? And what can be done for the statusbar to accomodate the camera cutout?
Click to expand...
Click to collapse
Here are the commands needed for that. But if a GSI have a separate GApps package, then I don't think you could flash it via fastboot commands. This is because GApps comes in .ZIP format and these types of files can't be flashed via fastboot (correct me if I'm wrong).
adb reboot bootloader // reboot to fastboot
fastboot flash vbmeta vbmeta.img //if the GSI ROM has a vbmeta file. Official Android builds provided by Google (Android 10,11) do come with this file.
fastboot erase system
fastboot flash system system.img //replace system.img with the name of the GSI ROM
fastboot -w //factory reset
fastboot reboot //reboot to system
Regarding the camera cutout, I don't use these GSI ROMs for more than a few hours. So haven't yet thought about it. If you want you could change the cutout style from Developer Options and see if it works.
binary**# said:
On stability and battery life, Pixel is the go-to ROM. I am saying this from my previous experience of using custom ROMs. I have tried many custom ROMs and Pixel always took the first position in battery life and stability. The main reason for that could be attributed to the fact that it is a trimmed down ROM with just the basic functionalities.
As far as camera goes, I tried a bunch of GCams but unfortunately have to give up on all as none of them worked. There is a GCam channel on the Telegram for Action/Vision and there are a lot of discussions going on and Gcams being shared over there. Check it out.
Click to expand...
Click to collapse
About the gCam I also tried several, but this one seems most stable and functional. And with good quality in my opinion (at least not worse from the Moto's stock one: GoogleCamera-Pixel2Mod-Arnova8G2-V6.apk
Try it out. I've downloaded it from the group you mentioned.
Havoc os gsi rom
Well, the ROM is famous for providing tons of customizations and this GSI build doesn't disappoint either. You will be getting all the customizations functionality that is present in the custom ROM. However, there still exist some network issues which forbid making calls and sending messages. I have reached the halfway mark for finding the fix, and soon as I am able to find out the entire fix, I will update the guide. In the meantime check out the screenshots and the steps to install.
Notes:
Download both the ROM and Gapps. They both should be AB and ARM64. Thanks to turbolukex5 for the ROM and Gapps. GApps are near about 1GB whereas the ROM is around 500MB . But don't even think of skipping the Gapps, you will definitely get a bootloop (tried and tested).
STEPS:
Boot to TWRP and wipe Dalvik, Data, and System
Flash the GSI ROM in the system partition
Reboot to recovery
Flash Gapps in the system partition
Reboot to Recovery > System
Partial Calling Workaround:
After booting, first off turn off Aeroplane Mode and then type in *#*#4636#*#* --> Phone Information --> Enable the Mobile Radio Power. You will get the Network signal, unfortunately, this doesn't do much good. As soon as I get it working, will update this post
binary**# said:
Well, the ROM is famous for providing tons of customizations and this GSI build doesn't disappoint either. You will be getting all the customizations functionality that is present in the custom ROM. However, there still exist some network issues which forbid making calls and sending messages. I have reached the halfway mark for finding the fix, and soon as I am able to find out the entire fix, I will update the guide. In the meantime check out the screenshots and the steps to install.
Notes:
Download both the ROM and Gapps. They both should be AB and ARM64. Thanks to turbolukex5 for the ROM and Gapps. GApps are near about 1GB whereas the ROM is around 500MB . But don't even think of skipping the Gapps, you will definitely get a bootloop (tried and tested).
STEPS:
Boot to TWRP and wipe Dalvik, Data, and System
Reboot to recovery
Reboot to Recovery > System
Partial Calling Workaround:
After booting, first off turn off Aeroplane Mode and then type in *#*#4636#*#* --> Phone Information --> Enable the Mobile Radio Power. You will get the Network signal, unfortunately, this doesn't do much good. As soon as I get it working, will update this post
Click to expand...
Click to collapse
Any progress?
binary**# said:
Here are the commands needed for that. But if a GSI have a separate GApps package, then I don't think you could flash it via fastboot commands. This is because GApps comes in .ZIP format and these types of files can't be flashed via fastboot (correct me if I'm wrong).
adb reboot bootloader // reboot to fastboot
fastboot flash vbmeta vbmeta.img //if the GSI ROM has a vbmeta file. Official Android builds provided by Google (Android 10,11) do come with this file.
fastboot erase system
fastboot flash system system.img //replace system.img with the name of the GSI ROM
fastboot -w //factory reset
fastboot reboot //reboot to system
Regarding the camera cutout, I don't use these GSI ROMs for more than a few hours. So haven't yet thought about it. If you want you could change the cutout style from Developer Options and see if it works.
Click to expand...
Click to collapse
is there a possibility to add a custom screen cutout for the moto one action? since none of the cutout option fit our screen? or the move the position of the clock?
Thank you for your guide! I've installed Lineage 17 GSI on my phone this way & it is working perfectly (phone, NFC, camera, cellular internet)!
Update
mymagicmyhero: Someone suggested me a few adb root commands which might fix the calling issue on HavoCOS. I tried the same but unfortunately, it didn't do any good. The carrier's internet strangely works pretty well, its just the call that's creating issues. I even flashed the stock modem file onto Havoc, but still no luck. It's all messed up on professional front, so can't give in more time to it, but will still try to see if something works out.
Emmarelia: There's one magisk module that you could try out for the said process to work. Once you flash the GSI ROM, flash the phh's magisk file from TWRP (not the regular one, that isn't supported in GSI builds) . Then flash the None Display Cutout magisk module. And do share the results!
Hey binary, I just wanted to say thanks for the posts you've made in the one action forums, it really gave me a place to start from.
Just picked up a -4 variant a couple weeks ago in Canada on sale.
I've had many phones with varying degrees of custom ROM support and this phone is in a really weird place, open as all hell but nothing..
I used to build ROMs for i9100, d2can/d2att, mako, (ZTE) tulip, herolte, and m8ul. I havent looked into building for troika yet, with all the quarantine going on I have other priorities, but it's in my plans.
Have you tried building anything for troika yet?
I haven't found a ExtendedUI GSI that works but I've been running the Evo X GSI by Luke and all is well. Signal seems a bit weaker but it works fine.
Status bar is the right height out of the box.
I set the custom carrier in the rom to a few invisible characters, set it to the left side and made the carrier label size larger so it gives me a blank space where the camera is.
While it might not have true notch support in full screen apps, using the phone in portrait mode doing day to day tasks works like a charm.
I'm going to run this rom for a while but when I flash a new GSI I'll post the results here. If anybody has success with a particular ExUI GSI please let me know.
natetokes said:
I haven't found a ExtendedUI GSI that works but I've been running the Evo X GSI by Luke and all is well. Signal seems a bit weaker but it works fine.
Status bar is the right height out of the box.
I set the custom carrier in the rom to a few invisible characters, set it to the left side and made the carrier label size larger so it gives me a blank space where the camera is.
While it might not have true notch support in full screen apps, using the phone in portrait mode doing day to day tasks works like a charm.
I'm going to run this rom for a while but when I flash a new GSI I'll post the results here. If anybody has success with a particular ExUI GSI please let me know.
Click to expand...
Click to collapse
Could you please provide a link to the gsi?
mymagicmyhero said:
Could you please provide a link to the gsi?
Click to expand...
Click to collapse
https://sourceforge.net/projects/ex...-4.1.69-20200329-GSI-ARM64-AB.img.xz/download
i had some issues getting the bluetooth connected in my car but otherwise evox was a good gsi. might go back to it after im done testing the new android 10 update for -4
binary**# said:
So I have decided to create a Thread to share with you- all the Custom ROM GSI that I have tried till now. First off, let's begin with Pixel Experience. It has managed to retain the same smooth UI and user experience. Furthermore, it actually comes with a Dark Mode and not that dark grey hue that our device has to offer. Apart from that, there are few other features as well. However, since we are already running an Android One device, you wouldn't find much difference. With that said, check out the screenshots to experience this ROM in detail
How to Flash GSI ROM on Moto One Action
There are two methods for that, the fastboot command method and the TWRP Recovery method. I will be discussing the latter because via the fastboot commands Bootloader wouldn't even allow formatting the system for some strange reasons SO here is what needs to be done (and yes I won't be responsible for your bricked devices, if that happens :silly
Notes:
Download the Pixel Experience GSI ROM. A huge thanks to turbolukex5 for this GSI ROM.
Do remember to always download an ARM64 CPU architecture ROM with AB partition for Moto One Action.
Transfer this ROM to SDCard. Although we won't be formatting Internal Storage, yet it is always advisable to keep it in external storage like SD Card or Pendrive.
Steps to Follow:
Boot to TWRP and go to Wipe > Dalvik, Data and System.
Head over to SD Card and tap on Install Image (the bottom right button on your recovery).
Now flash the GSI ROM.
Once it gets flashed (2-3mins at max), go to Reboot and tap Recovery. You will get a message that NO OS is installed. IGNORE it and proceed with the reboot. You should NOT reboot to the system otherwise bootloop is guaranteed from my end
Reason for bootloop: WIth A/B partition devices like ours, there is no separate recovery partition. It is handled by the boot partition itself (that is why we boot the recovery rather than actually flashing itself). Now we will have to refresh the boot [partiton and for that, you will have to reboot the TWRP recovery. If you don't do so, system won't be able to recognize the boot partition (personal experience: tried many times and ended up in bootloop each time ).
Once you reboot to recovery, again head over to Reboot > System. This time you won't notice the NO OS message. The first time the device might reboot once or twice, that is completely normal.
That's it. Enjoy the New Pixel Experience on your Moto One Action
Next Up: Flashing the HavocOS GSI ROM.
Click to expand...
Click to collapse
I boot to recovery first but still show me no system installed no matter what I do..
areq1987 said:
I boot to recovery first but still show me no system installed no matter what I do..
Click to expand...
Click to collapse
Don't quote the whole op.
No problems here.
Wipe, flash GSI image as system, reboot to recovery, reboot to system.
Which GSI ROM are you trying to run?
natetokes said:
Don't quote the whole op.
No problems here.
Wipe, flash GSI image as system, reboot to recovery, reboot to system.
Which GSI ROM are you trying to run?
Click to expand...
Click to collapse
From the topic- Pixel experience. Shows no os installed even when i first boot to recovery after install.
Wysłane z mojego motorola one action przy użyciu Tapatalka
areq1987 said:
From the topic- Pixel experience. Shows no os installed even when i first boot to recovery after install.
Wysłane z mojego motorola one action przy użyciu Tapatalka
Click to expand...
Click to collapse
Are you booting to recovery after a shutdown or pressing reboot to recovery in TWRP?
natetokes said:
Are you booting to recovery after a shutdown or pressing reboot to recovery in TWRP?
Click to expand...
Click to collapse
Pressing reboot to recovery in twrp kole manual says.
Wysłane z mojego motorola one action przy użyciu Tapatalka
i just need to know which steps to take, in which order.
i can later add details to the steps.
but every f*&(^*( time i have to upgrade phone (ota doesnt work to upgrade to guacamole)
i have to rediscover which order.... finally i'm on a quest to log it all
1) install fastboot/adb on pc/linux/mac
2) unlock phone
3) fastboot flash boot twrp.img
4) reboot to recovery (should go to twrp)
5) flash twrp.zip
6) flash magisk
7) flash lineage_nightly.zip
8) reboot to os
Lineage will finally load... "about phone" says i'm in 17.1 guacamole doing this now my sim card won't read.... & i can't rotate screen (a problem i've had when the last lineage 16.? worked)
i can't flash oxygen.. cuz an error comes up
i need help
(i did wipe all data etc.. but i need to place the wipes in the order above)
(after flashing to lineage, the settings say im encrypted(maybe that matters))
EDIT: to make matters easier.. i can get into fastboot mode now, and my linux pc recognizes the phone
how can i fix this
Did you also FORMAT your data?
Use MSM Tool
csmooth2001 said:
i just need to know which steps to take, in which order.
i can later add details to the steps.
but every f*&(^*( time i have to upgrade phone (ota doesnt work to upgrade to guacamole)
i have to rediscover which order.... finally i'm on a quest to log it all
1) install fastboot/adb on pc/linux/mac
2) unlock phone
3) fastboot flash boot twrp.img
4) reboot to recovery (should go to twrp)
5) flash twrp.zip
6) flash magisk
7) flash lineage_nightly.zip
8) reboot to os
Lineage will finally load... "about phone" says i'm in 17.1 guacamole doing this now my sim card won't read.... & i can't rotate screen (a problem i've had when the last lineage 16.? worked)
i can't flash oxygen.. cuz an error comes up
i need help
(i did wipe all data etc.. but i need to place the wipes in the order above)
(after flashing to lineage, the settings say im encrypted(maybe that matters))
EDIT: to make matters easier.. i can get into fastboot mode now, and my linux pc recognizes the phone
how can i fix this
Click to expand...
Click to collapse
Same thing happened to me, I went from locked boot loader to unlock + lineage. When I tried to go back, the error kept popping up and the only thing that worked was fastboot.
Use MSM tool linked below and you should be good.
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
Note : IMPORTANT ! msm tool will also relock your bootloader, so you will lose any data you might have on your phone.
csmooth2001 said:
i just need to know which steps to take, in which order.
i can later add details to the steps.
but every f*&(^*( time i have to upgrade phone (ota doesnt work to upgrade to guacamole)
i have to rediscover which order.... finally i'm on a quest to log it all
1) install fastboot/adb on pc/linux/mac
2) unlock phone
3) fastboot flash boot twrp.img
4) reboot to recovery (should go to twrp)
5) flash twrp.zip
6) flash magisk
7) flash lineage_nightly.zip
8) reboot to os
Lineage will finally load... "about phone" says i'm in 17.1 guacamole doing this now my sim card won't read.... & i can't rotate screen (a problem i've had when the last lineage 16.? worked)
i can't flash oxygen.. cuz an error comes up
i need help
(i did wipe all data etc.. but i need to place the wipes in the order above)
(after flashing to lineage, the settings say im encrypted(maybe that matters))
EDIT: to make matters easier.. i can get into fastboot mode now, and my linux pc recognizes the phone
how can i fix this
Click to expand...
Click to collapse
Wrong order. First flash LOS, then TWRP Installer and then Magisk. When you flash LOS after TWRP and Magisk, your TWRP and root will be gone.
n2851991m said:
Same thing happened to me, I went from locked boot loader to unlock + lineage. When I tried to go back, the error kept popping up and the only thing that worked was fastboot.
Use MSM tool linked below and you should be good.
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
Note : IMPORTANT ! msm tool will also relock your bootloader, so you will lose any data you might have on your phone.
Click to expand...
Click to collapse
crap... my link is old.. may not work.. i'll try yours.... fingers crossed
csmooth2001 said:
Lineage will finally load... "about phone" says i'm in 17.1 guacamole doing this now my sim card won't read.... & i can't rotate screen (a problem i've had when the last lineage 16.? worked)
Click to expand...
Click to collapse
I can confirm the auto rotate issue with 17.1. In my situation, this was with a tmo 1915 variant. When I loaded OOS 9.5.13 and LOS 16, no mobile data but rotation. If I loaded OOS 10.3.1 firmware with LOS 17.1, had mobile data but no rotation. I even flashed the modem from OOS 10.3.1 into 9.5.13 that produced mobile data but no rotaion. No matter which firmware I tried which was many, I could never have both mobile data and rotation!! I wound up returning the tmo 1915 and ordered a 1917. .Have not received it yet. Maybe better luck with the international variant.
As a side note, luk1337, one of the los 17.1 maintainers for guac, is using the EU 1913 variant and confirmed that los 17.1 was not tested with the 1915 variant. So if you gots a tmo 1915, lots of luck. Searching around, they are supposed to be the same hardware but due to tmo locking tihs down, I dont know.
As for flashing, the thing to remember is that when you flash roms, you are flashing to the OTHER slot. When you are flashing mods, you are flashing to the CURRENT slot. Flashing roms and mods in recovery without changing the slot between will hose your install.
Official install method from maintainers:
1. Download the latest build
2.. Boot to recovery (the current slot. Could be A or B)
3. Flash the latest build
4. Boot to recovery again (now you are in the other slot)
5. Flash magisk
6. Reboot
Hope that helps.
razorshiv said:
I can confirm the auto rotate issue with 17.1. In my situation, this was with a tmo 1915 variant. When I loaded OOS 9.5.13 and LOS 16, no mobile data but rotation. If I loaded OOS 10.3.1 firmware with LOS 17.1, had mobile data but no rotation. I even flashed the modem from OOS 10.3.1 into 9.5.13 that produced mobile data but no rotaion. No matter which firmware I tried which was many, I could never have both mobile data and rotation!! I wound up returning the tmo 1915 and ordered a 1917. .Have not received it yet. Maybe better luck with the international variant.
As a side note, luk1337, one of the los 17.1 maintainers for guac, is using the EU 1913 variant and confirmed that los 17.1 was not tested with the 1915 variant. So if you gots a tmo 1915, lots of luck. Searching around, they are supposed to be the same hardware but due to tmo locking tihs down, I dont know.
As for flashing, the thing to remember is that when you flash roms, you are flashing to the OTHER slot. When you are flashing mods, you are flashing to the CURRENT slot. Flashing roms and mods in recovery without changing the slot between will hose your install.
Official install method from maintainers:
1. Download the latest build
2.. Boot to recovery (the current slot. Could be A or B)
3. Flash the latest build
4. Boot to recovery again (now you are in the other slot)
5. Flash magisk
6. Reboot
Hope that helps.
Click to expand...
Click to collapse
so if I boot to recovery in the current slot A
so if i flash a ROM, it will install to B ?
ok ok ok.. i was told that i have to flash a rom, then twrp.zip then magisk
but according to you (i think)
i flash a rom, reboot to recovery.. then flash twrp.zipo then magisk?
im guessing big time
is there a forum just for GM1915 ??? anywhere in the world...
csmooth2001 said:
so if I boot to recovery in the current slot A
so if i flash a ROM, it will install to B ?.
Click to expand...
Click to collapse
yes.
ok ok ok.. i was told that i have to flash a rom, then twrp.zip then magisk
but according to you (i think)
i flash a rom, reboot to recovery.. then flash twrp.zipo then magisk?
Click to expand...
Click to collapse
flash rom, flash twrp, reboot recovery, flash magisk.
is there a forum just for GM1915 ??? anywhere in the world..
Click to expand...
Click to collapse
They are scattered around the op7pro forum. Just do a search for tmo or tmobile.
boot to other slot & sim will work
I decided it was finally time to upgrade to the newer LineageOS 17.1 branch nightlies from my previous installation of 16, rebooted to recovery and sideloaded lineage-17.1-20201013-nightly-enchilada-signed.zip onto it from https://download.lineageos.org/enchilada .
After doing so it appears the recovery successfully updated, it has a new purple skin it didn't have before, however the actual ROM won't start. Instead it goes to fastboot mode and asks whether I want to Start/Restart/Recovery/etc, but I can only get into fastboot or recovery mode.
I've tried flashing older nightlies, but even with 20200922 the issue was still there. I did notice there was a ton of updates in that specific release so I wonder if anything is broken in there.. unfortunately that's also the oldest available nightly so without compiling my own there's no way I can test whether older ones are functional, unless someone here has an older version available perhaps.
I did notice doing adb sideload only makes it go to 47% before the phone goes to installing it, however maybe that's normal, I haven't used it in a while so I don't know for sure. I tried using ADB to push an image onto /tmp, however the new recovery only seems to have 'Apply from ADB' as option so I can't actually install it from there.
Does anyone have any ideas I could try, or perhaps an older LineageOS nightly from before 09-22 laying around somewhere? Any help or suggestions much appreciated!
PPS: Of course I forgot to mention but I also did a factory reset, but that did not help. unsure what else to try besides compiling a rom myself or trying other roms from the forums here, though I'd very much prefer having LineageOS..
I found the reason. I had to install the official Oneplus 6 ROM first, probably to get the right vendor binaries/kernel modules/drivers.
This is what I did:
- fastboot boot TWRP ( TWRP can be found here https://twrp.me/oneplus/oneplus6.html )
- wipe -> advanced wipe -> all the things (technically optional but if you want to get rid of GApps etc this is needed)
- adb sideload official OnePlus 6 'Oxygen' ROM ( https://www.oneplus.com/global/support/softwareupgrade/details?code=PM1574156173727 )
- reboot, fastboot boot TWRP
- run the 'copy partitions' zip from https://androidfilehost.com/?fid=8889791610682929240 to copy Oxygen to the other A/B partition
- Install latest build from https://download.lineageos.org/enchilada
- reboot, optionally boot TWRP again and install GApps, also optionally install TWRP, reboot, enjoy.
PS: Please note that after this you shouldn't switch A/B partition without first flashing another nightly or something over it, i.e fastboot boot twrp and install latest lineageos again, otherwise you'll end up booting the vanilla Oxygen rom