[Q] soft brick need help N900T - Galaxy Note 3 Q&A, Help & Troubleshooting

I realized I posted this on the wrong section I have just re-posted it in the tmobile galaxy note 3 section, I apologize for my mistake, Please delete thread as it is in the wrong section.
Hello, I am new here this is going to be my first post.
I installed CWM from rom manager a while ago on my rooted note 3 N900T it was on kitkat 4.4.2 then I tried rebooting into recovery mode and then it wouldn't go in it would keep restarting, then after I did a battery pull now I get: ( Firmware upgrade encountered an issue. Please select recovery mode in kids & try again)
ODIN MODE
PRODUCT NAME: SM-N900T
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: CUSTOM
KNOX KEANEL LOCK: 0X0
KNOX WARRANTY VOID: 0XL
QUALCOMM SECUREBOOT: ENABLE (CSB) AP SWAREV: S2, T2, A2, A3, P2
WRITE PROTECTION: ENABLE
VDC START
So I tried connecting to kies it wouldn't detecting it would just say "connecting" I tried on my mac osX mavericks and also on VMWare windows 7.
I tried to download the stock firmware and flash it via odin to come back to stock and thought maybe that would fix it but it keeps giving me a error.
I have the usb drivers installed as it detects the device, I am sure I have downloaded the correct firmware for the phone.
this is the firmware I downloaded: N900TUVUCNB4_N900TTMBCNB4_N900TUVUCNB4_HOME.tar.md5
I tried using odin 3.07 and 3.09 both and ran it as administrator.
I checked the "time reset" also the "auto reboot" as mentioned, I tried adding it in pa in 3.09 and pda in 3.07
This is the error I get while trying to flash the rom: <OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900TUVUCNB4_N900TTMBCNB4_N900TUVUCNB4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Unfortunately that is what I get from odin sometimes it goes further down and then stops but most of the times i get this, I've tried using the original 3.0 usb cable with different usb ports and also another normal micro usb cable, both gives me the same error, I have tried to use JODIN as well on my mac but my device doesn't detect on that therefore i used my VMware windows 7 32bit. I tried that while I had kids installed on my computer and then I read that kies doesn't go well with odin so I uninstalled kies and tried again but no difference.
Could someone please help me out, I have been trying to fix this for 2 days I am a college student and I work part time, so it is very frustrating not to have a phone to use for work and college.

malimt said:
Hello, I am new here this is going to be my first post.
I installed CWM from rom manager a while ago on my rooted note 3 N900T it was on kitkat 4.4.2 then I tried rebooting into recovery mode and then it wouldn't go in it would keep restarting, then after I did a battery pull now I get: ( Firmware upgrade encountered an issue. Please select recovery mode in kids & try again)
ODIN MODE
PRODUCT NAME: SM-N900T
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: CUSTOM
KNOX KEANEL LOCK: 0X0
KNOX WARRANTY VOID: 0XL
QUALCOMM SECUREBOOT: ENABLE (CSB) AP SWAREV: S2, T2, A2, A3, P2
WRITE PROTECTION: ENABLE
VDC START
So I tried connecting to kies it wouldn't detecting it would just say "connecting" I tried on my mac osX mavericks and also on VMWare windows 7.
I tried to download the stock firmware and flash it via odin to come back to stock and thought maybe that would fix it but it keeps giving me a error.
I have the usb drivers installed as it detects the device, I am sure I have downloaded the correct firmware for the phone.
this is the firmware I downloaded: N900TUVUCNB4_N900TTMBCNB4_N900TUVUCNB4_HOME.tar.md5
I tried using odin 3.07 and 3.09 both and ran it as administrator.
I checked the "time reset" also the "auto reboot" as mentioned, I tried adding it in pa in 3.09 and pda in 3.07
This is the error I get while trying to flash the rom: <OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900TUVUCNB4_N900TTMBCNB4_N900TUVUCNB4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Unfortunately that is what I get from odin sometimes it goes further down and then stops but most of the times i get this, I've tried using the original 3.0 usb cable with different usb ports and also another normal micro usb cable, both gives me the same error, I have tried to use JODIN as well on my mac but my device doesn't detect on that therefore i used my VMware windows 7 32bit. I tried that while I had kids installed on my computer and then I read that kies doesn't go well with odin so I uninstalled kies and tried again but no difference.
Could someone please help me out, I have been trying to fix this for 2 days I am a college student and I work part time, so it is very frustrating not to have a phone to use for work and college.
Click to expand...
Click to collapse
Known issue in vmware on Mac. Use parallels, bootcamp, or a real windows machine.
Sent from my leanKernel 3.0 powered stock 4.4.2 (NE6) SM-N900T

toastido said:
Known issue in vmware on Mac. Use parallels, bootcamp, or a real windows machine.
Sent from my leanKernel 3.0 powered stock 4.4.2 (NE6) SM-N900T
Click to expand...
Click to collapse
Thanks so much man, You were right, I un-installed VMWare and then installed parallels desktop 9 and then from then I flashed the stock rom using odin 3.07 and boom wallllla I'm back on my 4.4.2 stock rom. thanks thanks thanks

Related

[Q] stock rom flash fail

Hello,
-sorry for my english I dont speak well but...
phone: I9505
I was testing cyanogemod 10.1.3 for a while but then I decided get back to stock rom, did full wipe and put this ROM I9505XXUBMF8 into Odin and start flashing but he said this:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUBMF8_I9505OXABMF8_I9505XXUBMF8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<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> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
-then I couldnt go to system, recovery just to download mode so I flashed TWRP.
(I tried another stock rom, odin, PC but always same problem.)
-then i tried get back CM 10.1.3 via TWRP and it flashed and work without problem.
-then I tried flash omega rom via TWRP and it flashed without problem but booting is very slow and during the logo Samsung it takes about 10mins to boot into system and device is very hot.
-Everything about Kies and antivirus is off.
-Using just original USB cable.
-what says download mode:
ODIN MODE
PRODUCT NAME: gt-i9505
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
KNOX KERNEL LOCK: 0X0
KNOX WARRANTY VOID: 0X1
CSB-CONFIG-LSB: 0X30
WRITE PROTECTION: ENABLED
START [224, 1440]
SW REV, CHECK FAIL : FUSED : 2 , BINARY : 1
Any ideas how to resolve this?
Thank you
you have a secured bootloader, you can not flash old firmwares, flash MH8
use search button, there is a lot of threads talking about this issue
samersh72 said:
you have a secured bootloader, you can not flash old firmwares, flash MH8
use search button, there is a lot of threads talking about this issue
Click to expand...
Click to collapse
Thank you so much, I was looking for something all day but i didnt sure what Im really looking for

[Q] Soft brick on Samsung S4 but cant write stock rom?

Hey guys,
I had succesfully rooted my device. a few weeks ago. because i wanted cyanogenmod rom on it i tried to flash CWM recovery menu.
now my device gives the following message:
firmware upgrade encountered an issue. please select recovery mode in kies and try again.
Now i tried to reflash the stock rom with odin.
i downloaded the stock rom for my area (i guess)
i also downloaded a europe .pit file (someone said that on a tutorial how to remove soft brick)
Tried flashing
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUFNA1_I9505OXAFNA1_I9505XXUFNA1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
I have an dutch galaxy s4. i have the provider T-mobile but the phone is not provider specified.
how can i fix this problem?
after trying with odin my downloading mode show's the following.
Odin mode
product name: GT-I9505
current binary: Custom
system status: Custom
knox kernel lock: 0x0
knox warranty void: 0x1
csb-config-lsb: 0x30
write protection: enable
emmc burst mode: enabled
start (224, 1440)
sw. rev. check fail : fused : 4 , binary : 3
what can i do to get my phone to start up normally, now i keep getting the firmware fault message.
Thanks in advance.
Edit: i cant open recovery mode. but i can open download mode.
VeryStealth said:
Hey guys,
I had succesfully rooted my device. a few weeks ago. because i wanted cyanogenmod rom on it i tried to flash CWM recovery menu.
now my device gives the following message:
firmware upgrade encountered an issue. please select recovery mode in kies and try again.
Now i tried to reflash the stock rom with odin.
i downloaded the stock rom for my area (i guess)
i also downloaded a europe .pit file (someone said that on a tutorial how to remove soft brick)
Tried flashing
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUFNA1_I9505OXAFNA1_I9505XXUFNA1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
I have an dutch galaxy s4. i have the provider T-mobile but the phone is not provider specified.
how can i fix this problem?
after trying with odin my downloading mode show's the following.
Odin mode
product name: GT-I9505
current binary: Custom
system status: Custom
knox kernel lock: 0x0
knox warranty void: 0x1
csb-config-lsb: 0x30
write protection: enable
emmc burst mode: enabled
start (224, 1440)
sw. rev. check fail : fused : 4 , binary : 3
what can i do to get my phone to start up normally, now i keep getting the firmware fault message.
Thanks in advance.
Edit: i cant open recovery mode. but i can open download mode.
Click to expand...
Click to collapse
Try flashing a custom recovery through odin if u succeed u may have access to recovery nd if it doesnt work try flashing firmware without using pit file nd unchecking repartition option
Sent from my GT-I9500 using Tapatalk
---------- Post added at 10:56 PM ---------- Previous post was at 10:55 PM ----------
Which version is this which u r trying to flash via odin 4.3 or 4.4 2
Sent from my GT-I9500 using Tapatalk
aayushkhajuria2842 said:
Try flashing a custom recovery through odin if u succeed u may have access to recovery nd if it doesnt work try flashing firmware without using pit file nd unchecking repartition option
Sent from my GT-I9500 using Tapatalk
---------- Post added at 10:56 PM ---------- Previous post was at 10:55 PM ----------
Which version is this which u r trying to flash via odin 4.3 or 4.4 2
Sent from my GT-I9500 using Tapatalk
Click to expand...
Click to collapse
I thought it were a test version of 4.4.2 kitkat
though i now downloaded a netherlands version from this tread no idea wich version.
http://forum.xda-developers.com/showthread.php?t=2265477
and then the second one. also downloaded the .pit here. im gonna try it now.. youll hear in a few minutes
VeryStealth said:
I thought it were a test version of 4.4.2 kitkat
though i now downloaded a netherlands version from this tread no idea wich version.
http://forum.xda-developers.com/showthread.php?t=2265477
and then the second one. also downloaded the .pit here. im gonna try it now.. youll hear in a few minutes
Click to expand...
Click to collapse
I just want u 2 confirm it is 4.4.2 as u were trying to install cyanogenmod
Sent from my GT-I9500 using Tapatalk
aayushkhajuria2842 said:
I just want u 2 confirm it is 4.4.2 as u were trying to install cyanogenmod
Sent from my GT-I9500 using Tapatalk
Click to expand...
Click to collapse
leaked official version of 4.4.2
Why did i overlook that cyanogenmod recovery isnt compatible with 4.4.2 yet?
VeryStealth said:
leaked official version of 4.4.2
Why did i overlook that cyanogenmod recovery isnt compatible with 4.4.2 yet?
Click to expand...
Click to collapse
U can flash It if it is 4.4.2 ....nd I dont get your last line ???
Sent from my GT-I9500 using Tapatalk
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUEMKF_I9505PHNEMK5_I9505XXUEMKF_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
following happend with the downloaded version of stock rom.
now trying with .pit file
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1
so i guess its not the pitt file?
is anything damaged? or do i have a faulty rom combo?
so your saying basicly that i should just try to reflash cyanogenmod? do you have a link to the version i can use. just to make sure i use the right one and don't screw it up more..
thanks for your help already btw.
I downloaded the newest CM i can find? CM 11-20140327? also i have the newest gapps i can find.. though its 20130813.
but how do i flash the recovery menu?
NVM i gave you a lot of false information< i had the firmware fault while installing clockworkmod recovery menu< not cyanogen< both with C im sorry.. i needed a recovery menu to install cyanogen. thats why i had problems.. i tried flashing to get the recovery menu and that failed. that gave the issues.. not cyanogen
Need to go puppy training with my dog< back in an hour or so
VeryStealth said:
so your saying basicly that i should just try to reflash cyanogenmod? do you have a link to the version i can use. just to make sure i use the right one and don't screw it up more..
thanks for your help already btw.
I downloaded the newest CM i can find? CM 11-20140327? also i have the newest gapps i can find.. though its 20130813.
but how do i flash the recovery menu?
NVM i gave you a lot of false information< i had the firmware fault while installing clockworkmod recovery menu< not cyanogen< both with C im sorry.. i needed a recovery menu to install cyanogen. thats why i had problems.. i tried flashing to get the recovery menu and that failed. that gave the issues.. not cyanogen
Need to go puppy training with my dog< back in an hour or so
Click to expand...
Click to collapse
Problem solved.. downloaded a new stock rom.. and used a 2.0 usb. I only have 3.0 stock an i could flash without problems on 3.0.. 2.0 were a first time hit.
Thanks again
VeryStealth said:
Problem solved.. downloaded a new stock rom.. and used a 2.0 usb. I only have 3.0 stock an i could flash without problems on 3.0.. 2.0 were a first time hit.
Thanks again
Click to expand...
Click to collapse
Glad u sovlved ur prblm bt from nxt tym read before flashing any custom rom u may hav flashed some wrong one
Sent from my GT-I9500 using Tapatalk

[Help] My Phone won't boot (Samsung Galaxy S4)

Hi guys, i been searching for long time to resolve my issue and nothing found i think you guys could help me.
The issue is
My phone was rooted - Samsung Galaxy S4 - GT-I9505
And then i unrooted, but nothing to do with this, it was all oK..
After that i tried to upgrade the firmware from sammobile something like that..
I downloaded the new firmware I9505XXUGNG8_I9505MAXGNG1_I9505XXUGNG8_HOME.tar for my phone
And in the end of the line using Odin i got FAILED red box.. And since that i can't boot my phone stuck at Odin Mode: Firmware upgrade encountered an issue. Please select recovery mode in Kies & Try again. And up with small text says: Odin Mode, PRODUCT NAME: GT-19505, CURRENT BINARY: costum, SYSTEM STATUS: costum, KNOX KERNEL LOCK: 0x0, KNOX WARRANTY VOID: 0x1, CS0-CONFIG-LS8: 0x30, WRITE PROTECTION: enable, eMMc BURST MODE: enable
i tried with Kies but i can't connect , because i think after i unrooted, i reset my phone so USB debugging is not checked. I think for that. So i'm trying to install new firmwares with Odin and is not working i always get fail message red box, i tried all versions.
Does anyone know what to do please.
i Appreciate it.
Thanks.
GoodMan14 said:
Hi guys, i been searching for long time to resolve my issue and nothing found i think you guys could help me.
The issue is
My phone was rooted - Samsung Galaxy S4 - GT-I9505
And then i unrooted, but nothing to do with this, it was all oK..
After that i tried to upgrade the firmware from sammobile something like that..
I downloaded the new firmware I9505XXUGNG8_I9505MAXGNG1_I9505XXUGNG8_HOME.tar for my phone
And in the end of the line using Odin i got FAILED red box.. And since that i can't boot my phone stuck at Odin Mode: Firmware upgrade encountered an issue. Please select recovery mode in Kies & Try again. And up with small text says: Odin Mode, PRODUCT NAME: GT-19505, CURRENT BINARY: costum, SYSTEM STATUS: costum, KNOX KERNEL LOCK: 0x0, KNOX WARRANTY VOID: 0x1, CS0-CONFIG-LS8: 0x30, WRITE PROTECTION: enable, eMMc BURST MODE: enable
i tried with Kies but i can't connect , because i think after i unrooted, i reset my phone so USB debugging is not checked. I think for that. So i'm trying to install new firmwares with Odin and is not working i always get fail message red box, i tried all versions.
Does anyone know what to do please.
i Appreciate it.
Thanks.
Click to expand...
Click to collapse
Hi mate ,
You have to flash an stock rom with odin , there is no other solution
Check this thread , i will give you in detail how to proceed
http://forum.xda-developers.com/showthread.php?t=2265477
MAX 404 said:
Hi mate ,
You have to flash an stock rom with odin , there is no other solution
Check this thread , i will give you in detail how to proceed
http://forum.xda-developers.com/showthread.php?t=2265477
Click to expand...
Click to collapse
That's what he's doing. It should be working.
It MIGHT be because you have non official firmware on it now and it's not accepting the flash back to stock. IF that's the case the solution is to uncheck auto reboot in Odin and run the install sequence twice in a row. That's worth a shot here, but I don't think it's the solution.
Do you still have a working custom recovery? If so you should still be able to flash a custom ROM. I might try flashing a custom TouchWiz rom then starting over.
Still fail !
ty for reply guys, ok i captured everything
this is image when i browse the file on AP / PDA odin freezed for few seconds...
And this is what i got:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUGNG8_I9505MBMGNG1_I9505XXUGNG8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
GoodMan14 said:
ty for reply guys, ok i captured everything
this is image when i browse the file on AP / PDA odin freezed for few seconds...
And this is what i got:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUGNG8_I9505MBMGNG1_I9505XXUGNG8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
Click to expand...
Click to collapse
Hi ,
This is from the post i gave you earlier
Odin troubleshooting: If Odin accidentally gives you "fail" try the following:
- Repeat procedure.
- Make sure that all actions of Kies are disabled from task manager.
- Change usb port.
- Try another usb cable (make sure it is the original).
- Try another Odin version.
- Uninstall and re-install driver.
- Use pit file.
- Try another computer.
Check and see if it helps , did you try what Skipjacks said?
i di all
Hi, in this morning i tried again and passed.. finally
Thanks for helping.
GoodMan14 said:
Hi, in this morning i tried again and passed.. finally
Thanks for helping.
Click to expand...
Click to collapse
Great news mate
Sent from my Nexus 7 using XDA Premium 4 mobile app
Try flash stock firmware using odin

[Q] Going back to stock from CM12

I have a Sprint Galaxy S4 (SPH-L720), non-spark edition.
It is currently running the Euroskank CM12 Feb 22 nightly.
Everything is working well, except I no longer have any voice/text service. Data (4G LTE), however, works.
Sprint has told me to update my profile/PRL, however, I don't think those options exist in CM12? So I've decided to go back to stock.
I downloaded the L720VPUFNAE_L720SPTFNAE_L720VPUFNAE_HOME.tar.md5 file and am using Odin v3.09
It gets very far (>90%) in the install process before it fails:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUFNAE_L720SPTFNAE_L720VPUFNAE_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl1.mbn
<ID:0/005> sbl2.mbn
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Do I need a PIT file? Do I extract that from the L720VPUFNAE_L720SPTFNAE_L720VPUFNAE_HOME.tar file?
The Odin screen now shows:
ODIN MODE
PRODUCT NAME: SPH-L720
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE enabled
Click to expand...
Click to collapse
I also just finished downloading the L720VPUFNG2_L720SPTFNG2_SPR file, it similarly, also errors out.
When I reboot the phone, it says it's in Emergency Recovery Mode and to connect it to Kies, but Kies doesn't recognize the phone.
Any help is greatly appreciated!
I (half) figured it out.
Tried using a different computer (both Windows 7 machines) to flash back to stock (L720VPUFNAE_L720SPTFNAE_SPR using Odin 3 v3.09) and it went through!
Hit a boot loop, so I factory reset, updated the profile/PRL/activated the device, and everything worked for about 10 minutes.
Then Sprint told me of an OTA update, I installed it, and now I have no service (voice, text or data). There are service bars shown in the system tray, but attempting to even dial out gives me a "Mobile network not available" error.
With no service, I'm unable to update profile/PRL/activate. Unsure how to proceed from here other than maybe trying to flash a different ROM completely then going from there to stock?
I called Sprint and all the lady tried to do was sell me an insurance plan so that I could take it into the store and their technicians could look at it.
@MrCodedude, Try flashing KT's TW kernel or Negamann's r50
JhoonB51 said:
@MrCodedude, Try flashing KT's TW kernel or Negamann's r50
Click to expand...
Click to collapse
It was recommended elsewhere to put the phone in airplane mode, reset, then take it out of airplane mode. That didn't work, but reseating the SIM card did.
I haven't used this Galaxy S4 in awhile, I wonder if there's a problem with the SIM (or maybe the enclosure). I'll probably hold off on flashing a non-stock kernel to see if it still acts up.
I'll also be sad if this is the reason why voice/text didn't work in CM12.

[Q] Need help recovering a bricked SM-900W8

This morning I updated my Note 3 (SM-900W8 on the Canadian Rogers network) to 5.0.
I had rooted this device before then, and had used Titanium Backup to backup all my apps/data. When the initial OTA update failed, someone pointed out that it was because the phone was rooted. So, figuring I had this backup in hand, I factory-reset my phone and went through the update - though I used the Samsung KIES app as it was quicker to download the firmware update than over my phone's WiFi.
Once the phone was on 5.0, I went to restore the backup... and found that Titanium Backup only works when the phone is rooted. Oops.
So, I figure that I need to root my phone again. I find instructions on how to root a note 3 and start to work through it. I go to the link for "Download appropriate CWM or TWRP recovery for your Note 3" and find the one that says "KitKat/Lollipop Android 4.4.2 CWM Recovery" and pick the one "SM-N900W8 Canadian Note 3 – CWM Recovery", because 5.0 is 'Lollipop' and my phone is the SM-N900W8. I attempt to use this with Odin, and Odin reports 'FAIL!' and the phone is stuck on "Downloading - Do not turn off target !!'. I give this a while just in case things take a while to happen... and nothing does, so I figure it did fail. I have no alternative but to turn off the phone now.
And restarting it, the phone comes up in "ODIN MODE" with the message "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
The messages at the top of my phone on this screen are:
Code:
ODIN MODE
PRODUCT NAME: SM-900W8
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
REACTIVATION LOCK: OFF
KNOX WARRANTY VOID: 0x1 (4)
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S2, T2, R2, A3, P2
SECURE DOWNLOAD : ENABLE
UDC START
I connect the phone up again, select the Recovery tool in Kies... and the phone is not detected. No matter what I try.
So then I try and download the official firmware N900W8_RWC_N900W8VLU2DOC4_N900W8OYADOC4 from Samsung Updates and try to use Odin to recovery it that way.
Again, the update fails... time and time again.
The Odin messages output is:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900W8VLU2DOC4_N900W8OYADOC4_N900W8VLU2DOC4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I now have a bricked phone, and no idea how to fix it.
What can I do?
frysco said:
What can I do?
Click to expand...
Click to collapse
1. Reflash STOCK firmware 5.0 for your device: HERE. Factory reset your device when finish of boot.
2. Use TWRP (You can flash this ONE via ODIN) and root your device then.
3. Don't restore your data of android 4.4.2.
I've managed to fix things.
From other searching around, it seems that trying to use Odin via VMWare Fusion on a Mac is a 'known issue' where it gets stuck at this point.
Installed a trial version of Parallels and a basic Win XP install, re-flashed and it WORKED!

Categories

Resources