Database Info

[Q] Bricked Nexus S

Hi
I have bricked my nexus s when I loaded a ROM that I downloaded.
I have used several different ROMs and had no problems.
I asume this ROM was dodgey.. Anyway I get no screen at all, the menu control at the botom of the screen lights up but that is it.
I can get to it using fastboot but it won't load any ROMS. There is no action on the Nexus screen itself.
Is there a guide using fastboot to recover this also what file/files will I need to download?
Thanks in advance any help would be much appreciated.....

If you are here looking for help you need to give us more information.
What model Nexus S do you have?
What rom did you flash?
What have you done sense flashing the rom?
My guess is you flashed a rom that isn't for your model phone. So you either have SAMOLED or SLCD. I'm guessing the rom you installed was for the screen type you don't have.
So let us have some more details so we can help.
Sent from my Nexus S 4G using xda premium

Sounds like a call for the mighty Odin...
Sent from my Nexus S 4G using xda premium

And u can't get into recovery using the button method?
Sent from my Nexus S using XDA App

If you can get fastboot to work, you can flash all partitions including system. Don't worry, this is an easy fix.

Hi Again guys
Firstly thanks a lot for the replys I really appreciate it.
Its a 3g the model no: is GT-19023.
Its SAMOLED that much I know.
I cannot get into recovery I can get fastboot to recognise the phone but nothing on the screen.
I have downloaded a stock rom and extracted the boot, recovery & system.img files.
I have followed the instructions below and all seems to work till I get to the system. it fails with the following message. The other steps seem to work OK.
"FAILED (remote write failed)"
I have also tried this with several other ROMs I know work on wifes Nexus s and still no luck. Some allow the system to be flashed but the phone still won't boot.
1. fastboot flash boot boot.img
2. fastboot flash recovery recovery.img
3. fastboot flash system system.img
4. fastboot erase cache
5. fastboot erase userdata
Any help would be great
I also downloaded ODIN but cant get it to work; It does not recognise that it is connected to the USB, but fastboot does!. (Is there a step by step guide to using it?)
Sorry for sounding like noob, but I have read everything and looked up these forums and tried a lot before asking for help.
GL

If your phone is a Gt-i9023 it is SLCD!!!!! Not SAMOLED.
Again what rom did you flash? Post a link to it. I still think you flashed a rom for SAMOLED when you have SLCD.
Sent from my Nexus S 4G using xda premium

Rem3Dy said:
If your phone is a Gt-i9023 it is SLCD!!!!! Not SAMOLED.
Again what rom did you flash? Post a link to it. I still think you flashed a rom for SAMOLED when you have SLCD.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
BTW, so 9020 ROMs are incompatible with 9023? I am aware of differences between those devices, but when I looked in "Development" section, there is no info, about compatibility with 9020a/t/9023

http://forum.xda-developers.com/showthread.php?t=955719
pretty sure that is the link to the ROM.
I tried to restore using another stock ROM (I backed it up from another Nexus that was only rooted and stock)... Yes it was exactly the same phone model etc.
The problem is now the error is saying ===FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)===
I tried that (the unlock command) and the prompt just types three dots (...) and then hangs there. I have tried removing the battery etc and the same issue.
I am happy to erase the phone to nothing and load another image.
It seems that maybe this phone is cooked....
I hope not ==shattered==

k_myk said:
BTW, so 9020 ROMs are incompatible with 9023? I am aware of differences between those devices, but when I looked in "Development" section, there is no info, about compatibility with 9020a/t/9023
Click to expand...
Click to collapse
ROMs are compatible between those variants! But, if you're flashing some stock ROM bundles you can flash wrong one. Because bundles contain rom, kernels and radios for specific device with specific drivers. In that case you can flash wrong driver for your display, or even something worse...

Follow what it says, unlock your bootloader first.
Sent from my GT-P1000 using xda premium

glockman63 said:
http://forum.xda-developers.com/showthread.php?t=955719
pretty sure that is the link to the ROM.
I tried to restore using another stock ROM (I backed it up from another Nexus that was only rooted and stock)... Yes it was exactly the same phone model etc.
The problem is now the error is saying ===FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)===
I tried that (the unlock command) and the prompt just types three dots (...) and then hangs there. I have tried removing the battery etc and the same issue.
I am happy to erase the phone to nothing and load another image.
It seems that maybe this phone is cooked....
I hope not ==shattered==
Click to expand...
Click to collapse
Your link still does not tell us which rom you flashed....
You can't flash a rooted rom through fastboot without unlocking the bootloader first. Sounds like you need to restore a factory rom with Odin.
Sent from my Nexus S 4G using xda premium

Hi all
I got this sorted out and am really happy to have my phone going again.
For those interested or in the same predicament I was in please read on as this is how I managed to make this phone go again.
Please rmemeber this phone was really bricked no screen at all jus the menu light like in the picture in my first post.
As I stated I could get fast boot to see the phone. And also Odin. (Still no screen at all)
I had another phone the same with the original rom on board.
I rooted this phone and installed ClockworkMod recovery ad used this to backup the standard ROM.
I then rebooted this phone an copied these files from the backup into my fastboot directory (boot.img, recovery.img, system.img)
I then connected my dead phone up to my PC and ran the following commands.
1. fastboot flash boot boot.img
2. fastboot flash recovery recovery.img
3. fastboot flash system system.img
4. fastboot erase cache
5. fastboot erase userdata
I then removed the battery and to my astonisment the phone booted normally into the standard ROM.
WOW I was over the moon I have since installed my MIUI Rom and using my phone happily...
Thanks everyone for your input..

Rem3Dy said:
Your link still does not tell us which rom you flashed....
You can't flash a rooted rom through fastboot without unlocking the bootloader first. Sounds like you need to restore a factory rom with Odin.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
I've got a phone in the same state I am trying to revive for a guy. With the bootloader locked download mode gives you a locked bootloader screen. Odin sends the flash images to the phone, the phone verifies them but then refuses to flash them (presumably due to the bootloader being locked). The bootloader won't unlock so there is no way to flash a rom to fix the phone.

glockman63 said:
Hi all
I got this sorted out and am really happy to have my phone going again.
For those interested or in the same predicament I was in please read on as this is how I managed to make this phone go again.
Please rmemeber this phone was really bricked no screen at all jus the menu light like in the picture in my first post.
As I stated I could get fast boot to see the phone. And also Odin. (Still no screen at all)
I had another phone the same with the original rom on board.
I rooted this phone and installed ClockworkMod recovery ad used this to backup the standard ROM.
I then rebooted this phone an copied these files from the backup into my fastboot directory (boot.img, recovery.img, system.img)
I then connected my dead phone up to my PC and ran the following commands.
1. fastboot flash boot boot.img
2. fastboot flash recovery recovery.img
3. fastboot flash system system.img
4. fastboot erase cache
5. fastboot erase userdata
I then removed the battery and to my astonisment the phone booted normally into the standard ROM.
WOW I was over the moon I have since installed my MIUI Rom and using my phone happily...
Thanks everyone for your input..
Click to expand...
Click to collapse
So it wasn't bricked...... glad you got it working.
Sent from my Nexus S 4G using xda premium

Rem3Dy said:
So it wasn't bricked...... glad you got it working.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Your lucky your bootloader was already unlocked. Once a phone gets borked like that unlocking the bootloader is impossible and Odin refuses to flash.

jboxer said:
Your lucky your bootloader was already unlocked. Once a phone gets borked like that unlocking the bootloader is impossible and Odin refuses to flash.
Click to expand...
Click to collapse
Dude.... stop spreading incorrect information. The bootloader state does not affect Odin. Please understand this!
Sent from my Nexus S 4G using xda premium

Rem3Dy said:
Dude.... stop spreading incorrect information. The bootloader state does not affect Odin. Please understand this!
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Yes it does! Or at least on the phone I am trying to repair it has. On the phone I am trying to repair when you go into download mode you get a screen that says to unlock the bootloader. Odin connects and sends the file but then the phone refuses to flash it. If that is not the bootloader being locked affecting Odin then I don't know what is. I have flashed with Odin hundreds of times with Galaxy S phones so I know what I am doing. I have never seen Odin send a file, have the phone say it is verified and then refuse to flash it, but that is what is happening with this Nexus S with an unlockable bootloader. The files are the correct files and Odin is the correct version. If you are so smart, then you tell me what to do to get Odin to accept the flash and you will be my hero.
I have attached a shot of the phone in "download mode." Notice it is a warning about the bootloader being locked, not the normal screen with the Android bot and a shovel. Odin sees the phone (connected to computer as Samsung device) but once the phone verifies the file nothing else happens. The file is never flashed. Notice in the photo there is no YES and NO selections to unlock the bootloader like you get when you issue the "fastboot oem unlock" command. In Fastboot when that command is issued you get the normal unlock the bootloader screen but when you select YES and press Power nothing else happens. It just hangs no matter how long you leave it. A battery pull is the only thing you can do and when you turn the phone back on the bootloader is still locked.

If you are getting g stuck there you may have a hardware issue. I still think you need to try flashing through fastboot.
Sent from my Nexus S 4G using xda premium

Rem3Dy said:
If you are getting g stuck there you may have a hardware issue. I still think you need to try flashing through fastboot.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Cannot flash in fastboot. Sends over image then says fail due to bootloader being locked. If you have a signed update.zip with android-info and android-product files that can be flaahed in fastboot mode let me know where it can be downloaded from.
Sent from my LG-P999 using Tapatalk

HELP!!

Hi everybody
I've been so stupid
I tried to flash Jelly Bean to my nexus s,
I forgot to root, restarted, it didn't start, I went into stock recovery, deleted system by accident, now it won't boot anymore.
Can I do something about it or is it really dead?
Dennis

If the phone turns on and fastboot works then no it is not dead.Follow the instructions below to install CWM on your phone and then you can flash stock/custom rom using CWM.
If you have lost recovery then install pdanet on your computer.(It will also install Nexus S USB Drivers) then put your phone into fastboot mode by holding down both Volume Up and Power buttons together. When you are in fastboot mode connect your phone to your PC using USB cable.Download ADB and recovery you want to flash put it in your C:/recovery (Put adb and recovery image in this folder)
Then open cmd and type
1)CD C:/recovery
2)fastboot flash recovery recoveryname.img (replace recoveryname with actual file name of the recovery image).
You can download recovery from here
Or you can avoid all this and just use this
http://forum.xda-developers.com/showthread.php?t=1544940&highlight=recovery

Android-Junky said:
If the phone turns on and fastboot works then no it is not dead.Follow the instructions below to install CWM on your phone and then you can flash stock/custom rom using CWM.
If you have lost recovery then install pdanet on your computer.(It will also install Nexus S USB Drivers) then put your phone into fastboot mode by holding down both Volume Up and Power buttons together. When you are in fastboot mode connect your phone to your PC using USB cable.Download ADB and recovery you want to flash put it in your C:/recovery (Put adb and recovery image in this folder)
Then open cmd and type
1)CD C:/recovery
2)fastboot flash recovery recoveryname.img (replace recoveryname with actual file name of the recovery image).
You can download recovery from here
Or you can avoid all this and just use this
http://forum.xda-developers.com/showthread.php?t=1544940&highlight=recovery
Click to expand...
Click to collapse
Thank you for you reply. I have adb installed and it worked, but now my laptop won't recognize my device anymore:S

Denn77 said:
Hi everybody
I've been so stupid
I tried to flash Jelly Bean to my nexus s,
I forgot to root, restarted, it didn't start, I went into stock recovery, deleted system by accident, now it won't boot anymore.
Can I do something about it or is it really dead?
Dennis
Click to expand...
Click to collapse
Lol, forgot to root? That made me literally laugh out loud. Are you the same guy that posted this on Engadget.com? Some guy just explained on there of how he did the exact same thing...
Make sure you are running as admin on your computer. Right click on whatever program you are using and click "run as admin". That can solve most of the problems with your computer not recognizing the device. Good thing you messed up on the nexus. It's a pretty good phone for fixing newb mistakes.
Sent from my Galaxy Nexus using xda app-developers app

nikeman513 said:
Lol, forgot to root? That made me literally laugh out loud. Are you the same guy that posted this on Engadget.com? Some guy just explained on there of how he did the exact same thing...
Make sure you are running as admin on your computer. Right click on whatever program you are using and click "run as admin". That can solve most of the problems with your computer not recognizing the device. Good thing you messed up on the nexus. It's a pretty good phone for fixing newb mistakes.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Well, i forgot to flash the root as I first wanted to see if Jelly Bean worked at all.. And it wasn't me on Engadget.com
I really really really hope I can fix it, as I don't want to lose my nexus s, it's a great phone!
If i can fix it, I'll be more carefull in the future
thanks for your replies!

PdaNet hangs on 'installing PdaNet to your phone'

Solved
He's alive again (My phone wasn't dead, I know)
Thank you so much!

Good! We learn from mistakes! Rooting is fun and has many benefits! Hard parts done, flash away!
Sent from my Galaxy Nexus using xda app-developers app

Stuck on boot screen. Plz help.

Ok guys like I posted earlier I damaged my power key somehow and for the time being I downloaded a widget by means of which I could boot into the recovery. However now I'm stuck on the boot screen and my phone is currently going through a boot loop and I don't know how to boot into recovery now. ...plz help guys how do I boot into recovery now with my power key not working. Any help in the said matters shall be appreciated. Thanks in advance.

[email protected] said:
Ok guys like I posted earlier I damaged my power key somehow and for the time being I downloaded a widget by means of which I could boot into the recovery. However now I'm stuck on the boot screen and my phone is currently going through a boot loop and I don't know how to boot into recovery now. ...plz help guys how do I boot into recovery now with my power key not working. Any help in the said matters shall be appreciated. Thanks in advance.
Click to expand...
Click to collapse
Try remove battery from phone. After back battery in phone. Press the button Home and Power together.
Wait a little and you will have CWM.

do you have adb installed on your pc ?
if yes , just connect your mobile to your pc using usb cable ,using terminal / cmd prompt navigate to adb folder and type
adb reboot recovery
if you don't have adb then google how to setup adb on windows/ubuntu whichever os you have
Sent from my GT-S5670 using xda premium

ZmisiS said:
Try remove battery from phone. After back battery in phone. Press the button Home and Power together.
Wait a little and you will have CWM.
Click to expand...
Click to collapse
I've tried doing that many times and btw my power button is not working. So cant boot into recover with that method. Thanks anyways.
soham jambhekar said:
do you have adb installed on your pc ?
if yes , just connect your mobile to your pc using usb cable ,using terminal / cmd prompt navigate to adb folder and type
adb reboot recovery
if you don't have adb then google how to setup adb on windows/ubuntu whichever os you have
Sent from my GT-S5670 using xda premium
Click to expand...
Click to collapse
Yes I do have adb installed. Even I was thinking about doing the same but will adb recognize the device when its stuck on bootloader?

just give it a try dude
I think it will recognize your device
Sent from my GT-S5670 using xda premium

If it is not a hardware problem, Power should work with this method.
I have several times had a problem like yours and I solved it this way.

soham jambhekar said:
just give it a try dude
I think it will recognize your device
Sent from my GT-S5670 using xda premium
Click to expand...
Click to collapse
That worked. I have my phone back in working condition. Thanks a lot buddy.
ZmisiS said:
If it is not a hardware problem, Power should work with this method.
I have several times had a problem like yours and I solved it this way.
Click to expand...
Click to collapse
No luck doing that although!!

[Q] Stuck in "FASTBOOT MODE - NO BOOT OR RECOVERY IMG"

My NExus S is stuck on the screen that says:
Fastboot Mode No Boot or Recovery IMg.
Product Name - Herring
HW Version - Rev34
Bootloader Version - D720SPRKC5
Baseband Version - D720SPRLCI
Carrier Inro - SPR
Serial Number 32300E25C33500EC
Lock State - Locked
options to select
Reboot Bootloader (gives me exact same screen) except it only says "Fastboot"
Reboot Back to the "FASTBOOT MODE - NO BOOT OR RECOVERY IMG"
Recovery (Can boot to CWM but I can't mount anything)
Power OFF (That works fine)
Then the little green man and the android logo
Followed by USB Control INIT
USB Control INIT End
STANDARD_SET_CONFIGURATION
Conventional wisdom says download some files and fix via fastboot. However in fastbootI can't run ANY of the steps without running FASTBOOT OEM UNLOCK. When I run it my phone asks if I really want to unlock the bootloader. when I choose YEs and hit power it just freezes there.
My next thought Boot to recovery and restore. A restore through recovery followed by a reboot leads me back to the original no boot or recovery img.
Okay I'll just sideload a working rom by mounting usb storage. Then I can flash it with CWM and be up and running.
but when I try to do mount the USB Storage I get "E:Unable to write to ums 1unfile (No such file or directory)"
Finally, Last ditch Effort, I'll load up ODIN and use that to put on a working recovery. there's forums all over the place explaining how to do that right? Well yes, but the links to the Tar file are all broken.
What next my friends? I'd really like to get this phone working.

Wug's Nexus Root Toolkit.

ej8989 said:
Wug's Nexus Root Toolkit.
Click to expand...
Click to collapse
I tried doing the Flash stock + unroot in wug's kit but no luc. any other ideas?

swing4thefence said:
I tried doing the Flash stock + unroot in wug's kit but no luc. any other ideas?
Click to expand...
Click to collapse
Your bootloader is LOCKED. You must first UNLOCK the bootloader by clicking "Unlock" on Nexus Root Toolkit.

ej8989 said:
Your bootloader is LOCKED. You must first UNLOCK the bootloader by clicking "Unlock" on Nexus Root Toolkit.
Click to expand...
Click to collapse
No matter how I try to do it, it always freezes at the unlock bootloader step.

Did you install proper drivers?

ej8989 said:
Did you install proper drivers?
Click to expand...
Click to collapse
I thought so. My wife is on the computer so if she ever gives it back I'll re-install the drivers and try again.

swing4thefence said:
I thought so. My wife is on the computer so if she ever gives it back I'll re-install the drivers and try again.
Click to expand...
Click to collapse
Reinstalled Drivers. Still no luck.

I have the same problem.

Same situation for me, because i pressed "Reboot" in CWM without having flashed a Rom (stupid ). Broken power button, hanging on Google logo or in Fastboot mode.
I hope RTK will help me :good: :laugh:
Edit: I have no idea how to revive my Nexus S. Status: Broken Power button, Bootloop, can access Fastbood Mode but dont select someting, Bootloader unlocked, RTK doesn´t find any devices in Fastboot Mode, Device is rooted and has CWM

!Lür said:
Same situation for me, because i pressed "Reboot" in CWM without having flashed a Rom (stupid ). Broken power button, hanging on Google logo or in Fastboot mode.
I hope RTK will help me :good: :laugh:
Edit: I have no idea how to revive my Nexus S. Status: Broken Power button, Bootloop, can access Fastbood Mode but dont select someting, Bootloader unlocked, RTK doesn´t find any devices in Fastboot Mode, Device is rooted and has CWM
Click to expand...
Click to collapse
what about just using adb? Can you find it when you type fastboot devices? If so there's a command in fastboot to reboot to recovery I think.
I on the other hand am screwed. I read in another forum that it hangs on unlock because the internal memory is fubar.

swing4thefence said:
what about just using adb? Can you find it when you type fastboot devices? If so there's a command in fastboot to reboot to recovery I think.
I on the other hand am screwed. I read in another forum that it hangs on unlock because the internal memory is fubar.
Click to expand...
Click to collapse
Solution for me:
1. Turn device on into Bootloop
2. Connect it via USB (PC founds it)
3. type in CMD "adb reboot recovery"
4. device is in recovery
5. reflash everything i wanted :good:
Requirement is a working Android-SDK!

I wish it was that easy for me. I can access recovery just fine. It's the memory I can't touch. Unless someone knows a way to fix corrupted memory...
Sent from my SCH-I510 using xda app-developers app

Im having this same issue too i can still get to CWM recovery but nothing really helps from there. I can still mount my storage and put zip files on there etc but nothing seems to fix the problem...any progress?

swing4thefence said:
I wish it was that easy for me. I can access recovery just fine. It's the memory I can't touch. Unless someone knows a way to fix corrupted memory...
Sent from my SCH-I510 using xda app-developers app
Click to expand...
Click to collapse
I think I'm going to try using my computer to mount and format the internal memory. any ideas as to the correct settings to use when I try this? at this point what have I got to lose?

swing4thefence said:
I think I'm going to try using my computer to mount and format the internal memory. any ideas as to the correct settings to use when I try this? at this point what have I got to lose?
Click to expand...
Click to collapse
Was this solved by any means ??, i am myself stuck at that position

Flash the stock image again using the Nexus Toolkit
Sent from my Nexus S using xda app-developers app

Akbar89 said:
Flash the stock image again using the Nexus Toolkit
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
Wug's Nexus toolkit ?? It is stuck on bootloader unlock menu, as unlocking bootloader makes it freeze. Without unlock it doesn't flashI anything.
If there is another tool please guide me with link.
Avoid Spells!!! "Auto correct : ON"

stuck on fastboot mode(lenovo S860)
recently i've bought lenovo s860 (2GB version).....its latest updates had bugs....so i was trying to downgrade to lower version(jelly bean).....in the way i got stuck in fastboot mode......is there any way to get out of it??

same problem in galaxy nexus i9250m
ej8989 said:
Did you install proper drivers?
Click to expand...
Click to collapse
i have same problem in galaxy nexus i9250m
my bootloader showingh no boot or recovery img
i have working fastboot, workin adb and driver
my oem is unlocked with fastboot
bt i am unable to flash recovery and rom

Did my phone bricked itself? Please help!

Hey guys, I received my OnePlus One today yayy!
BUT. I booted the phone, configured everything like I wanted, installed all the apps I wanted and then I got an OTA update so I figured I would do that too!
The phone rebooted and... stuck on the 1+ logo / powered by android.
I asked around and people on the OnePlus forums told me to boot into recovery and perform a factory reset / clear cache.
I did this and my phone booted again. I reconfigured everything, reinstalled everything and I decided to reboot the phone.
It got stuck again on the logo.
Now though... I can't boot into recovery mode. I asked for help again but no answers... through some research, I installed Android SDK and tried to open a command prompt and type "adb devices". Nothing appears in the list.
Can someone help me? I just want to cry...

Before you can use ADB, you need the ADB drivers. Download the OnePlus One Toolkit and use the feature that downloads and installs the correct drivers. Or you can manually look for them.
Sent from my One using Tapatalk

TheShoxter said:
Before you can use ADB, you need the ADB drivers. Download the OnePlus One Toolkit and use the feature that downloads and installs the correct drivers. Or you can manually look for them.
Sent from my One using Tapatalk
Click to expand...
Click to collapse
Drivers are already installed, the phone is stuck in the boot sequence.
It's detected by both "adb devices" and "fastboot devices". It responds to commands like "fastboot reboot" but since it cannot reboot, this achieves nothing. I can't "fastboot oem unlock" because the phone doesn't load the OS.

djodars said:
Drivers are already installed, the phone is stuck in the boot sequence.
It's detected by both "adb devices" and "fastboot devices". It responds to commands like "fastboot reboot" but since it cannot reboot, this achieves nothing. I can't "fastboot oem unlock" because the phone doesn't load the OS.
Click to expand...
Click to collapse
Ok, and you said that you're on 100% stock? No custom ROM or kernel?
Sent from my One using Tapatalk

If you can get fastboot just load everything back to stock and start over.
Sent from my One using XDA Premium 4 mobile app

You can manually enter into fastboot mode without command.Just press power button+volume up button.Once you enter into fastboot ,unlock bootloader,flash twrp & then flash stock rom
Sent from my One using XDA Premium 4 mobile app

RISHI RAJ said:
You can manually enter into fastboot mode without command.Just press power button+volume up button.Once you enter into fastboot ,unlock bootloader,flash twrp & then flash stock rom
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hey, thanks for your reply!
I'm also getting help from the OnePlus forums but here are the latest updates:
I managed to get into fastboot and flash everything (boot, cache, system, recovery etc.). However, everytime I reboot, it still hangs on the boot screen. I have to leave the phone off for about 5 minutes, get into recovery mode, clear the cache and boot into the OS... every... single... time I reboot.
Is there a reason for this? Should I install another ROM (like Paranoid Android or Color OS) instead? Is there a fix to this or is it even software-based?

Unlock bootloader ,flash twrp,flash flashable rom zip.In twrp wipe everything,then go to mount & then uncheck system.Then flash the rom.zip
Sent from my One using XDA Premium 4 mobile app