Hello all, I'm new to the forums. I recently bricked my S4. It was "somewhat" rooted with CWM but it couldn't go into recovery mode, so I was unable to install custom roms. I was able to user SU and had root access to everything, but I just couldn't go into Recovery Mode. I tried to re root it a few times but nothing seemed to work except for the one CWM recovery img I found. Yesterday I decided I would try to erase everything and return the phone to factory settings and by doing so, I'm pretty sure I bricked my phone. I can't get it passed developer mode now. I tried using a tar file I found for re flashing the phones firmware along with a 16gb pit file in odin but the results I got back were this:
<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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Added!!
I put the md5 in the PDA slot and used an SGS-i337 16gb pitfile.
Is there a possibility that by deleting and erasing everything I turned off debugging mode and now I can't write to my hdd?
Please help!
Were you on mdl firmware? That's the tar your trying to flash. I'm guessing you're not on mdl and you need a different tar file. So do you know your firmware version?
Sent from my Nexus 5
@Mkarpe91 How sure are u that u have MDL firmware? Seem to me that u did not have MDL firmware that's why it failed. IF u sure that u have MDL firmware then u can try using different USB cable or Port. If u not sure then u might have either MF3 or MK2 firmware which u CAN"T install CWM recovery, coz u would ended up bricked if u install CWM/TWRP recovery......U can only use Safestrap recovery for MF3 and up firmware....then the only way back is to flash MK2 tar follow my thread and check post #2 for guide on how to.....goodluck....:good::good: @jd1639 Man!!!.....u beat me by a minutes.......good job bro....:good::good:
ted77usa said:
@Mkarpe91 How sure are u that u have MDL firmware? Seem to me that u did not have MDL firmware that's why it failed. IF u sure that u have MDL firmware then u can try using different USB cable or Port. If u not sure then u might have either MF3 or MK2 firmware which u CAN"T install CWM recovery, coz u would ended up bricked if u install CWM/TWRP recovery......U can only use Safestrap recovery for MF3 and up firmware....then the only way back is to flash MK2 tar follow my thread and check post #2 for guide on how to.....goodluck....:good::good: @jd1639 Man!!!.....u beat me by a minutes.......good job bro....:good::good:
Click to expand...
Click to collapse
I have no clue what firmware I have other than that I have a i337 AT&T model. I'm going to try the Mk2 flash, I'll let you know how it goes shortly.
Thanks for the rapid response you guys took no time to answer lol.:good:
I tried the Mk2 method. I followed the directions in the 2nd post and all the files were in their appropriate slots. I tried doing it with and without the pit file. Here are my results:
<OSM> Please wait..
<OSM> BL_I337UCUEMK2_1921628_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> AP_I337UCUEMK2_1921628_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> CP_I337UCUEMK2_1921628_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> CSC_ATT_I337ATTEMK2_1921628_REV06_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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_I337UCUEMK2_1921628_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> AP_I337UCUEMK2_1921628_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> CP_I337UCUEMK2_1921628_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> CSC_ATT_I337ATTEMK2_1921628_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
Do not use the pit file, it's useless. I'm not sure what you've posted. One says succeeded/0 failed/1 and the other succeeded/0 failed/0. I've never seen that before. Try it without the pit file, do not check re-partition and let us know what your results are.
Sent from my Nexus 5
jd1639 said:
Do not use the pit file, it's useless. I'm not sure what you've posted. One says succeeded/0 failed/1 and the other succeeded/0 failed/0. I've never seen that before. Try it without the pit file, do not check re-partition and let us know what your results are.
Sent from my Nexus 5
Click to expand...
Click to collapse
Alright! Problem solved!
It turned out that it indeed WAS the wire I was using. I guess 7 Eleven products aren't too dependable .
Thanks to jd1639 and ted77 for the help.
Can I re root now? The right way? If there is a "right way" for my phone?
what firmware did you end up at? MK2? if so, there is http://forum.xda-developers.com/showthread.php?t=2616221 that is all about MK2..rooting...compatible roms...etc
xDark-Moonx said:
what firmware did you end up at? MK2? if so, there is http://forum.xda-developers.com/showthread.php?t=2616221 that is all about MK2..rooting...compatible roms...etc
Click to expand...
Click to collapse
Yeah I flashed it with the all in one stock MK2 firmware. It's back to it's nice, stock, settings; A fresh start
I'll give the MK2 root a try and I'll let ya know how it goes.
Mkarpe91 said:
Yeah I flashed it with the all in one stock MK2 firmware. It's back to it's nice, stock, settings; A fresh start
I'll give the MK2 root a try and I'll let ya know how it goes.
Click to expand...
Click to collapse
I'm interested in flashing a ROM that requires me being on the MDL firmware. Is there anyway I can flash over to that? If not, I'll take the Mk2 route and use the ROMS you guys suggested.
Mkarpe91 said:
I'm interested in flashing a ROM that requires me being on the MDL firmware. Is there anyway I can flash over to that? If not, I'll take the Mk2 route and use the ROMS you guys suggested.
Click to expand...
Click to collapse
You can not go backwards in firmware. You're stuck on mk2
Sent from my Nexus 5
jd1639 said:
You can not go backwards in firmware. You're stuck on mk2
Sent from my Nexus 5
Click to expand...
Click to collapse
Can I upgrade to any other versions if I need to?
Mkarpe91 said:
Can I upgrade to any other versions if I need to?
Click to expand...
Click to collapse
You can try the leaked version of Kit Kat, then flash back to mk2, now that we have the tar files, but other than that you are stuck on 4.3 mk2 Our boot loader is locked, so we can't move up or down on the firmware chain. Here please read the following guide. It will help you. Good luck.
http://forum.xda-developers.com/showthread.php?t=2616221
Related
So triangle away doesn't work as of now for mf9 I'm wondering has anyone tried and had any luck going back to mdl then using triangle away to reset the flash counter?
Sent from my SPH-L720 using xda app-developers app
Is the flash counter present somewhere in the file system? I know if I Odin back to MDL and let the phone boot all the way and go through the finalizing android update after setup screens, and then go back to recovery all will say official agaim
Sent from my SPH-L720 using xda premium
It can't read it or change it. Something is interfering.
Triangle away doesn't work on MF9. You have to use it while on MDC or MDL. Yes I have used it and it works.
Sent from my Sprint Galaxy S4 using Tapatalk
Sent from my Sprint Galaxy S4 using Tapatalk 2
Great just what I thought my rule of thumb ask before you flash thanks everyone
HELP!!! PLEASE firmware upgrade encountered an issue.
OK so this is what i did. so i tried to root my s4, and in odin it said fail. so i took out the battery. and try to turn it on now it has the phone YELLOW triangle and a monitor. it says "firumware upgrade encountered an issue. Please select recovery mod in kies & try again.
what i have tried so far was download the sprint stock and odin it back. i used qbking77 . com the stock i used is linked on that website. which then links me to stockroms.net. so during the process of doing going back to stock it said fail. i read some where that in the id:com on odin, it should say 0:[COM6] and i read some where else that it does have to say com6 it could say com3. i dont know if that matters. and i also read on the forum they say to use another stock rom? is that also if so where can i get one besides from stockroms.net please someone help me..
this is what it says when i try to odin to stock:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUAMDC_L720SPTAMDC_L720VPUAMDC_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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Added!!
texassoljaz said:
OK so this is what i did. so i tried to root my s4, and in odin it said fail. so i took out the battery. and try to turn it on now it has the phone YELLOW triangle and a monitor. it says "firumware upgrade encountered an issue. Please select recovery mod in kies & try again.
what i have tried so far was download the sprint stock and odin it back. i used qbking77 . com the stock i used is linked on that website. which then links me to stockroms.net. so during the process of doing going back to stock it said fail. i read some where that in the id:com on odin, it should say 0:[COM6] and i read some where else that it does have to say com6 it could say com3. i dont know if that matters. and i also read on the forum they say to use another stock rom? is that also if so where can i get one besides from stockroms.net please someone help me..
this is what it says when i try to odin to stock:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUAMDC_L720SPTAMDC_L720VPUAMDC_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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Added!!
Click to expand...
Click to collapse
You need to download the stock file from xda, reports from others have said the file linked by qbking is bad.
Sent from my icrap 2 using Tapatalk HD
A couple of days ago I rooted my Galaxy S4 from AT&T, and used SafeStrap as a recovery tool. After, I attempted to partition a ROM slot with SafeStrap, but it said I didn't have enough room.
I then installed the Cyanogenmod ROM, but apparently I installed it incorrectly (maybe over the stock ROM, not sure). After, I booted my phone but it said that the recovery failed, and if I continued the screen would be horribly pixilated with bright purplish squares and stripes. Through SafeStrap, I went to ('wipe' or 'restore') and then used the advanced option, and then clicked the box marked 'System' and 'Data', which I now horribly regret. I had thought that they would be replaced, not completely wiped. I attempted to use a backup, but I had no luck.
Then the boot loops came.
For about 9 hours straight, I've been researching and troubleshooting my phone with Odin, stock recovery tool (Hold down Volume Up and Home button on start up), and tried custom ROM's, as well as a Stock ROM.
Through the boot menu, I've wiped the cache data and the partition data (I believe that's the name), then attempted to install custom ROM's with no luck.
I then downloaded a Stock ROM (http://forum.xda-developers.com/showthread.php?t=2502003) and used multiple versions of Odin with the original Samsung USB cable. I've also re installed the drivers multiple times. After trying Odin, I receive "FAILED (Auth)" messages.
Ever since I deleted the 'System' and 'Data' from the phone, Samsung's 'Kies' won't reconize the phone, but will attempt to install firmware if I try to through the 'Tools' menu and 'Firmware Upgrade and Initialization'. After entering the model number and serial number, I accept the lose of data messages and give administrative access to the program. After, the program freezes in a dark-gray tint and I must use task manager to close it.
At this point, on start up the phone will only go into download mode, and not the boot menu mode. The message that is shown is "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again".
If this post was too long, I apologize, but I'd like to give as much info as possible, as other people post very short posts that give no information at all.
If the phone is stuck in a 'soft' brick, I'll need to purchase a new one, as my phone is vital to my work and family communication, which will be unfortunate.
So, how would I go about restoring functionality to my phone, though stock ROM or custom?
Thanks for anyone who took the time to read this, and to anyone whose willing to share some advice!
AhellHound said:
A couple of days ago I rooted my Galaxy S4 from AT&T, and used SafeStrap as a recovery tool. After, I attempted to partition a ROM slot with SafeStrap, but it said I didn't have enough room.
I then installed the Cyanogenmod ROM, but apparently I installed it incorrectly (maybe over the stock ROM, not sure). After, I booted my phone but it said that the recovery failed, and if I continued the screen would be horribly pixilated with bright purplish squares and stripes. Through SafeStrap, I went to ('wipe' or 'restore') and then used the advanced option, and then clicked the box marked 'System' and 'Data', which I now horribly regret. I had thought that they would be replaced, not completely wiped. I attempted to use a backup, but I had no luck.
Then the boot loops came.
For about 9 hours straight, I've been researching and troubleshooting my phone with Odin, stock recovery tool (Hold down Volume Up and Home button on start up), and tried custom ROM's, as well as a Stock ROM.
Through the boot menu, I've wiped the cache data and the partition data (I believe that's the name), then attempted to install custom ROM's with no luck.
I then downloaded a Stock ROM (http://forum.xda-developers.com/showthread.php?t=2502003) and used multiple versions of Odin with the original Samsung USB cable. I've also re installed the drivers multiple times. After trying Odin, I receive "FAILED (Auth)" messages.
Ever since I deleted the 'System' and 'Data' from the phone, Samsung's 'Kies' won't reconize the phone, but will attempt to install firmware if I try to through the 'Tools' menu and 'Firmware Upgrade and Initialization'. After entering the model number and serial number, I accept the lose of data messages and give administrative access to the program. After, the program freezes in a dark-gray tint and I must use task manager to close it.
At this point, on start up the phone will only go into download mode, and not the boot menu mode. The message that is shown is "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again".
If this post was too long, I apologize, but I'd like to give as much info as possible, as other people post very short posts that give no information at all.
If the phone is stuck in a 'soft' brick, I'll need to purchase a new one, as my phone is vital to my work and family communication, which will be unfortunate.
So, how would I go about restoring functionality to my phone, though stock ROM or custom?
Thanks for anyone who took the time to read this, and to anyone whose willing to share some advice!
Click to expand...
Click to collapse
Use Odin 3.07 Download the MF3 Firmware from https://mega.co.nz/#!WEEzSA7Z!aB46731_AwM7P83eMdDlmFYd1hUZfFBcQAZjc1X7wAE And put all the extracted files in the correct spot
compucanton said:
Use Odin 3.07 Download the MF3 Firmware from (your link) And put all the extracted files in the correct spot
Click to expand...
Click to collapse
Thanks for the reply!
After attempting this, it failed with the below message:
Code:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PLATFORM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_ATT_I337ATTAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sbl1.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl2.mbn
<ID:0/006> sbl3.mbn
<ID:0/006> rpm.mbn
<ID:0/006> aboot.mbn
<ID:0/006> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
AhellHound said:
Thanks for the reply!
After attempting this, it failed with the below message:
Code:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PLATFORM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_ATT_I337ATTAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sbl1.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl2.mbn
<ID:0/006> sbl3.mbn
<ID:0/006> rpm.mbn
<ID:0/006> aboot.mbn
<ID:0/006> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
The phone's status on the top right when in download mode is as followed:
Code:
ODIN MODE
PRODUCT NAME: SGH-I337
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURSRT MODE enabled
I don't know anything about safestrap, but can you get into safestrap recovery and flash another recovery program like CWM or TWRP? From there you can wipe the phone clean and "mount usb storage" to transfer a custom rom to load and start fresh.
Nurmi_CEO said:
I don't know anything about safestrap, but can you get into safestrap recovery and flash another recovery program like CWM or TWRP? From there you can wipe the phone clean and "mount usb storage" to transfer a custom rom to load and start fresh.
Click to expand...
Click to collapse
No
For future reference as posted in both the SS development thread and QA Thread OPs, Cyanogen and the like is not compatible with SS
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
---------- Post added at 07:11 PM ---------- Previous post was at 07:09 PM ----------
Also, if you are unable to restore with Odin and the MF3 files, I suggest mobitechvideos. They can possibly J-tag it.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
HELP NEEDED! soft brick at&T s4 i337
hey i recently upgraded my at&t samsung galaxy s4 sgh-i337 from stock mf3 to stock 4.3 mk2 then upgraded to 4.4.2 nb1 then to 4.4.2 nc1 everything worked perfectly. then i decided to flash custom roms i succeeded to flash multiple roms via safestrap but then i flashed a rom and i got a msg saying that the firmware is not recognized by at&t probably because the kernel was different so i tried to flash stock mk2 again however i stupidly forgot to wipe data/system in recovery and odin failed during the flash and i recieved a msg saying firmware upgrade encountered an issue please select recovery mode in kies and try again. kies doesnt connect to the device and i dont know what to do please can someone assist me!!!!
gtrijoe said:
hey i recently upgraded my at&t samsung galaxy s4 sgh-i337 from stock mf3 to stock 4.3 mk2 then upgraded to 4.4.2 nb1 then to 4.4.2 nc1 everything worked perfectly. then i decided to flash custom roms i succeeded to flash multiple roms via safestrap but then i flashed a rom and i got a msg saying that the firmware is not recognized by at&t probably because the kernel was different so i tried to flash stock mk2 again however i stupidly forgot to wipe data/system in recovery and odin failed during the flash and i recieved a msg saying firmware upgrade encountered an issue please select recovery mode in kies and try again. kies doesnt connect to the device and i dont know what to do please can someone assist me!!!!
Click to expand...
Click to collapse
You can't flash mk2 any more since you've updated to nc1. You can however flash the nb1 tar file and get your phone working again.
http://forum.xda-developers.com/showthread.php?p=50912149
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You can't flash mk2 any more since you've updated to nc1. You can however flash the nb1 tar file and get your phone working again.
http://forum.xda-developers.com/showthread.php?p=50912149
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Dude, you totally saved me. I soft bricked my galaxy s4 and tried everything to get it back up. couldnt get anything to take on it. Until I found this and I pushed it through via Odin 3.07 in the PDA slot. It took and I am back up. Much thanks my man
Is there a download with the NC1 stock flash? I am soft bricked at the Custom boot screen and can get to Download mode but that is all. I have safestrap but won't post past Samsung Splash screen with Unlock on it.
If no option how can I hard brick this phone so employer won't be able to turn it on?
morphius2036 said:
Is there a download with the NC1 stock flash? I am soft bricked at the Custom boot screen and can get to Download mode but that is all. I have safestrap but won't post past Samsung Splash screen with Unlock on it.
If no option how can I hard brick this phone so employer won't be able to turn it on?
Click to expand...
Click to collapse
There's a nb1 tar file in the general forum. Use that.
Sent from my Nexus 5 using XDA Free mobile app
I have an AT&T S4, with MF3 (I think). After installing safestrap successfully, I couldn't install a custom ROM so I kinda gave up and tried to flash it back to stock. I went all over the xda forums, and I attempted to flash about 3-4 stock ROMS using Odin, but none of them work; I always get the error message: <ID:0/005> FAIL! (Auth)
I attempted to flash the MFR.tar file at http://forum.xda-developers.com/showthread.php?t=2413746 and got the same FAIL! message from Odin.
Can anyone please help me?
Check my thread. ... http://forum.xda-developers.com/showthread.php?t=2573080 u can go back to stock MF3 using Odin with MF3.tar files.....and then if u decide to update to MK2 follow second post for guide. .... If u ever brick from MK2 follow third post to unbricked from gtj0 guide method that I edited and replace with MF3> MK2 update. Zip files from first post (OP).... goodluck. ..... Hope this help.. ... If I helped u ..... Hit Thank button. ...
Swyped from MK2 Deadly Venom SS
ted77usa said:
Check my thread. ... http://forum.xda-developers.com/showthread.php?t=2573080 u can go back to stock MF3 using Odin with MF3.tar files.....and then if u decide to update to MK2 follow second post for guide. .... If u ever brick from MK2 follow third post to unbricked from gtj0 guide method that I edited and replace with MF3> MK2 update. Zip files from first post (OP).... goodluck. ..... Hope this help.. ... If I helped u ..... Hit Thank button. ...
Swyped from MK2 Deadly Venom SS
Click to expand...
Click to collapse
I really appreciate your response! You're the only one who's reached out to me (in my desperate hour of need) and I'm thankful!
I checked your thread, downloaded Odin and MF3.tar files. I tried to flash the MF3 files onto my phone using Odin, but got the following error:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_ATT_I337ATTAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PLATFORM_I337UCUAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<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> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl2.mbn
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> aboot.mbn
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
As you can see, I'm still having that weird FAIL error. Any ideas what to do?
I went to Best Buy, and they said that it was permanently bricked. I feel so stupid. Anywhere I can sell a bricked phone?
Someone also suggested I install a custom recovery, but since it's bootlocked, I have no idea how to. Is it possible to install a custom recovery on an AT&T phone via Odin?
pwn4g3n3ss said:
I went to Best Buy, and they said that it was permanently bricked. I feel so stupid. Anywhere I can sell a bricked phone?
Someone also suggested I install a custom recovery, but since it's bootlocked, I have no idea how to. Is it possible to install a custom recovery on an AT&T phone via Odin?
Click to expand...
Click to collapse
Are u sure that u have MF3 firmware ... Since u said .... "I think" .....PM me for more help. ... Maybe I can help u........:good:
EDIT: CHECK YOUR PM>>>>>U SHOULD BE OK>>>>>LET ME KNOW HOW IT GO........
Swyped from MK2 Deadly Venom SS
I attempted to do my first root via the tutorial: ibtimes.co m/android-442-kitkat-released-samsung-galaxy-s4-canada-while-odin-flashable-update-availabl
follow all instructions to the key, and ran into these errors:
1. FAIL! as soon as I pressed Start ( i did have the blue light)
2. second attempt started successfully but stopped 3/4 way through and received a invalid percent of drawing download error
Im trying to flash a telus canada samsung s4 that had the 4.4.2 update stock.
what can i do?
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_I337MVLUFNC1_880525_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CP_I337MVLUFNC1_880525_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_I337MVLUFNC1_880525_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_OYA_I337MOYAFNC1_880525_REV06_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> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> persdata.img.ext4
<ID:0/004> system.img.ext4
<ID:0/004> __XmitData_Write
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/006> Added!!
lock1nout said:
I attempted to do my first root via the tutorial: ibtimes.co m/android-442-kitkat-released-samsung-galaxy-s4-canada-while-odin-flashable-update-availabl
follow all instructions to the key, and ran into these errors:
1. FAIL! as soon as I pressed Start ( i did have the blue light)
2. second attempt started successfully but stopped 3/4 way through and received a invalid percent of drawing download error
Im trying to flash a telus canada samsung s4 that had the 4.4.2 update stock.
what can i do
Click to expand...
Click to collapse
what i would do would be to downgrade to mk2 from i assume your on the NB1 build of 4.4.2
root using the saferoot methood or what i used was the kingo root methood, you can google kingo.
then flash a "already rooted" rom version of kitkat. i belive ShoStock rom is very close to stock but has some cool changes,
i am on the at&t network, i havent figured out quite yet how to flash shostock on my phone but ive been busy the past few days and havent been able to do any searching,
ill subscribe to this forum for you so you'll have someone watching for your post
anyone else have any ideas?
mejakola said:
what i would do would be to downgrade to mk2 from i assume your on the NB1 build of 4.4.2
root using the saferoot methood or what i used was the kingo root methood, you can google kingo.
then flash a "already rooted" rom version of kitkat. i belive ShoStock rom is very close to stock but has some cool changes,
i am on the at&t network, i havent figured out quite yet how to flash shostock on my phone but ive been busy the past few days and havent been able to do any searching,
ill subscribe to this forum for you so you'll have someone watching for your post
anyone else have any ideas?
Click to expand...
Click to collapse
thanks for the reply.
at this point, any firmware version of stock would do. Can i flash a stock 4.3 rom through, or is that too risky?
mejakola said:
what i would do would be to downgrade to mk2 from i assume your on the NB1 build of 4.4.2
root using the saferoot methood or what i used was the kingo root methood, you can google kingo.
then flash a "already rooted" rom version of kitkat. i belive ShoStock rom is very close to stock but has some cool changes,
i am on the at&t network, i havent figured out quite yet how to flash shostock on my phone but ive been busy the past few days and havent been able to do any searching,
ill subscribe to this forum for you so you'll have someone watching for your post
anyone else have any ideas?
Click to expand...
Click to collapse
By what he said he's on an I337m, different from the AT&T I337. Not only will the Safestrap method not work, it's more work than he needs.
lock1nout said:
thanks for the reply.
at this point, any firmware version of stock would do. Can i flash a stock 4.3 rom through, or is that too risky?
Click to expand...
Click to collapse
I don't know how downgrading goes, I believe you can flash a 4.3 though. I'd make sure that your 4.4 ODIN is a full download and the MD5 matches if there is one where you downloaded it. Also, when you retry the root, try just using the link to CF Auto Root from its thread in one of the development sections.
Sent from my GT-I9505 using xda app-developers app
DeadlySin9 said:
By what he said he's on an I337m, different from the AT&T I337. Not only will the Safestrap method not work, it's more work than he needs.
I don't know how downgrading goes, I believe you can flash a 4.3 though. I'd make sure that your 4.4 ODIN is a full download and the MD5 matches if there is one where you downloaded it. Also, when you retry the root, try just using the link to CF Auto Root from its thread in one of the development sections.
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
im currently downloading the stock rom for my phone and region and carrier from the samsung updates site. I going to try a 4.4 first. I did not see a MD5 file listed along with the zip.
Can you explain to me a little more on how to 'link to CF Auto Root'?
lock1nout said:
Can you explain to me a little more on how to 'link to CF Auto Root'?
Click to expand...
Click to collapse
You need to find the thread for your phone for cf auto root and there will be a clickable link for you and will take you to chainfires Google plus page with the correct files
mejakola said:
You need to find the thread for your phone for cf auto root and there will be a clickable link for you and will take you to chainfires Google plus page with the correct files
Click to expand...
Click to collapse
I follow the instructions for the CF-Auto boot. Every seems to load up fine until i got the the samsung boot screen after recovery mode and stuck there. I tried a cache wipe and even a factory reset and it still sticks at the boot screen. I also tried to reflash the cf auto boot to not avail.
im back to stock, thanks to everyone for their help.
EDIT: Sorry for the bad title. Derp.
So my phone, AT&T Galaxy S4, is running into problems. It was running rooted MK2 firmware with Safestrap 3.72 installed on top. I was trying to flash Paranoid Android 4.6 Beta 5 onto the device, but the device would, upon booting to the intro screen, give some message about com.android.phone not working or something. This message would constantly throw itself up no matter how many times I would tap "okay." Anyways, onto the other stuff. I was tired of the bad flashing and decided to try to wipe Data in the separate button with Safestrap's recovery. While the wipe was running, the phone shut down and went into this state...
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." Accompanied by an image of a phone connected by a large dotted line to a computer monitor with a large yellow warning sign in the middle. In the upper right is...
HTML:
ODIN MODE
PRODUCT NAME: SGH-I377
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
Download mode is ordinary but the phone will not flash correctly. I have tested multiple cables and USB ports along with Odin 3.07 and 3.09, as well as the All-in-One and 4-part MK2 Odin files, but nothing works. They all output this:
HTML:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_I337UCUEMK2_1921628_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_I337UCUEMK2_1921628_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CP_I337UCUEMK2_1921628_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_ATT_I337ATTEMK2_1921628_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sbl1.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl2.mbn
<ID:0/006> sbl3.mbn
<ID:0/006> rpm.mbn
<ID:0/006> aboot.mbn
<ID:0/006> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
I've heard something about a PIT file which can save me and also that Best Buy can flash my phone back to stock. Any hope in these avenues?
If try flashing the nb1 tar file. You can find it in the general forum. A pit file isn't going to do you any good
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
If try flashing the nb1 tar file. You can find it in the general forum. A pit file isn't going to do you any good
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
So just flash the .tar file using Odin's PDA slot? Not the PIT file in this NB1 post?
Razznak said:
So just flash the .tar file using Odin's PDA slot? Not the PIT file in this NB1 post?
Click to expand...
Click to collapse
Yes, PDA slot
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Yes, PDA slot
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Well it is currently downloading at less than 100 KBps, so the download time is going to be something like 12 hours. I will post back when it is downloaded.
Never mind. I have the same file downloaded from when I flashed the MK2 Odin file a while ago.
Razznak said:
So just flash the .tar file using Odin's PDA slot? Not the PIT file in this NB1 post?
Click to expand...
Click to collapse
The fail auth indicates that you have a newer boot loader than the one being flashed. That means you have to flash NB1. You don't need the pit file. Just ensure that re-partition is unchecked in Odin.
I flashed the NB1 tar and everything seems good. Took a while to boot, but it hit the Ready2Go screen and all seems well. Will report back when I try to restore my backup I made before trying to flash the custom ROM.
Razznak said:
I flashed the NB1 tar and everything seems good. Took a while to boot, but it hit the Ready2Go screen and all seems well. Will report back when I try to restore my backup I made before trying to flash the custom ROM.
Click to expand...
Click to collapse
I've hit a problem. After restoring the backup on the NB1 recovery using Safestrap 3.72 (same as when I made the backup), the phone won't boot. Instead, it stays on the looping part of the boot animation for a while until it just shuts itself off.
I should note that on the NB1 OS I used Odin to flash yesterday, the Wi-Fi would not activate.
Razznak said:
I've hit a problem. After restoring the backup on the NB1 recovery using Safestrap 3.72 (same as when I made the backup), the phone won't boot. Instead, it stays on the looping part of the boot animation for a while until it just shuts itself off.
I should note that on the NB1 OS I used Odin to flash yesterday, the Wi-Fi would not activate.
Click to expand...
Click to collapse
I realized that I actually flashed the MK2 .tar file in Odin, that was my problem. Flashed the NB1 file and had to use Towelroot to get root, but I am back to where I was with my backup.