yashsingh1/xdaforums huggingface dataset:
[Desire HD Themes and Apps] kalagas:
You didn't use few of my icons, you used almost ALL my icons... and you took over about 60 apps themed by Me in system/app...

And in the morning we talked I haven't realised exactly what you did...

I don't want to humiliate you, I wrote that I admire you for you MODs like the Browser MOD you did...

But now I am telling this for 1000time...

THERE ARE 2 SAME THEMES OUT THERE...

So if you don't delete your theme and try to make it from begging to show your viewpoint you will force me to delete Mine Theme...

And in you last theme obviously you didn't spend much time...

In previous themes yes I agree you have done good work, but not in your last one, as you used almost ALL my icons and not just FEW...

And I DIDN'T take a single icon from anybody that's for sure...

And if you think I'm crying what can I say???

I agree Android=Open Source but you tell me what's the point to exist 2 same THEMES out there for the users????

P.S Read few post above to see the opinion of another themer here and try to realise that it's nothing wrong with my attitude but with yours...

Sent from my DesireHD with Mixed_Theme
[Desire HD Themes and Apps] LordManhattan:
Liamstears, there's a difference between open source and being polite. It's fine if you're modifying Kalagas work, and use it for yourself, but repack it as your own and release it is just wrong.

Now, just say that you're sorry, and that's it. And next time, i hope you'll ask before you release other peoples work without permission. :)
[Desire HD Themes and Apps] leppie:
Liamstears, copyright still exists in open source. You can never claim the work as your own, unless explicitly given that right by the copyright holder.
[Desire HD Themes and Apps] kalagas:
My most important point here is that if one themer takes almost all icons from another themer, then the users will be confused and they will not be able to select a theme for their phone... That's why I insist that every one of the themers must have their unique identity...

And unfortunately the identity of a theme is made by how it's be looking, that means by the icons...

Sent from my DesireHD with Mixed_Theme
[Desire HD Themes and Apps] liamstears:
I agree with both of you and that is why he is mentioned in my thread and thanked for his icons but what I dont get it why he was ok with it and then decided to open this thread?

Also im sorry if hes p***** off I didnt mean to but I dont see why hes going to the extent of saying he will delete his theme theres no need for that. He does good work and should keep it up, people like his theme and mine for different reasons and people choose 1 or the other and people like the choice, you shouldnt take it down.
[Desire HD Themes and Apps] liamstears:
Mine is designed to use 1 of my 2 skins and when skins are used the themes look completely different
[Desire HD Themes and Apps] kalagas:
They were a lot users that liked your previous releases too...

Now all users that liked my theme, they find it also in your latest release...

I'm not extent it cause I am bad guy or anything else, I just say that there is no reason to exist 2 same THEMES in the same section...

That's all...

Sent from my DesireHD with Mixed_Theme
[Desire HD Themes and Apps] liamstears:
Yes I understand and agree BUT I think themes are different, I have had people say they prefer your theme to mine and people say they prefer mine to yours after my 3.6.0 release, both themes should exist
[Desire HD Themes and Apps] kalagas:
But how can be different themes if both use almost the same icons in all apps in system/app and almost the same icons in framework-res.apk and in com.HTC. resources.apk

There are no other icons inside the phone...

Sent from my DesireHD with Mixed_Theme
[Nexus S Q&A, Help & Troubleshooting] sarge363:
I had a Vibrant before and flashed it constantly. I soft bricked it several time and it was easy just to Odin back to stock and try again. Before I begin to flash Roms on this phone I would like to know how one would fix a bricked Nexus S. I searched "bricked Nexus S" and didn't come up with much.
[Nexus S Q&A, Help & Troubleshooting] Bronk93:
Flash a stock img thru fastboot/adb. Just as painless as Odin was if not easier.

Sent from my Nexus S
[Nexus S Q&A, Help & Troubleshooting] sarge363:
Yeah I figured that much but I have never used ADB before. What are the commands to flash a stock img and where can I get a stock img? I already have ADB set up, serial # comes up when I enter - adb devices. I'm ready to root and flash but I want to be prepared for anything. I don't want to panic for ten minutes like I did the first time I bricked my Vibrant.
[Nexus S Q&A, Help & Troubleshooting] Bronk93:
You should be able to snag a stock image from the development section. As far as what adb commands to use check out any of the root tutorials in development.

Sent from my Nexus S
[Nexus S Q&A, Help & Troubleshooting] leyvatron:
bricking the phone is not easy... everything can be wiped and reinstalled with ease. Recovery is your friend.
[Nexus S Q&A, Help & Troubleshooting] kenvan19:
That's why I love this phone. When I first rooted my wife's phone she was a nervous wreck about me ruining it. Now, she jokingly cheers when it boot loops or hangs on the google splash screen.
[Nexus S Q&A, Help & Troubleshooting] risegeek:
Coolest wife ever? haha :p
[Nexus S Q&A, Help & Troubleshooting] kenvan19:
hehe why'd'ya think I married her :D
[Nexus S Q&A, Help & Troubleshooting] Van_Dyke:
Hi Everyone.

I have my Nexus S for a 3 days - it's brand new. Last night i turned it off. It was about 50% charged. Today i can't turn it on. Phone is dead. What's wrong? There is no any response, even during charging (black screen).

Phone wasn't rooted. It has Android 2.3.2 update.

What can I do?
[Nexus S Q&A, Help & Troubleshooting] zephiK:
not enough information is present. you can attempt to get into bootloader / recovery, plug USB to the computer. When plugged, does the computer make a plugged in noise? if it does.. try turning it on, try using adb on it, etc.

as a last resort: if its not rooted or modified in any way, you can go back to best buy and exchange it since you said you've only had it for 3 days
[Nexus S Q&A, Help & Troubleshooting] distortedloop:
First thing to do is pull the battery, let it sit a minute or two, then put the battery back in and try to boot.

Also, try booting into recovery or fastboot. With power off, press and hold volume up button, then press/hold power on switch. You should enter fastboot mode. From fastboot menu, select boot to recovery. The phone will reboot and you'll get to a screen with an "!" and an android robot on it. At that point you press hold power, then press/hold volume up (make note that this is the reverse of what you did earlier).

Once in Recovery, try wiping cache from the menu.

Reboot.

If still no good, then repeat the process but pick factory reset/wipe from the menu in recovery. Note that this will wipe all personal data and apps off the phone but it won't touch your sdcard contents.
[Nexus S Q&A, Help & Troubleshooting] Van_Dyke:
The case with pull battery - not working.

I can't enter fastmode using 2 keys combination.

Computer don't recognize the phone. It's brick...
[Nexus S Q&A, Help & Troubleshooting] distortedloop:
Last option is to try to trick it into Samsung's Download Mode (see the Odin thread in Development section), but if the keys aren't recognized you can't soft boot into it so you'll need a dongle with a resistor to get there.

Sounds like it's truly a brick at this point. You'll probably have to return it, but I'm concerned about returning a phone that has your personal data on it without being able to wipe it. Doesn't seem like much way around that at this point if you can't get fastboot or download.
[Nexus S Q&A, Help & Troubleshooting] AllGamer:
get the 301k resistor JIG and then you can go into the download mode even without the 2 keys + usb plug

you can always make your own JIG if you have the materials at home or a nearby Radio shack
[Nexus S Q&A, Help & Troubleshooting] Van_Dyke:
Thx for all Your advices :)

Problem was with the dead battery. The battery died during the night - i don't know why. I think the system waren't able to boot up ant start charging process.

My solution:

I took 9V battery, 2 wires and charged dead battery for a while from 9V battery. Then a put it into phone and plug in to wall charger. Charging process started :)

Now everything is ok :D
[Nexus S Q&A, Help & Troubleshooting] jamiemac1977:
That's pretty scary that it wouldnt take a charge if run down completelty. But hey handy to know incase it happens to any of us,

If you get any repeat i would take it back to get a fresh battery of course (only right to do so).

here's hoping you never need to though ;)
[Nexus S Q&A, Help & Troubleshooting] sarge363:
That is scary......
[Nexus S Q&A, Help & Troubleshooting] warrenb:
Bricked

Tried unlocking nexus s last night, now it appears bricked. Cannot connect to computer to reflash as it seems to have wiped the driver. Any ideas on how to bring it back from the dead? thanks:(

I have managed to see the phone with fastboot. I was hoping that fastboot update, would re-image the brick. Can anyone let me know the correct syntax. I am not able to copy an image onto the phone. Thanks again
[Nexus S Q&A, Help & Troubleshooting] tamaratee:
Noob {MAC User}... Please be gentle

Greetings Everyone,

Okay, so I endeavoured to root my phone last night and was successful. I ran into trouble when the clockwork recovery and superuser permissions kept getting removed each time I reboot.

Now, I'm at the Google splash screen with no way to move forward. I'm a mac user and I don't really get the adb thing. Got adb to work with mac from a youtube video, but still not sure what commands to run.

What I've done so far:

- wiped cache

- wiped/factory data reset

- retraced my steps by using terminal to setup superuser permission from this post (http://xdaforums.com/showthread.php?t=927838)

What I think:

- maybe in all of my clicks I removed the ROM, so the phone doesn't have a ROM to work with.

This maybe a really infantile conclusion, but I know there's a solution (had a rooted G1 that I flashed all the time and thought I bricked once but was able to get it back to stock).

Eagerly waiting for a reply... no cell phone if this can't be fixed.

Tamara
[Nexus S Q&A, Help & Troubleshooting] distortedloop:
It would be easier to help you if we knew exactly what you did that caused the problem. You said you tried to unlock it...you mean fastboot oem unlock or something else?

If you can get into fastboot, you're not totally lost, but the computer needs to see the phone to do it.

I'm working in a vacuum here on what your real problem is, but without further details, the things you can try are boot into recovery (from the fastboot mode select boot recovery)...if you're stock recovery, press/hold power, then volume up once you see the android "!". From there wipe cache and whatever else it will let you wipe. Try rebooting. IF that didn't work go back to recovery and try a factory reset of the phone (will delete all your apps and stuff on the phone, but not on the sdcard (pics and stuff).

If none of that works, you can still try getting Clockwork recovery on the phone via fastboot. Boot phone to fastboot and then on computer type the command "fastboot flash recovery <put file name of recovery version you're flashing here>"

Once in clockwork, you should have access to adb via the computer. On your computer go to the Development section here and download any of the various nandroid images posted there. Now you use clockwork mounts and storage menu to mount the sdcard. Then use adb to "adb push <insert path and filename of your nandroid image here> /sdcard"

Unmount the sdcard with the clockwork mounts and storage menu. Now go to the backup menu, select advanced restore and find the nandroid image and restore it.

With any luck, you should be able to boot into a fresh phone.
[Nexus S Q&A, Help & Troubleshooting] AllGamer:
download the latest Android SDK

Mac OS X (intel)	android-sdk_r10-mac_x86.zip	28847132 bytes	e3aa5578a6553b69cc36659c9505be3f

then make sure to check the box to download all the Tools and USB drivers

once that is done, you should be able to get Fastboot in one of the directories, usually under tools

if fastboot doesn't work

you can always use Odin on a windows machine, to flash your phone back to stock
[Nexus S Q&A, Help & Troubleshooting] warrenb:
Thanks - I have managed to get clockwork recovery, but when I:

adb push update.zip /sdcard, I get failed to copy 'update.zip' to '/sdcard': Is a directory.

Am I trying to cpoy the wrong thing?

Thanks
[Nexus S Q&A, Help & Troubleshooting] Si_NZ:
What about

adb push update.zip /mnt/sdcard

Would that work for you?
[Nexus S Q&A, Help & Troubleshooting] warrenb:
Getting closer but this time:

Failed to copy ;update.zip' to '/mnt/sdcard/update.zip' : Read-only file system

How do I get it to write?

Thanks
[Nexus S Q&A, Help & Troubleshooting] peeturr:
You don't push the update.zip file. In clockwork, go to mount > USB storage. Just copy paste to your "sd card" as you would with any USB flash drive. You then install the update zip through the install update selection.
[Nexus S Q&A, Help & Troubleshooting] peeturr:
Forgot to mention. Copy to root of "SD card"
[Nexus S Q&A, Help & Troubleshooting] svoi:
My nexus s stock on google logo screen

I've tried to root my SNS, flashed Clockwork recovery thru ADB.

Than tried to load the phone and no success, I got stock on google screen.

Tried to wipe/factory reset and it says:

E: Failed to find "cache".......

E: Can't mount /cache/recovery/log

and few more E: Can't lines.

Than I tried to download nandroid back up. That's what it says when I try to do the restore through CWR.

Erasing Boot before restore

Error while formatting BOOT :!

E: Failed to find cache

and so on....

Than I tried to flash Miu ROm, that's what is says

E:Can't find misc

Finding update package...

Opening update package...

Installing update...

assert failed: write_raw_image("/tmp/boot.img"."boot")

E: Error in /sdcard/miudev-nexusS-1.3.25-deodexed_2.3.zip

(Status 7)

Installation Aborted.

Please provide me with any help.

Thank You
[Nexus S Q&A, Help & Troubleshooting] peeturr:
If you've managed to UNLOCK your bootloader already, do this.

Follow this thread to ODIN back to stock and have it repartitioned to avoid/eliminate any corruptions.

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

Since you've unlocked your bootloader, you can get into download mode by turning off phone, holding volume rocker up, plug into usb of computer.

After that, follow this guide step by step to root.

http://xdaforums.com/showthread.php?t=895545
[Nexus S Q&A, Help & Troubleshooting] suboxide:
Sounds like you have a 9023 nexus s (just like me) and you installed clockworkmod 3.0.0.5 and then tried to flash a rom onto it not looking at the errors present at the time (just like me when i first got my 9023), i did odin to fix it at the time but maybe you just could try to install the new clockwork mod 0.2.4 for 9023 devices ( http://xdaforums.com/showthread.php?t=988686 ) and then try to install a rom from within that clockwork mod (if it doesn't give errors)

ps. make sure you know what device you have 9020 or 9023 (the 9023 is the slcd version (europe mostly) while the 9020 is the samoled version (america mostly), since you can even make mistakes while installing the wrong version with odin, but if you have the 9023 version first thing i would try now is the 0.2.4 clockwork mod)
[Nexus S Q&A, Help & Troubleshooting] svoi:
I have 9020.

Just tried Odin with these drivers

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

SAMSUNG_USB_Driver_for_Mobile_Phones_v1.3.1600.0.e xe

It was looking like everything was going well.

Than it RESET with Odin

and Now it won't turn on.
[Nexus S Q&A, Help & Troubleshooting] svoi:
bump

I still need help, can't get it to power on
[Nexus S Q&A, Help & Troubleshooting] asuerio:
Please help-me

when I'm flashing on odin, he stands in system.img, it does not continue

p.s. sorry, I'm brazilian, don't speak english.

change "xx" for "tt"

hxxp://flickr.com/photos/asuerio/5716164499/

hxxp://flickr.com/photos/asuerio/5716163423/in/photostream/

hxxp://flickr.com/photos/asuerio/5716162899/in/photostream/

hxxp://flickr.com/photos/asuerio/5722383955/

error when trying to access the sdcard by recovery: is not possible to mount the sdcard

I try to do everything to access the sdcard, it has this error

:(:confused::(:confused::(:confused::(:confused:
[Desire Q&A, Help & Troubleshooting] Feltwo:
3 Days ago i flashed my desire with RCmixHD 2.0 a2SD ROM .Most of things works fine , except that one :

I can record 720p video , but when i turn it on it freezes every 3-4 seconds :(

Can you suggest me any HD Rom which support most of the things , or I just have to wait for better release ?

Thanks alot :)
[Desire Q&A, Help & Troubleshooting] Meaple:
As far as I'm aware for the HD roms, the 720p recording doesn't fully work. You can try them all but I've not actually tested them all. I am set to test them all today though so if you want, I can tell you which worked best for me. But generally, a rom is down to personal preferrence.
[Desire Q&A, Help & Troubleshooting] EddyOS:
Does work now going by the HD ROM threads...
[Galaxy 3 Themes and Apps] nastyba:
How can I make facebook SNS work in clear rom

or do you know some application which will sync my contacts & dates of born and pictures with my contacts .. thanks

I have JPA/JPB custom ROM without SNS apps.

- - - - - - - I have easyli solved this thing by coping ODEX and APK to system APP folder and installing SNS from system/app and not from SD card
[Galaxy 3 Themes and Apps] diamond_4g64:
I had the same problem and just went for jpf instead but if you find a way please tell us!
[Galaxy S I9000 Q&A, Help & Troubleshooting] frangiov:
To Forum Admins: this post was intended to be in the thread "[GUIDE] Unlock Froyo 2.2 I9000 Galaxy S manually", but as new user I am not allowed to post there, so here you have it.

I really liked the sgux.exe way to unlock the Samsung Galaxy S. This because I don't like the idea of messing up /efs files (deleting or hexediting).

Much neater workflow:

1. adb pull /efs/nv_data.bin
2. analyze nv_data.bin to find out NCK and FREEZE codes
3. restart your phone with a sim from a different operator
4. insert NCK and the phone unlocks itself

Notice that such an approach would completely bypass the .md5 'salt' problem, since somehow "it is the phone to unlock itself", thus generating a new and correct nv_data.bin.md5.

Sgux.exe was pulling codes that could be found in plain-text in nv_data.bin.

This was pretty easy if compared to the situation we face now:

- Froyo

scrambles

the codes

- Froyo

hides the codes somewhere

(I believe somewhere inside nv_data.bin or .nv2.bak)

I was locking and relocking (using the *7465625*638*# method) my Galaxy S #A (with known NCK and FREEZE codes), and comparing resulting nv_data.bin with vbindiff.

I also have a new Galaxy S (#B) shipped from Samsung with Froyo 2.2 (natively Froyo), from which I adb pulled nv_data.bin.

As a result of several hours comparing, I think I found something interesting at offsett 0x181540. Have a look:

Above you see nv_data.bin from phone #A, under nv_data.bin from phone #B, both running Froyo 2.2 and thus having the new version of nv_data.bin with NCK and FREEZE codes "encrypted". Red bytes are those which differ.

What about phone #A we know:

NCK code: 08036070
FREEZE code: 04837275
MCC lock: 21407

I noticed that locking and unlocking phone #A (with the known NCK code), those bits don't change. But in phone #B they are different. I guess it is because there is where the NCK and FREEZE codes are actually stored (in an encrypted form).

What about the encryption, have a look at the '6B' byte in the second red group standing for ASCII letter 'k' (common to #A and #B). It could stand for 'key', some kind of XOR key (for example) to scramble the first red sequence (not tested yet).

These are only my hipotesis anyway. There is much still to investigate.

Can anyone decode those bytes? and reverse engeneer the crypto algo?

#A: plain-text (NCK) [known] + algo(key) [un-known] = cipher-text [known]

#B: plain-text (NCK) [to find out] + algo(key) [reverse engeneered from #A] = cipher-text [known]

Maybe they use the same encryption algo used to scramble the imei code at offset 0x180000?

Another way to do it: does anyone knows, for example, where is located on the filesystem the routine (bash script or object file program) that triggers that pop-up window that allows you to relock the phone? (I refer to *7465625*638*#)

Looking foreward to hearing from you guys!
[Desire HD General] sjta3b:
I was just clearing out my SD card when I noticed in a folder called "download" on the root of the card there was a lot of apk files called "downloadfile-1.apk" with different numbers in place of the 1. Does anyone know where these come from and if I'm ok to delete them? Thanks.
[Desire HD General] Jason1978:
These are Android packages for the apps you have downloaded probably through some application.

These are safe to delete as your actual apps installed will live elsewhere. It is safe to say if your not noticing anything not installed and you don't know what they are, these can be deleted. If you need them again and you have paid for them, the market should have these information stored with your google account and can be downloaded again if needed.

If you really want to, you can transfer them to your home pc for backup. You can find out what they are using the android software development kit if you so wish, using a program called aapt.
[Desire HD General] sjta3b:
Thanks for the advice. Very helpful.
[Windows Mobile Apps and Games] khakhi:
Guyz,

I can access facebook and skype on my XPERIA X1 phone, but i have never been able to access twitter on my X1 using the twitter panel, pocketwit, twikini or even going through google.

As soon as i enter my log in details and press "sign in" within two seconds it gives me error message saying it cannot log me in.

I log into twitter on my laptop daily, why cant i access it on my phone?

oh...when i go into google and search for twitter, the twitter log in page shows but then becomes so pixelated that you cnt c anything.

Pls advice, i have read other similar threads on this but cannot find solution.
[HD Mini Themes and Apps] fra18061988:
Hello! Why MorphGear 2.4.0.9 does not work in full screen mode? If I press the center of the screen when the game is running does not change in full screen mode. In the settings I have unchecked "disable full screen". Also do not see the MiniPad! Is sure that MorphGear works on Htc Mini? Help me!!! :(
[HD Mini Themes and Apps] redeye998:
Do u have instal it correctly?

I mean, keeping both .exes, copy the HVGA minipad files in /games/morphgear?

Find the original version and instal it (google) and install.

Go to instal position

default: program files/games/morphgear/skins

and rename the morphgear.exe to something else (for registering it later)

Find the hd2 port (xda forums) and install

Find the HVGA minipad (xda forums) and unzip to program files/games/morphgear/skins

Open morphgear, go options, double tap the options to close so you can see the Minipad

Use HD mini keyboard to navigate, (arrows) and select with Enter.

Open the rom you want and tap the screen for fullscreen!

If i have time i will update this post, cause i am in hurry now :P
[HD Mini Themes and Apps] fra18061988:
Thank you!!! I solved it! Now it works!

There's only one problem. When I open the program, the screen looks like this (screen01). Can I make it look like this (screen02)?
[HD Mini Themes and Apps] redeye998:
the screen you should use is the 1st. there is no way or reason to take it to screen2. screen 2 is only for pressing the "i" for registering some products on the program

hope i helped tho!
[Galaxy S I9000 Q&A, Help & Troubleshooting] azzledazzle:
is it possible to put all my apps in to a zip file and flash through recovery after installing a new rom ?? to save the hassle of manual installation. ?? :confused: