Related
I am aware that the questions i am about to ask might have been asked 1000 times, but the search feature didnt help this time, so i am sorry if i am bugging out somebody. So here is what happened.
I got a mytouch 4g phone today, and i rooted it using gfree as it was the first sticky on the forum. i did a bit of research about bricks on mt4g (have been playing with androids since a long time) and didnt find anything about the emmc problem. then i tried gfree and it was easier than i thought. so i unlocked it (s-off), changed cid and unlocked sim (all using gfree -f). and i installed cwm and installed a rom. everything is working perfect.
but i discovered all the threads about bad emmc and bricks and stuffs like that. so i checked my emmc name and it came out to be the bad one. and i figured out that i did a big mistake. so i thought about restoring gfree backup and using the other root method (hboot s-off not radio). i was just about to restore the backup using gfree, then i noticed that my backup file (.bin file) was not present on my sd. i was shocked at first. then i found that i could s-on the phone using gfree without using backup bin file. but if i do that, will my phone not get emmc bricked like others? or do i need my backup file? can i use someone else's bin backup file? if yes, can you give me yours? any help would be really appreciated. i am worried that i might get a brick anytime. i was planning to make some tools for mytouch 4g (like i did for hd2) but i guss i will not be able to do that anymore cuz i might get a brick anytime. thanks for reading.
Edit: do all bad emmc phones using gfree get bricked? and what is the average period before it gets bricked (yea im too worried ) and is there anythign i could do now? (except for sending it for replacement since i bought it off craigslist)
This gfree and bad eMMC is just a correlation. Nothing has been proven to be a fact just yet. I've rooted my phone via gfree about 3 months ago now and I flash at least 2-3 times a week and nothing happened so far (I have the bad eMMC by the way). Everything seems fine for now.
I've also came across people that have the bad eMMC and have bee rooting and flashed hundreds of time for 6 months and going, so it's not a definite that your phone with the bad chip will die soon, so just keep that in mind.
But yes, it has happened to numerous people with the bad chip. Honestly, I would just ride it out and see what happens. If it dies just exchange it through T-Mobile.
You can't root the phone with "bad" eMMC by root.sh method, so you shouldn't even bother trying.
Jack_R1 said:
You can't root the phone with "bad" eMMC by root.sh method, so you shouldn't even bother trying.
Click to expand...
Click to collapse
I used this method on mine with the "bad chip" and had no problems.
tooter1 said:
I used this method on mine with the "bad chip" and had no problems.
Click to expand...
Click to collapse
You used g-free previously.. or root.sh wouldn't work on bad eMMc.
Please refer to the guides.
root.sh is guaranteed not to work on bad eMMc's unless g-free had previously been used.
Also not all "can't open /cache/recovery/log" errors in recovery are due to a dead eMMC chip. It can happen if your cache partition gets corrupted. Earlier this week, I had a bad flash--forgot to verify the md5sum before flashing, and after things started messing up, wifi not working, force-closes, etc...
So I went back to restore a nandroid backup I had made prior to the bad flash and got the dreaded "can't open /cache/recovery/log" error. I plopped the PD15IMG.zip on my sdcard and flashed it through hboot without any fail-PU errors.
So no, a M4G2DE eMMC chip doesn't always mean you'll have a brick. And cache partition errors in recovery don't always mean the eMMC chip died. What it means is that the "bad" eMMC chip has a much higher failure rate than the "good" chip. So if you have a "bad" chip, judging by the numbers, you have a much higher chance of ending up with a brick at some point.
might sound silly but where would I get the PD15IMG.zip file??
I thought PD15IMG.zip was the RADIO file.. but i think am pretty clueless...any enlightenment ?
3p4145 said:
might sound silly but where would I get the PD15IMG.zip file??
I thought PD15IMG.zip was the RADIO file.. but i think am pretty clueless...any enlightenment ?
Click to expand...
Click to collapse
Any file that has to be flashed through the bootloader (such as the stock RUU, radio files, etc) has to be named PD15IMG.zip for the bootloader to recognize it. There are two threads in the dev section that have the stock RUU you're looking for. A little searching should locate them.
Hi,
I'm a newb, and was thinking about rooting my phone and installing a different rom, but I read about this bad eMMC problem. I was wondering, if I have the bad eMMC and I don't root and install roms, will I still have the same problem that my phone might just die? Or is it only if I flash roms onto my phone?
Thanks,
Andy
Yes, if the "bad" eMMC in your phone is really bad - it'll die no matter if you flash ROMs or not. Just slower if you don't.
For what it's worth, I've had my phone with the bad emmc since December ... rooted since January & flashing roms ever since... no dead emmc. (Yet, if ever).
Sent from my HTC Glacier using XDA App
So, if you do have the M4G2DE chip, is it possible that is good? Like, you have a good version of the M4G2DE chip?
DashBlacK said:
So, if you do have the M4G2DE chip, is it possible that is good? Like, you have a good version of the M4G2DE chip?
Click to expand...
Click to collapse
+1
Sent from my Tweaked out RCmix3D myTouch 4G via xda premium !
good question. i don't have an answer to that. i've warrantied my phone, got another bad emmc around april? & have rooted & been flashing roms. phone hasn't died.
M4G2DE is just a regular chip. It's used for at least 3 other phones (G2, DHD, DS). I have one in my wife's Desire S, and it's rooted and running VU.
All the hype of the "bad" chip has gone WAY out of proportions.
DashBlacK said:
So, if you do have the M4G2DE chip, is it possible that is good? Like, you have a good version of the M4G2DE chip?
Click to expand...
Click to collapse
Yes, there is a good and a bad batch like most things in the world. My mytouch had the bad emmc from march to now and it's been fine. I flash like a maniac and it's been fine.
But like someone mentioned before if you really do have the bad bad chip; eventually your phone will just crap out. There are several cases on it from people who has never rooted before.
What people usually don't talk about is that some "good" chips are also bad and will eventually go bad overtime. Someone made a poll and discovered that the bad emmc chip showed a higher susceptibility of the phone failing. But remember it is only a poll. The poll also said that blacks are more susceptible than other colors... Why? because more blacks were distributed. It is possible that more bad chips were distributed. who knows?
Hope that clears some things up for everyone.
Teo032 said:
Yes, there is a good and a bad batch like most things in the world. My mytouch had the bad emmc from march to now and it's been fine. I flash like a maniac and it's been fine.
But like someone mentioned before if you really do have the bad bad chip; eventually your phone will just crap out. There are several cases on it from people who has never rooted before.
What people usually don't talk about is that some "good" chips are also bad and will eventually go bad overtime. Someone made a poll and discovered that the bad emmc chip showed a higher susceptibility of the phone failing. But remember it is only a poll. The poll also said that blacks are more susceptible than other colors... Why? because more blacks were distributed. It is possible that more bad chips were distributed. who knows?
Hope that clears some things up for everyone.
Click to expand...
Click to collapse
Interesting info...
Sent from my HTC Glacier using xda premium
HTC Mytouch 4G EMMC
I sent in my lifeless HTC Mytouch 4G to have 'Jtag Service' done to it as thats what I thought it needed, but instead they performed this 'EMMC Repairs Service' which was what they diagnosed the problem to be. An it fixed it, before sending it in, all my phone did was to charge batteries. checkout their website they even send the bad EMMC chip with the phone :good: hope I helped someone be blessed :angel: here is the URL---> mobiletechvideos.mybigcommerce .com/htc-mytouch-4g-emmc-chip-repair-replacement/
Nice how much was that
Sent from my HTC Glacier using xda app-developers app
bramz said:
I sent in my lifeless HTC Mytouch 4G to have 'Jtag Service' done to it as thats what I thought it needed, but instead they performed this 'EMMC Repairs Service' which was what they diagnosed the problem to be. An it fixed it, before sending it in, all my phone did was to charge batteries. checkout their website they even send the bad EMMC chip with the phone :good: hope I helped someone be blessed :angel: here is the URL---> mobiletechvideos.mybigcommerce .com/htc-mytouch-4g-emmc-chip-repair-replacement/
Click to expand...
Click to collapse
I almost had the JTAG service done too. Before I did I did my research and come to find out that when I explained my situation to one of their techs I was emailing, he said that my situation was folly and there was nothing they could do. He stated it was the dreaded "bad eMMC chip problem" yet all i had was cache and recovery errors just like what was mentioned above. Formatted my sdcard, put the stock T-Mobile GB PD15IMG.zip on there, flashed, and booted right up. Lost root of course, but able to get it back to rooted state and been flashing custom roms ever since. Pretty sure just like what was stated above... Blown WAY out of proportion. Hope this helps some people with their anxiety about this issue.
Rooted a friend's phone using visionary, put root folder on SD card, followed Prompts in terminal emulator, reboot and S still show's on.. any suggestions.. I never had this problem rooting my own mytouch.. & The phone hasn't been updated, still running 2.2.1
Check out the Post Your eMMC thread in the general section, it will tell you how to check which one the phone has using terminal emulator. Phones with the "bad" eMMC cannot be rooted using the root.sh method, but can be with g-free.
King350z said:
Rooted a friend's phone using visionary, put root folder on SD card, followed Prompts in terminal emulator, reboot and S still show's on.. any suggestions.. I never had this problem rooting my own mytouch.. & The phone hasn't been updated, still running 2.2.1
Click to expand...
Click to collapse
Root via gfree method...
Sent from my HTC Glacier Sense 3.0 using XDA app
King350z said:
Rooted a friend's phone using visionary, put root folder on SD card, followed Prompts in terminal emulator, reboot and S still show's on.. any suggestions.. I never had this problem rooting my own mytouch.. & The phone hasn't been updated, still running 2.2.1
Click to expand...
Click to collapse
Before I learned about this website I had rooted my phone using the tutorial from the unlockr's website, gfree method.. Worked great.
saranhai said:
Root via gfree method...
Sent from my HTC Glacier Sense 3.0 using XDA app
Click to expand...
Click to collapse
you need to be careful before throwing out the idea that ./gfree is a fix all. It's not. It's a huge problem on phones that have bad eMMC chipset.
neidlinger said:
you need to be careful before throwing out the idea that ./gfree is a fix all. It's not. It's a huge problem on phones that have bad eMMC chipset.
Click to expand...
Click to collapse
Yea... That's what happened to my old MT4G
Best suggestion is to just keep stock.
Sent from my HTC Glacier Sense 3.0 using XDA app
Does that mean I shouldn't put custom roms on my phone? What if I get bored?
U can also use launchers and home replacements if u get bored wit stock
McSurge45 said:
Does that mean I shouldn't put custom roms on my phone? What if I get bored?
Click to expand...
Click to collapse
Sent from my HTC Glacier using XDA App
McSurge45 said:
Does that mean I shouldn't put custom roms on my phone? What if I get bored?
Click to expand...
Click to collapse
I wouldn't say don't put roms on your phone EVER.... but before you do make sure you check what emmc chip you have. If you have the bad one you're sort of giving your phone a death sentence by rooting with gfree. It might last a good while, but most likely your phone will brick itself at some point. And considering the root.sh method doesn't work with the bad chip, gfree is your only option.
Basically, if you have the good chip feel free to flash roms to your delight, AFTER YOU INFORM YOURSELF HOW. But if you have the bad chip just know that your phone is at risk of dying if you root it.
AlanB412 said:
I wouldn't say don't put roms on your phone EVER.... but before you do make sure you check what emmc chip you have. If you have the bad one you're sort of giving your phone a death sentence by rooting with gfree. It might last a good while, but most likely your phone will brick itself at some point. And considering the root.sh method doesn't work with the bad chip, gfree is your only option.
Basically, if you have the good chip feel free to flash roms to your delight, AFTER YOU INFORM YOURSELF HOW. But if you have the bad chip just know that your phone is at risk of dying if you root it.
Click to expand...
Click to collapse
I have rooted and unrooted my phone(with the bad chip) many times, which writes to the emmc and power cycles it and flash at least 5 ROMS a week and flash back to nandroid backups as well during the week, so saying the bad chip and gfree combine is the issue is not true... There are cases of the root.sh emmc failure as well just not as many.... There is something more at bay with the bad emmc that has to be a common fail point not known yet. Cause as much as my chip has been power cycles and written to, it should be the first to fail! Just my two cents...
Sent from my HTC Glacier using XDA Premium App
irrelephant said:
I have rooted and unrooted my phone(with the bad chip) many times, which writes to the emmc and power cycles it and flash at least 5 ROMS a week and flash back to nandroid backups as well during the week, so saying the bad chip and gfree combine is the issue is not true... There are cases of the root.sh emmc failure as well just not as many.... There is something more at bay with the bad emmc that has to be a common fail point not known yet. Cause as much as my chip has been power cycles and written to, it should be the first to fail! Just my two cents...
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
+1 I have heard more horror stories about root.sh and visionary method failures then gfree method there's got to be more to the story then just the bad emmc chip and using Gfree to root. I used Greer to root as well and have bad emmc but good display and I'm a crack flasher, tho I've slowed down a bit after finding my 3 favorite roms.
Sent from my HTC Glacier using XDA Premium App
@Irrelephant & DrunkBastard
I don't intend to discount your experiences with what I said. Like I posted before, I have read about plenty of people with bad chips who have spent a long time flashing and reflashing their phones, so I can totally believe that you guys haven't had any problems with it or gfree. And considering the nature of rooting I can also believe that people have messed their phones up with the visionary method as well, especially since I actually was one of those people. However, I was fortunate enough and informed enough to fix it without any lasting damage.
As you said, the emmc chip problem is something that nobody is entirely sure about, but the general consensus seems to be that they are much more likely to fail when you have the bad model, whether or not you have rooted your phone or flashed roms or anything. I've even read some cases where people with entirely stock phones have had it fail on them.
On top of that, the gfree method, while very reliable, relies heavily on that chip. I can't honestly say that I know the exact processes that are different between the visionary method of rooting and the gfree method, but from what I've read gfree is more of a hardware oriented approach to achieving s off while visionary is more software oriented. Feel free to correct me if I'm wrong, I'm here to learn just like everyone else.
I guess it was sort of bold(and grim) for me to say that having a bad chip and then rooting it was a death sentence for your phone. What I was trying to get across was that the bad chips definitely do have a worst reputation. And while anybody who wants to root their phone should try and be as well informed of the risks and processes as possible, I think that if you have a product with a bad reputation you should read up about the problem and what extra risks it may cause.
ALL of the evidence doesn't point towards death sentences for bad chipped phones, but a lot definitely points to major problems with the bad chips, and that's something people should know about, particularly if they are one of the people who have it.
So in the end, people just need to try and make well informed decisions about what they will do with their phones(and the same can be applied to life I guess). That's what I was trying to get across. Sorry if I bothered you guys with my strongly worded post before, I just wanted to make sure people knew what they were getting into before they jumped into the pool.
____________________________________
Sent from the AFB Corporation's Main Communication Portal
AlanB412 said:
As you said, the emmc chip problem is something that nobody is entirely sure about, but the general consensus seems to be that they are much more likely to fail when you have the bad model, whether or not you have rooted your phone or flashed roms or anything. I've even read some cases where people with entirely stock phones have had it fail on them.
Click to expand...
Click to collapse
That.
Moreover, I had an experience with Desire S (HTC Saga) with the aforementioned "bad" chip, and I can confirm it's prone to failure even in completely stock form. The "bad" chip seems to have a bad production run or post-silicon verification issues, since there are many perfectly fine specimens, yet more than enough reports of failing devices, not necessarily rooted. Of course, vast majority of reports on XDA would be of rooted devices, since this is what XDA is about.
Judging by the time-to-failure reports for those chips, it's probably safe to say that 2-3 weeks of heavy use would be a good checkpoint - if a chip is prone to failure, it'll fail within 2-3 weeks of heavy use, and if it didn't fail - it'll most likely serve the regular lifetime of eMMC (which isn't eternal either).
There was an interesting hypothesis for this chip's failures in one of the threads at Desire S section, which might be worth checking. It was said that the chip is most likely to fail when it has power failure (intentional or not) during write cycle. Which means, pulling the battery while installing the app, for example, has a high chance of bricking a completely stock device.
i totally agree with both of you guys!!! and as jack stated, i think there was just a bad production run, or lot run for that matter... but all in all, rooting your phone is taking a chance since there are always unknown variables that could come to play. i have noticed that my phone with the bad chip has always been a bit more wonky that the one with the good chip, but i continue to use the bad one to flash away with because it was the one i started all the crack flashing on and if it fails, then it fails! i kinda wish it would fail so that i can start poking around at it to see what craziness i can find in there... i am all about troubleshooting things and if all else fails then i can send it in under insurance!
i think people should read and know what could happen and make a choice based on that, but i see too many ppl trying to scare off users because they have the so-called bad chip... but the bad chip has been good to me over a yr now and i continue to abuse this bad boy more than the average user!
and nothing anyone says on here is going to get me BUTT HURT, i am always open to a good debate on a controversial topic... so long as it is civil that is, cause if it gets ignorant, then i just leave it at that... to in the end, thank yall for holding open debate with me as it keeps me informed and thinking!!!
I wish you could buy the phone and pick the rom it comes with......
Long lurker, posted a few times.
I had a my myTouch since February, and I went ahead and rooted it the first day I got it. Then, when I discovered Virtuous Unity 2.35, I went ahead and flashed it, along with the Panache radio and theme (Revolution). After about 2 days, the phone started acting up. It would freeze about 1 minute into boot and would require a battery pullout to turn back on. On it's fourth time of freezing, I pulled the battery out as usual, and put it back in. The phone never came back on again. I tried everything, from using another battery; waiting ten minutes before putting it back in; putting in the charger didn't help, as there was no charging light.
I sent it back to T-Mobile and got a new one. Again, I did the same for the new one, and heard about the bad emmc chips. I went ahead and looked at mine, and with dimay, I found out I had a bad one. After 3 days, the same thing that happened to the old one happened to the new one.
Seriously, what is going on here? TWO bricks within a couple of days apart? Also, why is T-Mobile still releasing these dead chips?
My question is, "Is there any way to fix this full brick, if at all boot into recovery?" Thanks!
nzube14 said:
Long lurker, posted a few times.
I had a my myTouch since February, and I went ahead and rooted it the first day I got it. Then, when I discovered Virtuous Unity 2.35, I went ahead and flashed it, along with the Panache radio and theme (Revolution). After about 2 days, the phone started acting up. It would freeze about 1 minute into boot and would require a battery pullout to turn back on. On it's fourth time of freezing, I pulled the battery out as usual, and put it back in. The phone never came back on again. I tried everything, from using another battery; waiting ten minutes before putting it back in; putting in the charger didn't help, as there was no charging light.
I sent it back to T-Mobile and got a new one. Again, I did the same for the new one, and heard about the bad emmc chips. I went ahead and looked at mine, and with dimay, I found out I had a bad one. After 3 days, the same thing that happened to the old one happened to the new one.
Seriously, what is going on here? TWO bricks within a couple of days apart? Also, why is T-Mobile still releasing these dead chips?
My question is, "Is there any way to fix this full brick, if at all boot into recovery?" Thanks!
Click to expand...
Click to collapse
I'm just trying to learn from experience after all the flashing when you started to get freezing and acting up did you flash that one file on Virtuous Unity 2.35 page that states if you get phone freeze to flash the file
nzube14 said:
Long lurker, posted a few times.
I had a my myTouch since February, and I went ahead and rooted it the first day I got it. Then, when I discovered Virtuous Unity 2.35, I went ahead and flashed it, along with the Panache radio and theme (Revolution). After about 2 days, the phone started acting up. It would freeze about 1 minute into boot and would require a battery pullout to turn back on. On it's fourth time of freezing, I pulled the battery out as usual, and put it back in. The phone never came back on again. I tried everything, from using another battery; waiting ten minutes before putting it back in; putting in the charger didn't help, as there was no charging light.
I sent it back to T-Mobile and got a new one. Again, I did the same for the new one, and heard about the bad emmc chips. I went ahead and looked at mine, and with dimay, I found out I had a bad one. After 3 days, the same thing that happened to the old one happened to the new one.
Seriously, what is going on here? TWO bricks within a couple of days apart? Also, why is T-Mobile still releasing these dead chips?
My question is, "Is there any way to fix this full brick, if at all boot into recovery?" Thanks!
Click to expand...
Click to collapse
As of now, there is no way to fix it. Strange though, my old one had a dead eMMC as well but I.could still go in CWM
Sent from my HTC Glacier using xda premium
Always remember, after rooting you should Check your eMMC
If the eMMC is good, try flashing otherwise report it to T-Mobile
SEMO4G is the "good" one & M4G2DE is the name of the "bad" one.
__________________
If this replay helped, please hit the "Thanks" button.
Flashing that one file? I don't know which one you are talking about. If you saw it, could you point me to it, please?
Also, if your eMMC is bad, you could report it to T-Mobile? How? I was asking them about the eMMC, and they (the tech department) knew nothing about it. -__- Yeah, I had the M4G2DE. Although looking at this thread (http://forum.xda-developers.com/showthread.php?t=1081243) it seems that the SEM04G is still bad, or am I just confused?
Don't get confused. If you get just SEMO4G it is "good"
Try for yourself
Download terminal emulater
Type in:
su
(to gain root permission)
Than type in
cat /sys/class/block/mmcblk0/device/name
__________________
If this replay helped, please hit the "Thanks" button.
If your eMMC is bad, don't try to flash any custom Rom.
If you try to modify the system, the phone will get damaged.
febycv said:
Always remember, after rooting you should Check your eMMC
If the eMMC is good, try flashing otherwise report it to T-Mobile
SEMO4G is the "good" one & M4G2DE is the name of the "bad" one.
__________________
If this replay helped, please hit the "Thanks" button.
Click to expand...
Click to collapse
No. Check eMMC before rooting. That way, you will not have warranty problems.
Sent from my HTC Glacier using xda premium
Just to throw it out there though, it's not definitive that your phone will brick when you have the bad eMMC.
I used to have the bad eMMC before I exchanged it out for an unrelated problem. I flashed a ROM on that phone about couple times a week for 3-4 months with no issues. I've even seen some that have had the bad chip since day one and flash almost every CM7 nightly and still haven't had a problem. So my guess is that if your bad eMMC doesn't fail fairly soon and quick then you should be in the clear.
Ive had the bad eMMC since day one and have flashed many roms of all kinds. Knock on wood, i have had no problems
cowboy2844 said:
Ive had the bad eMMC since day one and have flashed many roms of all kinds. Knock on wood, i have had no problems
Click to expand...
Click to collapse
Yeah my point exactly. All of the failed ones are highly documented so every one thinks every "bad" eMMC is going to fail but who knows how many people with that eMMC has actually not failed?
I'm another one with the "bad" eMMC, so far no problems flashing roms.
I have the good eMMC chip and this is my 3rd failure. -.- after rooting using visionary+ it seems like data partition gets borked either while formatting or flashing rom.
CWM outputs unable to mount /data
lmao
anyway downloading pd15img.zip lets see what happens (I know I will lose root and my eng bootloader but oh well atleast i might get my phone back xD)
_ice_ said:
I have the good eMMC chip and this is my 3rd failure. -.- after rooting using visionary+ it seems like data partition gets borked either while formatting or flashing rom.
CWM outputs unable to mount /data
lmao
anyway downloading pd15img.zip lets see what happens (I know I will lose root and my eng bootloader but oh well atleast i might get my phone back xD)
Click to expand...
Click to collapse
Have you tried format the SD card with sdformatter v.2.0 or any other program to fat32 then try gain full root and put CWM on it to see if it stops that unable to mount problem
Sent from my HTC Glacier using XDA App
Just got another replacement, and looked up eMMC chip. SEMO4G!
With good screen as well! Hopefully, no more bricks.
Yeah I have the bad eMMC on a Mobilicity Panache. But so far nobody with a Panache (as opposed to MT4G) has reported failure, even though at least half of them have the "bad" eMMC. And seeing as a thread I started here is the only guide that speaks directly to rooting the Panache, I would expect any bricks to be reported on that thread.
Dear all,
Maybe strange.........
I just cant brick my note! Not that i want to but how? before i knew the brickbug i did:
Odin flash to a leak ICS
Rebooted in CWM And wiped Factory default.. No problem
At one time i even formatted EMMC however its called.
At this time ICS brickbug shows up in this forum and i downloaded the APK brickbug app and i seem to be vulnarable.
Today a friend comes in with a bricked note.. tellin me he was flshing from odin and it hung on first part of flash without starting. He removed phone after 30 secs.
please take notice that it can take up to 2 minutes to start flashing.
any thoughts on this story?
jeroen180 said:
Dear all,
Maybe strange.........
I just cant brick my note! Not that i want to but how? before i knew the brickbug i did:
Odin flash to a leak ICS
Rebooted in CWM And wiped Factory default.. No problem
At one time i even formatted EMMC however its called.
At this time ICS brickbug shows up in this forum and i downloaded the APK brickbug app and i seem to be vulnarable.
Today a friend comes in with a bricked note.. tellin me he was flshing from odin and it hung on first part of flash without starting. He removed phone after 30 secs.
please take notice that it can take up to 2 minutes to start flashing.
any thoughts on this story?
Click to expand...
Click to collapse
Go to the church and donate 10 euros...
You might not be so lucky next time around.
Because you didn't brick doing 1 wipe, doesn't mean that you cannot brick..
It's like getting struck by lightning, maybe you will survive the first, but it
might not save you a second time...
Well, it is a brick bug, so it is only a chance - not definitive. I have stock ICS infected with the bug, but haven't nor plan on flashing or anything like that so...
friedje said:
Go to the church and donate 10 euros...
You might not be so lucky next time around.
Because you didn't brick doing 1 wipe, doesn't mean that you cannot brick..
It's like getting struck by lightning, maybe you will survive the first, but it
might not save you a second time...
Click to expand...
Click to collapse
Back on first HTC android phone )G1) i got it bricked 3 times by flashing SPL 3 times. Anywayz Android is much better (for me) then IOS from crapple. Only HTC dreams where crap in quality since the board has been replaced 5 times due hardware failures...
Now back on business:
I know im lucky. But still .. what causes the randomness of bricking. I mean it is there or it is not? Maybe god exists. I love my note too much to brick it
jeroen180 said:
Back on first HTC android phone )G1) i got it bricked 3 times by flashing SPL 3 times. Anywayz Android is much better (for me) then IOS from crapple. Only HTC dreams where crap in quality since the board has been replaced 5 times due hardware failures...
Now back on business:
I know im lucky. But still .. what causes the randomness of bricking. I mean it is there or it is not? Maybe god exists. I love my note too much to brick it
Click to expand...
Click to collapse
It isn't random. There are just multiple conditions that need to come together to trigger it. Read the thread about it to understand better the hows and why's.
friedje said:
It isn't random. There are just multiple conditions that need to come together to trigger it. Read the thread about it to understand better the hows and why's.
Click to expand...
Click to collapse
Even if all the conditions are met there's still a good chance it won't happen. IIRC there are also versions of emmc chips that don't have the brickbug.
pboesboes said:
Even if all the conditions are met there's still a good chance it won't happen. IIRC there are also versions of emmc chips that don't have the brickbug.
Click to expand...
Click to collapse
Well the fact of having a dangerous chip is one of the conditions....
So if you don't have it then not ALL the conditions are met..
Believe me if all the conditions are met, it will brick, it"s not random.
Then, Jeroen stated that he tested with Chainfires app, and he does have the faulty chip.
Finally I haven't seen a Note in the wild yet that doesn't have a faulty chip.
I feel like the OP. Before I knew of the bug I flashed and wiped many times. But I only flash stock roms. I don't know if that helped or not.
Sent from my GT-N7000 using xda premium
Hey there XDA Samsung Galaxy S4 Community, I come to you today to ask, If something should go wrong(mainly a user error) while flashing a new rom/kernel and my phone starts bootlooping like a fruit bowl, is there a fail safe for this phone? Like for the Samsung Infuse 4g no matter what you messed up on the phone all you had to do was put it into download mode and flash stock rom via Oden. It was pretty much unbrickable unless you totally noobed something xD So I was just wondering if this beautiful sex god of a phone had the same fail safe. Get back at me
MaliciousIntent69 said:
Hey there XDA Samsung Galaxy S4 Community, I come to you today to ask, If something should go wrong(mainly a user error) while flashing a new rom/kernel and my phone starts bootlooping like a fruit bowl, is there a fail safe for this phone? Like for the Samsung Infuse 4g no matter what you messed up on the phone all you had to do was put it into download mode and flash stock rom via Oden. It was pretty much unbrickable unless you totally noobed something xD So I was just wondering if this beautiful sex god of a phone had the same fail safe. Get back at me
Click to expand...
Click to collapse
Same with the GS4, if you get to download mode, flash back to stock with odin, no issues here.
TheAxman said:
Same with the GS4, if you get to download mode, flash back to stock with odin, no issues here.
Click to expand...
Click to collapse
Awesome. I've been wondering that, Now I feel well enough about it to finally flash a ROM on my new baby xD
MaliciousIntent69 said:
Awesome. I've been wondering that, Now I feel well enough about it to finally flash a ROM on my new baby xD
Click to expand...
Click to collapse
Whatever rom you choose, just make sure you read, you will be ok, in fact, the hard brick is hard to do on this phone, but it could happen. Good luck
Some of us can testify that soft bricking your device when you start out definitely makes you start reading a lot more. LOL Unless you try flash a rom from a totally different device, you should be able to reboot into recovery and just wipe and restore. If I don't bootloop more than once a week I'm not flashing enough.
Phoneguy589 said:
Some of us can testify that soft bricking your device when you start out definitely makes you start reading a lot more. LOL Unless you try flash a rom from a totally different device, you should be able to reboot into recovery and just wipe and restore. If I don't bootloop more than once a week I'm not flashing enough.
Click to expand...
Click to collapse
Haha i know exactly how that is xDD I used to be an insane flashaholic on my Infuse 4G mainly because the community for that phone was amazingly large at the time.
+1
Isn't having a bootloop not a part of the process, if your not bootlooping, your not FLASHING enuf! yeah baby.
TheAxman said:
if your not bootlooping, your not FLASHING enuf! yeah baby.
Click to expand...
Click to collapse
That's a reckless attitude to have toward your $700 device. And that's fine; I'm not here to tell you how to treat your phone. However, I really don't think you should post cavalier comments like that that might teach new users to do the same.
I've owned an HTC Inspire, a Galaxy S2, and a Galaxy S4. I've flashed many roms/kernels/recoveries/modems on all of them, and not once have I ever caused a boot loop. You just have to read, and never do anything before you know exactly what it is you're doing.
mattdm said:
That's a reckless attitude to have toward your $700 device. And that's fine; I'm not here to tell you how to treat your phone. However, I really don't think you should post cavalier comments like that that might teach new users to do the same.
I've owned an HTC Inspire, a Galaxy S2, and a Galaxy S4. I've flashed many roms/kernels/recoveries/modems on all of them, and not once have I ever caused a boot loop. You just have to read, and never do anything before you know exactly what it is you're doing.
Click to expand...
Click to collapse
Same here. Never once bootlooped. There's a difference between constantly flashing and correctly flashing.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
plwalsh88 said:
Same here. Never once bootlooped. There's a difference between constantly flashing and correctly flashing.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
There's also a difference between flashing things that are untested / should work and things that have been fleshed out so to speak.
I flash a lot of untested stuff (mostly built by others, some by me) and have boot looped my phone at least 10 times since 5 May when u bought it.
Bootloops are not damaging as the software is juat not loading (hence the loop). As long as you dont mess with bootloaders you should b3 fine (and loki is not touching the bootloader just feeding it false info)
Sent from my GT-I9505 using Tapatalk 4 Beta
mattdm said:
That's a reckless attitude to have toward your $700 device. And that's fine; I'm not here to tell you how to treat your phone. However, I really don't think you should post cavalier comments like that that might teach new users to do the same.
I've owned an HTC Inspire, a Galaxy S2, and a Galaxy S4. I've flashed many roms/kernels/recoveries/modems on all of them, and not once have I ever caused a boot loop. You just have to read, and never do anything before you know exactly what it is you're doing.
Click to expand...
Click to collapse
All it is, is a statement saying that you are going to get bootloops, guess you guys are perfect. but they happen, easily recoverable, so I think my statements holds true.
Moving along!
_Dennis_ said:
There's also a difference between flashing things that are untested / should work and things that have been fleshed out so to speak.
I flash a lot of untested stuff (mostly built by others, some by me) and have boot looped my phone at least 10 times since 5 May when u bought it.
Bootloops are not damaging as the software is juat not loading (hence the loop). As long as you dont mess with bootloaders you should b3 fine (and loki is not touching the bootloader just feeding it false info)
Sent from my GT-I9505 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Completely agree and knew that would be the response. But based on their posts it sounded more like ROM hopping than testing.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Please read forum rules before posting
Questions and help issues go in Q&A and Help sections
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator