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.

System Software not authorized?

Just rooted my Note 3 (MJE) and flashed CWM via Rom Manager and tried to boot into the recovery and get this message "System software not authorized by verizon has been found on your phone, please turn off your phone and go to the nearest store." Now the phone won't boot at all. Anyone know how to fix this without having to use Odin?

Slimfast35 said:
Just rooted my Note 3 (MJE) and flashed CWM via Rom Manager and tried to boot into the recovery and get this message "System software not authorized by verizon has been found on your phone, please turn off your phone and go to the nearest store." Now the phone won't boot at all. Anyone know how to fix this without having to use Odin?
Click to expand...
Click to collapse
The Verizon Note 3 uses secure (signed) blob verification at each step in it's boot sequence including boot images (normal OS kernel or recovery); if you attempt to flash anything which is not signed by Samsung, it results in exactly what you are experiencing. For now - no custom recoveries nor custom boot partitions.
If the phablet won't boot into *anything*, how exactly would you flash anything except by using Odin?
Disclaimer: I've never flashed used Odin. If the question you are asking is "can I put only the recovery back using Odin to avoid a full wipe?" then I suspect the answer is "possibly yes" - if you provide an Odin .tar file containing only the stuff you want to flash (e.g. the recovery image).
I note that the folks with developer versions of the VSGN3 use Odin files that do not include "aboot.mbn". That sort of suggests that Odin only wipes partitions that are slated to be flashed, not all of them. Were that not the case, you would have to always use a PIT file and always provide an image for every partition.
OTOH, Odin is a rather opaque tool, so you can't preclude it from having unexpected behaviors. Given that your device is brand-new, it would be a bummer to hard-brick it, so it might be better for you to just take your lumps and reflash the entire MJE Odin release ROM.
I *think* that folks here have said that attempting to roll back to prior full (factory) releases with Odin will result in a hard-brick. (Well, at least flashing down-rev low-level boot gearing such as aboot.mbn, sbl1.mbn, dbi, tz, etc). So if you flash anything, use MJE components (for now).
good luck. Please report your experiences, good or bad.
.

bftb0 said:
The Verizon Note 3 uses secure (signed) blob verification at each step in it's boot sequence including boot images (normal OS kernel or recovery); if you attempt to flash anything which is not signed by Samsung, it results in exactly what you are experiencing. For now - no custom recoveries nor custom boot partitions.
If the phablet won't boot into *anything*, how exactly would you flash anything except by using Odin?
Disclaimer: I've never flashed used Odin. If the question you are asking is "can I put only the recovery back using Odin to avoid a full wipe?" then I suspect the answer is "possibly yes" - if you provide an Odin .tar file containing only the stuff you want to flash (e.g. the recovery image).
I note that the folks with developer versions of the VSGN3 use Odin files that do not include "aboot.mbn". That sort of suggests that Odin only wipes partitions that are slated to be flashed, not all of them. Were that not the case, you would have to always use a PIT file and always provide an image for every partition.
OTOH, Odin is a rather opaque tool, so you can't preclude it from having unexpected behaviors. Given that your device is brand-new, it would be a bummer to hard-brick it, so it might be better for you to just take your lumps and reflash the entire MJE Odin release ROM.
I *think* that folks here have said that attempting to roll back to prior full (factory) releases with Odin will result in a hard-brick. (Well, at least flashing down-rev low-level boot gearing such as aboot.mbn, sbl1.mbn, dbi, tz, etc). So if you flash anything, use MJE components (for now).
good luck. Please report your experiences, good or bad.
.
Click to expand...
Click to collapse
I just flashed back to stock via odin. Worked fine.

Slimfast35 said:
I just flashed back to stock via odin. Worked fine.
Click to expand...
Click to collapse
Full MJE over the top of soft-bricked MJE?

bftb0 said:
Full MJE over the top of soft-bricked MJE?
Click to expand...
Click to collapse
Yeah.

[Q] $100 Reward / Bounty - Boot Loop OC4 to OE1

The title pretty much says it all.
Don't late night flash.
The Good:
Verizon S5, OC4 flashed to OE1 - Deodexed successfully using FlashFire. FlashFire backup restored successfully.
The Bad:
Tried to Flash a tethering fix using FlashFire / Flash Zip or OTA. Now stuck in boot loop.
What I've Tried:
Wipe Cache, Factory Reset, Wait it out (4 hours).
Reward:
$100USD via PayPal if you can get my s5 booting back to either OC4 or OE1 (preferred) with tethering. Contact via PM please.

If your still on OC4 firmware and kernel, your in good shape. If your on OE1, your hosed. If you know how to use Odin, you'll be fine. You can flash a stock NCG or NI2 Rom, then root it with Towel Root, then load up FlashFire and restore your backup. Hopefully you saved your backups on your external sd card, and have Odin and the proper .tar files on there to get you back up and rolling. It takes a little time, but not too bad
---------- Post added at 06:17 AM ---------- Previous post was at 06:14 AM ----------
This should help you a lot my friend. And if you do get it working. Keep your money. Most of us like helping folks out for fun
http://forum.xda-developers.com/showthread.php?t=2784880

So I am forever in your debt. I have my phone back running kit-kat. So Ive rooted, and installed FlashFire.....
If I want to get back to where I was...... (oc4) I go to restore and the defaults are listed below. Do I need to add/subtract any checked boxes?
[x] Verify MD5 hashes
[_] Verify Primary Bootloader
[_] Secondary Bootloader
[_] Secondary Bootloader AP
[x] Boot
[x] Recovery
[x] System
[x] Data
[x] Cache
[x] Param
[x] Persist
[x] Persisted Data
[_] EFS
[_] TrustZone
[_] DBI/SDI
[_] Modem Firmware
[_] Firmware
[_] Modem Firmware Data #1
[_] Modem Firmware Data #2
[_] Modem Firmware FSG
[_] Modem Firmware SSD

Glad your up and running. Depending on how you backed it up, full or partial, I would check all the boxes that you can. Won't hurt anything at all

Although, you may need to Odin the OC4 firmware again if your restore doesn't boot up correctly, or your Rom is acting wonky. I always do a full backup with FF. That way my firmware and kernel are still intact.

I did a full backup with FF and TP - Just to make sure. I was able to restore everything and am running back on OC4. I plan on keeping OC4's boot loader when I move to OE1 - In case something like this happens again. I don't see any info about a new tethering patch / app for OE1 - am I missing it?

I was about to say the same thing as Badger50. Glad to see this community is willing to help out for free even when money is offered .

Soft Brick Help? (NC2 or NC4)

Recently decided to try the Bootloader unlock.
Thought everything had gone well, it seemed OK.
Flashed TWRP, and now it won't boot.
I'm stuck at the phone telling me to take it to a Verizon store to fix it.
That being said, I can get into download mode and I get the following :
ODEN MODE
PRODUCT NAME : SM-N900V
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0X0
KNOW WARRANTY VOID: 0X1
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SMREV: S1, T1, R1, A2, P1
WRITE PROTECTION: Enable
UDC START
SYS REV CHECK FAIL : No Version
SECURE MAGICCODE CHECK FAIL : recovery
From all that, it seems that my recovery is not any good (probably from flashing twrp, duh).
I haven't been able to find a NC2 or NC4 flashable recovery anywhere.
Help?
Or am I barking up the wrong tree and do I need something else?

darkhawkff said:
Recently decided to try the Bootloader unlock.
Thought everything had gone well, it seemed OK.
Flashed TWRP, and now it won't boot.
I'm stuck at the phone telling me to take it to a Verizon store to fix it.
Click to expand...
Click to collapse
That "Verizon" message means that you did NOT unlock the bootloader succesfully.
You would normally see [size=+1]MODE: Developer[/size] in the Odin/Download mode screen if you had successfully unlocked.
As a matter of fact, that condition should always be checked for before trying to flash any recovery.
darkhawkff said:
AP SMREV: S1, T1, R1, A2, P1
Click to expand...
Click to collapse
[size=+1]Whoa! HOLD THE PHONE![/size] (Somebody with an older bootloader - MJE or NC2 at the latest)
If you reflash with Odin, USE EITHER MJE or NC4 at most - nothing later than that!
darkhawkff said:
SYS REV CHECK FAIL : No Version
SECURE MAGICCODE CHECK FAIL : recovery
Click to expand...
Click to collapse
I've never seen those messages before, but it's probably because you flashed something either into the boot partition or the recovery partition and your bootloader is not yet unlocked.
darkhawkff said:
From all that, it seems that my recovery is not any good (probably from flashing twrp, duh).
I haven't been able to find a NC2 or NC4 flashable recovery anywhere.
Help?
Click to expand...
Click to collapse
I will help you out. Please stand by. DO NOT FLASH NJ6 NK1 OB6 or OF1.
darkhawkff said:
Or am I barking up the wrong tree and do I need something else?
Click to expand...
Click to collapse
Stand by for more. posting now (quickly) so you don't do something rash.

bftb0 said:
That "Verizon" message means that you did NOT unlock the bootloader succesfully.
You would normally see [size=+1]MODE: Developer[/size] in the Odin/Download mode screen if you had successfully unlocked.
As a matter of fact, that condition should always be checked for before trying to flash any recovery.
[size=+1]Whoa! HOLD THE PHONE![/size] (Somebody with an older bootloader - MJE or NC2 at the latest)
If you reflash with Odin, USE EITHER MJE or NC4 at most - nothing later than that!
I've never seen those messages before, but it's probably because you flashed something either into the boot partition or the recovery partition and your bootloader is not yet unlocked.
I will help you out. Please stand by. DO NOT FLASH NJ6 NK1 OB6 or OF1.
Stand by for more. posting now (quickly) so you don't do something rash.
Click to expand...
Click to collapse
Thanks for the insight. No worries, I was downloading NC4 ATM, but I would prefer NC2 I think, for now. I got no problems waiting...it isn't my 'main' phone anymore. I got a note 5, but I prefer my note 3 for most usage. It's just....nicer....
I appreciate the help greatly though! Finding older files (like NC2) is damn near impossible. If I was at home, it's probably sitting on my file server somewhere, but I don't have access at the moment. Still at work.
I will also note, I did verify prior to trying to bootloader, to ensure the CID started with 0x15, and it does. Checked like 5 times, just to be sure.
And I figured it would.....since I bought this the day it was released. Anyway.....
Thanks!

OK. First things first. Let's examine the state your phone is currently in before you flash anything.
My educated guesses are that (a) your bootloader is NOT unlocked, and possibly (b) the phone is "stuck" always trying to boot into the recovery - which gives you the Verizon screen, or (c) something worse - for example if you flashed the custom recovery into the wrong partition.
The not-unlocked condition means that whatever is trying to be booted (either the recovery partition or the boot partition) has something non-Samsung in it. Either one would give you the Verizon message about unauthorized software.
When the phone boots from a cold startup, it looks at something in NVRAM called the "BCB" - the Boot Communication Block. If it is "empty" it will do the normal thing - try to boot the phone normally, starting with the "boot" partition. But, the BCB can contain other instructions, such as "boot to recovery", or "boot to Odin mode". And experience seems to indicate that the conditions under which the BCB is cleared (i.e., goes back to the default) is a little bit buggy or quirky - so that the phone can get "stuck" always trying to boot either the recovery or Odin/Download mode.
The "three-finger salute" of Vol-Down + Home + Power - which you normally use to start up Odin - seems to clear the BCB when you choose the "Cancel" option (Vol-Down) from that initial splash screen, and it usually will attempt to boot the normal ("boot") partition if you select "Cancel" ( = Vol-Down ).
So FIRST: Pull your battery. Re-insert. Vol-Down+Home+Power until you get that "do you want to install custom software?" screen. Press Vol-Down to cancel.
===> Does your ROM boot correctly?
If so, then you can attempt to unlock again without any flashing. I suppose you are still rooted if your phone still boots.
===> If your ROM still boots, please report it's exact firmware version. It makes a big difference whether it is a M-series or an N-series. (Note: I am asking about the bootloader firmware, not the ROM version).
If your ROM does not boot, then you are going to have to use Odin in one way or another.
I can help you out with that and point you at the correct custom recovery, depending on which bootloader firmware you want to end up with. (Especially if you have a copy of the NC2 firmware at home (it's the only one I don't have).) DON'T FLASH NJ6 OR ABOVE IN ODIN - yet. (Towelroot V3 is trivially easy on anything from MI9 through NC4, and rooting appears to be a pain in the rear beyond that)
let me know what you find.

darkhawkff said:
I will also note, I did verify prior to trying to bootloader, to ensure the CID started with 0x15, and it does. Checked like 5 times, just to be sure.
And I figured it would.....since I bought this the day it was released.
Click to expand...
Click to collapse
That certainly is a mandatory prerequisite to success. But it doesn't mean that something won't go wrong during the unlock process. To be sure, just boot into Odin mode after you think everything has succeeded and look for that "MODE: Developer" message on the Odin screen to verify that the unlock process succeeded.
There are a couple different versions of the unlocker binary in that Unlock thread, and most of the variations have to do with how the program went about reading the CID value out of the volatile filesystem /sys during initial sanity checks. As that location seemed to change from firmware release to release, there was some dependency between the unlock binary version and the OS release level of the rooted ROM it was used on. So a "safety check" in the code was what was making it non-portable; the actual CID change and binary patching of the "aboot" partition was the same in every version.
I might have used @donc113's original variant (post #218) when I was on MJE. If you are rooting with M* or N* ROM firmware, that version should work.
The other thing that happened was that (I think?) someone released an app that was really just a wrapper around the binary file. That had the unfortunate side effect of hiding the status and error messages the unlock binary produces if someone happened to use it on the wrong OS version. It's possible that someone that is rooted could slip a different version of the "unlock" binary underneath that app (in it's appropriate /data/data/* location), but that's asking a lot from people who gravitate towards using "one click" apps.
You didn't mention whether you were using the app or just the command line. If it was the latter I think that careful inspection of the unlock binary's output would have indicated success or failure.
Anyway, some TWRP custom recovery links:
TWRP for hltevzw
If you have a M* series bootloader use the -4.3.img recoveries, otherwise use -4.4 for N*, O*, or P* firmware
(The AryaMod ROM uses the Aroma installer, which apparently needs the twrp-2.8.7.0-hltevzw version, not the twrp-3.0.2-0-hltevzw. So... grab both of them)
PS I recently "upgraded" my bootloader from MJE to NC4. I did this because the M* series bootloader is incompatible with later kernels (due to technical issues about how the "DTB" (Device Tree Blob) attached to the kernel is parsed and initialized by the bootloader). I probably would have gone with NC2 instead of NC4, but all the links for the NC2 leak firmware were dead. At least NC4 is easy to root with Towelroot v3, and so far I've been able to boot and run not only lolipop roms (e.g. CM13) but a marshmallow rom (AryaMod) without major troubles. So I have an Odin-back-to-stock method for device recovery that is easily rootable (in contrast to NJ6, NK1, or PL1 which have no root method, or OB6/OF1 which have crufty/difficult rooting methods (& perhaps dodgy too)).
.

Any chance of just using Odin and flashing a stock recovery image? Rather than killing the entire os too?

I can't find just a recovery image though.

darkhawkff said:
Any chance of just using Odin and flashing a stock recovery image? Rather than killing the entire os too?
Click to expand...
Click to collapse
That works when the bootloader is unlocked (even with unsigned recoveries such as TWRP). Not sure about the locked case.
Code:
tar -H ustar -c -f my_recovery_only_Odin_bundle.tar recovery.img
md5sum my_recovery_only_Odin_bundle.tar >> my_recovery_only_Odin_bundle.tar
mv my_recovery_only_Odin_bundle.tar my_recovery_only_Odin_bundle.tar.md5
Note that the above technique for preparation of Odin flashables isn't restricted to adding just a single file. For instance, someone that had a bootlooping stock ROM in need of repair could probably create a tar.md5 bundle that only contained "boot.img" and "system.ext4.img"* Note that when Odin does the MD5 checking, it wants the filename to be unchanged (other than the .md5 extension). So don't change the name of the .tar.md5 file to something else or the MD5 check in Odin will fail.
darkhawkff said:
I can't find just a recovery image though.
Click to expand...
Click to collapse
It's inside the stock Odin tar.md5 bundle. Just extract it.
Is it even important at the moment? So long as your phone boots normally, what's in the recovery partition simply doesn't matter
Did you try the Vol-Down+Home+Power startup (followed by Cancel == Vol-down) that I suggested above? What happens?
.
* There is one place where partial firmware flashes would be extremely ill-advised: if you were flashing a bootloader (dear lord why?) ALL five pieces (aboot.mbn, sbl1.mbn, rpm.mbn, tz.mbn, sdi.mbn) need to be flashed as a group all in one go

Yup. Just tried that finally (was busy at work).
Fixed. I'm unlocked bootloader.
Yup, I'm still on NC2 (not that it's a surprise).
Still haven't been able to find the files at home. I thought I might have them saved somewhere, but apparently not. Still have 1 or 2 places to look, but I'm going to guess that I don't have it anywhere.

darkhawkff said:
Yup. Just tried that finally (was busy at work).
Fixed. I'm unlocked bootloader.
Yup, I'm still on NC2 (not that it's a surprise).
Still haven't been able to find the files at home. I thought I might have them saved somewhere, but apparently not. Still have 1 or 2 places to look, but I'm going to guess that I don't have it anywhere.
Click to expand...
Click to collapse
hope I helped.
Make a backup of your current ROM in TWRP and get it off the phone into a safe place. Then you will feel free to experiment with different ROMs as time allows. I would also suggest it is really a good idea to save that "debrick" image on the SD card in case a utter disaster happens (probably you will never use it though).
(before reformatting the SD card to get it back to usefulness)
Code:
dd if=/dev/block/mmcblk1 bs=4096 count=65536 of=/data/local/debrick.img
(or, too-late... get a debrick image with the modded "aboot" partition unlocked bootloader)
Code:
dd if=/dev/block/mmcblk0 bs=4096 count=65536 of=/sdcard/debrick.img
I'll archive the NC2 if you can find it (send me a PM) even though I can't use it any longer as I recently flashed NC4 bootloader. I have all the other firmware releases, just not that one.
The NC2 (leak) engineering bootloader appeared at a time when the kernel DTB blobs were changing structure; hopefully it is able to boot all later kernels. Please drop a note somewhere in these forums if you discover problems booting newer kernels - whether custom or stock. As I mentioned, if NC2 won't work, NC4 seems decent enough so far and it preserves a full-stock Odin recovery/rescue to a ROM version which is easily rooted with Towelroot v3
As to modems, I've done a few pairings of my flashable-stock ROMs with different modem releases (see the flashable stock thread for downloads) and - strangely - the NC4 modem won't work at all with NJ6 or NK1 (no service) kernels/ROMs, but it will work with later kernels/ROMs e.g. OB6-PL1. Just mentioning it because the NC2 modem might behave in a similar strange fashion since it is of the same vintage. I haven't had any troubles flashing modems up-version or down-version.
.

Well, all great!
I got Aryamod installed and going well.
NC2 bootloader yet too! TWRP obviously installed and OK, with 2.8.7 I believe. Installing apps now.
It really makes a difference with this phone too. I'm quite surprised by it to be honest.
All I know, is I might actually switch back to using my note 3 instead of my note 5 as my daily driver again.
Thank you again for the help. I really appreciate it.

darkhawkff said:
Well, all great!
I got Aryamod installed and going well.
NC2 bootloader yet too! TWRP obviously installed and OK, with 2.8.7 I believe. Installing apps now.
It really makes a difference with this phone too. I'm quite surprised by it to be honest.
All I know, is I might actually switch back to using my note 3 instead of my note 5 as my daily driver again.
Thank you again for the help. I really appreciate it.
Click to expand...
Click to collapse
Good deal.
AryaMod is a pretty nice ROM. Marshmallow FTW!
(I'm glad I bought a device with 3GB of RAM.)

Could you please message me at [email protected] I tried to root my sm-n900v note 3 on 5.0 and it's soft bricked. I can't get Odin to flash..keeps failing. I need to talk to someone just bought it week ago man.

PL1 modem/baseband?

Anybody have a tar.md5 of just the modem and baseband from PL1 update?
TIA

dragonhart6505 said:
Anybody have a tar.md5 of just the modem and baseband from PL1 update?
TIA
Click to expand...
Click to collapse
Perhaps. I followed the tutorial which works if you are already on the modem you want to backup. I will upload later but if you already are on PL1 modem then follow instructions I found (no warranties, all risks of damage etc)
Run in TWRP's terminal or ADB while in TWRP or Terminal command in Android with USB debugging on (root required and terminal app)
ls -al /dev/block/bootdevice/by-name
Look for modem or mdm. Once you find it, make note of the block.
To back them up in Terminal modem: dd if=/dev/block/mmcblk0pXX of=/sdcard/modem.bin
where XX means proper block partition.
you can also backup APN-HLOS, fsg, modemst1, and modemst2 providing other names instead of modem.bin
Got information from here: https://forum.xda-developers.com/showpost.php?p=64169401&postcount=3
For creating tar file use TAR_MD5_PACKAGER

AjvarXX said:
Perhaps. I followed the tutorial which works if you are already on the modem you want to backup. I will upload later but if you already are on PL1 modem then follow instructions I found (no warranties, all risks of damage etc)
Run in TWRP's terminal or ADB while in TWRP or Terminal command in Android with USB debugging on (root required and terminal app)
ls -al /dev/block/bootdevice/by-name
Look for modem or mdm. Once you find it, make note of the block.
To back them up in Terminal modem: dd if=/dev/block/mmcblk0pXX of=/sdcard/modem.bin
where XX means proper block partition.
you can also backup APN-HLOS, fsg, modemst1, and modemst2 providing other names instead of modem.bin
Got information from here: https://forum.xda-developers.com/showpost.php?p=64169401&postcount=3
For creating tar file use TAR_MD5_PACKAGER
Click to expand...
Click to collapse
Unfortunately Im not on PL1, I'm on OK2. I'm having Bluetooth and Wifi disconnections/failures. Sometimes after a while they will completely die out and refuse to turn back on or allow connections, requiring a reboot where they will work again for a while. I'm hoping that an update to the baseband will either subdue or fix these issues. I've tried multiple roms and tried reverting to older basebands (which killed BT/Wifi all together). Stock works ok, but since the device is no longer in service I'm unable to tether my wifi/Bluetooth without root. If I'm rooting anyway, I might as well be running a custom ROM.
It's a longshot, but if it COULD help I'd like to update anyway

dragonhart6505 said:
Unfortunately Im not on PL1, I'm on OK2. I'm having Bluetooth and Wifi disconnections/failures. Sometimes after a while they will completely die out and refuse to turn back on or allow connections, requiring a reboot where they will work again for a while. I'm hoping that an update to the baseband will either subdue or fix these issues. I've tried multiple roms and tried reverting to older basebands (which killed BT/Wifi all together). Stock works ok, but since the device is no longer in service I'm unable to tether my wifi/Bluetooth without root. If I'm rooting anyway, I might as well be running a custom ROM.
It's a longshot, but if it COULD help I'd like to update anyway
Click to expand...
Click to collapse
OK, I just downloaded full official PL1 stock, these were right in the tar file as my backups contain slightly more info. It is getting uploaded right now.
https://mega.nz/#!8chxiDJa!OS_i03da_uJ4p2BKzo7DGPEGubcEIzEOgk6zVjbCDfE
NON-HLOS should have more chances to help as modem is for GSM although it might end up with same incompatibility with ROM (turned off Wi-Fi). As for your problem, maybe another Kernel would work better.
How to install: you can try Heimdall or Odin. This topic provides enough info about how to do this: https://forum.xda-developers.com/galaxy-s4/general/ref-galaxy-s4-i9505-modems-bootloaders-t3315987

AjvarXX said:
OK, I just downloaded full official PL1 stock, these were right in the tar file as my backups contain slightly more info. It is getting uploaded right now.
https://mega.nz/#!8chxiDJa!OS_i03da_uJ4p2BKzo7DGPEGubcEIzEOgk6zVjbCDfE
NON-HLOS should have more chances to help as modem is for GSM although it might end up with same incompatibility with ROM (turned off Wi-Fi). As for your problem, maybe another Kernel would work better.
How to install: you can try Heimdall or Odin. This topic provides enough info about how to do this: https://forum.xda-developers.com/galaxy-s4/general/ref-galaxy-s4-i9505-modems-bootloaders-t3315987
Click to expand...
Click to collapse
Awesome! Thanks alot. Hopefully the wifi won't go out. That would certainly be the opposite of what I'm trying to achieve as the S4 on Wifi is primarily my tether device for my PC. If the case is that it'll kill my Wifi, I am more than familiar with using Odin to flash back to OK2 (this is not my first rodeo with Samsung devices).
Thank you very much mate

dragonhart6505 said:
Awesome! Thanks alot. Hopefully the wifi won't go out. That would certainly be the opposite of what I'm trying to achieve as the S4 on Wifi is primarily my tether device for my PC. If the case is that it'll kill my Wifi, I am more than familiar with using Odin to flash back to OK2 (this is not my first rodeo with Samsung devices).
Thank you very much mate
Click to expand...
Click to collapse
Please, tell me how it worked out.

Fail
Both Failed in Odin for me. It seems the only option is to reflash the whole stock image and reinstall the custom recovery
Now , all we need is someone to upload the whole PL1 stock rom to androidfilehost or mega so that we wouldnt have to wait 6 hours on a throttled download from these greedy Samsung Firmware losers.....
Ill post a link to the stock PL1 rom as soon as it finishes......

Reinstall of custom recovery shouldn't be of any problem as you already flash firmware in Odin so just extra reboot to DM and quick flash. Just uncheck Reboot, then when finished press power button and remove battery (for modem to get switched) and then boot in D mode.
---------- Post added at 09:19 PM ---------- Previous post was at 08:41 PM ----------
dragonhart6505 said:
Anybody have a tar.md5 of just the modem and baseband from PL1 update?
TIA
Click to expand...
Click to collapse
Also, are you on L720 or L720T? Had to ask earlier, I assumed you are on L720.

AjvarXX said:
Reinstall of custom recovery shouldn't be of any problem as you already flash firmware in Odin so just extra reboot to DM and quick flash. Just uncheck Reboot, then when finished press power button and remove battery (for modem to get switched) and then boot in D mode.
---------- Post added at 09:19 PM ---------- Previous post was at 08:41 PM ----------
Also, are you on L720 or L720T? Had to ask earlier, I assumed you are on L720.
Click to expand...
Click to collapse
L720T. I've had the phone up and running for a while now on Oreo. It's been better, but my Wifi speeds have cut down from 25Mbs to like 10 even right next to my router with every other device disconnected. BT still cuts out often. I like how much cleaner Stock runs so I've been waiting for the post above to link PL1.

Tried to install the PL1 Modem from this thread, but Odin displays 'Fail' message. Receive response from BootLoader.
My bootloader is a PL1 (5.0.1). I went from PL1 (Stock, Unrooted, SIM locked) to NG5 (Rooted, SIM Unlocked) and now on 6.0.1 JDCTeam's ROM. https://forum.xda-developers.com/ga...dcteam-android-source-project-mra58v-t3251663
As per 6.0.1 Rom's requirement, both Bootloader and Baseband have to be above 5.0. My baseband is still stuck at NG5.

I have the Sprint L720, has anyone posted the full PL1 rom? I bought it used and it was already on PL1. Tried flashing back to NG2, but kept getting the no seandroid error. Used a pit file that was listed on XDA and now it flashed, but it'll get stuck at the Sprint screen. Need some assistance on getting it to at least boot. Thanks much.