yashsingh1/xdaforums huggingface dataset:
[Samsung Mesmerize] cloudstrife7:
Out of curiosity - What do you use the space for?
[Samsung Mesmerize] 02busa:
I use my phone as an mp3 player too. So I have alot of music on it, back ups, and roms take up a lot of space also. No such thing as too much space.
[Samsung Mesmerize] hyelton:
I never use that much space
[Samsung Mesmerize] WankAttack:
I use an application called audio galaxy. Now I never have to go through the hassle of transfering music to my phone/mp3 player. Leave my desktop on like always and stream, stream, and stream. Now I have lots of room for other stuff :D
[Samsung Mesmerize] elijahblake:
damn you for making this go back to the front... lol
[Samsung Mesmerize] sageDieu:
HI ELI
[Samsung Mesmerize] 02busa:
I never leave mine on... I already have too many power hungry devices in my house. Lol
[Samsung Mesmerize] Omnibot:
Streaming is ok but I also slapped a 32GB card in to carry a good selection of music with me at all times. Android Winamp + last.fm = yum
[Samsung Mesmerize] elijahblake:
:mad::mad::mad::mad::mad::mad::mad::mad::mad::mad::mad:
[Samsung Mesmerize] sageDieu:
:D so... uh... on topic... I used an SD card once.
[Samsung Mesmerize] KyleIsTheBeast:
LOL I am going to stick with my 16 GB considering I didn't even cap the 2 GB that came with my hero
[Samsung Mesmerize] monthlymixcd:
Speaking of HTC (in the Mesmerize forum, I know)... my friend missed out on the free Mesmerize deal that I got so he ended up with an HTC Desire. That model hadn't been on the market THAT much longer than the Mesmerize, but it only came with a 2GB card. Granted, I had a 2GB card in my Motorola Rokr and it held a surprising amount of music... but it wasn't a smart phone and a 2GB card seems pretty skimpy... especially since the onboard RAM in the Desire in much less than the Mez in the first place.
[Samsung Mesmerize] phidelt82:
I think we should sticky this thread.
[Samsung Mesmerize] sageDieu:
We need an off topic lulz thread to let off steam... 4chan with morals.
[Samsung Mesmerize] lmartin92:
that's an awesome price
[Samsung Mesmerize] jpaulwaite:
this is my cheap thread reply to hit ten posts. thanks all.
[Samsung Mesmerize] godofwar762:
thts cheap
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] nysokheng:
Dear all,

Since i am a newbie, i want to ask you before taking the risk.

Can i flash radio 2.06.51.07 to 2.15.50.14 ?

I ask this because i saw some people wrote that "never flash .51 Radio".

I want 2.15.50.14 Radio so that i can flash wp7 ROM or android.

Thank YOU in advance!
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] A new hacker:
Absolutely.
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] kurt-willems:
Like mentioned before yes you can.

It's only the users who have a USA T-Mous device who can't/may not install a .51 Radio because this will brake his/there device.
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] nysokheng:
ok thank you guys,, i'll try it.... i just want to make sure coz i don't want to brick my phone... thank YOU
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] seanyuan62:
Yes, in fact, I had the same radio as you and when I flashed wp7, I got robot voices in calls and constant screen of deaths. I flashed to 2.15.50.14 and there has not been any problems since.
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] 96edwy:
i read somewhere that it you could only flash xxxx.50 roms, your saying that you can flash xxx.50 roms to TMO aswell?

if its not clear, im sure it is but just incase, i meant 4 digits before the 50 and 3 digits before 50
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] thecutem:
hi

i had 2 activation code for wp7 and i try to active my phone but it doesn't.

i did all this

http://xdaforums.com/showthread.php?t=912218

but it doesn't work.

please your help to active my phone.
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] thecutem:
no answer.

please i need your help.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Vylle:
hey guys, im not new to android but im new to HD2(TMo).. i have resently put android on ma phone and decided to flash clockwork onto my phone.. i did as the videos said and flashed it onto the phone with DAF but when the phone restarts it says "Nand kernel open failed" in red - i've seen alot of people have this problem but no1 has suggested a solution that works

can anyone help me out? would like to solve this problem
[HD2 Android Q&A, Help & Troubleshooting and Genera] CGCR:
I unable to gain permission from Superuser to be able to use SetCPU. I am using "[DFT]LEO "Stock Desire" NAND Android ROM", I downloaded SetCPU but nothing happened, so I figured its something with my root so I used the "One Click Root". I rooted it, rebooted it, tried to use SU, nothing happened, then I unrooted followed by a re-root and another reboot, once again opened SU but nothing happens. I still cannot use SetCPU and SU just has a blank black screen, I cannot seem to find a solution.

Any help is greatly appreciated, thank you.
[HD2 Android Q&A, Help & Troubleshooting and Genera] CGCR:
Please help!
[HD2 Android Q&A, Help & Troubleshooting and Genera] LiFE1688:
You need a rooted phone before you can use superuser.

Download z4root.
[G2 and Desire Z Q&A, Help & Troubleshooting] jontornblom:
Three questions about libraries.

1. Are the libraries loaded on boot, or are they accessed on demand when a program needs them?

2. Are the libraries different depending on the hardware? Kernel?

3. Can two libraries co-exist that have overlapping functions so that the user has access to the non-overlapping functions, or will this break the phone?

Thanks for your help! Just starting to learn the dev ropes...sorry if the questions sound ignorant!
[Vibrant Android Development] untermensch:
this script is based on the work to Danesham90 and others see link

http://xdaforums.com/showthread.php?t=598026

===============================================================================

Tested on the Samsung Vibrant, Script may need modification for other phones

===============================================================================

===============================================================================

Directions:

===============================================================================

the easy way:

1. turn on USB debugging

2. plug phone in to computer

3. run the script and follow the screen pormpts

the script will download everything needed to make a

signed deodexed clockwork flashable update.zip while also

adding root and the modified 3e recovery in the proccess.

===============================================================================

the hard way:

http://xdaforums.com/showpost.php?p=10986893&postcount=28

================================================== =============================

/* This program is free software. It comes without any warranty, to
* the extent permitted by applicable law. You can redistribute it
* and/or modify it under the terms of the Do What The **** You Want
* To Public License, Version 2, as published by Sam Hocevar. See
* http://sam.zoy.org/wtfpl/COPYING for more details. */

UPDATED 02/03/2010

bug fix to signupdate.jar

clockwork script tweeks

UPDATED 02/02/2011

added upload to ROM to SDCard

added reboot recovery

added test sign all apk's in ROM - see README for details

added pull "/data/app/" and install "/data/app"

UPDATED 02/01/2011

added adb on by default toggle

added data wipe toggle

updated smali/baksmali to 1.2.6

UPDATED 01/31/2011

updated adb

fix similar filename deletion when using delete.txt

added barebones_delete.txt deletes everything that

does not cause phone to crash

UPDATED 01/29/2011

add "symlink dumpstate SYSTEM:bin/dumpmesg" to update-script.

add "symlink debuggerd SYSTEM:bin/csview" to update-script.

completed secondary method to make ROM from extracted Odin files.

see this post for instructions

http://xdaforums.com/showpost.php?p=10986893&postcount=28

UPDATED 01/28/2011

added auto delete apk's (bloat removal), edit bin/example_delete.txt and rename to delete.txt

added auto add apk's (pre-install or update apk's) add apk's to bin/apks directory

UPDATED 01/23/2011

fix path error when space in user name

UPDATED 01/22/2011

updated TempRoot.exe to not trigger anti-virus

updated Superuser.apk
[Vibrant Android Development] Whitehawkx:
This is fantastic! Thank you for always making things a little less troublesome. ;)
[Vibrant Android Development] untermensch:
Oooops, last minute change broke something, fixed and re-uploaded.
[Vibrant Android Development] Whitehawkx:
Thanks for the heads up. I was just testing this on KA5 for funsies. It looked like it went ok but there was a prob with temp root at the beginning and it looked like a few java errors at the end. I'll re-download and give it another go.

Edit: Ah, looks like it's working now. Temp root worked and it downloaded the modem and kernel.

Edit2: So it looked as though everything worked fine, but when I went to install it I got

E:Can't symlink /system/bin/cat

E:Failure at line15:

symlink toolbox SYSTEM:bin/cat

Installation aborted.
[Vibrant Android Development] untermensch:
I just tested on my laptop and got a java out of memory error

while signing the rom so I increased the heap size which seems

to have fixed it.
[Vibrant Android Development] Whitehawkx:
Yea I got the same thing as well. Thanks again, will give it another go.

Update: The process was more in-depth when deodexing. Signing went through np and when I flashed through clockwork it worked (goodbye splash screen!). There must be some issue with KA5 though. It got through to the Galaxy S screen and then started vibrating and then blackscreen. T_T
[Vibrant Android Development] Master™:
Thank god for this.. :D (Deodexer)

Thanks untermensch, your the best :)
[Vibrant Android Development] guruchimi:
Really really appreciate this. Thanks a bunch!
[Vibrant Android Development] Whitehawkx:
Most useful tool EVAR!

I T W O R K E D~! :D

My final attempt last night did not shoot out the "signed_ROM.zip" at the end. I ran it again this morning on KA5 and when it finished I had the signed_ROM.zip in the folder. Put that on my internal, flashed through clockwork and viola! Doedexed KA5 with root and modded 3e recovery. I can't thank you enough Untermensch for putting this together for everyone.

"Give a man fish feed him for a day. Provide him with tools to fish and feed him for a lifetime." (Yea I tweaked it but you get the idea!) :D
[Vibrant Android Development] Whitehawkx:
I noticed one thing. During the deodexing process I got [null] on one file in the core.odex. After it had all finished up I looked in the framework folder and core.odex was still there. So am I correct in assuming that it did not doedex properly? Other than that everything else looks golden.
[Vibrant Android Development] justlovejoy:
Oh this is sick. i was looking for this all day the otherday when i was trying to deodex ka5! you rock and rule. i cant wait to explore the possiblities!
[Vibrant Android Development] Whitehawkx:
I deleted the core.odex file and rebooted just to see what would happen and it soft bricked and is stuck at the Vibrant screen. So it seems the only issue lies in deodexing the core.jar at this point.
[Vibrant Android Development] justlovejoy:
can i use this to port a rom? forgive me if that is a noob question. just wanted to know if i had the right idea...
[Vibrant Android Development] untermensch:
yep that was an baksmali error, likely you could run the script again and it

would baksmali OK.

this script is a real system stress test, any way I increased the java maxmem

setting for framework files to 1024m added error logging and the script will

now stop if there is an error. hopefully to prevent a broken ROM from being

released.
[Vibrant Android Development] untermensch:
can you reproduce this error? I have seen it once but cant reproduce it
[Vibrant Android Development] Whitehawkx:
Pretty sure the core.odex [null] error I got happened every time I ran the program. I ran it once after the 1:25am update and it happened. That is also the time it did not produce the signed_ROM.zip. I ran it again this morning after I saw the OP had been updated and it did produce the signed_ROM.zip but I still got the [null] error on core.odex. I'm going to Odin KA5 and do it again right now. I will let you know how it works out.

On a side note. I flashed the one I recieved this morning with everything being deodexed except the core.jar and it ran great until I deleted the odex file. Anywho, will test now. Also, not sure if this matters but I am running 32-bit Windows 7.

Update1: Initial news is good. Core.jar was deodexed properly with no errors. :) Will let you know how the entire process fairs once its completed.
[Vibrant Android Development] Whitehawkx:
Worked perfectly. I got no errors and everything deodexed properly. Flashed it on my phone and it's running just fine. You are awesome. :)
[Vibrant Android Development] untermensch:
Thanks for retesting, glad it worked, there are thousands of files being generated

an lots of java processes being spawned so there are bound to be an occasional

error. I have added an automatic retry when there is an error to the next version

should be posted some time tomorrow.
[Vibrant Android Development] jellette:
I'm about 3/4 the way through testing this out - it seems to be working just fine with the exception that every command is appended with "ATTRIB" is not recognized as...

Hopefully it will work anyway.

One thing I noticed that might speed the script up in the beginning would be a root check, I have already rooted this rom but it still needed to run rageagainstthecage.
[Vibrant Android Development] jdanisevich:
I've been looking for something like this forever now, thanks so much! Can't wait to play with it.
[Vibrant Android Development] guruchimi:
These scripts along with other topics helped me to understand the 'rageinthecage' rooting process. I usually root my phone only to remove bloat and to install necessary utilities like MobileAP. This post helped me immensely to obtain temporary root access to accomplish these tasks. Can't thank you enough!
[Vibrant Android Development] untermensch:
I just posted a new version that adds support for rooted phones, if su not found

or permission denied the script then falls back to rageagainsthecage

the only thing attrib does is hide the output directory for the decompiled smali

files that command is standard on ms operating systems since DOS so it's

weird that your getting an error, the new version removed the attrib command

it was just cosmetic anyway.
[Vibrant Android Development] jellette:
By the way, I can report that it successfully deodexed yesterdays JSY 2.2.1 Norwegian I9000 leak.

AND, I am so glad that it checks it's own folders first since my son closed my laptop, I just started over and it checked on what was in the folders and picked up at the next odex.

Great work as always!
[Vibrant Android Development] ndwgs:
So is this your next project?

Sent from my SGH-T959
[Vibrant Android Development] jmcghee1973:
Can this be used to place Supercurio's Voodoo kernels on a ROM also while deodexing? Add say KA6 kernel w/voodoo.zip to the bin file before deodex?

Or can someone direct me along the lines of deodexing KA6 Official with all the bloat and the KA6 voodoo kernel already on it and make it CWM flashable because I hate having to disable voodoo to flash a deodex'd version just to re-enable again.
[Vibrant Android Development] Whitehawkx:
You can place the modem and/or kernel in the same folder as the "deoall" and I believe it will add those to your .zip as opposed to downloading whatever you are using on your current rom.
[Vibrant Android Development] untermensch:
UPDATED 01/28/2011

added auto delete apk's (bloat removal), edit bin/example_delete.txt and rename to delete.txt

added auto add apk's (pre-install or update apk's) add apk's to bin/apks directory
[Vibrant Android Development] untermensch:
UPDATED 01/29/2011

Instruction's for making ROM with out flashing to device

first you need a linux box to mount the files

EDIT:

it has been reported that MagicISO will extract the files from the

.rfs file system images.

extract the Odin tar to your linux desktop

make a tmp directory for the mount point

open console

CD Desktop

mount cache.rfs

sudo mount -o loop cache.rfs tmp

copy /recovery/sec_csc.zip to desktop

unmount cahce.rfs

sudo umount tmp

make a directory for the system files

mount factoryfs.rfs

sudo mount -o loop factoryfs.rfs tmp

copy the system files to the directory for the system files

unmount factoryfs.rfs

sudo umount tmp

now move the system files, sec_csc.zip, modem.bin, zImage to the windows machine.

place the system files in ROM/system

place sec_csc.zip, modem.bin, zImage in the same directory as deoall.bat

then run the script.
[Vibrant Android Development] IamSonoma:
Works good for my Captivate. As for the factoryfs.rfs I have been using MagicISO. Thank you.
[Vibrant Android Development] hard5ter:
This works great...many thanks...

2 things..

Can you add support for a no wipe option..

And is it impossible to add the clockwork recovery to jpy kernels? Dont like voodoo or hardcore..prefer stock. But with recovery and root...

Many thanks
[Vibrant Android Development] krylon360:
You can also use MagicISO to extract the Factoryfs.rfs

This makes it eaiser for though who do not have a linux partition set up.
[Vibrant Android Development] untermensch:
UPDATED 02/01/2010

added adb debugging on by default toggle

added data wipe toggle

updated smali/baksmai to 1.2.6
[Vibrant Android Development] iammodo:
Worked like a glove on my i9000

Sent from my GTI-9000 Using that XDA app thingy
[Vibrant Android Development] IamSonoma:
It works great for me as long as I do not add a theme or ext power menu. I can run the image fine but if I pull a themed version from my phone it loops on first boot. Could be just me though.

Anyone else?
[Vibrant Android Development] Whitehawkx:
If it is themed wouldn't that imply that it has already been deodexed?
[Vibrant Android Development] hard5ter:
many thanks for the quick add!
[Vibrant Android Development] untermensch:
Thanks I found my old copy of MagicISO and can confirm that it works.
[Vibrant Android Development] IamSonoma:
May I suggest a new menu item?

If not no biggie... :)

ECHO 99......Push signedROM to SDCARD

IF %menunr%==99 (GOTO pushtosdcard)

::
:pushtosdcard
CLS
ECHO Push signedROM to SDCard
ECHO.
::
CLS
echo What should signed_ROM.zip be renamed to before pushing to sdcard
CD "%~dp0"
set /P NewName=Enter name : %=%
ECHO Pushing signedROM to SDCard
adb push "%~dp0signed_ROM.zip" /sdcard/%NewName%
ECHO Pushing signedROM to SDCard
ECHO.
PAUSE
GOTO rebootrecovery
::
:rebootrecovery
ECHO.
ECHO 1......Reboot in Recovery
ECHO.
ECHO 2......Quit
ECHO.
SET /P recovery=What do you want to do?
ECHO.
IF %recovery%==1 (GOTO :rebootrecovery)
::IF %recovery%==2 (GOTO :------) <-- any suggestions?
::
:rebootrecovery
ECHO Starting adb server
%adb% start-server >nul
%adb% -d reboot recovery >nul
::
[Vibrant Android Development] untermensch:
thats a great idea, I will add it to the next update.
[Vibrant Android Development] IamSonoma:
sweet. I modify the menu every release.

Could you determine the best action for #2?

Another one modification I am working out is the edify menu and pull the data/apps folder. I have experimented with a secondary apk folder to handle this. It would work better.

Still learning the basics though. At least I am am up am running. :)
[Vibrant Android Development] IamSonoma:
I figured it out. :) Bad themes? Not sure. Loaded new them and walla.
[Vibrant Android Development] IamSonoma:
2.5.4 _ You are quick. :)

My \data\apps idea is working well. It is simple code.
[Vibrant Android Development] untermensch:
what I did was add return to main menu after the upload is finished, and then

you can select reboot recovery.

you could download /data/app to /ROM/data/app the clockwork script might need

to be modified to mount DATA (I will have to test this though) then the apps

will be installed to /data/app by clockwork.
[Vibrant Android Development] IamSonoma:
1. Nice. Working well.

2. That was my original plan but the the local was a quicky, I'd rather pull from the phone.
[Vibrant Android Development] untermensch:
I just uploaded a new version that will pull /data/app and then install to /data/app.
[Vibrant Android Development] IamSonoma:
Pulling apps is working fine.

Signing apks is working too.

Might need to work out a but with the reboot recovery. I did not account for device not being connected.

Also, not sure if this is by design. When pushing signedROM to sd card if you forget to name it it names it signedROM. I missed this test earlier. Seems you picked it up.
[Vibrant Android Development] IamSonoma:
Minor Bug...

E:Failure at line 92:

set_perm 1000 1000 0771 DATA:app

My data/app/ folder was empty. If I add apps it seems to be ok.

There is nothing to give permissions to.

Could we add a placeholder if no apps are pulled? Maybe an alternate script?

Thank you again.
[Vibrant Android Development] untermensch:
yep, should have thought of that, I'll have it fixed in a moment.

EDIT:

it's also part of the addroot sub on line 230

IF NOT EXIST "%~dp0ROM\data\app" MD "%~dp0ROM\data\app"

I'm going to add it again just before the zip operation just to be safe.
[Vibrant Android Development] MikeyMike01:
FYI, MagicISO is free and can open the .rfs files in Windows.
[Vibrant Android Development] IamSonoma:
Might need a 0k file in there at the least.

_placeholder
[Vibrant Android Development] untermensch:
I moved QuickBoot.apk to /data/app so there is a file in the directory.

if you are trying this on a phone other than a Vibrant then your data partition

might not be getting mounted see if /bin/mountdata is correct for your phone.
[Vibrant Android Development] IamSonoma:
Captivates/I9000 = JS3

#!/system/bin/sh

mount /data/app
[Vibrant Android Development] untermensch:
hey can you see if this will work

#!/system/bin/sh

mount -a

that should mount everything in /etc/fstab

EDIT:

I went ahead and added "mount -a" to the clockwork script, as long as clockwork recovery

has the right values in /etc/fstab that should make the script work on any phone.

new version uploaded
[Vibrant Android Development] IamSonoma:
I was not having any luck pulling my /data/app/ so I made a change to line 359 in deoall.bat.

Changed

%adb% -d shell sh -c "mount -o rw,remount /dev/block/stl9 /system && chmod 444 /system/etc/dbus.conf && chmod 444 /system/etc/bluetooth/*" >>%errorlog%

to

%adb% -d shell sh -c "mount -o rw,remount /dev/block/stl9 /system && chmod 444 /system/etc/dbus.conf && chmod 444 /system/etc/bluetooth/* [COLOR="red"]&& chmod 444 /data/" [/COLOR]>>%errorlog%

Giving read access to /data/.

This would allow us to later copy over any customizations like "/data/gps/secgps.conf".

This is nearly perfect. Just need a way to keep my custom settings like

Sound - unclick Audible touch tones and Audible selection

Display - Maintain lock screen setting setting and full animations

Local and text - Set Local - English (US)

Local and text - Select Input - Gingerbread Keyboard

Date and time - Unclick Use 24-Hour format

Date and time - Select date format

I have searched for these and onkly finds ways to set it manually. If there is a certain phrase to search for that would be good too.
[Vibrant Android Development] untermensch:
I added "chmod 775 /data/app" to the su command because setting to 444

would remove write and execute permissions for the whole system which

would break almost everything.

system settings are kept in a database file in /dbdata/databases/com.android.providers.settings/settings.db

you could pull it from the phone and include it in the ROM update-script would

also have to be modified with

copy_dir PACKAGE:dbdata DATADATA:

this might not be the same on all phones, and you would have to make sure to

set permissions.

the other way would be to write a script that Clockwork recovery would run at

install time to create the database and insert the values you want.