Hi, I'm new to the forum and to mobile operating system troubleshooting in general. I'm hoping to gain some insight into an issue I'm having.
I broke the screen on my mi mix 3 and after waiting for 2 months it finally arrived from Shenzhen. Yesterday I disassembled the phone, connected the new screen, turned it on, and it just went into a bootloop. I've never changed any part of the operating system on the phone before so I just assumed something was making a poor connection. I unplugged all the leads and plugged them back in again, checked that everything was firmly in place, and ended with the same result.
Fastboot will run sometimes for 10+ minutes and then the phone will just shut off, normal booting it will switch from "Mi" to "MIX" and the animation at the bottom of the screen will freeze after a couple clicks and it will loop back to restarting (but twice it has just ended with an all white screen). Rebooting from Mi Recovery mode results in the same.
From what I've seen I'll just need to follow this and flash the phone : https ://c.mi .com/thread-2504118-1-1.html?t=1590725045909
But my question, is there any possible way to try to fix this issue without loosing all my data and without using a back door method that may just brick the phone?
Thanks for any help, btw I still have the back glass off (I've tried with the fingerprint scanner plugged in, nothing) just in case it could somehow be a hardware issue.
So I've given up on trying to save my data, I don't really care much about that to be honest. I just really like this phone and would like to use it. I tried to flash the phone using Miui's official instructions but I can't unlock the bootloader because I can't download the app Miui's flash tool is requiring me to download on the phone to authorize it.
I guess I'll keep looking for a work around.
TheUnibomber said:
So I've given up on trying to save my data, I don't really care much about that to be honest. I just really like this phone and would like to use it. I tried to flash the phone using Miui's official instructions but I can't unlock the bootloader because I can't download the app Miui's flash tool is requiring me to download on the phone to authorize it.
I guess I'll keep looking for a work around.
Click to expand...
Click to collapse
I changed my display too and it's bootlooping. Did you solve this problem?
I changed my Display too...everything worked fine when I tested it. I unplugged it again to clean the phone and to bring on the glue..when I had the Screen on I restarted and had a black screen...so tried to remove the screen which then just broke...so I ordered a new one and a new display flex cable - I didn't glue the screen yet because I either experience black screens when the screen gets pushed against the backplate or the phone ends in a bootloop -> for the bootloop thingy I just waited for about 10 minutes and then it started normally so there must be something with replacement screens...I don't know whats going on -.-
Hi
Has anyone managed to get this fixed?
The screen works initially but after a while it goes blank, reboot I get the Mix logo not mix 5G. The replacement is a LCD.
Looks like it is stuck in bootloop as inserting sim does phone does not ring when I call it nor front face camera clunk when I slide it
Related
Hey All,
I posted this over on r/nexus5 as well, but figured id see if anyone here had any ideas as well.
I replaced my screen/frame earlier today and started having some trouble, figured I'd see if anyone else has had a similar experience and can give some advice.
I replaced my screen about a year ago, and all was well until a month ago. Dropped it again and cracked the screen, so I ordered another. Decided to spice things up and get a red frame as well, so this afternoon I took it apart. Tore it all down, and moved all the parts over to the new frame, everything went over nice and easy, and I got it all about together and booted it up. I see the Google logo with the unlock symbol, hangs out for about 15 seconds, and then reboots. Will do this for a bit until I power it down.
I read some other threads with some similar symptoms. A few people suggested the power button was being held down and causing the reboot, but that isnt the case here. I can get into the boot loader/fastboot screen, and can see it over adb. Soemone else suggested it was the long wide noddle cable not properly connected, so I've reseated that about a dozen times with no luck. I have checked all of my connections over a handful of times, but still the same deal.
So since my pc can see it in fastboot, I ran the nexus toolkit and did the force flash. Files transferred over and were written successfully, and as far as NRTK was concerned, it all went well. so it tells me the phone to reboot, and of course its the same 15seconds of google logo, rinse/repeat.
So I am thinking maybe my motherboard got damaged somehow during the transition? I just cant find any signs of damage, and I was pretty careful during the transfer. This was a replacement from China, but I figured since it shows the google logo and boot loader, the screen is indeed working... could it be the screen/digitizer preventing it from fully booting? I think its odd that root toolkit could still see the device, send data to it, and write it successfully.
Any thoughts would be much appreciated.
Actually now that I think about it, I will throw the guts back into the old frame in the morning to confirm if it is the new screen causing the problem or not.
So it turns out it was the chinese knock off screen that was the problem. put the guts back into my old phone, and all was well. Going to return it and get a new screen on the way.
I've been experiecing an issue like no other I can find online and I'd love to hear some opinions.
So, originally the problem was the phone's screen was going black straight after the Google logo, I had a hunch that it was a fault with just the screen as it was pretty badly smashed and seemed the phone was running in the background and you could get the backlight to come on. Then all of a sudden it would stop doing it and then start again intermittently.
I flashed to 6.0 to see if might be some random ROM error, but still exact same problems. Screen came back and then went again. So I grabbed a new screen and swapped out the part. Now at least I don't have a smashed screen and faulty digitizer.
Now the problem appears to be slightly worse. The phone gets to the Google logo again now but now it completely shuts down after it, but it still gets to fastboot! (Is fastboot stored on another chip than FW? If so that worries me.)
Any suggestions on getting some more info by troubleshooting would be golden. I've got some basic to intermediate experience with phone repairs, computing and electronics etc. so no need to simplify explanations too much.
Thanks in advance!
Have you tried re-flashing a stock ROM and then performing a factory wipe?
Hi,
I got my new Onelus 6 five days ago, and i installed the latest updates (ONEPLUS A6003_22_180614).
For the last three days, i've had issues with the screen going black. When i lock it and then try to unlock it, the screen doesn't switch back on, it keeps being dark.
I tried to reboot it several times (Volume button + power) but the screen is still black. The phones vibrates and the LED works but the screen doesn't.
I tried to remove the SIM card, but the problem is still here.
Sometimes after 100 trials, the reboot works, but the problem comes back as soon as i try to unlock it.
Do you know where this bug might come from ? Firmware problem or phone problem ?
I really don't know what to do... I hope you'll be able to help me !
Thank you
Sounds like you should contact OnePlus and it may be a defective phone. Maybe have to RMA it and have it replaced.
Krody said:
Hi,
I got my new Onelus 6 five days ago, and i installed the latest updates (ONEPLUS A6003_22_180614).
For the last three days, i've had issues with the screen going black. When i lock it and then try to unlock it, the screen doesn't switch back on, it keeps being dark.
I tried to reboot it several times (Volume button + power) but the screen is still black. The phones vibrates and the LED works but the screen doesn't.
I tried to remove the SIM card, but the problem is still here.
Sometimes after 100 trials, the reboot works, but the problem comes back as soon as i try to unlock it.
Do you know where this bug might come from ? Firmware problem or phone problem ?
I really don't know what to do... I hope you'll be able to help me !
Thank you
Click to expand...
Click to collapse
Have you tried a factory reset,or using the msmdownloadtool
My phone is brand new, I don't think a factory reset would change anything, does it ?
I want to see what OnePlus support can do for me before trying anything with softwares on my phone ! (I don't want to loose warranty)
Krody said:
My phone is brand new, I don't think a factory reset would change anything, does it ?
I want to see what OnePlus support can do for me before trying anything with softwares on my phone ! (I don't want to loose warranty)
Click to expand...
Click to collapse
I had a similar issue within a day of getting the phone. Nothing worked and had to send for replacement.
Try to reset to the factory settings. If this can't help you, refer to the service center or to shop where you bought the phone.
Hello. I'm having the same problem. Bought my phone couple days ago and it runs ONEPLUS A6003_22_180713. Don't know what to do sinse there is no OnePlus service centre in my city. Have your problem been solved? Have you done anything special?
Hi,
Unfortunately I had to send it back to the website where i bought it. I have been refunded, and i bought a galaxy S9+ (cheaper than the OnePlus 6 i got)
Even i got the same issue since Pie update.
Had rooted when it was on Oreo, when Pie (OOS 9.0) update came, it came with a new issue. Whenever I unlocked the phone, the screen would flash with blue lines and black background multiple times then show the lockscreen. And now with OOS 9.0.2 the issue went even more drastic, the screen kept on flashing while using apps. Even forced reboot didn't solve the problem. I had to power it off and leave it aside in nighttime. The issue has decreased but the lockscreen flashing still exists.
Temporary fix - https://thedroidguy.com/2018/07/how-to-fix-oneplus-6-that-wont-turn-on-easy-fix-1087099
If the issue increases, then I would restore Oreo ROM and relock the bootloader.
I need help tooo!
---------- Post added at 09:54 AM ---------- Previous post was at 09:50 AM ----------
amihir said:
Even i got the same issue since Pie update.
Had rooted when it was on Oreo, when Pie (OOS 9.0) update came, it came with a new issue. Whenever I unlocked the phone, the screen would flash with blue lines and black background multiple times then show the lockscreen. And now with OOS 9.0.2 the issue went even more drastic, the screen kept on flashing while using apps. Even forced reboot didn't solve the problem. I had to power it off and leave it aside in nighttime. The issue has decreased but the lockscreen flashing still exists.
Temporary fix - https://thedroidguy.com/2018/07/how-to-fix-oneplus-6-that-wont-turn-on-easy-fix-1087099
If the issue increases, then I would restore Oreo ROM and relock the bootloader.
I need help tooo!
Click to expand...
Click to collapse
Best solution is to keep the screen ON always. Or else that flashing bug will keep recurring.
But this is a temporary fix and not all would like to keep it Always ON
Same here from 3 days ago. OX 9.0.2
The phone hangs, No respond and must hard-restart the thing.
Same issue here,since the past 2 weeks.The phone screen keeps flashing when the phone is locked and even restarting the thing 20 times doesn't make the phone start.The LEDs work fine,the phone receives calls and messages too but the entire screen is black and unresponsive at the moment I face this issue.The moment I lock the phone the issue crops up and it's a pain to restart it every time it happens.
Hey guys.
So today my screen just randomly died. Didn't drop the thing. Used it the one second, the other second it was just dead. Phone still works. vibration, touch, sound etc still works, but the screen will not display anything, not even booting to recovery or fastboot.
Recently installed the global ROM. I got the phone in the original Chinese ROM. This poses a problem. Ordinarily, I would have sent this thing off to Xiaomi, but I am fearing that I may have voided my warranty by unlocking the phone and also installing the global ROM. So, I would greatly appreciate input on the following 3 points
1) What troubleshooting measures can I take to try and get the screen live again?
2) I have heard that I can flash the original ROM and this might help my case for a warranty claim. Problem is - 1) I cannot use the phone's interface, this might make it difficult to navigate TWRP. Unless I can control TWRP through the PC command line? 2) I never enabled USB debugging on the flashed ROM. However, i flashed something recently through TRWP (the Global ROM region fix), so I am hoping I can still flash things through TWRP.
3) If I cannot achieve the previous two points, is it worth sending this phone back to Xiaomi. I bought the phone through Gearbest and I live in South Africa, so I imagine safe shipping will set me back anything from 50USD to 150USD.
UPDATE: I managed to boot to TWRP - using the "adb devices" command brings up my device ID. Maybe there is hope for flashing the chinese ROM if I can simply navigate TWRP through the command line.
Is there not a fastboot image of the ROM you can flash? I'd send it back in anyway, chances are they'll just replace the screen and flash it back to stick.
invisiblewave said:
Is there not a fastboot image of the ROM you can flash? I'd send it back in anyway, chances are they'll just replace the screen and flash it back to stick.
Click to expand...
Click to collapse
Yes I believe there is. But I hope I can flash the original via MiFlash.
On another note - ive been doing some reading and apparently black screening on Xiaomi phones is actually quite common. I am beggining to think my black screen might be a software problem with having moved over to the global.
If anyone has some spare time - I would appreciate a step by step guide on how to revert to the chinese ROM (i am busy downloading it). I am hoping this might fix my black screen, and if not, then atleast I can send the phone back to xiaomi with stock ROM and make a warranty repair/refund
Thanks.
mi mix 3 very fragile
black screen, same happened to me, new phone, fell down and black screen. not broken , phone still vibrate, and ringing at a call . nothing shows up, useless . I had 3 xiaomi phones before, I broke the screen but they still work.
I destroyed a note4 screen after a car pass over it ( feel from my pocket driving my motorcycle,).and still work. I Have also a note5a prime with broken screen totaly working. Then I loved MI phones.
this mix3 is a ****, a little fall down,(whit gorilla protection in the screen and with
it the cover on it , and become garbage). I will not reapair it , will repair my note5a prime.
Lisent this : if you go fishing and your are not taking well care of your phone do not buy xiaomi mi mix3
it is slippery .
If you know any solution whitout replacing the display module, will appreciate. Regards. Martin
I had the same problem, do you have any solution without replacing the display?
Regards Andreas
my screen was replaced.. had same problems.
I broke my screen. Went to xiaomi hk and they fixed it. 860 hkd which I thought was fair.
Hello,
What happened:
I updated about two to three weeks ago to Android 10, looking forward for another happy year with my Pixel 1 128GB, bought on day one.
The very next morning I started a timer (default clock app) and wondered why it never rang. Boom, my Pixel is dead. Countdown to self destruction? Just kidding.
Of course the device was not dropped, no water or whatsoerver touched the phone recently. It just died silently on my table.
State summary:
Bootloader locked, was never unlocked
OEM Unlock is disabled / never enabled in the running system
Original Android 10 running for approx 12-16h
No root, custom rom, whatsoever. Stock android.
While still working, adb was connecting fine on my PC (I used scrcpy every now and then)
All that works now is if I press Vol up, Vol down and Power for approx. 10s, the phone vibrates. Then I can see in my PC that my Pixel is in fastboot mode. The screen stays off at all times. As my bootloader is locked, I can't do a lot, even flashing a zip with stock firmware won't work. If I type 'fastboot reboot bootloader' the device disappears from fastboot and never reaches adb.
I also tried to discharge my phone, thats why I write only now. Takes quite long if the screen is off to empty the battery in fastboot mode. All that happend now is that once I charge my phone the status LED is flashing red for some minutes. Now my phone can enter fastboot again, no bootlaoder, no screen.
Is there anything I can do to get to my data? I already bought a new phone, so disassembly without reasembly would be an option. After almost full three years rma is no option any more.
Greetings!
KobiP
KobiP said:
Hello,
What happened:
I updated about two to three weeks ago to Android 10, looking forward for another happy year with my Pixel 1 128GB, bought on day one.
The very next morning I started a timer (default clock app) and wondered why it never rang. Boom, my Pixel is dead. Countdown to self destruction? Just kidding.
Of course the device was not dropped, no water or whatsoerver touched the phone recently. It just died silently on my table.
State summary:
Bootloader locked, was never unlocked
OEM Unlock is disabled / never enabled in the running system
Original Android 10 running for approx 12-16h
No root, custom rom, whatsoever. Stock android.
While still working, adb was connecting fine on my PC (I used scrcpy every now and then)
All that works now is if I press Vol up, Vol down and Power for approx. 10s, the phone vibrates. Then I can see in my PC that my Pixel is in fastboot mode. The screen stays off at all times. As my bootloader is locked, I can't do a lot, even flashing a zip with stock firmware won't work. If I type 'fastboot reboot bootloader' the device disappears from fastboot and never reaches adb.
I also tried to discharge my phone, thats why I write only now. Takes quite long if the screen is off to empty the battery in fastboot mode. All that happend now is that once I charge my phone the status LED is flashing red for some minutes. Now my phone can enter fastboot again, no bootlaoder, no screen.
Is there anything I can do to get to my data? I already bought a new phone, so disassembly without reasembly would be an option. After almost full three years rma is no option any more.
Greetings!
KobiP
Click to expand...
Click to collapse
Pixel has an auto backup feature so everything should be backed up to the Google servers and if you use Google photos then your photos are most likely backed up. However if your screen is black, check the display closely if you can see even a small crack in your AMOLED display. I had a Galaxy J5 2017 that broke on the table and got a crack in the display and when an AMOLED display is cracked then the whole display goes black. It can happen from pressure on the display. Idk if you had cases on but the Pixel can flex quite a bit. If you see a crack then you can replace the display and be good as these AMOLED displays are so fragile. Otherwise it's a software related issue...
XperiaGUY47 said:
Pixel has an auto backup feature so everything should be backed up to the Google servers and if you use Google photos then your photos are most likely backed up. However if your screen is black, check the display closely if you can see even a small crack in your AMOLED display. I had a Galaxy J5 2017 that broke on the table and got a crack in the display and when an AMOLED display is cracked then the whole display goes black. It can happen from pressure on the display. Idk if you had cases on but the Pixel can flex quite a bit. If you see a crack then you can replace the display and be good as these AMOLED displays are so fragile. Otherwise it's a software related issue...
Click to expand...
Click to collapse
Hey,
some while passed, and I managed to get the most important data back by a Helium Backup Pro. That did not work initially due to a bug, but in the end I could get it to run. Google Backup did not help at all... I don't understand why and I can't check any more if it was enabled or disabled . Does Google Backup restore work only on new Pixel? My new Phone is a Xiaomi. Worst data loss was Google Authenticator, that is not backed up anywhere as it seems. I almost logged out of my Github Account forever, a ssh certificate plus github support saved my butt.
As I have 2 years old kid my phone was sometimes dropped. But until now I could not see any tiny damage at all (glass screen protectors broke more often). I will take a closer look at my screen the next days.
Cheers
Edit: I had a close look, tried to bend the phone. The Pixel is quite stable, I am impressed. Also I was very surprised that I could not see any scratch at the screen, the screen protectors did a good job over all the years. So I could not see a tiny crack or similar.
Macuway said:
Pixel has an auto backup feature so everything should be backed up to the Google servers and if you use Google photos then your photos are most likely backed up. However if your screen is black, check the display closely if you can see even a small crack in your AMOLED display. I had a Galaxy J5 2017 that broke on the table and got a crack in the display and when an AMOLED display is cracked then the whole display goes black. It can happen from pressure on the display. Idk if you had cases on but the Pixel can flex quite a bit. If you see a crack then you can replace the display and be good as these AMOLED displays are so fragile. Otherwise it's a software related issue...
Click to expand...
Click to collapse
google android backup is a **** show. you are lucky if it restores even half of what it promises. I used it with my pixel 2. set it up to back up everything . then that phone's screen died and i restored the backup to a new phone, only some apps came over, no app settings, and no SMS. it doesn't work. don't bother using it.