Is it possible to flash a new ROM but somehow backup your applications so that they are installed when you have finished flashing?
This is not dev related.
Check Titanium Backup.
PookyPooka said:
Is it possible to flash a new ROM but somehow backup your applications so that they are installed when you have finished flashing?
Click to expand...
Click to collapse
You can try the hard way around:
# adb shell
# tar cf /sdcard/apps.tar /data/app/*.apk
restore:
# cd / ; tar xf /sdcard/apps.tar
(optional) # you can backup your user data:
# tar czpf /sdcard/data.tgz /data/data/*your.app.tuple*
for example:
# tar czpf /sdcard/google.talk.tgz /data/data/com.google.android.talk
Just make sure when you restore it, google talk has the same uid; if not, just chown the restored directory recursively with the new uid
restore same as above.
i like TAR method...will try it...
but i wud luv to have all my apps in a 'Apps.zip' and flash it after rom..
also flashable 'Data.zip' containing settings like wifi,sync and others...
can any one give me # commnads..
titanium backup
i cant get this app to work on cronos 1.5.1.
it always hangs on black screen saying "SU request" or "being loaded".
USB debugging is on and the "problems" button do download busybox was used also. but busybox stops downloading at 99%.
has anybody a hint for me?
cu
Has anyone tried removing bloatware after the J16 update? Root Explorer isn't working for me anymore. Terminal isn't working either. I get a:
rm failed for example.apk Read Only file system
I finally got rid of everything using Root Manager.
Anyone else encountered this issue? Any fix? Or do we need to wait for updates on the apps?
HG! said:
Has anyone tried removing bloatware after the J16 update? Root Explorer isn't working for me anymore. Terminal isn't working either. I get a:
rm failed for example.apk Read Only file system
I finally got rid of everything using Root Manager.
Anyone else encountered this issue? Any fix? Or do we need to wait for updates on the apps?
Click to expand...
Click to collapse
Anytime you get a "Read only filesystem" error in terminal when dealing with /system, you need to remount the partition as RW using
Code:
mount -o rw,remount -t yaffs2 /dev/block/stl9 /system
I removed all my bloatware using an adb shell without an issue.
I learn something new everyday.
Thanks burner!
I removed them all... but it's always good to know another way.
I want to unroot my phone, obviously i deleted everything needed to go back to stock so i was hoping someone could tell me the best method.
I want to unroot it because I have a feeling my phone has some sort of defect a ota/root won't fix. IT will NOT download MMS messages at all, it was working two weeks ago but since all download messages fail, my moms blackberry and sisters iphone work fine but mine will not.
My phone was rooted a long time ago, like in october but I never installed any rom's or anyhting, it has superuser and clockworkmod/rom manger. Awhile ago I tried to install things on rom manager but never noticed any difference. I also did the fix permissions thing.
Just wondering if its safe to use http://forum.xda-developers.com/showthread.php?t=867648
and if i decide to just keep the phone how would i go about updating the phone to newer roms?
The easiest way is to odin the DL09 stock rom to your phone. It will install the OTA to the latest firmware after you boot up.
There is also a thread started by Adrynalyne that has the EA28 and ED01 update.zips, do you don't have to OTA the updates (which takes forever to download). The thread is about how to get the most updated radio.
Of course, using Odin will wipe everything off your phone.
P.S. Rom manager is borked on our phones, so don't use it
Sent from my SCH-I500 using XDA Premium App
Yes it is safe to use that DL01 Odin file, that is what I use. I would do that, then see if MMS works.
You could do it manually through adb:
adb shell
su (its going to ask you for permission on your phone so hit allow)
mount -t rfs -o remount,rw /dev/block/stl9 /system
rm /system/app/Superuser.apk
rm /system/xbin/busybox
rm /system/xbin/su
rm /system/bin/su
rm /system/bin/busybox
mount -t rfs -o remount,ro /dev/block/stl9 /system
exit
OhioYJ said:
Yes it is safe to use that DL01 Odin file, that is what I use. I would do that, then see if MMS works.
Click to expand...
Click to collapse
I think you mean DI01 or DL09. There is no DL01
Hi,
I would like to know if voodoo rootkeeper is able to restore the root after the JB update ?
Greamlive said:
Hi,
I would like to know if voodoo rootkeeper is able to restore the root after the JB update ?
Click to expand...
Click to collapse
Worked for me
Does anyone know if the built in "OTA Root keeper" in SuperSU works too?
Sent from my Galaxy Nexus using Tapatalk 2
Unfortunately rootkeeper did not work for me. TPSparkyRoot and Debugfs were unsuccessful. Does anyone know of a root method for JB? The method used for TF300 perhaps?
Greamlive said:
Hi,
I would like to know if voodoo rootkeeper is able to restore the root after the JB update ?
Click to expand...
Click to collapse
Worked fine for me. FYI if you are using EZOverclock.apk freeze or remove it.
Scumbag Inc. said:
Unfortunately rootkeeper did not work for me. TPSparkyRoot and Debugfs were unsuccessful. Does anyone know of a root method for JB? The method used for TF300 perhaps?
Click to expand...
Click to collapse
Currently (to the best of my knowledge), the only way they could have root on the TF300 with JB was to restore root using both SuperSU and OTA Rootkeeper. There haven't been any new exploits as far as I know.
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app.
Rootkeeper did not work for me. The only apps I was using that required root were Titanium Backup and Samba Fileshare, plus obviously Super User and Busy Box. Anyway I can't use them now, with no root after updating to 4.1.1 despite Rootkeeper.
Something to take note of. Prior to the update I deleted my su backup and did it over again. Don't know if that made a difference or not but that was the only thing I did prior to the JB update.
Rooted, stock, locked bootloader.
My Transformer Prime just finished the update successfully!
Took several minutes to do whatever it does.
Lost root when updated, but Voodoo OTA RootKeeper restored root.
Nice to have JB on my Prime and Nexus 7.
Darkseider said:
Something to take note of. Prior to the update I deleted my su backup and did it over again. Don't know if that made a difference or not but that was the only thing I did prior to the JB update.
Click to expand...
Click to collapse
I checked and I have no /system/su_backup file, despite OTA RootKeeper telling me it was there before I installed the JB OTA. I wonder if my doing a cold boot before installing the OTA somehow erased the su_backup? I wish I had copied it somewhere else.
So I Do Have Su Backup File in sys but it doesnt work any thoughts? root keeper says it works but doesnt acually work
Updateing now.
I just erased and recreated my su backup with Voodo's OTA Rootkeeper.
back in a minute.
-------------
EDIT:
no dice.
installs .
restores the su binary at /system/bin/su
but it does not work.
-------------
Update got root access though adb using the backup su binary at /system/usr/we-need-root/su-backup
i just used the full path at the commad line...
copied the binary to /system/bin/su
more later.
-------------
Update:
got root working using
Root MANY ANDROID! [Upd: 20.09.2012]
I use linux so i just followed the steps in the batch file ( following the GOTO jumps for normal install) .
Problems:
this is the script i followed. it is in the zip at the link.
These are the command i used from the file. on linux i just replaced the stuff\adb.exe part with adb at the command line.
The files would not push to /data/local/tmp directly so i pushed the files to /sdcard/tmp then used adb shell and su'ed to cp (mv gave errors) them to /data/local/tmp
Code:
:START
echo Pushing busybox....
stuff\adb.exe push stuff/busybox /data/local/tmp/.
echo Pushing su binary ....
stuff\adb.exe push stuff/su /data/local/tmp/.
echo Pushing Superuser app
stuff\adb.exe push stuff/Superuser.apk /data/local/tmp/.
echo Making busybox runable ...
stuff\adb.exe shell chmod 755 /data/local/tmp/busybox
When i launched the backup app from adb it did not appear to ever stop. so i closed it after about 5 minutes and rebooted then continued.
Code:
stuff\adb.exe restore stuff/fakebackup.ab
echo Please look at your device and click RESTORE!
echo If all is successful i will tell you, if not this shell will run forever.
echo Running ...
stuff\adb.exe shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done" > NUL
echo Successful, going to reboot your device!
stuff\adb.exe reboot
echo Waiting for device to show up again....
ping -n 10 127.0.0.1 > NUL
stuff\adb.exe wait-for-device
The busybox binary did not work so i just used regular commands at adb shell prompt. Some of the commands required me to su first.
Code:
echo Going to copy files to it's place
stuff\adb.exe shell "/data/local/tmp/busybox mount -o remount,rw /system && /data/local/tmp/busybox mv /data/local/tmp/su /system/xbin/su && /data/local/tmp/busybox mv /data/local/tmp/Superuser.apk /system/app/Superuser.apk && /data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin/busybox && chown 0.0 /system/xbin/su && chmod 06755 /system/xbin/su && chmod 655 /system/app/Superuser.apk && chmod 755 /system/xbin/busybox && rm /data/local.prop && reboot"
:FINISH
echo You can close all open command-prompts now!
echo After reboot all is done! Have fun!
echo Bin4ry
pause
I may have left out some steps but if you follow the script and use su at the adb shell prompt you can get most of the steps to work. If there is enough demand i may put together a shell/bat script.
Greamlive said:
Hi,
I would like to know if voodoo rootkeeper is able to restore the root after the JB update ?
Click to expand...
Click to collapse
I had no issues. restored root perfectly
I lost root. Before i updated I deleted my backed up root in root keeper then protected again. Then updated to jb with file. Lost root but voodoo says I have a protected copy. But pressing restore does not bring it back. Hope there's a way to bring it back.
Edit: I did not temp unroot b4 update. Maybe my problem?
Sent from my DROID RAZR using xda app-developers app
Shinare said:
I lost root. Before i updated I deleted my backed up root in root keeper then protected again. Then updated to jb with file. Lost root but voodoo says I have a protected copy. But pressing restore does not bring it back. Hope there's a way to bring it back.
Click to expand...
Click to collapse
If i remember correctly from one of the previous updates, updating using a file is what caused voodoo to not be able to restore the root.
I had to wait until they found a new exploit to get it back.
x-web said:
I may have left out some steps but if you follow the script and use su at the adb shell prompt you can get most of the steps to work. If there is enough demand i may put together a shell/bat script.
Click to expand...
Click to collapse
I appreciate you pointing this out but here's the problem I'm running into. "mount: permission denied"
I can't su because I don't have root.
Here's what I do.
1. After knowing Superuser could very possibly be failed to restore root, I downloaded SuperSu in Google Play and installed it. Updated new binary of SuperSU.
2. Deleted the old backup in OTA Rootkeeper and protect the new root.
3. Went through OTA.
4. restored root from OTA Rootkeeper. Voila.
Something strange is going on here, i restored root with OTA root keeper, everything worked well and when i check status it states that my device is rooted and root permission granted.
Titanium Backup works perfectly as well, but other apps like Gesture Control are unable to get root access and when i run a root checker app it says that I dont have proper root access. Is there a way to fix this? Or is my root lost? I still have some hope as it works fine with TB
Stuff i'm still able to do:
-Temp unroot/reroot with OTA root keeper
-delete SU backup and make a new one
-Use Titanium Backup
-Use any root explorer i've tested so far, i can also access /data folder!
-Use Terminal emulator
-Also the file system/bin/SU is present.
What i cant do:
-app: gesture control
-update my SU binary with superuser app
-update my busybox using BusyBox free from play store
there must be a way!
Damn pissing on my sunny day. I want to see JB but am afraid of what problems it will cause. Thanks to all that posted saying OTA worked I hope it works for me too.
iamhcg said:
Here's what I do.
1. After knowing Superuser could very possibly be failed to restore root, I downloaded SuperSu in Google Play and installed it. Updated new binary of SuperSU.
2. Deleted the old backup in OTA Rootkeeper and protect the new root.
3. Went through OTA.
4. restored root from OTA Rootkeeper. Voila.
Click to expand...
Click to collapse
I did the same and can confirm that I successfully restored root.
Have a Verizon GS4 with ME7
Was able to root and use safestrap to install Hyperdrive. Played with it, now i want to go back to stock
In safestrap I click uninstall recovery and it seems like it goes through the motion of uninstalling. Also go into app manager and remove from there. On reboot i still see safestrap. I am able to boot back into my stock Verizon rom.
Any tips/tricks? Something I'm not seeing or catching? First time messing with this
joeyd161 said:
Have a Verizon GS4 with ME7
Was able to root and use safestrap to install Hyperdrive. Played with it, now i want to go back to stock
In safestrap I click uninstall recovery and it seems like it goes through the motion of uninstalling. Also go into app manager and remove from there. On reboot i still see safestrap. I am able to boot back into my stock Verizon rom.
Any tips/tricks? Something I'm not seeing or catching? First time messing with this
Click to expand...
Click to collapse
it's a know issue. Hashcode has provided instructions for manually removing SS in the OP of the dev thread. Be sure you read up on the modifications you're doing to your phone before you jump in, it'll save you confusion and frustration down the road.
Yes I've noticed the frustration part, should of waited
Through open terminal can i run the removal script/code?
su
mount -o remount,rw /system
mv /system/etc/init.qcom.modem_links.sh.bin /system/etc/init.qcom.modem_links.sh
rm -rf /system/etc/safestrap
rm /system/etc/firmware/q6.mdt
ln -s /firmware/image/q6.mdt /system/etc/firmware/q6.mdt
mount -o remount,ro /system