Database Users

Oneplus 2 having screen issue. Help!

Hi,
My OPT has deveoped these white spots all over the screen. I have tried wiping the device several times and also tried installing a different OS and the problem still persists. Do you think it's a h/w issue? When i boot into TWRP these spots don't appear so I think it's a software issue. Can anyone suggest methods to fix this? I have attached some screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

If it were hardware, we wouldn't be able to see it through screenshots. I suggest you reflash OxygenOS (dirty flash, no need to wipe your data) and see if that fixes it.

Waterdroid said:
If it were hardware, we wouldn't be able to see it through screenshots. I suggest you reflash OxygenOS (dirty flash, no need to wipe your data) and see if that fixes it.
Click to expand...
Click to collapse
Tried that as well, When I flash a new OS does it change the drivers for the display?

wackyrish said:
Hi,
My OPT has deveoped these white spots all over the screen. I have tried wiping the device several times and also tried installing a different OS and the problem still persists. Do you think it's a h/w issue? When i boot into TWRP these spots don't appear so I think it's a software issue. Can anyone suggest methods to fix this?
Click to expand...
Click to collapse
have u rooted the device? it seems to be a display driver problem. download the latest 2.0.2 ota (zip file about 1gb) and copy it on ur phones memory. then go into the bootloader and install it by apply update through internal memory

daninantro said:
have u rooted the device? it seems to be a display driver problem. download the latest 2.0.2 ota (zip file about 1gb) and copy it on ur phones memory. then go into the bootloader and install it by apply update through internal memory
Click to expand...
Click to collapse
I tried that as well. I wasn't able to find a 2.0.2 so I installed 2.0.1 and updated OTA to 2.0.2 Yes it is un rooted. Tried installing the CM12.1 by Temasek and still the same issue.

I suggest setting up a remote session with the Customer Support. I know it's a pain in the ass to communicate with them, but they've got the images and can reflash those.

wackyrish said:
I tried that as well. I wasn't able to find a 2.0.2 so I installed 2.0.1 and updated OTA to 2.0.2 Yes it is un rooted. Tried installing the CM12.1 by Temasek and still the same issue.
Click to expand...
Click to collapse
how were u able to install cm12.1 when ur device is not rooted? anyway contact customer support or else go to the service centre. they will help u

daninantro said:
how were u able to install cm12.1 when ur device is not rooted? anyway contact customer support or else go to the service centre. they will help u
Click to expand...
Click to collapse
Oops, Sorry meant to say that the phone is rooted and I have custom recovery installed. I live in UAE no service centers here

Stuck in Google FRP (Nougat)

Followed these instructions to unlock the bootloader and flash the latest DU to my wife's XT1575: https://forum.xda-developers.com/moto-x-style/general/guides-how-to-guides-beginners-t3200808
DU was buggy so I decided to flash stock nougat using these instructions (left bootloader unlocked): https://forum.xda-developers.com/moto-x-style/general/xt1575-moto-x-pure-edition-factory-t3704142
Everything seemed to go fine until we attempted to sign into her existing account and got this error: Unable to sign in to device due to an unknown error. Please try another account or try to sign in again after 24 hours.
Had no idea what that was about, so I Googled it and found out about Factory Reset Protection (FRP). I didn't find much information and the only advice I found was to wait at least 24 hours before trying again. Turned off the phone and waited a full 26 hours before turning it on again--attempted to sign in again and still getting the same error.
Any advice for what to do next?

This was the first link that popped up. Just asking, have you tried this?

antariksh said:
This was the first link that popped up. Just asking, have you tried this?
Click to expand...
Click to collapse
Thanks for the reply. I hadn't tried that yet, but I just did and it didn't seem to work. Everything happened exactly the same even after "removing" the device as per the instructions.
Screenshot from Google account: https://image.ibb.co/dbnjz6/screenshot.jpg

thejukes said:
Thanks for the reply. I hadn't tried that yet, but I just did and it didn't seem to work. Everything happened exactly the same even after "removing" the device as per the instructions.
Screenshot from Google account: https://image.ibb.co/dbnjz6/screenshot.jpg
Click to expand...
Click to collapse
Are you seeing 'Access Removed' in Google Settings?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Have you tried logging in any other GMail accounts?

antariksh said:
Are you seeing 'Access Removed' in Google Settings?[/IMG]
Click to expand...
Click to collapse
No. I saw the big red "REMOVE" button, clicked it, and got the confirmation just like the article said, but as you can see from my screenshot, it does not say "Access Removed." next to the device. There is also no more "REMOVE" button. But the interface seems slightly different from the time that article was written so perhaps that's why.
antariksh said:
Have you tried logging in any other GMail accounts?
Click to expand...
Click to collapse
Yes, tried but it won't allow it. It says that a factory reset was done on it and that I need to log in from the account that was on it. But, when I try doing that, of course I get the same error as before: Unable to sign in to device due to an unknown error. Please try another account or try to sign in again after 24 hours.

thejukes said:
No. I saw the big red "REMOVE" button, clicked it, and got the confirmation just like the article said, but as you can see from my screenshot, it does not say "Access Removed." next to the device. There is also no more "REMOVE" button. But the interface seems slightly different from the time that article was written so perhaps that's why.
Yes, tried but it won't allow it. It says that a factory reset was done on it and that I need to log in from the account that was on it. But, when I try doing that, of course I get the same error as before: Unable to sign in to device due to an unknown error. Please try another account or try to sign in again after 24 hours.
Click to expand...
Click to collapse
Not sure what causing it, but try Factory resetting the current Stock ROM or try any other custom ROM with Nano GApps.
P.S: If you currently are on Stock Nougat then flash any Custom ROM based on stock nougat.

I thought FRP didn't work with an unlocked bootloader?

antariksh said:
Not sure what causing it, but try Factory resetting the current Stock ROM or try any other custom ROM with Nano GApps.
P.S: If you currently are on Stock Nougat then flash any Custom ROM based on stock nougat.
Click to expand...
Click to collapse
The phone originally had Marshmallow. The issue with custom ROMs is reliability. Even with DU, which is known for being one of the more stable ROMs, there were a lot of glitches. For example, sometimes the camera app would open, sometimes it wouldn't, which isn't good when you've got a toddler and want to capture moments.
Maybe I'm misinterpreting what you're saying... Are you suggesting that maybe I can somehow circumvent FRP by going from a custom ROM and back to a stock ROM?

Try commenting out this line in build.prop with a # tag
Code:
ro.frp.pst=/dev/block/platform/soc.0/f9824900.sdhci/by-name/frp

antariksh said:
Try commenting out this line in build.prop with a # tag
Code:
ro.frp.pst=/dev/block/platform/soc.0/f9824900.sdhci/by-name/frp
Click to expand...
Click to collapse
Thanks. Unfortunately, I don't know how to do this. I did some Googling and found instructions that won't work for me since I can't get into the phone. Also, looking at the firmware files, I don't see any the files in question.
I called Google and they blamed Motorola and patched me through to their support line. Motorola had no clue what to do. They blamed the legally required "kill switch" but said that it should let me in if I know the right account and password, which I do, but it still doesn't work.

Tab A Rebooting Like Hell.Need Custom Rom

My Tab A Sm-T355Y Is Rebooting Randomly While using.It has developed so it is unusable mostly.Please Develop a Custom ROM.Many other users are also facing the use issue.Downgrading does not solve the issue.

Reflashing the firmware up or down rarely solves crashing issues unless the system partition is corrupted.
Wiping the data partition should be you next call

ashyx said:
Reflashing the firmware up or down rarely solves crashing issues unless the system partition is corrupted.
Wiping the data partition should be you next call
Click to expand...
Click to collapse
I tried everything from formatting to downgradomg but nothing helps.

Balaji Sriram said:
I tried everything from formatting to downgradomg but nothing helps.
Click to expand...
Click to collapse
Then I guess it's hardware related.

ashyx said:
Then I guess it's hardware related.
Click to expand...
Click to collapse
Bro many members faced this issue.Developing a Custom ROM Would Fix This.We already have TWRP.It does not reboot in Recovery or in Safe Mode.

Balaji Sriram said:
Bro many members faced this issue.Developing a Custom ROM Would Fix This.We already have TWRP.It does not reboot in Recovery or in Safe Mode.
Click to expand...
Click to collapse
What do you mean it doesn't reboot in recovery?

ashyx said:
What do you mean it doesn't reboot in recovery?
Click to expand...
Click to collapse
If I Keep In recovery It does not reboot.Already you have developed Twrp for Sm-T355Y Model Of Tab A.Can you please release a Custom Rom.Even Nougat or Marshmallow would help.

Balaji Sriram said:
My Tab A Sm-T355Y Is Rebooting Randomly While using.It has developed so it is unusable mostly.Please Develop a Custom ROM.Many other users are also facing the use issue.Downgrading does not solve the issue.
Click to expand...
Click to collapse
This is the common issue of Samsung tablet: loose battery cables and no ROM can fix it.
You can use this glue to make it works better without loosing the connection. However, the glue is conductive, make sure wipe clean with alcohol. Otherwise, you will end with overheating due to trace between terminals. It should not have any residues between the top as well. A lousy job will cause overheating or shorted circuit.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You can buy it online from Ebay or Amazon
https://www.ebay.com/itm/Silver-Con...028785&hash=item4d622308f1:g:zFQAAOSwyXNZ5XVn
Or adjust it manually, like this. Squeeze as much as possible
This is not an opinion, I have done many times to fix this problem of rebooting or quick discharge, not only this tablet but others as well.
Unless the mainboard is defective, this solution should fix the reboot issue easily.

Boost E4 1766 Only Boots to TWRP

-Screwed up somewhere as my goal was to install LineageOS and try to use it on an At&t mvno.
-Package was unopened for months, so it still had the older firmware.
-Everything seemed okay after I unlocked the bootloader.
-Then I installed TWRP.
-Did a backup of everything using TWRP before I was going to try and root the device.
-I knew something was wrong when no verity opt encrypt and Magisk gave some error message and failed.
-Now whenever I boot the device, I get a N/A in the top left corner and then goes into TWRP.
-Restoring the backup using TWRP did nothing.
-I thought this would be the solution (dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=1M), but I get the bad key first and then N/A before going back to TWRP.
https://forum.xda-developers.com/moto-e4/help/moto-e4-metro-variant-rebooting-to-twrp-t3825841
What should I do now?
Any help would be appreciated. Even links to other posts that dealt with this issue is fine. Be aware that my skill level is only a little better than following Youtube videos.
Thank you.

N/A is normal. It will be there forever after you unlock bootloader. Did you format data in TWRP and type yes to format?

Thanks for the reply.
As far as I know, I did not format within TWRP. Is that my next step? If not, please advice what should be done next.
My concern is something is wrong because both the suggestions you gave in that other thread did not result in the phone booting to Android properly.

ah-le-le said:
Thanks for the reply.
As far as I know, I did not format within TWRP. Is that my next step? If not, please advice what should be done next.
My concern is something is wrong because both the suggestions you gave in that other thread did not result in the phone booting to Android properly.
Click to expand...
Click to collapse
once you flash TWRP you have to flash a no verity zip and probably magisk and definitely format data to remove encryption for your phone to boot.

Installing no verity zip and magisk produced the following. Did I do this properly because there looks like multiple errors?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

ah-le-le said:
Installing no verity zip and magisk produced the following. Did I do this properly because there looks like multiple errors?
Click to expand...
Click to collapse
I can't read that, LoL. Maybe... Failed toount data? That's because you're still encrypted.
Put the zips on external storage. Format data, type yes.
Now reboot recovery (not system) then flash the zips.
And you can take screenshots in TWRP.

Thanks so much.
I followed your instructions plus the one from the other thread. Phone is now able to boot to the stock Android. I guess my next step is doing a little more research before trying to install LineageOS to see if the phone works well enough on a USA GSM mvno.

One more question please.
On the E4, are the system firmware updates mandatory? I read that users are first notified and then forced to take the update even if you Disable Automatic System Updates.
Is that true? I wish to stay with the old firmware because people have posted that the new firmware eliminates any chance of using a USA GSM sim on a Boost 1766.
Thanks.

ah-le-le said:
Thanks so much.
I followed your instructions plus the one from the other thread. Phone is now able to boot to the stock Android. I guess my next step is doing a little more research before trying to install LineageOS to see if the phone works well enough on a USA GSM mvno.
Click to expand...
Click to collapse
ah-le-le said:
One more question please.
On the E4, are the system firmware updates mandatory? I read that users are first notified and then forced to take the update even if you Disable Automatic System Updates.
Is that true? I wish to stay with the old firmware because people have posted that the new firmware eliminates any chance of using a USA GSM sim on a Boost 1766.
Thanks.
Click to expand...
Click to collapse
Use caution going with a custom ROM on this device, especially with a mvno. You may score far more hurt than benefit. Also consider what you are trying to accomplished going with custom ROMs given the clean stability of Moto stock ROMs. Toss in Xposed framework and a few modules like Gravitybox for full control/customization.
OTA updates can not be processed with a custom recovery (one of several prerequisites that your device no longer meets). You may get notified but the update won't install; you'll be dumped into TWRP. You can easily disable the update engine and corresponding notifications on a rooted device.

I have some t350's with issues recovery/MDM/black screen and bootloops

I recently found at the dumps a box of t350's 6/18 didnt like combination flashing the mdm away/new firmware install. 3 failed the same way while putting on newest firmware with odin now they say mdm mode in odin again and i have no debug access. 1 black screens in bootloader and when booting no debug access mdm mode in odin again. BUT ! I have 1 with debug access and see it in ADB BUT it fails to install due to signature verifcation of the ROM's I've tried. I think the later is savable EZ just need a a little help getting TWRP onto it I guess and I'm good. I'll worry about the others later but any ideas ? my brain hurts from trying cables/roms/adb versions lol

Maybe the rom is incorrect have you checked the region and model number etc?

Kenora_I said:
Maybe the rom is incorrect have you checked the region and model number etc?
Click to expand...
Click to collapse
the issue is the MDM mode seems like, it fails to write. only time i every got them to flash was after the combination flash the download menu popped up very slow after it was working hard to explain..... i have 7.1.1 on all the working one's which seem finebut i ****ed up i shouldve TWRP them first, one of them i successfully did get twrp on and lineage after the fact and i tried again with now another boot looping tablet SMH. idk what i did to do it the first time

TDIfrogman said:
the issue is the MDM mode seems like, it fails to write. only time i every got them to flash was after the combination flash the download menu popped up very slow after it was working hard to explain..... i have 7.1.1 on all the working one's which seem finebut i ****ed up i shouldve TWRP them first, one of them i successfully did get twrp on and lineage after the fact and i tried again with now another boot looping tablet SMH. idk what i did to do it the first time
Click to expand...
Click to collapse
no matter what i write to it twrp any firmware just fails like it did when it was mdm locked

Could you provide ODIN logs?

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

it shows mdm locked and the odin log reflects that BUT they where unlocked at some point im, afraid to try and flash the other and they'll end up like this one

TDIfrogman said:
View attachment 5364601
Click to expand...
Click to collapse
They might have NAND flash erros because they arent able to write to it.

Kenora_I said:
They might have NAND flash erros because they arent able to write to it.
Click to expand...
Click to collapse
hmmmm how can i fix it ?

It could be hardware issue, I'm not sure how to fix hardware issues. Thats probably the reason they were all together in a box.

no they where in a box because they came from a school and they didn't take knox off, there was 1000+ of them I just grabbed a tray full they have these crazy polycarbonate cases on them too with security screws. they all worked until i flashed knox away with varying results 12/18 working fine 18 worked prior but in knox

Oh that info is noted.
May I help you later. Its pretty late and I have to get off.
Ill help in the mornin