I have a Galaxy S4 from AT&T. I got it a few months ago, rooted it a few weeks after I got it. Randomly about a week ago, when I would make or receive a phone call, I could not hear the phone ringing, couldn't hear the person talking and they couldn't hear me. The only two ways I found it would work is if I booted into safe mode or I was connected to my cars bluetooth. I have no idea what caused it and I haven't messed with anything (like installing apps or changing settings) anywhere around the time it happened. I did many factory resets and hard key resets but nothing fixed it. I saw I had an OTA update so I did that (which I now realize was a big no-no -_-).
Since I did the OTA update while still rooted, that seems to have messed up my root. I seem to be both rooted and not rooted. So in trying to fix my first problem, I created the second problem. To solve both of these, I've been trying to install a fresh stock ROM onto the phone (to nothing but failure). I was trying to remove the root and put it back to stock incase I had to send it in for repairs. I found a few guides/posts from other people who did the OTA update while rooted but I couldn't seem to get it to work. It mostly consisted of re-rooting the phone, then un-rooting it but I could never get the phone to actually show that it was rooted.
(I just tested the phone part of my phone to see if it was working. Called it, and I could hear and be heard fine. Hung up, waited a few minutes and tried again and it didnt work at all. Both times were while it has been turned on for several minutes).
Does anyone know how I can get back to as close to stock as I can get so I can at least get the actual calling part of my phone fixed? Either see if something to do with the rooting is causing the problem or at least let me send it in to get it fixed, then I'll re-root it later.
Phone: AT&T Galaxy S4
Baseband: I337UCUAMF3 <I know the MF3 isn't good for rooting now
Model: Samsung SGH-I337
Android version: 4.2.2
Device Status: Custom
Thanks for any help!
Update: Managed to get rooted again, using this method: http://forum.xda-developers.com/showthread.php?t=2387577. Calling still doesn't work, and (forgot to mention this before) oddly, if I push numbers on the number pad on my phone, you can hear the tones on the phone I'm connected to. Just can't hear me.
steven2k7 said:
I have a Galaxy S4 from AT&T. I got it a few months ago, rooted it a few weeks after I got it. Randomly about a week ago, when I would make or receive a phone call, I could not hear the phone ringing, couldn't hear the person talking and they couldn't hear me. The only two ways I found it would work is if I booted into safe mode or I was connected to my cars bluetooth. I have no idea what caused it and I haven't messed with anything (like installing apps or changing settings) anywhere around the time it happened. I did many factory resets and hard key resets but nothing fixed it. I saw I had an OTA update so I did that (which I now realize was a big no-no -_-).
Since I did the OTA update while still rooted, that seems to have messed up my root. I seem to be both rooted and not rooted. So in trying to fix my first problem, I created the second problem. To solve both of these, I've been trying to install a fresh stock ROM onto the phone (to nothing but failure). I was trying to remove the root and put it back to stock incase I had to send it in for repairs. I found a few guides/posts from other people who did the OTA update while rooted but I couldn't seem to get it to work. It mostly consisted of re-rooting the phone, then un-rooting it but I could never get the phone to actually show that it was rooted.
(I just tested the phone part of my phone to see if it was working. Called it, and I could hear and be heard fine. Hung up, waited a few minutes and tried again and it didnt work at all. Both times were while it has been turned on for several minutes).
Does anyone know how I can get back to as close to stock as I can get so I can at least get the actual calling part of my phone fixed? Either see if something to do with the rooting is causing the problem or at least let me send it in to get it fixed, then I'll re-root it later.
Phone: AT&T Galaxy S4
Baseband: I337UCUAMF3 <I know the MF3 isn't good for rooting now
Model: Samsung SGH-I337
Android version: 4.2.2
Device Status: Custom
Thanks for any help!
Update: Managed to get rooted again, using this method: http://forum.xda-developers.com/showthread.php?t=2387577. Calling still doesn't work, and (forgot to mention this before) oddly, if I push numbers on the number pad on my phone, you can hear the tones on the phone I'm connected to. Just can't hear me.
Click to expand...
Click to collapse
bro best solution for yu is to FLASH THE STOCK FIRMWARE THROUGH ODIN AND DEN ROOT UR DEVICE..
IT WILL SOLVE UR PHONE CALL PROBLEMS TOO
siva aggzz said:
bro best solution for yu is to FLASH THE STOCK FIRMWARE THROUGH ODIN AND DEN ROOT UR DEVICE..
IT WILL SOLVE UR PHONE CALL PROBLEMS TOO
Click to expand...
Click to collapse
I've been trying to flash the stock firmware, or at least I think its the stock firmware I need for it. Odin keeps giving me an "aboot" then "fail" errors as soon as I start the flashing process. Since I upgraded the software, is it even possible to install an older version of it back on?
steven2k7 said:
I've been trying to flash the stock firmware, or at least I think its the stock firmware I need for it. Odin keeps giving me an "aboot" then "fail" errors as soon as I start the flashing process. Since I upgraded the software, is it even possible to install an older version of it back on?
Click to expand...
Click to collapse
yup...if yu have nandroid backup den restore it with cwm/twrp... and if not
den flashing stock firmware is the only solution for yu to solve ur problem
siva aggzz said:
yup...if yu have nandroid backup den restore it with cwm/twrp... and if not
den flashing stock firmware is the only solution for yu to solve ur problem
Click to expand...
Click to collapse
Will I be able to flash the stock firmware after doing the OTA update? My baseband version is I337UCUAMF3 and the only ROM versions I can find are I337UCUAMDL and I337UCUAMDB.
steven2k7 said:
will i be able to flash the stock firmware after doing the ota update? My baseband version is i337ucuamf3 and the only rom versions i can find are i337ucuamdl and i337ucuamdb.
Click to expand...
Click to collapse
yup yu can ...stock rom can b flshed at any tym yu want except wen the mobile has hard bricked
hit thanks rather then typing bro
siva aggzz said:
yup yu can ...stock rom can b flshed at any tym yu want except wen the mobile has hard bricked
hit thanks rather then typing bro
Click to expand...
Click to collapse
Is there a version or a download you recommend I use? I have I337UCUAMDB that is a .tar.md5 file, but when I use Odin to flash it, it gives an Aboot warning then fail about 2 seconds after I start it. How can I fix that? Do I need to be rooted or not before I flash an update, or does it matter?
steven2k7 said:
I have a Galaxy S4 from AT&T. I got it a few months ago, rooted it a few weeks after I got it. Randomly about a week ago, when I would make or receive a phone call, I could not hear the phone ringing, couldn't hear the person talking and they couldn't hear me. The only two ways I found it would work is if I booted into safe mode or I was connected to my cars bluetooth. I have no idea what caused it and I haven't messed with anything (like installing apps or changing settings) anywhere around the time it happened. I did many factory resets and hard key resets but nothing fixed it. I saw I had an OTA update so I did that (which I now realize was a big no-no -_-).
Since I did the OTA update while still rooted, that seems to have messed up my root. I seem to be both rooted and not rooted. So in trying to fix my first problem, I created the second problem. To solve both of these, I've been trying to install a fresh stock ROM onto the phone (to nothing but failure). I was trying to remove the root and put it back to stock incase I had to send it in for repairs. I found a few guides/posts from other people who did the OTA update while rooted but I couldn't seem to get it to work. It mostly consisted of re-rooting the phone, then un-rooting it but I could never get the phone to actually show that it was rooted.
(I just tested the phone part of my phone to see if it was working. Called it, and I could hear and be heard fine. Hung up, waited a few minutes and tried again and it didnt work at all. Both times were while it has been turned on for several minutes).
Does anyone know how I can get back to as close to stock as I can get so I can at least get the actual calling part of my phone fixed? Either see if something to do with the rooting is causing the problem or at least let me send it in to get it fixed, then I'll re-root it later.
Phone: AT&T Galaxy S4
Baseband: I337UCUAMF3 <I know the MF3 isn't good for rooting now
Model: Samsung SGH-I337
Android version: 4.2.2
Device Status: Custom
Thanks for any help!
Update: Managed to get rooted again, using this method: http://forum.xda-developers.com/showthread.php?t=2387577. Calling still doesn't work, and (forgot to mention this before) oddly, if I push numbers on the number pad on my phone, you can hear the tones on the phone I'm connected to. Just can't hear me.
Click to expand...
Click to collapse
No u dnt need to b rooted bro for flashing stock rom...
siva aggzz said:
No u dnt need to b rooted bro for flashing stock rom...
Click to expand...
Click to collapse
I can't get the stock roms to flash. I've tried I337UCUAMDB and I337UCUAMDL, used different USB ports and different computers and they all fail right away. Do you know where I can find a I337UCUAMF3 rom?
steven2k7 said:
I can't get the stock roms to flash. I've tried I337UCUAMDB and I337UCUAMDL, used different USB ports and different computers and they all fail right away. Do you know where I can find a I337UCUAMF3 rom?
Click to expand...
Click to collapse
Did you Tried the official Samsung firmware site?
http://www.sammobile.com/firmwares/
Fantassy123 said:
Did you Tried the official Samsung firmware site?
http://www.sammobile.com/firmwares/
Click to expand...
Click to collapse
Yeah, its not listed there, just two older ones that I can't get to work on my device.
Edit: Just realized my device isn't showing that its custom now. When I boot, I have the normal 'Samsung Galaxy S4' splash screen and in about device, the secure boot status is Samsung. I think I got that somehow with GooManager. Still rooted though as far as I can tell. Tested the phone calling again and seems it only works when my S4 is on speaker phone. I may try and just call samsung tomorrow and see if they will ship me a new one.
Well, I solved the problem. Kinda. I called AT&T warranty support (1-800-801-1101), talked to a guy and ran him through everything I've done. He tried a few things on his end, asked around to see if anyone else had heard of a similar problem (no one had), and they are sending me a replacement and I send the old one back.
Related
Ok, here's the deal:
Rooted the device, everything was a-ok.
Installed Clockwork, everything still a-ok.
Tried using mod manager to install Cyanogen nightly 9, phone rebooted and the progress bar for the mod install wouldn't move. I waited for a while and eventually manually turned the device off as it wasn't making any progress.
Ever since, it won't go past the screen you get at the beginning (w/ the yellow sign indicating an unsecured rom). It just stays there forever.
What I have to work with:
- Clockwork Recovery is available.
- The device is recognized by Odin when in download mode.
- The device is not recognized by the computer/Kies.
What I've tried:
- Followed the instruction for boot loop w/ both stock rom and Villain (no dice).
I'm sorta freaking out now. I have yet to see anyone having the same problem online and I really hope it's not bricked - a 600$ paperweight...
Is there something else I can try? Is it possible to flash stock PIT/Bootloader/PDA/everything else? If it is, would it fix the problem?
Please just point me in the right direction.
Thank You,
Edit: In recovery mode, the following error appears:
- Can't access to "/system/csc/VMC/system/"
Edit: In download mode, the current binary is set to "Samsung Official". Therefore I think this isn't the problem.
Edit: OMG OMG holy crap. Problem has been solved. Got a friend who had the same phone from the same provider to tell me what the firmware for the phone was. Downloaded it. Installed it w/ Odin. I almost turned religious when it booted a bit slower than what I remembered. It works well enough now, although I will probably go exchange it for a new one ASAP, before my warranty expires.
If anyone has similar problems. Don't panic and re-install stock firmware.
Cheers Folks!
Rovah said:
Ok, here's the deal:
Rooted the device, everything was a-ok.
Installed Clockwork, everything still a-ok.
Tried using mod manager to install Cyanogen nightly 9, phone rebooted and the progress bar for the mod install wouldn't move. I waited for a while and eventually manually turned the device off as it wasn't making any progress.
Ever since, it won't go past the screen you get at the beginning (w/ the yellow sign indicating an unsecured rom). It just stays there forever.
What I have to work with:
- Clockwork Recovery is available.
- The device is recognized by Odin when in download mode.
- The device is not recognized by the computer/Kies.
What I've tried:
- Followed the instruction for boot loop w/ both stock rom and Villain (no dice).
I'm sorta freaking out now. I have yet to see anyone having the same problem online and I really hope it's not bricked - a 600$ paperweight...
Is there something else I can try? Is it possible to flash stock PIT/Bootloader/PDA/everything else? If it is, would it fix the problem?
Please just point me in the right direction.
Thank You,
Edit: In recovery mode, the following error appears:
- Can't access to "/system/csc/VMC/system/"
Edit: In download mode, the current binary is set to "Samsung Official". Therefore I think this isn't the problem.
Edit: OMG OMG holy crap. Problem has been solved. Got a friend who had the same phone from the same provider to tell me what the firmware for the phone was. Downloaded it. Installed it w/ Odin. I almost turned religious when it booted a bit slower than what I remembered. It works well enough now, although I will probably go exchange it for a new one ASAP, before my warranty expires.
If anyone has similar problems. Don't panic and re-install stock firmware.
Cheers Folks!
Click to expand...
Click to collapse
Same problem. anyone?
Vincho said:
Same problem. anyone?
Click to expand...
Click to collapse
Did you read the answer ???
jje
Look online (samfirmware), ask friends or on forums for anyone who has the SGS2 w/ the same carrier in the same country and try to find the firmware version (I9100***** - the stars are letter codes). Then just download that firmware and use Odin to install it.
If you can't find it,you presumably could just flash any stock firmware and it might work (or it might make things worse, try at your own risk)
Rovah said:
Tried using mod manager to install Cyanogen nightly 9, phone rebooted and the progress bar for the mod install wouldn't move. I waited for a while and eventually manually turned the device off as it wasn't making any progress.
Click to expand...
Click to collapse
The progress bar not moving is a known issue with the CM7 Recovery. All you need to do is wait for it to say that it's finished. There is nothing wrong with your phone and no need to return it. You just cancelled the CM7 install part way through which meant not all required files were installed on the phone, causing it to not boot.
As for it taking longer to boot into android after the odin reflash. That's because it has to build up it's dalvik-cache again. This is completely normal any time you install a new rom. It only happens on first boot of a rom.
So again, no need to return your device and feel free to try CM7 again. Just remember to let it finish even if the progress bar isn't moving.
Ahh. Ok that makes sense. This ought to teach me to read before screwing around w/ my phone.
I wanted to exchange it because I wasnt sure i'd still be able to install official Samsung firmware updates through Kies.
Suppose an official 2.3.4 firmware comes out, would i be able to install it through Kies?
Sent from my GT-I9100 using XDA App
Rovah said:
Ahh. Ok that makes sense. This ought to teach me to read before screwing around w/ my phone.
I wanted to exchange it because I wasnt sure i'd still be able to install official Samsung firmware updates through Kies.
Suppose an official 2.3.4 firmware comes out, would i be able to install it through Kies?
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Yes, as long as the firmware you're flashing is the same as the stock version that came on the phone. And even if not, you'll get the kies updates for whatever region firmware you did flash onto the phone.
I see. Thanks a lot!
Is there any danger to flashing firmware from a different region than the one youre from?
Sent from my GT-I9100 using XDA App
Hi All,
I have had my S3 for about 6 months now, in November 2011 after taking a call my phone turned off and refused to turn back on. I did all the usual stuff, taking the battery out, trying recovery mode etc but nothing worked. Searched Google and forums and basically said it was a known fault with some of the S3's and it'd have to go off to be repaired. It came back within 2 weeks and worked great again.
Yesterday, the LED was flashing blue so went to look at incoming message / email and it wouldn't come to life...exactly the same problems as before! I was gutted. My conclusion is that it will have to go off and be repaired / replaced. My question is, is this likely to be happening because I rooted my phone with the CF-Root-SGS3-v6.3? I have had no other issues.
Thank you
you need to use a kernel that has the sudden death fixed
Glebun said:
you need to use a kernel that has the sudden death fixed
Click to expand...
Click to collapse
So if I can find another CF-Root version it should be okay once I get it back from being 'repaired'
chrisbrawn said:
So if I can find another CF-Root version it should be okay once I get it back from being 'repaired'
Click to expand...
Click to collapse
Yes. Assuming your repaired phone is running a recent build of the stock ROM, it will include the fixes for the brick bug. You can then root as you did before. I would also flash a more recent recovery, the CWM bundled with CF-Root is out of date.
Thanks greatly!
I have found the following root file: CF-Auto-Root-m0-m0xx-gti9300.tar
Does anyone know (providing it matches my phone when it come back from Carphone Warehouse) if this is the most recent one?
If it's for the I9300, it'll work.
I still prefer to flash some custom recovery and flash zip SuperSU..
I've just bought myself a USB JIG..I'm going to try to recover it myself. My problem is that it won't turn on, the USB JIG appears to be able to boot it into download mode. I can then use odin to flash a stock rom, which i'm downloading from SamMobile.
What custom recoveries would you suggest?
Hello guys please hear me out!
I'm new to android as well as this forum, but I hear it's a great community. I followed a lot of tuts on how to upgrade my S2 to jelly bean or ics none of them really worked.
OK my friend got me the phone from amazon it's a Samsung Galaxy S2 International Version 16gb Unlocked with 2.3.5 Gingerbread stock firmware. The following day I tried to upgrade the unrooted firmware via KIES, it told me there is no update available for my phone. Okay I decided to root it and flash it though odin. I read that it was wise to back-up the software first and boy was it! So I rooted it and backed it up with ClockworkMod to an sd card just in case. But I forgot to get the other information before I flashed: original Baseband version, Kernel and Build number.
The flashing went fine I got 4.1.2 on my phone but I lost the network service, the lock screen and the turn off key dialog (the phone would just turn off as soon as i hit the off button). Rooted it, installed a different 4.1.2 firmware, same thing. Then I tried ICS, it was worse - I had similar issues as well as the home key was not working when multitasking. So I went back to original backed up rom. Everything works fine now but the baseband version remains from the last "update". Everytime I try a new firmware and go back to the original rom the last baseband sticks.
My question is: Is it at all possible to upgrade my phone? My kernel (from backedup rom) is I9100XXKI3 and build number gingerbread.XXKI3 Imei is fine.
Also my binary data counter is up to 7, is that bad?
Any help I will greatly appreciated! I badly want to upgrade, it's the whole reason I got S2 because it was supposed to be "upgradeable"
Thank youuuu.
iceman8443 said:
I followed a lot of tuts on how to upgrade my S2 to jelly bean or ics none of them really worked.
Click to expand...
Click to collapse
Read every word of a thread at least once before even attempting anything then make sure you have all the files you need ready to be used in their relevant places too and try again. When People claim to have read lots of tutorials and guides that have worked for the majority of People but can't get something to work then it's usually down to user error, i.e skimming through guides and missing a vital step that throws the whole thing off.
http://forum.xda-developers.com/showthread.php?t=1826497
iceman8443 said:
Hello guys please hear me out!
I'm new to android as well as this forum, but I hear it's a great community. I followed a lot of tuts on how to upgrade my S2 to jelly bean or ics none of them really worked.
OK my friend got me the phone from amazon it's a Samsung Galaxy S2 International Version 16gb Unlocked with 2.3.5 Gingerbread stock firmware. The following day I tried to upgrade the unrooted firmware via KIES, it told me there is no update available for my phone. Okay I decided to root it and flash it though odin. I read that it was wise to back-up the software first and boy was it! So I rooted it and backed it up with ClockworkMod to an sd card just in case. But I forgot to get the other information before I flashed: original Baseband version, Kernel and Build number.
The flashing went fine I got 4.1.2 on my phone but I lost the network service, the lock screen and the turn off key dialog (the phone would just turn off as soon as i hit the off button). Rooted it, installed a different 4.1.2 firmware, same thing. Then I tried ICS, it was worse - I had similar issues as well as the home key was not working when multitasking. So I went back to original backed up rom. Everything works fine now but the baseband version remains from the last "update". Everytime I try a new firmware and go back to the original rom the last baseband sticks.
My question is: Is it at all possible to upgrade my phone? My kernel (from backedup rom) is I9100XXKI3 and build number gingerbread.XXKI3 Imei is fine.
Also my binary data counter is up to 7, is that bad?
Any help I will greatly appreciated! I badly want to upgrade, it's the whole reason I got S2 because it was supposed to be "upgradeable"
Thank youuuu.
Click to expand...
Click to collapse
Go to sammobile.com
Click on firmware
Type in the searchbar: gt-i9100
Search for your country or the one thats the closest to ya
Download the file
Once downloaded set your s2 in download mode by pressing volume down, home en power buttons
Plug in your s2 into your comp
Open Odin
Press the PDA button
Choose the ....home....tar.md5 you downloaded
Make shure that re-partion, f reset time and auto reboot are checked
And hit the start button
If your phone rebooted check and you must be running on 4.1.2...
After that root it... And do what you wanna do
The binary counter doesn't meane something worse... Its only a counter thats counting how manny custom roms you have flashed...
You can reset it with a usb jig or triangle away app in the playstore... ( the app doesn't work always...)
XperienceD said:
Read every word of a thread at least once before even attempting anything then make sure you have all the files you need ready to be used in their relevant places too and try again. When People claim to have read lots of tutorials and guides that have worked for the majority of People but can't get something to work then it's usually down to user error, i.e skimming through guides and missing a vital step that throws the whole thing off.
http://forum.xda-developers.com/showthread.php?t=1826497
Click to expand...
Click to collapse
Thank you guys for the replies however do you know anything about my weird issues, like the lockscreen not working after update, then no network service and the power off dialogue missing completely. I've tried at least 3-4 different jelly bean firmwares and always i got the same issues.
I live in Kosovo and i downloaded the Greek firmware which I'm going to try next. I'm going to go through pelpa87's thread you suggested and hopefully it will work and I will report back.
Thanks again.
Edit: thanks for the help guys, last night I installed jelly bean and it works great without any issues.
A couple of weeks ago I bought a Galaxy Note 2 from Simple Mobile began to experiment with it. Later on I managed to root it, but I accidentally flashed a recovery via Rom Manager which after a restart broke my phone.
After that I flashed a OTA through Odin of Verizon 4.1.2. The system booted and everything but the radio was missing meaning that I could not text or use 3G. I looked for many ways to restore it but none worked.
I later on flashed a T-Mobile ROM thinking it will help restore the radio and it did successfully flash the ROM through the recovery. But the ROM turned out to be 4.3 and the radio still didn't work. Later on in the same day I flashed an OTA of T-Mobile through Odin and that's when this happened. My phone bootloops really fast when I turn it on. The recovery doesn't show up at all. And every time I flash anything through Odin it fails. I've felt ashamed all this time and it took me a while to reflect and face what I've done and decided to post on here to get help.
Thanks for reading! Any help is appreciated. I will try every method that gets posted and will post back results.
Chronosin said:
A couple of weeks ago I bought a Galaxy Note 2 from Boost Mobile began to experiment with it. Later on I managed to root it, but I accidentally flashed a recovery via Rom Manager which after a restart broke my phone.
After that I flashed a OTA through Odin of Verizon 4.1.2. The system booted and everything but the radio was missing meaning that I could not text or use 3G. I looked for many ways to restore it but none worked.
I later on flashed a T-Mobile ROM thinking it will help restore the radio and it did successfully flash the ROM through the recovery. But the ROM turned out to be 4.3 and the radio still didn't work. Later on in the same day I flashed an OTA of T-Mobile through Odin and that's when this happened. My phone bootloops really fast when I turn it on. The recovery doesn't show up at all. And every time I flash anything through Odin it fails. I've felt ashamed all this time and it took me a while to reflect and face what I've done and decided to post on here to get help.
Thanks for reading! Any help is appreciated. I will try every method that gets posted and will post back results.
Click to expand...
Click to collapse
I have a very similar problem. hope you get help on this, I have been trying to fix this problem for a month.
The 4.3 update is where the issue came from if it will allow you to flash try using a custom rom to get you out the boot loop but because the 4.3 bootloader is locked you now have another issue you will now have to run a virtual rom and there is a certain way you have to do it or you will completely brick your phone try researching first Google your phone model with the rom build 4.3 root you have to root it now before you can do any modifications at this point
Sent from my SCH-I605 using XDA Free mobile app
I decided to get my girlfriend a Verizon SCH-I545 to replace her T-Mobile Galaxy S3. It was working great on our T-Mobile service. Then I saw online that Verizon had released lollipop on their S4, so I figured I would plug the phone into Kies and update it from 4.4.2 to 5.0.1. I updated it overnight. When she went to use it in the morning, everything worked great, except it wouldn't send a text message. T-Mobile and Samsung support said that it is because T-Mobile hasn't released their lollipop rom for the S4 yet. I figured the best thing to do would be to roll back the firmware. Having done some rooting and custom roms on my old galaxy S2 Epic 4g Touch, I felt like I knew exactly what to do. I downloaded multiple ROMs and tried to install them through ODIN and through stock recovery. Nothing took. Finally after trying about 10 things, I soft bricked the phone. I can still get into download (ODIN) mode, but I can't get into stock recovery anymore. When I try to go into stock recovery it gives me this message: "Software Update Failed" "Your device didn't update successfully. Use the Verizon Software Repair Assistant on a computer to repair your device and complete the update." But, while the phone was still able to boot into android, the phone installed the Verizon Software Repair Assistant. I attempted to use it to rollback to 4.4.2 and the Assistant told me that it couldn't do anything to repair 5.0.1.
What I need to accomplish is either getting the phone back to 4.4.2 or 5.0.1 with text messaging working by any means necessary. Before I soft bricked the phone, I was hoping to avoid changing from stock recovery, but at this point I'm willing to do whatever I need to. For compatibility reasons, I hoped to try to keep her on a stock rom. If anyone knows of a rom with no bugs and a close to stock experience, I'll gladly set her up any way you guys think I should.
Thank you in advance for your assistance. I apologize for being "long winded" but I wanted to try and give as much detail as possible.
Still looking for any help I can get in resolving these issues.
You can't flash custom recovery for anything newer than 4.3 you will just jack up your phone trying.
Is both Talk & Data working??? SMS might be just improper APN settings. Google the APN for T-Mobile and that should fix it.
Since you installed 5.0.1 over Kies you are kind of stuck cause that would have updated the baseband and you can't have anything older than the baseband version.
Try installing this over Odin:
https://www.androidfilehost.com/?fid=23991606952596145
If you have Odin 3.09 or 3.10 choose AP to load the file. Make sure its unzipped too.
google luck!
somewhat resolved
I'm no longer soft bricked. I just got that back up and going. However the phone will still not send text messages. From what I've found, this only happens on 4g LTE. But, data, incoming texts, phone calls, mms, and everything else has been working just fine.
Yeah, you can curse Verizon for this. They lock down everything. A lot of people are flashing the Verizon version of Lollipop which screws their phone. I would show you a fix for that, but you need root, and OC1 doesn't have it yet. No fix for this because you can't Odin back and there is no root.
if you look at the link i posted its a version of Lollipop that lets you flash back to KitKat. It only works if you never installed lollipop. Unfortunately for me my phone wont read my sim card anymore its pretty much just a small tablet.
cwa82 said:
if you look at the link i posted its a version of Lollipop that lets you flash back to KitKat. It only works if you never installed lollipop. Unfortunately for me my phone wont read my sim card anymore its pretty much just a small tablet.
Click to expand...
Click to collapse
Sadly I had upgraded to lollipop, which is what created my problems to begin with. If I had never updated, text messages would've always worked, and ib never would have soft bricked the phone trying to roll back to kit-kat. I'm just glad I got the soft brick fixed, now I just have to wait for a fix on the text messaging.
bigg6987 said:
Sadly I had upgraded to lollipop, which is what created my problems to begin with. If I had never updated, text messages would've always worked, and ib never would have soft bricked the phone trying to roll back to kit-kat. I'm just glad I got the soft brick fixed, now I just have to wait for a fix on the text messaging.
Click to expand...
Click to collapse
You might be better off just buying her a different phone and selling that one.