Related
Pardon for the long post but my Nexus One has been out of comission for a few days now so I'll list everything I've tried to make it work in an attempt someone might be able to help me!
Okay, here goes.
A couple days ago I removed the battery on my phone to install an invisible shield. Prior to that I had owned the Nexus One brand new for about a week, had it rooted first thing with the HTC Desire ROM...it was running perfectly
After the installation of the shield was complete I reinserted the battery and hit the power button. The phone booted straight to the bootloader (aka white Robots on Skateboards screen). Funny thing, I was unable to navigate the bootloader (vol up/down) without fiddling with the trackball first by pressing it a couple times) Anyway if I would reboot the phone via bootloader it would return...power off the phone it wouldn't power off just reboot to bootloader.
In this mode I could still use fastboot perfectly and I could enter the restore screen. At this point I kept attempting a reboot and it actually went through at one point and did a full boot to the OS...when I powered down and booted up again however, it was back to the same issue.
On the modaco forum they suggested I flash an alpha2boot.img as the boot image replacement for r21 desire rom as a fix, I tried this method with no success. Since, I've factory reset the phone several times replacing it with various ROMs (currently running stock) none of it fixed the problem.
I also found a way to brute force the phone into safe mode via the fastboot command in prompt: fastboot-windows reboot Using this command the phone successfully reboots, albeit into SAFE MODE. In safe mode the phone works perfectly in every way. I'm just limited in that I can't install any applications and I can't reboot properly (without a computer and command prompt).
I was doing some research on the forums and read the problem could be with the trackball. It would make sense that the phone could only boot to bootloader if the phone had the key press for the trackball triggered somehow. That said, the trackball functions perfectly when operating the phone in safe mode so I doubt this is the issue.
Another idea is that the phone is stuck in some state in the SPL or bootloader...I was wondering if there was anyway to reflash the SPL or bootloader to see if I could resolve the issue that way. (how I would do this, I have no idea)
Any help, suggestions, or advice is very appreciated. As I already unlocked my phone I have a feeling I am out of luck for warranty though I would pay for HTC to repair it if they could. I would prefer to fix it in the software however and not send it in.
Reflash the stock ROM and see if that helps.
mortzz said:
Reflash the stock ROM and see if that helps.
Click to expand...
Click to collapse
He said he's running stock rom...
@ OP, if everything was absolutely perfect before putting the shield on, and everything to crap immediately after finishing the shield, then obviously something went wrong during the install.
The obvious yet unfortunate conclusion is that some solution got inside or something, most likely inside the trackball. =\
Detail exactly what you did when you installed the invisible shield.
Did you get you phone wet at all?
Got the front of the phone a little wet and I'm guessing some did get in the trackball. That said, I do invisi shields every day for my job and never had an issue with any phone...wouldn't it be ironic that mine was the one that got screwed up.
I think it's interesting to note that the trackball still works perfectly when the phone is running in safe mode, no double clicks or anything like that...possibly a sensor was tripped?
Got the front of the phone a little wet and I'm guessing some did get in the trackball. That said, I do invisi shields every day for my job and never had an issue with any phone...wouldn't it be ironic that mine was the one that got screwed up.
I think it's interesting to note that the trackball still works perfectly when the phone is running in safe mode, no double clicks or anything like that...possibly a sensor was tripped?
So I called it quits on fixing this phone and I'm sending it out to HTC does anyone know how I go about getting restore back to factory settings?
Well you can't relock the bootloader, but if you can use fastboot when your phone's on the booatloader, you can use that to wipe the phone.
Oh wow, sorry to hear it.
If your phone will not boot without the help of fastboot, I wouldn't worry to much about what state Android is in (factory, or custom rom). HTC will attempt to boot the phone, toss it in a bin, and then send you a replacement.
Or that is my assumption anyways. A friend had a similar issue; he unlocked his phone and decided after flashing the Desire rom, that he wanted to stay stock with what came on his Nexus for a while. After flashing the stock images back, his phone looped into bootloader. Off to HTC it went and within a week he had a new phone.
Best of luck!
Sorry to post in such an old thread, but I'm having the exact same issue. Even the part with the invisible shield. Didnt install it myself, the idiot at best buy used too much of the liquid I guess. Did you send yours in or what? I managed to get the phone to work for about a month then it started acting up again today. Wont boot into anything other than safe mode, or fastboot. When it boots into safe mdoe, the phone turns off within a few seconds then goes straight to the boot animation. Would love to get this issue settled, really annoying
i am having same problem. fasboot doesnt even find my phone. i got into safe mode but when i turned it off and back on it went back to fastboot
Same
I am getting the same problem! this really sucks. I think the phone might have gotten a little bit wet, just a few drops of water, and that may have caused this. Should I just call HTC and send it in?
btw, the phone was working fine, even with the very little moisture that was wiped from it. But, I took out the battery when I got home, and this happened.
so is this because on invisibleshield? cuz i just ordered mine today!!
I think its from a little bit of moisture getting into the trackball. I've been doing many "tests" trying to figure out the problem, and my almost final conclusion is the trackball not working good. Most of the time I try to start-up the phone i get into safemode, and once I have gotten into the normal way of things, but the trackball wasn't working well. I think I might have to cal htc, and that sucks because I am going out of the country in 4 days... I won't be able to take my nexus if I can't come up with a way to fix it myself.
I DID IT!
Well, I think I did.
My theory that moisture was the cause of this bootloader stuckness is quite correct. I took a towel, and rubbed the trackball to it for a good 5-10 min, then I did it for another 5-10 min wiping while pressing down on the trackball. I'm very sure that there was some moisture extracted from the device. The trackball is working now. I now do not have to call HTC or send it in.
I kept on booting into fastboot and then recovery, being unable to press buttons, but then I rebooted again into safe mode, where the trackball wasn't working either. I kept moving around the trackball, and then I figured it out, because I felt a slight bit of moisture. Now, it boots up normally, I can access the recovery, and all selection is working.
But, I have a bad feeling that this problem will come back to haunt me. It's good for now though.
Phone is working great as usual.
Can confirm the same issue.
Drop of water on the trackball.
Rebooted into an unresponsive fastboot.
Fastboot reboot command from the computer got me into safemode.
Rolling the trackball while pressed fixed it, the phone boots properly now.
Hello,
I bought a Nexus one and as I don't live in a country that sells it my cousin brought it to me.
The device doesn't work and self Reboots giving me 20 seconds of use.
Tryed working with/without a sim,
Did a Factory Reset,
Formated the Sd-Card on my Pc,
and still in the same spot.
any ideas on what else to try before giving up?
anyone had this problem and fixed it?
My phone is not ROOTed and is on Version 1 of 2.1
didn't have enough time to get other info like Baseband and stuff.
I'm not willing to root the phone.
** If i send it back it will make the phone very expensive as i will have to pay costums fee when they mail it back to me
Thanks in advance!
Sounds like a DOA. Really bad luck.
If you send it back you should not pay duty to get it back usually, unless you live in a very tax hungry country! Between US and CAN you would not get duty.
Beside try speaking with cust support, DOA are usually well handled by company and so far HTC seem to be handling repair quite well as per the few post about broken screen I have seen.
Did you try running the phone WITHOUT an SD card ? good luck!
Krypton1984 said:
Hello,
I bought a Nexus one and as I don't live in a country that sells it my cousin brought it to me.
The device doesn't work and self Reboots giving me 20 seconds of use.
Tryed working with/without a sim,
Did a Factory Reset,
Formated the Sd-Card on my Pc,
and still in the same spot.
any ideas on what else to try before giving up?
anyone had this problem and fixed it?
My phone is not ROOTed and is on Version 1 of 2.1
didn't have enough time to get other info like Baseband and stuff.
I'm not willing to root the phone.
** If i send it back it will make the phone very expensive as i will have to pay costums fee when they mail it back to me
Thanks in advance!
Click to expand...
Click to collapse
If the boots, has never been rooted (boot unlock), no immediate physical damage, and has no signs of liquid damage or tampering (check void sticker).... it's likely just a software issue. Reload original firmware, or load a new firmware... Don't give up, sounds like the phone is still okay.
Was it bnib?
mrbkkt1 said:
Was it bnib?
Click to expand...
Click to collapse
So it seems.
Where are you from, Krypton1984 ?
Looks like some rogue app is loading at boot, causing reset. Possibly corrupt ROM image - but not sure. Might be software, might be hardware. But here's one thing to try:
If you're on a T-Mobile-compatible phone (900/1700/2100), do yourself a favor and flash stock Froyo. No need to root for that. The guide is in the sticky thread. In case of corrupted ROM image it'll do the trick.
I think you should factory reset it. Maybe even download the official 2.1 rom and install it. See if it fixes it.
Try a battery trade in first. Believe it or not, my first N1 seemed dead, and support gave me a swap for a new unit. When the new unit came in, it was still "dead" with the battery that originally shipped with the device. A new battery is what caused my N1 to finally come to life. The batteries that ship with N1's have QC issues, because I was one of many to report a DOA battery in the Google support forums.
its brand new,
I didn't pay customs on the way in because my cousin brought it to me, so if i send it back i will and it makes the phone very expensive.
what if when i try to change firmware the phone reboots again without finishing?
i dont want to brick the phone.
Krypton1984 said:
its brand new,
I didn't pay customs on the way in because my cousin brought it to me, so if i send it back i will and it makes the phone very expensive.
what if when i try to change firmware the phone reboots again without finishing?
i dont want to brick the phone.
Click to expand...
Click to collapse
Well booting to the bootloader will answer the hardware software question.
1. Turn off the phone.
2. Now press (and hold) the Trackball and turn on the phone.
Once you're in the loader let it sit for a while. If it stays up it's a software problem and a new ROM should sort it out. If it reboots while in the bootloader it sounds like a DOA phone.
Good luck.
You can also try a full factory reset through the bootloader. Search for the instructions as i do not know them off the top of my head
P00r said:
Between US and CAN you would not get duty.
Click to expand...
Click to collapse
Yeah, North America is all one big happy family. We've got NAFTA and everything now.
OP, I am assuming you've allowed the battery to charge full?
badomen said:
Well booting to the bootloader will answer the hardware software question.
1. Turn off the phone.
2. Now press (and hold) the Trackball and turn on the phone.
Once you're in the loader let it sit for a while. If it stays up it's a software problem and a new ROM should sort it out. If it reboots while in the bootloader it sounds like a DOA phone.
Good luck.
Click to expand...
Click to collapse
i am having a similar issue. The phone reboots randomly and gets stuck at the static X logo screen. i have to remove the battery and let it be aside for at least 10 minutes before i am able to get the phone up and running again.
i tried updating to froyo. it installed but then froze up again on reboot. i did the battery thing and then started it up, went on fine..froyo had been successfully installed, but my random reboot problem STILL DID NOT GO AWAY..
can this be sorted by installing the original rom image?? or do i have to go in for a swap?!?
i don't want to swap coz they send out refurbished devices,,but its the last option...
padhi87 said:
i am having a similar issue. The phone reboots randomly and gets stuck at the static X logo screen. i have to remove the battery and let it be aside for at least 10 minutes before i am able to get the phone up and running again.
i tried updating to froyo. it installed but then froze up again on reboot. i did the battery thing and then started it up, went on fine..froyo had been successfully installed, but my random reboot problem STILL DID NOT GO AWAY..
can this be sorted by installing the original rom image?? or do i have to go in for a swap?!?
i don't want to swap coz they send out refurbished devices,,but its the last option...
Click to expand...
Click to collapse
You'll probably need to swap based on what you're saying. I, though, actually think Refurbished devices are just as good or even better than new. Think about it, if you keep getting dust under the screen maybe a refurbished phone will already have the fix? For that scenario it works out.
padhi87 said:
i am having a similar issue. The phone reboots randomly and gets stuck at the static X logo screen. i have to remove the battery and let it be aside for at least 10 minutes before i am able to get the phone up and running again.
i tried updating to froyo. it installed but then froze up again on reboot. i did the battery thing and then started it up, went on fine..froyo had been successfully installed, but my random reboot problem STILL DID NOT GO AWAY..
can this be sorted by installing the original rom image?? or do i have to go in for a swap?!?
i don't want to swap coz they send out refurbished devices,,but its the last option...
Click to expand...
Click to collapse
I really think this is a bad RAM issue.
I had this happen to my Nexus (ATT). It was prior to flashing froyo. I tried everything, flashing back to stock (including radio), cyan's latest, Paul's (stock) Froyo (with and without radio). Same result. Seemingly random reboots.
I thought initially that it was a software issue - It would not reboot while in fastboot/Amon's Recovery. But having tried every software combination, I've concluded that it MUST be hardware, unless I'm missing something big.
The phone, for the most part, would be fine as long as I DON'T TOUCH IT. It would stay idle for a long period of time (24hrs+), then I would use it Everything from web browsing to downloading apps to making calls, and it would reboot. It's frustrating because it seems that it's rebooting for no reason except that I'm touching it.
Sent in for a replacement, it arrives today. Hopefully it will not suffer this problem.
After talking with HTC they told me i need to swap the phone.
Because i'm out of america i need to send it to someone in the US amd then they send him the new divice after he sends my old one,
I am not satisfide with google's (first guy I talked with) and HTC because none of whome understand the severity and the hard feeling of getting a BRAND NEW IN BOX paper-weight. nothing about we'll compensate you or nada.
For me it tells me the brand is not strong enough to manage an outer state service and i wouldn't recomend them for countries that they don't cell it for.
If you where born in a HTC GOOGLE compatible country enjoy!
As i'm am probably less lucky and still in 2010 nationality counts
And now I'm boot looping won't go past n color startup animation wth
Sent from my Cyanogen Mod EVO using Tapatalk
I had that problem on my NC when it was rooted. Luckily I had another problem that let me get out by the 8 times reset manual method. Mine would occasionally update itself back to version 1.0.0. When it did that I managed to reset it & now a new NC is on its way to replace this one.
This probably won't help solve the issue but at least it lets you know you're not alone.
Mine boot looped and I did the full 8X reboot thing and then the 3 button data reset. All of that puts you back to "out-of-the-box" stock. You can then redo the autonooter rooting procedure.
Can't get out
I am stuck in a boot loop and cant get out.
First it was stuck on the droid boot animation from the auto config. After I put the autonooter card back in it started looping the rooted boot animation.
Did the 3 button thing and that forced an update but went back to bootlooping the rooted animation.
Then did the 8X reboots manually and that also forced the down arrow update, but then it still bootloops.
I tried getting in from PuTTy (as admin) but it never connects. Do I just use port 22? (to 192.168.2.2 with Data and username as root?)
adb doesn't work... going to bed now and will try again tomorrow after work.
What i had to do to resolve my issue was that was to do the 8x reset to trigger the factory reset of the OS and then do the 3 button reset of the user data. In my case it was a self tweaked issue with an app permisson. If I remember right the key combo is Power+VolUp+"n" key. Try this and let us know.
Sent from my NookColor using XDA App
Bigger Issues.... First Brick?
Nate731 said:
What i had to do to resolve my issue was that was to do the 8x reset to trigger the factory reset of the OS and then do the 3 button reset of the user data. In my case it was a self tweaked issue with an app permisson. If I remember right the key combo is Power+VolUp+"n" key. Try this and let us know.
Sent from my NookColor using XDA App
Click to expand...
Click to collapse
So ... I left my Nook in what I thought was an "OFF" state last night, only to bring it to work and find it says "Battery too low to Power on" "Please wait 15 minutes and try again"
I think... no worries... plug it in and let 'er sit for an hour.... an hour passes and I'm still getting the same screen.
Is this better or worse? let me see...
1) if it stays like this, I can return/exchange it at B&N and they won't be able to verify that it was rooted due to non-bootiness
2) If it eventually boots, I will have to try to get it out of bootloop.
3) If it comes to life and I can't get it out of bootloop, I will drain the battery again and go back to #1.
Any thoughts besides this current train?
sort of working?
OK....
so after charging on USB port (all I have at work today as I forgot the base to the charger), it will bootloop again... yay!
problem is... the bootloops take too much juice and won't allow me to fail 8 reboots. I can't even charge it up enough since I'm on USB charging and it keeps trying to turn itself on.
2 Options i see:
1) Go home and charge it on the wall and see if that helps
2) Discharge it to death and return within my 30 days (X-mas gift)
Doubt this will work, but have you tried putting in an autonooter sdcard and then plug it into the usb? If it tries to boot maybe it will boot from that sdcard?
Boot from the Froyo SD card, then fix /rom/devconf/BootCnt from ADB.
Cal you never mentioned if you cleared the user data... Did you?
Nate731 said:
Cal you never mentioned if you cleared the user data... Did you?
Click to expand...
Click to collapse
If you mean the 3 button reset? Yes.
If not... I did not because I'm not aware of it. (couldn't through the UI of course)
cal3thousand said:
If you mean the 3 button reset? Yes.
If not... I did not because I'm not aware of it. (couldn't through the UI of course)
Click to expand...
Click to collapse
Try Geezer's tip but do this:
Do three button reset WITH the autonooter card in there.
Got it working
Finally got it working after creating a Nookie Froyo card and booting off of that.
Then I reinstalled ADB on my work computer and reset the BootCnt file to 8...
that successfully restored /system and then the 3 finger trick actually gave an option to wipe.
Now to start over.
New Question: How likely is this hardware related and should I be looking to replace it before my 30 days is up>?
I ran into the same problem, trying the same solution - any luck the second time?
JasonBunting said:
I ran into the same problem, trying the same solution - any luck the second time?
Click to expand...
Click to collapse
My Nook has been great since the fix. But I also needed to use a program to turn off Wifi when I turn the display off.
I did it all from my Nookie...
confused?!
I was wondering how you fixed this..i have read everywhere, but nothing...im stuck in the nook co screen. This happened right after i plugged my nook to charge after my battery was drained...thnks
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
Hey guys,
I have a problem with this phone. I got my relative's note 8 for trying to fix ( i'm not android expert ).
As she says, for no reason phone freezed and shuted down. After that charging problem started, and battery doesn't show real percentage.
After that i got the phone, and tried to go factory reset in recovery menu. Now phone stucks at samsung logo. Sometimes it stucks at blue screen with "no command" text.
Phone doesn't works all the time also. For example, somehow phone charged %100, after that i tried to open it, it stucked at samsung logo. I tried hard reset, screen off and no more screen. After 4-5 hours it worked again, but stuck at samsung screen again.
I send phone to trusted local repair shop. They couldn't managed to fix also, they reported me that it should be motherboard issue and they can't do anything about it. I don't know did they tried to install stock rom again.
I see no reason for motherboard issue. No water, no big damage or something else happened to phone. There should be a way to fix this and i seek your support here.
Whaki said:
Hey guys,
I have a problem with this phone. I got my relative's note 8 for trying to fix ( i'm not android expert ).
As she says, for no reason phone freezed and shuted down. After that charging problem started, and battery doesn't show real percentage.
After that i got the phone, and tried to go factory reset in recovery menu. Now phone stucks at samsung logo. Sometimes it stucks at blue screen with "no command" text.
Phone doesn't works all the time also. For example, somehow phone charged %100, after that i tried to open it, it stucked at samsung logo. I tried hard reset, screen off and no more screen. After 4-5 hours it worked again, but stuck at samsung screen again.
I send phone to trusted local repair shop. They couldn't managed to fix also, they reported me that it should be motherboard issue and they can't do anything about it. I don't know did they tried to install stock rom again.
I see no reason for motherboard issue. No water, no big damage or something else happened to phone. There should be a way to fix this and i seek your support here.
Click to expand...
Click to collapse
I would go with what the repair shop said personally. They certainly know a lot more than I do. Unfortunately things do just break even with no error for the owner themselves.
It is definitely worth trying to flash stock rom with Odin though.
stonedpsycho said:
I would go with what the repair shop said personally. They certainly know a lot more than I do. Unfortunately things do just break even with no error for the owner themselves.
It is definitely worth trying to flash stock rom with Odin though.
Click to expand...
Click to collapse
Thanks for your thoughts, honestly i don't expect it to work again, but before throw away i want to try all chances