Samsung working on eMMC hardbrick fix...or not ? - Galaxy S II General

Does anybody know what Samsung is doing about hardbrick issue ?
Latest news from Daniel Hillenbrand was on Jun 8 (He contacted Samsung and:
Patches will be out in form of new official ROMs and also sourcecode releases after testing, which might take some time
Click to expand...
Click to collapse
source: Daniel Hillenbrand Google +
Yesterday, Entropy512 said:
Even secure erase is not 100% guaranteed to cause damage. It turns out it will only cause damage when the eMMC is in a certain specific state. (I unfortunately can't elaborate on the specifics as that is proprietary information) - However it explains why some people manage to wipe even in CWM without damage.
Click to expand...
Click to collapse
I don’t want any details, but after reading all the threads, information from Ken Sumrall and posts on Samsung official support forums, I think that they don’t want to admit, that there’s a problem with their eMMC chips. I know that it is almost impossible to recreate brickbug situation on stock devices - so there is no problem for Samsung at all (custom rom - not their problem) .
I just don’t know what to think – Samsung is currently Rolling-out the Official ICS 4.0.4 Update for Galaxy S2 and we all know, that each of them contains unsecure kernel (all they need to do is disable emmc_cap_erase, right? )
I may be wrong, maybe fix is a lot more complex than just disabling emmc_cap_erase in kernel, but this is the difference between secure and unsecure kernel…so why they didn’t ? Everyone knows about eMMC bug, but Samsung is rolling out new updates and don’t care…

Its Simple They moved on .......
They dont want to spend their time and energy on this phone instead they are thinking about s4 or galaxy note 2

No, they are not. It's so simple to fix hardbrick bug... But Samsung is not interested at all, and seems that it's a computer working on the builds, not real people, since they still releasing this crap. Samsung super fail.

They just don't care and why should they?
The stock Firmwares are noobproof, but if some geeks from XDA D) flash custom Roms its already not their business because a usual customer never even get accidentally into a recovery where he could wipe the phone.
So, they say users fault. Why invest $$$ for a few people who already figured out themselves how to avoid that bug on an "old" device.
Business.Simple as that.

Testraindrop said:
They just don't care and why should they?
The stock Firmwares are noobproof, but if some geeks from XDA D) flash custom Roms its already not their business because a usual customer never even get accidentally into a recovery where he could wipe the phone.
So, they say users fault. Why invest $$$ for a few people who already figured out themselves how to avoid that bug on an "old" device.
Business.Simple as that.
Click to expand...
Click to collapse
Actually its also their loss as they fix the bricked devices under warranty
No one will tell "I flash a ROM from xda and bricked my phone" to the service center guys
Sent from the beast using CMX

I think there is a fix - I heard a couple XDA members saying that they've got a PIT file to fix the problem. Though all it does is make a new /data partition, and you lose a bit of your space (8GB instead of 11GB)

epic118 said:
I think there is a fix - I heard a couple XDA members saying that they've got a PIT file to fix the problem. Though all it does is make a new /data partition, and you lose a bit of your space (8GB instead of 11GB)
Click to expand...
Click to collapse
That's not a fix. Just a workaround to get the device up and running
Sent from my GT-I9100 using xda app-developers app

Related

I9300 xxella sds- is here

hey guys..
my i9300 is 6.5 moths old, today at 21:00 [+2] I got SDS...just plugged my phone to the wallcharger[original samsung charger] and after 1 hour i returned to my phone and BOOOOM....SDS...
i9300 black 16gig
ROM: XXELLA 4.1.2 STOCK NOT ROOTED.
what can i do now?=\
UPDATE: my phone get back to work!!!Very Surprising but Jig has saved my phone.
Warranty claim
ApresVu said:
hey guys..
my i9300 is 6.5 moths old, today at 21:00 [+2] I got SDS...just plugged my phone to the wallcharger[original samsung charger] and after 1 hour i returned to my phone and BOOOOM....SDS...
i9300 black 16gig
ROM: XXELLA 4.1.2 STOCK NOT ROOTED.
what can i do now?=\
Click to expand...
Click to collapse
Are you sure?
I think you need root to flash this http://forum.xda-developers.com/showpost.php?p=36317871&postcount=798
cybdani said:
Are you sure?
I think you need root to flash this http://forum.xda-developers.com/showpost.php?p=36317871&postcount=798
Click to expand...
Click to collapse
FLASHED VIA ODIN.
http://www.sammobile.com/firmware/?page=8&view=9906
ApresVu said:
FLASHED VIA ODIN.
http://www.sammobile.com/firmware/?page=8&view=9906
Click to expand...
Click to collapse
Of course, no problem...........
cybdani said:
Of course, no problem...........
Click to expand...
Click to collapse
oh man...ok..
i've used null_ rom... but then i found some info that xxella should prevent sds and security bug only if its stock[not rooted]...and then i flashed a stock rom....BOOM
Only security bug ! SD fix is a myth
What is SDS?
Sent from my GT-I9300 using xda premium
cukiwap said:
What is SDS?
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Sudden Death Symdrome
I've been telling people; the new bootloader is only here to void the warranties of people who rooted, because it checks to see if your device is modified every time you turn it on, unlike the old bootloader. The new bootloader will make the flash counter stay at 1 and show a red exclamation mark on the screen.
Samsung next will probably say, "Yes, there is an issue. We'll fix it, just send in your S3." And half the people will be screwed because their bootloader screen will show that the phone is modified and that's it. The fix for the Exynos security exploit is in the kernel. What other possible reason is there for a bootloader update beyond what I described? It's to save Samsung money from repairing rooted S3's (even though root has NOTHING to do with what is clearly a hardware issue).
I know people are going to tell me that I'm wrong because when the phone dies, it won't power on at all. That's only half true because some people can get to the bootloader screen, but the device model and other information will show up blank, except it will also still show that the device was modified.
That's why I warned people not to update their bootloader.
Product F(RED) said:
I've been telling people; the new bootloader is only here to void the warranties of people who rooted, because it checks to see if your device is modified every time you turn it on, unlike the old bootloader. The new bootloader will make the flash counter stay at 1 and show a red exclamation mark on the screen.
Samsung next will probably say, "Yes, there is an issue. We'll fix it, just send in your S3." And half the people will be screwed because their bootloader screen will show that the phone is modified and that's it. The fix for the Exynos security exploit is in the kernel. What other possible reason is there for a bootloader update beyond what I described? It's to save Samsung money from repairing rooted S3's (even though root has NOTHING to do with what is clearly a hardware issue).
I know people are going to tell me that I'm wrong because when the phone dies, it won't power on at all. That's only half true because some people can get to the bootloader screen, but the device model and other information will show up blank, except it will also still show that the device was modified.
That's what I warned people not to update their bootloader.
Click to expand...
Click to collapse
My thoughts exactly
Product F(RED) said:
I've been telling people; the new bootloader is only here to void the warranties of people who rooted, because it checks to see if your device is modified every time you turn it on, unlike the old bootloader. The new bootloader will make the flash counter stay at 1 and show a red exclamation mark on the screen.
Samsung next will probably say, "Yes, there is an issue. We'll fix it, just send in your S3." And half the people will be screwed because their bootloader screen will show that the phone is modified and that's it. The fix for the Exynos security exploit is in the kernel. What other possible reason is there for a bootloader update beyond what I described? It's to save Samsung money from repairing rooted S3's (even though root has NOTHING to do with what is clearly a hardware issue).
I know people are going to tell me that I'm wrong because when the phone dies, it won't power on at all. That's only half true because some people can get to the bootloader screen, but the device model and other information will show up blank, except it will also still show that the device was modified.
That's what I warned people not to update their bootloader.
Click to expand...
Click to collapse
never thought of it that way
but now that i read your opinion i can say it makes sense..... HFS - gotta get the old bootloader up ASAP
Product F(RED) said:
I've been telling people; the new bootloader is only here to void the warranties of people who rooted, because it checks to see if your device is modified every time you turn it on, unlike the old bootloader. The new bootloader will make the flash counter stay at 1 and show a red exclamation mark on the screen.
Samsung next will probably say, "Yes, there is an issue. We'll fix it, just send in your S3." And half the people will be screwed because their bootloader screen will show that the phone is modified and that's it. The fix for the Exynos security exploit is in the kernel. What other possible reason is there for a bootloader update beyond what I described? It's to save Samsung money from repairing rooted S3's (even though root has NOTHING to do with what is clearly a hardware issue).
I know people are going to tell me that I'm wrong because when the phone dies, it won't power on at all. That's only half true because some people can get to the bootloader screen, but the device model and other information will show up blank, except it will also still show that the device was modified.
That's what I warned people not to update their bootloader.
Click to expand...
Click to collapse
Kinda makes sense. I really wondered how those SDSs can be software caused? So basically Samsung screwed up somehow on the hardware side and some of the SIII devices are ticking timebombs and now they are releasing a new spy bootloader to check if you modified software in any way, so that in the end you are screwed and Samsung can keep their money because you rooted your device. Gladly I didn`t flashed the new bootloader yet. The negative side is that all devices are still potentially brickable through SD because of unknown reasons. Good job Samsung.
But the SII had the same problem of SDS, it was just smaller in count but the syndromes were the same. Charging over night and in the morning device was not working.
The new bootloader may very well be of some significance in SDS case...!!!
This is a question nobody but Samsung can answer. The bootloader may do some MMC alteration as well, I do not know, but the soft-patch on the kernel side seems to be complete, even though it's just magic code and nobody can understand it so nobody can be sure of it.
Click to expand...
Click to collapse
If my phone is rooted with xxell4 custom rom and my phone died bcz of SDS , will i be able to have my warranty ?
The phone will die completly ?
If they fix it can they know if my phone was rooted ??
Sent from my GT-I9300 using xda premium
If he has suffered SDS using stock LLA kernel it is very weird.
LLA kernel should have the SDS fix that AndreiLux talks about (and implemented it in his kernel).
sachilleas said:
If he has suffered SDS using stock LLA kernel it is very weird.
LLA kernel should have the SDS fix that AndreiLux talks about (and implemented it in his kernel).
Click to expand...
Click to collapse
No LLA kernel dont have this fix !
samydroid said:
The new bootloader may very well be of some significance in SDS case...!!!
Click to expand...
Click to collapse
Kernel and bootloader are 2 different things. You don't need a new bootloader to use a kernel. I'm sure Samsung is hoping the kernel fixes thing, and the bootloader is damage control to reduce repair costs for those that are already damaged beyond repair.
donteo said:
No LLA kernel dont have this fix !
Click to expand...
Click to collapse
Are you sure about this? Update 7 codes by Samsung don't have to do with LLA kernel?
Product F(RED) said:
Kernel and bootloader are 2 different things. You don't need a new bootloader to use a kernel. I'm sure Samsung is hoping the kernel fixes thing, and the bootloader is damage control to reduce repair costs for those that are already damaged beyond repair.
Click to expand...
Click to collapse
You're saying A thing... may be you're right. The developer I quoted said B thing... may be he's right. The point is that lets not jump to conclusions that early. The developer who discovered the fix isn't sure himself. And when one can downgrade to earlier bootloader easily and people are reporting that red exclamation mark can be reset successfully, its not a big deal if they flash the new bootloader.
http://forum.xda-developers.com/showthread.php?t=2083860

voiding warranty

I just learned through Samsung Chat that if you FLASH your device with anything, you void your warranty. Even their official JB.
rosystreasures said:
I just learned through Samsung Chat that if you FLASH your device with anything, you void your warranty. Even their official JB.
Click to expand...
Click to collapse
So by Samsung Chat logic, that includes OTA and their favorite support "suggestion" KIES..... Don't think so. From everything I've read, really depends on region, the support center willingness (some have successfully reported warranty repair on fully rooted and customised devices) and (un)enforced local consumer laws. It's really "hit and miss".
Arobase40 said:
NOPE !!!
Only if you flash a custom non official kernels that trigger the flash counters many times et if you cause damages on your device !!!
Click to expand...
Click to collapse
I have been informed (not personally confirmed) that the P6800 JB 4.1.2 MD3 firmware does not have a flash counter.....
In any case, all my ICS & JB kernels are Triangle Away app compatible, and able to reset if need be.
We all know that in almost every case, any "damage" caused by flashing is actually the result of GUI (general user incompetence). Failure to research, read, prepare and follow guides/instructions properly are the main cause. Not the act of flashing.
Sent from my GT-I9500 using XDA Premium 4 mobile app
As I said, can be really "hit & miss".... consumer laws/protection aren't always enforced either, if there are indeed any at all ....
Edit: GUI could also mean Gross User Incompetence too lol.
We've all done silly things, misread and GUI, just hope the results aren't too bad and recoverable...
Sent from my GT-I9500 using XDA Premium 4 mobile app

Can you Advise me Please ?

I have Rooted my Samsung Galaxy Note 3 LTE Running 4.3 . Now I want to Upgrade to 4.4.2 . Is it Better ? Or is it better to stay on 4.3 ? .
Thank you
Edit: I just realized this thread is in the wrong section. Q and A section please. Not to mention there are other threads like this already
Maybe you should read all the comments and decide for yourself? There is no way I could upgrade because it breaks microSD (can't write to it anymore), it loads new bootloader, so you can't go back and likely you will loose root in the process and some third accessories don't work anymore. It also fixes some holes in Knox security. So if you don't use SD card and don't care about other issues, why not upgrade, if you do care, I think you should wait. All this is changing almost daily and maybe all those issues will be fixed soon, but for now I don't see any benefits, your case may be totally opposite.
Pete4k is the external SD problem affecting all of kitkat or just some roms? Is there a thread page you could link me to about it if you CPUs be bothered?
Ahmed.Soubih said:
I have Rooted my Samsung Galaxy Note 3 LTE Running 4.3 . Now I want to Upgrade to 4.4.2 . Is it Better ? Or is it better to stay on 4.3 ? .
Thank you
Click to expand...
Click to collapse
It's better in terms of being faster overall. Having said that some functions don't work at the moment, for example in my case, the relative humidity sensor doesn't work ( or at least no driver was provided ). Also once you update to 4.4.2 you cannot go back to 4.3. But if you're the type that doesn't flash custom roms/recovery that often then I would say go upgrade.
I want to flash official 4.4.2 , but I want to know before doing that what are the differences between 4.3 and 4.4.2 , what features will be added
Thank you,
Sent from my SM-N9005 using XDA Premium 4 mobile app
Hakired said:
Pete4k is the external SD problem affecting all of kitkat or just some roms? Is there a thread page you could link me to about it if you CPUs be bothered?
Click to expand...
Click to collapse
For example this
http://forum.xda-developers.com/showthread.php?t=2625148
but I've seen few others. They claim you can fix it if you're rooted, but I don't think you can root KK without tripping Knox yet. Samsung admitted themselves some third party acc. don't work any more and they promised fix, but who knows when. I won't have official update for at least few months, but even then, especially sd card issue completely kills it for me, since one of the main reasons I get Samsung phones is for SD card.
pete4k said:
Maybe you should read all the comments and decide for yourself? There is no way I could upgrade because it breaks microSD (can't write to it anymore), it loads new bootloader, so you can't go back and likely you will loose root in the process and some third accessories don't work anymore. It also fixes some holes in Knox security. So if you don't use SD card and don't care about other issues, why not upgrade, if you do care, I think you should wait. All this is changing almost daily and maybe all those issues will be fixed soon, but for now I don't see any benefits, your case may be totally opposite.
Click to expand...
Click to collapse
Hakired said:
Pete4k is the external SD problem affecting all of kitkat or just some roms? Is there a thread page you could link me to about it if you CPUs be bothered?
Click to expand...
Click to collapse
The SD card issue that you mention is not a bug. It would never be patched. Kitkat handles external SD card differently. Apps which want to write data to it need to have a different permission. As of yet, not many apps have been updated with the new permission. Butin time, you can expect most of them to get updated.
In the meantime, you can root your Kitkat rom and change a simple value in an XML file. It will give all apps the permission to write to the external SD card.
Ahmed.Soubih said:
I want to flash official 4.4.2 , but I want to know before doing that what are the differences between 4.3 and 4.4.2 , what features will be added
Thank you,
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The differences between 4.3 and 4.4 are subtle. The status bar icons have changed to white. And Google has enforced it. So every vendor has to make white icons. Honestly, they look nicer to me than the ones Samsung had earlier.
The phone is noticeably faster when turning the screen on and also when unlocking.
Another thing I noticed was a slight improvement in the multiwindow functionality. You can maximize one of the two apps over the other one without it closing. Very useful when you need one of the apps to use the full screen for a small duration of time.
Kitkat also provides native support for wireless printing.
Not much else I can think of right now. But take a look at kitkat's changelog. Just google it.
---------- Post added at 02:20 AM ---------- Previous post was at 02:14 AM ----------
pete4k said:
For example this
http://forum.xda-developers.com/showthread.php?t=2625148
but I've seen few others. They claim you can fix it if you're rooted, but I don't think you can root KK without tripping Knox yet. Samsung admitted themselves some third party acc. don't work any more and they promised fix, but who knows when. I won't have official update for at least few months, but even then, especially sd card issue completely kills it for me, since one of the main reasons I get Samsung phones is for SD card.
Click to expand...
Click to collapse
The only third party accessory not working is the S-view cover. You can use the exposed module by MohammadAG to fix that.
Also, Samsung has admitted to the issue and have commited to fixing it in an OTA update.
I just Realized that if I had upgraded to 4.4.2 , S view and SD Card will have some issues ?
Questions and Help issues go in Q&A and Help section
Thread moved
Thanks
FNSM
Ahmed.Soubih said:
I just Realized that if I had upgraded to 4.4.2 , S view and SD Card will have some issues ?
Click to expand...
Click to collapse
Hi
I just upgraded to 4.4.2 and the only problem am having that {VLC app} doesn’t detect the media inside the Sd card other then that everything works as it was on 4.3(SD).
Overall the 4.4.2 feels smooth and fast.
Sent from my SM-N9005 using Tapatalk

downgrade confirmation

hello guys
I have a sm-n900.....it came upgraded to kitkat in the box
although the performance of the phone is mind blowing but I feel it is a battery draimer......and also I read reviews on net that people with jellybean used to have their battery last more than one day with usual udage but in my case it is only upto 16-17 hrs
I thought of downgrading to jellybean and went to service cemtre where they told me that downgrading in not possible in note 3
I then searched at home and found it is bit complicated and if we do we may loose update to kitkat if we want afterwards
like in my earlier s2 (i9100) and note (n7000) I could flash any firmware anytime
but wat to do downgrade this to jellybean without loosing the possibilities of update to kitkat
plz someone
I know people are here having far big issues compared to mine
but I would be really happy is someone would guide me through this
anikanu said:
hello guys
I have a sm-n900.....it came upgraded to kitkat in the box
although the performance of the phone is mind blowing but I feel it is a battery draimer......and also I read reviews on net that people with jellybean used to have their battery last more than one day with usual udage but in my case it is only upto 16-17 hrs
I thought of downgrading to jellybean and went to service cemtre where they told me that downgrading in not possible in note 3
I then searched at home and found it is bit complicated and if we do we may loose update to kitkat if we want afterwards
like in my earlier s2 (i9100) and note (n7000) I could flash any firmware anytime
but wat to do downgrade this to jellybean without loosing the possibilities of update to kitkat
Click to expand...
Click to collapse
you cant downgrade at all
just not going to happen sorry bud
anikanu said:
plz someone
I know people are here having far big issues compared to mine
but I would be really happy is someone would guide me through this
Click to expand...
Click to collapse
The reason you are not getting any response is because this question has been asked 59 billion times a day since KK rolled out, and the other million plus members who are aware of it are restraining themselves through giant facepalms.
In short, no, there is no way to downgrade.
donalgodon said:
The reason you are not getting any response is because this question has been asked 59 billion times a day since KK rolled out, and the other million plus members who are aware of it are restraining themselves through giant facepalms.
In short, no, there is no way to downgrade.
Click to expand...
Click to collapse
mate do you math its 58 billion times a day lol :silly:
jaythenut said:
you cant downgrade at all
just not going to happen sorry bud
Click to expand...
Click to collapse
donalgodon said:
The reason you are not getting any response is because this question has been asked 59 billion times a day since KK rolled out, and the other million plus members who are aware of it are restraining themselves through giant facepalms.
In short, no, there is no way to downgrade.
Click to expand...
Click to collapse
jaythenut said:
mate do you math its 58 billion times a day lol :silly:
Click to expand...
Click to collapse
so can I root the phone and move to some other custom kernel based rom and then flash jellybean via odin
wat wud happen if I do it using odin.....will it hardbrick or some apps wont work.....plz tell...I know its annoying but plz
anikanu said:
so can I root the phone and move to some other custom kernel based rom and then flash jellybean via odin
wat wud happen if I do it using odin.....will it hardbrick or some apps wont work.....plz tell...I know its annoying but plz
Click to expand...
Click to collapse
Forget jelly beans you can never go back all it will do is Bootloop
donalgodon said:
The reason you are not getting any response is because this question has been asked 59 billion times a day since KK rolled out, and the other million plus members who are aware of it are restraining themselves through giant facepalms.
In short, no, there is no way to downgrade.
Click to expand...
Click to collapse
and I see that u r using same ohone rooted
whuch method did y follow and also is der any prob in handling og the phone after rooting
and can u go back to stock unrooted again to restorr warranty and reset binary counter
jaythenut said:
Forget jelly beans you can never go back all it will do is Bootloop
Click to expand...
Click to collapse
u mean I cant even go to cm10.2 too
anikanu said:
u mean I cant even go to cm10.2 too
Click to expand...
Click to collapse
No, you can't
anikanu said:
and I see that u r using same ohone rooted
whuch method did y follow and also is der any prob in handling og the phone after rooting
and can u go back to stock unrooted again to restorr warranty and reset binary counter
Click to expand...
Click to collapse
I rooted via CF-AutoRoot (as my signature indicates below) and there were no problems. For me, KitKat is working perfectly in every respect.
No, you cannot reset the Knox binary trigger. I could not possibly care any less about it at this point in time.
I plan to use the device until something better comes along, then sell it, so why worry about it?
donalgodon said:
I rooted via CF-AutoRoot (as my signature indicates below) and there were no problems. For me, KitKat is working perfectly in every respect.
No, you cannot reset the Knox binary trigger. I could not possibly care any less about it at this point in time.
I plan to use the device until something better comes along, then sell it, so why worry about it?
Click to expand...
Click to collapse
so now if u visit samsung
what page the officials would open in order to see ur knox counter
Pierre118 said:
No, you can't
Click to expand...
Click to collapse
how r u having knox still 0 even after rooting
anikanu said:
how r u having knox still 0 even after rooting
Click to expand...
Click to collapse
You need to do some searching on the site. All these questions have answers that have been gone over and over.
Early 4.3 users could root their phone but Knox gets tripped. RDLV method worked then without tripping Knox up till MJ3 of 4.3. Anything above that as stock and Knox gets tripped. KitKat goes one step further in that you cannot revert to 4.3 at all, even if you are willing to trip Knox.
You can root the phone but AFAIK (I haven't bothered with KK - my phone runs brilliantly on v6 (4.3) Omega) you trip Knox anyway you do it.
Knox 0x1 may or may not doom your warranty - somecountries have laws that say Samsung cannot quirm out of hardware problems by claiming software changes. You may or may not care about Knox. Mine is a grey import from HK that I had all kinds of fun getting over to a non-freaky ROM, so when it eventually triggered Knox I didn't give a toss. I did root the phone with RDLV and changed ROMs several times before something that shouldn't have, tripped the Knox bit.
Now there is about as brief a history as you will get. Use what is in it to go search and find any more complete answers.
Always search before asking basic questions - at the least it means you will be able to ask intelligent questions, not ones you can find by looking at the titles of recent posts in Q&A forums.
anikanu said:
so now if u visit samsung
what page the officials would open in order to see ur knox counter
Click to expand...
Click to collapse
They'd just boot to Download mode and see the Knox flag.
I don't care about it, honestly. If I ever need warranty assistance, I'd just hope for the best, but since it's Samsung, I'd expect the worst.
Journyman16 said:
You need to do some searching on the site. All these questions have answers that have been gone over and over.
Early 4.3 users could root their phone but Knox gets tripped. RDLV method worked then without tripping Knox up till MJ3 of 4.3. Anything above that as stock and Knox gets tripped. KitKat goes one step further in that you cannot revert to 4.3 at all, even if you are willing to trip Knox.
You can root the phone but AFAIK (I haven't bothered with KK - my phone runs brilliantly on v6 (4.3) Omega) you trip Knox anyway you do it.
Knox 0x1 may or may not doom your warranty - somecountries have laws that say Samsung cannot quirm out of hardware problems by claiming software changes. You may or may not care about Knox. Mine is a grey import from HK that I had all kinds of fun getting over to a non-freaky ROM, so when it eventually triggered Knox I didn't give a toss. I did root the phone with RDLV and changed ROMs several times before something that shouldn't have, tripped the Knox bit.
Now there is about as brief a history as you will get. Use what is in it to go search and find any more complete answers.
Always search before asking basic questions - at the least it means you will be able to ask intelligent questions, not ones you can find by looking at the titles of recent posts in Q&A forums.
Click to expand...
Click to collapse
donalgodon said:
They'd just boot to Download mode and see the Knox flag.
I don't care about it, honestly. If I ever need warranty assistance, I'd just hope for the best, but since it's Samsung, I'd expect the worst.
Click to expand...
Click to collapse
I may be annoying u guys
but what I understand from till now is dat I wont get the privileges of the phone as I used to get in xperia live and sgs2 and maybe what I will use be the stock rom
btw I have still not downloaded the app data of knox which is of 170mb.....wat do u guys suggest should I do it or let it be
and 1 last question that is der any way to have mass storage mode.....as in mtp we dont see the files and folders starting with (.) and I have many imp stuffs on my sd which have their starting with a . and u all know that in mtp we dont see such files and folders.....so is der any way to have the mass storage mode back
plz answer......I know I annoyed a lot.....but plz
You should be able to use another mode. When you connect via USB, swipe down the Notification bar and there should be a Notify there you can tap to choose other modes.
You might need to go into Build Number (Settings/About Phone) and tap 7 times to turn on Developer mode and then turn on USB Debug. (not sure as that's always one of the first things I do)
Unless you are the only person on the planet who sees a need for Knox, you don't need to DL anything to do with Knox. Check in Application Manager and see if you can turn all of it off.
Journyman16 said:
You should be able to use another mode. When you connect via USB, swipe down the Notification bar and there should be a Notify there you can tap to choose other modes.
You might need to go into Build Number (Settings/About Phone) and tap 7 times to turn on Developer mode and then turn on USB Debug. (not sure as that's always one of the first things I do)
Unless you are the only person on the planet who sees a need for Knox, you don't need to DL anything to do with Knox. Check in Application Manager and see if you can turn all of it off.
Click to expand...
Click to collapse
I also have enabled developer options due to my habit of doing in cm roms in previous phones
but on usb connection there are only 2 modes
media transfer protocol
camera protocol
mass storage is missing
donalgodon said:
I plan to use the device until something better comes along, then sell it, so why worry about it?
Click to expand...
Click to collapse
Interesting question. Do you find you can easily sell your rooted/modified phones?
I'm always concerned that people won't want to buy a rooted phone that's potentially been flashed 100+ times with possible excessive CPU over-clocking etc. I always try to put the phone back to stock (or as close as possible) before I sell it on.
Is it just me who feels those concerns?
Medical HRH said:
Interesting question. Do you find you can easily sell your rooted/modified phones?
I'm always concerned that people won't want to buy a rooted phone that's potentially been flashed 100+ times with possible excessive CPU over-clocking etc. I always try to put the phone back to stock (or as close as possible) before I sell it on.
Is it just me who feels those concerns?
Click to expand...
Click to collapse
Well, in my region, the vast majority of buyers don't even know what root is, so it's never been an issue for me. I don't expect that to change anytime soon. The Note 3 doesn't show any issues at all when reflashed unless Knox flag is tripped. Even then, the only "issue" is the warranty bit flag shown in Download mode and the loss of Knox container, which almost nobody uses. Out of a 100 buyers, you might find one that knows what root is and less than that who know how to get to Download mode, and even fewer who'd potentially use Knox, so no, not a problem.

[Q] Lollipop For S4 SHV-E300L?

Will The Korean S4 SHV-E300L get a taste of the New Lollipop update? also if any one has any links to its Custom roms will be highly appreciated, Thanks.
]Edit:
"Ok Guys i dont know if any body knows this already but i have found a ROm for SHV-E300L here:
http://www.7hdmovie.com/2015/02/galaxy-s4.html?m=1
And it is found to be working nicely on SHV-E300L. I recommend it!
johniaxxault said:
Will The Korean S4 SHV-E300L get a taste of the New Lollipop update? also if any one has any links to its Custom roms will be highly appreciated, Thanks.
Click to expand...
Click to collapse
Its exynos version right?
Try i9500 rom ,, i see some shv-e300l user on i9500
ZeroDroid said:
Its exynos version right?
Try i9500 rom ,, i see some shv-e300l user on i9500
Click to expand...
Click to collapse
Thanx for the reply man :good: i was thinking about the same but some say it might hard brick my device and Yes its the exynos version but there is a slight change in the processors see my device Screenshot, Might have to make i bit change in the rom which i dont know how to , if there is any one that has been there and done that please help me
So any progress?
johniaxxault said:
Thanx for the reply man :good: i was thinking about the same but some say it might hard brick my device and Yes its the exynos version but there is a slight change in the processors see my device Screenshot, Might have to make i bit change in the rom which i dont know how to , if there is any one that has been there and done that please help me
Click to expand...
Click to collapse
I have the same phone and I'd like to install lollipop or probably flash a rom. have you found any?
kartabya said:
I have the same phone and I'd like to install lollipop or probably flash a rom. have you found any?
Click to expand...
Click to collapse
No progress yet if any one that have done flashing any rom on this device kindly help us to do so too.
Lets keep it updated here if any thing lollipop happens
No luck
I have this phone since last September and really regret that I bought it. Even though it looks like and feels like a normal 9505 or 9500 model, due to its specifications you can not use any custom rom of more common variants. (No Cyanogen, No Miui, No any other well known custom rom). Do not even try flashing 9505 or 9500 roms, I managed to soft brick my phone already with them.
There is almost zero support for this product in forums or if there is any it is in Korean language. The only custom rom I came across is TeamLeader rom, which is a cleaner stock rom practically, getting rid of Samsung's bloatware, but nothing special, same user experience.
IIRC the SHV-E300 is the Galaxy S4 LTE-A and more or less the same device as the ks01lte. So take a look in the i9506 section, there you will find some custom ROMs for your phone, some already LP-based.
I recommend arters 97's CM12, he is doing a great job on this phone.
srancsik said:
I have this phone since last September and really regret that I bought it. Even though it looks like and feels like a normal 9505 or 9500 model, due to its specifications you can not use any custom rom of more common variants. (No Cyanogen, No Miui, No any other well known custom rom). Do not even try flashing 9505 or 9500 roms, I managed to soft brick my phone already with them.
There is almost zero support for this product in forums or if there is any it is in Korean language. The only custom rom I came across is TeamLeader rom, which is a cleaner stock rom practically, getting rid of Samsung's bloatware, but nothing special, same user experience.
Click to expand...
Click to collapse
I am feeling the same regret my friend i dont think this phone is going to get an official Lollipop update either
why do they make so much devices they can't give support to, or some phones are just labs rats experiments
And yeah thanks for the info, i m not going to flash any other Rom.... yet but i m getting really frustrated :silly:
johniaxxault said:
I am feeling the same regret my friend i dont think this phone is going to get an official Lollipop update either
Click to expand...
Click to collapse
Have you seen this thread? The official Lollipop-ROM for S4 LTE-A has begun to roll out, did you check if it works with your SHV-E300L?
ral9005 said:
Have you seen this thread? The official Lollipop-ROM for S4 LTE-A has begun to roll out, did you check if it works with your SHV-E300L?
Click to expand...
Click to collapse
yeah man i know that and SHV-e300l and i9506 have some notable differences like the chips (Exynos and Qualcomm) it would definetly brick my device
don't install any custom rom for now if you want everything in working order.
and If u want to upgrade to lollipop, just download firmware of another s4 with same configuration from sammobile.com
I think yours is Korean and it will not get 5.0
OK Guys I don't know if any body knows this already but i have found a ROM for SHV-E300L here:
http://www.7hdmovie.com/2015/02/galaxy-s4.html?m=1
i have successfully downloaded it and yes extracted it as well but any body else had tried this already does it work? i am afraid if it would brick or blast my device any help? :angel:
yourshubhamkansal said:
don't install any custom rom for now if you want everything in working order.
and If u want to upgrade to lollipop, just download firmware of another s4 with same configuration from sammobile.com
I think yours is Korean and it will not get 5.0
Click to expand...
Click to collapse
there are some reports of bricked devices after installing Firmware of another S4, suppose i bricked my device would i be able to get it working again if i installed the stock ROM again i mean can u flash a bricked device?
NOt get 5.0 :'( words hurt man they really do
First of all, lets get something straight. Most people use the term "bricked" improperly. A bricked phone means one thing: your phone won't turn on in any way, shape or form, and there's nothing you can do to fix it. It is, for all intents and purposes, as useful as a brick. A phone stuck in a boot loop is not bricked, nor is a phone that boots straight into recovery mode. These are things you can usually fix, and they're a lot more common than a truly bricked phone. If your phone is actually bricked, you won't be able to fix it yourself (but there are things you can do
If Your Phone Is Truly Bricked: Take It Into the Store and Play Dumb
If your phone is actually bricked—that is, it won't turn on at all, no matter how hard you try—it's time to give up and move on. The first thing you can do in this situation is try to take it back to your carrier's store and play dumb—just say something like "I don't know what happened, but my phone won't turn on anymore" (don't tell them you rooted it, obviously). Most carriers don't have time to deal with such issues and they'll just give you a new phone. Sure, it's a tad evil, but it should work most of the time
yourshubhamkansal said:
First of all, lets get something straight. Most people use the term "bricked" improperly. A bricked phone means one thing: your phone won't turn on in any way, shape or form, and there's nothing you can do to fix it. It is, for all intents and purposes, as useful as a brick. A phone stuck in a boot loop is not bricked, nor is a phone that boots straight into recovery mode. These are things you can usually fix, and they're a lot more common than a truly bricked phone. If your phone is actually bricked, you won't be able to fix it yourself (but there are things you can do
If Your Phone Is Truly Bricked: Take It Into the Store and Play Dumb
If your phone is actually bricked—that is, it won't turn on at all, no matter how hard you try—it's time to give up and move on. The first thing you can do in this situation is try to take it back to your carrier's store and play dumb—just say something like "I don't know what happened, but my phone won't turn on anymore" (don't tell them you rooted it, obviously). Most carriers don't have time to deal with such issues and they'll just give you a new phone. Sure, it's a tad evil, but it should work most of the time
Click to expand...
Click to collapse
"Thanx for the info, soo if i install a firmware of another s4 will it TRuly Brick my device"
It depends on the device your are refering another s4 here.
b.t.w higher the risk higher the happiness after success.
yourshubhamkansal said:
It depends on the device your are refering another s4 here.
b.t.w higher the risk higher the happiness after success.
Click to expand...
Click to collapse
So what if u Flash i9500 Rom on my SHV-E300l?
kartabya said:
I have the same phone and I'd like to install lollipop or probably flash a rom. have you found any?
Click to expand...
Click to collapse
i found a rom see above but hadn't tried it yet.. (see on the starting post)
i already tried this rom
johniaxxault said:
Will The Korean S4 SHV-E300L get a taste of the New Lollipop update? also if any one has any links to its Custom roms will be highly appreciated, Thanks.
]Edit:
"Ok Guys i dont know if any body knows this already but i have found a ROm for SHV-E300L here:
http://www.7hdmovie.com/2015/02/galaxy-s4.html?m=1
i have succesfully downloaded it and yes extracted it aswell but any body else had tried this already does it work? i am afraid if it wold brick or blast my device any help?"
Click to expand...
Click to collapse
HI i already tried that rom. im using galaxy s4 SHV E300L..
flash via odin. the rom works well. it wont brick the device because i checked first the file. it does not have modem.bin so the device wont get problem on imei..
i just dont like the chinese characters at the top notification located in the date
here are some screen shots
dajhacker said:
HI i already tried that rom. im using galaxy s4 SHV E300L..
flash via odin. the rom works well. it wont brick the device because i checked first the file. it does not have modem.bin so the device wont get problem on imei..
i just dont like the chinese characters at the top notification located in the date
here are some screen shots
Click to expand...
Click to collapse
That is awesome! are there any bugs? wifi games all well? good to know it is a working rom i will flash it now and hey tell me how to check if the file is ok to go and not corrupted or something

Categories

Resources