Related
I have a stock GN, not rooted yet. Today my phone automatically shut off and now it starts back up, google logo shows up and all those colors come on for couple of seconds and then the phone reboots itself.
I can press both volume up+volume down + power button and get into a menu which gives me the options of Start, Restart bootloader, recovery mode, and power off. I choose recovery mode but then it goes on to an android sign with exclamation mark. After that I can't seem to get anywhere. I have tried volume up +power, volume down+power, and volume up+down+power but nothing seems to work. It just keeps on rebooting it self.
Any solutions to this problem??
There are two possibilities:
1) Software problem. Since you were stock, this is unlikely.
2) Hardware problem. This is more likely, in my opinion.
If you want to eliminate 1) as a possibility, you can try this:
1. Download the GNex Toolkit here
2. Install it & get the drivers working on your computer (if you haven't already)
3. Unlock the bootloader by selecting Option 3 (it'll wipe your phone)
4. Flash factory stock rom by selecting option 8
5. Try it. If it works, congratulations. (if you want to re-lock your bootloader, use option 11)
If this doesn't work, relock your bootloader and send it in for warrantee. (most likely a hardware problem)
....
FredFS456 said:
There are two possibilities:
1) Software problem. Since you were stock, this is unlikely.
2) Hardware problem. This is more likely, in my opinion.
If you want to eliminate 1) as a possibility, you can try this:
1. Download the GNex Toolkit here
2. Install it & get the drivers working on your computer (if you haven't already)
3. Unlock the bootloader by selecting Option 3 (it'll wipe your phone)
4. Flash factory stock rom by selecting option 8
5. Try it. If it works, congratulations. (if you want to re-lock your bootloader, use option 11)
If this doesn't work, relock your bootloader and send it in for warrantee. (most likely a hardware problem)
Click to expand...
Click to collapse
So, I did the above method and after flashing the factory stock rom it won't start up anymore. It doesn't respond to anything at all. It seems I've bricked it
Is there any way to unrbick it now? I'm assuming I can't send it in for warranty either now if it's semi bricked. Unless it's been completely bricked which means there is still a chance of getting a replacement phone.
I have the same prob on rooted SGN
This morning I switched off the airplane mode to be available, system crashed and restarted. And then still the same again - booting / android logo / restart again.. /./. I am using Android Revolution HD 2.1.5, for last month with no problems.
I tried to boot into recovery, then wipe the cache and reflash rom and radio from sd, it is still the same. I can see all the files on my int. sd with no probs.
Please help.
I'm thinking it might be a hardware issue, but I'll wait for another member's opinion before confirming.
Solved!!!
That's what I thought - HW prob, but it seems that luck is on my side, I hope. It helped to get back on stock but with total deletion including int partition
Anyway thanks for support.
630263 said:
That's what I thought - HW prob, but it seems that luck is on my side, I hope. It helped to get back on stock but with total deletion including int partition
Anyway thanks for support.
Click to expand...
Click to collapse
Was your phone rooted or bootloader unlocked before the problem occurred?
Anyways I've sent in my phone for warranty, hopefully samsung will fix it.
So my phone company called me today and apparently Samsung told them that it's corrosion(?) problem. When I asked exactly what does that mean they said it's moisture damage or physical damage that probably caused it. But I'm confused how could my phone possibly get moisture damage inside an otter box. I know how delegate these devices are and I know how to take care of them.
Anyhow it'll be $90 to fix it. I had no other option so I asked them to go ahead with the repairs. So frustrated with Samsung to be honest. I never dropped my phone once, never had any water damage, phone was always inside the defender case. And I still have to pay them for fixing my phone even though it's not my fault.
That's quite worrying, I just started having boot loop problems today. I've had the phone since Feb 29th and not had a problem with it yet, but today it started boot looping. I went into recovery and did a factory reset, was alright for a couple of hours then it crashed, started bootlooping again. Running stock 4.0.2 unrooted, I'm wondering if flashing 4.0.4 might help.
I'm in the same boat.... unrooting stock 4.0.1 firmware - canadian version from Negri.
April 23rd my phone crashed and started boot looping. Google logo - reboot - Google logo - reboot
Factory reset worked. I installed less apps than I had before figuring perhaps an app was corrupting something.
Yesterday - it happened again. Phone crashed. Boot loop. Factory Reset worked. Installed even fewer apps.
We'll see what happens this time around. I am hoping it is just a software thing. Hoping 4.0.4 gets pushed soon too.....
I've been having the same issue, plus sometimes my home screen it would lock up and wouldn't let me do anything, so I did a battery pull and it would boot loop for a half hour.
After the 3rd time I just took it to my Verizon wireless store, and showed them the situation and they couldn't figure it out, so their sending me a replacement, which I'm not looking forward too, don't want a semi-used phone....
Via Galaxy Nexus [LTE]
Rebooting Issue Solved.
I was also a troubled Samsung Galaxy Nexus user and my phone kept restarting more than half a dozen times everyday. Most of the times when I switched between two or more applications, or when it was simply idle on my desk.
However, I found a solution (at least in my case). All I did was root my phone, install cwm recovery, and flash a custom rom after wiping cache and factory resetting the phone, It's been about 5 to 6 hours now since I flashed the custom rom and I haven't had a single reboot or hang since.
Others who face this problem, please give it a shot, who knows? You might save your Galaxy Nexus instead of sending it back to get a replacement or spend some money on it for repairs which aren't even required in the first place.
I also had this problem unrooted. I had to give it to Samsung for the warranty
Swyped on my Galaxy Nexus running AOKP with Trinity Kernel, overclocked to 1.4GHz
I got my nexus yesterday, almost immediately after first start it start to install JB from OTA.
I did buy 2000mAh samsung original battery and started straight with it. not even testing with 1750mAh bat.
after installing JB and needed softwares, it started to randomly reboot.
it rebooted even it was just in my pocket.
sometimes when I did do something, display freezed and after about 5sec it rebooted.
Now I did changed to original 1750mAh, and it havent boot at all couple hours, even I did play angrybirds space.
I wont dare to root it before I am very sure problem is with 2000mah battery.
2stardiver said:
I got my nexus yesterday, almost immediately after first start it start to install JB from OTA.
I did buy 2000mAh samsung original battery and started straight with it. not even testing with 1750mAh bat.
after installing JB and needed softwares, it started to randomly reboot.
it rebooted even it was just in my pocket.
sometimes when I did do something, display freezed and after about 5sec it rebooted.
Now I did changed to original 1750mAh, and it havent boot at all couple hours, even I did play angrybirds space.
I wont dare to root it before I am very sure problem is with 2000mah battery.
Click to expand...
Click to collapse
I could be wrong, but have you tried to clean the pin on the battery? Seems like battery and the phone isn't contracting too well
Swyped on my Galaxy Nexus running AOKP with Franco Kernel, overclocked to 1.4GHz
Little update, phone did continue rebooting with original 1750mAh battery also.
I did also reset with recovery mode, and after that it did also reboot one time.
like it uses all memory/cpu and when nothing to do reboot (like windows )
I also did flash stock rom with toolkit but no help.
I will test rooting phone and flash another rom, or is it useless ?
after using couple days, not yet rooted.
Phone works and wont reboot even in heavy stress. but sometimes it just reboots by own not a single program in task list.
might reboot right after previous reboot or take hours to reboot.
stupid phone
I have been done some research.
I did one more time reflash google stock with rootkit, and forgot lock phone, it was almost 3 hours by own in wifi, no reboots at all.
when I noticed that I forgot to lock it I rooted whole phone and installed paranoid android 2.13 with CWM.
Now Ive been using 2 hours without any reboot, installing software, setting things up and using apps.
I dont understand at all:silly:
edit: noup, yesterday evening one almost reboot, paranoid android did reset itself but didnt even reset uptime. so I didnt count that normal reboot.
but after wake up this morning, it did reboot once when I put in my pocket, another just lying on table, once activating bluetooth in my car.
going to send it back to seller.
I have a similar issue, although not quite the same. Last night my phone started boot looping - it managed to boot up to the lock screen, and I can use it for about a minute before it dies and then reboots. This continues again and again (I have to pull the battery to quit it).
I have stock JB on my GSM GN, but rooted with an unlocked bootloader / CWM. I restored my old CWM backup, and had the same issue. I also wiped the cache and the dalvik just to see if that helped, but I had the same issue. I then tried to do a factory reset in CWM, but after I did that the boot loop just got to the nexus logo and died, entering a new (slightly shorter) boot loop. I went back into recovery and reflashed my CWM backup, and that at least got me back to booting into android.
I can't understand what's going on - could it be a hardware issue if it will happily stay alive in recovery, but dies after 1-2mins of android?
Thanks for your help. If it is hardware then I hope I can reflash the stock recovery / bootloader and unroot through recovery... the phone doesn't stay on long enough to do it when it's booted into full android!
I was messing around with my phone and entered recovery mode (PhilZ Touch) and I kept tapping the empty part of the screen. Then the screen turned off, but on again after a few seconds. Then the phone wouldn't boot past recovery mode. I was stuck!
I researched the problem online and found another forum that posted a flashable "fix". So, I flashed it and then to my horror, realized that the zip was meant for a completely different phone!
Now my phone won't display anything on the screen, won't enter into Bootloader/Download Mode nor Recovery. I can't even do a Cold Reboot!
When I plug the phone into my computer though, Windows makes the USB connected dinging sound and attempts to install drivers but fails. In Device Manager, there is now a QHSUSB_DLOAD entry that appears and disappears depending on whether my phone is plugged in or not.
Does anyone know how to fix this and get the phone up and running again?
Preferably ASAP!? I literally have no phone... not even a landline!
Bro am in tha same boat...am about to send mines off to mobiletechvideos and they'll fix it for 50$ thats the only option ppl been saying...i tried the other way but its a headace and it dosent work for me ...
I ended up solving my problem, but not in the way I wanted. Since my phone was 100% dead, I went back to ATT since it was still under warranty. I told them a story about how the phone had been malfunctioning lately and then just completely died. They replaced the phone under warranty, so now I have a brand new one.
There definitely doesn't seem to be any easy way out of this problem once it strikes. I still don't know what happened to make the phone unable to boot out of recovery, even after wiping stuff, factory reseting, and reflashing roms. All I do know is that I have never had a problem with PhilZ until I started to rapidly tap the blank part of the screen (I like how it vibrates... I'm weird like that). This caused the recovery to never want to exit. Every time I reboot the phone, it automatically went to recovery, even after a full power off or battery pull.
Nevertheless, I am still going to root and mod my phone... just carefully.
You have a hard brick, which is nearly impossible to fix.
Sent from my LG-E980 using Tapatalk
I was just using my phone like normal today opening up the transit app at the bus stop and it randomly froze and restarted. After that, it only shows the initial Google screen and just keeps bootlooping, but never even gets to the part where the OS is loading (with the google animation). It was just on stock 6.0.1, MTC20K I think. Was not rooted. Bootloader was/is unlocked. Secure boot was/is enabled. It won't even go into stock recovery (when I select recovery it immediately goes back to the Google screen and continues as if I had never selected recovery). I have tried manually flashing each piece of the latest factory 7.0.0 build (NRD90S), but even though fastboot says everything was successful, nothing seems to have changed. Any ideas on how to fix this?
Same thing just happened to me. I have no root or anything but it will not boot the OS. I hope there is a fix for the problem because I really want to use the phone.
Same thing just happened to me.
Click to expand...
Click to collapse
No recovery for you either?
What was the latest Build you had when it was working fine?
To get into the recovery plug the phone into your computer. Go into fastboot (vol down + power) and select the power off option. When it turns off or goes to the charging screen, hold volume up + power to boot to download mode. Once in download mode, turn the phone off by holding vol down + power, then go back into fastboot and you should be able to now access recovery mode. This is what I did, and then flashed back to 6.0.1 and it runs fine now. No Idea why going into download mode allows you to then access recovery and get one clean boot, but it does
Druas said:
I was just using my phone like normal today opening up the transit app at the bus stop and it randomly froze and restarted. After that, it only shows the initial Google screen and just keeps bootlooping, but never even gets to the part where the OS is loading (with the google animation). It was just on stock 6.0.1, MTC20K I think. Was not rooted. Bootloader was/is unlocked. Secure boot was/is enabled. It won't even go into stock recovery (when I select recovery it immediately goes back to the Google screen and continues as if I had never selected recovery). I have tried manually flashing each piece of the latest factory 7.0.0 build (NRD90S), but even though fastboot says everything was successful, nothing seems to have changed. Any ideas on how to fix this?
Click to expand...
Click to collapse
Had the same thing happen - Now typing to you from my warranty replacement. Only option.
blackpaw78 said:
To get into the recovery plug the phone into your computer. Go into fastboot (vol down + power) and select the power off option. When it turns off or goes to the charging screen, hold volume up + power to boot to download mode. Once in download mode, turn the phone off by holding vol down + power, then go back into fastboot and you should be able to now access recovery mode. This is what I did, and then flashed back to 6.0.1 and it runs fine now. No Idea why going into download mode allows you to then access recovery and get one clean boot, but it does
Click to expand...
Click to collapse
Surprisingly, this worked. I forgot about download mode being an option. I also am not sure why this worked.
Edit: The phone boots, but is still randomly rebooting rather often. Not sure why, as everything was wiped and it should have been a fresh install of everything.
Another Edit: Back to boot looping/not getting to the Android loading screen. I didn't do anything other than let it download my apps. Maybe it is a hardware problem after all because it did successfully boot into Android a couple times.
This seems to be a common problem which I have, too. Looks like a whole series of devices had these issues. Currently LG is unable to repair my device because auf missing spare parts they say. So after effortless 3 weeks they will send my unrepaired device back to me with a letter for my dealer to get back my money.
Nice quality and service, LG - NOT!
Janny82 said:
This seems to be a common problem which I have, too. Looks like a whole series of devices had these issues. Currently LG is unable to repair my device because auf missing spare parts they say. So after effortless 3 weeks they will send my unrepaired device back to me with a letter for my dealer to get back my money.
Nice quality and service, LG - NOT!
Click to expand...
Click to collapse
That is actually pretty good outcome. Pixel phone is coming out soon.
Just had this happen today. Streaming music over Bluetooth and using another app, then tried switching tracks in Google Play Music and the app froze. Phone was unresponsive with app on the screen, then screen went off and wouldn't power on.
I finally got it on by holding down power for 30 seconds, but kept boot-looping to Google boot screen. I was able to get into fastboot mode and wipe everything and install the factory image. Still doing the same thing!
Just got off phone with Google. Told the rep everything I had tried and she is working on a replacement order. Supposed to call me back after chatting with higher level support. I wish they would just send me a new Pixel phone, or the 6P at least!
Ive had the same issue, where I just couldnt get passed the Google screen, the only solution for me to get back on to my phone was to let it happen until the battery died. After i let the battery die i turned it back on normally and connected it to my charger, it hasnt turned off since but im sure it will sooner or later
Edit: Issue is still happening but the only way for me to turn it back on is because the battery dies
This just happened to my and my wifes phones...all within a week of each other. I sent my wife's in about a week and a half ago to LG for warranty service. I am hoping that they are able to fix it...it is still in the 'repair' phase. I am trying to decide whether or not I want to send my phone in (which just died yesterday) before or after LG figures out what is going on with my wifes. In both cases, the phones were running fine and just shut down by themselves. The battery was not dead. Each time, the phone will boot to the Google screen, but then immediate shut down. I can get in to recovery and do actions within there, so I do not believe it to be a battery issue. However, as soon as you attempt to boot the phone, it will die.
Were you guys using stock setups or custom ones?
Sent from my Nexus 5X using Tapatalk
Its a 'known' issue. Google has confirmed there is an issue. Only solution appears to be a warranty replacement.
https://productforums.google.com/forum/#!topic/nexus/r29mtzLFS0g;context-place=topicsearchin/nexus/nexus$205x$20bootloop
---------- Post added at 10:22 AM ---------- Previous post was at 10:21 AM ----------
Psychofrantics said:
Were you guys using stock setups or custom ones?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
on both phones, bone stock. Only difference was I was running the beta before getting the stock OTA and my wife's was full stock and received the stock OTA.
I'm having the exact same problem here. Running Android 6.0.1, rooted. Phone suddenly turned off and won't start past the "Google" screen, except for once when it booted fully then immediately shut down, and three times when it loaded the boot animation and shut down. Bootloader is unlocked and TWRP recovery is installed. I can access fastboot but not recovery. I've tried the suggestion of booting into download mode then recovery again, but that didn't work. I have NOT tried updating to Android 7 yet, so this isn't the same boot loop issue faced by some other users. I don't want to try flashing stock yet and lose my data because I have a ton of Tasker profiles and tasks that I haven't backed up in months and I don't want to risk losing them! Serves me right...
Any suggestions?
Same HERE !!!!
the samed for me, and still now i can't light it up
sagshar said:
I'm having the exact same problem here. Running Android 6.0.1, rooted. Phone suddenly turned off and won't start past the "Google" screen, except for once when it booted fully then immediately shut down, and three times when it loaded the boot animation and shut down. Bootloader is unlocked and TWRP recovery is installed. I can access fastboot but not recovery. I've tried the suggestion of booting into download mode then recovery again, but that didn't work. I have NOT tried updating to Android 7 yet, so this isn't the same boot loop issue faced by some other users. I don't want to try flashing stock yet and lose my data because I have a ton of Tasker profiles and tasks that I haven't backed up in months and I don't want to risk losing them! Serves me right...
Any suggestions?
Click to expand...
Click to collapse
In my opinion your EMMC probably died, but you can try reflashing factory images to see if it is some other problem.
I would only try LGUP as a last resort because it will set Allow OEM unlocking to false and lock your bootloader, making further experimentation difficult.
BTW IMO the Android 7 bootloop probably isn't related to Android 7. I think they are just saying hardware problem (EMMC failure) that happens to show up more frequently when you have large updates of OS.
The way Google worded it, it made it seem like Android 7 is killing some hardware because of some incompatibility with just some isolated hardware builds.
I would suggest you let it keep booting and flash some factory images and sometimes EMMC will come back briefly and boot. If it does, immediately backup as much as you can before doing anything else.
Same deal for me and they are sending a replacement. This is a MAJOR blackeye!
Is your phone under warranty then? I am having the same problem as everyone on here. I've tried everything. I bought the phone just over a year ago though, so am a little concerned Google will turn around and tell me it's not their problem... Even though this is clearly a fault!
Greetings!
My girlfriend's Nexus 5X recently got stuck into boot loop. What I tried to fix it:
- Completely discharging it and charging it again
- Get into recovery mode - after going to the bootloader and choosing recovery mode, the phone reboots to the google logo
- I tried reflashing system, boot and recovery with TWRP - still the phone reboots when trying to get into recovery mode
What else can I try, having in mind that I can't get into recovery or boot it at all? The bootloader is unlocked, so I can try flashing anything.
You could try the BLOD-fix boot/recovery images on other threads in this forum.
If the phone is still in warranty (and even if it's not), I'd suggest getting in touch with your local LG repair people.
My wife's Google Nexus 5x died yesterday too after updating. Go to load recovery mode, and it does nothing. I can get into developer boot screen, but that's it... Nothing works. Her bootloader is locked though, so no flashing anything. Any idea on how to contact Google about getting a replacement?
Squealor said:
My wife's Google Nexus 5x died yesterday too after updating. Go to load recovery mode, and it does nothing. I can get into developer boot screen, but that's it... Nothing works. Her bootloader is locked though, so no flashing anything. Any idea on how to contact Google about getting a replacement?
Click to expand...
Click to collapse
No point contacting google, you have to go to the manufacturer LG wherever they happen to be in your country. A simple replacement phone will only potentially have the same issue - its a hardware problem and the PCB/motherboard must be replaced. I had a brand new phone (well 'brand new' as bought in 2016 but only unboxed last Tuesday lol) which didn't last 6 hours before getting overly hot and going into bootloop...tried a factory reset and got into setup but it shutdown and bootlooped again halfway through. Fortunately it was within the 2 year warranty period, so LG authorised the replacement motherboard on Thursday (1 hour wait as a walk-in service) and it has been fine (and cool!) ever since.
As a bonus, they upgraded it from 6.0 to 7.1.2, which LG considers the "latest" stable version for the 5x.
Hoping for some help or alternatives to fix my fiancee's Pixel XL. Last night the phone just kept flashing the 'G' logo on for 10 seconds, off for 10 seconds. She said the phone was close to dying before it happened, and I imagine it probably ended up draining the battery afterwards with the constant bootloop. Plugged it in all night but the charging screen didn't come up and would just stay in the bootloop. I could get it into the boot loader (power button and volume down), but it wouldn't go into recovery mode and instead would go right back to the boot loop.
So I tried a battery pack to charge it and it still didn't show charging, but I was able to get it into recovery mode eventually, but still boot loop afterwards. At one point, after leaving it on boot loader menu while attempting to charge, it eventually just tried to start itself and made its way to the second Google splash screen after the main G logo. Looked like it froze there though and I couldn't get it to that point again.
On my way to work this morning I tried plugging it into my car's USB port after powering off from the boot loader, and this time I kept flashing that it was charging (looked like it was 3/4 charged but not sure how accurate that is). So I got into recovery again and tried 3 factory resets consecutively. Still bootloop after attempting a startup afterwards. There was a similar issue a couple weeks ago where it looked like it was stuck in a bootloop, but it turned out the phone actually was dead that time and the charger wasn't working. Once we switched chargers it booted right up.
Any other suggestions or possibilities? I don't have much troubleshooting experience otherwise. Phone is fully stock, Google Fi. Any other info I can provide please let me know!
well, i'm not sure if it makes a difference, but now for some reason i can't get into recovery mode again. just goes into the boot loop. It also goes into the boot loop as soon as I plug the phone in to charge.
cgibsong002 said:
well, i'm not sure if it makes a difference, but now for some reason i can't get into recovery mode again. just goes into the boot loop. It also goes into the boot loop as soon as I plug the phone in to charge.
Click to expand...
Click to collapse
I assume you can't get into the bootloader using power and volume down buttons?
I have always been about to get into the boot loader. Actually i can get into recovery again as well. Seems if i let it sit for a while it'll go to recovery again. Maybe heat related.
My OG Pixel did the same thing to me one morning. I tried everything to revive my pixel but nothing worked. I did some digging and it turns out there is an issue with the storage on the phone. It's just a old fancy paper weight.
cgibsong002 said:
I have always been about to get into the boot loader. Actually i can get into recovery again as well. Seems if i let it sit for a while it'll go to recovery again. Maybe heat related.
Click to expand...
Click to collapse
If you can get into recovery, have you tried to sideload a full ota.zip (not an update)?
mozhno said:
If you can get into recovery, have you tried to sideload a full ota.zip (not an update)?
Click to expand...
Click to collapse
I haven't. I see that Google has all the ota's on their site. Is there a specific one that i might want to try? The same one? Go back a few? Will i even be able to sideload if my phone is fully stock?
Edit: sideload adb successfully but no change. I loaded the 6-5 ota which was what i already had.
cgibsong002 said:
I haven't. I see that Google has all the ota's on their site. Is there a specific one that i might want to try? The same one? Go back a few? Will i even be able to sideload if my phone is fully stock?
Edit: sideload adb successfully but no change. I loaded the 6-5 ota which was what i already had.
Click to expand...
Click to collapse
Sounds as if it's time to just try stuff and see what sticks. Regarding using an ota, it works if you are stock, and I sideload it even if I have installed majisk or installed another kernel. It typically works for me with fewer chances of blowing things up than flashing a stock image. Regarding what to try next, you may have already gone into recovery to check the install function to see if your storage still appears and try to flash anything that worked in the past; if you have a backup in twrp you could try to restore it; you could wipe cache and dahlvik; or even sideload an earlier ota version that worked. Since the 6-5 ota did not work nothing really jumps out to me as obvious. One final caveat, I once had to reboot a sideloaded ota a second time before my pixel booted properly. If I think of something else I'll post again.
I took it to ubreakifix and they told me that this is indeed a known issue with pixel xl's that they all suffered from a faulty motherboard and that is indeed the cause here. Said he thought there was actually a class action about it so I'll have to look into it. Really pisses me off that Google repeatedly told me it's not a known issue when their authorized repair center says it is.
Anyway i have a warranty with Upsie that I'm hoping to get this replaced with. We'll see.
cgibsong002 said:
I took it to ubreakifix and they told me that this is indeed a known issue with pixel xl's that they all suffered from a faulty motherboard and that is indeed the cause here. Said he thought there was actually a class action about it so I'll have to look into it. Really pisses me off that Google repeatedly told me it's not a known issue when their authorized repair center says it is.
Anyway i have a warranty with Upsie that I'm hoping to get this replaced with. We'll see.
Click to expand...
Click to collapse
Good luck
I'm assuming you tried booting into twrp recovery, going to reboot, and picked slot A ( or B if already in A) to reboot to and then rebooted system? A lot of the times simply switching slots from recovery and then rebooting is the fix. At least for me.
手机早期经历的情况得说明一下。root没有?Twrp是谁的?
Also, for anyone else having this issue, try rebooting into the bootloader. Connect to PC, and try fastboot --set-active=a
If this doesn't work, try booting back into your recovery image using fastboot boot *whatever you named your TWRP recovery image* and then flashing your twrp.zip again in recovery, and when rebooting if you're in slot B choose slot A in recovery to boot into.
Also keep in mind in Windows 10, it uses Powershell, so commands have to be typed in .\fastboot not just fastboot or it won't take it.