Related
How would it be able to do this? I've seen terminal codes floating around, but none of them look like they'd be replacing the proper files for a cupcake build (old RC33 builds I believe, long lost now!)
I'm running TheDude's 1.3 RC2. I've seen plenty of ADB commands, however I've never been able to get ADB to work on my computer, and I don't feel like putting more pointless hours into it
So how would the terminal commands work, and what would the pre-requisites for the files have to be? Thanks!
http://forum.xda-developers.com/showthread.php?t=467693 Im pretty sure all you need is fastboot not adb for splash1 the animated splash just requires you to resign an update.zip http://forum.xda-developers.com/showthread.php?t=467693
crotalusfreak said:
http://forum.xda-developers.com/showthread.php?t=467693 Im pretty sure all you need is fastboot not adb for splash1 the animated splash just requires you to resign an update.zip http://forum.xda-developers.com/showthread.php?t=467693
Click to expand...
Click to collapse
I'm pretty sure it uses ADB, hence why I'm asking...Fastboot IS ADB
yea fastboot is the only other way that I know of!!
this is where i downloaded the tools for creating your own boot image!
http://www.modmygphone.com/forums/downloads.php?do=file&id=1471&act=down
this is the link that teaches on how to make one and im pretty sure there is one here in the forums!
http://modmygphone.com/forums/showthread.php?t=10461
if you need help PM me ill take you step by step!
or email [email protected]
lukekirstein said:
I'm pretty sure it uses ADB, hence why I'm asking...Fastboot IS ADB
Click to expand...
Click to collapse
it wont use ADB, fastboot is like an alternate route...
Drizzy Drake Rogers said:
yea fastboot is the only other way that I know of!!
this is where i downloaded the tools for creating your own boot image!
http://www.modmygphone.com/forums/downloads.php?do=file&id=1471&act=down
this is the link that teaches on how to make one and im pretty sure there is one here in the forums!
http://modmygphone.com/forums/showthread.php?t=10461
if you need help PM me ill take you step by step!
or email [email protected]
Click to expand...
Click to collapse
Step number two of those directions: "2. Get ADB setup and working. Read here. "
Let's clarify. I cannot get ADB to work, at all, on my computer. Fastboot doesn't work because I can't get ADB to work. Moreso, I just realized that I can't even find my data cord.
Either way, the point of my post is to find a way to change the boot animation at start up, without having to use anything but the phone and maybe some photo editing software.
So how can we do this?
You do not have to have the whole sdk(adb etc..) for fastboot to work you do have to have a driver running for android found in the sdk or here http://dl.google.com/android/android_usb_windows.zip .
The boot animation is found in /system/framework/framework-res.apk/assets/images,android-logo-mask.png and android-logo-shine.png are the images you wanna edit.Dont believe you can get it back on your phone without the sdk set up with adb working though as you will either have to resign an update or push the edited files back somehow.
Edit:without a data cord I think this is an impossibility I dont think you can go through the process needed on your phone,dont hold me to that though good luck man.
crotalusfreak said:
You do not have to have the whole sdk(adb etc..) for fastboot to work you do have to have a driver running for android found in the sdk or here http://dl.google.com/android/android_usb_windows.zip .
The boot animation is found in /system/framework/framework-res.apk/assets/images,android-logo-mask.png and android-logo-shine.png are the images you wanna edit.Dont believe you can get it back on your phone without the sdk set up with adb working though as you will either have to resign an update or push the edited files back somehow.
Edit:without a data cord I think this is an impossibility I dont think you can go through the process needed on your phone,dont hold me to that though good luck man.
Click to expand...
Click to collapse
Alright, I just confirmed the location on the phone. So if I upload a file onto my SD card, and overwrite it through Terminal, what do you think that'll do? I'm not big into the Themes section, I'm into the Development section, so I'm not sure what overwriting will do to my phone.
Actually you might be able to get away with that.Try backing up framework res in terminal type:
$su
#mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
#cp -r /system/framework/framework-res.apk /sdcard
Now the .apk you want is on your sdcard root pull that onto a computer unzip it with 7zip.In the framework-res folder there are some more folders go to assets then images edit those two images to your liking.Then go back to your framework-res.apk that you backed up add .zip to the end,right click it and choose open or explore navigate back to the images folder and paste your edited boot images in there.Now remove .zip so it is framework-res.apk again put that back on your sd cards root.Go to terminal and type
$su
#mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
#cp -f /sdcard/framework-res.apk /system/framework
#reboot
If all goes well that should work.
crotalusfreak said:
Then go back to your framework-res.apk that you backed up add .zip to the end,right click it and choose open or explore navigate back to the images folder and paste your edited boot images in there.Now remove .zip so it is framework-res.apk again put that back on your sd cards root.
Click to expand...
Click to collapse
Lost you at naming it as a .zip. I can't explore or open the file, as Windows Vista doesn't know how to handle it. Any ideas?
lukekirstein said:
Lost you at naming it as a .zip. I can't explore or open the file, as Windows Vista doesn't know how to handle it. Any ideas?
Click to expand...
Click to collapse
right click-> open with -> WinRAR
Or go to Folder Options and uncheck "Hide extensions for known filetypes" (you should do that for all folders.... its a bad idea not to because a virus may look like *.doc instead of *.doc.exe anyways its also more convenient)
does anyone know how to change the boot image for a rogers g1 none of these things work for me i bricked my last phone a week ago cause someone said it would work
jokefox said:
does anyone know how to change the boot image for a rogers g1 none of these things work for me i bricked my last phone a week ago cause someone said it would work
Click to expand...
Click to collapse
Well if you're bricking phones, I wouldn't recommend trying it again
I have looked around quite a bit, and haven't really figured out the straight answer on this.
I have seen apks that can be downloaded of things like the clock or gallery app, and then I have seen custom roms that include things like the AOSP dialer, contact app, browser, etc. However in my small amount of trying, I couldn't install them on top of another ROM (or stock).
Is there an issue with signing them, or does it have to be done in recovery mode, or do I have to remove the existing stuff in something like Titanium backup and then install the other APKs, or would my only option be to learn the dark arts of rom cooking?
Edit: Answered thanks to mrchu001. Doing an "adb remount" and then issuing the install command from the shell worked.
I'm not sure if this works for ALL apks between roms, but when i flashed Fresh it didn't have the cooliris 3d gallery that DC has, so i opened the zip, and copied the APK from one rom to the other then flashed it. I'm sure there are some programs that just won't work even if you did it this way, but something to consider.
That works in most cases..
Just get the zip on your computer, open it extract the apk you want and adb install it to your connected device.
No luck with either method mentioned above. I'm sure I don't know what I'm doing... but I did an adb install <apk name> and got an error:
Code:
MacBook: tools laydros$ adb install CarDock.apk
1344 KB/s (238640 bytes in 0.173s)
pkg: /data/local/tmp/CarDock.apk
Failure [INSTALL_PARSE_FAILED_UNEXPECTED_EXCEPTION]
And I grabbed one of the base rooted roms, unzipped, added the CarDock and DeskClock apks to the system/app folder with everything else, and the ROM failed to load. I did the same clockwork rom manager install rom from SD card methods I have done before. I assume this means that the zip was not properly signed.
The apks I was testing were ones from bugless beast 0.4, any ideas?
laydros said:
No luck with either method mentioned above. I'm sure I don't know what I'm doing... but I did an adb install <apk name> and got an error:
Code:
MacBook: tools laydros$ adb install CarDock.apk
1344 KB/s (238640 bytes in 0.173s)
pkg: /data/local/tmp/CarDock.apk
Failure [INSTALL_PARSE_FAILED_UNEXPECTED_EXCEPTION]
Click to expand...
Click to collapse
it looks like you didnt direct your terminal correctly. i'm assuming you have the sdk on your computer btw. now try to upload the rom you want on your phone. plug it in. make sure usb debugging is set. make sure the apks you want to put on your phone are on your desktop. and try this:
Code:
cd ~/*where every your sdk is*/tools
./adb remount
./adb shell
./adb install ~/desktop/*apk name* /system/app
./adb shell reboot
maybe you already tried but just incase.. do you have the Unknown sources check box "Checked" under "Settings/application" menu? if not you need to to install apps not from the market..
mrchu001 said:
it looks like you didnt direct your terminal correctly. i'm assuming you have the sdk on your computer btw. now try to upload the rom you want on your phone. plug it in. make sure usb debugging is set. make sure the apks you want to put on your phone are on your desktop. and try this:
Code:
cd ~/*where every your sdk is*/tools
./adb remount
./adb shell
./adb install ~/desktop/*apk name* /system/app
./adb shell reboot
Click to expand...
Click to collapse
The remount part did it, and then doing the install from adb shell. Thanks so much.
For the sake of anyone else that finds this, once you type adb shell, you are working from the phones shell instead of the one on your computer, so you would skip that command. I ended up moving the files to the sdcard, and then doing
Code:
cd ~/*where every your sdk is*/tools
./adb remount
./adb shell
(at this point you are at the phone's prompt)
install /sdcard/*apk name* /system/app
exit
(now you are back at the computer's prompt)
./adb shell reboot
Now I need to figure out what to install to get the phone/contacts working. Calendar and Mms applications were easy, but after installing several apks for the phone and contacts I just have a mess.
FroydVillain 1.0.0 install *.apk files in /system/app
Hi has anyone tried installing another apk file in FroydVillain 1.0. I follow the steps in the thread described i am able to issue adb shell commands and i have placed the apk files in the SD card as described. but i am getting an error as below that the file or dir is not found. tried several paths:
# install /mnt/sdcard/*.apk /system/app
install /mnt/sdcard/*.apk /system/app
install: can't stat '/mnt/sdcard/*.apk': No such file or directory
# install /sdcard/*.apk /system/app
install /sdcard/*.apk /system/app
install: can't stat '/sdcard/*.apk': No such file or directory
I use /mnt/sdcard path cause on Froyo the SDCARD folder is under /mnt.
any help solving this. i am trying to install some of the HTC Sense UI app to sys app. Like Stock.apk for test. and HTCAlbum.apk and others same result every time.
I have tried also AndroidCommander 0.7.9.6 updated for froyo. installing with it's install option button, and also from the console i run the shell command for install, successfully adds the apk in sys app folder but the apk is not installed, and asks for installation.
Thanks.
Regards Alek
help
Hi,
Can you explain to begginers (like me) how do you installed the apk in system/app? please, I want to install contacs.apk form CM9 to other rom.
Thanks.
Although there are a few threads out there with similar titles I have not found one that is specific to the T-mobile slide nor is there a step by step guide. So I have taken the liberty to post this here. Mods feel free to delete if this is a repeat on this particular forum or if there are any mistakes that need to be corrected.
First off DO NOT ask me any questions as I am a complete noob like many others out there. I give ALL the credit to DanFrance from Android Forums for putting this list. I did slight modifications to his instructions in order to suite our mytouch slides but that is it. He put in all the time and hard work.
If you would like to see his exact instructions please go here http://androidforums.com/desire-all-things-root/158131-how-easily-remove-installed-system-apps.html. He used Android SDK and I was able to successfully remove aps without having to tap into it.
Disclaimer: I am in no way responsible if ANYTHING goes wrong with your phone. Follow instructions at your own risk and will. phew! With that out of the way, let's proceed.
Pre-requisites-
A. First off your phone MUST be rooted!
B. Very important, you need to feel comfortable using the command prompt. Although this is an idiots proof step by step guide some of us can feel a bit uneasy with that little black window.
C. You need ROM Manager with ClockWorkMod recovery flashed
D. You will also need a backup created with ROM manager (in case anything goes wrong you can revert back to the saved backup).
Now for the fun stuff!
NOTE: Commands must be typed exactly. Be careful you identify spaces.
1. Connect your phone via USB, open ROM manager and select Reboot into recovery (press OK when the small window pops up in your screen). You will see a black screen with a circle and an arrow on it. This will then change to a black screen with green menu options
2. Using the optical trackball to navigate the menu (or vol up and down), select (by pressing the trackball) Partitions menu
3. Then select mount /system
4. On your PC open Command prompt (Start>Run Type “cmd” [without the quotation marks] and press enter)
5. Type adb shell and press enter (this should give you a # sign)
6. Type cd /system/app and press enter
7. Type ls (the letter L ) and press enter, this lists all the system installed Apps.
8. Type rm AppName.apk (where AppName.apk is the application you want to remove) and press enter. Note: this IS case sensitive. Example rm Amazonmp3.apk
Repeat step 8 to delete all the apps you want. Be VERY careful and only delete what you don’t need. If you do not know what an app is for, DO NOT delete it.
Once you are done deleting:
a) Close the command prompt on your PC
b) Select unmount system on your phone.
c) On the phone, press back once to get back to the main menu.
d) Navigate to advanced and select it
e) Navigate to Wipe Dalvik Cache and select it.
f) Once complete, in the menu, press back until the top option is reboot system now. Select it.
You are done.
The reboot will take a long time as it will be creating the dalvik cache from scratch (just like when you install a new rom).
Now wasn’t that easy?!?! Now run along and enjoy your crap free phone.
Additional info:
Those of you who have managed to successfully delete apps on your phones (mytouch slides that is) without issues, would you be kind enough to share/recommend what you have removed? Your information will be of much help many of us. There are a few lists out there pertaining to other phones but I have not found one specific to the Espresso/mytouch Slide.
Here’s my list so far:
Amazonmp3.apk
AppPack2.0.apk
Music.apk (speaker)
mytouchmusic_1.1.5_13.apk
Faves.apk
FavesWidget.apk
Flickr.apk
Teeter_NoHTC.apk
VpnServices.apk
HtcTwitter.apk
com.htc.TwitterWidget.apk
MagicSmokeWallpapers.apk
Checking these to see which one is giving me the app&sync error
NewsReader.apk
com.htc.NewsReaderWidget.apk
Stock.apk
com.htc.StockWidget.apk
FriendStream.apk
com.htc.FriendStreamWidget.apk
SocialNetworkProvider.apk
IM.apkIM.apk
There are a few things that I need clarification for:
1. what's the difference between lattitude and maps?
2. Car home and navigation
3. All calendar aks (3 total)
4. All the weather aks (5 total)
Cheers!
arcybarrios said:
DanFrance from Android Forums
Click to expand...
Click to collapse
DanFrance from everywhere it seems
danfrance said:
DanFrance from everywhere it seems
Click to expand...
Click to collapse
The master makes an appearance! I was about to send you the link
This is great. There is a page on the cyanogen wiki about making a barebones rom but most people don't know that so it's good to have it here. Not to mention we've all found out over time that the slide operates a bit different than the norm sometimes.
There is a super easy way to delete them without adb. Does it in one click, but it's super special and I'm not talking
Actually I don't want to turn attention away from your thread. It's good learning material for noobs I'll PM it to you if you want to know arcybarrios.
arcybarrios said:
Here’s my list so far:
Amazonmp3.apk
AppPack2.0.apk
Music.apk (speaker)
mytouchmusic_1.1.5_13.apk
NewsReader.apk
com.htc.NewsReaderWidget.apk
Faves.apk
FavesWidget.apk
Stock.apk
com.htc.StockWidget.apk
Flickr.apk
FriendStream.apk
SocialNetworkProvider.apk
Teeter_NoHTC.apk
VpnServices.apk
com.htc.FriendStreamWidget.apk
HtcTwitter.apk
com.htc.TwitterWidget.apk
IM.apk
MagicSmokeWallpapers.apk
There are a few things that I need clarification for:
1. what's the difference between lattitude and maps?
2. Car home and navigation
3. All calendar aks (3 total)
4. All the weather aks (5 total)
Cheers!
Click to expand...
Click to collapse
1. Latitude is a social function for google maps - if you don't know what it is, you don't need it and it's safe to delete.
2. Car home is like an alternate UI you can use while you're driving. Very basic and big buttons. It's safe to delete.
3. I'll look into the calendar and weather apk's.It's been awhile since I've messed with a sense ROM.
KCRic said:
There is a super easy way to delete them without adb. Does it in one click, but it's super special and I'm not talking
Click to expand...
Click to collapse
I tried deleting via Root Explorer toggling r/o to r/w and that didn't work (and it was actually pretty easy). I also tried Titanium and that didn't work either....Soooo I was left out in the cold pretty much until a kind bright soul (danfrance) thought of the step by step idiot proof tutorial lol
Please do share which other method is out there that you consider easy. This tut my not be everyones cup of tea and so if you have something that is 101 for idiots then by all means
KCRic said:
1. Latitude is a social function for google maps - if you don't know what it is, you don't need it and it's safe to delete.
2. Car home is like an alternate UI you can use while you're driving. Very basic and big buttons. It's safe to delete.
Click to expand...
Click to collapse
As far as latitude and maps, I find them the exact same (when I click on each) so I am not sure which one to delete. Will deleting latitude affect the "check-in" on facebook?
As for the Car home app, so this and Navigation are exactly the same? Being the only difference of visual preference?
You need to be S-OFF on the desire to mount /system/app as r/w, otherwise the apps reappear.
How is s-off achieved on the Slide?
danfrance said:
You need to be S-OFF on the desire to mount /system/app as r/w, otherwise the apps reappear.
How is s-off achieved on the Slide?
Click to expand...
Click to collapse
you read my mind! LOL
BTW I have a wee bit issue... ahem, I have a ""The application Accounts & Sync (process com.htc.settings.accountsync) has stopped unexpectedly"
Please list what you have removed.
danfrance said:
Please list what you have removed.
Click to expand...
Click to collapse
Here’s my list so far:
Amazonmp3.apk
AppPack2.0.apk
Music.apk (speaker)
mytouchmusic_1.1.5_13.apk
Faves.apk
FavesWidget.apk
Flickr.apk
Teeter_NoHTC.apk
VpnServices.apk
HtcTwitter.apk
com.htc.TwitterWidget.apk
MagicSmokeWallpapers.apk
I also deleted these and from what I am reading one of these is what is causing the problem if not all of them
NewsReader.apk
com.htc.NewsReaderWidget.apk
RSS.apk
Stock.apk
com.htc.StockWidget.apk
FriendStream.apk
com.htc.FriendStreamWidget.apk
SocialNetworkProvider.apk
IM.apk
EDIT: BTW I made both a nandroid and Titanium backup
Suggestions
danfrance said:
You need to be S-OFF on the desire to mount /system/app as r/w, otherwise the apps reappear.
How is s-off achieved on the Slide?
Click to expand...
Click to collapse
S-off is not available on the Slide yet, but it's being worked on. There's a thread for it in the dev section if you'd like to check the status.
@ the OP, I suggest a couple of revisions.
1. Most who have rooted their phones would already know this, but in case someone doesn't know, you need to download the android SDK from google, and then in command prompt navigate to your android SDK tools folder, for example, for me, my android sdk is in my downloads folder. So I would type cd C:\users\ryan\downloads\android\android-sdk_r06-windows\android-sdk-windows\tools and THEN do adb shell, so on and so forth. If you just start command prompt and type ADB it won't recognize ADB as a command. Command prompt needs to be navigated to the same directory as adb.exe for it to work. Like I said, most people who root their phones would know this, but some noobs may not.
2. I also suggest adding a little bit of linux terminal 101 info- to list all the files in any directory, in this case, /system/app, once in shell mode, type ls and hit enter and it will list out all directories and files in your current location, in this case the APK's.
3. On some computers, including one of mine, if you do not eject or "safely remove" the sd card in my computer before unmounting usb storage in your phones recovery, it causes an IRQL_NOT_LESS_OR_EQUAL blue screen on your computer. Just a heads up. So before unmounting or doing ANYTHING in recovery, unmount the sd card from your computer first, THEN unmount usb storage on your phone. This has prevented blue screens for me. Like I said, it only happens on some computer chipsets.
Great post overall though, if it isn't already stickied it should be stickied.
MusicMan374 said:
@ the OP, I suggest a couple of revisions.
1. Most who have rooted their phones would already know this, but in case someone doesn't know, you need to download the android SDK from google, and then in command prompt navigate to your android SDK tools folder, for example, for me, my android sdk is in my downloads folder. So I would type cd C:\users\ryan\downloads\android\android-sdk_r06-windows\android-sdk-windows\tools and THEN do adb shell, so on and so forth. If you just start command prompt and type ADB it won't recognize ADB as a command. Command prompt needs to be navigated to the same directory as adb.exe for it to work. Like I said, most people who root their phones would know this, but some noobs may not.
Click to expand...
Click to collapse
Hi musicman! Although I have Android SDK installed on my computer, I personally didn't need to tap into it to delete files BUT that is why I made mention of it and included the original link of where I found the step by step process. Danfrance includes the sdk procedure in his tutorial. As soon as I opened the command prompt I typed adb shell and continued with the steps successfully.
MusicMan374 said:
2. I also suggest adding a little bit of linux terminal 101 info- to list all the files in any directory, in this case, /system/app, once in shell mode, type ls and hit enter and it will list out all directories and files in your current location, in this case the APK's.
Click to expand...
Click to collapse
This would be great if I knew linux BUT since I don't maybe if I add snap shots of what I did and what it looks like? What is typed in the OP seems to be along the lines of what you are suggesting.
MusicMan374 said:
3. On some computers, including one of mine, if you do not eject or "safely remove" the sd card in my computer before unmounting usb storage in your phones recovery, it causes an IRQL_NOT_LESS_OR_EQUAL blue screen on your computer. Just a heads up. So before unmounting or doing ANYTHING in recovery, unmount the sd card from your computer first, THEN unmount usb storage on your phone. This has prevented blue screens for me. Like I said, it only happens on some computer chipsets.
Click to expand...
Click to collapse
I am glad you add this for those who have their Connect to PC settings to disk drive. I will make a note to the OP I usually have it on charge only when I mock around with the phone.
arcybarrios said:
This would be great if I knew linux BUT since I don't maybe if I add snap shots of what I did and what it looks like? What is typed in the OP seems to be along the lines of what you are suggesting.
Click to expand...
Click to collapse
Well not much is needed, lots of commands are the same between windows and linux, but "ls" can be useful, it's the equivalent of "dir" in windows. That's probably the only thing that would be useful for this, so you could list out all of the apps in the app directory to get the exact name.
And that's odd, I have to CD to the directory that adb is in to run adb, otherwise it won't work. Maybe I did something wrong when downloading it, I suppose I could just throw adb.exe into my user directory. Great tutorial overall though
The car home app actually has nothing to do with navigation and latitude will not have any effect on the checkin service.
I'll PM you the easy way to delete these things and you can post it in the OP if you want to. S-OFf is required to delete apps while the phone is booted normally, this is done while the phone is off.
KCRic said:
The car home app actually has nothing to do with navigation and latitude will not have any effect on the checkin service.
I'll PM you the easy way to delete these things and you can post it in the OP if you want to. S-OFf is required to delete apps while the phone is booted normally, this is done while the phone is off.
Click to expand...
Click to collapse
By off you mean while the phone is in recovery right?
MusicMan374 said:
By off you mean while the phone is in recovery right?
Click to expand...
Click to collapse
No, it's actually off because it doesn't require the phone for the first part.
For the guy that wanted the Linux commands:
Obviously, to find the apps:
Code:
ls /system/app/
Code:
ls /data/app/
Packages:
Code:
pm list packages
This may be needed before proceeding:
Code:
mount -o rw,remount /system
To remove /system apps:
Code:
rm -f /system/app/<apk name>.apk
pm uninstall <package name>
For apps in data just replace /system/ with /data/
arcybarrios said:
Here’s my list so far:
Amazonmp3.apk
AppPack2.0.apk
Music.apk (speaker)
mytouchmusic_1.1.5_13.apk
Faves.apk
FavesWidget.apk
Flickr.apk
Teeter_NoHTC.apk
VpnServices.apk
HtcTwitter.apk
com.htc.TwitterWidget.apk
MagicSmokeWallpapers.apk
I also deleted these and from what I am reading one of these is what is causing the problem if not all of them
NewsReader.apk
com.htc.NewsReaderWidget.apk
RSS.apk
Stock.apk
com.htc.StockWidget.apk
FriendStream.apk
com.htc.FriendStreamWidget.apk
SocialNetworkProvider.apk
IM.apk
EDIT: BTW I made both a nandroid and Titanium backup
Click to expand...
Click to collapse
Accounts and sync will require socialnetworkprovider I would expect
danfrance said:
Accounts and sync will require socialnetworkprovider I would expect
Click to expand...
Click to collapse
Might be for your google accounts since stock android has that apk as well as sense and (as far as I know) every other flavor of UI.
I think that this thread should definitely be stickied in this forum, it's pretty rich with info for noobs
So I assume that we're listing apk's for sense right? Well that's a long list. This is what I've got so far but stopped at the facebook app. I'll make a full list and upload it.
Calendar.apk
Calendar.odex
CalendarProvider.apk
CalendarProvider.odex
Clicker.apk (used to calibrate LatinIME or HTC_IME Keyboards)
Clicker.odex
com.htc.FriendStreamWidget.apk
com.htc.FriendStreamWidget.odex
com.htc.MusicWidget.apk
com.htc.MusicWidget.odex
com.htc.NewsReaderWidget.apk
com.htc.NewsReaderWidget.odex
com.htc.StockWidget.apk
com.htc.StockWidget.odex
com.htc.TwitterWidget.apk
com.htc.TwitterWidget.odex
com.htc.WeatherWidget.apk
com.htc.WeatherWidget.odex
Flashlight.apk
Flashlight.odex
Flickr.apk
Flickr.odex
FriendStream.apk
FriendStream.odex
HtcCalculatorWidget.apk
HtcCalculatorWidget.odex
htccalendarwidgets.apk
htccalenderwidgets.odex
HtcClockWidget.apk
HtcClockWidget.odex
htccontactwidgets.apk
htccontactwidgets.odex
HtcFacebook.apk
HtcFacebook.odex
FLASHEX 2.05 (unified release 4)(Release Date: 5/2/2012)
Description
Flashex is designed to allow people using an Android device to watch hulu and some other restricted sites with Adobe Flash Player and a properly configured web browser as if it was a Windows PC. Dolphin HD Stock Browser(choose "request desktop site" in menu each time) is a good choice but any browser that allows you to act as Desktop via settings should work.
Note: Dolphin HD has some issues with full screen video at the moment so I have switched over to useing the stock browser and selecting "request desktop site" from the upper right-hand menu for now this works and has good full screen performance on FlexReaper and Stock ICS 4.0.3.
How it works
The script will look for libflashplayer.so then attempt to create a copy, edit the copy, and copy the edited version back. It stores the edited copy, and writes it over the default file each time it's run. It will check the version of the current libflashplayer.so file each time before it copies the edited version over. If libflashplayer.so's version has been upgraded or downgraded it will make a new copy, edit, write it back and store the new one to use each time. I suggest using Script Manager to run the script at boot once you run it the first time manually to make the first edited copy.
What's New in Version 2.05?
-Added a few more checks for libflashplayer.so to help improve troubleshooting and configuring on different ROMs and to eliminate the possibility of a hang if libflashplayer.so is not readable.
(Still waiting on feed back and/or -x mode debug output reports. feel free post them or better yet PM them to me)
What's New in Version 2.04?
-Added support for Custom BusyBox from CynogenMod (BusyBox 1.19.4-cm9) when testing the Busybox version
What's New in Version 2.03?
-Added checks to verify Busybox location, permisssions, and version to verify compatability and inform the user if they need to update/reinstall busybox or make a configuration change.
-Various minor refinements.
-Can now safely be test run on ANY device since it will verify the location of all required elements prior to performing any task.
NOTE: This doesnt mean it will enable hulu on an old 500mhz 2.2 device, just that it should be safe to use to modify Adobe Flash on any device capable of properly running it.(If your Adobe Flash is installed in a diffrent location you will need to configure the script to point it's install directory, or put a copy of your libflashplayer.so file into the Flashex2 directory and name it AND_libflashplayer.so and copy the resulting WIN_libflashplayer.so back by hand if you prefer.)
What was new in Version 2.02?
-Fixed various typoes in output messages
-Added a fix for people having issues with strings, grep etc returning as not found when /system/xbin is either not in the users default $PATH or is too low in the list to get used.
What was new in Version 2.01?
-Many minor bug fixes
-Scripts have been unified into a single script.
-Made some changes to how version checking is done
-Script is safer, more reliable, and easier to use over all.(at least IMO hehe)
-Automatic re-edit of edited source file, when either an upgrade or downgrade is detected. This allows the script to be run at boot via Script Manager, or other while still leaving, Adobe Flash to auto update.
-Script is now a single executable file that will both hex edit Adobe Flash(each update), and copy the edited file over to /data when needed.
-Improved version detection
-Improved output messages
Some notes on running during bootup
Once you have decompressed the Flashex2 folder and flashex.sh script to /mnt/sdcard/Flashex2 you will be able to run it automatically at boot via Script Manager if you wish. I currently have been using it this way. I have tested it performing the hexedit during a boot up. It works fine.
Known Limitation
Note: This only applies to auto-running the script via Script Manager, Cron, what ever It takes about 2 minutes with a Tegra 2 to complete the hexedit of the file.
Because of this when booting after an update to libflashplayer.so it will be editing the file for a min or two after your home screen shows. You will want to wait 3 min or so to be safe before you try to use Adobe Flash. This will ONLY happen when the version changes. Since Adobe Flash isn't changed that often it's not a big deal.
The rest of the time, it will be the same version so it will just take a few seconds to copy the file over. This allows you to just watch when you like even right after a system boot.
Install Instructions
Quick Directions:
Download file, unzip/extract the Flashex2 folder and it's contents, copy it to the sdcard to end up with /mnt/sdcard/Flashex2/flashex.sh. Run flashex.sh as root. Set web browser to Desktop. Enjoy watching hulu.
Full Directions:
When using Flashex205.zip via a File Manager like Astro for example.
1) Either download Flashex204b.zip directly to your tablet, or copy it to a micro SD card via PC.(note: you could unzip the contents in Windows if you prefer)
2) Save, Copy or Move Flashex205.zip to /mnt/sdcard/ It has a folder inside already of the correct name.
3) Open Flashex205.zip, then copy/paste the whole folder to /mnt/sdcard/
Note: After you do this you should have a folder named Flashex2 on your internal sdcard example: /mnt/sdcard/Flashex2
4) Inside the Flashex2 folder from the zipfile is flashex.sh
5) run flashex.sh either via terminal emulator or with an app like Script Manager.
The script "can" be run without root, BUT it will only make the hexedited file. It MUST be run as root if you also want the script to install the edited file so you can watch hulu. You can also copy the file by hand.
When using flashex205.tar.gz via a terminal emulator do the following.
1) Either download the file directly to your tablet, or copy it to a micro SD card.
2) Copy or Move the file to /mnt/sdcard/
example(copy): cp /mnt/external_sd/flashex205.tar.gz /mnt/sdcard/
example(move): mv /mnt/external_sd/flashex205.tar.gz /mnt/sdcard/
3) unzip and untar the Flashex folder and flashex.sh script from flashex205.tar.gz
gzip -d /mnt/sdcard/flashex205.tar.gz
tar -xvf /mnt/sdcard/flashex205.tar
Note: If you get an error saying not found. Your trying to install it in a diffrent location then it's currently configured you can probably figure out how to make it work easy enough. Just remember to set the path to the script inside the script it's self so it knows where make/read the edited file.
4) Now change working directories and run the script.
cd /mnt/sdcard/Flashex2
5) Run the script(su is optional, but running as root it wont copy the edited file over)
su
sh flashex.sh
Note: I suggest using sh before the script name though it's not nessesary if the path to sh at the top of the script matches yours.
Confirmed Compatable Device List(Make sure you are rooted if you want to use the script to install the modified file)
Acer Iconia A100, A200, A500 HC or ICS, FlexReaper ------ Use Latest Version
Samsung Galaxy S 4G rooted modified Gingerbread 2.3 --- Use Latest Version
Samsung Galaxy Nexus LTE ----------------------------------- Use Latest Version
Asus Eepad Transformer Prime ------------------------------- Use Version 2.2 or Latest Version
Motorola Droid Razr ------------------------------------------- Use Latest Version
HTC EVO 3D --------------------------------------------------- Use Latest Version
HTC EVO 4G running mikg v11 ------------------------------- Use Latest Version
Note: Any Device that is compatable with Adobe Flash and capable of playing hulu videos(500 Mhz or better ARM7 CPU 256 MB ram, Android 2.2 or better) that has been rooted and has busybox installed should be compatable
If you are attempting to use a Busybox older then v1.18.1 You will have to change a value at the top of the script before attempting to run it since I'm not sure how old of versions are 100% compatible.
===============================================
ATTN: SUPPORT, QUESTIONS, COMMENTS
If you need help getting it to work for your device and cant post in this section you can follow this
->SUPPORT LINK HERE
You can PM me or you can also try me on Twitter
Legal Info
Flashex205.sh was made by NoSudo for personal use
anyone may use it or change it but I retain creative
licence for my work. You should only take credit for your
changes.
I take no reponsablility for anyone elses actions. If you break
something or violate any rules it's on you.
If you wish to try and make money on it or use it for any comercial
venture I expect to be contacted and informed so I may negociate
an acceptable for profit licence with compensation.
This software is FREE and yours to enjoy, give away, edit, use for Non-Profit purposes ONLY.
A NOTE ON VERSIONS!
I recommend the use of the latest version Flashex204.sh. If you have old versions installed. MAKE SURE YOU RUN THE RIGHT ONE. It's up you to reconfigure Script Manager etc. so don't forget or it will keep running the old one.
ALSO Please remember to hit that Thanks button if you find my script useful.
I have been doing a little version testing.
I can confirm that flashex v2.01 does edit other versions so far I have tested it with. I just tested with 11.1.115.7 and it works fine via xxd. Im going to test on Android with Busybox's hexdump next.
I can also confirm that it works on 11.1.111.8 since my tablet just auto-updated. I simply ran the script and updated my hexed version from 11.1.111.7 to 11.1.111.8 as designed.
Just tried the new version and still a no go. See the pic for the full error.
Ran with terminal emulator, gscript, and root explorer. Same error for all.
And you have the .so file from the old version thread.
.so path: /data/data/com.adobe.flashplayer/lib/libflashplayer.so
ICS Leak .012.
busybox 1.19.3
Joecascio2000 said:
Just tried the new version and still a no go. See the pic for the full error.
Ran with terminal emulator, gscript, and root explorer. Same error for all.
And you have the .so file from the old version thread.
.so path: /data/data/com.adobe.flashplayer/lib/libflashplayer.so
ICS Leak .012.
busybox 1.19.3
Click to expand...
Click to collapse
Weard here is the output I got running a test edit. I used the same 2.01 script just modified so it doesn't write to my adobe flash. Kind of sandbox I guess. As you can see it reads and edits it fine. I'll look some more.
Command: '/mnt/sdcard/FLASHEX2_vtest/flashex_vtest.sh'
-------------
Out: $ exec sh '/mnt/sdcard/FLASHEX2_vtest/flashex_vtest.sh'
=================================================
Source Files Doesn't Exist
Destination File: /mnt/sdcard/FLASHEX2_vtest/DST/libflashplayer.so
Destination Ver: Adobe Flash says AND(Androiud) v1111157
Detected READ access for /mnt/sdcard/FLASHEX2_vtest/DST/libflashplayer.so
Created /mnt/sdcard/FLASHEX2_vtest/cache Sucessfully... Checking...
/mnt/sdcard/FLASHEX2_vtest/DST/libflashplayer.so preparing to copy and edit file........
Copy: /mnt/sdcard/FLASHEX2_vtest/cache/libflashplayer_PREMOD looks good =================================================
Preparing to create a hexdump.........
Dont panic...This could take over a minute on a Tegra 2..
Its Converting an 8MB or so Binary on a little tablet...Just wait its fine Created a hexdump of /mnt/sdcard/FLASHEX2_vtest/cache/libflashplayer_PREMOD
=================================================
Preparing to edit /mnt/sdcard/FLASHEX2_vtest/cache/libflashplayer_HEXDUMP..
This might take a minute too.... /mnt/sdcard/FLASHEX2_vtest/cache/libflashplayer_HEXDUMP has been edited... =================================================
Converting /mnt/sdcard/FLASHEX2_vtest/cache/libflashplayer_EDITED to binary...
Binary File: /mnt/sdcard/FLASHEX2_vtest/WIN_libflashplayer.so created...
Checking Binary file /mnt/sdcard/FLASHEX2_vtest/WIN_libflashplayer.so... =================================================
HEXEDIT SUCCESSFUL File: /mnt/sdcard/FLASHEX2_vtest/WIN_libflashplayer.so now reads as Version: WIN 11,1,115,7
Sent from my A100 using XDA
I'm at a bit of a loss as to why it's not working for you Joecascio2000. I'm still looking into it.
I can confirm if I copy your libflashplayer.so v 11.1.115.7 to my device and run the script on it. I AM able to edit the file and get a good binary at the end. I was able to run it via Terminal IDE, Terminal Emulator, and Script Manager.
Going by the error your getting I would say the issue could be related to Busybox. I know you say you have 1.19.3(same as mine)
what happens if you try this from a Terminal
strings /data/data/com.adobe.flashplayer/lib/libflashplayer.so | grep "AND 1[0-2],[0-9]*"
You should get back a list of strings out of the binary, and one of them should say something like "AND 11,1,115,7"
If that doesnt return the correct line, what does this return
strings /data/data/com.adobe.flashplayer/lib/libflashplayer.so | grep "AND 1"
This should return "AND 11,1,115,7" if it doesn't then I would take a closer look at your strings, and grep binaries which would indicate a possible issue with your copy of Busybox or maybe your $PATH as it could effect what version gets used when running a shell command.
I still feel very confused by it working on my device and not on yours with the same file. However I also feel confident that since it works on my A100 we can get it working on yours too without much hassle. We just need to figure out what the deal is.
NoSudo said:
Sent from my A100 using XDA
Click to expand...
Click to collapse
Yeah so weird. I just tried it again after uninstalling flash and re-installing it. Same error. Maybe I'm executing it wrong. This is what I put:
su
sh /mnt/sdcard/Flashex2/flashex201.sh
It does seem to work, just give me an error with the .so file.
EDIT: and both string lines return "no such file or director". I just copy and pasted them in, maybe I did something wrong?...maybe its busybox...?
I just copy and pasted them in, maybe I did something wrong?
Click to expand...
Click to collapse
copy and past of the strings command above should work yes. You can even just run the following
strings /data/data/com.adobe.flashplayer/lib/libflashplayer.so
If that give you bad command or something then you have an issue with either Busybox or your $PATH
$PATH is a special variable that unix/linux/android uses to store the locations of programs like grep, strings, etc. It specifies various directories commands are stored in. If the directory strings is stored in IS NOT in your path the script will not be able to access the command, so I can't say at this point which issue it in fact is, but I'm 99% sure it's one of those two things at this point.
That error is kinda old and can be erroneous. I'll look at that area a little closer later and see.
If you rerun the script after a successful edit it will tell you if it was successful BTW. If /data/data/com.adobe.flashplayer/lib/libflashplayer.so is already edited and is the same version as the WIN_libflashplayer.so Source file it will just print out a message that displays the actual version string from inside both files. The output will look somthing like this
Source File: /2.01FLASHEX_Dev/Lib_Version_Testing/WIN_libflashplayer.so
Source Ver: Adobe Flash says WIN(Windows) v1111157
Destination File: /2.01FLASHEX_Dev/Lib_Version_Testing/DST/libflashplayer.so
Destination Ver: Adobe Flash says WIN(Windows) v1111157
=================================================
It looks like you dont need make any further changes at this time.
Make sure you have set your browser to Desktop in settings(try Dolphin HD)
a
Joecascio2000 said:
Yeah so weird. I just tried it again after uninstalling flash and re-installing it. Same error. Maybe I'm executing it wrong. This is what I put:
su
sh /mnt/sdcard/Flashex2/flashex201.sh
It does seem to work, just give me an error with the .so file.
EDIT: and both string lines return "no such file or director". I just copy and pasted them in, maybe I did something wrong?...maybe its busybox...?
Click to expand...
Click to collapse
It could be. If you don't have a "strings" command the script wont work for you in it's current state. I made extensive use of strings to read info out of the binary files for version checking and to confirm the edit.
The error you got is something you could get from no strings command. It could also just be that the location "strings" is installed if it IS NOT in your $PATH for your ENV this would be a simple fix, in fact I'm tempted to add a PATH="" export PATH line back into the script just in case of stuff like this. I had removed it thinking it overkill.
Two diffrent folks seem to have a Busybox installer available via play.google.com. I use the one from J Rummy because it's only 1.99 for the Pro version instead of 4.99 and so far it has all the features I want and even has 1.19.4 available currently. It sounds like you may just need to figure out the location of the strings command and make sure that directory is exported as part of your $PATH. Let me know if would like assistance figuring this out.
NoSudo said:
It could be. If you don't have a "strings" command the script wont work for you in it's current state. I made extensive use of strings to read info out of the binary files for version checking and to confirm the edit.
The error you got is something you could get from no strings command. It could also just be that the location "strings" is installed if it IS NOT in your $PATH for your ENV this would be a simple fix, in fact I'm tempted to add a PATH="" export PATH line back into the script just in case of stuff like this. I had removed it thinking it overkill.
Two diffrent folks seem to have a Busybox installer available via play.google.com. I use the one from J Rummy because it's only 1.99 for the Pro version instead of 4.99 and so far it has all the features I want and even has 1.19.4 available currently. It sounds like you may just need to figure out the location of the strings command and make sure that directory is exported as part of your $PATH. Let me know if would like assistance figuring this out.
Click to expand...
Click to collapse
When I open terminal emulator the first line reads:
[email protected]:/ $ export PATH=/data/local/bin: $PATH
Also, I can't update busybox because for my current root method 1.19.3 is required.
Joecascio2000 said:
When I open terminal emulator the first line reads:
[email protected]:/ $ export PATH=/data/local/bin: $PATH
Also, I can't update busybox because for my current root method 1.19.3 is required.
Click to expand...
Click to collapse
You don't need a newer version of Busybox I'm running the same version.
it's your $PATH I will post an updated version that includes an Export PATH line to resolve after I eat some dinner.
for now you can copy/paste this into a terminal before running the script. Im guessing if you run that, then the script it will work
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/system/sbin:/system/xbin:/system/bin:/data/local/bin:/vendor/bin; export PATH
Darn...still isn't working. Lol my tab hates me. See the pic I think its a little different.
here's a link the one below is a little low res: http://i.imgur.com/uP9ZR.png
Joecascio2000 said:
Darn...still isn't working. Lol my tab hates me. See the pic I think its a little different.
here's a link the one below is a little low res: http://i.imgur.com/uP9ZR.png
Click to expand...
Click to collapse
It looks like you might still be missing the strings command. Because it doesnt look like anything is getting passed to grep. It looks like strings didnt run, so grep tried to look for the search expression as a file name.
what do you get if you type
ls -la /system/xbin/strings
or even just
ls -la /system/xbin
I show a symbolic link for /system/xbin/strings that points to Busybox. If it's in another location with your version of Busybox you just need to make sure the strings command is located in the path you use.
If you dont have a strings command at all for some reason since you have the same version of Busybox 1.19.3 you should be able to just make a Symbolic Link in /system/xbin(or what ever space you are configured to use) called strings that points to busybox. All those buxybox commands are symlinks to the same binary file in reality.
NoSudo said:
It looks like you might still be missing the strings command. Because it doesnt look like anything is getting passed to grep. It looks like strings didnt run, so grep tried to look for the search expression as a file name.
what do you get if you type
ls -la /system/xbin/strings
or even just
ls -la /system/xbin
I show a symbolic link for /system/xbin/strings that points to Busybox. If it's in another location with your version of Busybox you just need to make sure the strings command is located in the path you use.
If you dont have a strings command at all for some reason since you have the same version of Busybox 1.19.3 you should be able to just make a Symbolic Link in /system/xbin(or what ever space you are configured to use) called strings that points to busybox. All those buxybox commands are symlinks to the same binary file in reality.
Click to expand...
Click to collapse
Both commands showed: not found, however, I looked in /system/xbin/ and busybox and strings are in that folder. Also, right under strings is ( -> busybox )
Joecascio2000 said:
Both commands showed: not found, however, I looked in /system/xbin/ and busybox and strings are in that folder. Also, right under strings is ( -> busybox )
Click to expand...
Click to collapse
Yep the
strings --> busybox
is the way strings and the other Busybox commands look the
"--> Busybox" is to show what it links to, but the name is still strings. It's sorta like a shortcut in windows in a way.
Anyway that means you should be able to use strings try copy/paste this before you run the script in the same terminal.
PATH=$PATH:/system/xbin; export PATH
that take what ever you currently have for a $PATH and add /system/xbin to it
you can view your $PATH by typing
echo $PATH
Either way if your Busybox is properly installed into /system/xbin this should return a few lines out the binary. Just to confirm it's a working command on your system.
/system/xbin/strings /data/data/com.adobe.flashplayer/lib/libflashplayer.so | grep "AND"
I will come up with an up date to check for the location of Busybox and use hard paths for the commands, later in the week. That should avoid this issue coming up in the future.
First off thank you for helping with my pain-in-the-you-know-what tablet.
But sadly still a no go. I did get some more info though: http://i.imgur.com/oVxBz.png
It showed AND 11,1,115,7.
I think it's either the way I'm putting in the commands or the way my tab is rooted.
Joecascio2000 said:
First off thank you for helping with my pain-in-the-you-know-what tablet.
But sadly still a no go. I did get some more info though: http://i.imgur.com/oVxBz.png
It showed AND 11,1,115,7.
I think it's either the way I'm putting in the commands or the way my tab is rooted.
Click to expand...
Click to collapse
First off, Your very welcome. I actually enjoy this kinda stuff as long as I have time.
Next, Since it DID respond with AND 11,1,115,7 I am sure you CAN use the script, once updated. I will be working on an update this weekend. I may have a revised version made today, if I get an extra hour to dedicate to make the changes.
The issue seems to be, for what ever reason your device is having an issue with /system/xbin not being in your PATH or PATH and ENV not working as it should, BUT since /system/xbin/busybox and the symlink /system/xbin/strings both work when you type the full path, it's not a big deal.
I'm also going to try to write in a feature to test the location and version of Busybox and make sure it lists "strings" as a defined function, so the script can identify and resolve the issue when possible.
Updated Version should resolve any issues with the script not being able to use strings, grep etc on some systems.
Also check here for information on configuring Terminal Emulator to work correctly with Busybox. This I belive would get the old script working for those that had issues also for what it's worth.
NoSudo said:
Updated Version should resolve any issues with the script not being able to use strings, grep etc on some systems.
Also check here for information on configuring Terminal Emulator to work correctly with Busybox. This I belive would get the old script working for those that had issues also for what it's worth.
Click to expand...
Click to collapse
This is with the new version 2.02 and after configuring Terminal Emulator:
http://i.imgur.com/Rb458.png
Joecascio2000 said:
This is with the new version 2.02 and after configuring Terminal Emulator:
http://i.imgur.com/Rb458.png
Click to expand...
Click to collapse
Man I am at a total loss as to what your system is doing. That just doesn't make any sense at all. Are you running the script or Copy/Pasting lines into Terminal? What Busybox are you running anyway, not the version where did you get it? It seems totally defective honestly.
The script should work fine for you at this point TBH. Heck it works for me on my Linux PC too when I change the paths, and swap out xxd for hexdump and change the pattern format.
At this point I can only conclude that either you have a bad version of Busybox or you are doing something wrong.
Here is an example of what I mean
BUSYBOXPATH="/system/xbin"
if [ -e "$BUSYBOXPATH/busybox" ]&&[ -e "$BUSYBOXPATH/grep" ]; then
echo "Found BusyBox in $BUSYBOXPATH"
BSYBX_VER=`$BUSYBOXPATH/busybox | $BUSYBOXPATH/grep "BusyBox v"`
echo "Version: $BSYBX_VER"
else
echo "Unable to confirm location of BusyBox, please configure the script"
exit 3
fi
This statement says if /system/xbin/busybox and /system/xbin/busybox exist to echo "Found" etc.
Your output has those lines, so those commands HAVE to exist in those locations or it would respond with
Unable to confirm location of BusyBox, please configure the script.
However the script is unable to read the Version line off busybox because busybox isnt spitting out anything or maybe it's been modified and no longder displays the correct response. Again even a Desktop PC with Linux on it get's this response from Busybox.
What happens when you just type
/system/xbin/busybox
Do you get anything?
You should get something like;
$ busybox
BusyBox v1.19.3 (2011-11-22 01:37:10 MST) multi-call binary
Copyright (C) 1998-2011 Erik Andersen, Rob Landley, Denys Vlasenko
and others. Licensed under GPLv2.
See source distribution for full notice.
Usage: busybox [function] [arguments]...
or: function [arguments]...
BusyBox is a multi-call binary that combines many common Unix
utilities into a single executable. Most people will create a
link to busybox for each function they wish to use and BusyBox
will act like whatever it was invoked as!
Currently defined functions:
[, [[, addgroup, adduser, adjtimex, ar, arping, ash, awk,
basename, brctl, bunzip2, bzcat, bzip2, cal, cat, chgrp,
chmod, chown, chroot, chvt, clear, cmp, cp, cpio, crond,
crontab, cut, date, dc, dd, deallocvt, delgroup, deluser,
df, dirname, dmesg, dos2unix, dpkg, dpkg-deb, du, dumpkmap,
echo, ed, egrep, eject, env, expand, expr, false, fbset,
fdflush, fdisk, fgrep, find, fold, free, freeramdisk, fsck.minix,
ftpget, ftpput, getopt, getty, grep, gunzip, gzip, halt,
head, hexdump, hostid, hostname, httpd, hwclock, id, ifconfig,
ifdown, ifup, init, ip, ipcalc, kill, killall, klogd, last,
length, less, linuxrc, ln, loadfont, loadkmap, logger, login,
logname, logread, losetup, ls, lzmacat, makedevs, md5sum,
mdev, mesg, microcom, mkdir, mkfifo, mkfs.minix, mknod,
mkswap, mktemp, more, mount, mt, mv, nameif, nc, netstat,
nslookup, od, openvt, passwd, patch, pidof, ping, ping6,
pivot_root, poweroff, printf, ps, pwd, rdate, readlink,
realpath, reboot, renice, reset, rm, rmdir, route, rpm,
rpm2cpio, run-parts, sed, setkeycodes, sh, sha1sum, sleep,
sort, start-stop-daemon, static-sh, strings, stty, su, sulogin,
swapoff, swapon, sync, syslogd, tac, tail, tar, tee, telnet,
telnetd, test, tftp, time, top, touch, tr, traceroute, true,
tty, udhcpc, umount, uname, uncompress, unexpand, uniq,
unix2dos, unlzma, unzip, uptime, usleep, uudecode, uuencode,
vconfig, vi, vlock, watch, watchdog, wc, wget, which, who,
whoami, xargs, yes, zcat
Note: Busybox in Android will have a slightly diffrent list of functions but the version line etc is the same.
NoSudo said:
Man I am at a total loss as to what your system is doing. That just doesn't make any sense at all. Are you running the script or Copy/Pasting lines into Terminal? What Busybox are you running anyway, not the version where did you get it? It seems totally defective honestly.
The script should work fine for you at this point TBH. Heck it works for me on my Linux PC too when I change the paths, and swap out xxd for hexdump and change the pattern format.
At this point I can only conclude that either you have a bad version of Busybox or you are doing something wrong.
Click to expand...
Click to collapse
The command I'm using is
Su
Sh /mnt/sdcard/flashex2/flashex202.sh
I think it might be my version of busybox. I think its a modified version because rooting ICS on the a100 was a difficult process. It also says not to update busybox because root will be broken.
Sent from my A100 using XDA Premium HD app
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