Related
Hi guys and girls,
I'm new to this forum and new-ish to flashing roms and rooting my phone (SGS4 i9505 jfltexx i9505xxUBMGA), so I apologize If I've posted this in the wrong thread for starters.
I've been jumping between Samsung's stock ROM and Cyanogenmod 10.1/10.2 ROMs.
I can't remember exactly what I did wrong for my phone to be soft bricked, but I can list a few possibles and my device information to see if anyone can spot the problem;
CF-AUTO-ROOT jflte-jfltexx-gti9505
CM-10.2 Nighty Jfltexx
GAPPS
openrecovery-twrp-2.6.3.1
recovery-clockwork 6.0.4.4
PhilZ Touch 5.18.9-i9505
Now when I try boot my device I get told to boot recovery mode in samsung kies .. Which I've tried but it doesn't bring up any device in the list. I've tried it whilst my phone is in download mode, recovery mode and where it displays I've got a firmware issue.
I've tried flashing new recovery files and also I tried flashing "XSS-I9505XXUBMGA-20130924140120.home.tar" via Odin.. All seems to fail
I'm running out of ideas and options and I'm not the wisest guy so if any of you criticize me for my poor knowledge It'll be pointless as I wouldn't be here writing this in the first place If I didn't know that already.
I've never had a problem flashing custom ROMs and recoverys before, this is the first time. I've not selected no stupid options in Odin such as Re-Partition. I stick to the Auto Reboot and occasionally the F. Reset Time. Every guide I look at tells me different.
Below is a list of my devices original stock details:
kernal version
3.4.0-1081224
[email protected] #1
build number
JDQ39.I9505XXUBMGA
Click to expand...
Click to collapse
Any help, files, guides on how to solve this problem given to me would be VERY appreciated.
Also, I'm not sure if this is a kernal problem. But my battery has recently appeared to be draining rather quickly and It'll display "low battery" warnings at about 30% instead of the usual 14%. And It'll also shut down thinking its out of battery at about 16%, then I turn it back on and it says like 30%. Sometimes once its fully died, I place it on charge and after a matter of minutes it says its at 50%... I guess fully draining and leaving my battery on charge for 24 hours may fix that problem?
Please help!
EDIT: I think USB debugging is disabled, but I cannot get into my phone settings to enable it now?
My download mode screen says "Write protection: Enabled".
Just download stock firmware from sammobile and flash with Odin.
Sent from my GT-I9505 using XDA Premium HD app
Obagleyfreer said:
Just download stock firmware from sammobile and flash with Odin.
Sent from my GT-I9505 using XDA Premium HD app
Click to expand...
Click to collapse
I've looked on sammobile but there isn't a i9505xxubmga?
Ipasah said:
I've looked on sammobile but there isn't a i9505xxubmga?
Click to expand...
Click to collapse
here you go
http://www.sammobile.com/firmwares/1/?model=GT-I9505&pcode=BTU#firmware
Really do appreciate it - I'll get downloading that now and I'll let you know how it goes.
As for the debugging mode? Is there a way to enable USB debugging from recovery or download mode?
Also, can I only get xxumbga for my device? xxuemj7 and xxudmh8 are also being show in that link you sent me. Would they not work?
Ipasah said:
Really do appreciate it - I'll get downloading that now and I'll let you know how it goes.
As for the debugging mode? Is there a way to enable USB debugging from recovery or download mode?
Also, can I only get xxumbga for my device? xxuemj7 and xxudmh8 are also being show in that link you sent me. Would they not work?
Click to expand...
Click to collapse
no need to enable usb debugging to flash with odin.
mj7 and mh8 had a secured bootloader with knox (for more info read here), once flashed, you can not downgrade
samersh72 said:
no need to enable usb debugging to flash with odin.
mj7 and mh8 had a secured bootloader with knox (for more info read here), once flashed, you can not downgrade
Click to expand...
Click to collapse
Seems like my bootloader isn't knoxd yet, which i guess makes easier for me to resolve my softbrick problem.
Damn hotfile downloading at 200kb/s. Hopefully I'll have my phone fixed before tomorrow, kinda waiting on a phone call for a job interview lol.
I'm flashing the stock version to my phone now, and it appears to be stuck at the BOOT part.
It is a 2.4GB file though so I'll leave it doing it overnight I guess.
What I got so far:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUBMGA_I9505OXXBMH1_I9505XXUBMGA_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<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> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
Click to expand...
Click to collapse
EDIT - Anyone got any idea how long this takes roughly? It's been stuck on BOOT for about an hour now.
My device displays this in the download mode whilst trying to flash this stock firmware.
ODIN MODE
Product name: GT-i9505
Current binary: Samsung official
System status: Custom
CSB-CONFIG-LSB:0x30
Write protection: Enabled
START [224,1440]
Click to expand...
Click to collapse
UPDATE: Tried flashing the stock firmware with two different versions of ODIN, in different USB slots, and they both failed with the same reason as before. Writing had failed. I'm running out of ideas and really hope I haven't permanently bricked my phone...
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Bump - Need my phone fixing today really, considering anything as long as it works again.
Now it appears like I've got the knox warranty due to trying to fix my phone over Kies .... which failed -.-
Odin mode
Product name: GT-I9505
Current binary: Samsung official
System status: customer
Knox kernel lock: 0x0
Knox warranty void: 0x0
CSB-CONFIG-LSB:0x30
write protection: enabled
eMMC BURST MODE: enabled.
Click to expand...
Click to collapse
HELP ME
same ensingsb
I'm gonna try install this version from Samsung Kies off the Sammobile.com website now:
Model: GT-I9505
Country: United Kingdom
Version: Android 4.3
Changelist: 1765174
Build date: Tue, 15 Oct 2013 07:21:56 +0000
Product Code: BTU
PDA: I9505XXUEMJ7
CSC: I9505BTUEMJ8
MODEM: I9505XXUEMJ7
Click to expand...
Click to collapse
Appears to be my only remaining method of fixing my phone....
Even tried PIT file and re-partitioning now and STILL fail..
I know I shouldn't try things unless I'm 100% sure, but that's the best help I'm getting right now.
The internet has no answers for my problem, and it appears neither does the community of this forum.
One £400 house brick, ****ing brilliant stuff.
Ipasah said:
Even tried PIT file and re-partitioning now and STILL fail..
I know I shouldn't try things unless I'm 100% sure, but that's the best help I'm getting right now.
The internet has no answers for my problem, and it appears neither does the community of this forum.
One £400 house brick, ****ing brilliant stuff.
Click to expand...
Click to collapse
Odin troubleshooting: If Odin accidentally gives you "fail" try the following:
- Repeat procedure.
- Make sure that all actions of Kies are disabled from task manager.
- Change usb port.
- Try another usb cable (make sure it is the original).
- Try another Odin version.
- Uninstall and re-install driver.
- Use pit file.
- Try another computer.
if not, flash a pre-rooted firmware http://forum.xda-developers.com/showthread.php?t=2250824
samersh72 said:
Odin troubleshooting: If Odin accidentally gives you "fail" try the following:
- Repeat procedure.
- Make sure that all actions of Kies are disabled from task manager.
- Change usb port.
- Try another usb cable (make sure it is the original).
- Try another Odin version.
- Uninstall and re-install driver.
- Use pit file.
- Try another computer.
if not, flash a pre-rooted firmware http://forum.xda-developers.com/showthread.php?t=2250824
Click to expand...
Click to collapse
Tried all of those steps many times over.
Is there a point in trying to root my rom when my phone doesn't even get to the bootloader?
Soon as i turn it on i get told theres a firmware issue encountered. I can still get to download mode, but not recovery mode.
EDIT: I dont even know what ROM is on it right now, everything is a mystery to me now, I'm relying purely on the XDA communities help now. As far as I'm aware, I've got a brick.
Sorry I'm giving up trying to find an answer myself now.
If anyone out there actually knows how to fix it, please enlighten me as I haven't the foggiest.
I'll try include as much details as I can ..
Recovery mode doesn't work
Download mode does work
Soon as i turn the device on I get the "Encountered firmware issue" problem
I've tried using many different versions of Odin
I've tried using different USB ports
I've tried using a different USB cable
I've tried using a different PC
I've tried flashing all sorts of recoveries such as TWRP, CWM, PhilZ.
I've tried flashing all sorts of custom and STOCK ROMs
I've tried re-partitioning using a PIT file
Click to expand...
Click to collapse
I've tried EVERYTHING I can possibly think of..
The problem appears to be that my phone WONT let ANYTHING write to it.
Thus making it impossible to flash ANYTHING therefore leaving me stuck with a waste of metal and plastic.
I have the Samsung Galaxy S4 LTE i9505 Jfltexx .. Not sure what ROM is on it, not sure what Kernal, not sure what firmware .. I haven't a clue
Just help me dear god please.
Ipasah said:
Tried all of those steps many times over.
Is there a point in trying to root my rom when my phone doesn't even get to the bootloader?
Soon as i turn it on i get told theres a firmware issue encountered. I can still get to download mode, but not recovery mode.
EDIT: I dont even know what ROM is on it right now, everything is a mystery to me now, I'm relying purely on the XDA communities help now. As far as I'm aware, I've got a brick.
Click to expand...
Click to collapse
try to flash a pre-rooted firmware from the link i gave
samersh72 said:
try to flash a pre-rooted firmware from the link i gave
Click to expand...
Click to collapse
Not gonna lie, i'm not even sure which one I should be downloading from the link you provided.
I dont even know If my device is still under xxubmga or not anymore.
Now I get:
Odin Mode
Product name GT-i9505
current binary samsung official
system status custom
knox kernel lock 0x0
knox warranty void 0x0
csb-config-lsb 0x30
write protection enabled
emmc burst mode enabled
Click to expand...
Click to collapse
and now when odin fails it says
start [224,1440]
sw rev. check fail : fused : 3, binary : 1
Click to expand...
Click to collapse
Ipasah said:
Now I get:
and now when odin fails it says
Click to expand...
Click to collapse
hmmmm.... emmc burst!!!!
samersh72 said:
hmmmm.... emmc burst!!!!
Click to expand...
Click to collapse
If it helps, I couldn't care less about the warranty?
I'd just like my phone to work again, I don't care on what ROM whether it be custom or stock.
Ok, going to try to cover all my bases up front. Here's the whole story.
I rooted my phone and loaded CyanogenMod about 2 days ago. It's way too easy, vastly improved the operation of my phone, so why not? Went off without a hitch. I've been informed that I should have done a NAND Backup, but I had no idea at the time.
About 4 hours ago my wife changed our phone numbers to a local area code after putting it off for the last year. I call Sprint because we're getting Error 16 Switch 386. Turns out you can just update the System Profile on the stock software, but after looking around for a while, turns out you can't in CyanogenMod. I'm like, "Ok, well I'll just put the stock software back on."
So, I try and I try and I try, but it keeps failing. I can still get back in to CyanogenMod, but ODIN won't let me flash any sofware onto my device. Well, one of the times I go to try to make it work I accidentally hit NAND Erase All. Now I'm stuck in a boot loop. I can boot in to recovery and download, but when I try to mount /data to do a factory reset, it can't. Cannot mount /data. Awesome. Now I'm getting into Re-partitioning this piece, which I seem to have successfully done once, but now I still can't flash any software to the phone because this:
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
And here we are. I've tried using different cords, different USB ports, restarting the phone and my computer, different versions of ODIN.
My .pit is CSB_signed_Fusion3_EUR_0325_V2.pit, and my .md5 is \L720VPUAMDC_L720SPTAMDC_L720VPUAMDC_HOME.tar.md5
I'm not trying to go crazy, I just wanted the bloatware and background bull off of my phone. Now I probably have a brick in my pocket.
What firmware were you running when you rooted?? 4.2 or 4.3? If it was 4.3 you need to make sure that the file your trying to flash is a 4.3 (mja or mk2) file!
The tar you posted is MDC if you were on mja or higher this is your problem and you have go back to that!
Here's a link to the tar files I mentioned!
http://forum.xda-developers.com/showthread.php?t=2509605 Sent from my SCH-R970 using Tapatalk
bignick1215 said:
What firmware were you running when you rooted?? 4.2 or 4.3? If it was 4.3 you need to make sure that the file your trying to flash is a 4.3 (mja or mk2) file!
The tar you posted is MDC if you were on mja or higher this is your problem and you have go back to that!
Here's a link to the tar files I mentioned!
http://forum.xda-developers.com/showthread.php?t=2509605 Sent from my SCH-R970 using Tapatalk
Click to expand...
Click to collapse
It was definitely on 4.3. I just started a download for the MJA. Is that the one I need, then?
Should work! If not try the mk2 but I think this will fix ya!
Sent from my SCH-R970 using Tapatalk
bignick1215 said:
Should work! If not try the mk2 but I think this will fix ya!
Sent from my SCH-R970 using Tapatalk
Click to expand...
Click to collapse
Good news and bad news. The new process/files worked, but now I'm stuck on the Sprint boot screen. I'm going to keep poking around because this is much better than where I was at an hour and a half ago, but I've still got a ways to go.
So I did a factory reset, still got the Error mounting /data! message. Pulled the battery, did it again, successfully reset, phone is back to normal. Thanks a ton, homie.
No problem!!
Sent from my SCH-R970 using Tapatalk
i just picked up my Note 3 the other day from verizon (SM-N900V) and i attempted to root it using Root_de_la_vega. It was my fault for not doing more research, but i thought since i wasn't going to do anything fancy other than remove all the bloat ware that it should be simple enough. Now when i use Odin (3.09) it keeps failing and now my phone is bricked and now it says i need to use the software repair assistant.I have tried downloading Kies 3 as one site suggested, but for some reason it does not recognize the device What is the quickest way to repair this? I don't care if it goes back to default. I really need to fix it ASAP! Please help!
Below is the script that shows up in odin when i try to root it:
ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> cache.img.ext4
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Make sure you are using the latest MJE odin file. Also try a different usb port or even a different version of Odin such as 1.85/3.07
droidstyle said:
Make sure you are using the latest MJE odin file. Also try a different usb port or even a different version of Odin such as 1.85/3.07
Click to expand...
Click to collapse
ok, im new to this, and its my fault for jumping in the deep end without doing my proper due diligence. I dont have a good clue what you mean my MJE odin file? Are you refering to the AP file that i drop into odin?
droidstyle said:
Make sure you are using the latest MJE odin file. Also try a different usb port or even a different version of Odin such as 1.85/3.07
Click to expand...
Click to collapse
i also tried using different versions of odin. Can you link to a good root file for SM-N900V?
When @droidstyle mentioned MJE, he is talking about the most current customer release ".tar.md5" file for use with Odin. (There have been at least three public releases so far - MI9, MJ7, and now MJE)
I *think* links for the files you want are here (section 1 of this post)
http://forum.xda-developers.com/showthread.php?t=2483380
I haven't been down the road you are travelling, so I honestly don't know if you are soft bricked (recoverable) or in worse shape than that.
If you succeed in getting things working again, let us know what steps you took.
.
theicro was
bftb0 said:
When @droidstyle mentioned MJE, he is talking about the most current customer release ".tar.md5" file for use with Odin. (There have been at least three public releases so far - MI9, MJ7, and now MJE)
I *think* links for the files you want are here (section 1 of this post)
http://forum.xda-developers.com/showthread.php?t=2483380
I haven't been down the road you are travelling, so I honestly don't know if you are soft bricked (recoverable) or in worse shape than that.
If you succeed in getting things working again, let us know what steps you took.
.
Click to expand...
Click to collapse
Ok, so it seems like i was able to find a .tar.md5 that worked. It loaded up and it seems to have gone back to how it was before i mucked around with it. However i am not sure if i achieved super user. Is there a easy way to tell?
Just to Add Here Are 2 Other Good Places To Look
http://forum.xda-developers.com/showthread.php?t=2576104
How To Flash in ODIN
http://forum.xda-developers.com/showthread.php?t=2543386
Root Recovery Roms
---------- Post added at 11:02 PM ---------- Previous post was at 11:01 PM ----------
deathrage said:
Ok, so it seems like i was able to find a .tar.md5 that worked. It loaded up and it seems to have gone back to how it was before i mucked around with it. However i am not sure if i achieved super user. Is there a easy way to tell?
Click to expand...
Click to collapse
Download root checker from play store
thanks all for the help, and thanks for not chastising me much for my ignorance. Ill def make sure to do much much much more research before i try to do something like this again lol.
Your all back up and running with root I take it then ?
Root checker says that my device was not correctly rooted.....ill look into i more, not sure why it did not take.....it seems like verizon makes it more difficult than any other carrier to root their devices
deathrage said:
Ok, so it seems like i was able to find a .tar.md5 that worked. It loaded up and it seems to have gone back to how it was before i mucked around with it. However i am not sure if i achieved super user. Is there a easy way to tell?
Click to expand...
Click to collapse
The Odin factory image stuff returns everything back to 100% factory, so you shouldn't be rooted if that's all you did.
And since you didn't mention anything else, I suppose that's exactly what we should presume.
Normally when you use that Odin procedure, you are returning to square one - you need to root. Probably with kingo.
As btfb0 said.... root with KingoApp (dot) com.
drag&fly said:
As btfb0 said.... root with KingoApp (dot) com.
Click to expand...
Click to collapse
As you seem to have figured out, the more research you do, the more likely you are to succeed at stuff like this. At least you were able to recover it.
That being said, KingoApp is definitely the best/easiest way to root this phone.
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 everyone.
I bought a phone off ebay recently. Phone is great and all but I cant get pass the Samsung account on the device. I tried the method in these two videos another member provided in another thread but neither worked for me.
http://forum.xda-developers.com/galaxy-s5/help/help-to-bypass-samsung-activation-lock-t3303479
Link 1 :
I cant get to the accessibility settings as when i turn on the phone it brings me straight to the choose wifi network screen.
Link 2:
I get to as far as where he mentions to tap the email, but it doesn't work whether I tap it or hold it down.
I have tried using an OTG cable and an apk to get into the settings but whenever I try to change anything like for instance turning off encryption lock it turns back the option on a second later. Because of this I cant even Flash the phone with Odin. I have tried everything to my knowledge to get it to work and nothing does.
Please Help:crying:
If you can boot into download mode you can flash with Odin
Cryceratops said:
If you can boot into download mode you can flash with Odin
Click to expand...
Click to collapse
I tried Odin fails everytime. I read somewhere that the reactivation lock can stop you from flashing it, is this true?
Gheddo said:
I tried Odin fails everytime. I read somewhere that the reactivation lock can stop you from flashing it, is this true?
Click to expand...
Click to collapse
Shouldn't fail, make sure you have the correct firmware and the latest version of Odin (3.10.7). Are you sure you're flashing it correctly? You need to flash the .tar.md5 file to the AP tab in Odin.
Yup I did all that
This is what I got.
<ID:0/005> Added!!
<ID:0/005> Removed!!
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1100)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On the Phone screen it says this.
Odin Mode
Product Name: SM-G900A
Current Binary: Samsung Official
System Status: Official
Reactivation Lock (KK): ON
KNOX Warranty Void: 0x0
Qualcom Secureboot: Enable (csb)
AP SWAEV : S1, T2, R1, A3, P1
Secure download: Enable
UDC START
SW REV CHECK FAIL: [aboot]Fused 3 > Binary 1
Cryceratops said:
Shouldn't fail, make sure you have the correct firmware and the latest version of Odin (3.10.7). Are you sure you're flashing it correctly? You need to flash the .tar.md5 file to the AP tab in Odin.
Click to expand...
Click to collapse
Reactivation lock blocks reflashing from odin.
Sent from my SAMSUNG-SM-G900A using Tapatalk
Rakuu said:
Reactivation lock blocks reflashing from odin.
Sent from my SAMSUNG-SM-G900A using Tapatalk
Click to expand...
Click to collapse
I figured as much, is there anyway around this cause I cant turn off the lock?
Gheddo said:
I figured as much, is there anyway around this cause I cant turn off the lock?
Click to expand...
Click to collapse
Contact the seller to A.) Delete the associated Samsung account or B.) Give you the login information. I can't find any ways of bypassing it, I've found threads where people suggest stuff but nothing's clear cut as to what worked or not, deleting the Samsung account or logging in to it will surely work though.
Sent from my SAMSUNG-SM-G900A using Tapatalk
Rakuu said:
Contact the seller to A.) Delete the associated Samsung account or B.) Give you the login information. I can't find any ways of bypassing it, I've found threads where people suggest stuff but nothing's clear cut as to what worked or not, deleting the Samsung account or logging in to it will surely work though.
Sent from my SAMSUNG-SM-G900A using Tapatalk
Click to expand...
Click to collapse
Thanks, I did this but the seller claims they dont know what it is cause they are just a re seller. I just have to accept the fact that for now the phone is just a paperweight. :crying:
Rakuu said:
Reactivation lock blocks reflashing from odin.
Sent from my SAMSUNG-SM-G900A using Tapatalk
Click to expand...
Click to collapse
No it doesn't - it stops you 'Reactivating' the phone... many people got stung with that Xtrestolite ROM having reactivation lock enabled as default, and no way to disable if you missed it during initial setup
Fix was to flash a stock KK ROM with ODIN, and log into all accounts > disable reactivation lock
@ OP - Have you tried flashing a stock KitKat ROM?
*Detection* said:
No it doesn't - it stops you 'Reactivating' the phone... many people got stung with that Xtrestolite ROM having reactivation lock enabled as default, and no way to disable if you missed it during initial setup
Fix was to flash a stock KK ROM with ODIN, and log into all accounts > disable reactivation lock
@ OP - Have you tried flashing a stock KitKat ROM?
Click to expand...
Click to collapse
You still need the original Samsung account for that though.
Sent from my SAMSUNG-SM-G900A using Tapatalk
Rakuu said:
You still need the original Samsung account for that though.
Sent from my SAMSUNG-SM-G900A using Tapatalk
Click to expand...
Click to collapse
Not necessarily, the youtube videos I linked in the OPs link show how to bypass it without the original account - and I'm wondering if the reason it's not working for OP is because he's not running KK (I assume)
I know those video tutorials work, good few people have confirmed here on XDA
*Detection* said:
Not necessarily, the youtube videos I linked in the OPs link show how to bypass it without the original account - and I'm wondering if the reason it's not working for OP is because he's not running KK (I assume)
I know those video tutorials work, good few people have confirmed here on XDA
Click to expand...
Click to collapse
Hmmm, I'll leave it to you then I seem to be misinformed about this topic.
Sent from my SAMSUNG-SM-G900A using Tapatalk
Yeah I have actually. The rom I'm using is from SamMobile for my specific phone, SM-G900A.
*Detection* said:
Not necessarily, the youtube videos I linked in the OPs link show how to bypass it without the original account - and I'm wondering if the reason it's not working for OP is because he's not running KK (I assume)
I know those video tutorials work, good few people have confirmed here on XDA
Click to expand...
Click to collapse
You're right I'm on 5.0, so Lollipop I guess.
Gheddo said:
Yeah I have actually. The rom I'm using is from SamMobile for my specific phone, SM-G900A.
You're right I'm on 5.0, so Lollipop I guess.
Click to expand...
Click to collapse
Links to Sammobile are banned here
Try a KK stock ROM (or are you saying you have tried a KK ROM and the youtube tutorial already?)
*Detection* said:
Links to Sammobile are banned here
Try a KK stock ROM (or are you saying you have tried a KK ROM and the youtube tutorial already?)
Click to expand...
Click to collapse
Sorry about the banned content mate i removed it now. Can you provide me a link to a stock KK rom other than Sam. I haven't tried them together cause the Flashing fails I have however tried both you tube videos and they fail. The phone doesnt allow me to change anything in the settings. If I get as far as adding a new Samsung account and I click the option absolutely nothing happens.
Gheddo said:
Sorry about the banned content mate i removed it now. Can you provide me a link to a stock KK rom other than Sam. I haven't tried them together cause the Flashing fails I have however tried both you tube videos and they fail. The phone doesnt allow me to change anything in the settings. If I get as far as adding a new Samsung account and I click the option absolutely nothing happens.
Click to expand...
Click to collapse
Ah, you're AT&T ?
They lock their bootloaders, that might be causing problems with downgrading to KK
I'm in the UK with a G900F, so don't have much know-how about tricks on downgrading your model S5
Vaguely remember people having success, you'll have to hunt through the forums and see if you can find any, but I do know people have taken them to AT&T and had them downgrade their S5s for them
Not sure what they'll say about it being locked though, maybe take proof of purchase
If I come across a downgrade method for your phone, I`ll post it back here
*Detection* said:
Ah, you're AT&T ?
They lock their bootloaders, that might be causing problems with downgrading to KK
I'm in the UK with a G900F, so don't have much know-how about tricks on downgrading your model S5
Vaguely remember people having success, you'll have to hunt through the forums and see if you can find any, but I do know people have taken them to AT&T and had them downgrade their S5s for them
Not sure what they'll say about it being locked though, maybe take proof of purchase
If I come across a downgrade method for your phone, I`ll post it back here
Click to expand...
Click to collapse
Thanks a lot mate I wont be able to take it to a store as I live outside the US. I'll be looking out thanks a lot.
This one I do know the answer to : P as it stands unless you were already rooted on KK and updated to L using the prerooted rom file you cannot downgrade to KK.
Sent from my SAMSUNG-SM-G900A using Tapatalk
Rakuu said:
This one I do know the answer to : P as it stands unless you were already rooted on KK and updated to L using the prerooted rom file you cannot downgrade to KK.
Sent from my SAMSUNG-SM-G900A using Tapatalk
Click to expand...
Click to collapse
Thanks mate I just have to wait patiently till someone figures something out. Thanks