Related
Hi guys. I very narrowly (somehow) managed to recover from almost bricking my phone.
I successfully S-Off'd my phone, and previously successfully installed TWRP. I tried to install this ROM:
https://forum.xda-developers.com/ve...m-perfumewl-m60-dev-edition-unlocked-t3442969
When I tried the to flash the ZIP for firmware and for the ROM, the firmware wouldn't install. I tried some other stuff and basically almost bricked my phone. Some how got it to suddenly start being able to use the htc_fastboot commands (????????) and was able to start installing the zip for stock... but it ran an error, I ran it again and it froze... then I forced my phone to reboot and somehow I'm back to having a stock system. No clue what I did.
My question is, can I take a software update on my phone normally (to 7.0) , and then install just that ROM? Or so I need to flash the firmware separately with a command line command? I just don't want to give myself another heart attack tonight. Current firmware version is 1.82.605.6, not rooted, don't believe my recovery is TWRP right now (but I know how to install that one).
I'm just looking for root access and the ability to remove pre-installed Verizon crap (VZW Messager, My Verizon, etc). Thanks guys.
CritKlepka said:
Hi guys. I very narrowly (somehow) managed to recover from almost bricking my phone.
I successfully S-Off'd my phone, and previously successfully installed TWRP. I tried to install this ROM:
https://forum.xda-developers.com/ve...m-perfumewl-m60-dev-edition-unlocked-t3442969
When I tried the to flash the ZIP for firmware and for the ROM, the firmware wouldn't install. I tried some other stuff and basically almost bricked my phone. Some how got it to suddenly start being able to use the htc_fastboot commands (????????) and was able to start installing the zip for stock... but it ran an error, I ran it again and it froze... then I forced my phone to reboot and somehow I'm back to having a stock system. No clue what I did.
My question is, can I take a software update on my phone normally (to 7.0) , and then install just that ROM? Or so I need to flash the firmware separately with a command line command? I just don't want to give myself another heart attack tonight. Current firmware version is 1.82.605.6, not rooted, don't believe my recovery is TWRP right now (but I know how to install that one).
I'm just looking for root access and the ability to remove pre-installed Verizon crap (VZW Messager, My Verizon, etc). Thanks guys.
Click to expand...
Click to collapse
I recommend you install this one instead:
https://forum.xda-developers.com/ve...m-1-85-605-9-aroma-root-root-debloat-t3529732
Follow instructions in OP...or:
1)fastboot flash FW w/o Boot w/ TWRP (htc_fastboot oem rebootRUU, fastboot flash zip...)
2)htc_fastboot reboot-bootloader
3) Finally, go into recovery-- backup and flash ROM (choose root w/ Magisk and debloat)
Thanks, I figured out why it wasn't working before. Used official TWRP, thats why it wasn't working. Wouldn't have thought that'd made that much of a difference.
New problem though; something I really would like to use the Google versions of contacts and dialers. Trying to flash those just made my phone app unusable. So I turned to LineageOS but it REFUSES to boot. Hangs on their little vertical line with a moving circle. Found out AOSP roms don't like VZW firmware? Flashed global firmware, updated through WiFi as much as possible, and then ran into issues with radio, even though I flashed the VZW one. So I reverted those changes, am going through with what you said above to have a working phone (after not having one all day), but any advice on getting Google dialer and contacts? I'd like to use LineageOS but I couldn't get it work at all.
CritKlepka said:
Thanks, I figured out why it wasn't working before. Used official TWRP, thats why it wasn't working. Wouldn't have thought that'd made that much of a difference.
New problem though; something I really would like to use the Google versions of contacts and dialers. Trying to flash those just made my phone app unusable. So I turned to LineageOS but it REFUSES to boot. Hangs on their little vertical line with a moving circle. Found out AOSP roms don't like VZW firmware? Flashed global firmware, updated through WiFi as much as possible, and then ran into issues with radio, even though I flashed the VZW one. So I reverted those changes, am going through with what you said above to have a working phone (after not having one all day), but any advice on getting Google dialer and contacts? I'd like to use LineageOS but I couldn't get it work at all.
Click to expand...
Click to collapse
You've got to read OPs, search threads, etc. Some ROMs work w/ our phone, and some do not. Check out the latest versions of ice and leedroid. Your most likely want to grab the SVN versions is the official versions may not yet support Verizon N firmware
Antny6 said:
You've got to read OPs, search threads, etc. Some ROMs work w/ our phone, and some do not. Check out the latest versions of ice and leedroid. Your most likely want to grab the SVN versions is the official versions may not yet support Verizon N firmware
Click to expand...
Click to collapse
I have been doing a lot of searching, but I've found so many different, conflicting sources of information. For example, one website told me to install LineageOS, was to be on latest Verizon OTA and just normally flash it; that obviously didn't work.
So from what I can see, our choices are Viper, Ice, LeeDroid, NuSense and the one you linked. I'm going to try out LeeDroid... out of curiousity, is there any reason, for example, LeeDroid or Ice haven't posted in this Verizon section with links to their ROMs?
*Edit Two* Dialer wouldn't work out of the "box" so to speak, so I had to go to Phone settings at the bottom, there is a menu called Calling Accounts. Had to go there and tap Receive Incoming Calls... why is that disabled in the first place..? But that seems to be an issue going even as far back as the Nexus 5. But that's how you find the option in the HTC 10 for anyone who comes across this issue too...
Not sure why your having issues with the flashing. Are you doing a full wipe? Not just factory reset. Going from stock to lineage requires a complete format of internal SD card. On the stock roms, most will ask if you are still on marshmallow firmware & are working fine. Again, we need more info on what firmware version your on, version of twrp& how your wiping your device. Most AOSP roms work, but no advanced calling
LOS ROMs will work without issue IF you have flashed the US unlocked firmware at some point in time. This is the only information that we have found from a VzW device with LOS booting and VzW device without. We started a thread awhile ago and is the only known method we currently know of to get LOS booting. Also works for Sprint users.
https://forum.xda-developers.com/verizon-htc-10/how-to/how-to-cm-booting-vzw-vzw-firmware-t3500900
Hello, guys.
Recently, i wanted to install the fulmics ROM (which is awesome) on my LG G6 H870.
So, i've done it, the bootloader has been unlocked, it's rooted right now, and i've got the Fulmics ROM which works perfectly.
But, i still have a question. When i boot up my phone, i've got this message :
"Your device software cannot be checked for corruption. Lock the bootloader. etc..."
This isn't a problem, because i can boot up my phone.
But i just wanted to know if i can remove this message, and how ?
Thank you all for your answers and your help.
This is normal and cannot remove that message. Just ignore it, how many times do you actually reboot for it to be an issue? If you ever need send phone off for repair just flash stock and lock bootloader again.
normal bro don't worry
[/COLOR]
basicreece said:
This is normal and cannot remove that message. Just ignore it, how many times do you actually reboot for it to be an issue? If you ever need send phone off for repair just flash stock and lock bootloader again.
Click to expand...
Click to collapse
dude I've got a question: if you wanted to get your bank's app working again in a custom rom/recovery is it possible to relock the bootloader in order to get older compatibility (mario kart, spotify options, bancoestado) but in a system like PA Quartz 3 or PixelExperience ? Or bootloader wont boot locked another system than LG?
I seriously need those apps but also need Android 10
learning_to said:
[/COLOR]
dude I've got a question: if you wanted to get your bank's app working again in a custom rom/recovery is it possible to relock the bootloader in order to get older compatibility (mario kart, spotify options, bancoestado) but in a system like PA Quartz 3 or PixelExperience ? Or bootloader wont boot locked another system than LG?
I seriously need those apps but also need Android 10
Click to expand...
Click to collapse
Magisk manager and use the magisk hide feature.
HI,
I just got a NIB, HTC 10 Verizon phone that came with Oreo. I immediately unlocked the bootloader, installed latest TWRP and installed Lineage 14.1 Nougat...same version that's running successfully on another HTC 10 VZW I own.
However I just noticed the home button/sensor apparently isn't working, nothing happens when I press or hold it. I unlocked it so fast I really don't know if it worked in the stock rom or not. I tried installing the microg version of Lineage 14.1 and am seeing same issue. I can't find any setting I might have forgotten about to enable it, and the settings there are for it (long press etc) are set.
Does anyone know on an HTC 10 with latest Verizon Oreo, did something change in the firmware so that I need to run an Oreo rom to make it work?
Is there anyway I can test the home button in a terminal or some such to see if it's physically not working? It just seems unlikely to me that a new phone would have a DOA button/sensor and feel like i'm missing something.
thanks
generalnod said:
HI,
I just got a NIB, HTC 10 Verizon phone that came with Oreo. I immediately unlocked the bootloader, installed latest TWRP and installed Lineage 14.1 Nougat...same version that's running successfully on another HTC 10 VZW I own.
However I just noticed the home button/sensor apparently isn't working, nothing happens when I press or hold it. I unlocked it so fast I really don't know if it worked in the stock rom or not. I tried installing the microg version of Lineage 14.1 and am seeing same issue. I can't find any setting I might have forgotten about to enable it, and the settings there are for it (long press etc) are set.
Does anyone know on an HTC 10 with latest Verizon Oreo, did something change in the firmware so that I need to run an Oreo rom to make it work?
Is there anyway I can test the home button in a terminal or some such to see if it's physically not working? It just seems unlikely to me that a new phone would have a DOA button/sensor and feel like i'm missing something.
thanks
Click to expand...
Click to collapse
It doesn't work because you need to have Nougat firmware in order to run LOS 14.1. So you can either downgrade your firmware, or go to LOS 16.
But I'm curious how you could have possibly unlocked the bootloader on a Verizon 10. The only way to unlock the bootloader on that variant is to have s-off, which in of itself would require you to send the phone to the Sunshine team if you're on Oreo...
Tarima said:
It doesn't work because you need to have Nougat firmware in order to run LOS 14.1. So you can either downgrade your firmware, or go to LOS 16.
Click to expand...
Click to collapse
Thanks, I was about to return the phone, seems like an odd quirk doesn't work on 14.1 does on 15.1 and 16. I do not have s-off so I don't think I can downgrade the firmware, without sending it to sunshine (think i read can also send to htc?) first.
However I did find a LOS 15.1 unofficial rom, that so far seems to be working, but haven't popped in the sim yet.
https://forum.xda-developers.com/ht...lineageos-15-1-unofficial-builds-pme-t3808812
And you're correct home button works! I might see if I can compile a Microg version of that 15.1 LOS
Tarima said:
But I'm curious how you could have possibly unlocked the bootloader on a Verizon 10. The only way to unlock the bootloader on that variant is to have s-off, which in of itself would require you to send the phone to the Sunshine team if you're on Oreo...
Click to expand...
Click to collapse
I followed what I think is pretty much the standard procedure
https://wiki.lineageos.org/devices/pme/install
The only unexpected parts where enable oem unlock being greyed out, requiring a connection to the internet at which point it became ungreyed and let me check it. Also in those instructions there's some confusion regarding 'fastboot' / bootloader / download mode, things need to be done in download mode now.
https://forum.xda-developers.com/on...ken-failed-t3263170/post78869656#post78869656
thanks for your help
generalnod said:
Thanks, I was about to return the phone, seems like an odd quirk doesn't work on 14.1 does on 15.1 and 16. I do not have s-off so I don't think I can downgrade the firmware, without sending it to sunshine (think i read can also send to htc?) first.
However I did find a LOS 15.1 unofficial rom, that so far seems to be working, but haven't popped in the sim yet.
https://forum.xda-developers.com/ht...lineageos-15-1-unofficial-builds-pme-t3808812
And you're correct home button works! I might see if I can compile a Microg version of that 15.1 LOS
I followed what I think is pretty much the standard procedure
https://wiki.lineageos.org/devices/pme/install
The only unexpected parts where enable oem unlock being greyed out, requiring a connection to the internet at which point it became ungreyed and let me check it. Also in those instructions there's some confusion regarding 'fastboot' / bootloader / download mode, things need to be done in download mode now.
https://forum.xda-developers.com/on...ken-failed-t3263170/post78869656#post78869656
thanks for your help
Click to expand...
Click to collapse
Glad you were able to solve it.
What the last part tells me is that it wasn't an official Verizon device, since as I said you can't enable oem unlocking and unlock the bootloader on those. Nevertheless it seems you have an unlocked bootloader anyway, which is good. With that said, you can probably downgrade even without s-off, and there is a (risky) procedure on how to do that around. I don't think you'll need it now though since you're up and running.
Same same?
generalnod said:
Thanks, I was about to return the phone, seems like an odd quirk doesn't work on 14.1 does on 15.1 and 16. I do not have s-off so I don't think I can downgrade the firmware, without sending it to sunshine (think i read can also send to htc?) first.
However I did find a LOS 15.1 unofficial rom, that so far seems to be working, but haven't popped in the sim yet.
https://forum.xda-developers.com/ht...lineageos-15-1-unofficial-builds-pme-t3808812
And you're correct home button works! I might see if I can compile a Microg version of that 15.1 LOS
I followed what I think is pretty much the standard procedure
https://wiki.lineageos.org/devices/pme/install
The only unexpected parts where enable oem unlock being greyed out, requiring a connection to the internet at which point it became ungreyed and let me check it. Also in those instructions there's some confusion regarding 'fastboot' / bootloader / download mode, things need to be done in download mode now.
https://forum.xda-developers.com/on...ken-failed-t3263170/post78869656#post78869656
thanks for your help
Click to expand...
Click to collapse
I bought my HTC 10 Verizon on eBay new other which they explained is either a store model or excess stock.
HTC 10 32GB 6545LVW Glacier Silver (Verizon)+Unlocked GSM Smartphone Cell Phone https://ebay.us/rLPGq8
download mode said that it was locked s-on.
htc_pmewl
mid-2ps650000
this came with android 6.0.1
oem unlock was not listed in the developer options.
The sunshine app APK was able to gain temporary root and confirm compatibility but failed to unlock on the first attempt. I had many items disabled so I did a factory reset and was able to gain S off using the app but my download mode still says locked.
I installed TWRP through a DB and was able to then install 14.1 15.1 and 16 lineageos.
I tried 16.O then switch to 15.1 then switched to 14.1 then back to 15.1 and then back to 14.1 via twrp backup.
Everything works great except my home button and fingerprint sensor did not work on 15.1 or 16. They both work on 6.0.1 stock and lineageos 14.1. I tried on 15.1 and 16 to enable the additional buttons to use the fingerprint button as the home button and it still did not work.
I'm also not able to backup system image the air says that it's mounted as read only. It seems to get about 90% done and says fails to write in the log.
I can back up everything else using TWRP such as data and system just not system image.
resolved
benjuken said:
I bought my HTC 10 Verizon on eBay new other which they explained is either a store model or excess stock.
HTC 10 32GB 6545LVW Glacier Silver (Verizon)+Unlocked GSM Smartphone Cell Phone https://ebay.us/rLPGq8
download mode said that it was locked s-on.
htc_pmewl
mid-2ps650000
this came with android 6.0.1
oem unlock was not listed in the developer options.
The sunshine app APK was able to gain temporary root and confirm compatibility but failed to unlock on the first attempt. I had many items disabled so I did a factory reset and was able to gain S off using the app but my download mode still says locked.
I installed TWRP through a DB and was able to then install 14.1 15.1 and 16 lineageos.
I tried 16.O then switch to 15.1 then switched to 14.1 then back to 15.1 and then back to 14.1 via twrp backup.
Everything works great except my home button and fingerprint sensor did not work on 15.1 or 16. They both work on 6.0.1 stock and lineageos 14.1. I tried on 15.1 and 16 to enable the additional buttons to use the fingerprint button as the home button and it still did not work.
I'm also not able to backup system image the air says that it's mounted as read only. It seems to get about 90% done and says fails to write in the log.
I can back up everything else using TWRP such as data and system just not system image.
Click to expand...
Click to collapse
-------------------------------------------
after the steps above, I installed this
3.18.605.13_combined_NoBoot_Twrp3.2.1-4_firmware.zip using htc_fastboot
wiped
then this
lineage-16.0-20190310-UNOFFICIAL-pme.zip using twrp from sd card
open_gapps-arm64-9.0-aroma-20190316 (add more zips in the same install)
now the fingerprint setup and home button are working without turning it on in settings > system > additional buttons.
still locked s-off is showing in download mode.
all fixed
I originally posted this on the Lineage 16.0 thread, but I figured it might not hurt to post this in a stand-alone thread.
I'm having some issues with the baseband/wifi after successfully flashing Lineage 16.0
I did do a complete nandroid backup in TWRP before flashing the copy-partitions-ab.zip, and I followed the instructions at the beginning of the thread, sideloaded the ROM, and it booted just fine, but I kept getting "No SIM card inserted" . Now when I try to restore the EFS and Persistent partitions from the backup, I still don't get a working baseband...
I even tried restoring the backup I made previously, but I still was not able to make the baseband work. I then tried flashing this stock ROM: https://forum.xda-developers.com/g6-plus/how-to/rom-official-stock-pie-9-ppw29-116-11-t3892935 through fastboot, and since this hasn't fixed the problem, I tried restoring the EFS and Persistent partitions from the backup, but still no go.
Does anyone know what I can do to fix this? Not being able to receive/make calls or connect to a wifi network basically renders this phone useless...
Seems the problem was that I didn't flash the correct version of the stock rom. The linked thread has the first version of the Pie stock OS, while previously I updated the phone two times after the Pie update. Flashing the latest version of the stock rom brought back the IMEI numbers and the WiFi MAC address. After seeing that the problem was fixed, I decided to try flashing the Lineage ROM, and that worked as well. Not sure what happened, but I'm glad I was able to fix it with no hassle.
You can get all versions of the stock ROM here: https://mirrors.lolinet.com/firmware/moto/evert/official/RETEU/
andoruB said:
Seems the problem was that I didn't flash the correct version of the stock rom. The linked thread has the first version of the Pie stock OS, while previously I updated the phone two times after the Pie update. Flashing the latest version of the stock rom brought back the IMEI numbers and the WiFi MAC address. After seeing that the problem was fixed, I decided to try flashing the Lineage ROM, and that worked as well. Not sure what happened, but I'm glad I was able to fix it with no hassle.
You can get all versions of the stock ROM here:
Click to expand...
Click to collapse
Thanks man, you saved me ! I tried everything to restore IMEI on my G6 Plus, and that was the only thing that worked. Like you said, I flashed the newest firmware for my channel (RETEU), from the link you provided. I was going to get crazy to solve this !
BrnLuca said:
Thanks man, you saved me ! I tried everything to restore IMEI on my G6 Plus, and that was the only thing that worked. Like you said, I flashed the newest firmware for my channel (RETEU), from the link you provided. I was going to get crazy to solve this !
Click to expand...
Click to collapse
How did you get updated? asks for the OEM Unlock and I can't do the unlock because I don't have wifi or 4g to connect to the internet, which is a must for OEM unlock. How did you install new stock without oem unlocking?
djcmix said:
How did you get updated? asks for the OEM Unlock and I can't do the unlock because I don't have wifi or 4g to connect to the internet, which is a must for OEM unlock. How did you install new stock without oem unlocking?
Click to expand...
Click to collapse
The restore of the stock firmware can be done through fastboot and you don't need to unlock the bootloader for that. Just search on Google and you'll find a lot of guides to do that
djcmix said:
How did you get updated? asks for the OEM Unlock and I can't do the unlock because I don't have wifi or 4g to connect to the internet, which is a must for OEM unlock. How did you install new stock without oem unlocking?
Click to expand...
Click to collapse
Here you can have internet connection on your phone shared by your PC
https://www.google.com/url?sa=t&sou...FjAAegQIBBAB&usg=AOvVaw2_SbMLCRbcTSSDcnzVbAdG
How to know the correct version of the stock rom please help
No IME, No SIM, No WIFI, No MAC. Solucionado
andoruB said:
I originally posted this on the Lineage 16.0 thread, but I figured it might not hurt to post this in a stand-alone thread.
I'm having some issues with the baseband/wifi after successfully flashing Lineage 16.0
I did do a complete nandroid backup in TWRP before flashing the copy-partitions-ab.zip, and I followed the instructions at the beginning of the thread, sideloaded the ROM, and it booted just fine, but I kept getting "No SIM card inserted" . Now when I try to restore the EFS and Persistent partitions from the backup, I still don't get a working baseband...
I even tried restoring the backup I made previously, but I still was not able to make the baseband work. I then tried flashing this stock ROM: https://forum.xda-developers.com/g6-plus/how-to/rom-official-stock-pie-9-ppw29-116-11-t3892935 through fastboot, and since this hasn't fixed the problem, I tried restoring the EFS and Persistent partitions from the backup, but still no go.
Does anyone know what I can do to fix this? Not being able to receive/make calls or connect to a wifi network basically renders this phone useless...
Click to expand...
Click to collapse
Thank you!!! It is the only solution for the problem of WIFI not working and without MAC. The NO IME is solved and SIM recognized.
Hold the Collective Knowledge!
Cheers
nope
BrnLuca said:
The restore of the stock firmware can be done through fastboot and you don't need to unlock the bootloader for that. Just search on Google and you'll find a lot of guides to do that
Click to expand...
Click to collapse
you cant do that, i keep trying to flash stock rom, but got a error in the last commands it gives a error like "partition ddr"
Downloading and flashing latest ALI_RETAIL_9.0_PPSS29.118-15-11-9_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml from https://mirrors.lolinet.com/firmware/moto/ali/official/RETAIL/ for MOTO G6 ALI XT1295-13. I tried ALI_RETAIL_9.0_PPSS29.55-24-2 many times before, it did not work.
Okay, so I've been trying to get some answers regarding custom ROMs for the past few days but I haven't even got one...and it seems I'm not the only one looking for them. So...lay it in this thread maybe we can start something up.
I am on stock OREO B04, phone's software has never been tampered with anything, TWRP, BL unlock and so on.
This is the premise of the thread, not only for me but for other users who find themselves in the same situation.
Oreo seems to be a bit of a hassle right now for migrating to custom ROMs, and this is not helped by the fact guides in the A7 section are all over the place as well, some may be outdated and there's no clear "Don't use this on x.x version" warning.
I am not even going to attempt to unlock the BL until I clear answer on wether it's possible or not. So let's start with this:
-Is it possible to unlock the BL on OREO?
-If not, what stock official ROM should we install in order to successfuly attempt to unlock the bl?
-Which guide or method is the best for doing so? I've found 2, one from 2016 on MM ROMs and one provided by TurkDevs that seems to work on some Nougat ROMs.
Then comes the recovery section:
-What TWRP should we install on a freshly unlocked device, the official releases, or the Nfound custom ones?
-Also, what are the prerequisites for installing TWRP...I hear that fastboot commands are gone since Nougat and that some flashing methods don't work, then I hear somehow you can do it by bringing back fastboot. How? There's only replies saying "type that command in fastboot" but nobody says if they had it or reinstalled it somehow.
Then comes the ROMs section:
-All custom ROMs seem to require a vendor partition as most if not all of them are Treble based. How do we get that to work?
- I am aware of the fact that the ROM threads have a prerequisites section, but none of them redirect you to a guide on how to get those prerequisites working. I understand that it's not the dev's responsability, I am not bashing anyone here, but a little bit of info cleaning and structuring should be in order in this section.
What I want for me and others in my situation is a clear answer on how to proceed, not a "flash this flash that". There's no secret that the A7 still has life in it especially with the new PIE ROMs.
I've recently seen a reply in one of the threads, encouraging the dev of one of this ROMs to not be disappointed by the seemingly low interest in PIE ROMs. I don't think there's a low interest in them, I think there are users that don't want to risk a bricked phone because of outdated guides and unlcear steps.
There's a lot of confusion going around here so I hope this thread will become a source of updated info on what's possible and what not. Thanks in advance!
Hi, I'm not the best person to help you with this since i've unlocked my Axon 7 a long time ago and I can't remember everything but I will try to help you based on my experience and on what I can remember.
Let's go
Starting with the bootloader, I unlocked mine on stock Nougat B09 using EDL Tool (Oreo wasn't even out when I unlocked my bootloader so I don't know if you can do it while running Oreo but just to be safe you should downgrade to Nougat)
It should be quite easy to unlock the bootloader, here's a simple step by step (please anyone correct me if I'm wrong)
- Download the EDL tool from the link above
- Downgrade your phone to Nougat (Using the updater on the phone itself or an EDL Package with EDL Tool or MiFlash - you can find the stock ROMs on @raystef66 's Download Center
- Once running Stock Nougat, turn on USB Debugging and Allow OEM Unlocking on Developer Settings
- Plug the phone to your computer and open EDL Tool (that should reboot the phone into EDL mode automatically)
- Navigate through the EDL Tool using the number keys on the keyboard, and it should be easy to find the Unlock Bootloader option. Unlock it and you should be done.
Once again that's the way I did it, I don't know if this is the easiest one available. You have more methods available like this one
Now onto the recovery situation, I think each developer recommends a specific TWRP version for their ROM's, like for example
@raystef66 likes NFound's TWRP 3.2.1-8 as you can see on his ROM's posts (check the first line in the installation guide)
@OrdenKrieger likes the official TWRP as you can see on Lineage OS 16.0 post
Generally, official TWRP should work just fine with any ROM.
On a recently unlocked Nougat Stock ROM, I recommend maybe an older version of TWRP, like 3.2.1 for example and you can flash it also using EDL Tool.
But when moving to Pie I recommend you use the latest TWRP version or the version that the ROM developer recommends. You probably know this but you can update your TWRP version by flashing it over the current version you have.
Now about the ROM's, the new ones have a Vendor partition so you have to create it when you're coming from Stock (because our Axon 7 doesn't support Project Treble) and to do that you can use @Oki 's PARTY Tool and after that you can flash the ROM normally, using the proper Bootstack and Modem files.
You could also try GSI's but I can't help you with that because I never tried them.
And this should be all.
I tried to keep it simple for now but i can help you further
I'm not the best person to guide you but at least I tried Feel free to ask me something and good luck!
@joaocandeias Well, dang it worked. Everything you described:
-going back to Nougat
-unlocking the bootloader with the EDL tool
-flashing TWRP-
creating the Vendor partition, and installing the new ROMs.
There were a few hiccups on the road, mostly driver related from my previous attempt, but nothing severe or something that would cause the device to brick.
I just installed @raystef66 's ResRemix ROM and it works fine. I'll start testing more of them in daily use and see which suits my needs best.
Thanks for the assistance!
TorqueSsS said:
@joaocandeias Well, dang it worked. Everything you described:
-going back to Nougat
-unlocking the bootloader with the EDL tool
-flashing TWRP-
creating the Vendor partition, and installing the new ROMs.
There were a few hiccups on the road, mostly driver related from my previous attempt, but nothing severe or something that would cause the device to brick.
I just installed @raystef66 's ResRemix ROM and it works fine. I'll start testing more of them in daily use and see which suits my needs best.
Thanks for the assistance!
Click to expand...
Click to collapse
I'm glad I could help
Since you're not the only person with questions on how to migrate from stock to custom, I'm thinking about writing a full post so more people can see it.
Btw what method did you use to downgrade to nougat?
@joaocandeias Sorry for the delayed response, I've got a really f'd up sleeping schedule these days. I'll write the exact steps I've done.
1. So, I first downloaded the B09 Nougat full stock ROM from the download center and tried to downgrade using the normal software updater in the phone (OTA window, local option).
It didn't work at first, I received a compatibility error, saying that the update is for "ailsa_ii" devices, while the device is not(or to be more exact, my device was " " ), which I found odd.
But, I thought that maybe I need the linked versions(like the last Nougat ROM before Oreo) so I downloaded the B10 Nougat ROM, and used the same procedure.
2. I set up the phone as a dud(skip everything, no Google account), turned USB debugging and OEM unlocking on, installed the original ZTE drivers straight from the phone and rebooted it into EDL to proceed with unlocking the BL.
At this point, I had the QUSB_BULK driver stick from my previous use of Zadig, so one quick "uninstall device software" and relpuging the phone go me the Qualcom 9008 driver in order.
3. I started the EDL tool, navigated through it and started the BL unlock procedure.
Once the phone rebooted I was greeted by the password screen.
One factory reset later and repeating the procedure greeted me with the "Bootloader unlocked" message. Sucess!
4.Now for TWRP, Vendor and ROM, got all the files onto the SD card, I flashedTWRP 3.2.1-8 NFound, then, from TWRP, I used the party tool, then flashed the UBv2(at which point it reverted TWRP to 3.2.3, flashed the 3.2.1-8 again with EDL ), modem, ROM, GApps, rebooted, set it up, then flashed Magisk...and everything seems fine.
The only issue I have now seems to be the camera, both stock app and GCam.
Open camera works , has the correct photo and video res, 60FPS doesn't work and the flash seems a bit laggy, but for me it's ok.
The DAC however is there, alive and kicking, Neutron detected the Hi-Res codec at launch and switched to it. It sounds the same as stock OREO to me so it is great, as this was my greatest fear when migrating to PIE. The DAC-AMP combo is like 60% of the reason I bought this phone in the first place.
TorqueSsS said:
@joaocandeias Sorry for the delayed response, I've got a really f'd up sleeping schedule these days. I'll write the exact steps I've done.
1. So, I first downloaded the B09 Nougat full stock ROM from the download center and tried to downgrade using the normal software updater in the phone (OTA window, local option).
It didn't work at first, I received a compatibility error, saying that the update is for "ailsa_ii" devices, while the device is not(or to be more exact, my device was " " ), which I found odd.
But, I thought that maybe I need the linked versions(like the last Nougat ROM before Oreo) so I downloaded the B10 Nougat ROM, and used the same procedure.
2. I set up the phone as a dud(skip everything, no Google account), turned USB debugging and OEM unlocking on, installed the original ZTE drivers straight from the phone and rebooted it into EDL to proceed with unlocking the BL.
At this point, I had the QUSB_BULK driver stick from my previous use of Zadig, so one quick "uninstall device software" and relpuging the phone go me the Qualcom 9008 driver in order.
3. I started the EDL tool, navigated through it and started the BL unlock procedure.
Once the phone rebooted I was greeted by the password screen.
One factory reset later and repeating the procedure greeted me with the "Bootloader unlocked" message. Sucess!
4.Now for TWRP, Vendor and ROM, got all the files onto the SD card, I flashedTWRP 3.2.1-8 NFound, then, from TWRP, I used the party tool, then flashed the UBv2(at which point it reverted TWRP to 3.2.3, flashed the 3.2.1-8 again with EDL ), modem, ROM, GApps, rebooted, set it up, then flashed Magisk...and everything seems fine.
The only issue I have now seems to be the camera, both stock app and GCam.
Open camera works , has the correct photo and video res, 60FPS doesn't work and the flash seems a bit laggy, but for me it's ok.
The DAC however is there, alive and kicking, Neutron detected the Hi-Res codec at launch and switched to it. It sounds the same as stock OREO to me so it is great, as this was my greatest fear when migrating to PIE. The DAC-AMP combo is like 60% of the reason I bought this phone in the first place.
Click to expand...
Click to collapse
Thanks! That will help me a lot to write a full guide. You'll be credited, don't worry
And yeah, when you migrate to custom roms you'll have to sacrifice camera quality and functionality and also a bit of speakers sound quality (all dolby atmos ports I tried are quite buggy and don't work well ; i only use atmos with the speakers). Headphones sound quality is great though.
If you don't use camera that much (not my case) and you're okay with the speakers sound quality then custom roms are probably the best option out there.
@joaocandeias
I was fully aware of the camera issues I might encounter, this has been the case with my old Mediatek devices when going to custom as well, same camera issues, but at least...it works here. Yeah, I lost some functionality, but to me it's a good trade-off. It can still take snaps and film properly so it's enough for me.
I am kind of going to miss Dolby on speakers (never liked it on headphones though), as it did a really good job for podcast style videos on YT, but it still sounds way better than a lot of phones without it so it's fine. I just need to crank the volume up a little more than usual.
I've heard that treble Pie Roms require a oreo bootloader, is this true? I am still confused how to install on my A2017G. In which order would I install bootloader and vendor partition?