Database Users

[Q] help with xnote

hey guys i was wondering if anyone could help me with installing the latest build of xnote 10.0 for my n9005
i am currently using the xnote 7.0 rom which is 4.3
my baseband is n900AUCUBMJ5
kernel is 3.4.0-1625098 [email protected]#1
and my version of xnote is XXUDML2
i currently have safestrap installed as my recovery
i am rooted as well
the xnote note instructions read as the following
"
[SIZE="1"[SIZE="3"]]ONLY IF COMING FROM ANDROID 4.3
FIRST DO THIS, SKIP IF ALREADY DONE CLICK H E R E
So you need a 4.4.2 official firmware already installed, a working KITKAT recovery and ROOT to backup EFS (use chainfire root for KITKAT)
1- Untick reactivation lock in security settings
2- do a EFS backup from your KitKat firmware
3- check the MD5 of your downloaded X-Note zip
4- reboot recovery
5- wipe data (don't do other wipes)
6- install zip and choose the rom in your sd
7- follow aroma, wait for first boot, done.[/SIZE][/SIZE]"
so my question is do i need to follow those instructions in order to flash from the old xnote 7 to xnote 10 and if so where do i find the download link for the 4.4.2 official poland firmware. (will the langauge be in polish) and will it completely wipe my device in any part of this process and do i need to install a different or newer recovery
thanks for all the help in advance
-ben

Omg
Is there a question?

kenny1991 said:
Omg
Is there a question?
Click to expand...
Click to collapse
Yes > >>
so my question is do i need to follow those instructions in order to flash from the old xnote 7 to xnote 10 and if so where do i find the download link for the 4.4.2 official poland firmware. (will the langauge be in polish) and will it completely wipe my device in any part of this process and do i need to install a different or newer recovery
thanks for all the help in advance
-ben
Click to expand...
Click to collapse
theres a couple of threads in the general section of this forum to download 4.4.2 - The language won't be Polish as you get to choose on setup wizard.
It won't wipe your device using Odin to flash it - although it's advisable you do wipe.
Lastest CWM by Chenglu - PhilZ Adavanced CWM - TWRP are all Kitkat compatible now. -- remember you don't need to root to install a custom recovery.

radicalisto said:
Yes > >>
theres a couple of threads in the general section of this forum to download 4.4.2 - The language won't be Polish as you get to choose on setup wizard.
It won't wipe your device using Odin to flash it - although it's advisable you do wipe.
Lastest CWM by Chenglu - PhilZ Adavanced CWM - TWRP are all Kitkat compatible now. -- remember you don't need to root to install a custom recovery.
Click to expand...
Click to collapse
thank you for the help is safestrap 3.71 using twrp v 2.6.3.1 an acceptable recovery to use to flash 4.4.2 and then xnote afterwards?

armadilloben said:
thank you for the help is safestrap 3.71 using twrp v 2.6.3.1 an acceptable recovery to use to flash 4.4.2 and then xnote afterwards?
Click to expand...
Click to collapse
Not 100% sure with using safestrap, you'd have to check the safestrap thread for advice.

flustered
radicalisto said:
Not 100% sure with using safestrap, you'd have to check the safestrap thread for advice.
Click to expand...
Click to collapse
okay in all honesty im becoming frustrated with this whole process could someone possibly reply with clear instructions with exactly what i need to do in order to update xnote 7.0 to xnote 10.0 im getting a tad bit confused as to exactly what i need to do :crying:

armadilloben said:
okay in all honesty im becoming frustrated with this whole process could someone possibly reply with clear instructions with exactly what i need to do in order to update xnote 7.0 to xnote 10.0 im getting a tad bit confused as to exactly what i need to do :crying:
Click to expand...
Click to collapse
Using safestrap automatically throws a spanner in the works due to the way it's handled flashing etc, there won't be a simple way with this but there are ways.

gchat
if anyone would be willing to google hangout chat me or skype me and possibly walk me through this process it would be hugely appreciated all of my usernames are armadilloben

radicalisto said:
Using safestrap automatically throws a spanner in the works due to the way it's handled flashing etc, there won't be a simple way with this but there are ways.
Click to expand...
Click to collapse
well in that case do you know of a way for me to reflash to a different recovery?
im sort of becoming overwhelmed with this process.
i understand how to flash roms pretty well and have been following the xda community for about two years now ive learned and read enough posts to not be a complete idiot anymore. this process however has kinda screwed with my head and im nervous to attempt to update to 10.0 without clearer instructions

ok ii attempted to do it
alrighty so i built up the courage and attempted to flash the poland 4.42 stock rom via odin i checked auto reboot and f. reset time loaded the firemware into AP
i put my phone into download mode plugged it in the my machine tried to start the proceess with odin and i got the following fail error
heres the log:
"<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENB3_N9005OXXENB1_N9005XXUENB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)"
in download mode my phone says the following
"odin mode
product name sm-900a
current binary: samsung official
system status: official
know kernel lock: 0x0
knox warranty void: 0x0
qualcomm securtboot: enable (csb)
rp swrev: s2, t2 , a2 , a2, p2
wirte protection: enable
secure check fail: sbl1
what exactly did i do wrong?

my baseband is n900AUCUBMJ5
Click to expand...
Click to collapse
Which Note do you have? region/model I mean, defo an N9005? -- on first look at that I assume an ATT N900A - possibly wrong tho -

radicalisto said:
Which Note do you have? region/model I mean, defo an N9005? -- on first look at that I assume an ATT N900A - possibly wrong tho -
Click to expand...
Click to collapse
its an att sm n900a so US and ATT

Ah OK thought so, due to the bootloader being locked you can't write to the device hence the error. I wouldn't advise trying to write N9005 ROMs for now. I'm gonna guess however that due to the BL lock and since no 4.4.2 is out yet for the ATT version you won't be able to upgrade because of the requirement for the new 4.4.2 BL to boot up xnote 10.
Your really better off asking on the safestrap thread though as most people in this part won't know due to us having the international model.

radicalisto said:
Ah OK thought so, due to the bootloader being locked you can't write to the device hence the error. I wouldn't advise trying to write N9005 ROMs for now. I'm gonna guess however that due to the BL lock and since no 4.4.2 is out yet for the ATT version you won't be able to upgrade because of the requirement for the new 4.4.2 BL to boot up xnote 10.
Your really better off asking on the safestrap thread though as most people in this part won't know due to us having the international model.
Click to expand...
Click to collapse
so your saying that even though i installed the xnote 7.0 that 10.0 wont work because i need the bootloader unlocked. and how the hell did i install 7.0 if it was locked in the first place?

armadilloben said:
so your saying that even though i installed the xnote 7.0 that 10.0 wont work because i need the bootloader unlocked. and how the hell did i install 7.0 if it was locked in the first place?
Click to expand...
Click to collapse
7 used 4.3's Bootloader IIRC, 8 onwards uses the new KK bootloader. ATT has the JB bootloader, but doesn't yet have access to the new 4.4.2 bootloader.

radicalisto said:
7 used 4.3's Bootloader IIRC, 8 onwards uses the new KK bootloader. ATT has the JB bootloader, but doesn't yet have access to the new 4.4.2 bootloader.
Click to expand...
Click to collapse
ahhhh okay that makes sense to me. so basically am i SOL until i can get an official att 4.42 stock rom?

armadilloben said:
ahhhh okay that makes sense to me. so basically am i SOL until i can get an official att 4.42 stock rom?
Click to expand...
Click to collapse
I think so

radicalisto said:
I think so
Click to expand...
Click to collapse
crap that makes me very frustrated do you know if i can move to cyanogenmod 11 with my locked bl?
if not i really appreciate the help brother, its nice to know there really are people will to help all the time here

In regards to CM - I honestly have no idea if it's compatible with the ATT model - but from having a quick glance around the ATT Note 3 forum I can't see that it is. And checking the new unified build tree it shows it's only compatible with "hltespr(Sprint), hltetmo(T-Mobile), hltevzw(Verizon), htlexx(N9005) - However, that's not to say that there is no definite method. One may come via Safestrap or possibly already and I have just missed it.
No problem with helping, just sorry couldn't help you get xnote 10

radicalisto said:
In regards to CM - I honestly have no idea if it's compatible with the ATT model - but from having a quick glance around the ATT Note 3 forum I can't see that it is. And checking the new unified build tree it shows it's only compatible with "hltespr(Sprint), hltetmo(T-Mobile), hltevzw(Verizon), htlexx(N9005) - However, that's not to say that there is no definite method. One may come via Safestrap or possibly already and I have just missed it.
No problem with helping, just sorry couldn't help you get xnote 10
Click to expand...
Click to collapse
its alright not your fault and alrighty i mean ive searched around for cm for att and didnt find it either.
in all reality i just wanted 10.0 to get 4.42 because i assumed that my battery drain would be better on it. i love 7.0 its a great rom i just wish there was a real fix for my audio out wakelock issues that suck my battery dry. i have a 10,000ma zero lemon battery on my phone and it still only lasts me about a day. like its at about 20 percent when i charge it before bed every night

[Q] Soft Bricked sgh-i337m. Please Help

Please lend a hand to help me rectify a problem.
Started earlier today by CF-Auto-Root my New Rogers SGH-i1337m, installed without incident via Odin 3.07, followed up with TWRP 2.7 install, again via Odin, without incident, then created NANDROID backup to ext sdcard.
First issues started cropping up, but culminating in what appears to be soft bricking:
1st) Could not mount internal memory (was attempting to browse in Windows) via TWRP. Every time I would select internal memory it would mount the sd card contents only. Weird, but pales compared to further issues.
2nd) Was preparing to install Custom ROM, boot into TWRP, attempted factory reset but this just constantly restarted TWRP. Thought this was strange so I figured Id use Goomanager to update TWRP, occurred without incident and I went back to attempt to factory reset, but then trouble started.
3rd) Boot looping, could not boot back into the OS. Decided I would attempt to restore my Nandroid backup, TWRP loads fine but restore didn't work. Figured Id try flashing back to stock rom (obtained RWC-I337MVLUEMK6-20131125124040 via links in other comments. This is where things got out of control:
A) Restore via Odin 3.07 failed, device restart failedbut loaded the "Firmware Upgrade encountered an issue..." screen.
B) Attempted redownloading the stock rom, new usb port, new oem cable, reinstalled drivers, and with each Odin would fail as follows:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUEMK6_I337MOYAEMK6_I337MVLUEMK6_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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
C) Briefly TWRP would not load, so I reflashed 2.7.0.1 for openrecovery-twrp-2.7.0.1-jfltecan without incident, TWRP reloaded fine, could now do factory reset, but often end up getting could not mount /system. Now using TWRP to restore theNANDRPID from earlier seemed to rebuild the partitions and said it was successful, and the device will boot to a static Samsung screen, but after 20 mins of waiting, would not boot farther.
D) At this point tried to reflash w Odin 3.07 the stock, but still get that error.
So here is where I'm at, with what appears to get me the closest to booting/flashing with stock:
1) Reflashed openrecovery-twrp-2.7.0.1-jfltecan.tar with Odin 3.07, immediately following this:
<ID:0/004> Removed!!
<ID:0/006> Added!!
<ID:0/006> Removed!!
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
..and the device hangs @ "Samsung Galaxy S4" black screen, letting that sit for 15mins without any change (didn't expect it to, but may as well be complete).
2) TWRP is bootable (load screen says Recovery is not SEANDROID ENFORCED and Set Warranty Bit: recovery) and functional, rebooting recovery states "No OS installed, are you sure you want to restart? ". Interestingly with 2.7.0.1 now installed, i can factory reset but with errors "E: unable to mount '/system". In TWRP, i have tried restore of my NANDROID backup, it completes successfully and appears to rebuild the partitions, but even after completing the restore and rebooting, still end up hanging at the static Samsung screen for >20mins without a change. I could transpose the entire log from the restore if needed.
3) At this point I would try Odin 3.07 with the above stock image, and the failure when attempting to write system occurs again.
Ive been searching for hours and hours and attempting to reflash but not making any headway.
Could anyone help point me in some better directions? I just finished attempting KIES emergency restore, but it too failed when it tried to upload to the device.
Any help would be greatly appreciated.

You've done all the right things. The only other thing I can think of is using a different firmware version in Odin.
Sent from my Nexus 5

jd1639 said:
You've done all the right things. The only other thing I can think of is using a different firmware version in Odin.
Sent from my Nexus 5
Click to expand...
Click to collapse
Perhaps I should try flashing a custom rom? Maybe something like CM 10.2?
I think the problem lies with a possible permission problem with the system partition, but I don't know how to go about checking those permissions, let alone correcting a possible fault.
Thoughts?

Did you factory reset in stock recovery before you installed twrp?
Sent from my SGH-I337M using Tapatalk

2Tone5 said:
Did you factory reset in stock recovery before you installed twrp?
Sent from my SGH-I337M using Tapatalk
Click to expand...
Click to collapse
I believe so, but it has been several iterations of different attempts to fix things that I cannot be certain any longer.
Let's pretend I didn't, for arguments sake. Implications?
Furthermore, I have created some life back into the device; however, still having problems.
1) Using ODIN 3.09, I successfully flashed TWRP back on to the device.
2) With TWRP, I successfully flashed CM 10.2. The device loads completely into the OS--the only thing I cannot confirm yet is full telephone functionality as my backup phone is what was reconnected to ROGERS. So.....there is life in this thing yet.
3) With TWRP, I have successfully created NANDROID backup of the device under 10.2 and used it to restore after a few failed attempts at getting to stock.
So here's a problem for right now: No matter what source stock ROM I have been using, I337MVLUFNC1_I337MOYAFNC1_I337MVLUFNC1_HOME.tar.md5 or I337MVLUFNC1_880525_REV06_user_low_ship_MULTI (both are what were claimed to be stock 4.4.2 for sgh-i337m ROGERS), it consistently fails in ODIN when flashing system.
I can easily then reflash TWRP (because the ODIN flashing the above stock breaks the recovery image), get into TWRP and restore the CM10.2 NANDROID, and at least back in business there.
I'm about to try flashing (again, but likely fruitlessly) RWC-I337MVLUEMK6-20131125124040.zip from samsung-updates.com via ODIN 3.09. I don't have much hope that ODIN will get it onto the device.
Seems to me like perhaps ODIN can't get the stock roms onto the device for some reason!? Am I doing something wrong? Perhaps someone can point me to a stock 4.3 (or 4.4.2) ROM for ROGERS SGH-i337M that is known to work (or at least deemed reliable) that I could try? Perhaps ODIN is messed up for me?
I'm pretty frustrated as I would think if I can install via TWRP a custom kernel and custom ROM, I should be able to get the stock ROM/etc. back onto the device.
Perhaps I'm missing a step?
TWRP: Wipe> Factory Reset then wipe Cache.
Reboot into Download Mode
ODIN 3.09: Added!! --> AP Select my stock ROM (any of the above), only have Auto Reboot and F. Reset Time selected, start (then fail in my case).
Perhaps I should find another computer!? I have two OEM cables, tried both ports......
This is ridiculously frustrating.

Which bootloader are you on?
Sent from my SGH-I337M using Tapatalk

Just wanted to say that I got burned by TRWP a few days ago due to the same issues.
1) Flashed a custom kernel days before. Was working fine but didn't like the performance of the new kernel so I decided to restore my backups of /boot and /system.
2) Did the restore. Cleared /cache and dalvik. Reboot.
3) Stuck on the Samsung Galaxy S4 bootloader screen.
4) Tried to reboot into TWRP, but didn't work. Would just cause phone to automatically restart and hang at the bootloader screen.
5) After many many reboots, was able to finally boot into TWRP.
6) Flashed a custom ROM based the original stock ROM I had installed and that got me up and running again. No data loss as I never touched /data with TWRP.
I'm currently experimenting with CWM and Philz. TWRP, never again.

2Tone5 said:
Which bootloader are you on?
Sent from my SGH-I337M using Tapatalk
Click to expand...
Click to collapse
Uncertain at this point -- any way to determine that or just flash a known decent one?
Interestingly: CM10.2.1 everything works except for calls and any other sound on the device. ......this is ridiculous.

bzwick said:
Uncertain at this point -- any way to determine that or just flash a known decent one?
Interestingly: CM10.2.1 everything works except for calls and any other sound on the device. ......this is ridiculous.
Click to expand...
Click to collapse
Upon more research, I guess I have a knox bootloader since I have a Knox 0x1 trip.

bzwick said:
Upon more research, I guess I have a knox bootloader since I have a Knox 0x1 trip.
Click to expand...
Click to collapse
Without knowing exactly, theres more trial and error ... so ill give you an example: you can't flash 4.2.2 firmware.tar.md5 over a 4.4.2 bootloader (which sounds like you may have )in odin anymore due to knox. What I can suggest to you that should work is go to sammobile.com and download the latest 4.4.2 official firmware for the 1337m and follow the instructions precisely on the download page.
Sent from my SGH-I337M using Tapatalk
---------- Post added at 12:14 AM ---------- Previous post was at 12:12 AM ----------
http://www.sammobile.com/firmwares/
Sent from my SGH-I337M using Tapatalk
---------- Post added at 12:16 AM ---------- Previous post was at 12:14 AM ----------
Once you download it and its installed make sure to turn off your phone and boot into stock recovery and do a factory reset and if you really want to be clean flash the firmware again and all your problems should be gone
Sent from my SGH-I337M using Tapatalk

2Tone5 said:
Without knowing exactly, theres more trial and error ... so ill give you an example: you can't flash 4.2.2 firmware.tar.md5 over a 4.4.2 bootloader (which sounds like you may have )in odin anymore due to knox. What I can suggest to you that should work is go to sammobile.com and download the latest 4.4.2 official firmware for the 1337m and follow the instructions precisely on the download page.
Sent from my SGH-I337M using Tapatalk
---------- Post added at 12:14 AM ---------- Previous post was at 12:12 AM ----------
http://www.sammobile.com/firmwares/
Sent from my SGH-I337M using Tapatalk
---------- Post added at 12:16 AM ---------- Previous post was at 12:14 AM ----------
Once you download it and its installed make sure to turn off your phone and boot into stock recovery and do a factory reset and if you really want to be clean flash the firmware again and all your problems should be gone
Sent from my SGH-I337M using Tapatalk
Click to expand...
Click to collapse
Ok, I'll give it a go and report findings as follows (decided to try a different computer to eliminate that fact too):
1) sammobile.com --> http://www.sammobile.com/firmwares/3/?download=26590 - PDA - I337MVLUFNC1, CSC - I337MOYAFNC1, etc.
2) Downloaded and installed fresh 3.09 from sammobile per instructions.
3) Successfully flashed this firmware, phone returning back to normal as official kernel and official rom, knox warranty tripped still, but that's the way it goes.
SO: Moral of the story - ensure that not just using any kind of virtualization software to try and do flashing, use a proper PC. I hope somehow this finds its way to some other schlub that messes this up.
ROGERS is sending me a new phone anyway other problems involving sound and I was within 15 day return. Lucky me I guess...
I guess the next time around I'll need a closer look at avoiding knox tripping...

It works for me
2Tone5 said:
[/COLOR]Once you download it and its installed make sure to turn off your phone and boot into stock recovery and do a factory reset and if you really want to be clean flash the firmware again and all your problems should be gone
Sent from my SGH-I337M using Tapatalk
Click to expand...
Click to collapse
Thank you!! It works for me. It's very important to do a clean flash. :good:

I am having a crazy issue I can't seem to fix with my i337. I am trying to revert back to stock and I ran odin I get a pass notification but when I reboot my phone prompts that I have unauthorized software on my phone an to contact AT&T. I can't seem to make this work and I can't boot into recovery. Any ideas on what may help. Feeling pretty lost at this point.

Bricked Device

Hey Guys,
i have a Samsung Galaxy s4 i9505 LTE and i stayed a long time with Slimkat ROM which was 4.4.4, so i wanted to flash the offical stock rom 4.4.2 via odin and it says failed and when i start my phone it says: Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. The bootloader calls:
Product Name: GT-I9505
Current Binary: Samsung offical
System Status: Custom
Knox Kernel lock: 0x0
Knox Warranty Void: 0x1
CSB-Config-LSB: 0x30
Write Protection: Enable
eMC Burst Mode: Enable
Is it maybe knox blocked the downgrade? Should i flash the offical Lollipop firmware or what?
so could someone please help im so mad and frustrated.

What error did you get in Odin? Where did you get the stock Odin ROM?

audit13 said:
What error did you get in Odin? Where did you get the stock Odin ROM?
Click to expand...
Click to collapse
hey thank you for your answer odin says:
<ID:0/004> Added!!
<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/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!

audit13 said:
What error did you get in Odin? Where did you get the stock Odin ROM?
Click to expand...
Click to collapse
i downloaded the stock rom from sammobiles a long time ago, so right im downloading another stock rom from sammobiles which is I9505XXUGNG8 same as the slimkat version and hopefully get it worked

audit13 said:
What error did you get in Odin? Where did you get the stock Odin ROM?
Click to expand...
Click to collapse
i also used odin version 3.10.7

It could be that the ROM you are trying to flash has bootloader that is older than the ROM currently on the phone. You could try flashing the latest ROM as the latest ROM would have a bootloader, modem, etc. that is the same or newer that the bootloader currently on the phone.

audit13 said:
It could be that the ROM you are trying to flash has bootloader that is older than the ROM currently on the phone. You could try flashing the latest ROM as the latest ROM would have a bootloader, modem, etc. that is the same or newer that the bootloader currently on the phone.
Click to expand...
Click to collapse
So should i flash the latest stock rom?

Here's a test:
download the latest Odin-flashable TWRP for your phone;
open Odin and uncheck everything except f.reset time;
connect the phone and flash TWRP;
when you see the word "reset" in the status window, remove the USB cable, remove battery, replace battery;
use button combination to try and boot into recovery.
If you can boot into recovery, flash a CM ROM, install Samsung Phone Info app from the play store. This app will confirm the modem and bootloader on the phone.

audit13 said:
Here's a test:
download the latest Odin-flashable TWRP for your phone;
open Odin and uncheck everything except f.reset time;
connect the phone and flash TWRP;
when you see the word "reset" in the status window, remove the USB cable, remove battery, replace battery;
use button combination to try and boot into recovery.
If you can boot into recovery, flash a CM ROM, install Samsung Phone Info app from the play store. This app will confirm the modem and bootloader on the phone.
Click to expand...
Click to collapse
thank you for your help i will try it right now and post a reply if it worked
i got one another question, can i flash again the slimkat rom trough recovery if i got twrp?

If TWRP works, you can use it to flash any custom ROM that is designed for your phone.

audit13 said:
If TWRP works, you can use it to flash any custom ROM that is designed for your phone.
Click to expand...
Click to collapse
ok can i also flash also other recovery instead of twrp like cwm ?

audit13 said:
If TWRP works, you can use it to flash any custom ROM that is designed for your phone.
Click to expand...
Click to collapse
could maybe send me a link of the right twrp for my phone because i dont want to make my phone useless,sorry for my stupid questions but i really afraid right now

This TWRP is for the i9505 International s4 with qualcomm processor: https://dl.twrp.me/jfltexx/twrp-2.8.6.0-jfltexx.tar.html
The latest tar version is 2.8.6.0. There is a 2.8.7.0 version but it is in an img format. You can use cygwin to convert the file from img to tar for flashing in Odin.
I recommend TWRP as many ROMs require it as the recovery program.

audit13 said:
This TWRP is for the i9505 International s4 with qualcomm processor: https://dl.twrp.me/jfltexx/twrp-2.8.6.0-jfltexx.tar.html
The latest tar version is 2.8.6.0. There is a 2.8.7.0 version but it is in an img format. You can use cygwin to convert the file from img to tar for flashing in Odin.
I recommend TWRP as many ROMs require it as the recovery program.
Click to expand...
Click to collapse
thank u so much im gonna try it right now hopefully it will work

audit13 said:
This TWRP is for the i9505 International s4 with qualcomm processor: https://dl.twrp.me/jfltexx/twrp-2.8.6.0-jfltexx.tar.html
The latest tar version is 2.8.6.0. There is a 2.8.7.0 version but it is in an img format. You can use cygwin to convert the file from img to tar for flashing in Odin.
I recommend TWRP as many ROMs require it as the recovery program.
Click to expand...
Click to collapse
omg it worked i got the recovery thank you so much for your help i pressure it man :**** im so happy right now

Awesome. Glad you got it working.
Next step: install a custom ROM and confirm your bootloader and modem.

audit13 said:
Awesome. Glad you got it working.
Next step: install a custom ROM and confirm your bootloader and modem.
Click to expand...
Click to collapse
ok i want to install slimkat jflte but there is also jfltexx so im really confused which one i should choose?

I believe the jflte should work. Look under i9505 development for other ROMs too.

audit13 said:
I believe the jflte should work. Look under i9505 development for other ROMs too.
Click to expand...
Click to collapse
thank u slimkat is the best for my phone and i successfully got my phone work thank u so much for your time and your help :*

You're very welcome. We are all here to help and share our knowledge.

Newbie Help ! Flash i337 ATT To stock then to Android 7

Ok ive never messed with android before, and have spent hours n hours etc reading and trying things... and have failed ;(
Tried to play with TWRP or whatever etc... that didnt work
Ive got a S4 ATT i337 that is on 4.2.2 it has some custom FW on it and its UNLOCKED.
I was using this a while back on TMOBILE so it IS unlocked (from AT&T)...
Ive tried to boot into recovery to SET IT BACK to STOCK (1st) then (so I could put it on 7.1)
I get a ATTENTION message that appears and says: System software not authorized by AT&T has been found on your phone. Please turn off and goto the nearest at&t store... (not happing haha)
I Have found the original FW for my ATT I337...
If anyone can help me in simple english of HOW to etc It would be a big xmas present to me !!!
Thanks in advance

Is the bootloader locked? If yes, you cannot run custom roms based on anything other than a stock Samsung rom.

Could you tell me how I can check to see if the bootloader is locked ? and I will
I read something somewhere about the baseband it ends in MF3
and Kernal version 3.4.0-812098
I dont know WHICH or WHAT ROM is loaded onto it but it IS version 4.2.2 android
audit13 said:
Is the bootloader locked? If yes, you cannot run custom roms based on anything other than a stock Samsung rom.
Click to expand...
Click to collapse

Transam98 said:
Could you tell me how I can check to see if the bootloader is locked ? and I will
I read something somewhere about the baseband it ends in MF3
and Kernal version 3.4.0-812098
I dont know WHICH or WHAT ROM is loaded onto it but it IS version 4.2.2 android
Click to expand...
Click to collapse
Download terminal emulator app from play store. Open it and type "getprop ro.bootloader" without the " "
It will give you some letters and numbers. If the last 3 are anything but MDL or MDB then your bootloader is locked and you have to use safe strap and can only boot Samsung ROMs.

Stoney: Thanks for the reply... So I got the terminal an it replied I337UCUAMF3...
Can you tell me the next step ?
(Ill google and get SAFE STRAP)....
what file would I use with safestrap ? Can I still put Android 7.1 on this ?
Thanks in advance !!
StoneyJSG said:
Download terminal emulator app from play store. Open it and type "getprop ro.bootloader" without the " "
It will give you some letters and numbers. If the last 3 are anything but MDL or MDB then your bootloader is locked and you have to use safe strap and can only boot Samsung ROMs.
Click to expand...
Click to collapse

If the bootloader is locked, and it looks to me like it is, you wont' be able to install Nougat or MM ROMs.

understandable ! Thanks for the info !!
So I have android 4.2.2 on it now (remember at&t i337 S4)....
is there a newer ROM like android 5 or 6 I can put onto it ? (stock ?)
I DID get safestrap and installed that
audit13 said:
If the bootloader is locked, and it looks to me like it is, you wont' be able to install Nougat or MM ROMs.
Click to expand...
Click to collapse

Don't think there is any custom MM but there may be a custom LP but a custom LP may require an updated bootloader and modem.
I would consult the ROM threads located here: http://forum.xda-developers.com/galaxy-s4-att/development/rom-resurrectionremix-5-7-4-t3476519

well I screwed up LOL ;(
I did a backup of my ROM with safestrap (its on the SD Card) and tried to write the file and now phone is stuck on attention yellow symbol ;(
I CAN boot into the DOWNLOADING but odin just sits there ;(
I guess phone now = garbage ;(
audit13 said:
Don't think there is any custom MM but there may be a custom LP but a custom LP may require an updated bootloader and modem.
I would consult the ROM threads located here: http://forum.xda-developers.com/galaxy-s4-att/development/rom-resurrectionremix-5-7-4-t3476519
Click to expand...
Click to collapse

does the phone appear as a com port in Odin? You're using the original Samsung USB cable?

the phone DOES appear in odin
Im using a motorla cable but does still fully work....
I also can get the phone into DL mode (pwr down,home,power)
and it WILL take a Download....
when it boots up it does says SAMSUNG and CUSTOM and a UNLOCKED Padlock...
But I guess I cant find the correct files ;( as it always goes to the attention from att detected blah blah blah software....
Id just be happy to get this to the newest ATT Stock FW and then unlock it I believe it is called 4.4.2 and im on 4.2
or IF it exists would be nice to get to at least 5.0 to use android auto
audit13 said:
does the phone appear as a com port in Odin? You're using the original Samsung USB cable?
Click to expand...
Click to collapse

Did you try flashing a stock rom from sammobile.com?

Ive downloaded : I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5
(from sammobile)... 2.49Gb
but rememeber my bootloader says (ends in MF3) and the only TWO on sammobile are MDL and MDB..
but of course the file name has MDB in it..... I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5
I loaded it in Odin3 (run as admin) and clicked AP and loaded it there, and it fails:
<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> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Id really love to get this going If you or someone can help/make suggestions for me to try as im pulling my hair out ;(
audit13 said:
Did you try flashing a stock rom from sammobile.com?
Click to expand...
Click to collapse

Bootloader is definitely locked based on Odin log.
This may help to restore the phone and upgrade the rom: http://forum.xda-developers.com/gal...-to-update-to-i337oc3-5-0-1-keeproot-t3075814

is there anything I can do ? It DID have a custom rom on it (well when it starts booting it says CUSTOM and has a padlock unlocked) and it was also unlocked (not stuck to at&t)... but now im just stuck with that attention logo ;(
audit13 said:
Bootloader is definitely locked based on Odin log.
This may help to restore the phone and upgrade the rom: http://forum.xda-developers.com/gal...-to-update-to-i337oc3-5-0-1-keeproot-t3075814
Click to expand...
Click to collapse

I'm not sure how the phone had a custom rom and a locked bootloader and now has a locked bootloader.
Which rom was on the phone running?

I believe it was somewhat a stock firmware, nothing looked "fancy" compared to a regular at&t firmware but it was DEF unlocked as I used to have a tmobile sim in it ....
but it still boots up with SAMSUNG and a unlocked padlock and then the samsung ring animation, then the AT&T logo, now it just boots u the samsung unlock "custom" and then to the yellow exclamation point about non at&t software.
audit13 said:
I'm not sure how the phone had a custom rom and a locked bootloader and now has a locked bootloader.
Which rom was on the phone running?
Click to expand...
Click to collapse

Were you able to try the methods outlined in the referenced thread to revive and update the phone?

I tried them but none of them work
audit13 said:
Were you able to try the methods outlined in the referenced thread to revive and update the phone?
Click to expand...
Click to collapse

Samsung S4 SGH I337(Don't know the PDA it's running on) hangs on AT&T logo.

Dear All,
I have been reading many threads for a week before I decided to post a new thread here.
I am running in a big problem here with my S4 SGH-I337 which I have. I have never updated it with any version and it's hanging on it's ATT logo. I have tried all the factory and data reset options which I have come across on this forum, but the phone didn't come back to life.
Then I tried to flash it with Odin using I337UCUAMDB tar file(Since the phone is not working I couldn't find the PDA its running on), but it's failing saying FAIL! (Auth). Since I am doing it first time and I don't know much about flashing things, I am stuck out here. After doing some research I found that I should flash it with the PDA version matching to my phone but since my phone is not booting up I am not sure how can i find the PDA version for my phone. Even I have tried reaching to SAMSUNG's authorized center but they replied, as you are in INDIA and your phone was purchased when you were in USA, so we don't have that software to repair it. Please help me as I don't know what to do this phone now. Your help would be greatly appreciated.

Have you tried to ODIN the MDL firmware instead of the MDB firmware? It might be on MDL if you never updated it. When you get it working my advice is DO NOT take any OTA firmware updates until you know what bootloader you're on. If it is MDL then NEVER update it because the MDL bootloader had a flaw in it that can be exploited by using Loki doki to allow you to boot custom ROM and recovery.

StoneyJSG said:
Have you tried to ODIN the MDL firmware instead of the MDB firmware? It might be on MDL if you never updated it. When you get it working my advice is DO NOT take any OTA firmware updates until you know what bootloader you're on. If it is MDL then NEVER update it because the MDL bootloader had a flaw in it that can be exploited by using Loki doki to allow you to boot custom ROM and recovery.
Click to expand...
Click to collapse
Thank You! so much StoneyJSG, Actually I have come across one post that says never update it on if you have MDB/MDL firmware, so I got scared and didn't try anything. As your advice let me try using MDL firmware, hopefully that should work if you are advising it. Just to confirm it once if I get successful then I would be able to update it with custom ROM as you mentioned.

mahendra_bhawsar said:
Thank You! so much StoneyJSG, Actually I have come across one post that says never update it on if you have MDB/MDL firmware, so I got scared and didn't try anything. As your advice let me try using MDL firmware, hopefully that should work if you are advising it. Just to confirm it once if I get successful then I would be able to update it with custom ROM as you mentioned.
Click to expand...
Click to collapse
Yeah try the MDL firmware in ODIN. Only the MDB and MDL firmware can use a custom ROM with loki doki. Don't flash any other firmware or else you won't be able to use loki doki and will be forced to use safe strap recovery instead of TWRP which can only boot custom Samsung ROM.

StoneyJSG said:
Yeah try the MDL firmware in ODIN. Only the MDB and MDL firmware can use a custom ROM with loki doki. Don't flash any other firmware or else you won't be able to use loki doki and will be forced to use safe strap recovery instead of TWRP which can only boot custom Samsung ROM.
Click to expand...
Click to collapse
@StoneyJSG, Really appreciate your quick responses and the value of this forum. I had been gone in a complete frustration from past one week but now I am having hope to get the phone working. Trying to download I337UCUAMDL and flash it through ODIN ? Thank You! so much once again.

Does the phone say anything about Knox in the download screen where you see the model #?
The phone is definitely the sgh-i337 on the download screen?

mahendra_bhawsar said:
@StoneyJSG, Really appreciate your quick responses and the value of this forum. I had been gone in a complete frustration from past one week but now I am having hope to get the phone working. Trying to download I337UCUAMDL and flash it through ODIN ? Thank You! so much once again.
Click to expand...
Click to collapse
I downloaded I337UCUAMDL firmware from http://stockroms.net/file/GalaxyS4/SGH-I337/I337UCUAMDL_I337ATTAMDL_ATT.zip but when I flesh it using ODIN it says FAIL(!Auth). Here is the ODIN Log: <ID:0/004> Added!!
<ID:0/004> Removed!!
<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/004> Added!!
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Please help me what should I do in this case.

audit13 said:
Does the phone say anything about Knox in the download screen where you see the model #?
The phone is definitely the sgh-i337 on the download screen?
Click to expand...
Click to collapse
Nope, It does not say anything about Knox in the download screen. I see model number(SGH-I337) on the hardware underneath the battery.
Thank You!

The aboot.mbn file is not flashing because the bootloader in the phone is newer than the bootloader in the rom, the bootloader is not meant for the phone, or you need to use a different usb cable or usb port.

audit13 said:
The aboot.mbn file is not flashing because the bootloader in the phone is newer than the bootloader in the rom, the bootloader is not meant for the phone, or you need to use a different usb cable or usb port.
Click to expand...
Click to collapse
I think I have purchased this cell phone back in Sept 2013, that time I believe AT&T had the following versions:
Build Date: 27.04.2013 -> Region: ATT (AT&T) PDA: I337UCUAMDL Changelist: 453947 Android: 4.2.2
Build Date: 09.04.2013 -> Region: ATT (AT&T) PDA: I337UCUAMDB Changelist: 440216 Android: 4.2.2
I tried both of them using both the ports of my laptop with different USB Cables(Original cable from Sony, Samsung and Moto G), but every time I got the same Odin Fail (!Auth) error. I am not sure whats the wrong here or what should I do to resolve this error and get the phone working.
Thank You!

What version of android was on the phone when you bought it?
Do you see anything about warranty bit in download mode?

audit13 said:
What version of android was on the phone when you bought it?
Do you see anything about warranty bit in download mode?
Click to expand...
Click to collapse
I think it was Android 4.2.2, this is what the download mode says:
ODIN MODE
PRODUCT NAME: SGH-I337
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNAL LOCK: 0*0
KNOX WARRANTY VOID: 0*0
CSB-CONFIG-LSB: 0*30
WRITE PROTECTION: Enable
eMMC BURST MODE enabled
Thank You!

The fact that you see "Knox" on the screen indicates this:
1) the phone has a locked bootloader;
2) you cannot flash any stock rom that is older than 4.3. If you try, Odin will not flash the aboot.mbn file which is an old bootloader; and
3) the phone must have been running at least a 4.3 or newer rom.

audit13 said:
The fact that you see "Knox" on the screen indicates this:
1) the phone has a locked bootloader;
2) you cannot flash any stock rom that is older than 4.3. If you try, Odin will not flash the aboot.mbn file which is an old bootloader; and
3) the phone must have been running at least a 4.3 or newer rom.
Click to expand...
Click to collapse
Ohh I understand this now. But knox says 0*0 bit still it means it has a locked bootloader ? I think may be it was running on 4.3 before it crashed, may be I had got some update on 4.2.2 and that made it got updated on 4.3 which I didn't re-collect. What should I do now, which ROM you would suggest me to flash it with. Really appreciate your help.
Thank You!

If the was never updated to 4.3 or newer, you would not see the word "Knox" in download mode.
This may help: https://forum.xda-developers.com/showthread.php?t=2616221

audit13 said:
If the was never updated to 4.3 or newer, you would not see the word "Knox" in download mode.
This may help: https://forum.xda-developers.com/showthread.php?t=2616221
Click to expand...
Click to collapse
It has lots of ROMS and instructions to follow, I am a novice user in this so got confused what to do and what not. Even I don't know my current baseband version so unable to choose firmware or method to flash it in order to get it working. Any help from your side on this front ?
Thank You!

You could try this: https://forum.xda-developers.com/galaxy-s4-att/development/rom-100-stock-i337oc3-5-0-mdl-t3098197

audit13 said:
You could try this: https://forum.xda-developers.com/galaxy-s4-att/development/rom-100-stock-i337oc3-5-0-mdl-t3098197
Click to expand...
Click to collapse
My phone is in hanging state on boot loop won't be able to perform the steps mentioned on that link like : 1. Place the ROM onto your device (use either internal or ext-sdcard). etc... Any other suggestion please ?

You could downloading this file and flashing it with Odin: https://androidfilehost.com/?fid=23501681358540571
I found the link by googling around. I can't try the file because I don't the i337, I only have the i337m.

audit13 said:
You could downloading this file and flashing it with Odin: https://androidfilehost.com/?fid=23501681358540571
I found the link by googling around. I can't try the file because I don't the i337, I only have the i337m.
Click to expand...
Click to collapse
Great! Thanks I am trying to download it, it will take time since my network is a bit slow, will let you know if that works, hopefully it should.