give me rom ZTE axon 7 Oreo b20 for TWRP? - ZTE Axon 7 Questions & Answers

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.

Related

Phone Bricked Can Someone Help?

This method here seemed pretty straightforward to upgrade to Nougat: https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
I was already unlocked so I figured I just need to flash the "Full" package then the "TWRP" package. TWRP is working, the bootloader still shows as unlocked in fastboot mode, but trying to boot just shows a Linux penguin and nothing else!
I just cleared everything in TWRP to see if that was somehow the issue then reboot, and TWRP says no OS installed! HOW?!
All this happened because I'm unclear on everything, and instead of a yes/no answer I get mocked. Someone please help.
Can you Boot in Fastboot?
When yes . load a Original Firmware update.zip and extract recovery.img from this . Do the recovery.img in Minimal adb and fastboot , open a command windows .
Type: fastboot flash recovery recovery.img ,before this boot the phone in fastboot mode.
After the flash recovery ,boot the phone in the recovery with Volume down (tick them 1 or two times ) reboot ist with power.
Put a SD Card in the Phone with the update zip in root folder of the SD Card.
In recovery tick with Volume down to the Point update via SD Card and wait the Process ist finished.
tester2017 said:
Can you Boot in Fastboot?
When yes . load a Original Firmware update.zip and extract recovery.img from this . Do the recovery.img in Minimal adb and fastboot , open a command windows .
Type: fastboot flash recovery recovery.img ,before this boot the phone in fastboot mode.
After the flash recovery ,boot the phone in the recovery with Volume down (tick them 1 or two times ) reboot ist with power.
Put a SD Card in the Phone with the update zip in root folder of the SD Card.
In recovery tick with Volume down to the Point update via SD Card and wait the Process ist finished.
Click to expand...
Click to collapse
I have access to fastboot mode. However I'm still confused as to what is going on.
At least I've figured out where it goes wrong, at the TWRP step. The "no OS detected" made no sense so I tried flashing using the same method but just the "Full" package first. It eventually does boot and it appears Android 7 is working.
The bootloader shows as unlocked. However when I install the TWRP package after, TWRP is restored but then the phone is bricked and TWRP says no OS detected. I'm not sure if this is because I clicked "allow modifications" and if so why that causes it to go wrong and what I missed. I tried flashing TWRP manually using fastboot mode in case something was wrong with that EDL package, and the result is the same, after installing TWRP and clicking allow modifications the OS is no longer detected.
What am I missing? I must have missed a step.
ok. go to twrp and format data to ext 4 then flash new and restart.
tester2017 said:
ok. go to twrp and format data to ext 4 then flash new and restart.
Click to expand...
Click to collapse
When go to "Format Data", enter yes to allow it, it fails and says:
"mkfs.f2fs -t 0 /dev/block/sda9 process ended with
ERROR: 255
Unable to wipe Data.
Unable to format to remove encryption
Upadting partition details...
Failed to mount '/data' (device or resource busy)
... done"
Even if that went through I'm unsure what you mean flash new? Flash a new what?
When I enter repair/change it says the file system is ext4 anyway.
Well I tried starting at that point again since I didn't allow modifications in TWRP this time, and it actually booted Android but then asks for a password... what?
So something about allowing modifications in TWRP seems to be the culprit, but then I'm unsure why it would ask for a password to start the device when it boots after, it's obviously encrypted.
Flashing back to the "Full" package yet again to restore it working.
Edit: I thought double posts would be auto-merged...
Edit 2: "Format Data" left my device encrypted and the only way around it was a factory reset!
Edit 3: I read over the instructions in the TWRP thread again and I think I've found what I missed. If I don't update this thread again by tomorrow that means I've figured it out and everything should be fine.
Thank you everyone who tried to help.
Can you please give me instructions of what you did to upgrade to Nougat, I'm like you when started the upgrade on B29 Unlocked and rooted. I like the way of EDL process but It is a little vague and I don't want to brick my phone. Thanks in advance.
Cyrus D. said:
Well I tried starting at that point again since I didn't allow modifications in TWRP this time, and it actually booted Android but then asks for a password... what?
So something about allowing modifications in TWRP seems to be the culprit, but then I'm unsure why it would ask for a password to start the device when it boots after, it's obviously encrypted.
Flashing back to the "Full" package yet again to restore it working.
Edit: I thought double posts would be auto-merged...
Edit 2: "Format Data" left my device encrypted and the only way around it was a factory reset!
Edit 3: I read over the instructions in the TWRP thread again and I think I've found what I missed. If I don't update this thread again by tomorrow that means I've figured it out and everything should be fine.
Thank you everyone who tried to help.
Click to expand...
Click to collapse
romeoh said:
Can you please give me instructions of what you did to upgrade to Nougat, I'm like you when started the upgrade on B29 Unlocked and rooted. I like the way of EDL process but It is a little vague and I don't want to brick my phone. Thanks in advance.
Click to expand...
Click to collapse
Hi...I ran into your original issue and I believe it's related to dm-verify. For anyone that runs into this again, try flashing a dm-verify disabling zip and see if it'll boot again. This was the only way I could get the phone to boot after upgrading to nougat...not sure why this is an issue though as (I think) I had the stock bootstack in place along with stock System files.
Here is a link to the dm-verify disabling tool I used:
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
flyer_andy said:
Hi...I ran into your original issue and I believe it's related to dm-verify. For anyone that runs into this again, try flashing a dm-verify disabling zip and see if it'll boot again. This was the only way I could get the phone to boot after upgrading to nougat...not sure why this is an issue though as (I think) I had the stock bootstack in place along with stock System files.
Here is a link to the dm-verify disabling tool I used:
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
Click to expand...
Click to collapse
This is clearly posted in the TWRP thread.
flyer_andy said:
Hi...I ran into your original issue and I believe it's related to dm-verify. For anyone that runs into this again, try flashing a dm-verify disabling zip and see if it'll boot again. This was the only way I could get the phone to boot after upgrading to nougat...not sure why this is an issue though as (I think) I had the stock bootstack in place along with stock System files.
Here is a link to the dm-verify disabling tool I used:
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
Click to expand...
Click to collapse
Thanks, already read the TWRP thread and found what I was missing.
romeoh said:
Can you please give me instructions of what you did to upgrade to Nougat, I'm like you when started the upgrade on B29 Unlocked and rooted. I like the way of EDL process but It is a little vague and I don't want to brick my phone. Thanks in advance.
Click to expand...
Click to collapse
I used the EDL method in the end. Part of the reason I set that up to begin with was just in case in the future I brick something, I'll have the ability to recover from anything prepared.
The step I missed which resulted in a brick was installing SuperSU (since I wanted root anyway, or you can disable dm-verity as the other fellow posted here) after allowing TWRP to be able to do modifications. Then I ended up with more bricks because I used SuperSU 2.79-SR2 and SR3, I thought it was fine since SR2 is what I was using with Marshmallow, apparently not, you have to use a non-SR version of 2.79 with Nougat.
So in summary, from EDL mode I:
1 - Installed the "Full" EDL package.
2 - Installed the "TWRP" EDL package, or you can flash it from Fastboot mode which might be more convenient since you'll have to restart EDL mode after flashing the first package to get it working/ready to flash in EDL mode again.
3 - Gave TWRP permission to do modifications and immediately (without rebooting/starting which would result in a brick) installed SuperSU 2.79 (non-SR), then rebooted (this could take a few mins as it says and can bootloop a few times).
If you said no to permissions for SuperSU and it's not giving you the option again you can reflash SuperSU then reboot to bootloader then reboot to recovery, that should make it show the option again. And in case you're not aware, to make changes to system files and such permanent when you have root, you have to enter a command in TWRP's terminal emulator or ADB shell. I think it was "reboot disemmcwp", it may need "SU" in front if you're doing it through an ADB shell in Windows, I'm not sure. Not quotes of course. Search the forums to find out for sure, it had to be in a guide somewhere.
Edit: Just to be clear, for step 2, when I said "or you can flash it from Fastboot" I meant TWRP in general, not the TWRP EDL package.
Cyrus D. said:
Thanks, already read the TWRP thread and found what I was missing.
I used the EDL method in the end. Part of the reason I set that up to begin with was just in case in the future I brick something, I'll have the ability to recover from anything prepared.
The step I missed which resulted in a brick was installing SuperSU (since I wanted root anyway, or you can disable dm-verity as the other fellow posted here) after allowing TWRP to be able to do modifications. Then I ended up with more bricks because I used SuperSU 2.79-SR2 and SR3, I thought it was fine since SR2 is what I was using with Marshmallow, apparently not, you have to use a non-SR version of 2.79 with Nougat.
So in summary, from EDL mode I:
1 - Installed the "Full" EDL package.
2 - Installed the "TWRP" EDL package, or you can flash it from Fastboot mode which might be more convenient since you'll have to restart EDL mode after flashing the first package to get it working/ready to flash in EDL mode again.
3 - Gave TWRP permission to do modifications and immediately (without rebooting/starting which would result in a brick) installed SuperSU 2.79 (non-SR), then rebooted (this could take a few mins as it says and can bootloop a few times).
If you said no to permissions for SuperSU and it's not giving you the option again you can reflash SuperSU then reboot to bootloader then reboot to recovery, that should make it show the option again. And in case you're not aware, to make changes to system files and such permanent when you have root, you have to enter a command in TWRP's terminal emulator or ADB shell. I think it was "reboot disemmcwp", it may need "SU" in front if you're doing it through an ADB shell in Windows, I'm not sure. Not quotes of course. Search the forums to find out for sure, it had to be in a guide somewhere.
Click to expand...
Click to collapse
Many thanks body, As you said using EDL mode is great to unbrake your phone from any state plus it reminds me with Odin that's why I like this way it's very simple, but as you know this is not Samsung phone and it has so many complications. ???
romeoh said:
Many thanks body, As you said using EDL mode is great to unbrake your phone from any state plus it reminds me with Odin that's why I like this way it's very simple, but as you know this is not Samsung phone and it has so many complications.
Click to expand...
Click to collapse
No problem. I threw in an edit to my last post to clarify point 2 in case you thought I meant you can flash the EDL package from Fastboot mode, I meant TWRP in general. In case you forgot the command to use in the ADB shell it's "fastboot flash recovery FileName.img" (twrp-3.0.4-1-ailsa_ii.img in my case).
If you already had the "reboot disemmcwp"/"SU reboot disemmcwp" step done you don't need to do it again.
And just some general information for you regarding my experience with Nougat so far:
1 - When I started it I selected Canadian English as my language. This apparently disables ZTE voice functions, or Nougat is missing it in general. It's missing from the menus and when I hold the back key it said "Only English and Spanish supported". Piss poorly done as usual, ZTE, since the pronunciation of Canadian and American English is nearly identical with very few exceptions, might as well have left American English enabled for voice commands. So I went into the menu and selected just "English" as my system language, and now the option to set Canadian English is missing entirely, and voice functions are still missing. Holding the back key just results in nothing now instead of the "Only English and Spanish supported" message. So I'm saying I don't know if ZTE voice functions are still there, someone else can answer this, or I guess you'll find out.
2 - Google's Timely alarm app (and possibly other alarms) still don't work properly and will be off by several minutes, so I'm stuck using the default sucky clock app until I find something else that works.
3 - The default apps are all still the exact same trash. If you really want to use the AKM "32 bit" (truncated to 16 bit output) Hi-Fi DAC and amp you're still stuck with the garbage laggy default music app, which now has some sort of bonus lag/stutter. People claiming that you can use the DAC with something like PowerAmp are sadly mistaken, that sounds so different and lower quality than when using the stock music app and even says it's using the SD 820's 24 bit DAC when set to Hi-Fi output. There's even a ridiculous rumour going around that the Axon 7 doesn't have the SD 820's DAC which is retarded, ZTE can't pick and choose components of SoCs supplied by Qualcomm, they just buy some of their stock of what's already made. It's definitely in there, whether or not it's enabled is another story.
4 - Battery life is worse, this is at least partly because there is no Xposed support for Nougat yet so I can't enable the Greenify module to allow really aggressive dozing and dozing on the go (which I thought Nougat was supposed to support?). It could also be partly due to my battery being rapidly degraded from Daydream mode being a firey hell inferno. It heated my battery up to 48C and over 42C in other cases even with my best efforts to keep it cool by enabling Ultra Power Saving Mode (which Daydream may be overriding) and shoving in aluminium foil to act as a heatsink. All phones from reports so far overheat horribly when using Daydream, especially the Pixel XL. It's not surprising that the Axon 7 rapidly overheats as well considering it literally uses the battery as a heatsink; a heatpipe carries heat from the SoC to the battery. I would have not bought the A7 if I knew this.
Edit: I forgot -
5 - ZTE locker no longer allows browsing all of their past content, only what they allow per day, which so far for me has only been the same crap and never anything new. Too bad, I liked some of their old content, though it was all 1080p and not 1440p. Oh well.
Cyrus D. said:
No problem. I threw in an edit to my last post to clarify point 2 in case you thought I meant you can flash the EDL package from Fastboot mode, I meant TWRP in general. In case you forgot the command to use in the ADB shell it's "fastboot flash recovery FileName.img" (twrp-3.0.4-1-ailsa_ii.img in my case).
If you already had the "reboot disemmcwp"/"SU reboot disemmcwp" step done you don't need to do it again.
And just some general information for you regarding my experience with Nougat so far:
1 - When I started it I selected Canadian English as my language. This apparently disables ZTE voice functions, or Nougat is missing it in general. It's missing from the menus and when I hold the back key it said "Only English and Spanish supported". Piss poorly done as usual, ZTE, since the pronunciation of Canadian and American English is nearly identical with very few exceptions, might as well have left American English enabled for voice commands. So I went into the menu and selected just "English" as my system language, and now the option to set Canadian English is missing entirely, and voice functions are still missing. Holding the back key just results in nothing now instead of the "Only English and Spanish supported" message. So I'm saying I don't know if ZTE voice functions are still there, someone else can answer this, or I guess you'll find out.
2 - Google's Timely alarm app (and possibly other alarms) still don't work properly and will be off by several minutes, so I'm stuck using the default sucky clock app until I find something else that works.
3 - The default apps are all still the exact same trash. If you really want to use the AKM "32 bit" (truncated to 16 bit output) Hi-Fi DAC and amp you're still stuck with the garbage laggy default music app, which now has some sort of bonus lag/stutter. People claiming that you can use the DAC with something like PowerAmp are sadly mistaken, that sounds so different and lower quality than when using the stock music app and even says it's using the SD 820's 24 bit DAC when set to Hi-Fi output. There's even a ridiculous rumour going around that the Axon 7 doesn't have the SD 820's DAC which is retarded, ZTE can't pick and choose components of SoCs supplied by Qualcomm, they just buy some of their stock of what's already made. It's definitely in there, whether or not it's enabled is another story.
4 - Battery life is worse, this is at least partly because there is no Xposed support for Nougat yet so I can't enable the Greenify module to allow really aggressive dozing and dozing on the go (which I thought Nougat was supposed to support?). It could also be partly due to my battery being rapidly degraded from Daydream mode being a firey hell inferno. It heated my battery up to 48C and over 42C in other cases even with my best efforts to keep it cool by enabling Ultra Power Saving Mode (which Daydream may be overriding) and shoving in aluminium foil to act as a heatsink. All phones from reports so far overheat horribly when using Daydream, especially the Pixel XL. It's not surprising that the Axon 7 rapidly overheats as well considering it literally uses the battery as a heatsink; a heatpipe carries heat from the SoC to the battery. I would have not bought the A7 if I knew this.
Edit: I forgot -
5 - ZTE locker no longer allows browsing all of their past content, only what they allow per day, which so far for me has only been the same crap and never anything new. Too bad, I liked some of their old content, though it was all 1080p and not 1440p. Oh well.
Click to expand...
Click to collapse
Omg bro, To be honest I hate the software experience on that phone. It is the only thing that turning me off from it. I played a little with my brother's S7 edge the other day, and believe me the software experience is extraordinary. However I noticed that the S7 edge overheats a lot too without even using the daydream. In my opinion I think Axon 7 lacks in hardware wise a bigger battery and the support of the new RCS messaging feature, and in software wise a whole new developed system.

Touch screen works in TWRP no touch booted

Okay. This is an odd one for me. bought another axon 7 bc it was cheap. swapped in my old board and battery because it was charging and running really hot. (ive owned 4 axon 7 now, it was the hottest ever) so surgery went fine. upon booting, the touch screen, does not respond to touch. while within recovery (twrp by nfound) touchscreen works perfectly. i really dont know what to do to it. i have tried to restore all sorts of backups, but every one has the same issue. ive tried not including EFS and tried it included. if the screen wasnt working in TWRP, id question my hardware labor, but im kind of stumped. i keep trying to download B19 nougat edl, but the download keeps failing. (thanks tmobile and my in-laws wifi). my question is coming from a functional custom recovery is there a way to flash or restore stock recovery? i know i can EDL eventually, i was just wondering if there is an easier way?
EDL fails to complete using any of the EDL files i have tried so far using
Secondary question, is there any EDL thats works as a necessary starting point? i.e.- on moto devices, many firmwares were not backward flashable. ultimately, i just want to know if i can EDL Marshmallow or if that is even possible. i have attempted B15, B19, and B32 with no success.
kitcostantino said:
Okay. This is an odd one for me. bought another axon 7 bc it was cheap. swapped in my old board and battery because it was charging and running really hot. (ive owned 4 axon 7 now, it was the hottest ever) so surgery went fine. upon booting, the touch screen, does not respond to touch. while within recovery (twrp by nfound) touchscreen works perfectly. i really dont know what to do to it. i have tried to restore all sorts of backups, but every one has the same issue. ive tried not including EFS and tried it included. if the screen wasnt working in TWRP, id question my hardware labor, but im kind of stumped. i keep trying to download B19 nougat edl, but the download keeps failing. (thanks tmobile and my in-laws wifi). my question is coming from a functional custom recovery is there a way to flash or restore stock recovery? i know i can EDL eventually, i was just wondering if there is an easier way?
EDL fails to complete using any of the EDL files i have tried so far using
Secondary question, is there any EDL thats works as a necessary starting point? i.e.- on moto devices, many firmwares were not backward flashable. ultimately, i just want to know if i can EDL Marshmallow or if that is even possible. i have attempted B15, B19, and B32 with no success.
Click to expand...
Click to collapse
you should be able to EDL any update without problems. Use EDL Tool, that one works even better than miflash.
What a mess. ? Maybe an EDL flash on the newer board would have fixed the thermal problems...
Try an IDM for downloading stuff. If the download fails you can simply resume it no problem. IDMs on Windows are crap, but this one works perfectly (on Android, that is):
https://play.google.com/store/apps/details?id=idm.internet.download.manager
Choose an username... said:
you should be able to EDL any update without problems. Use EDL Tool, that one works even better than miflash.
What a mess. Maybe an EDL flash on the newer board would have fixed the thermal problems...
Try an IDM for downloading stuff. If the download fails you can simply resume it no problem. IDMs on Windows are crap, but this one works perfectly (on Android, that is):
https://play.google.com/store/apps/details?id=idm.internet.download.manager
Click to expand...
Click to collapse
Pretty much par for the course with me and Axon 7's. Simple op impossible. lol.
I just flashed b32 which Miflash says flashed successfully, yet as was the case after b15N and b2xN the splash screen pops up, the image of stock recovery flashes just for a sec, several red flashes, and power off.
It takes a try or two to get EDL mode after that. i guess tomorrow (left it at work on my desk) the phones original board is going back in. lol.
So i swapped back to the board that came in the phone and touch works perfectly. that board was missing the pink paste on the back of the SOC. after having it run 115-125° F, i decided to swap the battery with my good one and add the pink gummy stuff too. on stock it got so hot it would freeze and shut down, and now bl unlocked on O RR, i have to undervolt -25 global to keep it stable. i did finally manage to get full EDLs to work, but the SOC just seems faulty or tweaked. i imagine it is just one that runs hotter. also, in swapping the screen back, i have concluded that the other board i had must have a connector issue for the touch display. i may try to resinstall it later. kinda tired of screwing with it for now. any input is appreciated. thanks
EDit:
hot board made cool by flashing back as far as i could go, but now it has no IMEI. lol.
UPDATE: finally figured out the b15 full edl i was using was what was killing the screen. flashed back to b20 and screen worked fine. now both phones do not have IMEIs, though. win some, lose some. lol

Vendor, Bootstack and Kernel questions for running AEX V6 GSI

Hey guys!
Just a couple of quick regarding the right vendor, bootstack and custom kernels I can use for my Axon 7
Im running...
AOSP Extended V6 GSI
Lineage 15.1 vendor
B20_Bootstack_by_Verequies.zip
I wonder if anyone can point me to the best bootstack and vendor for running AEX V6 GSI. Ive used the universal bootstack provided by Draken from here https://androidfilehost.com/?w=files&flid=270519. Which one of these would run the best if you know? Also with the bootstack I want to retain all of my button combination options (recovery and EDL) and offline charging but I can do without the warning screen.... ok I REALLY want to get rid of the warning screen.
Also I found this page https://github.com/AospExtended/platform_vendor_aosp that claims to have a AOSP vendor platform and I wanted to know if this would work.
My device was Treble checked and is Treble enabled so Im guessing I dont have to flash an EDL package with MiFlash anymore and just flash the partitions. (Confirm).
The only kernel I have is whatever came with the AEX ROM. I havent flashed anything custom yet other than the files I used for the initial install. Reason Im asking about a kernel is because Ive noticed the battery life isnt that great so Im looking for one that can give me more in that area first and foremost. Any other perks come secondary.
Thanks in advance and XDA has saved me and my phone tinkering more times than I can count. I appreciate all of your hard work! :highfive:
juniorD said:
Hey guys!
Just a couple of quick regarding the right vendor, bootstack and custom kernels I can use for my Axon 7
Im running...
AOSP Extended V6 GSI
Lineage 15.1 vendor
B20_Bootstack_by_Verequies.zip
I wonder if anyone can point me to the best bootstack and vendor for running AEX V6 GSI. Ive used the universal bootstack provided by Draken from here https://androidfilehost.com/?w=files&flid=270519. Which one of these would run the best if you know? Also with the bootstack I want to retain all of my button combination options (recovery and EDL) and offline charging but I can do without the warning screen.... ok I REALLY want to get rid of the warning screen.
Also I found this page https://github.com/AospExtended/platform_vendor_aosp that claims to have a AOSP vendor platform and I wanted to know if this would work.
My device was Treble checked and is Treble enabled so Im guessing I dont have to flash an EDL package with MiFlash anymore and just flash the partitions. (Confirm).
The only kernel I have is whatever came with the AEX ROM. I havent flashed anything custom yet other than the files I used for the initial install. Reason Im asking about a kernel is because Ive noticed the battery life isnt that great so Im looking for one that can give me more in that area first and foremost. Any other perks come secondary.
Thanks in advance and XDA has saved me and my phone tinkering more times than I can count. I appreciate all of your hard work! :highfive:
Click to expand...
Click to collapse
how would your phone not be 'treble-enabled' if you are using a GSI? Food for thoughts
Also, which bootstack are you running? Draken's or Verequies's? If Ver's, download the NO-SPLASH bootstack. That one's going to do what you want.
When I installed it for some reason it blackscreened my phone, the solution is just to get Oki's B12 EDL bootstack from his androidfilehost profile and flash it via edl (if you get dfu, use MultiDL).
Use the stock kernel or try Schwifty kernel, maybe Crimson too. Just test yourself
Choose an username... said:
how would your phone not be 'treble-enabled' if you are using a GSI? Food for thoughts
Also, which bootstack are you running? Draken's or Verequies's? If Ver's, download the NO-SPLASH bootstack. That one's going to do what you want.
When I installed it for some reason it blackscreened my phone, the solution is just to get Oki's B12 EDL bootstack from his androidfilehost profile and flash it via edl (if you get dfu, use MultiDL).
Use the stock kernel or try Schwifty kernel, maybe Crimson too. Just test yourself
Click to expand...
Click to collapse
As I said in the initial post Im using the Verequies boot which is the No Splash which I dont mind but i want to get rid of the warning screen. Also if this is the one with the gold boot screen I am definitely gonna have to change that as it is ugly. LOLOL!
Im asking about who's tested what especially with kernels so I dont brick my phone as Ive already done this twice so I know what Ive used and will not use again.
But as I said I also found an AEX specific vendor or one labeled as one. I put the link in my OP so before I test it Im asking if anyone knows about it before I wipe my phone for no reason.
Im definitely going to try those kernels cuz like I said the battery life on the stock for the AEX V6 GSI isnt that great. LOS 16 was better but for some reason Lineage OS kept causing my phone to freeze and randomly reboot. I was using it for 3 days and it rebooted prolly 5-6 times running normally. So I dont think Im going back to LOS and will prolly stick to Havoc, Arrow or AEX for now.
juniorD said:
As I said in the initial post Im using the Verequies boot which is the No Splash which I dont mind but i want to get rid of the warning screen. Also if this is the one with the gold boot screen I am definitely gonna have to change that as it is ugly. LOLOL!
Im asking about who's tested what especially with kernels so I dont brick my phone as Ive already done this twice so I know what Ive used and will not use again.
But as I said I also found an AEX specific vendor or one labeled as one. I put the link in my OP so before I test it Im asking if anyone knows about it before I wipe my phone for no reason.
Im definitely going to try those kernels cuz like I said the battery life on the stock for the AEX V6 GSI isnt that great. LOS 16 was better but for some reason Lineage OS kept causing my phone to freeze and randomly reboot. I was using it for 3 days and it rebooted prolly 5-6 times running normally. So I dont think Im going back to LOS and will prolly stick to Havoc, Arrow or AEX for now.
Click to expand...
Click to collapse
verequies's splash hasn't got the 5 sec screen, but it has a weird 3 logo splash. I'm using Oki's B12 bootstack (the gold splash one, really ugly lol) but I made my own splash to replace it. it has no 5 sec screen. Oki's is based on B12 though.
Choose an username... said:
verequies's splash hasn't got the 5 sec screen, but it has a weird 3 logo splash. I'm using Oki's B12 bootstack (the gold splash one, really ugly lol) but I made my own splash to replace it. it has no 5 sec screen. Oki's is based on B12 though.
Click to expand...
Click to collapse
Yeah the Splash version takes away the offline charging and the EDL button combo which I want to keep. I just wanna get rid of the Warning screen I guess and keep all the other functionality and Im good!

Random bootloaders coming up flashing but no rom and no data on sims card

This oneplus6t is gettin on my nerves. Everytime i do the same thing it does something different. when i put on twrp and flash a rom i get this new bootloader that doesnt really let me do anything. Sometimes it just keeps going into fastboot. when the new bootloader comes up i got to put twrp back on and after doing it like 5 times i get tired of it. Is it a partition thing? Why is rooting so much harder then when i did it a few years ago.....................
Anyway i need help getting a rom on my phone. Thankfully the phone seems to back up oxygen cuz after a few factory resets oxygen just RANDOMLY came up even though i flashed another rom. TWRP and magisk is on the phone. Im also trying to get data working on my phone. I took the sims card(Verzion) out and put it in my Sgalaxy 7 for the time being and data works just fine on that.
O.P.P said:
This oneplus6t is gettin on my nerves. Everytime i do the same thing it does something different. when i put on twrp and flash a rom i get this new bootloader that doesnt really let me do anything. Sometimes it just keeps going into fastboot. when the new bootloader comes up i got to put twrp back on and after doing it like 5 times i get tired of it. Is it a partition thing? Why is rooting so much harder then when i did it a few years ago.....................
Anyway i need help getting a rom on my phone. Thankfully the phone seems to back up oxygen cuz after a few factory resets oxygen just RANDOMLY came up even though i flashed another rom. TWRP and magisk is on the phone. Im also trying to get data working on my phone. I took the sims card(Verzion) out and put it in my Sgalaxy 7 for the time being and data works just fine on that.
Click to expand...
Click to collapse
you're using oxygenos on your other slot now, did you format data before or after flashing your rom? if you haven't then that's why you keep going to fastboot/bootloader mode
@O.P.P.
There are other AB partition devices that are much more of a mess to use. ?? It's one of those things where you have to understand it. It took me a minute and I bricked a Motorola G7 Power a few times during my quest to learn about AB partition devices. Thank God for Blank flash files and all the people who helped me unbrick my G7 Power more than a few times. I guess I'm a slow learner. I feel your pain though. One day it just all made sense for me after reading countless information about it all. You'll understand it. Made me feel really dumb when I finally did.
I recommend reading Funk Wizards guide over in guides section of the forums for OnePlus 6/t. The data not working ...I Are your imei # present or are the gone? In that guide the op tells how to backup your efs using terminal commands. If and when you get your device working again I would most definitely get those backed up and throw them on your PC or usb drive or a cloud or all of the above. This is important because if you have a situation come up where your imei is gone and you have no data you can fastboot flash these backed up bin files to your device and restore your imei and get data working. I've read there has been some users who didn't backup these two bin files and we're not able to get data and imei restored.
How I install a rom on my converted OnePlus 6t. This installation process varies depending on whether or not whatever rom I'm installing comes with gapps and or TWRP and of course you don't want to install global OOS on another model device. Since I converted my T-Mobile OnePlus 6t using guide and msm tool I now use global or international OnePlus 6t roms, firmware... Example Pixel Experience rom installation:
Boot TWRP
Flash OOS 10.3.6 global from repo xda thread
Flash Pixel Experience rom
Flash TWRP installer zip
Flash finalize zip
Format data
Reboot system.
Start to set up device then at some point enable developer options and usb debugging and doable any lock screen and boot twrp and flash magisk for root and reboot system. That is how I install a rom that has gapps but not twrp included in rom zip. Finalize can he found with a quick search on xda. It copies firmware to other slot on your AB partition device so that you don't have to. Saves 5-6 minutes and works great.
I would head over to msm tool thread and maybe give that a go. Msm tool is an awesome tool and much of the time a last resort depending on what's going on... If you have a T-Mobile model device be sure and use the patched tool. You'll see all that on msm tool thread. Hope this helps some..
Edit
Sounds like maybe you needed to format data after your install process. If you don't it usually sends you back to twrp or bootloader mode ..
Sent from my OnePlus6T using XDA Labs

OnePlus 8 Pro refuses to install TWRP. Qualcomm Crash Dumps every time. Any advice?

I want to install TWRP as my recovery I've tried at least four different versions that are listed here and a few others from other links:
https://forum.xda-developers.com/t/...p-for-oneplus-8-8-pro-unified-stable.4101313/
I'm not having driver issues anymore so I'm working with adb and fastboot fine. All commands are going through fine and I've tried flashing to recovery_a and recovery_b. Factory resetting doesn't resolve the issue. Every walkthrough I find I get to says flash then boot to TWRP but every time I flash it qualcomm dumps and every time I boot to it it qualcomm dumps.
Is there something corrupted in my recovery I need to wipe somehow? If so how do I wipe it because the only command I found online that would run was fastboot -w and that didn't fix the issue either.
Honestly really annoying at this. This is my 4th OnePlus phone and I've never had so many issues flashing it.
Edit:
I have also tried to do whatever steps are needed to go back to base stock and OS and it doesn't seem to work either. Any help would be appreciated.
Edit 2:
I did it. For anyone who finds this thread in the future the MSM tool did finally work. This is the video I used in the end
(I muted it.) and the first few starts it failed. I went into the properties of the MSM exe and under compatibility checked ran as admin. I also did install the qualcomm driver at some point way before this so not sure if that helped. The MSM tool still didn't work until I started it, turned my phone off, held both volume buttons (not the power) while plugging the phone in. All the stuff online I saw had people starting the program at this point but mine had started already and was in a "waiting for device" state when it worked.
What a lifesaver. Won't be messing around with this again until TWRP is available.
Because you are unable to flash phone's Stock ROM take phone to authorized service center and let them fix it.
Flash stock recovery. TWRP is but compatible with OOS11 for 8/Pro.
Edit: not
Lossyx said:
Flash stock recovery. TWRP is but compatible with OOS11 for 8/Pro.
Click to expand...
Click to collapse
I have had so much trouble figuring that out too. Do you have a good link for that? I can't find an easy way to do it. I've seen people recommend the msmdownloadtool but every time I use it it doesn't pick up my phone.
I've settled with Lineage OS and Gapps until I figure out more.
TheFloppyDisk said:
I have had so much trouble figuring that out too. Do you have a good link for that? I can't find an easy way to do it. I've seen people recommend the msmdownloadtool but every time I use it it doesn't pick up my phone.
I've settled with Lineage OS and Gapps until I figure out more.
Click to expand...
Click to collapse
Meant to say it's **not** compatible with Android 11 yet.
Lossyx said:
Meant to say it's **not** compatible with Android 11 yet.
Click to expand...
Click to collapse
Sorry if I wasn't clear either. I was wondering if you have a good resource for flashing the stock again. I haven't been able to myself.
TheFloppyDisk said:
Sorry if I wasn't clear either. I was wondering if you have a good resource for flashing the stock again. I haven't been able to myself.
Click to expand...
Click to collapse
The same way to flashed TWRP.
fastboot flash recovery recovery_a and _b.
In the future, you should not flash both slots, just flash without specifying _a or _b.
Recovery image can be obtained here;
Android Dumps / oneplus / oneplus8pro · GitLab
GitLab Enterprise Edition
dumps.tadiphone.dev
Although i am not sure which OOS version you use, so you might have to change branch
Lossyx said:
The same way to flashed TWRP.
fastboot flash recovery recovery_a and _b.
In the future, you should not flash both slots, just flash without specifying _a or _b.
Recovery image can be obtained here;
Android Dumps / oneplus / oneplus8pro · GitLab
GitLab Enterprise Edition
dumps.tadiphone.dev
Although i am not sure which OOS version you use, so you might have to change branch
Click to expand...
Click to collapse
I hate to be this much of a noob about it but I see a recovery file listed in the link you sent. Is that the recovery I flash? And if so after flashing is this branch also a stock rom? I've been trying for a while now just to get back to the basic oxygen that comes with the phone but it's been a nightmare for me and it feels like no resource I find fully explains it.
TheFloppyDisk said:
I hate to be this much of a noob about it but I see a recovery file listed in the link you sent. Is that the recovery I flash? And if so after flashing is this branch also a stock rom? I've been trying for a while now just to get back to the basic oxygen that comes with the phone but it's been a nightmare for me and it feels like no resource I find fully explains it.
Click to expand...
Click to collapse
If you want OOS back / new start, best way is really to use MSM. Haven't really used it, so can't help you much. There are tutorials online / YouTube though
Lossyx said:
If you want OOS back / new start, best way is really to use MSM. Haven't really used it, so can't help you much. There are tutorials online / YouTube though
Click to expand...
Click to collapse
Gotcha. Unfortunately I haven't been able to get MSM to recognize my phone yet but I guess I will keep working on it and see what I can do. Thanks for your help.
TheFloppyDisk said:
Gotcha. Unfortunately I haven't been able to get MSM to recognize my phone yet but I guess I will keep working on it and see what I can do. Thanks for your help.
Click to expand...
Click to collapse
It is very sensitive to which USB port you use. For some people only USB2.0 works, for me USB3 works fine as long as it's chipset USB3. The second ASMedia controller doesn't work.
Also, use original cable, and switch off the phone completely, get MSM to the point it's waiting for device so start the download before connecting phone, then while holding the volume keys connect the USB cable and it should instantly start flashing.

Categories

Resources