Database Develop

System partition not booting up?

I'll try to keep this one explained simple
- Was running have boot loader unlocked and am rooted, was trickdroid
- Decided to try what else was out there for ROMS, switched to Renovate rom, was a downgrade from trickdroid in my eyes
- Decided to switch to one more rom before making the jump back to trickdroid, accidentally wiped internal storage data along with everything else
- After wasting most of my day messing with this crap, I finally got everything back to somewhat operational again
- My internal memory and Cache at one point were unmountable and read 0MB, had to do a factory reset via boot loader then a full wipe using TWRP
- Finally have trickdroid installed and its semi operational, aside from the fact that when I load it, it instantly has no service, no internet, nothing. It sends me to the launcher portion and there are no apps on there either. Shortly after it starts it will restart the device.
-After doing several restarts into recovery I have confirmed that the system partition consistently unchecks itself and I have already attempted fixing permissions several times and doing a system wipe and full ROM install again.. same issue to no avail.
- Last night I actually managed to pull up icons and programs, somehow, but again there was no system being loaded up
A little help please? I am in a state of a soft brick at this point, which is not bad considering I had a SUPER HARD brick earlier.
Help me, please. I just want to get this phone back to a functioning state!

Armygoat05 said:
- Finally have trickdroid installed and its semi operational, aside from the fact that when I load it, it instantly has no service, no internet, nothing. It sends me to the launcher portion and there are no apps on there either. Shortly after it starts it will restart the device.
-After doing several restarts into recovery I have confirmed that the system partition consistently unchecks itself and I have already attempted fixing permissions several times and doing a system wipe and full ROM install again.. same issue to no avail.
- Last night I actually managed to pull up icons and programs, somehow, but again there was no system being loaded up
A little help please? I am in a state of a soft brick at this point, which is not bad considering I had a SUPER HARD brick earlier.
Help me, please. I just want to get this phone back to a functioning state!
Click to expand...
Click to collapse
A hard brick is unrecoverable. It means your phone is literally as responsive as a brick. I would say your phone is pretty functional if the actual OS loads.
Anyway, have you tried RUU? That usually brings everything back to normal. Be sure to use the correct one, and note that you will lose EVERYTHING. Even root.
EDIT: Try this.

sauprankul said:
A hard brick is unrecoverable. It means your phone is literally as responsive as a brick. I would say your phone is pretty functional if the actual OS loads.
Anyway, have you tried RUU? That usually brings everything back to normal. Be sure to use the correct one, and note that you will lose EVERYTHING. Even root.
EDIT: Try this.
Click to expand...
Click to collapse
So I did try using this link and downloaded the full zip file and unzipped as per instructions of QBKing77 off of youtube, then clicked setup.exe within the folder which was unzipped, but after it ran through its setup process, nothing else popped up? I tried doing it as well through hasoons all in one toolkit but while that worked, it didn't work as expected and it just stayed at the black htc screen. I'm lost at the moment.

Trickdroid works on the Sprint variant?
Sent from my HTCONE using xda premium

sounds to me like you flashed an international rom and messed up your partitions
run an RUU

flex360 said:
sounds to me like you flashed an international rom and messed up your partitions
run an RUU
Click to expand...
Click to collapse
That's what I was thinking too.
Sent from my HTCONE using xda premium

We should add to the Q/A sticky the names of ROMs NOT to flash like Android revolution, trickdroid, etc.
P.S. He tried RUU, he's having trouble.

sauprankul said:
We should add to the Q/A sticky the names of ROMs NOT to flash like Android revolution, trickdroid, etc.
P.S. He tried RUU, he's having trouble.
Click to expand...
Click to collapse
I'll add it right now
Done Q21

bigdaddy619 said:
I'll add it right now
Click to expand...
Click to collapse
Sweet, will save a lot of noobs a lot of trouble.

sauprankul said:
Sweet, will save a lot of noobs a lot of trouble.
Click to expand...
Click to collapse
Maybe if they actually read it haha

bigdaddy619 said:
Maybe if they actually read it haha
Click to expand...
Click to collapse
It wouldn't be as bad if the Int'l forum was marked so. If I were new, I would assume all HTC Ones are the same too.

sauprankul said:
It wouldn't be as bad if the Int'l forum was marked so. If I were new, I would assume all HTC Ones are the same too.
Click to expand...
Click to collapse
Very true there are HTC One forums for:
International
Sprint
AT&T
T-Mobile
So it could be confusing to some

Hello from my finally unbricked one! Turns out I was having issues with the computer itself launching installshield so it wouldn't keep the factory RUU running. I did it from a different computer and it did it in stride.. I'm so happy to have this thing back. So on a sidenote I had to rwlock bootloader and then I had to reload the factory RUU.

[Q] Am I Bricked? Won't go past lockscreen on Sense Roms, reboots on GE Roms.

Bought a T-Mobile HTC One off a guy (never a good start), who said it was rooted with a GE 4.3 Rom and randomly rebooting. He said it was given to him like that... In my mind, I thought it was probably a bad flash and an easy fix. Wrong.
The Rom was bigixe Android 4.3 JWR66V Google Play Ed. - Rooted/Busybox/Odexed/Deodexed (8/6/13). It didn't necessarily reboot randomly, it would load, you could run it like normal and then it would consistently reboot about 2 minutes after boot. It was rooted, unlocked, CWM recovery, and S-On with HBOOT 1.44.
I then flashed Android Revolution HD 22.0 without any problems, but this time, it would load to the lockscreen and not give me the initial setup. As soon as i unlocked, it would go the HTC screen and freeze for about 3 minutes before rebooting. I tried several Roms, both Sense and GE, and the same thing would happen with each Rom respectively. From here I did everything imaginable: Relock and flash stock, format data, flash firmwares, download RUU's, sideload, RRU zips, downgrade to turn S-OFF...everything.
Still no better than when I started. My question is, did the previous owner have S-OFF and then turned S-ON again with some altered partition or would that have caused a more severe brick? Did I miss something?
Any help is appreciated.

Have you tried the fastboot clear cache command? I know it mainly helps when stuck on the boot logo screen, but there's a chance it may work in your situation as well.
You may also want to try running the RUU found directly on HTC's dev site
Sent from my HTC One using Tapatalk 4

Still no luck
Thrashlord said:
Have you tried the fastboot clear cache command? I know it mainly helps when stuck on the boot logo screen, but there's a chance it may work in your situation as well.
You may also want to try running the RUU found directly on HTC's dev site
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
I set everything back to stock and ran the RUU downloaded from HTC, tried the erase cache command, still same thing. Thank you for the suggestions though.

That sound messed up, wow....
Since you wiped everything software related, (except the partition structure, you could try to read that out of the phone, and cross check it with another device), it sounds like a hardware problem..
But! If its a hardware problem, why is it then crashing at specific events (eg, lockscreen unlock), and why is the behaviour consistent? THAT points to software.. Possibly try to dump what the system is doing during a crash. Could it be the software that reaches out for some hardware, that then malfunctions, causing the crash? Possibly RAM issues?
Kind Regards
TwinAdk

Fixed reboot, no service
TwinAdk said:
That sound messed up, wow....
Since you wiped everything software related, (except the partition structure, you could try to read that out of the phone, and cross check it with another device), it sounds like a hardware problem..
But! If its a hardware problem, why is it then crashing at specific events (eg, lockscreen unlock), and why is the behaviour consistent? THAT points to software.. Possibly try to dump what the system is doing during a crash. Could it be the software that reaches out for some hardware, that then malfunctions, causing the crash? Possibly RAM issues?
Kind Regards
TwinAdk
Click to expand...
Click to collapse
Managed to finally fix the reboots occurring every 3 minutes by flashing this stock GE rom 7_UL_JB43_STOCK_UI_S_Google_WWE_3.06.1700.10. However, I cannot get it to read my SIM and have no service. The baseband and iemi is listed as unknown.
Since the reboot issue was fixed, I tried to go back to stock, but if I run anything other than that GE rom, the same issue continues. Any more thoughts?

[Q] Help! Can't reboot into new rom!

Hi, so I made the dumb mistake of deleting the OS from my HTC One (Sprint). I got the One deodexed stock Jelly Bean rom from Android Revelution HD. Sideloaded it onto the phone and went into TWRP recovery to install the zip. It says the install was successful, however, when I hit reboot, it doesn't start into the rom. It just stays on the bootloader screen and sometimes I have to fastboot flash a recovery in order to get back into TWRP. I have tried fastboot erase cache and have also tried factory resetting it and wiping cache/dalvik cache before I install. Nothing seems to work. Any ideas???

tale419 said:
Hi, so I made the dumb mistake of deleting the OS from my HTC One (Sprint). I got the One deodexed stock Jelly Bean rom from Android Revelution HD. Sideloaded it onto the phone and went into TWRP recovery to install the zip. It says the install was successful, however, when I hit reboot, it doesn't start into the rom. It just stays on the bootloader screen and sometimes I have to fastboot flash a recovery in order to get back into TWRP. I have tried fastboot erase cache and have also tried factory resetting it and wiping cache/dalvik cache before I install. Nothing seems to work. Any ideas???
Click to expand...
Click to collapse
If it was me, I would just RUU and start over. Once that is done, boot it up transfer your rom over to the internal storage via usb while booted up. Then go back into fastboot, flash newest TWRP recovery and flash your rom. Also I don't think that rom supports the Sprint Variant at least that what is says under the details section. That could be part of your issues as well. I usually stay away from roms that weren't specifically made for my version but that's just me.

uckaus was
Sim-X said:
If it was me, I would just RUU and start over. Once that is done, boot it up transfer your rom over to the internal storage via usb while booted up. Then go back into fastboot, flash newest TWRP recovery and flash your rom. Also I don't think that rom supports the Sprint Variant at least that what is says under the details section. That could be part of your issues as well. I usually stay away from roms that weren't specifically made for my version but that's just me.
Click to expand...
Click to collapse
You're right. I checked and it's not compatible with Sprint. I downloaded the 31.6, but now I can't install it? Something about error with partitions. I've thought about doing the RUU but thought it might be more difficult.

tale419 said:
You're right. I checked and it's not compatible with Sprint. I downloaded the 31.6, but now I can't install it? Something about error with partitions. I've thought about doing the RUU but thought it might be more difficult.
Click to expand...
Click to collapse
RUU is easy. Just boot into fastboot, connect usb and launch the RUU. Once it's done then flash recovery and a different rom. It won't affect your s-off either if you are. I am currently using stock with goodies. It's a little older but it's rock solid, bloat is all gone, no blink feed and awesome battery. Will be switching once kit kat officially drops.
Sent from my HTCONE using XDA Premium 4 mobile app

Sim-X said:
RUU is easy. Just boot into fastboot, connect usb and launch the RUU. Once it's done then flash recovery and a different rom. It won't affect your s-off either if you are. I am currently using stock with goodies. It's a little older but it's rock solid, bloat is all gone, no blink feed and awesome battery. Will be switching once kit kat officially drops.
Sent from my HTCONE using XDA Premium 4 mobile app
Click to expand...
Click to collapse
RUU was SO much easier! Only problem is I can't get service now? It says I have Sprint service and there are some signal bars, but it doesn't say 3G or anything. Anyone have this problem after RUU?

tale419 said:
RUU was SO much easier! Only problem is I can't get service now? It says I have Sprint service and there are some signal bars, but it doesn't say 3G or anything. Anyone have this problem after RUU?
Click to expand...
Click to collapse
Try resetting the radio. ##786 then reset. You will need your MSL there are a few ways to get it. When I first activate a new phone, I always get in the habit of getting the MSL so I just have it. If you don't have it just call Sprint and ask. If you get some moron CSR just hang up and call back don't argue. I also don't like to use the word MSL when asking, I always say reset code so you can reset your phone most the time they will give it to you.

Sim-X said:
Try resetting the radio. ##786 then reset. You will need your MSL there are a few ways to get it. When I first activate a new phone, I always get in the habit of getting the MSL so I just have it. If you don't have it just call Sprint and ask. If you get some moron CSR just hang up and call back don't argue. I also don't like to use the word MSL when asking, I always say reset code so you can reset your phone most the time they will give it to you.
Click to expand...
Click to collapse
I did an easy fix and just re-inserted the sim card in hahaha. Hopefully it stays, but if I have any problems I'll definitely call them. Thanks for your help guys!

[Q] HTC One M7 Soft Brick (Stuck on HTC logo during boot)

Hi everyone,
I'm hoping that someone can provide some assistance with my HTC One that won't load past the HTC One logo. I've never done any rooting or unlocking, the phone was stock when this happened. Last week the battery drained on me (not the first time it happened), I came home and put the phone to charge and when I tried to turn it on it wouldn't load past the HTC logo. I don't have any custom recovery on the phone. I am able to access the bootloader menu. I tried resetting the phone and wiping the cashe but that didn't help.
I downloaded ABD setup but would like some assistance before I try anything. I've been reading and "googling" a lot over the past week but it all seems a little over my head.
I'm a total noob when it comes to cell phones but I'm willing to learn.
Any help is greatly appreciated! Thanks in advance for your time.

xdabrainiak said:
Hi everyone,
I'm hoping that someone can provide some assistance with my HTC One that won't load past the HTC One logo. I've never done any rooting or unlocking, the phone was stock when this happened. Last week the battery drained on me (not the first time it happened), I came home and put the phone to charge and when I tried to turn it on it wouldn't load past the HTC logo. I don't have any custom recovery on the phone. I am able to access the bootloader menu. I tried resetting the phone and wiping the cashe but that didn't help.
I downloaded ABD setup but would like some assistance before I try anything. I've been reading and "googling" a lot over the past week but it all seems a little over my head.
I'm a total noob when it comes to cell phones but I'm willing to learn.
Any help is greatly appreciated! Thanks in advance for your time.
Click to expand...
Click to collapse
Honestly, if this is not a result of tampering, you might want to check into warranty. HTC Sync might have a recovery option, never used it, you could check there. Any solution I would have would void said warranty. It's not entirely uncommon for software to corrupt upon power loss.. rare indeed but it happens. See if you warranty is good have a new one in no time.

How about this ?
MrLizm said:
Honestly, if this is not a result of tampering, you might want to check into warranty. HTC Sync might have a recovery option, never used it, you could check there. Any solution I would have would void said warranty. It's not entirely uncommon for software to corrupt upon power loss.. rare indeed but it happens. See if you warranty is good have a new one in no time.
Click to expand...
Click to collapse
I have pretty much the same issue except the fact that mine was nit battery drained. It just crashed on some app and then device went to boot loop. Deleted the cache and factory reset thing. No luck.
Best bet is warranty get it replaced. Bloody so many devices going blank just like that !!! Htc should now make a statement on this!!
Else there is a long way , Some steps broadly.. if you on the latest android version and with a never tampered device.
Spend some time on this forum for each of those steps.
Unlock Bootloader (htcdev.com)[all data is gone] - Twrp recovery flash (2.7.1 recommended) -> Adb Sideload - Custom Rom (Android revolution 8.1 recommended)- If okay with custom rom stop here. And enjoy your device.
Else continuing ... Custom Rom -> Use firewater to do S-off --> RUU.exe of the latest Stock Build of your CID and MID (htc1) guru.com --> OTA updates to latest builds by HTC.
Notes :
1) RUU doing with S-on on a older version of android will leave you with bricked device.
2)Adb is needed to run the S-off firewater. So you need a working Android OS , thus the custom rom.
3)Once S-off , make sure you clear the tampered flag and relocked flag in bootloader. Just in case you need to visit the HTC service center later.
I want to the above as same situation. Stuck at the adb sideload step.

anirudhgargi said:
I have pretty much the same issue except the fact that mine was nit battery drained. It just crashed on some app and then device went to boot loop. Deleted the cache and factory reset thing. No luck.
Best bet is warranty get it replaced. Bloody so many devices going blank just like that !!! Htc should now make a statement on this!!
Else there is a long way , Some steps broadly.. if you on the latest android version and with a never tampered device.
Spend some time on this forum for each of those steps.
Unlock Bootloader (htcdev.com)[all data is gone] - Twrp recovery flash (2.7.1 recommended) -> Adb Sideload - Custom Rom (Android revolution 8.1 recommended)- If okay with custom rom stop here. And enjoy your device.
Else continuing ... Custom Rom -> Use firewater to do S-off --> RUU.exe of the latest Stock Build of your CID and MID (htc1) guru.com --> OTA updates to latest builds by HTC.
Notes :
1) RUU doing with S-on on a older version of android will leave you with bricked device.
2)Adb is needed to run the S-off firewater. So you need a working Android OS , thus the custom rom.
3)Once S-off , make sure you clear the tampered flag and relocked flag in bootloader. Just in case you need to visit the HTC service center later.
I want to the above as same situation. Stuck at the adb sideload step.
Click to expand...
Click to collapse
How exactly are you stuck at adb sideload?
assuming you have your custom rom, you would:
boot to recovery, select advanced then sideload...
from your pc you goto your ADB folder open cmd and type: adb sideload filename.zip
this pretty much sums it up

So I've been fiddling with the phone trying to fix it, looking at youtube videos and reading the forums but I'm still stuck. It's a Telus phone and it is not under warranty anymore... or it would have gone back already. I almost want to just give it back hahaha :laugh:
I managed to unlock to bootloader... that was pretty simple. The next thing I tried to do was do an adb sideload of twrp... it worked fine until I went into recovery mode and the phone was frozen there. I used an older version of twrp that was suggested 2.7.1 I believe. I noticed on the twrp website that in order to get it on your phone you need to be S-off.
How do I get some sort of custom recovery on my phone? It feels like whatever I do there is always some glitch or little thing that I failed to do.

xdabrainiak said:
So I've been fiddling with the phone trying to fix it, looking at youtube videos and reading the forums but I'm still stuck. It's a Telus phone and it is not under warranty anymore... or it would have gone back already. I almost want to just give it back hahaha :laugh:
I managed to unlock to bootloader... that was pretty simple. The next thing I tried to do was do an adb sideload of twrp... it worked fine until I went into recovery mode and the phone was frozen there. I used an older version of twrp that was suggested 2.7.1 I believe. I noticed on the twrp website that in order to get it on your phone you need to be S-off.
How do I get some sort of custom recovery on my phone? It feels like whatever I do there is always some glitch or little thing that I failed to do.
Click to expand...
Click to collapse
TWRP 2.7.1.1 is here, http://forum.xda-developers.com/showthread.php?t=2173870
Main advise is to follow steps, Do them no matter how trivial. Usually things go wrong for the littlest reason. You want to make sure you have the most current version of fastboot and adb tools on your computer when working with your HTC. Other good things to pay attention is use OEM cables and take note that you are plugged directly into a USB 2.0 on the board, not a port on the front of PC, a hub or extender..

xdabrainiak said:
So I've been fiddling with the phone trying to fix it, looking at youtube videos and reading the forums but I'm still stuck. It's a Telus phone and it is not under warranty anymore... or it would have gone back already. I almost want to just give it back hahaha :laugh:
I managed to unlock to bootloader... that was pretty simple. The next thing I tried to do was do an adb sideload of twrp... it worked fine until I went into recovery mode and the phone was frozen there. I used an older version of twrp that was suggested 2.7.1 I believe. I noticed on the twrp website that in order to get it on your phone you need to be S-off.
How do I get some sort of custom recovery on my phone? It feels like whatever I do there is always some glitch or little thing that I failed to do.
Click to expand...
Click to collapse
Download the latest version of TWRP for your phone
Place in your adb folder
Reboot to bootloader
Fastboot flash recovery "name_of_recovery".img
Fastboot erase cache
Reboot bootloader again and boot into recovery

Phone Die or did I kill It?

So here's the deal. I use WUGS and don't manually do stuff.. Yes this makes me a weak individual and I bow to the people who can manually flash and their omniscient power. I bought a 64gb google version Nexus 6 about a month ago when the price dropped. I had issues with it just shutting off every once in a while, but tried rooting and romming and no matter what the rom was, about a day in it would just force shutdown... In the early days I could access TWRP and even if I restored to a stock back up, only one time did it just restore and boot up, the rest of the time it would just not boot up..... I called about an RMA and put it back to complete stock, unlocked, trying to get it working, just thought maybe it was something I did and if so, I wanted to try stock. I flashed it, a few times I even made it to the set up screen on the initial boot, but after failing it didn't matter if I navigated to stock recovery and wiped or anything. Only thing I can do is access stock recovery and bootloader and all that and try to power it on but it just says google for a few seconds then shuts down. . Last night I got worried and relocked the bootloader so I could send it back and not have Moto void me on that... Was this always just a faulty phone or is it more likely something i did? I appreciate any intelligent thougts.
Dustin

kickenwing13 said:
So here's the deal. I use WUGS and don't manually do stuff.. Yes this makes me a weak individual and I bow to the people who can manually flash and their omniscient power. I bought a 64gb google version Nexus 6 about a month ago when the price dropped. I had issues with it just shutting off every once in a while, but tried rooting and romming and no matter what the rom was, about a day in it would just force shutdown... In the early days I could access TWRP and even if I restored to a stock back up, only one time did it just restore and boot up, the rest of the time it would just not boot up..... I called about an RMA and put it back to complete stock, unlocked, trying to get it working, just thought maybe it was something I did and if so, I wanted to try stock. I flashed it, a few times I even made it to the set up screen on the initial boot, but after failing it didn't matter if I navigated to stock recovery and wiped or anything. Only thing I can do is access stock recovery and bootloader and all that and try to power it on but it just says google for a few seconds then shuts down. . Last night I got worried and relocked the bootloader so I could send it back and not have Moto void me on that... Was this always just a faulty phone or is it more likely something i did? I appreciate any intelligent thougts.
Dustin
Click to expand...
Click to collapse
There is honestly no way to tell. We would be guessing. You cannot unlock the bootloader now either, so we can't even get you to manually flash stock to test.
You can try a "fastboot format userdata" and "fastboot format cache" to see if that helps you boot, otherwise, nothing you can do.
We do recommend that you only use toolkits if you know what they are doing in the background. It really isn't difficult. In fact, I wrote a very simple thread to explain in in General > Sticky roll-up. None of this has anything to do with omniscience. Though, that particular skill would be helpful to us to answer your actual question.

Lol thanks dude. I'll try anything. I figured out how to run simple commands, but when it comes to putting the files in the correct directory I think so that it reads it... But, you're saying now that I'm locked, stock, and not loading up, I could try to do fastboot and format data and cache? Is this a more in depth wipe than just wiping in stock recovery does ? I assume now that I locked, I can't flash firmwares without voiding my warranty or? I was actually on chroma and it shutdown, so I went to stock, started typing gmail log in on initial set up and it shut down.. .So as far as I know. I'm stock... and locked..

kickenwing13 said:
Lol thanks dude. I'll try anything. I figured out how to run simple commands, but when it comes to putting the files in the correct directory I think so that it reads it... But, you're saying now that I'm locked, stock, and not loading up, I could try to do fastboot and format data and cache? Is this a more in depth wipe than just wiping in stock recovery does ? I assume now that I locked, I can't flash firmwares without voiding my warranty or? I was actually on chroma and it shutdown, so I went to stock, started typing gmail log in on initial set up and it shut down.. .So as far as I know. I'm stock... and locked..
Click to expand...
Click to collapse
Format is not a wipe. It will wipe, but unlike a wipe, it will recreate the file system. A corrupt file system can prevent boot so worth trying.
If the BL is locked and won't unlock, that's about all you can try.
Boot.to recovery just incase you have TWRP recovery still

danarama said:
Format is not a wipe. It will wipe, but unlike a wipe, it will recreate the file system. A corrupt file system can prevent boot so worth trying.
If the BL is locked and won't unlock, that's about all you can try.
Boot.to recovery just incase you have TWRP recovery still
Click to expand...
Click to collapse
tried and the process failed... I have it back to status 2 and not rooted and it died after flashing stock so I assume sending it back is okay.. my replacement is here today. I'm unlocking and rooting as we speak

I erased everything on my Nexus 6 and then tried using the flash-all.bat from image-shamu-lmy48i.zip.
It failed saying could not allocate so many bytes.
Accidentally i did lock my bootloader using fastboot oem lock.
Now cant load anything and my phone doesn't boot.
When i try fastboot oem unlock it says enable that option under developer options.
I am now with a brick Nexus 6 please help me out of this situation.

openbook said:
I erased everything on my Nexus 6 and then tried using the flash-all.bat from image-shamu-lmy48i.zip.
It failed saying could not allocate so many bytes.
Accidentally i did lock my bootloader using fastboot oem lock.
Now cant load anything and my phone doesn't boot.
When i try fastboot oem unlock it says enable that option under developer options.
I am now with a brick Nexus 6 please help me out of this situation.
Click to expand...
Click to collapse
No matter how many times this question is asked, unfortunately, the answer is still, there is no fix.
This has been happening since the nexus 6 went to 5.1 and has been documented numerous times. A bit of reading beforehand is all that is needed to avoid this situation.
RMA is the only option.

Evolution_Tech said:
No matter how many times this question is asked, unfortunately, the answer is still, there is no fix.
This has been happening since the nexus 6 went to 5.1 and has been documented numerous times. A bit of reading beforehand is all that is needed to avoid this situation.
RMA is the only option.
Click to expand...
Click to collapse
I did unlock before and rooted the phone and i was using it.
Does it mean my warranty is also void and no more support?
Is any devs working on fixing this problem?

openbook said:
I did unlock before and rooted the phone and i was using it.
Does it mean my warranty is also void and no more support?
Is any devs working on fixing this problem?
Click to expand...
Click to collapse
It's a security feature since 5.1. You cannot.unlock the bootloader without first setting "enable oem unlock". If you unlocked before 5.1, then you most likely didn't do this as it wasn't needed. So now you're locked and there is no way to unlock it.
Some devs may be looking into it, but if they are, they have been looking into it for a long time. It's extremely unlikely there will be a solution for this that doesn't come from Motorola. It could be an easy fix if Moto Wanted. They could provide a stock recovery flash able fully signed, rom.zip. This wouldn't bypass security either because you would still need your unlock code / google password to boot the device. But so far, we've heard nothing
Send it in to them. If you haven't got TWRP installed, there is nothing you can do. There's no reason for them to void warranty