yashsingh1/xdaforums huggingface dataset:
[Advantage X7500, MDA Ameo Upgrading] johnripper:
roms from x7510 for ssd test http://xdaforums.com/showthread.php?t=441684
[Advantage X7500, MDA Ameo Upgrading] keithwwalker:
I have the Transcend 16gb SSD installed and the ROM for the SSD test.

Here is more Transcend SSD info:

http://www.hjreggel.net/hdtechdat/hd-transcend.html

Last time I used WM5 Storage aka WM5torage, to format the SSD. That resulted in only ~78mb being recognized. This time, hopefully some controllers for the SM223TF AC will show up. I know that the Eee PC with SSD has the same controllers. Does anyone have an SSD Eee to help out?

If that doesn't work, I just may format it to be an external USB drive and see how large the partitions are.
[Advantage X7500, MDA Ameo Upgrading] keithwwalker:
Question?

How to dump the registry listing from the ROM? I figure, if we can have the listing, then we can have more than 2 people scanning the registry looking for files related to the SSD.

Am I on the right track???
[Advantage X7500, MDA Ameo Upgrading] keithwwalker:
I ran v1.73 of WM5torage and the SSD is recognized under USB connection.

It is titled WM5torage ATHE400 USB Storage Device. It is not formatted so the capacity still reads 0

Question is how to format it through WinXP or Vista????
[Xperia Z1 Compact Q&A, Help & Troubleshooting] camdecoster:
I recently purchased a Z1 Compact and have discovered that when using Google Voice to dial all calls, the wrong number is stored in the call log. This makes it hard to track who I'm calling. From what I've read, this is the number that Voice calls before connecting you to your contact. The way it's worked previously on other phones is that the contact number is stored in the call log and the go-between number is called in the background. This is the proper way and what I'd like to get back to. Does anyone know how to fix this? I'm on 4.4.4. If anyone has Lollipop, has this issue been fixed? The one workaround I've seen is that you should store these numbers in the contact information (as each number is specific to a contact) so that you'll see your contact in the call log, but I'd rather just fix the issue. Ultimately, I believe the issue stems from Sony modifying the stock dialer such that the Voice app doesn't hook in properly to show the contact phone number in the call log. I've seen that some Samsung phone users have the same issue. Please let me know if you have any advice.
[Xperia Z1 Compact Q&A, Help & Troubleshooting] camdecoster:
Whatever the issue was, it has been fixed in Lollipop.
[G 2014 Q&A, Help & Troubleshooting] utkarsh agarwal:
Hey guys,

Im on 5.0.2 stock rom and there's a problem while m merging calls . when i click on merge option it says unable to conference call.

Is there a solution to this problem
[Sony Cross-Device General] aminfauzi:
​

>>> INTRODUCTION <<<

Here I shared the lollipop media sound took from latest Xperia Z3&Z2 Lollipop firmware. Maybe it was not necessary for devices that are already on the android 5.0 aka Lollipop, but it may be necessary to device users who are still running, such as Jellybean or Kitkat.

>>> REQUIREMENT <<<

Rooted devices

Have recovery (CWM/TWRP)

Some flashing experience

>>> INSTALL INSTRUCTIONS <<<

Download the zip file

Place the zip in your device

Reboot into recovery

[*]Do a BACKUP first ( in case of any problem)

Flash the zip

Done !

>>> DOWNLOAD <<<

=> Xperia Lollipop Media Sound

***NOTE : This Flashable zip will erase all old media sound and replace it with new one.

>>> CREDITS <<<

All XDA community members
[Sony Cross-Device General] yakupTR:
Thanks Bro :)
[Sony Cross-Device General] Pandemic:
[MENTION=5329107]yakupTR[/MENTION]

Is it always needed to quote the whole OP ?

Please edit your reply !

Link is working fine, look !

Sent From My Z2 On LP 5.0.2 Full Debloated !
[Sony Cross-Device General] Inceptic:
I hear the sounds from LP is copy from KK. Did sound is really changed?
[Sony Cross-Device General] aminfauzi:
maybe we didn't noticed some changes right? but if you hear that properly, there is diffrent between kitkat and Lollipop ringtones. ;)
[Sony Cross-Device General] Rajeev:
Wowww.. Nice work bro.. Happy to see you back...
[Sony Cross-Device General] aminfauzi:
Nahh, just a simple mod bro. not expert like you. hihi. happy to see you too.
[Sony Cross-Device General] mbc07:
Thanks for the upload, really liked the new default notification sound and ringtone.
[Sony Cross-Device General] Saelfos Emaka:
Thanks man, i really appreciate this.
[Sony Cross-Device General] mszain:
Work for custom roms or only stock?
[Sony Cross-Device General] aminfauzi:
Both.
[Sony Cross-Device General] Rajeev:
Hi

Both of you my friends.. Is there any specific reason for quoting the whole OP? Its really irritating dudes.. Kindly edit ur reply and remove OP content.. Its against XDA rules...
[Sony Cross-Device General] Diverti:
Mediafire not downloading

I tried it on PC also and i got blank page..can you upload it to another site? Thanks
[Sony Cross-Device General] alexmakerperson:
Works for lineage 14.1 on my xperia V. Thanks a lot!
[Shield Tablet Q&A, Help & Troubleshooting] Mechcondrid:
is there currently a custom kernel for ota 2.2? i currently have multirom installed and need the kexec feature but i notice the kernel img on stock is about 7 megs while pichu's kernel is about 5.5megs so im guessing i cant use his kernel with the 2.2 ota?
[Galaxy S III Q&A, Help & Troubleshooting] Salah77:
After I flash new official rom my phone ? loose the network

I tried service mod but not work ,rooted and flash modem also not work

Please help
[Galaxy S III Q&A, Help & Troubleshooting] josephiskandar:
You tried flashing back your former firmware ?
[Galaxy S III Q&A, Help & Troubleshooting] boomboomer:
You have posted only half the story, what had been done to the phone previously? If your efs was patched, or kernel & modem, to fix botched repairs then you will have to repeat these patches each time you flash a firmware.
[Galaxy S III Q&A, Help & Troubleshooting] Salah77:
No. because I don't backup before flashing ??
[One (M8) Q&A, Help & Troubleshooting] BaconSupreme:
****ed up and didn't read things properly. I was trying to revert my phone to stock with an HTC RUU, that didn't work, and in haste and anger I set S-ON. On a device running CyanogenMod.

The threads I found on the subject weren't entirely helpful, so I'm here now, hoping I don't have to explain to HTC why I'm dumb. My device boots immediately to fastboot:

*** TAMPERED ***

*** RELOCKED ***

*** Security Warning ***

M8_UL_CA PVD SHIP S-ON

HBOOT-3.18.0.0000

RADIO-1.14.21331931.LA02_2G

OpenDSP-v32.2.2-00542-M8974.0213

OS-2.12.1700.1

eMMC-boot 2048MB

Jun 16 2014,18:47:55.0

Here's the output of fastboot getvar all:

(bootloader) version: 0.5

(bootloader) version-bootloader: 3.18.0.0000

(bootloader) version-baseband: 1.14.21331931.LA02_2G

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 2.12.1700.1

(bootloader) version-misc: PVT SHIP S-ON

(bootloader) serialno: FA45P

(bootloader) imei: 35871

(bootloader) imei2: Not Support

(bootloader) meid: 00000000000000

(bootloader) product: m8_ul_ca

(bootloader) platform: hTCBmsm8974

(bootloader) modelid: 0P6B12000

(bootloader) cidnum: CWS__001

(bootloader) battery-status: good

(bootloader) battery-voltage: 0mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: 6e0f5a3d

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!

finished. total time: 0.131s

If anyone has advice, I'd appreciate it. Thanks!
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
Delete your IMEI and serial number. Those are personal data, which should never be posted on open forums.

Which RUU? Only an AT&T RUU will work unless you modify MID/CID by s-off.

An AT&T RUU should work.
[One (M8) Q&A, Help & Troubleshooting] BaconSupreme:
Thanks, I'll make sure to edit those out if I post again. A mod did that this time, hooray.

It was an AT&T RUU. At one point, I installed a stock GPE ROM and might have changed my MID, but don't quite remember. I remember that I changed my CID, but changed it back for the AT&T RUU. Judging by this thread, my MID is an "AT&T, unlocked, developer ID", so I guess it'll work.

If it helps, the specific RUU I used was named RUU_M8_UL_K44_SENSE60_ATT_SECURITY_Cingular_US_1.58.502.1_Radio_1.16.21331931.LA11G_20.31A.4145.02L_release_368350_signed_2. I downloaded it from HTC.
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
That's because I reported to the mods to delete the personal data.

Your CID and MID are the correct one for AT&T.

That RUU will fail, since it corresponds to hboot 3.16; and with s-on you can't run an RUU with a lower number hboot than is installed on the phone (3.18 in your case). Any other RUU except that one should work. You can find the other RUUs on my AT&T specific Index thread:

http://xdaforums.com/showthread.php?t=2751432
[One (M8) Q&A, Help & Troubleshooting] BaconSupreme:
Bad news first: the only RUU in that thread (the 4.4.4 one from HTC) that I could have used didn't work and gave me an unknown error (155). The other executable was the one I was already using and all the others require a microSD card, which I don't own.

Good news instead: This was fixed by... unlocking my bootloader again. Once I did that, my phone booted into CWM which was still installed and then booted into Cyanogenmod which was still there due to all the failed RUUs not doing anything. Hooray!

Thanks for the help, redpoint.
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
Actually, you discovered an error in my Index thread, as the "Official" 4.4.3 RUU link should go here:

http://xdaforums.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423

Instead of incorrectly sending you to the "bootable" RUU.

Not sure why the 4.4.4 RUU is giving your error 155 (wrong image).

You actually never mentioned what the original issue with CWM was. Did it not boot?

I think relocking the bootloader wipes the phone. So maybe that was all that was needed to get CWM to boot.
[One (M8) Q&A, Help & Troubleshooting] BaconSupreme:
Yeah, I couldn't boot into CWM. Fastboot > HBoot > Recovery... poof, back into Fastboot.
[Nexus 6 Q&A, Help & Troubleshooting] mikecole79:
I am ever impatient. So when I saw new factory images up on the Google page, I just had to try them out. I upgraded to LMY47E, then naturally the next day I saw the news about LMY47M. Being that I'm a T-Mobile customer, I want the M version (reported the T-Mobile version) of the new 5.1. Unfortunately, as part of the LMY47E upgrade, the bootloader was moved from 71.05 to 71.08.

Now, trying to flash factory images from LRX22C results in a bootloader mismatch error. I got around this by manually flashing radio, system, boot, etc. images on the phone, and I do in fact now have the 5.01 build showing. However, when I try to sideload the LMY47M build, I'm receiving an error from this line in the updater script:

#getprop("ro.build.fingerprint") == "google/shamu/shamu:5.0.1/LRX22C/1602158:user/release-keys" ||
abort("Package expects build fingerprint of google/shamu/shamu:5.0.1/LRX22C/1602158:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");

It's stating that I have 5.0.2 LRX22G signed with test keys. I don't know how I would have got an engineering build installed from flashing factory firmware from the Google page, but apparently something is confused somewhere along the way. The best I can guess is that perhaps that's some leftover remnants from when I had installed a CM12 nightly build (which I believe is based on 5.0.2).

I don't know what I need to flash with what to get that cleared so I can sideload the LMY47M OTA, and I'm concerned that I may be unable to properly upgrade to additional OTA upgrades if there's a missmatch along the way. There was a confirmed update coming to move from LMY47E to LMY47M per T-Mo support , also confirmed by [MENTION=4504155]askd[/MENTION]es) but again, if I have some funky mismatched stuff, unsure if I can upgrade to LMY47E again and still expect to receive the OTA.

I'd love to have someone with more knowledge of these wonderful things weigh in on this. Educated opinions are always welcome, but someone with actual first-hand knowledge would be incredibly helpful to my sanity as well.

Thanks!
[Nexus 6 Q&A, Help & Troubleshooting] danarama:
Theres nothing you can do to receive the OTA now.

Maybe the M factory image will become available. If so, you'll be able to flash that. Well at least the system and boot image. If the bootloader is newer, that too.

I suppose the other options are that if someone could install TWRP with an unmodified, unrooted M on, they could take a backup of system and boot and give you them to do a Nandroid restore via TWRP... Or maybe someone can take a system dump for you. But you cannot downgrade the bootloader.
[Nexus 6 Q&A, Help & Troubleshooting] clairez:
What about relashing the factory image? Of course, this would wipe all data, config, apps, etc.
[Nexus 6 Q&A, Help & Troubleshooting] mikecole79:
Thank you both for the replies. My course at this point seems to be "wait until M is up on the factory images page", which is what I suspected.

I have done a full factory flash of the LRX22C image, manually (since the script fails because of the newer bootloader) and it has still left me with the engineering build stamp showing. Any idea where that information is coming from? The image I used to flash back was the LRX22C for Shamu from developers <dot> google <dot> com/android/nexus/images. I would think that would have wiped the world (exception of the bootloader that doesn't know how to travel back in time; should really introduce that thing to Doc....). I'm not sure if it's because of the bootloader itself, or because of some other thing that just didn't get wiped properly. I flashed the radio, boot, cache, recovery, userdata, and system images initially, then re-flashed recovery to TWRP 2.8 after. Where does ro.build.fingerprint get it's information from? Is that all from the bootloader?
[Nexus 6 Q&A, Help & Troubleshooting] gee2012:
But you can not flash an older bootloader;) So far for the developer phone :( At least HTC has S-Off.
[Nexus 6 Q&A, Help & Troubleshooting] clairez:
I could be wrong (often am), but I thought several folks tried and succeeded with a factory image flash, by using the following methodology:

1. If your phone is showing OEM Unlock in the developer options and you can boot into recovery, then

2. Boot into android and remove all security

3. Set OEM Unlock and USB debugging

4. Perform several reboots to ensure OEM Unlock is persistent (if not, do not proceed)

5. Perform a factory reset/data wipe in recovery

6. Reflash the 5.01 factory image (or wait for 5.1 M version) using the manual method located here:

[TUTORIAL][GUIDE][HOW TO] Flash Factory Images || Unroot || Relock bootloader

http://xdaforums.com/nexu...shamu-t2954008

* Use Method 2 from this tutorial, Method 1 does not work

7. You can relock the bootloader as outlined in the tutorial.

8. At this point if all went as expected, the N6 is factory fresh and eligible for the OTA.

But before you proceed check out some of the other posts to ensure that others have succeeded. So many reports of bricked phones it is hard to tell what caused the problem.

I have used the above method several times, but only reflashing to a newer version.

Hope this helps ....

PS: I missed the mention of CM12! There are so many variables in your situation, I am unsure now that there is a way back. So many of the hard bricked cases involved CM12. Good luck, I hope you come out of this right side up!
[Nexus 6 Q&A, Help & Troubleshooting] wadsface:
I am in the same situation as you are, mine shows my build fingerprint as "google/omni_shamu/shamu:5.0.2/LRX22G/dees_troy020120939:eng/test-keys" I have gone through the same steps as you have and tried to reflash LRX22C. I guess we wait until the factory image!
[Nexus 6 Q&A, Help & Troubleshooting] xdatastic:
Have you flashed a custom kernel? Sounds like a non-google boot.IMG or something is on the device.
[Nexus 6 Q&A, Help & Troubleshooting] doitright:
That is absurd.

Unlocked is unlocked is unlocked.

The only thing that may not be persistent is the flag in the dev settings menu, ENABLE oem unlock.

Once you enable the unlock, you may *immediately* try to unlock it. If the enable setting isn't persistent, then it just won't unlock.

ONCE IT IS UNLOCKED, IT IS UNLOCKED. DON'T EVER LOCK IT AGAIN.
[Nexus 6 Q&A, Help & Troubleshooting] chrisbo4:
I also received that error when trying to sideload the OTA. The only modification I made was using a custom kernel, but I flashed the stock boot.img before attempting to sideload. So I'm not sure what could have caused the error?

I just read somewhere that we can get the sideload to work if a line in the updater script is deleted or modified. Has anyone else read this?
[Nexus 6 Q&A, Help & Troubleshooting] android_mp99:
To sideload an OTA you need a stock recovery. I have been unable to sideload an OTA with a custom recovery installed since 5.0. The Dees Troy (guessing TWRP recovery) in the path is a dead giveaway that it is from the recovery. I don't think it is checking bootloader version when sideloading OTA.
[Nexus 6 Q&A, Help & Troubleshooting] danarama:
It is. OTA doesn't replace the bootloader. It patches the existing BL with the deltas - I.e. the code that have changed. Obviously the bootloader must be the exact expected version for a patch to work, so it is definitely being checked when you install an OTA, no matter what method you use..

If you patched the BL with an incorrect patch, you could very easily be facing a brick.
[Nexus 6 Q&A, Help & Troubleshooting] android_mp99:
Then I'm guessing the people that were able to sideload the OTA with the new bootloader got lucky or are talking a bunch of BS (totally possible). I haven't tried it myself but I know for sure that the stock recovery is needed to sideload the OTA since 5.0 and the error reported earlier by some could be because of the recovery installed.
[Nexus 6 Q&A, Help & Troubleshooting] danarama:
You definitely need stock recovery, yes
[Nexus 6 Q&A, Help & Troubleshooting] chrisbo4:
Since I have never updated my bootloader, I'm inclined to think it must be recovery. I was trying to sideload via TWRP.
[Nexus 6 Q&A, Help & Troubleshooting] efrant:
There are many reasons that people want to have a locked bootloader, such as, among many other reasons, your employer requires it, for example.

No, OTA updates do not verify which bootloader your device is running, and they do NOT patch the bootloader -- they fully replace it.
[Nexus 6 Q&A, Help & Troubleshooting] efrant:
You can use TWRP as well. It just requires an edit to one line in the updater-script file.
[Nexus 6 Q&A, Help & Troubleshooting] danarama:
Yes you're right, my mistake.

You need to have stock recovery to apply a stock ota. You could edit the updater-script for any amount of purposes, but that isn't really the point. The people who simply want to "check for updates" and use the standard mechanism to apply it, it will not work with twrp.
[Nexus 6 Q&A, Help & Troubleshooting] efrant:
Yeah, ok, but we were talking about sideloading the OTA, no? You can sideload an OTA update file (or even flash it directly from your device) using TWRP just by editing one line. But yes, as far as clicking on "check for updates" and having it install that way requires the stock recovery.
[Nexus 6 Q&A, Help & Troubleshooting] danarama:
You technically can. But then you edit the line, side load the ota via twrp, and immediately flash SuperSU to stop the updated system image from replacing the recovery.. It all seems a little pointless to me. If you're going to modify an ota (or download a modified ota) to side load from custom recovery rather than use a pre-rooted ROM.zip, it seems to add unnecessary steps.
[LG G Watch] woody4165:
Hi

I'm experiencing a lot of crashes on LG G watch with Android Wear 1.0.5.1785466 and a Nexus 5 with Cataclysm 5.1 Stable version.

The G Watch crashes and I get a message that Android Wear stopped working.

After this message the watch become unstable and starts to drain a lot of battery and in a few hours it arrives at 0% battery.

Anyone else experiencing this issue with Android 5.1 (stock or other ROMs)?

Thanks

Woody
[LG G Watch] prototovsky:
Yes, with a nexus 4 (5.0.1 or 5.0.2, stock or custom rom, it doesn´t matter) when the watch (5.0.2) looses bluetooth connection, it freezes and show this message. After a minute totally unresponsive, the watch begins to work again. It always happens.
[LG G Watch] woody4165:
It wasn't happening to me with cataclysm 5.0.1 on Nexus 5 with watch on 5.0.1 and then 5.0.2.

Really strange to me.

If it will happen again, I will think about going back in the Nexus...
[LG G Watch] prototovsky:
I´m waiting for 5.1 on nexus 4, but a factory reset on both devices should fix this
[LG G Watch] woody4165:
I have tried several times.

Now I have tried uninstalling Android wear on phone, factory reset on watch, reinstalling on phone and reconnecting.

I will wait tomorrow and see.
[LG G Watch] woody4165:
I'm still getting strange drain on the watch, even if it's unpaired from the phone.

Is there a way to reinstall the stock 5.0.2 onto the watch?

Where can I download and how can I do it?

Thanks

Woody
[LG G Watch] woody4165:
Solved

It seems it's an Android Wear issue. Now I am back to 1724356 and I have no issue, no crashes and no big battery drain.
[Advantage X7500, MDA Ameo Accessories] emilnaeri:
Hi guys i have dopod u1000 the battery life is realy good and im charging it every 2 days but unfortunatly when the battery got empty i want to recharge it will takes about 8 hours to get full charge!!!!! yes almost 8 hour for full charge. this is realy bad for someone if realy want to carry this thing everythime to everywhere because if the battery got empty then you have to sit at hoe for 8 hour for full charge or got second phone when the dopod u1000 battery got empty swuch the sim card to the senderly phone when you put you dopod to charging. now this is the question i have . i need a external battey charger i mean put your second battery sepratley to he device and charge by itself as you know the other pda hav ethis kind of charge it have battery slot place you put battery on it and it will charge automaticly. now i want to know do you guys know where can i find such external batterycharger for my dopod u1000 ? let me know
[Advantage X7500, MDA Ameo Accessories] wu5262:
don't double post pls
[Galaxy S Advance I9070 Q&A, Help & Troubleshooting] MachoFantastico:
Hello all,

I need some help. So a family member of mine was recently handed a Samsung Galaxy S Advance to use and it was my intention to see if it were possible to unlock the phone (from Orange UK) allowing her to use her own network on the Samsung. Now I've rooted android tablets a good few times and it's been a breeze but this phone as proven to be a nightmare all day. Basically I decided to use Odin3 to give the phone a clean standard firmware for me to start with (2.3.6) and Odin went fine, in the end it informed me that it had past and I thought everything was okay. But now the device won't start up at all or charge, the only thing that appears to get a response out of it is if I connect the USB cable, disconnect the battery then my PC will inform me of a connection noise and then it suddenly disconnected seconds later. Have I done something wrong here?

Unfortuantly I can't access recovery or download without the screen even turning on. I'd greatly appreciate some help. :( Thanks.