yashsingh1/xdaforums huggingface dataset:
[Vibrant Q&A, Help & Troubleshooting] Br1cK'd:
One thing you can try that worked for me on a couple of machines that wouldn't recognize dl mode is the following. Download the 64 bit drivers, can be found through the vibrant bible, and unzip the folder, should come in .zip format. Then put your phone into dl mode, plug it into your computer, and let it detect the devices and not load the drivers. Once its recognized the unknown device, access your windows device manager manager, right click on the unknown device, choose update driver, do not let windows auto detect it, rather, manually install the driver by selecting "install from a specific location", then "include this location in the search" and use the browse button to navigate to the driver folder you unzipped. Let it do its thing and should then be recognized in dl mode.
[Droid X General] iceblue11:
Used Boot Straper from Market flashed .320 from .315 everything went correctly verified update in settings. Booted with bootstraper again cleared all the partitions like cache installed

2.3.340 Kernel Updater (2.6.32.9-g55626e1) .zip

BP_C_1.09.07P Baseband Updater .zip

2.3.340 System Updater .zip

ApeX 1.3.1 .zip

note none where sbf files rebooted the system and im stuck in bootleader and reads

Bootloader

30.04

err:A5,69,35,00,27

Battery OK

OK to Program

USB connected

Data Cable

Nothing I do can avoid botloader. After Finaly getting RSD Loader 4.9 to reconize my device I tried to cure it by flashing Droid Life 2.3.340 .sbf file and RSD give err 0x700
[Droid X General] zehkaiser:
Try the .320 SBF, then .340 SBF. If that fails you will have to wait until you can get a hold of the next full SBF.
[Droid X General] iceblue11:
I went to a new computer and I flashed .15 SBF I belive full bc it was like 400mb with success on flash but my cute little android man pissing on craple is gone and boots immedieately into BL saying no system. So Now flashing .340 SBF and see what happens. If this don't work I am fresh out of ideas
[Droid X General] mlclm:
That won't work. Flash the full .320 SBF then the system only .340 SBF and you'll be fine.
[Droid X General] willjohnson:
This worked for me. You should do it this way.
[Droid X General] bouchigo:
If you are on stock 2.3.15 now, then just go to Settings>About Phone>System Updates. This should do the OTA update and bring you to 2.3.340. No Need to flash the 2.3.320 full sbf and then the 2.3.340 sbf.
[Droid X General] iceblue11:
Your right that won't work. Its stuck in loader so no system will boot. So I need to go find the 320 sbf in order to get out of this. I'm asuming its the 30.04 bootloader preventing the 315 sbf from bringing me out and why the 340 system sbf won't rescue me. Ok ill try it thanks
[Droid X General] bouchigo:
Yeah, I think I remember reading if you have 30.04 bootloader, the 2.3.15 sbf will not work, but I can't remember for sure.

To check what bootloader you have, power off your phone. Now press and hold both volume keys; keep pressing the volume keys as you power the phone back up. The phone will proceed to enter bootloader mode and show you what bootloader you have.
[Droid X General] iceblue11:
Sorry for the pore responses and spelling. I was sneaking posts at the Verizon store while fighting with the manager to please charge my battery so I could flash my phone. Battery died on me apparently it will not accept any type of charge from the phone when stuck in boot loader.

bouchigo - Thanks you been a big help bud, Finally! Someone says how to put the X into that bootloader I couldn't figure it out so went with the clockworks .zip 340 system flash instead of the sbf. Had to google for the 320.sbf couldn't find much on here for this so it is downloading now and see what happens after that. I did find during my search that if the bootload was 30.04 the phone would not accept a 315 system so that is indeed accurate.

mlclm - Thank you
[Droid X General] iceblue11:
w00t phone just booted out of the dead with the 320.sbf!

Curious thing is what in my method caused the phone to do this?

Well no matter if im on 320 or 340 the phone wont activate over air programming and thus cant go anywhere past that damn droid icon, coincidence of bad timing was an outage in service on my area life is peachy now
[Droid X General] willjohnson:
Strange. I have had the ota programming fail and I had the option to skip. Then open dialer and do *22899 to program.
[Droid X General] bouchigo:
Try doing a "data/factory reset" and "wipe cache", after that reboot and see if fixes your problem.

1. Power off your phone

2. Press and hold the home key (the button with the little house on it).

3. While holding the home button down, power up the phone. Once phone starts to power up, you can let go of the power button, but keep holding the home button until you see a triangle with an exclamation mark in the middle with a little android underneath the triangle.

4. Now, press the search button (the magnifying glass button).

5. Scroll to "wipe data/factory reset" (with the volume up and down buttons) and select it with the camera button.

6. Now scroll to "wipe cache partition" and do the same as you did previously.

7. Reboot and hope it solved your problem.
[Droid X General] iceblue11:
Yeah I did all that to try and skip the programming. I could do emergency dial and do *22898 and get to customer rep who found a outage in my area after that was fixer the phone programmed like it should and all was good.

Im about to post on Apex thread about a small issue. But all together the setup is working so much better faster cleaner then the old setup so 5 *'s.

For some reason if you hold power button and select restart the phone will boot into clockworks recovery every time. Uninstalled clockworks app and still does it. And currently have 2 SMS apps and wont let me uninstall any of them and its causing all SMS to be duplicated. Only bugs so far
[Droid X General] forever29:
I had that service problem too when I SBF'd. When I was on .15 I tried to use the

system updater on droid world (stupidly) to .340 and the patches. So after I got

stuck on the bootloader like you did, I just SBF'd to .320 and then went back

to droid world and then installed the system updater (.340) with bootstrap and

then the following patches. I had to go outside to get at least one bar of service

in order to activate the phone. After about 20 minutes or so I started getting

signal back the way it was before. I *228 again a few times to get rid of the

roaming icon. Sometimes it takes a few programs to get you to the correct towers.

Here's the droid world thread.

http://www.mydroidworld.com/forums/...ystem-baseband-2-3-340-kernel-bootloader.html

Note: I of course activated the phone before using the system updater and patches.

Gain your signal back first before you get onto .340
[Droid X General] willjohnson:
Open droid x bootstrapper and hit the bootstrap recovery button. This should stop you booting to ce everytime you restart.
[EVO 4G General] 5-6-ACE:
Ever since the newest update has been released for the EVO I've been trying to update and have been unable to thus far.

When I try to do the Software Update from the phone, it will just stay on the "Checking" window for hours without doing anything... I've tried to connected to 3G AND 4G (I know it doesn't work on WIFI)

I've also tried manually updating it and it gives me some error... Im not sure what the error is but I'll try again in a few mins and update the thread...
[EVO 4G General] _MetalHead_:
Are you running a stock ROM?
[EVO 4G General] 5-6-ACE:
Yeah, never been rooted.
[EVO 4G General] _MetalHead_:
What software version are you currently on?
[EVO 4G General] 5-6-ACE:
3.29.651.5
[EVO 4G General] _MetalHead_:
I'm not on a sense rom right now but i remember there were two different options for updating, one was for firmware update and the other was for system or software or something like that. Which one are you checking, I'm pretty sure its supposed to be the software update, not the firmware one.
[EVO 4G General] caguirr4:
That would be correct mr. Metalhead. The firmware is not the one being updated the software is. Try that op then let us know.
[EVO 4G General] 5-6-ACE:
I've been trying the Software Update... I've also updated everything else...
[EVO 4G General] iaccax:
Just becareful with the update if it updates to the 3.70 check your wifi an make sure it works cause I got wifi errors and sprint could not fix it so I got a new one today
[Droid X Themes and Apps] miguel11691:
I cant stand the regular music player.. its horrible... is there a better player like the galaxy s or sense music player available... I have the latest darkslide 4.2 rom and this will put my phone over the top
[Droid X Themes and Apps] drewoid:
try miui music. that seems to be all the rave. I personally love the 2.2.1 com.android.music.apk... but don't know if its compatable with droid x.. can be found in the eris forums under development/froshedyo/version 7. long press volume to skip tracks but a similar UI just no visuals so it runs smooth
[Droid X Themes and Apps] mlclm:
Doubletwist with AirSync. :)
[Droid X Themes and Apps] ilearnedwar:
PowerAmp. Best player out now, sound is terrific, and the EQ allows for audio tweaking to fit anyone's taste. Costs 4.99 in the market, but is definitely worth it if you care how your music sounds.
[Droid X Themes and Apps] kodakeos:
i reluctantly bought it and its pretty awesome. Just needs to fix the headphone removal service eating battery and it would be perfect
[Droid X Themes and Apps] ilearnedwar:
You can totally change that in the settings :)
[Droid X Themes and Apps] zanix:
I use Winamp

Its free on the market

It can do wifi sync if you have Winamp installed on your computer
[Droid X Themes and Apps] Joco1289:
I use mSpot. Its an awesome cloud based music player
[Droid X Themes and Apps] Ubermicro13:
+1 More for PowerAMP.
[Droid X Themes and Apps] Jubakuba:
Lithium user here...and I personally love it.

The UI was just so original that I had to have it. I even went through the trouble of asking the dev to put it up on SlideMe market...as my bank won't allow charges in a foreign currency.

*OT*

Goddamn market...I swear...please convert currency FOR ME so my bank allows me to buy foreign applications...Too many times; I've wanted an app...but had to pirate it because it wasn't in the market or SlideME.
[Droid X Themes and Apps] Elite Precision:
Player Pro (Paid) or Lithium Player (Paid). I hate the stock android player - no intuition whatsoever. I hate Apple products but the iPod/Phone music player is very nice.
[Droid X Themes and Apps] williams37:
I didn't hate the stock music player, but I downloaded the "leaked 2.3 music player apk" and I love the look and feel to it. With that app open, it feels like I am on an actual mp3 player and not a phone.
[Droid X Themes and Apps] joshmerd:
Thanks for the info. I downloaded it and am loving the interface!
[Droid X Themes and Apps] williams37:
Glad to hear it. Mine worked amazing up until changing a few phone files for theme-ing. Now my music skips when running in the background if I'm doing any type of navigation on my phone (scrolling through apps, looking through facebook) Have you run into anything like that with the leaked app?
[Droid X Themes and Apps] _kast:
I use the winamp player, its pretty good
[Droid X Themes and Apps] keefles:
I've noticed this. Also, tons of forcecloses with the honeycomb music app.
[Droid X Themes and Apps] BFS1983:
One of the forum members on this site leaked a new motorola media player, its been reviewed on several droid blogs to be great, but apparently Motorola made him take it down.
[Droid X Themes and Apps] jonwgee:
tried real player yet? its not bad
[Droid X Themes and Apps] frub3nz:
The eq on poweramp makes the $5.00 worth it.
[Droid X Themes and Apps] d1973b:
PowerAmp or the Gingerbread music app!
[Droid X Themes and Apps] WonderDroid:
Another happy PowerAmp user here. It is very quick when switching tracks etc.
[G2 and Desire Z General] eax05:
How I was trying to root my phone by was unsuccessful.

Now I am trying to figure out away to erase the files that I pushed on my phone. I am trying to get the phone to the factory settings.

How would I do that???

btw can i root a version 2.2??
[G2 and Desire Z General] KiNG OMaR:
What method did you use to attempt at root?

What files did you push?

And yes, you can root 2.2 :)
[G2 and Desire Z General] eax05:
I used the ATB method i think
[Nexus One Q&A, Help & Troubleshooting] XZQ't:
My N1 power button is unresponsive to any press and I realized it's completely broken. Now I can't turn off screen, turn off a phone and when i turn it off I know I won't be able to turn it on again.

I live outside US and can't get N1 to repair.

Do you guy have a way to turn N1 on without power button ?
[Nexus One Q&A, Help & Troubleshooting] danger-rat:
Quickboot for shutting down, restarting etc.

Lock enabler for sleeping the screen.

Some short of trackball wake to wake the screen.

To restart from power off, just pull and reinsert the battery a few times, or pull and reinsert the sim.

Theres a thread on here, where someone replaced the power button for about $30...
[Fascinate General] hbc.ciccone:
After reading, reading and more reading on these forums (thanks to everyone posting) I've finally broken into the true capabilities of these phones. I come to a question every time i'm surfing around tho...

Voodoo or not?

If so, what do the sv, lv, ov remarks mean when choosing a kernel? I havent and dont want to mess things up on my phone...

any insight is always appreciated
[Fascinate General] bwheelies:
I guess you run what the phone can handle. From a logical point of view, if you increase the performance of something it will need more fuel to operate. Some folks seem to be able to get away with low voltage or ultra low voltage kernels at the higher processing speeds without ill affects but it was the opposite for me. When I tried the OTB ul1300, lv1300, or sv1300, it would constantly have issues running most any app, and the lower the voltage the more it would boot loop. With the over voltage 1300 I was able to almost function normally but it still wasn't steady enough for daily use. Any 1200 I tried worked with no problems.

You go with stability and performance that suits you. If I were you I would start at the top but have all of the kernels you want to try at the ready so you can go into recovery and flash another and try again until you settle on what works best. The 1300's are almost guaranteed to give you problems but it's a simple fix if you have them all on standby.

Whether to go with voodoo or not; it works very well and with the new recovery(red lagfix version), it is a piece of cake to disable. Just go to voodoo menu and disable for next boot and enable the partition conversion. As long as you are testing voodoo kernels, you don't have to mess with that setting. Just flash the next one.
[Fascinate General] xlinth:
I came from a g1,mytouch,and droid 1 to the fascinate. Rooted from day 1. I also questioned the voodoo method. I chose not to because of the hassle of removing it to install certain roms then reinstalling it. It fixes lag in the file system but i truely haven't noticed any without it. And to answer your kernel questions....oc=overclocked sv=standard voltage and lv=low voltage (doesn't always work with all phones)
[Fascinate General] s44:
Yeah, you don't have to do that any more. Voodoo5 plays well with Clockwork (or, actually, comes with its own custom Clockwork), so you only have to remove it to switch to a non-Voodoo kernel. Nandroid backups, restores, etc. can all be done with Voodoo active.

Plus removing it doesn't hang up much (if at all) these days.
[Fascinate General] hbc.ciccone:
What I'm battling is battery life, I'm running DJ05/SuperDark v.9/StupidFast 1.54. I use my phone for almost everything, all the time(even now via wifi tether for internet). I'm expierencing moderate batt life. Although I have ample oppurtunities to be on a charger, I'm worrying about those times I cant. Obviously I want great life w/ great performance. Maybe I'm watching the battery too much and expecting more than I should. I guess I'm still trying to find the best combination for my needs. Can't wait for cyanogen.

props to all the devs
[Droid Eris General] jcase:
I apologize for my absence, life has been crazy. Just wanted to stop in and say hey, android isn't forgotten. Got something neat under my hat, as soon as I have time. Hope everyone is having a good new year.

Would like introduce my new daughter Carrie. Born Dec 29 2010, in her first outfit.
[Droid Eris General] bkratzer83:
Congratulations
[Droid Eris General] synesthete:
Awwww, Congratulations!
[Droid Eris General] bftb0:
good to hear from you j

Congrats on the new addition to the family!
[Droid Eris General] CondemnedSoul:
Congratulations and best of luck to you and your family.
[Droid Eris General] strongergravity:
Congrats!

When will she get her first phone?!? :D
[Droid Eris General] Chevelle1768:
Congrats!
[Droid Eris General] roirraW "edor" ehT:
Awwwwwwww! Congratulations!
[Droid Eris General] MrObvious:
How cute. Congrats on being a dad. Now...........
[Droid Eris General] scary alien:
jcase,

Congratulations on the birth of your new daughter---hope you, your wife, and new daughter are all healthy and doing well.

Good to hear from you again.

Cheers!
[Droid Eris General] johnrbrown1968:
Couldn't imagine a better Christmas gift! What an awesome blessing! Congrats!
[Droid Eris General] USSENTERNCC1701E:
Congratulations to you and yours and best wishes. I think you've been absent from the community longer than I've had my account, but I know I've benefited greatly from your works regardless. Looking forward to your hint of things to come...
[Droid Eris General] johnrbrown1968:
I have to echo this comment!
[Droid Eris General] Zalatorisaurus:
Congrats. Good to hear from you again.
[Droid Eris General] dianeofarcadia:
she's adorable jcase,

welcome back and congrats. ;)
[EVO 4G Q&A, Help & Troubleshooting] scooter185:
Burnt droid 1.4, netarchy 4.3 nosbc static universal, I had a boot loop earlier and upon getting back into the os after a battery pull my MLB 2010 app as well as pandora are gone and wont reinstall from either the market or titanium backup. I'm at a loss with this :confused:
[HD2 Android Q&A, Help & Troubleshooting and Genera] Jarrett76:
I have installed the Nand on my hd2 and everything works spectacular except I am unable to send mms .... I can recieve them ! I have tried many different APN settings to no avail ! My internet works fine and I can receive pics ! Like I said I have tried every APN setting suggestion given but its not working . My mms just sets in the sent box with the timer next to it
[HD2 Android Q&A, Help & Troubleshooting and Genera] gijoe69:
Someone on another thread reported that he made 5 APN account's to make MMS work not sure haven't tried it yet
[HD2 Android Q&A, Help & Troubleshooting and Genera] bjcolema:
You should post this in the thread for your rom. Chances are someone else had the issue. It is not a general nand problem.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Wickster:
Which NAND rom are you using? I've noticed that roms using MDJ's kernel usually needs to be patched before you flash it to your phone in order for the mms to work. Other builds based on kernels like Hastarin's, Projection's and gauner1986's usually works without a patch. So far from the countless builds I've tried, CMYLXGO's Topia series are usually the most compatible build for TMOUS HD2 phones here in the states. Might want to that. But if you really like the rom you are using, try searching for the appropriate patch for it. Then share your steps to resolve it here so we may all learn from it.
[HD2 Android Q&A, Help & Troubleshooting and Genera] prosto:
It has been discussed multiple times on these forums.

The problem is Google DNS (8.8.8.8, 8.8.4.4) don't recognize mms.msg.eng.t-mobile.com

So, either you change DNS to TMOUS, OpenDNS, etc. ones, edit your APN settings or use different patches.

Read this thread, search the forums and good luck!
[HD2 Android Q&A, Help & Troubleshooting and Genera] c00lfon:
Use mobile network widget. Widgets -> Settings -> Network/Mobile network/smth like that. Just disable it, send/recive MMS, and enable it again. You can also use "APN on/off Widget" from Market.
[HD2 Android Q&A, Help & Troubleshooting and Genera] c00lfon:
I think it is general problem with APN's - Android can be connected to only one access point at a time, and that cause some problems. I noted same issues in HTC Wildfire, Samsung Galaxy S, HTC HD2 Android Desire/Desire HD/Nexus One from NAND and SD (Android 2.1/2.2/2.2.1). In all cases "APN on/off Widget" or similar software helped for me.

Finally there is another solution - just enable wifi, wait for icon in notification bar, and try to send MMS.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Nismo300zx:
Aside from the topia roms are there any builds that can send mms without a patch? And not come out blurry? Preferebly a band desire z rom
[HD2 Android Q&A, Help & Troubleshooting and Genera] jose makalolot:
I am currently using mdj gingerbread 1.5 and though it scale down the pics, it is not blurry. O tried using topia but i get blurred mms.
[HD2 Android Q&A, Help & Troubleshooting and Genera] wrecless:
edit your APN to this and it will work

MMSC http://10.165.193.22/mms/wapenc
[Epic 4G Android Development] msponsler:
Yeah, I know...let's get a stable Froyo first.

But...

I pulled the 2.3.1 (gingerbread) source, and it's currently building. I hit a couple of snags, but I'm off and running so far.

I've also compiled the latest 2.6.36 kernel -- compiled, not tested! Don't get excited just yet.

I'm not going to lie, I'm green to android. But I've worked with Linux professionally for 15+ years. I've been compiling kernels since Linus released 2.0 oh so long ago. Building Linux x86 from scratch (go gentoo linux!) is nothing new to me. But android and arm...ehh...bear with me.

So is anyone else trying to do this? I'd like to collaborate and hear about your progress and any problems you've had. No need to try to reinvent wheels or anything.

Step 1 is getting it to boot...
[Epic 4G Android Development] msponsler:
Here's my 2.6.36 kernel zImage file and .config build if anyone is curious.
[Epic 4G Android Development] plapczyn:
My suggestion...change your title to [Dev] AOSP Gingerbread. Start a github or similar repository and get cracking. I'm sure there are plenty of people that would consider jumping on board. With the Nexus S source out, some things shouldn't be TOO hard, but I think porting the CDMA stuff is probably a huge challenge.
[Epic 4G Android Development] sweepingzero:
id jump on board if i knew what i was doing :)
[Epic 4G Android Development] dreamsforgotten:
Glad your focusing on this! I don't think we have to finish froyo to start gingerbread. Not sure how much I can help but hit me up if you need anything done.
[Epic 4G Android Development] bryanfritz1:
I glad too see that someone is taking initiative here. My thinking all along is the drivers for froyo will most likely work in someway for gingerbread but without kernel source for froyo yet, I would think you would have to start from ground up. But good luck to you regardless.
[Epic 4G Android Development] akijikan:
This is delicious. Now it only needs sauce.

Everyone can learn from the OP's example. Less posturing more action.
[Epic 4G Android Development] Ranger093:
About time!
[Epic 4G Android Development] somedude0608:
Thank you for working on this. I never really understood the source argument. I just put gingerbread on my old hero and everything works except for camera and screen rotation. It sure as hell doesn't have an official/leaked release or even froyo source. Anyways just ranting about the things I hear. I know I dont have the skills to work on this stuff, so thanks for the effort.
[Epic 4G Android Development] bubby323:
I have it just about booting(;