anyone know anything about these tablets? It is a cheap brand from bestbuy, I was just wondering if anyway could help me to get the android market to run on it.. It is a custom Itomic branded rom, it only has swift market or something like that on it.. Also, the recovery is not a regular recovery. When I go into recovery it just shows Itomic on the screen and says recovery mode at the bottom.. Itomic BestBuy That is the link to bestbuy for specs on it..
TIA
Julian
Are you rooted? If you're not rooted then go here: HERE and pick up the latest SuperOneClick program to get you started. Once you're rooted you need to download the latest Android Market apk here: HERE. Put that file on the root of the sd card in your tablet and then use a file explorer such as Root Explorer to find the file. Once you know where the apk is located you can use an APK installer to install the file. Then viola! You now have the Android market on your new tablet.
Trust me when I say you want to avoid a resistive screen (no multitouch) and 256M RAM (slooooow) as I have a 10" tablet with those specs.
Its not mine, i would not buy one with those specs just for the reason of I am used to my evo, not the best phone, but I like the way it responds and I would want the same or better response from a tablet... This is actually my 10 year old cousins tab, and it did not come with the android market as stated above so I am trying to fix that... I am nervous to root it because it doesnt have a regular recovery so if something goes wrong I would not be able to fix it... So I am looking for a dev that has experience with this or a similar tab... If I knew linux programming Id be a dev but unfortunately I dont know and at this point in time I do not have the time to learn...
That one click root program won't hurt anything. I've rooted many tablets and phones with it and it works like a charm, no problem. Once you're rooted and get the market make sure you get rom manager and see if there are any flashable recoveries for the tablet.
Sent from my SkyRaider Bolt using Tapatalk
I also forgot to mention I cannot get adb drivers to work... I have dev on and it still wont recognize the android drivers.. It is not the micro usb but mini usb, I have tried multiple usbs but it still will not find the correct drivers...
I dug into this and just found the tab came rooted, all I had to do was mount the system as rw through adb and then manually changed su to the gb su.. I installed root explorer and rom manager but unfortunately there isnt a recovery for it... I saw on androidtablets.net that a guy is willing to port cwm to any tab for you but am nervous to try anything because it is my cousins... I think for now I will just install the market and be done..
Yeah that would be the best since it doesn't look like it's too widely supported. But cm would give it a smoother feel and be a little nicer, but do what you choose.
Sent from my SkyRaider Bolt using Tapatalk
alil2cul4u said:
I dug into this and just found the tab came rooted, all I had to do was mount the system as rw through adb and then manually changed su to the gb su.. I installed root explorer and rom manager but unfortunately there isnt a recovery for it... I saw on androidtablets.net that a guy is willing to port cwm to any tab for you but am nervous to try anything because it is my cousins... I think for now I will just install the market and be done..
Click to expand...
Click to collapse
I am new to this whole thing, but I just got an Itomic tablet and I am also trying to get the Android market to work. Im stucj though i cant for the life of me get an ADB to work. Ive tried everything I could think of but cant get it to work. What did you do to make it work?
Plewis831 said:
I am new to this whole thing, but I just got an Itomic tablet and I am also trying to get the Android market to work. Im stucj though i cant for the life of me get an ADB to work. Ive tried everything I could think of but cant get it to work. What did you do to make it work?
Click to expand...
Click to collapse
I did it on my laptop, I have windows 7 64 bit with the android sdk installed.. Sdk install guide I think that adb worked just with the sdk installed, because I didnt do anything special that I know of.. I was having trouble getting adb to work on vista where I just had the adb files not the full sdk.. I also have the sdk in my path (if that makes any difference?) I also have all the htc diag drivers and motorola diag drivers installed... If you cant figure it out, just let me know and Ill dig through everything and see if I cant figure out what drivers helped... Also, I didnt use the plug that came with it.. The one I used was much thicker than the one supplied, the one I used came with a card reader... also the su file i used is the latest one posted over at gooinside.me SU.zip To change it i went into adb and
Very often when you want to write files to a particular partition on ADP1, you will get a "Permission Denied" if the partition is mounted read-only.
To get around this, you need to mount the partition read-write. Typically this is done with /system partition
$ adb shell
$ su
$ mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
(Replace /dev/block/mtdblock3 & /system with appropriate device path and mount point, as obtained from cat /proc/mounts) quoted from: android-tricks.blogspot.com
Click to expand...
Click to collapse
mounted the system as read-write then changed the su found in /system/xbin... forgot to add you must extract the su found in the zip folder...
alil2cul4u said:
I did it on my laptop, I have windows 7 64 bit with the android sdk installed.. I think that adb worked just with the sdk installed, because I didnt do anything special that I know of.. I was having trouble getting adb to work on vista where I just had the adb files not the full sdk.. I also have the sdk in my path (if that makes any difference?) I also have all the htc diag drivers and motorola diag drivers installed... If you cant figure it out, just let me know and Ill dig through everything and see if I cant figure out what drivers helped... Also, I didnt use the plug that came with it.. The one I used was much thicker than the one supplied, the one I used came with a card reader... also the su file i used is the latest one posted over at gooinside.me To change it i went into adb and mounted the system as read-write then changed the su found in /system/xbin... forgot to add you must extract the su found in the zip folder...
Click to expand...
Click to collapse
thanks for your help! I got the ADB to work and was able to mount it as rw. But, like I said I am new to this and am still having some trouble. then you say you changed the su found in the /system/xbin what does that mean? how do I get to /system/xbin? Thanks again for your help
---------- Post added at 02:59 PM ---------- Previous post was at 02:41 PM ----------
alil2cul4u said:
I did it on my laptop, I have windows 7 64 bit with the android sdk installed.. I think that adb worked just with the sdk installed, because I didnt do anything special that I know of.. I was having trouble getting adb to work on vista where I just had the adb files not the full sdk.. I also have the sdk in my path (if that makes any difference?) I also have all the htc diag drivers and motorola diag drivers installed... If you cant figure it out, just let me know and Ill dig through everything and see if I cant figure out what drivers helped... Also, I didnt use the plug that came with it.. The one I used was much thicker than the one supplied, the one I used came with a card reader... also the su file i used is the latest one posted over at gooinside.me To change it i went into adb and mounted the system as read-write then changed the su found in /system/xbin... forgot to add you must extract the su found in the zip folder...
Click to expand...
Click to collapse
I was able to get the adb to work and remount it as rw. But like I said im new to this, and Im confused when you say you manually changed the su to the gb su. How do I access the /system/xbin folder? thanks again for you help.
---------- Post added at 03:16 PM ---------- Previous post was at 02:59 PM ----------
actually I figured it out once I got a root explorer. Im able to find the su file, but not really sure what, if anything Im supposed to change. Once thats taken care of , how to I download the android market? Do i just find an APK online for it? Or is therre another program or something I have to go through. Thanks again, im learning...
Sorry its taken so long to reply, when i say I changed the SU in /system/xbin, I opened windows cmd and ran "adb shell" "cd to /system/xbin" "rm ./su" then "exit" still in the cmd i adb pushed the su file that i extracted from this file su-2.3.1-efgh-bin-signed.zip (thanks to goo-inside.me) with "adb push C:\su /system/xbin" I then pushed superuser.apk to /system/app with "adb push C:\superuser.apk /system/app" then "adb reboot" and when it turns back on you are fully rooted. now download gapps from goo-inside.me then extract the system/app from the zip you need to install GoogleServicesFramework.apk OneTimeInitializer.zip SetupWizard.apk Talk.apk Gmail.apk Vending.apk with "adb push *.apk /system/app"
Related
hey guys, been a short term fan of android, and i recently (or what i thought so) rooted my X10i with the original RB..20 Firmware.
Today i updated to the new R2BA026 firmware. and my device appears routed but it not, how do i go about rooting this firmware to remove the annoying Moxier apps etc.
Plz Plz Plz Help
http://forum.xda-developers.com/showthread.php?t=740240
Read this thread !!!
I just found it Lol
Thank you for telling me anyhow.
im really stuck on rooting it even with the instructions. im in the CMD.exe and all im getting is it cannot find the files even though they are directly on my C drive and also it IS connected via USB / Development mode
hellllllllllllllllp!
do you have adb installed ?
I prefer this method - forum.xda-developers.com, having tried the other today it's a bit more complicated afterwards imo trying to run adb.
the other way you said to me i tried on my unlocked X10i, but it wont work on this build as its already above the 24 build.
Ive downloadd the SDK and i have the ADB.exe in the kit but am i looking at the wrong thing? how would i install it if it just runs a cmd.exe?
With this method you can root any regional firmware, atleast up to 026 and you will get updates from seus, root will be gone but its hopefully just to root the new firmware again.....
Saw somewhere a full script with adb inside no need to install it on the computer but atm i can find it
ok well, erm, which method would be better, ?? shall i do the original root procedure i did before flashing the files on to the phone?
fkofilee said:
the other way you said to me i tried on my unlocked X10i, but it wont work on this build as its already above the 24 build.
Ive downloadd the SDK and i have the ADB.exe in the kit but am i looking at the wrong thing? how would i install it if it just runs a cmd.exe?
Click to expand...
Click to collapse
extract the exploid_x10 to a folder with the same name directly under C:
then put the adb.exe, AdbWinApi.dll,AdbWinUsbApi.dll into same folder
then cd to that folder with command promt and then run runme.cmd
that should do it
ok well so far so goo most of the files are moving on to the SD card BUT...
c:\exploid_x10mini>adb push su /sdcard/su
failed to copy 'su' to '/sdcard/su': Permission denied
thats what im getting on my Cmd panel.
Sorry, adb.exe, AdbWinApi.dll,AdbWinUsbApi.dll should be put into Exploid_x10/FILES folder.........
so do i have to create a folder inside the exploid_x10mini? because the files are already there
fkofilee said:
so do i have to create a folder inside the exploid_x10mini? because the files are already there
Click to expand...
Click to collapse
nah then u got the right one, your sdcard shouldnt be mounted to pc
and you have to turn wifi off and on when program tells you to
usb debugging should be enables on the phone aswell
all good till running rootshell when it comes back saying...
$ rootshell
rootshell
rootshell: permission denied
sorted YEY!!!
Thank you for all your help. Im not a complete noob ith computers, i know quite a bit but, dealing with android is a bit of a new experience.
fkofilee said:
ok well, erm, which method would be better, ?? shall i do the original root procedure i did before flashing the files on to the phone?
Click to expand...
Click to collapse
It's personal preference I guess.
I rooted... now what?
How do I remove the Timescape and other crap after rooting with this method? If you didn't guess, I am a complete noob with Android.
The world's first ereader with a color Mirasol display is finally on the market, but unfortunately it's running a severely locked-down Android by the Korean bookstore chain Kyobo. The Kyobo ui is entirely in Korean, the browser blocks downloads, and the reader app is crap. In other words, it's basically useless to anyone outside of Korea. A few enterprising Americans have imported them and been extremely disappointed. Will someone please take a look at this device and see if it can be rooted or if something else can be done to make it of use to the rest of us?
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Nate over at The Digital Reader has a firmware update that supposedly contains all of the installed apps. He is asking for someone to try and hack it. He has a download link for the firmware at The Digital Reader.
I also posted this as a question here on XDA:
http://forum.xda-developers.com/showthread.php?t=1432283
it is rooted since some time already.
files and instructions are in the following archive, but since instructions are in korean, i'll do a writeup below.
(argh! spambot won't allow this link, so you'll have to piece it together...)
www<dot>4shared<dot>com/zip/aLwRc7ZG/mirasol_rooting.html
edit: needed files are also in an attachment below
the gist is that you need to flash the boot partition via fastboot, setup root and busybox, and then modify secure->install_non_market_apps in settings.db.
you will need to have adb and fastboot from the android sdk working on your computer. There are many posts about this elsewhere, so i won't go into the details.
also, i only print filename without path, just find the corresponding file in the mentioned archive and modify the commands accordingly.
flash the boot partition via fastboot
first get your kyobo into fastboot mode (with usb cable attached) by pressing volume-down at bootup. timing here can be a bit finicky, but easiest seems to be to shut it down completely and then press just after pressing power.
issue a 'fastboot devices' on computer, if successful it should give you the response '???????????? fastboot' or similar. if empty or hangs, try again by rebooting the kyobo by pressing power with volume-up held (you can go into fastboot immediately after reboot by volume-down as expected).
when positive response above, you can flash by
Code:
fastboot flash boot boot.img
and then reboot by
Code:
fastboot reboot
edit: simplified fastboot instructions, thanks to smb_gaiden, whose button-poking-fu is strong.
setup root and busybox
with boot partition flashed you now have adb access, so let's use it. let the device boot as normal, and then issue the following.
Code:
adb push busybox /data/local/tmp
adb push fixsu.sh /data/local/tmp
adb push su /data/local/tmp
adb shell chmod 777 /data/local/tmp/busybox
adb shell chmod 777 /data/local/tmp/fixsu.sh
adb shell chmod 777 /data/local/tmp/su
adb shell /data/local/tmp/fixsu.sh
adb shell ln -s /data/local/tmp/busybox /system/xbin/busybox
after this, install some apk's from the archive
Code:
adb install superuser.apk
adb install blackmart.apk
fix non-market apps setting
only thing left is to change a setting to allow non-market apps to be installed. if you don't care about your current settings (locale, etc), you can just push the settings.db from the archive like so:
Code:
adb push settings.db /data/data/com.android.providers.settings/databases/
if you *do* care about your settings, you'll need to pull the settings.db, edit it in some sqlite db editor (set secure->install_non_market_apps to 1) and push the result.
that's it. all rooted. now you just need to install angry birds and yer' set ;-)
Adb doesn't seem to start properly on device
Hello.
I did succeed in flashing the bootloader via fastboot.
However when I boot device - I see adb on usb only for some initial seconds, and then it disappears.
For that matter my device already had December firmware on it.
Any ideas how to activate adb on device?
Thank you,
Leonid
it may be that persist.service.adb.enable is reset, stopping the adbd service. try flashing the attached boot image instead, see if that fixes it. it is the same as above, except that persist.service.adb.enable is ignored.
edit: i took a look at the december update, afaict it should pose no problem (very few changes in there).
Once these steps are done, how do you install google market?
Thanks.
edit: the original instructions were snafu, so i replaced them with something that should actually work.
getting android market running on the kyobo
needed files are in the attached archive.
install like so:
Code:
adb remount
adb push DrmProvider.apk /system/app
adb push MediaProvider.apk /system/app
adb push DownloadProvider.apk /system/app
adb push GoogleServicesFramework.apk /system/app
adb push Market-3.4.4.apk /system/app
adb push init.qcom.post_boot.sh /system/etc
adb push fix-shared-user.sh /data/local/tmp
adb shell chmod 777 /data/local/tmp/fix-shared-user.sh
adb shell /data/local/tmp/fix-shared-user.sh
wait for the reboot, find market in the menu, and off you go (with downloads this time ;-)
if downloads still do not work after this, try re-executing the last line. android periodically writes to the file we are modifying, which might clobber our changes if unlucky.
I am thinking about buying one of these because I have seen it on sale for 50% discount. However, the general reviews aren't too encouraging, so will rooting make any difference to overall performance?
fatboy1976 said:
I have seen it on sale for 50% discount.
Click to expand...
Click to collapse
where is that?
throwaway4096 said:
you'll need GoogleServicesFramework.apk and Market-3.4.4.apk from the following links:
http://androidmarketu.googlecode.com/files/GoogleServicesFramework.apk
http://forum.xda-developers.com/showthread.php?t=1391565
install like so:
Code:
adb remount
adb push GoogleServicesFramework.apk /system/app
adb push Market-3.4.4.apk /system/app
find Market in the menu and off you go.
Click to expand...
Click to collapse
I'm finding the market force closes when downloading an app.
May I seek help from someone who has rooted recently? I am finding it pretty difficult to get into fastboot. So some questions as I continue to play.
Which version is currently rootable? I bought mine this week and want to be sure it is still applicable with the method here.
Do I need a USB driver to work this hack? EDIT: Yes, found with a web search.
When do I press the volume keys? Immediately after power? Similar timing? When I see the flicker on the screen? When I see the logo? Before all that? EDIT: I did not need the volume up key to get into fastboot.
Thanks!
rooting for beginners
Some friends and i ordered the kyobo to solve our eye-problem (nystagm)
We still can´t figure out, how to root it.
Can you please give us some rooting instruktion vor beginners??
It would be so essential for us, as the kyobo is little worth without forgeign apps!
Thank you very much!
Joe
send2toonie said:
I'm finding the market force closes when downloading an app.
Click to expand...
Click to collapse
Hi, I am stuck with the same problem. Have tried many things?!
---------- Post added at 04:57 PM ---------- Previous post was at 04:32 PM ----------
smb_gaiden said:
May I seek help from someone who has rooted recently? I am finding it pretty difficult to get into fastboot. So some questions as I continue to play.
Which version is currently rootable? I bought mine this week and want to be sure it is still applicable with the method here.
Do I need a USB driver to work this hack? EDIT: Yes, found with a web search.
When do I press the volume keys? Immediately after power? Similar timing? When I see the flicker on the screen? When I see the logo? Before all that? EDIT: I did not need the volume up key to get into fastboot.
Thanks!
Click to expand...
Click to collapse
Hi, Managed to root my kyobo after about 8 h trying. I installed the firmware update on my kyobo, that is found on the web, as instructed from the SD card. Then I installed fastboot and adb on my computer (search for 'how to install fastboot and adb'), as I found instructions for that as well. To enter fastboot I kept Kyobos, volume down button for about 10 sec, when booting the device (kyobo connected to computer with USB) - nothing happens -> however on my computers command window (cmd), 'fastboot devices' command produces an answer with '? ..' as it should. The biggest issue I had was to get adb working. For this purpose I installed and removed a couple of USB drivers - I don't really know how I got it to work finally.
You can tell if you have succeeded installing a useful usb driver, if you enter the 'adb devices' command in the cmd window and it returns a device number. Then you are ready to go with the rest of the commands/instruction as seen in the insturction of this thread.
From the blackmart application I was able to install many useful applications - the Launcher application can replace the Kyobo "home" application, which is very useful.
I installed android market as well, but so far I have not been able to download and install applications. I think It might be a permission issue between kyobo software and the installed android market?
Hey Guys!
is there a way to root the kyobo via mikrosd?
thanks a lot
Joe
Hey Joe. I've seen you on this forum as well as The Digital Reader asking for help with the Kyobo rooting. I too am a beginner and I'm trying to build up the nerve to try it. Wish us both luck and I hope someone can share rooting-for-dummies with us.
@fatboy1976: rooting won't improve performance in itself. it makes the device better as you can install apps, but ofc the hardware is still the same.
@send2toonie: yes, sorry about that. it worked for me, but only thanks to other changes. it's hard to keep track :-/. i updated the original post with new instructions which should work properly.
@smb_gaiden: hah, excellent, i never tried that! original post updated.
@Joe84: it should be possible to root via microsd by creating an update.zip. i haven't gotten around to trying that yet, but maybe in future. for now this is as simple as it gets.
Kaarlos said:
Hi, I am stuck with the same problem. Have tried many things?!
---------- Post added at 04:57 PM ---------- Previous post was at 04:32 PM ----------
Hi, Managed to root my kyobo after about 8 h trying. I installed the firmware ...(updated -see above..) .., which is very useful.
I installed android market as well, but so far I have not been able to download and install applications. I think It might be a permission issue between kyobo software and the installed android market?
Click to expand...
Click to collapse
Jep! With the updated instuctions the Android Market now finally works!! Thanks! (Installed twice)
Kaarlos said:
Jep! With the updated instuctions the Android Market now finally works!! Thanks! (Installed twice)
Click to expand...
Click to collapse
Hi,
Could you post the OS/processor version and driver name that got adb working for you. If you can also remember the keys pressed to put the Kyobo in the correct boot mode for adb, that would be nice too.
I have also managed to load apps on my Kyobo but that is without having su, Superuser, adb and Android Market working. The above info would be helpful in fixing that. Holding the volume down fir 10 seconds after pressing power on puts the Kyobo into fastboot mode. Adb requires a different mode and set of key presses. This is because there is a menu of boot options being displayed which can't be seen on the Mirasol screen. I suspect this is because of display settings within the boot.img but that is only a guess on my behalf.
Hello,
Here is the short story.
I have Samsung Galaxy ACE which is rooted.
Till y'day I was using CM9 Beta 8 ICS 4.0.4 and it was working well.
I installed CM10 JB for Galaxy Ace alpha1 from "hxxp://maclaw.pl/?page_id=180#comment-3642"
Now the problem is, JB doesn't have File Manager installed and I need to install TB to revert my backups.
Due to some unknown reason I am not able to access internet on my device either through GPRS or 3G connection.
I am desperately looking for a way to access my SDCARD wherein I have all my apk's which I can install however, without File Manager I am not sure how to install an apk.
I did some google search and came across topics about installing apk using Android SDK etc.. however I would not want to work on SDK as I feel its bit tedious job for me.
I also tried Android Injector however that didnt work even if I have enabled USB debugging Mode for adb + apps.
Now, I am hoping that, I can use the Terminal Emulator which is preinstalledo n my phone to install apk present on my sdcard.
However, I am not sure how to do that, It would be really appreciated if anyone can suggest the steps to install apk present on my sdcard from Terminal Emulator available on my phone.
Here are some of the screen captures
http://imageshack.us/photo/my-images/855/screenshot2012072418240.png/
http://imageshack.us/photo/my-images/52/screenshot2012072418234.png/
http://imageshack.us/photo/my-images/822/screenshot2012072418230.png/
Thanks
Never mind...
I managed to install Astro File Manager apk from Terminal Emulator.
For those who are interested, here is what I had done.
Previously, I wasn't able to browse sdcard contents from TE,
I rebooted my phone once, fired up TE again
~Android$ su
Allow root access for TE
~Android# cd sdcard
~Android# ls ( Contents of SD card are listed ) I had copied astrofm.apk on root of SDCARD
~Android# pm install astrofm.apk
Success !
Thanks
P.S. This thread can be closed.
@@
hsotnas said:
Never mind...
I managed to install Astro File Manager apk from Terminal Emulator.
For those who are interested, here is what I had done.
Previously, I wasn't able to browse sdcard contents from TE,
I rebooted my phone once, fired up TE again
~Android$ su
Allow root access for TE
~Android# cd sdcard
~Android# ls ( Contents of SD card are listed ) I had copied astrofm.apk on root of SDCARD
~Android# pm install astrofm.apk
Success !
Thanks
P.S. This thread can be closed.
Click to expand...
Click to collapse
Awesome guide !!!! , thanks bro !! :good::fingers-crossed:
Thank you for the guide
it works. thank you
works, thanks
hsotnas said:
Never mind...
I managed to install Astro File Manager apk from Terminal Emulator.
For those who are interested, here is what I had done.
Previously, I wasn't able to browse sdcard contents from TE,
I rebooted my phone once, fired up TE again
~Android$ su
Allow root access for TE
~Android# cd sdcard
~Android# ls ( Contents of SD card are listed ) I had copied astrofm.apk on root of SDCARD
~Android# pm install astrofm.apk
Success !
Thanks
P.S. This thread can be closed.
Click to expand...
Click to collapse
I very much appreciate the quick tutorial!
However, with that being said, I am having an issue trying to install my .apk onto my Motorola Xoom (Rooted running CM10.1) through the use of Terminal Emulator. I first tried installing the .apk from my File Manager and just clicking on the icon, and clicking Install, like one would think one should be able to do. When that method failed, multiple times(kept saying "insufficient storage, please delete files through app manager") which by the way, I know for a fact I have 15.8GB of storage left on my Xoom, so this should not be the issue. I then decided to try and install through Terminal Emulator. Now one would think it would be about the same as using adb commands on a Computer, which it somewhat is I guess you could say. So I go to T.E. and type the commands to get Super User access, then cd sdcard to go into the directory, then cd download because this is where my file is located, then I type pm install ****.apk.
I get a line of command that says: a) pkg: ****.apk and then b) Failure [INSTALL_FAILED_INSUFFICIENT_STORAGE], and then the command line just goes back to my download folder directory.
I've had this issue before on my Galaxy S3, but can't remember how I ended up resolving the issue. Think I did a factory data reset/wipe, which I don't want to have to do to my Xoom. So any assistance would be much appreciated. I do understand that your device was a Galaxy ACE, but I wouldn't think it would matter as to what the device is, since it is the same install method/command for any Android device essentially. Hope someone can help out. If not, I may have to post in another Device Thread (Motorola Stingray Xoom I would assume).
Many thanks in advance, and I will click the Thank You, if any responses come through.
Really appreciate for the guide man
Sent from my LG-P700 using xda app-developers app
Thanks for the reply... short, to the point, and it works.
DannyShane said:
I very much appreciate the quick tutorial!
However, with that being said, I am having an issue trying to install my .apk onto my Motorola Xoom (Rooted running CM10.1) through the use of Terminal Emulator. I first tried installing the .apk from my File Manager and just clicking on the icon, and clicking Install, like one would think one should be able to do. When that method failed, multiple times(kept saying "insufficient storage, please delete files through app manager") which by the way, I know for a fact I have 15.8GB of storage left on my Xoom, so this should not be the issue. I then decided to try and install through Terminal Emulator. Now one would think it would be about the same as using adb commands on a Computer, which it somewhat is I guess you could say. So I go to T.E. and type the commands to get Super User access, then cd sdcard to go into the directory, then cd download because this is where my file is located, then I type pm install ****.apk.
I get a line of command that says: a) pkg: ****.apk and then b) Failure [INSTALL_FAILED_INSUFFICIENT_STORAGE], and then the command line just goes back to my download folder directory.
I've had this issue before on my Galaxy S3, but can't remember how I ended up resolving the issue. Think I did a factory data reset/wipe, which I don't want to have to do to my Xoom. So any assistance would be much appreciated. I do understand that your device was a Galaxy ACE, but I wouldn't think it would matter as to what the device is, since it is the same install method/command for any Android device essentially. Hope someone can help out. If not, I may have to post in another Device Thread (Motorola Stingray Xoom I would assume).
Many thanks in advance, and I will click the Thank You, if any responses come through.
Click to expand...
Click to collapse
Hi DannyShane,
Not sure if this is still relevant and you are around here, since it's been a very long time and I stopped using Android
I am not an Android geek but here are my 2 cents...
You need to keep .apk file on the root of the SD CARD instead of a folder. IIRC, I had the same exact error which you had mentioned, I was trying to install .apk which was placed in a folder and it didnt work., then I had to move the .apk file to root and it worked flawlessly.
Extremely sorry for the very late response though. I use my secondary e-mail for this forum and missed replies on this thread.
@ All others who have replied, I am glad that, my little finding helped you guys.
Cheers :angel:
I have a few things to add to hsotnas answer. The insufficent space error seems to be a very generic error on android that can have various causes. Maybe there is something like this in the android source code:
PHP:
try{
installApk();
} catch (Exception ex){
output("Failure [INSTALL_FAILED_INSUFFICIENT_STORAGE]");
}
If you understand what I mean
I had this error myself a few days ago and for me it was caused by some left over files in the /data/app-lib directory. It was a self-developed application and I added a library to this directory manually. As I uninstalled the application, it wasn't removed and the reinstall failed with the above mentioned error. So make sure the directories /data/data/app.package.name/ and /data/app-lib/app.package.name/ are empty.
I tried this, to install the play store apk. But I get the error INSTALL_FAILED_INVALID_URI. What is this error refering to?
PSV_Supporter said:
I tried this, to install the play store apk. But I get the error INSTALL_FAILED_INVALID_URI. What is this error refering to?
Click to expand...
Click to collapse
Me too same thing happens when I try to install 3.apk
the command used is "pm install apps/*.apk"
Mine are backups of play store
Thankyou for this tutorial... IT WORKS.. Can't believe it.. You made my day. Thankyou :good:
I'm trying to recover an old tablet and need to install a file manager... the touch screen inst working so I thought terminal would do the job... but .APK's dont show when I go to the root of the SD card and type 'ls'
An ideas?
Thanks it works
failed on me ..
For the last two days I have been trying this Ive been getting this error... EVERYTIME! I cant see that I am doing anything wrong in cmd. No clue what to do.
No luck with moonshine either
Also, installed Ubuntu, ran distiller... Nothing. It tells me to "run distiller again and READ" BTW, all radios were off when this happened
I'm not an expert by any means. But when you downloaded adb, did you download the sdk for android? If so, go to sdk manager and make sure you have all the options under tools installed. Secondly, did you rename it to revone.2.0? I used revone.DNA, and while it took me 24+ hours, and 100s of tries, I finally got it to go through. Just to confirm, so far you have pushed adb revone to the device via the adb push revone.2.0 /data/local/tmp, then adb shell, cd /data/local/tmp, chmod 755 revone.2.0? I have found that some people have gotten success from removing -P from the command.
---------- Post added at 06:42 AM ---------- Previous post was at 06:38 AM ----------
It may work easier if you move adb to a folder in C: and title the folder something like adb_android, and move the revone file in there as well. From there, you can go to the search bar, enter cmd.exe and it will bring you in directly at C:\ adb_android.
Why don't you post this as a reply to the revone thread? We don't need a new thread every single time someone runs into an issue s-offing their phone...
So Im not entirely sure how to open the sdk manager. I unzipped the adb folder (it was the ADT package), renamed it DNA and placed it under my C:\ drive. Also, I had downloaded the updated revone (revone-0.2) and just removed the dash and have tried removing and adding the -P with identical results.. I have also done many factory resets and still the same problem. From what it seems like, my problem would be with the sdk manager?
shobon said:
Why don't you post this as a reply to the revone thread? We don't need a new thread every single time someone runs into an issue s-offing their phone...
Click to expand...
Click to collapse
Im a new member and I'm not allowed to post in that section. Ive gone through darn near every page of that thread and it seems my problem was unique. Sorry for flooding the forum, I was just looking for some help.
jenniferstough said:
I'm not an expert by any means. But when you downloaded adb, did you download the sdk for android? If so, go to sdk manager and make sure you have all the options under tools installed. Secondly, did you rename it to revone.2.0? I used revone.DNA, and while it took me 24+ hours, and 100s of tries, I finally got it to go through. Just to confirm, so far you have pushed adb revone to the device via the adb push revone.2.0 /data/local/tmp, then adb shell, cd /data/local/tmp, chmod 755 revone.2.0? I have found that some people have gotten success from removing -P from the command.
---------- Post added at 06:42 AM ---------- Previous post was at 06:38 AM ----------
It may work easier if you move adb to a folder in C: and title the folder something like adb_android, and move the revone file in there as well. From there, you can go to the search bar, enter cmd.exe and it will bring you in directly at C:\ adb_android.
Click to expand...
Click to collapse
I installed java and got the sdk manager working, everything is installed and I still cant get it to work. ugh
SpacemanJake said:
I installed java and got the sdk manager working, everything is installed and I still cant get it to work. ugh
Click to expand...
Click to collapse
Tbh it took about my tenth time. I don't know why but if you don't want to switch to linux just keep trying
Sent from my HTC6435LVW using Tapatalk 2
SpacemanJake said:
For the last two days I have been trying this Ive been getting this error... EVERYTIME! I cant see that I am doing anything wrong in cmd. No clue what to do.
Click to expand...
Click to collapse
they released an updated zip... maybe try that. mine worked first time this morning no problems
i also cannot post a reply in the regular revone section.
when i download revone-0.2.1 it is not a .zip file...its just a file that cmd wont recognize when i try to push it to the device, it says its not a recognizable file. when i download revone, do i need to move the file to the same directory as adb and fastboot or what?
yes it needs to be in same folder as adb and fastboot
munchy_cool said:
yes it needs to be in same folder as adb and fastboot
Click to expand...
Click to collapse
do i need to change it to a .exe or anything?
nopes...
one last question (which probably should've been my first)...does the DNA already have to be unlocked and/or rooted to use revone? i thought i read that it needed to have an unlocked bootloader to use this.
Got it! Although revone did not work for me at all! I tried to install ubuntu but failed due to windows 8 issue. Downloaded MintLinux 64 bit, used LinuxLive USB Creator to put my .iso on thumb drive, and boot with usb hard disk. In Mint download the 32-bit libraries, download moonshine and run. Done! No adb needed in mintlinux, reboot pc without usb drive if you didnt want to install mint. worked flawlessly.
So I bricked my Kinde Fire HDX by changing the build.prop and not fixing permissions. I have adb access but no root (I don't know why :S). Would a factory reset work? If not, how can I get to fix the build.prop or replace it with the old one? thank very much, I've been a couple hours looking for solution but I couldn't find any.
No, a factory reset would only break it further. It would remove your adb access and not fix anything. What makes you think you lost root? Have you tried "adb shell" then "su"?
Sent from my Amazon Tate using Tapatalk
r3pwn said:
No, a factory reset would only break it further. It would remove your adb access and not fix anything. What makes you think you lost root? Have you tried "adb shell" then "su"?
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
I used the HDX ToolKit v0.92 to check the root access, and it said "Please grant root on your device"
I've also tried "adb shell", and then "su", but it just returns "su" again. I am new with adb commands so I don't really know what it should show.
Thank you very much for your help
May I ask what version you were on before you bricked?
Sent from my Amazon Tate using Tapatalk
14.3.2.3.2, last update I think.
?
peter_b93 said:
14.3.2.3.2, last update I think.
Click to expand...
Click to collapse
Fixed?
jimyv said:
Fixed?
Click to expand...
Click to collapse
Nope, I couldn't find any way to get root acces again. But nevermind, my new kindle fire will be here in two days. I am surprised how well amazon costumer service works. Even though I bought my kindle in the US and now I am in Spain (not going back), they called me from the US for free, and they are paying all the shipping costs and sending it by priority shipping.
I am still interested if anyone knows how to fix it, just for fun
well
peter_b93 said:
Nope, I couldn't find any way to get root acces again. But nevermind, my new kindle fire will be here in two days. I am surprised how well amazon costumer service works. Even though I bought my kindle in the US and now I am in Spain (not going back), they called me from the US for free, and they are paying all the shipping costs and sending it by priority shipping.
I am still interested if anyone knows how to fix it, just for fun
Click to expand...
Click to collapse
It sounds like to me that you still root access you just were not mounted RW in other words it would not boot up completely so you could hit allow to the adb Shell. So you will have to mount system rw manually Try last 3 pages of this thread http://forum.xda-developers.com/showthread.php?t=2588608. He can fix you most likely if you can comprehend and follow directions.. or if ur understanding adb is fair you'll be able to probably extract your repair from the thread as is.
jimyv said:
It sounds like to me that you still root access you just were not mounted RW in other words it would not boot up completely so you could hit allow to the adb Shell. So you will have to mount system rw manually Try last 3 pages of this thread http://forum.xda-developers.com/showthread.php?t=2588608. He can fix you most likely if you can comprehend and follow directions.. or if ur understanding adb is fair you'll be able to probably extract your repair from the thread as is.
Click to expand...
Click to collapse
I've tried what it is said in the other thread. However, the problem there is that the guy cannot get his device to be recognized.
I've tried this:
adb root
adb shell
su
mount -o rw,remount /system *****- if this fails, try: mount -o remount /system
chmod 644 /system/build.prop
chown root.root /system/build.prop
reboot
But adb root gives me this error:
adbd cannot run as root in production builds
On the other hand if I skip the "adb root" step I cannot go further than "su" since I don't get the "[email protected]:/ #" line.
well
peter_b93 said:
I've tried what it is said in the other thread. However, the problem there is that the guy cannot get his device to be recognized.
I've tried this:
adb root
adb shell
su
mount -o rw,remount /system *****- if this fails, try: mount -o remount /system
chmod 644 /system/build.prop
chown root.root /system/build.prop
reboot
But adb root gives me this error:
adbd cannot run as root in production builds
On the other hand if I skip the "adb root" step I cannot go further than "su" since I don't get the "[email protected]:/ #" line.
Click to expand...
Click to collapse
Well since you do have ADB connectivity why can't you hook a bruting utility and push root ? Romaster_3.4.3.7593_Setup use as describe back in the roll back thread and the rooting thread 4 the new yes I kno wat is in chinese but this is the 1 that you must use sent you cannot install the apk install software plugin your tablet look at the upper right corner you will see an gear icon tap that then second row down second icon over "root"
jimyv said:
Well since you do have ADB connectivity why can't you hook a bruting utility and push root ? Romaster_3.4.3.7593_Setup use as describe back in the roll back thread and the rooting thread 4 the new yes I kno wat is in chinese but this is the 1 that you must use sent you cannot install the apk install software plugin your tablet look at the upper right corner you will see an gear icon tap that then second row down second icon over "root"
Click to expand...
Click to collapse
FIXED!!!!!
The chinese software worked! Thank you very much! As I first rooted with towelroot I wasn't aware that it was possible to root without booting into android! I think I won't edit the build.prop again lol.
peter_b93 said:
FIXED!!!!!
The chinese software worked! Thank you very much! As I first rooted with towelroot I wasn't aware that it was possible to root without booting into android! I think I won't edit the build.prop again lol.
Click to expand...
Click to collapse
Ok now use this http://forum.xda-developers.com/showthread.php?t=2532818 and uninstall romanager from pc...and reboot... And BTW modifying your build prop is alot easier useing build prop editing app. It takes care of permissions anyway as long as you entrys are correct..
jimyv said:
Ok now use this http://forum.xda-developers.com/showthread.php?t=2532818 and uninstall romanager from pc...and reboot... And BTW modifying your build prop is alot easier useing build prop editing app. It takes care of permissions anyway as long as you entrys are correct..
Click to expand...
Click to collapse
Good call on RomMaster. I have no idea what it is doing since I haven't had any time to look at it, but I'd figured it was an app like TR. At any rate, nicely done. :good:
sweet
GSLEON3 said:
Good call on RomMaster. I have no idea what it is doing since I haven't had any time to look at it, but I'd figured it was an app like TR. At any rate, nicely done. :good:
Click to expand...
Click to collapse
I'm not sure either that's why when I used it I was on a blacklisted unit and I kept the PC and the tablet and airplane mode at all times. Until I was certain I got all the files off of both before I let them go to Wi-Fi Chinese files that is.. But one thing I was very curious about is if you open that tool up the Chinese tool that is an you go to the same page you would hit the anchor to root to your device just below that it says fastboot I'm wondering if they have a fastboot working for also too bad nobody here know Chinese..