here is a quick bootscreen i made.
i could have done a better job, but ill fix it soon.
forgot to post audio file.
Unzip SPC_animation_final.zip..
Leave bootanimation.zip as is...
---- install -----
adb remount
adb push bootanimation.zip /system/customize/resource
adb push SPC_animation_final.mp3 /system/customize/resource
----/install------
-----test----- boot sequence
adb shell bootanimation
I like it...will be testing out soon.
What changes will be made?
EDIT: Also, that youtube clip only shows 22 seconds, I thought it was supposed to be around 28 seconds for boot up...or am i mistaken?
it is.. the last couple frames in the actual bootanimation are looped until the phone starts.. the animation on youtube was in its entirety only without looping.
Okay, I finally got to it. Sorry, I was trying out the new roms from flip and hero last night.
Only one thing, is the audio low or is that just my phone? I tried turning all the volume options all the way up but it still sounds low.
I'm almost 70% sure it is my phone because I have noticed with the one droidx bootanimation I have that sometimes the "droid" will be real low and other times it will be normal.
CYBERxNUKE,
can u make this boot screen into a flammable zip?
Great work by the way....
Sent from my supersonic
Sorry flashable*
Sent from my supersonic
Note: Why not try the Froyo NAND Release by Stratulus
http://forum.xda-developers.com/showthread.php?t=831178
Its safer then trying this one..as there are a few bricked pads from this release.. so.. beaware before you play with it..
Thought I would prune this out of the Rom development thread as this way we can leave stragulus & friends to keep working on his developments..
Post all your comments to here on this new update so that we can work out the improvements and not so improvements to the update
As of 7th Feb there is still not any links to a stable SDcard upgrade.. as soon as I find one will post the links..
This Manual upgrade link is in part to the information out of this site..
http://www.slatedroid.com/index.php?topic=15457.0
the links posted below
Burntool
http://www.mediafire.com/download.php?3572bd7zfjo0r0y
Firmware version 2.1-update1 v1.9:#2852 for the Flytouch II
http://www.mediafire.com/download.php?3bkklw36b1414nd
Please use them at your own risk. cheers
dgcruzing said:
Just did it.. but. using the USB cable method..
As have been said.. change the sequence from the MSword file
1: Load the drivers for Uburn .. IUW driver in the directory otg file=secbulk.inf (xp go to dir.. right click on file then “install”)
I rebooted my xp machine at this point… ) plug in the pad.. XP should find it as a hard drive.. Might even make you install the secbulk.sys file..
2: Burn Uboot .. (no 4 in the MSfile..) I burnt the 0.6.1.5_1.4.587_GT2005 version (as yet not sure if thats the right one.. will find out as I play with the thing)
Then my pad kinda freaked out on the reboot with some screen tests.. it should tell you that this will take 2 minutes.. Mine even had a split screen thing going..
Note: I didn’t close the IUW program at anytime.. and kept plugging and unplugging things in during the process..
2: do the easy burn process as per No 1 ..MSword file.. let it burn everything in…
3: Do the reboot.. once again.. weird screen tests .. lots of blinking going on..
(DDRII study ok.. Press back.. a 615 number to the right bottom of screen.. )
Little android with a curser blinking for a while.. Then a new look Metallic Android boot screen..
Took a while to go through this process.. Some sounds then into the new look screen…
K.. hope this saves someone time.. I have just figured that with all these updates I most as well use the USB cable method now.. as the sdcard method means you have to deal with burning to a dedicated SD card..
I used this method on one of the other updates then found that the card was screwed.. i.e it had a was a bootable card.. so couldnt stay in the top slot.. and I kept on putting it in there by mistake.. if you have problems with your card and you need to bring it back to a clean slate.. use this..
HDD Low Level Format Tool
http://hddguru.com/software/2006.04.12-HDD-Low-Level-Format-Tool/
Don't try using the right click format in Windows.. it will just give you pain..
K.. its looking good.. noticed that its got VPN services now.. thats great news.. as I use it on my phone.. and was going nuts trying programs over the last few days to try to get a VPN going.. and if you are doing a stint in China like me at the moment.. you gotta have a VPN to do normal things..
Plenty of other new things in there.. and looking forward to playing with it..
I would almost say by the feel and look that we now have something worth playing with..
of course.. most of us on this thread (regulars) will be flicking these off and getting a new one within 6 months..
but its been fun playing with it as it is..
My wish now is.. can someone work out how we can get some Ram on board.. can it be done?
a little soldering?
Can it be done? I don't know enough about chips apart from popping them in and out.. but.. hey.. I would give it a go..
as this is why I brought this in the first place..
Click to expand...
Click to collapse
This was taking from the Sladedroid thread.. Creds got to Duno..
Ok, I downloaded the 2 files:
MID-2.1-update1 v1.9-2852-20110110.rar
iuw1.1-english.rar
Extracted them to a new folder.
Tried to use the new burntool to burn WWE10B_Android_393477-v9full.ius direct.
It burned, but with no changings!
Then I used the 2nd way, to make a bootable sd-card (2GB) with the new burntool.
Booted with the sd-card, Pad wrote something with updating and reboot, but no changings!
Then I decided to update the u-boot ... hmmm ... (be carefull with that!)
I used the doc in the iuw1.1-english.rar - UIWxyz-2003.doc and decided to use the u-boot-nand.bin from the
0.6.1.2_1.4.587_OV2655 folder.
(didn't know if that is/was the right file, it was a risc!)
Burned the U0 = /0.6.1.2_1.4.587_OV2655/u-boot-nand.bin
rebooted the Pad (incl. sd-card) and then it was possible for me to make the update.
During the updates are some tests from the system, I think graphic and ram ...
After reboot it was hanging on "ANDROID" (screen), was waiting about 10 min. ... then I made a reset
Pad was booting again ... "ANDROID" (screen)... then screen calibration ...
To make the sd-card full usable again delete all partitions from the sd-card on windows with the own
system tools from windows, you don't need to download a software to create/delete or format a partition on windows!
Click to expand...
Click to collapse
Reserved for FAQ's
New in this Rom..
1: No more registration hack needed.. they seem to have moved away from this.. but
2: infomarket - they have you to sign up to their new market for apps.
3: Webtv - Good idea and I can see where they are going with it. I used PPTV here in China when my Cable goes down.. so it would be nice to have some TV on the pad when I have a good connection going..
4: VPN service - Same as on the Droidphones.. this is great as now allows me to use my VPN service
5: Mypad - New file management software - getting there.. nice menu's for editing and shifting files -- Seems to be the "Helen browser.apk" (someone else can confirm this please??) as I have had a few force closes on it when going into Titaniumbackup folders and it sees the zipped files..
6: New Videoplayer - seems to not to be calling CCplayer -- does a scan of your drives and or any usb drives you plug in.. I tested a flv's, wmv, avi, mp4 all worked fine..
7:"APKManager" Also I noticed that the apk's I loaded up with "appmonster pro" as not showing in any of the screens.. but they show installed in appmonster and also in my "folder organiser" setups.. Strange.. its like the "APKManager" wants to have charge of the system.. I wouid guess that this is tied in with the "infotm market" as none of the apps show in that either..
Pruned from Rom development thread
l33tlinuxh4x0r said:
I am attempting to flash. I think that it might not be working thought because it said board undetected however it appeared to flash correctly. I am now up and it appears that I was right that it did NOT flash. The version number is the same... I'm about to flash a sdcard and see if i can flash that way.
Still no luck... Anyone have any luck flashing this new firmware??
EDIT: flashing instructions... Flash the u0 first then reboot your device will run a 2 minute test. After that it will still be wowpad. Next flash like the instructions instruct. you should now get a very stock android boot screen. That is where I am currently... I will let you know when it boots. First boot takes a while as always.
This is also the most responsive rom that I have used so far. You may have to reflash the U0 to get the camera to work. I flashed 0V2655
One more thing... I was considering getting rid of my tablet due to lag and uselessness but now after flashing this rom I am gonna keep it and use it more. Just my 2 cents letting you know how much batter this rom is.
Click to expand...
Click to collapse
l33tlinuxh4x0r said:
Once you flash U0 you can flash from sdcard but you need U0 first Also you need to make the sdcard with burn tool but the good news is that it is a new version of burn tool.
EDIT: anyone have any ideas on how to extract the ius file so that we can grab the img files from it?
Click to expand...
Click to collapse
L33.. I did a bit of a check on ius files and not sure if I headed in to the right area.. but it seems they are part of the PHP family..
I got to this thread and dug a bit deeper but then it all started to go down hill.. lol.. I think we need a dedicated Programmer that is used to dealing with these files..
http://iuscommunity.org/faq/
Pruned from Rom development thread
wahliow said:
With universal root v1.6.1, it shows your device is rooted. Than I use Root Explorer.
Not sure, what is USB debugging is all about.
Have you tried the WEB TV, quite cool.
Market is working but I prefer AppBrain.
wow at least someone tried it and is happy with it.
Click to expand...
Click to collapse
l33tlinuxh4x0r said:
Once you flash U0 you can flash from sdcard but you need U0 first Also you need to make the sdcard with burn tool but the good news is that it is a new version of burn tool.
EDIT: anyone have any ideas on how to extract the ius file so that we can grab the img files from it?
Click to expand...
Click to collapse
dgcruzing said:
if you want to change from the stock "home" launcher, go into system-apps in root and change the "launcher.apk"
I got my flying now with ADW.. the stock one is nice but stills seems to have a bit of bloat to it..
lol you can see I had to much time on my hands.. so have been able to burn this thing like 3 times today from my screwups..
Click to expand...
Click to collapse
Edit : I have gone back to stock.. Had problems loading ADW after a few boots..
started getting a system error I think it was coming out of Settingsprovider or setupwizard apk's.. I didnt document it as was getting a bit tired with the rebotting of it..
Anyone else can have a crack at it and once it is confirmed that there is a stable switch of a stable swop.. let me know and I will give it a go
Wifi noise still there.. but not as bad... it used to be that the hiss was going all the time.. but its not now.. and then the wifi.. tick tick tick. comes on once you turn it on.. and I mean.. once you turn it on in software not switch.. as I have been testing it with the switch on..
Edits: Got ADW going and setup again, but its from the first boot screen I have to launch it.. I just setup up a widget and so once system boots I tap it and it now goes in to my normal setup that I like to use..
haven't figured out which system apk's to change to allow it to take command of the Home button.. but it is working and seems stable..
I have it set with 8x8 rows, columns, with the 5 zoom screens working..
Confirmed that I can "touch" screen and add Widgets to the screen.. which is something that System home wont let you do..
I use "folder organizer" on it.. with settings of "widget size" 4x2 then in the widget settings I am using 5 rows.. and a setting of 4x2..
The nice thing about this is that I can tap it to "edit" and do a manual resizing of the box.
Note: This next Procedure is still unstable.. do not try it unless you have a Task manager that is loaded to the top bar, as you will need to use it if your tablet starts to loop out on you..
I am using Battery saver by easyfilter as it is letting me grab it from the top and kill processes..
Edit: just loaded "Multitasking Pro" on to it.. and got it to take over the home key when pushed..and the little home icon to the right hand side so now I can jump between the screens I want and not getting pushed by "home" to go to their so called wowhome.. (or the new Launcher.apk).. so once I hit home it pops up in the middle of the screen and gives me a srollable inlay list of programs that are open.. so now it feels a bit like my HTC EVO with Sense..nice..
I don't notice any problems so far and or decrease in speeds..
Edit: On booting I get to the Pause screen, it sits here fine and loads up everything in the background.. then when I flick to go to home screen I am getting forced closes of "multitasker".. (I would say it is fighting for resources with the Wowhome.... thus got to use the task manager to close things.. funny thing here is that it is not actually closing "ADW" or "multitasker" as once I clear the programs that pop up it then boots into my home ADW screen with "Multi-tasking" working and the Wowhome killed..
This is nice, but.. its the boot process that is a painful.. as I only get about 6-8 attempts to rip down the Task manager before the Tab freezes..
Next step is to rename "launcher.apk" to see if I can release it from trying to claim the resources that I want the other two to take.. so here goes...
Nope.. didn't do anything.. still getting force close's on the multitasking.. but at least by using the above method I am not having to do a factory reset as I can kill the looping process.. So now its just a matter of trial and error.. rename everything that usually starts on the wow-home and see which one is getting in the way of "multitasking"
Edit Took Multitasking off.. had to do a manual delete of it, as the program installers didn't let me take it out.. but once done I hit the "home key" and it gave me the usual option of what do I want to "map" to it.. so now I mapped it to ADW and seems to be be running fine..
confirmed that after 5 boots ADW is now home and I have renamed "launcher.apk" back to original state, will try to transfer some screen shots over the next few days..
time out from this thing..
I BURNED NEW VERSION of the PROGRAM, ALL PASSED FINE, BUT did NOT WORK CAMERA, I BEGAN burn u0 AS it is RECOMMENDED In DESCRIPTION To PROGRAMEE. AFTER BURN u-boot.bin GT2005, HAS GOT BRICK!!!
ON BUTTON POWER does NOT, NO VIBRATIONS , TRIED ANY COMBINATIONS, ALL ELSE BRICK, HELP WHO CAN!!!
WHAT have SAID HERE http://forum.xda-developers.com/showthread.php?t=831178&page=134 I killed MY flash!!!
AS NOW I CAN brighten HIS ? and can I this does their own power not using special device, which beside me simply no!
DD,
Would love to help you but I dont know what you are trying to say..
its seems you are getting a "no response" from your power buttons..
but you are also saying that you can see your Battery meter, Which kinda tells me you are seeing the header but no other screen..
I got this too when I screwed around with the change of loader to ADW..
What I did was re: burn the WWE10B_Android_393477-v9full.ius
This was to reset all the files and operation system..
I also had the problems with the camera and burnt both of the drivers for them..
works now..
Also, as a note.. I had some problems with the on/off button.. i.e not turning off right away.. what I did was just leave it for a few minutes. then Push and hold it for 4 seconds or so.. then release it.. I made sure all things plugged in to it where pulled out.. things like the USB mouse, keyboard or USB to USB cords..
my button combinations are
"Power+Home" ... gets me to sd options and factory reset
To burn recover press "Power+Home+Back" and hold it.
Then "back" to get it to burn a recover process..
K.. hope you get it back..
shall tell as I did
1)folder OV2655 burned u-boot-nand.bin
2) burned WWE10B_Android_393477-v9full.ius
board was loaded all were fine, only did not work camera.
I burned folder GT2005 u-boot-nand.bin
device was included but camera on former did not work!!!
whereupon I burned folder GT2005 u-boot.bin
the rally of the rebooting device was not included and ceased to respond to any actions. single charger at connection, fires red indicator of the charge to batteries!!!
For me just happens the same. I burn the U0 flash with the u-boot-nand.bin from OV2655 folder and everythng was fine; on the screen appear the message that i could remove the OTG and reboot but...then my FT2 just do not reboot. It only vibrates continuosly (more that one hour then I hit the reset just to stop it) without going on. The screen remain blank. I've tried all the possibile buttons combination in order to reach the programing state or the recovery console without success. I can charge the battery cause I can see the redlight on the pad...I've prepared a 2gb SD with the rom WWE10B_Android_393477-v9full.ius, made with iuw, and is inserted in the boot tf reader, without success
djidai said:
shall tell as I did
1)folder OV2655 burned u-boot-nand.bin
2) burned WWE10B_Android_393477-v9full.ius
board was loaded all were fine, only did not work camera.
I burned folder GT2005 u-boot-nand.bin
device was included but camera on former did not work!!!
whereupon I burned folder GT2005 u-boot.bin
the rally of the rebooting device was not included and ceased to respond to any actions. single charger at connection, fires red indicator of the charge to batteries!!!
Click to expand...
Click to collapse
DD,
You say you burnt the "GT2005 u-boot.bin " ...
This could be your problem.. as no where in any instructions I have read so far says.. "burn -- u-boot.bin"
But the pictures and the writing in the MSword file clearly says...
4. Buring of Uboot
Get the OTG tools ready, u-boot-nand.bin files for 10- or 8-inch tablets; connect the devices and open the IUW software as follows:
Click to expand...
Click to collapse
As I don't know enough about the .bin files, you could only hope that someone more knowledgeable chimes in with a fix for you..
As said before, I burnt GT2005 - u-boot-nand.bin - 1st... had only green for a camera..
then burnt OV2655 - u-boot-nand.bin - 2nd.. and it works like a charm..
So the moral of the story at this stage ( and it might be going in to the FAQ at the top)... dont Burn - U-boot.bin.. be careful of what you are doing.. as you could brick your flytouch...
What are these GT2005/OV .. directories you are talking about?
The rom I download has 0.6.1.2 and 0.6.1.5 directories containg u-boot-nand.bin files.
I can confirm that it's required to burn one of those to U0 first, before using the easyburn setting to flash the entire .ius file. Flashing the pad seems to take 2 steps: 1. Upload file to be flashed to device. 2. Flash uploaded file to nand. Without burning U0 first with the new u-boot version, it will *NOT* do step 2. But once you *have* flashed the new u-boot, you don't have to do it again, ever. Just reflash the *.ius file using easyburn.
To confirm that step 2 takes place, the pad will display texts and progress bars on its screen after the IUW tool has uploaded the .ius file. This takes a few minutes at most.
In the rom dev thread I have explained how to extract the ramdisk, kernel and system images from the .ius file. I'll move it to here:
stragulus said:
I'll have a go at it later if no one has beat me to it
Click to expand...
Click to collapse
uImage:
Code:
dd if=WWE10B_Android_393477-v9full.ius bs=1 skip=260096 count=2681856 of=uImage
ramdisk.img:
Code:
{ dd if=WWE10B_Android_393477-v9full.ius bs=1 skip=503296 count=64 ; dd if=WWE10B_Android_393477-v9full.ius bs=503360 skip=1 | gzip -cd - |gzip ; } > ramdisk.img
system.img (gzip header = 0x1f8b08, got it wrong before):
Code:
dd if=WWE10B_Android_393477-v9full.ius bs=3352128 skip=1 | gzip -cd - > system.img
You can use these images directly in burntool, though I think you have to flash U0 before they will actually work. Without doing that, I'm seeing the old boot image (green screen) somehow.
I was wondering whether someone form the gurus could have transformed the existing 2852 firm into a one upgradable vias a SD card (in the form of update.zip). I am afraid i will not dare do all this complicated steps (seeing already 3 owners of bricked flytouches). Thank you!
What are these GT2005/OV .. directories you are talking about?
The rom I download has 0.6.1.2 and 0.6.1.5 directories containg u-boot-nand.bin files.
Click to expand...
Click to collapse
stragulus, you would be seeing what we all have got, if they are downloading the same files..
0.6.1.5_1.4.587_GT2005
6x files.. u-boot-nand.bin, u-boot.img, u-boot.bin, spl.S, u-boot.S, u-boot-spl.bin
0.6.1.2_1.4.587_OV2655
2x files.. u-boot-nand.bin & u-boot.img
I think the problem is that they didn't read the instructions before loading files in to the IUW program
sdedo71 said:
For me just happens the same. I burn the U0 flash with the u-boot-nand.bin from OV2655 folder and everythng was fine; on the screen appear the message that i could remove the OTG and reboot but...then my FT2 just do not reboot. It only vibrates continuosly (more that one hour then I hit the reset just to stop it) without going on. The screen remain blank. I've tried all the possibile buttons combination in order to reach the programing state or the recovery console without success. I can charge the battery cause I can see the redlight on the pad...I've prepared a 2gb SD with the rom WWE10B_Android_393477-v9full.ius, made with iuw, and is inserted in the boot tf reader, without success
Click to expand...
Click to collapse
I quote myself cause the same happened to me. I've used the right .bin ( u-boot-nand.bin) file from the folder OV2655 and everything was fine until I reboot. Then my pad only vibrate...
sdedo71 said:
I quote myself cause the same happened to me. I've used the right .bin ( u-boot-nand.bin) file from the folder OV2655 and everything was fine until I reboot. Then my pad only vibrate...
Click to expand...
Click to collapse
Ouch.. any more info you can give? You used the supplied IUW tool? On what OS? Native, or in a virtual machine..? It would also help to know the board revision, which you can find if you open up the device. There's a guide on that somewhere. Can anyone else who has this problem also report this information?
I flashed the other version (GT2500) to U0 without any problems. Except that the camera doesn't work.
Here are some info.
Os Windows XP Pro
Soft for burn IUW tool
No Virtual machine
I cannot read the board rev (my pad is still closed...)
Hope someone could find a solution...
Flashing U0 is risky.. I wonder if those problems could be due to bad bits in the nand flash? Those pads really should have a non-flashable routine that allows one to reflash the bootloaders. Perhaps they can still be saved with a jtag cable..??
I was thinking the same...Do you know if there is some sort of jtag interface such as routers or Satellite STB? I made my personal jtag interface some years ago just to operate on some devices adn must be somewhere in my desktop...
who will answer? my device possible to return to lifes ?
Hello,
Has anyone successfully removed the colorful (but very annoying to me) Verizon LTE boot animation for the Galaxy 7.7?
Thank you!
I hope responding to my own message isn't a big no-no when there is something of substance (I think) to post:
After rooting and installing superuser and accessing the SCH-i810 using the "Root Browser" posted here at XDA (thank you), I determined that I could cut the two files:
/system/media/bootsamsung.qmg
/system/media/bootsamsungloop.qmg
paste them both in
/system/media/video
And now the SCH-i810 boots with no animation.
The momentary Samsung 7.7 splash remains but, otherwise nothing until the home screen appears in about 18 seconds.
Maybe this info helps someone. The Verizon boot animation was just too much color flashing and movement. The animation might be great for the store but for everyday use -- ugh.
Thanks for this. Too bad there's no way to get rid of the sound too.
Open a root explorer, go to /system/media/audio/ui.
Rename the "PowerOn.ogg" to whatever you want... eg PowerOn.ogg.bak
then its done.. no more start up sound
Hi,
yesterday i almost bricked my pad. At least i think so.
What i did was to copy a build.prop for US SKU insted of WW.
What that meant was that i couldn't get pass ASUS logo and the boot sequence didn't even start. At least i think this is a reason. Can't think of anything else. Except I have also temporarily unrooted it with OTA root keeper.
Anyway, long story short is that the only thing that helped me get my pad to life again was to manually update it to version .26 with a microSD card.
Because before this i have tried wipe data option and didn't help i have lost all my sd data, but that is a small price.
I went and started to get my pad in order and tweaks i had before. Rooted, changed build.prop and installed my own bootanimation.
I usually create my own folder for boot animations inside the /system/media and change the bootanimation_config_04.txt to pioint to my new zip. After restart, however, there was a weird bootanimation i have never seen before - android text, thats all.
I thought i did something wrong, because this always worked and i was surprised. Maybe a typo or something and the system provided with backup one....don't know.
So, i have searched and searched. No help. Whatever i did i always got that weird android animation.
Finally i have installed a bootanimation app from market, installed some random animation via that app and rebooted.
Huh, the animation changed, Dafuq?
So I looked at app settings and the location that it installs zip to is /data/local
My questions:
Is this normal? Why doesn't the old way work (/system/media), do i have a faulty installation?
Everything up until now looks pretty OK, except i am now getting a google maps crashes that i never had before.
I am away this week so i can't test everything, but it seems OK, except for some minor things. For example some games i had before cant be found on the market etc (dark knight, nfs). Maybe this is becouse of DPI changes.
Aynway, is this normal? What to do to get my /system/media way of bootnaimations back?
Thanks!
Hello, I am attempting to do something that I didn't think would be that hard and it has ran me into so many problems.
I have the Samsung Galaxy s4 Active. So I now have gained root acess, but I found out I cannot change the boot animation that easily for samsung phones because they use a different something. So I go through the trouble of downloading a ton of crap and making a animation compatible with my phone, set it up, and email it to my device copy paste to system/media and ovverrite existing. Rebooted, Said samsung then custom under it with a unlocked lock. Rebooting ever since does nothing so I gave up with that and decided to look into a mod allowing using basic bootanimation.zip like all other phones, But for Samsung active can't use Clockwork mod or whatever so I gotta get something else called Flash Gordon. When I go to download it on my phone, I get an error. First it says "Connecting to Dl.xda.developers and then it'll say Sorry, this player does not support this type of audio file and I'm at a loss because now my phone will not lock or time out the screen. When I hit the lock button it won't lock. It works fine becuase if I hold it it pulls up turn off and crap. I just made sure in settings that screen timeout is set at 15 sec and it won't timeout already tried reboot for fixing that and it didn't help. I feel like giving up right now..