Database Users

[Q] DOWNLOAD mode N9005 - 4.4.2 - UDC START?

I'm installing the new firmware but i had an issue with odin...
I flashed again 4.4.2 but in download mode, the last line you can see " UDC START" in colour red... Is this normal? I think the phone works good, but i don't know why put on this...
Anyone have this new line??

I have the same problem with a N9005 I guess it was Hong Kong version for the kanjis in the back, but is stuck in odin mode with the UDC START line

UDC Start info.
Ok gent's little more knowledge about "udc start" I am guessing that the problem became clear as you installed 4.4.2 KK.
So did I and came across UDC Start the second time I booted into download mode.
As I played around i became aware that the "UDC Start" mode locks the download loader to certain criteria. This would be 4.4.2 KK,
so anything under 4.4.2 will get a MASSIVE RED FAIL. That including the CWR/TWRP recoveries and ROOT files.
So just to specify, yes phone is now locked/bricked to 4.4.2 KK software only.
Therefore I would please like some help to get the udc start away!? If anyone can help.
If I shared some light to the darkness please say thanks.:good:

Try this out:
Worked for me on a Hong Kong 16GB N9005 which was stuck on the 'Samsung Galaxy Note 3' screen after getting a 'Invalid: ext4 image' or 'Repartioning failed' errors while installing 4.4.2 OFFICIAL (Single File ROM) via Odin.
Binary: Custom
Knox: 0x1
Method:​
In Odin mode
1. Flash the latest cf-autoroot (Kitkat support) [http://download.chainfire.eu/352/CF-...x-smn9005.zip]
2. Flash the Chenglu's latest CWM - 6.0.4.6 (the one that supports KitKat) http://forum.xda-developers.com/show....php?t=2454079
Download Sweet Rom and place it in ExtSDcard (http://forum.xda-developers.com/show....php?t=2487425)
I tried external sd-card with various format and could not install the ROM. After format my SD Card to FAT32, the ROM can be installed.
On Device
1. Boot in to Recovery mode by Volume up + Home + Power
2. Wipe Factory reset / Dalvik Cache
3. Format /System (under "mount and storage" menu) [IMPORTANT STEP]
4. Install Rom from SD Card
5. Say your prayer. You'll need it. (The installation could take sometimes. If the device screen shows Samsung boot animation, you're half way there)

How is that going to take away the udc start?

I have UDC Start in Odin/Download mode... It hasn't affected my flashing of custom ROMs nor Stock, everyone on KK has it.

Ok, but why if i try to install a previous version of TW rom 4.3 i get a massive fail?
But all the rest works?
Thanx in regards.

FdeKlerk said:
Ok, but why if i try to install a previous version of TW rom 4.3 i get a massive fail?
But all the rest works?
Thanx in regards.
Click to expand...
Click to collapse
Because you are locked into the new Bootloader (NA6) and it's unable to downgrade

So I am guessing there is no way to downgrade the boot-loader without unlocking it?

FdeKlerk said:
So I am guessing there is no way to downgrade the boot-loader without unlocking it?
Click to expand...
Click to collapse
There's no way full stop. Samsung have blocked downgrades within the bootloader itself.

Wow now that's some sort of a problem.
My 4.4.2 works but i love xposed modules to make everything transparent and as of yet kitkat does not support that.
And now i a stuck on 4.4.2..
But thanx for the assist.:good:

Same Problem with E330s
ManuH8 said:
I'm installing the new firmware but i had an issue with odin...
I flashed again 4.4.2 but in download mode, the last line you can see " UDC START" in colour red... Is this normal? I think the phone works good, but i don't know why put on this...
Anyone have this new line??
Click to expand...
Click to collapse
Hi. I have a unrooted SHV-E330 (I9506 to some) I was running the unrooted firmware and updating with Kies up until yesterday when the update to came up. I ran it as with every other update however on self rebooting the phone now goes to ODIN MODE (in red) and UDC Start (in red) i'm a root virgin and was happy with the phone running as it was AnTU TU score 36118 with the Korean bloatware running in the background. From what I have picked up after 4.3 firmware update to 4.4.2 there is no going back. I tired to root with earlier versions of firmware but get fail every time. I Picked up a zip SKT-E330SKSUCNA7 wich goes as far as checking the MD5 file successfully in Odin 3 v3.09. everywhere I look on the web it states the com box should be yellow however mine is blue.
After MD5 successful I get leave CS. I click start I get 'Get PIT for mapping. There id no PIT partion followed by a red box and the'FAIL!' box with 'all threads completed Failed 1.
I have never rooted a phone and a buff mentioned that I will not regret it. I figure thart i'm doing something wrong as there was no PIT file with the firmware.
On first trying a firmware recovery in Kies because the phone is stuck In ODIN MODE it will not recognise the phone even though the USB drivers are installed.
If their is a person out there that could talk me through rooting trough the stuck ODIN MODE I would appreciate contact.
I gather that I have no choice but to try ODIN MODE on phone as that's where the phone is stuck. Removing battery etc has been tried to death.

summan971 said:
Hi. I have a unrooted SHV-E330 (I9506 to some) I was running the unrooted firmware and updating with Kies up until yesterday when the update to came up. I ran it as with every other update however on self rebooting the phone now goes to ODIN MODE (in red) and UDC Start (in red) i'm a root virgin and was happy with the phone running as it was AnTU TU score 36118 with the Korean bloatware running in the background. From what I have picked up after 4.3 firmware update to 4.4.2 there is no going back. I tired to root with earlier versions of firmware but get fail every time. I Picked up a zip SKT-E330SKSUCNA7 wich goes as far as checking the MD5 file successfully in Odin 3 v3.09. everywhere I look on the web it states the com box should be yellow however mine is blue.
After MD5 successful I get leave CS. I click start I get 'Get PIT for mapping. There id no PIT partion followed by a red box and the'FAIL!' box with 'all threads completed Failed 1.
I have never rooted a phone and a buff mentioned that I will not regret it. I figure thart i'm doing something wrong as there was no PIT file with the firmware.
On first trying a firmware recovery in Kies because the phone is stuck In ODIN MODE it will not recognise the phone even though the USB drivers are installed.
If their is a person out there that could talk me through rooting trough the stuck ODIN MODE I would appreciate contact.
I gather that I have no choice but to try ODIN MODE on phone as that's where the phone is stuck. Removing battery etc has been tried to death.
Click to expand...
Click to collapse
Your phone does not have a pit file on it. Odin downloads the pit file from the phone to make sure that all the partitions are correctly flashed.
Try ticking the 'Re-partition' box in odin while flashing. Though I don't really think it will help, because your single file ROM most probably does not contain the pit.
Your best bet is to find somebody else with the same model as you, and get a pit from them.
PS- You are in the wrong forums.

[COLOR=[/COLOR]
feralfire said:
your phone does not have a pit file on it. Odin downloads the pit file from the phone to make sure that all the partitions are correctly flashed.
Try ticking the 're-partition' box in odin while flashing. Though i don't really think it will help, because your single file rom most probably does not contain the pit.
Your best bet is to find somebody else with the same model as you, and get a pit from them.
Ps- you are in the wrong forums.
Click to expand...
Click to collapse
do not tick re-partition without having a pit file, you will get a brick.
Feralfire, you just broke the first law of flashing with ODIN... If you don't know what to do then don't say anything...

Thanks for caring XDA developers - i fixed it
FeralFire said:
Your phone does not have a pit file on it. Odin downloads the pit file from the phone to make sure that all the partitions are correctly flashed.
Try ticking the 'Re-partition' box in odin while flashing. Though I don't really think it will help, because your single file ROM most probably does not contain the pit.
Your best bet is to find somebody else with the same model as you, and get a pit from them.
PS- You are in the wrong forums.
Click to expand...
Click to collapse
Hey thanks for the response the same day I managed to fix the problem a hour ago after 24 hours of banging my head on a wall.
I uninstalled all software including Odin remembering that ODIN MODE was the only option. most of the Boot Operating system was in Korean.
I followed a you tube guide from another root and noticed that although ODIN MODE and UDC start are new (according to other forums) that the other information insinuated that the screen I was looking at was also the download mode.
I reinstalled Kies and rather than asking me for the emergency recovery code it reset and was asking for the Model and serial number. After which it stated it could not recover the device only reinstall the stock firmware. I selected OK. the phone came back to life and reinstalled all data from cloud.
now on 4.4.2 and still thinking about rooting
however I must warn anyone that comes across the unlocker website that states its mod allows for E330S root. that clockwork mod does not cater for E330S.

ultramag69 said:
[COLOR=[/COLOR]
do not tick re-partition without having a pit file, you will get a brick.
Feralfire, you just broke the first law of flashing with ODIN... If you don't know what to do then don't say anything...
Click to expand...
Click to collapse
Au contraire, I have done a lot of research on pit file and played around a lot. Check out my threads.
If you tick re-partition without having a pit, it just gives you an error. Maybe in the olden days, it might have been an issue (I haven't always been a Samsung guy), but definitely not now.

FeralFire said:
Au contraire, I have done a lot of research on pit file and played around a lot. Check out my threads.
If you tick re-partition without having a pit, it just gives you an error. Maybe in the olden days, it might have been an issue (I haven't always been a Samsung guy), but definitely not now.
Click to expand...
Click to collapse
If so, then make sure they know which version of ODIN to use as this is the fastest way to kill a phone I know...
Right from the very first this was a cardinal sin but then you didn't have a phone anymore or much sympathy either... But to tell a noob to do this was in effect saying "put your phone in front of a steamroller, it'll be ok after its gone over it a couple of times"...

ultramag69 said:
If so, then make sure they know which version of ODIN to use as this is the fastest way to kill a phone I know...
Right from the very first this was a cardinal sin but then you didn't have a phone anymore or much sympathy either... But to tell a noob to do this was in effect saying "put your phone in front of a steamroller, it'll be ok after its gone over it a couple of times"...
Click to expand...
Click to collapse
He was using 3.09. Don't overcomplicate things.
But anyway, I apologize for making people put their phones in front of 20 ton vehicles.

re Pit File
FeralFire said:
Your phone does not have a pit file on it. Odin downloads the pit file from the phone to make sure that all the partitions are correctly flashed.
Try ticking the 'Re-partition' box in odin while flashing. Though I don't really think it will help, because your single file ROM most probably does not contain the pit.
Your best bet is to find somebody else with the same model as you, and get a pit from them.
PS- You are in the wrong forums.
Click to expand...
Click to collapse
I found this KS01LTE_KOR_SKT_32G.pit and ran it in Odin running download mode and it worked. It appears there are several Korean versions of the right ROM and unless the right rom is used flash in odin does not work.
I'm starting to sound like i know what i'm talking about!

summan971 said:
I found this KS01LTE_KOR_SKT_32G.pit and ran it in Odin running download mode and it worked. It appears there are several Korean versions of the right ROM and unless the right rom is used flash in odin does not work.
I'm starting to sound like i know what i'm talking about!
Click to expand...
Click to collapse
The different ROMs must have different pits. That would explain why only some specific ones work.
Anyway, congratulations.

After flashing 4.4.2 NA6 - stuck in Download mode, help (solved)

I tried to install the N9005XXUENA6 firmware using odin and this happened:
<ID:0/005> system.img.ext4
<ID:0/005> FAIL! (Ext4)
And now it's stuck on odin mode, please help!

arboy2 said:
I tried to install the N9005XXUENA6 firmware using odin and this happened:
<ID:0/005> system.img.ext4
<ID:0/005> FAIL! (Ext4)
And now it's stuck on odin mode, please help!
Click to expand...
Click to collapse
put it back in download mode and flash again
if not download it again you might of had a bad download

For some reason on the tutorial it says to select stuff that doesn't come with the rar, care to give me a step by step instruction on the Odin 3.09?

arboy2 said:
For some reason on the tutorial it says to select stuff that doesn't come with the rar, care to give me a step by step instruction on the Odin 3.09?
Click to expand...
Click to collapse
are you just flashing stock or stock and root

jaythenut said:
are you just flashing stock or stock and root
Click to expand...
Click to collapse
Right now just stock N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_HOME.tar 4.4.2

arboy2 said:
Right now just stock N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_HOME.tar 4.4.2
Click to expand...
Click to collapse
http://www.youtube.com/watch?v=PurJfuEsA0s
heres a how to

jaythenut said:
http://www.youtube.com/watch?v=PurJfuEsA0s
heres a how to
Click to expand...
Click to collapse
Still does it for some reason :'(
I even closed kies like he said
I'll try downloading the firmware he included although it's the same one I think

arboy2 said:
Still does it for some reason :'(
I even closed kies like he said
I'll try downloading the firmware he included although it's the same one I think
Click to expand...
Click to collapse
Try this guide. Step by step! Even redownload this file! Like said above, you might got bad zip. did u check md5?
http://www.droidviews.com/android-4-4-2-kitkat-firmware-for-samsung-galaxy-note-3-sm-n9005/
Report back if it helped

I redownloaded the file and it still does it! ((

arboy2 said:
I redownloaded the file and it still does it! ((
Click to expand...
Click to collapse
Are you sure you followed this guide? http://www.droidviews.com/how-to-install-restore-stock-firmware-on-samsung-galaxy-note-3-all-models/
Because i used this one and it worked perfectly. Didn't use any magic.
What Odin version you have? Is it v3.09? Have you installed all the drivers, samsung kies...

ryanrazer said:
Are you sure you followed this guide? http://www.droidviews.com/how-to-install-restore-stock-firmware-on-samsung-galaxy-note-3-all-models/
Because i used this one and it worked perfectly. Didn't use any magic.
What Odin version you have? Is it v3.09? Have you installed all the drivers, samsung kies...
Click to expand...
Click to collapse
I tried following the guide and it still did it, using Odin v3.09, found a possible fix here http://forum.xda-developers.com/showthread.php?p=47287747 gonna download and try it

arboy2 said:
I tried following the guide and it still did it, using Odin v3.09, found a possible fix here http://forum.xda-developers.com/showthrea.php?p=47287747 gonna download and try it
Click to expand...
Click to collapse
ok, report back if helped. mean while http://forum.xda-developers.com/showthread.php?t=2619017&page=2
Try his solution. It was a simple usb trick. If u use usb 3.0 try 2.0 and if you use desktop comp try back usb not fron. Try restart the computer... I know those are all weak tips but i would try everything in your case.
Hope you fix it bro..

ryanrazer said:
ok, report back if helped. mean while http://forum.xda-developers.com/showthread.php?t=2619017&page=2
Try his solution. It was a simple usb trick. If u use usb 3.0 try 2.0 and if you use desktop comp try back usb not fron. Try restart the computer... I know those are all weak tips but i would try everything in your case.
Hope you fix it bro..
Click to expand...
Click to collapse
Already tried usb 2, didn't work and I would restart but I'm downloading that N9005XXUDMJ6_N9005OXADMJ4_BTU.zip rom

Same thing happened with me, after it froze in odin mode I took out the battery for 5 mins, then put it into download mode (bit fiddly holding in the buttons and pushing the battery in) the I flashed Cwm recovery using odin, and hey presto my phone came to life...
Sent from my SM-N9005 using xda app-developers app

Well I tried with that other firmware and :
<ID:0/005> aboot.mbn
<ID:0/005> FAIL! (Auth)
on the phone it said: SW REV CHECK FAIL : [aboot]Fused 3 > Binary 2
((((((
heeellllppp T_T

arboy2 said:
Well I tried with that other firmware and :
<ID:0/005> aboot.mbn
<ID:0/005> FAIL! (Auth)
on the phone it said: SW REV CHECK FAIL : [aboot]Fused 3 > Binary 2
((((((
heeellllppp T_T
Click to expand...
Click to collapse
Sorry to hear that.. waay beyond my knowledge. You might change the title (if possible) to smth like: "After flashing 4.2.2 NA6 - stuck in Download mode, help"
Might attract more people to help you, bro.
:/

ryanrazer said:
Sorry to hear that.. waay beyond my knowledge. You might change the title (if possible) to smth like: "After flashing 4.2.2 NA6 - stuck in Download mode, help"
Might attract more people to help you, bro.
:/
Click to expand...
Click to collapse
Might be a long shot but for some reason Odin says I9505 aka galaxy S4 instead of my note model, could it be it?
EDIT: No it's not it I saw here https://www.youtube.com/watch?v=PurJfuEsA0s it was the same, but what is it!!! ;_;

Why you don't try another PC?
Sent from my SM-N900 using Tapatalk 2

arboy2 said:
Might be a long shot but for some reason Odin says I9505 aka galaxy S4 instead of my note model, could it be it?
EDIT: No it's not it I saw here https://www.youtube.com/watch?v=PurJfuEsA0s it was the same, but what is it!!! ;_;
Click to expand...
Click to collapse
When you installed via odin, was there only 1 tar.md5 file (all in one) and you just added AP and flashed or did you have 3 files, flashing bootloader manually, rom manually and another one that i don't actually know what it is, like this guy http://www.youtube.com/watch?v=W0QcggQ5bAs
also, re-partition was ticked off?
When i was flashing i couldn't figure out why my ROM ZIP had only 1 file and the guy on youtube had 3 files, than i found tutorial that suited me (all in one installation)... i still don't know why are there 2 different procedures...

what CSC region of your phone?
-On 1st post you had ext4 error, more likely your is HK or Some Asia model with bad ext4. If in this case someone had own HK handset successful flash KK update.
PS: I think better way for more people to help. you should post your AP,CP and CSC of your phone.
Sent from my SM-N9005 using Tapatalk

[Q] Bricked - Please Help (SOLVED)

Hi all,
I am really hoping someone can help me. I have a Sprint Samsung Galaxy S4 (Non T version) that appears to be soft bricked. My phone was hanging on the yellow Sprint screen so after other procedures, I decided to try and ODIN a stock version. What I had before all this happened was MK2 (knox) stock with only CF Auto Root. I downloaded the MK2 stock ROM from XDA and tried to ODIN. It failed. It got through the majority of the process and then at the very end it said FAILED. Now if I try and boot the phone, it automatically goes into the firmware error screen. So I still have the ability to ODIN but it always fails. I have also downloaded the NAE stock ROM from XDA and tried that too. I have tried using Odin 3.07, 3.09, and even 1.85. All fail. On the screen I sometimes get these messages as the ODIN process fails. Either a start [2xx, 1440] and next line BAR [2xx, 1440], or I get a start and then a sw rev check fail fused 5 binary 4. These are all in red letters just underneath the download mode details. I really don't know what to do. Please help me recover my phone. Any help is greatly appreciated. Thanks so much!

IF your phnone was on an NAE firmware you will probably have problems going back to MK2.
Search for the NAE firmware .tar and try that.

@SuperG03
So great to see you posting back after asking for help.
So cool when people contribute to what worked and didn't so that others can be helped and help to contribute to the community at large.....
Oh, wait you didn't.
Guess all is good.
smmmeeesh.

leaderbuilder said:
IF your phnone was on an NAE firmware you will probably have problems going back to MK2.
Search for the NAE firmware .tar and try that.
Click to expand...
Click to collapse
As I mentioned in my OP, I tried the NAE firmware with multiple attempts on various editions of Odin. All without success.
leaderbuilder said:
@SuperG03
So great to see you posting back after asking for help.
So cool when people contribute to what worked and didn't so that others can be helped and help to contribute to the community at large.....
Oh, wait you didn't.
Guess all is good.
smmmeeesh.
Click to expand...
Click to collapse
I'm sorry, it's been like a day and a half and I've been trying like crazy to figure out how to fix this thing... Not sure how fast you expect me to reply, but I do appreciate any and all help.
SuperG03

Just really wondering if you attempted the suggestions. And or what you've done to get it to work.
It gets old trying to assist people, especially when they make it sound so urgent, and then never hearing back.
Hope you get it working.
Good luck!

leaderbuilder said:
Just really wondering if you attempted the suggestions. And or what you've done to get it to work.
It gets old trying to assist people, especially when they make it sound so urgent, and then never hearing back.
Hope you get it working.
Good luck!
Click to expand...
Click to collapse
I definitely understand trying to help and not ever hearing back would get annoying... However, for the first like half a day I checked back at this thread every hour or 2 and it had a lot of views but not any replies. Even as of now, there hasn't been a reply with a suggestion of what to do that I haven't already stated I did try in my OP (you suggested NAE and I had been trying that already). I do appreciate you at least trying though.
SuperG03

SuperG03 said:
Hi all,
I am really hoping someone can help me. I have a Sprint Samsung Galaxy S4 (Non T version) that appears to be soft bricked. My phone was hanging on the yellow Sprint screen so after other procedures, I decided to try and ODIN a stock version. What I had before all this happened was MK2 (knox) stock with only CF Auto Root. I downloaded the MK2 stock ROM from XDA and tried to ODIN. It failed. It got through the majority of the process and then at the very end it said FAILED. Now if I try and boot the phone, it automatically goes into the firmware error screen. So I still have the ability to ODIN but it always fails. I have also downloaded the NAE stock ROM from XDA and tried that too. I have tried using Odin 3.07, 3.09, and even 1.85. All fail. On the screen I sometimes get these messages as the ODIN process fails. Either a start [2xx, 1440] and next line BAR [2xx, 1440], or I get a start and then a sw rev check fail fused 5 binary 4. These are all in red letters just underneath the download mode details. I really don't know what to do. Please help me recover my phone. Any help is greatly appreciated. Thanks so much!
Click to expand...
Click to collapse
So now I would like to reply as to try and help anyone else that might have had something similar to this happen to their phone. I DID FIX my phone but using a CRAZY method that I have no good idea of why it worked. So here goes...
LONG VERSION (Short Version below for those that don't want to read about all my trials and efforts):
So as I mentioned I was on MK2 before the problem started. I tried to ODIN the MK2 Stock ROM I downloaded here but it failed. So then I decided ok maybe the issue was the older ROM, so I downloaded the NAE Stock ROM and tried to ODIN that. Again, failed. Now both of these 2 tries got far into the process before they failed. So again, through reading various posts here and on other forums it was suggested to try with other version of ODIN (I had been trying 3.07). I then tried the MK2 ROM again but with ODIN 3.09 but it failed almost immediately. That is when I noticed the lines "SW Rev Check Fail Fused 5 Binary X" every time it tried and failed. My guess is that this has something to do with the whole not being able to downgrade ROMs at any point and since I had almost completed the NAE stock ROM ODIN flash, it was stuck only with the option for NAE. So then onto trying NAE with ODIN 3.09. Once again, got most of the way done but failed toward the end of the system.img.ext4 part. I kept noticing that on the screen, almost as soon as I started the ODIN process it would output a line saying Start [220, 1440] and then soon after a line saying BAR [224, 1440]. Now I still have no idea what any of that means, but it was always failing, mostly toward the end of the flash. I then tried other ODIN versions including 1.85. All with the same results. I was at a loss. At that point I got desperate and decided I wasn't even going to try and save my DATA and thought maybe the partitions got corrupted so I found the NAE PIT file from these forums and attempted to ODIN both the PIT and the PDA with re-partition option. Once again, all attempts with all ODIN versions failed, with the same START and BAR messages showing up. I then broke down and decided to post here for help. I kept reading but everyone kept just saying in other threads about maybe KIES interfering if it was active in anyway, etc. so I check my processes and there were no KIES ones running. At that moment something occurred to me about another process by which to flash that I remember from my Galaxy S2 days. That was Heimdall. So, I decided to go on a mission to learn how to use Heimdall myself without a ready package. I finally learned how and decided to try it. I had to extract out all the .bin and .ext4, etc files out of the NAE tar and load them up manually. I started to flash and it looked to be working but then alas, it failed similarly to how ODIN did. I was at my wits end by this point. However, something occurred to me when I realized that the .tar had all these independent files in it that ODIN just tried to do all together. So here is what I did that finally WORKED. I used ODIN 3.09 with the NAE PIT file and the NAE ROM PDA file. I checked only Re-Partition and unchecked all others. I then watched exactly what ODINs log said was being flashed to the phone and what failed. I kept re-flashing until I got passed the system.img.ext4 file and the it failed on one of the others. I made note at which files out of the 13 that came from the .tar file were sent by ODIN successfully before it failed. I then closed ODIN and restarted phone in download mode and went to Heimdall. I used Heimdall to manually select only the remaining files left of the 13 that DID not go through successfully. I then flashed those I think 3 or 4 files and it said it was successful. I then rebooted my phone and to my SHOCK the phone booted up successfully and went into the OS as if it was factory wiped and ready for first time use. I was a bit bummed about having to redo all my settings, etc again and losing my old Text Messages, etc, but was so happy to have my phone back up and running. Thanks for reading this whole thing (I know it was quite long) and I hope it helps someone else out of a similar jam.
SHORT VERSION:
GET NAE Stock ROM
GET NAE PIT File
GET ODIN 3.09
GET Heimdall
YOU WILL LOSE YOUR DATA
Step 1) Use ODIN 3.09 (Run as Admin) and load up PIT file and PDA. Uncheck everything but RE-Partition
Step 2) (Hard Part) Keep flashing over and over again until you get at least the system.img.ext4 part to go through before ODIN says FAIL (It should fail on another file, like hidden.img.ext4 or NON-HLOS.bin
Step 3) Scroll through the ODIN log on the left and note every file that was successful. Basically any files it says was successful until the last one that it stops at and says FAIL
Step 4) You will need to extract out the contents of the NAE Stock ROM tar file to another directory
Step 5) Use Heimdall frontend (Run as Admin) and use the flash tab
Step 6) Load the PIT file into Heimdall as that is required for anything. But DO NOT use RE-Partition option
Step 7) Click Add and select each of the remaining files with their appropriate Partition Name and browse for those files from the ones you extracted from the tar. There are 13 files total from the tar file. Just load up (Add) starting with the file that failed in ODIN and then load up whichever ones that did not show up on the ODIN log at all. Click Start and cross your fingers
Step 8) If all went well, the phone should reboot and be up and running. If not you might have to start at Step 1 and try again
Step 9) Jump For Joy that your phone is Alive and working again!!!
Once again, I wanted to share my experience with everyone in hopes that it will help someone else out. I have no idea why I had to go to such great lengths of combining 2 versions of FLASHING and doing it piece by piece, but that is for greater minds then me to either know or figure out. I'm just happy my phone is working again! Good luck to anyone else having a similar issue.
SuperG03

[Q] Please help w/ getting back to stock.

I don't want this post to be too long but I need some help here, let me sum it up.
I purchased a secondhand Note3 off Ebay to replace my Note2. I got it an it appears to me that it's been "modified", I see this SafeStrap thing at startup and a SuperSU App. Once I saw this I decided to hold off on putting my sim card in and have just been using it on wifi. I used the "RootChecker" app to see if it's rooted and it tells me yes. System info tells me the phone is running 4.3. I know not much of this rooting, flashing, roms, kernel scene. So:
- My goal is to get this phone back to stock setting, no SafeStrap or root of any kind if it's there, so the phone operates and is just as it would be if purchased new from Verizon. What is the easiest way to go about doing this?
From there I might actually think of trying my hand at rooting this thing since it's a secondhand device, but I first want to eliminate any modifications made to the phone by the previous owner, and if I do root I want to start from ground zero and do it myself.
I apologize for my ignorance in this but could really use the help and hopefully learn more about this world along the way since it seems everyone who roots swears by it, I must be missing something but for now my objective is a clean slate with this device
Thanks in advance.

mgftp said:
I don't want this post to be too long but I need some help here, let me sum it up.
I purchased a secondhand Note3 off Ebay to replace my Note2. I got it an it appears to me that it's been "modified", I see this SafeStrap thing at startup and a SuperSU App. Once I saw this I decided to hold off on putting my sim card in and have just been using it on wifi. I used the "RootChecker" app to see if it's rooted and it tells me yes. System info tells me the phone is running 4.3. I know not much of this rooting, flashing, roms, kernel scene. So:
- My goal is to get this phone back to stock setting, no SafeStrap or root of any kind if it's there, so the phone operates and is just as it would be if purchased new from Verizon. What is the easiest way to go about doing this?
From there I might actually think of trying my hand at rooting this thing since it's a secondhand device, but I first want to eliminate any modifications made to the phone by the previous owner, and if I do root I want to start from ground zero and do it myself.
I apologize for my ignorance in this but could really use the help and hopefully learn more about this world along the way since it seems everyone who roots swears by it, I must be missing something but for now my objective is a clean slate with this device
Thanks in advance.
Click to expand...
Click to collapse
You're basically going to use Oding to flash the MJE software. Everything you need for instructions and files can be found HERE.

airmaxx23 said:
You're basically going to use Oding to flash the MJE software. Everything you need for instructions and files can be found HERE.
Click to expand...
Click to collapse
Thanks so much. Following this will remove safestrap, unroot, and basically undo any changes made to the phone and bring it back to 4.3 out of the box from Verizon status? If so, I'll give this a go tomorrow.

mgftp said:
Thanks so much. Following this will remove safestrap, unroot, and basically undo any changes made to the phone and bring it back to 4.3 out of the box from Verizon status? If so, I'll give this a go tomorrow.
Click to expand...
Click to collapse
Yes it will.

And since you're new to this, even tho it is a straight - forward procedure, read and make sure you understand what you are doing before proceeding. Ask additional questions if necessary. And let us know how it goes!
《 #VerizonLovesYou 》

airmaxx23 said:
Yes it will.
Click to expand...
Click to collapse
LeftyGR said:
And since you're new to this, even tho it is a straight - forward procedure, read and make sure you understand what you are doing before proceeding. Ask additional questions if necessary. And let us know how it goes!
《 #VerizonLovesYou 》
Click to expand...
Click to collapse
Thanks guys, hopefully I can find some time tomorrow to tackle this.
One question just reading through the guide quickly, for step 2, downloading the stock image, I assume I want 4.3 for retail? IF so, I see 3 options: Official VRUBMJE 4.3, Official VRUBMJ7 4.3, and Official VRUBMI9 4.3. Does it matter which one? I am assuming they are just different releases of 4.3 but not sure, or if I could pick one that would work better than another.
I'll copy and paste the info below if you don't know off-hand what I am referring to.
Thanks again! :good:
Section 1: How to return to Stock Android 4.3 and recover from a Soft Brick.
Take Note If your Retail Locked N3 took the OTA update, you can not revert back to older firmware. Verizon now has Samsung blacklist the older firmwares bootloader after each update. If you try and flash older firmware the device will softbrick.
Step 1: Download and install Odin to a Windows based PC- http://forum.xda-developers.com/show....php?t=2189539
Step 2: Download a stock Odin image and Pit file to the PC. If Odin does not recognize the file then extract it with a program such as 7zip.
RETAIL Locked N3 Restore Files
Official VRUCNC4 4.4.2- http://samsung-updates.com/details/2...0VVRUCNC4.html(Only use this if you took the OTA or do not mind being stuck on stock...there is currently no root method available yet!)
Official VRUBMJE 4.3- http://www.androidfilehost.com/?fid=23269279319196106(Retail locked N3 only)
Official VRUBMJ7 4.3- http://d-h.st/IEW(Retail Locked N3 ONLY)
Official VRUBMI9 4.3- https://docs.google.com/file/d/0B26p...LWs/edit?pli=1(Retail Locked N3 ONLY)
Developer Edition N3 Restore Files
DE_VRUBMJE 4.3-http://www.androidfilehost.com/?fid=23269279319196402
-------------
HLTE_32gb.PitFile- http://www.androidfilehost.com/?fid=23159073880936457(works for bothe DE and Retail devices)
Step 3: Power device off, hold the volume down/home/power keys until you see a yellow triangle, then press the volume up key to access "odin or download mode".
Step 4: Open Odin and connect the oem usb cable from pc to device. The driver should automatically install( it did for me on windows 7 64bit). There should also be a "comport number" in upper left hand corner of Odin indicating communication between the pc & device.
*If the drivers do not automatically install, then manually install the drivers in link and proceed to the next step. http://forum.xda-developers.com/show....php?t=2038555
Step 5: Click on the Pit function of Odin and select Pit file you downloaded in Step:2.
Step 6: Click on the AP/PDA(depends on Odin version) function of Odin. Select the stock 4.3 image you downloaded in step 2, then select start. This operation should take less than 8 minutes before Odin will say pass/reset.
Step 7: Your device should boot back up into factory stock 4.3 Android! However, these stock Odin files do not wipe data. To wipe data, power the device off, press and hold the volume up/home/power buttons until the samsung logo appears. The device will boot into recovery and from there you will need to wipe data/factory reset, then reboot.
Click to expand...
Click to collapse

The mje should do fime. It's the latest jb stock firmware. Once you boot up into that, your phone should promt you to accept the new kk update.
I know you do not want or care about root, but I'll say this anyways. Once you've accepted the new ota update, there's no way to root and there's no way to get back to jb. Like I said, probably not a concern of yours... just throwing it out there.
《 #VerizonLovesYou 》

Hey guys, in the process to this and stuck at these steps:
Step 5: Click on the Pit function of Odin and select Pit file you downloaded in Step:2.
Step 6: Click on the AP/PDA(depends on Odin version) function of Odin. Select the stock 4.3 image you downloaded in step 2, then select start. This operation should take less than 8 minutes before Odin will say pass/reset.
Click to expand...
Click to collapse
Following step 2 gave me one file, which I believe is the 4.3 image ( the file is 1.28GB). What exactly is the Pit file I am missing and how do I get it?
Thanks

u shouldnt need it. I think its a fix for a bootloop. I've returned my note 3 to stock many of times and havent had the use for a pit file
Sent from my SM-N900V using Tapatalk

mike7728 said:
u shouldnt need it. I think its a fix for a bootloop. I've returned my note 3 to stock many of times and havent had the use for a pit file
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
So essentially I just skip step 5 in that guide and proceed?
Thanks for the response.

mgftp said:
So essentially I just skip step 5 in that guide and proceed?
Thanks for the response.
Click to expand...
Click to collapse
Correct. The pit file is really only needed to fully wipe and reparation the phone.
《 #VerizonLovesYou 》

Thanks guys, giving this a go now... will report back.

Another hangup, clicking on AP in Odin it doesn't seem to recognize the image file I downloaded. It seems to be looking for .tar, .md5, .smd, .gz, and .tgz . The file I got from the guide is .7z
Am I doing something wrong?

mgftp said:
Another hangup, clicking on AP in Odin it doesn't seem to recognize the image file I downloaded. It seems to be looking for .tar, .md5, .smd, .gz, and .tgz . The file I got from the guide is .7z
Am I doing something wrong?
Click to expand...
Click to collapse
You need to download a program called 7zip and use that to extract the md5.

ouch1976 said:
You need to download a program called 7zip and use that to extract the md5.
Click to expand...
Click to collapse
Thanks!
-
Now how do I know if Odin is working? It doesn't seem to be doing anything that I can tell. Last message is "D:0/004> Odin v.3 engine (ID:4)..

mgftp said:
Thanks!
-
Now how do I know if Odin is working? It doesn't seem to be doing anything that I can tell. Last message is "D:0/004> Odin v.3 engine (ID:4)..
Click to expand...
Click to collapse
So 30min later no change, I feel as if it's frozen but scared to power down phone or try to exit application :/

mgftp said:
Thanks!
-
Now how do I know if Odin is working? It doesn't seem to be doing anything that I can tell. Last message is "D:0/004> Odin v.3 engine (ID:4)..
Click to expand...
Click to collapse
Sounds like you're all set to go. Just add the md5 to the PDA section and click start.

mgftp said:
So 30min later no change, I feel as if it's frozen but scared to power down phone or try to exit application :/
Click to expand...
Click to collapse
Across the top of odin, there's a series of boxes. Are any not blank?
《 #VerizonLovesYou 》

ouch1976 said:
Sounds like you're all set to go. Just add the md5 to the PDA section and click start.
Click to expand...
Click to collapse
I clicked start and I am 99% sure it's frozen, I don't see anything that would indicate that it's working and it's nearly 1 hour later.
Is it safe to try and power down the phone and/or exit Odin and try again or could that screw something up?

mgftp said:
I clicked start and I am 99% sure it's frozen, I don't see anything that would indicate that it's working and it's nearly 1 hour later.
Is it safe to try and power down the phone and/or exit Odin and try again or could that screw something up?
Click to expand...
Click to collapse
If you haven't run anything then you're safe to reboot it.

[Q] Galaxy S5 Bootloop

Before marking this as a duplicate, please note that I've gone through almost every thread on this and different possibilities, but nothing had worked.
This morning, I rooted my AT&T Samsung Galaxy S5 (US) using towelroot. The root was successful. Next I downloaded Superuser from the Play Store (not the Chainfire one). It said it needed to update something using recovery mode, but it failed with an error. So, I ignored it and continued using the phone. Next, I downloaded the Google Now Launcher from Android L, to get Material Design. I installed Sliding Explorer from the Play Store to access root files. I also got a simple text edit app. To get Material Design, I needed to change ro.build.version.codename=REL to =L in build.prop. When I did and tried to save, it said access denied, so I changed permissions (oops!) to allow the file to be saved. Still didn't work for some reason so I saved the file as build.prop somewhere else and cut and pasted it in. Then, I rebooted my device and it got stuck on the boot screen with the Samsung Galaxy S5 logo with powered by Android beneath it.
What I've tried:
- I have wiped data, the cached, but there is no advanced option for me to wipe dalvik in the stock recovery for the Galaxy S5.
- When I try to use ADB, my device shows up as sideload and sideloading a ROM goes to 100% but ends up in an error. I cannot run ADB Shell, which ends in error:close.
- Using Odinv3 Build 3.09, I think, gets stuck on connecting to the phone, while Odinv3 Build 1.85, I think, gets fails at Complete(Write) error after something to do with NAND write.
My device drivers are all updated, and I've tried different USB ports, even different PC's. Nothing works. How can I fix this? Thanks!

I am allergic to posts that use Urgent in the title. Obviously you'd like to regain use of your phone ASAP. But how that makes your post more important than someone else's is a mystery. Nevertheless, I'm sure that someone else will be along soon to help you.
If you don't find something more expedient, the most reliable solution for a non-bricked phone is to Odin flash a full, stock firmware image that matches your baseband version.
.

fffft said:
I am allergic to posts that use Urgent in the title. Obviously you'd like to regain use of your phone ASAP. But how that makes your post more important than someone else's is a mystery. Nevertheless, I'm sure that someone else will be along soon to help you.
If you don't find something more expedient, the most reliable solution for a non-bricked phone is to Odin flash a full, stock firmware image that matches your baseband version.
.
Click to expand...
Click to collapse
Problem is, as I said, Odin has errors every time I try to flash, different ports and even different PC's. Maybe I'm not doing it correctly? And I'm sure I get the correct version.
Sorry for the Urgent ?.

tforkan99 said:
Problem is, as I said, Odin has errors every time I try to flash, different ports and even different PC's. Maybe I'm not doing it correctly? And I'm sure I get the correct version.
Sorry for the Urgent ?.
Click to expand...
Click to collapse
You've made some ill advised mods. Now we need more information. Post as many details as you can so that we can spot were the exact problem is.
Paste the exact error from both Odin vetsions here.
Is this originally an ATT phone?
Regular model (i.e. not the special unlocked Developer version)?
Do you know if it the new re-activation lock feature is enabled?
Do you know the phone's baseband /exact firmware version?
Do you have a recent backup?
Are you still able to boot to recovery mode (vol up + home + power)?
Did you ever successfully use Odin with this phone before the bootloop happened?
Perhaps you could remove the Urgent from your title? Edit /Delete > Go Advanced
.

fffft said:
You've made some ill advised mods. Now we need more information. Post as many details as you can so that we can spot were the exact problem is.
Paste the exact error from both Odin vetsions here.
Is this originally an ATT phone?
Regular model (i.e. not the special unlocked Developer version)?
Do you know if it the new re-activation lock feature is enabled?
Do you know the phone's baseband /exact firmware version?
Do you have a recent backup?
Are you still able to boot to recovery mode (vol up + home + power)?
Did you ever successfully use Odin with this phone before the bootloop happened?
Perhaps you could remove the Urgent from your title? Edit /Delete > Go Advanced
.
Click to expand...
Click to collapse
Odin3 v3.09: Stuck on "SetupConnection"
Odin3 v1.85:
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Yes, originally ATT
Regular model
Don't know about re-activation lock
I think the firmware version is the problem. The last update was the one from ATT that added Yellowpages and Lookout in May. Don't know version. I've been download an April build so maybe that's why there is an error. My phone says "SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1" which apparently occurs when downgrading. Maybe if I can get an updated ROM, I can use Odin? And I've seen suggestions to use Odin3 v3.04, but same error with the April build. I can't find the May build anywhere.
Maybe this will work?:http://forum.xda-developers.com/showthread.php?t=2737257 But it's .zip and I can't flash it with Odin.
I have a Kies backup, that's it. This always happens to me . I'm always too lazy to back up my devices.....
Yes recovery mode works and I can get into ADB Sideload.
Nope, never used Odin before. never tried.

I may have something here!
http://forum.xda-developers.com/showthread.php?t=2785185
My firmware is G900AUCU2AND3.
I will update after following the guide.

It works! The only thread that I needed in the world and I couldn't find until after I wiped my device....
Device successfully restored to functionality.

tforkan99 said:
Device successfully restored to functionality.
Click to expand...
Click to collapse
Great to hear.
As I commented at the outset, all you needed to do was restore a full, stock firmware image to recover. Ideally one that matches your existing baseband. Which is essentially what that thread did. Collected all of the pieces to do a 100% reversion to stock.
I've written similar posts for Verizon and TMobile. Was in fact just rewriting the Verizon one for you when you updated the thread. Anyway, good work. Give yourself a pat on that back and promise to make more backups this time.
.

Ego?
fffft said:
I am allergic to posts that use Urgent in the title. Obviously you'd like to regain use of your phone ASAP. But how that makes your post more important than someone else's is a mystery. Nevertheless, I'm sure that someone else will be along soon to help you.
If you don't find something more expedient, the most reliable solution for a non-bricked phone is to Odin flash a full, stock firmware image that matches your baseband version.
.
Click to expand...
Click to collapse
I'm allergic to egocentric attitudes when it comes to answers in a Q & A thread.

tforkan99 said:
It works! The only thread that I needed in the world and I couldn't find until after I wiped my device....
Device successfully restored to functionality.
Click to expand...
Click to collapse
Happy to hear it that worked out for you!