Database Users

[Q] Galaxy Y Bricked

Hi,
I am completely new in phone flashing. I met some troubles with my Galaxy Y device.
I will explain the details and hope someone can give me guidelines to fix it.
I have a Galaxy Y that freezes at logo screen when powered up.
We can access Download mode, but not Recovery one.
Initially it had an official rom that has not been modified.
I get trouble with it with a boot loop.
So, I went to Recovery Mode and did a wipe Data. This worked once and then I get boot loop problem 2 days later.
I tried again to wipe data through Recovery mode, but now with out result.
So I decided to flash it … Odin failed and now it stays frozen at the logo screen when powered up.
For the flashing:
- I try on 3 different PC (1 Win7 and 2 XP) and tried different USB ports
- For the drivers, I tried by installing Kies_2.3.3.12085_7_5 and by installing USB drivers only (SAMSUNG_USB_Driver_for_Mobile_Phones.exe)
- I tried a lot of time, with and without restarting Odin
- I tried with Odin 1.83, 1.84 and 1.85 ( I know that 1.84 and 1.85 support S5360 model)
- And I tried using different ROMs
The communication between Odin and the device seems correct (I can see the yellow highlight when connecting the device in Download mode)
I tried some Doky’s packages from here http://forum.xda-developers.com/showthread.php?p=21846620:
- S5360_XXKK6_OXXKK2_XXKK5
- S5360_XXKL3_OXXKL1_XXKL3
- S5360_XXLF3_OXXLF3_XXLF3
I tried also some other packages containing only one file and one dll (retrieved from here as example http://www.tsar3000.com/Joomla/inde...laxy-y-firmwares&catid=55:samsung&Itemid=82):
- S5360XXKL3_LUXKJ1_Luxembourg_Android_2.3.6
- S5360TAJKK3_TLPKK3_Austria_Android_2.3.6
- S5360LUHKJ2_PSNKJ2_Argentina_Personal_Android_2.3.6
- S5360XXLA2_S5360OXXLA2_EUR
- S5360XXKL3_S5360OXXKL1_EUR
I tried also this package, as I saw that some people were able to unbrick there device with it:
GalaxyS5360_DDLA1_2.3.6
This last package contains totoro_0623.pit file. So I tried with and without Re-Partition checked.
I tried also to download totoro_0623.pit file again from other locations and the .pit file with other packages from the previous lists, but without success (Odin always fails).
On point that can be perhaps important is then when flashing, with Odin, the CSC package alone it always succeeds.
The same, when flashing only BOOT package (taken from GalaxyS5360_DDLA1_2.3.6), is it always successful.
I tried also to flash different couples of BOOT and CSC packages and it is always successful.
Unfortunately, I am completely new in this domain and I do not know the purpose of each package (BOOT, PDA, MODEM and CSC).
So, I do not know what to do now ... Perhaps someone can have some advices or guidelines to help.
Thanks again.
Yacy.

refer to youtube watch with video TUT

yabyuh22 said:
refer to youtube watch with video TUT
Click to expand...
Click to collapse
Thank you very much, Tabyuh22, for your advice.
Unfortunately, I did a lot of search already (xda forum and google), but unfortunately without success.
The only unbrick tutorial I found, related to Galaxy Y, is flashing GalaxyS5360_DDLA1_2.3.6 packages with Odin. I tried this already, but unfortunately, it was not successful (Odin flash fails, except if I flash, BOOT and CSC packages only, as explained previously).
Perhaps you have in mind a specific link that I can try?
Thanks again.
Yacy.

Most probably, the Odin you downloaded is a corrupt one, or maybe you're using an older version. Try the one from Doky73's thread.

sorry but i believe its the Odin,
try the v1.85 and do not use a pit file,
very well detailed question,
thanks

can you post screenshot for odin after "Fail" and/or all text in Message area
and I will help I've unbricked my phone just today

Thank you very much for your advice and help.
In fact, I tried already to download Odin 1.85 from different sources. I just tried again, but unfortunately I get the same bad result.
What I find strange is that the flash is successful when using the CSC package only.
I do not know how to put images in the post, so I attached 2 .jpg snapshots of Odin failure and success.
Here is Odin's log when failure (when trying to flash PDA, MODEM and CSC packages):
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_S5360_XXLF3.tar.md5 is valid.
<OSM> MODEM_S5360_XXLF3.tar.md5 is valid.
<OSM> CSC_S5360_OXXLF3.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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
And here is Odin's log when success (when trying to flash CSC package only):
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_S5360_XXLF3.tar.md5 is valid.
<OSM> MODEM_S5360_XXLF3.tar.md5 is valid.
<OSM> CSC_S5360_OXXLF3.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> csc.rfs
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
Click to expand...
Click to collapse
Thanks again for your help.
Yacy

Just choose PDA and It's required file and live Phone and CSC alone then you'l be able to boot into Recovery mod

Mohamed.Anwar said:
Just choose PDA and It's required file and live Phone and CSC alone then you'l be able to boot into Recovery mod
Click to expand...
Click to collapse
It seems it is what I did. The result is in the Failed snapshot I attached.
Do you see any thing wrong in this snapshot and the associated logs?
(I tried also to flash PDA or PHONE alone, but failed. It is successful only if I flash CSC alone)
Thanks again.
Yacy.

Try data/cache wipe after flash,maybe it helps
MANY GREEEEETZ!!!

Alright, now when you downloaded the firmware package, there would be 4 different .tar files - BOOT_something.tar, PDA_something.tar, CSC_something.tar and MODEM_something.tar. Sometimes, there is one more, DefaultCalDataBOOT_something.tar, which i use in place of BOOT. Try flashing that in place of BOOT file. Still if it dosen't work, flash the PIT file along. Make sure the PIT's right. Our device's pit is "totoro_0623.pit".

CALIBAN666 said:
Try data/cache wipe after flash,maybe it helps
Click to expand...
Click to collapse
I imagine we can do this only by accessing Recovery Mode.
Unfortunately, I cannot access this mode, but the Download one only

anasdcool71 said:
Alright, now when you downloaded the firmware package, there would be 4 different .tar files - BOOT_something.tar, PDA_something.tar, CSC_something.tar and MODEM_something.tar. Sometimes, there is one more, DefaultCalDataBOOT_something.tar, which i use in place of BOOT. Try flashing that in place of BOOT file. Still if it dosen't work, flash the PIT file along. Make sure the PIT's right. Our device's pit is "totoro_0623.pit".
Click to expand...
Click to collapse
The only package I get containing BOOT file is GalaxyS5360_DDLA1_2.3.6. This package contains:
- BOOT_S5360DDLA1_REV05.tar.md5
- DefaultCalDataWithBoot_S5360DDLA1_REV05.tar.md5
-PDA_S5360DDLA1_REV05.tar.md5
-MODEM_S5360DDLA1_REV05.tar.md5
-GT-S5360-MULTI-CSC-ODDLA1.tar.md5
Flashing BOOT_S5360DDLA1_REV05.tar.md5 alone is successful and here is Odin’s log:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOT_S5360DDLA1_REV05.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> BcmBoot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
Click to expand...
Click to collapse
Flashing DefaultCalDataWithBoot_S5360DDLA1_REV05.tar.md5 alone fails and here is Odin’s log:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> DefaultCalDataWithBoot_S5360DDLA1_REV05.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> BcmBoot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> HEDGE_NVRAM8_RF_LE.bin
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Selecting totoro_0623.pit alone fails and here is Odin’s log:
<ID:0/004> Added!!
<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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
The remark when flashing DefaultCalDataWithBoot_S5360DDLA1_REV05.tar.md5 alone, I can see on the device the progress bar increasing, but it fails before the end.
(I do not have this at all when trying to flash PDA or MODEM files)
Thanks again.
Yacy.

Possible solution : That what I did
Keep ODIN alive don't close it then try changing USB ports and use man ports ( in the back if you're using Desktop PC ) and flash only pit and PDA if it didn't worked restart download mode
then check if you could boot into Recovery mod

Flash some kernel.tar in place of PDA file....
Then you'll be able to boot into recovery and then install any rom ....!!!!

Sorry for the late answer, as I was not available these days.
And thank you for your guide lines.
Mohamed.Anwar said:
Possible solution : That what I did
Keep ODIN alive don't close it then try changing USB ports and use man ports ( in the back if you're using Desktop PC ) and flash only pit and PDA if it didn't worked restart download mode
then check if you could boot into Recovery mod
Click to expand...
Click to collapse
I tried this operation again many times, but I always get flash failure
The_animaToR said:
Flash some kernel.tar in place of PDA file....
Then you'll be able to boot into recovery and then install any rom ....!!!!
Click to expand...
Click to collapse
I had a look to the Development area and tried to flash different kernels.
Unfortunately, I get failures again.
What is different now is that
1/ Odin hangs at the steps below:
<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> boot.img
<ID:0/003> NAND Write Start!!
Click to expand...
Click to collapse
2/ In the phone, “custom bin down” counter is now uncremented.
Its value is 10 (it was zero, before trying to flash kernels from custom roms).
Do you have any other idea?
Does an alternative tool to flash the device exist?
Is there a way (perhaps by using Android design tools) to get more information about why the flash does not work (a more precise error message)?
Thanks again for your help.
Yacy.

Hi try this one ,hope it helps

denniz05 said:
Hi try this one ,hope it helps
Click to expand...
Click to collapse
Hello Yacy, I'm sorry I have no Idea about your problem. I just wanted to ask if you got your issue solved?
Actually, I bought my SGY about 3 weeks ago and I was going through problems of Flashing. I'm also interested in Flashing with a Custom ROM.
And I'm Totally new to Android. If you got the problem sorted out, can you tell me a DETAILED and CLEAR TUT for flashing one?

asd
please give me a link about galaxy y duos bricked please.

yacy said:
Hi,
I am completely new in phone flashing. I met some troubles with my Galaxy Y device.
I will explain the details and hope someone can give me guidelines to fix it.
I have a Galaxy Y that freezes at logo screen when powered up.
We can access Download mode, but not Recovery one.
Initially it had an official rom that has not been modified.
I get trouble with it with a boot loop.
So, I went to Recovery Mode and did a wipe Data. This worked once and then I get boot loop problem 2 days later.
I tried again to wipe data through Recovery mode, but now with out result.
So I decided to flash it … Odin failed and now it stays frozen at the logo screen when powered up.
For the flashing:
- I try on 3 different PC (1 Win7 and 2 XP) and tried different USB ports
- For the drivers, I tried by installing Kies_2.3.3.12085_7_5 and by installing USB drivers only (SAMSUNG_USB_Driver_for_Mobile_Phones.exe)
- I tried a lot of time, with and without restarting Odin
- I tried with Odin 1.83, 1.84 and 1.85 ( I know that 1.84 and 1.85 support S5360 model)
- And I tried using different ROMs
The communication between Odin and the device seems correct (I can see the yellow highlight when connecting the device in Download mode)
I tried some Doky’s packages from here http://forum.xda-developers.com/showthread.php?p=21846620:
- S5360_XXKK6_OXXKK2_XXKK5
- S5360_XXKL3_OXXKL1_XXKL3
- S5360_XXLF3_OXXLF3_XXLF3
I tried also some other packages containing only one file and one dll (retrieved from here as example http://www.tsar3000.com/Joomla/inde...laxy-y-firmwares&catid=55:samsung&Itemid=82):
- S5360XXKL3_LUXKJ1_Luxembourg_Android_2.3.6
- S5360TAJKK3_TLPKK3_Austria_Android_2.3.6
- S5360LUHKJ2_PSNKJ2_Argentina_Personal_Android_2.3.6
- S5360XXLA2_S5360OXXLA2_EUR
- S5360XXKL3_S5360OXXKL1_EUR
I tried also this package, as I saw that some people were able to unbrick there device with it:
GalaxyS5360_DDLA1_2.3.6
This last package contains totoro_0623.pit file. So I tried with and without Re-Partition checked.
I tried also to download totoro_0623.pit file again from other locations and the .pit file with other packages from the previous lists, but without success (Odin always fails).
On point that can be perhaps important is then when flashing, with Odin, the CSC package alone it always succeeds.
The same, when flashing only BOOT package (taken from GalaxyS5360_DDLA1_2.3.6), is it always successful.
I tried also to flash different couples of BOOT and CSC packages and it is always successful.
Unfortunately, I am completely new in this domain and I do not know the purpose of each package (BOOT, PDA, MODEM and CSC).
So, I do not know what to do now ... Perhaps someone can have some advices or guidelines to help.
Thanks again.
Yacy.
Click to expand...
Click to collapse
hey just see http://forum.xda-developers.com/showthread.php?t=1465800

SGS4 won't boot....

Hi guys,
My SGS4 won't boot anymore. At all.
I can (with difficulty) access my custom recovery menu (TWRP 2.5.1) and the download menu.
But whatever I'm trying to flash using ODIN from download menu, it fails! Whether it's the current ROM, official UK BTU ROM, stock recovery etc... So can't use Odin.
Can't put anything on the device either as I can't boot. When I use the "mount USB" from the TWRP menu, my PC doesn't recognize the phone so I can't put any ZIP on the phone that I could install from TWRP.
This happened when I used Triangle Away to reset the counter from 1 to 0....
I'm afraid my phone is bricked (although it's a temp phone and will be getting mine in 2 days), but I wanted to be sure that I didn't forget to do anything....
ANy ideas how to make this work pls?
thnx

vivelafrance said:
Hi guys,
My SGS4 won't boot anymore. At all.
I can (with difficulty) access my custom recovery menu (TWRP 2.5.1) and the download menu.
But whatever I'm trying to flash using ODIN from download menu, it fails! Whether it's the current ROM, official UK BTU ROM, stock recovery etc... So can't use Odin.
Can't put anything on the device either as I can't boot. When I use the "mount USB" from the TWRP menu, my PC doesn't recognize the phone so I can't put any ZIP on the phone that I could install from TWRP.
This happened when I used Triangle Away to reset the counter from 1 to 0....
I'm afraid my phone is bricked (although it's a temp phone and will be getting mine in 2 days), but I wanted to be sure that I didn't forget to do anything....
ANy ideas how to make this work pls?
thnx
Click to expand...
Click to collapse
where odin failed exactly?
did you try changing usb port? kies totally disabled? original usb cable?

thnx for your help.
- Kies is definitely not running, stopped all services and processes
- Using samsung USB cable
- Tried on several USB ports of my PC
- Using Odin 3.4
- this is what I can read in ODIN after it has failed:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUAMDD_I9505VODAMD9_I9505XXUAMDD_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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
Thnx again.

vivelafrance said:
thnx for your help.
- Kies is definitely not running, stopped all services and processes
- Using samsung USB cable
- Tried on several USB ports of my PC
- Using Odin 3.4
- this is what I can read in ODIN after it has failed:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUAMDD_I9505VODAMD9_I9505XXUAMDD_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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
Thnx again.
Click to expand...
Click to collapse
one more thing, remove battery for a couple of minutes, then try with odin 1.85

All of these were really good ideas, but I'm afraid none of them work!
Same error message, it seems it can't write on the damn phone. I tried to reflash TWRP, the green bar went further but at the end, same thing, fails.

vivelafrance said:
All of these were really good ideas, but I'm afraid none of them work!
Same error message, it seems it can't write on the damn phone. I tried to reflash TWRP, the green bar went further but at the end, same thing, fails.
Click to expand...
Click to collapse
i dont know if flashing pit file along with the firmware will work

yeah that's exactly what I was thinking, after clickingon your "unroot, back to stock" link in your signature...
So can I flash the firmware + Pit at the same time or should I flash pit first and then the ROM?

vivelafrance said:
yeah that's exactly what I was thinking, after clickingon your "unroot, back to stock" link in your signature...
So can I flash the firmware + Pit at the same time or should I flash pit first and then the ROM?
Click to expand...
Click to collapse
pit file is flashed with the firmware. choose the right pit for your device! re-partition will be checked automatically when you select the pit file.

still doesn't work unfortunately, don't know what 's happening....
I flashed PIT file alone, it worked fine.
Tried to install anything else, it fails again, all the time...

vivelafrance said:
still doesn't work unfortunately, don't know what 's happening....
I flashed PIT file alone, it worked fine.
Tried to install anything else, it fails again, all the time...
Click to expand...
Click to collapse
did you flash firmware with the pit file at same time and didnt work?
almost you did everything.
try to change computer if available.

no I flashed the pit file alone, cause if I flash the pit and PDA at the same time, it doesn't work either:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUAME2-PRE-ROOTED-DEODEX-SUPER-SLIM.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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
ok well, thnx anyway for your help

vivelafrance said:
no I flashed the pit file alone, cause if I flash the pit and PDA at the same time, it doesn't work either:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUAME2-PRE-ROOTED-DEODEX-SUPER-SLIM.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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
ok well, thnx anyway for your help
Click to expand...
Click to collapse
If you haw acess t dawnload mod you are nhot bricked pleas go and try other pc
Sent from my GT-I9505 using xda premium

First, thanks for the info that if I can access the download mode, then the phone is not bricked, I didn't know that, so thanks.
And yes, you were both right, I plugged my phone into my laptop and it worked! THANK YOU.
So the next question is: What could be the issue on my PC? It's not Kies cause it's not installed, and I already uninstalled and reinstalled the Samsung Drivers....
thnx

this is surely NOT a mobile issue if you can enter into download mode.
i had the exact issue a month ago when i had note2.
if you can't try it on another pc, try :
1) uninstall skies completely
2) unisnstall usb drivers
3) reboot the pc
4) connect your s4 in download mode to your pc.
5) let your pc install freah usb drivers
6) start odin and flash
7) if still you get the same error download a different verison of the official rom and try flashing.
i followed the above procedure couple of times and was finally able to install the rom. the issue is either with the drivers or the rom.
Sent from my GT-I9500 using xda app-developers app

bricked for sure
vivelafrance said:
First, thanks for the info that if I can access the download mode, then the phone is not bricked, I didn't know that, so thanks.
And yes, you were both right, I plugged my phone into my laptop and it worked! THANK YOU.
So the next question is: What could be the issue on my PC? It's not Kies cause it's not installed, and I already uninstalled and reinstalled the Samsung Drivers....
thnx
Click to expand...
Click to collapse
expirienced exactly same situation with i9300. Able to get to recovery but failed to flash. Tryed everything on PC and on the phone itself. You have to try different odin versions, but in my case it was NAND failure. If you failed to flash PIT your phone is for sure bricked. Sorry.
Got mainboard replacement in my case.

Have you tried putting a rom on the sdcard with an adapter.. And then put it in the phone and flash the zip from recovery?
Sent from my GT-I9505 using xda app-developers app

Bluetoth10 said:
expirienced exactly same situation with i9300. Able to get to recovery but failed to flash. Tryed everything on PC and on the phone itself. You have to try different odin versions, but in my case it was NAND failure. If you failed to flash PIT your phone is for sure bricked. Sorry.
Got mainboard replacement in my case.
Click to expand...
Click to collapse
thnx. yeah, flashing the PIT actually always worked but it was the only thing that worked! lol

DenmarkRootN00b said:
Have you tried putting a rom on the sdcard with an adapter.. And then put it in the phone and flash the zip from recovery?
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
no but good idea. Actually all the flashing work now, but I still can't boot into the phone! This is madness...
before I couldn't flash anything. Now, I flashed the original BTU ROM, Stock recovery but can't boot into recovery anymore, can't boot into the OS, the only thing that works is the download mode.
Will try to get the phone to a repair thing. I'm gonna try with samsung repair centre first cause the right ROM is installed (original) and the counter is at zero so should be fine with warranty.

vivelafrance said:
no but good idea. Actually all the flashing work now, but I still can't boot into the phone! This is madness...
before I couldn't flash anything. Now, I flashed the original BTU ROM, Stock recovery but can't boot into recovery anymore, can't boot into the OS, the only thing that works is the download mode.
Will try to get the phone to a repair thing. I'm gonna try with samsung repair centre first cause the right ROM is installed (original) and the counter is at zero so should be fine with warranty.
Click to expand...
Click to collapse
good luck at least i just thought it would work by doing it in recovery but yeah... warranty is better.. if not.. then keep trying if they wont replace it

ok I FINALLY could access the stock recovery, did a full wipe and everything is back in order now, works perfectly.
THANKS to all!

[Q] How to root after the latest update ?

Hi all,
I've just updated my Note3 SM-N9005 via kies to Build number N9005XXUDMK2 and now I can't flash root, It fails every time...
My version is N9005XXUDMJ7 and my build number is N9005XXUDMK2.
I don't know if it has something to do with it, but when I enter download node I see a gray line saying: "Write protection: Enabled".
Can anyone please tell me how can I gain root access again ?
I'm tring to flash this file: "CF-Auto-Root-hlte-hltexx-smn9005.tar.md5" with "Odin3 v3.09.exe"
which I found in this site: http://true-android.blogspot.co.il/2013/12/root-n9005xxudmk2-galaxy-note-3-sm.html

frliran said:
Hi all,
I've just updated my Note3 SM-N9005 via kies to Build number N9005XXUDMK2 and now I can't flash root, It fails every time...
My version is N9005XXUDMJ7 and my build number is N9005XXUDMK2.
I don't know if it has something to do with it, but when I enter download node I see a gray line saying: "Write protection: Enabled".
Can anyone please tell me how can I gain root access again ?
I'm tring to flash this file: "CF-Auto-Root-hlte-hltexx-smn9005.tar.md5" with "Odin3 v3.09.exe"
which I found in this site: http://true-android.blogspot.co.il/2013/12/root-n9005xxudmk2-galaxy-note-3-sm.html
Click to expand...
Click to collapse
Can you paste the Odin log after it fails?
Also you may have the new updated CF Root which has been adapted for KitKat and doesn't work with 4.3 anymore.

Here is the log from odin
radicalisto said:
Can you paste the Odin log after it fails?
Also you may have the new updated CF Root which has been adapted for KitKat and doesn't work with 4.3 anymore.
Click to expand...
Click to collapse
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-hlte-hltexx-smn9005.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I even tries using the same root file I did the first time I rooted my phone...

frliran said:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-hlte-hltexx-smn9005.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I even tries using the same root file I did the first time I rooted my phone...
Click to expand...
Click to collapse
Gave the same error using the original file you used from the first time? -- It is possible it doesn't like MK2, however it should work because I used it fine when I was on it.. Try re-downloading it again and trying again (I don't have it anymore, only the KK version )

Here is the log of the first file
radicalisto said:
Gave the same error using the original file you used from the first time? -- It is possible it doesn't like MK2, however it should work because I used it fine when I was on it.. Try re-downloading it again and trying again (I don't have it anymore, only the KK version )
Click to expand...
Click to collapse
The previous log was from the new file I downloaded today.
This is the log from "Odin3 v3.07" using the first file I rooted my phone with:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-hlte-hltexx-smn9005.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
PLEASE...Can you please help me to re-root my phone.
(And if you can, please send me a link to download root for the KitKat version so that I can re-root it when the update will rollout in my country.)

Just to double check -- you are flashing it via the PDA option correct? and you have unrar'd it so you can see the tar.md5 file ?

yes
radicalisto said:
Just to double check -- you are flashing it via the PDA option correct? and you have unrar'd it so you can see the tar.md5 file ?
Click to expand...
Click to collapse
Yes I am.
But in odin 3.9 there is AP and not PDA.
But I tried both in both odin versions: 3.7 and 3.9.
In odin 3.7 I am using PDA, and in odin 3.9 I am using AP.

Hmm I am stumped I'm afraid. Usually re-flashing it normally works. See if anyone else will chime in and know the answer.

)-;
radicalisto said:
Hmm I am stumped I'm afraid. Usually re-flashing it normally works. See if anyone else will chime in and know the answer.
Click to expand...
Click to collapse
Do you think doing "Wipe cache partition" can fix it ? I don't realy knkow what it means...
Can you please send me a download link for rooting after updating to KitKat ? So I could use it when the update rolls out in my country

frliran said:
Do you think doing "Wipe cache partition" can fix it ? I don't realy knkow what it means...
Can you please send me a download link for rooting after updating to KitKat ? So I could use it when the update rolls out in my country
Click to expand...
Click to collapse
When it rolls out it may be a different version of KK than is currently compatible with CR Root. Better waiting til it comes out then seeing what is available.
**[Side Note... If you want KK now you can flash the Official XEO version depending on your Model (IF Hong Kong then it won't work) - and you can root on that without issue after flashing, but you cannot go bac to 4.3 again]**

hmmm
radicalisto said:
When it rolls out it may be a different version of KK than is currently compatible with CR Root. Better waiting til it comes out then seeing what is available.
**[Side Note... If you want KK now you can flash the Official XEO version depending on your Model (IF Hong Kong then it won't work) - and you can root on that without issue after flashing, but you cannot go bac to 4.3 again]**
Click to expand...
Click to collapse
I prefer to wait till an official KK will roll out and update via kies.
Can you please tell me if I do "Wipe cache partition" will fix the root failure probloem ?
I don't realy know what this wipe does...

Solved it (-:
frliran said:
I prefer to wait till an official KK will roll out and update via kies.
Can you please tell me if I do "Wipe cache partition" will fix the root failure probloem ?
I don't realy know what this wipe does...
Click to expand...
Click to collapse
On the settings page under security..make sure you have reactivation lock uncheck...
Than try again..that's usually the problem

It's always something so simple, Not turned activation lock on myself so never had an issue with it. Glad you got sorted thouugh.

Thank you very much for your help
radicalisto said:
It's always something so simple, Not turned activation lock on myself so never had an issue with it. Glad you got sorted thouugh.
Click to expand...
Click to collapse
Yes (-:
Thanl you very much for your help and consideration

Verizon Galaxy Note 3 bricked?

I think I may have bricked my phone, possibly a softbrick? I was using Odin3 v3.09 with Root de la vega for my Verizon Galaxy Note 3, Model SM-N900V. The tutorial I was using said it was for my phone, I followed all the instructions, and I got fail the first time using the stock cord that came with it so I tried again and used a regular usb 2.0 cord and got a fail the second time.
This is the text from Odin.
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Root_de_la_Vega.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> cache.img.ext4
<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)
This is the text on my phone.
Code:
Odin Mode
Product Name: SM-N900V
Current Binary: Samsung Official
System Status: Official
[COLOR="Gray"]KNOX Kernal Lock: 0x0
KNOW Warranty Void: 0x0
QualCOMM SecureBoot: Enable (CSB)
RP SWREV: S1, T1, R1, A2, P1
Write Protection: Enable[/COLOR]
[COLOR="Red"]Secure Check Fail: cache[/COLOR]
I am assuming I am going to need to flash the phone back to a stock firmware but I am not sure which one I should be using, or how to go about doing that exactly as well. I have rooted/unrooted phones in the past. I have also flashed my old phones as well, but I don't remember how to nor can I seem to figure it out with this phone. If someone could point me in the right direction I would greatly appreciate the help. I am trying to put the HyperDrive ROM on my phone.

Update!
I came accross this method, http://forum.xda-developers.com/showthread.php?t=2483380
I followed the instructions on flashing to stock with Odin and I didn't have any luck in getting it to work. I downloaded the MI9 tar.md5 file, and the pit file selected them in there proper spots in the program and ran it. I got this error.
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_N900VVRUBMI9_N900VVZWMI9_1671014_REV03_user_low_ship_MULTI_CERT.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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and this error on my phone
SW REV CHECK FAIL : (aboot)Fused 2 > Binary 1

This should be a easy fix. Enter recovery mode by powering down the phone then holding the home button, vol up and the power button. Hold down all three buttons until you see recovery booting on the top in blue. The phone will reboot into recovery and then scroll to wipe data/factory reset with the vol down key and then press the power button and wait until it completes the reset. Now you should be good to go again. This will wipe all data but you will have your phone back.

Misterxtc said:
This should be a easy fix. Enter recovery mode by powering down the phone then holding the home button, vol up and the power button. Hold down all three buttons until you see recovery booting on the top in blue. The phone will reboot into recovery and then scroll to wipe data/factory reset with the vol down key and then press the power button and wait until it completes the reset. Now you should be good to go again. This will wipe all data but you will have your phone back.
Click to expand...
Click to collapse
When I do that I get a screen that says,
"Firmware upgrade encountered an issue. Please use Software Repair Assistant & try again."

luckychalmz said:
When I do that I get a screen that says,
"Firmware upgrade encountered an issue. Please use Software Repair Assistant & try again."
Click to expand...
Click to collapse
You might need to flash MJE instead of MI9 with Odin.

Misterxtc said:
You might need to flash MJE instead of MI9 with Odin.
Click to expand...
Click to collapse
Do you know of anywhere that I can get that file, the link that is in the guide is saying its going to take like three days. It's only 1.3gbs so I don't see why.

luckychalmz said:
Do you know of anywhere that I can get that file, the link that is in the guide is saying its going to take like three days. It's only 1.3gbs so I don't see why.
Click to expand...
Click to collapse
Try this guide if you haven't already. I just tried and it said three hours not days. If it's slow try canceling and restarting it again. You might get a faster dl rate. http://forum.xda-developers.com/showthread.php?t=2528707

Misterxtc said:
Try this guide if you haven't already. I just tried and it said three hours not days. If it's slow try canceling and restarting it again. You might get a faster dl rate. http://forum.xda-developers.com/showthread.php?t=2528707
Click to expand...
Click to collapse
That one is definitely going faster. Thank you. I will try this one once it's finished.

luckychalmz said:
That one is definitely going faster. Thank you. I will try this one once it's finished.
Click to expand...
Click to collapse
No problem. Did you try to clear cache in recovery mode? If not give that a try and then the factory reset while you are waiting. You have nothing to loose at this point.

Misterxtc said:
No problem. Did you try to clear cache in recovery mode? If not give that a try and then the factory reset while you are waiting. You have nothing to loose at this point.
Click to expand...
Click to collapse
That fixed it, thank you. Appreciate your help.

luckychalmz said:
That fixed it, thank you. Appreciate your help.
Click to expand...
Click to collapse
Cool, I'm glad to help and direct you to the info that has been shared. Enjoy.

I know a much faster,simpler and less data-damaging wau
You use odin to flash the PIT (keep the default 3 boxes that are auto-checked when you select the PIT file). It is only a couple MB and will fix your phone up in a jiff. You can flash the PIT with odin when the screen with the two exclamation signs is on and the phone is connected via USB. This is where I got mine for the note 3 verizon, got mine just last week, which was january 26th or something. androidfilehost com / ? fid= 23159073880936457 so just remove all spaces from that and paste it into the omnibar and g2g!

technoshima said:
You use odin to flash the PIT (keep the default 3 boxes that are auto-checked when you select the PIT file). It is only a couple MB and will fix your phone up in a jiff. You can flash the PIT with odin when the screen with the two exclamation signs is on and the phone is connected via USB. This is where I got mine for the note 3 verizon, got mine just last week, which was january 26th or something. androidfilehost com / ? fid= 23159073880936457 so just remove all spaces from that and paste it into the omnibar and g2g!
Click to expand...
Click to collapse
You my friend, are a genius!!! I was crapping my pants thinking it was over. Thanks a bunch. And yes, it is a much, much faster download than that MJE that took forever to download.
Kudos again, my friend.

Still having issue with Samsung Write Protection
fanatic4hockey said:
You my friend, are a genius!!! I was crapping my pants thinking it was over. Thanks a bunch. And yes, it is a much, much faster download than that MJE that took forever to download.
Kudos again, my friend.
Click to expand...
Click to collapse
technoshima said:
You use odin to flash the PIT (keep the default 3 boxes that are auto-checked when you select the PIT file). It is only a couple MB and will fix your phone up in a jiff. You can flash the PIT with odin when the screen with the two exclamation signs is on and the phone is connected via USB. This is where I got mine for the note 3 verizon, got mine just last week, which was january 26th or something. androidfilehost com / ? fid= 23159073880936457 so just remove all spaces from that and paste it into the omnibar and g2g!
Click to expand...
Click to collapse
I was able to flash the PIT file with Odin like you said which enabled me to get back to recovery, but I am still having issues with the Samsung Write protection being enabled (which is preventing me from flashing anything with Safestrap including trying to fully wipe and restart). I found out after attempting to flash my verizon note 3 that the write protection was an option that needed to be unchecked on the phone before flashing. Now I can't change it without being able to login all the way into the phone. Are there any options out there to change the write feature outside of being able to actually load the phone, like ADB?

luckychalmz said:
That fixed it, thank you. Appreciate your help.
Click to expand...
Click to collapse
Hi guys
I need some help I rooted my Verizon Note 3 and is stock on:
Odin Mode Please see attached image
When I ran these files : ALL_N900VVRUBMI9_N900VVZWMI9_1671014_REV03_user_low_ship_MULTI_CERT.tar.md5
DevEdition_P900v_MJE_StockRestore.tar.md5HLTE_USA_VZW_32G.pit on odin3
I got this error.
Please advice.
ALL_N900VVRUBMI9_N900VVZWMI9_1671014_REV03_user_low_ship_MULTI_CERT.tar.md5
DevEdition_P900v_MJE_StockRestore.tar.md5HLTE_USA_VZW_32G.pit
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_N900VVRUBMI9_N900VVZWMI9_1671014_REV03_user_low_ship_MULTI_CERT.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> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> aboot.mbn
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

vampirelife said:
Hi guys
I need some help I rooted my Verizon Note 3 and is stock on:
Odin Mode Please see attached image
When I ran these files : ALL_N900VVRUBMI9_N900VVZWMI9_1671014_REV03_user_low_ship_MULTI_CERT.tar.md5
DevEdition_P900v_MJE_StockRestore.tar.md5HLTE_USA_VZW_32G.pit on odin3
I got this error.
Please advice.
ALL_N900VVRUBMI9_N900VVZWMI9_1671014_REV03_user_low_ship_MULTI_CERT.tar.md5
DevEdition_P900v_MJE_StockRestore.tar.md5HLTE_USA_VZW_32G.pit
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_N900VVRUBMI9_N900VVZWMI9_1671014_REV03_user_low_ship_MULTI_CERT.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> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> aboot.mbn
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Looks similar to what I was getting from Odin. Did you have to uncheck the write protection in your phone settings before flashing anything? Someone told me that might be the cause of what happened with mine since I didn't even hear about doing so until I had already attempted to flash my phone.

im also getting a fail just after aboot. I originally attempted to install the deodex version on kitkat and originally was still able to access safestrap.
I have tried flashing every rom i can get my hands on over odin. ive tried making a recovery from my other note 3 via safestrap and swapping the micro sd over to this one. did not show up when i went to ss recover. so i booted to recovery cleared cache. still got aboot failed(auth) so i booted to recovery again and cleared everything except data. (including system) now i cant access SS any longer. get stuck on bootload screen or get verizon sofware assistant message. still unable to flash roms via oden i have tried everything but lollipop and odin versions 3.9 3.7 3.10
im am completely lost. im almost ready to ship it to someone to fix it for me.

I'm gonna bump this in the hopes someone sees it and can help me.

luckychalmz said:
I think I may have bricked my phone, possibly a softbrick? I was using Odin3 v3.09 with Root de la vega for my Verizon Galaxy Note 3, Model SM-N900V. The tutorial I was using said it was for my phone, I followed all the instructions, and I got fail the first time using the stock cord that came with it so I tried again and used a regular usb 2.0 cord and got a fail the second time.
This is the text from Odin.
Code:
Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
Root_de_la_Vega.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Odin v.3 engine (ID:4)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
SingleDownload.
cache.img.ext4
NAND Write Start!!
FAIL! (Auth)
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
This is the text on my phone.
Code:
Odin Mode
Product Name: SM-N900V
Current Binary: Samsung Official
System Status: Official
[COLOR="Gray"]KNOX Kernal Lock: 0x0
KNOW Warranty Void: 0x0
QualCOMM SecureBoot: Enable (CSB)
RP SWREV: S1, T1, R1, A2, P1
Write Protection: Enable[/COLOR]
[COLOR="Red"]Secure Check Fail: cache[/COLOR]
I am assuming I am going to need to flash the phone back to a stock firmware but I am not sure which one I should be using, or how to go about doing that exactly as well. I have rooted/unrooted phones in the past. I have also flashed my old phones as well, but I don't remember how to nor can I seem to figure it out with this phone. If someone could point me in the right direction I would greatly appreciate the help. I am trying to put the HyperDrive ROM on my phone.
Click to expand...
Click to collapse
Before you started this...what version of android were you using? You must flash the last version you had running or higher.
Get the firmware from here
http://www.sammobile.com/firmwares/database/SM-N900V/
instructions are also there
You can also try having Verizon reflash it or at the Samsung section of your local best buy
marcotheclepto said:
I'm gonna bump this in the hopes someone sees it and can help me.
Click to expand...
Click to collapse
Sent from my Note 3 via Tapatalk

donc113 said:
Before you started this...what version of android were you using? You must flash the last version you had running or higher.
Get the firmware from here
instructions are also there
You can also try having Verizon reflash it or at the Samsung section of your local best buy
Sent from my Note 3 via Tapatalk
Click to expand...
Click to collapse
thanks, im just jumping straight to 5.0 and hoping for the best. half hour left on the download. fingers crossed
*update* it seems the newer version was the answer for me... now to find a way to root it on lolipop... whole point was originally to get hyperdrive and get some headphone software worth using.

Note 3 SM-N9005 Firmware Issue & Device Recognised As 'Samsung GT-S5690'

Hi all,
I've heard great things about this website and joined up hoping to God you could help me. I tried updating the firmare on my phone to 4.4.2 from 4.3 using Odin3 v3.07 and it stopped suddenly with an error message and now my Note 3 continuously displays:
“Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again“
I have looked extensively through the threads already started but couldn't find a solution particularly as Kies is not recognising my device anymore stating it is an unsupported device, furthermore, 'MobileGo' software is showing the device as being a 'Samsung GT-S5690', instead of Note 3??. I tried Odin to recover back to original firmware but failed both times and phone now stuck on “Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again“.
My Mobile details are:
Model Number: SM-N9005
Serial Number: RF1DA5NMM5M
This is a log of 2 different attempts using Odin, one to 4.4.2 and the other back to stock:
Odin3 v3.07
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUDMK2_N9005OXADMK2_N9005XXUDMJ7_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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENB3_N9005OXXENB1_N9005XXUENB1_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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.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> FAIL! (Ext4)
<OSM> All threads completed. (succeed 0 / failed 1)
Please advise as I am left without a phone and only had it two months.
Your expertise and help would be gratefully appreciated.
Many thanks
John

Mamba25 said:
Hi all,
I've heard great things about this website and joined up hoping to God you could help me. I tried updating the firmare on my phone to 4.4.2 from 4.3 using Odin3 v3.07 and it stopped suddenly with an error message and now my Note 3 continuously displays:
“Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again“
I have looked extensively through the threads already started but couldn't find a solution particularly as Kies is not recognising my device anymore stating it is an unsupported device, furthermore, 'MobileGo' software is showing the device as being a 'Samsung GT-S5690', instead of Note 3??. I tried Odin to recover back to original firmware but failed both times and phone now stuck on “Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again“.
My Mobile details are:
Model Number: SM-N9005
Serial Number: RF1DA5NMM5M
This is a log of 2 different attempts using Odin, one to 4.4.2 and the other back to stock:
Odin3 v3.07
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUDMK2_N9005OXADMK2_N9005XXUDMJ7_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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENB3_N9005OXXENB1_N9005XXUENB1_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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.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> FAIL! (Ext4)
<OSM> All threads completed. (succeed 0 / failed 1)
Please advise as I am left without a phone and only had it two months.
Your expertise and help would be gratefully appreciated.
Many thanks
John
Click to expand...
Click to collapse
hello. have you tried another version of odin? im sure someone can help you revive your phone

Mine did the same thing,put it into download mode and flash cwm recovery and it'll come to life..

hypnodaz said:
Mine did the same thing,put it into download mode and flash cwm recovery and it'll come to life..
Click to expand...
Click to collapse
Thanks, once I have used Odin v3.09 to flash cwm recovery, will I still need to flash back to stock or will it simply work?

Mamba25 said:
Thanks, once I have used Odin v3.09 to flash cwm recovery, will I still need to flash back to stock or will it simply work?
Click to expand...
Click to collapse
You will have to flash stock firmware 4.4 before your phone will work again. Simply flashing cwm will get you to cwm recovery but not a working phone.
---------- Post added at 09:37 AM ---------- Previous post was at 09:31 AM ----------
Mamba25 said:
Thanks, once I have used Odin v3.09 to flash cwm recovery, will I still need to flash back to stock or will it simply work?
Click to expand...
Click to collapse
Have you tried using Odin V3.09 to flash 4.4?

hey_joe said:
You will have to flash stock firmware 4.4 before your phone will work again. Simply flashing cwm will get you to cwm recovery but not a working phone.
Click to expand...
Click to collapse
Hi, I have found a tutorial on flashing ClockworkMod Recovery v6.0.4.5 but it states:
"Must enable USB Debugging first" and also "Must let Reactivation lock off first", is this absolutely necessary as I can't access my phone, let alone its settings? Can I still proceed with installing ClockworkMod Recovery?

Mamba25 said:
Hi, I have found a tutorial on flashing ClockworkMod Recovery v6.0.4.5 but it states:
"Must enable USB Debugging first" and also "Must let Reactivation lock off first", is this absolutely necessary as I can't access my phone, let alone its settings? Can I still proceed with installing ClockworkMod Recovery?
Click to expand...
Click to collapse
Don't follow that one.
Go here and download the right file for your phone's model, put phone in download mode and flash using odin in ap/pda slot.
Btw, have you tried flashing 4.4 using odin v3.09?

When odin gives you the fail message technically you've already flashed the stock, but for some reason odin doesn't recognise it as a pass. .leave your phone plugged in, reset odin, put your phone into download phone and then flash recovery. . Hey presto your phone will wake up..

hypnodaz said:
When odin gives you the fail message technically you've already flashed the stock, but for some reason odin doesn't recognise it as a pass. .leave your phone plugged in, reset odin, put your phone into download phone and then flash recovery. . Hey presto your phone will wake up..
Click to expand...
Click to collapse
I don't think this is the case because when I first tried flashing from 4.3 to 4.4.2 it tried for a few seconds then failed and been stuck on “Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again“ despite resetting Odin and going back into download mode, tried reflashing but keep getting the 'FAIL' (logs posted in original first post).
Is there any reason why my phone is being detected as 'Samsung GT-S5690' in MobileGo? I'm thinking if Kies could detect it as the Note 3 again my problems would be solved.
I haven't tried Odin v3.09 because to be honest I thought the firmware file once extracted as a RAR file could only be read by Odin v3.07 is that not the case?
Soz everyone

Mamba25 said:
I haven't tried Odin v3.09 because to be honest I thought the firmware file once extracted as a RAR file could only be read by Odin v3.07 is that not the case?
Soz everyone
Click to expand...
Click to collapse
No it's not.

Mamba25 said:
Hi all,
I've heard great things about this website and joined up hoping to God you could help me. I tried updating the firmare on my phone to 4.4.2 from 4.3 using Odin3 v3.07 and it stopped suddenly with an error message and now my Note 3 continuously displays:
“Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again“
I have looked extensively through the threads already started but couldn't find a solution particularly as Kies is not recognising my device anymore stating it is an unsupported device, furthermore, 'MobileGo' software is showing the device as being a 'Samsung GT-S5690', instead of Note 3??. I tried Odin to recover back to original firmware but failed both times and phone now stuck on “Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again“.
My Mobile details are:
Model Number: SM-N9005
Serial Number: RF1DA5NMM5M
This is a log of 2 different attempts using Odin, one to 4.4.2 and the other back to stock:
Odin3 v3.07
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUDMK2_N9005OXADMK2_N9005XXUDMJ7_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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENB3_N9005OXXENB1_N9005XXUENB1_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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.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> FAIL! (Ext4)
<OSM> All threads completed. (succeed 0 / failed 1)
Please advise as I am left without a phone and only had it two months.
Your expertise and help would be gratefully appreciated.
Many thanks
John
Click to expand...
Click to collapse
looks like u r trying to flash 4.3 & 4.4 one after one, now dont try 4.3 at all, make sure kies is not running in baground, disable antivirus if any.

I had the the same issue with kies myself, tried every trick in the book before I tried the method I mention above.. maybe it's an issue with the phone itself, or a certain batch of phones?

Mamba25 said:
Hi all,
I've heard great things about this website and joined up hoping to God you could help me. I tried updating the firmare on my phone to 4.4.2 from 4.3 using Odin3 v3.07 and it stopped suddenly with an error message and now my Note 3 continuously displays:
...
Click to expand...
Click to collapse
The writing of stock 4.3 fails since your bootloader was updated by your failed attempt. You will probably never be able to write a 4.3 stock image.
The writing of 4.4 NB1 fails since probably it is for a slightly different region with a slightly different partitioning scheme. Ideally install the 4.4 for your specific model/region. If that fails you might need to write some 4.4 with repartition - there are some threads around (I think also the Hong-Kong version had serious problems with 4.4 because of that).

xclub_101 said:
The writing of 4.4 NB1 fails since probably it is for a slightly different region with a slightly different partitioning scheme. Ideally install the 4.4 for your specific model/region. If that fails you might need to write some 4.4 with repartition - there are some threads around (I think also the Hong-Kong version had serious problems with 4.4 because of that).
Click to expand...
Click to collapse
I saw the Hong Kong thread and to be honest got lost reading the posts, i'm beginning to think this is going to be a task beyond my capabilities as not the most technologically minded of people and need to be spoon fed. Is there an easy way to find out if I have a Hong Kong version phone? I brought it from e-cell on Ebay a couple of months ago?
If using a different version of Odin such as v3.09 once the firmware file is extracted where does it go as v3.07 is goes in the PDA section?
Many thanks

Mamba25 said:
I saw the Hong Kong thread and to be honest got lost reading the posts, i'm beginning to think this is going to be a task beyond my capabilities as not the most technologically minded of people and need to be spoon fed. Is there an easy way to find out if I have a Hong Kong version phone? I brought it from e-cell on Ebay a couple of months ago?
If using a different version of Odin such as v3.09 once the firmware file is extracted where does it go as v3.07 is goes in the PDA section?
Many thanks
Click to expand...
Click to collapse
There is AP in 3.09 in place of PDA.

Mamba25 said:
I saw the Hong Kong thread and to be honest got lost reading the posts, i'm beginning to think this is going to be a task beyond my capabilities as not the most technologically minded of people and need to be spoon fed. Is there an easy way to find out if I have a Hong Kong version phone? I brought it from e-cell on Ebay a couple of months ago?
If using a different version of Odin such as v3.09 once the firmware file is extracted where does it go as v3.07 is goes in the PDA section?
Many thanks
Click to expand...
Click to collapse
I don't think there is an easy way to see what the original version was as long as you can no longer boot the phone. I think the EU model is generally listed as N9005ZWE while the HK is N9005ZKA and that might be written somewhere on the box. Also it might be a different partitioning model even if it is not a Hong-Kong model.

xclub_101 said:
I don't think there is an easy way to see what the original version was as long as you can no longer boot the phone. I think the EU model is generally listed as N9005ZWE while the HK is N9005ZKA and that might be written somewhere on the box. Also it might be a different partitioning model even if it is not a Hong-Kong model.
Click to expand...
Click to collapse
Could you please let me know if the update be completed successfully. I have the same problem so want to know the steps of the
same. Please help me.

madsus said:
Could you please let me know if the update be completed successfully. I have the same problem so want to know the steps of the
same. Please help me.
Click to expand...
Click to collapse
I've taken the phone to a repair shop recommended by Samsung themselves, they've had it a week now and I rang yesterday and they said it is the first Hong Kong Note 3 they've received and are waiting to hear from Samsung as to how to repair it. BIG YAWN!
Will keep you posted - miss my phone

Note 3 SM-N9005 firmware upgarade issue
Hi , i am having the same problem in my Note 3 i upgraded phronesis rom and after the phone was not detected in computer. so tried to flash custom kitkat rom again then it got disconnected and then showing error as firmware upgrade issue,
tried to download firmware and update by Odin, tired cmw recovery and tried many firmwares, Odin shows Failure and Kies dosent shown code or phone in emergency recovery , all ways failed, is it possible to make the phone work normal.