Develop Bugs

I need some guidance

Could someone give me the steps on how to install MIUIv4 on my R800x?
I know that I need to flash kernel, firmware and the conversion zip from the cm9 nightlies thread. I just don't know the order in which I need to do said things, or whether there's another step I don't know about.

You need an unlocked bootloader. After you got it unlocked, flash the kernel, then the rom and then the "conversion zip". Note that I do not have a R800x.

Do I have to make any changes to my firmware version?
I also haven't activated the phone yet so would that affect the process in any way?

usern3mo said:
Do I have to make any changes to my firmware version?
I also haven't activated the phone yet so would that affect the process in any way?
Click to expand...
Click to collapse
Are you on the latest baseband? it's something like 1290_10-03.. that's what firmware you need to be on. Then activate your phone otherwise it will give you a huge mess of problems then follow the steps above me I'm and X user too so don't worry

So I change the firmware to the latest version and activate the phone. The phone is going to prompt me to update once its activated so I ignore the OTA right?

usern3mo said:
So I change the firmware to the latest version and activate the phone. The phone is going to prompt me to update once its activated so I ignore the OTA right?
Click to expand...
Click to collapse
I always ignore it. It's just 2.3.4 not a full fledged system update

agraceful said:
I always ignore it. It's just 2.3.4 not a full fledged system update
Click to expand...
Click to collapse
Last questions. How do I actually update the baseband? Would downloading to the stock .62 firmware work on my phone?

usern3mo said:
Last questions. How do I actually update the baseband? Would downloading to the stock .62 firmware work on my phone?
Click to expand...
Click to collapse
No, you need verizon's 2.3.3 ftf file and flashtool. go to your "about phone" option in the settings to see if you're already on it, if not then there will be a few things you'll need before flashing a rom
Edit: wait maybe the .62 is the 2.3.3 lol I hate cdma!!!

Slow performance, lagging, low battery

Hello Everyone,
When i was in USA i ordered htc one m8 and it is AT&T phone i guess. Since i hate the AT&T apps in the phone i tried to flash a custom rom and i sort of succeeded. Yet i still have problem about it. Whenever i flash a custom rom form( http://forum.xda-developers.com/htc-...opment#romList ) here its smooth and perfect first 1-2 weeks. No lagging no annoying problems. But after 2 weeks i am having lags (like slow app opening, late reactions, even freezing) It happens all the time, doesn't matter whichever rom i tried. And another problem is I can kill my battery in 2-3 hours just playing a game (lower than 500mb games). How can i make my phone stable smooth fast and longer battery life? (I love the room that i am using at the moment http://forum.xda-developers.com/htc-...pload-t3064838) And i also started to consider that am i flashing the roms wrong??!
Please can somebody help me
I am in begginer stage about these rom and root stuff

tugratolunay said:
Hello Everyone,
When i was in USA i ordered htc one m8 and it is AT&T phone i guess. Since i hate the AT&T apps in the phone i tried to flash a custom rom and i sort of succeeded. Yet i still have problem about it. Whenever i flash a custom rom form( http://forum.xda-developers.com/htc-...opment#romList ) here its smooth and perfect first 1-2 weeks. No lagging no annoying problems. But after 2 weeks i am having lags (like slow app opening, late reactions, even freezing) It happens all the time, doesn't matter whichever rom i tried. And another problem is I can kill my battery in 2-3 hours just playing a game (lower than 500mb games). How can i make my phone stable smooth fast and longer battery life? (I love the room that i am using at the moment http://forum.xda-developers.com/htc-...pload-t3064838) And i also started to consider that am i flashing the roms wrong??!
Please can somebody help me
I am in begginer stage about these rom and root stuff
Click to expand...
Click to collapse
Can you check your firmware version? It's in the bootloader menu(to enter it: restart phone then right after screen turns black hold volume down). Mine for example is 6.14.401.4. Also can you tell the name of the rom you use as the links you posted are not full and can't see it?

high_voltage said:
Can you check your firmware version? It's in the bootloader menu(to enter it: restart phone then right after screen turns black hold volume down). Mine for example is 6.14.401.4. Also can you tell the name of the rom you use as the links you posted are not full and can't see it?
Click to expand...
Click to collapse
[ROM] S.ROM-S3-10.0-A(A9) B(B2) | MMB29M Sense7g/7 | HK/JBL/BS | A9 1.56.617.1
But i didnt updated the lates version yet. But i have same problems in every roms.
HBoot 3.19.0.000
Os- 4.28.502.1

tugratolunay said:
[ROM] S.ROM-S3-10.0-A(A9) B(B2) | MMB29M Sense7g/7 | HK/JBL/BS | A9 1.56.617.1
But i didnt updated the lates version yet. But i have same problems in every roms.
HBoot 3.19.0.000
Os- 4.28.502.1
Click to expand...
Click to collapse
Your OS firmware is lollipop one, not MM. The best way is to search for RUU(MM one) and flash it. There is thread in the forum how to flash ruu and section for your variant. Beware: RUU will erase ALL your data(yes, including the internal memory) except the Sdcard!

high_voltage said:
Your OS firmware is lollipop one, not MM. The best way is to search for RUU(MM one) and flash it. There is thread in the forum how to flash ruu and section for your variant. Beware: RUU will erase ALL your data(yes, including the internal memory) except the Sdcard!
Click to expand...
Click to collapse
What if I want to use current custom or similar one?

tugratolunay said:
What if I want to use current custom or similar one?
Click to expand...
Click to collapse
Then you unlock the bootloader as you did before(should be locked to flash ruu it's easy done with fastboot relock command you will see in the instructions) and flash the custom rom. I did that. Was on lollipop firmware(4.16.401.10 in my case) and MM rom, locked the bootloader, flashed stock recovery(before locking the bootloader), flashed the ruu, unlocked the bootloader, flashed custom recovery twrp, flashed the desired new custom MM rom.
Check the instruction, I am not sure if it's needed to flash the stock recovery as the RUU flash that too.

high_voltage said:
Then you unlock the bootloader as you did before(should be locked to flash ruu it's easy done with fastboot relock command you will see in the instructions) and flash the custom rom. I did that. Was on lollipop firmware(4.16.401.10 in my case) and MM rom, locked the bootloader, flashed stock recovery(before locking the bootloader), flashed the ruu, unlocked the bootloader, flashed custom recovery twrp, flashed the desired new custom MM rom.
Check the instruction, I am not sure if it's needed to flash the stock recovery as the RUU flash that too.
Click to expand...
Click to collapse
Would you be angry if i said i didnt get it?

high_voltage said:
Then you unlock the bootloader as you did before(should be locked to flash ruu it's easy done with fastboot relock command you will see in the instructions) and flash the custom rom. I did that. Was on lollipop firmware(4.16.401.10 in my case) and MM rom, locked the bootloader, flashed stock recovery(before locking the bootloader), flashed the ruu, unlocked the bootloader, flashed custom recovery twrp, flashed the desired new custom MM rom.
Check the instruction, I am not sure if it's needed to flash the stock recovery as the RUU flash that too.
Click to expand...
Click to collapse
I started to download http://www.htc.com/us/support/htc-one-m8-att/news/ this ruu for my phone. I will install this ruu and then unlock bootloader and flash recovery twrp and flash the custom rom again ? and it will help my phone to stabilize?

tugratolunay said:
I started to download http://www.htc.com/us/support/htc-one-m8-att/news/ this ruu for my phone. I will install this ruu and then unlock bootloader and flash recovery twrp and flash the custom rom again ? and it will help my phone to stabilize?
Click to expand...
Click to collapse
Sadly, I checked, there is no MM update for at&t at that point of time. You are.1 this is .2 version with only SF fix that is not relevant for your problem. Still, I would advice you to try for a weak developer edition stock rooted rom.
Link: http://forum.xda-developers.com/htc-one-m8/development/rom-stock-unlocked-developer-sense-7-t3262894
Try this rom. Keep in mind that internal memory files will be moved to folder with name "0", but won't be deleted.

high_voltage said:
Sadly, I checked, there is no MM update for at&t at that point of time. You are.1 this is .2 version with only SF fix that is not relevant for your problem. Still, I would advice you to try for a weak developer edition stock rooted rom.
Click to expand...
Click to collapse
Can you help me to find the correct rom to flash please?

high_voltage said:
Sadly, I checked, there is no MM update for at&t at that point of time. You are.1 this is .2 version with only SF fix that is not relevant for your problem. Still, I would advice you to try for a weak developer edition stock rooted rom.
Link: http://forum.xda-developers.com/htc-one-m8/development/rom-stock-unlocked-developer-sense-7-t3262894
Try this rom. Keep in mind that internal memory files will be moved to folder with name "0", but won't be deleted.
Click to expand...
Click to collapse
This one requires S-off mine is s-on

Ryokan said:
Can you help me to find the correct rom to flash please?
Click to expand...
Click to collapse
http://forum.xda-developers.com/devdb/project/dl/?id=15489&task=get
I use it currently, in the aroma installer I choose root(normal root method that it's default one, I don't like systemless), swipe2sleep ON and write protection disabler ON. Hope it runs smooth, but give it a few days to settle. This is stock MM rom and I run it with lollipop firmware without problems, tho I have europe unlocked edition and just don't know how at&t copes with it's lollipop firmware and new MM roms. Give it a shot.
---------- Post added at 03:56 PM ---------- Previous post was at 03:55 PM ----------
Ryokan said:
This one requires S-off mine is s-on
Click to expand...
Click to collapse
Only flashing the firmware requires s-off, relax, I am s-on too. Check the direct link, this is the rom itself and all you need.

high_voltage said:
http://forum.xda-developers.com/devdb/project/dl/?id=15489&task=get
I use it currently, in the aroma installer I choose root(normal root method that it's default one, I don't like systemless), swipe2sleep ON and write protection disabler ON. Hope it runs smooth, but give it a few days to settle. This is stock MM rom and I run it with lollipop firmware without problems, tho I have europe unlocked edition and just don't know how at&t copes with it's lollipop firmware and new MM roms. Give it a shot.
---------- Post added at 03:56 PM ---------- Previous post was at 03:55 PM ----------
Only flashing the firmware requires s-off, relax, I am s-on too. Check the direct link, this is the rom itself and all you need.
Click to expand...
Click to collapse
Thank you so much sir I will try it and how can i know that at&t release the ruu that i need ? where can i follow it?

Ryokan said:
Thank you so much sir I will try it and how can i know that at&t release the ruu that i need ? where can i follow it?
Click to expand...
Click to collapse
There is at&t android development section in the M8 forum, I am sure there will be noticed if MM is released.
Also in general thread in the sticky thread updates. Cheers!

Ryokan said:
This one requires S-off mine is s-on
Click to expand...
Click to collapse
You only need s-off to flash the recommended firmware for this ROM. If you have the right firmware, you never NEED s-off to flash a ROM. This ROM comes with a guide on how to bypass S-ON Write Protection-- a hack by Flar2. This isn't the same as a hard S-OFF
You should give it a try
Edit looks like somebody else beat me to the punch, sorry about that

Anonaru said:
You only need s-off to flash the recommended firmware for this ROM. If you have the right firmware, you never NEED s-off to flash a ROM. This ROM comes with a guide on how to bypass S-ON Write Protection-- a hack by Flar2. This isn't the same as a hard S-OFF
You should give it a try
Edit looks like somebody else beat me to the punch, sorry about that
Click to expand...
Click to collapse
How can i know if my firmware matches?

Ryokan said:
How can i know if my firmware matches?
Click to expand...
Click to collapse
By asking you what firmware version you have. So, which version do you have? I put the big "If you have the right firmware" in there for a reason :laugh:

Ryokan said:
How can i know if my firmware matches?
Click to expand...
Click to collapse
I think you are confusing "firmware" with "ROM". While true on some devices, these terms are used interchangeably, its better to not treat them so on the M8.
On this device, "firmware" usually refers to a number of modules (hboot, radio, WiFi, Bluetooth, and others) not included in the ROM, but included in official OTA updates and RUUs.
Your firmware is Lollipop, as shown by your OS number (on hboot screen) or main version (getvar all). This doesn't change when you flash a ROM.
LP firmware should run fine with MM ROMs. Technically, its best to run MM firmware. But you can't update the firmware until AT&T MM is released, or alternately if you get s-off. And the changes in the firmware seem minimal. I'm running LP firmware with the 6.12.1540 stock ROM linked by another user in this thread, with no glitches whatsoever.

redpoint73 said:
I think you are confusing "firmware" with "ROM". While true on some devices, these terms are used interchangeably, its better to not treat them so on the M8.
On this device, "firmware" usually refers to a number of modules (hboot, radio, WiFi, Bluetooth, and others) not included in the ROM, but included in official OTA updates and RUUs.
Your firmware is Lollipop, as shown by your OS number (on hboot screen) or main version (getvar all). This doesn't change when you flash a ROM.
LP firmware should run fine with MM ROMs. Technically, its best to run MM firmware. But you can't update the firmware until AT&T MM is released, or alternately if you get s-off. And the changes in the firmware seem minimal. I'm running LP firmware with the 6.12.1540 stock ROM linked by another user in this thread, with no glitches whatsoever.
Click to expand...
Click to collapse
Big thank you inbound!
I wanted to suggest that it might be safe to try running a MM ROM with the LP firmware, but had no precedent to do so. Sounds like it is generally safe to do so, then :laugh:

Anonaru said:
Big thank you inbound!
I wanted to suggest that it might be safe to try running a MM ROM with the LP firmware, but had no precedent to do so. Sounds like it is generally safe to do so, then :laugh:
Click to expand...
Click to collapse
You are correct, in that general rule of thumb is to update firmware to match the ROM. Especially having KitKat firmware with a LP ROM, which caused major problems (no WiFi, audio issues, no boot or extreme long boot times).
But MM ROMs in general seem to work fine with LP firmware. It seems minimal changes to the firmware this time around. I haven't seen any issues (at least not anything major or significant) reported running MM ROMs with LP firmware.
And for the OP's AT&T version, he can't update firmware unless he does s-off. So at least for the time being, I don't see a compelling reason to do that; and look at other options to help his performance issues.

Downgrade to Marshmallow with S-On?

I'm wondering if anyone has attempted to install a Marshmallow custom ROM or stock RUU over the Nougat firmware with any success.
I'm doubtful, but perhaps it's possible with S-On. Thanks!

the nougat firmware is not downcompatible with marshmallow roms.
only way would be to s-off, downgrade firmware then, flash the marshmallow rom.
be aware to pick a full firmware though and no incremental one...we've seen a handful people doing this and that ends in a hardbrick.

j to the 4n said:
the nougat firmware is not downcompatible with marshmallow roms.
only way would be to s-off, downgrade firmware then, flash the marshmallow rom.
be aware to pick a full firmware though and no incremental one...we've seen a handful people doing this and that ends in a hardbrick.
Click to expand...
Click to collapse
When I then eventually update ViperROM from Marshmallow to Nougat, will I have to perform a full wipe - or can the update be directly applied?
Trying to plan ahead, thanks a bunch j4n.

fullydeveloped said:
When I then eventually update ViperROM from Marshmallow to Nougat, will I have to perform a full wipe - or can the update be directly applied?
Trying to plan ahead, thanks a bunch j4n.
Click to expand...
Click to collapse
well, that sounds like that you are still on marshmallow firmware + rom.
That would mean, you could flash the nougat rom and revert back to the marshmallow one anytime. Just ensure you flash latets TWRP before and backup your data, including sdcard..in case something goes wrong with encryption.
the nougat rom can be dirty flashed.
you know what the difference between firmware and rom is, right?

j to the 4n said:
well, that sounds like that you are still on marshmallow firmware + rom.
That would mean, you could flash the nougat rom and revert back to the marshmallow one anytime. Just ensure you flash latets TWRP before and backup your data, including sdcard..in case something goes wrong with encryption.
the nougat rom can be dirty flashed.
you know what the difference between firmware and rom is, right?
Click to expand...
Click to collapse
Thanks, apologies for the confusion. I'm on Nougat, but am planning to downgrade for xposed - then eventually update back up to Nougat once there's a stable release. I asked about dirty flashing since I'm less likely to full wipe for 7.0 after many months of customizing

j to the 4n said:
the nougat firmware is not downcompatible with marshmallow roms.
only way would be to s-off, downgrade firmware then, flash the marshmallow rom.
be aware to pick a full firmware though and no incremental one...we've seen a handful people doing this and that ends in a hardbrick.
Click to expand...
Click to collapse
Has anyone downgraded the Firmware and succeeded? I hard bricked mine twice, first was trying to downgrade it with a full stock firmware from OTA and 2nd time it died when i accidentally picked and flashed a wrong Marshmallow aboot trying to get rid of Hidden Red text which made me believe flashing a Marshmallow aboot while on Nougat hardbricks the Phone. It died at the stage where it should restart so we can run fastboot flash zip Firmware_xx.zip command the 2nd time. It goes black, doesn't turn on, a PC doesn't recognize it, doesn't show if charging. Was lucky HTC took care of the problem.

emrug said:
Has anyone downgraded the Firmware and succeeded? I hard bricked mine twice, first was trying to downgrade it with a full stock firmware from OTA and 2nd time it died when i accidentally picked and flashed a wrong Marshmallow aboot trying to get rid of Hidden Red text which made me believe flashing a Marshmallow aboot while on Nougat hardbricks the Phone. It died at the stage where it should restart so we can run fastboot flash zip Firmware_xx.zip command the 2nd time. It goes black, doesn't turn on, a PC doesn't recognize it, doesn't show if charging. Was lucky HTC took care of the problem.
Click to expand...
Click to collapse
thats what I said. The firmware in an ota is NOT a full firmware, its a incremental one.
You need a full firmware package like its provided in @Sneakyghost 's threads, with those lots of downgraded already.

j to the 4n said:
thats what I said. The firmware in an ota is NOT a full firmware, its a incremental one.
You need a full firmware package like its provided in @Sneakyghost 's threads, with those lots of downgraded already.
Click to expand...
Click to collapse
Great!! Now i get it, well explained. Thanks :highfive:

New OTA File for build number 67

I managed to capture the OTA link and get the file guys
https://drive.google.com/open?id=0B_as3y0lZtevWkR5NjgzU0h1cTQ

sandy108 said:
I managed to capture the OTA link and get the file guys
https://drive.google.com/open?id=0B_as3y0lZtevWkR5NjgzU0h1cTQ
Click to expand...
Click to collapse
Is this ok to install on the US variants?
Sent from my iPhone using Tapatalk

From what I understand, I'm just supposed to download this and then go to my recovery and update from recovery right?
As in like update from internal storage right?

What version is this from?

hey bro did you have the flashligt icon and gesture in the new update?

Anyone flashed this with flash fire?

How to install on rooted devices???

sandy108 said:
I managed to capture the OTA link and get the file guys
https://drive.google.com/open?id=0B_as3y0lZtevWkR5NjgzU0h1cTQ
Click to expand...
Click to collapse
You didn't tell us what variant of the phone you have

How to install???

zimplemeh said:
Is this ok to install on the US variants?
Click to expand...
Click to collapse
No this is not recommended to install on US variant

saqlainrattansi said:
From what I understand, I'm just supposed to download this and then go to my recovery and update from recovery right?
As in like update from internal storage right?
Click to expand...
Click to collapse
Yes you got it right

olive23 said:
What version is this from?
Click to expand...
Click to collapse
It's from build number *67

Jayesh Nirve said:
How to install???
Click to expand...
Click to collapse
Either use stock recovery or use Flashfire

zeft64 said:
You didn't tell us what variant of the phone you have
Click to expand...
Click to collapse
Indian Variant

Flash fire ain't working phone just reboots with no changes

can i install on retbr?

I think the location version does not matter as long as you have the right build number. I had retla .15 and tried to flash .35 in order to update to .67 (fail), the ota ask for .14/.15. So I had to install stock .15 again and redo the process.
Something I'd like to add is the stock recovery did not recognize internal or sd storage, so I had to push ota via ADB.
*Also my warning bootscreen changed from N/A to Bad Key multiple times for apparently no reason. But everything is working fine.

Pls tell me how u went back to 15 plsss

Aredhelelen said:
I think the location version does not matter as long as you have the right build number. I had retla .15 and tried to flash .35 in order to update to .67 (fail), the ota ask for .14/.15. So I had to install stock .15 again and redo the process.
Something I'd like to add is the stock recovery did not recognize internal or sd storage, so I had to push ota via ADB.
*Also my warning bootscreen changed from N/A to Bad Key multiple times for apparently no reason. But everything is working fine.
Click to expand...
Click to collapse
Exactly what I have been trying to tell. There is a fingerprint mismatch that happens. On a side note how did you manage to take yourself back from .35 to .15 and then update to .67. I get the last part, but downgrading with a higher bootloader; and where did you get the .15 build

You can simply install one of the stock versions already posted here in the forum, I just downloaded the .15 and installed it again via fastboot with the command lines (also explained in that post, in comments) like any other stock rom. Then, after starting the phone you must activate USB debbuging mode to be able to use ADB commands, so you can restart the phone in stock recovery and activate the push ota update via ADB.
Anyway, if this sounds complicated I think there is already a flashable .zip to apply ota, you can give it a try.

Update to oreo PROBLEM

my build number is NPPS25.137-93-14
I want to update to oreo but read some posts says that i can not because of build number
HELP

ahmedAZ said:
my build number is NPPS25.137-93-14
I want to update to oreo but read some posts says that i can not because of build number
HELP
Click to expand...
Click to collapse
You must be running NPPS25.137-93-2-5 to be able to update through OTA. However, you can still update to Oreo using fastboot method (link here: https://forum.xda-developers.com/g5/how-to/official-oreo-8-1-0-opp28-85-16-t3849244), but most probably, you will loose all of the data stored in the phone.

Andrej_SK said:
You must be running NPPS25.137-93-2-5 to be able to update through OTA. However, you can still update to Oreo using fastboot method (link here: https://forum.xda-developers.com/g5/how-to/official-oreo-8-1-0-opp28-85-16-t3849244), but most probably, you will loose all of the data stored in the phone.
Click to expand...
Click to collapse
Is it safe to downgrade?
Some people say you may hard brick

Using adb don't need to downgrade?

ahmedAZ said:
Is it safe to downgrade?
Some people say you may hard brick
Click to expand...
Click to collapse
It's safe as long as you don't try to flash gpt and bootloader. Downgrading one (or both) of these partition results in hardbrick.

Andrej_SK said:
It's safe as long as you don't try to flash gpt and bootloader. Downgrading one (or both) of these partition results in hardbrick.
Click to expand...
Click to collapse
But if i install oreo custom rom fingerprint may not work because it needs updated bootloader
I have read something like that on forum

ahmedAZ said:
But if i install oreo custom rom fingerprint may not work because it needs updated bootloader
I have read something like that on forum
Click to expand...
Click to collapse
If you update to official Oreo but then decide, you want to install CustomROM, you have to downgrade to Nougat first. Otherwise, your fingerprint won't simply work with any CustomROM. I have already mentioned it in this thread https://forum.xda-developers.com/g5/help/finger-print-sensor-issue-oreo-roms-t3853491.
Btw, bootloader version is not related to fingerprint working or not with CustomROM. There's another partition that makes difference in it.

Andrej_SK said:
If you update to official Oreo and decide later, you want to install CustomROM, you have to downgrade to Nougat first. Otherwise, fingerprint won't work with any CustomROM. I have already mentioned it in this thread https://forum.xda-developers.com/g5/help/finger-print-sensor-issue-oreo-roms-t3853491.
Click to expand...
Click to collapse
So it is better to be on nougat if i want custom roms in future?
Treble project needs stock nougat or oreo?

ahmedAZ said:
So it is better to be on nougat if i want custom roms in future?
Click to expand...
Click to collapse
In my opininon yes, but your opininon might be different. Downgrading from official Oreo to official Nougat isn't difficult at all. You just have to remember, you can't flash gpt and bootloader. It's also recommended to avoid erase modem commands to prevent loss of IMEI.
ahmedAZ said:
Treble project needs stock nougat or oreo?
Click to expand...
Click to collapse
None of them. Treble project needs Treble TWRP and Treble LineageOS installed firstly for correct functionality of other Treble CustomROMs. More info in this thread https://forum.xda-developers.com/g5/development/treble-project-treble-cedric-t3820451.

ahmedAZ said:
my build number is NPPS25.137-93-14
I want to update to oreo but read some posts says that i can not because of build number
HELP
Click to expand...
Click to collapse
Hi everyone , I have not yet received update for Oreo ? Indian region, having same build no , my bootloader is unlocked as well

Same problem here. I have also the same build number on amzin software channel. Didn't receive the update till now. It says there is no update available.
akshayshirkar10 said:
Hi everyone , I have not yet received update for Oreo ? Indian region, having same build no , my bootloader is unlocked as well
Click to expand...
Click to collapse

achintyakv said:
Same problem here. I have also the same build number on amzin software channel. Didn't receive the update till now. It says there is no update available.
Click to expand...
Click to collapse
I was on 137-93-14 too. I flashed the fastboot firmware 137-93-2-5 to go back full stock and official. No need to re lock bootloader..then I downloaded the latest OTA update 28.85-16 and installed it via ADB sideload.
My phone is xt1670 on channel retca..though I can't say for sure what difference it makes if your on amzin. Wish I could help more.

No problem bro Yesterday I flashed the fastboot files and successfully updated to oreo which I found on this thread.
https://forum.xda-developers.com/g5/how-to/official-oreo-8-1-0-opp28-85-16-t3849244
Btw you have taken the long step bro. No need to get back to 137-93-2-5.
Cheers!
Chekm8Qc said:
I was on 137-93-14 too. I flashed the fastboot firmware 137-93-2-5 to go back full stock and official. No need to re lock bootloader..then I downloaded the latest OTA update 28.85-16 and installed it via ADB sideload.
My phone is xt1670 on channel retca..though I can't say for sure what difference it makes if your on amzin. Wish I could help more.
Click to expand...
Click to collapse

achintyakv said:
No problem bro Yesterday I flashed the fastboot files and successfully updated to oreo which I found on this thread.
https://forum.xda-developers.com/g5/how-to/official-oreo-8-1-0-opp28-85-16-t3849244
Btw you have taken the long step bro. No need to get back to 137-93-2-5.
Cheers!
Click to expand...
Click to collapse
i updated through twrp

@achintyakv
Yeah your right that was definitely the long way hehe. It's cause I wasn't sure that th oreo fastboot method would have worked for me. I had tried the TWRP version and it kept boot looping so I thought the other way would be safer