Unrooting G900A AT&T usa - Galaxy S 5 Q&A, Help & Troubleshooting

I rooted my phone two weeks ago with towelroot and disabled Knox with supersu.Note: my device status said official I'm still running stock firmware. Have to send my phone back for warranty problem so I unrooted with supersu and reset my phone. So now when I look at my device status it says custom (never flashed any roms or nothing) so I factory reset and notice unlock padlock and custom on my reboot startup screen. I also put phone in Odin mode the binary still said Samsung official but now the other say custom. And Knox says 0×0. I was told to use Odin so I installed odin3v3.09, drivers, stock firmware on the PC tried to flash it but got a Auth: Fail in the left lower box.
My replacement phone will be here today and will send the old back Monday to give me a couple more days to figure this out. What did I do wrong?
PLEASE HELP!

UPDATE
I just notice when I was using Odin I tried to flash G900AUCU1ANCE stock firmware. My phone says I'm running G900AUCU2AND3. I wonder if that's why I've been getting that auth: Fail
Where can I get the G900AUCU2AND3 stock firmware from?

Try going to the sammobile website (cant post link because I'm a new member). It should be there
Sent from my SM-G900F using XDA Premium 4 mobile app

tmadekush said:
I just notice when I was using Odin I tried to flash G900AUCU1ANCE stock firmware. My phone says I'm running G900AUCU2AND3. I wonder if that's why I've been getting that auth: Fail
Where can I get the G900AUCU2AND3 stock firmware from?
Click to expand...
Click to collapse
Your warranty should be honoured because it still shows Knox 0x0. But it would be prudent to resolve the custom message as you are trying to do. It's showing custom because you disabled Knox. Flashing a full stock firmware should restore Knox and resolve the custom message.
Odin flashes can fail for many reasons e.g. trying to flash non-Odin versions of firmware, bad signatures, poor quality USB cables, wrong firmware version e.g. one meant for a different phone, et cetera.
Back up your files, then do a full system reset from the settings menu. Then put your phone into download mode and use Odin to flash a full stock firmware. Ideally use the latest firmware version for carrier that the phone originally came from (i.e. it should match the baseband). Google will find many firmware repositories e.g. sammobile, samsung-updates and this site.
.

Related

Cannot update S4

I bought a 'brand new Galaxy S4' which came with rooted. I have flashed the BTU firmware to the device but in Keis it says device not eligible for update.
How can I fix this?
roastspud said:
I bought a 'brand new Galaxy S4' which came with rooted. I have flashed the BTU firmware to the device but in Keis it says device not eligible for update.
How can I fix this?
Click to expand...
Click to collapse
You should be able to flash back to stock using odin then upgrade or flash the updated version with odin.
Sent from my SCH-I545 using xda app-developers app
You have to unroot your device and flash the firmware with corresponding CSC to your country. On top of that you have to flash the firmware that was ALREADY officialy in your country (best way is to download package from sammobile.com) after that the OTA will work. I know because I also had problems with OTA after rooting the device.
I have reflashed the BTU UK firmware I9505XXUAMDM via ODIN and my device now shows as running official rom
Kies now says...
Your devices current firmware version is not supported to update via Kies.
What gives?
Hi,
Recovery mode mentions multi csc. Could this be the problem?
roastspud said:
I have reflashed the BTU UK firmware I9505XXUAMDM via ODIN and my device now shows as running official rom
Kies now says...
Your devices current firmware version is not supported to update via Kies.
What gives?
Click to expand...
Click to collapse
Maybe go into stock recovery and wipe data/factory reset then reboot ??
Sent from my SCH-I545 using xda app-developers app
jds3118 said:
Maybe go into stock recovery and wipe data/factory reset then reboot ??
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Thanks.
Just tried that. Went back to recovery mode after and it said manual mode.. applied the csc again and mentioned multi csc exists
roastspud said:
Thanks.
Just tried that. Went back to recovery mode after and it said manual mode.. applied the csc again and mentioned multi csc exists
Click to expand...
Click to collapse
Recovery mode has a android bot lay down with a red exclamation mark
roastspud said:
I bought a 'brand new Galaxy S4' which came with rooted. I have flashed the BTU firmware to the device but in Keis it says device not eligible for update.
How can I fix this?
Click to expand...
Click to collapse
Hi,
Where did you buy a "Brand New S4" with root?
Not sure what you are trying to do.
You have root, so, just flash the latest stock ROM and you are up to date.
If you are trying to get back to "Official" stock, then, look HERE
Use Triangle Away to reset your counter, and you will be able to get Ota.
Sent telepathically from my S4
malybru said:
Hi,
Where did you buy a "Brand New S4" with root?
Not sure what you are trying to do.
You have root, so, just flash the latest stock ROM and you are up to date.
If you are trying to get back to "Official" stock, then, look HERE
Use Triangle Away to reset your counter, and you will be able to get Ota.
Sent telepathically from my S4
Click to expand...
Click to collapse
I bought the phone from Amazon as new.. This is my first Android phone and I only noticed the problem when I checked the apps and it had SuperSU istalled and Kies complained about not being supported for updates.
What I am trying to do is get the phone running as stock so it will update via Kies + OTA and also remove the yellow multi CSC writing from the boot recovery menu.
I have tried unrooting and flashing stock BTU firmware but then I still have the yellow writing in the boot recovery menu and cannot update via Kies.
roastspud said:
I bought the phone from Amazon as new.. This is my first Android phone and I only noticed the problem when I checked the apps and it had SuperSU istalled and Kies complained about not being supported for updates.
What I am trying to do is get the phone running as stock so it will update via Kies + OTA and also remove the yellow multi CSC writing from the boot recovery menu.
I have tried unrooting and flashing stock BTU firmware but then I still have the yellow writing in the boot recovery menu and cannot update via Kies.
Click to expand...
Click to collapse
Hi,
OK.
Did you use the link I gave you ?
You need to get Triangle Away from the market.
malybru said:
Hi,
OK.
Did you use the link I gave you ?
You need to get Triangle Away from the market.
Click to expand...
Click to collapse
Thanks for your help so far.
Yes I have Triangle Away but no root..
malybru said:
Hi,
OK.
Did you use the link I gave you ?
You need to get Triangle Away from the market.
Click to expand...
Click to collapse
Ok.. here is what I have done so far..
Rooted the rom and ran triangle away to reset my counter to 1 . I have removed root and flashed stock BTU firmware then wiped data/cache from the recovery menu.
But I still have the multi csc message in stock recovery that will not budge and Kies reports the phone is not supported for updates.
Could this be because the boot loader is locked?
roastspud said:
Ok.. here is what I have done so far..
Rooted the rom and ran triangle away to reset my counter to 1 . I have removed root and flashed stock BTU firmware then wiped data/cache from the recovery menu.
But I still have the multi csc message in stock recovery that will not budge and Kies reports the phone is not supported for updates.
Could this be because the boot loader is locked?
Click to expand...
Click to collapse
Hi,
The bootloader is not locked.
You should have reset the counter to "0"
Then, flashed the stock firmware without rebooting the phone.
Does the recovery says that it "applied BTU" ? If not then your region code is not proper and that's why OTA does not work. Unfortunately it is hard to change CSC right now as Samsung has blocked the keystrings for user packages, keystrings works only for engineer builds.
And about that flash counter, it does not matter if its 100 or 0. The OTA will work as long as the status in download mode is official for both variables, and in Settings > About device is official too.
As I work at Samsung's R&D I know that you have to flash the firmware which was RELEASED for your country with proper CSC, the CSC has to be set (you can check it in recovery mode) and then both variables in download mode have to "Official" and status in About device also has to be Official. Then the OTA will work (At least over-the-air, not through Kies). Best way to check the OTA is to flash first firmware released for your country and check the updates. Ive done it dozen times on various devices and it always worked. You cannot be rooted and need stock recovery. The only major problem might be changing CSC on your own, because as I said it is not easy right now as Samsung blocked *#272* keystring in user packages (released for the market). Flashing engineering build will make the all keystrings work, but I guess you won't find any of those odin flashables on the net.
tehaerpl said:
Does the recovery says that it "applied BTU" ? If not then your region code is not proper and that's why OTA does not work. Unfortunately it is hard to change CSC right now as Samsung has blocked the keystrings for user packages, keystrings works only for engineer builds.
And about that flash counter, it does not matter if its 100 or 0. The OTA will work as long as the status in download mode is official for both variables, and in Settings > About device is official too.
As I work at Samsung's R&D I know that you have to flash the firmware which was RELEASED for your country with proper CSC, the CSC has to be set (you can check it in recovery mode) and then both variables in download mode have to "Official" and status in About device also has to be Official. Then the OTA will work (At least over-the-air, not through Kies). Best way to check the OTA is to flash first firmware released for your country and check the updates. Ive done it dozen times on various devices and it always worked. You cannot be rooted and need stock recovery. The only major problem might be changing CSC on your own, because as I said it is not easy right now as Samsung blocked *#272* keystring in user packages (released for the market). Flashing engineering build will make the all keystrings work, but I guess you won't find any of those odin flashables on the net.
Click to expand...
Click to collapse
It says applied BTU but multi CSC exists. How do I find the original CSC code out? SO its not possible to change this at all or at least get rid of that stupid message?
Is a green andriod bot with a red exclamation mark anything to be worried about?
OTA updates now work fine However they dont work via Kies. Is this normal?
FYI the flash counter was at 3 so somebody had obviously messed with this.
Sorry for all the questions. This is my first Android device having switched from Crapple
It is weird because the box was sealed and had the protectors on the phone.
Multi CSC means that the file that was flashed contains few regions code and that it can be changed inside the OS with keystring. So nothing to worry about as long as it is set to your country and OTA works. As for the icon, it is normal after entering recovery, my device also has that icon, it does not mean that there is some error. Kies does not always wants to cooperate I do not know why, but as long over-the-air works you're not missing anything apart from cable update.
tehaerpl said:
Multi CSC means that the file that was flashed contains few regions code and that it can be changed inside the OS with keystring. So nothing to worry about as long as it is set to your country and OTA works. As for the icon, it is normal after entering recovery, my device also has that icon, it does not mean that there is some error. Kies does not always wants to cooperate I do not know why, but as long over-the-air works you're not missing anything apart from cable update.
Click to expand...
Click to collapse
Thanks everyone Now I just need to find some decent apps
Have fun with Android, in case of any questions you can always send a PM
roastspud said:
It says applied BTU but multi CSC exists. How do I find the original CSC code out? SO its not possible to change this at all or at least get rid of that stupid message?
Is a green andriod bot with a red exclamation mark anything to be worried about?
OTA updates now work fine However they dont work via Kies. Is this normal?
FYI the flash counter was at 3 so somebody had obviously messed with this.
Sorry for all the questions. This is my first Android device having switched from Crapple
It is weird because the box was sealed and had the protectors on the phone.
Click to expand...
Click to collapse
Hi,
That is why I questioned the fact that you bought a phone , and it came "Out-of-the-box" with root.
This just does not happen.
Anyway,glad you got it sorted.

Update Error

Hi guys! I hope someone could help me. I just bought a Galaxy Note 3 (international version) yesterday. The phone's fine. It's just that I am unable to update. I am able to download it but when my phone reboots it shows a dead android with a red triangle on its chest. I read flashing the firmware via odin can fix it but problem is our internet is hella slow. I couldn't even complete downloading my brother's Note 2 firmware. Any way I can make it install the firmware successfully? By the way it's OTA. I am able to download the update, just won't let me finish installing it. Goes around 35% then the android on the black screen dies with a red triangle on its chest.
EDIT:
I have official firmware, never rooted, just got it yesterday. Still factory new.
version 4.3, build # JSS15J.N9005ZHUBMI7, baseband version N9005XXUBMI5, Kernel version 3.4.0-1626679
Have you tried reseting your phone go into recovery mode factory reset
Mygadgetgeek.com
mygadgetgeek.com said:
Have you tried reseting your phone go into recovery mode factory reset
Mygadgetgeek.com
Click to expand...
Click to collapse
not yet, but i have a lot of data now on my phone. will try that though. in case that doesn't work, any other advice?
cptnappy said:
Hi guys! I hope someone could help me. I just bought a Galaxy Note 3 (international version) yesterday. The phone's fine. It's just that I am unable to update. I am able to download it but when my phone reboots it shows a dead android with a red triangle on its chest. I read flashing the firmware via odin can fix it but problem is our internet is hella slow. I couldn't even complete downloading my brother's Note 2 firmware. Any way I can make it install the firmware successfully? By the way it's OTA. I am able to download the update, just won't let me finish installing it. Goes around 35% then the android on the black screen dies with a red triangle on its chest.
EDIT:
I have official firmware, never rooted, just got it yesterday. Still factory new.
version 4.3, build # JSS15J.N9005ZHUBMI7, baseband version N9005XXUBMI5, Kernel version 3.4.0-1626679
Click to expand...
Click to collapse
Was your phone brand new? And did you check your KNOX status? -- reason I ask, after you've rooted a phone you are unable to recieve OTA updates, unless you use Wanam to fake system status, then you can download the OTA update but it stalls on the install about 35% or so in..
Best advice, is grab the stock image from sammobile (ballache to download I know) then use ODIN to flash her back to original state.
radicalisto said:
Was your phone brand new? And did you check your KNOX status? -- reason I ask, after you've rooted a phone you are unable to recieve OTA updates, unless you use Wanam to fake system status, then you can download the OTA update but it stalls on the install about 35% or so in..
Best advice, is grab the stock image from sammobile (ballache to download I know) then use ODIN to flash her back to original state.
Click to expand...
Click to collapse
i didn't root the phone when i got it. it's fresh and on official firmware. have no idea about KNOX, that's new to me. if it helps, my device status says "official"
unfortunately the internet in my area is very slow, i couldn't download firmwares from sammobile. i tried several times
cptnappy said:
i didn't root the phone when i got it. it's fresh and on official firmware. have no idea about KNOX, that's new to me. if it helps, my device status says "official"
unfortunately the internet in my area is very slow, i couldn't download firmwares from sammobile. i tried several times
Click to expand...
Click to collapse
Ah Ok, if it says Official it should be good to go. Seems like maybe the download has gotten corrupt due to an intermittent internet connection.
cptnappy said:
i didn't root the phone when i got it. it's fresh and on official firmware. have no idea about KNOX, that's new to me. if it helps, my device status says "official"
unfortunately the internet in my area is very slow, i couldn't download firmwares from sammobile. i tried several times
Click to expand...
Click to collapse
OK, then maybe you should learn a few things before trying to update - Knox is a security system in latest Samsung phones that is supposed to be triggered/set when you root (or install any custom kernel/recovery). Your initial (old) firmware could still let you root without triggering the Knox flag, and then you can update to the latest firmware for your region using Mobile Odin Pro and still keep your root AND without triggering the Knox flag. However once you update using Samsung OTA / Odin / Kies to a firmware more recent than MJ3 you can no longer root without also triggering your Knox warrany flag - read more about this in the Universal Root De La Vega thread!
i gave up after several tries, since i'm on 4.3 i think that would do for now. maybe it's just downloading a stability update or something? everytime i do an OTA update, it tells me that the download of the new firmware is complete then reboot. when i get to 32% the droid falls flat on its back and shows the red triangle on its chest, over and over. i don't lose my phone data or anything. just won't update. i'll wait for 4.4 Kitkat instead. hope i'll be able to update to that when it comes out.
EDIT: i tried going into recovery mode, wiping cache, and factory reset.. still no dice. maybe Odin's the only way i guess. problem is my internet connection lol
@cptnappy - i also have the same problem...got my note3 n9005 a week ago and I also have the same problem as you....error at 30+%
tried update thru Kies with no luck...same error appears
Sent3 said:
@cptnappy - i also have the same problem...got my note3 n9005 a week ago and I also have the same problem as you....error at 30+%
tried update thru Kies with no luck...same error appears
Click to expand...
Click to collapse
i managed to update mine using Samsung Kies3 (not Kies, but Kies3). Hope updating OTA is fixed in the future with the update i just did

WIFI not working after using KIES to update

Hi all,
Phone Details:
Spring Galaxy S4
Baseband Version L720TVPUBNG5
Used CF autoroot
This all started a few days ago. The latest OTA update came out and my phone kept telling me I had insufficient storage for the update. I figured it was because I had it rooted. I followed QBking77's video for Unroot / Unbrick. Downloaded all files recommended in the video.
Every time I try to flash with ODIN I get a failure. I have tried three different .tar versions at this point, it always seems to fail after "aboot" attempts to flash. Two different cables, both came with an SGS4.
I finally had enough and used the factory reset. After factory reset I used KIES for my update. The phone took it fine and rebooted. Although now I have no WIFI.
When initiating WIFI it will tell me that the security application has rejected a request to protect my phone. I deleted lookout security even though I have never used it.
Does this have something to do with KNOX? Knox flag is at 0x1 so I know it is tripped. Is there a way to completely flash my phone back to a stock state with the original recovery and rom?
Are there any options for me to get my phone back in order. I really dont give a **** about root or roms, I just need my WIFI. Would my best bet be to use a custom firmware?
Your correct thread have to go: HERE.

cannot update s5 software with kies, help?

my galaxy s5 model number is sm-g900t, android version is 4.4.2, ..not sure what other info might help, but anyway, i cannot update the software/firmware over the air because the device is rooted through steps on here and its been rooted awhile now. so anyway, i downloaded the kies 3 from the samsung site, it says all im supposed to do is plug the phone in, a box is supposed to pop up showing an update is needed......well, the kies box does pop up, but all it shows is current firmware version and shows my internal and external storage availabilty, and so on.... no auto update thing came up. so in kies i went into tools up a t the top, i hit firmware upgrade and initialization, then a smaller box pops up saying---does not support initializing, so now what? nothing else i can do in kies except move pic files around and such. i need to update the software. any advice? i attached 2 pics.....pic 1 is the initial message when phone is plugged in, #2 is when i go into tools and hit ugrade
knight1701 said:
my galaxy s5 model number is sm-g900t, android version is 4.4.2
Click to expand...
Click to collapse
Samsung has now embedded a security flag called KNOX in it's later devices. Unfortunately after you flash a package/custom ROM or whatever with a different signature than Samsungs own it trips that KNOX flag.
When your KNOX flag is tripped you can no longer update your phone via official methods. It is just the way it is, and there is nothing to be done. Once KNOX flag is tripped, there is no way to "untrip" it, so you will never be able to update via KIES again.
Im not really sure whether flashing a stock lollipop rom via odin works when KNOX is tripped, i have never tried it, so you should wait for any other member for confirmation. As far as i know, it shouldn't be a problem.
What i can tell you, if you have the time, is that you flash a ROM that is compatible with 4.4.2 (Omega v13 or AllianceROM v5.6 etc) and then flash it's ROMs lollipop update after a full wipe. It is the only thing i personally am sure about (i have done it before).
I'm by no means an expert on the matter but I'm pretty sure that if you can't get the Ota due to being rooted, then updating vIA Kies isn't going to work either.
Go to settings> about device> status
scroll to bottom of list and respond here what it says under "device status" (it's gong to say either official, or custom).
If it says official, you could unroot, maybe check that the proper drivers are installed on your computer, and try once again to apply the update via kies.
If it says custom, then knox has been tripped and I cannot help further.
The biggest issue here is that if you take the OTA update you'll lose the option to root or downgrade so you should probably use TWRP to install a ROM that's pre-rooted rather than trying to get the OTA
Akalsemann said:
Samsung has now embedded a security flag called KNOX in it's later devices. Unfortunately after you flash a package/custom ROM or whatever with a different signature than Samsungs own it trips that KNOX flag.
When your KNOX flag is tripped you can no longer update your phone via official methods. It is just the way it is, and there is nothing to be done. Once KNOX flag is tripped, there is no way to "untrip" it, so you will never be able to update via KIES again.
Im not really sure whether flashing a stock lollipop rom via odin works when KNOX is tripped, i have never tried it, so you should wait for any other member for confirmation. As far as i know, it shouldn't be a problem.
What i can tell you, if you have the time, is that you flash a ROM that is compatible with 4.4.2 (Omega v13 or AllianceROM v5.6 etc) and then flash it's ROMs lollipop update after a full wipe. It is the only thing i personally am sure about (i have done it before).
Click to expand...
Click to collapse
well i hear what your saying, but on my other phone, same setup, rooted and all.......updated just fine---did it about a month ago...updated to android 5 from 4.4.2..just plugged in the phone and boom it did its thing............on this other phone though, daughters phone, it wont work
Swimguy14 said:
I'm by no means an expert on the matter but I'm pretty sure that if you can't get the Ota due to being rooted, then updating vIA Kies isn't going to work either.
Go to settings> about device> status
scroll to bottom of list and respond here what it says under "device status" (it's gong to say either official, or custom).
If it says official, you could unroot, maybe check that the proper drivers are installed on your computer, and try once again to apply the update via kies.
If it says custom, then knox has been tripped and I cannot help further.
The biggest issue here is that if you take the OTA update you'll lose the option to root or downgrade so you should probably use TWRP to install a ROM that's pre-rooted rather than trying to get the OTA
Click to expand...
Click to collapse
ok, on the phone in question, device status says--- custom, guess that ends that..........on my phone howerver, it says official which is why i guess i was able to update mine
just download a rom for your phone from sammobile and install with odin and your done

O2U Note 4.... Broken?

So this is a bit of an odd situation my friend is having. He bought his Note 4 off eBay over a year ago, and it was (and still is) a rooted mess. And I mean a big mess. Now I'm trying to help him fix it, because he can't update his phone at all whatsoever from 5.1.1. So I send him 6.0.1 firmware for O2U and have him go into Download mode, odin, all that fun stuff. Download mode says SM-N910T. Settings says SM-N910F. Anyway, he tries flashing the firmware via odin, fails, I have him try multiple things (I'm pretty tech savvy when it comes to this type of stuff) but it always failed. Also, "Current Binary" and "System Status" are both custom, and the KNOX counter is 0x1.
So what I'm asking is, how to fix this problem for him? What steps should he take (or should I help him take)? Is this actually a T-Mobile phone from the USA, but rooted to work with O2 sim cards? The hell is going on here?
Thanks for any replies, and all suggestions will be taken seriously and addressed.
Install the Phone INFO Samsung APK by vndnguyen and see what it's written there.
Get the serial number - example: mine is a 910C with serial RF8H70D.... and so on (obviously I can't write it all here)
With this serial number try with Samsung Smart Switch on the PC and see what info you get. Also you have the possibility to get the latest original firmware installed on the phone.
Good luck.
Gunshots911 said:
So this is a bit of an odd situation my friend is having. He bought his Note 4 off eBay over a year ago, and it was (and still is) a rooted mess. And I mean a big mess. Now I'm trying to help him fix it, because he can't update his phone at all whatsoever from 5.1.1. So I send him 6.0.1 firmware for O2U and have him go into Download mode, odin, all that fun stuff. Download mode says SM-N910T. Settings says SM-N910F. Anyway, he tries flashing the firmware via odin, fails, I have him try multiple things (I'm pretty tech savvy when it comes to this type of stuff) but it always failed. Also, "Current Binary" and "System Status" are both custom, and the KNOX counter is 0x1.
So what I'm asking is, how to fix this problem for him? What steps should he take (or should I help him take)? Is this actually a T-Mobile phone from the USA, but rooted to work with O2 sim cards? The hell is going on here?
Thanks for any replies, and all suggestions will be taken seriously and addressed.
Click to expand...
Click to collapse
Looks like its an refurbished note 4 original motherboard is N910T and faked with N910F software cuz N910F has more value in Market.
So the bottom line is you have N910T Tmobile note 4 and you have to flash N910T firmware but after flash firmware from odin you have to immediately boot into stock recovery by pressing 3 button combo and do factory reset to get clean fresh opreating system otherwise it will get stuck in a bootloop at samsung logo.
First boot after flash and factory reset can take upto 10 minutes.
You can get firmware from www.sammobiles.com/firmwares
Or from link below for faster download.
https://androidfilehost.com/?fid=890129502657581810
Remember once you flash this latest marshmalow firmware there is no way you can ever downgrade to 5.1.1 again.
Good luck
Trex888 said:
Looks like its an refurbished note 4 original motherboard is N910T and faked with N910F software cuz N910F has more value in Market.
So the bottom line is you have N910T Tmobile note 4 and you have to flash N910T firmware but after flash firmware from odin you have to immediately boot into stock recovery by pressing 3 button combo and do factory reset to get clean fresh opreating system otherwise it will get stuck in a bootloop at samsung logo.
First boot after flash and factory reset can take upto 10 minutes.
You can get firmware from www.sammobiles.com/firmwares
Or from link below for faster download.
https://androidfilehost.com/?fid=890129502657581810
Remember once you flash this latest marshmalow firmware there is no way you can ever downgrade to 5.1.1 again.
Good luck
Click to expand...
Click to collapse
Thanks so much! Everything is flashing on his phone right now like it should be. Appreciate it a bunch!
I also used samsung-firmware.org. I would use sammobile but I only had enough on my card for a 48 hour upgrade.

Categories

Resources