yashsingh1/xdaforums huggingface dataset:
[Touch Diamond2, Pure Themes and Apps] locoo:
Hi everybody,

I want to create a animated bootup screen.

since im pretty high skilled in adobe flash pro i wanted to make a nice

bootup animation together with a relaxing sound

i know i got to use a .WAV file for the sound, i think i'll be able to add that

into my booting screen.

but my question is :

what size does it need to be ...x... ?

what format do i have to use so it will actually work ( will be neat after alot of work )

i know it is possible, i did try to search for a ''how-to'' but couldn't find one.

let me know :)

bye's

alex
[Touch Diamond2, Pure Themes and Apps] ztracenyDen:
Size is 800x480, format is animated GIF.

Use Schapman's Advanced Config to change the startup sound and animation ;)
[Touch Diamond2, Pure Themes and Apps] locoo:
thank you very much!

i will post some animated boot-up screens.

any requests?

p.s.

what is the time limit, not that i whas thinking of a boot screen

that's taking forever, but just incase ;)
[Touch Diamond2, Pure Themes and Apps] franklopez:
I have a blue angels theme with blue angles logo in black background.

some fading efect or bottom up slide with be nice.

or a y axes rotation.
[Touch Diamond2, Pure Themes and Apps] locoo:
sorry for the late responce, i working on it, its looking nice so far

the fading affect is done, now trying to add a reflection, like metal flickering in

the light of the sun:)

ill post it when its done.
[Touch Diamond2, Pure Themes and Apps] locoo:
remove post, my bad

this is a basic thing, tell me what u want change, trying to give it the refection but it doent come out nice enough yet

got to waste some time on that.

edit : its not playing my swf file -.-.

click to see the file anyway :)
[Upgrading, Modifying and Unlocking] crzyruski:
Model number: GM_DSTL1

Firmware version: 1.5

Baseband version: 20/05/09,st32,x2a.m1

Kernel version: 2.6.28-svn1368

Build number: CUPCAKE.eng.long.20090720.210535.r1368

Trying to figure out how this could be rooted because I can't seem to use traditional methods like downgrading and 1-click rooting.

If I understand correctly this is possible for me due to CVE-2009-2692

In an effort to try and cover my butt I have backed up all that "adb shell" permission would let me.

Zinx's "Recovery partition flasher for Android" has not been helpful.

Getting my device to use FastBoot seems to be my first step.

Constructive comments?
[Upgrading, Modifying and Unlocking] crzyruski:
still no luck

Ruled out the telnetd hack, bummer:

I run telnetd in terminal and it gives me no errors but a port scan doesn't return anything besides port 110(pop3), 25(smtp), and 21(ftp) - none of which have proved useful thus far. Must have been patched with cupcake... or something I'm missing.

Also ran cat /proc/cpuinfo for fun

--------------------------------

Processor : XScale-V3 based processor rev 2 (v5l)

BogoMIPS : 103.58

Features : swp half thumb fastmult edsp iwmmxt

CPU implementer : 0x69

CPU architecture: 5TE

CPU variant : 0x0

CPU part : 0x689

CPU revision : 2

Hardware : yuhua X2_V4 on Marvell (Littleton)

Revision : 0004

Serial : 0000000000000000

-----------------------------------------------------

103.58 is weak sauce... but apparently that is the minimum for the Marvell PXA310 RISC Microprocessor

I wonder if anyone else on this board is bumpin the DSTL1? I may be the lone fish out here
[Upgrading, Modifying and Unlocking] crzyruski:
Following this guide to get Fastboot aka Engineering Bootloader

I skipped flashing the radio because I figured it had to do with the OTA stuff which doesn't affect my model...

So I downloaded spl-signed.zip and renamed it to update.zip, placed it on my sdcard in the folder "update" (these instructions are specific to my model). In recovery mode I tried to update it but it FAIL.
[Upgrading, Modifying and Unlocking] crzyruski:
update.log from failed update

Starting recovery on Thu Oct 8 01:22:51 2009

framebuffer: fd 4 (240 x 400)

I:text_cols 24 text_rows 22

E:Can't open /cache/recovery/command

Command: "/sbin/recovery"

ro.secure=1

ro.allow.mock.location=0

ro.debuggable=0

persist.service.adb.enable=1

ro.build.id=CUPCAKE

ro.build.display.id=CUPCAKE.eng.long.20090710.190105.r1322

ro.build.version.incremental=eng.long.20090710.190105.r1322

ro.build.version.sdk=3

ro.build.version.release=1.5

ro.build.date=Fri Jul 10 19:15:42 CST 2009

ro.build.date.utc=1247224542

ro.build.type=user

ro.build.user=long

ro.build.host=long-desktop

ro.build.tags=ota-rel-keys,test-keys

ro.product.model=GM_DSTL1

ro.product.brand=generic

ro.product.name=gm_x2

ro.product.device=x2

ro.product.board=x2a_v4

ro.product.manufacturer=yh

ro.product.locale.language=en

ro.product.locale.region=US

ro.board.platform=

ro.build.product=x2

ro.build.description=gm_x2-user 1.5 CUPCAKE eng.long.20090710.190105.r1322 ota-rel-keys,test-keys

rild.libpath=/system/lib/libyh-ril.so

rild.libargs=-d /dev/ttyp1

persist.gsm.dual.mode.phone=1

persist.gsm.sim.active.phone=GSM1

sms.supports.national.lang=1

wifi.interface=eth0

ro.config.sm_notification_snd=notf_gm_02.ogg

ro.config.sm_notification_snd_2=notf_gm_02.ogg

ro.config.notification_sound=F1_New_SMS.ogg

ro.config.ringtone=GM_01.ogg

ro.config.ringtone_2=GM_01.ogg

ro.config.sync=yes

net.bt.name=Android

net.change=net.bt.name

dalvik.vm.stack-trace-file=/data/anr/traces.txt

ro.factorytest=0

ro.serialno=

ro.bootmode=unknown

ro.baseband=unknown

ro.carrier=unknown

ro.bootloader=unknown

ro.hardware=yuhua

ro.revision=4

init.svc.recovery=running

init.svc.adbd=running

init.svc.yuhua-board-init=stopped

ro.kernel.android.qemud=0

ro.radio.use-ppp=no

ro.com.google.locationfeatures=1

RecVer:Fri Jul 10 19:15:42 CST 2009

Recovery tools:

HOME: Sd-card update

CALL: Board test

BACK: Factory reset

POWER: Reboot system

I:Key 102 pressed, alt 0

Search /sdcard/update/*

I:Find file . in /sdcard/update/

I:Find file .. in /sdcard/update/

I:Find file update.log in /sdcard/update/

I:Find file update.zip in /sdcard/update/

Find update.zip, Home to update

I:Update package /sdcard/update/update.zip

Installing /sdcard/update/update.zip

Installation failed.
[Upgrading, Modifying and Unlocking] crzyruski:
Another Fastboot attempt

http://android-dls.com/wiki/index.php?title=Engineering_Bootloader

Downloaded update.xxx, renamed it to update.zip, placed it on my sdcard in the folder "update" (these instructions are specific to my model). In recovery mode I tried to update it but it FAIL... again.

From the log files it seems this stock recovery system SUCKS...
[Upgrading, Modifying and Unlocking] crzyruski:
Another FAIL

Revisiting http://xdaforums.com/showthread.php?t=532719 from my earlier post (#3). Tried to do the Radio Update... Downloaded ota-radio-2_22_19_26I.zip and renamed it to update.zip... yada yada yada, you know the rest.
[Upgrading, Modifying and Unlocking] wineleven:
Visit "http://www.generalmobile.com/index.asp?action=Android_Phones/DSTL1_support", and you can find how the update system work(it is not a G1:D). Also take some time to see the install package and hack it.

1. Unzip the package.

unzip Android_20090826_r1502.zip

2. Copy some missed property app(http://www.sendspace.com/file/dii80c get from adp1.5) to /system/app/ after diff it with the ADP image.

3. zip the new package.

zip Android_20090826_r1502_hack.zip -ry system boot.img

4. update package and wait it bootup.
[Upgrading, Modifying and Unlocking] crzyruski:
Very cool!

@wineleven

THANKS!

That was very cool! Finally some progress :)

So I was not too off from that path, I had already downloaded the update from General Mobile and had been inspecting the zip file they were trying to shove in my face as a quick fix to their buggy ROM. I was asking the support some very hard questions, which is probably why it has taken them more than their 48 hours to reply to me. (its been 5 days now)

General Mobile's update is Android_20090826_r1502.zip

containing the following particularly interesting (to me) files:

/system/build.prop

/system/system-update-post-script

/boot.img

/update-validate-script

Attempt 1

Here I tried to zip up their unmodified package with the suggested -ry arguments and hope that stock recovery takes it and runs with it.

FAIL

I reviewed wineleven's suggestions noticed he omitted the file update-validate-script

This was probably my problem

Attempt 2

Here I omitted update-validate-script

SUCCESS!

Attempt 3

Spirits high I go for the gusto:

I downloaded superuser.zip from this forum and embedded it in the location /system/app

Flash SUCCESS, functionality FAIL

I got too excited and put Superuser.apk and su both in the same directory... silly mistake

Attempt 4

This time I put Superuser.apk in /system/app and su in /system/bin

Flash SUCCESS, functionality FAIL

running su in terminal gave me "permission denied" with the following carriage return:

here1here2here3here4$

obviously I'm missing something here... but have made progress and feel more confident about this.

More attempts to come. Suggestions and advice is welcome!

Question to those knowledgeable

Why are certain files in the /system/bin included as "links" and not actual files? save space in zip?

Can boot.img be modified? Replaced with a better (more useful) one?

Any ideas on obtaining root?
[Upgrading, Modifying and Unlocking] crzyruski:
Root idea and shortcommings

After reviewing http://android-dls.com/wiki/index.php?title=Magic_Root_Access

I may have bin (lol) too hasty with slapping su in /system/bin

But logic tells me it shouldn't matter... bin or xbin

And I feel like permissions are my real issue because my current su (residing in /system/bin)

command

ls -l /system/bin/su

returns

-rwxr-xr-x root shell 34612 2008-08-01 08:00 su

command

chmod 6755 /system/bin/su

returns

Unable to chmod su: Read-only file system

^--- in hindsight I see that as a DUH, because I can't remount the /system partition as read/write

More questions

I have always understood chmod to use three digits, why are there four digits now?

Also, what is 's' in terms of permission... is that to see? like hidden files?
[Upgrading, Modifying and Unlocking] crzyruski:
Main task accomplished!

After reviewing Cyanogen's experimental ROM I can see where and how he sets permission for su

Trying to emulate his method for myself has been plenty of trial and error, but I have finally done it.

system-update-post-script was the key file that set permissions.

One MUST keep the carriage return at the end of the file - I have a neatfreak habit of cleaning them up.

Also, using the su and Superuser.apk in Cyanogen's latest build kept restarting my device, must be because his kernel is newer than mine.

RapidShare is hosting for 90 days Android_20090826_r1502_rooted.zip - NEW BUILD HERE

MD5: F1DE9A270CDDF01ADEE708B6660B7AFA

PM me if not avail.

NOTE:

I am not responsible for your new paper-weight mode...

This has worked fine on my device, but I guarantee nothing for yours...

My device is General Mobile's DSTL1 - details in post #1

What you get:

Root access via su and Superuser.apk - procured from XDA forums: http://xdaforums.com/attachment.php?attachmentid=211569&d=1249225060

To use:

Your sdcard must contain "update" folder, this is where you will place the zip file after you have renamed it to "update.zip"

Happy ROOT :)

------------------------------------------

My next task will be to get Cyanogen's ROM to work on my device... seeing as how Cyanogen codes for the popular HTC models, I am left out - and I don't like being left out. ;)

Side quests will be to play with the boot.img, flash the SPL, and maybe get a nice recovery :)

Particularly I would love to try out nandroid.

@wineleven THANK YOU for the nudge in the right direction!

Thank you:

Google for the open source Android OS - without the free SDK wouldn't have been possible for me

General Mobile for the nifty device

Remote Exploit for BackTrack3/4 - I did most of my work on this Live CD distro

XDA-Developers Forum for info and resources: superuser files and Cyanogen's ROM for info
[Upgrading, Modifying and Unlocking] wineleven:
congratulation to you.

Some notice:

As this devices is deeply modified based on Android open source and hardware different to G1. So you can not rebuild any system framework APK from open source unless you can get the DSTL1 source code. As i now, one thing we can do is to add some external APK file (API compatible to device, now SDK 1.5) to system. Like the Superuser.apk you do:).
[Upgrading, Modifying and Unlocking] jlcd:
Hi crzyruski

I'm a new android and DSTL1 user and this information is cool

it's easy to do for a newbie as I?
[Upgrading, Modifying and Unlocking] crzyruski:
What do you mean easy? What would you like to do?

I took General Mobile's only update: http://www.generalmobile.com/index.asp?action=Android_Phones/DSTL1_support and gave it ROOT. If this is all you want to do, I have compiled the package already for you in my post above. If you want to do it manually then read the whole thread to see how I did it.

If you want to use my compiled package, it is easy.

Then again, I don't know if anyone else has tried it. It worked for me.

You are only the second individual to inquire about it, I am not sure if the other fellow had any luck - he hasn't replied to me.

Hope this helps.

Keep in touch!
[Upgrading, Modifying and Unlocking] jlcd:
I only have 3 days with Android, but I think that I want to get root access. The only thing I have to do is a second "update" with your package, isn't it? :confused:

I'm going to look for a backup system program first... :)

Can I have problems to update from General Mobile support web in a future? (i.e Android 2.0)
[Upgrading, Modifying and Unlocking] crzyruski:
It does not need to be second. That is your choice. You can use it in any order. This is not a patch so order is no relevant.

My package is basically the original General Mobile update + 2 files.

These two files are su and Superuser.apk - nothing special (except that you will obtain root access on demand)

I currently only utilize root access to run Advanced Task Manager.

And in the future I want to overclock because I feel the DSTL1 is greatly underclocked though it should max out at ~600Mhz.

Good luck with a backup program as I have not found any free versions and NAndroid is ideal but not not yet possible as you have to flash the SPL and I am not aware how to do this for DSTL1 though I am sure it is possible.

Please let me know what you end up using to backup, if you do.

I would like to note that I am not all knowing and if something goes wrong I am sorry, but can't take responsibility.

There is no reason you should not be able to update from my package to another like: original 1.5 or new 1.6 or future 2.0 (whenever it comes out).

Hopefully when those come out I will be able to modify them similarly and make them available.

But you mentioned you will only have the device for 3 days, do you suppose 2.0 will be released within this time?

-crzyruski
[Upgrading, Modifying and Unlocking] jlcd:
I'm going to try with My Backup Pro

And about 2.0 this all I know...

http://www.boygeniusreport.com/2009/10/16/android-2-0-screenshot-walkthrough/
[Upgrading, Modifying and Unlocking] crzyruski:
Good luck to you.

I think I may begin working on some more DSTL1 hacks.

Please keep me updated with your progress :)
[Upgrading, Modifying and Unlocking] jlcd:
I only have to do ALL this process with your zip, isn't it?
[Upgrading, Modifying and Unlocking] crzyruski:
Looks correct to me. Tell me how it works out.
[Upgrading, Modifying and Unlocking] jlcd:
I've done it! and all seems to be ok... :):)

Thank you crzyruski.

I'll be waitng for your future DSTL1 hacks. :D
[Upgrading, Modifying and Unlocking] Ozichileno:
Hi Guys,

I am waiting for my N21 to arrive, can't wait to get it and try to root it to 1.6

I am glad I found this forum

William
[Upgrading, Modifying and Unlocking] edridev:
@crzyruski

Hello,

First of all, many thanks for your enthusiastic work for the DSLT1/N21 community.

I’ve upgraded my N21 to your rooted Donut and all went well except for the DUAL SIM support. With the original Cupcake from GM all works.

Is this the expected behavior, or is there something I can do?

:) Bye
[Upgrading, Modifying and Unlocking] killdashnin9:
Calendar issue

I am trying to do some research on the issue. I installed the 1.6 beta update for this phone and I found one annoying problem:

The phone does sync with my google account and I have multiple personal calendars but the phone only brings up 1. "default"

I went into the My Calendars setting to add a calendar and it does not find any others.

Has anyone else seen this issue?
[Upgrading, Modifying and Unlocking] crzyruski:
This is not expected. What steps did you take?

Have you attempted a Factory Reset yet?

You are the first to report a loss of DUAL SIM!

-crzyruski
[Upgrading, Modifying and Unlocking] nandika:
problem with my n21

hi!

my n21 just arrived today.

Was reading your guide, tried to do it to 1.6, without success:(

I copied the recovery.img, it was flashed, the file was deleted, so i think it went fine.

After that, the phone work, nothing happened, and after copying the zip to the SD I cannot boot to recovery mode using power & home buttons.. It shows up the sciphone logo, and then turns off screen, and not responding to anything (won't even power up without removing the battery again)

Did I do something wrong?

Thanks!

ps: only thing i was able to boot is a Safe mode thing.

And after running recovery img, nothing was updated (kernel version 2.6.28-svn1789-dirty, mon oct 12 11:11:22 cst 2009, baseband: 20/05/09,sr32,x2a.m1, firmware 1.5) cupcake 20090925
[Upgrading, Modifying and Unlocking] killdashnin9:
@nandika

I encountered the same issue, are you holding the Sim2 (home on our phones) call button when you press power? I made the same mistake. When you do it right you will see the linux penguin right away.
[Upgrading, Modifying and Unlocking] nandika:
yea, tnx that worked

now after doing the patch for market.zip it is done, but the phone cannot boot.

It keeps showing the android logo, and then rebooting always.

What could have happened?

Tnx
[Upgrading, Modifying and Unlocking] crzyruski:
I suggest you do a Factory Reset
[Upgrading, Modifying and Unlocking] Ozichileno:
@crzyruski

Thanks a lot mate, got my N21 today and followed your instructions and my phone now is so much better...

Keep it up great work.

I also had the same issue as nandika, but you just have to do a Factory reset and phone works great...

Now I am going to play with it.

PS.

Does anyone have trouble connecting to the PC, My Windows 7 64 bit machine does not detect it. I have tried installing the USB driver from the General Mobile but still does not work. If you had this problem can you please let me know how you fixed it.
[Upgrading, Modifying and Unlocking] kingnappa:
Hello! first of all I want to thank you for the great guide! excellent work!

I've updated my Sciphone N21 to Donut 1.6, I only have one problem, my wifi doesn't work! I've also noticed that the MAC address of mi wifi has changed (I use a router with a MAC address control access, that's why I've noticed that!)

Any suggestions?

Thanks!
[Upgrading, Modifying and Unlocking] cmoegele:
First of alle THX to all of the great developers for the fast generated rom-files, which makes our devices much more reliable!!!

There seem to be a known bug in the wifi part, because once the phone (my N21, too) went to standby wifi doesnot work anymore. I read this somewhere in a forum.

so the only way to run wifi at the moment is to enable display always on while connectetd to usb and reboot phone, or use long time before phone goes to standby and keep your phone (N21) active.

for x64 OS users, you have to install DSTL-USB-drivers manually via devicemanager and search driver manually, then there should appear, with debug mode enabled , an adbinterface, after installing non certfifed devices.

If you want to see the phones storage, just stay a while on the top line with the symbols and pull down a menu. There you can enable USB-storage.

best regards

cm
[Upgrading, Modifying and Unlocking] ryszon:
system file from new N21 obtained using the "Boot into recovery mode of BETA1.5_recovery-RA-DSTL1-v1.2.3.img" hope that is what you wanted :)

http://hotfile.com/dl/18975530/5c316ed/N21-system-mtd3.zip.html
[Upgrading, Modifying and Unlocking] ryszon:
quote wrong message, how to remove this post?
[Upgrading, Modifying and Unlocking] edridev:
Well, after i played arround installing some apps and rebooting the phone, the problem seems to be gone!!!:) Fully satisfied now. :D

Bye
[Upgrading, Modifying and Unlocking] asunde:
I am trying to do the upgrade to 1.6 step 4, see below, but nothing happens when I reboot the phone.

Is it enough to turn it off and back on again or should it be booted in a certain way?

Should the USB cable be connected to the PC or not while I boot it?

Arild

#4

New Recovery:

Donut image needs more space, so we must get a bigger NAND partition via the new Recovery

Also this new Recovery has more attractive features.

Copy recovery.img to "/sdcard/update/" and reboot you phone.

DSTL1 will auto flash the above location at bootup.

- A good indication of successful Recovery flash is that recovery.img will now be missing (it is deleted by the auto-flash). You may wish to make sure it was deleted before you attempt to boot into Recovery.

- Enter into Recovery mode, and check the "RecVer". If it has a Donut label, first big step has been completed. (pat yourself on the back )