Database Users

[Q] SM-N9005 HK softbricked. Please help

Hi ,
My phone is soft-brocked and I can't get it back. Let me explain what happened, maybe you can suggest next course of action:
1- I tried to install KitKat official release via ODIN (N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_HOME.tar.md5 version). Odin FAILED in the middle of the process, and got soft-bricked. When I turn the phone on now I get "Firmware upgrade encountered an issue. Please selecr recovery mode in Kies and try again" :crying:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2- I tried to install previous Poland version, so that I could just perform an OTA update, and it also failed. Then I investigated further and realized my Note 3 is actually a model from Hong Kong (16GB) and seems to be the only version not compatible with other SM-N9005 firmwares.
3.- I found a version of the FW for this specific device (TGY-N9005ZHUDMK1-20131111204936) and tried to install it, then I got to a ext-4 error in Odin (again), unresolved)
4- I got a FW version for my phone with all files separate (N9005ZHUBMI7_China) and tried to upload individualy, I got everything but BL and AP
5- I tried with a forum suggesting to upload Bootloader from leaked KitKat version, and PI, AP, CP and CSC from Chinese version, that did not fix the problem
6.- Now, for any version I try to install I get this:
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> NON-HLOS.bin
<ID:0/012> NAND Write Start!!
<ID:0/012> aboot.mbn
<ID:0/012> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
I tried with ODIN 3.07 and 3.09. Results are exactly the same
7- I tried Kies and I get "The connected device is not supported by Kies 3 (I have the latest version)
8- In Kies, when I try to perform a "Firmware upgrade and initialization" after requesting Model and seial# I get "SM-N9005 does not support initialization"
9- I took my phone to the official Samsung Support in my country (argentina) and they said the model is not sold in Argentina, so there's nothing they can do
What do I have
1.- I can still access download mode and upload via Odin (works fine for CSC, CP and PIT, not for AP and BL)
2.- I can still access recovery mode (after installing CSC alone, the phone starts in recovery mode)
3- Fortunatelly, I have 2 batteries and an external charger, so no battery issues
I have ran out of ideas. Is there anyone around who can lend me a hand with this, please? I am desperate.
Thanks a lot!!!

Have a look at the procedure mentioned here..
http://forum.xda-developers.com/showthread.php?p=49527507
Edit: From the same thread-
* Is this Poland KitKat support Hong Kong N9005 - No, Hong Kong N9005 is not friendly with others country N9005, cannot cross flashing.
* What to do if I accidentally flash it under Hong Kong N9005 and soft brick now - The only solution now is flashing custom recovery (Knox trip due to custom recovery) for KitKat and later flash SweetROM v7 KitKat custom ROM.
Sent from my SM-N900 using Tapatalk

Same thing happened with mine, flashed Cwm with odin and it sprang to life...

Your phone has the kitkat bootloader but no ROM. The only thing you can do is either wait for the official Hong Kong Kitkat ROM or install a custom ROM based on Kitkat.
EDIT:
Here.
rinuvimal said:
This is for Hong Kong 16GB N9005 who were 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.
Many Thanks to @Volrath for his/her post in another forum with this solution. I have tried and it worked. I've tried almost every other solution without avail. So, this is probably the only solution available at the time I'm writing this post.
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/showthread.php?t=2454079
Download Sweet Rom and place it in ExtSDcard (http://forum.xda-developers.com/showthread.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)
Click to expand...
Click to collapse

FeralFire said:
Your phone has the kitkat bootloader but no ROM. The only thing you can do is either wait for the official Hong Kong Kitkat ROM or install a custom ROM based on Kitkat.
EDIT:
Here.
Click to expand...
Click to collapse
I have the same issue and im just waiting for the Official KitKat HK version. As of right now im stuck basically a phone has no ROM. And since i cannot downgrade to 4.3 because my bootloader already says 4.4.2 and I have tried installing SweetRom KitKat but it keeps crashing on the Samsung Setup Wizard and yes i have every wipe that you can think of still has the same issue.
You can try installing Sweet Rom KitKat and let me know if it works for you because for mine i just cant get it to work and pass the Samsung Setup Wizrd thing it will just crashed.

con2vp1 said:
I have the same issue and im just waiting for the Official KitKat HK version. As of right now im stuck basically a phone has no ROM. And since i cannot downgrade to 4.3 because my bootloader already says 4.4.2 and I have tried installing SweetRom KitKat but it keeps crashing on the Samsung Setup Wizard and yes i have every wipe that you can think of still has the same issue.
You can try installing Sweet Rom KitKat and let me know if it works for you because for mine i just cant get it to work and pass the Samsung Setup Wizrd thing it will just crashed.
Click to expand...
Click to collapse
Try some other custom ROM. Try Echoe.

http://forum.xda-developers.com/showthread.php?t=2616103
Sent from my SM-N9005 using Tapatalk

con2vp1 said:
I have the same issue and im just waiting for the Official KitKat HK version. As of right now im stuck basically a phone has no ROM. And since i cannot downgrade to 4.3 because my bootloader already says 4.4.2 and I have tried installing SweetRom KitKat but it keeps crashing on the Samsung Setup Wizard and yes i have every wipe that you can think of still has the same issue.
You can try installing Sweet Rom KitKat and let me know if it works for you because for mine i just cant get it to work and pass the Samsung Setup Wizrd thing it will just crashed.
Click to expand...
Click to collapse
Please delete. Wrong post.

i got the same problem before and i manage to fix it... but KNOX is triggered.. better bricked ..
so i manage to get HK Note 3 fixed from a soft brick. (flashed kitkat and didnt realize the poland rom is not for HK version LOL)
I got all the file it needed to make it work since i cant post direct link to my mega account.
so i give u guys the file name to search in google
(1) N9005ZHUBMI7.rar
(2) Note 3 Kitkat.zip
(3) n9005-cwm-recovery-6.0.4.6-kitkat(0113).tar
(4) SweetROM_V7.00_NA6_4.4.2_N9005.zip
i used ODIN 3.07 for the progress... it might work on 3.09 or even better
so here is the procedure
a) unzip all the file in (1) and (2)
b) phone in download mode
c) open 3.07 .
d) pick the PIT file from (1). bootloader/BL from (2), PDA/AP, Phone/CP and CSC all from (1)
e) flash and wait until it reboot.
f) download mode again and use ODIN 3.07 to flash (3) in the PDA
G) after root (shall into a boot loop) . take the battery out and put into recovery (vol up , home , power)
H) make sure u have the (4) inside the root of the SD card (rename to update.zip) and do a wipe/ reset . then flash
i) when is done .. ur phone will boot fully.. then shut off and flash CP again one more time. CP is from (2) and use ODIN 3.07
now ur phone will be up and running
any question let me know
and if u need the file
email me and i give u the link
u g l y b b @ h o t m a i l . c o m

uglybb88 said:
i got the same problem before and i manage to fix it... but KNOX is triggered.. better bricked ..
so i manage to get HK Note 3 fixed from a soft brick. (flashed kitkat and didnt realize the poland rom is not for HK version LOL)
I got all the file it needed to make it work since i cant post direct link to my mega account.
so i give u guys the file name to search in google
(1) N9005ZHUBMI7.rar
(2) Note 3 Kitkat.zip
(3) n9005-cwm-recovery-6.0.4.6-kitkat(0113).tar
(4) SweetROM_V7.00_NA6_4.4.2_N9005.zip
i used ODIN 3.07 for the progress... it might work on 3.09 or even better
so here is the procedure
a) unzip all the file in (1) and (2)
b) phone in download mode
c) open 3.07 .
d) pick the PIT file from (1). bootloader/BL from (2), PDA/AP, Phone/CP and CSC all from (1)
e) flash and wait until it reboot.
f) download mode again and use ODIN 3.07 to flash (3) in the PDA
G) after root (shall into a boot loop) . take the battery out and put into recovery (vol up , home , power)
H) make sure u have the (4) inside the root of the SD card (rename to update.zip) and do a wipe/ reset . then flash
i) when is done .. ur phone will boot fully.. then shut off and flash CP again one more time. CP is from (2) and use ODIN 3.07
now ur phone will be up and running
any question let me know
and if u need the file
email me and i give u the link
u g l y b b @ h o t m a i l . c o m
Click to expand...
Click to collapse
Do you have the 16gb or the 32gb hongkong version?

Hi guys, thanks a lot for your comments. I have finally resolved, trying the methods you suggested and others, and finally got it back to life this way (I'm posting in case this might be useful for any of you as well)
1.- Flashed bootloader from N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_OXX (Leaked Kit Kat version)
2.- After reboot, flased bootloader, CP and CSC from the same version (N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_OXX). Flashing bootloader again might not be necessary, but this is how I did it, and how it worked, so I cannot confirm otherwise
3.- Flased AP from N9005ZHUBMI7 (Honk Kong version)
4.- Entered recovery mode and wiped system, cache and dalvik (just in case)
4.- Flashed autoroot (n9005-cwm-recovery-6.0.4.6-kitkat(0113).tar)
5.- Flased CWM recovery for KitKat (n9005-cwm-recovery-6.0.4.6-kitkat(0113).tar)
6.- Installed the latest version of SweetRom (SweetROM_V7.00_NA6_4.4.2_N9005.zip) from this thread: http://forum.xda-developers.com/showthread.php?t=2487425
So long it seems to be working correctly, battery consumption has increased, but this seems normal every time I change my ROM. Thanks again for all your help, and hopefully this will help someone else resolve the issue until the official version for the HK 16GB version is available.

is a 16gb
filchi756 said:
Do you have the 16gb or the 32gb hongkong version?
Click to expand...
Click to collapse

Question
Hi there,
I reached step 4 and flashed AP N9005ZHUDMJ8 (HK version too) but got an error. Is it a must to use your suggested version?
Thank you.
maumarti2k said:
Hi guys, thanks a lot for your comments. I have finally resolved, trying the methods you suggested and others, and finally got it back to life this way (I'm posting in case this might be useful for any of you as well)
1.- Flashed bootloader from N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_OXX (Leaked Kit Kat version)
2.- After reboot, flased bootloader, CP and CSC from the same version (N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_OXX). Flashing bootloader again might not be necessary, but this is how I did it, and how it worked, so I cannot confirm otherwise
3.- Flased AP from N9005ZHUBMI7 (Honk Kong version)
4.- Entered recovery mode and wiped system, cache and dalvik (just in case)
4.- Flashed autoroot (n9005-cwm-recovery-6.0.4.6-kitkat(0113).tar)
5.- Flased CWM recovery for KitKat (n9005-cwm-recovery-6.0.4.6-kitkat(0113).tar)
6.- Installed the latest version of SweetRom (SweetROM_V7.00_NA6_4.4.2_N9005.zip) from this thread: http://forum.xda-developers.com/showthread.php?t=2487425
So long it seems to be working correctly, battery consumption has increased, but this seems normal every time I change my ROM. Thanks again for all your help, and hopefully this will help someone else resolve the issue until the official version for the HK 16GB version is available.
Click to expand...
Click to collapse

Maybe I can help
fbasbas said:
Hi there,
I reached step 4 and flashed AP N9005ZHUDMJ8 (HK version too) but got an error. Is it a must to use your suggested version?
Thank you.
Click to expand...
Click to collapse
Maybe I can help.
Please read my article at http://forum.xda-developers.com/showthread.php?p=49831876

fbasbas said:
Hi there,
I reached step 4 and flashed AP N9005ZHUDMJ8 (HK version too) but got an error. Is it a must to use your suggested version?
Thank you.
Click to expand...
Click to collapse
Actually, I only got it to work with the version I mentioned in the post, I don't think I tried with the version you mention. If it failed, I'd suggest you start over, but this time try with the version I suggested, since at least I know this worked for 2 people already. Also, I believe you need to own a 16GB HK version, just in case, Hope this helps

Ask for Help
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_N9005ZHUBMI7_1626679_REV03_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CP_N9005XXUBMI5_REV03_CL1252918.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_ZZH_N9005ZZHBMI7_1626679_REV03_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Ext4)
can not..............hix hix hix

working solution
Download and ODIN flash N9005ZHUENB5 in sam mobile. Works on my HK Note 3
minhluansgk said:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_N9005ZHUBMI7_1626679_REV03_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CP_N9005XXUBMI5_REV03_CL1252918.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_ZZH_N9005ZZHBMI7_1626679_REV03_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Ext4)
can not..............hix hix hix
Click to expand...
Click to collapse

0[Q] [Help] (4.2.2 MDL i337 AT&T) Unknown IMEI Number + softbrick (SOLVED)

Hi,
I'm still a newb to the s4, so thanks for taking the time to look at my thread!
I got an S4 i337 from eBay. The phone booted up with the little custom and unlock graphic on the boot screen. The IMEI was reading all 0000... I tried to use QPST to see if restoring the .QCN from my other S4 i337 (also on 4.2.2 MDL) would help the IMEI issue. QPST gave me a "no phone" error when I tried to backup/restore on the new i337. I tried to root / reinstall recovery using CASUAL. It successfully rooted and installed TWRP but didn't help my QPST situation.
I had read that an incorrect or mis-flashed modem could be causing my problems so tried installing the MDL modem through ODIN 3.07. I tried to flash the modem.bin from through "phone" and got...
"<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)"
After that point I couldn't do anything with the phone so I unplugged the USB and did a battery pull to reboot. Since then I haven't been able to boot up the phone, nor boot into Recovery. It just sits on the samsung logo, or in the case of recovery goes to a black screen and then reboots to the samsung logo. I can still boot into download-mode.
I imagine the solution is simple to one of you pros, but I've been having trouble searching for it and clearly haven't done such a good job so far... any help is much appreciated!
Thanks XDA!

Are you sure your phone is on mdl firmware? If you are I would try to flash the mdl factory firmware with odin, not just the modem but the tar file.
Sent from my Nexus 5

jd1639 said:
Are you sure your phone is on mdl firmware? If you are I would try to flash the mdl factory firmware with odin, not just the modem but the tar file.
Click to expand...
Click to collapse
You're right I don't know what the previous owner did. I'll try that, thanks for the advice!

jd1639 said:
Are you sure your phone is on mdl firmware? If you are I would try to flash the mdl factory firmware with odin, not just the modem but the tar file.
Click to expand...
Click to collapse
Okay well I downloaded the firmware from Sammobile and followed their instructions...
http://www.sammobile.com/firmwares/3/?download=14623
This time Odin finished it's job...
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> modem.bin
<ID:0/003> NON-HLOS.bin
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
The phone is still unable to get past the startup screen
This one...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And if I try to boot it into recovery I get the "recovery booting..." but it then shuts off and (fails at) start up again...
Is it possible my recovery is damaged? If so is there a way to install it through Odin? Am I still able to somehow use ADB?
Thanks

Odin does flash the recovery. Keep trying to get into recovery. When you do do a factory reset. That'll get you past the boot loop. The boot loop is common, but you need to do the factory reset.
If you can't get in to recovery try flashing with odin again
Sent from my Nexus 5

jd1639 said:
Odin does flash the recovery. Keep trying to get into recovery. When you do do a factory reset. That'll get you past the boot loop. The boot loop is common, but you need to do the factory reset.
If you can't get in to recovery try flashing with odin again
Click to expand...
Click to collapse
Hey you're right, I didn't think I'd eventually get into recovery. I just kept holding down the "vol up" button, and after it failed to boot into recovery the first time it successfully did it the second time!
Ran factory reset, reboot phone... successful boot!
Now both my Baseband and IMEI are listed as unknown...
So I rooted this time using Motochopper (worked well for me on my other S4)
Ran RegionLock Away (as a crapshoot... someone reported it bringing back their lost imei...)... didn't help
Installed phoneutil.apk and ran QPST again. It still reports no phone connected on the the COM#s it was connected to.
So far softbrick has been fixed (Thank you SO much!), but now does anyone have any ideas regarding my IMEI number?

This might sound crazy, but I'd Odin again. It should bring your baseband and imei back unless something is really messed up.
Sent from my SAMSUNG-SGH-I727

jd1639 said:
This might sound crazy, but I'd Odin again. It should bring your baseband and imei back unless something is really messed up.
Click to expand...
Click to collapse
Reinstalled the same MDL firmware through ODIN, booted fine on first try but no fix to IMEI or Baseband. used CASUAL to install TWRP, and used TWRP to install the "modem_CWM_I337UCUAMDL.zip", followed by the "Modem_CWM_I337UCUAMDL_Unlock.zip". Neither seemed to help anything. Going to run the firmware install through Odin again, but I don't expect results.
(Edit: yea, no results)

I found this thread on the Galaxy S3 boards talking about efsv1 and efsv2 (came out July 2013) and efsv1 basebands can't read efsv2... is this at all relevant to the Galaxy S4?

Ziida said:
I found this thread on the Galaxy S3 boards talking about efsv1 and efsv2 (came out July 2013) and efsv1 basebands can't read efsv2... is this at all relevant to the Galaxy S4?
Click to expand...
Click to collapse
@rootSU do you know the answer to this? He's lost his imei and odining the stock firmware has not brought it back. I'm out of ideas. Thanx rootSU
Sent from my Nexus 5

Check this thread
http://forum.xda-developers.com/showthread.php?t=2370699

jd1639 said:
@rootSU do you know the answer to this? He's lost his imei and odining the stock firmware has not brought it back. I'm out of ideas. Thanx rootSU
Sent from my Nexus 5
Click to expand...
Click to collapse
I'll be honest, I do not know. I would assume that since Samsung released EFSv2, all subsequent devices were already EFSv2. Of course., these are just the names I have penned. They, in reality could have been EFSv46 and EFSv47. It could also be that each device undergoes these revisions of EFS, to fix bugs or improve service, but this is mere conjecture.
In short, I cannot answer as I have no direct experience of the device in question. Sorry.

jmjoyas said:
Check this thread
http://forum.xda-developers.com/showthread.php?t=2370699
Click to expand...
Click to collapse
Well... That thread worked in getting my imei from "null / null" to "0 / 00". It also made my phone recognized in QPST again! so I was able to install the AWS qcn file and that gave my phone a legitimately recognized IMEI number!
I need to thank everyone for all their help in this thread, the linked thread, and the AWS thread. Looks like I've got an IMEI number again!

[Q] Soft brick - Fail flashing Stock ROM at hidden.img Odin

Guys good morning.
I have rooted and successfully flashed custom recovery and custom firmwares on my Note 3 (9005 Qualcomm LTE), however the last flash (stock ROM 4.4.2 N9005XXUENB4) attempt with Odin (v 3) failed at the end of the flash process ( hidden.img.ext4 -> FAIL! (Size)):
Code:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENB4_N9005DBTENB1_N9005XXUENB1_HOME.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> sbl1.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> aboot.mbn
<ID:0/007> rpm.mbn
<ID:0/007> tz.mbn
<ID:0/007> sdi.mbn
<ID:0/007> NON-HLOS.bin
<ID:0/007> boot.img
<ID:0/007> recovery.img
<ID:0/007> system.img.ext4
<ID:0/007> modem.bin
<ID:0/007> cache.img.ext4
<ID:0/007> hidden.img.ext4
<ID:0/007> FAIL! (Size)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Now the phone won't boot anymore, it is stuck at the following screen (click to enlarge):
I cannot boot in recovery mode. What can I try?

RixNox said:
Guys good morning.
I have rooted and successfully flashed custom recovery and custom firmwares on my Note 3 (9005 Qualcomm LTE), however the last flash (stock ROM 4.4.2 N9005XXUENB4) attempt with Odin (v 3) failed at the end of the flash process ( hidden.img.ext4 -> FAIL! (Size)):
Code:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENB4_N9005DBTENB1_N9005XXUENB1_HOME.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> sbl1.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> aboot.mbn
<ID:0/007> rpm.mbn
<ID:0/007> tz.mbn
<ID:0/007> sdi.mbn
<ID:0/007> NON-HLOS.bin
<ID:0/007> boot.img
<ID:0/007> recovery.img
<ID:0/007> system.img.ext4
<ID:0/007> modem.bin
<ID:0/007> cache.img.ext4
<ID:0/007> hidden.img.ext4
<ID:0/007> FAIL! (Size)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Now the phone won't boot anymore, it is stuck at the following screen (click to enlarge):
I cannot boot in recovery mode. What can I try?
Click to expand...
Click to collapse
You need to flash with this PIT file:
http://forum.xda-developers.com/showpost.php?p=50614669&postcount=77
Click PIT, select that file and tick Re-Partition in addition to the other stuff.

Wrathlon said:
You need to flash with this PIT file:
http://forum.xda-developers.com/showpost.php?p=50614669&postcount=77
Click PIT, select that file and tick Re-Partition in addition to the other stuff.
Click to expand...
Click to collapse
You mean I need to flash again the whole stock ROM + PIT & repartition using the suggested file?

RixNox said:
You mean I need to flash again the whole stock ROM + PIT & repartition using the suggested file?
Click to expand...
Click to collapse
Correct

Flashed successfully, however the Samsung logo kept glowing endlessly at startup, so I have removed the battery, booted in recovery mode and wiped cache and factory reset and YESSSSSSSSSSSS!!!!!!!!!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You rule mate!!! Thanks a lot!!!!!!!!!!!

Thankfully Samsung have a secondary bootloader. The picture you displayed is secondary bootloader, if the flash fails there then you are looking at a brick, not a soft brick but a true paperweight...
You can also forget Kies, since the MJ3 bootloader Kies doesn't recognise the Note 3....

ultramag69 said:
Thankfully Samsung havce 2 bootloader modes, the picture you displayed is secondary bootloader, if the flash fails there then you are looking at a brick, not a soft brick but a true paperweight...
Click to expand...
Click to collapse
I recall once upon a time it was very easy to brick Samsung phones over Odin. Did things change lately? Are later firmwares/phones more foolproof than before as much as HTC are?

RixNox said:
I recall once upon a time it was very easy to brick Samsung phones over Odin. Did things change lately? Are later firmwares/phones more foolproof than before as much as HTC are?
Click to expand...
Click to collapse
Since the Samsung Galaxy S I can safely say it has a secondary bootloader, maybe before but I started on the Samsung galaxy tab7(1st edition) which was an enlarged Galaxy S. If you used Heimdall you'd see it has a file called SBL - secondary bootloader.
It gives you 2 chances to stuff up completely though if you do flash the wrong firmware - for different device - then you overwrite the secondary bootloader and essentially brick your device...

ultramag69 said:
Since the Samsung Galaxy S I can safely say it has a secondary bootloader, maybe before but I started on the Samsung galaxy tab7(1st edition) which was an enlarged Galaxy S. If you used Heimdall you'd see it has a file called SBL - secondary bootloader.
It gives you 2 chances to stuff up completely though if you do flash the wrong firmware - for different device - then you overwrite the secondary bootloader and essentially brick your device...
Click to expand...
Click to collapse
So what conditions can occur to brick the phone?
- damaged/wrong firmware?
- power failure while flashing?
- Or?

RixNox said:
So what conditions can occur to brick the phone?
- damaged/wrong firmware?
- power failure while flashing?
- Or?
Click to expand...
Click to collapse
All the above but if you have the pictured screen on the device you have a final chance to flash correctly... This really is the FINAL chance though, Screw up that flash and you've got a brick that won't turn on or charge...
I have a friends Gtab 7" to prove it. Short of replacing the MB there is no way to get it up and running....

ultramag69 said:
All the above but if you have the pictured screen on the device you have a final chance to flash correctly... This really is the FINAL chance though, Screw up that flash and you've got a brick that won't turn on or charge...
I have a friends Gtab 7" to prove it. Short of replacing the MB there is no way to get it up and running....
Click to expand...
Click to collapse
Very risky.... I wonder how they manage at Samsung OTA/Kies updates... are they any safer? Maybe it's a bad habit to download firmwares from other sites?

It's a standard risk when you flash a rom... This is why the MD5 checks are there, even from the best source you can get a corrupted file...
Also why the devs put the disclaimer that you are flashing your rom and they take no responsibility if it fails...

ultramag69 said:
It's a standard risk when you flash a rom... This is why the MD5 checks are there, even from the best source you can get a corrupted file...
Also why the devs put the disclaimer that you are flashing your rom and they take no responsibility if it fails...
Click to expand...
Click to collapse
The good thing is that an OTA or Kies flashing failure will be covered bi warranty, if any.
Any chance to get the bit 0x1 to 0x0 once "spoiled"? Flashing an original stock rom will not reset to 0...

Still Stuck
RixNox said:
Flashed successfully, however the Samsung logo kept glowing endlessly at startup, so I have removed the battery, booted in recovery mode and wiped cache and factory reset and YESSSSSSSSSSSS!!!!!!!!!!!
You rule mate!!! Thanks a lot!!!!!!!!!!!
Click to expand...
Click to collapse
Many thanks to Wrathlon as I was stuck in the same place! Now I'm stuck at the Samsung logo. I cannot boot into recovery mode to wipe cache and factory reset. Any suggestions?

RixNox said:
The good thing is that an OTA or Kies flashing failure will be covered bi warranty, if any.
Any chance to get the bit 0x1 to 0x0 once "spoiled"? Flashing an original stock rom will not reset to 0...
Click to expand...
Click to collapse
Nope... The bounty is over $3000 USD...

jebanec said:
Many thanks to Wrathlon as I was stuck in the same place! Now I'm stuck at the Samsung logo. I cannot boot into recovery mode to wipe cache and factory reset. Any suggestions?
Click to expand...
Click to collapse
As I wrote I got through removing the battery, booting in recovery mode, performed a wipe data (format) & wipe cache (2 steps in total)

RixNox said:
As I wrote I got through removing the battery, booting in recovery mode, performed a wipe data (format) & wipe cache (2 steps in total)
Click to expand...
Click to collapse
Please excuse my ignorance, but how are you actually booting into recovery? I'm on stock ROM and haven't rooted.

jebanec said:
Please excuse my ignorance, but how are you actually booting into recovery? I'm on stock ROM and haven't rooted.
Click to expand...
Click to collapse
Once you've turned off the phone, keep pressed at the same time (with following sequence)
1) Volume up
2) home
3) power
Keep the buttons pressed at the same time until the phone shows "booting recovery"
This should bring into recovery mode. navigate menus using volume up/down and use power button to confirm/enter. Perform both wipe data factory reset & wipe cache. Once done select reboot

RixNox said:
Once you've turned off the phone, keep pressed at the same time (with following sequence)
1) Volume up
2) home
3) power
Keep the buttons pressed at the same time until the phone shows "booting recovery"
This should bring into recovery mode. navigate menus using volume up/down and use power button to confirm/enter. Perform both wipe data factory reset & wipe cache. Once done select reboot
Click to expand...
Click to collapse
Many thanks. I tried this earlier but for some reason I couldn't get into recovery. I'll try again later to see if I can get it to work.

jebanec said:
Many thanks. I tried this earlier but for some reason I couldn't get into recovery. I'll try again later to see if I can get it to work.
Click to expand...
Click to collapse

[Recovery] Unofficial TWRP 3.0 for Galaxy Tab 8.9 (p5wifi/P7310 and p5/P7300)

These are unofficial builds of TWRP for the Samsung Galaxy Tab 8.9 p5wifi/GT-P7310 and p5/GT-P7300.
This version of recovery uses the extra partition for storing recovery system files. It hasn't been used since the original Samsung ROMs. If you have been using it for whatever reason then back up the data you have stored on there. If you haven't been using it then this is of no concern to you.
I do not have this device however this tablet is nearly the same as the Galaxy Tab 10.1 (p4wifi/GT-P7510) which I have been doing ROMs and recoveries for. The only difference in this build of TWRP is the kernel.. These builds are not personally tested by me since I don't have this device so use it at your own peril.
Installation:
Install the TWRP zip file in recovery
or
Flash the TWRP tar.md5 file with odin
Download:
twrp3020-20160927-p5wifi.zip
twrp3020-20160927-p5wifi.tar.md5
twrp3020-20160927-p5.zip
twrp3020-20160927-p5.tar.md5
Donate:
Via Paypal
XDA:DevDB Information
TWRP 3.0 for Galaxy Tab 8.9 p5wifi / P7310 and p5 / P7300, Tool/Utility for the Samsung Galaxy Tab 8.9
Contributors
decatf
Source Code: https://github.com/decatf
Version Information
Status: Testing
Created 2016-09-27
Last Updated 2016-09-27

@decatf , THX for dev. of a new Recovery Version for our old Tab. I will try it the next days and give you feedback.
In case of issues i will take a log from Recovery.

@decatf First Feedback
1. after a full backup of my installed Rom , i install the Test TWRP and rebooted directly to the New Version. With out probs.
2. Twrp shows in Porträt mode , but the touch function are rotated + 90° in the landscape mode.
After find out where are the Position of reboot button it was possible to reboot into my installed Rom with out probs.

bierma32 said:
@decatf First Feedback
1. after a full backup of my installed Rom , i install the Test TWRP and rebooted directly to the New Version. With out probs.
2. Twrp shows in Porträt mode , but the touch function are rotated + 90° in the landscape mode.
After find out where are the Position of reboot button it was possible to reboot into my installed Rom with out probs.
Click to expand...
Click to collapse
Is recovery for this device normally in landscape or portrait?

decatf said:
Is recovery for this device normally in landscape or portrait?
Click to expand...
Click to collapse
Our recovery is defaulted to portrait (at least the ones we have).I am happy to see you here trying to give some love to our tab. I'll be happy to test anything that needs testing. Just send them up here and I'll test and report back.
Edit: Installed and works fine except for the rotation issue (shows in portrait but touch is in landscape). All other functions as far as I tested works fine. The only thing I noticed for me was that when I pressed reboot system it powered off instead but that's no big issue.

bierma32 said:
@decatf First Feedback
1. after a full backup of my installed Rom , i install the Test TWRP and rebooted directly to the New Version. With out probs.
2. Twrp shows in Porträt mode , but the touch function are rotated + 90° in the landscape mode.
After find out where are the Position of reboot button it was possible to reboot into my installed Rom with out probs.
Click to expand...
Click to collapse
L3R0N said:
Our recovery is defaulted to portrait (at least the ones we have).I am happy to see you here trying to give some love to our tab. I'll be happy to test anything that needs testing. Just send them up here and I'll test and report back.
Edit: Installed and works fine except for the rotation issue (shows in portrait but touch is in landscape). All other functions as far as I tested works fine. The only thing I noticed for me was that when I pressed reboot system it powered off instead but that's no big issue.
Click to expand...
Click to collapse
Here's another try.
twrp3020-20160922-p5wifi.zip
twrp3020-20160922-p5wifi.tar.md5
It's the same filenames as the first build (sorry).

decatf said:
Here's another try.
twrp3020-20160922-p5wifi.zip
twrp3020-20160922-p5wifi.tar.md5
It's the same filenames as the first build (sorry).
Click to expand...
Click to collapse
New build has fixed the touch rotation issue and it works as it's supposed to.
Edit: Reboot System now works as it should as well. Gonna flash a ROM and see how it goes.
Edit 2: Backup and restore function works great. Flashing ROM zip files also works.

L3R0N said:
New build has fixed the touch rotation issue and it works as it's supposed to.
Edit: Reboot System now works as it should as well. Gonna flash a ROM and see how it goes.
Edit 2: Backup and restore function works great. Flashing ROM zip files also works.
Click to expand...
Click to collapse
Great. Thanks for testing.

decatf said:
Great. Thanks for testing.
Click to expand...
Click to collapse
And thank you for bringing us a new and updated recovery. Happy to test out anything that needs testing. :good:

@decatf THX for New Version.
I installed your new Version and all basic function im tested works fine. ( wipe / advanced ; backup/ restore ; install ) will try a the weekend also otg USB function and full wipe included data/ media and install from USB storage. ( so i have full fresh formated Tab )

I was unable to Flash using Odin 3.0. Will be trying the zip file for P5 using previous TWRP 2.71
Below is ODIN logs:
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> twrp3020-20160927-p5.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> hidden.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
---------- Post added at 07:26 PM ---------- Previous post was at 07:19 PM ----------
wbisschoff said:
I was unable to Flash using Odin 3.0. Will be trying the zip file for P5 using previous TWRP 2.71
Below is ODIN logs:
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> twrp3020-20160927-p5.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> hidden.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
The zip file in Recovery seems to be working, so next step is to try the the aosp 5.1.1 p5

It's working great, but when I press the power button, it doesn't turn the screen off, but locks the recovery. Is it meant to be like this, or is it a bug? Could it be caused by the theme I installed?

The .zip.md5 file didn't work for me. How I fixed it: First, I flashed TWRP 2.7.1.0 (link) using odin and then flashed the .zip from this thread to update twrp.

TheRandomLabs said:
It's working great, but when I press the power button, it doesn't turn the screen off, but locks the recovery. Is it meant to be like this, or is it a bug? Could it be caused by the theme I installed?
Click to expand...
Click to collapse
It is meant to be like that.
marti201 said:
The .zip.md5 file didn't work for me. How I fixed it: First, I flashed TWRP 2.7.1.0 (link) using odin and then flashed the .zip from this thread to update twrp.
Click to expand...
Click to collapse
Was it an error flashing with odin?

decatf said:
Was it an error flashing with odin?
Click to expand...
Click to collapse
Yes, and I took a screenshot when it happened.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried three times and it failed every time.
I have a p5 and was trying to flash the p5wifi recovery (so that I can install AOSP 7.1). It's compatible, so I don't think that was the problem.
I don't have Kies or SmartSwitch installed, just the drivers, and my antivirus was disabled, so they were probably not the problem either.
I was using Odin 3.11.1 from Sammobile.

marti201 said:
Yes, and I took a screenshot when it happened.
I tried three times and it failed every time.
I have a p5 and was trying to flash the p5wifi recovery (so that I can install AOSP 7.1). It's compatible, so I don't think that was the problem.
I don't have Kies or SmartSwitch installed, just the drivers, and my antivirus was disabled, so they were probably not the problem either.
I was using Odin 3.11.1 from Sammobile.
Click to expand...
Click to collapse
Try with Odin 1.85.

decatf said:
Try with Odin 1.85.
Click to expand...
Click to collapse
Thanks for the suggestion, but I've already installed twrp successfully.

Does anyone have backup for this twrp
---------- Post added at 11:35 PM ---------- Previous post was at 11:35 PM ----------
The link is broken

egha5037 said:
Does anyone have backup for this twrp
---------- Post added at 11:35 PM ---------- Previous post was at 11:35 PM ----------
The link is broken
Click to expand...
Click to collapse
Do not try the links included in the reply, use the links from the original thread's post. I used them yesterday and those were working. Also, I did not experience issue with screen rotation versus touch, so those original links are probably the latest ones.

doesnt work..
<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> hidden.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
-----------------------------
GT-P7300 ...
Odin v3 1.85
I can`t flash TWRP 3.0 into my GT-P7300... Any suggestions?

Note 4 SM-N910W8 - Help

Hi
So I got this note from a seller online. The seller was forth coming in letting me know of the problem with the phone. It was stuck ultra-saving mode and the person didn’t know how to get it out of it, hence I got a good deal to tinker with.
NOW, I am stuck. As you can see from the pics below I am trying to flash it with kies. However, its unable to write.
There was an instance where download screen was telling me that I was missing PIT file, and now its just unable to write to system………
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any help will be highly appreciated.
I tried flashing TWRP, but after brute forcing it via odin, it shows “Pass” but when I try to boot into recovery, again it displays that unable to write…….so I cant even flash a stock rom.
Model # SM-N910W8
Thanks.

Flash the full recovery firmware.
Reporting via N910G.

@yashthemw, Could you please direct me to the recovery .tar for my model..... Model # SM-N910W8 - Canadian version.
Can i use any model's recovery? N910F/C/T?
Really appreciate it.
Could you also please clarify the PIT partition message i got:
Should i flash .pit file first with a recovery image (via odin) OR do flash pit first and then flash recovery.
Thanks again.

your best bet would be to google "how to flash a galaxy note 4" from there take your time you"ll see anything you need....its not that hard at the end.....your phone only need a brand new flash!!

Hey guys, so i did do a re-flash
followed this guide
https://www.youtube.com/watch?v=1TsTQeSXJBA
How To UnRoot, UnBrick, and/or Flash your Samsung Galaxy Note 4 Stock!
Got the firmware from samobile (that took 2 hours :S)
here is the log from Odin:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> sbl1.mbn
<ID:0/005> rpm.mbn
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Removed!!
Any thoughts? really appreciate the help...........

Try to flash the c.f. auto root file.
There is no recovery firmware available for n910w8 .
Reporting via N910G.

HI
So i flashed CF root via odin and have this showing up...............I am clueless as to what to do next...............any suggestions?

samsha said:
HI
So i flashed CF root via odin and have this showing up...............I am clueless as to what to do next...............any suggestions?
Click to expand...
Click to collapse
Now try to flash stock rom.
Reporting via N910G.

Hi
I tried flashing a stock rom.............its still asking for a pit file :S
I am totally lost now what to do, anyone with ideas??
Does it matter if i use a different model (eg: f/g etc) note 4 firmware??? recovery? to flash??
Or am i stuck with N910W8 files............. :S

i think u need a pit file if u search for the pit file there should be one on xda

Solved!
Hi guys,
So after weeks of reading up on possible solutions, I got the N4 to work.
Here are the steps to try out, this is for the SM-N910W8 model, but you can find the pit files and your specific files online or from the links I post.
You will need 3 things;
1) Odin – I used the 3.09 version.
http://odindownload.com/Samsung-Odin/#.WCvgpeYrKMo
2) Pit file: http://www.sammobile.com/forum/showthread.php?t=30022
Search your model, for me it was the SM-N910W8.
3) Download the latest firmware from online - http://www.sammobile.com/firmwares/
Try to get the original carrier brand you have but I used a unknown one.
(on a side note, this step will take 2 hours, at-least for me it did. Damn you regular download)
2016-05-30 Unknown 6.0.1 N910W8VLU1DPE2 N910W8OYA1DPE2
Steps:
I loaded up the pit file, and the AP file extracted from the firmware on ODIN.
NOW MAKE SURE – IMP – when you load the files on ODIN have the following boxes ticked off!!
 Auto-Reboot
 Re-Partition
 F. Reset Time
Make sure your device is in Download mode and plugged in the PC as well as recognized by ODIN with a COM ID.
Press START and cross your fingers and legs and whatever you can find.
Hopefully, it went smooth and worked out.
All credits goes to the contributors in XDA and Sammobile and various other forums for providing insights and technical knowledge. You have to do your reading and above all be patient and something will work out………….

samsha said:
Solved!
Hi guys,
So after weeks of reading up on possible solutions, I got the N4 to work.
Here are the steps to try out, this is for the SM-N910W8 model, but you can find the pit files and your specific files online or from the links I post.
You will need 3 things;
1) Odin – I used the 3.09 version.
http://odindownload.com/Samsung-Odin/#.WCvgpeYrKMo
2) Pit file: http://www.sammobile.com/forum/showthread.php?t=30022
Search your model, for me it was the SM-N910W8.
3) Download the latest firmware from online - http://www.sammobile.com/firmwares/
Try to get the original carrier brand you have but I used a unknown one.
(on a side note, this step will take 2 hours, at-least for me it did. Damn you regular download)
2016-05-30 Unknown 6.0.1 N910W8VLU1DPE2 N910W8OYA1DPE2
Steps:
I loaded up the pit file, and the AP file extracted from the firmware on ODIN.
NOW MAKE SURE – IMP – when you load the files on ODIN have the following boxes ticked off!!
 Auto-Reboot
 Re-Partition
 F. Reset Time
Make sure your device is in Download mode and plugged in the PC as well as recognized by ODIN with a COM ID.
Press START and cross your fingers and legs and whatever you can find.
Hopefully, it went smooth and worked out.
All credits goes to the contributors in XDA and Sammobile and various other forums for providing insights and technical knowledge. You have to do your reading and above all be patient and something will work out………….
Click to expand...
Click to collapse
Hey there, I'm getting the following error: "Device does not have DRK, (Device Root Key), ...." please install DRK etc... (sorry, didn't get the rest of error msg, got distracted by wife)
I was hoping your solution would fix my problem but it didn't.
I did however find the files I needed on various sites but these bastards are all charging for it. Any ideas where I can find these files for free or if you know of an alternate solution?
COMBINATION_OYA_FA44_N910W8VLU1AOC2_OYA_3357306_RE V00_user_mid_noship_MULTI_CERT.tar.rar
https://firmware.gem-flash.com/index...tegory&id=1280