hello everyone i am new here.
i have come here because i was trying to install a new recovery twrp to be exact. while i was installing it apeared a messge it said: the recovery has been installed correctly would you like to restart your mobile? and i restared my mobile and then it shown a message it said: system software not authorized by at&t has been found on your phone. at that time i had installed android lollipop 5.0.1 and it was rooted and i just wanted to re-install lollipop again by odin but knox and bootloader was enable so i cant reinstall the rom again and it seem like i have bricked my mobile..
help me please.
SGH-i337 is an AT&T phone which has a locked bootloader. If you have old bootloader like MDL you could use the loki exploit when you install the TWRP. What is your bootloader version?
I do not think there is a odin flashable lollipop full firmware exist. The last full firmware released for i337 is NB1 (kitkat). After that there is only incremental OTA upgrade to lollipop.
can i downgrade to kikkat?
i dont know what kind of bootloader i have. but odin is always fail when i try to apply the firmware... let me post a screemcapture!
can i dowgrade via ota... because i have tried to intall lollipop by ota but there is always an error! unpacking the package!
either samsung kies doesnt detect my mobile and i cant not enter to recovery mode because it says that firmware upgrade encountered an issue. please select recovery mode in kies and try again.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The ROM you are trying to flash has a bootloader that is older than the bootloader on the phone. This is evidenced by the fact that Odin stops after trying to flash aboot.mbn.
Look here for a possible solution: http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642
my mobile was running lollipop 5.0.1 and how can i get the latest version?
thank you it works hehe i am so thankful with you...
arigatou..
Related
Hello,
Hello,
Samsung S4 from Canada - Provider Bell - Model SGH-I337M
Phone was functional, new in box, with latest November firmware.
Soft Bricked it when Odin failed (auth) to downgrade from latest frimware to 4.22 (reason for downgrade: unlock codes not working; USB unlock not working due to new security features in latest update).
Tried steps in http://forum.xda-developers.com/showthread.php?t=2261153 using Kies and that also fails with - PC failed to recognise the mobile phone
Now trying to upload latest firmware using Odin 3.09, i get FAILED:
<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/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On Phone, looks like 2% done (blue bar)
Is this phone garbage????
Thanks !!
Hey have you tried re-flashing the original bell rom? Or did you have a backup? I haven't bricked my s4 but I bricked my S3 multiple times and I ended up bringing it back with a basic ATT rom before getting the rom I wanted to work.
So first try flashing your original stock rom (if you have it or go to your backup)
Next step try an ATT stock rom.
If that doesn't fix it, someone more experienced will have to chime in.
mfreeman3769 said:
Hello,
Hello,
Samsung S4 from Canada - Provider Bell - Model SGH-I337M
Phone was functional, new in box, with latest November firmware.
Soft Bricked it when Odin failed (auth) to downgrade from latest frimware to 4.22 (reason for downgrade: unlock codes not working; USB unlock not working due to new security features in latest update).
Tried steps in http://forum.xda-developers.com/showthread.php?t=2261153 using Kies and that also fails with - PC failed to recognise the mobile phone
Now trying to upload latest firmware using Odin 3.09, i get FAILED:
<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/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On Phone, looks like 2% done (blue bar)
Is this phone garbage????
Thanks !!
Click to expand...
Click to collapse
Odin fails due to the firmware
Hello,
Finally I found the issue. The File at Sam Mobile version 4.2.2 for Bell is the cause. It fails at 2% upload. The 4.3 file restored the phone, but had to root using CF-AUTO-ROOT in order to get the /data folder back (phone stuck in a loop in boot animation).
The other file available there, an older 4.2.2 is corrupt once downloaded (tried 3 times).
Reason I was flashing back to 4.2.2 is because with the new Bell 4.3 firmware, network unlock codes no longer work (changed??) and neither does USB unlocking (new security feature).
It is conceivable that the new 4.3 frimware from this provide is the cause of the Odin failure at 2% for 4.2.2 ?
Any other good reliable sources for a 4.2.2 firmware version pre ME1 ?
Samsung S4 i337m for Bell (Canada) ??
Thanks!
Try this: launch Samsung Kies and go to Tools -> Firmware Upgrade and Initialization.
I tied it (my phone work now) but i have always the same trouble with ODIN (nothing can't put in except CF-AUTO-ROOT don't tell me fail)
mfreeman3769 said:
Hello,
Finally I found the issue. The File at Sam Mobile version 4.2.2 for Bell is the cause. It fails at 2% upload. The 4.3 file restored the phone, but had to root using CF-AUTO-ROOT in order to get the /data folder back (phone stuck in a loop in boot animation).
The other file available there, an older 4.2.2 is corrupt once downloaded (tried 3 times).
Reason I was flashing back to 4.2.2 is because with the new Bell 4.3 firmware, network unlock codes no longer work (changed??) and neither does USB unlocking (new security feature).
It is conceivable that the new 4.3 frimware from this provide is the cause of the Odin failure at 2% for 4.2.2 ?
Any other good reliable sources for a 4.2.2 firmware version pre ME1 ?
Samsung S4 i337m for Bell (Canada) ??
Thanks!
Click to expand...
Click to collapse
You might want to check which bootloader you are on, you can do this through terminal on the the phone (instructions burried somewhere in one of the threads) or download Phone INFO from the play store, it will display which bootloader you are on. Once you know that, see if you can find a thread (search) on downgrading from 4.3 to 4.2
Hey, guys. I left my G2 to go back to my GS4, and I'm having a bit of trouble. I'm trying to get back to an earlier firmware to gain root and flash custom recovery. Currently on NB1 firmware. TowelRoot does not work.
Anyway, I downloaded the stock ATT Firmware for my phone. UCUAMDL. When I go to Odin, Auto reboot and F reset time is checked. Re-Partition is not checked. Odin sees my phone. I hit PDA or AP and load my firmware file and hit start. Everytime, it fails after Nand write start.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
I have tried v1.85, 3.04, 3.08, and 3.09. I have tried various USB ports on my computer. I have tried 2 different cables. I always run as admin. I have tried running in compatibility mode. Kies is not installed. I have uninstalled and reinstalled drivers.
Any help?
Your phone has a locked boot loader which prevents a full downgrade. If you are on stock NB1, you can adb sideload the NC1 OTA update file. The all things AT&T should have the link.
Sent from my SGH-I337 running GPE using Tapatalk
jmjoyas said:
Your phone has a locked boot loader which prevents a full downgrade. If you are on stock NB1, you can adb sideload the NC1 OTA update file. The all things AT&T should have the link.
Sent from my SGH-I337 running GPE using Tapatalk
Click to expand...
Click to collapse
If I sideload NC1, will I be able to install custom recovery and flash custom ROMs? Or will that require the MK2 downgrade to flash custom recovery after root?
N12X93R said:
If I sideload NC1, will I be able to install custom recovery and flash custom ROMs? Or will that require the MK2 downgrade to flash custom recovery after root?
Click to expand...
Click to collapse
You will be able to root using towelroot and install touchwiz based custom roms. There is a version of the google play edition that works (there are some known issues though).
The stock recovery cannot be replaced. We have a special recovery (this recovery is available during normal boot itself) called safestrap that can be used to flash the custom roms.
All things AT&T
jmjoyas said:
You will be able to root using towelroot and install touchwiz based custom roms. There is a version of the google play edition that works (there are some known issues though).
The stock recovery cannot be replaced. We have a special recovery (this recovery is available during normal boot itself) called safestrap that can be used to flash the custom roms.
All things AT&T
Click to expand...
Click to collapse
Oh, wow. What happened? I guess Samsung stuck it to us one final hard time. Made things so much harder. Thanks for the clarification.
Unfortunately you cant install Safestrap Recovery while on NC1. At least I haven't been able to at all. Really f'n hating this crappy updated phone I got from ATT as a replacement for my broken old on with the good bootloader.
You should be able to, once you set selinux to permissive mode. Towelroot was also updated to do the same.
Sent from my SGH-I337 running GPE using Tapatalk
N12X93R said:
Hey, guys. I left my G2 to go back to my GS4, and I'm having a bit of trouble. I'm trying to get back to an earlier firmware to gain root and flash custom recovery. Currently on NB1 firmware. TowelRoot does not work.
Anyway, I downloaded the stock ATT Firmware for my phone. UCUAMDL. When I go to Odin, Auto reboot and F reset time is checked. Re-Partition is not checked. Odin sees my phone. I hit PDA or AP and load my firmware file and hit start. Everytime, it fails after Nand write start.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
I have tried v1.85, 3.04, 3.08, and 3.09. I have tried various USB ports on my computer. I have tried 2 different cables. I always run as admin. I have tried running in compatibility mode. Kies is not installed. I have uninstalled and reinstalled drivers.
Any help?
Click to expand...
Click to collapse
If you are on NB1 you can go back to MK2 to root or update to NC1 to use TowelRoot .
If you want to downgrade to MK2 and root please follow the steps in post 1, 2, 3 at here.
.
Ok, so I rooted my phone using a method where i flashed an older kernel then used towelroot to root, and then flashed back to NJ4. All was going well, and i installed the safestrap recovery. Then, today i was tryin to install the CM12 for the S4, and i messed up where i put the files for this, so when i was in safestrap, it told me it failed. I hit reboot, and that is when my phone essentially 'soft bricked'. I tries to boot up, fails and goes into download mode. I tried pulling out the battery, tried to go into recovery, but i cant do it. I tried to flash 4.2.2. stock s4 firmware thru odin, but it kept saying "Can't open the serial(COM) port." and fails. I can't do anything right now, please help im panicking Dx
UPDATE: I tried again to flash stock and now when i try to boot it tells me "firmware upgrade encountered an issue.." now when i try to flash something it won't let me because odin fails and says
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUAMDJ_I337MOYAAMDJ_I337MVLUAMDJ_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> boot.img
<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)
HELP
Someone wiser then me will probably come in but if you can get to download mode no big worries. The com port issue makes me think drivers or the USB port. I would try different USB port and potentially uninstall drivers and reinstall. I believe skip makes a tool kit for s4 today may help. Can you see the device in adb?
McAwesome said:
Someone wiser then me will probably come in but if you can get to download mode no big worries. The com port issue makes me think drivers or the USB port. I would try different USB port and potentially uninstall drivers and reinstall. I believe skip makes a tool kit for s4 today may help. Can you see the device in adb?
Click to expand...
Click to collapse
I updated my last post btw. Dumb question but...what is adb?
EDIT:
Got it. I found a link to a rootable 4.4.2 md5 file and flashed it and it worked!
Not compatible
Well CM12 CM11 no CM period is compatible with out S4 because of the locked bootloader and youre trying to use the wrong firmware in odin once you upgrade to 4.4.4 or 4.4.2 you can no longer downgrade and go down to 4.2.2 so stop trying that you need to either download NB1 or NI1 odin files and restore it that way thats if you havent completely messed up youre phone Good Luck!
I have the Samsung Galaxy S5 by Verizon.
It is on the 6.0.1 firmware.
I rooted the device when it was one the 4.4 firmware. When I did OTA update, I lost it.
I am trying to flash the 4.4 rom onto the phone through ODIN.
I get this on ODIN
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_VZW_G900VVRU1ANCG_G900VVZW1ANCG_964333_REV00_user_low_ship_MULTI_CERT.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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
On the phone it says
SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1
BTW the volume keys don't work so I used adb to enter download mode.
Please help
Thanks
I am on marshmallow 6.0.1
I can't flash any rom or tar files.
There is a screenshot attachment with more info.
how to downgrade to kitkat
deleted
I can't root the phone because it won't let me flash a custom rom.
I also have tried flashing the rom from the micro SD but the phone says signature verification failed.
what Ota and baseband version are you on?
extremewonder1 said:
I have the Samsung Galaxy S5 by Verizon.
It is on the 5.0 firmware.
I rooted the device when it was one the 4.4 firmware. When I did OTA update, I lost it.
I am trying to flash the 4.4 rom onto the phone through ODIN.
I get this on ODIN
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_VZW_G900VVRU1ANCG_G900VVZW1ANCG_964333_REV00_user_low_ship_MULTI_CERT.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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
On the phone it says
SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1
BTW the volume keys don't work so I used adb to enter download mode.
Please help
Thanks
Click to expand...
Click to collapse
Go to this thread http://forum.xda-developers.com/showthread.php?t=2784880
If you took the OTA of anything higher than OD5, you would be unable to ODIN back to NCG(KitKat). It sounds as if your device may have taken the OTA of MM....but I wouldn't be able to answer you that....as you had stated that you were on 4.4 KitKat, did you have at least SafeStrap installed? If so, try to flash the NI2 kernal via Odin to see if you can get back into SafeStrap....
---------- Post added at 03:24 AM ---------- Previous post was at 03:18 AM ----------
hauckk said:
first root the phone http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370/
then unlock the bootloader http://forum.xda-developers.com/ver...t/rd-unlocking-galaxys-s5-bootloader-t3337909
then install custom recovery just google twrp download then flash using odin
then find a stock custom rooted rom and install it using twrp and make sure to download gapps also. i prefer open gapps. google open gapps for kitkat. make sure to flash both the rom and gapps at the same time in twrp ps your rom may come with the google apps make sure to check before you install gapps.
Click to expand...
Click to collapse
Why are you having him install TWRP and a CM ROM? No where did he mentioned that he had an "Unlocked Bootloader". He said that he was "ROOTED" on 4.4 KitKat and happened to lose root via an OTA. Which WE don't exactly know which OTA....so please, before digging him/her deeper in a hole, respectively respond with SAFE and Helpful advice....thank you
So ive been trying to root for a while and nothing seem to work its a snapdraggon CPU when i use cf-auto root i brick my phone when i try to root via TWRP nothing happens when i try to flash an official samsung firmware it fails at CM.BIN im on 6.0.1 and anything i do either bricks it or nothing happens an i stay unrooted with original firmware.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> A510FXXU2APD5_A510FEVR2APD4_A510FXXU2APD4_HOME.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> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> cm.bin
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
alexsheff said:
So ive been trying to root for a while and nothing seem to work its a snapdraggon CPU when i use cf-auto root i brick my phone when i try to root via TWRP nothing happens when i try to flash an official samsung firmware it fails at CM.BIN im on 6.0.1 and anything i do either bricks it or nothing happens an i stay unrooted with original firmware.
Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
A510FXXU2APD5_A510FEVR2APD4_A510FXXU2APD4_HOME.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Odin engine v(ID:3.1005)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
SingleDownload.
sboot.bin
NAND Write Start!!
cm.bin
FAIL!
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Simple - wrong firmware for your device.
Twrp, nothing happens? - you need to give details.
ashyx said:
Simple - wrong firmware for your device.
Twrp, nothing happens? - you need to give details.
Click to expand...
Click to collapse
it is 100% the correct firmware i downloaded it on samstock for EE (EVR) stock 6.0.1 and 5.1.1 both wont install via odin and samsung tools pro. ive flashed twrp following your guide and that worked but installing super su just gave me the app and no binary files were installed, cf auto root just boot loops me the only tike im able to install any firmware is through emergency recovery on smart switch
alexsheff said:
it is 100% the correct firmware i downloaded it on samstock for EE (EVR) stock 6.0.1 and 5.1.1 both wont install via odin and samsung tools pro. ive flashed twrp following your guide and that worked but installing super su just gave me the app and no binary files were installed, cf auto root just boot loops me the only tike im able to install any firmware is through emergency recovery on smart switch
Click to expand...
Click to collapse
If part of the firmware doesn't install then it is not the correct firmware for your particular device, simple.
The bootloader does a sanity check via Odin on any firmware attempted to be installed.
If it doesn't meet the requirements it fails to install.
It's pointless arguing the case because it's a fact and I've been down this road with others who have eventually got the correct firmware of which you've almost proved my point by stating that downloading through Smartswitch installs the correct firmware.
Several factors come into play, model, carrier, region and revision.
Any of these mismatch and installation could potentially fail. Simply being the right model no. isn't enough.
You could probably help yourself if you post more details:
Exact firmware your device is currently running, the firmware you are attempting to install and screenshots or post a log of the output from odin and the info provided on the device display itself after failure.
I got the device on contract with EE so i thought it was locked to EE, my partner bought me a S7 (flat) on vodafone so i put the voda sim into my A510F n it seems to be unlocked to voda not quite sure why i always thought they was locked to the network if it was a contract device, could it possibly be a vodafone stock rom or any other network.
alexsheff said:
I got the device on contract with EE so i thought it was locked to EE, my partner bought me a S7 (flat) on vodafone so i put the voda sim into my A510F n it seems to be unlocked to voda not quite sure why i always thought they was locked to the network if it was a contract device, could it possibly be a vodafone stock rom or any other network.
Click to expand...
Click to collapse
Post the details as requested above and we'll get it sorted.