Related
Hello everyone,
I hate to be the person that joins a forum with an immediate question without having contributed anything previously, but here it goes: looking for some advice from experts on this one. I have an AT&T Galaxy S4 i337 that I recently updated to KitKat 4.4.2 - worst mistake I've ever made, not only do I have constant problems getting GPS locks now, perhaps the most aggravating issue is slow charging. It can take upwards of 7 hours to charge to 100% and I've tried everything including new cable and new battery. The phone can be plugged in and charging and still discharge until it dies. This issue surfaced immediately after I updated and, based on other information I've seen on XDA and other forums, it seems entirely probable this is a software issue since a lot of people seem to have the same problem. Plus, I'm getting tired of TouchWiz.
So I've decided to go towards SlimKat custom ROM hopefully to rectify some of these issues. However, I've had major problems at every step especially being on 4.4.2 (and what I believe is the newer firmware MF3?). Here is a summary of what I've done:
1) Tried rooting the phone through the XDA tutorial on this subforum where you use Motochopper, CF root and all of that, I forget the exact issue but it never worked. I tried for quite a long time.
2) I finally got the device rooted through Towelroot, which I had suspicions about because it was so easy and quick, but after installing SuperSU and RootChecker it's working like a charm!
3) Installed TWRP without success through GooManager... it would download and hang or say successfully installed but wouldn't ever boot into recovery.
4) Tried installing SafeStrap and as soon as I downloaded the lastest version and tried to install it from the app/GUI it would say install successful but the state would be listed as Not Installed
5) Moved onto ClockWorkMod which I had success with in the past on my Samsung Vibrant and CyanogenMod several years ago. I tried flashing recovery from the app and while it says it's sucessfully installed, once again I boot into recovery and I get an blue Andriod for a split second then a dead looking Andriod with a No Command error given. It boots into stock recovery, and it has the custom unlock logo under the samsung POST (or bootup) screen but won't launch ClockWorkMod.
So that brings me to where I am at now. I got the latest GS4 drivers from Samsung, made sure Kies was not installed, went through countless processes/cables USB ports (made sure they weren't hubs obviously) and I keep getting the same error when I try flashing ClockWorkMod for the i337 right from Odin3. I get:
<ID:0/005> Added!!
<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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Removed!!
or
<ID:0/005> Added!!
<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> Get PIT for mapping..
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
I know the Galaxy S4 i337 from AT&T especially with KitKat 4.4 is notoriously hard to root but I'm on my last nerve with this phone, I wouldn't be so frustrated if the stock OS didn't have so many issues with the update. When in Odin, I tried getting an SGH-i337 16GB PIT file and still got an error so that's not working either. No idea where to go from now, and sick and tired of waiting for AT&T, Google, and Samsung to come out with a fix and network-pushed update.
Please help!!! :fingers-crossed:
Nati0n said:
Hello everyone,
I hate to be the person that joins a forum with an immediate question without having contributed anything previously, but here it goes: looking for some advice from experts on this one. I have an AT&T Galaxy S4 i337 that I recently updated to KitKat 4.4.2 - worst mistake I've ever made, not only do I have constant problems getting GPS locks now, perhaps the most aggravating issue is slow charging. It can take upwards of 7 hours to charge to 100% and I've tried everything including new cable and new battery. This issue surfaced immediately after I updated and, based on other information I've seen on XDA and other forums, it seems entirely probable this is a software issue since a lot of people seem to have the same problem. Plus, I'm getting tired of TouchWiz.
So I've decided to go towards SlimKat custom ROM hopefully to rectify some of these issues. However, I've had major problems at every step especially being on 4.4.2 (and what I believe is the newer firmware MF3?). Here is a summary of what I've done:
1) Tried rooting the phone through the XDA tutorial on this subforum where you use Motochopper, CF root and all of that, I forget the exact issue but it never worked. I tried for quite a long time.
2) I finally got the device rooted through Towelroot, which I had suspicions about because it was so easy and quick, but after installing SuperSU and RootChecker it's working like a charm!
3) Installed TWRP without success through GooManager... it would download and hang or say successfully installed but wouldn't ever boot into recovery.
4) Tried installing SafeStrap and as soon as I downloaded the lastest version and tried to install it from the app/GUI it would say install successful but the state would be listed as Not Installed
5) Moved onto ClockWorkMod which I had success with in the past on my Samsung Vibrant and CyanogenMod several years ago. I tried flashing recovery from the app and while it says it's sucessfully installed, once again I boot into recovery and I get an blue Andriod for a split second then a dead looking Andriod with a No Command error given. It boots into stock recovery, and it has the custom unlock logo under the samsung POST (or bootup) screen but won't launch ClockWorkMod.
So that brings me to where I am at now. I got the latest GS4 drivers from Samsung, made sure Kies was not installed, went through countless processes/cables USB ports (made sure they weren't hubs obviously) and I keep getting the same error when I try flashing ClockWorkMod for the i337 right from Odin3. I get:
<ID:0/005> Added!!
<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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Removed!!
or
<ID:0/005> Added!!
<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> Get PIT for mapping..
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
I know the Galaxy S4 i337 from AT&T especially with KitKat 4.4 is notoriously hard to root but I'm on my last nerve with this phone, I wouldn't be so frustrated if the stock OS didn't have so many issues with the update. When in Odin, I tried getting an SGH-i337 16GB PIT file and still got an error so that's not working either. No idea where to go from now, and sick and tired of waiting for AT&T, Google, and Samsung to come out with a fix and network-pushed update.
Please help!!! :fingers-crossed:
Click to expand...
Click to collapse
SGH-i337 has a locked bootloader. That prevents us from replacing the stock kernel and recovery. The only working recovery we have is safestrap.
The bootloader also prevents a downgrade unless the versions are compatible. NB1 and NC1 are compatible and so you should be able to flash the stock NB1 firmware using Odin.
Since you have root already, you can install safestrap after setting SELinux to permissive mode. Use the selinuxmodechanger app from play store for that.
All things AT&T thread.
So I would have to downgrade to compatible NB1 using ODIN (once I do the step you described) and then from there could I flash a custom ROM such as SlimKat? Would safestrap work in NB1 even though it doesn't work in the current firmware?
Nati0n said:
So I would have to downgrade to compatible NB1 using ODIN (once I do the step you described) and then from there could I flash a custom ROM such as SlimKat? Would safestrap work in NB1 even though it doesn't work in the current firmware?
Click to expand...
Click to collapse
Since you successfully rooted with towel root, I guess your firmware is NC1.
You do not need to downgrade to NB1. Your safestrap version should be 3.72. Are you sure your safestrap is not working. To go to the safestrap you simply restart your phone. You do not need to go the recovery mode.
You have locked bootloader so you can not use the custom kernel or AOSP rom like Slimkat. You can only use the TOUCHWIZ roms.
sway8966 said:
Since you successfully rooted with towel root, I guess your firmware is NC1.
You do not need to downgrade to NB1. Your safestrap version should be 3.72. Are you sure your safestrap is not working. To go to the safestrap you simply restart your phone. You do not need to go the recovery mode.
You have locked bootloader so you can not use the custom kernel or AOSP rom like Slimkat. You can only use the TOUCHWIZ roms.
Click to expand...
Click to collapse
Can you help me? I am trying to factory reset my galaxy s4 that is rooted with towelroot to sell on ebay. When I reset it, it saids "ATT detected software not authorized for phone", and it doesn't reset. Anyway to do this?
patstar5 said:
Can you help me? I am trying to factory reset my galaxy s4 that is rooted with towelroot to sell on ebay. When I reset it, it saids "ATT detected software not authorized for phone", and it doesn't reset. Anyway to do this?
Click to expand...
Click to collapse
Flash nb1 firmware using odin
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
drock212 said:
Flash nb1 firmware using odin
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ok,following instructions here: www.androidrootz.com/2014/03/how-to-unrootunbrick-at-galaxy-s4-sgh.html?m=1
Internet is really slow, 1mbps, so started 2.2gb file download and will try it when it finishes downloading, probably tomorrow. Going to post here if it works. Well, July 4th, going to do fireworks later on. Happy Independence day for all of you in U.S!
patstar5 said:
Ok,following instructions here: www.androidrootz.com/2014/03/how-to-unrootunbrick-at-galaxy-s4-sgh.html?m=1
Internet is really slow, 1mbps, so started 2.2gb file download and will try it when it finishes downloading, probably tomorrow. Going to post here if it works. Well, July 4th, going to do fireworks later on. Happy Independence day for all of you in U.S!
Click to expand...
Click to collapse
Remember what I already mentioned. Since you are on NC1, you can only flash NB1 (as they are compatible and we dont have a full NC1 tar file). You cannot flash MK2.
sway8966 said:
Since you successfully rooted with towel root, I guess your firmware is NC1.
You do not need to downgrade to NB1. Your safestrap version should be 3.72. Are you sure your safestrap is not working. To go to the safestrap you simply restart your phone. You do not need to go the recovery mode.
You have locked bootloader so you can not use the custom kernel or AOSP rom like Slimkat. You can only use the TOUCHWIZ roms.
Click to expand...
Click to collapse
Ah okay understood, thanks for linking me to that thread I will look through those Touchwiz based roms. I was hoping to go to a Google Play Edition ROM too but from what I'm reading a lot of things don't work on it.
Thanks again everyone for your knowledge and advice. In reality do you think flashing a custom Touchwiz based ROM will address my issues or should I just downgrade to NB1? And is there REALLY no way to unlock the S4 bootloader on GSM devices? I thought someone did it on a CDMA version recently.
UPDATE: I should have reread the first post, after installing SELinuxModeChanger and setting it to permissive, I was able to get SafeStrap to install and boot properly.
You need to have selinux in permissive mode. Use selinuxmodechanger app for that.
jmjoyas said:
Remember what I already mentioned. Since you are on NC1, you can only flash NB1 (as they are compatible and we dont have a full NC1 tar file). You cannot flash MK2.
Click to expand...
Click to collapse
OK, downloaded first file here:http://forum.xda-developers.com/showthread.php?t=2674223
After flashing, I can do OTA update to get one NC1?
Yeah with the combination of TowelRoot, SELinuxModeChanger, and SafeStrap I now have a rooted phone with a recovery installed, what ROMs do you guys recommend that are TouchWiz based for the i337 NC1? I'm looking through the list and not seeing much.
Nati0n said:
Yeah with the combination of TowelRoot, SELinuxModeChanger, and SafeStrap I now have a rooted phone with a recovery installed, what ROMs do you guys recommend that are TouchWiz based for the i337 NC1? I'm looking through the list and not seeing much.
Click to expand...
Click to collapse
All the ROMs listed in the all things at thread will work.
Yeah, with hesitation I ended up going with a Google Play Edition ROM to get rid of touchwiz and man did it work well, my only minor annoyances are wifi (as was warned) and the face that MMS pictures are compressed WAY too much when I send them. The charging issue got marginally better but the battery lasts a lot longer without bloatware and the interface is super sleek.
Nati0n said:
Yeah, with hesitation I ended up going with a Google Play Edition ROM to get rid of touchwiz and man did it work well, my only minor annoyances are wifi (as was warned) and the face that MMS pictures are compressed WAY too much when I send them. The charging issue got marginally better but the battery lasts a lot longer without bloatware and the interface is super sleek.
Click to expand...
Click to collapse
Every time you reboot the phone, you will lose WiFi. You can recover it by soft rebooting the phone.
s4 recovery issues
Nati0n said:
Yeah with the combination of TowelRoot, SELinuxModeChanger, and SafeStrap I now have a rooted phone with a recovery installed, what ROMs do you guys recommend that are TouchWiz based for the i337 NC1? I'm looking through the list and not seeing much.
Click to expand...
Click to collapse
could you tell me the steps you took? i'm stuck with a rooted samsung s4 also. this is my phones info. i would appreciate the help. many thanks will come your way.
Hey guys, I'm having a little trouble getting custom roms installed on my Galaxy S4. Here is a little information about the phone
Carrier: ATT
Model: Galaxy SGH - 1337
Android version 4.2.2
After spending a few hours here on XDA both searching the site and posting on the help thread, I've come to no solution.
So yesterday due to a level of frustration with the amount of bloat that comes pre-installed on the Samsung devices, I decided I would try to set up a custom rom. I've used the Towelroot site to root the device (enable superuser access and disable Knox,) But wasn't able to install CWM. I've downloaded and installed the CWM Rom Manager and inside that app is an option to install CWM manually. Of course it isn't that easy, because although it says it's installed the recovery, when I boot into recover mode, it is still the stock android recovery mode.
So I turned to Odin. Specifically Odin 3.09. This is where the problems start. I start my phone and enable download mode. The phone is recognized by Odin and I choose the CWM file I have (recover-clockwork-touch-6.0.4.4-jflteatt.tar.) I press start and the process begins, but before long I see FAIL! in red at the top
The message box reads as follows:
<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> recovery.img
<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)
<ID:0/003> Removed!!
I've tried using three different usb cables (including the stock s4 cable included in the packaging) and several different ports of course to no avail.
What exactly does FAIL! (Auth) mean? That seems to be the point where it goes south.
Could I be flashing a bad file? Is the CWM.tar.md5 not the correct file to flash?
I've tried several different versions of both Odin and CWM. Is there something else that I have to do before this step? I've read a lot about the S4 being a pain to load custom roms onto.
Anyways if anyone has a fix to this particular solution then let me know. Otherwise I'll take really any other viable solution to enabling custom roms on the Galaxy S4 for ATT. I'd like this to be a thread that people see when they google search it, so I won't give up and I'll be sure to post with the best process that I can find!
Your boot loader is locked. So, no custom recovery and kernel. The only working recovery we have is safestrap.
More info - http://forum.xda-developers.com/showthread.php?t=2616221
misterbreadcrum said:
Hey guys, I'm having a little trouble getting custom roms installed on my Galaxy S4. Here is a little information about the phone
Carrier: ATT
Model: Galaxy SGH - 1337
Android version 4.2.2!
Click to expand...
Click to collapse
I see this above but need more info... Are you completely stock right now?
You will NOT be able to Odin any CWM to this phone. See below for other brief info for you to look into for CWM/TWRPand how to install IF on MDB or MDL firmware. Or if MF3 Your ONLY OPTION is Safestrap and limited to TouchWiz based Roms.
If you are then when you go to Settings/More/About Phone what does your Baseband say? Does it end with MDB, MDL, MF3?
IF it ends with MDB or MDL the look up Casual Root with TWRP. This will allow you to flash ANY Roms.
IF it ends with MF3 Then look up Safestrap for MF3. This will allow you to flash Safestrap versions of Roms.
ALSO IF it is MF3 you might as well update to MK2 or NB1 then use their safestrap version for root
Sent fron I337 Red BadAss Themed ShoStock 7.0
Q&A for [RECOVERY][UNOFFICIAL] TWRP for the Samsung Galaxy S5
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY][UNOFFICIAL] TWRP for the Samsung Galaxy S5. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
It does not work for me.
When i try to install the custom recovery it just ends with a fail. I use Odin 3.10, removed battery and putted it in again but still not working. Can anyone help?
Samsung galaxy s5 - Android 5 lollipop G900F.
<ID:0/007> Added!!
<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> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Installation Partition
Hi, i have downloaded the TWRP Manager and attempting to install the twrp recovery onto my phone.
It has a prompt to ask me if the install partition /dev/block/platoform/msm_sdcc.1/by-name/recovery is correct. Can i know if this is the correct installation location for SM-G900F Devices for TWRP?
Please advise.
Which latest TWRP works for the S5 ?
On the first post of http://forum.xda-developers.com/showthread.php?t=2697762 at "The goods" the recovery-twrp-klte.img there dates from 2014-Apr-19 and no version number with it.
Offical TWRP at http://forum.xda-developers.com/showthread.php?t=2727406 has version 2.8.4.0 [2015-01-13].
At http://forum.xda-developers.com/showthread.php?t=2697762&page=28 I read that TWRP 2.8.3.0 is buggy for S5.
So should I use the old version of April 2014 or 2.8.3.4 ?
vatbier said:
Which latest TWRP works for the S5 ?
On the first post of http://forum.xda-developers.com/showthread.php?t=2697762 at "The goods" the recovery-twrp-klte.img there dates from 2014-Apr-19 and no version number with it.
Offical TWRP at http://forum.xda-developers.com/showthread.php?t=2727406 has version 2.8.4.0 [2015-01-13].
At http://forum.xda-developers.com/showthread.php?t=2697762&page=28 I read that TWRP 2.8.3.0 is buggy for S5.
So should I use the old version of April 2014 or 2.8.3.4 ?
Click to expand...
Click to collapse
Use the latest: 2.8.3.4 works fine BUT in MOUNT optons DISABLE MTP to avoid errors while wiping cache,data and dalvik partitions.
With enabled MTP there is errors while restoring backup or flashing new rom.
I am using phillz TWRP.
Both works on S5 4.4.2 or 5.0 (g900f, g900i tested by me, other variants - you must read in thread).
Will this work on SG-M900W8 on andriod 5.1.1 I have not been able to get root at all need help!!
@PlayfulGod dose this work on SG-M900W8 on 5.1.1
TWRP 3.0.2-1 cannot decrypt S5, wrong password
HI, when I try to install new firmware on my galaxy j5 with odin with pda and file pit for repartition, I got this errors:
<ID:0/010> Added!!
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Set PIT file..
<ID:0/010> DO NOT TURN OFF TARGET!!
<ID:0/010>
<ID:0/010>Re-Partition operazioni failed.
<OSM>All threads completed. (succeed 0 / fail 1)
Please, help me.
Seconded. Does anyone have a solution for this issue?
@Vincenzolt98 @Dionisis89
It's a custom PIT or stock one? From where you downloaded stock ROM?
When I flashed stock ROM I only had to put it at PDA ( AP for newer Odin versions). I think the repartition should be done automatically when is flashed stock ROM.
Try latest Odin version and also make sure that the PIT file is the correct one (can be for 8gb, 16gb for example).
I recommend you to use SamFirm program for downloading stock ROMs faster.
SamFirm: http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647 . Even if it's deprecated, it still works fine. The program is attached at attachments in that thread.
#Henkate said:
@Vincenzolt98 @Dionisis89
It's a custom PIT or stock one? From where you downloaded stock ROM?
When I flashed stock ROM I only had to put it at PDA ( AP for newer Odin versions). I think the repartition should be done automatically when is flashed stock ROM.
Try latest Odin version and also make sure that the PIT file is the correct one (can be for 8gb, 16gb for example).
I recommend you to use SamFirm program for downloading stock ROMs faster.
SamFirm: http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647 . Even if it's deprecated, it still works fine. The program is attached at attachments in that thread.
Click to expand...
Click to collapse
It should be the stock PIT. I don't remember where I downloaded it from but it appears to be the correct one. I don't know where the problem is.
The firmware corresponding to my J500FN's CSC is Austrian (ATO), so I downloaded it from that updato site.
The reason I went to find the PIT file in the first place is because flashing stock ROM via Odin failed. It showed this code (last 2 lines):
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Ext4)
It had failed at this point, and I've tried flashing the 6.0.1 and 5.1.1 stock image, to no avail. Perhaps you have a solution for that instead?
Dionisis89 said:
It should be the stock PIT. I don't remember where I downloaded it from but it appears to be the correct one. I don't know where the problem is.
The firmware corresponding to my J500FN's CSC is Austrian (ATO), so I downloaded it from that updato site.
The reason I went to find the PIT file in the first place is because flashing stock ROM via Odin failed. It showed this code (last 2 lines):
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Ext4)
It had failed at this point, and I've tried flashing the 6.0.1 and 5.1.1 stock image, to no avail. Perhaps you have a solution for that instead?
Click to expand...
Click to collapse
Regsrding hidden.img.ext4 error, try this: https://www.youtube.com/watch?v=2uTHilnRsWw. Credits to @pacower for sharing that video. Also try to use newer Odin version (I used 3.09 or so all the time though).
People confirmed that this video works, but here is a post/tip regarding that video: http://forum.xda-developers.com/showpost.php?p=69673728&postcount=10 .
#Henkate said:
Regsrding hidden.img.ext4 error, try this: https://www.youtube.com/watch?v=2uTHilnRsWw. Credits to @pacower for sharing that video. Also try to use newer Odin version (I used 3.09 or so all the time though).
People confirmed that this video works, but here is a post/tip regarding that video: http://forum.xda-developers.com/showpost.php?p=69673728&postcount=10 .
Click to expand...
Click to collapse
I've tried this method, but Odin shows me another error: MD5 error! binary is invalid .
And yes, I've tried removing the .md5 from the file name, but then Odin is stuck on file analysis forever. That happens on Odin v3.12. At version 3.11, it simply hangs after choosing that file. At version 3.09 (which also has the option of flashing a PIT file) it shows this:
<ID:0/005> Added!!
<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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any idea of what I could do? Maybe the PIT file I used isn't correct, after all? Where should I download it from?
---------- Post added at 01:43 PM ---------- Previous post was at 01:28 PM ----------
Hey bro, found the issue. Apparently the firmware I downloaded wasn't right and that's why it never went through with booting the hidden.img.ext4. The link you provided, however, made it happen! You saved my phone. Thanks a million!
Dionisis89 said:
I've tried this method, but Odin shows me another error: MD5 error! binary is invalid .
And yes, I've tried removing the .md5 from the file name, but then Odin is stuck on file analysis forever. That happens on Odin v3.12. At version 3.11, it simply hangs after choosing that file. At version 3.09 (which also has the option of flashing a PIT file) it shows this:
<ID:0/005> Added!!
<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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any idea of what I could do? Maybe the PIT file I used isn't correct, after all? Where should I download it from?
---------- Post added at 01:43 PM ---------- Previous post was at 01:28 PM ----------
Hey bro, found the issue. Apparently the firmware I downloaded wasn't right and that's why it never went through with booting the hidden.img.ext4. The link you provided, however, made it happen! You saved my phone. Thanks a million!
Click to expand...
Click to collapse
Did you try to flash it without PIT file?
Also, if you flashed TWRP before, then try to flash TWRP, then boot in TWRP recovery and wipe /system, /data, /cache and dalvik-cache. Then power off the phone, boot in download mode and try to flash again through Odin.
If you didn't flash TWRP before and you don't wanna lose warranty, then boot in stock recovery and wipe, but your internal memory will be wiped too.
I never used a PIT file when I flashed stock ROM.
EDIT:
Dionisis89 said:
Hey bro, found the issue. Apparently the firmware I downloaded wasn't right and that's why it never went through with booting the hidden.img.ext4. The link you provided, however, made it happen! You saved my phone. Thanks a million!
Click to expand...
Click to collapse
Oh. Nice
I'm glad I helped you.
#Henkate said:
Did you try to flash it without PIT file?
Also, if you flashed TWRP before, then try to flash TWRP, then boot in TWRP recovery and wipe /system, /data, /cache and dalvik-cache. Then power off the phone, boot in download mode and try to flash again through Odin.
If you didn't flash TWRP before and you don't wanna lose warranty, then boot in stock recovery and wipe, but your internal memory will be wiped too.
I never used a PIT file when I flashed stock ROM.
EDIT:
Oh. Nice
I'm glad I helped you.
Click to expand...
Click to collapse
I'm sorry I didn't try flashing the firmware you provided me with in the first place, thereby "making you" type more on an answer that has been answered (by my flashing the correct firmware). There is something else you might help me with, if you have the time. Why did you provide me with a link to the German firmware? I told you it had Austrian CSC. And yet the German firmware was the one that actually worked. How so? And something else. Which is the website that you sent that firmware from? You edited your post soon after you had posted the link.
Dionisis89 said:
I'm sorry I didn't try flashing the firmware you provided me with in the first place, thereby "making you" type more on an answer that has been answered (by my flashing the correct firmware). There is something else you might help me with, if you have the time. Why did you provide me with a link to the German firmware? I told you it had Austrian CSC. And yet the German firmware was the one that actually worked. How so? And something else. Which is the website that you sent that firmware from? You edited your post soon after you had posted the link.
Click to expand...
Click to collapse
Huh? I only gave you links with the YouTube video and SamFirm.
Oh wait, I think that maybe SamFirm downloaded latest available update. In SamFirm you can switch to manual mode and type there the region, PDA and CSC and you can download the firmware which you want.
#Henkate said:
Huh? I only gave you links with the YouTube video and SamFirm.
Oh wait, I think that maybe SamFirm downloaded latest available update. In SamFirm you can switch to manual mode and type there the region, PDA and CSC and you can download the firmware which you want.
Click to expand...
Click to collapse
I didn't use SamFirm to download the firmware file, of that I'm sure. Mostly because upon attempting, I failed. I had put SM-J500FN in model name and ATO in CSC, but SamFirm found nothing.
I think you had a link from Mediafire in your response to me and that's how I downloaded the firmware. Hell, I might be mistaken, since I searched through a ton of threads, including some at XDA, in order to find a solution. It's possible I saw the link at another user's post.
In any case, thank you very much, once again. You saved my phone from becoming a paperweight.
Dionisis89 said:
I didn't use SamFirm to download the firmware file, of that I'm sure. Mostly because upon attempting, I failed. I had put SM-J500FN in model name and ATO in CSC, but SamFirm found nothing.
I think you had a link from Mediafire in your response to me and that's how I downloaded the firmware. Hell, I might be mistaken, since I searched through a ton of threads, including some at XDA, in order to find a solution. It's possible I saw the link at another user's post.
In any case, thank you very much, once again. You saved my phone from becoming a paperweight.
Click to expand...
Click to collapse
Is this the link you talk about? http://www.mediafire.com/download/skldahurz12dick/DBT-J500FNXXU1AOI1-20151006173751.zip . If yes, it's the German stock ROM I've uploaded andmentioned it in my ROM thread at installation instructions I posted it only there. It's kinda old firmware, but always worked fine for me, didn't have any issues (it's the firmware which my phone came with).
You welcome! I'm glad I helped you!
Maybe the OP (first post) has same problem like you. He'll have to read
#Henkate said:
Is this the link you talk about? http://www.mediafire.com/download/skldahurz12dick/DBT-J500FNXXU1AOI1-20151006173751.zip . If yes, it's the German stock ROM I've uploaded andmentioned it in my ROM thread at installation instructions I posted it only there. It's kinda old firmware, but always worked fine for me, didn't have any issues (it's the firmware which my phone came with).
You welcome! I'm glad I helped you!
Maybe the OP (first post) has same problem like you. He'll have to read
Click to expand...
Click to collapse
Yes, yes, that's the one!
I doubt he still has the problem though, since the thread was created at the end of August. Nonetheless, other people who might face the same issue will be able to read this thread and extract useful information.
Hello, I have Canadian version of S7E which should be compatible with G935F but I'm getting pit error
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
OEM/USB are both on in developer options, any ideas what's causing this or should I try a different firmware?
re: firmware flashing
HeavenlyFall said:
Hello, I have Canadian version of S7E which should be compatible with G935F but I'm getting pit error
OEM/USB are both on in developer options, any ideas what's causing this or should I try a different firmware?
Click to expand...
Click to collapse
When flashing any firmware in Odin do NOT checkmark the PIT option.
Make sure that the PIT option in Odin is NOT checked before flashing!
Good luck, have a great day!
Misterjunky said:
When flashing any firmware in Odin do NOT checkmark the PIT option.
Make sure that the PIT option in Odin is NOT checked before flashing!
Good luck, have a great day!
Click to expand...
Click to collapse
The only options checked is auto reboot and reset time tho
Since this is not working, is it possible to flash directly to a nougat rom if I'm on MM + rooted with TWRP?
re: flashing
HeavenlyFall said:
The only options checked is auto reboot and reset time tho
Since this is not working, is it possible to flash directly to a nougat rom if I'm on MM + rooted with TWRP?
Click to expand...
Click to collapse
Yes, if you are rooted and have twrp both sucessfully installed
simply go to: https://forum.xda-developers.com/s7-edge/development
There you will find many Nougat 7 custom roms.
I would suggest not to flash any of the unofficial
nougat 7 roms though, they are not complete and
have many bugs and other issues.
There are about 3-4 really good Nougat 7 roms in the above link
to choose from.
You won't need Odin to flash any of the custom roms and it's a lot
easier to flash. All the zip file custom roms are flashed via twrp.
Good luck, have a great day!