Related
Hello, I'm new to the whole Android thing, but I managed to recently root my Shift, and I can attest to the addictive properties of trying out ROMS/Kernels and all that good stuff. But I was worried about the idea of all this flashing I'm doing, as in the month or so I've been rooted I've flashed about four ROMS, messed up a few times, done a good 5 or 6 Nandroid restores/backups. I was just curios to know if this is excessive, or if this could damage my phone in any way. Thanks for any help guys!
P.S., I apologize if this is either in the wrong thread, or has already been answered >_< I'm still a young'un
As far as I know by flashing a lot you can damage the relationship with your wife or g/f due to spending a lot of time doing it.. besides that I believe that the only way you can damage your phone is due to a bad flash or flashing something that wasn't exactly supported by the Shift.
I recall this discussion back when I had a TouchPro2, I don't know if it applies to the Shift as well but I assume it does. From my understanding it was determined by people far more informed than me that flashing would eventually wear out the NAND memory...but it would take more flashes than even the most fiendish flashaholic could complete in the phones lifetime to do. This is what I know from discussions of a past phone, I'm not claiming anything about the lifetime of the phone and take no responsibility if you flash 5000 ROMS tonight and your NAND burns out. lol
I think the only way you can actually brick your phone from flashing is if you flash a bad ratio from like a gsm carrier to a cdma phone. Might be wrong. Cause even if you flash a bad rom as long as you have a working recovery you can always just reflash a new rom or ruu
I think his underlying question may have to do with the fact that every NAND flash memory module has a limited number of writes in its lifetime before it can't write another bit and tell whether or not the module is in the 0 or 1 state.
This is also why data2ext/apps2ext etc anything that constantly writes information to your SD card will also degrade the lifetime of the SD card.
Basically yes, in principle the number of times you write new data to the phone's built-in memory, you shave off another write from its life. But I don't think this is significant at all. Just as a reference, I'm sure there are people with the original G1 who have flashed a countless number of times over several years and still have it working.
^^This.
If it gives you peace of mind, think about how many times a ROM chef's phone gets flashed in its lifetime and usually if the phone dies it's on account of flashing something experimental that bricks the phone (wrong radio, etc.) I've never heard of someones NAND actually burning out. I flashed my TouchPro and TouchPro2 quite literally hundreds of times if that makes you feel better.
kbrn said:
As far as I know by flashing a lot you can damage the relationship with your wife or g/f due to spending a lot of time doing it.. besides that I believe that the only way you can damage your phone is due to a bad flash or flashing something that wasn't exactly supported by the Shift.
Click to expand...
Click to collapse
THIS. Main danger.
^ Shift Faced
jesusice said:
THIS. Main danger.
^ Shift Faced
Click to expand...
Click to collapse
Agreed!
Sent from my PG06100 using XDA Premium App
Thanks for all the answers, you guys are great I really appreciate your help. You're replies have put my mind at ease seeing as my level of flashing honestly doesn't seem that excessive compared to that of a developer's.
Sent from my PG06100 using XDA App
On my HeroC I changed roms two to three times a week. When CM6 came out, it was everyday (with full wipe) thanks to the nightlies. Then aosp started releasing his stuff in IRC yada yada.
My heroc made it well over a year of that torture. My wife did as well, barely.
share your idea, i not sure would i update my phone with safe or risk firmware
The Samsung official updates are risk free... Bricks occur by doing wipes in CWM..
Those who bricked even doing the regular factory reset has a HISTORY of flashing modified firmware. Virgin phones are not affected, imho.
Zapped through server hops to XDA forums
praetorius said:
Those who bricked even doing the regular factory reset has a HISTORY of flashing modified firmware. Virgin phones are not affected, imho.
Zapped through server hops to XDA forums
Click to expand...
Click to collapse
Virgins don't use Gnotes, they would be scared of something so big
friedje said:
Virgins don't use Gnotes, they would be scared of something so big
Click to expand...
Click to collapse
+1
vivek2701 said:
The Samsung official updates are risk free... Bricks occur by doing wipes in CWM..
Click to expand...
Click to collapse
it's not true
friedje said:
Virgins don't use Gnotes, they would be scared of something so big
Click to expand...
Click to collapse
Good one lol
Elle est bonne celle la
friedje said:
Virgins don't use Gnotes, they would be scared of something so big
Click to expand...
Click to collapse
+1 that means you have to risk to get what you wanted.
vivek2701 said:
The Samsung official updates are risk free... Bricks occur by doing wipes in CWM..
Click to expand...
Click to collapse
You should know that this isnt true... Brick with ICS stock have happened... no CWM involved at all.
I guess they depend on that OTA and Kies update are not Wipe upgrade so no one will have a problem. Still, it's not a good idea to give people a poisoned Ice Cream!
So far in my country (Singapore), I have not heard of super bricks on the local forums yet.
They warned about no cwm wipes though .
Closest so far was someone who softbricked at bootloader after OTA update, then WIPED and FACTORY RESET his phone, and failed too.
Saved by flashing ICS via Odin.
Time will tell over the weekend about this issue.
vivek2701 said:
The Samsung official updates are risk free... Bricks occur by doing wipes in CWM..
Click to expand...
Click to collapse
WRONG. There are reported instances of people bricking in stock factory reset.
praetorius said:
Those who bricked even doing the regular factory reset has a HISTORY of flashing modified firmware. Virgin phones are not affected, imho.
Zapped through server hops to XDA forums
Click to expand...
Click to collapse
Is this true? I updated OTA and did a full wipe in stock recovery (how could I imagine that was risky?). Never flashed anything onto this Note before. Now, everything works (except for the heating and the poor battery life, due to wakelocks, i guess) but I'm scared to death, so i haven't even tried to go back to GB via pc odin.
Has anybody got a hard brick doing factory reset in a "virgin" Note??
oscarsalgar said:
Is this true? I updated OTA and did a full wipe in stock recovery (how could I imagine that was risky?). Never flashed anything onto this Note before. Now, everything works (except for the heating and the poor battery life, due to wakelocks, i guess) but I'm scared to death, so i haven't even tried to go back to GB via pc odin.
Has anybody got a hard brick doing factory reset in a "virgin" Note??
Click to expand...
Click to collapse
Seems to be lots of guess work going on. I have been checking my local forums, so far nothing out of the ordinary. Not sure about the other regions though.
The thing is that the bug has a probability of bricking your phone each time a wipe occurs, making it practically difficult to tell whether our OTAs are actually immune or we are being lucky thus far.
iihito702 said:
share your idea, i not sure would i update my phone with safe or risk firmware
Click to expand...
Click to collapse
Because its SAMSUNG
Slow (on updates)
Absurd (with end user policies)
Meaningless (this does not need an explanation)
Selfish and shameless (won't admit there's a bug)
Unreliable (isn't it?)
Neglected (end users are always neglected)
Garbage (garbage software on great hardware)
I hope this helps, OP.
Well I guess that Samsung are looking at it like this.
Problem nearly only occurs in CWM during wipe/reset so people effected are nearly "only" the ones that have moddified there phones. I dont think its because Samsung does not care about the "modding/developer" comunity but this is only a very small percent of the total number of customers who buy Note's.
Secondly.
As far as I have seen all official OTA roll-out have been non-wipe. Which mean most people will never wipe there phone. Even then out of these only a VERY few will actually have any problem and I guess Samsung will simply take those warrenty costs that might come from that.
Boy124 said:
Because its SAMSUNG
Slow (on updates)
Absurd (with end user policies)
Meaningless (this does not need an explanation)
Selfish and shameless (won't admit there's a bug)
Unreliable (isn't it?)
Neglected (end users are always neglected)
Garbage (garbage software on great hardware)
I hope this helps, OP.
Click to expand...
Click to collapse
Bahhh they all suck. I'm coming from all HTC and this phone to factory support ain't no different..
I remember the little game HTC played with us EVO users when they limited our fps to 30 and tried stroking us it was a limitation due to HDMI out or whatever..
Then someone here cracked it and they changed their tune.
At least we aren't dealing with locked boot loaders. All these companies suck so I buy the best hardware I can and run a cyanogenmod variant.
Sent from my GT-N7000
senectus said:
You should know that this isnt true... Brick with ICS stock have happened... no CWM involved at all.
Click to expand...
Click to collapse
Anyone you personally know who've experienced this?
Sent from my GT-N7000 using Tapatalk 2
Entropy512 said:
WRONG. There are reported instances of people bricking in stock factory reset.
Click to expand...
Click to collapse
Reported but never really confirmed. Could be just a case of user error.
Sent from my GT-N7000 using Tapatalk 2
Honestly, there have been a lot of "reported" bricks even before lpy came out due to user error. It's just now that it's being highlighted because a few hardcore flashers experienced it. I personally think it's being blown out of proportion. Just my opinion i'm a member of a lot of note forums with regular people who don't do hardcore stuff except flash stock roms and never do i see them posting that thier phones got bricked due to lpy or any stock ics roms released by samsung.
Sent from my GT-N7000 using Tapatalk 2
Hey, I've seen many threads about people bricking their phone, and I don't wanna end up like them.
So, I want to unlock bootloader,root and flash kernel, I've read using TOOLKIT isn't the best thing to do, so I'll follow this tutorial.
My question is, what can go wrong? How to prevent anything from going wrong?
Sorry if it's a stupid question, but it's my first Android and I rather ask than be sorry, thanks in advance.
Ciclop said:
Hey, I've seen many threads about people bricking their phone, and I don't wanna end up like them.
So, I want to unlock bootloader,root and flash kernel, I've read using TOOLKIT isn't the best thing to do, so I'll follow this tutorial.
My question is, what can go wrong? How to prevent anything from going wrong?
Sorry if it's a stupid question, but it's my first Android and I rather ask than be sorry, thanks in advance.
Click to expand...
Click to collapse
Just make sure anything u do you read the thread and defiantly the op and only flash stuff that made for the N4 u should be good. Read read read and learn. I've only bricked one phone and I know what I did wrong its very hard to brick a phone so long as u don't just go flash stuff u dont know what it is.
Oh yea don't over clock your phone and run benchmarks its stupid and has fried a few also. I'm onderclocked to 1134 and I still run smooth as butta.
Sent from my Nexus 4 using Xparent Blue Tapatalk 2
Ciclop said:
Hey, I've seen many threads about people bricking their phone, and I don't wanna end up like them.
So, I want to unlock bootloader,root and flash kernel, I've read using TOOLKIT isn't the best thing to do, so I'll follow this tutorial.
My question is, what can go wrong? How to prevent anything from going wrong?
Sorry if it's a stupid question, but it's my first Android and I rather ask than be sorry, thanks in advance.
Click to expand...
Click to collapse
For a REAL hard brick on a Nexus device, you really have to do something wrong. Like I did with my Nexus S .
A real hard brick, one that isn't even repairable with a JTAG brick repair service, it never happens with a Nexus device. Well, ALMOST never. I made it happen. I don't even know what I did wrong, but apparently I screwed up the radio. Even the best of the best (Adam Outler) wasn't able to repair it. It happened the day after I installed a new ROM and a mod. The battery drained really fast. After it was dead, I plugged it in the charger, booted up my phone, started the browser, and BAM. Dead. Forever.
But I wouldn't worry about those things. Just don't do too much overclocking, because there are ways to screw up the hardware inside. Almost all bricks are fixable. If you can access fastboot mode you're okay. If you can't, there are still ways to fix it, but it might cost you some money. I don't know if Adam Outler's Unbrickable Resurrector tool works with the N4, but that's also an option if you think you really screwed up.
1) Make sure that you never flash a file that wasn't designed for the Nexus 4 (MAKO)
2) Make sure that you don't have empty batteries when you flash. 50% would be a safe minimum (though I personally frequently flash with much less than that)
3) Flashing radios / bootloaders is traditionally amongt the most dangerous operations that you can do. Make sure to check MD5 on all radios (you can check on every file if you want to be super careful)
Note: the reality is that with a nexus device, it's almost impossible to brick your device. Even if you do all of the things above wrong, you'r probably still safe. BUT, you were looking for advise--so follow those three points and you should be fine.
OP, read the link in my signature about toolkits and it will answer your question.
Sent from my Nexus 4 using xda premium
Thank you all for quick replies!
I only plan on flashing Franco's/Faux's kernel, hopefully everything will go well
unlocking the BL on a nexus is very easy. I am not sure if you need a toolkit for that.
but yeah use one if you feel more comfortable with it.
also as of now do not overclock the processor as that has been causing some bricks AFAIK.
Androyed said:
For a REAL hard brick on a Nexus device, you really have to do something wrong. Like I did with my Nexus S .
A real hard brick, one that isn't even repairable with a JTAG brick repair service, it never happens with a Nexus device. Well, ALMOST never. I made it happen. I don't even know what I did wrong, but apparently I screwed up the radio. Even the best of the best (Adam Outler) wasn't able to repair it. It happened the day after I installed a new ROM and a mod. The battery drained really fast. After it was dead, I plugged it in the charger, booted up my phone, started the browser, and BAM. Dead. Forever.
But I wouldn't worry about those things. Just don't do too much overclocking, because there are ways to screw up the hardware inside. Almost all bricks are fixable. If you can access fastboot mode you're okay. If you can't, there are still ways to fix it, but it might cost you some money. I don't know if Adam Outler's Unbrickable Resurrector tool works with the N4, but that's also an option if you think you really screwed up.
Click to expand...
Click to collapse
My N4 its bricked, I contact Google for RMA. Now, my history...
N4 bought 13/nov.
-Rooted with Nexus 4 Toolkit
- ROMS installed: 1- Stock (default) 2- Minco 3- Xylon (when i got bricked)
- Kernels:1- Stock (default) 2- Franco 3- Faux (when i got bricked)
In kernel Ops: (Last Faux beta kernel)
- Underclock: (YES, READ, UNDER): 1mgz at max
- Undervolt: -137 mv all freqs
- GPU Downgraded to 200mhz
- Screen settings changed
- Hapatic feedback downgraded to 50%
That was my config. Now comes the drama...
My phone was perfectly OK at less for 2 days with that kernel and ROM combination (because i've updated few days before got bricked) So, my phone even with the downgrade config was so smoth and everything was perfectly ok.... the night of new year, when I was taking a shower, my N4 was charging SO SLOW, i dont give a f*ck and continue my night so normal, then I went out to my gf house, i have like 30 % and decide to charge again, starts charging slow again, now im worried about it so i decide to restart the phone, and problem still there... but now the device was overheating so much and the phone got discharged because i got to go, when I come to my house in the morning, i put the charger, the only thing it do is blink red led, nothing else.
Conclusion:
When your phone got bricked doesn't mean you have the guilty, because mine was STABLE for at least 2 days, for my, it was an hardware prob.
Now, the only way, RMA.
So if I was you, I lock my bootloader again.
Well, I recently was talking to a friend who got a Galaxy S III some time ago.. And his device suddenly had some kind of SOD..
He was stock TW and non rooted.. He's like the 99% of the people out there whom will never flash a custom rom So he gave me the device to see if I could fix it..
First thing I noticed was I could not enter to recovery or odin mode, changed battery, connected to pc and nothing.. Was completely dead.. So i started reading about on sIII forums and seems like SIII its infected with a bug called SDS (sudden death syndrome) i was like wtf?.. The bug consist in: you could be either charging your device or happily using it and when the screen goes off the device will never ever again will turn on.. The effect of the bug? It burns the emmc chip and you either lose your device (like him because he bought it in Europe and we are from Venezuela so no warranty) or if you have warranty you will receive a new device..
Thing its that after seeing that.. Damn our mmc_cap_erase bug its nothing compared to that..
What the hell its samsung doing with the quality control and the engineering?
Devs in SIII forums already patched the bug in the kernel but hey that's a preventive solutions.. Not a fix for already bug triggered devices.
So if any of you have an SIII or a family member.. Go read about it and patch it
Edit: here a link to the issue http://forum.xda-developers.com/showthread.php?t=2091045
Tapatalking on my n7000
msedek said:
Well, I recently was talking to a friend who got a Galaxy S III some time ago.. And his device suddenly had some kind of SOD..
He was stock TW and non rooted.. He's like the 99% of the people out there whom will never flash a custom rom So he gave me the device to see if I could fix it..
First thing I noticed was I could not enter to recovery or odin mode, changed battery, connected to pc and nothing.. Was completely dead.. So i started reading about on sIII forums and seems like SIII its infected with a bug called SDS (sudden death syndrome) i was like wtf?.. The bug consist in: you could be either charging your device or happily using it and when the screen goes off the device will never ever again will turn on.. The effect of the bug? It burns the emmc chip and you either lose your device (like him because he bought it in Europe and we are from Venezuela so no warranty) or if you have warranty you will receive a new device..
Thing its that after seeing that.. Damn our mmc_cap_erase bug its nothing compared to that..
What the hell its samsung doing with the quality control and the engineering?
Devs in SIII forums already patched the bug in the kernel but hey that's a preventive solutions.. Not a fix for already bug triggered devices.
So if any of you have an SIII or a family member.. Go read about it and patch it
Tapatalking on my n7000
Click to expand...
Click to collapse
Thanks.my cousin just bought one but it has warranty.i think i cant make him trust me.what if i brick the phone?or what if after some time he bricks the phone?so their will be no warranty for a phone that is modified
I think i should warn him and let him decide
Sent from my GT-N7000 using xda premium
Samsung :thumbdown: for that..
click THANKS BUTTON if I helped…
Recognized Distributor™
i know of a close relative with a white s3 , after two months of purchase the set stopped charging from wall socket, the charging worked with laptop ......since he had warranty he was told the motherboard needed replacement and he got that done. the back of it has a spider-like faint grey mark and he asks me if its cracked or what ....he doesnt want to go back to service centre and wont let me root it and he doesnt have patience for xda. he is on 411 still.
he didnt pay for it himself, doesnt have a job yet and its not a gift...pretty chaotic situation if u ask me !!
bloody money grubber *** *****. Poor quality control. There's still no permanent solution for N7000 emmc brick bug.
sepehrthegreat-iran said:
Thanks.my cousin just bought one but it has warranty.i think i cant make him trust me.what if i brick the phone?or what if after some time he bricks the phone?so their will be no warranty for a phone that is modified
I think i should warn him and let him decide
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Talk to him and make him read about it here
http://forum.xda-developers.com/showthread.php?t=2091045
Check if he have an affected device..
Tapatalking on my n7000
I sold My s3, a few days ago, which was my first choice and bought note.
Now I read about brick bug. Wtf?
Can I buy device and be safe and peacefull?!
Sent from my GT-N7000 using xda app-developers app
krivinash said:
I sold My s3, a few days ago, which was my first choice and bought note.
Now I read about brick bug. Wtf?
Can I buy device and be safe and peacefull?!
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Just flash a safe kernel according to your rom and live in peace
Tapatalking on my n7000
msedek said:
Just flash a safe kernel according to your rom and live in peace
Tapatalking on my n7000
Click to expand...
Click to collapse
The brick bug on the Note shouldn't be a problem anymore. Just flash the PhilZ kernel which gives you root without increasing the flash counter and you're Note is fixed. You can also download Chainfires got brick bug app.to see if your Note is affected at all. Or you download the brick bug app from the play store which does the same.
Sent from my revived Galaxy Note
N7000
My Samsung Galaxy Note is on JB Alliance Rom XXLSC Beta1.1 which comes with it's own kernel and I don't think PhilZ is supporting it, PhilZ and Alliance Cook had a minor misunderstanding/fallout, (I could be getting my Roms mixed up) I've flashed different Roms 10+ times. Started to worry reading threads on here so downloaded the eMMC Brickbug Check app. All's good here
Maybe you wiped on STOCK ICS KERNEL which is known to cause the Brickbug
click THANKS BUTTON if I helped…
Recognized Distributor™
Arobase40 said:
The brick bug on Note is just a legend... ^^
The only safe kernel I'm aware of is the stock one !
The sole time I flashed a non stock kernel I got my Note fully bricked !!!
Click to expand...
Click to collapse
Yeh you are right!so can you post a video wiping on your stock kernel???!!!
I really appreciate the job that Phil and other Devs are doing
Sent from my GT-N7000 using xda premium
Wrong forum yo dicuss it, but u have a good point. I have also discussed this on s3 forum, but seems like some regions got that buggy phone or maybe this is the samsungs way of self killing the device....whatever it is one should get what they paid for.
Well for my note i have that brick bug thing but i factory resetted my stock rom so many times and my device is fine. So i think stock roms are harmless and this emmc_cap was put to prevent users from using a custom ics in the initial days ,which definitely the devs figured out and fix it in their custom kernel.
Sent from my GT-N7000 using xda app-developers app
qazibasit said:
Wrong forum yo dicuss it, but u have a good point. I have also discussed this on s3 forum, but seems like some regions got that buggy phone or maybe this is the samsungs way of self killing the device....whatever it is one should get what they paid for.
Well for my note i have that brick bug thing but i factory resetted my stock rom so many times and my device is fine. So i think stock roms are harmless and this emmc_cap was put to prevent users from using a custom ics in the initial days ,which definitely the devs figured out and fix it in their custom kernel.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
What you believe it's completely different from what's a FACT... The bug its not some legend based on empirical trials.. It's been proved that mmc_cap_erase triggers the bug because the mmc chip can't handle secure erase formating .. Simple the chip gets damaged..
The bug was introduced on ICS kernels.. And it's so true that Samsung even disabled secure erase from JB kernels because they say that insecure erase its not harmful...
We disagree because it hasn't been proven (that insecure erase its safe) .. So the best way to be safe its disabling mmc_cap_erase and no formating at all..
To everyone talking nonsense about wiping on stock ICS kernels, next time I'll report you all because that's misleading.. Maybe you have been lucky wiping but that's the problem.. It can happen on wipe number 1 or wipe number 1000.. Who knows..
Tapatalking on my n7000
msedek said:
What you believe it's completely different from what's a fact... The bug its not some legend based on empirical trials.. It's been proved that mmc_cap_erase triggers the bug because the mmc chip can't handle secure erase commands.. Simple the chip gets damaged..
The bug was introduced on ICS kernels.. And it's so true that Samsung even disabled secure erase from JB kernels because they say that insecure erase its not harmful...
We disagree because it hasn't been proven (that insecure erase its safe) .. So the best way to be safe its disabling mmc_cap_erase and no formating at all..
To everyone talking nonsense about wiping on stock ICS kernels, next time I'll report you all because that's misleading.. Maybe you have been lucky wiping but that's the problem.. It can happen on wipe number 1 or wipe number 1000.. Who knows..
Tapatalking on my n7000
Click to expand...
Click to collapse
Agree with the misleading but a little bit respect for the people sharing own experience with us is not so bad!
Any user who reads this attention:
<<do not,under any condition,I repeat do not wipe from your stock ICS recovery>>
sent from galaxy s4(testing dev edition) using xda premium
sepehrthegreat-iran said:
Agree with the misleading but a little bit respect for the people sharing own experience with us is not so bad!
Any user who reads this attention:
sent from galaxy s4(testing dev edition) using xda premium
Click to expand...
Click to collapse
I'm not disrespecting anyone.. Own experience it's bullcrap.. Software developing and electronics engineering its not popular believes or "experiences" everything its done by scientific methods, procedures and knowledge of how things works..
A clear example could be that an engine its build to reach [email protected] if you force the engine beyond that it will get damaged...
Now some people could force it to 160kph and maybe it will work some times.. But at some point it will break.. And you know this because engineers made the engine to work Max at those speeds and RPMs..
It's matter of design.. Not "experiences"
Tapatalking on my n7000
Its been reported that stock ICS is unsafe, since the day it was released, people know about it and avoid it, so anyone saying that it is safe is talking nonsense, if they wanna take the risk and brick their device then thats their choice.
Moving back on to the S3 chips, my GF has had hers several months now and luckily havent encountered any issues at all, I tend to only find device faults AFTER ive purchased them !! i really need to research more before buying
the S3 is 100% stock, my GF wont let me mod it but luckily the device has warranty for the lenght of the contract which is 24 months, so if it ever breaks within this time they'll just fix it for me free of charge
Still, it makes me wonder WTF are a giant company like Samsung doing about this issue ? SGS 2, SGS 3, SGN 1 (unsure about SGN2)
this isnt acceptable from Samsung, regardless if <5% of devices suffer this, I would expect sudden death and insane chips from a cheap chinese knock off, but not a £500 smart phone.
If u say everything is scientific and methodical then howcome samsung didnt knew about it before ics and please define secure wipes, because once things are wiped what are u protecting. Third samsung is the holder of exynos sources. Howcome they didnt knew about it earlier, and discovered by the community first. So here ur proven total wrong, samsung knew about it and they even responded some complains bricked by this issue.
Do u pick articles from retro and bring those things here ????
Sent from my GT-N7000 using xda app-developers app
qazibasit said:
If u say everything is scientific and methodical then howcome samsung didnt knew about it before ics and please define secure wipes, because once things are wiped what are u protecting. Third samsung is the holder of exynos sources. Howcome they didnt knew about it earlier, and discovered by the community first. So here ur proven total wrong, samsung knew about it and they even responded some complains bricked by this issue.
Do u pick articles from retro and bring those things here ????
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
They knew about it. It was fixed in Galaxy Nexus eMMC firmware but yet they kept shipping other devices with the same firmware.
Cut the crap: Do you know more about the emmc brick bug than some elite and recognized devs here ?
qazibasit said:
If u say everything is scientific and methodical then howcome samsung didnt knew about it before ics and please define secure wipes, because once things are wiped what are u protecting. Third samsung is the holder of exynos sources. Howcome they didnt knew about it earlier, and discovered by the community first. So here ur proven total wrong, samsung knew about it and they even responded some complains bricked by this issue.
Do u pick articles from retro and bring those things here ????
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Before ICS (gb and older) , Android used recursive deletion.. (no mmc_cap_erase procedures in the kernel).. Samsung didn't know about it because the chip was designed under another required process and there's no way to know this kind of things until you produce something in big scales.. As you said you could spend months wiping everyday on stock ICS and never get brick, but after 6 months of doing it the next day you brick...
Entropy went to samsung and he tried several times to brick a note in front of samsung engineers with no luck.. But the bug its there from the first ICS firmware to the very last and considering we are still officially on ICS, i dont think it's a "retro" information...
Exynos source has nothing to do with the emmc chip and what kind of delete/formating methods will damage it.. Heck even deleting big files (over 500 mb) could trigger the bug.
Once again you are talking nonsense
Tapatalking on my n7000
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