Stuck on bootloop - T-Mobile Samsung Galaxy Note5

i'm running the arter97 X kernel w/ stock rom on my sm-n920t. i have xposed installed and a few thing disabled through package disabler pro and thats about it. phone worked fine for weeks. went to sleep with it at 9% around 2am this morning with the intention of charging when i woke. got up @ 10am, plugged it up, hit the power button and i've been stuck in bootloop ever since. im able to get to CWM recovery mode but my backups are on my pc, not the sd card. when i plug into the pc the bloody thing doesn't even recognize it (it does kinda, b/c it makes the sound but never shows). i've got the proper drivers installed. not sure what to do or even how this happened. Would greatly appreciate any advice...

newguy15 said:
i'm running the arter97 X kernel w/ stock rom on my sm-n920t. i have xposed installed and a few thing disabled through package disabler pro and thats about it. phone worked fine for weeks. went to sleep with it at 9% around 2am this morning with the intention of charging when i woke. got up @ 10am, plugged it up, hit the power button and i've been stuck in bootloop ever since. im able to get to CWM recovery mode but my backups are on my pc, not the sd card. when i plug into the pc the bloody thing doesn't even recognize it (it does kinda, b/c it makes the sound but never shows). i've got the proper drivers installed. not sure what to do or even how this happened. Would greatly appreciate any advice...
Click to expand...
Click to collapse
Have you tried going into recovery and plugging in USB cable to the phone and AC charger for 30 minutes and then power off the phone in recovery mode then power up the phone using the power button?
If that don't work do a full wipe in recovery including factory reset.
Doing a full wipe in recovery by default will not wipe the internal sdcard unless you select that option.
Good luck,
Have a happy new years.
Sent from my SM-G928T using Tapatalk

Misterjunky said:
Have you tried going into recovery and plugging in USB cable to the phone and AC charger for 30 minutes and then power off the phone in recovery mode then power up the phone using the power button?
Sent from my SM-G928T using Tapatalk
Click to expand...
Click to collapse
just tried this and nothing. Guess i'll attempt the wipe. By wipe i'm assuming you mean factory reset in CWM?
and if so, am I able to (or is it sensible, rather) restore the phone from the last backup/nandroid that contained Xposed+Arter97 Kernel?

newguy15 said:
just tried this and nothing. Guess i'll attempt the wipe. By wipe i'm assuming you mean factory reset in CWM?
and if so, am I able to (or is it sensible, rather) restore the phone from the last backup/nandroid that contained Xposed+Arter97 Kernel?
Click to expand...
Click to collapse
It's best not to do a restore, start fresh for best results.
I would also suggest that you flash twrp recovery and get rid of philz.
A factory reset in twrp does not wipe internal sdcard unless you select it.
99% of people who have the G928T S6 EDGE+ and the N920T Note 5 all use twrp.
Here is the download link for twrp:
https://www.androidfilehost.com/?fid=24352994023704396
Flash this in recovery.
Good luck,
Happy New Years.
Sent from my SM-G928T using Tapatalk

Related

CM7 boot loop

I'm stuck in a boot loop and I have no idea why, and I've tried wiping cache, wiping data/factory reset, and re-flashing the CM7 rom. Nothing worked. What happned was, my phone died, so I plugged it in, and it went into "charging mode". The phone will boot, but the touchscreen doesnt work, and non of the radios turn on, so that it can just charge I guess? anyway, the phone got to about 20% battery so I decided to reboot it so I could actually use it while charging, but when I did, it started boot looping. I tried everything mentioned above and its still boot looping. Is there anything else I can try?
let phone go all the way dead
I run Cyanogemod with Da_G's kernel and I let the device die. I had a similar lock up when I finally plugged the charger back in. After it got to about 8 or 9% is all and was still unresponsive, couldn't unlock the screen I simply pulled the battery AND REMOVED THE CHARGE CORD and counted to twenty, slapped it back in and held the power button for the count of ten and let go. It booted back up fine and no issues since.
I assumed you tried a battery pull?
fukenbiker said:
I run Cyanogemod with Da_G's kernel and I let the device die. I had a similar lock up when I finally plugged the charger back in. After it got to about 8 or 9% is all and was still unresponsive, couldn't unlock the screen I simply pulled the battery AND REMOVED THE CHARGE CORD and counted to twenty, slapped it back in and held the power button for the count of ten and let go. It booted back up fine and no issues since.
I assumed you tried a battery pull?
Click to expand...
Click to collapse
Yea, that non responsive state is what led me to reboot. It only does that when the phone is dead and you plug it in. I assume it's because with cm7 there is no way to charge while the phone is off, at least that's the way it was with my infuse and captivate. So that's not the issue. It's that when I rebooted to get out of that state, it gets to the cm7 boot logo and then reboots. It's never done that before, and I do that a lot. I searched for this issue and I found someone with a nexus on cm7 that had a boot loop, and it was solved by some cwm zip that deleted the partitions, then once you do that, if you flash cm7, all will be well, but I don't know if that's applicable to this situation.
EDIT: I tried the battery pull, I left it out for 20 min and it's still boot looping
How are you getting into recovery? Seems once you get into recovery and wipe data/factory reset and flash version 4 and flash the kernel it would fix boot loop.
I use three button method to get to clockworkmod recovery.
If you Odin back to stock the method to get download mode for me was volume down only when plugging in.
I have a 400mb+ size file used by recovery of a working image of my favorite setup to flash back to. Everyone should take a few minutes and boot into recovery and make a backup to flash to once you get up and running good.
Sent from my SGH-I727 using CyanogenMod
I tried to duplicate. You are so correct I put the battery back in after making sure the phone was off and then plugged in the power.
For brief moment the big battery symbol appeared, but rather than continuing to stay with that and charge, it blinked away and promptly booted up into that frozen screen and no radio signal.
I had 50% charge when I tested this just now.
Upon pressing the power button I got the shutdown menu, but the screen was still unresponsive and wouldn't let me select reboot.
Ended up doing another battery pull (with no power cord of course)
I don't see how you did it, reboot while in that state escapes me.
Sent from my SGH-I727 using CyanogenMod
fukenbiker said:
I tried to duplicate. You are so correct I put the battery back in after making sure the phone was off and then plugged in the power.
For brief moment the big battery symbol appeared, but rather than continuing to stay with that and charge, it blinked away and promptly booted up into that frozen screen and no radio signal.
I had 50% charge when I tested this just now.
Upon pressing the power button I got the shutdown menu, but the screen was still unresponsive and wouldn't let me select reboot.
Ended up doing another battery pull (with no power cord of course)
I don't see how you did it, reboot while in that state escapes me.
Sent from my SGH-I727 using CyanogenMod
Click to expand...
Click to collapse
I hold the power button until the phone reboots.
fukenbiker said:
How are you getting into recovery? Seems once you get into recovery and wipe data/factory reset and flash version 4 and flash the kernel it would fix boot loop.
I use three button method to get to clockworkmod recovery.
If you Odin back to stock the method to get download mode for me was volume down only when plugging in.
I have a 400mb+ size file used by recovery of a working image of my favorite setup to flash back to. Everyone should take a few minutes and boot into recovery and make a backup to flash to once you get up and running good.
Sent from my SGH-I727 using CyanogenMod
Click to expand...
Click to collapse
I use the three button combo to get into recovery, and I did wipe data then flash both version 4 and the kernel, and it still loops. I am so confused as to how in the world this happened... anyway, I tried to go back to stock using odin twice and it just got stuck at system.img.ext4.
Oh dear you must take this to the Odin thread.... You belong there until you flash back to stock. Did you try only holding volume down when plugging in to download mode? Your skyrocket is powered down when you try?
Sent from my SGH-I727 using xda premium
I got into download mode fine the first time. then when it got stuck, I changed to a usb port on the back of my pc, but it still got stuck. now it just boots right into download mode.
I don't know what changed.. but since going back to stock wouldn't work, I decided to re flash cwm and try to install cm7 again, and I'm now back up and running just fine. This whole situation was very odd... Thank you for being helpful.
Odin3-v1.85.zip is what you have set up on your computer?
Glad you fixed it.
Sent from my SGH-I727 using CyanogenMod

A Warning for TWRP 2.3.1.0

If you let the phone battery run down, it will not, I repeat WILL NOT boot back up out of recovery.
When I plug the charger in it just boot it right back into recovery, which we all know won't charge the battery.
Pull the battery, put battery back in, plug in the charger....boot right back into recovery.
Power off from recovery with charger still plugged in...boot right back up in recovery.
Reboot system from recovery...boot right back up in recovery.
No way to charge the battery without getting out of recovery first.
No way to boot out of recovery without enough juice in the battery.
I had to use the extended battery (spare) to boot up the phone and...well you guest it...to flash the "other" recovery to get it working normal again.
Thunderbolt
Miui
TWRP 2.3.1.0
Works fine on earlier version, if this is a false alarm, then please delete.
Update: After reading through a few forums, TWRP might be able to charge while in recovery. It doesn't work for me.
That's a +1 for 4ext. It let's you charge the battery in recovery.
Sent from my Thunderbolt using Tapatalk 2
Your phone should charge in the powered off state though.
Thought so too but I know for a fact that cwm boots you into recovery as soon as there is enough juice to boot. Then having the screen on starting what little there is left. I know because I dealt with that for a month before I realized that my stock battery finally took a drive and wasn't retaining a full charge anymore.
Sent from my SCH-I535 using xda app-developers app
Its recovery 101 never mess with recovery unless you have a decent charge. You are just asking for trouble. I agree it makes 4ext look better because you can charge while in its recovery. If you let your phone die in recovery then you deserve it. Not to sound harsh but for the longest time when devs post roms they said make sure your battery is charged before flashing the rom. You think they was joking? lol
I remember having to do that with the Droid Eris.
Sent from my Thunderbolt using Tapatalk 2
I think what he means is, if you let your phone die normally, then plug it in to charge, it will boot to recovery. I had that happen to me when i first tried clockwork touch.
Sent from my Liquid ICS Bolt
Let me clear it up a bit.
If there's not enough juice in the battery to boot up the phone. If you push and hold the power button and nothing happen then you're screwed.
As soon as you plug in the charger, it will boot right to TWRP. you can not stop it from booting into TWRP, when you power it off from within TWRP it will boot right back into TWRP as long as the charger is connected.
Bottom Line:
If your battery went dead (under normal usage condition) and you don't have a good spare. You are SCREWED. This is a FATAL bug.
There's no way to charge a dead battery.
DarkJedi thinks that I'm in TWRP while the phone went dead. The answer is NO. The battery went dead under standby.
Dark Jedi said:
Its recovery 101 never mess with recovery unless you have a decent charge. You are just asking for trouble. I agree it makes 4ext look better because you can charge while in its recovery. If you let your phone die in recovery then you deserve it. Not to sound harsh but for the longest time when devs post roms they said make sure your battery is charged before flashing the rom. You think they was joking? lol
Click to expand...
Click to collapse
You're not understanding the post. This has nothing to do with messing with TWRP. Battery went dead under normal using condition, has nothing to do with recovery.
Shadow Death said:
Your phone should charge in the powered off state though.
Click to expand...
Click to collapse
That's the problem, it will not power down out of TWRP, as soon as you plug in the charger it will boot right back into TWRP.
It has the same cwm bug there used to be. When you plug the phone in to charge it boots into recovery.
Sent from my Thunderbolt using Tapatalk 2
That's good to know, I had been using TWRP on my Thunderbolt so I guess it's time to switch back to 4ext, i just wish there was software keyboard support in 4ext.
Also with a note, I had this problem the op had when using TWRP on my Asus Transformer, actually strangely, while the recovery was installed it would not charge the device at all, not even when turned off. Once TWRP was taken off of it, and CWM back on, it charged properly. After using TWRP I can say for some reason this recovery has some serious game changing bugs.
EDIT: Also, "Boot Manager" doesn't seem to be compatible with restoring backups made with TWRP.
Give this build a shot and see if it fixes the charging:
http://techerrata.com/dees_troy/mecha.img
Ellises said:
That's good to know, I had been using TWRP on my Thunderbolt so I guess it's time to switch back to 4ext, i just wish there was software keyboard support in 4ext.
Also with a note, I had this problem the op had when using TWRP on my Asus Transformer, actually strangely, while the recovery was installed it would not charge the device at all, not even when turned off. Once TWRP was taken off of it, and CWM back on, it charged properly. After using TWRP I can say for some reason this recovery has some serious game changing bugs.
EDIT: Also, "Boot Manager" doesn't seem to be compatible with restoring backups made with TWRP.
Click to expand...
Click to collapse
No idea what your trouble with the Transformer were but charging on the Transformer isn't done in recovery and changing recovery wasn't the fix.
The Thunderbolt & most all HTC devices made after it use recovery for charging. There's a handful of HTC binaries & a special init.rc that make the device charge while turned off. None of this is part of the recovery code so it's not inherent to TWRP itself.
Dees_Troy said:
Give this build a shot and see if it fixes the charging:
http://techerrata.com/dees_troy/mecha.img
Click to expand...
Click to collapse
my port is busted so i cant test charging but the build does work
Another tester confirmed that it was fixed in that version, so I have updated everything.

[Q] Bricked Phone, and T-Mobile Replacement policy

I was running CM 10 and tried to flash the stock ROM. I flashed it fine (no errors in CWM, I also did clear the cache, dalvik, wiped system) after that I pressed reboot and nothing happened no Samsung just a black screen. I waited for around 10 minutes and then finally took out the battery. After that the phone wouldn't boot, recovery or download wouldn't work either. I tried everything I could and figured it's hard bricked. So if you have any suggestions on this they will be greatly appreciated. I still have my T-Mobile warranty, and the question I have is would they accept a phone that is rooted, but won't even boot so basically there is no way of finding out if it's rooted or not?
aanonymoushuman said:
I was running CM 10 and tried to flash the stock ROM. I flashed it fine (no errors in CWM, I also did clear the cache, dalvik, wiped system) after that I pressed reboot and nothing happened no Samsung just a black screen. I waited for around 10 minutes and then finally took out the battery. After that the phone wouldn't boot, recovery or download wouldn't work either. I tried everything I could and figured it's hard bricked. So if you have any suggestions on this they will be greatly appreciated. I still have my T-Mobile warranty, and the question I have is would they accept a phone that is rooted, but won't even boot so basically there is no way of finding out if it's rooted or not?
Click to expand...
Click to collapse
First error was you wiped system before reboot so there was nothing there to boot into... Leave the battery out for a bit then insert and boot into recovery.. reflash rom and this time only wipe cache and dalvik not system.. reboot.. Also how charged was the battery? maybe it is almost dead and needs charging!
Racing19969 said:
First error was you wiped system before reboot so there was nothing there to boot into... Leave the battery out for a bit then insert and boot into recovery.. reflash rom and this time only wipe cache and dalvik not system.. reboot.. Also how charged was the battery? maybe it is almost dead and needs charging!
Click to expand...
Click to collapse
I cant boot into anything at all... And the baterry was fine it was maybe at 60% when I flashed
aanonymoushuman said:
I cant boot into anything at all... And the baterry was fine it was maybe at 60% when I flashed
Click to expand...
Click to collapse
what rom were you flashing when this happened?? if it was a stock rom you should have been using odin.. unless it was one of the stock CWM flashable roms... if you can't get it going send me a pm.. I do JTAG repair
aanonymoushuman said:
I was running CM 10 and tried to flash the stock ROM. I flashed it fine (no errors in CWM, I also did clear the cache, dalvik, wiped system) after that I pressed reboot and nothing happened no Samsung just a black screen. I waited for around 10 minutes and then finally took out the battery. After that the phone wouldn't boot, recovery or download wouldn't work either. I tried everything I could and figured it's hard bricked. So if you have any suggestions on this they will be greatly appreciated. I still have my T-Mobile warranty, and the question I have is would they accept a phone that is rooted, but won't even boot so basically there is no way of finding out if it's rooted or not?
Click to expand...
Click to collapse
Wait... you wiped system after flashing stock...? That wiped the stock rom That's why nothing booted after the reboot.
I don't know why you can't get into download mode... When you plug in a usb when the battery is out does the phone vibrate? If not, try another usb cable. If that fails then you do have a hardware issue. If the phone vibrates hold vol + and vol - and power and reinsert battery-you should get download mode.
AFAIK, they (T-Mo) put the phone in download mode and check the flash counter. If it says anything other than "no" they will not accept it. Any odin flash adds to the flash counter.
anactoraaron said:
Wait... you wiped system after flashing stock...? That wiped the stock rom That's why nothing booted after the reboot.
I don't know why you can't get into download mode... When you plug in a usb when the battery is out does the phone vibrate? If not, try another usb cable. If that fails then you do have a hardware issue. If the phone vibrates hold vol + and vol - and power and reinsert battery-you should get download mode.
AFAIK, they (T-Mo) put the phone in download mode and check the flash counter. If it says anything other than "no" they will not accept it. Any odin flash adds to the flash counter.
Click to expand...
Click to collapse
As said before it's a brick, no screen, no vibration nothing. And I don't think T-Mo can even get to the phone unless they jtag it or something, which they will most likely not do as it will cause discomfort and timeloss to the customers (ME)
aanonymoushuman said:
As said before it's a brick, no screen, no vibration nothing. And I don't think T-Mo can even get to the phone unless they jtag it or something, which they will most likely not do as it will cause discomfort and timeloss to the customers (ME)
Click to expand...
Click to collapse
Well I doubt they can do that at the store (I don't have any confidence in the salespeople's tech ability there lol), so if you are under warranty just tell them that when you unplugged it this morning it was like that :laugh:
If it doesn't vibrate when plugged in and no battery installed then it sounds like a hard brick.
I think they do the manufacturer warranty as an exchange on the spot, so even if they do figure it out eventually you should be good.
But it would suck if they can get it into download mode at the store... better try numerous usb ports (even switch computers to be sure!) and cables to be sure Also wouldn't hurt to leave the battery out overnight and try again. If they get it in download mode... well two things. One they won't ever honor any warranty on the phone anymore (and they will give the phone back to you), but two... if they can get it in download mode have them leave it like that and rush back home - and then you're back in business
Kind of a win-win...
anactoraaron said:
Well I doubt they can do that at the store (I don't have any confidence in the salespeople's tech ability there lol), so if you are under warranty just tell them that when you unplugged it this morning it was like that :laugh:
If it doesn't vibrate when plugged in and no battery installed then it sounds like a hard brick.
I think they do the manufacturer warranty as an exchange on the spot, so even if they do figure it out eventually you should be good.
But it would suck if they can get it into download mode at the store... better try numerous usb ports (even switch computers to be sure!) and cables to be sure Also wouldn't hurt to leave the battery out overnight and try again. If they get it in download mode... well two things. One they won't ever honor any warranty on the phone anymore (and they will give the phone back to you), but two... if they can get it in download mode have them leave it like that and rush back home - and then you're back in business
Kind of a win-win...
Click to expand...
Click to collapse
I got a replacement going from T-Mobile, they just sent out the new phone today, but I'm confused do I send them my broken one right now? or wait till the new one comes?
They should have explained everything on the phone, they will send you a box to return it in . And if they find out that it has been rooted and modded , you could be charged the full price for the phone. Every time I sent the phone back I've always read it back to stock if yours was bricked hopefully they won't notice
Sent from my SAMSUNG-SGH-T769 using xda app-developers app

Help! Any Suggestions would do. :(

Can someone help me. My phone is on Valhalla final, one morning when it got battery empty and i was supposed to charge it, it just got stuck on the boot screen and wont progress anymore. can i install this rom to my phone? BTW i have a USB jig, i think thats the only way i could restore my phone through odin or heimdall. Thanks in advance!
I am not sure what you are asking since you are aware of Odin and Heimdall. Are you asking if you can still reinstall the Valhalla rom back?
You don't need the USB jig. You can access Odin or Heimdall by putting the phone in download mode. Follow the instructions in the guide.
Sent from my SGH-T959V using xda premium
peterpandesal06 said:
Can someone help me. My phone is on Valhalla final, one morning when it got battery empty and i was supposed to charge it, it just got stuck on the boot screen and wont progress anymore. can i install this rom to my phone? BTW i have a USB jig, i think thats the only way i could restore my phone through odin or heimdall. Thanks in advance!
Click to expand...
Click to collapse
Reboot recovery. Wipe cache and dalvik. Fix permissions. Reboot. If that doesn't do it you'll have to factory reset.
If all else fails and you want to try one last thing before restoring your phone and losing your data then flash a stock kernel like antonx stock with a twist it should boot your phone back up
Sent from my Galaxy Nexus using xda premium
hechoen said:
Reboot recovery. Wipe cache and dalvik. Fix permissions. Reboot. If that doesn't do it you'll have to factory reset.
Click to expand...
Click to collapse
thats also my another problem, i cannot access recovery mode neither.
Pull battery with USB unplugged so phone turns off completely. Hold down both volume buttons. Put battery back in. Press the power button for a second. Let go of the power button, but keep holding the volume buttons. You should now be in recovery mode.

Stuck in Recovery Mode

Alright, so I was using my phone just like normal. Phone dies after long work day. I plug in and allow it to get to approx 50%. When I attempt to turn it back on it goes straight into recovery mode. I havent ever rooted it, or done anything but install stock updates. I have tried to wipe cache, as well as factory reset. Everything takes it right back to recovery mode. If I power off and plug into either charger or computer it boots right back into recovery mode. Any help is greatly appreciated. Unfortunately, the only cpu access I have is a mac at this time. thanks in advance.
hawkpal1519 said:
Alright, so I was using my phone just like normal. Phone dies after long work day. I plug in and allow it to get to approx 50%. When I attempt to turn it back on it goes straight into recovery mode. I havent ever rooted it, or done anything but install stock updates. I have tried to wipe cache, as well as factory reset. Everything takes it right back to recovery mode. If I power off and plug into either charger or computer it boots right back into recovery mode. Any help is greatly appreciated. Unfortunately, the only cpu access I have is a mac at this time. thanks in advance.
Click to expand...
Click to collapse
Have you tried select reboot system now (First option) don't switch phone off and then reboot this will only take you back to recovery.
tallman43 said:
Have you tried select reboot system now (First option) don't switch phone off and then reboot this will only take you back to recovery.
Click to expand...
Click to collapse
Yes indeed. It simply reboots into recovery mode.
hawkpal1519 said:
Yes indeed. It simply reboots into recovery mode.
Click to expand...
Click to collapse
hi - same issue here...
EDIT : Sorry didn't read that yours wasn't rooted. Mine is and only starts to TWRP for some reason.

Categories

Resources