yashsingh1/xdaforums huggingface dataset:
[Nexus 6P General] borisb:
That's a crazy deal.

I got mine from NewEgg 25$ gift card but the phone cost 550.

I got a protection plan with no deductibles for 50$. B&H has one but it's 70$ per accident.

So over all 575 vs 525.

I never bought from B&H before but new egg has really good support. They sent me a second phone right away one day delivery when I called and said I have a scratch out of the box on the screen.

---------- Post added at 07:59 PM ---------- Previous post was at 07:47 PM ----------

Prices at new egg just dropped to 499 and 39 for protection plan. Plus 25 gift card.
[Nexus 6P General] adam_pl:
I paid ~700$ on french amazon in January for 64GB variant. You Americans are so lucky bastards
[Nexus 6P General] JUSTINMARMER:
I just pulled the trigger on this deal. Got the graphite (black) 32gb model with Speck TPU case. After taxes it came to $466.33. I'm pretty dang happy right now. It will be available for pickup from my local bestbuy on the 17th. I'm upgrading from my Galaxy S4 (AT&T), so I'm guessing I'll need to run by my local AT&T store to get a different sim.
[AT&T Samsung Galaxy S6] glasseffects:
I recently updated the Indian varient of G920i to 5.1.1 and attemped to root by flashing Unikernel. Seems like that had been the moment the phone would not stop from bootlooping with the Samsung Logo and a red text that reads "Kernel is not SEAndroid Enforcing" The "arter97-recovery-g920fi-12.0-twrp_3.0.0-0.tar" recovery works but it can't mount an OTG. The only relief was I could now power down the phone.

Is there any way I can restore the phone and root?

Please help!
[AT&T Samsung Galaxy S6] s629c:
You posted in the wrong area. This is for the AT&T Galaxy S6 G920A. Now, the solution would be using Odin to flash back to stock which you will find the files in the forum for the G920i

Edit: http://xdaforums.com/showthread.php?t=3086387 this should help you
[AT&T Samsung Galaxy S6] glasseffects:
schhy

Thank you! I have ben able to recover the device and install arter97 recovery. However the recovery does not mount OTG in the absence of which I wont be able to restore any backup should the internal system fails.

PS: I request the Moderators to please move this thread to the S6 general section since I need some help to resolve some issues.

Thanks.
[Nexus 6P Q&A, Help & Troubleshooting] in3ssi:
Noticed recently after I unlock the phone there is some sort of Asian text at the bottom of the screen and I'm unsure how to get rid of it. If anyone has any ideas let me know ?

Currently running pure nexus slightly older version but still 6.0.1
[Nexus 6P Q&A, Help & Troubleshooting] ripv2:
I see your running Lockout security and assuming it didnt find any malware. When did this start happening?
[Nexus 6P Q&A, Help & Troubleshooting] Heisenberg:
It's from one of the apps that you have installed.
[Nexus 6P Q&A, Help & Troubleshooting] AndyYan:
Chinese here. The text roughly says "Keeping the last screen state: on/bright".

Dunno what this actually means, but check for any app that might be of Chinese origin, even if the app displays in English.

Sent from Google Nexus 6P @ CM13

[WARNING: XDA One have not implemented "mark forum as read" - do not use]
[Galaxy Tab S2 Q&A, Help & Troubleshooting] mankvl:
Mine is not working. Googled a little bit and found out that after root SM is not working. The only fix was adding additional line to build.prop. Source here http://xdaforums.com/tab-s2/help/screen-mirroring-t3241344 but this didint helped ?

Anyone with rooted Tab S2 can confirm that screen mirroring is working? BTW I use debloated ROM, maybe SM needs some app to work?
[Galaxy Tab S2 Q&A, Help & Troubleshooting] danyvw:
SM-T810 rooted with NN-J kernel, SM working flawlessly but with the build.prop line added.
[Galaxy Tab S2 Q&A, Help & Troubleshooting] mankvl:
Did you add that line at the end of the build.prop file? Or somewhere else?
[Galaxy Tab S2 Q&A, Help & Troubleshooting] danyvw:
At the end of the build.prop
[Galaxy Tab S2 Q&A, Help & Troubleshooting] mankvl:
Lol just had to reboot and it's working ☺
[ZenFone 2 Q&A, Help & Troubleshooting] mastermarkofroms:
So as of recent I have noticed both my mom and dad who both have samsung galaxy core's can't phone me? it just forwards them to voicemail but they can phone anyone else and I can recieve calls from anyone else I have looked and they are not in my blocklist witch makes no sense to me. I am able to phone out as well. I am with Virgin Mobile and they are on Wind. Also I have entered *#21# and made sure call forwarding was disabled and it is. Any ideas? I am so confused
[Galaxy Note5 General] Mr A:
Good news SA people. Finally Have the marshmallow update :D

http://www.sammobile.com/firmwares/download/66940/N920CXXU2BPBA_N920COJV2BPBA_XFE/
[Nexus 7 (2013) Q&A] bl4cKz4cK:
Hello everyone,

usually I was able to solve almost any issue with android devices by myself, simply by doing some searching here on the forums and via google. But this time it seems like that I've screwed things up big time, since I couldn't really find anyone having the same issue as I have.

My device is a Nexus 7 2013 LTE. It's unlocked and was running rooted with a custom ROM before, without any real issues. Since I traveled a lot with it, I was using the encryption as well. After I tried wiping the device, things went south. At first TWRP was unable to decrypt the data (?) partition but that was due some outdated version which I got fixed by installing the most recent version of TWRP (3.0.0.0) via fastboot. Unfortunately The device doesn't boot into the OS anymore but at the same time, I can't wipe any of the existing partitions using the TWRP GUI and I haven't even bothered trying to flash any ROM on the device.

Here are some logs:

Updateing partition details...
...done
Unable to mount storage
Full SELinux support is present.
Data successfully decrypted, new block devices: '/dev/block/dm-0'
Updateing partition details...
...done
Unable to mount storage
Unable to mount /data/media/TWRP/.twrps
Failed to mount '/data' (Invalid argument)
MTP Enabled
Failed to mount '/data' (Invalid argument)
Failed to mount '/data' (Invalid argument)
Failed to mount '/data' (Invalid argument)
Failed to mount '/data' (Invalid argument)
Failed to mount '/data' (Invalid argument)
Failed to mount '/data' (Invalid argument)
Failed to wipe dalvik
Updating partition details...
...done
Unable to mount storage

I feel like I messed up the partitions or something but I'm not quite sure if that's actually the case. And even if so, wouldn't know how to fix that. If there is any more information I can provide to make troubleshooting easier, I'll gladly do so.

Any help would be highly appreciated, thank you very much.
[Nexus 7 (2013) Q&A] k23m:
All you need is:

run: fastboot format userdata

run: fastboot reboot

wait for the long first OS start
[Nexus 7 (2013) Q&A] bl4cKz4cK:
Thanks for your reply!

I tried that out, unfortunately without any success.

root@TECRA:~# fastboot devices
0876df52	fastboot
root@TECRA:~# fastboot format userdata

formatting 'userdata' partition...
FAILED (command write failed (Bad file descriptor))
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
root@TECRA:~#
[Nexus 7 (2013) Q&A] k23m:
Interesting, note...

fastboot format userdata
Creating filesystem with parameters:
Size: 28856791040
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7045115
Block groups: 215
Reserved block group size: 1024
Created filesystem with 11/1761280 inodes and 154578/7045115 blocks
erasing 'userdata'...
OKAY [ 19.767s]
sending 'userdata' (139085 KB)...
OKAY [ 4.797s]
writing 'userdata'...
OKAY [ 5.985s]
finished. total time: 30.564s

Please post the output of fastboot oem gpt-info
[Nexus 7 (2013) Q&A] k23m:
I see, go TWRP - Wipe - Format Data ('...removes encryption...')
[Nexus 7 (2013) Q&A] k23m:
No worries at all. We could use mke2fs but CWM can do it faster.

download CWM to your folder with fastboot app

boot N7 in fastboot mode

run: fastboot boot recovery-clockwork-touch-6.0.4.3-flo.img

in CWM select mount and storage

do format /data and format /data/media

This should fix it :good:

Note - we're not flashing new recovery, CWM is only temporarily booted
[Nexus 7 (2013) Q&A] bl4cKz4cK:
Thanks again for your continuous support, I really appreciate that.

I gave CWM a go and did the steps you posted. This time there was no error message, however, when I booted back into TWRP, it still asked me for the encryption password. :(
[Nexus 7 (2013) Q&A] k23m:
This is getting serious. Let's check now fastboot format userdata - still with errors?

Then please extract "recovery.img" file from your preferred stock factory image or just download this LMY48T

Run fastboot boot recovery.img and do factory reset from it.
[Nexus 7 (2013) Q&A] k23m:
Well, how did it go?

I checked TWRP source code and noticed a bug in the Wipe_Encryption() function:

partition.cpp

} else {
string Command = "flash_image " + Crypto_Key_Location + " /dev/zero";
TWFunc::Exec_Cmd(Command);
}

"flash_image" does not work with "/dev/zero", it insists on a real image file. We can fix it manually from adb shell.
[Nexus 7 (2013) Q&A] bl4cKz4cK:
I'm currentyl trying the first thing (fastboot format userdata) and it's still going, since like two hours. I'm gonna leave it running for the night, just to make sure. If that won't work I'm gonna give the stock recovery a go tomorrow.
[Nexus 7 (2013) Q&A] bl4cKz4cK:
Not too well :/
[Nexus 7 (2013) Q&A] k23m:
It's OK, just more clean up to do.

Please boot TWRP and run these commands in the following order:

adb shell dd if=/dev/block/platform/msm_sdcc.1/by-name/metadata of=/md
adb shell dd if=/dev/block/platform/msm_sdcc.1/by-name/misc of=/mc
adb shell tar cvzf mm.tgz md mc tmp/recovery.log
adb pull mm.tgz mm.tgz

You will find mm.tgz in your adb app folder, attach it to your next post.

Next adb reboot bootloader

Wait and run: fastboot format cache

I need to see the mm.tgz file before the next step. In the meantime you could try stock recovery reset again but this time use LMY48T from my earlier link.
[Nexus 7 (2013) Q&A] k23m:
Instead of ADB you could use a scripted zip run from USB OTG. Let me know if you prefer this option and I'll prepare it for you.
[Nexus 7 (2013) Q&A] bl4cKz4cK:
Sorry for the late response, I had little free time to look into this.

For some reason, it doesn't boot int TWRP anymore. I tried to "fastboot boot twrp-3.0.0-0-deb.img" but it gets stuck and never goes past the loading screen. Bootloader still works but neither flashing nor booting a recovery was any successful.
[Nexus 7 (2013) Q&A] k23m:
Please extract 'recovery.img' from a stock factory image and check if fastboot boot recovery.img works. Download and try twrp-2.8.6.0 because the newer versions are unreliable for me too. What are the error messages when you are flashing? Did you flash a stock image?
[Nexus 7 (2013) Q&A] BanBoo:
I think I got the same issue... solved it by install a factory image from here.

https://developers.google.com/android/nexus/images#instructions

After that I wiped data and cache via stock recovery. Worked for me
[Nexus 7 (2013) Q&A] bl4cKz4cK:
Okay I've tried the following:

Booting twrp-2.8.6.0 via fastboot boot -> works

Booting stock recovery via fastboot boot -> works

However, trying to flash the stock recovery (just like any other recovery) failed.

sending 'recovery' (8188 KB)...
OKAY [ 0.281s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 90.059s

After that I tried to use the dd commands you posted prior.

C:\>adb shell dd if=/dev/block/platform/msm_sdcc.1/by-name/metadata of=/md
dd: /dev/block/platform/msm_sdcc.1/by-name/metadata: I/O error

C:\>adb shell dd if=/dev/block/platform/msm_sdcc.1/by-name/misc of=/mc
dd: /dev/block/platform/msm_sdcc.1/by-name/misc: I/O error

Finally I tried to flash the stock image using the flash-all.bat:

sending 'bootloader' (3911 KB)...
OKAY [ 0.141s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.561s
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: 0.016s
sending 'radio' (76038 KB)...
OKAY [ 2.524s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 92.572s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters:
Size: 28521246720
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6963195
Block groups: 213
Reserved block group size: 1024
Created filesystem with 11/1741488 inodes and 153337/6963195 blocks
Creating filesystem with parameters:
Size: 587202560
Block size: 4096
Blocks per group: 32768
Inodes per group: 7168
Inode size: 256
Journal blocks: 2240
Label:
Blocks: 143360
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/35840 inodes and 4616/143360 blocks
--------------------------------------------
Bootloader Version...: FLO-04.05
Baseband Version.....: DEB-Z00_2.44.0_0213
Serial Number........: 0876df52
--------------------------------------------
checking product...
OKAY [ 0.000s]
checking version-bootloader...
OKAY [ 0.016s]
checking version-baseband...
OKAY [ 0.000s]
sending 'boot' (7442 KB)...
OKAY [ 0.250s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 90.054s
Press any key to exit...
[Nexus 7 (2013) Q&A] k23m:
It's time to have a look at your hardware log:

boot TWRP

connect PC

run: adb shell dmesg > dmesg

find 'dmesg' file in your adb folder

attach it here or upload to http://pastebin.com
[Nexus 7 (2013) Q&A] bl4cKz4cK:
There you go.
[Nexus 7 (2013) Q&A] k23m:
Thanks!

<6>[ 3.601959] mmc0: new HS200 MMC card at address 0001
<6>[ 3.603149] mmcblk0: mmc0:0001 MMC32G 28.8 GiB

<3>[ 9.120544] mmc0: CMD25: Data timeout
<6>[ 15.914215] mmc0: CMD25: Request timeout

<3>[ 17.073242] end_request: I/O error, dev mmcblk0, sector 3031112
<3>[ 17.073455] Buffer I/O error on device mmcblk0p23, logical block 9
<4>[ 17.073760] lost page write due to I/O error on mmcblk0p23
<3>[ 17.074127] end_request: I/O error, dev mmcblk0, sector 3031120
<3>[ 17.074493] Buffer I/O error on device mmcblk0p23, logical block 10
<4>[ 17.074798] lost page write due to I/O error on mmcblk0p23
<3>[ 17.074981] end_request: I/O error, dev mmcblk0, sector 3031128

<3>[ 17.082916] mmcblk0: error -110 sending status command, retrying
<3>[ 17.088836] mmcblk0: error -110 sending status command, retrying
<3>[ 17.094482] mmcblk0: error -110 sending status command, aborting
<3>[ 17.094818] end_request: I/O error, dev mmcblk0, sector 3031040

Unfortunately it is a typical log of a defective eMMC flash memory:

MMC32G 28.8 GiB is a Kingston chip

mmcblk0: error -110 is the hardware error logged by other bricked N7s too

I/O error, dev mmcblk0 just confirms it
​

Your emmc log is more 'alive' than other bricked N7s and that is why, perhaps intermittently, you were able to do more with it than others. The encryption removal issue simply coincided with hardware failure. Encryption, decryption, wipe and flash, rewrite almost entire 28GB every time and trigger failures of poorly manufactured flash memory. I am sorry, I have to add your Kingston to the bricked stats.
[Nexus 7 (2013) Q&A] bl4cKz4cK:
Well, rest in peace I guess. Is there a way of repairing it (cost effective) or should I just forget about it and bury the thing in the backyard?
[Nexus 7 (2013) Q&A] k23m:
Nexus 7 is a great tablet, still manufactured and sold. Get a new one and keep this for spares. The cheapest repair option so far is this ebay listing. Two months ago it was $30, then $25 and now $27.

:good:
[Droid Turbo 2 General] blkhrt13:
So my turbo just updated to marshmallow, and I'm curious as to whether that opened the door to root and possibly bootloader unlock. BTW the Moto x force thread needs to be moved from this one. They're 2 different phones. I mean they're the same, but anything on Verizon is always going to be different. We all know this. Chime in guys!
[Droid Turbo 2 General] mjones73:
Too soon to tell if it opened up any possible exploits, best thing is to keep an eye on this thread - http://xdaforums.com/droid-turbo-2/general/root-discussionthink-tank-t3239979

The X-Force question came up before, mods said it's basically the same phone so it's not getting it's own section.
[Droid Turbo 2 General] imnuts:
If anything, it patched a bunch of exploits and made it that much harder to root the phone. Unless Motorola does the same thing as they did with the one Moto X on Verizon, I doubt the bootloader will ever be unlocked.

Sent from my DROID Turbo 2
[Droid Turbo 2 General] jayman94fly:
I feel like this could happen one of 4 ways.

1. Good ol diggin round code.

2.Motorola employee helps us.

3.someone me (I've tried) but both Motorola reps and Verizon reps are unhelpful but someone might do better. Maybe get it " escalated"

4. Just hope....

Also I just really think it's possible to get past the people who know nothing about it and find someone willing to help.. Then again maybe just simply wishful thinking.
[Droid Turbo 2 General] tonyc0642:
^^^This. Whoever has had success cracking BLs on Verizon Moto devices in the past might help, or at the very least point you in the right direction. You also might be able to get some of the CM devs that have worked on VZW Moto devices in the past.
[Droid Turbo 2 General] blkhrt13:
I know Verizon has been notorious about locking their phones down for a while now, but can it really be completely locked? There has to be something there that can be cracked right? Nothing is impossible right?
[Droid Turbo 2 General] Digital DJ:
Hey, guys, I haven't checked in for awhile, but would someone be willing to work on it for a bounty? I mean if we could pool together somewhere between $500-$1k wouldn't it be worth it for someone who has a ton of knowledge in this comeover and help?

I'd be willing to donate to that cause even though my sig says otherwise...
[Droid Turbo 2 General] jayman94fly:
Same here I second that, seems the hard part would be setting this up, I mean this is a great phone if devs would come on board
[Droid Turbo 2 General] Blubbking:
Rooted and installed twrp KINZIE today. Followed a italian tutorial for the Moto X Force. Android 6.0

http://www.androidiani.com/forum/mo...moto-x-force-ottenere-i-permessi-di-root.html

I would pay too if somebody hopped on the developer train for the X-Force !
[Droid Turbo 2 General] Digital DJ:
You rooted your droid turbo 2?
[Droid Turbo 2 General] bigv5150:
No he has the moto x force it's confusing they shouldn't be posting in this thread they can root this is about obtaining a root exploit. To be honest I don't care that he rooted his phone it's not such a triumph the damn phone is unlocked.
[Droid Turbo 2 General] Digital DJ:
That's what I thought. Still not sure why the mod won't separate the threads. It gets stupid and confusing...
[Droid Turbo 2 General] tonyc0642:
There is a bounty thread started in Q&A

http://xdaforums.com/droid-turbo-2/help/root-droid-turbo-2-bounty-t3339484
[Droid Turbo 2 General] SecretPotatoChip:
I want to change the ugly, unintuitive material design soft buttons.

I know that verizon locks down their phones.

I want to root so that I can get back the old Holo soft buttons (ics, jelly bean, kitkat) and maybe holo blue.

I know from experience that root can make a device much more laggy.

This is my main and only phone that I can use, so I don't want to take many chances.
[Droid Turbo 2 General] bigv5150:
Who told you root makes a phone lag that is 100% false. Anyway there is no root method at this time.
[Droid Turbo 2 General] SecretPotatoChip:
I have a droid razr that I rooted in jelly bean. Since that, it's more laggy and unresponsive. Probably because of the root processes running in the background
[Droid Turbo 2 General] Zeljko1234:
There is no such thing as "root process". Root is just about rights to access particular part of the system, run specific commands or applications.
[Droid Turbo 2 General] mjones73:
He is asking for an X-force developer (since there's a lack of roms) so gonna say no.
[Droid Turbo 2 General] jayman94fly:
Yea he just doesn't know what he's talking about here, maybe he installed something that was eating away at the CPU or RAM or both, also may have been a bad root method to
[Droid Turbo 2 General] Zeljko1234:
Maybe he's talking about supersu...
[Droid Turbo 2 General] mjones73:
That isn't because you rooted it. The base crap on the phone already runs/is owned by root, by default you're locked out to touch them.
[Droid Turbo 2 General] johnboggs6661:
remove motox from turbo 2

i agree. im new and im confused enough already and at first assumed that if was on the turbo 2 page it was all inclusive. thank you, john
[Droid Turbo 2 General] robsharp78:
The developers are learning from the cracks and the systems are just getting better. It might get to the point where they can't crack it.
[Droid Turbo 2 General] ChazzMatt:
Because once phone is unlocked and rooted, all Kinzie phones can use the same ROMs.

Look at what happened with the Droid Turbo forum. All Quarks were in the same forum. Droid Turbo was locked down, Moto Turbo and Moto Maxx was not. Droid Turbo owners were jealous of all the dev work. Forum got split. Two months later, exploit was found to unlock Droid Turbo bootloader.

Now they have to trek over to the Moto Maxx (Quark) forum for most everything.

Guess what? Several Droid owners have petitioned to merge the forums back!
[Droid Turbo 2 General] bigv5150:
We'll if we get unlock then merge them back seems simple enough right.
[Droid Turbo 2 General] ChazzMatt:
Been six months since bootloader unlock and still hasn't happened for the Quarks. Forums still split.

I think the mods have more important things to do. And I don't blame them. Droid owners wanted the split, now they have to live with it.

All the Turbo users have to go to the Moto Maxx forum for the good stuff.
[Droid Turbo 2 General] Zeljko1234:
Yeah but it's pretty pointless first to bug admins to separate then later on to merge. Xda members should be able to read and understand the first post in the topic. In most cases is enough to just read subject for which device is custom rom, firmware, etc.
[Droid Turbo 2 General] Digital DJ:
Yeah I didn't realize all that. Thanks for the information.
[JASJAR, XDA Exec, MDA Pro General] WackMachine:
Hi,

I noticed that when playing games (specifically, classic console emulators) I cannot press more than one key at a time. For example, if I press forward then jump the forward gets canceled.

Note: I want to play games that I actually own. I just want them mobile.

Is there a way to fix this with software? (driver, patch whatever)?

Thanks.
[Samsung Galaxy S7 Edge Questions and Answers] cristy78:
I have this error : Game Launcher has stopped. anyone else got this?

I don't know why is happening.

Same error I have with Samsung Members app.

anyone knows a fix ?
[Samsung Galaxy S7 Edge Questions and Answers] Ithicka:
I got the same error. :( I'm actually trying to find out as well. Lol unfortunately new phones will have bugs to work out....I just hope it's soon
[Samsung Galaxy S7 Edge Questions and Answers] brianthangathurai:
Go to Settings -> Applications -> Application manager -> more -> apps that can appear on top. Set it on enabled and manually enable it for Game Launcher. Worked for me!
[T-Mobile Samsung Galaxy S7 Edge Questions & Answer] blah_blah_blah_blah:
Samsung has a new promotion that if you make a successful purchase with samsung pay you get a $30 dollar gift card from a variety of retailers including best buy so hurry and make your purchase lol
[T-Mobile Samsung Galaxy S7 Edge Questions & Answer] XxKINGxX2580:
Bank of America Debit cards not eligible? :/
[T-Mobile Samsung Galaxy S7 Edge Questions & Answer] jrock79:
Neither are USAA cards :(
[T-Mobile Samsung Galaxy S7 Edge Questions & Answer] rodnii:
BoA debit isn't eligible, but the credit card from them is ? Just got an eBay gift card!