yashsingh1/xdaforums huggingface dataset:
[Windows 10, 8, 7, XP etc.] leclark:
I'm very tempted... How much?
[Windows 10, 8, 7, XP etc.] FumiJ:
about $350.
[Nexus 6 Q&A, Help & Troubleshooting] php111:
Hey, how do I root the Nexus 6 on 7.1.1 and the Build Number is N6F26Q? Thanks.
[Nexus 6 Q&A, Help & Troubleshooting] Lawstorant:
I use Magisk
[Nexus 6 Q&A, Help & Troubleshooting] php111:
But how do I root? A link to a tutorial would be helpful.
[Nexus 6 Q&A, Help & Troubleshooting] bigmarv31:
https://xdaforums.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452

Go here and you should be fine? Is this your 1st time rooting the nexus ?
[Nexus 6 Q&A, Help & Troubleshooting] sanumaj:
Step-1

https://www.youtube.com/watch?v=29U7X4NgoUY

Look up Shamu Latest TWRP

Step-2

https://www.youtube.com/watch?v=84D2-UnUIA4

Look for the latest stable SuperSU

Done
[Nexus 6 Q&A, Help & Troubleshooting] php111:
Or this way which is longer.

Make sure the phone is in fastboot mode.

Than:

fastboot erase boot

fastboot erase cache

fastboot erase recovery

fastboot erase system

fastboot flash bootloader "name of bootloader"

fastboot reboot-bootloader

fastboot flash radio "name of radio"

fastboot reboot-bootloader

fastboot flash system system.img

fastboot flash boot boot.img

fastboot flash recovery recovery.img

fastboot flash cache cache.img

fastboot erase userdata

fastboot flash userdata userdata.img

fastboot reboot

First, delete the recovery file or replace with the TWRP recovery (just rename the TWRP recovery to recovery.img and yes, to replace when copy/paste, that should do the job).

Now reboot again and boot into recovery and than wipe cache and dalvik and flash SuperSU and wipe cache and dalvik again.

Someone above asked me is this my first root? No, my first root was on a Galaxy S3 which I do not have the S3 anymore. What made me to lose the root on the S3 was I took an OTA update and it KNOX the device so I could not root.

Yes, this is my first root on Nexus. No, it is not my first root in regards to Android :)
[Nexus 6 Q&A, Help & Troubleshooting] mpiekp:
Wugs toolkit does it fine in one click
[Nexus 6 Q&A, Help & Troubleshooting] poythegreat:
I just flashed supersu 2.78 in twrp, that worked
[Samsung Galaxy S7 Questions and Answers] dovedescent7:
Im getting constant bug reports with a new G930f G930FXXS1APG3 Trinidad & Tobago Baseband G930FXXU1APEQ rooted with TWRP security patch July, 1 2016.

My wife has identical phone/software with no bugs.

It keeps prompting me to update ota, i dont because i havent fully wrapped my head around taking software updates directly from Samsung. Coming from G900t so this is new to me.

For right now i would like to stay stock and custom recovery and keep or re root

Would anyone suggest trying to flashfire the latest ota if someone has it? Or would i flash in TWRP?

Can i Flashfire and keep TWRP?

Will updating 6.0.1 to 6.0.1 help with bugs?

I'm not sure what to do, but i would like to update this or stop the bugs without a custom rom for now.
[Samsung Gear S3] arl16:
Looking for a backup/travel charger. Anyone 100% satisfied with a 3rd party charger?

Saw this article with a bunch of them, many with no Amazon reviews. Anyone have any experience with these brands?

https://www.megebyte.com/best-samsung-gear-s3-charging-docks/

Or do I have to suck it up and pay $40 for an OEM S3?

Thanks!
[Samsung Gear S3] klingon888:
I bought a generic one from Amazon and working great so far but you have to use your own power supply which I have plenty. Eventhough it says for S2, the base is also taller which fits the S3 better. Only $9.99 - https://www.amazon.com/gp/product/B01K7F5F8Y. Some reviewers say watch gets hot but when I compared with the original charger, its the same - warmish but not hot. Even my S2 gets warmish after a full charge with original charger. Maybe I only used a 750mA power supply.
[Samsung Gear S3] arl16:
Awesome. Thanks! I'll give that one a try. For $10, hard to complain!
[Samsung Gear S3] Techvir:
I thought any regular induction charger should be work.

Sent from my Nexus 6P
[Samsung Gear S3] ednaptwo:
I bought a generic one from eBay which said it worked for S2 & S3.

Placed my S3 in and the watch displayed a "use original charger" message but it did charge, at least for a while.

The charger caused the S3 to get so hot that after about 10 minutes the watch displayed an over temp alarm, shut down and stopped charging.

$15 bucks wasted.
[Samsung Gear S3] arl16:
That sucks. I did go ahead and grab the one rec'd by Klingon888. I've had it for a little over a week, and so far so good. Seems to work as fast as the OEM, warm, but no more than OEM, definitely not "hot". So I'm satisfied. (So far - fingers crossed). Thanks again, [MENTION=321187]klingon888[/MENTION]!
[Samsung Gear S3] arl16:
This got me a little nervous. I've been using mine for a couple weeks now, and no problem. But I didn't realize they could go bad. Probably not worth waiting to find out. Think I'll grab an OEM...

http://www.tizenexperts.com/2017/02...rs-with-your-gear-s3-it-could-fry-your-watch/
[Samsung Gear S3] sandrinopi:
I got this charger from Amazon last week; so far so good, no overheating and charging times seem similar to the Samsung charger.
[Samsung Gear S3] Redflea:
How does that match up w/the height of the stock S3 charger from Samsung...I don't see it sticking up behind the watch face the way the stock one does.

Seems important that the aftermarket chargers match up w/the dimensions of the watch to have the charging HW positioned correctly on the watch for best efficiency and to avoid overheating issues.
[Samsung Gear S3] sandrinopi:
I don't have the Samsung charger with me to do a direct comparison; anyway here are some shots of the MoKo charger from different views so you can understand the way it couples with the watch compared to the Samsung charger.

S
[Samsung Gear S3] moralesd66:
Got this one. Solid and works well. Attached are comparison pics with the OEM charger. The only noticeable difference is the front facing led.

Galaxy Gear S3 Charger, Kissmart Replacement Charger Charging Cradle Dock for Samsung Galaxy Gear S3 Classic / Frontier Smart Watch https://www.amazon.com/dp/B01N0JTDXQ/ref=cm_sw_r_cp_apap_LDMtqlC4lTycA

View attachment 4036662View attachment 4036663
[Samsung Gear S3] Redflea:
Thanks, that's the first one I've seen that appears to be the same form factor.

When you say the "...only noticeable difference is the front-facing LED" do you mean that there isn't an LED, or that it uses different colors?

Just took a quick look at the reviews and remember seeing that one, but it has a bunch of bad reviews...I guess it's been OK for you, and based on comments you are using a different cable than the one included w/the charger.

Thanks!

---------- Post added at 10:50 AM ---------- Previous post was at 10:49 AM ----------

Thanks for the pics, don't have my S3 charger in front of me, but the pics you posted look like it's smaller than the stock charger. I'll check at home later.
[Samsung Gear S3] moralesd66:
The Led on the OEM one is larger. They both have LEDS but the OEM indicator light is bigger. The aftermarket one works well with my usb cables. The one that came with it will go in the trash. No charging disconnects with it either.
[Samsung Gear S3] Redflea:
Ordered it and it arrived today. Amazon URL: https://www.amazon.com/gp/product/B01N0JTDXQ/ref=oh_aui_detailpage_o07_s00?ie=UTF8&psc=1

As you said, looks very much like the S3 stock charger, very similar size/form factor, and charging time for a short 15% charge was what I expected, and watch did not heat up. I'm using my own USB cord, because from the Amazon reviews, problems w/the included USB cord were a primary cause of low ratings for this charger.

So I'm happy w/this one for now - see pics for more comparison. Samsung stock charger is on the left in pics attached.

Thanks!
[Samsung Gear S3] sandrinopi:
Yes the MoKo is smaller, here other pics.
[Samsung Gear S3] jestexman:
Bought one of these https://www.amazon.com/gp/product/B01ETEDPMC/ref=oh_aui_detailpage_o00_s00?ie=UTF8&psc=1 for my S8+ plus.. for fun i put my Gear s3 on it and it started charging.. I did not leave it on there to find out if it got hot or anything..
[Samsung Gear S3] jgrob:
I bought a package of two from Amazon and it fried my S3. The electronics inside did not seem to handle the charging rate. In 5 hours, the charge went from about 50% to about 80% and the watch was so hot I could hardly touch it. The vendor refunded my money and the chargers are in the recycle box. I was using it on the wall plug USB (Leviton) that can deliver about 2 amps whereas the Samsung adapter delivers 0.7 amps.
[Samsung Gear S3] moralesd66:
Post a link to the ones folks should avoid so save someone else.
[Samsung Gear S3] big_redfox:
Make sure it has magnet in the charge plate like the genuine one so that the watch can sit properly while charging. Otherwise it will either do not charge or fry your watch in extreme case.
[Samsung Gear S3] wwjoshdew:
Bought two of those. One for work (watch keeps "unsyncing" from my phone and I see "Start Journey" a lot. So my Watch tries to use LTE, and the signal is so weak... my watch dies very quickly!) so now I can charge it at work. Bought another for when we travel. Wife and I can take turns charging our watches. So far so good!
[Samsung Gear S3] Lister Of Smeg:
Hi Guys,

You're reviews are very useful, as I am looking to purchase an additional charger. I've got 2x of these Watches, as bought of a mate for a good price. However he lost one of the chargers, and Ive given one of the Watches to my dad. Was looking around, and bought one of these "compatible" chargers off eBay.

Whilst it said it was for the S3, when it arrived... it looked much smaller, and the S3 dwarfed the charger. I also own an S2 Watch too, and have the genuine charger for that. I compared the eBay charger with the genuine S2 charger, and they were the same size.

If I put the S2 on the compatible charger, it seemed to charge fine and no complaints. If I put the S3 onto the same compatible charger, it would show a message "Please use original charger". As soon as I saw that message, I removed the Watch, and going to send it back.

Some good reviews here, but when searching for THOSE chargers, they don't appear to show up... :(

Another thing I noticed, why are some chargers saying "NOT FOR USE with Tizen 3.0.0.2" What's so bad about the latest OS? Is the OS faulty, or has Samsung deliberately modified the latest firmware to not work with compatible chargers?? Seems a little dangerous if they've programmed them to overheat?? Last thing Samsung needs is ANOTHER FIRE issue...

All these issues with chargers now, makes me a little worried I could kill my dads Watch. But then on the other hand, I don't want to get stiffed, by paying 5x times the price for an official charger. It's how the manufacturers have us over a barrel... :(

Cheers, Lister
[Samsung Gear S3] RaymondPJR:
Those are basically copies of Samsung's design. I want a portable charger that's just a simple hockey puck design to top off when I'm out and about. I don't need a stand.
[Moto E Android Development] shubhojit89:
TeamHorizon's XenonHD rom builds for moto e Aka condor

http://www.xenonhd.com/

​

XenonHD is a custom firmware aka ROM for various Android devices. It is built from Android Open Source Project (AOSP) with additional features, performance and battery life improvements.

The idea behind XenonHD is to give users a ROM that is "blazing fast, rock stable and buttery smooth".

​

To install this ROM you will need to have a latest custom Recovery such as TWRP

Copy the downloaded ROM to your phone.

Boot into your recovery

Back up your ROM

Enter recovery

Make a full wipe (system, data, cache, dalvik). If you're updating rom or have other 5.1 already you don't need to wipe data (wipe system, cache, dalvik)

Install the ROM

Install GAPPS package

Reboot - and Enjoy

Download Links :

ROM : Xenon-HD OMS

Dated : 04-Feb'17

Gapps : Open Gapps ......

*This is a fast and fluid rom with perfect performance

Some Features:

1. Statusbar tweaks

2. Gestures

3. and find it yourself..

Know issues :-

Bluetooth : Unable to send/receive files

You can use shareit,xender

Credits :

CM Team

XenonHD Team

Google

XDA:DevDB Information

[NOUGAT 7.1] XenonHD 7.1.1 [UNOFFICIAL] [OMS], ROM for the Moto E

Contributors

shubhojit89

Source Code: https://github.com/teamhorizon

ROM OS Version: 7.x Nougat

ROM Kernel: Linux 3.4.x

Based On: AOSP

Version Information

Status: Stable

Stable Release Date: 2017-01-06

Created 2017-01-07

Last Updated 2017-02-04
[Moto E Android Development] shubhojit89:
Screens

Added screenshots
[Moto E Android Development] herloct:
This looks like CypherOS but with a lot more CM14.1 features.

Would love to try :D
[Moto E Android Development] Ujwal Agrawal:
Looking cool. One of my personal favorite ROM since mm days. But wasn't updated. Hope u will always maintain the ROM.:):good:
[Moto E Android Development] herloct:
After flashing it and fiddle with it, it really feels like CM14.1 + OMS + Pixel animated navbar.

I love it so far, since i needs some of CM14.1 features that a bit hard to find on other AOSP roms, like home long press action, live display, etc.
[Moto E Android Development] satria113nu:
I love this ROM but FC in cam record any solution?
[Moto E Android Development] herloct:
Use other camera apps, like Open Camera

------------

The SoT here is quite good.

I could get almost 6 hours today, and I don't even use any custom kernel yet :good:
[Moto E Android Development] shubhojit89:
Rom update

Anyone ready to test xenonhd update. Please pm.

Edit : Build has been tested by Shaikh Arbaaz.

Video recording bug is fixed at first it gives fc but later it works fine.

Link updated in OP.
[Moto E Android Development] Shaikh Arbaaz:
Smoothest Nougat Rom ever tested.:)
[Moto E Android Development] ankshious:
Has the bluetooth bug been fixed or not?

Sent via STARK SERVER
[Moto E Android Development] shubhojit89:
Nope it's not yet fixed. I have mentioned in the OP to.
[Moto E Android Development] Ujwal Agrawal:
Anyone wants update?
[Moto E Android Development] Rajendran Rasa:
We are waiting....
[Moto E Android Development] Ujwal Agrawal:
Ok, will do. But don't ask ETA
[Moto E Android Development] jasondutch:
Im Sorry, but what is an ETA?
[Moto E Android Development] ankshious:
ETA stands for Estimated time of arrival.
[Moto E Android Development] jasondutch:
Oh, Yea i understand why he doesn't like that, Thanks for explaining Ankshious?
[Moto E Android Development] govind1233:
New Build is Up... Android 7.1.2_r8.

https://www.androidfilehost.com/?fid=673368273298957207

Changelog -

1. Bluetooth bug is fixed.

2. Better RAM optimization.

3. Rootless Substratum Support

4. Home Button Animation.

5. Based on 7.1.2_r8.

6. May Security Patch...

Thanks...

---------- Post added at 08:53 PM ---------- Previous post was at 08:51 PM ----------

Here is Update For You all...

Please feel free to ask any ROM updates...

I will provide it...
[Moto E Android Development] Modder001:
Please compile AOSPA ROM bro :good:

And AOSIP too
[Moto E Android Development] govind1233:
Update wjll be available on 6th...with june security patch and more features
[Moto G 2015 Q&A, Help & Troubleshooting] username20162016:
Can someone please upload cyanogenmod 13.0-20161031 or 13.0-20161114-NIGHTLY zip file? Official website doesn't have old files other than snapshot but it isn't working well, too many issues.
[Moto G 2015 Q&A, Help & Troubleshooting] usernam20162016:
This request is for Moto G3 2015 Ospery Cyanogenmod nightly. Forgot to mention that
[Moto G 2015 Q&A, Help & Troubleshooting] Fupri:
Go to your phones forum. This one is for 1st Gen.
[G 2014 Q&A, Help & Troubleshooting] crypticlight:
Hi,

My friend's Moto G 2nd Gen (XT1068) stopped working all of a sudden couple of days back. When she tried to boot it, it went to bootloader screen (AP Fastboot Flash Mode) and none of the options work in the menu there. The phone had locked bootloader with stock firmware, so no customizations there. I thought may be something got corrupt in the firmware so I tried flashing stock firmware today, followed the instructions from 2 different posts -

1) https://xdaforums.com/moto-g-2014/general/official-stock-firmware-t3018682

2) https://xdaforums.com/moto-g-2014/general/official-stock-firmware-5-0-2-lxb22-46-t3019612

However, both of them gave me errors like below for all steps:

>fastboot devices
ZX1D63BLC6 fastboot

>mfastboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 5.007s]
writing 'partition'...
(bootloader) Failed to write primary GPT.

(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 10.277s

Irrespective of what and how I try, I get failed error every time. Can someone please help me here?

Thanks.
[G 2014 Q&A, Help & Troubleshooting] Vighneswar:
https://youtu.be/hDSpYALP_80 try this

If it doesn't work unlock bootloader https://youtu.be/isVFgZmfirg

---------- Post added at 05:13 AM ---------- Previous post was at 05:06 AM ----------

What is the status code ??
[G 2014 Q&A, Help & Troubleshooting] V.Mr.Gamer:
Just unlock bootloader, and try restarting to system
[G 2014 Q&A, Help & Troubleshooting] bostro:
Hey bro i had a similar error when trying to relock my phone after trying some customs roms.

I think it's same problem, it's the firmware version.

Recently Moto G 2014 had an update and if you use old firmware you had these errors, i suggest not to continue.

Some days ago new firmware has been published here: http://www.filefactory.com/folder/c6cdedc45a775d27/

XT1068_TITAN_RETAILDSDS_6.0_MPB24.65-34-3_cid7_CFC.xml.zip

http://www.filefactory.com/file/3lc...RETAILDSDS_6.0_MPB24.65-34-3_cid7_CFC.xml.zip

If you look, firmware is 24.65-34-3 and it's that "-3" that makes the difference!

Try to reflash with this firmware.
[Nexus 6P Q&A, Help & Troubleshooting] jhs39:
A lot of people in these threads seem to think Nougat is to blame for the boot loop issues. I know people on custom ROMs have encountered the issue--but if those ROMs are based on Nougat that doesn't disprove the blame on N. I'm curious if anyone running Marshmallow or Marshmallow based ROMs have encountered either boot loop issues or the boot loop of death?
[Nexus 6P Q&A, Help & Troubleshooting] CyberpodS2:
One person in another thread said after they downgraded to MM a week later it looped. Several questions I have would be, does the nougat install actually trip some condition? Was this users problem the same as the nougat loops? With only one example, it's too soon to really know. The 6P seems to be a bootloop magnet anyway so to answer your question, yes bootloop have happened but they can be corrected. The problem with the bootloop of death is even after flashing a full stock image (of any version) it's still boned.
[Nexus 6P Q&A, Help & Troubleshooting] jhs39:
I actually think a lot of bootloops of death could have been corrected but they are on stock phones with the bootloader locked and Allow OEM Unlock not selected in Developer's Menu. I've come across a lot of people in the threads in that situation. The only option then is RMA or paperweight.
[Nexus 6P Q&A, Help & Troubleshooting] v12xke:
If MM users are immune, then wouldn't flashing back to their old rom (or factory MM image) cure the loop? I don't know the answer, but just throwing that out for discussion. I think this has been tried on some affected devices but did not work. How could a loop in N prevent you from going back to MM? I honestly don't know. I'm very surprised that simply restoring a solid backup doesn't get a device right back on track, unless there is some kind of hardware defect causing the loop.

None of my Nexus devices are encrypted, and I'd be interested to know if the initial encryption process can be ruled out as a trigger for the bootloop. I wonder if the use of a no force-encryption modified boot.img to prevent encryption would prevent the looping. There's no way to know unless someone with a bootlooping device has already tried this and failed. Anyway, I'd like to hear from (and offer help to) anyone who would like to take things one step further and possibly find a way out of the looping.
[Nexus 6P Q&A, Help & Troubleshooting] CyberpodS2:
In my case, I was running pure nexus 7.1.1 , dynamics gapps, elementalx and supersu. Unencrypted. The install was running for a week and then while it was sleeping on my recliner arm I saw it reboot and that was it. No matter what I tried, it never recovered.
[Nexus 6P Q&A, Help & Troubleshooting] v12xke:
Ok, thanks for responding. My theory was that during the initial encryption process the phone locked up and started to bootloop. Just to clarify, how were you modifying the boot.img? Just running SU before first boot? I would usually queue up SU and then EX in TWRP and run before first boot. Now I just use FlashFire and it takes care of that on the fly. Glad you are back up and running. Wonder how long you will stay on 6.0.1? ha ha ha :D
[Nexus 6P Q&A, Help & Troubleshooting] CyberpodS2:
Followed the Heisenberg tutorial to get to the point where I was running unencrypted, rooted with twrp. Then was just flashing like normal.

---------- Post added at 05:02 PM ---------- Previous post was at 05:01 PM ----------

No I am not back up yet. RMA was my only option. Waiting for it to return.
[Nexus 6P Q&A, Help & Troubleshooting] jhs39:
Are you running Marshmallow or Nougat?
[Nexus 6P Q&A, Help & Troubleshooting] CyberpodS2:
It was on nougat 7.1.1 I'm back on my N6 now until the 6P is back from RMA. I'll be installing 6.0.1 on it what it returns unless someone has answers.
[Nexus 6P Q&A, Help & Troubleshooting] CyberpodS2:
I'm going to try bumping this thread before starting a new one. Anyone who got into the "bootloop of death" and had to RMA, can you please list what Rom and what circumstance brought on the loop. Maybe we can find a common thread. If this has already been tried, no harm no foul but I'll start. Pure Nexus 7.1.1 with elementalx and super su. It was just sitting there sleeping in front of me when I saw it reboot. Never got it back up again.
[Nexus 6P Q&A, Help & Troubleshooting] ticiano_arraes:
I managed to get back from bootloop. Dont know if just luck but my phone was totally locked, no OEM Unlock or Root. I did a wipe for no good, flashed latest OTA from stock recovery and nothing. Than I put my phone in my wife's Moto Z charger and wiped everything again. Boom. Booted.
[Nexus 6P Q&A, Help & Troubleshooting] BIGSAMDA1ST:
Stock rooted, about a week or so after updating to 7.0, while on a YouTube video phone froze, rebooted and the rest is history. Without being able to get into recovery mode and trying about everything there was to try ,I just finally gave up and had it rma'd.

This happened back on October.
[Nexus 6P Q&A, Help & Troubleshooting] Balino:
Stock rom and flash kernel. I was Just playing around the settings and started to bootloop. Huawei replaced the Logic board in a month here
[Nexus 6P Q&A, Help & Troubleshooting] Wickidmasshole:
DU 7.1.1 latest weekly on J vendor. a week after i got the battery replaced! had the flashlight on and went to take a pic. phone froze. booted into recovery once and it just died. Out for repair now. the only saving grace is Huawei ships to and from with Overnight.
[Nexus 6P Q&A, Help & Troubleshooting] :
who replaced your battery, was it an oem battery?
[Nexus 6P Q&A, Help & Troubleshooting] rndchef:
I am on stock unrooted. Was updating permission for Greenify and the bootloop started. I have Wugfresh flashed stock image and still bootloop. I can get into bootloader but not recovery. I have flashed stock image 3 times and everything loads properly but still bootloops. Never seen this before on any phone. A fresh stock flash always brings it back. Not this time. Any help would be great????
[Nexus 6P Q&A, Help & Troubleshooting] Wickidmasshole:
im under warranty so i sent it back to huawei directly and they put it in. It was marvelous having true 100% and not s h i t t i n g out randomly during they day. But once again they have it bc of this damn bootloop issue.