Database Users

[Q] Need help reinstalling stock Twitter app

Okay, I rooted my N1 with Universal Androot and removed the stock Froyo Twitter app without backing it up. (Shame on me.) Now, I can't update to 2.2.1 because of it (a status 7 error complaining about not finding /system/app/Twitter.apk)
I have, at the advice of some other forum posts I've read, installed Twitter from Android Market and backed it up to the sd. Renamed it Twitter.apk and used the Terminal Emulator to copy it to /system/app. That worked and the file is there, but the update still will not apply. Do I also need a .odex file? Is there any way to update at this point?
Any help would be super appreciated. THANKS!

if this is the new twitter app would you be kindly enough to share it..lol
Sent from my Nexus One

grab it from an older update like from frf91 update.. then do adb push /system/app
if you cant do that...
put the twitter app in sdcard then go to terminal and do
cp /sdcard/twitter /system/app
reboot then apply it.. i had trouble with amazon and i did it that way and it worked well

ilostchild said:
put the twitter app in sdcard then go to terminal and do
cp /sdcard/twitter /system/app
reboot then apply it.. i had trouble with amazon and i did it that way and it worked well
Click to expand...
Click to collapse
That's exactly what I did. It didn't work.
I'd love to pull the app from a FRF91 build but I have no idea how that's done.

Flash a GAPPS update (try the on listed with CM6)
Sent from my Nexus One using XDA App

danger-rat said:
Flash a GAPPS update (try the on listed with CM6)
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
It looks as though I can't flash the GAPPS without unlocking the bootloader and installing a new recovery, correct? I'm really not that motivated if that's the case. I appreciate the information.

OK, just download the GAPPS, then use something like estrongs file manager to unzip to a folder of choice (with estrongs, longpress and select extract).
The Twitter apk will be in the extract folder/system/app. Just click the apk to install...
Sent from my Nexus One using XDA App

BTW, if you have root, you may as well install a custom recovery (without touching the bootloader).
Easy way with ROM Manager (has Clockworkmod and Amon-Ra), or use adb if you wanna learn something...
Sent from my Nexus One using XDA App

Thanks for the tips. I'll check it out tomorrow when I can make a data transfer. I am doubtful that installing from the zip will solve much since I already loaded the app and its already in the system folder.
could someone verify whether or not the Twitter app has a corresponding odex file that I might need?

I ran into the same problem when I removed Amazon Mp3, but I was impatient so I ended up reflashing the stock rom and then updating.

There is a thread that has all n1 updates look for it and download froyo fr91 update then unzip it go to system app and look for twitter apk then put in sdcard and do commands again .. I tried to do with market twitter and it failed so I did it the way I'm explained andnworkd

[SOLVED]
ilostchild said:
There is a thread that has all n1 updates look for it and download froyo fr91 update then unzip it go to system app and look for twitter apk then put in sdcard and do commands again .. I tried to do with market twitter and it failed so I did it the way I'm explained andnworkd
Click to expand...
Click to collapse
You sir, have saved my life. I swear I used that same exact Twitter.apk but I must not have. I used 3 different apks all with the same result but the one in the zip I found somewhere in this forum worked perfectly. I appreciate all the help and feel like such a 'tard for not trying something so seemingly simple earlier.

68pontiac said:
You sir, have saved my life. I swear I used that same exact Twitter.apk but I must not have. I used 3 different apks all with the same result but the one in the zip I found somewhere in this forum worked perfectly. I appreciate all the help and feel like such a 'tard for not trying something so seemingly simple earlier.
Click to expand...
Click to collapse
No problem man.. glad you got it working.. now reroot the phone and back up all the apps from then phone.. doin adb pull /system/app

God Mode? (solved)

How can I activate God Mode on a rooted XOOM? I want to nullify some stock apps, but Root Explorer is saying they are read only.
Thanks.

[edit] Changed the thread question.

LOL. I didn't know we were playing Quake.
What do you mean by god mode. You already have root. That's all you should need.
Sent from my Nexus One using XDA App

lol.
That might not be the correct term, and it may require a custom rom. Not sure, but on Project Elite for the OG Droid, there's an option under General>System called God Mode that gives you full access to files on the system. That may just be what Actngrezy calls it in PE.
I just want to rename some of the apps that were included on the XOOM. Specifically, I want to nullify the Quick Office apk so I can install the NI Adam version. When I navigate to the apk in Root Explorer, I get an error telling me it's a read only file. I never got that error with the Droid. I can change whatever I want to on that device.

Did you click on mount r/w in root explorer

arrtoodeetoo said:
How can I activate God Mode on a rooted XOOM? I want to nullify some stock apps, but Root Explorer is saying they are read only.
Thanks.
Click to expand...
Click to collapse
Did you install superuser? if so make sure you have allowed root explorer in it. Then on the top left hand side in root explorer hit mount r/w

arrtoodeetoo said:
lol.
That might not be the correct term, and it may require a custom rom. Not sure, but on Project Elite for the OG Droid, there's an option under General>System called God Mode that gives you full access to files on the system. That may just be what Actngrezy calls it in PE.
I just want to rename some of the apps that were included on the XOOM. Specifically, I want to nullify the Quick Office apk so I can install the NI Adam version. When I navigate to the apk in Root Explorer, I get an error telling me it's a read only file. I never got that error with the Droid. I can change whatever I want to on that device.
Click to expand...
Click to collapse
Im just visiting the forum to steal a few files to compare with atrix , how ever if i read your cleverly phrased question correctly and you are trying to remove/freeze some apps that came on the Xoom and you are getting read only error its because to modify anything in the /system dir you need to
1. back up anything you might remove via adb pull or via adb shell cp
2. adb shell
3.su
4. mount -o rw,remount (what ever the path to zoom block is i dont know cause i dont have one ) exp /dev/block/mmcblk0p12 /system
from there you can remove what ever you want out of system dir
5. exp. rm /system/app/quickoffice.apk

Thanks! I never noticed that button before. lol.

you can also get a system uninstaller in the market that will do it for you just the same, I usually use that in case there is more included than just the apk file

PaulG1488 said:
Did you click on mount r/w in root explorer
Click to expand...
Click to collapse
x 2
Sent from my Xoom using XDA Premium App

I thought about the uninstaller thing, but I'd rather not uninstall anything that came on the XOOM just in case. I just add an extra .null at the end of the apk (and associated files, which are easy to find) in case I need to restore them.
For instance, the NI Quick Office app force closes when you just breathe on the freaking tablet, so I had to restore the default one.

Cannot for the life of me get system r/w permissions

I've been running cm7 nightlies and now stable 7.0 for some time now. I have the new radio, ladios' kernel, and the sdcard read fix flashed.
I installed super manager and successfully deleted some of the stock cm7 media off my phone last week. Today, I came across the new GPS.conf files and wanted to try them.
Super manager couldn't switch the system to r/w despite saying "ok"
When I try to delete or write in the system with EStrongs file explorer, ghost commander, or android mate, they all give strange errors. The deleted files disappear but reappear after reboot. If I try to paste a file in system/etc I only get an error.
Superuser is successfully allowing permissions. I have the latest busybox. I have r/w enabled in each file manager.
I even tried an adb push test which first said "system is r/o only". The next try was "successful" but didn't do anything.
I'm still new with adb so I probably did something wrong. I typed in that r/w command, mount now shows: /dev/block/mtdblock3 on /system type yaffs2 (rw,relatime)
I can't figure out what changed and what I need to do to get r/w permissions. My only theory is that i had uninstalled and reinstalled super manager earlier and that somehow messed with my permissions.

You cannot permanently modify the system partition while the phone is booted into Android. The only way is to use adb while the phone is in recovery mode. Any changes you make while the phone is booted will be lost after a reboot.
Go check on those media files you thought you deleted. I bet you'll find they are still there.

Yes that worked. Thank you.
I thought I had read somewhere that you had to be booted to adb push.
I also thought that root managers advertising r/w capability would make permanent changes.
Next question:
Can I add and remove files from the cm7 zip before flashing it? Do I have to rezip it in any special or can windows 7 manage it fine?
EDIT: Ok I guess i need to sign it... lets see...

jamus28 said:
Yes that worked. Thank you.
I thought I had read somewhere that you had to be booted to adb push.
I also thought that root managers advertising r/w capability would make permanent changes.
Next question:
Can I add and remove files from the cm7 zip before flashing it? Do I have to rezip it in any special or can windows 7 manage it fine?
EDIT: Ok I guess i need to sign it... lets see...
Click to expand...
Click to collapse
You don't need to sign them on the aria
Sent from my Liberty using XDA App

jamus28 said:
Yes that worked. Thank you.
I thought I had read somewhere that you had to be booted to adb push.
I also thought that root managers advertising r/w capability would make permanent changes.
Click to expand...
Click to collapse
Those programs will work on some phones but not the Aria.
Next question:
Can I add and remove files from the cm7 zip before flashing it? Do I have to rezip it in any special or can windows 7 manage it fine?
EDIT: Ok I guess i need to sign it... lets see...
Click to expand...
Click to collapse
It really is as simple as adding or removing a few files from the zip file if you want to modify it.

Alternative thoughts on preventing OTA update

I don't think I have seen any mention of this idea yet. Sorry if I missed it...
In a recent thread about the 6.2.2 update and people wanting to prevent it, I thought I read that someone saw the file show up in the update directory. I'm assuming this means the same 'kindleupdates' directory you could manually drop the update into -- but if not, the idea is the same. Why not just take some step to prevent access to this directory?
The exact step to take would depend on how smart the developers were about dealing with problems in the update process
The easiest step would be to chmod 555 it. But of course if the update process is running as root it is under no requirement to honor those permissions! (My experience in the unix world tells me that about half the time, programs running as root do honor the permissions even though technically root overrides them).
Another easy step would be to delete it altogether. But they probably thought of that (if it's /mnt/sdcard/kindleupdates where someone could easily accidentally delete it) and recreate it if it's missing.
One trick that is often done is to replace the directory with a file. Some programmers do not think to check this kind of condition - they see there is something there, but they get an error opening it as a directory, and they just declare it's an error.
A more subtle trick would be to replace the directory with a symlink that points to a read-only directory (such as /system). In this case, they could open it as a directory, and just fail to write there. The programmer probably would not have thought to check whether it's a link vs. a real directory. One possible gotcha is if you point to /system, and /system is r/w, then the update could screw something up under /system. So maybe mount /system r/w, mkdir /system/kindleupdates, remount /system r/o, then link the update dir to /system/kindleupdates.
And finally, I don't know if Android has any kind of loopback filesystem capability, but loopback-mounting something read/only on that directory would certainly fake the OS into thinking there was a directory there; it would definitely be read/only, and I don't think they would ever think to check whether there is actually some filesystem mounted there! (and if there was, all you need is an app that constantly accesses some file you put there, which would make it busy so that it couldn't be unmounted).

The first method won't work because the sdcard partition is fat32 and doesn't accept unix permissions.

it downloads to the /cache folder - this folder is also used for other things like market downloads, logs from twrp and i don't know what else
btw. there are a lot of threads about this from the 6.2.1 update
make a short search for "prevent ota update" - you'll have a lot to read ...

well, i just deregistered my kindle acount and i'm still in 6.2.1...

b63 said:
it downloads to the /cache folder - this folder is also used for other things like market downloads, logs from twrp and i don't know what else
Click to expand...
Click to collapse
Ah, that makes this less practical. Still, perhaps when the next update comes out I can try a variation on this but it requires the filename to be known.
If the update is downloaded as a single file to /cache, which is named the same as the file you can manually grab, then someone who hasn't gotten 6.2.2 (and is not averse to this failing) can try this in a root shell:
mkdir /cache/update-kindle-6.2.2_D01E_3205220.bin
mkdir /cache/update-kindle-6.2.2_D01E_3205220.bin/blah
The purpose here is to put something unremovable in the way of the file it wants to download. Most likely if the update sees something with the existing name there it would probably want to blow it away (after determining it's incomplete) - and since any update there would normally be a regular file, they probably would do nothing more complicated than a simple unlink syscall to delete it before re-downloading. However, since it's a directory with something in it, that unlink will fail. In actuality, making the subdirectory (second command above) should be unnecessary because the unlink should not work for directories; there's a special rmdir syscall for them.
btw. there are a lot of threads about this from the 6.2.1 update
make a short search for "prevent ota update" - you'll have a lot to read ...
Click to expand...
Click to collapse
I did read a lot of that last time and I don't think I actually saw a definitively successful method. If there is one it should be stickied
My interest in this is a little different from most of you guys - I have very limited satellite internet and I don't like these unscheduled 185-meg downloads so I want to be able to update only when I want mostly to control that. This kind of means looking for the least-intrusive way to accomplish this.

/cache/update-kindle-6.2.2_D01E_3205220.bin is exactly where it downloads
if you find a way to even prevent the download, that would be greatly appreciated

Unfortunately I already got the update so I can't try it this time.

at least you could try your method with a dummy file of an other name and try to overwrite it with adb - if you can't overwrite it there's a good chance

I think I'm about the only one who prevented 6.2.1. I did it by constantly checking the cache folder. Found the update by chance and deleted it before it updated. Waited over a week for it to come back. Never did. An app that watched the cache folder for the updates and then moved/deleted them would work fine
Sent from my SGH-I897 using xda premium

jcase already work a way around this automatic OTA update, so when FIREMOD is ready to replace burrito I think we will have no more problem with this OTA issue. (you can find jcase announcement in the kindle developer section)

Heres what I have done to prevent this.
1) Droidwall (white list only the apps you want to allow internet access)
2) Removed "otacerts.zip" from /system/etc/security/otacerts.zip.
3) I removed "OTASilentInstall.apk" /system/app
4) Installed this 6.2.2 based Rom http://forum.xda-developers.com/showthread.php?t=1439916
Hopefully this eliminates the OTA. I had my Fire rooted on 6.2.1 with twrp and it OTA'd on its own, broke root and twrp. So I rerooted with burritoroot2 and installed CWM based recovery.

[ROOT] Stock ICS Leak One-Click Root Tool

Hi all!
First off, I'm new to xda Developers so please excuse me if this is in the wrong forum! I thought I'd post information about a tool I wrote here which roots stock 4.0.3 leak on the A500, A501 and assumingly the A200 too. Its literally one click - just enable USB debugging. "ICS Root" also installs, optionally, FaceLock and Trebuchet (although FaceLock doesn't want to work. It lets you set it up though =P)
Since version 5.0.1 this also now works with the new 0.022.00 leak!
The full post is over at TegraOwners: http://forum.tegraowners.com/viewtopic.php?f=30&t=350
The only real system requirements are Windows (with .Net Framework 4) and an Iconia on the stock 4.0.3 leak. I hope somebody finds this useful its been tested by myself and a couple of TegraOwners users and it works well.
In terms of the technique used, it uses the great Jay Freeman's mempodroid exploit to gain root at which point it mounts /system rw and installs su, busybox and Superuser.apk so no real surprises there. Installing Trebuchet adds that apk to /system/app and installing FaceLock installs the apk to /system/app before installing the pittpatt folder to the flexrom (mounted as /system/vendor). I plan to open source it when all the requested features have been implemented and the code has been cleaned up.
Thanks!
~blackthund3r
EDIT 14/05/2012: ICS Root 7 is out enjoy!
Sent from my A500 using Tapatalk

cwm version?
why would it not work with cwm version?

With this tool does system remain writeable after rooting?

What about flashing CWM with acer recovery installer once rooted? I guess it would screw the bootloader...

lowsum said:
What about flashing CWM with acer recovery installer once rooted? I guess it would screw the bootloader...
Click to expand...
Click to collapse
If you are on the cwm with the HC boot loader it should work as Its Magic will be run..
if you are on the new boot loader as in the full non modded leak.. It will give you secure boot error ..
The new boot loader Blocks its magic.

Thanks
Hey this worked easy. I had to re-install USB drivers and make sure I had the latest from Google. Other then that, hit the button, wait about 1.5 minutes, and it rebooted! No problems thus far! Thanks Again!

JeanBubu said:
why would it not work with cwm version?
Click to expand...
Click to collapse
It would but the cwm one, afaik, is prerooted?
Sent from my A500 using Tapatalk

root doesnt work like its supposed to. i know its only half root due to the bootloader, but terminal emulator flat out says i'm not rooted after this despite sixasis working and titanium backup/root checker both saying i have root and busybox. i'm going to post this on TO as well for you incase you dont check here often.

nifterific said:
root doesnt work like its supposed to. i know its only half root due to the bootloader, but terminal emulator flat out says i'm not rooted after this despite sixasis working and titanium backup/root checker both saying i have root and busybox. i'm going to post this on TO as well for you incase you dont check here often.
Click to expand...
Click to collapse
That's storage cos terminal works for me and running su in an adb shell works great too.
Code:
[email protected]:/ $ export PATH=/data/local/bin:$PATH
[email protected]:/ $ su
# exit
[email protected]:/ $ su
#
Sent from my A500 using Tapatalk

SteamBishop said:
Hey this worked easy. I had to re-install USB drivers and make sure I had the latest from Google. Other then that, hit the button, wait about 1.5 minutes, and it rebooted! No problems thus far! Thanks Again!
Click to expand...
Click to collapse
You're welcome and I'm glad it worked!
Sent from my A500 using Tapatalk

After reading the other post, I have found that I cannot write to the system directory from the device itself. The folder attributes indicate that it is set to write, however File Explorer HD will not let me. I have tried to create a folder in the /system and it will not accept the addition. The strange thing is that Root Check says it is rooted, File Explorer HD accepts putting it into Root Explore, but that is it. It is odd. I will try to reapply the Root to see if that makes a difference.

SteamBishop said:
After reading the other post, I have found that I cannot write to the system directory from the device itself. The folder attributes indicate that it is set to write, however File Explorer HD will not let me. I have tried to create a folder in the /system and it will not accept the addition. The strange thing is that Root Check says it is rooted, File Explorer HD accepts putting it into Root Explore, but that is it. It is odd. I will try to reapply the Root to see if that makes a difference.
Click to expand...
Click to collapse
Please, read the op before bringing this up. This method is for half root, its the only way possible right now on stock leak ics. There is a special script you need to use to mpunt system. You can find it in the stock leak thread, run it in terminal or use rom toolbox and set it as a script to run at boot because rebooting loses write privileges.

nifterific said:
Please, read the op before bringing this up. This method is for half root, its the only way possible right now on stock leak ics. There is a special script you need to use to mpunt system. You can find it in the stock leak thread, run it in terminal or use rom toolbox and set it as a script to run at boot because rebooting loses write privileges.
Click to expand...
Click to collapse
Sorry for offending you and whoever else it did. Thank you for pointing that script out in that post. My intent was to offer a second comment to your assessment..

nifterific said:
Please, read the op before bringing this up. This method is for half root, its the only way possible right now on stock leak ics. There is a special script you need to use to mpunt system. You can find it in the stock leak thread, run it in terminal or use rom toolbox and set it as a script to run at boot because rebooting loses write privileges.
Click to expand...
Click to collapse
I have a better script which I'll be releasing as an update to the root app this morning hopefully. It'll be a terminal command to remount rw.
Sent from my A500 using Tapatalk

New update out!!
blackthund3r said:
I have a better script which I'll be releasing as an update to the root app this morning hopefully. It'll be a terminal command to remount rw.
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
Version 3 came out this morning
It features some bug fixes as well as a completely new remount menu which mounts /system rw properly on the fly. Tested with a busybox installer app
Enjoy!

Thanks for your tool blackthund3r !
I tried it with the new leak from this morning and it doesn't seem to work anymore
Edit :
Just to be a little more specific, the app says the process was OK and state that the tablet is rooted but the tablet doesn't reboot by itseld and su is not installed. I tried to install su manually but it's unable to find a previous su package on the system.

paugustin said:
Thanks for your tool blackthund3r !
I tried it with the new leak from this morning and it doesn't seem to work anymore
Edit :
Just to be a little more specific, the app says the process was OK and state that the tablet is rooted but the tablet doesn't reboot by itseld and su is not installed. I tried to install su manually but it's unable to find a previous su package on the system.
Click to expand...
Click to collapse
ah okay it appears a completely new leak has been released. It is possible that the mempodroid exploit has been patched up. I'm gonna look into it soon. I can't much tonight - I have school work. I'll see what can be done and what the differences between leaks are.
Sent from my A500 using Tapatalk
EDIT: mempodroid hasn't been patched See ICS Root v3.1

Hi blackthund3r
Thanks for the update 3.1 but could you please fix the problem on your hosting website? clicking on this file send to an error warning.
The other files can be downloaded though.

can someone post a mirror to the 3.1 version? current link is not working.
can somebody also confirm, if i root with this tool, i will be able to reinstall my clockworkmod recovery through 'acer recovery installer' and flash any other cwm rom? or do i have to downgrade to honeycomb 3.01, install iconiaroot for honeycomb and then acer recovery installer?

Gersma,
I'll be able to answer to your question as soon as I'll be able to download this tool and test it.