Related
Ok you guys have talked me into atleast trying some roms before I abandon the fuze and go back to my 8525 and/or iphone.
Ive read through
http://forum.xda-developers.com/showthread.php?t=436053
and
http://forum.xda-developers.com/showthread.php?t=410150
Im not a noob when it comes to flashing Ive done it countless times on the 8525.
1st problem is I cant get HardSLP installed on the device. I navigate through all of the menus and when I get to the progress bar it sits for a min and pops an error saying device is not connected. This is after its allready seen the device, verified the batter charge, read which version is on the phone etc.
I'm on a vista machine if that matters although Ive never had an issue with the 8525.
Next, Ive read some people are having issues at going back to orginal everything for return purposes. Can anyone prove or disprove this?
and I think thats it for now.
Thanks in advanced
Uncheck Enable advanced network functionality under the USB to PC network connections section (settings, connections).
Thats what did it for me.. had the same problem.
I have it unchecked other wise it would not sync.
Flash via MicroSD. Safest and best way to flash.
AllTheWay said:
Flash via MicroSD. Safest and best way to flash.
Click to expand...
Click to collapse
Don't I need to get HardSLP installed first?
hondaguyjoe said:
Don't I need to get HardSLP installed first?
Click to expand...
Click to collapse
Try unplugging the USB cable and plug it into another port. If it's plugged into a front USB use a back one if you can.
Also try putting your phone into the bootloader (holding down volume down + reset hole)
See if you can flash it that way.
If that doesn't work. Delete the device driver from you PC and start over.
My Xoom refuses to turn off completely. Every time I do anything related to shutting it down, it simply restarts. CWM restarts it, holding the button restarts it, QuickBoot restarts it. It hasn't always been like this, but soon after I started to root it and such, it stopped shutting down.
It might also be of help to note that I cannot install any OTA update or relock my bootloader. OTA updates simply fail at a screen with an android logo with an exclamation point, and if I relock the bootloader, the Xoom simply won't boot until I unlock it again. I have no idea if any of these problems are related to one another.
I'm currently using the Tiamat Xoom ROM 2.0.1, but it's done this for almost as long as I can remember (probably ever since I rooted the first time). It might also be worth noting that I flashed the wrong images the very first time I rooted it, but I've since flashed all of the appropriate images, so it should theoretically not be an issue.
Athenon87 said:
My Xoom refuses to turn off completely. Every time I do anything related to shutting it down, it simply restarts. CWM restarts it, holding the button restarts it, QuickBoot restarts it. It hasn't always been like this, but soon after I started to root it and such, it stopped shutting down.
It might also be of help to note that I cannot install any OTA update or relock my bootloader. OTA updates simply fail at a screen with an android logo with an exclamation point, and if I relock the bootloader, the Xoom simply won't boot until I unlock it again. I have no idea if any of these problems are related to one another.
I'm currently using the Tiamat Xoom ROM 2.0.1, but it's done this for almost as long as I can remember (probably ever since I rooted the first time). It might also be worth noting that I flashed the wrong images the very first time I rooted it, but I've since flashed all of the appropriate images, so it should theoretically not be an issue.
Click to expand...
Click to collapse
Question, Have you cleared your Dalvik Cache and/or trying another ROM to see if maybe it was not the Tiamat Xoom ROM that could have been corrupted in the flashing process? I am also curious if you have attempted to stock flash and then retry the ROM? You also should know that doing OTA Updates to the android devices that do not have stock ROMs (aka the ROM that you bought with the phone/tablet, no super user and so on) should not be updated with the OTA updates because it can corrupt the ROM that you have. I would suggest, that because Tiamat Xoom Rom 2.0.1 is now labled as [ROM][OMG] Team Tiamat Xoom Rom 2.0.1 Manta Ray [OBSOLETE] (as gotten from the link -- http://forum.xda-developers.com/showthread.php?t=1146153 ) you might want to try a newer version or different rom, OR try to redownload the rom and start over. I would also suggest that if you are going to do that, please clear cache
If I was unable to help you, please let me know and I will try and help you till the issue is solved or someone else has a better answer to help
I've restored to stock and then to the Tiamat rom 2 or 3 different times now, none of which resulted in the Xoom being able to shut off. If memory serves, the Xoom won't even shut off when I'm on completely stock images.
Have you cleared the Devlik Cache and other Cache before each install and as well as after install of the roms? because flashing rom after rom without actually clearing the files could result in residue of older files and corrupting a ROM. I would also look into a different kernal or maybe that your battery/charging cable is bad.
I know with my Ally dev phone it likes to just turn on (with or without a charge/hard boot off) when the phone is plugged into the wall socket (as it is not the normal wall adapter cause I bought the phone off ebay) so the adapter likes to force it online... can you turn off the Xoom when it is or is not plugged in?
Cranvis said:
Have you cleared the Devlik Cache and other Cache before each install and as well as after install of the roms? because flashing rom after rom without actually clearing the files could result in residue of older files and corrupting a ROM. I would also look into a different kernal or maybe that your battery/charging cable is bad.
I know with my Ally dev phone it likes to just turn on (with or without a charge/hard boot off) when the phone is plugged into the wall socket (as it is not the normal wall adapter cause I bought the phone off ebay) so the adapter likes to force it online... can you turn off the Xoom when it is or is not plugged in?
Click to expand...
Click to collapse
The rom install automatically wipes the two caches, so I haven't worried about it. There is no case in which my Xoom has been able to turn off for months, plugged in, not plugged in, or ANY other case. I asked solarnz on IRC about the problem, but he had no idea :/
Athenon87 said:
The rom install automatically wipes the two caches, so I haven't worried about it. There is no case in which my Xoom has been able to turn off for months, plugged in, not plugged in, or ANY other case. I asked solarnz on IRC about the problem, but he had no idea :/
Click to expand...
Click to collapse
You could, in all and all, have a bad device that has a power surge/fault/something where two wires are jumping/something else and just need to contact Motorola and ask them for help (after of course you make sure you reflashed back to 100% stock). These tablets, heck any computer like device, are so fickle to power that they will do anything if there is a right charge... good example is my Dev Phone I mentioned earlier... Plug it in off, and it boots up... you just might have had a bad tablet to start with and it took it a tiny bit to show it's ugly bug filled head... I am sorry that I can't help you any more on this, but I really do think you need to contact Motorola before your warranty is up... it takes only one wire to be solder incorrectly to mess up a whole system... trust me, I have had computers burn up on me and friends because of exposed wires, incorrectly soldered wires, and let alone, DUST of all things...
I hope you can get Motorola to help you out, because I am suspecting that it is a hardware issue... not a software...
Hi.
I don't know much about details about root/room/recovery, but know some about
ODIN, CWM and other ROM to use.
I've been using Humble 5.0 for a while and my phone got unstable recently, so I ODIN the same Humble rom again, but that is how the problem started.
The main problem is, I can't wipe userdata or cache at all.
CWM says it wiped, but I always get Force close, so many that I can't even use the phone normally.
I tried to go back to stock ROM or any other, but all failed.
Stock ROM with stock recovery says, E:Can't mount /dev/block/mmcblk0p1 (Invalid argument). and most of the time, Bootloops.
Humble is the only option I can go into, and actually use the phone, but it has all the apps and data from the past, even though I wipe data/cache thousand times.
I even erased all SD data, formatted in FAT32, and nothing works.
Finalizing my status,
Can't mount...error with Stock ROM.
Bootloop with other ROM.
Constant Force Close with Humble 5.0 (Can't wipe data/cache).
Please help.
So stock, you used ODIN EE4 and PIT file to go back to stock and took the newest update and still have problems?
Thank you for the reply.
Yes. I tried ED1 and EE4, and even with PIT(repartition) and I get "Can't mount..." error.
I went back to Humble 5.0 which has all kind of force close (still showing all app names I had, mysterious), and formatted SD, factory reset, and tried ODIN ED1/PIT, but result is same.
I have a feeling my internal SD partition got screwed.
I am no pro myself.. But I am running GummyCharge Froyo 2.0 which comes with Imoseyon's Kernel and its rock stable even overclocked to 1,200 mhz for me.. You may want to try getting a copy of that as well as flashing with your SIM Card out and Battery in after booting into recovery.. Let me know if this helps at all!
jiehooni said:
Thank you for the reply.
Yes. I tried ED1 and EE4, and even with PIT(repartition) and I get "Can't mount..." error.
I went back to Humble 5.0 which has all kind of force close (still showing all app names I had, mysterious), and formatted SD, factory reset, and tried ODIN ED1/PIT, but result is same.
I have a feeling my internal SD partition got screwed.
Click to expand...
Click to collapse
I had a similar problem but dont remember what I did to fix lol like that helps you. Did you format your sd card on a computer or with your phone? If not try using an adapter and format on computer. Going back to stock has always solved my problems. There is a new cwm that came out. Just throwing stuff out there. Have you tried re downloading images of the stock ee4 and pit? It is loading so shouldnt be a problem , hmm. Maybe someone with more knowledge will pop in.
I tried GummyCharge 2.0.zip from SD but it didn't help.
I tried CWM 5.0, with many ROMs to wipe cache/data, no use.
I formatted my SD on PC, and from phone, same result.
What I don't understand is, even after I flashed Humble 5.0 ROM which I used right before, and only ROM it works now, it shows all apps I had even after many times of Wipe Data/cache/dalvic.
Even funnier, I delete some apps causing Force Close, and I reboot my phone, it always goes back to where I start. Same Home, the app is still there.
It is just weird.
Im getting FC now all of a sudden. It's you fault damn it lol. Said I was gonna reload anyhow. Just didnt want to do it twice in one night. Oh it is past 12pm so I guess it is another day.
It's been now 3 days, and I found this thread hopelessly.
Same problem I think.
http://forum.xda-developers.com/showthread.php?t=1191650&page=2
I hope somebody can help me fix it.
Now I can't even flash Humble, can't even get through recovery(stock or CWM).
I can't do anything now.
I will Odin back to stock and take it to the verizon tomorrow.
Thank you all of you for the help.
Tried a different usb cable, how did you flash the new cwm? So everytime it says pass through ODIN? Are you checking the right selections through ODIN and using PDA? Man just trying to think of everything and thats about it. Get another phone lol. Superuser and busybox?
I tried different USB cable, PC, installed Samsung driver again.
I took the phone to Verizon today, and they can't hard reset it either at that place.
I dropped the phone 3 month ago and it has a little dent, so that they refuse to repair it under warranty. I am sending it to MobileTechVideo tomorrow.
Thank you.
I'm having the same issues. I was on Humble 5.0 and had been using it without a problem for about 2 weeks and yesterday I noticed my phone reboot on it's own. After the reboot it was stuck in the boot loop. I've also tried reflashing Humble 5.0, tried the instructions on the fix your phone thread, tried flashing to stock and also tried the all in one Gingerbread 2.3.6 W/Root/CWR/IMO Kernel 4.0 to see if CWM would help any.
All successfully pass according to Odin, but they all still boot loop and all give error messages in their recovery modes if I try to do anything involving /cache or /data stating that they fail to mount.
Any thoughts would be greatly appreciated.
Okay, I started this thread with the issue of not being able to root. I bit the bullet and wiped it all and ended up being able to root. Now I have a much bigger issue... My phone wont go into storage mode. Not in the OS, not in CWM, not in download mode. It just can't be recognized by a computer. Yes I have the drivers installed, and the phone knows it's plugged in, it will charge and everything, it just wont give me the option to go into storage mode. This will be an issue if I ever need to flash it for any reason since download mode can't be recognized in ODIN. It was working a day ago... Think it's a hardware issue?
JoeVsFox said:
Okay, I started this thread with the issue of not being able to root. I bit the bullet and wiped it all and ended up being able to root. Now I have a much bigger issue... My phone wont go into storage mode. Not in the OS, not in CWM, not in download mode. It just can't be recognized by a computer. Yes I have the drivers installed, and the phone knows it's plugged in, it will charge and everything, it just wont give me the option to go into storage mode. This will be an issue if I ever need to flash it for any reason since download mode can't be recognized in ODIN. It was working a day ago... Think it's a hardware issue?
Click to expand...
Click to collapse
Storage mode and download mode are different to me atleast.
Have you tried settings/usb settings/ask on connection.
When you connect your usb cable from your computer to your phone it should beep and then ask what you want to do. Is your sd card good? Have you checked it maybe on your computer with an adapter?
Or are you talking about getting into ODIN?
Have you usb cable connected to the main usb port. Pull the battery,put it back in, connect the usb cable , hold the volume down button and power key. Worked every time for me. Not sure what else to say from me atleast. Someone else might chime in. Ive done it both with the battery and with out. Try a different usb port.
ODIN Flash Stock
blueis300 said:
So stock, you used ODIN EE4 and PIT file to go back to stock and took the newest update and still have problems?
Click to expand...
Click to collapse
If you have the charge pit file and EE4 you should be able to wipe everything on your phone. If I am correct, this bypasses all permissions and partitions and basically supercedes any roms or data you have. This should work. try another cable on a different usb port or another computer. I have hard brocked my phone numerous times and this was the only workable method. (if you want you can do a little solder job and have phone by fixed with the unbrickable mod here
I already sent my phone to the repair shop.
Btw, it is the normal case you described, but I tried different PCs, drivers, cables, USB slot, nothing works.
Thank you anyway.
blueis300 said:
Storage mode and download mode are different to me atleast.
Have you tried settings/usb settings/ask on connection.
When you connect your usb cable from your computer to your phone it should beep and then ask what you want to do. Is your sd card good? Have you checked it maybe on your computer with an adapter?
Or are you talking about getting into ODIN?
Have you usb cable connected to the main usb port. Pull the battery,put it back in, connect the usb cable , hold the volume down button and power key. Worked every time for me. Not sure what else to say from me atleast. Someone else might chime in. Ive done it both with the battery and with out. Try a different usb port.
Click to expand...
Click to collapse
Tried it with 2 different computers, different cables, different ports. Ask on connection is on. The SD card works fine when I put in in an adapter. The phone just doesn't data connect via usb. ODIN can't find it. Nothing. Pretty sure this is a hardware issue...
My phone just got back from the repair shop and they say they can't fix it. They think NAND got corrupted. Now I am really stuck...Man...
I have searched these forums over and over for an answer. I have come with nothing, and so I figure I will try and ask myself.
I have a Samsung Infuse 4G. A while ago, I decided to upgrade it via Samsung Kies. It bricked from the upgrade, and so i used GTG Unbrick to fix it. While GTG did not fix it, Kies actually completed the emergency recovery, and it worked again.
Slowly, over time, the phone just kept having problems. It wouldn't let me save new contacts, it kept having errors whenever I connected to 4G, and most recently, I was not able to even access my home page or any of my apps cause it kept crashing. I figure if I run it through Kies, it will fix. Well, I was wrong. Its now bricked again. i have spent the last three hours going through many solutions.
Odin wont get passed the Factoryfs section of the process, heimdall keeps telling me it needs a new driver, but then after I get the driver, it doesnt run, kies just doesn't do anything, and GTG does the same thing as odin being it uses Odin.
I really need help. This phone is pretty much my house phone, and I have important calls that I am supposed to recieve in the next few days. If anyone can solve my problem, I'll thank you forever, thats all I really have to give. i wish I could do more, but either way, please help me. I'm currently trying Odin again, and I have tried the Re-partition option, but I'm still getting nothing.
If it is getting stucked during the process, it might be a faulty usb cable. Try another one, switch ports and even PCs if you can.
Sent from my sweet & buttery Infuse
If you are using Kies, I take it that you are not rooted.
Are you able to put your phone into download mode?
I thought my situation was hopeless too but if you can get into download mode you are good, pull battery and hold both vol up and down together, plug in cable to computer then insert battery, volume up once from there and you should be in download mode.
I think you are trying to use Heimdall from the GUI you don't have to do this if it is installed correctly, I was making the same error for a while, but all you need to do is double click the .jar (back to stock one click) from your file tree and it opens up all for you then select the pit or partition option or whatever the check box is hit flash and your good, it might fail once but it will go on the second or third try works great like magic after you use this correctly you will never Odin again.
Thank very much to all the cool people on here sharing their knowledge you guys rock!!
So sorry for the late response. Ok. so, I can get it into download mode. The USB cable is not the issue, nor the comp, cause it does this on every comp.
It is not rooted, but I have just learned that it is no longer under warranty, so I plan to root the little demon asap.
Can someone link me to the latest version of Heimdall maybe. I feel that would help a lot.
And lastly, even ATT didn't know what to do with it.
I'll be on all night if anyone can help.
Sorry for the double post
I have been trying to operate Heimdall. However, everytime I hit flash, it says it needs a different driver. I install the suggested driver, and even then, it still does the same thing. I remember this happening last time and I gave up on heimdall.
Please if someone could help, I will give you thanks.
So I have no clue what I did, but I somehow finally got heimdall to work. It may have been the cord, or the port, idk, but my phone is back online. Thanks for the help provided. You all get thanks
Hello guys,
It is my first time yesterday to flash and root my Xperia Z5 since the camera app always says that it is currently in use.
I used this guide by sceryavuz . And it turned out great, I have used my phone for a day without any errors or problems encountered. But the thing is, I still cannot use the camera app and it has the same currently used by other application message so I decided to downgrade it to Marshmallow this morning. So I went to the same routine, downloaded an FTF file and loaded it into the flashtool.
After clicking Flash device in the flashtool and waited for the flashmode, I connected and pressed the volume down button of my phone but the flashtool is not reading and recognizing my phone. So I decided to open the TWRP and assumed that factory resetting my phone will do the work and it turns out that it just removed the /system folder and now I have a bigger problem with my phone.
When I'm connecting in flashmode the LED is turning to red, green, then will turn off, and then will do the same cycle if left unattended.
Could you guys please help me out with this. You'll be greatly appreciated guys. Thanks!
My phone is E6653 Xperia Z5
Well, you should reflash the system, by a custom rom of your choice or even the stock rom if you want to.
I'm using a custom rom and I highly recommend you to do so if you already lost your data, give it a try.
You don't need to downgrade to MM, it not an android version issue, I would recommend you carbon rom. Go to it's thread and figure out how to flash it, if you need help ask over there or quote me back in this thread.
Another option could be restoring your phone with xperia companion but you will need to relock the bootloader and get flashmode to work again. You can also try flashtool from your computer. Anyway I recommend you to do so ONLY and ONLY if you want your phone to run stock again as it was when you bought it.
Otherwise yep, figure out what's a customrom and how to flash it, you find tons of custom roms in xda threads. having already TWRP is an advantage, less sketchy stuff to do.
Hope it helped, as I said, quote me back if you need help
Edit: if you need the files we're running the exact same device, if you don't find em (and only if you can't find em) i could send them to you.
ofmoll said:
Well, you should reflash the system, by a custom rom of your choice or even the stock rom if you want to.
I'm using a custom rom and I highly recommend you to do so if you already lost your data, give it a try.
You don't need to downgrade to MM, it not an android version issue, I would recommend you carbon rom. Go to it's thread and figure out how to flash it, if you need help ask over there or quote me back in this thread.
Another option could be restoring your phone with xperia companion but you will need to relock the bootloader and get flashmode to work again. You can also try flashtool from your computer. Anyway I recommend you to do so ONLY and ONLY if you want your phone to run stock again as it was when you bought it.
Otherwise yep, figure out what's a customrom and how to flash it, you find tons of custom roms in xda threads. having already TWRP is an advantage, less sketchy stuff to do.
Hope it helped, as I said, quote me back if you need help
Edit: if you need the files we're running the exact same device, if you don't find em (and only if you can't find em) i could send them to you.
Click to expand...
Click to collapse
Hi ofmoll,
I'm sorry for the very late response, I had an internet connection issue this past week. I have tried your suggestion by using Carbon Rom, it works perfectly fine but I have one problem. It is not charging and the battery keeps saying that it is on 100% even if it is not. I'm trying to reflash other ROMs and I'll get back to you as soon as I finish flashing. Happy new year! Thanks!
Hi,
I tried to flash my phone a carbon rom and a crdroid rom and it was successful, my problem was it wasn't charging, and whenever I try to use flashtool, and I am entering flashmode, the phone turns red then green then after a minute it turns red again and then green after I press volume down and connect the phone to my PC. And the PC seems cannot recognize my device since no sounds are going off my computer when I connect it. I hope you can share your expertise regarding this.
Toshiiiiiiii said:
Hi,
I tried to flash my phone a carbon rom and a crdroid rom and it was successful, my problem was it wasn't charging, and whenever I try to use flashtool, and I am entering flashmode, the phone turns red then green then after a minute it turns red again and then green after I press volume down and connect the phone to my PC. And the PC seems cannot recognize my device since no sounds are going off my computer when I connect it. I hope you can share your expertise regarding this.
Click to expand...
Click to collapse
So you say it's not charging? Or did you manage to solve that? You don't really need flashtool at this point (unless you want to relock the bootloader, but I guess there are backdoors for that as well)
If it's not charging, well, the options are this: either it's a hardware problem, for example charger or charge port, or a software problem, because some files are needed for the phone to detect a charger source plugged in.
1. If the software is crashing you can try going into TWRP and wipe cache and dalvik cache, may help may not, try. If you get it yo work remember to calibrate the battery after it, it might be important because after flahsing roms and having this kind of issues the battery could not be showing the actual percentage of battery. So just calibrate, it's easy, Google it.
2. It could happen that the phone is charging but the battery status icon won't show it, I'm not too sure about this but I heard that could happen, might not be the case.
3. In none of that works, search, make a lot of research of people with your same problem and try amd try and try, If nothing works a clean reflash should solve it, usually does, if not try another rom, another kernel or go back to stock. It's your choice, but anyway I guess a clean reflash should get it working. I had the same issue with LineageOS and wiping Dalvik Cache solved it.
If you wipe dalvik expect a long reboot time, I don't suggest you to turn the phone off while it boots up. Wiping Dalvik means all cache files have to be built again the next time you reboot your phone, so yeah, expect some battery drain and a hot device while it boots up, but don't panic, it's totally normal.
Happy new year, hope you get it working again
Remember to hit thanks, cheers!
ofmoll said:
So you say it's not charging? Or did you manage to solve that? You don't really need flashtool at this point (unless you want to relock the bootloader, but I guess there are backdoors for that as well)
If it's not charging, well, the options are this: either it's a hardware problem, for example charger or charge port, or a software problem, because some files are needed for the phone to detect a charger source plugged in.
1. If the software is crashing you can try going into TWRP and wipe cache and dalvik cache, may help may not, try. If you get it yo work remember to calibrate the battery after it, it might be important because after flahsing roms and having this kind of issues the battery could not be showing the actual percentage of battery. So just calibrate, it's easy, Google it.
2. It could happen that the phone is charging but the battery status icon won't show it, I'm not too sure about this but I heard that could happen, might not be the case.
3. In none of that works, search, make a lot of research of people with your same problem and try amd try and try, If nothing works a clean reflash should solve it, usually does, if not try another rom, another kernel or go back to stock. It's your choice, but anyway I guess a clean reflash should get it working. I had the same issue with LineageOS and wiping Dalvik Cache solved it.
If you wipe dalvik expect a long reboot time, I don't suggest you to turn the phone off while it boots up. Wiping Dalvik means all cache files have to be built again the next time you reboot your phone, so yeah, expect some battery drain and a hot device while it boots up, but don't panic, it's totally normal.
Happy new year, hope you get it working again
Remember to hit thanks, cheers!
Click to expand...
Click to collapse
Hi Sir,
Happy new year! Thanks for your reply and I really appreciated it. When I connect the phone to my charger when it's off, it turns on then shows the screen of charging 0% by carbon rom then immediately dies after 2 bars being filled. I hope that it is not a hardware problem since when I connect my phone to my computer via the usb, it lights on but the computer can't recognize it. I am suspecting that this is a rom problem with my phone since the phone shows that it's charging connected to AC and 100% even if it is not connected to a charger. I am trying to get the flashmode to work again so I can flash a stock rom to it because the stock rom works perfectly fine but the camera. I will try all your suggestions tomorrow and I'll research harder to solve this. Will post an update once done. Cheers!
Toshiiiiiiii said:
Hi Sir,
Happy new year! Thanks for your reply and I really appreciated it. When I connect the phone to my charger when it's off, it turns on then shows the screen of charging 0% by carbon rom then immediately dies after 2 bars being filled. I hope that it is not a hardware problem since when I connect my phone to my computer via the usb, it lights on but the computer can't recognize it. I am suspecting that this is a rom problem with my phone since the phone shows that it's charging connected to AC and 100% even if it is not connected to a charger. I am trying to get the flashmode to work again so I can flash a stock rom to it because the stock rom works perfectly fine but the camera. I will try all your suggestions tomorrow and I'll research harder to solve this. Will post an update once done. Cheers!
Click to expand...
Click to collapse
As said, first of all try what I said. It nothing of that solves it, I suggest you 3 options
1. Either go stock, try using XPeria Companion, but I think since you flashed custom it doesn't work, at least for me. For Companion you'll need to relock bootloader. Or go stock by flashing a stock rom via TWRP. Note that after flashing a custom rom you'll never go back to the "real" stock if you don't have a backup, but you can always flash a stock rom.
2. You can also try to reflash the rom and see if that works.
3. Download a Custom kernel, then go to TWRP, wipe everything, then first of all flash the Kernel (remember to ensure that's a kernel for your device). Then reflash the ROM. This could look stupid because the ROM comes with a built-in kernel itself, but it solved an issue I had with random reboots. I didn't read this anywhere, I tried and for me it solved a problem I had which everybody was telling me that was caused by hardware, then it came out to be a Kernel issue. Try to if you want.
Try what I said before as well. This is all I know
Cheers
Edit: I forgot to tell you that PC Companion won't recognize your phone if it's running a customROM. Use Android File Transfer instead. You also need to check "use usb to transfer files" on the notifications pannel. Enable USB debugging as well, I guess you know how to do it, in case: you need to go to "about phone" in settings, hit 8 times Build Number, then the developer options should appear and check Android Debugging. That's it.