Found this from Chainfire here Tried it and my device is at risk. If we only had this before the problems with the Leak that was bricking phones.
So, i'm in danger. So what. What can i do?
RatusNatus said:
So, i'm in danger. So what. What can i do?
Click to expand...
Click to collapse
I don't think I'll be using any AT&T leaks. Until they have proven they are safe. At least we can make more informed decisions on what to flash.
blutruck said:
I don't think I'll be using any AT&T leaks. Until they have proven they are safe. At least we can make more informed decisions on what to flash.
Click to expand...
Click to collapse
Already did 8 flashs of aokp. Really great.
No one conplains.
You should try it but Follow the intructions.
Most bricked is user f... up.
Sent from my SGH-I777 using XDA
Wow so i thought this was related to a bad wipe setting Samsung had compiled into their kernels? This is an actual hardware defect now or is it software based??
Sent from my SAMSUNG-SGH-I777 using Tapatalk
I belive AOKP is on the same boat that cm9... ITS SAFE!
Namida said:
It's important to understand that the source of this problem is bad firmware in the eMMC chip. There is nothing technically wrong with the kernel itself. The eMMC claims to support a method of erasure that causes it to write bad data when it's used.
To achieve safety, you either fix the chip so that it supports the method it claims to properly or avoid using that method of erasure.
Cyanogenmod 9 is safe because it doesn't erase using that method. They use their own kernel built from their own source code.
Samsung ICS kernels are not safe because they call the best method the eMMC claims to support when erasing, which is bugged within the chip's firmware.
Anyone who uses the official Samsung ICS kernel or the ICS leaks of Samsung's kernel are at risk. Chainfire's kernel is risky because Chainfire uses Samsung's official kernels and adds Clockwork Mod to them at the binary level. He doesn't have source to modify to make his kernels safe. Samsung must make their kernel safe before Chainfire can release a safe one himself. What Chainfire has done is modify the recovery so that it won't ask the kernel to erase the eMMC in a potentially dangerous way, but it won't stop sources other than that recovery from asking for a potentially bricking erase operation because the kernel hasn't been modified and will still do it if asked to.
Because we know something which versions of the eMMC chip are affected by this flaw, we can determine if a user is at risk simply by asking the chip to identify itself.
Decompiling a kernel is a completely different ball of wax. I wouldn't hold my breath for a tool that can do that and identify if your kernel is patched or not. Besides that, the source of the problem is now known with certainty and can be avoided by not flashing Samsung kernels until Samsung gets off their lazy butt and fixes theirs, or provides the code that can be used to fix the eMMC chip that is the source of all our troubles.
Click to expand...
Click to collapse
Thanks for posting this, I was unaware that the issue had been diagnosed.
Sent from my SAMSUNG-SGH-I777 using Tapatalk 2
Its not the rom its the kernal and the hardware (emmc) so all the att gs2 are gonna all say the same thing .
Sent from my SAMSUNG-SGH-I777 using XDA
Mine is at risk.
Sent from my SGH-I777 using XDA
looks like an snake oil app to me. this is like running a test for bad sectors on a Standard hard drive for defects. THEY ALL LEAVE THE FACTORY WITH DEFECTIVE SECTORS, but they work just fine, and 95% of users never have any clue of this fact
Only this isn't simply bad sectors. Its a certain chips firmware that gets corrupted and unrecoverable when its simply wiped using an ATT ICS kernel...
Sent from my SAMSUNG-SGH-I777 using Tapatalk
Related
So, what exactly is keeping us from flashing kernel's from the HTC One X, or for that matter a ROM made for the One X? I thought that the insides were basically the same, so isn't the software basically identical? Sorry if this sounds noobish, And could anyone clarify as to why this may or may not be possible?
Thank you for your time!
i believe (but not totally positive) not having S-OFF is what is keeping us for now..
butterbuns said:
i believe (but not totally positive) not having S-OFF is what is keeping us for now..
Click to expand...
Click to collapse
no its not that cause if u have a recovery u can flash a kernel... i do kno that
There isn't any source released yet
Not Sent
So, WE don't have the kernel source yet but we do have access to kernels on the One X. I'm curious if we would be able to flash these.
Is there any way that flashing a kernel could brick my phone?
jkt97401 said:
So, WE don't have the kernel source yet but we do have access to kernels on the One X. I'm curious if we would be able to flash these.
Is there any way that flashing a kernel could brick my phone?
Click to expand...
Click to collapse
Flashing kernels from a close relative device is usually not a good idea. Even though you would be able to recover your device from recovery or the bootloader when it bricks. Why don't you try?
Sent from my EVO 4G LTE
jkt97401 said:
So, WE don't have the kernel source yet but we do have access to kernels on the One X. I'm curious if we would be able to flash these.
Is there any way that flashing a kernel could brick my phone?
Click to expand...
Click to collapse
No you cant flash them its a completely different phone. The kernel is made specifically for that phone, if you try ot you WILL BRICK YOU EVO trust me on that. Same with if you try to flash a one x rom. Please dont be that guy.
Sent from my EVO using xda premium
I will try it as soon as I am able.
I have been waiting to flash anything until I can get into the Google Wallet app and reset the settings to protect my NFC.
Needless to say, it's been having issues even getting into the app haha
david279 said:
Flashing kernels from a close relative device is usually not a good idea. Even though you would be able to recover your device from recovery or the bootloader when it bricks. Why don't you try?
Sent from my EVO 4G LTE
Click to expand...
Click to collapse
I think it would be a hard brick right? So no getting into anything incliding recovery. Do not try it. But if you want a 700 dollar paperweight go ahead.
Sent from my EVO using xda premium
Why would it be a hard brick?? A kernel is part of the OS. It's not a firmware or a radio. If a kernel doesn't take, at worst, the phone will lock up. Use the battery pull equivalent to reboot the phone back into recovery and restore a previous image.
In pc terms, a kernel is not the bios. It's just part of the OS that lets the OS communicate with the hardware layer of the machine/device.
gpz1100 said:
Why would it be a hard brick?? A kernel is part of the OS. It's not a firmware or a radio. If a kernel doesn't take, at worst, the phone will lock up. Use the battery pull equivalent to reboot the phone back into recovery and restore a previous image.
In pc terms, a kernel is not the bios. It's just part of the OS that lets the OS communicate with the hardware layer of the machine/device.
Click to expand...
Click to collapse
I always thought a bad kernel would hard brick a phone. My bad. I stand corrected.
Sent from my EVO using xda premium
So any luck with that kernel?
Sent from my EVO using xda premium
Hi Everyone I Want To Test ROM's Before Flash ON My PC So Please Help Me
You can't....
Sent from my GT-I9300 using XDA Premium HD app
Most roms have a video by TotallyDubbed
Sent from my GT-I9300 using xda premium
Hi,
Just made a Nandroid backup of your current rom then flash the new rom you want and if something is wrong or you don't like it... just restore your backup...
You can do that for all the rom you want to test, it is much simpler
That way you can really test on your phone... Even if it were possible on a PC, you can imagine that if you could test it on your pc it would not be comparable to test on your phone.
I Read That Triangle Away Is Very Dangerous Is There Another Way To Reset Flash Counter? I Heard That USB Jig Is Not Working For GS3
I Heard That USB Jig Is Not Working For GS3
Click to expand...
Click to collapse
It does work, in the way it was intended to do and does across all Galaxy devices; to revive a semi-hardbricked phone by making it enter Download mode.
I Read That Triangle Away Is Very Dangerous
Click to expand...
Click to collapse
Everything that flashes ROM's or works on the formatting of the device's internal storage is dangerous. I have yet to see someone who caused his device to hardbrick by using the app according to it's description.
It only modifies a value in the NAND, nothing much that can really go wrong. A risk always exists with all changes and updates.
Is There Another Way To Reset Flash Counter?
Click to expand...
Click to collapse
Nope
THE.W!ZARD said:
I Read That Triangle Away Is Very Dangerous Is There Another Way To Reset Flash Counter? I Heard That USB Jig Is Not Working For GS3
Click to expand...
Click to collapse
If you're that worried about bricking or avoiding the flash counter... why are you even trying to flash custom roms?
This is a development forum, I'll be the first to admit I have no idea how to develop anything apart from a deep hatred towards in-your-face vegetarians but at least I have a vague idea of what I'm doing, what I can do, and what I really shouldn't even think of doing. I got that from many hours lurking and searching these forums, try it some time.
Sent from my tricked out AOKP GT-I9300
spamcakes said:
If you're that worried about bricking or avoiding the flash counter... why are you even trying to flash custom roms?
This is a development forum, I'll be the first to admit I have no idea how to develop anything apart from a deep hatred towards in-your-face vegetarians but at least I have a vague idea of what I'm doing, what I can do, and what I really shouldn't even think of doing. I got that from many hours lurking and searching these forums, try it some time.
Sent from my tricked out AOKP GT-I9300
Click to expand...
Click to collapse
Because Some ROM's Have Better Performance, Fixing Some Bugs And Bringing Early Updates
d4fseeker said:
It does work, in the way it was intended to do and does across all Galaxy devices; to revive a semi-hardbricked phone by making it enter Download mode.
Click to expand...
Click to collapse
So To Avoid Risk I Should Buy Jig
THE.W!ZARD said:
Because Some ROM's Have Better Performance, Fixing Some Bugs And Bringing Early Updates
Click to expand...
Click to collapse
And you would test all this on a pc how?
It's so ridiculously easy to flash roms these days just flash some and try them out, if nothing bugs you about it tadaa, daily driver.
THE.W!ZARD said:
So To Avoid Risk I Should Buy Jig
Click to expand...
Click to collapse
If you do things right you shouldn't need one, I'd say don't buy it till you need it.
THE.W!ZARD said:
So To Avoid Risk I Should Buy Jig
Click to expand...
Click to collapse
I would, for 2 bucks you might as well, and then if anything goes wrong you don't have to wait to sort it. Having said that in 2 years of flashing and beta testing I have never needed one.Your choice, but flashing this device is simple if you do the necessary reading and follow the guides
Sent from the asylum
It's About If I Want To Reset The Flash Counter To Avoid Warranty Lose That's It. I Flash Omega ROM Before And Flashed Stock ROM Again And Reset Flash Counter Using Triangle Away But I Update The Mobile So It's Not To Use.
How To Restore Stock Kernel?
THE.W!ZARD said:
How To Restore Stock Kernel?
Click to expand...
Click to collapse
Reflash your rom without wiping data.
Sent from my tricked out AOKP GT-I9300
I Really Appreciated Your Help @spamcakes @slaphead20
I personally think that a bunch of people who come across custom roms for their 4.0 galaxy players ask themselves this question, "why aren't there very many roms for my device that are simply flashed through clockwork recovery?" Is it because this device is not very popular? Is it because not very many people know how to put a custom rom in a cwm package? In no way do I want to sound rude, but when I have to flash multiple things onto my device from my computer in order for the tomorto work right as well as not brick my device, it just ruins it for me. There is nothing wrong with roms that require a computer to install, but I personally think that with all those instructions that might not be too clear on what you are support to do, something is bound to go wrong.
Sent from my YP-G1 using xda app-developers app
NATO556 said:
I personally think that a bunch of people who come across custom roms for their 4.0 galaxy players ask themselves this question, "why aren't there very many roms for my device that are simply flashed through clockwork recovery?" Is it because this device is not very popular? Is it because not very many people know how to put a custom rom in a cwm package? In no way do I want to sound rude, but when I have to flash multiple things onto my device from my computer in order for the tomorto work right as well as not brick my device, it just ruins it for me. There is nothing wrong with roms that require a computer to install, but I personally think that with all those instructions that might not be too clear on what you are support to do, something is bound to go wrong.
Sent from my YP-G1 using xda app-developers app
Click to expand...
Click to collapse
This is not that it can't be done, but it the case of ics for the 4.0, it's a bug in the kernel that force us to flash a kernel from heimdall. If this bug was not here, the rom would be simply flashed with cwm. So the answer is it's not because dev don't want to do it like this, it's because they can't.
Couldn't they fix it?
Sent from my YP-G1 using xda app-developers app
NATO556 said:
Couldn't they fix it?
Sent from my YP-G1 using xda app-developers app
Click to expand...
Click to collapse
They don't fix it because they don't know what is broken, this is not a choice. This is not that easy to find what is causing a bug and to repair it. You should be a little more thankful of what you already have because without them there would be no custom rom and no recovery. If you really want it so bad just go ahead and fix it then share it with the dev and they will include it.
ti-pich said:
They don't fix it because they don't know what is broken, this is not a choice. This is not that easy to find what is causing a bug and to repair it. You should be a little more thankful of what you already have because without them there would be no custom rom and no recovery. If you really want it so bad just go ahead and fix it then share it with the dev and they will include it.
Click to expand...
Click to collapse
The problem is that the param.lfs isn't getting updated, probably because their kernel isn't compatible with Samsung's proprietary param.ko (so the bootloader still thinks you're in recovery). If it's not, there's nothing that can be done about it. If it is, they should include that module in the ramdisk. and insmod it with init.rc, and the recovery bootloop will be gone.
Mevordel said:
The problem is that the param.lfs isn't getting updated, probably because their kernel isn't compatible with Samsung's proprietary param.ko (so the bootloader still thinks you're in recovery). If it's not, there's nothing that can be done about it. If it is, they should include that module in the ramdisk. and insmod it with init.rc, and the recovery bootloop will be gone.
Click to expand...
Click to collapse
You seem to know what your're talking about, maybe you could explain this to zaclimon, the last time I tried to help him he was trying to change the onenand driver so the device have the good partirion layout. It would be nice to get rid of that bootloop.
ti-pich said:
You seem to know what your're talking about, maybe you could explain this to zaclimon, the last time I tried to help him he was trying to change the onenand driver so the device have the good partirion layout. It would be nice to get rid of that bootloop.
Click to expand...
Click to collapse
Well, that's part of it too. I think on the 4.0, the problem may be more complicated than that, due to it's storage layout, (I have the 5.0) but rest assured the devs are working on it.
Please let me know when they fix this bug what I need to do from there.
Sent from my YP-G1 using xda app-developers app
Mevordel said:
The problem is that the param.lfs isn't getting updated, probably because their kernel isn't compatible with Samsung's proprietary param.ko (so the bootloader still thinks you're in recovery). If it's not, there's nothing that can be done about it. If it is, they should include that module in the ramdisk. and insmod it with init.rc, and the recovery bootloop will be gone.
Click to expand...
Click to collapse
There's this but mostly because we change the partition (we completely ditch the j4fs support). Also the bootloaders expect to run BML/STL partitions so the bootmode isn't cleared. The thing that teamhackung made is that they created a partition named reservoir that would handle all the bad blocks. This partition is used to flash the boot partition which is the kernel one. This is still an undergoing experimentation for me but I'll try to compile a CM9 with this new type of flashing. An example of the partition layout is here:
https://github.com/CyanogenMod/andr...ung-3.0-ics/drivers/mtd/onenand/samsung_gsm.h
I may miss some things too but this is the things simplified.
Also NATO I do know how you feel about it and I'm trying to do my best (with han and oisis gone) to solve everything as soon as I can. (Don't forget that I have school too )
Sent from my Nexus 7 using Tapatalk HD
Actually most of the GB ROMs for the 4.0 are CWM flashable zips,
http://forum.xda-developers.com/showthread.php?t=1834375
http://forum.xda-developers.com/showthread.php?t=1718339 (older versions)
http://forum.xda-developers.com/showthread.php?t=1821860
http://forum.xda-developers.com/showthread.php?t=1895629
http://forum.xda-developers.com/showthread.php?t=1884557
http://forum.xda-developers.com/showthread.php?t=1719685
http://forum.xda-developers.com/showthread.php?t=1759949 (several ROMs)
http://forum.xda-developers.com/showthread.php?t=1825281
there are 2 or 3 more ROMs that are CWM zips but there based on the OLD CM7 port and with no deep sleep there not worth the time IMO (not the Porting DEVs fault, it was a known issue of the CM7 base).
NOT ENOUGH FOR YOU?
The ones that aren't are because of data corruption issues.
As for ICS, well thats been covered.
Thank you guys for all you do. I really am thankfull to have a website like this one to turn to for help.
Sent from my YP-G1 using xda app-developers app
As soon as the glitch is fixed please let me know. Another question, will there ever be an official CWM release on the player? And will Tardis_Balor update the Terra Silent Kernel once the glitch is corrected?
Sent from my YP-G1 using xda app-developers app
Also, why is hanthesolo's ethereal tomorrow not on this list?
Sent from my YP-G1 using xda app-developers app
rom*
Sent from my YP-G1 using xda app-developers app
BTW, the link for v2.0 of Icy Fusion is dead.
Sent from my YP-G1 using xda app-developers app
I have an I9100 running stock 4.0.3 in portuguese-br. I've never rooted or done anything "illegal" to it.
I'm willing to install CM10, but in the installation page is written:
"Some second-generation Samsung Exynos devices are potentially susceptible to a "superbrick" caused by performing a factory reset with the stock kernel, which effectively kills the internal memory in the device. It is highly recommended you do not perform this operation while using a stock kernel for safety reasons. The install guide assumes the device is already running stock Android 4.x. This device used to be called galaxys2 on get.cm, so older builds of CM can still be found under that title."
I'm running the stock kernel, but i'm also running an stock android 4.x. Is safe to me to install CM10 without changing kernels?
Thanks in advance,
This brickbug appears only at 4.0.4 stock kernel, in some cases. Just don't do anything unwise in stock recovery, but flash a custom kernel with Odin first (a must for rooting anyway). When you've done this, you're safe, and you don't need to worry about it anymore when you're about to flash something from CWM (like CM).
Sent from the Matrix
I would just like to add that rooting/flashing etc is not "illegal" in any way shape or form. It may void your warranty but it is in no way "illegal" so relax. Its like a PC, you can install any OS you want on it, Its your hardware.
TheATHEiST said:
I would just like to add that rooting/flashing etc is not "illegal" in any way shape or form. It may void your warranty but it is in no way "illegal" so relax. Its like a PC, you can install any OS you want on it, Its your hardware.
Click to expand...
Click to collapse
In the US it is now illegal to unlock your bootloader without carrier approval. :x
Sent from my Galaxy Nexus using xda app-developers app
SGS2 bootloaders aren't 'locked' in the first place.
MistahBungle said:
SGS2 bootloaders aren't 'locked' in the first place.
Click to expand...
Click to collapse
Whoops sorry guys.. I get confused with the app I can't even see what forum this thread is in.
Edit: I just figured it out, never paid much attention since I usually go directly to "Participated"
Sent from my Galaxy Nexus using xda app-developers app
thefatalepic said:
In the US it is now illegal to unlock your bootloader without carrier approval. :x
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
No... its illegal in US to unlock carrier network lock. Plus nobody mentioned anything about unlocking. The topic is about rooting/flashing roms.
TheATHEiST said:
No... its illegal in US to unlock carrier network lock. Plus nobody mentioned anything about unlocking. The topic is about rooting/flashing roms.
Click to expand...
Click to collapse
Yes, I completely screwed up on that post didn't even realize what device it was for. I had also just read something putting relating bootloader and carrier but I now know thats utterly and completely wrong. Nothing to do with each other, though I think s-off might.
Sent from my Galaxy Nexus using xda app-developers app
I downloaded a JB update for my Samsung Galaxy S Advance and flashed it via odin but it became slower.
Is it bad to update via odin? If I updated via kies, will my phone be faster?
iso188 said:
I downloaded a JB update for my Samsung Galaxy S Advance and flashed it via odin but it became slower.
Is it bad to update via odin? If I updated via kies, will my phone be faster?
Click to expand...
Click to collapse
In what way did your phone become slower? It is not bad to update via Odin, things are flashed through Odin all the time without any problem. Updating via Kies versus Odin will not make your phone any faster. Let me know if you still have questions I'll be happy to answer them.
As shimp208 stated the answer is most certainly no. Updating with Odin or kies or hiemdal will not in itself make a device slower or worse or whatever, an improper or bad update will do this no matter the method
Sent from my Nexus 4 using XDA Premium 4 mobile app
Some people say that the update is good and some say that it is laggy I don't know Why?
This is why I asked the question. Do you have any suggestion of the reason?
OEMS don't always make the highest quality updates for older or less popular phones, they feel you should be lucky the updated at all
That being said all users experiences differ so what works for one may not work for you, you can always try a full wipe and reflash to see if it helps
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
OEMS don't always make the highest quality updates for older or less popular phones, they feel you should be lucky the updated at all
That being said all users experiences differ so what works for one may not work for you, you can always try a full wipe and reflash to see if it helps
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I did but it do nothing. some people use custom kernels to make it better but they root their phones. Is it safe?
iso188 said:
I did but it do nothing. some people use custom kernels to make it better but they root their phones. Is it safe?
Click to expand...
Click to collapse
Adding on to what demkantor mentioned, it is perfectly safe to root your phone and use a custom kernel provided you follow the proper rooting procedure and kernel flashing instructions and requirements/recommendations included in the kernel thread. There will always be inherent risk with modifying your device but by reading and re-reading the proper instructions and procedures risk is very minimal.
Sent from my SCH-I535 using XDA Premium 4 mobile app
A virus possibility.
shimp208 said:
Adding on to what demkantor mentioned, it is perfectly safe to root your phone and use a custom kernel provided you follow the proper rooting procedure and kernel flashing instructions and requirements/recommendations included in the kernel thread. There will always be inherent risk with modifying your device but by reading and re-reading the proper instructions and procedures risk is very minimal.
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Does rooting increase the possibility of virus infection?
iso188 said:
Does rooting increase the possibility of virus infection?
Click to expand...
Click to collapse
While rooting does not directly increase the possibility of virus infection if your phone is rooted you have full access to your phones file-system operation (With some exception). Although in theory a malicious app could do more damage on a rooted phone, as long as you are smart about what apps you install (You should always use common sense when installing any apps regardless of whether your device is rooted or not) you have nothing to worry about (For example a Tetris game shouldn't need root permission). Overall the risks of rooting - which the vast majority of which can be avoided with common sense - are greatly outweighed by the benefits rooting your device brings.