Believe it or not, this netbook comes already rooted, but how to access it is hidden. The original adventure is posted below if you're interested,but I'll put the tl;dr up top.
You'll need to side load the app USB Debug by tatibana. This will shortcut to the hidden developer options. Slide the developer options on. You may or may not need to reboot, I was too focused on USB Debug to notice the SuperUser Options... The default is Always Deny. Set to Always Allow, then you can replace with your choice su manager (I installed Chainfire's SuperSU).
That's it. The rest below is my original posts up to this point, including getting a Linux working prior to figuring out root. Enjoy the read.
Edit 2: You can pick up new posts from this point by going directly to post #11.
Original Post:
---
Okay, this one is a bit puzzling and I haven't found any good info in searches. This is an Android netbook with Jellybean. Pointer control is a single point touch pad which makes zooming out on several apps impossible; I wish to attain root so I can install desktop Linux in parallel and use some desktop apps in place of some Android apps. I know I could use something like qemu but I'd rather install root and use arm binaries than take a performance hit using non-root methods.
This netbook comes with an installed su binary and busybox 1.19.4 but trying to invoke su results in
su: uid 10084 not allowed to su
Settings is also a bit crippled; no Developer Options section means no option to invoke USB Debugging. Anyone have any good ideas?
---
Sent from my C5155 using XDA Free mobile app
addendum
There also is no physical volume or photo buttons, and no obvious way to get into fastboot mode. My guess is that the original OS image was made in root mode, then the CV dev created a default user with almost no permissions, then backed it out effectively locking it out of root forever. I have also discovered that the busybox doesn't have access to the network as this user 10084, negating half its usability. No Play Store either (using Amazon instead), though I can (and have) install to my phone and copy to this if necessary.
This has a cool little form factor and I think has so much potential for a cheap device if I could just bust this major barrier. Does anyone know any sh or setuid tricks that might fake this thing into a root mode, or at least manage to give me enough permissions to edit /system files?
system seems to be owned by user 1003 and group 120, if that helps.
---
Mmmmmm, tasty foot...
So apparently this is normal behavior for the stock android su (see guys, I'm learning >P ); only the user shell (and root) can use su. This thing using a shared uid for apps might or might not have an effect, don't know yet. The normal way around it is to adb shell and su in, then overwrite with a custom su binary such as ChainsDD. I don't know if I have that option since there's no USB Debugging option, and I'm too tired to find out tonight. I will update this adventure later.
USB failed, but not anything to do with adb, didn't even get that far. The netbook failed to even register to the desktop (Linux)... lsusb didn't show anything. I don't know if it's a cable thing (tried direct A-A patch and the MiniUSB charge port- charge port predictably didn't support data and neither standard port showed any reaction) or a hardware limitation.
I also took a crack at adb over wifi but as usual it was the catch 22 of needing root to invoke adbd into tcpip to attain root.
Still open to suggestions... please?
---
Sent from my C5155 using XDA Free mobile app
Developer Options?
This is driving me up a new wall. Based on what I have been reading all day, Developer Options are a core function and cannot be removed, only hidden. This thing has not been giving me much confidence in that statement, however. I have been through the settings over and over again with a fine tooth comb and the whole thing eludes me.
This is Android 4.1.1. The 4.2+ trick (7 clicks on Build Number) doesn't work, and it's not in the App settings either, nor is there any sections renamed "Advanced" or the like. It may not be an end-all but I feel it would at least be a step in the right direction. I might be able to use an exploit such as Poot or Framearoot, which are currently ineffective.
I also haven't had any luck with getting into a recovery boot mode, not sure it's possible with this keyboard (I suspect it's soft driven; inactive until the kernel and modules are loaded). This seems to be just one shut down after another. I need more ideas, pointers, whatever. Don't forget, it can also help the next sap stuck with this model...
I decided to not lose sight of my original reasoning and move forward anyway with an app that claims to install Linux without root. I installed Gnuroot Wheezy which taught me some more f'd up things about this netbook but it at least in concept is working. What more things I have learned...
One of the issues with running Linux without root is the inability to use the external SD-card, at least native, because you can't mount an external partition/file that hasn't already been set up in the mount scripts outside of userspace. Gnuroot uses a chroot off the secure asec in /data. With about 3G user space available on this netbook, you'd think that wouldn't be a problem... but it is, because of another setup issue with this netbook...
See, while the external SD card does mount to /sdcard,/mnt/sdcard, that is NOT where Android app setup calls SDcard... there is a so called internal SDcard that is really a fake vfat via fuse mount off /data mounted to /mnt/local. This means it does no good to move my plethora of other apps to the "SD Card," actually, it makes the problem worse on this device. I imagine it was done so you could swap SD cards without affecting your apps, good move for flexibility but poor for expandability.
For those who would try it, that's also a big hint for getting it working. This device does not have access to the Play market*, so you will have to move helper apps from another Android device over. Don't bother with 3rd party repositories, you will not get everything you need. The biggest issue is the WheezyX obb file. It on install ONLY from the Play store will be located in /sdcard/Android/obb/champion.gnuroot.wheezyx/main.2.champion.gnuroot.wheezyx.obb , on this netbook the file must be moved to /mnt/local/Android/obb/champion.gnuroot.wheezyx or it will not be recognized, and because of the play store issue, can't be downloaded and gnuroot will exit with error.
Anyway, so now WheezyX is actually running and I am attempting to install an Openbox/LXDE desktop... the problem I am hitting now is the space limitation... It said it needed about 330 MB space and I had 360MB available on start... I'm now about 1/4 through and the netbook has come to a dead crawl due to... yep, very little space left (about 55 MB free on /data)... WTF! I feel like I am just not meant to win at like anything...
---
*Edit: Once rooted, the play store can be installed to the system partition and does work pretty good.
---
Sent from my C5155 using XDA Free mobile app
Some success with Linux
Well, it took quite a bit of monkeying and persistence but I do have desktop Linux running via the above described method. I found Synaptic was useful for finding packages but as the GNURoot author warned, for the love of all that's holy, use apt-get to actually install the packages. It seems trying to install a desktop environment via Synaptic totally overthrew the system. Also try installing only a few packages at a time and clean up after each one, especially where space is a premium.
What's left now is experimenting with vnc viewers a/o X11 environments. I'm presently using PocketCloud but it doesn't seem to like this keyboard (right shift = 6, no down arrow, Ctrl is sticky- forget combo keys; at least the included soft-keyboard does work, just a productivity killer) and getting a right mouse click is almost impossible, so I want to see if I can do better.
The environment is OpenBox with lxpanel and the background is set with qiv. I am confident now that providing space wasn't such an issue I could run pretty much any basic Linux program I want. I have not tested audio and I already know just being vncserver that motion video is a bad idea; this was mostly proof of concept until I can open up some space. I may now see how far I can take this (e.g. link large trees to the SD card, such as bin directories; since it's already running fake-root, I'm not too worried about user permissions. I may also experiment with fuse).
Edit:
This does not mean I don't still want to get a true root. If nothing else, even if I can't take Linux off the internal storage, root will allow me to force Android apps on to the external SD; either solves the current space issue and thus is still desirable. I'm just not as stuck in the mud now. Ideas still very much appreciated.
Done and done.
Just a quick update to say the project isn't dead, just dormant. I have successfully turned on USB debugging thanks to a shortcut app called "USB Debug" by Tatibana. Thank you
---
Sent from my C5155 using XDA Free mobile app
Framaroot, Universal Androot, and Poot have all failed.
:banghead:
Have yet to see if physical USB will now work... I don't exactly live alone.
---
Sent from my C5155 using XDA Free mobile app
SUCCESS!!!!!
IDFBT! I must have not been paying enough attention before or something, or maybe it was one of the half dozen greyed out options before... not sure, but after I was again unable to connect via direct USB, I decided to double check the developer options to make sure noting was reset by the last reboot.... and there in bright white last in the top section... Superuser Options (set to Always Deny)! I set it to Ask and tested, but it promptly rebooted as soon as I tried to su, and again on that boot, so I had to set to Always Allow. Amazon doesn't have SuperSU and last I knew ChainsDD Superuser is still adrift in the doldrums, so I'll have to sideload (as usual), but, I just wanted to share. This netbook does come rooted, you just need to turn on the hidden developer options, reboot, and go back and allow SuperUser.
Will report more as I progress. Banzai!!!
Adventures in Linux land
Well, I had mentioned before how space was an issue. Thanks in part to Link2SD, I managed to curb that problem.
Problem still though was my base graphical Linux install was taking 1G of my /data space. Since I made 2G available on the Link2SD ext4 (/data/sdext2) partition, I found I had about 1.3G available after moving most apps over, I decided I'd try a manual data move. I was slow with this since I didn't know how Link2SD or the system was going to handle it. That turned out to be a good thing.
When using Link2SD, one thing that should be obvious is to never move essential apps off the internal storage. These would be things like Link2SD itself, a Terminal emulator, and your superuser manager (e.g. SuperSU); basically, things you absolutely cannot lose access to even temporarily.
Okay, so, to test the behavior, I went into the emulator..
su
cd /data/sdext2
mkdir Linux
That's all. I then did a normal power off and restart. When rebooting, an "Android is Updating..." box came up and went away in a few seconds. The launcher came up and I waited for everything to load normally. Then I started getting a rash of "App is not installed" messages... uh oh. The only reason this turned out to not be a big deal is Link2SD and SuperSU were still on internal storage, and Link2SD is designed to deal with this problem. I simply launched Link2SD, clicked the tab bar on the upper left, and selected "Relink all application files," after which it requested a reboot, and I complied.
With a semi-disaster averted, I went back into /data/sdext2 to see if the Linux directory was still there. Hallelujah it was. Next was finding the GNURoot wheezyx root. This turned out to be fairly easy:
/data/data/champion.gnuroot/app_install/roots/wheezyx . I decided for potential future expansion to move the whole roots directory. Being cautious as I try, I do a copy.
su
cd /data/data/champion.gnuroot/app_install
cp -a roots /data/sdext2/Linux/
(... go make a sammich ...)
rm -R roots
(... go make and eat dinner ...)
ln -s /data/sdext2/Linux/roots roots
This appeared to work at first, until I tried to install something (abiword). I discovered that the permissions were not copied to the lib directories (android security quirk?). This would probably not be an issue if this were a true root install but being a fake root app install, it effectively prevented the installation of libraries. This was fixed simply by doing a chown and chmod on the lib directories.
Contined from above:
cd roots/wheezyx
chown 10102.10102 lib
chmod 771 lib
chown 10102.10102 usr/lib
chmod 771 usr/lib
*note: the app id number may be different on your copy. This will be fairly obvious with a simple ls -lh .
After that, the install completed and this thing is running pretty good. I am now considering this a complete success. While technically solved, I'll keep this thread open for questions or updates (for as long as the mods don't mind).
---
Sent from my C5155 using XDA Free mobile app
Screencap op
Assuming the uploads work this time, attached are some screencaps. Enjoy.
Related
Good Day Folks.
I'm a Noob in need of help and i'm hoping the more experienced among us might be able to assist. I have an issue with disappearing phone storage. Over the course of a week I realized that I was losing about 1MB a day. My phone would basically be dormant and I would still see my storage space dropping by this amount everyday.
Cache cleaning didn't work. Later I realized that Android creates a bunch of log files in Data/System/Dropbox that was responsible for the disappearing phone storage trick I've been seeing for a while now.
I know now that Google has incorporated into Android as of the 2.2 iteration, a DropBox Manager that's responsible for logging all of the events that take place during the course of a running Android session. Everything from what took place at boot to force close details.
I understand that this is used for debugging purposes but I'm no developer . So my question is.... Can this DropBox Manager be disabled....somehow.
I really don't need all these files (and its A LOT OF THEM) being created as they serve no practical purpose for me. Not sure if anyone else might have noticed this but I'm hoping to receive some help. Even if it means pointing me in the right direction so I can work on it myself.
I really don't have a clue on how to start. Any help will be appreciated....Seriously...
Currently using G1 with CM6 Magpie running on EZTERRY's 2.6.34.7 kernel.
Its perfect except for this annoying problem.......
Hm what happens if you rename the directory. It might throw some errors in the logger, but probably won't create anymore files.
I just deleted the content of my dropbox folder, the DropboxManagerService was throwing some errors that he could not open files, but the phone was fine, no FCs or anything.
Renaming the directory just results in a random reboot. My guess is that when Android tries to create a new log, its unable to find the directory and then it just freezes and after a while it reboots. Once restarted it just reappears... I've tried that too.
And its true.. Its ok to delete the files. Its what I do currently. All of those files in Data/System/Dropbox as well as the ones located in Data/Tombstones are ok to delete. As I said, its just used for debugging purposes. Whats really annoying though is that, no matter how many times you delete anything, they just get repopulated just as fast as they're deleted. I'm ok with micro-managing my memory and phone storage (its a G1 after all) but this is ridiculous. It just creates too many of these log files too quickly.
If there was a way to turn the DropBoxManager service off then that would be the end of it all.
What's unusual about it too is that in my particular case, the contents of these text files just have two things listed in them. Pertaining to my online accounts associated with the phone: My Google account and My Whatsapp account...
It just repeats the same thing over and over again. I'm starting to think that the event data might actually be synchronization data or at least synchronization attempts made at regular intervals. But ultimately i'm guessing....
I really don't have a clue... Have you ever heard of anything like this on XDA......possible resolutions of this issue?
epolaris said:
I really don't have a clue... Have you ever heard of anything like this on XDA......possible resolutions of this issue?
Click to expand...
Click to collapse
Not yet .
What about replacing the folder by a symlink to /dev/null ?
You could also try to change permission on the folder.
Ok... I'm a real Noob but I'll take a shot.. When you say symlink what do you mean.
I'm not really familiar with Android at that level yet its really just flashing and such.
But I know a symlink is really just a reference to a location that the OS would interpret and follow (like a pointer i think). So, is it that you're suggesting some sort of redirection where the Data/System/Dropbox directory is pointed to another arbitrary location. Kind of like a creating a dead link that Android is unable to follow up on. Or maybe, redirecting the folder to an entirely new location that Android would then follow. I'm not sure... How do you perform a symlink in Android... I'm willing to try.
You can do it with a console on the phone it self or using adb shell. You need root of course.
You could make a link to another location where you have more space?
Or you change to permissions of that directory to write only.
Or you can mount a different file system to that directory that is read only.
On how to do that just google a bit for linux tutorials on that topic.
I have just googled a bit and it seems you can't symlink directories to /dev/null.
If all that doesnt help post again, there might be an option to make an app delete the files automaticly, first time they get created.
If that would be an option too let me know, im in the mood to program something intresting .
Disabling Android 2.2 DropboxManager [RESOLVED]
I took your advice and did the research you suggested and it worked.
The first thing I tried was changing the permissions on the "Data/System/Dropbox" directory and it worked. But I didn't use CHMOD and console command line to do it.
I have a program called Root Explorer that allows me to permanently change the permissions on any file or folder I select. I set all of the offending folders to read only and the log files stopped being written to those folders.
These are the directories I set to read only:
1. "Data/System/Dropbox"
2. "Data/System/UsageStats"
3. "Data/Tombstones"
Since changing the permissions on these folders my phone storage has stopped dwindling out of control. No additional programming necessary
Disabling the DropBoxMangerService itself is not necessary which is good.
I'm going to take your advice and read up some more on Linux commands (specifically Ubuntu as its what I currently use).
You have been very helpful, thanks for the advice. If you have any ideas about Froyo ROMS (Maybe even Gingerbread ) I should try let me know.
Thanks again....
I have also found these files. They can take MUCH space in memory and nothing seems to delete them. I made the dropbox system folder RO but I think this is a bug. It should be reported to the dropbox team. Is there a bug report form somewhere? I did not find it... Just found the forum, QA,...
[edit]I reported it in the forum... Just see http://forums.dropbox.com/topic.php?id=41227 [/edit]
vax said:
I have also found these files. They can take MUCH space in memory and nothing seems to delete them. I made the dropbox system folder RO but I think this is a bug. It should be reported to the dropbox team. Is there a bug report form somewhere? I did not find it... Just found the forum, QA,...
[edit]I reported it in the forum... Just see http://forums.dropbox.com/topic.php?id=41227 [/edit]
Click to expand...
Click to collapse
You are mistaken: /data/system/dropbox, has NOTHING todo with www.dropbox.com !
See http://developer.android.com/reference/android/os/DropBoxManager.html
Dark3n said:
You are mistaken: /data/system/dropbox, has NOTHING todo with www.dropbox.com !
See http://developer.android.com/reference/android/os/DropBoxManager.html
Click to expand...
Click to collapse
Hey, just looked at your SD Maid app (looks cool).
So what do you know about /data/system/dropbox? I just read that htc uses the dir to store phone events which is then sent to the htc cloud of spying-on-your-ass. But since non-htc phones have this dir, is htc merely misusing the directory and it has other legit uses, or is this a directory we should try to keep cleaned out?
(I like the idea of changing perms so nothing writes to it if that's the case.)
600 MB additional free storage
Hi all
Just found a smart way to increase your Dropbox account with 600 MB:
1 Sign into your existing Dropbox account (or create a new account)
2 Goto https://www.dropbox.com/free
3 Follow instructions ... and voila 600 MB additional free storage
Mittaa said:
Hi all
Just found a smart way to increase your Dropbox account with 600 MB:
1 Sign into your existing Dropbox account (or create a new account)
2 Goto https://www.dropbox.com/free
3 Follow instructions ... and voila 600 MB additional free storage
Click to expand...
Click to collapse
Yay, nice to see you didn't read the thread at all.
This has nothing todo with dropbox.com
Yea other day I got the SD Maid, and the Pro version after I saw how handy it was. I too on my G1 (with 2.2) see that dropbox folder.. and lately Ive been thinking its causing my G1 to constantly reboot. When I look, it has 300+ files in it. So I clear that folder and seems to stop rebooting for a lil while.
Not sure what the deal is here however, been trying to find out. HOWEVER it only seems to reboot once its connected to the internet, so I am wondering if this is where it tries to upload and so. Not really sure. That and its hard to tell in logcat whats going on before it reboots.
Thanks
Excellent information. This works on my Sony Ericsson Xperia Pro MK16a, Rooted. Thank you so much. My best regards.
Try to change the permisions of the folder, I'm not sure if it would work but you could try ^^
Sent from my GT-I9001 using xda premium
All is ok
All was fine. The permissions :laugh:changed with root explorer. Thank you so much
Note completely disabled but only 1 file in the /data/system/dropbox folder with these Android shell commands (or use Sqlite3 editor):
content insert --uri content://settings/secure --bind name:s:dropbox_max_files --bind value:i:1
Or for Android 4.2+
content insert --uri content://settings/global --bind name:s:dropbox_max_files --bind value:i:1
settings put global dropbox_max_files 1
Reboot.
more dropboxmanager settings:
dropbox_age_seconds
dropbox_max_files
dropbox_quota_kb
dropbox_quota_percent
dropbox_reserve_percent
I've been using the advice from this thread to control this "dropbox" data collection directory for several years now until I updated to 9.0 and found that the folder and default permissions were restored after every reboot. Was irritating bc I can use root to modify /system but no longer have control over my own data partition Something is over-riding my root-user!!!
I tried different apps, TWRP's FM, adb, and almost gave up when init.d scripts wouldn't work either. init.d will work tho. A simple script to run
Code:
#!/system/xbin/sh
busybox rm -f /data/system/dropbox
at boot. You can probably chown and chmod if you want but I just deleted it. Just put it in your init.d folder and make sure you give it the correct permissions (root:shell -755), then immediately perform a soft reboot. Use hardware keys if you have to. You want the phone to go immediately OFF, no spinny wheels or "powering off" notifications. That's the only way I could get rid of the damn thing.
Anyway, I came across this thread while searching for a solution and thought I would add this in case any other paranoids like me are concerned about this mysterious "dropbox" directory. This will probably break any ability for google to troubleshoot your phone but I don't think that's real anyway. It's just spyware as far as I'm concerned.
p.s. (off-topic) Thanks @Dark3n I'm also a frequent SD Maid user btw and in case you happen to read this, I thought I might mention I intended to send a donation via your app the other day (i like to show love when ppl share badass works) but balked at the only available option for "pizza," not bc I don't appreciate it that much but I can afford a little every now and then. If you add a smaller option, "coffee" or beer or whatever, maybe even an outside of googlePlay option, BTC perhaps. I'd be happy to shoot a few dollars at you.
In addition to the standard Market Fix to get protected applications working (clearing cache/data), we also need to trick Google to think we have a Tegra 2 device.
We simply need to change the following line in /system/build.prop
ro.product.device=olympus
This tells Google Market we are using a Motorola Atrix 4G and will give us the missing Tegra 2 apps when applying our market fix.
However, since we are mimicking a phone, Tablet specific apps will not show up (NYTimes app for Tablets is an example)
Cheers!
Edit:
It is well known that the Google Web Market is hit and miss on our GTablets. This thread indicates it may take a few days for our tablet's to show up on the web interface. However, what this fix does is allow you to download most of the Froyo + Tegra2 apps via the Market Application within our tablets. There will be applications that will refuse to install through the web market interface (if your tablet can actually show up on the darn thing) because of missing capabilities, but will install just fine via the Market app.
If you want to install apps using a web browser from your Desktop computer, I recommend the use of Appbrain to generate your list of desired apps and then syncing your list on the tablet to install.
Hi,
SUPER!!
This build.prop change, just by itself, on stock 3588, allows me to see a bunch of apps I haven't been able to see before, including Firefox, Flash, Tank Hero, etc. Didn't have to do anything else, no fingerprint changes, etc.
Thanks!
Jim
AWESOME! The only thing I can't find is message ease which is no great loss and I'm not seeing it on the web either -- I think they are pulling it on and off the market. But YES -- Laucher Pro, Saumari, Silver Creek games, Flash 10.2, tv.com, both opera browsers, dolphin HD -- all there. FANTASTIC. THANK YOU!
Even Vlingo shows up which was never found before. Truth is I don't even want it but it was one of my indicators.
wd5gnr said:
AWESOME! The only thing I can't find is message ease which is no great loss and I'm not seeing it on the web either -- I think they are pulling it on and off the market.
Click to expand...
Click to collapse
Are you looking for MessagEase?
https://market.android.com/details?id=com.exideas.mekb
Whoops! Helps if you spell it right. I always think that should be a faster keyboard but then I give up and go back to BetterKeyboard or the word predicting one which is great until you need to do Linux command lines and such.
Sorry for the confusion. I even found Astro Bluetooth Module another I used to have to switch for. Very cool.
Hmmm... the market.android.com site no longer shows my device since I made the above fix! It only shows my older device. I tried just clearing the market cache and rerunning but no go. I am now running the regular market fix (clear cache in market, stop, clear data in service framework, stop, reboot).
I did install things off the market, but it had to be from the device.
Ok tablet is booted back up.... drum roll....
Nope. And now I am -- for now -- only showing my paid apps off the market, none of the freebies I had previously installed.
UPDATE: I killed the market data and cache along with the service framework data and rebooted. This made no difference to the web site (unless it takes time for it to catch up) but it did -- after installing something else -- restore my existing apps. On the other hand, having the market working on the device beats the web site, but it still means something is "off".
How do we request this be made a sticky?
I know I've tried just about every market tweak for the last 3+ months and this is the only 1 that made a huge diff.
Jim
I haven't tried this fix (heck I don't even know how to apply it, someone mind helping a noob out?) but I had the same problem you did where the web market doesn't show your device. I tried spamming the regular market fix and still no good.
However I logged back into the web store today and it showed my device, weird.
Not sure how to fix it but yesterday I changed my password so I was forced to sign in again. Of course that didn't work at the moment but I guess it worked since I can now see my device now.
Hope this helped.
wd5gnr said:
Hmmm... the market.android.com site no longer shows my device since I made the above fix! It only shows my older device. I tried just clearing the market cache and rerunning but no go. I am now running the regular market fix (clear cache in market, stop, clear data in service framework, stop, reboot).
I did install things off the market, but it had to be from the device.
Ok tablet is booted back up.... drum roll....
Nope. And now I am -- for now -- only showing my paid apps off the market, none of the freebies I had previously installed.
UPDATE: I killed the market data and cache along with the service framework data and rebooted. This made no difference to the web site (unless it takes time for it to catch up) but it did -- after installing something else -- restore my existing apps. On the other hand, having the market working on the device beats the web site, but it still means something is "off".
Click to expand...
Click to collapse
Yeah I tried logging out of the web site and back in. I've tried forcing a google account sync. And I've tried making sure Talk is running (apparently the website uses talk to send things to your device.).
Just for fun I put my ro.product.name/device/board back to Vega and with no reboot or anything the web site immediately found the device.... curious....
Well now that I'm back on the web site, my market is back to how it was even after I put the olympus line in. Getting too late. Will look at it tomorrow :-(
Hachi2Go said:
I haven't tried this fix (heck I don't even know how to apply it, someone mind helping a noob out?) but I had the same problem you did where the web market doesn't show your device. I tried spamming the regular market fix and still no good.
However I logged back into the web store today and it showed my device, weird.
Not sure how to fix it but yesterday I changed my password so I was forced to sign in again. Of course that didn't work at the moment but I guess it worked since I can now see my device now.
Hope this helped.
Click to expand...
Click to collapse
I did the change by:
- get temp root via z4root
- make /system R/W via root explorer
- start a terminal
- cd /system
- Edit build.prop: busybox vi build.prop
- did regular market fix
- reboot
Jim
wd5gnr said:
Hmmm... the market.android.com site no longer shows my device since I made the above fix! It only shows my older device. I tried just clearing the market cache and rerunning but no go. I am now running the regular market fix (clear cache in market, stop, clear data in service framework, stop, reboot).
I did install things off the market, but it had to be from the device.
Ok tablet is booted back up.... drum roll....
Nope. And now I am -- for now -- only showing my paid apps off the market, none of the freebies I had previously installed.
UPDATE: I killed the market data and cache along with the service framework data and rebooted. This made no difference to the web site (unless it takes time for it to catch up) but it did -- after installing something else -- restore my existing apps. On the other hand, having the market working on the device beats the web site, but it still means something is "off".
Click to expand...
Click to collapse
You're right that having market work on the device beats the website! The web market issues may be a whole separate battle.
Jim
jimcpl said:
I did the change by:
- get temp root via z4root
- make /system R/W via root explorer
- start a terminal
- cd /system
- Edit build.prop: busybox vi build.prop
- did regular market fix
- reboot
Jim
Click to expand...
Click to collapse
I'm quite new to the Android OS so I'm not really sure how to do this.
I installed z4root and got temp root. I'm not sure if I needed it as I read somewhere that Vegan 5.1.1 (which I am using) gives me root already.
But I installed it and ran it anyways.
I'm stuck on giving my /system read and write permissions. Is this 'root explorer' app needed? Or can I use my 'iFileExplorer' app to do so, if so how? (It came with the vegan ROM)
Not sure if you meant to type ifileManger, but it will not get you write permissions. Root explorer will allow you to write. It looks as though you may have to
open a terminal up as discussed above, to change the build prop.
Hachi2Go said:
I'm quite new to the Android OS so I'm not really sure how to do this.
I installed z4root and got temp root. I'm not sure if I needed it as I read somewhere that Vegan 5.1.1 (which I am using) gives me root already.
But I installed it and ran it anyways.
I'm stuck on giving my /system read and write permissions. Is this 'root explorer' app needed? Or can I use my 'iFileExplorer' app to do so, if so how? (It came with the vegan ROM)
Click to expand...
Click to collapse
Hachi2Go said:
I'm quite new to the Android OS so I'm not really sure how to do this.
I installed z4root and got temp root. I'm not sure if I needed it as I read somewhere that Vegan 5.1.1 (which I am using) gives me root already.
But I installed it and ran it anyways.
I'm stuck on giving my /system read and write permissions. Is this 'root explorer' app needed? Or can I use my 'iFileExplorer' app to do so, if so how? (It came with the vegan ROM)
Click to expand...
Click to collapse
Hi,
If you don't have root explorer, there's a free app on market called something like "system mount r/w" that is free that will mount /system as r/w for you. Or, I think that you can do it using a terminal and a mount command (something like mount -remount....).
Normal file explorers won't do the remount.
Jim
mount -o remount,rw /system /system
Watch out for the spaces and you need to be root so do an su command first.
When done, repear the mount command but use ro instead of rw. You can do this with a terminal program or the adb.
Root Explorer is what, $3.99? Worth it for the time savings. I bought the Ti Pro too. $300+ on a tablet...spend $9 on some software to make life easier.
iam a noob. i have stock rom 3588. how do i get market working?
By the light of morning I got back to a full market! But it again broke the web site connection. Is anyone seeing this behavior? Or is it just me?
For the new guys.
1) This appears like it MAY break your connection with the market web site [Update: Wait a few hours and it appears to catch up with you]. It may have other unknown effects. If you are not comfortable with making mods you might wait until more people have reported success or failure with this. For the record I did NOT find this fix (thanks Isira -- see OP of this thread). Just writing up my take on what you need to do. This applies to VEGAn 5.1.1 with supplement. It has been noted that with a stock rom you may need to put "busybox" before commands like cp (which you don't need to use if you have Root Explorer, by the way). If you get this to work (or not) on a different ROM, report it in this thread.
2) That being said, you need a file explorer that will look at / and edit text files, an su utility (comes with your root kit; as far as I know all the custom ROMs are pre rooted) and a command shell/terminal. Or you could spring a few bucks and get Root Explorer which is well worth it and does all of these things. Others have suggested Absolute Root tools which I do not know about. You could also use adb for all of it (which is what I did) but if you know how to do that, you probably don't need me to tell you what to do. We will be changing your build.prop file in the /system directory.
IF YOU ARE NOT USING ROOT EXPLORER GO DOWN TO STEP 3B. IF YOU ARE, GO TO STEP 3A.
3A) Open root explorer. Find /system and press the "Mount R/W" button.
4A) Long press on build.prop and select Copy. Then navigate somewhere like /mnt/sdcard and press the paste button at the bottom of the screen. This is your backup. Please backup.
5A) Go back to /system
6A) Long press on build.prop again. The menu is scrollable. You want Open in Text Editor.
7A) Find the line that says ro.product.device=XXXX (where XXXX is probably Vega). Make it read:
ro.product.device=olympus
Don't change anything else.
8A) Save the file by pressing the menu key and selecting Save & Exit.
9A) Scroll to the top of the /system directory and press the Mount R/O button.
10A) Reboot your tablet. Wait for things to settle down on restart. Open Market. Look for Saumari 2. Look for LauncherPro, Opera Mobile, etc. It will all be there.
If you don't have root explorer:
3B) Open the terminal. At the prompt, enter (spaces and lower case matter):
su
mount -o remount,rw /system /system
HINT: If you think you will do this a lot grab Script Manager off of the market. You can put the mount line in a script, tell it to execute as root (which is the same as su) and then you can run the script when you want to make changes.
4B) Start your file manager and find the /system directory. Your file manager probably starts in /sdcard or /mnt/sdcard. You'll need to go "up" a directory or two to root and then back down. Either way, when you find it, make a backup copy of build.prop somewhere you can write to. Seriously. Do not skip this step. Make the copy.
5B) Edit build.prop. You are looking for a line that sys ro.product.device=XXXX (probably Vega; I don't know about other ROMs and if this works for other ROMs but for VEGAn 5.1.1 its Vega). Carefully replace whatever you have as XXXX to olympus. So the line should read:
ro.product.device=olympus
Note: Some of us had other changes to build.prop. Not clear if these had any effect or not.
6B) Save your changes. If your file explorer is not root, you probably need to save the file to where you can write (your sdcard for example) and the copy from a terminal, such as:
su
cp /mnt/sdcard/new-buildprop.txt /system/build.prop
or
su
busybox cp /mnt/sdcard/new-buildprop.txt /system/build.prop
7B) Open your terminal and enter:
su
mount -o remount,ro /system /system
Remember spaces and case count! Also if you are in the same terminal window as before you don't have to keep entering su since you stay root.
NOTES FOR BOTH SETS OF INSTRUCTIONS
I did the original market fix after saving the file, but some people say it is not necessary. But at least a few people have said they don't see much or anything in market until the redo the fix (the one where you delete the market cache and the google services framework data and reboot).
Things that appear to work:
1) Installing free programs
2) Updating existing programs
3) Amazon market web site oddly enough
4) The official market Web site AFTER WAITING SEVERAL HOURS
5) Buying an app off the build in application
Some of us had other changes to build.prop but I don't think any of them were significant. If you have trouble you might apply it (shouldn't hurt). Also, if your "my apps" only shows your paid apps (or nothing if you have no paid apps), try downloading anything off the market and that will usually restore it. There is also an update local cache key that might do the trick, but loading some freebie off the market is easier. Also check to make sure gtalk is logged in. You can try forcing a resync on your Google accounts (in the main menu under Accounts).
Hope that helps someone. Its early so I probably made mistakes and will edit any that are found.
wd5gnr,
I don't know how "unusual" it is, but on my Gtab, where I had 3452 for awhile, then now 3588, I've always noted that I don't have a "cp" command, so I have to use "busybox cp".
Just FYI, in case anyone encounters this when they try your instructions.
Jim
wd5gnr said:
By the light of morning I got back to a full market! But it again broke the web site connection. Is anyone seeing this behavior? Or is it just me?
Click to expand...
Click to collapse
Based on this thread ( http://forum.xda-developers.com/showthread.php?t=941205 ), it seems it may take a few days for the tablets to register on the market.
I have 3 tablets and I'm trying to change the identifier for each tablet through the ro.product.model and seeing if each of the tablets will show up on the market. So far, only one tablet is showing on the web market, but it's still using the old ro.product.model identifier (GTablet-TnT-Lite).
However, the web market is still pretty wonky. Certain apps may refuse to install through the web market because of missing capabilities on our tablets, but will install just fine through the market app.
https://market.android.com/details?id=com.galoula.LinuxInstall
New every thing. Redesign of everything every where, rewite of all English parts, many bug fixes.
What for ? install Debian using debootstrap in chroot, and use your Android device like if you had installed Linux on a standard computer.
Bugs shall be reported to [email protected] .
Misc questions about how to use and feature request and general discussions to [email protected]
Market description:
This application will allow you to install a complete Debian distribution in your Android device. Based on chroot, it will perform a standard debootstrap and install a legacy Debian so that you can install, and run any classic Linux command, tool, daemon or service.
The package has few limitations; it is not restricted to Debian; we already offer the choice to use Ubuntu, and will add more distributions in close future. Each distribution is available in several tastes (stable, testing ...). It will not require to reboot; chroot is run inside Android. Installation can be done on any storage device, either on SD card, or inernal memory; no need to repartition any thing, run mkfs or fdisk. We do with what you let use. If you have almost nothing, the package will manage with almost nothing; if you can afford for a large ext4 partition on your SD card, the package will be happy to use it.
It will allow you to install all classic LAMP services like Apache, MySql, PHP, Samba, Netatalk, or just any classic Linux tool like vim, xterm, aterm, Abiword, Firefox, dillo, wget, cron, Perl, Python ... just everything.
Package utilisation will require a rooted device.
Reasons to install this package can not be listed. Just too many: want a cron daemon ? want to have gcc inside your phone ? want to recompile some kernel driver because the legacy Android driver for your Wi-Fi card has is bogus or limited ? want to use vim, or the real full featured desktop ls, ip, nmap, or top commands ? this package will give you all this for free, and much much more.
Requierments:
- an Android device based on some Linux kernel
- a rooted environment
- 300M free space
That's all.
Optionnal registration on our website, http://android.galoula.com/LinuxInstall/Register.php , will allow you to use advanced management features, and install package from within the application interface. You will not need to type any strange command in any terminal. And you will be able to make some services start automaticly at phone boot, and/or application start.
Online documentation: http://android.galoula.com/en/LinuxInstall/
Quick installation guide: http://android.galoula.com/en/LinuxInstall/QuickTutorial.html
Click to expand...
Click to collapse
Free space must be on sd-card or phone memory?
Both accepted You choose where to install.
500M by default on SD card using loop method (on ext2 or fat). Down to 180M using the directory method (does not work on FAT).
thanks for this man.
Sorry if this is a noob question but will this in any way brick/soft brick my device?
Sent from my GT540RR using XDA App
Yes, it can.
But this app is underdevelopment since almost two years, and nobody ever bricked yet. I have written a very long complete tutorial, where I say what you should NOT do. I could easily tell you how to brick in 5 steps.
But we have been working very hard on default settings, to make default settings as much safe as possible.
There are many bugs, many known bugs; but 99.999% bugs will just make the chroot not work. Data loss is very rare. Data loss was highly probable in previous version 3.2 . But default settings are now safer. And if you do not do what we claim to be dangerous ... you are safe.
The most frequent case with 3.2 was complete wipe of /sdcard and /data . This have been fixed.
We never ran into wipe of /system until now. Never bricked.
And since Galoula and me are working on it, we are the most exposed ones. We test every single feature, in all possible situations. And when we find a wipe case, we repro it dozen time until we understand why, and how to fix, so that it won't happen to YOU.
3.3 is way safer than 3.2. And nobody reported wipe on 3.2 ...
But if you blindely clik any where, yes it can. And if I tell you where to click, you can brick in 5 steps for sure And it won't be a soft brick. I promise a good real brick where even HTC will be in trouble to repair it It's explained in the tutorial.
Wow. Thanks for the reply. At least i have an idea now. Is the tut on the app itself? I'll nake sure to read it very carefully coz i wanna learn all about this stuff
Sent from my GT540RR using XDA App
A not so short tuto is inside; but since most mobile devices have only one screen, you may want to read the online tuto on your computer: http://android.galoula.com/en/LinuxInstall/
Default settings are safe. Just follow the guide.
Will go ahead and read this tut. I'll make sure to give feedback. Thanks for paying attention to this noob
Sent from my GT540RR using XDA App
this is just great, are there any videos or screen shots?
edit: nevermind i just checked the market
Feel free to send us screen shots; I am not good at doing that (i can to shots, but I don't know what could be nice to upload).
We would apreciate shots of working (of course ) VNC clients connected to server running localy, or local consoles (like Connectbot) doing funny things.
Send to support. Thanks.
Spent the whole weekend on this...
I'm trying o get an X- GUI on the Samsung Captivate, (hope i said that right) like Ubuntu so i can VNC to a linux desktop environment. I'm on FASTY and wondering why I keep running into refusal of connection. I have the password and localhost as well as the port correct. I've lost sleep on making this work. Can anyone help...?
You question is somehow off topic.
You seem to have a basic VNC connexion issue.
Could not help without deeper description. And I rarely use VNC, i have very low experience.
First point: do you have free space in the distro ? depending on installation method, and what you installed, you may have run out of disk space (especially Ubuntu, uses lot more than Legacy Debian).
The distribution manager is still beta AOT. It may report the VNC service to be up and running, when it could not rally run. First thing to check is: is it up ?
- from local machine, to ps, and check if process is up
- from remote machine, just scan your IP for the device. VNC should be port 5800 or 5900, forgot which one.
Your VNC password is *NOT* your distribution password. VNC password need to be set at a different place (this is VNC specific; VNC is not UNIX, and never claimed to be fully a *UNIX "merged" service*).
Never used VNC in LinuxInstaller. Never yet. Not enough time to test it. We take report, and will test only major and frequent issues. We have many "easy success" reports, so, we don't worry about it. We have much more issues about rooting (getting root on phone), and starting debootstrap; this is what we focus on.
Make sure you have enough free space (at least 50M free left), then join any Debian or Ubuntu forum. They will ask you if you have a CLI; you shall use either adb shell, or connectbot. Fact you are in a chroot is not an issue, chrooting is not frequent for debian users, chrooting is the normal procedure to install Gentoo; and all debootstrap users use chroot daily; forums should not reject you for this reason. As long as you have a CLI.
Good luck.
Lost me fast...
Sorry..but you lost me, and FAST! I really don't have the terminology down...but I do have the Linux 3.3 Installer running properly...it indicates so. I was assuming that this would allow me to somehow load Ubuntu on my Captivate..as I've seen on some screen shots...I guess I'm just lost...a little knowledge is dangerous...I have a little. Just enough to accomplish the basics..but the vernacular is LOST to me. Guess I'll have to wait for the Ubuntu apk...thanks for trying...
I've got this errors...(see attached files).
I have busybox 1.19, connectbot and the superuser (v2.3.6.3 and su binary v2.3.2, the latest from the maket)...
What can I do?
you guys are still lucky.your able to make it work...
im running the ongoing cm7 2.3.5 on moto defy...
kernel is not supporting this yet.
hailmary what's missing in your kernel ? I don't know any Android that won't have ext2 in; if you have an Android without any ext2 filesystem, please contact me in private, I know it could be done, and I would be VERY CURIOUS to see how HTC did it.
If you are missing loop support in kernel, try block or directory method. Blocck will require ext2; directory won't (but will work only over ext FS ... so ... unless you can use NFS )
dugryce , ScumpinatoS, I will come back later (maybe today, maybe not).
ScumpinatoS said:
I've got this errors...(see attached files).
I have busybox 1.19, connectbot and the superuser (v2.3.6.3 and su binary v2.3.2, the latest from the maket)...
What can I do?
Click to expand...
Click to collapse
Reading the first message, you as, as said, a CPU issue. What's your CPU ? device model ?
run in some console:
uname -a
which tail
Application could not load viable environment to work; it is an issue, but it can be fixed. I can help digging, but I won't give you any solution. Send an email to Galoula; the bug report system via the console should work for you.
doublehp said:
Reading the first message, you as, as said, a CPU issue. What's your CPU ? device model ?
run in some console:
uname -a
which tail
Application could not load viable environment to work; it is an issue, but it can be fixed. I can help digging, but I won't give you any solution. Send an email to Galoula; the bug report system via the console should work for you.
Click to expand...
Click to collapse
I have a Huawei Ideos CPU: MSM7225 without GPU.
I am use it and try install Ubuntu Natty but after download all deb package i get error installation, "issue binary, try other version"
Can someone help me what distro (Ubuntu/Debian) and what version of it that have installed succesfully.. please...
Sent from my GT-S5570 using XDA App
I've seen countless threads on these 2 errors, but I just found something intriguing on my android device.
This one is a Measy U1A android stick (the ones that you connect to your TV via HDMI). A truly nice piece of hardware, but it seems to have some issues.
Since day 1 I can't install apps most of the time. Yes, *most* of the time. 80% I get the "Invalid Package file" error, another 10% of the time I get a "Package was not signed correctly", but curiously enough, a 10% of the time the packages go through and install correctly.
Of course, this gets on my nerves.
Now, I'd really want to know what's going on and I'd love some help from the true Android experts.
This is what I've already done:
Got a Log Viewer to see what was going on.
At first it said that was an error downloading (more on this later)
Then other times it said that there was no signature for X or Y file INSIDE the apk file (I remember some libraries, I was trying to install netflix on my tests)
So, I tried to tackle the download error by checking the space (df), I found that /data had few space remaining, so I cleared stuff from it. Now I have 308Mb free, more than enough to download Netflix (14Mb download). I'm talking about /data since I found out that the downloadfile-x.apk files get downloaded to /data/data/com.android.providers/downloads/cache
Tried again, nothing. Ok, so I thought that maybe there was some weird error in the /data partition. I created a directory on the sdcard portion of the stick and linked it (ln -s). Same issues. I created a directory on my external sd card and liked to it, and the same.
Now, for the weird part, and this is where I'd love some insight:
Out of 5 downloads, ES File Explorer got installed correctly, and I got a bunch of EQUALLY SIZED downloadfile-x.apk files on that directory, but NONE OF THEM HAS THE SAME MD5 SUM. Weird? Yep, but that could only mean 3 things: Either there's a problem with my wifi/network stack, or the /data, /sdcard, /mnt/extsd partitions ALL have errors in them. The 3rd option is that Perhaps Google signs every download with a different salt and that's the reason they are all different. But I DON'T THINK THE 3rd OPTION IS LOGICAL OR PRACTICAL.
Now, I don't have access to recovery here... well, I haven't tried but there's no obvious option, perhaps CWM but I don't want to risk it too much since it ran Ubuntu for a while and now that won't boot (that's another topic, unable to debug it since I can't see anything on the screen until it boots).
I've already tried:
1. Deleting Play Cache and Data, rebooting
2. Deleting Play and installing it again (it took several tries because of the same issue)
3. Factory Default and logging to my google account again
4. FIRMWARE UPGRADE (yes, I found a new firmware, it seems faster and more stable, but I still have that issue).
Now, I haven't found a memory checker or a "nand" (as you call it) checker on the app market, do these apps exist? I'd love to rule this out.
Thanks if anyone has another option, as I said, I'm out of them. The funny thing is that once the apps are installed THEY WORK FINE!!!!
Please help, I just can't spend 15 minutes to install each app that I want :laugh:
I know my way around Linux, so don't be afraid to suggest crazy things :fingers-crossed:
*The only thing I still want to do is to be able to boot Linux again and perform some tests from there*
No one?
Sent from my Galaxy S3 using Tapatalk 2
NuttyBunny said:
I've seen countless threads on these 2 errors, but I just found something intriguing on my android device.
This one is a Measy U1A android stick (the ones that you connect to your TV via HDMI). A truly nice piece of hardware, but it seems to have some issues.
Since day 1 I can't install apps most of the time. Yes, *most* of the time. 80% I get the "Invalid Package file" error, another 10% of the time I get a "Package was not signed correctly", but curiously enough, a 10% of the time the packages go through and install correctly.
Of course, this gets on my nerves.
Now, I'd really want to know what's going on and I'd love some help from the true Android experts.
This is what I've already done:
Got a Log Viewer to see what was going on.
At first it said that was an error downloading (more on this later)
Then other times it said that there was no signature for X or Y file INSIDE the apk file (I remember some libraries, I was trying to install netflix on my tests)
So, I tried to tackle the download error by checking the space (df), I found that /data had few space remaining, so I cleared stuff from it. Now I have 308Mb free, more than enough to download Netflix (14Mb download). I'm talking about /data since I found out that the downloadfile-x.apk files get downloaded to /data/data/com.android.providers/downloads/cache
Tried again, nothing. Ok, so I thought that maybe there was some weird error in the /data partition. I created a directory on the sdcard portion of the stick and linked it (ln -s). Same issues. I created a directory on my external sd card and liked to it, and the same.
Now, for the weird part, and this is where I'd love some insight:
Out of 5 downloads, ES File Explorer got installed correctly, and I got a bunch of EQUALLY SIZED downloadfile-x.apk files on that directory, but NONE OF THEM HAS THE SAME MD5 SUM. Weird? Yep, but that could only mean 3 things: Either there's a problem with my wifi/network stack, or the /data, /sdcard, /mnt/extsd partitions ALL have errors in them. The 3rd option is that Perhaps Google signs every download with a different salt and that's the reason they are all different. But I DON'T THINK THE 3rd OPTION IS LOGICAL OR PRACTICAL.
Now, I don't have access to recovery here... well, I haven't tried but there's no obvious option, perhaps CWM but I don't want to risk it too much since it ran Ubuntu for a while and now that won't boot (that's another topic, unable to debug it since I can't see anything on the screen until it boots).
I've already tried:
1. Deleting Play Cache and Data, rebooting
2. Deleting Play and installing it again (it took several tries because of the same issue)
3. Factory Default and logging to my google account again
4. FIRMWARE UPGRADE (yes, I found a new firmware, it seems faster and more stable, but I still have that issue).
Now, I haven't found a memory checker or a "nand" (as you call it) checker on the app market, do these apps exist? I'd love to rule this out.
Thanks if anyone has another option, as I said, I'm out of them. The funny thing is that once the apps are installed THEY WORK FINE!!!!
Please help, I just can't spend 15 minutes to install each app that I want :laugh:
I know my way around Linux, so don't be afraid to suggest crazy things :fingers-crossed:
*The only thing I still want to do is to be able to boot Linux again and perform some tests from there*
Click to expand...
Click to collapse
hey dude
finally a fellow measy u1a user.....
where r u from???
regarding the package invalid problem the rom of the device isnt exactly signing the package while installing....hope measy would release an update(i know its impossible)
i tried installing mk808 firmware but couldnt despite tampering its kernel code
no use of factory reset as it just installs the already existing os
p.s
i am trying hard to find a wifi remote control app to control this dongle from my sammy galaxy r mobile but no luck did u do anything like that??
also check out
http://forum.xda-developers.com/showthread.php?t=2173501
thanks
mahi98 said:
hey dude
finally a fellow measy u1a user.....
where r u from???
regarding the package invalid problem the rom of the device isnt exactly signing the package while installing....hope measy would release an update(i know its impossible)
i tried installing mk808 firmware but couldnt despite tampering its kernel code
no use of factory reset as it just installs the already existing os
p.s
i am trying hard to find a wifi remote control app to control this dongle from my sammy galaxy r mobile but no luck did u do anything like that??
also check out
http://forum.xda-developers.com/showthread.php?t=2173501
thanks
Click to expand...
Click to collapse
Mexico City here.
I found a firmware update, it makes the homepage icons bigger, changes the boot screen and overall feels faster. But I still have the same error.
As for the remote control, I found a vnc server that can be run on the dongle, and any vnc viewer can be used to control it.
I got a Rikkomagic III (not S, silly me), and let me say, that thing kicks the U1A over the window, performance is great but it has no bluetooth.
I'll keep trying to find a solution for my issue, as the Rikkomagic works fine.
Sent from my Galaxy S3 using Tapatalk 2
What's that remote app name??
Sent from my GT-I9103 using xda app-developers app
mahi98 said:
What's that remote app name??
Sent from my GT-I9103 using xda app-developers app
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=org.onaips.vnc
That's the server. You need a VNC viewer for your phone
NuttyBunny said:
https://play.google.com/store/apps/details?id=org.onaips.vnc
That's the server. You need a VNC viewer for your phone
Click to expand...
Click to collapse
As of now there is only one app . Remodroid which works as per requirement
you can download it from play store. you need to install in both the Dongle and cellphone . it works well.but sluggish at times
Hi and straight to the point: I just can't do anything relevant on this brand new Huawei G730-U251 even after being properly rooted. Can't modify most parts of the system 'cause I'm unable to make useful apps to perform their jobs. AdAway, NinjaMorph, Xposed Framework, GravityBox... you name it; the usual army of development wonders is plain useless on this device, so root becomes worthless too. Blame the infamous "set_immutable_file" for that. Then, there's no file explorer capable to even simply rename it and no Terminal Emulator is able to change it's properties or mount the entire system as writable... at least on this particular device. Funny thing is I actually have a previous release of this very same model that has not such a PITA issue. Seems Huawei did not had enough making this model's bootloader unlockable, they had to go further in their quest of selling you, unaware people (just like me) uncustomizable stuff. But that's another story... So, if there's somebody out there with this sort of issue solved or just wanting to bring some help... be welcome. I've found many answers to similar problems that just don't work nor even apply; but no one seems to have exactly this kind of issue, therefore, no answers found yet ...
Ok. Here it's me answering my own question: System Tuner by 3c (Cedric Counotte) That's the answer. I've been trying all sorts of terminal emulators with no luck, til I tried the one included in System Tuner app (using the script below). For some reason it was the only one capable to solve my problem (I will ask Cedric why, soon). His app (which btw I've been using for some other minor system tweaks, tho never tried the emulator before) has proved to be very powerful in many ways. In fact, I'm pretty sure that once you learn how to use it (which I didn't yet) you could easily save the space of at least five or six apps. Really. Now, everything's working as supposed: charmingly. So thanks to Cedric. He's the master
Here's the (well known) script:
mount -o rw,remount /system
chattr -R -i /system
... again: for me, the ONLY one able to run this common script was System Tuner emulator. So, if you're victim of the same issue and don't want to get into major computer related hassle, well... just give it a try!
:thumbup:
Sent from my HUAWEI G730-U251 using XDA Free mobile app