yashsingh1/xdaforums huggingface dataset:
[8525, TyTN, MDA Vario II, JasJam General] MikeChannon:
Before assuming something physical I would double check everything else. The obvious -settings that turn on/off vibrate, any phone related software I might have installed. Then I would try a hard reset and test the vibrate funtion without any new software installed. (make a backup first though - if it turns out to be a hardware issue you can restore this backup)

If it looks like the motor contacts then it's a pretty simple fix. Remove back and adjust the motors spring contacts.

Just remember to align the camera macro's toggle arm when putting case back on

Mike
[8525, TyTN, MDA Vario II, JasJam General] ironbear:
Well...

The hard reset has done nothing for me. I can't believe that the 8525 is so touchy that without even a fall the vibrate thing won't work now.

That is poor manufacturing. This is my second 8525, the first one had screen issues. Very disappointing, almost makes me want to look at treo's.
[8525, TyTN, MDA Vario II, JasJam General] MikeChannon:
Well, it's certainly looking more like the contacts. Not a difficult fix if your doing it yourself. Still, a hassle all the same:(

Mike
[8525, TyTN, MDA Vario II, JasJam General] ironbear:
I recall seeing a very good picture of the contacts and the back of the phone taken apart. My search has come up without me finding those pictures again. Has anyone seen the pictures I am referring to?
[8525, TyTN, MDA Vario II, JasJam General] MikeChannon:
Here you go. Remove the 4 screws including one under Void (warranty) sticker and open back, bottom end first. Gently prise open. Top end may need a bit of wiggling about to come free.. That's more or less it - bend out contacts a bit. Remember to line up toggle arm on camera with macro switch on rear cover when replacing back. Test camera macro switch is moving lens in and out before replacing screws. It'll be a right pain if you put it all back just to find you have to redo it all cos camera switch is misaligned!

Mike
[8525, TyTN, MDA Vario II, JasJam General] ironbear:
Thanks Mike!

You are a great resource here at XDA.
[8525, TyTN, MDA Vario II, JasJam General] jbartlett777:
My 8525 stopped vibrating when I received a txt message. Since other things were getting screwy, I went ahead and did a hard reset. Fixed.
[8525, TyTN, MDA Vario II, JasJam General] MikeChannon:
Good news it's fixed. Always sensible to try the software solutions before assuming a hardware issue.

Mike
[8525, TyTN, MDA Vario II, JasJam General] zerofractal:
Same problem on my trinity. When i tap it it works once or twice.. I guess I must look for those springs. Is there any photo of the insides of the trinity so that I don't screw things up?
[8525, TyTN, MDA Vario II, JasJam General] jayp99:
No sound in my Hermes after flashing PDAVIET ROM

I know this sounds like a software issue but I have flashed and reflashed several times but to no avail.

I have a Hermes 300 with HardSPL. I flashed the latest PDAVIET ROM after which my sound stopped working. I also flashed Radio 1.56.70.11 (upgraded from 1.51) and installed Throttle Launcher and TouchFlo at the same time so I am not sure which of them may have caused this. I read somewhere that radio could be the cause so i downgraded to 1.47.30.10 but no luck. I flashed PDACorner ver 16, then ver 15, and finaly the original Dopod ROM (838Pro_HK_ENG_WM6_Upgrade_20070712). The funny thing is, after flashing the Dopod ROM, now my vibration doesnt work! Even after I flashed PDACorner ver 15 back, both sound and vibration dont work still.

I installed Schaps Avanced Config tool to check settings but it wont run - errors out "it is not signed with a trustedcertificate or one of its componenets cannot be found.."

Does anyone have any clue about this problem? This is beginning to worry me as i am not sure whether it is a hardware or software issue. BTW, sound from earphones work.
[8525, TyTN, MDA Vario II, JasJam General] jayp99:
Funny thing.. after I flashed the PDAVIET ROM the vibration is back again. No sound however. Do you still think its a hardware problem? i will have to go get a torque screwdriver to open it up ...

Yeah it took a mild knock a couple of days back but im not sure if that what caused it
[8525, TyTN, MDA Vario II, JasJam General] MikeChannon:
Well it's not an uncommon thing for that connector to work loose. Oh and the vibrate contacts can come and go as well. So if it suddenly stops vibrating again you could be pretty sure it's the contacts.

Torx 6 screwdriver and preferably a plastic case opening tool Though any flat plastic tool would do even a plastic knife - metal damages the casing.

I am assuming you have no warranty as opening will obviously void it.

Mike
[8525, TyTN, MDA Vario II, JasJam General] jayp99:
its out of warranty so no worries there. Havent opened it up yet due to lack of the torx screwdriver :(

It now hangs on the bootscreen ....
[8525, TyTN, MDA Vario II, JasJam General] jayp99:
Hi Mike, it looks like something else may have come loose. Reflashing works for a while, then the whole thing resets by itself (randomly) and hangs at the bootscreen. What else should I check when I open it up? Thanks for all your help.
[8525, TyTN, MDA Vario II, JasJam General] MikeChannon:
Well it could be the main internal connector one board to the other. However, I'm more inclined to think the random closing is the old battery connectors not making a good contact with the battery. In the best cases all you need is a slip of card between the casing and the battery on the opposite side to the connector. In other words to push the battery a little more firmly against the connector block - hope that's clear.

In worse cases the battery connector block with the row of gold contacts has actually come free or partially free from the board - may be re-solderable.

With a slip of card in place do repeated soft resets until it re-boots fully.

Good luck

Mike
[8525, TyTN, MDA Vario II, JasJam General] jayp99:
hey mike, where does the stylus rubber go in the hermes? do you have a pic or something? thanks for your help. cheers.
[8525, TyTN, MDA Vario II, JasJam General] jayp99:
finally, sound working...connector was loose just as you had predicted. vibration also fine. also managed to fix that pesky rubber under the metal plate :)

Only the keyboard seems a little stiff when I slide it...

Thanks a bunch for your help. Those guides you have are real handy.
[8525, TyTN, MDA Vario II, JasJam General] MikeChannon:
Well forgot to check in here to see how it was going! Pleased it worked out.

Just for the information of others here are some pics to help with the loose stylus caused by the rubber block coming loose:

Back casing removed, stylus in place

Stylus removed. Note the white clip that holds the end of the stylus.

NOTE: This picture also shows the vibrate motor on the back casing. (Bottom right with the two gold contacts). To improve the contact between vibrate motor and m/board, simply bend those springy contacts out a little.
[8525, TyTN, MDA Vario II, JasJam General] MikeChannon:
The block is important because although the white clip helps retain the stylus it will remain loose and wobbly without the rubber/plastic block in place. When re-sticking the block use some superglue but be careful NOT to get glue on the face of the block that is not be stuck to the metal. If you do it will have a smooth surface and will not friction grip the stylus as it is meant to. Also do not assume that the previous sticky layer on the block will be enough to re-stick the block! It won't and it will come off again when you slide the stylus in and out.

Mike
[8525, TyTN, MDA Vario II, JasJam General] RikShaw:
Vibrate Question

I have a vibrate question, not a problem. It seems that the vibrator is either on or off. Most cell phones that I have used, the vibrator will pulse when a call comes in. I find that this gets my attention better than a steady vibrate. When I'm riding my motorcycle the steady vibrate blends in with the vibration of the motorcycle and gets lost. I think a pulsed vibrate would work better.

The question. Is there any software application that provides a pulsed vibrate for the ring?

Running PDACorner V11 (works great).
[8525, TyTN, MDA Vario II, JasJam General] MikeChannon:
Well YOU can be the software application!! (I'm sure there is software around but this could be fun:D)

Arm yourself with a registry editor such as PHM reg edit (freeware) and go to:

HKCU\ControlPanel\Sounds\RingTone0\Script.

Change ringtone/vibrate/LED flash characteristics

If you would like more control over how your device rings/vibrates/flashes its LEDs on events, you can can change the Script values of these events. For example, for an incoming call performing 'activate device, play ringtone, wait 3 seconds, repeat':

HKCU\ControlPanel\Sounds\RingTone0\Script = "apw3r" (REG_SZ string, no quotes) (This is often the default setting)

For performing 'active device, set volume to 33%, play ringtone, set volume to 67%, play ringtone, set volume to 100%, play ringtone (no repeat)':

HKCU\ControlPanel\Sounds\RingTone0\Script = "ac33pc67pc100p" (REG_SZ string, no quotes)

The following are the full codes available to you. Please note that all the codes are executed simultaneously except after a ringtone play / wait code. E.g. 'v1p' will vibrate and play at the same time, while vibrating for 1 second. But 'pv1' will play the ringtone through all the way first, then start vibrating for 1 second.

a = activate device

cN = set volume to N in percentage max volume

fN = flash notification LED for N seconds

p = play ringtone. Note that this will play the ringtone all the way through before continuing with the next code.

r = repeat. Note that this should be the last code in your Script string, if used at all.

vN = vibrate for N seconds

v0 will vibrate continuously;

v3 will vibrate for 3 seconds;

v3p will vibrate for 3 seconds, then play the ringtone;

v0p will vibrate and play the ringtone at the same time, and when the ringtone stops, the vibrating stops as well;

v0p3 will vibrate and play the ringtone at the same time, and stop after 3 second
​

wN = wait for N seconds. Note that the device will wait this long before continuing with the next code.

Some more examples

Display - a

Flash - af1w60f0

Ring - apw3r

Ring Once - ap

Increasing Ring - c50apw3c150r

Vibrate Then Ring - v3w3apw3r

Vibrate - av3w3r

Short Vibrate - av1w3r

Vibrate Long Then Ring - v3w3v3w3apw3r

Vibrate And Ring - av0pw3r

Increasing Ring And Vibrate - c50apv3w3c150r

Fast Vibrate And Flash - af1v1w1f0r

There are several notification sound settings in the registry – examples:

[HKEY_CURRENT_USER\ControlPanel\Sounds\RoamingRing0]

"Script"="apw3r"

[HKEY_CURRENT_USER\ControlPanel\Sounds\KnownCallerR ing0]

"Script"="apw3r"

[HKEY_CURRENT_USER\ControlPanel\Sounds\RingTone0]

"Sound"="\\Storage Card\\My Documents\\Trout.wma"

"Script"="av0pw3r"

Now don't say I'm not good to you

Mike
[8525, TyTN, MDA Vario II, JasJam General] RikShaw:
Thanks Mike

Thanks Mike. Your too good to me. ;)

Its kind of what I was looking for. There still doesn't seem to be a way to have it pulse while the music is playing. I used 'v1w1v1w1av0pr' which works after a fashion. I'll play with it a bit and see what else I can get.

Thanks again
[8525, TyTN, MDA Vario II, JasJam General] hdomingu:
Stops vibrating

My 8525 stops vibrating and there is no in call sounds at times. Then it magically starts vibrating again and the sound comes back. Is this a hardware problem or a software problem?? thanks ahead of time
[8525, TyTN, MDA Vario II, JasJam General] MikeChannon:
Well, randomly stopping vibrating is a sign that the contacts on the vibrate motor are needing tweaked out a little.

However, the fact that you also lose in call sound makes the problem more difficult to analyse.

So, initially I'd back everything up and do a hard reset.

Before restoring the backup, thoroughly test the vibrate and in call sound. If all is good then it was a software glitch and this will be confirmed if the problems recur after you restore the backup.

If problems continue, you can either have it repaired or dismantle it yourself. (Voids Warranty obviously). Both the vibrate motor and the in call front speaker have springy contacts that may simply need benmt out a fraction.

Mike
[8525, TyTN, MDA Vario II, JasJam General] RikShaw:
Very Funny

Mike,

How do they say it? There's a clown in every group. Nice graphic, I got a kick out of it.:D

Thanks again for your help.

Rick
[8525, TyTN, MDA Vario II, JasJam General] michaelmark:
vibrating sometimes!?!?!?

Hey,

i'm having a similar problem where my phone stopped vibrating, i was going to go look for the required screwdriver to open it up when voila it started vibrating again, but since then it has stopped and started vibrating and i have no idea what to do now. is the motor dying or should i try and open it up and do the fix that y'all recommended?

haven't dropped it or upgraded software in a while so i'm a bit puzzled.

help?

Thanks
[8525, TyTN, MDA Vario II, JasJam General] MikeChannon:
Hmmm. I show a picture above of the vibrate motor and it's contacts!

No it's not dying. Look at post 21 above. The last pic there shows the vibrate motor and it's two gold contacts. These spring contacts can lose a bit of their springiness and then randomly lose contact with the board. All you need do is tweak them out a little. The vibrate motor is on the back casing so only a little dismantling needed. When you re-assemble, remember to line up the camera macro switch and check it's working before putting the four screws back in.

Mike
[8525, TyTN, MDA Vario II, JasJam General] mrpiggae:
This vibrating thing is odd...I dropped my phone onto my hardwood floors a couple of weeks ago, and it stopped vibrating completely. Two days ago it just started working again perfectly.

Strange...I was trying to work myself up to crack open the case and then it starts working again.
[8525, TyTN, MDA Vario II, JasJam General] MikeChannon:
Yes, a knock can push it out of place a little but equally another knock can push it back into place again. Once it starts though, it tends to get a bit erratic. Simple fix bend those springy contacts out a little.

Mike
[8525, TyTN, MDA Vario II, JasJam General] michaelmark:
Thanks! i'm gonna try and grab the screwdriver and give it a try this weekend,
[G 2014 Q&A, Help & Troubleshooting] EJSMiranda:
[Q] Creating Backup: motoboot.img & gpt.bin from another Firmware? Nextel Mex XT1064

Hi everyone! I need your help! I'm dumping the Firmware of my XT1064 Nextel México to share it with everyone in the community. I dumped almost all the partitions of my device, excluding "motoboot" (In another firmwares Dumps is motoboot.img) which I can not find it, and the "system" partition, which I can not flash it in the device because the file (system.img) is too big and I don't know how to divide it. Finally, I want to know if I can use the motoboot.bin and the gpt.bin from another firmware like the XT1064 Retail from USA.

Sorry for my bad english! I hope someone can help me! :D :D :D

Here I put the files I've already uploaded! USE AT YOUR OWN RISK!

https://mega.co.nz/#F!VMQHFJxB!7aSAkqkYI1SX7GI_S5yItw

USE AT YOUR OWN RISK! YOU MUST HAVE UNLOCKED BOOTLOADER

How-to:

-Copy all the files from the IMG's And BIN folder and the TWRP Recovery "twrp-2.8.3.0-titan.img" to your "platform-tools" folder

-Copy the TWRP Backup to your SD Card Backup's folder

Enter to fastboot in your device and run this commands in order (I exclude "fastboot flash partition gpt.bin" and

"fastboot flash motoboot motoboot.img")

fastboot flash logo logo.bin <--- From Retail US Firmware

fastboot flash boot boot.img <--- From XT1064 Nextel México

fastboot flash recovery twrp-2.8.3.0-titan.img <--- Flash TWRP Recovery include in the Link

-Enter to TWRP Recovery using your device, Wipe System/Data/Cache and Restore the System Partition from the Backup.

-Power Off the Device and enter to Fastboot again.

fastboot flash recovery recovery.img <--- Original Recovery from Retail US Firmware

fastboot flash modem NON-HLOS.bin <--- Modem from XT1064 Nextel México

fastboot erase modemst1

fastboot erase modemst2

fastboot flash fsg fsg.mbn <--- From XT1064 Nextel México

fastboot erase cache

fastboot erase userdata
[G 2014 Q&A, Help & Troubleshooting] reefuge:
Ok Lets just say this clearly 'STOP NOW' CALM DOWN AND LEARN A BIT MORE...... flashing images can and will brick your phone.

'I've dumped all most all the partitions of my device' -- Not really you have made TWPR backup of your Android Partitions (there are many more hidden partitions) some common android partitions are /boot /cache /data /system /recovery. these are the ones normally backed up with TWRP etc. A basic TWRP flashable custom rom can be made of as little as (boot.img, system folder and a META-INFO folder ) zipped up

You are mixing and matching 2 separate Flashing Methods - yes it can be done, but it can Also go badly wrong.

motoboot.img is your bootloader IT IS NOT the same as boot.img

forget flashing anything with fastboot or mfastboot untill you learn more. stick to TWRP backups (full all partitions for you. and just boot and system to share)

you can only upgrade (at moment) your gpt.bin and motoboot.img - so just leave them as they are.
[G 2014 Q&A, Help & Troubleshooting] EJSMiranda:
Yes, I learned a lot in another devices, I'm just Asking if I can use motoboot.img (Bootloader) and the gpt.bin of another variant of my phone... I made a Backup of all the partitions included in the Factory Firmware Images of another Variants (In specific, the Xt1064 from USA and the one of Canada. and the Xt1063 Retail... I don't know if you have checked all the files that I upload, but all dumps that I did are from the ADB method, it's universal, works with every device... I tested all the dumps (fsg.mbn, boot.img, logo.bin, NON-HLOS.bin, recovery.img) in my device and it worked, except the system.img dump, because is too big, And I had the idea of adding the step of the Custom Recovery just to flash System... and then, continue with all the remaining partitions...
[G 2014 Q&A, Help & Troubleshooting] reefuge:
It's hard to say but motoboot.img and gpt.bin it's normally a one way upgrade only, if you flash newest, it can be hard to go back. Yes the should flash but you wont gain much and may lose OTA updates in future.

So there is no need to flash these for restoring TWRP back ups, I strongly suggest you leave yours alone.

ADB flashing really is just for OTA upgrades and using to get a custom recovery on phone, once you have a custom recovery you can make custom roms to flash from that.

Adb flashes system from OTA as 4 parts that combine into /system folder - so thats why you cant flash 1 big img via adb

again you need to learn how to make a flashable custom rom to use via TWRP, look for a guide there are many.

but i will give you a idea how to do

using your xt1064 mexcio TWRP back up - ALL you need for now is Boot.emmc.win and system.ext4.win nothing else

rename boot.emmc.win to boot.img and change system.ext4.win to system.ext4.tar and find a guide on how to extract the tar to a system folder ( I use cygwin )

then take a meta-info folder from a custom xt1064 rom and adjust the updater-script to work with your rom - zip these 3 files up into your new custom rom.

this is a very simple idea, there are more steps so search for a guide on here
[G 2014 Q&A, Help & Troubleshooting] iamDeeh:
I just need the motoboot.img file, would provide for me?
[Android General] thorstenhirsch:
Hi, I want to build a minimal ROM for my LG P990. It will be used as a remote control only, so I don't need telephony and bluetooth.

Here's what my local_manifest.xml looks like so far:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>

<remote name="aosp"
fetch="https://android.googlesource.com"
review="android-review.googlesource.com" />

<remote name="github"
fetch=".."
review="review.cyanogenmod.org" />

<remote name="private"
fetch="ssh://git@github.com" />

<default revision="refs/heads/cm-10.2"
remote="github"
sync-c="true"
sync-j="4" />

<remove-project name="CyanogenMod/android_external_Focal" /> -->
<remove-project name="CyanogenMod/android_external_stressapptest" />
<remove-project name="CyanogenMod/android_external_svox" />
<remove-project name="CyanogenMod/android_external_tagsoup" />
<remove-project name="CyanogenMod/android_frameworks_opt_telephony" />
<remove-project name="CyanogenMod/android_packages_apps_Apollo" />
<remove-project name="CyanogenMod/android_packages_apps_CellBroadcastReceiver" />
<remove-project name="CyanogenMod/android_packages_apps_CMUpdater" />
<remove-project name="CyanogenMod/android_packages_apps_Focal" />
<remove-project name="CyanogenMod/android_packages_apps_Mms" />
<remove-project name="CyanogenMod/android_packages_apps_VoiceDialer" />
<remove-project name="CyanogenMod/android_packages_apps_VoicePlus" />
<remove-project name="CyanogenMod/android_packages_providers_TelephonyProvider" />
<remove-project name="CyanogenMod/android_packages_wallpapers_Galaxy4" />
<remove-project name="CyanogenMod/android_packages_wallpapers_HoloSpiral" />
<remove-project name="CyanogenMod/android_packages_wallpapers_LivePicker" />
<remove-project name="CyanogenMod/android_packages_wallpapers_MagicSmoke" />
<remove-project name="CyanogenMod/android_packages_wallpapers_MusicVisualization" />
<remove-project name="CyanogenMod/android_packages_wallpapers_NoiseField" />
<remove-project name="CyanogenMod/android_packages_wallpapers_PhaseBeam" />
<remove-project name="CyanogenMod/android_frameworks_opt_mms" />
</manifest>

However when compiling I get the following error:

make: *** No rule to make target `.../work-p990/out/target/common/obj/JAVA_LIBRARIES/telephony-common_intermediates/classes.jar', needed by `.../work-p990/out/target/common/obj/JAVA_LIBRARIES/mms-common_intermediates/classes-full-debug.jar'. Stop.
make: *** Waiting for unfinished jobs....

1.) What project does the target "mms-common_intermediates/classes-full-debug.jar" belong to? There's only 1 project with "mms" in its name and that's "CyanogenMod/android_frameworks_opt_mms", which I have already added to local_manifest.xml.

2.) How can I find out more about the dependencies between the projects? What's safe to remove?
[Galaxy Note 10.1 Accessories] mangurian:
wanted to buy......... note 10.1 (2012) s pen tips or tip kit for my N8013

Let me know if you want to sell some. (maybe you do not use the s pen much or you've trashed your note 10.1)

Samsung does not sell the pen or tips.

I bought a Chinese replacement pen and it sucks.

(The pen tip pushes up into the housing when used.﻿)
[Galaxy Note 10.1 Accessories] erica_renee:
the pen is for sale ll over amazon
[Galaxy Note 10.1 Accessories] d4rkkn16ht:
S-Pen tip = Wacom Stylus tip

There are plenty store that sell Wacom Stylus Tip & it consists of several type (rubberized, plastic, etc...)
[Galaxy Note 10.1 Accessories] erica_renee:
http://www.ebay.com/itm/121256143945?_trksid=p2059210.m2749.l2649&ssPageName=STRK:MEBIDX:IT
[Galaxy Note 10.1 Accessories] jimyv:
http://www.ebay.com/itm/Replacement...131003132420&rk=3&rkt=6&sd=121256143945&rt=nc
[General Topics] joerolando2701:
Anyone know how get to the portal/blog in the crappy tapatalk update? Ever since the update i haven't been able to find i t
[Verizon Samsung Galaxy S III] Orion116:
I have an old d2usc that is rooted and is running LiquidSmooth milestone 3.2. My question is can I run d2vzw Lollipop Roms on my phone? I am getting mixed answers on this. I do know the d2vzw has a locked boot loader so I think I already know what the answer to my question but I figured I would ask anyway.
[Verizon Samsung Galaxy S III] ShapesBlue:
No. Do not run any rom intended for the d2vzw on another variant, unless it's a d2lte rom

My S3 running BlissStalk
[Galaxy Note 3 Q&A, Help & Troubleshooting] haigboardman1:
Basically im selling my N9005 so needed to return to the stock firmware... however the odin process failed and i cant for the life of me get it to pass now the phone only goes into download mode.

I basically need all the tar files for odin... bootloader, phone, pda and csc. My Note 3 is the UK N9005 on H3G.

if you can help me ill be very grateful!