Related
The guides/walkthroughs seem to cover windows but I use OS X...are there any guides/walkthroughs to root a G2 using OS X?
I'm getting frustrated
Which guide are you trying to follow? Most of them require/mention adb, but the android SDK is available for Mac, so you should be able to get adb.
It should all work the same on a Mac. All you're doing on the PC/Mac end is using adb to send stuff over to your phone. The adb guide at http://forum.xda-developers.com/showthread.php?t=865685 has some stuff in there (which I still need to work on) about getting adb working on the Mac (see later replies).
dadewy said:
Which guide are you trying to follow? Most of them require/mention adb, but the android SDK is available for Mac, so you should be able to get adb.
Click to expand...
Click to collapse
I am following this guide
steviewevie said:
It should all work the same on a Mac. All you're doing on the PC/Mac end is using adb to send stuff over to your phone. The adb guide at http://forum.xda-developers.com/showthread.php?t=865685 has some stuff in there (which I still need to work on) about getting adb working on the Mac (see later replies).
Click to expand...
Click to collapse
I have got got adb working, I put the android_sdk folder at the root of my macs hard drive. I figured out I have to put "./" infront of adb to execute commands, and I have gotten it to recognise my device.
But where I am stumped is, where do I unzip the temp and perm root folders to, onto the desktop or into somewhere in the android sdk folder?
Also do need to have two terminals running, 1 navigated to adb and the other to the unzipped folders?
Or do I do something completely different?
bobbytomorow said:
I am following this guide
I have got got adb working, I put the android_sdk folder at the root of my macs hard drive. I figured out I have to put "./" infront of adb to execute commands, and I have gotten it to recognise my device.
But where I am stumped is, where do I unzip the temp and perm root folders to, onto the desktop or into somewhere in the android sdk folder?
Also do need to have two terminals running, 1 navigated to adb and the other to the unzipped folders?
Or do I do something completely different?
Click to expand...
Click to collapse
I think the common way is to unzip or move the files to your Android_sdk/tools folder so that adb and the files are in the same directory.
Another way would be to use the full path in the adb command:
adb push /users/bobby/desktop/gfree_unzipped/gfree /data/local/
you should change it to match your actual directory structure
The slick way is to add android_sdk/tools to your path so that it will work at any direectory level.
Either way, you should only need 1 terminal window (Unless you are trying to verify you have radio s-off- the last bit that starts with "stop ril-daemon")
gee one said:
I think the common way is to unzip or move the files to your Android_sdk/tools folder so that adb and the files are in the same directory.
Another way would be to use the full path in the adb command:
adb push /users/bobby/desktop/gfree_unzipped/gfree /data/local/
you should change it to match your actual directory structure
The slick way is to add android_sdk/tools to your path so that it will work at any direectory level.
Either way, you should only need 1 terminal window (Unless you are trying to verify you have radio s-off- the last bit that starts with "stop ril-daemon")
Click to expand...
Click to collapse
That helped me out perfectly, I just rooted my G2, YAY!
Thank you everyone for your help
This is a copy post from here when I realised it was in the wrong spot.
I have a rooted Desire using unrevoked and am trying to use AdFree on 2.2 but I am told that the hosts file I need to block ads cannot be written to /system while Android is running. I did some searching but, alas, no luck on an answer.
I do not know how to get to a command prompt to follow the instructions in this thread and have looked in the ClockworkMod Recovery mode for something similar.
Anyone have an idea?
edit:
I also got Root Explorer off the market (which cannot simply copy the hosts file into /system/etc/ as it does not have access whilst Android is running) and I think the command prompt I need is the pc cmd prompt when the device is plugged into USB, but I am unsure which drivers I need. The ones mention in Toastcfh's guide is for the EVO, not the Desire.
edit 2:
I got the Android SDK with adb and made progress, but still stumped.
I connect the Desire to the PC and with the Desire in recovery mode with ClockworkMod I run adb with:
Code:
adb shell
# mount /system
# exit
adb push hosts /system/etc
adb reboot
Following the example from here but it's a different device and dunno what to put for the first argument in '# mount /dev/block/mtdblock4 /system'. Any help at all would be much appreciated.
The symlink option in adfree should work for S-on devices.
If it doesn't try this:
Code:
adb remount
adb push hosts /system/etc
adb reboot
If that doesn't work flash this.
I am pretty new to this whole android market. I have a stock epic 4g running DI18 and 2.1 update 1, rooted with the one-clicked root available on the sticky note forum[forum.xda-developers.com/showthread.php?t=770388]. It installed superuser and Clockwork Recovery mod 2.5 and i have been able to access that with no problem, even did a system backup. i tried using the remount/unmount feature in this and it read that the filesystem was unmounted and mounted, but i could not figure out how that could operate with the root tools application, because i have to reboot the system and it still reads the same problems. I am not looking to change roms just yet because the SQL benchmark test scores are 49.4 seconds which seem to be enough for me. I am however trying to change the themes, boot animation, and move the cache to SD card. I have downloaded the SetCPU, titanium backup with the available BusyBox in help menu, and Root Tools by Jrummy16. The root tools application works to manage applications, but anytime i try to use any "tweaks or hacks" such as ad blocker, it does not allow it and shows me a screen reading, "unable to remount filesystem read/write." To fix this problem i downloaded android SDK on my windows 32 bit system, and downloaded all of the neccesary drivers. Most of the instructions tell you to access the Command Prompt on the computer and use:
cd\
cd androidsdk\tools
adb devices
The problem is.. once i get the file to read C:\androidSDK\tools, i try to enther adb devices and it reads to me that " 'adb' is not recognized as an internal or external command, operable program or batch file"
I am just trying to get my root tools to work so i can manage my cache and use the ad blocker, and possibly install new roms later. i also tried using the 'su' command and it said it was not recognized.
Few questions:
Is there any steps i missed to be able to develop and change my themes, or is there anything i should have used instead of the programs i used?
Is there a different way to access adb shell on the epic 4g?
Is there another way to change themes/fonts/widgets/scroll animations?
hookinhorns81 said:
I am pretty new to this whole android market. I have a stock epic 4g running DI18 and 2.1 update 1, rooted with the one-clicked root available on the sticky note forum[forum.xda-developers.com/showthread.php?t=770388]. It installed superuser and Clockwork Recovery mod 2.5 and i have been able to access that with no problem, even did a system backup. i tried using the remount/unmount feature in this and it read that the filesystem was unmounted and mounted, but i could not figure out how that could operate with the root tools application, because i have to reboot the system and it still reads the same problems. I am not looking to change roms just yet because the SQL benchmark test scores are 49.4 seconds which seem to be enough for me. I am however trying to change the themes, boot animation, and move the cache to SD card. I have downloaded the SetCPU, titanium backup with the available BusyBox in help menu, and Root Tools by Jrummy16. The root tools application works to manage applications, but anytime i try to use any "tweaks or hacks" such as ad blocker, it does not allow it and shows me a screen reading, "unable to remount filesystem read/write." To fix this problem i downloaded android SDK on my windows 32 bit system, and downloaded all of the neccesary drivers. Most of the instructions tell you to access the Command Prompt on the computer and use:
cd\
cd androidsdk\tools
adb devices
The problem is.. once i get the file to read C:\androidSDK\tools, i try to enther adb devices and it reads to me that " 'adb' is not recognized as an internal or external command, operable program or batch file"
I am just trying to get my root tools to work so i can manage my cache and use the ad blocker, and possibly install new roms later. i also tried using the 'su' command and it said it was not recognized.
Few questions:
Is there any steps i missed to be able to develop and change my themes, or is there anything i should have used instead of the programs i used?
Is there a different way to access adb shell on the epic 4g?
Is there another way to change themes/fonts/widgets/scroll animations?
Click to expand...
Click to collapse
I'm not sure if you had a typo in your original post or if that is how you actually entered the commands on your computer when you tried this, but based on the "paths" you entered, the commands should be:
CD\
CD\androidsdk\tools
adb devices
As for the themes, fonts, etc., there is an app in the market called MetaMorph that will do that for you. You just need to have .zips for it to apply.
There is also a tutorial for MetaMorph "somewhere" in the "Themes" section on XDA. I couldn't find a link to post for you, but I know it's there!
As far as getting in adb if you have windows XP you can go to the tools folder and hold shift and right click it. In the.menu it will say start command prompt here. Click it. Now you are on your tools folder where adb is. Then you can use adb and get into the shell.
Sent From My Evo Killer!
I wanted to change my device model, so I copied build.prop from another mobile to my mobile. I am already rooted. But unfortunately I did not change the o.s. from gingerbread to froyo in build.prop ( I have android 2.2 FROYO) When I rebooted, there were many errors. It is now showing no sim card. Mobile network search gives error. Effectively, I can not use the mobile. Terminal emulator, X-plore etc. stopped working. Only Rom toolkit free version works and astro file manager works. Other programs are forcefully closed. Needles to say, I must replace new build.prop with new one.
Using adb I can only pull files but can not write as it is in read only mode.
adb root and adb remount works only if you are in recovery mode ? Y mobile does not have any custom recovery so when I boot in recovery mode it hangs.
Superuser has installed su in system\bin directory. But from adb shell I can use su also. It gives permission denied error. Hence I can not remount the system.
I have read similar threads and found that on some mobiles adb root or adb shell su works but on some not.
I am using Vista 32 bit with admin rights, still can not use root in adb.
Please tell me, how can I mount system read-write. I can not install root explore as google play and even internet is not working.
Please help.
maheshchavan said:
Using adb I can only pull files but can not write as it is in read only mode.
Click to expand...
Click to collapse
activate USB debugging then in console
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p1 /system
adb push build.prop /system/build.prop
check where is your build.prop
ruscan.calin said:
activate USB debugging then in console
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p1 /system
adb push build.prop /system/build.prop
check where is your build.prop
Click to expand...
Click to collapse
OMG ruscan.calin i COULD KISS YOU! I had tried to change my OG EVO 4G's buildprop file to another phone so that I could purchase & download an incompatible Google Play app. However after I restarted the phone wouldn't start! It would boot into my rooted HTC EVO 4G Android 2.3.3 and HTC Sense 2.1 but it would get stuck on the wallpaper with just the notification bar at the top and all buttons would be frozen. However I noticed when I plugged in my phone to my computer via usb the computer recognized it. I always keep my phone with USB debugging enabled so I thought I should be good right? I have spent the last 4 hours trying to install and setup adb with no real previous experience with it. I am familiar with dos from years ago and that helped me as it's basic procedure, commands, etc. Then I found out how to install the HTC drivers which I needed and then download the Android SDK with adb that's included which many guides show easily. I started the command prompt (cmd), typed my adb devices command and hurray it showed my phone! I connected and quickly navigated to the build.prop system folder! Luckily when I changed the file I made a bak backup and left it in the same folder. Now the main issue was figuring out how to change the naming of the files which I did via usual adb commands (mv build.prop.bak build.prop). But then to no avail I couldn't get it to write due to it being a system read only folder! Arg! Then I found your post on here, above, and typed it in simply leaving out the adb push portion and replacing that with the mv file command instead and first changing the name of the bad file and then replacing the bak file as the good copy! I exited back to the adb main and unplugged my phone. Moment of truth and man was everything flashing through my head at once! I booted up and YESSSSSSSSSSSSSS, it worked! I went back into root explorer and got rid of the offending leftovers and I've learned my lesson! I just don't want to think about what would have happened if I hadn't found this post. Thank you and if anyone else makes this hug mistake let me know and maybe I can help. Moral of the story don't mess with the build.prop or any system folder unless you know what you're doing! Thanks again!
Quick Guide to Fix Android "build.prop" Issues:
1. Find and download USB drivers for your phone by model or type (HTC EVO 4G's HTC Fastboot drivers): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
2. Download and install Android SDK and choose adb: http://developer.android.com/sdk/index.html
Guide: http://htcevohacks.com/htc-evo-hacks/how-to-install-android-sdk-and-adb-drivers-for-htc-evo-4g/
3. Run a command prompt from the "c:/program files/android/android-sdk/platform-tools/" directory. I had to copy the command prompt to get it to open there but sometimes a right-click action will do it. The guide below will help just navigate down to "Using ADB" and skip the rest.
Guide: http://www.howtogeek.com/114667/how...y-default-move-almost-any-app-to-the-sd-card/
4. Once you open the command prompt and you're in the "c:/program files/android/android-sdk/platform-tools/" foler type "adb devices" and your device should appear. If it does move on to next step.
5. Then type adb shell and use the ls command to see directories. Then you'll need to navigate to the system folder by typing "cd system" and then type "ls" to look around in the directory (similar to "dir" in DOS). You should now see the bad build.prop file.
6. You'll need to rename the file or push a correct version. First you need to use the "adb shell" command again and then "su" and finally "mount -o rw,remount /dev/block/mmcblk0p1 /system" to make the directory writable (see ruscan.calin post above for additional info).
Note: I only had to rename my build.prop as I already had my old one in the same system folder. You may have to copy the bad build.prop to your computer, edit it and then push it back to the same system directory. These directions are only for renaming files in the same folder. For the info on how to copy the file to your computer and push it back to your phone go to step *10 below or use the guide below it.
7. I already had the bad build.prop in the system directory with my old one which I had named build.prop.bak. If you have this too simply rename by changing the name first of the bad file to anything by typing "mv build.prop build.prop.bad" or similar.
8. Next rename the build.prop.bak to build.prop by typing "mv build.prop.bak build.prop". Everything should go smoothly and move onto the next step.
9. Finally, If no error messages are found, simply type "adb reboot" or "adb shell reboot" (Depending which version of ADB you have). You should be done, your phone will reboot like normal (working, lol) and everything should be working again! YAY!
*10. To copy the build.prop to your phone type "adb pull /system/build.prop c:\" and the file should be placed in the main c:/ directory on your computer. Navigate to the root (c:/) directory and then right click and "open with" the "build.prop" file using a notepad or other file editor. Then use the text editor (Notepad, etc) to change back what you originally changed to mess everything up. There is tons of stuff on the net to let you know what to fill back in depending on your phone model/type. Or it's possible to get a previous version from an old Nandroid backup or similar. Save the changed text file and make sure its named the same "build.prop" and make sure it's still in the root directory (If you're having issues on this step or just want more insight check out the guides and threads below for more help).
Guide 1: http://androidforums.com/admire-all...p-computer-not-phone-using-root-explorer.html
Guide 2: http://www.modaco.com/topic/328943-quick-guide-to-modifying-buildprop-with-adb/
Guide 3: http://forums.androidcentral.com/sp...-replaced-build-prop-phone-wont-start-up.html
*11. We've already made the directory writable in step 6 so we simply need to push the file back to the phone. If any error message appear re-do step 6 to make writable again. Otherwise push the modified file back to the phone by typing "adb push c:\build.prop /system/". Back to step 9 above! Yay!
If anyone wants to help cleanup this quick guide or make any changes feel free. I just wanted something so that if anyone else has this issue they won't have to worry or search forever to find a solution. OMG it's 2:30AM, to bed... I ride! LOL
Enjoy,
5th :highfive:
THANK YOU!!! Totally saved me today.
One thing that I noticed. After pushing the correct build.prop, I had to fully power down, then turn back on my Razr for it to load up the fixed build.prop.
error message,Help please
Hello, when i am going to mount and change the permission i am getting constant error od device not found or sh:not found.
What to do?Help me please?
jigarpattani said:
Hello, when i am going to mount and change the permission i am getting constant error od device not found or sh:not found.
What to do?Help me please?
Click to expand...
Click to collapse
What step are you on? What phone do you have? More info please?
i am have problem whit my pantech flex i need to use the build.prop.bak but when i type the su it stay in blank do nothing any ideas pls help
ehy there hope someone can help me...i have an archos 97b platinum, messed up with build.prop. So i pulled out and restored but can't push in any way. I have a cwm installed, tablet rooted but i alwais got "permission denied" at push command. Other error is operation not permitted" if i try remount command from adb. i can do mount -o rw,remount /dev/block/mtdblock7 /system but after that push still give me permission denied.
any suggestion?
http://imgur.com/FDLp4fl
i open a 2nd cmd, give the mount -o rw,remount /dev/block/mtdblock7 /system , and system is now rw, but from the first cmd when i give "push build.prop /system (or /system/build.prop) it will always return me permission denied
help
dev.block
i want to view to dev/block using adb shell #
eg . what block is boot.img
what block is recovery.img
what block is system.img
what block is cache.ing
adb shell getprop mtd is not work . Pls Help Me & sent to mail [email protected]
How to enable ADB on ALLWINNER A13 9" - 4.2.2 - Windows 7 - error:device not found
Hi folks, my target is to do a full backup of my android tablet device without rooting nor installing app's on the device. It can be done just by the ADB tool and the simple command
Code:
adb backup -apk -shared -all
.
Basic information
PC: Windows 7, pro. USB 2.0 port. ADB Driver "Drivers-AllwinnerA10-32bits\32Bit_Win_7_Vista_XP" from 2011. ADB Platform-Tool, Android Debug Bridge version 1.0.31. Logged in as normal User, not Admin. The development kit is not installed, I just downloaded the Platform-Tool, unzipped it and started "adb" - I just want to make a f***ing backup :crying:
Tablet:
ALLWINNER A13 9". Android Version 4.2.2. USB Debugging enabled. Detail Info's:
Model number: JL902
Kernel Version: 3.4.0+ [email protected] #1 Mon 25.11.2013
Build-Number: full_gs702c-userdebug 4.2.2 JDQ39 eng.root.20131207
NOT ROOTED.
Problem:
I do not get a connection from the PC to the tablet. Also no RSA Key question comes up at the tablet. The adb tool just throws an error :"device not found". I tried several things, log in as Admin, "adb wait-for-device", plugging and unplugging ... nothing helped. The adb tool works fine, I tested it with a Samsung Galaxy S2. I'm not quite sure about the adb USB driver on windows, but there is no exclamation mark nor other problems reported. So this should be fine.
Anyone any hint, tip or solution? Would be great - gathering for hours with this problem - searching forum 'n stuff....
Thanks in advance
Juha
Try with uberizer or MTKDroid tools. Just connect and select adb terminal.
kramkumar said:
Try with uberizer or MTKDroid tools. Just connect and select adb terminal.
Click to expand...
Click to collapse
Thx 4 the hint, tried uberizer:
Code:
ERROR No useable device has been found
I think since in Android 4.2.2 the RSA Key authentication was introduced, something is wrong with the connection. Because I would expect the RSA Key question on the tablet, but the tablet does not show this dialog.
By the way, I recognized that the USB driver for the ADB interface is titled "Drivers-AllwinnerA10" but the tablet has a A13 core. But I do not find another driver at the moment and the vendor ID -VID_10D6&PID_0C02&REV_0202&MI_01- fits (otherwise, windows wouldn't install it anyway). Does it make sense to search for another driver?
hi from messing with various drivers and android devices i have found that installing PDA net for windows (theirs and android version too but not needed) once pdanet installs let the drivers for your phone be installed, if by any chance you have drivers already installed what you can do is go to device manager, click on your device uninstall the drivers, unplug your phone and then open pdaNET a window will come up waiting for you to connect your phone and the driver installation process will begin.
The program downloads the correct driver for mostly any model phone you have and works flawlessly with ADB, if by any chance this helped just give me a thanks !
abstractVoid said:
The program downloads the correct driver for mostly any model phone you have and works flawlessly with ADB, if by any chance this helped just give me a thanks !
Click to expand...
Click to collapse
Thanks for the tip. It really installed an USB driver as you said (I've deinstalled the other driver before). But sadly the result is the same. I can't access the ADB interface - same error "Device not found".
At this point I want to say thanks to all viewers of this thread, it seems really to be not an easy task. I'm still open minded in any direction and would be happy for any suggestion what I might try.
Even a hint, how I could reduce the possibilities for the root of my problem. I'm still not quite sure, if the driver is the problem or even if the tablet itself has some kind of software defect on this kernel version - By the way, does anyone have the same kernel version (posted at the beginning - 3.4.0+ [email protected] --- repeated for your convenience) of Jelly Bean (4.2.2)? Do you have experience with the ADB interface then?
How may I isolate the real problem? Any idea wellcome :cyclops:
I have nearly an identical tablet except mine has the PnP code of Vendor 10D6/Device 0C01 and it shows as P706 on the USB description.
I installed PDAnet, that actually was able to upload the Android version of PDAnet to the tablet, so I think that's a definite for the driver working. But I'm also having trouble getting ADB to list the device and I'm using the latest ADB from the SDK. Since ADB tries to setup a network server, I'm wondering if the ADB driver on windows has to be tethered as a NIC somehow?, just a theory.
I'm using a fresh install of XP and can do a complete rollback, so I'm certain it's not the OS.
There's also another quirk about this tablet. I wanted to do a backup of the firmware from this device. Techknow's utilities use ADB to issue several shell commands to copy "partitions" to the SD card, I thought I might as well try to do that manually only to find what would've been copied as /dev/block/nanda, nandb, etc. is named /dev/block/acta, actb, etc. instead. But lack of "root" means I can't read any of those partitions or even copy su into /sbin.
Uberizer isn't any good since as far as I can see that also uses ADB. Any known issues with versions of ADB? or even any other tools which do similar to ADB?, or even a way to "root" these devices just by Terminal and SD?
Regards
Ah, okey, soz I got the USB thing a bit mixed up. My tablet does have the same code, I assume the 0C01 is when it's in recovery mode (power on with volume + pressed)
I also realised the driver that was working wasn't one from PDAnet.
I've updated the working 32-bit driver with the version of ADB I'm using and included it in the attachment. Maybe you can try that and see if you have any progress.
I'll keep posted on this thread.
SOLVED!
Copy .android from the attachment into your %USERPROFILE% directory (i.e. C:\Document and Settings\<user> on XP or C:\Users\<user> on Windows 7)
You can check what the user directory is by DIR %USERPROFILE% in the "DOS" command line (%USERPROFILE% is case sensitive).
ADB should list your device when you do adb devices in the "DOS" command line.
Basically, adb_usb.ini with a custom identifier was missing.
Regards,
qUE
Right, I've made up a pack to automate putting SU on the device and setting up permissions on SU and BUSYBOX.
!!! This is only for the VID_10D6&PID_0C02 device, your mileage may very with other devices. !!!
DRIVER directory should contain the USB driver you need, otherwise try installing PDAnet and tell it to replace the driver.
Install USB driver, run SUME.BAT
to hopefully backup all the needed stock firmware to SD;
adb shell
su
cat /dev/block/acta > /mnt/sd-ext/acta.img
cat /dev/block/actb > /mnt/sd-ext/misc.img
cat /dev/block/actc > /mnt/sd-ext/system.img
exit
exit
adb kill-server
qUE
Confirmed solved
qUE-ARM said:
SOLVED!
Copy .android from the attachment into your %USERPROFILE% directory (i.e. C:\Document and Settings\<user> on XP or C:\Users\<user> on Windows 7)
<SNIP>
Basically, adb_usb.ini with a custom identifier was missing.
Click to expand...
Click to collapse
CONFIRMED SOLVED
Yes, that was it! I copied the adb_usb.ini file into the .android user directory (which only contains these ascii chars "0x10D6" - no CR no LF or anything else) and it worked out !!!
Thank you (Thanks meter will follow ) Some interesting things I discovered now:
There was no RSA-Key question at all on the tablet!!!
as I did the full backup with "adb backup -apk -shared -all" I was asked on the tablet to confirm this
So obviously something strange is going on here. Since it is claimed everywhere the with Android 4.2.2 the ADB interface should be generally RSA-Key protected. Okay, might be that I misunderstood something here :silly:
At least this problem is solved and I appreciated every comment in this thread. One question would be final to answer:
Who should have brought the adb_usb.ini to my PC. The ADB driver ? The ADB Platform-Tool package? So, whom to blame here - NO - just kidding :laugh:
I did briefly try the platform-tools (since I didn't mind the OS being trashed), they didn't add any adb_usb.ini and there isn't any real indication the file was needed/didn't exist, they could've simply put a note on the ADB utility when it didn't find any devices.
I'm not sure what ADB backup does. As far as I know the mounted partition images are differently named to various backup tutorials, so I get the feeling ADB backup just simply copies the user data and not much else. I recommend doing the backup I mentioned as well, it'll at least capture a copy of the boot partition, which if the device doesn't have that you'll probably need to revert to using live suite or some other firmware utility to restore it. Getting the firmware for that is another story, read a fair amount of posts here and other places on the net that don't sound fun.
I personally still can't get superuser to behave for using su on the terminal/term.apk (I want to remove useless "system" apps and make sure the device isn't talking back to anyone, i.e. google), but I'll keep tinkering.
My main aim for getting one of these tablets was to boot other firmware from the SD slot, but it looks as if the u-boot process is locked to internal NAND. So might have to modify it by adding "fatload mmc" to the script.
qUE
Quick Update;
Right the permissions thing turned out to be an issue with Superuser, dunno why. So replace the su binary from SuperSU (http://forum.xda-developers.com/showthread.php?t=1538053) into my SUME pack and install the Superuser.apk by;
adb root
adb shell mount -o rw,remount /system
adb push Superuser.apk /system/app
as for stripping back the Applications, I've got it down to this as bare bones
adb pull /system/app backup\system\app
to backup system applications before you do anything
I found if you do delete any applications and then android gets stuck at the logo, just adb push them back and it'll boot without reboot when you've got the chain right.
minimum applications needed for boot are;
DefaultContainerService.apk
DefaultContainerService.odex
SystemUI.apk
SystemUI.odex
Launcher2.apk
Launcher2.odex
Settings.apk
Settings.odex
SettingsProvider.apk
SettingsProvider.odex
ActSensorCalib.apk
InputDevices.apk
InputDevices.odex
FusedLocation.apk
FusedLocation.odex
LatinIME.apk
LatinIME.odex
PackageInstaller.apk
PackageInstaller.odex
ApplicationsProvider.apk
ApplicationsProvider.odex
A few odds and sods missing will make settings close, but it's trivial stuff. Personally don't like the sound of Fused Location, but it won't boot without it and I haven't seen any dodgey traffic from it (yet).
I recommend installing Droidwall with adb push /system/app, before installing games.
And modifying /etc/hosts with 127.0.0.1 to certain you know whos and advertisers.
Some of my personal choice replacement applications (so far);
Total Commander over ES file explorer.
Opera Classic over the inbuilt browser (although I'm still trying to remove the default search engine).
qUE
More update;
Discovered some new things;
BACKUP FILES WITH "ADB PULL" BEFORE MODIFYING ANY FILES!!!
I think performancepolicy.apk needs to be added to the bare bones application list, afaics from looking inside the package it sets system performance stuff, so likely throttling to preserve battery power.
bin_cfg.xml in /misc which can be modified by
adb shell mount -o rw,remount /misc
then adb pull, edit and push the file back
the line in there for "backlight_brightness" 780;1020;780 can be changed to 240;1020;240 which dims the backlight substantially saving battery power. not sure if 240 is the absolute minimum, but 120 seems to be too low afaics. interestingly information on the settings is in the files named _userview.xml
build.prop in /system which can be modified by
adb shell mount -o rw,remount /system
then adb pull, edit and push the file back
and then chmod 644 /system/build.prop
the lines in there for ro.wifi.signal.level.# can all be set to 0, this theoretically cuts the wifi power usage to less than 1mW, again saving battery. if android doesn't boot fully on reboot it's because chmod hasn't been set, you should be able to adb back in and correct.
please be careful modifying either file as both seem to have safety limits imposed on certain device components (i.e. battery temprature), messing with those can make the tablet stop working.
qUE