Related
Here's the story:
I got excited about the bootloader vulnerability (Loki) being released, and I saw that a few devs had updated their ROMs to work with Loki so I decided to give it a shot.
The easiest, fail-free way of installing a recovery was to install TWRP through goomanager. I had only ever used CWM, but I figured it couldn't be that difficult to learn/use. And it wasn't, I'm just dumb. I went to wipe my S4 and I misunderstood what I was supposed to do and ended up formatting the phone instead. On CWM, this is normal and basically just means factory restore, but on TWRP this wipes everything, including the OS. This might not have been as big of a problem if that wipe hadn't just erased the ROM I was intending to install.
Long story short, with no OS on the phone, I was stuck on the Samsung boot screen and I could not even get into recovery. I tried ODIN restoring the stock firmware twice, but despite the fact that ODIN said "SUCCESS", my phone was in the same state. After panicking for a couple of hours :crying: and trying different things (including just leaving the phone alone for a while in hopes that I would come back and it would be magically fixed) I downloaded Kies. I figured, Kies comes directly from Samsung. If there's a way to fix my phone, this has to be it.
I did the emergency firmware recovery, and it took forever and when it was done it looked like I was going to end up right where I started, when after about a minute of the Samsung boot screen, I saw the heavenly blue-purple swish of the boot animation. :victory:
tl;dr: I thought I bricked my phone. I brought it back to life with Kies.
That's my story. Hopefully it'll help someone who is panicking that they just borked their new phone and helps them restore it.
I'm sad to say that I also wiped a phone with TWRP. It wasn't an S4 and I didn't need Kies.
I had no idea that it would delete the OS - I don't think there was even a warning.
What ROM were you going to use that supported Loki?? I can't seem to find one anywhere...
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
drucquerkellan said:
What ROM were you going to use that supported Loki?? I can't seem to find one anywhere...
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
Okay, I hope it goes without saying that what you do with this is your responsibility. That being said, I was going to try:
[ROM][BETA][4.2.2][May 23] Slim Bean jflteatt [build 5.6] - LOKI patched
and here are a few more:
[ROM] Task650 AOKP(Jellybean 4.2.2)(5.23.2013)(LOKI-d) (AT&T)
[KERNEL][ATT][AOSP/TW][5/23/2013] KT-SGS4 - MDL - LOKI'd - KTweaker
CyanogenMod 10.1 Loki'd for the Galaxy S4 ATT
okzygen said:
Okay, I hope it goes without saying that what you do with this is your responsibility. That being said, I was going to try:
[ROM][BETA][4.2.2][May 23] Slim Bean jflteatt [build 5.6] - LOKI patched
and here are a few more:
[ROM] Task650 AOKP(Jellybean 4.2.2)(5.23.2013)(LOKI-d) (AT&T)
[KERNEL][ATT][AOSP/TW][5/23/2013] KT-SGS4 - MDL - LOKI'd - KTweaker
CyanogenMod 10.1 Loki'd for the Galaxy S4 ATT
Click to expand...
Click to collapse
OK thanks I'll try them in a little bit and report back here how it goes!
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
You can still mount to USB through recovery and transfer a ROM zip over and then flash it.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
okzygen said:
Here's the story:
I got excited about the bootloader vulnerability (Loki) being released, and I saw that a few devs had updated their ROMs to work with Loki so I decided to give it a shot.
The easiest, fail-free way of installing a recovery was to install TWRP through goomanager. I had only ever used CWM, but I figured it couldn't be that difficult to learn/use. And it wasn't, I'm just dumb. I went to wipe my S4 and I misunderstood what I was supposed to do and ended up formatting the phone instead. On CWM, this is normal and basically just means factory restore, but on TWRP this wipes everything, including the OS. This might not have been as big of a problem if that wipe hadn't just erased the ROM I was intending to install.
Long story short, with no OS on the phone, I was stuck on the Samsung boot screen and I could not even get into recovery. I tried ODIN restoring the stock firmware twice, but despite the fact that ODIN said "SUCCESS", my phone was in the same state. After panicking for a couple of hours :crying: and trying different things (including just leaving the phone alone for a while in hopes that I would come back and it would be magically fixed) I downloaded Kies. I figured, Kies comes directly from Samsung. If there's a way to fix my phone, this has to be it.
I did the emergency firmware recovery, and it took forever and when it was done it looked like I was going to end up right where I started, when after about a minute of the Samsung boot screen, I saw the heavenly blue-purple swish of the boot animation. :victory:
tl;dr: I thought I bricked my phone. I brought it back to life with Kies.
That's my story. Hopefully it'll help someone who is panicking that they just borked their new phone and helps them restore it.
Click to expand...
Click to collapse
all you have to do is boot to recovery, and push a rom through adb to your phone. I've done this dozens of times accidentally and the easiest way to avoid it is to keep a backup rom on your sd at all times
mcmb03 said:
all you have to do is boot to recovery, and push a rom through adb to your phone. I've done this dozens of times accidentally and the easiest way to avoid it is to keep a backup rom on your sd at all times
Click to expand...
Click to collapse
or....takeout the sdcard...put the rom on it and flash....
Sent from my SGH-I337M using xda premium
niceppl said:
or....takeout the sdcard...put the rom on it and flash....
Sent from my SGH-I337M using xda premium
Click to expand...
Click to collapse
yeah, either way kies was probably at the bottom of the list for solutions since you were trying to put a different rom on your phone anyways
niceppl said:
or....takeout the sdcard...put the rom on it and flash....
Sent from my SGH-I337M using xda premium
Click to expand...
Click to collapse
Or the easiest of the options that I already mentioned 4 posts up... Don't even need to bother with adb or taking off your back cover. Plug in, mount, click-and-drag file transfer, unmount, flash, done.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
I'm just glad you got it taken care of OP. Hopefully this thread will help others who may have a mishap while flashing ROMs.
To all of those talking about recovery... maybe I wasn't clear. It's not that I couldn't get into TWRP. I couldn't get into recovery mode at all. I could get into download mode, which is why I went the ODIN route. Whenever I would try to boot into recovery, it would show the little blue text on the top right of the screen, and the proceed to throw me right back to the booth screen.
This is incredible. Incredible how badly you almost screwed yourself over with, and incredible that Kies was actually helpful.
I installed Kies to backup contacts, once. After that? Thing crashes on updates, takes 30 minutes to load, hated any music I threw at it, didnt like my wireless transfer setting....
idk I had a pretty bad experience with Kies, i'm glad to hear that program isnt all useless.
okzygen said:
To all of those talking about recovery... maybe I wasn't clear. It's not that I couldn't get into TWRP. I couldn't get into recovery mode at all. I could get into download mode, which is why I went the ODIN route. Whenever I would try to boot into recovery, it would show the little blue text on the top right of the screen, and the proceed to throw me right back to the booth screen.
Click to expand...
Click to collapse
Yea that part doesn't make sense though. Many times I've seen people try to boot out of recovery with no system and always be able to get right back into recovery. Not that I don't believe you, just saying it's weird. Which leads me to the guy above... he didn't really screw himself that bad, no danger of bricking at all, just needed a reflash.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Just FYI on Kies
Am not sure on windows pc, but on my imac adb does not work with Kies. Had to use the Kies uninstaller to get if off imac then use adb. Maybe this isn't an issue on all phones?
Just got s4, and coming from HTC One S. So, if this is old news, sorry--
okzygen said:
To all of those talking about recovery... maybe I wasn't clear. It's not that I couldn't get into TWRP. I couldn't get into recovery mode at all. I could get into download mode, which is why I went the ODIN route. Whenever I would try to boot into recovery, it would show the little blue text on the top right of the screen, and the proceed to throw me right back to the booth screen.
Click to expand...
Click to collapse
I'm pretty sure you have to wipe cache once you do odin in order to boot back in OS or else you'll just get stuck at logo
polish_pat said:
I'm pretty sure you have to wipe cache once you do odin in order to boot back in OS or else you'll just get stuck at logo
Click to expand...
Click to collapse
I'm curious, is there a way to do this in download mode (via Odin or otherwise)? As far as I know, I can only do that through recovery. Do I have to adb and wipe /cache?
Sent from my SGH-I337 using xda app-developers app
okzygen said:
I'm curious, is there a way to do this in download mode (via Odin or otherwise)? As far as I know, I can only do that through recovery. Do I have to adb and wipe /cache?
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
i do it thru recovery, thats always how it worked for me. You cant do it thru adb since you need root to do that and odin wipes root
okzygen said:
Okay, I hope it goes without saying that what you do with this is your responsibility. That being said, I was going to try:
[ROM][BETA][4.2.2][May 23] Slim Bean jflteatt [build 5.6] - LOKI patched
and here are a few more:
[ROM] Task650 AOKP(Jellybean 4.2.2)(5.23.2013)(LOKI-d) (AT&T)
[KERNEL][ATT][AOSP/TW][5/23/2013] KT-SGS4 - MDL - LOKI'd - KTweaker
CyanogenMod 10.1 Loki'd for the Galaxy S4 ATT
Click to expand...
Click to collapse
OK I installed the AOKP one and it works like a charm. Only thing is NFC doesn't work so once that works it will be pretty Much perfect
Sent from my SGH-I337 using Tapatalk 2
jasbur17 said:
I'm sad to say that I also wiped a phone with TWRP. It wasn't an S4 and I didn't need Kies.
I had no idea that it would delete the OS - I don't think there was even a warning.
Click to expand...
Click to collapse
Yeah me too, was and still am not happy about it. Should gave stuck to CWM. TWRP is a cool recovery, as long as you realize what you hit.
Glad Kies worked! Now that I have an Att phone I can utilize it again. Wouldn't recognize my International SGS3, so Kies was useless.
Sent from GT-I9505 transformed SGH-I337
I've done some searching, finding similar things that have happened to others here, but nothing that specifically fits what I'm experiencing...
I'm hoping someone has a step-by-step that I can do to get this phone rooted properly... First, I've been on XDA for a while, Droid Eris and HTC Incredible 2, but this is the first Samsung phone I've owned... A few days ago, I tried the Casual Root method and went ahead and rooted, unlocked the bootloader (unsecure ABOOT) and loaded CWM touch as my recovery. All looked fine, but when I went in to recovery to try and backup the stock rom, it threw a ton of Not able to write/Cannot Mount errors... My phone came with the MF1 4.1.2 already running.
Since, I've tried EZ-Unlock 1.2 to check and unlock the bootloader (which it showed as "Unknown" until I clicked unlock) and I've tried installing different recoveries through EZ Recovery (TWRP 2.2.2, CWM variants, etc...). Still, no joy in getting this to work properly.
The last attempt kept the phone in Download mode until I rebooted using the Power, Vol. Down, Menu to bypass it (Not detecting ANY recovery now!?). I'm still able to get back to the original Rom (which is rooted now), but I'm concerned with bricking if I keep trying this.
So, I'm thinking now of just doing an Odin back to stock and reflashing all the original firmware so I can start over with Casual. Was wondering if anyone had any other input which might get the R/W issue fixed so I don't have to go through all the Odin stuff? Compared to HTC phones, this is quite different with Root/Flashing, so I'm a little confused with the whole process of things right now... Any help would really be appreciated! I'm looking forward to deving at some point, once I'm comfortable with the process...
Thanks,
Rich
Anyone?
Sent from my SCH-I535 using xda premium
Never mind...
Macrodroid said:
I've done some searching, finding similar things that have happened to others here, but nothing that specifically fits what I'm experiencing...
I'm hoping someone has a step-by-step that I can do to get this phone rooted properly... First, I've been on XDA for a while, Droid Eris and HTC Incredible 2, but this is the first Samsung phone I've owned... A few days ago, I tried the Casual Root method and went ahead and rooted, unlocked the bootloader (unsecure ABOOT) and loaded CWM touch as my recovery. All looked fine, but when I went in to recovery to try and backup the stock rom, it threw a ton of Not able to write/Cannot Mount errors... My phone came with the MF1 4.1.2 already running.
Since, I've tried EZ-Unlock 1.2 to check and unlock the bootloader (which it showed as "Unknown" until I clicked unlock) and I've tried installing different recoveries through EZ Recovery (TWRP 2.2.2, CWM variants, etc...). Still, no joy in getting this to work properly.
The last attempt kept the phone in Download mode until I rebooted using the Power, Vol. Down, Menu to bypass it (Not detecting ANY recovery now!?). I'm still able to get back to the original Rom (which is rooted now), but I'm concerned with bricking if I keep trying this.
So, I'm thinking now of just doing an Odin back to stock and reflashing all the original firmware so I can start over with Casual. Was wondering if anyone had any other input which might get the R/W issue fixed so I don't have to go through all the Odin stuff? Compared to HTC phones, this is quite different with Root/Flashing, so I'm a little confused with the whole process of things right now... Any help would really be appreciated! I'm looking forward to deving at some point, once I'm comfortable with the process...
Thanks,
Rich
Click to expand...
Click to collapse
If you were able to root your phone successfully, then what I would recommend what to do is download whatever image you want (for me, I downloaded twrp 2.6.3.0) and then flash it through flashify (free in play store).
If you want to get it an easier way, then use goomanager and then install open recovery script (you'll see it when you press menu). It should install the recovery automatically.
If you want clockworkmod touch, then if you want an image, use flashify to flash it. Doing either of the options will give you a working recovery.
david_hume said:
If you were able to root your phone successfully, then what I would recommend what to do is download whatever image you want (for me, I downloaded twrp 2.6.3.0) and then flash it through flashify (free in play store).
If you want to get it an easier way, then use goomanager and then install open recovery script (you'll see it when you press menu). It should install the recovery automatically.
If you want clockworkmod touch, then if you want an image, use flashify to flash it. Doing either of the options will give you a working recovery.
Click to expand...
Click to collapse
Ok, I've gotvtwrp 2.6.3.0 loaded, works... But, I cannot mount anything, backup totally fails. Any ideas? Twrp also asks for a password for some reason...
Btw, nice to see a familiar face on here! How's life treating you these days?
Sent from my SCH-I535 using xda premium
Try this. But download and use the correct and updated cwm recovery from somewhere else.
http://bestandroidtricks.com/how-to...covery-on-the-samsung-galaxy-s3-all-versions/
Sent from my SCH-I535 using xda app-developers app
stolo said:
Try this. But download and use the correct and updated cwm recovery from somewhere else.
http://bestandroidtricks.com/how-to...covery-on-the-samsung-galaxy-s3-all-versions/
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Thanks! After going through Rom Manager and letting it update CWR on it's own, I finally got everything working now! Backup of the Stock Rom is done finally and I can start flashing some Rom's to get comfortable with things... Hopefully, I can start putting out some Rom's for this device soon!! Thanks for all the help, I really appreciate it!
I have been using kitkang cm11, so far really excited and loving 4.4. I have been updating daily.
Sent from my SCH-I535 using xda app-developers app
stolo said:
I have been using kitkang cm11, so far really excited and loving 4.4. I have been updating daily.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Got wicked loaded up! So far, so good. I might try pulling a repo on cm11 sometime soon...
Sent from my SCH-I535 using xda premium
Hey everyone,
So I think I may have done something strange and i'm not sure how to fix it. Long story short, screen cracked, so I bought a new one and I used TWRP to backup my original phone. So now, i'm just trying to unlock and root, you know, the usual. BTW, I tried using ABD/Fastboot, which I never typically do, but I heard it was more efficient and whatnot so I thought I try. I think the unlocking of the bootloader went well. And I even think I flashed recovery properly. But when I tried to access recovery, it prompted me for a password.
I read on the TWRP site I was supposed to let the phone boot as normal before accessing recovery. Oops. So I tried formatting all the data on the phone and no I have no OS or any files to recover from and adb push keeps giving me "Device not found" and now I don't know what to do.
Help?
EDIT: In case anyone has this issue searching threads, I just used Wug Toolkit to flash everything back to stock and then used the same Toolkit to unlock and root. TWRP isn't going to recognize a backup from a different phone. To my understanding, there is a way around that, but I didn't look into it. Oh, and apparently, don't flash the EFS partition lol
New Jer-Z said:
Hey everyone,
So I think I may have done something strange and i'm not sure how to fix it. Long story short, screen cracked, so I bought a new one and I used TWRP to backup my original phone. So now, i'm just trying to unlock and root, you know, the usual. BTW, I tried using ABD/Fastboot, which I never typically do, but I heard it was more efficient and whatnot so I thought I try. I think the unlocking of the bootloader went well. And I even think I flashed recovery properly. But when I tried to access recovery, it prompted me for a password.
I read on the TWRP site I was supposed to let the phone boot as normal before accessing recovery. Oops. So I tried formatting all the data on the phone and no I have no OS or any files to recover from and adb push keeps giving me "Device not found" and now I don't know what to do.
Help?
Click to expand...
Click to collapse
I never heard of this problem before, maybe you can use Odin to flash the recovery again
Sent from my Galaxy S4 using Tapatalk p.s if I helped you peles hit the thanks button
mpalomba3 said:
I never heard of this problem before, maybe you can use Odin to flash the recovery again
Sent from my Galaxy S4 using Tapatalk p.s if I helped you peles hit the thanks button
Click to expand...
Click to collapse
Oh, that reminds me, TWRP wasn't able to mount any of the directories, it seems. I think it can, now, but I remember seeing those errors in the log before I wiped everything. Thanks for that suggestion, i'll give it a shot.
No problem, report back if it works
Sent from my Galaxy S4 using Tapatalk p.s if I helped you peles hit the thanks button
I can't seem to find on the internets which odin version is compatible with the Nexus 5. I'm not finding any hits to directly correlate and I don't want to damage further. Which one would you recommend?
Odin is for Samsung devices
sent from my HAMMERHEAD neXus
New Jer-Z said:
I can't seem to find on the internets which odin version is compatible with the Nexus 5. I'm not finding any hits to directly correlate and I don't want to damage further. Which one would you recommend?
Click to expand...
Click to collapse
Odin is a Samsung thing. Not LG.
What you'll need to do is flash the 4.4.2 factory image. Follow this guide: http://forum.xda-developers.com/showthread.php?t=2513701
El Daddy said:
Odin is a Samsung thing. Not LG.
What you'll need to do is flash the 4.4.2 factory image. Follow this guide: http://forum.xda-developers.com/showthread.php?t=2513701
Click to expand...
Click to collapse
OK!
So, I used the Wug toolkit to basically flash everything to stock, and then root it. I installed TWRP using the app and I tried using the app to restore from my earlier back up. So, it boots into recovery but nothing happened. Looking at the log, it says the TWRP isn't able to locate the files. Trying to just restore from recovery isn't helpful because when I hit "Restore" nothing pops up. As if the SDCard partition isn't being accessed. I can't see any of the files in any directory. Anyone have any ideas?
You need to let the phone boot into android before flashing a custom recovery.
Sent from my Nexus 10 using Tapatalk
El Daddy said:
You need to let the phone boot into android before flashing a custom recovery.
Sent from my Nexus 10 using Tapatalk
Click to expand...
Click to collapse
I realize that now lol. Well, I fixed that, but now have a new issue. Any ideas for me?
Flashing the factory image erases everything. Such as backups stored on your phone.
Sent from my Nexus 10 using Tapatalk
El Daddy said:
Flashing the factory image erases everything. Such as backups stored on your phone.
Sent from my Nexus 10 using Tapatalk
Click to expand...
Click to collapse
I had a copy saved on my desktop, so I transferred it back.
New Jer-Z said:
I can't seem to find on the internets which odin version is compatible with the Nexus 5. I'm not finding any hits to directly correlate and I don't want to damage further. Which one would you recommend?
Click to expand...
Click to collapse
Sorry about that, I have a gs4 so I thought Odin was for all devices
Sent from my Galaxy S4 using Tapatalk p.s if I helped you peles hit the thanks button
New Jer-Z said:
I had a copy saved on my desktop, so I transferred it back.
Click to expand...
Click to collapse
Did you put the backup on the root of the sdcard? I think it needs to be in the TWRP folder. You should first make a backup of your current rom even if it's stock rooted.
Sent from my Nexus 5 using Tapatalk
housry23 said:
Did you put the backup on the root of the sdcard? I think it needs to be in the TWRP folder. You should first make a backup of your current rom even if it's stock rooted.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Someone explained to me TWRP won't recognize a backup with a serial number from a different phone. So essentially, I will just have to forego it. I used Wug Toolkit to fix this issue and just flashed everything to stock and had the same toolkit unlock and root. Using ADB was a fail and cost me a whole afternoon lol
I have been looking for something similar to what is going on with my phone and I found nothing. I have been rooted for awhile (so I could use all my apps with MW) but decided to flash CM 11 and get all the bloatware off. I followed a youtube tutorial to flash a custom recovery but I seem to have been unsuccessful in unlocking my bootloader first and so I get the following error.
System software not authorized by Verizon Wireless has been found on your phone. Please turn your phone off and go to the nearest Verizon Wireless store for help.
Yeah, that's not gonna happen. Any help would be appreciated.
Can you get to download mode? If so you can try to re flash stock ROM.
Sent from my SM-N9005 using XDA Free mobile app
DeuXGod said:
Can you get to download mode? If so you can try to re flash stock ROM.
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
That's exactly what I had to do, problem I had though was Odin would fail as soon as I clicked start. Then for no damn reason my (still without a successful Odin run) my phone boots up like nothing was wrong. But I shot myself in the foot cause towelroot isn't working. Boooo....at least I have a working phone. Thanks for responding.
Tried getting help. I recently tried a fresh install of cm13. When it booted up it searched for a network. Went to network settings and let it look for a network. Found sprint and said it was trying to connect or register. Now I'm only getting schity 3g data sometime. No 4g. Almost seems like its not using the sim card. Tried booting up without it and it was still working?
Edit: using the g900p for sprint
Someone please help. All is appreciated
Sent from my kltespr using XDA-Developers mobile app
Anybody? I'm gonna have to get a new phone if I can't figure this out. I use it for work and really need assistance
Sent from my kltespr using XDA-Developers mobile app
Which CM13 rom did you use?
chippinganimal said:
Which CM13 rom did you use?
Click to expand...
Click to collapse
it was the 6-27-16 nightly build. had a few little issues and tried a clean install. when it booted, it couldnt find a provider i guess so i went to settings-cell networks and tried to search. it found sprint, under network operators, tried to connect and couldnt. just sat forever saying registering. also its working the same with or without a sim card. i thought it should be using the sim card for the 4g?
steveokinevo said:
Anybody? I'm gonna have to get a new phone if I can't figure this out. I use it for work and really need assistance
Sent from my kltespr using XDA-Developers mobile app
Click to expand...
Click to collapse
If you're that desperate go back to a stock rom. Your sprint network will work. Then when you have time play with other roms.
i have tried to go back to stock through recovery and doesnt work. im on ok4. do i need to odin that?
ive tried stock ok4 and its stuck at the booting screen with samsung. is there a one click thing for this?
steveokinevo said:
ive tried stock ok4 and its stuck at the booting screen with samsung. is there a one click thing for this?
Click to expand...
Click to collapse
Use Odin to go back to complete stock. That should fix this issue. If you should then wish to do so take the OTA to MM. After you do that make a backup in TWRP that way if you screw up you can restore a full backup in minutes. I have trouble getting everything to work on the other custom roms as well. That's why you keep a good copy of a backup to restore in twrp just in case. Anway, get odin and flash the stock 0K4 tar through that, it will fix you.
Kreatur3 said:
Use Odin to go back to complete stock. That should fix this issue. If you should then wish to do so take the OTA to MM. After you do that make a backup in TWRP that way if you screw up you can restore a full backup in minutes. I have trouble getting everything to work on the other custom roms as well. That's why you keep a good copy of a backup to restore in twrp just in case. Anway, get odin and flash the stock 0K4 tar through that, it will fix you.
Click to expand...
Click to collapse
after all this happened i did try the restore of my backup. was still doing the same thing. no 4g. i tried the ok4 update from http://forum.xda-developers.com/spr...t/rom-sprint-ok4-stock-tar-file-odin-t3262667 and still didnt work. let it boot for 20-25 mins and wouldnt do anything. if thats not what i should be using can you give me the right one. thx for your help btw
steveokinevo said:
after all this happened i did try the restore of my backup. was still doing the same thing. no 4g. i tried the ok4 update from http://forum.xda-developers.com/spr...t/rom-sprint-ok4-stock-tar-file-odin-t3262667 and still didnt work. let it boot for 20-25 mins and wouldnt do anything. if thats not what i should be using can you give me the right one. thx for your help btw
Click to expand...
Click to collapse
Okay so you tried to Odin flash that OK4 tar? That should have worked. Do you have the 4g lte sim card? I bought my s5 used and it wouldn't connect to lte until I got my sim in the mail. Otherwise I have no clue. Did you follow those instructions exactly and make sure you wiped your phone completely before taking the tar file?
Kreatur3 said:
Okay so you tried to Odin flash that OK4 tar? That should have worked. Do you have the 4g lte sim card? I bought my s5 used and it wouldn't connect to lte until I got my sim in the mail. Otherwise I have no clue. Did you follow those instructions exactly and make sure you wiped your phone completely before taking the tar file?
Click to expand...
Click to collapse
this phone was bought new, with 4g working. has worked fine up until now. took the tar file from the link, flashed with auto restart and reset time unchecked, said it passed, then got to the samsung splash screen and got stuck there. is there another link or file i could use? i really just want all stock at this point so this dam thing will work. i can do what i need after
steveokinevo said:
this phone was bought new, with 4g working. has worked fine up until now. took the tar file from the link, flashed with auto restart and reset time unchecked, said it passed, then got to the samsung splash screen and got stuck there. is there another link or file i could use? i really just want all stock at this point so this dam thing will work. i can do what i need after
Click to expand...
Click to collapse
Hmm. Beyond trying to download the tar again I have no ideas. If it's pretty new maybe take it in?
Its not new anymore. Had it for like a year and a half. They won't touch my phone with custom stuff though....
Sent from my kltespr using XDA-Developers mobile app
Seems to be fixed!
Sent from my kltespr using XDA-Developers mobile app
steveokinevo said:
Seems to be fixed!
Sent from my kltespr using XDA-Developers mobile app
Click to expand...
Click to collapse
What did you do to resolve this??
was it connecting to LTE before? if not then you might be best served getting a new sim from sprint, but if it was working before then id get a fresh tar.md5 and flash it in Odin. Here is the place ive been getting my tarballs from as of late. The server seems to be pretty fast and i can attest to the tar.md5s working quite well.