Database Users

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.

please help before I brick it

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!!

..

[Q] I9500 Soft Brick

Hello,
I bought a Galaxy S4 I9500 from China and I tried to flash an European firmware.
Yesterday:
- Using Odin 3.04 I tried to flash several official firmwares from sammobile. I couldn't get any to work so I flashed back the Chinese one (
Model: GT-I9500, Model name: GALAXY S4, Country: China, Version: Android 4.2.2, Changelist: 1176533, Build date: Mon, 16 Sep 2013 13:29:50 +0000, Product Code: CHU, PDA: I9500ZNUCMI1, CSC: I9500CHUCMI1, MODEM: I9500ZNUCMI1).
Today:
- I decided to try again, but this time I downloaded and installed the drivers first: Samsung_USB_Drivers_for_Mobile_Phones_v1.5.27.0.
- I tried the German firmware 4.4.2 and it failed, but it didn't fail like yesterday (right on the start), it failed after he went through cache, radio, when it got to the system (in Odin). I tried to add back the Chinese firmware and it isn't working anymore.
- I tried different Odin versions and different ports. I ran everything as administrator.
- I can't access recovery mode, only download mode.
- When I connect the phone to flash the firmware it says: ODIN MODE, PRODUCT NAME: GT-I9500, CURRENT BINARY: Samsung Official, SYSTEM STATUS: Custom, KNOX WARRANTY VOID: 1, RP SWREV: A3. And when I get the fail message in Odin, on the phone's screen appears Failed to load magic string (I am not sure whether it says string or not, but I am to scared to try it again).
- When I try to plug the phone to normally charge it, on my screen appears that there was a problem installing the firmware. I am afraid battery will drain out and I can't do anything...
My questions:
1. Is there any chance to get my phone working again? (I don't care about the language and whether I can use Google services anymore... I just need to get it working...)
2. What should I do to fix it?
3. Can I ruin it even more?
Thank you in advance!

More details...
I tried it again with Russian and Chinese firmware. This is what I got.
- Odin log on attempting to flash the Chinese firmware:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9500ZNUCMI1_I9500CHUCMI1_I9500ZNUCMI1_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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> modem.bin
<ID:0/003> recovery.img
<ID:0/003> sboot.bin
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Click to expand...
Click to collapse
- When I tried to flash the Russian one, the log stopped at NAND Write Start!! -> Fail.
Another thing: yesterday the download mode was in Chinese language. After I tried the German firmware it changed to English. Also where it says the product name, yesterday it was GT-I9500CN, now it's just Gt-I9500.

link to OP's boot screen: http://www.secondinsights.com/IMG_0931.JPG

C.A.Mihai said:
I tried it again with Russian and Chinese firmware. This is what I got.
- Odin log on attempting to flash the Chinese firmware:
- When I tried to flash the Russian one, the log stopped at NAND Write Start!! -> Fail.
Another thing: yesterday the download mode was in Chinese language. After I tried the German firmware it changed to English. Also where it says the product name, yesterday it was GT-I9500CN, now it's just Gt-I9500.
Click to expand...
Click to collapse
Hi mate ,
If your phone is from China and had chinese firmware on it chances are you have a chinese PIT , meaning partitions are different , try this thread , try to flash a stock rom ( any) once there , root , flash recovery and any rom you want
http://forum.xda-developers.com/showthread.php?t=2265477

Thank's for your answer. I'm his friend and I know this phone.
Unfortunately, nothing works. He can enter download mode but that's it. And he tried different i9500 firmwares (Chinese and Russian) and they don't work. He tried from 2 different computers, 2 different Odin versions, different USB ports, etc.
By the way, in the process something strange happened: Knox counter is 1 and status is now custom. From my knowledge, that shouldn't suppose to happen.
What exactly should he do, because at this moment nothing works?

raducanmihai said:
Thank's for your answer. I'm his friend and I know this phone.
Unfortunately, nothing works. He can enter download mode but that's it. And he tried different i9500 firmwares (Chinese and Russian) and they don't work. He tried from 2 different computers, 2 different Odin versions, different USB ports, etc.
By the way, in the process something strange happened: Knox counter is 1 and status is now custom. From my knowledge, that shouldn't suppose to happen.
What exactly should he do, because at this moment nothing works?
Click to expand...
Click to collapse
Hi,
If he can enter download mode that is good , try and follow the thread i gave you , Flash PIT
Odin troubleshooting: If Odin accidentally gives you "fail" try the following:
- Repeat procedure.
- Make sure that all actions of Kies are disabled from task manager.
- Change usb port.
- Try another usb cable (make sure it is the original).
- Try another Odin version.
- Uninstall and re-install driver.
- Use pit file.
- Try another computer.
And after that try to flash stock , regarding stock rom (odin) what version you had before , you said 4.2.2 and that you tried a 4.4.2 , my point is if you have a new bootloader you can not flash (odin) a older bootloader , as you already tried to flash a 4.4.2 firmware just to avoid any further confusions i will stay with the 4.4.2 firmware
regarding the status and knox is hard to tell , who knows what happens to it before you got the phone

Fixed!!!!!!!!!
First of all, I would like to thank you for your help, MAX 404! Reading your message I figured out what I was doing wrong. This part helped me:
And after that try to flash stock , regarding stock rom (odin) what version you had before , you said 4.2.2 and that you tried a 4.4.2 , my point is if you have a new bootloader you can not flash (odin) a older bootloader , as you already tried to flash a 4.4.2 firmware just to avoid any further confusions i will stay with the 4.4.2 firmware
Click to expand...
Click to collapse
.
What I think happened:
- the bootloader was in Chinese when there was the 4.2.2 firmware installed.
- after I tried to flash a German 4.4.2 it changed to English, but the flash failed (it can be related to what you said about the fact that it have a Chinese PIT).
- so, instead of flashing the 4.2.2 Chinese firmware I tried the 4.4.2.
Now I don't think it will work to flash something outside of China without changing the PIT partitioning. What do you think, should I try it?
P.S. I tried to go to a service and they told me there is nothing to be done, but you knew better. Thanks a lot! Also thanks to raducanumihai!

C.A.Mihai said:
First of all, I would like to thank you for your help, MAX 404! Reading your message I figured out what I was doing wrong. This part helped me: .
What I think happened:
- the bootloader was in Chinese when there was the 4.2.2 firmware installed.
- after I tried to flash a German 4.4.2 it changed to English, but the flash failed (it can be related to what you said about the fact that it have a Chinese PIT).
- so, instead of flashing the 4.2.2 Chinese firmware I tried the 4.4.2.
Now I don't think it will work to flash something outside of China without changing the PIT partitioning. What do you think, should I try it?
P.S. I tried to go to a service and they told me there is nothing to be done, but you knew better. Thanks a lot!
Click to expand...
Click to collapse
Hi mate ,
Glad things are finally working out !!
If you want to flash a NON CHINESE firmware you first have to flash a NON CHINESE PIT , you can try it should work just fine, in the thread i posted you can find the PIT you need...

Going further
I tried to get Google services with a Google installer apk and it didn't work, so I decided to go for the solution you provided. I still have few more questions, because I am not entirely sure about the procedure:
First of all, I will use:
- Odin v_3.09
- The 2nd PIT attached to this post http://forum.xda-developers.com/showthread.php?t=2265477 -- this one: I9500_pit file.zip - [Click for QR Code] (1.0 KB, 16010 views)
- Russian firmware from sammobile [I9500XXUGNG3_I9500SERGNG3_I9500XXUGNF6_HOME.tar.md5] -- PDA: I9500XXUGNG3, CSC: I9500SERGNG3, MODEM: I9500XXUGNF6
I have all drivers properly installed and tested.
Second of all, this is what I figured out from reading on how to do it:
1. I add the PIT file
2. I check the Re-partition box
3. I add the firmware to AP
4. I look for Auto Reboot and F. Reset Time to be checked
5. I get my phone in download mode and after Odin recognizes it, I click start and say a prayer.
My questions for you, MAX 404:
1. Are the chosen files the right ones for my GT-I9500CN (PIT and Firmware), in order to be able to use the Google services?
2. Are these steps all I need to do, or am I missing something?
3. What's the worst can happen? (because it's my first time doing this I'm kinda scared, but I'm trying to gain confidence)
Thank you a lot!

C.A.Mihai said:
I tried to get Google services with a Google installer apk and it didn't work, so I decided to go for the solution you provided. I still have few more questions, because I am not entirely sure about the procedure:
First of all, I will use:
Odin v_3.09
The 2nd PIT attached to this post http://forum.xda-developers.com/showthread.php?t=2265477 -- this one: I9500_pit file.zip - [Click for QR Code] (1.0 KB, 16010 views)
Russian firmware from sammobile [I9500XXUGNG3_I9500SERGNG3_I9500XXUGNF6_HOME.tar.md5] -- PDA: I9500XXUGNG3, CSC: I9500SERGNG3, MODEM: I9500XXUGNF6
I have all drivers properly installed and tested.
Second of all, this is what I figured out from reading on how to do it:
1. I add the PIT file
2. I check the Re-partition box
3. I add the firmware to AP
4. I look for Auto Reboot and F. Reset Time to be checked
5. I get my phone in download mode and after Odin recognizes it, I click start and say a prayer.
My questions for you, MAX 404:
1. Are the chosen files the right ones for my GT-I9500CN (PIT and Firmware), in order to be able to use the Google services?
2. Are these steps all I need to do, or am I missing something?
3. What's the worst can happen? (because it's my first time doing this I'm kinda scared, but I'm trying to gain confidence)
Thank you a lot!
Click to expand...
Click to collapse
Hi ,
Odin v_3.09 OK
[
The 2nd PIT attached to this post http://forum.xda-developers.com/showthread.php?t=2265477 -- this one: I9500_pit file.zip OK
Russian firmware from sammobile [I9500XXUGNG3_I9500SERGNG3_I9500XXUGNF6_HOME.tar.md5] -- PDA: I9500XXUGNG3, CSC: I9500SERGNG3, MODEM: I9500XXUGNF6 OK
I have all drivers properly installed and tested.
Regarding this:
Second of all, this is what I figured out from reading on how to do it:
1. I add the PIT file
2. I check the Re-partition box
3. I add the firmware to AP
4. I look for Auto Reboot and F. Reset Time to be checked
5. I get my phone in download mode and after Odin recognizes it, I click start and say a prayer.
Looks good , see this thread also for reference is for the S2 but still valid
http://forum.xda-developers.com/gal...es/mod-partition-internal-memory-app-t2538947
Also note point 6
Note 6: If you flash I9500 stock firmware for China region, it will flash sboot.bin with it, that leads to have a Chinese bootloader (download mode will be in Chinese language and boot splash name will change). Even if you flash other stock firmware, it will not change the bootloader. So flash "GT-I9500_sboot.tar" (attached) as pda in Odin and it will fix the issue.
You did flash a Chinese firmware? Is your download mode in Chinese? , one last question what is the size of your internal SD?
Regarding your questions
1 Yes
2 seem to be all there, always double check
3 Even if you have done it 1000 times is still scary….is normal , just read make sure everything is set and go , Should be fine but there is never 100% guarantee that nothing will happen , as long as you can get into download made there should be no problem.
Good luck.

Okay, I got everything ready and I am going for it.
About what you asked me:
1. You did flash a Chinese firmware? -> Yes I flashed a 4.4.2 Chinese stock firmware (I9500ZNUHNF1_I9500CHUHNF1_I9500ZNUHNF1_HOME.tar)
2. Is your download mode in Chinese? -> Yes, the download mode is in Chinese.
3. what is the size of your internal SD? -> I am not sure what do you mean by internal SD, but it is the 16GB version and the SD card is just 2GB.
I will get back here with the results to let you know how it went.
Thank you!

C.A.Mihai said:
Okay, I got everything ready and I am going for it.
About what you asked me:
1. You did flash a Chinese firmware? -> Yes I flashed a 4.4.2 Chinese stock firmware (I9500ZNUHNF1_I9500CHUHNF1_I9500ZNUHNF1_HOME.tar)
2. Is your download mode in Chinese? -> Yes, the download mode is in Chinese.
3. what is the size of your internal SD? -> I am not sure what do you mean by internal SD, but it is the 16GB version and the SD card is just 2GB.
I will get back here with the results to let you know how it went.
Thank you!
Click to expand...
Click to collapse
Hi
1 Ok
2 See note 6 on my last post
3 Go to Settings / More / storage / and tell me your available space and usded space.
Good luck

MAX 404 said:
Hi
1 Ok
2 See note 6 on my last post
3 Go to Settings / More / storage / and tell me your available space and usded space.
Good luck
Click to expand...
Click to collapse
Good morning,
Here is the the info about the space:
{
"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"
}
From what I could understand, I can flash the "GT-I9500_sboot.tar" after I flash the PIT and Russian firmware, or it has to be done before that?
Right after I get an answer from you about the bootloader I'll start, because I can't figure out what else could go wrong.
Thanks a lot for your help and patience!

C.A.Mihai said:
Good morning,
Here is the the info about the space:
From what I could understand, I can flash the "GT-I9500_sboot.tar" after I flash the PIT and Russian firmware, or it has to be done before that?
Right after I get an answer from you about the bootloader I'll start, because I can't figure out what else could go wrong.
Thanks a lot for your help and patience!
Click to expand...
Click to collapse
Hi mate,
The NON CHINESE PIT gives you a Internal SD size of about 8.2 to 8.5 GB of memory , the CHINISE PIT give you about 11 GB ( used space + available space) , advantage more memory, disadvantage make it only compatible with chinese roms.....or r customs roms with that PIT
regarding this GT-I9500_sboot.tar for what i understand you are right.

It worked
Hello,
Again thanks for all the help. I eventually did it after the root method failed and it is working. My S4 bought from China runs now an Russian stock firmware.

Help with Rooting Galaxy S4

Hello, everyone. I'm new to this site, and have come here because I've gotten a bit desperate. I have been trying to root my AT&T Galaxy S4 (Model number: Samsung-SGH-I337, Android version 4.4.4) for a long time and have been unable to. I have tried multiple programs, such as Kingo Root, Root Genius, and towelroot. Nothing worked until someone I know told me to go to TomsGuide (a website; I tried to post the link, but was unable to) and follow the steps. It seemed to work at first, because I now have SuperSu and Superuser in my apps.
However, when I open the Superuser app, a message pops up: "The Superuser binary (su) must be updated. Please choose an installation method. Recovery mode installation is recommended for HTC devices." There are two options: Cancel and Recovery Install. Nothing happens when I click Cancel; when I click Recovery Install, I receive this message: "There was an error installing Superuser. Please send a log of the error to the developer."
I have also gone into My Files on my phone and found the apk files (there was one on my SD card and one in the phone's memory). I installed both, but when I opened it, I either received the same message as above or this one "There is no SU binary installed and SuperSU cannot install it. This is a problem! If you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device."
I am not sure what to do now and have been unable to find the answer to this problem yet. Any help would be appreciated. I am also new to this kind of stuff, so detailed explanations would be nice. Thank you in advance.

Kingroot DESKTOP will root a S4. Look for my post on the subject.
Unfortunately I haven't figured out how to include links in my posts from Tapatalk. Maybe someday.
Sent from my SAMSUNG-SGH-I337 using Tapatalk

This thread should help you out: http://forum.xda-developers.com/gal...to-root-i337ucufnj4-4-4-4-11-13-2014-t2939553

Kingroot seems kind of shady; I don't want to use it. I'd prefer to fix the problem I'm having, not try another one-click solution that won't work.
I've also already tried towelroot. It didn't work. Thanks for trying to help, though.

phoenix_fire said:
Kingroot seems kind of shady; I don't want to use it. I'd prefer to fix the problem I'm having, not try another one-click solution that won't work.
Click to expand...
Click to collapse
Agreed.
I've also already tried towelroot. It didn't work. Thanks for trying to help, though.
Click to expand...
Click to collapse
Towelroot works only with the NC1 kernel. You must flash the nc1 kernel, root with towelroot, and flash back the kernel for your system, presumably NJ4 or NJ5. If you didn't do this, then of course towelroot will not work. And it probably depends on which version of towelroot you use as well. The link above provided by @merlise will give you the download link for the correct version of towelroot, and will work if you follow it.

creepyncrawly said:
Towelroot works only with the NC1 kernel. You must flash the nc1 kernel, root with towelroot, and flash back the kernel for your system, presumably NJ4 or NJ5. If you didn't do this, then of course towelroot will not work. And it probably depends on which version of towelroot you use as well. The link above provided by @merlise will give you the download link for the correct version of towelroot, and will work if you follow it.
Click to expand...
Click to collapse
You are correct; I believe I have the NJ5 kernel (found it under Baseband Version; is that right?). Can you walk me through how to flash the nc1 kernel? And then how to flash back the kernel for my system? I have no idea how to do that.

phoenix_fire said:
You are correct; I believe I have the NJ5 kernel (found it under Baseband Version; is that right?). Can you walk me through how to flash the nc1 kernel? And then how to flash back the kernel for my system? I have no idea how to do that.
Click to expand...
Click to collapse
Baseband is the modem. Usually when stock firmware is installed, kernel, system and baseband will all be the same, although the modem can be installed individually, but you would probably know about it since you would have had to do it yourself. So let's assume that you are on NJ5 system. When you look in about device, "Build Number" should tell you which system and kernel is installed.
Here is the link for the walk-through you need. (It's the same thread that was linked above by @merlise.
Skip step 1, of course since you are already on NJ5. After that, follow the steps in order, 2 through 6. The download links for everything you need are in-line with the relevant steps.
If you've never flashed firmware using Odin, it's not difficult. I can post a tutorial for using Odin if you need it, or you can find similar on the forum.
Edit: Since you are on NJ5 and not NJ4, go here to download the NJ5 stock kernel.

creepyncrawly said:
If you've never flashed firmware using Odin, it's not difficult. I can post a tutorial for using Odin if you need it, or you can find similar on the forum.
Click to expand...
Click to collapse
Wow! Thanks; I'll give this a shot. I'll look for a tutorial for using Odin, but I'd appreciate if you could post one for me as well.

creepyncrawly said:
Here is the link for the walk-through you need. (It's the same thread that was linked above by @merlise.
Skip step 1, of course since you are already on NJ5. After that, follow the steps in order, 2 through 6. The download links for everything you need are in-line with the relevant steps.
If you've never flashed firmware using Odin, it's not difficult. I can post a tutorial for using Odin if you need it, or you can find similar on the forum.
Edit: Since you are on NJ5 and not NJ4, go here to download the NJ5 stock kernel.
Click to expand...
Click to collapse
Okay, so I just tried to follow the instructions from the link that merlise had posted. I skipped step 1, did step 2, and ran into trouble on step 3. Both the nc1 Kernel and Odin downloaded to my computer just fine, but flashing it to my phone failed. It said there was no pit partrition. So I Googled that, found the pit partition for my phone, and tried to flash that. This is what Odin said:
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
So I am completely clueless what to do next. Can you help?

phoenix_fire said:
Okay, so I just tried to follow the instructions from the link that merlise had posted. I skipped step 1, did step 2, and ran into trouble on step 3. Both the nc1 Kernel and Odin downloaded to my computer just fine, but flashing it to my phone failed. It said there was no pit partrition. So I Googled that, found the pit partition for my phone, and tried to flash that. This is what Odin said:
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
So I am completely clueless what to do next. Can you help?
Click to expand...
Click to collapse
From what you say above, you tried to flash the pit file alone, without a firmware. From what I understand, it is usually flashed in conjunction with a full firmware. It may not work when flashed by itself.
I wish you had posted the results of your first attempt to flash the NC1 kernel. I would be very surprised if you actually have a problem with the partitioning of your memory. It is almost never required to flash a pit file. There is usually some other cause for issues.
When Odin flash fails, it is very often a problem with the connection between the computer and the phone, so it is always a good idea to make some changes and try flashing again. Use another cable, use another port on the computer, especially one that is connected directly to the motherboard on a desktop pc, or even use another computer. Also, you might try a different version of Odin. If you are using v3.09 or similar, you might try v1.85 which you can download from my Download Repository (see link in my signature.)
Try again to flash the NC1 kernel, as in step 3 of the guide.
How to use stand-alone Odin3 to flash firmware:
Follow and recheck each of the following steps. Do them in order listed, as some steps are dependent on previous steps. Instructions are for Odin3 v1.85. It should work with any version of Odin, but some details, like color of items, may be different. In Odin 3.09, the PDA slot is named AP.
1.) Open Odin on the Windows Desktop.
2.) Have the USB cable plugged into USB port on the computer and into the phone.
3.) Shut the phone off.
4.) Put the phone into download mode.
5.) In Odin, you should get the yellow box under where it says ID:COM with the text 0:[COMx], and in the Message area, <ID:0/00x> Added!! where x is some number, usually 1-8.
6.) In Odin, make sure Auto Reboot and F. Reset Time are checked and all other items are not checked.
7.) Click on the PDA button. Browse to the tar file you want to install and select it so its path appears in the text edit box next to the button.
8.) Make sure the check box next to the PDA button is checked.
9.) Click the Start button.
10.) You should see the green progress bar advancing.
11.) When complete, you will get a PASS (or FAIL if unsuccessful).
Let me know if it flashes successfully. Regardless if it works or not, before you close Odin, copy out the information in the Messages section and post it back here.

creepyncrawly said:
I wish you had posted the results of your first attempt to flash the NC1 kernel. I would be very surprised if you actually have a problem with the partitioning of your memory. It is almost never required to flash a pit file. There is usually some other cause for issues.
Click to expand...
Click to collapse
I wish I had thought of that, too.
creepyncrawly said:
Let me know if it flashes successfully. Regardless if it works or not, before you close Odin, copy out the information in the Messages section and post it back here.
Click to expand...
Click to collapse
I was just about to attempt flashing again, but now my computer is not recognizing my phone at all: "The last USB device you connected malfunctioned and Windows does not recognize it." I tried a few different cables and two different ports. I believe it's a driver error. Also, I noticed that I've lost the ability to connect to wifi.

phoenix_fire said:
I wish I had thought of that, too.
I was just about to attempt flashing again, but now my computer is not recognizing my phone at all: "The last USB device you connected malfunctioned and Windows does not recognize it." I tried a few different cables and two different ports. I believe it's a driver error. Also, I noticed that I've lost the ability to connect to wifi.
Click to expand...
Click to collapse
If the problem is in the phone, then I don't know the remedy. If you can boot into recovery, you might try performing a wipe data/factory reset.
You might try uninstalling and reinstalling the USB driver. See this thread for download. Or you might try a different PC.

creepyncrawly said:
If the problem is in the phone, then I don't know the remedy. If you can boot into recovery, you might try performing a wipe data/factory reset.
You might try uninstalling and reinstalling the USB driver. See this thread for download. Or you might try a different PC.
Click to expand...
Click to collapse
Hi. Sorry about the late response; I've put trying to root my phone on the back burner for now, since I am really busy at the moment and things aren't going to slow down for a while. I'm going to attempt to figure it once more around Christmas time, so you'll hear from me again around then! Also, I just wanted to thank you for your help thus far; I appreciate it!

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.