Related
In December, when I picked up my TF101, I used Razorclaw + CWM to root it. I also found some kind of an update here that I applied that allowed me to overlock the device .. I believe it was a form of kernel patch?
I would like to go to ICS. I need to be rooted after ICS though, we have a VPN client for our SonicWall firewall that requires the OS to be rooted. I would also prefer an ICS port that supports overclocking like my current build .. it's been incredibly useful to clock up in to the 1400s as it makes everything run so much better.
Is it possible to upgrade to the stock ICS, root it easily and patch it to allow for overclocking at this time? If so, could someone direct me to a guide that shows what the easiest way to do this is, since I already have CWM in (although can't remember how to get it to come up on boot .. doh)?
Thanks =)
Wait till Asus fix the problems.
Yea dont install ICS, it would be like pouring water over your PC
It might seem fun at the time, but its really not a good idea
I would say it is a very bad idea. Avoid it. I did it and literally my tablet is unusable now because of
Slow response
Random rebooted
Random no message crash of apps like gmail.
Dead slow,app response
white screen on app loading
It is now embarrassing infront of ipad users.
Sent from my Transformer TF101 using Tapatalk
spinaldex said:
In December, when I picked up my TF101, I used Razorclaw + CWM to root it. I also found some kind of an update here that I applied that allowed me to overlock the device .. I believe it was a form of kernel patch?
I would like to go to ICS. I need to be rooted after ICS though, we have a VPN client for our SonicWall firewall that requires the OS to be rooted. I would also prefer an ICS port that supports overclocking like my current build .. it's been incredibly useful to clock up in to the 1400s as it makes everything run so much better.
Is it possible to upgrade to the stock ICS, root it easily and patch it to allow for overclocking at this time? If so, could someone direct me to a guide that shows what the easiest way to do this is, since I already have CWM in (although can't remember how to get it to come up on boot .. doh)?
Thanks =)
Click to expand...
Click to collapse
Ignore the fear mongering posters.
Tons of people are using ICS without issues. But yes, some do experience issues.
Since you have CWM, you can directly flash the pre-rooted stock ICS. http://forum.xda-developers.com/showthread.php?t=1552303 This is the latest 9.2.1.17 version.
If you want to overclock, you can flash custom ICS ROMs that support overclocking. There's only 2 at the moment, Team EOS and Codename Android.
Frequently updated custom ICS roms such as Team EOS and CM9 tend to be very stable and have fixes that stock ICS doesn't have, so flash a custom ROM instead of the stock ROM if you are concerned about possible issues.
As always, do factory reset + clear cache + clear dalvik cache within CWM before flashing the stock ROM or any custom ROM.
To be safe, I would update your CWM to the latest version here http://forum.xda-developers.com/showthread.php?t=1213723 before flashing anything.
horndroid said:
Ignore the fear mongering posters.
Tons of people are using ICS without issues. But yes, some do experience issues.
Since you have CWM, you can directly flash the pre-rooted stock ICS. http://forum.xda-developers.com/showthread.php?t=1552303 This is the latest 9.2.1.17 version.
If you want to overclock, you can flash custom ICS ROMs that support overclocking. There's only 2 at the moment, Team EOS and Codename Android.
Frequently updated custom ICS roms such as Team EOS and CM9 tend to be very stable and have fixes that stock ICS doesn't have, so flash a custom ROM instead of the stock ROM if you are concerned about possible issues.
As always, do factory reset + clear cache + clear dalvik cache within CWM before flashing the stock ROM or any custom ROM.
To be safe, I would update your CWM to the latest version here http://forum.xda-developers.com/showthread.php?t=1213723 before flashing anything.
Click to expand...
Click to collapse
Terrible advise.
Why tell someone to update to an OS that has literally flooded XDA and other forums, and ASUS's facebook page with people saying their TF is no longer usable ?
For the sake of waiting for a working update, why suggest doing something that could very well turn their TF into a buggy POS ?
There is nothing in ICS that is worth the risk
*Detection* said:
Terrible advise.
Why tell someone to update to an OS that has literally flooded XDA and other forums, and ASUS's facebook page with people saying their TF is no longer usable ?
For the sake of waiting for a working update, why suggest doing something that could very well turn their TF into a buggy POS ?
There is nothing in ICS that is worth the risk
Click to expand...
Click to collapse
There are just as many people, probably much much more, who aren't having problems.
Besides, have you tried any custom ROMs? If not, stfu.
I would no say my TF is unusable under ICS.
It works fine, apart from not so random reboots, as it reboots mainly in the morning when I wake it up form the night...
maybe the Sleeping Beauty requires a kiss from the Prince ...
By the way, it used to be really better under HoneyComb, I wish i could have refused that damned firmware upgrade ...
If I were you I'd rather wait as an other poster said for a really proven Stable version from Asus
Nickola
horndroid said:
There are just as many people, probably much much more, who aren't having problems.
Besides, have you tried any custom ROMs? If not, stfu.
Click to expand...
Click to collapse
Who the F are you telling to stfu ?
Of course I have tried custom ROMs you doosh, I just prefer to have a stock TF, well, I did until ASUS decided to send out buggy sh**
*Detection* said:
Who the F are you telling to stfu ?
Of course I have tried custom ROMs you doosh, I just prefer to have a stock TF, well, I did until ASUS decided to send out buggy sh**
Click to expand...
Click to collapse
If you are using one of the better custom ICS roms and still having such bad issues, the problem is you and your apps since those AOSP roms aren't even based on Asus's ICS.
The OP has root and CWM, and wants to overclock. So how was it a bad advice to recommend a custom ICS rom?
Just because you are having issues, doesn't mean everyone else will.
I've never had any issues at all and I just got done testing like 5 different ROMs. No issues whatsoever. Probably because I do it correctly and do a full wipe including format /system before I flash anything.
I've got issues on Stock and I did a full wipe using voldn+power method and this was before I rooted. I also lost sound randomly on Stock, and the custom kernels I still get reboots but my sound for the main part does work.
So, if the OP needs their tablet to work correctly then wait, if it's not that important to them and they don't need for day to day tasks then take a chance, you might get lucky or you might be causing yourself a headache, up to you.
horndroid said:
If you are using one of the better custom ICS roms and still having such bad issues, the problem is you and your apps since those AOSP roms aren't even based on Asus's ICS.
The OP has root and CWM, and wants to overclock. So how was it a bad advice to recommend a custom ICS rom?
Just because you are having issues, doesn't mean everyone else will.
I've never had any issues at all and I just got done testing like 5 different ROMs. No issues whatsoever. Probably because I do it correctly and do a full wipe including format /system before I flash anything.
Click to expand...
Click to collapse
How is the problem me when I am doing everything the "ASUS way" ?
The problem is ASUS and their code.
If you read the OP's actual post, you will see this line
"Is it possible to upgrade to the stock ICS"
And if you want to go even further into it, your line "Probably because I do it correctly and do a full wipe including format /system before I flash anything"
I don't think you can get a cleaner flash than NVFLASH, which is how I always flash my ROMs
Entropy recently stated that using any leaked build was dangerous.
I have used every single version of AOSP and CM9 from the beginning to current, jumping between and back and forth from GB many times with no issues.
I have also never SEEN a report of anyone bricking (when properly) flashing around with these roms.
Just curious if a case actually exists.
crawlgsx said:
Entropy recently stated that using any leaked build was dangerous.
I have used every single version of AOSP and CM9 from the beginning to current, jumping between and back and forth from GB many times with no issues.
I have also never SEEN a report of anyone bricking (when properly) flashing around with these roms.
Just curious if a case actually exists.
Click to expand...
Click to collapse
No but there is a risk. And the question is : "Do you want to take this risk while CM9 is announce next week with a safe kernel".
I was using Imilka Cm9, and yesterday i flashed back to GB. Maybe you could wait one week and avoid flashing a hazardous repack !
I had no issues with Imikas cm9 roms, I used all 3 of them and have since flashed to a stock gingerbread as the video playback in all the ICS roms is not good enough yet compared to GB roms.
I have tried all the ICS leaks and gone back to GB with no issues, just waiting for a proper stable release of ICS with good video playback performance as I get in GB then I will stick with the Ice Cream
remixtech said:
No but there is a risk. And the question is : "Do you want to take this risk while CM9 is announce next week with a safe kernel".
I was using Imilka Cm9, and yesterday i flashed back to GB. Maybe you could wait one week and avoid flashing a hazardous repack !
Click to expand...
Click to collapse
I wasn't stating that there isn't a risk, or that anyone should chance it. Just simply that I have not heard of a single case of anyone having a problem with iMilka's releases (killing the board). Therefore my none developer point of view is that the risk must be VERY small IF said risk does truly exist with all Kernel Leak builds.
It SEEMS to me that the problem does not lie with the kernel build but the way it is scripted and executed. Hence why no one has ever had the problem with AOSP/CM9, but the problem came up with Angelom's kernel and the last Stunner build. The problems were also immediate in both cases, again where no one has ever had this problem caused by AOSP/CM9. So YES, I am sure AOSP/CM9 could have caused the problem if iMilka made whatever mistake was made by Stunner/Angelom, but I would say to me it is quite obvious he did not, and that the problem IS a mistake in the way the kernel is handled. Speculation and opinion only of course.
I have been running them since the beginning, so I am not saying I personally would have chanced it this close to offical ICS / Official CM9, but i've been running his releases for quite some time.
crawlgsx said:
Entropy recently stated that using any leaked build was dangerous.
I have used every single version of AOSP and CM9 from the beginning to current, jumping between and back and forth from GB many times with no issues.
I have also never SEEN a report of anyone bricking (when properly) flashing around with these roms.
Just curious if a case actually exists.
Click to expand...
Click to collapse
Flashed all imilka Roms from day one, and never had as much as a hiccup on any one of them.
The question is if anyone tried to restore a cwm backup ? The most of the bricks were caused by doing that task..
Sent from my GT-N7000 using xda premium
No issues here either with Midnote or TeamMid ROMS (also tried a couple of Alba versions and Stunner).
I have flashed many times and with LP5 kernel through CWMR or Mobile Odin including full wipes.
I have made nandroid backups but haven't tried to restore any, perhaps this has saved me?
Tried CWM restore twice on ICS (missed reports that it is not recommended). Both times ended with corrupted system partition. But both times fixed this problem by flashing stock ROM with desktop Odin. Had no problems after.
Sent from my GT-N7000 using xda premium
dimcus said:
Tried CWM restore twice on ICS (missed reports that it is not recommended). Both times ended with corrupted system partition. But both times fixed this problem by flashing stock ROM with desktop Odin. Had no problems after.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Exactly the same here. Unable to format /system partition after restoring.
Odin managed to fix it tho.
jscurtu said:
The question is if anyone tried to restore a cwm backup ? The most of the bricks were caused by doing that task..
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I have multiple times. CWM Backup restore works sometimes for me ICS to ICS, and fine GB to GB. ICS to GB or GB to ICS causes issues but I can easily fix them with a flash/odin/etc and still have complete access to download mode / CWM. ICS to ICS I have run in to problems such as funky root or partition issues, once again still easily fixable and still have plenty of access to the phone/flash abilities, By no means even close to a brick.
That said at this point in the game I wouldn't even consider doing a CWM restore, why even chance it!
dimcus said:
Tried CWM restore twice on ICS (missed reports that it is not recommended). Both times ended with corrupted system partition. But both times fixed this problem by flashing stock ROM with desktop Odin. Had no problems after.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Just to report, I experienced exactly the same.
Regards!
Sent from my GT-N7000 using xda premium
dimcus said:
Tried CWM restore twice on ICS (missed reports that it is not recommended). Both times ended with corrupted system partition. But both times fixed this problem by flashing stock ROM with desktop Odin. Had no problems after.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Which kernel were you on?
chill392 said:
Which kernel were you on?
Click to expand...
Click to collapse
The first leaked one - LP1.
jscurtu said:
The question is if anyone tried to restore a cwm backup ? The most of the bricks were caused by doing that task..
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I think you are wrong.Bricks caused when trying to format /system
Sent from my GT-N7000 using Tapatalk
Bricks were caused by anything that tried to wipe a partition - and restoring a nandroid will first wipe a partition.
What kernel is imilka's a repack of? Maybe it's an unaffected one. I recall seeing stuff in imilka's thread saying not to use its CWM.
Without source for the leak kernels it's impossible to tell what's changed and declare one kernel "safe" and another "dangerous" - as long as some are proven dangerous they should all be considered dangerous.
afilopou said:
I think you are wrong.Bricks caused when trying to format /system
Sent from my GT-N7000 using Tapatalk
Click to expand...
Click to collapse
When restoring a backup , you usually format /system ; )...so basically yes that is correct, I only mentioned that it mostly happened while doing that task..
Sent from my GT-N7000 using xda premium
Entropy512 said:
What kernel is imilka's a repack of? Maybe it's an unaffected one. I recall seeing stuff in imilka's thread saying not to use its CWM.
Without source for the leak kernels it's impossible to tell what's changed and declare one kernel "safe" and another "dangerous" - as long as some are proven dangerous they should all be considered dangerous.
Click to expand...
Click to collapse
It was multiple different kernels, up to LP5 and LP6 even.
I understand the logic and respect your words of caution with what is most certainly from someone who has a much better understanding than I, I just feel it is the way the kernel was used/modified/implemented that caused the potential problems (by the devs), not the kernel itself. Based on the logic I provided earlier in the thread. I am not saying the problem still does not exist in the kernel, I have no idea, but it is obviously something that did not come out in many rom implementations, just those 2.
Flashed all roms from maxicet and some repack stock ICS roms. Never got any problems. Tested over 10 ICS roms... And now using maxicet's ROM as daily.
crawlgsx said:
It was multiple different kernels, up to LP5 and LP6 even.
I understand the logic and respect your words of caution with what is most certainly from someone who has a much better understanding than I, I just feel it is the way the kernel was used/modified/implemented that caused the potential problems (by the devs), not the kernel itself. Based on the logic I provided earlier in the thread. I am not saying the problem still does not exist in the kernel, I have no idea, but it is obviously something that did not come out in many rom implementations, just those 2.
Click to expand...
Click to collapse
The thing is, this has happened over multiple devices, with multiple recovery implementations, including recovery implementations that work fine with other kernel bases. The end result is the same - fried eMMC that can't even be recovered with JTAG.
Entropy512 said:
The thing is, this has happened over multiple devices, with multiple recovery implementations, including recovery implementations that work fine with other kernel bases. The end result is the same - fried eMMC that can't even be recovered with JTAG.
Click to expand...
Click to collapse
Agreed, very bad.
All I am saying is that it ONLY happened on those 2 botched kernel implementations. It is obviously SOMETHING the Dev's did with the kernel that caused this, seeing how ALL the other roms/versions clearly have not caused this. Since the result was immediate with both of those and many of us have jumped/cwm'ed/etc from MANY different Leaked kernel builds and NOT had that problem.
I am not trying to put them at blame, running any rom/dev is strictly at your own responsibility and risk, just stating that I don't think it is fair to place every leaked rom build in the same category of danger. Is there a risk, certainly, as the dev's could accidentally make said same mistake (I am not even clear if "we" know what causes it?) in a future version. That said I feel pretty confident that if the "final" versions of iMilka's roms were going to cause that issue, it would've happened by now. That is why I wanted to see if anyone had ever been bricked (fried eMMC) from them, and it seems, no.
I have flashed my rooted SGN to LPY ROM using mobile ODIN. First two days i had issues however now it seems fine.
1. Battery working fine 24Hrs on average with single charge (With 3G and Wifi on always)
2. No issues with screen or swype.
3. No issues with any other apps as of now
With all the Kernel related posts i'm a little worried. My phone kernel also shows as XXLPY. Please suggest if I need to do anythig to fix it.
Sent from my GT-N7000 using XDA
just do not do any full wipe, either from phone or CWM and you should be safe.
cracklenet said:
I have flashed my rooted SGN to LPY ROM using mobile ODIN. First two days i had issues however now it seems fine.
1. Battery working fine 24Hrs on average with single charge (With 3G and Wifi on always)
2. No issues with screen or swype.
3. No issues with any other apps as of now
With all the Kernel related posts i'm a little worried. My phone kernel also shows as XXLPY. Please suggest if I need to do anythig to fix it.
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
Danger lies in changing ROMs, as long as you keep it you're safe.
Should you decide to flash sth different, then read the instructions several times, then again, and one more time, part of the bricks happened due to small mistakes by experienced flashers.
Sent from my GT-N7000 using xda premium
Is Full wipe and Factory Reset the same?
After installing the ROM i had done a factory reset. Nothing happemed but for some setting changes. I'm able the use without issues.
Please advise.
Sent from my GT-N7000 using XDA
cracklenet said:
Is Full wipe and Factory Reset the same?
After installing the ROM i had done a factory reset. Nothing happemed but for some setting changes. I'm able the use without issues.
Please advise.
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
yeah someone pls reply to this question cause i flashed LPY twice and i did the factory reset and cleared the cache but did not get any problem.
I also flashed and wiped a couple of times while in LPY. I'm having no problems so far, but I read someone tried to flash with PC Odin and brocked because his eMMC was ALREADY damaged.
Is there a way to know if my device has some kind of damage?
aami.aami said:
yeah someone pls reply to this question cause i flashed LPY twice and i did the factory reset and cleared the cache but did not get any problem.
Click to expand...
Click to collapse
Wipe data/factory reset is where the problem lies. You can do it and be fine but you could do it again and be bricked. I did a wipe after install before the problem was known.
Just do what has already been posted don't factory reset from cwm or settings. If changing rom read everything several times before flashing
Sent from my GT-N7000 using xda premium
cracklenet said:
I have flashed my rooted SGN to LPY ROM using mobile ODIN. First two days i had issues however now it seems fine.
1. Battery working fine 24Hrs on average with single charge (With 3G and Wifi on always)
2. No issues with screen or swype.
3. No issues with any other apps as of now
With all the Kernel related posts i'm a little worried. My phone kernel also shows as XXLPY. Please suggest if I need to do anythig to fix it.
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
I am in the same boat as you bro. I think that you should stick to ICS for now. I am doing the same. It seems that google and samsung are already aware of this bug so i choose to wait instead of risking a bad flash. It seems that none of the methods are 100% right now so just i recommend you stick to ICS just be cautious and don't delete large files (larger than 1gb) and don't use CWM nor factory reset for now... In the end we are lucky we didnt get our devices bricked in the first place.
yllivia said:
I am in the same boat as you bro. I think that you should stick to ICS for now. I am doing the same. It seems that google and samsung are already aware of this bug so i choose to wait instead of risking a bad flash. It seems that none of the methods are 100% right now so just i recommend you stick to ICS just be cautious and don't delete large files (larger than 1gb) and don't use CWM nor factory reset for now... In the end we are lucky we didnt get our devices bricked in the first place.
Click to expand...
Click to collapse
there is already new ICS LPF, reportedly safe and faster than LPY - there is also/already dr ketan's guide on whats and hows
yllivia said:
I am in the same boat as you bro. I think that you should stick to ICS for now. I am doing the same. It seems that google and samsung are already aware of this bug so i choose to wait instead of risking a bad flash. It seems that none of the methods are 100% right now so just i recommend you stick to ICS just be cautious and don't delete large files (larger than 1gb) and don't use CWM nor factory reset for now... In the end we are lucky we didnt get our devices bricked in the first place.
Click to expand...
Click to collapse
yea ,,in the same boat as well and equally confused man .....
wish thr was a magic wand for this to fix it ,,,lol
so i guess most of us are finally deciding to stay on LPY even after entropy is saying to stay away from LPY ?
---------- Post added at 08:11 PM ---------- Previous post was at 08:10 PM ----------
p107r0 said:
there is already new ICS LPF, reportedly safe and faster than LPY - there is also/already dr ketan's guide on whats and hows
Click to expand...
Click to collapse
u see the issue with that idea is that most of us have already wiped the cache after installing LPY so now trying to go to LPF cud potentially result in bricking it .....what do ?
p107r0 said:
there is already new ICS LPF, reportedly safe and faster than LPY - there is also/already dr ketan's guide on whats and hows
Click to expand...
Click to collapse
From what i have read LPF has 0x19 firmware therefore has potentialy the same problem with bricking
Sent from my GT-N7000 using xda premium
Being afraid of the bug I flashed a rooted GB kernel before using Odin to upgrade from LPY to LPF The bug is apparently in the way the kernel sets the emmc chip erase process This apparently mainly affects the /data partition so flashing a gb kernel should be safe. I then used odin to update to the newer firmware.
Sent from my GT-N7000 using xda premium
gurnishdhillon said:
yea ,,in the same boat as well and equally confused man .....
wish thr was a magic wand for this to fix it ,,,lol
so i guess most of us are finally deciding to stay on LPY even after entropy is saying to stay away from LPY ?
---------- Post added at 08:11 PM ---------- Previous post was at 08:10 PM ----------
u see the issue with that idea is that most of us have already wiped the cache after installing LPY so now trying to go to LPF cud potentially result in bricking it .....what do ?
Click to expand...
Click to collapse
As far as i know there has been no reports of bricks on LPF but most of the people that flashed LPF flashed it from GB. We in the other hand are stuck we might have a leftover from flashing LPY. I would rather risk downgrading to GB then jumping to another unsettled ship. I am staying here just taking precautions NOT to use Recovery nor any kind of thing that involves wiping data.
Originally Posted by Chainfire
Ok so it still isn't really clear if the problem is still present in LPY, or if the issue is "left-over" due to previous ROMs.
It's all possible. Either way, what I wan't to make absolutely clear again:
If the problem is present in CF-Root LPY (and it's not a "leftover" problem from previous ROM - this is possibly the case), then it's also present in stock LPY. This means you *can* randomly brick your phone even if fully booted into Android, under heavy I/O load.
(on the Note there normal and recovery kernels are the same, and CWM is just a userspace program, nothing special(!) - so if the problem can happen in CWM, it can happen in Android)
Click to expand...
Click to collapse
gurnishdhillon said:
yea ,,in the same boat as well and equally confused man .....
wish thr was a magic wand for this to fix it ,,,lol
so i guess most of us are finally deciding to stay on LPY even after entropy is saying to stay away from LPY ?
---------- Post added at 08:11 PM ---------- Previous post was at 08:10 PM ----------
u see the issue with that idea is that most of us have already wiped the cache after installing LPY so now trying to go to LPF cud potentially result in bricking it .....what do ?
Click to expand...
Click to collapse
What you can do is only swap the kernel using mobile odin. I swapped it with the LPF CF-Kernel and everything is fine. But be advised, LPF has not been confirmed to be save yet.
Sent from my Galaxy Note running ICS
cracklenet said:
Is Full wipe and Factory Reset the same?
After installing the ROM i had done a factory reset. Nothing happemed but for some setting changes. I'm able the use without issues.
Please advise.
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
Yes. The problem is intermittent - you can often wipe once or twice, sometimes even ten times, before getting nailed.
Others (like xplodwild) get nailed the first time.
craig432 said:
From what i have read LPF has 0x19 firmware therefore has potentialy the same problem with bricking
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
No, XXLPY/ZSLPF don't "have" the eMMC firmware. The eMMC firmware is part of the eMMC chip itself - right now, whatever you have is what came with your phone. There is currently no way to change it.
The problem is that the firmware has a bug that will cause it to sometimes do VERY bad things if an erase command is sent to it:
I9100 update4 kernels don't support MMC ERASE at all - so they don't trigger the bug in the firmware in the first place
M250S Update5 does - So it triggers the bug - We don't have source for any other ICS kernel yet but I suspect they all have MMC_CAP_ERASE set
What I can't figure out is why Gingerbread isn't dangerous despite having MMC_CAP_ERASE set. I need to read in more detail, but it might be that even if the driver supports MMC_CAP_ERASE, some other change between 2.6.35 and 3.0 makes ERASE get used in situations it didn't get used in previously.
You need two things: buggy firmware (so far, nearly every Note and Exynos-based GS2 has this) and a kernel that will fire ERASE commands at the chip when wiping.
If a method can be found to update the flash chip's firmware, then XXLPY and ZSLPF will become safe when running on fixed chips.
Hey entropy is it possible to use the cm9 kernel with lpy? I'm assuming it is but don't want to take any risks
Somebody please shed light on this ?
- Is it possible that affected kernels inflict damage every time you perform factory reset or wipe data from recovery but it does not brick your phone.
But in future it might get bricked even on safe kernel just because you had used affected kernels ??
**** I had used recovery on LPY many times.
I'm sorry. I SWEAR I read tons of threads but things still aren't clear to me.
ICS leaks seem to possibly brick the Note.
But there are several threads with official ICS firmwares for the Note (ex: http://forum.xda-developers.com/showthread.php?t=1646088)
Can I use the official ICS firmware to upgrade my Note? Or should I wait a bit more?
Thanks!
From what I understand, you should be fine with official ICS as long as you don't do factory/data reset with the stock kernel. What are you using now?
leppo said:
From what I understand, you should be fine with official ICS as long as you don't do factory/data reset with the stock kernel. What are you using now?
Click to expand...
Click to collapse
Kernel says 2.6.35.7-N7000UBKK8
I suppose I'll stay on GB. Things look a bit scary even with the stock kernel!
The official can brick the note muaaahuahuahuahuuaaa
Seriously as the previous poster said only if you are into wiping and restoring you MAY be in danger
Sent from my iPad using Tapatalk
fjhuerta said:
I'm sorry. I SWEAR I read tons of threads but things still aren't clear to me.
ICS leaks seem to possibly brick the Note.
But there are several threads with official ICS firmwares for the Note (ex: http://forum.xda-developers.com/showthread.php?t=1646088)
Can I use the official ICS firmware to upgrade my Note? Or should I wait a bit more?
Thanks!
Click to expand...
Click to collapse
Well I upgraded my Note and it is completely fine, my friend with a Note as well hasn't told me about his phone being bricked either. But I'm not sure about all the others though, since mine is the Hong Kong official one, and I never use the leaks so they don't really bother me.
Sent from my Galaxy Note
leppo said:
From what I understand, you should be fine with official ICS as long as you don't do factory/data reset with the stock kernel. What are you using now?
Click to expand...
Click to collapse
When you say factory reset you mean going into settings and then "data factory reset"? I normally do that after a huge update and format my SD card too. So that is a no no on ICS?
Sent from my GT-N7000 using xda premium
Hagow said:
When you say factory reset you mean going into settings and then "data factory reset"? I normally do that after a huge update and format my SD card too. So that is a no no on ICS?
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
That is correct.
leppo said:
From what I understand, you should be fine with official ICS as long as you don't do factory/data reset with the stock kernel.
Click to expand...
Click to collapse
Bull****. I have tried to do wipe from CWM and MobileOdin over and over again more than 15 times at ICS leaks and ICS stocks and custom kernels and custom ROMs. Never got any problem.
anonymous572 said:
Bull****. I have tried to do wipe from CWM and MobileOdin over and over again more than 15 times at ICS leaks and ICS stocks and custom kernels and custom ROMs. Never got any problem.
Click to expand...
Click to collapse
You might want to read the stickies in this forum regarding the fact that it's not an issue that effects all users. But it effects some by bricking their phones.
Along with the advice to not tell others that the problem doesn't exist based on your experience.
diji1 said:
You might want to read the stickies in this forum regarding the fact that it's not an issue that effects all users. But it effects some by bricking their phones.
Along with the advice to not tell others that the problem doesn't exist based on your experience.
Click to expand...
Click to collapse
Please don't tell others that all N7000 have problems with wiping on ICS roms. I never saw anyone who have this strange wipe "problem".
anonymous572 said:
Please don't tell others that all N7000 have problems with wiping on ICS roms. I never saw anyone who have this strange wipe "problem".
Click to expand...
Click to collapse
How can you say that man,,,thr are so many ppl on Xda here that are reporting to have bricked thr devices......or are you saying that as long as you r not rooted , this bricking thing just wudn't happen?
anonymous572 said:
Please don't tell others that all N7000 have problems with wiping on ICS roms. I never saw anyone who have this strange wipe "problem".
Click to expand...
Click to collapse
and I never saw anyone without this strange wipe problem, want to know for sure? go install an app by chainfire called got brickbug?
http://forum.xda-developers.com/showthread.php?t=1693704
maybe you are lucky to have an unaffected chip ,but 99.9% of users have a known damaged chip fw.
I suggest you go read the sticky in which it says that some people have wiped 19 times and got a full brick on the 20th attempt ,some even more .
I myself have wiped once safely ,but the second wipe made the emmc go nuts ,luckily however it was not fully dead ,and I restored it ,barely .
besides ,samsung and Google have both confirmed this bug ,so who are you to state otherwise?!!
http://forum.xda-developers.com/showthread.php?p=27137024
so I would like to suggest that you stop spreading dangerous miss information to the noobs or I'll report your post next time.
MR.change said:
besides ,samsung and Google have both confirmed this bug ,so who are you to state otherwise?!!
http://forum.xda-developers.com/showthread.php?p=27137024
so I would like to suggest that you stop spreading dangerous miss information to the noobs or I'll report your post next time.
Click to expand...
Click to collapse
+1
The source of the problem has been found and confirmed...how can people still be ignorant and spread bad advice.
As Mr.change said above, yes there is a problem even with official ICS, you may get lucky but you will run into a problem eventually if you keep wiping data/factory reset with affected ICS kernels...so best not to do so.
What would be the alternative to a factory reset then? I'm waiting to receive a new Note and intend to install stock ICS straight away but I worry that I'll mess up my first ever Android install and have to start again. Could you re.install the update without a wipe?
solarboy said:
What would be the alternative to a factory reset then? I'm waiting to receive a new Note and intend to install stock ICS straight away but I worry that I'll mess up my first ever Android install and have to start again. Could you re.install the update without a wipe?
Click to expand...
Click to collapse
if you are new to this then I would advise that you stay way from it till you learn your way around the basics of flashing using PC ODIN ,mobile ODIN ,and recovery.
then flash stock ICS with a safe custom kernels and you should be safe.
besides ,samsung stock ICS isn't that different from GB ,same look and same performance . you'd want to install CM9 to get a taste of true ICS.
so like I said ,take your time ,bricking your new shinny phone can be devastating .
anonymous572 said:
Please don't tell others that all N7000 have problems with wiping on ICS roms. I never saw anyone who have this strange wipe "problem".
Click to expand...
Click to collapse
The problem is you don't know if you will hit the problem until you find out the hard way.
Once you've hit the problem there is no recovery.
So stop telling everyone that they are safe because you got lucky.
People who want to run ICS should use a kernel that has a safe configuration (MMC_CAP_ERASE removed from drivers/mmc/host/mshci.c) - This includes, but is not necessarily limited to (check the kernel's info) the CM9 included kernel, Hardcore's Speedmod ICS, and Franco.kernel r3 and above. Be sure to verify that you're running a safe kernel with CPUSpy before dropping into recovery - a few people had Mobile Odin fail to flash a safe kernel when they were on a dangerous one and then bricked because they didn't verify.
شكرا
solarboy said:
شكرا
Click to expand...
Click to collapse
you are most welcome my friend
لا شكر على واجب
nandihno said:
The official can brick the note muaaahuahuahuahuuaaa
Seriously as the previous poster said only if you are into wiping and restoring you MAY be in danger
What do u mean..? doing a factory reset is a common thing.. who on this earth doesn't do a factory data reset at all on their phone.. and if u ask me we must do a factory reset after updating to a new rom.
Pity on samsung.. their official builds destroy the phone. I can't believe.. how they released it without testing.. and why didnt the stop their ****ty ics update from being live till now..
i also have a question .. Has Samsung acknowledged the fact that their stock ics can cause bricking issues?
Click to expand...
Click to collapse
It was nice 8 months experience,just Super bricked my Note while perfotming a wipe with CWM,too bad couldnt claim the warrenty.
Thanks for everyone who helped me during this period,both Developers and Members.
Jack
Sorry for your phone man.
Btw which kernel were you using?
Boy124 said:
Sorry for your phone man.
Btw which kernel were you using?
Click to expand...
Click to collapse
German LRK DBT stock 4.0.4 and it was running fine no problems,just wiped it to test the Paranoid Android JB 4.1.1,which was actually the last thing it did.
I see. But you can't flash roms using stock recovery. Anyways it confirms the bug still exists.
What CWM did you use or did you wipe from stock recovery?
Does it give any sign of life?
If it boots you can use: https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check
to see if you have emmc damage.
jgaviota said:
What CWM did you use or did you wipe from stock recovery?
Does it give any sign of life?
If it boots you can use: https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check
to see if you have emmc damage.
Click to expand...
Click to collapse
Unfortunately doesnt boot up,just stuck on the Gt-7000 logo but the download screen works,however when try to flash with PC Odin stops at the factoryfs.img which after research discovered is a Superbrick symptom.
hagba said:
too bad couldnt claim the warrenty.
Click to expand...
Click to collapse
Hello hagba, since you cannot claim warranty have you thought of getting your device repaired via the Samsung service centre in your region?
I would suggest you to enquire about the repair cost and then make a suitable decision.
Have you tried this? it worked for many users.
http://forum.xda-developers.com/showthread.php?p=26285877
YLNdroid said:
Hello hagba, since you cannot claim warranty have you thought of getting your device repaired via the Samsung service centre in your region?
I would suggest you to enquire about the repair cost and then make a suitable decision.
Click to expand...
Click to collapse
First thing on monday,
dr.ketan said:
Have you tried this? it worked for many users.
http://forum.xda-developers.com/showthread.php?p=26285877
Click to expand...
Click to collapse
Dr.Ketan,
I have tried the PIT procedure,but its such a long and tedious process Im not sure will be able to make viable partition for normal usage.
However will see what Samsung does on Monday.
So does this mean that Stock ROMS are still unsafe to wipe rather than how samsung claims that Stock ROM wont brick?
Did you report this to Entropy? Did you wipe after flashing Paranoid ROM successfully or did you wipe on stock. If it was after succesfully flashing the CM10 based JB ROM, it should mean that CM10 doesnt have MMC_CAP_ERASE disabled or maybe no ICS kernel is safe.
Should report to Entropy if you didnt.
He already.wrote 'wipe it to test jb' means wiped on.stock.
Entropy aleeady aware of this (i have already reported 2 case on 4.0.4). And he hav mentioned on his thread, stock ics are known unsafe kernels.
Sent from my GT-N7000 using xda premium
dr.ketan said:
He already.wrote 'wipe it to test jb' means wiped on.stock.
Entropy aleeady aware of this (i have already reported 2 case on 4.0.4). And he hav mentioned on his thread, stock ics are known unsafe kernels.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I made a mistake of wiping twice from Settings under android in Indian Stock DDLP8 stock 4.0.3 but luckily never bricked. But now I take care not to. But do you think I may have caused damage in the first two wipes? I see no issues till now but just asked.
It cause damage once in while, not every wipe/reset result to brick (good if it was like that, sammy must have find solution then)
Still if you have any doubts find 'emmc brick bug' application from market n scan ur device.
Sent from my GT-N7000 using xda premium
dr.ketan said:
It cause damage once in while, not every wipe/reset result to brick (good if it was like that, sammy must have find solution then)
Still if you have any doubts find 'emmc brick bug' application from market n scan ur device.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I have the affected emmc firmware VYLOOM 0x19. Its just that I turned out to be lucky. I dont believe Samsung would fix the Indian firmware (4.0.3) while the bug remains on the latest 4.0.4 ROMS. If there is a fix from Samsung, we Indians are the ones who usually get it last. But strangely, I havent heard of any superbricked Indian Notes in this forum.
satishp said:
So does this mean that Stock ROMS are still unsafe to wipe rather than how samsung claims that Stock ROM wont brick?
Did you report this to Entropy? Did you wipe after flashing Paranoid ROM successfully or did you wipe on stock. If it was after succesfully flashing the CM10 based JB ROM, it should mean that CM10 doesnt have MMC_CAP_ERASE disabled or maybe no ICS kernel is safe.
Should report to Entropy if you didnt.
Click to expand...
Click to collapse
I think Samsung's claim was that you won't get bricked if you stick to stock and don't root. I'm not saying that's true . Even seems unlikely since I think you can factory wipe from the settings without root, IIRC (memory's rusty, haven't been on a stock ROM for ages).
There were some bricks with CM10, but only from people who flashed from stock ICS or stock ICS based ROMs. Flashing from the safe ICS kernels seems to still be safe.
satishp said:
But strangely, I havent heard of any superbricked Indian Notes in this forum.
Click to expand...
Click to collapse
Maybe that's because Indians are careful enough to read the instructions before risking their device? I doubt it's because Indian Notes have had some special pixie dust sprinkled over them while they passed customs.
If you dont mod your device then how many chances are.there to make hard reset device?
I know lot ppl they purchasing and selling.device without single reset.
So rooting opens.100 ways to explore ur device, simultaneously opens 100 ways to put u in situation,u needs reset. That is the only reason rate.of bricking is high with rooted device, but if you read carefully and avoid reset/wiping there is almost zero chances to brick.
And yes if you look, compare to selling of notes in india, u don't see indians are quite less on forum?
Sent from my GT-N7000 using xda premium
dr.ketan said:
If you dont mod your device then how many chances are.there to make hard reset device?
I know lot ppl they purchasing and selling.device without single reset.
So rooting opens.100 ways to explore ur device, simultaneously opens 100 ways to put u in situation,u needs reset. That is the only reason rate.of bricking is high with rooted device, but if you read carefully and avoid reset/wiping there is almost zero chances to brick.
And yes if you look, compare to selling of notes in india, u don't see indians are quite less on forum?
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I'm really worried because you said if I avoid wiping I'm almost zero chance of briking.. I got my note clean, I mean I don't dare to put music and movies into it because then I don't dare to delete all those files... Will this brick my phone? I'm stock 4.0.4 rooted
Enviado desde mi GT-N7000 usando Tapatalk 2
Obviously the culprit is wiping with CWM,I have factory Reset million times with no consequences at all,and just once with CWM was enough to Superbrick it,and yes I was on stock ROM.
msedek said:
I'm really worried because you said if I avoid wiping I'm almost zero chance of briking.. I got my note clean, I mean I don't dare to put music and movies into it because then I don't dare to delete all those files... Will this brick my phone? I'm stock 4.0.4 rooted
Enviado desde mi GT-N7000 usando Tapatalk 2
Click to expand...
Click to collapse
It says big files shudn't be deleted. Though frankly speaking i have not seen any case brick by that, though we cant ignore comments from recognised developer.
But wat best idea i found to manage file is
Connect device with PC as mass storage and manage files from PC explorer. I believe that is safe way.
hagba said:
Obviously the culprit is wiping with CWM,I have factory Reset million times with no consequences at all,and just once with CWM was enough to Superbrick it,and yes I was on stock ROM.
Click to expand...
Click to collapse
That was your bad luck this time, otherwise both have same effect.