[Q] Accidentally flashed verizon galaxy s5 to SM-G900A when i went to the OA8 build. - Galaxy S 5 Q&A, Help & Troubleshooting

I have been fan and user of this website and its forums for several years now and up to this time have always been very diligent about searching for the answers to my questions in the forums. I have always been impressed that i never had a question that had not been answered until today.. I found nothing on XDA nor the rest of the internet so here is my quere.. I Accidentally flashed my verizon galaxy s5 to SM-G900A when i went to the OA8 build. The funny thing is that it appears to have worked for the most part. It started up pre-loaded with all the at&t bloatware installed and everything! My phone now says SAMSUNG SM-G900A under model name and number..It gives G900VVRU1BOA8 as the baseband version and KTU84P.G900AUCU2AOA1 as the build number..It appears that I am on Lollipop, however, it says I have android version 4.4.4. All of that considered, my question is regarding taking the OC4 update through Flashfire. It clearly states that using it on any other variant could result in a hardbrick..Do you think it will hard brick my phone?

First of all what is flash fire? Second I would not take that chance.... But have you thought about restoring your phone through odin?

On a developers standpoint you'll have to do more than that hardbricking your phone. Or should I say the only ways to hardbrick your s5 is
1. Destroy some of its hardware
2. Rewrite/delete some of it's irreplaceable data.
And flashing different ROMs doesn't result to 1 of the 2 and you'll either just get a softbrick, buggy ROM or a working device.
There are only 3 versions of s5 in general
1. The snapdragon version
2. Exynos version
3. Sprint version
And subversions which are
1. 16GB model
2. 32GB model
cross flashing the exynos version to snapdragon and the other way around would surely lead to soft brick as the processor drivers, GPU drivers etc differ.
cross flashing between 16gb and 32gb variant would probably end up softbrick or buggy device since partition tables are different.
cross flashing sprint version and regular version would probably get your the same working device and probably get a FM radio enabled.
cross flashing different model numbers would end up having a working device since there's literally no difference in the hardware. As long as you crossflash the bootloader, modem etc then it should be fine. But if you're cross flashing the system partition only then that's something different.
---------- Post added at 12:02 PM ---------- Previous post was at 11:59 AM ----------
Almost forgot! THere's also the dual sim variants

I don't know if @Riyal gave you the info you need... but if not you better get odin and flash back to a Verizon rom

I didn't answer his question though... Just explaining in detail what happened/will happen when he/she cross flashed firmwares. I don't know what flashfire is so I couldn't answer his question. But as you said... flashing OC4 update thru odin is the surefire way to go.

@austocracy you read that get a copy of odin 3.09 and a copy of your s5 verizon firmware sammobile and have at it. The cure is within reach.... make sure you find some instructions first

Flash fire is basically mobile Odin and something else I can't remember I'll find the link for you I heard there's basically no need for Odin anymore because of it
Edit: http://forum.xda-developers.com/showthread.php?t=3075433

If only govt were half as expedient as this community...
I am severely impressed.. I posted at 3:42 in the am..I wasnt even thinking about checking for a response until lunchtime..I am grateful for the responses and will now take up the advise with a confidence that i did not have only a few short hours ago..Ill let you know how it goes..Thanks again.

Veid71 said:
Flash fire is basically mobile Odin and something else I can't remember I'll find the link for you I heard there's basically no need for Odin anymore because of it
Edit: http://forum.xda-developers.com/showthread.php?t=3075433
Click to expand...
Click to collapse
Naw I'm old school I'll do it by pc Thanks for the link [emoji3]
---------- Post added at 09:58 AM ---------- Previous post was at 09:50 AM ----------
@austocracy Dude do not attempt to use flashfire I know it's from chainfire and he helped me root my s5 but flashfire is in beta and crashes and even crashes when it's closed, just get odin 3.09 and YOUR firmware version for YOUR phone with some instructions and have at that

SnuggP said:
Naw I'm old school I'll do it by pc Thanks for the link [emoji3]
---------- Post added at 09:58 AM ---------- Previous post was at 09:50 AM ----------
@austocracy Dude do not attempt to use flashfire I know it's from chainfire and he helped me root my s5 but flashfire is in beta and crashes and even crashes when it's closed, just get odin 3.09 and YOUR firmware version for YOUR phone with some instructions and have at that
Click to expand...
Click to collapse
I don't blame you I don't use it either I do it with Odin but I don't know how to use flash fire xD

Related

SM-N910T partial downgrade from 5.1.1 to 4.4.4

I was able to downgrade from 5.1.1 to 4.4.4 on a SM-N910T. Kinda...
the phone had 5.1.1 N910TUVU2DOK2 and i downgraded to 4.4.4 N910T2TMB2AOG1.
N910T2TMB2AOG1 is 4.4.4 for a SM-N910T2 and I would like to get to 4.4.4 N910TUVU1ANIH for a SM-N910T.
Since I was able to downgrade to 4.4.4 I hope someone can figure out how to get over to 4.4.4 N910TUVU1ANIH.
Has anyone had any success in downgrading the SM-N910T to 4.4.4?
As far as EVERYONE with a N910T knows there is NO possible way at all to downgrade from DOK2. If you have achieved this bud you are the only single person that anyone knows who has...PLEASE sir provide screenshots and a full list of the steps you took... if you successfully managed to downgrade to T2 firmware we might can find a way to help you get over to a different firmware.
---------- Post added at 01:16 AM ---------- Previous post was at 01:14 AM ----------
But what do you mean kinda???? If all your partitions are on 4.4.4 buddy you are fully downgraded....how did you come to flashing T2 firmware...what's the story?
---------- Post added at 01:18 AM ---------- Previous post was at 01:16 AM ----------
I'm only so excited because I have been looking since I bought my phone for a method like your describing...you will be famous my friend if you have found this and can prove to others it's true....I don't mean that disrespectful....it's just thought to be impossible by even devs
---------- Post added at 01:35 AM ---------- Previous post was at 01:18 AM ----------
BTW bro you should prolly post this on N910T forums also....probably get way more attention there
I successfully downgraded 3 SM-N910T phones today, but it will be Tuesday before I can post screenshots, get more details and do more experiments etc.
For now this is what I did.
1. I used Odin 3.11.1 to flash the OG1 rom
2. I used a N910T2TMB2AOG1 rom I captured from Kies a while back that has the BL,AP,CP and CSC files in it
3. I selected "nand erase all" and "phone bootloader update" in options
4. After a sucessful flash, I did a hard reset in recovery
5. I used the app "Phone INFO ★Samsung★" to verify the phone is on the 4.4.4 OG1 bootloader
Tuesday I will try downloading the OG1 rom from sammobile for the SM-N910T2 and flashing it without all the extra setting to see if I get the same results.
Then I will post on the 910T forums to see if I actually have a breakthrough and if someone can use this info to get to 4.4.4 ANIH.
I have been able to get from 5.0.1 to 4.4.4 ANIH with no problems but like everyone else 5.1.1 to 4.4.4 seems to be impossible.
So to start with you were on DOK2 right? And now your phone is on T2 4.4.4 firmware? I have a N910T on DOK2. Well 6.0.1 now but I can downgrade back and I can download the FW and try it...if you can send me a link to the FW that you downgraded to and a link to the firmware that you want to be on I will see if I can get some of my way more tech savvy friends to help me check out the files to see if we can figure out how to get you to where u wanna be...where you get your phone and how old is it...and when you can send screenshots take one of the back under the battery and of your stock recovery if your on stock...
Sorry it has taken so long to respond but here are the steps I took to get down to 4.4.4.
(Warning!!!! I am not responsible if you damage your phone following these instructions.)
>>>>Proceed at Your Own Risk<<<<
The SM-N910T was on Android Version 5.1.1 build number N910TUVU2DOK2.
I used the 4.4.4 firmware N910T2UVU2AOG1 for the SM-N910T2 downloaded from SamMobile.com.
I flashed the N910T2UVU2AOG1 firmware through Odin 3.11.
The Note 4 will boot loop after the downgrade so you will have to boot into recovery after the downgrade, then wipe cache and wipe data/factory reset.
Remember that this will only get you to 4.4.4 for the SM-N910T2. I would like to get to 4.4.4 for the SM-N910T if someone smarter than me knows how to do it.
Have you tried flashing the ANK firmware?
grbrri said:
Sorry it has taken so long to respond but here are the steps I took to get down to 4.4.4.
(Warning!!!! I am not responsible if you damage your phone following these instructions.)
>>>>Proceed at Your Own Risk<<<<
The SM-N910T was on Android Version 5.1.1 build number N910TUVU2DOK2.
I used the 4.4.4 firmware N910T2UVU2AOG1 for the SM-N910T2 downloaded from SamMobile.com.
I flashed the N910T2UVU2AOG1 firmware through Odin 3.11.
The Note 4 will boot loop after the downgrade so you will have to boot into recovery after the downgrade, then wipe cache and wipe data/factory reset.
Remember that this will only get you to 4.4.4 for the SM-N910T2. I would like to get to 4.4.4 for the SM-N910T if someone smarter than me knows how to do it.
Click to expand...
Click to collapse
Sammobile also shows 4.4.4 firmwares ANIH and ANJ7 for the N910T. Did those also fail downgrade attempts from 6.0.1?
Sent from my SM-N910T using Tapatalk
Yes they failed.
That's why I tried the 4.4.4 firmware for the SM-N910T2. It was the only firmware that would downgrade.
I have tried to downgrade to ANJ7, ANK4, and ANIH with no success. AOG1 is the only one I have been able to downgrade successfully.
A side note, I can upgrade back to DOK2 and then downgrade back to AOG1 with no problem.
So it seems that the Note 4 bootloader is not exactly locked because it can be downgraded to 4.4.4 on at least one version of the firmware. What this leads me to believe is that these must be a database or whitelist in the bootloader code that allows for downgrade to 4.4.4 if the version is on the approved list. Or maybe it's a blacklist with ANJ7, ANK4 and ANIH on it that causes Odin to fail. I have not tried to decompile the bootloader to verify, so I am just speculating at this point.
grbrri said:
I have tried to downgrade to ANJ7, ANK4, and ANIH with no success. AOG1 is the only one I have been able to downgrade successfully.
A side note, I can upgrade back to DOK2 and then downgrade back to AOG1 with no problem.
So it seems that the Note 4 bootloader is not exactly locked because it can be downgraded to 4.4.4 on at least one version of the firmware. What this leads me to believe is that these must be a database or whitelist in the bootloader code that allows for downgrade to 4.4.4 if the version is on the approved list. Or maybe it's a blacklist with ANJ7, ANK4 and ANIH on it that causes Odin to fail. I have not tried to decompile the bootloader to verify, so I am just speculating at this point.
Click to expand...
Click to collapse
How does the firmware run...any different? Everything works?
noob4598 said:
How does the firmware run...any different? Everything works?
Click to expand...
Click to collapse
Not sure, I haven't really tested it since I am trying to get to ANIH. I know that it boots up fine and I can access the settings and install software. I haven't seen any force closes but I haven't tested it thoroughly.
Why do you want ANIH specificly....? There is a reason I'm asking...your answer will help me try to figure out a way for you to get there..
grbrri said:
Not sure, I haven't really tested it since I am trying to get to ANIH. I know that it boots up fine and I can access the settings and install software. I haven't seen any force closes but I haven't tested it thoroughly.
Click to expand...
Click to collapse
Also is it possible for you to upload the firmware to mega or Google drive...I can't find it anywhere...
It's on sammobile. Use the model number SM-N910T2.
Yea I saw it I was just trying to avoid 15kb a sec dl speed
noob4598 said:
Why do you want ANIH specificly....? There is a reason I'm asking...your answer will help me try to figure out a way for you to get there..
Click to expand...
Click to collapse
I want to use a rom that is based on the ANIH build.
Do you know how to edit firmware tars
---------- Post added at 09:26 PM ---------- Previous post was at 09:08 PM ----------
That's why I asked why you wanted to be on ANIH...you can possibly extract the tar and remove the BL...then you are left with a ANIH phone that has a different BL of the same build...but have you tried the rom you want on the T2 FW...? It might run perfect....it's like installing a N910F rom on N910T...all you really need is the BL and Modem that is compatible with our phone... T and T2 are the same as far as hardware from what I can find....
grbrri said:
Sorry it has taken so long to respond but here are the steps I took to get down to 4.4.4.
(Warning!!!! I am not responsible if you damage your phone following these instructions.)
>>>>Proceed at Your Own Risk<<<<
The SM-N910T was on Android Version 5.1.1 build number N910TUVU2DOK2.
I used the 4.4.4 firmware N910T2UVU2AOG1 for the SM-N910T2 downloaded from SamMobile.com.
I flashed the N910T2UVU2AOG1 firmware through Odin 3.11.
The Note 4 will boot loop after the downgrade so you will have to boot into recovery after the downgrade, then wipe cache and wipe data/factory reset.
Remember that this will only get you to 4.4.4 for the SM-N910T2. I would like to get to 4.4.4 for the SM-N910T if someone smarter than me knows how to do it.
Click to expand...
Click to collapse
After downgrading to the 910T2 4.4.4 stock, were you able to install recovery and any of the 910T 4.4.4 custom ROMs? ie FireKat? Were you still unable to Odin any of the T-Mobile 4.4.4 from your Rent-A-Center T2 4.4.4?
Sent from my SM-N910T using Tapatalk
vprasad1 said:
After downgrading to the 910T2 4.4.4 stock, were you able to install recovery and any of the 910T 4.4.4 custom ROMs? ie FireKat? Were you still unable to Odin any of the T-Mobile 4.4.4 from your Rent-A-Center T2 4.4.4?
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
same question here....also what happens when you odin flash only BL and CP of ANK4 or ANIH over T2 4.4.4 rom ?
---------- Post added at 05:14 AM ---------- Previous post was at 05:12 AM ----------
grbrri said:
I want to use a rom that is based on the ANIH build.
Click to expand...
Click to collapse
did you try ODIN re partition with PIT File for 910T , along with ANIH stock rom 4.4.4 ?
I've done the said method of downgrading to 444 N910T2 OG1 firmware from 601.
This is the closest you can get to NIH and all the other original 444 firmwares for N910T. You won't be able to flash stock n910t 444 rom from this one, though.
The positive side of it is that this OG1 firmware for N910T2 is fully functional with no TMO bloats. So it's almost like a dream 444 stock firmware.
Again: fully functional 444 daily driver with good battery life and no tmo bloats. You can flash Root, it works as well. If you love 444 just flash this over your 511 or 601, erase data and cache. Start fresh. Then, enjoy the benefits.
Loving my Note 4 even more now.

[HELP] G900V-CID11 Toshiba-locked bootloader, looking for 6.0.1 ROM working

Hi all, I can't really figure out from all the releases posted here how to find a rom which can be installed on my phone, while I'm waiting for an unclock for CID11.
I've a 900V CD11 locked with BT1 rom sim-locked and SD-not working and now I can't use my phone at all. I'm in stuck at all.
I've rooted it already, waiting for a proper rom.
I tried some roms but I always failed, the last one "G900V_PF4_Stock_Deodexed_Debloated_ROM" which is made for locked phone, was failed to upload from chainfire.flash_0.50 in the middle of flashing.. it reboots phone and it become bricked
You may kindly indicate me the steps I've to follow to install the right rom, if I've to use safestrap or chainfire.flash_0.50.apk, and if I've to flash with Odin the bootloader and with which file.
Thank you so much, please add any consideration that you can consider important!
with the G900V, you dont want to try to unlock the bootloader or itll hard brick. You have to use safestrap
---------- Post added at 12:56 PM ---------- Previous post was at 12:54 PM ----------
if you go to sammobile.com, you can get the stock image to flash in odin to unbrick if its just softbricked. You may want to check the G900V forums to make sure that you dont flash a version that doesnt have root available for it, as vzw has locked the device down like fort knox. Im at work currently, but can look further into this for you after 6pm cst
I tried to unlock and it didn't hard brick.
I can use safestrap but to upload what? I can't unlock it (it's CID11), and I can't find a ROM valid for this phone! (the one I used (suggested on the root phone procedure) is SIM-locked and with SD not working).
I hope someone can suggest me a rom which will work on my phone. Thank you
also, i dont know what you mean by "toshiba-locked bootloader"
Wow you're in the wrong area... Go here and scroll down to prepare your phone for root
http://forum.xda-developers.com/showthread.php?p=64744405
Actually read everything and make sure you understand it before doing it because if you tried to unlock your bootloader when you have the wrong emmc (11 instead of 15) you either didn't read or or didn't understand the thread good luck and you should stick with the vzw specific threads with the 11 good luck and happy flashing
---------- Post added at 12:39 PM ---------- Previous post was at 12:18 PM ----------
youdoofus said:
also, i dont know what you mean by "toshiba-locked bootloader"
Click to expand...
Click to collapse
The Verizon variant has two chips the Toshiba chip and the QUALCOMM chip the QUALCOMM chip can be unlocked the Toshiba can't
youdoofus said:
with the G900V, you dont want to try to unlock the bootloader or itll hard brick. You have to use safestrap
---------- Post added at 12:56 PM ---------- Previous post was at 12:54 PM ----------
if you go to sammobile.com, you can get the stock image to flash in odin to unbrick if its just softbricked. You may want to check the G900V forums to make sure that you dont flash a version that doesnt have root available for it, as vzw has locked the device down like fort knox. Im at work currently, but can look further into this for you after 6pm cst
Click to expand...
Click to collapse
thank u for help! Are u addicted to that forum? I would really appreciate if u give me some help finding an uploadable version. I'm looking for a 6.0.1 with sim unlocked, root if possible and SD working. If there isn't exist one a LL could be good too, my phone is sim-locked now and isn't reading SD, so I can't use it.
Yes I rooted it, I can use safestrap and chainfire flash application (superSU installed). Thank you so much!
I've found the ROM, now I'm on 6.0.1 but without SD usage, looking for a fix..
Does it happen anyone that after BP1 flashing the SD card is not more available? Have you ever lost SD card with wrong ROM?
I don't know if it is electric problem or software
When you tried to unlock your bootloader it wiped it so you will need to reformat it for it to work again... If you would have read the thread you would know this?
So, does it not boot at all now?
Tes it works good, the only problem is that it can't read SD.
Yes I formatted it FAT32 already and other pone and PC works with it without problems.
When it was ROM G900FXXU1BOC7 it worked, after update to PB1 it didn't, is that possible that ROM prevent see SD?
Thank you
i believe @bad bone is correct, it sounds like the problem is the bootloader. You may have to flash a pit file in Odin to correct this. im basically bowing out on this because where your problem is may also lie a den of dragons. Im just hoping that a bump in this thread will get the attention of someone more familiar with this variant of the device. Also, locked bootloaders are the bane of Samsung using existence
Barabba11 said:
I've found the ROM, now I'm on 6.0.1 but without SD usage, looking for a fix..
Click to expand...
Click to collapse
I have the same device as you, I am on stock Android 5.0 rooted (CID 11), what ROM are you using for 6.0.1? Is your device still rooted? Can you point me to a helpful tutorial?
Rooted s5 MOAR rom
I have a Verizon s5, rooted it with a method on here by jrkruse I believe, flashed the stock debloated rom, have safestrap and su and busy box installed, then flashed MOAR rom for 5.0, I have CID 11, running pb1.

Update rooted S5 to latest?

I've got a rooted S5: SM-G900F running 4.4.2
I managed to root without triggering KNOX.
I'd now like to update the phone to the latest available version - on the Virgin Mobile page that is Android 5.0 (https://community.virginmobile.com.au/t5/Support-Articles/Mobile-Software-Updates/ta-p/39921)
What's the easiest way to update it? Should I unroot, perform the official update, and then root, or is there an easier method? It's been a couple of years and I can't remember how I avoided KNOX before, and I'd like to do so again if possible.
Cheers,
Tony
from what ive seen, this is the international version. uncharted territory for me, but its likely more similar than different. Might want to check its specific forum as some idiosyncrasies do exist for the international one. like any galaxy device, you can get the firmware from sammobile.com and flash it in odin, but id just be careful as some of the firmwares make the phone unrootable and un-down gradable
Yes it's the international version.
In Mobile Odin Pro, it warns me that use of this software will trigger KNOX? Is that correct or is it just being extra cautious? My understanding was that I could flash official roms,, but KNOX would be triggered by flashing a Recovery??
Also - is there a good place to identify which ROMS are unrootable? - I assume I flash via MOP and then re-root?
Cheers
I'd stay away from mobile Odin man. Its been the source of many bricks in newer devices
---------- Post added at 04:36 AM ---------- Previous post was at 04:35 AM ----------
Also, you can flash whatever ROM you want as long as you have the right radios

Samsung S5 (SM-G900F) stopped loading

Hi,
My gf's phone stopped loading yesterday (stuck at the SAMSUNG logo), so I've tried to factory-reset it via recovery menu. Unfortunately, this didn't help, so I've decided that I need to re-flash the system. After some search I found https://www.kingoapp.com/root-tutorials/how-to-flash-samsung-stock-rom-via-odin.htm and tried to follow it. After checking the sticker behind the battery, I've learned that the model is SM-G900F. Unfortunately I wasn't sure what ROM was installed on the phone before and couldn't find any Ukrainian ROM, which is where the phone was bought originally. In the end, I decided to try installing latest ROM for Germany O2, since this is the operator that my gf uses now.
Unfortunately, Odin refused installing that image with an error "FAIL! (Auth)". After some further searching, I've noticed that when the phone is in download mode, it shows model name SM-G900V. I have no idea why and the ROM that was there before was clearly non-Verizon. Still, having no other option, I've downloaded Verizon ROM and it installed successfully. Luckily the phone has booted, but as expected, it wouldn't connect to any other network than Verizon, which is kinda useless to me given that we live in Germany and use O2. Now I wonder if it's possible to somehow root the phone, install custom recovery and flash that German O2 ROM?
The device is running Android 6.0.1 and kernel 3.4.0. How do I root it? How do I install custom recovery? Which one would you recommend?
Thanks,
Sergiy
In order to root it and install custom recovery you need to follow this guide
https://forum.xda-developers.com/tmobile-galaxy-s5/development/root-method-2018-updated-stock-firmware-t3781426
---------- Post added at 10:24 PM ---------- Previous post was at 10:21 PM ----------
I would recommend twrp and magisk
---------- Post added at 10:28 PM ---------- Previous post was at 10:24 PM ----------
Also you need to get the correct twrp for your phone from
https://twrp.me/samsung/samsunggalaxys5qualcomm.html
---------- Post added at 10:37 PM ---------- Previous post was at 10:28 PM ----------
After rooting and custom recovery installation you need to decide what ROM you want on this phone ,you can install any ROM that supports sm g900f or g900v or klte (that's your device nickname)
I am on aex and it works good for me so you can try it https://forum.xda-developers.com/galaxy-s5/unified-development/rom-aospextended-rom-v5-4-t3779910
---------- Post added at 10:47 PM ---------- Previous post was at 10:37 PM ----------
Follow the installation instructions from the Aex link and you should be good to go
If you need google apps and play store install gapps zip the link for that is also in the aex post hope it all works out for you ,if you need any help just ask
rryk said:
Now I wonder if it's possible to somehow root the phone, install custom recovery and flash that German O2 ROM?
The device is running Android 6.0.1 and kernel 3.4.0. How do I root it? How do I install custom recovery? Which one would you recommend?
Thanks,
Sergiy
Click to expand...
Click to collapse
Seems, you can read russian.
You may like to follow this my guide to flash SM-G900V with an international 6.0.1 ROM.
I think, you can even use VIA (O2) CSC.
P.S. Please, pay attention to:
1. The first boot after factory reset may take 12-15 min (but not more than 20), so be patient. This was the problem, I guess.
2. Read the QA section in my guide to find the answers to your questions about root and custom recovery. And feel free to ask questions (here or there).
bbsc said:
Seems, you can read russian.
You may like to follow this my guide to flash SM-G900V with an international 6.0.1 ROM.
I think, you can even use VIA (O2) CSC.
P.S. Please, pay attention to:
1. The first boot after factory reset may take 12-15 min (but not more than 20), so be patient. This was the problem, I guess.
2. Read the QA section in my guide to find the answers to your questions about root and custom recovery. And feel free to ask questions (here or there).
Click to expand...
Click to collapse
Thanks a lot. Indeed, I have probably not waited long enough for the first boot. The instructions you linked, worked! My gf is happy to have her phone back.
rryk said:
Thanks a lot. Indeed, I have probably not waited long enough for the first boot. The instructions you linked, worked! My gf is happy to have her phone back.
Click to expand...
Click to collapse
You're welcome.
Радий був допомогти.
And note for the next time: it's a good idea to try clearing cache and safe boot before performing a factory reset

Can't find XAA or ATT binary 7 firmware. Please help

I have an AT&T Galaxy G950u with my most recent firmware being g950usqs7dtb1. I flashed a combination file (g950usqu7ask1) to turn on OEM unlock so I could install Havoc (I know now, I didn't have to do all that,) but now I can't get Odin to flash any stock ROMs back to install TWRP. The main error I'm receiving in Odin is FAIL! (Auth).
I've tried all kinds of ROMs but I can't find my original ROM anywhere except some shady site that definitely isn't legit.
When I boot into Download/Odin mode the numbers next to RP SWREV are B7(2.1.1.1.1) k6 S7
The error on my phone is SW Rev Check fail: (ab)) Fused 7 > Binary 1
I realized I probably need a carrier free (XAA) or ATT firmware that is binary 7. The problem is it's so recent I can't find any binary 7 firmwares out there. I've searched Updato and couldn't find xaa firmware for binary 7
Working with patched/modded Odin 3B v3.14.1
If anyone can help I would be so grateful.
Edit: I've tried Frija and it says ATT not supported, and it says it can't find anything for XAA. I've also searched Updato thoroughly and can't find a binary 7 file.
Edit 2: I found a ROM.
uberdad said:
I have an AT&T Galaxy G950u with my most recent firmware being g950usqs7dtb1. I flashed a combination file (g950usqu7ask1) to turn on OEM unlock so I could install Havoc (I know now, I didn't have to do all that,) but now I can't get Odin to flash any stock ROMs back to install TWRP. The main error I'm receiving in Odin is FAIL! (Auth).
I've tried all kinds of ROMs but I can't find my original ROM anywhere except some shady site that definitely isn't legit.
When I boot into Download/Odin mode the numbers next to RP SWREV are B7(2.1.1.1.1) k6 S7
The error on my phone is SW Rev Check fail: (ab)) Fused 7 > Binary 1
I realized I probably need a carrier free (XAA) or ATT firmware that is binary 7. The problem is it's so recent I can't find any binary 7 firmwares out there. I've searched Updato and couldn't find xaa firmware for binary 7
Working with patched/modded Odin 3B v3.14.1
If anyone can help I would be so grateful.
Edit: I've tried Frija and it says ATT not supported, and it says it can't find anything for XAA. I've also searched Updato thoroughly and can't find a binary 7 file.
Edit 2: I found a ROM.
Click to expand...
Click to collapse
Well first off you can't flash any custom ROMs on this device it has a locked bootloader. Oem unlock doesn't matter. It's useless. Garbage. That's all for that. Flash any other carrier firmware and flash the oyn csc not home. It will repersonalize for att as the firmware are actually multi carrier. Att included.
TheMadScientist said:
Well first off you can't flash any custom ROMs on this device it has a locked bootloader. Oem unlock doesn't matter. It's useless. Garbage. That's all for that. Flash any other carrier firmware and flash the oyn csc not home. It will repersonalize for att as the firmware are actually multi carrier. Att included.
Click to expand...
Click to collapse
Thanks for the input. I'm trying to flash twrp as a custom recovery but it gets stuck on "waiting for device". I've updated all drivers and have no error in device manager
uberdad said:
Thanks for the input. I'm trying to flash twrp as a custom recovery but it gets stuck on "waiting for device". I've updated all drivers and have no error in device manager
Click to expand...
Click to collapse
You can't flash twrp. Locked bootloader
TheMadScientist said:
You can't flash twrp. Locked bootloader
Click to expand...
Click to collapse
(BUMP)
Hey there @TheMadScientist not following you! haha. Just came across this thread as im researching what elliwigy and jrkruse have done.
To @uberdad search for anything s8 SM-G950 by jrkruse and elliwigy here and you should have a solution if your device is still on 7. Wont be twrp but will be safestrap twrp. You can install a custom rom then.
noidodroid said:
(BUMP)
Hey there @TheMadScientist not following you! haha. Just came across this thread as im researching what elliwigy and jrkruse have done.
To @uberdad search for anything s8 SM-G950 by jrkruse and elliwigy here and you should have a solution if your device is still on 7. Wont be twrp but will be safestrap twrp. You can install a custom rom then.
Click to expand...
Click to collapse
There are no custom roms. You can only have root on a 7.0 stock system img. Please research more before beginning to pass on information. As well this thread is now old no need to dig up old stuff. I helped out with some of the stuff on this device I know what it can and cannot do. Here wanted to install a los based rom. which is a big no. Add I said to begin with
---------- Post added at 03:57 AM ---------- Previous post was at 03:50 AM ----------
Then he was trying to flash twrp. Which is a big no. Please don't go dragging up a bunch of old threads we have dealt with. This leads to confusing people
TheMadScientist said:
There are no custom roms. You can only have root on a 7.0 stock system img. Please research more before beginning to pass on information. As well this thread is now old no need to dig up old stuff. I helped out with some of the stuff on this device I know what it can and cannot do. Here wanted to install a los based rom. which is a big no. Add I said to begin with
---------- Post added at 03:57 AM ---------- Previous post was at 03:50 AM ----------
Then he was trying to flash twrp. Which is a big no. Please don't go dragging up a bunch of old threads we have dealt with. This leads to confusing people
Click to expand...
Click to collapse
Hi. Yes you are right I should have said Slightly Cooked Rom or Modified System Image. However preferred to put Custom Rom due to the fact the amount of new Customization Enthusiasts here on XDA to make it simpler. Also sure yes USER Root on XDA only obtained on 7.0 (at least public). Little off topic but our team has a *working* root along with our own SuperUser which means for repairs pretty much but if time was put into it could become possibly a semi to full user root. I have used Magisk SU older versions along with our root and had a semi working user root on past Galaxies.. Anyhow we don't really have time, especially myself, to work on an actual user root for every device i/we work on.
In the world of forums threads never really grow old they just go into a deep sleep eventually....Until someone wakes it up with the thirst for knowledge. It's how the internet works when it comes to these here BBS/Forums/Blogs etc. =]
What he asked could be something someone else might ask or attempt trying (he shouldnt have even got as far as he did unless on international variant which makes the Q odd.. haha eh? however i felt the need to straighten it up for anyone who might read and get confused. See what im saying..? along with the previous statement about data no become stale.
The more ya know the smarter you become. Information makes the world go around. .. IMO Always best to keep it flowing constantly added to.
2 cents
noidodroid said:
Hi. Yes you are right I should have said Slightly Cooked Rom or Modified System Image. However preferred to put Custom Rom due to the fact the amount of new Customization Enthusiasts here on XDA to make it simpler. Also sure yes USER Root on XDA only obtained on 7.0 (at least public). Little off topic but our team has a *working* root along with our own SuperUser which means for repairs pretty much but if time was put into it could become possibly a semi to full user root. I have used Magisk SU older versions along with our root and had a semi working user root on past Galaxies.. Anyhow we don't really have time, especially myself, to work on an actual user root for every device i/we work on.
In the world of forums threads never really grow old they just go into a deep sleep eventually....Until someone wakes it up with the thirst for knowledge. It's how the internet works when it comes to these here BBS/Forums/Blogs etc. =]
What he asked could be something someone else might ask or attempt trying (he shouldnt have even got as far as he did unless on international variant which makes the Q odd.. haha eh? however i felt the need to straighten it up for anyone who might read and get confused. See what im saying..? along with the previous statement about data no become stale.
The more ya know the smarter you become. Information makes the world go around. .. IMO Always best to keep it flowing constantly added to.
2 cents
Click to expand...
Click to collapse
All true. Well said

Categories

Resources