Related
According to the Verizon Galaxy S5 Update Page:
The current software update gives you the most up to date Android® security patches on your device.
Click to expand...
Click to collapse
The security patch included is the April (2017-04-01) one.
Stock No-Wipe FW. Will remove Developer Status Bootloader:
G900VVRS2DQD1_G900VVZW2DQD1_G900VVRS2DQD1_HOME.tar.md5.zip
Developer Bootloader Friendly:
G900VVRS2DQD1_G900VVZW2DQD1_G900VVRS2DQD1_HOME_No_Aboot.tar.md5.zip
what does the Developer Bootloader Friendly mean or differ from Stock No-Wipe FW. Will remove Developer Status Bootloader?
Thankyou!
knight194 said:
what does the Developer Bootloader Friendly mean or differ from Stock No-Wipe FW. Will remove Developer Status Bootloader?
Thankyou!
Click to expand...
Click to collapse
If you have a Developer Edition phone, the Stock one will remove the Developer status. The Developer Bootloader Friendly one won't.
Quick question... I've been on Lineage, and have flashed this and gone back (to update the baseband). But, do you know off-hand, how do I easily root on this image? My BL is still unlocked and I've got TWRP reinstalled.
Thanks!
sry this is off subject but what is the latest modem update for the 900v or the best one in regards to best lte signal?
nictabor said:
Quick question... I've been on Lineage, and have flashed this and gone back (to update the baseband). But, do you know off-hand, how do I easily root on this image? My BL is still unlocked and I've got TWRP reinstalled.
Thanks!
Click to expand...
Click to collapse
If you have TWRP installed, just flash a SuperSU zip (i.e. SuperSU 2.79 SR3) in recovery and you'll be rooted.
Unless of course you're talking about going back to Lineage and re-rooting. In that case, you'll have to use the Lineage root zip, which I don't have a link to.
KazuDante said:
sry this is off subject but what is the latest modem update for the 900v or the best one in regards to best lte signal?
Click to expand...
Click to collapse
Normally the latest update provides the latest/best modem.
Dudash said:
If you have TWRP installed, just flash a SuperSU zip (i.e. SuperSU 2.79 SR3) in recovery and you'll be rooted.
Unless of course you're talking about going back to Lineage and re-rooting. In that case, you'll have to use the Lineage root zip, which I don't have a link to.
Normally the latest update provides the latest/best modem.
Click to expand...
Click to collapse
where can i find the latest modem for the 900v , and im guessing its a flash process using odin correct?
KazuDante said:
where can i find the latest modem for the 900v , and im guessing its a flash process using odin correct?
Click to expand...
Click to collapse
It depends. It could be a .tar file you flash via Odin or it could be a flashable zip via TWRP. It depends on the maker of the file.
It's just the modem.bin file from the update. I don't have the time to make one for it right now.
Dudash said:
If you have TWRP installed, just flash a SuperSU zip (i.e. SuperSU 2.79 SR3) in recovery and you'll be rooted.
Unless of course you're talking about going back to Lineage and re-rooting. In that case, you'll have to use the Lineage root zip, which I don't have a link to.
Normally the latest update provides the latest/best modem.
Click to expand...
Click to collapse
I actually figured it out while waiting. Thank you for responding though!
nictabor said:
I actually figured it out while waiting. Thank you for responding though!
Click to expand...
Click to collapse
You're welcome.
On a side note, it seems like Verizon read the recent articles where the Galaxy S5 was still rated as the most popular smart phone being used on any network. Meaning, they are updating the phone monthly now, which is good news for us. We won't ever get Nougat but apparently we'll get Security Patches monthly now.
Dudash said:
It depends. It could be a .tar file you flash via Odin or it could be a flashable zip via TWRP. It depends on the maker of the file.
It's just the modem.bin file from the update. I don't have the time to make one for it right now.
Click to expand...
Click to collapse
so can i take the modem.bin file from this update and replace it with the one from a 7.1.2 rom ? also i used to mess with porting roms but on mediatek platform , are the modem files still located in /system/etc/firmware directory?
because what i see is modem.b00-b27 ,modem.mdt
---------- Post added at 08:04 PM ---------- Previous post was at 07:08 PM ----------
i tried flashing the dev friendly one and the md5 check failed....am i missing something?
Dudash said:
According to the Verizon Galaxy S5 Update Page:
The security patch included is the April (2017-04-01) one.
Stock No-Wipe FW. Will remove Developer Status Bootloader:
G900VVRS2DQD1_G900VVZW2DQD1_G900VVRS2DQD1_HOME.tar.md5.zip
Developer Bootloader Friendly:
G900VVRS2DQD1_G900VVZW2DQD1_G900VVRS2DQD1_HOME_No_Aboot.tar.md5.zip
Click to expand...
Click to collapse
Developer bootloader friendly??? Do 11 EMMC Chips finally have freedom???
how do we flash this update , odin fails on md5 check
Deleted
flashed the update but phone stuck on verizon logo.
did i do something wrong?
i would assume due to the fact that the bootloader is not its bootloader it froze/locked up , so heres my question if i flash the non dev friendly one , can that bootloader be unlocked or its better not to risk it?
KazuDante said:
flashed the update but phone stuck on verizon logo.
did i do something wrong?
i would assume due to the fact that the bootloader is not its bootloader it froze/locked up , so heres my question if i flash the non dev friendly one , can that bootloader be unlocked or its better not to risk it?
Click to expand...
Click to collapse
I would not do it.
erw38 said:
I would not do it.
Click to expand...
Click to collapse
Since there no tut regarding an unlocked version of this update I simply updated from bpb1 to qa1 , just needed my modem to be somewhat up to date , but it seems that it's def a tx rx issue in my case , so my best bet is a custom kernel with that feature included.
KazuDante said:
Since there no tut regarding an unlocked version of this update I simply updated from bpb1 to qa1 , just needed my modem to be somewhat up to date , but it seems that it's def a tx rx issue in my case , so my best bet is a custom kernel with that feature included.
Click to expand...
Click to collapse
I didn't think a tutorial was necessary as I've never had to give one in the past. If your device is unlocked, you should know it. That's the only reason there is a Dev Friendly version of the update. It won't unlock your bootloader, but it won't lock it if it is unlocked. That's the only reason I make a Developer Bootloader Friendly version of updates.
If you want to update your modem but not the firmware, open either of the files in 7zip/WinZip, extract the modem.bin, then repackage it as a .tar file and flash it in Odin.
KazuDante said:
flashed the update but phone stuck on verizon logo.
did i do something wrong?
i would assume due to the fact that the bootloader is not its bootloader it froze/locked up , so heres my question if i flash the non dev friendly one , can that bootloader be unlocked or its better not to risk it?
Click to expand...
Click to collapse
In regard to your previous post, there is no problem with the MD5 for either file or any problem with the files themselves. I test them both before uploading them to prevent problems like this for people. I flashed the Dev Friendly version on both of my eMMc 15 S5's and experienced zero problems. The phone will hang on the "Verizon logo" for a minute or two at first boot but it will go past it and continue to "Optimizing" after that.
If you flash the Stock version, if your bootloader is unlocked, it will lock it and in order to re-unlock it, you'll have to use jrkruse's unlock method which requires you to go back to PB1. As of this post, he has not created a QD1 bootloader unlocker. The latest bootloader unlocker he has created is for QC2, which still requires you to have an unlocked bootloader prior to flashing it.
EDIT: Also, if you use an app like Package Disabler Pro to disable applications without root, it can cause updates to hang indefinitely at first boot if you don't re-enable all disabled applications and turn off/remove Admin rights for Package Disabler Pro prior to updating. I've experienced this in the past with both of my S5's and my S7. I'm not directing this at you KazuDante, this is just a warning to all.
21-Savage said:
Developer bootloader friendly??? Do 11 EMMC Chips finally have freedom???
Click to expand...
Click to collapse
No. The Developer Bootloader Friendly version is just that, friendly to devices with a Developer Bootloader. Meaning it won't remove Developer Bootloader status/lock the bootloader.
If I had figured out a way to help all of the eMMc 11 people unlock their bootloader, I would've made a thread that clearly stated that.
I think the only way people with Toshiba eMMc's will get an unlocked bootloader is if either
A: Verizon provides an update to unlock the bootloaders on all S5's AFTER they stop putting out Security Updates, which is highly unlikely since it is Verizon, they've never done it before, and there's no end to Security Updates in sight.
B: Someone at Samsung or Verizon leaks an engineering bootloader. This is the most likely scenario since it's happened before. First, in my experience, with the VZW S3, and the latest being with the S7. There's still hope but it may rely on someone from within Verizon or Samsung feeling bad for us.
Sorry
@Dudash Any idea how to go from the Dev-friendly QD1 version you uploaded to a TWRP flashable zip file which resembles the jrkruse VZW_QA1_STOCK_ROOTED_DEODEXED.zip? I really like to debloat and root before flashing. Thanks!
I got the "custom binary boot blocked by frp lock" issue so I gotta reflash the stock firmware, which I should have since I did a full TWRP backup so if I convert my twrp backup in to a flashable zip will i be able to flash it through ODIN? (obviously i cant do it through TWRP Recov since I can only access download mode)
I can get the stock firmware from sammobile.com but its going to take like 4h+ to download and I dont have time for that
izou1838 said:
I got the "custom binary boot blocked by frp lock" issue so I gotta reflash the stock firmware, which I should have since I did a full TWRP backup so if I convert my twrp backup in to a flashable zip will i be able to flash it through ODIN? (obviously i cant do it through TWRP Recov since I can only access download mode)
I can get the stock firmware from sammobile.com but its going to take like 4h+ to download and I dont have time for that
Click to expand...
Click to collapse
Had the same issue. Rookie mistake. I accidentally left the developer option OEM unlock disabled and viola! Had to do a reset. Also, if you had any fingerprints while using the Rom you used, You might come into issues when resetting using Odin. You might have to format your internal memory using TWRP. Im not saying its something slcertain. I just had to. The only firmware I had available was a 6.0.1 MM stock Rom and I came into issues when unlocking the phone. Remember, this was a full reinstall in Odin and the screen was locked. When I unlocked the screen it would just reboot. So, lesson learned. Make sure if you go and root your phone again never ever, ever, ever disable that option in developer.
But try it. You can follow the steps from the root guide for nougat in the threads and go up until the step where you install TWRP. Boot into TWRP and see if you can restore the backup. Chances are it might work without having to do the extra steps like reinstalling the stock firmware. If that doesn't work and you run into issues in TWRP you might need to reinstall everything from scratch again.
Thanks! Already figured it out ?
please explain
izou1838 said:
Thanks! Already figured it out
Click to expand...
Click to collapse
my note 5 is at custom binary blocked by frp lock. i think I also turned off the option of oem unlock in developers option by mistake.
I have twrp back up on pc only. please help me how to unbrick the phone now.
Unfortunately the TWRP back is no help ):
However if you have the stock full system image you can just flash that through ODIN and then re-root? easy fix.
Look for the image here in XDA I've seen it
Sir i have note 5 with csc n920pvps3bpk1 shows in phone aftar dialing *#1234# but on the box of this cell phone is printed as n920fvps3bpk1 and n9200 will u plz tell me which csc is correct and i want to upgrade it to 7.0 and its knox waranty has voided.
izou1838 said:
I got the "custom binary boot blocked by frp lock" issue so I gotta reflash the stock firmware, which I should have since I did a full TWRP backup so if I convert my twrp backup in to a flashable zip will i be able to flash it through ODIN? (obviously i cant do it through TWRP Recov since I can only access download mode)
I can get the stock firmware from sammobile.com but its going to take like 4h+ to download and I dont have time for that
Click to expand...
Click to collapse
Hi, I have the same problem with an SM-520F, did you manage to solve it?
According to the Verizon Galaxy S5 Update Page:
Android® Security Patch Level: 2017–08-01
The current software update gives you the most up to date Android security patches on your device.
Click to expand...
Click to collapse
This is basically the same thing they are doing with other devices. Since Samsung never released their September Security patch due to them addressing the BlueBorne problem, they have been re-releasing the QH* updates as QI* but they include the BlueBorne patch. For some reason, Verizon didn't include the BlueBorne patch in the changelog like they have been for every other phone.
For example. The Galaxy S6, Galaxy S8, and Galaxy S8+ updates all say
Includes: Blueborne security patch
The current software update gives you the most up to date Android® security patches on your device.
Click to expand...
Click to collapse
Who knows why they chose to include the exact same changelog as the prior update with the same security patch. Whatever. Verizon sucks. We all know it.
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQI2_G900VVZW2DQI2_G900VVRU2DQI2_HOME.tar.md5.zip
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQI2_G900VVZW2DQI2_G900VVRU2DQI2_HOME_No_Aboot.tar.md5.zip
Also, I'm not sure how much longer I'll be doing this though because the screen on my S5 is going bad (flickering and flashing green whenever I bring it out of sleep) so this weekend I'm getting an S8+.
so its safe to say that the new modem ql2 is pretty much the same sa the previous update?
Updated to this build from QH2, flashed in odin, then booted up, reflashed TWRP and SU, froze system updater all good. If you do end up leaving, this will just be another loss for this model as no one else is updating the stock images anymore.
Thank you for your work on this. Does this have root, and if not, do those of us with locked bootloaders have a way to keep root and safestrap?
Tell us how the S8+ goes and if you can unlock the bootloader and root that. Thanks again!
Dudash said:
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQI2_G900VVZW2DQI2_G900VVRU2DQI2_HOME.tar.md5.zip
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQI2_G900VVZW2DQI2_G900VVRU2DQI2_HOME_No_Aboot.tar.md5.zip
Also, I'm not sure how much longer I'll be doing this though because the screen on my S5 is going bad (flickering and flashing green whenever I bring it out of sleep) so this weekend I'm getting an S8+.
Click to expand...
Click to collapse
For the record, this loses root, and loses safestrap. I'm too dumb to know how to root this since I can't get TWRP on this phone, so I'm going to hope the way back to root and safestrap is get back Kitkat and then up to PB1 starting over using these steps.. This will probably be better for someone who knows what they're doing or just wants to upgrade for the security updates and doesn't care about root.
androidman807 said:
Thank you for your work on this. Does this have root, and if not, do those of us with locked bootloaders have a way to keep root and safestrap?
Tell us how the S8+ goes and if you can unlock the bootloader and root that. Thanks again!
Click to expand...
Click to collapse
I have a 15 Emmc chip and unlocked the bootloader via this thread: https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529
I flashed EMMC_15_VZW_QB2_STOCK_MAGISK_ROOT.zip to my phone. I also have TWRP installed.
Now, if I understand all this correctly, I can simply flash your Developler Boatloader friendly version via TWRP? This will upgrade my OS to the latest update? Then flash Magisk to get root back?
This all seems too simple.
You will also have to re-flash TWRP via Odon.
kevin98208 said:
I have a 15 Emmc chip and unlocked the bootloader via this thread: https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529
I flashed EMMC_15_VZW_QB2_STOCK_MAGISK_ROOT.zip to my phone. I also have TWRP installed.
Now, if I understand all this correctly, I can simply flash your Developler Boatloader friendly version via TWRP? This will upgrade my OS to the latest update? Then flash Magisk to get root back?
This all seems too simple.
Click to expand...
Click to collapse
HolyHog said:
You will also have to re-flash TWRP via Odon.
Click to expand...
Click to collapse
I too followed the instructions in the thread above for a CID 15 eMMC.
I was unable to flash the "G900VVRU2DQI2_G900VVZW2DQI2_G900VVRU2DQI2_HOME_No_ Aboot.tar.md5.zip" from the OP using TWRP, but was able to do it no problem using Odin 3.12 (AP option).
After flashing that I then used Odin again (AP option) to flash the latest TWRP (https://dl.twrp.me/klte/twrp-3.1.1-0-klte.img.tar.html). I then did another factory reset on the phone (since I had already just wiped my data following the bootloader instructions) and reinstalled Magisk from TWRP and MagiskManager.
Everything looks great so far. Thanks for this update OP and for those of you providing guidance.
I have G900VVRU2DPD1 with unlocked bootloader and twrp 3.0.0-0.
Can I flash the
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQI2_G900VVZW2DQI2_G900VVRU2DQI2_HOME_No_ Aboot.tar.md5.zip ?
If yes, after flashing, will my bootloader remain PD1 unlocked? Is it OK to have unlocked PD1 bootloader with DQI2 firmware?
Will the TWRP and root be lost? And how I can get back TWRP? Using ODIN? If root is lost then can not use flashify to flash TWRP.
If using odin to flash TWRP, then I can just flash supersu zip in zip to get root back, right?
Thanks.
I guess this is slightly off topic since it's not about this specific firmware version, but here goes ~
How do you guys go about extracting firmware/modems from stock ROM updates?? It boggles my mind lol. I'm running a OP3T now, but am working on an old device (and I still have my old S5 too). Over the years it appears people are now able to do this process for most devices and make it flashable one way or another.
I wish I understood how this gets done (and possibly figure out how to do it myself). Would love a guide / video / brief explanation with terms I could look up if it's long & involved??
Thanks for the work!
purplepenguin said:
How do you guys go about extracting firmware/modems from stock ROM updates??
Click to expand...
Click to collapse
Stock ROM update is just a tar archive with files inside.
The names of the files are mostly self-explaining.
Use some tool to access the archive, like Total Commander or 7zip archiver.
bbsc said:
Stock ROM update is just a tar archive with files inside.
The names of the files are mostly self-explaining.
Use some tool to access the archive, like Total Commander or 7zip archiver.
Click to expand...
Click to collapse
Hmmm and then to make flashable??
purplepenguin said:
Hmmm and then to make flashable??
Click to expand...
Click to collapse
Just pack what you want into tar archive and it will be flashable.
No need to attach checksum.
But it's possible too.
Say, this tar-file is flashable:
Missing apps
TraderJack said:
and reinstalled Magisk from TWRP and MagiskManager.
Click to expand...
Click to collapse
Can I reuse the same Magisk from the "EMMC_15_VZW_QB2_STOCK_MAGISK_ROOT.zip" file from the other thread on how to unlock bootloader and root, or should I download the latest Magisk and MagiskManager?
Edit 1: Okay, I installed Magisk after updating to the latest QI2 and am rooted. However, I found that I'm missing busybox and safestrap. Do I have to reinstall both of those as well or can I just reinstall busybox?
Also, QI2 lost tether/hotspot capability as it reverted back to asking to purchase the service (I'm also on the old grandfathered unlimited plan)...is there a way to get it back as when on rooted QB2?
Edit 2: Did some more research while hiding at work...so now I know, having TWRP recovery is enough and just need to reinstall busybox.
Now still need to find a way to get hotspot capability back like when on the rooted magisk QB2...
Thanks
Hi! I'm really humbly sorry, I'm new to this stuff, so I have to ask you...
I have a Galaxy S8+ Duos (SM-GD955FD). I bricked it once or twice trying to root it. So I had to flash a sammobile.com ROM...
Now this is done, I have a successfully rooted phone with with the Baseband version G955FXU1AQH3 and the irritating "security notice" (since I was not able to install Magisk, and the NotifyClean app doesn't work either).
I would like to flash the latest Oreo and root it. I also heard good things about the Oreo ROM by alexega.
So: I'm on AQH3 rooted. What can I do?
Thank you for your patience.
If wou want to install stock ROM you must follow this instructions: https://forum.xda-developers.com/galaxy-s8+/how-to/guide-how-to-flash-crap-using-odin-t3748555. Bear in mind that if you install stock due to security issues you can't unlock OEM for 7 days after flashing (you must not reboot your phone for 170 hours).
If wou want to flash a custom rom you must have TWRP installed, move the zip rom to your SD card and just flash it from recovery. Make sure to format data before flashing.
josegon30 said:
If wou want to install stock ROM you must follow this instructions: https://forum.xda-developers.com/galaxy-s8+/how-to/guide-how-to-flash-crap-using-odin-t3748555. Bear in mind that if you install stock due to security issues you can't unlock OEM for 7 days after flashing (you must not reboot your phone for 170 hours).
If wou want to flash a custom rom you must have TWRP installed, move the zip rom to your SD card and just flash it from recovery. Make sure to format data before flashing.
Click to expand...
Click to collapse
Nice, thank you. So I have just flashed the thing with the sammobile.com ROM again (so, no root) and updated to the oroginal firmware Oreo following your link (I worked parallel).
I was just about to root Oreo and was googling for a way... But did I get you right? I should not reboot my phone for 170 hours now?!? So, no rooting until next week?!
Edit: I have developer options enabled and the "OEM unlock" switch is on (it says: "Bootloader is already unlocked.""). So... confusion...
andifla852 said:
Nice, thank you. So I have just flashed the thing with the sammobile.com ROM again (so, no root) and updated to the oroginal firmware Oreo following your link (I worked parallel).
I was just about to root Oreo and was googling for a way... But did I get you right? I should not reboot my phone for 170 hours now?!? So, no rooting until next week?!
Edit: I have developer options enabled and the "OEM unlock" switch is on (it says: "Bootloader is already unlocked.""). So... confusion...
Click to expand...
Click to collapse
Excuse me, are you currently on Nougat 7.0? If so, you obviously have OEM unlock option available. The problem is in the new 8.0 stock rom, wich sets RMM state to pre-normal preventing you to flash TWRP and to get root in OREO. To skip that you can directly flash a custom rom with 8.0.- Otherwise (stock rom) you must wait 7 days with no phone reboot to get ridd of that pre-normal issue and then flash TWRP and flash Magisk.
Just rooted the new Oreo ROM with TWRP. Works just fine, thank you.
So, what are the advantages of the Oreo ROM by alexega compared to XXU1CRAP?
josegon30 said:
Excuse me, are you currently on Nougat 7.0? If so, you obviously have OEM unlock option available. The problem is in the new 8.0 stock rom, wich sets RMM state to pre-normal preventing you to flash TWRP and to get root in OREO. To skip that you can directly flash a custom rom with 8.0.- Otherwise (stock rom) you must wait 7 days with no phone reboot to get ridd of that pre-normal issue and then flash TWRP and flash Magisk.
Click to expand...
Click to collapse
Hi Jose. I am with stock nogat. Not root. Any advice for flash stock oreo firmware?
Allrey know about odin. Im talking about unlock options, etc.
Thks
Juan from Argentina.
juange said:
Hi Jose. I am with stock nogat. Not root. Any advice for flash stock oreo firmware?
Allrey know about odin. Im talking about unlock options, etc.
Thks
Juan from Argentina.
Click to expand...
Click to collapse
Just follow the steps from the link in my previous repply. As it's an original software, it won't trip knox or void your warantee.
hi, does anybody knows how to install the oreo firmware using odin but without changing the csc I already have?
josegon30 said:
Excuse me, are you currently on Nougat 7.0? If so, you obviously have OEM unlock option available. The problem is in the new 8.0 stock rom, wich sets RMM state to pre-normal preventing you to flash TWRP and to get root in OREO. To skip that you can directly flash a custom rom with 8.0.- Otherwise (stock rom) you must wait 7 days with no phone reboot to get ridd of that pre-normal issue and then flash TWRP and flash Magisk.
Click to expand...
Click to collapse
Do you need a custom rom to not have the RMM lock anymore? A stock with BlackMesa's RMM START .zip is not right?
costafabiof said:
Do you need a custom rom to not have the RMM lock anymore? A stock with BlackMesa's RMM START .zip is not right?
Click to expand...
Click to collapse
There's no need to have a custom rom, if you flash the fix in stock RMM lock gets killed everytime.
josegon30 said:
There's no need to have a custom rom, if you flash the fix in stock RMM lock gets killed everytime.
Click to expand...
Click to collapse
Did not work.
I can not find out where I went wrong.
developer11 said:
Android.com.pl **** you
Little cocksucker
Click to expand...
Click to collapse
Translation?
costafabiof said:
Did not work.
I can not find out where I went wrong.
Click to expand...
Click to collapse
First you have to install OREO and wait 7 days without reseting your phone. After 170 hours, you get OEM unlock in developer options and you will be able to flasf TWRP. After flashing TWRP you flash RMM-State_Bypass_Mesa and that´s all.
josegon30 said:
First you have to install OREO and wait 7 days without reseting your phone. After 170 hours, you get OEM unlock in developer options and you will be able to flasf TWRP. After flashing TWRP you flash RMM-State_Bypass_Mesa and that´s all.
Click to expand...
Click to collapse
That did not work out. But thank you for your attention.
hello everyone,
i have S8+ with android 7 installed, not rooted and still didnt get any OTA for either oreo or Pie, so i decided to do it manually but i wanna make sure of the steps since it's been a while for me not flashing anything.
first thing i should know is that this update is going to wipe my phone due to the bootloader update
and about that bootloader update, should i flash pie bootloader first or just flash a stock ROM with odin that includes bootloader file ?
any help with this issue is much appreciated
Warnahly said:
hello everyone,
i have S8+ with android 7 installed, not rooted and still didnt get any OTA for either oreo or Pie, so i decided to do it manually but i wanna make sure of the steps since it's been a while for me not flashing anything.
first thing i should know is that this update is going to wipe my phone due to the bootloader update
and about that bootloader update, should i flash pie bootloader first or just flash a stock ROM with odin that includes bootloader file ?
any help with this issue is much appreciated
Click to expand...
Click to collapse
I got my update just few days ago. Why don't you just wait for it.
Warnahly said:
hello everyone,
i have S8+ with android 7 installed, not rooted and still didnt get any OTA for either oreo or Pie, so i decided to do it manually but i wanna make sure of the steps since it's been a while for me not flashing anything.
first thing i should know is that this update is going to wipe my phone due to the bootloader update
and about that bootloader update, should i flash pie bootloader first or just flash a stock ROM with odin that includes bootloader file ?
any help with this issue is much appreciated
Click to expand...
Click to collapse
If you are going to update with Odin flash full firmware. ( 4 files )
As for wiping your phone when you unzip the downloaded firmware there will be 2 CSC files.
CSC - Clean install will wipe your data ( same as factory reset )
Home CSC - Dirty install should keep your data
Always do a backup before doing anything.
Note: Make sure after you upgrade your firmware to update your apps so that they will be comparable with new firmware.