I got a S4 today and I rooted it, and flashed CWM recovery, backed up the firmware, rebooted and everything was good. I updated the phone an hour so later and the boot hung on yellow Sprint screen. I rebooted into recovery and re-flashed my backup but that didn't fix the device. Now I've been trying to flash back to stock using Odin and this is what I see.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUEMK2_L720SPTEMK2_L720VPUEMK2_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> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/004> Added!!
I was on 4.3 when this all started so I am attempting to flash the MK2 file back on my device. I removed the drivers, and re-installed and that made no difference. Any advice would be great.
Did you accept an OTA? Or did you try to flash a stock MK2 ROM?
I'd say flash an older tar if possible, especially if you plan to root again or install a custom ROM. The MK2 bootloader has KNOX enabled, so any root/custom ROM installs trip the counter.
sorry if this doesn't help, but have you tried different versions of odin? also tried different usb ports? idk what you're flashing or if this is what you want, but there's a stock mk2 rom on this thread if you wanna' try that. http://forum.xda-developers.com/showthread.php?t=2575470
I believe it updated via OTA after I activated it today. This was before I rooted. I am currently trying to flash the MK2 Rom. I've also tried MJA which is older. Is there an different older one that could work? I am planning on rooting again, but was going to run the stock rom for the time being. I've never an a touchwiz rom so I'm interested in trying it.
I have tried 3.09, 3.07, 1.85 for versions of Odin. All the same error.
I'm able to flash TWRP recovery from Odin without the error, but not the stock rom which is a bit confusing to me.
When you say
I updated the phone an hour so later
Click to expand...
Click to collapse
what did you 'update' it to and how? And even why?
Did you run Odin 'As administrator'?
What version of Odin are you using? 1.85 and 3.07 seem to work well.
Are you using a new USB cable? I've seen LOADS of issues with USB cables (ports too)
---------- Post added at 10:58 PM ---------- Previous post was at 10:57 PM ----------
Try and boot to stock recovery and do a factory reset.
Oh and also you are not BRICKED, you're just borked.
leaderbuilder said:
When you say what did you 'update' it to and how? And even why?
Did you run Odin 'As administrator'?
What version of Odin are you using? 1.85 and 3.07 seem to work well.
Are you using a new USB cable? I've seen LOADS of issues with USB cables (ports too)
---------- Post added at 10:58 PM ---------- Previous post was at 10:57 PM ----------
Try and boot to stock recovery and do a factory reset.
Oh and also you are not BRICKED, you're just borked.
Click to expand...
Click to collapse
I updated some apps and rebooted. Always find that this best after a lot of app updates.
Odin running as admin on Win 7 64. Mostly been using 3.07. USB cable is the new one that ship with the phone.
I've been looking for a stock recovery I can flash with Odin but can't seem to find one. Can you provide a link? Maybe I'm just missing it?
Are you flashing the full MK2 including boot? There's some thing where the phone refuses to boot into an MK2 ROM unless you've updated the bootloader as well.
I got the full rom from here: http://forum.xda-developers.com/showthread.php?t=2601443 I also tried flashing MJA too and I get the same message in Odin. I'm sure that I have the MK2 bootloader as it shows my knox being 0x1.
Since you are on MK2 already try using the 3.09 version of odin. It seems to work best with MK2. Also, if you have the MJA tar file try that one. Either MJA or MK2 should flash on your phone.
cruise350 said:
Since you are on MK2 already try using the 3.09 version of odin. It seems to work best with MK2. Also, if you have the MJA tar file try that one. Either MJA or MK2 should flash on your phone.
Click to expand...
Click to collapse
I re-downloaded Odin 3.09, USB drivers (using 1,5,29), the rom and attempted to flash again and get the same error in Odin. Same result with MJA too.
benpfeil said:
I re-downloaded Odin 3.09, USB drivers (using 1,5,29), the rom and attempted to flash again and get the same error in Odin. Same result with MJA too.
Click to expand...
Click to collapse
Hmm, you're doing or missing something because in the last week or so there have been about five or ten people with close to the same issue (HELP, I'M BRICKED, MY LIFE IS OVER...etc.) and we've mangaged to get them all work. I've posted dozens of replies to those people and they've been able to get up and running following others and my advice(s).
Spend some time and go through the first few pages of the Q&A, Help forum and read all the way through some of the similar posts. Then try what is suggested in them.
You will resolve your issue. IF you don't, just warranty your phone or grab an iPhone.
I broke down and stopped into Sprint tonight. I had tried the process on 3 different PC's and still no luck. They tried to flash it and weren't able to as well. The woman in the store told me they could not exchange it because they do not have the phone yet. I was confused by this. The phone that I have has "Sprint Spark" on it which is a tri-band phone and the stores do not have it yet. My company has a large plan with Sprint and we get our phones shipped directly to us. She said I would have to have my procurement person request a new phone for me. My model is actually SPH-L720T. My guess is that this was causing my issues.
Thank you to you all who tried to help out.
My model is actually SPH-L720T. My guess is that this was causing my issues.
Click to expand...
Click to collapse
YEP!
That would be the problem.
leaderbuilder said:
YEP!
That would be the problem.
Click to expand...
Click to collapse
Just wasn't making any sense to me up until then. I've done numerous phones and never had any issue before so I was just baffled.
Trying to find a MK5 rom that will download. Working on one now that is pulling in at < 200 KB/s.
benpfeil said:
Just wasn't making any sense to me up until then. I've done numerous phones and never had any issue before so I was just baffled.
Trying to find a MK5 rom that will download. Working on one now that is pulling in at < 200 KB/s.
Click to expand...
Click to collapse
I didn't think XDA had a forum up yet for SPH-L720T.
Sammobile.com has the mk5 tar file for the 720T.
Sent from my icrap 2 using Tapatalk HD
Related
This has been a long day...
I previously rooted my N900V Note 3 using the Root_de_la_Vega method. Everything was fine until last night when I stupidly accepted the OTA update from Verizon. I lost root because I forgot to persist Super User. Without thinking I started to reroot using the original Root_de_la_Vega method. The ODIN attempt failed.
This is the message stream from ODIN:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Root_de_la_Vega.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> cache.img.ext4
<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)
Also, on the top of my Note 3 it says SECURE CHECK FAIL : cache
My phone will now only boot into ODIN download screen, and gives me the message: "Firmware upgrade encountered as issue. Please use Software Repair Assistant & try again."
My guess is that I have tried to flash/download a mismatched ROM.
Any suggestions on how to get past the ODIN boot screen and back into normal operation?
Any help would be appreciated, obviously...
Read this thread
http://forum.xda-developers.com/showthread.php?t=2516667
Flash the pit
ANYBODY ELSE ON MJ7 DO NOT TRY FLASHING BACK TO MI9 OR DE LA VEGA OR THIS IS WHAT HAPPENS.
NeoMagus said:
Read this thread
http://forum.xda-developers.com/showthread.php?t=2516667
Flash the pit
ANYBODY ELSE ON MJ7 DO NOT TRY FLASHING BACK TO MI9 OR DE LA VEGA OR THIS IS WHAT HAPPENS.
Click to expand...
Click to collapse
How/where do I find the PIT file?
http://forum.xda-developers.com/showthread.php?t=2483380
NeoMagus said:
http://forum.xda-developers.com/showthread.php?t=2483380
Click to expand...
Click to collapse
Freak man, thank you so much.
So if I wanted to get root back, I would flash the VRUBMJ7 file, and then go through the de la vega method again?
cmubigguy said:
Freak man, thank you so much.
So if I wanted to get root back, I would flash the VRUBMJ7 file, and then go through the de la vega method again?
Click to expand...
Click to collapse
NO, using the old software with new update will just brick your phone again... Dont do it.
The only root method once on the new update is not condoned by XDA at the moment but if you do some searching youre sure to find it
NeoMagus said:
NO, using the old software with new update will just brick your phone again... Dont do it.
The only root method once on the new update is not condoned by XDA at the moment but if you do some searching youre sure to find it
Click to expand...
Click to collapse
I guess I'll just wait for a safe way to root post-OTA. I can live with no root for a while. Thanks for helping out, I shot you some cash for your time and not making me feel like a complete idiot.
I rooted after OTA with something that rhymes with bingo. Had no problems.
Sent from my Galaxy Note 3
goldy253 said:
I rooted after OTA with something that rhymes with bingo. Had no problems.
Sent from my Galaxy Note
Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
goldy253 said:
I rooted after OTA with something that rhymes with bingo. Had no problems.
Sent from my Galaxy Note 3
Click to expand...
Click to collapse
I just tried what rhymes with bingo, and it didn't work. It's likely because I just took the OTA straight away without using Kies or unrooting through SU. What was your unroot/re-root method?
I did a full unroot before doing and used it. When it was done it had said it failed (not supported), but supersu had actually been installed and was in the app drawer. Used it to get safestrap installed then flashed the good supersu binary from chainfire's site to get rid of the bad one
NeoMagus said:
I did a full unroot before doing and used it. When it was done it had said it failed (not supported), but supersu had actually been installed and was in the app drawer. Used it to get safestrap installed then flashed the good supersu binary from chainfire's site to get rid of the bad one
Click to expand...
Click to collapse
When I try to flash the updated SuperSU files, I get a "Failed to verify whole file signature" error and it aborts. Thoughts?
cmubigguy said:
When I try to flash the updated SuperSU files, I get a "Failed to verify whole file signature" error and it aborts. Thoughts?
Click to expand...
Click to collapse
Do you have the newest safestrap apk?
http://forum.xda-developers.com/showthread.php?t=2517610
it went thru without an issue for me might be worth posting in that thread
NeoMagus said:
Do you have the newest safestrap apk?
http://forum.xda-developers.com/showthread.php?t=2517610
it went thru without an issue for me might be worth posting in that thread
Click to expand...
Click to collapse
Do now. It turns out I needed to reboot my laptop after I installed Kango.
I'm back rooted!
I wasn't previously rooted. I took the OTA then rooted with bingo. Then installed safe strap with no problems.
Sent from my Galaxy Note 3
NeoMagus said:
Read this thread
http://forum.xda-developers.com/showthread.php?t=2516667
Flash the pit
ANYBODY ELSE ON MJ7 DO NOT TRY FLASHING BACK TO MI9 OR DE LA VEGA OR THIS IS WHAT HAPPENS.
Click to expand...
Click to collapse
This worked for me, I flashed the pit for MJ7 and was able to get out of soft brick
Had the same issue, resolved with .pit solution above. Can we include a note in the N900V Root de la Vega instructions? IE: If you have update to Baseband version N900VRUBMJ7, attempting to flash through Odin will fail on cache writing.
I had the exact same problem as OP. Tried to follow steps, kind of got lost.
So, I was able to unbrick the phone using Odin with VZW_32gb.pit. It boots up fine now, I'm still on MJ7. No root. So, how do you get your root back from this point? I can't use safestrap since no root. Kingo doesn't work either -- if my phone is fully booted, it can't connect to it; if I'm in vol-down/home/power mode, Kingo tries, but fails.
kalagula said:
I had the exact same problem as OP. Tried to follow steps, kind of got lost.
So, I was able to unbrick the phone using Odin with VZW_32gb.pit. It boots up fine now, I'm still on MJ7. No root. So, how do you get your root back from this point? I can't use safestrap since no root. Kingo doesn't work either -- if my phone is fully booted, it can't connect to it; if I'm in vol-down/home/power mode, Kingo tries, but fails.
Click to expand...
Click to collapse
After you install Kango, don't enter the download mode, just boot the phone as normal and make sure USB debugging is on. Attach the phone to Kango, and it will download and install the necessary drivers. Once those are done, you can attempt to root, but it likely won't take. Restart your computer, and then reattach the phone. Try to root method again, and it should work. That's what worked for me.
cmubigguy said:
Try to root method again, and it should work.
Click to expand...
Click to collapse
Yeah, mine just sits there for a while, after which it says "ROOT failed! NotSupport". Bummer!
Edit: after 5 tries, it worked. Still got the ROOT failed error, but I did get root! Thanks for your help.
My samsung Galaxy is totaly dead after I try to root the system.
Noy my phone is stay in Downloading mode, can't boot up, or recover mode.
I was using ATT OS and uppdrage to Android 4.3, after I upgrade, rood function is not working any more. Super user is ask my to manual root again.
my recover mode is still original can't back up or install any ROM.
can any one please help me provide how to flash my phone, may need some .md5 or .tar by using Odin3-v1.85 to reflash boot rocover mode that I can install other rom from web.
thank you , thank you please help.......................
Sam
sammaspda said:
My samsung Galaxy is totaly dead after I try to root the system.
Noy my phone is stay in Downloading mode, can't boot up, or recover mode.
I was using ATT OS and uppdrage to Android 4.3, after I upgrade, rood function is not working any more. Super user is ask my to manual root again.
my recover mode is still original can't back up or install any ROM.
can any one please help me provide how to flash my phone, may need some .md5 or .tar by using Odin3-v1.85 to reflash boot rocover mode that I can install other rom from web.
thank you , thank you please help.......................
Sam
Click to expand...
Click to collapse
What is your baseband?
AT&T Galaxy S4 SGH-I337 RUNNING HYPERDRIVE 12
[email protected] said:
What is your baseband?
AT&T Galaxy S4 SGH-I337 RUNNING HYPERDRIVE 12
Click to expand...
Click to collapse
thank you for help...
my is ATT I337 xxxxMF3, ..not sure, I try to root, after root ...is brick, please please help.
sammaspda said:
thank you for help...
my is ATT I337 xxxxMF3, ..not sure, I try to root, after root ...is brick, please please help.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2502003
Download the md5 tar file. And flash via odin
AT&T Galaxy S4 SGH-I337 RUNNING HYPERDRIVE 12
[email protected] said:
http://forum.xda-developers.com/showthread.php?t=2502003
Download the md5 tar file. And flash via odin
AT&T Galaxy S4 SGH-I337 RUNNING HYPERDRIVE 12
Click to expand...
Click to collapse
thank you for your help.
Can you please let me know how should I choose this file? by using Odin3
which one I have to choose........Filedownload form "Bootloader" or "PDA"
thank you,
sammaspda said:
thank you for your help.
Can you please let me know how should I choose this file? by using Odin3
which one I have to choose........Filedownload form "Bootloader" or "PDA"
thank you,
Click to expand...
Click to collapse
I try all of them, now phone is asking me
Firmware upgrade encountered an issue. please selete recover mode in Kies & try again.
But I try to connect Kies to recover, but Kies can;t connected phone.....still need help.....
please please ...
thank you
sammaspda said:
I try all of them, now phone is asking me
Firmware upgrade encountered an issue. please selete recover mode in Kies & try again.
But I try to connect Kies to recover, but Kies can;t connected phone.....still need help.....
please please ...
thank you
Click to expand...
Click to collapse
Follow this guide by gtj0 http://forum.xda-developers.com/showthread.php?t=2526964
Or
There is a link to a guide to show you how to use this. You need to use Odin 3.07 or 3.09 http://www.droidviews.com/how-to-unbrick-your-bricked-samsung-galaxy-s4-gt-i9500-gt-i9505/
AT&T Galaxy S4 SGH-I337 RUNNING HYPERDRIVE 12
<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..
<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> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> recovery.img
<ID:0/006> persdata.img.ext4
<ID:0/006> system.img.ext4
<ID:0/006> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
Still failed.....screen always ask me use Kies to update firmware, but Kies still unable to undate............
still need more help.....
thank you
sammaspda said:
<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..
<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> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> recovery.img
<ID:0/006> persdata.img.ext4
<ID:0/006> system.img.ext4
<ID:0/006> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
Still failed.....screen always ask me use Kies to update firmware, but Kies still unable to undate............
still need more help.....
thank you
Click to expand...
Click to collapse
Go to best buy and have them reflash your firmware.
AT&T Galaxy S4 SGH-I337 RUNNING HYPERDRIVE 12
I went best buy this morning but they unable reflash my phone.
they ask call 1800 to get repair.......
If you were trying to upgrade to 4.3 and it failed, you might have to follow these directions: http://forum.xda-developers.com/showpost.php?p=48927617&postcount=3
sammaspda said:
I went best buy this morning but they unable reflash my phone.
they ask call 1800 to get repair.......
Click to expand...
Click to collapse
Your going to lose mf3. Follow that guide I posted earlier by gtj0 download the emergency files flash via Odin in PDA then adb sideload mf3-mj9 then mj9-mk2
AT&T Galaxy S4 SGH-I337 RUNNING HYPERDRIVE 12
---------- Post added at 06:49 PM ---------- Previous post was at 06:48 PM ----------
DeadlySin9 said:
If you were trying to upgrade to 4.3 and it failed, you might have to follow these directions: http://forum.xda-developers.com/showpost.php?p=48927617&postcount=3
Click to expand...
Click to collapse
I think he was trying to reflash the mf3 firmware
AT&T Galaxy S4 SGH-I337 RUNNING HYPERDRIVE 12
thank you for your help....I total give it up now....
I already try over weekend spend over 48HRs to working with phone.
always get problem, I have to send to JTAG not, thank you for your help.
How do you think JTAG repair service?
http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=190990521197&ssPageName=ADME:X:RTQ:US:1123
thank you
Sam
sammaspda said:
thank you for your help....I total give it up now....
I already try over weekend spend over 48HRs to working with phone.
always get problem, I have to send to JTAG not, thank you for your help.
How do you think JTAG repair service?
http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=190990521197&ssPageName=ADME:X:RTQ:US:1123
thank you
Sam
Click to expand...
Click to collapse
Don't give up so easy. ... If you tell us what kinda root method did u use it might help us to help you figure it out what is your firmware. ....MF3 use jortex method to root. ...(format your sd card to exfat and use terminal emulator)......If already on 4.3 MK2 u should use SAFEROOT METHOD from Verizon forum. .... follow my thread..... http://forum.xda-developers.com/showthread.php?t=2573080.... it will get u back on track. ...... If u are MF3 just use MF3.tar files from first post. ....If u think u are Mk2 using that one click tool..... (Most likely u are MK2 already. ... Since u said u upgraded to 4.3 and root doesn't work anymore).... Then u should go to post#3 follow the guide. .....u should be ok..... save that money.... If u need more help PM me......
Swyped_from_SS_MK2_Tapatalk
Jtag service man told me..."It looks like the bootloader is permanentaly locked with the rom you tried flashing"
do you know how to solve?
thank you
sammaspda said:
Jtag service man told me..."It looks like the bootloader is permanentaly locked with the rom you tried flashing"
do you know how to solve?
thank you
Click to expand...
Click to collapse
sammaspda said:
My samsung Galaxy is totaly dead after I try to root the system.
Noy my phone is stay in Downloading mode, can't boot up, or recover mode.
I was using ATT OS and uppdrage to Android 4.3, after I upgrade, rood function is not working any more. Super user is ask my to manual root again.
my recover mode is still original can't back up or install any ROM.
can any one please help me provide how to flash my phone, may need some .md5 or .tar by using Odin3-v1.85 to reflash boot rocover mode that I can install other rom from web.
thank you , thank you please help.......................
Sam
Click to expand...
Click to collapse
From my understanding that u are on MF3 and u updated to 4.3 MK2 firmware but your root isn't working (coz MK2 use different ROOT method....it called SAFEROOT) ....so i'm guessing u used terminal emulator ( same root method ) from MF3....or i dunno what u did manually (ADB shell maybe) ....u don't give enough information so other can help u......and then u hit bricked wall.......FOLLOW MY THREAD ON POST#3 MK2_UNBRICKED_METHOD from gtj0 guide that i edited .....make sure u download MF3>MK2update.zip from OP(Original Post) coz u gonna need it in the end .....download and extract all MF3-emergencypart 1 and 2 files......recovery-mj6.tar.md5....(or i337MK2stockrecovery.tar.md5...it also work with some user)....and follow the guide flashing via ODIN.....READ OP,post#2,post#3 make sure u understand everything before u damage more your expensive S4......need more help just PM me.....GOODLUCK.....U SHOULD BE OK....:good:....To show your appreciation in the future .......instead of typing thank you.....thank you....thank you......hit THANK button.....
Im having similar woes. I had problems installing a ROM, softbricked, tried restore to 4.2.2, wouldnt go, tried updating (stupidly) to 4.3 got obKNOXious (had no clue then about knox) tripped knox by trying to go back to 4.2.2 and got firmware update fail. Stuck with no recovery, nor any way of repairing. I tried many versions of ODIN, both kies emergency firmware update options, and heimdall. Heimdall seems promising as i have been able to flash a custom recovery with --no-reboot and reboot using pwr+home+vlup, and i get a warning about tripping knox but it boots into custom recovery. I am able to flash (CM11 for example) but it gives me kernel trips on knox and shuts down on boot. i saw your other thread about the mf3 and mk3 but im not sure if they would work for my variant. no matter what i try i cant get this paperweight to its former glory. local repair center said they wont do anything as knox warranty = tripped. no best buy samsung centers in my area. someone please help.
ted77usa said:
From my understanding that u are on MF3 and u updated to 4.3 MK2 firmware but your root isn't working (coz MK2 use different ROOT method....it called SAFEROOT) ....so i'm guessing u used terminal emulator ( same root method ) from MF3....or i dunno what u did manually (ADB shell maybe) ....u don't give enough information so other can help u......and then u hit bricked wall.......FOLLOW MY THREAD ON POST#3 MK2_UNBRICKED_METHOD from gtj0 guide that i edited .....make sure u download MF3>MK2update.zip from OP(Original Post) coz u gonna need it in the end .....download and extract all MF3-emergencypart 1 and 2 files......recovery-mj6.tar.md5....(or i337MK2stockrecovery.tar.md5...it also work with some user)....and follow the guide flashing via ODIN.....READ OP,post#2,post#3 make sure u understand everything before u damage more your expensive S4......need more help just PM me.....GOODLUCK.....U SHOULD BE OK....:good:....To show your appreciation in the future .......instead of typing thank you.....thank you....thank you......hit THANK button.....
Click to expand...
Click to collapse
sammaspda said:
Jtag service man told me..."It looks like the bootloader is permanentaly locked with the rom you tried flashing"
do you know how to solve?
thank you
Click to expand...
Click to collapse
OK im shocked but somehow i made this work. i used to kies to download firmware by using firmware upgrade and initialization under tools and grabbing the firmware from windows user/appdata/local/temp folder after kies finished downloading (as it starts decompressing)(faster than waiting to download from sammobile). i then pulled all files out of md5 using 7zip, and used heimdall to flash all files to their respective partitions/mountpoints. rebooted still no recovery nor boot. tried again and nothing. i then tried a custom recovery and it gave me seandroid enforcing RECOVERY and restart. so then i tried flashing custom recovery again using heimdall with --no-reboot switch and rebooted with volup+home+pwr and then i was able to enter custom recovery. so i wiped data and cache rebooted got nothing, no recovery no boot just dl mode. so i then reflashed stock rom through heimdall and rebooted, got stock recovery which would try to do something (progress bar appeared) and bootlooped. so i reflashed custom recovery again wiped cache and data and /data /media option (which took longer even though no extsdcard present, which puzzled me) and this time i tried to mount system in recovery and got an error. so i formated /system and it mounted fine. rebooted no boot no recovery. flashed custom recovery wiped /data /media, /cache, /dalvik, formated /sdcard, /system, /data, /cache, mounted /system and rebooted right into download mode and flashed stock image but this time with --no-reboot switch and once finished i manually rebooted into recovery. recovery did its thing and i finally i got a boot animation and glowing led, left it for 10 minutes and it was at samsung setup screen. unplugged my phone instantly died. no boot no recovery. repeated last step but once in samsung os i went to settings backup and reset menu and reset the phone from there. it went into recovery on its own, erased and rebooted and it seems to work fine now (fingers crossed, its only been ten minutes (relatively little compared to this 2 week ordeal.) Oddly enough kies downloaded a bell version although my phone is fido
Please lend a hand to help me rectify a problem.
Started earlier today by CF-Auto-Root my New Rogers SGH-i1337m, installed without incident via Odin 3.07, followed up with TWRP 2.7 install, again via Odin, without incident, then created NANDROID backup to ext sdcard.
First issues started cropping up, but culminating in what appears to be soft bricking:
1st) Could not mount internal memory (was attempting to browse in Windows) via TWRP. Every time I would select internal memory it would mount the sd card contents only. Weird, but pales compared to further issues.
2nd) Was preparing to install Custom ROM, boot into TWRP, attempted factory reset but this just constantly restarted TWRP. Thought this was strange so I figured Id use Goomanager to update TWRP, occurred without incident and I went back to attempt to factory reset, but then trouble started.
3rd) Boot looping, could not boot back into the OS. Decided I would attempt to restore my Nandroid backup, TWRP loads fine but restore didn't work. Figured Id try flashing back to stock rom (obtained RWC-I337MVLUEMK6-20131125124040 via links in other comments. This is where things got out of control:
A) Restore via Odin 3.07 failed, device restart failedbut loaded the "Firmware Upgrade encountered an issue..." screen.
B) Attempted redownloading the stock rom, new usb port, new oem cable, reinstalled drivers, and with each Odin would fail as follows:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUEMK6_I337MOYAEMK6_I337MVLUEMK6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
C) Briefly TWRP would not load, so I reflashed 2.7.0.1 for openrecovery-twrp-2.7.0.1-jfltecan without incident, TWRP reloaded fine, could now do factory reset, but often end up getting could not mount /system. Now using TWRP to restore theNANDRPID from earlier seemed to rebuild the partitions and said it was successful, and the device will boot to a static Samsung screen, but after 20 mins of waiting, would not boot farther.
D) At this point tried to reflash w Odin 3.07 the stock, but still get that error.
So here is where I'm at, with what appears to get me the closest to booting/flashing with stock:
1) Reflashed openrecovery-twrp-2.7.0.1-jfltecan.tar with Odin 3.07, immediately following this:
<ID:0/004> Removed!!
<ID:0/006> Added!!
<ID:0/006> Removed!!
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
..and the device hangs @ "Samsung Galaxy S4" black screen, letting that sit for 15mins without any change (didn't expect it to, but may as well be complete).
2) TWRP is bootable (load screen says Recovery is not SEANDROID ENFORCED and Set Warranty Bit: recovery) and functional, rebooting recovery states "No OS installed, are you sure you want to restart? ". Interestingly with 2.7.0.1 now installed, i can factory reset but with errors "E: unable to mount '/system". In TWRP, i have tried restore of my NANDROID backup, it completes successfully and appears to rebuild the partitions, but even after completing the restore and rebooting, still end up hanging at the static Samsung screen for >20mins without a change. I could transpose the entire log from the restore if needed.
3) At this point I would try Odin 3.07 with the above stock image, and the failure when attempting to write system occurs again.
Ive been searching for hours and hours and attempting to reflash but not making any headway.
Could anyone help point me in some better directions? I just finished attempting KIES emergency restore, but it too failed when it tried to upload to the device.
Any help would be greatly appreciated.
You've done all the right things. The only other thing I can think of is using a different firmware version in Odin.
Sent from my Nexus 5
jd1639 said:
You've done all the right things. The only other thing I can think of is using a different firmware version in Odin.
Sent from my Nexus 5
Click to expand...
Click to collapse
Perhaps I should try flashing a custom rom? Maybe something like CM 10.2?
I think the problem lies with a possible permission problem with the system partition, but I don't know how to go about checking those permissions, let alone correcting a possible fault.
Thoughts?
Did you factory reset in stock recovery before you installed twrp?
Sent from my SGH-I337M using Tapatalk
2Tone5 said:
Did you factory reset in stock recovery before you installed twrp?
Sent from my SGH-I337M using Tapatalk
Click to expand...
Click to collapse
I believe so, but it has been several iterations of different attempts to fix things that I cannot be certain any longer.
Let's pretend I didn't, for arguments sake. Implications?
Furthermore, I have created some life back into the device; however, still having problems.
1) Using ODIN 3.09, I successfully flashed TWRP back on to the device.
2) With TWRP, I successfully flashed CM 10.2. The device loads completely into the OS--the only thing I cannot confirm yet is full telephone functionality as my backup phone is what was reconnected to ROGERS. So.....there is life in this thing yet.
3) With TWRP, I have successfully created NANDROID backup of the device under 10.2 and used it to restore after a few failed attempts at getting to stock.
So here's a problem for right now: No matter what source stock ROM I have been using, I337MVLUFNC1_I337MOYAFNC1_I337MVLUFNC1_HOME.tar.md5 or I337MVLUFNC1_880525_REV06_user_low_ship_MULTI (both are what were claimed to be stock 4.4.2 for sgh-i337m ROGERS), it consistently fails in ODIN when flashing system.
I can easily then reflash TWRP (because the ODIN flashing the above stock breaks the recovery image), get into TWRP and restore the CM10.2 NANDROID, and at least back in business there.
I'm about to try flashing (again, but likely fruitlessly) RWC-I337MVLUEMK6-20131125124040.zip from samsung-updates.com via ODIN 3.09. I don't have much hope that ODIN will get it onto the device.
Seems to me like perhaps ODIN can't get the stock roms onto the device for some reason!? Am I doing something wrong? Perhaps someone can point me to a stock 4.3 (or 4.4.2) ROM for ROGERS SGH-i337M that is known to work (or at least deemed reliable) that I could try? Perhaps ODIN is messed up for me?
I'm pretty frustrated as I would think if I can install via TWRP a custom kernel and custom ROM, I should be able to get the stock ROM/etc. back onto the device.
Perhaps I'm missing a step?
TWRP: Wipe> Factory Reset then wipe Cache.
Reboot into Download Mode
ODIN 3.09: Added!! --> AP Select my stock ROM (any of the above), only have Auto Reboot and F. Reset Time selected, start (then fail in my case).
Perhaps I should find another computer!? I have two OEM cables, tried both ports......
This is ridiculously frustrating.
Which bootloader are you on?
Sent from my SGH-I337M using Tapatalk
Just wanted to say that I got burned by TRWP a few days ago due to the same issues.
1) Flashed a custom kernel days before. Was working fine but didn't like the performance of the new kernel so I decided to restore my backups of /boot and /system.
2) Did the restore. Cleared /cache and dalvik. Reboot.
3) Stuck on the Samsung Galaxy S4 bootloader screen.
4) Tried to reboot into TWRP, but didn't work. Would just cause phone to automatically restart and hang at the bootloader screen.
5) After many many reboots, was able to finally boot into TWRP.
6) Flashed a custom ROM based the original stock ROM I had installed and that got me up and running again. No data loss as I never touched /data with TWRP.
I'm currently experimenting with CWM and Philz. TWRP, never again.
2Tone5 said:
Which bootloader are you on?
Sent from my SGH-I337M using Tapatalk
Click to expand...
Click to collapse
Uncertain at this point -- any way to determine that or just flash a known decent one?
Interestingly: CM10.2.1 everything works except for calls and any other sound on the device. ......this is ridiculous.
bzwick said:
Uncertain at this point -- any way to determine that or just flash a known decent one?
Interestingly: CM10.2.1 everything works except for calls and any other sound on the device. ......this is ridiculous.
Click to expand...
Click to collapse
Upon more research, I guess I have a knox bootloader since I have a Knox 0x1 trip.
bzwick said:
Upon more research, I guess I have a knox bootloader since I have a Knox 0x1 trip.
Click to expand...
Click to collapse
Without knowing exactly, theres more trial and error ... so ill give you an example: you can't flash 4.2.2 firmware.tar.md5 over a 4.4.2 bootloader (which sounds like you may have )in odin anymore due to knox. What I can suggest to you that should work is go to sammobile.com and download the latest 4.4.2 official firmware for the 1337m and follow the instructions precisely on the download page.
Sent from my SGH-I337M using Tapatalk
---------- Post added at 12:14 AM ---------- Previous post was at 12:12 AM ----------
http://www.sammobile.com/firmwares/
Sent from my SGH-I337M using Tapatalk
---------- Post added at 12:16 AM ---------- Previous post was at 12:14 AM ----------
Once you download it and its installed make sure to turn off your phone and boot into stock recovery and do a factory reset and if you really want to be clean flash the firmware again and all your problems should be gone
Sent from my SGH-I337M using Tapatalk
2Tone5 said:
Without knowing exactly, theres more trial and error ... so ill give you an example: you can't flash 4.2.2 firmware.tar.md5 over a 4.4.2 bootloader (which sounds like you may have )in odin anymore due to knox. What I can suggest to you that should work is go to sammobile.com and download the latest 4.4.2 official firmware for the 1337m and follow the instructions precisely on the download page.
Sent from my SGH-I337M using Tapatalk
---------- Post added at 12:14 AM ---------- Previous post was at 12:12 AM ----------
http://www.sammobile.com/firmwares/
Sent from my SGH-I337M using Tapatalk
---------- Post added at 12:16 AM ---------- Previous post was at 12:14 AM ----------
Once you download it and its installed make sure to turn off your phone and boot into stock recovery and do a factory reset and if you really want to be clean flash the firmware again and all your problems should be gone
Sent from my SGH-I337M using Tapatalk
Click to expand...
Click to collapse
Ok, I'll give it a go and report findings as follows (decided to try a different computer to eliminate that fact too):
1) sammobile.com --> http://www.sammobile.com/firmwares/3/?download=26590 - PDA - I337MVLUFNC1, CSC - I337MOYAFNC1, etc.
2) Downloaded and installed fresh 3.09 from sammobile per instructions.
3) Successfully flashed this firmware, phone returning back to normal as official kernel and official rom, knox warranty tripped still, but that's the way it goes.
SO: Moral of the story - ensure that not just using any kind of virtualization software to try and do flashing, use a proper PC. I hope somehow this finds its way to some other schlub that messes this up.
ROGERS is sending me a new phone anyway other problems involving sound and I was within 15 day return. Lucky me I guess...
I guess the next time around I'll need a closer look at avoiding knox tripping...
It works for me
2Tone5 said:
[/COLOR]Once you download it and its installed make sure to turn off your phone and boot into stock recovery and do a factory reset and if you really want to be clean flash the firmware again and all your problems should be gone
Sent from my SGH-I337M using Tapatalk
Click to expand...
Click to collapse
Thank you!! It works for me. It's very important to do a clean flash. :good:
I am having a crazy issue I can't seem to fix with my i337. I am trying to revert back to stock and I ran odin I get a pass notification but when I reboot my phone prompts that I have unauthorized software on my phone an to contact AT&T. I can't seem to make this work and I can't boot into recovery. Any ideas on what may help. Feeling pretty lost at this point.
Hey so one of my friends is having problems getting their S4 to boot. Currently she has K0T49H.L720VPUFNAE on her S4. She has no custom recovery, but did have the phone rooted. Now the device can't boot. It gets past the Samsung Galaxy S4 screen and then goes black, the blue notification light pulses, and the phone makes a beep (almost like the initial boot sound) and then just hangs there. I've tried to odin back to stock, but I receive "failed! (Auth) almost immediately after starting.
On the Samsung Galaxy S4 screen both "Kernel is not seandroid enforcing" & "Warranty bit: kernel" are displayed in the top corner.
I can boot into stock recovery & download mode.
Any help would be appreciated!
It sounds like you are trying to Odin an older version on there than NAE. You cant downgrade, only can flash the NAE tar or the newer NG2.
Download it here, and try flashing it instead. After you flash, if it still wont boot, boot into recovery mode and do a factory reset.
random45 said:
It sounds like you are trying to Odin an older version on there than NAE. You cant downgrade, only can flash the NAE tar or the newer NG2.
Download it here, and try flashing it instead. After you flash, if it still wont boot, boot into recovery mode and do a factory reset.
Click to expand...
Click to collapse
I am trying to flash NAE tar and have tried the NG2. Both result in the errors mentioned above.
I also have gone into stock recovery and performed a factory reset.
Joey43 said:
I am trying to flash NAE tar and have tried the NG2. Both result in the errors mentioned above.
I also have gone into stock recovery and performed a factory reset.
Click to expand...
Click to collapse
can you post the log from odin? Also what version of odin are you using? have you tried flashing Phil's Recovery and maybe just installing a ROM?
random45 said:
can you post the log from odin? Also what version of odin are you using? have you tried flashing Phil's Recovery and maybe just installing a ROM?
Click to expand...
Click to collapse
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUFNAE_L720SPTFNAE_L720VPUFNAE_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)
There's the log. I can't install a custom recovery either. It acts like it is installing correctly, but when it reboots it is still stock recovery.
Joey43 said:
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L720VPUFNAE_L720SPTFNAE_L720VPUFNAE_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)
There's the log. I can't install a custom recovery either. It acts like it is installing correctly, but when it reboots it is still stock recovery.
Click to expand...
Click to collapse
what version of odin are you using?
random45 said:
what version of odin are you using?
Click to expand...
Click to collapse
Oh, sorry. I've tried both 3.07 & 3.09
Joey43 said:
Oh, sorry. I've tried both 3.07 & 3.09
Click to expand...
Click to collapse
Okay, its really strange honestly. I spent sometime looking online for possible solutions, and the only thing I can come up with is:
1. make sure you are using the usb cable that came with the phone, and that it is undamaged
2. if its a desktop, make sure the usb cable is connected on the back. if you have usb 3.0 ports try it on there
3. some people say odin and kies dont get along. I do not share this experience, but who knows, doesnt hurt to try uninstalling kies, and install phone drivers
How did this happen by the way?
random45 said:
Okay, its really strange honestly. I spent sometime looking online for possible solutions, and the only thing I can come up with is:
1. make sure you are using the usb cable that came with the phone, and that it is undamaged
2. if its a desktop, make sure the usb cable is connected on the back. if you have usb 3.0 ports try it on there
3. some people say odin and kies dont get along. I do not share this experience, but who knows, doesnt hurt to try uninstalling kies, and install phone drivers
How did this happen by the way?
Click to expand...
Click to collapse
I'm using my S3 cable since her OEM one is broken. I tried around 4 different cables since I had the same thought. I never had kies installed and I did install the drivers.
I have really awful internet stability and speed (like 100kbs) so I'm hoping that the download is just corrupted and I'm just trying to re-download it.
I honestly don't know, she gave it to her brother to look at first, whom I suspect made the issue worse. I'm usually pretty good at fixing these things and I thought that it was an easy fix since it could reach download mode. I really appreciate all the help still.
have you tried flashing a pit file?
here is a 16 GB Sprint L720 NAE pit file you can try. do that with caution, and as a last resort.
Joey43 said:
I'm using my S3 cable since her OEM one is broken. I tried around 4 different cables since I had the same thought. I never had kies installed and I did install the drivers.
I have really awful internet stability and speed (like 100kbs) so I'm hoping that the download is just corrupted and I'm just trying to re-download it.
I honestly don't know, she gave it to her brother to look at first, whom I suspect made the issue worse. I'm usually pretty good at fixing these things and I thought that it was an easy fix since it could reach download mode. I really appreciate all the help still.
Click to expand...
Click to collapse
random45 said:
have you tried flashing a pit file?
here is a 16 GB Sprint L720 NAE pit file you can try. do that with caution, and as a last resort.
Click to expand...
Click to collapse
I tried that and received a "secure check fail: PIT" error. Phone performs the same as before.
i think the phone's busted....maybe try sending it to that one place that can jtag phones?
I think this is the site, but dont hold me to it.
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s4-jtag-brick-repair/
random45 said:
i think the phone's busted....maybe try sending it to that one place that can jtag phones?
I think this is the site, but dont hold me to it.
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s4-jtag-brick-repair/
Click to expand...
Click to collapse
I got philz custom recovery finally, and was able to flash NG2 pre-rooted, but the baseband version is old and wifi/data isn't working. I'm trying to flash the NG2 Modem.tar under the phone tab in odin, but i receive fail auth still and secure check fail: apnhlos.
I'm currently pursuing .tar to flashable .zip python converters, because it seems I cannot flash anything but one specific version of philz recovery in odin, but can flash anything through custom recovery.
Joey43 said:
I got philz custom recovery finally, and was able to flash NG2 pre-rooted, but the baseband version is old and wifi/data isn't working. I'm trying to flash the NG2 Modem.tar under the phone tab in odin, but i receive fail auth still and secure check fail: apnhlos.
I'm currently pursuing .tar to flashable .zip python converters, because it seems I cannot flash anything but one specific version of philz recovery in odin, but can flash anything through custom recovery.
Click to expand...
Click to collapse
Okay, so your making some progress.
random45 said:
Okay, so your making some progress.
Click to expand...
Click to collapse
where can i get that philz recovery im goin thru the same thang
I don't have this phone anymore. Good luck.
Sent from my SM-N910P using Tapatalk
To be honest TWRP is your better option for recovery on the S4 (I was a staunch supporter of Philz on my S3) one thing you need to make sure when you flash TWRP it to uncheck the auto reboot option. When flash completes, unplug and pull battery and then boot directly into recovery, then it sticks. You may be having WiFi/data issues because of your baseband/ROM combo. Have you tried flashing the latest stock?
Need Help Device stuck After flash?
I have the sprint sph l720t model. I finally acquired root access. I tried to flash Cyogenmod. When I did, it finished and rebooted and a after reboot it says cyogen mod in a circle that just keeps on spinning. I tried to get back to my blue team win screen into recovery but no luck. I got the phone to go into download mode once. I do have backups on my SD card with all the files can I flash a backup? What can I do?? The recovery says in red kernel is not se enforcing then under that in yellow set warranty bit: kernel? Can I use odin to do something in download mode to get my device back up?? I did refash my MD.5 file again from chainfire no luck! Help? Thanks
mattzeller said:
To be honest TWRP is your better option for recovery on the S4 (I was a staunch supporter of Philz on my S3) one thing you need to make sure when you flash TWRP it to uncheck the auto reboot option. When flash completes, unplug and pull battery and then boot directly into recovery, then it sticks. You may be having WiFi/data issues because of your baseband/ROM combo. Have you tried flashing the latest stock?
Click to expand...
Click to collapse
Yes I am now running Lollipop 5.0.1. I also did finally get TWRP installed. Everything is back to normaral. I re-installed the firmware from sam mobile. I then ofcoarse, went and flashed cf-autoroot with Odin. I pulled the batterry this time and booted up into recovery. Somehow everything is working and I do have recovery somewhere in my device. I want to try another Rom but Honestly TWRP makes me nervous evertime I open the app! What should I try next. Its just like factory rom with root but not really root. Its weird. At suggestios would be cool.. Thanks
EngineManShawn said:
Yes I am now running Lollipop 5.0.1. I also did finally get TWRP installed. Everything is back to normaral. I re-installed the firmware from sam mobile. I then ofcoarse, went and flashed cf-autoroot with Odin. I pulled the batterry this time and booted up into recovery. Somehow everything is working and I do have recovery somewhere in my device. I want to try another Rom but Honestly TWRP makes me nervous evertime I open the app! What should I try next. Its just like factory rom with root but not really root. Its weird. At suggestios would be cool.. Thanks
Click to expand...
Click to collapse
You have a lot of options now that you are presumably on the latest baseband. Just download the ROM you want, copy it to your external SD card and flash in TWRP.
If you like TouchWiz I suggest Wicked X:
http://forum.xda-developers.com/showthread.php?t=3115583
It's a fairly modified TW ROM, with quite a few mods that you can apply as you see fit. The developer is fantastic, quick to support and address issues. Every time he changes devices, I change to that device, he's that good. I've been stalking him since his time developing for the S2.
If TW isn't your thing, I suggest BlissPop:
http://forum.xda-developers.com/showthread.php?p=62018060
When I'm not running Wicked X I'm running BlissPop. The only caveat is I have not been able to get data to work properly on the latest builds, but the experimental build from 9/28 that I run is flawless. If you can't find it on their page, let me know I have it up on Mega.
Neither one is better than the other, it just a matter of preference. They both have great battery life, especially when paired with Greenify.
My GS5 G900V is stuck to recovery mode while I was trying to root. My mistake was I used odin to flash it back to a older version to try to root it and I did not did my research I know im a dummy. Now its Soft brick. I looked around and looked around to find answers but nothing seems to work for me. Ive tried using odin again to flash it back to the current firmware but Odin does not work.
It will be stuck on the Samsung GS5 screen and will go straight to recovery mode. Ive tried wiping cache and restore to factory settings still did not work. Tried taking out the battery for some time still did not work. I tried flashing through sd card still did not work.
This is the current log I have. Been trying different things since last night. Nothing works.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Found this link here but not sure how to use it: http://forum.xda-developers.com/showthread.php?t=2446269
I saw one thread with my similar problems. I think this is how they fixed it but I do not know how to do it. Can someone tell me how to use it? It will be greatly appreciated.
Thanks for all the help!
j0mz said:
My GS5 G900V is stuck to recovery mode while I was trying to root. My mistake was I used odin to flash it back to a older version to try to root it and I did not did my research I know im a dummy. Now its Soft brick. I looked around and looked around to find answers but nothing seems to work for me. Ive tried using odin again to flash it back to the current firmware but Odin does not work.
It will be stuck on the Samsung GS5 screen and will go straight to recovery mode. Ive tried wiping cache and restore to factory settings still did not work. Tried taking out the battery for some time still did not work. I tried flashing through sd card still did not work.
This is the current log I have. Been trying different things since last night. Nothing works.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Found this link here but not sure how to use it: http://forum.xda-developers.com/showthread.php?t=2446269
I saw one thread with my similar problems. I think this is how they fixed it but I do not know how to do it. Can someone tell me how to use it? It will be greatly appreciated.
Thanks for all the help!
Click to expand...
Click to collapse
What version (3 letter) are/were you on?
How I unbricked my phone was to do #4 in Notes in the first post: http://forum.xda-developers.com/ver...w-to-update-to-g900voe1-5-0-keeproot-t3149784
BEWARE the warnings...you might be up the creek if you are on OE1 firmware
simplepinoi177 said:
What version (3 letter) are/were you on?
How I unbricked my phone was to do #4 in Notes in the first post: http://forum.xda-developers.com/ver...w-to-update-to-g900voe1-5-0-keeproot-t3149784
BEWARE the warnings...you might be up the creek if you are on OE1 firmware
Click to expand...
Click to collapse
I believe mine was on OD5
I cant use flashfire because my phone is stuck on recovery mode. I cant get pass that.
j0mz said:
I believe mine was on OD5
I cant use flashfire because my phone is stuck on recovery mode. I cant get pass that.
Click to expand...
Click to collapse
you don't use flashfire...
I'm not saying to do the whole thing on the first post...just NUMBER #4 IN THE NOTES...
You use Odin and the file given to unbrick your phone back to NCG...
again, just go to NOTES and do #4 to unbrick the phone. You should be safe/fine if you are on OD5. Don't forget to root again and install a superuser...
Then you can go here to install whatever version you are interested in... http://forum.xda-developers.com/showthread.php?t=2784880
simplepinoi177 said:
you don't use flashfire...
I'm not saying to do the whole thing on the first post...just NUMBER #4 IN THE NOTES...
You use Odin and the file given to unbrick your phone back to NCG...
again, just go to NOTES and do #4 to unbrick the phone. You should be safe/fine if you are on OD5. Don't forget to root again and install a superuser...
Then you can go here to install whatever version you are interested in... http://forum.xda-developers.com/showthread.php?t=2784880
Click to expand...
Click to collapse
I tried it but Odin cant find it. Its a rar file?
Stuck in recovery mode loop. SM-G900V Verizon G900VVRU2BOG5
Im in the exact same situation... i have been literally sitting in front of my PC for hours on end to try and resolve this issue. I cant get back my current firmware now even. Just stuck on the recovery mode. I flashed NCG kernal and it went through as normal, however, all it does not is after the samsung loading sign it goes back into system recovery. I have tried everything from cache wipe to factory reset, system reboot, everything! it just does the same thing - goes back into recovery mode- it is getting really frustrating for me. I would really appreciate it if someone could tell me exactly how to get out of it and use the phone as normal again.
I am on sm-g900v
G900VVRU2BOG5
Verizon mobile S5
I have tried to flash almost all the available ROMS and nothing works everytime this come up: ( i am using the latest Kies drivers, Odin 3.10.6, etc)..
<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/007> Added!!
<ID:0/007> Odin engine v(ID:3.1005)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping.. - - i have the pit file and if i use it to flash i get the same output failed completion.
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
PLEASE HELP. THANK YOU.
Tried rooting my SM-G900V. I managed to flash a kernel on it, but kept getting "FAIL!" in Odin when I tried flashing a custom rom. Even after I flashed a kernel on my phone still worked fine. One day it said some nonsense about securtiy updates, I clicked on it and BOOM. Stock OS, GONE. Kernel, GONE. It started giving me a message "use Verizon recovery assistant" I tried getting the program, no dice. I don't have root and I'm on the latest version of lolipop that they have released for the SM-G900V.
CAN ANYONE HELP, PLEASE. IF MY MOM KNEW I WAS MESSING WITH MY PHONE SHE'D KILL ME. SHE THINKS I'VE BEEN CHARGING IT FOR 3 DAYS!!!
m0bk3yn1nj4 said:
Tried rooting my SM-G900V. I managed to flash a kernel on it, but kept getting "FAIL!" in Odin when I tried flashing a custom rom. Even after I flashed a kernel on my phone still worked fine. One day it said some nonsense about securtiy updates, I clicked on it and BOOM. Stock OS, GONE. Kernel, GONE. It started giving me a message "use Verizon recovery assistant" I tried getting the program, no dice. I don't have root and I'm on the latest version of lolipop that they have released for the SM-G900V.
CAN ANYONE HELP, PLEASE. IF MY MOM KNEW I WAS MESSING WITH MY PHONE SHE'D KILL ME. SHE THINKS I'VE BEEN CHARGING IT FOR 3 DAYS!!!
Click to expand...
Click to collapse
can you boot into download mode? if go here http://forum.xda-developers.com/ver...w-to-update-to-g900voe1-5-0-keeproot-t3149784 and flash the full NCG tar then re root your device remember you always wanna flash ni2 kernal or nk2 then flash the rom then the kernal that works with your rom never flash the kernel that works with your rom before you flash the rom
m0bk3yn1nj4 said:
Tried rooting my SM-G900V. I managed to flash a kernel on it, but kept getting "FAIL!" in Odin when I tried flashing a custom rom. Even after I flashed a kernel on my phone still worked fine. One day it said some nonsense about securtiy updates, I clicked on it and BOOM. Stock OS, GONE. Kernel, GONE. It started giving me a message "use Verizon recovery assistant" I tried getting the program, no dice. I don't have root and I'm on the latest version of lolipop that they have released for the SM-G900V.
CAN ANYONE HELP, PLEASE. IF MY MOM KNEW I WAS MESSING WITH MY PHONE SHE'D KILL ME. SHE THINKS I'VE BEEN CHARGING IT FOR 3 DAYS!!!
Click to expand...
Click to collapse
If you were on the latest version of Lollipop and were not yet rooted, you cannot root your phone, flash custom ROMs, and I don't think you can flash kernels. You need to get your hands on a full ODIN stock tar file for the build your phone was on. OG5 is available, but I don't think the OK3 file is available yet. If you took an update in the past 2 or 3 days prior to trying this, you are stuck for a while with no way out. If you did not take an update on your phone in the past 2 or 3 days, look for the OG5 full stock ODIN file to flash to your phone.
---------- Post added at 05:36 PM ---------- Previous post was at 05:34 PM ----------
Veid71 said:
can you boot into download mode? if go here http://forum.xda-developers.com/ver...w-to-update-to-g900voe1-5-0-keeproot-t3149784 and flash the full NCG tar then re root your device remember you always wanna flash ni2 kernal or nk2 then flash the rom then the kernal that works with your rom never flash the kernel that works with your rom before you flash the rom
Click to expand...
Click to collapse
He said he was on the latest Lollipop version when he tried to root. If so, he cannot flash the NCG file. He wasn't already rooted, he was trying to root on the latest Lollipop build which can't be done at this time.
landshark68 said:
If you were on the latest version of Lollipop and were not yet rooted, you cannot root your phone, flash custom ROMs, and I don't think you can flash kernels. You need to get your hands on a full ODIN stock tar file for the build your phone was on. OG5 is available, but I don't think the OK3 file is available yet. If you took an update in the past 2 or 3 days prior to trying this, you are stuck for a while with no way out. If you did not take an update on your phone in the past 2 or 3 days, look for the OG5 full stock ODIN file to flash to your phone.
---------- Post added at 05:36 PM ---------- Previous post was at 05:34 PM ----------
He said he was on the latest Lollipop version when he tried to root. If so, he cannot flash the NCG file. He wasn't already rooted, he was trying to root on the latest Lollipop build which can't be done at this time.
Click to expand...
Click to collapse
ah okay i see then his post was kinda confusing
I don't know how to do that ODIN stuff, is there a video guide out or something?
landshark68 said:
If you were on the latest version of Lollipop and were not yet rooted, you cannot root your phone, flash custom ROMs, and I don't think you can flash kernels. You need to get your hands on a full ODIN stock tar file for the build your phone was on. OG5 is available, but I don't think the OK3 file is available yet. If you took an update in the past 2 or 3 days prior to trying this, you are stuck for a while with no way out. If you did not take an update on your phone in the past 2 or 3 days, look for the OG5 full stock ODIN file to flash to your phone.
Click to expand...
Click to collapse
I have no idea what any of this means. Please, can you help me?!
m0bk3yn1nj4 said:
I don't know how to do that ODIN stuff, is there a video guide out or something?
Click to expand...
Click to collapse
m0bk3yn1nj4 said:
I have no idea what any of this means. Please, can you help me?!
Click to expand...
Click to collapse
No offense intended, but if you don't know how to use ODIN and you don't have any idea what any of what I wrote means, you shouldn't be trying to root your phone without understanding all of it. I'm not aware of a video guide for using ODIN but I'd be willing to bet you could probably find one on youtube. If you can't find a video guide, found in post #4 of this thread is an old picture guide that should give you a pretty good understanding of using ODIN:
http://forum.androidcentral.com/ver...=1.251820425.1215152510.1443888191#post542513
I believe the PDA button is now called the AP button. Follow the video guide you found or the attached picture guide and flash the full BOG5 ODIN tar file found in this thread:
http://forum.xda-developers.com/verizon-galaxy-s5/general/g900vvru2bog5-factoryodintarimage-t3179527
There may even be a guide for using ODIN found here at XDA if you dig around some. Not sure.
landshark68 said:
No offense intended, but if you don't know how to use ODIN and you don't have any idea what any of what I wrote means, you shouldn't be trying to root your phone without understanding all of it. I'm not aware of a video guide for using ODIN but I'd be willing to bet you could probably find one on youtube. If you can't find a video guide, found in post #4 of this thread is an old picture guide that should give you a pretty good understanding of using ODIN:
http://forum.androidcentral.com/ver...=1.251820425.1215152510.1443888191#post542513
I believe the PDA button is now called the AP button. Follow the video guide you found or the attached picture guide and flash the full BOG5 ODIN tar file found in this thread:
http://forum.xda-developers.com/verizon-galaxy-s5/general/g900vvru2bog5-factoryodintarimage-t3179527
There may even be a guide for using ODIN found here at XDA if you dig around some. Not sure.
Click to expand...
Click to collapse
Much obliged
simplepinoi177 said:
What version (3 letter) are/were you on?
How I unbricked my phone was to do #4 in Notes in the first post: http://forum.xda-developers.com/ver...w-to-update-to-g900voe1-5-0-keeproot-t3149784
BEWARE the warnings...you might be up the creek if you are on OE1 firmware
Click to expand...
Click to collapse
i have a sm-g900v BOG5. i bricked mine phone so i tried #4 as you said and get FAIL! in Odin. am i doing something wrong?
rachelrgr said:
i have a sm-g900v BOG5. i bricked mine phone so i tried #4 as you said and get FAIL! in Odin. am i doing something wrong?
Click to expand...
Click to collapse
You can grab the stock firmware, either OG5. OK3, or PB1 (newest), and flash with odin in the AP slot, I also recommend grabbing the PIT file (goes in the PIT slot). If you want root, then just go ahead and grab the PB1 and follow the directions on this link.
Firmware Link: http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370