S5 Issues rooted with 4.4.4 - Verizon Galaxy S 5 Q&A, Help & Troubleshooting

My S5 is rooted on 4.4.4 and I've been having lots of issues.
1. Phone would restart randomly.
2. Random apps would close.
3. If I have an app open (for example, the Camera), it would stop.
4. Phone would randomly freeze and would restart or stay frozen. I'd then have to pull the battery.
Is anybody else having these issues and/or know how to fix this? It's getting really annoying and I obviously can't use my phone properly. This is why I sometimes think about just getting a bloody iphone. ha!

We need more info. Did you freeze/uninstall anything? Does it have SafeStrap installed? Custom rom? Xposed modules? Or anything else?

I did "turn off" some apps in System > Applications and I also uninstalled some bloatware apps I didn't want. I just installed SafeStrap, so the issue was occurring way before I installed that. I have no roms nor Xposed modules.

So...take us through the steps you took to update and root.

Well, I first unrooted the phone and then updated to 4.4.4 through Kies because it would not let me update directly from the phone. The issues that I mentioned above started occurring after the update. Anyway, I then used the rooting method in one of the xda posts and started from Step 3.

xazilizax said:
Well, I first unrooted the phone and then updated to 4.4.4 through Kies because it would not let me update directly from the phone. The issues that I mentioned above started occurring after the update. Anyway, I then used the rooting method in one of the xda posts and started from Step 3.
Click to expand...
Click to collapse
This is how I root. I flash the NI2 tar in odin and use the files and instructions here. If you have the option to factory reset in the settings menu before you first flash the tar do so. Works like a charm every time for me.

Misterxtc said:
This is how I root. I flash the NI2 tar in odin and use the files and instructions here. If you have the option to factory reset in the settings menu before you first flash the tar do so. Works like a charm every time for me.
Click to expand...
Click to collapse
Let me 2nd Misterxtc' s suggestion. I was just about to suggest you Odin back to stock and start over. This time, once you are rooted and have ss installed go and make a backup. Now if you bone it up deleting stuff you can start over on a good install. Little extra work up front saves a ton down the road.

So, I un-rooted my phone using ODIN back to 4.4.4 and I did a factory reset and cleared cache. I'm restoring my apps now and some of them are still stopping - "Unfortunately Google Play (or whatever other app) has stopped." Grrr! -----So the un-rooting process did not fix my issues. =(

xazilizax said:
So, I un-rooted my phone using ODIN back to 4.4.4 and I did a factory reset and cleared cache. I'm restoring my apps now and some of them are still stopping - "Unfortunately Google Play (or whatever other app) has stopped." Grrr! -----So the un-rooting process did not fix my issues. =(
Click to expand...
Click to collapse
That happens immediately after restoring apps. Have you rebooted the phone and still have the issue? have you cleared cache and dalvik since restoring?

I did everything. I did factory reset from the Recovery. I cleared cache. I even did factory reset after the phone started up and nothing. I noticed that when I was going through Setup the last time, random system or google apps were stopping. Right now, my phone isn't connected to my google acct and I didn't install any apps, except for this one app called 'App Info' and it shows my Knox Warranty Void is 0x0, so I'm definitely taking it to Verizon this afternoon. Hopefully, they can fix it.

xazilizax said:
I did everything. I did factory reset from the Recovery. I cleared cache. I even did factory reset after the phone started up and nothing. I noticed that when I was going through Setup the last time, random system or google apps were stopping. Right now, my phone isn't connected to my google acct and I didn't install any apps, except for this one app called 'App Info' and it shows my Knox Warranty Void is 0x0, so I'm definitely taking it to Verizon this afternoon. Hopefully, they can fix it.
Click to expand...
Click to collapse
Did you flash the kernel after you flashed the update?

Misterxtc said:
This is how I root. I flash the NI2 tar in odin and use the files and instructions here. If you have the option to factory reset in the settings menu before you first flash the tar do so. Works like a charm every time for me.
Click to expand...
Click to collapse
I am having similar issues to OP. I followed your guide to a T. Here is what problems I had. After installing and running tr.apk it said device not suppored. I then went to TR website and got v3 and 'made it rain', it said it was okay. After this step 7: Shutdown and reboot once more into download mode and flash NI2_stock_kernel.tar.md5 with Odin in the AP slot.
It just sits on the Samsung Galaxy S5 (powered by android) boot screen and I cannot complete step 8. Any thoughts? Thanks in advance.

xazilizax said:
I did everything. I did factory reset from the Recovery. I cleared cache. I even did factory reset after the phone started up and nothing. I noticed that when I was going through Setup the last time, random system or google apps were stopping. Right now, my phone isn't connected to my google acct and I didn't install any apps, except for this one app called 'App Info' and it shows my Knox Warranty Void is 0x0, so I'm definitely taking it to Verizon this afternoon. Hopefully, they can fix it.
Click to expand...
Click to collapse
did you check md5 on the download? i simply installed a 444 rom and then used odin to flash 444 firmware n i was good to go lol. you must have a bad dl somewhere or doing something wrong
Sent from my SM-G900V using XDA Free mobile app
---------- Post added at 06:36 PM ---------- Previous post was at 06:35 PM ----------
Berdistheword said:
I am having similar issues to OP. I followed your guide to a T. Here is what problems I had. After installing and running tr.apk it said device not suppored. I then went to TR website and got v3 and 'made it rain', it said it was okay. After this step 7: Shutdown and reboot once more into download mode and flash NI2_stock_kernel.tar.md5 with Odin in the AP slot.
It just sits on the Samsung Galaxy S5 (powered by android) boot screen and I cannot complete step 8. Any thoughts? Thanks in advance.
Click to expand...
Click to collapse
can you take a screen of your odin on the pc? do you have n e thing else ticked? do you have a pit file etc
Sent from my SM-G900V using XDA Free mobile app

Berdistheword said:
I am having similar issues to OP. I followed your guide to a T. Here is what problems I had. After installing and running tr.apk it said device not suppored. I then went to TR website and got v3 and 'made it rain', it said it was okay. After this step 7: Shutdown and reboot once more into download mode and flash NI2_stock_kernel.tar.md5 with Odin in the AP slot.
It just sits on the Samsung Galaxy S5 (powered by android) boot screen and I cannot complete step 8. Any thoughts? Thanks in advance.
Click to expand...
Click to collapse
It should be fine if you used the ni2 file from the root.zip file. It works for me as well as others but I've seen issues with new phones. I'm not sure why.

elliwigy said:
did you check md5 on the download? i simply installed a 444 rom and then used odin to flash 444 firmware n i was good to go lol. you must have a bad dl somewhere or doing something wrong
Sent from my SM-G900V using XDA Free mobile app
---------- Post added at 06:36 PM ---------- Previous post was at 06:35 PM ----------
can you take a screen of your odin on the pc? do you have n e thing else ticked? do you have a pit file etc
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
Good idea. I will re download and double check MD5. Here is a SS of Odin. Imgur url is this (wont let me post because noob) --> /tvRayDC.jpg
I'm basically trying to narrow down whether the rebooting is hardware or software related. I might just return to stock and get a refurb unit if I can't figure it out. It seems like the restarting occurs intermittently when the phone trys to use the signal. I had one random reboot when i was in Safestrap and am also seeing reboots in 4.4.2 NCG stock. So maybe modem related? Maybe I can try another Kernel?
<br>
Misterxtc said:
It should be fine if you used the ni2 file from the root.zip file. It works for me as well as others but I've seen issues with new phones. I'm not sure why.
Click to expand...
Click to collapse
Good to know. I will double check the MD5.

Berdistheword said:
Good idea. I will re download and double check MD5. Here is a SS of Odin. Imgur url is this (wont let me post because noob) --> /tvRayDC.jpg
I'm basically trying to narrow down whether the rebooting is hardware or software related. I might just return to stock and get a refurb unit if I can't figure it out. It seems like the restarting occurs intermittently when the phone trys to use the signal. I had one random reboot when i was in Safestrap and am also seeing reboots in 4.4.2 NCG stock. So maybe modem related? Maybe I can try another Kernel?
<br>
Good to know. I will double check the MD5.
Click to expand...
Click to collapse
You canalways download the NI2 full tar from here and then follow the Root NI2 directions. If towelroot doesn't work try this. I always factory reset the phone from the settings menu before I flash the tar.

Related

[Q]Can you downgrade from MJA to MF9 through ODIN?

The Knox Bootloader is.... Annoying
Anyone know if I could flash the MF9 tar in ODIN and revert back to the 4.2 Bootloader
do not you will even cause bigger problems stay cool untill a tar is released they are working hard to see what they can due the only choice you have no is to go to a ROM that is 4.3 but that I know of it is still un heard of KNOX is a whole new monster that I have a feeling is gonna tick a lot of people off love love love Samsung phones but they need to realize this could hurt them....
NO.
Sent from my SPH-L720 using Tapatalk
jprocket45 said:
do not you will even cause bigger problems stay cool untill a tar is released they are working hard to see what they can due the only choice you have no is to go to a ROM that is 4.3 but that I know of it is still un heard of KNOX is a whole new monster that I have a feeling is gonna tick a lot of people off love love love Samsung phones but they need to realize this could hurt them....
Click to expand...
Click to collapse
Thanks for the reply. If I had known that KNOX was gonna be such a problem I would of held off from upgrading...
Guess I gotta be patient until our beautiful dev community comes up with some way to deal with KNOX
Robin Dhicke said:
Thanks for the reply. If I had known that KNOX was gonna be such a problem I would of held off from upgrading...
Guess I gotta be patient until our beautiful dev community comes up with some way to deal with KNOX
Click to expand...
Click to collapse
so there is no way to go back to MDC then huh? -/-
kalanir said:
so there is no way to go back to MDC then huh? -/-
Click to expand...
Click to collapse
Well not yet.
Sent from my SPH-L720 using xda app-developers app
nope stuck just like the rest of us lol its not fun
Don't worry......it's only a matter of time. If u need a stable rom, I highly recommend sac23's custom 4.3 rom. V3 will be out soon. This rom has made it easier to cope with 4.3, well easier for us who are stuck with the Knox......check out his thread. You'll love it.
Sent from my SPH-L720 using XDA Premium 4 mobile app
I'm not sure what any of you are talking about. I updated to 4.3 a couple of days ago, then wiped and flashed a MDC tar with ODIN and brought it back to MF9 with OTA updates. Everything is fine.
---------- Post added at 12:15 AM ---------- Previous post was at 12:14 AM ----------
Robin Dhicke said:
The Knox Bootloader is.... Annoying
Anyone know if I could flash the MF9 tar in ODIN and revert back to the 4.2 Bootloader
Click to expand...
Click to collapse
Yes... You can do this. I did it. See my last post above.
Sleepycloud said:
I'm not sure what any of you are talking about. I updated to 4.3 a couple of days ago, then wiped and flashed a MDC tar with ODIN and brought it back to MF9 with OTA updates. Everything is fine.
---------- Post added at 12:15 AM ---------- Previous post was at 12:14 AM ----------
Yes... You can do this. I did it. See my last post above.
Click to expand...
Click to collapse
Hello,
How did you manage to do it?
I tried to do that with Odin 1.85 and 3.07 and nothing. It aborts right away.
edgardch said:
Hello,
How did you manage to do it?
I tried to do that with Odin 1.85 and 3.07 and nothing. It aborts right away.
Click to expand...
Click to collapse
I wiped everything in TWRP, and rebooted into download mode. Then flashed the tar with 3.07 and a PIT file. Uncheck reboot. Check Repartitition, Nand erase, and F. Reset Time. When it reboots it wiil update in recovery with the little andy dude, and then reboot to load up. I pull the battery and factory reset. It works fine. I updated to 4.3 friday morning. and decided to go back to MF9 so that I could use The HotSpot Mod and Reboot Menu. F**k 4.3...it was disapointing.
EDIT-----> READ ALL OF THE FOLLOW-UP POSTS BEFORE YOU TRY THIS.... MY PHONE HAD A UNIQUE SITUATION AND THIS WILL NOT WORK FOR MOST EVERYONE ELSE.
Sleepycloud said:
I wiped everything in TWRP, and rebooted into download mode. Then flashed the tar with 3.07 and a PIT file. Uncheck reboot. Check Repartitition, Nand erase, and F. Reset Time. When it reboots it wiil update in recovery with the little andy dude, and then reboot to load up. I pull the battery and factory reset. It works fine. I updated to 4.3 friday morning. and decided to go back to MF9 so that I could use The HotSpot Mod and Reboot Menu. F**k 4.3...it was disapointing.
Click to expand...
Click to collapse
I want proof lol. go to mja again and go back to mf9 lol
Sent from my SPH-L720 using Tapatalk
daniel4653 said:
I want proof lol. go to mja again and go back to mf9 lol
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
There is one problem. Now it won't update to MJA. Something is different, but I'm not sure what. I don't care if you don't believe me. I did it, and that is how I did it. There was one other issue. It kept redownloading the Sprint Default Configuration over and over and over. Like more than 50 times back to back.I finally deleted the apk to get that to stop. Outside of that, my phone works fine. I believe their are remnants of 4.3 and that is why it says the system is up to date on MF9 and does not prompt me for the 4.3 update. I really don't know, but m phone appears to be working perfectly.
Sleepycloud said:
There is one problem. Now it won't update to MJA. Something is different, but I'm not sure what. I don't care if you don't believe me. I did it, and that is how I did it. There was one other issue. It kept redownloading the Sprint Default Configuration over and over and over. I finally deleted the apk to get that to stop. Outside of that, my phone works fine.
Click to expand...
Click to collapse
As in tkaimg the OTA or trying to flash MJA ROM like Skyrockets or Sacs ?,
Sent from my SPH-L720 using Tapatalk
daniel4653 said:
As in tkaimg the OTA or trying to flash MJA ROM like Skyrockets or Sacs ?,
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
The OTA. It doesn't recognize any update as being available anymore. It went from MDC to MDL to MF9 just fine. Then stopped. It says it's up to date now? I'm not sure what's going on with it, but I rerooted it and it works fine. I even innitialised it on KIES to set it all the way back to stock MF9 but it still won't show any update as being available for 4.3
daniel4653 said:
I want proof lol. go to mja again and go back to mf9 lol
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
I tried it just barely as I want to go back to my mf9 rom with the stock kernel. You get a secure error on pit and also a firmware revision error "fused 4 .... 1" can't remember what the word was where the dots were. It was a no go for me. I tried to odin back to mdc like was mentioned in the previous posts.
:EDIT Definitely don't try this. Caused my data partition to get corrupt. Couldn't format it. Couldn't pit restore it. Philz recovery couldn't mount it. Finally found an option to format data and sdcard. This allowed me to format data and restore. Once again Definitely don't try if you have the mja bootloader. (I'm back up and running and will let other figure this out.)
I just found out why I was able to go back to 4.2.2!!! When I updated to 4.3 via OTA a couple of days ago, I plugged it in to KIES 3 and noticed it said "PDA:MJA, Phone:MF9, CSC:MJA".... notice the phone says MF9! I don't know how that happened, but I didn't question it at the time because it was OTA. I thought it was supposed to be that way. Last night before I went to bed I manually flashed the 4.3 update zip after using KIES to initialise my phone back to complete stock. (It wouldn't load the zip when I was rooted) Anyways.... Well this morning I plugged it in to KIES 3 after flashing the 4.3 update.zip last night and it said MJA on all three. I'm not sure how that happened, but I only got part of the OTA update a couple of days ago it appears, and thus being, it is the reason I was able to revert. Sorry if I got anyones hopes up. I just went back and edited a warning in my first post with instructions.
Bummer!!! lol i was getting all excited.
wilsonwa said:
I tried it just barely as I want to go back to my mf9 rom with the stock kernel. You get a secure error on pit and also a firmware revision error "fused 4 .... 1" can't remember what the word was where the dots were. It was a no go for me. I tried to odin back to mdc like was mentioned in the previous posts.
:EDIT Definitely don't try this. Caused my data partition to get corrupt. Couldn't format it. Couldn't pit restore it. Philz recovery couldn't mount it. Finally found an option to format data and sdcard. This allowed me to format data and restore. Once again Definitely don't try if you have the mja bootloader. (I'm back up and running and will let other figure this out.)
Click to expand...
Click to collapse
I'm having the same issue that you had with the data partition being corrupt. I had stupidly tried to downgrade stock MJA to MF9 before checking with the forums if it was possible. It got stuck in the Firmware error message (can't remember what it exactly said), but got to restore it to a stock MJA. And now its data partition cannot be recognized in any computer. IE: Whenever I plug it into the computer it used to show that it is connected via USB and give me the MTP option. Now it will not even do that and I cannot access its data partition via the computer. Kies won't even recognize it.
How did you get to format data and sdcard?
EDIT: OK, dont know how, (I'm blaming crappy cable) but now I do have access to the phone. In other words it's working normal. But in case that this were to happen again, it would be awesome to know how to format data section, so as it can be recognized by the computer. Thanks in advance.

4.3 fails during install

Hi,
On MF3.
I'm rooted. I have clock work recovery installed.
I can download the update succeffuly however when the phone reboots the install begins, gets as far as 25% then fails. Phone reboots back to 4.2.2 with a message that says the install was interrupted.
Have tried twice with the same result.
Anyone else experiencing this?
Sent from my SAMSUNG-SGH-I337 using Tapatalk
ckalantzis said:
Hi,
On MF3.
I'm rooted. I have clock work recovery installed.
I can download the update succeffuly however when the phone reboots the install begins, gets as far as 25% then fails. Phone reboots back to 4.2.2 with a message that says the install was interrupted.
Have tried twice with the same result.
Anyone else experiencing this?
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
If I were you I would go back and read a little information about mf3 and what kind of recovery can be used. It sounds to me like you might be very confused. In order to correctly keep from bricking your phone you may want to read up on things. Good luck.
ckalantzis said:
Hi,
On MF3.
I'm rooted. I have clock work recovery installed.
I can download the update succeffuly however when the phone reboots the install begins, gets as far as 25% then fails. Phone reboots back to 4.2.2 with a message that says the install was interrupted.
Have tried twice with the same result.
Anyone else experiencing this?
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
Since you are rooted, take a look in the /cache/recovery directory. Read the log file. It will tell you where things messed up.
For example, I had forgotten that I did something with csc and had replaced the feature.xml file. Luckily, I had a back up of the original file. I renamed it, fixed is file permissions to rw-r--r--, advanced my clock one day, and then was able to install MJ9.
Good luck, and remember you won't have root anymore when you install this (for the time being)
Yrs,
dkephart
Sent from my SAMSUNG-SGH-I337 using Tapatalk
ckalantzis said:
Hi,
On MF3.
I'm rooted. I have clock work recovery installed.
I can download the update succeffuly however when the phone reboots the install begins, gets as far as 25% then fails. Phone reboots back to 4.2.2 with a message that says the install was interrupted.
Have tried twice with the same result.
Anyone else experiencing this?
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
I had the same problem. The only way I was finally able to upgrade to 4.3 was to use Odin to revert to stock (unrooted) 4.2.2 MF3 using the files on this thread: http://forum.xda-developers.com/showthread.php?t=2502003 Once I did that I ran the OTA update to 4.3 and it worked without any problems
To able to keep your root and upgrade from 4.2.2 to 4.3 you have to change your param file back to the stock. Thats all the information that I have so far so... not completely sure. But I think that is what you're supposed to do.
Because you have a custom param file, when you try to upgrade to 4.3 it's telling you there is an issue with your phone.
I may be wrong.
Is there a copy of the correct feature.xml? Im having the same issue
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
According to the log its stopping when it can't find the chat on apk. I did remove it using titanium.
Will restore it try again andbipdate the thread. Thanks for pointing out the correct log file to look at.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
I checked again and found my backup feature.xml. Typed this from mj9.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
ckalantzis said:
Hi,
On MF3.
I'm rooted. I have clock work recovery installed.
I can download the update succeffuly however when the phone reboots the install begins, gets as far as 25% then fails. Phone reboots back to 4.2.2 with a message that says the install was interrupted.
Have tried twice with the same result.
Anyone else experiencing this?
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
I had the same problem happen to me on Wednesday night and last night. Today I used Odin to go back to stock MF3, however, then I couldn't get the OTA update. It kept saying my firmware was up to date each of the three times I restored it.
Now I'm finally on MJ9 after copying "update-mf3-mj9.zip" to my SD card, going into recovery mode, and updating from external SD card. Now I can use my Galaxy Gear!
Cause I want to sound like a noob.
How did you install CWM on what reads to me a MF3 S4.
Those on MF3 have been using Safestrap cause CWM hasn't been possible.
Sent from my ATT S4 MF3 using Tapatalk
jball said:
Cause I want to sound like a noob.
How did you install CWM on what reads to me a MF3 S4.
Those on MF3 have been using Safestrap cause CWM hasn't been possible.
Sent from my ATT S4 MF3 using Tapatalk
Click to expand...
Click to collapse
I was excited when I rooted the phone, then installed ROM manager premium. It allowed me to install the recovery. You can even boot into the recovery from ROM Manager.
However since the S4 is locked down tight, you can do any thing from there. So i can't flash anything. It even gives me a message saying as much.
However it is partially installed I can boot into it at will.
I will post a video of it. So that you all have an idea of what im talking about.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Don't waste your time with a video,its your stock recovery.your not the first to have done this.lets jump ahead a bit and just install Safestrap.whats Safestrap you might ask?search for it and READ please sir.
Sent from my ATT S4 MF3 using Tapatalk
jball said:
Don't waste your time with a video,its your stock recovery.your not the first to have done this.lets jump ahead a bit and just install Safestrap.whats Safestrap you might ask?search for it and READ please sir.
Sent from my ATT S4 MF3 using Tapatalk
Click to expand...
Click to collapse
While I was preparing to record it, I did notice that you are correct. Although Rom Manager goes through the motions of flashing the recovery, when you attempt to boot into the Recovery, you are faced with an Error, and default back into Android Recovery.
Although I know all about Safestrap...I think we've all missed the point. The OP was meant to get help about why the 4.3 OTA was failing 25% into the install.
I've got what I needed by being pointed to the location of the install log.....and while reading through it, I noticed that the install is failing because I removed the Chat On APK. I will install from backup and move forward.
Thank you all who provided the necessary guidance to solve the original problem.
Thank you as well to those who helped clear up the whole Clockwork vs Android recovery part. Although a minor part of the original post, it's good that we don't spread misinformation.
Cheers
ckalantzis said:
While I was preparing to record it, I did notice that you are correct. Although Rom Manager goes through the motions of flashing the recovery, when you attempt to boot into the Recovery, you are faced with an Error, and default back into Android Recovery.
Although I know all about Safestrap...I think we've all missed the point. The OP was meant to get help about why the 4.3 OTA was failing 25% into the install.
I've got what I needed by being pointed to the location of the install log.....and while reading through it, I noticed that the install is failing because I removed the Chat On APK. I will install from backup and move forward.
Thank you all who provided the necessary guidance to solve the original problem.
Thank you as well to those who helped clear up the whole Clockwork vs Android recovery part. Although a minor part of the original post, it's good that we don't spread misinformation.
Cheers
Click to expand...
Click to collapse
You handled this all very well.
ITNV said:
I had the same problem. The only way I was finally able to upgrade to 4.3 was to use Odin to revert to stock (unrooted) 4.2.2 MF3 using the files on this thread: http://forum.xda-developers.com/showthread.php?t=2502003 Once I did that I ran the OTA update to 4.3 and it worked without any problems
Click to expand...
Click to collapse
Did you use all files? I mean, I've been trying the same for the past couple of days, and I even asked in that thread if I could use just the PDA file, nobody replied so I went ahead and did it, it removed the root and I kept all my files and settings (That was the idea) but just after that I can't connect anymore to Kies ( I could without issues, I did a full backup moments before) and trying to do the sideload it always gives me the Error 7, I even tried the full SD card update,it erased everything and guess what, when it rebooted for my surprise I was still at 4.2.2 MF3, so it just did the Wipe Data and then rebooted, so I lost almost 6 hours getting everything back as it was and then, I had the Damaged SD card error so I also lost all my pictures and videos withoout back up.
So, as you can see half a day later I'm still at the same point I was this morning and with a huge loss, so, please, Did you use all the files? If you did, doing this erase everything also?
Thanks in adavance.
erasat said:
So, as you can see half a day later I'm still at the same point I was this morning and with a huge loss, so, please, Did you use all the files? If you did, doing this erase everything also?
Thanks in adavance.
Click to expand...
Click to collapse
Yes. I used all the files. The result was a completely stock unrooted 4.2.2 so, yes, it reset the phone and erased everything that I had on there. (It left my external SD card intact but I would still advise removing it if there is anything on there you don't want to lose.)
ITNV said:
Yes. I used all the files. The result was a completely stock unrooted 4.2.2 so, yes, it reset the phone and erased everything that I had on there. (It left my external SD card intact but I would still advise removing it if there is anything on there you don't want to lose.)
Click to expand...
Click to collapse
Yep, that was the reason why I just used the PDA I didn't want to lose my data, and then I did it anyways, my mistake was not doing the Odin Restore just after I realized that it erased everything and I was still at 4.2.2, that's was the perfect time to do it, but now, after I finally put everything back as it was, I simply don't see myself by my own choice, doing all this again.
Thanks.
erasat said:
Did you use all files? I mean, I've been trying the same for the past couple of days, and I even asked in that thread if I could use just the PDA file, nobody replied so I went a head and did it, it removed the root and I kept all my files and settings (That was the idea) but just after that I can't connect anymore to Kies ( I could without issues, I did a full backup moments before) and trying to do the sideload it always gives me the Error 7, I even tried the full SD card update,it erased everything and guess what, when it rebooted for my surprise I was still at 4.2.2 MF3, so it just did the Wipe Data and then rebooted, so I lost almost 6 hours getting everything back as it was and then, I had the Damaged SD card error so I also lost all my pictures and videos withoout back up.
So, as you can see half a day later I'm still at the same point I was this morning and with a huge loss, so, please, Did you use all the files? If you did, doing this erase everything also?
Thanks in adavance.
Click to expand...
Click to collapse
It was mentioned several times in that thread exactly what files to use and how to use them. There were also several pictures provided that showed EXACTLY what the ODIN screen should look like before the flash.
scott14719 said:
It was mentioned several times in that thread exactly what files to use and how to use them. There were also several pictures provided that showed EXACTLY what the ODIN screen should look like before the flash.
Click to expand...
Click to collapse
In the thread, there are tons of instances where it explains where to use each file and even pictures, I know because I read every single post, but none of them explains if I could use just the PDA one if I wanted to keep my settings while unrooting the phone, that's why I asked about it, because nobody replied to my question I decided to be the guinea pig, and yes, it works, you keep your settings, and I was glad, but as you can see, what I wanted to accomplish didn't work after all. Without all the files it doesn't fix the issue that causes the error 7 when doing the sideload.
help with mf3 to mj9
Having the same issue and formatted card with backup image.
Update got to 23 % and failed
now phone refuses to flash in odin.....and im missing factory apps preventing me from doing anything to get it back to stock
anyone have a stock restore image I could use in kies?
Would that work properly?

Cannot setup phone (unfortunately, setting has stopped).

Hello, today i wanted to flash a new rom on my galaxy s4, rooted it a while ago but hadn't flashed a rom. Went to Rom Manager and was gonna do a backup but it was giving me an error so I could not do the backup. Since I had saved all my pictures and everything on dropbox I just went ahead and went to recovery mode and wiped my data so I could flash the new rom. When I tried to wipe the cache partition it just rebooted my phone. When the phone started up I get all the usual setup from TouchWiz. I started setting it all up as usual but when I get to the final screen (learn about key features) I hit finish and then i get the "Unfortunately, Settings has stopped." not allowing me to continue on to my home screen. So as of right now my phone is basically a paper weight because I can not to anything. Has anyone else encountered this ? Is there a work around ? Will appreciate all help.
P.s. Sorry if there is already a post about this, I just don't frequent this page very often and don't quite understand how all the search functions and all that work.
abyxjohnson said:
Hello, today i wanted to flash a new rom on my galaxy s4, rooted it a while ago but hadn't flashed a rom. Went to Rom Manager and was gonna do a backup but it was giving me an error so I could not do the backup. Since I had saved all my pictures and everything on dropbox I just went ahead and went to recovery mode and wiped my data so I could flash the new rom. When I tried to wipe the cache partition it just rebooted my phone. When the phone started up I get all the usual setup from TouchWiz. I started setting it all up as usual but when I get to the final screen (learn about key features) I hit finish and then i get the "Unfortunately, Settings has stopped." not allowing me to continue on to my home screen. So as of right now my phone is basically a paper weight because I can not to anything. Has anyone else encountered this ? Is there a work around ? Will appreciate all help.
P.s. Sorry if there is already a post about this, I just don't frequent this page very often and don't quite understand how all the search functions and all that work.
Click to expand...
Click to collapse
First off what firmware are you on. MDL, mf3, mj6, mj9? To check go to settings - more - about device and check build number. If it is mf3 than you need to go to the general section and read how to odin the md5 file same as other build numbers. You just have to take your time and read.
Sent from my SAMSUNG-SGH-I337 using xda premium
Never use rom manage to flash a rom. As stated, we need to know the firmware you're on to help you.
[email protected] said:
First off what firmware are you on. MDL, mf3, mj6, mj9? To check go to settings - more - about device and check build number. If it is mf3 than you need to go to the general section and read how to odin the md5 file same as other build numbers. You just have to take your time and read.
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
I cant check because I cannot get into the phone. I cannot complete the initial setup of the phone.
abyxjohnson said:
I cant check because I cannot get into the phone. I cannot complete the initial setup of the phone.
Click to expand...
Click to collapse
Can you boot it into download mode?
Edit, do you have a custom recovery on it and did you make a nandroid?
Do you have safestrap or how do you flash roms? Because if you have safestrap than your on mf3.. If you can install Roms without safestrap than you must be on MDL.
Sent from my SAMSUNG-SGH-I337 using xda premium
jd1639 said:
Never use rom manage to flash a rom. As stated, we need to know the firmware you're on to help you.
Click to expand...
Click to collapse
I didnt use rom manager to flash the rom, I was trying to create a backup of my stock rom with it. I went to recovery mode to try and flash the rom.
[email protected] said:
Do you have safestrap or how do you flash roms? Because if you have safestrap than your on mf3.. If you can install Roms without safestrap than you must be on MDL.
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
I dont have safestrap, and I hadn't installed any roms on my S4 yet, this was going to be the first time. I use to flash rome on my S2 a while back and was gonna do it for the first time with my S4 through recovery mode. Sorry if im not really giving you key information, I just don't know it. I learned the basics of flashing roms and that was about it. Obviously the wrong thing to do because I might have just rendered my phone useless.
jd1639 said:
Can you boot it into download mode?
Edit, do you have a custom recovery on it and did you make a nandroid?
Click to expand...
Click to collapse
Yes I can boot into download mode. Yes, I have clockworkmod installed. No I could not make a backup, It kept crashing and would not allow me.
I would try to odin the mdl firmware in download mode. You can get the firmware at sammobile.com. You'll have to register but it's free. You'll download a zip file. Use 7-zip to extract the .tar.md5 file from it. Use that in odin, PDA.
jd1639 said:
I would try to odin the mdl firmware in download mode. You can get the firmware at sammobile.com. You'll have to register but it's free. You'll download a zip file. Use 7-zip to extract the .tar.md5 file from it. Use that in odin, PDA.
Click to expand...
Click to collapse
Is there a place I can get a step by step of how to do this somewhere ? Really sorry, Im just not very knowledgeable about all this stuff.
abyxjohnson said:
Is there a place I can get a step by step of how to do this somewhere ? Really sorry, Im just not very knowledgeable about all this stuff.
Click to expand...
Click to collapse
You can try this guide. It's not for the s4 but all the steps are the same. Just don't use any files except for Odin linked in it. http://forum.xda-developers.com/showthread.php?p=26056924
jd1639 said:
You can try this guide. It's not for the s4 but all the steps are the same. Just don't use any files except for Odin linked in it. http://forum.xda-developers.com/showthread.php?p=26056924
Click to expand...
Click to collapse
Did everything with Odin and downloaded the file I needed but when I try to flash with Odin it says Fail. And at the messages you get at the bottom it says "Cant open the serial (COM) port."
abyxjohnson said:
Did everything with Odin and downloaded the file I needed but when I try to flash with Odin it says Fail. And at the messages you get at the bottom it says "Cant open the serial (COM) port."
Click to expand...
Click to collapse
You doing it on a Windows pc? Use the usb ports in the back, not the front. You the usb cable that came with your phone.
jd1639 said:
You doing it on a Windows pc? Use the usb ports in the back, not the front. You the usb cable that came with your phone.
Click to expand...
Click to collapse
Im using a laptop. Trying all the USB ports with the original cable that came with the phone.
abyxjohnson said:
Did everything with Odin and downloaded the file I needed but when I try to flash with Odin it says Fail. And at the messages you get at the bottom it says "Cant open the serial (COM) port."
Click to expand...
Click to collapse
Check to see if there are any popups that you have to allow before a connection can be made. Sometimes they appear behind the ODIN screen (on the PC). Also, make sure you have the proper drivers installed.
If you can get to clockwork, just copy a new rom to your SD card and flash it. You'll be up and running in 5 minutes.

[Q] How to go back to stock? (SPH-L720T)

I have already unrooted my phone but I've been getting these update notifications to update my phone and when it restarts the phone to update, it fails! Everytime. So i'm guessing I need to go back to stock using Odin and a Tar file but I havent found any for the SPH-L720T version just SPH-L720. Does anyone know how I can fix this?
You didn't search long or hard enough. The answer IS here - even for the T version.
I'll thow this out to you.
Reason you can't update is because you have a custom recovery/kernel.
To get/receive an update you have to be on FULL Stock recovery and kernel.
If you want to get back to full stock you can try this
Got to sammobile.com and login in (register if you have to) then download the latest .tar for the T model
Then extract (unzip) the firmware file (just to the .tar.md5 file)
Open Odin
Reboot phone in Download Mode (press and hold Home + Power + Volume Down buttons. Volume up next)
Connect phone and wait until you get a blue sign in Odin
Add the firmware file to PDA slot (only file named .tar.md5)
Leave Autoreboot and F. Reset checked.
Make sure re-partition is NOT ticked
Click the start button, sit back and wait a few minutes.
You phone will finish and should reboot.
1st boot takes a while (about 5 EARTH minutes) then you should get the 'activate' process.
leaderbuilder said:
You didn't search long or hard enough. The answer IS here - even for the T version.
I'll thow this out to you.
Reason you can't update is because you have a custom recovery/kernel.
To get/receive an update you have to be on FULL Stock recovery and kernel.
If you want to get back to full stock you can try this
Got to sammobile.com and login in (register if you have to) then download the latest .tar for the T model
Then extract (unzip) the firmware file (just to the .tar.md5 file)
Open Odin
Reboot phone in Download Mode (press and hold Home + Power + Volume Down buttons. Volume up next)
Connect phone and wait until you get a blue sign in Odin
Add the firmware file to PDA slot (only file named .tar.md5)
Leave Autoreboot and F. Reset checked.
Make sure re-partition is NOT ticked
Click the start button, sit back and wait a few minutes.
You phone will finish and should reboot.
1st boot takes a while (about 5 EARTH minutes) then you should get the 'activate' process.
Click to expand...
Click to collapse
It worked but after initial reboot I found that my wifi no longer works everytime I go to turn it on I get a security message any suggestions?
go into system settings>about phone and check your baseband (it's the modem/firmware) if it doesn't match (it should say NC6) the build version then you may have to re-flash.
Also have you made sure to upate your PRL AND Profile?
I have read a few posts abou this and it seems to actually be a Sprint issue.
Just ODIN back to stock NC6. That should do it.
Sent from my iPad using Tapatalk
Why, why would you make another thread thread just for your WiFi problems when two users have already give you answers/options. You asked the question at 3:38pm and waited 12 mins to 4:00pm and decided to make a new thread. It clogges the forum up.
Sent from my SPH-L720 using Tapatalk
daniel4653 said:
Why, why would you make another thread thread just for your WiFi problems when two users have already give you answers/options. You asked the question at 3:38pm and waited 12 mins to 4:00pm and decided to make a new thread. It clogges the forum up.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
Because I didnt feel it was right to depend on that ONE guy who had already helped me once AND i'm putting in the correct tags so when other people have the same issues im having this same thread will pop up and they will have they're answered already here thanks to you guys so it's actually less clutter if you see it how I see it! lol
VandyCWG said:
Just ODIN back to stock NC6. That should do it.
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
Which one is NC6 again? The one the guy linked to up there ^ was the 4.4.2 and I was on 4.3 so yeah you guys were right I probably have different basebands. Is NC6 the 4.4.2? Im downloading the 4.3 as we speak but man those servers over there at samobile are bad right now :/
Cudeh said:
Because I didnt feel it was right to depend on that ONE guy who had already helped me once AND i'm putting in the correct tags so when other people have the same issues im having this same thread will pop up and they will have they're answered already here thanks to you guys so it's actually less clutter if you see it how I see it! lol
Click to expand...
Click to collapse
I understand that but you should give it some time to see if others answer. Lol
Sent from my SPH-L720 using Tapatalk
leaderbuilder said:
go into system settings>about phone and check your baseband (it's the modem/firmware) if it doesn't match (it should say NC6) the build version then you may have to re-flash.
Also have you made sure to upate your PRL AND Profile?
I have read a few posts abou this and it seems to actually be a Sprint issue.
Click to expand...
Click to collapse
What exactly do I reflash? The same tar file that got me to 4.4.2?
Did you try to wipe caches after going back to stock unrooted.
Sent from my SPH-L720 using Tapatalk
---------- Post added at 04:41 PM ---------- Previous post was at 04:39 PM ----------
Also I think that security message is from Knox which means that its detecting something on your phone. Possibly an app that requires root?
Sent from my SPH-L720 using Tapatalk
daniel4653 said:
Did you try to wipe caches after going back to stock unrooted.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
Yeah I even factory reset my phone. Turns out my modem and basebands are different. I just dont know which one to re flash the 4.4.2 that got me in this trouble or the original 4.3 thats taking forever to download lol
daniel4653 said:
Did you try to wipe caches after going back to stock unrooted.
Sent from my SPH-L720 using Tapatalk
---------- Post added at 04:41 PM ---------- Previous post was at 04:39 PM ----------
Also I think that security message is from Knox which means that its detecting something on your phone. Possibly an app that requires root?
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
It is from Knox I found that out when I tried clearing cache/data on the security message and I even forced closed it then tried wi-fi and no luck.
go into stock recovery and factory reset.
Then after booting up shut down completely.
Then boot to recovery.
Reflash the .tar (follow previous proceedure)
And see if the baseband/modem is properly updated this time.
I read that some people, after taking the latest OTA (the same as the .tar) have had to go back to sprint to have them fix it - most likely just flashing the modem.
That being said since there are some (read many) people having this issue with NC6, you can always try to Odin the NAF .tar and see if all works.
Then if you want try and take the Sprint OTA (via system settings>more>updates and check there.
I think my Device is bricked now
I followed the method which leaderbuilder said and now I believe my phone is bricked. It won't boot into recovery anymore. When the phone is turned on it says "Firmware upgrade encountered an issue. Please select recovery mode in kies & try again." But when I open kies it says my device is not supported. Someone help me please. :crying:

Issues have begun...Cant turn on wifi, Losing data connection, no sim

Hello Gents,
Have had my S4 for about a year now and its been awesome (still on MK2, stopped it from updating). It is rooted and safestrap has been installed. I didn't get around to installing a custom ROM though so im still on stock ROM. Been noticing some random issues today and cant pinpoint why. First I am unable to turn on WIFI, was able to yesterday but now it just stays grey. I randomly lose my data connection (well it has a circle with a line through it) and it randomly just pops back on to 4g. I was playing on the phone one time and no SIM error came up but then went away. Power saving mode turned itself on randomly when i have over half battery. Lots of random things happening...
Now i did lose some data and have been trying to recover it this past week using this thread http://forum.xda-developers.com/gal...e-internal-memory-data-recovery-yes-t1994705/
I didn't make it far though because when i try to launch ADB Shell it gives me a permission error.
So that is another thing on the list, it is no longer prompting me to give root access to things. I also noticed that when i power on the phone, it no longer shows Samsung with a lock like it did ever since i rooted it. It now shows Samsung Galaxy S4...I Guess i may have lost root? I downloaded root checker and it says i still have it. Anyway its just so confusing, is it time to blow everything out and go back to stock MK2 and start over? What do you guys think? Thanks!
If you don't mind, I'd say Odin to stock would be your first troubleshooting step.
Don't forget, internal SD gets erased when you Odin to stock.
Sent from my SGH-I337 using XDA Premium 4 mobile app
guut13 said:
If you don't mind, I'd say Odin to stock would be your first troubleshooting step.
Don't forget, internal SD gets erased when you Odin to stock.
Sent from my SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Think so huh? I was thinking so...and yeah i know it erases internal memory, ill pull everything off before that and titanium backup apps and blah blah..
What i'd like to know is does Odin to stock blow EVERYTHING out including root and safe strap to where i would have to do that all over again? and i assume there is an Odin to stock for MK2? because i do not want the new update...
jermo said:
Think so huh? I was thinking so...and yeah i know it erases internal memory, ill pull everything off before that and titanium backup apps and blah blah..
What i'd like to know is does Odin to stock blow EVERYTHING out including root and safe strap to where i would have to do that all over again? and i assume there is an Odin to stock for MK2? because i do not want the new update...
Click to expand...
Click to collapse
I think Odin to stock is easier than troubleshooting every issue that you are having. Especially considering you already tried fixing one of them.
Yes. Odin wipes the slate clean. You'd have to root and install safestrap again. In case you don't have it.
mk2 odin... http://forum.xda-developers.com/showthread.php?t=2621279
root for mk2... http://forum.xda-developers.com/showthread.php?t=2565758
guut13 said:
I think Odin to stock is easier than troubleshooting every issue that you are having. Especially considering you already tried fixing one of them.
Yes. Odin wipes the slate clean. You'd have to root and install safestrap again. In case you don't have it.
mk2 odin... http://forum.xda-developers.com/showthread.php?t=2621279
root for mk2... http://forum.xda-developers.com/showthread.php?t=2565758
Click to expand...
Click to collapse
thanks brother! running through the long ridiculous process now
I see you have started the process... But wouldn't doing a FDR first be a simpler first effort? You would still have to restore root and data and apps, but it would be a bit easier and probably fix the problem. Just a thought. Hope all worked out!

Categories

Resources