Related
Hey, was big into the android scene years ago, switched to other platforms for a bit just to play with them. Got a used 64 gig 6p and was thinking about dropping a custom rom onto it, but I don't know what's good anymore. What's the most stable, daily driver, minimalist rom out there? Wouldn't mind SOME extra features like task/notification bar customization and things like that. Stability and rock solid performance with great battery life are the concerns. Thank you!
GunnermanBill said:
Hey, was big into the android scene years ago, switched to other platforms for a bit just to play with them. Got a used 64 gig 6p and was thinking about dropping a custom rom onto it, but I don't know what's good anymore. What's the most stable, daily driver, minimalist rom out there? Wouldn't mind SOME extra features like task/notification bar customization and things like that. Stability and rock solid performance with great battery life are the concerns. Thank you!
Click to expand...
Click to collapse
I'm running f2fs file system with ABC oreo build & superUber kernel. I'm on latest radio & bootloader from 8.1. it has been pretty solid. I was on Pure Nexus nougat & Flash kernel; this set-up is tried & true. The Superxe ROM is aroma based and has 8.1 preview although I haven't got to try it yet. Hopefully this might point you in the right direction; there is a f2fs twrp build(s) in the 6p development thread if your interested.
Samuel Holland said:
I'm running f2fs file system with ABC oreo build & superUber kernel. I'm on latest radio & bootloader from 8.1. it has been pretty solid. I was on Pure Nexus nougat & Flash kernel; this set-up is tried & true. The Superxe ROM is aroma based and has 8.1 preview although I haven't got to try it yet. Hopefully this might point you in the right direction; there is a f2fs twrp build(s) in the 6p development thread if your interested.
Click to expand...
Click to collapse
Awesome reply, thank you for the heads up. F2FS is new to me, I'm guessing
https://forum.xda-developers.com/ne...recovery-twrp-2-8-7-0-touch-recovery-t3234976
is the thread you were talking about? I need to get it bootloader unlocked and rooted still, i'll probably tackle it when i get home and drop that version of TWRP onto it. Thanks again!
so it looks like the tools like Wug's are all very outdated, are they safe to use anyway on my device that has all the latest stock stuff? like 8.0 and my version aren't listed in Wug's at all.
GunnermanBill said:
Awesome reply, thank you for the heads up. F2FS is new to me, I'm guessing
https://forum.xda-developers.com/ne...recovery-twrp-2-8-7-0-touch-recovery-t3234976
is the thread you were talking about? I need to get it bootloader unlocked and rooted still, i'll probably tackle it when i get home and drop that version of TWRP onto it. Thanks again!
Click to expand...
Click to collapse
Here's the link to the unofficial twrp for 6p with f2fs support. Don't forget to check the box in twrp "Use rm -rf instead of formatting" after changing data and cache to f2fs. Make sure your rom and kernel support f2fs with kernel being mandatory for best results. Here's the link:
https://forum.xda-developers.com/nexus-6p/development/unofficial-twrp-3-0-3-x-f2fs-support-t3543450
---------- Post added at 12:27 PM ---------- Previous post was at 12:15 PM ----------
GunnermanBill said:
so it looks like the tools like Wug's are all very outdated, are they safe to use anyway on my device that has all the latest stock stuff? like 8.0 and my version aren't listed in Wug's at all.
Click to expand...
Click to collapse
I'm sure that unlocking the phone with the toolkit is safe. It's the method I used. Also in the link above or in the 6p section it should have any info you may need. You can flash recovery by vol dn & power button into bootloader(fastboot), and once you "cd /path tofolder with recovery image/" & "fastboot devices" to make sure you can see your 6p and drivers are installed correctly, you can rename twrp.img to recovery.img & they command is:
fastboot flash recovery recovery.img
I recommend going to xda 6p section; general, & questions, & answers & reading up on everything just to be on the safe side and very important; make backup at all times just to make sure if there is a "booboo" you can easily restore. If you need adb & fastboot installed, there is a thread here on xda "15 sec adb & fastboot installer".
I hope this could help and I hope you enjoy as much as I have.
Latest ROMs which gives me good performance and battery life are paranoid (still nougat, but always a winner), latest 8.1 with pixel 2 mod and aicp rom with kernvatore kernel.
Buying a 6P for good battery life may have been a mistake...
gman88667733 said:
Buying a 6P for good battery life may have been a mistake...
Click to expand...
Click to collapse
Battery life on stock has been as good as my iPhones 6s. Does charge slower though, even when it's rapid.
GunnermanBill said:
Hey, was big into the android scene years ago, switched to other platforms for a bit just to play with them. Got a used 64 gig 6p and was thinking about dropping a custom rom onto it, but I don't know what's good anymore. What's the most stable, daily driver, minimalist rom out there? Wouldn't mind SOME extra features like task/notification bar customization and things like that. Stability and rock solid performance with great battery life are the concerns. Thank you!
Click to expand...
Click to collapse
Clockwork mod is no more, TWRP is the new standard recovery.
Nexus/Pixel line by google gives you the minimalistic ROM you would need,ie. stock ROM :laugh:
Try stock rom for a while. Heck, i got so used to stock , I havent rooted my phone since ages. Atm i have moved on to pixel, and i am perfectly comfortable with stock ROM. I guess custom ROMs only attracted me when i had devices whose software cycle were abandoned by their OEM's.
NoobInToto said:
Clockwork mod is no more, TWRP is the new standard recovery.
Nexus/Pixel line by google gives you the minimalistic ROM you would need,ie. stock ROM :laugh:
Try stock rom for a while. Heck, i got so used to stock , I havent rooted my phone since ages. Atm i have moved on to pixel, and i am perfectly comfortable with stock ROM. I guess custom ROMs only attracted me when i had devices whose software cycle were abandoned by their OEM's.
Click to expand...
Click to collapse
Just now finally rooted etc. My issue with stock was it would crash and reboot sometimes when unlocking it while something was playing over bluetooth. Not going nuts with advanced feature roms, but honestly at this point trust the devs here over the crazies that Google hires these days. Just keeping it safe simple and solid.
You should try the SuperXE Custom ROM on 8.0 with the Pixel 2 features/addons. You should also give PureNexus a try, if you're not so satisfied with Oreo just yet. I'm currently running the Android 8.1 developer preview and I love it, the battery life is great and the ROM is fluid with little bugs.
alright, i thought i had rooted, i guess not. I'm unlocked, i used wug's to root, but it's not sticking. I don't have super user, and i cannot boot into recovery without using ADB. If recovery is selected from the bootloader menu it just brings me to the default android recovery with no options and I have to hold the power button down. I've tried manually flashing the recovery via fastboot and it's the same story. I tried booting into twrp via fastboot and flashing the superuser zip there but it's not in my app drawer. Everything seems to be successful when the operations are running. What gives?
GunnermanBill said:
alright, i thought i had rooted, i guess not. I'm unlocked, i used wug's to root, but it's not sticking. I don't have super user, and i cannot boot into recovery without using ADB. If recovery is selected from the bootloader menu it just brings me to the default android recovery with no options and I have to hold the power button down. I've tried manually flashing the recovery via fastboot and it's the same story. I tried booting into twrp via fastboot and flashing the superuser zip there but it's not in my app drawer. Everything seems to be successful when the operations are running. What gives?
Click to expand...
Click to collapse
the recovery does not stick on stock ROM if you don't flash either supersu or magisk. So you need to put the .zip of either one of those on your phone, then boot to bootloader and fastboot flash the recovery. Next, you boot into the recovery and flash the zip that you put on your phone.
you are now rooted, and your recovery will stick.
I'm currently on stock 8.0 waiting for paranoid android 8.0 update
knevelsg-j said:
the recovery does not stick on stock ROM if you don't flash either supersu or magisk. So you need to put the .zip of either one of those on your phone, then boot to bootloader and fastboot flash the recovery. Next, you boot into the recovery and flash the zip that you put on your phone.
you are now rooted, and your recovery will stick.
I'm currently on stock 8.0 waiting for paranoid android 8.0 update
Click to expand...
Click to collapse
I had flashed the super user zip in the wug kit myself while in TWRP but it still didn't stick. I mentioned that previously but i said a lot of other stuff too i'm not suprised you missed it. I guess I'm probably flashing the wrong SU and will look for another.
edit - grabbed the latest stable super user and it seems good now
What's this vendor image that's a thing now? You have to be tethered to a PC to flash most roms due to it nowadays it seems. Radios used to come in zips i could flash in twrp as well, what happened to that?
Greetings from Los Angeles. After following the steps kish and runningnak3d provided using lafsploit, I am having difficulty narrowing down what I’m missing. My goal is to be running the latest Lineage official builds. With high-end specs, an extended battery, and microSD combined with a custom ROM, this phone has the potential to be glorious.
Here’s what I did:
• Start with a running stock 10u phone. Did OEM unlocking. Did bootloader unlocking.
• Used LGUP to get it to 10p.
• Booted up FWUL. Ran the step 1 bash script. TWRP is installed.
• Instead of running the step 2 script, from inside of TWRP, I flash SuperSU and phoenix’s h918 build of TWRP.
At this point I have TWRP on two partitions—3.2.2 on recovery and 3.2.1-3 on laf. Running stock 10p + root is now working great. No issues.
Every time I flash lineage (with optional gapps + su), I tell TWRP to reboot. It consistently causes the phone to have the blinking backlight where it flashes on and off every 1 – 2 seconds. The LG logo appears, and then you're faced with the blackness. Think of it as an all black screen turning on and off. To recover from this, I pull the battery, hit the volume up button + USB cable to boot into TWRP, flash a 10u flashable zip, and then repeat from square one.
Things I have tried:
• I have tried flashing Lineage on the TWRP on recovery and the TWRP on laf to see if it would make a difference. Same blinking black screen.
• Before installing Lineage, I went into format and typed ‘yes’ to remove decryption. I installed Lineage. Hello blinking black screen.
• Under ‘advanced wipe’, I tried clearing everything onboard (Dalvik / ART Cache, System, Data, Internal Storage, and Cache). I went to installing Lineage. Hello black blinking screen.
• One guide suggested hitting ‘advanced wipe’ and to clear the /data and /cache partitions before installing. No difference. Hello blinkyness.
• I did the general wipe before installing Lineage. No change.
• I tried just installing Lineage images (tried different build dates) with no gapps or su to reduce the chance of any complications.
If I can get this phone working with Lineage with my triple capacity battery, tacos for everyone.
I don't use Lineage, so I am not 100% on this, but you didn't say you flashed a kernel. I am fairly certain that Lineage will not work with the stock kernel.
If you did flash a kernel, what kernel did you flash?
-- Brian
runningnak3d said:
I don't use Lineage, so I am not 100% on this, but you didn't say you flashed a kernel. I am fairly certain that Lineage will not work with the stock kernel.
If you did flash a kernel, what kernel did you flash?
-- Brian
Click to expand...
Click to collapse
I believe the lineage builds include it's own kernel
Sent from my LG-H910 using XDA Labs
Thanks dude, didn't know that. I actually love Lineage when all aspects of the phone are supported. Yes, I could get involved and help make that happen, but I have too much on my plate. You can bet your ass that I WILL be helping on P since this phone will never see an official release.
With that said, I guess I should keep my mouth shut when it comes to Lineage questions since I don't run it
-- Brian
runningnak3d said:
Thanks dude, didn't know that. I actually love Lineage when all aspects of the phone are supported. Yes, I could get involved and help make that happen, but I have too much on my plate. You can bet your ass that I WILL be helping on P since this phone will never see an official release.
With that said, I guess I should keep my mouth shut when it comes to Lineage questions since I don't run it
-- Brian
Click to expand...
Click to collapse
You're good, I don't use Lineage due to it's deficiencies, I just read up on it
Sent from my LG-H910 using XDA Labs
michaeljh9 said:
Greetings from Los Angeles. After following the steps kish and runningnak3d provided using lafsploit, I am having difficulty narrowing down what I’m missing. My goal is to be running the latest Lineage official builds. With high-end specs, an extended battery, and microSD combined with a custom ROM, this phone has the potential to be glorious.
Here’s what I did:
• Start with a running stock 10u phone. Did OEM unlocking. Did bootloader unlocking.
• Used LGUP to get it to 10p.
• Booted up FWUL. Ran the step 1 bash script. TWRP is installed.
• Instead of running the step 2 script, from inside of TWRP, I flash SuperSU and phoenix’s h918 build of TWRP.
Click to expand...
Click to collapse
Official lineage 14.1 only works with pre10p h918, some firmware blobs need changed.
I just built an unofficial for my own use a few days ago that should work, but I havnt gotten around to testing it yet.
lineage-14.1-20180721-UNOFFICIAL-h918.zip
lineage-14.1-20180721-UNOFFICIAL-h918.zip.md5
When lineage 15.1 becomes official the h918 builds will be aimed at post10p. x86cpu is currently doing unofficial builds for both.
Phoenix591 said:
Official lineage 14.1 only works with pre10p h918, some firmware blobs need changed.
Click to expand...
Click to collapse
I looked on xda lineage threads, h918 threads, v20 subreddit, lineage subreddit, etc. You're a hero for sharing that. I couldn't find any posts about that and it was becoming frustratingly insane. It explains everything. I have been successful in the past getting h918 official lineage running but you're absolutely correct in that it was using dirtycow on 10i. I'm currently working on getting this 10p working. After hearing the news, I am looking forward to 15.1's official release.
Give me a few minutes. I'm flashing your image.
michaeljh9 said:
I looked on xda lineage threads, h918 threads, v20 subreddit, lineage subreddit, etc. You're a hero for sharing that. I couldn't find any posts about that and it was becoming frustratingly insane. It explains everything. I have been successful in the past getting h918 official lineage running but you're absolutely correct in that it was using dirtycow on 10i. I'm currently working on getting this 10p working. After hearing the news, I am looking forward to 15.1's official release.
Give me a few minutes. I'm flashing your image.
Click to expand...
Click to collapse
Info is buried deep in one or more of the 3 lineage threads. Been watching them closely for ages.
Phoenix591 said:
I just built an unofficial for my own use a few days ago that should work, but I havnt gotten around to testing it yet.
lineage-14.1-20180721-UNOFFICIAL-h918.zip
Click to expand...
Click to collapse
I tried flashing it. When it boots up, it stays stuck at the LG logo. If it makes a difference, I did a normal standard wipe inside TWRP.
Phoenix591 said:
x86cpu is currently doing unofficial builds for both.
Click to expand...
Click to collapse
I went ahead and tried x86cpu's builds. While stock was installed, I booted into TWRP.
I flashed official-to-UNOFFICIAL.zip. Rebooted into the stock ROM as per the instructions.
Rebooted into TWRP. I flashed lineage-15.1-20180726-UNOFFICIAL-h918-10p.zip
I flashed 15.1 arm 64 pico gapps. I flashed the su add on. Hit reboot.
Son-of-a.... the Lineage boot animation started.....
I was greeted with the Lineage welcome wizard. This phone has never gotten this far. Words cannot express my relief and excitement. After it couldn't connect to WiFi, I fixed the 00:00:00:00:00:00 Mac address issue and that was straightforward.
I am one happy camper thanks to you guys.
To sum up my issue, it appears Lineage ROMs (and others?) need to be treated differently because the phone is configured to be ARB 1. *le sigh*
michaeljh9 said:
I tried flashing it. When it boots up, it stays stuck at the LG logo. If it makes a difference, I did a normal standard wipe inside TWRP.
I went ahead and tried x86cpu's builds. While stock was installed, I booted into TWRP.
I flashed official-to-UNOFFICIAL.zip. Rebooted into the stock ROM as per the instructions.
Rebooted into TWRP. I flashed lineage-15.1-20180726-UNOFFICIAL-h918-10p.zip
I flashed 15.1 arm 64 pico gapps. I flashed the su add on. Hit reboot.
Son-of-a.... the Lineage boot animation started.....
I was greeted with the Lineage welcome wizard. This phone has never gotten this far. Words cannot express my relief and excitement. After it couldn't connect to WiFi, I fixed the 00:00:00:00:00:00 Mac address issue and that was straightforward.
I am one happy camper thanks to you guys.
To sum up my issue, it appears Lineage ROMs (and others?) need to be treated differently because the phone is configured to be ARB 1. *le sigh*
Click to expand...
Click to collapse
yeah guess I forgot to mention that the first boot of lineage 14 after wiping takes 15-35 minutes. Usually not stuck on the lg logo.. ill take a look.
runningnak3d said:
Thanks dude, didn't know that. I actually love Lineage when all aspects of the phone are supported. Yes, I could get involved and help make that happen, but I have too much on my plate. You can bet your ass that I WILL be helping on P since this phone will never see an official release.
With that said, I guess I should keep my mouth shut when it comes to Lineage questions since I don't run it
-- Brian
Click to expand...
Click to collapse
Oh God dude!!!!!!! If and when you get involved in LOS, I will definitely flash that build.
You are by far my favorite Dev. That's why I'll always buy the same device you get. I know it would be WELL supported!
Sent from my LG-H918 using XDA Labs
Please make guide intall stock rom A2017UV2.1.0B20 with TWRP nfound!?
1. Download B20 EDL from:
https://androidfilehost.com/?w=files&flid=220826
2. Extract EDL zip
3. Boot phone into EDL mode and connect cable to PC
4. Open MiFlash or Axon 7 EDL Tool (your choice, MiFlash is simpler)
5. Make sure phone is detected, choose the folder you extracted to, flash
6. Reboot to stock recovery, format cache and data, reboot
7. You can reflash TWRP later via EDL as well
I really wouldn't recommend B20 though... LOS 15.1 is much better
@Teet1: I'm not a LOS fan, not enough customization options. But I generally don't like stock ROMs either, for any device. So in this case, LOS is better than stock.
AnonVendetta said:
@Teet1: I'm not a LOS fan, not enough customization options. But I generally don't like stock ROMs either, for any device. So in this case, LOS is better than stock.
Click to expand...
Click to collapse
Well I don't either but a lot of roms are based off LOS and adds customization. I'm just saying if he wants a stock like experience, LOS 15.1 always has an up to date security patch, lots of fixed and many more things that stock oreo doesn't have. For now anything is much better than stock. Except for audio. It's not the same and I wish it was
@Teet1: I'll agree that the audio quality of LOS/AOSP ROMs isn't up to par with stock. But I'm not an audiophile so I don't really care, the audio is good enough for me. Another beef I have with LOS is that Substratum doesn't fully work, you can't theme system apps. On my last test with Treble-enabled LOS15.1, Substratum was able to theme Google apps, but not other system apps like Settings, SystemUI, etc. I used Swift Black and they stayed white.
Lastly, don't use LOS's bootstack, trying to use the EDL button combo will give you DFU instead. You have to use TWRP, ADB, FTM, or DFU Tool to get into EDL.
AnonVendetta said:
@Teet1: I'll agree that the audio quality of LOS/AOSP ROMs isn't up to par with stock. But I'm not an audiophile so I don't really care, the audio is good enough for me. Another beef I have with LOS is that Substratum doesn't fully work, you can't theme system apps. On my last test with Treble-enabled LOS15.1, Substratum was able to theme Google apps, but not other system apps like Settings, SystemUI, etc. I used Swift Black and they stayed white.
Lastly, don't use LOS's bootstack, trying to use the EDL button combo will give you DFU instead. You have to use TWRP, ADB, FTM, or DFU Tool to get into EDL.
Click to expand...
Click to collapse
my 2 cents:
-I have been able to theme everything I wanted on LOS, at least with Flux. of course you have to go to the Manager tab and switch stuff on.
LOS Oreo now has OMS, as every other Oreo out there. B01/12/20 have it, and themeability is the same on all of them
-LOS's audio is good enough already, at least that's what I believe. way better than Nougat los at least
-DFU is already a non-issue, we have zte's tool now. Even before we had that it was no problemo: you have Fastboot on the LOS bootstack. This means that you can simply flash (or just boot) recoveries through Fastboot and do whatever you need through twrp.
Also every freaking bootstack in actuality gives DFU with the key combination on my U lmao
-B20 WILL encrypt your storage. There seems to be a way to avoid this but the guy who was able to do this doesn't really know what he did, we reproduced his steps and still have encryption.
Same with the bootstack, at least it seems so.
Installing this bootstack will either format your storage or force you to do so
@Choose an username...: My run with LOS15 O was short-lived, back to AOSPEx N for me. I also tried DotOS, and the Hellsgate/Schwifty kernels, but didnt have much success getting either ROM to boot with data/cache as F2FS.
Thanks for the Flux recommendation though, i pirated a copy and it works well, it's a good contender against Swift Black, but with more options. That's what i usually do when i want to test paid software but dont want to commit money initially. But now that i know i like it, i will buy it on Play Store as soon as I'm paid.
Flux even gives me Pie icons, which I kind of like, but I'm not sure I want that changed. I prefer a system-wide black but with original icons. It also makes notifications taskbar notifications difficult to read. Like for instance, if an app posts a notification in the taskbar, i can see the name of the app but not the message. Clicking still works.
I dont see a a Manager tab for Flux, it doesnt even have an app icon.
On the DFU thing, I dont think it's a bootstack issue, but I did at first. I've had it happen from B15 N to B35 N. And the refurb phone that ZTE sent back after my recent RMA, it was running great and had B35, but the button combo resulted in DFU. Downgrading the OS fixed nothing. Strangely enough, after flashing the B12 beta EDL, i was able to get directly into EDL with the buttons, and without the DFU tool, ADB, etc.
I was looking around in @djkuz's file collection on AndroidFileHost, I noticed he posted 2 EDL fix files. Curious to see what was inside, i checked them and found apdp and msadp files, and in the updater script it seemed to be flashing those 2 files to partitions. But his zips are for A2017G/A2017. Then I checked the B12 EDL and found those same files. 1+1=2, I figured that must be what fixed my EDL issue. More testing confirmed everything. You can just extract those files from that zip, then flash them to the correct partitions in a terminal/FlashFire, etc. Example:
dd if=/sdcard/msadp of=/dev/block/bootdevice/by-name/msadp
They are just raw partition image files, the exact filename to be flashed doesnt matter. But the destination partition's name must be an exact match or dd will throw an error. I cant say this will work on every bootstack, or on LOS bootstacks, on some bootstacks these partitions may not exist. But on the Nougat/Oreo bootstacks I've tried, this fix works, and it seems to stick no matter what stock EDL you flash, as long as it isnt the LOS bootstack.
It's nice to have the DFU tool, but it's even better to not have to use it. It's a minor inconvenience at worst. Besides, fastboot isnt available on the last few latest stock bootstacks (or bootstacks based on them).
AnonVendetta said:
@Choose an username...: My run with LOS15 O was short-lived, back to AOSPEx N for me. I also tried DotOS, and the Hellsgate/Schwifty kernels, but didnt have much success getting either ROM to boot with data/cache as F2FS.
Thanks for the Flux recommendation though, i pirated a copy and it works well, it's a good contender against Swift Black, but with more options. That's what i usually do when i want to test paid software but dont want to commit money initially. But now that i know i like it, i will buy it on Play Store as soon as I'm paid.
Flux even gives me Pie icons, which I kind of like, but I'm not sure I want that changed. I prefer a system-wide black but with original icons. It also makes notifications taskbar notifications difficult to read. Like for instance, if an app posts a notification in the taskbar, i can see the name of the app but not the message. Clicking still works.
I dont see a a Manager tab for Flux, it doesnt even have an app icon.
On the DFU thing, I dont think it's a bootstack issue, but I did at first. I've had it happen from B15 N to B35 N. And the refurb phone that ZTE sent back after my recent RMA, it was running great and had B35, but the button combo resulted in DFU. Downgrading the OS fixed nothing. Strangely enough, after flashing the B12 beta EDL, i was able to get directly into EDL with the buttons, and without the DFU tool, ADB, etc.
I was looking around in @djkuz's file collection on AndroidFileHost, I noticed he posted 2 EDL fix files. Curious to see what was inside, i checked them and found apdp and msadp files, and in the updater script it seemed to be flashing those 2 files to partitions. But his zips are for A2017G/A2017. Then I checked the B12 EDL and found those same files. 1+1=2, I figured that must be what fixed my EDL issue. More testing confirmed everything. You can just extract those files from that zip, then flash them to the correct partitions in a terminal/FlashFire, etc. Example:
dd if=/sdcard/msadp of=/dev/block/bootdevice/by-name/msadp
They are just raw partition image files, the exact filename to be flashed doesnt matter. But the destination partition's name must be an exact match or dd will throw an error. I cant say this will work on every bootstack, or on LOS bootstacks, on some bootstacks these partitions may not exist. But on the Nougat/Oreo bootstacks I've tried, this fix works, and it seems to stick no matter what stock EDL you flash, as long as it isnt the LOS bootstack.
It's nice to have the DFU tool, but it's even better to not have to use it. It's a minor inconvenience at worst. Besides, fastboot isnt available on the last few latest stock bootstacks (or bootstacks based on them).
Click to expand...
Click to collapse
Of course Flux doesn't have an app icon, most substratum modules don't have one. not sure what you mean with a Manager tab, themed stuff appears there
The DFU tool permanently switched my button combination to go to EDL
los 15 is not much better
For some strange reason, my A2017U gets stuck on the golden Axon logo for more than 30 minutes and still doesn't boot. I simply flashed the EDL with MiFlash and nothing else, not even a custom recovery or Magisk. Has anyone else faced this?
I've wiped everything, done a "Format Data" in TWRP and even used the Axon_7_EDL too. Same result.
One more thing. Initiating a force restart and booting to recovery ends up showing the recovery icon of the green Android logo with a red exclamation mark flickering on and off continuously.
KwesiJnr said:
For some strange reason, my A2017U gets stuck on the golden Axon logo for more than 30 minutes and still doesn't boot. I simply flashed the EDL with MiFlash and nothing else, not even a custom recovery or Magisk. Has anyone else faced this?
I've wiped everything, done a "Format Data" in TWRP and even used the Axon_7_EDL too. Same result.
One more thing. Initiating a force restart and booting to recovery ends up showing the recovery icon of the green Android logo with a red exclamation mark flickering on and off continuously.
Click to expand...
Click to collapse
flash twrp from EDL, then maybe format data and flash Magisk. Maybe it'll work
Oh yeah, I finally got it to work last night by flashing the B29 Rollback Mod from DrakenFX and then going through the steps again. I have a feeling it may have had something to do with the vendor/treble partitioning, although I can't be sure. I now have Magisk 16.7 and Xposed running. Thanks, though.
KwesiJnr said:
Oh yeah, I finally got it to work last night by flashing the B29 Rollback Mod from DrakenFX and then going through the steps again. I have a feeling it may have had something to do with the vendor/treble partitioning, although I can't be sure. I now have Magisk 16.7 and Xposed running. Thanks, though.
Click to expand...
Click to collapse
It sure was actually, you always have to get rid of the vendor partition when you go back to stock.
If you flashed a full edl via EDL Tool, then it should have been fixed. but whatever idk
Teet1 said:
Well I don't either but a lot of roms are based off LOS and adds customization. I'm just saying if he wants a stock like experience, LOS 15.1 always has an up to date security patch, lots of fixed and many more things that stock oreo doesn't have. For now anything is much better than stock. Except for audio. It's not the same and I wish it was
Click to expand...
Click to collapse
Camera is also much worse. As is battery life, thermal config and general UI responsiveness... So yeah, los15.1 is not ready for prime time yet.
i have a op6t bootloader unlocked still on tmobile 10.3.3 oos. i want to flash the nethunter/andrax kernel on it so i can check em both out. i am wondering if i should bother trying to flash the international rom on it, or what might be the best rom to use as a base for a pentesting platform.
it is my first oneplus device, but i messed around with nethunter on the galaxy series and kali on maemo before it. ive just gotten the unlock token and flashed it, i tried to msm it to the international rom prior, but kept getting a 'packed image not found' type error. i guess it doesnt matter now, i can just use twrp. but any advice, or direction on what i should flash or install in what order would be Greatly appreciated, im just trying to read up on all of it as much as i can right now.
moisturerichsoy said:
i have a op6t bootloader unlocked still on tmobile 10.3.3 oos. i want to flash the nethunter/andrax kernel on it so i can check em both out. i am wondering if i should bother trying to flash the international rom on it, or what might be the best rom to use as a base for a pentesting platform.
it is my first oneplus device, but i messed around with nethunter on the galaxy series and kali on maemo before it. ive just gotten the unlock token and flashed it, i tried to msm it to the international rom prior, but kept getting a 'packed image not found' type error. i guess it doesnt matter now, i can just use twrp. but any advice, or direction on what i should flash or install in what order would be Greatly appreciated, im just trying to read up on all of it as much as i can right now.
Click to expand...
Click to collapse
Reading is good! You'll really need that as you're about to venture on a potential world of pain. I have the international version so it's been smooth sailing for me but I've read a lot about these TMO devices and either it'll work for you if you follow the right guides or it'll go south really fast. And when it does, there's an endless road back to square one. It can be an excellent learning experience and there will usually be a way out but it will require a lot of patience. If you don't have that, you might as well stay with stock. You know yourself best [emoji6]
Timmmmaaahh said:
Reading is good! You'll really need that as you're about to venture on a potential world of pain. I have the international version so it's been smooth sailing for me but I've read a lot about these TMO devices and either it'll work for you if you follow the right guides or it'll go south really fast. And when it does, there's an endless road back to square one. It can be an excellent learning experience and there will usually be a way out but it will require a lot of patience. If you don't have that, you might as well stay with stock. You know yourself best [emoji6]
Click to expand...
Click to collapse
super good to know, as it sounds like if i can get the msm flash to work, it will be just like an international one. or maybe i can twrp flash it to a newish international oos that will work well with nethunter. But i guess my first order of business should be twrp flash and pull a full backup just in case. i am indeed looking for an odyssey, ive been bricking arm devices since the nokia n800 days so im sure i can figure things out.
im thinking:
twrp
magisk
backup
flash newest internation oos (msm or twrp?)
flash nethunter/andrax kernel
install non chroot nethunter
install andrax
...
profit?
i dunno why but im unreasonably excited to get a pentesting phone running with a kernel that supports native monitor mode and packet injection
I got it all to work, with plenty of haphazard dirty flashing, and only like 3 softbricks where I had to go back to 9x with msm. So I'm on 10.3.7 with twrp, magisk, seems like I disabled encryption, cause I ran into that issue before, and I have no lockscreen code now. I doubt I could reproduce it all, but the nethunter/andrax kernel seemed to have stuck, after I got nethunter chroot installed, I verified monitor mode worked. Got andrax all installed too, everything seems to be functioning properly. Sooo many tools to play with now. It's weird, every time I did things properly, I'd end up bricking it, then I would try some convoluted dirty flash and it would work out just how I wanted it.
moisturerichsoy said:
I got it all to work, with plenty of haphazard dirty flashing, and only like 3 softbricks where I had to go back to 9x with msm. So I'm on 10.3.7 with twrp, magisk, seems like I disabled encryption, cause I ran into that issue before, and I have no lockscreen code now. I doubt I could reproduce it all, but the nethunter/andrax kernel seemed to have stuck, after I got nethunter chroot installed, I verified monitor mode worked. Got andrax all installed too, everything seems to be functioning properly. Sooo many tools to play with now. It's weird, every time I did things properly, I'd end up bricking it, then I would try some convoluted dirty flash and it would work out just how I wanted it.
Click to expand...
Click to collapse
Hey im going through some things with the install so i flashed a international rom after the last fix i did with a .bat file from another post which its running fine so far. so could you explain some details with how you went about it at least the decryption part this has me lost as in...
1= TWRP format data
2=flash all the things i need to flash
3= flash DM verity disable force encryption last
all within the twrp.img first boot? or is it all done after twrp is installed
first of all im fresh to all flashing roms and i have been reading like crazy haha just trying to clearify the missing info or lack of maybe.
moisturerichsoy said:
I got it all to work, with plenty of haphazard dirty flashing, and only like 3 softbricks where I had to go back to 9x with msm. So I'm on 10.3.7 with twrp, magisk, seems like I disabled encryption, cause I ran into that issue before, and I have no lockscreen code now. I doubt I could reproduce it all, but the nethunter/andrax kernel seemed to have stuck, after I got nethunter chroot installed, I verified monitor mode worked. Got andrax all installed too, everything seems to be functioning properly. Sooo many tools to play with now. It's weird, every time I did things properly, I'd end up bricking it, then I would try some convoluted dirty flash and it would work out just how I wanted it.
Click to expand...
Click to collapse
Dude could you please help me I can't get nethunter running for the life of me, so it sounds you flashed the kernel then flashed nethunter oos10 for the op6 using twrp but it worked for the op6t? I'm pretty new to phones had nethunter on a oneplus one but that was a cakewalk, I got a T-Mobile op6t running international
Hate to bump an old post but did anyone manage to figure out the flash order on this?
And if so care ta share I'll be forever in your debt
Hello everyone! I have managed to get Global firmware on VZW UW OnePlus 8 and thought I would share.
Donations are appreciated. PayPal user @igp1490
You will need to download to get started.
1. FastbootEnhance: https://github.com/libxzr/FastbootEnhance/releases
2. Jaguar Rom Full: https://drive.google.com/file/d/1RIIZzz0IyVXeFdjjKRjgqdSphLxaE--w/view
3. Recovery: https://androidfilehost.com/?fid=15664248565197198941
4. PayloadDumper GUI. Download version 2.3: https://forum.xda-developers.com/t/...and-other-img-files-from-payload-bin.4442149/
5. Global OTA Firmware 11.0.11.11.IN21AA: https://www.thecustomdroid.com/download-oneplus-8-pro-oxygenos-ota-updates/
6. OnePlus 8 Visible OTA firmware: https://oxygenos.oneplus.net/OnePlu..._OTA_0080_all_2203082133_56fdf9c8718742cb.zip
7. Platform-tools, I'm using 33.0.3: https://www.techspot.com/downloads/downloadnow/5425/?evp=de0a68064118855fcddcc3980a2143c4&file=6062
Now to get started. First have bootloader unlocked of course.
1. Extract payload.bin from Visible OTA, then dump payload.bin with payload dumper. next find modem.img and move to desktop
2. Install Recovery
3.Be on A11 rom with A11 custom recovery or Install Jaguar Rom and go through setup.
Thanks to Bishop1312! for pointing out any A11 rom with A11 custom recovery works in step 3.
4. When Jaguar is setup reboot to fastboot
5. Run FastbootEnhance, double click your device that says fastboot
6. When in fastbootenhance click fastbootd then click little box to the left of "ignore unknown partitions" then select flash payload.bin and select global firmware zip. When flash is complete "select activate slot" my second slot to flash was slot B, you want to flash global to both slots.
7. After it installs click back in in Jaguar recovery and select "Factory reset", I did f2fs and regular format options
8. Afterformat is done reboot system
9. It may take a few minuets to get into the setup and you may get a message saying phone app has stopped working, don't worry just go through the setup process and connect to wifi.
10. when phone is setup turn off phone and boot into fastboot holding power+Vol down, when in fastboot connect to computer and run FastbootEnhancer. You should see your fastboot device, double click on fastboot, now in fastbootenhancer click reboot to Fastbootd. when in fastbootd go to Partitions tab in fastbootenhancer and look for Modem_b, click on modem_b to highlight it, then click erase then click flash and look for modem.img you put in desktop and select it to flash and after look for modem_a and follow same steps then reboot phone to system.
11. When phone is booted go to system updates and update. After update is finished reboot, after reboot follow steps 10 again for modem, continue step 10 until fully updated to Android 13. Verizon service will work in Android 13 but not 11 or 12.
One problem I have is if I turn on then off airplane mode it wont reconnect to Verizon service, you have to reboot phone and it will work again. I'm thinking maybe because it's an older modem.img, so if anyone can get there hands on the newer modem from Verizon or Visible newest OTA maybe that will fix the issue but no sure. This is my first guide so If anyone has problems let me know and i'll do my best to help you.
Hope ya'll enjoy.
Edit: I got EvolutionX A13 rom working! also airplane mode is working in EvolutionX A13 rom. You have to do step 10 every time after setting up new A13 roms. I Tried step 10 before going through setup but it just goes to bootloader, So make sure to complete rom setup before step 10.
Good work, man!!! This method fully work! I have some little notations:
In step 3, it can be any rom, based on Android 11, but recovery must be from custom A11 rom;
After another installing or updating rom, we must do step 10 every time, for working cellular data. But i think, it's small price for getting fully working custom A13 roms.
UPD. On every reboot, cellular data appears after ~1 min, so don't worry))
Bishop1312 said:
Good work, man!!! This method fully work! I have some little notations:
In step 3, it can be any rom, based on Android 11, but recovery must be from custom A11 rom;
After another installing or updating rom, we must do step 10 every time, for working cellular data. But i think, it's small price for getting fully working custom A13 roms.
Click to expand...
Click to collapse
Thank you. I'll edit step 3.
Bishop1312 said:
Good work, man!!! This method fully work! I have some little notations:
In step 3, it can be any rom, based on Android 11, but recovery must be from custom A11 rom;
After another installing or updating rom, we must do step 10 every time, for working cellular data. But i think, it's small price for getting fully working custom A13 roms.
UPD. On every reboot, cellular data appears after ~1 min, so don't worry))
Click to expand...
Click to collapse
Have you tried watching a video on youtube or any movie/video app? I'm having video playback freeze for a few seconds then video plays for another few seconds then freezes and continues this cycle. I'm wondering if it's just EvolutionX.
Incognit420 said:
Have you tried watching a video on youtube or any movie/video app? I'm having video playback freeze for a few seconds then video plays for another few seconds then freezes and continues this cycle. I'm wondering if it's just EvolutionX.
Click to expand...
Click to collapse
No, video playback i don't test for now. I tried to flash two roms and i apologize for unchecked words - after first flashing modem.img at the beginning, in the future no needs to flash modem, cellular data work fine.
Great work @Incognit420. A video guide will also be helpful for noob like me.
Zombify01 said:
Great work @Incognit420. A video guide will also be helpful for noob like me.
Click to expand...
Click to collapse
Even though reading is fundamental - a how-to video would take it over the top.
Does anyone know if OOS13 is working with this method? Don't you need the OOS12/ 13 firmware in order to be able to use the latest custom ROMs?
Xryphon said:
Does anyone know if OOS13 is working with this method? Don't you need the OOS12/ 13 firmware in order to be able to use the latest custom ROMs?
Click to expand...
Click to collapse
Yes OOS13 works. This method flashes OOS11 global firmware then you update to OOS12 in setting and then update to OOS13 in settings. Make sure to flash modem.img in fastbootd after each update. OOS13 works. Data and calling are not working in OOS12 global, don't know why but does work in OOS13. the only problem I have is OOS13 is if you turn off wifi it won't turn back on but data, calling and text work. I'm on a custom OOS13 rom and it fixed wifi.
Zombify01 said:
Great work @Incognit420. A video guide will also be helpful for noob like me.
Click to expand...
Click to collapse
I'm horrible at making videos lol but I'll give it a try.
hi, after step 7, i chose to back recovery , but show default recovery, and i go next step wipe data and reboot goot qualcom crush dump. any idea?
faritz1903 said:
hi, after step 7, i chose to back recovery , but show default recovery, and i go next step wipe data and reboot goot qualcom crush dump. any idea?
Click to expand...
Click to collapse
What rom were you on before flashing global firmware?
Incognit420 said:
What rom were you on before flashing global firmware?
Click to expand...
Click to collapse
oos 11, then install jaguar rom
after more try, it success. but in after upgrade to OOS 13 my wifi dont work, but cell is work, any idea?
faritz1903 said:
after more try, it success. but in after upgrade to OOS 13 my wifi dont work, but cell is work, any idea?
Click to expand...
Click to collapse
Glad to hear you got it working. Yeah I just realized that yesterday that wifi doesn't work. Install a custom a13 rom and you will get wifi back. I recommend starting with crdroid a13. I was using evolutionx but screen was flashing a little bit when typing so I installed crdroid and it is working perfectly. We need an actual developer to figure out the wifi issue in stock oos13. I'm not by any means a developer. I just messed around with firmware for months to figure out how to get a13 on our vzw devices since verizon is garbage for updates.I personally like the stock oos a13, so it would be nice to have wifi. I think the opeque look in the pixel roms is ugly, Google should have implemented blur in QS and notifications.
Incognit420 said:
Glad to hear you got it working. Yeah I just realized that yesterday that wifi doesn't work. Install a custom a13 rom and you will get wifi back. I recommend starting with crdroid a13. I was using evolutionx but screen was flashing a little bit when typing so I installed crdroid and it is working perfectly. We need an actual developer to figure out the wifi issue in stock oos13. I'm not by any means a developer. I just messed around with firmware for months to figure out how to get a13 on our vzw devices since verizon is garbage for updates.I personally like the stock oos a13, so it would be nice to have wifi. I think the opeque look in the pixel roms is ugly, Google should have implemented blur in QS and notifications.
Click to expand...
Click to collapse
i will try but link recovery and vbmeta is not found, can u share it?
can you try isntall Coloros 13?
faritz1903 said:
i will try but link recovery and vbmeta is not found, can u share it?
can you try isntall Coloros 13?
Click to expand...
Click to collapse
Install EvolutionX 13 and then install Crdroid 9.0. or you can try just using EvolutionX vbmeta and recovery to install Crdroid, both roms use the same method.
Incognit420 said:
Glad to hear you got it working. Yeah I just realized that yesterday that wifi doesn't work. Install a custom a13 rom and you will get wifi back. I recommend starting with crdroid a13. I was using evolutionx but screen was flashing a little bit when typing so I installed crdroid and it is working perfectly. We need an actual developer to figure out the wifi issue in stock oos13. I'm not by any means a developer. I just messed around with firmware for months to figure out how to get a13 on our vzw devices since verizon is garbage for updates.I personally like the stock oos a13, so it would be nice to have wifi. I think the opeque look in the pixel roms is ugly, Google should have implemented blur in QS and notifications.
Click to expand...
Click to collapse
The reason why the various issues on the ROMs exist is because the OOS12/ OOS 13 firmware has not been released by Verizon officially, and there are fundamental changes in the firmware such as the modem (since the Verizon model has the mmWave functionality). This leads to various networking issues such as Wi - Fi not working, cell data not working sometimes, etc. IN2019/ Verizon OnePlus 8 users will never get a stable OOS12/ OOS13 build unless Verizon decides to release the firmware for it - the custom ROMs are the same way since they rely in the OOS12/ OOS13 firmware in order to function properly.
Before I attempt this, is there an easy way to return to stock? Does flashing to stock with MSM undo these changes?
The0919 said:
Before I attempt this, is there an easy way to return to stock? Does flashing to stock with MSM undo these changes?
Click to expand...
Click to collapse
Yes, MSM will bring you back to vzw firmware.