So, I was bored at work today. I love the TeamEOS 4 CRT style screen off animation as it is a bit retro, and I was thinking about the BIOS style boot animation from a Honeycomb ROM (PRIME! by Roach2010 if I recall) and I decided to cook up one of my own.
First, I did one for the TeamEOS 4 (Android 4.2) for the TF101. Here is a preview video:
The spot light continues to shine left and right in a loop until the boot completes.
There are 4 versions of the TeamEOS 4 available:
16 GB Regular (shows 16 GB internal memory): http://db.tt/GDCmRrsy - Approximately 33 seconds until loop starts
16 GB Short (shows 16 GB internal memory): http://db.tt/ipSH5v2P - Approximately 22 seconds until loop starts
32 GB Regular (shows 32 GB internal memory): http://db.tt/RJfIKkhG - Approximately 33 seconds until loop starts
32 GB Short (shows 32 GB internal memory): http://db.tt/Gvt20bqV - Approximately 22 seconds until loop starts
Then, I decided to make one of these for those running CyanogenMod 10.1 on the TF101:
The light continues chasing inside the circle until boot finishes.
16 GB (shows 16 GB internal memory): CyanogenMod 10.1 Boot animation for TF101 with BIOS style boot.
CyanogenMod animation continues with the circular ring until boot completes.
There 2 versions available for the CM10.1:
16 GB (shows 16 GB internal memory): http://db.tt/E12GEFvc
32 GB (shows 32 GB internal memory): http://db.tt/6tjiR3E7
I also made one that says Cyanogen[SUP](mod)[/SUP] as I like that version better:
There 4 versions available for the C(m)10.1:
16 GB Long (shows 16 GB internal memory): http://db.tt/FCL62d84 Approximately 28 seconds
16 GB Short (shows 16 GB internal memory): http://db.tt/6cNrSyUu Approximately 20 seconds
32 GB Long (shows 32 GB internal memory): http://db.tt/fSUQhbfI Approximately 28 Seconds
32 GB Short (shows 32 GB internal memory): http://db.tt/i0oA8zD2 Approximately 20 Seconds
e154037 has requested the Dancing Android.
This will work on phones or tablets.
It is now square and has 2 size options:
400x400 size: http://db.tt/GGVRiQgb
800x800 size: http://db.tt/lUVFbcWz
Installation Instructions:
Disclaimer - I am not responsible for bricking your device. These are to be used at your own risk. I have personally tested these and they are fully working. Be sure to do a nandroid backup BEFORE installing these just in case.
Method 1 (works for rooted and unrooted devices)
Rename the file to bootanimation.zip
Use adb and issue the following commands (If you don't know how to use adb, please google it):
Code:
adb push bootanimation.zip /data/local/
adb shell
reboot
Method 2
Rename the file to bootanimation.zip
Use your favorite Root Explorer and copy the bootanimation.zip to /system/media/ OR /data/local/
Note that ES File Explorer does not work well for this.
I cannot take credit for most of the work on these - I only did some minor editing to the BIOS style files along with some assembly and testing.
Credit to frysee for the BIOS style boot animation from this thread: http://forum.xda-developers.com/showthread.php?t=648555 This boot animation was updated for the respective ROM names and SD card sizes.
Credit to JoinTheRealms for his work on the TeamEOS Boot Animation here that was incorporated into this animation.
Credit to CyanogenMod for the boot animation borrowed from the links of this video
As a side project, here is a copy of JoinTheRealms boot animation with it looping properly: http://db.tt/tm9J8lMB
i am getting a zip cannot be moved on es file explorer
catfishbilly said:
i am getting a zip cannot be moved on es file explorer
Click to expand...
Click to collapse
same here with ES and alot of other weird behavior when trying to move it. finally got it to delete. Re-downloaded it, and used Root Explorer to move it to /system/media with no issues. My guess is ES has issues with the zip. Always pays to have multiple file managers downloaded just for these occasions, if one doesn't work you can fall back to another file manager.
[Boot Animations] TF101 for Android 4.2 - BIOS style
I think you have to long press on the media folder with ES and change permissions to allow write access.
Root Explorer is a bit nicer I for this.
I boot looped myself trying to use ES.
I ended up using adb via WiFi and it was easier (didn't have my USB cord with me to use regular adb)
Nice Job
Nice job frederuco! Excellent work, my thanks to you, frysee and JoinTheRealms; works just fine.
On a side note when you get bored again do you think you can make one adding timduru's picture from the team roster giving him a little extra props for maintaining and developing for the tf101
thanks guys, it worked with root explorer. my tab boots kind of fast, so i just enjoy the bios part of the boot animation without the part from jointherealms.
catfishbilly said:
thanks guys, it worked with root explorer. my tab boots kind of fast, so i just enjoy the bios part of the boot animation without the part from jointherealms.
Click to expand...
Click to collapse
I added some shorter boot animations for the EOS ROM.
For the CM10 users, let me know if that is too long. I think it only takes about 25-28 seconds to get to the loop, so it should be OK. If y'all need a shorter one just let me know.
frederuco said:
I added some shorter boot animations for the EOS ROM.
For the CM10 users, let me know if that is too long. I think it only takes about 25-28 seconds to get to the loop, so it should be OK. If y'all need a shorter one just let me know.
Click to expand...
Click to collapse
I like the "Dancing Android Boot Animation" (http://androidbootanimation.com/page/3/), but it is for
phone. Any way to make it work for TF101 tab?
e154037 said:
I like the "Dancing Android Boot Animation" (http://androidbootanimation.com/page/3/), but it is for
phone. Any way to make it work for TF101 tab?
Click to expand...
Click to collapse
You want it, you got it!
From to the OP:
frederuco said:
e154037 has requested the Dancing Android.
This will work on phones or tablets.
It is now square and has 2 size options:
400x400 size: http://db.tt/GGVRiQgb
800x800 size: http://db.tt/lUVFbcWz
Click to expand...
Click to collapse
Related
For those of you who got stuck after having a MOD version of the streak 7 running 3.2 and still have yet to succeed in restoring your 2.2 image so you can do the dell update I announce to you an easier way. After all this time utilizing community resources I feel it is my time to give back.
Below is the link to the nvidia flash utility, the nvidia boot recovery drivers and image file p2 through p24 that will provide recovery to your Dell streak 7 tablet to the latest 3.2 unmodified image.
The link will have to be pasted since although I have visited often, I have yet to post very much, apparently 8 posts are required for a link and 10 posts to post to the developer page, thus you find my copy and paste link below removing the spaces between the ws' and the coms'.....
w w w .sicksubstance. c o m/Files/Streak7_3.2-Dell_img.rar
Download from the above link and extract.
-Place the nvflash folder into the root of your c drive
-Place the tablet in boot recovery mode (vol down and vol up while plugging in the tablet while it is turned off)
-Open up a command shell (if using vista or later make sure to run the shell as administrator)
-cd c:\nvflash
-restore.bat
The restore takes a bit, once it is complete power down the tablet via the pin hole, power back up and enjoy!
NOTE: If running windows vista or windows 7 be sure to boot your computer in the unsigned drivers disabled state. During boot up before the windows logo appears press F8 and choose disable unsigned driver requirement option.
I hope this helps some of you!
-redistribut(e)r
Fellow Android Developer
You should remove p23/23 unless your intention is to have everyone using the same service tag as whoever's device that came from
Recovery Image
This is directed at TheManii, on your wiki for the S7 the link is broken for the recovery image for the 506 package for the US 4G version... reason I think I need it is I'm getting gapps force closes as of last night, sure it was something I installed, but i wanted to try flashing the HC package rather than the HC zip, unless you think flashing the zip will have the same effect... I'm basing myself on experience using the Streak 5, that flashing packages is necessary to get things back in order
Wiki links are fixed now, as for the zips: the ones I have created are completely unmodified except that they remove the modem update and region checks.
It's not possible to flash the zips wrong, it's simply 2 large files that are written as-is, the update does not process them in any way at all. If anything at all goes wrong it simply wont boot at all.
Reason I supply the zips at all is because the 2xx recoveries wont load on 5xx and 5xx recoveries wont load on 2xx, due to 5xx having a bootloader update
TheManii said:
Wiki links are fixed now, as for the zips: the ones I have created are completely unmodified except that they remove the modem update and region checks.
It's not possible to flash the zips wrong, it's simply 2 large files that are written as-is, the update does not process them in any way at all. If anything at all goes wrong it simply wont boot at all.
Reason I supply the zips at all is because the 2xx recoveries wont load on 5xx and 5xx recoveries wont load on 2xx, due to 5xx having a bootloader update
Click to expand...
Click to collapse
Thanks TheManii, but before I take any drastic measures, I would like you opinion, what's the best flash on our Streak 7, to get things as they should... NVFlash, update.pkg, or update.zip?
And one more little question... the restore.bat file goes all the way to partition 24, should those last three (22,23 & 24) be deleted or just 22 & 23?
Thanks for your time in answering my questions and hookin us up with the links
Dell Streak 7 Partition Layout - xda wiki
22 is SDcard
23 is device IDs
24 is MAC address
Those should never be included in any uploaded dumps.
The install preference should go:
PKG
The zips I made
...
Using NVflash
On the EU3G i would recommend using the the pkg even after using the zip to get the correct modem update since mine has it removed
TheManii said:
Dell Streak 7 Partition Layout - xda wiki
22 is SDcard
23 is device IDs
24 is MAC address
Those should never be included in any uploaded dumps.
The install preference should go:
PKG
The zips I made
...
Using NVflash
On the EU3G i would recommend using the the pkg even after using the zip to get the correct modem update since mine has it removed
Click to expand...
Click to collapse
YOU THEMANIII, answers like that are priceless!! Thanks so much for your time
redistributer said:
NOTE: If running windows vista or windows 7 be sure to boot your computer in the unsigned drivers disabled state. During boot up before the windows logo appears press F8 and choose disable unsigned driver requirement option.
I hope this helps some of you!
-redistribut(e)r
Fellow Android Developer
Click to expand...
Click to collapse
This part really isn't necessary.
If you follow part 2 of my video series here, you just need to manually install the drivers.
http://tabletroms.com/forums/showwiki.php?title=DellStreakFAQ:How-to-Flash-your-Dell-Streak-7
This image (Only 2 to 14)can be applied to a 4G T-Mobile?
AdComa said:
This image (Only 2 to 14)can be applied to a 4G T-Mobile?
Click to expand...
Click to collapse
What you can do is modify the process so that your SD card is not rewritten and your Service tag number is not overwritten.
There is a partition.txt file, you delete the part that mentions partitions 22, 23 and 24.
There is also a restore.bat file, edit it also to not include those 3 partitions, and just to make sure, delete those 3 images from the folder, 22, 23 and 24.
Now, having said that, you are better off flashing the HC stock recovery.img via fastboot, loading the update.pkg to your EXTERNAL SD and flashing HC that way, which is the way I have had the best luck with. After flashing that, you then flash the CWM recovery for Honeycomb and then you can flash Superuser to have root, it takes all of about 20 minutes to have the cleanest install possible with that route. The NVFlash should only be used to get back to Froyo, and even still you would take the files and modify them in the same way to not flash partitions 22,23 and 24
Thanks to the wonderful information and knowledge of select user here I have been working on creating a dynamic multi-boot menu for my Archos 101 G9 Turbo 8gb Flash and thought I would contribute something back. I would still consider this to be in alpha/beta stage but basic functionality is working.
I am currently using Archos's built in menu system as I like the looks a little better than fbmenu and being a dynamic list it would be hard to specify a default image with a timeout so I currently do not need that functionality. (I may switch over to fbmenu at a later time)
The menu will look in the root of the internal storage /mnt/storage/ and /data/local/ for any files with a ext3, ext4 or squashfs extension and create a list of the images it finds. The menu currently only finds images with these extensions and the extension tells the menu what file system that image is using.
Special thanks to arctablet for creating an install tutorial.
http://www.arctablet.com/blog/archos-tablet/archos-g9-multiboot-sde-required/
Working:
Dynamic menu creation based on images in a specified folder (currently /mnt/storage/ and /data/local/)
Loading selected image as long as the kernel is compatible
Manual clearing of dalvik cache
To Do:
Clear dalvik-cache when switching images (may need to create config file to track last image)
Flashing of new initramfs and zImage from storage. (Currently looks in /mnt/storage/toflash/ but kernel is not updating)
Add option to flash correct kernel before loading an image (for switching between Android and Linux distros)
Built in system to determine an image's file system type without using extensions.
Bugs:
None that I am aware of
Updates:
V0.3a
Added zip with 4.0.6 kernel
V0.3
Fixed 10 image limit
Tracking last booted image with * in menu (saved to /data/local/bmimage)
V0.2
Added stock firmware to list
Added /data/local/ to image search directory
Added option to clear dalvik cache
(fixed) Menu finds files with extension in the middle of the name such as archos.ext4.backup
Changed menu color to android green
I am currently using the stock kernel with a modified initramfs.cpio.lzo which can be download from here
dmenu-0.3a.zip (4.0.6)(4shared)
dmenu-0.3.zip (4.0.5)(4shared)
Screenshots
Extra Info For those not failure with how the zImage and initramfs.cpio.lzo work
The zImage file is the actual kernel code that gets loaded during the boot process and the initramfs.cpio.lzo is a basic file system and init script that gets executed during start up. This specifies what image file should get loaded such as the stock Android image or another custom one. To make the multi boot menu I only modified the init script in the initramfs and and I left the zImage untouched. Since the initramfs is able to select multiple images you can actually flash it with most kernel files and it should work however you are still limited to booting what that kernel file is capable of running.
The zImage files included in the zips above are the stock kernels so they will only boot Android images. In the Ubuntu thread they are using a custom zImage file that is capable of booting both Android and Ubuntu by basically just using my initramfs with their custom zImage.
It is good
i will be testing on the 8"
10 entries : it is good may be
For the buzz
http://www.jbmm.fr/?p=27540
Problem :
I have [email protected] installed
when is reboot on recovery mode /developper
I have the multi-boot with 2 entries
-Archos.ext4.backup
-Archos.ext4.update
and nothing works
i do not view [email protected]
cajl said:
It is good
i will be testing on the 8"
10 entries : it is good may be
For the buzz
http://www.jbmm.fr/?p=27540
Problem :
I have [email protected] installed
when is reboot on recovery mode /developper
I have the multi-boot with 2 entries
-Archos.ext4.backup
-Archos.ext4.update
and nothing works
i do not view [email protected]
Click to expand...
Click to collapse
i think sirduke989 renamed the archos.ext4 from the [email protected] to [email protected]4
so it easier to distinguish them
je crois que sirduke989 a renome le archos.ext4.update en [email protected] pour pas les confondres
et :
archos.ext4.update = le nouveau firmware qui va etre flashe
archos.ext4.backup = une installation "clean" (sans apps personel), il te le faut si tu fait un "Reset Android"
Ok
I testing that
Great it 's works with [email protected]4
thanks djnilse
What about wiping dalvik-cache? Switching to a different android firmware requires it (or you'll get botloop/app FC's/other bad things)
Thank you for the feedback, I updated the bugs and to do section.
i think sirduke989 renamed the archos.ext4 from the [email protected] to [email protected]4
so it easier to distinguish them
Click to expand...
Click to collapse
I did, I also moved it to a different location. If surdu_petru does not mind I can work in the location he uses and some of his update routines.
What about wiping dalvik-cache? Switching to a different android firmware requires it (or you'll get botloop/app FC's/other bad things)
Click to expand...
Click to collapse
Good point, I did not think of that. Until I get on the fly flashing of new firmware working I will put in a manual option to clear it.
sirduke989 said:
I did, I also moved it to a different location. If surdu_petru does not mind I can work in the location he uses and some of his update routines.
Click to expand...
Click to collapse
This won't affect manual way of wiping dalvik-cache (dalvik-wipe.update file on /mnt/storage). Adjusting update routines is also not a big deal however /data/local was chosen not by accident- android doesn't make any changes there so there is no risk of deleting system image (android does clean uninstalled/not present app data/files by itself since 2.3)
updated to 0.2
Ok
please if it is possible zip the 2 files on 1 file with the good name of files
cajl said:
Ok
please if it is possible zip the 2 files on 1 file with the good name of files
Click to expand...
Click to collapse
I have made an archive with release 0.2 here:
http://www.arctablet.com/assets/too...iboot/Dynamic_Multi_Boot_menu_ArchosG9_02.zip
Also a quick tutorial and video for multiboot installation
http://www.arctablet.com/blog/archos-tablet/archos-g9-multiboot-sde-required/
Booting Ubuntu 12.04...
Is it possible to boot latest Ubuntu 12.04 beta2 image on Archos G9 tablet...?
http : / / cdimage.ubuntu.com / daily-preinstalled / current
The image has a ext4 Partition inside...
Well I tried 12.04 with the kernel from the ubuntu thread and the screen flickers when you get to the login screen. Currently with this boot menu it only if each image uses the same kernel but I am trying to add the ability to flash a new kernel when swiching images. This will make it a little easier to get a full linux distro working.
Sent from my SCH-I500 using Tapatalk
Just as a quick update I have fixed the 10 image limit so now the limit would be what fits on the screen and I am working on getting flashing of a new kernel working. I expect to have 0.3 posted this evening (us).
Updated to 0.3, still having issues with flashing a new image but I fixed the 10 image limit.
is it possible to use this with the CWM of Letama ?
Not without some modification. My boot menu is still using the loop back devices. Letama is welcome to modify my bootmenu to be compatable with his if he would like, the only changes I made in the initramfs so far are in /init and /etc/mountpoints
The toflash menu is a little bit buggy. I'm formatting the system partition successfully...
szanalmas said:
The toflash menu is a little bit buggy.
Click to expand...
Click to collapse
Yep, it currently does not work. I suspect that the issue is because it is trying to flash over the kernel that is running.
Lately I have been trying to compile the wifi drivers for Ubuntu 11.10 and once that is working I will have a good reason to want to switch kernels on the fly.
simo
Hello! I little bit in English only, sorry! but i would like to use 3 system imagess in my G9…
- (1) http://forum.xda-developers.com/showthread.php?t=1477667 and
- (2) http://forum.xda-developers.com/showthread.php?t=1592535 and
- (3) http://forum.xda-developers.com/showthread.php?t=1392167
is it possible somehow? if so, PLEASE perhaps describing in detail?
You can't use 3.2.80 firmware- kernel required for multiboot is not compatible with it. I don't know how about Ubuntu.
T-Mobile/Samsung have rebranded the Exhibit II 4G, giving us a new kernel, a bump to Android v2.3.6 and performance improvements (they claim) in the process. The phone we all love is now the Samsung Galaxy Exhibit 4G.
This stock ROM (UVLG3) is NOT vulnerable to USSD Dialer Attacks!
Rooting
Currently, zergrush will not root this phone's Android 2.3.6. Three known methods:
Root Stock 2.3.6 w/o a new kernel or ROM
root-stock.zip
Mirror
This zip will install Superuser, su and busybox, leaving you rooted, but otherwise no changes to your phone. ClockworkMod must be installed to flash this. So:
1. Flash ClockworkMod
2. Boot into ClockworkMod and flash root-stock.zip.
Rooted Community ROM (forkable)
t679.uvlg3.odex.01.zip
Mirror
(also see custom ROMs)
Linked above is Samsung's newest release for the Galaxy Exhibit, a stock rooted UVLG3 Gingerbread ROM. Busybox is also included. You must flash it via clockworkmod. Clockworkmod can be flashed with Samsung's stock recovery.
Custom rooted kernel
t679-root-v1.8.zip
Mirror
Kernel sources
The kernel is based on Samsung's kernel source. This kernel is rooted; if you flash it via stock recovery or cwm your ROM will be rooted with Superuser.apk, Busybox and the Galaxy Exhibit cwm-recovery installed. This kernel works with all Samsung Gingerbread releases.
Rooted ROM Installation
CWM Keys:
Home key = enter
Back key = back
VolUp/Dwn = highlight choice
1. Back up your data. The installation will format your data partition. I suggest Titanium Backup, available in the Market.
2. Download & copy the current t679.uv???.deodex.0x.zip to your internal sd card (if you already have a cwm installed you may use your removable card).
3. Install Galaxy Exhibit Custom Recovery . If you're already rooted, you may install from the command line, otherwise you may install from Samsung's Recovery. Samsung's recovery only sees the internal SD, so copy the cwm zip there if you just have stock recovery. Stock recovery sometimes takes more than one try to start.
Easy way to start recovery
* Make sure the cwm zip is on your internal (non-removable) sd.
* Pull the battery from your phone.
* Connect phone to your pc via usb.
* Press & hold Volume-up
* Insert battery
Your phone will boot into recovery. Press the capacitive menu button (left bottom button) when you see the open white box and droid. Choose 'apply update from sdcard' and select the cwm zip file.
4. Start Custom Recovery (cwm): Press & hold Vol-Up, then press & hold Power. Shortly after the plain white Samsung logo appears, release both buttons. Recovery should start after the Galaxy Exhibit logo.
5. Select ROMwipe. This step is required!
6. Highlight install zip from sdcard, then press Home.
7. Highlight 'choose zip from sdcard/external sdcard, depending where you placed the download in step 2.
8. Highlight the rooted rom zip file, then press Home.
After you confirm your choice, installation should take less than three minutes.
Anything you download and install is at your own risk. No guarantees or warranties are given or implied. Your first post-installation boot may be several minutes long.
Rooted Kernel Installation
CWM Keys:
Home key = enter
Back key = back
VolUp/Dwn = highlight choice
1. Back up your data. I suggest Titanium Backup, available in the Market.
2. Download & copy t679-root-v1.8.zip to your internal sd card (if you already have a cwm installed you may use your removable card).
It's recommended to install Clockwork Mod, but you can also flash the kernel from Samsung's stock recovery. Samsung's recovery only sees the internal sd, so copy files there if you don't have cwm.
Stock recovery sometimes takes more than one try to start.
Easy way to start recovery
* Make sure the cwm zip is on your internal (non-removable) sd.
* Pull the battery from your phone.
* Connect phone to your pc via usb.
* Press & hold volume-up
* Insert battery
Your phone will boot into recovery. Press the capacitive menu button (left bottom button) when you see the open white box and droid. Choose 'apply update from sdcard' and select the cwm zip file.
4. Start Custom Recovery (cwm): Press & hold Vol-Up, then press & hold Power. Shortly after the plain white Samsung logo appears, release both buttons. Recovery should start after the Galaxy Exhibit logo.
5. Highlight install zip from sdcard, then press Home.
6. Highlight 'choose zip from sdcard/external sdcard, depending where you placed the download in step 2.
7. Highlight the kernel zip file, then press Home.
After you confirm your choice, installation should take less than a minute.
Anything you download and install is at your own risk. No guarantees or warranties are given or implied.
Please DO NOT PM me with support questions! They will be ignored! Post them in this thread!
Links and useful info
Galaxy Exhibit XDA Wiki
Galaxy Exhibit IRC channel
Galaxy Exhibit Themes
Custom ROMs
All ROMs listed require cwm for installation.
Peach Sunrise
RebelROM
XquiziT
CyanogenMod 9 Beta
Galaxy ExHibition
CM10 Port
AOKP (WIP)
CM7 (WIP)
CM9 Pure Nexus
Stalled, partially working
AOKP
KEMIUI
Help! I keep getting FCs!
Custom kernel for Rebel Rom
This is custom kernel 1.8 packaged specifically for RebelRom, tested on
version 3.0.8. This package includes kernel & modules only.
rrkernel.zip
Mirror 2
Stock 2.3.6 via Odin
uvlg3.odin.zip
Mirror
Adb for Windows
winadb.zip unzip and copy to your c:\Windows directory
Mirror
Flash2Stock
Flash2Stock (flash via cwm) will install stock UVLG3 and Samsung's stock recovery, un-rooting
your phone, removing ClockworkMod and returning your phone to factory condition.
uvlg3.flash2stock.zip
Mirror
SwapSD
SwapSD This simple app allows you to swap internal "usb storage" (aka /sdcard) and your removable sdcard (aka external_sd) so your larger "external sd" is mounted as "/mnt/sdcard/" and the smaller sd internal memory is mounted as "/mnt/sdcard/external_sd". This is done by changing a file called vold.fstab in your phone's /etc folder. The original device vold.fstab file is backed up to /etc/vold.fstab.backup when this app first runs. Your data on /mnt/sdcard and /mnt/sdcard/external_sd is not touched in any way whatsoever.
Dropbear (flash via cwm)
is a software package that provides a Secure Shell-compatible (ssh) server and client. It is designed as a replacement for standard OpenSSH for environments with low memory and processor resources, such as embedded systems. This archive also includes the scp and rsync utilities.
dropbear.zip
Mirror
Bloatware
These apps are safe to delete. You may also freeze them using Titanium backup.
AnalogClock.apk
Browser.apk (Only if you use an alternative browser)
Dlna.apk
DownloadProviderUI.apk
DualClock.apk
DualClock.apk
IQ-tmobile-release-signed-zipaligned-v1.1....
JobManager.apk
KiesAir.apk
MobileBackup-unsigned_v3.3.02.apk
MyFiles.apk(Only if you have an alternative File Browser i.e. Astro File Manager)
SamsungWidget_Program...
Swype.apk
TetheringManager2.apk(Only if you don't use T-Mo's tethering service)
TouchWizCalendar.apk
TouchWizCalculator.apk
TwCalendarAppWidget.apk
VideoPlayer.apk(Only if you have an alternative video player)
VoiceRecorder.apk
WiFi-Calling.apk(If you don't use it)
ZinioSettingsProvider.v2.03.3331.TMobile....
sihome-signed-tmo-android-8.apk
talkback.apk
tmobile_m4m_3_0_15.signed...
vvm-signed.apk
Partition Table
/dev/block/mmcblk0p1 secboot2 partition map
/dev/block/mmcblk0p2 dbl.mbn (boot loader)
/dev/block/mmcblk0p3 osbl.mbn (boot loader)
/dev/block/mmcblk0p4 MBR extended partition table
/dev/block/mmcblk0p5 EMMCBOOT.MBN (boot loader, has odin download mode)
/dev/block/mmcblk0p6 amss.mbn
/dev/block/mmcblk0p7 emmcparam.bin
/dev/block/mmcblk0p8 boot.img (linux kernel)
/dev/block/mmcblk0p9 adsp.mbn (baseband)
/dev/block/mmcblk0p10 rmt
/dev/block/mmcblk0p11 rmt
/dev/block/mmcblk0p12 persist.ext4
/dev/block/mmcblk0p13 recovery.img (linux kernel+initrd for recovery mode)
/dev/block/mmcblk0p14 param
/dev/block/mmcblk0p15 system.ext4
/dev/block/mmcblk0p16 cache.ext4
/dev/block/mmcblk0p17 data.ext4
/dev/block/mmcblk0p18 preload.ext4
/dev/block/mmcblk0p19
/dev/block/mmcblk0p20 all 0's
/dev/block/mmcblk0p21 all 0's
/dev/block/mmcblk0p22 all 0's
/dev/block/mmcblk0p23 all 0's
/dev/block/mmcblk0p24 all 0's
/dev/block/mmcblk0p25 all 0's
/dev/block/mmcblk0p26 all 0's
/dev/block/mmcblk0p27 efs (encrypted fs)
/dev/block/mmcblk0p28 /mnt/sdcard
Credits:VanillaTbone,s0unds,KemikalElite, jocala, Wildchild, bpear96, camcory, Intercepter and others. If your name belongs here or you have info that needs to be added please speak up!
Zergrush
Rooting the original Exhibit II via zergrush: Please read DooMLoRD's Easy Rooting Thread
Please note that this method does not work with Android 2.3.6 on the Galaxy Exhibit.
ClockworkMod
Galaxy Exhibit cwm-based recovery v6.0.1.2
6.0.1.2 has new features, including better support for both external and internal SD cards, faster backups and restores with a new backup format that de-duplicates data in between backups. Exclusive features for Galaxy Exhibit include:
wipe menu with rom wipe
All system wipes under one menu: rom (system/cache/data),cache,dalvik,cache/dalvik,data.
Stack zip files for installation:
Flash cm9 & gapps, etc. Select as many zip files for installation as you choose. Flash them all with one command.
Install system images:
Drop any recognized system image into a folder on your phone and recovery can flash it. You can even drop the entire contents of an odin tar/md5 file in a folder and cwm recovery will flash it all automatically.
All images must conform to Odin naming standards:
adsp.mbn
amss.mbn
boot.img
cache.img.ext4
preload.img.ext4
recovery.img
system.img.ext4
Click to expand...
Click to collapse
This is regular interface, not touch.
cwm.6012.t679.zip
Mirror
To initially install Galaxy Exhibit Custom Recovery you need to:
1. Copy cwm.galaxy.exhibit.zip to your internal SD storage.
2. Boot into stock recovery:
Starting recovery: Press & hold Vol-Up, then press & hold Power. Shortly after the plain white Samsung logo appears, release both buttons.
Or a different method some find easier:
* Pull the battery from your phone.
* Connect phone to your pc via usb.
* Press & hold Volume-up
* Insert battery
Recovery should start after the Galaxy Exhibit/T-Mobile logo.
3. Press the capacitive menu button (left bottom button) when you see the open white box and droid. Choose 'apply update from sdcard' and select the cwm.galaxy.exhibit.zip file.
If you already have cwm installed, to update follow the steps above, booting into your current cwm instead of stock recovery.
Should you need to install ClockworkMod via Odin:
cwm.6012.tar
Mirror
We have needed a new thread for our phone, thanks for making this!
kingdavidd said:
We have needed a new thread for our phone, thanks for making this!
Click to expand...
Click to collapse
You're welcome. Just fyi, I'm no longer going to post in the old dev thread or discussion thread. I also plan to make good use of the <reserved> posts above for Galaxy Exhibit links and information.
I'm committed to this phone for the long haul, so thanks for joining me here. I hope this thread will be used for any general discussion of our Galaxy Exhibits (concerning development as well). I also hope folks will evangelize and point people here rather than carry on in the older abandoned OP threads.
Nice job jocala! Thanks.
Sent from my Calculator with Android.
So the rom is stock exhibit after the update... Other than being rooted and the custom recovery, correct? Much rather flash that then go back to stock then update. Thank you for that.
Sent from my SGH-T679 using xda premium
jocala said:
You're welcome. Just fyi, I'm no longer going to post in the old dev thread or discussion thread. I also plan to make good use of the <reserved> posts above for Galaxy Exhibit links.
I'm committed to this phone for the long haul, so thanks for joining me here. I hope this thread will be used for any discussion of our Galaxy Exhibits.
Click to expand...
Click to collapse
Yea all the old threads OP's abandoned them and the original post had all old info, I am glad you're dedicated to this phone!
SurgeRush said:
So the rom is stock exhibit after the update... Other than being rooted and the custom recovery, correct?
Click to expand...
Click to collapse
Yep, that's it. Purely stock except for root, busybox & recovery.
Cant wait to see what roms come out of this
Sent from my SGH-T679 using XDA
The rebranding works out nicely, if for no other reason than providing a point of demarcation.
Many props to Jocala who is awesome, as we all know. It can't be said too often but we'll try not to overdo it. :thumbup:
Sent via frazzled carrier pigeon -->
Ditto here man. We'd all be screwed & tattooed without his know-how. BTW worth mentioning I had to refreeze all the bloatware again after the update. Noticed how the phone lagged and then checked Titanium Backup. Sure enough all the crap was back. Also re-check settings in programs like Juice Defender and Rom Toolbox. I had to re-enter some of them again as well.
Has anyone managed to update successfully while already being rooted? (Specifically by Zerg Rush method)
I've yet to received the OTA notification and still holding off If i should update using the software. Stock ROM but just rooted. Holding off on "flashing" anything as I've never done it before.
ArtfulDodger said:
Ditto here man. We'd all be screwed & tattooed without his know-how.
Click to expand...
Click to collapse
That's not true at all, but thanks for saying it. Anyone handy with *nix can do what I do, and 95% (or more) of the techniques I use were pioneered by others here on xda.
Hey so i was just looking, and had a few questions, the rom you say is stock and odexed, are all the official roms odexed? Also just curious is the extra file in ur rooted rom, that are not in stock, extra like tweaks or part of odex or are they needed? some are just text and xml so im sure prolly wouldnt hurt, but not exatly the same as stock. Also depending on the answers to the above would you mind looking at the rom i made or maybe releaseing one that has no extras just root and busybox so stock kernel and recovery?
edit: also just noticed theres an extra folder(not in stock) T9DB just wondering what they are for or what they do, looks to be like something for the keyboard?
edit2: i think i answered one of my questions stock is odexed., other questions still wondering about though. It also looks like you might have taken a different approach to rooting the rom, maybe you could look at mine see if its just complete fail or not lol and or maybe pming me, to avoid clutter, on how you did urs.
ive made sooo many edits lol but just wanted to add too, thanx for all the work you have done for us.
cars1189 said:
Hey so i was just looking, and had a few questions, the rom you say is stock and odexed, are all the official roms odexed? Also just curious is the extra file in ur rooted rom, that are not in stock, extra like tweaks or part of odex or are they needed? some are just text and xml so im sure prolly wouldnt hurt, but not exatly the same as stock. Also depending on the answers to the above would you mind looking at the rom i made or maybe releaseing one that has no extras just root and busybox so stock kernel and recovery?
edit: also just noticed theres an extra folder T9DB just wondering what they are for or what they do, looks to be like something for the keyboard?
edit2: i think i answered one of my questions stock is odexed., other questions still wondering about though.
Click to expand...
Click to collapse
The phones I use have always come odexed. I know of no other root methods. I don't have time to beta your rom, but feel free to post a link. I'm sure you'll have volunteers
cool, and no problem, and basically all i did was use the dsixd kitchen and added root(from in the kitchen menu), does that not really root it? does that just change the file permissions? cause when i did that it added the su binary so i assumed it did, but doesn't look like thats what you did, urs has a mkroot folder that im gonna guess is used by the update-script to add the su binary and such.
cars1189 said:
urs has a mkroot folder that im gonna guess is used by the update-script to add the su binary and such.
Click to expand...
Click to collapse
You are correct
Flashed the ROM, all went smooth, but I can't install anything from the Market. Every time I try I get "ERROR "Blah" Could not be downloaded due to an error." Any ideas? Did a full romwipe and dalvik before flashing. The markets not even updating to Play store either.
** Work-In-Progress: Ubuntu Touch Preview is just that.. a PREVIEW. Do not complain about missing features, etc. The OS isn't nearly ready for primetime. **
Curious as to how the Ubuntu Touch Preview looks? Why not load it on your Droid Bionic and see for yourself.
Instructions:
1. Make a Titanium Backup and/or backup in recovery of your current Android (or just keep it on another rom-slot). This preview is fun to play with but not a replacement for something as developed as CM 10.1
2. Download the Bionic Mini-Android base for Ubuntu Touch and place it on your device:
[03/01] http://goo.im/devs/Hashcode/targa/ubuntu-phablet/ (use the newest one)
3. Download the latest Ubuntu Touch Preview Filesystem .zip from Ubuntu:
http://cdimage.ubuntu.com/ubuntu-touch-preview/daily-preinstalled/current/quantal-preinstalled-phablet-armhf.zip
If the above link is broken, use this link for a full listing of the current build files (download the quantal-preinstalled-phablet-armhf.zip .. soon to be raring-preinstalled-phablet-armhf.zip):
http://cdimage.ubuntu.com/ubuntu-touch-preview/daily-preinstalled/current/
4. Reboot into Safestrap. Create a NEW 2GB ROM in the #4 slot.
IMPORTANT:
4a. Install the quantal-preinstalled-phablet-armhf.zip FIRST, and then the phablet-2013xxxx.zip SECOND.
5. Reboot and Enjoy
FIRST BOOT TAKES A LONG TIME. AND THERE'S NO BOOT ANIMATION. BE PATIENT (MAYBE 3-4 MINUTES).
WHAT WORKS:
Display
Touch screen
Wifi
Audio
WHAT DOESN'T WORK:
There's so much that is still being implemented into the Touch version of Ubuntu, that this list could get pretty long.
Barely any sensors other than touchscreen work. IE: no rotation, etc. Ubuntu WIP issue.
No HD codecs (still being worked on) Ubuntu WIP issue.
No screen timeout / auto blank -- be careful when walking away from the device. Need to press the power button to turn the screen off. Ubuntu WIP issue.
RELATED UBUNTU TOUCH LINKS:
(Some of these describe how to install it on devices -- you can ignore those instructions and follow the above)
Ubuntu Touch Wiki: https://wiki.ubuntu.com/Touch/
Release Notes: https://wiki.ubuntu.com/Touch/ReleaseNotes
IRC Channel on freenode.net: #ubuntu-touch
thank you... let's give it a shot!
So does data work yet? Because you never mentioned data yet.
Sent from my XT875 using xda premium
silvernirvash said:
So does data work yet? Because you never mentioned data yet.
Sent from my XT875 using xda premium
Click to expand...
Click to collapse
wifi work... boot up in +/- 2minutes
So no data yet lol. Oh and where are the system settings I don't see any other then the quick toggle settings and the soft keys don't actually do anything it seems. Oh also they are always lit up...... Kinda annoying. But so far pretty cool lol
Sent from my XT875 using xda premium
Big thanks Hashcode, I will give this a try
Whaaaaaaaat!? Ubuntu touch on the locked down Bionic!? I'm happy to see your still holding it down hear hash, even with the DNA being fully unlocked and s-off we don't have even 1/4 of the development that the bionic has let alone a nexus phone. Kudos brudda.
Sent from my HTC6435LVW using xda premium
Is raring the latest build? Quantal seems downloads an empty zip, and it says it was last updated today. Thanks!
3. Download the latest Ubuntu Touch Preview Filesystem .zip from Ubuntu:
http://cdimage.ubuntu.com/ubuntu-touch-preview/daily-preinstalled/current/quantal-preinstalled-phablet-armhf.zip
If the above link is broken, use this link for a full listing of the current build files (download the quantal-preinstalled-phablet-armhf.zip .. soon to be raring-preinstalled-phablet-armhf.zip):
http://cdimage.ubuntu.com/ubuntu-touch-preview/daily-preinstalled/current/
I had a little trouble installing. I created a 2 gig slot using #4 and on the first file I got an error message. The log went like this...
Installing update...
assert failed:getprop(ro.product.device) =="groupe
E: error in /sdcard/download/raring-pre-installed-armel+(status 7)
error flashing zip '/sdcard/download/raring-preinstall
Does anybody know what the problem could be? Bad download maybe? Thanks in advance!
Sent from my DROID BIONIC using xda app-developers app
ok so got that issue resolved an I gotta say, sweet rom can't wait til it's stable enough to use as a dd!
Sent from my DROID BIONIC using xda app-developers app
Not having any luck with this on my Droid Bionic.
SS 3.11
2GB Slot on ROM#4
raring-preinstalled-phablet-armhf.zip (6/1/13)
phablet-20130412-cm-targa.zip
Installs fine, boots up to blank screen and just sits there...
I've let it sit for 30 minutes...It does nothing...
The hw keys are lit, and the screen is backlit.
What am I doing wrong?
TIA,
Flash
..
If you updated to official rooted jellybean you are out of luck, you can try to use dd command from linux terminal to copy each partition back to .905 to your phone while in recovery but you might brick your phone while doing it, I posted what all the partitions were if you have a large enough sdcard you can put every IMG on your phone in recovery from and type
dd if=/sdcard/IMG of=/dev/block/correctimgtoreplace
Skip replacing recovery and hope you didn't brick your device. I have done it before to get back to 895 but I got pretty close to bricking my phone while doing it. I finally got it to work but wouldn't recommend doing it unless you know alot about linux/Android and your phone.
mbmloader mmcblk1p1
mbm mmcblk1p2
mbmbackup mmcblk1p3
ebr mmcblk1p4 this is the extended partition for the rest of the partition table
bploader mmcblk1p5
cdt.bin mmcblk1p6
pds mmcblk1p7
lbl mmcblk1p8
lbl_backup mmcblk1p9
logo.bin mmcblk1p10
sp mmcblk1p11
devtree mmcblk1p12
devtree_backup mmcblk1p13
bpsw mmcblk1p14
boot mmcblk1p15
recovery mmcblk1p16
cdrom mmcblk1p17
misc mmcblk1p18
cid mmcblk1p19
kpanic mmcblk1p20
system mmcblk1p21
cache mmcblk1p22
preinstall mmcblk1p23
webtop mmcblk1p24 has been linked to vendor on ICS and up lost a lot of space in update
userdata mmcblk1p25
emstorage mmcblk1p26
sgpt mmcblk1p277
Has there been any work done since this thread was made? If there's been an update I'd like to know what the update contains.
Sent from my XT875 using xda premium
I think that Ubuntu for phones will be great on Bionic. We've already got convergence, in a way, and if you could run Android apps on it, I'd be set!
Sent from my XT875 using xda app-developers app
I don't see why it couldn't run android apps on it I mean under the skinning they are both Linux so..... It's very possible. Hell the new bb10 phone allows side loading of android apps and that isn't even based on Linux LOL
Sent from my XT875 using xda premium
Does 3g work on this yet? It's the only reason I wont try it. Plus last time iI tried it it sat on the black screen for about half an hour before I pulled the battery and went back to my normal rom.
There is a new Daily Driver version of ubuntu-touch 13, old quantel is 12, now there is saucy. you should take a look at it
Has anyone managed to get this to successfully boot? If it works, I'll try it.
Has anyone managed to get this booting, or tried the latest stable? With the newer version of safestrap, is it required to have such a large partition?
Hi,
I am trying to make some good boot animation. The animation itself is good, and smooth alerady, but i would like to have a boot sound along with that animation. But i ran to the issues that i can not overcome.
Now. On stock rom (I am using miui 10 from miuios.cz) I measured, that from phone turning on vibration "signal" to start of the boot animation, (that is the time when is on screen displayed mi logo static picture - not animation) it is about 13 seconds. Then bootanimation starts, and system boots up at about 37 seconds from the very beggining of the boot. That was with no sound.
But as soon as i add bootaudio.mp3 to /system/media folder, with correct permissions, bootanimation start is delayed to more than 30 seconds on that mi logo static screen! the boot time then prolongs to something over one minute, wich is pretty long. Anyways, when the bootanimation finally starts, sound plays, but then system obviously artifically speeds the animation up, because system is alerady booted (guess it booted up before bootanimation start) and i made animation to finish just few seconds before the system fully boots up, but because of delayed time of animation start, animation does not fit into the boot time.
So I want to know WHY it is happening and what can I DO about it?
Hope for quick and helpfull response. In case of need, I can send any king of *.log if I will know how to make it, what file it is and in what directory i would find it.
-------------------------------------------------------------------------------------------------------------------------
INFO about the phone:
Xiaomi redmi 4x (santoni)
MIUI 10 (miuios.cz)
root (Magisk)
custom recovery (TWRP)
Thanks!
Msprg said:
Hi,
I am trying to make some good boot animation. The animation itself is good, and smooth alerady, but i would like to have a boot sound along with that animation. But i ran to the issues that i can not overcome.
Now. On stock rom (I am using miui 10 from miuios.cz) I measured, that from phone turning on vibration "signal" to start of the boot animation, (that is the time when is on screen displayed mi logo static picture - not animation) it is about 13 seconds. Then bootanimation starts, and system boots up at about 37 seconds from the very beggining of the boot. That was with no sound.
But as soon as i add bootaudio.mp3 to /system/media folder, with correct permissions, bootanimation start is delayed to more than 30 seconds on that mi logo static screen! the boot time then prolongs to something over one minute, wich is pretty long. Anyways, when the bootanimation finally starts, sound plays, but then system obviously artifically speeds the animation up, because system is alerady booted (guess it booted up before bootanimation start) and i made animation to finish just few seconds before the system fully boots up, but because of delayed time of animation start, animation does not fit into the boot time.
So I want to know WHY it is happening and what can I DO about it?
Hope for quick and helpfull response. In case of need, I can send any king of *.log if I will know how to make it, what file it is and in what directory i would find it.
-------------------------------------------------------------------------------------------------------------------------
INFO about the phone:
Xiaomi redmi 4x (santoni)
MIUI 10 (miuios.cz)
root (Magisk)
custom recovery (TWRP)
Thanks!
Click to expand...
Click to collapse
I dont know too much about this stuff but xiaomi.eu has an option to select boot sound (in theme app). And also i think problem can be related with sounds file type. You can try to convert mp3 to ogg (or other sound file)
q0kHaN said:
I dont know too much about this stuff but xiaomi.eu has an option to select boot sound (in theme app). And also i think problem can be related with sounds file type. You can try to convert mp3 to ogg (or other sound file)
Click to expand...
Click to collapse
Hi.
Thank you for your suggestions, I tried few types of audio containers as you suggested for example: *.ogg, *.flac, *.wav and some others. The results was not good. With any type except *.mp3 of audio container, the phone behaved as if there was no boot audio at all. So, your suggestion unfortunately does not work. As for boot sound setting in themes app, I have no such option in my themes app. May be because I do not have rom from xiaomi.eu, rather miui.cz. Nevermind, you gave good suggestion anyways.
Thank you.
Anyone else?