Just to make sure there's no confusion, of course I understand that both unlocking and re-locking the bootloader result in a factory reset and all of my data stored on the phone will be lost if not otherwise backed up.
My question is about the hardware side of things. I know over the years some phones have been configured such that they lose DRM keys or other data when unlocked, which can not be backed up and thus result in permanent loss of software and sometimes (Sony Xperia Cameras) even hardware features.
Does OnePlus do anything like this on the 6T?
I totally get that if I'm rooted and/or running a custom ROM I may have issues with DRM, SafetyNet, etc while running a modified system. All of my previous Android devices have been rooted and ended their useful lives running CM/LOS versions 2-3 revisions beyond OEM support, I'm familiar with how that goes. My question is if I decide to go back to stock does everything go back to normal or is anything lost for good?
wolrah said:
Just to make sure there's no confusion, of course I understand that both unlocking and re-locking the bootloader result in a factory reset and all of my data stored on the phone will be lost if not otherwise backed up.
My question is about the hardware side of things. I know over the years some phones have been configured such that they lose DRM keys or other data when unlocked, which can not be backed up and thus result in permanent loss of software and sometimes (Sony Xperia Cameras) even hardware features.
Does OnePlus do anything like this on the 6T?
I totally get that if I'm rooted and/or running a custom ROM I may have issues with DRM, SafetyNet, etc while running a modified system. All of my previous Android devices have been rooted and ended their useful lives running CM/LOS versions 2-3 revisions beyond OEM support, I'm familiar with how that goes. My question is if I decide to go back to stock does everything go back to normal or is anything lost for good?
Click to expand...
Click to collapse
Just unlocking the bootloader shouldn't cause issues other than with a few apps such as Netflix streaming level. Rooting Will cause issues with Safety net and some apps although using magisk hide and random app name settings does a pretty good job of getting around that
unlocking the bootloader disables the encryption of filesystem, thus the phone will be wiped clean. So yes, you will lose anything not backed up.
intrusdave said:
unlocking the bootloader disables the encryption of filesystem, thus the phone will be wiped clean. So yes, you will lose anything not backed up.
Click to expand...
Click to collapse
This is partially wrong, unlocking the bootloader does not disable the encryption. It does wipe your phone clean though.
Unlocking the bootloader will cause you to loose Widevine L1 so Netflix and any other app that relies on this will not be able to play HD content, just as jestyr8 said.
Jager said:
This is partially wrong, unlocking the bootloader does not disable the encryption. It does wipe your phone clean though.
Unlocking the bootloader will cause you to loose Widevine L1 so Netflix and any other app that relies on this will not be able to play HD content, just as jestyr8 said.
Click to expand...
Click to collapse
Exactly, but this is reset if the boot loader is relocked, so it's not a permanent change, in answer to the OP query.
Sent from my ONEPLUS A6013 using Tapatalk
Thank you all, and yeah I don't care what I lose while running a modified system as long as I always have the option to just flash back to stock and make everything normal again if I want.
edit: Just to be clear about the Netflix thing, that means I lose some of the higher resolution options when playing on the device itself, right?
A few years ago one of the updates to the Netflix app made it just straight up stop working on my Note 4, even as a Chromecast controller.
I really don't care all that much either way because I basically never watch on my phone and all my main TVs have Fire Sticks or other devices with remotes and Netflix clients, but sometimes Chromecasting is the most convenient option so it'd be moderately annoying to lose that again.
wolrah said:
Thank you all, and yeah I don't care what I lose while running a modified system as long as I always have the option to just flash back to stock and make everything normal again if I want.
edit: Just to be clear about the Netflix thing, that means I lose some of the higher resolution options when playing on the device itself, right?
A few years ago one of the updates to the Netflix app made it just straight up stop working on my Note 4, even as a Chromecast controller.
I really don't care all that much either way because I basically never watch on my phone and all my main TVs have Fire Sticks or other devices with remotes and Netflix clients, but sometimes Chromecasting is the most convenient option so it'd be moderately annoying to lose that again.
Click to expand...
Click to collapse
Chromecast seems to work in most ROMs.
Related
Since release 2 of the N dev preview, I've really been pretty impressed with the stability and features, especially multi-windows. I seem to use that on a daily basis, either referencing 1 window while I do something on another window, or just 1/2 watching some vid while I do something else. The size of the Pixel C seems to work well with the multi windows, I have the feature on my 6P rom but don't use it anywhere as much.
The quick tiles and notifications are also decent. Usually the very 1st thing I do id unlock and root, but I've felt no need to do so. The apps I use have all worked, I know some folks had issues with some.
Also, the OTA install was also excellent, as easy as it gets.
How are you all liking N?
I'm really getting on with it, too. I think the testament to the OS is that it seems a bit more intuitive. Much like you were saying about not rooting, I don't feel the need to with the Pixel C at this point.
I also enjoy the fluidity of the OS in comparison to MM, it just seems smoother.
Does the OTA update from stock 6.0 work?
Does it still wipe all data from the tablet?
thanks
ghostbustaj said:
Does the OTA update from stock 6.0 work?
Does it still wipe all data from the tablet?
thanks
Click to expand...
Click to collapse
I'm wracking my brain to try and remember if it wiped my data and I just can't remember. Sorry.
Here is what I did; I signed up for the dev beta, then took the upgrade more or less like an OTA from 6.0 and it worked great! No flashing, nothing. Heck I didn't even put in a custom recovery. It took a little to download and install. I just can't remember if it asked me to restore all my apps and I said yes or it was still there.
I'm pretty sure it would say something about deleting all your data, but again I'm just not remembering. If you get it, please come back and let us know.
NJ72 said:
I'm really getting on with it, too. I think the testament to the OS is that it seems a bit more intuitive. Much like you were saying about not rooting, I don't feel the need to with the Pixel C at this point.
I also enjoy the fluidity of the OS in comparison to MM, it just seems smoother.
Click to expand...
Click to collapse
Thats a good point about the OS being as fluid as it is, very true. I can't wait to see the release version and what if anything else is added.
ghostbustaj said:
Does the OTA update from stock 6.0 work?
Does it still wipe all data from the tablet?
thanks
Click to expand...
Click to collapse
The beta program wipes data completely. It is like a typical fullvwipe or in HTC terms, a RUU.
I think I didn't have a full wipe when I changed to N.
Gesendet von meinem Pixel C mit Tapatalk
ghostbustaj said:
Does the OTA update from stock 6.0 work?
Does it still wipe all data from the tablet?
thanks
Click to expand...
Click to collapse
AFAIK the OTA doesn't wipe your data. Flashing via fastboot wipes. They also started releasing flashable zips beginning with Dev Prev 2, which also don't wipe. Idk if you can just flash that zip over Marshmallow.
as to the OP query, I like it a lot. I'm impressed by the options and, much more so, by the stability.
Sent from my Pixel C using XDA-Developers mobile app
I needed to revert because mtp file transfer didn't work. Also every time I connected the tablet on adb it was immediately forcefully shutdown and couldn't start until I plugged the cable.
Other than that, I didn't find an option to enable usb tether....but then again I didn't find this option in marshmallow (afterwards)...what the **** google?
Oh and mtp is also extremely unreliable back on marshmallow. I don't know what the **** they did with this tablet. I believe I will jump on the next tablet bandwagon if I happen to see one....
OTA to Android N is non-disruptive. The way back is.
I have many issues with Android N but cannot go back because of the full wipe.
I hoped that I will be able to use non tablet apps in the half screen mode but that does not work. I am loosing sound when disconnecting headphones. Some apps crash. You Tube cannot specify quality setting, public wifi hot spot without Internet connectivity drains battery quickly.
I regret my decision of installing Android N.
tfojta said:
OTA to Android N is non-disruptive. The way back is.
I have many issues with Android N but cannot go back because of the full wipe.
I hoped that I will be able to use non tablet apps in the half screen mode but that does not work. I am loosing sound when disconnecting headphones. Some apps crash. You Tube cannot specify quality setting, public wifi hot spot without Internet connectivity drains battery quickly.
I regret my decision of installing Android N.
Click to expand...
Click to collapse
There was way too many non compatible apps for my liking with N. Firefox would always crash, widgets wouldn't work with certain apps, I'd get random freezes, the Youtube app seemed jacked kinda, and overall...I thought the tablet seems LESS responsive. I switched back to MM.
Dude, all you have to do is back up all your data to Google (you can enable it in the Backup & Restore) Drive. When you opt out of the Beta it sends you an OTA file for MM. When it uninstalls N and reinstalls MM it literally finds the fact that you reset your tablet back to MM and re-installs everything for you. It worked flawlessly for me last night. Wasn't a pain in the butt in the slightest.
Actually at the end I reverted back to Android. You are right that all apps are automatically reinstalled however they are not configured, and you loose any local data.
I'm running Android N and want to use Smart Lock, but whenever I try setting Smart Lock or a trusted device, location, etc, it says I can't utilize Smart Lock because my device is encrypted. I've never setup encryption, and I can't remove encryption either. I can't even activate OK Google from any screen, and it's all because of the encryption. Is this a mandatory feature of Android N?
Has anyone got OK Google to work on all screens and lockscreen?
Google N is good but this is a preview issue so there's a fair few bugs within, e.g. YouTube crashing, low benchmark scores, dual screen having limited functionality and random error codes when opening apps.
I've reverted to MM and the process was super simple.
I'll wait for the third iteration and see if that irons out these issues, but N is very promising and I feel it'll really help release the potential of this tablet.
I just ordered my tablet and it shipped today. I was wondering if it is worth updating to Android N right away or stick with marshmallow
Stick with mm if u seek stability
Sent from my D6603 using Tapatalk
I'm enjoying it but where is the May stability update?
It worked well for me. Only real problem I had was app compatibility. Use it as a media device, so HBO GO, Hulu, TNT, etc crashing on me led me to revert. Can't wait for N to be finalized and apps to be made compatible with split screen.
Any one have this issue? I am on 5.0.2 and Netflix keeps crashing. When i choose a movie it loads and "Bamnn" Netflix tvq-pb-103 (2.10.0.1004) https://help.netflix.com/fr-ca/node/57683
I cleaned up cache and data, logout and reboot... Same problem.
Hi, are you using a type of VPN?
Are you DNS from ISP or your using custom ones?
Enviado desde mi Moto X mediante Tapatalk
Sorry i should say TVQ-PB-103 (2.10.0.2104)
No VPN and no custom DNS.
I called Netflix they looked lost about this error. After all the cache and data clearing for this app still no go. They asked me to do a full reset... 2 hours later finish setup the box, no change. Netflix Still gave me the same error.
Hmm, if you haven't touched router settings, then try rebooting both your modem, router and Shield TV, in that order. 30-30-30 reboot cycle.
I have experienced issues with some apps I have installed in the past that could cause some misbehaviours, so if you tested Netflix right after the factory reset then a bad app should not be the culprit, but if you restored some apps before testing Netflix then check your apps and start uninstalling suspicious apps.
Have you read this:
https://forum.xda-developers.com/an...s905x-help-mi-box-3s-mdz-19-aa-t3521362/page9
I wonder if it's network, bad app or bad update/flashing perhaps? problem.
Enviado desde mi Moto X mediante Tapatalk
Nvidia shield is fresh not a single app added.
tried the Netflix update and still no go.
I Tried reboot the router and plugged the shield tv to an other TV. Change 2.4 to 5 ghz still not working.
TVQ-PB-103 (2.10.0.2104)
I search on the net and i can't find this code. Some one know what it's mean?
Did you try the app from the link I posted below?
https://help.netflix.com/en/node/24776
Does it work?, at least does it play videos?.
You have Android TV OS right, are you rooted? It would be good if you could take a debug log.
How about upgrading to Nvidia experience 5.1 and test again.
Sent from my Tapatalk Hub ~
If I helped hit the Thanks! button, Follow Me or Buy Me a Coffee: https://bit.ly/pptome
I did and it's worked but like you said image quality is really bad. I am not sure it even 720p and all zoom in, no menu.
I tried wireless 2.4 and 5.2 and wired, i changed to 720p tv, i tried onkyo 4k amp. Hook up to 1080p Toshiba 1080p tv. Reboot and cleared multiple times but Still not good.
I going to reset my router or update it tonight and test again.
allcius said:
I tried wireless 2.4 and 5.2 and wired, i changed to 720p tv, i tried onkyo 4k amp. Hook up to 1080p Toshiba 1080p tv. Reboot and cleared multiple times but Still not good.
I going to reset my router or update it tonight and test again.
Click to expand...
Click to collapse
OK but before you update your router, try just changing DNS to google DNS: 8.8.8.8 and 8.8.4.4
It would be absurd but probably your ISP has enabled some restrictions so that is something very simple that might help.
How is your network setup?. Do you have a modem-router provided by your ISP plus your own router or just 1 router?
Test with nothing in between. Plugged in directly to your main router or even better to your modem to troubleshoot.
~ Sent from my Tapatalk Hub ~
If I helped hit the Thanks button. Follow Me! ~ Buy Me a Coffee
I think I might shed some light on that error. But, first tell me this can you log into Amazon? It might prove interesting just to log into it with your Amazon account. You will then be offered the opportunity to join if you wish, but you don't have to. There are a few freebies on there that do not require you to subscribe to it. If those play then I would be at a loss.
But, I would wager that it won't.
If I were you I would head off to the PlayStore, and search for an App called 'DRM Info' this App checks the status of all the local DRM Keys installed on your Device.
In short I suspect heavily you are getting that message 'cause somehow, some way, your DRM Keys either got corrupted, or erased, and lost for good.
In short in order to use Netflix, or Amazon, or HBO Go, etc... etc... That require the strongest DRMs to protect their Content. Only Widevine L(evel)1 will do. This Key can only be set at the Factory, and is highly likely to be very unique to the Device. If it did decide to go walkies. Then all you'd be left with is the basic Widevine L(evel)3. Which is not an acceptable level protection for their likes. And so you get the above Error Code: tvq-pb-103.
Outside of sending the Box back to nVIDIA, I don't know of any possible way to ever recover it.
OP seems to be in plain stock and the issue sounds like it suddenly happened.
Anyway yes is good to verify your DRM keys and confirm if you have done something else to your device in terms of flashing unofficial stuff, BUT even if you did root, etc this shouldn't happen. I run full Android nougat and I'm rooted, I've flashed many times now since Nvidia 3.3, upgrading back to new stock and reflashing to new full Android and DRM keys are intact, so is really really really hard and very odd to lose DRM keys just like that, but for troubleshooting is good to check that detail too.
~ Sent from my Tapatalk Hub ~
If I helped hit the Thanks button. Follow Me! ~ Buy Me a Coffee
lavero.burgos said:
OP seems to be in plain stock and the issue sounds like it suddenly happened.
Anyway yes is good to verify your DRM keys and confirm if you have done something else to your device in terms of flashing unofficial stuff, BUT even if you did root, etc this shouldn't happen. I run full Android nougat and I'm rooted, I've flashed many times now since Nvidia 3.3, upgrading back to new stock and reflashing to new full Android and DRM keys are intact, so is really really really hard and very odd to lose DRM keys just like that, but for troubleshooting is good to check that detail too.
~ Sent from my Tapatalk Hub ~
If I helped hit the Thanks button. Follow Me! ~ Buy Me a Coffee
Click to expand...
Click to collapse
Well OP never mentioned if his Unit was first owned, or used. It's possible someone damaged it before passing it on.
I will suspect that it's a DRM Permissions problem (e.g. Invalid Keys). Cause I got the case of the Stupids last month thinking that Rooting, and updating left me with a bricked Pro. Thankfully someone left a Backup Image of a working Shield TV Pro on this Board (SSHD > SSD Migration), using this 'Backup' was known to break Netflix in this exact same way. If you read that thread the going consensus had the ESN (Electronic Serial Number), pegged as the culprit. Although the ESN is more or less randomly generated on the fly. Also if it were just somehow the ESN that was to blame, it would not itself explain why Amazon also refuses to play anything. Of course when that Thread was at it hotest. Amazon Prime was not even a twinkle in Jen-Hsun Huangs' eye. However having ran the DRM Info App on my own Shield TV... It is clear that my own unique Keys are now long gone, and as a fact of it I'm limited to just Widevine L3. The Shield TV is in fact supposed to be a high tier L1 Device. So fell free to draw your own conclusions.
Ichijoe said:
Well OP never mentioned if his Unit was first owned, or used. It's possible someone damaged it before passing it on.
I will suspect that it's a DRM Permissions problem (e.g. Invalid Keys). Cause I got the case of the Stupids last month thinking that Rooting, and updating left me with a bricked Pro. Thankfully someone left a Backup Image of a working Shield TV Pro on this Board (SSHD > SSD Migration), using this 'Backup' was known to break Netflix in this exact same way. If you read that thread the going consensus had the ESN (Electronic Serial Number), pegged as the culprit. Although the ESN is more or less randomly generated on the fly. Also if it were just somehow the ESN that was to blame, it would not itself explain why Amazon also refuses to play anything. Of course when that Thread was at it hotest. Amazon Prime was not even a twinkle in Jen-Hsun Huangs' eye. However having ran the DRM Info App on my own Shield TV... It is clear that my own unique Keys are now long gone, and as a fact of it I'm limited to just Widevine L3. The Shield TV is in fact supposed to be a high tier L1 Device. So fell free to draw your own conclusions.
Click to expand...
Click to collapse
Yes, your drm keys are gone because you flashed partition images of another person's device with valuable and unique device info. But your case is very special, not something that you see everyday.
Anyway OP should report back with all the info requested.
BTW do you get the exact same error when you try Netflix? this would say alot too. You seem to only have tested Amazon Video.
~ Sent from my Tapatalk Hub ~
If I helped hit the Thanks button. Follow Me! ~ Buy Me a Coffee
lavero.burgos said:
Yes, your drm keys are gone because you flashed partition images of another person's device with valuable and unique device info. But your case is very special, not something that you see everyday.
Anyway OP should report back with all the info requested.
BTW do you get the exact same error when you try Netflix? this would say alot too. You seem to only have tested Amazon Video.
~ Sent from my Tapatalk Hub ~
If I helped hit the Thanks button. Follow Me! ~ Buy Me a Coffee
Click to expand...
Click to collapse
The ONLY reason why I even bothered to respond here, as on the nVIDIA Forums was that I was receiving the exactly the same code as above. Which is why I thought to throw it out there. I agree under normal circumstances it shouldn't happen. Especially on an eMMC 16Gb Device. But, that doesn't mean it couldn't have happened. It is however very checkable, and as easy as downloading a simple App off the Play Store.
I just found out that i have, Permanently losing Widevine L1 now DRM info showed L3 that why i have no Netflix or Amazon.
allcius said:
I just found out that i have, Permanently losing Widevine L1 now DRM info showed L3 that why i have no Netflix or Amazon.
Click to expand...
Click to collapse
Again, is your Shield new, or used? If its new (e.g. It's still under Warranty), I would contact nVIDIA about getting an RMA.
If OtOH it's neither new, or under Warranty than I guess your just whats in the technical jargon known as SoL.
But still, it may be one thing to fork this up on the SSHD. But normally this is a Partition that should never be touched 99% of the time and as part the 16Gb eMMC nealy impossible to format. Without permabricking the entire Device.
No warranty for me (don't have the receipt anymore..... ).
But i read it's very difficult to break the Drm because it's in a special partition. I have my original sshd in the shield tv. Couple weeks ago i started having issues because of bad connections in my sshd ribbon. i was able to fix it by trimming the edge the connector. When i was able to boot it. It stayed in the 4 spinning dots for hours that where i decided to flash the 5.0.2 from Nvidia dev. I downloaded both normal and root but I'm not sure with one i installed in it. After 2 hours it was up and running. And even updated itself to 5.1 after full reset. But for some reason it stock in Drm L3.
I installed as per nvidia instructions. No other mod. Nvidia original recovery. To be sure I am going to try the original 5.0.2 (not the rooted one) and see what will happen. Hoping i can still go from 5.1 to 5.0.2.
allcius said:
No warranty for me (don't have the receipt anymore..... ).
But i read it's very difficult to break the Drm because it's in a special partition. I have my original sshd in the shield tv. Couple weeks ago i started having issues because of bad connections in my sshd ribbon. i was able to fix it by trimming the edge the connector. When i was able to boot it. It stayed in the 4 spinning dots for hours that where i decided to flash the 5.0.2 from Nvidia dev. I downloaded both normal and root but I'm not sure with one i installed in it. After 2 hours it was up and running. And even updated itself to 5.1 after full reset. But for some reason it stock in Drm L3.
I installed as per nvidia instructions. No other mod. Nvidia original recovery. To be sure I am going to try the original 5.0.2 (not the rooted one) and see what will happen. Hoping i can still go from 5.1 to 5.0.2.
Click to expand...
Click to collapse
Trim as in cutting the Ribbon!? If so no wonder you have problems!
Ichijoe said:
Trim as in cutting the Ribbon!? If so no wonder you have problems!
Click to expand...
Click to collapse
It was fairly easy looked before and after. I used a shaped cisor
Just got this today and it's great besides being a bit smaller than my g6 and because of front camera design only being technically 5.5in screen for most apps especially games.
However since I have had it, it has randomly rebooted itself twice for no real apparent reason. Is this a known issue or something anyone else has experienced? I want to try to get a bit more information on it before contacting the eBay seller. It is a refurbished.
I have never experienced a random reboot. You might want to try factory resetting your phone and then setting it up with the fresh start option instead of restoring from a Google cloud backup. Was your phone on Nougat or Oreo when you received it? Were there any major software updates?
It was fully updated to 8.1.0 when I received it. April 5th security patch. It was factory reset and I started fresh. No backup other than logging into my Google account for contacts, passwords and logins and such. I never do backups and restores always start fresh other than Google account.
Nickvanexel said:
It was fully updated to 8.1.0 when I received it. April 5th security patch. It was factory reset and I started fresh. No backup other than logging into my Google account for contacts, passwords and logins and such. I never do backups and restores always start fresh other than Google account.
Click to expand...
Click to collapse
Must be rogue app, had mine 3 months and never had a glitch or reboot.
Sent from my PH-1 using Tapatalk
If you are still having the random reboots you might want to boot your phone into safe mode to verify that a third party app isn't causing the problem. Since your phone was refurbished it's also possible that it was damaged by the previous owner or returned for the same issue you are experiencing. I did read that some early PH-1 buyers had to return their phones because of hardware issues like overheating.
Just did it again while using chrome. Just froze up for a few seconds and restarted. Doesn't seem to be overheating and the first time it happened before I installed anything I think. Guess I'll try a reset and go from there.
Factory reset twice now. No 3rd party apps installed. Updated all apps on Google play. The default phone apps.
Now the phone is freezing and rebooting itself constantly. Out of control. I am in safe mode right now and hasn't frozen yet. I don't know what the hell is going on.
Would love to be able to fix this issue myself without having to do return shipping. I have contacted the seller already though.
If it doesn't freeze or reboot at all in safe mode that usually means an app that you downloaded is causing the problem. The normal thing to try would be to factory reset the phone, download one app and see if there are problems. If the phone seems to be fine download a second app and use the phone long enough to see if the phone is stable. If it seems fine download a third app and do the same.
That's obviously very time consuming and if you were running a phone with heavily modded code like OnePlus with Oxygen it would probably be worth the investment of time. But this phone runs stock Android. Unless you are installing something unusual that might cause stability issues what you are describing sounds like a hardware problem. You might have bad memory for example and not enough is going on when the phone is in safe mode to trigger the unstable behavior.
I think returning or exchanging the phone you bought is definitely your best course of action. I really like this phone but it sounds like yours is defective or damaged.
The only other thing that comes to mind is that sometimes if you own more than one phone the Play Store will show apps that aren't compatible with the phone you are actually using. Dialers, messaging apps, camera apps and music players made for a specific phone brand aren't usually compatible with other brands because they need modded framework to function properly. Some apps that definitely are not compatible with this phone do show up in my Play Store Library available for download. Is it possible you are downloading an incompatible app?
I factory reset and haven't installed a single app. Just updated everything that was stock with the phone after reset. I was thinking faulty ram too, seems like it is.
Yeah I guess it's toast. Last night while watching YouTube it froze. Screen scrambled with artifacts and the phone made a loud continuous howling sound like an emergency alert. I honestly thought it was an emergency alert until I saw the artifacting.
Unless someone here can possibly give me an idea of any other reason it could be displaying this behavior I guess I have no choice but to return it?
Nickvanexel said:
Yeah I guess it's toast. Last night while watching YouTube it froze. Screen scrambled with artifacts and the phone made a loud continuous howling sound like an emergency alert. I honestly thought it was an emergency alert until I saw the artifacting.
Unless someone here can possibly give me an idea of any other reason it could be displaying this behavior I guess I have no choice but to return it?
Click to expand...
Click to collapse
Grab a BTS zip from the back to stock thread... And flash that...
I'll bet however it was updated had some yuck in it...
Nickvanexel said:
Yeah I guess it's toast. Last night while watching YouTube it froze. Screen scrambled with artifacts and the phone made a loud continuous howling sound like an emergency alert. I honestly thought it was an emergency alert until I saw the artifacting.
Unless someone here can possibly give me an idea of any other reason it could be displaying this behavior I guess I have no choice but to return it?
Click to expand...
Click to collapse
Someone in the Essential stock ROM dump thread just described the exact same behavior that you are experiencing. He hopes reflashing stock will fix it but since it's identical to what's happening with your phone I think he's going to end up disappointed. You might want to check out his post and see if he has any luck. It was the latest post in the thread so it should be easy to find.
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681/page41
Yeah that was me. Trying to get information on the procedure to manually reflash this phone with stock firmware. I shouldn't need to unlock bootloader to do it? Just trying to flash stock over stock to hopefully correct any os corruption. Also mine is apparently a unlocked Sprint variant even though it was advertised as being a normal unlocked variant. Not sure if the firmware from that thread will work for me.
Nickvanexel said:
Yeah that was me. Trying to get information on the procedure to manually reflash this phone with stock firmware. I shouldn't need to unlock bootloader to do it? Just trying to flash stock over stock to hopefully correct any os corruption. Also mine is apparently a unlocked Sprint variant even though it was advertised as being a normal unlocked variant. Not sure if the firmware from that thread will work for me.
Click to expand...
Click to collapse
Sorry I didn't notice that. I haven't done any flashing on this phone but I know I read that people with the Sprint phones were flashing the regular stock image to get rid of the Sprint apps and get updates from Essential rather than Sprint. But if you don't want to unlock your bootloader you can download official factory images from the Essential website and sideload using a computer. Flashing instructions are on the download site.
https://www.essential.com/developer/current-builds
Alright I reflashed the latest firmware from essential page via adb sideload. I highly dout it worked but I'll see.
What would I need to do from here to do a complete fresh reflash completely overrighting any trace of the old os? I still want to keep it stock but doesn't matter if I need to unlock the bootloader. Just want a complete wipe of the old os and fresh reflash to be sure any traces of corruption are removed to be sure if it's a hardware issue.
That's easy on single partition phones but much more difficult on phones with an A & B partition like the PH-1. You definitely need to unlock the bootloader. On my Pixel XL you needed to flash the factory image separately to partitions A & B to ensure there was nothing left from before but the procedure might be different on this phone. I went through the flashing instructions when I got this phone and think if you flash the full restore stock image it supposedly returns both partitions to stock automatically but that definitely didn't happen on the Pixel. Considering that this phone is supposed to be easy to hard brick (which was virtually impossible on the Pixel) I wouldn't chance it unless you can't return or exchange the phone from the seller.
Well side loading the ota from essential website didn't work. I'd say it's already hard bricked. Still crashing after a while of using it. Last night I loaded as many apps at one time as I could. Got maybe 10 opened at once before it crashed. Seems like faulty ram to me.
Wife just had it happen on her new White one twice today while playing Pokemon GO.
She says she also had her podcast app and hangouts open but minimized and not being actively used in the background.
She's on a fresh install of Oreo 8.1 with the Gcam mod by MGC_5.1.018_Urikill_vXXII.apk using the settings suggested by aer0zer0
Anyhow I hope its just a completely random fluke and not a serious issue as I have a new black one from Amazon in the mail and would really hate to have to return these otherwise wonderful devices.
Mine ain't no fluke. After it crashes if I immediately reboot it instantly crashes again. I have to let it sit a while turned off and reboot again to any significant time before crashing. Longest time it's ran before crashing since having it it's maybe an hour. Didn't notice it much at first because I didn't use it more than a few minutes at a time. So it was in sleep mode constantly crashing and rebooting. Now that I have been watching it more it just constantly keeps rebooting even while sitting idle. I'll glance over at my phone and low and behold it's rebooting again.
Nickvanexel said:
Mine ain't no fluke. After it crashes if I immediately reboot it instantly crashes again. I have to let it sit a while turned off and reboot again to any significant time before crashing. Longest time it's ran before crashing since having it it's maybe an hour. Didn't notice it much at first because I didn't use it more than a few minutes at a time. So it was in sleep mode constantly crashing and rebooting. Now that I have been watching it more it just constantly keeps rebooting even while sitting idle. I'll glance over at my phone and low and behold it's rebooting again.
Click to expand...
Click to collapse
Ouch okay that most certainly sounds like a bad hardware issue as you suspected earlier.
Thankfully in her case the reboots were well apart from one another and the phone was fine after the reboot. Even let her play PKGO.
I mostly came in to comment to hopefully help by voicing that it had happened and the circumstances in which it did for her with the idea it might pinpoint some flaw in the overall system if there was one.
My brother passed away and was using this phone until a couple of weeks ago. I don't have the lockscreen pattern but I'm trying to do a little detective work regarding my brothers last activity. I reached out to law enforcement, but they don't have an active investigation and they suggested that I reach out to his cell provider [Tracfone] which I might try. Of specific interest to me is his text message activity on the day of his death.
Anyhow I scoured the net and tried to beat the lockscreen via emergency dialer, and also tried to connect via adb shell and MTP. I also don't think the device was registered via the samsung tools. I'm at the point where the device told me I have 9 unlock attempts left and it will erase the device after. The lockscreen seems to appear at device power and I think that it might not have booted android completely at this point.
Is anybody aware of a method to bypass the lockscreen which would work on this device so I can look into the details surrounding his death?
Sort of desperate here. There seems to be some software called Dr Fone that claims to have a lockscreen removal. However not sure that it works and on this device.
I may have a solution for this if you are wanting to preserve data if not check around on youtube for a video on FRP resetting this. I might have wrote a tutorial on this somewhere but I cant remember atm. Basically if you don't want to preserve the devices data (your brothers as you say) then you will simply factory reset it and then follow an FRP Removal tutorial you can find on here and or youtube.
btw nice leet username =]
phonecapone said:
I may have a solution for this if you are wanting to preserve data if not check around on youtube for a video on FRP resetting this. I might have wrote a tutorial on this somewhere but I cant remember atm. Basically if you don't want to preserve the devices data (your brothers as you say) then you will simply factory reset it and then follow an FRP Removal tutorial you can find on here and or youtube.
btw nice leet username =
Click to expand...
Click to collapse
Speaking of nice usernames
If you're still around, I have an old J327t1 that I had dropped and broke the screen on a few years ago. I recently fixed it, but can't remember PIN. I would like to preserve the data and am interested in what you have
veryspecialagent said:
Speaking of nice usernames
If you're still around, I have an old J327t1 that I had dropped and broke the screen on a few years ago. I recently fixed it, but can't remember PIN. I would like to preserve the data and am interested in what you have
Click to expand...
Click to collapse
All you need to do is find a recovery for that and flash it then go into the lock files and remove those. You can find some guides here on XDA or on youtube.
This was before I got into development, so adb isn't enabled, bootloader is still locked, and the phone is not rooted, so I'm skeptical I'd be able to flash. It's also running (I believe) Marshmallow, and most of those "find and delete lock settings" methods were for 4.x Kit-Kat and below. I could be wrong though.
If you have a particular thread in your watch list, I'd be grateful for the link.
I've been all over looking for a solution, hence me posting in here as opposed to creating a thread. Didn't want to reinvent the wheel if I didn't have to.
Despite the above limitations, the device has not received any updates since June 2017, it DOES go into MTP mode when I hook it to my laptop, and I have verified that it is vulnerable to the Mtpwn exploit.
noidodroid said:
All you need to do is find a recovery for that and flash it then go into the lock files and remove those. You can find some guides here on XDA or on youtube.
Click to expand...
Click to collapse
Also, I turned a moto g7 Play into a Nethunter device and had tried Android PIN Bruteforce, but after entering in so many PINs it would make me wait 30 seconds to try again and I couldn't figure out how to get my g7 to keep the screen of the J3 on. Or wake it back up, since it requires you to hit power then swipe the screen.
I ended up wiping it because it had Pie and no workaround for the wifi throttling, and installed Q. It's rooted, but I haven't set up nethunter back up on it yet. I do have an S5 that I has Nethunter, but haven't set it up with HID support yet. Plus, the battery on that would drain too quickly to use for this process.
Daughter had her Note 4 replaced a few months ago, and it had just been sitting there. Earlier this week got a DJI Spark, and the flight controller requires an Android or iOS phone. Got tired of pulling the case off and on MY phone (S8+), so figured I could use hers as a WiFi-only, dedicated device.
My main concern is that I don't think we ever got the phone formally unlocked by AT&T. I've gotten around that so far just by pulling out the sim. It doesn't seem "happy" about it, but hasn't stopped me configuring the phone to do what I need so far - though it would be nice to be able to uninstall all the AT&T apps that are on there even after a full reset/wipe.
So wondering if there is:
A) Some way to unlock this old thing so I can rest easy it won't have an issue waking up one day
B) A more recent ROM and/or security updates (while it mainly will access the Drone/Receiver WiFi I presume I need to still connect to the home LAN occasionally for app updates)
C) Anything I could flash to make it less of a phone and more of a small tablet (since that's how I'll be using it)
Thanks in advance!
If you are saying the phone is locked to AT&T and you want it unlocked then see here:
https://www.att.com/deviceunlock/#/
Apparently no one has been able to root your device before because they cannot unlock the bootloader:
https://forum.xda-developers.com/no...ty-att-note-4-root-knox-list-pledges-t2946770
My recommendation is to do a factory reset and use something like Package Disabler Pro app to freeze unneeded applications.
terminator911 said:
Apparently no one has been able to root your device before because they cannot unlock the bootloader:
https://forum.xda-developers.com/no...ty-att-note-4-root-knox-list-pledges-t2946770
My recommendation is to do a factory reset and use something like Package Disabler Pro app to freeze unneeded applications.
Click to expand...
Click to collapse
Ah... well that's too bad. I like that the phone has a replaceable battery, which makes it almost worth keeping as long as possible for that. Will try your suggestion on the other. Thanks anyway!