Related
Well, I recently was talking to a friend who got a Galaxy S III some time ago.. And his device suddenly had some kind of SOD..
He was stock TW and non rooted.. He's like the 99% of the people out there whom will never flash a custom rom So he gave me the device to see if I could fix it..
First thing I noticed was I could not enter to recovery or odin mode, changed battery, connected to pc and nothing.. Was completely dead.. So i started reading about on sIII forums and seems like SIII its infected with a bug called SDS (sudden death syndrome) i was like wtf?.. The bug consist in: you could be either charging your device or happily using it and when the screen goes off the device will never ever again will turn on.. The effect of the bug? It burns the emmc chip and you either lose your device (like him because he bought it in Europe and we are from Venezuela so no warranty) or if you have warranty you will receive a new device..
Thing its that after seeing that.. Damn our mmc_cap_erase bug its nothing compared to that..
What the hell its samsung doing with the quality control and the engineering?
Devs in SIII forums already patched the bug in the kernel but hey that's a preventive solutions.. Not a fix for already bug triggered devices.
So if any of you have an SIII or a family member.. Go read about it and patch it
Edit: here a link to the issue http://forum.xda-developers.com/showthread.php?t=2091045
Tapatalking on my n7000
msedek said:
Well, I recently was talking to a friend who got a Galaxy S III some time ago.. And his device suddenly had some kind of SOD..
He was stock TW and non rooted.. He's like the 99% of the people out there whom will never flash a custom rom So he gave me the device to see if I could fix it..
First thing I noticed was I could not enter to recovery or odin mode, changed battery, connected to pc and nothing.. Was completely dead.. So i started reading about on sIII forums and seems like SIII its infected with a bug called SDS (sudden death syndrome) i was like wtf?.. The bug consist in: you could be either charging your device or happily using it and when the screen goes off the device will never ever again will turn on.. The effect of the bug? It burns the emmc chip and you either lose your device (like him because he bought it in Europe and we are from Venezuela so no warranty) or if you have warranty you will receive a new device..
Thing its that after seeing that.. Damn our mmc_cap_erase bug its nothing compared to that..
What the hell its samsung doing with the quality control and the engineering?
Devs in SIII forums already patched the bug in the kernel but hey that's a preventive solutions.. Not a fix for already bug triggered devices.
So if any of you have an SIII or a family member.. Go read about it and patch it
Tapatalking on my n7000
Click to expand...
Click to collapse
Thanks.my cousin just bought one but it has warranty.i think i cant make him trust me.what if i brick the phone?or what if after some time he bricks the phone?so their will be no warranty for a phone that is modified
I think i should warn him and let him decide
Sent from my GT-N7000 using xda premium
Samsung :thumbdown: for that..
click THANKS BUTTON if I helped…
Recognized Distributor™
i know of a close relative with a white s3 , after two months of purchase the set stopped charging from wall socket, the charging worked with laptop ......since he had warranty he was told the motherboard needed replacement and he got that done. the back of it has a spider-like faint grey mark and he asks me if its cracked or what ....he doesnt want to go back to service centre and wont let me root it and he doesnt have patience for xda. he is on 411 still.
he didnt pay for it himself, doesnt have a job yet and its not a gift...pretty chaotic situation if u ask me !!
bloody money grubber *** *****. Poor quality control. There's still no permanent solution for N7000 emmc brick bug.
sepehrthegreat-iran said:
Thanks.my cousin just bought one but it has warranty.i think i cant make him trust me.what if i brick the phone?or what if after some time he bricks the phone?so their will be no warranty for a phone that is modified
I think i should warn him and let him decide
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Talk to him and make him read about it here
http://forum.xda-developers.com/showthread.php?t=2091045
Check if he have an affected device..
Tapatalking on my n7000
I sold My s3, a few days ago, which was my first choice and bought note.
Now I read about brick bug. Wtf?
Can I buy device and be safe and peacefull?!
Sent from my GT-N7000 using xda app-developers app
krivinash said:
I sold My s3, a few days ago, which was my first choice and bought note.
Now I read about brick bug. Wtf?
Can I buy device and be safe and peacefull?!
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Just flash a safe kernel according to your rom and live in peace
Tapatalking on my n7000
msedek said:
Just flash a safe kernel according to your rom and live in peace
Tapatalking on my n7000
Click to expand...
Click to collapse
The brick bug on the Note shouldn't be a problem anymore. Just flash the PhilZ kernel which gives you root without increasing the flash counter and you're Note is fixed. You can also download Chainfires got brick bug app.to see if your Note is affected at all. Or you download the brick bug app from the play store which does the same.
Sent from my revived Galaxy Note
N7000
My Samsung Galaxy Note is on JB Alliance Rom XXLSC Beta1.1 which comes with it's own kernel and I don't think PhilZ is supporting it, PhilZ and Alliance Cook had a minor misunderstanding/fallout, (I could be getting my Roms mixed up) I've flashed different Roms 10+ times. Started to worry reading threads on here so downloaded the eMMC Brickbug Check app. All's good here
Maybe you wiped on STOCK ICS KERNEL which is known to cause the Brickbug
click THANKS BUTTON if I helped…
Recognized Distributor™
Arobase40 said:
The brick bug on Note is just a legend... ^^
The only safe kernel I'm aware of is the stock one !
The sole time I flashed a non stock kernel I got my Note fully bricked !!!
Click to expand...
Click to collapse
Yeh you are right!so can you post a video wiping on your stock kernel???!!!
I really appreciate the job that Phil and other Devs are doing
Sent from my GT-N7000 using xda premium
Wrong forum yo dicuss it, but u have a good point. I have also discussed this on s3 forum, but seems like some regions got that buggy phone or maybe this is the samsungs way of self killing the device....whatever it is one should get what they paid for.
Well for my note i have that brick bug thing but i factory resetted my stock rom so many times and my device is fine. So i think stock roms are harmless and this emmc_cap was put to prevent users from using a custom ics in the initial days ,which definitely the devs figured out and fix it in their custom kernel.
Sent from my GT-N7000 using xda app-developers app
qazibasit said:
Wrong forum yo dicuss it, but u have a good point. I have also discussed this on s3 forum, but seems like some regions got that buggy phone or maybe this is the samsungs way of self killing the device....whatever it is one should get what they paid for.
Well for my note i have that brick bug thing but i factory resetted my stock rom so many times and my device is fine. So i think stock roms are harmless and this emmc_cap was put to prevent users from using a custom ics in the initial days ,which definitely the devs figured out and fix it in their custom kernel.
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
What you believe it's completely different from what's a FACT... The bug its not some legend based on empirical trials.. It's been proved that mmc_cap_erase triggers the bug because the mmc chip can't handle secure erase formating .. Simple the chip gets damaged..
The bug was introduced on ICS kernels.. And it's so true that Samsung even disabled secure erase from JB kernels because they say that insecure erase its not harmful...
We disagree because it hasn't been proven (that insecure erase its safe) .. So the best way to be safe its disabling mmc_cap_erase and no formating at all..
To everyone talking nonsense about wiping on stock ICS kernels, next time I'll report you all because that's misleading.. Maybe you have been lucky wiping but that's the problem.. It can happen on wipe number 1 or wipe number 1000.. Who knows..
Tapatalking on my n7000
msedek said:
What you believe it's completely different from what's a fact... The bug its not some legend based on empirical trials.. It's been proved that mmc_cap_erase triggers the bug because the mmc chip can't handle secure erase commands.. Simple the chip gets damaged..
The bug was introduced on ICS kernels.. And it's so true that Samsung even disabled secure erase from JB kernels because they say that insecure erase its not harmful...
We disagree because it hasn't been proven (that insecure erase its safe) .. So the best way to be safe its disabling mmc_cap_erase and no formating at all..
To everyone talking nonsense about wiping on stock ICS kernels, next time I'll report you all because that's misleading.. Maybe you have been lucky wiping but that's the problem.. It can happen on wipe number 1 or wipe number 1000.. Who knows..
Tapatalking on my n7000
Click to expand...
Click to collapse
Agree with the misleading but a little bit respect for the people sharing own experience with us is not so bad!
Any user who reads this attention:
<<do not,under any condition,I repeat do not wipe from your stock ICS recovery>>
sent from galaxy s4(testing dev edition) using xda premium
sepehrthegreat-iran said:
Agree with the misleading but a little bit respect for the people sharing own experience with us is not so bad!
Any user who reads this attention:
sent from galaxy s4(testing dev edition) using xda premium
Click to expand...
Click to collapse
I'm not disrespecting anyone.. Own experience it's bullcrap.. Software developing and electronics engineering its not popular believes or "experiences" everything its done by scientific methods, procedures and knowledge of how things works..
A clear example could be that an engine its build to reach [email protected] if you force the engine beyond that it will get damaged...
Now some people could force it to 160kph and maybe it will work some times.. But at some point it will break.. And you know this because engineers made the engine to work Max at those speeds and RPMs..
It's matter of design.. Not "experiences"
Tapatalking on my n7000
Its been reported that stock ICS is unsafe, since the day it was released, people know about it and avoid it, so anyone saying that it is safe is talking nonsense, if they wanna take the risk and brick their device then thats their choice.
Moving back on to the S3 chips, my GF has had hers several months now and luckily havent encountered any issues at all, I tend to only find device faults AFTER ive purchased them !! i really need to research more before buying
the S3 is 100% stock, my GF wont let me mod it but luckily the device has warranty for the lenght of the contract which is 24 months, so if it ever breaks within this time they'll just fix it for me free of charge
Still, it makes me wonder WTF are a giant company like Samsung doing about this issue ? SGS 2, SGS 3, SGN 1 (unsure about SGN2)
this isnt acceptable from Samsung, regardless if <5% of devices suffer this, I would expect sudden death and insane chips from a cheap chinese knock off, but not a £500 smart phone.
If u say everything is scientific and methodical then howcome samsung didnt knew about it before ics and please define secure wipes, because once things are wiped what are u protecting. Third samsung is the holder of exynos sources. Howcome they didnt knew about it earlier, and discovered by the community first. So here ur proven total wrong, samsung knew about it and they even responded some complains bricked by this issue.
Do u pick articles from retro and bring those things here ????
Sent from my GT-N7000 using xda app-developers app
qazibasit said:
If u say everything is scientific and methodical then howcome samsung didnt knew about it before ics and please define secure wipes, because once things are wiped what are u protecting. Third samsung is the holder of exynos sources. Howcome they didnt knew about it earlier, and discovered by the community first. So here ur proven total wrong, samsung knew about it and they even responded some complains bricked by this issue.
Do u pick articles from retro and bring those things here ????
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
They knew about it. It was fixed in Galaxy Nexus eMMC firmware but yet they kept shipping other devices with the same firmware.
Cut the crap: Do you know more about the emmc brick bug than some elite and recognized devs here ?
qazibasit said:
If u say everything is scientific and methodical then howcome samsung didnt knew about it before ics and please define secure wipes, because once things are wiped what are u protecting. Third samsung is the holder of exynos sources. Howcome they didnt knew about it earlier, and discovered by the community first. So here ur proven total wrong, samsung knew about it and they even responded some complains bricked by this issue.
Do u pick articles from retro and bring those things here ????
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
Before ICS (gb and older) , Android used recursive deletion.. (no mmc_cap_erase procedures in the kernel).. Samsung didn't know about it because the chip was designed under another required process and there's no way to know this kind of things until you produce something in big scales.. As you said you could spend months wiping everyday on stock ICS and never get brick, but after 6 months of doing it the next day you brick...
Entropy went to samsung and he tried several times to brick a note in front of samsung engineers with no luck.. But the bug its there from the first ICS firmware to the very last and considering we are still officially on ICS, i dont think it's a "retro" information...
Exynos source has nothing to do with the emmc chip and what kind of delete/formating methods will damage it.. Heck even deleting big files (over 500 mb) could trigger the bug.
Once again you are talking nonsense
Tapatalking on my n7000
Hi i have the galaxy s4 from verizon but it's actually on ebay trying to sell it because i bought the LG G2 and it's arriving today but i see that there is really only 1 decent ROM out which is CleanRom. I was wondering when CM and AOKP will be coming so i can customize my navigation buttons too and a whole bunch of other features. I havent followed up on the unlocking/rooting but when was root/recovery achieved for this device?
nazzo123 said:
Hi i have the galaxy s4 from verizon but it's actually on ebay trying to sell it because i bought the LG G2 and it's arriving today but i see that there is really only 1 decent ROM out which is CleanRom. I was wondering when CM and AOKP will be coming so i can customize my navigation buttons too and a whole bunch of other features. I havent followed up on the unlocking/rooting but when was root/recovery achieved for this device?
Click to expand...
Click to collapse
The bootloader hasn't been unlocked yet and I spoke with someone close to AOKP last week on Reddit and he said that none of the maintainers will be getting G2's but since the Nexus 5 will be built off of the G2, that there may be some compatibility. So it'll be a while. The N5 isn't even out yet.
We also don't have kernel source yet which makes any CM or AOKP base kinda hard to get running.
Development for anything non-nexus or locked bootloader is going be slow. This phone is brand new, however this is a concern coming from a Nexus with all the latest updates. I will be patient and happy for now, but the flasher in me and the ability to have full control over my own device is a little......sobering.
Lesser Version said:
Development for anything non-nexus or locked bootloader is going be slow. This phone is brand new, however this is a concern coming from a Nexus with all the latest updates. I will be patient and happy for now, but the flasher in me and the ability to have full control over my own device is a little......sobering.
Click to expand...
Click to collapse
This phone has LOKI, which means business as usual for custom ROMs and kernels.
Locked bootloader means nothing at this point, except bragging rights for saying they got it unlocked (if they unlock it, which I think will happen someday, but make no mistake this is not stopping development)
chrisexv6 said:
This phone has LOKI, which means business as usual for custom ROMs and kernels.
Locked bootloader means nothing at this point, except bragging rights for saying they got it unlocked (if they unlock it, which I think will happen someday, but make no mistake this is not stopping development)
Click to expand...
Click to collapse
I am not a developer, so I am not familiar with the possibilities of LOKI, however I appreciate the information. Gives me hope. Thanks again!!
Grady said:
I spoke with someone close to AOKP last week on Reddit and he said that none of the maintainers will be getting G2's
Click to expand...
Click to collapse
My hairdresser's daughter's dog reportedly sneezes more often lately so you should definitely get a flu shot, no matter if you buyvthis phone or not.
android404 said:
My hairdresser's daughter's dog reportedly sneezes more often lately so you should definitely get a flu shot, no matter if you buyvthis phone or not.
Click to expand...
Click to collapse
Is it really her daughters dog or does the hair dresser take care of it?
Sent from my LG-D800 using Tapatalk 2
I'm planning on getting a G2 and Nexus 5 for Sprint as soon as I can swing both. Bringup will take some time but probably not as long as other devices, especially if we can get started based on CAF.
garwynn said:
I'm planning on getting a G2 and Nexus 5 for Sprint as soon as I can swing both. Bringup will take some time but probably not as long as other devices, especially if we can get started based on CAF.
Click to expand...
Click to collapse
garwynn! Good to see you're planning to pick up a G2. I made the move from our beloved E4GT to the G2 myself, but also moved to AT&T. I finally had enough of Sprint's data network being so far behind.
<--- JayWill from the AC forums.
Seems Sprint phones get a lot of dev support, maybe when it's released on Sprint it will pick up.
CM/AOSP bring up is already in progress. I don't foresee anything being particularly difficult to get a basic CM build up and going in pretty short order. I'll be getting the Verizon version later today but won't have time to really start helping until next week.
dalingrin said:
CM/AOSP bring up is already in progress. I don't foresee anything being particularly difficult to get a basic CM build up and going in pretty short order. I'll be getting the Verizon version later today but won't have time to really start helping until next week.
Click to expand...
Click to collapse
You have no idea how happy I am that you are on the case, especially with a Verizon G2. You did great work on the HP TouchPad, can't wait to see what you can do with the G2!
Isn't the nex5 basically the g2 but with a crappier camera?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
irish.iolar said:
Isn't the nex5 basically the g2 but with a crappier camera?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Lol. There's no doubt there will be some sacrifices.
Sent from my VS980 4G using Tapatalk 4
dalingrin said:
CM/AOSP bring up is already in progress. I don't foresee anything being particularly difficult to get a basic CM build up and going in pretty short order. I'll be getting the Verizon version later today but won't have time to really start helping until next week.
Click to expand...
Click to collapse
Do you know the main PIC of that effort? Even if I have to hold off on getting it I'm more than willing to do whatever I can to help Sprint users. We always seem to need a little love on devices..
Dchibro said:
garwynn! Good to see you're planning to pick up a G2. I made the move from our beloved E4GT to the G2 myself, but also moved to AT&T. I finally had enough of Sprint's data network being so far behind.
<--- JayWill from the AC forums.
Click to expand...
Click to collapse
Hey! Nice to see you around! Reminds me, I really need to update my AC links.
I'm lucky being here in Chicago for Sprint, the G2 and Nexus 5 should be in prime shape to take advantage of Tri-band LTE. I'm not feeling the love from Samsung and I know I need the Nexus 5 for AOSP projects. Maybe I'll wait and see if someone sells a G2 over the holidays.
dalingrin said:
CM/AOSP bring up is already in progress. I don't foresee anything being particularly difficult to get a basic CM build up and going in pretty short order. I'll be getting the Verizon version later today but won't have time to really start helping until next week.
Click to expand...
Click to collapse
Very cool, thanks for the hard work.
This is good to hear, I've been eyeing the G2 but am reluctant to leave my S4 because of the Google edition ROM working so well. Will be watching to see what progress is made
Sent from my Galaxy S4
Yes!!!
dalingrin said:
CM/AOSP bring up is already in progress. I don't foresee anything being particularly difficult to get a basic CM build up and going in pretty short order. I'll be getting the Verizon version later today but won't have time to really start helping until next week.
Click to expand...
Click to collapse
Cant tell you how happy I am to hear that! I've been following your work since the nook color! Wonderful news! You have made my day sir!
Ok, so I have an idea to like downgrade from mk2 or mf3... I am a noob to i337, so please explain to me WHY I can't do this before flaming :C
So we obv can't flash because of Samsung's locked bootloader and knox and stuff, but what if we were to completely wipe our phone. Not like a regular "I'ma factory reset my brick yo!" No no no, I mean completely getting rid of EVERYTHING. Modem, kernel, everything to make it as if you haven't gotten a single flash of ANYTHING on your phone, as if your phone is just getting it's software installed. THEN, we flash a MDL and everything for 4.1.2, or practically whatever came before mf3 (since my phone was shipped with that, I never really took the time to research what came before so I'm not sure what version is before). So, I'm thinking maybe someone has actually tried this, and thinking someone has not... Just want to find out if you can, and if you can't, why not.
Thanks
P.S: Wasn't sure whether to post in General or Q&A, so I posted it here
Because when your phone updated to mf3 or later it blows a q fuse that makes it impossible. It's beyond software. It's a hardware issue
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Ends said:
Because when your phone updated to mf3 or later it blows a q fuse that makes it impossible. It's beyond software. It's a hardware issue
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Oh ok, well in that case (sorry I'm a noob) whats a qfuse? I've searched it up and haven't really gotten anywhere with it
SkyAttacksX said:
Oh ok, well in that case (sorry I'm a noob) whats a qfuse? I've searched it up and haven't really gotten anywhere with it
Click to expand...
Click to collapse
From what I've read, it's a piece of hardware that only counts up. It is checked when attempting to flash old bootloaders.
DeadlySin9 said:
From what I've read, it's a piece of hardware that only counts up. It is checked when attempting to flash old bootloaders.
Click to expand...
Click to collapse
This seems like a good place to ask this question: does flashing 4.3 MK2 blow another qfuse? And if we're already on MF3, would you recommend waiting to update and not blowing that qfuse in case that might be the key to regaining access to custom recovery? Or are we doomed forever already and I should just go ahead and take the update?
karate104 said:
This seems like a good place to ask this question: does flashing 4.3 MK2 blow another qfuse? And if we're already on MF3, would you recommend waiting to update and not blowing that qfuse in case that might be the key to regaining access to custom recovery? Or are we doomed forever already and I should just go ahead and take the update?
Click to expand...
Click to collapse
MK2 does trip it, so no MF3 downgrade. Whether or not you upgrade is really up to you: progress is not coming too quickly and unless Samsung patched a security hole we haven't even found yet in the boot loader there's a chance any MF3 exploit may carry over. I would recommend MF3 personally since you can still use Safestrap for some freedom and it'll be less difficult since they won't have Knox to work around.
Hmmm... so it's a piece of hardware huh... would it be possible to remove this hardware? I took apart my S3 when the screen broke to see what was going on internally so if I'm correct, you can take apart the S4, right?
EDIT : Then again, that hardware could be pretty itty bitty...
SkyAttacksX said:
Hmmm... so it's a piece of hardware huh... would it be possible to remove this hardware? I took apart my S3 when the screen broke to see what was going on internally so if I'm correct, you can take apart the S4, right?
EDIT : Then again, that hardware could be pretty itty bitty...
Click to expand...
Click to collapse
I think it would be better for someone to hack the firmware and alter it to make it "think" it has checked this piece of hardware and return a favorable response.
However, i am no developer...
joeybear23 said:
I think it would be better for someone to hack the firmware and alter it to make it "think" it has checked this piece of hardware and return a favorable response.
However, i am no developer...
Click to expand...
Click to collapse
Hmmmm I've wanted to be a dev for quite some time and I am only 14... However I did do a little noob java scripting for irc chats back when I was like 10, so if you know anyone willing to teach me the basics and give me the structure to adb and coding for android and all that, that'd be great
SkyAttacksX said:
Hmmmm I've wanted to be a dev for quite some time and I am only 14... However I did do a little noob java scripting for irc chats back when I was like 10, so if you know anyone willing to teach me the basics and give me the structure to adb and coding for android and all that, that'd be great
Click to expand...
Click to collapse
This is a great community. PM some of the developers and they can probably point you in the right direction to get started.
LOL.. If it were that easy, it would have already been done.
joeybear23 said:
This is a great community. PM some of the developers and they can probably point you in the right direction to get started.
Click to expand...
Click to collapse
Alright, thanks a ton! +1
custommx3 said:
LOL.. If it were that easy, it would have already been done.
Click to expand...
Click to collapse
That doesn't help
I still have a S4, and I never did the update, so I can flash roms, but do as I am fixing to do, I am fixing to sell the wifes S4 MF3, you can still get $500-$600 and get a T-Mobile Note 3.....there are people who know nothing of flashing roms that will pay that price....quit wasting time looking for a solution as the devs that were working on it moved on to different devices....you can bet that there will be no fix for this in the near future.....keep in mind that this is NO software problem.
.
TheAxman said:
I still have a S4, and I never did the update, so I can flash roms, but do as I am fixing to do, I am fixing to sell the wifes S4 MF3, you can still get $500-$600 and get a T-Mobile Note 3.....there are people who know nothing of flashing roms that will pay that price....quit wasting time looking for a solution as the devs that were working on it moved on to different devices....you can bet that there will be no fix for this in the near future.....keep in mind that this is NO software problem.
.
Click to expand...
Click to collapse
CURRENTLY CHATTING WITH SAMSUNG (SORRY FOR CAPS JUST SO EXCITED ) This is what they said just now after I asked about an eFuse/qFuse. Tell me if this is invalid!!!
******: As of now, I would like to inform you that, eFuse is not available in S4 mobile.
This is what the rep has said so far for the i337, will be updating further soon
UPDATE BEFORE POST : I had to ask them this, as I am a newbie and I didn't want to put the burden on you guys.
Visitor: Thank you very much. If you don't mind, is there a difference between qFuse and eFuse?
******: You are welcome. I wish I could have helped you in this regard. However we in live chat have information regarding the US model devices trouble shooting only.
So I guess this could mean they aren't completely suited for these types of Q&A's? Either way, rumors did spread about eFuse stuff being involved but I was just told officially that this was incorrect. Please tell me if I am wrong? Or I might have to start a new thread on this, rather.
SkyAttacksX said:
CURRENTLY CHATTING WITH SAMSUNG (SORRY FOR CAPS JUST SO EXCITED ) This is what they said just now after I asked about an eFuse/qFuse. Tell me if this is invalid!!!
******: As of now, I would like to inform you that, eFuse is not available in S4 mobile.
This is what the rep has said so far for the i337, will be updating further soon
UPDATE BEFORE POST : I had to ask them this, as I am a newbie and I didn't want to put the burden on you guys.
Visitor: Thank you very much. If you don't mind, is there a difference between qFuse and eFuse?
******: You are welcome. I wish I could have helped you in this regard. However we in live chat have information regarding the US model devices trouble shooting only.
So I guess this could mean they aren't completely suited for these types of Q&A's? Either way, rumors did spread about eFuse stuff being involved but I was just told officially that this was incorrect. Please tell me if I am wrong? Or I might have to start a new thread on this, rather.
Click to expand...
Click to collapse
Samsung customer service reps have no clue about the device other than what's on their scripts. A noob on xda has 100 times the knowledge they do
jd1639 said:
Samsung customer service reps have no clue about the device other than what's on their scripts. A noob on xda has 100 times the knowledge they do
Click to expand...
Click to collapse
My hopes
TheAxman said:
I still have a S4, and I never did the update, so I can flash roms, but do as I am fixing to do, I am fixing to sell the wifes S4 MF3, you can still get $500-$600 and get a T-Mobile Note 3.....there are people who know nothing of flashing roms that will pay that price....quit wasting time looking for a solution as the devs that were working on it moved on to different devices....you can bet that there will be no fix for this in the near future.....keep in mind that this is NO software problem.
.
Click to expand...
Click to collapse
Keep in mind the T-Mobile Note 3, N900T gets really bad LTE reception when using an AT&T sim. In places that had a -90dbm LTE signal on the S4 wouldn't even connect to LTE on the N900T for me. The device also got really warm when it was connected to LTE. I don't know if that's because the N900T isn't optimized for band 17, or just a way for them to discourage people from using AT&T.
Developers for the S4 have not called it quits. They are currently working on bringing safestrap to the latest MK2 update.
I'm really just wasting my time here because actually "searching" for any of the stuff in this thread would have provided answers, but I guess posting the information 1001 times is no different than the 1000 times it's already been posted.
A q-fuse involves hardware on some level, an e-fuse is software related. The AT&T S4 used q-fuses to increment firmware boot-loaders. It was incremented between MDL and MF3. It was incremented again between MF3 and MJ6. And it was increased again between MJ6 and MK2. When it is incremented, YOU CAN NOT GO BACK TO A PREVIOUS FIRMWARE...PERIOD! You can not simply change the information in aboot. Any changes invalidate Samsung's signature and without their encrypted key, a file CAN NOT be resigned.
scott14719 said:
I'm really just wasting my time here because actually "searching" for any of the stuff in this thread would have provided answers, but I guess posting the information 1001 times is no different than the 1000 times it's already been posted.
A q-fuse involves hardware on some level, an e-fuse is software related. The AT&T S4 used q-fuses to increment firmware boot-loaders. It was incremented between MDL and MF3. It was incremented again between MF3 and MJ6. And it was increased again between MJ6 and MK2. When it is incremented, YOU CAN NOT GO BACK TO A PREVIOUS FIRMWARE...PERIOD! You can not simply change the information in aboot. Any changes invalidate Samsung's signature and without their encrypted key, a file CAN NOT be resigned.
Click to expand...
Click to collapse
I'm very much sorry for that. However, do not misinterpret me when I say this but, your post was unnecessary as someone already said qFuse was on a hardware level. I dedicated a bunch of today to S4 and the I337 model specifically. Tomorrow or Wednesday is when I'll be sending some PMs to Devs
Basically, thread is over with. Thanks everyone
Hi guys,
I wonder if anyone knows if I set up a custom ROM in my note 4 ( my phone still are completely stock and original ), and change the counter it knox , I could go back to stock and use the Samsung pay later?
Thk´s
Hy everybody
Anyone?
Tks!
John___007 said:
Hi guys,
I wonder if anyone knows if I set up a custom ROM in my note 4 ( my phone still are completely stock and original ), and change the counter it knox , I could go back to stock and use the Samsung pay later?
Thk´s
Click to expand...
Click to collapse
Note 4 don't supoort Samsung Pay new Note 5 and s6edge+ have new NFC chip...
Jovan1997 said:
Note 4 don't supoort Samsung Pay new Note 5 and s6edge+ have new NFC chip...
Click to expand...
Click to collapse
Tks bro,
I know, but still in note 4 have the nfc tecnology, and samsung pay can use that. what do you think?
John___007 said:
Tks bro,
I know, but still in note 4 have the nfc tecnology, and samsung pay can use that. what do you think?
Click to expand...
Click to collapse
Yea but note 5 use new nfc technology,connection beetwen phone and 'phone' reader..I dont know may be it will work,u can download samsung pay apk and try,no need to flash custom roms and root phone.
*ps i tried app and it start and just block when i need to setup fingerprint or pin code
Jovan1997 said:
Yea but note 5 use new nfc technology,connection beetwen phone and 'phone' reader..I dont know may be it will work,u can download samsung pay apk and try,no need to flash custom roms and root phone.
*ps i tried app and it start and just block when i need to setup fingerprint or pin code
Click to expand...
Click to collapse
Yes, i doit, same thing here, stop on setup fingerprint.
My fear is install custom roms that i want, and later when i go back to stock, because os knox coutner, i dont can use samsung pay, understand?
What do you think?
John___007 said:
Yes, i doit, same thing here, stop on setup fingerprint.
My fear is install custom roms that i want, and later when i go back to stock, because os knox coutner, i dont can use samsung pay, understand?
What do you think?
Click to expand...
Click to collapse
How u can use Samsung pay if it dosnt work on Note 4?
No later,u think samsung will port samsung pay for Note 4 in android M? I dont think,so yea u can flash custom roms
Jovan1997 said:
How u can use Samsung pay if it dosnt work on Note 4?
No later,u think samsung will port samsung pay for Note 4 in android M? I dont think,so yea u can flash custom roms
Click to expand...
Click to collapse
That is the point, who knows? i know that note 4 dont have mst, but have nfc... android pay and others works with this, it will works after i have flashed a custom rom?... i dont know if samsung will lost the bigger part of market...
John___007 said:
That is the point, who knows? i know that note 4 dont have mst, but have nfc... android pay and others works with this, it will works after i have flashed a custom rom?... i dont know if samsung will lost the bigger part of market...
Click to expand...
Click to collapse
Android pay will work...even on custom rom-If not rooted.
Android pay will not work if u root phone.I hope samsung will lost and down like NOKIA
Jovan1997 said:
Android pay will work...even on custom rom-If not rooted.
Android pay will not work if u root phone.I hope samsung will lost and down like NOKIA
Click to expand...
Click to collapse
How i can install a custom ROM if not rooted?
You think that Samsung will fall?? really believe that Samsung will not enable Samsung pay for all devices with NFC ? at least those who have the fingerprint sensor?
John___007 said:
How i can install a custom ROM if not rooted?
How you think that samsung will down? really believe that her do not will take all phones with nfc to use samsung pay?
Click to expand...
Click to collapse
... What??? "samsung will down?". "really believe that her do not will take all phones". What the heck?? I know that auto-correct on phones stinks, but read over what you typed and fix it before you submit your comment. I can't decipher your comment in any way shape or form...
xtraspecialj said:
... What??? "samsung will down?". "really believe that her do not will take all phones". What the heck?? I know that auto-correct on phones stinks, but read over what you typed and fix it before you submit your comment. I can't decipher your comment in any way shape or form...
Click to expand...
Click to collapse
Was not for you dear , I'm talking to jovan 1997, he said he thinks the Samsung will drop equal to Nokia ... read all the reviews before bullshi*****.
John___007 said:
Was not for you dear , I'm talking to jovan 1997, he said he thinks the Samsung will drop equal to Nokia ... read all the reviews before bullshi*****.
Click to expand...
Click to collapse
I know you were replying to jovan, that had nothing to do with what I said... My point was that what you said makes zero sense. Take 12 seconds and proofread your comments before hitting Submit is all I'm saying. This isn't a private messaging site, this is a public forum, so even when you are replying to someone else you have to know that other's will come along and read your post, perhaps in hope of getting information for a question they have or a problem they are trying to solve. That's one of the main points of public forum boards like this is that the conversations are available for others to read at a later date. Anybody reading your comment, even after reading the entire thread (which I did) will have no clue what in the heck you are talking about... Good for jovan if he/she understood it, but it might as well be in a foreign language...
xtraspecialj said:
I know you were replying to jovan, that had nothing to do with what I said... My point was that what you said makes zero sense. Take 12 seconds and proofread your comments before hitting Submit is all I'm saying. This isn't a private messaging site, this is a public forum, so even when you are replying to someone else you have to know that other's will come along and read your post, perhaps in hope of getting information for a question they have or a problem they are trying to solve. That's one of the main points of public forum boards like this is that the conversations are available for others to read at a later date. Anybody reading your comment, even after reading the entire thread (which I did) will have no clue what in the heck you are talking about... Good for jovan if he/she understood it, but it might as well be in a foreign language...
Click to expand...
Click to collapse
I'm sorry my fault , I just wanted to say I will be glad if samsung lose its customers as it happened to 'nokia'
My english is bad yea samsung dont give us new features just push out new models,no new camera api for n4,no tw with theme engine,so wtf? Just change numbers and done ??! Ty Sammy
Can Someone Decipher This? Thanks XDA
WarriorMAL18 said:
Can Someone Decipher This? Thanks XDA
Click to expand...
Click to collapse
You should ask this to rom developer in the rom thread that you are running.
This is due to the fact that the custom OS, that you are running does get the latest Note 7 updates and the last one more or less cripples the device. Making it useless as a phone.
WarriorMAL18 said:
Can Someone Decipher This? Thanks XDA
Click to expand...
Click to collapse
That's cause your on a note 7 port rom. And your device is being recognized as a note 7 because your build.prop is showing it as one.
I got that message to when i was testing nemesis n7 port, the other day. Plus it was being pushed from the Samsung+ app for me. Does your rom have that app installed?
The big question is, even though we have different hardware, if samsung can't decifer the difference and they try to push software to our device. Will it [email protected]*k up our device? Or will our different hardware provide a safegaurd against this?
I don't know their limitations for forcing software onto our device, since it's not really a N7. Maybe someone with some better knowledge or coding skills can chime in on this.
Hmm....on an interesting note. I received this message on my T-Mobile Note 4 while running LamlazyROM V5.0. I went ahead and flashed Norma v11 and Aurora 4.1 in order to replicate this particular message. To my surprise. None came up. Not even the Note 5/Note7 ROM Port showed this anomalous message. Now the billion dollar question is, just as another member commented, "Will this update brick my Note 4?" In all honesty, I've tried on several occasions to try to run the Software Update feature that's been baked into the ROM and with every attempt I would get a Forced Closed/App Crash notification window. So yeah maybe it is possible but unfortunately we'll have to wait and see what happens. Yay. I guess.
WarriorMAL18 said:
"Will this update brick my Note 4?"
Click to expand...
Click to collapse
It certainly will. The note7 runs off completely different firmware which is included in the ota. Never update through ota on a ported rom.