Database Users

Soft Brick?? HELP!

Ok, so I rooted my phone using a method where i flashed an older kernel then used towelroot to root, and then flashed back to NJ4. All was going well, and i installed the safestrap recovery. Then, today i was tryin to install the CM12 for the S4, and i messed up where i put the files for this, so when i was in safestrap, it told me it failed. I hit reboot, and that is when my phone essentially 'soft bricked'. I tries to boot up, fails and goes into download mode. I tried pulling out the battery, tried to go into recovery, but i cant do it. I tried to flash 4.2.2. stock s4 firmware thru odin, but it kept saying "Can't open the serial(COM) port." and fails. I can't do anything right now, please help im panicking Dx
UPDATE: I tried again to flash stock and now when i try to boot it tells me "firmware upgrade encountered an issue.." now when i try to flash something it won't let me because odin fails and says
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUAMDJ_I337MOYAAMDJ_I337MVLUAMDJ_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
HELP

Someone wiser then me will probably come in but if you can get to download mode no big worries. The com port issue makes me think drivers or the USB port. I would try different USB port and potentially uninstall drivers and reinstall. I believe skip makes a tool kit for s4 today may help. Can you see the device in adb?

McAwesome said:
Someone wiser then me will probably come in but if you can get to download mode no big worries. The com port issue makes me think drivers or the USB port. I would try different USB port and potentially uninstall drivers and reinstall. I believe skip makes a tool kit for s4 today may help. Can you see the device in adb?
Click to expand...
Click to collapse
I updated my last post btw. Dumb question but...what is adb?
EDIT:
Got it. I found a link to a rootable 4.4.2 md5 file and flashed it and it worked!

Not compatible
Well CM12 CM11 no CM period is compatible with out S4 because of the locked bootloader and youre trying to use the wrong firmware in odin once you upgrade to 4.4.4 or 4.4.2 you can no longer downgrade and go down to 4.2.2 so stop trying that you need to either download NB1 or NI1 odin files and restore it that way thats if you havent completely messed up youre phone Good Luck!

[Q] Experiencing Soft Brick Issues when trying to use Odin

I had a friend come over who wanted me to root his Verizon Note 3. It had the latest version of Android available for it when I tried rooting, which, from what I can gather, is Android 4.4.2 or 4.4.4. I can't seem to find exactly what it was.
This is the guide I followed when I started. Immediately I knew something was wrong because Odin gave a FAIL output. I didn't think to grab that exact output, but this is what I'm getting at this stage:
Code:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900VVRUCNC4_N900VVZWCNC4_N900VVRUCNC4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Here are the steps I'm taking based on this guide:
1. Downloaded latest Odin version.
2. Downloaded latest stock firmware (MJE).
3. Downloaded PIT file.
4. Reboot phone into Download Mode [Power + Home + Vol Down].
5. Open Odin.
6. Plug in phone. (Shows "Added!")
7. Choose PIT file and stock firmware (under "AP")
8. Choose Start.
This is where I get the error message. On the phone, it shows:
Code:
SW REV CHECK FAIL : [aboot]Fused 4 > Binary 3
I've been doing nothing but running in loops trying to fix this phone. I've tried so many different links and ran around to just about every forum I can find. If anyone has any advice, I really need to fix this as it's not my device.

otacon239 said:
I had a friend come over who wanted me to root his Verizon Note 3. It had the latest version of Android available for it when I tried rooting, which, from what I can gather, is Android 4.4.2 or 4.4.4. I can't seem to find exactly what it was.
This is the guide I followed when I started. Immediately I knew something was wrong because Odin gave a FAIL output. I didn't think to grab that exact output, but this is what I'm getting at this stage:
Code:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900VVRUCNC4_N900VVZWCNC4_N900VVRUCNC4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Here are the steps I'm taking based on this guide:
1. Downloaded latest Odin version.
2. Downloaded latest stock firmware (MJE).
3. Downloaded PIT file.
4. Reboot phone into Download Mode [Power + Home + Vol Down].
5. Open Odin.
6. Plug in phone. (Shows "Added!")
7. Choose PIT file and stock firmware (under "AP")
8. Choose Start.
This is where I get the error message. On the phone, it shows:
Code:
SW REV CHECK FAIL : [aboot]Fused 4 > Binary 3
I've been doing nothing but running in loops trying to fix this phone. I've tried so many different links and ran around to just about every forum I can find. If anyone has any advice, I really need to fix this as it's not my device.
Click to expand...
Click to collapse
MJE is not the latest....you will probably have to flash 4.4.4 (NC4 or NK1). You can NOT flash old versions one a newer version is installed.
Sent from my Note 3 via Tapatalk

donc113 said:
MJE is not the latest....you will probably have to flash 4.4.4 (NC4 or NK1). You can NOT flash old versions one a newer version is installed.
Sent from my Note 3 via Tapatalk
Click to expand...
Click to collapse
Where do I find that? All of the places I've gone seem to show MJE. Do you have a reliable source where I can find the latest version at a reasonable download speed.

otacon239 said:
Where do I find that? All of the places I've gone seem to show MJE. Do you have a reliable source where I can find the latest version at a reasonable download speed.
Click to expand...
Click to collapse
You can get the latest 4.4.4 firmware from here: http://www.sammobile.com/firmwares/database/SM-N900V/ (if you think there is a chance that it was on 4.4.2 when you tried to root it with de la vega, then you may try that firmware first... Once you put 4.4.4 on it, there's no current root method for it and no going back to 4.4.2).
If you follow Droidstyle's restore guide and use the 4.4.4 firmware (or 4.4.2 if that's what it was on ), that should hopefully help you get the phone fixed. Here's the link to Droidstyle's guide: http://forum.xda-developers.com/showthread.php?p=46461911

mattnmag said:
You can get the latest 4.4.4 firmware from here: http://www.sammobile.com/firmwares/database/SM-N900V/ (if you think there is a chance that it was on 4.4.2 when you tried to root it with de la vega, then you may try that firmware first... Once you put 4.4.4 on it, there's no current root method for it and no going back to 4.4.2).
If you follow Droidstyle's restore guide and use the 4.4.4 firmware (or 4.4.2 if that's what it was on ), that should hopefully help you get the phone fixed. Here's the link to Droidstyle's guide: http://forum.xda-developers.com/showthread.php?p=46461911
Click to expand...
Click to collapse
This link is requiring a sign-up to download at 15 kb/s. The best download link I've found is Rapid Gator, which is limiting me to 40 kb/s. Are there any other faster sources for this file? I searched Google for maybe 15-20 minutes with no luck. Is this file so rare that no one has uploaded it to a more reliable/faster site (e.g. Mega)? I feel like this should be a much more common file than it is.

otacon239 said:
This link is requiring a sign-up to download at 15 kb/s. The best download link I've found is Rapid Gator, which is limiting me to 40 kb/s. Are there any other faster sources for this file? I searched Google for maybe 15-20 minutes with no luck. Is this file so rare that no one has uploaded it to a more reliable/faster site (e.g. Mega)? I feel like this should be a much more common file than it is.
Click to expand...
Click to collapse
Sammobile does require a free registration to be able to download from their servers, but I think most people would say it's a generally reliable source.... and they give a md5 to make sure you get a good download. Maybe you'll find something else if you spend enough time searching. Good luck.

mattnmag said:
Sammobile does require a free registration to be able to download from their servers, but I think most people would say it's a generally reliable source.... and they give a md5 to make sure you get a good download. Maybe you'll find something else if you spend enough time searching. Good luck.
Click to expand...
Click to collapse
I just finally got his phone back on and it's no longer bricked. Now I can't seem to get towelroot to work. I open it on his phone and towelroot claims it's not supported on his phone. Am I missing something simple? Anyone here that's rooted a recent Note 3?

otacon239 said:
I just finally got his phone back on and it's no longer bricked. Now I can't seem to get towelroot to work. I open it on his phone and towelroot claims it's not supported on his phone. Am I missing something simple? Anyone here that's rooted a recent Note 3?
Click to expand...
Click to collapse
Good to hear you got the phone working again. If you're on 4.4.4, then towelroot will not work and there's no current root method.
4.4.2 was the last build version for the Verizon Note 3 that's rootable.

[Q] Cannot install stock firmware - ODIN fail

All,
As I noted in another thread, when I worked on my wife's new Galaxy S5, I let it upgrade to Android 5.0, then rooted it, then made some mistakes while restoring apps via Titanium Backup. In order to undo those mistakes, I want to roll back to the beginning and start over. To that end, I have been trying to reinstall stock firmware on the phone but I keep running into the same problem:
Code:
<ID:0/022> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900PVPU1ANCB_G900PSPT1ANCB_G900PVPU1ANCB_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/022> Odin v.3 engine (ID:22)..
<ID:0/022> File analysis..
<ID:0/022> SetupConnection..
<ID:0/022> Initialzation..
<ID:0/022> Get PIT for mapping..
<ID:0/022> Firmware update start..
<ID:0/022> aboot.mbn
<ID:0/022> NAND Write Start!!
<ID:0/022> FAIL! (Auth)
<ID:0/022>
<ID:0/022> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Based on reading here and elsewhere, I have tried the following:
Factory reset the phone
Verified that USB debugging is enabled and that allow remote lock is disabled
Ran Odin as Administrator
Use different versions of Odin (have tried 1.3, 1.85, 3.07, and 3.09)
Tried different firmware versions
Reinstalled Samsung drivers
Tried different computers and different USB cables
Regardless of what I have tried, I keep getting the same error.
The phone still works - I can boot it, so it is not bricked. I was also able to successfully re-root the phone (using the CF Auto Root approach). Based on my reading, it seems that replacing the PIT file is a next step to try, but it also seems that this is a fast way to killing a phone, so I am hesitant to try.
The phone in question is a Sprint Samsung Galaxy S5, SM-G900P. The kernel is currently Android 5.0, build version LRX21T.G900PVPU2B0D3. I would like to replace with with the stock 4.4.4 kernel (found here: http://stockroms.net/file/GalaxyS5/SM-G900P/G900PVPU1ANCB_G900PSPT1ANCB_SPR.zip). If replacing the PIT file is the next thing to try, can you please point me to the specific one to use? If not, can you suggest something else to try?
Thank you.

Same here
I'm having exactly the same issue. Trying to downgrade from BOD3 to kit kat 4.4.2 NE5 in order to unlock my S5 G900P.
Hope someone has a workaround for this.

Sorry dumb question, what did you use to root a 5.0 firmware? I thought towelroot only works on 4.4.2?

Starting with BOD3 u cant downgrade anymore
Hope this will work 4 u.....it worked on my G900P :
1. Install CWM with odin...Philz: http://downloadandroidrom.com/file/G...2-klte.tar.md5
2. Download Galaxy S5 Rooted Stock ROMs and kernel, flashable zips, and copy to your SD card
3. Reboot in recovery ...wipe data/cache/dalvik....install the zips(kernel and rom)
4.Reboot to system and enjoy ur downgrade
thanks to bto001 here: http://forum.xda-developers.com/sprint-galaxy-s5/general/solution-to-sim-unlock-od3-downgrade-t3128120

What finally worked was to install the same version of the stock firmware.

CM.Bin Fail in Odin Constantly bricking my A510F

So ive been trying to root for a while and nothing seem to work its a snapdraggon CPU when i use cf-auto root i brick my phone when i try to root via TWRP nothing happens when i try to flash an official samsung firmware it fails at CM.BIN im on 6.0.1 and anything i do either bricks it or nothing happens an i stay unrooted with original firmware.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> A510FXXU2APD5_A510FEVR2APD4_A510FXXU2APD4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> cm.bin
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

alexsheff said:
So ive been trying to root for a while and nothing seem to work its a snapdraggon CPU when i use cf-auto root i brick my phone when i try to root via TWRP nothing happens when i try to flash an official samsung firmware it fails at CM.BIN im on 6.0.1 and anything i do either bricks it or nothing happens an i stay unrooted with original firmware.
Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
A510FXXU2APD5_A510FEVR2APD4_A510FXXU2APD4_HOME.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Odin engine v(ID:3.1005)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
SingleDownload.
sboot.bin
NAND Write Start!!
cm.bin
FAIL!
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Simple - wrong firmware for your device.
Twrp, nothing happens? - you need to give details.

ashyx said:
Simple - wrong firmware for your device.
Twrp, nothing happens? - you need to give details.
Click to expand...
Click to collapse
it is 100% the correct firmware i downloaded it on samstock for EE (EVR) stock 6.0.1 and 5.1.1 both wont install via odin and samsung tools pro. ive flashed twrp following your guide and that worked but installing super su just gave me the app and no binary files were installed, cf auto root just boot loops me the only tike im able to install any firmware is through emergency recovery on smart switch

alexsheff said:
it is 100% the correct firmware i downloaded it on samstock for EE (EVR) stock 6.0.1 and 5.1.1 both wont install via odin and samsung tools pro. ive flashed twrp following your guide and that worked but installing super su just gave me the app and no binary files were installed, cf auto root just boot loops me the only tike im able to install any firmware is through emergency recovery on smart switch
Click to expand...
Click to collapse
If part of the firmware doesn't install then it is not the correct firmware for your particular device, simple.
The bootloader does a sanity check via Odin on any firmware attempted to be installed.
If it doesn't meet the requirements it fails to install.
It's pointless arguing the case because it's a fact and I've been down this road with others who have eventually got the correct firmware of which you've almost proved my point by stating that downloading through Smartswitch installs the correct firmware.
Several factors come into play, model, carrier, region and revision.
Any of these mismatch and installation could potentially fail. Simply being the right model no. isn't enough.
You could probably help yourself if you post more details:
Exact firmware your device is currently running, the firmware you are attempting to install and screenshots or post a log of the output from odin and the info provided on the device display itself after failure.

I got the device on contract with EE so i thought it was locked to EE, my partner bought me a S7 (flat) on vodafone so i put the voda sim into my A510F n it seems to be unlocked to voda not quite sure why i always thought they was locked to the network if it was a contract device, could it possibly be a vodafone stock rom or any other network.

alexsheff said:
I got the device on contract with EE so i thought it was locked to EE, my partner bought me a S7 (flat) on vodafone so i put the voda sim into my A510F n it seems to be unlocked to voda not quite sure why i always thought they was locked to the network if it was a contract device, could it possibly be a vodafone stock rom or any other network.
Click to expand...
Click to collapse
Post the details as requested above and we'll get it sorted.

Galaxy S5 Active SM-G870W - CAN - Bell - Unlocked - Failed Root ODIN Mode

Hi!
!Total Newbie Alert!
I have a Galaxy S5 Active, SM-G870W. It was with Bell, but I unlocked and have been using another provider for some time now. I recently needed to install an app that needs root access, and figured I would be able to do the same.
In the distant past I had rooted some ancient android devices, so I read a bunch of pages, and feeling far too confident I pulled the trigger and tried to root my phone using the CF-Auto-Root tool from the firmware dot mobi website.
I entered SM-G870W, selected the only device option, hit Submit, Selected Android 6.0.1 (Build MMB29M.G870WVLU1CPF6), and continued to download a file:
cfar_samsung_sm-g870w_kltevlactive_mmb29m.g870wvlu1cpf6_t0.zip
I Extracted then launched the root.bat batch file, Odin Launched (Ver 3.12), I pick the AP as specified, and I get the following:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> cache.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
The phone stays at "Downloading... Do not turn off target!!"
I pulled the battery and rebooted into download mode again (Vol Down/Home/Power) and retried with the same file, and the same results.
I also tried powering up in recovery (Vol Up/Home/Power), but I get a message
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again
Click to expand...
Click to collapse
At this point I am trying to get my device at least usable, I can restart in download mode no issue, but even after regenerating and redownloading, I am not able to get past this error.
I spent the last 6 or so hours going over posts here and elsewhere, with no luck, I tried Kies (Version 3.2.16084_2) and it says "The connected device is not supported by Kies 3" and the link to view supported devices on Samsungs site does not lead to any information. I also read somewhere that you can't root Android 6 images, but that post was 2014, and I found contradicting information elsewhere.
I would appreciate help on where to go from here, my priority is getting the phone working, rooted or not.
Thanks in advance!