Database Users

[BRICK] Phone stuck in bootloop after ODIN

Hi!
So, i was playing last nice and my phone suddently rebooted, then, got stuck in bootloop.
I re-flashed stock firmware, cleaned data and cache, didn't fixed, so i repartitioned, still no changes.
What else can i do to try and restore the system?
I still can go the Recovery mode and download mode, however, recovery cant write logs to the /data folder.

Matsilagi said:
Hi!
So, i was playing last nice and my phone suddently rebooted, then, got stuck in bootloop.
I re-flashed stock firmware, cleaned data and cache, didn't fixed, so i repartitioned, still no changes.
What else can i do to try and restore the system?
I still can go the Recovery mode and download mode, however, recovery cant write logs to the /data folder.
Click to expand...
Click to collapse
you can either do a full data wipe - wipe data wipe system wipe cache
mount everything
install hells fusion kernel #50
reinstall rom
or
install stock rom via odin (find full list of stock roms on dorkys thread in development section - its a sticky at the top)

Matsilagi said:
Hi!
So, i was playing last nice and my phone suddently rebooted, then, got stuck in bootloop.
I re-flashed stock firmware, cleaned data and cache, didn't fixed, so i repartitioned, still no changes.
What else can i do to try and restore the system?
I still can go the Recovery mode and download mode, however, recovery cant write logs to the /data folder.
Click to expand...
Click to collapse
Do this
Partition Error
http://forum.xda-developers.com/showthread.php?t=2122370
PHONE SLOW CLICK ME?
1 days 2 s4​

As i said on the bricked device thread, i already did that, and it didnt worked.
I get to the Samsung logo, after a time, it stops when the logo is very bright, then start the boot animation again.
It looks like it is not Reading the system.
Also, going to try the method mentioned up here.
I will feedback in a few moments.
Also, is there a problem if i use the bootloader that you gave me on that thread on the Brazilian default firmware?
EDIT:ITS ALIVE!!!
This thread can be closed! Thanks a lot man!!

Matsilagi said:
As i said on the bricked device thread, i already did that, and it didnt worked.
I get to the Samsung logo, after a time, it stops when the logo is very bright, then start the boot animation again.
It looks like it is not Reading the system.
Also, going to try the method mentioned up here.
I will feedback in a few moments.
Also, is there a problem if i use the bootloader that you gave me on that thread on the Brazilian default firmware?
EDIT:ITS ALIVE!!!
This thread can be closed! Thanks a lot man!!
Click to expand...
Click to collapse
Your welcome I live to serve
PHONE SLOW CLICK ME?
1 days 2 s4​

After Flashing official stock rom (Country specific) using odin,
Just flash 3 files i.e. PDA, PHONE(MODEM) &, CSC and move on the go. It really works for me and hope this works for you. Give it a try bro.

Phone keeps bootlooping, possible EFS corruption?

I tried flashing X-Note 6.0 and things have gone sour from there. I keep getting bootloop, i'm able to do initial setup until it asks me for gmail, once i input my address, it pulls my name and when it asks me to confirm it, it restarts the phone. Then im able to finish setup, but as soon as i'm back and i reboot again, im stuck in infinite bootloop.
I tried reverting back to stock via odin, but i got bootloop again, fortunately for me, after about 1h, it booted back into OS and i was able to root and reinstall twrp.
I dont have a backup of my EFS, again i'm not even sure thats the real problem, can anybody please help?
EDIT: On stock the bootloop is not infinite, after about 10 minutes the phone eventually boot back in OS

polish_pat said:
I tried flashing X-Note 6.0 and things have gone sour from there. I keep getting bootloop, i'm able to do initial setup until it asks me for gmail, once i input my address, it pulls my name and when it asks me to confirm it, it restarts the phone. Then im able to finish setup, but as soon as i'm back and i reboot again, im stuck in infinite bootloop.
I tried reverting back to stock via odin, but i got bootloop again, fortunately for me, after about 1h, it booted back into OS and i was able to root and reinstall twrp.
I dont have a backup of my EFS, again i'm not even sure thats the real problem, can anybody please help?
EDIT: On stock the bootloop is not infinite, after about 10 minutes the phone eventually boot back in OS
Click to expand...
Click to collapse
Please help me someone. I tried the EFS fix here with no success. I tried to restore via odin, factory reset, every time i finish initial setup and restore my apps and reboot, it bootloops.

Shot in the dark, but disable auto installing of apps/restoring apps. Could be that it is triggering the bootloop due to an incompatible app with X-Note.
If no good. You gotta be brave and strip that badboy back with a full wipe/dalvik/cache, reflash your stock image (get shot of recovery also) then see if it can get past the bootloop (don't forget to remove your SD Card also if you have one) - Give it shot, see what you come up with.
Also if you're on an N9005 model, head over to Djembays thread and grab an image of him, seems to have gotten a lot of people out of issues (JayTheNut uses his images when he messes up) -
Lemme know how you get on, I'll have a nose around see what else it could be.

radicalisto said:
Shot in the dark, but disable auto installing of apps/restoring apps. Could be that it is triggering the bootloop due to an incompatible app with X-Note.
If no good. You gotta be brave and strip that badboy back with a full wipe/dalvik/cache, reflash your stock image (get shot of recovery also) then see if it can get past the bootloop (don't forget to remove your SD Card also if you have one) - Give it shot, see what you come up with.
Also if you're on an N9005 model, head over to Djembays thread and grab an image of him, seems to have gotten a lot of people out of issues (JayTheNut uses his images when he messes up) -
Lemme know how you get on, I'll have a nose around see what else it could be.
Click to expand...
Click to collapse
I dont think you read the thread. I'm not on xnote anymore, i'm on stock firmware, MJ4, i also have a W8 and the EFS script fix is for international version. I've odined back to stock and all the issues i'm having are also present on stock firmware

polish_pat said:
I'm not on xnote, i'm on stock firmware, MJ4, i also have a W8 and the EFS script fix is for international version
Click to expand...
Click to collapse
Ah ok, so that changes the playing field a little. - Give @CalcProgrammer1 a Message, he uses the W8 and the guy certainly knows a thing or two about it. All I can think of at this time.
EDIT: actually thinking about it, you haven't upgraded your bootloader by mistake have you?

I have a feeling background WiFi scanning is enabled in Settings -> WiFi -> Advanced - I don't think any of the newer ROM updates ever managed to have that not bootloop your phone on reboot. In case you're stumped and can't find the setting, you'll have to hit the menu key on the WiFI screen.

radicalisto said:
Ah ok, so that changes the playing field a little. - Give @CalcProgrammer1 a Message, he uses the W8 and the guy certainly knows a thing or two about it. All I can think of at this time.
EDIT: actually thinking about it, you haven't upgraded your bootloader by mistake have you?
Click to expand...
Click to collapse
I dont think so, unless flashing Xnote 6.0 or using odin to restore stock does that. Thats pretty much all I did, but i think i might have done something that might have fixed the problem, i'm not sure yet, but i'll confirm shortly

radicalisto said:
Ah ok, so that changes the playing field a little. - Give @CalcProgrammer1 a Message, he uses the W8 and the guy certainly knows a thing or two about it. All I can think of at this time.
EDIT: actually thinking about it, you haven't upgraded your bootloader by mistake have you?
Click to expand...
Click to collapse
I use the N900T (T-Mo) version, though I guess it's pretty similar to the W8. Unfortunately I don't know anything about the efs side of things on the N900T or equivalents. I've been avoiding the backup and restore functionality in TWRP since it was widely reported to cause bootloops in the first few weeks after release anyways. Have you tried the bootloop fix method over at the T-Mobile N900T forum? I forget what the process exactly was but people reported great success using it (including those who intentionally recreated the problem to test the fix). I did have a similar boot loop issue on my Note 1 which was fixed doing a complete Odin restore with a full factory image (bootloader, system, modem, kernel, recovery, etc. - the entire complete factory restore). I don't know if such a package exists for the N900W8 and that's something I wouldn't use the wrong variant's version of.

odin was one of the first thing i tried, as mentionned the problem was on 100% stock device. Now i've tried formating SD cards and i was able stop the bootloops but now instead i get a worse problem when my phone keep giving me force closes and everytime i dismiss one, another one pops back up and its just a FC Loop:crying:

I have an W8...I also had terrible boot loop problems and I can't quite remember the cause, but this is what fixed it.
Obviously I can't stress enough to read this and type this in very carefully, and that if your phone stops working, turns into a robot, explodes, or tries to kill your dog I'm not responsible .
1. Reboot to recovery
2. Hit "Advanced" Select "Terminal Command"
3. Hit "Select" (lower right corner)..Do not select any specific folder, just hit select..
4. keyboard will open, type in the following commands, make sure you put the spaces and / where they need to be, it needs to look exactly as outlined..
mke2fs /dev/block/mmcblk0p12
Hit Go - The command will run.
Clear the box, type the following command
mkdir /efs
Hit Go - The command will run.
Clear the box, type the following command
mount -t ext4 /dev/block/mmcblk0p12 /efs
Hit Go - The command will run.
Do a factory reset, reboot system
Can't remember where I got this from, only saved the text not the forum >.<

stucked
Hello guys .... I wanna say first ... that I tryed all options and all efs backups etc etc ... everything works just fine back up my efs . and restore but .. when I try to register my phone on network ends like this :
- only emergency calls
- when try to insert a new sim card my n9005 just reboot when search for network also ... is charging but allways remain at 8-10% no more up .
I tryed all kind of stuff ... made back ups .... and tryed install stock firmware etc ... rooting and did anything ... I will apreciate any kind of help ...I just wanna tell you I am close to deat ... becouse is my wife phone and still does not know I messed up with

polish_pat said:
EDIT: I'm offering a 50$ bounty to anybody that gives me a solution that fixes my phone, paid in full by paypal
I tried flashing X-Note 6.0 and things have gone sour from there. I keep getting bootloop, i'm able to do initial setup until it asks me for gmail, once i input my address, it pulls my name and when it asks me to confirm it, it restarts the phone. Then im able to finish setup, but as soon as i'm back and i reboot again, im stuck in infinite bootloop.
I tried reverting back to stock via odin, but i got bootloop again, fortunately for me, after about 1h, it booted back into OS and i was able to root and reinstall twrp.
I dont have a backup of my EFS, again i'm not even sure thats the real problem, can anybody please help?
EDIT: On stock the bootloop is not infinite, after about 10 minutes the phone eventually boot back in OS
Click to expand...
Click to collapse
Hey dude i think xnote 6 is mk2 based, so what basically is going wrong is that you're trying to downgrade your bootloader. please try flashing an mk2 stock rom ( or an mj7) via odin, that should fix it ..
just my 2 cents

Hi guys i tried everything my phone was in a constant state of bootloop and wouldnt connect to any carrier. Then i came across this thread http://forum.xda-developers.com/showthread.php?t=2567133 and now my phone is working, still wont connect to a carrier but the phone is now stable which is a good thing. Hope this helps some of you :fingers-crossed:

Thanks for all the input, as of now, i was able to stop the boot-looping on stock rom, but I do still have major issues like i cannot install twrp, by goomanger it tell me its done but when i reboot into recovery, i end up in stock recovery. And yes, i'm rooted. Also i cannot format my SD card from the OS, it keep telling me the card is being checked all the time. I also have a lot of other small issues that should not be there on a fresh install. i honestly dont know what screwed up so bad but i will try some of the solutions mentioned above and report back.

To me that sounds like your partitions are all screwed up have you tried flashing using a pit file?
Sent from my SM-N9005 using xda app-developers app

Steeno78 said:
To me that sounds like your partitions are all screwed up have you tried flashing using a pit file?
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
Never. I'm def not that newbish. I dont know whats happening but everytime i format the phone it gets a little better.
Sent from my SM-N900W8 using Tapatalk

[Root] Problem :\

Hey this is my first thread here and I'm sorry I didn't make an introduction but, I just rooted my phone yesterday. It was successful and I made a backup using titanium but the thing is I started deleting apps and bloat ware from the uninstall in titanium and well I deleted this program called like touchwiz because it was installed with this software I downloaded from Google play called like Iphone 7 screen lock or something and anyways it came with it and changed some things in my settings and I agreed. Once I deleted that I couldn't press the home button since it was linked to the deleted touchwiz which apparently took control of the home button and well my home screen when completely black and so I restarted my phone. Next thing I know I can't get passed this loading screen. Please help :\ sorry for the bad light as my computers literally in my closet and the light bulb screw is too rusty to take out. Please help! h t t p: / / i . i m g u r . c o m / 8 M q C B n l . j p g / <- Remove the spaces it's been on like that for hours, I've even tried restarting it and it wouldn't change..

Well looks like you killed your launcher (and or part of the actual ROM). But...
What happens if you press menu? Do you have the option managing apps? If you do see if you can open Titanium and restore it. Or if you can open play store and search for a launcher - nova or something.
Have you tried to go into the stock recovery (assuming you haven't already added a custom one) and run factory reset?
Did you enable usb debug mode and unknow sources? If so you may be able to push over the needed apk (and .odex file if you are still on stock) via ADB.

leaderbuilder said:
Well looks like you killed your launcher (and or part of the actual ROM). But...
What happens if you press menu? Do you have the option managing apps? If you do see if you can open Titanium and restore it. Or if you can open play store and search for a launcher - nova or something.
Have you tried to go into the stock recovery (assuming you haven't already added a custom one) and run factory reset?
Did you enable usb debug mode and unknow sources? If so you may be able to push over the needed apk (and .odex file if you are still on stock) via ADB.
Click to expand...
Click to collapse
Yes I'm still in stock I haven't installed anything custom, For factory reset isn't it like volume up, power, and home button?, umm so far when I press the menu nothing happens.. Do you think I can fix my phone over usb? to computer?

Mr Tabi said:
Yes I'm still in stock I haven't installed anything custom, For factory reset isn't it like volume up, power, and home button?, umm so far when I press the menu nothing happens.. Do you think I can fix my phone over usb? to computer?
Click to expand...
Click to collapse
Well you could grab the stock MK2 Odex from here.
Then use ADB (via USB cable to you PC) to push the files over (if the phone shows up).
Problem is do you know the actual name of the file you deleted vs the 'displayed' name.
Or you could PC Odin a recovery (like Philz or TWRP) boot to that custom recovery and flash the above mentioned stock ROM (or actually any ROM in the dev section; so long as you follow the OP's flashing instructions)

leaderbuilder said:
Well you could grab the stock MK2 Odex from here.
Then use ADB (via USB cable to you PC) to push the files over (if the phone shows up).
Problem is do you know the actual name of the file you deleted vs the 'displayed' name.
Or you could PC Odin a recovery (like Philz or TWRP) boot to that custom recovery and flash the above mentioned stock ROM (or actually any ROM in the dev section; so long as you follow the OP's flashing instructions)
Click to expand...
Click to collapse
Currently installing the MK2 Odex but what do I do next just connect it to my computer? What's an ADB sorry I'm not good at any of this...

Mr Tabi said:
Currently installing the MK2 Odex but what do I do next just connect it to my computer? What's an ADB sorry I'm not good at any of this...
Click to expand...
Click to collapse
If you install the odexed ROM then you shouldn't have to push anything. You should be good to go once installed. May have to do a battery pull to get first boot.
ADB = android debug bridge. It's a command line tool used to communicate with your device.
edit: here's a very good walkthrough
Sent from my SPH-L720 using XDA Premium 4 mobile app

[Q] Trying to factory restore the phone and nothing seems to work

So last night I tried installing a custom boot animation for my Samsung Galaxy S4, but I somehow misread the instructions and deleted some files in the /system/media directory. After a restart I noticed that I was led to a boot screen that has the Samsung logo and a padlock with custom written on the screen, after this screen passes there is darkness for a minute or so then the phone is booted into, yeah sounds okay, right? Well, after that happened I realized that my lock button won't actually lock the phone, the phone will actually continuously stay on, no matter what settings I tell the phone to lock, it's as if locking the screen now is not an option, but the lock button works if I hold it down which will give me the option to shutdown go into airplane mode and restart. I then proceeded to see if I could restore the phone to factory settings by going into the settings to factory restore but that doesn't do anything, just restarts the phone. After that I tried hard resetting which didn't work either, I wasn't even led to the GUI for hard resetting. I'm running a stock ROM on 4.4.2 Kit Kat that's rooted, an At&t I337 model. I'd just really like to factory reset the phone and I'm not sure what to do? Thanks.

Jester_Man said:
So last night I tried installing a custom boot animation for my Samsung Galaxy S4, but I somehow misread the instructions and deleted some files in the /system/media directory. After a restart I noticed that I was led to a boot screen that has the Samsung logo and a padlock with custom written on the screen, after this screen passes there is darkness for a minute or so then the phone is booted into, yeah sounds okay, right? Well, after that happened I realized that my lock button won't actually lock the phone, the phone will actually continuously stay on, no matter what settings I tell the phone to lock, it's as if locking the screen now is not an option, but the lock button works if I hold it down which will give me the option to shutdown go into airplane mode and restart. I then proceeded to see if I could restore the phone to factory settings by going into the settings to factory restore but that doesn't do anything, just restarts the phone. After that I tried hard resetting which didn't work either, I wasn't even led to the GUI for hard resetting. I'm running a stock ROM on 4.4.2 Kit Kat that's rooted, an At&t I337 model. I'd just really like to factory reset the phone and I'm not sure what to do? Thanks.
Click to expand...
Click to collapse
If factory reset doesn't work all you need to do it is flash the stock firmware again.. So that would restore all the system files again, if u flash the official one you would have to root the phone again, or u can just install a custom ROM.
Hit thanks if I helped!

bharathreddii said:
If factory reset doesn't work all you need to do it is flash the stock firmware again.. So that would restore all the system files again, if u flash the official one you would have to root the phone again, or u can just install a custom ROM.
Hit thanks if I helped!
Click to expand...
Click to collapse
What software would I use to go about this? and where would I go for looking for those files?

Jester_Man said:
What software would I use to go about this? and where would I go for looking for those files?
Click to expand...
Click to collapse
You would need Odin to flash the ROM, and a stock firmware for ur particular phone and region available at sammobile.com or you would just find one in the android development thread of this forum and the Odin just google it..

bharathreddii said:
You would need Odin to flash the ROM, and a stock firmware for ur particular phone and region available at sammobile.com or you would just find one in the android development thread of this forum and the Odin just google it..
Click to expand...
Click to collapse
Alright, thanks for the help!

Jester_Man said:
Alright, thanks for the help!
Click to expand...
Click to collapse
Don't forget to hit thanks.. It counts!! [emoji12][emoji23]

Nexus 6p weird bootlooping.

Hello xda community!
I received the nexus 6p christmas and after a few hours playing with it, I unlocked, installed twrp and installed cm13. I then installed ak kernal. My phone installs both fine and runs as normal without any FC. Then this is where it gets weird. When I had my new rom and kernal all set up. I go into TWRP and create a backup. I restart and I'm bootlooping. It tells me my device is corrupt. It did this with the original backup of stock rom, cm13, with and without ak kernal installed... and then sometimes my phone will soft-brick (gets stuxk on google logo) I really love cm engine as I habe a theme. But I'm unsure what is happening to my phone.
Any help is appreciated! - thanks.

Info
Xtra-arrow said:
Hello xda community!
I received the nexus 6p christmas and after a few hours playing with it, I unlocked, installed twrp and installed cm13. I then installed ak kernal. My phone installs both fine and runs as normal without any FC. Then this is where it gets weird. When I had my new rom and kernal all set up. I go into TWRP and create a backup. I restart and I'm bootlooping. It tells me my device is corrupt. It did this with the original backup of stock rom, cm13, with and without ak kernal installed... and then sometimes my phone will soft-brick (gets stuxk on google logo) I really love cm engine as I habe a theme. But I'm unsure what is happening to my phone.
Any help is appreciated! - thanks.
Click to expand...
Click to collapse
Wipe everything > Advance Wipe Phone in recovery
Reinstall CM13 through Recovery and don't flash another kernel
:good:

Geeks Empire said:
Wipe everything > Advance Wipe Phone in recovery
Reinstall CM13 through Recovery and don't flash another kernel
:good:
Click to expand...
Click to collapse
Whoa! Don't tell him to wipe everything in the advanced wipe menu, that'll wipe the internal storage too which is completely unnecessary.

Xtra-arrow said:
Hello xda community!
I received the nexus 6p christmas and after a few hours playing with it, I unlocked, installed twrp and installed cm13. I then installed ak kernal. My phone installs both fine and runs as normal without any FC. Then this is where it gets weird. When I had my new rom and kernal all set up. I go into TWRP and create a backup. I restart and I'm bootlooping. It tells me my device is corrupt. It did this with the original backup of stock rom, cm13, with and without ak kernal installed... and then sometimes my phone will soft-brick (gets stuxk on google logo) I really love cm engine as I habe a theme. But I'm unsure what is happening to my phone.
Any help is appreciated! - thanks.
Click to expand...
Click to collapse
Which partitions are you backing up when creating the nandroid with TWRP?

Heisenberg said:
Which partitions are you backing up when creating the nandroid with TWRP?
Click to expand...
Click to collapse
System, data, boot - Installing the kernel made no difference, the device still corrupted on reboot. and then sometimes at least twice it has soft-bricked

Geeks Empire said:
Wipe everything > Advance Wipe Phone in recovery
Reinstall CM13 through Recovery and don't flash another kernel
:good:
Click to expand...
Click to collapse
Already tried it mate, a number of times. no joy.

Xtra-arrow said:
Hello xda community!
I received the nexus 6p christmas and after a few hours playing with it, I unlocked, installed twrp and installed cm13. I then installed ak kernal. My phone installs both fine and runs as normal without any FC. Then this is where it gets weird. When I had my new rom and kernal all set up. I go into TWRP and create a backup. I restart and I'm bootlooping. It tells me my device is corrupt. It did this with the original backup of stock rom, cm13, with and without ak kernal installed... and then sometimes my phone will soft-brick (gets stuxk on google logo) I really love cm engine as I habe a theme. But I'm unsure what is happening to my phone.
Any help is appreciated! - thanks.
Click to expand...
Click to collapse
The bootloader message won't go away until you lock the bootloader. Its just there as a warning to you in case you did not unlock your phone. As for CM I'm sure there are still many bugs to be worked out. I know I'm going to wait before Flashing it until I see people enjoying it as a daily driver. There are some great devs here in the n6p forums though so I recommend checking out some other ROMs too.

XxMORPHEOUSxX said:
The bootloader message won't go away until you lock the bootloader. Its just there as a warning to you in case you did not unlock your phone. As for CM I'm sure there are still many bugs to be worked out. I know I'm going to wait before Flashing it until I see people enjoying it as a daily driver. There are some great devs here in the n6p forums though so I recommend checking out some other ROMs too.
Click to expand...
Click to collapse
i understand the boot message and CM - i have tried other roms too. i'm not the only one who is getting bootloops on every rom. not sure what to do mate. it says corrupted then boot loops upon restart

Xtra-arrow said:
i understand the boot message and CM - i have tried other roms too. i'm not the only one who is getting bootloops on every rom. not sure what to do mate. it says corrupted then boot loops upon restart
Click to expand...
Click to collapse
Maybe this will be helpful. I think you have the red level warning like this user. Seems like the exact same situation.
http://forum.xda-developers.com/showthread.php?p=64403982

Turns out it isn't bootlooping. Its taking at least 3 minutes to turn on. It looks like bootlooping. BUt if finally loaded. After doing my uninstalling of aomw system apps. Its rebooted and keeps optimising apps. 2-4 then restarts and does same

Info
Heisenberg said:
Whoa! Don't tell him to wipe everything in the advanced wipe menu, that'll wipe the internal storage too which is completely unnecessary.
Click to expand...
Click to collapse
It s necessary to Wipe everything when don't know which modification cause the problem.
+ Recovering the backup also not working for this situation.
@Xtra-arrow
Can u explain step-by-step what u did so far
more detail = better help
:good:

Geeks Empire said:
It s necessary to Wipe everything when don't know which modification cause the problem.
+ Recovering the backup also not working for this situation.
@Xtra-arrow
Can u explain step-by-step what u did so far
more detail = better help
:good:
Click to expand...
Click to collapse
No it isn't necessary to wipe the userdata partition. No modifications are stored in the userdata partition. It would only be necessary to wipe system, data, cache, and dalvik cache. And probably flash the vendor partition too. Not userdata though.

I had a similar problem when I botched a SU flash, same warning then it would take forever to boot, then the rom would degrade over the next several minutes. I know its not fun to start over, but it was the only thing that cleared all the problems. I didn't want to take more time finding another solution when going back to stock is so simple with this device. Follow the instructions in step #11 of Heisenberg's guide (great guide, I link it to friends a lot). Then start again, I know, not what you wanted to hear. Hope this helps!
I am also in agreement with Heisenberg in regards to the userdata partition.

Geeks Empire said:
It s necessary to Wipe everything when don't know which modification cause the problem.
+ Recovering the backup also not working for this situation.
@Xtra-arrow
Can u explain step-by-step what u did so far
more detail = better help
:good:
Click to expand...
Click to collapse
Thank you very much for replying. I have found the root of the cause but no solution. Uninstalling or disabling system apps will cause my phone to go into a "optimising apps" boot loop on the next restart. What do you think? ++ every restore I make on twrp either soft bricks or bootloops. Crazy!

Info
Xtra-arrow said:
Thank you very much for replying. I have found the root of the cause but no solution. Uninstalling or disabling system apps will cause my phone to go into a "optimising apps" boot loop on the next restart. What do you think? ++ every restore I make on twrp either soft bricks or bootloops. Crazy!
Click to expand...
Click to collapse
If you are sure about reason Forget ur Backups.
you should completely install Stock Kernel, Rom, Boot.img >> Back to Stock
But If I remember correctly u did this before...
I just have to say Retry Also Install and use Nexus Root Toolkit
:good:

I have reinstalled original stock files from google. I've wiped everything numerous times. Installed ROMs just after. It took me a while but I think it comes down to the system apps. I'm running a custom ROM, cm13 and my phone is running fine. I know if I was to delete all the unwanted apps off my phone, on next reboot it will try and optimise apps, finish. Says starting apps... Then reboots. Follows the same process.

Xtra-arrow said:
I have reinstalled original stock files from google. I've wiped everything numerous times. Installed ROMs just after. It took me a while but I think it comes down to the system apps. I'm running a custom ROM, cm13 and my phone is running fine. I know if I was to delete all the unwanted apps off my phone, on next reboot it will try and optimise apps, finish. Says starting apps... Then reboots. Follows the same process.
Click to expand...
Click to collapse
Can I ask what gapps are you using? Are you using your google account to recover your apps, or are starting fresh each time?
Sent from my Nexus 6P using Tapatalk

Thanks for your reply. I've actually now narrowed itnright down to a few apps, maybe gapps. Sound recorder, voice recorder app and the google app. Either one or more of these cause my optimising apps bootloop.