[Q] Suddenly won't boot, help - Galaxy S I9000 General

I have a Galaxy S as shipped by Bell Canada. It doesn't have the 3 button download mode so I'm staying away from 3rd party roms for now.
It is unlocked and rooted. All has been well until today. I had it off for a while to use the SIM in another phone. When I turned it back on it asked for the SIM unlock code. I Dismissed that and checked the phone, all seemed well other than no SIM activation. I turned it off and removed the SIM and now it won't boot. I get the usual logo, the song, and for a long time the S logo. If I wait long enough it then appears to be off. If I press the back or menu key they will light up but that's it. I can't do anything else other than pull the battery.
I tried the hard reset with holding volume down and tap the power button. That only turns it back on with the same problem. The actual SIM is fine and working in another phone.
Is there anything I can do? If I could hard reset it I'd take it back to the store but I hesitate for now while it still contains my data.

this is a problem i have just posted about a couple of mins ago
but i can get it recovery mode and fatory reset with the vol up, home and power
then it will boot but obviously i have to then reset everything from scratch which is really annoying so anyone got any idea re this

lucky for you that you can get into recovery. Right now I'd be happy with a hard reset, it doesn't take long to rebuild the setup. I'd like to know who decided to remove the recovery mode, that's evil and keeps me from simply resetting the device.

its all the apps re downloading and installing them and resetting up accounts and swype and all that lot need a fix asap
do you know what version of andoid you are running

yes but at least you can get a working phone again, I can't without being able to get into any boot menus. Honestly it only takes 30 minutes to setup again from scratch. I'm on 2.1 and what I find at least on my HTC when it had 2.1 is that I setup the google account, let it sync contacts etc, then from Market Downloads I'll see listed all my apps that were previously installed. As long as I don't leave that screen I can install each app one after the other. Or a proper backup....
Any other magic key combos to reset this thing???

did you try hooking up to kies?

Yes but that does nothing since it never fully boots.

3rdcoast said:
I have a Galaxy S as shipped by Bell Canada. It doesn't have the 3 button download mode so I'm staying away from 3rd party roms for now.
It is unlocked and rooted. All has been well until today. I had it off for a while to use the SIM in another phone. When I turned it back on it asked for the SIM unlock code. I Dismissed that and checked the phone, all seemed well other than no SIM activation. I turned it off and removed the SIM and now it won't boot. I get the usual logo, the song, and for a long time the S logo. If I wait long enough it then appears to be off. If I press the back or menu key they will light up but that's it. I can't do anything else other than pull the battery.
I tried the hard reset with holding volume down and tap the power button. That only turns it back on with the same problem. The actual SIM is fine and working in another phone.
Is there anything I can do? If I could hard reset it I'd take it back to the store but I hesitate for now while it still contains my data.
Click to expand...
Click to collapse
Same thing happened to my phone, but a factory reset did nothing. The internal SD card gave out. Phone is now sent away for 3 - 6 weeks awaiting repair.

my phone did this to me today too, I was just about to post about this when I saw this thread.
So its an SD Card problem? theres no hope of getting it fixed without sending it in?

Yes I think it is the internal card meaning there isn't anything good enough to reset to. I walked the phone over to the store and I'll have to wait for new stock next week. Actually I'm lucky they will exchange it since I bought it outright which apparently is "against policy" even though they list a no contract full price. We'll see how it goes next week but overall I despise the telco industry in this country.

3rdcoast said:
Yes I think it is the internal card meaning there isn't anything good enough to reset to. I walked the phone over to the store and I'll have to wait for new stock next week. Actually I'm lucky they will exchange it since I bought it outright which apparently is "against policy" even though they list a no contract full price. We'll see how it goes next week but overall I despise the telco industry in this country.
Click to expand...
Click to collapse
i went to best buy today to try and exchange it, and apparently they only have a 14 day exchange policy with phones despite it saying 30 day on the receipt, anyhow i phoned samsung and they said i have to go through bell, even though im using the phone on telus, so that should be interesting.

So all the people that are having this problem have the Bell model?
Today i got mine off eBay, as soon a i turned it on, i get exactly the same thing.
It wont load into Android, i see that galaxy S logo and then black screen.
If i go into recovery i see "cant mount SD Card".
The more is search this forum the more i see that all the people with this problem are owners of the Bell i9000M model.
I seriously think they have some defect with the manufacturing line of the phone.
Have you guys installed any firmware on your phone before this happened?
mine is like that out of the box.

Mine is the same Bell model. There seems to be some issues with them which makes the lack of download mode even more dangerous. Right now it doesn't feel like the warranty is going to cover us for problems not our fault. I hope they replace it next week but if it still lacks download mode I'll remain nervous.

Seems like everyone is with the Bell model but my questions is:
Have you guys installed another firmware than the factory one which caused this to happen?
Are you running Stock?
We need to try and narrow this down as i am seeing too many posts about this issue, and they are with the Bell model.

clubtech said:
Seems like everyone is with the Bell model but my questions is:
Have you guys installed another firmware than the factory one which caused this to happen?
Are you running Stock?
We need to try and narrow this down as i am seeing too many posts about this issue, and they are with the Bell model.
Click to expand...
Click to collapse
i put new firmware on it last week, can't remember what it was but it was upgraded through kies so it's one samsung pushed to me, not a froyo unstable one.

bigc_13 said:
i put new firmware on it last week, can't remember what it was but it was upgraded through kies so it's one samsung pushed to me, not a froyo unstable one.
Click to expand...
Click to collapse
Thanks. if it was pushed to you via Kies i assume you were running stock JH2.
So it just stopped booting out of the blue?
To the OP: have you install any firmware on your device before this happened?

clubtech said:
Seems like everyone is with the Bell model but my questions is:
Have you guys installed another firmware than the factory one which caused this to happen?
Are you running Stock?
We need to try and narrow this down as i am seeing too many posts about this issue, and they are with the Bell model.
Click to expand...
Click to collapse
I haven't flashed any 3rd party roms. I did do the official update via Keis which even at the store today they reminded me that I should do the update.. That update seemed to go well and has been working for over a week until I turned it off for an hour. It still isn't clear if the disabled 3 button mode is hardware or software related but we all seem to have that in common too. So before they dismiss the whole thing and we get hosed over technicalities such as unlocking it should be clear that there are clear defects in these phones as far as I can tell.
I want to be comfortable that I'm not left out of hundred of dollars just because I choose to buy it outright and not be tied to contracts. Samsung has to play nicely because it is their phone. Bell has to play nicely because they are bringing them in and distributing to retail. What carrier I use should be irrelevant because the problems are not related to usage.
FYI, the clerks went off for conference to decide if I somehow got the phone against policy. Either they trust my story or I got mine moments before they got the memo about not selling outright.

clubtech said:
Thanks. if it was pushed to you via Kies i assume you were running stock JH2.
So it just stopped booting out of the blue?
To the OP: have you install any firmware on your device before this happened?
Click to expand...
Click to collapse
Same here, stock JH2 from Kies. Not rooted. Boots to Galaxy S logo, then black screen. Mine is sent in for repair... Almost two weeks now.
Seeing more and more of this being posted. There is obviously some issues with this phone.

clubtech said:
Thanks. if it was pushed to you via Kies i assume you were running stock JH2.
So it just stopped booting out of the blue?
To the OP: have you install any firmware on your device before this happened?
Click to expand...
Click to collapse
Our posts crossed..
Yes I believe mine had the JH2, the official keis offered firmware. I was looking forward to the biggie update at the end of the month so wasn't about to risk bricking before then. Irony stepped in anyway.
I'm a bit nervous until I get a new one. At that point if the 3 button mode still doesn't work I'll remain nervous that I'll get another potential brick.
edit-> yes, I simply shut it down for an hour or two to use the SIM in another phone to test that phone. At next boot it died. I knew something was wrong when the logo stayed up for much longer.

I have the 3 buttons enabled so it is not related to the 3buttons being disabled, however when i boot into recovery it clearly displays an error that it can not find the internal SD.
There is definitely something wrong with the Bell Galaxy S corrupting itself.
I bought mine from an eBay seller, he is saying the phone booted fine when he shipped it but when i opened the box today i only got this black screen after logo.
Gladly the seller will take it back.
Maybe this is why there are shortages everywhere in Canada. I hope the caught this up and are fixing it with the new batch.

Related

[Q] Which Lag Fix/Root/Firmware work for the Bell Vibrant?

I swapped my Vibrant out at BestBuy with one that has Download/Recovery mode, so its now time to play.
Which lag fix and root procedures work with the Bell Vibrant? Also which Firmware is compatible?
AllGamer...since you seem to be the "guy" to talk to about the Bell Vibrant, do you want to start a sticky thread, one that lays out which fixes/root/firmwares are compatible with our phone?
i will be buying a Bell Vibrant very soon, so i just wan to know how can you tell it has the recovery feature?
Hold down Home+VolumeDown+Power. It will boot up into a screen with a yellow yield sign and say "Download mode".
Mine doesn't have it so im going back to exchange.
Sent from my GT-I9000M using XDA App
Want to hear a funny story?
I was in my Bell store today, seeing if they had any accessories in for the Vibrant yet. My sales rep was there, and we started talking about the device, unlocking, modding, etc.
He mentioned they had five returns since Monday regarding the download and recovery mode issue they swapped out on the DOA plan. Guess there's a lot of modders in the downtown Vancouver area.
I asked him if they still had any of those returns, he said yep, they had all of them, they hadn't been processed out of the store yet. He brought a couple out, and I fired them up, did the download keypress and fired them up. Repeated this process for four working phones in total, the fifth was well and truly dead.
Guess what?
EVERY SINGLE ONE OF THEM WENT INTO DOWNLOAD MODE.
EVERY
SINGLE
ONE
So did all the demonstration models.
I'll leave it to you to figure out the moral of this story.
Croak said:
Want to hear a funny story?
I was in my Bell store today, seeing if they had any accessories in for the Vibrant yet. My sales rep was there, and we started talking about the device, unlocking, modding, etc.
He mentioned they had five returns since Monday regarding the download and recovery mode issue they swapped out on the DOA plan. Guess there's a lot of modders in the downtown Vancouver area.
I asked him if they still had any of those returns, he said yep, they had all of them, they hadn't been processed out of the store yet. He brought a couple out, and I fired them up, did the download keypress and fired them up. Repeated this process for four working phones in total, the fifth was well and truly dead.
Guess what?
EVERY SINGLE ONE OF THEM WENT INTO DOWNLOAD MODE.
EVERY
SINGLE
ONE
So did all the demonstration models.
I'll leave it to you to figure out the moral of this story.
Click to expand...
Click to collapse
Maybe some people don't know how to do it properly, but when I was bringing my SGS in for replacement, I had no problems popping the demo phone into recovery and download modes Just wouldn't work with mine and the one they let me try out of the box. Ended up heading to Future Shop and couldn't get either of their 2 available phones to work.
Hopefully local stores have got another batch in stock.
DarthV said:
Maybe some people don't know how to do it properly, but when I was bringing my SGS in for replacement, I had no problems popping the demo phone into recovery and download modes Just wouldn't work with mine and the one they let me try out of the box. Ended up heading to Future Shop and couldn't get either of their 2 available phones to work.
Hopefully local stores have got another batch in stock.
Click to expand...
Click to collapse
what is the exact process to initiate the bootloader mode?
aquenne said:
what is the exact process to initiate the bootloader mode?
Click to expand...
Click to collapse
Pwr+Home+Vol- for download, switch vol+ and vol- for recovery. Power on with all 3 kept pressed, then let go of the pwr button before it loops another reboot. Or at least that's how I did it.
It took me a few tries to get it to work.
Now I don't have a problem.
I'm sure all those returns will simply go into the exchange pile.
This phone is freaking sweet !
DarthV said:
Pwr+Home+Vol- for download, switch vol+ and vol- for recovery. Power on with all 3 kept pressed, then let go of the pwr button before it loops another reboot. Or at least that's how I did it.
Click to expand...
Click to collapse
Ah i see. mine is working.
Coming from an HTC Touch, the key difference is you could initiate the bootloader mode WHILE the phone was running. This process requires the phone to first be off.
there are 2 topics in the Dev section with the undate.zip to root your phone
http://forum.xda-developers.com/showthread.php?t=748131
arr0ww said:
I swapped my Vibrant out at BestBuy with one that has Download/Recovery mode, so its now time to play.
Which lag fix and root procedures work with the Bell Vibrant? Also which Firmware is compatible?
AllGamer...since you seem to be the "guy" to talk to about the Bell Vibrant, do you want to start a sticky thread, one that lays out which fixes/root/firmwares are compatible with our phone?
Click to expand...
Click to collapse
Talking about how to activate the recovery/download thing. What I read (and what worked for me) was when the samsung logo appears on screen, let go of the power button for like half a second then hold it again. Worked flawlessly for me!
I rooted mine in-store while waiting for the paperwork to be finished.
AllGamer said:
there are 2 topics in the Dev section with the undate.zip to root your phone
http://forum.xda-developers.com/showthread.php?t=748131
Click to expand...
Click to collapse
I just rooted and installed the "OneClick Lag Fix 2-3. 2181 Quadrant score...holy crap this thing flies now!!!
Bell vibrant doesnt have recovery mode any suggestions???
Hi guys I think im writing in the right section. I just got an unlocked bell vibrant and cant enter recovery mode can anyone suggest a solution I cant stand this Lag!
mariotenuta said:
Hi guys I think im writing in the right section. I just got an unlocked bell vibrant and cant enter recovery mode can anyone suggest a solution I cant stand this Lag!
Click to expand...
Click to collapse
you should have opened a new topic, instead of lapping onto another one.
lag fix has nothing to do with the recovery mode
you can install the lag fix without being able to get into recovery mode
does that answer your question?

Random boot loop, can't get anywhere in recovery

I was on the latest CM13 nightly (was waiting a bit to go to 14.1) So I went to bed last night and my phone did a reboot as I was setting my alarm. Didn't think too much of it, crap happens. I waited for it to come back fully into the OS, which it did, checked my alarm. Noticed something strange I got the CM Updater notification in the statusbar ("There are new updates available" - CM14.1-12-02 or something), which I thought was weird that's the first time it's said that, and I've checked the CM Updater before and since the 14.1 switch there's been nothing there. As it should, I imagine, not try to update major versions like that. Anyways I dismissed it and went to bed (this entire thing is PROBABLY entirely unrelated, but I found it's timing interesting at least).
Woke up a few hours later to my phone getting really hot, and stuck in an infinite boot loop. It never gets passed the first Google screen. If I let it go it'll sit there for several minutes and maybe reboot. I was able to get into the bootloader, choosing Boot Recovery though sends me back to the Google bootup screen where it never progresses, doesnt have the blue text in the top that says booting into recovery..
Was able to get into the phone with fastboot so I tried flashing the latest recovery I had installed TWRP-3.0.2-2-angler. Still wouldn't boot into it, sometimes it would get to the TWRP recovery loading page, and then sit there for a couple minutes, then reboot.Tried flashing it a few times with fastboot with no success.
Erased userdata with fastboot, then did a full factory reflash of several images, MDB081 - MTC20l (factory images I know I've used in the past to recover, had them saved). Rebooted and I still can't get into the OS (stuck at first Google logo). Interesting the stock recovery though loads.
Flash an older TWRP recovery I had saved twrp-2.8.7.2-angler . Was able to get into recovery finally - kind of. Sometimes it still locks up and wont let me swipe to enter TWRP. The first time it let me in it asked me for my decryption password - I didn't have a password - had a swipe and fingerprint setup only. Got in again and first thing I tried doing honestly is erasing (formating) all my data, thinking if I'm going to have to warranty this phone or sell it broken, I want to make sure my data is wiped. Also I figure after that I can try to reinstall CM etc like I would a completely fresh build. It complained about not being able to mount the partition and locked up in TWRP then eventually auto rebooted. Got in again and tried to do a basic wipe, it said it cant find /sdcard then said it wiped, and then froze, auto rebooted again after a few seconds.
To note : All fastboot commands seem to execute with "OKAY" status, no errors reported anywhere, it always finds the device too.
I can't seem to get anywhere with this phone. Everything I try to do in recovery is met with freezes and reboots. It seems like maybe the internal emmc has taken a dump.
Problem is I'm literally 3 days out of the 1 year warranty from when I received my phone, and having tried to work with Huawei support previously, I'm 100% certain they won't help. I came across a few threads on here similar to mine recently without any real resolution other then RMA'ing it. I figured I'd post here for a last desperate attempt if anyone has any other suggestions, because I don't know what I'll do. The Pixel XL is ungodly expensive, and conveniently out of stock. And I don't think I could talk myself into buying another Huawei anytime soon after this.
Any suggestions?
the.root said:
I was on the latest CM13 nightly (was waiting a bit to go to 14.1) So I went to bed last night and my phone did a reboot as I was setting my alarm. Didn't think too much of it, crap happens. I waited for it to come back fully into the OS, which it did, checked my alarm. Noticed something strange I got the CM Updater notification in the statusbar ("There are new updates available" - CM14.1-12-02 or something), which I thought was weird that's the first time it's said that, and I've checked the CM Updater before and since the 14.1 switch there's been nothing there. As it should, I imagine, not try to update major versions like that. Anyways I dismissed it and went to bed (this entire thing is PROBABLY entirely unrelated, but I found it's timing interesting at least).
Woke up a few hours later to my phone getting really hot, and stuck in an infinite boot loop. It never gets passed the first Google screen. If I let it go it'll sit there for several minutes and maybe reboot. I was able to get into the bootloader, choosing Boot Recovery though sends me back to the Google bootup screen where it never progresses, doesnt have the blue text in the top that says booting into recovery..
Was able to get into the phone with fastboot so I tried flashing the latest recovery I had installed TWRP-3.0.2-2-angler. Still wouldn't boot into it, sometimes it would get to the TWRP recovery loading page, and then sit there for a couple minutes, then reboot.Tried flashing it a few times with fastboot with no success.
Erased userdata with fastboot, then did a full factory reflash of several images, MDB081 - MTC20l (factory images I know I've used in the past to recover, had them saved). Rebooted and I still can't get into the OS (stuck at first Google logo). Interesting the stock recovery though loads.
Flash an older TWRP recovery I had saved twrp-2.8.7.2-angler . Was able to get into recovery finally - kind of. Sometimes it still locks up and wont let me swipe to enter TWRP. The first time it let me in it asked me for my decryption password - I didn't have a password - had a swipe and fingerprint setup only. Got in again and first thing I tried doing honestly is erasing (formating) all my data, thinking if I'm going to have to warranty this phone or sell it broken, I want to make sure my data is wiped. Also I figure after that I can try to reinstall CM etc like I would a completely fresh build. It complained about not being able to mount the partition and locked up in TWRP then eventually auto rebooted. Got in again and tried to do a basic wipe, it said it cant find /sdcard then said it wiped, and then froze, auto rebooted again after a few seconds.
To note : All fastboot commands seem to execute with "OKAY" status, no errors reported anywhere, it always finds the device too.
I can't seem to get anywhere with this phone. Everything I try to do in recovery is met with freezes and reboots. It seems like maybe the internal emmc has taken a dump.
Problem is I'm literally 3 days out of the 1 year warranty from when I received my phone, and having tried to work with Huawei support previously, I'm 100% certain they won't help. I came across a few threads on here similar to mine recently without any real resolution other then RMA'ing it. I figured I'd post here for a last desperate attempt if anyone has any other suggestions, because I don't know what I'll do. The Pixel XL is ungodly expensive, and conveniently out of stock. And I don't think I could talk myself into buying another Huawei anytime soon after this.
Any suggestions?
Click to expand...
Click to collapse
It's an ongoing thing with these 6P's and 5X's. Some have been able to fully recover and others like myself were not. Here is a guide that might be able to help you if you haven't come across it yet. Good luck..
http://forum.xda-developers.com/android/help/guide-revive-angler-bootloop-t3454938/page6
Check Warranty Status:
http://consumer.huawei.com/us/support/warranty-query/index.htm
BIGSAMDA1ST said:
It's an ongoing thing with these 6P's and 5X's. Some have been able to fully recover and others like myself were not. Here is a guide that might be able to help you if you haven't come across it yet. Good luck..
http://forum.xda-developers.com/android/help/guide-revive-angler-bootloop-t3454938/page6
Check Warranty Status:
http://consumer.huawei.com/us/support/warranty-query/index.htm
Click to expand...
Click to collapse
Thanks. I came across that. I tried flashing MMB29P as well as several other factory images without success. My problem now it seems no matter what I flash I cannot get back into recovery anymore. Even if it's stock or if it's TWRP (any version - including 3.0.2.0 as they suggest), so I don't really get passed step 4-5 in that guide. I guess she only had so many reads left in her, sigh.
WEIRD @ warranty link. It says from my S/N that it's valid until 2017-02-17. I don't know how, I purchased it 2015-10-22, it shipped 2015-11-24, and I got it 2015-11-30. Unsure how/why that would've gotten extended until February. I'm concerned they'll get it back then deny it once they figure that out, or figure out it's been unlocked/flashed. When I first got the phone i had issues with it charging, I narrowed it down to the USB C->C cable being faulty, and contacted Huawei. They absolutely refused to replace just the cable. Said I had to ship the whole phone back and it'd take AT LEAST 3-4 weeks to get it back. I argued with several people on the phone there (their support 100% refuses to give you their name or transfer to their supervisors btw), and finally asked google support to pull some strings and get in contact with someone there to replace a simple freaking cable - no one cared at all - spent several hours trying and got nowhere. I'm /done with Huawei. I think my best bet is to probably find out how well that American Express extended warranty claim works, I've never actually had to use it before. IDK what I'll do after that. Sad this is a common problem with these phones exactly one year out, so even if I wanted to buy a used one on eBay I'd risk the same thing shortly thereafter.
I'll keep the phone powered off for a while and try some more flashing later see if I can get back into recovery to try the rest of his steps in that article. It's not looking promising anymore.
Well being that it's a known issue, like I said, I myself ran into this fiasco, had phone rooted and running custom rom. I myself couldn't get into recovery but was able to flash all factory images and relock bootloader manually. I then called Huawei and played dumb telling them that I had updated my phone to the latest firmware via OTA and then it went into bootloop. They never asked if it was unlocked and I never volunteered to tell them either. I had bought my 6P through Best Buy and still had receipt Incase they'd asked for it which they didn't. All they did was ask for IMEI # along with Ser # and verified that it was still under warranty, then they emailed me a return label. I shipped phone to them and in a matter of like a week or so I had a brand new device in hand. Build date on it was August, 16, 2016. So far running good but let's see for how long.
BIGSAMDA1ST said:
Well being that it's a known issue, like I said, I myself ran into this fiasco, had phone rooted and running custom rom. I myself couldn't get into recovery but was able to flash all factory images and relock bootloader manually. I then called Huawei and played dumb telling them that I had updated my phone to the latest firmware via OTA and then it went into bootloop. They never asked if it was unlocked and I never volunteered to tell them either. I had bought my 6P through Best Buy and still had receipt Incase they'd asked for it which they didn't. All they did was ask for IMEI # along with Ser # and verified that it was still under warranty, then they emailed me a return label. I shipped phone to them and in a matter of like a week or so I had a brand new device in hand. Build date on it was August, 16, 2016. So far running good but let's see for how long.
Click to expand...
Click to collapse
Hmm interesting. Maybe their US support has improved since last year. So it was brand new not refurbished? Did you get the full retail box set? I bought mine directly through Huawei, so I would like to think that they would have accurate warranty data, but perhaps not. I will consider RMA'ing it to them if it's really a new one. It's either that or a 550$ refund from my credit card company. I haven't tried fastboot lock yet, will do that when I give up on all else lol (and need to return it), but hopefully that will work if the rest of the emmc is hosed.
Yeah, mine came in a new box, sealed like day one. I was surprised thought I'd be getting a refurbished device but I can honestly say it was a brand new one. And I don't blame you on trying to get the device to a working state. I tried everything and it's mother before giving up and finally relocking bootloader and sending it in.
BIGSAMDA1ST said:
Yeah, mine came in a new box, sealed like day one. I was surprised thought I'd be getting a refurbished device but I can honestly say it was a brand new one. And I don't blame you on trying to get the device to a working state. I tried everything and it's mother before giving up and finally relocking bootloader and sending it in.
Click to expand...
Click to collapse
Just called them. They won't accept it back without a proof of purchase. I have to send in the proof of purchase before they'll approve the RMA and then I get the shipping label/information. And "they can't look it up by S/N, doesn't matter if the website says it's in warranty". LOL. Sounds about right from what I remember of their support. They say their website is inaccurate, and cant ever verify/lookup that I bought the product directly from them. Maybe I'll try back tomorrow to see if someone else will help but it's unlikely from the sounds of it. She did say this is very common problem however, knew all about it.
Damn, That truly sucks..I would definitely give them a call again and see if I get a different rep. I was lucky with the one I got, he basically knew it was an ongoing thing and really didn't give me a hard time. He didn't even ask for a receipt, about the only thing he asked was that if the bootloader was locked or unlocked and when I told him it was locked, he then proceeded with the RMA procedure.
BIGSAMDA1ST said:
Damn, That truly sucks..I would definitely give them a call again and see if I get a different rep. I was lucky with the one I got, he basically knew it was an ongoing thing and really didn't give me a hard time. He didn't even ask for a receipt, about the only thing he asked was that if the bootloader was locked or unlocked and when I told him it was locked, he then proceeded with the RMA procedure.
Click to expand...
Click to collapse
Yeah I played dumb and all, didn't help. She didn't ask me any real questions she was convinced of the problem just from my description. She also said it's 12 months from the date I purchased it and not when I received it in the mail (so since they took 5-6 weeks to get it to me - preorder madness - I don't get that time back in the warranty) lol. Not like it matters now, just to further comment on how crappy their support/warranty is (in my experience).
I'll follow up if I have any more luck unbricking the device or warrantying it for that matter.
Good luck on either with the warranty or bringing it back to life.
I also have problems such as your support Huawei says four weeks of waiting
Got a recovery image to boot finally (after like 10x attempts at flashing one). Tried doing the nandroid backup as that guide suggests, says it cannot find/mount /sdcard and freezes/reboots. Tried going into wipe -> advanced and repairing internal storage and data and it was an invalid partition or something. Tried repairing system and it locked up again. Tried formatting them with fastboot and didn't work. Tried installing the latest 7.0 factory image for the hell of it, nadda. Relocked the bootloader successfully. Giving up. Filed an claim online with my credit card company (most do a +1 year extended warranty), we'll see how that goes, if I get lucky they'll approve the claim and let me keep the phone. May pick up a used 5x or something.
the.root said:
Got a recovery image to boot finally (after like 10x attempts at flashing one). Tried doing the nandroid backup as that guide suggests, says it cannot find/mount /sdcard and freezes/reboots. Tried going into wipe -> advanced and repairing internal storage and data and it was an invalid partition or something. Tried repairing system and it locked up again. Tried formatting them with fastboot and didn't work. Tried installing the latest 7.0 factory image for the hell of it, nadda. Relocked the bootloader successfully. Giving up. Filed an claim online with my credit card company (most do a +1 year extended warranty), we'll see how that goes, if I get lucky they'll approve the claim and let me keep the phone. May pick up a used 5x or something.
Click to expand...
Click to collapse
I would stay away from the 5X as well..lol They are going through the same thing the 6P is going through. It's all over Reddit and XDA as well. I'm currently using the 6P but I'm waiting on the One Plus 3T to arrive. I have a few other devices to play with but I'm still using the 6P waiting for the 7.1.1 update to drop in a few days to see how that goes.
BIGSAMDA1ST said:
I would stay away from the 5X as well..lol They are going through the same thing the 6P is going through. It's all over Reddit and XDA as well. I'm currently using the 6P but I'm waiting on the One Plus 3T to arrive. I have a few other devices to play with but I'm still using the 6P waiting for the 7.1.1 update to drop in a few days to see how that goes.
Click to expand...
Click to collapse
Oh what the **** . That sucks. My wife owns a 6P and my son has a 5x. So our house is a ticking time bomb of failure. Maybe I'll buy a Note 7 and finish the job. I have my old Nexus One and Tmobile G1, both still power on last time I checked. I've gotten rid of all other past cell phones we've had unfortunately. Used to have so much trust in the Nexus lineup
the.root said:
Oh what the **** . That sucks. My wife owns a 6P and my son has a 5x. So our house is a ticking time bomb of failure. Maybe I'll buy a Note 7 and finish the job. I have my old Nexus One and Tmobile G1, both still power on last time I checked. I've gotten rid of all other past cell phones we've had unfortunately. Used to have so much trust in the Nexus lineup
Click to expand...
Click to collapse
Lmao.. Yeah I would stay away. Also you have to throw in the fact that the devices only have support until at least Sept. of 2017, then unless you're flashing custom roms your basically stuck.
BIGSAMDA1ST said:
Lmao.. Yeah I would stay away. Also you have to throw in the fact that the devices only have support until at least Sept. of 2017, then unless you're flashing custom roms your basically stuck.
Click to expand...
Click to collapse
Yeah I mean I've always liked the Nexus devices because they always seem to have a good strong developer/modding community. I don't know the definition of a stock - anything. I recently converted my wife & son over to Nexus from Samsung's because I got frustrated with how they now lock down their phones. I have no doubt the 6P/5x (if they survive that long lol) will still be one of primary devices in this community to receive new OS/etc (cyanogenmod/whatever) well past the September EOL. Just look at the older Nexus phones still some of the first to receive the CM14.1 builds.
the.root said:
Yeah I mean I've always liked the Nexus devices because they always seem to have a good strong developer/modding community. I don't know the definition of a stock - anything. I recently converted my wife & son over to Nexus from Samsung's because I got frustrated with how they now lock down their phones. I have no doubt the 6P/5x (if they survive that long lol) will still be one of primary devices in this community to receive new OS/etc (cyanogenmod/whatever) well past the September EOL. Just look at the older Nexus phones still some of the first to receive the CM14.1 builds.
Click to expand...
Click to collapse
Exactly.. That's why I'm still keeping mine and hoping it doesn't decide to go on the fritz again.

Note 4 wont turn on, "cannot boot normal" and "downlaoding target, dont turn off"

Note 4 wont turn on, "cannot boot normal" and "downlaoding target, dont turn off"
Its a Note 4 SM-N910F, Android 6.0.1, BB N910FXXU1DPE2, kernel 3.10.40-7733605 [email protected] #1
i feel I have tried everything... History:
Phone has been working fine for a year, upgraded to 6.0.1 no problems about 2 or 3 months ago. no new apps installed. Last week it started getting very laggy, keyboard strokes took for ever to register. I thought, ok, time to to a factory reset to blow out any old cobwebs. Did it via the menu. However the phone froze midway thought. I left it for an hour and then pulled out the battery. I popped it back in and it performed the reset without me having to press anything. Cool, thats good I thought.
Now I was going to change the battery, so I powered off as normal and put my other 2 week old original samsung battery in, and it would not power on. After a few reinsertions it powered back on. I though i have to do another reset. So I tried, and it would not reset. It just died. I cant restart the phone, it dies. If I shut it down normally. it wont turn on back on, I have to take out and reinsert the battery multiple times, holding down the powerbutton between to discharge. this can take up to 10 tries now. Sometimes it will go th the unable to bot in normal mode and "downloading , do not turn of target, but it will stay there for ever, more than an hour.
Every 15-20 tries it would turn on, let me get in via pin, only to start freezing up within a min, and then die again. Somewhere I read that a guy hada similar problem, and he used wakelock and that worked, on level 4. I managed to download that and used it, and hey presto, it works!
Now I had to power down the phone for a reason, and it took me about 30 min of battery and powerbuttonholding before it managed to boot up, and I was quick enough to start wakelock on level 4.
It wont boot in to safe mode, it wont boot in to recovery mode, it wont boot in to the factory reset mode. Its the same with either battery, and different cables.
Any ideas what i can do here, or what could be wrong? I havent gotten it wet or banged it.
I am having the same exact issue on a N910A. Phone was functioning correctly and in December it started getting really laggy. Performed various resets, purchased new battery. Still laggy. Up until two weeks ago the phone was slow but now it will not power on . The phone will not charge as well.
Mine did same, 6 months old, not rooted stock firmware. Locked up yesterday, couldn't do anything. Pulled battery and restarted. Samsung logo comes on screen goes black for android boot then it hangs with blue led flashing. Nothing I do gets it past that point. Tried safe boot but it doesn't fully launch with correct button combo and volume up. In the end I re-installed firmware using Keis. All went well, everything as per youtube tutorial. Except one thing, at end of download phone didn't re-start. Still can't get it to boot, any ideas?
Edit: Lock up didn't coincide with any new apps being loaded or updates of existing. Only change was a week ago which was an automatic update of the stock firmware (Lollipop)
armstrongracer said:
Mine did same, 6 months old, not rooted stock firmware. Locked up yesterday, couldn't do anything. Pulled battery and restarted. Samsung logo comes on screen goes black for android boot then it hangs with blue led flashing. Nothing I do gets it past that point. Tried safe boot but it doesn't fully launch with correct button combo and volume up. In the end I re-installed firmware using Keis. All went well, everything as per youtube tutorial. Except one thing, at end of download phone didn't re-start. Still can't get it to boot, any ideas?
Edit: Lock up didn't coincide with any new apps being loaded or updates of existing. Only change was a week ago which was an automatic update of the stock firmware (Lollipop)
Click to expand...
Click to collapse
are you still under warranty? i sent mine to a samsung center, the guy recognized the problem as the motherboard, said I wasnt the first. That was 3 weeks ago, they are STILL waiting for the parts. They say the Samsung factory are way behind with repair parts, etc etc. I am hoping it will go under warranty. Ill update when I know!
I've been having the same problem that started yesterday morning. I've tried a few different solutions but nothings worked, I get the feeling that my phone is dead and I'm not in warranty either. I'm going to approach Samsung but my guess is they will want more than the phone is worth to repair it. I've read about so many people having the same issues, its horrendous engineering on Samsungs part considering how much their phones cost to start with
neils0911 said:
I'm going to approach Samsung but my guess is they will want more than the phone is worth to repair it. I've read about so many people having the same issues, its horrendous engineering on Samsungs part considering how much their phones cost to start with
Click to expand...
Click to collapse
Your guess is probably correct and I totally agree with you. I seriously think manufacturers do not want their devices to be problem free for more than two years. Probably why they have stopped making phones with batteries that simply pop out.
bonfilet said:
Your guess is probably correct and I totally agree with you. I seriously think manufacturers do not want their devices to be problem free for more than two years. Probably why they have stopped making phones with batteries that simply pop out.
Click to expand...
Click to collapse
Definitely...surely it couldn't have been that hard to make a device with a battery that was still removable on the newer phones. It's frightening how many forum posts I've found with people having their phones just brick out of nowhere (and that's just the note 4). I've given up trying to fix mine, I've tried every method I could find and nothings worked. I can only assume that this problem is simply the motherboard of the phone not working anymore. I'm not even sure what phone to buy now but it certainly won't be a Samsung.
neils0911 said:
. I'm not even sure what phone to buy now but it certainly won't be a Samsung.
Click to expand...
Click to collapse
If you do not care about the camera thera are a lot of rather affordable options which can be tossed in the bin when they start malfunctioning and if their warranty has run out. If you care about the camera being as good as the Note 4's than the range of phones you can buy is quite limited.
mymigi said:
I am having the same exact issue on a N910A. Phone was functioning correctly and in December it started getting really laggy. Performed various resets, purchased new battery. Still laggy. Up until two weeks ago the phone was slow but now it will not power on . The phone will not charge as well.
Click to expand...
Click to collapse
If you are able to boot it into Download Mode then you should Download Stock Rom file for Galaxy Note 4 from Sammobile and Flash it through Odin..
Everything will be OK... ?
Unfortunately, SAMMOBILE does not have the SM-N910A firmware.
mymigi said:
Unfortunately, SAMMOBILE does not have the SM-N910A firmware.
Click to expand...
Click to collapse
You can find here firmware for N910A , 5.1.1 and 6.0.1 : https://simunlockremote.com/firmware-support/
bonfilet said:
If you do not care about the camera thera are a lot of rather affordable options which can be tossed in the bin when they start malfunctioning and if their warranty has run out. If you care about the camera being as good as the Note 4's than the range of phones you can buy is quite limited.
Click to expand...
Click to collapse
I think the camera on the note 4 is absolutley terrible. I might even go so far as to say the pictures are unusable. the applied noise reduction renders everything splotchy, colors are off and its not sharp at all. and Im not talking dark conditions here.
Anyway, my phone was repaired under warranty and is back to working as it should. It was indeed the motherboard, so if you have the same troubles I had, those are your best bets.
I don't think replacement via warranty will be available. I will attempt to power into download mode and verify if I can get it back up and running. If not, a good ole paperweight.
mymigi said:
Unfortunately, SAMMOBILE does not have the SM-N910A firmware.
Click to expand...
Click to collapse
You can download the Firmware from here ..
https://www.androidfilehost.com/?fid=24459283995298017
---------- Post added at 05:43 AM ---------- Previous post was at 05:41 AM ----------
mymigi said:
Unfortunately, SAMMOBILE does not have the SM-N910A firmware.
Click to expand...
Click to collapse
You can download the Firmware from here. .
https://www.androidfilehost.com/?fid=24459283995298017
Sounds like the problems I have: with my first N910F: started with lagging apps / freezing, then random reboots now and then, eventually giving error messages when booting. Finally, now it will only start after the battery has been out for at least 30 minutes, but hangs on error message. When pulling battery out and putting back in it, wont give a single sign of life. Since I was just out of warranty it has been lying around, and I bought a second hand N910F for replacement, sadly its starting to give the same errors too and is just out of warranty too (its currently still working, but with freezes / reboots / and already a event with boot error).
I read It could be memory chips or some power chip on the motherboard, appears to be a common problem. So.... Last month I bought a new motherboard on ebay (chinese delivery, 80€). Received it last week and put it back in; phone is back to life. (putting it in is a very simple task, with iFixit teardown / guide)
Anyway, I love the Note 4 for performance / size / looks, and have been Samsung fan for a while, but this recent breakdowns and information that it is fairly common, has diminished being a fan fairly quickly and I guess the Note 4 will be the last Samsung device for a while after this new motherboard breaks down as well
onno72 said:
Sounds like the problems I have: with my first N910F: started with lagging apps / freezing, then random reboots now and then, eventually giving error messages when booting. Finally, now it will only start after the battery has been out for at least 30 minutes, but hangs on error message. When pulling battery out and putting back in it, wont give a single sign of life. Since I was just out of warranty it has been lying around, and I bought a second hand N910F for replacement, sadly its starting to give the same errors too and is just out of warranty too (its currently still working, but with freezes / reboots / and already a event with boot error).
I read It could be memory chips or some power chip on the motherboard, appears to be a common problem. So.... Last month I bought a new motherboard on ebay (chinese delivery, 80€). Received it last week and put it back in; phone is back to life. (putting it in is a very simple task, with iFixit teardown / guide)
Anyway, I love the Note 4 for performance / size / looks, and have been Samsung fan for a while, but this recent breakdowns and information that it is fairly common, has diminished being a fan fairly quickly and I guess the Note 4 will be the last Samsung device for a while after this new motherboard breaks down as well
Click to expand...
Click to collapse
My phone is also random Rebooting
It also shuts down at 25% of battery remaining, Have you also faced similar issue?
Download the app "Wake Lock" and run the Partial Wake Lock option. Apparently the updated software impacts the CPU. For the restarting issue, put it in the freezer for a couple minutes. You may have to take the battery out once, but it has worked for me every time.
This looks very much like the issue reported here:
https://forum.xda-developers.com/no...-error-fix-t3434335/post72944466#post72944466
There are temporary fixes (wakelock), but ultimately this is a harware issue, and the fix is a new motherboard.
I think that underlying it is a problem with heat affecting the eMMC chip or its connection to the motherboard.
See also:
https://us.community.samsung.com/t5...ePhones/thread-id/12183/highlight/true/page/1
http://www.classlawdc.com/2017/04/25/investigation-samsung-galaxy-note-4-mmc_read-failed-defect/
Hey can u pls get me the stock firmware for n910gddu1dpb4
You might find this interesting. Since I couldn't get mine to power up at all, I called Samsung tech and they quoted me $75 to fix it and they would pay for shipping. I figured it was better then getting another phone off Swappa. 2-3 weeks later i get an email that they are repairing it under warranty at no cost to me. I got a refurbished phone since i know my IEMI number was different. they didn't explain why. Anyway, I got lucky i guess.

Bricked/randomly shuts off

Hello everyone! So my problem aroused a few days ago when I noticed my phone would randomly reboot and get stuck on the boot screen. I would have to mess around and finally only to get a few minutes of usage. I had King Rom installed which I believe was the issue. Fortunately, while trying to use Odin to recovery to stock, it shuts off in the middle of recovery mode. Now I am getting the screen that says: an error has occurred while updating the device software. please use the emergency recovery function in the smart switch pc software. I have been up all night trying to fix this with no results. I am so upset because I rely on my phone for my job as I am a delivery driver. I can't afford a new phone right now and I don't know what to do. It seems like I am pretty much SOL. I am hoping someone will be able to help me! Thanks so much
Somehow I was actually able to restore it to stock successfully in Odin. But before it will finish the initiation process it reboots over and over and the issue persists. Could there be another factor as to why this has happened?
slimspittle said:
Somehow I was actually able to restore it to stock successfully in Odin. But before it will finish the initiation process it reboots over and over and the issue persists. Could there be another factor as to why this has happened?
Click to expand...
Click to collapse
Well, if you're unlucky it might as well be a hardware related failure.
If you look through XDA, there are more and more people having the boot loop problem right now (me included).
Especially after the latest December FW update.
I would try to do a emergency restore through SmartSwitch, then factory reset.
That's the last thing I tried, although it didn't help me in the end and now my mobile is back at Samsung for repair.
If it still bootloops after these steps I think you're out of luck and have to contact a Samsung repair center.
slimspittle said:
aroused
Click to expand...
Click to collapse
Arose is the word i think you were looking for!!
MisterKanister said:
Well, if you're unlucky it might as well be a hardware related failure.
If you look through XDA, there are more and more people having the boot loop problem right now (me included).
Especially after the latest December FW update.
I would try to do a emergency restore through SmartSwitch, then factory reset.
That's the last thing I tried, although it didn't help me in the end and now my mobile is back at Samsung for repair.
If it still bootloops after these steps I think you're out of luck and have to contact a Samsung repair center.
Click to expand...
Click to collapse
Well my phone is the International from Kenya and I'm not sure if Samsung will honor the warranty. I am able to get to the point where you add your Google account. From that point, it gets stuck at ''just a sec''. From that point, it starts to freeze. I guess somehow the phone is still messed up. Think I should try flashing it again?
Do you have TWRP or any custom recovery, does it freeze when your in that menu? Do you have an external SD inside?
dude9946 said:
Do you have TWRP or any custom recovery, does it freeze when your in that menu? Do you have an external SD inside?
Click to expand...
Click to collapse
No I do not anymore and it freezes when the firmware has loaded and it says optimizing apps. And yes I do have a an SD Card
Long shot... have you tired booting up the phone without the card in? It's really sounding like a hardware problem, maybe GPU if it gets triggered reliably...
dude9946 said:
Long shot... have you tired booting up the phone without the card in? It's really sounding like a hardware problem, maybe GPU if it gets triggered reliably...
Click to expand...
Click to collapse
So this time I actually retried Odin with stock restored from a different website. Then bypassed adding a google account. From that point, I no longer got to the ''just a sec'' screen. I was actually able to fully set up the device. I am assuming it will still have issues occasionally. We will see though. I am very lucky because I go to work in a few hours and would miss out on so much tips! Thanks everyone for your support! If the phone still has problems after a restore how do you get a hold of Samsung if its an International phone. Do you have to send it back to the country of origin?
Samsung may decide that you need to contact the country of origin, I know for example Sony stopped supporting international phones in their repair centers last year... While you have the phone up and running try to get some diagnostic info on why its happening.
dude9946 said:
Samsung may decide that you need to contact the country of origin, I know for example Sony stopped supporting international phones in their repair centers last year... While you have the phone up and running try to get some diagnostic info on why its happening.
Click to expand...
Click to collapse
How would I go about doing that?
slimspittle said:
How would I go about doing that?
Click to expand...
Click to collapse
you could get CPU-Z from the app store and take screenshots.
Although i dont thing that would help, just call the samsung support line and select to go to phones and explain whats happening. you wont have to send the phone back to the country of origin.
Cyber5hark said:
you could get CPU-Z from the app store and take screenshots.
Although i dont thing that would help, just call the samsung support line and select to go to phones and explain whats happening. you wont have to send the phone back to the country of origin.
Click to expand...
Click to collapse
I agree you should call Samsung, However you might* still need to send it back to its Origin... It's totally up to Samsung's current policy on supporting international phones. Due to cost, a lot of repair centers really only keep parts/new phones for the ones locally available. However, It's also possible that they are able to contact their international warehouse for parts... So who knows ¯\_(ツ)_/¯ Keep us updated though, other users in your situation would love to know what happens!
dude9946 said:
I agree you should call Samsung, However you might* still need to send it back to its Origin... It's totally up to Samsung's current policy on supporting international phones. Due to cost, a lot of repair centers really only keep parts/new phones for the ones locally available. However, It's also possible that they are able to contact their international warehouse for parts... So who knows ¯\_(ツ)_/¯ Keep us updated though, other users in your situation would love to know what happens!
Click to expand...
Click to collapse
Okay so now it is stuck in a bootloop even after restoring to Odin again. I will try to get a hold of Samsung to see what they say. If not, I paid for my phone with my Wells Fargo Credit card and they have insurance. May get a replacement through them if Samsung won't help
So I just called them and they said to go into my local Samsung store within Best Buy to have them reflash the firmware lol. Going to take it their now to see what happens. Wish me luck
slimspittle said:
So I just called them and they said to go into my local Samsung store within Best Buy to have them reflash the firmware lol. Going to take it their now to see what happens. Wish me luck
Click to expand...
Click to collapse
Ha! did you tell them you already tried... good luck, keep us updated!
@slimspittle dont let us down, we need an update!
Okay so to send it in to Samsung(No charge for software issue as they said) they want a receipt with the IMEI on it. I bought the phone from Amazon and their is no IMEI on the receipt.

S7 Edge - Freezing and random rebooting

Hey all,
I have a galaxy s7 edge that's 2 months old. It's randomly freezing which is forcing me to do a hard reset or rebooting. I have done a factory restart by the settings, I have done a factory restart by holding the power, home and volume up key and lastly I have done a smart switch emergency thingy-me-bob.
The phone has never been rooted or messed around with in that matter and was working flawlessly up until this point. It's running all the latest updates you can get OTA - My next step tomorrow is to go into store for them to essentially repeat what I have done for several months...wondering if anyone here has any ideas of anything else I could try? Hoping it isn't a hardware defect.
Cheers,
Tom
Had exactly the same issue. Ran it in safe mode and it still froze. Factory reset - still the same problem. Sent it off to Samsung and got it back a few days ago along with the usual note explaining that the fault had been identified, latest software had been installed and it had passed through quality control. Went through setup and within an hour it was freezing again. Not convinced Samsung did anything other than re-flash the firmware and send it back. I'm guessing that this is a hardware issue, as I have read many posts with people experiencing the same issue. It's going back tomorrow so they can try again, with a note in the box, politely asking them to dig a little deeper....
Did another factory reset and it's frozen while on the always on display svtren. Think I'll be leaving a note asking them to do a physical hardware check!
You have latest software?
As per the original post, everything is running on latest.
Any way, visited the 'Geek squad' who informed me that I had done a factory reset wrong *sigh* restarted it infront of me and would you believe it! crashed. They're now sending it to Samsung to look at who I assume will just flash it again.
Very very disappointed with the edge, compared to my OP3T it's so sluggish.
had the same problem. had to send mine to samsung. there was something wrong with the partitioning i think but in some way odin couldn't fix
Fingers crossed it's something like that is wrong with mine!
I have exactly the same problem.
I'm in aus, and bought the phone from HK, so I'm a bit reluctant to send it back to HK/China.
I've done everything... but still the same.
rockuman_ex said:
I have exactly the same problem.
I'm in aus, and bought the phone from HK, so I'm a bit reluctant to send it back to HK/China.
I've done everything... but still the same.
Click to expand...
Click to collapse
From what I have read, it sounds like a hardware issue. The guy are the store was an utter moron but he did say the harder it is to the fix the more likely they are to just give me a new phone. Once i get it back ill share what they've done and see if it can help fix your issue.
Mine does reboot from time to time. Once a day, once a week...
Sometimes reboots when it stands alone on charging, sometimes in my pocket. I just realizes when my smartwatch vibrates to advert lost bluetooth conection.
Lastest firmware. I´ll probably will send to warranty.
I just recently got the S7 Edge. Great phone I just hates when it does that.

Categories

Resources