yashsingh1/xdaforums huggingface dataset:
[OnePlus 2 General] v7:
Read the post above your's!XDA doesn't encourage social media promotions.If you have some device related discussions,you can have it here.That's what XDA is intended for.

I've seen like 5-6 threads with the same post or some social media links.I had made a Telegram group initially for the OP2 discussion.That's when the device was released and there wasn't much activity here on XDA.Now I've removed the links and no longer posting about it.

Now we have an active community here and no longer needs any private/social media for discussion.Try to keep all discussions here and make sure you know what XDA is all about! :good:

___

v7

XDA Assist
[HTC One Mini 2] DRAFF:
HTC One MIni2 - Unlocked - TWRP - Rom flashed

Restart the phone and I'm stuck on a black screen, with battery logo on the center, and the red wrigting "This build is for developement purpose only....".

In windows command line, I do "adb reboot recovery" (previously worked) but I have this error:

http://s14.postimg.org/dvvzx6ngh/Immagine.jpg

...and now i cant shotdown/reboot and nothing else...

Any solution?
[HTC One Mini 2] :
do not reboot phone with USB cable connected.

use power+vol up to reboot

are you using HTC orginal cable???
[HTC One Mini 2] tryllz:
Do you have the USB Debugging enabled ?
[HTC One Mini 2] DRAFF:
original cable, debuggin not changed becausa frash rom flashed....I solv it with volume- + volume+ + power=shoutdown

I'v installed the last stock firmware.

Now there is another problem: the phone is completely drained, put it on charge, and after a while I displayed a black screen, with the logo of the battery in the middle, and bottom of the red "This build is for developement purpose only .... ", red LED flashing. Cut the cable, it will not budge from that screen, compelled to force a shutdown (volume keys + power). Then boot normally.

How can I avoid this problem?
[HTC One Mini 2] :
you recovery might be corrupted. re-flash. i advise TWRP.

charge phone when off for a while the remove cable and turn it on.

if LED its flashing, it means its not charging.
[HTC One Mini 2] DRAFF:
The problem happens only when the battery is fully discharged. When I connect it to the charger, the LED flashes, and appears on the screen the logo of the battery and the red lettering at the bottom. Then, after a while the charge, forcing poweroff the phone with volume buttons and power, and the phone will restart correctly.
[HTC One Mini 2] :
them don't let battery run out completely. Use super power saver if gets too low
[HTC One Mini 2] DRAFF:
Thanks :D, but I prefer to solve the problem
[HTC One Mini 2] tryllz:
We agree that you intend to solve the problem, but till the time a solution is not found its advisable to keep the phone into ultra power saving mode at 15% or 10%, this will give about 8-15 hours of time to find a charger to charge your phone.

For me I have never let my phone die out of charge and I don't have a charger with me every where.

The only way to know if this is a recovery problem, which I doubt, is to flash the stock recovery and stock boot and check.

Stock Recovery: https://www.androidfilehost.com/?fid=24052804347822267

Boot File: http://xdaforums.com/attachment.php?attachmentid=3544788&d=1447703726

NB: MAKE SURE YOU HAVE MORE THAN 75% BATTERY.
[LG G Watch] :
[YOUTUBE][/YOUTUBE]I have an LG G Watch, ofcourse, but I have a few problems.

1. Some info (if it helps, I'm new to smartwatches):

Serial number: 04a3111c02a2006d

Build number: LCA43

Android Wear version: 1.3.0.2160025

Google play services version: 8.4.89 (2428711-534)

Android os version: 5.1.1

- I have (or should have - I can't get to it) TWRP recovery for the g watch:

https://twrp.me/devices/lggwatch.html

- I have (I'm guessing) succesfully rooted the watch:

m.pocketnow.com/2014/07/14/lg-g-watch-root (I didn't flash Gohma, just rooted using the guide)

- I have a custom kernel:

xdaforums.com/g-watch/development/kernel-invisibleks-dory-kernel-t3082669

- I have ADB debugging enabled

- I have restarted the watch many times

- Oh and I have an unlocked bootloader

- Probably a **** ton of other stuff

2. The problems

- I can't get to Recovery mode, probably a problem with TWRP not working

- I can't factory reset my watch (It goes to fastboot menu intead of doing it automatically and when I want to choose Recovery menu it just restarts fastboot menu)

- I can't connect to pc (I have windows - It says the drivers are not installed correctly, I have been able to connect before)

- I can't re-pair with my phone, because in the app I removed the watch and the watch won't factory reset...

- I can actually use the watch normally, juat can't connect and stuff

I hope someone can help, if you have any info please tell me!

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

[IMG="Fastboot menu"]http://s27.postimg.org/ytvs0021f/IMG_20160114_182030.jpg[/IMG]

A video of me trying to go into Recovery some info too:

https://youtu.be/8Xa0pPsfbew
[LG G Watch] MihaiSG:
Have you tried to reset the watch from the Settings? And try to boot the TWRP recovery from fastboot, just type fastboot boot x.img (x=recovery file) (make sure that you removed the drivers and reinstall them again).
[LG G Watch] Jaocagomez:
use another pc, install twrp from this forums.
[LG G Watch] KevinX8:
Just do

fastboot erase data

and

fastboot erase cache

that is effectively a factory reset would look into why a normal factory reset isnt working thought
[Blu Pure XL] aim1999x:
I just received notification for OTA update. (134MB)

BLU_p0010UU_V11_GENERIC_5.1_20151123-0956

1. Stagefright patch

2. google security patches

3. Mcafee security 2015

4.Other bug fixes

Anyone tried it ?
[Blu Pure XL] DrBrick:
i want to know if it is going to try and stick me with mcafee. . . happy to see an update, though!
[Blu Pure XL] DrBrick:
you can remove mcafee after the update.
[Blu Pure XL] jasonmastertech:
Can anyone upload ota?
[Blu Pure XL] jndd333:
Yes please. I'm rooted and it won't let me download the update. If someone could even offer a system dump that would be helpful.

---------- Post added at 02:29 PM ---------- Previous post was at 02:28 PM ----------

If only for the stage fright patch :)

---------- Post added at 02:32 PM ---------- Previous post was at 02:29 PM ----------

Also if someone could offer a system dump of the newest upgrade I'd be more than willing to cook up a rooted stock rom. I know I haven't been on the forums much lately at all but I remember working on stuff back in the t-mobile g1 days
[Blu Pure XL] blacksmithjk:
Rooting after the update

I only first tried to root my Blu Pure XL after the update was installed. I find that the boot loader is locked and I can not find a way to gain access. I am not sure if the update added this major inconvenience but I suspect it did as the rooting method as described will not work for me at all. Any thoughts or suggestions?
[Blu Pure XL] tbirdguy:
ive updated with every ota and root works fine... boot loader isnt locked... try to flash twrp via fastboot, and if that doesnt work enable developer options in settings and "Enable OEM unlock"

but like i said Ive flashed back to stock FW with SP tool (compete stock boot, recovery, and system ver .11) so if any update would have locked BL it would have locked mine... but it didnt, doesnt, and hasnt...

Follow the thread about twrp... it gives you very easy to follow directions.
[Blu Pure XL] ArconHadron:
Yeah, I did the OTA update before rooting, and it didn't want to allow me after the OTA update.

I downloaded multiple files from all over the place, placed them in a "root" subfolder and it still seemed impossible.

Got it done AFTER 3 days :(
[Blu Pure XL] tbirdguy:
so...

using flashboot to flash twrp, after the OTA,

then using twrp to flash the SU.zip took 3 days?

what files and "root folder" are you referring to?

Sounds like sever case of lack of reading or lack or user error;

But Im glad you stuck with it long enough to get it working...
[Blu Pure XL] ArconHadron:
Thanks, hardest part was actually getting phone to boot into flash mode.

Specifically, holding Power plus Volume+ is fine, but you have to let go of the power button first, then the Volume+.

Plus, I had to adb reboot before getting the TWRP rom to flash properly....

Not my best effort, but findintg SPECIFIC instructions were difficult, and had to manually search for latest fastflash and TWRP......v2.8.6.0
[Blu Pure XL] tbirdguy:
Fastflash?

Manually search?

Under the Development heading there are 5 topics, 2 of which are for TWRP recoveries (3.0.2 is buggy but works, just takes long time to wipe and restore; and theres SOOOOO many posts about how to flash them and how to use SP Flash Tool... so once again; glad you stuck with it, but Im still going with user error due to fail to RTFM
[Android Q&A, Help & Troubleshooting] ggabrielber:
Hi everybody!

I have a problem with my Htc Desire 310 V1Plus from Austria.

It was traped into a bootloop and i've tried to flash with spflashtool a ROM from easy firmware for Europe Htc Desire 310 Models and

now the phone is really dead bricked.

It doesn't boot anymore and only is recognized in device manager(Preloader mediatek).

I've tried to flash many versions of ROM with different Spflashtool versions but i always got the same error:

BROM Error(2004).

When i hit download in spflashtool the red bar appears and after that the error.

Please help me solve this problem if it is possible anymore!
[Xperia Z4 Tablet Q&A, Help & Troubleshooting] astrovale:
Hello, just got my Z4 after my old Z just got in the hand of my 2-year old son :rolleyes:

I had rooted and installed a custom rom on that one (CM 12), but I never bothered with Sony own "things" such as the Bravia engine and all.

Now, given that there are not yet any interesting roms for the Z4 and that the developers' scene has never been so active for Sony's products (hence we won't probably see anything interesting for a while, in terms of rom), what are the true disadvantages of JUST rooting the device to install stuff like adaway, titanium backup and the rest of the goodies that rooting allows? Will I lose OTAs by simply unlocking the bootloader and rooting? Since the TA partition will be gone forever, what else are the side-effects of the rooting procedure?

Thanks for any help to a semi-noob.

Luca
[Xperia Z4 Tablet Q&A, Help & Troubleshooting] jelbo:
Apart from the minor Sony stuff that gets lost with the TA partition, I think I read you'll indeed lose the OTA updates abd the only way to upgrade your ROM is with Flashtool (from flashtool.net). Which is also no big deal, really. Just inconvenient, especially on Windows 8+, which you'll have to boot into a mode in which it accepts installation unsigned drivers needed for the tool.

Another potentially big disadvantage is warranty-related, of the bootloader unlocking. Depends on country and vendor.
[Xperia Z4 Tablet Q&A, Help & Troubleshooting] astrovale:
Thanks a lot for your help Jelbo. Don't worry too much about using flashtool (done already). I remember though that there used to be a tool to backup TA partition. I'll look into it, but I guess that, if it's not here....

Never worried about warranty as well. I just hope I'll be lucky, I guess!
[Xperia Z4 Tablet Q&A, Help & Troubleshooting] alex009988:
:crying::crying::crying: Another drawback which I haven't known. Meybe it's more comfortable to use virtual machine with flashtool.
[Xperia Z4 Tablet Q&A, Help & Troubleshooting] jelbo:
Backing up your TA is only possible when you have acquired root on your device without unlocking the bootloader. This is impossible as of now on the Z4 Tablet. Well, technically it might be possible, but no one has found an exploit yet. Maybe one will be found someday, but I wouldn't wait on it.

Haha, don't see things so badly. There's lots to enjoy on the Z4T right now.

Running Flashtool with the flashmode driver in a VM is impossible I think. The driver thing on Windows 8+ is really easy tough.
[Xperia Z4 Tablet Q&A, Help & Troubleshooting] astrovale:
Thanks Jelbo. I went and researched the subject and the first I read was that you need to be rooted to backup your TA partition (indeed I used for my Z the doomlord tool). Well, I guess I'll wait as much as I can, but I really miss adaway most: I hate those ads everywhere cluttering my apps!

Eventually, I'm afraid I'll root and forget about it! I was just wondering also what is the meaning of loosing the bravia engine, but I'll research that too and see. All I know is that I guess I lost it on my Z...but never missed it anyway, so I guess it isnt' that fundamental to enjoy a good tablet like the sony Z4!

Bye

Luca
[Xperia Z4 Tablet Q&A, Help & Troubleshooting] jelbo:
You won't miss the image 'enhancements' that are lost, especially when you care for color accuracy.

A cool thing I found out is that the Z4T supports 'KCAL', which enables you to tweak all kinds of image parameters using a tool like Kernel Adiutor.

Apart from killing ads, the thing I'm second most happy about with being rooted is the ability to permanently hide the soft keys using a build.prop edit, while keeping the ability to type anywhere. I mapped the back and home controls to sliding gestures from the left and right screen edges using a GMD app.
[Nexus 6 Q&A, Help & Troubleshooting] KJSTRIPE:
**Please move thread if needed**

Hi im completely new to this website but have a strange idea that might bring the nexus 6 back to life! It probably wont work but can we add this?:

Cant add links yet..but it is a nexus 5x fingerprint scanner on ebay for 10$ usd

Since android 6.0 supports it itll work software wise i think?

But my main question would be will it connect to the N6?

Also you'd need to mod the back cover to have a hole now i guess.

Please let me know if this is possible

Thanks!
[Nexus 6 Q&A, Help & Troubleshooting] Strephon Alkhalikoi:
Who says the Nexus 6 is dead?

Anyway, what you want to do I don't believe is possible as there is no way to plug the scanner into the motherboard. That's the biggest problem you're going to have. If you can somehow overcome that obstacle, then the rest may be possible as it is mostly kernel drivers, binaries, and Android itself. Personally, I see too much work for too little reward. In the United States, NOT having a fingerprint scanner on your device is actually a good thing, especially if you value your privacy. You're better off using a password or pattern lock, because with a fingerprint scanner, depending on location police in the US can compel you to unlock your phone without a warrant.
[Nexus 6 Q&A, Help & Troubleshooting] carlosjcar:
I read somewhere that they had intended for it to have it but it was axed and that's how we got the Larger Dimple in the Back.
[Nexus 6 Q&A, Help & Troubleshooting] Jaspreet84:
I believe the large dimple at the back is more of a design attribute. Helps in a better stability when holding with a single hand. If I'm not wrong, I've seen it on motog as well.
[Nexus 6 Q&A, Help & Troubleshooting] Gedablo666:
Not really. Nexus 6 prototype had a fingerprint sensor. And maybe here will fit Nexus 5x fingerprint sensor. I made a picture. As we see we dont have where to connect fingerprint. I dont know maybe its hided. I never tried to open back cover and look into it.
[Nexus 6 Q&A, Help & Troubleshooting] Strephon Alkhalikoi:
Ifixit did a teardown of the Nexus 6. The mainboard of production units has no connection for a fingerprint scanner. Now, if there were pictures of the prototype's mainboard available that would help figure out whether there was an actual connector or the scanner was juryrigged. If juryrigged, it may be possible to repeat the process on a production unit.

EDIT: I found additional pictures on Google. It wasn't readily apparent in the pictures above, but the fingerprint scanner was to be part of the upper ribbon cable on production units. So, we have the connector, but there is another issue: how to get the fingerprint scanner to connect to the existing ribbon cable, since you cannot slip two ribbon cables into one connector.
[Nexus 6 Q&A, Help & Troubleshooting] doitright:
My guess is that a fingerprint sensor is *probably* just a simple i2c interface, and maybe an interrupt. Likely those two signals are already on the ribbon cable that is in there. What that means, is that you *might* be able to add it, but it would require a custom made ribbon cable.

More important question though (@OP mainly)... is why would you go to all that trouble? A fingerprint is really NOT a great biometric security feature, they aren't that difficult to duplicate. In fact, a half decent hacker could duplicate your fingerprint by reading your fingerprints off the phone's body and the fingerprint sensor itself.

Its nothing that would "bring it back to life", its just a gimmick. Fact is that Nexus 6 really is still all the way up there by today's standards. It is NOT universally outperformed today's newer phones -- it DOES hold its own against SD810, winning more in benchmarks than it loses. For example, the single-threaded performance of the SD805 absolutely obliterates the 810.
[Nexus 6 Q&A, Help & Troubleshooting] Strephon Alkhalikoi:
[MENTION=6124077]doitright[/MENTION]: I already pointed out to the OP one of the big pitfalls of a fingerprint scanner, that pitfall being police can compel you to unlock your phone without a warrant. The lack of a fingerprint scanner is one reason why I picked the Nexus 6 in the first place, instead of spending lots more money for the 6P. Staying away from the 810 is another. :)
[Nexus 6 Q&A, Help & Troubleshooting] doitright:
You sure about that? What jurisdiction would that be, and what is the written law that supports it? It doesn't sound right, and I can't imagine there being any difference between being compelled on a biometric vs a passphrase... On top of that, of course, is the fact that just because it has a fingerprint sensor, doesn't mean that you need to use it or teach it your fingerprint.
[Nexus 6 Q&A, Help & Troubleshooting] Dusty Rhodes:
http://arstechnica.com/tech-policy/...-a-suspect-unlock-a-phone-with-a-fingerprint/

http://jolt.law.harvard.edu/digest/...s-to-unlock-fingerprint-protected-smartphones

The precedent has been set already, both articles explain why it stood in court. Essentially, they say that your fingerprint is like DNA and can be collected at the crime scene and if it leads to additional evidence, so be it.
[Nexus 6 Q&A, Help & Troubleshooting] doitright:
That's pretty scary, but not exactly the same as what you suggested. In particular, it doesn't look like the police can compel you, since even things like DNA/breath sample/etc., can't just be demanded on a whim, rather this would be compel, as in a judicial order, aka "warrant".
[Nexus 6 Q&A, Help & Troubleshooting] Dusty Rhodes:
Maybe I'm reading it wrong but it says:

A Virginia state trial court held that a suspect “cannot be compelled [by the police] to produce his passcode to access his smartphone but he can be compelled to produce his fingerprint to do the same.”

It doesn't say by the courts but specifically "by the police", but I'm not a lawyer so my chances of being incorrect are pretty high. It just seems to me that they are talking about when someone is a suspect the police are allowed to "compel" you to unlock your device via fingerprint. Either way, it all seems shady as hell.
[Nexus 6 Q&A, Help & Troubleshooting] doitright:
Those article's are *NOT* written by lawyers.

If you read the second one carefully, there is a key in this bit; "Because Baust evidently refused to unlock his phone so that the police could look for the incriminating video evidence, the prosecution filed a motion to compel him to do so.

The court reasoned that the success of the motion turned on whether a passcode or a fingerprint was “testimonial communication” under the Supreme Court’s precedents, concluding that the former was and the latter was not. Judge Frucci therefore granted the state’s motion as to the fingerprints, but not as to the password."

So it was a MOTION TO COMPEL, which was granted by the court. The motion was filed by the prosecution. The police have nothing to do with it except that (a) their demand was initially refused, and (b) they are the ones who would ultimately carry out the order, assuming that it holds up to appeals.
[Galaxy Note II Q&A, Help & Troubleshooting] zetazeta7:
Hi, sorry for my english.I ll try to explain my situation:

1 flash cf-root with odin, it work ok

2 flash twrp with odin and then (my friend suggest me) flash newest bootloader with odin beacouse he want install a newest mod.

Now phone stuk on galaxy note 2 logo at startup.

But there is a big problem, i can go only in download mode and when i try to flash a stock rom odin stops at system.img and don t go...

I tried with kies too but it stops to work at the same

Any idea?

Thank you all
[Galaxy Note II Q&A, Help & Troubleshooting] zetazeta7:
I tried other usb cable and other odin version and all work...
[Galaxy Note 4 Q&A, Help & Troubleshooting] sazasnet:
I am getting 70k score in antutu benchmark, and 30k in standard quadrant. I just got this phone so it's not rooted yet, is it normal or what.

Btw it's snapdragon version

N910f
[Galaxy Note 4 Q&A, Help & Troubleshooting] dkb218:
Antutu who?
[Galaxy Note 4 Q&A, Help & Troubleshooting] prophotoboy:
I've just put a new screen on my mates, and put stock rom on this morning and got 69633 I've now flashe the emotion note 5 rom and overclocked it a bit and its just done 72755
[Galaxy Note 4 Q&A, Help & Troubleshooting] greatgrandking:
Samsung phones usually are Champs on benchmarks but in real world use... They are not as snappy as those benchmarks suggest
[Galaxy Note 4 Q&A, Help & Troubleshooting] valimakik:
Samsungs good old dvfs kicks in when they are benchmarked.
[ZenFone 2 General] ASUS_Khang:
Hey everyone,

I just wanted to let you know that I've taken on a position at a new company. I can't say enough how awesome this community has been...it's incredible - the amount of positive feedback I've received. During my short time here, I really did try my best to help as many people as possible, and hoped that ASUS HQ would provide little unique tidbits of information exclusive to the community here. Things like the Marshmallow update schedule...it's been like herding cats, pulling teeth, (insert another idiom here). Regarding that, by the way, HQ is finalizing the update schedule next month some time, so I hope they release that information publicly.

I really hope people continue to love their ZenFones, and that the community continues to positively contribute and help each other experience the best in their devices. I've been proud to work at ASUS. I know we make great technology - and I know we have parts of the business that we can improve upon. Admittedly, we're not perfect, but really strive to provide the best experience possible.

With all that said, I wish this community the best - I'll be around - Android is my passion, so you'll be able to find me lurking 'round these parts.

Sincerely,

Khanger
[ZenFone 2 General] dasklney:
Good luck with the new job :D
[ZenFone 2 General] Siddk007:
[MENTION=6922370]ASUS_Khang[/MENTION]"Things like the Marshmallow update schedule..., HQ is finalizing the update schedule next month some time, so I hope they release that information publicly"

this just made my day :) hope its true!

btw, thanks for your support all this while.

Good Luck for your future :)
[ZenFone 2 General] android lover 2000:
Whichever company u work for , do your level best and thank you for all the help of being the intermediatery between xda and asus hq.... I wish they were like cm and listened to public with open hearts
[ZenFone 2 General] carloshq:
Good luck Khang!

Enviado desde mi ASUS_Z00AD mediante Tapatalk
[ZenFone 2 General] azthemansays:
Thank you for all you've done for this community, and the best of luck at your new job!
[ZenFone 2 General] jimchee:
Good luck Khang, let us know how you're doing from time to time.
[ZenFone 2 General] quicksilver53:
Best wishes on your next business venture Khang. You will be greatly missed. Cheers Mate.
[ZenFone 2 General] VinzNguyen:
tks u so much. tks for the infomation of MM for zen 2 ^^