yashsingh1/xdaforums huggingface dataset:
[Desire Q&A, Help & Troubleshooting] JeanFlea:
Found this: Will this answer any questions?

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

P.S I live in South Africa
[Desire Q&A, Help & Troubleshooting] jmcclue:
not really coz it just says south africa. we need the carrier, o2, vodaphone etc etc. to be honest i dont think the ruu is the problem coz the 2.3 ruu updated ur radio and system, it prob would failed well before that if it was wrong ruu.
[Desire Q&A, Help & Troubleshooting] JeanFlea:
I was even thinking that and I don't even know how this stuff works.

So... am I screwed?
[Desire Q&A, Help & Troubleshooting] Chromium:
I guess so. The problem could be that the nand has some bad blocks.

My only suggestion at this point would to keep running the ruu hoping that it eventually completes successfully.
[Desire Q&A, Help & Troubleshooting] JeanFlea:
ok.. Well thank you for both of your help and time. Much appreciated
[Desire Q&A, Help & Troubleshooting] jmcclue:
go here

http://alpharev.nl/

and download the "bravo_downgrade.img" and put the .img file in ur fastboot folder on pc. Then put ur phone into fastboot, back button + power, then plug it into pc. Then open a fastboot command window and type

fastboot flash hboot bravo_downgrade.img

then once its finished, run the 2.3gb ruu straight away. Might work, dunno. Like chromium says there prob a bad block/corrupt bootloader r something stopping the flash. Anyway try what i said above.
[Desire Q&A, Help & Troubleshooting] JeanFlea:
Where would I find the fastboot folder?

With this, would it be possible to completely wipe everything, including corrupt bootloaders or whatever, and just re-install? Won't that work?
[Desire Q&A, Help & Troubleshooting] jmcclue:
u know when u setup adb & fastboot on ur pc, put it in that same folder. it doesnt need to be there, its just easier. u can just put it in ur c:\ drive on ur computer and type in the correct path like

fastboot flash hboot c:\bravo_downgrade.img

get what i mean?
[Desire Q&A, Help & Troubleshooting] JeanFlea:
Oooh, ok yes yes. That's what I thought and I did that but I stupidly didn't type the path fully. Ok I'll try this and let you know.
[Desire Q&A, Help & Troubleshooting] jmcclue:
the chances of the ruu working is slim but its worth a shot.
[Desire Q&A, Help & Troubleshooting] JeanFlea:
What does the downgrade do exactly?
[Desire Q&A, Help & Troubleshooting] jmcclue:
becouse ur s-off with hboot 6.9.1002, that file just unlocks the hboot so a ruu can overwrite it.
[Desire Q&A, Help & Troubleshooting] JeanFlea:
Ok, it just did the same thing, gave me an error. What if I try a different ruu?
[Desire Q&A, Help & Troubleshooting] jmcclue:
yh u can but ul need to find out if the phone was carrier locked so u can find the exact ruu
[Desire Q&A, Help & Troubleshooting] JeanFlea:
Dunno how to do that..

If I do, will it work?
[Desire Q&A, Help & Troubleshooting] jmcclue:
No idea if it will work, in theory the 2.3gb upgrade ruu should of worked
[Desire Q&A, Help & Troubleshooting] JeanFlea:
I appreciate all the help guys :) Thank you.
[Desire Q&A, Help & Troubleshooting] jmcclue:
Ok so i could not find anything bout ur cid HTC_016 so i had another look at the pic u posted of the fastboot getvar command and used the "version-main" number (2.10.405.2) then searched and i only found 1 ruu with that number (see pic) so i downloaded the ruu and opened the rom.zip then had a look at the android-info.txt file to see what device its compatible for and here is the list

As u can see, same main-version and cid soo i think this is the ruu for u :cyclops:

Now its totally up to u if u wana try it and theres no guarantee it will work but i think its the best option we have.

Heres a direct link to ruu download

RUU_Bravo_Froyo_HTC_WWE_2.10.405.2_R_Radio_32.44.00.32U_5.09.05.30_2_release_142828_signed.exe
[Desire Q&A, Help & Troubleshooting] JeanFlea:
Wow, thank you for going through that extra bit of effort for me. I will give it a try. Should I run the downgrade first? Like I did previously for the other ruu

EDIT: Ok, I did the downgrade and ran the ruu. It completed successfully, the phone vibrated and something clearly happened, it even made the start-up tone, the LED is on and the buttons light up. This definitely fixed something. BUT, the screen is black. Do you think the screen is disconnected or it's a software problem?
[Desire Q&A, Help & Troubleshooting] jmcclue:
:D ok we getting somewhere. So we now know that the phone is up and running so we dont need to worry bout that anymore.

So the only thing left is to take the phone apart and check the flex cable connecting the lcd to the motherboard and see if its lose. There videos on youtube on how to do it. Its very easy, i recently put new motherboard in mine. Search youtube for a vid. If u get stuck just say and il help
[Desire Q&A, Help & Troubleshooting] JeanFlea:
I tried searching for it last night and I battled. It only came up with videos about changing the LCD screen on different HTC phones. I just don't wanna **** something up
[Desire Q&A, Help & Troubleshooting] jmcclue:
U wont, its very easy, il post a good video later, im on my phone now. I can strip mine down in like 3 mins haha. If iv time il try take some pics and show u exactly what ur looking, my old desire is around somewhere in bits :)
[Desire Q&A, Help & Troubleshooting] jmcclue:
Have a look at this video, dont worry you only have to watch it up to 3 minutes. All you need to do is take off battery cover, take out battery, sdcard and sim, then take out the screws and disconnect the plastic and ul see the motherboard. Iv attached also a pic so you know what connections you need to check, make sure they all connected properly. When you take off the plastic you will see all the connections, just make sure they all connected (give em a push to be sure). Once you done that, just put the plastic back on and screws back in and battery, sdcard and sim and hopefully when you press power it will be good. If not then id say you need new LCD.

Just wondering, do you know if the previous owner changed the screen? coz he might of put the wrong one in. The desire either has an S-LCD or Amoled screen.

HTC Desire disassemble video
[Desire Q&A, Help & Troubleshooting] JeanFlea:
Everything is attached fine. I had a closer look, there is a crack on the LCD screen, so it's probably damaged. It costs a lot to get that fixed. At least the software problem is fixed, so whoever else decides to use the phone they can just replace the LCD and be able to use the phone :)

So thank you for everything.
[Desire Q&A, Help & Troubleshooting] jmcclue:
Ah balls. U could fix it urself, u can get cheap lcd off ebay, bout 20 euro i think.

U know once the plastic is off the phone, at the top left corner theres a wee screw, take that out then unclip the flex cables and the motherboard comes straight out then simply pop out the lcd. Up to u tho :)
[Desire Q&A, Help & Troubleshooting] JeanFlea:
Yea, I think I will do this when I have the cash :)

Is this the right one?

http://www.ebay.com/itm/GENUINE-HTC...K_Replacement_Parts_Tools&hash=item53fb0452d1
[Desire Q&A, Help & Troubleshooting] jmcclue:
Cant tell to be honest. It says its for desire bravo, which is right but whats the 6200 number all about? Funny thing is, i have a perfect lcd in my drawer haha, pitty u live the other side of the world :p
[Desire Q&A, Help & Troubleshooting] JeanFlea:
haha, you could post it if you're not using it :P

it'd probably be quite pricey to do that. I'm also confused about all the numbers and stuff, don't wanna buy the wrong one, especially since I can barely afford it. Also, shipping takes like a month.
[Samsung Galaxy W I8150] ArkBlitz:
For some strange reason, after reinstalling CM 10.2 several times already, the phone keeps having a peculiar problem. After entering recovery, wiping data, cache and Dalvik, and either restoring a backup or installing the ROM from scratch, the system will allow me to boot exactly once. Then, after rebooting, no matter what I did on the last boot, the phone will be stuck on the "Samsung Galaxy W" screen, without advancing to the spinning CM logo. The current workaround is to reinstall the ROM every single time I start the phone, and that's evidently not an option. Can someone suggest a stable solution?
[Samsung Galaxy W I8150] ArkBlitz:
A quick update - the phone seems to be not frozen, but bootlooping after about three minutes per loop.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] skippywilcox:
im looking for a app that can change everything to dpi setting 240, like pasettings.

im on quantum 4.4

let me know if there is anything

thanks,
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jimchee:
With rom manager pro you can easily change build props
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KorGuy123:
ROM Manager works well. If you want something idiot proof use Density Changer
[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] ChoctawT:
How do I go about getting Multi window on my phone. Currently running OctOs

Sent from my SPH-L720
[JAM, MDA Compact, S100 General] -OPTICAL-:
Hi,

I've tried to answer this question with the help of several sites, but nobody seems to be able to help me (or am I looking at the wrong place?)

When I send an SMS-message, I get a notification when the actual message has been sent. I would like to stop this service, but I can't find the option. I've checked the registry, but I'm not really good at that stuff...

Please help me out...
[JAM, MDA Compact, S100 General] rustoss:
You are like a king..... try to use search & open your -OPTICAL- eyes

http://xdaforums.com/viewtopic.php?t=38037

or

http://xdaforums.com/viewtopic.php?p=194388

or Easytweak program
[JAM, MDA Compact, S100 General] -OPTICAL-:
Thank you for your help, and offcourse, your over-simplified comments. :wink:
[Glass General] jazzman97:
Edit #2: Mods please delete, I have returned them to Google. Thank you :)
[Glass General] Stretchttu:
Why did you return it? Did you have to pay restock fee?
[Glass General] jazzman97:
Returned for financial reasons and no restock fee
[One (M7) Q&A, Help & Troubleshooting] FearlessPixel:
Only one other person has posted about this, last year, and it went nowhere but I wanted to see if we could make the capacitive buttons flash with the beat of music. I just think it would be cool to try and get working, has anyone looked into it?
[Xperia SP Q&A, Help & Troubleshooting] Basilios-28:
Hey,

so i have a 16 g sd card next to the internal storage 5.5 g and it's working fine with me .. But .. After installing fifa 14 and nfs most wanted i got low on internal storage .. And the games won't work unless the data files are in the internal storage .. I tried moving the data files with different managers ( es .. File commander ) and the games just won't work unless the data is in internal storage !! .. Weird thing in my friend's stock 4.1.2 in xperia tx .. There is ( transfer to sd ) button in app settings but in 4.1.2 stock in xperia SP there is no such thing !! ..

..

Btw :i'm on stock and i don't prefer to root my device not with stock 4.3 and 4.4 are on the way

---

second thing .. So the google play is just not working .. Always no connection and giving me the retry button .. I tried uninstalling and many things but just won't work it's crazy !!
[Xperia SP Q&A, Help & Troubleshooting] zolaisugly:
Without root you won't be able to move any gave data or have dikes to SD card.

The xsp only see internal external is for media files like videos or music.

If you root you can use apps foldermount to move all gave data and game obb files to ext SD card and it will run without issue.
[General Questions and Answers] Mister-v:
oo
[General Questions and Answers] Mister-v:
BUMP Please help me BUMP
[General Questions and Answers] MilanRR:
Stock ROM for BLU Dash 4.5

There is facebook group with few links, so you could download and try to restore stock ROM for BLU Dash 4.5.

I hope this will help you.
[Galaxy S II HD LTE Android Development] Phil3759:
Main thread + features + install instructions + dev support

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

PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM

It is a well proven recovery for many phones

It also adds a full touch interface a completely configurable GUI

Please give your feedback, what works, and any bug you could encounter

Read the features, and check if you are missing something

Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut

Download links

Last version can be found here:

Huge thanks and credits to [MENTION=4859152]titanic_fanatic[/MENTION]

He ported the sources and provided all needed stuff to build it
[Galaxy S II HD LTE Android Development] titanic_fanatic:
Excellent, many thanks for all the work you put into this for us. We very much appreciate it ;)

On the topic of bugs, I only have two (but I really don't mind at all). The screenshot works except for the resulting image is wavy coloured lines and no vibration regardless of the setting.

We've never had either, so I'm not missing them at all, but wanted to let you know.

Take care Phil :)
[Galaxy S II HD LTE Android Development] Phil3759:
Added you to credits on the device page in main thread and here in OP :good:

screen shots: forget it, I should disable it once for all on new devices. Sadly, we have no working thing for most new devices. Only some Sammy and the mako did work

vibration: can you provide the path for vibrator?, it should be in kernel drivers I guess. Currently I use:

/sys/class/timed_output/vibrator/enable

We echo some msec value there and it Bzzzzz for that msec
[Galaxy S II HD LTE Android Development] titanic_fanatic:
That's the correct path :) Maybe the driver isn't loading properly... I'll see if I can get a dmesg Log when booting recovery to see if the driver actually loads ;)
[Galaxy S II HD LTE Android Development] titanic_fanatic:
Vibrator Fixed

Hey [MENTION=4666971]Phil3759[/MENTION], I did a whole lot of investigating tonight and have figured out and fixed the vibration issue. I discovered that it was trying to load the module from /system/lib/modules/vibrator.ko. This is my roms ko file and is currently for cm10.2. The kerenel I setup for this recovery is our cm11 kernel and uses a different module (compiled against that kernel). It was trying to load the cm10.2 module from my rom into the cm11 kernel which obviously doesn't work, so I split the recovery.img added the correct module at /tmp/system/lib/modules added the necessary lines to init.recovery.qcom.rc and repackaged the kernel and new ramdisk.

I have flashed this and tested it. it works like a charm now ;) Can you replace the version in your repo with this new one?
[Galaxy S II HD LTE Android Development] Phil3759:
If you update your device tree, it would be even better. That way, my next updates won't be affected again
[Galaxy S II HD LTE Android Development] titanic_fanatic:
I just finished updating my device tree with the necessary fixes for the vibrator to work in recovery ;)

https://github.com/titanic-fanatic/android_device_samsung_celoxhd/commit/6f005f4045551e48adfa0ac228641bf8d6a12128

Also, not that I care, but Amarullz was able to get screenshots working in the latest AromaInstaller (Flamboyan I think). If your interested, maybe ask him what he did to get it to work. He could probably point you to the commits ;)

Take Care :)
[Galaxy S II HD LTE Android Development] Phil3759:
Looking at it quickly: why that first extra / at end of copy files?

Also, won't be cleaner to use standard path like /lib/modules?

/tmp can be wiped and modified by installers and recovery
[Galaxy S II HD LTE Android Development] titanic_fanatic:
The first / is because it's part of a set of chained product copy files directives:

I did this only to adhere to the existing pattern in my device.mk file, the one appended to the first PRODUCT_COPY_FILES was already there from when I forked the project and took that as being a set of chained commands. If this is wrong, I will change it ;)

I definitely see your point on the /tmp dir. I here the commit that fixes that ;)

https://github.com/titanic-fanatic/android_device_samsung_celoxhd/commit/61da6be2d60a03797ddc31c0187cc5c62bb3a97a
[Galaxy S II HD LTE Android Development] Phil3759:
I uploaded 6.01.2 with your fixed vibrator :good:

PRODUCT_COPY_FILES:

Maybe I am wrong, but usually, in make files, only the last element has no trailing /

# Ramdisk
PRODUCT_COPY_FILES += \
device/samsung/celoxhd/ramdisk/init.qcom.usb.rc:root/init.qcom.usb.rc
xxx-yyy \
zzz-pppp\
last_one

# BT firmware
PRODUCT_COPY_FILES += \
device/samsung/celoxhd/firmware/bcm4330B1.hcd:system/etc/firmware/bcm4330B1.hcd

# Needed for vibrator to work in recovery
PRODUCT_COPY_FILES += \
device/samsung/celoxhd/recovery/root/tmp/system/lib/modules/vibrator.ko:recovery/root/tmp/system/lib/modules/vibrator.ko \
device/samsung/celoxhd/recovery/root/init.recovery.qcom.rc:recovery/root/init.recovery.qcom.rc

Also, just for info, my full gui builds need these, often in cm.mk:

TARGET_SCREEN_HEIGHT := 1280
TARGET_SCREEN_WIDTH := 720
[Galaxy S II HD LTE Android Development] titanic_fanatic:
It seems that the extra \ was introduced in our JB branch and has never been fixed. Various examples in googles repo confirm that you are correct. I have removed the extra \ and added the properties you mentioned above to the cm.mk file. Here is the relevant commit:

https://github.com/titanic-fanatic/android_device_samsung_celoxhd/commit/6ce5f482d63cd70cf64a3d1428ad2428844e23cb
[Galaxy S II HD LTE Android Development] titanic_fanatic:
Hey [MENTION=4666971]Phil3759[/MENTION], I just downloaded and flashed the latest version. Thanks kindly for the update ;)

I see that I made a boo boo and forgot to update the path to the vibrator in the init.recovery.qcom.rc file and so the vibrator isn't loading. I've fixed that with the following commit:

https://github.com/titanic-fanatic/android_device_samsung_celoxhd/commit/b87b3267d75a0de1bb94f68850ae6986ac4dde92

One other thing, for some reason the background is tiled 4 times as if my devices dimensions were not set correctly. I do have that set in my cm.mk file. Here was the commit for that:

https://github.com/titanic-fanatic/android_device_samsung_celoxhd/commit/6ce5f482d63cd70cf64a3d1428ad2428844e23cb

Is there somewhere else I'm supposed to specify the device screen dimensions?

Thanks again for the new version and I apologize for missing that path in the init.recovery.qcom.rc.
[Galaxy S II HD LTE Android Development] Phil3759:
About background image:

I think this is the cause:

https://github.com/CyanogenMod/android_device_samsung_celox-common/blob/cm-11.0/celox-common.mk#L45

called here:

https://github.com/titanic-fanatic/...xhd/blob/philz-recovery-cm-11.0/device.mk#L37

Your cm.mk settings are overridden

Maybe just move device resolution from cm.mk to device.mk after Line 37

About the vibrator: do you need exfat through kernel modules? If yes, let me know. It is much faster than fuse. For that, you'll need to compile the kernel with samsung exfat sources. I can guide you for that

Else, link me to what exactly is needed in your kernel for the vibrator to work. If it is just a change in defconfig, I can add it and compile along exfat
[Galaxy S II HD LTE Android Development] titanic_fanatic:
I see it, and now as you've recommended I reset the values after calling celox-common.mk. The commit is here:

https://github.com/titanic-fanatic/android_device_samsung_celoxhd/commit/cd44b44b7cbb0ddb3b649ac5c4f8d5d1f51d7998

As for exfat, I will be adding this when I have some time to rebuild this kernel. We can worry about exfat for the next time you do device updates and hopefully I'll have it ready by that time. I have your main thread in my subscriptions, so I'll know when your ready to release a new version and will remind you to sync with my repo at that time ;)

Thanks for catching that issue with screen size ;)
[Galaxy S II HD LTE Android Development] Phil3759:
np

Let me know if you need info to add exfat

I will update with the current fixes asap
[Galaxy S II HD LTE Android Development] titanic_fanatic:
Can I get a link to these fixes please when you have it ready ;)
[Galaxy S II HD LTE Android Development] Phil3759:
https://github.com/PhilZ-cwm6/GE-Ed...mmit/a8963ca853cfd88466716f8a25434d5c469a2bb9

It is just adding the exfat folder in drivers and edit the makefile with -y to have it built as static. No need to separate modules
[Galaxy S II HD LTE Android Development] titanic_fanatic:
Excellent. I'll add it soon, it should be a pretty quick process.

Quick question though since we are currently having some issues with random reboots in all of my latest builds of cm-11.0. My kernel was updated at some point, and that's when my builds started having random reboots. They are actually not random, but seem rather consistent.

My question is this, do you think this will affect operation in recovery? I believe the reboots are due to kernel panic from a graphics related issue but am not sure if that will only affect the rom and not recovery.

If this might affect recovery, I think I'll build it as a module so I can just add it to my device tree instead of having to update the entire zImage. This will at least give us the old working kernel with the exfat module included.

What do you think?
[Galaxy S II HD LTE Android Development] Phil3759:
you'll end up with magic number mismatch errors

There are some hacks to force loading on mismatch, but, in my previous experience, they failed on many devices

the drivers must be compiled along the zImage

Now, why don't we drop to celox-common kernel which seems to work fine on skyrocket and other phones?
[Galaxy S II HD LTE Android Development] titanic_fanatic:
It is for the most part the same kernel with the few quirks of my device. More notably is my devices display drivers are mipi s6e8aa0_720hd and had to fork the kernel to apply some fixes to that driver as it's not maintained by cm.

Hmmm. I'll be the guinea pig. I will build with the new kernel and I'll test the recovery before you upload. I just think that the issue might be a memory leak in android causing the kernel to panic (overlay issue) and might not have an effect in recovery since its graphics are very basic.

I'll let you know when it's ready ;)
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] DUBS73P:
What sort of battery life are you all seeing with this years note? come from the ipad 3 where i usually saw 10-11 hours screen time and 2-3d standby, today is the first time ive had it from 100% and i only lasted 6 hours screentime with 7 hours overall on time, i still havent run it down completely yet but surely i should be getting more than this?

Its such a shame because i love it so much, but i cant deal with this short battery life
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] reubenskelly1992:
It's much better than that. I found it better after a couple of charges. I rooted mine and deleted or froze b.oatware and I get 13 hours heavy use:)
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] Houndx:
I came from an ipad 3 as well and had the same problem until I disabled several apps, turned off GPS, etc and over the long weekend I was getting ~12 hours of web surfing.

I haven't rooted yet so that should be a number that can improve. I'm sorta trying to wait for a root that doesn't trip knox. I don't want a custom rom so no reason to install a bootloader and lose my warranty if I can be patient. Tried Cydia Impactor but I had already upgraded to MK1. I'm wondering if the shipping rom (P600XXUAMIE) might have the 4.3 vulnerabilities unpatched.
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] DUBS73P:
What apps did you disable and how Exactly? Thanks alot
[Galaxy Note 10.1 (2014 Edition) Q&A, Help & Troubl] benni_1994:
I've freezed all unnecessary apps and i am getting like 9 - 10 hours screen on time with 8 hours standby. Standby is great for me :) nearly no battery drain.