Well I am not new to android and xda but still finding it a bit confusing when it comes to deciding what to do.
Can we please have a simple insteuctions for some one like me who only wants
A Root
B Exynos fix
C SDS sw fix and sds fix for recovery
D Battery life just like on 4.1.1
As stock as possible.
With instructions would be just marvellaus.
Sent from my GT-N7100 using xda app-developers app
A. Read post#2 of this
B & C : already fixed on stock ROM released in jan13 and later (OR LL7 and later) read post#1 of above said thread for ROM available
D.Latest ROM have almost nice battery management almost like 4.1.1
Thanks for the quick answer so I am ok to flash Turkey latest rom on to my Uk BTU phone?
And which is the safest sds fixed recovery?
Sent from my GT-N7100 using xda app-developers app
all latest recovery, including turkey feb released bekieved to be patched, as you know samsung never gives changelog or utter a word regarding bug, but some elite developer saying it.
you can flash that ROM .
dr.ketan said:
A. Read post#2 of this
B & C : already fixed on stock ROM released in jan13 and later (OR LL7 and later) read post#1 of above said thread for ROM available
D.Latest ROM have almost nice battery management almost like 4.1.1
Click to expand...
Click to collapse
my friend has upgrade his rom to the latest
but when he check his phone with brickbug check, the note-II suddent death? still say "yes, insane chip"
emmc chip
type:VTU00M
fw Rev 0xf1
tabone said:
my friend has upgrade his rom to the latest
but when he check his phone with brickbug check, the note-II suddent death? still say "yes, insane chip"
emmc chip
type:VTU00M
fw Rev 0xf1
Click to expand...
Click to collapse
No update would be able to change your emmc chip physically(Hence no change in emmc chip name).
It is believed that the wear level bug has been patched in the new updates.
tabone said:
my friend has upgrade his rom to the latest
but when he check his phone with brickbug check, the note-II suddent death? still say "yes, insane chip"
emmc chip
type:VTU00M
fw Rev 0xf1
Click to expand...
Click to collapse
Read above post
Does fixing with software can change your hardware?
your chip is faulty and will remain faulty ever unless you change motherboard
Patching just stops issuing commands which believe to cause SDS.
Related
Hi guys, I have been recently reading a few Note 2's dying of SDS (Sudden Death Syndrome). This has affected previous Galaxy S3 phones, and now some versions of Note 2.
========= Note: This is different from the exynos bug ==========
To check, install "eMMC Check" from google play and run it. Disregard the message saying Brick bug = No. Sane chip, and look at your eMMC chip type and FWRev.
If your:
Type: VTU00M
FwRev: 0xf1
your phone is affected by the bug.
I have read that Andreilux's Perseus kernel V31.2 (Perseus alpha31 (09/01)) temporarily repairs this bug. I am running his kernel anyway. But my question is, how many of you guys have the above chip?
AndreiLux said:
It does include the fix but otherwise they're outdated, same story as on the S3.
Updated to 31.2; same changes as on the S3:
Samsung's fix for the sudden death syndrome (SDS) included. It is caused by eMMC failure on phones with VTU00M 16GB 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.
Click to expand...
Click to collapse
Perseus kernel thread:
http://forum.xda-developers.com/showthread.php?p=36552266#post36552266
==============================================================
Updates and useful links:
UK/EU Samsung repair: free samsung repairs
I spoke to these guys this morning asking about the free postage on their site, according to them, postage is free but they are not tracked, and they advised me to use a recorded/insured postage.
Does that mean if i install that kernal i will be safe if so please post the link to that kernal
Sent from my GT-N7100 using xda premium
Auch. Looks like mine is also affected. But doesn't the last update solve the problem ? (XXDLL7)
Mine is also affected :/ are you sure though ??
Sent from my GT-N7100 using xda premium
To be on the safe side install the kernal stated on the owl74's post.Below is the link to the custom kernal original post :
http://forum.xda-developers.com/showthread.php?t=1927852
Sent from my GT-N7100 using xda premium
thanks whit3h4awks.
I have updated the op with AndreiLux's statement and posted the thread to his kernel.
But according to my knowlegde I think still you wont be safe while you are on recovery mode.
"A developer please confirm this"
Sent from my GT-N7100 using xda premium
owl74 said:
Hi guys, I have been recently reading a few Note 2's dying of SDS (Sudden Death Syndrome). This has affected previous Galaxy S3 phones, and now some versions of Note 2.
To check, install "eMMC Check" from google play and run it. Disregard the message saying Brick bug = No. Sane chip, and look at your eMMC chip type and FWRev.
If your:
Type: VTU00M
FwRev: 0xf1
your phone is affected by the bug.
I have read that Andreilux's Perseus kernel V31.2 (Perseus alpha31 (09/01)) temporarily repairs this bug. I am running his kernel anyway. But my question is, how many of you guys have the above chip?
Kernel thread:
http://forum.xda-developers.com/showthread.php?p=36552266#post36552266
Click to expand...
Click to collapse
My phone is affected, having the exactly same type and firmware rev. I'm using it since October 16 until now and so far it never failed me. I've been flashing countless ROM and kernel and touch wood so far it still working fine
whit3h4wks said:
But according to my knowlegde I think still you wont be safe while you are on recovery mode.
"A developer please confirm this"
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
read the last sentence that I quoted in the op...
Thank you, guess I missed that part.
Sent from my GT-N7100 using xda premium
Type:-VTU00M
FR:0xf1
:/
Seems like everybody has the same chip. Anybody here who has a different type and fwrev?
Okay installed the Perseus kernel. Fingers crossed it doesn't get bricked in Recovery mode as I'm frequently trying out roms in cwm.
Sent from the Rabbit Hole
What do you recommend for flashing - cwm or twrp.....I just red that twrp was updated that soft patch for SDS so i guess it wouldn't be a problem with flashing through it....
I now have cwm 6.1.5 and i guess it's not patched because its rather old (2-3 months).....But i just want to know is twrp as good as cwm - never used it
Either use the official 4.1.2 or the v31 from perseus to avoid the SDS, correct?
Are there any reports of SDS on the Note 2 to begin with ?
denied1977 said:
What do you recommend for flashing - cwm or twrp.....I just red that twrp was updated that soft patch for SDS so i guess it wouldn't be a problem with flashing through it....
I now have cwm 6.1.5 and i guess it's not patched because its rather old (2-3 months).....But i just want to know is twrp as good as cwm - never used it
Click to expand...
Click to collapse
I'm using TWRP now coming from CWM...they're both good at doing what they're advertised to do...although twrp has extra options and looks a bit better as the keys are larger and fill the entire screen and it has a file explorer and allows you to backup you're entire phone either on the internal or external memory sort of like an image of a hard drive on my computer.
Sent from the Rabbit Hole
Well, it's too bad that we can't flash the desires ROMs and kernels. Is CM10 safe?
I just flashed stock ROM XXDLL4, rooted and reset counter. If it dies, I hope it will die as soon as possible so I can get rid of it. I can't take the risk of losing 600€ because Samsung are making buggy smartphones. I'm right now forced to stay on stock, just to not lose warranty.
However, are you guys 100% sure the bug is fixed in XXDLL7 and Perseus kernel?
ionutzm05 said:
Well, it's too bad that we can't flash the desires ROMs and kernels. Is CM10 safe?
I just flashed stock ROM XXDLL4, rooted and reset counter. If it dies, I hope it will die as soon as possible so I can get rid of it. I can't take the risk of losing 600€ because Samsung are making buggy smartphones. I'm right now forced to stay on stock, just to not lose warranty.
However, are you guys 100% sure the bug is fixed in XXDLL7 and Perseus kernel?
Click to expand...
Click to collapse
That's what they say in the perseus kernel thread.
Anyway here is link for latest TWRP recovery for note 2:
http://teamw.in/project/twrp2/115
It apear I have the bad chip
Well I have mi GS not II since december 31, and it apear I have the bad chip, but my question is I read about the lasted kernel LL7 corrected the problem, but I live in Mexico and last night I have a update to my kernel to version LL3 is this the same versión of LL7 but the 3 is for latin america?
thanks in advance
I have just ordered an Unlocked Version here in the UK. Do you think I may be effected by this bug?
whit3h4wks said:
Thank you, guess I missed that part.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Mine's 0xf7, but it's an N7105 so might be why.
people who bought the cellphone from germany have the bug ? and the emmc VTU00M
FwRev: 0xf1?
Blazy56 said:
people who bought the cellphone from germany have the bug ? and the emmc VTU00M
FwRev: 0xf1?
Click to expand...
Click to collapse
It doesn't matter where your phone comes from.
If it has this chip:
emmc: VTU00M
Rev: 0xf1
it is affected and needs to run safe kernels/recoveries that include Samsung's fix.
If it's 0xf7, or not VTU00M at all - it's considered to be safe as there was no instance of SD issue on those chips.
Akiainavas said:
It doesn't matter where your phone comes from.
If it has this chip:
emmc: VTU00M
Rev: 0xf1
it is affected and needs to run safe kernels/recoveries that include Samsung's fix.
If it's 0xf7, or not VTU00M at all - it's considered to be safe as there was no instance of SD issue on those chips.
Click to expand...
Click to collapse
so the note 2 have this bug too ?
and what does it mean safe kernels?
Blazy56 said:
so the note 2 have this bug too ?
and what does it mean safe kernels?
Click to expand...
Click to collapse
AFAIK, and for the international version (GT-N7100) safe kernels are :
Samsung stock kernel version LL7 and beyond.
Perseus alpha 31 and up
Redpill 1.01 and up
NEAK 1.4 and up
As for the recoveries the only safe one is TWRP 2.3.3.1 and up (current version is 2.4)
Androssama said:
AFAIK, and for the international version (GT-N7100) safe kernels are :
Samsung stock kernel version LK7 and beyond.
Perseus alpha 31 and up
Redpill 1.01 and up
NEAK 1.4 and up
As for the recoveries the only safe one is TWRP 2.3.3.1 and up (current version is 2.4)
Click to expand...
Click to collapse
and this will fix the problem?
Blazy56 said:
and this will fix the problem?
Click to expand...
Click to collapse
If you have the mentioned chip (VTU00M rev 0xf1) you need to be running two things : a kernel and a recovery that contain the fix. Then you'll be as safe as it can be at the moment.
Androssama said:
If you have the mentioned chip (VTU00M rev 0xf1) you need to be running two things : a kernel and a recovery that contain the fix. Then you'll be as safe as it can be at the moment.
Click to expand...
Click to collapse
I have perseus kernel ... I thought thats enough... And i have 4.1.2 stock ...
Laynee1 said:
I have perseus kernel ... I thought thats enough... And i have 4.1.2 stock ...
Click to expand...
Click to collapse
On top of that need a recovery that contains the fix!
how could I check if I have a VTU00M memory chip?
From emmc check from play store
Sent from my GT-N7100 using xda app-developers app
im safe
Hi,
Recently I got to know about the freezing problem of some Note 2 and how we could find out weather we have the same chip.
I used the app eMMC Check and below is the eMMC Chip details :-
eMMC Chip
Type: VTU00M
Date:08/2012
CID: 15010056545530304df1e83451558fcf
FwRev: 0xf1
So, basically I have the same chip as the one known for having the issue.
I have my warranty but I never had any issue yet.
How am I supposed to know if its a defected chip ? (if possible, without rooting please)
In case yes, what am I supposed to do ?
Bdw, here is the firmware and kernel version :-
Model Number
GT-N7100
Android Version
4.1.2
Baseband Version
N7100DDDLK6
Kernel Version
3.0.31-679347
[email protected]#1
SMP PREEMPT Mon Feb4 09:47:52 KST 2013
Build Number
JZO54K.N7100XXDMB2
You could try reading one of the many existing SDS threads instead of starting a whole new one...
Actually I did read. But I didnt get a response for what exactly one should do if he's got the same chip while no freezing issue is being witnessed.
Sent from my GT-N7100 using xda premium
Well, what do you expect to be able to do? Samsung aren't going to replace your device until it craps out.
There is plenty of information in the threads about how to protect yourself. Basically, flash a 4.1.2 ROM which has a workaround in it. Of course, there are some reports of it still happening on those ROM's as well, but nothing confirmed as yet.
Since you have 4.1.2, you won't have sds.
Sent from my GT-N7100
Thanks a lot. I can live in peace now.
Sent from my GT-N7100 using xda premium
Hello everyone~
I was planning to by the Ruby wine version of Galaxy note 2 n7100 but I kept getting worried about SDS since the phone boxes here doesnt show the manufaturing date on the box.
So I was thinking of buying the LTE Pink n7105 version.
Am I safe from sds if I get the n7105 one?
I need your opinion guys~
:fingers-crossed:
There are patches here on the forum to prevent SDS. And some say you just need to update your firmware to 4.1.2, cause it has a patch to prevent SDS too.
Anyway, search around about SDS and the patch. And if you think you can apply it, go for the GT7100.
Sent from my GT-N7100
ROM: ARHD 19
KERNEL: Stock
only the 16gb version is affected with SDS. but the 'ruby wine' colour option will be safe i think because only early batch of n7100 is affected. nevertheless,buying n7105 would be safe too.
laziafbaito said:
There are patches here on the forum to prevent SDS. And some say you just need to update your firmware to 4.1.2, cause it has a patch to prevent SDS too.
Anyway, search around about SDS and the patch. And if you think you can apply it, go for the GT7100.
Sent from my GT-N7100
ROM: ARHD 19
KERNEL: Stock
Click to expand...
Click to collapse
as far as I know..this is a hardware chip bug..the patches or fixes just perform some sort of skipping or ignoring a section like some memory address but that is done by the kernel...if you flash another ROM which most likely will have a different kernel chances are the phone will be bricked !!! and the only solution is to send it to Samsung repair store... for a mother board replacement probably which means...just buy another phone !!! that's if your not in warranty
Sent from my GT-N7105 using Tapatalk 4
---------- Post added at 03:12 AM ---------- Previous post was at 03:03 AM ----------
4everadumbangel said:
Hello everyone~
I was planning to by the Ruby wine version of Galaxy note 2 n7100 but I kept getting worried about SDS since the phone boxes here doesnt show the manufaturing date on the box.
So I was thinking of buying the LTE Pink n7105 version.
Am I safe from sds if I get the n7105 one?
I need your opinion guys~
:fingers-crossed:
Click to expand...
Click to collapse
I'm using the N7105 it didn't have the bug.... I don't think this model is affected but if it is then it's rare...this model is better anyways as it supports LTE which is the fastest cellular data/internet connectivity on the planet ryte now.... the only problem with this model is if you planning to flash custom ROMs ALWAYS backup your EFS else you can flash a ROM and may replace/destroy your modem/network portion of your phone...as most ROMs are ported from other variants and devs may overlook this and the other modems of the other models get flashed onto your phone instead replacing the current one and you will loose network connectivity... or jus wait a month or so and buy the note 3 coming out soon
Sent from my GT-N7105 using Tapatalk 4
UPDATE
I finally bought my note 2.
but Its the titanium gray LTE version. the store ran out of stock of rube wine and pink .
I'm happy with with my pjone now though.
and oh, GT-N7105 is safe from sds cause when I ran the eMMC check it says 0xf7.
4everadumbangel said:
I finally bought my note 2.
but Its the titanium gray LTE version. the store ran out of stock of rube wine and pink .
I'm happy with with my pjone now though.
and oh, GT-N7105 is safe from sds cause when I ran the eMMC check it says 0xf7.
Click to expand...
Click to collapse
Yes f7 version is safe but make sure u do all modding as per n7105 files and dont end up flashing n7100 international version rom or files and last keep efs backup safe
Good luck
Hello,
I have a question : is there a Gingerbread ROM for the GT-N7100? Or any way that it supports it? Or any way I can install it / adapt it?
I'm asking because I remember the stupid-crazy battery life I got from my GT-N7000 running Android 2.3 (5-7days of normal use)
I've searched everywhere and it seems that no-one was as crazy as me because I've found nothing on XDA or Google.
UzY3L said:
Hello,
I have a question : is there a Gingerbread ROM for the GT-N7100? Or any way that it supports it? Or any way I can install it / adapt it?
I'm asking because I remember the stupid-crazy battery life I got from my GT-N7000 running Android 2.3 (5-7days of normal use)
I've searched everywhere and it seems that no-one was as crazy as me because I've found nothing on XDA or Google.
Click to expand...
Click to collapse
First firmware for n7100 was 4.1.1 with sds bug (don't try it), sorry no gb for n7100.
Send from my phone
vagsvag said:
First firmware for n7100 was 4.1.1 with sds bug (don't try it), sorry no gb for n7100.
Send from my phone
Click to expand...
Click to collapse
Damn...I thought there would be a ROM of some sort somewhere...
Thank you for your answer!