I was going a back up on my phone in twrp and noticed that the time was off. I read that if you reflash twrp(2.6.3.3) that it would fix the issue. I used freegee to do it the first time and it worked fine since I couldn't get any other program to flash twrp successfully. I received a snapchat while freegee was flashing so i checked it out(big mistake in hindsight). I then attempted to go back to freegee but it wasn't listed in recent apps. So I loaded up freegee again and it acted like it was the first time. I attempted to flash twrp again and it finished successfully but when I tried to restart my phone it does nothing. Was the other Freegee running and didn't finish correctly causing this?
If I hold the power button down it will just vibrate in ~15 second intervals
No LG logo, no back light.
No download mode.
No Recovery.
Tried disconnecting battery cable and plugging phone in to reach download mode.
I've tried a few things on other sites like trying to flash via linux but my phone won't show up. It wont' show up when plugged in to my laptop either
Is it a lost cause?Do I just take it back to the store and say the phone died and won't reboot?
Any help would be appreciated.
nostang3 said:
I was going a back up on my phone in twrp and noticed that the time was off. I read that if you reflash twrp(2.6.3.3) that it would fix the issue. I used freegee to do it the first time and it worked fine since I couldn't get any other program to flash twrp successfully. I received a snapchat while freegee was flashing so i checked it out(big mistake in hindsight). I then attempted to go back to freegee but it wasn't listed in recent apps. So I loaded up freegee again and it acted like it was the first time. I attempted to flash twrp again and it finished successfully but when I tried to restart my phone it does nothing. Was the other Freegee running and didn't finish correctly causing this?
If I hold the power button down it will just vibrate in ~15 second intervals
No LG logo, no back light.
No download mode.
No Recovery.
Tried disconnecting battery cable and plugging phone in to reach download mode.
I've tried a few things on other sites like trying to flash via linux but my phone won't show up. It wont' show up when plugged in to my laptop either
Is it a lost cause?Do I just take it back to the store and say the phone died and won't reboot?
Any help would be appreciated.
Click to expand...
Click to collapse
Just to be clear, when plugging the usb cable in you were holding volume up right?
If so, you could try this.
http://forum.xda-developers.com/showthread.php?t=2582142
I think a lot of people are having problems with freegee lately. Flashify is working great, however.
1heffer said:
Just to be clear, when plugging the usb cable in you were holding volume up right?
If so, you could try this.
http://forum.xda-developers.com/showthread.php?t=2582142
I think a lot of people are having problems with freegee lately. Flashify is working great, however.
Click to expand...
Click to collapse
Yeah, I've tried all possible combinations. Vol up with power, volume down with power, hold power for 15 seconds, hold power for 1 minute, hold power for 2 mins. I even took the case off, removed the battery connection and tried the Vol up plus plugging in usb cable.
I tried the linux thing in that thread before posting but it won't recognize my phone to even try it.
nostang3 said:
Yeah, I've tried all possible combinations. Vol up with power, volume down with power, hold power for 15 seconds, hold power for 1 minute, hold power for 2 mins. I even took the case off, removed the battery connection and tried the Vol up plus plugging in usb cable.
I tried the linux thing in that thread before posting but it won't recognize my phone to even try it.
Click to expand...
Click to collapse
Okay, I think this one then.
http://forum.xda-developers.com/showpost.php?p=51810022&postcount=38
It sounds like a similar situation.
1heffer said:
Okay, I think this one then.
http://forum.xda-developers.com/showpost.php?p=51810022&postcount=38
It sounds like a similar situation.
Click to expand...
Click to collapse
It's actually mostly the same process as before, since my phone isn't recognized in linux I can't transfer any files to it. I have been all over the internet and found a lot of threads but all of the require the phone to be recognized by the OS or boot into some mode.
Thanks for looking.
nostang3 said:
It's actually mostly the same process as before, since my phone isn't recognized in linux I can't transfer any files to it. I have been all over the internet and found a lot of threads but all of the require the phone to be recognized by the OS or boot into some mode.
Thanks for looking.
Click to expand...
Click to collapse
Yeah, I think thats what the first part of that post is referencing. If you read posts before that one, he couldn't get his device recognized either.
Hopefully someone else will chime in, this is actually a bit over my head at the moment.
1heffer said:
Yeah, I think thats what the first part of that post is referencing. If you read posts before that one, he couldn't get his device recognized either.
Click to expand...
Click to collapse
Yeah, I followed the steps at work with no dice. I'll try it again at home and see if changes anything.
1heffer said:
Yeah, I think thats what the first part of that post is referencing. If you read posts before that one, he couldn't get his device recognized either.
Hopefully someone else will chime in, this is actually a bit over my head at the moment.
Click to expand...
Click to collapse
Ok, he didn't have gdisk installed. Do you?
Did you get output after ls/dev/sd* ?
1heffer said:
Ok, he didn't have gdisk installed. Do you?
Did you get output after ls/dev/sd* ?
Click to expand...
Click to collapse
I had to Apt-get to get it. Once I got it and listed the devices I only got like 4 listed or something close to this: /dev/sda /dev/sda1 /dev/sda2 /dev/sda5
So I attempted the rest with /dev/sda5 but it was giving me errors. I'll attempt it again here after Ubuntu downloads and post the results.
So when I run
~$: ls /dev/sd*
Click to expand...
Click to collapse
I get
/dev/sda /dev/sda2 /dev/sdb1 /dev/sdc1 /dev/sdd1
/dev/sda1 /dev/sdb /dev/sdc /dev/sdd /dev/sde
Click to expand...
Click to collapse
I tried
~$: gdisk -l /dev/sdc
Click to expand...
Click to collapse
but replaced sdc with each variation of the ones above and none of them returned anything like the list in this thread.
nostang3 said:
So when I run
I get
I tried
but replaced sdc with each variation of the ones above and none of them returned anything like the list in this thread.
Click to expand...
Click to collapse
You're definately not getting anything back with more than 1 or 2 partitions. Could be a brick . Maybe if you're lucky you just overlooked some seemingly minute detail. Possibly try a different usb port or different computer.....sorry bud.
There are quite a few "bricked" threads in q&a, and some in dev. Maybe combing through all of that will shed a little light on the subject.
Good luck
1heffer said:
You're definately not getting anything back with more than 1 or 2 partitions. Could be a brick . Maybe if you're lucky you just overlooked some seemingly minute detail. Possibly try a different usb port or different computer.....sorry bud.
There are quite a few "bricked" threads in q&a, and some in dev. Maybe combing through all of that will shed a little light on the subject.
Good luck
Click to expand...
Click to collapse
I searched on this forum and no dice. Since it's not being recognized I'm screwed. I tried doing a different computer with no luck.
nostang3 said:
I searched on this forum and no dice. Since it's not being recognized I'm screwed. I tried doing a different computer with no luck.
Click to expand...
Click to collapse
Had the EXACT same issue, I just got a replacement.
The only different thing, I was messing around with basebands.
NOT a good idea.
hiddenfive said:
Had the EXACT same issue, I just got a replacement.
The only different thing, I was messing around with basebands.
NOT a good idea.
Click to expand...
Click to collapse
I have one being shipped to me as well but I was hoping to somehow get some files off the sd card(if there is one). I have some pictures that mean alot to me.
nostang3 said:
I have one being shipped to me as well but I was hoping to somehow get some files off the sd card(if there is one). I have some pictures that mean alot to me.
Click to expand...
Click to collapse
No backups stored on computer? Didn't backup to google cloud? No cloud backups?
I tried recovering the data for about 6 hours. No dice.
Also, to my knowledge, there is no SD card in the phone, maybe solder points for one but I don't know.
hiddenfive said:
No backups stored on computer? Didn't backup to google cloud? No cloud backups?
I tried recovering the data for about 6 hours. No dice.
Also, to my knowledge, there is no SD card in the phone, maybe solder points for one but I don't know.
Click to expand...
Click to collapse
I had plans to do a cloud backup today, but the error happened. I learned a lot today. Lol. Won't happen again. If it does I'll have a backup.
Related
I was attempting to install the latest Cog...not I've got a little white phone-->!--->PC symbol on the display. No boot screen, no recovery mode. Notta.
Have I killed it?
Dan
No dude, phone is fine. There are a bunch of post on this very issue, and there are several methods on getting it back to d/l mode to restart it. I personaly remove the battery and take sim out and leave it out. Then I open odin, put battery back in, and hold down the volume up and down plug in usb and hit the power button. There are stickys to it also I believe.
Pulling the sim was the trick. I looked around and couldn't find that...when you're panicked, it's easy to look past the important info...
Thanks, I'm doing the one-click right now.
gl with it, happens to me sometimes several times odin stops or something and have to restart it.
jc2470 said:
gl with it, happens to me sometimes several times odin stops or something and have to restart it.
Click to expand...
Click to collapse
Thanks man! I'm back up and running on the latest Cog.
jc2470 said:
No dude, phone is fine. There are a bunch of post on this very issue, and there are several methods on getting it back to d/l mode to restart it. I personaly remove the battery and take sim out and leave it out. Then I open odin, put battery back in, and hold down the volume up and down plug in usb and hit the power button. There are stickys to it also I believe.
Click to expand...
Click to collapse
Thanks!!! You saved my day. This kind of info should be posted everywhere on this forum with big capital letters. Most of the things about bricks involve disappointment, frustration, complicated or intensive workarounds and of course tons of guys telling you that your phone is bricked and you can't do anything about it. Again thank you.
This stuff is posted everywhere.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
jc2470 said:
No dude, phone is fine. There are a bunch of post on this very issue, and there are several methods on getting it back to d/l mode to restart it. I personaly remove the battery and take sim out and leave it out. Then I open odin, put battery back in, and hold down the volume up and down plug in usb and hit the power button. There are stickys to it also I believe.
Click to expand...
Click to collapse
You reopen Odin and reflash the same things ?
PhoneTay11 said:
You reopen Odin and reflash the same things ?
Click to expand...
Click to collapse
yes
10 char
So I was playing angry birds on my nook color. things froze up, and i powered down. Well...now i cant power it on (screen remains black) and therefore cannot get my reset count to 8 and cannot wipe.
I was on 1.0.0 and used the original autonooter
My micro sd is not in the slot when i attempt to power the device.
any ideas? sorta freakin out here...
Have you tried booting by plugging it into the power adapter?
If it only boots when plugged in you might be able to get someone to dd a nook color image and you can restore from that...
Otherwise im outta ideas, and a return might be the only option.
Sent from my NookColor using XDA App
EDIT: try downloading the nookie froyo and see if it'll boot that off the sd... if so someone might make a bootable sd" installer" froma dd-ed image.
Does the three button (power, vol up, n button) boot go to a black screen as well?
Details on that and other steps you can try to recover can be found at: http://nookdevs.com/Portal:NookColor#Fixing_problems
I hope you get it figured out! I was going to root this weekend, but chickened out after seeing soo many problems on here, and a couple of bricked nooks!
I had the same issue last night.
Do the three-button push to wipe /data/ and you'll be set.
Power adapter was the first thing i tried...didnt do anything
as for the three button push, that didnt work either.
Guys, i think i have a genuine brick here
I've only seen one real brick (which actually could have been fixed, but wasn't worth the trouble), and that was caused by a corrupted boot partition.
I don't have the knowledge to really troubleshoot your problem, but I'd be VERY surprised if yours is actually bricked.
I took it back today. they didnt inspect it and just asked if it was defective. I just said i put it on the charger and when i came back it was unresponsive.
tokyoglow said:
I took it back today. they didnt inspect it and just asked if it was defective. I just said i put it on the charger and when i came back it was unresponsive.
Click to expand...
Click to collapse
So what was the result?
urbanengine1 said:
Have you tried booting by plugging it into the power adapter?
Click to expand...
Click to collapse
For future reference, I got mine to this state too, and the power adapter is what got me to actually boot. That's actually plugged into an outlet, not USB, by the way.
Here is what I've tried so far:
1- SuperOneClick. The program hangs at a step where it reads "Check if rooted : false"
2- Galaxy One Click Root. Program is responsive but it stops at "* daemon started successfully *" and does nothing from there.
3- Copying the "update.zip" file to the root of my internal SD card. I'm greeted by a "E: Signature verification failed. Installation aborted" error.
All remediable steps to fix one or all problems REQUIRES root, so i'm in limbo here. I honestly am about to cry. This seemed a hell of a lot easier when I read about it...
Well, what's left here for me to do? I'm lost. I read so many threads here I honestly can't do it anymore. This is my last resort.
This phone is all stock, AT&T Captivate.
Sorry if this is the wrong section of this forum... New here.
Flash your phone via Odin to jf6 stock then try superoneclick
Sent from my SPH-D710 using XDA App
hold up on that flash back. It oculd cause you to loop. Try using SOC v1.9 or lower. Also make sure your computer has all the required updates installed.
So this developed into a new, bigger, problem. I tried THIS guide to flash cyanogenmod (latest) but, guess what, the freaking thing hanged. So I was left with the only option, severing the link between PC and phone, and rebooting the phone.
I get this "phone - attention sign - computer" image. I think to myself "oh sh#&, I bricked the phone" so I rebooted it once again and to my surprise, the phone won't turn on. Won't react to the usb cable (can't boot to download mode), won't react to wall charger, won't turn on with the power button.
The battery was almost full...
What the heck is going on!?!? I had this phone for 3 days and I already ruined it?
I wan't to kill myself
leandroab said:
So this developed into a new, bigger, problem. I tried THIS guide to flash cyanogenmod (latest) but, guess what, the freaking thing hanged. So I was left with the only option, severing the link between PC and phone, and rebooting the phone.
I get this "phone - attention sign - computer" image. I think to myself "oh sh#&, I bricked the phone" so I rebooted it once again and to my surprise, the phone won't turn on. Won't react to the usb cable (can't boot to download mode), won't react to wall charger, won't turn on with the power button.
The battery was almost full...
What the heck is going on!?!? I had this phone for 3 days and I already ruined it?
I wan't to kill myself
Click to expand...
Click to collapse
Unfortunately, it doesn't sound promising. Even if you have a black screen, I would still try to access DL mode with Odin open (pull battery, remove sim, put battery back in, hold both volume buttons and insert the USB cord, don't touch the power button). If you get a yellow com light in Odin, even if the screen stays black, you're in download mode. If that doesn't work, you could try a jig and then see if Odin recognizes it. If neither of those work, you'll need to send your phone out to someone like Adam Outler to have it unbricked.
I get nothing with Odin. I can't believe I bricked my phone like that. I thought I would get an error screen at least. But this is outrageous. It's like the phone shorted and fried from the inside.
All I can say is wow... My happiness of a new phone turned to ashes in 30 seconds. Nice waste of money.
If you buy a USB download jig it will get you out of soft brick situations and if Odin fails try heimindal
Sent from my SPH-D710 using XDA App
leandroab said:
I get nothing with Odin. I can't believe I bricked my phone like that. I thought I would get an error screen at least. But this is outrageous. It's like the phone shorted and fried from the inside.
All I can say is wow... My happiness of a new phone turned to ashes in 30 seconds. Nice waste of money.
Click to expand...
Click to collapse
It didn't fry, it failed while flashing bootloaders. The bootloaders are what tell your phone what to do when you press power. Mismatched bootloaders = hard brick = no power up.
I would still try a jig, but if that doesn't work send a message to AdamOutler. He can give you the details of getting it unbricked.
MJHawaii said:
If you buy a USB download jig it will get you out of soft brick situations and if Odin fails try heimindal
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
Considering the flashing hanged at the very beggining, I'm 90% sure it HARD-bricked my device. A jig wouldn't work and I'm left with a very fancy paperweight.
There is NO power on whatsoever.
My luck is amazing, isn't it?
Please, someone tell me there is still hope (there isn't probably)
apbthe3 said:
It didn't fry, it failed while flashing bootloaders. The bootloaders are what tell your phone what to do when you press power. Mismatched bootloaders = hard brick = no power up.
I would still try a jig, but if that doesn't work send a message to AdamOutler. He can give you the details of getting it unbricked.
Click to expand...
Click to collapse
Exactly. I figured
I have no idea of who "AdamOutler" is. But I'll find out. :/
FML
leandroab said:
Considering the flashing hanged at the very beggining, I'm 90% sure it HARD-bricked my device. A jig wouldn't work and I'm left with a very fancy paperweight.
There is NO power on whatsoever.
My luck is amazing, isn't it?
Please, someone tell me there is still hope (there isn't probably)
FML
Click to expand...
Click to collapse
I suspect you are correct about the hard brick, but I would still try a jig. I had a failure flashing bootloaders once that killed my cappy, but though a stroke of fortune a jig still worked for me. You can build one for a couple of bucks of parts from Radio Shack, you've got nothing to lose. If not, it can be repaired.
Before you start looking at all that, make sure you are hard bricked. Easiest way is to use Linux Mode Detector. Use the link below labeled Captivate sig link, then choose am i bricked?.
apbthe3 said:
I suspect you are correct about the hard brick, but I would still try a jig. I had a failure flashing bootloaders once that killed my cappy, but though a stroke of fortune a jig still worked for me. You can build one for a couple of bucks of parts from Radio Shack, you've got nothing to lose. If not, it can be repaired.
Click to expand...
Click to collapse
Yes, it's still worth a try. But unfortunately it will have to wait at least till the end of the month. That's when my college break is over and I'm back to school.
mrhaley30705 said:
Before you start looking at all that, make sure you are hard bricked. Easiest way is to use Linux Mode Detector. Use the link below labeled Captivate sig link, then choose am i bricked?.
Click to expand...
Click to collapse
Sorry but I'm not installing an OS just to use a program. I do believe the phone is hard-bricked though:
1- Doesn't power up with the on/off button
2- Doesn't go into recovery mode
3- Doesn't go into download mode
4- Doesn't light up when plugged into wall charger
If that isn't hard-bricked, then I'm really scared to find out what that really is
I sent a PM and an email to Adam Outler. I hope he replies it!
Linux is easier to use than you think, and it's a really handy tool to have when working with Android phones. You can install Linux entirely to a cheap thumb drive (I have a $4 4gb thumb drive running lubuntu) and it can get you out of a lot of Android related jams. If you're not willing to go through letting Linux up and running, might not want to do too much with phones either. I don't mean to be snarky, but I started using Linux casually a couple years before I started messing with phones and Linux is much more straightforward.
Edit: and if you have a multimeter around, check the voltage of your battery. Should be 4.2v=full, 3.5v ish is dead. If you battery pull, reinsert, hold volume up and down, and then connect to your pc with Odin open (don't hit power) what does Odin show? Last, did you get this phone used? Battery may be completely worn out, which would be why it was almost full and looks hard bricked now.
Wubi installer would be a better choice. And when your finished, it uninstalls just like an app. It's kind if a semipermanent dual boot. Check it out.
sekine12 said:
Linux is easier to use than you think, and it's a really handy tool to have when working with Android phones. You can install Linux entirely to a cheap thumb drive (I have a $4 4gb thumb drive running lubuntu) and it can get you out of a lot of Android related jams. If you're not willing to go through letting Linux up and running, might not want to do too much with phones either. I don't mean to be snarky, but I started using Linux casually a couple years before I started messing with phones and Linux is much more straightforward.
Click to expand...
Click to collapse
Well, I guess I'll look into that now. I'm running windows over a MacBook (stuck with it till I get back home). Maybe some tips running linux w/ a pendrive with bootcamp?
sekine12 said:
Edit: and if you have a multimeter around, check the voltage of your battery. Should be 4.2v=full, 3.5v ish is dead. If you battery pull, reinsert, hold volume up and down, and then connect to your pc with Odin open (don't hit power) what does Odin show? Last, did you get this phone used? Battery may be completely worn out, which would be why it was almost full and looks hard bricked now.
Click to expand...
Click to collapse
I'll look into the multimeter. The phone IS used, but I'm sure the battery isn't worn out.
Hooking up the phone, pressing both volume buttons, with odin open gives me nothing. Zip. If it was the battery wouldn't the phone give some sign of life after charging it for a while? Didn't happen.
mrhaley30705 said:
Wubi installer would be a better choice. And when your finished, it uninstalls just like an app. It's kind if a semipermanent dual boot. Check it out.
Click to expand...
Click to collapse
As stated, using windows with bootcamp over a MacBook. Maybe you can help me out? Will this work?
leandroab said:
If it was the battery wouldn't the phone give some sign of life after charging it for a while? Didn't happen.
Click to expand...
Click to collapse
My understanding is that charging is controlled by firmware to protect the battery, so it won't even charge if it's bricked.
apbthe3 said:
My understanding is that charging is controlled by firmware to protect the battery, so it won't even charge if it's bricked.
Click to expand...
Click to collapse
Right, or if the battery is so dead it can't start to turn on, it won't turn on. Or, if it was soft-bricked with no images to display, it may have killed itself without a firmware to allow it to charge properly. Not very likely, but there are a couple possibilities that end with a dead battery and no way to know.
apbthe3 said:
My understanding is that charging is controlled by firmware to protect the battery, so it won't even charge if it's bricked.
Click to expand...
Click to collapse
sekine12 said:
Right, or if the battery is so dead it can't start to turn on, it won't turn on. Or, if it was soft-bricked with no images to display, it may have killed itself without a firmware to allow it to charge properly. Not very likely, but there are a couple possibilities that end with a dead battery and no way to know.
Click to expand...
Click to collapse
Right. I'll check the V of the baterry once I get my hands on a multimeter.(somebody took all of them here at the house for some reason)
The multimeter read that the battery has 3.92V, so it's not dead. So to sum it up I only have two options now:
1- Try a USB jig
2- Attempt the UnBrickable mod/send it to Adam Outler
Both of them will take time. Unfortunate for me. Good news is that WILL have it back up and running. It will just take some time
leandroab said:
The multimeter read that the battery has 3.92V, so it's not dead. So to sum it up I only have two options now:
1- Try a USB jig
2- Attempt the UnBrickable mod/send it to Adam Outler
Both of them will take time. Unfortunate for me. Good news is that WILL have it back up and running. It will just take some time
Click to expand...
Click to collapse
So nothing whatsoever shows up in ODIN when you 1- batt pull, 2- batt reinsert, 3- plug in USB while holding either volume down, or volume up + vol down (w/o turning phone on)?
Just looking for opinions. I have a stock note 5, no jail breaking or weird loads. Just a run of the mill Note with way too many candy crush saga apps. We weren't even using it a couple days ago when it turned itself off. Reboot just got it stuck in an endless boot cycle. Loading normal or safe mode gets you the android 'no command' blue screen of death.
I figured maybe bad update...possibly load new firmware. Samsung's smart link application doesn't work, as apparently I don't have a S/N, it doesn't exist and you need that for smart link. (It's not the IMEI.) Anyway, Samsung over the phone told me to try a best buy samsung rep, they'd flash it for free. I thought that sounds safe. But they couldn't get it to recognize my phone....Verizon won't help me, I'm past the year warranty. But still owe too much money to pay it off and get a new one through them...That leaves flashing it myself with Odin. So I did. It went ok, it said it PASSED, the phone rebooted....It started a little config in what looks to be a factory reset type screen...it got to 'erasing', refresh arrow spinning to show me it was going, then it just stops. The world stops and no amount of letting it sit every gets it to go again. Rebooting still has 'no command' and no signs of life.
Any thoughts on what might be going on? Anything else to load or try? The phone's no good to me ****ed, so I'm open to suggestions. Likewise, does it sound like any hardware related things? Is there any hope? would love to hear a first impression from someone more experienced with phones and Android.
Try flashing the latest stock firmware in Odin using "Nand erase all" ticked under options..
Let us know how it goes..
CompuTechnoPro™ said:
Try flashing the latest stock firmware in Odin using "Nand erase all" ticked under options..
Let us know how it goes..
Click to expand...
Click to collapse
Same Problem it looks like. Odin does it's thing for about 3 minutes. Says 'PASS'. Phone restarts, does some initializing bar moving stuff for 10 seconeds, it switches to 'Erasing' then the phone just stops
That's unfortunate dude.
I'm really sick of Samsung phones. They're just terrible. As someone who's had to replace their screen twice and battery three times, it shouldn't be difficult to replace the motherboard.
This happened to my NOTE 5 (SM-N920V) as well
YOUR NOT ALONE! THIS SAME THING HAPPENED TO MY NOTE 5
I was fishing, this morning at about 7am when my phone rebooted all on its own to the same Samsung Boot Logo screen then stuck as well. NO RYHME NO REASON, I have never, ever cracked, hacked or smacked this phone either,:highfive:
"The only updating that has been done has come via Verizon/Samsung..." But none recently ...that I recall as in, the last week or so.
While I will admit doing "it" (hacking,cracking,modding,) to other android phones (Obviously or I wouldn't have a membership here). But this Note 5? No... Maybe perhaps that's why its broken now? LOL...
It does always seem that my continued membership here is not in vain though, ......
For now, I will do whatever it takes to get it back... .......next to buying a new phone or it not coming back on ever.
I will share here what I did to resolve the issue. And I will without a doubt utilize "EVERY" resources here at XDA-DEVELOPERS to do it, and happily without the help of Verizon or Samsung.
So far I have determined that my Note 5 version is not commonly referenced here which is: the SM-N920V (Verizon U.S)
Thank you XDA-Developers this is why we need informational communities like this in our lives! :victory:
Even though I may still go nutz during this repair... if it happens.... Wish us luck!
chroniclogic said:
YOUR NOT ALONE! THIS SAME THING HAPPENED TO MY NOTE 5
I was fishing, this morning at about 7am when my phone rebooted all on its own to the same Samsung Boot Logo screen then stuck as well. NO RYHME NO REASON, I have never, ever cracked, hacked or smacked this phone either,:highfive:
"The only updating that has been done has come via Verizon/Samsung..." But none recently ...that I recall as in, the last week or so.
While I will admit doing "it" (hacking,cracking,modding,) to other android phones (Obviously or I wouldn't have a membership here). But this Note 5? No... Maybe perhaps that's why its broken now? LOL...
It does always seem that my continued my membership here is not in vain, ......as for now, I will do whatever it takes to get it back... .......next to buying a new phone or it not coming back on ever.
I will share here what I did to resolve the issue. And I will without a doubt utilize "EVERY" resources here at XDA-DEVELOPERS to do it, and happily without the help of Verizon or Samsung.
So far I have determined that my Note 5 version is not commonly referenced here which is: the SM-N920V (Verizon U.S)
Thank you XDA-Developers this is why we need informational communities like this in our lives! :victory: Even though I may still go nutz during this repair... if it happens.... Wish us luck!
Click to expand...
Click to collapse
might be bad emmc look into booting from sd card not possible on all devices but may be a start,I had a note 4 do the same thing and most def was bad emmc
Unfortunately, my sd card is internal on the Note5 the unique thing is the Note5 does not have an pop of back plate that covers the battery as, like previous versions which allow the back cover to be removed easily, I mean yeah I can take this thing apart, but its not conventional.
chroniclogic said:
Unfortunately, my sd card is internal on the Note5 the unique thing is the Note5 does not have an pop of back plate that covers the battery as, like previous versions which allow the back cover to be removed easily, I mean yeah I can take this thing apart, but its not conventional.
Click to expand...
Click to collapse
Oh yea and i owned one of these most def not conventional I had mine apart many times.
Mine just shut off one day and wouldn't do anything plugged in or not ended up being the battery
chroniclogic said:
Unfortunately, my sd card is internal on the Note5 the unique thing is the Note5 does not have an pop of back plate that covers the battery as, like previous versions which allow the back cover to be removed easily, I mean yeah I can take this thing apart, but its not conventional.
Click to expand...
Click to collapse
Is there any good way guides on how to find/test eemc or battery or whatever? I can't find many resources at all on how to help me troubleshoot.
Resplendentowl said:
Just looking for opinions. I have a stock note 5, no jail breaking or weird loads. Just a run of the mill Note with way too many candy crush saga apps. We weren't even using it a couple days ago when it turned itself off. Reboot just got it stuck in an endless boot cycle. Loading normal or safe mode gets you the android 'no command' blue screen of death.
I figured maybe bad update...possibly load new firmware. Samsung's smart link application doesn't work, as apparently I don't have a S/N, it doesn't exist and you need that for smart link. (It's not the IMEI.) Anyway, Samsung over the phone told me to try a best buy samsung rep, they'd flash it for free. I thought that sounds safe. But they couldn't get it to recognize my phone....Verizon won't help me, I'm past the year warranty. But still owe too much money to pay it off and get a new one through them...That leaves flashing it myself with Odin. So I did. It went ok, it said it PASSED, the phone rebooted....It started a little config in what looks to be a factory reset type screen...it got to 'erasing', refresh arrow spinning to show me it was going, then it just stops. The world stops and no amount of letting it sit every gets it to go again. Rebooting still has 'no command' and no signs of life.
Any thoughts on what might be going on? Anything else to load or try? The phone's no good to me ****ed, so I'm open to suggestions. Likewise, does it sound like any hardware related things? Is there any hope? would love to hear a first impression from someone more experienced with phones and Android.
Click to expand...
Click to collapse
What you need to do is in Odin options... Uncheck auto reboot. Find the exact .PIT file for your model and put it in odins PIT spot and ignore that it says it's for developers only just add the PIT anyway and in options again where you unchecked auto reboot make sure you check NAND erase all and then add your firmware and after odin flashes it and finally says PASS then disconnect the phone and then hold the volume down button and power button at the same time and when the screens turns off let them go and as soon as it comes back on select nothing but factory reset and when it gets into the recovery mode if it list options and you see factory reset a few lines down use the volume down button to move down to highlight the factory reset option and hit the power button and on the next page again go down to YES and hit the power button again and then let it finish and reboot and least give the phone a good 20 minutes after it's rebooted to get itself setup and to the point where you can start setting it up the same way you did the day you turned it on for the very first time.. Let me know if this works and don't skip any steps.
---------- Post added at 01:55 AM ---------- Previous post was at 01:35 AM ----------
Resplendentowl said:
Is there any good way guides on how to find/test eemc or battery or whatever? I can't find many resources at all on how to help me troubleshoot.
Click to expand...
Click to collapse
The newer Samsung's do not use eMMc they use the newer UFS 2.0 which is why the note 5 and S6 never got micro sd slots. I could be wrong here but I don't think so.
MrMike2182 said:
What you need to do is in Odin options... Uncheck auto reboot. Find the exact .PIT file for your model and put it in odins PIT spot and ignore that it says it's for developers only just add the PIT anyway and in options again where you unchecked auto reboot make sure you check NAND erase all and then add your firmware and after odin flashes it and finally says PASS then disconnect the phone and then hold the volume down button and power button at the same time and when the screens turns off let them go and as soon as it comes back on select nothing but factory reset and when it gets into the recovery mode if it list options and you see factory reset a few lines down use the volume down button to move down to highlight the factory reset option and hit the power button and on the next page again go down to YES and hit the power button again and then let it finish and reboot and least give the phone a good 20 minutes after it's rebooted to get itself setup and to the point where you can start setting it up the same way you did the day you turned it on for the very first time.. Let me know if this works and don't skip any steps.
______________________________________________________________________
Worth a shot.
Where the hell can I find pit files at? why is this **** so obscure on google search. I can't find **** all. It took me forever to find a fireware that appears to work. I'm having no luck finding .pit files
Click to expand...
Click to collapse
Resplendentowl said:
MrMike2182 said:
What you need to do is in Odin options... Uncheck auto reboot. Find the exact .PIT file for your model and put it in odins PIT spot and ignore that it says it's for developers only just add the PIT anyway and in options again where you unchecked auto reboot make sure you check NAND erase all and then add your firmware and after odin flashes it and finally says PASS then disconnect the phone and then hold the volume down button and power button at the same time and when the screens turns off let them go and as soon as it comes back on select nothing but factory reset and when it gets into the recovery mode if it list options and you see factory reset a few lines down use the volume down button to move down to highlight the factory reset option and hit the power button and on the next page again go down to YES and hit the power button again and then let it finish and reboot and least give the phone a good 20 minutes after it's rebooted to get itself setup and to the point where you can start setting it up the same way you did the day you turned it on for the very first time.. Let me know if this works and don't skip any steps.
______________________________________________________________________
Worth a shot.
Where the hell can I find pit files at? why is this **** so obscure on google search. I can't find **** all. It took me forever to find a fireware that appears to work. I'm having no luck finding .pit files
Click to expand...
Click to collapse
What service provider do you have?
Click to expand...
Click to collapse
MrMike2182 said:
Resplendentowl said:
What service provider do you have?
Click to expand...
Click to collapse
the Note 5 in question is a version phone. So n920V. I've honestly googled and opened about 30 ****ty websites, cant find a single one with actual pit files. Just copy pasted generic guides and broken links
Click to expand...
Click to collapse
Resplendentowl said:
MrMike2182 said:
the Note 5 in question is a version phone. So n920V. I've honestly googled and opened about 30 ****ty websites, cant find a single one with actual pit files. Just copy pasted generic guides and broken links
Click to expand...
Click to collapse
Download it from my android file host
.PIT Verizon Galaxy Note 5
Click to expand...
Click to collapse
MrMike2182 said:
Resplendentowl said:
Download it from my android file host
.PIT Verizon Galaxy Note 5
Click to expand...
Click to collapse
Well ****, we're worse off than when we were before. I don't know if this in indicative of a hardware problem, but now that the battery has had time to drain, I plugged it in and left if for a day, but any time the cord is plugged in the phone is stuck in an infinite no command/reboot loop, and I can't get to download mode with up arrow + home + power like I could before. With the phone unplugged it has no life whatsoever.
Could this be a battery issue the whole time?
Click to expand...
Click to collapse
Resplendentowl said:
MrMike2182 said:
Well ****, we're worse off than when we were before. I don't know if this in indicative of a hardware problem, but now that the battery has had time to drain, I plugged it in and left if for a day, but any time the cord is plugged in the phone is stuck in an infinite no command/reboot loop, and I can't get to download mode with up arrow + home + power like I could before. With the phone unplugged it has no life whatsoever.
Could this be a battery issue the whole time?
Click to expand...
Click to collapse
Yes and it sounds like a hardware issue by draining that fast.. Did you try holding the volume down button and power button until it reboots?
Click to expand...
Click to collapse
MrMike2182 said:
Resplendentowl said:
Yes and it sounds like a hardware issue by draining that fast.. Did you try holding the volume down button and power button until it reboots?
Click to expand...
Click to collapse
So When it was plugged in to my comp it would not go into download mode...If I unplugged the cord, it would not turn on.
I got a wall outlet charger instead, with that plugged in I could get to download mode, and when I tried to turn the phone on without the wall charger it gave a 'battery 0%' warning...
Anyway, I got it to down load mode, unplugged the wall charger, moved it to the comp and did the flash with the pit file...Odin said it passed. I restarted the phone, picked factory reset. It installs a few quick things, goes to 'erasing' and after about 20 seconds, freezes, same as last time. Now it's back to no command
Click to expand...
Click to collapse
Resplendentowl said:
MrMike2182 said:
So When it was plugged in to my comp it would not go into download mode...If I unplugged the cord, it would not turn on.
I got a wall outlet charger instead, with that plugged in I could get to download mode, and when I tried to turn the phone on without the wall charger it gave a 'battery 0%' warning...
Anyway, I got it to down load mode, unplugged the wall charger, moved it to the comp and did the flash with the pit file...Odin said it passed. I restarted the phone, picked factory reset. It installs a few quick things, goes to 'erasing' and after about 20 seconds, freezes, same as last time. Now it's back to no command
Click to expand...
Click to collapse
How long did you let it sit there? Do the factory reset again and let it sit there for a little bit and see if it eventually goes. If not boot into recovery again and read to see what version firmware is listed.
Click to expand...
Click to collapse
MrMike2182 said:
Resplendentowl said:
How long did you let it sit there? Do the factory reset again and let it sit there for a little bit and see if it eventually goes. If not boot into recovery again and read to see what version firmware is listed.
Click to expand...
Click to collapse
It kicks itself off and goes to a 'no command' after the erasing screen gets stuck and quits 'twirling' for awhile. I don't know how to see a firmware listing. I can't get to a recovery mode(using that terminology to google some screenshots, I don't have that). The phone boots to maintenance mode only...any option I pick there goes to no command. I can use the vol down + home + power to get into download mode so it will be seen by the pc. That's about it
Click to expand...
Click to collapse
Resplendentowl said:
MrMike2182 said:
It kicks itself off and goes to a 'no command' after the erasing screen gets stuck and quits 'twirling' for awhile. I don't know how to see a firmware listing. I can't get to a recovery mode(using that terminology to google some screenshots, I don't have that). The phone boots to maintenance mode only...any option I pick there goes to no command. I can use the vol down + home + power to get into download mode so it will be seen by the pc. That's about it
Click to expand...
Click to collapse
That means that it didn't flash fully.. What firmware version did you flash in odin? And you can see the phone version again by going into download mode too it should be right at the top after pressing the volume up.
Click to expand...
Click to collapse
Heyyo all. I was trying to reflash the stock rom, and kept having "too many links" errors. Restarted my PC, and tried again. Looked like it was working, until the phone "restarted". It didn't turn back on, and nothing is working on it now. Tried holding every button combo for 2+ minutes each. None had any effect. Tried holding volume down while plugging it in. Still nothing. Anyone have any idea how I can force it into download mode or anything?
Appreciate any input you have.
Edit: By nothing is working, I mean it won't turn on at all. Display stays black no matter how long I hold the power button.
Plugging in the charging cable also no response?
Docence said:
Plugging in the charging cable also no response?
Click to expand...
Click to collapse
Unfortunately not. Had tried leaving it charging for an hour or so in case it somehow died, and nothing. Left it unplugged all day today hoping a full battery drain may kick it back to life.
TBurn420 said:
Unfortunately not. Had tried leaving it charging for an hour or so in case it somehow died, and nothing. Left it unplugged all day today hoping a full battery drain may kick it back to life.
Click to expand...
Click to collapse
I guess you unlocked the critical bootstrap partition, the "too many links" error may be a problem with the connection of the data cable, which caused some underlying partitions to be damaged due to disconnection during the flashing process
Docence said:
I guess you unlocked the critical bootstrap partition, the "too many links" error may be a problem with the connection of the data cable, which caused some underlying partitions to be damaged due to disconnection during the flashing process
Click to expand...
Click to collapse
I had unlocked it, yeah. I was thinking it may have been the same thing. I had tried a different cable as well. Both would switch between no link, and too many links. Eventually just wouldn't boot into anything, so I think you're right about the partitions being damaged.
Do you know of any way to try to repair them? Ill do some Googling myself now as well
TBurn420 said:
I had unlocked it, yeah. I was thinking it may have been the same thing. I had tried a different cable as well. Both would switch between no link, and too many links. Eventually just wouldn't boot into anything, so I think you're right about the partitions being damaged.
Do you know of any way to try to repair them? Ill do some Googling myself now as well
Click to expand...
Click to collapse
I think your rp2 had turned a hard brick, because Razer did not provide a firehose file, can't flash any partition in 9008 mode
Docence said:
I think your rp2 had turned a hard brick, because Razer did not provide a firehose file, can't flash any partition in 9008 mode
Click to expand...
Click to collapse
riiiip. I'll try contacting them and see if its possible to get them. Thank you for your help!
Edit: Razer refuses to provide any support for the device now. It ended a year ago. Although in some other searching someone was saying they found the firehouse file within one of the .img's in the stock rom. Going to look more into it.