Related
Hey, guys,
I'm talking about this thread http://forum.xda-developers.com/showthread.php?t=1633943
Are these issues resolved somehow? I'm sitting on ICS Stunner ROM and I'm afraid to do anything serious with my phone.
Shouldn't there be fixes when Samsung released official AOSP source of Notes' ICS?
Or am I missing something? I really want to do a completely clean install of some ROM, because my current ROM (the newest version of Stunner) works terribly, forcecloses, slugish, freezing all the time.
Can the behavior of my phone have something to do with the problem discussed in the thread I linked? (I don't understand anything in that thread )
Hi
The issues regarding superbrick arent completely resolved. But there are Kernels for ICS wich contain a workaround. And so far noone has reported bricking with them.
It seems like the official kernel source from sammy still contained that bug. But now it has been bypassed. Still noone is completely sure yet that they are 100% safewhen it comes to wiping etc.
There is also a workaround to repartition the data section effectively bypassing any damaged areas for anyone that has a brick and no warranty.
This of course reduces the data partitions size, and it's still pot luck as to how much damage would occur.
It's also a pretty tricky operation.
Sent from my GT-N7000 using xda premium
So if I want to install a stock ICS rom (the newly released one, not the old leak), I should dooo, what? Which is the safe kernel (the one with a workaround)?..
Sorry for stupid questions..
Probably worth flashing stock ics ROM, with a custom kernel that's safe. Probably best to do it in mobile Odin. Make sure you extract the firmware file and only select ROM partition, then separately point to kernel.
Sent from my GT-N7000 using xda premium
I think its better to be in Stock rom what we got and never do any experiment, instead of wasting time on it to get very little stuff with high risk.
even if some work around solution is there, its very hard to understand and not all will be doing that.
I totally agree. Wait for safe ics kernels or use modified Cm9's for now.
Sent from my GT-N7000 using xda premium
So just to be sure:
I use this ROM http://forum.xda-developers.com/showthread.php?t=1646088
And a kernel? You mentioned CM9 kernel. How do I get it? Can I find it in here http://get.cm/?device=n7000 (I mean is it somehwere in the .zip?)
Or are all those franco/abbyss kernels also considered relatively safe?
Thanks for your patience
No you cant use Cm9 kernels with stock rom. If you flash a stock rom you get a stock kernel included
What if I flash chainfires kernel first and the flash stock rom?
Cyrusas said:
What if I flash chainfires kernel first and the flash stock rom?
Click to expand...
Click to collapse
No, either use a GB kernel or use Franco's #3+, or SpeedMod K3-3, CF's ICS kernels are NOT safe.
Hi Guys,
I am a new user in the community as well i am a new owner of a galaxy note.I purchased it 3 days back,I have no knowledge about ANDROiD as i have been using NOKIA since last 7 years.
I have a very few simple questions on which i would like to take your EXPERT advice
1.I have updated the FIRMWARE to ICS now.Now after i have updated it i feel that the battery is draining too fast,Just wanted to know how to fix it.
2.Also i have heard that there is a bug in ICS which can brick the phone.How can i check if that bug is there in my Phone or not?
3.Also wanted to know as to how can i make sure that i get atleast 1.5 days from normal use
Please reply back guys as i am very eager to use this fone but when i see the battery backup i feel very disappointed
Please help
dilpreetpuri said:
Hi Guys,
I am a new user in the community as well i am a new owner of a galaxy note.I purchased it 3 days back,I have no knowledge about ANDROiD as i have been using NOKIA since last 7 years.
I have a very few simple questions on which i would like to take your EXPERT advice
1.I have updated the FIRMWARE to ICS now.Now after i have updated it i feel that the battery is draining too fast,Just wanted to know how to fix it.
2.Also i have heard that there is a bug in ICS which can brick the phone.How can i check if that bug is there in my Phone or not?
3.Also wanted to know as to how can i make sure that i get atleast 1.5 days from normal use
Please reply back guys as i am very eager to use this fone but when i see the battery backup i feel very disappointed
Please help
Click to expand...
Click to collapse
If you are running stock ICS(which I'm sure you are) you should assume that you are affected by the bug.
Refrain from doing factory reset using the STOCK/CWM recovery as this will trigger the bug even on STOCK recovery. If you have CWM do not do a NANDROID RESTORE.
If you are rooted i suggest flashing a safe custom kernel, a good one that I can
recommend for solid battery life and balanced performance is Speedmod k3-3 just look for it on the development section.
If you don't like custom kernels and prefer stock just do not do the ones I've mentioned above. If you really need to do a factory reset do it on Gingerbread.
Regarding the battery life, there are many factors to consider. First thing that you need to check if your phone is going into deep sleep. Download cpuspy on play store and report back here so we can help you.
HOLY CRAPPPPPP
Well i have already done the FACTORY RESET 2 times but now its working fine so far
So what should i do now?????????????????????????
Also i would like to know if i can switch back to gingerbread os using Skies software?????????????????
You cant use Kies but Id recommend using ODIN because its faster and safer.
Check out dr.ketans guide http://forum.xda-developers.com/showthread.php?t=1424997, the man is a genius.
His English isnt great, but essentially
Download ODIN
Download whichever stock rom you want (GB)
Set phone to download mode
Connect to Odin
and flash.
His instructions are a lot more detailed (maybe to much so). But if you do this, the dangerous kernel will be gone and youll be safe.
I know where you are coming from being fairly new to the android scene. Have been in it now for about six months and i would consider myself fairly literate. From what you were saying you updated your phone to the official ics version for your phone. Well... The first thing you need to do my friend is read, read, and read some more. Alot of what i know and have learned has been from researching these forums and the web. Rootgalaxynote.com is pretty good for noobs as it usually has videos showing you how to do things step by step but you should also read some of the faq's about rooting and flashing on this site. If i were in your shoes the first thing that i would do would be the following;
1.) root the device using Dr. Keetans method on this site. If you havent done this it wouuld be a good place to egt started. His method will not trigger your phones counter.
2.) I would revert the phone back to its earlier version which would be gingerbread. You can do this by looking in the stock gingerbread roms section under android development on this site. Our fellow senior members have made it fairly easy to find and after reading you should have a pretty good idea of what to do.
3.) Install a kernel that is safe for ics roms such as franco kernel or abyssnote kernel. This should be fairly easy for you to do just make sure you do tue steps exactly as they describe or else you will mess the phone up.
4.) After that you can pick out a custom ics rom which if you are looking for optimal battery consumption this would be the best way to go about it as official ics rom consumes a substantial amount more battery than the sleak, lean more refined custom roms out there. Just be carefull what you choose as some are full of bugs and features not working.
The main thing here is to cover alot of ground and do your homework. Research is key and you always want to stick with sites like xda and a few others. Xda may not be the most user friendly site out there but it contains a wealth of information and iw where the best of the best come together. Hope this helps my friend.
dilpreetpuri said:
HOLY CRAPPPPPP
Well i have already done the FACTORY RESET 2 times but now its working fine so far
So what should i do now?????????????????????????
Click to expand...
Click to collapse
If you can still run it fine, then you're good. But from now on refrain from doing things on the recovery until you're on a safe kernel. Some users reported that they were able to do a factory reset to the nth time before encountering the brick. Meaning you can factory reset 999 times and get away with it and on the 1000th time, brick ur device seriously god knows when it will happen.
Just stay away from CWM or Stock recovery for now if you don't know what you're doing just to be safe.
P.S. ICS is nothing to be scared of if you know what you're doing. Do a little research about the hardbrick bug good place
to start reading about it is this POST
Well i completely agree with you mate and i need to do a lot of homework before i make any change.However since i am very new to the terminology used in ANDROID so would like to ask you if there is any website which can explain me a lil bit about these terminologies so that i know what everbody is talking about or is it that i should simply go through the forums and then join all the bits and pieces to get an idea about the terms used.
Also i would like to ask you that "ODIN" is it like another software which is used to flash the FIRMWARE
dilpreetpuri said:
Well i completely agree with you mate and i need to do a lot of homework before i make any change.However since i am very new to the terminology used in ANDROID so would like to ask you if there is any website which can explain me a lil bit about these terminologies so that i know what everbody is talking about or is it that i should simply go through the forums and then join all the bits and pieces to get an idea about the terms used.
Also i would like to ask you that "ODIN" is it like another software which is used to flash the FIRMWARE
Click to expand...
Click to collapse
hmm. website... ? well you can start on this website http://developer.android.com/about/index.html and don't forget our ever loved website.. (XDA-DEV)...
Just by snooping, hanging around, munch and digest all you can and soon you'll be able to pick some neat tricks in learning android terminologies in no time at all.
ODIN (PC /Mobile) is a very neat indispensable tool for custom room makers and flashers... With this tool you can always at your disposal.. whilst jump from one custom rom to another, which ever your choice or liking. Changing ROMS is akin to Flashing.. so if you flash a ROM, you are changing your current ROM to whatever ROM you would like to have it installed on your phone.
Every custom ROM has its highlights and lowlights... pick what suits you best and your good to go after. Flashing ROMs with Gingerbread support (if your still in stock GB), assures you no brick at all... Now on the other hand, if your already in ICS(Stock) and would like to flash custom roms with iCS support.. then I do warn you to be wary of it. A lot of people have fallen and have been bitten by the hardbrick bug... Just always be extra careful in doing it.
Cheers bud!
First of all i really thank everyone for their help considering that i am a noob when it comes to android
2ndly i am alos getting an impression that Gingerbread is a better bet as of now till there is a permanent fix for the Bug and secondly i am getting an impression that GB was much better when it comes to the battery backup
Correct me if i am wrong
Alos a clarification
Stock rom means the firmware from SAMSUNG?Am i correct?
Custom rom means that it has been tweaked to avoid any known issues?Am i correct?
Also if i change from custom to stock riom does that hamper the warrenty or not?
dilpreetpuri said:
First of all i really thank everyone for their help considering that i am a noob when it comes to android
2ndly i am alos getting an impression that Gingerbread is a better bet as of now till there is a permanent fix for the Bug and secondly i am getting an impression that GB was much better when it comes to the battery backup
Correct me if i am wrong
Click to expand...
Click to collapse
Right
dilpreetpuri said:
Alos a clarification
Stock rom means the firmware from SAMSUNG?Am i correct?
Click to expand...
Click to collapse
Correct
dilpreetpuri said:
Custom rom means that it has been tweaked to avoid any known issues?Am i correct?
Click to expand...
Click to collapse
Correct
dilpreetpuri said:
Also if i change from custom to stock riom does that hamper the warrenty or not?
Click to expand...
Click to collapse
Yes! Flash it back to Stock Rom and unroot it. You should be good to go.
You should not worry too much about the bricking bug. If you stay on stock rom and your phone gets bricked you are covered by the warranty. It is not your fault that the phone has that problem.
I also recommend that you ask some friend that has experience to help if you want to flash/root/install custom rom, given that you have little experience with android.
i have just checked in and found this link "Root Your Phone"
This means he is going back to a particular version
Right?
http://www.youtube.com/watch?v=EV3PLcYbAnU
Dilpreet,
U remind me of myself 2 years back when I was equally inquisitive, enthusiastic but lacking knowledge...
First of all... There is no problem whatsoever if you remain on stock(yes u r right official) Samsung ics provided you don't do factory reset ahead.
2. U need to familiarize yourself with android terminology such as rooting, flashing custom (yes again u r right tweaked) roms, recovery mode, download mode, full wipe, Odin, directly/not directly root able roms etc etc... I am not trying to psyche you out but just giving a word of caution. Unless you know all of these terminologies well (you will get lot of reading on xda on each of this) , PLEASE DO NOT ATTEMPT ANYTHING. By anything I mean even reverting to GB. U must have updated from GB to iCS OTA (over the air) that is on device itself but this rversal won't be easy unless u fully know what u r doing... so first familiarize urself and then get into it.
3. As regards battery life on stock ics , you can use app named juice defender (available on play store) it has lot of options for battery saving. Besides check if GPS and wifi options are not switched on when not in use... some apps are battery hoggers. Check battery usage under settings ---- battery to see how its doing.
4. There are few safe ics kernels available like what has been told u before by some people in this thread... I would strongly suggest Cm9 or any cm9 based rom like asylum (btw Cm stands for cyanogenmod ) which are smooth and safe & yes extremely battery efficient too.
5. Lastly, I will pm you one apk file which will help you know whether your phone has a brick bug or not... do uninstall that application after you check it. For installing any external app (apk file) you need to go in settings ---- security --- and tick unknown sources
PS: Do click Thanks if I have been of any help mate
Sent from my GT-N7000 using xda app-developers app
Nopes... rooting is gaining administrator rights over your phone. In simple terms , being able to access system folder on your phone... Beware, rooting voids warranty.. Please refer Dr. ketan's guide on rooting note on other thread... That's best
Sent from my GT-N7000 using xda app-developers app
". Lastly, I will pm you one apk file which will help you know whether your phone has a brick bug or not... do uninstall that application after you check it. For installing any external app (apk file) you need to go in settings ---- security --- and tick unknown sources:"
Thanks for the info mate
And i have already checked the article which helps you to check if your handset is affected or not and what i could understand was that we just have to install the application and then run the application and will generate a result
But what after that?
I mean how ill i come to know which files to look for which will tell us if its affected or not
I am not aware as to which all files to look for
Please help me
It will throw up the result after checking.. u need not look for anything... it will tell u if ur phone is prone to brick bug.. check it urself. Have sent u the apk file already through pm (personal message).
This will just tell you if you are really prone to this bug, nothing beyond that. If you are then you have three options:
1. Stick to stock ics rom but don't do full wipe again
2. Revert to stock GB through Odin
3. Switch to safe ics kernel (and enjoy lovely ics experience without boring Samsung touchwiz)
For the last you will have to root your phone for remaining, rooting not required.
PS: Please press Thanks button if I have helped you anyway
Sent using xda forum app
Device: SGN N7000
ROM: Asylum V.15
dilpreetpuri said:
HOLY CRAPPPPPP
Well i have already done the FACTORY RESET 2 times but now its working fine so far
So what should i do now?????????????????????????
Click to expand...
Click to collapse
What ROM are you on exactly??I've heard this brick issue is solved in the ROMS released last month.With CF-root 5.6 it's even safe to wipe.But no one dares to try apparently so it needs confirmation.
I am on 4.0.3
Any help guys??????????????????????
dilpreetpuri said:
HOLY CRAPPPPPP
Well i have already done the FACTORY RESET 2 times but now its working fine so far
So what should i do now?????????????????????????
Click to expand...
Click to collapse
Lol...I know just how you feel, searching for answers!
Greetings.
I am the first time user planning to flash my 16GB Galaxy Note GT-N7000 phone (from Asia).
Previously I have been hard bricked my phone (MoBo damaged) due to improper / incorrect kernel flashing ROM. Already sent to Service Centre for replacement of MoBo under warranty. Now it's in the progress and I should be expecting it back in the couples of days.
Anyhow, I still prefer third party ROMs with awesome GUI. I plan to "try" flashing again when my phone is back.
This time, I would take more caution while doing this stuff. My request is, for first time new user like me, which ROM is recommended (plus suitable Kernel type which is more power saving and low temperature operating)?
I mean here maybe pointing more to what I so call close to "Samsung Custom ROM". I think that should be more convenient and safer for me rather than trying completely on new AOSP type for the first time. This is only my own opinion
What say you? Again, thanks for your recommendation. Have a nice day
i recommend you first try to read the rules of posting mate...requesting a move to the Q & A section...
ps...3 posts and already in the development section? hmm...
Moved To Q&A
This is in no way development, please post in the correct section. Anybody wondering the reason why this user can post in the dev section is due to the amount of time he has been a member. We thought a user with a long membership would be aware of such a basic rule, guess not
cleanote seems what you asking for. It's a clean rom based on stock, but very smooth
Honestly,i think every rom the Dev created are great.Just read through the OP of the each rom to see what rom is fit your style ( like you go to mall looking for shoe is fit you) and try it .Wish you luck...:victory:
Yeah, right. read through the OP and intructions a few times to be sure first.
Dudes, sorry for wrong posting in other section. I've been quite long time never browsing through this forum. That's why not familiar with the rules.
As my friend recommended me to search from XDA which is one of the best ROMs forum, here I am back again
BTW, what does OP stand for?
I have viewed through few threads in ROM dev section. Honestly, I'm still digesting the contents and descriptions...
Also, I require Chinese input or viewing too (forgot to state).
So far, I have been read through Criskelo ROMs (I like its GUI i.e. close to GS3 too), Fusion ROMs, CM9 ROMs etc. Not sure if these ROMs may fulfill what I've been requested?? Safe Kernels (this really worries me from what I've been experienced before----hardbricked! scare!)?
Thanks for your comment.
I would recommend CRASH rom...you can request the DEV for your Chinese stuff...its touchwizz base...safe kernel and very smooth with NO BUGS at all..:good:
For the awesome user interface I would say Paranoid Android (CM9, not CM10).
For the chinese stuff, I think Criskelo's rom supports it"• ADD Chinese Keyboard (on request)"
I'm not really sure if that's what you're asking for.
I think PA also supports chinese.
I don't think there are "new users" roms. Just read carefully the instructions and you should be fine.
perri.etb said:
For the awesome user interface I would say Paranoid Android (CM9, not CM10).
For the chinese stuff, I think Criskelo's rom supports it"• ADD Chinese Keyboard (on request)"
I'm not really sure if that's what you're asking for.
I think PA also supports chinese.
I don't think there are "new users" roms. Just read carefully the instructions and you should be fine.
Click to expand...
Click to collapse
Hi, let's say if I would like to flash Criskelo ROM, which safe Kernel shall I choose to use?
Speedmod, AbyssNote, GL Notecore (never heard, is it safe kernel)??
I just got back my phone with default stock GingerBread 2.3.6 (correction) ROM, without any rooting after repairing
Make sure you read the details on Rooting and flashing your phone.
NEVER WIPE / RESET on ICS Stock Kernels/ ROMS..
There's a lot of info in Dr. K's Stock ROM thread..
As for what ROM to use - I'd say CleaNote is probably what you're after, very close to stock with bloat removed. Bundled with the Dev's own Kernel...
Anyway, Good luck and remember to read, read and read again before you start messing around and bricking your device again..
CJSlim79 said:
Make sure you read the details on Rooting and flashing your phone.
NEVER WIPE / RESET on ICS Stock Kernels/ ROMS..
There's a lot of info in Dr. K's Stock ROM thread..
As for what ROM to use - I'd say CleaNote is probably what you're after, very close to stock with bloat removed. Bundled with the Dev's own Kernel...
Anyway, Good luck and remember to read, read and read again before you start messing around and bricking your device again..
Click to expand...
Click to collapse
Thanks for your advice. Actually I'm on stock GB 2.3.6 ROM now.
Should I flash any safe kernel before installing CleaNote ROM (as recommended)? Root required?
Also, what is "bloat removed"?
symbian6600 said:
Thanks for your advice. Actually I'm on stock GB 2.3.6 ROM now.
Should I flash any safe kernel before installing CleaNote ROM (as recommended)? Root required?
Also, what is "bloat removed"?
Click to expand...
Click to collapse
First your anwwer to what OP stands for it means "Original Post" .
Secondly, as you are on stock GB, you are safe from the Brickbug & can very well flash as you like, but keep in mind two things:
1- Read, re read & follow to the point the ROM developers installation instruction.
2- Do not Wipe / factory reset from any unsafe kernel. Only wipe from a safe kernel, i.e., GB & in case of ICS those with their MMC_CAP_ERASE command disabled like Speedmod K3-11, GL Notecore, etc.
Pls. read the stick section for additional information
By the way I would recommend Kingdroid Notemania Version 5.1.1 (With S3 Touchwiz UI Mods) with Speedmod Kernel for ICS K3-11 (Good performance & better battery)
Yin-Yang said:
First your anwwer to what OP stands for it means "Original Post" .
Secondly, as you are on stock GB, you are safe from the Brickbug & can very well flash as you like, but keep in mind two things:
1- Read, re read & follow to the point the ROM developers installation instruction.
2- Do not Wipe / factory reset from any unsafe kernel. Only wipe from a safe kernel, i.e., GB & in case of ICS those with their MMC_CAP_ERASE command disabled like Speedmod K3-11, GL Notecore, etc.
Pls. read the stick section for additional information
By the way I would recommend Kingdroid Notemania Version 5.1.1 (With S3 Touchwiz UI Mods) with Speedmod Kernel for ICS K3-11 (Good performance & better battery)
Click to expand...
Click to collapse
Hi, thanks for your reply.
Noted your ROM & kernel recommendation. I've downloaded Criskelo v10.1 ROM previously (few hours downloading due to my slow internet connection). Thus, I plan to try this ROM first.
Actually, should I install any safer kernel even if this ROM contains it?
And, the correct steps for installation are ----> 1. root first 2. flash any so called CF_rooted_CWM_xxxx for GB ROM? 3. full wipe 4. flash this ROM in recovery mode?
actually you really should read, a LOT.
Sent from my GT-P1010 using xda app-developers app
praetorius said:
actually you really should read, a LOT.
Sent from my GT-P1010 using xda app-developers app
Click to expand...
Click to collapse
Bro, yup, you are right.
I still need to read A LOT. Still digesting those relevant threads (although some are not quite understanding...)
Working hard on them to make my first custom ROM flashing successfully
symbian6600 said:
Hi, thanks for your reply.
Noted your ROM & kernel recommendation. I've downloaded Criskelo v10.1 ROM previously (few hours downloading due to my slow internet connection). Thus, I plan to try this ROM first.
Actually, should I install any safer kernel even if this ROM contains it?
And, the correct steps for installation are ----> 1. root first 2. flash any so called CF_rooted_CWM_xxxx for GB ROM? 3. full wipe 4. flash this ROM in recovery mode?
Click to expand...
Click to collapse
I've downgraded to stock GB ROM 2.3.5 (XXKK1 in my region). Then, I used InitialCFRootFlasher (CF-Root-SGN_ZS_MUL_KK1-v5.0-CWM5) to root + CWM as guided by owner of the OP. Would both different XX and ZS kernel types affect anything in term of phone functionality?
Finally, I found SuperUser and CWM in the menu as per attached pictures. Rooted, right?
What would be my next step to flash Criskelo v10.1 ROM? Thanks.
Your next step should have been second after rooting gb, back efs up, see my profike page, statistics and then backup thread I started
Sent from my GT-N7000 using Tapatalk 2
2012-09-11: update. So far 12 xda users reported a bricked gt8.9. Don't join them...
2012-09-08: update. I will be out of town this weekend. I will keep the top post summarized once per day (if there is news)
Current knowledge is: (note: knowledge on this issue is still evolving and may become more accurate in future)
there is a serious bug in a hardware EMMC chip (or its driver) used in many Samsung devices
in GingerBread / HC this bug was not triggered
in its ICS kernels Samsung has used a feature to wipe EMMC in a way that triggers the bug in the chip
when xda developers used Samsung ICS kernel sources to continue work with (e.g. as kernel for the recovery - which has separate kernel from the ROM itself), they pulled the issue into their work
this has caused many bricks on many many different Samsung devices.
gt8.9 tab's CWM 6.0.1.2 includes this ICS kernel, and is dangerous if used to wipe /system or any other wipe (theoretically, that includes nandroid restore)
gt8.9 earlier CWM are believed to be safe (5.1.2.6, 5.5.0.4, 6.0.0.8, 6.0.0.8_alternate)
potentially, even update-binary inside a flashable .zip can be dangerous: IF it includes a specific (ext4) module from faulty ICS kernel, and IF the updater-script does a format(). So far there are no reports of such so far on the gt8.9
potentially, the same issue can be triggered from the kernel in the ICS ROM (although less risky, as that kernel is normally never used to wipe the boot or system partition). Nobody has reported issues after doing a "factory reset" from within Samsung p7310 stock ICS (USA region). We don't know if the ICS kernel inside that ROM is dangerous. Still, you are (till further notice) adviced not to use that feature inside any ICS rom. If you do, report here!
2012-09-07: v1 (modified)
Still more people are reporting bricking their device, after using CWM 6.0.1.2, even though it's already known 24-48 hours that this recovery can lead to this error.
I will link some threads in a follow up where the issue is discussed. Still, I recommend to try focus the discussion to just 1 thread... It will be easier on us all.
Proposal
- I propose to bump this thread hourly or so, for a few days at least, so that everybody has a chance to see it.
- There are many threads that discuss this issue. Try to keep the discussion a little focussed, don't continue posting in 6-7 different threads. Use this one
- If you see this disappearing from page 1 in General Forum, just reply with either:
* good idea, keep bumping
* stupid, stop it already
- If you heard of this issue here first, hit thanks
Thanks
Links
CWM 6.0.1.2 was made available in the CM9 thread (dev forum) around Sep 4.
By Sep 5 the first reports of bricked devices were coming in. The CM9 thread, starting from post 1066 (link, quote below) has been all about that for several pages. If you have found something really useful, reply on that dev thread. Do not spam it though.
kallt_kaffe said:
FYI, I might have bricked my P7310 so development is paused for now. Was flashing a CM10 build yesterday that I was experimenting with when it got stuck at "Formatting /cache" and after a while I did a long press on power thinking it would recover from it.
However I'm now stuck with black screen and it identifies itself as APX in Device Manager.
(...)
Click to expand...
Click to collapse
If you want to discuss in general, mention you have the same issue, ask for updates, etc, just reply here
other threads started for same issue. just for reference...
http://forum.xda-developers.com/showthread.php?p=31177035
http://forum.xda-developers.com/showthread.php?p=31158609
http://forum.xda-developers.com/showthread.php?p=31238668
http://forum.xda-developers.com/showthread.php?p=31172928
http://forum.xda-developers.com/showthread.php?t=1875756
Reserved
Sent from my HTC Desire using xda app-developers app
I hope those with the problem get a fix soon, i wouldnt be able to sleep if that happended to me
Sorry and up for this thread to warn others
Sent from my GT-P7300 using xda app-developers app
Im not really sure what makes this bugs happen..
But this issues is not new for me in galaxyNOTE gt n7000 and Sgs2 I9100 we call this as EMMC superbrick..
It happen in ICS kernel stock if you operates some EMMC_CAP_ERASE in kernel such as wiping your data or system.. Format.. Or deleting large file in recovery operation or factory reset in EMMC with firmware revision 0x19(firmware of this chip)..
It cannot recover with regular utility like JTAG coz This superbrick makes EMMC faulty in /data partition or /system partition blocks..
If you go to Samsung Service Centre.. Your device should be on mainboard replacement..
Sorry for my english.. You could use this app for testing your emmc has a bug or not..
If you had the emmc bug.. Dont use any recovery from ICS sources until someone with expert knowledge confirm that everything is fine..
Please read this thread for complete issues and discuss..from recognized developer entropy512
http://forum.xda-developers.com/showthread.php?t=1633938
I think it not about cwm version but the kernel is..
THANKS for makes this
Ups seems the i got the bug :-/
Sent from my GT-P7300 using xda app-developers app
I too got the bug and CWM 6.0.0.8 but my tablet will stay with AOKP for the time being until the dust settles.
Could somebody tell me what is the latest safest CWM to use for flashing KK's CM10 preview ROM.
Bump.
Cwm 5.1.2.6, 5.5.0.4 and 6.0.0.8 have all been around long enough to conclude that they are safe (in terms of this emmc bug)
You guys have a twrp?
Sent from my SGH-I727 using xda premium
Well, crap on a cracker...
Okay, so after reading the dumbed down facts about the issue at hand, it would seem that the latest CWM is not completely at fault for bricking devices. This most likely happened to users who were already on ICS and who already had a kernel that will allow the EMMC_CAP_ERASE to execute over a chip incapable of handling it.
The reports of using the latest CWM and successfully updating to ICS experimental builds without bricking most likely came from people going from stock Honeycomb to ICS?
Any of this true?
de3pkeeper said:
Well, crap on a cracker...
Okay, so after reading the dumbed down facts about the issue at hand, it would seem that the latest CWM is not completely at fault for bricking devices. This most likely happened to users who were already on ICS and who already had a kernel that will allow the EMMC_CAP_ERASE to execute over a chip incapable of handling it.
The reports of using the latest CWM and successfully updating to ICS experimental builds without bricking most likely came from people going from stock Honeycomb to ICS?
Any of this true?
Click to expand...
Click to collapse
Yes... You got the point..
strange.
What I understood (not necessarily correct) - simplified and without pointing fingers
the fault is likely in the kernel that is in that recovery 6.0.1.2.
there is another kernel, for the "Android OS", and it could hypothetically contain the same bug, but noone has found any ROM kernel to have the bug.
some developer tried to integrate a (Samsung?) ICS kernel (as released in the opensource for the ROM) in the CWM kernel -
some other developer copied that first developer's work and compiled it for the 8.9 tab
lots of bricked tabs.
So that's not correct? I've been reading about this all day, but I could have missed something in the last few hours.
de3pkeeper said:
The reports of using the latest CWM and successfully updating to ICS experimental builds without bricking most likely came from people going from stock Honeycomb to ICS?
Click to expand...
Click to collapse
I think kallt_kaffe said he flashed at least 10 ROMs using 6.0.1.2 before it failed on him...
Let me look if I can find that back.
orlandoxpolice said:
You guys have a twrp?
Click to expand...
Click to collapse
I've read about that recovery on the 10.1 forums, and on the sub-forum for Galaxy Tab 8.9 SGH-i957 (LTE, 4g version).
But never seen it for the P7300 and P7310.
fred_be9300 said:
I think kallt_kaffe said he flashed at least 10 ROMs using 6.0.1.2 before it failed on him...
Let me look if I can find that back.
Click to expand...
Click to collapse
First.. This bug it doesnt depends how many times you use.. Its random.. Maybe just once or twice or ten times when you wipe..
Second..hardbrick and superbrick is different..superbrick cannot recover with jtag because The chip is broken..
I hope this issue not happen to our tab..we need some testing and investigation..but who can do that?
I guess all samsung device with that kind of type EMMC chipsg is risky when in ICS..
this bug existed for the skyrocket as well as soon as ICS was released, it never existed with gingerbread. seemed completely random as well.
One dumb question: how about if you have already installed ICS kernel. By using CWM 6.0.0.8 or version below and do restore, wipe, etc, will it also brick the tab? Could someone confirm this if it is safe? Or has experience with lower CWM and survive the brick bug? Thanks
nexus_g said:
One dumb question: how about if you have already installed ICS kernel. By using CWM 6.0.0.8 or version below and do restore, wipe, etc, will it also brick the tab? Could someone confirm this if it is safe? Or has experience with lower CWM and survive the brick bug? Thanks
Click to expand...
Click to collapse
All indications are that CWM 6.0.0.8 is 'safe'. The problems appeared to start with 6.0.1.2.
Bump... Just hoping no others get brick from known issue
Hi everyone,
I know for many people, it is surprising what is SAFE KERNEL. When we go to any download page of a custom ROM, we will have a warning "Make sure you are on safe kernel".
Well, the first thing let me tell you about kernel. Just like for PCs we have BIOS which will be a small program which will run during the booting of machine, similarly, we have Kernels for Android.
Almost all the phones comes with a device specific kernels. They are usually capable of flashing a official ROM or to reset to your device. This is not safe kernel because, if you try to flash any custom ROM or any MODs you will brick your phone(your phone is completely dead and i really mean it).
ClockWorkModRecovery, Phillz are some of the kernels which has been developed by various developers. These kernels are safe kernels.
When you have your official kernel, you can copy a zip file of ClockWorkMod or Phillz (you can search XDA for this) into sdcard, goto recovery mode and select update via zip file. On doing this, your BIOS program gets changed, which means a custom kernel will get installed. After you do this, you are free to play around with any custom ROMs.
This I have learnt over time and hence thought of sharing the info with newbies.
Kernel = BIOS?
ClockWorkMod is a kernel?
Kernels are *usually* capable of flashing or resetting?
Pray tell me, when was the last time you had visited planet Earth?
Sharing is caring?
#BetterNot
@OP. Don't worry about some strange posts here.
The guys are too fixated on technology.
Transcendently you are absolutly right. And kernels are for noobs.
Just use your parapsychology and beam them away. :silly:
vinaybedre said:
Hi everyone,
I know for many people, it is surprising what is SAFE KERNEL. When we go to any download page of a custom ROM, we will have a warning "Make sure you are on safe kernel".
Well, the first thing let me tell you about kernel. Just like for PCs we have BIOS which will be a small program which will run during the booting of machine, similarly, we have Kernels for Android.
Almost all the phones comes with a device specific kernels. They are usually capable of flashing a official ROM or to reset to your device. This is not safe kernel because, if you try to flash any custom ROM or any MODs you will brick your phone(your phone is completely dead and i really mean it).
ClockWorkModRecovery, Phillz are some of the kernels which has been developed by various developers. These kernels are safe kernels.
When you have your official kernel, you can copy a zip file of ClockWorkMod or Phillz (you can search XDA for this) into sdcard, goto recovery mode and select update via zip file. On doing this, your BIOS program gets changed, which means a custom kernel will get installed. After you do this, you are free to play around with any custom ROMs.
This I have learnt over time and hence thought of sharing the info with newbies.
Click to expand...
Click to collapse
Actually, every operation system have a kernel, even on computers...
I don't know whether to trust you or the more experienced people. But Ill definitely not go with you. Seriously clockworkmod is a recovery people not a kernel. You've just entered xda last month and decided to teach the more experienced ones here about safe kernels. Next time before creating threads, make sure you get your facts right before being a bad teacher
This should be closed mods...?
Sent from my GT-N7000 using xda premium
SpyderTracks said:
This should be closed mods...?
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Deleted maybe? Since if they close it people can still open and see the thread
SpyderTracks said:
This should be closed mods...?
Click to expand...
Click to collapse
Juhan Jufri said:
Deleted maybe? Since if they close it people can still open and see the thread
Click to expand...
Click to collapse
I'd rather put it in the Hall of "Fame" forum, if only such existed
chasmodo said:
Kernel = BIOS?
ClockWorkMod is a kernel?
Kernels are *usually* capable of flashing or resetting?
Pray tell me, when was the last time you had visited planet Earth?
Click to expand...
Click to collapse
lol,,, I was depressed today but really you made my day man
Now it is proven. Chasmodo's wisdom saves human life.
I am surprised that you guys understood what he wrote on the OP. Why I can't get it right
I make SAFE KERNER GUIDE:
I make safe kerner. When you use my kernal you head make beef beserki. A kernel can stop time, but time cant stope the kerner.
Once you get inside of it, you start to regret it. Kernel make good company, but if you have big time hockey puck, you can use the SAFE KERNER to make sure that it doesnt reboot.
Once it Make Reboot, then you make SAFER KERNER to be recovered by an intermediate addendum to the plaintiff's first motion for summary judgment.
a SAFER SAFER SAFER KERNER is when in 1492 Columbus Sailed the Ocean Blue. North South East West.
Lol the funniest part
LOOK AT THE ONE PERSON WHO HIT THANKS... Guess who!
Sent from my GT-N7000 using Tapatalk 2