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
Related
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
Summary: I tried to root my 4.4.2 S4 using an incompatible method by mistake. The phone now has no OS and I am having trouble flashing the stock firmware. When the phone powers on, I see "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
The following describes the state the phone was in before the problems occurred...
Model: SGH-I337
Model name: GALAXY S4
Country: USA (AT&T)
Version: Android 4.2.2
Product Code: ATT
PDA: I337UCUAMDL
CSC: I337ATTAMDL
MODEM: I337UCUAMDL
Drivers were properly installed. I had both the Samsung and ADB interface drivers properly installed.
The knitty gritty...
This all started when I attempted to root the phone using djrbliss Saferoot method. Due to there being so many versions of the S4, I misinterpreted the post by djrbliss. Apparently, this method is not compatible with 4.4.2. I attempted to run the .bat file for this method, it hung indefinitely and I killed it. I rebooted the phone and began experiencing issues with my data network. I assumed at this point that the modem had been messed up.
After my failure with Saferoot, I tried to flash back to stock and fix the modem using the files in this thread. I believe some of these files were written successfully, but not all of them because after I booted into Windows, drivers were automatically installed for MSM8960 (snapdragon processor), Samsung Mobile USB CDC Compsite device, Serial gadget driver, Samsung modem.
I tried flashing the I337UCUAMDL firmware but it wouldn't write either.
As a last desperate resort I tried to use Kies to restore the firmware but it wouldn't automatically detect the device so I tried to initiate it manually using the device serial number. The application stopped responding and then the phone had no OS at all.
I am desperately in need of help and will offer a reward (to be sent via paypal) to anyone that can help me.
1. I supose u want keep ur warranty.
2. Go to STOCK RECOVERY (button home + button up + Power button) (like 1st pic)
3. You will see some options there (Wipe all -> wipe data/factory reset + wipe cache partition)
4. Reboot ur phone in DOWNLOAD MODE
5. Open Odin 3.09
6. Flash the firmware u have again -> I337UCUAMDL (like in the 2nd pic attached)
7. Tell me how it works.
Joku1981 said:
1. I supose u want keep ur warranty.
2. Go to STOCK RECOVERY (button home + button up + Power button) (like 1st pic)
3. You will see some options there (Wipe all -> wipe data/factory reset + wipe cache partition)
4. Reboot ur phone in DOWNLOAD MODE
5. Open Odin 3.09
6. Flash the firmware u have again -> I337UCUAMDL (like in the 2nd pic attached)
7. Tell me how it works.
Click to expand...
Click to collapse
I traded for it locally so I could care less about the warranty. I think I may have broken the recovery image because I can't get it to boot into recovery, but I can get it to boot into download mode. Is there any other way to clear the cache?
Thanks for your help.
goose90proof said:
I traded for it locally so I could care less about the warranty. I think I may have broken the recovery image because I can't get it to boot into recovery, but I can get it to boot into download mode. Is there any other way to clear the cache?
Thanks for your help.
Click to expand...
Click to collapse
You will have to flash custom recovery then but this supose lose the warranty.
*EDIT: Before this step, better try to flash the firmware u had before in DOWNLOAD MODE by ODIN
Joku1981 said:
You will have to flash custom recovery then but this supose lose the warranty.
*EDIT: Before this step, better try to flash the firmware u had before
Click to expand...
Click to collapse
Ok so flash clockwork or teamwin right?
I've tried flashing the firmware in every way I could. I'm about to leave work and head home so I will try this soon. If I can get this thing working I won't forget that you were the first to respond when I'm handing out donations.
goose90proof said:
Ok so flash clockwork or teamwin right?
I've tried flashing the firmware in every way I could. I'm about to leave work and head home so I will try this soon. If I can get this thing working I won't forget that you were the first to respond when I'm handing out donations.
Click to expand...
Click to collapse
Exactly you will have to flash one of the 2. I recommend u TWRP (teamwin) -> HERE (flash this file like it was a firmware through ODIN)
his easenga
Joku1981 said:
Exactly you will have to flash one of the 2. I recommend u TWRP (teamwin) -> HERE (flash this file like it was a firmware through ODIN)
Click to expand...
Click to collapse
I was able to successfully flash teamwin recovery and now I'm able to boot into the damaged os (still no modem), but I can't flash the 4.2.2 firmware. It still fails at authentication when attempting to write.
Here's the output from Odin:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/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> aboot.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)
goose90proof said:
I was able to successfully flash teamwin recovery and now I'm able to boot into the damaged os (still no modem), but I can't flash the 4.2.2 firmware. It still fails at authentication when attempting to write.
Here's the output from Odin:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/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> aboot.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)
Click to expand...
Click to collapse
Show us your download mode screen or tell us what you read in upper left corner. Do you see anything like "warranty bit" or "konx" and a hex number like 0x0 or 0x1? If so, you won't be able to flash a 4.2.2 rom neither your factory rom, you should try newest rom.
Enviado desde mi GT-I9500 usando Tapatalk 2
jaswinky said:
Show us your download mode screen or tell us what you read in upper left corner. Do you see anything like "warranty bit" or "konx" and a hex number like 0x0 or 0x1? If so, you won't be able to flash a 4.2.2 rom neither your factory rom, you should try newest rom.
Enviado desde mi GT-I9500 usando Tapatalk 2
Click to expand...
Click to collapse
It says...
Odin Mode
Product Name: SGH-I337
Current Binary: Samsung Official
System Status: Official
KNOX Kernel Lock: 0x0
Knox Warranty Void: 0x0
CSB-CONFIG-LSB: 0x30
Write Protection: Enable
eMMC Burst Mode enabled
Can someone link a ROM I can use? At this point I just want the modem working again. :/
This normally happens when the partitions on the embedded multi media card gets corrupted for whatever reason, also known as the emmc.
The phone can be revived by flashing a pit file to repartition the emmc in order so it can be written to.
1. Download this file and you will have a .pit file which you put in the tab marked PIT in Odin -> HERE
2. Next make sure > r partition, f /reset, and auto reboot are ticked in options in Odin.
3. Next put the STOCK ROM in the tab marked PDA/AP, hit start and start the flashing process.
4. When finished the phone should reboot and start up.
goose90proof said:
It says...
Odin Mode
Product Name: SGH-I337
Current Binary: Samsung Official
System Status: Official
KNOX Kernel Lock: 0x0
Knox Warranty Void: 0x0
CSB-CONFIG-LSB: 0x30
Write Protection: Enable
eMMC Burst Mode enabled
Can someone link a ROM I can use? At this point I just want the modem working again. :/
Click to expand...
Click to collapse
So here your problem... Maybe trying to root your device with a wrong file you flashed the new Knox bootloader (any 4.3 or 4.4.2), so your will never be able to flash a 4.2.2 room with old bootloader as you are trying to do. The question is if you flashed 4.3 bootloader or last 4.4.2 bootloader. To be sure try to flash last 4.4.2 rom (if you have 4.4.2 bootloader installed and you try older 4.3 you will also get an error). You can get last 4.4.2 rom for your i337 from www.sammobile.com
Enviado desde mi GT-I9500 usando Tapatalk 2
jaswinky said:
So here your problem... Maybe trying to root your device with a wrong file you flashed the new Knox bootloader (any 4.3 or 4.4.2), so your will never be able to flash a 4.2.2 room with old bootloader as you are trying to do. The question is if you flashed 4.3 bootloader or last 4.4.2 bootloader. To be sure try to flash last 4.4.2 rom (if you have 4.4.2 bootloader installed and you try older 4.3 you will also get an error). You can get last 4.4.2 rom for your i337 from www.sammobile.com
Enviado desde mi GT-I9500 usando Tapatalk 2
Click to expand...
Click to collapse
Problem is that phone i337 only have android 4.2.2 in SamMobile :highfive:
*EDIT: How u have CUSTOM RECOVERY installed. I recommend u flash THIS if you think @jaswinky is right
jaswinky said:
So here your problem... Maybe trying to root your device with a wrong file you flashed the new Knox bootloader (any 4.3 or 4.4.2), so your will never be able to flash a 4.2.2 room with old bootloader as you are trying to do. The question is if you flashed 4.3 bootloader or last 4.4.2 bootloader. To be sure try to flash last 4.4.2 rom (if you have 4.4.2 bootloader installed and you try older 4.3 you will also get an error). You can get last 4.4.2 rom for your i337 from www.sammobile.com
Enviado desde mi GT-I9500 usando Tapatalk 2
Click to expand...
Click to collapse
It could help if you post the name of the file you wrongly flashed to root. I assume you have att version i337 and not Canadian i337M version (is it right?) , so you will not find a Knox bootloader enabled rom (4.3 or 4.4) in sammobile. But as I see, if you successful flashed a i337M bootloader into your i337, you should be able to repeat it again with a full rom. Maybe you want search in the forum for the i337 and i337M ROM compatibility...
EDIT: Try first the last rom posted by joku1981 in the last post.
Enviado desde mi GT-I9500 usando Tapatalk 2
jaswinky said:
It could help if you post the name of the file you wrongly flashed to root. I assume you have att version i337 and not Canadian i337M version (is it right?) , so you will not find a Knox bootloader enabled rom (4.3 or 4.4) in sammobile. But as I see, if you successful flashed a i337M bootloader into your i337, you should be able to repeat it again with a full rom. Maybe you want search in the forum for the i337 and i337M ROM compatibility...
Enviado desde mi GT-I9500 usando Tapatalk 2
Click to expand...
Click to collapse
I have the US version. I'm not actually with AT&T. I'm with a 3rd party carrier called StraightTalk that simply uses AT&T sim cards and operates on the same network. I have not flashed any Canadian ROMS. The first ROM I tried to flash was a 4.3 ROM. I don't have the file anymore so I don't have the name, but I do know it was 4.3. My thinking at the time was that I didn't need to go all the way back to 4.2 to root the phone, but I obviously made an error in my judgement there. This is the thread I got the root method from that originally screwed up the device (and I'm assuming my APN).
Let me update you guys on the current situation... The phone is now working. Ever since I flashed the teamwin recovery image to the phone I was able to boot into the phone. I'm assuming that at some point I damaged the recovery image and the phone wouldn't boot without it.
I also found that my APN for straighttalk (3rd party carrier) was deleted so I reset that and now I can connect to the data network.
I still want to root the phone if it is possible!
Ty so much :highfive:. Better if u use this method: HERE. Your model is in the list "Tested and worked for". Its very easy process, i think u will have rooted in few minutes. Hi5
goose90proof said:
I have the US version. I'm not actually with AT&T. I'm with a 3rd party carrier called StraightTalk that simply uses AT&T sim cards and operates on the same network. I have not flashed any Canadian ROMS. The first ROM I tried to flash was a 4.3 ROM. I don't have the file anymore so I don't have the name, but I do know it was 4.3. My thinking at the time was that I didn't need to go all the way back to 4.2 to root the phone, but I obviously made an error in my judgement there. This is the thread I got the root method from that originally screwed up the device (and I'm assuming my APN).
Let me update you guys on the current situation... The phone is now working. Ever since I flashed the teamwin recovery image to the phone I was able to boot into the phone. I'm assuming that at some point I damaged the recovery image and the phone wouldn't boot without it.
I also found that my APN for straighttalk (3rd party carrier) was deleted so I reset that and now I can connect to the data network.
I still want to root the phone if it is possible!
Click to expand...
Click to collapse
So you are now in a 4.2.2 rom with the 4.3 bootloader? Or you have 4.3 or 4.4.2 rom? I only know 2 root methods, phil recovery and cfautoroot (this doesn't change your recovery but just temporally), a bit cleaner, but in your situation i wouldn't like to advice you a root method. If you try one, try it on your own risk...
Enviado desde mi GT-I9500 usando Tapatalk 2
Joku1981 said:
Ty so much :highfive:. Better if u use this method: HERE. Your model is in the list "Tested and worked for". Its very easy process, i think u will have rooted in few minutes. Hi5
Click to expand...
Click to collapse
I will give it a try.
jaswinky said:
So you are now in a 4.2.2 rom with the 4.3 bootloader? Or you have 4.3 or 4.4.2 rom? I only know 2 root methods, phil recovery and cfautoroot (this doesn't change your recovery but just temporally), a bit cleaner, but in your situation i wouldn't like to advice you a root method. If you try one, try it on your own risk...
Enviado desde mi GT-I9500 usando Tapatalk 2
Click to expand...
Click to collapse
No, I'm still where I started (4.4.2). Odin was never able to successfully flash a different rom. It failed everytime. This phone is at 4.4.2 from a legit OTA update so I guess I'm stuck here. Now to root it with 4.4.2
goose90proof said:
I will give it a try.
No, I'm still where I started (4.4.2). Odin was never able to successfully flash a different rom. It failed everytime. This phone is at 4.4.2 from a legit OTA update so I guess I'm stuck here. Now to root it with 4.4.2
Click to expand...
Click to collapse
If you are in 4.4.2, Saferoot not works.
*EDIT: Your model no is rootable with CF-Auto-Root. How im reading:
SGH-i337 -> AT&T: Bootloader locked, do not use CF-Auto-Root on it :/
Joku1981 said:
If you are in 4.4.2, Saferoot not works.
Click to expand...
Click to collapse
Yeah I didn't see that the first time I did it. I'm a bit dyslexic and the first time I read the version number wrong. Are there no root methods available to me at this time?
goose90proof said:
Yeah I didn't see that the first time I did it. I'm a bit dyslexic and the first time I read the version number wrong. Are there no root methods available to me at this time?
Click to expand...
Click to collapse
No is possible root it:
This update contains a new bootloader due to which downgrading to previous stock firmwares WILL NOT BE POSSIBLE.
As of yet, root CAN NOT be retained or acquired on this build (I337UCUFNB1).
Warranty may be void of your device if you follow the procedures given on this page.
You only are responsible for your device. We won’t be liable if any damage occurs to your device and/or its components.
Be relaxed and enjoy ur phone completely official. Hi5
Ive created this thread specifically for. The australian . Singapore. India and LATAM users
DISCLAIMER
anything you do or use from this thread, you are doing so at your own risk, and full responsibilty is on you, i nor any developer or moderator will accept any liability or responsibility to your device or computer
Click to expand...
Click to collapse
Before you start create a back up
download and install flashfire
And back up all your partitions
(only back up data if needed)
then copy the backups folder to your hdd/cloud
All thanks goes to @Chainfire do that here
DRIVERS
Firstly download and install the latest samsung mobile drivers
SAMSUNG MOBILE DRIVERS
FIRMWARE
secondly download the latest version of your firmware i recommend G925IDVU1AOD1
FIRMWARES
AIO TOOL
for root, recovery, back up, restore and much more
UNIFIED TOOLKIT
all thanks goes to @mskip
ROOT
to root, Flash as pda in odin. Making sure your phones in download mode and usb debugging has been enabled in developer options. And your computer has the latest drivers installed
If you havent taken the ota
flash the sm-g925t tar file
If you have taken the ota
flash the sm-g925f tar file
if either of these fail, or stick at boot, try this sm-g920i file
All thanks goes to @Chainfire for his continued legendary work
STOCK RECOVERY
Stock recovery
(baseband-g925idvu1aoc5 / build number lrx22g.g925idvu1aoc4)
which i converted to .tar for flashing in odin
STOCK KERNEL
stock kernel
(baseband-g925idvu1aoc5 / build number lrx22g.g925idvu1aoc4)
which i converted to .tar for flashing in odin
CUSTOM RECOVERY
if you would like twrp for your device
you will need to flash G925IDVU1AOD1 or above firmware and then zeroltetmo version of twrp 2.8.6.0
CUSTOM KERNEL
if you want to flash custom kernels
you will need to flash G925IDVU1AOD1 firmware and then your chosen kernel
KERNEL SOURCE CODE
SM-G925I_LATIN_LL_Opensource.zip is now available
SM-G925I_SEA_LL_Opensource.zip is now available
SM-G925I_SWA_LL_Opensource.zip is now available
http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=sm-g925
CUSTOM ROMS
YOU CAN FLASH ALMOST ANY S6 ROM OR S6 EDGE ROM
As long as
A, your running G925IDVU1AOD1 (or above) firmware , and
B, straight after, you flash any sm-g925i kernel
Troubleshooting
DEEP SLEEP
To regain deep sleep after rooting, please flash stock recovery in the op
SOFT BRICK
to fix soft brick, boot loop, or stuck at splash screen simply flash firware in odin and re root, no data will be lost
Have you tried it yet? I have an Australian SM-G925I bought outright from Harvey Norman. Haven't found a way to root it yet.
I flashed the g925t on my g925i and it went smoothly and I'm now rooted. The downside is that I'm now with "KNOX WARRANTY VOID: 1" haha but who cares
kR105! said:
I flashed the g925t on my g925i and it went smoothly and I'm now rooted. The downside is that I'm now with "KNOX WARRANTY VOID: 1" haha but who cares
Click to expand...
Click to collapse
What 925i do you have ? What country etc?
pcxnet said:
What 925i do you have ? What country etc?
Click to expand...
Click to collapse
32GB Galaxy S6 Edge Black/Blueish. I'm from Chile and the operator is Entel.
Thanks I might wait for a couple more confirmations then give it a go lol
I have the Australian version. I'm just waiting on the drivers to install and then il give it a whirl
I can confirm the root works for australian sm-g925i device . Uaing the sm-g925t .tar file
gav83collins said:
I can confirm the root works for australian sm-g925i device . Uaing the sm-g925t .tar file
Click to expand...
Click to collapse
Im getting below. Debugging is on, unknown resources are on. Drivers are installed.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-zeroflte-zerofltedv-smg920i.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1005)..
<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> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Confirmed, g950t file succesfully rooted my G925i phone
rjwdon said:
Confirmed, g950t file succesfully rooted my G925i phone
Click to expand...
Click to collapse
Doesn't work it fails for me.
According to this video G925t S6 Edge download is corrupt and they had to use G920t S6 to root.
https://www.youtube.com/watch?t=348&v=En2UpJjle6E
SkilletDesire said:
Doesn't work it fails for me.
According to this video G925t S6 Edge download is corrupt and they had to use G920t S6 to root.
https://www.youtube.com/watch?t=348&v=En2UpJjle6E
Click to expand...
Click to collapse
Did you download and install the latest s6 edge drivers ? Guessing so because odin detected it
Was your s6 edge in download mode
gav83collins said:
Did you download and install the latest s6 edge drivers ? Guessing so because odin detected it
Was your s6 edge in download mode
Click to expand...
Click to collapse
I got the drivers from here http://developer.samsung.com/technical-doc/view.do?v=T000000117
Yes was in download mode. Are these drivers old?
Did you accept any ota beforw tryong root. Not that im sure that matters. Take a screenshot if your "about phone" lets see of ours match. Il do the same
Hi there
I am in Saudi Arabia , I pre-ordered the device and I get that version SM-G925i.
Since that time I was upset because I was waiting for the international one , you know most developments are going to the international one.
My question is , are we going to get support and development for ours ( ROMS,MODS..etc.) ?
thanks in advance.
I was thinking about developing my own rom. I was gonna wait though. Im a bit of a perfectionist and i dont really have the time to dedicate what would be needed to fulfil the project
SkilletDesire said:
I got the drivers from here http://developer.samsung.com/technical-doc/view.do?v=T000000117
Yes was in download mode. Are these drivers old?
Click to expand...
Click to collapse
Im not sure. I juat downloaded the latest samsung drivers. And checked to makes sure they all installed. With the phone on. The phone off. And also in download mode.
This is my build number in this snapshot
gav83collins said:
Did you accept any ota beforw tryong root. Not that im sure that matters. Take a screenshot if your "about phone" lets see of ours match. Il do the same
Click to expand...
Click to collapse
Phone said it was up to date when I first set it up. Here is the screen shot.
Yeah its the same as mine. What machine did you use. I used a friend's windows vista machine i was cleaning.
So i thought i had a back up of my stock recovery on my SD card but it seem i left it on my phone. lol
does any on have a back up of the stock recovery for S7 edge ATT (SM-G935A).
been trying to look around cant find the stock recovery keep finding a stock firmware and not recovery.
any help would be appreciated. thx. Would even donate if i worked.
bfixer117 said:
So i thought i had a back up of my stock recovery on my SD card but it seem i left it on my phone. lol
does any on have a back up of the stock recovery for S7 edge ATT (SM-G935A).
been trying to look around cant find the stock recovery keep finding a stock firmware and not recovery.
any help would be appreciated. thx. Would even donate if i worked.
Click to expand...
Click to collapse
If I'm not mistaken , the recovery is included in the firmware .
SkyAttacksX said:
If I'm not mistaken , the recovery is included in the firmware .
Click to expand...
Click to collapse
Well when flashing the different recoveries. I was trying to get working it said back up current recovery in Flashify so I did but forgot to move it to my SD card. then i flashed it thats where i was pretty sure that recoveries were different files but written the same way as roms or AP's in ODIN. but then when I went to test it out my phone is stuck in a boot loop with no recovery and I've been trying to use ODIN to try and flash a stock on but it keeps failing.
bfixer117 said:
Well when flashing the different recoveries. I was trying to get working it said back up current recovery in Flashify so I did but forgot to move it to my SD card. then i flashed it thats where i was pretty sure that recoveries were different files but written the same way as roms or AP's in ODIN. but then when I went to test it out my phone is stuck in a boot loop with no recovery and I've been trying to use ODIN to try and flash a stock on but it keeps failing.
Click to expand...
Click to collapse
What firmware were you on prior to this ?
EDIT: Also , which firmware have you tried flashing ?
SkyAttacksX said:
What firmware were you on prior to this ?
EDIT: Also , which firmware have you tried flashing ?
Click to expand...
Click to collapse
the one here: http://forum.xda-developers.com/att-galaxy-s7/how-to/g935a-root-t3410403/
then here: http://d-h.st/lQY8
tried flashing the stock firmware but get this error
<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> FAIL! Model dismatch fail
<OSM> All threads completed. (succeed 0 / failed 1)
I have also been trying to flash a stock firm ware thats when i get the error maybe someone is using a SM-G935F or some other model number for the SM-G935A if anyone have and actual stock firm ware for the SM-G935A i would greatly appreciate it. also if it is a real working stock firmware i would be willing to donate if wanted.
bfixer117 said:
I have also been trying to flash a stock firm ware thats when i get the error maybe someone is using a SM-G935F or some other model number for the SM-G935A if anyone have and actual stock firm ware for the SM-G935A i would greatly appreciate it. also if it is a real working stock firmware i would be willing to donate if wanted.
Click to expand...
Click to collapse
Sir . . those were links to root methods and an engboot . What update were you on ? June , May , April ?
SkyAttacksX said:
Sir . . those were links to root methods and an engboot . What update were you on ? June , May , April ?
Click to expand...
Click to collapse
I'm pretty sure the newest one gomy phone like 3 months ago gonna try this firmware see if it works
https://www.androidfilehost.com/?fid=24572369242688242
bfixer117 said:
I'm pretty sure the newest one gomy phone like 3 months ago gonna try this firmware see if it works
https://www.androidfilehost.com/?fid=24572369242688242
Click to expand...
Click to collapse
That is your firmware , correct . Unrar it and put it in the correct ODIN slots and flash .
PB5 and newer versions have been posted for a while now. Flash the latest and you'll be fine
Yea thanks all the help guys. Called Samsung and acted like the phone just stated doing it then she was like take it to your nearest best buy and have them reflash it so after I took it up there they used there ODIN like program and then boom! it was working.
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.