Hi everyone, I have spent the past few hours searching for a similar problem but I can't quite figure it out and some help would be greatly appreciated!
As the title stated, I am on 6.0.1 and the unofficial CM13 with my baseband version being N910VVRU2CPF3. What I want to do is upgrade to hsbadr's 7.1.1 EmotionOS. In the Emotion thread it says that ROM Firmware Required: N910VVRS2CPL1. I am wondering what I do to get to that firmware.
Following this: https://forum.xda-developers.com/no...t/howto-bootloader-unlock-upgrade-to-t3398144
It says that
If you're already on unlocked Android 6.0.1 Marshmallow bootloader, you can extract and flash the DevEd partial firmware via Odin to upgrade:
This will upgrade the base firmware (NON-HLOS, modem, rpm, sbl1, sdi, and tz) to N910VVRS2CPL1.
Click to expand...
Click to collapse
I think that applies to me but it's only a partial firmware and that confuses me. Also, I don't know when to flash Emotion as well as the GApps (I'm assuming I'll have TWRP installed)
Sorry if this is all easy stuff but I'm relatively new to more complex android systems and all help would be greatly appreciated!
NinjaChachi said:
Hi everyone, I have spent the past few hours searching for a similar problem but I can't quite figure it out and some help would be greatly appreciated!
As the title stated, I am on 6.0.1 and the unofficial CM13 with my baseband version being N910VVRU2CPF3. What I want to do is upgrade to hsbadr's 7.1.1 EmotionOS. In the Emotion thread it says that ROM Firmware Required: N910VVRS2CPL1. I am wondering what I do to get to that firmware.
Following this: https://forum.xda-developers.com/no...t/howto-bootloader-unlock-upgrade-to-t3398144
It says that
I think that applies to me but it's only a partial firmware and that confuses me. Also, I don't know when to flash Emotion as well as the GApps (I'm assuming I'll have TWRP installed)
Sorry if this is all easy stuff but I'm relatively new to more complex android systems and all help would be greatly appreciated!
Click to expand...
Click to collapse
Is your phone a dev, or retail converted dev? Boot into downloading to see if it says Mode: Developer, in grey.
It does say Mode: Developer but I'm like 99% I had to convert it to that in the rooting process. I followed the guide on these forums to upgrade from stock 5.1.1 to CM13.
ziggy71 said:
Is your phone a dev, or retail converted dev? Boot into downloading to see if it says Mode: Developer, in grey.
Click to expand...
Click to collapse
It does say Mode: Developer but I'm like 99% I had to convert it to that in the rooting process. I followed the guide on these forums to upgrade from stock 5.1.1 to CM13.
NinjaChachi said:
It does say Mode: Developer but I'm like 99% I had to convert it to that in the rooting process. I followed the guide on these forums to upgrade from stock 5.1.1 to CM13.
Click to expand...
Click to collapse
You need to have upgraded from 5.1.1 to 6.0.1 and rooted that as well. Since you're on CM13, I'm assuming that you did that, so then all you need to do is flash the CPL1 partial firmware provided by hsbadr in the above post, full wipe, then clean flash EmotionOS. The firmware is partial because it only changes the base firmware, as long as you're on rooted 6.0.1 Marshmallow to begin with, you should be fine.
quinciebee said:
You need to have upgraded from 5.1.1 to 6.0.1 and rooted that as well. Since you're on CM13, I'm assuming that you did that, so then all you need to do is flash the CPL1 partial firmware provided by hsbadr in the above post, full wipe, then clean flash EmotionOS. The firmware is partial because it only changes the base firmware, as long as you're on rooted 6.0.1 Marshmallow to begin with, you should be fine.
Click to expand...
Click to collapse
Flash CPL1 and EmotionOS via TWRP? I am on rooted 6.0.1 btw
NinjaChachi said:
Flash CPL1 and EmotionOS via TWRP? I am on rooted 6.0.1 btw
Click to expand...
Click to collapse
Flash CPL1 via Odin, then clean flash EmotionOS via TWRP.
quinciebee said:
Flash CPL1 via Odin, then clean flash EmotionOS via TWRP.
Click to expand...
Click to collapse
Ok sweet! So the CPL1 partial firmware won't remove TWRP or anything?
NinjaChachi said:
Ok sweet! So the CPL1 partial firmware won't remove TWRP or anything?
Click to expand...
Click to collapse
Nope.
Related
I haven't done anything to my phone since I Unlocked my Bootloader, Upgraded to MM and Unlocked again, then installing PaulPizz from July (it's an outdated version, I know).
The thread I used to put on MM, put on the PD1 modem. I need to upgrade to PF3. I don't see a thread on how to do it Can someone explain to me how that works? Do I need to re-flash the full firmware and re-unlock or just the modem file? Please provide detailed instructions. Thanks.
Just download the partial update from here and flash via ODIN.
http://forum.xda-developers.com/showpost.php?p=67481370&postcount=1403
Note you are flashing a kernel as well so you may have to reflash whichever kernel you prefer.
BTW I'm still running Jasmine 6.0
freduser said:
Just download the partial update from here and flash via ODIN.
http://forum.xda-developers.com/showpost.php?p=67481370&postcount=1403
Note you are flashing a kernel as well so you may have to reflash whichever kernel you prefer.
Click to expand...
Click to collapse
Is a FDR required when flashing this file? Will I need to re-unlock?
Sent from my SM-N910V using Tapatalk
JOSHSKORN said:
Is a FDR required when flashing this file? Will I need to re-unlock?
Click to expand...
Click to collapse
If you're presently on a unlocked and rooted rom this will not lock the boot loader or require reroot.
freduser said:
If you're presently on a unlocked and rooted rom this will not lock the boot loader or require reroot.
Click to expand...
Click to collapse
so am on Xrom with the PD1 baseband,so what your saying all i should do is flash via odin the N910VVRU2CPF3 Partial Firmware + Patched Kernel and i can flash my prefer kernel after and i would be now on the latest baseband?
desmond462 said:
so am on Xrom with the PD1 baseband,so what your saying all i should do is flash via odin the N910VVRU2CPF3 Partial Firmware + Patched Kernel and i can flash my prefer kernel after and i would be now on the latest baseband?
Click to expand...
Click to collapse
Yes, this does not touch the boot loader as I understand.
freduser said:
Just download the partial update from here and flash via ODIN.
http://forum.xda-developers.com/showpost.php?p=67481370&postcount=1403
Note you are flashing a kernel as well so you may have to reflash whichever kernel you prefer.
Click to expand...
Click to collapse
I'm going to need better instructions.
I downloaded N910VVRU2CPF3_PartialFirmware_PatechedKernel.tar.md5.7z
Extracted it via 7zip
Booted into Download Mode
Connected my cable to my computer
Started Odin
Clicked AP, loaded N910VVRU2CPF3_PartialFirmware_PatechedKernel.tar.md5
Clicked START
It Failed.
Can you help me?
EDIT: OK, this is odd. It failed the first time and went through the second time. It worked. Thank you, @freduser .
No problem
Aren't pd1 and pf3 the same thing?
Hi,
I am running CYanogenMod 13.0-20360525 UNOFFICIAL tritevzw
Baseband N910VVRU2CPJ2
Build Number: ANdroid 6.0.1 MOB30JN910VVRU2BPA1
Whenever I go into settings and click on "Security" I get a popup box that says"
"Unfortunately Settings has stopped"
To try to fix this I have gone into recovery and wiped dalvik and caches.
Thanks for any help!
plainbum said:
Hi,
I am running CYanogenMod 13.0-20360525 UNOFFICIAL tritevzw
Baseband N910VVRU2CPJ2
Build Number: ANdroid 6.0.1 MOB30JN910VVRU2BPA1
Whenever I go into settings and click on "Security" I get a popup box that says"
"Unfortunately Settings has stopped"
To try to fix this I have gone into recovery and wiped dalvik and caches.
Thanks for any help!
Click to expand...
Click to collapse
What build of CM13 did you flash? Your build number says BPA1, but it should be saying CPF3.
quinciebee said:
What build of CM13 did you flash? Your build number says BPA1, but it should be saying CPF3.
Click to expand...
Click to collapse
Hi quinciebee, thanks fo ryour reply.
I was on ANdroid 6.0.1 MOB30JN910VVRU2 BPA1 and firmware BPA1
Then I wanted to try out Hsbadr's new 7.1.1 Nougat Rom and it required new CPJ2 firmware so I odin'd it in.
I TWRP backed up my ANdroid 6.0.1 MOB30JN910VVRU2 BPA1 build I have been running for months.
Then flashed his newest "EmotionOS" But could not get 4G LTE to work so I restored my 6.0 backup since I cant function on 3G only and no one in these forums was able to help me.
Hope that wasn't too confusing
Oh by the way, I am doing this on a Developer Edition Note 4 on Verizon
When I flashed CPJ2 firmware I used a partial build as explained here:
https://forum.xda-developers.com/no...t/howto-bootloader-unlock-upgrade-to-t3398144
He quotes:
Quote:
"If you're already on unlocked Android 6.0.1 Marshmallow bootloader, you can extract and flash the DevEd partial fimware via Odin to upgrade:
N910VVRU2CPJ2_PartialFirmware_DevEd.tar.md5.7z
This will upgrade the base firmware (NON-HLOS, modem, rpm, sbl1, sdi, and tz) to N910VVRU2CPJ2."
plainbum said:
Hi quinciebee, thanks fo ryour reply.
I was on ANdroid 6.0.1 MOB30JN910VVRU2 BPA1 and firmware BPA1
Then I wanted to try out Hsbadr's new 7.1.1 Nougat Rom and it required new CPJ2 firmware so I odin'd it in.
I TWRP backed up my ANdroid 6.0.1 MOB30JN910VVRU2 BPA1 build I have been running for months.
Then flashed his newest "EmotionOS" But could not get 4G LTE to work so I restored my 6.0 backup since I cant function on 3G only and no one in these forums was able to help me.
Hope that wasn't too confusing
Oh by the way, I am doing this on a Developer Edition Note 4 on Verizon
When I flashed CPJ2 firmware I used a partial build as explained here:
https://forum.xda-developers.com/no...t/howto-bootloader-unlock-upgrade-to-t3398144
He quotes:
Quote:
"If you're already on unlocked Android 6.0.1 Marshmallow bootloader, you can extract and flash the DevEd partial fimware via Odin to upgrade:
N910VVRU2CPJ2_PartialFirmware_DevEd.tar.md5.7z
This will upgrade the base firmware (NON-HLOS, modem, rpm, sbl1, sdi, and tz) to N910VVRU2CPJ2."
Click to expand...
Click to collapse
How did you flash CM13, and did you flash the 09/19 build?
quinciebee said:
How did you flash CM13, and did you flash the 09/19 build?
Click to expand...
Click to collapse
The build date is May 25 2016
Here is a list of roms of that ilk
https://forum.xda-developers.com/devdb/project/?id=12650#downloads
plainbum said:
The build date is May 25 2016
Here is a list of roms of that ilk
https://forum.xda-developers.com/devdb/project/?id=12650#downloads
Click to expand...
Click to collapse
Then I think that's the problem, you'll have to clean flash the 09/19 build.
Delete
quinciebee said:
Then I think that's the problem, you'll have to clean flash the 09/19 build.
Click to expand...
Click to collapse
I flashed to 09/19 build the phone would not boot. I kept getting a rapid glow behind the Blue android mascot.
I then tried to odin the BOG5 firmware and I got errors . rebooted the phone and it wouldnt boot.
Now just bootloops to the samsung screen,
It's borked.
I think I lost Dev Edition and the best I can do is start from scratch?
Not sure where to go now.
plainbum said:
I flashed to 09/19 build the phone would not boot. I kept getting a rapid glow behind the Blue android mascot.
I then tried to odin the BOG5 firmware and I got errors . rebooted the phone and it wouldnt boot.
Now just bootloops to the samsung screen,
It's borked.
I think I lost Dev Edition and the best I can do is start from scratch?
Not sure where to go now.
Click to expand...
Click to collapse
Is the BOG5 firmware stock? If so, you shouldn't have flashed it. If you still have TWRP and root, take these steps to clean flash to CM13.
1. Boot to TWRP, wipe all but your External Storage (SD Card)
2. Flash CM13 09/19 zip
3. Flash the boot image from CM13 07/24
(Click on install image, select the boot.img file, you will then see two choices: boot and recovery, select boot only, then swipe to flash.)
4. Flash gapps and SuperSU zip
5. Reboot
The rapid blinking was happening because you need the boot image from 07/24 in order for the rom to load properly. I'd post the boot image for you, but it exceeds the file size limit. To get the boot image, download the CM13 07/24 build, unzip the file, and extract the boot.img file to your SD card, along with everything else that you want to flash. Let me know if you need me to provide more details on any of the steps.
I can't even get into twrp.
All I can do is get into "Download mode"
I have started a new thread looking for help here:
https://forum.xda-developers.com/no...p-screwed-vzw-dev-ed-software-update-t3530282
plainbum said:
I can't even get into twrp.
All I can do is get into "Download mode"
I have started a new thread looking for help here:
https://forum.xda-developers.com/no...p-screwed-vzw-dev-ed-software-update-t3530282
Click to expand...
Click to collapse
What do you see when you try to boot into recovery?
Hi quinciebee,
I posted this before I borked my phone, before you started helping me.
How I got here was I was trying to upgrade the firmware so I could them flash The ne 7.1.1 "EmotionOS"
I was following the instruction here:
https://forum.xda-developers.com/no...t/howto-bootloader-unlock-upgrade-to-t3398144
Specifically where is says:
"If you're already on unlocked Android 6.0.1 Marshmallow bootloader, you can extract and flash the DevEd partial fimware via Odin to upgrade:
N910VVRU2CPJ2_PartialFirmware_DevEd.tar.md5.7z
This will upgrade the base firmware (NON-HLOS, modem, rpm, sbl1, sdi, and tz) to N910VVRU2CPJ2."
It flashed fine and then I installed the EmotionOS and all went well but I could NOT get 4G LTE to work, only 3G.
So I abandoned it and reflashed a backup of the CM 13 I was running since May 25.
I was good on cm13 but I got errors when I was in settings and tried to go into "Security"
Im all god now and I will be trying to get back to 6.0 and then 7.1.1 after my house guests leave.
The phone is running fine in 5.1.1.
THanks again!
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:
Hello everyone
I know there's no root available because of locked bootloader on N910A but i found this rom its pre rooted on 5.0.1 lollipop .
Anyone have tested this rom before ?
Let me know if there's anyone tested it.
WARNING
PLEASE FLASH ON YOUR OWN RISK I AM NOT RESPONSIBLE FOR ANY DAMAGES OF YOUR DEVICE.
MUST BE FLASH all 3 FILES TOGETHER VIA ODIN TOOL
BL/BOOTLOADER N910AUCU1COC4
https://androidfilehost.com/?fid=23991606952606182
CP/MODEM N910AUCU1COC4
https://androidfilehost.com/?fid=23991606952606184
AP/ROOTED SYSTEM FIRMWARE N910AUCU1COC4
https://androidfilehost.com/?fid=23991606952605865
AFTER FLASHING IF YOU STUCK IN A BOOTLOOP JUST GO TO RECOVERY AND DO A FACTORY RESET/WIPE CACHE.
PLEASE REPORT BACK OR SHARE SOME SCREENSHOTS SO OTHERS MAY KNOW.
Trex888 said:
Hello everyone
I know there's no root available because of locked bootloader on N910A but i found this rom its pre rooted on 5.0.1 lollipop .
Anyone have tested this rom before ?
On lolipop COC6 is the last we can downgrade from lolipop or marshmallow COC4 will not be flashed through Odin :silly:
I have tried rooting DIO2 and flashing rooted 5.0.1 through flasfire ...the flash was succesfull flashfire was able to completly flash the rom but the mobile colud not pass boot screen
I think its due to 5.1.1 BL that prevented booting 5.0.1 rom
So what we need is pre rooted 5.1.1 rom to flash through flashfire
Click to expand...
Click to collapse
pawar21 said:
Trex888 said:
Hello everyone
I know there's no root available because of locked bootloader on N910A but i found this rom its pre rooted on 5.0.1 lollipop .
Anyone have tested this rom before ?
On lolipop COC6 is the last we can downgrade from lolipop or marshmallow COC4 will not be flashed through Odin :silly:
I have tried rooting DIO2 and flashing rooted 5.0.1 through flasfire ...the flash was succesfull flashfire was able to completly flash the rom but the mobile colud not pass boot screen
I think its due to 5.1.1 BL that prevented booting 5.0.1 rom
So what we need is pre rooted 5.1.1 rom to flash through flashfire
Click to expand...
Click to collapse
If COC4 & COC6 BOTH ARE 5.0 THEN WE CAN FLASH COC6 BL/MODEM ALONG WITH COC4 ROOTED FIRMWARE I GUESS IT SHOULD MAKE IT BOOT.
Click to expand...
Click to collapse
Trex888 said:
pawar21 said:
If COC4 & COC6 BOTH ARE 5.0 THEN WE CAN FLASH COC6 BL/MODEM ALONG WITH COC4 ROOTED FIRMWARE I GUESS IT SHOULD MAKE IT BOOT.
Click to expand...
Click to collapse
I have tried both COC6 and COC4 but couldnt pass boot splash screen ...because i am flashing 5.0 over 5.1.1 temp rooted using flashfire
Click to expand...
Click to collapse
Trex888 said:
...i found this rom...
Click to expand...
Click to collapse
The development section is for posting your own development work. Please make sure you have read and understood the sticky titled "RULES for Posting in Development" before posting there.
THREAD MOVED
pawar21 said:
Trex888 said:
I have tried both COC6 and COC4 but couldnt pass boot splash screen ...because i am flashing 5.0 over 5.1.1 temp rooted using flashfire
Click to expand...
Click to collapse
Is there any particular reason this thread died? Granted, there may not be that many individuals that haven't already been screwed by a forced update, but I would think that 5.0.1 could be temp rooted as well. Perhaps I missed the point?
Click to expand...
Click to collapse
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