[Q] Push using adb fail (no room) - myTouch 3G, Magic General

Hey guys. I'm trying to push a libwebcore.so file from one .zip onto my current MyTouch phone that has CM 6 on it. The reason why I'm doing this is to have the Arabic browser support. This file causes the letters to be connected which they are in text messages, but not the browser. I heard pushing the libwebcore.so from a downloaded source (or from a rom .zip that has it from another rom) will do the trick.
However, everytime I try to push it to /system/lib it gives me an error saying that there is no room on the device. That's pretty unprobable since I'm sure I have a lot of space. How do I fix this and sucessfully push the file?

Shadowafs8 said:
Hey guys. I'm trying to push a libwebcore.so file from one .zip onto my current MyTouch phone that has CM 6 on it. The reason why I'm doing this is to have the Arabic browser support. This file causes the letters to be connected which they are in text messages, but not the browser. I heard pushing the libwebcore.so from a downloaded source (or from a rom .zip that has it from another rom) will do the trick.
However, everytime I try to push it to /system/lib it gives me an error saying that there is no room on the device. That's pretty unprobable since I'm sure I have a lot of space. How do I fix this and sucessfully push the file?
Click to expand...
Click to collapse
Do "adb shell df -h" to see how much room is available in your system partition. You may have to remove some unused system apps to make room.

I'm trying that now...but is it safe to delete the current libwebcore.so now and add the new one? If so what's the command. Also, if the libwebcore.so was for a testing version of CM 6 (specifically RC3), will it still work?

Also, is there a way to take some space from other parts of the system?

First of all, i'm going to move this to General since I fail to see how this is regarding the Development of anything. Some good information, but not related to Development.
Secondly, have you considered performing a nandroid backup, booting to recovery, mount the /system directory, then 'adb shell rm /system/lib/webcore.so' to remove your file then 'adb push webcore.so /system/lib'
Also, if you use the file directly from SOURCE it may not work since it may need to be compiled first. I'm not sure about that though since I've never tried it.
If any of the above goes wrong you can always nandroid restore and try again.
I personally use Clockwork Recovery since you can restore specific partitions individually (such as System) so it saves time.
Good luck.

I'm pretty much done trying...unless somebody can comply the file for me and test it. I'm really done trying this when all it does is fail over and over again. Hopefully somebody can come up with something

Related

[SOLVED] How to Delete System Apps after Loosing Root Access From 1.72.405.3 ROM

Ok so after much lots of frustration realising I'd lost access to the delete system apps after installing HTC 1.72.405.3 (in LeeDrOiD 1.3) I've finally figured out a way to do it and without needing to use ROM Cleaner then re-flash a ROM wich would remove all my data/apps/ect I've loaded. Now this may well be a guide for you guys like me who are very new to Unix commands and the whole Android system. I hope that it helps someone coz honestly the last couple of days I've searched high and low and haven't gotten any answers that worked until I worked it out tonight.
Just as a quick note I was able to delete apps from the /system/app folder before this update when I was still on 1.32.405.6 using Visionary+ in loading R/W access to the system folder on boot and a simple file manager like Astro or AndroZip to delete. Since updating to 1.72.405.3 without Radio S-Off I've tried the following methods and found they don't work:
- Flashing rmk40's Super User/Root patch for 1.72.405.3 as in this thread http://forum.xda-developers.com/showthread.php?t=886999
- Visionary+ selecting R/W system access then using a file manager like Astro or AndroZip to delete.
- Terminal Emulator after getting "supposed" super user access after typing su then going to the /system/data folder and typing rm Facebook.apk ect... also using the other unix commands to try and change the system apps from read only to writable still no access.
- Using Root Explorer which is granted "supposed" super user access does not want to mount as R/W the system/app folder and of course then won't let me delete the apps.
- One click Radio S-Off doens't work as obviously I'm already locked out as I've loaded 1.72.405.3 (LeeDrOiD 1.3) before running Radio S-Off.
- Re-flashing to a previous 1.32.405 ROM then trying to run Radio S-Off followed by all the steps above. Nope nuthin...
Okay and here is is here's how it's done. I had to have the Android SDK installed with USB drivers (HTC Sync has the USB Drivers). I then in windows I opened up command prompt and using the good old DOS commands like "cd\program files (x64)" I go to my android sdk folder platform-tools. Once in the platform-tools let the foreign Unix commands begin
Without the exclamation marks type I type "adb remount shell"
Then "adb shell rm /system/app/Facebook.apk"
Now Facebook.apk being an example of the app you want to delete. I use a file browser such as Astro on my phone to go the the /system/app folder and easily look around and get the file names of the apps I want to delete. An important thing to remember for all the other's unfamiliar with Unix commands like myself, this ain't DOS. Unlike DOS, files and commands are case sensitive so if you try to delete the Facebook app and type it in "facebook.apk" all lower case it won't delete. Make note of any letters uppercase or lowercase in the folder name and file and type it in correctly in the Unix commands or they won't work.
The other two important things to note before you go on a Spring cleaning, delete frenzy (like I will be after I finish typing this up ) is: 1) If you delete some certain system apps (for example TelephonyProvider.apk) Android will **** itself and after booting enter a loop where you can't access anything & you can't stop it complaining about blah blah app failed. So make sure you have on your microSD card either a Nandroid backup done recently using the Backp/Restore function under the Bootloader installed with Clockwork Recovery or a working ROM that you've tried and know works such as the stock ROM or a custom ROM from LeeDrOiD, Cyanogen, ect. If you get into one of those non recoverable loops you'll need to flash the ROM and of course loose any data and apps not backed up. Okay this brings me to my next point. 2) If you want to copy any of the system apps off to your microSD card either to backup or just if you're not 100% sure if you may want to install it again later then in command prompt type this:
"adb shell cp /system/app/Calculator.apk /sdcard/"
Obviously here Calculator.apk is the app we are copying but you can choose any app to copy. Also /sdcard/ means it will go to the root folder of your MicroSD card.
Stick it to tha man and have fun cleaning up your ROM and deleting all that crap bloatware your service provider and HTC don't wanna give you access to and now without the cripple of HTC update 1.72.405.3 stopping you!
Are these persistent changes? If so I think you will be the saviour of many on here!
Are you sure the apps are not back when you reboot your phone?
I'd be pretty surprised if they're persistent.
sorry i can't see how this has worked. unless by some weird chance when trying to get s-off, gain root and what esle you have try to do. has caused you to be able to r/w to the system partition.
cattleprod sorry i can't see how this has worked. unless by some weird chance when trying to get s-off, gain root and what esle you have try to do. has caused you to be able to r/w to the system partition.
Click to expand...
Click to collapse
Ok I assure you it has worked and continues to work. One possible major difference I've just been told supposedly the stock HTC RUU 1.72.405.3 reverts you back to original hboot eng s-on. Me on the other hand I never loaded a stock HTC ROM 1.72.405.3 or an update. I loaded LeeDroiD 1.3 which has in it the base as 1.72.405.3 but also his modifications to that. So never lost clockwork recovery hboot. I can still load ROMs fine, I just lost functionallity from Visionary+ or anything else for that matter on the phone to access System folder R/W access. Using ADB on my PC as described above however did solve this. Unfortunately the other issue is after loading LeeDroid 1.3 it's permanently done something to my phone and even after flashing back to previous stock 1.32ROM the 1click Radio S-Off patch does absolutely nothing. Luckily Vodafone supposedly offers a free SIM unlock and there are also cheap alternatives on ebay.
dr.m0x I'd be pretty surprised if they're persistent.
Click to expand...
Click to collapse
Eddie1506 Are you sure the apps are not back when you reboot your phone?
Click to expand...
Click to collapse
andyharney Are these persistent changes? If so I think you will be the saviour of many on here!
Click to expand...
Click to collapse
Yes guys these are all persistant. I've rebooted quite a few times and none of the apps I've deleted have come back. These are the apps I've deleted from the "/system/app" folder and they 4 sure have not come back to annoy me: Facebook (crackbook as I like to say ), Twitter & Flickr including any widgets of the same name, stock or shares trading apps, default internet browser (replaced it with Dolphin HD), Flashlight (replaced it with moddified HTC one that says "torch" as I'm not a fan of US English), HTC Likes, HTC coin, probably some others I can't remember now.
So anyway go for it just use your clockwork recovery (modified hboot) to do a full backup first as if you remove the wrong system apps it goes in a non working error loop.
I'm only real new to the whole Android thing. Only had the phone 4 bout 2 weeks and never hit up any Unix commands before then. I'm happy to help out if I can though. Just message me and when I'm on next I'll try to help.

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.

Asus programs on modded tablet, and some CM9 questions

Hi All,
I set out to flash my tablet back to stock with the goal of copying some of the awesome asus-specific widgets and applications and installing them back on my tablet after I re-rooted/modded it. I accomplished part of this goal by finding some of the .apk's I wanted, like the Asus weather & battery widgets, the Supernote.apk, anda few others (I still wasn't able to find the Swype Keyboard.apk file)
Anywho, I tried to install the .apk's on my tablet after re-installing cm9 and rooting it but it just says "Application not installed". Anyone have any ideas? And can anyone elaborate on how to copy that swype keyboard APK that I desperately want? I found the other .apk's in the /system/app folder but swype wasn't there.
My other questions relate to CM9:
1) is there any way to decrease the boot time for CM9, or at least customize the boot screen?
2) I'm currently running an older version of cm9 (rc0 unofficial) and I have the stable rc1 of cm9 but when i tried to flash it, it didn't work (i can get the exact error message if needed). Did I do something wrong in updating or is RC1 not compatible with the device? Should I just wait till CM10 comes out?
3) When I initially rooted/flashed cm9, I was able to connect my tablet to my computer and the root of the / directory, but after flashing stock and trying again, I don't have the same luck. Is there some step I missed?
I appreciate any responses, thanks.
- Opethfan89
3 days, 300 views, no responses. BUMP anyone?
opethfan89 said:
Hi All,
I set out to flash my tablet back to stock with the goal of copying some of the awesome asus-specific widgets and applications and installing them back on my tablet after I re-rooted/modded it. I accomplished part of this goal by finding some of the .apk's I wanted, like the Asus weather & battery widgets, the Supernote.apk, anda few others (I still wasn't able to find the Swype Keyboard.apk file)
Anywho, I tried to install the .apk's on my tablet after re-installing cm9 and rooting it but it just says "Application not installed". Anyone have any ideas? And can anyone elaborate on how to copy that swype keyboard APK that I desperately want? I found the other .apk's in the /system/app folder but swype wasn't there.
My other questions relate to CM9:
1) is there any way to decrease the boot time for CM9, or at least customize the boot screen?
2) I'm currently running an older version of cm9 (rc0 unofficial) and I have the stable rc1 of cm9 but when i tried to flash it, it didn't work (i can get the exact error message if needed). Did I do something wrong in updating or is RC1 not compatible with the device? Should I just wait till CM10 comes out?
3) When I initially rooted/flashed cm9, I was able to connect my tablet to my computer and the root of the / directory, but after flashing stock and trying again, I don't have the same luck. Is there some step I missed?
I appreciate any responses, thanks.
- Opethfan89
Click to expand...
Click to collapse
I haven't tried this, but it may work. If you have ADB on your computer, try doing an adb push [name of file].apk /system/app/
If you can't do that, try copy/pasting them there using a root explorer on your device itself. Make sure the permissions are set properly (I don't remember what they are off the top of my head).
After doing that, reboot. See if it works.
As for your CM Questions:
1) I'm not sure if you can reduce the time. For customizing the animation, look at something like Rom Toolbox Pro (which also includes a root explorer like I mentioned above).
2) All CM9 TF300T downloads are located here: http://get.cm/?device=tf300t RC1 is listed there so I'm assuming you did something wrong (what's the error you get?)
3) Did you re-root? I'm not sure I understand.
Link9228 said:
I haven't tried this, but it may work. If you have ADB on your computer, try doing an adb push [name of file].apk /system/app/
If you can't do that, try copy/pasting them there using a root explorer on your device itself. Make sure the permissions are set properly (I don't remember what they are off the top of my head).
After doing that, reboot. See if it works.
As for your CM Questions:
1) I'm not sure if you can reduce the time. For customizing the animation, look at something like Rom Toolbox Pro (which also includes a root explorer like I mentioned above).
2) All CM9 TF300T downloads are located here: http://get.cm/?device=tf300t RC1 is listed there so I'm assuming you did something wrong (what's the error you get?)
3) Did you re-root? I'm not sure I understand.
Click to expand...
Click to collapse
I apologize for the vagueness of my original post. I made this thread in anticipation of flashing everything back to stock, trying to copy over those Asus-specific .apk's (which I managed to do), and then re-rooting/re-flashing CM9.
I flashed the .30 firmware to get back to stock and found the Asus widgets & apk's I was looking for in the /system/app directory. After some bootloops and other fun, I was able to flash back to CM9 and when I tried to install the .apk's I immediately get the message "The Application was not installed"
Of the asus items I wanted, Supernote and Polaris Office were my top two picks, and I was able to acquire Supernote through 3-rd party means and install it. So I'm stoked to have Supernote on a CM9-flashed tablet. I wasn't able to find Polaris Office so I hope to at least be able to find a work-around to install that.
In response to #3 - yes I re-rooted my tablet (lost root with the .30 firmware) and previously I was able to browse the root directory of my tablet while it was connected to my computer. Now, I can only browse the SD card. I still haven't figured out a solution to this, but I just transfer files to my memory card and then to my tablet from there. I'm looking into how to do OTA file transfers via bluetooth or wi-fi, if at all possible.
opethfan89 said:
I apologize for the vagueness of my original post. I made this thread in anticipation of flashing everything back to stock, trying to copy over those Asus-specific .apk's (which I managed to do), and then re-rooting/re-flashing CM9.
I flashed the .30 firmware to get back to stock and found the Asus widgets & apk's I was looking for in the /system/app directory. After some bootloops and other fun, I was able to flash back to CM9 and when I tried to install the .apk's I immediately get the message "The Application was not installed"
Of the asus items I wanted, Supernote and Polaris Office were my top two picks, and I was able to acquire Supernote through 3-rd party means and install it. So I'm stoked to have Supernote on a CM9-flashed tablet. I wasn't able to find Polaris Office so I hope to at least be able to find a work-around to install that.
In response to #3 - yes I re-rooted my tablet (lost root with the .30 firmware) and previously I was able to browse the root directory of my tablet while it was connected to my computer. Now, I can only browse the SD card. I still haven't figured out a solution to this, but I just transfer files to my memory card and then to my tablet from there. I'm looking into how to do OTA file transfers via bluetooth or wi-fi, if at all possible.
Click to expand...
Click to collapse
So did you try what I suggested in my post (pushing the files to /system/app on your tablet, rather than trying to install them through File Browser or whatever)?
I'm not sure if they rely on any custom Asus framework stuffs, like with many other OEMs. I personally doubt it because Asus barely changes anything. I think it *should* work, but can't guarantee it.
The easiest way to get the files to /system/app (if you're not very ADB or tech. savvy) is to download a root explorer (like Rom Toolbox Pro has, for example) and copy all the .apks that you want from your sdcard to /system/app.
Link9228 said:
So did you try what I suggested in my post (pushing the files to /system/app on your tablet, rather than trying to install them through File Browser or whatever)?
I'm not sure if they rely on any custom Asus framework stuffs, like with many other OEMs. I personally doubt it because Asus barely changes anything. I think it *should* work, but can't guarantee it.
The easiest way to get the files to /system/app (if you're not very ADB or tech. savvy) is to download a root explorer (like Rom Toolbox Pro has, for example) and copy all the .apks that you want from your sdcard to /system/app.
Click to expand...
Click to collapse
I haven't tried pushing the files via ADB yet. I just wiped out my computer so I need to re-install the drivers to get the tablet recognized and/or the the Android SDK.
In the 3rd point of your point, do you mean my external SD card or the internal memory?
the Transformer Pad has a good portion of internal memory partitioned as an sdcard and mounts it at /sdcard/. I haven't used an external SD card with my tablet yet. Either one should work.
I also found out that Polaris Office has some library files that you probably should grab as well. You can find them at:
/system/lib/libpolarisoffice_tablet.so
/system/lib/libpolarisofficedump.so
/system/lib/libtfapps-polaris.so
/system/lib/libtflua-polaris.so
Click to expand...
Click to collapse
There might be some library files for the other apps. You might want to look around in the /system/lib folder for other libraries as well.
Link9228 said:
the Transformer Pad has a good portion of internal memory partitioned as an sdcard and mounts it at /sdcard/. I haven't used an external SD card with my tablet yet. Either one should work.
I also found out that Polaris Office has some library files that you probably should grab as well. You can find them at:
There might be some library files for the other apps. You might want to look around in the /system/lib folder for other libraries as well.
Click to expand...
Click to collapse
That's awesome, thanks. If I'm able to get this working I will post a guide for others to follow. I ended up just signing up for the swype beta (which I think is stupid since I paid for that app when I bought my tablet, shouldn't have to get a reduced version)
I was able to find a working supernote.apk app on a 3rd-party website and it installed and worked perfectly.
My other issue I'm having is I try to push the files with ADB and it tells me my tablet is read-only? it gives that same message no matter which directory I try to push to. I have the superuser app and have root, but superusers' log shows the 'adb shell' is consistently being denied root permission (if i try to do su or something similar). Any thoughts?
opethfan89 said:
That's awesome, thanks. If I'm able to get this working I will post a guide for others to follow. I ended up just signing up for the swype beta (which I think is stupid since I paid for that app when I bought my tablet, shouldn't have to get a reduced version)
I was able to find a working supernote.apk app on a 3rd-party website and it installed and worked perfectly.
My other issue I'm having is I try to push the files with ADB and it tells me my tablet is read-only? it gives that same message no matter which directory I try to push to. I have the superuser app and have root, but superusers' log shows the 'adb shell' is consistently being denied root permission (if i try to do su or something similar). Any thoughts?
Click to expand...
Click to collapse
You need to remount your system as read-write. Trying doing an adb remount. If that doesn't work, try typing the following into a terminal emulator:
su
busybox mount -o remount,rw /system
Click to expand...
Click to collapse
Try ADB pushing again after that.
if you are able to install the apps by adb push. then maybe a .zip file can be created and use CWM to install all the stock apps.
Link9228 said:
You need to remount your system as read-write. Trying doing an adb remount. If that doesn't work, try typing the following into a terminal emulator:
Try ADB pushing again after that.
Click to expand...
Click to collapse
Well part of the issue is that I can't "su" while in adb shell. It says permission denied. When I type ADB devices normally, it'll list my device. But when I'm in "adb shell" it doesn't show anything. "adb remount" gives me the message "error: device not found".
Any other suggestions?
opethfan89 said:
Well part of the issue is that I can't "su" while in adb shell. It says permission denied. When I type ADB devices normally, it'll list my device. But when I'm in "adb shell" it doesn't show anything. "adb remount" gives me the message "error: device not found".
Any other suggestions?
Click to expand...
Click to collapse
That's weird. I've never seen that before. Are you certain that your adb drivers are installed properly? You can always use a terminal emulator on your device itself to remount the system as read/write and then use adb afterwards.
Link9228 said:
That's weird. I've never seen that before. Are you certain that your adb drivers are installed properly? You can always use a terminal emulator on your device itself to remount the system as read/write and then use adb afterwards.
Click to expand...
Click to collapse
I'm pretty sure my drivers are installed correctly. Everything shows up in device manager, "adb devices" lists my device, fastboot flashes files just fine, so yea.
And yea I have the terminal emulator on my tablet and I've used it before for some stuff (installing Ubuntu) so I will try the steps you guys have mentioned. I'm in the process of trying out some other ROM's right now (Hydro atm, and then probably CleanROM) so once I go back to stock and have access to the appropriate files I'll try these steps.

No write permission on pushed+ overwritten sdcard directories?

So I have something pretty strange going on.
I had a replacement device sent to me, and I decided to wholesale transfer the contents of the original device's sdcard to the new N7.
I adb pulled and then pushed the entire /sdcard/ over to the brand new device, which I did in recovery directly after rooting. I only installed the OTA first.
Now however, the pushed folders have incorrect permissions, and I can't find anyway to modify their contents. That means I can't delete, no files will go to the Download folder, all that stuff. The only work-around I have found is I can rename those folders,e.g. Download -> Download_old, thereby getting Chrome and Dropbox to now use a new Download folder with write permission, allowing them to work.
But I pushed over 7 gigs of stuff, and now it is permanent, which isn't really an option. When I finish those books, I want to delete them. When I am done with GTA3, I would like those files gone, and so forth.
Attempts to fix permissions, mount through ADB shell, those things haven't worked. When I open a shell and attempt to change permissions with chmod, the command goes through but the permissions do not change. This has been attempted as root. The files aren't corrupted, at least not in the sense that I can play games with the game files, read the .pdf's and so forth.
Any advice? I guess I could reflash the stock image, but I would rather not go through getting those files on again, especially if the only way to have managable permissions is to not overwrite, but to push each folder's contents individually. I of course will do this if no one has any thoughts, but I figured it could benefit others to commit this to posterity.
I have actually found a couple people with this problem, but after recieving advice similar to the steps I outline above, they disappear with no solution i could find.
Any ideas?
Update: Well, it has been 8-9 hours, and this post is already pushed to the bottom of page 3 in the forum queue, with 17 views. Gotta love these outreach devices. 8 milliom people asking questions and nobody answering them, lol.
Well, I am just going to reflash the stock image instead of giving this an artificial bump and waiting longer. You would be suprised how many things don't work without write to sd privileges, especially on a device with no emmc or removable storage. I have been playing with it for awhile, but like I said, I can't even remove files after su, so you know that something is serious. When superuser rights fail, you're in trouble.
For those imaginary future researchers, sorry no non-destructive solutions here. But if you want to send me a fellowship, I can share screenshots of the carnage.
i have exactly the same problem.
flashed new rom and wiped the device.
wanted to restore all my pictures and files.
restore went well...but could not write to the folders or delete them.
rename was the only possible thing. did not find a solution either. just hat to wipe.
won't push anything on the device via adb.
next time i'll do it the simple GUI way!

Categories

Resources