This is lengthy and in detail, please bear with my query.
I purchased Z2 plus (Z2132) 32 GB for my mom.
After getting the device I unlocked bootloader, flashed TWRP (latest) and simply flashed the latest stock ZUI through TWRP.
The ZUI that I flashed was the Stock Indian build 2.5.104 ST which was repackaged to be TWRP flashable.
After few weeks the device started screen flickering with no identifiable cause. Sometimes the screen would turn Blue, sometimes Black, but would always freeze. Finally the device one day went completely dark. I could see the backlight of the LCD screen, but the device would not display anything except Black.
I could reboot the device because I knew where the 'reboot' and 'power off' buttons would be on screen, but the screen would not turn ON even after reboots, only Black screen and LCD backlight.
My mom was annoyed because my tinkering led to this issue on an expensive device. Now the device was thrown into closet for later disposal.
Few months later I decided to repair the phone, but thought let's check if it still boots. It didn't boot so I put it on charge and Voila!, the screen shows 7% battery and charging. After pumping till 30% I turned it on and now it works like if nothing ever happened.
Now it has Official TWRP (3.2.3-0) installed (I updated its TWRP recently) and Bootloader unlocked too. The device is on Indian ZUI 2.5.104 ST (TWRP flashable build).
My query is, I am worried that the device will start flickering again and showing other symptoms. What can I do to ensure my mom can use it again as her daily driver? I am ready to relock bootloader etc. After searching a week (30+ hours) for solution, I have learned a lot of things about Z2 Plus, but still unclear about what step to take next.
My intention is to restore the device to a stable state where my mum can use it as a daily driver.
And preferably not lose the existing data on the device (though I realize this is too much to ask for and maybe not even possible).
Thank You for your help.
Edit: Some typos
Edit 2: Resolved through QPST flash and restoring warranty. Though the warranty restoration guide has errors and needs an update.
Navin said:
This is lengthy and in detail, please bear with my query.
I purchased Z2 plus (Z2132) 32 GB for my mom.
After getting the device I unlocked bootloader, flashed TWRP (latest) and simply flashed the latest stock ZUI through TWRP.
The ZUI that I flashed was the Stock Indian build 2.5.104 ST which was repackaged to be TWRP flashable.
After few weeks the device started screen flickering with no identifiable cause. Sometimes the screen would turn Blue, sometimes Black, but would always freeze. Finally the device one day went completely dark. I could see the backlight of the LCD screen, but the device would not display anything except Black.
I could reboot the device because I knew where the 'reboot' and 'power off' buttons would be on screen, but the screen would not turn ON even after reboots, only Black screen and LCD backlight.
My mom was annoyed because my tinkering led to this issue on an expensive device. Now the device was thrown into closet for later disposal.
Few months later I decided to repair the phone, but thought let's check if it still boots. It didn't boot so I put it on charge and Voila!, the screen shows 7% battery and charging. After pumping till 30% I turned it on and now it works like if nothing ever happened.
Now it has Official TWRP (3.2.3-0) installed (I updated its TWRP recently) and Bootloader unlocked too. The device is on Indian ZUI 2.5.104 ST (TWRP flashable build).
My query is, I am worried that the device will start flickering again and showing other symptoms. What can I do to ensure my mom can use it again as her daily driver? I am ready to relock bootloader etc. After searching a week (30+ hours) for solution, I have learned a lot of things about Z2 Plus, but still unclear about what step to take next.
My intention is to restore the device to a stable state where my mum can use it as a daily driver.
And preferably not lose the existing data on the device (though I realize this is too much to ask for and maybe not even possible).
Thank You for your help.
Edit: Some typos
Click to expand...
Click to collapse
May be screen hardware issues.
Related
I'm stuck and confused:
Had a Nexus 4 and 5 for years. Decided to upgrade this past November to the LG G4 (T-Mobile H811)
Got it to root without touching the boot loader.
In came MM and then I had issues of repeating the process.
I came across a solution, to unlock my bootloader. So I did it and managed to get my G4 rooted while running stock LG MM (H81120i).
Everything was running well for several months, but then I started to see erratic behavior. It would heat-up in my pocket for no reason. It would not save pictures. Connections via WiFi and LTE were breaking up. All in all, I wasn't happy and I missed the stock Google interface.
So I've decided to install CM13. Had many issues of getting it to work for several days, which included persistent closings of Google Play services (and many others) and not being able to make/receive calls (it would automatically reboot) After several different attempts, I managed to get it all working. Cleared/Wiped everything off my internal drive, installed the "LG-H81120i-Flashable.COMPLETE" and "cm-13.0-201605xx-NIGHTLY-h811" and "open_gapps-arm64-6.0-nano-201605xx", all back to back. And then installed manual everything as needed Gmail, Maps, etc.
Everything worked great for about 2-days, until then next morning my screen locked up. Then the phone rebooted. After the reboot, it lasted for about 10-15 seconds in CM13 and rebooted again manually. Continued to reboot over and over, till it then stopped booting with CM13. I thought that maybe I needed to install the latest CM13 zip file, but found I couldn't get into recovery. The first reboot screen, showing "Bootloader State: Bootloader unlocked? and the LG logo would be in a loop. During that time, I could feel the phone getting hotter and hotter.
Sometimes, the phone would boot up into CM fully and last for 5 to 10 minutes. Then reboot again and stay in the first reboot screen.
I managed to get into TWRP recovery and thought that putting back the stock MRA58K image would help. During the install in recovery, the phone rebooted! I never thought it could do that. Eventually I got the stock LG back-up up and running, but it didn’t help, and same rebooting occurred.
I'm stuck and out of options. I would like to get the phone BACK TO STOCK and then perform an RMA. I’m afraid that with the BOOTLOADER UNLOCKED that my RMA will be denied and I’m stuck with what I have.
So can the H811's bootloader be re-locked?
PiCASSiMO said:
I'm stuck and confused:
Had a Nexus 4 and 5 for years. Decided to upgrade this past November to the LG G4 (T-Mobile H811)
Got it to root without touching the boot loader.
In came MM and then I had issues of repeating the process.
I came across a solution, to unlock my bootloader. So I did it and managed to get my G4 rooted while running stock LG MM (H81120i).
Everything was running well for several months, but then I started to see erratic behavior. It would heat-up in my pocket for no reason. It would not save pictures. Connections via WiFi and LTE were breaking up. All in all, I wasn't happy and I missed the stock Google interface.
So I've decided to install CM13. Had many issues of getting it to work for several days, which included persistent closings of Google Play services (and many others) and not being able to make/receive calls (it would automatically reboot) After several different attempts, I managed to get it all working. Cleared/Wiped everything off my internal drive, installed the "LG-H81120i-Flashable.COMPLETE" and "cm-13.0-201605xx-NIGHTLY-h811" and "open_gapps-arm64-6.0-nano-201605xx", all back to back. And then installed manual everything as needed Gmail, Maps, etc.
Everything worked great for about 2-days, until then next morning my screen locked up. Then the phone rebooted. After the reboot, it lasted for about 10-15 seconds in CM13 and rebooted again manually. Continued to reboot over and over, till it then stopped booting with CM13. I thought that maybe I needed to install the latest CM13 zip file, but found I couldn't get into recovery. The first reboot screen, showing "Bootloader State: Bootloader unlocked? and the LG logo would be in a loop. During that time, I could feel the phone getting hotter and hotter.
Sometimes, the phone would boot up into CM fully and last for 5 to 10 minutes. Then reboot again and stay in the first reboot screen.
I managed to get into TWRP recovery and thought that putting back the stock MRA58K image would help. During the install in recovery, the phone rebooted! I never thought it could do that. Eventually I got the stock LG back-up up and running, but it didn’t help, and same rebooting occurred.
I'm stuck and out of options. I would like to get the phone BACK TO STOCK and then perform an RMA. I’m afraid that with the BOOTLOADER UNLOCKED that my RMA will be denied and I’m stuck with what I have.
So can the H811's bootloader be re-locked?
Click to expand...
Click to collapse
Since you live in the US your only option is to apply over voltage to the battery terminal and burn the mobo so that it wont even boot up. The exact method is somewhere around here in xda so you should look it up since you have no other choice
Edit: To answer your question: No
sirsomething said:
Since you live in the US your only option is to apply over voltage to the battery terminal and burn the mobo so that it wont even boot up. The exact method is somewhere around here in xda so you should look it up since you have no other choice
Edit: To answer your question: No
Click to expand...
Click to collapse
If I can't re-lock the bootloader, has anyone had the success of returning their phones under warranty? Through T-Mobile?
Hi All,
My Nexus 5x 32 GB phone suddenly died on me last night. The situation as of now:
1. Cannot boot normally. Shows Google logo and everything goes dark.
2. Can boot into Fastboot with holding down power and volume down buttons
3. But not able to go into recovery. When I select Recovery in Fastboot mode, it just tries to reboot and the screen stays dark. Nothing happens.
4. The bootloader is locked. I think OEM protection in Developer tools is on, so not able to unlock bootloader through Fastboot commands.
What an I do?? Factory reset would be great, if option is there.
Please help!! Thanks.
Try to flash Factory image by command adb and fastboot if your pc recognized your nexus 5x
unlock oem if necessary After
Funny enough, I've got a very similar issue
I can boot into recovery though, but there's a catch, and I think it applies to everything past boot, the phone freezes and restarts after like 3-5 seconds.
I can't boot to system, as it takes way too long to boot up, but I can only see the first panel of the recovery before it dies and restarts.
I have flash official images, and even TWRP recovery to see what I can do, but this doesn't work out in the long run, as the issues are ever persistent
Thanks for the quick replies!
Tried everything, including Nexus toolkit... But nothing worked. So I finally took it to service center as its still in warranty. They said the problem is hardware related and it might have happened because of recent update. They also said they have been getting lots of phones with this problem. So they they are replacing the motherboard free of cost. Wish they could have given a new phone
Once again, thanks all!
Dude that's wild, this same exact issue literally happened to me 2 weeks ago while I was on tour. Was on 7.1.1 (Pixel ROM to be specific) and my 5X just died on me out of nowhere. Absolutely the same things happening here, would boot up, go black, and then start bootlooping. Could access fastboot, but I couldn't get into recovery. Called Google and got a replacement because it was definitely hardware failure and I was still under warranty (just a few days past a whole year). I wonder if the new 7.1 betas are breaking peoples' phones
Sent from my Nexus 5X using Tapatalk
LG said if I have rooted my device, then it's not covered by warranty, and a 200-300 dollar (AUD) repair fee
I wonder if I can get this done free of cost though, I'm not the first person to have used this phone
Scratch. said:
LG said if I have rooted my device, then it's not covered by warranty, and a 200-300 dollar (AUD) repair fee
I wonder if I can get this done free of cost though, I'm not the first person to have used this phone
Click to expand...
Click to collapse
Have you tried flashing the stock images? If you can get to fastboot, you can flash the stock image and unroot your phone. You should also then be able to lock your bootloader (if it is unlocked) and then do your warranty at that point.
I only have been using stock images
root is not a problem, as itis indeed not rooted.
no matter what image you would boot, fhe system will crash after a few seconds, freezeframing whatever on display, be it the recovery icon, or the beggining of the boot animation
so people saying android 7.1.1 brooking devices, so will that be safe to upgrade the phone from 7.0 to 7.1 .1 when stable release will be available ?
Scratch. said:
I only have been using stock images
root is not a problem, as itis indeed not rooted.
no matter what image you would boot, fhe system will crash after a few seconds, freezeframing whatever on display, be it the recovery icon, or the beggining of the boot animation
Click to expand...
Click to collapse
Sounds like the hardware bootloop issue that has been hitting 5x devices hard lately. Mine started looping last week and I had to send it in.
Are you still within your 1 year manufacturer's warranty? If so, you can call LG and report the issue to them. Your device may get fixed, but it was also reported Thursday that LG has started issuing full refunds because they ran out of the needed part.
The company have started offering refunds
https://www.neowin.net/news/lg-to-issue-full-refunds-to-customers-with-faulty-nexus-5x-handsets
So my brother gave me his old G3 which never turned on again after 1 year or less of use, I believe the problem it had was the LG famous black screen or whatever, I never had a LG phone of my own, but I heard something about it and that it happens to up to the G4 (G5 maybe). I took it to a repair shop and they got it to turn on and make it functional, but it didn't last much longer than a month, it then started freezing completely to the state it's now, which turns on but then it freezes after 10 seconds or something.
I doubt this has anything to do with the software, but still I don't miss anything by trying. So far I've tried installing a custom ROM but there is a problem, it has no recovery nor fastboot installed, I don't even know how this is possible, and I know this is the case because when I try to access any of both I get the LG logo with some white letters on the top left saying some kind of boot security error.
I tried installing the fastboot img through my pc with sdk tools but idk if either the file was corrupted or what but I couldn't make it work (tested multiple I believe), and without the fastboot I can't install a custom recovery.
So I'm hearing any suggestions you guys might have before throwing this phone already.
Hello.
Oneplus 5t 8/128.
The system is in stock, the bootloader is locked.
Please tell me. When updating by air with official firmware, the phone becomes a brick, a black screen and a blue indicator are on. When recovering from an article on this forum, everything starts working again until the next update by air.
A month ago, an update came over the air to version (9.0.7-> 9.0.8), it downloaded, the phone turned off, turned on, and the update began. In the middle of the process, an error occurred("Installation failed. Reboot"), after which the device turn on, black screen and blue indicator is on.
I wrote to tech support where they restored it to me in the same way that in the article. Yesterday an update came (9.0.8-> 9.0.9) and the exact same thing happened.
Now the question. This is a problem in the mechanical part of the device (although previously everything was normally updated) (the phone dropped a couple of times from a short distance long time ago, but there are no chips and everything works, except for updates by air) or in software? What do you advise? Thanks for the answer
Download full zip and flash
Then check same thing occurs
Hi everyone.
I have been reading a few posts about bootloops in hopes that someone would have been facing the same issue as me. It seems my case is a bit different. I am desperate for some help!
My Max 3 came initially with a chinese ROM but I followed some wonderful tutorials here and I unlocked it and installed initially the xiaomi.eu ROM. Then a couple of months later I installed AOSiP ROM, I updated it a couple of times dirty flashing over it, and settled in exactly the "AOSiP-9.0-Pizza-nitrogen-20190719" build. And there i was, for 4 months, all stable, then suddenly today I was going to unlock the phone with my fingerprint and asked for password.
This happens exactly 1 time per day but I noticed that today it was the second time. Then doesn't matter how many times I put my password correctly, it would keep asking for my password. So I decided to restart the device... and then the bootloop issue started. It starts, reaches the moment in which the AOSiP logo shows and (not even 1 second until the logo shows) freezes, and restarts the device.
I can access the recovery without issues so I didn't panic yet, I backed up all I could, wiped everything I could, started from zero: firmware 9.9.3 + AOSiP-9.0-Pizza-nitrogen-20191117 + gapps. The bootloop still there, in exactly the same way. So at this point I have no clue what could be the reason. I was always careful not to trigger any anti-rollback, it was all going good, now not even with a full factory reset seems to work. I even reinstalled the recovery.
Any ideas? does anyone know what could I try next? Thank you very much advance.
I forgot to attach some logs. I got using the TWRP Advanced > Copy Log option.
Well, I guess I completely screwed it now. I had the brilliant idea to go back to some of the original steps I did way back and flashed an old xiaomi.eu ROM "xiaomi.eu_multi_MIMAX3_8.8.9_v10-8.1", that completely bricked the phone. Screen doesn't even turn on anymore. Is it the end for my Max 3?
diegoocampo said:
Well, I guess I completely screwed it now. I had the brilliant idea to go back to some of the original steps I did way back and flashed an old xiaomi.eu ROM "xiaomi.eu_multi_MIMAX3_8.8.9_v10-8.1", that completely bricked the phone. Screen doesn't even turn on anymore. Is it the end for my Max 3?
Click to expand...
Click to collapse
The mi max 3 has arb enabled, so flashing old rom can cause it to brick.
Have you tried different button combinations to enter fastboot? If you can get to fastboot, just flash a fastboot rom, if that works.
If the brick is caused by triggering ARB, then that may cause some issues, and may need an Authorized Account to flash the ROM from scratch, with some qualcomm flashing tools things.
Though, there may be some way to bypass the authorization for mi max 3 on the internet and have your device unbricked.
Thank you for your replies. Yes probably ARB, I thought my phone had never installed a ROM with ARB and so I was safe to install xiaomi.eu_multi_MIMAX3_8.8.9_v10-8.1 (which it is also to be pre-ARB), but I guess I made a mistake at some point.
Situation now:
- with Mi Flash I am getting the authorization error with almost any ROM, with very old ROMs I am not even able to start the flashing process
- with Qualcomm QFIL tool I always get an error "function: sahara_rx_data:237 Unable to read packet header. Only read 0 bytes". And I also tried with the patched files from here https://forum.xda-developers.com/redmi-note-5-pro/how-to/fix-arb-bricked-device-qfil-t3841780
I think at this point I tried everything that can be tried. My bootloader was unlocked, but at this point I am not even sure if its unlocked anymore since I can't see anything on the device screen.
The only positive thing is that the phone always shows under the Windows 10 device manager "Qualcomm HS-USB QDLoader 9008", so at least is a bit alive, and with the Mi Flash at least for some ROMs starts the flash process. I am not sure if disassembling it and trying things like removing the batter would make any difference.
If anyone knows any other way to bypass authorization please let me know.
Here I am back with another update:
- I fixed the full brick by disassembling the phone and disconnecting the battery, with the battery disconnected I could finally flash a Chinese ROM. That however was just the beginning... more problems came
- Common problem I guess is that after booting with that Chinese ROM i was getting a message about how the encryption was interrupted. This was easy, just changed the file system of Data and formatted it and it was fixed.
- Now I am stuck in another hard to solve problem. Any ROM that boots will not allow me to use WiFi or SIM cards. And the reason is that the IMEI is not set anymore. Reading about it I see that this is related with the EFS partition being corrupted. Nothing seems to work now. I don't have any EFS backup . Anyone knows how to fix the IMEI in this case?