Related
Check out samdroid,net forums. Rooted kernel by leshak
Ohhh....Yessss....!!!
ohhhh yeah ...but i'm a little afraid atm to try this out .. .
Great news! Don't want to be the guinea pig so someone else has to try it out first.
http://forum.samdroid.net/f49/dev-kernel-i9000-root-lk9-01-beta3-22-06-2010-a-1319/
if you didn't already see it.
step up, guinea pigs, lets see this in action.
sweet!
paul o brian noticed too so maybe he will have a look into it..
now just a matter of time till we get a real f/w with jit, hi mem support etc..
hi mem is really needed as the phone becomes easily sluggish with all the crap that starts running..
rooted already! wow, these guys dont mess around hey
Ferdimage said:
rooted already! wow, these guys dont mess around hey
Click to expand...
Click to collapse
Wich f/w you had before?
Cause i'm having a "I9000XXJF3"...
Regards
Fluxx
Just started coverage and posted an announcement about the root here: Samsung Galaxy S Already Rooted!
Once root access is gained, can the I9000 be unlocked from a carrier?
EDIT: Yes, I9000, I900 is a different phone
Got it workin....
Read howto @ samdroid.net if you need some...
aerofluxx said:
Got it workin....
Read howto @ samdroid.net if you need some...
Click to expand...
Click to collapse
aerofluxx check your pm.
what does rooted version give you advantages over stock?
i find the stock f/w is running very well..
Ferdimage said:
what does rooted version give you advantages over stock?
i find the stock f/w is running very well..
Click to expand...
Click to collapse
Mostly that you can remove stock apps you don't want and you can test improvements in restricted areas (for instance /system and /data) easier.
Also some programs need root access to run; especially those fiddling with settings / performance
One downside to rooting: it gives you the opportunity to break your configuration (not literally). If you remove/alter some files, your system can get unstable or unbootable. Usually you can restore that by reflashing a stock rom or just replacing the edited file by the original
Im now buying !!!!
yes....got my S rooted.
For now, what can be done with a rooted Galaxy S?
looks like ill be staying with tmobile
T-Mobile is a little bit late for this phone + they don't have same GT-i9000 model. (they will have model without front facing camera).
I think fring/skype/facebook video and other IM messangers will become very popular in future. So people will more and more talk over Internet then on GSM. Because in some countries there is 3G flatrate package and also 4g (802.16e WiMAX) will bring us to new era of mobile industry.
kenkiller said:
yes....got my S rooted.
For now, what can be done with a rooted Galaxy S?
Click to expand...
Click to collapse
you can download apps from nexus one section or get your hands dirty on android themes and apps section, and even install cracked android apps and games ... do you know what root means .. like a tree it has root, you can add urea and fertilizers to it to make it grow better and bigger .. same case with this ...
dang dont consider me stupid but lame
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
Good evening all,
Basically I'm looking to root my girlfriends fathers U8800, it's currently running android 2.2. He's complained that its got major battery drain so I figure I can find a ROM here that can help that.
I've read there are 3 different types of models for this handset. How do I know which one we've got? If that's relevant?
I've found this thread that seems dead easy to follow, http://forum.xda-developers.com/showthread.php?t=1420728 , am I ok to proceed?
When I've rooted it, do I just flash a rom via CWM like I would with my galaxy s? And will I be caught out with bootloader issues or little things like that?
Thanks in advance.
If the device is the U8800 regular model(not pro or plus) you can follow the guides of the link.
And yes, you can flash a rom from cwm recovery.
Only one suggestion. If you flash the latest stock gingerbread rom(I think is the 522), search for a thread called "get your pink screen back" on developing section. The after 518 versions have the bootloader locked, and on the above thread you will find how to flash the unlocked bootloader from 518 stock rom.
Thanks for that, I'll get on it tomorrow with an operational head. I'll do the pre root checks and make sure I have everything I need in place before I get going.
dancer_69 said:
If you flash the latest stock gingerbread rom(I think is the 522)
Click to expand...
Click to collapse
It's 528
dancer_69 said:
The after 518 versions have the bootloader locked, and on the above thread you will find how to flash the unlocked bootloader from 518 stock rom.
Click to expand...
Click to collapse
*locked pink screen.
Sent from my GT-P1000 using Tapatalk 2
If the device is not yours I suggest you to do nothing. There's no better Rom, in terms of bug free than the original one.
Custom roms always have this or that and will require attention, which I'm sure your fatherin law can live better without these issues and concerns.
This devices have an high consumption and he has to get used to it.
Now if the device was yours meaning you would be using it daily, than i would advise you to install aurora. I don't like it but have to admit that is very good and stable.
:thumbup:
Sent from Odin's device!
Dave759 said:
He's complained that its got major battery drain so I figure I can find a ROM here that can help that.
Click to expand...
Click to collapse
Did you look to see what is causing the battery drain? I have a friend with a stock GT540 that had serious battery drain. Turns out it was the GoSMS program. Deleted the app and now his phone lasts 5 days between charges. Switching a rom won't help if the problem is an app.
1) Get cpu spy and see if it is going to deep sleep
2) If not sleeping, turn off running applications one by one and test via cpu spy to find out which one is causing it not to sleep.
3) Either remove the offending app or use Autorun Manager to modify the receivers (if rooted)
You can fix his problem without changing his rom. If he wants root, superoneclick can root 2.2, I just used it the other day. Also make sure he is on the latest 2.2: b138sp04 or b163. I prefer b163, even though it is the China rom, because I like the Huawei launcher better that stock.
A.C.A.B. said:
If the device is not yours I suggest you to do nothing. There's no better Rom, in terms of bug free than the original one.
Custom roms always have this or that and will require attention, which I'm sure your fatherin law can live better without these issues and concerns.
This devices have an high consumption and he has to get used to it.
Now if the device was yours meaning you would be using it daily, than i would advise you to install aurora. I don't like it but have to admit that is very good and stable.
:thumbup:
Sent from Odin's device!
Click to expand...
Click to collapse
That's not true... official 2.2 is the slowest thing in existence. If he just needs stability then Ezets CM7 is the answer. There are no bugs with it (except wifi tethering) and it's much much faster than stock...
Also he can undervoltage it to preserve battery life more than stock ROM.
Sent from my U8800
You want the best 2.2 you try Void Eridanus. Everything works.
Want the speed, OEX rom it's a Ferrari. Everything works less the mms with data off.
You can also keep the stock Rom, root it and just apply a ffranco kernel. This way you gain the speed.
3 good solutions here.
I'm don't revert to stock Rom for 2 reasons, cam quality and battery life, otherwise i would use stock Rom without a shadow of a doubt.
In terms of stability and all working it's stock 2.2 Rom and this is unquestionable!!!
I have been trying ALL roms and ALL respective versions since July 2011 therefore I do speak by personal extended experience
I repeat once again, in the conditions you mention leave the phone as it is. If you want to do something just root it and that's it.
as a matter of facts i had my phone with so many rooms that i can even say how many but if u want stability i recomend oxygen... if u want stability and good looks use miui 32...
last .32 miui that i used was from miui portugal in english and nothing to say about that...
battery for 2 days and all smoth...
but my phone is weird... he can take almost every rom and be usable...
The issue with miui pt versions it's the cam quality that is horrible. It's just this detail that it's not very good. The rest it's perfect.
Sent from Odin's device!
Hey everyone, back for an update and some other steps. basically, he got frustrated with how the battery so he went out today and bought the newer huawei. Reading eveyones comments here i think its due to the ammount of apps and being on froyo hasn't helped any thing, but anyways its now my new toy to play with. So far, followed the link i posted in the first thread, rooted and installed the latest CWM (v5). I'm now a little confused when it comes to the get the pink screen back, should i follow this thread http://forum.xda-developers.com/showthread.php?t=1457490 now before flashing a new rom or afterwards?
Again thanks for all the help, I'm almost done bothering you all for now
Edit: Reading on some ROM's and the comments above, i should install B518 stock ROM then flash the bootloader fix from the thread posted above then i can install other ROM's? If so where can i get the stock B518 ROM and how do i know which version I'm using? Sorry and thanks again.
First, which rom you have now?
You can find the version from settings -> about phone.
If you have a newer than 518 version you need to change the bootloader with the one from 518. If you have 518 you don't.
Also check which version of kernel you have(is on about phone also)
If you have a 2.6.32 version(which mean that you have froyo rom), you can flash only roms with this kernel version. If you have a 2.6.35 version, you can flash roms with 2.6.35 kernel or 3.0.8(as aurora ICS).
Basically its a stock froyo rom, im looking to get to gingerbread by the end of tonight but currently im stuck on the huawei splash screen after i did a data reset in CWM. Can still get to CWM though.
What rom you want to flash now?
A custom gingerbread based of froyo's kernel 2.6.32 like CM7.2, oxygen or miui, or the official gingerbread?
Im not particularly bothered, something that won't brick the phone and is stable. I'm more worried as to why it wont boot now after a data reset.. any suggestions for that?
You can use adb and logcat function to see where the problem is. Usually when some errors prevent device to complete the boot proccess, this piece of code loops. You need to have some knowledge of programming though, but maybe is something easy.
and now i have blue screen.. what can i do? or have i bricked it?
Where you have blue screen and what you did?
Usually blue screen instead of recovery mode, means that the recovery.img is deleted from .cust_backup/Image folder
basically, i formatted something, reboot and soon as the huawei logo appear a blue scrren rolls down. when i plug the phone into the pc it detects a folder but its empty, the phone is detected as qualcomm now..
Yes, seems that you formated the partition which has the Image folder with all system images. So, now you need to flash an official rom. You can either flash a froyo or a gingerbread rom. You can avoid this only if you previous had take a backup of this folder. In this case just put all files in (empty now) image folder.
Hey everybody I was just wondering if it was worth to do it...
Will the overall performance of my tablet be affected to better?
I have some small experience with rooting and installing new roms on my phone, (epic 4g touch) but i know nothing of rooting and installing new roms to tablets.
Thanks
Sent from my A500 using XDA Premium HD app
No answer? Helloooo somebody out there lol?
Sent from my Epic 4G Touch on Codename JoyRide using xda Premium.
Hi, and welcome!
First sorry that you waited so long for a response. It's been a slow Sunday at XDA as far as I can tell.
And it's kinda difficult to give you an answer that everyone would agree with. But I'll give you my take on it. You could change out the words "Why do I" for "Is it worth it" in the following if you like.
Why do I root my tablet? Mainly for bootanimations, system tweaks, like the gps fix we used to have to use to get the gps even marginally functional (That's not an issue anymore, so no worries). I also like to mess with very noobish mod attempts. Noobish, but it makes me smile when I do something neat. Things like that. There are plenty more reasons but I think that should reflect the gist of it.
Why do I unlock my devices (read; install custom bootloader in this case.) and install custom roms? Mainly because of neat features that are above and beyond what the manufacturer includes. For instance the Acer Ring (Some like it, some don't.). as well as tweaks already performed by the chef, like that gps fix I mentioned. Then there is overclocking and the custom kernels.
I'm sure that you probably already know all of this, and while our tablet is really great stock and will do just fine. I think that it is improved using a custom rom. Plus, since it is a tablet rather than a phone, it isn't as critical if something goes wrong when you are goofing around installing the rom or unlocking. No one wants a brick. But it's gotta be a little less of a major problem on a tablet than a phone.
The only real downside of installing the custom bootloader that I know of would be that some users (including myself.) report a flicker and the homescreen going blank on rare occasion and the icons dissapear, but restarting the launcher fixes it. Just put a shortcut in the lockscreen to a home switcher. Thanks to loth77 for that tip. But it isn't something that everyone gets and it's not that big of a drag. I can't really think of any other negatives.
Here's probably the most important thing that you should remember. Get your CPUID in case something goes wrong. The tab is bulletproof if you have that. Here's a link to help understand the whys and hows.http://forum.xda-developers.com/showthread.php?t=1624645. Remember to get the drivers from acer, and if something doesn't work try changing usb ports, usb cable, or even the pc.
That should pretty much be the long and short of it. Hope it helps. And good luck.
Hey thanks a lot, I think I might root it, Im familiar with flashing roms but the Bootloaders are new to me, can you tell me why do I need to unlock it to install a rom?
Sent from my Epic 4G Touch on Codename JoyRide using xda Premium.
If I understand the process correctly it is something about the way that the bootloader does its security checks. If you have a stock bootloader it looks for the stock rom only. If it doesn't find a rom/kernel that it expects you get to see the android on it's back. The custom bootloader doesn't mind a custom rom. If you want a technical answer maybe someone smarter than myself could explain it better. But I think that is pretty close.
JdgM3NT4L said:
If I understand the process correctly it is something about the way that the bootloader does its security checks. If you have a stock bootloader it looks for the stock rom only. If it doesn't find a rom/kernel that it expects you get to see the android on it's back. The custom bootloader doesn't mind a custom rom. If you want a technical answer maybe someone smarter than myself could explain it better. But I think that is pretty close.
Click to expand...
Click to collapse
And you said it, more or less
With ICS, the bootloader and boot.img communicate. A lot. Neither wish to run properly as they should. In the beginning, we hacked the ICS kernel to run on an HC bootloader. It worked and gave system somewhat RW, but is was crappy to say the least, and caused display irregularities on boot, and sometimes during operation. But when Skrilax_CZ started working on the ICS Bootloader, we could run an ICS kernel, and still get somewhat root and /system RW. But the RW was crappy, and required re-mounting /system all the time.
Having root, without /system RW, is like having a hamburger without the burger. Yeah, it kinda looks like it, but still....
Thus the "tweaked" ICS boot.img came out. Basically the same kernel, but the Zimage has some mods to it. Namely changing the part that prevented RW. And thus, the fully unlocked, fully RW system came out. And technically, you don't need busybox. Just SU. But busy box has to be there for other deals.
So now, to get the full unhindered benefit of both worlds, it's required to change bootloaders. We can do this via NVFlash, because we have the Secured Bootloader Key algorithm (SBK).
Also, HC based Roms WILL NOT run on the ICS bootloader, locked or unlocked. So if ya wanna play ball in our park, ya hafta play by our rules.
You can get your root under a stock ICS bootloader, but, you will have issues with system RW. This I promise.
Also with the unlocked bootloader, you get "fastboot" functions. Consider it your last line of defense. But for those that know how to use it, it's better than flashing certain things.
MD
For what this is worth, as a total noob to all this I decided to try the custom bootloader. Knowing from bricking a Wii once, I made a nand and a rom backup, got my CPUID using blackthund3r's ACER manager for those using ICS (just an incredible thing), and got to work.
I made an error and got hung in APX mode and initially I had at least three heart attacks when I thought I'd bricked; however I figured there had to be a way out as tablet still came on and I had done all the above. Reran Acer manager, changed my previous decision, and soon (within 5 mins) boatloader patched. I've since tried so many roms I've lost count.
Regrets? Not one. It's faster and better. Reading this thread, however, and learning that with a CPUID the tablet is bulletproof makes me feel even better! If you're a noob like me, it's a little scary, but backup, get a nand and the CPUID, Acer Mgr, follow the directions and go for it. After all I went through, if I can do it, so can you!
Yeah I flashed a rom already seens to be working great, i dont have much time right now to mess around with it but its definally better fellows, thanks
Sent from my Epic 4G Touch on Codename JoyRide using xda Premium.
The objective of this thread is to have all the knowns issues and known (or potential) fixes for the I9300 in an OP.
Latest Updates
- What to do if you only want warranty
- Updated CF-Auto-Root
- Perseus Kernel patched
Universal
There are mainly two major issues I've found around the forums: Exynos Root Exploit and Sudden Death (eMMC failure).
Exynos Root Exploit
alephzain said:
Recently discover a way to obtain root on S3 without ODIN flashing.
The security hole is in kernel, exactly with the device /dev/exynos-mem.
This device is R/W by all users and give access to all physical memory.
Click to expand...
Click to collapse
It was fixed by Samsung in the XELLA/XELLC kernel.
Stock ROMs collection.
Sudden Death
Sudden Death Syndrome (SDS): Some S3 devices which have a faulty eMMC chip seem to just die. Most victims have found their phone completely unresponsive while taking it out of charge. Some have managed to boot into download mode but are unable to flash any ROM (presumably because the NAND is already damaged).
There are two theories of this: both are explained below:
rlorange said:
Guys we don't know enough to say for sure that previous faulty wear leveling has already dine damage.
According to the best informed guess by Entropy, the faulty wear leveling firmware causes a brick only when it decides to move critical data to fresh block which DOESN'T EXIST.
Wear leveling works by keeping track of read/write cycles for data blocks. The faulty emmc controller is guessed to have a bad block address move as part of it's wear leveling which causes the failure.
There is no evidence that the brick happens because of too many read/writes in one place which eventually fails (Theory 1). Rather if and when the wear leveling controller moves a block there is a bug which screws this up somehow (Theory 2).
Assuming the kernel patch prevents the emmc wear leveling code from triggering the buggy block move then it really will prevent the affected NAND chips from ever failing.
We don't yet know for Sure but Entropy seems to think that the failure event is triggered during normal wear level block moving which goes wrong and does the damage then. Not the other scenario of the wear leveling actually never moving blocks thus after time eventually "wearing a block out" due to too many read/write cycles.
Click to expand...
Click to collapse
rootSU said:
The "Sudden Death" issue is caused by firmware on the (16 GB) VTU00M, revision 0xf1 eMMC (Embedded MultiMedia Card or internal memory if you like). Samsungs Kernel Source Code (Update 7) has been identified as the fix.
Click to expand...
Click to collapse
Appropriate fixes found in the OP.
NOTE
A lot of people seem to be confused about this: there are effectively two kernels that need to be patched: the obvious one: which Android runs on, and also the less obvious recovery.
- If you are running stock, flashing LLA onwards is enough to prevent further NAND damage
- If you are running a custom ROM or flashing a custom recovery, make sure you flash a patched recovery!
As of 14th January 2013:
EViollet said:
You have 3 different software parts on the GS3:
* bootloader
* recovery
* rom
The bootloader appears not to have the fix. NO bootloader is currently known to have the fix. So, any version will do. It won't protect you.
There is currently ONE known recovery that includes the kernel that fixes the SDS : philz recovery. No more.
ROM. This is what you're running on your phone. It comes bundled with a kernel. The SDS fix is included in the kernel. If you use the latest Siyah kernel, then you're safe. Up until the moment you boot recovery. Then you depend on the recovery you currently have on your phone.
Siyah kernel, however, has a peculiarity: it comes bundled with it's own TEMPORARY recovery that is used to manage 2 ROMs.
If you reboot in recovery from the Siyah STweaks tool, then you'll be using the Siyah recovery, which is correctly patched.
If you reboot in recovery from the ROM (or any other means of rebooting to recovery), you'll be back on your default recovery.
You can also "hijack recovery" from the Siyah STweaks tool. This will overwrite your current recovery with the Siyah recovery. And you will be protected whichever means of rebooting to recovery you choose.
Click to expand...
Click to collapse
rootSU said:
For those who don't care about being "safe" and only care about warranty, the step is simple.
Step 1: Do nothing
For those who don't care about being "safe" and only care about warranty AND are rooted
[Step 0: Flash ICS sboot]
Step 1: Reset flash counter
Step 2: Flash stock ROM [flashing patched firmware should make you "safe" too]
Click to expand...
Click to collapse
As of now ClockworkMod recovery is not patched.
Use PhilZ recovery instead.
Siyah kernel has been patched.
rootSU said:
Chainfire has updated to the ELLC recovery in Cf-auto-root
Click to expand...
Click to collapse
Update:
Patched Perseus Kernel
AndreiLux said:
Perseus alpha31 (09/01):
Removed my own security fixes and replaced them with the official Samsung one. I guess it can now be disclosed: exynos-mem was only one of multiple entry-points for the memory exploit. We discovered the s5p-smem exploit ourselves back in December but kept it quiet, I fixed that one back in version 29.2 without mentioning. Nobody was secure from a smart exploiter up until then, SuperCurios or Chainfire's software fixes are also just patching a single hole in what is a Swiss cheese. Kernels >v31 and beyond stock LLA are now the only truly protected ones.
Samsung's fix for the sudden death syndrome (SDS) included. It is caused by eMMC failure on phones with VTU00M internal memory chips with revision 0xF1. You can check your phone with the "eMMC Brickbug Check" in the Play Store (Ignore the message if it says you're not affected, the type and revision is what matters). The patch is a firmware soft-patch that is applied on every boot and MMC resume, it is not a permanent fix. You will need to stay forever on kernels which include the patch, this also includes updated recoveries and their embedded kernels.
Some other minor MMC changes extracted from Update 7 sources.
Click to expand...
Click to collapse
Bootloader Exclamation Mark
Apparently after flashing LLA bootloader, the red exclamation mark notoriously keeps reappearing unless you follow very specific steps, involving TraingleAway, recovery and ODIN flashing.
Original thread
EdgaBimbam said:
To start with, I'm flash addict and always trying to flash new roms/firmwares. However after flashing one of the newest samsung firmware i got this little red exlamation mark
Click to expand...
Click to collapse
Thread listing workarounds
Android 4.2 (CyanogenMod 10.1)
NFC Fix
It seems most devices coming from Stock Jellybean 4.1 to JB 4.2 are facing broken NFC. The current considered permanent solution is to:
1) Take a Nandroid backup
2) Flash a stock 4.0 ROM
3) Switch on WiFi and NFC
4) Restore from Nandroid
There is also a separate fix for CM10.1. ONLY apply the fix if your NFC is not working.
View attachment NFCFix.zip
Official CM10.1 discussion thread
Note: Not sure if this is a CM-specific issue. Let me know if that is the case.
don't you mean devices coming from Jellybean 4.1 to Jellybean 4.2? coming from ICS to JB 4.2.1 doesn't have the issue with NFC.
just checking.
EDIT: minor typo fixed.
you can add the downgrade from LLA bootloader to avoid the red exclamation mark..
''It seems most devices coming from Ice Cream Sandwich to Jellybean 4.2 are facing broken NFC.''
I think you meant devices coming from STOCK Jelly Bean to CM10.1 are facing the NFC problems
thegh0sts said:
don't you mean devices coming from Jellybean 4.1 to Jellybean 4.2? coming from ICS to JB 4.2.1 does have the issue with NFC.
just checking.
Click to expand...
Click to collapse
erto90 said:
you can add the downgrade from LLA bootloader to avoid the red exclamation mark..
Click to expand...
Click to collapse
PLUG313 said:
I think you meant devices coming from STOCK Jelly Bean to CM10.1 are facing the NFC problems
Click to expand...
Click to collapse
Done!
me thinks the NFC issue exists is because of the updated firmware in stock JB 4.1 and for some reason it can't communicate with CM10.1.
you can add my "KeepRil" zip if you like ... http://forum.xda-developers.com/showpost.php?p=35790900&postcount=1069
75markus said:
you can add my "KeepRil" zip if you like ... http://forum.xda-developers.com/showpost.php?p=35790900&postcount=1069
Click to expand...
Click to collapse
Is it a fix to a known issue of this phone? My understanding was that you need a matched RIL and Modem no matter what, i.e., it's not an "issue" as such, it's a technical constraint.
what about sdcard0/0 ... 0 issue ?
is not a real issue , i know , is just the way should be when running CM 10.1 Android 4.2.1
i think people found difficulties to understand how it works and how to deal with it in view of reverting to a Sammy Rom ... etc
i opened a thread in Q&A but i`m not sure if is complete or/and helpful enough
have a look please :angel:
http://forum.xda-developers.com/showthread.php?t=2075162
xanthrax said:
what about sdcard0/0 ... 0 issue ?
is not a real issue , i know , is just the way should be when running CM 10.1 Android 4.2.1
i think people found difficulties to understand how it works and how to deal with it in view of reverting to a Sammy Rom ... etc
i opened a thread in Q&A but i`m not sure if is complete or/and helpful enough
have a look please :angel:
http://forum.xda-developers.com/showthread.php?t=2075162
Click to expand...
Click to collapse
As far as I recall, It's an Android 4.2 "feature" (or issue, whatever way you look at it), not really specific to either CM or the I9300 device in particular.
pickandwhammy said:
As far as I recall, It's an Android 4.2 "feature" (or issue, whatever way you look at it), not really specific to either CM or the I9300 device in particular.
Click to expand...
Click to collapse
is this from your signature ?
ROM: CyanogenMod 10.1 (Android 4.2.1) Latest Nightly
don`t you have this sdcard 0 feature ?
of course is not specific to sg s3 but is specific for a ROM available for sg s4 ...
you confused me ... i`ll think about it ...
xanthrax said:
is this from your signature ?
ROM: CyanogenMod 10.1 (Android 4.2.1) Latest Nightly
don`t you have this sdcard 0 feature ?
of course is not specific to sg s3 but is specific for a ROM available for sg s4 ...
you confused me ... i`ll think about it ...
Click to expand...
Click to collapse
What I meant was it's a Google feature, which turns out to be not-very-user-friendly on phones (as opposed to tablets). It's not an issue with the device, be it hardware or firmware.
KERNEL issue or bootloader ?
pickandwhammy said:
The objective of this thread is to have all the knowns issues and known (or potential) fixes for the I9300 in an OP.
Exynos Root Exploit
It was fixed by Samsung in the XELLA/XELLC bootloader.
Click to expand...
Click to collapse
I thought Exynos bug was solved by KERNEL fix (XELLA , Perseus) .... NOT bootloader ??
could you please confirm ,
Thks
Got my answser : the exynos fix is in the kernel NOT in the booloader ...
philgalaxs3 said:
Got my answser : the exynos fix is in the kernel NOT in the booloader ...
Click to expand...
Click to collapse
Please post the thread/post URL elaborating on that, I'll update the first post with it.
pickandwhammy said:
Please post the thread/post URL elaborating on that, I'll update the first post with it.
Click to expand...
Click to collapse
Thks for the post update . But sorry I don't understand your "thread/post URL" remark ? seems Im on the correct thread and no need any URL ?
philgalaxs3 said:
Thks for the post update . But sorry I don't understand your "thread/post URL" remark ? seems Im on the correct thread and no need any URL ?
Click to expand...
Click to collapse
Okay. I thought the bootloader was initially believed to be the fix, and then the kernel, so I guess it was my misunderstanding. Since I've never run stock, I've never had any first-hand experience
Okay ! Not easy to know everything ! and thks again for your compile post :good:
Thanks
Sent from my GT-I9300 using xda app-developers app
Hello, first thanks alot of ur topic giving us solutions to protect our phones from SDS , but i wanna add something , there is another patched kernel beside Siyah one, its Perseus kernel .
Envoyé depuis mon GT-I9300 avec Tapatalk