yashsingh1/xdaforums huggingface dataset:
[Android Themes] suaverc118:
Re: [Theme Chooser][BETA]dy-NASTY "Android Building Blocks" **02/11/2013

Thanks bro for the icons
[Android Themes] varun26296:
Re: [Theme Chooser][BETA]dy-NASTY "Android Building Blocks" **02/11/2013

Hey guys can we apply this icon pack in TSF shell?? I just love the icons but I cannot ignore the customisation options offers by TSF shell...
[Android Themes] mjs2011:
Re: [Theme Chooser][BETA]dy-NASTY "Android Building Blocks" **02/11/2013

Bam!
[Android Themes] inferno17x:
Re: [Theme Chooser][BETA]dy-NASTY "Android Building Blocks" **02/11/2013

Just purchased the icon pack and looks great!
[Android Themes] mdroid28:
Re: [Theme Chooser][BETA]dy-NASTY "Android Building Blocks" **02/11/2013

Nice job on the icon pack. Way better than the other $4 one I bought.
[Android Themes] mjs2011:
Re: [Theme Chooser][BETA]dy-NASTY "Android Building Blocks" **02/11/2013

Where did you find that wallpaper?
[Android Themes] mdroid28:
Re: [Theme Chooser][BETA]dy-NASTY "Android Building Blocks" **02/11/2013

On Google. I also posted it a few pages back in this thread.
[Samsung Galaxy Gio GT-S5660] aronk:
How can I add or replace a keyboard in a custom ROM. I want to replace the samsung keyboard of this ROM: http://xdaforums.com/showthread.php?t=2136550 for the CM7 keyboard (because the number of dictionaries).

Someone knows how can I do this?
[Samsung Galaxy Gio GT-S5660] MoltenMotherBoard:
Download the .apk file and push it to /system/app (to keep it in the ROM when you make a data wipe) or to /data/app (when you make a data wipe, you'll lose it).

Otherwise, easier method, find it on GooglePlay and install it.
[Samsung Galaxy Gio GT-S5660] aronk:
I already downloaded the apk of the stock markert and tried also to copied the apk file from a cyanogen rom....but didnt work
[Samsung Galaxy Gio GT-S5660] aronk:
Anyone knows what files I have to copy from the CM7 to get its keypad??
[Desire HD Q&A, Help & Troubleshooting] mc0a:
I've tried to install this --> RUU_Ace_HTC_WWE_1.15.405.1_Radio_12.21.60.12_26.02.00.09_M_test_148662. I thought it was some kind of downgrade, because i couldn't downgrade with Ace Hack Kit. In the midlle of installation, about 22%, when my HDH rebooted, said error, now my phone won't even boot antything, only when I put it to charge it shows orang led indicator, and after some time it shows black screen with silver HTC screen.. :/ Desperate, any kind of help, suggestion please..
[Desire HD Q&A, Help & Troubleshooting] dannyboy_uk12:
Connect it through the ace hack kit, and start from scratch.

did it automatically download the downgrade ruu? Or is that one you downloaded yourself? Did you disconnect it thinking it had finished or something?
[Desire HD Q&A, Help & Troubleshooting] mc0a:
Thanks for answering.. :)

When I've got my phone, it was stock 2.3.5, i've unlocked bootloaders, downloaded ace hack kit, rooted, instaled cwm, s-off, installed couple of custom roms. Then, i've locked my phone via fastboot oem lock. Today, I wanted to unlock it again, to instal sabsa prime, but when i reach fastboot oem get_identifier_token it points to some kind of bootloader err error command. When i started the ace kit it demanded the downgrade, but, when the downgrade is downloaded, pushed to phone, phone restart to hboot, but wont flush it. So, i wanted to downgrade on my own. I've downloaded as i said ruu, started flashing, and thats pretty much it.. It showed error, i havent disconnected it on my own.

I can only connect phone by pressing volume up and power, i have a blinking orange led indicator and it reports as qualcomm cdma technologies msm to my computer..
[Desire HD Q&A, Help & Troubleshooting] yumm91:
i thought that aahk can only be used for the stock rom.. if you already have s-off and have cwm, just flash the new rom in recovery..

Sent from my Desire HD
[Desire HD Q&A, Help & Troubleshooting] bananagranola:
You couldn't have run AAHK on an unlocked bootloader. Exactly what have you done to your phone up to this point in time? What does your bootloader say now?
[Desire HD Q&A, Help & Troubleshooting] mc0a:
i cant enter to hboot, i cant start phone, only when i push volume up + power i have orange led blinking, and when i attach phone to pc, pc recognize it as a qualcomm cdma technologies..

from stock rom, unlocked bootloader via htcdev, used ace AAHK, instaled few custom roms, then relocked bootloader via fastboot (fastboot oem lock), then flashed ruu RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1_Radio_12.65.60.29_26.14.04.28_M_release_225512_signed. After that i wanted to unlock bootloader again, in fastboot got the (bootloader) [ERR] command error !!!, when runed AAHK, AAHK needed a downgrade, downgrade was downloaded, pushed to phone, but when phone restarted to hboot, downgrade coulndt be flashed, it shows PD98IMG-GB2 as a wrong image or something. Then I downloaded RUU_Ace_HTC_WWE_1.15.405.1_Radio_12.21.60.12_26.02.00.09_M_test_148662, started flash, my phone rebooted, and instead rebooting to ruu (black screen), phone just shuted down, ruu on pc showed error, that is it. I've tried to power on phone on different ways, but nothing, just once after i plugged it to pc, showd me black screen with silver letters, now won't even show that. Only with volume up + power, with orange led blinking, and somethimes, after some time attached to pc, phone connects, but how i figured out from computer managment, like a mass storage. Hope you understanded what i said.. :/

Thanks for answering bro..
[Desire HD Q&A, Help & Troubleshooting] mc0a:
i relocked bootloader via fastboot, flashed ruu RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1_Radio_12.65.60.29_26.14.04.28_M_release_225512_signed, so i've lost cwm and root..
[Desire HD Q&A, Help & Troubleshooting] yumm91:
when you shut down the phone and press voldown + power, do you get into hboot? or nothing happen?

Sent from my Desire HD
[Desire HD Q&A, Help & Troubleshooting] mc0a:
no, nothing happens.. its fu*ked up i guess..

Edit:

I connected to usbe, pushed a few times volume down + power, after that nothing happened, i left it that way, after 10 mins maybe it powered on itself, showed white screen with green letters htc, and vibrating constantly.. I couldnt do anything, so i removed battery.. Fight continues.. :D
[Desire HD Q&A, Help & Troubleshooting] leopardtag:
if its vibrating constantly it's bad... correct me if I'm wrong but I think somehow you manage to brick your device...
[Desire HD Q&A, Help & Troubleshooting] bananagranola:
Did your phone ship with Gingerbread by any chance?
[Desire HD Q&A, Help & Troubleshooting] mc0a:
yes..
[Desire HD Q&A, Help & Troubleshooting] bananagranola:
You messed your bootloader. Fix it with instructions from the PDF in post #7 in the thread in my signature.
[Desire HD Q&A, Help & Troubleshooting] mc0a:
i'll give it a try.. thanks.. :)
[Desire HD Q&A, Help & Troubleshooting] bondocel:
If you want step by step assistence go to the irc channel of the aahk team and search help there. I had a lot of issues when trying to gain root so the devs there helped me to do it. It took 2 days to fix. Good luck
[Desire HD Q&A, Help & Troubleshooting] glevitan:
No, hboot fix is no longer supported in the hack kit channel, so you won't get any,answers there. Use ths guide and ask in here if you have doubts.
[Desire HD Q&A, Help & Troubleshooting] mc0a:
i have problems with fastboot.. <bootloader> [ERR] Command error!!! ADB too, probably because usb debbuging.. :/
[Desire HD Q&A, Help & Troubleshooting] glevitan:
Fastboot does not need usb debugging. What step are you in? What are you trying to do?
[Desire HD Q&A, Help & Troubleshooting] mc0a:
http://tau.shadowchild.nl/attn1/?p=188

option two, when need to reboot to ruu.. fastboot oem reboot RUU. I follow that the case are sensitive, only thing i get from fastboot is mentioned error..
[Desire HD Q&A, Help & Troubleshooting] glevitan:
are you in fastboot usb (you have to see that in red in the phone)??
[Desire HD Q&A, Help & Troubleshooting] mc0a:
yes.. phone regonized by pc, proper drivers, on phone red letters FASTBOOT USB
[Desire HD Q&A, Help & Troubleshooting] glevitan:
wasn't your phone booting completely??

Do you mind If I have a look over teamviewer?? make sure that your phone is already in hboot..
[Desire HD Q&A, Help & Troubleshooting] mc0a:
i dont mind now, but i am at work now.. :/ Maybe tommorow.. :/ Not booting, when powered on regular, it comes to white screen with green htc letters, to enter hboot mode takes years, but it gets there.. fastboot is working, but when get to mentioned command, error
[Desire HD Q&A, Help & Troubleshooting] glevitan:
Ok, just let me know when you are able to do it and we arrenge to connect. :good:
[Desire HD Q&A, Help & Troubleshooting] mc0a:
img4.imageshack.us/img4/6800/29227925.jpg
[Desire HD Q&A, Help & Troubleshooting] glevitan:
The command is wrong. It is:

fastboot oem rebootRUU

Not reboot ruu
[Desire HD Q&A, Help & Troubleshooting] mc0a:
My problem is solved with folowing this article..

tau.shadowchild.nl/attn1/?p=188

Tnx goes to glevitan too, he help me a lot. Main problem in repairing.was that the command in article was fastboot oem reboot RUU, but.that was supposed to be fastboot oem rebootRUU. Tnx to all folks, phone is working just fine.. :) :D
[Xoom Q&A, Help & Troubleshooting] Landorin:
Hello,

I have the MZ601 (Xoom UK 3G) and had EOS Everest JB stable on it.

Now I wanted to go back to stock. I downloaded the original firmware from Motorola, flashed the img files with adb and everything was fine (I did not relock the bootloader). The first OTA went fine too, now I am on Android 3.0.1 (H.6.1.-38-1).

It now detects the next OTA (about 44 MB, 63.5.25.en.EU), downloads it, tries to install it but at about 1/3 of progress the green bot of ! appears. I reflashed the stock firmware several times now, same result.

Then I googled, flashed Tiamat CWM recovery, rooted the device and then did:

adb remount (got message: succeeded)

adb shell rm /system/recovery-from-boot.p (message: no such file or directory)

adb shell rm /system/etc/install-recovery.sh (no message, so guess it worked)

Now I have no idea what else to try. I'd like to get back to stock ICS.

edit: reflashed back to stock once more. This time I entered recovery mode before I applied the very first OTA and the green bot of ! already appears, what's wrong here?
[Xoom Q&A, Help & Troubleshooting] XxLordxX:
Hi,

It looks like your problem is not big deal. Just try flashing again all the files and principally DON'T FORGET TO FLASH RECOVERY! And I don't see why wouldn't you lock bootloader :confused:, if you really wants it unlocked and go to stock ICS I'd recommend you to flash stock, lock bootloader and then you update, after you get to the version you want unlock again :thumbup:

Wish you the best luck :D

Any problems please give me an up!
[Xoom Q&A, Help & Troubleshooting] Landorin:
​

Thanks for your reply!

I think I flashed recovery with the specific adb command (see below), not sure, not really an expert. :/ I even wiped dalvik cache and factory reset in cwm recovery before flashing back to stock.

Here's what I did in detail when reverting to stock:

I downloaded MZ601_H.6.1-38-1_Retail_Europe.zip from the official Motorola website, extracted all files and used these commands in adb:

adb reboot bootloader

fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache

Also, I noticed the green bot of ! appears after reboot when I enter recovery mode even before I flash the very first OTA (so just after flashing the stock files and reboot). Looks like recovery is somewhat broken or so? :(

I didn't want to relock the bootloader simply because I might want to root the device once I am back on stock ICS. Basically, I just wanted to get away from a custom ROM (Team EOS).

Would locking the bootloader make a difference for my success? According to google it doesn't but I am no expert to judge it right.
[Xoom Q&A, Help & Troubleshooting] XxLordxX:
Yea, it looks like something is going wrong there...

Try downloading the files again, and then flash recovery. If you have no success try locking your BL, maybe it can works. The two times I went back to Stock I relocked my BL and had no problems to update via OTA. Then you relock your BL and use LordAIOTool to root again, which can easy your work...

Also you should try erasing system, recovery, cache and data before flashing, but it looks like what you did is fine.

Good luck ;)
[Xoom Q&A, Help & Troubleshooting] Landorin:
Thanks! I will give that a shot and post the result here.

By the way, that is one thing I read about and didn't dare to try yet: formatting system.

From what I read, after formatting /system the tablet will no longer be able to boot into android. In that case, how can I perform adb commands still? Afaik USB debugging has to be on but I will not be able to get into settings (due to lack of boot) and turn it on (and it will be off after reflashing afaik).
[Xoom Q&A, Help & Troubleshooting] XxLordxX:
When you format system you can't boot in Android, but you can still flash things via fastboot, which uses a different protocol from adb. There was one time I had to format system to fix a cellphone, but if you don't want to try that, no worries ;), it may turn out without risking :D
[Xoom Q&A, Help & Troubleshooting] dfib1:
I believe in order to upgrade you need to lock the BL. Once you update you can unlock it again.
[Xoom Q&A, Help & Troubleshooting] Landorin:
Okay, downloaded the image again, this time via XDA. Suprisingly, all files were flashed in less than a min each (sometimes flasing system.img took half an hour or longer). Same result though. Since I forgot to lock the bootloader I flashed everything again after reboot:

>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *

>fastboot flash boot boot.img
sending 'boot' (8192 KB)... OKAY [ 49.293s]
writing 'boot'... OKAY [ 2.155s]
finished. total time: 51.477s

>fastboot flash system system.img
sending 'system' (262144 KB)... FAILED (remote: (00120003))
finished. total time: 1196.176s

Not sure why it failed here, worked dozens of times. So I simply decided to reflash system.img once more in the same run:

>fastboot flash system system.img
sending 'system' (262144 KB)... OKAY [ 25.391s]
writing 'system'... OKAY [ 14.744s]
finished. total time: 40.136s

Worked fine apparently, then continued from there as normal:

fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock

All went well this time, no error messages on the latest full reflash or locking bootloader. Then rebooted, and now it is stuck at the Motorola boot screen:

Failed to boot LNX 0x0004
Starting RSD mode 2
(charger information bla bla here)

Not sure why this happened and what this actually means? It won't boot up and since the bootloader is locked I can't enter recovery or anything. What do I need to do now?
[Xoom Q&A, Help & Troubleshooting] XxLordxX:
Man... You forgot to flash the kernel (boot.img)!!! And it's probably appearing because of this small mistake!!! Now that you're on RSD Mode 2 you have to fix it another way... I never went to it (only went twice to mode 3), so sorry, I can't help you this time :(, I will search a little and see what I can do for you.
[Xoom Q&A, Help & Troubleshooting] Landorin:
My mistake on posting, I did flash boot.img before that, corrected my previous posting.

Now I am stranded. And I can't even turn off the device on boot screen.

edit: rescued it, thanks to this posting:

Pushed power + vol up for reboot, waited 5 sec, then held vol down until fastboot appeared (kept pressing the button for about 17 sec until fastboot showed up).

Once there, I unlocked bootloader successfully again to flash all stock files. Xoom booted up bravely afterwards, phew.
[Xoom Q&A, Help & Troubleshooting] Landorin:
Another good news. This time it also applied the 2nd OTA successfully finally! I don't know why it worked this time. Either it's because I (somehow badly) locked the bootloader and unlocked it again OR because I did the flashing this time from my laptop. On the previous attempts I had the Xoom connected via front USB on my desktop computer, maybe that wasn't a good idea after all (flashing on the laptop connection went even faster, too, about 20 sec the most for each file). In the past I used to flash from my laptop as well and never ran into issues either - should have sticked to it maybe. ;)

I guess I won't go for custom ROMs again anytime soon, I've really had it, especially not the one I used to use. :P Simply not worth the hassle, considering the Xoom wasn't even faster and didn't work with virtual phone providers anymore.
[Xoom Q&A, Help & Troubleshooting] XxLordxX:
Glad you made it :D

Congrats!!
[Motorola Droid 4] munchy09:
Hello,

I was wondering has anyone accomplished or tried to connect the d4 to a home network? If so how did you do it?

Thank you
[Motorola Droid 4] dbreezy187:
Wi-Fi... the same with most device's menu settings wifi scan connect
[Motorola Droid 4] munchy09:
Thanks debreezy I've done that but I'm wanting to be able to access my desktop/server and also be able to print from it if needed so as to have it fully integrated into my network.
[Motorola Droid 4] dbreezy187:
I apologize... just used to the not so bright questions... I will give it a try... I have a wireless printer and print using motoprint... I'll try to disable the wireless features on the printer and try a few things... again I apologize... there's always motocast for documents and what not on your pc
[Motorola Droid 4] munchy09:
It's ok I understand I'm pretty knowledgable in IT but get lost in alot of the jargon that is used on these boards so I try to keep my wording as simple as possible. I dont even know how to use the motocast and couldnt get my phone to connect with the motoprint feature. What did you do to get the motoprint to work?
[Motorola Droid 4] dbreezy187:
Menu >settings >printer settings >add printer>find printer or You may have to use print shares... I mainly print pics which I just tap pic tap down arrow then print which should bring you to the printer settings my printers choose your printer and good to go... when I do print a doc its with quick office after composition menu scroll over tap print icon which should bring you to the printer settings my printers choose your printer and good to go... as far as motocast I used it on gb and haven't used it since ics ota...
[AT&T, Rogers HTC One X, Telstra One XL] Deleted member 3452239:
Is this the beginning of the end?

If I press hard enough on my phone screen, the screen turns off until the pressure is released.. Any fix that won't cost me money.. Is my phone on the road to the trash can?

I'm actually pretty angry right now...

And it does this with maybe 1-2 pounds of pressure applied to the glass.. and it's never done this before -.-
[AT&T, Rogers HTC One X, Telstra One XL] exad:
Perhaps applying pressure is loosening the ribbon cable. Ive taken one apart and I find that ribbon cable disconnects rather easily. ofcourse taking the onex apart is a ***** as far as im concerned.
[AT&T, Rogers HTC One X, Telstra One XL] Deleted member 3452239:
Maybe the cable is loose, but I watched some video where the guy said if the cable isn't plugged in completely the display turns off.

Maybe the pressure is pulling it away until released? I just hope the screen isn't dying for good.

I'm not sending it in to get it repaired, because I can't live with doing "fastboot flash boot boot.img".. If I can fix it myself (for less than $30) I'll be happy.

I'd hate to have my phone die on my now, especially since I started devving :crying:
[AT&T, Rogers HTC One X, Telstra One XL] area51avenger:
Lol I'm sure if anyone knows how to downgrade its you

Sent from my VENOMized HoxL
[AT&T, Rogers HTC One X, Telstra One XL] exad:
Sounds to me like that would be whats happening.. I cant think of anything else that would cause the issue youre having. I wish you luck. If theres anything I can do to help, dont hesitate.
[AT&T, Rogers HTC One X, Telstra One XL] Deleted member 3452239:
I don't know.. some people say downgrading 2.14 firmware has bricked/been unsuccessful
[AT&T, Rogers HTC One X, Telstra One XL] Deleted member 3452239:
Don't mind any talking.. my friend was talking to me on skype.

Anyways, that would make sense, because I *think* the area where my thumb is, is where the ribbon for the screen is?

https://www.dropbox.com/s/9d49rmjn910l8oh/Video Feb 11, 7 43 34 PM.mov
[AT&T, Rogers HTC One X, Telstra One XL] ChongoDroid:
Get Nexus 4

Problem solved

#troll

Sent from my Nexus 4
[AT&T, Rogers HTC One X, Telstra One XL] exad:
The cable comes from the bottom and pops in on the opposite side of where you're pressing. :/
[AT&T, Rogers HTC One X, Telstra One XL] Deleted member 3452239:
So a loose cable is probably the culprit?
[AT&T, Rogers HTC One X, Telstra One XL] exad:
Try putting some pressure on the right edge of the screen.. theres 3 connections there.. 2 that clip in and one that slides in and fastens.. I can't remember which one provides power... hopefully not the one that slips in.
[AT&T, Rogers HTC One X, Telstra One XL] Deleted member 3452239:
the right side of the screen doesn't make it turn off. just near the bottom left, and i got scared because my screen didnt come back on after pressing there.. but it did after i turned off the screen *phew*

GREAT NOW MY SCREEN WONT COME BACK ON..

and its back on.. wow this is nerve wracking.. it better be a loose cable
[AT&T, Rogers HTC One X, Telstra One XL] exad:
Hmmm weird... if you're phone is unlocked, when the screen comes back on is it locked?
[AT&T, Rogers HTC One X, Telstra One XL] Deleted member 3452239:
no, stays unlocked
[AT&T, Rogers HTC One X, Telstra One XL] exad:
If its the cable.. I believe the one all the way to the right is power. The thick copper looking one. And it slides in.. I'm thinking it may not be cable related... maybe the LCD itself.... you can always try reseating the cable though.

Wait.. no that's exactly where the cable is.. my bad. I think its the cable

Sorry for my confusion. Almost positive the cable is loosening when you press it.

---------- Post added at 09:06 PM ---------- Previous post was at 09:03 PM ----------

http://db.tt/kheutTWC

That's the back of the phone where the cable plugs in so that's exactly where you're pressing.
[AT&T, Rogers HTC One X, Telstra One XL] Deleted member 3452239:
Well the screen will only stay on if the housing is removed.. works perfectly fine without it.. can press down as hard as I want and the screen works

FML
[AT&T, Rogers HTC One X, Telstra One XL] WhatTheAndroid?:
As far as i know, it is not a good thing,As with the Housing, the housing applies pressure to the phone..that's part of the reason my one x developed screen flex, on the right side...and it is issuing your problem as well. Or it is more likely the cable. Lucky i haven't had this problem yet :victory: . Hmm
[AT&T, Rogers HTC One X, Telstra One XL] Deleted member 3452239:
well my phone is trashed, and I already took it apart and unscrewed the screws that say "void".. at least I can get my files off

gonna lock it, RUU it, and throw it in the trash I guess. HTC won't repair it, AT&T can go out of business for all I care.. and I'm not paying $100+ to warranty it..

They aren't getting anymore money out of me
[AT&T, Rogers HTC One X, Telstra One XL] exad:
I have the housing from the one x I took apart. You're welcome to it if you want to try a different housing. Its white though dunno if yours is black. Youd just have the pay the shipping which should be pretty cheap.
[AT&T, Rogers HTC One X, Telstra One XL] 954wrecker:
I'm sure XDA members can help piece together a nice FrankenXone for you!