I was messing around with lucky patcher and edited the play store permissions for an app. My phone slowed down a bunch so I decided to turn it off. I then tried to turn it on again and everything worked fine. The Samsung galaxy logo did its animation properly, the T-Mobile thing came on, and everything looked to be fine. Unfortunately, everything was not fine. After the tmobile logo, the screen went black and reset. Now it stays on an endless loop until you take out the battery.
As you might've guessed, the phone is rooted. This hasn't happened to me before and I am unfamiliar with this but have a vague idea of what to do. I don't want to try anything however because I might brick my phone and that's no fun for anyone. If you know what to do, please help. Thanks!
PS: I've tried booting up from the recovery mode and cleared the cache and everything. Using Samsung Galaxy Note 4 SM-N910T
Ok so you dont have a custom recovery?...if ur going to root , go the extra mile and install a recovery for this reason...your in boot loop and best advice is to re-flash your operating system with odin.....you will lose everything that you had on the internal memory of your phone...but at least you will have your phone back
Related
Just done the lag fix for my Galaxy S and it all seemed to go through fine. Tried running Quandrant benchmark to test it but it crashed. I turned the phone off and on, got the Galaxy S i9000 screen then is just goes blank, literally nothing, not even the menu or back lights. Had to then take the battery out to reboot but got the same blank screen.
I can boot into recovery but rebooting from that doesn't work either, does anyone know how to fix this? don't want to try anything for fear of making it worse
Thread moved in Galaxy S I9000 General.
Tobert said:
Just done the lag fix for my Galaxy S and it all seemed to go through fine. Tried running Quandrant benchmark to test it but it crashed. I turned the phone off and on, got the Galaxy S i9000 screen then is just goes blank, literally nothing, not even the menu or back lights. Had to then take the battery out to reboot but got the same blank screen.
I can boot into recovery but rebooting from that doesn't work either, does anyone know how to fix this? don't want to try anything for fear of making it worse
Click to expand...
Click to collapse
Try getting into the Recovery Mode with the 3 button combo
instruction on wiki http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S/GT-I9000
What lag fix are you using and what firmware are you on?
wont boot..
Hi, strangely but after the 2.2 upgrade on my SGS (it was JF5 and I made the trick with the registry to JPC and upgrade via KIES) it happened to me as well.. just a beautiful "S" blinking on the screen and nothing happens. On the time of upgrade in the instructions it was written that with the 3combo trick to make factory reset.. then everything worked just fine until yesterday...
Without installing any new apps, just browsing and trying to make my AllShare working.. I decided to gave up and without reason I have decided to restart my phone just to free RAM and etc.. And by no reason at all I got the same ****ty "S" screen and no boot.. tried first to wipe the cache.. didn't help.. and just after again factory reset it worked out and the phone is okay...
So probably for you the solution is really only factory reset, however this is very strange behavior
When I first applied the lagfix from the market in apk type it required an auto reboot to see if things wokred ok (as prompted on the screen).
Anyway, my phone stuck to a black screen and I was in a very inconvenient situation not to be able to use a PC (yeah, now I know I shouldn't mess with stuff like that while I'm on-the-go).
Long story short, after a couple of manual reboots (by taking out the battery for some seconds) it came back to life and no problems ever since. So before flashing (which can be rather incovenient if you have no backups etc) try the above mentioned method.
Original JF3 firmware (yeah need to change that).
I'm usually fairly good at troubleshooting my own stuff but this really has me stuck in the same place for a few hours now.
So basically Flipboard has been nagging me(well play store is, not the app itself but anyway) so I said to myself why don't I uninstall it since I've never used it and don't plan to, and besides I hate to have pointless apps installed. So I open TitaniumBackup and I see it is installed as a system app, I thought what's the worst that can happen? so I do uninstall it and a minute later my phone shuts off. I try to turn it on and it doesn't go past the Samsung Galaxy Note 4 flash screen, it either reboots or stays like that.
I try to go into recovery to restore a backup and I can't, it is stuck at Recovery Booting and again it either stays like that or reboots and does it again and again and again.
Now, I haven't made any changes or installs on my phone for weeks now, so this is either because I unistalled Flipboard(I know I shouldn't have risked it since it was a system app but I really could not see it going this way) or the hardware is on it's way out(don't see what else could it be).
I figured I should flash a stock rom with odin, I can get into download mode, and reinstall everything from scratch.
I took a stock image from xda and flashed it and it does exactly the same thing.
Right now I'm downloading another stock image from sammobile for my country/provider to see if this will change anything.
What else can I try? I'm completely stuck and I really don't want to send the phone back like this, I doubt amazon is gonna be happy about it.
Specs:
N910F
Emotion Revolution 12.1 Rom
POK1 BL&CP
TWRP 2.8.7.0
Really sorry for the double-post. I'm quite desperate and need my phone for work.
Since last post I've tried flashing N910FXXU1COH4_N910FH3G1COH3_H3G.zip through Odin from SamMobile and it did the same thing with rebooting constantly.
Then I've installed Kies and went to Tools -> Firmware Upgrade and Initialisation and gave it the model and S/N and it downloaded something and everything went all right, the phone reboots and I'm back in the same circle, it just shows me the splash screen(in some video's I've seen that after this procedure they get the splash screen and then the android bot with a progress bar, I don't get that, I only get the splash screen and reboot) and reboots.
I thought this was a last resort thing? Is the phone completely dead or is there something I can try?
Again sorry for the double-post.
Update: still no progress so I've contacted Amazon and they said to send it back so hopefully this works out in the end, no matter how annoying the waiting time will be, if you do have any suggestions on what I should try please let me know as I haven't posted the phone yet.
Hi,
I'm new to XDA forums, and this is the first time that have ever tried rooting my phone. I got it in my head that I wanted to root my Samsung Galaxy S5 SW-G900P so that I could add a hot spot mod. I followed a few tutorials which helped me accomplish root. I then added TWRP and that went fine as well. Then I added a WiFi Tethering Mod (unlockHotspot-1.4-NE5-DEODEX.zip) via TWRP. I was asked to wipe Dalvik cache which is where I think the problem started. I think I did something and stopped the delete process. I can't recall. I turned on my phone with anticipation of being able to use Hotspot. The phone started to boot as normal; the Samsung logo with lines moving around it showed; the yellow 4g 3d animated graphics showed; then the main 4g graphic showed and stayed on my screen which is where it stayed and nothing after that. Just the 4g logo. So, I pulled the battery and started my phone in recovery mode which took me directly into the TWRP interface. I figured that I needed to reload the 6gig backup file that I created (through TWRP) in order to bring my phone back to life. I believe that I was given options to install the recovery file which (I don't remember them all) already had a few check marks added to the options. However, there were other options such as the System and Recovery boxes that were not checked, so I checked those boxes as well. I reinstalled from the recovery backup file and everything seemed to work fine until TWRP rebooted the phone and now I am stuck going through the recovery booting process again. Every time I turn on the phone, I get to the teamwin screen which blinks and blinks. Did I brick or soft-brick my phone? I'm newb to this and need a little help to get my phone working again. Also, am I in the right part of the XDA forum to ask questions? Help me Obi-Wan Kenobi, you're my only hope.
@Uclid
Soft brick.
Go to sammobile, find your stock firmware, uzip it, flash with Odin in download mode and your phone will wake up from her sleep
Sent from my XT1528 using XDA Labs
Thank you, thank you! I really appreciate the reply. I downloaded the firmware this morning and just loaded it to my phone. All good now. Now, to get that hotspot mod to work.
Good to see you got your phone back up and running......but if you flashed the firmware with odin, you will have lost root and overwritten TWRP.......
You'll need both back before you can flash that zip......
http://i.imgur.com/rVnFwJM.jpg
I have a SMG870A that will not stop rebooting no matter what I do. The phone was on PK7 and has ran flawlessly for the past 3 months I've had it. Phone one day reboot and never booted up again, just bootlooped. After wiping cache/wiping data, I've had no luck. I tried reflashing the pk7 stock image from sd card, the image flashes, restarts like normal but reboots half way through the splash screen. So then I tried to Odin the phone back to OF3, no luck either. I get a pass on Odin but when then splash screen comes up, it reboots. I have a brand new battery in it, and I am not sure what else could be causing this. I have very good knowledge on flashing, as I've been doing it since the S3's came out. But this device actually has me stumped. Any help would be much appreciated!
Thanks
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?