Related
Sorry guys may I ask a question relative to restoring apps via TiBU?
Before flashing stock 4.3 I had updated TiBU and backed up my apk's+data
Wiped everything to have a clean slate for TRIM to work perfectly and I've started to restore my apps.
TIBU takes forever to install a single apk, actually never ends.
Reboot.....
If I try to install apk from the market and then restore only the data from TiBU the app crashes.
After that I cannot reinstall the app anymore even from the play store.
Is there a way to overcome this?
Thanks
PS: I have already tried the solution Menu/Preferences/backup folder location
PS2: Nexus 4 - built JWR66Y - FRANCO r178
vagos696 said:
Sorry guys may I ask a question relative to restoring apps via TiBU?
Before flashing stock 4.3 I had updated TiBU and backed up my apk's+data
Wiped everything to have a clean slate for TRIM to work perfectly and I've started to restore my apps.
TIBU takes forever to install a single apk, actually never ends.
Reboot.....
If I try to install apk from the market and then restore only the data from TiBU the app crashes.
After that I cannot reinstall the app anymore even from the play store.
Is there a way to overcome this?
Thanks
PS: I have already tried the solution Menu/Preferences/backup folder location
PS2: Nexus 4 - built JWR66Y - FRANCO r178
Click to expand...
Click to collapse
I don't trust TiBU. its a real mess for me. I for one backup my ANDROID folder, and flash all apps through recovery. and then copy back the Android folder on SDCARD.
How did you root your 4.3 image? Many custom kernels break root on 4.3. Try re-flashing SuperSU or re-flash ROM and stick to the stock kernel.
via Nexus Toolkit. I'm still rooted even after applied Franco, but I'll revert back to stock kernel just to check your possibility.
Even the saved TiBU apk's are not getting installed.
How can I re-install the broken apps which were affected from TiBU? As I mentioned even fresh installation from the play store is not processed.
I was hoping to avoid re-flashing and re-rooting from scratch.
Nope even with stock kernel I face the same problems. Any suggestions?
I guess there's something wrong with your /data partition. I'd either start over with flashing the factory image or at least format /data (not wipe, really format). Don't forget to backup your internal sdcard content first, it will be deleted with both methods.
Also I'd recommend not using a toolkit for flashing the factory image and rooting. It's easy enough using fastboot and a custom recovery. This way you'll be on the safe side, not missing any errors etc.
Make sure your TiBU directory is set to storage/emulated/legacy/TitaniumBackup, not storage/emulated/0/TitaniumBackup.
It worked for me, anyway. Well, after having to perform a factory reset, as it screwed up the UUIDs, that is
Thanks for the suggestion. You were right my path was storage/emulated/0/TitaniumBackup.
I revert it to the suggested one but I have the same issue.
Factory reset, start from scratch, initial path storage/emulated/legacy/TitaniumBackup
The same problem which also end up destroying the fresh apk as well.
Hopeless
Tell us exactly what you're doing. Which ROM / image, software, versions, procedure, all the details. Maybe something other well ring a bell.
As already quoted
1. Before updating to 4.3, I updated TiBU to the latest version and kept backup of the apps+data
2. Clean flash of stock 4.3 ROM (JWR66Y) via Nexus Toolkit
3. Root (Busybox, SU etc)
4. Flashing Franco Kernel r178
5. Installation of TiBU
6. Try to restore - PROBLEM
Plan B:
1. Factory Data Reset
2. BusyBox gone but still have root access
3. Stock ROM - Stock Kernel - Rooted
4. Install TiBU
5. Restoring - PROBLEM
Description of the PROBLEM:
I cannot restore apk's is getting into a loop and never ends.
I can restore data to an installed apk, but then the app crashes
I cannot re-install the (restored) app via playstore, I get "unknown error code during installation -24-"
Current situation
1. Factory Data Reset again
2. Franco r178
3. No restores via TiBU
Don't shoot me, but it still sounds like the TiBu 4.3 ROM backup folder path problem. Here's what I do and what works for me:
1. Open TiBu
2. Click on "Menu"
3. Click on "Preferences"
4. Click on "Backup folder location"
5. Click on "DETECT!"
6. Click on "Whole device"
7. Choose "/storage/emulated/legacy/TitaniumBackup"
8. Click on "Use the current folder"
9. TiBu will now ask if it should move the other backups to the new folder, say no.
10. Exit the preferences with the back key
11. TiBu will now reload with the new preferences
Now restoring should work if the path is the problem.
About loosing root with a custom kernel on 4.3 ROMs:
If you lose root by flashing a custom kernel it may still seem like root is active, i.e. the root frontend app will still be there and ask for root permissions etc. Try the following to ensure that TiBu is running with full root privileges: Uninstall some unimportant system application (some Gapp for example, like Google Currents - backup first if you need it). If uninstalling gets cancelled with a message like "Can't find the apk file", it's likely that root doesn't work properly.
Come on man, I hate to give up
Thanks for the inspiration but unfortunately:
1. I can unistall, backup and restore properly Google Currents (hence proper root)
2. Back up folder was set properly also by verifying your steps (2-10)
And again if I try to restore an old app (not the data) it gets to the familiar loop.
Ok. I'd now flash the full factory image, thus resetting every partition (backup internal sdcard first). Please try without a toolkit to be safe. You need the drivers installed (your toolkit should already have taken care of that) and have adb and fastboot ready. There are batch/shell scripts included in the factory image which invoke the fastboot commands in one step.
Next flash a custom recovery with fastboot and use it to flash SuperSU for root access.
Refrain from flashing a custom kernel now and try if you can successfully restore with TiBu at this point.
If you can, the problem was either one of your partitions/filesystems f_cked up or the toolkit doing something wrong.
My phone is rooted, unlocked
Today Moto has an new update showing up
I accidentally hit "Yes, I am in" to start the update
Now my phone becomes:
-- Booting into TWRP
-- I reboot it to normal, but it starts updating automatically again, then booting into TWRP
-- Repeat above forever....
Before anyone releases the update image so I can update it through TWRP, what else can I do to stop it loop like this so I can use my phone???
Thanks in advance!
You could try force closing Motorola Update Services when you start the device. I'm not sure this will work once you get into the bootloop cycle. If that doesn't work, the only thing you can do is restore from a backup or perform a wipe.
mrl515 said:
You could try force closing Motorola Update Services when you start the device. I'm not sure this will work once you get into the bootloop cycle. If that doesn't work, the only thing you can do is restore from a backup or perform a wipe.
Click to expand...
Click to collapse
Thanks, I found a previous twrp backup and restored it. Lost some data though but works.
If it happens again try just wiping cache. That should nuke the OTA zip and stop the bootloop.
i can flash moto_orig._recovery.img from stock rom for getting this update? and than flash TWRP recovery again? thx
This happened to me too.
Download SD maid, then go to motorola update services. Then go to AppControl > Motorola Update Services > Freeze app. Notifications stopped appearing for me after I did that.
Best way to do it through TWRP
View the log, see which update file is failing. It gives you exact location of the file. Use twrp file manager and delete the update from that location.. Reboot normally.
I think it downloads to /cache, log will verify.
This process worked for me with zero issues or data loss.
89ls1 said:
Best way to do it through TWRP
View the log, see which update file is failing. It gives you exact location of the file. Use twrp file manager and delete the update from that location.. Reboot normally.
I think it downloads to /cache, log will verify.
This process worked for me with zero issues or data loss.
Click to expand...
Click to collapse
I ended up wiping the Cache in TWRP, and upon restarting got the error message that said the update had failed, and if I wanted to do the update, I'd have to redownload it in the system settings. I didn't check the log to see where it downloads to, but I'm assuming you were right and that it does download to /cache.
Either way, you guys are life savers. Thanks!
hello, I would like to unistall Spotify and other apps included on my X compact Nougat firmware. (have root device)
I tried with Titanium Backup, but after some second the app reappears.
There is an option with TB that force the unistall by recovery, but if I do that recovery does not boot.
(I can boot in recovery manually only)...
Any Help?
THX
I am using Moto G5 plus, My camera is not working. I have downloaded latest update on my phone. Error,"camera has stopped" "camera keeps stopping" "camera busy" Restart Phone"
current error is "camera keeps stopping"
Before week, To enable screencast function i have rooted my phone. But my phone and camera was working perfectly fine, after week my fornt camera stopped working, and now rear camera is also not working
Below method i have tried but camera is still not working.
-checked in safe mode
-uninstalled all the application from mobile
-cleared date, cleared cache, disablled and enabled, download latest camera update.
-i have also removed sd card and tried in normal and safe mode.
Please guide what should i do next?
The update let you pass the root
vipul.vip009 said:
I am using Moto G5 plus, My camera is not working. I have downloaded latest update on my phone. Error,"camera has stopped" "camera keeps stopping" "camera busy" Restart Phone"
current error is "camera keeps stopping"
Before week, To enable screencast function i have rooted my phone. But my phone and camera was working perfectly fine, after week my fornt camera stopped working, and now rear camera is also not working
Below method i have tried but camera is still not working.
-checked in safe mode
-uninstalled all the application from mobile
-cleared date, cleared cache, disablled and enabled, download latest camera update.
-i have also removed sd card and tried in normal and safe mode.
Please guide what should i do next?
Click to expand...
Click to collapse
With my old motorolas if I made a root and try to make an update, the updater failed with a mistake, I supposed that you used magisk, and the root was hide for the system and if you only modify the build.prop to enable screen cast, my only advice to you is to restore a stock firmware that will help you really well with your problem, the easiest option for me is to install a zip based stock firmware to not to have to install RSD flasher and those stuff I will let you the link I hope this will help you.
https://franco28.github.io/stockrom/index.html
1. Wipe system, cache, dalvik-art
2. Erase manually in the TWRP the internal (Sdcard/Android) folder, and do the same in your (external_sd) folders.
Just in case make a copy of all your internal data, in drive and google fotos.
Thank you so much for the guidance
i do really appreciate your advice. yes you got it right, i have used magisk and build.prop to enable screen cast, but i novice to all this, i did not understand below options. hot do it, you mean, i have to reboot device and wipe system, cache, dalvik-art
1. Wipe system, cache, dalvik-art
2. Erase manually in the TWRP the internal (Sdcard/Android) folder, and do the same in your (external_sd) folders.
Please guide
tekkaman7 said:
With my old motorolas if I made a root and try to make an update, the updater failed with a mistake, I supposed that you used magisk, and the root was hide for the system and if you only modify the build.prop to enable screen cast, my only advice to you is to restore a stock firmware that will help you really well with your problem, the easiest option for me is to install a zip based stock firmware to not to have to install RSD flasher and those stuff I will let you the link I hope this will help you.
1. Wipe system, cache, dalvik-art
2. Erase manually in the TWRP the internal (Sdcard/Android) folder, and do the same in your (external_sd) folders.
Just in case make a copy of all your internal data, in drive and google fotos.
Click to expand...
Click to collapse
vipul.vip009 said:
i do really appreciate your advice. yes you got it right, i have used magisk and build.prop to enable screen cast, but i novice to all this, i did not understand below options. hot do it, you mean, i have to reboot device and wipe system, cache, dalvik-art
1. Wipe system, cache, dalvik-art
2. Erase manually in the TWRP the internal (Sdcard/Android) folder, and do the same in your (external_sd) folders.
Please guide
Click to expand...
Click to collapse
Hi? if I understood your reply is about if you have to make the steps I post on that time, the answer is no, I'm not sure but I was talking about someone returning to stock or something, if you enable the screen cast you'll be able to see the "hamburger menu" in the android screen settings, that let you to make the screen cast, what's your exact problem?
Today Iran across a post to turn on VoLTE and it requires onepluslogkit and engineering mode, both of which I have deleted. I found an apk for the log kit, installed it, still no engineering mode.
Not even sure I will be able to turn on VoLTE here in Thailand, but when I am stateside for the 1stQ it would be handy as service SUCKS in Las Vegas.
I deleted the logkit because it's a back door and talks to China way too much. My plan was reinstall, set up VoLTE, delete the app again.
Not a big enough issue to reflash a clean oos and start over.
Any thoughts and suggestions....contructive ones.....are appreciated.
Thanks in advance!
Just dirty flash OOS, it will re-install the system apps you have deleted without removing user data.
Thanks Jager!
Never done that before. Is this what I need to do?
Reboot into TWRP
Click Install and choose my last OOS zip file
Wipe dalvik and cache
Reboot to recovery
Install TWRP
Install Magisk
Reboot system
Thanks in advance, JC
No need to wipe the caches, it just leads to increased battery drain with current versions of Android.
It looks like you have two of those steps in the wrong order. I have underlined the steps that need to be switched switched:
Reboot into TWRP
Click Install and choose my last OOS zip file
Install TWRP
Reboot to recovery
Install Magisk
Reboot system