Related
Hey everyone, my hd2 died (original 1.48 rom), I already tried soft reset, hard reset, put out my battery, charge it and everyhting that came to my mind but when i turn it on it wont go further than the first htc image.
Is there anything i cant do or should i just take it back to the shop?
Thanks
I would take it back, even if you do fix it. You don't want a phone that may still have a underlying problem.
Htc HD2 BRICK Need HELP!!!!!!!
I flashed Duttys_Leo_Sense_2.5_5.2.23554.5.5.0_1.72_Multi-Lang_6.5.5_Radio_2.07.51.22.2_V1.2_WWE into tmobile htc hd2 cause i was [email protected]$kin goin Rom happy and didnt double check its compatibility and my screen went blank black, cant power on, cant go into bootloader, and cant hard reset but when i plug it in to my computer it recognizes it as a device without a driver i saw it in the device manager on windows 7 ulitmate. CAN I SAVE MY HTC HD2??
I KILL my htc hd2 (BRICKED)
I used HSPL2_1024_RUN.exe i flashed like 5 roms within 24hrs i was trying them out and this one made killed my hd2.
for those stuck on the htc boot image
take off the back cover of the phone and press the little red button, this will restart the phone
AS SOON AS you press it, press and hold the volume down button this will bring you to the bootloader
connect the phone via usb to your computer and flash a different radio rom (look first which are compatible with your rom)
if this doesnt work, using the same method flash back to your original rom.
hpg said:
I flashed Duttys_Leo_Sense_2.5_5.2.23554.5.5.0_1.72_Multi-Lang_6.5.5_Radio_2.07.51.22.2_V1.2_WWE into tmobile htc hd2 cause i was [email protected]$kin goin Rom happy and didnt double check its compatibility and my screen went blank black, cant power on, cant go into bootloader, and cant hard reset but when i plug it in to my computer it recognizes it as a device without a driver i saw it in the device manager on windows 7 ulitmate. CAN I SAVE MY HTC HD2??
Click to expand...
Click to collapse
for tmous with 1gb rom NEVER flash a radio with .51. in the code.
still haven't seen anyone recover from this. if anyone has please let me know.
Damn it captain!!!!!!
I just got it on the 24th shhhhhhhh....... ummm i just will take it to TMOBILE i hope i can get an other one, they may not have one in stock or they WONT give me another. i will see as soon as the store opens.
Sorry to hear about people's problems. Just remember if you have TMobile
USA there is NOT a way to flash another rom onto the phone..Just give it time the wonderful folks here are working on it. If your still in your 14 day grace period just return the phone to the store and play dumb. You might
have to wait for another phone since apparently they did not anticipate
how many people wanted this phone and sold out quickly. I know I was there
at 6:30 and the second in line and they only had 5!
Anyway, the most important thing you can do here is DO a search!
I KILL my htc hd2 (BRICKED)
BUT I have flashed roms into Tmobiles htc hd2 like TOUCH_X_TREME_23549_TMOUS_2_30_5_49 among others and they worked! i was just try different ones and i PICKED and I BRICKED!!!!!!!!!!!
Damitu said:
Just remember if you have TMobile
USA there is NOT a way to flash another rom onto the phone..
Click to expand...
Click to collapse
sorry? sure about that? seems to me lots of people have successfully flashed their tmous hd2.
It only goes wrong if you
1 - flash a rom based on anything less than 2.10 rom
or
2 - flash a radio with ..51.. in the version number.
I KILL my htc hd2 (BRICKED)
When I take it back do you think tmobile can they tell if i flashed a rom?
hpg said:
When I take it back do you think tmobile can they tell if i flashed a rom?
Click to expand...
Click to collapse
possibly, however its worth a try, there are other people that have reported they got it exchanged. the worst theu can do is send you it back un fixed. They can't keep it and make you pay for the fix.
I KILL my htc hd2 (BRICKED) and the walk of SHAME!!!
Ok well thanks for your GREAT!!! input how can i add you to friends for future epic fail endeavours!!! i encounter.
hpg said:
Ok well thanks for your GREAT!!! input how can i add you to friends for future epic fail endeavours!!! i encounter.
Click to expand...
Click to collapse
hehe, i rarely bother accepting friend requests, this isnt a social networking site!
Just find any post be me, and either click my name or the green button next to my name to PM me.
Shamely going back to tmobile on wed
I went to tmobile last friday they tried to turn it on, pushing reset and taking out the battery so they put me on a list for this coming wed. I still got the bricked one with me they told me to bring it in for a trade. i have tried everything to turn it on but the screen remains BLACK. so i got a BLACK BRICK!!!
Any more ideas?
cgrec92 said:
for those stuck on the htc boot image
take off the back cover of the phone and press the little red button, this will restart the phone
I do not see a little red button under the back cover. I am in the US, just bought phone, slightly used of course, no warranty. It suddenly went dead this afternoon while charging, will sometimes try to power up but will just keep flashing that one screen "stick together" over and over.....
Tried another battery, same thing.
Click to expand...
Click to collapse
Mine is doing the same thing . . . in the US, the reset button is right next to the SD card slot, and it's yellow. Mine wouldn't come on Friday, and I started a web chat with Tmobile to see if they would exchange it, and then it just came back on. They said as long as the white sticker at the top of the battery compartment is still white (proving you didn't get it wet), then they will exchange it. It worked fine for me the rest of the weekend (AFTER I did a hard reset, and got it running great!!). This morning, I locked it while running MobiTV, then I couldn't unlock it, so I pulled the battery. That was 2 hours ago, and it still won't come on . . .
If it doesn't come on before I leave work, I'm taking it to Tmobile tonight!!
UPDATED 20 minutes later: Just came on . . . no rhyme or reason why?? Just started after MULTIPLE times of taking out and putting back battery, SIM, and SD card. Got the same error that I've been getting the last couple months on reboots (services.exe)?? When I did a CleanRAM, it free'd up 3.36MB . . . so SOMETHING was hung up, but nothing was running in the task manager??
Generally, few task managers show what's really going on with the phone's memory. Use an advanced task manager which will allow you to control the actual processes running on your device, Google for the names of those which seem to cause mischief and terminate them (if possible) or try to find a solution.
hpg said:
When I take it back do you think tmobile can they tell if i flashed a rom?
Click to expand...
Click to collapse
Hey I am also Tmobile User and I have flashed a few ROMS luckily I have not Bricked my phone (knock on wood.) I was just wondering how your return went? I have insurance on mine and figured I would just take it back if that happened. I just didn't know if that would work? Did you ever get a new one
Another update . . . used my phone all afternoon, and tried to charge it, and it wouldn't charge??? Luckily, my husband has the same phone, so I checked his with the same charger. Compared the two phones, and the prongs that hit the battery were bent back. I folded them back down, and now it can charge again. Makes me wonder if that is the problem with the phone not coming back on? Maybe putting the battery back in so that it wasn't hitting the prongs has been keeping it from turning back on . . .
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.
I have noticed that when I charge my Galaxy S4 version 4.4.2 overnight, when I wake up the LCD screen is black and the only two buttons when pushed are the menu and back button. I have to take the battery out for a few seconds and restart before it will function correctly again. When I call ATT technical support the only thing they suggest is to master reset ALL THE TIME and of course that's getting annoying. I've been noticing this ever since the last update. Is there a fix anyone or any settings I should fix or change?
taiowa72 said:
I have noticed that when I charge my Galaxy S4 version 4.4.2 overnight, when I wake up the LCD screen is black and the only two buttons when pushed are the menu and back button. I have to take the battery out for a few seconds and restart before it will function correctly again. When I call ATT technical support the only thing they suggest is to master reset ALL THE TIME and of course that's getting annoying. I've been noticing this ever since the last update. Is there a fix anyone or any settings I should fix or change?
Click to expand...
Click to collapse
The original file may be lost when you update your phone.
It is hard to go back the old the version. You can ask the repair store near you to root it. Or you can wait for a more advanced version to update your phone again.
Another possible is that the LCD screen was broken during update the version.
Response to your response
LotoTutu said:
The original file may be lost when you update your phone.
It is hard to go back the old the version. You can ask the repair store near you to root it. Or you can wait for a more advanced version to update your phone again.
Another possible is that the LCD screen was broken during update the version.
Click to expand...
Click to collapse
I wish I could root but I'm terrified to. I've download all the software and prepare myself for it, but then I chicken out for fear of bricking my phone for I just upgraded to the galaxy s4 6 months ago. Thank you for your response, I will consider everything else you suggested though.
taiowa72 said:
I wish I could root but I'm terrified to. I've download all the software and prepare myself for it, but then I chicken out for fear of bricking my phone for I just upgraded to the galaxy s4 6 months ago. Thank you for your response, I will consider everything else you suggested though.
Click to expand...
Click to collapse
I would suggest rooting & installing a custom rom as far as I can see you are left with a useless phone & you can't brick it if you follow the instructions set out in threads ? Seriously it's almost impossible to brick even if you make a mistake ?
Otherwise I would suggest contacting tech support & demand a replacement/solution to the problem as it only happened after your last update?
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
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.