Database Users

SM-N9005 Kitkat 4.4.3 failed

After updating my phone to the new firmware N9005XXUENA6_N9005OXXENA5_XEO.zip my phone failed to flash using Odin. I have tried so many version of Odin and still no luck, i have basically downloaded every rom that i can find from samsung-updates.com and still no luck. Let me know if you guys have a for fix for this because as of right now i can boot into Odin Mode but when i try to flash it via Odin 3.09 on any Rom it will fail. And yes i have tried every Samsung Kies version to try initialize this phone but it just does not work. i have attached the image of my S/N and Model this is one of the HK version and yes i tried the HK TGY rom and still no luck.

con2vp1 said:
After updating my phone to the new firmware N9005XXUENA6_N9005OXXENA5_XEO.zip my phone failed to flash using Odin. I have tried so many version of Odin and still no luck, i have basically downloaded every rom that i can find from samsung-updates.com and still no luck. Let me know if you guys have a for fix for this because as of right now i can boot into Odin Mode but when i try to flash it via Odin 3.09 on any Rom it will fail. And yes i have tried every Samsung Kies version to try initialize this phone but it just does not work. i have attached the image of my S/N and Model this is one of the HK version and yes i tried the HK TGY rom and still no luck.
Click to expand...
Click to collapse
Well if you can still get into download mode you are still safe.
Does it fail mid flash or can´t even recognize your phone?

Reboot your pc and try again.

It will fail on the ABOOT, and i have tried to reboot my pc and still no luck i have attached my model of the phone

con2vp1 said:
It will fail on the ABOOT, and i have tried to reboot my pc and still no luck i have attached my model of the phone
Click to expand...
Click to collapse
Try this guide. It seems to be the same phone as yours.

If you are trying to go back to 4.3 from 4.4.2 then it won't be possible. You will now have to stay in KitKat only and wait for more ROM for KitKat.
Sent from my SM-N900 using Tapatalk

Did you try flashing with update bootloader ticked? If you tried that already then I think you are going to have to wait for the hk version of kit Kat for your phone to work again.
Or try this..... http://forum.xda-developers.com/showthread.php?t=null
Sent from my SM-N9005 using Tapatalk

odin 3.09 tick Phone boot loader update.

hey_joe said:
Try this guide. It seems to be the same phone as yours.
Click to expand...
Click to collapse
which one should i download the .zip or the .rar and they two different file size

con2vp1 said:
which one should i download the .zip or the .rar and they two different file size
Click to expand...
Click to collapse
Both are same.
Rar is just better compressed. I went with it.

Just an idea make sure reactivation lock is not ticked in settings
Sent from my SM-N9005 using xda app-developers app

rcp27 said:
Just an idea make sure reactivation lock is not ticked in settings
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
Its not ticked, i might just have to wait to an HK firmware to update this because any other i have tried is not working and it says PIT FAIL when i try this solution http://forum.xda-developers.com/showthread.php?t=2613374. even though i followed the instructions step by step.
Is there another way to flash my device other than Odin? and yes ADB does not work

con2vp1 said:
Its not ticked, i might just have to wait to an HK firmware to update this because any other i have tried is not working and it says PIT FAIL when i try this solution http://forum.xda-developers.com/showthread.php?t=2613374. even though i followed the instructions step by step.
Is there another way to flash my device other than Odin? and yes ADB does not work
Click to expand...
Click to collapse
Can you screenshot your odin configuration that you flashed and post it here?

FeralFire said:
Can you screenshot your odin configuration that you flashed and post it here?
Click to expand...
Click to collapse
This is the Odin config and after the CSC was only applied the phone says PIT FAIL

con2vp1 said:
This is the Odin config and after the CSC was only applied the phone says PIT FAIL
Click to expand...
Click to collapse
Hmm.
Weird.
Do you know how to use heimdall?
Use it to have a look at your pit file and compare it to the one in the CSC zip. See what all is different.
Or just post your pit here.
EDIT: Just noticed that you have a 16GB version. I don't know how to help you there, man. You need a completely different pit file. One that is designed for 16GB. But since that model was only launched in Hong Kong, I don't think you will find one from outside, unless somebody can make one specifically for you. I have been trying to learn to do that, but as of yet, I can't.
Without a proper pit file, your only options are either wait for the Hong Kong Kitkat version or try installing the Sweet ROM.

con2vp1 said:
After updating my phone to the new firmware N9005XXUENA6_N9005OXXENA5_XEO.zip my phone failed to flash using Odin. I have tried so many version of Odin and still no luck, i have basically downloaded every rom that i can find from samsung-updates.com and still no luck. Let me know if you guys have a for fix for this because as of right now i can boot into Odin Mode but when i try to flash it via Odin 3.09 on any Rom it will fail. And yes i have tried every Samsung Kies version to try initialize this phone but it just does not work. i have attached the image of my S/N and Model this is one of the HK version and yes i tried the HK TGY rom and still no luck.
Click to expand...
Click to collapse
're using Odin with Note 3 connected to a USB 3.0? if yes, try connecting it to a USB 2.0. already happened to me a few times, and the solution was this. sorry for the bad english.

FeralFire said:
Hmm.
Weird.
Do you know how to use heimdall?
Use it to have a look at your pit file and compare it to the one in the CSC zip. See what all is different.
Or just post your pit here.
Click to expand...
Click to collapse
Well thats an issue because im not sure if this my right PIT FILE for this phone. Because usually it will go smoothly for these manual updates using Odin and this is my first encountering this error. And my fault i didnt backup my ROM which i should have done first before getting excited with this KitKat for my Note 3. That CSC file i got that from this site http://forum.xda-developers.com/showthread.php?t=2613374 and just followed instructions on how to do it, but it will just give me that error when i try to apply that method. But here's the PIT file that i got from that download.
I think its on a wrong region because i got that leaked update here http://www.sammobile.com/2014/01/13...kitkat-rolling-out-to-galaxy-note-3-sm-n9005/ and it looks like from Poland? does that matter? because my Note 3 is and HK version?
I have done so many phones rooted them and install custom roms this is the first time it failed on me. And funny thing is its my own cell phone lol

con2vp1 said:
Well thats an issue because im not sure if this my right PIT FILE for this phone. Because usually it will go smoothly for these manual updates using Odin and this is my first encountering this error. And my fault i didnt backup my ROM which i should have done first before getting excited with this KitKat for my Note 3. That CSC file i got that from this site http://forum.xda-developers.com/showthread.php?t=2613374 and just followed instructions on how to do it, but it will just give me that error when i try to apply that method. But here's the PIT file that i got from that download.
I think its on a wrong region because i got that leaked update here http://www.sammobile.com/2014/01/13...kitkat-rolling-out-to-galaxy-note-3-sm-n9005/ and it looks like from Poland? does that matter? because my Note 3 is and HK version?
I have done so many phones rooted them and install custom roms this is the first time it failed on me. And funny thing is its my own cell phone lol
Click to expand...
Click to collapse
You gave me the pit file from the zip. I was asking for the one from your phone.
But anyway I found one for the 16GB version somehwere. I am taking a look at it. Will try editing it to fit your needs. Give me a little while.
And yes, it matters, because the pit file determines the sizes of the various partitions. Since yours is a 16GB version, the pit from a 32GB won't work.

View attachment Modded_16GB.tar
Try flashing this tar file. Put it in the CSC part of the Odin.
Though I can't guarantee anything. First time, I am doing anything like this.

FeralFire said:
View attachment 2520563
Try flashing this tar file. Put it in the CSC part of the Odin.
Though I can't guarantee anything. First time, I am doing anything like this.
Click to expand...
Click to collapse
Thanks
Odin just crashed on me while it was on SET PARTITION

[Q] Hong Kong 32GB n9005 and PIT

I want to flash an Aussie ROM on my HK 32GB n9005. I've been doing some reading and what I think I need to do is as follows...
ghibli3's thread at http://forum.xda-developers.com/showthread.php?t=2550823 specifically addresses this issue and thanks to those contributing there and elsewhere.
Now to check I understand what they are saying before I brick my phone.
I have these:
CSB_signed_HLTE_EUR_OPEN_32G_0718.pit
CSB_signed_HLTE_EUR_OPEN_32G_0805.pit
ghibli3-N9005.pit
ratcom-N9005.pit
I also used ghibli3's N9005-SaveMyPit from http://forum.xda-developers.com/attachment.php?attachmentid=2426123&d=1385903491 to get a copy of my current pit.
I have my original HK MI7 stock, a HK stock MK2 (used to root my phone originally using RDLV) and both an MI7 and MJ7 Aussie ROMs.
So... here is what I think I need to do... Please let me know if this is correct or tell me how to do it better.
Using Odin and with phone in DL mode, USB Debugging on, Samsung drivers and ADB setup on PC...
1. Load a PIT file in [PIT] in Odin and tick [Re-Partition] then [Start]
(1st question, do I reboot the phone or just go to the next step?)
2. Follow RDLV steps to flash the Aussie MJ7 to root the phone.
(2nd question, should I drop back to the MI7 version for the root operation? I don't think it is needed as when I rooted my phone with HK version, I had HK MI7 on the phone and used HK MK2 to root it)
(3rd question, I have Kies 3 on my PC - should I uninstall it before doing any of this or might it be helpful to have it still installed?)

OK, so no comments so far... let's try a slightly different approach.
(4th question, Can I load the PIT into Odin, tick [Re-Partition] and add in the VEGA version of the AP (from RDLV) and then flash them as one?

Journyman16 said:
OK, so no comments so far... let's try a slightly different approach.
(4th question, Can I load the PIT into Odin, tick [Re-Partition] and add in the VEGA version of the AP (from RDLV) and then flash them as one?
Click to expand...
Click to collapse
For using PIT file, you need to add the PIT to Odin when you flash so it'll repartition as it's flashing. However, don't take that as a solid cause I am not 100% sure myself as I haven't messed with PIT files (yet) - but from what I have read that is how it is done. - Have a scan through the HK bricked (solved) threads to be doubley sure cause yeah, it's easy to end up with a brick

Thanks for that. Kinda what I was planning to do but I'm not sure if I do the PIT flash first then do the rest or if I do it all as one process. I'll check out that thread... been looking anywhere I could find a PIT reference.

Well, that was fun... not.
I tried the PIT files with NAND erase all, re-partition f. reset time and Auto reboot all ticked - it failed - I got a systemconnection error. I tried again with each of the PITs listed above except ratcom's - his is from an MJ7 build and I was unsure if that would trip Knox or not.
2 hours pass, with me looking all around XDA and trying a variety of things. Incidentally I think maybe the systemconnect thing might be related to not restarting the phone to get the error screen. It seems Odin can do things when that screen is on that it can't do in plain Download mode. At least, on mine, the eventual fix worked only AFTER I had the error screen (shows the hone pic and a PC pic)
I didn't try flashing CWM. Nor doing anything that might add an MJ7 or KK bootloader. If I trip Knox I want it to be by my choice, not because I can't fix something.
But clearly I am doing something wrong in trying to repartition my phone - none of the PIT flashes worked. None of the flash ROM's worked. I looked around for a MJ3 or less ROM with the 4 files - figured I could get that I could try using a PIT for the right CSC and those files and solve both issues at once.
I tried my MK1 HK Vega image and no go. So I sat and thought it through and realised that last time I had problems I had the error screen NOT download mode so I rebooted the phone and Voila! up popped the error screen. Odin promptly flashed my HK MK1 version and now I am restoring my apps from the extSDcard. Got a bit of setup work to do but it's up and running again.
But I will have to trip Knox now - I'm sick of not having a Nandroid backup that could just restore everything where it was instead of me having to manually put things back as they were.
Any ideas as to what I did wrong?

Journyman16 said:
Well, that was fun... not.
I tried the PIT files with NAND erase all, re-partition f. reset time and Auto reboot all ticked - it failed - I got a systemconnection error. I tried again with each of the PITs listed above except ratcom's - his is from an MJ7 build and I was unsure if that would trip Knox or not.
2 hours pass, with me looking all around XDA and trying a variety of things. Incidentally I think maybe the systemconnect thing might be related to not restarting the phone to get the error screen. It seems Odin can do things when that screen is on that it can't do in plain Download mode. At least, on mine, the eventual fix worked only AFTER I had the error screen (shows the hone pic and a PC pic)
I didn't try flashing CWM. Nor doing anything that might add an MJ7 or KK bootloader. If I trip Knox I want it to be by my choice, not because I can't fix something.
But clearly I am doing something wrong in trying to repartition my phone - none of the PIT flashes worked. None of the flash ROM's worked. I looked around for a MJ3 or less ROM with the 4 files - figured I could get that I could try using a PIT for the right CSC and those files and solve both issues at once.
I tried my MK1 HK Vega image and no go. So I sat and thought it through and realised that last time I had problems I had the error screen NOT download mode so I rebooted the phone and Voila! up popped the error screen. Odin promptly flashed my HK MK1 version and now I am restoring my apps from the extSDcard. Got a bit of setup work to do but it's up and running again.
But I will have to trip Knox now - I'm sick of not having a Nandroid backup that could just restore everything where it was instead of me having to manually put things back as they were.
Any ideas as to what I did wrong?
Click to expand...
Click to collapse
2nd link in my signature.
Follow it to step 6. Then flash whatever ROM you want. Make sure your phone is 32 gigs or more. Won't work on 16 gb version.

So this gets a bit strange now... I downloaded Phone Info from Play Store and ran it. I did that because I noticed I was having Wifi issues - it was working but kept thinking it was off - I'd click it to turn it on and the button wouldn't go green, but I had signal in the Notification bar. Going to Recovery to clear cache showed it was now applying CSC-code as BTU instead of TGY, so SOMETHING worked when I was doing the PITs.
So, Phone Info shows my Region Code as BTU, my CSC country as UK/IRE and my CSC Country ISO as GBBut I have a mix of ROM info:
Bootloader: ZHUBMI7
Baseband: ZHUDMJ9
PDA: XXUDMK2
CSC: OXADMK2
So, PDA and CSC are from a UK MK2 I tried to use early on and failed with, while BL and BB are from the original HK MI7 (BL) and the HK MK1 I rooted with.
So my question is now, can I now flash a BTU or other normal ROM onto my phone, using the RDLV process to make sure I get root and don't trip Knox?
IIRC I think the process works up to MK2 (and certainly does to MK1 as that what I used originally) so I should be able to DL (say) XXUBMJ1 to use for the BL and use XXUDMK2 for the root process. (i.e. the same as I did using HK MI7 for the BL and HK MK1 for the root process)
3 questions:
1. Is it the PDA that determines the partition Hong Kong users have such problems with? Or is it the Bootloader?
2. Can anyone think of a reason why this would not work? (now my CSC is BTU)
3. Could I now use an Aussie ROM to run the RDLV process?

FeralFire said:
2nd link in my signature.
Follow it to step 6. Then flash whatever ROM you want. Make sure your phone is 32 gigs or more. Won't work on 16 gb version.
Click to expand...
Click to collapse
Thanks for the Reply.
For now I'd prefer to stay away from KK ROMs - too many people having issues, and the prevention of returning to 4.3 is, to me, a killer until Samsung get the bugs out. Given that many people are doing OK with KK, I think it is unlikely Samsung will do much about the bugs until a larger number of people have problems and start bombarding their support lines.
Plus, on 4.3 I have a very fast phone that gives more than 2 days use even with fairly heavy use (for me) and up to 4 days for light use. Why make an irreversible change when the phone is doing well already? For me the next step is custom recovery - I don't like not having a Nandroid BU and several times now after restoring apps I find I need to fix permissions - without custom recovery that means a laborious uninstall/reinstall from Play Store, one app at a time. Pisses me off...
I find it interesting that Samsung are clearly using users such as XDA members as their testing area, while at the same time shutting down the activities we like to do. (Custom ROMs etc) I say clearly using us because otherwise there is no excuse for the regularity of leaked ROMs - Samsung pass it on to us to try and I would bet, have staff watching us to see what issues we have.
So it seems a bit counter-productive to work so hard to lock the phones so we can't play with them.

Journyman16 said:
Thanks for the Reply.
For now I'd prefer to stay away from KK ROMs - too many people having issues, and the prevention of returning to 4.3 is, to me, a killer until Samsung get the bugs out. Given that many people are doing OK with KK, I think it is unlikely Samsung will do much about the bugs until a larger number of people have problems and start bombarding their support lines.
Plus, on 4.3 I have a very fast phone that gives more than 2 days use even with fairly heavy use (for me) and up to 4 days for light use. Why make an irreversible change when the phone is doing well already? For me the next step is custom recovery - I don't like not having a Nandroid BU and several times now after restoring apps I find I need to fix permissions - without custom recovery that means a laborious uninstall/reinstall from Play Store, one app at a time. Pisses me off...
I find it interesting that Samsung are clearly using users such as XDA members as their testing area, while at the same time shutting down the activities we like to do. (Custom ROMs etc) I say clearly using us because otherwise there is no excuse for the regularity of leaked ROMs - Samsung pass it on to us to try and I would bet, have staff watching us to see what issues we have.
So it seems a bit counter-productive to work so hard to lock the phones so we can't play with them.
Click to expand...
Click to collapse
You need the international pit file in your phone. Flashing the CSC file will put that pit in your phone. It won't touch the bootloader or the system files.

FeralFire said:
You need the international pit file in your phone. Flashing the CSC file will put that pit in your phone. It won't touch the bootloader or the system files.
Click to expand...
Click to collapse
Unfortunately, PIT's don't seem to come easy. As above I have about 4 of them I tried. There seems a bit of a disconnect between what the AP/CP/CSC are and what the files in a ROM are e.g. in XXUBMH1 there's boot.img, recovery.img, system.img.ext4, userdata.img.ext4, persdata.img.ext4, persist.img.ext4 and in XXUBMI7 there's sbl1.mbn, aboot.mbn, rpm.mbn, tz.mbn, sdi.mbn, NON-HLOS.bin, boot.img, recovery.img, system.img.ext4, modem.bin, cache.img.ext4, hidden.img.ext4
While I've been around a while now, this seems to be a blank spot for me at present - how do I flash a CSC? From reading it seems some ROM.s come with 4 or 5 files, e.g. see attachment - but I haven't been able to find one yet. (the one in the pic was hosted on Hotfiles which is now defunct thanks to the Almighty USA draconian control freaks. )
Update: I think I have found a copy of it so I can try that when it finishes DL'ing.
Other than that, anyone know of where there might be another such ROM to DL? Also if I am flashing a CSC file do I flash the PIT as well (i.e. at the same time) or do the PIT first?
Which Odin options get ticked for a PIT? I tried [F. Reset Time] [Re-Partition] [Auto Reboot] [Nand Erase All] previously and it didn't seem to work. I saw a recovery type post that suggested ticking [Phone EFS Clear] but seems to me that is a tick towards Brick - and the Recovery being offered was to a KK ROM anyway.

FeralFire said:
2nd link in my signature.
Follow it to step 6. Then flash whatever ROM you want. Make sure your phone is 32 gigs or more. Won't work on 16 gb version.
Click to expand...
Click to collapse
FeralFire said:
You need the international pit file in your phone. Flashing the CSC file will put that pit in your phone. It won't touch the bootloader or the system files.
Click to expand...
Click to collapse
I just looked at your post again - I realise I might have a wrong idea. Although the leaked ROM is KK, I was assuming flashing the CSC would upgrade my phone - is that the case or can I use your 6 steps just to change my PIT and then do the 4.3 RDLV process to have a root 4.3 phone?
Downloading it now - started with the torrent but that's running slow; I will let it run to completion to maybe help some others get it faster but I've got the Storage Cow one running as well. We'll see which one arrives first Either way I'll leave it seeding.

Journyman16 said:
I just looked at your post again - I realise I might have a wrong idea. Although the leaked ROM is KK, I was assuming flashing the CSC would upgrade my phone - is that the case or can I use your 6 steps just to change my PIT and then do the 4.3 RDLV process to have a root 4.3 phone?
Downloading it now - started with the torrent but that's running slow; I will let it run to completion to maybe help some others get it faster but I've got the Storage Cow one running as well. We'll see which one arrives first Either way I'll leave it seeding.
Click to expand...
Click to collapse
Yeah, you should be able to.
I tried flashing the MK2 ROM after flashing that CSC. It worked perfectly. But then I upgraded to kitkat. So I can't test JB stuff anymore.

FeralFire said:
Yeah, you should be able to.
I tried flashing the MK2 ROM after flashing that CSC. It worked perfectly. But then I upgraded to kitkat. So I can't test JB stuff anymore.
Click to expand...
Click to collapse
Well, it let me flash the vega BTU MK2 ROM but now there's a wifi problem. Still waiting for cygwin to download so I can RDLV on the XSA ROM. There seems to be some kind of conflict between BTU and Australian settings. Says to turn on wireless and actually finds my SSID's but then doesn't connect properly. le sigh...

Well it's been coming up to 24 hours with no phone but I seem to have found my way.
The problem seems to have been a mismatch between BL, CSC and PIT. In trying to get off the Hong Kong set up I wound up with a ZHU BL, BTU CSC and XSA CP and AP. It worked but I had no wifi. tried a few things to get it working and in trying to flash an XSA CSC (I think it was XSA) I got the Knox bit change. With no wifi I thought maybe the problem was the BUT-based CP needed changing. In trying to fix that, somehow I triggered Knox
I tried DL & Install of Omega 6 (it's a 4.3 - not ready to go KK yet) but although it completed nicely (so many ROM's got hidden or system errors in Odin) the phone didn't start. I tried installing Philz so I could run things from the extSDcard but an XSA wouldn't work nor would anything I had below MJ7. Last Phone Info view I had I still had a ZHU CP, even though AP and CSC were XSA-based.
Finally I got the MJ7 ROM from http://forum.xda-developers.com/sho...9005xxudmj7-pre-rooted-knox-free-odex-bl-free and it did the trick.
It's been a learning experience but I'd be happier if I knew for sure both what triggered the Knox bit (I was being very careful about it) and why some of the other ROM installs simply didn't work.

Resurrecting this one because I'm looking for info on flashing my 32G HK Note 3, but it came with KK pre-installed. So I'm not sure what differences I have to be aware of. Any tips?

For whoever still experiences issues with HK 32GB n9005 devices, After wasting half a day on that crap, i was able to flash N9005ZSUGOK2_N9005OZSGOK2_TGY from sammobile coupled with the PIT attached.

sm-n900
sm-900 and pit

[Q] Note 3 Lollypop Flashing Help

Hello all,
I had a galaxy note 3 (SM-N9005, 16GB Hong Kong Version) with last updated to KitKat(OTA). For the first time, i decided to take the risk of flashing the ROM manually and downloaded the Poland Lollypop Rom N9005XXUGBOA5_N9005XEOGBOA4_N9005XXUGBOA1_HOME.tar.md5 and flashed the phone using Odin with only Reset and Reboot flags checked. It failed at ext Image error.
After some reading i find out that HongKong have different partition structure and hence require to flash with a pit, i downloaded a pit file
(SM-N9005_HLTE_HKTW_OPEN_16G) from forums here and tried to re flash it with Reset, Reboot and Repartition flags and this time it stucks at error
PIT Fail : Total Sectors (38777344). I can now only boot up in download mode.
Can anyone let me know is there any chance, whether i can bring my phone back to life.

spandita said:
Hello all,
I had a galaxy note 3 (SM-N9005, 16GB Hong Kong Version) with last updated to KitKat(OTA). For the first time, i decided to take the risk of flashing the ROM manually and downloaded the Poland Lollypop Rom N9005XXUGBOA5_N9005XEOGBOA4_N9005XXUGBOA1_HOME.tar.md5 and flashed the phone using Odin with only Reset and Reboot flags checked. It failed at ext Image error.
After some reading i find out that HongKong have different partition structure and hence require to flash with a pit, i downloaded a pit file
(SM-N9005_HLTE_HKTW_OPEN_16G) from forums here and tried to re flash it with Reset, Reboot and Repartition flags and this time it stucks at error
PIT Fail : Total Sectors (38777344). I can now only boot up in download mode.
Can anyone let me know is there any chance, whether i can bring my phone back to life.
Click to expand...
Click to collapse
It sounds like you tried to reflash the HK PIT file - what you actually need is a PIT to suit the firmware you want to flash. If you use the HK pit you need to flash a HK ROM.
Also, make sure you actually pull the battery to get into Download mode. i.e. take out battery, wait 10 secs, then put it in and hold down the keys for DL mode. Restarts don't seem to work properly when flashing BL's and Modems so the physical method is needed.
Start by getting the latest HK version and see if Odin will flash it. THEN look at getting a EU pit file to go with BOA5.

Journyman16 said:
It sounds like you tried to reflash the HK PIT file - what you actually need is a PIT to suit the firmware you want to flash. If you use the HK pit you need to flash a HK ROM.
Also, make sure you actually pull the battery to get into Download mode. i.e. take out battery, wait 10 secs, then put it in and hold down the keys for DL mode. Restarts don't seem to work properly when flashing BL's and Modems so the physical method is needed.
Start by getting the latest HK version and see if Odin will flash it. THEN look at getting a EU pit file to go with BOA5.
Click to expand...
Click to collapse
Thanks for reply!!
Yes, it makes sense. So, i am going to download the Hongkong firmware. Will try it and let you know if i got any luck in bringing it up

spandita said:
Thanks for reply!!
Yes, it makes sense. So, i am going to download the Hongkong firmware. Will try it and let you know if i got any luck in bringing it up
Click to expand...
Click to collapse
I had a HK S3 and had similar problems. Not sure why Samsung makes them so different. I was new to Androids and thought I had trashed my new phone.
But it's a good way to learn - first you find out what has gone wrong and then how to fix it and before you know it, you are on your way to being flash-addicted.

Thank you
@Journyman16 Thank you very much :victory:, i got my phone up again with the hong kong firmware .... I was also looking for pit file for lollipop polland firmware, but didnt find anyone specific to 16gb note...
Can you direct me to some good resource from where i can go through tit bits of flashing? Particularly regarding this numbering system of Android basebands
As you mentioned, i like the whole incident(Learned something new) .... and dont want to gie up on getting lollipop :highfive:

spandita said:
@Journyman16 Thank you very much :victory:, i got my phone up again with the hong kong firmware .... I was also looking for pit file for lollipop polland firmware, but didnt find anyone specific to 16gb note...
Can you direct me to some good resource from where i can go through tit bits of flashing? Particularly regarding this numbering system of Android basebands
As you mentioned, i like the whole incident(Learned something new) .... and dont want to gie up on getting lollipop :highfive:
Click to expand...
Click to collapse
Been a while since I looked at such things but search in Q&A as well as Android Development for things like 'root guide' or perhaps click on the Advanced Search button and look for 'guide' in post headings.
Also as you browse the subjects that interest you there are often links out to tutorials etc. - another reason for always reading a thread before posting.
Good luck on the journey...

FAILED flashing a custom ROM.

I tried to root my device (Samsung Galaxy Note 3 SM-N9005) and it went quite well.
Then I tried to flash a custom rom (Darkwolf S7 edge port) on my phone but I ended up in a bootloop where it was stuck on the samsung logo for hours.
I tried different stuff to get out of it but nothing worked so I decided to flash the stock rom onto my phone and at the odin status I get "FAIL". And on my device it shows "Volume Size is too big 4620289 < 4718599. And my phone is unusable. I need some help asap to fix it.
Please Help!!!

What is the phone model?
You used a stock ROM from sammobile.com in Odin?

audit13 said:
What is the phone model?
You used a stock ROM from sammobile.com in Odin?
Click to expand...
Click to collapse
My phone is a Samsung Galaxy Note 3 SM-N9005.
Yes,I used a stock ROM from sammobile.com in Odin.
But I get "FAIL!" over and over again...with the message,"Volume size is too big......",on my phone.

Have you tried using different version of Odin, different USB cables, and USB ports? You may need to flash the stock ROM with a pit file.

audit13 said:
Have you tried using different version of Odin, different USB cables, and USB ports? You may need to flash the stock ROM with a pit file.
Click to expand...
Click to collapse
I've tried everything except for using a pit file. I don't really know much about using a pit file so I'm a bit apprehensive.
Could you help?

I have the exact same problem, but without the volume thing, I need help!

BarryAllen97 said:
I have the exact same problem, but without the volume thing, I need help!
Click to expand...
Click to collapse
Hey there Flash!! xD
Its a pain..isn't it?
Anyway I figured out how to fix the phone finally...
You'll need to flash the custom ROM with the PIT,CP,AP, and CSC files.
Here's the link...http://www.tsar3000.com/Joomla/inde...ader-csc-pit-files&catid=55:samsung&Itemid=82
>Download the file suitable for your phone and specific model...Extract those files.. BE VERY CAREFUL TO CHOSE YOUR SPECIFIC MODEL!!!
>Launch Odin...
>Put you phone in Download mode and connect it...
>Load the PIT,CP,AP and CSC files in their respective slots..
*DON'T FORGET TO CHECK THE "RE-PARTITION" OPTION*
>And then hit the "start" button and pray...IT WORKS!!!
However this will erase EVERYTHING on your phone...all the user data...if you have some photos/videos/songs/EVERYTHING...your sd card should be safe though.
I hope this works for you...it worked for me..
Let me know if it does!! Have a nice day!!

kurosaki999 said:
I've tried everything except for using a pit file. I don't really know much about using a pit file so I'm a bit apprehensive.
Could you help?
Click to expand...
Click to collapse
..

audit13 said:
Have you tried using different version of Odin, different USB cables, and USB ports? You may need to flash the stock ROM with a pit file.
Click to expand...
Click to collapse
hey thanks man...it did help..
flashed the stock rom with the pit,ap,csc files and finally got out of the bootloop..
I really appreciate the help!

Bad rooting. Stuck on Samsung-logo. Possible to undo / save personal data.

Hi, I might have messed up.
Took backup of all media, except that I'd forgotten that I also had a lot of photos saved as mms, directly in the messages. I'd also like to keep some of the messages, from my grandparents etc.
I'm stuck on "breathing" Samsung-logo.
I followed this recipe, as I've used it once before with success. Not this time though.
http://mobilesiri.com/galaxy-s7-edge-exynos-root/
I downloaded the auto-root from chainfire, but it might be outdatet?
https://download.chainfire.eu/930/CF-Root/CF-Auto-Root/CF-Auto-Root-hero2lte-hero2ltexx-smg935f.zip
I used Odin 3.12.3. Loaded the tar-file in AP.
Com + text comes up as good.
Started, and it came up as passed in a matter of seconds.
Phone turns off after a little while, and turn on again.
It won't go past the Samsung-logo when I power it on.
Safe-mode doesn't work, but it will go to download mode. I've tried wiping the cache, didn't help.
I might be mistaken, but could it be possible to flash stock rom from Odin, using this firmware: https://www.sammobile.com/firmwares/galaxy-s7-edge/SM-G935F/NEE/download/G935FXXU1DQJ2/193815/
It does look like it according to https://forum.xda-developers.com/showthread.php?t=2583588 and https://android.stackexchange.com/q...flashing-stock-rom-via-odin-delete-phone-data
If this isn't the case. Is it possible to install a recovery-program with Odin, even though the phone is "stuck"?
I've heard some people say it *might* be possible.
All the best, and thanks for any input
Chris

Well, I advice you to wait for second opinion, but I was in the same situation, for the exception I knew my current firmware details, re-downloaded the same firmware from sammobile and flash it with ODIN. Whatever firmware you flash, you must use HOME_CSC which is included in the zip package, not the "pure" CSC. Saying it again, it helped me, but I knew my current CSC (changing CSC triggers factory reset AFAIK) and factory reset wasn't made, so you should wait for second opinion before attempting anything. Good luck

MrYoan said:
Well, I advice you to wait for second opinion, but I was in the same situation, for the exception I knew my current firmware details, re-downloaded the same firmware from sammobile and flash it with ODIN. Whatever firmware you flash, you must use HOME_CSC which is included in the zip package, not the "pure" CSC. Saying it again, it helped me, but I knew my current CSC (changing CSC triggers factory reset AFAIK) and factory reset wasn't made, so you should wait for second opinion before attempting anything. Good luck
Click to expand...
Click to collapse
Thank you for replying MrYoan! I'm glad that you got your phone up and running again.
If anybody has a second opinon, I'd love to hear it.
Sorry if my text is too long/wrong etc.
Thanks again, Chris.

You need to put every file in, not just AP

tactical bacon said:
You need to put every file in, not just AP
Click to expand...
Click to collapse
Every file? The tmax.dll and zlib.dll?
The tutorial said only the AP?
Thanks for replying btw. This thing is driving me nuts.

ChrisSolt said:
Every file? The tmax.dll and zlib.dll?
The tutorial said only the AP?
Thanks for replying btw. This thing is driving me nuts.
Click to expand...
Click to collapse
You should have a folder with BL, AP, CP and CSC. Try redownloading the firmware from another site like sammobile

I recovered some pics with an app. Maybe this is also a solution if you need to do a full wipe.

tactical bacon said:
You should have a folder with BL, AP, CP and CSC. Try redownloading the firmware from another site like sammobile
Click to expand...
Click to collapse
But only on the firmware one right? That one looks ok.
I thouth you were talking about the autoroot itself.
Thanks!

pufnasti said:
I recovered some pics with an app. Maybe this is also a solution if you need to do a full wipe.
Click to expand...
Click to collapse
Could you tell me which app? The phone is non-responsive (except power + volup or voldown, etc.)
Thank you

anybody have any more input? I know it's busy with christmas and all, but it's really appreciated

pufnasti said:
I recovered some pics with an app. Maybe this is also a solution if you need to do a full wipe.
Click to expand...
Click to collapse
How? Was your phone correctly rooted beforehand?