HI all,
Had the Note 4 for a month or two now, been successfully rooted for a couple of weeks too. Rebooted the phone today though, and it's just gotten stuck with a message saying "installing system update". It doesn't seem to progress no matter how long I leave it aside from the screen flashing.
I've tried to boot into recovery, but for whatever reason it just doesn't work, it always goes back to the update screen. Getting a bit worried now, any help would be great.
Cheers.
drojman said:
HI all,
Had the Note 4 for a month or two now, been successfully rooted for a couple of weeks too. Rebooted the phone today though, and it's just gotten stuck with a message saying "installing system update". It doesn't seem to progress no matter how long I leave it aside from the screen flashing.
I've tried to boot into recovery, but for whatever reason it just doesn't work, it always goes back to the update screen. Getting a bit worried now, any help would be great.
Cheers.
Click to expand...
Click to collapse
Flash stock f/w via Odin it should boot just fine, you'll have to re-root though.
For some reason installing CWM fixed it. It wiped my data, but it's back at least.
Related
Okay so I finally got my shiny new Nexus 32GB a couple days ago. Rooted it last night no problem. This morning I flashed Trinity Alpha4. worked great but my OC/governer/etc settings wouldn't stick. So I tried to flash the latest build of Faux Kernel. After flashing it got stuck in a boot loop. So I got back into Recovery and flashed Trinity back on again. Now it won't boot at all. After the splash screen the device completely locks up at a blank black screen. Went back to Recovery, wiped cache/dalvik, reflashed Trinity. After going through the "Android has been upgraded, optimizing apps" thing, it got stuck on "starting apps". After a couple min. I forced it to reboot, and again just gets stuck at a blank screen. I apparently completely forgot to do a Nandroid backup which I realized when I tried to restore it back lol.
Anywho, any thoughts on getting the thing to boot? Bricking it 2 days after I got it home is not my idea of a good time.
thebullfrog said:
Okay so I finally got my shiny new Nexus 32GB a couple days ago. Rooted it last night no problem. This morning I flashed Trinity Alpha4. worked great but my OC/governer/etc settings wouldn't stick. So I tried to flash the latest build of Faux Kernel. After flashing it got stuck in a boot loop. So I got back into Recovery and flashed Trinity back on again. Now it won't boot at all. After the splash screen the device completely locks up at a blank black screen. Went back to Recovery, wiped cache/dalvik, reflashed Trinity. After going through the "Android has been upgraded, optimizing apps" thing, it got stuck on "starting apps". After a couple min. I forced it to reboot, and again just gets stuck at a blank screen. I apparently completely forgot to do a Nandroid backup which I realized when I tried to restore it back lol.
Anywho, any thoughts on getting the thing to boot? Bricking it 2 days after I got it home is not my idea of a good time.
Click to expand...
Click to collapse
You might try and flash the stock kernel which should not allow any under/over clocking or under/over volting. Otherwise flash back to stock using the manual way here http://forum.xda-developers.com/showthread.php?t=1907796 or download the Nexus 7 toolkit and use it to do the same.
Try WugFresh's Nexus Root Toolkit. It has an option to go back to stock if you're soft-bricked.
Well I just did a factory restore/wipe (because Im SO looking forward to setting everything up again...) and it made zero difference. I'll try the stock kernel if someone could point me in the right direction to find a copy of it.
NVM found it. I'll give it a shot.
Ummmm okay then. I had my N7 turned off while looking for a solution to this fiasco. I picked it up so I could flash the stock kernel, and it had turned itself back on. Not only that, but it was fully booted up. Granted it's back to the initial setup after doing a factory restore, but there we go. It automagically fixed itself. Now to spend a couple hours putting everything back how it was. Yay.
Protip children: Always. Be. Nandroiding.
Hello all. I've had a Verizon note 3 since release. I've been running HyperDrive 6 on 4.3 since I got the phone. I've had no reason to update at all, not to mention when I first got it I didn't understand knox so now my knox counter is 0x1. Its been great and themed and untouched for at least 3 months. Today I noticed everytime I opened an app it was upside down, and flipping my phone didn't help. So, I rebooted it.
Ever since that reboot about 3 hours ago I have been unable to get it to reboot fully. It boots up, gets to the lock screen and freezes for about 10 seconds then pops an error saying System process not responding "wait or close". I've done both options with no luck. I've booted into safestrap, cleared cache, recovered to my most recent (April) recovery, booted into stock rom slot, EVERYTHING ends in system process freezing and rebooting.
Why is it doing this out of nowhere? How do I make it stop? What is even wrong? I need this phone for work and in the 3 hours without it have already gotten crap via email for being unresponsive to phone calls.
I have zero idea how to update to KK with my knox counter voided. I'd prefer not to anyway since 4.3 HD6.0 worked great and was themed to my liking.
But I need this phone working, so I'm taking ideas.
Thanks for your help.
Have you tried using Odin if not might wanna start with that use a computer download the stock firmware tar file use Odin to flash the phone back to stock. That's what I would do I don't know what's wrong with you phone but that might help undo what was done.
burkechrs1 said:
Hello all. I've had a Verizon note 3 since release. I've been running HyperDrive 6 on 4.3 since I got the phone. I've had no reason to update at all, not to mention when I first got it I didn't understand knox so now my knox counter is 0x1. Its been great and themed and untouched for at least 3 months. Today I noticed everytime I opened an app it was upside down, and flipping my phone didn't help. So, I rebooted it.
Ever since that reboot about 3 hours ago I have been unable to get it to reboot fully. It boots up, gets to the lock screen and freezes for about 10 seconds then pops an error saying System process not responding "wait or close". I've done both options with no luck. I've booted into safestrap, cleared cache, recovered to my most recent (April) recovery, booted into stock rom slot, EVERYTHING ends in system process freezing and rebooting.
Why is it doing this out of nowhere? How do I make it stop? What is even wrong? I need this phone for work and in the 3 hours without it have already gotten crap via email for being unresponsive to phone calls.
I have zero idea how to update to KK with my knox counter voided. I'd prefer not to anyway since 4.3 HD6.0 worked great and was themed to my liking.
But I need this phone working, so I'm taking ideas.
Thanks for your help.
Click to expand...
Click to collapse
Sorry i got no idea what you can do, maybe oding back? But this is not the correct place to put a question... I am kind of sure you know that and if you didn't then read the forum rules.
Awesome ROM bro, I'll give it a try!!
tl;dr phone is in some kind of bootloop, tried flashing stock firmware (successful but can't get past start splash screen), plz halp me
So I was just simply browsing on my phone on reddit is fun app, some Google Chrome sites, and 9gag. So then I saved a gif on 9gag and the phone just gives up on me. It went straight to shut down without any warning whatsoever and proceeded to restart. Thinking that it was just an unusual one time thing, the phone kept rebooting and I started really getting worried. I kept getting the Samsung Galaxy S4 splash screen and after that a black screen and then it vibrated twice and I saw the splash screen again. Didn't even get to see the menu for SafeStrap. After several unsuccessful attempts, I finally accessed SafeStrap after restarting the phone from download mode pressing the volume down button. To make as much precious time as I had, I made a backup (although I checked enable compression which I shouldn't have but I didn't have a lot of space on my SD card) and made an advanced wipe cleaning everything except the SD card. I then proceeded to flash a different custom ROM (GoldenEye if you were wondering) and hoped that it was just a custom ROM error that kept giving bootloops. No such luck. The different ROM didn't even help. So I went back to SafeStrap and made another advanced wipe. At this point, I decided to flash stock firmware via Odin from this link (http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642) with NB1 base. I remember having flashed the non-rootable version successfully and restarted the phone after that. Got past the Samsung Galaxy S4 splash screen and went all the way to ATT splash screen but then it crashed right there. After that, I couldn't figure out the problem and I couldn't flash any more stock firmware (at least from that link) via Odin because I kept getting a fail notice. I asked this question on reddit and the responses kept saying that I may have a defective power button but it doesn't stay shut down and instead bootloops. Should I try to find a new GS4, get another phone or try sammobile firmwares next to see if there's any luck? I really need to save this phone as it is super dear to me. I'm at the point where I can cry right now :crying:
If you guys need any pictures or videos, I will be more willing to do so
RawSynergy said:
tl;dr phone is in some kind of bootloop, tried flashing stock firmware (successful but can't get past start splash screen), plz halp me
So I was just simply browsing on my phone on reddit is fun app, some Google Chrome sites, and 9gag. So then I saved a gif on 9gag and the phone just gives up on me. It went straight to shut down without any warning whatsoever and proceeded to restart. Thinking that it was just an unusual one time thing, the phone kept rebooting and I started really getting worried. I kept getting the Samsung Galaxy S4 splash screen and after that a black screen and then it vibrated twice and I saw the splash screen again. Didn't even get to see the menu for SafeStrap. After several unsuccessful attempts, I finally accessed SafeStrap after restarting the phone from download mode pressing the volume down button. To make as much precious time as I had, I made a backup (although I checked enable compression which I shouldn't have but I didn't have a lot of space on my SD card) and made an advanced wipe cleaning everything except the SD card. I then proceeded to flash a different custom ROM (GoldenEye if you were wondering) and hoped that it was just a custom ROM error that kept giving bootloops. No such luck. The different ROM didn't even help. So I went back to SafeStrap and made another advanced wipe. At this point, I decided to flash stock firmware via Odin from this link (http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642) with NB1 base. I remember having flashed the non-rootable version successfully and restarted the phone after that. Got past the Samsung Galaxy S4 splash screen and went all the way to ATT splash screen but then it crashed right there. After that, I couldn't figure out the problem and I couldn't flash any more stock firmware (at least from that link) via Odin because I kept getting a fail notice. I asked this question on reddit and the responses kept saying that I may have a defective power button but it doesn't stay shut down and instead bootloops. Should I try to find a new GS4, get another phone or try sammobile firmwares next to see if there's any luck? I really need to save this phone as it is super dear to me. I'm at the point where I can cry right now :crying:
If you guys need any pictures or videos, I will be more willing to do so
Click to expand...
Click to collapse
I'd say try redownloading the firmware and make sure your cable is good, try a back USB port, etc. I'd guess the firmware files didn't download properly and so it didn't flash properly. Before you do anything though, try going into stock recovery and wiping everything you can from there.
DeadlySin9 said:
I'd say try redownloading the firmware and make sure your cable is good, try a back USB port, etc. I'd guess the firmware files didn't download properly and so it didn't flash properly. Before you do anything though, try going into stock recovery and wiping everything you can from there.
Click to expand...
Click to collapse
Thank you for the reply. As for the firmware, where should I acquire them? The link I posted has only one firmware (NB1) and I cannot access stock recovery AT ALL. When I do, I can see the blue text in the corner "Recovery booting..." and then the phone restarts again. This is really frustrating
RawSynergy said:
Thank you for the reply. As for the firmware, where should I acquire them? The link I posted has only one firmware (NB1) and I cannot access stock recovery AT ALL. When I do, I can see the blue text in the corner "Recovery booting..." and then the phone restarts again. This is really frustrating
Click to expand...
Click to collapse
NB1 is the only one you can get, just try downloading either one again.
DeadlySin9 said:
NB1 is the only one you can get, just try downloading either one again.
Click to expand...
Click to collapse
I did twice today and I keep getting the same message in Odin, like setting up a connection and then it fails
RawSynergy said:
I did twice today and I keep getting the same message in Odin, like setting up a connection and then it fails
Click to expand...
Click to collapse
When you plug in the phone in Download Mode, does the blue box in Odin light up? If not, reinstall samsung drivers
Sent from my SM-N910G using Tapatalk
I hope I'm posting this at the right place. I have to start off by saying that I'm almost a complete noob regarding rooting and things that have to do with it. I rooted my phone about 6 months ago I think and the reason why I did that was only because I wanted to be able to freeze down some apps with titanumbackup. Since it's been such a long time ago I've forgotten almost all those steps I did when I rooted my phone.
Anyways back to the issue. So today I got a notification from SuperSU saying that it needed to update. I didn't think too much about it so I just followed the notification and updated it. When I started SuperSU I got 2 choices. Either updating normal or by TWRP/CWM. The dumb me just pressed TWRP/CWM for no reason and the phone rebooted into recovery mode. A lot of text started scrolling down at the bottom left corner and when it finally stopped it said something along the line with update failed. I pressed "reboot the system now" from the list and after that my phone rebooted. The samsung logo popped out as usual but after that the screen was completely black. Then I got a lot of popups telling me that this and that app stopped working. Contacts stopped working, whatsupp stopped working, messenger stopped working etc. Like all the apps stopped working.
So I've been trying to google a solution to this but it doesn't seem like someone has had the exact same problem. I've been trying to research things about rooting and such again to see if it can help me someway but I don't think I can't fix this problem by doing just that, so therefore I'm writing this to see if you guys can help me since you have waaay more experience than me when it comes to rooting. I've tried flashing CF-Auto-Root-jflte-jfltexx-gti9505 again using odin but the problem stays. I've tried updating to the latest stable SuperSU by downloading the zip file and putting it on the sd card and then using recovery mode but it didn't work either (I got an error E: signature verification failed). So after reading about the error I tried flashing a CWM but everytime I do that with odin I either get a FAIL or I keep getting the messages (Added, removed, added, removed). I download kies to get the drivers but it didn't help. and now when I try to boot into recovery mode my phone just keep rebooting.
I really don't know what to do now guys so I hope you guys can help me out :crying:
My phone:
Samsung galaxy s4 GT-I9505
Rooted with CF-Auto-Root-jflte-jfltexx-gti9505.tar
durantala said:
I hope I'm posting this at the right place. I have to start off by saying that I'm almost a complete noob regarding rooting and things that have to do with it. I rooted my phone about 6 months ago I think and the reason why I did that was only because I wanted to be able to freeze down some apps with titanumbackup. Since it's been such a long time ago I've forgotten almost all those steps I did when I rooted my phone.
Anyways back to the issue. So today I got a notification from SuperSU saying that it needed to update. I didn't think too much about it so I just followed the notification and updated it. When I started SuperSU I got 2 choices. Either updating normal or by TWRP/CWM. The dumb me just pressed TWRP/CWM for no reason and the phone rebooted into recovery mode. A lot of text started scrolling down at the bottom left corner and when it finally stopped it said something along the line with update failed. I pressed "reboot the system now" from the list and after that my phone rebooted. The samsung logo popped out as usual but after that the screen was completely black. Then I got a lot of popups telling me that this and that app stopped working. Contacts stopped working, whatsupp stopped working, messenger stopped working etc. Like all the apps stopped working.
So I've been trying to google a solution to this but it doesn't seem like someone has had the exact same problem. I've been trying to research things about rooting and such again to see if it can help me someway but I don't think I can't fix this problem by doing just that, so therefore I'm writing this to see if you guys can help me since you have waaay more experience than me when it comes to rooting. I've tried flashing CF-Auto-Root-jflte-jfltexx-gti9505 again using odin but the problem stays. I've tried updating to the latest stable SuperSU by downloading the zip file and putting it on the sd card and then using recovery mode but it didn't work either (I got an error E: signature verification failed). So after reading about the error I tried flashing a CWM but everytime I do that with odin I either get a FAIL or I keep getting the messages (Added, removed, added, removed). I download kies to get the drivers but it didn't help. and now when I try to boot into recovery mode my phone just keep rebooting.
I really don't know what to do now guys so I hope you guys can help me out :crying:
My phone:
Samsung galaxy s4 GT-I9505
Rooted with CF-Auto-Root-jflte-jfltexx-gti9505.tar
Click to expand...
Click to collapse
Did you try to just uninstall supersu and redownload it from the play store?
Lennyz1988 said:
Did you try to just uninstall supersu and redownload it from the play store?
Click to expand...
Click to collapse
When I boot up the phone the screen is totally black. The only thing that shows are those popups (a lot of them) that tells me that this and that app stopped working. :/
durantala said:
When I boot up the phone the screen is totally black. The only thing that shows are those popups (a lot of them) that tells me that this and that app stopped working. :/
Click to expand...
Click to collapse
Right now I don't see any other choice than flashing a stock rom.
Or you could try reflashing the recovery.
Make sure you are using the back USB ports and the original cable. Odin is quite sensitive with this.
After attempting to upgrade my wife's Verizon Note 4 from 5.1.1 with root to 6.0.1 with root, it is now in a boot loop. I had done my exact phone earlier this month with no issues, so I was confident I could do hers. Now she's pissed because she has no phone and I'm in the dog house. Fortunately, I made a complete backup of her phone using TWRP before attempting this upgrade.
So, can I just restore her backup or are there other steps I need to perform before trying to revert it, since I did flash the N910VVRU2CQL1_PartialFirmware_DevEd.tar and the N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar during the process, and also the JasmineROM_v7.0_N910VVRU2CPF3, though it was actually restored via TWRP.
The details are below if it helps determine what might have happened, but if I can just restore her backup, she'll be happy, which means I can finally get out of the dog house.
I tried upgrading my wife's phone since she has the same exact phone running 5.1.1 with root. Everything appeared to be going fine, but after performing the last step (flashing the N910VVRU2CQL1_PartialFirmware_DevEd.tar.md5.7z via Odin) and rebooting the phone, it now goes into a boot loop. It will load the Samsung logo for about 20-30 seconds, then reboot every time. I can still access TWRP from recovery and I have cleared Dalvik and Cache, but it still does the same thing. I also reflashed JasmineROM_v7.0_N910VVRU2CPF3, cleared Dalvik and Cache again, but still the same boot loop. It does still show the word Custom under the Samsung logo at boot, so I assume that is good news. Doesn't that mean the bootloader is still unlocked or something?
If it helps, the part of the process that had me concerned was after unlocking the bootloader. I powered off the phone, and then tried to load the recovery menu so I could factory reset the phone and clear the cache, but the recovery menu never appeared. It did show the Android fix-it guy for the recovery for about 10 seconds then a short progress bar under it for about 5 seconds, then it went straight to the Samsung logo. It never did give me the actual recovery menu, just the Android fix-it guy animation, which I thought was odd because I've always had the recovery menu pop up after that.
Any suggestions?
Mike
Modify_inc said:
After attempting to upgrade my wife's Verizon Note 4 from 5.1.1 with root to 6.0.1 with root, it is now in a boot loop. I had done my exact phone earlier this month with no issues, so I was confident I could do hers. Now she's pissed because she has no phone and I'm in the dog house. Fortunately, I made a complete backup of her phone using TWRP before attempting this upgrade.
So, can I just restore her backup or are there other steps I need to perform before trying to revert it, since I did flash the N910VVRU2CQL1_PartialFirmware_DevEd.tar and the N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar during the process, and also the JasmineROM_v7.0_N910VVRU2CPF3, though it was actually restored via TWRP.
Click to expand...
Click to collapse
Not that I'm impatient, but I thought I had a backup phone I could put my sim card in until I resolve this issue. Only problem is I forgot it was an at&t phone. Duh!
From what I've read the Note 4 n910v is a robust and almost unbrickable phone. So I said what the heck, I'm going to restore my backup. I mean that is why before all instructions it is advised to make a full backup, so you can revert back, right!. I don't recall the instructions claiming there is a special process or order of steps to take before you can restore your backup.
So, I wiped everything and restored my full backup via twrp. Upon reboot, I finally had the "Kernel is not seandroid enforcing" and "Set Warranty Bit: Kernel" that I was accustomed to. I thought this must be a good sign, but then it went to a black screen, which I realized after about 20 mins, that it had powered itself off. So I tried it again and same thing, it doesn't reboot or even vibrate or flash the LED light. I can press the power button and it will come back on, so I know it turns itself off. So what would cause it to power off after displaying the first boot logo titled Samsung Galaxy Note 4 Custom w/ unlocked icon powered by Android?
The next thing I will try, unless hopefully someone advises me otherwise, is reflash the N910VVRU2BPA1_N910VVZW2BPA1_VZW [5.1.1 Stock FW]. I assume that should be safe to do, and I'll just follow the directions for the "Easy Guide for How to Root Verizon Galaxy Note 4 (updated links and instructions)" though technically isn't the bootloader already unlocked since I have the red "Kernel is not seandroid enforcing" and the yellow, "Set Warranty Bit: Kernel" and the custom unlocked lock on my boot screen?
This is where I'm confused, I feel like this is not the issue, that it must be something else, but I'm at a lost.
Finally got my phone working! But no WiFi
I've finally got my phone working again! I just can't get the WiFi to work. I have tried three different modems but still the WiFi will not enable: N910VVRU2BPA1_Modem, N910VVRU2CPD1_Modem, and N910VVRU2CPF3_Modem. I even tried restoring the modem I had backed up, but still no go. I noticed that even when I restored my modem from backup, it still said my baseband was N910VVRU2CQL1, but when I flashed the other modems, they each updated the baseband correctly, displaying the correct baseband version, though still no WiFi.
Any suggestions?