so i tried flashing many oreo custom roms, and the fingerprint sensor just didn't work anymore, and i know is a common issue, is there any fix to this?
Frarione said:
so i tried flashing many oreo custom roms, and the fingerprint sensor just didn't work anymore, and i know is a common issue, is there any fix to this?
Click to expand...
Click to collapse
If you're still on the nougat bootloader it won't work
Flash the entire oero firmware via fastboot
TheFixItMan said:
If you're still on the nougat bootloader it won't work
Flash the entire oero firmware via fastboot
Click to expand...
Click to collapse
my bootloader is in the B8.31 version, isn't that the oreo bootloader?
Frarione said:
my bootloader is in the B8.31 version, isn't that the oreo bootloader?
Click to expand...
Click to collapse
I don't own this device
My advice would be to flash the entire oero firmware
TheFixItMan said:
If you're still on the nougat bootloader it won't work
Click to expand...
Click to collapse
I believe it doesn't matter in case he is running Oreo CustomROM.
my bootloader is in the B8.31 version, isn't that the oreo bootloader?
Click to expand...
Click to collapse
I would recommend you to downgrade to Nougat first - flash everything except gpt and bootloader to avoid hardbrick. Also don't run erase modem commands, they will erase your IMEI in this case. Then, make sure that fingerprint is working with Nougat StockROM. If it does, try to install CustomROM.
Andrej_SK said:
I believe it doesn't matter in case he is running Oreo CustomROM.
I would recommend you to downgrade to Nougat first - flash everything except gpt and bootloader to avoid hardbrick. Also don't run erase modem commands, they will erase your IMEI in this case. Then, make sure that fingerprint is working with Nougat StockROM. If it does, try to install CustomROM.
Click to expand...
Click to collapse
ok i will try this, wish me luck
Andrej_SK said:
I would recommend you to downgrade to Nougat first - flash everything except gpt and bootloader to avoid hardbrick. Also don't run erase modem commands, they will erase your IMEI in this case. Then, make sure that fingerprint is working with Nougat StockROM. If it does, try to install CustomROM.
Click to expand...
Click to collapse
Dude ily, all this time with that problem, and this was the simple solution, thx :good:
Frarione said:
Dude ily, all this time with that problem, and this was the simple solution, thx :good:
Click to expand...
Click to collapse
Glad to help you.
Just one more thing to mention: don't even try to install OTA updates (in case you stay on StockROM). Here's why. Your bootloader's version is B8.31 now, but phone is "still" running Android Nougat (I guess). Oreo OTA updates the bootloader from B8.25 to B8.31, but since yours bootloader is already updated to B8.31, OTA would try to make a changes, which were already made and break the whole "structure" of bootloader. This would end up most probably in hard brick.
If you'd like to revert back to official Oreo someday, install it using fastboot method. (https://forum.xda-developers.com/g5/how-to/official-oreo-8-1-0-opp28-85-16-t3849244). Even you will most probably loose all of the data, it seems to be the only one safe way to update back to Oreo after downgrading to Nougat.
Andrej_SK said:
Glad to help you.
Just one more thing to mention: don't even try to install OTA updates (in case you stay on StockROM). Here's why. Your bootloader's version is B8.31 now, but phone is "still" running Android Nougat (I guess). Oreo OTA updates the bootloader from B8.25 to B8.31, but since yours bootloader is already updated to B8.31, OTA would try to make a changes, which were already made and break the whole "structure" of bootloader. This would end up most probably in hard brick.
If you'd like to revert back to official Oreo someday, install it using fastboot method. (https://forum.xda-developers.com/g5/how-to/official-oreo-8-1-0-opp28-85-16-t3849244). Even you will most probably loose all of the data, it seems to be the only one safe way to update back to Oreo after downgrading to Nougat.
Click to expand...
Click to collapse
Roger that, thanks again
Related
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:
Long story short, I got pissed at Moto and decided to unlock my bootloader, flash TWRP, and flash a custom ROM (Alberto97's AOSP 8.1). While the ROM is working fine, eventually, I kind of missed the stock ROM, and decided I want to go back (Oreo). Keep in mind, though, I don't want to relock my bootloader as I will flash TWRP and root my device after going back to stock. How do I do this? I do have the Oreo OTA zip with me (Build no. OPN27.76-12-22), if that matters.
When you never were on stock oreo, you can easily flash stock firmware with February security patch (it's 7.1) and then update with the Oreo update zip you find in the forums. Then you can flash TWRP again.
jonas210678 said:
When you never were on stock oreo, you can easily flash stock firmware with February security patch (it's 7.1) and then update with the Oreo update zip you find in the forums. Then you can flash TWRP again.
Click to expand...
Click to collapse
Well, I was on official Oreo :/
djdelarosa25 said:
Well, I was on official Oreo :/
Click to expand...
Click to collapse
Bro, you and I are on same page. I also rooted my device when I was on stock Oreo and forgot to make a backup of stock Oreo (cuz I'm stupid). I talked a lot to other members and only option that is available for now to get back to stock with boot unlocked and OTA support is wait for Fastboot flash files for stock Oreo. Stock flash files will return your device to original state. I hope Oreo frimware would be available soon (about couple of months). I also want to get back to stock and guess what? I am also using AOSP by Alberto and it's working just like stock, no problem and bugs (there is some data connection bug but I use wifi all the time so it doesn't bother me) so far. Only problem with this ROM is safety net but I don't even use apps that requires safety net certification so I'm good with that too. Basically, it is a perfect ROM for me.
And don't try to back flash if you want to get back to original state, it is true you can still flash 7.1.1 but no guarantee, I just heard from someone but I never tried because I don't want to take risks and even if you got it running 7.1.1, a single OTA will brick your phone for sure. So wait for Oreo frimware, that's the only way and by the time enjoy AOSP.
Manish355 said:
Bro, you and I are on same page. I also rooted my device when I was on stock Oreo and forgot to make a backup of stock Oreo (cuz I'm stupid). I talked a lot to other members and only option that is available for now to get back to stock with boot unlocked and OTA support is wait for Fastboot flash files for stock Oreo. Stock flash files will return your device to original state. I hope Oreo frimware would be available soon (about couple of months). I also want to get back to stock and guess what? I am also using AOSP by Alberto and it's working just like stock, no problem and bugs (there is some data connection bug but I use wifi all the time so it doesn't bother me) so far. Only problem with this ROM is safety net but I don't even use apps that requires safety net certification so I'm good with that too. Basically, it is a perfect ROM for me.
And don't try to back flash if you want to get back to original state, it is true you can still flash 7.1.1 but no guarantee, I just heard from someone but I never tried because I don't want to take risks and even if you got it running 7.1.1, a single OTA will brick your phone for sure. So wait for Oreo frimware, that's the only way and by the time enjoy AOSP.
Click to expand...
Click to collapse
I definitely will. Thanks a lot, man . Lesson learned, always make backups
Manish355 said:
Bro, you and I are on same page. I also rooted my device when I was on stock Oreo and forgot to make a backup of stock Oreo (cuz I'm stupid). I talked a lot to other members and only option that is available for now to get back to stock with boot unlocked and OTA support is wait for Fastboot flash files for stock Oreo. Stock flash files will return your device to original state. I hope Oreo frimware would be available soon (about couple of months). I also want to get back to stock and guess what? I am also using AOSP by Alberto and it's working just like stock, no problem and bugs (there is some data connection bug but I use wifi all the time so it doesn't bother me) so far. Only problem with this ROM is safety net but I don't even use apps that requires safety net certification so I'm good with that too. Basically, it is a perfect ROM for me.
And don't try to back flash if you want to get back to original state, it is true you can still flash 7.1.1 but no guarantee, I just heard from someone but I never tried because I don't want to take risks and even if you got it running 7.1.1, a single OTA will brick your phone for sure. So wait for Oreo frimware, that's the only way and by the time enjoy AOSP.
Click to expand...
Click to collapse
Hey, so if someone can upload a TWRP flashable Nandroid backup of stock Oreo, are we saved?
djdelarosa25 said:
Hey, so if someone can upload a TWRP flashable Nandroid backup of stock Oreo, are we saved?
Click to expand...
Click to collapse
You'll get back to stock for sure but bootloader will still be unlocked, the only way to lock bootloader is through fastboot flashing of stock ROM. Moreover, TWRP backup contains personal information so not many want to share it but if someone kind enough to make a backup after doing factory reset so it will not contain any personal information then it will work.
Manish355 said:
You'll get back to stock for sure but bootloader will still be unlocked, the only way to lock bootloader is through fastboot flashing of stock ROM. Moreover, TWRP backup contains personal information so not many want to share it but if someone kind enough to make a backup after doing factory reset so it will not contain any personal information then it will work.
Click to expand...
Click to collapse
Why would one still want to relock the bootloader? It's to my understanding that unlocking it voids your warranty, and I've also read somewhere that even after relocking it, the warning persists.
By the way, have you checked my PM?
Hi guys, in my case I updated from Android Nougat 7.1.1 to AOSP 8.1. now I want to go back to stock rom 7.11 and after that update to Oreo by OTA. Should I only apply Stock Rom 7.11 by RSD Lite??
Thanks in advance
soadcma said:
Hi guys, in my case I updated from Android Nougat 7.1.1 to AOSP 8.1. now I want to go back to stock rom 7.11 and after that update to Oreo by OTA. Should I only apply Stock Rom 7.11 by RSD Lite??
Thanks in advance
Click to expand...
Click to collapse
You can directly flash the Oreo firmware via fastboot
Yeah, just flash the Oreo firmware
jonas210678 said:
You can directly flash the Oreo firmware via fastboot
Click to expand...
Click to collapse
But where can I find it to download ?
Thanks
---------- Post added at 04:39 PM ---------- Previous post was at 04:37 PM ----------
djdelarosa25 said:
Yeah, just flash the Oreo firmware
Click to expand...
Click to collapse
But where can I find it to download ?
Thanks
soadcma said:
But where can I find it to download ?
Thanks
---------- Post added at 04:39 PM ---------- Previous post was at 04:37 PM ----------
But where can I find it to download ?
Thanks
Click to expand...
Click to collapse
Link for the topic with the Oreo stock fastboot ROM. https://forum.xda-developers.com/moto-z-play/how-to/guide-relock-oreo-bootloader-to-stock-t3784621
1.67 GB in size.
no matter what i do with my htc 10, i always lose radio on flashing rom, i looked and it say only flash oreo roms if you are on oreo firmware, which is what i am doing. i am formatting data like it says to do to rid the encrypyion. because of this i have to restore from RUU everytime to fix radio, restoring from a twrp backup does not fix the radio. home button stops working aswell but it doesnt work in twrp either. is there any way i can fix these problems?
Thank you for your help
twosaltyy said:
no matter what i do with my htc 10, i always lose radio on flashing rom, i looked and it say only flash oreo roms if you are on oreo firmware, which is what i am doing. i am formatting data like it says to do to rid the encrypyion. because of this i have to restore from RUU everytime to fix radio, restoring from a twrp backup does not fix the radio. home button stops working aswell but it doesnt work in twrp either. is there any way i can fix these problems?
Thank you for your help
Click to expand...
Click to collapse
It lacks all the important info
1: what is your current firmware
2: what is your current OS
3: what ruu did you flash
Mr Hofs said:
It lacks all the important info
1: what is your current firmware
2: what is your current OS
3: what ruu did you flash
Click to expand...
Click to collapse
1. Oreo
2. 3.16.401.2
3. The Oreo RUU for 3.16.401.2
twosaltyy said:
1. Oreo
2. 3.16.401.2
3. The Oreo RUU for 3.16.401.2
Click to expand...
Click to collapse
Alright that setup is fine, using the ruu gives you radio so all is working fine at that point. What roms did you try to flash ?
Mr Hofs said:
Alright that setup is fine, using the ruu gives you radio so all is working fine at that point. What roms did you try to flash ?
Click to expand...
Click to collapse
I tried PureFusion and AOSiP
My radio works fine on fully stock (which is what i am running right now) but when i goto flash a rom i lose radio and home button, i just wanted to clarify because i didnt know how good my initial explanation was.
twosaltyy said:
I tried PureFusion and AOSiP
My radio works fine on fully stock (which is what i am running right now) but when i goto flash a rom i lose radio and home button, i just wanted to clarify because i didnt know how good my initial explanation was.
Click to expand...
Click to collapse
Yeah, ï believe purefusion is based on the nougat firmware so that explains the loss of radio. Check the specs before flashing.......maximus, leedroid or viper should work fine.
You have to read more mate, just checked the OP of the AOSP rom.......
It says it needs N or MM firmware so no O (oreo) firmware.
Mr Hofs said:
You have to read more mate, just checked the OP of the AOSP rom.......
It says it needs N or MM firmware so no O (oreo) firmware.
Click to expand...
Click to collapse
Hmm... what about purefusion though, i cant see anything on that page about what firmware i have to be on but i read somewhere you have to be on O firmware for any O roms to work and you cant flash N roms if you are on O firmware.
Mr Hofs said:
Yeah, ï believe purefusion is based on the nougat firmware so that explains the loss of radio. Check the specs before flashing.......maximus, leedroid or viper should work fine.
Click to expand...
Click to collapse
i dont want to use those because i wanted the fully stock android experience, like i did on my other phones. Should the lineageos 15.1 rom work?
twosaltyy said:
i dont want to use those because i wanted the fully stock android experience, like i did on my other phones. Should the lineageos 15.1 rom work?
Click to expand...
Click to collapse
Read the specs ?
Look all the info is there. Take your time and take all info in, don't be hasty, read it a second time if needed.
Mr Hofs said:
Read the specs
Click to expand...
Click to collapse
Yeah it says O firmware required. is there a specific way i need to erase the device in TWRP other than formatting data to rid the encryption? just want to be sure. it only says to erase /system and /data if coming from another ROM, im not sure if this includes stock sense also?
twosaltyy said:
Yeah it says O firmware required. is there a specific way i need to erase the device in TWRP other than formatting data to rid the encryption? just want to be sure. it only says to erase /system and /data if coming from another ROM, im not sure if this includes stock sense also?
Click to expand...
Click to collapse
Especially going from stock sense to an AOSP style rom it's wise to wipe the whole thing because you don't want to mix two roms, strange behavior may occur.
Follow the instructions in the specific thread, if you want to run the phone unencrypted then you need to format data indeed.
Hey sorry to hijack thread but I'm having a similar issue, any sort of flashing I do results in the airplane mode getting stuck to "turning off" and I can't use my mobile network. I can flash my official T-Mobile RUU zip and things will work fine, but if I flash twrp on official it breaks. I switched over to the unlocked Dev rom and it breaks. I can only get my official zip working. Any help?
My specs are:
Android 7.0
2.51.617.32
S-off locked
1.0.U010241a 6117.76.02_f radio
Switched cid to bs_us01 or whatever the Dev cid is. For the rom. Other than lineageOS which didn't work, I haven't tried any other rom except dev.
kazuki1 said:
Hey sorry to hijack thread but I'm having a similar issue, any sort of flashing I do results in the airplane mode getting stuck to "turning off" and I can't use my mobile network. I can flash my official T-Mobile RUU zip and things will work fine, but if I flash twrp on official it breaks. I switched over to the unlocked Dev rom and it breaks. I can only get my official zip working. Any help?
My specs are:
Android 7.0
2.51.617.32
S-off locked
1.0.U010241a 6117.76.02_f radio
Switched cid to bs_us01 or whatever the Dev cid is. For the rom. Other than lineageOS which didn't work, I haven't tried any other rom except dev.
Click to expand...
Click to collapse
That's odd, flashing twrp works fine for me. maybe you need to unlock to be able to use twrp?
Mr Hofs said:
Especially going from stock sense to an AOSP style rom it's wise to wipe the whole thing because you don't want to mix two roms, strange behavior may occur.
Follow the instructions in the specific thread, if you want to run the phone unencrypted then you need to format data indeed.
Click to expand...
Click to collapse
Just an update, i flashed the Unofficial LineageOS 15.1 ROM and it works perfectly, thank you so much for your help it is greatly appreciated!
Mr Hofs said:
Especially going from stock sense to an AOSP style rom it's wise to wipe the whole thing because you don't want to mix two roms, strange behavior may occur.
Follow the instructions in the specific thread, if you want to run the phone unencrypted then you need to format data indeed.
Click to expand...
Click to collapse
Just an update, i flashed the Unofficial LineageOS 15.1 ROM and it works perfectly, thank you so much for your help it is greatly appreciated!
UPDATE 2: The rom flash didnt go as well as i thought, the camera and flashlight didnt work nomatter what i did so i went back to RUU Stock and it worked fine
twosaltyy said:
That's odd, flashing twrp works fine for me. maybe you need to unlock to be able to use twrp?
Click to expand...
Click to collapse
Twrp works and flashes normal, it just breaks my airplane mode making the network unusable when I try to do any sort of modding to stock.
kazuki1 said:
Twrp works and flashes normal, it just breaks my airplane mode making the network unusable when I try to do any sort of modding to stock.
Click to expand...
Click to collapse
Just as all the other comments, read what you are flashing and which roms.
Nougat firmware - nougat roms
Oreo firmware - oreo roms
You have NOUGAT firmware so ONLY nougat roms work.
G
Mr Hofs said:
Just as all the other comments, read what you are flashing and which roms.
Nougat firmware - nougat roms
Oreo firmware - oreo roms
You have NOUGAT firmware so ONLY nougat roms work.
Click to expand...
Click to collapse
I am flashing nougat roms, the wwe/dev rom I have running atm(which is giving me airplane issues) is the same as the official T-Mobile ruu I have that works, only difference is that it's the dev edition instead of t-mobile, same firmware and both are Android 7.0. Flashing full RUU and not any of these custom roms on here. I had only flashed lineage to see what it was like But got rid of it and put on my working T-Mobile ruu.
Both T-Mobile and dev edition RUU is taken from the official HTC website, they're the exact same thing.
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
Not very active here but worth a try.
How to unlock bootloader these days, is it even possible?
Phone is still on MIUI 10.2
the_bulk said:
Not very active here but worth a try.
How to unlock bootloader these days, is it even possible?
Phone is still on MIUI 10.2
Click to expand...
Click to collapse
why not?
https://c.mi.com/thread-1857937-1-1.html
https://en.miui.com/unlock/index.html
Then
https://xiaomirom.com/en/rom/redmi-note-5-note-5-pro-whyred-global-fastboot-recovery-rom/
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
All done rather easily. Thought there's maybe still those wait times.
the_bulk said:
All done rather easily. Thought there's maybe still those wait times.
Click to expand...
Click to collapse
Always 168 hours.
NOSS8 said:
Always 168 hours.
Click to expand...
Click to collapse
No, it did it instantly.
Should I flash latest stock firmware before going to put TWRP ? I want to put a custom rom .
the_bulk said:
No, it did it instantly.
Should I flash latest stock firmware before going to put TWRP ? I want to put a custom rom .
Click to expand...
Click to collapse
It does it instantly if you have already unlocked it but normally it's 168 hours now maybe on older phones it's instantaneous.
You did it?
installed the rom version requested by the OP of the AOSP rom that way you won't need to flash the firmware.
It was surely never unlocked , must be cause it's an old device as you say.
AOSP ROM says Oreo which the device has but no luck with TWRP though, fastboot flash recovery comes up with FAILED (remote: Anti-rollback check failed) .
Even tried to boot twrp with fastboot boot but that gets me stuck at MI logo.
Think I'll try putting in newer firmware tomorrow and see what happens.
edit: It worked with newer firmware flawlessly , probably I had wrong TWRP version that did't work with Oreo ARB version. Thanks for your input