Hi,
I uninstalled TW4 from my phone and put GO Launcher into system. It was playing up today so I uninstalled it then reinstalled it...
Unfortunately I forgot to push it back into system before rebooting the phone. Now I have a lockscreen and then a crashing phone!
I can adb into it still and would like to know how to get either a launcher from my Titanium Backup into system/app, or from an apk I have on my desktop into system/app?
In adb I can't currently use remount for whatever reason.
I'm using CF-Root 3.5 kernel.
Thanks guys!
Stupidly lost launcher Huston We Have A Problem.
Factory reset ???
jje
Factory reset wont work I dont think due to the lack of TouchWiz at all!!
Also, trying to avoid a reset.
Thinking maybe I can launch Titanium via ADB and then I can sort it from there?
TheMathMan said:
Factory reset wont work I dont think due to the lack of TouchWiz at all!!
Also, trying to avoid a reset.
From recovery is how .
jje
Click to expand...
Click to collapse
Could you elaborate jje?
Code:
mount -o rw,remount /system
Posted by Chainfire himself in the kernel thread.
Then push normally with adb to system. You might need to use "su" before mounting but i don't think so with adb.
Edit:
Factory resets won't change anything since they don't touch the system partition, only data.
TheGhost1233 said:
Code:
mount -o rw,remount /system
Posted by Chainfire himself in the kernel thread.
Then push normally with adb to system. You might need to use "su" before mounting but i don't think so with adb.
Edit:
Factory resets won't change anything since they don't touch the system partition, only data.
Click to expand...
Click to collapse
Right... no joy. It mounted fine and a SU request came up on screen and all is good.
Then exiting shell and doing adb pus I get a permission denied error.
I can't enter adb push from # as it doesnt like it!
What am I doing wrong?
Also, what would be the am command to launch Titanium Backup from adb?
OK... read somewhere that you cant push directly to system/app with a secured kernel.
So I have pushed to sdcard and then cp to system/app... fingers crossed!
....
HURRAH!!!!
It reset the homescreen default and the menu popped up. Phew!
Related
Theres a new version of the Swype beta that is IMMENSELY better than the preloaded swype that comes with the atrix, it literally fixes all the annoying things of the older Swype versions:
http://beta.swype.com/
Swype 3.x beta works with the method below!
Process:
1) Use Root Explorer/Terminal/ADB to backup and then delete Swype.apk from /system/app and libSwypecore.so from /System/lib
2) Download the installer from https://beta.swype.com/android/get/ (on your phone)
3) Use installer to login and install latest version of swype
After your first phone reboot, if you are experiencing Swype Force closes after installing the latest swype, uninstall swype from your phone and then reinstall it; it should no longer force close after reboot.
If you are still experiencing force crashing after reinstall, try wiping your dalvik cache within CWM. Thanks Dudeman Broguy.
If you want to get in the latest beta, sign up over here. Registrations are open right now, hurry before they close them again!
Thanks to playin4sheezy for figuring this out: post #12
yes, i have been using it all day and it looks and feels great! if you have sideloading enabled, when you start the install it will ask to over write the current one.
graemegb said:
yes, i have been using it all day and it looks and feels great! if you have sideloading enabled, when you start the install it will ask to over write the current one.
Click to expand...
Click to collapse
Im trying to use the installer and it tells me to disable swype, and you cant disable the built in one. Can you pm me the apk?
Yea, I get to the point where it says "Licensing Swype, please wait...." and it doesn't get past that.
You need to go into /system/app and move Swype.apk to a backup folder on /mnt/sdcard
Then go into /system/lib and do the same for libSwypeCore.so
Give it a reboot and then try to install the beta. It worked for me
How did you move the apk, it wont allow me to do so
playin4sheezy said:
You need to go into /system/app and move Swype.apk to a backup folder on /mnt/sdcard
Then go into /system/lib and do the same for libSwypeCore.so
Give it a reboot and then try to install the beta. It worked for me
Click to expand...
Click to collapse
woo nice! thanks that worked for me! no more stupid tip window!
Krshaw18 said:
How did you move the apk, it wont allow me to do so
Click to expand...
Click to collapse
you have to use root explorer (and be rooted) or you could use terminal/adb (still have to be rooted)
Sorry for the noob questions! Move it completely? or make a back up of it? and also any apps out there like root explorer but free ?
I tried the above steps but the libswypecore is still in the system folder when i move it as it is read only...
Krshaw18 said:
Sorry for the noob questions! Move it completely? or make a back up of it? and also any apps out there like root explorer but free ?
Click to expand...
Click to collapse
If youre rooted, root explorer is worth the money. You have to move Swype.apk completely, and make sure its not there after moving or the install wont work.
Make sure if you are in Root Explorer that you click the R/W button at the top to make the system folder Read/Write access. Then long press the files and click move and goto sdcard and make a folder named "whatever you want" then click paste..
Or you could do this using adb with Atrix plugged into the computer:
goto command prompt
type the following:
adb shell
su
mkdir /mnt/sdcard/swype_backup
mount -o rw,remount /dev/block/mmcblk0p12 /system
cp /system/app/Swype.apk /mnt/sdcard/swype_backup
cp /system/lib/libSwypeCore.so /mnt/sdcard/swype_backup
rm /system/app/Swype.apk
rm /system/lib/libSwypeCore.so
Hopefully this gets you going
playin4sheezy said:
Make sure if you are in Root Explorer that you click the R/W button at the top to make the system folder Read/Write access. Then long press the files and click move and goto sdcard and make a folder named "whatever you want" then click paste..
Or you could do this using adb with Atrix plugged into the computer:
goto command prompt
type the following:
adb shell
su
mkdir /mnt/sdcard/swype_backup
mount -o rw,remount /dev/block/mmcblk0p12 /system
cp /system/app/Swype.apk /mnt/sdcard/swype_backup
cp /system/lib/libSwypeCore.so /mnt/sdcard/swype_backup
rm /system/app/Swype.apk
rm /system/lib/libSwypeCore.so
Hopefully this gets you going
Click to expand...
Click to collapse
Thanks a bunch!
Wont let me delete
Sent from my Atrix 4G using XDA App
joshuajoshua said:
Wont let me delete
Sent from my Atrix 4G using XDA App
Click to expand...
Click to collapse
Is your phone rooted? If so, then when you typed su in adb shell(not terminal) did it ask you for superuser permission? If so, then you should make sure and accept it.
If your phone is not rooted, then I don't think your gonna get this working
Sent from my MB860 using XDA App
I didnt need to move/delete libSwypeCore.so and the install worked fine.
andy2na said:
I didnt need to move/delete libSwypeCore.so and the install worked fine.
Click to expand...
Click to collapse
Ok. Be aware that I've had previous issues with swype after few days of use because I didn't remove that file
Sent from my MB860 using XDA App
I would suggest someone testing that you can in fact put it back to the stock setup. Mine somehow got deleted when i first got the phone, and it doesn't come back, factory reset or otherwise.
cegna09 said:
I would suggest someone testing that you can in fact put it back to the stock setup. Mine somehow got deleted when i first got the phone, and it doesn't come back, factory reset or otherwise.
Click to expand...
Click to collapse
i have been messing with swype for the last few days
i can guarentte you that if u installed / mounted a messed up version of swype (WVGA with a language pack in my case), you can just use put the backup stock swype back on /system/app and it'll be fine again
i get an error on sign-in into the installer, says device id dont match. any ideas?
EDIT: I had to log into mySwype and remove my old phone (nexus one) and then now it works!
Hello guys.
Yesterday i installed Chainfire 3D from Android Market and then installed driver. My phone is now not booting, just galaxy s logo. How can i delete this driver and repair my Android? It's located on my memory card.
Re-apply permissions to all files. Mount the ext2 partition read/write on Linux, cd to it, and do "chmod 0777 ./* -v -R" and then "chmod 4755 ./system/xbin -v -R". Flush the cache with "sudo sync" and unmount.
By the way, how did you manage to install Chainfire? It keeps giving me an error when I do, about not being able to mount /system read/write.
Is this commands safe for my data or i will lose it?
How i installed? Just by downloading *.apk file.
Are you sure? Installing the apk only installs a tool which takes you to a menu to install the driver. If you don't click the icon and go through the install process inside the app nothing happens, so CF3D is most likely not the cause of your problem.
The commands I posted should still solve it and they don't destroy any data.
tydem said:
By the way, how did you manage to install Chainfire? It keeps giving me an error when I do, about not being able to mount /system read/write.
Click to expand...
Click to collapse
You need a kernel which doesn't mount /system as read-only. If you use the latest release from nbates, then I think your only solution is to remount /system as rw either via adb or from a terminal emulator on the device, then install cf3d
anghelyi said:
You need a kernel which doesn't mount /system as read-only. If you use the latest release from nbates, then I think your only solution is to remount /system as rw either via adb or from a terminal emulator on the device, then install cf3d
Click to expand...
Click to collapse
Going to try. If the shell script cannot mount it I doubt a terminal will, but whatever. I'm using the SD version with the audiofix kernel (can't remember date) and the MIUI ROM by the way.
tydem said:
Are you sure? Installing the apk only installs a tool which takes you to a menu to install the driver. If you don't click the icon and go through the install process inside the app nothing happens, so CF3D is most likely not the cause of your problem.
The commands I posted should still solve it and they don't destroy any data.
Click to expand...
Click to collapse
My problem is that I installed that driver (CF3D) from tool. Your commands doesn't help. My android still is not booting.
@edit:
problem solved, i reinstalled system folder
I seem to be having the same exact problem, can someone tell me the adb lines to fix this? not sure how to reinstall the system folder
I have an unlocked+rooted CM7 Atrix which was working nicely this morning.
I was playing around and decided to install Titanium Backup. I also read somewhere that it needs BusyBox to work better so I decided to install that too.
i tried installing BusyBox in /system/xbin and it gave me an error about BusyBox being already installed
now for some reason I can't seem to do anything in a terminal emulator or adb except "cd" and "su" (Root checker returns success)
I'm getting a "permissin denied" error with basic commands like ls, cp, mv, mount, chmod
any suggestions?
thanks
this is just a shot in the dark but have you tried to fix permissions in cwm... its fixed odd things like that for me sometimes... also cant hurt to clear dalvik cache too jic... that has also helped at times. use a program like root explorer to check if busybox is actually there as well. other then that i have to shrug my shoulders lol
viperlox said:
this is just a shot in the dark but have you tried to fix permissions in cwm... its fixed odd things like that for me sometimes... also cant hurt to clear dalvik cache too jic... that has also helped at times. use a program like root explorer to check if busybox is actually there as well. other then that i have to shrug my shoulders lol
Click to expand...
Click to collapse
actually I was thinking about doing the fix permissions thing last night but I couldn't remember where I saw the option to do that
Anyways, I did try it just now as well as clearing the dalvik cache and they didn't seem to help.
I also tried root explorer last night (bought it just for this purpose) but it doesn't seem to be pulling up any data, it just hangs at a black screen when I open it and then it force closes.
I have a guess though but I have no way of confirming this since ls and explorers doesn't seem to work.
I used to have "su" in /system/bin as well as a couple of self-written scripts but they don't seem to be there anymore. when I try "/system/bin/su" or any of my scripts it give me the "not found" message
While poking around I then realized that there is a "su" in xbin (this is the one that runs when su is called without it's direct path). I'm guessing this works since root checking detects it.
So, I'm thinking maybe my /system/bin got wiped out when the new stuff (eg su) in xbin got created? Then maybe I don't have proper access to xbin? Like maybe when I installed busy box, it wiped out some of my stuff in /bin and copied/created then in /xbin and failed to set permissions?
Does this sound possible? Also, would it be possible to reflash /bin and /xbin to whatever came with CM7 maybe?
Thanks
johnusesandroid said:
I have an unlocked+rooted CM7 Atrix which was working nicely this morning.
I was playing around and decided to install Titanium Backup. I also read somewhere that it needs BusyBox to work better so I decided to install that too.
i tried installing BusyBox in /system/xbin and it gave me an error about BusyBox being already installed
now for some reason I can't seem to do anything in a terminal emulator or adb except "cd" and "su" (Root checker returns success)
I'm getting a "permissin denied" error with basic commands like ls, cp, mv, mount, chmod
any suggestions?
thanks
Click to expand...
Click to collapse
Just so you know busybox is included in atrix roms. There was/is no need to install it again.
You could try to push the folders you want from a cm7 zip file. Or you could just reflash cm7 without wiping data/factory resetting.
_Dennis_ said:
Just so you know busybox is included in atrix roms. There was/is no need to install it again.
You could try to push the folders you want from a cm7 zip file. Or you could just reflash cm7 without wiping data/factory resetting.
Click to expand...
Click to collapse
I ended up reflashing CM7 thanks for the tip
Hi all,
happened to me a mishap.
I had done a full wipe but forgot to push the stock launcher back on it, well now the launcher is missing and I can not do anything.
Would have otherwise update the Asus HC recorded but do not know how that should go without Launcher
Who has an advice what I could do?
sorry, trying to understand...
Had you done some sort of modification that removed the stock launcher? There isn't any reason why the stock launcher wouldn't be present. Can you try another factory reset using vol up + power? i don't recall exactly what the sequence is.
Its ok,
my english is not the best.
I delete the stock launcher with a script and forgot to restore it.
And then i do a factory resett..........
No Launcher anymore.........
A Androiddevice without an launcher become a bootloop or something similar
Did you uninstall the APK "launcher2.apk" and it's odex "launcher2.odex"?
I made that mistake and what i had to do was use ADB to install a 3rd party launcher (I found an APK for launcher pro and used that) and then once I had a working launcher, I downloaded Root explorer (I was rooted) and moved the "Launcher2.apk" and "launcher2.odex" into the /system/app folder. From there, I rebooted and everything was gravy
It is essential to include both the .apk and the .odex. Also, you have to have the files from the same build version you are. (You can't use an odex from 8.8.3.29 on a tablet running 8.8.3.33)
does ADB see your device? If so maybe you can push launcher API back to /system/app then set the permissions and you should be all set.
Sent from my Transformer Prime TF201 using xda premium
bscotth said:
Did you uninstall the APK "launcher2.apk" and it's odex "launcher2.odex"?
I made that mistake and what i had to do was use ADB to install a 3rd party launcher (I found an APK for launcher pro and used that) and then once I had a working launcher, I downloaded Root explorer (I was rooted) and moved the "Launcher2.apk" and "launcher2.odex" into the /system/app folder. From there, I rebooted and everything was gravy
It is essential to include both the .apk and the .odex. Also, you have to have the files from the same build version you are. (You can't use an odex from 8.8.3.29 on a tablet running 8.8.3.33)
Click to expand...
Click to collapse
Yes i uninstall the launcher2_apk and odex file.
ADB dont see my device.
I think its a mistake in the USB driver.
I pluged the prime in and MTP doesnt install correctly.
cooper1988 said:
Hi all,
happened to me a mishap.
I had done a full wipe but forgot to push the stock launcher back on it, well now the launcher is missing and I can not do anything.
Would have otherwise update the Asus HC recorded but do not know how that should go without Launcher
Who has an advice what I could do?
Click to expand...
Click to collapse
cooper1988, what you have to do is download a new launcher in your pc, put it in your sd card and apply it with the recovery mode in "apply any zip from sd".
ajmdve said:
cooper1988, what you have to do is download a new launcher in your pc, put it in your sd card and apply it with the recovery mode in "apply any zip from sd".
Click to expand...
Click to collapse
prime doesnt have a recovery (locked bootloader)
Power + Vol D --> Wipe or boot Android
well, then you might try flashing a new rom. sorry but if your pad doesnt have recovery, the it is the only way i see.
ajmdve said:
well, then you might try flashing a new rom. sorry but if your pad doesnt have recovery, the it is the only way i see.
Click to expand...
Click to collapse
won't it try to flash whatever image is on the sd card with that combo, effectively a hard reset?
Year
ADB show my device.
But i cant push the apk to /system/app or /data/app
failed to copy 'launcher.apk' to '/data/app/launcher.apk': Permission denied
a hard reset is not useful in this case because the launcher in not in the system folder anymore. he have to flash the pad with odin or any other method alike.
cooper1988 said:
Year
ADB show my device.
But i cant push the apk to /system/app or /data/app
failed to copy 'launcher.apk' to '/data/app/launcher.apk': Permission denied
Click to expand...
Click to collapse
I believe you have to mount /system in order to do that push
c:\android-sdk\platform-tools>adb shell mount /system
mount: permission denied
i dont have root on the prime and nachoroot doesnt work ( i have hc)
c:\android-sdk\platform-tools>adb push nachoroot.bin /data/local/
1140 KB/s (15182 bytes in 0.013s)
c:\android-sdk\platform-tools>adb shell chmod 777 /data/local/nachoroot.bin
chmod: permission denied
a hard reset wont do anything
tdrussell said:
won't it try to flash whatever image is on the sd card with that combo, effectively a hard reset?
Click to expand...
Click to collapse
a hard reset wont do anything, because it restores all by default, but, if the launcher isn't in the system folder, the phone wont make it appear from nowhere.
he should flash a new rom using odin or some other tools alike.
I am in a similar situation I am stuck in a boot loop! Not able to get passed the asus logo loading sign!
I can not get in ADB because of dumb asus sync I still need to try using ADB on linux! Because that does not need the asus sync
Sent from my PC36100 using Tapatalk
how it happens?
Wordlywisewiz said:
I am in a similar situation I am stuck in a boot loop! Not able to get passed the asus logo loading sign!
I can not get in ADB because of dumb asus sync I still need to try using ADB on linux! Because that does not need the asus sync
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
how it happens?
ajmdve said:
how it happens?
Click to expand...
Click to collapse
Well idrk either the system apps I froze or the changing the build.prop (added enable. Facelock) but even after I had done that I had rebooted Atleast twice
But maybe it only checks those things on a kernel panic
Sent from my PC36100 using Tapatalk
you rebooted twice and it starts completelly or it always get stuck in the boot logo?
cooper1988 said:
c:\android-sdk\platform-tools>adb shell mount /system
mount: permission denied
i dont have root on the prime and nachoroot doesnt work ( i have hc)
c:\android-sdk\platform-tools>adb push nachoroot.bin /data/local/
1140 KB/s (15182 bytes in 0.013s)
c:\android-sdk\platform-tools>adb shell chmod 777 /data/local/nachoroot.bin
chmod: permission denied
Click to expand...
Click to collapse
before you did factory reset , u removed the launch apk right ? so you had root before you did factory reset , you should still have it now , because factory wipe does not remove root.
Hello everybody,
i have gained root access to my phone via backup/restore method through adb where local.prop is stored in /data/. So when i log onto my phone with adb i have root access. I copied busybox, su and the superuser.apk to the right place and removed the local.prop file again. After a reboot I was hoping to remove some crapware off my phone but to my surprise the binaries i copied vanished from the filesystem. So the phone reverted the changes by itself. I did this process several times copying busybox and su to various places referred to by $PATH, but it´s everytime the same after i reboot. The files are gone.
After the first attempts failed i tried to make changes to my phone while logged in as root. I wanted to uninstall unnecessary packages with "pm uninstall" but that failed also. The command just responds "failed". Even when /system is mounted rw (it remounts itself to ro after a while though). I´ve also made changes to /init.rc but they are also gone after a reboot as other changes i´ve made. Basically i wasn´t able to accomplish anything with root access no matter what i did.
So what i want to know is how this black magic works andy why i cant do anything with root. I know how to achieve real root through htc dev and various other methods.
Thanks for reading!
nasenstueber said:
Hello everybody,
i have gained root access to my phone via backup/restore method through adb where local.prop is stored in /data/. So when i log onto my phone with adb i have root access. I copied busybox, su and the superuser.apk to the right place and removed the local.prop file again. After a reboot I was hoping to remove some crapware off my phone but to my surprise the binaries i copied vanished from the filesystem. So the phone reverted the changes by itself. I did this process several times copying busybox and su to various places referred to by $PATH, but it´s everytime the same after i reboot. The files are gone.
After the first attempts failed i tried to make changes to my phone while logged in as root. I wanted to uninstall unnecessary packages with "pm uninstall" but that failed also. The command just responds "failed". Even when /system is mounted rw (it remounts itself to ro after a while though). I´ve also made changes to /init.rc but they are also gone after a reboot as other changes i´ve made. Basically i wasn´t able to accomplish anything with root access no matter what i did.
So what i want to know is how this black magic works andy why i cant do anything with root. I know how to achieve real root through htc dev and various other methods.
Thanks for reading!
Click to expand...
Click to collapse
is your RECOVERY.img
and beside i dont really think your /system is fully mounted rw
mauricio.valladolid said:
is your RECOVERY.img
and beside i dont really think your /system is fully mounted rw
Click to expand...
Click to collapse
Thanks for the reply. i use mount -o remount,rw /system as mount command to get read/write permission on /system. If there is something more to do please let me know. And if the behavior i ve seen is caused by the recovery.img is there something i can do about it?
nasenstueber said:
Thanks for the reply. i use mount -o remount,rw /system as mount command to get read/write permission on /system. If there is something more to do please let me know. And if the behavior i ve seen is caused by the recovery.img is there something i can do about it?
Click to expand...
Click to collapse
why dont you just install ext4 recovery and flash supersu.zip?
I really dont get it why are you trying to do it the hard way