yashsingh1/xdaforums huggingface dataset:
[Verizon Motorola Droid Turbo General] pandimus:
Just not sure if it's a good enough upgrade over droid turbo considering its smaller with a smaller battery. Although it has an awesome camera and a fingerprint sensor
[Verizon Motorola Droid Turbo General] koftheworld:
Smaller battery, but much better battery management. The phone also has seamless upgrades, which you only get with a native nougat phone. Additionally you have monthly security updates and os upgrades for 2 years. regardless of what is said in this area, it is a legitimate upgrade over the turbo. Go to the store and try it out. That's really the only way to tell.
[Verizon Motorola Droid Turbo General] pandimus:
I just opted to keep my droid turbo. Sunshine has opened up the lifespan of it. So I'll probably hang on to it for another generation of phone.
[Google Pixel Questions & Answers] FrostedWaffle:
So I was helping a friend with his Pixel he bought from the Google Store. He wanted to install the new update. However, when I took a look at his build number, it was NDE63X not NDE63V. I remind you that he bought his phone directly from Google and not from Verizon. I do remember that when he set it up and put his Verizon sim in, he had to uninstall a couple Verizon apps. Could this have anything to do with him being on the wrong build? Also how can I get him off the Verizon build? Can I just sideload the NDE63V OTA or do I have to use a factory image?
[Google Pixel Questions & Answers] atlp99:
The November update sent X to google store phones if they had a Verizon sim in them.

Same thing here, play store device but on Verizon, when the OTA pushed it was X.
[Google Pixel Questions & Answers] kenjoma:
If we bought a phone from Google, have a Verizon sim, and are on build nde63x, can we and should we push a different build? Also, can we push the new build?
[Google Pixel Questions & Answers] dbrohrer:
You can flash another build, but there isn't a reason to. Only reason I can think is relevant right now is you want to get to the new ota that got pushed to Canadian phones for the new features. In that case you would need to move to the nde63v build, then sideload ota. If you're not doing that, then there is no reason.

If you are concerned with the "Verizon Pixel vs Google Pixel" discussion, then you have bought into the internet hype. Tsst. Your Google store Pixel is identical to a Verizon Pixel. There is a server side whitelist / blacklist that gives users the ability to toggle oem unlock or not(based on CID I think). That is all. Firmware (nde63x vs nde63v) is independent of where you bought the phone from or whether you can unlock your bootloader. Nde63x likely has some minor changes in it that Verizon and Google think will work better on their network (wifi calling changes, advanced calling tweaks, or something else). Pop a ATT or Tmobile sim in your phone and you will eventually be prompted to update to the unlocked build. Pop your VZW sim back in and it will try to go back. No big deal.
[Google Pixel Questions & Answers] charklos:
I have a bl unlocked Verizon Pixel, flashed the V build over P, then sideloaded the Canadian J build just for the new features. Now I'm on J with root and unlocked bl on Verizon. ;). So yeah, you can do whatever you want.
[Google Pixel Questions & Answers] FrostedWaffle:
So just to be clear (cause I don't wanna **** up my friend's phone) I can side load the NDE63v OTA on the NDE63x pixel? Or do I have to use some other method?
[Google Pixel Questions & Answers] dbrohrer:
No. I haven't tried it myself but others reported side loading 63v from 63x errors out. YMMV on that. The otas that are available are good for moving from a certain build to another. Not any build to 63v. I don't think you can get the ota that takes you from 63x to 63v.

If it was my friends phone, I would flash the factory image if you want to move to the other build. Edit the flash all script so it doesn't wipe data if he wants to keep apps and settings.
[Google Pixel Questions & Answers] FrostedWaffle:
OK thank you I will try that.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] hotstocks:
So I bought a refurb Note 4 and odin flashed it to latest marshmallow. Rooted/twrp and restored my image from my defective old one. Well everything worked except I lost my finger print sensor. So went to twrp and deleted

password.key

pattern.key

locksettings.db-wal

locksettings.db-shm

locksettings.db

Then I could get back into the phone, but still when trying to register fingerprint I get the error message and can't enter them. So I said fine, I will just odin flash stock and factory reset and start fresh. Well I have done that and the phone dialer *#0*# diagnostics sensor shows fingerprint reader as NULL, I lost the version # and all functionality. So I odin flashed the previous two stock T-mobile Note 4 images, factory reset and still even when starting from scratch now the fingerprint sensor is NULL and doesn't work. So I figured somehow I got a defective fingerprint scanner, I returned that phone, got another one that had kitkat and the fingerprint scanner worked. I flashed it to Marshmallow and now the same thing. I am pulling my hair out. How can software stock flash ruin my fingerprint sensor? How do I get it back? I am willing to flash any odin image/factory reset to do this and then just need to know what NOT to do so it doesn't happen again. There is no way both phones have a defective fingerprint scanner, so it is something that persists even AFTER an odin stock flash and factory reset?? Any help would be appreciated. The only other thing I noticed that I don't know what it means is on first boot it said something about no have DRK. Please flash ENG binary then install DRK. What is DRK? How do I install it, and will it get my fingerprint sensor working again?

Thanks in advance for any guru help.

P.S. I think the problem is I used my broken glass Note 4's twrp/nandroid image to restore the new phones, and I overwrote everything. My guess is the new phones where fingerprint sensors don't work have the old phones EFS, and I have no backup of the new phones EFS. I am only guessing this is the problem as I am newbish about EFS. I just don't see why I can't odin flash any version of T-mobile rom and get back to a REAL factory reset, not some partial one where things don't work. Help please.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] Trex888:
Flash n910t2 kitkat firmware in odin this will work 100% with n910t have a look post below.

http://xdaforums.com/note-4-tmobile/general/news-want-to-downgrade-to-4-4-4-kitkat-t3447773

Once flash firmware do wipe data factory reset and wipe cache

Once finish setup at homescreen let the phone rest for few minutes then reboot

Next go check fingerprint scanner.

Once it works go ahead and flash regular n910t marshmallow firmware.

Drk is ( device root key ) i believe your device is rooted before and efs partition+imei is modified and when you tried to flash official firmware things went wrong somehow.and i don't see any working method to fix drk the only fix for drk is replace entire motherboard.

Download link for n910t2 firmware link below

https://mega.nz/#!bZ8nFIaA!u67ewIWGe8HRtI8-OdxFUPoXFvpACIKhtQtbnv7KU18

If this method does not work go ahead and download n910t 5.1 1 repair firmware with pit file from www.tsar3000.com and flash with pit file maybe it will work.and then go take ota update of marshmallow.

My best suggestion will be get rid of this device now dont waste your time and money and get new device instead of refurbished.

report back please.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] hotstocks:
First method didn't get fingerprint scanner back. And I cant find the n910t 5.1 1 repair firmware with pit file from www.tsar3000.com could you please link me to that file so I can try method #2?

Also is there anything special I should do in Odin like check boxes for Nand Erase All or Phone EFS Clear?? RE-partition? Anything that would get this back to completely erased and stock so fingerprint sensor software gets re-installed. in dialer *#0*# sensor fingerprint it went to null when it used to say a version, so wherever that software for the fingerprint scanner is stored is where my problem is.

Thanks
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] hotstocks:
I found the pit file elsewhere. Can I use that pit file with the firmware I just flashed, and if so how? Or do I need to find the www.tsar3000.com n910t 5.11 repair firmware, because I can't find it anywhere on their site or I am just stupid? Please link to it and instructions, never flashed a pit.

Well I managed to get the pit and firmware to flash in an older odin, newer ones failed. But still when you dialpad *#0*# and go to sensors and down to bottom where finger print scanner is, it says NULL instead of a version and the test doesnt work. When you go to fingerprint scanner in the phone to register fingerprints it just keeps saying Attention an error has occured with fingerprint sensor, reboot.

I find it impossible to believe that there is no way to get the fingerprint sensor software/test back. I have done this on two phones so I KNOW the fingerprint sensor hardware works. Some bad EFS or rom flash lost the fingerprint sensor software and there must be a way to get it back. There is nothing wrong with the hardware of these two phones, it happened on a 910T and 910T3 both due to TWRP restoration of all checked boxes. Please help, I can flash anything from odin or twrp, SOMETHING has to re-install the fingerprint sensor software/dialer sensor info.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] hotstocks:
I also heard that the Samsung Experience at some Best Buy stores could fix these kind of issues, like they have a machine to REALLY overwrite all of the phone or something? I just don't see how odin flahing the firmware wouldn't do that, unless I need to check that Nand erase box or do something else? Please help or let me know if Best Buy kiosk is worth a shot.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] Trex888:
Sorry but tsar3000 removed n910t repair firmware

I'll give you pit file for 6.0.1 marshmallow

Flash 6.0.1 firmware with pit file in odin choose nand erase all

Choose pit file in pit tab in odin as in screenshot below.

But i highly suggest you return this device.

Good luck

https://mega.nz/#!yE0QkRgR!8DvGvAauRkb-2xmtH_3ZluoYwCvqNaaSOnXMLYB_CAI
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] hotstocks:
Thanks I will try that. As far as returning it, I really can't and I got it for a great deal $150 and it is literally brand new, the screen is perfect, ect. I somehow was an idiot and used my old twrp file to flash the new phone because I didn't want to re-set up everything. Well I checked every box in twrp for the backup and restore. Even though they are the same exact model phone I think it somehow did something to the fingerprint scanner firmware and I still can't figure out why it won't come back. I tried it with two seperate phones that both did this, but other than the fingerprint scanner not working the phone is mint and runs perfectly, any rom. I will probably just keep it without fingerprint sensor if we can't figure this out, it is not like I even use it and this is my backup phone (have an LG V20). It is very annoying, but mainly because it should just work and doesn't. There is no way a flash can fry a fingerprint scanner and make it's software disappear, but this happened twice on two different phones after I did the twrp restore from my previous Note 4 T with all boxes checked. I didn't know you shouldn't check all backup boxes in twrp. Nevertheless it should go back to factory and isn't. GRRR

P.S. I'm wondering if flashing some other totally modified rom would install the fingerprint software again, maybe something like cyanogen? I have been out of rom flashing scene. If you think any might please link me.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] hotstocks:
I found this, and it seems to be the fix for my problem, except I don't understand step 5 (and obviously I have a N910T and N910T3 to fix) also SmartSwitch just freezes, you can never flash anything with it, so I will use Odin for that, I assume it does the same thing. Still haven't got the fingerprint sensor back and have done everything but step 5. Any other ideas or explanation of step 5 would help. Thanks.

Found a solution if anyone ever stumbles across this thread.

How it happened:

I did a full Twrp backup, including EFS on a n910T. I received a replacement n910t. I thought I could restore the twrp backup from the old straight to the new n910t. I was wrong. EFS is device depending and contains the individual phone info like imei,S/N,etc. Basically my new phone took characteristics of the old one and the EFS became corrupted. My fingerprint sensor didn't work and I had the "dm-vertiy verification failed. If the dm-verity fails, finger print sensor won't work.

How I repaired my EFS, or what I did to get it to work. Your mileage may vary.

All of this on stock rom: I got the stock from by using smart-switch and doing emergency recovery, entering my model number and serial number. I then cf rooted and flashed twrp using odin.

1. I check to make sure my IMEI and S/N numbers stored in the phone (about device) matched the sticker on the back. My IMEI matched but my S/N did not. My S/N was from my old phone, big whoops!

2. I corrected my S/N by editing the serial number file found under your EFS folder. You need root access to edit it. I use room toolbox lite, root browser to edit it.

3. Because my EFS became corrupted, my phone was in limp mode, eg it was slow and lagging, it was stuck in "factory mode".

4. I took the phone out of factory mode. Again you need root access and root browser. Go to EFS folder/factoryapp/factorymode and edit the file. Change it to off. Also go to efs folder/factoryapp/keystry and turn it off also. Reboot.

5. I entered this command:

mke2fs /dev/block/mmcblk0p13 (for N910G Note 4)

mkdir /efs

mount -t ext4 /dev/block/mmcblk0p13 /efs

6. Do a factory reset, reboot system

7. I then did a stock firmware flash again with smart-switch. Everything works again now. This time I will make sure I back up my efs but don't try to restore it.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] hotstocks:
Can someone with a T-Mobile Galaxy Note 4 N910T3 that has a TWRP backup INCLUDING the EFS please upload that and give me a link. I screwed up my EFS and if someone with the same phone could please make and upload their TWRP backup (just with EFS box checked very small and not your data) for me it would be greatly appreciated. I know I will have to go into it and edit my serial # from yours, but it should get me back working.

Thanks
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] Trex888:
Efs backup from another device will never work because it's related to your phone's specific hardware.

You did big mistake that you flash backup and efs from old phone to new one that completely screw up your efs partitions and drk ( device root key ).

Sorry but you should make always efs backup from twrp in microsd card before start messing with phone. Cuz flashing always risky job.

Trust me odin or twrp will not going to help you.

Dont waste your time You should go to repair center cuz they have tools like dongle box to fix efs and imei.

They will write new cert files and restore your efs but i dont think they can fix drk cuz i see many drk damage cases but didn't see any working method unless changing entire motherboard.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] hotstocks:
Thank you. I have been doing a lot of research, and an EFS TWRP file from the same exact model N910T3 would work if I flashed it and then went in and edited that serial # to my phone's serial #. It sucks that I did not have a backup of EFS in TWRP and now no matter what rom I flash, wipe, ect, I can not get my fingerprint sensor back. In dialer *#0*# sensor it went to NULL from a version and it doesn't work at all, just get the error when trying to register fingerprints. I read that someone fixed this exact problem by getting a TWRP of just the EFS, flashing it, then editing the serial #'s, so I wanted to try that. But need a TWRP EFS uploaded for N910T3 as I can not find one anywhere. Unless you have another idea. I mean the phone works fine other than the lack of fingerprint sensor, but I think it is also in no verity and factory mode whatever that means. I posted the fix above that worked for someone, but once again I don't have the TWRP EFS and I don't understand how to do part 5. There has to be a way to either entirely wipe everything including EFS and getting my phone back to factory new thru Odin or TWRP flashing an EFS and changing serial # to my sticker # so I can get the damn fingerprint sensor working. I think the problem is I have a N910T EFS on my N910T3 which allows everything to work except fingerprint sensor.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] hotstocks:
Thanks. What is DRK and if I go to repair center does it even matter if they can't fix drk but they get the fingerprint sensor working with new EFS dongle? Also are you talking about a local T-mobile store or some Samsung repair center that I have to mail the phone to and pay a lot? Can you link me to repair center in USA Michigan or how to find one? Thanks again
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] Trex888:
Sorry i dont live in usa no ideas

if you have warranty you go to samsung or go to any local repair shop.

Tell them all issues and hopefully they will fix.
[Xperia Z5 Q&A, Help & Troubleshooting] mossywell:
E6683 (import from Hong Kong)

Had it for about 4 months.

Battery was on about 96%.

Then I decided to try a different ROM (was trying MWA 2.0) so I powered it off and that was the last of it.

What I have tried:

-power + vol up (for 2 minutes)

-power + vol down for 30 seconds

-power + vol up and down for about 30 seconds

-vol down + usb

-vol up + usb

-the reset button next to the SIM for 5 seconds

None of this works - it is totally dead. I've read that the sudden death on Xperias is a known issue thought I've never experienced it myself. Do I now have a brick?
[Xperia Z5 Q&A, Help & Troubleshooting] DeathStroke:
When you power on, does the sony logo come or not?
[Xperia Z5 Q&A, Help & Troubleshooting] mossywell:
Power on? LOL. That would be nice!

No, when I say it is "dead" I mean no vibration, no lights - nothing. What I'm struggling with is whybis happened so suddenly. Literally powered it off as I have done a million times and it just never came back on.
[Xperia Z5 Q&A, Help & Troubleshooting] erikcas:
oops...... looks like your emmc is fried... throw it under your bed for two days, then press all four buttons (cam + volup + voldown + power) + the poweroff button in your simslot for a minute or so (donot remember exact time) and after that attach usb. It might start (i.e. start charging and the led lights up) but I am afraid it will not... I just had that a while ago and I had to have my mobo replaced. Which kernel is used by that rom?
[Xperia Z5 Q&A, Help & Troubleshooting] mossywell:
Cheers m8 for your help - really appreciate it.

Kernel was Z5-DSDS_Sunkernel_Permissive_v253_corona_III.1_9_4_2_sum_dual.zip (I've not had any issues with Zach's kernels before. Could it really be the kernel?)

Anyway, I will ignore it for a few days the then try the "press every button" trick. If it is fried, I will probably put it on Ebay as Dead / For Parts. Someone might be interested in popping in a new mobo!
[Xperia Z5 Q&A, Help & Troubleshooting] HaoZeke:
So in such conditions... Have you tried fastboot?

For me, inspite of it not working or turning on or anything holding the volume up and connecting it to the computer got the blue fastboot led
[Xperia Z5 Q&A, Help & Troubleshooting] mossywell:
Of course. See OP.
[Xperia Z5 Q&A, Help & Troubleshooting] mossywell:
MAJOR PROPS to YOU! Thank you!

I left it unplugged for a whole week. Then I pressed power + vol up + vol down + camera for 2 minutes. The I plugged it in and BINGO - a red charge light. :D

I've since gone back to 253 stock (Singapore) as that was my trusty ROM. But at least I now have a phone again!
[Xperia Z5 Q&A, Help & Troubleshooting] erikcas:
Cool!

Verstuurd vanaf mijn F5121 met Tapatalk
[LeEco Le Pro3 Questions & Answers] ericerk:
Where can I find LES3 roms?
[LeEco Le Pro3 Questions & Answers] HewettBR:
Maybe start in the Le S3 forum?
[LeEco Le Pro3 Questions & Answers] ExTREmE99:
Le S3 = Le 2. theres an entire device forum for it
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] Sammichezzz:
Hi there.

I have had nothing but bad luck with phones and rooting, especially the s5 g9000v.

I recently bought a pre-rooted s5 off ebay, and everything was great. It came with TWRP and XPOSED, but the screen exploded.

I bought a new one with Alliance pre-installed, and tried to flash XPOSED. It is now stuck in a bootloop on the alliance animation, and I can't get into the custom recovery at all (TWRP) to clear the Dalvik cache.

I did not have Dev Options checked when I did this, like an idiot, and now ODIN and ADB won't work because:

1) ODIN gives me a "Failed Auth message (See below)

<ID:0/005> Firmware update start..

<ID:0/005> recovery.img

<ID:0/005> NAND Write Start!!

<ID:0/005> FAIL! (Auth)

2) ADB won't recognize the device to fast reboot or any fun tricks. (See Below)

C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices

List of devices attached

I Have tried:

-Wiping Cache partition (Nothing happens)

-Factory Resetting in recovery and basic mait. boot mode(Nothing)

-Download Mode and then cancelling out (Nothing)

All return to the endless cycling Alliance screen.

IS there anyway to write something or turn Dev options on to save the phone?

IS there anything I haven't done that I can do to fix this? I fully understand I'm an idiot, I got ahead of myself after a glass of wine and flashed with no back up or plan if it decided to fudge up.

I literally had it 15 minutes. :crying::crying::crying:
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] Sammichezzz:
Nevermind. Loaded back to PB1 on ODIN and will reflash.

Don't Drink and Flash Y'all.
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] hauckk@sfreserves.org:
Yeah sounds like a good idea ?

sent from my nexus 4 I also own a voyager tablet and an I-phone 4s

---------- Post added at 04:45 PM ---------- Previous post was at 04:44 PM ----------

But yeah odin is the way to fix bootloops if you can't boot into rom or custom recovery

sent from my nexus 4 I also own a voyager tablet and an I-phone 4s