Database Develop

[ROM][TAR] Stock MK2 Odin flashable

You will get the KNOX bootloader if you flash this.
YOU CANNOT UNDO THIS, ITS PERMANENT. FLASHING ANYTHING UNOFFICIAL AFTER FLASHING THIS TAR WILL VOID YOUR WARRANTY​
Just the MK2 FULL stock tar extracted from Kies. Very hard to find online, and only extremely SLOW downloads available, so here it is.
md5 of the Tar: b90c2a1b5b32dca4edc56a3e6a8a3522
Do NOT rename the tar file. Even though it may be convenient to do so, Odin may fail the md5 check for no reason.
(L720VPUEMK2_L720SPTEMK2_L720VPUEMK2_HOME.tar.md5)
This is NOT ROOTED. Its the original TAR file for people who need an Emergency Recovery for their phones, and dont want to wait hours for it to download from slow file hosts.
Mediafire
FileDropper
Instructions:
1. Download tar.md5 from above and download Odin
2. Put phone into download mode (power off, then power button + Volume Down, then volume up when prompted)
3. Open Odin (right click > open as administrator)
4. Load stock tar into the PDA slot
5. Start flashing
6. Grab some popcorn because it will take a while
7. Profit

Danger......Read carefully before flashing.

so if im on stock unrooted mja or mk2 and for any reason i want to flash this file it will cause knox to trip?
i dont understand.
you say it will cause knox to trip!

en11gma said:
so if im on stock unrooted mja or mk2 and for any reason i want to flash this file it will cause knox to trip?
i dont understand.
you say it will cause knox to trip!
Click to expand...
Click to collapse
You will be alright. You have already upgraded to stock 4.3, so you already have the knox bootloader.
If you flash something unofficial, such as CF autoroot or a different recovery, you will trip the warranty void. The tar file I posted are Official, and will not trip the warranty.
Sent from my SPH-L720 using Tapatalk

what happens if i am rooted or have a custom recovery and my knox counter = 1 and i want to flash this with odin?

en11gma said:
what happens if i am rooted or have a custom recovery and my knox counter = 1 and i want to flash this with odin?
Click to expand...
Click to collapse
Well you have already voided your warranty then and currently there is no way to get the knox counter back to 0.
If you flash this, you will be going back to full stock, like you would expect. You are safe to do this.
Sent from my SPH-L720 using Tapatalk

random45 said:
Well you have already voided your warranty then and currently there is no way to get the knox counter back to 0.
If you flash this, you will be going back to full stock, like you would expect. You are safe to do this.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
i have been reading over and over if you try to flash an mk2 or mja over a rooted or custom recovery that you can brick the phone?
are you sure odin would flash this when it detects there is a knox = 1 and custum recovery or root?
dont think it is as simple as you say when you are knox = 1 with custum recovery or root.
hope your right. but i dont think so.

en11gma said:
i have been reading over and over if you try to flash an mk2 or mja over a rooted or custom recovery that you can brick the phone?
are you sure odin would flash this when it detects there is a knox = 1 and custum recovery or root?
dont think it is as simple as you say when you are knox = 1 with custum recovery or root.
hope your right. but i dont think so.
Click to expand...
Click to collapse
I've used Odin to go back to MJA a couple times with a tripped knox counter and custom recovery. It works every time. Why wouldn't it? It just doesn't reset the counter.
Sent from my Galaxy S4 using Tapatalk 4

xanaxdroid said:
I've used Odin to go back to MJA a couple times with a tripped knox counter and custom recovery. It works every time. Why wouldn't it? It just doesn't reset the counter.
Sent from my Galaxy S4 using Tapatalk 4
Click to expand...
Click to collapse
i would assume something is stripped from the MJA and MK2 we get for odin files
kies and ota definately do checks and WIPES better
for some reason the MJA and MK2 i been flashing (stock mja/mk2) on me no root or cust reoovery (knox = 0x0)
those files are not wiping like they should
why are we always having to do wipes 2 and 3x like alot of these instructions say????
something not right
anyhow yea usually i would think just odin over a stock and everything ok.
knox is wierd and i dont know alot about.
people are talking about OTA and KIES screwing their phones up
i see alot of diff stuff being posted and its moving fast.
why are we still having problems with rooting?
isnt cf-auto-root working 100% now for mja and mk2?
are both twrp and cwmr/philz working 100% as far as functioning correctly and not messing anything up in the rom or firmware they go on top of or happen to install with?
seems like alot of people in those channels/forums dont like talking about it to much.
i thin what i will do is stick with stock firmwares (rooted) and then disable the hands free activation and the android system update
then i will just keep those roms to restore to in case it gets bad

en11gma said:
i would assume something is stripped from the MJA and MK2 we get for odin files
kies and ota definately do checks and WIPES better
for some reason the MJA and MK2 i been flashing (stock mja/mk2) on me no root or cust reoovery (knox = 0x0)
those files are not wiping like they should
why are we always having to do wipes 2 and 3x like alot of these instructions say????
something not right
anyhow yea usually i would think just odin over a stock and everything ok.
knox is wierd and i dont know alot about.
people are talking about OTA and KIES screwing their phones up
i see alot of diff stuff being posted and its moving fast.
why are we still having problems with rooting?
isnt cf-auto-root working 100% now for mja and mk2?
are both twrp and cwmr/philz working 100% as far as functioning correctly and not messing anything up in the rom or firmware they go on top of or happen to install with?
seems like alot of people in those channels/forums dont like talking about it to much.
i thin what i will do is stick with stock firmwares (rooted) and then disable the hands free activation and the android system update
then i will just keep those roms to restore to in case it gets bad
Click to expand...
Click to collapse
Sorry I don't understand. Who's having trouble rooting? And that wipe 2 or 3 times stuff is bs. You only have to wipe once. As for the other stuff I don't know. All I know is my phone has worked fine and has never bricked. I don't use KIES either though and mostly run aosp roms.
Sent from my Galaxy S4 using Tapatalk 4

xanaxdroid said:
Sorry I don't understand. Who's having trouble rooting? And that wipe 2 or 3 times stuff is bs. You only have to wipe once. As for the other stuff I don't know. All I know is my phone has worked fine and has never bricked. I don't use KIES either though and mostly run aosp roms.
Sent from my Galaxy S4 using Tapatalk 4
Click to expand...
Click to collapse
i can verify the wiping/erasing from installing that mja or mk2 is not doing what it usually did with other fully stock rom
i think this phone has 2 firmwares and when you mod one the other one boots the next boot that is why you have to wipe it there too
there is DEFINATELY some double booting going on here
that is also why you tell cf-auto-root, twrp and cwmr NOT to reboot
pull battery and boot directly into recovery
i have had to do 2 and 3 wipes and its not just that
i was on mk2 firmware and i downflashed the modem to mdc
i had to reboot at desktop to get it to show in "about" settings
i then flashed the mk2 firmware (stock 2GB) and when i got in ui AGAIN it still showing MDC.....WTF???
ok so i boot into android recovery and wipe again and reboot and its now MK2
sometimes i just reboot and it will show it next time
its not just there either.
settings in ##3424# and *#9090# are also not getting erased with new official rom installs
really wierd stuff
yea i prob only used kies once in mylife and that was just to test it
usually im on CMnightly whatever is the latest
im not new and i most likely above avg on phone stuff
this KNOX stuff is wierd
even if you do an OTA the phone resets 2x during the install process and i think even with odin too

en11gma said:
i can verify the wiping/erasing from installing that mja or mk2 is not doing what it usually did with other fully stock rom
i think this phone has 2 firmwares and when you mod one the other one boots the next boot that is why you have to wipe it there too
there is DEFINATELY some double booting going on here
that is also why you tell cf-auto-root, twrp and cwmr NOT to reboot
pull battery and boot directly into recovery
i have had to do 2 and 3 wipes and its not just that
i was on mk2 firmware and i downflashed the modem to mdc
i had to reboot at desktop to get it to show in "about" settings
i then flashed the mk2 firmware (stock 2GB) and when i got in ui AGAIN it still showing MDC.....WTF???
ok so i boot into android recovery and wipe again and reboot and its now MK2
sometimes i just reboot and it will show it next time
its not just there either.
settings in ##3424# and *#9090# are also not getting erased with new official rom installs
really wierd stuff
yea i prob only used kies once in mylife and that was just to test it
usually im on CMnightly whatever is the latest
im not new and i most likely above avg on phone stuff
this KNOX stuff is wierd
even if you do an OTA the phone resets 2x during the install process and i think even with odin too
Click to expand...
Click to collapse
I let c.f. auto root reboot itself after odining to mk2 and it worked fine. And why are you mixing and matching firmwares and basebands? Also are you using "official" files or files that some guy with one post puts up? I'd say decide what you want to use and stick with it. Anyway good luck.
Sent from my Galaxy S4 using Tapatalk 4

random45 said:
...
Click to expand...
Click to collapse
Hey man. I wanted to let you know I appreciate the crap out of you doing this. The slow downloads are awful. However, I've flashed this .tar file twice now using 2 different version numbers of Odin and the phone boots up but hangs on the SAMSUNG screen. Not the very first boot screen that says samsung galaxy s4 but the next one that begins with the purple and blue swirl and turns into the samsung logo while the led pulses blue. The phone doesn't freeze per se, it just never moves beyond this screen. Unless it's supposed to take 20-30 minutes, which I doubt is the case. Did I possibly get a bad download?

FlowingAway said:
Hey man. I wanted to let you know I appreciate the crap out of you doing this. The slow downloads are awful. However, I've flashed this .tar file twice now using 2 different version numbers of Odin and the phone boots up but hangs on the SAMSUNG screen. Not the very first boot screen that says samsung galaxy s4 but the next one that begins with the purple and blue swirl and turns into the samsung logo while the led pulses blue. The phone doesn't freeze per se, it just never moves beyond this screen. Unless it's supposed to take 20-30 minutes, which I doubt is the case. Did I possibly get a bad download?
Click to expand...
Click to collapse
As with any rom when you first boot up, yes it's supposed to take a while. ("android is upgrading" in disguise maybe?)
Did you do a factory reset before booting up?
Let it do its thing for 10 min at least, and longer than that if you didn't factory reset. If it doesn't boot, then do a factory reset.
Sent from my SPH-L720 using Tapatalk

random45 said:
As with any rom when you first boot up, yes it's supposed to take a while. (android is upgrading in disguise maybe?)
Did you do a factory reset before booting up?
Let it do its thing for 10 min at least, and longer than that if you didn't factory reset. If it doesn't boot, then do a factory reset.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
Just saw your reply, thank you. That was the one thing I didn't try. Right after I posted that last message I got into recovery (finally after 3 or 4 tries) and did the factory reset and it booted up perfectly! So handy having this file around. Thanks again for uploading.

I'm happy I found this post. I was able to help my friend with his phone. THANKS!

en11gma said:
i have been reading over and over if you try to flash an mk2 or mja over a rooted or custom recovery that you can brick the phone?
are you sure odin would flash this when it detects there is a knox = 1 and custum recovery or root?
dont think it is as simple as you say when you are knox = 1 with custum recovery or root.
hope your right. but i dont think so.
Click to expand...
Click to collapse
Just for reference, I just did this and it worked just fine. I downgraded the modem to MDC and had SACS installed on it, wifi was not working so did this and it works
i dont care about warranty -

its been over 10 minutes and im still on the yellow sprint screen

I understand that if your flash this MK2 tar you'll end up with the knox bootloader. But if someone wanted to get rid of knox, couldn't they just flash the MJA tar then re-root and update to an knox free MK2 firmware that unknownforce provided and you'd be all set?

LouRock said:
I understand that if your flash this MK2 tar you'll end up with the knox bootloader. But if someone wanted to get rid of knox, couldn't they just flash the MJA tar then re-root and update to an knox free MK2 firmware that unknownforce provided and you'd be all set?
Click to expand...
Click to collapse
There is no known method of removing the knox bootloader, to my knowledge.

New Canadian (900W8) ROM's released

Went to SamMobile today. Finally got an update from Samsung for my Rogers device, the SM-G900W8. It's dated July 2014, previous for Rogers was April.
Here are the PDA and CSC versions: G900W8VLU1ANF3 G900W8OYA1ANF3
Link is here: http://www.sammobile.com/firmwares/
Anyone install it yet? Anyone notice any difference?

Got the new ROM update this morning thru OTA. I don't see anything new or special. Still at 4.4.2

Anybody able to extract the NF3 modem from it and make it into a flashable file? That'd be gravy...

Tried to find a change log to see if there were any important changes, but no luck.

harry_fine said:
Went to SamMobile today. Finally got an update from Samsung for my Rogers device, the SM-G900W8. It's dated July 2014, previous for Rogers was April.
Here are the PDA and CSC versions: G900W8VLU1ANF3 G900W8OYA1ANF3
Link is here: http://www.sammobile.com/firmwares/
Anyone install it yet? Anyone notice any difference?
Click to expand...
Click to collapse
Thanks :good: I hope it fixes the problem I have with the radio getting stuck on 3G after calls...

I extracted the modem.... tried to make a flashable CWM file for you guys but 7zip is giving me a hard time... then again, I think it's better if you just flash from Odin directly, I believe it's safer

What about a Rom?. I wish I was able to I would have us a Canadian rom.

Well, this is NOT a flashable modem, merely the modem all rar'ed up; just download it, extract it, and flash it via PHONE on Odin 3.09, and you should be golden. If it does not stick, remove the battery for 15 seconds, and get into Download mode via the usual button combinations, then flash away.
G900W8_NF3_MODEM
---------- Post added at 03:34 AM ---------- Previous post was at 03:32 AM ----------
ChantalCaron13 said:
What about a Rom?. I wish I was able to I would have us a Canadian rom.
Click to expand...
Click to collapse
Lol why... just flash an international rom, works just as good... and if you really want to be up to date, just flash the modem I just posted.
Yes, you just
1- Download any international rom your body pleases
2- Flash it
3- Go eat a sandwich
Simple pimple control

omegajester said:
Well, this is NOT a flashable modem, merely the modem all rar'ed up; just download it, extract it, and flash it via PHONE on Odin 3.09, and you should be golden. If it does not stick, remove the battery for 15 seconds, and get into Download mode via the usual button combinations, then flash away.
G900W8_NF3_MODEM
---------- Post added at 03:34 AM ---------- Previous post was at 03:32 AM ----------
Lol why... just flash an international rom, works just as good... and if you really want to be up to date, just flash the modem I just posted.
Yes, you just
1- Download any international rom your body pleases
2- Flash it
3- Go eat a sandwich
Simple pimple control
Click to expand...
Click to collapse
Just hate that the phone dialer app on the int roms have the videocall icon on the bottom left corner instead of the text icon.

ChantalCaron13 said:
Just hate that the phone dialer app on the int roms have the videocall icon on the bottom left corner instead of the text icon.
Click to expand...
Click to collapse
Flash a T Mobile rom then... works just as good, plus you get the white dialer background, etc.

Flashed new modem, success. Via odin 3.09

Brava27 said:
Flashed new modem, success. Via odin 3.09
Click to expand...
Click to collapse
How's it going with it so far? At least my phone gets stronger reception in places it was weak before.

omegajester said:
How's it going with it so far? At least my phone gets stronger reception in places it was weak before.
Click to expand...
Click to collapse
How do you flash the new radio Bin file from Odin? I've done .tar files before for ROM's and such.

Anything new with this build ?

harry_fine said:
How do you flash the new radio Bin file from Odin? I've done .tar files before for ROM's and such.
Click to expand...
Click to collapse
Extract the zip file I uploaded; you're going to be left with a modem.bin. Flash via Odin as usual, just don't do it via PDA; use PHONE option instead.

So far I've noticed that you have to agree to terms for ultra power saving mode now when you first turn it on, and normal power saving mode shows an icon at the top left now when on.
Sent from my SM-G900W8 using XDA Premium 4 mobile app

omegajester said:
How's it going with it so far? At least my phone gets stronger reception in places it was weak before.
Click to expand...
Click to collapse
harry_fine said:
How do you flash the new radio Bin file from Odin? I've done .tar files before for ROM's and such.
Click to expand...
Click to collapse
No differences really, new modem flashed bin through Odin 3.09 and good reception. Clicked phone or CP and boom. Profit
Sent from my SM-G900W8 using Tapatalk

Thanks for the radio.

Am I the only one for whom the update failed? Because I tried twice to install it and I receive a message telling me that the updated failed to install correctly twice.

Worked fine for me. Towelroot still works too.
Sent from my SM-G900W8

custom binary blocked by frp lock SM-N920p

Well i flashed Tdunham's rom on the SM-N920P also flashed the second version of Freeza's beastmode kernel and twrp all is well after that unfortunately after doing some looking i found that i must have clicked oem unlock and turned it off and didnt know and shut it off now i get a custom binary blocked by frp lock in the upper left hand corner and i cant boot up the phone or access the bootloader because of it but i can switch to download mode but everything i try to flash comes up as failed can anyone tell if i can fix this?

T9EX said:
Well i flashed Tdunham's rom on the SM-N920P also flashed the second version of Freeza's beastmode kernel and twrp all is well after that unfortunately after doing some looking i found that i must have clicked oem unlock and turned it off and didnt know and shut it off now i get a custom binary blocked by frp lock in the upper left hand corner and i cant boot up the phone or access the bootloader because of it but i can switch to download mode but everything i try to flash comes up as failed can anyone tell if i can fix this?
Click to expand...
Click to collapse
I honestly have no clue what you're saying here. I'm not trying to be the grammar police, but there's not a single comma or period in that entire paragraph.
Are you suggesting that you flashed something (with TWRP) when "OEM unlock" was turned off? Then when you reboot the phone nothing happens except immediately seeing "frp lock" in the upper left corner (and nothing else whatsoever?)
Can you power down the phone? (press/hold volume down and power.) If so, after it's powered down, what happens when you try to boot into bootloader/download/odin mode? What steps are you performing to boot into odin mode from a power off state?
Are you able to boot directly into recovery mode from a powered down state? What steps are you performing to boot into recovery from a powered down state? What happens as a result of those steps?
PLEASE use periods, commas and line breaks to help format your message. Help us to help you...
Gary

garyd9 said:
I honestly have no clue what you're saying here. I'm not trying to be the grammar police, but there's not a single comma or period in that entire paragraph.
Are you suggesting that you flashed something (with TWRP) when "OEM unlock" was turned off? Then when you reboot the phone nothing happens except immediately seeing "frp lock" in the upper left corner (and nothing else whatsoever?)
Can you power down the phone? (press/hold volume down and power.) If so, after it's powered down, what happens when you try to boot into bootloader/download/odin mode? What steps are you performing to boot into odin mode from a power off state?
Are you able to boot directly into recovery mode from a powered down state? What steps are you performing to boot into recovery from a powered down state? What happens as a result of those steps?
PLEASE use periods, commas and line breaks to help format your message. Help us to help you...
Gary
Click to expand...
Click to collapse
i flashed a custom rom, kernel, and twrp everything worked after that, but somehow i wasnt paying attention and turned off oem unlock before i tried to restart my phone. Now when i try and turn it on or boot into recovery i get to the Samsung logo and it says frp lock in the corner. I am holding power, home, and volume up for recovery. And im holding power, home, and volume down for odin. Once i get into odin everything seems ok, but i cannot flash anything else to it. Sorry about the grammar it was kind of late

T9EX said:
i flashed a custom rom, kernel, and twrp everything worked after that, but somehow i wasnt paying attention and turned off oem unlock before i tried to restart my phone. Now when i try and turn it on or boot into recovery i get to the Samsung logo and it says frp lock in the corner. I am holding power, home, and volume up for recovery. And im holding power, home, and volume down for odin. Once i get into odin everything seems ok, but i cannot flash anything else to it. Sorry about the grammar it was kind of late
Click to expand...
Click to collapse
First, I don't think I'll be able to help you myself. However, I'm hoping that my questions might prompt enough information that someone else can...
How do you know that you turned off OEM unlock? Are you SURE that OEM lock was turned off?
I did a quick search on your behalf, and came up with some threads that may (or may not) be useful. At the very least, you might be able to pursue the people who posted in those threads to see what resolution they came up with:
This guy seems to have resolved his issue, but didn't mention how:
http://forum.xda-developers.com/s6-edge-plus/help/bricked-frp-lock-help-to-t3209788
This one seems to think that a stock flash with ODIN should recover:
http://forum.xda-developers.com/sprint-galaxy-s6-edge-plus/help/frp-lock-t3215940
Here's another one that did a stock ODIN flash to recover:
http://forum.xda-developers.com/tmo...ompletely-bricked-s6-edge-g925t-help-t3146069
Based on these, I'd try to get my hands on a full SM-N920P ODIN image and use ODIN. It would have to be a real "P" model tar.md5, probably. Sprint might also be able to re-flash an image on there for you.
You mentioned that you tried ODIN and it didn't work. What did you try to flash with ODIN? Was it an actual Sprint ODIN file? With OEM lock, I believe that the ONLY thing you'll be able to flash is a true n920p image...
Edit: I did a quick search on sammobile for your device type, and here's a link to n920p firmware. (Note to Mods: If this link violates any XDA rules, please edit it accordingly, but if possible leave enough information that the OP can get what he/she needs to recover their device.)
http://www.sammobile.com/firmwares/database/SM-N920P/
Another thought might be to use Samsung's "smart switch" software to do an emergency recovery of the firmware. (I've never used it for that, or anything else, but others have posted that something like this is possible.)

garyd9 said:
First, I don't think I'll be able to help you myself. However, I'm hoping that my questions might prompt enough information that someone else can...
How do you know that you turned off OEM unlock? Are you SURE that OEM lock was turned off?
I did a quick search on your behalf, and came up with some threads that may (or may not) be useful. At the very least, you might be able to pursue the people who posted in those threads to see what resolution they came up with:
This guy seems to have resolved his issue, but didn't mention how:
http://forum.xda-developers.com/s6-edge-plus/help/bricked-frp-lock-help-to-t3209788
This one seems to think that a stock flash with ODIN should recover:
http://forum.xda-developers.com/sprint-galaxy-s6-edge-plus/help/frp-lock-t3215940
Here's another one that did a stock ODIN flash to recover:
http://forum.xda-developers.com/tmo...ompletely-bricked-s6-edge-g925t-help-t3146069
Based on these, I'd try to get my hands on a full SM-N920P ODIN image and use ODIN. It would have to be a real "P" model tar.md5, probably. Sprint might also be able to re-flash an image on there for you.
You mentioned that you tried ODIN and it didn't work. What did you try to flash with ODIN? Was it an actual Sprint ODIN file? With OEM lock, I believe that the ONLY thing you'll be able to flash is a true n920p image...
Edit: I did a quick search on sammobile for your device type, and here's a link to n920p firmware. (Note to Mods: If this link violates any XDA rules, please edit it accordingly, but if possible leave enough information that the OP can get what he/she needs to recover their device.)
http://www.sammobile.com/firmwares/database/SM-N920P/
Another thought might be to use Samsung's "smart switch" software to do an emergency recovery of the firmware. (I've never used it for that, or anything else, but others have posted that something like this is possible.)
Click to expand...
Click to collapse
do you happen to know specifically which image i will have to flash? I'm still kinda new to this world and slowly teaching myself everything through trial and error.

T9EX said:
do you happen to know specifically which image i will have to flash? I'm still kinda new to this world and slowly teaching myself everything through trial and error.
Click to expand...
Click to collapse
I posted a link. There's only one image available at that link. If it's zip'd, unzip it to a file with an extension of "tar.md5"
That goes into the "AP" (or "PDA") slot for ODIN.
Now, I'm going to get on my soapbox for a moment:
Don't flash stuff on your phone without knowing ahead of time the steps to get it back to stock, AND having the tools/files needed to do so. If you ignore this "advice", you have only yourself to blame for any troubles. You're lucky that sammobile has a stock firmware file. (You won't find any AT&T variant files there for this phone.) If they didn't have that stock firmware file, you'd be screwed.
Learn FIRST... and always be prepared for "Uh oh"

He fixed his problem friend I have the same problem.

Dark235 said:
He fixed his problem friend I have the same problem.
Click to expand...
Click to collapse
I fixed mine by extracting each .img file from the stock ROM, then re-compressed back into a .tar file, then flashed each one individually. I don't know if that's what fixed it but that's what I did.

T9EX said:
I fixed mine by extracting each .img file from the stock ROM, then re-compressed back into a .tar file, then flashed each one individually. I don't know if that's what fixed it but that's what I did.
Click to expand...
Click to collapse
Thank you very much for your answer I'll try.

T9EX said:
Well i flashed Tdunham's rom on the SM-N920P also flashed the second version of Freeza's beastmode kernel and twrp all is well after that unfortunately after doing some looking i found that i must have clicked oem unlock and turned it off and didnt know and shut it off now i get a custom binary blocked by frp lock in the upper left hand corner and i cant boot up the phone or access the bootloader because of it but i can switch to download mode but everything i try to flash comes up as failed can anyone tell if i can fix this?
Click to expand...
Click to collapse
To solve the FRP lock is actually very simple
I'll give you a reminder ：“OTG cable”

Dark235 said:
Thank you very much for your answer I'll try.
Click to expand...
Click to collapse
Did you ever manage to fix it?

T9EX said:
Did you ever manage to fix it?
Click to expand...
Click to collapse
Not no fix

Dark235 said:
Thank you very much for your answer I'll try.
Click to expand...
Click to collapse
Dark235 said:
Not no fix
Click to expand...
Click to collapse
Must have been pure luck on my end then

T9EX said:
Must have been pure luck on my end then
Click to expand...
Click to collapse
You have a rom to try.

Dark235 said:
You have a rom to try.
Click to expand...
Click to collapse
I don't quite follow. What exactly do you mean?

T9EX said:
I don't quite follow. What exactly do you mean?
Click to expand...
Click to collapse
You repair you note?

Dark235 said:
You repair you note?
Click to expand...
Click to collapse
Yes I did.

T9EX said:
Yes I did.
Click to expand...
Click to collapse
How did please help?

Dark235 said:
You repair you note?
Click to expand...
Click to collapse
Dark235 said:
How did please help?
Click to expand...
Click to collapse
Well first do you have a software on your computer that has the ability to compress .img files into .tar files? And I would personally recommend having 7zip/WinRAR that way you can actually access the .img files on the stock ROM

T9EX said:
Well first do you have a software on your computer that has the ability to compress .img files into .tar files? And I would personally recommend having 7zip/WinRAR that way you can actually access the .img files on the stock ROM
Click to expand...
Click to collapse
First. Stock ROM img to. Tar =. Tar flash odio?

MM Update (QI2) - TWRP Won't Install!!!

Hi,
I just got this phone (same phone I had to replace the one that died)::
Samsung Galaxy (SM-N910T) Note 4 (QualComm)
Marshmallow 6.0.1
It's Unlocked.
Anyway, before I could install TWRP so I could Root it, Android Firmware Updates started coming through. I figured let them install and that way I'd have them. I knew that if I tried to install them after installing TWRP, it would just replace TWRP anyway.
After the last Update, the Build is now...
Build #: MMB29M.N910T3UVU3EQI2
I have tried TWRP 3.0.2.0 & 2.8.7.0 and even PhilZ 6.59.0 but nothing will go on! Odin (latest and tried older one) starts to Flash it, it says "Recovery" and then it says, "FAIL".
I'm thinking it's gotta have something to do with the Updates to Marshmallow???
PLEASE HELP! I can't do anything that I need to do without it Rooted and I can't Root it without a Custom Recovery.
Thanks!
Dave

Zeuszoos said:
Hi,
I just got this phone (same phone I had to replace the one that died)::
Samsung Galaxy (SM-N910T) Note 4 (QualComm)
Marshmallow 6.0.1
It's Unlocked.
Anyway, before I could install TWRP so I could Root it, Android Firmware Updates started coming through. I figured let them install and that way I'd have them. I knew that if I tried to install them after installing TWRP, it would just replace TWRP anyway.
After the last Update, the Build is now...
Build #: MMB29M.N910T3UVU3EQI2
I have tried TWRP 3.0.2.0 & 2.8.7.0 and even PhilZ 6.59.0 but nothing will go on! Odin (latest and tried older one) starts to Flash it, it says "Recovery" and then it says, "FAIL".
I'm thinking it's gotta have something to do with the Updates to Marshmallow???
PLEASE HELP! I can't do anything that I need to do without it Rooted and I can't Root it without a Custom Recovery.
Thanks!
Dave
Click to expand...
Click to collapse
From what I know, the bootloader isn't locked but I recommend installing a KitKat bootloader Using this thread
https://forum.xda-developers.com/no...ws-want-to-downgrade-to-4-4-4-kitkat-t3447773
From there you can install TWRP and/or update to qg1, qe2, or older.

dottyparent said:
From what I know, the bootloader isn't locked but I recommend installing a KitKat bootloader Using this thread
https://forum.xda-developers.com/no...ws-want-to-downgrade-to-4-4-4-kitkat-t3447773
From there you can install TWRP and/or update to qg1, qe2, or older.
Click to expand...
Click to collapse
First, thank you for responding!
I used that page on my last Note 4 (it died, hardware failure), after I tried MM but hated the Ext SD handling and so I went back down to the T2 KK ROM on that page and it worked fine (I installed the entire ROM). But my replacement Note 4 that just arrived already had MM as I said and updated to a Build # I haven't seen.
But if you look at the Build #, T-Mobile seems to have (via the Updates) turned the phone into a "N910T3" instead of a "N910T". Weird! Especially since I'm with MetroPCS. Hahaha! They're owned by T-Mobile though, use the same Towers, etc..
Anyway, I'd like to try and stick with MM this time around.
But you did hit one of my grey areas.
Let me see if I understand you correctly... If I were to Flash just the KK BL, my phone would/would not continue to Boot into Marshmallow as it is now, if I Flashed nothing but that?
Or am I correct in saying that your method would mean taking the phone back, so that it would be running KitKat and then going back up to Marshmallow using a different ROM that TWRP will be able to go onto?
The reason I'm fuzzy, is because I've never Flashed just a BootLoader, so I'm not sure what would happen if I Flash just the KK BootLoader onto an MM ROM and Reboot???
Thank you again for your time!

Zeuszoos said:
First, thank you for responding!
I used that page on my last Note 4 (it died, hardware failure), after I tried MM but hated the Ext SD handling and so I went back down to the T2 KK ROM on that page and it worked fine (I installed the entire ROM). But my replacement Note 4 that just arrived already had MM as I said and updated to a Build # I haven't seen.
But if you look at the Build #, T-Mobile seems to have (via the Updates) turned the phone into a "N910T3" instead of a "N910T". Weird! Especially since I'm with MetroPCS. Hahaha! They're owned by T-Mobile though, use the same Towers, etc..
Anyway, I'd like to try and stick with MM this time around.
But you did hit one of my grey areas.
Let me see if I understand you correctly... If I were to Flash just the KK BL, my phone would/would not continue to Boot into Marshmallow as it is now, if I Flashed nothing but that?
Or am I correct in saying that your method would mean taking the phone back, so that it would be running KitKat and then going back up to Marshmallow using a different ROM that TWRP will be able to go onto?
The reason I'm fuzzy, is because I've never Flashed just a BootLoader, so I'm not sure what would happen if I Flash just the KK BootLoader onto an MM ROM and Reboot???
Thank you again for your time!
Click to expand...
Click to collapse
This method will turn your phone temporarily to a t2, of which a mm Rom will not boot. Since your goal is to have TWRP on a MM Rom, I would do the following:
1. Flash the t2 KK bootloader.
2. Find your appropriate KK bootloader (ie if you have a 910t find a 910t bootloader) and flash it
3. Flash TWRP
4. Flash a MM bootloader and modem.

dottyparent said:
This method will turn your phone temporarily to a t2, of which a mm Rom will not boot. Since your goal is to have TWRP on a MM Rom, I would do the following:
1. Flash the t2 KK bootloader.
2. Find your appropriate KK bootloader (ie if you have a 910t find a 910t bootloader) and flash it
3. Flash TWRP
4. Flash a MM bootloader and modem.
Click to expand...
Click to collapse
Is this a method you've tried B4?
I'll check out that thread and see if they've got an MM Modem too.
Isn't that the "EFS" part of a ROM? If so, there are EFS Backup apps. But they may require Root though.
TTYL

Zeuszoos said:
Is this a method you've tried B4?
I'll check out that thread and see if they've got an MM Modem too.
Isn't that the "EFS" part of a ROM? If so, there are EFS Backup apps. But they may require Root though.
TTYL
Click to expand...
Click to collapse
Yes I have tried this. I changed my phone from a trip to a t2 and back again.

dottyparent said:
This method will turn your phone temporarily to a t2, of which a mm Rom will not boot. Since your goal is to have TWRP on a MM Rom, I would do the following:
1. Flash the t2 KK bootloader.
2. Find your appropriate KK bootloader (ie if you have a 910t find a 910t bootloader) and flash it
3. Flash TWRP
4. Flash a MM bootloader and modem.
Click to expand...
Click to collapse
dottyparent said:
Yes I have tried this. I changed my phone from a trip to a t2 and back again.
Click to expand...
Click to collapse
There is an MM ROM that is Rooted and has TWRP built in, but I don't know if it would Flash over this with Odin or not
I am also considering trying the entire KK T2 ROM again to go down to KK and then Flashing that MM ROM.
It has both Odexed & DeOdexed. If I remember right, DeOdexed is the better choice, right?
Thanks for all your time and help!
Dave

Hi,
You know what's sad, is that if I could somehow Roog it without TWRP, then I could use the way awesome "Flashify" app to try to get TWRP on this phone! <lol>
Dave

dottyparent said:
From what I know, the bootloader isn't locked but I recommend installing a KitKat bootloader Using this thread
https://forum.xda-developers.com/no...ws-want-to-downgrade-to-4-4-4-kitkat-t3447773
From there you can install TWRP and/or update to qg1, qe2, or older.
Click to expand...
Click to collapse
dottyparent said:
Yes I have tried this. I changed my phone from a trip to a t2 and back again.
Click to expand...
Click to collapse
Could you please tell me where the files are that you used, so that I can have the exact same ones to work with? I looked at the link you provided, but I couldn't find just the BootLoader in it. I saw where someone requested just the BootLoader and Modem (you?) and "Trex888" said he would upload them right away and provide a link, but I did not see one ever posted. Just the link for the entire ROM.
Btw, in Odin, if you're Flashing only the BootLoader, do you use the "BL" button instead of the "AP" (formerly "PDA") button? What about just the Modem (thru Recovery?)?
I just tried Flashing the entire T2 KK ROM that I had used to go back from MM to KK on my first Note 4, but this one wouldn't take that either. It immediately said "FAIL".
I'm sorry if I'm a pain. It's just that I'm disabled and constantly laying on my side, so a laptop is out for regular use and so this phone is my main and only communication with the outside world. What I'm saying is that it's not a hobby phone and I have to get it right, because (see below). So I don't want to Flash something that may not do it, so I want to exactly match what you did.
You see, I can only sit up to Flash from Odin on my Windows computer with my phone cabled to it for just so long because of my condition.
Not your problem, I know. But I'm explaining it to you so that you can understand that I'm not just trying to be lazy. But instead, I need to make sure I do exactly what worked for you, with exactly those files, because if something goes wrong, it could take me days of short time computer access due to my situation (too much overwhelming pain) to figure it out and get it (hopefully) fixed. So you can see the importance, no doubt.
This phone right now (see Build #) says it's a T3, but whatever works.
Right now, it's without Recovery so I can't Root it, so I can't get Write access to my Ext SD, etc.. I need to Root!
Also, this T3 MM ROM is having issues with the Display. Sometimes it'll get all chopped up and I have to Reboot.
So anyway, I need to get this done and I would very much appreciate your further help!
Thank You!!!
Dave

Zeuszoos said:
Could you please tell me where the files are that you used, so that I can have the exact same ones to work with? I looked at the link you provided, but I couldn't find just the BootLoader in it. I saw where someone requested just the BootLoader and Modem (you?) and "Trex888" said he would upload them right away and provide a link, but I did not see one ever posted. Just the link for the entire ROM.
Btw, in Odin, if you're Flashing only the BootLoader, do you use the "BL" button instead of the "AP" (formerly "PDA") button? What about just the Modem (thru Recovery?)?
I just tried Flashing the entire T2 KK ROM that I had used to go back from MM to KK on my first Note 4, but this one wouldn't take that either. It immediately said "FAIL".
I'm sorry if I'm a pain. It's just that I'm disabled and constantly laying on my side, so a laptop is out for regular use and so this phone is my main and only communication with the outside world. What I'm saying is that it's not a hobby phone and I have to get it right, because (see below). So I don't want to Flash something that may not do it, so I want to exactly match what you did.
You see, I can only sit up to Flash from Odin on my Windows computer with my phone cabled to it for just so long because of my condition.
Not your problem, I know. But I'm explaining it to you so that you can understand that I'm not just trying to be lazy. But instead, I need to make sure I do exactly what worked for you, with exactly those files, because if something goes wrong, it could take me days of short time computer access due to my situation (too much overwhelming pain) to figure it out and get it (hopefully) fixed. So you can see the importance, no doubt.
This phone right now (see Build #) says it's a T3, but whatever works.
Right now, it's without Recovery so I can't Root it, so I can't get Write access to my Ext SD, etc.. I need to Root!
Also, this T3 MM ROM is having issues with the Display. Sometimes it'll get all chopped up and I have to Reboot.
So anyway, I need to get this done and I would very much appreciate your further help!
Thank You!!!
Dave
Click to expand...
Click to collapse
Okay. Here is what I did exactly.
Download my Files here: https://1drv.ms/f/s!AJEa3D0cBAhIbQ
Stock 910T files here https://androidfilehost.com/?w=files&flid=20602
i guess if you need any other stock files sammobile works.
This will reset your phone!
1) Odin flash the AOG1 file. this turns the phone into a t2 phone.
2) Odin the ANK4 rom. this returns the phone to a 910t.
3) Boot into the ANK4 rom and download the MM update. This should land you on the first MM update, EPE3
4) Flash TWRP, thourgh AP, which should work. Might as well flash superSU or magisk.
At this point i would wipe everything and install a custom rom, but you could update to a newer boot loader and modem using the BL and CP buttons, respectively.
hope this helps

dottyparent said:
Okay. Here is what I did exactly.
Download my Files here: https://1drv.ms/f/s!AJEa3D0cBAhIbQ
Stock 910T files here https://androidfilehost.com/?w=files&flid=20602
i guess if you need any other stock files sammobile works.
This will reset your phone!
1) Odin flash the AOG1 file. this turns the phone into a t2 phone.
2) Odin the ANK4 rom. this returns the phone to a 910t.
3) Boot into the ANK4 rom and download the MM update. This should land you on the first MM update, EPE3
4) Flash TWRP, thourgh AP, which should work. Might as well flash superSU or magisk.
At this point i would wipe everything and install a custom rom, but you could update to a newer boot loader and modem using the BL and CP buttons, respectively.
hope this helps
Click to expand...
Click to collapse
Thank you for responding!
The OG1 is the T2 ROM that I had just tried and reported that unlike my previous Note 4, it would not Flash on this one to turn it into a KK T2. I also tried the other 2 ROMS to no avail.
I think it's because this one says it's a T3.
Thanks,
Dave

Zeuszoos said:
Thank you for responding!
The OG1 is the T2 ROM that I had just tried and reported that unlike my previous Note 4, it would not Flash on this one to turn it into a KK T2. I also tried the other 2 ROMS to no avail.
I think it's because this one says it's a T3.
Thanks,
Dave
Click to expand...
Click to collapse
I'm sorry man I did everything that I could think of. I knew that the T3 had a few issues with bootloaders and downgrading and stuff, but wow, i didn't know about these issues. Good luck with trying something else then.

dottyparent said:
I'm sorry man I did everything that I could think of. I knew that the T3 had a few issues with bootloaders and downgrading and stuff, but wow, i didn't know about these issues. Good luck with trying something else then.
Click to expand...
Click to collapse
No, I'm sorry, but you have to give me the answer.
All seriousness aside, I depreciate all your effort.
I can only think of one thing left to try... Go to Sammy's site and get the Lollipop 5.1.1 ROM and see what happens. It can't hurt to try, right?
I'll let ya know what happens and thank you again!
Happy Thanksgiving!
Dave

dottyparent said:
I'm sorry man I did everything that I could think of. I knew that the T3 had a few issues with bootloaders and downgrading and stuff, but wow, i didn't know about these issues. Good luck with trying something else then.
Click to expand...
Click to collapse
Guess what? I decided to take a picture of my phone's screen after it Failed to let me Flash anything at all in Odin. I tried TWRP again and this time read what my phone responds with and it says the following:
Custom Binary (Recovery) Blocked By FRP LOCK
Does that mean anything to you?
TTYL

Zeuszoos said:
Guess what? I decided to take a picture of my phone's screen after it Failed to let me Flash anything at all in Odin. I tried TWRP again and this time read what my phone responds with and it says the following:
Custom Binary (Recovery) Blocked By FRP LOCK
Does that mean anything to you?
TTYL
Click to expand...
Click to collapse
Well I searched around XDA and it seems to be a problem exclusive to the T3. Try going to settings -> security and see if there is a option to disable resetting protection. Or see if there is a way to disable OEM locking. However it's probably not there. The only successful thread I found was this
https://forum.xda-developers.com/note-4/help/note-4-t-mobile-sm-n910t3-custom-binary-t3346840
---------- Post added at 07:28 PM ---------- Previous post was at 07:24 PM ----------
If all else doesn't work, perhaps you could repartition your phone. You need a pit file and a few ROMs

Zeuszoos said:
Hi,
I just got this phone (same phone I had to replace the one that died)::
Samsung Galaxy (SM-N910T) Note 4 (QualComm)
Marshmallow 6.0.1
It's Unlocked.
Anyway, before I could install TWRP so I could Root it, Android Firmware Updates started coming through. I figured let them install and that way I'd have them. I knew that if I tried to install them after installing TWRP, it would just replace TWRP anyway.
After the last Update, the Build is now...
Build #: MMB29M.N910T3UVU3EQI2
I have tried TWRP 3.0.2.0 & 2.8.7.0 and even PhilZ 6.59.0 but nothing will go on! Odin (latest and tried older one) starts to Flash it, it says "Recovery" and then it says, "FAIL".
I'm thinking it's gotta have something to do with the Updates to Marshmallow???
PLEASE HELP! I can't do anything that I need to do without it Rooted and I can't Root it without a Custom Recovery.
Thanks!
Dave
Click to expand...
Click to collapse
That's weird. I updated my N910T to EQI2 with Odin, rooted using CF-Auto-Root for N910T and then flashed TWRP 3.1.1 and I had no problems at all

dottyparent said:
I'm sorry man I did everything that I could think of. I knew that the T3 had a few issues with bootloaders and downgrading and stuff, but wow, i didn't know about these issues. Good luck with trying something else then.
Click to expand...
Click to collapse
ShaDisNX255 said:
That's weird. I updated my N910T to EQI2 with Odin, rooted using CF-Auto-Root for N910T and then flashed TWRP 3.1.1 and I had no problems at all
Click to expand...
Click to collapse
But you updated to it. From KK?
KK doesn't have it and it's not in downloadable ROMS.
But if MM is already on the phone (mine), then it has FRP. See my other response.
TTYL

Zeuszoos said:
But you updated to it. From KK?
KK doesn't have it and it's not in downloadable ROMS.
But if MM is already on the phone (mine), then it has FRP. See my other response.
TTYL
Click to expand...
Click to collapse
That's because I have a n910t not a t3

Zeuszoos said:
But you updated to it. From KK?
KK doesn't have it and it's not in downloadable ROMS.
But if MM is already on the phone (mine), then it has FRP. See my other response.
TTYL
Click to expand...
Click to collapse
I upgraded from LL. The device was running 5.0.1 and now has 6.0.1

dottyparent said:
Well I searched around XDA and it seems to be a problem exclusive to the T3. Try going to settings -> security and see if there is a option to disable resetting protection. Or see if there is a way to disable OEM locking. However it's probably not there. The only successful thread I found was this
https://forum.xda-developers.com/note-4/help/note-4-t-mobile-sm-n910t3-custom-binary-t3346840
---------- Post added at 07:28 PM ---------- Previous post was at 07:24 PM ----------
If all else doesn't work, perhaps you could repartition your phone. You need a pit file and a few ROMs
Click to expand...
Click to collapse
Thank you for looking! I found out what it is.
It's "Factory Reset Protection" (FRP)
What it does, is keep someone else from Factory Resseting your phone if they steal it. When they reset it, during setup, they have to type in the last Google Email and Password that the phone used, before they can set up theirs.
After reading that, I remembered having to put my Google Info in at two separate points and seeing it telling me to "Verify", but I was just blowing right through setup, not reading all of the small print. I mean hey, I had no idea that even existed and was just annoyed that I had to type the same thing twice!
It will only be found on phones that already have Lollipop and up on them out of the box and probably not all of them yet. And you don't have to worry about downloadable ROMS, so those who have phones that started with KitKat, or even early versions of Marshmallow 6.0 or 6.0.1 would not have seen this happen to them. Even those who updated to the same version of Mm that my phone has won't, if they started with KK or an older MM and then updated to it.
Again, this is something that your phone would have "Out of the Box" and the phone (not all) would have at least L on it.
Just FYI, it's not just Samsung, either.
Just FYI, I have confirmed this info. It is a fact.
Once I have an easy to do, working fix, hopefully without having to perform a Factory Reset, I will "Create A Thread" and as normal for me, write clear and easy, step by step (not leaving any out) instructions on how to "Unlock FRP" and then come back here and post a link to the thread. Hopefully this week.
This phone will not beat me!!!
TTYL
Dave

Stuck on the black screen - power on doesn't work, only Recovery and Download works

Hello.
I've been playing with some custom ROMs, recoveries, etc. on S10 SM-G973F. Every time something went wrong I was able to flash stock Android 11 ROM with Odin and run the system after that. But not anymore...
At this moment I have access to Recovery Mode (stock, TWRP, LineageOS... whichever I flash with Odin) and Download Mode. When I try to power on the phone with button or with an option Boot to System from Recovery the phone turns off and nothing else happens. Black screen only, no vibration, etc.
I tried to format data and cache in Stock Recovery and TWRP. I tried to flash many time, changed USB cable, change USB port... nothing helps.
What is strange that after I flash the stock recovery the phone boots one time displaying the unlocked bootloader warning, Samsung logo and Android robot icon with an Erasing sign... but just for a 1-2s, very short time. Before the problem occurred the Erasing took much much more time. After that one time I cannot make to display bootloader unlocked warning and Samsung logo any more, no matter which ROM or recovery I flash.

Maybe you can try installing the original firmware and start over again.

That is what I do in the first place, I try to flash the original firmware with Odin. I use the same files as before. The only difference I can see is that after the flashing the Erase progress was very long and now it is only 1-2s and the phone turns off.

Ok, I've found my mistake and a solution. I will post it here if anyone else has a similar problem.
So while I was playing with different ROMs one of them had an instruction to flash G973FXXSCFUH5-twrp_flashable.zip that included:
modem.bin
dt.img
dtbo.img
cm.bin
sboot.bin
up_param.bin
keystorage.bin
uh.bin
The zip included was to an older firmware G973FXXSCFUH5, while I was already on newer G973FXXSEFUJ2. But the TWRP that I used to flash the zip did not protest and the process finished well. Causing the problems above of course.
Don't know why but flashing the whole original G973FXXSEFUJ2 firmware with Odin was not enough. But when I flashed G973FXXSEFUJ2-twrp_flashable.zip from the TWRP worked and made the phone operational again.

hello, I am in the same situation after having wanted to install blastui I find myself with the possibility of starting only in dow load or in twrp. Can you help me

FabienGege said:
hello, I am in the same situation after having wanted to install blastui I find myself with the possibility of starting only in dow load or in twrp. Can you help me
Click to expand...
Click to collapse
0. Make sure your phone is charged!
1. Check your current SW# in Download mode (the number stands for the number or letter in firmware code, the 5th sign from the end in hexadecimal, for example SW# 14 is E in G973FXXSEFUJ2_G973FOXMEFUJ2)
2. Find the proper version of bootloader and modem in ....-twrp_flashable.zip format (check here: https://github.com/corsicanu/9820-bootloaders_and_modems/releases)
3. Flash and run TWRP recovery.
4. Flash the zip file from #2.
Flashing the stock firmware with Odin was not enough for me. Flashing with TWRP made the S10 back to alive.

.

Doman said:
0. Make sure your phone is charged!
1. Check your current SW# in Download mode (the number stands for the number or letter in firmware code, the 5th sign from the end in hexadecimal, for example SW# 14 is E in G973FXXSEFUJ2_G973FOXMEFUJ2)
2. Find the proper version of bootloader and modem in ....-twrp_flashable.zip format (check here: https://github.com/corsicanu/9820-bootloaders_and_modems/releases)
3. Flash and run TWRP recovery.
4. Flash the zip file from #2.
Flashing the stock firmware with Odin was not enough for me. Flashing with TWRP made the S10 back to alive.
Click to expand...
Click to collapse
Hello brother can you please explain it again to me? My English is terrible and i hope you understand that.

Mohammed_9564 said:
Hello brother can you please explain it again to me? My English is terrible and i hope you understand that.
Click to expand...
Click to collapse
There is not much more to explain, just follow the steps I pointed. If any of them are not clear enough just ask, but I tried to make them as simple as possible If your English is not to well just try to use Google Translator.

Doman said:
There is not much more to explain, just follow the steps I pointed. If any of them are not clear enough just ask, but I tried to make them as simple as possible If your English is not to well just try to
Doman said:
There is not much more to explain, just follow the steps I pointed. If any of them are not clear enough just ask, but I tried to make them as simple as possible If your English is not to well just try to use Google Translator.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Oh man Thanks a lot for your reply i actually managed to do it 2 days ago and it worked thanks to your help again, but i have another question if it's not too much trouble for you, how can i go back to the stock room ? Can i just do it via Odin or is there another way to do it.

Mohammed_9564 said:
Oh man Thanks a lot for your reply i actually managed to do it 2 days ago and it worked thanks to your help again, but i have another question if it's not too much trouble for you, how can i go back to the stock room ? Can i just do it via Odin or is there another way to do it.
Click to expand...
Click to collapse
Best way to go back to stock rom is simply flash it with Odin from original files available from Samsung, for example on SamMobile:
https://www.sammobile.com/samsung/galaxy-s10/firmware/#SM-G973F

Doman said:
Best way to go back to stock rom is simply flash it with Odin from original files available from Samsung, for example on SamMobile:
https://www.sammobile.com/samsung/galaxy-s10/firmware/#SM-G973
Click to expand...
Click to collapse
Thanks for the help brother I appreciate it

For months I've tried searching for a solution to fix my SM-N976U that stopped booting up. None of the symptoms shared fully matched what I was experiencing, so every fix I attempted didn't get her fully functioning again, eventually I gave up trying, stuffed the phone in a drawer and just bought another one. Today I stumbled upon your post and every symptom you described fit exactly with what happen to me, I mean to the T, minus the model and fw version. So I grabbed my SM-N976U one more time and followed your solution... and guess what??? I am now a proud owner of 2 note 10 plus'!!!
Thank you so much for taking the time to share your experience and solution!! Cheers to you bud! Have a great New Year!

Thank you~! my s10 plus is back!