yashsingh1/xdaforums huggingface dataset:
[myTouch 3G Slide Q&A, Help & Troubleshooting] Code3VW:
This is probably going to get confusing, but I'll try to keep everything clear...

I installed Chiefz 2.1 Build onto my Slide. I used it for a week, customized it, and then CM6 final was released on 8/28. I backed up my phone with nandroid, and then wiped the cache and data and flashed CM6.

I used CM6 for a week. I realized after a couple of days that I was not receiving google talk messages on my phone. If I logged into GMAIL and looked at CHATS, I would see all of the messages people were sending, and I just wasn't receiving them. I cleared GMAIL, and Google Talk cache on the phone, but this still didn't fix it.

I figured I'd post and see what people thought, but I just bought a new car which has bluetooth built in for calls and A2DP to stream music from my phone. I tried doing this on CM6 and it didn't work. I looked it up, and it is because bluetooth isn't supported in CM6. So, I backed up CM6 using nandroid, and then restored the backup I had done of Chiefz 2.1 build. Bluetooth works perfectly, but I still can't receive Google Talk messages. I cleared Talk, Gmail, and Gmail storage on the phone, but they still aren't being delivered. Also, peep is not updating...it keeps saying that my phone is refreshed, and if I refresh tweets it will say updated, but the last tweet I see is the last one I saw before I backed up using nandroid the first time...coincidentally it is Cyanogen saying that CM6 is done baking in the oven. :D

I cleared the cache for Peep, and it still wouldn't update. So, I booted back into nandroid this morning after 2 days of not receiving Google Talk or Twitter, wiped data and cache, and restored the backup again. Same issue still exists.

Why did this happen? I used nandroid backup so I wouldn't have to wipe, load fresh roms, and then customize all over again...
[myTouch 3G Slide Q&A, Help & Troubleshooting] HebrewToYou:
First, Peep isn't working for anybody. T-Mobile is working on it.

Second, your nandroid backup appears to be working just fine.
[myTouch 3G Slide Q&A, Help & Troubleshooting] Code3VW:
Oh. :D

What about google talk? Is this broken for everyone too?
[myTouch 3G Slide Q&A, Help & Troubleshooting] stoneyjonez:
how is this a nandroid issue and why is this in the wrong section?
[myTouch 3G Slide Q&A, Help & Troubleshooting] Code3VW:
You are not a moderator, so stop acting like one. :rolleyes:

Google talk and tweet worked before the nandroid backup and restore, and both broke afterwards. Tweet appears to be a T-Mobile issue, and I'm trying to verify, at this point, that Google talk is as well. Otherwise, it is still a nandroid issue since that is the only change to my phone. Backup with nandroid, flashed a different rom, wipe, and restored with nandroid.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] smithisize:
So, I'm trying to develop my own XML file for XDA_UC, but I don't have a really efficient way of doing this. Could someone tell me how they do it?

My primary goal is to move shortcuts. Can I accomplish that task by this:

<characteristic type="%CE2%\Start Menu\Programs\Tools" translation="install">
<characteristic type="MakeDir" />
<characteristic type="CHTEditor.lnk" translation="install">
<characteristic type="Move">
<parm name="Source" value="%CE2%\Start Menu\Programs\CHTEditor.lnk" translation="install"/>
</characteristic>
</characteristic>

Thanks

Smith
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] Lennyz1988:
I don't know if this answer is of any help, but in the valkyre roms we use silent_uc. This works with any rom with mortscript cooked in.

http://xdaforums.com/showpost.php?p=4699952&postcount=5

You just copy the files from the start menu to your sd card in the map silent_uc/root/windows/start menu en it will install. I think that it's much easier then making a .xml :) Just a suggestion.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] smithisize:
Great advice, I guess I didn't know silentUC could do that. Too bad Valkyrie is the only ROM (that I've ever really seen, I guess) that uses it. If simplicity or energy used it, that would be awesome.

I haven't played with Valkyrie much, but when I did it was beta Cookie-FX 23xxx and it was very, very slow (that was like a week ago). Was that just a fluke? Is it normally a good ROM?

Regards

Smith
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] XirXes:
In Energy roms its in XDA_UC\Start Menu\.
[Touch Pro2, Tilt 2 Windows Mobile ROM Development] smithisize:
Will that move shortcuts though? Say, from the root of the start menu to start menu\tools?

Thanks

Smith
[General Questions and Answers] Bigdrago:
Hello. My last Desire got destroyed. And now I have a new Desire. I inserted my sd memory card into the new phone, but I don't get the question if I want to restore backup.

Have I lost everything or can I extract contacts, messages etc from the sdcard manually?
[Vibrant General] wbexpress:
After flashing Eugene's V9 I tried to get rid of that damn TW calendar by putting it in a temp file I created on the SD card, then put the 2 stock APK's onto the card. However, it would not install them with Root Explorer. So, I then moved them to temp, then I put the TW APK's back into system/app, that did not work (application not installed), and then on the card, but it will not install those from either place. I did click on "mounted as r/w" in Root Explorer, so that's not the problem. Can someone please give a step-by-step on what to do to fix this? I need some type of calendar, so if it's the TW one, it is what it is. I Googled and did not find anything exactly on point. I hope the answer is not "re-flash"!!!Thanks...
[Vibrant General] s15274n:
A guide/instructions on how to do this are in the sticky (where the title of the thread says to read before asking), as well as the files you need.... you drop them in system/app (you do not click on them and install them).
[Vibrant General] wbexpress:
Thank you, and, my apologies. I had read the whole thing several times, but when I screwed up I didn't figure this was a common issue and did not look:o
[Nexus One Q&A, Help & Troubleshooting] ellesshoo:
Up until recently, the corporation I work for only authorized blackberry devices to sync with the exchange servers. They've just recently started allowing iPhones and certain android devices to do the same.

On the corp intranet page that deals with this it explains that once you setup activesync a phone lock passcode is required, screen timeout of less than 15min is required, and 5 incorrect passcode attempts, lost/stolen, or something like leaving the company will result in a wipe that will affect non work related data loss as well. The next sentence then says that if it can't be wiped remotely it is the employee's responsibility to do so.

I don't know if some of that wording is from the blackberry only days or what.

If I were to go ahead and get authorization for this, would setting up an activesync with the corporation exchange server really allow them to wipe my phone, including personal data? Would it really make my phone require a passcode and limit my screen timeout all by just syncing?

I just don't know what kind of control simply setting up an activesync account is really possible.

I hate using our web access bc it requires and id and 2 passwords and even though I can use lastpass to make that easier its still slow/inconvenient.

I don't want to ask IT about all this bc I don't want them to think I'm trying to get around the system or give me an incorrect answer (fortune 100 company, they deal with a lot and don't know everything about everything ).
[Nexus One Q&A, Help & Troubleshooting] Jack_R1:
One of the features introduced in Froyo with Exchange/ActiveSync support was remote wipe. I believe they'll have no problem wiping your phone, unless you disconnect that account first.
[Nexus One Q&A, Help & Troubleshooting] ellesshoo:
I'm actually less concerned with wiping than I am with being forced (by that I mean them somehow enforcing my settings such that I can't make my screen timeout longer than 15min or have to use a passcode to come out of sleep). I've never lost a phone and am willing to deal with consequences of not having a damn unlock code. I just don't want my phone to be locked into particular settings. Hope that makes sense.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Jackasaur:
Is there a way to change the boot animation of my hd2 while it boots up android?
[HD2 Android Q&A, Help & Troubleshooting and Genera] Jackasaur:
nvm I learned how to do it.
[HD2 Android Q&A, Help & Troubleshooting and Genera] tobiascrystal:
really

I would like to know how to do the same could you give me a link or discription of how to do it?
[HD2 Android Q&A, Help & Troubleshooting and Genera] hoss_n2:
I want to know too ,share your info
[HD2 Android Q&A, Help & Troubleshooting and Genera] UN150N:
http://xdaforums.com/showthread.php?t=731614

Changing the splashscreen for your own.

Splashscreens. We all hate the operator splashscreens, and some of us like to have our own custom ones.

The process is simple.

1 - create your image, 480 x 800 as a 24 bit bmp.

The process fails if the bmp isn't 24bit.

In photoshop, choose save as BMP, and if it only gives you the option of 8 bit colour, then cancel out of the save, click Image - Mode - RGB Colour. (index colour gives 8 bit BMP)

2 - get nbimg-1.1win32.zip from THIS thread and extract it to a folder with your BMP image.

3 - With nbimg.exe and your bmp in the same folder, open up a command prompt** in that folder, and issue the command

nbimg -p 18400 -w 480 -h 800 -F nameofphoto.bmp -T 0x600 -S 64 -D PB8110000

This will create nameofphoto.bmp.nbh which you flash using customruu.exe, just like flashing a rom or radio.

This splashscreen will show for the first 12 - 14 seconds, up to the point where the animation splash starts. (Which is part of teh rom, and nothing to do with this).

This new splashscreen will stay until you flash either a new one yourself, or a stock rom, which will return it to stock, or some custom roms also include custom splash screens.

The point is, it's as easy to get rid of them as it is to flash them.

**To open a command prompt in the currently viewed explorer folder in vista/7, you can press shift and right click in the folder window, which will give you the option to 'open command window here', , , , which is handy.

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

Watermarking your Leo

WARNING, NOT SURE HOW TO REVERSE THIS NEXT PART, OR HOW IT WOULD AFFECT WARRANTY.

(Ideas welcome, blank nbh perhaps? Ramifications of flashing a blank nbh?)

in the command

nbimg -p 18400 -w 480 -h 800 -F nameofphoto.bmp -T 0x600 -S 64 -D PB8110000

the 0x600 refers to the memory location where the splash screen is written.

It turns out that you can also flash splashscreens to 0x601 with the same command as above, but 0x601 instead of 0x600

nbimg -p 18400 -w 480 -h 800 -F nameofphoto.bmp -T 0x601 -S 64 -D PB8110000

The splash at 0x600 would show when the phone first comes on, but then change to the 0x601 splash when the RGD info appears, until the animation starts.

The usefulness really comes in when you flash a stock rom, because this second splash isn't removed, (Tested with tmous 2.13 and O2 uk stock roms), so even if your thief has enough skill to know about flashing to wipe all trace, the second splash will remain.

Mine has a 'reward if found' message with contact details, and an image of me, with a warning to potential buyers that it's stolen if the seller isn't me, hehe

As mentioned above, I haven't yet tried to remove the second screen, because i don't want to, but be aware of it before you mess around.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Jackasaur:
http://xdaforums.com/showthread.php?t=710204

I just followed the instructions from here. I booted into Android, connect to my computer and just pushed it to my HD2. Works fine, I couldn't get the sound to work though.
[Vibrant General] GalaxyS_Bweb2185:
I'm just trying to enter recovery console. I have tryed EVERY button combination & used a computer to just did use SDK. Any help would be GREAT ! Thank you
[Vibrant General] MilkPudding:
Just to make sure: you need to release the button at the right time.

Turn off your phone and take out the battery for 5 sec then put the battery back. Then hold power+vol up + vol down together and once you see the Vibrant logo, release the power button immediately WHILE pressing vol up+vol down.
[Vibrant General] GalaxyS_Bweb2185:
That didn't work tryed 3 times.
[Vibrant General] courtmagician:
Have you tried via adb:

adb reboot recovery

I had difficulty getting to recovery when I reflashed the stock ROM via ODIN. But once it was rooted and I got Clockwork Recovery back on there, I haven't had an issue via the button combination t get into recovery.
[Vibrant General] GalaxyS_Bweb2185:
I will try that thx for the info.
[Vibrant General] rbirg:
I was on the same boat as you. I just gave up and did the one-click root process. It wasn't exactly one-click, but it was simple enough. Now I've got the Clockwork ROM manager, which will let you boot into its recovery through the application itself.
[Vibrant General] GalaxyS_Bweb2185:
I downloaded the one click lag fix app that roots your phone & fix the lag but I just can't get into recovery mode.
[Vibrant General] andryga:
I was in the same boat then read to do the 3 button thingy but do not let go of anything until the 2nd time the word vibrant comes up then let go of everything...after hours of frustration,i can't believe how easy it was....not sure why this tip is not in a sticky or easily found on xda.
[Vibrant General] rustyrebar:
that does not seem to work. I am pretty sure the newer models have this disabled somehow.
[Vibrant General] JakeRadden:
Not true, I just bought my vibrant yesterday and I can get into recovery console just fine...
[Vibrant General] option94:
are you rooted?

Download a terminal emulator from the market.

then do

su

reboot recovery
[Vibrant General] GuestK0080:
What date code is on your vibrant box? I am on my second phone both built in august and the buttons do not work on either. I had to root via adb recovery. The earlier built phones are rumored to be fine. Dosent seem to matter when you got the phone more when it was made.
[Vibrant General] SugarMouth:
My first Vibrant got into recovery no problem, I received a replacement phone which would not get into recovery using the hardware buttons. I called T-Mobile and told them of the problem and they sent me out a new phone. This last one boots into recovery first try. I know there is a common problem with some Vibrants out there not booting into recovery, thankfully T-Mobile will exchange if it won't.
[Vibrant General] JakeRadden:
Let me check when I get back home. Is this a t-mobile acknowledged issue with vibrants now?
[Vibrant General] atoz350:
When mine gets finicky, I just plug it to my Windows machine, Enable USB Debugging, open the command prompt, and type "adb reboot recovery" without quotes. Works every time. You can also use "adb reboot download" to get into download mode.
[Vibrant General] trunkstar1:
For what it's worth, this helped me.

Hold volume up, volume down, and power all together, wait for Vibrant to come for the second time, then let go of the power button but not the menu button. After another second, I let go of the volume buttons and instantly went into recovery.

Good luck.
[Vibrant General] spacecasespiff:
I tried terminal and it said it was not permitted
[Vibrant General] floepie:
Someone on the I9000 boards posted that recovery can also be invoked by heat! He used an oven, but suggested a hair dryer to be safe.
[Vibrant General] sym1:
I agree with this one. My Vibrant has a date of 8/14/10, and for the life of me it will not button into recovery. I really have read every thread on the topic here as well as other android forums, and tried every combination (over and over).

Rooting was a no brainer with one touch, and with that, I can get to recovery easily. The problem I see, is in the event of a miss step somewhere down the line.

I can't tell you the relief that I felt doing a battery pull to button recovery with my G1(many times). When you are in a bootloop or the like, and nothing else will work, you just need that capability.

Sadly, my Vibrant will be going back because of this. I don't understand why they would hobble the devise this way. I'm sure they will get many more phones returned because of it.
[Vibrant General] dexim:
You need to type su first.

From terminal:

su

reboot recovery
[Vibrant General] opiomorph:
I was having a problem with this as well, and I also couldn't download anything from the market. I went to Applications > Manage > Filter All > Download Manager, then cleared the data, and everything worked fine after that.
[Vibrant General] gmonies21:
You must have your phone rooted first, I cannot get into recovery with the 3 button, but with a terminal emulator works perfectly for me, just need to root first so you can have superuser permission.
[Vibrant General] p()()pypants:
Open the back of your phone of you don't mind and tell us the (2) 2 digit numbs with a period in between them inside, its the manufacturing date... The date is also on your box if you ask have it.

Pooped from my Samsung Vibrant using XDA app... Dont mind the skidmarks...
[Vibrant General] p()()pypants:
Wtf, lol

Would love to see how many losers try this option

Pooped from my Samsung Vibrant using XDA app... Dont mind the skidmarks...
[Vibrant General] p()()pypants:
Good thing to know, I am expecting a replacement in the next couple days and if it didn't manually boot into recovery I would refuse the replacement, so nice to know they will just send another willingly instead...

Pooped from my Samsung Vibrant using XDA app... Dont mind the skidmarks...
[Vibrant General] p()()pypants:
What problem? couldn't boot into recovery using hardware and your saying out was cause of old data on the market?..... I highly doubt this.

Pooped from my Samsung Vibrant using XDA app... Dont mind the skidmarks...
[Vibrant General] opiomorph:
Don't see any reason to lie to you. The first thing I noticed was that I couldn't get into the recovery menu, then I noticed that I couldn't download anything from the market, then I noticed I couldn't do a factory reset, then I came on here and described my situation and got a fix as I described and everything started working again. I can't make much sense of it either, but I'm not really going to start questioning it now that my phone works again.
[Vibrant General] GalaxyS_Bweb2185:
I used Android SDK to enter recovery mode thats for all the help sorry for not posting sooner that I rooted it.
[Vibrant General] mr2t32:
check the date on your box. if it's in Aug., you are pretty much locked out from using the vol. keys to gain download and recovery mode. There is nothing you can do other than using ADB or the one click root. And try to stay away from odin unless you really know what you're doing.
[Vibrant General] Scorpic1:
Have a same problem. Cannot entering in download mode and cannot rooting.

$ su

Permission denied

after:

adb reboot download

reboot only.

adb push update.zip /sdcard/update.zip

* daemon not running. starting it now *

* daemon started successfully *

failed to copy 'update.zip' to '/sdcard/update.zip': Permission denied

Why i can get root?
[Vibrant General] newtrip:
There is not enough coverage of this issue. I just sent a tip to Engadget Mobile about this issue, hoping that we can get some press or publicity out there on this issue. I would encourage any of you to do the same, we need to make it known in a more public fashion. Maybe it would also be worth submitting to other sites as well? If Engadget picks it up at least it will trickle it's way to other sites.

go to mobile . engadget . com (without the spaces)

Scroll to the bottom of the page and click "Tip us on news" on the right hand side.
[Vibrant General] qtilt112:
apparently samsung canada had acknowledged the issue and is working on a fix:

Samsung Mobile Canada Thanks to everyone for your continued patience and feedback as we work through the three-button reset issue on the Galaxy S Vibrant. Rest assured, it is a top priority. Please stay tuned for updates this week.

9/13 @ 10am

unfortunately, i cannot post links so just do a google search for "samsung mobile canada facebook." it should be the 1st link.
[Vibrant General] newtrip:
I saw their response there, but the UK, Australia, and US Samsung Mobile Facebook pages have not even acknowledged this issue even though people are asking them about it. I have a Captivate and am in the US, but am still affected by this issue.
[Vibrant General] qtilt112:
fortunately for us, someone here on xda would probably mod the samsung canada fix to apply to all phones... i hope
[Vibrant General] ryanjj2000:
Vol Up + Home Key + Power On Worked!

After a lot of wasted time i decided to try some different combos and lucked out on the first try. Not sure why this worked but it did. I think quality control may be an issue here.

1. Pull battery

2. Push vol up and home button then press power button simultaneously

3. Hold all 3 buttons until the phone flashes the galaxy logo for the second time then release the power button. DO NOT LET GO OF THE VOLUME UP AND HOME BUTTON. The recovery console should open up.

Phone build is 09/10.
[Vibrant General] Br1cK'd:
August 17th here, can get into both recovery and dl mode fine, it took a little while to get the button combos right trying all the methods out there, but its possible with some patience.
[Vibrant General] icandy75:
There are some phone that are hardware locked and yes TMobile will replace them. They did for me with no issues. This problem has been solved using the method here:http://xdaforums.com/showthread.php?t=804305

Best of luck
[Vibrant General] nzahorchak:
Finally! Thank you! I spent the last 8 hours trying to find a workaround (or a fix) for the inability to reboot into recovery without being able to use the 3 button method on my T-Mo Vibrant (T959) to install RyanZA's OCLF. Nothing was working for me until I saw and tied your suggestion.
[Vibrant General] scrizz:
there's always the JIG

;)
[Vibrant General] Kubernetes:
Wow, old thread.

I've said it before and I'll say it again: If you know your Vibrant is hardware locked, just take a few minutes to learn to use adb and Odin and then flash the hardware lock fix. Just read this:

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

Yes, this is a file you have to flash ONCE and it will remove the hardware lock, so that you can properly enter recovery and download mode.

The post is kind of old--the latest versions of Odin are much better and won't brick your phone. Just make sure to check md5 sums so you know your file is uncorrupted.

It's stupid easy, and once you've done it your Vibrant is effectively unbrickable (well, okay, you probably can BRICK brick your phone, but I think that's pretty rare with the Vibrant.
[Desire General] Andy`:
Recently upgraded my contract with Orange and picked the HTC Desire previously having Hero and enjoyed it.

Having previously owned the Hero i had some knowledge on the Android system, so began to root, flash custom recovery and rom.

After rooting using unrevoked and flashing amon ra recovery.

I selected Cyanogen 6.0 desire rom, all flashed well, also flashed the latest radio which is where i think the probelm persists.

After reading that flashing the latest radio onto branded orange desire locks the sim, i purchased an unlock code htccode.com to see if that solved my problem, didn't help one bit, i don't even think the code will work unless im running the stock orange rom, but tried anyway with tmobile sim card, network unlock successful but phone says emergency calls only, so obviously didnt!

Can anyone help me get my htc desire back to orange stock rom? so i can then unlock the phone properly and flash a generic rom.

Hope all that make sense.

Andy.