Alright, so I was trying to make Nova Launcher my one and default launcher by moving it to /system. I had previously backed up and uninstalled Huawei's launcher with Titanium. But in the middle of things - had already uninstalled HW launcher and was trying to move Nova to /system - I made the mistake to think there would be a newer version available (which there was, but I couldn't update it on top of my current Nova version, dunno why). Karma strikes, I forget about not having a launcher and decide to reboot the phone to see if it was just Nova misbehaving or something (lol).
Now the phone shows bootanim alright, but goes to a "updating" EMUI screen which halts at 100% (I'm assuming the phone can't start without a proper launcher in /system). I said alright, let's push a Nova.apk to /system via TWRP (which works fine at least, so I know the phone isn't bricked), but upon trying to copy the app I get:
failed to copy 'NovaLauncher.apk' to '/system/app/': Is a directory
I don't know what to do; I have two NANDroid backups (one pre-root and another one after I made lots of modifications but phone still worked fine) but would preferrably install Nova rather than restoring the whole backup (if it's at all possible, of course).
Using instructions to install apps at /system/app through ADB gets me the message "remount of system failed: Success remount failed" upon trying /adb remount , and I don't know how to procede. Any help?
ElBerretin said:
Alright, so I was trying to make Nova Launcher my one and default launcher by moving it to /system. I had previously backed up and uninstalled Huawei's launcher with Titanium. But in the middle of things - had already uninstalled HW launcher and was trying to move Nova to /system - I made the mistake to think there would be a newer version available (which there was, but I couldn't update it on top of my current Nova version, dunno why). Karma strikes, I forget about not having a launcher and decide to reboot the phone to see if it was just Nova misbehaving or something (lol).
Now the phone shows bootanim alright, but goes to a "updating" EMUI screen which halts at 100% (I'm assuming the phone can't start without a proper launcher in /system). I said alright, let's push a Nova.apk to /system via TWRP (which works fine at least, so I know the phone isn't bricked), but upon trying to copy the app I get:
failed to copy 'NovaLauncher.apk' to '/system/app/': Is a directory
I don't know what to do; I have two NANDroid backups (one pre-root and another one after I made lots of modifications but phone still worked fine) but would preferrably install Nova rather than restoring the whole backup (if it's at all possible, of course).
Using instructions to install apps at /system/app through ADB gets me the message "remount of system failed: Success remount failed" upon trying /adb remount , and I don't know how to procede. Any help?
Click to expand...
Click to collapse
Restore you stock backup and forget making Nova a system app.
just go to nova settings and choose it as your default launcher and your done
clsA said:
Restore you stock backup and forget making Nova a system app.
just go to nova settings and choose it as your default launcher and your done
Click to expand...
Click to collapse
Why? Easily enough, I just had to mount the /system partition from TWRP, and then the commands breezed through. Booted into Nova straight away...
Related
Delete
How exactly are you transferring them to your sd card?
Sent from my SCH-I500 using XDA Premium App
Delete
Delete
Can you elaborate a little bit on exactly what happens? Do you mean the apps are uninstalled, or that they just don't appear in the launcher right away? Whenever you have apps on the SD, when you first boot it does take a few minutes for them to show up in the app drawer, since the system has to rescan the SD card and make sure everything is still there.
Same thing happened to me today. I'm rooted and was previously running one of the few 2.2 roms compatible with DL09.
In Adryn's new 2.8 thread, he stated that SC2.8 was compatible with DL09, so I decided to give it a try. I restored my apps via TB, making sure to restore "apps only" (no system data). All was well until I rebooted today in an effort to get Voodoo enabled (kept stating "enable on next reboot"). After rebooting, I now have 0 apps in my app drawer.
I re-DL'd Root Explorer to check my app drawer. Sure enough, they're all there... just not viewable or launchable in my app drawer.
I flashed via CWM (red) wiping: cache, dalvik cache, and system wipe before doing any of this, so I'm not sure where I went wrong?
Nevermind... got off easy. A simple reboot fixed my problems!
Delete
Hmm ... what launcher are you using? What ROM are you using? Just so I understand ... the icon is just gone, not turned into something different (i.e. a green and white box with an android on it - or something like that)?
If you are using Launcher Pro Plus, I had the same issue. Asks for unlock code, I put it in, says accepted, then forgets that it was input. I asked LP support about this and got this response. "You can solve this issue by using a root explorer and erasing /dbdata/databases/com.fede.launcher
If you are not rooted, a factory reset should work. I would recomend performing a backup prior to the reset."
I erased the file and it worked.
So, I'm kinda new at this, as I was told by the forums when trying to post this question in the official gsb thread
I got an eris a few weeks ago for free, and its my first android device. I used it for a while, then rooted it and installed GSB.v2.0-CM7.0.0_RC2_STABLE
I've got it all customized and got some cool apps installed and am loving it. My question is, can I just go into recovery and install GSB.v2.6-CM7.0.0_RC4_STABLE and be good to go, or do I have to back up all my apps and settings and start fresh? I have most of my apps moved to sd. Will they be okay? Also, I went into system and changed my bootscreen, lock and unlock sounds, and added a boot script. I will have to back those up and redo them if anything, right?
skot85 said:
So, I'm kinda new at this, as I was told by the forums when trying to post this question in the official gsb thread
I got an eris a few weeks ago for free, and its my first android device. I used it for a while, then rooted it and installed GSB.v2.0-CM7.0.0_RC2_STABLE
I've got it all customized and got some cool apps installed and am loving it. My question is, can I just go into recovery and install GSB.v2.6-CM7.0.0_RC4_STABLE and be good to go, or do I have to back up all my apps and settings and start fresh? I have most of my apps moved to sd. Will they be okay? Also, I went into system and changed my bootscreen, lock and unlock sounds, and added a boot script. I will have to back those up and redo them if anything, right?
Click to expand...
Click to collapse
You will lose your bootscreen during any ROM flash, plus whatever your boot script is I assume it's somewhere where it would get lost, too.
This may not work for your apps and system settings, but it's safe to try, then you'll know for sure if it'll work.
1. Go to your recovery and create a Nandroid backup of everything just the way it is.
2. Wipe Dalvik cache ONLY, do NOT Factory Reset/Wipe Data.
3. Flash GSB v2.6 and immediately after flash the GAPPs package, just like before.
4. If you had flashed the Cache2Cache script before you have to do that again as well, right after flashing the GAPPs.
5. Reboot and test everything to see if everything works to your satisfaction.
If it's doesn't then you have the Nandroid backup that you can restore. I can provide instructions that I use, and at least one other person has recently used and reported good about which uses Titanium Backup, but you'd really probably want to buy it off the market for it to be easier to do Batch backups and Restores (choose Menu/Batch from TB's main screen).
1. First, make sure the option is checked in TB's preferences to "Force to same location". FYI I do NOT use the checkbox for "Migrate system data". At THIS time (you can change it later), I suggest changing the Compression method to No Compression. This'll make sense in step 6.
2. From Menu/Batch, choose "Backup all user apps + system data".
3. Boot into recovery, do a COMPLETE wipe (Factory Reset/Data/Dalvik cache), flash your ROM and then your GAPPs (it's recommended at this time to NOT flash C2C just yet).
4. Reboot, SKIP setup of your Google account, go into Preferences/CyanogenMod settings/Application and check the box for "Allow application moving". I also change "Install location" to External, but that's up to you; this is just what works for me.
5. Boot back into recovery and flash C2C and reboot the ROM again.
6. Use File Manager, which comes with GSB and navigate to the TitaniumBackup folder (not TitaniumBackup-system). Find the Titanium Backup apk app installer file and reinstall it from here.
7. In TB, under Menu/Batch, choose "Restore all apps with data".
After this is done, reboot. If this works for you and you want to do this again in the future, you can make a copy of the Titanium Backup apk file to some other folder, that way you can re-enable compression in TB's preferences for future backups. I recommend LZ0.
I've been using this second method for the last 3-4 new versions of GSB, don't know how it would work with such a big jump in versions. If neither of these work for you, let me know if you still need help.
You will lose your bootanimation and any scripts you have but your apps will be fine. Like WRT said above just make sure you do a nandroid back up in recovery then wipe cache only. Once that's done flash 2.6 and gapps. Enjoy!
DINC|CM7|SLAYHER#27
Awesome. I had done a nandroid and ti backup to prepare, but I never saw the option in ti for force same location. I know how to backup and reinstall my lockscreen sounds and bootani, so I've got that down. Now that I look there's a 2.7 release which integrates the sdcard speed fix, so I won't need my init script now
Thanks for clearing that up for me, I'll post back when its done and tested if there's any issues.
Update: Well everything worked great! Thanks for all the help guys
recovery just says something is wrong, look at log?
I tried a few versions (of the backup sets), same error.
What am I doing wrong? How do I fix it? :crying:
Log from recovery run...
Starting recovery on Thu Aug 16 21:58:52 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (720 x 1280)
RA Revamped
Build : RA-VIGOR-v3.15-getitnowmarketing
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
fuzzynco said:
recovery just says something is wrong, look at log?
Click to expand...
Click to collapse
This happens all the time to people.
You can't simply restore a backup from another device because then your new device will actually appear as your old device on Google and Verizons servers, which will cause all sorts of problems if Verizon were to ever successfully restore your old phone and try and send it off to someone else. To avoid this problem, the recovery won't even let you restore a backup from another phone, even if its the exact same hardware.
Go to play.google.com, go to view your devices in the settings section. You should see two Rezounds. One will have been activated in the past, and one whenever you first turned on your replacement after receiving it and logging in with your account. So the one that was activated in the past is clearly your original Rezound that you've returned. You can give it a name, like "DEAD REZOUND" so that you know by looking at the name which Rezound Google thinks you're using.
There is a workaround that will let you restore the backup anyway if you want to search for it, but I highly recommend you don't. If you do, you can then go to play.google.com again, view your existing devices in the settings section, and you'll see that Google thinks your new phone is the same one you just sent back to Verizon. It should show "DEAD REZOUND" as being registered again today (or whatever day you successfully restored a backup from your old phone)
To sum up: Don't restore a backup from another Rezound. You pretty much have to start over again.
I kind of follow... RA is an image backup
so it would duplicate the serial and device specific data.
I could do a TiBu of the user apps and data (and the
new xml files of the call log and sms's), though.
Use an app to export the calendar data to an
.ics (iCal file) and the phone book to a .vcf
for import on the 'new' phone.
Since Google added some 800+ empty
phone book entries and messed up my phone
book, I don't sync with it. I export the whole
thing to a vcf.
So the missing /dev/tty0 device file
error from the restore is just AR not
letting me shot myself in the foot,
right?
I'll need to install my ROM, then
restore the user apps and data
from TiBu then rebuild my 'desktop'?
Is it worth doing the RUU for ICS
to get there? The new phone was
offered the upgrade OTA, but I think
it was wiped by the unlock prior to
S-Off process. Would I flash
the ICS RUU, then flash the ICS/JB
hboot, to get fastboot commands,
then reflash recovery?
I have seperate micro cards for
the 600mb RUU zip and the
ICS firmware/radio/hboot(JB)
zip.
I'm thinking since I have to rebuild
the desktop anyway, maybe doing
the ICS RUU first is a good idea.
fuzzynco said:
so it would duplicate the serial and device specific data.
I could do a TiBu of the user apps and data (and the
new xml files of the call log and sms's), though.
Use an app to export the calendar data to an
.ics (iCal file) and the phone book to a .vcf
for import on the 'new' phone.
Since Google added some 800+ empty
phone book entries and messed up my phone
book, I don't sync with it. I export the whole
thing to a vcf.
So the missing /dev/tty0 device file
error from the restore is just AR not
letting me shot myself in the foot,
right?
I'll need to install my ROM, then
restore the user apps and data
from TiBu then rebuild my 'desktop'?
Is it worth doing the RUU for ICS
to get there? The new phone was
offered the upgrade OTA, but I think
it was wiped by the unlock prior to
S-Off process. Would I flash
the ICS RUU, then flash the ICS/JB
hboot, to get fastboot commands,
then reflash recovery?
I have seperate micro cards for
the 600mb RUU zip and the
ICS firmware/radio/hboot(JB)
zip.
I'm thinking since I have to rebuild
the desktop anyway, maybe doing
the ICS RUU first is a good idea.
Click to expand...
Click to collapse
In reply to the bolded part: Basically, yes. AR's nandroid places the backups in a folder with your phone's serial as the folder name. Attempting to restore any backup from a folder with any other name will fail to prevent the issues I mentioned above.
I do not and have not ever used Titanium Backup, so in regards to that, I can't be of any help.
If you have a linux machine, you can mount the data.img from any of your backups and then copy all the files from /data/app and data/data to your phone. This will restore most of your apps, and app data/settings. There will still be a few things you'll have to redo from scratch, and this may not work 100% for every app on your phone, but at least this way you don't have to redownload every single app and manually redo all your settings...
I did the RUU zip (it restarted itself, as expected), the firmware/radio/hboot(JB) zip
and then reflashed AR 3.15 from fastboot. Everything seems to be working now.
Do you know if the debloat script (freeze VZW apps) works for ICS OTA ROM?
fuzzynco said:
I did the RUU zip (it restarted itself, as expected), the firmware/radio/hboot(JB) zip
and then reflashed AR 3.15 from fastboot. Everything seems to be working now.
Do you know if the debloat script (freeze VZW apps) works for ICS OTA ROM?
Click to expand...
Click to collapse
not sure...
I couldn't get ViperROM 1.0.3 to not crash (com.android.phone kept crashing).
Trying a couple of others that are prerooted and deboated. So far the ICS &
Sense 3.6 looks fine. Still have the 'social network' stuff to freeze though,
Could I do something like make a zip (from adb shell) of the user apps
/data/app & /data/data directories (to preserve the unix permissions).
and leave that on fat32 sd card? Then merge that into the zip for the
rom to be installed so the installer will reload them?
Would I need to add lines to the installer script to have it load /data (with
the subdirs ../app and ../data)?
hmms maybe better to make a seperate zip to preinstall my saved
/data subdirs? Can I copy the ROMs installer binary and build
a installer script to mount /data, then install the /data directory,
umount /data?
a.mcdear said:
This happens all the time to people.
You can't simply restore a backup from another device because then your new device will actually appear as your old device on Google and Verizons servers, which will cause all sorts of problems if Verizon were to ever successfully restore your old phone and try and send it off to someone else. To avoid this problem, the recovery won't even let you restore a backup from another phone, even if its the exact same hardware.
Go to play.google.com, go to view your devices in the settings section. You should see two Rezounds. One will have been activated in the past, and one whenever you first turned on your replacement after receiving it and logging in with your account. So the one that was activated in the past is clearly your original Rezound that you've returned. You can give it a name, like "DEAD REZOUND" so that you know by looking at the name which Rezound Google thinks you're using.
There is a workaround that will let you restore the backup anyway if you want to search for it, but I highly recommend you don't. If you do, you can then go to play.google.com again, view your existing devices in the settings section, and you'll see that Google thinks your new phone is the same one you just sent back to Verizon. It should show "DEAD REZOUND" as being registered again today (or whatever day you successfully restored a backup from your old phone)
To sum up: Don't restore a backup from another Rezound. You pretty much have to start over again.
Click to expand...
Click to collapse
not really. im on my third rezound and i restored the same viper rom i had before.
this is what i did with AR
1. back up current rom
2. boot into rom
3. use root explorer and find the nandroids
4. noticed 2 folders in the same nanadroid folder ( light bulb)
5. move old back up to the location where the new one was.
6. boot into recovery and did a full wipe
7. restored old back up.
8 boot phone
9. BAM!
This app might work. I use it and it works great but I'm not sure if it restores data.
synisterwolf said:
not really. im on my third rezound and i restored the same viper rom i had before.
this is what i did with AR
1. back up current rom
2. boot into rom
3. use root explorer and find the nandroids
4. noticed 2 folders in the same nanadroid folder ( light bulb)
5. move old back up to the location where the new one was.
6. boot into recovery and did a full wipe
7. restored old back up.
8 boot phone
9. BAM!
Click to expand...
Click to collapse
Yeah this works perfectly fine, but can cause the new phone to register on the network as if it were the old one. It is perfectly possible to restore a backup from another phone, and it works fine... its just a bad idea because if your old phone is ever "recovered" and turned back on, VZW might see two identical devices on the network, which will cause problems in the future.
a.mcdear said:
Yeah this works perfectly fine, but can cause the new phone to register on the network as if it were the old one. It is perfectly possible to restore a backup from another phone, and it works fine... its just a bad idea because if your old phone is ever "recovered" and turned back on, VZW might see two identical devices on the network, which will cause problems in the future.
Click to expand...
Click to collapse
Good to know. Thanks
In my case, the backup is from a device that i bricked totally. couldnt get into download mode so im thinking they will just use it as parts
Sent from my iPhone...
Has anyone been able to backup using Titanium. Titanium Pro tells me "Backup interrupted...not enough space." I have lots of space. I have tried all the google search solutions and none work.
I have the same problem. Initially, I thought that the sdcards were not mounted (for su root) but that wasn't the issue.
TB will currently backup VIRTUAL items (e.g. Accounts, WiFi access points) which have the TB logo next to it. It seems to fail for all other items.
gale2000 said:
Has anyone been able to backup using Titanium. Titanium Pro tells me "Backup interrupted...not enough space." I have lots of space. I have tried all the google search solutions and none work.
Click to expand...
Click to collapse
Same problem here. According to this post:
http://forum.xda-developers.com/showthread.php?t=2391363&page=7
the small app called sdfix could solve the problem. I haven't tried yet.
cr2069 said:
Same problem here. According to this post: http://forum.xda-developers.com/showthread.php?t=2391363&page=7 the small app called sdfix could solve the problem. I haven't tried yet.
Click to expand...
Click to collapse
Sorry, I've already tried sdFix along with other possible fixes.
(see rooting thread http://forum.xda-developers.com/showpost.php?p=55286180&postcount=55 and http://forum.xda-developers.com/showpost.php?p=55339398&postcount=85)
sdFix fixes the issue with not having write permission to the EXTERNAL SD card. TB is able to write to both INTERNAL and EXTERNAL sd cards -- for VIRTUAL items but it may not have sufficient permission for backing up apps, etc. I sent a log to TB support a few days ago without reply.
Anybody have luck with Helium?
https://play.google.com/store/apps/details?id=com.koushikdutta.backup
iammudd said:
Sorry, I've already tried sdFix along with other possible fixes.
(see rooting thread http://forum.xda-developers.com/showpost.php?p=55286180&postcount=55 and http://forum.xda-developers.com/showpost.php?p=55339398&postcount=85)
sdFix fixes the issue with not having write permission to the EXTERNAL SD card. TB is able to write to both INTERNAL and EXTERNAL sd cards -- for VIRTUAL items but it may not have sufficient permission for backing up apps, etc. I sent a log to TB support a few days ago without reply.
Click to expand...
Click to collapse
Too bad, seems to be TB's problem. Waiting for any progress...The main reason I want rooting is to use TB, but it's not working...
TB will now work if you RE-root your device:
Use SuperSU (settings option) to fully un-root.
Use Modding.MyMind's TWRP custom recovery from http://forum.xda-developers.com/ascend-mate2/orig-development/2014-09-22-teamwin-recovery-project-t2885144
Code:
adb reboot bootloader
fastboot boot TWRP_MT2-L03_RECOVERY.img
Backup your stock recovery.
Backup your stock bootloader.
Backup your system.
When you reboot, TWRP will notice that you're NOT rooted and ask if you wish to be rooted. Choose YES.
Reboot to System.
Start SuperSU and follow the prompts to update SuperSU binaries.
Good luck but you assume all risks. If there are errors in the above instructions, please reply in this thread.
Thanks again to all those involved in bringing TWRP to this device.
iammudd said:
TB will now work if you RE-root your device:
Use SuperSU (settings option) to fully un-root.
Use Modding.MyMind's TWRP custom recovery from http://forum.xda-developers.com/asc.../2014-09-22-teamwin-recovery-project-t2885144
Code:
adb reboot bootloader
fastboot boot TWRP_MT2-L03_RECOVERY.img
Backup your stock recovery.
Backup your stock bootloader.
Backup your system.
When you reboot, TWRP will notice that you're NOT rooted and ask if you wish to be rooted. Choose YES.
Reboot to System.
Start SuperSU and follow the prompts to update SuperSU binaries.
Good luck but you assume all risks. If there are errors in the above instructions, please reply in this thread.
Thanks again to all those involved in bringing TWRP to this device.
Click to expand...
Click to collapse
Shouldn't it be "fastboot flash recovery TWRP_MT2-L03_RECOVERY.img"?
I like the above method though because you get to back up the original recovery first. Just reboot to bootlloader and do "fastboot flash recovery TWRP_MT2-L03_RECOVERY.img" after the backup.
On another note, Titanium Backup still fails for me.
foltz61 said:
Shouldn't it be "fastboot flash recovery TWRP_MT2-L03_RECOVERY.img"?
I like the above method though because you get to back up the original recovery first. Just reboot to bootlloader and do "fastboot flash recovery TWRP_MT2-L03_RECOVERY.img" after the backup.
On another note, Titanium Backup still fails for me.
Click to expand...
Click to collapse
Yes, fastboot boot TWRP_MT2-L03_RECOVERY.img allowed me to try it out first. If it had failed, then hopefully I would still have had the stock recovery. (After playing around with TWRP a bit, I DID eventually flash it.)
foltz61 said:
On another note, Titanium Backup still fails for me.
Click to expand...
Click to collapse
Just now, TB failed again (insufficient storage error).
Had to rerun SdFix to check the platform.xml modifications, FULLY UNROOT and then RE-rooting with TWRP and reinstalling SuperSU again.
Now TB is working again. Very strange. (Will report back if I find out what triggered the problem.)
iammudd said:
Just now, TB failed again (insufficient storage error).
Had to rerun SdFix to check the platform.xml modifications, FULLY UNROOT and then RE-rooting with TWRP and reinstalling SuperSU again.
Now TB is working again. Very strange. (Will report back if I find out what triggered the problem.)
Click to expand...
Click to collapse
TB still didn't work for me after flashing recovery and rerooting. What did work was:
Set backup path to /data/media/0/TitaniumBackup.
Had to change owner on data and media and 0 to Root.
Changed permissions to read write and execute for owner, group, and other just to be safe.
I don't know if all of this was necessary, but it it working now.
I tried the same thing for the sdcard1, and Titanium said backup successful, but I couldn't find the backup on sdcard 1???
gale2000 said:
TB still didn't work for me after flashing recovery and rerooting. What did work was:
Set backup path to /data/media/0/TitaniumBackup.
Had to change owner on data and media and 0 to Root.
Changed permissions to read write and execute for owner, group, and other just to be safe.
I don't know if all of this was necessary, but it it working now.
I tried the same thing for the sdcard1, and Titanium said backup successful, but I couldn't find the backup on sdcard 1???
Click to expand...
Click to collapse
Same problem and this also fixed it for me thanks
gale2000 said:
TB still didn't work for me after flashing recovery and rerooting. What did work was:
Set backup path to /data/media/0/TitaniumBackup.
Had to change owner on data and media and 0 to Root.
Changed permissions to read write and execute for owner, group, and other just to be safe.
Click to expand...
Click to collapse
This workaround has been made obsolete. See next post:
I didn't know what the drawbacks are to using this folder so I was initially reluctant but I've given up and went down this path as well. However, I've reduced some permissions and here's what appears to be working for me:
Use ES Explorer to create the new folder and change its permissions to rwx for group and others. (I didn't need to change owners for any of the folders.)
Use ES Explorer to TEMPORARILY add read-only permission to /data for OTHERS.
Change TiBu backup folder location by manually navigating to the new folder.
Once the new folder has been selected, I restore /data to its original permissions. (The read permission was only needed temporarily for TiBu to find the new folder.)
Copying the files back to my PC, I can see that the zip files for the apks appear to have "reasonable" apk sizes (i.e. not zero-length as before).
I ran across this thread while digging into a Titanium Backup "Insufficient Storage" error and digging into an error thrown by Helium backup. In newer versions of SuperSU there is an option "Mount namespace separation" that's enabled by default. Running su and ls in a terminal shows that the /storage/sdcard0 and /storage/sdcard1 mount points don't come through into the root name space. Unchecking this option and rebooting will let both sdcards into the root namespace fixing the problem with Titanium backup.
Still trying to figure out what's going on with Helium. I have a hunch it may be due to use of a password without encryption, not sure yet.
kemonine96 said:
In newer versions of SuperSU there is an option "Mount namespace separation" that's enabled by default. Running su and ls in a terminal shows that the /storage/sdcard0 and /storage/sdcard1 mount points don't come through into the root name space. Unchecking this option and rebooting will let both sdcards into the root namespace fixing the problem with Titanium backup.
Click to expand...
Click to collapse
Thanks, this appears to have done the trick. It was very baffling when TiBu would work for some tasks but not others. Glad you stumbled onto this thread.
And another follow up for those using Helium or looking for an "adb backup" based solution
This device does not appear to include the full adb backup stack. From some limited testing tonight the pop-up prompt when running "adb backup' or using Helium Backup does not produce prompt on the device so it just fails. This is a known problem on some devices and it's too bad Huawei decided this wasn't a necessary inclusion.
kemonine96 said:
I ran across this thread while digging into a Titanium Backup "Insufficient Storage" error and digging into an error thrown by Helium backup. In newer versions of SuperSU there is an option "Mount namespace separation" that's enabled by default. Running su and ls in a terminal shows that the /storage/sdcard0 and /storage/sdcard1 mount points don't come through into the root name space. Unchecking this option and rebooting will let both sdcards into the root namespace fixing the problem with Titanium backup.
Still trying to figure out what's going on with Helium. I have a hunch it may be due to use of a password without encryption, not sure yet.
Click to expand...
Click to collapse
helium has never worked right for me. I bought it sight unseen since he's such a great dev, but just could not get it to work either rooted or unrooted. I did learn how to do adb backup though because if that.
nrfitchett4 said:
helium has never worked right for me. I bought it sight unseen since he's such a great dev, but just could not get it to work either rooted or unrooted. I did learn how to do adb backup though because if that.
Click to expand...
Click to collapse
Were you able to get adb backup to work at all? I never was able to get it to work.
I solved my titanium backup issues by going into SuperSU, then settings for SuperSU, and unchecked the mount namespace seperation box, then reboot
kemonine96 said:
Were you able to get adb backup to work at all? I never was able to get it to work.
Click to expand...
Click to collapse
It worked just fine for me. Used it to backup kids unrooted phones. That's been a couple years though.
I was trying to free up space and saw LG Home was taking up some space. Never knew it was a critical launcher. Ive tried millions of methods on various sites including xda, android forums, android central with no luck. Here is a rundown of the situation.
1. I had clockwork installed then it "disappeared" adb reboot recovery stopped letting me go to the clockwork bootloader
2. I have a custom ROM sitting on an sdcard called Cyanogen.zip Its never been messed with yet.
3. I do not have a "nandroid" backup or backup of the stock rom because clockworkmod never worked
4. Doing a factory reset did not fix the issue because apparently the OS runs live off the rom aka it never installs itself to the device like in WIndows . SO I get a total black screen setup screen with only a signal bar on top.
So the latest thing ive been trying is adb pushing a copy of LG_Home into the /system . This is not working because im getting a "permission denied" . Now before you get hasty please do not have me do these commands:
1. mount /system already did this back when doing clockwork
2. remount -o ,rw does not work, probably due to already having root
3. adb root tried it and it doesn't really do anything, I still get permission denied, and usage errors
This does not make sense because the phone is rooted (does factory reset take away root? ) , chmod 777 has been applied to /system . If I lost root doing a factory reset, is there a way to root the phone now that I don't have a functioning phone?
Here is what im aming to do with your help
1. Force the LG_Home.apk file into the /system
2. Force some way to get cyanogen mod installed as I now have a corrupt stock rom
Something has to work and im hoping someone will help me