Recently I wanted to unroot my Galaxy S4 ATT I337 and return back to Stock. It hasn't been my first time doing this, so I knew sort of what I was doing. I used Odin v3.10 and flashed an NB1 tar file and it worked fine, but as it finished flashing it said the device had been removed, showing up as a fail. So I disconnected the cable and tried again, and started getting error messages. I guess it might have had to do something with that, but now it keeps giving me a fail message every time I try to flash with Odin.
My phone now shows this firmware error on default and Odin seems to be failing every time. Is there anyway to fix this, or did I just completely screw this up?
I think you might have just screwed it up. If the device is removed in the middle of flashing with Odin that's not a good thing.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
I think you might have just screwed it up. If the device is removed in the middle of flashing with Odin that's not a good thing.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Well, I guess this is what I get for flashing so carelessly. I hope that this doesn't happen again.
Daze_ said:
Recently I wanted to unroot my Galaxy S4 ATT I337 and return back to Stock. It hasn't been my first time doing this, so I knew sort of what I was doing. I used Odin v3.10 and flashed an NB1 tar file and it worked fine, but as it finished flashing it said the device had been removed, showing up as a fail. So I disconnected the cable and tried again, and started getting error messages. I guess it might have had to do something with that, but now it keeps giving me a fail message every time I try to flash with Odin.
My phone now shows this firmware error on default and Odin seems to be failing every time. Is there anyway to fix this, or did I just completely screw this up?
Click to expand...
Click to collapse
Are you flashing the official odin?
Did you try the Kies emergency recovery?
Did you try a different cable and port?
I always recommend one directly connected to the motherboard.
BehrendsTech said:
Are you flashing the official odin?
Did you try the Kies emergency recovery?
Did you try a different cable and port?
I always recommend one directly connected to the motherboard.
Click to expand...
Click to collapse
I'm not too sure if I'm really flashing the official odin, but I've used it before and it's worked. I've tried the Kies emergency recovery but when I connected the cable to my phone it showed up as an unsupported device. I've tried two different cables but haven't changed the port.
Although after spending 4 hours searching the Internet for a fix, I actually found a website that showed me how to fix it. It worked well, and now I'm back to stock on my phone. The first few tries actually ended up as a fail, but for some reason the last attempt ended up with my phone actually turning on, and I was thankful to see the startup screen.
Daze_ said:
I'm not too sure if I'm really flashing the official odin, but I've used it before and it's worked. I've tried the Kies emergency recovery but when I connected the cable to my phone it showed up as an unsupported device. I've tried two different cables but haven't changed the port.
Although after spending 4 hours searching the Internet for a fix, I actually found a website that showed me how to fix it. It worked well, and now I'm back to stock on my phone. The first few tries actually ended up as a fail, but for some reason the last attempt ended up with my phone actually turning on, and I was thankful to see the startup screen.
Click to expand...
Click to collapse
Good to hear!
Related
Traded my Mega for a S4 today
Love it
I rooted it, installed TWRP. I have i337m from Rogers. All was well.
I downloaded a Google Edition 4.3 Rom and went into TWRP, Wiped Cache/Dalvik/Data, and Formatted Data
I then went back, installed the Rom.zip
Wiped cache/dalvik
Rebooted.
My phone now goes directly to Odin Mood. Seems as if something partition wise happened.
UPDATE:
I attempted to flash via odin everything back to stock, it made it 1/2 way and got an error. Now I can't do anything, phone just boots to the screen attached. Odin doesnt detect phone, Kies doesn't detect phone.
Am I screwed? I can't believe this, I want to cry. Never have I had issues like this before!!!
Which TWRP version
Did you do the "Format Data" button where you had to select "Yes". If so you lost everything
Get twrp 2.5.0.2 if you get the chance
I never used Odin, so not much help there
Also, I always wipe only Data/System/Caches 2x and have no issues. I do it before flashing any rom/version update etc
I know not much help here. But, maybe an idea on what went wrong--
Good Luck
Yes - Shoot
I see the issue. I was following the guide and it states to do this with CWM, I was thinking I was reading the instructions for TWRP. I had 2.6.3.0 (whatever the newest one is)
I'm downloading the firmware now - will try Odin
You gotta use Odin to restore the firmware, but you can't use kies if you're going custom. You can also use Philz recovery for that. That's what I had and it worked great. It's based off CWM and has touch.
agent929 said:
You gotta use Odin to restore the firmware, but you can't use kies if you're going custom. You can also use Philz recovery for that. That's what I had and it worked great. It's based off CWM and has touch.
Click to expand...
Click to collapse
When attempting to flash with Odin, I'm getting the following error. Any help?
Stuck here right now if anyone has a second.
Edit
Sent from my SAMSUNG-SM-N900A using Tapatalk 5
Got it from here
http://forum.xda-developers.com/showthread.php?t=2269304
Its the Virgin Mobile Canada 4.2.2 firmware from July
My phone is Rogers but is unlocked and I'm using it with Virgin. Can I flash the virgin file rather than Rogers to avoid all the Rogers bloat?
What is the Pit error I'm getting? Did I delete a partition or anything here?
Man that stupid format is a major pain. Won't do that again. I flipped back at the guide page and read the CWM instructions by error.
agent929 said:
I don't think you're using the right firmware. You should be doing the MDL firmware.
Sent from my SAMSUNG-SM-N900A using Tapatalk 5
Click to expand...
Click to collapse
Why would he put MDL on a Canadian phone?
scott14719 said:
Why would he put MDL on a Canadian phone?
Click to expand...
Click to collapse
Oh good gosh I'm very sorry I missed that part.
Sent from my SAMSUNG-SGH-I467 using Tapatalk 4
agent929 said:
Oh good gosh I'm very sorry I missed that part.
Sent from my SAMSUNG-SGH-I467 using Tapatalk 4
Click to expand...
Click to collapse
So I attempted to flash Via Odin 3.0.7 (rogers firmware) and about 1/2 way through something Error'd and now my phone will not do anything but load the following screen attached.
Download mode or recovery does not load. Kies does not detect it. I can't get Odin to detect it either.
Did I screw myself over?
So depressed over this. I just got the phone.
That screen is another form of download mode. If you plug it into Odin at this point will Odin recognize it?
jd1639 said:
That screen is another form of download mode. If you plug it into Odin at this point will Odin recognize it?
Click to expand...
Click to collapse
I'll try again tonight after work.
Last night I could no longer get ODIN to recognize the device.
bigystyle84 said:
I'll try again tonight after work.
Last night I could no longer get ODIN to recognize the device.
Click to expand...
Click to collapse
If you are on MF3, this has worked to get me out of that screen http://forum.xda-developers.com/showthread.php?t=2360859 there is always some risk with flashing anything from Odin, so read through the thread and make sure you are comfortable with it first...
I'm on AT&T U.S. but it worked for me. You should also be able to boot in download mode (with the phone off hold vol down and home, then press power until your phone vibrates and continue holding home and vol down until you see Download mode)...
I hope this helps.
dustyhughes said:
If you are on MF3, this has worked to get me out of that screen http://forum.xda-developers.com/showthread.php?t=2360859 there is always some risk with flashing anything from Odin, so read through the thread and make sure you are comfortable with it first...
I'm on AT&T U.S. but it worked for me. You should also be able to boot in download mode (with the phone off hold vol down and home, then press power until your phone vibrates and continue holding home and vol down until you see Download mode)...
I hope this helps.
Click to expand...
Click to collapse
I have a i337M Canadian phone
And as mentioned, phone will not go into Download mode. I've tried a dozen times to get it into the regular download mode as always, does not work. It just boots to this screenshot almost instantly after hitting the power button.
I've flashed with Odin a dozen times previously with S3 and Note 2 in the past, never any issues.
How could TWRP Format Data cause all this to happen?
I just had my previous phone stolen - I bought this phone yesterday and now this happens. What a great week.
jd1639 said:
That screen is another form of download mode. If you plug it into Odin at this point will Odin recognize it?
Click to expand...
Click to collapse
jd1639 is right, I think the first line of small text says Odin, if I remember correctly.
dustyhughes said:
jd1639 is right, I think the first line of small text says Odin, if I remember correctly.
Click to expand...
Click to collapse
I couldn't get Odin to detect the phone on this screen though.
Odin detected the phone fine when I could get the to regular download mode screen before. Now I can't get to this screen, only what's attached in the screenshot, and I couldn't get Odin to detect it any longer last night.
Can a cable cause this? I am not using the Cable that came with the phone - That wasn't included when I bought it. I'm using a Sony Cable from a Xperia T I used to own.
Why did the Odin flash fail to begin with?
With did Format Data in TWRP cause all this to happen?
bigystyle84 said:
I couldn't get Odin to detect the phone on this screen though.
Odin detected the phone fine when I could get the to regular download mode screen before. Now I can't get to this screen, only what's attached in the screenshot, and I couldn't get Odin to detect it any longer last night.
Can a cable cause this? I am not using the Cable that came with the phone - That wasn't included when I bought it. I'm using a Sony Cable from a Xperia T I used to own.
Why did the Odin flash fail to begin with?
With did Format Data in TWRP cause all this to happen?
Click to expand...
Click to collapse
It's very possible it's the cable. Odin is very finicky on the cable, usb ports, and even computer you use. It works great on my lap top but I can't get it to work on my pc. Do you know anyone who has an s4 and you could borrow their cable. If you can boot into download you are not bricked and can get Odin to fix your phone. It may just take some trial and error. I've also had Odin fail a number of times and then decide to finally work for whatever reason so keep working at it.
jd1639 said:
It's very possible it's the cable. Odin is very finicky on the cable, usb ports, and even computer you use. It works great on my lap top but I can't get it to work on my pc. Do you know anyone who has an s4 and you could borrow their cable. If you can boot into download you are not bricked and can get Odin to fix your phone. It may just take some trial and error. I've also had Odin fail a number of times and then decide to finally work for whatever reason so keep working at it.
Click to expand...
Click to collapse
I'm going to get a Samsung Cable from a friend today and try it again when I get home.
jd1639 said:
It's very possible it's the cable. Odin is very finicky on the cable, usb ports, and even computer you use. It works great on my lap top but I can't get it to work on my pc. Do you know anyone who has an s4 and you could borrow their cable. If you can boot into download you are not bricked and can get Odin to fix your phone. It may just take some trial and error. I've also had Odin fail a number of times and then decide to finally work for whatever reason so keep working at it.
Click to expand...
Click to collapse
Here's some more thoughts:
I've always used firmware from sammobile.com
I've had best luck with odin ver 1.85
One other, use the usb ports in the back of your computer, not the front and no usb hub.
jd1639 said:
Here's some more thoughts:
I've always used firmware from sammobile.com
I've had best luck with odin ver 1.85
Click to expand...
Click to collapse
Cool Thanks
I downloaded the firmware from SamMobile - the latest Rogers firmware.
I will try 1.85
I have searched and searched and cannot find any fix for my issue hopefully I can get the help here like always.
Last night I flashed ktoonz kernel like I have a thousand times before and it failed in TWRP recovery, I thought nothing of it, hit reboot, and am now at a brick wall. My Gs4 acts like the Gs2 with a stuck power button, upon powering it on, it goes straight into a loop vibrating every few seconds over and over, I can't get into recovery mode and for that matter can't even get the the initial Samsung splash screen to pop up. The only thing I can do with the phone is boot into download mode, I tried restoring several times with Heimdall on my Mac and always failed when the system reached 100%, it wouldn't move past that point. I have also just finished flashing it with Odin on a friends Windows laptop which completed successfully each time but the phone is still doing the same thing. I need help, I can't afford a replacement right now and am just a little desperate!
re: official stock firmwares
lstat said:
I have searched and searched and cannot find any fix for my issue hopefully I can get the help here like always.
Last night I flashed ktoonz kernel like I have a thousand times before and it failed in TWRP recovery, I thought nothing of it, hit reboot, and am now at a brick wall. My Gs4 acts like the Gs2 with a stuck power button, upon powering it on, it goes straight into a loop vibrating every few seconds over and over, I can't get into recovery mode and for that matter can't even get the the initial Samsung splash screen to pop up. The only thing I can do with the phone is boot into download mode, I tried restoring several times with Heimdall on my Mac and always failed when the system reached 100%, it wouldn't move past that point. I have also just finished flashing it with Odin on a friends Windows laptop which completed successfully each time but the phone is still doing the same thing. I need help, I can't afford a replacement right now and am just a little desperate!
Click to expand...
Click to collapse
Odin and Heimdall don't have any options to RESTORE anything.
Both those utilities can only do one thing, they can flash firmware
TAR files. (and any other valid TAR files)
My advice to you is to simply go to SamMobile.com and download
the specific odin flash firmware for your phone model and country.
Here is an example of what you will find at SamMobile: http://www.sammobile.com/firmwares/2/
Good luck!
Misterjunky said:
Odin and Heimdall don't have any options to RESTORE anything.
Both those utilities can only do one thing, they can flash firmware
TAR files. (and any other valid TAR files)
My advice to you is to simply go to SamMobile.com and download
the specific odin flash firmware for your phone model and country.
Here is an example of what you will find at SamMobile: http://www.sammobile.com/firmwares/2/
Good luck!
Click to expand...
Click to collapse
I understand what they do, that is why I used them. I downloaded both the amdl and amdb firmware from SamMabile.com and neither of them worked, it still goes through the same process.
lstat said:
I understand what they do, that is why I used them. I downloaded both the amdl and amdb firmware from SamMabile.com and neither of them worked, it still goes through the same process.
Click to expand...
Click to collapse
I would keep trying Odin. Try different usb ports, don't use hub. Make sure you have the original usb cord. If it can get into download mode there's hope.
I tried flashing through Odin a few more times today with no luck, even tried to repartition with a .pit file and that failed. I think my phone is just screwed.
test
testtesttesttesttesttesttesttesttesttesttesttest
Actually, I had the same exact problem when I flashed KTkernel to my S4 a while back. At first I tried Odin, and it said flash was successful, but still no recovery mode or any screen.
I actually used KIES, either firmware recovery or firmware update. And that solved it. The phone boot up normally after KIES.
Kevinnme said:
Actually, I had the same exact problem when I flashed KTkernel to my S4 a while back. At first I tried Odin, and it said flash was successful, but still no recovery mode or any screen.
I actually used KIES, either firmware recovery or firmware update. And that solved it. The phone boot up normally after KIES.
Click to expand...
Click to collapse
How exactly were you able to do this? Kies doesn't recognize the phone in download mode.
Make sure your KIES is up to date, and it should recognize the phone.
Here is a thread that may be helpful,
http://forum.xda-developers.com/showthread.php?t=2261153
and
http://www.samsung.com/us/support/faq/FAQ00029015/29183
Kevinnme said:
Make sure your KIES is up to date, and it should recognize the phone.
Here is a thread that may be helpful,
http://forum.xda-developers.com/showthread.php?t=2261153
and
http://www.samsung.com/us/support/faq/FAQ00029015/29183
Click to expand...
Click to collapse
Unfortunately this doesn't seem to be working for me, either. Kies is not recognizing my phone in emergency firmware recovery on OS X or Windows.
See if you can find help making kies to recognize your device. I think you should be able to since you used Odin.
Have you tried to Odin on a windows instead of a mac.
Sent from my GT-I9505 using XDA Premium 4 mobile app
Reinaldo33897 said:
Have you tried to Odin on a windows instead of a mac.
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes, on both a Windows box and through Parallels, neither have worked.
lstat said:
Yes, on both a Windows box and through Parallels, neither have worked.
Click to expand...
Click to collapse
Same problem. I tried flashing Ktweaker, install failed, and now the phone just vibrates every few seconds.
I have tried installing the PIT file, as well as the original firmware. Trying to reinstall the recovery ends with a "Fail" message.
Totally stumped.
I scheduled a repair with Samsung. Mines boxed up ready to go, just haven't sent it off yet. I gave up trying to fix it and went back to my iphone.
Sent from my iPhone using Tapatalk
lstat said:
I scheduled a repair with Samsung. Mines boxed up ready to go, just haven't sent it off yet. I gave up trying to fix it and went back to my iphone.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Did the same thing
I’m having a problem flashing via ODIN or anything else… I have a Sprint SPH-L720 MF9 everything. I am using a mac with VMware fusion and windows xp and 7. I have also tried everything below on a native windows 7 machine.
I started with MF9 and had rooted and ran TriForce 3.1 for a long time. Everything was working fine, so I never updated. I didn’t want to get tangled up in the knox mess. I decided to go ahead and update last night and I went through using unknownforce’s instructions and downloads. I tried to flash NAE modem only, but odin failed. Now it won’t boot, just goes to the download mode page. (the one that says to recover using kies) it also allows me to enter download mode (power+volume \/)
I’ve tried:
Odin full MF9 firmware (as my phone started with this, and I’ve never flashed anything knox)
Odin MF9/NAE modem
Full MF9 odin restore (there’s a thread that has the whole exe that does everything)
All of these with adding a pit file.
Every time, odin fails. It seems to be failing at the modem.bin, but who knows. It doesn't seem to transfer for very long, perhaps 2 minutes.
I’ve gotten to the “screw it” stage and loaded Kies (tried both mac and windows xp and 7) and tried to do a recovery there. It won’t recognize the phone right now though. It just sits there, basically. EDIT: It sees the phone and sits there trying to connect, but eventually times out.
Odin can see the phone and attempts to flash, but again, runs into the problems above. I can’t download the firmware through kies due to being a sprint phone and no S/N. I'd prefer to avoid knox, but if I have to, I'm fine with going that route. If I'm not out of warranty yet, it will be soon. As long as that's the only big ramification, I don't really care.
Anyone have any ideas? Need more information?
Update: I was able to get part of the NAE update to work. The Knox bootloader. That's it. It's not tripped, but it's now showing in download mode. Still can't get any further, however.
Sent from my Nexus 7 using Tapatalk
Maybe try this: http://forum.xda-developers.com/showthread.php?t=2277480. I always use Run as Administrator for Odin and used 3.07 Odin to flash MF9 and NAE. If you try, follow every step to the T. Sorry if I didn't help.
.
2WhiteWolves said:
Maybe try this: http://forum.xda-developers.com/showthread.php?t=2277480. I always use Run as Administrator for Odin and used 3.07 Odin to flash MF9 and NAE. If you try, follow every step to the T. Sorry if I didn't help.
.
Click to expand...
Click to collapse
The linked page for unknownforce is actually the page I was using to update the first time. The problem is, odin fails no matter what I do... I appreciate the suggestion though.
Try different usb cable and usb port. Someone mentioned to uninstall kies it will cause issues with odin. You can try that or uninstall drivers an install it again. Or try different versions of odin. I use 1.85 and some versions thats starts with 3. Since you already flashed NAE tar. You can not flash any version before NAE. Hope it helps.
Sent from my Nexus 5 using Tapatalk
Called sprint who transferred me to Samsung, they couldn't talk me through it. The phone wouldn't show up in kies for them. They did mention, to my great relief, to steer clear of the sprint store. They instructed me to head to best buy and go to the Samsung store inside. Apparently they supposedly have a tool to reflash the phone there... We'll see later today. I'll post back with my results. I have 28 days left in my warranty. Just in time, it seems.
I didn't try using 1.85, but had tried 3.07 and 09. Kies came later. I originally used the drivers recommended in other threads. I only have two ports on my main machine, but did try another machine without success. Cords as well. Actually I did a backup with one of the cords right before trying the flash. Who knows.
Now that the warranty is nearly gone and I'm surely knoxed now.. Is there anything I need to watch out for? Does it make it much different to flash or is it just the flag for my soon to be nonexistent warranty?
Sent from my Nexus 7 using Tapatalk
Update:I took the phone to Samsung inside Best Buy. They hooked it up to a laptop and got it working within 20 minutes. They flashed 4.4.2 onto the phone, and to my surprise, everything was as I left it, minus root, and with Sprint ID added. Somehow, through everything, my data partition was untouched. Even more interesting, all of my apps and everything work. I was on TriForce ROM 3.1... Only thing I've noticed is that my data connection isn't consistent. It will drop out, and stay out until I toggle airplane mode. Still says I have signal, and can make calls.. I think a full restore may be in order.
Moral of the story? The SWAS (Store Within A Store) Samsung is running in Best Buys is pretty decent. They took no time at all, in the grand scheme of things. Unfortunately, I wasn't able to see the software they used. He tried Kies at first, but moved on quickly.
I had no problem using QBKing77's guide to root my S3. I looked for the comparable thread when I got my S4.
I loaded up Odin but got an error saying there was no PIT partition. I put the phone into debug mode (not in the instructions?) and it seemed to work.
But then it failed half-way through. I was plugged into a USB port on the front of the computer.
Now I get the error "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I searched and found other threads for the S3 and other phones but would appreciate some help with the S4. Thanks.
Edit: are these the steps I need to take?
Edit #2: Uh, I guess those steps won't work since they will prompt me for a serial number and there doesn't seem to be a way to get that from a Galaxy S4 if it won't boot.
Help?
Does the phone boot into download mode? Have you tried flashing the stock firmware through ODIN?
nxtech3 said:
Does the phone boot into download mode? Have you tried flashing the stock firmware through ODIN?
Click to expand...
Click to collapse
When it boots, it goes straight to the error. If I hold volume down + Home, it *will* go into download mode.
I didn't know what to flash with ODIN.
After the fiasco with the attempted rooting, I didn't want to chance flashing the wrong thing.
Thanks for the reply.
Edit: Can someone post step-by-step directions on how to flash stock firmware through Odin? (Or the link to the thread that probably already exists)
Preferably with a link to the exact ROM/firmware that I need?
Dougmeister said:
When it boots, it goes straight to the error. If I hold volume down + Home, it *will* go into download mode.
I didn't know what to flash with ODIN.
After the fiasco with the attempted rooting, I didn't want to chance flashing the wrong thing.
Thanks for the reply.
Edit: Can someone post step-by-step directions on how to flash stock firmware through Odin? (Or the link to the thread that probably already exists)
Preferably with a link to the exact ROM/firmware that I need?
Click to expand...
Click to collapse
Look for CF-Auto-Root for jfltespr. That will get you rooted but will trip your Knox counter.
garwynn said:
Look for CF-Auto-Root for jfltespr. That will get you rooted but will trip your Knox counter.
Click to expand...
Click to collapse
I have this file already downloaded: CF-Auto-Root-jfltespr-jfltespr-sphl720
I started Odin 3.07 ("Run as administrator") and loaded the file in the PDA slot. I waited for "<OSM> Leave CS.." to appear in the "Message" box. I hooked up the Galaxy S4 but the COM port will not show up... trying different cables now... (it is plugged into the back of the computer...)
Dougmeister said:
I have this file already downloaded: CF-Auto-Root-jfltespr-jfltespr-sphl720
I guess that's it?
Click to expand...
Click to collapse
That's it. Make sure it's the current one and flash in PDA slot using Odin.
Will reboot, apply root, reboot back to stock and voila!
garwynn said:
That's it. Make sure it's the current one and flash in PDA slot using Odin.
Will reboot, apply root, reboot back to stock and voila!
Click to expand...
Click to collapse
I can't get ODIN to recognize the S4 via the USB slot ("ID:COM" port stays blank). I even re-installed the S4 drivers. Any ideas?
I've tried 3 different cables, all plugged into the back.
Dougmeister said:
I can't get ODIN to recognize the S4 via the USB slot ("ID:COM" port stays blank). I even re-installed the S4 drivers. Any ideas?
I've tried 3 different cables, all plugged into the back.
Click to expand...
Click to collapse
Not to sound silly but did you reboot into download mode?
garwynn said:
Not to sound silly but did you reboot into download mode?
Click to expand...
Click to collapse
Not a silly question at all. I've been known to do that
But no, this time I was in "download mode". For some reason, it finally worked with one of the cables using a front USB port. (?)
Thanks for everyone's help. Crisis averted.
Dougmeister said:
Not a silly question at all. I've been known to do that
But no, this time I was in "download mode". For some reason, it finally worked with one of the cables using a front USB port. (?)
Thanks for everyone's help. Crisis averted.
Click to expand...
Click to collapse
I've had dicey situations using download mode just like you've described on 2 different gs4's. I use heimdall, not odin, but same flakey results. The gs4's download mode appears to be very finicky about the quality of the usb cable and port. I never had any issue with download mode with identical hardware when I used to flash my gs2. So it's not you, it's the gs4. I finally got some reasonably reliable and consistent flashing results by using the usb ports on the back, and a high quality blackberry usb cable. In my case, the "bad" ports on the front are usb1.1, while the ports on the back are usb 2.0. So it seems to matter when flashing the gs4. So I would say avoid using usb 1.1 ports if your computer is old enough to have them.
OK guys, I'm begging for your help. I just traded my HTC One M7 in for a Galaxy S 5 and immediately rooted it. Well, I forgot to unlock the bootloader, so when I tried to flash TWRP using Flashify, I rebooted into the dread yellow ! triangle with the words "System software not authorized by AT&T has been found on your phone. Please turn off your phone and go to the nearest AT&T."
After researching solutions, I downloaded the USB drivers and latest firmware as well as Odin v1.09. Well, I can't even get started fixing it because my computer doesn't recognize the phone, nor does Odin. I've tried re-downloading the drivers and Odin, but still nothing. The only thing I can think of is that the usb cable I'm using is not stock. But I'm at work and don't have access to the stock charger.
Anyone have any advice? Needless to say, I feel like a nimrod. I rooted my HTC One no problem, but then I followed all the directions then...
Chase88 said:
OK guys, I'm begging for your help. I just traded my HTC One M7 in for a Galaxy S 5 and immediately rooted it. Well, I forgot to unlock the bootloader, so when I tried to flash TWRP using Flashify, I rebooted into the dread yellow ! triangle with the words "System software not authorized by AT&T has been found on your phone. Please turn off your phone and go to the nearest AT&T."
After researching solutions, I downloaded the USB drivers and latest firmware as well as Odin v1.09. Well, I can't even get started fixing it because my computer doesn't recognize the phone, nor does Odin. I've tried re-downloading the drivers and Odin, but still nothing. The only thing I can think of is that the usb cable I'm using is not stock. But I'm at work and don't have access to the stock charger.
Anyone have any advice? Needless to say, I feel like a nimrod. I rooted my HTC One no problem, but then I followed all the directions then...
Click to expand...
Click to collapse
Pull the battery, wait 30 seconds and try to boot into downloadmode. If you can do that you can maybe flash a stock rom.
gee2012 said:
Pull the battery, wait 30 seconds and try to boot into downloadmode. If you can do that you can maybe flash a stock rom.
Click to expand...
Click to collapse
God bless you.
Chase88 said:
God bless you.
Click to expand...
Click to collapse
Glad it worked mate, don`t mess up again