Develop Bugs

[Q] Stuck in boot loop, trying to return to stock, I think I need to use PIT file

Hi all. I'm in a real pickle here and hoping someone can tell me how to get out of this mess. It's a bit of a long story, but I'll summarise as best I can.
I've had my Galaxy Note 2 LTE (N7105) for a year and I rooted it pretty much the day after I got it. I'm not new to rooting at all (fourth Android device since 2010, all rooted), but I still feel like a noob at times. Over this 2014 Easter period I had time off so I decided to change ROMs.
I was previously using CM 11, which I had been using pretty much since I rooted. And I had updated CM at least once a month, sometimes more frequently. So I was looking for some new ROMs, downloaded about 5 and tried them out. The last two I tried was OmniROM (a 4.4.2 ROM) and CM 11 Remix (also a 4.4.2 ROM). I was using TWRP 2.7.0.2 to do the wipes, caches, flashes, etc. I had no issues flashing OmniROM, but when I flashed CM 11 Remix, I couldn't get in the first time. I was stuck in a boot loop. I pulled the battery, got back into recovery and tried flashing again. Still boot looping. I think the mistake I made was a Data Format. Either way, I finally got CM 11 Remix to load by first wiping, flashing the ROM, GApps, a sensor fix, a camera fix, Devil Kernel and then Super SU. However once in the ROM I was getting constant Google Play Store / Services FCs. Oh, and yes, I went through the typical brand new Android setups, entering my Google account and so on... I found that if I cleared data / caches on both Google Play Store app and Google Play Services app, it gave me temporary joy but as soon as I tried to download any app in Google Play I'd get the FC. Also, my signal was totally gone. I tried flashing back to OmniROM as it was my last known good and working ROM, but now that was boot looping. I even tried some of the other ROMs from that bunch I had, including AOKP. All would boot loop.
So after much trying different GApp packages, I decided to best thing to do would be restore it to stock, root again, then go for the custom ROM (hopefully CM 11 Remix) from a nice clean slate. So I did this. I downloaded the Android 4.3 stock ROM from SamMobile here. Installed Odin 3.07, then loaded it up and flashed the stock ROM. All seemed to go great, but when the ROM was done and phone rebooted, I get stuck in another boot loop! This time at the white "Samsung" logo with the glowing blue edges. Not the model number screen. Also my LED light is on blue, if that means anything.
So I found this thread (post at top of page) which suggests I need to flash the PIT file during the stock ROM installation with Odin. So I found the PIT file here, and I'm ready to flash this along with the stock ROM... HOWEVER, I read something somewhere (can't find it now) that implied if I'm on Android 4.3, flashing a PIT is a bad move. Can anyone comment on that? I guessing since the stock ROM is 4.3, I'm technically on 4.3 (even though I can't get into it).
Or if anything else I'm doing immediately stands out as a seriously stupid move, please let me know. I've been without normal use of my phone for a couple days now and ironically I'm at the point where I'm considering going without a phone for the rest of my life... LOL! AS IF I COULD!
Anyways, any help will be much appreciated!
EDIT: I just realised I should have posted in Troubleshooting, not General Questions... If mods want to move this, please do.

i just suggest that you flash the stock odin without the pit and see if its working out or not. sometimes playing with pit files can screw up your device even more...
btw... next time you play flashing... i'm suggesting you make a backup of your working custom. its will save you lots of time if this kind of problem happen.

edan1979 said:
i just suggest that you flash the stock odin without the pit and see if its working out or not. sometimes playing with pit files can screw up your device even more...
btw... next time you play flashing... i'm suggesting you make a backup of your working custom. its will save you lots of time if this kind of problem happen.
Click to expand...
Click to collapse
I don't have any working ROM. All I have now is a boot loop.

invertedskull said:
I don't have any working ROM. All I have now is a boot loop.
Click to expand...
Click to collapse
I had a problem with my device where I was stuck at boot loader as well, but it was from the rar file of the rom(cm 11) cause I tried downloading it again and it worked.
I suggest you prepare Odin and the stock firmware, wipe factory/cache dalvik, system (advanced), then flash stock firmware, to bring everything back to normal.

Banutu said:
I had a problem with my device where I was stuck at boot loader as well, but it was from the rar file of the rom(cm 11) cause I tried downloading it again and it worked.
I suggest you prepare Odin and the stock firmware, wipe factory/cache dalvik, system (advanced), then flash stock firmware, to bring everything back to normal.
Click to expand...
Click to collapse
Hmmm, I'm not stuck at boot loader, just boot loop. Maybe you meant that?
To clarify, all I can do now is...
1. Boot normally and end up in a boot loop (at "Samsung" white logo with glowing blue edges).
2. Boot into Download mode and from there I can use Odin to flash / install.
3. Boot into stock recovery, which I've never used before (only ever used custom recovery).
I've prepped Odin again, ready to flash the stock firmware, but I've never done a wipe / factory reset with Odin. I don't see any Advanced settings? Did you mean I can do it elsewhere? Cos I see I can do wipes / factory reset from stock recovery.
So should I do that AND then go into Download mode and flash stock firmware with Odin?

invertedskull said:
Hmmm, I'm not stuck at boot loader, just boot loop. Maybe you meant that?
To clarify, all I can do now is...
1. Boot normally and end up in a boot loop (at "Samsung" white logo with glowing blue edges).
2. Boot into Download mode and from there I can use Odin to flash / install.
3. Boot into stock recovery, which I've never used before (only ever used custom recovery).
I've prepped Odin again, ready to flash the stock firmware, but I've never done a wipe / factory reset with Odin. I don't see any Advanced settings? Did you mean I can do it elsewhere? Cos I see I can do wipes / factory reset from stock recovery.
So should I do that AND then go into Download mode and flash stock firmware with Odin?
Click to expand...
Click to collapse
ohhh my bad, I meant boot loop (stuck at samsung logo), mine was stuck there but then after it restarts and goes into recovery mode
do these following steps and you should be fine with your device.
1. Go into recovery mode
2. Wipe factory/reset
3. Wipe cache
4. Wipe dalvik
5. Advance > format/system
Now you have no rom or any OS to load,
1. Power off the device
2. Open Odin on your PC(right click run as administrator)
3. power on your note in Download Mode
4. Connect your device to your PC via USB
5. odin should recognize your device, something blue like " ID" or something there, you should be familiar with that.
6. click PDA, and find the official stock firmware zip you got it from samsung website, and make sure it fits your device(for example if you have your note from italy you should have ITV)
7. Hit Start and it should finish in 5-10 minutes.
Its the cleanest way with Odin, I did some crap on my device and that's how I return it to normal.

Banutu said:
ohhh my bad, I meant boot loop (stuck at samsung logo), mine was stuck there but then after it restarts and goes into recovery mode
do these following steps and you should be fine with your device.
1. Go into recovery mode
2. Wipe factory/reset
3. Wipe cache
4. Wipe dalvik
5. Advance > format/system
Now you have no rom or any OS to load,
1. Power off the device
2. Open Odin on your PC(right click run as administrator)
3. power on your note in Download Mode
4. Connect your device to your PC via USB
5. odin should recognize your device, something blue like " ID" or something there, you should be familiar with that.
6. click PDA, and find the official stock firmware zip you got it from samsung website, and make sure it fits your device(for example if you have your note from italy you should have ITV)
7. Hit Start and it should finish in 5-10 minutes.
Its the cleanest way with Odin, I did some crap on my device and that's how I return it to normal.
Click to expand...
Click to collapse
All good! Cheers man!
I actually went ahead and booted into stock recovery and did the factory reset and partition wipe before I saw your post. And the stock firmware I'd flashed with Odin previously is now booting and I'm finally back in!!! WOOOOOOOOO!!!
Just need to root this bad boy and get back to a nice shiny custom ROM.
Thanks for the advice everyone!

invertedskull said:
All good! Cheers man!
I actually went ahead and booted into stock recovery and did the factory reset and partition wipe before I saw your post. And the stock firmware I'd flashed with Odin previously is now booting and I'm finally back in!!! WOOOOOOOOO!!!
Just need to root this bad boy and get back to a nice shiny custom ROM.
Thanks for the advice everyone!
Click to expand...
Click to collapse
I'm glad to hear that man, peace ^^

Banutu said:
I'm glad to hear that man, peace ^^
Click to expand...
Click to collapse
I have another hurdle... Some built in security is stopping SuperSU from running. It's not Knox, but something like it. I get this error message:
"Unauthorized access to a secured area has been blocked. Tap here for more info."
How can I disable this? I've searched on Google already but so far nothing is helping and I can mostly only find info about Knox...
EDIT: It was goddamn Knox all along... And I just disabled it by means of SuperSU. Finally!

invertedskull said:
I have another hurdle... Some built in security is stopping SuperSU from running. It's not Knox, but something like it. I get this error message:
"Unauthorized access to a secured area has been blocked. Tap here for more info."
How can I disable this? I've searched on Google already but so far nothing is helping and I can mostly only find info about Knox...
EDIT: It was goddamn Knox all along... And I just disabled it by means of SuperSU. Finally!
Click to expand...
Click to collapse
Lolol, see your finding your way on your own ^_^, I was about to give you this link and suggest you to read the comments as well
http://www.w0lfdroid.com/2013/12/Fix-Root-Problem-on-Android-4.3-for-Galaxy-S3-S4-Note2-Note3.html
Unfortunately for me I don't have Note 2 =(, I have an S II Plus, I hope to get Note 2 next month can't wait =S

Banutu said:
Lolol, see your finding your way on your own ^_^, I was about to give you this link and suggest you to read the comments as well
http://www.w0lfdroid.com/2013/12/Fix-Root-Problem-on-Android-4.3-for-Galaxy-S3-S4-Note2-Note3.html
Unfortunately for me I don't have Note 2 =(, I have an S II Plus, I hope to get Note 2 next month can't wait =S
Click to expand...
Click to collapse
Heh, yeah, all is well in my world once again!
The Note 2 is a great device man. I am sure you'll love it. The Note 3 looks great also, but I don't like the ribbed sides (I'm fussy) and last I read there's an eFuze that goes off once rooted or something along those lines. That's sh!t.

invertedskull said:
Heh, yeah, all is well in my world once again!
The Note 2 is a great device man. I am sure you'll love it. The Note 3 looks great also, but I don't like the ribbed sides (I'm fussy) and last I read there's an eFuze that goes off once rooted or something along those lines. That's sh!t.
Click to expand...
Click to collapse
What do you think about the new oneplus one, do you think I should get that instead?
Sent from my GT-I9105P using Tapatalk

Banutu said:
What do you think about the new oneplus one, do you think I should get that instead?
Sent from my GT-I9105P using Tapatalk
Click to expand...
Click to collapse
Hmmm, I haven't seen that one... Feel free to PM me a link.

Help Me!
Banutu said:
I'm glad to hear that man, peace ^^
Click to expand...
Click to collapse
My case is the same case of Invertedskull. I already did all steps as you instructed. I wiped data/cache/system and flash a stock room 4.4.2 of Nordic Rom on SamMobile website.
After flashed, the looping still happens. When I put the charger, the looping stops and goes to the main screen normally. Sometimes, it suddenly restarts but not frequently.
OMG! How to stop it. Pls help me.
My Note 2 is N7105 LTE - Optus (Australia)

mroldman281 said:
My case is the same case of Invertedskull. I already did all steps as you instructed. I wiped data/cache/system and flash a stock room 4.4.2 of Nordic Rom on SamMobile website.
After flashed, the looping still happens. When I put the charger, the looping stops and goes to the main screen normally. Sometimes, it suddenly restarts but not frequently.
OMG! How to stop it. Pls help me.
My Note 2 is N7105 LTE - Optus (Australia)
Click to expand...
Click to collapse
If you have access to anything, and don't get JUST the boot loop, then you DO NOT have the same case I was in. You are probably able to recover from this. Try posting on the Tf Forums. The guys over there are "specialists" in Asus Tf tablets, and as you'll see on this thread (http://www.transformerforums.com/fo...-boot-loop-after-doing-routine-cm-update.html), they gave me a lot of help. Not that I was able to recover, but they were awesome dudes.

mroldman281 said:
My case is the same case of Invertedskull. I already did all steps as you instructed. I wiped data/cache/system and flash a stock room 4.4.2 of Nordic Rom on SamMobile website.
After flashed, the looping still happens. When I put the charger, the looping stops and goes to the main screen normally. Sometimes, it suddenly restarts but not frequently.
OMG! How to stop it. Pls help me.
My Note 2 is N7105 LTE - Optus (Australia)
Click to expand...
Click to collapse
mroldman281, You didn't post again, so I don't know, If You found solution, but since I had same simptoms, and after four days of reinstalling different stock roms, wiping and even messing with PIT via Odin etc..I can say, that in my case the reason for boot loop was faulty battery. The phone worked when it was plugged in and restarted soon after i unplugged USB cable, and just lopped afterwards. Replacement battery put everything back in order. And I am one happy Camper!
Hope this info helps someone else with boot loop problem

same problem stuck in bootloop
hey guys i have the same problem bootloop all the time i tryied stock firmware but nothing happend avec i rooted my note 2 and intalled a costom recovery and a many roms but stuck in bootloop i didn't chage baterry , by the way i wiped cache and reset factory and clear dalvick cache but the same always bootloop
what u suggest i do
ps : i can acces to bootloader or download mode it charge normally

woow get back my note 2 lte alone
hey guys i get back my note 2 i don't know how but it was a succes :victory:
first : i tried so many afficial firmware 4.4.2 and costom roms but didn't change the problem of bootloop
then i remembred what version i was in it was 4.1.1 so i download it from sammobiles thenks to them flash it and boooom the note 2 lte start like a charm
i want to thanks everyone for their help even if they didn't help directly but this past 3 days i read almost all the threads about note 2
well i thinks one of the selutions here is to revert back the the original stock firmware like i did so maybe will fix the bootloop

Please Help!!! Phone in bootloop after flashing TWRP.

Hi Hope someone can help.
History of what I did.
Im on BPA1
1. Rooted with Kingroot
2. Ran ADB Commands step by step.
3. Booted into Download mode, phone showed Developer
4. Booted into Android phone was fine.
5. Booted back into Download Mode.
6. Flashed TWRP with Odin.
7. Phone went into bootloop would not go past Galaxy note 4 screen.
This went on for an hr so I decided to flash stock BPA1 to try get phone back to original state. It flashed fine in ODIN but its still boot looping and wont go passed Note 4 screen.
Im getting very worried. Can someone help please

gersrt said:
Hi Hope someone can help.
History of what I did.
Im on BPA1
1. Rooted with Kingroot
2. Ran ADB Commands step by step.
3. Booted into Download mode, phone showed Developer
4. Booted into Android phone was fine.
5. Booted back into Download Mode.
6. Flashed TWRP with Odin.
7. Phone went into bootloop would not go past Galaxy note 4 screen.
This went on for an hr so I decided to flash stock BPA1 to try get phone back to original state. It flashed fine in ODIN but its still boot looping and wont go passed Note 4 screen.
Im getting very worried. Can someone help please
Click to expand...
Click to collapse
MAke sure you dont have the memory card used when unlocking bootloader, inside the phone. It will cause bootloop. IF bootloop persists, flash stock firmware, go to recovery and clear cache/data etc. It should boot.
For perfect root and twrp, refer my post #501 (http://forum.xda-developers.com/not...der-unlock-t3358913/post66386928#post66386928)

felixtaf said:
MAke sure you dont have the memory card used when unlocking bootloader, inside the phone. It will cause bootloop. IF bootloop persists, flash stock firmware, go to recovery and clear cache/data etc. It should boot.
For perfect root and twrp, refer my post #501 (http://forum.xda-developers.com/not...der-unlock-t3358913/post66386928#post66386928)
Click to expand...
Click to collapse
Cheers Mate, I'm sure I've already tried this, I will try again when I get home.
Thanks for your input.
Il let ya know.

felixtaf said:
MAke sure you dont have the memory card used when unlocking bootloader, inside the phone. It will cause bootloop. IF bootloop persists, flash stock firmware, go to recovery and clear cache/data etc. It should boot.
For perfect root and twrp, refer my post #501 (http://forum.xda-developers.com/not...der-unlock-t3358913/post66386928#post66386928)
Click to expand...
Click to collapse
First and foremost... THANK YOU!
I've been pulling my hair out for weeks trying to get my phone to boot, but this boot loop has been driving me insane! I've probably flashed 7 different factory ROMs in Odin no less than 5 times each!
And all I had to do was pull my SD card out??
Second:
How did you know that???
Sent from my SM-G900V using XDA-Developers mobile app

Wired4Fun said:
First and foremost... THANK YOU!
I've been pulling my hair out for weeks trying to get my phone to boot, but this boot loop has been driving me insane! I've probably flashed 7 different factory ROMs in Odin no less than 5 times each!
And all I had to do was pull my SD card out??
Second:
How did you know that???
Sent from my SM-G900V using XDA-Developers mobile app
Click to expand...
Click to collapse
It's a common mistake.

Well, thank you again....
Sent from my SM-G900V using XDA-Developers mobile app

Tiny little explanation, When rooting and unlocking your bootloader via ADB, the script wipes your SD card and puts a special code in it to backup your phones original CID. This may be used to unbrick your phone one day. So your NEWLY unlocked phone is using a new CID and your SD card is on the old one. Hence the boot loop. So when reading the OP, I thought the same thing. I didn't seem his say he pulled out his SD card after rooting. Hopefully you guys got it working again.

Lol, Honestly I dint figure it out. I read somewhere in the forums about it. Dont remember exactly who suggested it. But, it worked for me.
Did it work for you?

I have same problem, was on BPA1, unlocked bootloader, flashed twrp, something went wrong had to flash stock again, CPL1 loads up fine but when flashing back to BPA1 runs into bootloop, help.

you rock
felixtaf said:
MAke sure you dont have the memory card used when unlocking bootloader, inside the phone. It will cause bootloop. IF bootloop persists, flash stock firmware, go to recovery and clear cache/data etc. It should boot.
For perfect root and twrp, refer my post #501 (http://forum.xda-developers.com/not...der-unlock-t3358913/post66386928#post66386928)
Click to expand...
Click to collapse
you rock mate ... itried this for 2 hrs and all i had to so is take the damn sd out...thanks

Stuck in Boot loop after weeks of normal usage

Hi.
I have a problem with my D855. My phone is rooted and runs the fulmics ROM. Everything was working fine, , on Fulmics 5.3, except than one day, I was using my phone normally and then it crashed. I saw the phone rebooting, but for some reason it got stuck. The phone tried to boot unsuccessfully until the "firmware update" went through, after what it reboots again (unsuccessfully) and so on.
At that time, I was able to access twrp, do some backup, and flash properly with a downgraded version of fulmics (from 5.3 to 4.1).
It was able to boot again and use my phone like before. Yet, after one month of usage, the same problem happened on version 4.1. The phone crashed and now cannot boot.
Any idea of where it is coming from? Should I go back to stock? Should I contact customer service?

What did you do before the phone crashes ?
I think you probably should flash the stock ROM and wait for an other crash... or not.

Jb-kun said:
What did you do before the phone crashes ?
I think you probably should flash the stock ROM and wait for an other crash... or not.
Click to expand...
Click to collapse
I haven't done anything special. I think that the first time I was playing on candy crush. The second time I was just looking at pictures in my gallery.
I was using the ROM without any tweaks or extra modules such as Xposed. Just regular use.
Update on my situation: I switched back to stock ROM and it seems to work OK for now (it has been 4 days). So I will wait and see if new problems happen. By the way, it was extremely difficult for me to get back to Stock directly from fulmics ROM. I tried several methods that I have found on xda based on LGUP or LG Flash tool without success. For some reason I was not able to connect the phone to my PC in download mode.
The only way that I found was to use a nandroid backup that I did just after rooting the phone and that was based on stock ROM.

shewshain said:
I haven't done anything special. I think that the first time I was playing on candy crush. The second time I was just looking at pictures in my gallery.
I was using the ROM without any tweaks or extra modules such as Xposed. Just regular use.
Update on my situation: I switched back to stock ROM and it seems to work OK for now (it has been 4 days). So I will wait and see if new problems happen. By the way, it was extremely difficult for me to get back to Stock directly from fulmics ROM. I tried several methods that I have found on xda based on LGUP or LG Flash tool without success. For some reason I was not able to connect the phone to my PC in download mode.
The only way that I found was to use a nandroid backup that I did just after rooting the phone and that was based on stock ROM.
Click to expand...
Click to collapse
You can also use the Stock rom flashable from twrp. So you can wipe the system partition and get a "better situation" than a nandroid backup that should be with an old version.
Or use this that has also root and other improvements.

shewshain said:
Hi.
I have a problem with my D855. My phone is rooted and runs the fulmics ROM. Everything was working fine, , on Fulmics 5.3, except than one day, I was using my phone normally and then it crashed. I saw the phone rebooting, but for some reason it got stuck. The phone tried to boot unsuccessfully until the "firmware update" went through, after what it reboots again (unsuccessfully) and so on.
At that time, I was able to access twrp, do some backup, and flash properly with a downgraded version of fulmics (from 5.3 to 4.1).
It was able to boot again and use my phone like before. Yet, after one month of usage, the same problem happened on version 4.1. The phone crashed and now cannot boot.
Any idea of where it is coming from? Should I go back to stock? Should I contact customer service?
Click to expand...
Click to collapse
Same problem here. Normal usage suddenly started to reboot and now it's stuck in boot loop

Coming from Fulmics too - stopped working one fine day.
Now, continues to boot-loop at the initial LG screen. Trying to get into the recovery shows me the the 'Factory Reset' screen, but beyond that leads to boot-loops again. Even the Download mode loops!
I'm at my wits end without a solution in sight.

Blysterk said:
You can also use the Stock rom flashable from twrp. So you can wipe the system partition and get a "better situation" than a nandroid backup that should be with an old version.
Or use this that has also root and other improvements.
Click to expand...
Click to collapse
Thank you for this advice. I was able to update my stock ROM after the Nandroid backup through LGUP, but your method would have been faster.
But anyway, I am waiting to see if I am stuck with bootloops again, using non-root stock version, so I can send it to customer service if this happen again.
AhmadAlmousa said:
Same problem here. Normal usage suddenly started to reboot and now it's stuck in boot loop
Click to expand...
Click to collapse
abourdeau said:
I have the exact same problem, I even bought a second battery with no success.
Click to expand...
Click to collapse
Are you using Fulmics ROM as well? Can you have access to TWRP? I was able to connect to a PC in the recovery mode and to transfer files before flashing, in case you need some basic backup...

prakhargr8 said:
Coming from Fulmics too - stopped working one fine day.
Now, continues to boot-loop at the initial LG screen. Trying to get into the recovery shows me the the 'Factory Reset' screen, but beyond that leads to boot-loops again. Even the Download mode loops!
I'm at my wits end without a solution in sight.
Click to expand...
Click to collapse
Silly question, but are you sure that you selected "Yes" when the screen asks you about factory reset? you have to press "volume down" and the "power button", since the default answer is no.

shewshain said:
Silly question, but are you sure that you selected "Yes" when the screen asks you about factory reset? you have to press "volume down" and the "power button", since the default answer is no.
Click to expand...
Click to collapse
Yes, of course I was able to access TWRP successfully earlier.
Curiously enough, the phone boot-loops in regular startup, Download mode and trying to get to recovery. However, it doesn't restart itself and fall into a loop, while on the Factory Reset menu. Am I correct in assuming that the battery could not be the root cause of the overall problem? Because if it was, it would likely loop even on this Factory Reset menu as well as far as I understand.
Unfortunately, the phone restarts as soon as it lands in the Download mode so I cannot even restore to stock.
EDIT: Okay, weirdly enough it just booted and reached the homescreen before restarting again. What I did was let it charge to a 100% and tried booting while plugged in. Could it be the battery after all? Though this exact set of steps hasn't been helpful before.

Boot Looping Help Please

I purchased a 5x for my wife so she can get on Project Fi. They said it was stuck boot looping, thinking I could solve the problem.
Here are the basics.
-Yes, I can get into boot loader (the menu of start, recovery, etc), but I can't get into TWRP. Tried flashing TWRP a few times and nothing. SkipSoft recognizes that its installed though.
-After bootlooping for awhile, it will load normally and work fine. However it wants to update to the newest version of android. I run the ota and back to bootlooping. It will show the android dude and say "error". Will eventually start bootlooping and then boot normally.
-I have flashed different stock versions. I tried the newest, the second to newest and the last M available. All will flash but continue the bootlooping.
Bootlooping can be anywhere from 1 minute to 10+.
The device will also first display something like, "Your device software can't be checked for corruptions. Please lock the bootloader"
But it'll show up whether the bootloader is locked or not.
The phone will freeze at some point. Whether right away or after 5 minutes. It freezes and then restarts and goes through the bootloop again.
So what else can/should I do? I've never dealt with Kernels but wondering if the last owner did something to them. Is there a way to flash stock kernels just incase or is this done when I flash a Google Factory Stock Image?
Would flashing a non-stock rom be a good idea?
Thanks

So I tried sideloading. I was able to get into the stock recovery. I tried wiping cache and data, then tried installing the newest stock rom.
Everything seemed to work. Then I had to restart. A message popped up after the same "Your device software can't be checked for corruptions. Please lock the bootloader". It had the title in blue stating "Encryption unsuccessful".
Then said, "Encryption was interrupted and can't complete. As a result, the data on your phone is no longer accessible. To resume using your phone you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google Account."
Then there is a single button that says, "Reset Phone".
Problem still persists.
Help please...

Why did you bought a bootlooped phone?

Sin Stalker said:
I purchased a 5x for my wife so she can get on Project Fi. They said it was stuck boot looping, thinking I could solve the problem.
Here are the basics.
-Yes, I can get into boot loader (the menu of start, recovery, etc), but I can't get into TWRP. Tried flashing TWRP a few times and nothing. SkipSoft recognizes that its installed though.
-After bootlooping for awhile, it will load normally and work fine. However it wants to update to the newest version of android. I run the ota and back to bootlooping. It will show the android dude and say "error". Will eventually start bootlooping and then boot normally.
-I have flashed different stock versions. I tried the newest, the second to newest and the last M available. All will flash but continue the bootlooping.
Bootlooping can be anywhere from 1 minute to 10+.
The device will also first display something like, "Your device software can't be checked for corruptions. Please lock the bootloader"
But it'll show up whether the bootloader is locked or not.
The phone will freeze at some point. Whether right away or after 5 minutes. It freezes and then restarts and goes through the bootloop again.
So what else can/should I do? I've never dealt with Kernels but wondering if the last owner did something to them. Is there a way to flash stock kernels just incase or is this done when I flash a Google Factory Stock Image?
Would flashing a non-stock rom be a good idea?
Thanks
Click to expand...
Click to collapse
When my Nexus 5x got into bootloop, I sent it to LG and they had to change the whole circuit. So yeah.

When you flash Google Factory Image, it flash the stock kernel.
If you have warranty, then send it to Google/LG. If you haven't got, then you're in problem. New motherboard needed, but it's expensive.

See the following thread for more info.
https://forum.xda-developers.com/nexus-5x/help/5x-bootloop-cause-fix-t3476794/

khalifakk said:
Why did you bought a bootlooped phone?
Click to expand...
Click to collapse
Cause its cheaper.

Sin Stalker said:
Cause its cheaper.
Click to expand...
Click to collapse
Then face the consequences...

khalifakk said:
Then face the consequences...
Click to expand...
Click to collapse
What consequences?

Hardware bootloop can't be fix by software.

Duckscreen said:
Hardware bootloop can't be fix by software.
Click to expand...
Click to collapse
Exactly. Everyone has either been able to get a replacement under warranty or was pretty much screwed if it was out of warranty.
Sent from my Nexus 5X using Tapatalk

Sin Stalker said:
What consequences?
Click to expand...
Click to collapse
A bootlooped phone for ever....

I recommend you will install kernel adiutor app after try rooting
I recommend you will install kernel adiutor app after try rooting
Almost I got no bootloop even no random reboot nexus 5x's state

Note 4 N910P rooted- crash followed by phone being stuck on logo

So i got my note 4 sprint variant a few weeks ago. Rooted it using CF auto root, installed twrp 3.1.0 and installed cm13 on it. It ran fine for a few days then out of nowhere it would shut off and when i tried rebooting it, it would get stuck on logo screen, the blue led would just stay on and then nothing. I thought it maybe the rom so i tried a deoxed rom and the same thing happened. 3 more roms later i kept getting the random crash and then not being able to go past the boot screen.
I don't have xposed installed, or magisk. Just plain root. i am forced to make daily backups using twrp just in case my phone blacks out again. Has this problem happened to any of you guys before? Is there a fix or do i have to break the receipt out?

Personally, I've read about issues on CM and lack of SPen features on CM so I didn't try CM.
But when I ran CM on another Samsung S model phone, I did run CM but always wiped internal memory when switching because app data isn't compatible between the two OS platforms.
Did you wipe internal memory? Have you tried modified stock ROMs? UN7 with modset is a well featured ROM based on Note7. And stable too. Currently using Beastmode kernel but there's a kernel being developed for it.
Sent from my SM-N920P using Tapatalk

mrblack92 said:
So i got my note 4 sprint variant a few weeks ago. Rooted it using CF auto root, installed twrp 3.1.0 and installed cm13 on it. It ran fine for a few days then out of nowhere it would shut off and when i tried rebooting it, it would get stuck on logo screen, the blue led would just stay on and then nothing. I thought it maybe the rom so i tried a deoxed rom and the same thing happened. 3 more roms later i kept getting the random crash and then not being able to go past the boot screen.
I don't have xposed installed, or magisk. Just plain root. i am forced to make daily backups using twrp just in case my phone blacks out again. Has this problem happened to any of you guys before? Is there a fix or do i have to break the receipt out?
Click to expand...
Click to collapse
Try Lineage 14.
https://forum.xda-developers.com/showthread.php?p=70508450
Sent from my trltespr using XDA-Developers Legacy app

samep said:
Personally, I've read about issues on CM and lack of SPen features on CM so I didn't try CM.
But when I ran CM on another Samsung S model phone, I did run CM but always wiped internal memory when switching because app data isn't compatible between the two OS platforms.
Did you wipe internal memory? Have you tried modified stock ROMs? UN7 with modset is a well featured ROM based on Note7. And stable too. Currently using Beastmode kernel but there's a kernel being developed for it.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
Thanks I will give it a try when i get the chance this weekend. It's so strange out of all the devices i've rooted this is the only one to give me this crazyness. Yes always wipe internal, system, cache, and dalvik cache.

Even on stock it gave me the random crash and no boot past the samsung logo. I think it's safe to say that this thing is ****ed lol

mrblack92 said:
Even on stock it gave me the random crash and no boot past the samsung logo. I think it's safe to say that this thing is ****ed lol
Click to expand...
Click to collapse
Though not normal, these non boots on Samsung logo should be corrected by wiping dalvik-cache or factory reset. If not, something may be wrong.
That said, the initial boot after flash to optimize applications can easily take more than 12 minutes. Much longer if many apps are to be optimized. Shorter if factory reset is applied (less user apps to optimize but still has some optimization to do).
Are you familiar with reactivation lock or eMMC failure? When you flash stock tar in Odin, check your phone's display and Odin log for errors. A failed boot may boot to download mode and indicate an eMMC error.
Outside of those issues, I'd say wipe everything but ext sdcard, pull the battery, wait at least 30 seconds while discharging the power circuit with power button press and hold (not too firmly). Reinstall battery and boot directly to download mode and flash the stock tar in Odin using Odin defaults. Let it auto reboot. Note any failures.
Alternately, you can remove the ext sdcard or delete the Android folder on it. A functional phone should boot rather quickly with the wipes and no errors; shouldn't stay at the Samsung logo very long but still needs to initialize and find network and start the auto start apps. But prior to initial boot, you should also see it make a brief stop in stock recovery to initialize csc before booting system.
Sent from my SM-N920P using Tapatalk

samep said:
Though not normal, these non boots on Samsung logo should be corrected by wiping dalvik-cache or factory reset. If not, something may be wrong.
That said, the initial boot after flash to optimize applications can easily take more than 12 minutes. Much longer if many apps are to be optimized. Shorter if factory reset is applied (less user apps to optimize but still has some optimization to do).
Are you familiar with reactivation lock or eMMC failure? When you flash stock tar in Odin, check your phone's display and Odin log for errors. A failed boot may boot to download mode and indicate an eMMC error.
Outside of those issues, I'd say wipe everything but ext sdcard, pull the battery, wait at least 30 seconds while discharging the power circuit with power button press and hold (not too firmly). Reinstall battery and boot directly to download mode and flash the stock tar in Odin using Odin defaults. Let it auto reboot. Note any failures.
Alternately, you can remove the ext sdcard or delete the Android folder on it. A functional phone should boot rather quickly with the wipes and no errors; shouldn't stay at the Samsung logo very long but still needs to initialize and find network and start the auto start apps. But prior to initial boot, you should also see it make a brief stop in stock recovery to initialize csc before booting system.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
I recieved no errors on my phone screen during the flash. It always passed right through, although one time it did fail due to a faulty usb cable. Other than that once incident I've had no issues with flashing tars through odin. Thanks for your help! really appreciate. I will give the the battery discharge a shot when i get the chance.