Hi, so I have Moto G 2014 XT1068. It's rooted, and TWRP is installed. I flashed the Nexus dialer (the one with Nearby Places, and Caller ID by Google) from recovery using a zip file, and uninstalled the original one (Big mistake, I know.)
Then I couldn't get calls UI to work, so I reinstalled the original stock dialer using a backup. Now calls work, but everytime I try to open the stock dialer, it shows up as "Dialler has stopped working."
The Nexus UI, however, still works.
I could live with this current scenario, as I can make, pick up, and break calls without problems, but I might need to access the call settings from the stock dialer's menu, which I can't.
All help appreciated - I'm not open to reflashing the firmware / resetting it. I have a backup of the stock dialer made using Titanium, but restoring it does not fix the issue.
Cheers!
Uninstall the Nexus dialer app and then wipe cache and dalvik-cache from TWRP.
sharkymyn said:
Uninstall the Nexus dialer app and then wipe cache and dalvik-cache from TWRP.
Click to expand...
Click to collapse
EDIT : Thank you for your reply. Sadly, this did not work.
I have also tried booting in Safe Mode, but the app did not work there either.
Cheers!
Did you take a full system backup via TWRP?. Try restoring it else flashing factory firmware is the only option left.
Follow this thread : http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
sharkymyn said:
Did you take a full system backup via TWRP?. Try restoring it else flashing factory firmware is the only option left.
Follow this thread : http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
Click to expand...
Click to collapse
I think I'll wait it out, see if somebody else has another solution, or until I really need to open the settings
Thanks again.
Go to setting>app>stock dialer>clear data n cache> reboot. Njoy
gauravrai said:
Go to setting>app>stock dialer>clear data n cache> reboot. Njoy
Click to expand...
Click to collapse
Thanks, but that didn't work. I fixed it, but it was quite long, though not complicated.
Remove Nexus dialer using Titanium.
Take Nandroid / Titanium backup of all apps and data.
Flash stock - without clearing user data. This will remove recovery as well. Boot and install any OTA updates available.
Reinstall recovery and reroot. Restore stuff using Titanium.
Moral of the story : Have a nandroid backup before messing around.
Cheers!
Related
My N7000 stays stuck at the "Samsung Galaxy Note" screen when I try restarting after a restore using TiBu. This is the case with both CM 10.2 as well as Stock ROM. However, If I get into the recovery and wipe data and cache (Factory Reset) it boots back normally.
I am on the latest DBT German ROM with latest Philz Kernel in case of Stock.
In case of CM 10.2 there is no kernel or recovery change.
Any suggestions to fix this?
Maybe you'll tell us what you restored with TB first?
TB Back up order
ThaiDai said:
Maybe you'll tell us what you restore with TB first?
Click to expand...
Click to collapse
Step 1: Restoring the messages and call logs (XML Format)
Step 2: Followed by restore of User Apps and Data.
Step 3: Finally System Apps Data.
I have shuffled between CM and Stock several times in the past and have followed this order without issues.
Now, as soon as I restore User Apps and do a reboot, it gets stuck.
Step 3: not difficult to guess why this is your problem. Try without.
ThaiDai said:
Step 3: not difficult to guess why this is your problem. Try without.
Click to expand...
Click to collapse
Right now it is getting stuck after step 2 but before executing step 3. I was also aware that step 3 could be an issue so i let it stay minimal or rare.
Fixed
Can the Admins close the thread please? This has been fixed now.
Solution the way i closed the issue:
I did not perform the App restore. I downloaded the apps afresh and then did the data restore alone for the really necessary apps.
Never restore system apps. Don't even use TiBU to back up system apps. This causes conflicts within the OS and will cause a boot loop.
normaltusker said:
Step 1: Restoring the messages and call logs (XML Format)
Step 2: Followed by restore of User Apps and Data.
Step 3: Finally System Apps Data.
I have shuffled between CM and Stock several times in the past and have followed this order without issues.
Now, as soon as I restore User Apps and do a reboot, it gets stuck.
Click to expand...
Click to collapse
Never restore system data. If the rom has other structure there's no way it can boot. You have to set up whole settings by yourself. And for the messages use program from Google store to backup and restore them. This won't brick Your phone
Sent from my GT-N7000 using xda app-developers app
I have a rooted HTC one with viper rom, my coworker has the same phone but with Android Revolution.
If I was to restore my recovery image.zip onto his phone, would this work? Or do I have to customise it alittle. If so, how would I do this?
I want him to keep all the same settings I have, but with different phone information. If that makes any sense? (sorry)
Any help would be greatly appreciated. Don't want the trouble of installing the rom and setting up the same settings and tweaks.
Thanks,
Andy
killerb4dger said:
I have a rooted HTC one with viper rom, my coworker has the same phone but with Android Revolution.
If I was to restore my recovery image.zip onto his phone, would this work? Or do I have to customise it alittle. If so, how would I do this?
I want him to keep all the same settings I have, but with different phone information. If that makes any sense? (sorry)
Any help would be greatly appreciated. Don't want the trouble of installing the rom and setting up the same settings and tweaks.
Thanks,
Andy
Click to expand...
Click to collapse
the image.zip that recovery creates only contains /system not everything (at least for me CWM 6.0.3.2), but you could do a full backup and transfer the entire folder to the other phone, and then do a RESTORE (not flash).
That will duplicate everything including apps and data, as well as all your accounts etc. which I guess you would have to delete and setup again.
nkk71 said:
the image.zip that recovery creates only contains /system not everything (at least for me CWM 6.0.3.2), but you could do a full backup and transfer the entire folder to the other phone, and then do a RESTORE (not flash).
That will duplicate everything including apps and data, as well as all your accounts etc. which I guess you would have to delete and setup again.
Click to expand...
Click to collapse
So I would need wipe and install the viper rom onto his device and restore my (custom) backup to it also. Sounds easy enough, I'll give that a try.
Thanks for the help.
killerb4dger said:
So I would need wipe and install the viper rom onto his device and restore my (custom) backup to it also. Sounds easy enough, I'll give that a try.
Thanks for the help.
Click to expand...
Click to collapse
No need to wipe, the restore will automatically wipe everything on the phone. Except sdcard of course.
But in recovery do a wipe of cache and dalvik after restore and before boot, just to be safe.
Sent from my HTC One using Tapatalk
Ah, I understand.
Thanks again!
I have tried this numerous times still no result.
Cm 10.1.3 works perfectly fine. But once i flash it with my Titanium backup update.zip file. There will be errors, and after i reboot it, it iwll just get stuck at the spinning blue circle. I have tried everything, from apps+data to only app data. Nothing works.
I would have to factory reset and reflash it again.
I use clockworks mod recovery.
My phone is a odin rooted Galaxy S3 Lte (i9305)
Shinny123 said:
I have tried this numerous times still no result.
Cm 10.1.3 works perfectly fine. But once i flash it with my Titanium backup update.zip file. There will be errors, and after i reboot it, it iwll just get stuck at the spinning blue circle. I have tried everything, from apps+data to only app data. Nothing works.
I would have to factory reset and reflash it again.
I use clockworks mod recovery.
My phone is a odin rooted Galaxy S3 Lte (i9305)
Click to expand...
Click to collapse
use recovery to flash roms not TB, its much more reliable.. i think the problem is because of apps and data you trying to restore with the update.zip. i know you use tb because you want to restore your apps+data easily while flashing new rom, but tb seems to give problems with this method
MaHo_66 said:
use recovery to flash roms not TB, its much more reliable.. i think the problem is because of apps and data you trying to restore with the update.zip. i know you use tb because you want to restore your apps+data easily while flashing new rom, but tb seems to give problems with this method
Click to expand...
Click to collapse
Nah, i didnt flash my rom with tb, i flashed it with recovery. Then once everything was done, i would go back into recovery and flash the update.zip file
Shinny123 said:
Nah, i didnt flash my rom with tb, i flashed it with recovery. Then once everything was done, i would go back into recovery and flash the update.zip file
Click to expand...
Click to collapse
yes i see, but that seems to be the problem ''restoring apps, data with tb'' and from what i know it occurs that this sometimes gives errors, fc's and bootloops like in your case
MaHo_66 said:
yes i see, but that seems to be the problem ''restoring apps, data with tb'' and from what i know it occurs that this sometimes gives errors, fc's and bootloops like in your case
Click to expand...
Click to collapse
So is there no way to go through with this? Maybe export my backups to another software or something? or am i supposed to start fresh?
Shinny123 said:
So is there no way to go through with this? Maybe export my backups to another software or something? or am i supposed to start fresh?
Click to expand...
Click to collapse
you could try to export your backups (only data) to pc temporary and after having flashed the rom with full wipe, install the apps again and put the backups manually in corresponding directories and see how that is gonna work out. I gave up on TB because of this problem and usually i always start fresh with new flashed roms. I only put my personal files on pc and put it back manually after rom install.
MaHo_66 said:
you could try to export your backups (only data) to pc temporary and after having flashed the rom with full wipe, install the apps again and put the backups manually in corresponding directories and see how that is gonna work out. I gave up on TB because of this problem and usually i always start fresh with new flashed roms. I only put my personal files on pc and put it back manually after rom install.
Click to expand...
Click to collapse
Thanks so much, I dont really need all my apps to be backed up, just important ones, has the manual method worked out for you?
Shinny123 said:
Thanks so much, I dont really need all my apps to be backed up, just important ones, has the manual method worked out for you?
Click to expand...
Click to collapse
yes, most of the times works fine but cant guarantee it will work with every app, i guess has something to do with permissions i.m.h.o
I've tried flashing slim rom and paranoid Android and all do the same thing. As soon as Google apps are installed the Google voice search prompt pops up repeatedly. It disables calling and also all sounds. I have turned it off in Google settings best I could and it still keeps happening. It has essentially made my nexus 6 unusable. And since I need the Google app I don't know what to do. Anyone seen this problem before? I am guessing it is not rom specific as it happens on all I have tried. Help severely needed
Sent from my Nexus 6 using Tapatalk
wessiide said:
I've tried flashing slim rom and paranoid Android and all do the same thing. As soon as Google apps are installed the Google voice search prompt pops up repeatedly. . .
Click to expand...
Click to collapse
When I flashed a different ROM there were always issues when I did not a wipe in TWRP recovery (factory reset).
I have cleared data and cache along with a system wipe. Any thing else I can try to wipe?
NLBeev said:
When I flashed a different ROM there were always issues when I did not a wipe in TWRP recovery (factory reset).
Click to expand...
Click to collapse
Sent from my Nexus 6 using Tapatalk
wessiide said:
I have cleared data and cache along with a system wipe. . .
Click to expand...
Click to collapse
In TWRP there is a message about wiping.
When you did that it is OK.
Effect should be that after booting the new rom, you need to completely setup the device again (setup wizard).
When there are still issues it could be a corrupt download.
I'll try to be more clear here.
I have done a factory reset (system, data, cache, dalvik) from TWRP.
I install new rom (chroma, paranoid, slim, and a stock build)
Boot up phone, complete setup wizard.
"Listening" prompt from google voice search starts popping up repeatedly, over and over no matter what I am doing on the phone.
I disable google voice search, doesn't matter, continues to pop up.
In the meantime it disables all sounds on the phone and I cannot place a call/take a call.
Again, this is the same actions that happen regardless of what rom I have installed, even after doing the reset.
Try changing the GApps package you flash after your ROMs.
I'm guessing you've been using the same GApps with each ROM you listed. Download another GApps and use that instead in a clean flash of a given ROM.
Good luck!
(One more thought: You could try clean flashing a ROM with a built-in GApps and see if that works...)
Sent from my A0001 using Tapatalk
wessiide said:
I have done a factory reset (system, data, cache, dalvik) from TWRP.
I install new rom (chroma, paranoid, slim, and a stock build)
Boot up phone, complete setup wizard.
Click to expand...
Click to collapse
There are two important options in TWRP.
WIPE and FORMAT.
You have installed several different roms. The memory could be messed up.
A format could help.
The last suggestion I can do is: back to stock.
Flash a factory image.
Leave bootloader unlocked.
Check if the issue is gone when the stock rom is set up.
Than choose a custom rom, start with Chroma.
NLBeev said:
There are two important options in TWRP.
WIPE and FORMAT.
You have installed several different roms. The memory could be messed up.
A format could help.
The last suggestion I can do is: back to stock.
Flash a factory image.
Leave bootloader unlocked.
Check if the issue is gone when the stock rom is set up.
Than choose a custom rom, start with Chroma.
Click to expand...
Click to collapse
What do I format? System? It doesn't seem to be a Google specific problem as even with Google not installed the phone just hangs up when I dial a number and sound doesn't work. It went away on its own about an hour after start up and I've been good for a week. Now just this morning it started doing it again. The volume turned itself up a notch and boom no sound on video can't call anyone. It's very strange, and must be a deep rooted issue as it is across all roms. The only difference with Google now installed is the listening prompt popping up constantly. Without its just what I listed above.
Sent from my Nexus 6 using Tapatalk
Revert back to stock (e.g. with Wug's nexus root Toolkit), leave bootloader unlocked. Then reflash your things and see if problem persists. If it does, try TK GApps and don't install Google App (per gapps-config.txt).
Hey, so i opened my Bootloader and now I cant find how the hell to flash the latest Weekly version of Xiaomi EU, can someone help me? I searched on youtube but they flash via Fastboot and I don't see a weekly version with Fastboot
Follow the instructions found on the first post here https://forum.xda-developers.com/t/...mi-eu-rom-for-xiaomi-mi-11-pro-ultra.4260617/
Look at the bottom, there's an edit that tells you how to install TWRP, that's the primary way to install the new versions of that rom
Bananablob said:
Follow the instructions found on the first post here https://forum.xda-developers.com/t/...mi-eu-rom-for-xiaomi-mi-11-pro-ultra.4260617/
Look at the bottom, there's an edit that tells you how to install TWRP, that's the primary way to install the new versions of that rom
Click to expand...
Click to collapse
HELP - i flashed the EU rom and wiped Dalvik cache, and reeboted, now It reboots to the TWRP over and over again, what do I need to do?
You also need to wipe data and such before flashing, so maybe you didn't notice or forgot, but as long as you have TWRP, you can recover.
Maybe your ROM download got corrupted. If possible, check the checksum, they should provide it.
It's also possible your USB port + cable combo doesn't work properly, it's happened to many people, so if you are sure it's not the rest, it might be just that
Bananablob said:
You also need to wipe data and such before flashing, so maybe you didn't notice or forgot, but as long as you have TWRP, you can recover.
Maybe your ROM download got corrupted. If possible, check the checksum, they should provide it.
It's also possible your USB port + cable combo doesn't work properly, it's happened to many people, so if you are sure it's not the rest, it might be just that
Click to expand...
Click to collapse
I flashed it but now every app I open crushes, Im on weekly version and I restored apps from the Xaiomi backup, do you know why?
I can't say I do, but I'd assume it's because Xiaomi backup is configured to work only on stock roms.
It's possible that uninstalling and reinstalling each app using whatever the proper app shop is for the given app will fix it without losing the restored data and cache for it.
Bananablob said:
I can't say I do, but I'd assume it's because Xiaomi backup is configured to work only on stock roms.
It's possible that uninstalling and reinstalling each app using whatever the proper app shop is for the given app will fix it without losing the restored data and cache for it.
Click to expand...
Click to collapse
omg I only did it because i thought I would be able to restore everything within 1 click and now everything crushes. I have like 100 apps + tons of accounts to login
I would always assume auto backup things to fail when you need them.
Try to reflash your original rom from here and restore using the same backup tool: https://forum.xda-developers.com/t/miui-updates-tracker-mi-11-pro-ultra-star-mars.4263135/
Then you can reevaluate how you wanna backup and restore to transition.
It's possible it failed because you have an official rom backup, but it would work if the tool had backed up from Eu to Eu
Bananablob said:
I would always assume auto backup things to fail when you need them.
Try to reflash your original rom from here and restore using the same backup tool: https://forum.xda-developers.com/t/miui-updates-tracker-mi-11-pro-ultra-star-mars.4263135/
Then you can reevaluate how you wanna backup and restore to transition.
It's possible it failed because you have an official rom backup, but it would work if the tool had backed up from Eu to Eu
Click to expand...
Click to collapse
I dont wanna mess with reinstalling CN version, etc
I will just Factory reset and reinstall manually..
To factory reset in brings me to TWRP, why is it?
Because you installed TWRP instead of the normal recovery utility, you now have TRWP in that partition on your phone. If you use TWRP to flash the proper stock ROM, it will have the same effect as using factory reset using the stock recovery utility. BTW, the stock recovery utility is not built to support having flashed another rom, so you're in good hands having TWRP instead.
You probably had issues because you only wiped dalvik rather than format data after installing the EU ROM. You must format data after flash because the different branches have different partition layouts, hence your problems.
As you must format, you might as well start from scratch again or go in to twrp wipe menu and select format, type yes to confirm and then reboot system. If you want to go down the full install, then flash the ROM again, format data, with the yes confirmation, then reboot system. After each update, just a dalvik wipe is