Related
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.
Hey guys,
I was updating my Focus earlier today. It went through the process fine until the last restart step of the last update(there were 2 or 3 in total), when it seemed to just hang on the Samsung loading screen. I left it for about 10-15 minutes, but I had to go catch a bus so I had to unplug the phone and go.
Bad choice on my part. Reading online after the fact informed me the Focus could hang for a while on the Samsung loading screen at that step of the update. And now, since I interrupted the update process, its been bricked for me. Whenever I turn it on, it just stays on the Samsung loading screen. It will not be recognized by Zune, or my computer at all. I can get it to go to the hard reset screen, but nothing seems to come of that (I let it go for intervals of 15 minutes, as a few sites advised, to 45, with nothing occuring).
I'm trying leaving it on the Samsung focus screen for a few hours. If that fails, I'll leave it on overnight in the hard reset download mode. I dont have much hope though, and I'm wondering if any of you guys know anything I could try to fix it.
Thanks a bunch.
I'm pretty sure you can get to download mode and flash one of the original focus roms. Just head over to the Focus development section and reflash the rom. Make sure you flash the right one in regard to rev version. The thread will give you all the directions you need.
Figured i'd include the link just to make it a little easier. I hate bricking phones haha. Good Luck
http://forum.xda-developers.com/showthread.php?t=1131022
I flashed the Omnia 7 ROM onto my samsung focus after the memory was ruined by a bad microsd card (had only 15mb of memory, many people have had this issue from what i read). The unique problem is after flashing the samsung omnia 7 ROM onto the phone it now will not load past the samsung load screen it just stays frozen.
I have flashed every ROM possible onto the phone and it will not complete and just freezes on the samsung screen despite seeming to complete on the computer and even on phone to extent (shows the green loading bar on bottom while flashing). I figrue by this point one of you smart guys have figured out how to solve this. I would love to replace my HTC surround with my focus to refresh things.
PLEASE somone help me... Can someone at least confirm the phone is useless, and if so what I should do with it? Or is it possible that I can unlock it again somehow.
neibl said:
I flashed the Omnia 7 ROM onto my samsung focus after the memory was ruined by a bad microsd card (had only 15mb of memory, many people have had this issue from what i read). The unique problem is after flashing the samsung omnia 7 ROM onto the phone it now will not load past the samsung load screen it just stays frozen.
I have flashed every ROM possible onto the phone and it will not complete and just freezes on the samsung screen despite seeming to complete on the computer and even on phone to extent (shows the green loading bar on bottom while flashing). I figrue by this point one of you smart guys have figured out how to solve this. I would love to replace my HTC surround with my focus to refresh things.
PLEASE somone help me... Can someone at least confirm the phone is useless, and if so what I should do with it? Or is it possible that I can unlock it again somehow.
Click to expand...
Click to collapse
The low storage issue from adding a mSD card would have been resolved with a simple HARD RESET.
Right now you need a backup of your phone, made before the flashing with Omnia bits. Someone else had this issue, read here. This is also for the specific thread you opened here.
*noob*
My phone froze during the update for 7.5... Zune gave me an error code but wasn't able to write it down. The phone froze on the left arrow and the red "do not remove" symbol for about 30 mins before i unplugged it and turned it off. When i turned on the phone it stayed on the samsung logo and did nothing. i did a hard reset i still got the same thing. Then i took out the memory card and reset, still the same stuck on samsung. Then i called samsung and the walked me through a reset/reformat By pulling out the sim card then Holding down the camera/volume/power at the same time until it vibrates then after just hold down the camera and volume down, click the windows icon to reformat, still stuck on the Samsung logo!!!!
I'm going to try this flash thing... We will see how it goes i'm a noob
Interesting Samsung gave you that advice.
First thing you should have done is connect it with Zune started and it should have continued the process as long as there wasn't a fatal error.
Flashing UCJK2 should work in your case (assuming you have 1.3 hardware).
Flashing any and all ROMS will not work, keeps freezing at the samsung logo screen after seeming to finish, can't get god damn phone to lauch up, then I could connnect it to zune and exhaust mroe resources. samsung just sent me a bad phone and it stinks.
neibl said:
Flashing any and all ROMS will not work, keeps freezing at the samsung logo screen after seeming to finish, can't get god damn phone to lauch up, then I could connnect it to zune and exhaust mroe resources. samsung just sent me a bad phone and it stinks.
Click to expand...
Click to collapse
As I said and the per the info in the thread above, you need to restore from backup. Most likely flashing any rom is not working.
If you tinkered by flashing unknown bits and without taking precautionary measures, don't blame others.
I was not blaming anyone, the only reason i started flashing was because a microsd card ruined the phone down to 15 mb and no matter what method i used to reset the phone it would not leave that state, i tried for month before resorting to drastic flashes.
It does not matter anyway what is done is done, just exploring if there is any moving forward. If restoring is what I have to do to have a chance, is there any way to restore without being able to connect to zune. Also I do not have a backup is there one available anywhere?
neibl said:
It does not matter anyway what is done is done, just exploring if there is any moving forward. If restoring is what I have to do to have a chance, is there any way to restore without being able to connect to zune. Also I do not have a backup is there one available anywhere?
Click to expand...
Click to collapse
Zune creates backups of stages before the last update. If you're on Mango, you should have a NoDo backup in Zune. There is no way you can restore without Zune. You can check by going in Zune (when phone connected), Phone (near Marketplace/Social - top left), then "Settings", then "Update". Now Zune should tell you you have a Restore. Good luck!
Hi Everybody,
I believe that I am now in serious trouble with my Motorola Defy. I have tried to look everywhere today to find a similar problem to what I am experiencing, and although I can find all the problems, I can't find anyone which has happened like this. It would be so great if someone could help me. I am so so desperate and in total panic right now. I need this phone to work which I had bought in Germany (where my home base is set up) but I am currently working in Estonia where salary really does not allow me to just go out and buy a new one - not even a cheap 20€ phone.
I originally bought the phone about 1 1/2 years ago with Android 2.1. After about 6 months I did the official update to Android 2.2. This is where a few things started to go wrong. Google maps would crash the phone so that I would have to take the battery out to restart it. The camera didn't work properly, and not at all with the flash, and the phone would quite often restart itself. I could however live with all this and just accepted it as I didn't want to do anything to make it worse - I trust myself 100% with computers and there isn't much that I can't do with them. But with phones, that's where I have to put my hands up as I really don't trust myself to do anything because of the fear of bricking one.
Anyway, today as I was using the phone after taking a few pictures the phone had frozen, so as always I took the battery out and turned it on again, when it loaded up and as soon after I put my pin and unlock number in, it restart itself, So I again I put my pin and unlock number in, and it restarted itself. After this I couldn't even put my pin number in.
I then did went into Bootloader to do a wipe and restore, This however, after taking two hours and just watching the yellow dots move along, was clear to me that this also wasn't working. After coming home from work I then copied the instructions found I think in the Beginners Defy Guide on this site for using RSD Lite and an SBF File. This then failed and in Bootloader it also then said Corrupt.
So I then started to watch a video on youtube for a complete guide from unbricking to installing CM10 (something I wanted to do the whole time and never trusted myself). Meanwhile, whilst everything was downloading, although the phone still had about 60% battery, I thought I would plug it in just to charge it for a bit, this however also did not work but I left it in just in case it was working.
After everything was finished downloading, I unplugged the phone from the wall and now it won't even turn on,, neither in Bootloader, or the screen. It does NOTHING! :crying::crying:
When I plug it into the computer the little white led light comes on (top left of the phone) and the computer makes the sound that something is plugged in. This is also recognised my RSD Lite, however once a file has been created it cannot be flashed. It's like the phone is there, but it isn't.
I am really desperate to get this working as I really need this phone for work, and like I said just cannot afford to run and buy anything.
I'm very sorry if I have posted this in a wrong area, but I honestly did try to find something. I just don't understand how plugging it in to charge can stop it from not even opening bootloader, It's like it's got a mind of it's own.
Thank you very very much for reading, and I apologise that it's so long,
Best Wishes,
Steve
To get into the bootloader , keep the volume up button pressed and then press the power button. Is this what you tried to do?
And I didn't get the part where you wiped through the bootloader. As far as I know there is no option there. Do you mean the stock recovery?( The yellow dots are there in the stock recovery)
Sent from my MB526 using xda app-developers app
wahat3 said:
Hi Everybody,
I believe that I am now in serious trouble with my Motorola Defy. I have tried to look everywhere today to find a similar problem to what I am experiencing, and although I can find all the problems, I can't find anyone which has happened like this. It would be so great if someone could help me. I am so so desperate and in total panic right now. I need this phone to work which I had bought in Germany (where my home base is set up) but I am currently working in Estonia where salary really does not allow me to just go out and buy a new one - not even a cheap 20€ phone.
I originally bought the phone about 1 1/2 years ago with Android 2.1. After about 6 months I did the official update to Android 2.2. This is where a few things started to go wrong. Google maps would crash the phone so that I would have to take the battery out to restart it. The camera didn't work properly, and not at all with the flash, and the phone would quite often restart itself. I could however live with all this and just accepted it as I didn't want to do anything to make it worse - I trust myself 100% with computers and there isn't much that I can't do with them. But with phones, that's where I have to put my hands up as I really don't trust myself to do anything because of the fear of bricking one.
Anyway, today as I was using the phone after taking a few pictures the phone had frozen, so as always I took the battery out and turned it on again, when it loaded up and as soon after I put my pin and unlock number in, it restart itself, So I again I put my pin and unlock number in, and it restarted itself. After this I couldn't even put my pin number in.
I then did went into Bootloader to do a wipe and restore, This however, after taking two hours and just watching the yellow dots move along, was clear to me that this also wasn't working. After coming home from work I then copied the instructions found I think in the Beginners Defy Guide on this site for using RSD Lite and an SBF File. This then failed and in Bootloader it also then said Corrupt.
So I then started to watch a video on youtube for a complete guide from unbricking to installing CM10 (something I wanted to do the whole time and never trusted myself). Meanwhile, whilst everything was downloading, although the phone still had about 60% battery, I thought I would plug it in just to charge it for a bit, this however also did not work but I left it in just in case it was working.
After everything was finished downloading, I unplugged the phone from the wall and now it won't even turn on,, neither in Bootloader, or the screen. It does NOTHING! :crying::crying:
When I plug it into the computer the little white led light comes on (top left of the phone) and the computer makes the sound that something is plugged in. This is also recognised my RSD Lite, however once a file has been created it cannot be flashed. It's like the phone is there, but it isn't.
I am really desperate to get this working as I really need this phone for work, and like I said just cannot afford to run and buy anything.
I'm very sorry if I have posted this in a wrong area, but I honestly did try to find something. I just don't understand how plugging it in to charge can stop it from not even opening bootloader, It's like it's got a mind of it's own.
Thank you very very much for reading, and I apologise that it's so long,
Best Wishes,
Steve
Click to expand...
Click to collapse
Check out this link all the best :good:
Hi,
Not sure if it's a right place to ask, but let it be my first post here. I own an S5 device, and it's sort of crazy. Let me explain.
Three months ago my device suddenly rebooted and got almost-soft-bricked in sense of being unable to boot to the operating mode normally: its display just got black after the splash screen, however I could tap the display and watch 1 FPS "live stream" using `adb screencap` at my PC. So the device was not dead and I could take out all private not synced data I needed (it was really hard once for an application that has the backup facility disabled in its application manifest) -- blind tapping everywhere. My first attempt to fix the device was re-flashing another compatible ROM having all important data backed up. Well, I got it bricked and could not boot anymore. The recovery mode was not available (the device just frozen if trying to enter the recovery), however I could enter the download mode.
Unfortunately, no reflashing helped, so I decided to let it be fixed by a repaire service (since an official Samsung service center in my country has rejected the repair request _with payment_ because the device was not intended for sale here -- well, "thanks Samsung"). Ok, the alternative service took the device and asked almost a half of the device price for the display replace. Honestly, I forgot to ask why there was an idea to replace the display if it worked perfect while it was waiting in the Download mode. Again, it just got black after the splash screen, but the display worked fine in the Download mode until the device was powered off or reset. So after a few days they gave it back to me, and the device was really good now -- it worked fine. They also re-fllashed the device to Android 6 (previously Android 5) and the device was unrooted. Well, that's fine to me.
But after a few hours of rooting, testing and re-installing the software and migrating the data back to the device, the device rebooted again being unable to boot to the "operating mode". Now it just got stuck at the Samsung S5 splash screen or rebooted in a loop. But after a long time (it might took more than a day; the battery seems to be inserted in the device and not pulled off) the device was able to boot normally and (this might be odd) upgrade the installed apps. If I remember, this was a cyan screen with two or three animated white gears. So about 150 apps were upgraded and the normal "operating" mode activated -- so I could use the device. Now after working a few hours, the device falls into a reboot loop / splash freeze coma again for undetermined time, and then, for unknown to me reason, the device woke up.
In short:
1) The device reboots or shuts down suddenly.
2) Instant rebooting does not work for whatever reason.
3) Just wait for some undetermined time without the device battery pulled off.
4) ... It boots again.
5) The upgrading process starts after the boot.
6) Working with the device until paragraph 1: "The device reboots or shuts down suddenly".
Now I don't know if it's a hardware or a software issue: the repair service guys didn't explain much, and now I'm feeling cheated for the replacement of the display that worked perfect in the Download mode that I gave half device price just because it was an idea of theirs. Yes, I have the repair warranty paper for their service, but I just would like to know the real context.
What I could be deservedly blamed for:
* I rooted the device after their repair in a wrong way.
* When I rooted the device, I removed most Samsung bloatware I used to remove earlier. I don't tend to think that I could kill some important software, though. But, to me, it's hard to believe that a software issue might cause such an odd device behavior (I mean the booting just after a certain period of time).
So... I would really and really appreciate getting the real issue behind the symptoms or just a hint spark of light to reveal possible root causes. And was I really cheated by the repair service?
* My device: Samsung SM-G900P S5, Sprint
* Firmware before the repair: stock, Android 5.0.x (?), root, most Samsung bloatware removed
* Firmware after the repair: stock, Android 6.0.1, root, most Samsung bloatware removed (yes, the bloatware list difference is significant now)
* The battery: seems to work fine and does not get drained when the device is in coma
Thank you!
hurricane flow said:
Hi,
Not sure if it's a right place to ask, but let it be my first post here. I own an S5 device, and it's sort of crazy. Let me explain.
Three months ago my device suddenly rebooted and got almost-soft-bricked in sense of being unable to boot to the operating mode normally: its display just got black after the splash screen, however I could tap the display and watch 1 FPS "live stream" using `adb screencap` at my PC. So the device was not dead and I could take out all private not synced data I needed (it was really hard once for an application that has the backup facility disabled in its application manifest) -- blind tapping everywhere. My first attempt to fix the device was re-flashing another compatible ROM having all important data backed up. Well, I got it bricked and could not boot anymore. The recovery mode was not available (the device just frozen if trying to enter the recovery), however I could enter the download mode.
Unfortunately, no reflashing helped, so I decided to let it be fixed by a repaire service (since an official Samsung service center in my country has rejected the repair request _with payment_ because the device was not intended for sale here -- well, "thanks Samsung"). Ok, the alternative service took the device and asked almost a half of the device price for the display replace. Honestly, I forgot to ask why there was an idea to replace the display if it worked perfect while it was waiting in the Download mode. Again, it just got black after the splash screen, but the display worked fine in the Download mode until the device was powered off or reset. So after a few days they gave it back to me, and the device was really good now -- it worked fine. They also re-fllashed the device to Android 6 (previously Android 5) and the device was unrooted. Well, that's fine to me.
But after a few hours of rooting, testing and re-installing the software and migrating the data back to the device, the device rebooted again being unable to boot to the "operating mode". Now it just got stuck at the Samsung S5 splash screen or rebooted in a loop. But after a long time (it might took more than a day; the battery seems to be inserted in the device and not pulled off) the device was able to boot normally and (this might be odd) upgrade the installed apps. If I remember, this was a cyan screen with two or three animated white gears. So about 150 apps were upgraded and the normal "operating" mode activated -- so I could use the device. Now after working a few hours, the device falls into a reboot loop / splash freeze coma again for undetermined time, and then, for unknown to me reason, the device woke up.
In short:
1) The device reboots or shuts down suddenly.
2) Instant rebooting does not work for whatever reason.
3) Just wait for some undetermined time without the device battery pulled off.
4) ... It boots again.
5) The upgrading process starts after the boot.
6) Working with the device until paragraph 1: "The device reboots or shuts down suddenly".
Now I don't know if it's a hardware or a software issue: the repair service guys didn't explain much, and now I'm feeling cheated for the replacement of the display that worked perfect in the Download mode that I gave half device price just because it was an idea of theirs. Yes, I have the repair warranty paper for their service, but I just would like to know the real context.
What I could be deservedly blamed for:
* I rooted the device after their repair in a wrong way.
* When I rooted the device, I removed most Samsung bloatware I used to remove earlier. I don't tend to think that I could kill some important software, though. But, to me, it's hard to believe that a software issue might cause such an odd device behavior (I mean the booting just after a certain period of time).
So... I would really and really appreciate getting the real issue behind the symptoms or just a hint spark of light to reveal possible root causes. And was I really cheated by the repair service?
* My device: Samsung SM-G900P S5, Sprint
* Firmware before the repair: stock, Android 5.0.x (?), root, most Samsung bloatware removed
* Firmware after the repair: stock, Android 6.0.1, root, most Samsung bloatware removed (yes, the bloatware list difference is significant now)
* The battery: seems to work fine and does not get drained when the device is in coma
Thank you!
Click to expand...
Click to collapse
someone said after an OTA to 6.0.1 it borked the phone into a reboot loop too. I had mine rooted for maybe a week or 2 and now I have reboot Loops, not even twrp can fix this issue. I am trying a battery like this person said here http://forum.xda-developers.com/galaxy-s5/help/marshmallow-6-0-1-ota-update-boot-loop-t3425838,
spending 9 bux and change beats spending 250 for another Unlocked G900T
http://forum.xda-developers.com/galaxy-s5/help/marshmallow-6-0-1-ota-update-boot-loop-t3425838
eidairaman1 said:
someone said after an OTA to 6.0.1 it borked the phone into a reboot loop too. I had mine rooted for maybe a week or 2 and now I have reboot Loops, not even twrp can fix this issue. I am trying a battery like this person said here http://forum.xda-developers.com/galaxy-s5/help/marshmallow-6-0-1-ota-update-boot-loop-t3425838,
spending 9 bux and change beats spending 250 for another Unlocked G900T
http://forum.xda-developers.com/galaxy-s5/help/marshmallow-6-0-1-ota-update-boot-loop-t3425838
Click to expand...
Click to collapse
Hm, that's interesting, thank you. I also noticed that the loop happens after some time only, it's like the more you have your phone running in the normal mode, the more your phone can get into the loop again. However, I don't think it's a battery overheat issue or so (sorry, I may use silly terms not being an expert at all). So in short:
1) After some pretty long power-off time you power on the device. It's working really stable unless...
2) ... unless something happens (battery? some intricate software or hardware issue?) and the device gets rebooted.
3) Here comes the boot loop, and usually no reboot helps to get out of the reboot loop.
4) Just power off the device and let it just be alone for some time, and now you're back to the step 1 until the "unless..."
My coma device is powered off for long time (thus I think that the step 4 still works for me after that long time) and I'm going to give it to the repair service again, just comparing what the service guys say and what the forum folks say.
I will follow up on the battery swap when mine arrives.
hurricane flow said:
Hm, that's interesting, thank you. I also noticed that the loop happens after some time only, it's like the more you have your phone running in the normal mode, the more your phone can get into the loop again. However, I don't think it's a battery overheat issue or so (sorry, I may use silly terms not being an expert at all). So in short:
1) After some pretty long power-off time you power on the device. It's working really stable unless...
2) ... unless something happens (battery? some intricate software or hardware issue?) and the device gets rebooted.
3) Here comes the boot loop, and usually no reboot helps to get out of the reboot loop.
4) Just power off the device and let it just be alone for some time, and now you're back to the step 1 until the "unless..."
My coma device is powered off for long time (thus I think that the step 4 still works for me after that long time) and I'm going to give it to the repair service again, just comparing what the service guys say and what the forum folks say.
Click to expand...
Click to collapse
I received a battery yesterday, charged it up and started using it today, no reboots or bootloops so far.
The battery that came in my phone was made in china, the one I just got yesterday was made in Vietnam.
I'm wondering if Samsung really needs to stop using china to make batteries lol, Surefire flashlights state not to use batteries made in china lol.
eidairaman1 said:
I received a battery yesterday, charged it up and started using it today, no reboots or bootloops so far.
The battery that came in my phone was made in china, the one I just got yesterday was made in Vietnam.
I'm wondering if Samsung really needs to stop using china to make batteries lol, Surefire flashlights state not to use batteries made in china lol.
Click to expand...
Click to collapse
Hm, that's really interesting. It's hard to believe that replacing the old battery might affect it that much and get rid of bootloops -- I mean, I just thought that it might be a software/firmware failure (let's say I removed some system apps [actually Samsung bloatware] improperly), or something very core hardware might fail, but I have never thought of a batter as the root cause. Hard to say, sorry. But I'll take your solution into account. Thank you!
hurricane flow said:
Hm, that's really interesting. It's hard to believe that replacing the old battery might affect it that much and get rid of bootloops -- I mean, I just thought that it might be a software/firmware failure (let's say I removed some system apps [actually Samsung bloatware] improperly), or something very core hardware might fail, but I have never thought of a batter as the root cause. Hard to say, sorry. But I'll take your solution into account. Thank you!
Click to expand...
Click to collapse
I thought it was a bad rom flash as well or SuperSU causing it, well I found another article stating they replaced the battery and the issue went away. I think the phone was stating a bad POST so it would restart
Today on my way to work I was playing music through my bluetooth and the music stopped. I went to reset bluetooth and it took almost 3 mintues to turn off. When I went to turn it back on, it wouldn't. I powered off and reset the phone. After, it got stuck in a bootloop. LG logo for about 7-8 secs and restarts.
Before the bootloop, I was noticing a few weird things: A notification of USB Options was always up, was saying I was using my phone as a USB Power Supply. If I changed the options it would revert back to USB PwrSply. I noticed the battery life was getting a lot worse. Also, when plugged into Quick Charge it would not say "Quick Charging" anymore.
I can get into the Recovery menu, but all options revert to the bootloop.
I can get to the Download menu. After about a few seconds of sitting on the Download menu, it starts the LG logo bootloop.
I have not tried to flash another stock ROM. I have downloaded the LGUp program, Uppercut, LG Mobile Support Tool, and LG Mobile Driver. I also downloaded the previous 1BA firmware kdz file.
I believe I have the knowledge to reflash properly, but I do not want to make the phone worse or lose my data. Plus, I don't want to void the warranty.
TL;DR I have bootloop and want to save my data!
Any suggestions would be very much appreciated! Thank you!
Flashing won't help you, this is a hardware problem. You can try freezing then phone, seeing if it will boot, and then backing up your files a fast as you can. Alternatively, if that doesn't work, you can take a hair dryer and heat the phone up.
Either way, LG will definitely take care of it under warranty since those morons can't seem to make a decent heat sink that lasts. Every LG flagship phone since the G4 has had this problem. I am sure the V30 and G7 will be no different -- they just haven't been out long enough yet.
-- Brian
runningnak3d said:
Flashing won't help you, this is a hardware problem. You can try freezing then phone, seeing if it will boot, and then backing up your files a fast as you can. Alternatively, if that doesn't work, you can take a hair dryer and heat the phone up.
Either way, LG will definitely take care of it under warranty since those morons can't seem to make a decent heat sink that lasts. Every LG flagship phone since the G4 has had this problem. I am sure the V30 and G7 will be no different -- they just haven't been out long enough yet.
-- Brian
Click to expand...
Click to collapse
I was hoping that this wasn't the issue. I was hoping that it was from the 1CA update, because the other random problems seemed to have started when it updated. Should I at least try to reflash? Would reflashing to a stock/OEM ROM (the one i mentioned above) void the warranty?
Also, when I restarted the phone today, that was the first restart that I have done since the update. Not sure if that means anything, but maybe??? lol
No, flashing a KDZ does not void the warranty even by LGs terms.
In the US rooting your phone doesn't void the warranty either .. no matter what OEMs will have you believe.
-- Brian
runningnak3d said:
No, flashing a KDZ does not void the warranty even by LGs terms.
In the US rooting your phone doesn't void the warranty either .. no matter what OEMs will have you believe.
-- Brian
Click to expand...
Click to collapse
Awesome! That's definitely good to know. Thanks.
I'm going to attempt to downgrade flash it. If it doesn't work, I'll contact LG. I dont really care about buying a new phone. My data on it is worth WAY more to me than the phone. (Guess I really should start backing up my stuff XD )
If you have any suggestions as to recovering my data, even if it kills the phone, I'm all ears!
Update: I attempted to flash or just access the phone as storage using many different ways. While I was browsing for new answers, I kept the phone connected to my computer and left it bootlooping. Eventually, the phone battery died and booted up properly. The battery was at 1%, but everything loaded just fine. I was able to recover all my data and save it to my PC.
Thinking that this was a soft-brick due to the phone actually fully booting, I was going to attempt to root and flash. I let the phone charge to 100%. When I reset the phone to implement the root, the phone got stuck in a BOOTLOOP AGAIN.
Any ideas in why this would happen? Does this mean it's a software based bug, or hardware?
Dart_Fur said:
Update: I attempted to flash or just access the phone as storage using many different ways. While I was browsing for new answers, I kept the phone connected to my computer and left it bootlooping. Eventually, the phone battery died and booted up properly. The battery was at 1%, but everything loaded just fine. I was able to recover all my data and save it to my PC.
Thinking that this was a soft-brick due to the phone actually fully booting, I was going to attempt to root and flash. I let the phone charge to 100%. When I reset the phone to implement the root, the phone got stuck in a BOOTLOOP AGAIN.
Any ideas in why this would happen? Does this mean it's a software based bug, or hardware?
Click to expand...
Click to collapse
I'm not sure to be honest, your situation seems strange
Was it hot and was your phone in the sun during your trip to work? Overheating can make weird things happen.
lakingslayer said:
Was it hot and was your phone in the sun during your trip to work? Overheating can make weird things happen.
Click to expand...
Click to collapse
It wasn't hot at all, I had the A/C in my car on and it sets on a car mount that mounts to the air vent. It gets direct A/C. I didn't have it charging either.
All I did was connect my phone to Bluetooth, play a mix, and drive 15mins to work at 6am in the morning. It was still dark and cool out. The music stopped and I tried to reset bluetooth. It took forever to turn off and wouldnt turn back on. I reset phone and BOOTLOOP. ???
There is no damage to the phone physically. I don't think I've ever dropped it ever. It's gotten hot a couple times, but that was months and months ago.
I've never had a problem with this phone since I got it almost 2 years ago, since the 1CA update, I had a couple bugs, now this bootloop.
Dart_Fur said:
Update: I attempted to flash or just access the phone as storage using many different ways. While I was browsing for new answers, I kept the phone connected to my computer and left it bootlooping. Eventually, the phone battery died and booted up properly. The battery was at 1%, but everything loaded just fine. I was able to recover all my data and save it to my PC.
Thinking that this was a soft-brick due to the phone actually fully booting, I was going to attempt to root and flash. I let the phone charge to 100%. When I reset the phone to implement the root, the phone got stuck in a BOOTLOOP AGAIN.
Any ideas in why this would happen? Does this mean it's a software based bug, or hardware?
Click to expand...
Click to collapse
I hope you got your data off before you started messing with it.. your phone is dead.. Runningnak3d gave you a clear warning
Flashing won't help you, this is a hardware problem. You can try freezing then phone, seeing if it will boot, and then backing up your files a fast as you can. Alternatively, if that doesn't work, you can take a hair dryer and heat the phone up.
Click to expand...
Click to collapse