I need Major help with my phone. So here's the run down.
Starting on a Tuesday my phone started acting funny, it would get to the AT&T logo and stop, but then if I removed the battery and hold down the power button for roughly 20 seconds and start it up it would come on without any problems that I could see. Through the week it got worse, and by that I mean that it would restart on it's own, randomly. By that Sunday pulling the battery and holding the power button no longer did anything and from what I understand it is stuck in a boot loop.
I should have started by asking all of you, but unfortunately for me I tried fixing it myself by searching for the answers.
This is where my phone sits. It was rooted, but there is no back up. I can get to the Android system recovery. I foolishly did a reset and cleared my phone (I have all of my info and pics backed up so I'm not worried about that). My computer does not recognize my phone unless I go into the ADB setting in recovery mode and as far as I can tell the computer just knows that something is connected through USB but can't quite tell what it is. Kies has been installed on said computer recently so I have the newest Samsung drivers. I have a 32 gb sd card for my phone if that helps any. I forgot to mention that my phone is running Version 4.3 of the S4 software.
I am a total noob when it comes to these types of problems so please help me.
Do you know what firmware version you're on? Did you do a factory reset in recovery? Kies is junk you're probably going to have to use Odin. But even that may not work based on your description of the problems.
Sent from my Nexus 5 using XDA Free mobile app
Re:
jd1639 said:
Do you know what firmware version you're on? Did you do a factory reset in recovery? Kies is junk you're probably going to have to use Odin. But even that may not work based on your description of the problems.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I am running Version 4.3. I only installed Kies to make sure I had the right driver, but you're right, Odin doesn't see my phone. I did do a factory reset in recovery, hopefully I didn't completely screw myself.
Bulk like Hulk said:
I am running Version 4.3. I only installed Kies to make sure I had the right driver, but you're right, Odin doesn't see my phone. I did do a factory reset in recovery, hopefully I didn't completely screw myself.
Click to expand...
Click to collapse
If Odin the mk2 tar file, see the all in one from here
http://forum.xda-developers.com/showthread.php?p=49687770
What Windows os version are you using? Google 15 second adb install xda and try those drivers.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
If Odin the mk2 tar file, see the all in one from here
http://forum.xda-developers.com/showthread.php?p=49687770
What Windows os version are you using? Google 15 second adb install xda and try those drivers.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I'm running Windows 7. I'll try that when I get home. I'll let you know what happens.
jd1639 said:
If Odin the mk2 tar file, see the all in one from here
http://forum.xda-developers.com/showthread.php?p=49687770
What Windows os version are you using? Google 15 second adb install xda and try those drivers.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Sorry I haven't logged in for a while. This worked very well, thank you.:good:
Related
Hello All,
I am quite new to the world of Android, but have searched and read up for multiple days on this site before finally posting my issue.
I have a GS4 that had been running stock with the MF3 OTA update. I finally decided to root and install safestrap to mess with a few custom roms. Everything went well. I was able to create a Rom Slot and load a custom rom for testing whilst keeping my stock in original form. NO issues what so ever. I used the Wicked Rom.... Eventually I decided that I would delete Rom Slot 1 and go back to stock. I followed directions to the T, deleted the slot and selected to boot from Stock. NO GO. This is where the horror begins:
Now, the phone boots up but I see the Samsung Galaxy S4 logo and it stays there...does not go back. I no longer see the SafeStrap recovery screen when booting up. --- I cannot even get into recovery on the phone any longer: it says recovery booting in blue and stays there.
I am able to get into Download mode to re-flash - but naturally none of the stock firmware files are loadable via Odin due to an error I keep getting NAND Flash! (Fail).
I finally decided to drive to Best Buy and asked the guy to flash my phone to stock there. He put the phone in download mode and used their multiflash tool which did not detect the phone and thus he could not move forward. The laptop did detect the phone at best buy, but their software did not and thus flashing did not occur.
I am looking for any and all advice to get this phone running without having to return it to Samsung....please and thanks in advance.
My apologies if my search did not yield a positive result and there is something out there....
Well There is no way to flash with Odin while on MF3, so that effort is completely fruitless at this time. Did the guy try a different USB port, cord or even restarting the computer he was using?
Can you get into your recovery to do a factory reset?
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Best buy should be able to do it. I remember reading somewhere that someone had to go to 3 different stores before they found someone smart enough to do it.. Lol
Sent from my SGH-I337 using XDA Premium HD app
I cannot get into recovery at all, it just says recovery booting and sits there....recovery booting is displayed at the top left of the screen in blue.
The guy did not try a different port or reboot. When he plugged the phone in, in download mode, the computer did recognize the phone but his Samsung software did not.
graydiggy said:
Well There is no way to flash with Odin while on MF3, so that effort is completely fruitless at this time. Did the guy try a different USB port, cord or even restarting the computer he was using?
Can you get into your recovery to do a factory reset?
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well he is an idiot for not troubleshooting his system. I have had the same exact thing happen with multiple different computers and phones. The computer detects the device correctly, but the program I needed to use would not. More often than anything a quick changing of ports or a reboot of the computer fixed it. I have had to completely wipe out the drivers a few times and reinstall them to get it to work. 9 times out of ten, it is not the phone that is the culprit, it is something else before the phone.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
FIXED
Well it seems the guy at my best buy was a TOOL! I took the phone in again today, had the battery pulled before I arrived - put it in download mode for him. Told him that Samsung tech support said he should reboot his pc. He did. Voila, reflashed to stock. Thank goodness....thank you guys for the advice.
Apply cold water directly to burned area.
Who's awesome?
ME!
Anyways, glad you are back up.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
I was updating my mdl s4 to a new build and flashed a rom for t0ltetmo, a T-Mobile note, by accident. I believe it updated the bootloader but not totally sure.
This is the error I get from TWRP when trying to flash a backup:
twrp E: unable ti mount ' /system'
If I go back to stock using kies can I then root with casual? Or will kies change my bootloader to something undesirable (mk1, nb1, etc.)
Any help would be greatly appreciated.
Have you tried flashing the correct firmware in Odin? You may have bricked your device, but it's a good sign you can still get into twrp.
Sent from my Nexus 5
No haven't tried Odin. I only have a Mac, need to borrow a friends PC. Don't think it's bricked. I believe it has the note 2 bootloader, and that's why TWRP isn't flashing the backup
numbere said:
No haven't tried Odin. I only have a Mac, need to borrow a friends PC. Don't think it's bricked. I believe it has the note 2 bootloader, and that's why TWRP isn't flashing the backup
Click to expand...
Click to collapse
If odin doesnt work, check out mobiletechvideos.com they fixed my bricked S4.
numbere said:
No haven't tried Odin. I only have a Mac, need to borrow a friends PC. Don't think it's bricked. I believe it has the note 2 bootloader, and that's why TWRP isn't flashing the backup
Click to expand...
Click to collapse
You could try a Windows vm on the Mac
Sent from my Nexus 5
Will try running odin on windows vm. Do you know if I go back to stock using kies if the bootloader will update to something other than the original MDL?
numbere said:
Will try running odin on windows vm. Do you know if I go back to stock using kies if the bootloader will update to something other than the original MDL?
Click to expand...
Click to collapse
If you use kies it'll force the latest firmware. You want to use Odin.
Sent from my Nexus 5
jd1639 said:
If you use kies it'll force the latest firmware. You want to use Odin.
Sent from my Nexus 5
Click to expand...
Click to collapse
Thanks for all the support! That was a scary situation.
Got Odin to run on parallels. Before using Odin I gave twrp one last try. Factory reset and then flashed a rom I tried previously, but this time without the gapps. Success! Got very lucky on this mistake.
Word to the wise double check your rom before flashing.
numbere said:
Thanks for all the support! That was a scary situation.
Got Odin to run on parallels. Before using Odin I gave twrp one last try. Factory reset and then flashed a rom I tried previously, but this time without the gapps. Success! Got very lucky on this mistake.
Word to the wise double check your rom before flashing.
Click to expand...
Click to collapse
Glad you got it working. It may have been a bad download of gapps.
Sent from my Nexus 5
No I definitely flashed a rom for the note 2.
Makes me think it's a sign that the software in our community is becoming more stable. Meaning that one can flash the incorrect ROM and potentially not destroy their device.
Sent from my SGH-I337 using XDA Premium 4 mobile app
numbere said:
No I definitely flashed a rom for the note 2.
Makes me think it's a sign that the software in our community is becoming more stable. Meaning that one can flash the incorrect ROM and potentially not destroy their device.
Sent from my SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No, you got lucky. The partitions are different for different devices and that's what will get you. I.e.flash a boot img where system is supposed to be and you'll be hard bricked
Sent from my Nexus 5
Wow, what a coincidence.
I had a similar issue over the last couple of days.
Here: http://forum.xda-developers.com/showthread.php?t=2701379
I used Odin in VMWare Fusion and it would not work at all, except to flash bootloaders and kernels. I finally got it to work through using heimdall using this thread: http://forum.xda-developers.com/showthread.php?t=2374441
So I've had this problem for a while and I think at one point I knew what the issue was, but things came up and I guess I lost my place. I have a GS4 running 4.3 on AT&T, but if I recall correctly it took a long time (longer than it was supposed to in US) for even that update to become available to me. I'm not sure if this phone is set as a different country or something, but I seem to think that had something to do with it when I checked last time. Now when I check for updates, it does say I have an available update (KitKat?) but fails when attempting to update. Download is successful, but install is not. Baseband is I337ucuemk2 if that helps anything. Any help here would be appreciated, thanks.
Install is failing as some of the files it is trying to update has been modified. You would have to be on stock for the update to work.
Remember that there is no direct root method for KitKat yet.
http://forum.xda-developers.com/showthread.php?t=2616221 for more info
Sent from my GT-I9505 using Tapatalk
jmjoyas said:
Install is failing as some of the files it is trying to update has been modified. You would have to be on stock for the update to work.
Remember that there is no direct root method for KitKat yet.
http://forum.xda-developers.com/showthread.php?t=2616221 for more info
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
I'm actually not rooted, already stock and still having errors still...any idea why that would be?
Anyone have any advice?
Anyone have any advice?
Click to expand...
Click to collapse
Have you changed any system files and do you have xposed running? They'll break the ota.
Edit, I should have read closer. I think there is an update.zip file you could flash in the general forum. I'll look and see if I can find it.
See post 2 http://forum.xda-developers.com/showthread.php?p=50667360
Sent from my Nexus 5
jd1639 said:
Have you changed any system files and do you have xposed running? They'll break the ota.
Edit, I should have read closer. I think there is an update.zip file you could flash in the general forum. I'll look and see if I can find it.
See post 2 http://forum.xda-developers.com/showthread.php?p=50667360
Sent from my Nexus 5
Click to expand...
Click to collapse
Thanks for the link, so I should just flash the md5 with Odin? Appreciate the help.
Imnice777 said:
Thanks for the link, so I should just flash the md5 with Odin? Appreciate the help.
Click to expand...
Click to collapse
No, flash the update.zip in the stock recovery
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
No, flash the update.zip in the stock recovery
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Ok cool, thanks again...however now another issue. I've tried several times, I can not boot into recovery. Any time I try to the phone just goes black until I let go and then reboots. Even if I get the blue print in the top left, the phone does not boot into recovery. Any idea why this would be?
Imnice777 said:
Ok cool, thanks again...however now another issue. I've tried several times, I can not boot into recovery. Any time I try to the phone just goes black until I let go and then reboots. Even if I get the blue print in the top left, the phone does not boot into recovery. Any idea why this would be?
Click to expand...
Click to collapse
If you can get into download mode you may be better off flashing the md5 and Odin. Don't know why you can't get into recovery
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
If you can get into download mode you may be better off flashing the md5 and Odin. Don't know why you can't get into recovery
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Me either, guess I'd just flash normally like I would a rom? Or would an update be different. I haven't done this in a while.
Imnice777 said:
Me either, guess I'd just flash normally like I would a rom? Or would an update be different. I haven't done this in a while.
Click to expand...
Click to collapse
If you flash the tar in Odin it's going to wipe your device so backup what you can. You'll need to download the tar file to your pc and download Odin to it too if you don't already have it. You run Odin from the pc
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
If you flash the tar in Odin it's going to wipe your device so backup what you can. You'll need to download the tar file to your pc and download Odin to it too if you don't already have it. You run Odin from the pc
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Ok so I finally got into recovery, but am I supposed to rename the file or anything? It keeps telling me:
"-- Verify the file type of MD5, Before Install /sdcard ...
-- Install /sdcard"
Imnice777 said:
Ok so I finally got into recovery, but am I supposed to rename the file or anything? It keeps telling me:
"-- Verify the file type of MD5, Before Install /sdcard ...
-- Install /sdcard"
Click to expand...
Click to collapse
Anyone ever see that error before?
Imnice777 said:
Anyone ever see that error before?
Click to expand...
Click to collapse
Are you trying to flash the update.zip? I'd re-download it. It could be a bad download
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Are you trying to flash the update.zip? I'd re-download it. It could be a bad download
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
So... pretty unhappy. Downloaded the update.zip and flashed in stock recovery, it wiped my whole phone and still didn't update. I saw a couple error messages appear as it was "updating" so now I'm still on old firmware and lost everything on my phone. Luckily I did a Kies backup but still pretty ridiculous. I still lose all save data from apps and all convenience that there was from using my phone for as long as I did. Just wanted to update, shouldn't be this big of a mess. Not sure what to do next.
Imnice777 said:
So... pretty unhappy. Downloaded the update.zip and flashed in stock recovery, it wiped my whole phone and still didn't update. I saw a couple error messages appear as it was "updating" so now I'm still on old firmware and lost everything on my phone. Luckily I did a Kies backup but still pretty ridiculous. I still lose all save data from apps and all convenience that there was from using my phone for as long as I did. Just wanted to update, shouldn't be this big of a mess. Not sure what to do next.
Click to expand...
Click to collapse
Well that sucks. No idea how it works wipe you're device. It shouldn't touch the userdata. If it's truly wiped I'd Odin the nb1 tar at this point. Get it updated and start over
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Well that sucks. No idea how it works wipe you're device. It shouldn't touch the userdata. If it's truly wiped I'd Odin the nb1 tar at this point. Get it updated and start over
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
That's what I did and I'm finally updated, but pretty disappointed that it took all that just for an update. Hopefully things like that don't continue in future updates...
[Q] Help stuck on "System Software not authrized by AT&T has been found on your phone
Well as the title says thats exactly what happened. It happened when I booted to recovery on Rashr recovery tools. Mistake on my part. I also know that there are similar threads, but I've already tried them out but they don't work for me. So I thought this would be the best way. The situation is well... its stuck on that error message. I tried to factory reset with ODIN but ODIN never detects my phone when I plug it in. I already tried taking the battery out and putting it back in. Then i tried Kies, but no luck there either since I can't find the serial number on the back of the phone sticker nor on the box of the phone. Does this mean my phone is dead?
Odin will work. You just need to get it to recognize your device. You have a usb driver issue. You need to install the court drivers. Kies should have done that but it can get in the way of Odin. Uninstall kies but keep the drivers and try Odin again.
Sent from my Nexus 5 using XDA Free mobile app
Okay I uninstalled kies, and updated my drivers to 1.5.45 on the Samsung website, but Odin still doesn't detect it. I feel like I'm missing something.
Psysora said:
Okay I uninstalled kies, and updated my drivers to 1.5.45 on the Samsung website, but Odin still doesn't detect it. I feel like I'm missing something.
Click to expand...
Click to collapse
Are you using Windows 8? You need to allow it to use unsigned drivers. Google how to do that if you do
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Are you using Windows 8? You need to allow it to use unsigned drivers. Google how to do that if you do
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
No, I'm on Windows 7 Home Premium.
Psysora said:
No, I'm on Windows 7 Home Premium.
Click to expand...
Click to collapse
With your device plugged into the pc, go to device manager. There's probably an exclamation mark on one of the usbs. That's the one having the issues. Right click on it and up date the driver. Go to where it say let me pick from a list on the computer. Pick the Samsung adb android interface, or something along those lines.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
With your device plugged into the pc, go to device manager. There's probably an exclamation mark on one of the usbs. That's the one having the issues. Right click on it and up date the driver. Go to where it say let me pick from a list on the computer. Pick the Samsung adb android interface, or something along those lines.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks a lot for the help, but oddly enough when I was about to try your idea i entered download mode to install a custom os. Of course
I didn't need to not I restarted my phone, and VIOLIA it works. Seriously what a turn of events. It now works perfectly. But, seriously thanks man, if that didn't happen just now I know for sure you would've helped me out and my phone would work. This was really just a shortcut if you think about it. Either way thanks a lot you were a great help.
Psysora said:
Thanks a lot for the help, but oddly enough when I was about to try your idea i entered download mode to install a custom os. Of course
I didn't need to not I restarted my phone, and VIOLIA it works. Seriously what a turn of events. It now works perfectly. But, seriously thanks man, if that didn't happen just now I know for sure you would've helped me out and my phone would work. This was really just a shortcut if you think about it. Either way thanks a lot you were a great help.
Click to expand...
Click to collapse
No problem, just glad it's working for you
Sent from my Nexus 5 using XDA Free mobile app
Bonehead move I know. Now I need some help to fix. I flashed a stock 5.0 ROM and everything was working fine. Got the 5.0.1 prompt so I flashed a stock recovery (4.4.4 hence my problem). Of course the update wouldn't flash. Now to complicate things all of a sudden my PC won't detect my Nexus 4. It detects my wife's Nexus 4 fine so I'm thinking not a cable or driver problem. Ive tried multiple cables and reinstalled drivers with no luck. So now I need to root and or install custom recovery without a PC. Any ideas?
icekold1694 said:
Bonehead move I know. Now I need some help to fix. I flashed a stock 5.0 ROM and everything was working fine. Got the 5.0.1 prompt so I flashed a stock recovery (4.4.4 hence my problem). Of course the update wouldn't flash. Now to complicate things all of a sudden my PC won't detect my Nexus 4. It detects my wife's Nexus 4 fine so I'm thinking not a cable or driver problem. Ive tried multiple cables and reinstalled drivers with no luck. So now I need to root and or install custom recovery without a PC. Any ideas?
Click to expand...
Click to collapse
You're going to need to get your pc to recognize your device. When booted into the bootloader and your device connected to the pc look in device manager. What does it show?
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
You're going to need to get your pc to recognize your device. When booted into the bootloader and your device connected to the pc look in device manager. What does it show?
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
It doesn't show anything. Its as if it isn't connected at all. I've tried from the bootloader and recovery screens and also rebooted both phone and pc. Still shows nothing in device manager. Phone shows charging but no mtp notification or anything that it is connected. As soon as I plug our other nexus 4 in the pc recognizes it immediately.
icekold1694 said:
It doesn't show anything. Its as if it isn't connected at all. I've tried from the bootloader and recovery screens and also rebooted both phone and pc. Still shows nothing in device manager. Phone shows charging but no mtp notification or anything that it is connected. As soon as I plug our other nexus 4 in the pc recognizes it immediately.
Click to expand...
Click to collapse
Is your device still rooted? If so you can flash the stock recovery image file from 5.0 in flashify
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Is your device still rooted? If so you can flash the stock recovery image file from 5.0 in flashify
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
No I lost root when I flashed the 5.0 stock rom.
icekold1694 said:
No I lost root when I flashed the 5.0 stock rom.
Click to expand...
Click to collapse
I would try deleting your usb drivers on the pc, rebooting and then trying your device again. Flashing the 4.4.4 recovery should not have done anything to mess up your device
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
I would try deleting your usb drivers on the pc, rebooting and then trying your device again. Flashing the 4.4.4 recovery should not have done anything to mess up your device
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
OK I will try that again and post results. Another possible problem I noticed is in root explorer I have a directory of emulated/0 I don't remember having before.
icekold1694 said:
OK I will try that again and post results. Another possible problem I noticed is in root explorer I have a directory of emulated/0 I don't remember having before.
Click to expand...
Click to collapse
I'm sure that directory was always there. It's a normal directory
Sent from my Nexus 9 using XDA Free mobile app
I uninstalled/reinstalled drivers and still no go. Detects the wifes nexus 4 but not mine. Guess I'm screwed.
icekold1694 said:
I uninstalled/reinstalled drivers and still no go. Detects the wifes nexus 4 but not mine. Guess I'm screwed.
Click to expand...
Click to collapse
To root your device use towelroot from your device. Although I don't know what you're going to do with root. Also, can you get the device detected by your pc when you're booted into recovery or the device?
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
To root your device use towelroot from your device. Although I don't know what you're going to do with root. Also, can you get the device detected by your pc when you're booted into recovery or the device?
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Towelroot wouldn't work. Says device isn't supported. Maybe it will get updated to work on lollipop. If I could obtain root I can flash custom recovery and start with a fresh install. Just have to find a way to do it with an app