Related
Ok I have a very silly question. Does flashing too much harm the nand ?im flashing a hell lot of roms and kernels. Asking it because to go from sgs rom to nexus s port I have to flash the kernel each time and im playing with it. Also I like trying cm nightly builds. From what I've learned kernels are flashed to same nand and the nand has wear levelling capability.
I an very far from usa and have the vibrant.so don't want to destroy it beyond print or ill have a 500$ brick.
Any enlightment on this would be appreciated. Thanks
Sent from my SGH-T959 using Tapatalk
I think nand chips like most solid state memory support writes several hundred thousand times. So you should be good.
Sent from my SGH-T959 using XDA App
Any writes performed on the device decrease it's lifespan. Whether it's done by flashing, installing apps, loading various media on it, etc. You shouldn't need to worry too much about it. Even a serial flasher's phone will likely brick (for other reasons) before the SD card gives out, I'd think.
Solid state flash indeed has a limited number of write cycles. However, it is unlikely that you'll encounter this within the normal lifetime your phone. Several hundred thousand write cycles should be possible before it expires. SD cards also include circuitry to manage "wear-leveling". This spreads writes over the whole of the storage media to try to avoid writing to various frequently written locations too often which could cause premature failure.
Thanks guys.....ya I was thinking the same but since 2 gb is partitioned for the system ,i started thinking what if I messed that 2gb partition.but I guess wear levelling will use whole nand chip to manage wear.
Sent from my SGH-T959 using Tapatalk
Hi Friends,
Everything was fine until my HD2 it turned off and since then ( two weeks ago) all it shows me when I turn it on is a black and white striped page( it goes to bootloader mode though and everything is fine,! it's not a hardware problem) . I've tried everything you name it,( Flashing via SD card, Using Mtty, Usin diff radios, and a buch of other stuff) I have the T-mobil insurance plan where I'll tell them the problem and they will send me a new phone, all I need to do is to get rid of that CotullaHSPL so that they wont find out that the phone has been messed with. So, My question is how do you recover to the original SPL, ((I've tried uninstalling the HSPL and it goes all the way to 100 but once the phone restarts and I go to bootloader it still shows me "CotullaHSPL"
Thanks,
Amir Najafi
its a reasonably common problem, , radio gets stuck, flashing appears to work but doesnt.
there are some out there threads about chilling it for half an hour, flashing certain test roms and the like, but there is no real answer to it. (not taht ive seen)
you could always try flashing a non tmous stock rom, (with a 51 radio) and hoping it takes enough to brick it completely, or go for the ten seconds in a microwave option, but ive always thoughtthe danger of exploding teh screen a bit much.
samsamuel said:
its a reasonably common problem, , radio gets stuck, flashing appears to work but doesnt.
there are some out there threads about chilling it for half an hour, flashing certain test roms and the like, but there is no real answer to it. (not taht ive seen)
you could always try flashing a non tmous stock rom, (with a 51 radio) and hoping it takes enough to brick it completely, or go for the ten seconds in a microwave option, but ive always thoughtthe danger of exploding teh screen a bit much.
Click to expand...
Click to collapse
I have accidental on the phone worse comes to worse, I'll just do that, I've heard of freezing it for half an hour, but would that really work?!
lol, no idea, ,
i can imagine a scenario where corrupt software is overpowering the hardware so much that it is failing, and that cooling it may allow it to work past its thermal limits just long enough to flash, , , but its more like an old wives tale, an urban legend really, doing somethng just because someone else did it and it worked i think, luck of the draw. 1 - freeze phone - 2 - into bootloader - 3 - sacrifice chicken - 4 - flash hspl - 5 - recite ' arr ay dee eye ohh ' over and over - 6 - flash radio.... hehehe.
samsamuel said:
lol, no idea, ,
i can imagine a scenario where corrupt software is overpowering the hardware so much that it is failing, and that cooling it may allow it to work past its thermal limits just long enough to flash, , , but its more like an old wives tale, an urban legend really, doing somethng just because someone else did it and it worked i think, luck of the draw. 1 - freeze phone - 2 - into bootloader - 3 - sacrifice chicken - 4 - flash hspl - 5 - recite ' arr ay dee eye ohh ' over and over - 6 - flash radio.... hehehe.
Click to expand...
Click to collapse
HA HA HA HA HA HA HA HA HA
That is the funniest sh*t I have heard all day.
Now as for the op's problem, if the phone feels hot after you try the flashing or after you leave it on for a while then you might have a processor that is slowly frying itself are causing itself to lose it's connections to the mother board because of the heat.
I know you said you tryiex everything but go get yourself a cheap 2GB SD card and format it even though it is new and the use it to put you ROM on e ergonomics time you try a ROM and try to flash via your SD card. If one ROM does not work delete it from the SD card download another and copy it to the SD card and try to flash it. One of them had got to eventually flash. Just be aware that if you flash any official ROM via SD card it will revert you back to SPL and you will have to reflash HSPL
I've tried the chilling thing btw, lol, it didnt work hahaha
Tonight was second time in about one week when my phone shut itself down at night. Because of that I slept in both times Both times it was connected to charger and battery was full, also there was a lot of updated apps (notifications in status bar). Right before first time this happened I recovered from soft brick. First after recovering phone didn't work well it use to freeze on higher load so I re-installed stock ROM one more time and everything seemed fine.
Now I wonder if it's software or hardware issues. Any ideas?
Cheers in advance.
kaiseris said:
Tonight was second time in about one week when my phone shut itself down at night. Because of that I slept in both times Both times it was connected to charger and battery was full, also there was a lot of updated apps (notifications in status bar). Right before first time this happened I recovered from soft brick. First after recovering phone didn't work well it use to freeze on higher load so I re-installed stock ROM one more time and everything seemed fine.
Now I wonder if it's software or hardware issues. Any ideas?
Cheers in advance.
Click to expand...
Click to collapse
Did you UV/UC your device? And which rom/kernel are you on?
Sent from the Matrix
Donnie Sins said:
Did you UV/UC your device? And which rom/kernel are you on?
Sent from the Matrix
Click to expand...
Click to collapse
No, I didn't UV/UC. I was on rooted stock kernel.
Made factory reset today and installed custom JB ROM today to see if it helps.
I think your problem is a software related one, try using the latest stock Rom, also it may be induced bya virus or a new program which you May have installed, if this didn't help them you should think of a hardware problem.
iper said:
I think your problem is a software related one, try using the latest stock Rom, also it may be induced bya virus or a new program which you May have installed, if this didn't help them you should think of a hardware problem.
Click to expand...
Click to collapse
I was using 4.0.4 official ROM (NEE). And most of my apps are from Play store and only few from a reputable forum.
But as I said, I wiped everything today and installed a different ROM. If everything's OK for a week it will be clear that it was a software glitch.
Maybe it's tired?
****Non of this is of any importance. Just chill the f**k out and relax****
One week after installing custom ROM my SGSII has shutdown at night again. Like last times it was connected to a charger but this time there were no updated apps. So it's not ROM's fault because it happened with custom and stock ROMs.
Is it possible that soft brick damaged some part of phone's hardware (internal flash memory)? When recovering from brick I re-partitioned it.
...
MistahBungle said:
1) There's no such thing as a 'soft brick'. Your phone is either bricked (unfixable other than by authorised repairer/JTAG) or it ain't.
2) Highly unlikely anything firmware related would cause hardware issues like that.
It may well be a hardware issue given it's happened on different roms. If you're still on stock & haven't reset the flash counter, do that & send it in to Samsung/authorised repairer to be looked at assuming your warranty is still good. If it isn't, take it to a local mobile repair shop & have them take a look (if you've gone back to a custom rom, reset the flash counter & back to stock).
Click to expand...
Click to collapse
There's no warranty, therefore I won't be taking it to service center just to hear it needs new motherboard etc. because it'll cost me almost same as to buy another SGSII.
At this moment I'm only interested if there's anything I can do by myself. If not it's time for a new phone I'm afraid. The phone is still perfectly usable but I don't want to risk sleeping in and being late for work and I don't want to buy an alarm clock.
Common sense dictates you try a different battery.
TheATHEiST said:
Common sense dictates you try a different battery.
Click to expand...
Click to collapse
How can it be caused by battery when all times this happened phone was connected to a charger? All times after I turn it on I find a full battery.
...
MistahBungle said:
Do a completely clean install of stock (format cache, data, system, & internal sd card in CWRecovery first, Odin flash after), do not restore any apps (or app data with the exception of contacts/calendar/call logs/sms) via Ti or whatever, clean reinstall a few apps at a time, test for a day or two. Install a few more apps, test for a day or two. And so on.
If it's still happening after you do that, "it's time for a new phone" in your words.
Click to expand...
Click to collapse
Thing is that when the phone got bricked I had no backup of any kind and since internal storage was re-formated we can say that it was fully wiped. I installed stock ROM first. But phone was rebooting on higher load so I did factory reset and wiped dalwik and data. Reinstalled stock ROM again (even re-downloaded to make sure it's not corrupted). This time it wasn't rebooting. But after a couple of night shutdowns I decided to try a custom ROM. I did a full wipe (including internal storage) before installing it. Clearly it didn't help
BTW night shutdown happens about once in a week.
kaiseris said:
How can it be caused by battery when all times this happened phone was connected to a charger? All times after I turn it on I find a full battery.
Click to expand...
Click to collapse
I tried a different battery and Ive noticed when Ive connected it to the charger,a couple of times my phone has switched off as I was facing the screen wanting my sim pin.
This doesnt happen with my original battery.
So it must be the battery.
theunderling said:
I tried a different battery and Ive noticed when Ive connected it to the charger,a couple of times my phone has switched off as I was facing the screen wanting my sim pin.
This doesnt happen with my original battery.
So it must be the battery.
Click to expand...
Click to collapse
But I'm using my original battery. Also like I mentioned earlier all this started after the brick. Therefore I don't think it's the battery.
P.S.Before SGSII I owned HTC Desire for couple of years. I flashed and re-flashed it again and again, never had a brick etc. But when I decide to flash a custom ROM on SGSII for the first time phone gets bricked and even after recovering from brick phone is still f*****-up. Don't get me wrong I love this phone, it's better in every way but it's not exactly "flash friendly". Forums are full of stories of bricked SGSII. That makes me thinking should I choose a Samsung device if I'll be forced to buy a new phone...
kaiseris said:
How can it be caused by battery when all times this happened phone was connected to a charger? All times after I turn it on I find a full battery.
Click to expand...
Click to collapse
Simple, Because you cant run your phone just via charger, it goes from charger to device via battery so if your battery is faulty you could have lost power to device.
kaiseris said:
Thing is that when the phone got bricked
Click to expand...
Click to collapse
You're devcie was never "bricked". If it was your devcie would simply not power on or if it did it wouldnt go into download or recovery mode via buttons or jig.
If you can do the above yor devcie is not bricked. There is no such thing as a "soft brick", that is just a label n00bs like to use as a label for when they cant boot to system. Liek when they get a boot loop etc.
kaiseris said:
But I'm using my original battery. Also like I mentioned earlier all this started after the brick.
Click to expand...
Click to collapse
No it didnt.
kaiseris said:
P.S.Before SGSII I owned HTC Desire for couple of years. I flashed and re-flashed it again and again, never had a brick etc.
Click to expand...
Click to collapse
And you haven't on SGS2 either.
kaiseris said:
But when I decide to flash a custom ROM on SGSII for the first time phone gets bricked
Click to expand...
Click to collapse
No it doesnt.
kaiseris said:
and even after recovering from brick phone is still f*****-up.
Click to expand...
Click to collapse
No you didnt, you simply re-flashed a rom. When you're bricked this cannot be done (without hardware access/replace) hence the word "bricked"[/QUOTE]
kaiseris said:
Don't get me wrong I love this phone, it's better in every way but it's not exactly "flash friendly".
Click to expand...
Click to collapse
Wrong, its very flash friendly. Only thing you need to look out for is wiping data on leaked stock kernel.
kaiseris said:
Forums are full of stories of bricked SGSII.
Click to expand...
Click to collapse
1000% Untrue. They are full of stories from n00bs who "think" they have bricked their device, ie all the silly "soft-brick" topics.
My advice to you would be to check battery pins for bends or corrosion and also swap battery and see if you get different results.
Before any of this though you should try a kernel cleaning script, flash stock rom via ODIN and then flash Siyah kernel.
Jeez man! Why do you waste your an my time typing this long but pointless post?! To show how "l33t" you are? If so please stay away from this thread.
As for battery, if it is faulty why it's still fully charged? Also why does it act-up just once in a while? IMHO battery is quite a simple thing, either it charges or not. It looses it's capacity over time. Mine is about six months old and still lasts me about 36 hours.
kaiseris said:
Jeez man! Why do you waste your an my time typing this long but pointless post?! To show how "l33t" you are? If so please stay away from this thread.
As for battery, if it is faulty why it's still fully charged? Also why does it act-up just once in a while? IMHO battery is quite a simple thing, either it charges or not. It looses it's capacity over time. Mine is about six months old and still lasts me about 36 hours.
Click to expand...
Click to collapse
Because I was trying to help you [email protected] ungrateful moron! How on earth was it trying to sound "l33t" (By the way its "1337").
Your problem is that you create a thread about a problem you have with device and then dont even listen to what you get told with regards to advice from multiple people, ie check rom/kernel/battery. What the hell do you expect any of us to do give you some magic words you can say to solve your problem?
What I wrote was correcting your misconceptions and giving you on advice on how to resolve your issue, Did you even bother to read what I wrote at bottom??
Also you're been very narrow minded if you think that the only symptoms of a faulty battery is if it cant charge or hold charge. Symptoms can also include random drops of output which result in your phone losing power and rebooting or powering off which is exactly what is happening to you. Now I'm not saying this is your exact problem but the fact that you are ignoring this possibility shows how much of a fool you are been especially when been hostile towards people who are trying to "waste their time" helping you.
If you dont want our advice then I suggest you GTFO and find another site to post your problem on.
TheATHEiST said:
n00bs
Click to expand...
Click to collapse
TheATHEiST said:
n00bs
Click to expand...
Click to collapse
TheATHEiST said:
[email protected] ungrateful moron
Click to expand...
Click to collapse
TheATHEiST said:
a fool you are
Click to expand...
Click to collapse
Wow, you're a real "keyboard cowboy". Do you tell same thing to people you don't know in real life? I bet you don't.
I already wrote this but I will repeat it one more time. I did full wipes, flashed a few different ROMs and kernels since this problem started. It didn't affect the problem in any way!
TheATHEiST said:
Now I'm not saying this is your exact problem
Click to expand...
Click to collapse
Reading your posts makes me think opposite. I will repeat myself shutdowns started right after recovering from "soft brick"/"NAND rw corruption" (which ever suits you better). Other reason I don't believe it's battery's fault is that I have never heard about:
TheATHEiST said:
random drops of output
Click to expand...
Click to collapse
in otherwise perfectly working battery.
Like everyone else I owned a bunch of cellphones, laptops, cordless drills, MP3 players and other battery-powered devices but never had such problem or heard about anyone having this exact problem. Would you care to elaborate about it?
TheATHEiST said:
GTFO and find another site to post your problem on.
Click to expand...
Click to collapse
I'm not going to do that only because there are a few "anal" people in this great community.
Ok, you're obviously an idiot and its pointless trying to help you. Good luck trying to find somebody who will help you now after showing how much of a **** you are to people trying to offer advice.
I'm off to play on my fully working i9100.
Bye.
Hello!
I just want to know whether non-removable battery causes major probs in smartphones? Asking about Xperia Z1. Someone told me that if u want to do custom rom stuff, always go for removable battery handset.. Pls. Suggest..
As much as I prefer an easily replaceable battery (no such thin as non replaceable just harder to replace) this makes no difference on custom ROMs, get the phone you want for the reasons you want, if there is development for your device then you have no worries
Sent from my Nexus 4 using XDA Premium 4 mobile app
If you want to do customs ROMs, get a phone with a microSD card and preferably a removable battery.
The problem with non-removable batteries is your loss of control. For example:
- If you get a defective battery (and we all know that happens), you are SOL.
- Sometimes a battery pull is the only solution to a problem
- A non-removable battery means the phone can never really be turned off, making you your carrier's *****. They always know your location, all your data belong to them, etc.
EEngineer said:
If you want to do customs ROMs, get a phone with a microSD card and preferably a removable battery.
The problem with non-removable batteries is your loss of control. For example:
- If you get a defective battery (and we all know that happens), you are SOL.
- Sometimes a battery pull is the only solution to a problem
- A non-removable battery means the phone can never really be turned off, making you your carrier's *****. They always know your location, all your data belong to them, etc.
Click to expand...
Click to collapse
Again, custom ROMs have nothing to do with batteries or sdcards
Defective battery does not mean SOL, get a replacement free under warranty or swap it yourself, never seen a phone that is actually non replaceable as its said, just not as easy, instead of three seconds it may take three minuets, but really often takes just 30 seconds
No need to battery pull ever, always a hard reset options with key presses (yes even in a bootloop)
And becoming carriers ***** is a bit over dramatized, but youre free to whatever opinion there (but really I can't see it)
As much as I want an easily replaceable battery and SD card, these are only some of the many factors that go into phone purchases but again to each there own
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Again, custom ROMs have nothing to do with batteries or sdcards
Defective battery does not mean SOL, get a replacement free under warranty or swap it yourself, never seen a phone that is actually non replaceable as its said...
Click to expand...
Click to collapse
The title of this thread is "non-replaceble battery an issue?"
EEngineer said:
The title of this thread is "non-replaceble battery an issue?"
Click to expand...
Click to collapse
sorry! My mistake! I meant non-removable.. Not non-replaceble! Means i shud go for z1 na?
Is it possible to hard reset such battery? How?
I understand what is often meant by non-replaceable battery, I have owned many phones and other devices that say this, the phone I'm typing on has a "non-replaceable battery" which is just one of many that I have replaced (when installing a new screen so replaced it with the same battery but same point) and yes they are most always still very simple to replace
More than likely a hard reset will be a combo of the buttons available such as volume up + down + power for like 10 seconds, try a few combos on your current phone and I'm sure you'll find the way
Ask at z1 thread how to do it or go to a store that has display models and try, never seen an android phone that doesnt
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
More than likely a hard reset will be a combo of the buttons available such as volume up + down + power for like 10 seconds, try a few combos on your current phone and I'm sure you'll find the way
Click to expand...
Click to collapse
Doesn't a hard reset clear all your data too?
I like the Z1 but I'm nervous about a non-replaceable battery. Sometimes when hacking your phone, playing with ROMs, etc the only solution to a problem like a boot-loop is a battery pull.
As an adage, performing a rest via button combinations compared to a battery pull, it reminds me of the old adage "for reliability, never do in software what you can do in hardware".
I figured i would put my 2 cents in but my preference with devices (as a developer) would be a phone with a removable battery. Sometimes there are freezes and bootloops when flashing custom ROMs (ive had my nice share of that LOL). A device with a removable battery can easily shut the phone down (by removing the battery) unlike a phone with a non-removable battery. Some devices though come with a hard reset option where you can hold down certain buttons while your phone is frozen and you can just reboot that way, not sure about bootloops though. My advice to you would be to get a phone with a removable battery if you plan on doing a lot of flashing! Just my 2 cents.
Sorry, I meant hard reboot, not hard reset so no this won't wipe data
And as much as I agree with you all that an easily removable battery is nice it should not be a factor at all when talking about flashing ROMs or development. As like I said I have never seen an android that doesn't have the ability to hard reboot via keypress
Not to mention when flashing ROMs we are most often in front of a computer so adb reboot recovery or whatever (of course device may not be online depending on nature of bootloop or whatever so hard reboot)
So if you like all aspects of the z1 but are scared the removable battery will not allow you to reboot buy the phone, as this fear is misguided for there is always another way
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Sorry, I meant hard reboot, not hard reset so no this won't wipe data
And as much as I agree with you all that an easily removable battery is nice it should not be a factor at all when talking about flashing ROMs or development. As like I said I have never seen an android that doesn't have the ability to hard reboot via keypress
Not to mention when flashing ROMs we are most often in front of a computer so adb reboot recovery or whatever (of course device may not be online depending on nature of bootloop or whatever so hard reboot)
So if you like all aspects of the z1 but are scared the removable battery will not allow you to reboot buy the phone, as this fear is misguided for there is always another way
Click to expand...
Click to collapse
This is all soooooooo wrong, so very very wrong...
EEngineer said:
This is all soooooooo wrong, so very very wrong...
Click to expand...
Click to collapse
Enlighten me then, how is discussing ROM flashing and development remotely related to the ease of battery replacement? Call me crazy but some of the most development on any device is done on phones and tablets with the so called "non-user-replaceable-batteries" and there is zero issue in flashing ROMs or testing new kernels or ROMs, I've been in bootloops enough times with my n4, n7 and n10 and never did I go damn, need a battery pull
Even with the other 12 or more androids that have an easily removable battery I don't do battery pulls, even when I'm testing my ROMs, mods and kernels and get stuck in bootloops, its a non-issue
Buy a phone because you like what it can do, not because of unfounded fears. I love quick replace batteries and SD cards in my phones, but not having them doesn't make me think I can't flash something to it easily, if I did that would just be silly
But feel free to explain how the above is just a load of **** and I'm full of it, I don't mind at all
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Enlighten me then, how is discussing ROM flashing and development remotely related to the ease of battery replacement? Call me crazy but some of the most development on any device is done on phones and tablets with the so called "non-user-replaceable-batteries"
Click to expand...
Click to collapse
You are crazy. Most phones have replaceable batteries.
Let's hear from the experienced developer:
Droid Premium said:
I figured i would put my 2 cents in but my preference with devices (as a developer) would be a phone with a removable battery. Sometimes there are freezes and bootloops when flashing custom ROMs (ive had my nice share of that LOL). A device with a removable battery can easily shut the phone down (by removing the battery) unlike a phone with a non-removable battery. Some devices though come with a hard reset option where you can hold down certain buttons while your phone is frozen and you can just reboot that way, not sure about bootloops though. My advice to you would be to get a phone with a removable battery if you plan on doing a lot of flashing! Just my 2 cents.
Click to expand...
Click to collapse
EEngineer said:
You are crazy. Most phones have replaceable batteries.
Let's hear from the experienced developer:
Click to expand...
Click to collapse
I never said most phones don't, but lets look at some of the biggest devices with the most development as of late
which is just about every phone not made by Samsung - there is no issue flashing ROMs on these phones, at least none that involve the battery
seriously, and for some reason you need to replace the battery and phone is out of warranty, spend 2 minuets doing it, its still easy
but that's besides the point, and i must be failing in explaining to you
I have flashed countless amount of ROMs mod and kernels to so many androids, many with your "non removable batteries" and no issues
even when I am developing my ROMs or testing my kernels, no issues when in a bootloop
so enjoy your misguided reasonings and your new Samsung device, ill just say your right for the sake of i don't care,
and I'm bored of this conversation and all the electronic ink I've waste
have a nice battery pull! :good:
hard reboot is possible in z1. Chkd it.. Going for it den.. Thnx every1..
Thread closed at OP's request.
Okay... initially i was on Custom Rom Jellybam based on Jellybean 4.2.1 with Siyah Kernel V5 sync.
I want to upgrade to Kitkat 4.4
so i downloaded all the required files , made nandroid backup , reboot the phone and started transferring all ROM files into internal SD card Sdcard0
I am doing all this is Linux Mint..
It started transferring and got stuck 33.2%
so i removed the cable and try it again and this time again it stucked again
and my phone reboots automatically ..
Samsung logo main screen shows and loading starts but after completing loading bar .. it Freezes there and i cannot boot into recovery either..
SO on searching on goggle for solutions .. it states that i have to flash kernel again through ODIN again in order to access recovery to do Factory Reset..
SO i did the same flashed siyah kernel v4.1.5
it shows its successfully flashed BUT on reboot it shows Yellow triangle and freezes there and i still cannot access recovery and it also freezes on battery charge animation
So i again try to flash using ODIN this time again with siyah kernel 6.b5
and still same problem ,, so pull out battery and leave for 5 minutes and again boot phone in download mode and flash again using odin siyah kernel 6.0b5 and upon Reboot PHONE does not Boot.. I was literally Shocked and i try to pull out battery .. put back in and Try to charge but it shows no animation nor it is going in download mode.
Please HELP ..
Suggest me some ways because 1 year before I've replaced the motherboard due to same problem caused by factory reset in stock ICS rom when There was Hard Brick problem in Stock ICS roms..but it was in warranty so there was no problem but this time its out of warranty..
I didn't do anything wrong and still it got HARD BRICKED and still not have a clue what went wrong ??
No booting at all = nothing anyone here can do = replace motherboard or get a new phone (JTAG also very unlikely to work).
MistahBungle said:
No booting at all = nothing anyone here can do = replace motherboard or get a new phone (JTAG also very unlikely to work).
Click to expand...
Click to collapse
i know. this.. its TOO scary to hear this thing..
If anything is possible ?? Anything ??
i will give every info you needed..
And what exactly do you expect people here to suggest ? If the phone won't boot you can:-
*Try a jig (0.0000000001% chance of working, but try it if you like torturing yourself with false hope)
*Try a JTAG if the person who tries is prepared to do it on the basis of 'you only pay them if the JTAG is successful' (also 0.0000000001% chance of working, try this if you like torturing yourself with false hope even more)
*Replace the motherboard; 99.99% chance of successfully fixing the phone provided there's nothing else wrong hardware-wise
MistahBungle said:
And what exactly do you expect people here to suggest ? If the phone won't boot you can:-
*Try a jig (0.0000000001% chance of working, but try it if you like torturing yourself with false hope)
*Try a JTAG if the person who tries is prepared to do it on the basis of 'you only pay them if the JTAG is successful' (also 0.0000000001% chance of working, try this if you like torturing yourself with false hope even more)
*Replace the motherboard; 99.99% chance of successfully fixing the phone provided there's nothing else wrong hardware-wise
Click to expand...
Click to collapse
i'll go to samsung care tomorrow but i am still wondering what happened wrong as i did nothing wrong at all then still how it hardbricked ??
... probably you only need to flash a correct running ROM. Did you try to flash an original Samsung firmware? Did you wipe data before starting the new ROM? Otherwise there is a big chance for a bootloop.
Sent from my Nexus 7 using xda app-developers app
AndDiSa said:
... probably you only need to flash a correct running ROM. Did you try to flash an original Samsung firmware? Did you wipe data before starting the new ROM? Otherwise there is a big chance for a bootloop.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
the guide suggest to flash kernel so that i can wipe/data factory reset .. i tried that with odin but phone does not boot and freezes at Samsung logo when loading bar finishes... so i thought to flash stock ics rom but before doing that after flashing kernel again it reboot and hard bricked... and does not boot after all even in download mode..
So this happens after i flashed kernel 3rd time and i still have no clue why did it happened..
and customer care asks it would costs at least Rs.8,000 or $133 to replace a Motherboard.. which is too costly...
can anyone suggest me any other things.. ay alternatives ??
There are no other alternatives. Just because you refuse to accept reality doesn't make it anything less than reality.
And isn't it wonderful to see people still not reading threads & suggesting stuff that's impossible: 'probably you only need to flash a correct running ROM'. I mean, seriously ? The OP has already stated on multiple occasions that the phone will not boot. At all. How do you propose he flash 'a correct running rom' exactly ?
MistahBungle said:
There are no other alternatives. Just because you refuse to accept reality doesn't make it anything less than reality.
And isn't it wonderful to see people still not reading threads & suggesting stuff that's impossible: 'probably you only need to flash a correct running ROM'. I mean, seriously ? The OP has already stated on multiple occasions that the phone will not boot. At all. How do you propose he flash 'a correct running rom' exactly ?
Click to expand...
Click to collapse
hahah... i know .. people are sometimes too lazy to read ..
I just need to know.. what's wrong happened so that it will not happen next time..
Honestly ? That's almost impossible to say. Best guesses based on what you've told us are you simply got a bad flash, which is a small possibility (maybe 1 in 10,000) with any given flash. Or, I've had a theory based on instances like this I've seen on here over the past two yrs which involves the connection between phone & PC being broken for a split second during the flash (possibly caused by less than reliable USB ports on the PC or something else intermittent on the PC side), but not long enough for the disconnection to 'register' on the PC-side like it normally does when an external device is disconnected (you get that exclamation sound & a notification that the device has been disconnected in your taskbar).
It doesn't sound like you did anything 'wrong', put it that way. So I'm not sure there's a whole lot you can do to avoid it in future. Unfortunately, that's the risk all of us take whenever we flash stuff to our phones; every single flash (even CWM ones) involves that small risk (due to the nature of the NAND; having a write abruptly interrupted partway through can 'scramble' it) and the only way you can mitigate that 100% is to not flash anything at all.
Well .. I've already seen several people claiming a 'hardbrick' while the phone was only stuck in a boot loop. Especially while flashing only boot.img / system.img (which the OP claimed) it's normally really hard to create a hardbrick. That was the reason to suggest to try to flash an original firmware.If instead the bootloader is messed up, there is not much to do ...
AndDiSa said:
Well .. I've already seen several people claiming a 'hardbrick' while the phone was only stuck in a boot loop. Especially while flashing only boot.img / system.img (which the OP claimed) it's normally really hard to create a hardbrick. That was the reason to suggest to try to flash an original firmware.If instead the bootloader is messed up, there is not much to do ...
Click to expand...
Click to collapse
well I've got my s2 since past 1.7 years and nothing wrong has happened till date as I've flashed plenty of ROMS earlier.. its nothing new to me.. i am well known to these things..
i have exams from 1 month and s2 was creating problems such as freezes while scrolling in any application and automatic reboot from many time
i have no time to solve this during exams..
so i tried to solve this issue yesterday by upgrading to new ROM.. downloaded ROM files .. and ready to transfer to internal sd where copying stuck at 33% 2 times and at 2nd time from where main problem starts.. of freezing at bootscreen and then i trty to solve by flahsing new kernel thriugh ODIN where Hardbrick was TOTALLY UNEXPECTED.. as I've done this earlier time too but nothing happened wrong that time... i was literally surprised that it does not boot at all even i didn't done any mistakes at all & followed procedure.. even ODIN every time shows "Flash Successful"
i've attached screenshot of ODIN flashing.. so you can check for yourself..
May be there is a possibility of battery dying and phone cannot charge the battery ??
i've no spare battery to check .. so will go soon to care to check if its battery problem or not..
MistahBungle said:
Honestly ? That's almost impossible to say. Best guesses based on what you've told us are you simply got a bad flash, which is a small possibility (maybe 1 in 10,000) with any given flash. Or, I've had a theory based on instances like this I've seen on here over the past two yrs which involves the connection between phone & PC being broken for a split second during the flash (possibly caused by less than reliable USB ports on the PC or something else intermittent on the PC side), but not long enough for the disconnection to 'register' on the PC-side like it normally does when an external device is disconnected (you get that exclamation sound & a notification that the device has been disconnected in your taskbar).
It doesn't sound like you did anything 'wrong', put it that way. So I'm not sure there's a whole lot you can do to avoid it in future. Unfortunately, that's the risk all of us take whenever we flash stuff to our phones; every single flash (even CWM ones) involves that small risk (due to the nature of the NAND; having a write abruptly interrupted partway through can 'scramble' it) and the only way you can mitigate that 100% is to not flash anything at all.
Click to expand...
Click to collapse
i totally understand what you wanted to say..
i now how to do these things.. i know the risks...
still don't know what happened wrong..
hey guys.. i just went to samsung care and they told me that PCB need to be replaced and it ill costs me INR 8,000 or $133.33 which is too expensive and i told them if any other thing can be done .. i see some videos in youtube stating DEAD or HARDBRCIKED S2 can be fixed by changing its POWER IC...
so i told them that thing then they told me that OFFICIALY only Motherbaord could be replaced however I can ask local reapir shops in my city whether they can replace POWER IC or any other such thing which will be cheap..
So i went to one of the Repair shop (MAIN one in my CITY) & i ask them .. after checking he said.. I'll check IF Repalcing POWER IC will solve the problem or not... otherwise Motherboard need to be replaced..
the cost of POWER IC replacement is INR 800 or $13.33
otherwsie
he'll replace the motherboard for INR 3000 or $ 30..
so i deposoited my Phone to him and will go again in 2 hours.. to check if POWER IC replacement will fix the problem or not..
I am wondering if it will be safe to do this from unofficial reapir centre whether he will not take orignal parts of my phone internals ? however every people go to his shop.... Motherboard repalcing by him costs only INR 3000 ($50) while officialy its INR 8000($133)..
why is there so much price difference..??
IF POWER IC replacement is good idea ??
i just don't want to be in another problem...
Probably a 2nd hand board. If it were me, I'd be replacing the whole board. I wouldn't want someone fartarsing around replacing individual components on a board that size no matter how competent they claim to be. But that's up to you/how much money you're prepared to spend.
As to whether what he's going to do (replacing an individual component) will definitely fix it, how do you expect us to possibly know that ? You're the one who's met the person who's going to fix your phone/we have absolutely no knowledge whatsoever of this person/their competencies. I know one thing though, in Australia, nobody who repairs Samsung phones for a living (I.E a commercial operation/business) would replace an individual component like that. Only 'spare timers' would do that.
MistahBungle said:
Probably a 2nd hand board. If it were me, I'd be replacing the whole board. I wouldn't want someone fartarsing around replacing individual components on a board that size no matter how competent they claim to be. But that's up to you/how much money you're prepared to spend.
As to whether what he's going to do (replacing an individual component) will definitely fix it, how do you expect us to possibly know that ? You're the one who's met the person who's going to fix your phone/we have absolutely no knowledge whatsoever of this person/their competencies. I know one thing though, in Australia, nobody who repairs Samsung phones for a living (I.E a commercial operation/business) would replace an individual component like that. Only 'spare timers' would do that.
Click to expand...
Click to collapse
well i ask a local official samsung mobile shop onwer whom we knows from years ... he said.. he is the main person in our city and everyone goes to him for repair... and he thinks he won't do such as thing..
SO i gave my phone to him..
and about power IC replacment there are some videos on youtube i checked before asking for POWER IC replacement....
so thought may be it'll work.. :/
hope for the best..
anyways thanks..
MistahBungle said:
And what exactly do you expect people here to suggest ? If the phone won't boot you can:-
*Try a jig (0.0000000001% chance of working, but try it if you like torturing yourself with false hope)
*Try a JTAG if the person who tries is prepared to do it on the basis of 'you only pay them if the JTAG is successful' (also 0.0000000001% chance of working, try this if you like torturing yourself with false hope even more)
*Replace the motherboard; 99.99% chance of successfully fixing the phone provided there's nothing else wrong hardware-wise
Click to expand...
Click to collapse
What's up with the sarcasm? Pretty sure that's not what this forum is about.
Sent from my SCH-R950 using xda app-developers app
^^^^
Unless you're one of the 'slow kids up the back', you'll know there is absolutely nothing anyone on a phone forum can do for a person like the OP who has a phone in that state. How do I know this ? Experience. I have seen thousands of examples on here exactly like this in 2 & a bit years. They all turn out the same whether you tell people straight up, or whether you stuff them around for two weeks trying stuff that has no chance of working.
And as it's turned out, I was absolutely correct in my initial post. I'm not a believer in having people try a bunch of stuff that has no chance whatsoever of working which builds up their hopes, only to have them end up disappointed when the 'stuff that had no chance of working in the first place' doesn't work (funnily enough ).
I'd much rather be honest with people from the outset, so they can either have their phone repaired & working again (or buy a new phone if people decide that's a better option) sooner rather than later, because I know what it's like to be without a (decent) phone for week/however long.
But you're not capable of comprehending this, are you ? You'd rather make your 2nd post on here a 'gob off' re: something you know absolutely nothing about.
So . the thing is IF POWER IC replacemet will fix the phone or not...i've done some googling and found that the POWER IC replacemet works for users..
If anyone here in this forum has tried this and successfuly saved his phone instead of replacing whole Motherboard.. ??
MistahBungle said:
^^^^
Unless you're one of the 'slow kids up the back', you'll know there is absolutely nothing anyone on a phone forum can do for a person like the OP who has a phone in that state. How do I know this ? Experience. I have seen thousands of examples on here exactly like this in 2 & a bit years. They all turn out the same whether you tell people straight up, or whether you stuff them around for two weeks trying stuff that has no chance of working.
And as it's turned out, I was absolutely correct in my initial post. I'm not a believer in having people try a bunch of stuff that has no chance whatsoever of working which builds up their hopes, only to have them end up disappointed when the 'stuff that had no chance of working in the first place' doesn't work (funnily enough ).
I'd much rather be honest with people from the outset, so they can either have their phone repaired & working again (or buy a new phone if people decide that's a better option) sooner rather than later, because I know what it's like to be without a (decent) phone for week/however long.
But you're not capable of comprehending this, are you ? You'd rather make your 2nd post on here a 'gob off' re: something you know absolutely nothing about.
Click to expand...
Click to collapse
dude please if anything irritates you .. then i'm sorry..
i ts just its first time happened with me...s i am worried about my phone..
that's all :/