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.

Can flash firmware but cannot access Recovery

I'm new here so please bear with me. I've been reading up on these forums and other places all over the internet. Currently, I'm not sure what the problem is with my device. I can boot into download mode but never in recovery.
First off, I got this phone from someone else and it was bricked when I got it. I've tried flashing and I've got the "Fused 3: Binary 2" when trying to flash different stock files. If I'm correct, this means the last person should have tried to upgrade it to the latest Kitkat firmware. I've been using Odin 3.07, 3.09, and even 1.85 to see if the flash is just bad in one version or the others. However, each version will flash the latest firmware that Sammobile give me just fine (or at least appears so).
I've even tried flashing a pit file (HLTE_USA_VZW_32G.pit) but that really does nothing. If I flash the pit file and then flash the firmware alone 2 time back to back... it will show its attempting to go into recovery ONCE but fail and go into a never ending bootloop. Sometimes after a flash it will even bootloop trying to go into recovery automatically.
I haven't read anyone who has had it happen like this and I'm not sure if I'm in a soft-brick or in a weird hard-brick. Any suggestions?

LeveeWasDry said:
I'm new here so please bear with me. I've been reading up on these forums and other places all over the internet. Currently, I'm not sure what the problem is with my device. I can boot into download mode but never in recovery.
First off, I got this phone from someone else and it was bricked when I got it. I've tried flashing and I've got the "Fused 3: Binary 2" when trying to flash different stock files. If I'm correct, this means the last person should have tried to upgrade it to the latest Kitkat firmware. I've been using Odin 3.07, 3.09, and even 1.85 to see if the flash is just bad in one version or the others. However, each version will flash the latest firmware that Sammobile give me just fine (or at least appears so).
I've even tried flashing a pit file (HLTE_USA_VZW_32G.pit) but that really does nothing. If I flash the pit file and then flash the firmware alone 2 time back to back... it will show its attempting to go into recovery ONCE but fail and go into a never ending bootloop. Sometimes after a flash it will even bootloop trying to go into recovery automatically.
I haven't read anyone who has had it happen like this and I'm not sure if I'm in a soft-brick or in a weird hard-brick. Any suggestions?
Click to expand...
Click to collapse
the fact you can get into download modes shows you're not hard brick. Make sure you are downloading the correct firmware, since I don't know what you were running the safest approach would be to download NC4 Firmware, pit file, and use odin 3.10. Now flash the pit file, then flash the firmware in the PDA/PA spot. Restart you phone, on boot up hold home and I believe the down power button to get into recovery, select factory restore, and restart.

Yeah, definitely check which firmware you have. Make sure it's for the N900V. The leaked nc2 came with either missing or broken recovery, so don't odin that. Verify the md5 code after you download both the pit and the tar.md5. I'm pretty sure odin does this, but check just in case.

LeftyGR said:
Yeah, definitely check which firmware you have. Make sure it's for the N900V. The leaked nc2 came with either missing or broken recovery, so don't odin that. Verify the md5 code after you download both the pit and the tar.md5. I'm pretty sure odin does this, but check just in case.
Click to expand...
Click to collapse
I'm pretty sure my phone needs N900VVRUCNC4_N900VVZWCNC4_N900VVRUCNC4_HOME.tar because its the only one that successfully flashed in Odin. I have a new theory that may have something to do with it. My phone battery is completely dead so maybe that is a failsafe for recovery mode? I know people say the battery needs to be a certain % charged before doing any flashing. Perhaps its due to the fact it won't boot into recovery proper until the battery is at a certain charge? I sort of think it could be the case.
Since it won't charge due to boot loop... I had to do a bad flash and reproduce the results I got a day ago. I did a bad flash that won't send the device into a bootloop and rather straight into a charge state. I'm going to get the battery to 100% and try a flash with the above firmware again. Perhaps recovery will actually work with the battery at 100%. I will keep update with the results.

Battery is at 100% now but it still will not boot into recovery. I flash the .pit file and then the firmware file stated above. I try different combinations all to no fix. I'm still stuck in a bootloop.
I don't understand really. The phone seems to be soft-bricked obviously... so there is a way to salvage... I just can't seem to get it to work. Any thoughts on what I can try from here?

LeveeWasDry said:
Battery is at 100% now but it still will not boot into recovery. I flash the .pit file and then the firmware file stated above. I try different combinations all to no fix. I'm still stuck in a bootloop.
I don't understand really. The phone seems to be soft-bricked obviously... so there is a way to salvage... I just can't seem to get it to work. Any thoughts on what I can try from here?
Click to expand...
Click to collapse
LeveeWasDry said:
Battery is at 100% now but it still will not boot into recovery. I flash the .pit file and then the firmware file stated above. I try different combinations all to no fix. I'm still stuck in a bootloop.
I don't understand really. The phone seems to be soft-bricked obviously... so there is a way to salvage... I just can't seem to get it to work. Any thoughts on what I can try from here?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2755970
Have you tried this link ? Contains the working recovery to flash.

mjh68 said:
http://forum.xda-developers.com/showthread.php?t=2755970
Have you tried this link ? Contains the working recovery to flash.
Click to expand...
Click to collapse
the link provided above will fix your phone. Follow the steps exactly and you will be good to go.

Since I cannot start my phone, I can't root it under "Steps for Retail Edition" I have to skip straight to step 10 and flashing that files does not work.Unified_KK_Firmware_RE.tar So, am I screwed or what else is there to do?

LeveeWasDry said:
Since I cannot start my phone, I can't root it under "Steps for Retail Edition" I have to skip straight to step 10 and flashing that files does not work.Unified_KK_Firmware_RE.tar So, am I screwed or what else is there to do?
Click to expand...
Click to collapse
The Unified_kk is not the full firmware. It's only the radio, recovery, etc.
But to verify from a previous post, you tried the full firmware for nc4?
When you boot to download mode, in the upper left corner there is some info and codes. What are they on your phone?

LeftyGR said:
The Unified_kk is not the full firmware. It's only the radio, recovery, etc.
But to verify from a previous post, you tried the full firmware for nc4?
When you boot to download mode, in the upper left corner there is some info and codes. What are they on your phone?
Click to expand...
Click to collapse
Yes. I've tried the full firmware for NC4 and it just bootloops. This is what the download page tells me.
ODIN MODE
PRODUCT NAME: SM-N900V
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, R1, A3, P1
WRITE PROTECTION: Enable
UDC START

LeveeWasDry said:
Yes. I've tried the full firmware for NC4 and it just bootloops. This is what the download page tells me.
ODIN MODE
PRODUCT NAME: SM-N900V
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, R1, A3, P1
WRITE PROTECTION: Enable
UDC START
Click to expand...
Click to collapse
Ok. Everything seems right to me. It's definitely not you!
What info did you get from the previous owner? When you bought it did they tell you it was bricked and what they did to brick it?

LeftyGR said:
Ok. Everything seems right to me. It's definitely not you!
What info did you get from the previous owner? When you bought it did they tell you it was bricked and what they did to brick it?
Click to expand...
Click to collapse
I was told nothing really. They just told me that it boot looped and it was stuck on the "Firmware Upgrade has Encountered an Issue" screen. It was more so a gamble really. The phone looks impeccable so it seems to be rather new. Maybe the owner had flashed it before and tool the OTA, soft-bricking it... I don't know. I just know that its last flash was 4.4 KK because it wouldn't let me downgrade firmware.

I'm not quite sure what else you could look at doing here. You seem to be doing everything right, but not getting the right results.
The following is an option:
Seems to me that the previous owner did something "unofficial" that caused this. If it was something official, it would've easily been accepted as a replacement via warranty situation. But instead, they got rid of it!
---------- Post added at 07:33 AM ---------- Previous post was at 07:26 AM ----------
Actually, there is one more thing you can try. You should never do this because there is too high a risk of bricking if you do something wrong. But you are already pretty bricked, so what else have you got to lose?
http://forum.xda-developers.com/showthread.php?t=2610757
Go check this out, and nand erase all during the odin flash.

[Q] (for me) unrecoverable softbrick

Guys, I need a hand here, as I hit a solid brick wall and no amount of scouring the forums helped me find a suitable solution.
Hardware involved:
Galaxy Note 3 N9005 that was running 4.4.2 (bought unlocked)
iMac with Yosemite and Parallels with Ubuntu and Windows 10 with Heimdall and Odin 3.09 installed
What I set out to do: root & install clockworkmod recovery with the ultimate goal to install Linux on Android. I had my previous Note 2 and LG P990 rooted too, so I was not entirely new to the procedure.
What I "achieved": Heimdall would not work at all due to a problem that apparently affects all Samsung 4.4.2 devices. So I got Parallels on my Mac and installed Windows 10 Technical Preview to run Odin. After several attempts I finally managed to got Odin to say "PASS" on the CF Auto-Root procedure. However, the phone would not boot anymore and always return to it's ODIN state. But I also succeeded to get Clockworkmod installed.
With that I installed Cyanogen, thinking to be able to get around the booting problem. I wasn't. Now when booting Cyanogen, I get a message that encryption was unsuccesful and the device needs to be restored.
I would like to comply and downloaded the stock files for restoring through Odin, but now even with the device in the proper ODIN download state, the phone is no longer recognized by the Software. Tried about a hundred times now with reboot etc. and nothing seems to work. Even KIES does note recognize the phone anymore.
I can enter CWM and Odin modes just fine. I just can't boot and I can't get it recognized by my Mac anymore. My best guess is I unintentionally screwed up the partition table / PIT file and now I can't restore it anymore.
I am at the end of the rope here and getting desperate, any suggestions (preferably step by step) would be most welcome!

psearcher said:
Guys, I need a hand here, as I hit a solid brick wall and no amount of scouring the forums helped me find a suitable solution.
Click to expand...
Click to collapse
It's very weird that in Download Mode Odin don't recognize your device. Remember that you need Kies 3 for android 4.4.2 and Kies 3 has to be completely closed for use ODIN.

Joku1981 said:
It's very weird that in Download Mode Odin don't recognize your device. Remember that you need Kies 3 for android 4.4.2 and Kies 3 has to be completely closed for use ODIN.
Click to expand...
Click to collapse
Ok, I tried on my Win Laptop from work now and Odin can recognize the Smartphone there. I will take it home on the weekend to go further.
However, a hasty try to flash the stock rom (Vodafone NL Lollipop) resulted in the same "encryption failed" error I had before. Any ideas what I am doing wrong?

psearcher said:
Ok, I tried on my Win Laptop from work now and Odin can recognize the Smartphone there. I will take it home on the weekend to go further.
However, a hasty try to flash the stock rom (Vodafone NL Lollipop) resulted in the same "encryption failed" error I had before. Any ideas what I am doing wrong?
Click to expand...
Click to collapse
Your phone is unlocked. You had to try the POLAND Lollipop firmware or wait till future udpates.

Joku1981 said:
Your phone is unlocked. You had to try the POLAND Lollipop firmware or wait till future udpates.
Click to expand...
Click to collapse
Hi there Joku!
Just tried the Polish Lollipop Firmware and it still keeps displaying the "Encryption failed" error. It looks like it does not matter which file I flash, it will keep showing the same error.
Like I said, I believe I somehow broke the PIT file of the phone. Any ideas how to fix this?
Regards,
Rene

Try this pit file.
https://meocloud.pt/link/4ebb315a-867c-4469-bfdf-c234ca9f4d1e/PIT-File-DBT VFG-UK-MSM8974.zip/
Put it on pit field. Set repartition on and auto reboot. If all goes well then try to flash the Vodafone NL 4.4.2 rom (it's the one I use so I know that this pit file works with it).
Sent from my SM-N9005
---------- Post added at 09:42 PM ---------- Previous post was at 09:38 PM ----------
If it doesn't work try to go in TWRP and wipe the /data partition and then reflash the stock rom.
Sent from my SM-N9005

Question solved!
DeuXGod said:
Try this pit file.
Put it on pit field. Set repartition on and auto reboot. If all goes well then try to flash the Vodafone NL 4.4.2 rom (it's the one I use so I know that this pit file works with it).
Sent from my SM-N9005
---------- Post added at 09:42 PM ---------- Previous post was at 09:38 PM ----------
If it doesn't work try to go in TWRP and wipe the /data partition and then reflash the stock rom.
Sent from my SM-N9005
Click to expand...
Click to collapse
Thanks DeuXGod, but by now I more or less stumbled on the solution by trial and error. I'll post it here, hoping that somebody may benefit from my endeavours in the future. As a n00b I can't post links though. Sorry for that.
I do not know if all the steps are necessary or correct, but in the end they did lead me back to a working device. :fingers-crossed:
After trying a few PIT files here in the forums, the problems did not go away. Some of them would lead to a phone that just got stuck at the "Samsung" screen and would not fully boot up.
So I got the idea to flash back the "old" Dutch 4.4.2 ROM, which I downloaded from Sammobile and flashed in ODIN. After booting it showed a bit of a different error message, saying the file system was corrupted
I googled for this and stumbled on a small ZIP file that is supposed to fix "cannot mount DATA / EFS errors". I loaded this on my SDXC.
Flashed aforementioned ZIP file through the recovery from the SDXC.
After rebooting it still showed the same error, so I got back to recovery, did a factory reset and a cache wipe.
Another reboot and much to my surprise (and great relief) the phone booted up normally again!
From there I thought that if this worked, the Polish 5.0 should work too. I flashed it. Flashed CF Auto Root after that and everything seems to be working fine!
I set everything up and the phone is now restoring the apps etc. So far looking very good!

[Help]Samsung Galaxy S5 softbrick :(

Posted first on reddit but didn't get to much help there. Someone suggested a debrick image, however i have not found one for the SM-G900P model of the Galaxy S5(I have found the image for other carriers though :crying
"Long story short I got stuck in a bootloop and now want to go back to stock rom for the Sprint Galaxy S5(SM-G900P). However, before this bootloop I believe I forgot to turn usb debugging on so every time I try to flash stock rom in Odin it hangs on setup connection for 10-15mins then says FAILED. I've tried all the Odin fixes(different usb cable, different usb port, different computer, etc.) and still same issue, I did however notice in BLUE: Secure Download:Enable(I never noticed that while flashing the phone before and think it may be the issue). Phone was rooted, on lollipop 5.0, and had TRWP Recovery on it but booting to bootloader takes me to Odin Mode for some strange reason. Please send any help you can my way."
My Odin Mode looks like this(Sorry for no picture):
--------------------------------------------------------------------
ODIN MODE
PRODUCT NAME: SM-G900P
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
REACTIVATION LOCK(KK): OFF
KNOX WARRANTY VOID: 0x1 (4)
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T3, R1, A3, P1
SECURE DOWNLOAD : ENABLE
UDC START
-------------------------------------------------------------------
~Android Logo
~Downloading..
~Do not turn off target!!
If you need any more info about phone please let me know.

MrHundreds said:
Posted first on reddit but didn't get to much help there. Someone suggested a debrick image, however i have not found one for the SM-G900P model of the Galaxy S5(I have found the image for other carriers though :crying
"Long story short I got stuck in a bootloop and now want to go back to stock rom for the Sprint Galaxy S5(SM-G900P). However, before this bootloop I believe I forgot to turn usb debugging on so every time I try to flash stock rom in Odin it hangs on setup connection for 10-15mins then says FAILED. I've tried all the Odin fixes(different usb cable, different usb port, different computer, etc.) and still same issue, I did however notice in BLUE: Secure Download:Enable(I never noticed that while flashing the phone before and think it may be the issue). Phone was rooted, on lollipop 5.0, and had TRWP Recovery on it but booting to bootloader takes me to Odin Mode for some strange reason. Please send any help you can my way."
My Odin Mode looks like this(Sorry for no picture):
--------------------------------------------------------------------
ODIN MODE
PRODUCT NAME: SM-G900P
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
REACTIVATION LOCK(KK): OFF
KNOX WARRANTY VOID: 0x1 (4)
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T3, R1, A3, P1
SECURE DOWNLOAD : ENABLE
UDC START
-------------------------------------------------------------------
~Android Logo
~Downloading..
~Do not turn off target!!
If you need any more info about phone please let me know.
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist. To get you the best available help, I'm going to move this thread to your device's Q&A forum. Good luck!

Hi @MrHundreds......
First of all, USB debugging has absolutely no impact on Odin flashing....
Whether it's enabled or disabled makes no difference.....
Second...
Don't give up on trying to odin flash.....
Perseverance is the name of the game...
Do the usual things....
Make sure antivirus and firewalls are disabled.
Make sure you have the Samsung usb drivers installed.
If you have Kies on your PC/Laptop, disable it in task manager before running Odin.
Run Odin as an administrator.
Only use usb sockets that are directly connected to the PC/Laptop main board.
Try multiple usb cables.....The one that came with the phone should be your primary choice though.
Try different versions of Odin (though the newer versions will have a better chance of working)
Re download the firmware package....just to rule out the possibility of a corrupt file (it does happen)
Try all of the above on different PC's with different OS versions.....it *can* be as simple as that....xp, vista, 7 & 8 all have successful track records....can't vouch for 10 though.
You could (as a last resort) try flashing a pit file with the firmware....this will erase every trace of the previous OS from your device as it flashes the new OS.....normally all odin does is overwrite what is already on the device.....but a word of caution.....If you flash the wrong pit, or the pit flash fails, it will permanently brick the device.
http://i.imgur.com/rVnFwJM.jpg

keithross39 said:
Hi @MrHundreds......
First of all, USB debugging has absolutely no impact on Odin flashing....
Whether it's enabled or disabled makes no difference.....
Second...
Don't give up on trying to odin flash.....
Perseverance is the name of the game...
Do the usual things....
Make sure antivirus and firewalls are disabled.
Make sure you have the Samsung usb drivers installed.
If you have Kies on your PC/Laptop, disable it in task manager before running Odin.
Run Odin as an administrator.
Only use usb sockets that are directly connected to the PC/Laptop main board.
Try multiple usb cables.....The one that came with the phone should be your primary choice though.
Try different versions of Odin (though the newer versions will have a better chance of working)
Re download the firmware package....just to rule out the possibility of a corrupt file (it does happen)
Try all of the above on different PC's with different OS versions.....it *can* be as simple as that....xp, vista, 7 & 8 all have successful track records....can't vouch for 10 though.
You could (as a last resort) try flashing a pit file with the firmware....this will erase every trace of the previous OS from your device as it flashes the new OS.....normally all odin does is overwrite what is already on the device.....but a word of caution.....If you flash the wrong pit, or the pit flash fails, it will permanently brick the device.
Click to expand...
Click to collapse
I will continue to try to get Odin to work with the methods you suggested above, but as far as other different OS's go I have a slim selection(Windows 7, Windows 10, Ubuntu Mate and Arch Linux). Also would Heimdall have a better chance of working opposed to Odin? I have tried Heimdall once with a pit I found for my device but it also failed. Looking around XDA I found some programs like skipsoft, go thru the whole process up until it is about to flash and replies with waiting for USB debugging to be enabled. Anyways I appreciate your response to my question and will try your "fixes" and see how that goes.

From everything I have read, Heimdall has less of a success rate than Odin....
I've also read that unless you know exactly how to handle it, it is considerably more complicated than Odin.......as such I've never used it and can't really comment on this method.
My (limited) experience stretches as far as multiple Samsung devices and Odin.....
http://i.imgur.com/rVnFwJM.jpg

keithross39 said:
From everything I have read, Heimdall has less of a success rate than Odin....
I've also read that unless you know exactly how to handle it, it is considerably more complicated than Odin.......as such I've never used it and can't really comment on this method.
My (limited) experience stretches as far as multiple Samsung devices and Odin.....
Click to expand...
Click to collapse
Okay i was not able to flash stock rom however I did get TWRP Recovery installed on it after the third try, can I somehow use TWRP to get stock rom back on the phone?(I had all important info backup on pc so i have no problem wiping the phone clean)

MrHundreds said:
Okay i was not able to flash stock rom however I did get TWRP Recovery installed on it after the third try, can I somehow use TWRP to get stock rom back on the phone?(I had all important info backup on pc so i have no problem wiping the phone clean)
Click to expand...
Click to collapse
You can download a custom, TouchWiz-based ROM and flash it to TWRP.

^agreed.....
You can't flash an official firmware through recovery.....wrong file type....
But custom roms aren't a problem.
As mentioned, some of those custom roms are Samsung Touchwiz based, so you'll have the look and feel of stock, but without the disadvantages.....
http://i.imgur.com/rVnFwJM.jpg

keithross39 said:
^agreed.....
You can't flash an official firmware through recovery.....wrong file type....
But custom roms aren't a problem.
As mentioned, some of those custom roms are Samsung Touchwiz based, so you'll have the look and feel of stock, but without the disadvantages.....
Click to expand...
Click to collapse
Okay i was able to get Cyanogenmod installed thru twrp with no issue, phone works good but can i get stock rom on device now that it is no longer in a boot loop.

MrHundreds said:
Okay i was able to get Cyanogenmod installed thru twrp with no issue, phone works good but can i get stock rom on device now that it is no longer in a boot loop.
Click to expand...
Click to collapse
I've read of a couple of cases on XDA (just recently) where a firmware flash just simply will not (for some reason) 'take'.....it's looking like your device may well have to be added to that list.....
Nobody has been able to work out why a firmware flash is unsuccessful....it just *is*......
My advice would be (for the moment) to stay away from official stock, and to experiment with the various available custom roms until you find one that suits you.....
If you *really* want the stock touchwiz 'look' try one of the stock based custom roms.......
http://i.imgur.com/rVnFwJM.jpg

keithross39 said:
I've read of a couple of cases on XDA (just recently) where a firmware flash just simply will not (for some reason) 'take'.....it's looking like your device may well have to be added to that list.....
Nobody has been able to work out why a firmware flash is unsuccessful....it just *is*......
My advice would be (for the moment) to stay away from official stock, and to experiment with the various available custom roms until you find one that suits you.....
If you *really* want the stock touchwiz 'look' try one of the stock based custom roms.......
Click to expand...
Click to collapse
Oh okay, thank you for all your help you have no idea how grateful I am. I'll stick with Cyanogenmod since I have used it before and like it in general. Thank you from help me get from softbrick to a working phone

No problem fella......it was you doing the sweating though.....I just made some suggestions and handed out some info.....
Glad it's sorted though......
http://i.imgur.com/rVnFwJM.jpg

bricked sm-t580

i have the T580 32GB of a friend here, that does not work at the moment (and maybe never again ) - the problem is that on startup it only gives this message in red letter :
could not do normal boot invalid kernel length
Click to expand...
Click to collapse
the only thing i can do is get into download mode - but i fail when i try to install a stock rom via odin - after NAND Write Start!! it times out and gives me a fail.
i already tried a 3 different odin versions and adroid 6.0, 7.0 and 8.01 Stock Rom for SM-T580 but no luck so far.
another problem is my friend does not know what the android version he was on before that hapend - and the tablet has Samsung FRP on.
maybe some of the experts here have an advice what i can try otherwise this tab a is really bricked - furthermore i wonder how this could happen as my friend swears he did not try to put twrp or anything else onto the tablet ....

Have you tried flashing TWRP using ODIN? (AP Slot)

i do not know if flashing twrp is a good idea as i do not know if oem unlock is enabled - and as it does not boot up i cannot switch it on in developer options

ilovebytes said:
i do not know if flashing twrp is a good idea as i do not know if oem unlock is enabled - and as it does not boot up i cannot switch it on in developer options
Click to expand...
Click to collapse
Wouldn't it simply fail if OEM unlocking was disabled? I don't know honestly. I'd try it if no other solutions come up.

ilovebytes said:
i have the T580 32GB of a friend here, that does not work at the moment (and maybe never again ) - the problem is that on startup it only gives this message in red letter :
the only thing i can do is get into download mode - but i fail when i try to install a stock rom via odin - after NAND Write Start!! it times out and gives me a fail.
i already tried a 3 different odin versions and adroid 6.0, 7.0 and 8.01 Stock Rom for SM-T580 but no luck so far.
another problem is my friend does not know what the android version he was on before that hapend - and the tablet has Samsung FRP on.
maybe some of the experts here have an advice what i can try otherwise this tab a is really bricked - furthermore i wonder how this could happen as my friend swears he did not try to put twrp or anything else onto the tablet ....
Click to expand...
Click to collapse
I think you are going about it wrong. Instead of booting to download mode, try booting to recovery mode via Home, Vol Up and Power and then selecting Factory Reset. This is always necessary before you can use download to flash a ROM via Odin and it might make using Odin unnecessary.

of course i tried to get into receovery mode but the problem is i can't - when i do home, vol up and power absolutely nothing happens, i only get into download mode
edit: i believe FRP is the Problem this prevents odin from writing the files to the tablet - as it allways times out with :
Complete(Write) operation failed.
Click to expand...
Click to collapse
what i do not really understand is why FRP does not let odin flash an original samsung firmware ?

[QUOTE what i do not really understand is why FRP does not let odin flash an original samsung firmware ?[/QUOTE]
This sounds more like a binary issue. I have reason to believe you are what's called an FRP Binary Lock. Recovery is usually inaccessable or re-routed and you cannot "seem" to use Odin3 but in fact you can. This issue you apparently are having sounds oddly like some issues I've had on these devices and is often a result of bad Rooting or invalid firmware being installed. This overloads the binaries and puts the device in a locked mode with symptoms of an inaccessible Recovery a difficult to use Odin3 or a bootloop. Most of the time I hear of a notification somewhere of an FRP lock. If this is the situation you are in here is a link to a page of mine that will give you the files to helpfully solve your issue. Let me know if that works or not.
https://forum.xda-developers.com/general/help/custom-binary-blocked-frp-lock-2019-t3979661

Casper Young said:
If this is the situation you are in here is a link to a page of mine that will give you the files to helpfully solve your issue. Let me know if that works or not.
https://forum.xda-developers.com/general/help/custom-binary-blocked-frp-lock-2019-t3979661
Click to expand...
Click to collapse
it sounds like i am in the same situation and i tried your files but it does not let me download them through odin - i also wrote you a pm maybe you find the time to answer me.
i really wonder how this could happen as my friend swears he did never try to flash anything onto the tab, and i really believe him as he absolutely knows nothing about flashing or where to get a firmware and not even how to get into dl mode ....

ilovebytes said:
it sounds like i am in the same situation and i tried your files but it does not let me download them through odin - i also wrote you a pm maybe you find the time to answer me.
i really wonder how this could happen as my friend swears he did never try to flash anything onto the tab, and i really believe him as he absolutely knows nothing about flashing or where to get a firmware and not even how to get into dl mode ....
Click to expand...
Click to collapse
The situation I was suspecting is a "Custom Binaries are Blocked by FRP Lock" to which you would have seen a notification of it in one of 4 ways. Your situation is somewhat similar because you cannot access Recovey and although Download Mode is accessable it appears useless. Your device is not Bricked. A bricked device is unusable in any way and these days most devices can be restored.
You do seem to be having some difficulties that are usually common with binary issues. You can in fact use Odin3 but how is the question. Usually one can flash in the Stock firmware and that returns the device to normal. When it becomes impossible to flash in stock firmware or anything else it seems, to my experiance has always been a Binary issue. I will provide a link to the 4File Official firmware. And instructions for you to properly use it for your needs.
SM-T580 Official Stock Firmware 4Files
https://drive.google.com/open?id=1zvhwUfSRW44V1ZwEsHLRvlh-T0M79ks9
I'll assume you know something about using Odin3. Unzip the file to your desktop. There are 4 files but you'll only use 3 of them. You can use the patched version of Odin3.13B or you can use Odin3.14. Place the files in their respective places. BL, and AP are easy enough to see where they go. Now there is a file labeled CSC and one labeled HOME CSC. You will only use one of them. The CSC file returns your app data to factory settings (it erases everything). The Home CSC file keeps the app data. So it's your choice which one you choose. These are Official Firmware Files so you should be able to flash them in. Should that not work for you my most likely answer would be that your binaries are the issue and that is why you can't as of yet use Odin sucessfully. Does Odin even try to initiate a flash then stalls or does it do nothing altogether?
There are two different Binary files for the SM-T580 that I have. I would suggest using the Binary 4 FRP first. f I recall correctly the Odin3.13B patched version was made for this. Place the file in the AP section and try flashing it. You should get a few gears on the screen turning if it applied, or maybe not. If that fails use the U4 Binary Unlock file. It is only after you flash in the binary files that you can then install the Stock Firmware. It is the overloaded binaries that prevent the use of Odin as you may be experiancing. I am also including the Knox cleaner in case you need to reset it.
SM-T580 Binary files:
Binary 4 FRP Unlock
https://drive.google.com/open?id=1iXrZR2E7m6Ai5InAw8u3lzeLhb3ThRo5
U4 Binaries. This is two files. Flash one at a time using the AP section. They are labeled 1rst or 2nd
1. https://drive.google.com/open?id=1rX_luP_0W4ygdloIr2Gr9TCSfqFyaTK-
2. https://drive.google.com/open?id=1xsw4GVYtNMJhiMXV2cR2jaJvToG_n6Pi
Knox Cleaner: Also flashed in using the AP section of Odin3
https://drive.google.com/open?id=1EolYe9auY9jslYSpSgHoon_YB00D2noV
Good Luck and let me know if this helps or not.

lewmur said:
I think you are going about it wrong. Instead of booting to download mode, try booting to recovery mode via Home, Vol Up and Power and then selecting Factory Reset. This is always necessary before you can use download to flash a ROM via Odin and it might make using Odin unnecessary.
Click to expand...
Click to collapse
Only if they could get into Recovery they may be able to reset it.
I have never once needed to go to Recovery to do "anything" before using Odin3 to flash.
The only time I've had to go there (repetedly) and reset was when trying to get past FRP Google Account Protection. Sometimes it takes out the page I want to get to and I need to reset it to get to it again. This is "not" always neccesary before flashing a ROM which rewrites the device programing.

sorry for double post

@Casper Young
thanks for your help so far, i am gonna try your suggestions on weekend when i have a bit more spare time - hope i can get the tab running again