I need some help getting an AT&T S4 back to stock. I tried rooting it and installing a custom ROM but things took a bad turn and now I'm stuck. The device is MK2 so I rooted the phone following the instructions in the ULTIMATE HOW-TO thread using Saferoot, then I used Safestrap to successfully install Recovery. Everything was good up to here. I tried to install a ROM that I later found out was unsupported onto the Stock slot in Safestrap. After realizing my mistakes I tried to put a supported ROM into Slot 1 on safestrap and that still failed. No matter what it will just boot loop. I tried fully wiping both slots and in the process lost my custom recovery.
Now I am to the point of just going back to stock, the phone is going to be sold anyways. I followed this thread http://forum.xda-developers.com/showthread.php?t=2261573
Downloaded ODIN and factory image but when I try to flash it with ODIN it comes up FAIL! within a few seconds. It gets as far as NAND Write Start!! then it fails out.
Please tell me I'm not hosed and bricked the device. I'm not new to this either, had several Galaxy phones for years but switch to Windows Phone a few months ago and am a little rusty with this stuff.
Any help is greatly appreciated.
Sympl3x said:
I need some help getting an AT&T S4 back to stock. I tried rooting it and installing a custom ROM but things took a bad turn and now I'm stuck. The device is MK2 so I rooted the phone following the instructions in the ULTIMATE HOW-TO thread using Saferoot, then I used Safestrap to successfully install Recovery. Everything was good up to here. I tried to install a ROM that I later found out was unsupported onto the Stock slot in Safestrap. After realizing my mistakes I tried to put a supported ROM into Slot 1 on safestrap and that still failed. No matter what it will just boot loop. I tried fully wiping both slots and in the process lost my custom recovery.
Now I am to the point of just going back to stock, the phone is going to be sold anyways. I followed this thread http://forum.xda-developers.com/showthread.php?t=2261573
Downloaded ODIN and factory image but when I try to flash it with ODIN it comes up FAIL! within a few seconds. It gets as far as NAND Write Start!! then it fails out.
Please tell me I'm not hosed and bricked the device. I'm not new to this either, had several Galaxy phones for years but switch to Windows Phone a few months ago and am a little rusty with this stuff.
Any help is greatly appreciated.
Click to expand...
Click to collapse
Why are you posting in the Verizon help forum for an AT&T S4?
I think you need to use this thread: http://forum.xda-developers.com/showthread.php?t=2621279
If your stock build ends with MK2, you need an Odin tar for your version that ends in MK2 (or later release) as well. Using an earlier build will fail.
Oishikatta said:
Why are you posting in the Verizon help forum for an AT&T S4?
I think you need to use this thread: http://forum.xda-developers.com/showthread.php?t=2621279
If your stock build ends with MK2, you need an Odin tar for your version that ends in MK2 (or later release) as well. Using an earlier build will fail.
Click to expand...
Click to collapse
Appologies, that's what I get for posting at 2AM. Thank you anyway for still helping me out. Downloaded the MK2 version and it is now flashing in ODIN.
Related
I'm desperately hoping that someone, somewhere can provide a stock firmware for the Bell SGH-I527M that includes knox. Maybe someone from sammobile is reading this and can post it there. I took the OTA update a week ago, then rooted the phone and flashed CWM recovery on it, no problem at all. Everything was running fine.
Yesterday, I thought I'd give the unofficial CM11 ROM a go, so I took a backup and tried flashing CM11 from CWM - failed. So I thought, "No problem, I'll just restore my backup I made ten minutes ago." That, too, failed. I had nothing to go back to since I was trying to do a super-clean flash of CM11 - wipe data/factory reset, format data, format sdcard, all the steps that I've taken a million times flashing different ROMs on different Samsung phones. So I effectively had no OS on the phone, just recovery.
Went to Sammobile and downloaded the only stock firmware they have available for this device for this carrier. Flashed through Odin and on reboot, got the "secure fail kernel - image size too large" error message. Also tried the emergency firmware recovery through Kies and got the same thing.
So basically, I'm completely stuck. The only thing I can get to boot up is download mode. Does anyone know if there is a different firmware I can flash through Odin to get this device up and running again? I'm given to understand that this has something to do with knox security. That since I took the OTA last week, it updated knox security, then when I flashed the stock firmware from sammobile, this is actually an older firmware that does not include knox. I'm hoping that someone has access to the newest stock firmware for this device for Bell with knox that I can flash through Odin to get back up and running.
Any help would be greatly appreciated.
Thanks in advance,
-GB
GladdBag said:
I'm desperately hoping that someone, somewhere can provide a stock firmware for the Bell SGH-I527M that includes knox. Maybe someone from sammobile is reading this and can post it there. I took the OTA update a week ago, then rooted the phone and flashed CWM recovery on it, no problem at all. Everything was running fine.
Yesterday, I thought I'd give the unofficial CM11 ROM a go, so I took a backup and tried flashing CM11 from CWM - failed. So I thought, "No problem, I'll just restore my backup I made ten minutes ago." That, too, failed. I had nothing to go back to since I was trying to do a super-clean flash of CM11 - wipe data/factory reset, format data, format sdcard, all the steps that I've taken a million times flashing different ROMs on different Samsung phones. So I effectively had no OS on the phone, just recovery.
Went to Sammobile and downloaded the only stock firmware they have available for this device for this carrier. Flashed through Odin and on reboot, got the "secure fail kernel - image size too large" error message. Also tried the emergency firmware recovery through Kies and got the same thing.
So basically, I'm completely stuck. The only thing I can get to boot up is download mode. Does anyone know if there is a different firmware I can flash through Odin to get this device up and running again? I'm given to understand that this has something to do with knox security. That since I took the OTA last week, it updated knox security, then when I flashed the stock firmware from sammobile, this is actually an older firmware that does not include knox. I'm hoping that someone has access to the newest stock firmware for this device for Bell with knox that I can flash through Odin to get back up and running.
Any help would be greatly appreciated.
Thanks in advance,
-GB
Click to expand...
Click to collapse
If someone with this new update and root could dump some images i could make an odin tar for yall.
GladdBag said:
I'm desperately hoping that someone, somewhere can provide a stock firmware for the Bell SGH-I527M that includes knox. Maybe someone from sammobile is reading this and can post it there. I took the OTA update a week ago, then rooted the phone and flashed CWM recovery on it, no problem at all. Everything was running fine.
Yesterday, I thought I'd give the unofficial CM11 ROM a go, so I took a backup and tried flashing CM11 from CWM - failed. So I thought, "No problem, I'll just restore my backup I made ten minutes ago." That, too, failed. I had nothing to go back to since I was trying to do a super-clean flash of CM11 - wipe data/factory reset, format data, format sdcard, all the steps that I've taken a million times flashing different ROMs on different Samsung phones. So I effectively had no OS on the phone, just recovery.
Went to Sammobile and downloaded the only stock firmware they have available for this device for this carrier. Flashed through Odin and on reboot, got the "secure fail kernel - image size too large" error message. Also tried the emergency firmware recovery through Kies and got the same thing.
So basically, I'm completely stuck. The only thing I can get to boot up is download mode. Does anyone know if there is a different firmware I can flash through Odin to get this device up and running again? I'm given to understand that this has something to do with knox security. That since I took the OTA last week, it updated knox security, then when I flashed the stock firmware from sammobile, this is actually an older firmware that does not include knox. I'm hoping that someone has access to the newest stock firmware for this device for Bell with knox that I can flash through Odin to get back up and running.
Any help would be greatly appreciated.
Thanks in advance,
-GB
Click to expand...
Click to collapse
im in the same boat lol....any luck bro?
Nubsta said:
im in the same boat lol....any luck bro?
Click to expand...
Click to collapse
See this thread:
http://forum.xda-developers.com/showthread.php?t=2461203
I am a bit of a noob but I have rooted my sprint note 3 which came out successful. I have rooted my galaxy s3 before in the past and flashed many roms without any issues.
Once I rooted my note 3 I ran the stock rom for a week and then decided to kick it up a notch and flashed the bonsai rom, which worked fine until i discovered the camera didn't work. Before I flashed the bonsai rom, I did a backup of the stock rom via cwm. Once I figured out the camera didn't work with the bonsai rom, I reset and wiped the data for my phone and tried to restore the stock rom which i figured it was a boo boo because I got stuck in a bootloop so I reflashed the bonsai rom back on my phone until I got back home to my pc. At that point, I decided to unroot and return the phone back to stock. I used odin and followed unrooting instructions to a tee and I had an official stock firmware, but odin failed and I think I may have soft bricked my phone. In a panic, I downloaded a "rooted stock" rom and flashed that...after a few bootloops, I updated my cwm recovery and superuser app...and my phone has been working fine every since (whew). I really want to unroot, then re-root and just run the stock rom without flashing any more custom roms, however I am afraid of bricking it again.
I have the stock official firmware N900PVPUBMJ4_N900PSPTBMJ4_N900PVPUBMJ4_HOME.tar.md 5 which to my understanding is android 4.3. I do understand that 4.4 is out. I was wondering is it ok to flash the 4.3 using odin to return my phone back to stock?? I've been spooked ever since my soft brick encounter. Any info will be helpful. Btw, sorry for the long story. I figured I should give all the details. That would help me get to the bottom of it all
Thanks in Advance!
LadyDroid81 said:
I am a bit of a noob but I have rooted my sprint note 3 which came out successful. I have rooted my galaxy s3 before in the past and flashed many roms without any issues.
Once I rooted my note 3 I ran the stock rom for a week and then decided to kick it up a notch and flashed the bonsai rom, which worked fine until i discovered the camera didn't work. Before I flashed the bonsai rom, I did a backup of the stock rom via cwm. Once I figured out the camera didn't work with the bonsai rom, I reset and wiped the data for my phone and tried to restore the stock rom which i figured it was a boo boo because I got stuck in a bootloop so I reflashed the bonsai rom back on my phone until I got back home to my pc. At that point, I decided to unroot and return the phone back to stock. I used odin and followed unrooting instructions to a tee and I had an official stock firmware, but odin failed and I think I may have soft bricked my phone. In a panic, I downloaded a "rooted stock" rom and flashed that...after a few bootloops, I updated my cwm recovery and superuser app...and my phone has been working fine every since (whew). I really want to unroot, then re-root and just run the stock rom without flashing any more custom roms, however I am afraid of bricking it again.
I have the stock official firmware N900PVPUBMJ4_N900PSPTBMJ4_N900PVPUBMJ4_HOME.tar.md 5 which to my understanding is android 4.3. I do understand that 4.4 is out. I was wondering is it ok to flash the 4.3 using odin to return my phone back to stock?? I've been spooked ever since my soft brick encounter. Any info will be helpful. Btw, sorry for the long story. I figured I should give all the details. That would help me get to the bottom of it all
Thanks in Advance!
Click to expand...
Click to collapse
Depends on what version you are running, but sounds like you are on mj4 still... http://forum.xda-developers.com/showthread.php?t=2657828 this one is mj4 (4.3), if you are on 4.4 you need to go to the Android development forum and use whatever version you are on, just look for rwilcos one click.
tonyevo52 said:
Depends on what version you are running, but sounds like you are on mj4 still... http://forum.xda-developers.com/showthread.php?t=2657828 this one is mj4 (4.3), if you are on 4.4 you need to go to the Android development forum and use whatever version you are on, just look for rwilcos one click.
Click to expand...
Click to collapse
Yes...I am still on 4.3.
LadyDroid81 said:
Yes...I am still on 4.3.
Click to expand...
Click to collapse
Follow the instructions from this thread and you will be fully unrooted http://forum.xda-developers.com/showthread.php?t=2657828:good:
Requesting help. I am not a noob by any means, I have installed custom roms many times, and rooted many phones, and installed and used safestrap on several phones, but I cannot get ANY custom rom to install properly on my Verizon Samsung Galaxy S4, which is (was) rooted, with Safestrap 3.72, and MK2 firmware.
I was running the stock 4.3/mk2 firmware, with the latest busybox and supersu, and the latest safestrap, and safe root installed. I was able to successfully root the phone, and install safestrap, but even when I created a rom slot, gave it a name, wiped it completely, and then try to install one of the many 4.3/mk2 "Safe" roms, no rom will boot, once installed. It is so frustrating! I read somewhere that with the Verizon S4, and MK2 firmware, you could only install a rom in the stock rom slot, so I tried that, and now safestrap is gone, and the phone boots to a light blue screen with little green checkmarks. So I'm in the process of downloading the original MK2 firmware from Samsung and using Odin to restore. Anybody have any ideas? I'm thinking of quickly getting rid of the S4 while it still has some value.
mactechnm said:
Requesting help. I am not a noob by any means, I have installed custom roms many times, and rooted many phones, and installed and used safestrap on several phones, but I cannot get ANY custom rom to install properly on my Verizon Samsung Galaxy S4, which is (was) rooted, with Safestrap 3.72, and MK2 firmware.
I was running the stock 4.3/mk2 firmware, with the latest busybox and supersu, and the latest safestrap, and safe root installed. I was able to successfully root the phone, and install safestrap, but even when I created a rom slot, gave it a name, wiped it completely, and then try to install one of the many 4.3/mk2 "Safe" roms, no rom will boot, once installed. It is so frustrating! I read somewhere that with the Verizon S4, and MK2 firmware, you could only install a rom in the stock rom slot, so I tried that, and now safestrap is gone, and the phone boots to a light blue screen with little green checkmarks. So I'm in the process of downloading the original MK2 firmware from Samsung and using Odin to restore. Anybody have any ideas? I'm thinking of quickly getting rid of the S4 while it still has some value.
Click to expand...
Click to collapse
3.72 is for 4.4 KitKat and was made for the AT&T version of the S4, therefore, you are not able to create slots. You would need to install 3.71 and only flash 4.3 based roms. If you want 4.4 based roms you need to upgrade to NC5 and install 3.72, but you are only able to flash to the stock side.
There's plenty of info for you to read in the General section.
riker147 said:
3.72 is for 4.4 KitKat and was made for the AT&T version of the S4, therefore, you are not able to create slots. You would need to install 3.71 and only flash 4.3 based roms. If you want 4.4 based roms you need to upgrade to NC5 and install 3.72, but you are only able to flash to the stock side.
There's plenty of info for you to read in the General section.
Click to expand...
Click to collapse
Thank you for your response. Actually what I failed to mention is I did have 3.71 installed first, and I had the exact same problem. So it's not an issue with the safestrap version. And I have tried about 12 different ROMs. Including BajaROM-S4-Release-v-2.2 and BoneStock4.3_S4v2.1. As I said, I'm not a newbie at all, and I'm not about to hunt and peck for information again (which is what I've been doing for two days now). I wouldn't have asked for help if I had been successful in my search.
I have never had an issue installing any safestrap compatible rom...3.72 is strictly for android 4.4 and no rom slots...so no way you would ever get a rom installed using 3.72 on MK2 base build. As for 3.71...never heard of any issue with SS compatible roms for 3.71 not installing right. Really difficult to figure out what you are doing wrong from what you are giving us...
sent by safestrap powered echo v26
decaturbob said:
I have never had an issue installing any safestrap compatible rom...3.72 is strictly for android 4.4 and no rom slots...so no way you would ever get a rom installed using 3.72 on MK2 base build. As for 3.71...never heard of any issue with SS compatible roms for 3.71 not installing right. Really difficult to figure out what you are doing wrong from what you are giving us...
sent by safestrap powered echo v26
Click to expand...
Click to collapse
Again, thanks for your help. I'm going to start with Odin. Wipe it all clean and start over. That's always the best option. Thanks!
basically, I'd follow this:
http://forum.xda-developers.com/showthread.php?t=2763834
I'd go back to MK2, root, BB, SS 3.71. Then go up to NC5 ROMs with SS 3.72. Wiping EVERYTHING along the way, system included, not just factory reset
Similar Issue
I not a noob either im very familiar with how this whole operation works.
I have a very similar issue as well I'm (unable to flash roms including my own recovery). I'm 100% knowledgeable on CM, but when it comes to Safestrap or TWRP base Recoveries I'm far from noon but not an expert so to say... Here's my issue. I have the NC5 firmware and once had the Hyperdrive RLS17.1 KK S4 Final.zip... I went back to the I545VRUFNC5-Stock-Root-Deodex.zip.... I recently attempted to download another ROM, (based on the same firmware of course) as soon as I attempted to flash it (which only took about 1 min and didn't work) I figured something was wrong. So I just decided to go back to my recovery that I've made a few moments ago. When I tried to do that. The msg " E: Unable to mount '/system' " appeared.
Now I've notice since then Wiping and Flashing return the same results.
There is no longer an OS on my S4... I can not Mount the System.
So I believe in stuck in Safestrap 3.72.
(Please let me know what other info you need, I spent the last couple of days trying to figure this out on my own, so far I'm losing the battle)
Please help guys.
same problem
mactechnm said:
Requesting help. I am not a noob by any means, I have installed custom roms many times, and rooted many phones, and installed and used safestrap on several phones, but I cannot get ANY custom rom to install properly on my Verizon Samsung Galaxy S4, which is (was) rooted, with Safestrap 3.72, and MK2 firmware.
I was running the stock 4.3/mk2 firmware, with the latest busybox and supersu, and the latest safestrap, and safe root installed. I was able to successfully root the phone, and install safestrap, but even when I created a rom slot, gave it a name, wiped it completely, and then try to install one of the many 4.3/mk2 "Safe" roms, no rom will boot, once installed. It is so frustrating! I read somewhere that with the Verizon S4, and MK2 firmware, you could only install a rom in the stock rom slot, so I tried that, and now safestrap is gone, and the phone boots to a light blue screen with little green checkmarks. So I'm in the process of downloading the original MK2 firmware from Samsung and using Odin to restore. Anybody have any ideas? I'm thinking of quickly getting rid of the S4 while it still has some value.
Click to expand...
Click to collapse
im having the same problem i am also frustrated i don't know what to do
Similar Issue
I know there must be a way... If only I can get it to mount the "system" and "systemorig"...
I'm going to play around with the Slots and the datas Size's and see what I come up with.
Pretty sure you will need to Odin the stock NC5 image and start over.
Sent from my SCH-I545 using Tapatalk
jmgib said:
Pretty sure you will need to Odin the stock NC5 image and start over.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Oh ok. The Stock NC5 image... Great.
Where can I find the stock image?
If possible, could you please send a link?
Thanks in advance
damien302 said:
I not a noob either im very familiar with how this whole operation works.
I have a very similar issue as well I'm (unable to flash roms including my own recovery). I'm 100% knowledgeable on CM, but when it comes to Safestrap or TWRP base Recoveries I'm far from noon but not an expert so to say... Here's my issue. I have the NC5 firmware and once had the Hyperdrive RLS17.1 KK S4 Final.zip... I went back to the I545VRUFNC5-Stock-Root-Deodex.zip.... I recently attempted to download another ROM, (based on the same firmware of course) as soon as I attempted to flash it (which only took about 1 min and didn't work) I figured something was wrong. So I just decided to go back to my recovery that I've made a few moments ago. When I tried to do that. The msg " E: Unable to mount '/system' " appeared.
Now I've notice since then Wiping and Flashing return the same results.
There is no longer an OS on my S4... I can not Mount the System.
So I believe in stuck in Safestrap 3.72.
(Please let me know what other info you need, I spent the last couple of days trying to figure this out on my own, so far I'm losing the battle)
Please help guys.
Click to expand...
Click to collapse
shonnick01 said:
im having the same problem i am also frustrated i don't know what to do
Click to expand...
Click to collapse
I only just saw these posts, I have not been on here for a week or so but if you are still having issues... As far as what went wrong to begin with, did you factory reset/advanvanced wipe all but the internal sd before flashing? Are you only installing into the 'stock' slot on SafeStrap? As far as the fix, if you are suck in Safestrap, you will need to boot into recovery mode, if possible and wipe/factory reset and then boot into download mode and flash one of these http://forum.xda-developers.com/showthread.php?t=2735172 in Odin.
liljoe727 said:
I only just saw these posts, I have not been on here for a week or so but if you are still having issues... As far as what went wrong to begin with, did you factory reset/advanvanced wipe all but the internal sd before flashing? Are you only installing into the 'stock' slot on SafeStrap? As far as the fix, if you are suck in Safestrap, you will need to boot into recovery mode, if possible and wipe/factory reset and then boot into download mode and flash one of these http://forum.xda-developers.com/showthread.php?t=2735172 in Odin.
Click to expand...
Click to collapse
Thanks a lot man. The is has been resolved...
I had to Odin the stock NC5 (exactly what you've just mentioned in your response.) I had to flash it twice actually. The first time only took about 3 mins. I then tried to restore my backup, but during the time it restari SS (when the flash was approximately 90% done) I then went to restart the system and then received the notice "No OS loaded). So I wiped all except my SD card and then I just thought to myself to just try and Odin the stock NC5 one more time (it was getting late and I was about to give up). On the 2nd attempi it took almost 3 times the length as before (15-20mins) when it finished, it bypass the " unlock Samsung screen " and displayed the stock splash screen and audio then the Verizon screen. ( I was happier the a crackhead at a free crack-give-away)...
So I want to thank you for responding, I was determined not to give up,, and it was really close before I was about throw in the towel... Thanks a bunch. (You're response was exactly what I did last night)... I was about to update my issue as soon as I fixed it las night was it was so late and I was really sleepy, then I wake up to your message with the exact fix.
Thanks a lot ☺☺
I'm familiar with rooting and ROMs and have been flashing HyperDrive on my S4 as updates came out. I have a Verizon S4 on NC5. Last night I messed up my phone big time. I was going to install the new version of Hyperdrive and put all the necessary files on my sd card. While in Safestrap when I went to wipe the phone I accidentally checked to wipe the sd card also. So now the phone was wiped and there was nothing to flash. I panicked and shut down the phone, took out the SD to connect to my PC and put the necessary files back on. When I turned the phone back on it doesn't go to safestap it just hangs at the samsung galaxy s4 logo.
I was up all night reading and trying everything I could think of. I tried to use Odin 3.09 using the .tar for no wipe and the .tar with .pit for full wipe and Odin fails every time. I checked the md5s. I tried downloading Odin from another source and it still just says it fails every time.
I'm not due for an upgrade till late this year. I'm desperate. Please someone help.
delsoul6 said:
I'm familiar with rooting and ROMs and have been flashing HyperDrive on my S4 as updates came out. I have a Verizon S4 on NC5. Last night I messed up my phone big time. I was going to install the new version of Hyperdrive and put all the necessary files on my sd card. While in Safestrap when I went to wipe the phone I accidentally checked to wipe the sd card also. So now the phone was wiped and there was nothing to flash. I panicked and shut down the phone, took out the SD to connect to my PC and put the necessary files back on. When I turned the phone back on it doesn't go to safestap it just hangs at the samsung galaxy s4 logo.
I was up all night reading and trying everything I could think of. I tried to use Odin 3.09 using the .tar for no wipe and the .tar with .pit for full wipe and Odin fails every time. I checked the md5s. I tried downloading Odin from another source and it still just says it fails every time.
I'm not due for an upgrade till late this year. I'm desperate. Please someone help.
Click to expand...
Click to collapse
Did you make sure Odin found the S4?
delsoul6 said:
I'm familiar with rooting and ROMs and have been flashing HyperDrive on my S4 as updates came out. I have a Verizon S4 on NC5. Last night I messed up my phone big time. I was going to install the new version of Hyperdrive and put all the necessary files on my sd card. While in Safestrap when I went to wipe the phone I accidentally checked to wipe the sd card also. So now the phone was wiped and there was nothing to flash. I panicked and shut down the phone, took out the SD to connect to my PC and put the necessary files back on. When I turned the phone back on it doesn't go to safestap it just hangs at the samsung galaxy s4 logo.
I was up all night reading and trying everything I could think of. I tried to use Odin 3.09 using the .tar for no wipe and the .tar with .pit for full wipe and Odin fails every time. I checked the md5s. I tried downloading Odin from another source and it still just says it fails every time.
I'm not due for an upgrade till late this year. I'm desperate. Please someone help.
Click to expand...
Click to collapse
You're trying to flash a version that's too old. There's a check in place called rollback protection that prevents you from using older versions of software. I'd try flashing NC5 or NK1 via tar. Let me know if you need more help.
FIXED!
Thanks guys. I really appreciate your input. I was so desperate a actually went to a Verizon store in the morning even though I had no faith they would do anything. I just told them it wouldn't boot after I wiped it and they said we don't fix phones we only give replacements. Thanks for nothing. I saw some people posting that Odin failed on one computer and worked on another so I figured I'd try on my work computer. I downloaded an NK1 .tar file from SamMobile this time instead of the xda thread. It worked the first time. No problems at all. I have no idea why it worked but I'm just thankful it did. My phone is running like new.
delsoul6 said:
Thanks guys. I really appreciate your input. I was so desperate a actually went to a Verizon store in the morning even though I had no faith they would do anything. I just told them it wouldn't boot after I wiped it and they said we don't fix phones we only give replacements. Thanks for nothing. I saw some people posting that Odin failed on one computer and worked on another so I figured I'd try on my work computer. I downloaded an NK1 .tar file from SamMobile this time instead of the xda thread. It worked the first time. No problems at all. I have no idea why it worked but I'm just thankful it did. My phone is running like new.
Click to expand...
Click to collapse
Glad to see the issue was resolved :good:
It's pretty difficult to permanently brick these devices, just takes a little patience and the know-how.
ryanbg said:
Glad to see the issue was resolved :good:
It's pretty difficult to permanently brick these devices, just takes a little patience and the know-how.
Click to expand...
Click to collapse
Agreed! This is the only thing I really like Samsung for is Odin! Now if LG or Moto could put in a form of Odin it would make them way more appealing!
So the first thing was I rooted a Samsung S4 SGH-M919.
I used Chainfire's files and Odin. it worked just fine.
Gave the phone to my wife but the firmware 4.4.2 was clearly outdated that none of the apps she played worked, everything just froze on her or crashed.
So I decided to install a custom rom, this led me to Imperium Lollipop 5.0.1
Well that in turn made the phone unbootable. It would continuously go into these 4 circular swirling balls and get stuck there. I cant even get into Recovery Mode. Only Download Mode.
So this made me do some searching and I dl'ed SGH-M919 stock firmware 4.2.2
I used Odin to flash that and it failed.
So now the phone boots into a screen that telling me to uses Kies to fix the issue.
I'm at a loss what to do next.
Can someone give me the necessary steps to fix the phone and where I intended to go with this?
Much appreciated. thanks.
catheapp said:
So the first thing was I rooted a Samsung S4 SGH-M919.
I used Chainfire's files and Odin. it worked just fine.
Gave the phone to my wife but the firmware 4.4.2 was clearly outdated that none of the apps she played worked, everything just froze on her or crashed.
So I decided to install a custom rom, this led me to Imperium Lollipop 5.0.1
Well that in turn made the phone unbootable. It would continuously go into these 4 circular swirling balls and get stuck there. I cant even get into Recovery Mode. Only Download Mode.
So this made me do some searching and I dl'ed SGH-M919 stock firmware 4.2.2
I used Odin to flash that and it failed.
So now the phone boots into a screen that telling me to uses Kies to fix the issue.
I'm at a loss what to do next.
Can someone give me the necessary steps to fix the phone and where I intended to go with this?
Much appreciated. thanks.
Click to expand...
Click to collapse
Are you sure that you have the right bootloader installed for the lollipop rom? Did you factory reset before installing custom rom? Try to wipe davlik after installation completes before restarting device. Also follow the instructions given by the rom thread op.