please help before I brick it - Galaxy S 5 Q&A, Help & Troubleshooting

please help before I brick it - Galaxy S 5 Q&A, Help & Troubleshooting

good evening
I am in a bit of tight spot
and before a srew it up (more) I wonder if you could help
I have a SM-G900V which is rooted and I had TWRP working just fine
I tried to flash a rom (project infinity) with aroma which freezed on installing aroma
the developer replied to me that the problem was from TWRP which had a bus and that I should instal CWP
I tried to install CWP on top of TWRP through ODIN and got a failure message
as of now I have neither TWRP or CWP or any rom flashed in mydevice
once I go into recovery mode and try to flash the previous rom that I had through the sdcard it says "footer is wrong signature fail" an reboots and gets stuck with no rom
just tried to reinstall TWRP through ODIN and got the failure message again
with the folowing message:
<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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth) <OSM> All threads completed. (succeed 0 / failed 1)
please help

Hey man,
Sounds like you're in a bit of a pickle. Not sure if this would be a bit extreme, but I'd download the stock firmware and flash it through Odin. After that, reflash recovery and retry your rom.
I kind of see flashing back to stock a 'fail safe' in most cases, so it's always handy to have the stock firmware stored somewhere anyway. ?
Sent from my SM-G900I

..

fffft said:
Don't flash anything until someone discerns what went wrong..
being impatient at this point will put you at high risk of bricking or worse.
The phone boots normally up until the footer error?
What is the exact error message that you see?
What version of TWRP did you have?
Any backups? If so, do they include your baseband, EFS & PIT?
16 GB ROM?
Did you have a Verizon ROM when this happened?
Rooted?
.
Click to expand...
Click to collapse
let me start by thank you for your time!
I am a bit new to all this, I have flashed some roms in the past so I am also familiar with some stuff...
The phone doesn't boot it gets stuck like the attached picture, the OS doesn't start.
I don't see any message as it is stuck like I mentioned before, I just saw a message of "FAIL!" in Odin when I tried to install CWM on top of TWRP
my version of TWRP was 2.7.1.0
I had a backup on TWRP but as I dont see TWRP working anymore I dont know if its still available
my phone is 16GB
my SM-G900V is rooted and at the moment I had working perfectly SpeedROM v1 Rev2
if you would like to contact me through chat let me know, and again thank you very much!!

Try this
..

fffft said:
Okay, on the positive side there isn't anything to suggest that your bootloader is corrupt which would make this a lot harder. Probably the failed aroma install just messed your kernel up. But I don't want to recommend messing around with shortcut solutions e.g. just flashing the kernel that may or may not work, but would put you at unnecessary further risk.
The earlier suggestion to flash a full stock image is generally sound advice, but it does not apply to all situations. My questions were basically aimed at getting a sense of whether you have corrupted the bootloader or partitioning which has a bearing on how to best recover your phone.
First, I am assuming that you do not have the Dev (unlocked bootloader) version S5. If you have the Dev edition with the unlocked bootloader, do not proceed with the rest of this post until we discuss that.
On the assumption that you have a regular 16 GB Verizon SM-G900V S5, then I would like to see you Odin flash a full stock S5 Verizon image that has been rooted. Unfortunately I couldn't find anyone who has made and posted a stock rooted Verizon S5 image like that. I don't mean a stock rooted (custom) ROM.. I mean the full stock firmware image, including the bootloader, but rooted.
That's fine. The rooted part would just be a little extra insurance put against theoretical possible snags i.e. Knox issues. So I will suggest that you use Odin to flash a full stock Verizon S5 image, with an explicit partition table. Normally we don't touch the partition information (PIT) in Odin, but in your case we need to.
Download the files below from this thread
Unless you already have the file on your PC
Verizon S5 Retail Tar 4.4.2 NCG baseband and Mar 31 kernel
MD5: 699a949b57c771b00db9f3ed675c7a5e
NCG Pit
MD5: 3dd82f91a02c82e60e0a1f9964fdb5c0
Odin 3.09
MD5: 810ad286967d0a33881fd8181d35959f
You should thank the OP in that thread for collating the files that you need in one place.
Particularly that all important PIT file.
Start Odin and check these three boxes only: Auto reboot, Re-Partition, F. Reset Time
Choose the PIT file in the PIT window. Note that the PIT file needs to be extracted. Do not leave it zipped.
Choose the stock firmware tar.md5 file in the PDA window. The tar.md5 file needs to remain tarred i.e. tar.md5 or .tar
Put your phone into download mode. Ensure that your phone is off, remove the battery for a few seconds if necessary, then press volume down + home + power until you see the android robot screen come up. If it doesn't go into download mode, repeat these steps. And in the very unlikely event that you can't get into the download mode at all, stop and post that information
Connect your phone to your PC, Odin should say that it has detected your phone
Press start and let Odin flash your phone
Basically we are replacing all of the system files and assuring that your partitioning has not been corrupted
When Odin finishes with a success message your phone should be back to normal. Do a normal reboot to confirm
If you did not backup your phone, your user files in the /data partition might still be accessible
Decide if you wish to back them up or not. Do so if you need them. Then do a factory reset from the Settings menu
You will need to re-root and reinstall your apps, etc
If you run into any difficulties:
If the Odin write fails, note the error message and double check that your Odin settings were correct
Do not close Odin. Pull the battery from your phone for ten seconds.
Then replace the battery and go into download mode again (vol down + home + power)
Note whether Odin detects the phone
Then try flashing with Odin again. Note that you are not closing the Odin program if the first flash attempt fails
Odin can be a bit picky and it is not unheard of to have to reset the phone like this and run the session a second time
Odin is also picky about USB cables. If you still continued trouble, try a different USB cable and USB port
Don't despair if anything goes astray. There is almost always an alternate way to go about something.
Let us know your results so that we can (hopefully) celebrate. Or at least regroup.
.
Click to expand...
Click to collapse
you senior member??? pppffffffff
you should OWN this forum!!! thanx a lot for your extended time in this explanation mate, I will proceed and let you know

Agreed. I use a Dell and sometimes I have problems with odin using the front usb. I have to use the read usb and then no problems.

Hi Guys!!
I am back, back with my phone completely restored
A special THANX to fffff for your help!!

..

Related

[Q] hyperdrive rls12 install problems

Hello peeps a Happy New Year to all!
I tried searching the forums and google but no luck on my case. I am trying to install hyperdrive and am following instructions, downloaded files multiple times on multiple computers and i337m itself. Aroma opens fine and works through fine untill it tries to flash kernel it says:
flashing kernel
file_getprop: failed to stat "/tmp/aroma/kernel.prop": No such file or directory.
So I thought it was just missing a kernel, so continued and installed the att compatibility pack and all i get is ODIN/download mode. I then tried flashing kstoonez kernel and same thing.
I am using Philz Touch latest version on Canadian s4
Any ideas?

The_SilverOne said:
Hello peeps a Happy New Year to all!
I tried searching the forums and google but no luck on my case. I am trying to install hyperdrive and am following instructions, downloaded files multiple times on multiple computers and i337m itself. Aroma opens fine and works through fine untill it tries to flash kernel it says:
flashing kernel
file_getprop: failed to stat "/tmp/aroma/kernel.prop": No such file or directory.
So I thought it was just missing a kernel, so continued and installed the att compatibility pack and all i get is ODIN/download mode. I then tried flashing kstoonez kernel and same thing.
I am using Philz Touch latest version on Canadian s4
Any ideas?
Click to expand...
Click to collapse
The kernel message was no problem for me.using safe strap?
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

the kernel error is common just proceed as you did
did you wipe all including system before flashing? i don't usually wipe in aroma unless no choice given
did you choose your correct carrier--who is your carrier--that info helps us tp help you--
i don't have i337m so can't be specific on things relating to that phone. you say i337m and i337 is in your sig
if you have i337 you need to flash loki-doki after rom
maybe try twrp--i use 2.5.0.2--i have, and there is a flashable zip for it (i337)
got to go for now--

rugmankc said:
the kernel error is common just proceed as you did
did you wipe all including system before flashing? i don't usually wipe in aroma unless no choice given
did you choose your correct carrier--who is your carrier--that info helps us tp help you--
i don't have i337m so can't be specific on things relating to that phone. you say i337m and i337 is in your sig
if you have i337 you need to flash loki-doki after rom
maybe try twrp--i use 2.5.0.2--i have, and there is a flashable zip for it (i337)
got to go for now--
Click to expand...
Click to collapse
Thank you both for your replys, your help is very much appreciated.
So I wiped it with recovery not aroma.
Carrier is Fido (Rogers subsidiary)
Phone is Canadian S4 variant (SGH-I337m) I believe it is the same as i337 (The m being a canadian designation) but don't quote me on that.
I was under the assumption that Canadian s4 Didn't need lokidoki.
Can you elaborate on safestrap?
No matter what I try it goes boots to download mode. Even if I plug it in to charge not pressing any power button.

Canadian s4 doesnt need loki doki. And your not on safestrap if you have twrp.
As far as your problem. Did it complete the install of the rom even after it said it failed the kernel?
I suggest installing then flashing a 4.3 tw kernel for your device before rebooting system. You shouldn't need a compatibility pack as your not att. Plus im pretty sure the compat pack has loki in it which may cause problems. I also remember philz recovery as having auto loki. So I dont know if you've used philz recovery b4 successfully. If you haven't then id suggest trying twrp. Definitely just try a kernel for your device though. Ktoons worked for me. Other kernels left me stuck at spash screen

SelfElevated2 said:
Canadian s4 doesnt need loki doki. And your not on safestrap if you have twrp.
Click to expand...
Click to collapse
I believe that my phone's bootloader is unlocked (as with most other jtflecan models), but again don't quote me. As a result I have never used safestrap. Should/could I still use it if my bootloader is unlocked?
SelfElevated2 said:
As far as your problem. Did it complete the install of the rom even after it said it failed the kernel?
Click to expand...
Click to collapse
It seemed that way as that was the only error, and aroma proceeded through. First time I tried without the ATT compatibility pack, no go, then with and still no go. Then i tried with a few kernels and same thing.
SelfElevated2 said:
I suggest installing then flashing a 4.3 tw kernel for your device before rebooting system. You shouldn't need a compatibility pack as your not att. Plus im pretty sure the compat pack has loki in it which may cause problems. I also remember philz recovery as having auto loki. So I dont know if you've used philz recovery b4 successfully. If you haven't then id suggest trying twrp. Definitely just try a kernel for your device though. Ktoons worked for me. Other kernels left me stuck at spash screen
Click to expand...
Click to collapse
I transitioned from cwm to philz for ntfs capability as my external sdcard is ntfs. I remember reading somewhere that autoloki was not included and some have complained about it so im not sure if it was added in a later build. In any case I just tried flashing twrp and got a mushy brick.
Now Im curious if I should restore to original and use safestrap or what as my phone does nothing but odin mode.
As always thanks for your valued input.

Your boot loader is definitely not locked. If it was you wouldnt have a custom recovery. So you don't need safestrap. Just restore and reroot and get a recovery. What you put on your phone after that is up to you. I know hyperdrive wouldn't boot for me with most kernels it was just stuck on the splash screen. But it booted for kt kernel. I would honestly find another Rom if I was in the same position

MINI UPDATE:
Phone was bootlooping so I tried to restore to stock 4.2.2 but ODIN failed continuously. Tried 4.3 stock (mk6) and odin failed, tried older odin and succeeded but it bootlooped and went to the kies upgrade error. Tried multiple Computers (2PC 1OSX) multiple ports and cables and all failed.
Trying to figure this out but not much help out there with regards to canadian s4, att guides ok? any suggestions? trying kies restore now but kies hangs after it downloads firmware. urgh
ODIN Outuput:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUEMK6_I337MOYAEMK6_I337MVLUEMK6_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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> __Xmit Write fail
<ID:0/003> XmitData Fail..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Added!!
ODIN seems to fail at different points, sometimes in recovery, or modem or etc.
do i need to repartition?if so where do i find the pit file for my device?
im reading that im screwed and praying its not true.
Thanks for any help

You cant get into recovery? Only odin? Just keep looking around. I bet its because the aroma flashed a incomplete flash. But I dont know the difference between i337 and i337m so I dont know what to tell you. I suggest keep trying to Odin. If it doesn't work I believe theres a tool to force a stock image onto the phone but I cant remember what its called

SelfElevated2 said:
You cant get into recovery? Only odin? Just keep looking around. I bet its because the aroma flashed a incomplete flash. But I dont know the difference between i337 and i337m so I dont know what to tell you. I suggest keep trying to Odin. If it doesn't work I believe theres a tool to force a stock image onto the phone but I cant remember what its called
Click to expand...
Click to collapse
no i only get odin.
phone only turns on when plugged in to usb on pc, otherwise unresponsive to hardkeys.
Every instance of ODIN flashing fails. No matter which firmware or computer i used, either write failure or PIT failure. both of which im attributing to an incomplete flash, and its making me think that the partition tables are chewed.
im stumped and phonless
any idea what that app was called? google yields no results
thanks for your help

Heres something to read. I dont know if you need the.Canadian pit or reg att pit. Dont just flash one. Get informed first
http://www.droidviews.com/how-to-unbrick-your-bricked-samsung-galaxy-s4-gt-i9500-gt-i9505/

SelfElevated2 said:
Heres something to read. I dont know if you need the.Canadian pit or reg att pit. Dont just flash one. Get informed first
http://www.droidviews.com/how-to-unbrick-your-bricked-samsung-galaxy-s4-gt-i9500-gt-i9505/
Click to expand...
Click to collapse
Thank you very much for that link. It summed up everything i have been reading for the past 24 hours, but alas i have yet to figure out which pit to use, whether I can use the att pit, wind (different provider, uses aws (2 different frequencies from gsm standard) as opposed to gsm although they may have changed that recently),find a rogers pit, since they and fido are essentially the same network or continue searching for a fido pit.
Knowing what the pit does, would it really be carrier specific (asides from the difference in radios between fido/rogers and wind)? Is it ROM version and android version specific?

Update:
-Have Tried all options for recovery in KIES on multiple Pcs and Multiple Macs
-Download/Odin Mode Reads:
ODIN MODE
PRODUCT NAME: SGH-I337M
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB; 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE: enabled
START [224,1440]
BAR [240,1440
Questions:
Before this whole fiasco ODIN didnt show KNOX. I assume thats from the 4.3 revert i tried?
Does Write Protection have anything to do with it? I do recall being able to odin flash with this before.
eMMC Burst is new to me, havent seen this before
BAR pops up before failing but not seconds before, maybe a minute before.
Still Stumped
Edit: Even if i were to find the pit file, i cant seem to find modem, csc, and bootloader to add to odin. (unless they are all combined in that md5 file) so i wouldnt be able to flash until having all the necessary items as pit rewrites the partitions and all data is lost.
i also remembered one odd thing, may or may not apply here, but just before flashing to hyperdrive, i was not able to properly format. it would take a few tries to format data or whichever for example, before files were actually gone.
tried reverting to MDJ got vibrate loop
trying again to MK6

The_SilverOne said:
Hello peeps a Happy New Year to all!
I tried searching the forums and google but no luck on my case. I am trying to install hyperdrive and am following instructions, downloaded files multiple times on multiple computers and i337m itself. Aroma opens fine and works through fine untill it tries to flash kernel it says:
flashing kernel
file_getprop: failed to stat "/tmp/aroma/kernel.prop": No such file or directory.
So I thought it was just missing a kernel, so continued and installed the att compatibility pack and all i get is ODIN/download mode. I then tried flashing kstoonez kernel and same thing.
I am using Philz Touch latest version on Canadian s4
Any ideas?
Click to expand...
Click to collapse
Hi, I am currently having this problem after trying to install RLS15.
After trying to flash the new ROM, phone would not boot, and I was no longer able to install ROMS or Restore backups.
When I would try to restore a backup, it would get to Restoring Data, and immediately fail.
When installing the ROM and its kernel, I got the same message as you:
flashing kernel
file_getprop: failed to stat "/tmp/aroma/kernel.prop": No such file or directory.
I've tried:
flashing kernels before flashing the ROM
re-install of Loki + TWRP + Motochopper Casual (Did not revert back to stock before doing this)
flashing the AT&T Compatibility pack.zip for RLS15 Before and After flashing the ROM
Fixing permission
I've noticed once or twice, when trying to restore a backup, a message in TWRP saying that SuperUser was not installed, and it asked if I wanted to install it. So I did the "Swipe to install" in TWRP, but the phone quickly reboots and again doesn't get passed the boot logo.
Sooo, I'm not too sure where to start on this one

d9vabder said:
Hi, I am currently having this problem after trying to install RLS15.
After trying to flash the new ROM, phone would not boot, and I was no longer able to install ROMS or Restore backups.
When I would try to restore a backup, it would get to Restoring Data, and immediately fail.
When installing the ROM and its kernel, I got the same message as you:
flashing kernel
file_getprop: failed to stat "/tmp/aroma/kernel.prop": No such file or directory.
I've tried:
flashing kernels before flashing the ROM
re-install of Loki + TWRP + Motochopper Casual (Did not revert back to stock before doing this)
flashing the AT&T Compatibility pack.zip for RLS15 Before and After flashing the ROM
Fixing permission
I've noticed once or twice, when trying to restore a backup, a message in TWRP saying that SuperUser was not installed, and it asked if I wanted to install it. So I did the "Swipe to install" in TWRP, but the phone quickly reboots and again doesn't get passed the boot logo.
Sooo, I'm not too sure where to start on this one
Click to expand...
Click to collapse
What variant do you have?

So I figured out my problem. In TWRP recovery, I went to mounts, and mounted my micro SD card. It was mounted to internal memory and I guess that was screwing up flashes. Hope this works for you too!
Sent from my SAMSUNG-SGH-I337 using xda premium

ODIN Nand Erase All

What does this option do if i select it and use ODIN???
Will this Erase my phone content along with internal memory???
My Verizon Note 3 is Sim unlocked...so will this option lock my device???
(Updated: Actually all Verizon Note 3 are Sim Unlocked, so no worries there)
EDIT:
Well i finally did it...Thanks to our XDA member @mirek190 for clarifying the use of those options and guiding me through the steps...All credit goes to him...
He explains:
Pit file setup partitions - very useful if you broke some partition...Nand Erase All clean all partitions including internal sdcard before installing rom...EFS ( block 11 ) on note 3 doesn't contain IMEI ( all devices on snapdragon ).
IMEI is on block 12 and 13. If you clean efs, the partition will be rebuild from block 12.
So you can check the options Re-partition, Nand Erase All and also Phone EFS Clear to do clean Wipe...and make sure you have the PIT file of the respective device and STOCK ROM.
Click to expand...
Click to collapse
I successfully did Clean Wipe and Erased User Data Partition on my Note 3 using Nand Erase All , Re-partition & Phone EFS Clear in ODIN 3.09...using Pit file and Stock ROM.
Note: I never had any problems in my Note 3 but i just wanted to a perform a clean Wipe of my Note 3
First we need ODIN latest version 3.09...
ODIN 3.09 : http://d-h.st/cEk
Then we need a pit file to put in PIT button in ODIN...
Pit file for Verizon Note 3 32 GB : http://www.androidfilehost.com/?fid=23159073880936457
Pit file Thread: http://forum.xda-developers.com/showthread.php?t=2484064
Then we need a STOCK ROM to put in AP button in ODIN...
(Note: Please make sure that the Stock ROM which u use to flash in ODIN is the same as the current bootloader in your device or newer.If you are on MJE bootloader then u can use MJE or NC4 Stock ROM and if you are already on NC4 bootloader then you can use only the NC4 Stock ROM or any newer Stock ROM than NC4 but cant use the older MJE Stock ROM.)
Stock ROMs Collection: http://forum.xda-developers.com/showthread.php?t=2524572
Thanks to @BeansTown106 for the Pit file & Stock ROMs...
Then put the device in Download Mode and connect it to PC...Check the status in ODIN after connecting...
Then select the options Auto Reboot, F.Reset Time, Nand Erase All, Re-partition & Phone EFS Clear in ODIN...
Put Pit file in PIT button and Stock ROM in AP button...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Make sure all settings in ODIN looks the same like in above image...ID:COM should show the device connection status...
Then click on start and let ODIN do the magic...you can also see the status "Erasing User Data Partition" in your phone in download mode...
After the Process completes the device Auto reboots and do not unplug the device until the status in ODIN is Pass...
(Note: If you are using 4.4.2 NC4 Kitkat Stock ROM in ODIN, then when the device auto reboots after flashing it doesnt initialise ever and gets stuck on the Verizon Logo, this is happening only with Kitkat firmware...So when ODIN Auto reboots the device after flashing we have to wait till the status is Pass and Exit option is highlighted in ODIN, then Unplug the device, remove the battery, Power on the device, go into recovery mode, perform Factory Reset Data, Wipe Cache Partition and reboot it.)
After first boot of the ROM, go into Stock Recovery mode and "Wipe Factory Reset/Data and Wipe Cache Partition" (Must step)
Now your Note 3 is Clean Wiped and installed with fresh STOCK ROM...
My Knox is also not tripped 0x0 and my sim is also Unlocked as before...
PS: So i think it is useful to do a Clean Wipe (Re-partition, Nand Erase All, Phone EFS Clear) only when
1) Your Partition is broken.
2) Your device is soft bricked.
3) You want to sell your phone.
4) Upgrading the firmware or bootloader (Like MI9 to MJ7, MJ7 to MJE or MJE to NC4)
5) Once in a while because of flashing Stock/Custom ROMS many times using ODIN or Safestrap...
And don't do clean wipe often because erasing the Nand often will degrade its quality...
Thanks for the help brothers...:good:

moin786 said:
What does this option do if i select it and use ODIN???
Will this Erase my phone content along with internal memory???
My verizon device is Sim unlocked...so will this option lock my device???
Click to expand...
Click to collapse
I found this if it helps http://forum.xda-developers.com/showthread.php?t=1747066&page=4 there is some good info in the last few posts.

Misterxtc said:
I found this if it helps http://forum.xda-developers.com/showthread.php?t=1747066&page=4 there is some good info in the last few posts.
Click to expand...
Click to collapse
Can i use this option and flash my device???
Will it work on Locked Bootloader???

Clean Wipe & Erasing Userdata Partition in Note 3
Well i finally did it...Thanks to our XDA member @mirek190 for clarifying the use of those options and guiding me through the steps...All credit goes to him...
He explains:
Pit file setup partitions - very useful if you broke some partition...Nand Erase All clean all partitions including internal sdcard before installing rom...EFS ( block 11 ) on note 3 doesn't contain IMEI ( all devices on snapdragon ).
IMEI is on block 12 and 13. If you clean efs, the partition will be rebuild from block 12.
So you can check the options Re-partition, Nand Erase All and also Phone EFS Clear to do clean Wipe...and make sure you have the PIT file of the respective device and STOCK ROM.
Click to expand...
Click to collapse
I successfully did Clean Wipe and Erased User Data Partition on my Note 3 using Nand Erase All , Re-partition & Phone EFS Clear in ODIN 3.09...using Pit file and Stock ROM.
Note: I never had any problems in my Note 3 but i just wanted to a perform a clean Wipe of my Note 3
First we need ODIN latest version 3.09...
ODIN 3.09 : http://d-h.st/cEk
Then we need a pit file to put in PIT button in ODIN...
Pit file for Verizon Note 3 32 GB : http://www.androidfilehost.com/?fid=23159073880936457
Pit file Thread: http://forum.xda-developers.com/showthread.php?t=2484064
Then we need a STOCK ROM to put in AP button in ODIN...
(Note: Please make sure that the Stock ROM which u use to flash in ODIN is the same as the current bootloader in your device or newer.If you are on MJE bootloader then u can use MJE or NC4 Stock ROM and if you are already on NC4 bootloader then you can use only the NC4 Stock ROM or any newer Stock ROM than NC4 but cant use the older MJE Stock ROM.)
Stock ROMs Collection: http://forum.xda-developers.com/showthread.php?t=2524572
Thanks to @BeansTown106 for the Pit file & Stock ROMs...
Then put the device in Download Mode and connect it to PC...Check the status in ODIN after connecting...
Then select the options Auto Reboot, F.Reset Time, Nand Erase All, Re-partition & Phone EFS Clear in ODIN...
Put Pit file in PIT button and Stock ROM in AP button...
Make sure all settings in ODIN looks the same like in above image...ID:COM should show the device connection status...
Then click on start and let ODIN do the magic...you can also see the status "Erasing User Data Partition" in your phone in download mode...
After the Process completes the device Auto reboots and do not unplug the device until the status in ODIN is Pass...
(Note: If you are using 4.4.2 Kitkat Stock ROM in ODIN, then when the device auto reboots after flashing it doesnt initialise ever and gets stuck on the Verizon Logo, this is happening only with Kitkat firmware...So when ODIN Auto reboots the device after flashing we have to wait till the status is Pass and Exit option is highlighted in ODIN, then Unplug the device, remove the battery, Power on the device, go into recovery mode, perform Factory Reset Data, Wipe Cache Partition and reboot it.)
After first boot of the ROM, go into Stock Recovery mode and "Wipe Factory Reset/Data and Wipe Cache Partition" (Must step)
Now your Note 3 is Clean Wiped and installed with fresh STOCK ROM...
My Knox is also not tripped 0x0 and my sim is also Unlocked as before...
PS: So i think it is useful to do a Clean Wipe (Re-partition, Nand Erase All, Phone EFS Clear) only when
1) Your Partition is broken.
2) Your device is soft bricked.
3) You want to sell your phone.
4) Upgrading the firmware or bootloader (Like MI9 to MJ7, MJ7 to MJE or MJE to NC4)
5) Once in a while because of flashing Stock/Custom ROMS many times using ODIN or Safestrap...
And don't do clean wipe often because erasing the Nand often will degrade its quality...
Thanks for the help brothers...:good:

Thanks for sharing the info with the Nand. From the looks of the thread I linked to you it looked like a No No but your findings tell different. I tried it too to verify and it works well with no bad effects.

So this does a REAL full wipe?
I ask because I've ODIN'd many times already for various reasons and afterwards, even doing a factory reset, there were still some leftover files in the /root folders. Specifically the efs folder where I had made .bak files from mods.
Selling my phone soon and want to make sure it is TRULY 100% stock.

Since we're talking PIT files and Odin, I am curious:
I have flashed MJE tar in Odin and never used a PIT file (PIT box remained unchecked and no file was loaded at any time during Odin)..
My question is: if the PIT file configures partitions, and I didn't use the PIT file, SHOULD I be having issues with my int sdcard because I am not having ANY issues with it...
If I am supposed to use PIT file and didn't, should I be expecting issues down the road?
I kinda understood that the PIT was only needed to CHANGE standard configuration of partitions...
A little PIT file / partition schooling would be great so I know one way or the other for future Odin use... THANKS!

moin786 said:
Well i finally did it...Thanks to our XDA member "mirek190" for clarifying the use of those options and guiding me through the steps...All credit goes to him...
Click to expand...
Click to collapse
As long as you are giving credit, how about including a URL to his post(s) that you used?
(If @mirek190 helped you via PM or off of XDA, then please disregard this inquiry.)
carlz28 said:
So this does a REAL full wipe?
I ask because I've ODIN'd many times already for various reasons and afterwards, even doing a factory reset, there were still some leftover files in the /root folders. Specifically the efs folder where I had made .bak files from mods.
Selling my phone soon and want to make sure it is TRULY 100% stock.
Click to expand...
Click to collapse
Someone would probably have to look at slack space at the end of partitions to determine that; reason being is that we don't have a good way to boot the device in a "blank" state, but only after a bunch of stuff has already been re-written by Odin. (On other Android devices with unlocked bootloaders, it is easy: you just soft-boot a recovery using fastboot, and then talk to the in-memory-only recovery using ADB to do raw dumps of the various partitions).
If you could write something into a partition (e.g. dd seek=...) SAFELY skipping over important stuff at the front end, you could look for it after an Odin install. (Maybe the PAD or FOTA partitions would be a safe place to do this).
It might just re-partition only. Or, in the case of ext4 filesystem formatting, only the space used by the filesystem overhead (journal, superblocks, inode tables,etc) gets re-written and "trash" with your old data can still exist in unallocated space. (Seems like flash memory wear-leveling should make complete erasure desirable - but with a penalty of an annoying delay).
Any clues from the Odin erase times? The fastest I've been able to *read* from the N3's memory is about 110 MB/sec, and I would think erasures would take longer - at that kind of speed a full erase of 32 GB would take nearly 5 minutes just to perform the erase.
The EFS thing you mention is a little odd - unless you were flashing an Odin tarball file without an image file corresponding to the EFS partition, and the partitioning by the PIT stayed identical. In that case, /data would be wiped (or maybe more precisely the /data partition would have it's ext4 filesystem re-built), but since the /efs is a mount (ext4, rw) of a separate partition, it could survive with those conditions.

Misterxtc said:
Thanks for sharing the info with the Nand. From the looks of the thread I linked to you it looked like a No No but your findings tell different. I tried it too to verify and it works well with no bad effects.
Click to expand...
Click to collapse
I am glad that this post helped u too...actually in the beginning i was also scared to use all those options, but after reading whole forum and asking developers and an experienced guy who actually did this...i can confirm that it is the best way to Clean Wipe and Erase User data partition of our Note 3...because other methods such as Wipe Factory Reset fail to do so...
Cheers!!!

carlz28 said:
So this does a REAL full wipe?
I ask because I've ODIN'd many times already for various reasons and afterwards, even doing a factory reset, there were still some leftover files in the /root folders. Specifically the efs folder where I had made .bak files from mods.
Selling my phone soon and want to make sure it is TRULY 100% stock.
Click to expand...
Click to collapse
Yes brother it really does Full Clean Wipe...If u want to sell your phone...this is the best way to bring it to 100% Stock...
@mirek190 is an experienced developer and has personally did it on his Note 3 many times, he explained me about it
Pit file setup partitions - very useful if you broke some partition...Nand Erase All clean all partitions including internal sdcard before installing rom...EFS ( block 11 ) on note 3 doesn't contain IMEI ( all devices on snapdragon ).
IMEI is on block 12 and 13. If you clean efs, the partition will be rebuild from block 12.
So you can check the options Re-partition, Nand Erase All and also Phone EFS Clear to do clean Wipe...and make sure you have the PIT file of the respective device and STOCK ROM.
Click to expand...
Click to collapse
Don't be afraid...you wont face any problems...just do it...and share your experience...
Cheers!!!

az_biker said:
Since we're talking PIT files and Odin, I am curious:
I have flashed MJE tar in Odin and never used a PIT file (PIT box remained unchecked and no file was loaded at any time during Odin)..
My question is: if the PIT file configures partitions, and I didn't use the PIT file, SHOULD I be having issues with my int sdcard because I am not having ANY issues with it...
If I am supposed to use PIT file and didn't, should I be expecting issues down the road?
I kinda understood that the PIT was only needed to CHANGE standard configuration of partitions...
A little PIT file / partition schooling would be great so I know one way or the other for future Odin use... THANKS!
Click to expand...
Click to collapse
I also used to flash MJE tar in ODIN and never use PIT file...because
1) It is not needed if ur purpose is only to flash STOCK ROMS...
2) Don't worry your current partitions will have no issues if u dont use PIT file while flashing STOCK ROM...but if u select the option Re-partition in ODIN and then don't use PIT file in PIT button then you will have problems with your partitions...and later u must use PIT file to Re-partition your device.
A PIT contains the Partitions details of the respective device and is only used :
1) When u want to Re-partition your device and Flash STOCK ROM in ODIN...
2) When u want to Re-partition & Perform Full Clean Wipe using Nand Erase All and then Flash STOCK ROM in ODIN...
thats why when u put the PIT file in PIT button the Re-partition is automatically checked...
Also If you want use the Nand Erase All option only then also you need PIT file because Nand Erase wipes the contents of the partitions and it uses PIT file to read the partitions details of our device...
Thats why don't use the option Nand Erase All without having PIT file because it will Brick your device...
@mirek190 is an experienced developer and has personally did it on his Note 3 many times,he explained me:
Pit file setup partitions - very useful if you broke some partition...Nand Erase All clean all partitions including internal sdcard before installing rom...EFS ( block 11 ) on note 3 doesn't contain IMEI ( all devices on snapdragon ).
IMEI is on block 12 and 13. If you Clean EFS, the partition will be rebuild from block 12.
So you can check the options Re-partition, Nand Erase All and also Phone EFS Clear to do clean Wipe...and make sure you have the PIT file of the respective device and STOCK ROM
Click to expand...
Click to collapse
So when u add the STOCK ROM in AP Button and if u check the Re-partition option without having Pit file...it may break your partition and your device may Boot loop...So PIT file is mandatory while doing Re-partition or Nand Erase All...
And Regarding Phone EFS Clear i had no idea what it is...I just didnt wanna lose my IMEI information and Unlocked Sim after Re-partition and Nand Erase...
So @mirek190 told me to clear Phone EFS also to perform clean wipe... and i wont lose any information...as it is completely safe because ODIN doesnt wipe IMEI details...
So you guys can even check the option Phone EFS Clear...
PS: So i think it is useful to do a Clean Wipe (Re-partition, Nand Erase All, Phone EFS Clear) only when
1) Your Partition is broken.
2) Your device is soft bricked.
3) You want to sell your phone.
4) Upgrading the firmware or bootloader (Like MI9 to MJ7, MJ7 to MJE or MJE to NC4)
5) Once in a while because of flashing Stock/Custom ROMS many times using ODIN or Safestrap...
And don't do clean wipe often because erasing the Nand often will degrade its quality...
And always make sure that you have the right PIT file and STOCK ROM...
Cheers!!!

bftb0 said:
As long as you are giving credit, how about including a URL to his post(s) that you used?
(If @mirek190 helped you via PM or off of XDA, then please disregard this inquiry.)
Click to expand...
Click to collapse
I had interaction with him mainly via PM...
I read his entire thread on how to recover Note 3 if Soft bricked...
http://forum.xda-developers.com/showthread.php?t=2567133
In the above thread he is working on his Bricked Note 3 and he has mentioned the symptoms also...
We dont have to run the adb commands mentioned in his thread...because we will lose the IMEI and Phone information if we follow the steps in his OP...
If we just follow the steps mentioned in my OP (Opening Post) then that is enough to clean wipe Note 3...
Cheers!!!

Just did it on my Canadian Note 3 N900W8 with Rogers 4.4.2. The first boot didn't initialize for 10 minutes so I went into stock recovery and wipe data, wipe cache and reboot and it loaded fine.
edit: Here's the full result from Odin's message box:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900W8VLUCNB7_N900W8OYACNB7_N900W8VLUCNB7_HOME.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> Erase...
<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> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl1.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> cache.img.ext4
<ID:0/005> modem.bin
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
edit: Also attached the PIT file I used for the N900W8

If i do this the reactivation lock turn to off ?
and no more samsung account for the first startup ?
its any way to bypass rl ?

bleuwave said:
Just did it on my Canadian Note 3 N900W8 with Rogers 4.4.2. The first boot didn't initialize for 10 minutes so I went into stock recovery and wipe data, wipe cache and reboot and it loaded fine.
edit: Here's the full result from Odin's message box:
edit: Also attached the PIT file I used for the N900W8
Click to expand...
Click to collapse
Cheers mate...i am glad this method helped u too!!! Yes when the device auto reboots after flashing, it doesnt initialise ever and gets stuck on the Verizon Logo, this is happening only with Kitkat firmware...So when ODIN Auto reboots the device after flashing we have to wait till the status is PASS and Exit option is highlighted in ODIN, then Unplug the device, remove the battery, Power on the device, go into recovery mode, perform Factory Reset Data, Wipe Cache Partition and reboot it.
Thanks!!!

Hey guys,
I was on 4.4.2 from the verizon OTA. I rooted using towel root but I still wanted to change to jasminROM. Unfortunately, this method got me stuck in the broken android screen (download mode) and I had to repair using the verizon upgrade software.
This resulted because Odin had a NAND WRITE Fail error when I was flashing the stock MJE rom. Is there anything I can do to load the leaked NC2/4 bootloader?

neur0t0xin64 said:
Hey guys,
I was on 4.4.2 from the verizon OTA. I rooted using towel root but I still wanted to change to jasminROM. Unfortunately, this method got me stuck in the broken android screen (download mode) and I had to repair using the verizon upgrade software.
This resulted because Odin had a NAND WRITE Fail error when I was flashing the stock MJE rom. Is there anything I can do to load the leaked NC2/4 bootloader?
Click to expand...
Click to collapse
Once you have taken the 4.4.2 NC4 OTA...you cant ODIN back to MJE firmware using any method because we can't downgrade our bootloader from NC4 to MJE...

moin786 said:
Once you have taken the 4.4.2 NC4 OTA...you cant ODIN back to MJE firmware using any method because we can't downgrade our bootloader from NC4 to MJE...
Click to expand...
Click to collapse
What about the leaked NC4?

neur0t0xin64 said:
What about the leaked NC4?
Click to expand...
Click to collapse
We have two things Leaked NC2 and Official NC4, there is nothing like leaked NC4...
Because u have taken NC4 OTA...your bootloader is fixed to NC4 now and cant be downgraded to NC2 or MJE...
I think you can do one thing, which is flash the leaked NC2 kernel in ODIN on the NC4 firmware and then you can use the Jasmine ROM on your device because Jasmine ROM needs NC2 Kernel...
Leaked NC2 Kernel : http://www.androidfilehost.com/?fid=23501681358549122

moin786 said:
We have two things Leaked NC2 and Official NC4, there is nothing like leaked NC4...
Because u have taken NC4 OTA...your bootloader is fixed to NC4 now and cant be downgraded to NC2 or MJE...
I think you can do one thing, which is flash the leaked NC2 kernel in ODIN and then you can use the Jasmine ROM on your device because Jasmine ROM needs NC2 Kernel...
Click to expand...
Click to collapse
Thanks! I'll give that a try.

[Q] Soft Bricked sgh-i337m. Please Help

Please lend a hand to help me rectify a problem.
Started earlier today by CF-Auto-Root my New Rogers SGH-i1337m, installed without incident via Odin 3.07, followed up with TWRP 2.7 install, again via Odin, without incident, then created NANDROID backup to ext sdcard.
First issues started cropping up, but culminating in what appears to be soft bricking:
1st) Could not mount internal memory (was attempting to browse in Windows) via TWRP. Every time I would select internal memory it would mount the sd card contents only. Weird, but pales compared to further issues.
2nd) Was preparing to install Custom ROM, boot into TWRP, attempted factory reset but this just constantly restarted TWRP. Thought this was strange so I figured Id use Goomanager to update TWRP, occurred without incident and I went back to attempt to factory reset, but then trouble started.
3rd) Boot looping, could not boot back into the OS. Decided I would attempt to restore my Nandroid backup, TWRP loads fine but restore didn't work. Figured Id try flashing back to stock rom (obtained RWC-I337MVLUEMK6-20131125124040 via links in other comments. This is where things got out of control:
A) Restore via Odin 3.07 failed, device restart failedbut loaded the "Firmware Upgrade encountered an issue..." screen.
B) Attempted redownloading the stock rom, new usb port, new oem cable, reinstalled drivers, and with each Odin would fail as follows:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUEMK6_I337MOYAEMK6_I337MVLUEMK6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
C) Briefly TWRP would not load, so I reflashed 2.7.0.1 for openrecovery-twrp-2.7.0.1-jfltecan without incident, TWRP reloaded fine, could now do factory reset, but often end up getting could not mount /system. Now using TWRP to restore theNANDRPID from earlier seemed to rebuild the partitions and said it was successful, and the device will boot to a static Samsung screen, but after 20 mins of waiting, would not boot farther.
D) At this point tried to reflash w Odin 3.07 the stock, but still get that error.
So here is where I'm at, with what appears to get me the closest to booting/flashing with stock:
1) Reflashed openrecovery-twrp-2.7.0.1-jfltecan.tar with Odin 3.07, immediately following this:
<ID:0/004> Removed!!
<ID:0/006> Added!!
<ID:0/006> Removed!!
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
..and the device hangs @ "Samsung Galaxy S4" black screen, letting that sit for 15mins without any change (didn't expect it to, but may as well be complete).
2) TWRP is bootable (load screen says Recovery is not SEANDROID ENFORCED and Set Warranty Bit: recovery) and functional, rebooting recovery states "No OS installed, are you sure you want to restart? ". Interestingly with 2.7.0.1 now installed, i can factory reset but with errors "E: unable to mount '/system". In TWRP, i have tried restore of my NANDROID backup, it completes successfully and appears to rebuild the partitions, but even after completing the restore and rebooting, still end up hanging at the static Samsung screen for >20mins without a change. I could transpose the entire log from the restore if needed.
3) At this point I would try Odin 3.07 with the above stock image, and the failure when attempting to write system occurs again.
Ive been searching for hours and hours and attempting to reflash but not making any headway.
Could anyone help point me in some better directions? I just finished attempting KIES emergency restore, but it too failed when it tried to upload to the device.
Any help would be greatly appreciated.

You've done all the right things. The only other thing I can think of is using a different firmware version in Odin.
Sent from my Nexus 5

jd1639 said:
You've done all the right things. The only other thing I can think of is using a different firmware version in Odin.
Sent from my Nexus 5
Click to expand...
Click to collapse
Perhaps I should try flashing a custom rom? Maybe something like CM 10.2?
I think the problem lies with a possible permission problem with the system partition, but I don't know how to go about checking those permissions, let alone correcting a possible fault.
Thoughts?

Did you factory reset in stock recovery before you installed twrp?
Sent from my SGH-I337M using Tapatalk

2Tone5 said:
Did you factory reset in stock recovery before you installed twrp?
Sent from my SGH-I337M using Tapatalk
Click to expand...
Click to collapse
I believe so, but it has been several iterations of different attempts to fix things that I cannot be certain any longer.
Let's pretend I didn't, for arguments sake. Implications?
Furthermore, I have created some life back into the device; however, still having problems.
1) Using ODIN 3.09, I successfully flashed TWRP back on to the device.
2) With TWRP, I successfully flashed CM 10.2. The device loads completely into the OS--the only thing I cannot confirm yet is full telephone functionality as my backup phone is what was reconnected to ROGERS. So.....there is life in this thing yet.
3) With TWRP, I have successfully created NANDROID backup of the device under 10.2 and used it to restore after a few failed attempts at getting to stock.
So here's a problem for right now: No matter what source stock ROM I have been using, I337MVLUFNC1_I337MOYAFNC1_I337MVLUFNC1_HOME.tar.md5 or I337MVLUFNC1_880525_REV06_user_low_ship_MULTI (both are what were claimed to be stock 4.4.2 for sgh-i337m ROGERS), it consistently fails in ODIN when flashing system.
I can easily then reflash TWRP (because the ODIN flashing the above stock breaks the recovery image), get into TWRP and restore the CM10.2 NANDROID, and at least back in business there.
I'm about to try flashing (again, but likely fruitlessly) RWC-I337MVLUEMK6-20131125124040.zip from samsung-updates.com via ODIN 3.09. I don't have much hope that ODIN will get it onto the device.
Seems to me like perhaps ODIN can't get the stock roms onto the device for some reason!? Am I doing something wrong? Perhaps someone can point me to a stock 4.3 (or 4.4.2) ROM for ROGERS SGH-i337M that is known to work (or at least deemed reliable) that I could try? Perhaps ODIN is messed up for me?
I'm pretty frustrated as I would think if I can install via TWRP a custom kernel and custom ROM, I should be able to get the stock ROM/etc. back onto the device.
Perhaps I'm missing a step?
TWRP: Wipe> Factory Reset then wipe Cache.
Reboot into Download Mode
ODIN 3.09: Added!! --> AP Select my stock ROM (any of the above), only have Auto Reboot and F. Reset Time selected, start (then fail in my case).
Perhaps I should find another computer!? I have two OEM cables, tried both ports......
This is ridiculously frustrating.

Which bootloader are you on?
Sent from my SGH-I337M using Tapatalk

Just wanted to say that I got burned by TRWP a few days ago due to the same issues.
1) Flashed a custom kernel days before. Was working fine but didn't like the performance of the new kernel so I decided to restore my backups of /boot and /system.
2) Did the restore. Cleared /cache and dalvik. Reboot.
3) Stuck on the Samsung Galaxy S4 bootloader screen.
4) Tried to reboot into TWRP, but didn't work. Would just cause phone to automatically restart and hang at the bootloader screen.
5) After many many reboots, was able to finally boot into TWRP.
6) Flashed a custom ROM based the original stock ROM I had installed and that got me up and running again. No data loss as I never touched /data with TWRP.
I'm currently experimenting with CWM and Philz. TWRP, never again.

2Tone5 said:
Which bootloader are you on?
Sent from my SGH-I337M using Tapatalk
Click to expand...
Click to collapse
Uncertain at this point -- any way to determine that or just flash a known decent one?
Interestingly: CM10.2.1 everything works except for calls and any other sound on the device. ......this is ridiculous.

bzwick said:
Uncertain at this point -- any way to determine that or just flash a known decent one?
Interestingly: CM10.2.1 everything works except for calls and any other sound on the device. ......this is ridiculous.
Click to expand...
Click to collapse
Upon more research, I guess I have a knox bootloader since I have a Knox 0x1 trip.

bzwick said:
Upon more research, I guess I have a knox bootloader since I have a Knox 0x1 trip.
Click to expand...
Click to collapse
Without knowing exactly, theres more trial and error ... so ill give you an example: you can't flash 4.2.2 firmware.tar.md5 over a 4.4.2 bootloader (which sounds like you may have )in odin anymore due to knox. What I can suggest to you that should work is go to sammobile.com and download the latest 4.4.2 official firmware for the 1337m and follow the instructions precisely on the download page.
Sent from my SGH-I337M using Tapatalk
---------- Post added at 12:14 AM ---------- Previous post was at 12:12 AM ----------
http://www.sammobile.com/firmwares/
Sent from my SGH-I337M using Tapatalk
---------- Post added at 12:16 AM ---------- Previous post was at 12:14 AM ----------
Once you download it and its installed make sure to turn off your phone and boot into stock recovery and do a factory reset and if you really want to be clean flash the firmware again and all your problems should be gone
Sent from my SGH-I337M using Tapatalk

2Tone5 said:
Without knowing exactly, theres more trial and error ... so ill give you an example: you can't flash 4.2.2 firmware.tar.md5 over a 4.4.2 bootloader (which sounds like you may have )in odin anymore due to knox. What I can suggest to you that should work is go to sammobile.com and download the latest 4.4.2 official firmware for the 1337m and follow the instructions precisely on the download page.
Sent from my SGH-I337M using Tapatalk
---------- Post added at 12:14 AM ---------- Previous post was at 12:12 AM ----------
http://www.sammobile.com/firmwares/
Sent from my SGH-I337M using Tapatalk
---------- Post added at 12:16 AM ---------- Previous post was at 12:14 AM ----------
Once you download it and its installed make sure to turn off your phone and boot into stock recovery and do a factory reset and if you really want to be clean flash the firmware again and all your problems should be gone
Sent from my SGH-I337M using Tapatalk
Click to expand...
Click to collapse
Ok, I'll give it a go and report findings as follows (decided to try a different computer to eliminate that fact too):
1) sammobile.com --> http://www.sammobile.com/firmwares/3/?download=26590 - PDA - I337MVLUFNC1, CSC - I337MOYAFNC1, etc.
2) Downloaded and installed fresh 3.09 from sammobile per instructions.
3) Successfully flashed this firmware, phone returning back to normal as official kernel and official rom, knox warranty tripped still, but that's the way it goes.
SO: Moral of the story - ensure that not just using any kind of virtualization software to try and do flashing, use a proper PC. I hope somehow this finds its way to some other schlub that messes this up.
ROGERS is sending me a new phone anyway other problems involving sound and I was within 15 day return. Lucky me I guess...
I guess the next time around I'll need a closer look at avoiding knox tripping...

It works for me
2Tone5 said:
[/COLOR]Once you download it and its installed make sure to turn off your phone and boot into stock recovery and do a factory reset and if you really want to be clean flash the firmware again and all your problems should be gone
Sent from my SGH-I337M using Tapatalk
Click to expand...
Click to collapse
Thank you!! It works for me. It's very important to do a clean flash. :good:

I am having a crazy issue I can't seem to fix with my i337. I am trying to revert back to stock and I ran odin I get a pass notification but when I reboot my phone prompts that I have unauthorized software on my phone an to contact AT&T. I can't seem to make this work and I can't boot into recovery. Any ideas on what may help. Feeling pretty lost at this point.

I have Soft-Bricked my s5, and tried almost everything. what to do?

Hello there xdadevelopers!
Today I made the brilliant descision to root my Samsung Galaxy S5 ( SM-G900F ) with a tool called KINGO ROOT.
Aware of the fact that there is a risk while rooting your phone, I procceed forward and now im left with a useless, expensive piece of electronic..
The tool i used said root was successfully installed, but my phone got stuck on the "samsung loading screen". after 40 minutes i decided to remove the battery and try again, same thing happend. I tried to use the "remove cahce/factory" setting ( or what ever its called) and that did not help. I have also tried to install the standard firmware through ODIN, but that failed over and over again at "img.ext4"..
I've also looked through this forum to find a solution, but nothing matches my problem it seems.
I really have no idea what to do anymore. :crying: I really hope someone could help me out with this problem, im sure there is others that would benefit from the same help aswell

Really should have done some research here on XDA first, but let's try and get you back up and running
You downloaded the stock ROM from sammobile .com for the G900F ?
Download and extract this PIT file
http://forum.xda-developers.com/attachment.php?attachmentid=2721101&d=1399024091
Put the phone in Download Mode from a powered off state: (Volume Down & Home & Power) release when text appears, and hit Volume Up to enter download mode
Make sure samsung drivers are installed
Connect phone to PC > USB
Ensure ODIN 3.10.7 says connected and shows the COM port at the top
Add the PIT file to the PIT section
Add the ROM (Extracted to .MD5) to the AP or PDA section
Hit Start
--
All being well, it should begin the flashing process, and complete successfully, rebooting the phone back into Android
--
To root - extract and flash CF Auto Root for the G900F with ODIN in download mode again (Some G900Fs need a different method, but try this first)
http://download.chainfire.eu/397/CF-Root/CF-Auto-Root/CF-Auto-Root-klte-kltexx-smg900f.zip
Delete Kingo Root

*Detection* said:
Really should have done some research here on XDA first, but let's try and get you back up and running
You downloaded the stock ROM from sammobile .com for the G900F ?
Download and extract this PIT file
http://forum.xda-developers.com/attachment.php?attachmentid=2721101&d=1399024091
Put the phone in Download Mode from a powered off state: (Volume Down & Home & Power) release when text appears, and hit Volume Up to enter download mode
Make sure samsung drivers are installed
Connect phone to PC > USB
Ensure ODIN 3.10.7 says connected and shows the COM port at the top
Add the PIT file to the PIT section
Add the ROM (Extracted to .MD5) to the AP or PDA section
Hit Start
--
All being well, it should begin the flashing process, and complete successfully, rebooting the phone back into Android
--
To root - extract and flash CF Auto Root for the G900F with ODIN in download mode again (Some G900Fs need a different method, but try this first)
http://download.chainfire.eu/397/CF-Root/CF-Auto-Root/CF-Auto-Root-klte-kltexx-smg900f.zip
Delete Kingo Root
Click to expand...
Click to collapse
Hello and thanks for answering that quickly!
I have now downloaded the stock rom from sammobile, along with the PIT file and ODIN 3.10.7 which you directed me to.
However I did not manage to get the flashing completed.
I added the .md5 file to the AP section in ODIN, and the PIT file was added to the PIT section. I left the options untouched ( Auto reboot ticked, re-partition ticked and F. reset time ticked aswell. everything else was unticked )
It did start the flashing and it kept going for a couple of minutes, but at the very end it failed at 99% completion this is the log:
<ID:0/004> 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/004> Odin engine v(ID:3.1100)..
<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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> NON-HLOS.bin
<ID:0/004> rpm.mbn
<ID:0/004> sbl1.mbn
<ID:0/004> tz.mbn
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Size)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have no idea what this log means, but Im sure you do.
What did i do wrong? I tried it several times and i ended up with the same result..

I also had this problem but got out of it By downloading an earlier firmware for my phone. This is a tips guide I donei after I soft bricked due to me leaving the activation lock on! http://forum.xda-developers.com/galaxy-s5/general/read-flashing-rom-t3145703 hope this helps?

Along with the above ^^, when you put your phone in download mode, does is also say the model is the G900F ?
Some S5s have conflicting info about exactly which model they are, the section you need to trust, is download mode, double check it says G900F in download mode

*Detection* said:
Along with the above ^^, when you put your phone in download mode, does is also say the model is the G900F ?
Some S5s have conflicting info about exactly which model they are, the section you need to trust, is download mode, double check it says G900F in download mode
Click to expand...
Click to collapse
It says " Product name: SM-G900F "
deanr1977 said:
I also had this problem but got out of it By downloading an earlier firmware for my phone. This is a tips guide I donei after I soft bricked due to me leaving the activation lock on! http://forum.xda-developers.com/galaxy-s5/general/read-flashing-rom-t3145703 hope this helps?
Click to expand...
Click to collapse
Im downloading some earlier firmwares for my phone now. hope it works !

*Detection* said:
Along with the above ^^, when you put your phone in download mode, does is also say the model is the G900F ?
Some S5s have conflicting info about exactly which model they are, the section you need to trust, is download mode, double check it says G900F in download mode
Click to expand...
Click to collapse
I have now tried a 4 different firmwares, some older than the other to see if it would flash correctly.
I tried to flash only the firmware, then i tried firmware+ the PIT file you suggested in your first answer.
I also tried the PIT file all by itself, this worked , after that i tried the firmware, but that did not work..
I keep getting the same " FAIL!" over and over again when I try to flash the firmware.
At the end of the log it says " <ID:0/004> FAIL! (Size) " no matter what firmware i try to flash.
Any Ideas ?

deanr1977 said:
I also had this problem but got out of it By downloading an earlier firmware for my phone. This is a tips guide I donei after I soft bricked due to me leaving the activation lock on! http://forum.xda-developers.com/galaxy-s5/general/read-flashing-rom-t3145703 hope this helps?
Click to expand...
Click to collapse
Ive tried this several times now. but the end result is always the same : FAIL! (size)
Maybe I have done this so many times that my phone simply dont have enough space to successfully do a flash ?
Is it any way to wipe the phone clear maybe ?

babydash123 said:
I have now tried a 4 different firmwares, some older than the other to see if it would flash correctly.
I tried to flash only the firmware, then i tried firmware+ the PIT file you suggested in your first answer.
I also tried the PIT file all by itself, this worked , after that i tried the firmware, but that did not work..
I keep getting the same " FAIL!" over and over again when I try to flash the firmware.
At the end of the log it says " <ID:0/004> FAIL! (Size) " no matter what firmware i try to flash.
Any Ideas ?
Click to expand...
Click to collapse
You could try flashing a specific version of TWRP Recovery with ODIN, version TWRP 2.8.7.0
https://dl.twrp.me/klte/twrp-2.8.7.0-klte.img.tar
Flash from AP / PDA again, without extracting this time
If that flashes, try booting into recovery, Volume Up & Home & Power
If that is successful, try flashing a custom ROM from TWRP

*Detection* said:
You could try flashing a specific version of TWRP Recovery with ODIN, version TWRP 2.8.7.0
https://dl.twrp.me/klte/twrp-2.8.7.0-klte.img.tar
Flash from AP / PDA again, without extracting this time
If that flashes, try booting into recovery, Volume Up & Home & Power
If that is successful, try flashing a custom ROM from TWRP
Click to expand...
Click to collapse
TWRP 2.8.7.0 did flash without a problem. and now I did manage to boot into recovery - and now i have alot of options from Twam Win Recovery Project , and i guess im going in the right direction here hehe.
However I have no idea how to flash a custom ROM from TWRP. Do you mind walking me through the steps ?

you need to sideload a rom to your device or push it to sdcard

babydash123 said:
TWRP 2.8.7.0 did flash without a problem. and now I did manage to boot into recovery - and now i have alot of options from Twam Win Recovery Project , and i guess im going in the right direction here hehe.
However I have no idea how to flash a custom ROM from TWRP. Do you mind walking me through the steps ?
Click to expand...
Click to collapse
Great, OK well this is a popular ROM
http://forum.xda-developers.com/showthread.php?t=2732110
Instructions on how to install are on the main post
Basically copy the ROM to the MicroSD Card, and flash it using TWRP, but follow the instructions on this thread
Format / wipe everything apart from external SD from TWRP wipe menu
Go to the Install menu, and flash that ROM
Flash Gapps (Google apps) not sure if included, but not needed for flashing the ROM initially
Reboot, hopefully into the new ROM

*Detection* said:
Great, OK well this is a popular ROM
http://forum.xda-developers.com/showthread.php?t=2732110
Instructions on how to install are on the main post
Basically copy the ROM to the MicroSD Card, and flash it using TWRP, but follow the instructions on this thread
Format / wipe everything apart from external SD from TWRP wipe menu
Go to the Install menu, and flash that ROM
Flash Gapps (Google apps) not sure if included, but not needed for flashing the ROM initially
Reboot, hopefully into the new ROM
Click to expand...
Click to collapse
How am I suppose to copy the ROM to my MicroSD card ?

babydash123 said:
How am I suppose to copy the ROM to my MicroSD card ?
Click to expand...
Click to collapse
Put it in an adapter and put it in your PC, copy the ROM, put it back in your phone
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you don't have an adapter, you`ll have to buy one, they're cheap as chips - or find another device that works, you can use to copy the ROM to it with
You could try mounting the external SD (MicroSD) in TWRP, and plugging the phone into the PC and see if it is recognised, but I haven't tried that

*Detection* said:
Put it in an adapter and put it in your PC, copy the ROM, put it back in your phone
If you don't have an adapter, you`ll have to buy one, they're cheap as chips - or find another device that works, you can use to copy the ROM to it with
You could try mounting the external SD (MicroSD) in TWRP, and plugging the phone into the PC and see if it is recognised, but I haven't tried that
Click to expand...
Click to collapse
YOU are my hero, my saviour, my new idol. it actually worked!
I really cant thank you enough!
But I have some questions aswell hehe. This ROM that i downloaded installed. its not the "original" firmware that samsung provided right? what are the benefits of this VS the normal samsung one ?

babydash123 said:
YOU are my hero, my saviour, my new idol. it actually worked!
I really cant thank you enough!
But I have some questions aswell hehe. This ROM that i downloaded installed. its not the "original" firmware that samsung provided right? what are the benefits of this VS the normal samsung one ?
Click to expand...
Click to collapse
Pleased its working
No, that is not original firmware, it comes with benefits such as customisation, overclocking if the kernel allows, better speed, debloated (No crapware), more free storage, probably can install Xposed Framework for loads of tweaks and hacks and mods
Basically just about anything you want to change about your phone, you should be able to with a custom ROM, or at least request that change to the dev in that ROMs thread
But now that you have TWRP installed, you can pick and choose any custom ROM you want to try by using the same method you used to get this one installed
World is your oyster now

*Detection* said:
Pleased its working
No, that is not original firmware, it comes with benefits such as customisation, overclocking if the kernel allows, better speed, debloated (No crapware), more free storage, probably can install Xposed Framework for loads of tweaks and hacks and mods
Basically just about anything you want to change about your phone, you should be able to with a custom ROM, or at least request that change to the dev in that ROMs thread
But now that you have TWRP installed, you can pick and choose any custom ROM you want to try by using the same method you used to get this one installed
World is your oyster now
Click to expand...
Click to collapse
Ive now used it for a couple of days. and its just amazing! However I have encountered some problems with apps not working correctly. Snapchat wont load stories, and I cant watch any snapchat movies - but normal images works great when sending to my friends, which is weird. I get this errer " could not connect to server, please try again later". have tried to reinstall, clear cache etc but it seems it wont work. Ill read through the Xtrestolite thread and see if i find a solution now as Im a little more familiar with the forum
If I decide to install another ROM, is it any way that i can backup my whole phone ? so if i mess up again I can just reflash the one thats backed up, and all my apps and stuff will be just like it was ?

Yea sure, just boot back into TWRP, goto the 'Backup' section, and create a full Nandroid backup, tick all the boxes other than the caches
Make sure you have enough room on your external MicroSD (Select that as the backup location)
Once that is done, you can wipe, flash etc etc, play about with any ROM you like, and if and when you want to go back to your backup, just wipe the old one, and restore the backup from TWRP again, and your phone should be exactly the way it was when you backed it up once it finishes first boot
Very powerful recovery is TWRP

*Detection* said:
Yea sure, just boot back into TWRP, goto the 'Backup' section, and create a full Nandroid backup, tick all the boxes other than the caches
Make sure you have enough room on your external MicroSD (Select that as the backup location)
Once that is done, you can wipe, flash etc etc, play about with any ROM you like, and if and when you want to go back to your backup, just wipe the old one, and restore the backup from TWRP again, and your phone should be exactly the way it was when you backed it up once it finishes first boot
Very powerful recovery is TWRP
Click to expand...
Click to collapse
Thanks alot again!
Im experiencing some problems with some apps while using the Xtrestolite.
- Snapchat, wont load Stories at all, and wont open private video snaps, but normal pictures sent to my friends works. ( states that there was a problem connecting to the server, but when i use my Samsung S3 it works just fine )
- Dropbox - unable to preview any pictures and videoes
- larger apps/games that requires extra download ( like 3-500 MB ) wont open/load/download at all.
To me it seems that there is a problem with the phone writing temp files, such as snapschats, dropbox preview pictures.
Do you see any pattern here, maybe even some suggestions?

babydash123 said:
Thanks alot again!
Im experiencing some problems with some apps while using the Xtrestolite.
- Snapchat, wont load Stories at all, and wont open private video snaps, but normal pictures sent to my friends works. ( states that there was a problem connecting to the server, but when i use my Samsung S3 it works just fine )
- Dropbox - unable to preview any pictures and videoes
- larger apps/games that requires extra download ( like 3-500 MB ) wont open/load/download at all.
To me it seems that there is a problem with the phone writing temp files, such as snapschats, dropbox preview pictures.
Do you see any pattern here, maybe even some suggestions?
Click to expand...
Click to collapse
Did you do a FULL WIPE? Sounds like something went wrong, try SuperWipe, but make sure you have the Rom.zip on your external SD Card & not on you phone memory or you will not have nothing to flash & you will have to start mucking about. Hope this helps
Sent from my SM-G900F using Tapatalk

S7 Edge Boot Loop and Unable to Boot in Recovery (Stock ROM Unrooted)

Guys please help me out. I had a S7 edge which was just lying around for couple of months. I had taken out it's memory card and used in another phone (after format). Now I started S7 and it was very slow. I figured it was due to missing memory card as most apps were on card. I went into settings and set RESET in order to factory reset the device. It restarted slowly and since then it stuck in booth loop and does not turn off. I tried few things like booting into recovery by pressing Vol + Power and Home but nothing works. It shows error while going in recovery. Please see screens below. What do I need to do to restore it to original factory condition. It was totally stock and no modifications were made, I just wanted to factory reset it and ended up in this, don't want to to root it.
Also, is this condition called soft bricked ? Screenshot 4 tells me that recovery is also corrupted ?

Reflash with correct binary version firmware (the firmware which your phone was previously running) for your model in odin, if its not a hardware fault, it will get fixed.
Sent from my hero2lte using XDA Labs

shah22 said:
Reflash with correct binary version firmware (the firmware which your phone was previously running) for your model in odin, if its not a hardware fault, it will get fixed.
Sent from my hero2lte using XDA Labs
Click to expand...
Click to collapse
I think I missed 4th image of recovery black screen, uploaded it now. However, as I said, it was stock, I was also not trying to root or reflash anything. Still I need to flash firmware ? How will I find the version which I need to flash and what about OS, I will have to find and flash ROM too ?

lazers378 said:
I think I missed 4th image of recovery black screen, uploaded it now. However, as I said, it was stock, I was also not trying to root or reflash anything. Still I need to flash firmware ? How will I find the version which I need to flash and what about OS, I will have to find and flash ROM too ?
Click to expand...
Click to collapse
Yes, to get phone out of this condition, reflashing is an easy way, since I don't have phone in hand I can't guess the exact cause but reflashing mostly solves such issues (if its not a hardware fault)
Just to tell- you can only flash binaries with the same version number as the one which was running prior on your phone or higher. So if you don't know your current binary code, you would need to go in about section of your phone to see that info.
But since your phone won't boot anymore, just send a pic of your download mode (it has that info too) and tell me your csc/region and I will link you the correct binary firmware.
Sent from my Legendary Hero2LTE using Tapatalk

shah22 said:
Yes, to get phone out of this condition, reflashing is an easy way, since I don't have phone in hand I can't guess the exact cause but reflashing mostly solves such issues (if its not a hardware fault)
Just to tell- you can only flash binaries with the same version number as the one which was running prior on your phone or higher. So if you don't know your current binary code, you would need to go in about section of your phone to see that info.
But since your phone won't boot anymore, just send a pic of your download mode (it has that info too) and tell me your csc/region and I will link you the correct binary firmware.
Sent from my Legendary Hero2LTE using Tapatalk
Click to expand...
Click to collapse
I will find the box (i have it somewhere) but mean while i have following information which was shown on download screen,
ODIN Mode
Product Name: SM-G935F
Current Binary: Samsung Official
System Status: Official
FRP Lock: Off
Warrant Void : 0 *(0x0000)
RP SWREV: B: 7 K: 5 S: 6
I dont remember if if had snapdragon or exynos. It is dual SIM.
Question: What about the softwares like samsung knows, health apps, will they be removed once if flash it with odin and then install a new OS. How to take back to just like stock

lazers378 said:
I will find the box (i have it somewhere) but mean while i have following information which was shown on download screen,
ODIN Mode
Product Name: SM-G935F
Current Binary: Samsung Official
System Status: Official
FRP Lock: Off
Warrant Void : 0 *(0x0000)
RP SWREV: B: 7 K: 5 S: 6
I dont remember if if had snapdragon or exynos. It is dual SIM.
Question: What about the softwares like samsung knows, health apps, will they be removed once if flash it with odin and then install a new OS. How to take back to just like stock
Click to expand...
Click to collapse
Yours is an exyos variant, not snapdragon.
No, flashing with odin doesn't effect anything if you just reflash a stock rom, only rooting/installing custom recovery will trigger knox and cause problems in samsung apps. Please read forums thorough because this is basic knowledge about flashing.
You don't install new os, you just reflash your stock rom. Your phone will be as it was previously. And please I say again, read forums for some general knowledge.
You can just tell me which country you're from or where you bought your phone from and I can link you to correct firmware.
And read flashing guides on odin before proceeding. And remember, we're just helping you get your phone fixed, no one is responsible if it gets in worse condition.
Sent from my hero2lte using XDA Labs

lazers378 said:
I will find the box (i have it somewhere) but mean while i have following information which was shown on download screen,
ODIN Mode
Product Name: SM-G935F
Current Binary: Samsung Official
System Status: Official
FRP Lock: Off
Warrant Void : 0 *(0x0000)
RP SWREV: B: 7 K: 5 S: 6
I dont remember if if had snapdragon or exynos. It is dual SIM.
Question: What about the softwares like samsung knows, health apps, will they be removed once if flash it with odin and then install a new OS. How to take back to just like stock
Click to expand...
Click to collapse
Ok the download mode says SM-G935F but the box says SM-G935FD. F is for global and FD is Southeast Asia and India
Phone is made in Vietnam but I am using it in Pakistan.
I tried using an older version of samsung smart switch -> Device emergency software recovery and initialization and it gives error that device does not support initializing. That was one way to go.

lazers378 said:
Ok the download mode says SM-G935F but the box says SM-G935FD. F is for global and FD is Southeast Asia and India
Phone is made in Vietnam but I am using it in Pakistan.
I tried using an older version of samsung smart switch -> Device emergency software recovery and initialization and it gives error that device does not support initializing. That was one way to go.
Click to expand...
Click to collapse
Well I asked where you 'bought' it, but assuming you bought it from pakistan, here's the link for your firmware :
https://samfw.com/firmware/SM-G935FD/PAK/G935FXXS7ESL6
Just to tell, smart switch doesn't work anymore for flashing, you'ill need to use odin. And F and FD both use same firmwares. Good luck
Sent from my Legendary Hero2LTE using Tapatalk

Thanks. Yes bought in Pakistan.

Ok, so it failed with message <ID:0/003> Complete(Write) operation failed.
I have the correct samsung drivers installed cause smart switch is also installed on that system. tried with odin version 3.13.1 as well as Odin3 v3.13.1_3B_Patched. Selected only AP file. It performs MD5 check and then tells the size and keeps on "SetupConnection..." and then fails with the message.
I remember USB debugging was already enabled on this phone.
What if my internal storage does not have enough storage to this 2+ GB file ? There is nothing i can do to make storage available since it wont boot.

lazers378 said:
Ok, so it failed with message <ID:0/003> Complete(Write) operation failed.
I have the correct samsung drivers installed cause smart switch is also installed on that system. tried with odin version 3.13.1 as well as Odin3 v3.13.1_3B_Patched. Selected only AP file. It performs MD5 check and then tells the size and keeps on "SetupConnection..." and then fails with the message.
I remember USB debugging was already enabled on this phone.
What if my internal storage does not have enough storage to this 2+ GB file ? There is nothing i can do to make storage available since it wont boot.
Click to expand...
Click to collapse
Make sure smart switch isn't running in background while flashing with odin.. also try the latest odin version. Links for it are posted in my essential guide below my signature.
Sent from my hero2lte using XDA Labs

Update: I downloaded files for Vietnam instead of Pakistan and maybe that made a difference. Now it starts initialization, goes till boot.img and then keeps on stuck on boot.img and ultimately fails with same write error. I tried odin 3.13, 3.13.1 and 3.14 but still same. I saw a video where people would extract AP file and then maybe rename and compress img file (have to see it completely). Any ideas ?
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 3923 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

lazers378 said:
Update: I downloaded files for Vietnam instead of Pakistan and maybe that made a difference. Now it starts initialization, goes till boot.img and then keeps on stuck on boot.img and ultimately fails with same write error. I tried odin 3.13, 3.13.1 and 3.14 but still same. I saw a video where people would extract AP file and then maybe rename and compress img file (have to see it completely). Any ideas ?
Added!!
Removed!!
Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
Checking MD5 finished Sucessfully..
Leave CS..
Odin engine v(ID:3.1301)..
File analysis..
Total Binary size: 3923 M
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
NAND Write Start!!
SingleDownload.
boot.img
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Firmware region shouldn't make any difference as long as binary is correct (also you shouldn't flash different region firmware then your original purchase), also no need to compress any stock ap file because its intended for the same model.
I recommend to try with another pc and/or different usb cable/ports, delete and re-install samsung usb drivers and try with a different odin version (must be 3.13.1+)
Also reverify that you're flashing the firmware I provided. And you're not making any mistake in the process and smart switch isn't running in background processes..
If trying all above still gives failure, then you would need to get it checked in a repair shop, I fear it maybe some kind of hardware failure, sadly. But before you reach this conclusion try everything I mentioned in above paragraph. Good luck
Sent from my Legendary Hero2LTE using Tapatalk

shah22 said:
Firmware region shouldn't make any difference as long as binary is correct (also you shouldn't flash different region firmware then your original purchase), also no need to compress any stock ap file because its intended for the same model.
I recommend to try with another pc and/or different usb cable/ports, delete and re-install samsung usb drivers and try with a different odin version (must be 3.13.1+)
Also reverify that you're flashing the firmware I provided. And you're not making any mistake in the process and smart switch isn't running in background processes..
If trying all above still gives failure, then you would need to get it checked in a repair shop, I fear it maybe some kind of hardware failure, sadly. But before you reach this conclusion try everything I mentioned in above paragraph. Good luck
Sent from my Legendary Hero2LTE using Tapatalk
Click to expand...
Click to collapse
One question, What if the phone does not have enough storage available ? The AP file is itself in GBs and even the recovery.image by itself is around 45 MB. What if there is not enough storage for this even, what will happen and what can be done in that scenario.
I am asking cause when all else failed, I only extracted the recovery lz4 file and then extracted to img file and only packed the recovery.img file to TAR file and tried to flash that. In this scenario it still failed with one striking difference. This time the progress bar on phone went to around 80 percent and in one case 100 percent, similarly the progress par on top on odin tool also went to 100 percent, but still the same error in the end. When i select the bigger AP file (containing sys and boot image), the progress bar on both remain at 0 percent. Could it be a space issue on phone and if yes then what ?

lazers378 said:
One question, What if the phone does not have enough storage available ? The AP file is itself in GBs and even the recovery.image by itself is around 45 MB. What if there is not enough storage for this even, what will happen and what can be done in that scenario.
I am asking cause when all else failed, I only extracted the recovery lz4 file and then extracted to img file and only packed the recovery.img file to TAR file and tried to flash that. In this scenario it still failed with one striking difference. This time the progress bar on phone went to around 80 percent and in one case 100 percent, similarly the progress par on top on odin tool also went to 100 percent, but still the same error in the end. When i select the bigger AP file (containing sys and boot image), the progress bar on both remain at 0 percent. Could it be a space issue on phone and if yes then what ?
Click to expand...
Click to collapse
No and yes,
Flashing via odin of the same model firmware, formats and wipes all storage and then rewrites the firmware.
The only case it doesn't wipes storage is when you select Home_CSC file, in that case it only flashes firmware while retaining your data.
It is recommended to always backup your data first and clean flash using normal CSC file (which wipes all storage) and NOT Home_CSC as it is known to cause issues.
But, even keeping your data and flashing via Home_CSC shouldn't prevent it from flashing even if your internal storage is not enough, because odin writes firmware to /system partition which has a fixed size according to the phone's hardware model. And it's a separate reserved partition not user manageable in unrooted phones. And free storage space shouldn't effect it in anyway.
Now, when could flash fail ?
1. You're using a wrong model firmware.
2. You're using a counterfeit/modified phone whose real hardware model is different then whats displayed.
3. Your phone's internal nand storage hardware got faulty and fails to write anything on it.
4. Odin's version is wrong.
5. Either your PC/Samsung usb drivers/Usb cables/Usb ports got some bugs/issues.
6. Smart switch is running in background and it is known to mess with odin flashing (often that's the culprit)
7. If you're rooted and have installed twrp recovery and you try to flash a custom rom which has /system partition size greater then that reserved for the phone's hardware model, it will fail at writing too (But this only applies to rooted users using twrp recovery to flash custom roms)
I hope I made it clear now.
Sent from my hero2lte using XDA Labs

shah22 said:
No and yes,
Flashing via odin of the same model firmware, formats and wipes all storage and then rewrites the firmware.
The only case it doesn't wipes storage is when you select Home_CSC file, in that case it only flashes firmware while retaining your data.
It is recommended to always backup your data first and clean flash using normal CSC file (which wipes all storage) and NOT Home_CSC as it is known to cause issues.
But, even keeping your data and flashing via Home_CSC shouldn't prevent it from flashing even if your internal storage is not enough, because odin writes firmware to /system partition which has a fixed size according to the phone's hardware model. And it's a separate reserved partition not user manageable in unrooted phones. And free storage space shouldn't effect it in anyway.
Now, when could flash fail ?
1. You're using a wrong model firmware.
2. You're using a counterfeit/modified phone whose real hardware model is different then whats displayed.
3. Your phone's internal nand storage hardware got faulty and fails to write anything on it.
4. Odin's version is wrong.
5. Either your PC/Samsung usb drivers/Usb cables/Usb ports got some bugs/issues.
6. Smart switch is running in background and it is known to mess with odin flashing (often that's the culprit)
7. If you're rooted and have installed twrp recovery and you try to flash a custom rom which has /system partition size greater then that reserved for the phone's hardware model, it will fail at writing too (But this only applies to rooted users using twrp recovery to flash custom roms)
I hope I made it clear now.
Sent from my hero2lte using XDA Labs
Click to expand...
Click to collapse
Thanks for all your help. One final thing. How can I get a PIT file specific to my phone model ? As per my understanding this PIT file also contains information about the phone internal memory.

lazers378 said:
Thanks for all your help. One final thing. How can I get a PIT file specific to my phone model ? As per my understanding this PIT file also contains information about the phone internal memory.
Click to expand...
Click to collapse
Pit file is already included in CSC file and so no need to get it separately as your phone will be already partitioned and formatted when using CSC file..
Note : Talking about CSC file NOT home_CSC... think i already explained it few posts earlier
Edit : what kind of internal memory information you're after? Pit file contains all android partitions info on your phone not just internal user-accessible storage .. some of those partitions shouldn't be messed with.
If you just want to see partitions info, you can use pit magic (search on xda) to view the information pit file contains

shah22 said:
Pit file is already included in CSC file and so no need to get it separately as your phone will be already partitioned and formatted when using CSC file..
Note : Talking about CSC file NOT home_CSC... think i already explained it few posts earlier
Click to expand...
Click to collapse
Cause I wanted to check by enabling the PIT option in Odin and see what happens. As I used Frija tool too to download firmware but it still fails. Now was thinking to use PIT to re-partition.

Database Users

welcome