Related
Hello everyone,
I'm a new poster here at XDA , and I've gotten myself into a bit of a predicament. If there are any rules that I happened to skim over that are broken, please let me know! I have performed a search of my issue, but no solution has been procured from what I can tell.
For three days now, I've been trying to fix my phone. Stats below:
Model: SGH-I337 (AT&T Galaxy S4)
Build Number: JSS15J.I337UCUEMK2
OS: 4.3 (JB)
I believe that's all that needs to be listed, I'll be able to provide more information upon request if necessary.
I'll try to shorten my story to the key elements: Less than a week ago I tried to root, unlock, and flash a custom ROM to my S4 to no avail. I completed the rooting successfully and I believe I may have bypassed unlocking it via LOKI, but the ROM did not install. Since that failed, I've been trying for three days to completely restore my phone to stock and just deal with Samsung's TouchWiz UI. I can flash (through ODIN) my phone to stock 4.3 and everything is fine except for a lack of WiFi and Data. This is where my conundrum comes in to play.
Knox seems to display a message stating "The device has detected an application attempting to perform actions that are not permitted. These actions have been blocked. It is recommended that you restart your device." anytime that I attempt to turn WiFi on. The widget and the setting in options will attempt to turn on for a split second and turn off prior to displaying this security message. It's as if Knox believes my WiFi is attempting to access parts of my phone that are restricted. My data is able to be turned on in the settings, but no 3g/4g is ever utilized. I figured an update off of 4.3 would help remedy this issue, but I can't seem to update my phone through any other means (ODIN, Kies, no OTA due to no WiFi/Data, etc.).
I've run out of different combinations of the keywords about my problem to search for in Google and any question about my problem was asked approximately April-October 2013, not answered, and not many more similar questions have risen since then.. which leads me to believe that this fix should be relatively easy.
On an S3 forum thread (I know, different device) I read that there could be corruption of my Nandroid system, but I'm not even sure what that entails. The user answering implied that the phone was done for. Again, though, this was a separate thread for another user about a Galaxy S3.
Well, apologies for the wall of text, folks. If you are willing to assist me, I would very much appreciate it. Thank you very much for reading my issue and I hope assistance can be organized.
What did you use to get back to stock
Sent from my SAMSUNG-SGH-I337 using Tapatalk
seedeh said:
What did you use to get back to stock
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
I used ODIN to flash (What I'm very confident is) 4.3 Stock in the same manner I flashed the custom ROM.
I feel like that isn't specific enough for you though. I used Odin3 v3.09 first and then after several failures switched to Odin3 v1.85 as demonstrated in a few tutorials I've seen.
Did you use this tutorial?: http://forum.xda-developers.com/showthread.php?t=2621279 cause if you didn't, do.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
seedeh said:
Did you use this tutorial?: http://forum.xda-developers.com/showthread.php?t=2621279 cause if you didn't, do.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
Let me attempt this thread's instructions before I make more of a fool of myself. Thank you for the assistance so far. I really appreciate it.
No problem
Sent from my SAMSUNG-SGH-I337 using Tapatalk
seedeh said:
No problem
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
Seedeh,
The errors still continued as usual even with the explicit following of the linked directions. It appears that during the process:
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> sbl1.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl2.mbn
<ID:0/007> sbl3.mbn
<ID:0/007> rpm.mbn
<ID:0/007> aboot.mbn
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
that the "NAND Write Start" step isn't really even trying to write before it fails.
Kies "Emergency Firmware Recovery" also yields no success due to "Firmware emergency recovery stopped due to GALAXY S4(SGH-I337) error. If the problem persists, please contact the Samsung service centre.", which does persist each time I attempt to do so.
If you have any more suggestions, I'd be more than happy to attempt them.
Thank you.
AmpGuitarChase said:
Hello everyone,
I'm a new poster here at XDA , and I've gotten myself into a bit of a predicament. If there are any rules that I happened to skim over that are broken, please let me know! I have performed a search of my issue, but no solution has been procured from what I can tell.
For three days now, I've been trying to fix my phone. Stats below:
Model: SGH-I337 (AT&T Galaxy S4)
Build Number: JSS15J.I337UCUEMK2
OS: 4.3 (JB)
I believe that's all that needs to be listed, I'll be able to provide more information upon request if necessary.
I'll try to shorten my story to the key elements: Less than a week ago I tried to root, unlock, and flash a custom ROM to my S4 to no avail. I completed the rooting successfully and I believe I may have bypassed unlocking it via LOKI, but the ROM did not install. Since that failed, I've been trying for three days to completely restore my phone to stock and just deal with Samsung's TouchWiz UI. I can flash (through ODIN) my phone to stock 4.3 and everything is fine except for a lack of WiFi and Data. This is where my conundrum comes in to play.
Knox seems to display a message stating "The device has detected an application attempting to perform actions that are not permitted. These actions have been blocked. It is recommended that you restart your device." anytime that I attempt to turn WiFi on. The widget and the setting in options will attempt to turn on for a split second and turn off prior to displaying this security message. It's as if Knox believes my WiFi is attempting to access parts of my phone that are restricted. My data is able to be turned on in the settings, but no 3g/4g is ever utilized. I figured an update off of 4.3 would help remedy this issue, but I can't seem to update my phone through any other means (ODIN, Kies, no OTA due to no WiFi/Data, etc.).
I've run out of different combinations of the keywords about my problem to search for in Google and any question about my problem was asked approximately April-October 2013, not answered, and not many more similar questions have risen since then.. which leads me to believe that this fix should be relatively easy.
On an S3 forum thread (I know, different device) I read that there could be corruption of my Nandroid system, but I'm not even sure what that entails. The user answering implied that the phone was done for. Again, though, this was a separate thread for another user about a Galaxy S3.
Well, apologies for the wall of text, folks. If you are willing to assist me, I would very much appreciate it. Thank you very much for reading my issue and I hope assistance can be organized.
Click to expand...
Click to collapse
Loki is for MF3 not for MK2. So you should just Odin back to stock. Here are the tar files.
http://forum.xda-developers.com/showthread.php?t=2621279.
If that didn't work, then follow ted77USA's guide.
Once you are back on Stock MK2 firmware, here are your options. Have a good read of this guide.
http://forum.xda-developers.com/showthread.php?t=2616221
Be sure to thank the op in the threads that help you & of the developers of the roms you flash. Good luck :fingers-crossed: & remember, reading saves phones.
John The Rhino said:
Loki is for MF3 not for MK2. So you should just Odin back to stock. Here are the tar files.
http://forum.xda-developers.com/showthread.php?t=2621279.
If that didn't work, then follow ted77USA's guide.
Once you are back on Stock MK2 firmware, here are your options. Have a good read of this guide.
http://forum.xda-developers.com/showthread.php?t=2616221
Be sure to thank the op in the threads that help you & of the developers of the roms you flash. Good luck :fingers-crossed: & remember, reading saves phones.
Click to expand...
Click to collapse
John The Rhino,
Thank you for you assistance. I will surely give credit where credit is due
I've attempted the XDA Full Odin Tar MK2 link's instructions three times on two separate computers (one w8 and one w7) to no avail. I've triple-checked the instructions, but my Odin always fails when attempting to Complete(Write).
NAND Write Start!
sbl2.mbn
sbl3.mbn
rpm.mbn
aboot.mbn
Complete(Write) Operation Failed
All threads completed. (succeed 0 / failed 1)
Odin settings: Auto Reboot checked, F. Reset Time checked, PDA = I337MK2_Full_Odin_Tar.tar file, nothing else is checked.
Device: Dev mode activated, USB debugging active, this is all verified after a recovery-initiated factory reset, device is in download mode.
Computer(s): Samsung Android ADB Interface drivers are installed, Odin does show a yellow bar upon device connection. MicroUSB cable is the default one that came with the device, all USB ports have been tried with the same results.
I tried to be as thorough as possible with my setup. I'll see if my process is correct now just in case that will help.
[Fixing Device to Working Status w/o wifi/data permissions] Flashed AP_I337UCUEMK2_1921628_REV06_user_low_ship_MULTI_CERT.tar.md5 via Odin
Automatic Reboot via Odin
[Device is back to working status w/o data/wifi permissions (No reset has been done)]
Power off
Reboot in Recovery Mode (Volume up + Home + Power)
Wipe data/factory reset command
Wipe cache (just in case)
Reboot
[Phone is now factory reset 4.3 MK2 (WiFi/Data permissions denied still]
Enable developer options
Enable USB debugging and Screen Stay Awake during charging
Power off
Boot into download mode (Volume down + Home + Power)
Open Odin3 v1.85
Bar in Odin for COM Port is yellow
Auto reboot & F. Reset Time are both checked
Load I337MK2_Combined_Odin_Tar\I337MK2_Full_Odin_Tar.tar.md5 in PDA slot
Screenshot of Odin before "START" http://i.imgur.com/oXufVNQ.png
Odin START
Wait for Odin to check .md5 compatibility
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MK2_Full_Odin_Tar.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl2.mbn
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> aboot.mbn
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Back to where these points began
Apologies for the length, but again I wanted to be as thorough as possible. My WiFi still won't turn on due to permissions issues and Data is on, but no 3g/4g/LTE comes through.
Surely I'm just missing an essential step or two.
Can you offer any further advice on this matter?
Odin can be finicky, try different usb ports, 2.0 not 3.0, and make sure you're using the cable that came with your device. I don't see that your doing anything wrong, keep trying.
Sent from my Nexus 5
The bootloader on MK2 and later is encrypted and without the key it will always fail. ODIN sees the ABOOT is locked and cannot flash the complete image. AT&T and Verizon have chosen this method to keep you off their cheaper competitors. I had to take my I337 to Best Buy Samsung experience to have it re flashed so that it would boot after a refused OTA from MDL and now it is a paperweight.
jd1639 said:
Odin can be finicky, try different usb ports, 2.0 not 3.0, and make sure you're using the cable that came with your device. I don't see that your doing anything wrong, keep trying.
Sent from my Nexus 5
Click to expand...
Click to collapse
I don't think Odin is the issue as it flashes what I like to call "The cure-firmware" .md5 AP_I337UCUEMK2_1921628_REV06_user_low_ship_MULTI_CERT.tar.md5) file just fine every time with no issues with Odin. Only when I try to flash that file, it works. I wish there was a way to tell what exactly is going wrong with the other files. I also can't seem to find where I located this file, but whatever it's doing works on my S4. I'd like to find either a 4.2.2 or 4.4.2 version of this stock OS that would work.
I'm beginning to wonder if it'd be more worthwhile to reroot, reset the flag binary counter, reset, and drive an hour and a half away to the closest AT&T store and see if they can fix my device. Does this sound like it may be my best course of action?
Again, thanks for all the help guys. I means a lot.
There is no way to downgrade to 4.2.2 from MK2. The bootloader is locked. Read the guide for MK2 it will help you.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
---------- Post added at 11:09 AM ---------- Previous post was at 11:04 AM ----------
Check your APN settings re enter according to correct settings posted on XDA.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Hey guys,
Solution confirmed!
I remedied the situation by flashing an NB1 firmware on the device. I'm aware that this firmware has a locked bootloader, but Loki is evidently a solution to that problem. I'll cross that bridge eventually when I cross it.
You guys are terrific and I really appreciate all the assistance that you've offered.
Take care.
AmpGuitarChase said:
Hey guys,
Solution confirmed!
I remedied the situation by flashing an NB1 firmware on the device. I'm aware that this firmware has a locked bootloader, but Loki is evidently a solution to that problem. I'll cross that bridge eventually when I cross it.
You guys are terrific and I really appreciate all the assistance that you've offered.
Take care.
Click to expand...
Click to collapse
Loki does not work with MF3 and up
Congrats!
Sent from my SAMSUNG-SGH-I337 using Tapatalk
AmpGuitarChase said:
Hey guys,
Solution confirmed!
I remedied the situation by flashing an NB1 firmware on the device. I'm aware that this firmware has a locked bootloader, but Loki is evidently a solution to that problem. I'll cross that bridge eventually when I cross it.
You guys are terrific and I really appreciate all the assistance that you've offered.
Take care.
Click to expand...
Click to collapse
Don't flash Loki to your phone, as it's only for MF3 not MK2 or above. You need to read the guide, which obviously you still haven't or you wouldn't be talking about flashing Loki on the new 4.4.2 Kit Kat firmware. Reading saves phones!
John The Rhino said:
Don't flash Loki to your phone, as it's only for MF3 not MK2 or above. You need to read the guide, which obviously you still haven't or you wouldn't be talking about flashing Loki on the new 4.4.2 Kit Kat firmware. Reading saves phones!
Click to expand...
Click to collapse
John The Rhino,
Thank you for the advice. I posted in a hurry earlier out of excitement and stated the incorrect method as you've pointed out. I'll be sure to be extremely thorough in the future when I decide to flash new software to my device. You've been a tremendous help and it is greatly appreciated.
Take care until my next issue. Haha.
Chase
AmpGuitarChase said:
John The Rhino,
Thank you for the advice. I posted in a hurry earlier out of excitement and stated the incorrect method as you've pointed out. I'll be sure to be extremely thorough in the future when I decide to flash new software to my device. You've been a tremendous help and it is greatly appreciated.
Take care until my next issue. Haha.
Chase
Click to expand...
Click to collapse
You're welcome. I'm glad it all worked out for you. As they say in the construction business, measure twice, cut once. Well same here, except I'd recommend as do others to read thrice (3x) FLASH once. Then you'll rarely have issues. Enjoy.
i337 same issue as original post
i have done the same research as posted in this link and read exhaustively every means google XDA and all the other pages dealing with rooting and flashing my AT&T s4 i337. I have ended up in the same boat as this guy with:
Baseband version - I337UCUFNB1
Build Number - JSS15J.I337UCUEMK2
i have attempted Kingo Loki, Motochopper, Odin(4 or 5 versions) adb flash in Linux(2 builds) and Winblows 7. My original desire was to have this build
https://www.youtube.com/watch?v=mJLKX_QWSpc
which got my hopes up immensely, as having wasted days upon days several times over the course of the last 9 months rooting this i337. The guy in the vid says he was able to get UT up and running following guidance from XDA. I want to be able to flash a twrp-like dual boot recovery to my device maintaining Andy functionality using UT as a daily driver.
I have read, as reading saves phones, everything I can glean from the aforementioned posts and forms, researched this thing to death and neded up with a phone with the knox-? security message listed in the original post. I have no Idea where to go from here, but know you guys do, as like a myriad of others, I worship this site like a god.
Please help an old retired disabled veteran of most of the sandy wars in the past 25 years. All I have now are my devices which bring me some comfort to my days.
I really need your help, as I've tried seemingly all and have a semi-dead i337.
buxtor, aka, Chief
Hello friends
Have a question
I am using s5 sm g900h indian variant
I am on indian rom right now but i want to try latest 4.4.2 which is in indonesia so can i flash indonesian rom on my variant or should i wait for my update
No, you can't do that. This will brick your phone..
Wait for your regional update..
sharingan said:
I am using s5 sm g900h indian variant
I am on indian rom right now but i want to try latest 4.4.2 which is in indonesia so can i flash indonesian rom on my variant or should i wait for my update
Click to expand...
Click to collapse
You should probably wait for an update from your carrier.
Flashing the actual Indonesian ROM as you proposed is problematic. It can be done, provided that the ROM is intended for the same model of phone i.e. 900H. To do it properly, you need to also flash the proper PIT file at the same time to guard against possible partition corruption. So if your phone is e.g. a 16 GB 900H, you need to use a PIT file from a 16 GB 900H that already has firmware installed from the Indonesian carrier. If you flash without the appropriate PIT file, you may well brick your phone as the poster above cited.
Another possibility is changing your CSC to another local carrier that is already rolling out the OTA update. That would likely be compatible but no one will guarantee it as that specific update may depend upon a carrier specific firmware base. Also if you change your CSC from the Android UI, it will insist on wiping your user data, so you'd need to use an app or manually change the CSC code if that matters to you.
.
fffft said:
You should probably wait for an update from your carrier.
Flashing the actual Indonesian ROM as you proposed is problematic. It can be done, provided that the ROM is intended for the same model of phone i.e. 900H. To do it properly, you need to also flash the proper PIT file at the same time to guard against possible partition corruption. So if your phone is e.g. a 16 GB 900H, you need to use a PIT file from a 16 GB 900H that already has firmware installed from the Indonesian carrier. If you flash without the appropriate PIT file, you may well brick your phone as the poster above cited.
Another possibility is changing your CSC to another local carrier that is already rolling out the OTA update. That would likely be compatible but no one will guarantee it as that specific update may depend upon a carrier specific firmware base. Also if you change your CSC from the Android UI, it will insist on wiping your user data, so you'd need to use an app or manually change the CSC code if that matters to you.
.
Click to expand...
Click to collapse
Okk then
I will wait for my update
I have cross flashed from different regions without issues.
What issues did you guys have when flashing a different region firmware? It should be good as long as it is for G900H
fffft said:
Flashing the actual Indonesian ROM as you proposed is problematic. It can be done, provided that the ROM is intended for the same model of phone i.e. 900H. To do it properly, you need to also flash the proper PIT file at the same time to guard against possible partition corruption. So if your phone is e.g. a 16 GB 900H, you need to use a PIT file from a 16 GB 900H that already has firmware installed from the Indonesian carrier. If you flash without the appropriate PIT file, you may well brick your phone
Click to expand...
Click to collapse
drakester09 said:
What issues did you guys have when flashing a different region firmware? It should be good as long as it is for G900H
Click to expand...
Click to collapse
If you had read either of the two posts above yours, you would have found an answer to your question.
Having made a handful of working flashes does not equate to a guarantee that it will work in all situations and cases. You are encouraging people to put their phones at risk. Your statement that it should be good as long as it is for a 900H is demonstrably wrong.
It does not always work. You've merely been lucky so far.
.
fffft said:
If you had read either of the two posts above yours, you would have found an answer to your question.
Having made a handful of working flashes does not equate to a guarantee that it will work in all situations and cases. You are encouraging people to put their phones at risk. Your statement that it should be good as long as it is for a 900H is demonstrably wrong.
It does not always work. You've merely been lucky so far.
.
Click to expand...
Click to collapse
The condescending tone of yours is ill fitted to this conversation.
I read your post, now could you be so kind to actually read mine?
What issues did you guys have when flashing a different region firmware?
Click to expand...
Click to collapse
Can you please share some cases where this has happened?
Where it has been stated and proven that CSC differences can risk your phone?
If so then the CSC changer app is a risk and should be removed, but it isn't.
We are not talking about variants, of course T/L/S/F are not the same despite haviing Snapdragon and you might break something when cross flashing, basebands are different, etc etc.
All G900Hs are equal. The software that was built for one G900H will work in another.
The carrier/regional customizations COULD cause issues if there's a certain incompatibility between app data, but they are easily fixed by a wipe.
For once the PIT argument is useless, Odin pulls the current PIT from your phone to map partitions.
In old days the update was not as seamless and you might be forced to use a PIT file. That's not the case for current releases.
drakester09 said:
The condescending tone of yours is ill fitted to this conversation.
Click to expand...
Click to collapse
Uh huh. You give no rationale for encouraging people to do something very risky. One doesn't have to search very far in the forum to find people that have bricked phones doing what you suggest. Your last post at last offers an elaboration in which we find you relying upon several factual errors. Leaving me no choice but to disagree with you about about who is being condescending.
Firmware is installed as a set of partitioned images. In particular hidden.img contains carrier specific items in a partition that is known to vary in size amongst some carriers. There are numerable and repeatable cases of people flashing firmware from another carrier bricking their phones.
As you say, if you provide no explicit PIT file, Odin will map the partitions by drawing the current PIT from your phone. And that is exactly what corrupts partitions if the new firmware expects a larger partition for hidden.img. The existing PIT is not accurate for a new firmware image that requires a larger partition. And not surprisingly, corrupt partitions can amount to a bricked phone.
Anyone following your advice is playing Russian roulette with their phone. Sometimes it will work. And sometimes your advice will brick their phone.
.
.
fffft said:
Uh huh. You give no rationale for encouraging people to do something very risky. One doesn't have to search very far in the forum to find people that have bricked phones doing what you suggest. Your last post at last offers an elaboration in which we find you relying upon several factual errors. Leaving me no choice but to disagree with you about about who is being condescending.
Firmware is installed as a set of partitioned images. In particular hidden.img contains carrier specific items in a partition that is known to vary in size amongst some carriers. There are numerable and repeatable cases of people flashing firmware from another carrier bricking their phones.
As you say, if you provide no explicit PIT file, Odin will map the partitions by drawing the current PIT from your phone. And that is exactly what corrupts partitions if the new firmware expects a larger partition for hidden.img. The existing PIT is not accurate for a new firmware image that requires a larger partition. And not surprisingly, corrupt partitions can amount to a bricked phone.
Anyone following your advice is playing Russian roulette with their phone. Sometimes it will work. And sometimes your advice will brick their phone.
.
.
Click to expand...
Click to collapse
I crossflashed numerous factory roms with Odin on my S/S2/S3/S4/S5 and Note/2/3 from various (European) country`s and never had a issue with pit files ans csc files to be honest. Can`t imagine beeing luky like that all the time every time.
gee2012 said:
Can`t imagine beeing luky like that all the time every time.
Click to expand...
Click to collapse
That you cannot imagine it does not make it any less true. To argue so is a non sequitur, a formal error of logic or logical fallacy referred to as an Appeal to Probability.
Instead of trying to convince us that there is no risk because the particular carrier's you have flashed worked, address the facts. Show a factual error in the thesis e.g. that hidden partition must be an invariant size, that partitions can be overwritten with impunity or why firmware corruption cannot brick a phone.
Constructive arguments based on facts and structured reasoning would be welcome. If you can demonstrate that this information is incorrect and provide a better explanation, great. Unsupported statements that you don't think that it is, not so much.
If you wish to defend an unsupported assertion that it doesn't make sense to you, then you are welcome to have the last word and readers can draw their own conclusions. Given the notable lack of a fact based discussion in this thread, it isn't constructive to pursue it further.
.
fffft said:
That you cannot imagine it does not make it any less true. To argue so is a non sequitur, a formal error of logic or logical fallacy referred to as an Appeal to Probability.
Instead of trying to convince us that there is no risk because the particular carrier's you have flashed worked, address the facts. Show a factual error in the thesis e.g. that hidden partition must be an invariant size, that partitions can be overwritten with impunity or why firmware corruption cannot brick a phone.
Constructive arguments based on facts and structured reasoning would be welcome. If you can demonstrate that this information is incorrect and provide a better explanation, great. Unsupported statements that you don't think that it is, not so much.
If you wish to defend an unsupported assertion that it doesn't make sense to you, then you are welcome to have the last word and readers can draw their own conclusions. Given the notable lack of a fact based discussion in this thread, it isn't constructive to pursue it further.
.
Click to expand...
Click to collapse
Lets agree to disagree. Imo you don`t have to flash a pit file if you flash a compatible rom for your model with the same partition layout (16 or 32GB) everytime you flash a stock rom.
PS saw earlier posts by you and i want to point out none of my my advices/posts ever lead to a bricked device
fffft said:
That you cannot imagine it does not make it any less true. To argue so is a non sequitur, a formal error of logic or logical fallacy referred to as an Appeal to Probability.
Instead of trying to convince us that there is no risk because the particular carrier's you have flashed worked, address the facts. Show a factual error in the thesis e.g. that hidden partition must be an invariant size, that partitions can be overwritten with impunity or why firmware corruption cannot brick a phone.
Constructive arguments based on facts and structured reasoning would be welcome. If you can demonstrate that this information is incorrect and provide a better explanation, great. Unsupported statements that you don't think that it is, not so much.
If you wish to defend an unsupported assertion that it doesn't make sense to you, then you are welcome to have the last word and readers can draw their own conclusions. Given the notable lack of a fact based discussion in this thread, it isn't constructive to pursue it further.
.
Click to expand...
Click to collapse
I'm sorry to be a bother but could you please share any case where the mentioned situation has happened?
There must be at least one or several.
I'm all in for factual data so I'd love to see real scenarios where this has happened. It will take you much less time than to post such a long winded post and will prove your point.
Thanks in advance.
gee2012 said:
I crossflashed numerous factory roms with Odin on my S/S2/S3/S4/S5 and Note/2/3 from various (European) country`s and never had a issue with pit files ans csc files to be honest. Can`t imagine beeing luky like that all the time every time.
Click to expand...
Click to collapse
Exactly. Even I've done it like number of times. No issues whatsoever. Although I take care it's the correct model, I don't really bother about region.
drakester09 said:
I have cross flashed from different regions without issues.
What issues did you guys have when flashing a different region firmware? It should be good as long as it is for G900H
Click to expand...
Click to collapse
Sent from 5th Galaxy
How did you cross flash i got G900P i want to flash G900WD how ?
Hi . I have a S5 G900F. I had Alliance rom until recently I decided to bring it back to stock. So i downloaded the european firmware from sammobile.com and flashed it via mobile odin but now my phone is bricked. Another problem is that I cant flash any firmware or custom rom via pc odin it fails. when I press start these commands appear on the lower left corner
<ID:0/015> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900FXXU1ANG2_G900FOXA1ANG3_G900FXXU1ANG2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> SingleDownload.
<ID:0/015> aboot.mbn
<ID:0/015> NAND Write Start!!
<ID:0/015> FAIL! (Auth)
<ID:0/015>
<ID:0/015> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I also cant flash anything from recovery beacause when I to go recovery mode these lines are wriiten in red colour
E: unable to mount /system
E; unable to mount /sd card.
Can anyone help me please.
One more thing I ordered the mobile from an online store so I dont know the region of my mobile. on the back, under the battery it says made in vietnam.
waleed794 said:
Hi . I have a S5 G900F. I had Alliance rom until recently I decided to bring it back to stock. So i downloaded the european firmware from sammobile.com and flashed it via mobile odin but now my phone is bricked. Another problem is that I cant flash any firmware or custom rom via pc odin it fails. when I press start these commands appear on the lower left corner
<ID:0/015> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900FXXU1ANG2_G900FOXA1ANG3_G900FXXU1ANG2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> SingleDownload.
<ID:0/015> aboot.mbn
<ID:0/015> NAND Write Start!!
<ID:0/015> FAIL! (Auth)
<ID:0/015>
<ID:0/015> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I also cant flash anything from recovery beacause when I to go recovery mode these lines are wriiten in red colour
E: unable to mount /system
E; unable to mount /sd card.
Can anyone help me please.
One more thing I ordered the mobile from an online store so I dont know the region of my mobile. on the back, under the battery it says made in vietnam.
Click to expand...
Click to collapse
Im have the same problem!
Im have a S5 SM-G900M and try install G900F and have the same error.
Is possible install this?
Hello friends i have s5 4g vession G900I how can i enable 4g .i can see only WCDMA/GSMA i din't find LTE/4G in the settings
Sent from my SM-G900I using XDA Free mobile app
sandeep20064096 said:
Hello friends i have s5 4g vession G900I how can i enable 4g .i can see only WCDMA/GSMA i din't find LTE/4G in the settings
Sent from my SM-G900I using XDA Free mobile app
Click to expand...
Click to collapse
Hi.
Im think your phone have a different chip
For example the difference into g900m and the g900f is the bands avaible
The g900m have only 900Mhz / 1800Mhz
The g900f have all bands
But in try install the firmware g900f into g900m but dont work.
please help
walkermoon said:
Exactly. Even I've done it like number of times. No issues whatsoever. Although I take care it's the correct model, I don't really bother about region.
Sent from 5th Galaxy
Click to expand...
Click to collapse
i want to flash newest cambodia ROM to my S5 g900h ... so can i do it easily with odin or i want to change moedm firmware and bootloader first ?? and please help me ASAP
i rooted my S5 and i flash the recovery. but now it has error that it could not run cache partition ...
so i want to go back to stock ... tell me if i have to go to direct cambodia ROM or i have to flash india ROM first ??
please help me with this
Hi Everyone! I've been looking for a way to fix this and have been to a LOT of other Forums about this, but I didn't find anything relating to my problem. I hope you guys could help me
I have a Samsung Galaxy Grand Prime (SM-G530H) running on Lollipop 5.0.2
And a TWRP custom recovery and had it rooted for a bunch of things, but nothing really fancy.
Let me tell you what happened...
Three days ago I was looking through my phone's settings and saw an ENCRYPTION function that I could use to protect my phone.
It somehow looked promising for some reason and it said it would take an hour or more to finish the encryption. So I tried it.
Then hours had past until it took the whole day, I assumed that it might have froze so it made me worry a lot. So I Removed The Battery just to stop it and tried to boot and this message appeared, "ENCRYPTION FAILED" and told me to wipe my data and I did. (I'm actually past this message because I wiped the Dalvik Cache, System, Cache, Data, and Internal Storage [Not External Storage]. That's where the "NO OS Installed showed up". So I tried to do some firmware flashing.)
The next problem was I can't seem to Flash my Stock Rom using Odin neither TWRP, both of them keeps giving me big "FAIL!" messages that I can't figure out what wrong things I did.
Here's what my phone is saying
https://drive.google.com/open?id=0B47QYMfr69HwazU1c2NmZWxyV2c
Here's what Odin keeps saying
https://drive.google.com/open?id=0B47QYMfr69HwRklnU3VpTFFVVU0
I don't have a lot of tools and methods at hand to try right now, but I do have Odin v3.10, TWRP 2.8.7, and my Download Mode is still working and some stock roms I saved as backup.
I would appreciate any help given in an easy to understand way. Thanks
(EDIT) Hi guys! Gladly my phone is fixed by that technician so no need to see this thread haha
The Audiophile said:
Hi Everyone! I've been looking for a way to fix this and have been to a LOT of other Forums about this but I really haven't found anything. I hope you guys could help me
I have a Samsung Galaxy Grand Prime (SM-G530H) running on Lollipop 5.0.2
And a TWRP custom recovery and had it rooted for a bunch of things, but nothing really fancy.
Let me tell you what happened...
Three days ago I was looking through my phone's settings and saw an ENCRYPTION function that I could use to protect my phone.
It somehow looked promising for some reason (My worst Idea EVER) and it said it would take an hour or more to finish the encryption. So I tried it.
Then hours had past until it took the whole day, I assumed that it might have froze so it made me worry a lot. So I Removed The Battery just to stop it and tried to boot and this message appeared, "ENCRYPTION FAILED" and told me to wipe my data and I did. (I'm actually past this message because I wiped the Dalvik Cache, System, Cache, Data, and Internal Storage [Not External Storage]. That's where the "NO OS Installed showed up". So I tried to do some firmware flashing.)
The next problem was I can't seem to Flash my Stock Rom using Odin neither TWRP, both of them keeps giving me big "FAIL!" messages that I can't figure out what wrong things I did.
Here's what Odin's saying:
<ID:0/011> Added!!
<ID:0/011> Odin engine v(ID:3.1005)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialization..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> SingleDownload.
<ID:0/011> aboot.mbn
<ID:0/011> NAND Write Start!!
<ID:0/011> FAIL!! (Auth)
<ID:0/011>
<ID:0/011> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I don't have a lot of tools at hand to try right now, but I do have Odin v3.10, TWRP 2.8.7, and my Download Mode is still working and some stock roms I saved as backup.
I would appreciate any help given in an easy to understand way. Thanks
Click to expand...
Click to collapse
Hello,
Thanks for using XDA Assist.
"FAIL (AUTH)" in your Odin means that the downloaded firmware is not compatible with your device.Try to flash the firmware of your region.
___
v7
XDA Assist
v7 said:
Hello,
Thanks for using XDA Assist.
"FAIL (AUTH)" in your Odin means that the downloaded firmware is not compatible with your device.Try to flash the firmware of your region.
___
v7
XDA Assist
Click to expand...
Click to collapse
Hi v7! Thanks, but your suggestion didn't work. My phone's region is XSE (Indonesia) and my firmware backup doesn't seem to work at all. I still get the same "FAIL (Auth)" message after trying a lot of times
The Audiophile said:
Hi v7! Thanks, but your suggestion didn't work. My phone's region is XSE (Indonesia) and my firmware backup doesn't seem to work at all. I still get the same "FAIL (Auth)" message after trying a lot of times
Click to expand...
Click to collapse
Did you try the Indonesian firmware?
___
v7
XDA Assist
v7 said:
Hello,
Thanks for using XDA Assist.
"FAIL (AUTH)" in your Odin means that the downloaded firmware is not compatible with your device.Try to flash the firmware of your region.
___
v7
XDA Assist
Click to expand...
Click to collapse
v7 said:
Did you try the Indonesian firmware?
___
v7
XDA Assist
Click to expand...
Click to collapse
Yes, I did but it didn't work. I'm not sure what I did wrong, that firmware's version was 4.4 (KitKat). But I upgraded to 5.0.2 (Lollipop) which was from Uzbekistan before I tried the encryption function
And I'm sort of freaking out since this is the only phone I have and it's been a week since I had this problem
And I might bring my phone to a technician tomorrow. Is there something I haven't tried to fix my phone within my powers? Any suggestions would be helpful enough. Thanks guys!:good:
sama gan gimana ya fix nya?
Hey Guys,
Edit
So it turns out you can't even flash the Canadian S7 to Tmobile's firmware. I installed the super stock rom and it started working again. I am not on the official Tmobile modem but I get service and WiFi calling so no biggie.
/Edit
This is driving me crazy. I bought the Canadian version of the S7 edge so I can put TWRP on it but I can't use odin on it. (SM-G935W8) Well at least I can't put the Tmobile files on it. Has anyone been able to do it successfully? I really need help, I'm losing my marbles, thanks guys!
I can't flash my appropriate radio so I can't get any service.
This is the error I get whenever I try to flash the radio.
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> modem.bin
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> RQT_CLOSE !!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Did you make sure the oem unlock is on?
gurnsey101 said:
Did you make sure the oem unlock is on?
Click to expand...
Click to collapse
Made sure OEM unlock was checked and USB Debugging was off. I am using the phone right now but I am not on USA radio so my service is not that great but I have WiFi calling so I am making due right now.
You need to ask in the section for your phone, not the software you want to load.
Try this:
https://forum.xda-developers.com/s7-edge/help/samsung-sm-g935f-sm-g935w8-rom-t3414612
joe3681 said:
You need to ask in the section for your phone, not the software you want to load.
Try this:
https://forum.xda-developers.com/s7-edge/help/samsung-sm-g935f-sm-g935w8-rom-t3414612
Click to expand...
Click to collapse
It's not software, it's the radio and bootloader. That thread had no information related to my problem? Maybe I missed something? Thank you for your time.
Well, you're trying to load TMobile software onto hardware with a different bootloader than the TMobile version has so...
joe3681 said:
Well, you're trying to load TMobile software onto hardware with a different bootloader than the TMobile version has so...
Click to expand...
Click to collapse
I'm not sure if you're trolling or not but I am NOT trying to install TMobile software. I am trying to install the radio from USA. I have done it before but for some reason this phone keeps giving me an error through Odin. I thought maybe someone knew of a way to sideload the radio. I searched and found fastboot but I cannot load up fastboot through my S7, I think they removed that feature? Anyway, in case you really aren't trolling you can install a radio that is not from your region as long as you have an unlocked bootloader (which I have now).
*Edit I installed the Tmobile CSC so I'm not sure why you're still hung up on Tmobile software
Your first post mentions twrp, then you mention files, then at the end radio so excuse me for not knowing which one of these you're inquiring about...
Don't get smart if someone is trying to help you and not understanding what your asking cause your OP is a cluster **** to make heads or tails of...
joe3681 said:
Your first posts and **** twrp, then you mention files, then at the end radio.
Don't get smart if someone is trying to help you and not understanding what your asking cause your post is a cluster **** to make heads or tails of.
Click to expand...
Click to collapse
I didn't mean to have an attitude sorry about that. I'm just frustrated because I feel like I am missing something, thank you for your help.
You got it now or no?
Have you tried the CP too which is the modem
joe3681 said:
You got it now or no?
Have you tried the CP too which is the modem
Click to expand...
Click to collapse
Not yet. I was able to restore the phone back to everything stock using Kies but I am still on the Canadian modem. I can actually get service now but now my main issue is I cannot use Samsung Pay since the radios do not match. I wonder if I get a Tmobile S7 edge serial number I can restore it with Kies?
A friend of mine gave me 3x 'oldish" SM-A310F that were decomissioned from his workplace. I successfully brought 2 of them to LOS 16 and recently to 17.1 :good:
But I clumsily "bricked" the process for the third one: tired-me forgot to enable "OEM Unlock" before trying to sideload TWRP... nominal unlucky consequence, it rose the FRP flag :crying:
From then, I can't find a working solution. Download mode unwelcomes unofficial packages. Here are my trials to remedy the situation:
Open the webnavigator during initial setup (trick seen on youtube) >> FAIL
"SMS class 0 / HushSMS" trick (tip seen on youtube) >> FAIL
Upgrade the official firmware: the upgrade went fine with ODIN, but FRP lock is stil there >> FAIL
UnlockFRP_v3.0 : the software tells me unlock is a success, but FRP lock is stil there >> FAIL
SPD FRP by 9jaROM 2017 : running it, I'm able to load the ADB sideload recovery function, LOS ROM is transfered via ADB, but verification of the upgrade fails >> FAIL
ADB commands : it returns the error message 'no devices/emulators found' >> FAIL
I've searched a working solution for a *little* while, seems I'm running out of option. Or... guys, do you have a solution/working tutorial to remove an FRP lock?
Guys, any ideas?
fneuf said:
Guys, any ideas?
Click to expand...
Click to collapse
Hi,
I have absolutely the same phone and same problem.
The only way I know is to download the stock ROM and flash it. I took one from sammobile with A310FXXU5CSI1 PID.
and flashed it with Odin v3.14.4 and even with patched Odin v3.14.1, found on xda.
In both cases I got following:
Code:
<ID:0/023> File analysis..
<ID:0/023> Total Binary size: 3125 M
<ID:0/023> SetupConnection..
<ID:0/023> Initialzation..
<ID:0/023> Get PIT for mapping..
<ID:0/023> Firmware update start..
<ID:0/023> NAND Write Start!!
<ID:0/023> SingleDownload.
<ID:0/023> sboot.bin
<ID:0/023> cm.bin
<ID:0/023> boot.img
<ID:0/023> recovery.img
<ID:0/023> system.img
<ID:0/023> cache.img
<ID:0/023> hidden.img
<ID:0/023> FAIL!
<ID:0/023>
<ID:0/023> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Of course, since the FRP lock is on, I can't flash TWRP or a normal ROM. I can't get into recovery mode or even shutdown the phone. I assume, the recovery partition is lost as well.
Do you have any ideas here as well? Could it be possible to flash only the standard recovery?
I myself used "A310FXXU4CRG2". But doing so, flashing stock, unfortunately doesn't reset the FRP lock.
Hi There, here the same problem sm-A310F,2016, android 7 . Until now no succes. Samsung was from a friend, trouble is google account will sign her out on her new phone. She is blind, so I don 't want to take that risk. I made a backup on smart switch before factory reset. The covid-19 virus is still here and its numbers are rising high again. I've heart problem so the virus is a big risk for me, so I'm on my own (except for online help, no visitors, no meetings, and no visit to the store or repairshop). Odin seems to have contact with the device. Hope somebody had a good idea. Greetings Mary
fneuf said:
I myself used "A310FXXU4CRG2". But doing so, flashing stock, unfortunately doesn't reset the FRP lock.
Click to expand...
Click to collapse
Hey man, stuck with the same problem, I did the same things you did, did you already find a fix?
Phonetimes said:
Hey man, stuck with the same problem, I did the same things you did, did you already find a fix?
Click to expand...
Click to collapse
Funny, I recently gave it to a friend of mine, telling him all I tried... he found by chance an updated working method using wap push sms. Give this a try, I hope it'll also work on your phone.
fneuf said:
Funny, I recently gave it to a friend of mine, telling him all I tried... he found by chance an updated working method using wap push sms. Give this a try, I hope it'll also work on your phone.
Click to expand...
Click to collapse
Alright, thanks so much for replying! I will try it out when I have time, I will let you know if it worked
Phonetimes said:
Alright, thanks so much for replying! I will try it out when I have time, I will let you know if it worked
Click to expand...
Click to collapse
Any success?
fneuf said:
Any success?
Click to expand...
Click to collapse
I tried it a while back but when doing so I found out that the battery was completely ****ed, so I decided it wasnt worth the hassle.. still thanks for the reply, people like you keep the community alive