I'm running an AT&T Samsung Galaxy S4 (SGH-I337) 4.3 with MK2. I got it soft bricked because I was trying to install cwm or twrp a couple months ago, and was able to recover using the Down Volume Key method. This was fine until I tried to update to 4.4.2 and since my recovery menu is gone, I can't update. It says that It can't boot normally when it restarts. Is there a way to update or will I have to get it "unbricked" somewhere else? If so, where?
You'll have to flash the mk2 tar files in odin. See this for the files, read the whole thread @Rehdnehck
Edit, sorry wrong link use this
http://forum.xda-developers.com/showthread.php?p=49687770
Sent from my Nexus 5
Does it boot to Android. If so use a Terminal Emulator and "dd" the MK2 stock recovery.img
found in general section
Got it to restore with first guide, will try second guide to get the recovery mode back.
Rehdnehck said:
I'm running an AT&T Samsung Galaxy S4 (SGH-I337) 4.3 with MK2. I got it soft bricked because I was trying to install cwm or twrp a couple months ago, and was able to recover using the Down Volume Key method. This was fine until I tried to update to 4.4.2 and since my recovery menu is gone, I can't update. It says that It can't boot normally when it restarts. Is there a way to update or will I have to get it "unbricked" somewhere else? If so, where?
Click to expand...
Click to collapse
put it into odin mode and flash mk2 ap, cp. and csc (don't know if you need all three but they worked for me). don't flash the bl because it will fail if you have updated to 4.4.2. then side load the update zip. that should get you up and running again. or you can try this
http://forum.xda-developers.com/showthread.php?t=2663545 hope this helps
Related
I just followed this thread and successfully rooted my S4
http://forum.xda-developers.com/showthread.php?t=2387577
I think i deleted some core apps thru titanium backup and the phone could not display normally (keep Blinking)
then I tried to downloaded Goo Manager and installed TWRP Recovery on my S4. when I restart my phone can only boot to ODIN mode. I fixed this by using
http://forum.xda-developers.com/showthread.php?t=2360859
Now the phone can boot up but stuck at ATT logo Screen. Any body can help me?
PS. I try KIES emergency recovery and it keep telling me there is a error of updating.
I bricked my s4 (i337 Canadian, bell) the day I bought it, TWRP 2.6.0.0 was what bricked my phone (I think, or improper use of TWRP) and it wouldn't boot whatsoever (even my recovery was bricked), I managed to fix it by flashing stock firmware from ODIN 1.85 on PC to the phone (couldn't access recovery, so I flashed from PC) , make sure you download a stock firmware that is .tar to use with the PC version of ODIN, the second thing I had to do was flash CF Auto Root again using ODIN 1.85 from PC to phone, since I still couldn't boot my phone or recovery (other root flashing methods wouldn't unbrick my phone, but CF Auto Root did, download the MF3 version of CF auto root).
after all this crap I installed TWRP 2.5.0.0 as my recovery and haven't had any issues since :victory:
this was done on a I337MVLUAMG1 which I believe is the bell equivalent of the MF3 (update that blocked rooting by most methods like motochopper ect)
Thanks
Amb669 said:
I bricked my s4 (i337 Canadian, bell) the day I bought it, TWRP 2.6.0.0 was what bricked my phone (I think, or improper use of TWRP) and it wouldn't boot whatsoever (even my recovery was bricked), I managed to fix it by flashing stock firmware from ODIN 1.85 on PC to the phone (couldn't access recovery, so I flashed from PC) , make sure you download a stock firmware that is .tar to use with the PC version of ODIN, the second thing I had to do was flash CF Auto Root again (other root flashing methods wouldn't unbrick my phone, but CF Auto Root did, download the MF3 version of CF auto root).
after all this crap I installed TWRP 2.5.0.0 as my recovery and haven't had any issues since :victory:
this was done on a I337MVLUAMG1 which I believe is the bell equivalent of the MF3 (update that blocked rooting by most methods like motochopper ect)
Click to expand...
Click to collapse
Thanks for your reply.
I have the same problem as this guy
http://forum.xda-developers.com/showthread.php?t=2407950
Any Idea how to fix it?
jerryhuanginusa said:
I just followed this thread and successfully rooted my S4
http://forum.xda-developers.com/showthread.php?t=2387577
I think i deleted some core apps thru titanium backup and the phone could not display normally (keep Blinking)
then I tried to downloaded Goo Manager and installed TWRP Recovery on my S4. when I restart my phone can only boot to ODIN mode. I fixed this by using
http://forum.xda-developers.com/showthread.php?t=2360859
Now the phone can boot up but stuck at ATT logo Screen. Any body can help me?
PS. I try KIES emergency recovery and it keep telling me there is a error of updating.
Click to expand...
Click to collapse
Dont thinknthere is antthing you can do. We have no return to stock method at this point in time. This is why it is important to follow forum rules and read and search before doing something youll regret, im nkt saying this to be mean...but there has been at least 5 people these past few days who have done the exact same thing as you and have gone in here looking for help...
My best advice, throw in some money for the bootloader unlock bounty and hope somethung happens soomer than later
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
jerryhuanginusa said:
I just followed this thread and successfully rooted my S4
http://forum.xda-developers.com/showthread.php?t=2387577
I think i deleted some core apps thru titanium backup and the phone could not display normally (keep Blinking)
then I tried to downloaded Goo Manager and installed TWRP Recovery on my S4. when I restart my phone can only boot to ODIN mode. I fixed this by using
http://forum.xda-developers.com/showthread.php?t=2360859
Now the phone can boot up but stuck at ATT logo Screen. Any body can help me?
PS. I try KIES emergency recovery and it keep telling me there is a error of updating.
Click to expand...
Click to collapse
If you read through the threads it specifically stated that the MF3 boot loader is locked and you cannot install twrp or custom ROMS on it. I have seen so many posts regarding this it makes me sick. It's kies seeing the device? But is falling to recover? Or is it not seeing it?
Tylor
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
http://forum.xda-developers.com/showpost.php?p=44570305&postcount=366
Fail to recover
Tylorw1 said:
If you read through the threads it specifically stated that the MF3 boot loader is locked and you cannot install twrp or custom ROMS on it. I have seen so many posts regarding this it makes me sick. It's kies seeing the device? But is falling to recover? Or is it not seeing it?
Tylor
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
the Kies can detect the phone buy it fail to recover it. the progress bar runs a little and stopped. error message pop out on PC screen says "Emergency recovery failed, Please contact Samsung Customer Service"
Hi there. I think I soft-bricked my phone. I am running mf3 firmware on my i337 galaxy s4 and i tried to flash Graviton. I was using safestrap and I, like an idiot, didn't use a romslot and did it over my stock. Seemed to work fine until I actually booted the phone. It can't access wifi and therefore wont go past the find wifi screen. I try to enter recovery but it just keeps going to the download screen. After trying every way I could find I still cant either wipe my phone or flash the stock firmware. I have tried kies and odin but nothing works. Can anyone help me out or am I royally screwed?
LCubed22 said:
Hi there. I think I soft-bricked my phone. I am running mf3 firmware on my i337 galaxy s4 and i tried to flash Graviton. I was using safestrap and I, like an idiot, didn't use a romslot and did it over my stock. Seemed to work fine until I actually booted the phone. It can't access wifi and therefore wont go past the find wifi screen. I try to enter recovery but it just keeps going to the download screen. After trying every way I could find I still cant either wipe my phone or flash the stock firmware. I have tried kies and odin but nothing works. Can anyone help me out or am I royally screwed?
Click to expand...
Click to collapse
as long as the phone can go into download mode, you can use odin to reflash the stock firmware (and factory recovery). Check samsungupdates for your model/region and stock/official firmware. You'd have to re-root after. I did the same thing a while back, lost my recovery and this is the method I used to bring my phone back to life, was just sitting at the samsung logo and had no recovery (but had download mode).
LCubed22 said:
Hi there. I think I soft-bricked my phone. I am running mf3 firmware on my i337 galaxy s4 and i tried to flash Graviton. I was using safestrap and I, like an idiot, didn't use a romslot and did it over my stock. Seemed to work fine until I actually booted the phone. It can't access wifi and therefore wont go past the find wifi screen. I try to enter recovery but it just keeps going to the download screen. After trying every way I could find I still cant either wipe my phone or flash the stock firmware. I have tried kies and odin but nothing works. Can anyone help me out or am I royally screwed?
Click to expand...
Click to collapse
Does Odin recognize the phone? Also, when you say it won't go past the "find wifi" screen, does that mean it booted to the "Welcome" screen?
nerdyblonde said:
Does Odin recognize the phone? Also, when you say it won't go past the "find wifi" screen, does that mean it booted to the "Welcome" screen?
Click to expand...
Click to collapse
Sorry should have edited the first post. I actually fixed my original problem and am now having a different one. I got all the way through nd did a restore of my stock rom. I then tried to flash the graviton one to a different rom-slot in safestrap. So now there is a completely different partition in the storage and the flash didnt work so I'm now completely stuck in download mode. I have tried to flash the tar files in odin and it fails every time. I should have all of the necessary files for mf3.
LCubed22 said:
Sorry should have edited the first post. I actually fixed my original problem and am now having a different one. I got all the way through nd did a restore of my stock rom. I then tried to flash the graviton one to a different rom-slot in safestrap. So now there is a completely different partition in the storage and the flash didnt work so I'm now completely stuck in download mode. I have tried to flash the tar files in odin and it fails every time. I should have all of the necessary files for mf3.
Click to expand...
Click to collapse
If you have the 16GB Galaxy, try flashing this file in the PIT slot in Odin.. Don't put any other files in the PDA slot, etc. It's worked many times when phone would only boot to download..
https://www.dropbox.com/s/fptxnxsqevjhnt9/SGS-I337_16GB.pit
Hey Nerdyblonde, what does this pit file do?
I softbricked my phone when trying to flip from CWM to TWRP. (Thought I could just wipe phone and odin flash on top of CWM... VERY WRONG). Now I can't get into recovery and my phone is telling me to use kies recovery *shudder*. So I tried kies when I couldn't Odin flash to stock rom and still nothing.
nerdyblonde said:
If you have the 16GB Galaxy, try flashing this file in the PIT slot in Odin.. Don't put any other files in the PDA slot, etc. It's worked many times when phone would only boot to download..
https://www.dropbox.com/s/fptxnxsqevjhnt9/SGS-I337_16GB.pit
Click to expand...
Click to collapse
snoops609 said:
Hey Nerdyblonde, what does this pit file do?
I softbricked my phone when trying to flip from CWM to TWRP. (Thought I could just wipe phone and odin flash on top of CWM... VERY WRONG). Now I can't get into recovery and my phone is telling me to use kies recovery *shudder*. So I tried kies when I couldn't Odin flash to stock rom and still nothing.
Click to expand...
Click to collapse
Sorry it took a few days to answer.. The Kies screen was the same thing that happened to me... I have the MF3 version, so I can't install custom recovery, but I couldn't boot into recovery period. I flashed that pit file in the pit box on Odin, it restored my recovery.
Do you have MDL or MF3? If you have MDL, I would be really careful not to flash MF3 unless you want to stick with basically stock until one of the geniuses here figures out how to unlock the bootloader.
So I've been running a rooted Note 3 for a while. When the Note 3 Kitkat update came out, I updated it via Odin as OTA update was not available since I was rooted.
All the posts I read had mentioned that updating to 4.4.2 from 4.3 would erase all my data but after updating via odin all my data was in place. I had only lost root which I rooted again though CF Auto Root.
The problem now is that when I try to install CWM (via Odin) or TWRP (via Goo or Odin), it goes through the installation but then the phone goes into a boot loop of sorts..It's NOT the normal boot loop which gets stuck on the Samsung logo.
What happens is that the phone vibrates twice (with a 1 sec interval in between), then the Samsung Note 3 N-9005 screen appears with "Booting Recovery..." on the top left and within a sec it goes blank and then back to 2 vibrates and the screen come on to show Samsung Note 3 N-9005.
The only way I found to fix this was a battery pull and then turning on the device holding the power, home and down vol key to boot into recovery and then flashing CF Auto Root again.
I don't know why am I not able to install any of these recoveries. I've made sure I try to install the latest versions of them which are Kitkat compatible.
Anyone else with this problem or a solution?
Can a Cache and data wipe fix this? But the problem again being I won't be able to backup my ROM since i can't get these recoveries to install!
There is a script in official firmware that checks for official recovery and if it finds a custom one it tries to overwrite with official one. If i remember correct it's called install-recovery. sh
PhilZ recovery handles it automatically.
It's impossibe to flash anything other than the leaked 4.4.2 stock because you flashed your bootloader to kitkat, no you MUST stay on sammy 4.4.2 till the devs found a solution for this. Thats why you have to read carefully be4 you flash.
silentvisitor said:
There is a script in official firmware that checks for official recovery and if it finds a custom one it tries to overwrite with official one. If i remember correct it's called install-recovery. sh
PhilZ recovery handles it automatically.
Click to expand...
Click to collapse
No luck!
I tried PhilZ recovery from the below link.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/hltexx
What are my other options?
sid8907 said:
No luck!
I tried PhilZ recovery from the below link.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/hltexx
What are my other options?
Click to expand...
Click to collapse
This one seems to be the only one working with 4.4.2 right now.
Possible solution
The way I can suggest is to create a little update.zip file with little updater-script to remove install-recovery.sh file from device (just one line needed).
Ok, I found a zip which I am attaching below. You(or anyone) may review the script before flashing.
Place this on your external (or internal) sdcard.
In ODIN don't check Auto reboot
Flash Recovery. Remove phone when it says PASS.
Remove battery. Start in Recovery mode by pressing buttons.
You should now be in new Recovery.
Flash that zip file.
Reboot.
You should be good.
The Auto Reboot for some reason is faded out. Tried different versions of Odin and also tried to open it with the phone connected/disconnected.
I am out of ideas.
I would suggest you to wait for someone to come up with working solution. Being too adventurous with ODIN could brick your device.
sid8907 said:
The Auto Reboot for some reason is faded out. Tried different versions of Odin and also tried to open it with the phone connected/disconnected.
Click to expand...
Click to collapse
Clear out all your ODIN caches etc, delete all files and keep 1.85.
Flash this (only working recovery on 4.4.2) via PDA in ODIN, If it doesn't reboot auto after saying PASS or RESET.. just turn phone off, reboot into recovery and it'll be fine.
EDIT: Just re-read, Re flash your Stock 4.4.2 (Use XEO not the leaked one!) and then start again
Thanks!
Maybe a little off topic, but is there a way to install CM11 on Stock 4.4.2 on the Note 3?
I've been reading Samsung is out with a new bootloader so there is no way round this?
radicalisto said:
Clear out all your ODIN caches etc, delete all files and keep 1.85.
Flash this (only working recovery on 4.4.2) via PDA in ODIN, If it doesn't reboot auto after saying PASS or RESET.. just turn phone off, reboot into recovery and it'll be fine.
EDIT: Just re-read, Re flash your Stock 4.4.2 (Use XEO not the leaked one!) and then start again
Click to expand...
Click to collapse
Thanks!!
sid8907 said:
Thanks!
Maybe a little off topic, but is there a way to install CM11 on Stock 4.4.2 on the Note 3?
I've been reading Samsung is out with a new bootloader so there is no way round this?
Click to expand...
Click to collapse
You may have to do a little reading but I believe CM11 is now working on the KK bootloader...
sid8907 said:
So I've been running a rooted Note 3 for a while. When the Note 3 Kitkat update came out, I updated it via Odin as OTA update was not available since I was rooted.
All the posts I read had mentioned that updating to 4.4.2 from 4.3 would erase all my data but after updating via odin all my data was in place. I had only lost root which I rooted again though CF Auto Root.
The problem now is that when I try to install CWM (via Odin) or TWRP (via Goo or Odin), it goes through the installation but then the phone goes into a boot loop of sorts..It's NOT the normal boot loop which gets stuck on the Samsung logo.
What happens is that the phone vibrates twice (with a 1 sec interval in between), then the Samsung Note 3 N-9005 screen appears with "Booting Recovery..." on the top left and within a sec it goes blank and then back to 2 vibrates and the screen come on to show Samsung Note 3 N-9005.
The only way I found to fix this was a battery pull and then turning on the device holding the power, home and down vol key to boot into recovery and then flashing CF Auto Root again.
I don't know why am I not able to install any of these recoveries. I've made sure I try to install the latest versions of them which are Kitkat compatible.
Anyone else with this problem or a solution?
Can a Cache and data wipe fix this? But the problem again being I won't be able to backup my ROM since i can't get these recoveries to install!
Click to expand...
Click to collapse
here's the link for twrp for ya'll http://forum.xda-developers.com/showpost.php?p=50333147&postcount=398
sid8907 said:
So I've been running a rooted Note 3 for a while. When the Note 3 Kitkat update came out, I updated it via Odin as OTA update was not available since I was rooted.
All the posts I read had mentioned that updating to 4.4.2 from 4.3 would erase all my data but after updating via odin all my data was in place. I had only lost root which I rooted again though CF Auto Root.
The problem now is that when I try to install CWM (via Odin) or TWRP (via Goo or Odin), it goes through the installation but then the phone goes into a boot loop of sorts..It's NOT the normal boot loop which gets stuck on the Samsung logo.
What happens is that the phone vibrates twice (with a 1 sec interval in between), then the Samsung Note 3 N-9005 screen appears with "Booting Recovery..." on the top left and within a sec it goes blank and then back to 2 vibrates and the screen come on to show Samsung Note 3 N-9005.
The only way I found to fix this was a battery pull and then turning on the device holding the power, home and down vol key to boot into recovery and then flashing CF Auto Root again.
I don't know why am I not able to install any of these recoveries. I've made sure I try to install the latest versions of them which are Kitkat compatible.
Anyone else with this problem or a solution?
Can a Cache and data wipe fix this? But the problem again being I won't be able to backup my ROM since i can't get these recoveries to install!
Click to expand...
Click to collapse
jp.26 said:
here's the link for twrp for ya'll http://forum.xda-developers.com/showpost.php?p=50333147&postcount=398
Click to expand...
Click to collapse
so.... yeah i just updated my bootloader to 4.4.2 and this drove me literally insane. ive been working on it for 4 hours now. i encountered so many problems with installing the bootloader. exact same problem as SID8907. i gotta tell you tho.... you worked some magic my friend. i tried almost everything. then i came across your link. i was like why not? so i flashed the img in odin..... anddddd :drumroll pleaseeeeee:: IT WORKED. ahhh....... so much frustration and the problem is solved!!! thank you so much JP.26 :good::laugh:
is there any word on how to fix this been looking for hours tmobile note beast dont want to put any roots down on my phone before i find a way to flash cm or a non bloated note rom would be nice.
I'll that I've managed is to root and flash twrp I found a way to turn cwm recovery into a tar file and flash through odin. But i just get into a boot loop with cwm due to the boot loader I presume but tarp works fine I just can't flash cm11. I get boot loop every time
Sent from my SM-N900T using XDA Premium 4 mobile app
im sorry but im confused here... does this all simply mean that there is not yet a working cwm for 4.4.2 yet? and that while we can root, there is no working recovery for this version?
I'm not sure myself tarp works but I can't flash cm11
Sent from my SM-N900T using Tapatalk
Phillz cwm Dev edition I think that's the name works its a themed touch cwm. This works great but still can't flash cm so gayyyy
Sent from my SM-N900T using Tapatalk
I was wondering what happened to the cmw too.
The modded cmw by Chenglu is the only one working that I know of.
Link to thread: http://forum.xda-developers.com/showthread.php?t=2454079
Okay so I've searched the forums and haven't found the answer to what I'm looking for quite yet. I'm not new to rooting, but new to the Galaxy Note 3. I just recently started getting prompted for the update to KK4.4.2 (I have the Verizon model and we all know how long they take to push out updates.) So I decided to flash the leaked de-oxed NC2 rom and after follow the instructions from here. I reboot and get stuck at a black screen. It boots no further and I have to pull the battery to get back to recovery.
Am I missing something, another step maybe? Is this an old process?
Any help would be appreciated. Thanks
Did you also flash the firmware package in odin?
<Note3>
LeftyGR said:
Did you also flash the firmware package in odin?
<Note3>
Click to expand...
Click to collapse
Yes I also flashed the firmware through Odin. Does it matter which version of Odin I used?
Odin doesn't matter.
Root 4.3
Install safe strap.
Now you can update to the rooted 4.4 through odin.
barrackOBAMA said:
Odin doesn't matter.
Root 4.3
Install safe strap.
Now you can update to the rooted 4.4 through odin.
Click to expand...
Click to collapse
Actually it looks as if this was caused by Odin 3.09. It doesn't seem to like the bootloader file for NC2 and for some reason doesn't load the entire boot portion of the file. Flashed with Odin 3.07 and booted no problem. Thanks for the input though.
Ok so I updated to the 5.0.1 update on my S4 yesterday and kept my root using that method with the chainfire app. Today I wanted to try flashing CWM on my S4. Upon trying on Odin 3.09, it said failed and now my S4 boots into Odin Mode and says "Firmware upgrade encountrered an issue. Please select recovery mode in Kies & Ttry again."
WHAT THE HELL DID I JUST DO?
EDIT:
Fixed it, http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642
CrossBones3129 said:
Ok so I updated to the 5.0.1 update on my S4 yesterday and kept my root using that method with the chainfire app. Today I wanted to try flashing CWM on my S4. Upon trying on Odin 3.09, it said failed and now my S4 boots into Odin Mode and says "Firmware upgrade encountrered an issue. Please select recovery mode in Kies & Ttry again."
WHAT THE HELL DID I JUST DO?
EDIT:
Fixed it, http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642
Click to expand...
Click to collapse
From the sounds of it you need to stick with safestrap only mdl and under can use a custom recovery on ATT
Glad you got it fixed.
BehrendsTech said:
From the sounds of it you need to stick with safestrap only mdl and under can use a custom recovery on ATT
Glad you got it fixed.
Click to expand...
Click to collapse
Thanks for the info. I was able to do every step and am back on 5.0.1 and rooted. My issue now is that I can't boot into recovery mode. Can you help me?
CrossBones3129 said:
Thanks for the info. I was able to do every step and am back on 5.0.1 and rooted. My issue now is that I can't boot into recovery mode. Can you help me?
Click to expand...
Click to collapse
Safestrap doesn't allow recovery boot for lollipop. This is because safestrap hasn't been updated for lollipop yet. Everyone's moving to lollipop someone will update it or come up with a alternative soon I'm sure.
CrossBones3129 said:
Thanks for the info. I was able to do every step and am back on 5.0.1 and rooted. My issue now is that I can't boot into recovery mode. Can you help me?
Click to expand...
Click to collapse
If you want to fix the stock recovery. find the OC3 Stock Partitions file and ODIN it to your phone. If you find the one that's a zip file, you'll have to ODIN a kitkat kernel to flash that in Safestrap.
DeadlySin9 said:
If you want to fix the stock recovery. find the OC3 Stock Partitions file and ODIN it to your phone. If you find the one that's a zip file, you'll have to ODIN a kitkat kernel to flash that in Safestrap.
Click to expand...
Click to collapse
I don't understand. I've never used safestrap. I was able to flash back using odin to the nc4. Than flashed to NJ1, rooted that, then upgraded to 5.0.1 while keeping root using that flashfire method.
Now if I use flashfire, do a cache wipe that way I can access flashfire's reboot options, select boot to recovery, it will boot to recovery fine. I just can't get it to boot recovery using the volume up, power, and home buttons. It says recovery boot in blue at the top but then restarts and boots normally