yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Q&A, Help & Troubleshooting] gee2012:
Glad it worked out for you and you learned something :)
[Nexus 6 Q&A, Help & Troubleshooting] TTchy:
Is there anything else you think i should do? on my phone ? install twrp etc? Enable usb debugging?
[Nexus 6 Q&A, Help & Troubleshooting] gee2012:
I always enable usb debugging, twrp is only for flashing custom roms, kernels and mods. And in developer options i set all 3 animations from 1 to 0,5 for a bit faster opening of apps and widgets. And sorry for forgetting boot.img, its bedtime for me i guess ;)
[Nexus 6 Q&A, Help & Troubleshooting] TTchy:
It's ok nothing another 5 mins flashing cant fix XD

Good night..
[Verizon LG G4] S1L3nTShaDoWz:
Around 2 months ago it was announced that there was going to be a boot-loader unlock for 10b I think, what ever happen to that? Haven't heard a single word since then, figured there would be more info on that by now or it'd be released.
[Galaxy Note 3 Neo Q&A, Help & Troubleshooting] pankajgera:
Hi guys,

I just updated my note 3 neo with russian rom 5.1.1 from Odin. My phone was rooted earlier but now it has lost root.

I can't install TWRP. I tried things like untick "Auto Reboot" from Odin then manually starting phone but every time I get this message - "Recovery is not Seandroid Enforcing" and then the normal recovery starts.

It would be great if anyone could help me.

Thanks!
[Galaxy Note 3 Neo Q&A, Help & Troubleshooting] GabriF:
Hi, try to follow this guide http://xdaforums.com/note-3-neo/general/recovery-root-root-lollipop-note-3-neo-t3265412 and make sure you have 50% or more battery life
[Galaxy Note 3 Neo Q&A, Help & Troubleshooting] thanhhungtn1:
Mine also showed that message. But after a while the TWRC showed up.

Do it again.
[Galaxy Note 3 Neo Q&A, Help & Troubleshooting] pankajgera:
It worked. Thanks
[Galaxy Note 3 Neo Q&A, Help & Troubleshooting] seyfelislam:
not work

doesn t work for me what is a sollution please
[Galaxy Note 3 Neo Q&A, Help & Troubleshooting] pankajgera:
Make sure you have battery more than 50%.

Untick Reboot in Odin.

Switch off your mobile after flashing TWRP from Odin. Press Home,volume down and power to switch off.

Press Home, Volume up and power to switch on and TWRP will work.

It will work.
[Galaxy Note 3 Neo Q&A, Help & Troubleshooting] patel8888:
running twrp great. if u have any problems pm me
[Nexus 6P Q&A, Help & Troubleshooting] aryehzev:
MTP takes forever and I tried adb pull /sdcard but it was copying at 12mb/s and I have about 60gb of data on my 128gb nexus... so I was wondering if there is a better way... (My laptop ssd writes at 500mb/s and the internal storage shouldn't be slower than a $50 sandisk microsd that reads at 80mb/s)
[Android Q&A, Help & Troubleshooting] Trijunction:
Hi,

When I click on Flipboard articles to read them fully, they render incorrect tlt as shown I the pic. My phone e runs on a custom dpi but I have app setting modules installed and tried Flipboard at different modules. Same issue with any combination. Tired turning off dpi custom setti g sfor Flipboard but still same issue.

Please suggets
[T-Mobile Samsung Galaxy Note 3] Arwym:
Hello,

I recently joined Sprint's network. I am aware that their phones are CDMA-based, unlike T-Mobile's and ATT's, which are GSM-based.

My mother has a Note 3 in good condition that she is getting rid of, and I'd like to keep it; but it's a T-Mobile model, and have been trying to find info. about whether or not the phone can be made to work in Sprint's network after unlocking it.

Any information is greatly appreciated.
[T-Mobile Samsung Galaxy Note 3] pogotv:
No, 2 different types of radios. work with any GSM based carrier like T Mobile AT&T etc but not sprint
[T-Mobile Samsung Galaxy Note 3] Rolatnor:
should work in 2020 as sprint is now owned by tmobile
[Nexus 6 Q&A, Help & Troubleshooting] mwalt2:
[Update]

It looks like you cannot edit build.prop using with the system booted (not sure if it is a limitation of SuperSU or no space left in /system). However, you can edit in TWRP recovery. To get tethering,

adb shell mount /system
adb shell
echo "net.tethering.noprovisioning=true" >> /system/build.prop

You cannot use the adb pull/push because it states there is not enough room in /system. Shell commands seem to work (you can adb pull build.prop and see if the correct changes are there before rebooting, etc).

[Original Post]

I was going to see if Android Pay would still work with SuperSU 2.61 Beta while adding net.tethering.noprovisioning=true to build.prop (read a post on reddit that said it would). I have tried it twice now (flashing the mmb29k image in between) and it just hangs on the Google screen showing lock. Has anyone else run into this? Root works fine.
[Nexus 6 Q&A, Help & Troubleshooting] gregg1ep00:
I had the same symptoms, but after I made a different build.prop change. I used Textdroider to set the DPI to 493, rebooted, and was stuck on the Google logo with lock icon at the bottom.

I was on mra58r prior, with CF systemless-root method (using SuperSU v2.56).

Full steps of what I did to update my rooted, stock kernel, mra58r to mmb29k:

fastboot flash bootloader bootloader-shamu-moto-apq8084-71.15.img

fastboot reboot-bootloader

fastboot flash boot boot.img

fastboot reboot-bootloader

fastboot flash radio radio-shamu-d4.01-9625-05.32+fsg-9625-02.109.img

fastboot flash system system.img

fastboot flash cache cache.img

Reboot into TWRP 2.8.5.0

Flash SuperSU-v2.61-20151207213702.zip with TWRP, which successfully patched boot image for systemless root method

Reboot

Use Textdroider to change DPI to 493

Reboot

Stuck on Google logo

I did not do a full wipe or install userdata.

I'm thinking either a full wipe may be required (which I doubt), or perhaps the bootloader loads some kind of checksum on what it thinks system ought to look like, and if they don't match, it hangs? Just a stab in the dark there... but something certainly seems to be causing the system to hang when booting with a modified build.prop.
[Nexus 6 Q&A, Help & Troubleshooting] mwalt2:
I tried a full wipe with the same result. I guess at least it's not just me :p
[Nexus 6 Q&A, Help & Troubleshooting] gregg1ep00:
I just flashed back to mra58r, flashed everything (including bootloader), then did systemless root... Gonna see if modifying build.prop works and will post results.

---------- Post added at 11:25 PM ---------- Previous post was at 11:13 PM ----------

I should also note that I am running encrypted with passcode on startup (corporate email policy).

[MENTION=1589124]mwalt2[/MENTION] did you flash the bootloader for mmb29k as well, or just the system image?

---------- Post added at 11:49 PM ---------- Previous post was at 11:25 PM ----------

Well, the phone boots, but I'm getting spammed with "the process com.android.phone has stopped" repeatedly. I think I updated some sort of Google service when I was in 6.0.1, which means that updated process is still on the phone and it's incompatible with 6.0... or something.

I was, however, able to successfully set DPI with Textdroider back on mra58r while feverishly trying to clear the com.android.phone message, and it booted just fine.

Going to try and update system and radio to 6.0.1 without updating bootloader or boot.img... Stay tuned...
[Nexus 6 Q&A, Help & Troubleshooting] MILH0U5E:
Did you have to wipe to get it to boot back up?
[Nexus 6 Q&A, Help & Troubleshooting] yamahakid:
Same issue. Thought it was something I did, glad I checked here before trying it again.
[Nexus 6 Q&A, Help & Troubleshooting] gregg1ep00:
No, I flashed everything back to mra58r, using the same method I posted for updating to mmb29k. I did *NOT* wipe or flash userdata. But like I said, com.android.phone was extremely unhappy when it came back up. I am doing everything I can to not wipe userdata, because I *really* don't feel like dealing with reinstalling everything.

I just flashed system, radio, and cache only from mmb29k and it's in the process of optimizing apps now. Once it comes up, I'll report on how com.android.phone is behaving, and will also set DPI, reboot, and let you know if it hangs again.
[Nexus 6 Q&A, Help & Troubleshooting] MILH0U5E:
So using the boot.img in the Systemless SU 2.61 caused the battery bugs for me... I just clean flashed with the boot.img from the Google image, and everything is fine now.

Now, figuring out what things will play nice with this new SU...
[Nexus 6 Q&A, Help & Troubleshooting] gregg1ep00:
Well, looks like it's either system or radio that doesn't like build.prop edits, and it's probably not radio.

After flashing radio, system, and cache from mmb29k (using bootloader and boot from mra58r, with CF SuperSU v2.61 systemless root method), system booted just fine. Root was fine. The com.android.phone issues went away, and Textdroider had no issue with setting my DPI to 493. So first of all, it looks like whatever Google service got updated when I booted into 6.0.1 the *first* time is incompatible with the com.android.phone process in 6.0.0.

Unfortunately, I am now sitting at a Google logo with a lock screen at the bottom.

The next thing I'll try is reflashing the stock boot.img and see if maybe the 6.0.1 system image will only boot if a stock boot.img is present. If that doesn't work, it looks like I'll be reflashing mra58r and wiping userdata.

---------- Post added at 12:58 AM ---------- Previous post was at 12:42 AM ----------

Hrm.... This is interesting.

What I did:

Reboot into bootloader

fastboot flash bootloader bootloader-shamu-moto-apq8084-71.15.img (from mmb29k)

fastboot reboot-bootloader

fastboot flash boot boot.img (from mmb29k)

fastboot reboot

I was then presented with a nice little message notifying me that my device was untrusted and would not boot. Lovely.

Back into the bootloader we go...

fastboot flash bootloader bootloader-shamu-moto-apq8084-71.15.img (from mmb29k)

fastboot reboot-bootloader

fastboot flash boot boot.img (from mmb29k)

fastboot flash radio radio-shamu-d4.01-9625-05.32+fsg-9625-02.109.img (from mmb29k)

fastboot flash system system.img (from mmb29k)

fastboot flash cache cache.img (from mmb29k)

fastboot reboot

This got me into the stock 6.0.1 (after briefly telling me AGAIN that my device was untrusted), but of course I was no longer rooted. I then rebooted and chose recovery, and to my surprise, TWRP was gone...

fastboot flash recovery openrecovery-twrp-2.8.5.0-shamu.img

fastboot reboot-bootloader

Select recovery with volume buttons and went in

So now I'm sitting at recovery options... Going to try original CF root method with modifying system to see if that works to obtain root.

EDIT: that didn't work. Thinking about options now, as device won't boot at all. If I can get back to where I was earlier, with mra58r, even if I have to wipe / reload, that's better than where I'm at.... LOL
[Nexus 6 Q&A, Help & Troubleshooting] gregg1ep00:
I ended up going back to 6.0.0 by flashing everything from mra58r again, along with a full wipe. No issues so far. I'll wait to update to 6.0.1 until we hear from the devs.
[Nexus 6 Q&A, Help & Troubleshooting] gregg1ep00:
Since I had already wiped the device, I figured I didn't have much to lose by going back to 6.0.1 (mmb29k) and trying all this again.

Flashed bootloader, boot, radio, system, and cache of mmb29k using method described above, then reinstalled TWRP at the end. Rebooted into TWRP, wiped data, and installed SuperSU v2.61. Reboot into system, and root was just fine.

Just out of curiosity, I decided to attempt setting up Android Pay. To my surprise, it worked fine...

Not sure what conclusions to draw from this.

Note, I have NOT modified build.prop in any way, and I'm very hesitant to try at this point.
[Nexus 6 Q&A, Help & Troubleshooting] f2:
I flashed 6.0.1 at least 5 times today and tried different ways to gain root. Although Root Checker always says I was successful, I was never able to change the DPI setting of the phone without running into trouble.

For now I give up and will wait until a dev comes up with a solution ....
[Nexus 6 Q&A, Help & Troubleshooting] gregg1ep00:
Yeah, it definitely seems that modifying build.prop causes the "hang at Google lock screen" issue. What really surprised me was the fact that I was able to set up Android Pay without any trouble, with root. The only thing that was different from my previous failed attempts was that I wiped data. So perhaps something in data was old or weird and was causing issues with Android Pay?
[Nexus 6 Q&A, Help & Troubleshooting] mwalt2:
Android pay works fine with the new beta supersu. I wanted to see if it still worked with a modified build.prop. I wasn't hopefully, but couldn't even boot after adding a line to build.prop.
[Nexus 6 Q&A, Help & Troubleshooting] NLBeev:
Same here. I needed to wipe caches, data and system with TWRP.

Flashed the lite rom 6.0.1 of Danvdh and let G. restore the apps with the setup wizard.
[Nexus 6 Q&A, Help & Troubleshooting] Brotuck:
Edited build.prop with root explorer, reboot and only the logo stayed

I could copy the build.prop.bak back to build.prop and it booted fine again.

So no space isn't the issue here, i guess a validation check ?
[Nexus 6 Q&A, Help & Troubleshooting] Danvdh:
here is a workaround that actually is probably better then editing a build.prop while the system is active

open ROM zip you just downloaded or want to use in 7-zip and navigate to system folder

copy build.prop to desktop

open build.prop in notepad++ and make your edits

Copy your edited build.prop and overwrite the stock build.prop in your ROM zip (drag it and drop it with 7-zip!)

Flash and enjoy what you want on first boot ;)

same can be done for ringtones and notification sounds ahead of time ;)
[Nexus 6 Q&A, Help & Troubleshooting] gregg1ep00:
Confirmed, I was able to change ro.sf.lcd_density using this method, and upon reboot it did not get stuck on Google logo. After booting into TWRP:

adb shell mount /system
adb shell
cp /system/build.prop /data/build.prop.bak
echo "ro.sf.lcd_density=493" >> /system/build.prop

Awesome job [MENTION=1589124]mwalt2[/MENTION] !
[Nexus 6 Q&A, Help & Troubleshooting] mwalt2:
Most of us of us are stock and flashing images with fastboot. That will work great for custom ROMs though.
[Nexus 6 Q&A, Help & Troubleshooting] gregg1ep00:
I may have spoken too soon.

The file is updated, but for whatever reason the change doesn't seem to have taken effect. Textdroider reports that the density is 493, but it doesn't LOOK like 493... Any ideas?

UPDATE

Looked at build.prop again, there's already a line with ro.sf.lcd_density=560 in there, so more than likely, my additional line at the bottom didn't take effect.
[Nexus 6 Q&A, Help & Troubleshooting] f2:
Does not work for me! The DPI setting is still the same.

And the Battery % is broken now.
[Nexus 6 Q&A, Help & Troubleshooting] gregg1ep00:
I even tried editing in place with sed:

sed -i -- 's/560/493/g' /system/build.prop

And it gave me a write error, saying there was no space left.

---------- Post added at 11:35 AM ---------- Previous post was at 11:34 AM ----------

@f2 yeah, the line gets added to build.prop, but see my previous post (#20), there's another lcd_density line in there, so my guess is the second one has no effect.

We need a way to edit this in-place somehow.
[Nexus 6 Q&A, Help & Troubleshooting] gregg1ep00:
Alright... Just found this:

http://stackoverflow.com/questions/11421955/running-vi-in-adb-under-windows

Downloaded PuTTYtray v020 as suggested, rebooted into recovery, and launched PuTTYtray in ADB mode. Used vi to modify build.prop, set ro.sf.lcd_density=493, saved, rebooted, and it works. My DPI is indeed set at 493.

If you've never used vi before, it's way different from notepad... do some googling for basic commands and how to do stuff. :)

---------- Post added at 03:25 PM ---------- Previous post was at 03:22 PM ----------

What would be really cool is if we could get rid of that line altogether and import /data/local.prop or something, so we can safely make modifications to build.prop without actually having to touch it again.
[Nexus 6 Q&A, Help & Troubleshooting] mwalt2:
Yeah, it seems there should be a way to change it without modifying /system. You can symlink the hosts file, so it seems it may be possible to do something similar with build.prop. Android Pay works fine with the tether edit.
[Nexus 6 Q&A, Help & Troubleshooting] BinaryW01f:
Okay, okay, trying to do this at work and my brain is fried, doing this via the terminal and I keep getting "sh: adb: not found" what am I doing wrong, TWRP 2.8.7.1
[Nexus 6 Q&A, Help & Troubleshooting] snot:
Worked great for me!!!! Thank you, I've been working on/looking for a fix since I flashed the update 2 days ago! Working great, on tethering now.
[Nexus 6 Q&A, Help & Troubleshooting] tabormeister:
THIS FIXED MY EVERYTHING on 6.0.1 on the Nexus 5, totally stock save tethering and TWRP. So stoked. Thanks a million.

EDIT: actually my everything is still broken on Sprint. Have systemless root and twrp, android pay works, have net.tethering.noprovisioning=true in build.prop (with a space between it and the end but still) and no tether. Hotspot kicks on but can't pull an IP on laptop.
[Nexus 6 Q&A, Help & Troubleshooting] jdogg3982:
what worked for me was fastboot install everything, boot to twrp, install su2.62. then I couldn't edit build prop in es file explorer because it kept saying no space when I tried to save. so I deleted/uninstalled some of the system Google apps (like play games) and then I was able to save changes to build prop. tethering and custom dpi changes in build prop are working.

now I want to test Android pay, although I should mention I did a dirty install from 6.0.
[Nexus 6 Q&A, Help & Troubleshooting] ManHands:
If all you're looking to do is enable tethering in build.prop, here's a different way to accomplish this without tripping Safety Net. Therefore, you can still use Android Pay or any other app that checks if /system has been modified. I'm using the latest SuperSU 2.62-3 systemless root.

Create a script in /su/su.d. Call it whatever you like (i.e., 0000tether.script), and add the following line...

setprop net.tethering.noprovisioning 1;

Set permissions to 775, reboot, done. I did all this within Solid Explorer. You should be able to use any root file explorer that's compatible with systemless root. Or of course, adb can be used as well.

Hopefully this helps some. If so, please let me know if you know of, or can find a way to do something similar for pixel density. I tried several different variations in the same script to modify ro.sf.lcd_density to no avail. And of course, without tripping Safety Net so Android Pay can still be used.
[Nexus 6 Q&A, Help & Troubleshooting] Princesation:
OK... So I was able to add the line to build.prop yesterday using twrp. But now I can't do it anymore. I think I just got lucky last night... Can someone provide a more detailed step by step? Thanks.
[Nexus 6 Q&A, Help & Troubleshooting] istperson:
Systemless root doesn't require permissive kernel, and without permissive kernel you can't remount system as rw.

Also there is no space left on the system partiion, it's filled to the brim.

You can mount system in TWRP and then you can delete things from the system/app that you don't need.
[Nexus 6 Q&A, Help & Troubleshooting] Ratamacue:
Thanks!
[Nexus 6 Q&A, Help & Troubleshooting] interloper:
Sprint tether win!

In a running system I did "adb shell", "settings put global tether_dun_required 0" then I did adb reboot bootloader>fastboot flash recovery recovery.img>fastboot reboot bootloader then chose reboot recovery with the hard buttons. Then I did "adb shell", "mount system", and " echo "net.noprovisioning=true" >> /system/build.prop"

Exit

adb reboot

Tethering works fine on Sprint with the not trustable message on boot. Speed was nice, no throttling.
[Nexus 6 Q&A, Help & Troubleshooting] saryon1:
This worked on my VZW nexus 6 running 6.0.1 Thank you!
[Nexus 6 Q&A, Help & Troubleshooting] framerate:
I tried all night to get to this to work on 6.0.1 and kept getting "device is corrupt" message followed by black screen. I'm on AT&T.

I ended up flashing manually everything from 6.0.0 and did the stuff in the first step (echo into build.props) and tethering is enabled.

Has anyone had real luck with 6.0.1 and if so, how did you do it exactly?
[Nexus 6 Q&A, Help & Troubleshooting] istperson:
On 6.0.1 there is not space on system, you can't modify the build.prop. You just mess it up and if fails to boot. Why don't you modify (or create if it's missing) /data/local.prop?
[Nexus 6 Q&A, Help & Troubleshooting] framerate:
I'm not familiar with local.prop. I'm a linux guy, but fairly new to the android FS.

Does local.prop override build.prop? If so, why has nobody else tried that? haha
[Nexus 6 Q&A, Help & Troubleshooting] istperson:
Yes it's supposed to override the build.prop which should be left alone, since it tells us what settings were used to build the rom.

So, try it then, and tell us the result. ;)
[Nexus 6 Q&A, Help & Troubleshooting] ManHands:
Because it doesn't work. That's why.
[Nexus 6 Q&A, Help & Troubleshooting] istperson:
You're a bucket of helps. Since when, and why?

---------- Post added at 11:02 PM ---------- Previous post was at 10:56 PM ----------

But the grumpy stranger is right. local.prop only works on userdebug and eng builds.

So dive in system/app delete some bloatware, and then modify your build.prop.
[Nexus 6 Q&A, Help & Troubleshooting] ManHands:
Yeah, I usually test something prior to posting claiming something works. It doesn't work on 6.0.1 on a N6.

No clue. Just read about it last month when testing systemless SuperSU 2.6.2-3. Maybe it worked on prior versions or other phones; but, it doesn't on this phone and this OS version.

---------- Post added at 04:10 PM ---------- Previous post was at 04:04 PM ----------

Or just simply create a script in su/su.d.

setprop net.tethering.noprovisioning 1;

No need to delete apps and modify system partition.
[Nexus 6 Q&A, Help & Troubleshooting] istperson:
Well, I believed [MENTION=6124077]doitright[/MENTION], he was very convincing. And it haven't worked for about four years now.

https://android.googlesource.com/pl...dbda7e1c5bcebc501b4943cd6483122297e1834^!/#F0

"Don't read /data/local.prop on user builds

Creating a root owned /data/local.prop is one of the most common

ways to root an Android device. /data/local.prop is only intended

to assist developers on debuggable devices, and is never

intended to be used on production devices."

---------- Post added at 11:20 PM ---------- Previous post was at 11:10 PM ----------

So you do have a more recent solution that's supposed to work. Why didn't you start with this?
[Nexus 6 Q&A, Help & Troubleshooting] ManHands:
Didn't feel I needed to repeat myself since it's a few posts back. But, I guess I did.

http://xdaforums.com/showpost.php?p=64281346&postcount=30
[Nexus 6 Q&A, Help & Troubleshooting] istperson:
No you didn't, obviously. And you could have helped without repeating yourself.

You do know that local.prop is a method that works on AOPS builds that are built as userdebug as default. And it worked for me last time I checked, before I switched to user build myself. So when [MENTION=6124077]doitright[/MENTION] said it will work on stock I believed him, so shoot me, I deserve it.

But you still didn't help the guy who asked how to modify build.prop on 6.0.1, and not how to add to the su.d. In the Q&A thread.
[Nexus 6 Q&A, Help & Troubleshooting] tabormeister:
Did this, no dice. On Sprint with a Nexus 5 stock rooted with systemless 2.64 and twrp, build.prop has a space at the end and then net.tethering.noprovisioning=true, and no device can pull an ip from my phone when tether is active, usb bluetooth or wifi. Tried your su/su.d script and still no dice. What am I missing? Is there an APN step?
[Nexus 6 Q&A, Help & Troubleshooting] ManHands:
If editing build.prop directly isn't working for you, the su.d script definitely will not. I'm on VZW, so that may be the difference.

[MENTION=839943]interloper[/MENTION] confirmed this method worked for him on Sprint.