how to root and install TWRP or CWM in January 2018 security patch?? :crying:
version : A520FXXU4BRA8
xXxDmCxXx said:
how to root and install TWRP or CWM in January 2018 security patch?? :crying:
version : A520FXXU4BRA8
Click to expand...
Click to collapse
Not a chance.
ashyx said:
Not a chance.
Click to expand...
Click to collapse
can I do rooting without twrp?
xXxDmCxXx said:
can I do rooting without twrp?
Click to expand...
Click to collapse
Unfortunately you can't root or modify at all.
ashyx said:
Not a chance.
Click to expand...
Click to collapse
Is there any change that we would modify our phones again with February security patch? I mean it is possible that the bootloader may become level 2 again or so?
Hi, i have A520FXXBQIJ with twrp and root... so i just download the new firmware, i.e.from sammobile, flash with flashfire and bootloader is save/not locked??
catdoggy said:
Hi, i have A520FXXBQIJ with twrp and root... so i just download the new firmware, i.e.from sammobile, flash with flashfire and bootloader is save/not locked??
Click to expand...
Click to collapse
Should be fine if you update with Flashfire.
ashyx said:
Should be fine if you update with Flashfire.
Click to expand...
Click to collapse
Thanks, sounds good. I will test it on weekend
ashyx said:
Should be fine if you update with Flashfire.
Click to expand...
Click to collapse
Can you run through steps needed to do this via Flashfire?
My A5 2017 is still on November patch, but not rooted. It never auto updated because I already tripped knox when I unsuccessfully tried to root with Chainfire. Could I just use Odin to update to everything to January (excluding the BL, which would come from Marshmallow) and then try to install TWRP and the 'No Verity/Encrypt' patch? Does it matter what version of TWRP or root manager I use?
And from then on, I'll need to update only through "flashfire" if I want to be able to root again? Logic tells me I could just keep using Odin with the MM bootloader as I described above to repeat the process.
Charles Miller said:
My A5 2017 is still on November patch, but not rooted. It never auto updated because I already tripped knox when I unsuccessfully tried to root with Chainfire. Could I just use Odin to update to everything to January (excluding the BL, which would come from Marshmallow) and then try to install TWRP and the 'No Verity/Encrypt' patch? Does it matter what version of TWRP or root manager I use?
And from then on, I'll need to update only through "flashfire" if I want to be able to root again? Logic tells me I could just keep using Odin with the MM bootloader as I described above to repeat the process.
Click to expand...
Click to collapse
Just make sure you only use the sboot.bin from the Marshmallow firmware when flashing with Odin.
ashyx said:
Just make sure you only use the sboot.bin from the Marshmallow firmware when flashing with Odin.
Click to expand...
Click to collapse
I'm not sure I follow. Aren't all the files I flash MD5 Files? My assumption was that I download the stock firmwares of MM and January Nougat from a site like Sammoble, finding the right files with my phone specs (CSC, build number, baseband). Then I start up Odin and put all the MD5 files from the downloaded folders into their appropriate sections (AP in AP, BL in BL, ect), using the bootloader MD5 file from Marshmellow, but everything else from the January Nougat folder. Then flash it.
I went through this process to fix my A5 after my first failed root attempt left it unable to enter recovery mode, except I just needed only the November nougat MD5 files. I don't recall using or even downloading any "bin" files.
Charles Miller said:
I'm not sure I follow. Aren't all the files I flash MD5 Files? My assumption was that I download the stock firmwares of MM and January Nougat from a site like Sammoble, finding the right files with my phone specs (CSC, build number, baseband). Then I start up Odin and put all the MD5 files from the downloaded folders into their appropriate sections (AP in AP, BL in BL, ect), using the bootloader MD5 file from Marshmellow, but everything else from the January Nougat folder. Then flash it.
I went through this process to fix my A5 after my first failed root attempt left it unable to enter recovery mode, except I just needed only the November nougat MD5 files. I don't recall using or even downloading any "bin" files.
Click to expand...
Click to collapse
If you do it that way then you will be flashing more than just the bootloader as there are several images in the BL tar file, sboot.bin is one of these.
It will likely work, but there maybe wifi and telephony issues.
ashyx said:
If you do it that way then you will be flashing more than just the bootloader as there are several images in the BL tar file, sboot.bin is one of these.
It will likely work, but there maybe wifi and telephony issues.
Click to expand...
Click to collapse
I see. So you're saying that instead of just loading the whole BL file from Marshmallow into Odin, I need to do something else. Are you advising that I find a way to take this sboot.bin file out of the Marshmallow BL MD5 file and put it into the BL section of Odin as it is? Or am I supposed to replace the sboot.bin file of the January Nougat bootloader MD5 with the sboot.bin file of the Marshmellow bootloader to create a sort of customised BL MD5, then flash that?
Charles Miller said:
I see. So you're saying that instead of just loading the whole BL file from Marshmallow into Odin, I need to do something else. Are you advising that I find a way to take this sboot.bin file out of the Marshmallow BL MD5 file and put it into the BL section of Odin as it is? Or am I supposed to replace the sboot.bin file of the January Nougat bootloader MD5 with the sboot.bin file of the Marshmellow bootloader to create a sort of customised BL MD5, then flash that?
Click to expand...
Click to collapse
I suggest pulling the sboot.bin out of the marshmallow md5 and unpacking the BL md5 from the Nougat firmware and swapping the sboot.bin then repacking everything back into a BL tar.
ashyx said:
I suggest pulling the sboot.bin out of the marshmallow md5 and unpacking the BL md5 from the Nougat firmware and swapping the sboot.bin then repacking everything back into a BL tar.
Click to expand...
Click to collapse
Very well. I'll look into learning how to do that. Hopefully it's not too complicated. Apparently, it's either this process, or learning how to update with Flashfire if I wish to get updates and still be able to root. I can't help but feel like I'm playing with fire, though. Odds are, there will eventually to be an update that won't work with the MM bootloader at all. I can't imagine this will still work by the time Oreo is released.
ashyx said:
I suggest pulling the sboot.bin out of the marshmallow md5 and unpacking the BL md5 from the Nougat firmware and swapping the sboot.bin then repacking everything back into a BL tar.
Click to expand...
Click to collapse
Hi ashyx... can you teach me how to do unpack and repack also what app. Can I use for all of those?
kobejor said:
Hi ashyx... can you teach me how to do unpack and repack also what app. Can I use for all of those?
Click to expand...
Click to collapse
It's OK I'll repack it and post it later for you.
---------- Post added at 04:17 PM ---------- Previous post was at 04:11 PM ----------
Charles Miller said:
Very well. I'll look into learning how to do that. Hopefully it's not too complicated. Apparently, it's either this process, or learning how to update with Flashfire if I wish to get updates and still be able to root. I can't help but feel like I'm playing with fire, though. Odds are, there will eventually to be an update that won't work with the MM bootloader at all. I can't imagine this will still work by the time Oreo is released.
Click to expand...
Click to collapse
I think you're probably right, but as long people don't update the bootloader then downgrade is always possible.
Happy willy nilly flashers need to be aware that they don't need to jump on every update available, especially unknown security updates which inevitably can turn out to be nothing more than ways to lock a device down even more.
ashyx said:
It's OK I'll repack it and post it later for you.
---------- Post added at 04:17 PM ---------- Previous post was at 04:11 PM ----------
I think you're probably right, but as long people don't update the bootloader then downgrade is always possible.
Happy willy nilly flashers need to be aware that they don't need to jump on every update available, especially unknown security updates which inevitably can turn out to be nothing more than ways to lock a device down even more.
Click to expand...
Click to collapse
Thanks bro...
kobejor said:
Thanks bro...
Click to expand...
Click to collapse
Here you go, this is a mix of the Marshmallow A520FXXU2AQF7 sboot and the rest from the Nougat A520FXXU2BQK1 BL file.
https://androidfilehost.com/?fid=962187416754456246
.
Related
so i have been trying to flash aboot.mbm from recovery,
i created my update zip and it seems to pass, but does not update the bootloader.
i tried everything i could think of (assert, package_extract, dd, write_raw_image) none of them fail in recovery but the actual bootloader doesn't update.
so now i'm wondering if that's even possible or it absolutely has to be done with odin.
any info would help.
I am fairly certain you can only flash bootloader using Odin.
I don't remember seeing any update.zip file to flash them on this device.
Odin dude
Sent from my SM-G900T using XDA Free mobile app
yes i realize odin will flash it, i was just wondering if it was possible at all to do it from recovery since i have not found any zips to do it.
gillesguinet said:
yes i realize odin will flash it, i was just wondering if it was possible at all to do it from recovery since i have not found any zips to do it.
Click to expand...
Click to collapse
You cannot flash a bootloader from recovery. Gotta use Odin, or take the OTA.
The Sickness said:
You cannot flash a bootloader from recovery. Gotta use Odin, or take the OTA.
Click to expand...
Click to collapse
I pulled the stock OTA i received and was looking at the updater-script:
assert(package_extract_file("aboot.mbn", "/dev/block/platform/msm_sdcc.1/by-name/aboot"));
tried that as well and got the same result with twrp and philz, says passed but doesn't actually flash. is it a matter of signing the update.zip or is it the recovery that has access to the protected partition?
also this is just a learning experiment for me, don't want to be wasting any of the devs valuable time, but i do appreciate all the help.
edit: i do not use my G900T as a daily driver and do not mind it being a guinea pig for any experiment anyone would like to try, you can just let me know and ill be happy to help.
gillesguinet said:
so i have been trying to flash aboot.mbm from recovery,
i created my update zip and it seems to pass, but does not update the bootloader.
i tried everything i could think of (assert, package_extract, dd, write_raw_image) none of them fail in recovery but the actual bootloader doesn't update.
so now i'm wondering if that's even possible or it absolutely has to be done with odin.
any info would help.
Click to expand...
Click to collapse
You do know there's more than just aboot for the bootloader?
ShinySide said:
You do know there's more than just aboot for the bootloader?
Click to expand...
Click to collapse
yes i have added all the partitions, i took them from the TAR (aboot.mbm rpm.mbn sbl1.mbn sdi.mbn and tz.mbn).
i got all the commands from the stock OTA and still got that it flashed successfully, but it really doesn't allow me to write them that way.
i managed to get the OF6 sprint full rom file through kies.
this is only to be flashed using odin in the ap slot.
you will probably lose root and your custom recovery.
you may be able to root it and restore the data . That up to you to try.
This is the Sprint version Only!
here is the link: if someone wants to provide a mirror that would be appreciated.
Disabling 'Reactivation Lock' from 'Security' in the settings allowed me to root and add a custom recovery (TWRP).
your on your own from here!
https://onedrive.live.com/redir?resid=CD08CE789EB6B040!1155&authkey=!AIOZNh5nLeYDbcs&ithint=file,md5
here is another link thats a zipped MD5.tar file. this must be unzipped before putting the file into odin ap slot . (thanks to itskapil for the link)
http://www.theandroidsoul.com/download/download-sprint-galaxy-s5-android-5-0-2-update-odin-tar-file/
It's always great to have a TAR file on PC. Thanks!
But btw, this is Android 5.0 update, right? Have read on android blogs that OF6 has been 5.1 update for T-Mobile Galaxy S6 sets. So..
Okay, it's 5.0.2. Brings Reactivation lock.
itskapil said:
It's always great to have a TAR file on PC. Thanks!
But btw, this is Android 5.0 update, right? Have read on android blogs that OF6 has been 5.1 update for T-Mobile Galaxy S6 sets. So..
Okay, it's 5.0.2. Brings Reactivation lock.
Click to expand...
Click to collapse
Yes it's still 5.0
Sprint GS5 Moars 6.2
Any special features or affects on this update? Thanks for taking the time doing this for us
Sent from my SM-G900P using XDA Free mobile app
Son Rise said:
Any special features or affects on this update? Thanks for taking the time doing this for us
Sent from my SM-G900P using XDA Free mobile app
Click to expand...
Click to collapse
this
http://support.sprint.com/support/a...pdateTheSoftwareVersionOnYourSamsungGalaxy#!/
First is this a necessary update? Second does one have to update to OD3 first before doing the update. I'm still on OA6
Cmicasa the Great XvX said:
First is this a necessary update? Second does one have to update to OD3 first before doing the update. I'm still on OA6
Click to expand...
Click to collapse
no you dont have to update and no it isnt necessary. but if you are on stock OA6 I would take to guess that this rom is 5 months newer with improvements in alot of areas. they claim its for factory reset protection (so someone cant steal your phone and just factory reset it and it theirs now) and for reactivation protection (same thing so noone can reactivate the phone and make it theirs)
if i was on straight stock i would update. if i was on a stock rooted i would either try and root it or wait for someone to root the tar file and make it flashable through recovery.
thats my take on it.
cool... thanks. I like the security features, but at the same time I may wait till the new Moar comes out to do the work.
Is there a new radio and modem version with this update?
BrickedHouse said:
Is there a new radio and modem version with this update?
Click to expand...
Click to collapse
yes its the full rom, modem, and firmware
Robalboa said:
yes its the full rom, modem, and firmware
Click to expand...
Click to collapse
Thank you for this and by chance has anyone seen a firmware/modem update only for OF6 yet?
Edit: Found! Thanks tdunham - https://www.androidfilehost.com/?w=files&flid=21717
I was just gonna show you that. Lol
Sprint GS5 Moars 6.2
Has anyone successfully loaded a custom recovery and possibly one of the available OA6 ROMs after updating to this full tar?
I know there are separate modem and firmware files, but I was just curious if anyone has tried to go there from full stock.
DurhamHusker said:
Has anyone successfully loaded a custom recovery and possibly one of the available OA6 ROMs after updating to this full tar?
I know there are separate modem and firmware files, but I was just curious if anyone has tried to go there from full stock.
Click to expand...
Click to collapse
Yes. In fact, I did a full rom install, with nand erase all (after a bad flash), and I still went back to OA6 and OD3 stock deodexed roms.
Flashing TWRP from Odin works fine after flashing OF6 or OD3. I also used the CF one click root method, and that also worked for me.
Everything I did was in Odin 3.10.6.
Chainfires auto root makes odin complains about the recovery and shows 'fuse>3', which (I assume) means I've already burnt thru three of the 400+ fuses in the phone (kernel, recovery and probably rooting). I've tried odin 3.10.6 and the version that comes with chainfires auto root. Towelroot v3 says my phone isn't supported, even when using the command mod options.
I'll boot back into Windowz and try this a few more times. I don't see/know how joshdv rooted his phone...
edit: let's add insult to injury. I can't downgrade the firmware/OS to OA6, says it fails OS version.
joshdv said:
Yes. In fact, I did a full rom install, with nand erase all (after a bad flash), and I still went back to OA6 and OD3 stock deodexed roms.
Flashing TWRP from Odin works fine after flashing OF6 or OD3. I also used the CF one click root method, and that also worked for me.
Everything I did was in Odin 3.10.6.
Click to expand...
Click to collapse
@joshdv
Maybe it would help if you posted the link to the autoroot tar and any special steps you took to get it working.
Buddlespit said:
Chainfires auto root makes odin complains about the recovery and shows 'fuse>3', which (I assume) means I've already burnt thru three of the 400+ fuses in the phone (kernel, recovery and probably rooting). I've tried odin 3.10.6 and the version that comes with chainfires auto root. Towelroot v3 says my phone isn't supported, even when using the command mod options.
I'll boot back into Windowz and try this a few more times. I don't see/know how joshdv rooted his phone...
edit: let's add insult to injury. I can't downgrade the firmware/OS to OA6, says it fails OS version.
Click to expand...
Click to collapse
Yes, you're stuck on the newer firmware now.
tdunham said:
Yes, you're stuck on the newer firmware now.
Click to expand...
Click to collapse
Ya, before I flashed this, I knew I was probably stuck with OF6 and that there currently wasn't a reliable method to get root. Now, it's a waiting game to see if someone comes up with a method/hack to root this. GooooOOOOO CHAINFIRE!!!
Buddlespit said:
Ya, before I flashed this, I knew I was probably stuck with OF6 and that there currently wasn't a reliable method to get root. Now, it's a waiting game to see if someone comes up with a method/hack to root this. GooooOOOOO CHAINFIRE!!!
Click to expand...
Click to collapse
Depends how long you're willing to wait and if you want to keep the warranty bit untripped.
If it doesn't matter, you can still flash custom recovery in odin and any one of the pre-rooted custom or stock roms that will run on the lollipop bootloader.
I got root by just installing custom recovery and flashing super su. zip
Sent from my SM-G900P using Tapatalk
lascoul said:
I got root by just installing custom recovery and flashing super su. zip
Sent from my SM-G900P using Tapatalk
Click to expand...
Click to collapse
Link for Super user zip???
Hi guys, this is the a full Odin tar files for offical Nougat. Person outside the US can Flash and use it.
Unzip this package and get five file, flash it by Odin.
PS: It is better to flash the pit files. Don't worry, your Network unlocked status will remain same after updates.
mega: https://mega.nz/#!ZQg0FCoY
By the way, Nougat on S7Active is too slow，I found S7's package in waiting it LoL....
The decription key is: !WHLOkv-PVKMzWhe4ARbXonkOIa_mh_phjU9mYSHmHL8
error
smxwang said:
Hi guys, this is the a full Odin tar files for offical Nougat. Person outside the US can Flash and use it.
Unzip this package and get five file, flash it by Odin.
PS: It is better to flash the pit files. Don't worry, your Network unlocked status will remain same after updates.
mega: https://mega.nz/#!5Z5xwS4Z!WHLOkv-PV..._phjU9mYSHmHL8
By the way, Nougat on S7Active is too slow，I found S7's package in waiting it LoL....
Click to expand...
Click to collapse
Says provided decryption key is invalid.
sashaohio said:
Says provided decryption key is invalid.
Click to expand...
Click to collapse
Please try again....
Will tgis work to update the g930a from the qa4 nougat ota from earlier this year? Or would i have to downgrade to marshmallow first?
logoster said:
Will tgis work to update the g930a from the qa4 nougat ota from earlier this year? Or would i have to downgrade to marshmallow first?
Click to expand...
Click to collapse
backup and you can try. I don't have s7 and just get this package. In fact odin can flash as it can.
logoster said:
Will tgis work to update the g930a from the qa4 nougat ota from earlier this year? Or would i have to downgrade to marshmallow first?
Click to expand...
Click to collapse
It's a full firmware package so yes. You won't keep any of your data though.
Thanks for uploading this @smxwang
It worked for me to upgrade my rooted MM to rooted Nougat, and I used Flashfire to do a backup and restore of data and internal SD and haven't had any issues except that I can't download themes.
I have tried several times to download. I have copied and pasted key and still says I need a key. Can you remove the lock or can someone mirror?
will this allow future OTA update when ATT release them?
it says 'model dismatch fail'
why?
corrado85 said:
it says 'model dismatch fail'
why?
Click to expand...
Click to collapse
Do you have the right files for your model G930A or G935A. Normally that's the issue. Also make sure your using the official Odin when flashing factory firmware.
yes, i have the right files for my G930A, It must be because I'm using OdinPrinceComsy version
corrado85 said:
yes, i have the right files for my G930A, It must be because I'm using OdinPrinceComsy version
Click to expand...
Click to collapse
That would be the problem. Always use official Odin for stock firmware. Only us princecomsy Odin when flashing eng kernel.
it worked. thank you!
under options which should i select if I want full factory wipe (Fresh install)? or does it do automatically
thanks for your help
corrado85 said:
it says 'model dismatch fail'
why?
Click to expand...
Click to collapse
Which Odin are you using? If you use the Prince Comsy Odin you will get that. I accidentally used that version and got that message.
corrado85 said:
it worked. thank you!
under options which should i select if I want full factory wipe (Fresh install)? or does it do automatically
thanks for your help
Click to expand...
Click to collapse
Using Odin, it will wipe automatically. Just install all 4 files and it'll wipe you completely.
Dumb question here, We can flash each file independently. EX: If i wanted to flash just the ap file to replace the eng boot i could do that...
Downloaded file but when extracting I got error message files are corrupted. Any suggestions
Download worked!
DragonMax08 said:
Downloaded file but when extracting I got error message files are corrupted. Any suggestions
Click to expand...
Click to collapse
I just downloaded the file and used it to flash a G930A successully. You should probably just re-download the file.
Thanks for the feedback but I got it to work. Idk but it wasn't extracting on my Mac so I tried on Windows and it worked. Am actually running it now on my phone and everything so far working as it should.
you mention the S7Active there,
does that mean you have the Nougat Odin files for that too ?
and where did you get these images from ? did you get them from their servers ? (somewhere like ? h t t p s://xdmd.sl.attcompute.com/agents/48838/1488/ ??)
Hey maybe someone can give me a hand. Trying to flash back to stock on my Note 8 using the TMobil Firmware found [here](https://forum.xda-developers.com/galaxy-note-8/how-to/collection-firmware-rom-file-galaxy-t3676943). I put AP into AP. BL into BL, CP in CP, and CSC into CSC. Theres no PIT file in there. Do I used HOME_CRC or do anything with USERDATA??? I tried flashing using simFAIL but it wasnt working at all. The error im getting is SW REV CHECK FAIL : [adl]Fused 2 > Binary 1
Drackeo112 said:
Hey maybe someone can give me a hand. Trying to flash back to stock on my Note 8 using the TMobil Firmware found [here](https://forum.xda-developers.com/galaxy-note-8/how-to/collection-firmware-rom-file-galaxy-t3676943). I put AP into AP. BL into BL, CP in CP, and CSC into CSC. Theres no PIT file in there. Do I used HOME_CRC or do anything with USERDATA??? I tried flashing using simFAIL but it wasnt working at all. The error im getting is SW REV CHECK FAIL : [adl]Fused 2 > Binary 1
Click to expand...
Click to collapse
Start over from beginning use samfail step by step
kirschdog1 said:
Start over from beginning use samfail step by step
Click to expand...
Click to collapse
I did several times, and each time the same thing. My phone never rebooted after the first step. Im trying to flash back to tmobile but im getting " FAIL! Model dismatch fail" errors can cant get anywhere
Drackeo112 said:
I did several times, and each time the same thing. My phone never rebooted after the first step. Im trying to flash back to tmobile but im getting " FAIL! Model dismatch fail" errors can cant get anywhere
Click to expand...
Click to collapse
Read through the samfail thread at least 20 people had that same issue and got past it using a different variation of those steps listed in op. Also, don't forget to use search feature in the samfail op to look for others who have device mismatch errors and how they got it up and running.
kirschdog1 said:
Read through the samfail thread at least 20 people had that same issue and got past it using a different variation of those steps listed in op. Also, don't forget to use search feature in the samfail op to look for others who have device mismatch errors and how they got it up and running.
Click to expand...
Click to collapse
See I think Im getting lost on what goes where in ODIN. The AP goes to AP, BL to BL, CP to CP and CRC to CRC. Correct? What do I do with the HOME_CRC and USERDATA_CCT? Anything?
And do I make the Files TAR or keep them as MD5? Becasue the ext are tar.md5
Drackeo112 said:
See I think Im getting lost on what goes where in ODIN. The AP goes to AP, BL to BL, CP to CP and CRC to CRC. Correct? What do I do with the HOME_CRC and USERDATA_CCT? Anything?
And do I make the Files TAR or keep them as MD5? Becasue the ext are tar.md5
Click to expand...
Click to collapse
Leave them alone and only use csc not home csc or user data cct leave those alone.
Also use regular odin not prince odin
Drackeo112 said:
See I think Im getting lost on what goes where in ODIN. The AP goes to AP, BL to BL, CP to CP and CRC to CRC. Correct? What do I do with the HOME_CRC and USERDATA_CCT? Anything?
And do I make the Files TAR or keep them as MD5? Becasue the ext are tar.md5
Click to expand...
Click to collapse
You can't flash those with .MD5 at the end. Delete those (.md5) first.
Just so you know. your issue is because you took the update and you are incrimented. You are currently trying to downgrade and you cant. You must install the incrimented firmware to get working again. This also means No root for you.
me2151 said:
Just so you know. your issue is because you took the update and you are incrimented. You are currently trying to downgrade and you cant. You must install the incrimented firmware to get working again. This also means No root for you.
Click to expand...
Click to collapse
What do you mean by "You must install the incremented firmware to get working again." What and where do we find said firmware and are instructions posted anywhere, i must have missed them...
DeviceManagent said:
What do you mean by "You must install the incremented firmware to get working again." What and where do we find said firmware and are instructions posted anywhere, i must have missed them...
Click to expand...
Click to collapse
look around. why would instructions need to be posted? I have not released v2 root. and wont be released yet. You will have to deal with stock.
me2151 said:
look around. why would instructions need to be posted? I have not released v2 root. and wont be released yet. You will have to deal with stock.
Click to expand...
Click to collapse
I was rooted with v1 and updated to BQJA because another method was found thanks to you, and i would just re-root. When i flashed the BQJA files, it PASSED but my Note had error under the progress line on the screen. I would like to flash it correctly with the correct files until v2 is available. Device is doing stupid stuff like most apps F/Cing when they first open and some other odd things. I did a factory reset and wiped the cache in recovery and tried reflashing the factory firmware, still saying error on display, it PASSED, but im putting all my apps back and waiting for it to happen again....
The previous uploaded odin link for BRA1 went down, and you need to be on BRA1 to use the new oreo system updates. So I ended up buying them myself. Enjoy.
G930AUCS4BRA1
How can i update my 930A to oreo? I'm using 930u rom on my device
tx.takenori said:
How can i update my 930A to oreo? I'm using 930u rom on my device
Click to expand...
Click to collapse
I did it this morning, I used ODIN to go back to BRA1 AT&T version and then put the newest update on an empty SD card and applied update for SD using the recovery menu.
Hi, quick question. Sorry if this has been asked before. I already searched the entire forum for an answer.
So if I am on security patch March 1, 2017 (BQC2) version, can I just go ahead and flash this or do I need to be on an specific version in order to install this? I just don't want to brick. Thanks in advance.
Click to expand...
Click to collapse
I think I found my answer on another thread. For future references:
Quote:
Originally Posted by nasik.ubaid
I have Samsung Galaxy S7 AT&T
SM-G930A
6.0.1
Baseband: G930AUCU2APG1
Build Number : MMB29M.G930AUCU2APG1
Can i use flash my cell phone with this update??? Please help me.
You can Odin to BRA1, it'll be much faster than OTA all the way to BRA1 (which is alot of updates for where you currently are.
Im having issues flashing this file because it doesn't come up with the .md5 format. And Odin stays stuck on "file analysis" when i take off the .rar extension. Any one have any other firmwares i really dont want to flash all the way back and go through several updates just to get it up to date. Thanks.
Don't just take remove the. Rar, actually unzip them with 7zip,was the only way I could make them work myself
RN_ReFlux said:
Don't just take remove the. Rar, actually unzip them with 7zip,was the only way I could make them work myself
Click to expand...
Click to collapse
can you please give me a more in depth explanation? i extracted them first then removed tar then i tried removing tar and then extracting them but nothing is working? odin is not processing
SamGuy2020 said:
can you please give me a more in depth explanation? i extracted them first then removed tar then i tried removing tar and then extracting them but nothing is working? odin is not processing
Click to expand...
Click to collapse
you do realize you need to let odin run for more than 10 minutes sometimes. its literally processing 500mb -4gb of data. stop interrupting odin because its not finishing on your time. its called patience.
all you should be doing is extracting the md5's from the zip using winrar or something similar. when in odin you need to be clicking on the bl ap cp and csc and putting the extracted files in their places and hitting start and literally letting it run until it is finished without clicking anything. it is not STUCK on file processing... it IS processing the files
aarongotgame said:
you do realize you need to let odin run for more than 10 minutes sometimes. its literally processing 500mb -4gb of data. stop interrupting odin because its not finishing on your time. its called patience.
all you should be doing is extracting the md5's from the zip using winrar or something similar. when in odin you need to be clicking on the bl ap cp and csc and putting the extracted files in their places and hitting start and literally letting it run until it is finished without clicking anything. it is not STUCK on file processing... it IS processing the files
Click to expand...
Click to collapse
Thanks, yeah i figured it out that I wasn't unpacking them correctly. On oreo now
SamGuy2020 said:
Thanks, yeah i figured it out that I wasn't unpacking them correctly. On oreo now
Click to expand...
Click to collapse
Hi, im not in the US, how do you have oreo? do you have the firnware? can you send me please, my email [email protected]