yashsingh1/xdaforums huggingface dataset:
[Sony Xperia E3] vanugenth:
updater-script

thank you for this tutorial it works well for FXP-cm-12-20150411-UNOFFICIAL-flamingo I also tried with cm 12.1 but it bricks the phone. Is there a different updater-script needed for every build? the AOSP builds cannot be flashed.
[Sony Xperia E3] aaronblaze:
Problem With Reverting To Stock Rom

When i flashed this custom rom (CM12 for D2203 FXP) i thought i would be able to get back to stock rom using flashtool and Xperifirm

But now Flashtool does not detect the device which it earlier did...Any suggestions ..I really want to get back to the stock..

Any help would be appreciated...XPERIA E3
[Sony Xperia E3] Jebik:
Xperia E3 Block on black screen

Hello boy i have try to upgrade my D2203 on CM12 But when i reboot it stuck on black screen apparently i didn't take the last version and i was needed to flash boot.img before launch my phone...

The probleme is the E3 battery is no removable how can i force reboot or shut down to flash it again??
[Sony Xperia E3] PJMOR:
You can either use a thin stick of some sort (like a needle) and poke it in the little hole at the back of the E3, or you can press the power and volume up button for approx 10 sec.
[Sony Xperia E3] Solskun:
Question regarding the compatibility of my Firmware

I currently have a Sony Xperia E3 D2203, rooted, and has CWM-Recovery installed. Will this ROM installation method work with my device that currently has Firmware 18.5.C.0.19? And does the camera work for this ROM? I really want to make the transition to Cyanogen mod! Any replies would be highly appreciated!!!
[Miscellaneous Android Development] raviindia:
1.	First installed drivers for your Micromax model, Download root file from this link. (This is a password protected file, ask for password) and this is genuinely working.

2.	Transfer the SuperSu.zip file in your phone’s SD card or internal SD Card.

3.	Then open SP_Flash_Tool_v5.1352.01 and double click on flash_tool.exe

4.	Select scatter file for your mobile phone, see picture for below information

5.	Then select recovery (See below picture for info)

6.	Now click download in SP flash tool, remove the battery from your phone and connect it to pc via USB Cable. A green circle/download ok will confirm flashing.

7.	Now insert battery and press Volume UP+Down+Power ON, then press Volume UP to select recovery.

8.	Tap on Install from SD Card/ Internal SD card and select SuperSu.zip file from file location and select “yes” for flash this file.

9.	Reboot your Device, Done.

10.	You can check there is a SuperSu icon in your App Drawer.
[Miscellaneous Android Development] O_G:
Thread closed.

Please open one thread with the same subject matter.

http://xdaforums.com/android/development/root-micromax-unite-2-a106-fullly-method-t3116945
[One (M7) Q&A, Help & Troubleshooting] kel singh:
Hi Guys

I am very new to this. I bought a M7 from ebay. It was a T-Mobile UK phone. It had the latest lollipop OS on and it was working fine. I was transferring my files over from my other M7 and it suddenly turned off. Since then it is just stuck on the HTC logo. I have tried to hard rest but even after selecting factory reset or recovery it restarts to the logo and is stuck.

Also on the bootloader it says LOCKED and not TAMPERED.

Please can someone tell me how to resolve this step by step as I have been searching the forums but am extremely confused (certain links to toolkits are not available and I just do not understand all the technical stuff like unlock, s on /off!!)

Please someone help!
[One (M7) Q&A, Help & Troubleshooting] alray:
Is the phone still under warranty? If yes send it back.

Otherwise post the output of "fastboot getvar all". Remove the IMEI and SerialNo before posting it.
[Wear OS General] dataonlycod:
Hey guys, this is my first post so probably i will have a lot of erros. Pls dont be angry haha.

First Everything here is at your own risk so if your watch stop working is your fault no mine. You have been warned. Lets start:

-You need to instal TWRP in your smartwatch.

-When you have installed, start in recovery mode, and go to mount and press system. Connect your watch to your computer and open ADB

-Make a copy of the file and open the file with notepad++, you will se the following things

-Remove the part of ( touch.wake = 1 , please make a copy, because you will need it :D.

-Now go other time to adb and putt he following

-Restart the watch.

-Now you will see that is impossible to block the watch, calm down xD. Restart other time the watch in recovery.

-Now with the copy of the original file, mount system on twrp and puth this on adb (the file must have the same name as the original)

-Restart the watch and now, you will se that the screen is only going to be unlocked by the button of your watch.

Also if you want to sabe more battery you can change the cpu governor :p
[Wear OS General] kavinzhao:
Looks like you have mistyped adb push into adb pull.

Good idea. Tryin.

EDIT : looks like you don't know adb pull and push:

Push means Computer to Device

Pull means Device to Computer

---------- Post added at 19:51 ---------- Previous post was at 19:46 ----------

And shouldn't 'sec' means Samsung? This guide may only work for Samsung devices. Please modify.

Maybe we have to find the exact file using ls.

Nice work.
[Wear OS General] dataonlycod:
I know hahaha, muy mistake :p .Also i want to know if this work for mor people
[Wear OS General] -RioT-:
Thanks! Ill wait a bit for you to work out the typos. I also have to decide if i want to keep my LG R or get the zenwatch2 when it is out... But hanks all the same. This has been bugging me since i got the watch. Theater mode doesn't send notifications and I cross my arms while I sleep, waking my watch up all night...

Also thanks for posting the other sources for each watch. Great first post!
[Wear OS General] kavinzhao:
Working on Gear 2.. no need to copy the original file back.
[Wear OS General] bitstra:
working on LG g watch (wear 5.1) fine too, but the .idc-filename is

/system/usr/idc/synaptics_rmi4_i2c.idc now!

Only replace the last line

touch.wake = 1

with

# touch.wake = 1

I'm sure

touch.wake = 0

instead of commenting out, would work to! - But didn't test it...

and push the file back...

after reboot touch2wake is disabled and rotateWRIST2wake works fine!

Lets see how much battery drain will be decreased...

Thanx [MENTION=5975046]dataonlycod[/MENTION] ! (for finding and your solution):good:
[Wear OS General] bitstra:
No measureable benefit

Disabling touch2wake gave me no longer battery life here !!!
[Wear OS General] 2k4ever:
I've done the mod on my LGWR by simply booting (not flashing) TWRP

funny thing is that now the watch won't wake when touched, but it is still possible to scroll through notifications

as scrolling notifications is still possible, the touch screen is still active

to save battery, you would have to find a way to really disable it - but the power reduction sould be negligible
[Wear OS General] starbase64:
how can i block scrolling in ambient mode?
[Wear OS General] 2k4ever:
I don't know

keep in mind that disabling touch 2 wake is just a hack

the most probable way would be an xposed module that disables the toch screen when the watch goes into ambient mode
[Wear OS General] persichini:
I was hoping this would fix the issue i have when i cross my arms and the watch starts doing things because it thinks my arm is my finger... ugh
[Wear OS General] Alaa apk:
Thanks

La:good:
[Wear OS General] foggy69:
Has anybody managed to get this hack working on the Sony Smartwatch 3.

The file that appears to need editing is called 'synaptics_dsx.idc'.

I have ensured the edited file is pushed back to the phone, but the hack never works.
[Wear OS General] ediulia:
hi friends/ does it work for URBANE ?
[Wear OS General] orekasep:
Hi friends, anyone get it to work with Moto 360 ?
[Wear OS General] flippy_:
I had the same issue.

And here's what I did:

1. Set touch.wake = 0 on the file

2. Installed 'Showear: Android Wear Lock ' app from google play

link: https://play.google.com/store/apps/details?id=com.jdd.showear&hl=fi

3. Set lock method as sequence of swipes: Just one swipe from left to right

4. Set the following setting:

- Auto-lock on standy

- Lock on startup

- Vibration (to notify me when I unlock the screen since I set the lock screen invisible)

- Hide lock screen on standby

- Transparent lock screen

- Transparent (unselected) lock elements (Answer no to the msg box after setting this on)

Yes this way needs me to swipe the screen from left to right every time I want to use touch on the watch with my finger, but it is now impossible for any touch event to occur when the screen is dimmed since the lock cannot be unlocked from dim mode with the option 'Hide lock screen on standby' selected.

And having that no-touch on dim mode is way more important to me than the added swipe.

Hope this helps
[Wear OS General] KiToNaS:
very useful tip , thanks
[Wear OS General] moody07:
nice woooooooork
[Wear OS General] Dandgqro:
Fine

I will try, anyway I get pretty decent batt life with my Sony sw3, 4 days. :)
[Huawei Ascend P7] luiskpm:
Hi guys,

I got a Huawei P7 and wanted to know how its currently the battery life in a daily use, with normal usage.

WhatsApp, some Facebook, some camera.
[Huawei Ascend P7] gregysk:
Average use...stock rom B.616..rooted..some system apps and google stuff deleted...
[Huawei Ascend P7] luiskpm:
Hi can you advice me please how to get those numbers
[Huawei Ascend P7] gregysk:
Like I said before,I deleted all google c..p and almost all system apps so I don´t have any background process beside necessary process.Look at the screenshot what I have from apps.
[Huawei Ascend P7] PrimuSSaintS:
thanks for the screenshots. What did you use to get rid of all the apps? (I'm not rooted yet (I was but got rid of it to update) My battery hasn't last a day for me (I might have an heavy usage) and I only get about 2 hours of screen time (and when I say about it means under two hours ... :( )

Could you post a picture (or pictureS) of your app tab in the settings menu? You know, to see what you disabled and what you got rid of.
[Huawei Ascend P7] gregysk:
I deleted apps with root explorer(after rooting the phone) and that's it.

View attachment 3344335
[Huawei Ascend P7] skeptic1007:
Hello. Could you, please, post the contents of your /system/app and /system/priv-app folders? It would be easier to remark the files that were removed. Thanks a lot.
[Huawei Ascend P7] gregysk:
Here are the screenshots...

View attachment 3357800View attachment 3357801View attachment 3357802View attachment 3357803View attachment 3357804View attachment 3357805View attachment 3357808View attachment 3357809View attachment 3357810
[Huawei Ascend P7] skeptic1007:
Thank you, good work. I may have removed too much, since after doing this I can no longer send sms messages. Verifying the guilty party requires a reboot each time a file is added to /system/app folder.
[Verizon Motorola Droid Turbo General] hassancasa:
DROID Turbo by Motorola​

View attachment 3329129

Specifications:

-Operating system:

Android 4.4.4, KitKat®

-System Architecture/Processor:

Motorola Mobile Computing System, including Qualcomm® Snapdragon™ 805 processor with 2.7 GHz quad-core

CPU (APQ8084) with 64-bit memory access

Adreno 420 a 600 MHz GPU

Natural Language Processor

Contextual Computing Processo

-Memory (RAM):

3 GB (LPDDR3 with 64-bit access)

-Storage:

32 GB (All models)‡

64 GB (Black Ballistic Nylon only)

-Dimensions:

Black Ballistic Nylon

Height: 143.5 mm (5.65 inches)

Width: 73.3 mm (2.89 inches)

Curve: 8.3-11.2 mm (0.33-0.44 inches)

Metallic Red, Metallic Black

Height: 143.5 mm (5.65 inches)

Width:73.3 mm (2.89 inches)

Curve:7.8-10.6 mm (0.31-0.42 inches)

-Weight:

Black Ballistic Nylon

176 grams (6.2 ounces)

Metallic Red, Metallic Black

169 grams (6.0 ounces)

-Display:

5.2” AMOLED

1440x2560 Quad HD

565 ppi

Corning® Gorilla® Glass 3

-Battery:

3900 mAh

Mixed-usage Up to 48 hours*

Supports Motorola Turbo Charger (included)

Up to 8 hours of mixed usage battery in 15 minutes of charging

-Water-resistant:

Yes

-Networks:

4G LTE

CDMA / EVDO Rev A

UMTS / HSPA+

GSM / GPRS / EDGE

Rear Camera:

21 MP (5248 x 3936) in 4:3

15.5 MP (2952 x 5248) in 16:9

f/2.0 aperture

Tap anywhere to capture

Dual LED flash

Auto focus

4X digital zoom

1080p HD video

4 K (UHD) video

Slow motion video

Burst mode

Auto HDR

Panorama

Drag to Focus & Exposure

-Front Camera

2MP + 1080p HD Video

-SIM card:

Nano-SIM

-Connectivity

Micro USB

3.5 mm headset jack

-Bluetooth® Technology:

Bluetooth version 4.0 LE

-Wi-Fi:

802.11 a/b/g/n/ac (dual-band capable), mobile hotspot

-Speakers:

Mono, front-ported

-Audio Playback:

AAC, AAC+, Enhanced AAC+, AMR-NB, AMR-WB, MIDI, MP3, PCM/WAVE, FLAC, OGG/Vorbis

-Video Playback:

H.263, H.264 AVC, H.265, MPEG-4 SP, VP8

-Video Capture:

4K at 24fps

1080p at 30fps

720p Slow Motion

NFC:

Yes

-Mobile Payment Services:

Softcard

Google wallet

-Location Services

A-GPS

-Sensors

Accelerometer, Ambient Light, eCompass, Gyroscope, Hall Effect, Infrared, Proximity

-Base Colors:

Black Ballistic Nylon

Metallic Black

Metallic Red

Sapphire Blue
[Verizon Motorola Droid Turbo General] RACER69:
When lolipop is coming???
[Verizon Motorola Droid Turbo General] hassancasa:
PROS

Beautiful redesign

Notifications are much better

Support for multiple user accounts

Improvements in performance

Smart Lock

CONS

Some UI elements can be confusing

Limited multi-pane support in landscape mode, and no split-screen multitasking

Some users will lament lack of lock screen widgets

Overview can get too crowded with tabs

SUMMARY

Lollipop is the biggest Android update yet, featuring a pleasant new design and loads of clever features that enhance the user experience.
[Verizon Motorola Droid Turbo General] ceelos218:
thanks for the information... had no idea whatsoever.
[Verizon Motorola Droid Turbo General] jaymz168:
This may be the most useless post I've seen in the Droid Turbo forum and that's really saying something.
[Verizon Motorola Droid Turbo General] seshaz:
Thanks sooo much for this information that is otherwise unavailable anywhere on the internet. Such a great contribution to the development
[Verizon Motorola Droid Turbo General] ceelos218:
this guy might just surpass j.case in development
[Verizon Motorola Droid Turbo General] wrconstruction:
i have widgets on my lock screen
[Verizon Motorola Droid Turbo General] Pika71:
it is copy and paste? :confused:
[Verizon Motorola Droid Turbo General] sseuorosal:
thanks for the information
[Verizon Motorola Droid Turbo General] TonyStark R.I.P.:
There is no need for posting extended information beyond here.

However if there is a need for more in depth specfications, please use this link in the future:good:

Thank you,

Thread closed
[Wear OS Software and Hacking General] admisi:
Anybody know if there is an Android Wear app to easily get to the bluetooth option in the Watch Settings to quickly Connect or Disconnect my headphones.

Thanks
[Wear OS Software and Hacking General] 1%Walker:
just open bluetooth view or toggle bluetooth?
[One (M7) Q&A, Help & Troubleshooting] QA Bot:
Q&A for [MOD/Fix]Re-enable back button menu

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for [MOD/Fix]Re-enable back button menu. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)
[Xperia Z1 General] f3nix82:
Hi,

!!! WARNING !!!

C6903 only!

Use at your own risk!

!!! WARNING !!!

Firmware info:

Device: C6903

Build number: 14.5.A.0.270

Android version: 5.0.2

Customization version: 1276-4318

Branding: Central Europe 1

The following items are integrated into this ROM:

XZDR: 2.8.15

SuperSU: 2.46

How to update:

1. Put the flashable zip file on an external SD.

2. Boot into TWRP and install the update file.

3. Clear cache/Dalvik cache.

4. _Power off_ the phone (do not boot into system yet!).

5. Flash the stripped ftf with Flashtool (version 0.9.18 required). _DOUBLE CHECK THE WIPE OPTIONS!!!_

6. Boot into system.

7. Enjoy! :)​

Do not forget to _BACKUP_ before performing these steps!!!

This wouldn't be possible without the great work of [MENTION=4904057][NUT][/MENTION]! Thank You very much! :good:

Downloads (Google Drive):

Flashable zip: C6903_14.5.A.0.270_CE1_1276-4318.flashable.zip

md5sum: 3ea49434cb9f72acffd6e6648b14ca7c, sha1sum: f9c585ffe4ea47f3aedf37e90073eb3293f3f246​

Stripped ftf: C6903_14.5.A.0.270_CE1_1276-4318-stripped.ftf

md5sum: 3e0a0c93ce2392453c6e9ef2ec44916f, sha1sum: b9919fe6354d67505832c5100490b4d5b36c416c​

Enjoy! :)

Cheers,

Mateusz
[Xperia Z1 General] vladanpg:
After I flashed the tft, and checked the build number, I still have the .242 version. The flashing went fine. Why?
[Xperia Z1 General] f3nix82:
Hi,

did You do all the steps from the instructions? Or have You skipped some steps?

It looks like You have not flashed the zip file via recovery.

Cheers,

Mateusz
[Xperia Z1 General] fosko_esper:
About the 5th step

the 3 wipe options must be all checked or all excluded?

Thanks
[Xperia Z1 General] f3nix82:
Hi,

I do usually uncheck APPSLOG and DATA.

HTH! :)

Cheers,

Mateusz

Wysłane z mojego C6903 przy użyciu Tapatalka
[Xperia Z1 General] santaa:
thank you <3
[Micromax A106 Unite 2] raviindia:
1.	First installed drivers for your Micromax model, Download root file from this link. (This is a password protected file, ask for password) and this is genuinely working.

2.	Transfer the SuperSu.zip file in your phone’s SD card or internal SD Card.

3.	Then open SP_Flash_Tool_v5.1352.01 and double click on flash_tool.exe

4.	Select scatter file for your mobile phone, see picture for below information

5.	Then select recovery (See below picture for info)

6.	Now click download in SP flash tool, remove the battery from your phone and connect it to pc via USB Cable. A green circle/download ok will confirm flashing.

7.	Now insert battery and press Volume UP+Down+Power ON, then press Volume UP to select recovery.

8.	Tap on Install from SD Card/ Internal SD card and select SuperSu.zip file from file location and select “yes” for flash this file.

9.	Reboot your Device, Done.

10.	You can check there is a SuperSu icon in your App Drawer.
[Micromax A106 Unite 2] raviindia:
and the password is : "Micro106"
[Galaxy Note 4 General] zaidmashni:
Here's uploaded model for SM-N910G MODEL ONLY NOT RESPONSIBLE FOR IT

KNOX WILL STAY 0X0

WHATEVER COUNTRY N910G NO PROBLEM ONLY SM-N910G MODEL

ONLY BY ODIN

https://mega.nz/#!mpFjiJqL!8ZxwWozpEJAC448F4oWDqonm2rZtgMa8LRFzBvOVfwo
[Galaxy Note 4 General] m4gg0t:
Btw all the BOE1 firmware for N190G are carrier firmwares in Singapore M1, StarHub and Singtel. So you will get carrier bloat with them fyi. As far as i know Singtel firmware is the one with the last bloat.
[Galaxy Note 4 General] scoopdreams:
Any idea what changed in boe1?
[Xiaomi Redmi 1S] varunkum76:
:cowboy:I was using cyanogenmod 12.1 with twrp istalled when i get bored with it i change it to miui 6 with the help of stock recovery and recovery rom. After that i rooted it and installed super su binary script using twrp but i forget that i was on stock recovery and now it is rebooting and try to get in recovery andrebooting and try to get in recovery same..................

Those who experienced same situation please post how to solve .

Now i unable to boot and even recovery
[Android Q&A, Help & Troubleshooting] ashishghadi7:
This is my first thread about how to increase your android device volume.

Requirements:- Your device should be mediatek soc.

Note:- Before you increase the volume of your device just check the volume of your device so that you can differentiate between volume before and after.

To increase volume follow steps below:-

1. Open your dialer enter this code *#*#3646633#*#*. After dialing this code you will enter into engineering mode. (If you are not able to enter in engineering mode just install MTK Engineering Mode app from Play store, open app and tap on MTK settings you will enter into Engineering Mode.

View attachment 3329145

View attachment 3329146

2. Swipe and go to "Hardware Testing" section.

View attachment 3329141

3. Tap on "Audio". In Audio tap on "Loudspeaker Mode"

View attachment 3329142

4. In Loudspeaker Mode you will see " Max vol. 0~xxx"(for me it is 160) set it to highest value i.e 160 for me. Now play any song and check the volume.

View attachment 3329143

5. Don't change type and level.

Worked on my Micromax Bolt A068 and my sister's Lava iris 456 (MT6572) ;););)

If this thread is helpful please hit thanks and follow me on g+ :good: :cool:

Don't Repost

Note: If you feel setting higher values can damage your speaker than please set little lower values

The same procedure is listed on modaco.com by Kamal882. I've not copied his post but aftercreating this post just for verification whether anyone has derived this method I googled and I found another post by kamal882. I've not copied his post
[Galaxy Note II Q&A, Help & Troubleshooting] oscaraya:
Hi All,

I am having problem with a friend's phone. She have a GT-N7105 that loops into a "pseudo" download mode.

It is similar to ODIN Download mode but without the Odin message on top.

I cannot enter recovery mode but I can enter Odin mode (The real Odin mode)

I try Odin and Heindall but looks like there is a problem with the phone.

Odin fails with:

<ID:0/004> Get PIT for mapping..

<ID:0/004>

<ID:0/004> There is no PIT partition.

I cannot read the PIT file from the phone using Heindall. I am 99% sure that she did not have "USB Debug" mode on so I am not sure if that could cause the problem.

I don't even know if this is 32GB or 64GB version and I have been trying to download the PIT files, but I cannot find anywhere.

Am I missing something?

I know the basic of flashing but not that expert.

Please help!!

Thanks in advance.
[Galaxy Note II Q&A, Help & Troubleshooting] yaro666:
read THIS

or

THIS
[Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot] kirby2000:
I've managed mess up my HDX 8.9 while trying to install TWRP and now the touchscreen doesn't work properly.

I have ADB access and can navigate my tablet using shell commands to simulate keyboard presses, however when I use the touchscreen, it responds on the wrong part of the screen. This makes unlocking manually or selecting anything impossible. Touches still register, but just at the wrong part.

The table was working fine on the same day. I downgraded to 14.3.1.0 with no issue, however when I went to install TWRP I made a fatal mistake, I installed the THOR rom, instead of the Apollo.

After it rebooted, the touchscreen stopped working correctly. I then installed the Apollo TWRP over it using ADB but this didn't install TWRP or fix the issue. I used the commands shown

adb shell

su

dd if=/sdcard/signed-apollo-twrp-2860.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery

and it appeared to work, but no blue kindle fire logo or recovery menu when I hold down the + button.

I then tried to install SafeStrap. This works correctly, but the touchscreen still responds wrong.

Is there something I can do? Oddly enough the works fine and I can select and run apps, get into SuperSU, etc by using ADB keyboard commands.