Database Users

[Q] DOWNLOAD mode N9005 - 4.4.2 - UDC START?

I'm installing the new firmware but i had an issue with odin...
I flashed again 4.4.2 but in download mode, the last line you can see " UDC START" in colour red... Is this normal? I think the phone works good, but i don't know why put on this...
Anyone have this new line??

I have the same problem with a N9005 I guess it was Hong Kong version for the kanjis in the back, but is stuck in odin mode with the UDC START line

UDC Start info.
Ok gent's little more knowledge about "udc start" I am guessing that the problem became clear as you installed 4.4.2 KK.
So did I and came across UDC Start the second time I booted into download mode.
As I played around i became aware that the "UDC Start" mode locks the download loader to certain criteria. This would be 4.4.2 KK,
so anything under 4.4.2 will get a MASSIVE RED FAIL. That including the CWR/TWRP recoveries and ROOT files.
So just to specify, yes phone is now locked/bricked to 4.4.2 KK software only.
Therefore I would please like some help to get the udc start away!? If anyone can help.
If I shared some light to the darkness please say thanks.:good:

Try this out:
Worked for me on a Hong Kong 16GB N9005 which was stuck on the 'Samsung Galaxy Note 3' screen after getting a 'Invalid: ext4 image' or 'Repartioning failed' errors while installing 4.4.2 OFFICIAL (Single File ROM) via Odin.
Binary: Custom
Knox: 0x1
Method:​
In Odin mode
1. Flash the latest cf-autoroot (Kitkat support) [http://download.chainfire.eu/352/CF-...x-smn9005.zip]
2. Flash the Chenglu's latest CWM - 6.0.4.6 (the one that supports KitKat) http://forum.xda-developers.com/show....php?t=2454079
Download Sweet Rom and place it in ExtSDcard (http://forum.xda-developers.com/show....php?t=2487425)
I tried external sd-card with various format and could not install the ROM. After format my SD Card to FAT32, the ROM can be installed.
On Device
1. Boot in to Recovery mode by Volume up + Home + Power
2. Wipe Factory reset / Dalvik Cache
3. Format /System (under "mount and storage" menu) [IMPORTANT STEP]
4. Install Rom from SD Card
5. Say your prayer. You'll need it. (The installation could take sometimes. If the device screen shows Samsung boot animation, you're half way there)

How is that going to take away the udc start?

I have UDC Start in Odin/Download mode... It hasn't affected my flashing of custom ROMs nor Stock, everyone on KK has it.

Ok, but why if i try to install a previous version of TW rom 4.3 i get a massive fail?
But all the rest works?
Thanx in regards.

FdeKlerk said:
Ok, but why if i try to install a previous version of TW rom 4.3 i get a massive fail?
But all the rest works?
Thanx in regards.
Click to expand...
Click to collapse
Because you are locked into the new Bootloader (NA6) and it's unable to downgrade

So I am guessing there is no way to downgrade the boot-loader without unlocking it?

FdeKlerk said:
So I am guessing there is no way to downgrade the boot-loader without unlocking it?
Click to expand...
Click to collapse
There's no way full stop. Samsung have blocked downgrades within the bootloader itself.

Wow now that's some sort of a problem.
My 4.4.2 works but i love xposed modules to make everything transparent and as of yet kitkat does not support that.
And now i a stuck on 4.4.2..
But thanx for the assist.:good:

Same Problem with E330s
ManuH8 said:
I'm installing the new firmware but i had an issue with odin...
I flashed again 4.4.2 but in download mode, the last line you can see " UDC START" in colour red... Is this normal? I think the phone works good, but i don't know why put on this...
Anyone have this new line??
Click to expand...
Click to collapse
Hi. I have a unrooted SHV-E330 (I9506 to some) I was running the unrooted firmware and updating with Kies up until yesterday when the update to came up. I ran it as with every other update however on self rebooting the phone now goes to ODIN MODE (in red) and UDC Start (in red) i'm a root virgin and was happy with the phone running as it was AnTU TU score 36118 with the Korean bloatware running in the background. From what I have picked up after 4.3 firmware update to 4.4.2 there is no going back. I tired to root with earlier versions of firmware but get fail every time. I Picked up a zip SKT-E330SKSUCNA7 wich goes as far as checking the MD5 file successfully in Odin 3 v3.09. everywhere I look on the web it states the com box should be yellow however mine is blue.
After MD5 successful I get leave CS. I click start I get 'Get PIT for mapping. There id no PIT partion followed by a red box and the'FAIL!' box with 'all threads completed Failed 1.
I have never rooted a phone and a buff mentioned that I will not regret it. I figure thart i'm doing something wrong as there was no PIT file with the firmware.
On first trying a firmware recovery in Kies because the phone is stuck In ODIN MODE it will not recognise the phone even though the USB drivers are installed.
If their is a person out there that could talk me through rooting trough the stuck ODIN MODE I would appreciate contact.
I gather that I have no choice but to try ODIN MODE on phone as that's where the phone is stuck. Removing battery etc has been tried to death.

summan971 said:
Hi. I have a unrooted SHV-E330 (I9506 to some) I was running the unrooted firmware and updating with Kies up until yesterday when the update to came up. I ran it as with every other update however on self rebooting the phone now goes to ODIN MODE (in red) and UDC Start (in red) i'm a root virgin and was happy with the phone running as it was AnTU TU score 36118 with the Korean bloatware running in the background. From what I have picked up after 4.3 firmware update to 4.4.2 there is no going back. I tired to root with earlier versions of firmware but get fail every time. I Picked up a zip SKT-E330SKSUCNA7 wich goes as far as checking the MD5 file successfully in Odin 3 v3.09. everywhere I look on the web it states the com box should be yellow however mine is blue.
After MD5 successful I get leave CS. I click start I get 'Get PIT for mapping. There id no PIT partion followed by a red box and the'FAIL!' box with 'all threads completed Failed 1.
I have never rooted a phone and a buff mentioned that I will not regret it. I figure thart i'm doing something wrong as there was no PIT file with the firmware.
On first trying a firmware recovery in Kies because the phone is stuck In ODIN MODE it will not recognise the phone even though the USB drivers are installed.
If their is a person out there that could talk me through rooting trough the stuck ODIN MODE I would appreciate contact.
I gather that I have no choice but to try ODIN MODE on phone as that's where the phone is stuck. Removing battery etc has been tried to death.
Click to expand...
Click to collapse
Your phone does not have a pit file on it. Odin downloads the pit file from the phone to make sure that all the partitions are correctly flashed.
Try ticking the 'Re-partition' box in odin while flashing. Though I don't really think it will help, because your single file ROM most probably does not contain the pit.
Your best bet is to find somebody else with the same model as you, and get a pit from them.
PS- You are in the wrong forums.

[COLOR=[/COLOR]
feralfire said:
your phone does not have a pit file on it. Odin downloads the pit file from the phone to make sure that all the partitions are correctly flashed.
Try ticking the 're-partition' box in odin while flashing. Though i don't really think it will help, because your single file rom most probably does not contain the pit.
Your best bet is to find somebody else with the same model as you, and get a pit from them.
Ps- you are in the wrong forums.
Click to expand...
Click to collapse
do not tick re-partition without having a pit file, you will get a brick.
Feralfire, you just broke the first law of flashing with ODIN... If you don't know what to do then don't say anything...

Thanks for caring XDA developers - i fixed it
FeralFire said:
Your phone does not have a pit file on it. Odin downloads the pit file from the phone to make sure that all the partitions are correctly flashed.
Try ticking the 'Re-partition' box in odin while flashing. Though I don't really think it will help, because your single file ROM most probably does not contain the pit.
Your best bet is to find somebody else with the same model as you, and get a pit from them.
PS- You are in the wrong forums.
Click to expand...
Click to collapse
Hey thanks for the response the same day I managed to fix the problem a hour ago after 24 hours of banging my head on a wall.
I uninstalled all software including Odin remembering that ODIN MODE was the only option. most of the Boot Operating system was in Korean.
I followed a you tube guide from another root and noticed that although ODIN MODE and UDC start are new (according to other forums) that the other information insinuated that the screen I was looking at was also the download mode.
I reinstalled Kies and rather than asking me for the emergency recovery code it reset and was asking for the Model and serial number. After which it stated it could not recover the device only reinstall the stock firmware. I selected OK. the phone came back to life and reinstalled all data from cloud.
now on 4.4.2 and still thinking about rooting
however I must warn anyone that comes across the unlocker website that states its mod allows for E330S root. that clockwork mod does not cater for E330S.

ultramag69 said:
[COLOR=[/COLOR]
do not tick re-partition without having a pit file, you will get a brick.
Feralfire, you just broke the first law of flashing with ODIN... If you don't know what to do then don't say anything...
Click to expand...
Click to collapse
Au contraire, I have done a lot of research on pit file and played around a lot. Check out my threads.
If you tick re-partition without having a pit, it just gives you an error. Maybe in the olden days, it might have been an issue (I haven't always been a Samsung guy), but definitely not now.

FeralFire said:
Au contraire, I have done a lot of research on pit file and played around a lot. Check out my threads.
If you tick re-partition without having a pit, it just gives you an error. Maybe in the olden days, it might have been an issue (I haven't always been a Samsung guy), but definitely not now.
Click to expand...
Click to collapse
If so, then make sure they know which version of ODIN to use as this is the fastest way to kill a phone I know...
Right from the very first this was a cardinal sin but then you didn't have a phone anymore or much sympathy either... But to tell a noob to do this was in effect saying "put your phone in front of a steamroller, it'll be ok after its gone over it a couple of times"...

ultramag69 said:
If so, then make sure they know which version of ODIN to use as this is the fastest way to kill a phone I know...
Right from the very first this was a cardinal sin but then you didn't have a phone anymore or much sympathy either... But to tell a noob to do this was in effect saying "put your phone in front of a steamroller, it'll be ok after its gone over it a couple of times"...
Click to expand...
Click to collapse
He was using 3.09. Don't overcomplicate things.
But anyway, I apologize for making people put their phones in front of 20 ton vehicles.

re Pit File
FeralFire said:
Your phone does not have a pit file on it. Odin downloads the pit file from the phone to make sure that all the partitions are correctly flashed.
Try ticking the 'Re-partition' box in odin while flashing. Though I don't really think it will help, because your single file ROM most probably does not contain the pit.
Your best bet is to find somebody else with the same model as you, and get a pit from them.
PS- You are in the wrong forums.
Click to expand...
Click to collapse
I found this KS01LTE_KOR_SKT_32G.pit and ran it in Odin running download mode and it worked. It appears there are several Korean versions of the right ROM and unless the right rom is used flash in odin does not work.
I'm starting to sound like i know what i'm talking about!

summan971 said:
I found this KS01LTE_KOR_SKT_32G.pit and ran it in Odin running download mode and it worked. It appears there are several Korean versions of the right ROM and unless the right rom is used flash in odin does not work.
I'm starting to sound like i know what i'm talking about!
Click to expand...
Click to collapse
The different ROMs must have different pits. That would explain why only some specific ones work.
Anyway, congratulations.

[Q] Galaxy S5 Bootloop

Before marking this as a duplicate, please note that I've gone through almost every thread on this and different possibilities, but nothing had worked.
This morning, I rooted my AT&T Samsung Galaxy S5 (US) using towelroot. The root was successful. Next I downloaded Superuser from the Play Store (not the Chainfire one). It said it needed to update something using recovery mode, but it failed with an error. So, I ignored it and continued using the phone. Next, I downloaded the Google Now Launcher from Android L, to get Material Design. I installed Sliding Explorer from the Play Store to access root files. I also got a simple text edit app. To get Material Design, I needed to change ro.build.version.codename=REL to =L in build.prop. When I did and tried to save, it said access denied, so I changed permissions (oops!) to allow the file to be saved. Still didn't work for some reason so I saved the file as build.prop somewhere else and cut and pasted it in. Then, I rebooted my device and it got stuck on the boot screen with the Samsung Galaxy S5 logo with powered by Android beneath it.
What I've tried:
- I have wiped data, the cached, but there is no advanced option for me to wipe dalvik in the stock recovery for the Galaxy S5.
- When I try to use ADB, my device shows up as sideload and sideloading a ROM goes to 100% but ends up in an error. I cannot run ADB Shell, which ends in error:close.
- Using Odinv3 Build 3.09, I think, gets stuck on connecting to the phone, while Odinv3 Build 1.85, I think, gets fails at Complete(Write) error after something to do with NAND write.
My device drivers are all updated, and I've tried different USB ports, even different PC's. Nothing works. How can I fix this? Thanks!

I am allergic to posts that use Urgent in the title. Obviously you'd like to regain use of your phone ASAP. But how that makes your post more important than someone else's is a mystery. Nevertheless, I'm sure that someone else will be along soon to help you.
If you don't find something more expedient, the most reliable solution for a non-bricked phone is to Odin flash a full, stock firmware image that matches your baseband version.
.

fffft said:
I am allergic to posts that use Urgent in the title. Obviously you'd like to regain use of your phone ASAP. But how that makes your post more important than someone else's is a mystery. Nevertheless, I'm sure that someone else will be along soon to help you.
If you don't find something more expedient, the most reliable solution for a non-bricked phone is to Odin flash a full, stock firmware image that matches your baseband version.
.
Click to expand...
Click to collapse
Problem is, as I said, Odin has errors every time I try to flash, different ports and even different PC's. Maybe I'm not doing it correctly? And I'm sure I get the correct version.
Sorry for the Urgent ?.

tforkan99 said:
Problem is, as I said, Odin has errors every time I try to flash, different ports and even different PC's. Maybe I'm not doing it correctly? And I'm sure I get the correct version.
Sorry for the Urgent ?.
Click to expand...
Click to collapse
You've made some ill advised mods. Now we need more information. Post as many details as you can so that we can spot were the exact problem is.
Paste the exact error from both Odin vetsions here.
Is this originally an ATT phone?
Regular model (i.e. not the special unlocked Developer version)?
Do you know if it the new re-activation lock feature is enabled?
Do you know the phone's baseband /exact firmware version?
Do you have a recent backup?
Are you still able to boot to recovery mode (vol up + home + power)?
Did you ever successfully use Odin with this phone before the bootloop happened?
Perhaps you could remove the Urgent from your title? Edit /Delete > Go Advanced
.

fffft said:
You've made some ill advised mods. Now we need more information. Post as many details as you can so that we can spot were the exact problem is.
Paste the exact error from both Odin vetsions here.
Is this originally an ATT phone?
Regular model (i.e. not the special unlocked Developer version)?
Do you know if it the new re-activation lock feature is enabled?
Do you know the phone's baseband /exact firmware version?
Do you have a recent backup?
Are you still able to boot to recovery mode (vol up + home + power)?
Did you ever successfully use Odin with this phone before the bootloop happened?
Perhaps you could remove the Urgent from your title? Edit /Delete > Go Advanced
.
Click to expand...
Click to collapse
Odin3 v3.09: Stuck on "SetupConnection"
Odin3 v1.85:
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Yes, originally ATT
Regular model
Don't know about re-activation lock
I think the firmware version is the problem. The last update was the one from ATT that added Yellowpages and Lookout in May. Don't know version. I've been download an April build so maybe that's why there is an error. My phone says "SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1" which apparently occurs when downgrading. Maybe if I can get an updated ROM, I can use Odin? And I've seen suggestions to use Odin3 v3.04, but same error with the April build. I can't find the May build anywhere.
Maybe this will work?:http://forum.xda-developers.com/showthread.php?t=2737257 But it's .zip and I can't flash it with Odin.
I have a Kies backup, that's it. This always happens to me . I'm always too lazy to back up my devices.....
Yes recovery mode works and I can get into ADB Sideload.
Nope, never used Odin before. never tried.

I may have something here!
http://forum.xda-developers.com/showthread.php?t=2785185
My firmware is G900AUCU2AND3.
I will update after following the guide.

It works! The only thread that I needed in the world and I couldn't find until after I wiped my device....
Device successfully restored to functionality.

tforkan99 said:
Device successfully restored to functionality.
Click to expand...
Click to collapse
Great to hear.
As I commented at the outset, all you needed to do was restore a full, stock firmware image to recover. Ideally one that matches your existing baseband. Which is essentially what that thread did. Collected all of the pieces to do a 100% reversion to stock.
I've written similar posts for Verizon and TMobile. Was in fact just rewriting the Verizon one for you when you updated the thread. Anyway, good work. Give yourself a pat on that back and promise to make more backups this time.
.

Ego?
fffft said:
I am allergic to posts that use Urgent in the title. Obviously you'd like to regain use of your phone ASAP. But how that makes your post more important than someone else's is a mystery. Nevertheless, I'm sure that someone else will be along soon to help you.
If you don't find something more expedient, the most reliable solution for a non-bricked phone is to Odin flash a full, stock firmware image that matches your baseband version.
.
Click to expand...
Click to collapse
I'm allergic to egocentric attitudes when it comes to answers in a Q & A thread.

tforkan99 said:
It works! The only thread that I needed in the world and I couldn't find until after I wiped my device....
Device successfully restored to functionality.
Click to expand...
Click to collapse
Happy to hear it that worked out for you!

Flash problem? PIT? Bricked

Hi all,
Over the weekend my phone died in my hands, it was on charge (low battery), turned off and wouldn't turn on again. It just displays the Samsung Galaxy Note logo and never gets passed that.
I tried to get into recovery CWM is installed) and I get MMC: mmc_read fail and Moviand Checksum Confirmation Fail.
I've tried to upload a PIT as Odin reports that there is no PIT partition - I'm using a few .pits I've found on the forum and am trying to use these (I'll attach one) and also using the ROM from SamMobile - I believe this is the correct one. My sim is Everything Everywhere but the phone is unlocked so I picked the United Kingdom one. N9005XXUGNG1_N9005OXAGNJ3_N9005XXUGNG1_HOME.tar
However when I add the PIT to Odin and the tar to "PDA" in Odin I get "There is no PIT partition":
and on the screen itself in Download Mode gives these errors:
MMC: mmc_read fail
ODIN: flash read failure
SECURE CHECK FAIL: PIT
What am I doing wrong here? Could the hardware have failed... I'm not even that bothered about the phone itself, I just really want to try and get the data off it - but don't think there is a way to do this without booting into a ROM or at least recovery to use ADB.
Any help would be appreciated!

I know how you feel
oli356 said:
Hi all,
Over the weekend my phone died in my hands, it was on charge (low battery), turned off and wouldn't turn on again. It just displays the Samsung Galaxy Note logo and never gets passed that.
I tried to get into recovery CWM is installed) and I get MMC: mmc_read fail and Moviand Checksum Confirmation Fail.
I've tried to upload a PIT as Odin reports that there is no PIT partition - I'm using a few .pits I've found on the forum and am trying to use these (I'll attach one) and also using the ROM from SamMobile - I believe this is the correct one. My sim is Everything Everywhere but the phone is unlocked so I picked the United Kingdom one. N9005XXUGNG1_N9005OXAGNJ3_N9005XXUGNG1_HOME.tar
However when I add the PIT to Odin and the tar to "PDA" in Odin I get "There is no PIT partition":
and on the screen itself in Recovery Mode gives these errors:
MMC: mmc_read fail
ODIN: flash read failure
SECURE CHECK FAIL: PIT
What am I doing wrong here? Could the hardware have failed... I'm not even that bothered about the phone itself, I just really want to try and get the data off it - but don't think there is a way to do this without booting into a ROM or at least recovery to use ADB.
Any help would be appreciated!
Click to expand...
Click to collapse
Hi Oli,
I've had the same issue a few months ago on my pretty much brand new N3, Canadian. I tried a few "PIT" files as well, with no success! My solution, can't recommend to you, was to install i.e. Slimkat ROM or CM11. I'm never concerned about data partition as I can always drop my MP3s once I'm able to boot into the OS. All important ROMs, Gapps and Apps are on EXT SD card .
So, that was my last resort to bring the N3 back to life. I have flashed a few TW based ROMs after, and it was all well.
But honestly, (someone else confirm this) you can "dirty" flash AOSP based ROM without wiping data partition. In other words when you think about what I did, that's what fixed the problem. I wish you nothing but good luck!
Are you even able to get to CWM recovery point? I do NOT remember if mine was broken, TWRP, that is.
Kind regards,
Sonny B.

Hi Sonny B
Unfortunately I can't boot into CWM recovery as I get this:
MMC: mmc_read fail and Moviand Checksum Confirmation Fail.
As far as I know though right CM11/Slimkat can't be installed from Odin so I would need to be in TWRP or CWM which I can't get to
I guess I need to know why I can't push the PIT file from Odin... if this works then hopefully I can install CWM recovery and get somewhere.
Thanks

My, My...
oli356 said:
Hi Sonny B
Unfortunately I can't boot into CWM recovery as I get this:
MMC: mmc_read fail and Moviand Checksum Confirmation Fail.
As far as I know though right CM11/Slimkat can't be installed from Odin so I would need to be in TWRP or CWM which I can't get to
I guess I need to know why I can't push the PIT file from Odin... if this works then hopefully I can install CWM recovery and get somewhere.
Thanks
Click to expand...
Click to collapse
Oli, oli...
If I could just remember what I've done in my case. I don't think I ever received that many "serious" error messages when my phone was down. I honestly think that my recovery was not broken, therefore I was able to install custom ROM, when original stock ROM was not working for me!
I'll definitely keep my eye on this thread. Don't give up please! I hope seasoned kanger can chime in here with a solution.
Good luck,
Sonny B.

sonny_b_bih said:
Oli, oli...
If I could just remember what I've done in my case. I don't think I ever received that many "serious" error messages when my phone was down. I honestly think that my recovery was not broken, therefore I was able to install custom ROM, when original stock ROM was not working for me!
I'll definitely keep my eye on this thread. Don't give up please! I hope seasoned kanger can chime in here with a solution.
Good luck,
Sonny B.
Click to expand...
Click to collapse
Given up for now - just getting no where and out of ideas on how to get this to work.
Can't flash a ROM because no PIT is found but then I can't re-partition with the PIT either =/

After trying more PIT files and ROMS from different sources I have well and truly given up. I've requested the phone to be recycle so at least I can get some money for it

I used to the same problem this summer you should try reflashing a stock rom with odin

o-ellinas said:
I used to the same problem this summer you should try reflashing a stock rom with odin
Click to expand...
Click to collapse
Tried a few now from Samsmobile and other sites but just get the message about no PIT partition.

http://www.galaxynote3update.com/fi...-the-unbrick-and-recovery-guide-just-for-you/
Check this out

Thanks but its unfortunately just the same as every other help guide They all seem to suggest that if you can get into download mode then it's possible to fix the phone but after trying so many different stock ROMs from different sources and using the PIT file.. it's just not happy.
Reluctant to recycle the phone though based on the fact that I keep reading that it can be fixed...

Need help on unfamiliar error screen. Image provided.

Just got the Note3 from a online seller who seems to be legit but when the phone was received via the mail, it didn't work as expected.
I've had some experience with android ROMs and rooting but those are mostly for the other phones, this is the first Samsung phone i got. Could you guys help and advise what to do to resolve this error?
I've actually downloaded Kies3 and use the emergency recover thing, but most of the times it couldn't detect the phone connection.
And on the rare occasion that it does detect something, it says that the model is incompatible with Kies3. Tried it with the old Kies too, but didn't work as well!
UPDATE <21_03_2015><16_54_09_524>____________________________________________________________
I just tried flashing lollipop from http://forum.xda-developers.com/galaxy-note-3/general/finally-official-5-0-firmware-galaxy-t3029557
It didn't work, with and without the PIT file.
Before flashing
first_flash_no_pit
first_boot_after_first_flash
Second_flash_no_pit
3rd_flash_with_pit

I think that this error appears when a ROM isn't flashed properly to the device. So a possible solution might be a factory reset in recovery and a clean ROM flash with Odin. You just need to download a ROM for your device model - SM-N9005 from sammobile or samsung-updates.

3XTR3M1ST said:
Just got the Note3 from a online seller who seems to be legit but when the phone was received via the mail, it didn't work as expected.
I've had some experience with android ROMs and rooting but those are mostly for the other phones, this is the first Samsung phone i got. Could you guys help and advise what to do to resolve this error?
I've actually downloaded Kies3 and use the emergency recover thing, but most of the times it couldn't detect the phone connection.
And on the rare occasion that it does detect something, it says that the model is incompatible with Kies3. Tried it with the old Kies too, but didn't work as well!
Click to expand...
Click to collapse
Download an official firmware from sammobile and use odin to flash. It's all on their site
Sent from my SM-N9005 using XDA Free mobile app

Is Odin a entirely different piece of software to kies?
Also would you this to be soft brick and reason to demand for compensation from the seller?

intervall said:
I think that this error appears when a ROM isn't flashed properly to the device. So a possible solution might be a factory reset in recovery and a clean ROM flash with Odin. You just need to download a ROM for your device model - SM-N9005 from sammobile or samsung-updates.
Click to expand...
Click to collapse
Yes this appears when a rom isn't flashed properly, Or the user has manually soft bricked the device.
st3chn0 said:
Download an official firmware from sammobile and use odin to flash. It's all on their site
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
I wouldn't take this advice as you bought a phone that is soft bricked with knox tripped (0x1)
try and return it before you attempt to fix it.
3XTR3M1ST said:
Just got the Note3 from a online seller who seems to be legit but when the phone was received via the mail, it didn't work as expected.
I've had some experience with android ROMs and rooting but those are mostly for the other phones, this is the first Samsung phone i got. Could you guys help and advise what to do to resolve this error?
I've actually downloaded Kies3 and use the emergency recover thing, but most of the times it couldn't detect the phone connection.
And on the rare occasion that it does detect something, it says that the model is incompatible with Kies3. Tried it with the old Kies too, but didn't work as well!
Click to expand...
Click to collapse
3XTR3M1ST said:
Is Odin a entirely different piece of software to kies?
Also would you this to be soft brick and reason to demand for compensation from the seller?
Click to expand...
Click to collapse
It looks like your knox is 0x1 and the system status is 'custom' but i can't really tell as the quality of the pictures isn't good enough.
This means that the phone has been used before and rooted, then a wrong flash or simply just deleting a few system files so it doesn't boot to get that screen to show up instead.
If there is nothing wrong with the hardware, Odin should fix this easily.. but i wouldn't trust it as your imei could of been changed.. many things could of been tampered with.
Also you mention that kies doesn't detect the phone properly, only sometimes. This could be your pc but it is likely a hardware problem with the phone judging by how you recieved it with knox tripped (0x1).
As it has been sold in this condition i can only assume that it has been tampered with. Why else would the seller sell a soft bricked device ?
Was it advertised as new or used?
Return it and get your money back as soon as possible is all i can suggest, good luck.

1. If its possible for him to return to the seller then yes but he can't to samsung. Due to knox being tripped. If he does its just basically a 50/50 chance
2. This nothing to do with soft brick. Such thing as a soft brick doesn't really exist.
3. Using odin to flash any official firmware. Is not bad advice.
Sent from my SM-N9005 using XDA Free mobile app

celderic said:
Yes this appears when a rom isn't flashed properly, Or the user has manually soft bricked the device.
I wouldn't take this advice as you bought a phone that is soft bricked with knox tripped (0x1)
try and return it before you attempt to fix it.
It looks like your knox is 0x1 and the system status is 'custom' but i can't really tell as the quality of the pictures isn't good enough.
This means that the phone has been used before and rooted, then a wrong flash or simply just deleting a few system files so it doesn't boot to get that screen to show up instead.
If there is nothing wrong with the hardware, Odin should fix this easily.. but i wouldn't trust it as your imei could of been changed.. many things could of been tampered with.
Also you mention that kies doesn't detect the phone properly, only sometimes. This could be your pc but it is likely a hardware problem with the phone judging by how you recieved it with knox tripped (0x1).
As it has been sold in this condition i can only assume that it has been tampered with. Why else would the seller sell a soft bricked device ?
Was it advertised as new or used?
Return it and get your money back as soon as possible is all i can suggest, good luck.
Click to expand...
Click to collapse
The seller is not responding to my questions, so I think the next best bet to attempt and fix it myself. Am I right to think that flashing an official firmware is the best option? What could go wrong if the imei have been changed?
Also, you just got me curious about the knox thing. Where do you suggest I look at for a comprehensive elaboration of the error codes?
http://postimg.org/image/rorg1p21n/

Flashing firmwate from sammobile will not trigger knox so as suggested earlier download and flash a firmware for your phone

st3chn0 said:
2. This nothing to do with soft brick. Such thing as a soft brick doesn't really exist.
Click to expand...
Click to collapse
This is a softbrick, if the hardware is fine then you should be able to fix it in 10mins by flashing a stock rom, but as the seller has sold it in this state then i assume it is softbricked for a reason so you can't test the device for example.
cryostasis25 said:
Flashing firmwate from sammobile will not trigger knox so as suggested earlier download and flash a firmware for your phone
Click to expand...
Click to collapse
But his knox is already tripped.. he bought a phone with knox 0x1 that's why i suggested returning it.
3XTR3M1ST said:
The seller is not responding to my questions, so I think the next best bet to attempt and fix it myself. Am I right to think that flashing an official firmware is the best option? What could go wrong if the imei have been changed?
Also, you just got me curious about the knox thing. Where do you suggest I look at for a comprehensive elaboration of the error codes?
http://postimg.org/image/rorg1p21n/
Click to expand...
Click to collapse
If the seller is not responding, then it points to them tampering with the device before selling it. Where did you buy it from, i would ring your bank as soon as possible.
Download the latest n9005 rom from sammobile and flash it through odin if you want to try and fix it, shouldn't really matter what csc as your knox is already tripped anyway so you can't recieve OTA updates or warranty from samsung anymore, mine is a BTU device but i have used many XEO roms.
If the phone isn't connecting to the computer properly like you say, then it's probably best to leave it. As this could result in the connection failing when it is flashing the bootloader or something. But if it works fine, then there should be no problems.
Here is something you could try, start up odin (i use v3.09), close all processes relating to kies, boot the device into download mode, that screen you provided pictures of. Plug the phone in and wait a few minutes to check the connection is stable, move the cable around to make sure the socket and cable are okay. You will see it come up on the top left in odin after windows has installed the drivers.
If this all works fine then flashing a stock rom should fix the device if the hardware is okay.

Just a quick question. From what site did you buy the phone and how did you pay for the phone?
Sent from my SM-N9005 using XDA Free mobile app

Where is a reliable source to download the official firmwares? I cant find it on the samsung site.
Tried http://www.samsungupdate.com/how-to/download-firmware but the file sizes are different on either filehost mirrors and it seems shady.

www.sammobile.com/firmwares/

I just tried flashing lollipop from http://forum.xda-developers.com/galaxy-note-3/general/finally-official-5-0-firmware-galaxy-t3029557
It didn't work, with and without the PIT file.
Before flashing
first_flash_no_pit
first_boot_after_first_flash
Second_flash_no_pit
3rd_flash_with_pit

3XTR3M1ST said:
I just tried flashing lollipop from http://forum.xda-developers.com/galaxy-note-3/general/finally-official-5-0-firmware-galaxy-t3029557
It didn't work, with and without the PIT file.
Click to expand...
Click to collapse
1. Try flashing the new bootloader and modem first: http://forum.xda-developers.com/galaxy-note-3/general/odin-flashable-lollipop-bootloader-t3058101
2. If flashing modem and bootloader succeeded, try flashing the whole firmware again.
From what I learned from this http://forum.xda-developers.com/showthread.php?p=47287747#post47287747 thread, "invalid ext4 image" errors occur when bootloader is wrong.
Actually, do you have any info with what firmware was this phone last? I think I might have encountered another thread (don't remember it, though) which says that these exact problems occur when trying to upgrade from Jelly Bean 4.3 to Lollipop directly.

sirobelec said:
1. Try flashing the new bootloader and modem first: http://forum.xda-developers.com/galaxy-note-3/general/odin-flashable-lollipop-bootloader-t3058101
2. If flashing modem and bootloader succeeded, try flashing the whole firmware again.
From what I learned from this http://forum.xda-developers.com/showthread.php?p=47287747#post47287747 thread, "invalid ext4 image" errors occur when bootloader is wrong.
Actually, do you have any info with what firmware was this phone last? I think I might have encountered another thread (don't remember it, though) which says that these exact problems occur when trying to upgrade from Jelly Bean 4.3 to Lollipop directly.
Click to expand...
Click to collapse
Thanks for the suggestion. I'll give it a try after a little more research.
I have no idea what the phone was before, or what the seller did to it since he's just not responding anymore.

So I tried flashing the new bootloader as suggested, it seem to have worked to some extent, but then I screw it up again by pulling out the cable before seeing "PASS!". What now?
http://forum.xda-developers.com/showpost.php?p=59616074&postcount=16 said:
iketil said:
Hi the file size should be 58 041 KB
From what I can see from you ODIN log, ODIN has "done its thing"
If you did not uncheck the auto reboot tab, the phone should now be rebooting.
And bootloader and Modem should be updated when its booted up.
Are you still stuck at the "Samsung GALAXY Note3 SM-9005" screen ?
Click to expand...
Click to collapse
I'm still stuck on the "Samsung GALAXY Note3 SM-9005" screen. However I do think that the "hlte_lollipop_bootloader_modem.tar.md5" has "done its thing". I was previously unable to get to the recovery, but I was able to get to this <3e>recovery after flashing.
Also managed to see some logs of "i'm not sure what it is" before the phone went blank. I presume its due to battery going flat.
Later, I tried putting TWRP on it. Starting with "twrp-2.8.3.0-hlte-4.3.img.tar". But being a novice odin user I mistakenly unpluged the phone when odin is showing "RESET!". Then I tried going into recovery using VOLUP+HOME+POWER, and got this screen instead. I'm not sure if removing the phone before "PASS!" in odin could have caused this? Subsequently I tried flashing "twrp-2.7.0.3-hlte-4.3.img.tar" and
"twrp-2.7.2.0-hlte-4.3.img.tar", which resulted in the same error screen about SEANDROID.
I also noticed it increased my KNOX counter?
This is before and after.
Next I tried flashing ""hlte_lollipop_bootloader_modem.tar.md5" again hoping it would fix it. It didnt work. Silly me, this flash does not have a recovery image in it does it?
Anyway, now I dont have a working recover and is still stuck on the "Samsung GALAXY Note3 SM-9005". Thankfully odin mode still work. What should I do next? Please see this thread below for a little background to my problem. Thank you.
http://forum.xda-developers.com/galaxy-note-3/general/help-unfamiliar-error-screen-image-t3059227
Click to expand...
Click to collapse

HORRY SHET!!
I think my phone is asian! I just flashed the latest taiwan firmware released (N9005ZSUGOC3_N9005OZSGOC3_BRI) after flashing the new bootloader and everything works now!
I'm not sure what actually made it work since this is the first taiwan firmware I tried (its all XEO and BOB previously), but big thanks to everyone who helped!

[Q] Bricked Galaxy S4, pls help (everything tried)

Hi all ! Hope sb help me with this...
I updated my S4 i9500 to android 5.0.1 lollipop (XXUHOAA ) about 8 months ago. No problem untill 2 days ago my phone turned off itself then went to bootloop.
Now it just shows the s4 logo then restarts again all the time. SOMETIMES it turns on but after 4 or 5 seconds again turns off (not able to do anything during 4 seconds)
I CAN NOT access recovery mode. The recovery mode became a black screen and not able to wipe/factory reset.
Before I bring it to serviceman I want to see if u can help me with this(It's warranty is voided now)
WHAT I HAVE TRIED RECENTLY:
I tried to flash 4 different Roms using 3 different odin versions but no success
[flashing roms get the error "complete(write) operation failed" and by using the suitable PIT file I get the error "repartition operation failed"]
Also tried flashing 5-files-firmware (with pit file) but again "repartition operation failed"
I used 3 usb cables including the original one
I did all of those steps using 2 different laptops and also different ports
I'm sure the samsung drivers are installed[odin port comes blue or yellow]
I used SkipSoft ToolKit and one click unsoftbrick softwares but no success
Also used adb to factory reset phone but it doesn't detect my phone[ seems it needs to be turned on]
I removed simcard, format extra sd card, remove battery for a long time and.....
Is there anything I haven't tried yet?? Can somone help ? I appreciate any suggestion,Thanks
[[Sorry my English]]

Try flashing a custom recovery and then factory reset?

KennethHau said:
Try flashing a custom recovery and then factory reset?
Click to expand...
Click to collapse
Hi and Thanks for replying, Well I downloaded some CWM/TWRP recoveries but the problem is that I can't flash anything with Odin. I always get the error:
<ID:0/007>NAND Write Start!!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed
And this error is the same while flashing anything like Rom,Recovery,philz_touch and even auto root files.
I'm so confused

Have you tried downloading stock firmware from sammobile for your model and carrier and installing? If that doesn't work you may have a serious issue.
Sent from my unknown using Tapatalk
---------- Post added at 01:12 AM ---------- Previous post was at 01:10 AM ----------
alimtale said:
Hi and Thanks for replying, Well I downloaded some CWM/TWRP recoveries but the problem is that I can't flash anything with Odin. I always get the error:
<ID:0/007>NAND Write Start!!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed
And this error is the same while flashing anything like Rom,Recovery,philz_touch and even auto root files.
I'm so confused
Click to expand...
Click to collapse
Is the Odin version the proper one for your phone?
Sent from my unknown using Tapatalk

Jchef said:
Have you tried downloading stock firmware from sammobile for your model and carrier and installing? If that doesn't work you may have a serious issue.
Is the Odin version the proper one for your phone?
Click to expand...
Click to collapse
Of course I did. I even downloaded different android versions (5.0.1,4.4.2,4.2.2) But non of them flashed
I remember I used Odin 3.0.9 to upgrade my S4 to 5.0.1 months ago but I tried different Odin versions (1.85,3.0.7,3.0.9) for in case.
Unfortunately,I face an error all the time that is related to Nand write corruption .

If you have flashed 4.2.2 it's a brick ,for sure.

ludoke said:
If you have flashed 4.2.2 it's a brick ,for sure.
Click to expand...
Click to collapse
No it didn't flashed. After I got error while flashing 5.0.1 firmware I tried other versions to see if it works. But the error is the same.

alimtale said:
No it didn't flashed. After I got error while flashing 5.0.1 firmware I tried other versions to see if it works. But the error is the same.
Click to expand...
Click to collapse
Even trying to flash 4.2.2 will result in a brick,so it's normal that it didn't work

ludoke said:
Even trying to flash 4.2.2 will result in a brick,so it's normal that it didn't work
Click to expand...
Click to collapse
My phone turned off itself. I tried flashing firmware after the problem occurred. I don't think the problem is because of flashing 4.2.2

Deleted

Maybe it's the battery

ludoke said:
Even trying to flash 4.2.2 will result in a brick,so it's normal that it didn't work
Click to expand...
Click to collapse
This is incorrect. You don't brick your phone when you try to flash 4.2.2. That's simply not possible.

dorian2kx said:
Maybe it's the battery
Click to expand...
Click to collapse
I have 2 batteries...both of them same result (bootloop)

alimtale said:
I have 2 batteries...both of them same result (bootloop)
Click to expand...
Click to collapse
Does it reboot when you are in download mode? If so, then it's your power button that is faulty. Either try to wiggle it loose or replace it.
If it doesn't reboot while in download mode then you have some other hardware damage. Probably your motherboard is damaged.

Lennyz1988 said:
Does it reboot when you are in download mode? If so, then it's your power button that is faulty. Either try to wiggle it loose or replace it.
If it doesn't reboot while in download mode then you have some other hardware damage. Probably your motherboard is damaged.
Click to expand...
Click to collapse
No it doesn't reboot while download mode.Maybe hardware damage but it sometimes turns on and I can access applications and settings for a short time (about 5 seconds)
I have rooted my device when upgraded to 5.0.1. And recently I unchecked "enable superuser" in the superuser app.( I have done this before many times without problem)
I guess there is a problem related to that because when my phone turned on I tried to check the enable option in the superuser but as soon as I touch the check box my phone turns off instantly

If your phone goes into download mode. I don't think it is bricked.
Sent from my unknown using Tapatalk

You cannot fix your phone by Odin because of the Secure Download enabled bootloader.
You will have to pay a JTAG repair service.
Android 5.0.1 is a crap, which replaces your bootloader with a secure-download featured one,
so you won't ever be able to have the control of your phone again!

@Killnolife: A little melodramatic? It's not a locked bootloader so he still has total control over the device. Come back with an AT&T or Verizon S4 and then complain about having no control.
OP, Lennyz1988's advice is sound. Follow it.

Well I got tired of trying to flash my device with Odin. Always error... The Only choice I have is to take the phone to the service center and see what they can do...I'll share the result...

I took my phone to service centers for repair, they said the hard is damaged and it takes about 100$ to replace that:crying: if I pay that much I'm not sure it wont damage again
So my phone is dead now on my table and I gonna buy a new phone (maybe s5 or z3). Hope no one experience this situation