Hi everyone.
I have a question regarding a small problem I have.
First of all, I have a Touch Diamond which I just installed "Dazzza.2.7.1_Final.V1E ROM" on with Radio 1.09.25.23.
I upgraded from the original HTC ROM (RUU_Diamond_HTC_SVE_1.93.413.3_Radio_Signed_Diamond_52.29.25.12_1.00.25.05_Ship.exe).
Before I started I ran a FULL backup using Spirit backup.
The actual ROM install went smooth and without problems, but when installing Spirit and trying to restore the data from privious ROM the device freezes at start up after reseting the device upon restore completion.
When it freezes the only thing I have on the screen is Touch DIAMOND (logo) and the version numbers of ROM, Radio etc in red text in the bottom right corner..
I have to hard reset to start the phone, and then of course the data is gone.
I realize that it is something that it is trying to restore that no longer works in the Dazzza ROM.
What I really miss from the backup is the contacts and text messages.
But where are they stored? If I knew that i could choose to restore only that info and pray that it isn´t that part that "corrupts" the phone..
So, any way to 1: Solve the whole problem so I can do a full restore? 2: Only restore contacts and text mess..
Crossing my fingers..
Related
Hello,
I am having a problem with my jasjam where after I view any sms (inbox, drafts etc) and try to exit from the screen, it gets stuck and only half of the Today screen is showing. The phone is frozen in that state and cannot access any menu again and must soft reset to get it to work again.
I've only experienced this within the last week or so and have not changed anything in that time other than having more smses come in.
Is there a limit on the number of smses that can be stored? I tried to delete some but it still causes the freeze whenever I'm looking at some sms.
Any ideas?
Thanks.
Are you using a custom rom? If so the rom may be the culprit
Yes I am using a TNT rom. I guess I'll try flashing a new one and see how I go.
a tnt rom caused that problem on wizard. Reflashed an official rom then went back to the TNT rom and that fixed it. If you like the rom you may flash an official rom the go back to the tnt.
Thanks for the tip. I think I might try another rom now that there are 6.1 versions around now. Now just need to find an offline sms and contacts backup before I flash again
I am using Pays-Rom v 1.9 but since 2.0 is out now i've been trying to upgrade. I made a number of android backups dating from 23/08/2010 up to today. I've successfully flashed the updated ROM but I was getting a google talk authentication error so I tried to revert to my most recent backup (yesterday - 27th). However once clockworkmod said it had been restored, my phone wouldn't boot past the white screen with the HTC logo.
Here's the thing, I tried an older backup from the 23rd and that worked so I was using it since yesterday as I thought I'd leave sorting out the update until today. But now when I flash the new rom it bootloops at Pays-Rom boot screen, and if I restore any nandroid backup later than the 23rd it doesn't boot past HTC logo.
I can always go back to the nandroid backup from the 23rd but I would like to update the ROM. Any Ideas why this is happening?
N.b. I've wiped data before every flash, and I've flashed w/o sim card everytime (this is what I did the very first time I rooted last week, I heard orange simlocks if you don't)
I'm considering trying a different ROM but idk so
narcoustic said:
I am using Pays-Rom v 1.9 but since 2.0 is out now i've been trying to upgrade. I made a number of android backups dating from 23/08/2010 up to today. I've successfully flashed the updated ROM but I was getting a google talk authentication error so I tried to revert to my most recent backup (yesterday - 27th). However once clockworkmod said it had been restored, my phone wouldn't boot past the white screen with the HTC logo.
Here's the thing, I tried an older backup from the 23rd and that worked so I was using it since yesterday as I thought I'd leave sorting out the update until today. But now when I flash the new rom it bootloops at Pays-Rom boot screen, and if I restore any nandroid backup later than the 23rd it doesn't boot past HTC logo.
I can always go back to the nandroid backup from the 23rd but I would like to update the ROM. Any Ideas why this is happening?
N.b. I've wiped data before every flash, and I've flashed w/o sim card everytime (this is what I did the very first time I rooted last week, I heard orange simlocks if you don't)
I'm considering trying a different ROM but idk so
Click to expand...
Click to collapse
This is purely a guess, but your SD card me be corrupt and that is causing the nandroid restore to become corrupted too. I'd try a new rom and repartition the card.
yeah I've tried other ROMs and they install fine so I think I'll just switch. Does anyone know the most efficient way to backup and restore all apps, sms, and contacts?
I've been using Titanium which is good but I've been having problems with it backing up my sms data, also I have to manually accept every app to install
Let me start by saying, I have searched all of the treads for my phone, and the ones suggested before posting a new one, with no luck. I also searched all over other sites for an answer, about 3 hours now, and still nothing that quite fits my problem..
I have a Verizon HTC Inc2
-running 2.3.4
-Virtuous Unity v2.39.0
The problem I keep running into is that whenever I flash a new rom, or do a factory reset with clockworkmod, I can never get my phone to send or recieve MMS. It always says, generic network failure. I have tried with the HTC messages app and handsent app, both failed. The data icon in the notification area usually does not even show activity. I tried wiping the cache several times, restarts, changing data and wifi settings but to no avail. Funny thing is, I can restore my phone to the first backup I made, Gingerbread 2.3.3, and then MMS works.
Any ideas as to what may be happening? I can give you any additional info you need or ask as well. I'm not a total noob, but I feel like one right now. I just can't figure this one out on my own. Thanks!
my3kgt said:
Let me start by saying, I have searched all of the treads for my phone, and the ones suggested before posting a new one, with no luck. I also searched all over other sites for an answer, about 3 hours now, and still nothing that quite fits my problem..
I have a Verizon HTC Inc2
-running 2.3.4
-Virtuous Unity v2.39.0
The problem I keep running into is that whenever I flash a new rom, or do a factory reset with clockworkmod, I can never get my phone to send or recieve MMS. It always says, generic network failure. I have tried with the HTC messages app and handsent app, both failed. The data icon in the notification area usually does not even show activity. I tried wiping the cache several times, restarts, changing data and wifi settings but to no avail. Funny thing is, I can restore my phone to the first backup I made, Gingerbread 2.3.3, and then MMS works.
Any ideas as to what may be happening? I can give you any additional info you need or ask as well. I'm not a total noob, but I feel like one right now. I just can't figure this one out on my own. Thanks!
Click to expand...
Click to collapse
General Network Error is when the system returns an error stating that you have no connectivity to send a message or an MMS (at least from my experience w/ it). I have this issue a lot with any messaging on my end because of shoddy reception. Which other ROMs besides Virtuous are you flashing that are giving this error? I know for a fact the CM7 has been having a LOT of issues with data connectivity. The last ones I remember hearing about with working data is #79 (or was it #80, I can't remember) and #85 and for a few people, #92.
I do have plenty of reception, always around 2 to 3 bars. Sorry I worded that wrong in my post, Virtuous is the only and first rom I flashed. I did it because Verizon OTA updates kept freezing my phone and I would get the blue android with the !. What I meant was, even when I did a factory reset, my MMS wouldnt work. First time I got that error, I was able to use bootloader and make a backup of eberything, then did a factory reset/wipe data and thats when I first noticed MMS was not working. So I copied the backup to my laptop, did another factory reset and format SD card, then I copied the backup to my card again, and did a restore with that backup. I restored data, cache, system, and boot I believe, and everything was back to normal and MMS was working. Unfortunetly I kept getting the OTA updates and each time, same problem, so this morning I read on a forum that a custom rom would prevent OTA updates, so I flashed Virtuous. I just found it odd that a normal factory reset, with no custom rom, would prevent MMS.
One more thing, not sure if its related, but I keep recieving messages from #6250 that say "VZWNMN: 1." Google searched that, most responses in forums are people saying they get the same thing and that Verizon told them they know nothing about it..
Have you tried a different radio?
Sent from my Incredible 2 using xda premium
my3kgt said:
I do have plenty of reception, always around 2 to 3 bars. Sorry I worded that wrong in my post, Virtuous is the only and first rom I flashed. I did it because Verizon OTA updates kept freezing my phone and I would get the blue android with the !. What I meant was, even when I did a factory reset, my MMS wouldnt work. First time I got that error, I was able to use bootloader and make a backup of eberything, then did a factory reset/wipe data and thats when I first noticed MMS was not working. So I copied the backup to my laptop, did another factory reset and format SD card, then I copied the backup to my card again, and did a restore with that backup. I restored data, cache, system, and boot I believe, and everything was back to normal and MMS was working. Unfortunetly I kept getting the OTA updates and each time, same problem, so this morning I read on a forum that a custom rom would prevent OTA updates, so I flashed Virtuous. I just found it odd that a normal factory reset, with no custom rom, would prevent MMS.
One more thing, not sure if its related, but I keep recieving messages from #6250 that say "VZWNMN: 1." Google searched that, most responses in forums are people saying they get the same thing and that Verizon told them they know nothing about it..
Click to expand...
Click to collapse
People on CM were complaining of the same exact issue. They'd get bars of reception but MMS was just broken. I was just stating that when I try to send a message thru verizon and not google voice, I often get the same error message you're getting, which means that the data is being prevented from going out. I probably should've clarified that a little better lol. When you installed Virtuous, did you do a wipe data/cache and a wipe dalvik cache?
Also, if you restore back to your Gingerbread 2.3.3 that's rooted and your MMS is working fine there, then I don't believe it could be your radio. A possibility would be the kernel, but I doubt that Virtuous would package a kernel that would crash the MMS function. And since it's any SMS/MMS app, that knocks out the possibility of it being application based. The only thing I can suggest, would be to test out another ROM. If you're looking for sense based roms, go for BAMF's (http://www.teambamf.net) or Newt's Incredible 2 HD (http://www.themikmik.com). If you're looking for an AOSP based rom, go for CM7 (found on ROM Manager or at http://www.cyanogenmod.com) or MIUI (ROM Manager again, or http://www.miuiandroid.com). If you want a hybrid, I would suggest Skyraider Zeus (http://www.teambamf.net) or Gingersense (it can be found in the development portion of XDA). Remember when you flash a rom for the very first time, I'm sure you know this already, but you need to backup your rom first and then wipe data/cache and wipe your dalvik cache. Not doing either wipe before installing a brand new rom for the first time can cause unforseen errors.
Ok I found the answer while actually looking for new radios, so thanks for the post! haha
For all you out there who might run into the same problem, this is the solution I found..
Instructions to fix MMS (by xelsewherex)
1.Go to the market and download apn backup and restore (Market Link APN B&R).
2.Create a folder on your sdcard named APNBackupRestore if it doesn't exist already.
3.Copy this file, ht tp://db.tt/9Ao5ErR, to APNBackupRestore folder (If you aren't doing this on desktop, hit menu now in xda and choose browser. File is an xml and your phone will not know what to do with it. Long press the link and use 'save link'). This is an XML doc, sorry but since I'm new I can't just post a link, just remove the spaces between ht and tp.
4.Run APN Backup Restore and press Delete Apns and then Restore from the downloaded file.
5.You should be good to go from there. MMS should now work and the softkey lights do as well.
For some reason, my phone randomly has lost the ability to make or receive phone calls. Any time i try to place a call, it simply says "call ended" before even attempting to dial. I have not made any major changes to the phone recently. This seems to have happened out of nowhere. Data and text messaging work just fine, but phone calls won't.
My phone is rooted and I have the leaked Touch Wiz Jelly Bean rom installed. Also using CWM recovery.
I have tried pulling the battery for 10 minutes, and I also wiped cache/dalvik then did a system reboot through recovery, to no avail. Is there anything else I can try? Would prefer not to have to do a full data wipe if possible. Unfortunately I can't even call Telus (my carrier) to ask them for advice, due to this problem.
Is your IMEI# intact? Maybe try a new SIM card? Go back to stock to see if that fixes it. (I know you said you'd prefer not to wipe.)
Just to rule out any ROM related issues you could always make a full backup from recovery, then full wipe and flash back to stock and see if the problem persists. This way although you did wipe you can revert back to you current setup in a matter of minutes like nothing ever happened, if the problem is not fixed by going back to stock.
saj222 said:
Is your IMEI# intact? Maybe try a new IMEI card? Go back to stock to see if that fixes it. (I know you said you'd prefer not to wipe.)
Click to expand...
Click to collapse
Yep IMEI is still there. Anyone have any other suggestions before I wipe and flash back to stock? I'll try a new SIM card if wiping and re-flashing doesn't work.
dntesinfrno said:
Just to rule out any ROM related issues you could always make a full backup from recovery, then full wipe and flash back to stock and see if the problem persists. This way although you did wipe you can revert back to you current setup in a matter of minutes like nothing ever happened, if the problem is not fixed by going back to stock.
Click to expand...
Click to collapse
This seems like a good idea, I think I'll have to go this route... thanks.
Okay so I did a full backup using CWM, then wiped everything. Attempted to re flash the stock rom but ran into an issue and decided to try a different rom instead just to try it out.
Dialler worked fine on the new rom, so that was great news. Then I attempted to sync my contacts and everything with my Gmail.... But nothing was there. Apparently I somehow lost all my contacts!
So, freaked out, I immediately reverted to my Cwm backup, which thankfully restored everything. Just for the hell of it I tried the dialler... And it worked! So.... Yeah I have no idea what exactly fixed my problem in the end, but I'm just happy its working.
Thanks for the suggestions everyone!
Sent from my SGH-I747M using xda app-developers app
Sounds like the dialer app was borked somehow, might want to look into those sync settings though. I had an issue one time where the contacts i added to my phone were saving to the phone and not as gmail contacts. To check you can just log into gmail in a broswer and look at your contacts, make sure they are all there. If not you can go to your contacts on your phone, press menu and export to a .csv file. This will move all contact info into this file and you contacts will be blank, at this point simply find where you saved the .csv and import the contacts which will give you the option to make them gmail contacts. Then all you need to do is go into gmail on the browser again and delete and/or merge the duplicates.
Okay so I left my phone as-is for the past couple weeks until earlier tonight. I made a backup with CWM, then I attempted to flash a couple new roms. Did a cache/dalvik/system format/factory reset before each rom installation, then made sure to format cache/dalvik and fix permissions after each installation attempt. The roms installed fine and everything was working, except I lost use of my dialler again! So I reverted to my backup, but the dialler problem has persisted, just like I described in the OP. The way I "fixed" it last time, was to restore my backup....but that isn't helping this time...
Anyone know what else I can try? IMEI still intact, getting mobile data, wifi, MMS, etc... just can't make or receive calls again.
I should also mention that I a while back, before I tried rooting/installing any custom ROMs, I made a backup of my EFS folder on my phone... should I attempt to restore this?
Dial
*#2263#
Check to make sure automatic it's selected.
I had a similar problem messing around with lte, and found the above fixed the issue.
Also on Telus.
Sent from my SGH-I747M using Tapatalk 2
Wow thanks so much! That totally fixed the problem. I seem to pick up lte signals less often now but at least I can use my phone!
Sent from my SGH-I747M using xda app-developers app
Yeah, the lye on my phone only picks up when I'm out of my house. Has to do with the signal from telus I believe
Sent from my SGH-I747M using Tapatalk 2
Going to install custom Rom on at&t s3 had phone towelrooted and saved stock Rom with Rom manager. Decided maybe I should not do it than tried to restore from backup.After backup ran started getting pop ups saying Google app not responding keep hitting ok and goes right back to same message.Did a soft reset after that I lost calling and text ability. Phone is not showing baseband info
Before flashing anything, determine what bootloader is on your phone.