Hi everyone!
This is my first post on here. I appreciate the value of all the info here and have been browsing unregistered for awhile.
Yesterday while using my Note 4 N910V, the phone cut off with 10% battery. Not unusual. I have 3 batteries for the device and it happens when putting a load though it while low. However this time it appeared to kill the phone. Now I'm trying to figure out if it fried something on the logic board when it cut off suddenly this time or if it corrupted my ROM.
I work in IT so I'm not totally without some kind of knowledge. So I installed ODIN and found a stock Verizon ROM and installed it. ODIN said it was successful and still, the phone is stuck in a bootloop. I have never rooted or loaded a custom ROM on this phone. It is completely stock. Am I missing something here? Do I have to mess with the bootloader or something? After ODIN installed the stock ROM I performed a whip data/factory reset. Still the same bootloop. It will get to the Verizon splash screen and reboot. I am able to get into recovery mode as well. The phone doesn't turn off or anything while in the Recovery menu. This is what lends me to believe it may be something corrupt with the ROM and the hardware might be ok.
Any insight would be greatly appreciated. Thank you very much!
Robert
Related
i bought a phone off ebay in december. the phone was working well and then i decided to start installing different Roms on my phone. the phone was not s-off when i was installing these roms. about two weeks ago my phone just started to restart. it does not stay on for more than a minute before it restarts and i have no idea why it is happening. i would really appreciate any help in this matter because it is really frustrating. i think it is a software problem because the phone does not restart when it is in recovery mode or if it is in bootloader mode. if there is anything...anything at all you can do to help me it would be greatly appreciated.
hvagrantz said:
i bought a phone off ebay in december. the phone was working well and then i decided to start installing different Roms on my phone. the phone was not s-off when i was installing these roms. about two weeks ago my phone just started to restart. it does not stay on for more than a minute before it restarts and i have no idea why it is happening. i would really appreciate any help in this matter because it is really frustrating. i think it is a software problem because the phone does not restart when it is in recovery mode or if it is in bootloader mode. if there is anything...anything at all you can do to help me it would be greatly appreciated.
Click to expand...
Click to collapse
It would nice if you put a title to your thread instead of just [Q].
Anyway, if you suspect its a software problem, why not just flash back to stock and see if it persists? If the problem is still there, then it's most likely a hardware issue. I would replace the battery first.
Sorry about that .. it was the first time i posted something and wasn't really sure what to do. and i replaced the battery and the problem is still there .. i flashed and it still restarted. the weird thing is that if i'm doing something it doesn't restart. like if i'm using the phone as a hotspot it doesn't restart. but as soon as i stop it restarts. or if i'm using the camera it doesn't restart.
Did you wipe/format everything before flashing/flashing back to stock? Are you on CWM or EXT4? Some more details would be helpful.
yes i did that. i used superwipe. i am also 4EX and i S-off the device also. i tried installing the stock rom but it didnt work. it is confusing because once i am in recovery the phone stays on. but as soon as i turn it on it just keeps restarting. the phone boots up and then restarts.
i am hoping that i did not brick my phone as i just spent $600 to go get the bloody thing. i flashed darkcore kernel onto it and it was fine. the phone was fine until i went to go change the battery icon (the phone is a samsung i9000 galaxy s) it boots into recovery but when i go to do a normal boot it littraly freezes at the boot screen and thats it i left it on the table for HALF AN HOUR and when i came back it was still on the boot screen . the boot screen says galaxy s gt-i9000 (white writing) powered by darkcore and darkysrom (green writing) please help me i hope i have no bricked my phone as i am a noob to android as i have only had my phone a few days. do i need to replace the modem on the phone ? or the kernel? please if someone knows to get in contact with me. i have odin and superoneclick installed on my pc. i have wiped everything off my phone wipe data/factory reset but that doesnt do anything diffrent. it simply stays on the boot screen. i have not flashed a custom rom onto my galaxy it only has a custom kernel.
FaZeHaViiK,
I can't help you but I recommend you change your topic to fit your problem. Maybe then people would check your post out.
how do i do that ??
FaZeHaViiK said:
how do i do that ??
Click to expand...
Click to collapse
OK it is simple really. What did you do when it started causing issues? You tried to change the icon, so undo your changes. You didn't say how you tried to change it at all so not sure what steps you have to take. Also please do the proper research before you do something that can't be fixed
Sent from my Inspire 4G using Tapatalk 2
Android phones are REALLY REALLY hard to brick. what you need to do, is get yourself a factory default rom, and start over where you messed up. Messing with these phones is all trial and error. I have bricked my samsung fascinate over 30 times im sure, hell almost 10 times last night as im porting miui v4 to my phone. Dont freak out learn what ODIN is, and get it fixed.
zeruth said:
Android phones are REALLY REALLY hard to brick. what you need to do, is get yourself a factory default rom, and start over where you messed up. Messing with these phones is all trial and error. I have bricked my samsung fascinate over 30 times im sure, hell almost 10 times last night as im porting miui v4 to my phone. Dont freak out learn what ODIN is, and get it fixed.
Click to expand...
Click to collapse
Not all android phones are hard to brick. Take a look at the SGS II and the Euro Note that were perm bricked from a wiping data. No JTAG recovery would fix it. Also there are many ways to brick a device and as you recovered it. You didnt brick it. Bricking it makes it non recoverable except by Jtag. Too many people use this word wrong.
On a side note... Why would you spend 600 dollars on that phone?
Samsung problems
i really have no idea why i spent so much on it lol and i used the android app "DarkyODA" i think it was i flashed CwM DarkCore v3.0.2.8x kernel onto it via DarkyODA and it was fine after that but until i went to change the battery icon on the DarkyODA app then i went to reboot my phone and now its stuck at the boot screen i left it on overnight on the boot screen to see if it would reboot got up in the morning and it still was on the boot screen, i can get into the recovery menu but thats about it, i have been trying to find a stock kernel and rom for my phone but i simply cannot find one (build number xwjvp), i think its the battery icon thats making the phone freeze at the boot screen ive done a full system wipe but that didnt fix it, and i cannot remove the icon as i installed it on the darky app (which i cannot access as i cannot get past the boot screen), do i need to flash a stock rom and kernel or just a stock rom ? do you reckon that would fix my phone ? as i do not want to go and spend another $450 to get samsung to fix it (lol) i have odin 1.85 and i went to go flash voodoo kernel xwjvp v1.3 through odin but it got stuck half way through............
I recently tried to install a new ROM on my phone.
I installed it using ROM Manager, which I realize now is probably what caused it mess up. I hadn't checked these forums in a while and didn't realize it was causing issues, so that was my stupidity but what's done is done.
Anyways, after installing the ROM, it just sat on the boot animation endlessly.
I attempted to get into Recovery mode, but when I tried using Volume Up+Down+Power, it always went to download mode, whether it was plugged in or not.
I tried flashing it back to stock image and kernel using this guide but even after that, it still got stuck on the boot animation.
Any help is greatly appreciated.
In desperate cases I found myself in, I have had great success with the the jig method without the jig (for lack of a better term). Look around on the Captivate forum there is a description there. It works like the normal procedure for getting the phone in download mode but then you also (at the same time) insert the battery. I think that simulates what the jig does.
It is awkward to coordinate all the different movements but it works on the Captivate, and I believe I have been successful on the I-777 as well with the same method.
Aaronneyer said:
I recently tried to install a new ROM on my phone.
I installed it using ROM Manager, which I realize now is probably what caused it mess up. I hadn't checked these forums in a while and didn't realize it was causing issues, so that was my stupidity but what's done is done.
Anyways, after installing the ROM, it just sat on the boot animation endlessly.
I attempted to get into Recovery mode, but when I tried using Volume Up+Down+Power, it always went to download mode, whether it was plugged in or not.
I tried flashing it back to stock image and kernel using this guide but even after that, it still got stuck on the boot animation.
Any help is greatly appreciated.
Click to expand...
Click to collapse
Thanks, I actually did get it to go into recovery this morning. I let the battery drain over night and afterwards, it got into recovery. I'm still having some problems with a few other things but I think all the problems I have now are solvable, although if I get back into the same situation again, I'll be sure to take a look at that method.
try flashing stock pda with odin.
problem solved
So i'm helping a buddy out that was having an issue with several Note 2's that were purchased from a company that restricted their employees access to a lot of things on the phone. My friend handed a couple off to me. The first one was not passcode locked and it was a breeze (Basically just enabled USB Debugging). It is up and running. The other ones are passcode locked and when you try to go into wipe the data/factory reset from recovery it says "MDM does not allow factory reset". The Note 2 I'm having issues with in particular has a locked bootloader on KitKat 4.4.2 through Verizon.
I've spent almost literally every waking moment trying to find a way around this issue. I may have compounded it though. I discovered ODIN, flashed the stock firmware in the hopes that it would clear the phone. It did not (password was still in place). I then decided to flash the stock firmware with the .Pit file for an SCH-I605 and made sure re-partition was checked as well as erase nand. After the process completed successfully and the phone rebooted it will no longer boot beyond the Verizon screen. I still have access to recovery and download mode but in recovery its throwing out a bunch of command lines such as E:failed to mount /data etc. I've tried to reflash the stock firmware with and without the .pit file to no avail.
In the mean time I've tried to unlock the bootloader, attempted auto root, and install custom recoveries to see if I could some how get around the MDM issue. I've also attempted to install or flash from ADB and its still the same deal.
Anyway I'm tired, kind of exhausted, and not really sure what avenues I have left. That's where I'm hoping some of you guys come in. If you have any questions for me let me know and I'll try to shed some more light on it for you. Data DOES NOT matter to me so if you can think of anyway I can get this thing completely wiped out it so I can start from scratch it would be greatly appreciated, Thanks.
Is it just one phone with this problem or several? The mounting issues are becoming more common around here, and seem to be internal memory failure.
http://forum.xda-developers.com/note-2-verizon/help/stuck-boot-file-exists-t3286946
Droid_Nut said:
Is it just one phone with this problem or several? The mounting issues are becoming more common around here, and seem to be internal memory failure.
http://forum.xda-developers.com/note-2-verizon/help/stuck-boot-file-exists-t3286946
Click to expand...
Click to collapse
Well tonight I'll be getting my hands on a couple other test SCH-i605 phones that are in the same situation (Password locked and no ability to wipe from recovery) and I'll put them through the paces to see if I wind up with the same issue and get back with you on it.
The basic issue with this phone is just after trying that repartition with the pit file it doesn't want to boot beyond the verizon logo anymore and thats when it started throwing those errors in recovery. It could be a coincidence I guess.
I've been messing with Heimdall today to see if I could get a custom recovery flashed that way but the phone fails protocol initialization. The only thing I can get to flash to this phone is 4.4.2 and the i605 pit file through ODIN. Nothing else will budge.
I guess the question I really need answered, is there another way to wipe data/factory reset without the option in the stock Samsung recovery and no access beyond the lock screen?
What I have to work with is ODIN mode and whatever is in recovery that is not wipe data/factory reset.
So I did get my hands on a couple other phones with passcode locks that have the MDM lockout within the stock recovery that still fails to flash anything in Odin except the stock 4.4.2 firmware. So I can eliminate the idea its hardware. I have 4 phones here 3 of which have the same issue and the 4th I was lucky enough to not have a passcode. Quick fix to get MDM removed that way.
Again any ideas that are slightly more outside the box would be appreciated. Thanks.
Edit: If this helps the phone that is working that I manage to clean all of that stuff off of also throws the same error in ODIN with or without USB debugging so it leads me to believe there is something I'm actually missing... Time to go read more.
Well, sound like it is more than coincidence. Maybe you should contact Samsung and see if they can help?
Yeah I might do that. I'd just hope they have a one size fits all solution because I have about 600 to 1000 phones to tackle... Hahaha.
The conundrum here is that for the MDM company to release the lock on the phone I have to be able to get beyond the lock screen for the phone to process the request. To get beyond the lock screen I need the psswords that the previous company allowed their employees to put on the phones that for some odd reason they didn't have remove.
Anyway if I get this figured out i'll let you guys know how I got it. Thanks for the suggestion.
((deleted))
Hello guys, I have a serious predicament that needs to be solved.
I haven't did anything major to my phone in years so the past couple days have been a nightmare. Ever since I did a wipe of cache partition after trying to get rid of this "unfortunately, contacts stopped working." message, it's sent my phone into a spiraling disaster. (I have been using stock 5.0 rooted rom for at least a year so idk why the sudden issues)
I've literally tried every method imaginable. I even tried flashing with different versions of Odin and still the exact same problems.
I can get my phone into DL mode easily but Recovery mode only works if I have the phone plugged in at this point (Actually, it seems like the only time when my phone wants to work)
Every time I'm done flashing, it'll load all the way up to the T-Mobile screen then restart the loop all over again :/
Really need help seeing as I need to get this situation handled before work today, thanks!
Nevermind, after more research, I decided to order a new battery and the problem is solved.
Bootloop solved with replacement battery
gkenga said:
Nevermind, after more research, I decided to order a new battery and the problem is solved.
Click to expand...
Click to collapse
A replacement battery also solved my boot loop issue. Prior to replacement, it would boot to Galaxy S5 screen, and then reboot. Replaced battery and boots. Put the old battery back in, and it boot looped.