Hello,
I've successfully managed to install OnePlus3T_28_A.86_191104_repack through MsmDownloadTool V4.0.71 where the Status of Communication is "Download Complete".
{
"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"
}
After this, when the phone boots, the OnePlus logo shows up for a little while – and after that, a black screen. I can only access fastboot – and that's about it. The phone is locked, etcetera, so I can't flash via adb/fastboot. When I try to access recovery mode through the fastboot menu, the screen becomes black too.
Worth mentioning I've also successfully installed through an older version of MSM before this. But same results. The version is the following OnePlus3T_28_A.23_161027 and the MsmDownloadTool V3.0.6.
What are the alternatives? Is it good game? If someone could pinpoint me what to do next would be glorious. The hard-brick guides seem to always point to the MSM way of things.
Thanks in advance!
Alright so I've been digging a bit deeper.
Stumbled upon a bunch of different YouTube videos that had similar solutions.
Most of them were squeezing, tapping and doing different motions onto the phone. Like pressing down the screen at different angles with some pressure, etc. Also from the back, the buttons to loosen them, etc. I'm sure I've missed some of the methods mentioned in the video.
However, the squeezing on the screen and the back actually made the phone go past the black OnePlus logo into the boot animation -- and I thought that was it. Apparently, it hung up half-way through.
The last method they mentioned was to put the phone in the freezer in a zipper bag and TRUTHFULLY it worked after being in there for 10 minutes. The phone booted up, went through the installation setup and it worked for a while... until it didn't.
Apparently, my battery does not charge and it's stuck at 0% all the time. Seems a bit suspect. Will dig further into it.
Related
Hey everyone, I've got an issue I've been trying to get figured out with no luck & I'm hoping someone can point me in the right direction. As it says in the title I'm on the Note 5 32GB from t-mobile, it's running 6.0.1, and is rooted with TWRP recovery. Now on to the issue.
Yesterday I rebooted my device, and when it came back up the home screen shrunk. What I mean is the icon/folder area and the screen indicator dots are smaller causing a significant dead space area between the dots and my bottom bar. I have included two photos, one untouched and one with yellow highlighting illustrating the area I am talking about.
In an attempt to remedy this, so far I have done the following:
Checked that one handed operation is disabled (it is)
Checked and changed screen fonts & font size
Changed the home screen grid options
I've even went as far as doing a system reset in twrp erasing everything and starting over
With that I have been unsuccessful in getting this fixed. I am hoping someone can help. In my research the only information I have found to this point talks about the settings I listed above as attempts, and I haven't seen this problem come up at this point, so please don't blast me if I've missed it, and you know where I should look, I am more than happy to read any information provided.
{
"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"
}
I've shared the photos with an image tag from my onedrive account, if they aren't working please alert me and I'll try to find another way to share them.
Not working. Curious though. How is the rest of the system? Setting and whatnot set to normal? Did you flash a ROM?
Sent from my SM-N920T using XDA-Developers mobile app
Everything is default accept my theme, which changing it didn't affect it either. It's a stock rom and systemless root with TWRP recovery. I was thinking I screwed up a setting also which is why I tried to do a reset.
I recently had a problem with my s6 edge where the screen would randomly lock up and give me a black screen with a small x but it was unresponsive. Even if I powered it down via the power button and volume down key it would boot back into that black screen
Here is a video I found that someone else uploaded with the same problem.
https://www.youtube.com/watch?v=GtdahXCetu4
Now I am no expert but after some research I found the problem to be that the phone thinks it is in VR mode and basically locks the user out of using the screen. The reason it thinks it is in VR mode is because that metal tab piece inside the charger port was touching the bottom of the phone causing it to lock itself in VR mode which is why the phone will often freeze up when charger or won't charge when in this frozen state.
I found a fix, which may only be temporary but I thought I would share since I could not find a tutorial anywhere else.
To Unfreeze:
1. VERY VERY gently use something small like tweezers or a tiny flat screwdriver to lift the metal piece inside the charger up just a little. The image below is the metal piece that should be lifted incase there is confusion, I drew a small red marker around it.
{
"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"
}
Guide to Fix from happening again
1. I used Titanium Backup to freeze all the Gear VR programs but then the problem occurred again, except this time the screen just froze as my wallpaper instead of the black screen so you also need step 2
2. I then used a DisableService application and under system tab, I disabled all four items on "Gear VR Services"
I haven't had the problem since I disabled the gear vr services so hopefully it will fix it permanently
Unconfirmed fix
0. If you can get your hands on a VR headset you can attempt plugging it in and unplugging it to reset , but I do not have one so unknown if it would work.
If anyone more knowledge has any information or better fixes feel free to share incase I'm completely wrong here :laugh:
Hey Guys, this one is a doozie. My fire 7 screen has mirrored itself. The touch panel is regestering the correct locations and a screenshot sent to the computer looks fine, but the screen is mirrored on the tablet (as in it reads correctly when held to a mirror. This is not the RTL layout in the developers options. Even the Amazon logo during startup is mirrored. It happened randomly when I turned on my tablet from sleep mode, and it hasn't been the same since. Also, no, this is not a rotation error as not matter what the screen is rotated to, it is displayed wrong.
I have restored to stock and installed TWRP and a custom rom to see if any of those would fix the issue to no avail. I also took the tablet apart, inspected the logic board, ad disconnected/reconnected all internal connections, but that didn't make a difference either.
Is there any way to fix this? Amazon won't fix it without me paying, but a new Fire is cheaper than a repair (although the new ones are locked down). It seems to be a kernal/boot/weird bit that got flipped somewhere, but I haven't been able to track it down.
{
"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"
}
JM0535 said:
Hey Guys, this one is a doozie. My fire 7 screen has mirrored itself. The touch panel is regestering the correct locations and a screenshot sent to the computer looks fine, but the screen is mirrored on the tablet (as in it reads correctly when held to a mirror. This is not the RTL layout in the developers options. Even the Amazon logo during startup is mirrored. It happened randomly when I turned on my tablet from sleep mode, and it hasn't been the same since. Also, no, this is not a rotation error as not matter what the screen is rotated to, it is displayed wrong.
I have restored to stock and installed TWRP and a custom rom to see if any of those would fix the issue to no avail. I also took the tablet apart, inspected the logic board, ad disconnected/reconnected all internal connections, but that didn't make a difference either.
Is there any way to fix this? Amazon won't fix it without me paying, but a new Fire is cheaper than a repair (although the new ones are locked down). It seems to be a kernal/boot/weird bit that got flipped somewhere, but I haven't been able to track it down.
Click to expand...
Click to collapse
Sure you have the right forum (5th gen Fire)? I assume device has the 5.0.x bootloader as you referenced TWRP which can be booted but not installed. You could try reflashing the bootloader from this thread. Beyond that there may be a hardware or low level firmware glitch that can not be repaired.
Okay, so here's what I've tried to fix this problem, and I'm still drawing blanks. Here's the problem - the phone acts as if there is no rear camera whatsoever, nor led light on the back for a flashlight. Selfie (front-facing) camera works as intended.
1) Clear Cache on app.
2) Multiple different camera apps
{
"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"
}
- no change
3) full factory reset - no change
4) Aftermarket ROM - LineageOS - no change
5) installed brand new camera purchased new from witrigs - no change
6) Z-Device test
Weird that it shows front facing (secondary) camera isn't working, but front-facing works fine. If I try to save a z-device log, the app crashes every time. And this is a fresh install.
There was no inciting incident or anything done to the phone, no fall or water damage or anything along those lines. I'm running out of ideas here, what else can I do/try to get this thing working?
Crossposted to Reddit
I would recommend performing the Unbrick guide.
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
ZVNexus said:
I would recommend performing the Unbrick guide.
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Click to expand...
Click to collapse
So I've just spent the past couple of hours trying to make that work. No luck on SO many steps. I imagine it's because the phone is not bricked? Is there another tool that would potentially accomplish the same thing?
marvin_rock said:
So I've just spent the past couple of hours trying to make that work. No luck on SO many steps. I imagine it's because the phone is not bricked? Is there another tool that would potentially accomplish the same thing?
Click to expand...
Click to collapse
This unbrick guide can be used even if the phone is not bricked.
What steps gave you problems?
Hi
I know mykindle is old but my autistic son uses it and he cannot handle change thus still using it.
I have no idea how this has happened at all. BUt now it seems when I reboot the device, the notifications bit has a notice saying "tap to access launcher debug settings".
When I tap this it takes me to those settings (which I have never seen before in any of the settings area) and I can quit out of it.
Why is this happening and is it a sign of a bigger problem?
Just to be clear, while I do have ADB enabled (in case I brick it and need to use kindle-unbrick in the future) nothing else is unusual. It is not rooted and I have never put a custom rom/system/launcher on it at all.
I can only guess that this change has accurred because either a game I have installed has tweaked something, or, a particular tablet-crash has pushed this into being.
So is it a problem? Can I stop it? Why has it happened?
Any thoughts would be massively appreciated please.
Thank you.
Alex
Hello. Sorry for the late reply. Anyways, I'm happy to help you. I also use a Kindle Fire HD 7 2012, so you can expect the best results. IDK the reason of the problem, it appeared in the same way as yours. But the fix is so simple, take a closer look at it:
{
"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"
}
Long-tap at the notification (some program appeared at the top, don't pay attention to it):
Tap "Manage Notification", as the arrow above suggests.
So, you must have the same screen, applications may differ. Tap the "Off" toggle in the right corner after the "Launcher", as arrow suggests, and go to the home screen. When you will look at notifications, a message must disappear.
If you experience any further problems, let me know. I'll try to respond in my free time.
And thank you for posting the question, without it I couldn't solve it (really).
Have a nice day!
HTH,
Anonymous