Can flash firmware but cannot access Recovery - Verizon Galaxy Note 3 Q&A, Help & Troubleshooting

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.

Related

[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.

[Q] incidentally formated stock rom slot in ss

I got distracted and accidentally formatted the stock rom slot in ss. Now it will not boot. Ss comes up then the screen goes black. I tried to create a new rom slot but its saying there is no available memory. Ive been reading a lot of posts but any advice would be greatly appreciated
Have you tried flashing a new Rom to that slot yet?
talonzme said:
Have you tried flashing a new Rom to that slot yet?
Click to expand...
Click to collapse
Not yet. Would i just download the stock firmware to an sd card and flash it that way? i've been trying to mess around with odin but the i cant get a good firmware download that odin will recognize
You have safestrap still functional? If so then yes you can download stock rom and install.
talonzme said:
You have safestrap still functional? If so then yes you can download stock rom and install.
Click to expand...
Click to collapse
yes safstrap is the only thing that comes up. its either enter recovery or black screen. It is saying no os loaded and the install and wipe button are red when on stock rom slot. I've downloaded a stock rom on my sd but it isn't showing up in safestrap. but there is a MD5 file there when I check it on my computer
Reboot the phone into download mode and flash with Odin. You will need to find stock note 3 in tar format for Odin.
Ill try that now. I got safestrap to recognize the file but it fails everytime i flash
Try these. VERY IMPORTANT-Make sure you get the correct firmware for your phone. http://wccftech.com/how-to-install-stock-firmware-on-galaxy-note-3-all-models/
talonzme said:
Try these. VERY IMPORTANT-Make sure you get the correct firmware for your phone. http://wccftech.com/how-to-install-stock-firmware-on-galaxy-note-3-all-models/
Click to expand...
Click to collapse
I followed the steps and made sure I got eh correct firmware but it failed and now my phone is at "firmware upgrade encountered an issue. Please use Software Repair Assistang & try again.
You can use kies to try and restore as well. Just make sure you remove it after as it can cause future problems with installs and Odin
talonzme said:
You can use kies to try and restore as well. Just make sure you remove it after as it can cause future problems with installs and Odin
Click to expand...
Click to collapse
Ive tried that as well. Kies doesnt recognize my phone....Ive tried to trouble shoot....I downloaded the correct version and updated but still nothing..
Im looking for a software repair assistant download now
Before doing that remove everything to do with the phone from your computer. Kies, Odin.....all of it. Download just the driver for your phone. Try Odin again. There are reports of Odin and kies clashing. I feel your frustration, I had the same issue with my note 2. When in the download screen what is listed in the top left corner?
talonzme said:
Before doing that remove everything to do with the phone from your computer. Kies, Odin.....all of it. Download just the driver for your phone. Try Odin again. There are reports of Odin and kies clashing. I feel your frustration, I had the same issue with my note 2. When in the download screen what is listed in the top left corner?
Click to expand...
Click to collapse
ok i'll try that.
top left corner:
ODIN MODE (in red)
Product Name: SM-n900v
Current Binary: Samsung Official
System Status: Custom
Knox Kernel Lock: 0x0
Qualcomm Secureboot: Enable (CSB)
AP SWREV: S1, T1, R1, A3, P1
WRITE PROTECTION: Enable
UDC START (in red)
SW REV CHECK FAIL : (aboot) Fused 3 > Binary 1 (in red)
then the Please use software assistant
I don't recognize the sw.rev check line. That may be part of the problem. Also note that wrote protection is enabled. There might be the need for some JTAG intervention.
---------- Post added at 04:10 PM ---------- Previous post was at 04:08 PM ----------
For JTAG my recommendation would be this place, http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-note-3-jtag-brick-repair/. They fixed my note 2 and unlocked the gsm (remove carrier specificity). Reasonable prices and quick turnaround.
talonzme said:
I don't recognize the sw.rev check line. That may be part of the problem. Also note that wrote protection is enabled. There might be the need for some JTAG intervention.
---------- Post added at 04:10 PM ---------- Previous post was at 04:08 PM ----------
For JTAG my recommendation would be this place, http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-note-3-jtag-brick-repair/. They fixed my note 2 and unlocked the gsm (remove carrier specificity). Reasonable prices and quick turnaround.
Click to expand...
Click to collapse
ok...thanks for your help man. I guess thats what I'll have to do
Definitely a bummer.
so your saying write protection that is enabled is time for jtag?
Not to sound rude, but i think the write protection is always enabled. I did the exact samething. I just used odin and returned it back to stock. bam fixed. I just checked mine and it shows enabled.
l
the_rooter said:
so your saying write protection that is enabled is time for jtag?
Not to sound rude, but i think the write protection is always enabled. I did the exact samething. I just used odin and returned it back to stock. bam fixed. I just checked mine and it shows enabled.
Click to expand...
Click to collapse
Im open to ideas. I've tried 2 stock tar files and both have failed repeatedly.
Ryan303 said:
Im open to ideas. I've tried 2 stock tar files and both have failed repeatedly.[/Q]
Where did u get the tar files and pit files from? and what version of odin are you using.
EDIT: Go here and make sure you dont have odin or keis installed, and follow these steps. down to the exact.
http://forum.xda-developers.com/showthread.php?t=2483380
EDIT 2: If odin doesnt reconize the tar file. at the end of the file may be two many extentions.. right click and rename. keep the same name but remove the extra extentions except the tar.
Click to expand...
Click to collapse
the_rooter said:
Ryan303 said:
Im open to ideas. I've tried 2 stock tar files and both have failed repeatedly.[/Q]
Where did u get the tar files and pit files from? and what version of odin are you using.
Click to expand...
Click to collapse
I tried this one from a thread here http://www.androidfilehost.com/?fid=23501681358549642
i just googled for the pit file. I've tried odin 3.09 and 3.10. But I may not even be using it correctly. I followed some steps i found in a thread on this site
Click to expand...
Click to collapse

soft-bricked galaxy s5 g900f

My s5 g900f recently started having this weird battery issue where the battery would go from 100% - 0 in under an hour, But before I got to replace the battery I jus woke up one morning n the phone was off, tried putting it on after recharging but all it did was continuously show the Samsung logo and reboot. Got a new battery but no change, plus I only seem to have access to download mode.
Is it rooted? Custom ROM/kernel?
Or is it totally stock.
It was totally stock,hadn't even rooted it yet
Install a battery monitoring app, see if its an app or system process draining it
Clear all caches in recovery
Flash a stock ROM from sammobile .com and factory reset
*Detection* said:
Install a battery monitoring app, see if its an app or system process draining it
Clear all caches in recovery
Flash a stock ROM from sammobile .com and factory reset
Click to expand...
Click to collapse
That's just it, I can't get past the galaxy s5 logo... As soon as it shows that it reboots and shows the logo over and over again. plus I can't access recovery, am only able to access download mode.
Sleekkite said:
That's just it, I can't get past the galaxy s5 logo... As soon as it shows that it reboots and shows the logo over and over again. plus I can't access recovery, am only able to access download mode.
Click to expand...
Click to collapse
You flash stock ROMs from download mode using ODIN
Instructions under the download on sammobiles site
*Detection* said:
You flash stock ROMs from download mode using ODIN
Instructions under the download on sammobiles site
Click to expand...
Click to collapse
Okay bro let me give it a go ,am i tied to the specific rom for my region or can i just pick which ever ,because i am unawear of the phones original region ,i dint get it from any mobile service provide and am certain every time i did a factory reset id it would boot with the default language as french then id have to set it back to english.
Sleekkite said:
Okay bro let me give it a go ,am i tied to the specific rom for my region or can i just pick which ever ,because i am unawear of the phones original region ,i dint get it from any mobile service provide and am certain every time i did a factory reset id it would boot with the default language as french then id have to set it back to english.
Click to expand...
Click to collapse
Pick whichever region you like, just match the model S5 you own to the firmware (eg: G900F)
*Detection* said:
Pick whichever region you like, just match the model S5 you own to the firmware (eg: G900F)
Click to expand...
Click to collapse
went ahead and flashed a rom from sammobile.com like you suggested and it all went fine,...even got a pass at the end of it all. But it dint get fixed ,just got a recovery booting in blue when it rebooted same samsang s5 logo then it was the boot loop all over again.... any more details you think i could give that would give you a clue on what else i could try??
Sleekkite said:
went ahead and flashed a rom from sammobile.com like you suggested and it all went fine,...even got a pass at the end of it all. But it dint get fixed ,just got a recovery booting in blue when it rebooted same samsang s5 logo then it was the boot loop all over again.... any more details you think i could give that would give you a clue on what else i could try??
Click to expand...
Click to collapse
Flash this PIT file at the same time as the stock ROM
http://forum.xda-developers.com/attachment.php?attachmentid=2721101&d=1399024091
Add it to the PIT section in ODIN and the ROM to the AP or PDA section, flash together
*Detection* said:
Flash this PIT file at the same time as the stock ROM
http://forum.xda-developers.com/attachment.php?attachmentid=2721101&d=1399024091
Add it to the PIT section in ODIN and the ROM to the AP or PDA section, flash together
Click to expand...
Click to collapse
Flashed the pit file and rom at the same time, slight change... Now I simply get the Samsung logo then the screen goes blank n pressing the power button after it goes blank seems to do nothing unless I take the battery out n put it back in.
Are you 100% sure it is a G900F?
What does download mode say?
*Detection* said:
Are you 100% sure it is a G900F?
What does download mode say?
Click to expand...
Click to collapse
this is what i have........
ODIN MODE
PRODUCT NAME: Samsung official
SYSTEM STATUS: official
REACTIVATION LOCK(KK) : OFF
KNOX WARRANTY VOID :0x1 (4)
QUALCOMM SECUREBOOT: ENABLED (CSB)
RP SWREV: S1, T1, R1, A1, P1
SECURE DOWNLOAD : ENABLED
UDC START
Download Mode on mine (Volume Down & Home & Power) says:
ODIN MODE
PRODUCT NAME: SM-G900F
etc
etc etc
*Detection* said:
Download Mode on mine (Volume Down & Home & Power) says:
ODIN MODE
PRODUCT NAME: SM-G900F
etc
etc etc
Click to expand...
Click to collapse
Sorry for that,
ODIN MODE
PRODUCT NAME: SM-G900F
CURRENT BINARY : Samsung official
SYSTEM STATUS: official
REACTIVATION LOCK(KK) : OFF
KNOX WARRANTY VOID :0x1 (4)
QUALCOMM SECUREBOOT: ENABLED (CSB)
RP SWREV: S1, T1, R1, A1, P1
SECURE DOWNLOAD : ENABLED
UDC START
Anything yet detection?
I have no idea why it's not working, if it is definitely the G900F, which it seems to be if download mode says so
Make sure you're running ODIN as Admin, using a native PC not a Mac, got the Samsung drivers installed, and running the latest version of ODIN, I think it 3.10.7 or something
Some people report using an older version having worked when the latest failed too, try 3.07 etc
You could also try flashing TWRP 2.8.7.0 with ODIN, and see if you can get into recovery, if you can, try flashing a custom ROM from TWRP
Almost seems too obvious......
But can you get into recovery? If so, have you tried wiping data and cache?.......
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
Almost seems too obvious......
But can you get into recovery? If so, have you tried wiping data and cache?.......
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
Sleekkite said:
That's just it, I can't get past the galaxy s5 logo... As soon as it shows that it reboots and shows the logo over and over again. plus I can't access recovery, am only able to access download mode.
Click to expand...
Click to collapse
That was my first thought too, but seems to be a deeper problem
He's getting a pass at the end of the odin flash, so we have to assume he's got a functioning OS on the device......unless he's got hold of a faulty firmware and Odin hasn't picked up on it during the flash.....
There are 16gb and 32gb versions of the device......did the OP use the correct pit file?.....
http://i.imgur.com/rVnFwJM.jpg

[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

900V stuck in bootloop after FW upgrade

My Father-in-law tried updating the firmware on my wife's SM-G900V and now it's stuck in a boot loop. I am able to get it into download mode and recovery (I've cleaned the cache and factory reset it dozens of times), and I have been able to flash the latest marshmallow and lollipop images using Odin (passes with no issues), but it's still stuck in the boot loop.
When I get home from work tonight my plan is to try some of the "debricking" and or "rooting" guides I've found on this site:
https://forum.xda-developers.com/ve...images-hardbrick-recovery-plan-t3387010/page1
https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529
Should one of these do the trick, or will I be wasting my time and should be trying something else? Thanks in advance for your advice/help!
RetroRider said:
My Father-in-law tried updating the firmware on my wife's SM-G900V and now it's stuck in a boot loop. I am able to get it into download mode and recovery (I've cleaned the cache and factory reset it dozens of times), and I have been able to flash the latest marshmallow and lollipop images using Odin (passes with no issues), but it's still stuck in the boot loop.
When I get home from work tonight my plan is to try some of the "debricking" and or "rooting" guides I've found on this site:
https://forum.xda-developers.com/ve...images-hardbrick-recovery-plan-t3387010/page1
https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529
Should one of these do the trick, or will I be wasting my time and should be trying something else? Thanks in advance for your advice/help!
Click to expand...
Click to collapse
I have not tried the first method so I cannot say if it will work for a stock debrick. If you are going to use that, make sure the phone is on a PB1/PD1 firmware.
The second one is rooting the phone. I have usedthis one with both CIDs and have had no issues. Since the phone wont boot, you might not be able to locate the CID, so please read the following thread before starting:
https://forum.xda-developers.com/verizon-galaxy-s5/help/to-id-cid-15-loading-app-t3756413
UPDATE: Also, Here is a link to a firmware with the pit file:
https://forum.xda-developers.com/ve...rmware-pit-verizon-samsung-galaxy-s5-t3757416
You may want to try that first before doing the other ones. Having a pit file during the firmware install sometimes helps to fix it.
Try it, see if it works, if you have any more issues, let me know.
Good Luck!
Thanks for the quick reply!
I updated the pit file and didn't get any errors from Odin. I think the issue I'm stuck with is I don't know what original firmware was on here, so I randomly pick on of the many available ones (like I mentioned previously, I've tried Lollipop and Marshmallow). This time I tried this one:
G900VVRU2BPB1_G900VVZW2BPB1_G900VVRU2BPB1_HOME.tar
The phone actually boots up and I hear the music of it booting up, but the screen doesn't come one. I can still get to recovery and download mode (but I can't see what I'm doing). Is this a matter of just working my way through the list of firmwares until I find the one that works?
Thanks again
RetroRider said:
Thanks for the quick reply!
I updated the pit file and didn't get any errors from Odin. I think the issue I'm stuck with is I don't know what original firmware was on here, so I randomly pick on of the many available ones (like I mentioned previously, I've tried Lollipop and Marshmallow). This time I tried this one:
G900VVRU2BPB1_G900VVZW2BPB1_G900VVRU2BPB1_HOME.tar
The phone actually boots up and I hear the music of it booting up, but the screen doesn't come one. I can still get to recovery and download mode (but I can't see what I'm doing). Is this a matter of just working my way through the list of firmwares until I find the one that works?
Thanks again
Click to expand...
Click to collapse
Do you see the "Samsung Galaxy S5" logo when it first boots up? It sounds like the screen went bad.
Fear_The_Fluff said:
Do you see the "Samsung Galaxy S5" logo when it first boots up? It sounds like the screen went bad.
Click to expand...
Click to collapse
It depends on which firmware I flash it with.....usually I get the logo as it's in the bootloop. The only change was when I used that PB1 firmware and it actually booted, minus the screen....
RetroRider said:
It depends on which firmware I flash it with.....usually I get the logo as it's in the bootloop. The only change was when I used that PB1 firmware and it actually booted, minus the screen....
Click to expand...
Click to collapse
Try going into Download/Odin Mode and (first grab some binoculars LOL!) take a look at the top (small letter) information and (you may want to write it down) see what the device information states there.
It just seems as though you may have a specific variant of the S5 that may have been unlocked and flashed to the one you believe that you have...
... OR you are correct with the Variant but, are trying to flash the wrong Firmware Version (one of the previous releases) and the device is preventing it.
I think that it may be the first assumption but, I could be wrong...
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Fear_The_Fluff said:
Do you see the "Samsung Galaxy S5" logo when it first boots up? It sounds like the screen went bad.
Click to expand...
Click to collapse
Ibuprophen said:
Try going into Download/Odin Mode and (first grab some binoculars LOL!) take a look at the top (small letter) information and (you may want to write it down) see what the device information states there.
It just seems as though you may have a specific variant of the S5 that may have been unlocked and flashed to the one you believe that you have...
... OR you are correct with the Variant but, are trying to flash the wrong Firmware Version (one of the previous releases) and the device is preventing it.
I think that it may be the first assumption but, I could be wrong...
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Click to expand...
Click to collapse
here's what I see when I go into download mode:
ODIN MODE
PRODUCT NAME: SM-G900V
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
REACTIVATION LOCK: OFF
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T2, R1, A2, P1
SECURE DOWNLOAD : ENABLE
UDC START
Is there anything there that tells me what version of firmware I should be using?
RetroRider said:
Is there anything there that tells me what version of firmware I should be using?
Click to expand...
Click to collapse
Product name is correct.
I'd flash this one: https://androidfilehost.com/?fid=818070582850486654
It's the latest firmware with full-wipe.
The first boot should take 12-15 min.
If the phone does not boot within 20 min. it will mean a hardware problem.

Categories

Resources