Related
Alright, I've been posting this all over trying to help people figure out how to do this and figured it's time to make a dedicated thread. If at any point you get an error DON'T PROCEED. See if I referenced the error you're getting and, if so, do what I suggested. If not, post your error here and I'll try to get back to you ASAP.
NOTE: This can now also be done through my appstoSD app posted on this forum!!!! It will do everything for you.
This tutorial assumes you have:
A: A micro-sd card with 2 partitions, the first must be FAT32 and the second must be ext2.
B: Your phone must have one of the apps-to-sd ROM's installed.
C: Busybox installed into the /system/xbin directory. For steps on this please reference Darkrift's thread.
Before we start, let's make sure your phone is set up to handle this. Open up the terminal emulator app(available in the market) and type:
Code:
su
busybox df -h
If /system/sd doesn't appear, something is wrong. Either your sd card isn't partitioned correctly or your phone has a ROM that doesn't have apps to sd enabled. If /system/sd does show up then you're set and can start the tutorial
NOTE: Moving the cache is highly unstable and works for some people but not for most. I don't recommend trying unless you have a good idea of how to get your phone back to a usable state if it starts boot looping.
Now, for the first step you need to copy all the apps over to the sd card. To do this type(still in the terminal emulator)(The third and fourth lines are for cache to sd only):
Code:
busybox cp -a /data/app /system/sd/
busybox cp -a /data/app-private /system/sd/
busybox cp -a /data/dalvik-cache /system/sd/
busybox cp -a /data/data /system/sd/
exit
exit
Once the terminal emulator app closes, power off your phone. Then, turn it on in recovery mode by holding down the home button and then pressing the power button. Continue holding the home button until the "T-Mobile G1" icon goes away and a menu comes up. Then press Alt-x to go to recovery terminal. Press enter and a prompt should come up with a "#". Now type(If you only want your apps on your sd card and not the caches, skip steps 6-9)
Code:
mount data
rm -rf /data/app
ln -s /system/sd/app /data/app
rm -rf /data/app-private
ln -s /system/sd/app-private /data/app-private
rm -rf /data/data
ln -s /system/sd/data /data/data
rm -rf /data/dalvik-cache
ln -s /system/sd/dalvik-cache /data/dalvik-cache
reboot
And... you're all set! Your phone might take a while at the android screen since it has to populate the apps tray. If it lasts >5-10 minutes then something likely went wrong. Make sure you did all the steps correctly and if you did try the steps in the recovery terminal section of this tutorial again. If it still doesn't work, post here and we'll try to get it sorted out. That aside, enjoy having your apps on SD card and the permanent 72-73MB available!
EDIT: forgot the app-private directory. Thanks, LucidREM!!!
Maximus is the man.
[email protected] said:
Now, for the first step you need to copy all the apps over to the sd card. To do this type(still in the terminal emulator)(The second and third lines are for cache to sd only):
Code:
busybox cp -a /data/app /system/sd/
busybox cp -a /data/dalvik-cache /system/sd/
busybox cp -a /data/data /system/sd/
exit
exit
Once the terminal emulator app closes, power off your phone. Then, turn it on in recovery mode by holding down the home button and then pressing the power button. Continue holding the home button until the "T-Mobile G1" icon goes away and a menu comes up. Then press Alt-x to go to recovery terminal. Press enter and a prompt should come up with a "#". Now type(If you only want your apps on your sd card and not the caches, skip steps 4-7)
Code:
mount data
rm -rf /data/app
ln -s /system/sd/app /data/app
rm -rf /data/data
ln -s /system/sd/data /data/data
rm -rf /data/dalvik-cache
ln -s /system/sd/dalvik-cache /data/dalvik-cache
reboot
Click to expand...
Click to collapse
i see a missing step here .. what about /data/app-private
LucidREM said:
i see a missing step here .. what about /data/app-private
Click to expand...
Click to collapse
RIGHT! I keep forgetting that one cause that folder pisses me off and I move all the apps there to the normal app folder lol. Will fix in 5, 4, 3...
EDIT: 2,1,0
cp: cannot stat '/data/davlik-cache': no such file or directory
whats up?
NEVERMIND. i need to go back to spelling class.
I'm sure its been asked and answered but I'll ask again! I understand it can take quite a few minutes to boot but is this every time you reboot or just the first time?
Thanks
DynaMight said:
I'm sure its been asked and answered but I'll ask again! I understand it can take quite a few minutes to boot but is this every time you reboot or just the first time?
Thanks
Click to expand...
Click to collapse
just the first time. its moving all the apps and cache from phone to sd card during that first reboot.
won't that slow down the phone even more?
the first time takes much longer. Subsequent reboots are of normal duration, comparable to the standard build.
Smokuevo said:
won't that slow down the phone even more?
Click to expand...
Click to collapse
if you use a class six sdcard, the apps will load faster. i believe that class 6 flash media is faster than the phones flash.
stogchris81 said:
if you use a class six sdcard, the apps will load faster. i believe that class 6 flash media is faster than the phones flash.
Click to expand...
Click to collapse
Pushing (writing) a 2MB file through adp push seems a bit faster to the SDCARD compared to the internal memory.
-> rough average for SDCARD : 1200 KB/s
-> rough average for system storage : 1000 KB/s
Regarding pulling (reading), internal seems faster :
-> rough average for SDCARD : 1247 KB/s
-> rough average for system storage : 1250 KB/s
These tests are everything but serious.. This is using the famous SanDisk 8GB Mobile Ultra (class 6).
To conclude I'd say that speed is almost the same, sometimes a bit faster for SDCARD.
i have one question
i tried to read through the thread but it was waay to large and long
if u do install apps to the sd card
when u install a newer rom on it does that mean the apps are automatically installed once again? i would like to do this because haykuro's roms are released once a week and i dont like reinstalling apps over and over again...
bigballa said:
i have one question
i tried to read through the thread but it was waay to large and long
if u do install apps to the sd card
when u install a newer rom on it does that mean the apps are automatically installed once again? i would like to do this because haykuro's roms are released once a week and i dont like reinstalling apps over and over again...
Click to expand...
Click to collapse
Unfortunately the answer is "sorta". The apps will still be on your sd card in the same places you put them. BUT all the symlinks will be gone so it'll look like they all dissapeared. You'll have to repeat the recovery terminal part of the tutorial, but all the stuff before it will be unnecessary.
i keep getting /system/sd/app is not a directory but when i run mkdir /system/sd/app it says that the file already exists.
the one time i got adb to work i did the steps through it to get apps to sd but the i had to wipe my phone. do i have to do the steps in the first post or recreate the symlinks?
wizern23 said:
i keep getting /system/sd/app is not a directory but when i run mkdir /system/sd/app it says that the file already exists.
the one time i got adb to work i did the steps through it to get apps to sd but the i had to wipe my phone. do i have to do the steps in the first post or recreate the symlinks?
Click to expand...
Click to collapse
In terminal emulator do this:
Code:
su
cd /system/sd
ls -l[CODE]
And put what it says on the line with "app" in it here. If it says "app ->" and has something after the arrow(my guess would be /data/app) then you put the symlink the wrong way. Make sure you do ln -s /system/sd/app /data/app, not the other way around. Let me know what your results are
[email protected] said:
In terminal emulator do this:
Code:
su
cd /system/sd
ls -l[CODE]
And put what it says on the line with "app" in it here. If it says "app ->" and has something after the arrow(my guess would be /data/app) then you put the symlink the wrong way. Make sure you do ln -s /system/sd/app /data/app, not the other way around. Let me know what your results are[/QUOTE]
huh? can you repeat that because i didnt understand what you were saying
im at the first step anyway. and thats when it says /system/sd/app is not a directory. my other question is is do i have to use
rm -rf /data/app
rm -rf /data/dalvik-cache
rm -rf /data/app-private
to re-establish the symlinks or did the steps through adb i used get erased when i wiped it.
Click to expand...
Click to collapse
[email protected] said:
In terminal emulator do this:
Code:
su
cd /system/sd
ls -l[CODE]
And put what it says on the line with "app" in it here. If it says "app ->" and has something after the arrow(my guess would be /data/app) then you put the symlink the wrong way. Make sure you do ln -s /system/sd/app /data/app, not the other way around. Let me know what your results are[/QUOTE]
i had the same problem. it said /system/sd/app is not a directory even though it already existed. when i used your code above this was my result:
drwx----- root root 2009-04-12 20:11 lost+found
-rw-r--r-- system system 29303 2009-04-11 11:56 app
Click to expand...
Click to collapse
wizern23 said:
huh? can you repeat that because i didnt understand what you were saying
im at the first step anyway. and thats when it says /system/sd/app is not a directory. my other question is is do i have to use
rm -rf /data/app
rm -rf /data/dalvik-cache
rm -rf /data/app-private
to re-establish the symlinks or did the steps through adb i used get erased when i wiped it.
Click to expand...
Click to collapse
Umm I wouldn't proceed cause if /system/sd/app isn't a directory then you're gonna have lots of problems. I need to know what it says after you type
Code:
su
cd /system/sd/
ln -s
Specifically, there'll be a line of output that has the word "app" towards/at the end. I need to know what's in that line. If the line doesn't start with a 'd' then app isn't a directory and something happened and you need to remove /system/sd/app by typing this in the terminal emulator:
Code:
su
busybox rm -rf /system/sd/app
and then restart the process from the beginning.
it says that /system/sd/app is not a directory but when i do mkdir /system/sd/app it says the file already exists.
the line with app in it says
-rw-r--r-- system system 29303 2009-04-14 17:27 app.
okay removing that made it work.
[edit] Thank you so much. it finally worked. i now have 73mb free on the phone.
glad I could help. On a side note Apps to SD app is now live
Now that we have root access I was trying to figure out the cause of the "old apps keep reappearing after an update and restart bug."
From the looks of it it seems the /data/boot-cache directory is corrupt. I tried my experiment with Google Sky Map and got the following:
Code:
$ adb shell
$ su
# cd /data/boot-cache
# ls -al *stardroid*
-rw------- system system 3988 2009-10-17 18:36 AndroidManifest.xml
# rm -rf *stardroid*
rm failed for -rf, No such file or directory
# rmdir *stardroid*
rmdir failed for [email protected]@com.google.android.stardroid.apk, Directory not empty
# fsck
fsck: not found
Same thing happens with all the other apps that misbehave when updated.
Do we have any way of running fsck or some other file system repair utility to fix these issues?
Code:
# rm -rf *stardroid*
rm failed for -rf, No such file or directory
# rmdir *stardroid*
rmdir failed for [email protected]@com.google.android.stardroid.apk, Directory not empty
Do we have any way of running fsck or some other file system repair utility to fix these issues?
Click to expand...
Click to collapse
Or you could just empty the directory before you tried to remove it, since whatever 'rm' binary is provided apparently doesn't understand "-rf" and treated it as a filename.
posguy99 said:
Or you could just empty the directory before you tried to remove it, since whatever 'rf' binary is provided apparently doesn't understand "-rf" and treated it as a filename.
Click to expand...
Click to collapse
Seems it doesn't know -rf but works with -r. Let me see if this now fixes the issues.
Keep up the good work man I had this problem multiple times I think it bothered me more than not receiving sms or vvm.
The fix
That is it, you use -r not -rf. So the fix is as follows (I use Astro for getting the following information):
1) Use Astro and backup all your apps to your SD card.
2) The Astro Application Manager/Backup tool will list in red all the apps that it thinks are newer on the SD card than the phone thinks are installed.
3) For each of those apps select them and note the app installed name (first line, called "Name"). Usually com.xxx.xxx, etc.
4) Get a root shell to your phone (follow instructions elsewhere.)
5) cd /data/boot-cache
6) For all the names you generated in step 3 type
Code:
rm -r *<name>*
e.g. taking Google Sky Map as an example this would be
Code:
rm -r *com.google.android.stardroid*
7) Reboot your phone.
8) All apps should now appear in their latest, correct, version.
Google claims this problem is specific to the Hero and SenseUI. Does this cache folder exist on a normal Android build?
is there a chance someone can make an app that would automate this process?
does the issue come back after awhile?
goku14238 said:
does the issue come back after awhile?
Click to expand...
Click to collapse
Anytime you update an app you will see the issue for that app.
This works great. I used it to fix my Handcent which messed up after I upgraded today.
+1 on this. You guys are really killing this phone.
Hey guys,
My uncle works for Motorola and gave me a prototype phone (which I believe will be called the Motorola Sage, and it's model number is MB508. This thread isn't really about that, I can't post pictures because I don't want to get anyone in trouble). This phone is an AT&T phone, complete with AT&T startup screen, uninstallable AT&T apps and of course the inability to install non-market apps. Also it's running Android 2.1.
Now, I seem to have default root access to this phone. I'm assuming the file system is very similar to that of the Backflip (which I was previously using until I received this one). From what I've read and learned from poking around in /system/etc, non-market apps are blocked by two config files. These are:
/system/etc/motorola/com.android.providers.settings/secure.mkitso
Code:
# cat secure.mkitso
cat secure.mkitso
location_providers_allowed=network,gps
wifi_on=0
data_roaming=1
bluetooth_on=0
install_non_market_apps=0
usb_mass_storage_enabled=1
and
/system/etc/motorola/com.motorola.android.providers.settings/settings.mkitso
Code:
# cat settings.mkitso
cat settings.mkitso
mms_maximum_message_size=614400
auto_scan_on_flip=true
sms_pref_key_emailgateway_num=121
Single_Digit_Dial_Enabled=True
roaming_icon=0
dun_enable=1
force_only_market_apps=1
Bluetooth_Dun_Enabled=true
mms_x_wap_profile_url=http://uaprof.motorola.com/phoneconfi/MotoMB51/profile/MotoMB511.rdf
sms_pref_key_to_email=1
Okay, now it would seem that it's a simple matter of changing the values for "force_only_market_apps" to 0, and "install_non_market_apps" to 1. I did this, and let me quickly tell you how I did it.
- Make /system writable: mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
- Copy mkitso files to sdcard
- Edit mkitso files using Notepad++, changing the values as stated above
- Copy mkitso files back to their original directories
- chmod 644 to the files in order to keep their original permissions
- Make /system read only again: mount -o remount,ro -t yaffs2 /dev/block/mtdblock4 /system
- Restart the phone
However, this did not work, as I still get the warning when I try to install a non-market app.
I was wondering if anyone had any ideas on this, as when the Backflip gets rooted this is one thing that I'm sure we would like to know.
Have you tried adb install? I've heard that works on Backflops. You could download the app to your PC,and install it using "adb install PATH/TO/APP.APK"
Thanks, I know that I can use adb to install non market apps, but I was looking at how to change this setting on the phone. Since I have root on my phone, I figured it was possible.
Check out some of these terminal apps found in /system/bin/ directory of the backflip.Maybe they will help you.
Code:
modemlog
chown
check_prereq
dumpsys
qmuxd
rild
dd
port_bridge
installd
minipadut
vmstat
vold
ioctl
mm-audio-native-test
lsmod
id
mm-adec-omxamr-test
notify
getevent
hciattach
dhcpcd
service
cat
system_server
linker
mm-vdec-omxh264-test
mm-adec-omxevrc-test
wpa_supplicant
netstat
mm-adec-omxmp3-test
ls
wipe
iwpriv
stop
log
mm-vdec-omxmp4-test
top
bt_init
app_process
kill
dumpcrash
iwspy
tcmd_engine
sleep
port-bridge
input
chmod
flash_image
wfa_dut
monkey
dmesg
umount
dalvikvm
sh
sync
ptf
mm-jpeg-dec-test
ime
diag_klog
route
ln
batch
fuel_gauge
iwlist
bugreport
insmod
hcid
svc
rmmod
servicemanager
iwgetid
debuggerd
test_diag
am
renice
applypatch
ps
watchprops
sendevent
reboot
mount
mm-adec-omxQcelp13-test
pm
start
ping
busybox
toolbox
df
touchpad
mediaserver
setconsole
loc_api_app
setprop
logwrapper
rm
dvz
hd
ifconfig
rmdir
printenv
getprop
mm-venc-omx-test
fsck_msdos
iwconfig
iftop
bt_downloader
akmd2
sdptool
disp_util
mm-aenc-omxamr-test
newfs_msdos
gzip
cmp
iwevent
mv
smd
mmclog
mknod
mm-adspsvc-test
bt_test_exec
dexopt
date
set_grp_id
i2c
tcmd_sql
recovery
dumpstate
netcfg
surfaceflinger
mkdir
dbus-daemon
mm-adec-omxaac-test
schedtest
mm-jpeg-enc-test
logcat
mm-aenc-omxaac-test
schedtop
fmradio
EDIT:Also there does not seem to be a com.android.providers.settings in /system/etc/motorola/ only com.motorola.android.providers.settings and the file located in that directory is named secure.mkitso and the market app setting is set up like this:install_non_market_apps=0
So there is a slight difference in how the devices are set up and maybe a bit less security on the backflip =)
Thanks for your suggestion, but if you read above I changed the mkitso files without any changes in the behavior of the phone .
I was thinking that since I changed the settings files and they didn't do anything, maybe they will be applied during a hard reset. I'll try that sometime this weekend and report on the results.
The reason I'm asking for help is because I believe that once the Backflip gets rooted, we will need to know how to disable this setting.
I doubt you have root unless it came already rooted (you did make up some **** about a prototype) I honestly think this wont be a hard issue to tackle or work around when root is achieved on the Lackflip...yes I did Lackflip on purpose because of how crippled it is..so spend your time ANNONYMOUSLY sending www.endgadget.com some nice shiney pics of your supposed prototype codnamed:
"Motorola Sage"
I'm not sure why you're so aggressive, Honestly77. I'm able to "su" in shell and I'm able to modify files in the /system folder, so unless I'm mistaken (which I very well might be), then I believe I have root on the phone.
It is a prototype phone for testing, so it coming rooted isn't too farfetched at all.
When the Backflip does get rooted yes, this will be an easier issue to solve, but I'm trying now. If we're able to figure it out now then no time will have to be devoted to it when the Backflip is rooted.
Alright, I just did a hard reset and it activated a menu toggle under Settings -> Applications -> "Unknown Sources: Allow install of non-Market applications" which can be checked or unchecked.
To summarize, if you have root on your phone, edit secure.mkitso and settings.mkitso and change the variables, then you need to hard reset the phone.
hey met3ora, I too have a backflop, I am currently trying to sell my soul to obtain some sort of root or even simple control over the device, I have 2 questions for you...
1: using the config files and other software availible on this forum, would it be possible to obtain a workaround to be able to install apps from sd? I'm sure you are well aware that the backflip has no memory and won't even allow market apps to be installed via sd.
my second question (its ok if you don't want to answer as we will find out soon enough)
is: the moto sage, how does it compare to the backflip? no specifics needed just, is it better?
Iv'e seen the photos of the sage that appeared a couple weeks ago and it looks good, just incase we need it you should copy the system files as I'm sure the one AT&T will give us will be on lockdown as well. Thanks!
Honestly77 said:
I doubt you have root unless it came already rooted (you did make up some **** about a prototype) I honestly think this wont be a hard issue to tackle or work around when root is achieved on the Lackflip...yes I did Lackflip on purpose because of how crippled it is..so spend your time ANNONYMOUSLY sending www.endgadget.com some nice shiney pics of your supposed prototype codnamed:
"Motorola Sage"
Click to expand...
Click to collapse
THis thread is old but it still helped me with a bravo. Thanks OP.
And to this guy above, wtf, why be such a douche? You are also clearly an idiot or you would know that engineering models always have root.
Calling the OP a liar was way out of line and you should apologize.
Ok, so a friend of mine bought 3 of these things from Kohls on Black Friday as Christmas presents for her kids and has asked me to help set them up as kid friendly devices. Unfortunately they don't come with any Gapps installed and I'm having difficulty installing any of them including the Play Store. I'm also running into problems installing simple games like Angry Birds. In fact very few of the APK's that I have backed up from my other Android devices seem to want to install on these tablets. I also can't find any forums on here or anywhere else evening addressing these devices yet. I'm wondering if there's some kind of generic udate.zip I can use for these things that isn't device specific? A little while back I was able to install an update.zip on a Zeki tablet that enabled me to finally install all the Gapps and maximize it's potential. But then again those things come rooted out of the box and the update was Zeki specific, so...
Anyways, please if anyone can help? This could be your chance to be the first to help unlock the potential of these devices.
Rooting PTAB8000
This is NOT my work, it is from mbellot at FreakTab, but it worked great for me.
Rooting is easy, market is nearly as easy. Here is the original thought process.
Here it is, modified the way I have done it (a couple times), broken into logical chunks.
1. C:\ADB> adb shell
2. [email protected]:/ $ mv /data/local/tmp /data/local/tmp.bak
3. [email protected]:/ $ ln -s /data /data/local/tmp
4. [email protected]:/ $ exit
5. C:\ADB> adb reboot
This gives you write access to /data for the next set of steps.
6. C:\ADB> adb wait-for-device
7. C:\ADB> adb shell
8. [email protected]:/ $ echo ro.kernel.qemu=1 >/data/local.prop
9. [email protected]:/ $ exit
10. C:\ADB> adb reboot
This puts you into a "debug" mode of sorts, the LCD will be black after the boot logo comes and goes.
11. C:\ADB> adb wait-for-device
12. C:\ADB> adb remount
remount succeeded
13. C:\ADB> adb push su /system/bin/su
518 KB/s (22364 bytes in 0.042s)
14. C:\ADB> adb shell
15. [email protected]:/ # chown root.shell /system/bin/su
16. [email protected]:/ # chmod 06755 /system/bin/su
17. [email protected]:/ # rm /system/xbin/su
rm failed for /system/xbin/su, No such file or directory
18. 255|[email protected]:/ # ln -s /system/bin/su /system/xbin/su
19. [email protected]:/ # exit
The chown and chmod in steps 15 and 16 are critical to su working properly.
20. C:\ADB> adb push Superuser.apk /system/app/.
3923 KB/s (843503 bytes in 0.209s)
At this point you can install market files. You need to do it before you remove the local.prop file since the PTAB8000 refuses to run adb in root mode or allow remounting. You can use this as a starting point for installing market, but I would suggest you grab the latest ICS gapps and replace the files. Also, market/play is not vending.apk in ICS, its phonesky.apk.
Once you're done with su and market you need to make your tablet boot normal again.
21. C:\ADB> adb shell
22. [email protected]:/ # rm /data/local.prop
23. [email protected]:/ # rm /data/local/tmp
24. [email protected]:/ # mv /data/local/tmp.bak /data/local/tmp
25. [email protected]:/ # exit
26. C:\ADB> adb reboot
Finished.
Thanks.
HD Brian said:
This is NOT my work, it is from mbellot at FreakTab, but it worked great for me.
Rooting is easy, market is nearly as easy. Here is the original thought process.
Here it is, modified the way I have done it (a couple times), broken into logical chunks.
1. C:\ADB> adb shell
2. [email protected]:/ $ mv /data/local/tmp /data/local/tmp.bak
3. [email protected]:/ $ ln -s /data /data/local/tmp
4. [email protected]:/ $ exit
5. C:\ADB> adb reboot
This gives you write access to /data for the next set of steps.
6. C:\ADB> adb wait-for-device
7. C:\ADB> adb shell
8. [email protected]:/ $ echo ro.kernel.qemu=1 >/data/local.prop
9. [email protected]:/ $ exit
10. C:\ADB> adb reboot
This puts you into a "debug" mode of sorts, the LCD will be black after the boot logo comes and goes.
11. C:\ADB> adb wait-for-device
12. C:\ADB> adb remount
remount succeeded
13. C:\ADB> adb push su /system/bin/su
518 KB/s (22364 bytes in 0.042s)
14. C:\ADB> adb shell
15. [email protected]:/ # chown root.shell /system/bin/su
16. [email protected]:/ # chmod 06755 /system/bin/su
17. [email protected]:/ # rm /system/xbin/su
rm failed for /system/xbin/su, No such file or directory
18. 255|[email protected]:/ # ln -s /system/bin/su /system/xbin/su
19. [email protected]:/ # exit
The chown and chmod in steps 15 and 16 are critical to su working properly.
20. C:\ADB> adb push Superuser.apk /system/app/.
3923 KB/s (843503 bytes in 0.209s)
At this point you can install market files. You need to do it before you remove the local.prop file since the PTAB8000 refuses to run adb in root mode or allow remounting. You can use this as a starting point for installing market, but I would suggest you grab the latest ICS gapps and replace the files. Also, market/play is not vending.apk in ICS, its phonesky.apk.
Once you're done with su and market you need to make your tablet boot normal again.
21. C:\ADB> adb shell
22. [email protected]:/ # rm /data/local.prop
23. [email protected]:/ # rm /data/local/tmp
24. [email protected]:/ # mv /data/local/tmp.bak /data/local/tmp
25. [email protected]:/ # exit
26. C:\ADB> adb reboot
Finished.
Click to expand...
Click to collapse
HD Brian,
I'm going to say thanks because I'm sure everything you just posted is probably going to be very clear to quite a few people that understand all of that. So thank you for helping out. Unfortunately though for me, I got lost. Though I've been tinkering with android and windows mobile devices for about 3 years now, I've actually never done any ADB editing and not sure I fully understand how to do it.
Personally I'm not too concerned about modifying these things too much because they are for someone else's kids, and I've found a way to work around rooting and using Gapps to be able to install the apps they're needing. And before I hand these things back over to be wrapped for Christmas I'm going to make a video showing what I've done to maximize the out of box potential of these things.
But on that note, I'm going to make a request of you if you don't mind. Considering you seem to know how to easily achieve the task, I was wondering if you'd be willing to make and post a Youtube video that takes people through the steps. I know it might be time consuming, but after all we are all here to help each other out. And I'm sure that the people who actually own these devices would really appreciate it. At this point I haven't been able to find any videos on how to mod this tablet yet and the only forums that I've found discussing these things are the one you mentioned and this one here.
So I hope you'll be willing to help other owners out, and I appreciate you taking the time to respond.
Thanks
I had been thinking about reloading the stock rom and doing the root all again as a refresher for myself, but I have never done a YouTube video before. I will try to find the time to do it and them I will post the link here.
For anyone still having issues with rooting and getting the play store on this device I have just made a script to automate the whole process.
filedropper [dot] com / polaroidaio
Note ADB drivers are required.
TeODH4 said:
For anyone still having issues with rooting and getting the play store on this device I have just made a script to automate the whole process.
filedropper [dot] com / polaroidaio
Note ADB drivers are required.
Click to expand...
Click to collapse
Thanks! I was able to run this script, it read the tablet, I asked it to root and install gapps, it said it completed but when the device restarts, I see the polaroid logo twice, then the screen goes black and just sits there forever. I was able to re-install factory and boot it back up so that was good. But didn't know if you had any ideas on what was wrong with my device. I'm using a brand new stock Polaroid PTAB8000 ICS 4.0.3. Windows 7, freshly installed Android Development Kit from today to get my ADB.
smokethrower2 said:
Thanks! I was able to run this script, it read the tablet, I asked it to root and install gapps, it said it completed but when the device restarts, I see the polaroid logo twice, then the screen goes black and just sits there forever. I was able to re-install factory and boot it back up so that was good. But didn't know if you had any ideas on what was wrong with my device. I'm using a brand new stock Polaroid PTAB8000 ICS 4.0.3. Windows 7, freshly installed Android Development Kit from today to get my ADB.
Click to expand...
Click to collapse
Any luck with this script yet? Also, how were you able to flash back to factory?
Wanted to add, got the same black screen so I booted to recovery and did factory reset which got me back to square 1. I install the getjar app store and did a search for gmail. when it came up i downloaded it, and during the installation it also installed the "Google Play" store. I was getting a few errors but after turning sync on and using the store for a bit they all cleared up so far. Now I have google play and gmail apps on the tab.
BigT504 said:
Wanted to add, got the same black screen so I booted to recovery and did factory reset which got me back to square 1. I install the getjar app store and did a search for gmail. when it came up i downloaded it, and during the installation it also installed the "Google Play" store. I was getting a few errors but after turning sync on and using the store for a bit they all cleared up so far. Now I have google play and gmail apps on the tab.
Click to expand...
Click to collapse
Sorry about the black screen issue guys there was an issue with the code. I've also completely rewritten the application in c++. All features should work without issues now.
You can download the software here: mediafire [dot] com/?o2864kb92hcc0hb (sorry i can't post links yet, I'll work on getting some posts done...)
1) Download RAR file
2) Extract RAR file
3) Run PolaroidAIO.exe
4) Enable USB debugging and Stay awake
5) Drivers are included in this release if needed
6) Enjoy your fully rooted tablet with the Play Store and Google Services Framework.
If anyone is intrested in the source code let me know and I will post it as well...
Have fun guys!
---------- Post added at 09:58 AM ---------- Previous post was at 09:26 AM ----------
smokethrower2 said:
Thanks! I was able to run this script, it read the tablet, I asked it to root and install gapps, it said it completed but when the device restarts, I see the polaroid logo twice, then the screen goes black and just sits there forever. I was able to re-install factory and boot it back up so that was good. But didn't know if you had any ideas on what was wrong with my device. I'm using a brand new stock Polaroid PTAB8000 ICS 4.0.3. Windows 7, freshly installed Android Development Kit from today to get my ADB.
Click to expand...
Click to collapse
There was a bug in the old code, same thing happend to mine after i did a factory reset to try and replicate your situation. Try the updated version 1.2 and let me know if u face any simular issues.
---------- Post added at 10:14 AM ---------- Previous post was at 09:58 AM ----------
Dossey said:
HD Brian,
I'm going to say thanks because I'm sure everything you just posted is probably going to be very clear to quite a few people that understand all of that. So thank you for helping out. Unfortunately though for me, I got lost. Though I've been tinkering with android and windows mobile devices for about 3 years now, I've actually never done any ADB editing and not sure I fully understand how to do it.
Personally I'm not too concerned about modifying these things too much because they are for someone else's kids, and I've found a way to work around rooting and using Gapps to be able to install the apps they're needing. And before I hand these things back over to be wrapped for Christmas I'm going to make a video showing what I've done to maximize the out of box potential of these things.
But on that note, I'm going to make a request of you if you don't mind. Considering you seem to know how to easily achieve the task, I was wondering if you'd be willing to make and post a Youtube video that takes people through the steps. I know it might be time consuming, but after all we are all here to help each other out. And I'm sure that the people who actually own these devices would really appreciate it. At this point I haven't been able to find any videos on how to mod this tablet yet and the only forums that I've found discussing these things are the one you mentioned and this one here.
So I hope you'll be willing to help other owners out, and I appreciate you taking the time to respond.
Thanks
Click to expand...
Click to collapse
Hey I just wanted to point out that you can indeed use root and remount /system. if you have proper root. which my AIO application will test for you as well. Here's what you do to remount /system as r/w:
Code:
C:\dev\adb>adb shell
[email protected]:/ $ su
su
[email protected]:/ # mount -o remount,rw /system
mount -o remount,rw /system
[email protected]:/ # chmod 777 /system
chmod 777 /system
[email protected]:/ # chmod 777 /system/app
chmod 777 /system/app
[email protected]:/ # exit
exit
[email protected]:/ $ exit
exit
C:\dev\adb>adb push sample.apk /system
/app/sample.apk
12 KB/s (187 bytes in 0.015s)
C:\dev\adb>adb shell
[email protected]:/ $ su
su
[email protected]:/ # chmod 755 /system/app
chmod 755 /system/app
[email protected]:/ # chmod 755 /system
chmod 755 /system
[email protected]:/ # mount -o remount,ro /system
mount -o remount,ro /system
[email protected]:/ #
I was able to get the play store on with the first upload and then by following a couple of steps from aother tutorial, but I can't seem to get any apps in the Play Store to open or download. I keep getting a "device is not compatible" message. I've tried the DPI play store and also messed around with LCD Density Monitor but haven't had any luck. If someone could help tackle this problem as well as get netflix up and running, I would be extremely grateful. This seems like a pretty awesome tablet, it just needs to be let free.
I feel I should also add, for anyone considering doing this, that once you have the Play Store installed, at least in my experience; if you have it hooked up to a PC via the USB and try to install anything, it goes ape sh** and starts trying to force close and kicks a whole bunch of errors. It doesn't seen to do anything, but it's annoying as hell. I haven't tried it yet with it plugged into the charger, and it doesn't do it nearly as much when you have it unplugged, but it's just another one of those quirks that I'm sure will be fixed in due time.
TeODH4 said:
Sorry about the black screen issue guys there was an issue with the code. I've also completely rewritten the application in c++. All features should work without issues now.
You can download the software here: mediafire [dot] com/?o2864kb92hcc0hb (sorry i can't post links yet, I'll work on getting some posts done...)
1) Download RAR file
2) Extract RAR file
3) Run PolaroidAIO.exe
4) Enable USB debugging and Stay awake
5) Drivers are included in this release if needed
6) Enjoy your fully rooted tablet with the Play Store and Google Services Framework.
If anyone is intrested in the source code let me know and I will post it as well...
Have fun guys!
---------- Post added at 09:58 AM ---------- Previous post was at 09:26 AM ----------
There was a bug in the old code, same thing happend to mine after i did a factory reset to try and replicate your situation. Try the updated version 1.2 and let me know if u face any simular issues.
---------- Post added at 10:14 AM ---------- Previous post was at 09:58 AM ----------
Hey I just wanted to point out that you can indeed use root and remount /system. if you have proper root. which my AIO application will test for you as well. Here's what you do to remount /system as r/w:
Code:
C:\dev\adb>adb shell
[email protected]:/ $ su
su
[email protected]:/ # mount -o remount,rw /system
mount -o remount,rw /system
[email protected]:/ # chmod 777 /system
chmod 777 /system
[email protected]:/ # chmod 777 /system/app
chmod 777 /system/app
[email protected]:/ # exit
exit
[email protected]:/ $ exit
exit
C:\dev\adb>adb push sample.apk /system
/app/sample.apk
12 KB/s (187 bytes in 0.015s)
C:\dev\adb>adb shell
[email protected]:/ $ su
su
[email protected]:/ # chmod 755 /system/app
chmod 755 /system/app
[email protected]:/ # chmod 755 /system
chmod 755 /system
[email protected]:/ # mount -o remount,ro /system
mount -o remount,ro /system
[email protected]:/ #
Click to expand...
Click to collapse
Just to be sure you may want to run the updated script because there was alot of garbage left behind by 1.0. which 1.2 will clean up.
1) Select "Remove Google Applications and Framework"
2) When done, select "Un-Root Device"
3) Finally select "Root Device and Install Google Applications, and Framework"
This will clean up the garbage left behind by 1.0 and might help with some of your issues.
I am aware that some apps are showing up as un-supported, I'm pretty sure its an issue with build.prop. I'm looking into it right now. Are you having issues with all the apps on the play store? or just some of them like netflix, angry birds, etc? Also can you elaborate on what errors you are getting? I think i need to find an updated version of google services framework, I've noticed when the market upgrades to the play store it will crash quite a few times during the updates, and then gets better but does crash from time to time. Don't hurt functionality but it is very annoying.
If you find any info on any of this please be sure to share. I'll try and get an updated release out tonight that takes care of at least some of these issues... At least we are making progress...
I downloaded the files from location listed above but it my anti virus primped me for a Trojan virus... Is this not a secure release?
psctornado said:
I downloaded the files from location listed above but it my anti virus primped me for a Trojan virus... Is this not a secure release?
Click to expand...
Click to collapse
This is a secure release, it probably doesn't like all the files embedded into the exe... I can re-upload it un-packed if you like.
No it's ok I thought I would ask. So the big issue is the play store?
psctornado said:
No it's ok I thought I would ask. So the big issue is the play store?
Click to expand...
Click to collapse
Yes, the protected applications do not show up, or if you try to use the web site, and send an app to your device it will say unsupported, I'm going to take a look at my build.prop in a little bit and see if i cant get the full market working. From what I can tell its google blocking the apps because this is a non google supported device. which is why we needed to load the play store in the first place, if you run AIO 1.2 you will at least get all Googles app's working... Gmail, etc. I will have an update out soon to fix the play store issues, and hopefully fix the crashing gapps service...
Okay. I don't have the tablet with me right now, but when I do, I'll redo everything. Also, I was able to get Netflix to work by downloading it from Amazon's App store and everything "seemed" to work. I'll have to try more testing when I get the tablet back. As far as the Play store goes, it just says that it has stopped working and has to close, and when I hit okay, the error goes away but it stays open. I'll get the exact verbatim when it pops up again. Other than that, nice work and hopefully we can work out the kinks.
TeODH4 said:
Just to be sure you may want to run the updated script because there was alot of garbage left behind by 1.0. which 1.2 will clean up.
1) Select "Remove Google Applications and Framework"
2) When done, select "Un-Root Device"
3) Finally select "Root Device and Install Google Applications, and Framework"
This will clean up the garbage left behind by 1.0 and might help with some of your issues.
I am aware that some apps are showing up as un-supported, I'm pretty sure its an issue with build.prop. I'm looking into it right now. Are you having issues with all the apps on the play store? or just some of them like netflix, angry birds, etc? Also can you elaborate on what errors you are getting? I think i need to find an updated version of google services framework, I've noticed when the market upgrades to the play store it will crash quite a few times during the updates, and then gets better but does crash from time to time. Don't hurt functionality but it is very annoying.
If you find any info on any of this please be sure to share. I'll try and get an updated release out tonight that takes care of at least some of these issues... At least we are making progress...
Click to expand...
Click to collapse
rysimpson318 said:
Okay. I don't have the tablet with me right now, but when I do, I'll redo everything. Also, I was able to get Netflix to work by downloading it from Amazon's App store and everything "seemed" to work. I'll have to try more testing when I get the tablet back. As far as the Play store goes, it just says that it has stopped working and has to close, and when I hit okay, the error goes away but it stays open. I'll get the exact verbatim when it pops up again. Other than that, nice work and hopefully we can work out the kinks.
Click to expand...
Click to collapse
If the play store is just crashing then i would most definitely recommend using 1.2 to clean things up and reload the playstore, you may even want to go as far as to do a factory reset after you un-install and un-root... Well for some reason build.prop doesn't seem to change anything on the market, I'm downloading an updated gapp for 4.0.3 maybe that will take care of some issues under the hood.
TeODH4 said:
If the play store is just crashing then i would most definitely recommend using 1.2 to clean things up and reload the playstore, you may even want to go as far as to do a factory reset after you un-install and un-root... Well for some reason build.prop doesn't seem to change anything on the market, I'm downloading an updated gapp for 4.0.3 maybe that will take care of some issues under the hood.
Click to expand...
Click to collapse
So are you saying a clean install will remedy the issue?what is the 1.2 download link?
psctornado said:
So are you saying a clean install will remedy the issue?what is the 1.2 download link?
Click to expand...
Click to collapse
Sorry for the late response, but it should fix some of the issues. See the thread below for more info on current bugs...
I will now be posting all project updates and downloads here: http://forum.xda-developers.com/showthread.php?t=2066041
BigT504 said:
Any luck with this script yet? Also, how were you able to flash back to factory?
Click to expand...
Click to collapse
I haven't tried the new version yet since I don't have my laptop with me right now but I'll try it later. To reset back to factory after getting stuck on the black screen follow this sites direction. You will need a micro SD card. southerntelecom dot com / polaroidsupport / firmware /firmware_guide_ptab8000 dot html then download the files for your model and then put them on the SD card and insert the SD card in the tablet. Then to start the factory reset hold down volume down and power at the same time until you see the update screen come up. I believe that is what it said. It should explain it all in the link. If my link won't post since I'm new just Google ptab8000 firmware and click on the link for a southerntelecom firmware site.
I created a gemlog post (http proxy version) listing my current root persistence steps, but figured I'd post here the steps I use to disable the updater.
Most of the core filesystems are read-only and integrity checked, so directly modifying scripts isn't easy. Fortunately the `start-devmode.sh` runs pretty early.
The `/etc/init/update.conf` checks if the `/usr/sbin/update` file exists. If it doesn't then it continues normally. To delete this file I mount an overlayfs over the existing `/usr/sbin/` and delete/whiteout the update file. My steps are:
Bash:
mkdir /tmp/rmupdate
mkdir /tmp/rmupdate/upper
mkdir /tmp/rmupdate/work
mount -t overlay -o lowerdir=/usr/sbin/,upperdir=/tmp/rmupdate/upper/,workdir=/tmp/rmupdate/work/ overlay-rm /usr/sbin/
rm /usr/sbin/update
mount -o remount,ro /usr/sbin
If you want to do something similar make sure you add it after something like starting `telnetd`, as that's also in /usr/sbin and you don't want the overlay to break your connection service.
Easier way that works on my LG TV: just add this line to start-devmode.sh. Then you don't have to remove the actual file.
Code:
killall /usr/sbin/update
HI guys, what is yours TV models and version of Web OS.
wins.911 said:
HI guys, what is yours TV models and version of Web OS.
Click to expand...
Click to collapse
webOS TV 5.2.1 LGwebOSTV