So, long story short, my GS4 just froze up and shut off on me this morning while checking out Facebook on the phone, and now it won't turn on no matter what I do.
Removing the battery and holding the power button for a few minutes partly resolves my issue, as I am then able to actually power on the phone, but then it just gets stuck on the GS4 logo and doesn't boot into the actual system. I was also able to get into Download mode at one point, but I wasn't sure about flashing new firmware from there since my phone is rooted and has a custom recovery installed, and maybe that will interfere with the installation.
Anybody got some input on this? I am kinda freaking out here, would really love it if I could fix this thing without taking it to an overpriced shop, who maybe wouldn't even accept it due to it's 'modified firmware'.
BamBamBam. said:
So, long story short, my GS4 just froze up and shut off on me this morning while checking out Facebook on the phone, and now it won't turn on no matter what I do.
Removing the battery and holding the power button for a few minutes partly resolves my issue, as I am then able to actually power on the phone, but then it just gets stuck on the GS4 logo and doesn't boot into the actual system. I was also able to get into Download mode at one point, but I wasn't sure about flashing new firmware from there since my phone is rooted and has a custom recovery installed, and maybe that will interfere with the installation.
Anybody got some input on this? I am kinda freaking out here, would really love it if I could fix this thing without taking it to an overpriced shop, who maybe wouldn't even accept it due to it's 'modified firmware'.
Click to expand...
Click to collapse
if it boot into recovery, factory reset your phone and wipe cache, it's a painful solution but it's functional.., I've had the same issue on another Samsung phone and that fixed it, also I don't think flashing stock rom would interfere with anything, you can try that as well.
Related
Ok, I went to take a picture and it freaked the **** out. Now I rooted my phone when I got it, I have done nothing else other then Xposed modules and since it start acting up I've literally done nothing else. I only get the screen that says custom and then blah nothing else. I swapped battery (got another battery from samsung directly) and I have no idea wtf to do. Don't recommened ****ing flashing **** or whatever because I have everything stock. This should not happened. I wiped dalvik cache and cache and it was within recovery but my phone can't boot, I removed SD card, sim card and sometimes it'll boot be on for a couple minutes and bam same issue.... WHAT THE FLYING **** CAN I DO? I need this phone ASAP.... I'm this close to just tossing it over the edge and getting a new one.... it's a flying piece of **** and **** samsung!
You might have to start from scratch and determine if it's a hardware issue. Do you know what firmware you're on? Also back everything up because if you start from scratch, we'll that's the what you'll have.
Thanks, I managed to get it on again, made some calls uninstall some apps, but then it ****ing freaked out again. I have the firmware that was on when it was released. I got the first batch of 32gb's S4's haven't changed the firmware since... to prevent this type of ****. UGH! So after a phone call my phone just bleeped again and ****ed up. So I don't understand anything anymore.
rubsnick said:
Thanks, I managed to get it on again, made some calls uninstall some apps, but then it ****ing freaked out again. I have the firmware that was on when it was released. I got the first batch of 32gb's S4's haven't changed the firmware since... to prevent this type of ****. UGH! So after a phone call my phone just bleeped again and ****ed up. So I don't understand anything anymore.
Click to expand...
Click to collapse
So you used odin to flash mdl firmware?
I've done nothing in regards to flashing. I have not connected my phone to my computer. I've done nothing at all. other then keep trying to turn it on over and over again.
rubsnick said:
I've done nothing in regards to flashing. I have not connected my phone to my computer. I've done nothing at all.
Click to expand...
Click to collapse
Well you might have to to see if it's a hardware issue. I would suggest flashing the firmware you're currently on through Odin
How am I supposed to do that if the phone just won't be recognized by anything? it's ****ing dead now. It shows me the Samsung Custom lock and logo and then nothing. I press the power button and nothing, I have to remove the batter and put it back in to see that screen.
Ok now it randomly is charging and now I can turn it on again, no problem, after I forcefully press the power button and some other random things... could I have an issue wiht my power button staying pressed? why would it do that? how can I fix this? I'm willing to open it up. I'm currently doing a backup in titanium backup and so far it seems ok. Recieved a phone call, phone is charging and everything is ok. how do I boot it into safe mode?
http://m.samsung.com/us/support/faq/FAQ00052827/62062/SGH-I337ZWAATT
Thanks, I believe the cause was a stuck power button.
I was headed home today and my Sprint Galaxy S4 shutoff. It would not come back on, so i removed the battery. When i reinsert the battery, my phone does a quick vibrate, then the white Samsung Galaxy S4 logo screen appears, then disappears, then thats it. Nothing else happens. I have tried different chargers, a different battery, tried download and recovery mode. Nothing has worked so far to get me any further. When i try to go into recovery, blue writing shows in the top left that says Booting Recovery, then it shuts off and nothing else happens. When i plug into a computer, the phone does not connect to the computer.
I am usually pretty good with anything to do with a phone, but this has me stumped.
I have not downloaded any new apps or any different roms or kernels anytime recently. My phone is rooted but still on the stock rom. This phone was rooted about a year ago when i got it, and as far as roms or programming or anthing, nothing has been done to it since then.
Does anyone have any ideas?
Ok so i was wrong, the phone will boot into download mode, but only for about 2 secs, then it goes blank and off again. So it seems like some sort of power issue with the phone itself, as in hardware. Not sure that there is too much that i can do about that, but does anyone have any ideas?
I just read something on here about Samsung having a bad batch of batteries. If I were you I would take my battery to someone that could test it to see if it is holding a charge.
Had the same issue. The dude at sprint said it was a bad update that went out but not sure how true that is due to the fact that i was running a custom rom and recovery. I was running clockword mod recovery and latest CM11 nightly. If you have the insurance I'd say bring it back and they should replace it.
Any fix?
I have just been experiencing this problem as well. My s4 was working fine then all of the sudden the power button would become very sensitive and would think I would want to turn the phone off. I would click the back arrow but the phone would still either turn itself off or reboot. Then it got worse and would get stuck in bootloops. Now I have to reinsert the battery every time for it to turn on. It gets to the samsung logo and then shuts off. I can get into recovery for about 2 seconds and then it shuts off as well. My s4 is not rooted at all. Can someone please help me? I really don't want to pay at least 70 dollars for samsung just to look at it.:crying:
Hey,
This is my first time posting here and really using the site. I have the Sprint Galaxy S4 and just updated to the SlimKat official build 7 and had no initial problems. A day later it starts to reboot constantly and would stay on for a couple minutes. Now it is stuck in a bootloop and will shut off even when going into download or recovery mode. When plugged into a computer the computer won't even recognize the phone and the phone will not turn on. The only time the phone will even start to boot is when it is not plugged into wall/computer and on battery. I have no idea what to do now.
That's a tough one. Usually with a soft brick, if you can make it to recovery, your phone can be saved but since you can't... I hope you get it working!
Sent from my SPH-L720 using XDA Free mobile app
puresublimie said:
Hey,
This is my first time posting here and really using the site. I have the Sprint Galaxy S4 and just updated to the SlimKat official build 7 and had no initial problems. A day later it starts to reboot constantly and would stay on for a couple minutes. Now it is stuck in a bootloop and will shut off even when going into download or recovery mode. When plugged into a computer the computer won't even recognize the phone and the phone will not turn on. The only time the phone will even start to boot is when it is not plugged into wall/computer and on battery. I have no idea what to do now.
Click to expand...
Click to collapse
Go to sprint galaxy s4 thread. All answers there. You need Odin 3.09 then stock ng2 tar. To flash through computer.
Sent from my SPH-L720 using XDA Free mobile app
I already have odin and the tar files for stock. When plugged into my computer it will not even register that it is connected and so I can't use odin to flash it.
The same thing is happening to me. I get to the Galaxy S4 splash screen, then it shuts off. Even if I try to boot into recovery
I'm going to pile on in here as I seem to be having a similar issue. I had my S4 (not rooted, stock rom) on my dock streaming google music. A phone call came in and the phone started vibrating like crazy and wouldn't stop. The screen shut off and the phone was still vibrating. Finally it stopped and was shut off. When I try to start it a few things happens. It will sometimes boot to my lock screen and the screen goes black and I think it is powered off. Sometimes it will get past the lock screen and then die shortly after. After like 2 or 3 times of that it won't even boot. It loads the Samsung screen but never gets to the Sprint screen or boots. If I leave it for some time shut off with battery out it will go back to booting to the lock screen then dying etc... When I press the buttons to get into recovery it says recovery is loading and then the screen goes black. I swapped batteries and that didn't do anything. I tried pressing the menu button or the home button to try and boot safe mode and it just loads normally not that I think that would help anyway.
Any ideas on things I can try next? What is this odin thing? Would that work for me?
---------- Post added at 07:09 PM ---------- Previous post was at 06:16 PM ----------
Ok... I can get into recovery now and will try a factory reset. Are you sure you are going into recovery correctly. Apparently I was not. Hold volume up power and menu button and when the phone vibrates let go of power only.
Before I do a hard wipe is there any way to get data off the internal memory from recovery mode?
So I got a custom recovery installed, reinstalled stock rom, things worked ok for awhile. Then it started random reboots every 10 mins or so. Now it is back to instant crashing and rebooting. Any idea what could be the issue? I'm assuming at this point it is hardware related. Why can recovery and download mode run consistently without crashing but when an os is fired up it has issues? If it was a hardware issue shouldn't it not work across the board?
So I had Sprint replace my phone on the 8th. I have been using my same batteries (1 stock 1 Anker) and chargers (some stock some not) without issue the past 5 days. I rooted and installed xposed and some modules (original broken phone was never rooted and was completely stock). Things were going great until tonight when it started reboot looping exactly like the old phone. I switched battery and same proble. After I took the battery out and left it out awhile it fired back up but I'm afraid the problem will return. Is it possible that the battery or charger randomly are causing damage to the phone? I only have 14 day warranty on this replacement and need to figure this out.
So things were going well for awhile and then the reboot loops started up again. I did some digging and read that apparently Samsung phones are notorious for sticking power buttons and the symptoms were exactly what I was experiencing. I watched some videos online how to open the phone and clean out the power button but it didn't make a difference. I then read that squeezing the connector for the power button with a pair of pliers sometimes does the trick. Not for me. So finally since I'm not under warranty, have no insurance, and the phone wasn't working anyway, I just ripped the white plastic part of the power button right off. Well, that seemed to do the trick. Phone immediately fired back up without issue and has been going strong. I glued a small thin piece of plastic where the old one used to be and I am back in action. If my little plastic piece solution eventually fails or breaks off I will consider soldering on a new button but so far so good.
If you have tried everything else, and are looking for last resort, try cleaning the power button with some alcohol, and if that fails, rip off that power button! Here is the video that gave me the idea: https://www.youtube.com/watch?v=3Glllc7bEJs and here are some other power button videos: https://www.youtube.com/results?search_query=s4%20power%20button&search_type=&aq=f&oq=
I was sitting on my couch yesterday, and my nexus 10 froze up. This is pretty normal as it freezes up alot and i have to hold the power button down for 10 seconds and restart it. But it went to the bootloader screen and now its stuck in there. I have never rooted my device or have never even attempted to, my device has been stock since day 1. Pushing the RECOVERY MODE, RESTART BOOTLOADER, START buttons do nothing but restart the device into bootloader. I have searched up and down these forums for a solution and cannot find anything, everything thats related with this problem is because of a ROOT, once again i did not root or have ever attempted to root my device. please help. here is a youtube video with the problem. BTW my device is not recognized in windows either.
Edit: so i cant post a video cause im new on the sight. Im really stuck on what to do here.
razrus said:
I was sitting on my couch yesterday, and my nexus 10 froze up. This is pretty normal as it freezes up alot and i have to hold the power button down for 10 seconds and restart it. But it went to the bootloader screen and now its stuck in there. I have never rooted my device or have never even attempted to, my device has been stock since day 1. Pushing the RECOVERY MODE, RESTART BOOTLOADER, START buttons do nothing but restart the device into bootloader. I have searched up and down these forums for a solution and cannot find anything, everything thats related with this problem is because of a ROOT, once again i did not root or have ever attempted to root my device. please help. here is a youtube video with the problem. BTW my device is not recognized in windows either.
Edit: so i cant post a video cause im new on the sight. Im really stuck on what to do here.
Click to expand...
Click to collapse
So if you hold both volume buttons + power button, then select "Recovery Mode" with the power button, it just reboots back to that same exact bootloader screen? You don't see the Android laying on it's back with a red exclamation mark over him?
Sent from my Nexus 6 using Tapatalk
charesa39 said:
So if you hold both volume buttons + power button, then select "Recovery Mode" with the power button, it just reboots back to that same exact bootloader screen? You don't see the Android laying on it's back with a red exclamation mark over him?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I was finally able to get it to a screen by holding the down volume + power that says "downloading do not turn off target nexus 10", but that still did nothing. Thats the only thing that it will let me do besides constantly rebooting to the same bootloader screen, no matter which option i choose.
razrus said:
I was finally able to get it to a screen by holding the down volume + power that says "downloading do not turn off target nexus 10", but that still did nothing. Thats the only thing that it will let me do besides constantly rebooting to the same bootloader screen, no matter which option i choose.
Click to expand...
Click to collapse
That's the Samsung Download Mode, which is different from the bootloader. Could it be possible that your volume button may be stuck, and that's why it keeps bringing you back to the bootloader? I mean, you should at least be able to boot into Recovery Mode. If not, the only solution I can think of is unlocking the bootloader and flashing the factory image. Maybe your partitions got corrupted somehow?
charesa39 said:
That's the Samsung Download Mode, which is different from the bootloader. Could it be possible that your volume button may be stuck, and that's why it keeps bringing you back to the bootloader? I mean, you should at least be able to boot into Recovery Mode. If not, the only solution I can think of is unlocking the bootloader and flashing the factory image. Maybe your partitions got corrupted somehow?
Click to expand...
Click to collapse
I dont think the volume button is stuck, when i select recovery it just restarts and vibrates twice. When i power it off and start it it vibrates once, dont know if that helps. I also remember my battery being below 15% when it froze up. My device has froze up alot since the day i got it, is that normal? maybe it did destroy the partitions.
razrus said:
I dont think the volume button is stuck, when i select recovery it just restarts and vibrates twice. When i power it off and start it it vibrates once, dont know if that helps. I also remember my battery being below 15% when it froze up. My device has froze up alot since the day i got it, is that normal? maybe it did destroy the partitions.
Click to expand...
Click to collapse
Hmm. Well, I can tell you I've never had a freeze up on mine. However, I did only buy mine a year ago, back in April of 2014. So I've pretty much only run KitKat on it before Lollipop now. Also not sure if they made any hardware revisions to get more reliability later in the device life cycle. I also pretty much only use it for media consumption like watching videos, so I'm not really doing any taxing processing tasks on it. It's weird that it vibrates twice when you try to boot into recovery. You mention your battery was low when it locked up. Have you left it charging while powered off for a while?
charesa39 said:
Hmm. Well, I can tell you I've never had a freeze up on mine. However, I did only buy mine a year ago, back in April of 2014. So I've pretty much only run KitKat on it before Lollipop now. Also not sure if they made any hardware revisions to get more reliability later in the device life cycle. I also pretty much only use it for media consumption like watching videos, so I'm not really doing any taxing processing tasks on it. It's weird that it vibrates twice when you try to boot into recovery. You mention your battery was low when it locked up. Have you left it charging while powered off for a while?
Click to expand...
Click to collapse
Really? Never froze? mine would freeze all the time, especially watching youtube videos, i just thought it was normal haha, maybe something was actually wrong with it this whole time. Ive had it for a little over a year now. The battery did die when i left bootloader on over night, but automatically started itself up into bootloader when it had some charge. i might just contact google at this point to see what they say, like i said i never have rooted it or did anything other then normal usage. maybe they can help me.
charesa39 said:
Hmm. Well, I can tell you I've never had a freeze up on mine. However, I did only buy mine a year ago, back in April of 2014. So I've pretty much only run KitKat on it before Lollipop now. Also not sure if they made any hardware revisions to get more reliability later in the device life cycle. I also pretty much only use it for media consumption like watching videos, so I'm not really doing any taxing processing tasks on it. It's weird that it vibrates twice when you try to boot into recovery. You mention your battery was low when it locked up. Have you left it charging while powered off for a while?
Click to expand...
Click to collapse
Really? Never froze? mine would freeze all the time, especially watching youtube videos, i just thought it was normal haha, maybe something was actually wrong with it this whole time. Ive had it for a little over a year now. The battery did die when i left bootloader on over night, but automatically started itself up into bootloader when it had some charge. i might just contact google at this point to see what they say, like i said i never have rooted it or did anything other then normal usage. maybe they can help me.
So I called google and they transfered me to samsung, and samsung transferred me to google. no one seems like they could possibly help me. This is frustrating and i dont think ill buy another nexus tablet, or anything nexus for that matter. i dont even think i can sell this on ebay at this point, and if someone were to be able to get it up and running, all my data might still be on there. ARRRGGGHHH ive never owned something that has "bricked" and not been able to fix it. this one looks hopeless.
razrus said:
So I called google and they transfered me to samsung, and samsung transferred me to google. no one seems like they could possibly help me. This is frustrating and i dont think ill buy another nexus tablet, or anything nexus for that matter. i dont even think i can sell this on ebay at this point, and if someone were to be able to get it up and running, all my data might still be on there. ARRRGGGHHH ive never owned something that has "bricked" and not been able to fix it. this one looks hopeless.
Click to expand...
Click to collapse
That sucks. I can empathize as I (and I'm sure plenty of others) know how it feels to get the runaround. Always frustrating. Well, I am thinking the only shot at possibly getting it working again is to unlock the bootloader and flash a factory image. Chances are always good that with a Nexus (barring any hardware issues), flashing a factory image will get it running again. That's why it's Nexus only for me, as Nexus devices are virtually unbrickable. Not sure if you have any experience with Fastboot and ADB. If not, I'm sure you can find some useful research tools on the interwebs and here on XDA. Once you understand it, here are a couple threads with some simplified installers: http://forum.xda-developers.com/showthread.php?t=2588979 and http://forum.xda-developers.com/showthread.php?t=2317790. Do keep in mind that UNLOCKING THE BOOTLOADER ERASES YOUR DATA, so you will lose everything on your N10. But at this point, it's all about getting it working again so you're not stuck with a $300 paperweight.
charesa39 said:
That sucks. I can empathize as I (and I'm sure plenty of others) know how it feels to get the runaround. Always frustrating. Well, I am thinking the only shot at possibly getting it working again is to unlock the bootloader and flash a factory image. Chances are always good that with a Nexus (barring any hardware issues), flashing a factory image will get it running again. That's why it's Nexus only for me, as Nexus devices are virtually unbrickable. Not sure if you have any experience with Fastboot and ADB. If not, I'm sure you can find some useful research tools on the interwebs and here on XDA. Once you understand it, here are a couple threads with some simplified installers: http://forum.xda-developers.com/showthread.php?t=2588979 and http://forum.xda-developers.com/showthread.php?t=2317790. Do keep in mind that UNLOCKING THE BOOTLOADER ERASES YOUR DATA, so you will lose everything on your N10. But at this point, it's all about getting it working again so you're not stuck with a $300 paperweight.
Click to expand...
Click to collapse
Is it possible to flash even though it's not recognized by windows?
razrus said:
Is it possible to flash even though it's not recognized by windows?
Click to expand...
Click to collapse
It's not recognizing it because you need the drivers so it knows it's connected in bootloader mode.
charesa39 said:
It's not recognizing it because you need the drivers so it knows it's connected in bootloader mode.
Click to expand...
Click to collapse
i have the device up and working now! Thank you so much for you help! I had to unlock my device with the nexus root toolkit after installing that usb fix you suggested, then i had to flash it, but the 5.1 update would get stuck in a bootloop, so i installed 4.4 and it worked. Lost all my data but thats ok. Thanks so much.:highfive:
Edit: Google play was not working, tried updating android software and it got stuck in the bootloop again. will try and tweak it more tomorrow, im gunna look for other custom firmwares as well, dont have to have stock anymore.
razrus said:
i have the device up and working now! Thank you so much for you help! I had to unlock my device with the nexus root toolkit after installing that usb fix you suggested, then i had to flash it, but the 5.1 update would get stuck in a bootloop, so i installed 4.4 and it worked. Lost all my data but thats ok. Thanks so much.:highfive:
Edit: Google play was not working, tried updating android software and it got stuck in the bootloop again. will try and tweak it more tomorrow, im gunna look for other custom firmwares as well, dont have to have stock anymore.
Click to expand...
Click to collapse
That's great to hear. I'm glad it came back to life. :good: Although, I wouldn't suggest using a toolkit. In my experience from what I've seen around these forums, they tend to cause more harm than good. It's good if you understand everything that's going on, and they can prove useful for devices that have really complex unlocking and rooting procedures, but Nexus devices are so easy to unlock and flash manually. I always flash each image file manually so if something goes wrong, I know exactly where it went wrong and how to fix it. The Google Play issue you mentioned is a perfect example. Flashing manually also helped me learn the basics of Fastboot and ADB. So if you want to stay on stock 5.1, I would recommend reflashing the factory image manually. I always use this thread to help me out in case I forget something: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008. Although it's for the Nexus 6, it's the same procedure for the Nexus 5, Nexus 10, Nexus 7, etc. That's the real convenient thing about Nexus devices as well, as they are all pretty much flashed the same way. Should all be really simple since you already have the drivers set up from installing the toolkit. Good luck! And have fun with your newly revived N10.
Hello
This is my first post here and I'd really appreciate advice in this matter.
I've spent the past couple of hours searching for an answer but nothing works or totally irrelevant results.
I have a problem where I'd rooted my phone with KingRoot, changed it to SuperSU successfully (restarted my phone several times since then and no issues)
I installed TWRP (only the app) from the Google Play store and that's as far as I got before I powered off my phone to cool down before attempting any installation of TWRP. Powered on my phone and I can't get past the Samsung logo.
Recovery won't come up, Download mode works but restarts itself and volume buttons do nothing to let me confirm download mode and so it's sending me in a loop. Samsung logo and restart again and again. I insert my battery and the first thing that happens is my phone goes on a mission, determined to power itself on only to Bootloop.
No, before anyone suggests it be a hardware issue, it's a brand new phone. There's nothing wrong with the buttons.
If anyone is going to point out the obvious in saying that I'm responsible for rooting my device, I'm aware of this. The rooting procedure was a one-click method which was successful and caused no boot issues after restarting the phone countless times.
Basically:
Bootloop
Can't access recovery
Can't get to Download mode without it getting back into the bootloop after 5 seconds or so. Volume buttons do nothing to confirm download mode.
USB debugging wasn't enabled before this Bootloop occurred
Do I have a paperweight or is there a way to salvage something from this?
The phone isn't supposed to power itself on after inserting the battery.
This behavior is only acceptable when the phone is plugged in while inserting the battery. But even so, the phone wouldn't try to boot up, it would just display the charging animation.
i had a similar problem where my phone would boot up to the white samsung logo as soon as i insert my battery. tirned out the power button was stuck. try gently knocking the power button onto the corner of a table or something with the battery pulled out. it might work for you if your problem is what i think it is.
GDReaper said:
The phone isn't supposed to power itself on after inserting the battery.
This behavior is only acceptable when the phone is plugged in while inserting the battery. But even so, the phone wouldn't try to boot up, it would just display the charging animation.
Click to expand...
Click to collapse
Thank you for your response but would you like a video to prove that it is in fact attempting to boot up when inserting the battery?
adrxano said:
i had a similar problem where my phone would boot up to the white samsung logo as soon as i insert my battery. tirned out the power button was stuck. try gently knocking the power button onto the corner of a table or something with the battery pulled out. it might work for you if your problem is what i think it is.
Click to expand...
Click to collapse
Oh my god you are amazing thank you so much! Wow. I really appreciate this you've fixed the problem. Thank you!!!
Thanks to all for the time taken to read this and for the responses
Lol it feels great to be helpful.
Sent from my GT-I9500 using Tapatalk
BackShooter said:
Thank you for your response but would you like a video to prove that it is in fact attempting to boot up when inserting the battery?
Click to expand...
Click to collapse
I tested it on my device (I9505) and it doesn't boot up, it just turns on to display the charging animation. If I want it to boot up I have to hold the power button.
So, in conclusion, it must be your power button.
You can say the phone is new as much as you want, but there is a chance it came with a factory defect.
There might also be a possibility it is refurbished phone, which means it is pseudo-new.
GDReaper said:
I tested it on my device (I9505) and it doesn't boot up, it just turns on to display the charging animation. If I want it to boot up I have to hold the power button.
So, in conclusion, it must be your power button.
You can say the phone is new as much as you want, but there is a chance it came with a factory defect.
There might also be a possibility it is refurbished phone, which means it is pseudo-new.
Click to expand...
Click to collapse
You're correct, thank you again I thoroughly appreciate your time and help with this