I've got a Hero running LiquidSense and everything's working great. Except that I dropped the phone and now the earpiece stopped working. So I was going to try and get a refurb from Sprint. I made a fresh Nandroid backup of the phone and plan to restore it to my replacement phone (assuming Sprint gives me one). But will that restore my SMS text messages, too?
Your concern should really be can a nand on one phone be restored to another. If that's the case, then yes your sms, and everything, are in there.
AFAIK It just makes an image of the current state of your phone it really doesn't even know/care what it's backing up.
If it can be restored, it will be like you never left it. (Except for a few special things like the prl and the radio, afaik.)
Is there any reason I wouldn't be able to restore a Nandroid backup on one Sprint HTC Hero to another? Assuming the original was no longer in-use?
bsmith1051 said:
Is there any reason I wouldn't be able to restore a Nandroid backup on one Sprint HTC Hero to another? Assuming the original was no longer in-use?
Click to expand...
Click to collapse
I don't see any reason why it shouldn't work once the new phone is rooted.
Sent from my HERO200 using XDA App
I'll bet they can actually fix the phone.
Yesterday my earpiece stopped working (speakermic still worked) brought it to my local non-Sprint Sprint store and 15 minutes later it was all better. They even did it for NO CHARGE (my phone is out of warranty and I have no insurance on it)
bsmith1051 said:
I've got a Hero running LiquidSense and everything's working great. Except that I dropped the phone and now the earpiece stopped working. So I was going to try and get a refurb from Sprint. I made a fresh Nandroid backup of the phone and plan to restore it to my replacement phone (assuming Sprint gives me one). But will that restore my SMS text messages, too?
Click to expand...
Click to collapse
Alright, I've read the forum rules and I've scowered XDA forums for all the different problems I've had on my Galaxy Tab and I fear I've just made it worse. I purchased a refurbished TAB from AT&T. I decided to use it for a while to make sure it's all good before I hack the heck out of it. (good idea) I found that after a while, if I have bluetooth enabled the device would act like the CPU is pegged at 100% and could barely run. If I got BT disabled, it would run fine again. I decided to call AT&T which was a mistake in the first place. After 5 call transfers and a very rude AT&T rep telling me I have to talk to Samsung, I hung up. I decided to flash the rom myself to try and get rid of the problem (bad flash?). I flashed ROTO's roms and now every rom I flash, any rom I can get my hands on, has the Back Button problem. It's like It's holding down the back key. I wanted to send it in for repair (after googling and realizing that alot of samsung products have this problem) but realized that I unlocked my bootloader and can't go back to an original rom Does anyone have a rotobackup of an AT&T tab I could use? Or maybe should I brick the device and send it in? saying it was a bad kies flash? Any help would be appreciated. Also, if there is an original AT&T rom out there I could put back I would, but I can't find it. I've been on samfirmware.com and the like to no avail. Thanks Again!
TopHatHacker
(P.S. I found that Noob video when you sign up quite entertaining )
One of the gingerbread roms may work by upgrading the bootloadwr (at your own risk)
Sent from my GT-P1000 using XDA App
Hey Thanks
hey thanks, i have tried that rom. the euro gingerbread rom was actually the first one that i tried and the first one that gave me problems. I actually bricked it trying to flash another rom and so I just said to heck with it and sent it in. worst case is they fix it and charge me? do they warranty their fix if I pay for it? I mean if they just reflash it and don't fix the hardware issue (which i know there is one) will they fix it again?
I have two ATT note 3's, my own, which is on 4.3 and rooted, and my wife's is completely stock. Mine tried to do the OTA update but fails to complete, most likely because I'm rooted, I'm guessing. Her OTA went through and she was updated to 4.4.2. Since the update SMS appears to send out fine from the phone, but never actually does based on testing. The APN settings initially reverted back to AT&T, so after setting that back, mobile data worked fine again.
We both recently ported from AT&T to Striaght Talk and use an AT&T Microcell in our home. It has all been working well until the 4.4.2 update to her phone, that's all that changed.
I have tried quite a few different APN settings but have seen no change. Right now I am not sure if this is an Android issue or Straight Talk issue. I've done the very obvious things like rebooting the phone, I'm just unsure on what the next troubleshooting steps would be, other than contacting Straight Talk or googling these symptoms, but it's just a very broad problem to find a specific fix for.
Last Friday I noticed that I stopped receiving texts on my unlocked DE running stock rooted 4.4.4. Sending texts works fine. This phone has never had any problems with anything since I started using it 18 months or so ago, and out of the blue it stopped receiving texts. I have checked Verizon's side on another phone (moved sim card to old Gnex and texts are received fine) and it is definitely a problem with my phone. I have deleted all texts, wiped caches, tried Safe Mode nothing has fixed it. Seems like some odd radio problem. I have read about the 4.4.4 issues others have had, but as I mentioned, this phone has been fine on 4.4.4 since I set it up.
In any event, I am here looking for some answers or some suggestions of what else to try. I would like to keep the total wipe and restore as a last resort, as this phone is mission critical to me for work, and being too stupid to do regular backups, resetting everything back to the way it is now would be a hardship. I do have a nandroid backup from when I originally set up the phone, and was thinking of trying that. If I wipe everything though, does that wipe the SD card too? I thought a factory reset wipes the SD card, so if so I need to back it up first.
(So this is interesting... I was using Verizon's Messaging app and went to the "Subscribe" in the integrated messaging feature in the Settings area, and when I do that it basically hangs and finally goes back to the messaging app. A few minutes later I get the following error message, "Failed to retrieve security code. Please try to connect again later by using the Subscribe option withing the Settings screen.". The error message comes in like a text (with notification). Googling this error really yields no real information, however I wonder if there is something to the security thing. Not sure how to investigate, though...)
Thanks in advance for anything you guys can offer!
In my case, and others, this problem was solved as indicated in post #25 by qtonic (thanks to you, qtonic!). In my case, VVM was not an issue as I did not use that feature, so I can't vouch for whether or not that problem is solved. No "factory reset" was involved, nor any "upgrade" to Lollipop was necessary, so no worries there. One important note is to backup your texts if you want to restore them after you clear the data. I did that and I am back up and running with all my old texts in place. Hopefully this fix works for everyone experiencing this issue.
Same thing happened to me. I was running eclipse rom 4.4.4 I had to upgrade to lollipop to get texts working again. Which sucks cuz I think kit Kat is better. I'm wondering if it's all 4.4.4 where this happens?
cnoevl21 said:
Same thing happened to me. I was running eclipse rom 4.4.4 I had to upgrade to lollipop to get texts working again. Which sucks cuz I think kit Kat is better. I'm wondering if it's all 4.4.4 where this happens?
Click to expand...
Click to collapse
Did you try a wipe and reinstall first before trying the lollipop upgrade? Are you running a rom now or stock rooted lollipop?
I am dealing with the same issue. Don't want to upgrade to lolly or do i want to factory reset. I will stay tuned to this thread and hopefully get a fix.
Sent from my XT1060 using XDA Free mobile app
amajamar said:
Did you try a wipe and reinstall first before trying the lollipop upgrade? Are you running a rom now or stock rooted lollipop?
Click to expand...
Click to collapse
i just wiped cache and dalvik. then went to lollipop. it then dawned on me that i should have tried to wipe kitkat, but when u switch to LP it screws everything up so idk if you can go back to kitkat. i may try to at some point, maybe over the weekend.
right now im just running a debloated stock LP rom and i used xposed to customize.
I just added the following to my OP.
So this is interesting... I was using Verizon's Messaging app and went to the "Subscribe" in the integrated messaging feature in the Settings area, and when I do that it basically hangs and finally goes back to the messaging app. A few minutes later I get the following error message, "Failed to retrieve security code. Please try to connect again later by using the Subscribe option withing the Settings screen.". The error message comes in like a text (with notification). Googling this error really yields no real information, however I wonder if there is something to the security thing. Not sure how to investigate, though...
Can you guys duplicate this?
Any solutions other than factory wipe?
Having this issue on both my Moto X developer edition phones. One stock software it stopped receiving texts yesterday one running a custom Rom which stopped receiving texts last thursday.
Verizon's answer is some of the provisioning code implemented when I activated the phones is no longer supported and they have changed whatever they have to change but the phone has to be factory reset and activated in order to be reprogrammed with the proper provisioning. Verizon said it is motorola's problem.
I honestly have no idea what all that means that is what they kept repeating to me.
I really don't want to have to do a factory reset.
ray4jc said:
Having this issue on both my Moto X developer edition phones. One stock software it stopped receiving texts yesterday one running a custom Rom which stopped receiving texts last thursday.
Verizon's answer is some of the provisioning code implemented when I activated the phones is no longer supported and they have changed whatever they have to change but the phone has to be factory reset and activated in order to be reprogrammed with the proper provisioning. Verizon said it is motorola's problem.
I honestly have no idea what all that means that is what they kept repeating to me.
I really don't want to have to do a factory reset.
Click to expand...
Click to collapse
I went up several levels of tech support at Verizon and eventually ended up getting the same story. I need a factory reset and then all will be fine. They said it was due to some voicemail interface version not being supported anymore and my phone is trying to use the old one and it's keeping the phone from provisioning and that's why texts stopped working.
I've been putting off applying the Lollipop update because I knew it was going to have undesired consequences, but I went ahead and applied it. Text work again but of course I had to re-root (Developer Edition so no sweat there) and even with root WiFi Tether for Root Users (which had been working great under KitKat) bit the dust and no longer works. Under KitKat I had to use the special version that had some added binaries to make up for pieces that were missing from the kernel and I guess those binaries don't work with the Lollipop kernel.
So I'm using the stock tether app now (with provisioning check disabled) but I hate it. You can't turn on access control lists (to "approve" users), you can't see who's connected, you can't define an inactivity timeout, blah blah blah. It sucks so bad compared to WiFi Tether for Root Users.
Oh yeah, in the process of troubleshooting they removed voicemail from my line and put it back on. So I had to set up my voicemail from scratch and lost a bunch of voicemails I'd been saving for years including one from a friend who's dead now. Not happy.
Eh, at least SMS works again.
ray4jc said:
Having this issue on both my Moto X developer edition phones. One stock software it stopped receiving texts yesterday one running a custom Rom which stopped receiving texts last thursday.
Verizon's answer is some of the provisioning code implemented when I activated the phones is no longer supported and they have changed whatever they have to change but the phone has to be factory reset and activated in order to be reprogrammed with the proper provisioning. Verizon said it is motorola's problem.
I honestly have no idea what all that means that is what they kept repeating to me.
I really don't want to have to do a factory reset.
Click to expand...
Click to collapse
Yes, for me it was last Thursday that it was working as well. So, that being said, I take it a factory wipe is required. A couple of questions for you guys: Since I have a Developer Edition (running Xposed) too, do I have anything to worry about about doing a factory wipe? I am currently on 4.4.4, rooted, do I need to prep anything to do the factory wipe so I don't brick? Can I stay on 4.4.4 and just re-root and reinstall my apps from TiBU? I haven't messed around with anything since setting it up over a year ago, and not really thrilled with starting from scratch...
Anyway, great sleuthing MotoCache1, seems that you got to the bottom of things. At least we can be sure it was not some other app or something causing this.
I have the same setup so I am very interested too...on how to set this all up. I use my phone to tether a lot...how will I go about this with lollypop?
Sent from my XT1060 using XDA Free mobile app
mlucht said:
I have the same setup so I am very interested too...on how to set this all up. I use my phone to tether a lot...how will I go about this with lollypop?
Sent from my XT1060 using XDA Free mobile app
Click to expand...
Click to collapse
If you're rooted edit your /system/build.prop file, add this line to the end, reboot the phone, and then use the factory hotspot tethering:
Code:
net.tethering.noprovisioning=true
More information here if you want it.
I backed everything up and did a factory reset but still no text coming in. Maybe I didn't do it right?
I booted into TWRP and picked factory reset, can anyone tell me if there is something more I need to do besides that??
And to reiterate what has been said verizon again just told me
To correct issue
1-Visual Voice Mail must be removed from account (if it has not been done already)
2-Device data must be backed up
3-Master/Factory reset required on device
But those things have been done and my text still aren't coming in. So they said they would escalate it....
ray4jc said:
I backed everything up and did a factory reset but still no text coming in. Maybe I didn't do it right?
I booted into TWRP and picked factory reset, can anyone tell me if there is something more I need to do besides that??
And to reiterate what has been said verizon again just told me
To correct issue
1-Visual Voice Mail must be removed from account (if it has not been done already)
2-Device data must be backed up
3-Master/Factory reset required on device
But those things have been done and my text still aren't coming in. So they said they would escalate it....
Click to expand...
Click to collapse
That's what they told me as well. They said "take it in to a Verizon store and they will back it up and do a factory reset and then restore your data".
I decided against that and instead opted to use the VZW Software Repair Assistant tool. When you use that there are 2 options - Software Repair Assistant (which is supposed to "repair" your currently installed software) and Software Upgrade Assistant (which is supposed to update your device to the latest available software for it).
I didn't particularly want to go to Lollipop so I chose the "repair" option, chose the phone, and clicked "Repair". And it "repaired" it by upgrading it to Lollipop. Lol. Maybe it's because I had previously told the phone to go ahead and try to apply the Lollipop OTA. The OTA failed to install. Not sure why - possibly due to root and/or other changes to the system partition. I was using stock recovery.
So anyway, I ended up on Lollipop even though that's not really what I wanted to do, and that did fix the problem - though, as previously bemoaned, I can't use WiFi Tether for Root Users anymore and have to use the piece of crap that's built into the OS. I guess I should be grateful that works because I'd be in a pickle if I had to do without tether.
Back to what you posted -- I don't think anybody here has yet posted that the factory reset actually fixed the problem for them. Honestly I don't understand how it would. A factory reset isn't going to suddenly make your phone start using a newer version of anything and what I was told was that the phone was using an old, no longer supported version/protocol to access voicemail and that was the root of the problem.
I suspect that if you take it into a VZW store for a "factory reset" what you're really going to get is an upgrade to Lollipop. Lol.
@MotoCache1 so basically Verizon's treating us like idiots!
I just got done chatting with them (the agent finally just disconnected not sure why) and they told me to see if Motorola would replace the phone......yeah that isn't going to happen.
I chatted with Motorola and did a bunch of troubleshooting with them, they suggested trying a new sim card.
ray4jc said:
@MotoCache1 so basically Verizon's treating us like idiots!
I just got done chatting with them (the agent finally just disconnected not sure why) and they told me to see if Motorola would replace the phone......yeah that isn't going to happen.
Click to expand...
Click to collapse
Wow. Talk about a lame answer. Nothing on the phone changed. Nothing on the phone broke. Obviously Verizon changed something on their side and rather than back out, or fix it, they want to shift the problem to the device owners.
At least you know you can probably fix it by going to Lollipop (so far that seems to have fixed everyone that has posted here) but that comes with some negatives. I'd rather still be on KitKat personally, but I put too much time into it already so I'm just going to be satisfied that it's working and try to forget how much I hate the factory tether piece of crap.
Wow, I didn't even think to look here, I figured this problem was just my phone. I too lost the ability to receive text a few days back. After confirming it wasn't a SIM problem with another device, I did a factory reset and all was well. 4.4.4. I test texting every morning from AIM now, just to make sure it still works, but I'm afraid it'll happen again. Has anyone figured out what the actual problem is?
domenci said:
Wow, I didn't even think to look here, I figured this problem was just my phone. I too lost the ability to receive text a few days back. After confirming it wasn't a SIM problem with another device, I did a factory reset and all was well. 4.4.4. I test texting every morning from AIM now, just to make sure it still works, but I'm afraid it'll happen again. Has anyone figured out what the actual problem is?
Click to expand...
Click to collapse
Were you rooted prior to factory reset? Did you need to re-root? Did the factory reset wipe the SD card? I want to fix this without upgrading to lollipop if possible
Have you tried to factory reset and it didn't fix the problem? I don't understand, you have the option to try it with nothing to lose. Worse case scenario it doesn't work and you have to upgrade anyways.... either way better than using a 6 year old phone
That being said...
I was rooted. I did the factory reset from Settings in Android. Factory reset SAID it would wipe everything, but it didn't touch my 'sd card', so I wasted a lot of time transferring my backups to the computer, but better safe than sorry. Root remained after the reset. I also froze anything Verizon related with TiBu just in case it is the voicemail app (though I'm pretty sure it was frozen before).
domenci said:
Have you tried to factory reset and it didn't fix the problem? I don't understand, you have the option to try it with nothing to lose. Worse case scenario it doesn't work and you have to upgrade anyways.... either way better than using a 6 year old phone
That being said...
I was rooted. I did the factory reset from Settings in Android. Factory reset SAID it would wipe everything, but it didn't touch my 'sd card', so I wasted a lot of time transferring my backups to the computer, but better safe than sorry. Root remained after the reset. I also froze anything Verizon related with TiBu just in case it is the voicemail app (though I'm pretty sure it was frozen before).
Click to expand...
Click to collapse
I did try a factory reset and it didn't work. Of course I'm running the eclipse 4.4.4 ROM not sure if that matters.
Looking in TiBU I've only got a few Verizon apps, none of them appear to be for voicemail the only thing that says voicemail is the phone 4.4.4-26 (19) app.
I'd love to stay on 4.4.4 if possible.
Otherwise I need to figure out which ROM to go to next.
Warning / FYI:
After installing and running Nemesis Note 7 Rom, AT&T suspended my service tonight and also blocked / blacklisted my imei. Mind you I am using an N910T3 and have been flashing custom Roms on this note 4 since January of this year. I installed the ROM yesterday and have been messing with it up until 7:30 tonight when I realized I didn't have mobile data. I thought I broke something by flashing governor tuner but uninstalling it and reapplying data fixes wasn't working so I restored a backup that had no issues and still no data. Confirmed by logging into my at&t account that it had been suspended and then began a lengthy chat with at&t rep which is how I found out they blacklisted the imei also in addition to suspending service.
The representative was adamant that the phone imei had been blocked by TMobile, but a call to them confirmed that while at&t put in the blacklisting, reported the phone as stolen as soon as Nemesis ROM registered a note 7 to their system yesterday night, and that there was nothing in their system they could do to unblock the imei. I
Long story short, after explaining the concept of custom Roms to the rep, at&t has put an unblock request in to be resolved by the 14th, hopefully it works, and just a word of warning to everyone!
PS. I had also changed build.prop product model to SM-G935F shortly after installing yesterday, so the red flag must've gone into their system as soon as it went online. Maybe developers need to stop putting the N9300 as the product model stock to avoid this!!
Another thing just came to mind as well. Nemesis was the first rom I installed that required data fixes and all that jazz because it wasn't ported exclusively for a t-mobile device. I wonder if that also had anything to do with it, as running Aurora, Project L, etc. never triggered my carrier. Unless as they get closer to the 15th when they release that deathbed update for the note 7, they are getting more and more aggressive...
Wow that sucks! Thanks for the warning. I was considering one of the Note7 ports, guess I'll just stick to CyanogenMod for now.