So I recently got a Galaxy S4 last night, I rooted it with Kingoroot and it worked great. I then went to sleep and left it alone to wake up to it trying to install a AT&T update and then turning off and booting to a screen that says "Samsung Custom" and does the same processs again.
I have spent more than 2 hours trying to fix this with no avail.
I tried to install stock 4.2.2 but I receive as Fail in Odin which I learned is because you can't install older Android OSes.I then tried to install stock recovery because when I try to boot to recovery it tries to install the update again.
No luck.
I heard of something called a MF3 and downloaded the files but not sure how to use them...
I can still get into Download Mode
This is my main phone so I really need help.
I've read people got soft brick while updating their phones rooted with kingroot!
Try flashing the stock kernel
Google everything before you make sensitive changes in your phone!
Although rooting isnt that sensitive these days!
Sent from my MT27i using XDA Free mobile app
Piyush jaiswal said:
I've read people got soft brick while updating their phones rooted with kingroot!
Try flashing the stock kernel
Google everything before you make sensitive changes in your phone!
Although rooting isnt that sensitive these days!
Sent from my MT27i using XDA Free mobile app
Click to expand...
Click to collapse
After playing around with it, It I am now hit with a "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I connect to Kies and It claims the Galaxy S4 isnt supported.
PCiE said:
After playing around with it, It I am now hit with a "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I connect to Kies and It claims the Galaxy S4 isnt supported.
Click to expand...
Click to collapse
Use this guide. You can stop at section 2 if you want to stay at Kitkat or go to section 3 if you want to update to Lollipop.
You can definitely install older versions, but you have to start with a full ROM like NB1. My guess is you flashed an incremental update like NC1, NJ4, etc. so Odin failed. When you Odin though, make sure Kies is completely closed or better yet, uninstall it as they hate each other
PS: This is assuming you have AT&T S4. I have no clue about other variants.
Related
Hi Guys,
I had rooted my phone using motochopper then yesterday I received OTA update. Everything seems to be fine then later I started getting Samsung Text-to-Speech engine has stopped working everytime I opened Gallery. It was very frustrating, so I did factory Reset. After Factory reset when I go to last screen to startup my phone(Learn about Key Features:Air view, Air gesture) and click Finish. I get "Unfortunately Settings has stopped" error. I found the stock firmware here hxxp://galaxys4root.com/galaxy-s4-stock-firmware/ But every time I use Odin I get PIT Partition not found.
Please help guys, I am stuck, don't know what to do now. :crying:
You can get the stock firmware from the "Development" section and also a step-by-step guide how to do it...search the development section for it. You can also find a lot of information about the issue you are having with the "stopped settings" error, again you can search for the info. I would also suggest you research ODIN to make sure you have the correct boxes checked so you don't hard brick your phone. Good luck.
i had the same exact issue and tried ODIN. didint work. i used to KIES to restore my firmware and it works again! try using KIES.
scott14719 said:
You can get the stock firmware from the "Development" section and also a step-by-step guide how to do it...search the development section for it. You can also find a lot of information about the issue you are having with the "stopped settings" error, again you can search for the info. I would also suggest you research ODIN to make sure you have the correct boxes checked so you don't hard brick your phone. Good luck.
Click to expand...
Click to collapse
I checked all appropriate settings for ODIN before upgrading the firmware. I got the same error all the time. I will research "Stopped Settings" error and let you know if I find anything. Thanks for the quick response.
kuraijay said:
i had the same exact issue and tried ODIN. didint work. i used to KIES to restore my firmware and it works again! try using KIES.
Click to expand...
Click to collapse
Hi I am choosing "Firmware upgrade and initialization" option to download the firmware. I put my phone into recovery mode as per steps mentioned and click "Start Upgrade" it takes around 40-50 minutes to download the firmware, then after sometime I get failed to connect to the phone. It's weird the "Start Upgrade" option is only enabled after I properly connect the cable and Kies have recognized the phone. Then why after some time it would say failed to recognized please try again?
zukaa12 said:
Hi I am choosing "Firmware upgrade and initialization" option to download the firmware. I put my phone into recovery mode as per steps mentioned and click "Start Upgrade" it takes around 40-50 minutes to download the firmware, then after sometime I get failed to connect to the phone. It's weird the "Start Upgrade" option is only enabled after I properly connect the cable and Kies have recognized the phone. Then why after some time it would say failed to recognized please try again?
Click to expand...
Click to collapse
weird mine never said enter recovery. what i did was plugged in my phone and i did the ""Firmware upgrade and initialization" then it gose through all the agreements and downloads the firmware. then it'll auto boot in to download mode for the install. are you using the stock usb? which port are you using on your computer? is KIES up to date? do you have the right drivers?( then again i think kies will install them but just in case) try already being in download mode.
also you can try this http://forum.xda-developers.com/showthread.php?t=2261232
I tried same at&t stock firmware but this time I used Odin 3.0.7 like Adam recommended in another post to upgrade and it worked like a charm. Before I was using Odin 1.8.5 and I was getting Missing PIT partition error all the time.
Thanks all for the quick response.
kuraijay said:
i had the same exact issue and tried ODIN. didint work. i used to KIES to restore my firmware and it works again! try using KIES.
Click to expand...
Click to collapse
I get different errors trying to flash stock ROM in Odin too. Missing PIT error mostly. Now phone is stuck at bad upgrade screen. Kies won't detect phone to use that method to restore either. Any other suggestions??
stumpmuncher said:
I get different errors trying to flash stock ROM in Odin too. Missing PIT error mostly. Now phone is stuck at bad upgrade screen. Kies won't detect phone to use that method to restore either. Any other suggestions??
Click to expand...
Click to collapse
Read the post above yours. Use the latest Odin 3.0.7.
-Sent from my Samsung Galaxy Note II using Tapatalk 2
What NOT to do with a new S4
RMXO said:
Read the post above yours. Use the latest Odin 3.0.7.
-Sent from my Samsung Galaxy Note II using Tapatalk 2
Click to expand...
Click to collapse
Did. Wouldn't have appealed for help without first making sure I followed the OP's instructions perfectly. I know the rules. I read the other posts before posting. I'm here for 2 things: To learn how to get the most potential out of my devices and to contribute from my experiences when I can. Thanks for your prompt reply though...
EDIT: solution to my stuck phone problem was solved by visit to ATT store for replacement. I can tell you what happened to my 7 day old device that brought it to the point where it would not load through Kies or Odin:
Eager to remove Samsung & ATT bloat stuff, I rooted using motochopper then used Titanium Backup to remove all ATT related apps & some of the Samsung apps. I got the unlock icon on lock screen as others have after root. I removed Superuser and replaced with SuperSU. Unlock icon went away and phone status went back to official. This is when I started noticing the Samsung text-to-speech program would frequently FC during the launch of few apps. Internet would also FC during certain operations. I read of others having success installing the stock ROM with ODIN and decided to give it a try. At first I got the no PIT error then finally after a few repeated attempts it moved past that point but then failed for some other reason during installation. I did notice a little activity on the progress bar on my device during Odin flash, but when the flash failed, that was it. My device was locked up. My PC & Kies would detect the device but could never connect or mount the device. My guess is that some of the Samsung apps I deleted were tied to the Samsung engines and the lack of their presence somehow caused FCs. Comments and questions appreciated.
Got the same Odin Mode Recovery Kies problem, No Pit fixed with ODIN 3.07 used PDA and loaded normal firmware.
Hey guys. Ive had a note 3 before in the past and have used the Root DelaVega to root successfully. This was early in the year. I sold my old note 3 for an HTC One. Well today i traded my HTC One back for a note 3 as i missed the Note 3. As soon as i came home i attempted to use the Root DelaVega method to foot (just like i did before) and immediately it failed.
I have been stuck on a screen saying "firmware update encountered an issue - select recovery in Kies" so i tried Kies 3.2 however it says my device is not compatible. Come to find out after doing research (talking to the original owner i traded my HTC One for) the Note 3 i have is on the latest version of KitKat 4.4.2 that is not compatible with the Root DelaVega method or any root method - so i screwed that up. I can successfully boot in and out of download mode. Ive tried to flash N900XXUDNA6 4.4.2 in Odin several times, it begins then fails almost immediately and the bar on the phone itself (in download mode) begins then freezes shortly after beginning. Ive also tried to flash N900XXUDNC1 JellyBean thru odin and get the same results - almost immediately fail and the blue status bar on the phone freezes when it barley begins. What else can i do??? am i totally screwed? Ive been researching and trying to fix this for 6 straight hours now! My gf is about to kill me for being online so long Is there anything i can do at this point? Am i stuck.
Do you know what Region the phone was originally? I had a similar issue and I had to get the Hong Kong (in my case) version of a stock ROM and flash that to get things working again. Not all partitions are the same - you might need a PIT file to match your original region and then flash the ROM.
What info do you get in DL mode?
Journyman16 said:
Do you know what Region the phone was originally? I had a similar issue and I had to get the Hong Kong (in my case) version of a stock ROM and flash that to get things working again. Not all partitions are the same - you might need a PIT file to match your original region and then flash the ROM.
What info do you get in DL mode?
Click to expand...
Click to collapse
Yes the phone is for AT&T so it's US. When I go into DL mode Knox counter is still 0x0. Is there a certain firmware I need then to match with the AT&T model? Or a pit?
jthornton71707 said:
Yes the phone is for AT&T so it's US. When I go into DL mode Knox counter is still 0x0. Is there a certain firmware I need then to match with the AT&T model? Or a pit?
Click to expand...
Click to collapse
Go to Sammobile and see if you can find the version you had, sounds like an older JB if kingo app didn't trip Knox. Reflash that using ODIN.
I don't know if there was a problem with American bootloader, see if there's an AT&T Note 3 forum. Might find answers there...
jthornton71707 said:
Hey guys. Ive had a note 3 before in the past and have used the Root DelaVega to root successfully. This was early in the year. I sold my old note 3 for an HTC One. Well today i traded my HTC One back for a note 3 as i missed the Note 3. As soon as i came home i attempted to use the Root DelaVega method to foot (just like i did before) and immediately it failed.
I have been stuck on a screen saying "firmware update encountered an issue - select recovery in Kies" so i tried Kies 3.2 however it says my device is not compatible. Come to find out after doing research (talking to the original owner i traded my HTC One for) the Note 3 i have is on the latest version of KitKat 4.4.2 that is not compatible with the Root DelaVega method or any root method - so i screwed that up. I can successfully boot in and out of download mode. Ive tried to flash N900XXUDNA6 4.4.2 in Odin several times, it begins then fails almost immediately and the bar on the phone itself (in download mode) begins then freezes shortly after beginning. Ive also tried to flash N900XXUDNC1 JellyBean thru odin and get the same results - almost immediately fail and the blue status bar on the phone freezes when it barley begins. What else can i do??? am i totally screwed? Ive been researching and trying to fix this for 6 straight hours now! My gf is about to kill me for being online so long Is there anything i can do at this point? Am i stuck.
Click to expand...
Click to collapse
Hi mate,
if you are stuck, maybe you can try this.
http://forum.xda-developers.com/show....php?t=2701062
it's a way to unbrick your software.
and if the older owner of your N3 said it's on the latest firmware of kitkat.
maybe your problem is the firmware in the sammobile were before the firmware you have install on your device via OTA update.
Yours firmware came throw out via OTA update and with some reason you can't see any latest firmware USA N900A in sammobile.
try the method in the link and reply if you have been successful.
cumps
Ik Knox is 0×0,then u can try samsung service centre ?
Sent from my SM-N900 using XDA Premium 4 mobile app
So to make long story short, I was on Official 4.3, then I rooted it, then installed CyanogenMod, by going here: beta.download.cyanogenmod(DOT)org/install
Then I wanted to go back to OFW, so I re flashed 4.2.2 and my WiFi didn't work, so I found out I got the older version of Android I wanted 4.3, so I re download it and it goes thru, and EVERYTIME it fails at the end, right after a file called "aboot.mbn". I'm getting all my firmware from Sammobile.com. What can I do?! I also tried a .pit file, and Samsung Kies, nothing works, I'm using the original cord I've tried different ports, and everything. Works fine with the older version of Android, but it does not update to 4.3 and the WiFi STILL doesn't work. HELP! It has shown a error saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again". However I can get into Download mode, but not recovery mode.
Thanks in advance!
-Jeremy
Hello guys,
I tried to root my SM-N900 this morning. I've root my Note 2 before and i thought it would just be the same. Unfortunately as i am starting to root with Odin, i've waited for hours but Odin is still not done with the phone and the download bar progression thing didnt move an inch. So with regret i turned off the phone and now it is stuck on "firmware upgrade encountered an issue" screen. I tried to download firmwares from sammobile but failed at 99% with a message of Unknown Network Error. So with that, are there any other solution possible? I've also tried Kies, but it wouldnt recognize my phone..
@bluws just download any stock firmware for your phone and flash it later with Odin. Use Odin 3.04 or 3.07 if 3.09 failed.
tetakpatalked from Nexus 7 flo
Make sure you are using correct Ver of root, make sure kies not running in bag round when you flash threw Odin, take care of antivirus
Sent from my SM-N9005
bluws said:
Hello guys,
I tried to root my SM-N900 this morning. I've root my Note 2 before and i thought it would just be the same. Unfortunately as i am starting to root with Odin, i've waited for hours but Odin is still not done with the phone and the download bar progression thing didnt move an inch. So with regret i turned off the phone and now it is stuck on "firmware upgrade encountered an issue" screen. I tried to download firmwares from sammobile but failed at 99% with a message of Unknown Network Error. So with that, are there any other solution possible? I've also tried Kies, but it wouldnt recognize my phone..
Click to expand...
Click to collapse
Try to connect your phone from the KIES program in a mode of emergency restoration of firmware by Model phone type and Serial Number of the phone. This may take several hours. To do this, you need a good internet.
bluws said:
Hello guys,
I tried to root my SM-N900 this morning. I've root my Note 2 before and i thought it would just be the same. Unfortunately as i am starting to root with Odin, i've waited for hours but Odin is still not done with the phone and the download bar progression thing didnt move an inch. So with regret i turned off the phone and now it is stuck on "firmware upgrade encountered an issue" screen. I tried to download firmwares from sammobile but failed at 99% with a message of Unknown Network Error. So with that, are there any other solution possible? I've also tried Kies, but it wouldnt recognize my phone..
Click to expand...
Click to collapse
Did you previously disable Knox? If you didn't, that can cause random problems, read about it in the newest Chainfire's thread in recent post:
http://forum.xda-developers.com/showthread.php?p=55325329
What kind of root process did you use Odin for?
tetakpatalked from Nexus 7 flo
Ty guys i got it working just by flashing a new stock rom. Tho now i am unable to call (no mobile services). Apparently it says that there are no sim card or something like that, does the region of the firmware i downloaded have something to do with it. Im living in indonesia (xse) but downloaded the russian stock i think.
bluws said:
Ty guys i got it working just by flashing a new stock rom. Tho now i am unable to call (no mobile services). Apparently it says that there are no sim card or something like that, does the region of the firmware i downloaded have something to do with it. Im living in indonesia (xse) but downloaded the russian stock i think.
Click to expand...
Click to collapse
Good it works again now!
Maybe it is just a baseband problem? I'm sure you will find an asian baseband only and be able to flash it.
Is your IMEI number still there? If yes, make sure to create backup of it now.
tetakpatalked from Nexus 7 flo
Hi! I am having major issues with my s4 i337 after switching from att to tmobile. The phone was unlocked so I took it upon myself to unlock it. It is unlocked but sometimes or rather most of the time does not pick up the network. When it does have data connection, it is Edge. I flashed the NC1 to root my phone, then reflashed to NJ4 (to unlock) but now nothing works. No wifi, camera fails, no multitasker, no voice assistant. Please help!!!!! I don't know what to do. I should have never unrooted it to unlock. I should have paid the $35 to get an unlock code. Can I fix this?
I have tried multiple APN settings,
Tried reflashing what I found online as att official firmware but it fails on ODIN.
So reflashed to NJ4, it is a bit laggy as well. Tried wifi which is greyed out, Camera still shows failed, pressing the home button to open multitasker and voice assistant brings up a blank grey screen. Phone is no longer connected as a mass storage device, only charges and can connect to ODIN.
I have attempted to factory reset which doesn't go through, unroot through SU which gets stuck on uninstalling and even trying to do an emergency recovery on Kies where it fails and gets stuck on kies failure mode.
I am on 4.4.4
I'm not sure what you mean by re flash to nj4, but have you flashed the nb1 tar? http://forum.xda-developers.com/showthread.php?p=50912149
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
I'm not sure what you mean by re flash to nj4, but have you flashed the nb1 tar? http://forum.xda-developers.com/showthread.php?p=50912149
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
No I have not tried that one! Should I try it and which version should I use since I am rooted?
jd1639 said:
I'm not sure what you mean by re flash to nj4, but have you flashed the nb1 tar? http://forum.xda-developers.com/showthread.php?p=50912149
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I guess I was following outdated information for rooting. =[ Which was dated 2013.... Should have sensed something was wrong.
I flashed this and it worked perfectly as you suggested! THANK YOU SO MUCH. No more sleepless nights combing through forums, thanks to you! Everything works and is back to normal, I was about to just throw away this phone thinking I permanently broke it. AGAIN MANY THANKS! I'm scared to root it now.
Although I have one more question, if you could please answer.
After booting and everything working, in the notification, it says unauthorized access and to restart to reset changes made, if I dismiss it, will this fix be permanent and not revert to the unworkable state it was in? When I reboot manually?
vannicuhh said:
No I have not tried that one! Should I try it and which version should I use since I am rooted?
Click to expand...
Click to collapse
It doesn't really matter since you can root the device in either case. The rootable nb1 can be directly rooted. The other one, you'll have to update to nc1 to root. Flashing with odin, you will lose and will have to re-root. Also, see "Index All things AT&T...." by Gutt13 in the General Forum
vannicuhh said:
Hi! I am having major issues with my s4 i337 after switching from att to tmobile. The phone was unlocked so I took it upon myself to unlock it. It is unlocked but sometimes or rather most of the time does not pick up the network. When it does have data connection, it is Edge. I flashed the NC1 to root my phone, then reflashed to NJ4 (to unlock) but now nothing works. No wifi, camera fails, no multitasker, no voice assistant. Please help!!!!! I don't know what to do. I should have never unrooted it to unlock. I should have paid the $35 to get an unlock code. Can I fix this?
I have tried multiple APN settings,
Tried reflashing what I found online as att official firmware but it fails on ODIN.
So reflashed to NJ4, it is a bit laggy as well. Tried wifi which is greyed out, Camera still shows failed, pressing the home button to open multitasker and voice assistant brings up a blank grey screen. Phone is no longer connected as a mass storage device, only charges and can connect to ODIN.
I have attempted to factory reset which doesn't go through, unroot through SU which gets stuck on uninstalling and even trying to do an emergency recovery on Kies where it fails and gets stuck on kies failure mode.
I am on 4.4.4
Click to expand...
Click to collapse
ODINing to NB1 should definitely help, but as far as mobile data if it still isn't working I thought i read somewhere that T-Mobile needs the AWS bands or something and you'll have to follow the process to enable those. There's a thread somewhere in the General section to do it on 4.4