Related
Hi everyone!
I'm wondering, how risky it is to flash new firmware to the tab? Is it really brickable, I mean, is it possible to really really brick the tab to a point where it's not possible to fix it? I'm asking partly because I'm a rookie, but mostly because it seems that everyone who manages to brick their tab around here, is somehow able to restore it. Or am I mistaken?
Where I live, the tab has a starting price of $1100. And thats gotta be one of the most expensive bricks in xda history. And if I brick mine, I know I won't be able to resist buying a new one, which adds ut to a $2200 pricetag and a very VERY angry gf..
thanks btw to all of you who make this place what it is
As risky as any other device. Simple. The risk doesnt just lay on the devices shoulders, its the user and the rom maker.
Sent from my GT-P1000 using XDA App
Okay, I'm so confused with the brick-terminology being used here. In all posts regardig new firmware to the tab you'll see at least to guys saying that they bricked their tab. Only to say that they fixed it/unbricked it moments later.
I thought that if you bricked your device, whatever device it is, then it's dead, period. No more usefull than a brick like the ones you'll find in a brick wall, just a hell of a lot more expensive. Heck, the word "unbrick" shouldn't even exist by this definition.
So, let me rephrase:
If I brick my tab, can't I just unbrick it? And if not, why? Is it even possible for the tab to be totally and permanently bricked forever? Is the tab in any way safer to fool around with than other devices? Do we know anyone who have bricked their tab permanently? Should I be afraid of fooling around with my tabs firmware for real?
I think it's just a question of perception on the part of the person who "bricked" their device (the "brickie"? ). If you flash and find that you have what appears to be a dead device then you may well come on here and say "I've bricked my device!". You may then find that it's not bricked at all as there is a way (previously unknown to yourself) to recover. I remember in the old days on here people would pick up "bricked" phones on ebay etc, knowing that quite often they could recover them. It probably still happens...
But devices certainly can get permanently bricked too as you know. Personally, I would only flash if I had confidence in myself that it would work, having read up on the procedure and seen enough working examples. Others may just dive in and see what happens . Only you can decide if it's worth the risk or not, but these days I think it's quite rare to permanently brick a device if you fully understand the procedures and the risks. A stable recovery ROM makes a big difference. Not sure if the SGT has that yet.
paulshields said:
A stable recovery ROM makes a big difference. Not sure if the SGT has that yet.
Click to expand...
Click to collapse
It's in the works, just not quite there yet.
As Paul said, there's always going to be a risk it COULD happen. But following documentation and fully understanding the task at hand before diving in helps to limit the risks to a minimum.
Thanks to all of you for enlightening me
When I was flashing the different files to get calling on my ATT Tab I managed to flash the wrong file and get the device not to boot up but there was still the "download mode" to go into and I was then able to flash the correct file. I find it is very rare to actually "brick" a device requiring the device to be replaced or cracked open & reprogrammed manually. Most of the time now when a device is described as a brick it just won't boot the OS like it is normally supposed to.
paulshields said:
I think it's just a question of perception on the part of the person who "bricked" their device (the "brickie"? ). If you flash and find that you have what appears to be a dead device then you may well come on here and say "I've bricked my device!". You may then find that it's not bricked at all as there is a way (previously unknown to yourself) to recover. I remember in the old days on here people would pick up "bricked" phones on ebay etc, knowing that quite often they could recover them. It probably still happens...
But devices certainly can get permanently bricked too as you know. Personally, I would only flash if I had confidence in myself that it would work, having read up on the procedure and seen enough working examples. Others may just dive in and see what happens . Only you can decide if it's worth the risk or not, but these days I think it's quite rare to permanently brick a device if you fully understand the procedures and the risks. A stable recovery ROM makes a big difference. Not sure if the SGT has that yet.
Click to expand...
Click to collapse
Lol @ "brickie" - I guess you have to be British to get that one?
As for "bricking" , quite right, the device isn't "bricked" if it can be fixed by the user.
People have gotten sloppy with the term, but really it means that you could build a house with it if it were fat enough, but it's no more useful than an expensive paperweight.
The worst you can do without bricking is boot-loop/no-boot which can usually be fixed. The point is, if the device shows any signs of life whatsoever, it's usually fixable.
I thought I bricked my tab, I got the infamous "phone-!-pc" screen
http://forum.xda-developers.com/wiki/index.php?title=File:Samsung_Galaxy_S_Black_Screen_of_Death.jpg
I thought I was screwed. However, I still had it connected via USB and Odin still running and I saw that the com port popped up. I though, hmmmm
clicky and bam, its flashing.
Got it back.
This was after a stupid botched flash attempt on my part.
So, I think you REALLY gotta mess it up to be proper "bricked"
I did a lots of tries and I thing that is not that easy to brick, but I can give a suggestion: Backup the EFS folder!!!!!!!!!!!!!!
I deleted by mistake with root explorer the nv_data and relatives backups, and I had a corrupted IMEI that is not a brick but I think is one of the bad things (and hard to recover if not impossible if you don't have a backup) because if the carriers ban double IMEI the phone (tab) will not work + is not legal
Forgot to say: seems that some SGS firmware upgrades corrupted the IMEI too, I didn't see something flashing the TAB, but restoring the EFS folder will fix (almost always) the problems
I have not tried to brick my GT, but the JM6 gave me a scare... I have been flashing it for a while now.
The one thing you have to give up for now is SWYPE. I se you have a norwegian flag... And norwegian is not included in any flash I have found. So if you ever decide to try flashing. Say goodbye to SWYPE in norwegian for now...
Yeah, the loss of the Norwegian keyboard is the only thing stopping me from flashing jm6. Lucky for me, I'm very patient.
Sent from my HeTC Desire using XDA App
Apparently, you can brick it. I succeeded !
I flashed with Odin and a custom made PDA package including boot.bin but no repartition.
Odin flashed without problems but the Tab did not reboot and simply 'died'.
Black screen all the time, no recovery/download mode, not seen by the PC, does not charge on ac/dc (neither the charger or the PDA ever gets hot, no sound on connection, ...).
I'm letting the battery discharge completely (but how long can that take when it's not using any energy...) to test again tomorrow but I will probably RMA it on monday.
One thing that concerns me is not being able to remove the battery to force the phone to shut down completely.
As an example when I originally 'bricked' my SGS using Kies, no matter how many times I powered the phone it simply refused to go into Recovery or Download mode. All it would do was show me the two icons on screen.
The only way I managed to totally shut the phone down was by removing the battery and wait 30 seconds before returning. Only then would the SGS allow me to access the 3-Button Recovery/Download Mode.
So..... has anyone come across a situation where you needed to remove the battery and if so how did you manage to recover?
Beards said:
One thing that concerns me is not being able to remove the battery to force the phone to shut down completely.
As an example when I originally 'bricked' my SGS using Kies, no matter how many times I powered the phone it simply refused to go into Recovery or Download mode. All it would do was show me the two icons on screen.
The only way I managed to totally shut the phone down was by removing the battery and wait 30 seconds before returning. Only then would the SGS allow me to access the 3-Button Recovery/Download Mode.
So..... has anyone come across a situation where you needed to remove the battery and if so how did you manage to recover?
Click to expand...
Click to collapse
The worst I have done is get the device in the "Phone---!----PC" mode where you can't enter "Download Mode". It seems that simply flashing a new PIT file and then forcing it off, it will then enter download mode again.
alias_neo said:
The worst I have done is get the device in the "Phone---!----PC" mode where you can't enter "Download Mode". It seems that simply flashing a new PIT file and then forcing it off, it will then enter download mode again.
Click to expand...
Click to collapse
A little un-nerving isn't it... I have deep thoughts of not being able to get the Tab to drop out of memory by not being able to remove the battery and flush.
Beards said:
One thing that concerns me is not being able to remove the battery to force the phone to shut down completely.
As an example when I originally 'bricked' my SGS using Kies, no matter how many times I powered the phone it simply refused to go into Recovery or Download mode. All it would do was show me the two icons on screen.
The only way I managed to totally shut the phone down was by removing the battery and wait 30 seconds before returning. Only then would the SGS allow me to access the 3-Button Recovery/Download Mode.
So..... has anyone come across a situation where you needed to remove the battery and if so how did you manage to recover?
Click to expand...
Click to collapse
I think that when you leave/turn "USB Debugging" on in Applications -> Development, it is fairly save. As long as you are near a computer with adb installed and you have your usb cable within reach, you can reboot the device into recovery with adb reboot recovery or just reboot with adb reboot.
Another way is of course to let the battery run out of power, charge it and reboot.
appelflap said:
I think that when you leave/turn "USB Debugging" on in Applications -> Development, it is fairly save. As long as you are near a computer with adb installed and you have your usb cable within reach, you can reboot the device into recovery with adb reboot recovery or just reboot with adb reboot.
Another way is of course to let the battery run out of power, charge it and reboot.
Click to expand...
Click to collapse
Are you saying that the Tab will accept an "adb reboot" in it's unresponsive black screen state or some other? I'v not yet come across a state where just holding power didn't turn it off.
appelflap said:
I think that when you leave/turn "USB Debugging" on in Applications -> Development, it is fairly save. As long as you are near a computer with adb installed and you have your usb cable within reach, you can reboot the device into recovery with adb reboot recovery or just reboot with adb reboot.
Another way is of course to let the battery run out of power, charge it and reboot.
Click to expand...
Click to collapse
Running down the battery is an option... but it would take an age seeing as you're not doing anything with the phone except looking at two icons on a black screen.
alias_neo said:
Are you saying that the Tab will accept an "adb reboot" in it's unresponsive black screen state or some other? I'v not yet come across a state where just holding power didn't turn it off.
Click to expand...
Click to collapse
That thought passed me by as well.
alias_neo said:
Are you saying that the Tab will accept an "adb reboot" in it's unresponsive black screen state or some other? I'v not yet come across a state where just holding power didn't turn it off.
Click to expand...
Click to collapse
I did . I was fooling around with the button definitions of the tab, I lost all my buttons so to speak (also the powerbutton) and couldn't get into the system. A simple adb reboot got me out of there without any problem.
Yes, I believe adb can connect with the Tab in very unresponsive states and still issue commands. I've seen it also with my old galaxy S. A bad flash and a blank screen still gave me access to the system shell with adb.
My lesson learned is: alway have "USB Debugging" turned on.
Hi,
Not sure what is happening to my phone. I have had stock 4.2.2 rooted with CF auto root for months and had no problems. A few weeks ago my phone started to randomly shut down, not properly just complete power off in an instant. It would then start to reboot and get to the Samsung S4 logo screen before powering off again and trying to reboot and then gets stuck in a constant loop. At first I was able to just reinstall CF root with Odin and it would start up OK. I could also get it to start by re-installing Philz recovery.
Now though, that doesn't work so this morning I installed JB 4.3 I9505XXUEMK8-PRE-ROOTED-KNOX-FREE-ODEX-FULL.tar.MD5 and it says that it is rooted and everything seems to be OK but after an hour or so it has started to randomly shut down again. If I attempt to go into recovery (stock) and clear the cache partition it will reboot normally and run for a while until I use an app and do it again. Am I doing something wrong here or is my phone just knackered?
Phooka
Maybe is coz the RAM is overloaded. Take a look in:
- Press HOME button for 2 secs
- U will see 3 icons in the bottom. Click on the "cheese"
- Tab "RAM"
- If ur phone use more of 1 GB of RAM for run ur apps maybe will be time of delete bloatware
I had the same problem in GT-I9500, I had to get it repaired in a service center.
There was a problem with mother board to charger port connection..
Hope it helps you!
Random Shutdown
praveen_kalasa said:
I had the same problem in GT-I9500, I had to get it repaired in a service center.
There was a problem with mother board to charger port connection..
Hope it helps you!
Click to expand...
Click to collapse
Thanks. Probably not as I've been told that warrantee will be void now as I've flashed whilst having Knox installed which I understand to be irreversable
random shuts and boot loops
Joku1981 said:
Maybe is coz the RAM is overloaded. Take a look in:
- Press HOME button for 2 secs
- U will see 3 icons in the bottom. Click on the "cheese"
- Tab "RAM"
- If ur phone use more of 1 GB of RAM for run ur apps maybe will be time of delete bloatware
Click to expand...
Click to collapse
Thanks. its running at 1.04 out of a possible 1.78G. When cleared it drops to 847 MB.
I Am Phooka said:
Thanks. its running at 1.04 out of a possible 1.78G. When cleared it drops to 847 MB.
Click to expand...
Click to collapse
If u wanna try to recover some RAM u can delete some bloatware that u dont use. Tc with what u delete. I let u some info about if u wanna try -> HERE
I have this problem, I swear it is because of the dodgy battery. (I have the BD battery)
When I plug it in to charge all works again properly.
Last night my battery was showing in the high 60's the phone went off. When I put charger in the battery was at 3%!
Very annoying, going to take to Geek Squad tonight and see if they wil lreplace battery. Guy here at work has same phone, different battery derial number and no problems at all.
Hopefully they will change the battery, I don't have any paperwork with me but the phone is obviously within the 1 year warrenty.
Random Shutdown and boot loop
choccy31 said:
I have this problem, I swear it is because of the dodgy battery. (I have the BD battery)
When I plug it in to charge all works again properly.
Last night my battery was showing in the high 60's the phone went off. When I put charger in the battery was at 3%!
Very annoying, going to take to Geek Squad tonight and see if they wil lreplace battery. Guy here at work has same phone, different battery derial number and no problems at all.
Hopefully they will change the battery, I don't have any paperwork with me but the phone is obviously within the 1 year warrenty.
Click to expand...
Click to collapse
Interesting. I have noticed a couple of times when I look at the battery stats that it has drained from say 90% to 3% in less than 1min, just a verticle line. When I plug it in to charge it says that it's at 90% or whatever it was. Other times it needs charging and is almost dead. It's as though it has shorted out. I wonder if that is the problem here.
random shuts and boot loops
Joku1981 said:
If u wanna try to recover some RAM u can delete some bloatware that u dont use. Tc with what u delete. I let u some info about if u wanna try -> HERE
Click to expand...
Click to collapse
Thanks for that. It's quite a list. I'll go through it and remove the ones i think i can do without and see how it goes.
Same Issue
I have the same problem with my I9505
- It shuts down randomly (sometimes you see a few seconds in advance that your connection to the mobile antennas disconnects), when you look at it, in the middle of a phonecall, ... whenever it's nog plugged in to the power of external battery
- It's almost impossible to get it powered on again (gets stuck in a loop of rebooting: most times at the Samsung logo or after it's on for a few seconds), unless you connect your charger that is connected to the powergrid or external battery
- sometimes it resets the phonelanguage to default (so in stead of for example Dutch, everything is in English again)
I just cleared the cache and removed some programs...
Fingers crossed
--> I'll give an update if anything changes
Random Shutdown and boot loop
LinusN said:
I have the same problem with my I9505
- It shuts down randomly (sometimes you see a few seconds in advance that your connection to the mobile antennas disconnects), when you look at it, in the middle of a phonecall, ... whenever it's nog plugged in to the power of external battery
- It's almost impossible to get it powered on again (gets stuck in a loop of rebooting: most times at the Samsung logo or after it's on for a few seconds), unless you connect your charger that is connected to the powergrid or external battery
- sometimes it resets the phonelanguage to default (so in stead of for example Dutch, everything is in English again)
I just cleared the cache and removed some programs...
Fingers crossed
--> I'll give an update if anything changes
Click to expand...
Click to collapse
I've tried that as well. Didn't work. The problem you describe is exactly the problem I have. I have ordered another battery but I don't think it's that. I'll let you know if it is. I hadn't noticed that it always boots OK if it is plugged into the mains. Wish I knew what was causing the problems.
Random Shutdown and boot loop
So I think I am finally getting somewhere. I took this screenshot straight after it shut down and got stuck in a boot loop. So I plugged it into the mains and it started OK. The battery just gives up when i stress the device with a hungry app or when booting which causes a heavy drain on the on the power even when its got a healthy charge. Got a new battery on order. Take a look at the screenshot. You can see the battery instantaneously drops to zero charge until it's re-booted on the mains.:laugh:
LinusN said:
I have the same problem with my I9505
- It shuts down randomly (sometimes you see a few seconds in advance that your connection to the mobile antennas disconnects), when you look at it, in the middle of a phonecall, ... whenever it's nog plugged in to the power of external battery
- It's almost impossible to get it powered on again (gets stuck in a loop of rebooting: most times at the Samsung logo or after it's on for a few seconds), unless you connect your charger that is connected to the powergrid or external battery
- sometimes it resets the phonelanguage to default (so in stead of for example Dutch, everything is in English again)
I just cleared the cache and removed some programs...
Fingers crossed
--> I'll give an update if anything changes
Click to expand...
Click to collapse
in the list I forgot to mention that the known wifi's are also wiped. --> you have to connect to them again...
I too am having this exact problem; I'm glad to hear it is not only me, not that it helps any of us.
I posted in another thread, but the symptoms everyone here are describing are exactly what I am seeing:
- Sudden battery drop from anything (it's happened to me before about 5 minutes after unplugging from the wall socket) to zero; then phone goes into a loop unless I plug it back into the mains socket
- When plugging into the mains socket with this issue, sometimes the battery is empty and sometimes it shoots straight back up to where it was
- Plants Vs Zombies 2 is the sure-fire way for me to reproduce this issue
- examined logs (although not sure if the right one) using CatLog; nothing obvious (in fact the last line on one of the logs is litterally cut halfway through)
- Wifi connection details lost occasionally
I have reflashed about 4 other (4.3) ROMs (and I tried a 4.4 GE one too) and they all seem to do the same; I am wondering if it is something to do with the non-Knox modems required to flash the 4.3 ROMs as I don't think I had this problem before updating to 4.3. I don't have the time or patience to revert back to a 4.2 ROM to test this though.
I can go for a couple of days without this happening, but fire up PvZ2 and here we go again.
I too have a new battery on order (allegedly genuine from a well-known auction site), so I will update this thread when that arrives to see if it makes any difference.
I don't like this post for one reason.... it means that the problem I am facing won't solve with a format and a new fresh flash... :crying:
I was spending some time on XDA searching for a good stable firmware to flash because I am having your exactly same issues on my phone... I just tought my phone got a bit messy because I have 130 apps installed and a lot of stuff on it.. so I was just thinking of solving all my problems with a new rom... but then I found this 3d...
So you are telling me that my problem won't get solved so easely? How am I going to deal with a Phone that randomly shuts up??? I need my phone and over the last week it got always worse.. first it shut up at about 5pm.. (at ca 15% charge) then at 3pm and 50% charge... today it shut up at 11am and 80% charge... soon I won't be able to use my phone at all!!
I'm happy I backed up all my data today, but it still doesn't solve my problem since I really need my phone... :crying:
This evening I'm going to flash anyway... let's see what happens..
PS I own a GT-I9505 with 4.2.2 stock rom (root)
Random Shutdown and boot loop
Sorry to hear there's a few more out there with the same problem that I am having. AhHm... Sorry, WAS having. I tried re-flashing all sorts of ROMS from 4.2.2 to Echoe KitKat 4.4, flashed CF Root, reinstalled philz touch recovery god knows how many times all to no avail. I now know that it is nothing to do with your ROM or phone setup. It's Samsungs crappy battery. As soon as I put in my new battery problems solved. I have been running multi-window apps whilst having FB on in the background and watching a film all at the same time. If this was gonna crash it would have done by now.
Problem solved. Don't buy the cheap SPB £9.99 one on ebay it has lots of bad reviews. I got this one with no problems:
http://www.ebay.co.uk/itm/GENUINE-S...114?pt=LH_DefaultDomain_3&hash=item3f278d6f32
Hope this helps and don't forget the thanks meter.
I Am Phooka said:
Problem solved.
Click to expand...
Click to collapse
I'm glad you solved.. this means there could be a solution to my problem... in any case the fact that alla batteries here seem to fail in the same week is really strange!!
And the thing I hate most is that a 500€ phone shouldn't be dying after just some months!
After having spent some time googling around.. I found a solution... well, not exactly a solution... let's say I found the core of the problem...
I found some very interesting posts on the misfuncion on all Samsung S4 Batteries Made and Produced in China with SN starting with BD....
And guess what? my battery corresponds!!
If you look at the battery you will notice that it is a little "bumped" and not perfectly flat...
Here in Italy many users went to samsung customer service and got the battery replaced!
Tomorrow I will check to see if I can get a new battery... for now I'm happy to know exactly what to do in order to get my phone working again!
Samsung Batteries beggining with BD.
I Am Phooka said:
Sorry to hear there's a few more out there with the same problem that I am having. AhHm... Sorry, WAS having. I tried re-flashing all sorts of ROMS from 4.2.2 to Echoe KitKat 4.4, flashed CF Root, reinstalled philz touch recovery god knows how many times all to no avail. I now know that it is nothing to do with your ROM or phone setup. It's Samsungs crappy battery. As soon as I put in my new battery problems solved. I have been running multi-window apps whilst having FB on in the background and watching a film all at the same time. If this was gonna crash it would have done by now.
Problem solved. Don't buy the cheap SPB £9.99 one on ebay it has lots of bad reviews. I got this one with no problems:
http://www.ebay.co.uk/itm/GENUINE-S...114?pt=LH_DefaultDomain_3&hash=item3f278d6f32
Hope this helps and don't forget the thanks meter.
Click to expand...
Click to collapse
nioBee said:
After having spent some time googling around.. I found a solution... well, not exactly a solution... let's say I found the core of the problem...
I found some very interesting posts on the misfuncion on all Samsung S4 Batteries Made and Produced in China with SN starting with BD....
And guess what? my battery corresponds!!
If you look at the battery you will notice that it is a little "bumped" and not perfectly flat...
Here in Italy many users went to samsung customer service and got the battery replaced!
Tomorrow I will check to see if I can get a new battery... for now I'm happy to know exactly what to do in order to get my phone working again!
Click to expand...
Click to collapse
Yeah I found that out tonight also. I called samsung earlier today and they said if it is less than 2 years old they will repair it and I should send it to them. I have flashed so many ROMS since I purchased it last year and one or two with Knox which as we know registers that it has had a custom download which voids the warrantee so I thought it would be a waste of time sending it to them. Also I need my phone for work so it was easier to purchase a new battery.
Bad samsung batteries
nioBee said:
After having spent some time googling around.. I found a solution... well, not exactly a solution... let's say I found the core of the problem...
I found some very interesting posts on the misfuncion on all Samsung S4 Batteries Made and Produced in China with SN starting with BD....
And guess what? my battery corresponds!!
If you look at the battery you will notice that it is a little "bumped" and not perfectly flat...
Here in Italy many users went to samsung customer service and got the battery replaced!
Tomorrow I will check to see if I can get a new battery... for now I'm happy to know exactly what to do in order to get my phone working again!
Click to expand...
Click to collapse
Hi,
Do you have a link to the info? was it on an official samsung site?
Hi there,
My phone not turning on not without battery and SD not with home and volume+ and power button not with both volumes and power nothing at all not even vibrating when charging I am not sure if it's the battery but it was charged before I rebooted once rebooted it didn't turn back on I am on aurora ics and cwm.
I didn't have any problems with it partitions might of been wiped but I guess this would leave me with access to bootloader or anything or a vibrate on charge at least it happened as I was formatting another device but put the wrong sd on ubuntu so I started to think it might be the battery except it was charged unless it decided to leak all the charge in no time.
Also it doesn't do anything on usb or charge connection no vibrate no led no light buttons no nothing just nothing.
Sounds like my issue...
If in fact you did format the whole 3.69gb partition, then you wiped the phone.
So far, my only recourse has been to attempt a JTAG and install a bootloader.
I'm thinking that maybe I can try some form of "wire trick", like the ones used on the HTC Sensation, but I don't want to blow it up by shorting something unrepairable.
If you find another solution, please reply as it would be helpful to others.
PoXFreak said:
Sounds like my issue...
If in fact you did format the whole 3.69gb partition, then you wiped the phone.
So far, my only recourse has been to attempt a JTAG and install a bootloader.
I'm thinking that maybe I can try some form of "wire trick", like the ones used on the HTC Sensation, but I don't want to blow it up by shorting something unrepairable.
If you find another solution, please reply as it would be helpful to others.
Click to expand...
Click to collapse
nope i didnt format 3.96 gb it was 3 mb and it was shown as linux cd gadget also it worked afterwards until i rebooted next day then blackness the thing is i cant seem to find a battery to try with so i need to try everything first
The one I have here wouldn't start charging the battery until I force-fed the battery directly. (use a 4-5v charger and directly charge the battery for a couple of minutes).
Mine worked, but I made the mistake of formatting the entire partition (3.69gb), so now the phone does absolutely nothing.
PoXFreak said:
The one I have here wouldn't start charging the battery until I force-fed the battery directly. (use a 4-5v charger and directly charge the battery for a couple of minutes).
Mine worked, but I made the mistake of formatting the entire partition (3.69gb), so now the phone does absolutely nothing.
Click to expand...
Click to collapse
I am a bit confused here so now when you plug it you can do something to it since it's charging? I guess I never did the 3.69 thingy if I am not mistaken..So lemme ask you if I tried the wall outlet for example instead of the USB to tv or laptop would that help to start it? I am thinking of replacing the battery and see what happens that's if I can find it here in Turkey the Turks always into the newest phones so this one is ancient to them to find a battery for...
Mine is in the same state. But I know that in my efforts to get it to start again I accidently wiped the the entire partition. Can't turn it on, can't get a pink screen, not a thing and haven't beenable to find any solution. So I guess all I can do is sit back and check the postings to see if anyone else has the same issue and knows of a way to restore the boot partition.
Burtrum57 said:
Mine is in the same state. But I know that in my efforts to get it to start again I accidently wiped the the entire partition. Can't turn it on, can't get a pink screen, not a thing and haven't beenable to find any solution. So I guess all I can do is sit back and check the postings to see if anyone else has the same issue and knows of a way to restore the boot partition.
Click to expand...
Click to collapse
I'm thinking of trying to run MTTY 1.42 and talk directly with the qualcomm chip to send the boot files myself, but I need to know what I need and where it goes first.
I did this with the HTC Kaiser (AT&T Tilt) with some success.
That was on Windows XP though...not sure if it will run correctly on Win 7.
PoXFreak said:
I'm thinking of trying to run MTTY 1.42 and talk directly with the qualcomm chip to send the boot files myself, but I need to know what I need and where it goes first.
I did this with the HTC Kaiser (AT&T Tilt) with some success.
That was on Windows XP though...not sure if it will run correctly on Win 7.
Click to expand...
Click to collapse
help me i have the same issue....
service
May be best option is to take it to service center.
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.
hello my question is simple
....well not that simple or i wouldnt be here but ill get to the point quikly then!
ive had 3x note 4 910G all die from emmc read fail after freezing,reboots,non starts,lagging etc.2 of th Ed 3 would have been lucky to see over 10-15 flashes of anything each now can someone please inform me of maybe one or two reasons that are the main causes of motherboard failure
only factors id like to add that may help and thats the one or two times the phones became hot from either charging or in direct sun as i work outdoor.
im about to purchase a 4th as after my upgrade as my contract expired and recieved the note 5 and its just not cricket LONG LIVE THE 4!
I don't know if this is gonna help you but I hope it does. I still consider myself a noob when it comes to rooting, flashing and roms in general so please take all this with a grain of salt.
I too have an 910G and have seen this emmc read fail a few times while playing around with different Note7 roms. The setup I have going at the moment though doesn't have the emmc read fail, but it does have other issues. I'll explain what they are later but I'd rather have the current issues I have now rather than the emmc read fail.
My current setup is this
Note7 Rom - Aurora v4.1
Kernel Version 3.10.40 H-Vitamin
Bootloader - N910GDTS1DPK2
Baseband - N910GDTU1DPF4
THE ISSUES
1. I have to have AOD turned on. If I don't have it turned on and the screen automatically turns off after five minutes it won't come back on again. I have to remove the battery to get it to boot up and work properly again.
2. Restarting/Rebooting. It doesn't work. It will just hang. If you want to reboot your phone you have to do a shutdown. And not just any shutdown. I kid you not if I don't do this my Note4 WILL NOT boot...
1. Shutdown Note4
2. Remove battery
3. Hold down power button for at least 10 seconds
4. Put it in a ziplock bag and place it in the fridge for 10 minutes.
5. Remove from fridge, insert battery and it will boot normally.
Again, I'm not joking about the fridge thing. I read about it in a Note4 de-brick thread. I didn't believe it when I read but one day I bricked my Note4 so I thought what the hell, it can't hurt to try. And blow me down it worked!
So that was my fix anyway. AOD does'nt work perfectly. It messes up your auto brightness but there is a workaround. You just have to wake up the sensor. To do that you just turn on your screen with the Home or Power button, then immediately turn it off again with the power button. Immediately proceeding that turn the screen on again with the Home button and it will readjust to the light in the room or environment you are in.
I hope that helps. And yes, long live the Note4! When I had to return my 2nd Note7 my carrier offered me any other phone, including the Note5. I asked to go on a sim only plan and went back to my Note4. Nothing out there at the moment grabs me atm. Not even the S8. I need my sPen! Waiting patiently for the Note8.
Sent from my iPad using Tapatalk
Jad Morffier said:
I don't know if this is gonna help you but I hope it does. I still consider myself a noob when it comes to rooting, flashing and roms in general so please take all this with a grain of salt.
I too have an 910G and have seen this emmc read fail a few times while playing around with different Note7 roms. The setup I have going at the moment though doesn't have the emmc read fail, but it does have other issues. I'll explain what they are later but I'd rather have the current issues I have now rather than the emmc read fail.
My current setup is this
Note7 Rom - Aurora v4.1
Kernel Version 3.10.40 H-Vitamin
Bootloader - N910GDTS1DPK2
Baseband - N910GDTU1DPF4
THE ISSUES
1. I have to have AOD turned on. If I don't have it turned on and the screen automatically turns off after five minutes it won't come back on again. I have to remove the battery to get it to boot up and work properly again.
2. Restarting/Rebooting. It doesn't work. It will just hang. If you want to reboot your phone you have to do a shutdown. And not just any shutdown. I kid you not if I don't do this my Note4 WILL NOT boot...
1. Shutdown Note4
2. Remove battery
3. Hold down power button for at least 10 seconds
4. Put it in a ziplock bag and place it in the fridge for 10 minutes.
5. Remove from fridge, insert battery and it will boot normally.
Again, I'm not joking about the fridge thing. I read about it in a Note4 de-brick thread. I didn't believe it when I read but one day I bricked my Note4 so I thought what the hell, it can't hurt to try. And blow me down it worked!
So that was my fix anyway. AOD does'nt work perfectly. It messes up your auto brightness but there is a workaround. You just have to wake up the sensor. To do that you just turn on your screen with the Home or Power button, then immediately turn it off again with the power button. Immediately proceeding that turn the screen on again with the Home button and it will readjust to the light in the room or environment you are in.
I hope that helps. And yes, long live the Note4! When I had to return my 2nd Note7 my carrier offered me any other phone, including the Note5. I asked to go on a sim only plan and went back to my Note4. Nothing out there at the moment grabs me atm. Not even the S8. I need my sPen! Waiting patiently for the Note8.
Click to expand...
Click to collapse
Hello sir, if i understand right you have an hardware issue, like a cold-soldering circuit.. When the motherboard reaches cold temp it contracts and due to contraction "bad circuit" makes contact with motherboard and everything works fine for a while.. Does the phone crashes during intense usage? (battery / motherboard / screen reaching hot temp?)
Daniel RR said:
Hello sir, if i understand right you have an hardware issue, like a cold-soldering circuit.. When the motherboard reaches cold temp it contracts and due to contraction "bad circuit" makes contact with motherboard and everything works fine for a while.. Does the phone crashes during intense usage? (battery / motherboard / screen reaching hot temp?)
Click to expand...
Click to collapse
I actually have no abnormal issues. It warms up a little when charging but once it gets to 100% it gets cold again. There are no phone crashes during intense usage. It runs rather well. I reboot it once a week like I've always done with mobile phones as OS memory leaks build up over time.
Sent from my iPad using Tapatalk
Probably a bad batch. Mine has been working fine for two years and still going, I even used it a lot for Waze outdoor and it gets extremely hot, killed the battery but nothing else. Mine was the Exynos though.
adzo73 said:
hello my question is simple
....well not that simple or i wouldnt be here but ill get to the point quikly then!
ive had 3x note 4 910G all die from emmc read fail after freezing,reboots,non starts,lagging etc.2 of th Ed 3 would have been lucky to see over 10-15 flashes of anything each now can someone please inform me of maybe one or two reasons that are the main causes of motherboard failure
only factors id like to add that may help and thats the one or two times the phones became hot from either charging or in direct sun as i work outdoor.
im about to purchase a 4th as after my upgrade as my contract expired and recieved the note 5 and its just not cricket LONG LIVE THE 4!
Click to expand...
Click to collapse
Sir, there is one fix I know for this cause and it seems to work for all note 4 users who face this problem.
We all have to install this app called wakelock , you can search up the google store.
This happens in snapdragon variants mostly as of I heard. When system goes to deep sleep mode the restart and stuff happens this wakelock app would stop phone from going off deep sleep and fix the issue.
Here is a 100% hardware fix for this issue that anyone can do with no tools or specia
Here is a 100% hardware fix for this issue that anyone can do with no tools or special equipment.
It really works. Give it a try. ?
https://youtu.be/jLPHWtb0StI