Hi there!
As i said on a thread (bit long time ago), i had the intention of making an opensource file manager for the kin.
So i have been working on for two days, and i'm reserving this thread for its releases and descriptions.
It will be given as donationware, which means that you can take it for free and donate if you wish (or not to... )
SECURITY DISCLAIMER
- As you can imagine, by using this tool you have not guaranteed the operational state with your device and is provided "as is". You are the only responsable on the effects if could have on your device, even though i tested locally all the options for hours. Like you do for 3rd party non-certified software.
- DO NOT, i repeat DO NOT unplug the device nor close the program while writing or reading from the device. Errors states are unknown and you may scr3w up your flash memory.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- If during the usage, it takes long, WAIT for the transmission to end. Errors are handled by the program and in the last cases there are 2 to 3 levels of error treatment, notificating you in the info box and storing a brief description on the "error.log" file when it's ultra. (I'm still human, new errors can appear).
- IF during this usage the kin gets a "Connected" window and the program is clossed without closing that window, then it's the time where you can unplug and it will reset the device communication values, pluggin again. If you reach this state without doing magic, notify it to solve the bug.
Characteristics
- Libusb driver given for the kin (needs to remove the Zune one)
- Windows (XP,7) 32/64 bits. Linux (through Mono), Mac Osx(through Mono Framework) Compatibility
- Developed in pure c# (using libusbdotnet)
- Developped in layers:
----> Usb
----> Mtp Functions
----> Mtp<->Interface manager
----> Interface
Images V0.01
Requirements
- OS:
---> Windows
------->Net Framework 2.0
------->Libusb-win32 driver(provided below)
---> Linux
------->Root mode to access the devices.
------->Mono
------->Libusb 1-0 components
---> Mac OsX (Checked with Snow Leopard, PAIN IN THE ASS)
-------> Mono framework
-------> Libusb-1.0 source (sourceforge)
----------> Modern OSX compile for 64 bits. Mono needs 32 bits. Compile (as root) with:
Code:
sudo su
./configure CC="gcc -m32"
make CC="gcc -m32"
make CC="gcc -m32" install
*Note: it takes a looooooooooooooooooong time to load the first time. be patient
*Note2: if mono yells about needing X11 for Winforms, download Wireshark for OSX, which has X11 easy installation inside (needed for it).
Download links
Kin Driver (libusb-win32): (Create one with InfWizard for the kin PID and VID)
32 bit version: http://www.mediafire.com/?0nhrdn7f5je6dcx
64 bit version: (please use above version)
Source: ***Still needs a bit more documentation, cleaning and binary testing for errors ***
* Note that i DONT have a 64 bit hardware, so i based its compatibility on the failed running in my Windows 7 (aka "this is for other architecture error")
** Note that to use this driver you MUST remove the Zune driver. I recommend to test it on a clean virtual machine first
Functions
- TreeView Kin Storage explorer (Auto Resyncs after each operation)
---> Select one or multiple items with the checkboxes next to them.
- Batch upload to the kin (to the root of the tree)
---> Select one ore more files from the selection dialog and go go go. Any file, anytime
-------> **Danger** pressing twice will upload files twice, be patient.
- Multiple file download from the kin
----> Mark any file from the tree and press "Download". The file will be downloaded to a subfolder "Downloads" next to the exe, where the tree storage has been replicated.
-------> **Danger** Folder and Playlists and other files are just logical, and have no size, so program deals with them as folders (and are created emptied in the local system at the pc)
- Multiple file delete
-------> Mark any file from the tree and press "Delete". After confirmation, the files selected will be removed from the device.
-------> **Danger** Folders are not deleted. Infobox at the bottom will inform you if a file could not be deleted.
-------> **Danger** I trickied it so the storage root could not be deleted... ahhh smart little fellas.. you were already thinking in that huh! rofl.
Known issues
- During my random tests around, i found that sometimes (dunno why exactly), the kin <-> Kino communication skips a step, messing up the mtp communication schema. The solution i used in this release was to show the root storage without children nodes. As this case is an error, you should tell me if you know a repeatable way to get it so i can retest and solve it.
To keep going with the kin, close Kino, and unlock the Connected window (slide your finger over it) and unplug & plug the usb again.
F.A.Q.
- Q: No donation button in the end?
- A: Nope. Just when it proves to be useful .
- Q: This works with Kin One devices?
- A: No. I only have access to Two (bricked) and TwoM devices, so cannot test for the little round turtle.
- Q: Do you provide a driver for Kin?
- A: Yes. It is only a bridge from the programs to the libusb-win32 functions. Unfortunately, you would have to remove the zune driver (Hardware manager) before using this one.
- Q: This bricks kin devices?
- A: At all.
- Q: This can hack the device?
- A: No. This is only a tool to upload and download files to your kin. If later it's used to hack, good anyway
- Q: Can this upload *any* file to the kin storage?
- A: Yes, binary files like exe, cab,pdf, ... will be labeled as 0x3000 (undefined filetype) for the kin.
- Q: Can i take the code and make my version called OmgKinManager?
- A: Yup. It would be a nice detail to include a little text in "about..." regarding me though
kk, apart from the above, i'm a bit stuck on the uploading procedure, doing it dinamically, not with known filesizes like i tested before.
I will try to get it to work and allow multiselection file dialogs.
Later, downloading, which is easier, as i just request files. I will try to make the selectable tree work, so several files can be downloaded at a time.
Btw, the tree is not a demo, it's my real storage, being asked to the kin. It's a long process, as i ask for the id's and their values to the kin to create a Tree structure, later parsed by the interface.
Whenever that and deletion is done, i will upload both the driver and the program/source to the public.
For Zune's functionality lost scared people, i would suggest to try on a windows virtual machine first (which i will do to test for .net framework requirements and so)
Way cool imn glad to see some progress
Nice work! I spend a lot of time on this forum reading posts and 75% of the time it's your post. You've spent a lot of time working on this project and we all appreciate it. Expect a donation from me in the near future
I'm speechless.
Hey john, you have only gotten into the media section correct? What type of things have you gotten to do if i may ask. If you want, I can help get "into" the other parts of the phone. A.K.A contacts. That's my main concern right now. I could care less of customizing the OS (which I will get to if you care to lend a hand.) Since I don't want to Say anything just yet, send me an email to [email protected]. I would like to help. I'm on my phone at the moment but tomorow I'll post how i got the phone into a writeable state (which I don't know if it still work. I've only tested twice.) If it doesn't work tomorrow, I'll donate my time during the week helping you guys. I may need to get a new battery.
P.S. It's taking me awhile to do this becuase I dont want to brick my phone. Im definately not using my enV touch!
please, read the faq above. this is not a hacking thing, but a sync one.
to be honest, i dont care about contacts cause i dont use this phone to make calls and i just wanted it to be more open. pinned apps or phone settings storage would be my only interest apart storage folder.
also, i dont want to keep secrets or long term waiting things. post what you want or dont post, but dont make it a teaser of nothing. plus i dont wanna go emailing people.
Props to you. Great utility, if it were able to get deeper into the system. Then it would be golden.
Edited for many reason
As some other forumeer seems to have gotten into the phone system, imma halt this development till acess range is shown (filesystem / storage / settings), if any.
There's no need to redo all the required mtp subsystem if we can get there by other (easier) means. OS native explorer, for example.
just go ahead and work on it in case the other guy fails. ^.^
oaktree333 said:
just go ahead and work on it in case the other guy fails. ^.^
Click to expand...
Click to collapse
Nice future-sight on this post
I just tested the file upload in the command-line again with static (coded by hand) filesizes.
Here is a new vid (hahaha famous ultralowres) where a file is upload to a just-formatted kin (CB+power).
File: dstpa.mp4 (BEP- Don't stop the party), 33.1MB
Destination: Kin storage root
Playable after upload: yup!
Mp4 tags: At all .
Just a upload showcase, not just naming the procedure .
nice nice ^.^
more freedom in file management I like.
woot goodjob
I have to give you kudos for your dedication. You kept at it even after you bricked your first kin.
I patiently await a release.
I'm trying to get the alpha release up today (tonight here).
I was in the mood and moved my coding-ass. Solved most of the problems on-the-go, but downloading.
I'm trying to allow multidownload keeping same directories on the pc... just cause i wanted to... rofl.
Hummmmm,
EVERYDAYIAMSHUFFLIN
Mmm after discovering several things, and implementing a lot of bugfixes (didnt know some things about MTP), there it is.
here, and all the versions are updated and uploaded in the 1st post, among the driver for it.
As posted there, i suggest to use it on a virtual machine with .net framework 2.0 cause the removal of the zune's driver for the kin.
You can now take your kin and (if the driver & program behave correctly), upload the files you want to the Kin.
Any type of file, any time.
I'm pretty naughty telling this, but apart from uploading....... i don't check for the file contents... so if any of you want to turn a .exe into .mp4 to look for exploits i wouldnt blame you for testing....
Double naughty if i say that Zune doesnt load info from the files itself, but only what was transfered from MTP (.. poor fella)
You can check that, cause it will only load the filename and name of the mp3, ... cause i did that (before today, i just sent filename, which makes its name blank on zune, like you saw in my video from BEP).
Hope you all enjoy and no errors appear.. rofl.
Btw, there's no donate option, cause i think it's more fair to think about that when the program is known to work, and not just alpha releases .
It's 02:53 AM here, so i better go to bed, to work tomorrow and that things....
I just wish this thing could play games lol.
@Johnkussack
Wow. I have to say thank you for putting your time and effort into really hacking this phone. I can't wait to see someone get android or wp7 running on this thing (if it's even possible with the hack you have, I'm not sure). Ether way, thanks for everything.
Related
I just found http://www.androidx86.org/ and took the time to break the dsk and the iso images to build a boot.ini via grub sitting in a directory on the disk version.
Really all you need to do is winimage the dsk from the tar.gz and then grab all the files and setup grubldr in boot.init
Anyhow It booted! On my two laptops I generally get wireless (not stable), and no sound, and vesa, maybe nvidafb on m200. The ibm t60 shows hda_intel on lsmod but files seems to be missing. The m200 didn't mention sound in the console output. The graphics didn't work on the high end (black out), but vesa did. Standby doesn't seem right but thats likely google standby behavior on a unit in gimp mode. I took some video of it running on my laptops need to upload it somewhere. I will join the x86 forum here in a moment. Just wanted to share the build here. Wish it had audio.
I don't think the android build is as advanced as what is here on the phones so development wise I'm curious if I can swap the system files from the phone to the latop but homework calls. I'm uploading the build now it says 200 minutes on my very slow connection.
Can I just say download mssmissions system.img and run the system.img or will binary-arm stuff throw me thus I need to pretend I am a gentoo user and compile stuff or is it all python and java and intependent in the system.img?
Can I merge an ubuntu and android?
Any pointers as far as setting up a dev enviroment within android? You can also run android.iso vrom virtualbox and I'm pretty sure you can tweak it to get sound but I got none if anyone is interested in that. If anyone can give me any kernel advice vs compiling known linux drivers that be nice. Can i confidently think it'll work cause I have generic linux sources. Any sage advice for ati x1300 driver or a nvidia g5500 mobile card? Also my waacom didn't work on my tablet . I just wanted to post the build someone mirror it?
When its done uploading I will edit this.. Don't want the message to time out..
I was very impressed by the browsing speed of droid on the machines...
I just sent a pm to a mod who will move this thread.
dam thats actually pretty legit lol
Drool.
Thanks I thought so too! I just found http://blog.android-x86.org/2010/01/eclair-test-build-20100115.html and my. I need to study :| android crack is bad. But eclair is out so I need to give that a shot. I just did donut. Someone who is going to go crazy please go do eclair now. please compile hoards of video and sound drivers and just upload
Download Donut prebuild. Edit boot.ini and reboot
http://rapidshare.com/files/401173367/android-system.rar.html
OR!!!!!
Download this to build your own.
http://grub4dos.sourceforge.net/
http://www.winimage.com/download.htm
http://iweb.dl.sourceforge.net/project/grub4dos/WINGRUB/WINGRUB 0.02 Build 6/WINGRB0206.EXE
http://www.androidx86.org/downloads.html
http://blog.android-x86.org/2010/01/eclair-test-build-20100115.html
(I don't think you'll need the iso, get the usb disk, but the iso is cool cause it boots in virtual box. I'm having sound issue but it looks like it is loaded. )
extract android-system from android.img from gz and put into c:\android-system
download wingrub. Run it tell it to copy stage files.
C:\grub is created
edit the attached menu.lst or use the one from the android.dsk.. Copy the splash screen.xpm.gz from the dsk root to android-system, or wherever and reference it appropriately in menu.lst.
my boot.ini
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional"
C:\wubildr.mbr = "Ubuntu"
C:\grldr="Start GRUB4DOS"
C:\CMDCONS\BOOTSECT.DAT="Microsoft Windows Recovery Console" /cmdcons
notice the grldr, Recovery Console, or Ubuntu is not necessary. After you install wingrub you can copy grldr to the root of the c:\ drive. Grldr is in:
C:\Program Files\WinGrub\GRUB
there is a file called grldr_p12 rename it to grldr and put at C:\grldr
my menu.lst in c:\grub
root (hd0,0)
splashimage=/android-system/android-x86.xpm.gz
timeout=600
title Live USB - VESA Mode
root (hd0,0)
kernel /android-system/kernel root=/dev/ram0 androidboot_hardware=eeepc acpi_sleep=s3_bios,s3_mode quiet vga=788 SRC=/android-system
initrd /android-system/initrd.img
title Live USB - Debug Mode
root (hd0,0)
kernel /android-system/kernel root=/dev/ram0 androidboot_hardware=eeepc acpi_sleep=s3_bios,s3_mode vga=788 SRC=/android-system DEBUG=1
initrd /android-system/initrd.img
title Live USB - Run Android-x86 without Installation
root (hd0,0)
kernel /android-system/kernel root=/dev/ram0 androidboot_hardware=eeepc acpi_sleep=s3_bios,s3_mode quiet SRC=/android-system
initrd /android-system/initrd.img
title Installation - Install Android-x86 1.6-r2 to harddisk
root (hd0,0)
kernel /android-system/kernel root=/dev/ram0 androidboot_hardware=eeepc acpi_sleep=s3_bios,s3_mode SRC=/android-system INSTALL=1 DEBUG=
initrd /android-system/initrd.img
title Windows at (hd0,0)
root (hd0,0)
chainloader +1
As far as differences in the directions to build your own or to just download the donut prebuild, I made the build I put grub in C:\boot\grub this is not the default. Wingrub installs the stage files to C:\grub by default so in the directions I went that route. I know it works either way cause I just redid that portion following my directions and it gave me stable mute android with wifi for about 30-50 minutes. Thats the only thing different between the build and the directions, and I believe if you move C:\grub to c:\boot\grub it would still work as they are booth search path for grldr.. Anyhow..
Or go download the cdrom iso's and burn it to cdrom/usb
hehehe
I've now entered all my bugs at:
http://code.google.com/p/android-x86/issues/list
here are some screenshots..
http://code.google.com/p/android-x86/wiki/ScreenShots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Looks promising if motivated:
http://code.google.com/p/android-x86/wiki/CustomizeKernel
eclair install not going so well initrd.gz referenced but not included on usb image. downloading iso which is good to have anyways for virtual boot in virtualbox. I hope initrd.gz and kernel are in there, but sadly they are older too. So donut maybe better after all. I'm waiting to test eclair. The donut kernel addresses system.sfs the eclair references system.img perhaps i should convert the format : I would try to do a rename but I am downloading the iso.
What does it have common with kaiser on android???
It it relates. It's like sql.
Select Interest from community where Tangent=Related
Okay man its a stretch. I just got excited at the prospect of running android on my other hardware. I should migrate my tangent babbling soon. I shouldn't even be working on this at all. I.E. what does this have to do with physics ii?
Duh.
But, when I saw it I thought ok great I boot android I'll be better able to work on android builds here maybe help out with the phantom haret issue all you l33t experts ignore. I.e. the last post about me not being up to date on stuff is crap. Seriously goto the n00b thread and fix my haret issue with instructions as clear as these..
Also kernel compiling is kernel compiling. I should go to the pure android forum and will move there I guess. But playing with this makes it much easier to work with kaiser droid. From what I've been reading it also makes me wonder about kubuntu and droid as booting android from ubuntu on os86 was mentioned and the kernel compile process seemed straight forward, so it may work? Making it work on my system I could then download all the dev stuff and maybe spew out a cross compile; but then again I'm not some sort of gcc guru. I'm just trying to get to know it is all? Why you downing me brah?
Also this build looks way less advanced maybe I can get some kind of merge on the sources here for the benefit of my 86x. It's funny how sound is an issue on 86x as much as it is here and even that says hey maybe in the 86x world with a keyboard and mouse could soomething so generic be fixed on 86x that it fixes a kaiser issue? But I agree were now in tangent territory. Need to find a better home and give it a link in a more suitable audience/ stronger relationship area.. I mean the affinity isn't that much higher.
I just got done building the last boot.ini grub environment. I'll leave it on that note and find a better place to continue this and link this to that and start over if i continue this work/effort. I just like people in this forum so I wanted them to benefit from my download. But I only was so stoked because I forget how easy it is to download an iso and boot from it when I have to do something else cause my m200 doesn't have a cdrom. Anywho..
-----
http://rapidshare.com/files/401231657/AndroidX86_2.0_and_1.6.basefiles.rar.html
move everything in the archive to the root of C:\
Download (From: http://code.google.com/p/android-x86/downloads/list)
AndroidX86-1.6: donut
http://code.google.com/p/android-x86/downloads/detail?name=android-x86-1.6-r2.iso&can=2&q=
AndroidX86-2.0: eclair
http://code.google.com/p/android-x86/downloads/detail?name=android-x86-eeepc-2.0.iso&can=2&q=
Open the each iso (WinImage, Winrar, MagicIso, or other iso program) then extract system.sfs and place it in its respective directory under grub
(i.e:
android-x86-1.6-r2.iso extract system.sfs from iso and put in C:\Grub\android-donut
android-x86-eeepc-2.0.iso extract system.sfs from iso and put in C:\Grub\android-eclair )
Edit boot.ini to include:
C:\grldr="Start GRUB4DOS"
Happy booting!
Alternatively:
You can of course boot the iso's using virtualbox
Go here: http://code.google.com/p/android-x86/wiki/Releasenotefor20091024dailybuild
for any more info or to report a bug about it.. I'll bet I don't work on this for a while..
-----
I find this interesting, and somewhat relevant, at any rate it looks fun to play with
I may have to experiment with this myself, lol, wonder if it'll work on my spare laptop? ........
Good find Tyler
also a neat find..
http://forum.xda-developers.com/showthread.php?t=553366
Looks like emulation is horrible. Thats sad its a linux kernel and it has a host someone needs to paravirtualize android? I'm reading the android thread it seems like alsa sound should just work so I'm being a ninnny nanny by not compiling stuff into the g.d. kernel, yet bug reports are abundant for lack of certain functions on different devices. grr.
This thread maybe moving soon to:
xda-developers > Android Development and Hacking > Android Software Development ?
bummer the emulator doesn't work well.. I wonder if the x86 kernel does virtualized arm support, someone need to do that...
man this is a distracting bummer. I have to compile a kernel.. I just installed a grub ubuntu too , I need to see if I can just start android in that no matter what, I may get lucky.. maybe even luckier if someone will hook it up in the other thread ..
tyler51773 said:
But eclair is out so I need to give that a shot. I just did donut. Someone who is going to go crazy please go do eclair now. please compile hoards of video and sound drivers and just upload
Click to expand...
Click to collapse
I made a working android-x86 alpha eclair 2.1 build with gapps. Designed for aspire one but also should work on vmware and vbox. Will boot and work (somewhat) on most computers (built with generic kernel config so all available .ko drivers are there) however you may have to modprobe the drivers for ethernet and wlan for your hardware. http://www.aspireoneuser.com/forum/viewtopic.php?f=90&t=19299&p=116492&hilit=aoa110#p116492
Make a bootable usb with unetbootin from the .iso is the best way to use it and you can install to hdd too from it.
Password?
just wanted to give the above aspireone-x86 build a try but the rar is password protected?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Android on your Windows Mobile HTC Device...
Supports Blackstone, Diamond, Diamond 500, Fuze, Raphael, Raphael 800, Rhodium, Tilt 2 & Topaz
This thread is dedicated to FroYo, and NOT Eclair releases!
First things first, this post is PURELY an instruction guide for noobies that aims to reflect the latest status and downloads (give or take a day).
I am not an Android developer, I do not create any of this software... this is done by far more talented people than I. This thread is purely to collate the latest info for Android on Windows Mobile HTC devices and make deploying Android on your device as simple as possible.
If you have new information that should be added to the guide (and is relevant for ALL folks) then feel free to add to the thread and I'll update the OP frequently.
These opening few posts should have ALL the latest info you need to get started (no need to trawl through the threads).
The only time you 'might' need to look in the thread is for 'breaking news' info that is no more than a day old...i.e. The Opening Post is the place!
Credits: There are too many to mention, and many are unknown, but basically the guys poring Android to our devices should be thanked, along with all those making the effort to help others test, document, or use their work (along with those who provide answers to the same questions, time and time again). These are the guys who deserve the credit. From memory...
osamaa,
babijoee,
phhusson,
herpez
scanny
klinux
Oliwe
and many more
What's New?
Latest Update: 03 Sep 2010 (V1.6)
InitRD - 20100813-b11116a
Rootfs - 20100828-c29a486
System - XDAndroid 2.2.AOSP.3.9.10.RC.2.2
Kernel - 20100830_01302 (no debugging)
Headset support - Credits to Oliwe
3D support for Blackstone/Diamond/Raphael (Rhodium/Topaz have no 3D)- Credits to Oliwe
Gallery working - Credits to Oliwe
Touchscreen Calibration is back! During first clean install, touch each of the five calibration points CAREFULLY to calibrate your screen before installation completes. Plus, general touchscreen fixes and power off support - Credits to Oliwe
Back to basics System... stock Android system.
Takes about 5 mins usage before the system starts to speed up, so expect it to be a little sluggish for the first 5 mins.
None 3D devices may not show boot screen, so please be patient during install (screen will show black)
I'd advise that once installed, you also launch SpareParts, and configure the window animations etc to 'fast'
There is a chance that after installation, some Startup.txt settings MAY be incorrect for your device. If you discover any mistake, PLEASE let me know, I will correct asap. I need your help on this guys.
How To Install (CAB Version)
Step 1 - Prepare your SD Card
Find a nice clean SD card to load Android on.
You can either format your card to get it entirely clean, or you can leave all the files you may already have on there.
*Warning* - If you have valuable data on your card, back it up. Android is usually safe, but if you can't afford to lose the data on your card, don't risk it!
Some cards have difficulty working, there is a POSSIBILITY this is due to the formatting of the card. If in doubt, format to FAT32, not FAT16
Step 2 - Download and install the CAB
Download and install the following 'full package' cab (a collection of ALL the files you'll need to run Android on your device) by clicking the XDAndroid Cab button below.
You MUST install on the Storage Card. The cab file will take a couple of minutes to install Android. Please be patient.
For those that are interested the cab files does the following:
- Installs Android in the root of the SD Card
- Deploys the correct Startup.txt for the device (the user can choose their device type)
- Adds a high res icon for Android in the root of the SD Card
- Installs a shortcut in Program Files named "Android" (launches Haret.exe)
- Installs the high res icon in the registry for WM6.5 users
Step 3 - Run Android
Android is now installed... So launch 'Android' from your Program Files menu in WinMo. Your phone should reboot into Android with 2 quick vibrations.
Have patience... the first time you do this can take a LONG time (3 mins or more). During the first boot on SOME devices, you will be asked to calibrate the screen. This is very similar to Windows Mobile screen calibration (except it's in text mode).
The reason the first boot takes longer is that Android is 'preparing' your device for the first time.
How To Install (ZIP Version)
Step 1 - Prepare your SD Card
Find a nice clean SD card to load Android on.
You can either format your card to get it entirely clean, or you can leave all the files you may already have on there.
*Warning* - If you have valuable data on your card, back it up. Android is usually safe, but if you can't afford to lose the data on your card, don't risk it!
Some cards have difficulty working, there is a POSSIBILITY this is due to the formatting of the card. If in doubt, format to FAT32, not FAT16
Step 2 - Download and extract the ZIP
Download and install the following 'full package' zip(a collection of ALL the files you'll need to run Android on your device) by clicking the XDAndroid zip button below.
You MUST unzip to the ROOT of the Storage Card. The zip file will take a short while to extract. Please be patient.
Once you've extracted the zip:
- Click Auto-Setup.exe to configure XDAndroid for your particular device
Step 3 - Run Android
Android is now installed... So launch 'Android' from your Program Files menu in WinMo. Your phone should reboot into Android with 2 quick vibrations.
Have patience... the first time you do this can take a LONG time (3 mins or more). During the first boot on SOME devices, you will be asked to calibrate the screen. This is very similar to Windows Mobile screen calibration (except it's in text mode).
The reason the first boot takes longer is that Android is 'preparing' your device for the first time.
If you want to exit Android and go back to Windows Mobile, then you need to shut down / reboot. To do so with the latest Android releases, hold down the 'end call' button until you see a menu appear.
If this fails to work, then the only option is remove the battery or press the reset button.
Known Issues
Many things are still not working properly, and the developers are fully aware of 99% of them.
SDCard - Most SDCards are working, but if you the 'waiting for SDCard' message, you should try one of these fixes (and please let us know if it works)
Fix 1: Format your card with this tool http://www.sdcard.org/consumers/formatter/
Fix 2: Edit your startup.txt file and add these entries to your cmdline:
set cmdline "lcd.density=240 msmts_calib=0x395.0x3c9.0x79.0x77 clock-7x00.a11=500 msmvkeyb_toggle=off pmem.extra=1 gsensor_axis=-2,-1,3
msmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave"
Fix 3: Tell your wife / girlfriend that you are about to make some modifications to her phone... change the ringtone and steal her old Class 2 SD Card to use with Android. She will never discover what you have done, and if she does, you'll be able to use Android to send texts to your former girlfriends ;-)
SDCard - A few users have claimed to have had trouble using their SD Cards after installing XDAndroid. Some of those have reformatted the SD Card, and it worked, some couldn't recover it. This is a minority of users, but be warned.
Camera - Not working
GPS - working
Battery Status - Highly problematic for most users (don't trust the capacity Android tells you, it's simply up and down a lot, and highly inaccurate)
WiFi - Working for most people, suspected to cause slight heat, definitely drains the battery faster than WinMo.
Audio - Speaker working for most people, microphone can have issues
Deep Sleep - Working for most people, but can have issues waking up (sometimes, it will not wake up)
GPRS - Working
3G - Working for most
PIN Code - Unknown
GSensor - Working (Screen only handles 0 and 270 degrees)
Bluetooth - Experimentally working (don't expect too much, but it's working for a number of users)
OpenGL ES - 'should' be working but only for Blackstone... more to follow soon
USB - Supported, but will NOT operate in mass storage mode. You can charge via USB and you can debug, but forget accessing your files by it.
Headphone Socket - Semi working (see FAQ for details on how to make it work)
Application Errors: It's very common to see 'Application (xxxxxx) is not responding: Force Close or Wait'. Click wait. I do not know the precise reason for this, but from what I can gather, it COULD be related to the slow speed of the SD Card causing the app response times to JUST be a little too slow for Android's liking, thus causing the message. This seems to happen more after bootup or wakeup when the device is busy doing stuff in the background.
Cannot choose ringtones: This is believed to be caused by the media scanner failing (due to discovering some filenames with none English characters). The best option of all is to use a CLEAN SD Card. But, if you insist on hosting other files on the same SD Card, you MUST make sure they have English character filenames.
reserved
reserved reserved reserved 2
Reserved
reserved reserved reserved 3
Reserved
reserved reserved reserved 4
I'm here waiting for the new release......
zsdja said:
I'm here waiting for the new release......
Click to expand...
Click to collapse
Zip now available
Cab will be here in the next hour... but...
This is major move from Eclair to FroYo, and it's slightly slower than the Eclair release (so far).
This is normal though, since many of the Eclair release issues where ironed out, but with FroYo we take a small step backwards before we can progress again...
This release is VERY untested... I used it for 30 mins on a Blackstone only... no other devices tested yet
There is newer system version
Hi,
there is new system version:
XDANDROID.2.2.AOSP.18.7.10.RC1.system.ext2.7z
Link: http://htcandroid.xland.cz/XDANDROID.2.2.AOSP.18.7.10.RC1.system.ext2.7z
I'm using this and works like charm!
Regards Jiri
jura55 said:
Hi,
there is new system version:
XDANDROID.2.2.AOSP.18.7.10.RC1.system.ext2.7z
Link: http://htcandroid.xland.cz/XDANDROID.2.2.AOSP.18.7.10.RC1.system.ext2.7z
I'm using this and works like charm!
Regards Jiri
Click to expand...
Click to collapse
This includes 19.7 system. You posted a bit too quickly, I was still editing stuff !
TheBrilliantMistake said:
This includes 19.7 system. You posted a bit too quickly, I was still editing stuff !
Click to expand...
Click to collapse
Hi,
many thanks for quick explanation and I'm sorry for so quick reply
Will be Sense UI included in this build?
Or where can I get Sense UI for Android?
Many thanks
looks like just an update from 2.1 to 2.2 - no bug-fixes or new working features, right?
downloading now to have a play
OMFG!! YES!!
android 2.2 has calendar sync to exchange (2007) natively!. this release has hammered yet another nail into WM coffin!
also it looks like my 2.1 install was broken - seems noticably faster and touchscreen seems to be working a bit more predicably.
sorry but where is the file.
:-D First post, Step 2 -> Biiig black button
sorry being a noob, all done and running.
Damo
Is this version include the chinese language?Thanks for the good work.
Sent from my MSM using XDA App
ok MarketPlace is now not working.....argggghhhhh
damianpadden said:
ok MarketPlace is now not working.....argggghhhhh
Click to expand...
Click to collapse
I think you can try to delete the data.img and restart the android then try again,good luck ^_^
Sent from my MSM using XDA App
lol...i just did that exact thing....remembered it from before on 2.1...thanks
Damo
thanks for marketplace fix. i too was having the same issue!
jura55 said:
Hi,
many thanks for quick explanation and I'm sorry for so quick reply
Will be Sense UI included in this build?
Or where can I get Sense UI for Android?
Many thanks
Click to expand...
Click to collapse
No it does not have Sense. Why would you want it?
You can get virtually all the same widgets from other sources. Sense is a massive resource drain (esp on XDAndroid), and on non 3D supported hardware
If you want the flipclock, you can get it from multiple places, the wallpaper, the wallpaper, and similar widgets are all floating around too.
Hi hackers!
IMPORTANT ANNOUNCEMENT!
WP7 Root Tools will soon be available for Mango!
More info HERE
With this tool you get root-access to parts of your WP7 device. The first release only contains a registry-editor. The file-explorer and certificate stores will follow.
This tool is in alpha stage. That means that it is not feature complete and it is not yet properly tested. This tool also provides you with high privileges with which you can alter low level settings and data on this device. All this may result in unexpected and undesired behaviour, which may ultimately damage your device. Use this tool with care and use it at your own risk. The developer of this tool cannot be hold responsible for any kind of damages, caused directly or indirectly by using this tool.
The current version of this tool can only be used on Samsung devices. A small part of the code uses Samsung-specific functionality. The performance of the tool may sometimes be slow. This is the result of the way access to the system is elevated. The goal is to make this tool device-independent and to elevate access more directly in the future, but that requires more research.
To install this you need a developer-unlocked Windows Phone 7 device. For questions about unlocking your device, please refer to the appropriate threads.
If you have bug-reports or feature-requests, please give a full description.
If you like this, hit the "Thanks" and/or "Donate to me" button.
Ciao,
Heathcliff74
Update 2011/04/06:
1. Some people requested a possibility for donations. I opened a paypal-account and the "Donate to me" should work. Thanks!
2. I get an overwhelming amount of comments and pm's. I can't answer them all right now. I will try to answer them a bit later. Sorry.
Thanks for all the support guys!
Update 2011/04/13: RELEASE "WP Root Tools 0.2 alpha"
Consider this an "interim build". Most changes are under the hood. I did a lot of refactoring for performance improvements and paving the way for the file-explorer. This version does not include the file-explorer just yet. That will be the next release. Fixes in the new 0.2 alpha version:
- Compatible with light theme.
- Navigate out of the app with back-button.
- Due to refactoring and better use of the exploit I gained a lot of performance. It is very fast compared to the previous version. Should also reduce battery drain significantly.
Update 2011/04/14: RELEASE "WP Root Tools 0.3 alpha"
Mightyhog found a regression bug in the 0.2 version. HKLM\Software\Microsoft\ was not listed properly. It is fixed in the 0.3 alpha version.
Update 2011/04/18: Info about known limitations
Yesterday I added some info here which, after more research, did not seem to be entirely correct. I misinterpreted some of the file-flags I was seeing. So here's some more detailed info about the know limitations of the current Registry Editor and the File Explorer which is coming soon. It seems that having TCB privileges still has some limitations on accessing the filesystem and the registry.
Some registry values can be changed but they are reset back to their default value after the device is restarted. One example of such value is:
HKLM\System\CurrentControlSet\Control\Power\Timeouts\BattUserIdle DWord 300
Possible explanations:
- The value is stored in a ROM registry hive. The change is made in RAM and after the device is restarted and RAM is cleared, the value is read from ROM.
- In the boot sequence of the device some xml-files which contain settings, are provisioned and overwrite changes made to the registry.
- A certain service or startup-program simply overwrites settings on system-startup.
I'm working on the File Explorer now. While testing I found out that eventhough I have TCB privileges some access is still restricted, because system-files are mapped directly in ROM. There are 2 file-flags that have impact on this:
- 0x0040 = FILE_ATTRIBUTE_INROM - This file is an OS file stored in ROM. Most files in the \Windows folder have this attribute. These files cannot be moved, modified, renamed or removed. Only a firmware update can change these files.
- 0x2000 = FILE_ATTRIBUTE_ROMMODULE - The exe- and dll-files in the \Windows folder also have this flag set. These ROM files are mapped directly into executable read-only address-space, rather than being first copied to RAM. They cannot even be accessed as a file. They can only be executed. And therefore these files also can't be copied to another location, ie. we don't even have read-access on these files. However, I may have found a way to access these files anyway. This needs a bit more research, but I hope that I can at least copy the files to a location where they can be accessed.
Everything else seems to be possible. Creating files in the \Windows folder is no problem. I hope to be able to release a version with a File Explorer soon. I guess it will be in about two weeks or something. Bear with me.
Update 2011/04/19: No luck on reading the ROM modules
I did more testing. I wanted to have at least read-access to the exe- and dll-files in the \Windows folder. As it is not possible to call CreateFile() on those files, I tried LoadLibrary(). That works. With CreateToolhelp32Snapshot(), Module32First() and Module32Next() I can enumerate the modules and find the one I loaded. I also get a baseaddress and size of the module. The problem is that I can't access that memory. I tried direct-access and I tried using ReadProcessMemory(). ReadProcessMemory() returns "Incorrect parameter" as soon as I try to access the ROM memory. Also using VirtualProctect() to unlock the memory gives me "Incorrect parameter" all the time. So it seems we won't have read-access to the exe- and dll-files in the \Windows folder for now. I will now concentrate on other functionality for the File Browser. I will try to get access to the ROM modules later on.
Update 2011/06/14: RELEASE "WP Root Tools 0.4 alpha"
It has taken me a long time, here's a new release, finally. Actually this release is not very useful yet, because the file-explorer is read-only so far. The "Cut / Copy / Paste / Delete / Rename" will follow soon. The browsing part has been extremely difficult. The main problem was the performance. Opening a folder could take up to 4 minutes. Ouch! Through a combination of multi-threading techniques, caching and combining multiple exploits I finally got this to a stable solution where browsing can be done in quite an acceptable way. The write actions don't have these performance issues, because it is not a real problem when copying a file will take a few seconds more or less. I already started on implementing this. This release also has a few minor fixes to the Registry editor, but no new functionality. I also did a lot of testing on the certificate stores. I got full read / write access to all the stores, but none of that is implemented in the WP7 Root Tools yet. That will be next.
Update 2011/06/24: RELEASE "WP Root Tools 0.5 alpha"
In this version I implemented the basic file-operations and a certificate installer.
You might wonder why I created a certificate installer, because it is already possible to add certificates. When you email a certificate to yourself and tap that attachment, WP7 will install it. But if you install like this, the certificate will always be installed in the "Root" certificate store. With my certificate installer you can also install in "CA", "My" and "Code Integrity" stores. This may be very useful for hacking attempts. You can install a certificate by browsing to the ".cer" file and tap it. The possibilities for getting a certificate file on your phone will follow below. If you start installing certificates on your phone you should consider making backups in advance. I once experienced Zune going totally bezerk after installing certs. Zune took 100% and lost connection with the phone all the time. Everything was back to normal when I deleted the certs. In this version there is no view on the certificate stores available yet. In a future version you will be able to view the contents of all the certificate store and also uninstall certificates from there.
I specifically mentioned that this version has basic file-operations, because not everything is implemented. This is what you can do:
- Cut / Copy / Paste / Delete / Rename single files
- Delete empty folders
- Create new folders
This is what you can't do (will be possible in later versions):
- Cut / Copy / Paste multiple files or entire folders
- Delete folders with content
- Rename folders
Last, but not least: I fixed some performance issues. Mainly memory-leaks in native code and in COM interop. I'm not sure if I got all leaks now, because it's not easy to do native C++ without debugger and profiler. But improvement is clearly noticeable.
This version does not have a connection with the PC. So it is not possible to use WP7 Root Tools to transfer files between the phone and the PC. You can however, use other tools to get files onto your phone and then use WP7 Root Tools to move the files to the desired location. WP7 Root Tools has write access on every folder of your phone.
How to transfer files to your phone:
Mail the file to yourself. Use your phone to go to your mailbox (not webmail). The attachment will be downloaded in the background. Then use WP7 Root Tools to navigate to \Application Data\Volatile\EmailAttachments\Attachments(number). You have to look which attachment is the one you want. The filename may be changed. The extension is the same.
Install Davux' webserver on your phone. Configure a password in that webserver. The IP of the phone is visible in the webserver app. Browse to the phone like this: http://192.168.1.2/IsolatedStorage using the IP of the phone. Upload a file to the phone. Open WP7 Root Tools 0.5 alpha. Navigate to this folder: \Applications\Data\9BFACECD-C655-4E5B-B024-1E6C2A7456AC\Data\IsolatedStore\. There's your file. You can copy it to another location if you want.
Use the Zune storage hack, described here and here. If you copied the files to your phone in this way, they will be located at \My Documents\Zune\Content in one of the subfolders. Again, the files here are renamed. You have to find the file you want and then rename it.
Have fun!
Some screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
so what you are saying is you have been able to get read/write access to the file system on the focus? or is that something you just "hope" to add later?
EDIT: I'm sorry if that came off rude, I don't mean it to be I'm just excited about the idea of file system access!
very nice tool, needed a good registry editor for the samsung focus and this is perfect. thanks!
ur f-n awesome bro!
brilliant heathcliff
Very nice - works really well with the Focus.
Do you have any timeline for the file browser part? I'd love to see functionality that can copy files on and off the system folders.
Thanks for the tool!
EXCELLENT WORK Heathcliff, finally a way to write to the parts of the registry that we wasnt able to before. NOW we are getting somewhere with the Focus!!
Nice! Looks pretty neat!
Live tiles on Samsung Focus work now!
This is exactly what I was looking for to accomplish the live tile fix on my Samsung Focus detailed on wmpoweruser.
how-to-fix-live-tiles-which-are-not-updating-without-a-hard-reset-only-developer-unlocked-devices
Thanks, dude!
TOM.
voluptuary said:
so what you are saying is you have been able to get read/write access to the file system on the focus? or is that something you just "hope" to add later?
EDIT: I'm sorry if that came off rude, I don't mean it to be I'm just excited about the idea of file system access!
Click to expand...
Click to collapse
Yes I have 'full' access to the filesystem. The are 2 exceptions I found so far, using my hack:
1. I don't have access to files that are in use by the system. So, driver-files that are currently used cannot be accessed. Not even read-access. Possible work-around: I want to try to make a kind of copy-on-boot. I've already seen locations in the registry, where I can possibly add a startup-item that copies a file to a temporary location, when the file is not in use yet. But I have not tried that yet.
2. I can't overwrite or modify files that have the systemfile-flag. But I can copy the files, as long as they are not in use. Possible work-around: I have not tried all possibilities for changing file-flags. I might be able to do that.
I do have access through the entire file-system, including the \Windows folder and to the IsolatedStorage-folders of other apps. So that should give you a full file-explorer. Working on that now.
sorcy said:
Very nice - works really well with the Focus.
Do you have any timeline for the file browser part? I'd love to see functionality that can copy files on and off the system folders.
Thanks for the tool!
Click to expand...
Click to collapse
Well, there is not really a time-line yet. I wanted to finish the first release of this tool for a long time now. But I got some serious family issues. My grandpa died and my mother got a stroke and needed brain-surgery. Surgery went ok, but she needs rehabilitation right now. You can understand that I spent a lot of time with family over last weeks. I'm not sure how things will go. Situation with my mother looks promising. I visit her every other day now and it is a long ride. So that makes planning for this tool a bit difficult. But a lot of code that I made now is reusable for the other parts of WP7 Root Tools. So that should be a lot easier. I guess it won't take too long before I can add the file-explorer and certificate-stores. Just bear with me.
Hi Heathcliff74,
I hope everything goes well for your Family. The tool is one of kind, it's the first time that I see full Registry access on my Omnia 7. It looks very promising and I cannot wait for the File Explorer part. I hope you can add more features for both the registry and file explorer. Can you export the registry? Or that is not possible yet. Also, I would love to see a favorite’s option so we can add locations of the registry as favorites. We are very grateful to you for an excellent tool. Thanks.
Big thanks for the first alpha release ! Later this day I will do some tests and reply...
GIPAQ said:
Hi Heathcliff74,
I hope everything goes well for your Family. The tool is one of kind, it's the first time that I see full Registry access on my Omnia 7. It looks very promising and I cannot wait for the File Explorer part. I hope you can add more features for both the registry and file explorer. Can you export the registry? Or that is not possible yet. Also, I would love to see a favorite’s option so we can add locations of the registry as favorites. We are very grateful to you for an excellent tool. Thanks.
Click to expand...
Click to collapse
Thanks for the compliment. Importing and exporting registry keys is a feature that is not present yet, but it can be implemented for sure. Also a favorites option can be done. I'll put that on my ToDo-list.
Very good app. Hope to see quickly the file explorer feature !!!!
Take care of your family which is the most important .
Good luck!!!!
This is huge, I confirm it works on restricted Registry keys.
You are the best
martani said:
This is huge, I confirm it works on restricted Registry keys.
You are the best
Click to expand...
Click to collapse
Thanks! Now you can update your blog, right?
Heathcliff74 said:
Thanks! Now you can update your blog, right?
Click to expand...
Click to collapse
speaking of I did post a story about this hopefully later today it should be up
domineus said:
speaking of I did post a story about this hopefully later today it should be up
Click to expand...
Click to collapse
Can you tell me where you posted that? I'd like to read that. Tnx.
Heathcliff74 said:
Can you tell me where you posted that? I'd like to read that. Tnx.
Click to expand...
Click to collapse
wmpoweruser.com
waiting for acceptance
domineus said:
wmpoweruser.com
waiting for acceptance
Click to expand...
Click to collapse
Cool
Sent from my OMNIA7 using XDA Windows Phone 7 App
As seen on the front page: http://www.xda-developers.com/android/streamline-your-app-theming-with-batchapktool/ (Thanks nikwen and Will!)
I never was overly happy with available solutions/tools/scripts for theming. So, over time my collection of homegrown batch scripts grew... and now I made a menu interface for them to collect them in a (for me, at least) logical manner. I'm gonna put them up here, maybe some people might find them useful.
BatchAPKTool differs from other Apktool/Smali-manager scripts in a few ways. It doesn't do everything everybody might find useful in a script, but it gets basic things done really fast and really neat. Where it makes sense, several working steps are combined into one command. BatchAPKTool is not a monolithic script. You can use the main menu script (!0-batchapktool-menu.bat), or you can simply click the various single scripts to get stuff done, which is usually the fastest option. There aren't a lot of folders to keep track of - everything is basically done in the root folder of the script. Just drop some APKs there and get going. BatchAPKTool automatically makes backups of the original files. And, of course, the name of the script comes from the fact that you don't select a single APK file to work with, but everything is done in batch (it's the user's responsibility to not mix system and user apps when signing/pushing/installing APKs).
On first startup the script checks if Java is installed on the computer, and sends you to the Java website if not. It also pulls the framework from your device and installs it for Apktool. After that you're good to go. The frameworks are tagged, so one can easily switch when developing for different devices.
The main menu (orange font) shows everything in order that's needed for theming system APKs. Basically, just go from option 1 to option 6 (or 7) and be done. The additional options (red font) contain features one might need as well - options 1 to 3 for non-system apps - but not as often as the main menu ones. Options 4 to 6 are just some 'internals'. It's all pretty self-explanatory, methinks:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Prerequisites are - besides Java - a custom recovery like TWRP that can mount partitions (for pushing system apps), and of course USB debugging enabled, ie. a working ADB connection.
I probably packed some safety checks in the scripts that might break operation on certain systems. Bug reports are welcome.
Tools included:
7za v9.20
aapt v0.2
adb v1.0.31
apktool v1.5.2
DeflOpt v2.07
jpegoptim v1.2.2
OptiPNG v0.7.4
signapk [?]
Stripper v1.5.5.60
zipalign
(I didn't include PNGOut for optimizing images, since it is extremely demanding, even on modern hardware... but one can easily add it to the toolchain.)
Changelog:
v1.01 Streamlined some functions, more (in)sanity checks, better integration of framework switching function
v1.00 Initial release
Cool.
Suggested it for the portal.
Awesome - thanks a lot!
A slightly updated version is coming sometime soon.
New v1.01 in first post.
Changelog: Streamlined some functions, more (in)sanity checks, better integration of framework switching function.
dfkt_ said:
New v1.01 in first post.
Changelog: Streamlined some functions, more (in)sanity checks, better integration of framework switching function.
Click to expand...
Click to collapse
Not really into cooking ROMs these days, but this tool will definately help if I enter the kitchen again and try my hand at themimg.
Thanks a lot :good:
Thanks for this, it's really productive
Thanks for this tool, Really useful & helpful!
Thanks bro, it makes so much things easier
Thanks mate. I'll give a try asap
I saw your thread from the portal and this is worth cuz it looks very useful on paper :good:
Glad you guys find it useful.
Don't hesitate to report eventual bugs, or illogical combinations of options, etc.
dfkt_ said:
On first startup the script checks if Java is installed on the computer, and sends you to the Java website if not.
Click to expand...
Click to collapse
Thanks for putting this together, but I think the download Java links in your script should point to the JRE download page instead of the main page for Java:
Java JRE download page
dfkt_ said:
As seen on the front page: http://www.xda-developers.com/android/streamline-your-app-theming-with-batchapktool/ (Thanks nikwen and Will!)
I never was overly happy with available solutions/tools/scripts for theming. So, over time my collection of homegrown batch scripts grew... and now I made a menu interface for them to collect them in a (for me, at least) logical manner. I'm gonna put them up here, maybe some people might find them useful.
BatchAPKTool differs from other Apktool/Smali-manager scripts in a few ways. It doesn't do everything everybody might find useful in a script, but it gets basic things done really fast and really neat. Where it makes sense, several working steps are combined into one command. BatchAPKTool is not a monolithic script. You can use the main menu script (!0-batchapktool-menu.bat), or you can simply click the various single scripts to get stuff done, which is usually the fastest option. There aren't a lot of folders to keep track of - everything is basically done in the root folder of the script. Just drop some APKs there and get going. BatchAPKTool automatically makes backups of the original files. And, of course, the name of the script comes from the fact that you don't select a single APK file to work with, but everything is done in batch (it's the user's responsibility to not mix system and user apps when signing/pushing/installing APKs).
On first startup the script checks if Java is installed on the computer, and sends you to the Java website if not. It also pulls the framework from your device and installs it for Apktool. After that you're good to go. The frameworks are tagged, so one can easily switch when developing for different devices.
The main menu (orange font) shows everything in order that's needed for theming system APKs. Basically, just go from option 1 to option 6 (or 7) and be done. The additional options (red font) contain features one might need as well - options 1 to 3 for non-system apps - but not as often as the main menu ones. Options 4 to 6 are just some 'internals'. It's all pretty self-explanatory, methinks:
Prerequisites are - besides Java - a custom recovery like TWRP that can mount partitions (for pushing system apps), and of course USB debugging enabled, ie. a working ADB connection.
I probably packed some safety checks in the scripts that might break operation on certain systems. Bug reports are welcome.
Tools included:
7za v9.20
aapt v0.2
adb v1.0.31
apktool v1.5.2
DeflOpt v2.07
jpegoptim v1.2.2
OptiPNG v0.7.4
signapk [?]
Stripper v1.5.5.60
zipalign
(I didn't include PNGOut for optimizing images, since it is extremely demanding, even on modern hardware... but one can easily add it to the toolchain.)
Changelog:
v1.01 Streamlined some functions, more (in)sanity checks, better integration of framework switching function
v1.00 Initial release
Click to expand...
Click to collapse
Now this will come in handy very very much! Keep up the good work and keep adding features to it
Sent from my Galaxy Nexus using Tapatalk 4
Not sure that your quote is useful.
8notime said:
Thanks for putting this together, but I think the download Java links in your script should point to the JRE download page instead of the main page for Java:
Java JRE download page
Click to expand...
Click to collapse
Yeah, that's a dilemma - the URL for the JRE direct download link is dynamic (the "1880261" part), changes with each new version. So the script would have to be constantly updated (or some really sophisticated URL crawler implemented). The lazy-but-safe way of linking to the index page is probably the best I can offer. Or maybe it's safe to link to the root JDK/JRE download page (which seems to have a fixed URL), and tell people that the JRE is enough, no need to get the JDK.
THANK YOU
Great tool. Im currently working on my dialpad theme. Great find! :good:
This is the support thread of PixelFlasher
(PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/rooting/updating with extra features).
Note: This thread is meant for issues and problems faced in Google Pixel 6 Pro devices, generic issues that are device agnostic should be discussed in the main thread.
For full details on where to download / usage and feature set of the tool, visit the main thread at XDA or the project's Github page.
Troubleshooting:
If you need support or assistance, the best way to get is by generating a support file from within PixelFlasher.
You can hit that big Support button on the main screen, or select it from the Help menu.
The generated support.zip file is sanitized (redacted) to keep your sensitive information (username device id ...) private.
Placeholder
Placeholder
this is an interesting project.
can you add a way to flash all partition/boot slots easily for new users? I think that can resolve a ton of issues. (the flash tool doesn't do this, just reinstalls some of the images like bootloader and raidio).
Alekos said:
this is an interesting project.
can you add a way to flash all partition/boot slots easily for new users? I think that can resolve a ton of issues. (the flash tool doesn't do this, just reinstalls some of the images like bootloader and raidio).
Click to expand...
Click to collapse
There's some discussion ongoing in the main thread of PixelFlasher about advanced options.
Feel free to chime in there, as this point is not specific to Pixel 6 Pro and would help all devices if it is discussed in the main thread.
📳🔥 PixelFlasher, a GUI tool for flashing / updating / rooting / managing Pixel phones.
DESCRIPTION As the name suggests this is an application to flash (update) Pixel™ phones (possibly all Google™ made phones/tablets, YMMV.) PixelFlasher at its core is a UI layer (with bells and whistles) on top of adb / fastboot commands, hence...
forum.xda-developers.com
badabing2003 said:
There's some discussion ongoing in the main thread of PixelFlasher about advanced options.
Feel free to chime in there, as this point is not specific to Pixel 6 Pro and would help all devices if it is discussed in the main thread.
📳🔥 PixelFlasher, a GUI tool for flashing / updating / rooting / managing Pixel phones.
DESCRIPTION As the name suggests this is an application to flash (update) Pixel™ phones (possibly all Google™ made phones/tablets, YMMV.) PixelFlasher at its core is a UI layer (with bells and whistles) on top of adb / fastboot commands, hence...
forum.xda-developers.com
Click to expand...
Click to collapse
Done, check the new release.
New Release:
March 24, 2022 v1.2.0.1-alpha release.
Added Advanced Configuration menu which unlocks advanced features such as:
- Flashing to both slots
- Disabling Verity
- Disabling Verification
- (More features to come)
The UI will now display the chosen Android Platform Tool's version.
Added an option to toggle verbose console output (help troubleshooting, more verbosity to come).
Stability fixes.
New Release: (See full details here on xda or here at github)
April 03, 2022 v2.0.0.0-pre release.
Major refactoring
Added Advanced (Expert) mode UI.
Basic mode keeps UI simple and hides expert features.
Support for setting active slot.
Reboot options (recovery, system, bootloader)
Moved custom ROM options to expert mode.
Added custom flashing to expert mode, can now flash to live (temporary root), or custom flash any image to any partition.
Moved flashing to both slots, disabling verity / verification to expert mode.
Many other improvements, validations and checks.
Updated documentation.
Update:
Version 2.0.1 which includes a hotfix for issue reported here.
Flawless one click update. Thanks. This going to be my default update tool.
Just used it to flash April update on my 6 Pro. Worked like a charm. Thanks.
Also used this to get to April from February and it was one of the simplest things I've ever had to do. Excellent work on this.
It keeps saying magisk is not on my phone, but it is, and it's not hidden.
According to the logs it thinks my phone is not rooted, but it is.
Edit: Followed the instructions and it updated perfectly though, just weird it thinks my phone is not rooted. Awesome app my friend, will be using this as long as it works!
Zach Alt said:
It keeps saying magisk is not on my phone, but it is, and it's not hidden.
According to the logs it thinks my phone is not rooted, but it is.
Edit: Followed the instructions and it updated perfectly though, just weird it thinks my phone is not rooted. Awesome app my friend, will be using this as long as it works!
Click to expand...
Click to collapse
Thanks for bringing this up, I'll add it to the guide,
Shell would need root permission for it to be able to do detect and use magisk.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
badabing2003 said:
Thanks for bringing this up, I'll add it to the guide,
Shell would need root permission for it to be able to do detect and use magisk.
View attachment 5581317
Click to expand...
Click to collapse
Awesome, I'll enable it for next month's update. Again, thanks for this software, it's awesome.
I toggled root access for shell and now my phone shows as rooted in Pixel Flasher.
New Release:
April 06, 2022 v2.1.0 release
Setup dedicated profile directory.
Put logs in the profile directory and maintain log history.
Plumbing for Linux support (just the flashing part is left to do).
Plumbing for new workflow.
Bugfix to handle name conflict in ROM filename.
Various minor improvements.
Update documentation.
Forgot to mention this but I was running this last night and did a dry run before the real thing, it progressed but my cable was apparently faulty so it lost connection mid way (good thing I did dry run and thank you for having it). Anyway, when it lost connection it caused the app to lock up. I closed it in task manager but the files were stuck in use and I had to find and kill the processes still open to free them up before I could start again.
Suggestion: add a check for and close of any existing processes related to the pixel flasher program if it gets reopened to avoid things being stuck in use. I work in IT so I was fine poking around to kill those processes but not everyone will be.
If you can't, maybe just add the list of processes to the OP so people can kill them on their own.
wgrant said:
Forgot to mention this but I was running this last night and did a dry run before the real thing, it progressed but my cable was apparently faulty so it lost connection mid way (good thing I did dry run and thank you for having it). Anyway, when it lost connection it caused the app to lock up. I closed it in task manager but the files were stuck in use and I had to find and kill the processes still open to free them up before I could start again.
Suggestion: add a check for and close of any existing processes related to the pixel flasher program if it gets reopened to avoid things being stuck in use. I work in IT so I was fine poking around to kill those processes but not everyone will be.
If you can't, maybe just add the list of processes to the OP so people can kill them on their own.
Click to expand...
Click to collapse
The reason that happened is because PixelFlasher is running flash-all equivalent script, which has fastboot commands in it, most fastboot commands (aside from informational ones) are blocking, i.e. it waits for device.
Because your cable was faulty and your device was not appearing connected, it got blocked waiting for it.
It's a good idea to display a message and the PID of the spawned process, the user can kill it if they wish.
I really don't want to intervene with that spawned process as it is the one flashing your phone, any glitch in there and it could mess up the phone.
badabing2003 said:
The reason that happened is because PixelFlasher is running flash-all equivalent script, which has fastboot commands in it, most fastboot commands (aside from informational ones) are blocking, i.e. it waits for device.
Because your cable was faulty and your device was not appearing connected, it got blocked waiting for it.
It's a good idea to display a message and the PID of the spawned process, the user can kill it if they wish.
I really don't want to intervene with that spawned process as it is the one flashing your phone, any glitch in there and it could mess up the phone.
Click to expand...
Click to collapse
That's a good idea as well, better to not force a closure of the process and instead inform then give the user the information necessary to close it themselves. It was definitely the fastboot process that was holding the files. Once I killed that it was fine for me to proceed. Providing a pop up with the PID or even just the process name (unless the PID is always the same) and instructions in that pop up would certainly help someone get out of a jam without needing to reboot the computer.
I've done some stuff like this project with batch but this blows that completely out of the water. Excellent work, you should be proud of what you've given to the community.
can I also root my Pixel with that?