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

[Q] How to Root on G900FXXU1BNL7 5.0?

Hello I was trying to root my G900F that is currently running Lollipop BNL7 with CF-Auto-Root-klte-kltexx-smg900f and Odin 3.09 after enabling USB debug but Failed at the end of the process. Had to restore stock G900FXXU1BNL7 to get phone back working.
Try it two times always fails at the end.
Any other method or have to wait for updated version of CF-Auto?
Does G900FXXU1BNL7 is rootable?
Is there a way to downgrade to 4.4 safely as I try already and end up in nightmare and dont have EFS backup that is why I want to root first.?
Code:
<OSM> Please wait..
<OSM> CF-Auto-Root-klte-kltexx-smg900f.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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

egejo said:
Hello I was trying to root my G900F that is currently running Lollipop BNL7
Click to expand...
Click to collapse
You haven't done anything serious. Don't worry. You can only use SuperSU 2.38 or above versions. No other method works for TouchWiz Lollipop so far.

Reactivation lock
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I think you already enable (Reactivation lock) from setting --> security
Just uncheck the option and i hope it will work fine

Thanks for the advice but did not work.
I have try these way so to first load a custom recovery via odin to root and install SUperSu tested with both Philz and TWRP but failed also on Odin at the end of the process of each of them.
Had to put stock BNL7 again to recover the phone from "firmware upgrade issue" screen
Does BNL7 has some locked bootloader security or so I cant mod anything neither root it now...
lingowistico said:
You haven't done anything serious. Don't worry. You can only use SuperSU 2.38 or above versions. No other method works for TouchWiz Lollipop so far.
Click to expand...
Click to collapse

egejo said:
Thanks for the advice but did not work.
I have try these way so to first load a custom recovery via odin to root and install SUperSu tested with both Philz and TWRP but failed also on Odin at the end of the process of each of them.
Had to put stock BNL7 again to recover the phone from "firmware upgrade issue" screen
Does BNL7 has some locked bootloader security or so I cant mod anything neither root it now...
Click to expand...
Click to collapse
Yes some people say that it only works with Fusion TWRP 2.8.2.0. I don't know if it's true because I already flashed it before flashing SuperSU 2.38 beta And of course it worked.

i cant install recovery mode on bnl7 . Tried it whole day and all i get is stock recovery mode.
Help ?

lingowistico said:
Yes some people say that it only works with Fusion TWRP 2.8.2.0. I don't know if it's true because I already flashed it before flashing SuperSU 2.38 beta And of course it worked.
Click to expand...
Click to collapse
Thanks, sorry to be such a noob but downloaded the Fusion TWRP you post got the zip... but how to install if unzipped there is no odin Tar or such flashable file...neither like and apk, sorry lost in here?
Lastly to let you know that now I'm in Stock G900FXXU1ANCE, dowgraded from BLN7 to BLN2, then ANJ1 and then ANCE. On all of them I have been trying to root or put a custom recovery, used CF-Auto-Root-klte-kltexx-smg900f, openrecovery-twrp-2.8.1.0-klte or philz_touch_6.57.8-klte with same results always Failing Odin at the end of process... The thing I notice is that always it shown on the dowload mode screen
"QUALCOMM SECURE BOOT: ENABLED (CSB)"
Even after downgrade, could these be the issue?
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.57.8-klte.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse

Made a little progress here,
As I'm now on G900FXXU1ANCE I used towelroot and finally gain root access it Work installed SuperSu from Gplay and then finally made an EFS backup with samsung tool...
But still dont know why it does not work all other methods and ODIN rooting and cant have a custom recovery neither...But for now I feal a little safer having my EFS on Dropbox to be sure....
Will keep playing trying to get a working custom recovery so to flash customs roms later...But looks like I will have to wait for updates now...

egejo said:
Made a little progress here,
As I'm now on G900FXXU1ANCE I used towelroot and finally gain root access it Work installed SuperSu from Gplay and then finally made an EFS backup with samsung tool...
But still dont know why it does not work all other methods and ODIN rooting and cant have a custom recovery neither...But for now I feal a little safer having my EFS on Dropbox to be sure....
Will keep playing trying to get a working custom recovery so to flash customs roms later...But looks like I will have to wait for updates now...
Click to expand...
Click to collapse
had the same problem as you use this twrp it worked perfect in the end make you scroll down to where it says THE GOODS TWRP ODIN its near the bottom of first post in this link http://forum.xda-developers.com/showthread.php?t=2697762

pnr2020 said:
had the same problem as you use this twrp it worked perfect in the end make you scroll down to where it says THE GOODS TWRP ODIN its near the bottom of first post in this link http://forum.xda-developers.com/showthread.php?t=2697762
Click to expand...
Click to collapse
Thanks but tested an did not work Odin Fails flashing it.
I can only flash stock roms and root on those old enough for towelroot...
I'm starting to think these brand new S5 SM-G900F is starting to come with locked bootloader....
Is there a way to verify these...?

egejo said:
Thanks, sorry to be such a noob but downloaded the Fusion TWRP you post got the zip... but how to install if unzipped there is no odin Tar or such flashable file...neither like and apk, sorry lost in here?
Click to expand...
Click to collapse
This is the story that I heard and followed, after which I got root on bln2:
You can only get root on Samsung Lollipop with SuperSU v2.38 and above, but the only 100% sure way to flash SuperSU v2.38+ is by flashing it in Fusion TWRP 2.8.2.0.
So you do it like this:
1 Flash rom in odin
2 Flash custom recovery in Odin (CWM/TWRP doesn't matter)
3 Now boot custom recovery and flash the Fusion TWRP 2.8.2.0 zip file
4 Reboot recovery
5 Flash SuperSU v2.38+ zip
6 Enjoy root

lingowistico said:
This is the story that I heard and followed, after which I got root on bln2:
You can only get root on Samsung Lollipop with SuperSU v2.38 and above, but the only 100% sure way to flash SuperSU v2.38+ is by flashing it in Fusion TWRP 2.8.2.0.
So you do it like this:
1 Flash rom in odin
2 Flash custom recovery in Odin (CWM/TWRP doesn't matter)
3 Now boot custom recovery and flash the Fusion TWRP 2.8.2.0 zip file
4 Reboot recovery
5 Flash SuperSU v2.38+ zip
6 Enjoy root
Click to expand...
Click to collapse
I cant flash any custom recovery at all it always fails and softbricks the phone... Looks like these G900F is now bootloader Locked...
If so samsung is now selling them from factory locked not just ATT versions...

egejo said:
Thanks but tested an did not work Odin Fails flashing it.
I can only flash stock roms and root on those old enough for towelroot...
I'm starting to think these brand new S5 SM-G900F is starting to come with locked bootloader....
Is there a way to verify these...?
Click to expand...
Click to collapse
dont know to be honest mine only 2 weeks old from uk was on BTU but now on polish version

egejo said:
Looks like these G900F is now bootloader Locked...
Click to expand...
Click to collapse
I don't think so, everything works fine for me..

i also cant install recovery but i dont get soft bricks , just normal stock recovery mode all over.

"qualcomm secure boot: Enabled (csb)
hello everyone
if you got error in odin when flash any custom recovery just deactivate reactivation lock from setting>security.

[Q] -CM- What to update to

Hi guys, I have a Samsung Galaxy S4 from Canada, specifically Rogers. The phone is currently on the CM11 Nightly ROM. (I can check specifically which nightly, my phone is just backing up at the moment so I can't see!)
I have this problem, which is, when the phone automatically locks or I myself lock it, the radio signal completely drops. Sometimes the signal will come back, but to get it back for sure is to turn the phone on airplane mode then off again. It is annoying because when the phone is locked for a while, it will receive signal at some point. During that time I'll get a call and it'll ring but once the screen turns on the signal will drop, also dropping the call. I have a slight understanding that it could be a problem with the phone's radio firmware?
Now that you guys have an understanding about my problem, this is what I am hoping to accomplish. I want to update the phones ROM, as it is probably old, along with the proper fix to the phone's radio firmware. How do i go about doing this? The kind of ROM that I want is something in between stable version and nightly (not nightly as I think nightly was the one that caused my radio problem), I think that's SNAPSHOT M12? Please correct me if I am wrong. I would rather not lose any of my data but if I have to then I will but please do guide me because I am scared to lose any of my data.
Thank you guys for reading my long post, I hope my English and grammar is fine! I look forward to hearing from you guys!

The current version of Cyanogenmod is 12.1 (Android 5.1.1). The two release channels for 12.1 are nightlies and snapshots. As of yet there has been no CM12.1 snapshot I'm aware of, meaning all CM12.1 ROMs are nightlies.
You haven't said what version of the stock ROM you had before moving to CM11, but if the radio is too old, you'll want to update it. You'll need Odin and either the modem file, or a complete ROM, which you can download from here. If you choose to install the stock ROM, be aware that you will have to root your device again, using CF-Autoroot. Flashing the stock ROM or modem won't wipe your data unless you tell Odin to partition the S4, so you don't want to do that. What you do want to do before you attempt to do anything is make a nandroid backup as well as move any important files off the internal storage. While you won't need to wipe the S4 prior to installing the new stock ROM or the modem, you will need to do so when installing the new version of Cyanogenmod.
P. S. In the future, you want to direct your questions to the AT&T Galaxy S4 forums as this is the International S4 forum, which doesn't cover North American S4 devices. Your question however is general enough that we should still be able to help you.

Thanks for the reply!
Strephon Alkhalikoi said:
You haven't said what version of the stock ROM you had before moving to CM11
Click to expand...
Click to collapse
I don't know how to answer this, It's been quite a long time since I moved to CM11. Basically what I did was, when I bought the phone I went home and installed CM11 on it, haha.
Strephon Alkhalikoi said:
You'll need Odin and either the modem file, or a complete ROM, which you can download from here. If you choose to install the stock ROM, be aware that you will have to root your device again, using CF-Autoroot. Flashing the stock ROM or modem won't wipe your data unless you tell Odin to partition the S4, so you don't want to do that. What you do want to do before you attempt to do anything is make a nandroid backup as well as move any important files off the internal storage. While you won't need to wipe the S4 prior to installing the new stock ROM or the modem, you will need to do so when installing the new version of Cyanogenmod.
Click to expand...
Click to collapse
I am quite confused, sorry. What I'm doing right now is I'm downloading the newest radio firmware from the link you have given me. After that I'm going to follow the instructions of:
Extract (unzip) the firmware file
Download Odin v3.10.6
Extract Odin ZIP file
Open Odin v.3.10.6
Reboot Phone in Download Mode (press and hold Home + Power + Volume Down buttons)
Connect phone and wait until you get a blue sign in Odin
Add the firmware file to AP / PDA
Make sure re-partition is NOT ticked
Click the start button, sit back and wait few minutes
That will fix my radio problems?
Now to update my ROM. This is where I am mostly confused. In your opinion, should I stick with CM11 Nightly? Can I somehow go from nightly to a more stable version like cm11 snapshot m12? Should I update to CM12? Will my phone keep up with the CM12 ROM?
Strephon Alkhalikoi said:
P. S. In the future, you want to direct your questions to the AT&T Galaxy S4 forums as this is the International S4 forum, which doesn't cover North American S4 devices. Your question however is general enough that we should still be able to help you.
Click to expand...
Click to collapse
Sorry I will keep that in mind! Mind you, I carefully chose this and looked at all my other options. I didn't see the AT&T forum to fit because AT&T is in the United States and my carrier is in Canada, I just didn't want to have problems with anything else

Guys, I think i screwed up.... So when i downloaded that firmware from Sammobile. I flashed it with ODIN and made sure re-partition was not checked. Everything looked fine and when my phone rebooted (its still rebooting at the moment) the welcome screen was the default "samsung" splash screen, not the Cyanogen Mod . I thought this method was only going to flash the phone's modem, not the ROM too
EDIT:
No....my worst nightmare came true .........NO!!!!
So my phone finished rebooting and its just a black screen. All I can see is the status bar at the top right that displays the WiFi signal and the Phone's network signal and the battery. Okay so I figured something out. When the phone is locked and I press the Home button, Battery Doctor's charging wallscreen shows up, meaning my device wasn't wiped ? When I tried to unlock from Battery Doctor's charging screen, it would just show the black screen with just the status bar .... PLEASE HELP ME !!!

It flashes a complete ROM, which is part of the reason I mentioned making a backup. Now you'll need to root your S4 again, as I mentioned, install a custom recovery, and then you can install Cyanogenmod (12.1 recommended). By flashing the complete ROM it also ensures you have a clean slate from which to move forward. Now all the firmware pieces "match" and you avoid any odd effects by having a mismatched bootloader and baseband.

Strephon Alkhalikoi said:
It flashes a complete ROM, which is part of the reason I mentioned making a backup. Now you'll need to root your S4 again, as I mentioned, install a custom recovery, and then you can install Cyanogenmod (12.1 recommended). By flashing the complete ROM it also ensures you have a clean slate from which to move forward. Now all the firmware pieces "match" and you avoid any odd effects by having a mismatched bootloader and baseband.
Click to expand...
Click to collapse
D'awww Well I guess a clean slate isn't so bad. I backed up my text messsages and my photo's should be backed up onto the google drive anyways. I don't know if you saw my edited post but the UI is not loading. Its just showing the status bar at the top right (signal, wifi signal, battery).
Thanks.

If you're going to install CM12.1 I wouldn't worry about Touchwiz not starting. Just go ahead and prep the phone for Cyanogenmod, as the most important parts - baseband and bootloader - are apparently working properly.
EDIT: ROM installs don't wipe data when done through Odin unless you tell Odin to partition the device. Thus you'd need a factory reset to ensure Touchwiz works. But where you're going to put Cyanogenmod on, don't worry about Touchwiz.

Strephon Alkhalikoi said:
If you're going to install CM12.1 I wouldn't worry about Touchwiz not starting. Just go ahead and prep the phone for Cyanogenmod, as the most important parts - baseband and bootloader - are apparently working properly.
Click to expand...
Click to collapse
The problem is, I can't. There's nothing there on the phone. Its just a black screen. Unless, thats what you meant.
I tried searching for a CM 12.1 Canadian version and I found this thread. http://forum.cyanogenmod.org/topic/104233-jfltesgh-i337m/
apparently theres no canadian version of the CM 12.1
what should I do ?

Use the Optimized CM12.1 here in I9505 Original Android Development. It's supposed to work with all Qualcomm S4s except the Value Edition S4.
Oh, and you don't need CF-Autoroot. Simply install the recovery using Odin, then install Cyanogenmod. Wipe data and cache, then reboot. Everything should be back to normal about ten minutes after rebooting, as the ART compiler compiles the apps.

Strephon Alkhalikoi said:
Use the Optimized CM12.1 here in I9505 Original Android Development. It's supposed to work with all Qualcomm S4s except the Value Edition S4.
Oh, and you don't need CF-Autoroot. Simply install the recovery using Odin, then install Cyanogenmod. Wipe data and cache, then reboot. Everything should be back to normal about ten minutes after rebooting, as the ART compiler compiles the apps.
Click to expand...
Click to collapse
Thanks for the replies! I'm sorry if im asking for too much but could you please confirm that this is the right one? link
So, I don't need to root? how can i verify that my phone is still rooted? If my phone is still rooted, I download Canadian Galaxy S4 SGH-i337M (Bell, Rogers, Telus) – CWM Recovery v6.0.4.4
Then flash that with Odin ?
edit: I think I know why this failed miserably....On Odin V3.10.6 I clicked "AP" for some reason, when I was flashing the firmware. Could that be the problem? If so, is there a fix ? i can't access my phones SD card .

Right link, but Clockworkmod is not a good choice for a recovery to flash through Odin. Use TWRP instead as Clockworkmod is no longer updated.
Cyanogenmod is pre-rooted, though until you open the developer options in settings you can't access it. That's why you don't need to root beforehand. There is no harm however if you choose to root anyway before installing.
Clicking Odin like that shouldn't do anything. But where you've encountered problems, read the instructions here to wipe the storage. Then install the stock ROM again through Odin to see if that resolves the problem.

i just installed cm-12.1-20150625-NIGHTLY-jfltexx on my s4 with cm-12.1-20150623-NIGHTLY-jfltexx but there is a problem with the phone functions. It can't make any call. .it do not find my sim card!! Same thing with cm-12.1-20150624-NIGHTLY . The last one that works is 20150623 . Is there anyone that can confirm my problem?

Strephon Alkhalikoi said:
Right link, but Clockworkmod is not a good choice for a recovery to flash through Odin. Use TWRP instead as Clockworkmod is no longer updated.
Cyanogenmod is pre-rooted, though until you open the developer options in settings you can't access it. That's why you don't need to root beforehand. There is no harm however if you choose to root anyway before installing.
Clicking Odin like that shouldn't do anything. But where you've encountered problems, read the instructions here to wipe the storage. Then install the stock ROM again through Odin to see if that resolves the problem.
Click to expand...
Click to collapse
I am following this:
Code:
TWRP Recovery v2.8.7.0 is suggested for installation
First time or clean install:
Download the ROM from the link above
Download GApps package for Lollipop 5.1
Put the zip files on your SDCard
Reboot in Recovery
Wipe Data / Factory Reset
Optional: convert to F2FS
Select "Install zip from SDCard"
Choose ROM's zip file
Choose GApps zip file
Reboot system
Unfortunately, I am stuck though. I can't put the zip files in my phone because my phone is semi-bricked. I can't access my SD card. I don't have another device that I could plug my SD card into, and I don't have an SD card reader either!
edit: sorry im really like uneasy right now and im thinking that I don't want to lose all my data, so i'm exploring a bit. I booted up CWM because I had a backup made from there. I saw the backup, but when I tried to restore it, it said "MD5 Mismatch" is there ANY way I could get that backup of mine to restore? I would have a peace of mind and then we can restart this process from there.

flipboi15 said:
I am following this:
Code:
TWRP Recovery v2.8.7.0 is suggested for installation
First time or clean install:
Download the ROM from the link above
Download GApps package for Lollipop 5.1
Put the zip files on your SDCard
Reboot in Recovery
Wipe Data / Factory Reset
Optional: convert to F2FS
Select "Install zip from SDCard"
Choose ROM's zip file
Choose GApps zip file
Reboot system
Unfortunately, I am stuck though. I can't put the zip files in my phone because my phone is semi-bricked. I can't access my SD card. I don't have another device that I could plug my SD card into, and I don't have an SD card reader either!
edit: sorry im really like uneasy right now and im thinking that I don't want to lose all my data, so i'm exploring a bit. I booted up CWM because I had a backup made from there. I saw the backup, but when I tried to restore it, it said "MD5 Mismatch" is there ANY way I could get that backup of mine to restore? I would have a peace of mind and then we can restart this process from there.
Click to expand...
Click to collapse
I assume your model is i337M. Check it in download mode. If that's the case, then follow this.
1. Flash this:
http://forum.xda-developers.com/galaxy-s4-att/general/sgh-i337m-canadian-stock-official-t3082758
2. Flash TWRP
3. Flash the rom you want.
That's all. You are making it to difficult.

Lennyz1988 said:
I assume your model is i337M. Check it in download mode. If that's the case, then follow this.
1. Flash this:
http://forum.xda-developers.com/galaxy-s4-att/general/sgh-i337m-canadian-stock-official-t3082758
2. Flash TWRP
3. Flash the rom you want.
That's all. You are making it to difficult.
Click to expand...
Click to collapse
So step 1 and 2 flash that with Odin? Do I wipe or no? If i decide not to wipe, will i still have my old stuff from my phone back?
I am confused with step 3. How do I flash the ROM? Using ODIN? Or TWRP? If its through TWRP, how do I get the ROM in my SD card?
edit: I flashed the first link and this is my log, it failed
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUGOC4_I337MOYAGOC4_I337MVLUGOC4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> cache.img.ext4
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
tried a second time, it still failed
I think my phone is bricked. Its stuck on "firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
latest log im digging myself a deeper hole :
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUGOC4_I337MOYAGOC4_I337MVLUGOC4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Removed!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Added!!

Flashing CM is easy. It doesn't require root access because this phone has no bootloader lock. Download a custom recovery with TAR file format, install drivers, go to the download mode of your phone, connect your phone to your computer, and use Odin to flash the recovery. Then copy CM zip file to a SD card and flash it in recovery. That's all!?
For recovery I recommend TWRP: teamw.in
If you've installed Kies you should have drivers on your computer. Otherwise install Kies or only drivers if you can find them on Samsung official website.

flipboi15 said:
So step 1 and 2 flash that with Odin? Do I wipe or no? If i decide not to wipe, will i still have my old stuff from my phone back?
I am confused with step 3. How do I flash the ROM? Using ODIN? Or TWRP? If its through TWRP, how do I get the ROM in my SD card?
edit: I flashed the first link and this is my log, it failed
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUGOC4_I337MOYAGOC4_I337MVLUGOC4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> cache.img.ext4
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
tried a second time, it still failed
I think my phone is bricked. Its stuck on "firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
latest log im digging myself a deeper hole :
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUGOC4_I337MOYAGOC4_I337MVLUGOC4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Removed!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Added!!
Click to expand...
Click to collapse
Use a different usb port / different usb cable.

Thanks for all the help guys I really do appreciate it and I can't thank you all enough. I have the stock rom working at the moment. I have TWRP installed and I put the ROM and GAPPS into my SD card. I booted into TWRP recovery and clicked on install then i chose the ROM zip but, it fails. This is the error attached picture.

flipboi15 said:
Thanks for all the help guys I really do appreciate it and I can't thank you all enough. I have the stock rom working at the moment. I have TWRP installed and I put the ROM and GAPPS into my SD card. I booted into TWRP recovery and clicked on install then i chose the ROM zip but, it fails. This is the error attached picture.
Click to expand...
Click to collapse
Try redownloading the .zip file. Maybe it's corrupt.

So after trying to install the ROM in TWRP and failing. I couldn't load up the phone anymore, it got stuck at the Samsung Logo screen. I am now re-flashing I337MVLUGOC4 - 5.0.1 Lollipop.
edit:
So at the moment, my phone is working fine on stock rom. I redownloaded the CM-12.1 optimized. I moved it into my SD card. I need to know if there are certain steps I need to do to get this right. These are the steps I took the first time.
Rebooted into TWRP recovery mode, then clicked install then I navigated to the CM-12.1 ROM zip and swiped to install.
Was I supposed to wipe anything? The only time I wiped(the default wipe in twrp) was after I installed the 5.0.1 Lollipop firmware. By the way, i noticed that my phone's internal memory is almost full, it only has 2GB of 9.69GB left in the internal. I checked it out and all my old files were still there!

910c Bootloop stock rom

hi,
i flashed cm13 from here:
http://forum.xda-developers.com/not...-cyanogenmod-13-semi-official-builds-t3259878
then i went back and tried to flash N910CXXU2COJ5_N910COXA2COJ5_XEO via Odin, which was my rom before flashing to cm13
now i am facing a bootloop at "samsung Powered By Android Screen"
i also tried N910CXXU1COI4_N910COXA1COI4_XEO, N910CXXU1COH4_N910COXA1COH4_XEO, i get Fail message from Odin
i redownloaded N910CXXU2COJ5_N910COXA2COJ5_XEO, thinking maybe the file was corrupted during my first download, but still same problem
please help, also please provide me a link to download bootloader and modem
thank you in advance

Update
i downloaded a bootloader and modem from this link:
http://forum.xda-developers.com/note...-team-t3031712 2nd post
but everytime i try to odin the bootloader using BL i get a FAIL messsage below:
<ID:0/003> Removed!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1100)..
<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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Dont try to flash any bootloader below COJ5 as downgrading isn't possible.
Did you do a factory reset when you flashed COJ5 ?

Styrke said:
Dont try to flash any bootloader below COJ5 as downgrading isn't possible.
Did you do a factory reset when you flashed COJ5 ?
Click to expand...
Click to collapse
Thank you for your reply,
Yes, i did a factory rest after flashing COJ5
FYI, i also tried many roms which are based on COJ5 but no luck
The only rom i can flash now is CM13 from here
http://forum.xda-developers.com/not...-cyanogenmod-13-semi-official-builds-t3259878
Your thanks counter was 499, glad to make it 500

bobalyafeai09 said:
Thank you for your reply,
Yes, i did a factory rest after flashing COJ5
FYI, i also tried many roms which are based on COJ5 but no luck
The only rom i can flash now is CM13 from here
http://forum.xda-developers.com/not...-cyanogenmod-13-semi-official-builds-t3259878
Your thanks counter was 499, glad to make it 500
Click to expand...
Click to collapse
If you can boot cm while not stock I would suspect the kernel.
Make sure that the zipped custom rom you tried to flash by recovery has the stock kernel (boot.img) inside in some folder other than "system".And always wipe data/factory reset when coming from non stock.
If it still doesn't help then Im afraid I'll be out of solutions cause I haven't had any experience with locked bootloaders.

Styrke said:
If you can boot cm while not stock I would suspect the kernel.
Make sure that the zipped custom rom you tried to flash by recovery has the stock kernel (boot.img) inside in some folder other than "system".And always wipe data/factory reset when coming from non stock.
If it still doesn't help then Im afraid I'll be out of solutions cause I haven't had any experience with locked bootloaders.
Click to expand...
Click to collapse
It didn't help
Thank you for trying bto help

bobalyafeai09 said:
It didn't help
Thank you for trying bto help
Click to expand...
Click to collapse
Any luck? I'm facing the same problem.

ticiano_arraes said:
Any luck? I'm facing the same problem.
Click to expand...
Click to collapse
So far no luck, will post here if i find anything,
Please let me know if you fine a solution.

bobalyafeai09 said:
So far no luck, will post here if i find anything,
Please let me know if you fine a solution.
Click to expand...
Click to collapse
Hey, try flashing cm13 again and see if your serial number and IMEI are still showing.
Refer to this http://forum.xda-developers.com/showpost.php?p=64327408&postcount=213

Help me root my phone, please.

Hello everyone.
I would really like to be able to remove remove unnecessary, bloatware and energy consuming apps for example google +, hangouts, dropbox,...and maybe even the play store.
I want to take full control of my phone so every piece of information is welcome.
I have a Samsung Galaxy S3 Neo phone with the following specifications:
Model number:
GT-I9301I
Android version:
4.4.2
Android security patch level:
2006-06-01
Baseband version:
I9301IXXUAPG1
Kernel version
3.4.0-6004186
[email protected] #1
Wed Jan 4 19:28:00 KST 2017
Build number:
KOT49H.I9301IXXSAQA1
SE for Android status
Enforcing
SEPF_GT-I9301I_4.4.2_0055
Wed Jun 29 20:36:25 2016
Security software version:
ASKS v1.2_161011

https://forum.xda-developers.com/ga...overy-t-r-p-samsung-galaxy-s3-neo-gt-t2906840
Hopefully its help you !! Cheer bro

I am not sure it's going to work and I really wouldn't like to make my phone useless.
Thanks for your reply though.
mitu725 said:
https://forum.xda-developers.com/ga...overy-t-r-p-samsung-galaxy-s3-neo-gt-t2906840
Hopefully its help you !! Cheer bro
Click to expand...
Click to collapse

Update
P.S. And I don't know if the build number is the same.
I got the impression that it matters and if you don't get the right tools for the exact phone specifications you render you phone useless.
meekss said:
I am not sure it's going to work and I really wouldn't like to make my phone useless.
Thanks for your reply though.
Click to expand...
Click to collapse

Need help with this as well
Basically the same situation as OP, same phone, same build number.
Samsung Galaxy S3 Neo
Model: GT-I9301I
Build: KOT49H.I9301IXXSAQA1
Prior to my rooting attempts I enabled debug mode, installed the USB drivers and made a full backup via MyPhoneExplorer.
I tried rooting it with CF-Auto-Root. Went to the site, selected the correct model and build (it was listed twice, tried both) and downloaded the Auto-Root package as well as the provided original boot and recovery images. When I try to flash the CFAR image.tar.md5 file, Odin initiates the transfer, however it fails to complete the task.
Here is the log:
<ID:0/003> Added!!
<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/003> Odin engine v(ID:3.1203)..
<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> recovery.img
<ID:0/003> cache.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The progress bar stops at around a quarter completed and my phone says "unsupported dev_type" in red letters, rebooting it results in a message that a firmware upgrade encountered a issue and it won't boot.
Thankfully it isn't bricked (yet) as I am able to use Odin to flash the original boot image successfully after which the phone boots normally again.
I tried several versions of Odin all with the same result, I even tried running it in Windows XP compatibility mode which interestingly doesn't make it fail but crash the application at the point where it normally would.
However, that's not helping me getting it rooted so any help would be much appreciated.

Here are the steps:
- install twrp via flashing it with Odin.
- after that make a full backup with twrp just in case
- flash supersu which will give you root (sometimes there is an option in twrp to flash supersu)

Best way to root s3 neo is SuperSU

I had the same version you have, so the solution is:
You'r version cannot be rooted. You have to change it.
Flash this version with Odin you will find on google or here : I9301IXXUANC6 : https://samfrew.com/download/Galaxy__S3__Neo+__/128t/ATO/I9301IXXUANC6/I9301IOXAUANC6/
Then flash recovery to TRWP or something else, then install SuperSu with TRWP recovery or others, and finally flash ROM if you want.
Have fun, tell me if it worked.