well, after several threads on the LPY issue
i hope someone can make some order in this mess and give us (the ppl) an answer on the LPY risk and how to avoid it.
while i myself don't have enough knowledge on the issue i hope someone who does would answer and i will link the answers in the first post (this one)
iakovl said:
well, after several threads on the LPY issue
i hope someone can make some order in this mess and give us (the ppl) an answer on the LPY risk and how to avoid it.
while i myself don't have enough knowledge on the issue i hope someone who does would answer and i will link the answers in the first post (this one)
Click to expand...
Click to collapse
Depends who you ask. I say yes, it is safe. The best thing you can do is wait a day or two and see what happens. If there is truly a problem, you will see more than just one brick.
I had a brick la7 or how was it called. Was using stock Rom and upgraded with Kies. **** happens you can't do anything if it has to be.
Sent from my GT-N7000 using Tapatalk 2
Simple answer : The ICS kernel leaks are not safe. IT HAS NOTHING TO DO WITH THE ROM. IT IS THE KERNEL.
Long answer : Clockwork doesn't play well with the new kernels... No one knows why. Some people brick... Some don't. I didn't. Chas did.
Real simple answer : If you have to ask, then don't do it.
Just like with the leaked kernels LP5/LP6 ,some people would brick while others are fine.
Just avoid it if you can ,and if you must taste ICS then may I advice you to flash cm9 ,it's far better than the stock in my opinion .
Short answer: maybe..
This is not a leak! It is a official release from Samsung.
Sent from my GT-N7000 using xda premium
but if you are in germany and get the ota is dangerous too?
I bet a good portion of bricks are user error.
Sent from my GT-N7000 using xda premium
tyrael64 said:
but if you are in germany and get the ota is dangerous too?
Click to expand...
Click to collapse
No, only if you root and wipe.
tyrael64 said:
but if you are in germany and get the ota is dangerous too?
Click to expand...
Click to collapse
I don't think that people being in another country be a reason that it bricks for other people or not.
In the end the versions are all the same, just with some modifications. (I mean the versions that are brought out per country)
I have xeu uk unlocked phone and i updated to ics via odin and german update love it note is nippy and so far no crashes on apps
Battery seems ok to glad i took plunge
Sent from my GT-N7000 using xda premium
Official Samsung ICS Update -> Safe
Official Samsung ICS Update + anything related to flashing/getting root -> AT YOUR OWN RISK
If you want a stock Touchwiz ICS experience you're going to be OK. If you want to do more with your device, like always you do that at your own risk.
I jump sooner than i usually do and flashed it because i thought stock roms were safe. It did brick my phone when i made a backup and then using that backup. How i got my phone back going is downloading pc odin and an older gingerbread and flashing it. The ics rom do work very well. But you cant used the backups made with cwm. Im using LPY rightnow after unbricking it with pc odin and an older gingerbread. If u get it going LPY is worth flashing its smoother than gingerbread and very responsive. I hope someone can figure out why we cant use our backups.
Sent from my GT-N7000 using xda premium
The answer is very simple.
Can you follow directions? Can you not do things outside of what is needed?
If so then yes.
If you go from GB rooted to ICS Official (with or without CF), By the book, you will have no problems.
Do not do something stupid, like say flashing CF Kernel with CM9 first
crawlgsx said:
The answer is very simple.
Can you follow directions? Can you not do things outside of what is needed?
If so then yes.
If you go from GB rooted to ICS Official (with or without CF), By the book, you will have no problems.
Do not do something stupid, like say flashing CF Kernel with CM9 first
Click to expand...
Click to collapse
I agree with this. If only people will follow procedures based on the guidelines and without experimenting or creating new instructions outside the normal conditions, i guess it should work accordingly.
Sent from my GT-N7000 using xda premium
I think the safest thing is if you want to go to another rom go via a stock gb and make sure to pc odin and flash pit with repartition check then root and run cwm from it
Sent from my GT-N7000 using Tapatalk 2
Right now: We don't know. We have at least one person who bricked when wiping with the new kernel.
That's the most dangerous operation - wiping in recovery. However a large file deletion could trigger the issue. It's not likely, it hasn't happened yet, but it's a similar eMMC access pattern so it's possible.
Jack143 said:
It did brick my phone when i made a backup and then using that backup. How i got my phone back going is downloading pc odin and an older gingerbread and flashing it.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Not sure that is the kind of brick "we" are talking about. The bricks that happens with ICS i9220 leaks are hard bricks and there is no way to recover from them except a motherboard exchange.
However, there is always a small risk to softbrick (when flashing anything) but these are not severe and you could recover from them in different ways depending on what type of softbrick it is.
It is still under debate if the new ICS based on LPY has the same potential to hard brick your note as the ICS i9220 leaks.
Personally I belive that if we don't get any more reports of true hardbricks then it must have been a combination of bad luck and in some way bad hardware.
Entropy512 said:
Right now: We don't know. We have at least one person who bricked when wiping with the new kernel.
Click to expand...
Click to collapse
We have one person who bricked their phone by wiping from CF Kernel combined with CM9 Official, clearly NOT what the recommended is anyway.
We have 0 (reported) bricks from those of us who follow the directions.
If on anything other than GB, ODIN to stock GB. Then use mobile odin or odin to flash ICS offical; with or without latest CF Kernel (if you want root). THIS is the safe and recommended way. If you follow any other idea's or thoughts, you are doing so KNOWING DAMN WELL you could brick your phone. Do NOT use CWM functions from any other build of ICS, Period. That is what is safe right now.
Why is this so hard for people?
Why does everyone feel the need to panic and spread chaos and over exaggerate the problem.
No offense Entropy, I know you are a smart man and you know your stuff, but seriously you are making this MUCH worse than it should/needs to be. It has gone from a general "at your own risk" to a spread of fear and chaos.
Strictly my opinion of course.
Related
Howdy!
(sorry... guess Stampede is getting to me...)
I am looking for a Bell Vibrant (Samsung Galaxy S i9000M) expert in the Calgary AB area.
I have successfully rooted, installed custom ROMs and then "bricked" two (yes, 2) i9000M phones. Both times, I "bricked" when using ODIN.
Yes, I had researched how to use ODIN before using it... trading weeks of my "life" for the said pearls of ODIN wisodm . I've obviously missed something important, have very bad karma, or I am just an idiot...
After "ODINing", both phones ended-up looping at the SGS Logo. I have tried re-flashing via ODIN many times, always with the same result. I can get both phones into "download" mode (i.e. the yellow triangle screen).
Anyways, I am hoping to find a local expert who is willing to meet me somewhere (library???), look at my phones and confirm:
1. My SD cards have crashed; OR
2. I am a uber noob idiot;
I am also hoping that if #2 is proven the case whether the charitable expert individual might suggest a way and/or help me to fix these expensive plastic paper weights.
So, any charitable local experts willing to help-out an unlucky moron?
t.
What version are you flashing via odin?
you'll most likely have to take them in for warranty repair
@ BottleB:
I tried flashing JH2 (Stock Bell Vibrant ROM???) and 512.pit.
I had original installed CM 7.1 RC1 (via CM wiki method). Everything work awesome.
I decided to try some OC'ing, and flashed the Glitch v10 kernel... with spectacular speed results! Unfortunately, post Glitch flashing, SMS would receive but not send. Researched possible causes and cures for this, could not find any, and decided to revert to stock and try again...
... and here I am.
@graison:
I bought these i9000M's "used" off Kijiji (HATE contracts!). Both worked fine until ODINing.
As such, Bell won't "warranty" these devices (tried with the first one).
I have no problems paying for repairs... if the cost is reasonable. Any ideas/suggestions on the "how's and where's" I can go about trying this?
They most probably had lagfix installed which was not disabled when reflashed to stock. You need to flash the rfs...bin file (i'll upload it later tonight for faster accessing). I found the fix here on xda under a thread on bricked phone.
The lagfix change the filesystem used by the phone. Stock firmware is only compatible with the RFS filesystem. Also, i recommend that you flash KC1 instead oh JH2. Froyo is way better than eclair.
Sent from my GT-I9000M using Tapatalk
Found the fix
Here is the link http://forum.xda-developers.com/showthread.php?t=984140
Sent from my GT-I9000M using Tapatalk
urself25 said:
Found the fix
Here is the link http://forum.xda-developers.com/showthread.php?t=984140
Sent from my GT-I9000M using Tapatalk
Click to expand...
Click to collapse
+1
Pretty sure thats the problem. You flashed stock kernel on a EXT4'ed filesystem.
@urself25,
Ah-ha... I have a feeling that you are right, and that I did miss something CRAP!
I await your upload on bated breath... in the mean time, I will search the million posts for the fix you mentioned.
ooops... you beat me to my response.
Tell us how it went when you'll try the RFS fix.
Tried the RFS fix as per the instructions in the link.
After rebooting, both phones go into a SGS start-up screen loop.
Downloading ODIN files right now (JVE - Gingerbread???). I will try and reflash and let you know how it goes.
I'm in Airdrie, don't flash gingerbread! Sell me both phones for $100. Or search for the "trick to unbricking my sgs" thread. It worked for me. Though I am worried that because they were on Eclair firmware, they may be dead if they never got the bootloader update. I repeat, DO NOT FLASH GINGERBREAD!
Sent from my GT-I9000 using XDA Premium App
try a deodexed KC1 (current firmware for Bell Canada) firmware from [Ramad]
Using ODIN -- use a 512.pit file, re-partition ticked, Bootloader Update (just in case), and put PDA -> PDA, PHONE -> PHONE, etc.
http://forum.xda-developers.com/showthread.php?t=948790
IF it takes you to android recovery 2e or 3e (i cant remember), do a factory reset/cache wipe, and even format sd if you want. it SHOULD work (i just did this too and it worked mint.
Holy crap! It's near 4:30 a.m., and I FINALLY restored/recovered my two phones! Truth be told, I spent half the night screwing up my phones WAY worse than they were ... and the second half of the night cleaning up my mess
@urself25 & @BottleB - I can't say definitively whether or not your link really helped me any... but it definitely put me on the right path. Thanks a lot boys!
@xWarMachine04 - Thanks for the directions and link! I *kinda* went that route in a round-about-way... I just wished I would have check my post and found your reply 4 hours ago! Regardless, my gratitude.
@hansonator - Thanks but no thanks; for $100, I'd use my bricked phones as door stops. REGARDLESS, I do thank you for your gingerbread warning. I did have problems with gingerbread, and (successfully) shifted to froyo on your recommendation. Thanks dude!
All's well that ends well...
- t.
Most probably the firmware didn't install properly because fo the problem RFS problem. A fresh reinstall of the firmware with bootlader finally fix the problem. Glad everything worked out for you.
I'm in Calgary. But I'm hardly an expert. I think you've gotten further than I have.
So I have nothing to contribute to this thread. I'll see my way out.
Glad u got your phones up and running! Good thing is you probably learned a lot during that night!
Sent from my GT-I9000 using XDA Premium App
BottleB said:
Glad u got your phones up and running! Good thing is you probably learned a lot during that night!
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
~~~~~~
Learned a lot? No kidding...
Why is it that the biggest/best lessons always have to be soooo painful???
I must admit that my opinion of ODIN has sure changed; it's a pretty slick piece of software when it works right (i.e. when you have half a clue about what you are doing)!
@urself25 - It wasn't so much a firmware installation problem, as much as the SD card file format (like you suggested in the first place). I kept getting a message along the lines of "can't mount sd; storage not ready... blah blah blah... file format blah blah blah...". I did have to do a complete reinstall (PDA, Phone/Modem, CSC) WITH repartition... and on the second phone, a Bootloader update. Didn't do the repartition in the first place because 95% of the threads out there advise against it. Anyways, my solution was pretty much @xWarMachine04's approach/solution.
Unfortunately, I have developed the "randomly self-invoking" back button problem on the second phone. Fortunately, there seems to be an easy fix for that... but that's what I thought at the beginning of this journey!
Again, thanks everyone!
- t.
Now if you want to flash gingerbread it should be OK. I only advised against it because the phones were bricked. Good to hear you got it sorted out.
Sent from my GT-I9000 using XDA Premium App
davanw said:
I'm in Calgary. But I'm hardly an expert. I think you've gotten further than I have.
So I have nothing to contribute to this thread. I'll see my way out.
Click to expand...
Click to collapse
i'm in Calgary too, but i am no expert either... however i have been able to upgrade my phone from froyo (after taking my i9000m to market mall due to the internal card dying back in December), to gingerbread.
First went with Darky's 9.5... then upgraded to 10 and had NO issues with GB. I'm on GB still using the F1 Rom V9 now and love this.
For the OP: Glad to see you were able to fix both of your phones! Congrats... definitely no easy feat!
[Poll] I have bricked my Note while..
Here is thread to boost up confidence of newbie, many new to android asking chances of bricking of note.
I think you brick it, if you don't follow guide properly
Last option for all, whether you have bricked it or Not
Let's watch, what poll says !
I never bricked mine, largely thanks to your guides.
Thanx for compliments
Sent from my GT-N7000 using xda premium
Just make sure you have a jig handy (~£7 off amazon)
Sent from my GT-I9100 using xda premium
How do i identify whether a phone is bricked? I've got into a lot of **** spots, but gotten out of them. If i brick my phone does it mean i can never use it again?
bharat4ever said:
How do i identify whether a phone is bricked? I've got into a lot of **** spots, but gotten out of them. If i brick my phone does it mean i can never use it again?
Click to expand...
Click to collapse
brick - mean it will not boot up
Softbrick means recoverable
Hardbrick means dead
brick? never. not following instructions. yes im guilty.
dr.ketan said:
Softbrick means recoverable
Hardbrick means dead
Click to expand...
Click to collapse
Is it even possible to hardbrick via Odin?
Sent from my GT-I9100 using xda premium
I think,Wrong pit n wrong rom(different device) can lead to it
bharat4ever said:
How do i identify whether a phone is bricked? I've got into a lot of **** spots, but gotten out of them. If i brick my phone does it mean i can never use it again?
Click to expand...
Click to collapse
a proper bricked phone will not turn on or do anything
otester said:
Is it even possible to hardbrick via Odin?
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Hmmm yeah!! There is this Kernel, no matter how you flash it, there is something inherent that would corrupt the flash drive, a rare instance where you have Download mode and recovery working but you cannot do a thing to restore your phone. Things happen, you know?
Only time mine has ever soft bricked has been on those few occasions when I have tried ICS and then tried returning to GB. There is always a way to get through a problem I think. Although I understand that there was a hard bricking episode recently with ICS on the note.
Luckily I was busy when that happened otherwise I'd have bricked mine.... No doubt
Sent from my GT-N7000
Oh yes, I soft brick my Note alright.. just yesterday... while I tried to flash to CheckRom RevoHD v6.... (had a v5 already installed)....
It would just stuck on the Samsung Galaxy Note N7000 Logo....
Restored it back using PC Odin
Personally, I don't think it has something to do on not reading properly the instruction on flashing.... I read it to a tee mind you.. yet the instructions presented have some gaps and loopholes that if the user isn't aware of it... most likely it would end up bricking their note as well...
Anyway, as the famous lines say 'That which can't kill you, makes you stronger...', I will continue flashing to whatever Custom Rom I want and I welcome the challenge of encountering the famous 'Bricking' again...
let's get it on!
@prem1
I think your poll option better fit in this option
It was issue with specific ROM n Kernel
isn't?
chasmodo said:
I never bricked mine, largely thanks to your guides.
Click to expand...
Click to collapse
+1. followed dr.ketan after reading it a thousand times. I am fortunate and cautious enough to stay away from ICS at the moment because I heard switching back to gingerbread is behind my skills.
Sent from my GT-N7000 using Tapatalk
Only time I bricked my phone was while deodexing. 'CP' command was not working, then I did not know about 'BUSYBOX CP' command. So I copied and pasted all deodexed apps and framework files using Root Explorer and dang! It was bricked =)).
If every newbie follows DrKetan's guide carefully there're 0% chances of ending up with bricked phone.
Trust the guide - make your mind.
Yesterday i think i soft bricked my Note. I tried to put pre rooted LC1 via *Odin 1.85 but it went wrong. Was stuck in factoryfs part. I pulled it off the cable.
It did only boot to recovery screen or download mode, so i just downloaded the stock rom LC1 and got it back online!
It is almost impossible to brick the Note. Unless you do it on purpose
offenberg said:
It is almost impossible to brick the Note. Unless you do it on purpose
Click to expand...
Click to collapse
I don't know if the emmc/mainboard got fried recently by flash/using the monster kernel/touch cwm whatever belongs to a brick, if it is, it's not impossible to brick the note, even you are an experienced user. Anyway, there's a risk on flashing, so be 100% careful.
Sent from the forgotten Atrix"2
AS Many of you know, there have been some People that have been experiencing hard bricking on their Note after Flashing leaked versions of ICS...... Thanks to Entropy512 & Chainfire we have some definitive answers on what is causing this.
THIS IS A MUST READ IF YOU ARE FLASHING CUSTOM ROMS........
DON'T BE LAZY, LAME or FOOLISH.... READ THIS NOW!!!!!
This will help you understand the risks and issues that have yet to be resolved ......
-Now Please Read the Article in the Link... (thx-EGZThunder1)
Thanks,................. Moderators
http://www.xda-developers.com/android/hard-brick-bug-on-galaxy-s-ii-and-note-leaked-ics-kernels/
Good one but I think there are too many threads now giving information on bricking etc,. I think it would be better if they are all combined and summarized in a single thread. Just my thought!
Seems redundant to have two stickies for the same topic?
And you posted this saying "leaked" long after official releases have been confirmed affected.
plz i ve read this article but i ve noob question
i am now using lpf prefectly, is it one of leaked ics ?
what leaked ICS mean ?
sehooo said:
plz i ve read this article but i ve noob question
i am now using lpf prefectly, is it one of leaked ics ?
what leaked ICS mean ?
Click to expand...
Click to collapse
It's not leaked ICS. It is the official stock ICS for Taiwanese devices. And it's all safe as long as you don't use CWM, do a factory reset from even the settings menu and also try not to delete huge files right from your phone's explorer.
Sent from my GT-N7000 using XDA
sujal said:
It's not leaked ICS. It is the official stock ICS for Taiwanese devices. And it's all safe as long as you don't use CWM, do a factory reset from even the settings menu and also try not to delete huge files right from your phone's explorer.
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
well I don't know I am on stock LPF rom and did a factory reset and no problems at all
I think this whole bricking thing is exaggerated
I upgraded from gb to lpy to lpf
and i used those way by dr ketan
http://forum.xda-developers.com/showthread.php?t=1659308
and rooted by cwm, is it safe or should I go back to gb?
Sent from my GT-N7000 using xda premium
hykhleif said:
well I don't know I am on stock LPF rom and did a factory reset and no problems at all
I think this whole bricking thing is exaggerated
Click to expand...
Click to collapse
It does not affect everyone but there a few 'unlucky' souls. Glad you aren't but avoid doing that. Even one brick is dangerous.
Sent from my GT-N7000 using XDA
If someone don't undestand yet...
read this:
http://forum.xda-developers.com/showthread.php?t=1633938
and pages 123, 124 e 125 of this:
http://forum.xda-developers.com/showthread.php?t=1490986&page=124
Now... stop giving bad advice based on what happens when you flash on your device!
The problem exists and it's not exaggerated.
It doesn't happen 100% of the times, but has high chances to happen !
wrong forum...sorry
yes it happen to me..
this is warning for official ICS too..
Yup... I'm still trying to figure out why we have TWO stickies on this subject now, one of which has had wrong information from the moment it was posted. (As stated before - even when THIS thread was first posted, it was already known that official releases were causing problems.)
Danger after going back to GB
Entropy512 said:
Yup... I'm still trying to figure out why we have TWO stickies on this subject now, one of which has had wrong information from the moment it was posted. (As stated before - even when THIS thread was first posted, it was already known that official releases were causing problems.)
Click to expand...
Click to collapse
I'm still a little unclear: is the danger to the eMMC simply from wiping/recovery with an ICS kernel or is it any wiping operations after having flashed the ICS kernel? That is to say, I had stock Android 4.0.3 LPY ROM and now I'm back on stock Android 2.3.5 KK1. Am I in danger after having used ICS, or am I safe flashing now that I'm back on GB?
vhanna said:
I'm still a little unclear: is the danger to the eMMC simply from wiping/recovery with an ICS kernel or is it any wiping operations after having flashed the ICS kernel? That is to say, I had stock Android 4.0.3 LPY ROM and now I'm back on stock Android 2.3.5 KK1. Am I in danger after having used ICS, or am I safe flashing now that I'm back on GB?
Click to expand...
Click to collapse
No man, you are clear !
Wipe as many as you want !
http://goo.gl/V8aQb
another victim of emmc bug on LP9...
vhanna said:
I'm still a little unclear: is the danger to the eMMC simply from wiping/recovery with an ICS kernel or is it any wiping operations after having flashed the ICS kernel? That is to say, I had stock Android 4.0.3 LPY ROM and now I'm back on stock Android 2.3.5 KK1. Am I in danger after having used ICS, or am I safe flashing now that I'm back on GB?
Click to expand...
Click to collapse
Once you're back on GB or a safe ICS kernel, you're safe. If you experience problems after returning to GB it's because the damage was already done before reverting and it's already too late.
I mean is there any safe ICS kernels out there to use with LPF or LP9?
daraj said:
I mean is there any safe ICS kernels out there to use with LPF or LP9?
Click to expand...
Click to collapse
Not yet. Hopefully, our kernel Devs will deliver us something to work with soon.
daraj said:
I mean is there any safe ICS kernels out there to use with LPF or LP9?
Click to expand...
Click to collapse
Not yet. Well - DAFUQ is safe but it has serious compatibility problems. I'll hopefully fix those this weekend.
Entropy512 said:
Not yet. Well - DAFUQ is safe but it has serious compatibility problems. I'll hopefully fix those this weekend.
Click to expand...
Click to collapse
Great That could be a temporary solution
***This is not for devices that have already been bricked. It applies to only those people who have inadvertantly flashed one of the 'Unsafe' 4.04 ROMs and wish to change ROMs or restore back their nandroid backup.***
Hi All,
Considering that a lot of gentry is unawares of how to go back to their nandroid back ups from the 'unsafe' 4.04 Stock Builds and are afraid to flash kernels fearing that their beloved may develop cataract, get pimples or maybe pass way (god rest their souls..) , below is the most foolproof, noob friendly way of going back to stock set up while circumventing the dreaded 'emmc_cap_erase' bug...
- Go to Intratech's thread of all stock firmwares in Original Development section.
- Download Stock KL1 <http://hotfile.com/dl/146342883/c1bdbd7/I9100XWKL1_I9100ODDKL1_INU.zip.html> (because it is no wipe) + Odin tool (you did flash LPM/LPO/LQ5/LQ6, exactly the same way!!!)
- Switch off your phone, restart in Download mode (Volume Down+Home+Power), you will see a flash page, choose to continue.
- Fire up Odin, confirm that the phone is connected, Click on 'PDA' and add KL1, flash KL1.
- First reboot, phone will bootloop.
- Switch off, restart in stock recovery (Volume Up + Home + Power)
- Do a factory reset.
That is it!!! Your beloved has been saved from Satanic evil...! Now install your favorite GB/ 4.03 ROM/ CM9 or CM9 derivatives or restore a nandroid back up (if you had any... )
I hope this helps...
Learn and Share.. That is what XDA is about..
kranti2064 said:
Now since you read the entire post, press the 'Thanks' button, will you?
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
NO,
Don't be a thanks whore
Sent from my GT-I9100 running CM10
MemoryController said:
NO,
Don't be a thanks whore
Sent from my GT-I9100 running CM10
Click to expand...
Click to collapse
Stop being a scrooge mate..!!
Epic fail.. !!!
Sent from my GT-I9100 using Tapatalk 2
It sounded more like Gnote situation over here lol
Sent from my GT-I9100 using xda premium
what?
kranti2064 said:
below is the most foolproof, noob friendly way of going back to stock set up while circumventing the dreaded 'emmc_cap_erase' bug...
Click to expand...
Click to collapse
What?. Come that again?. Why you dont tell us step by step, what exactly what you did?. Because I TRIED (and a lot of other more complex things) that before I have to CHANGE my MB...
cpl.Bower said:
What?. Come that again?. Why you dont tell us step by step, what exactly what you did?. Because I TRIED (and a lot of other more complex things) that before I have to CHANGE my MB...
Click to expand...
Click to collapse
this is not a fix. this is a method to prevent brick. if you brickef it allready like I did, only PBA main replacement solves it.
Sent from my reborn i9100
Thank you for the feedback. Have amended OP as advised..
Sent from my GT-I9100 using Tapatalk 2
cpl.Bower said:
What?. Come that again?. Why you dont tell us step by step, what exactly what you did?. Because I TRIED (and a lot of other more complex things) that before I have to CHANGE my MB...
Click to expand...
Click to collapse
I did exactly as stated in OP.. I just happened to read around before flashing ROMs ( ***noob flashaholics*** ).. And hence, even though I have an unsafe chip and after flashing LQ5, LPM and going back to VR 3.0 and now running LPO.. I write this from my phone..
Learn and Share.. That is what XDA is about..
Can someone confirm that this works when going from LPO backwars? Also why should I flash from ICS rom to GB rom? Isn't that bad for the phone? I wanna go to some stock rom from where I can flash the jelly bean preview
Vilzu said:
Can someone confirm that this works when going from LPO backwars? Also why should I flash from ICS rom to GB rom? Isn't that bad for the phone? I wanna go to some stock rom from where I can flash the jelly bean preview
Click to expand...
Click to collapse
Yes mate, it works for LPO as well. You should flash a GB rom so that the unsafe kernel kernel is overwritten by a GB kernel which is completely safe before the phone or you attempt a wipe.
No it is not bad for your phone. In fact trying anthing else can be fatal for your phone.
Once you have taken the steps I have provided, you can flash the JB preview from CWM from the GB ROM.
Learn and Share.. That is what XDA is about..
I got a simpler way
flash siyah via heimdall/odin,
boot into recovery,
???
Profit
Sent from my GT-I9100 running CM10
MemoryController said:
I got a simpler way
flash siyah via heimdall/odin,
boot into recovery,
???
Profit
Sent from my GT-I9100 running CM10
Click to expand...
Click to collapse
Indeed, now can you please explain step by step how to get rid of the triangle and restore the binary counter to 0. (with appropriate links).
I'll add it to the OP.
Learn and Share.. That is what XDA is about..
Use triangle away or a usb jig on an older bootloader.
Sent from my GT-I9100 running CM10
MemoryController said:
Use triangle away or a usb jig on an older bootloader.
Sent from my GT-I9100 running CM10
Click to expand...
Click to collapse
Give me a step by step guide and I'll add to the OP. Else stop trolling the thread trying to portray a higher level of intellect or smartassness..
Learn and Share.. That is what XDA is about..
Use search
Sent from my GT-I9100 running CM10
kranti2064 said:
Give me a step by step guide and I'll add to the OP. Else stop trolling the thread trying to portray a higher level of intellect or smartassness..
Learn and Share.. That is what XDA is about..
Click to expand...
Click to collapse
He's actually right. Flash siyah or another custom kernel and you're good to go. Looks like the latest speedmod is safe as well.
To reset the counter and get rid of the triangle, use chainfire's app.
Or flash an older GB boot loader from Intratech's thread and use a jig.
Sent from my GT-I9100 using Tapatalk 2
just one more thing which KL1 should I flash? The one which is based of of the original package or some indian version? also the thread where you linked to only has megaupload links :/
mrcreativity said:
He's actually right....... from Intratech's thread and use a jig.
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
As I said, give me a step by step method and I will add it to the OP. Or else forever maintain your peace.
My method is simple, requires no additional tinkering apart from the steps I have mentioned. Not all people like Siyah (3.1 brick incident) or want to go through the hassle of running a kernel cleaning script.
I want to keep it simple... You are free to open an another thread with the steps you feel are simplest.. You could call it "Simpler than Simplest...."
Sent from my GT-I9100 using Tapatalk 2
Vilzu said:
just one more thing which KL1 should I flash? The one which is based of of the original package or some indian version? also the thread where you linked to only has megaupload links :/
Click to expand...
Click to collapse
Use the Indian version, it is a no wipe.. You can then flash your own country's firmware over it..
Well, the <samsung-updates.com> is down for the moment, it has faster links. I guess megaupload it is for the moment then..
kranti2064 said:
As I said, give me a step by step method and I will add it to the OP. Or else forever maintain your peace.
My method is simple, requires no additional tinkering apart from the steps I have mentioned. Not all people like Siyah (3.1 brick incident) or want to go through the hassle of running a kernel cleaning script.
I want to keep it simple... You are free to open an another thread with the steps you feel are simplest.. You could call it "Simpler than Simplest...."
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
To have an informative thread an OP should first learn how to search and read. People suggested that you should search for it, which everybody knows is the answer for almost everything. If you want to know how to remove the triangle and add them to your first post, you should do your research first instead of asking the guy to spoon feed you the solution. Using TraingleAway is a no brainer, just simply flash an ICS ROM, run the app, press whatever is needed to be pressed (of course you need to verify that the information about, if you have a triangle or how many binary counts you have etc is correct), let it reboot and the binary counter and triangle will be gone. Of course just saying that won't guarantee the success of every people using it. There are some instances that problems occur that i haven't put in my so called "guide" for triangle away. The only way is to read the original post of TraingleAway thread.
If you want to help people by answering their query is to acquire knowledge on how to do things etc. You can't do that if you won't try to search and understand the subject first. Spoon feeding is the last thing we, as members of this developer site, should do.
Anyway, i am not here to bash you or anything. Of course i appreciate this thread because it will help people who are unaware how to safely flash their phone if they are on the famous "brickable ROM/Kernel". I am just here to remind you that no matter who we/you are, everyone needs to do their research first rather than people just giving you all the answer to everything. After all, using TriangleAway is "RISKY (well, i haven't heard anyone bricking their phone yet with it)" according to its developer hence the need to read its thread first before posting a guide to your thread. Good luck to you and your thread and hope you understand what i am talking about.
Cheers
Sent from my GT-I9100 using xda premium
Guys i need your advice
i was on ics 4.0.4 recovery. do a wipe cache/partition..my phone freeze then shutdown..now i cant even turn it on....even doing recovery nothing.....just trying my luck if theres a way to revive this....thanks in advance!!!!!
richterbelmont said:
Guys i need your advice
i was on ics 4.0.4 recovery. do a wipe cache/partition..my phone freeze then shutdown..now i cant even turn it on....even doing recovery nothing.....just trying my luck if theres a way to revive this....thanks in advance!!!!!
Click to expand...
Click to collapse
Completely stock?
richterbelmont said:
Guys i need your advice
i was on ics 4.0.4 recovery. do a wipe cache/partition..my phone freeze then shutdown..now i cant even turn it on....even doing recovery nothing.....just trying my luck if theres a way to revive this....thanks in advance!!!!!
Click to expand...
Click to collapse
You bricked your device completely. Do you have warranty?
Sent from my GT-N7000 using XDA Premium App
PoisonWolf said:
Completely stock?
Click to expand...
Click to collapse
yes man..im on official ics 4.0.4 germany rom
Have you tried swapping batteries? Just trying to rule out a dead/faulty battery of sorts...
A brick from stock recovery.. Can you get hold of Entropy? This is a valuable info about the brick bug.. Sorry about the incident buddy..
please don't send your phone in for warranty until you've spoken to entropy!!
richterbelmont said:
yes man..im on official ics 4.0.4 germany rom
Click to expand...
Click to collapse
Not CF-Root, no CWM fakeflash with ROM Manager?
If it was in Samsung's own stock recovery ("3e" recovery), I want to put you in touch with a contact of mine at Samsung.
Could you PM me your email address please?
And can you go into very specific detail about what firmwares you have had installed on this device previously?
richterbelmont said:
yes man..im on official ics 4.0.4 germany rom
Click to expand...
Click to collapse
Get your motherboard replaced asap.
Sent from my GT-N7000 using XDA Premium App
sahilarora2003 said:
Get your motherboard replaced asap.
Sent from my GT-N7000 using XDA Premium App
Click to expand...
Click to collapse
ARE YOU KIDDING ME??? Seriously... If we ever want this nightmare to end, we need to get evidence of danger in stock recovery to engineers at Samsung (not their service centers... they're clueless... If it goes into a service center, it's a lost opportunity). Thank you very much for your attempts to sabotage those efforts.
sahilarora2003 said:
Get your motherboard replaced asap.
Sent from my GT-N7000 using XDA Premium App
Click to expand...
Click to collapse
We are trying to get info from this user. This brick is so valuable if indeed it was pure stock recovery and what we can get on this brick can benefit the whole note conmunity and other devices that have the brick bug.. we know he needs a mobo replacement but please DO NOT send the device to service asap..
richterbelmont said:
Guys i need your advice
i was on ics 4.0.4 recovery. do a wipe cache/partition..my phone freeze then shutdown..now i cant even turn it on....even doing recovery nothing.....just trying my luck if theres a way to revive this....thanks in advance!!!!!
Click to expand...
Click to collapse
Hope you can communicate with Entropy first before you decide to send your device.. He has a contact at Samsung..
i hope you can get in contact with entropy,, samsung will likely replace your unit with a brand new one.. we all love brand new things, don't we?
Unbelievable.... I never thought stock ICS 4.0.4 can brick our phone....
By the way to the OP... where you also using the stock kernel when you wiped partition /cache? or where you using a custom kernel?
*now this me think on the credibility of all stock ICS (including the latest 4.0.4) ones already... If the OP got hit by this hard brick bug (on stock 4.0.4 ICS, assuming he was using also the stock kernel that comes with it), how many more do you think will follow the OP's plight of hard bricking their phones...?
...and come to think 4.0.4 ICS is beginning to be released already in every region of the world..... this is quite an alarming news.....
What do you guys mean with stock recovery? You mean the one that you use to flash cwm to flash a rom in order to not overwrite some binary so you're phone doesn't lose warranty?
stock recovery is the recovery you have when you buy the phone or just after you flash a stock rom.
If it's a full stock and the wipe was done during automatic upgrade then samsung has to release a solution. But will they?? Entropy has been battling so much and still are people that rush in and say: "replace as fast as you can with a ss"...... unbelieveble.
I think there are more that had the same problem but or aren't users of the WWW or just didn't realise that it was the bug. I'm sure that there are a number of devices that were already repaired by some ss WITHOUT knowledge, just a swap of the mb, new flash and new phone !! That makes the customer happy but doesn't solve the problem.
Ok, it must be hard to be without a phone (i know) but if you are willing to sacrifice some time to solve a WORLDWIDE problem i'm pretty sure that you'll be considered a hero..... :laugh:
As i read here Entropy did already knows of this so just hang in there....
Wish a swift and good solution not just for you but for all....
beco
Follow Entropy that is best way.
Can you plz change title of thread?
it will be easy n better to find if it will
'Bricked not by emmc bug on pure stock ROM' or like something.
hunterhp said:
What do you guys mean with stock recovery? You mean the one that you use to flash cwm to flash a rom in order to not overwrite some binary so you're phone doesn't lose warranty?
Click to expand...
Click to collapse
Recovery is the system you get by pressing "vol up", power and menu at the same time at startup
Stock is the one that you get out of the box, looks like this:
http://www.hostingpics.net/viewer.php?id=867265stock.png
CWM is installed with custom roms and CFRoot, looks kis this:
http://rootgalaxynote.com/wp-content/uploads/2012/01/backup-cwm-rooted-galaxy-note-3-690x431.jpg
You know which one you used ?
We just have to wait for the OP to report back, if it is not a false alarm. I mean, he has only 3 posts, could be anything. I hope he was on stock, but it smells like a noob not following the instructions. Forgive me if I'm wrong. In any case:
DO NOT SEND THE DEVICE to the service centre before contacting Entropy!