Develop Bugs

Returning to stock

To those of you who may not have followed my previous thread, I recently had a problem with my Inc2 only being able to charge while turned off. I had to ask for a replacement under warranty, meaning the defective unit needs to be sent back. Long story short, I was able to restore the stock ROM on the defective one, but unable to restore the stock bootloader, meaning it is now on the stock ROM, but with S-off. Do you guys think whoever at Verizon is responsible for checking phones sent back under warranty will notice this or even care?
Sent from my ADR6350 using XDA

Of course it is possible they will see and care, but I think it is more than likely they will not notice or care. I have heard of many people returning phones (even back to my Eris days) with a stock ROM on an s-off device without a problem.
Good luck!

TheAtheistReverend said:
Of course it is possible they will see and care, but I think it is more than likely they will not notice or care. I have heard of many people returning phones (even back to my Eris days) with a stock ROM on an s-off device without a problem.
Good luck!
Click to expand...
Click to collapse
All they really look for is water and physical damage. There are so many launchers out there that they usually have no idea. Unless you get the guy who also roots and flashes. Then they usually just flash back to original. I still recommend to always restore your stock backup at the very least.
Sent from my VivoW using xda premium

Is there a way to get s-on after you have used revolutionary?
Sent from my Incredible 2 using xda premium

http://www.youtube.com/watch?v=tnlnWW8tsvo
Sent from my Incredible 2 using xda premium

Its ridiculous how to unroot. I have a skyrocket though. Would it be the same thing???
Sent from my SAMSUNG-SGH-I727 using xda premium

jordansN00B said:
Its ridiculous how to unroot. I have a skyrocket though. Would it be the same thing???
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
No
Sent from my Incredible 2 using xda premium

tattedupboy said:
To those of you who may not have followed my previous thread, I recently had a problem with my Inc2 only being able to charge while turned off. I had to ask for a replacement under warranty, meaning the defective unit needs to be sent back. Long story short, I was able to restore the stock ROM on the defective one, but unable to restore the stock bootloader, meaning it is now on the stock ROM, but with S-off. Do you guys think whoever at Verizon is responsible for checking phones sent back under warranty will notice this or even care?
Sent from my ADR6350 using XDA
Click to expand...
Click to collapse
I am in the same boat - except mine is barely even charging when it's off and not charging at all on. My usb port on the phone is all screwed up - I cannot even mount it. I called verizon and they are sending a replacement. I have 5 days from when I get the replacement to return the old one.
I still had a backup of my original Verizon Rom so I flashed it (thank goodness I was able to do it with barely any battery).
All the processes to get S-ON back seem to require the USB port and a good amount of battery power. I have neither. I will keep searching but it looks like i will be sending it back with just the stock ROM and S-ON.
The agent said that they "need to verify that your phone has not had any physical or liquid damage. As this is not covered under the warranty. You will need to send back your defective phone to the warehouse."
So technically I do not have that kind of damage - I will report back the outcome - wish me luck!

Good luck!
Sent from my ADR6350 using xda premium

razzie33 said:
All the processes to get S-ON back seem to require the USB port and a good amount of battery power. I have neither.
Click to expand...
Click to collapse
Once you get your replacement, you can always use that to charge up the battery, swap it back into your broken phone and do what you can.
As far as the adb commands necessary to replace the boot loader, I don't think anyone had confirmed if this works or not, but you CAN initiate an adb connection over WiFi. There are apps on the market that'll switch between USB and WiFi for adb.
But it's probably not worth the hassle, just get a stock rom on it and they'll probably never notice.

ChrisDDD said:
...But it's probably not worth the hassle, just get a stock rom on it and they'll probably never notice.
Click to expand...
Click to collapse
+1
Sent from my ADR6350 using xda premium

ChrisDDD said:
Once you get your replacement, you can always use that to charge up the battery, swap it back into your broken phone and do what you can.
As far as the adb commands necessary to replace the boot loader, I don't think anyone had confirmed if this works or not, but you CAN initiate an adb connection over WiFi. There are apps on the market that'll switch between USB and WiFi for adb.
But it's probably not worth the hassle, just get a stock rom on it and they'll probably never notice.
Click to expand...
Click to collapse
So I got the replacement phone (s-on ) and, powered up the battery and used it on the old phone. I factory reset the phone but since it was rooted, I had "Superuser" in there as an app and couldn't remove it. That was the only thing that was giving me a little hesitation about sending it back.
Downloaded Terminal Emulator and manually removed superuser, did another factory reset and Superuser is gone. Have FastBoot checked on in the Settings so unless they actually go into the phone and change that, they won't boot into the bootloader or see the s-off revolutionary.
Phone is going in the mail today

Update:
Got a text message from Verizon yesterday: The defective device has been received by Verizon.
and no charge or any notice that it breached the warranty/contract!

USB issues as well unless I get the device at the correct angle. A pain, but used the directions and links from the youtube link to get my DInc2 back to stock and S-On. A pain to angle things right but worth it to me knowing I'm going in with no potential "threats".
Gotta wait the 3-5 days now...
EDIT::
In case people are wondering, my DInc2 was rooted using revolutionary method and it worked flawlessly.

How does Samsung feel about rooted phones?

I need to send my phone back to Samsung because they have a 1 year manufacturer warranty per Sprint. If I send them back a Stock but rooted phone will they notice/care? The repair is hardware related not software. I need to get half of the small little hooks that are compressed when the battery is inserted. My only though is they may want to wipe battery stats and when they go into Recovery and notice it's TWRP they might get pissy. Thoughts & experiences? Thanks.
Sent from my SPH-L710 using xda premium

I took mine to sprint fully rooted and on a custom ROM, because my LCD was fried.. They didn't care at all. I wouldn't worry about unrooting it and crap. Just send that bad boy in.
Sent from my SPH-L710

xbmoyx said:
I need to send my phone back to Samsung because they have a 1 year manufacturer warranty per Sprint. If I send them back a Stock but rooted phone will they notice/care? The repair is hardware related not software. I need to get half of the small little hooks that are compressed when the battery is inserted. My only though is they may want to wipe battery stats and when they go into Recovery and notice it's TWRP they might get pissy. Thoughts & experiences? Thanks.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
My initial thoughts are as follows:
Samsung bootloaders are unlocked by default and they have indicated that they will not lock them in the future. So I'd think they're more likely to forgive rooting when it comes to their 1-year warranty.
According to Samsung's warranty page, as long as the defects you have are in no way caused by custom ROMs or the rooting process, they should cover the repair. Unfortunately, they have the final say in what caused the damage to the phone and could say that the custom kernel fried whatever part is malfunctioning. I seriously doubt that they'd do that, but it all depends on which service person you get and how good/bad their Monday has been. I'd say it'd be best to triangle-away the flash counter and to restore the stock recovery/rom. As always, qbking77 has a great video on how to unroot, so check it out.

I dont know. Samsung would probably be more "aware" of your phones root state compared to sprint. If its something simple like bad USB port, or burnt pixels, I doubt they would care. If your phones O.S. is jacked or you hard brick your phone, likely they will notice. You can avoid these problems if you install triangle away and have it automatically clear your bootloader every time you boot your device.
Remember,
You are taking a risk when you root your phone. Sometimes you will get a service rep who doesn't know anything about rooting and/or could care less....sometimes you will get an XDA Member service rep pissed you are raising their premium, it all depends.

Thanks everyone for your responses! Awesome I'm glad Samsung is open minded with this matter. Yes there is no way my hardware issue is ROM/Software related so I'm hoping they won't care. I'm still going to flash the stock MB1 ROM and use the paid SuperUser app to hide the icon in the app drawer before sending it out just in case. Thanks everyone!
Sent from my SPH-L710 using xda premium

xbmoyx said:
Thanks everyone for your responses! Awesome I'm glad Samsung is open minded with this matter. Yes there is no way my hardware issue is ROM/Software related so I'm hoping they won't care. I'm still going to flash the stock MB1 ROM and use the paid SuperUser app to hide the icon in the app drawer before sending it out just in case. Thanks everyone!
Click to expand...
Click to collapse
What happens after you sent your device to Samsung.... Please let me know....nothing personal just curious to see what their reaction is

tasnim_tamim said:
What happens after you sent your device to Samsung.... Please let me know....nothing personal just curious to see what their reaction is
Click to expand...
Click to collapse
This thread is 3 years old, they probably won't answer.
Sent from my SCH-I535 using Tapatalk

Droidriven said:
This thread is 3 years old, they probably won't answer.
Click to expand...
Click to collapse
Maybe Samsung didn't fixed it at all and they forgot their XDA password...

My Note II on 4.1.2 Experienced SDS

I just wanted to let you all know that even on 4.1.2 (stock and stock recovery), your note can just all of a sudden die. For no reason. I had stock malaysia ROM 4.1.2 that was released in April I believe. It was rooted, but all I used that for was Titanium Backup.
My usage of the phone was bare minimum, all I really use the phone is for Google Talk. That's actually all I was doing when all of a sudden the screen froze and the phone would not respond to any buttons or touches. Once I removed the battery it never started again. I can't get it to boot normally, or download mode or anything.
I'm in the US and i bought this off eBay back in November or something of last year, so I have no idea what to do now except get another phone.

Yes its the chipset in the phone that has a bug which can kill the phone. Alot of the note2 phones have it including mine. There is an app on market that can tell you if you got the chip in your phone but by now you already know that. Try a phone repair shop or if you want surf around the net and see if you can find a motherboard for a decent price then you could change it your self.
Sent from my GT-N7100 using XDA Premium 4 mobile app
---------- Post added at 06:50 PM ---------- Previous post was at 06:47 PM ----------
The newer roms have a software fix for the hardware bug. Dont remember if that fix is in the rom it self or in the kernel but if you had the latest custom rom on your phone then it might not have died.
Sent from my GT-N7100 using XDA Premium 4 mobile app

I was on 4.1.2 with stock rom and kernel combination. As far as everyone seems to say on this site, that is what you need to do to try to avoid SDS. In either case, my suggestion to everyone here is to just get another phone before yours dies as well.

ksc6000 said:
I was on 4.1.2 with stock rom and kernel combination. As far as everyone seems to say on this site, that is what you need to do to try to avoid SDS. In either case, my suggestion to everyone here is to just get another phone before yours dies as well.
Click to expand...
Click to collapse
My N7105 died also, simply would not boot, not even into download/recovery mode at all, no red led. Tried switching batteries, charging, pressing buttons for 30secs, etc; no response.
It was running 4.1.2 and on Perseus kernel alpha33, which was what everyone said it needed to avoid the SDS issue. My phone was even tested safe/sane via the eMMC test app.
Not 100% certain if it was SDS, but either way it was unresponsive/dead.

ksc6000 said:
I just wanted to let you all know that even on 4.1.2 (stock and stock recovery), your note can just all of a sudden die. For no reason. I had stock malaysia ROM 4.1.2 that was released in April I believe. It was rooted, but all I used that for was Titanium Backup.
My usage of the phone was bare minimum, all I really use the phone is for Google Talk. That's actually all I was doing when all of a sudden the screen froze and the phone would not respond to any buttons or touches. Once I removed the battery it never started again. I can't get it to boot normally, or download mode or anything.
I'm in the US and i bought this off eBay back in November or something of last year, so I have no idea what to do now except get another phone.
Click to expand...
Click to collapse
Ohh,Sorry for that & Thanks share this IMP Info,Have u ever Test eMMC Bug app? U have Sane Chip?U bought new phone?

No I didn't buy a new phone yet, don't have the money. I probably won't, I'll probably just use my old Nexus One. Yes I did use that app and it was insane chip. I just thought that with 4.1.2 it was safe, guess not.
Anybody know if it's safe for me to sell this phone on eBay? Obviously I'm going to sell it as is and write that it doesn't work, but I'm wondering if I do that, if someone can get it repaired, will they have access to my data that was on it?

ksc6000 said:
No I didn't buy a new phone yet, don't have the money. I probably won't, I'll probably just use my old Nexus One. Yes I did use that app and it was insane chip. I just thought that with 4.1.2 it was safe, guess not.
Anybody know if it's safe for me to sell this phone on eBay? Obviously I'm going to sell it as is and write that it doesn't work, but I'm wondering if I do that, if someone can get it repaired, will they have access to my data that was on it?
Click to expand...
Click to collapse
Oh OK,but who ever face SDS they have one common symptoms like when press power button red led blinks,is it same happening in your mobile? also they are able to go in download mod but product id will be missing but in your case u r not able to go in download mod,its confusing.

jdomadia said:
Oh OK,but who ever face SDS they have one common symptoms like when press power button red led blinks,is it same happening in your mobile? also they are able to go in download mod but product id will be missing but in your case u r not able to go in download mod,its confusing.
Click to expand...
Click to collapse
No red light. I can't get into download mode at all.

a piece of my knowledge acquired by reading the whole thread. First of all it doesn't matter if you were at 4.1.2 it should be dlk7 or higher (firsts 4.1.2 didn't have it). so do you know the number? if it was higher it could be a big problem for the affected chips :S
and secondly, there are 2 ways of SDS the first is known as "soft" which allow to enter download. the second is the hard one and the one that OP may have.
hope it helped somehow
Sent from my GT-N7100 using xda premium

aka_sirok said:
First of all it doesn't matter if you were at 4.1.2 it should be dlk7 or higher (firsts 4.1.2 didn't have it). so do you know the number? if it was higher it could be a big problem for the affected chips :S
Click to expand...
Click to collapse
Hmm ok, just curious, my dead phone was running 'HashCheck Hybrid v2.2 ZHDMB1.t0lte' with Perseus kernel. Should it have been safe or no?
aka_sirok said:
and secondly, there are 2 ways of SDS the first is known as "soft" which allow to enter download. the second is the hard one and the one that OP may have.
hope it helped somehow
Click to expand...
Click to collapse
I see, so Hard SDS it was then.

Perseus kernel has the patch for sds added.
GT N7105 with XDA Premium......that is all......

sure but i readed somewhere that to be 100% safe it has to be kernel and recovery sds patched. if you had those patched both the ones that have the insane chip must be worried :S
Sent from my GT-N7100 using xda premium

I wonder if using cyanogenmod also end up the same? I mean this problem only caused by original firmware? if both is the same is there a reasonable solution for stock users? My wife has the phone for 2 months and I want to make sure she doesn't suffer the problem from the beginning. What are the measures I can take to avoid this problem?

maluus said:
I wonder if using cyanogenmod also end up the same? I mean this problem only caused by original firmware? if both is the same is there a reasonable solution for stock users? My wife has the phone for 2 months and I want to make sure she doesn't suffer the problem from the beginning. What are the measures I can take to avoid this problem?
Click to expand...
Click to collapse
it is a hardware problem. check the version of the chip with EMMC checker, 2 months old it's quite a good notice because it means newer chip probably.
Sent from my GT-N7100 using xda premium

Well hopefully. But while investigating the issue in internet I read 1-2 guys who have so called "sane" chips but still having freezes. I don't know if they really had the same issue or they had their phones bricked in the end but that caused me to doubt the safety of sane chips. I don't know.
Enviado desde mi One S usando Tapatalk 4

aka_sirok said:
sure but i readed somewhere that to be 100% safe it has to be kernel and recovery sds patched. if you had those patched both the ones that have the insane chip must be worried :S
Click to expand...
Click to collapse
That was my understanding too, I had Philz CWM Touch (cant remember which version, but I d/led and installed it last month) installed as well.

This was the version I was running:
N7100XXDMC3 N7100OLBDMD1 - Malaysia

maluus said:
Well hopefully. But while investigating the issue in internet I read 1-2 guys who have so called "sane" chips but still having freezes. I don't know if they really had the same issue or they had their phones bricked in the end but that caused me to doubt the safety of sane chips. I don't know.
Enviado desde mi One S usando Tapatalk 4
Click to expand...
Click to collapse
Checked it and my wife's is a "sane" chip.

Sleep of Death

I'm root and unlocked bootloader and I want to know if xperia ZL suffers from "Sleep of Death" issue like the Z...and does the fix applied to ZL as well..
Cause my zl kinda suffer from it...after a reboot the phone shut itself..it will stay longer if I connected to a charger but after a long period it will shut it self again...I think it's a software issue cause when in cwm, it doesn't shut down...but I have formatted to factory state and everything stock but the problem still persist...
I'm on latest 2.67 firmware and stock kernel but will relocking the bootloader will save my phone...if not, I'm gonna try to claim warranty and hopping they don't detect I'm already void the warranty even I'm relock again...
Hope someone can help....tq
Sent from my iPhone using Tapatalk Pro

martin132014 said:
I'm root and unlocked bootloader and I want to know if xperia ZL suffers from "Sleep of Death" issue like the Z...and does the fix applied to ZL as well..
Cause my zl kinda suffer from it...after a reboot the phone shut itself..it will stay longer if I connected to a charger but after a long period it will shut it self again...I think it's a software issue cause when in cwm, it doesn't shut down...but I have formatted to factory state and everything stock but the problem still persist...
I'm on latest 2.67 firmware and stock kernel but will relocking the bootloader will save my phone...if not, I'm gonna try to claim warranty and hopping they don't detect I'm already void the warranty even I'm relock again...
Hope someone can help....tq
Sent from my iPhone using Tapatalk Pro
Click to expand...
Click to collapse
Well, im 100% sure that problems on phone comes put when people root, change firmware, custom. etc all kind of (pirate stuff) not officilly from sony to the phone, i have always been stok official on every phone i had ( S2, S3, NOTE2, ZL) and nothing has happened to me with sudden death or sleep of death.
I just want to know WHY PEOPLE KNOWING ALL THIS ISSUES ON CUSTOM, LIKE BUGS ETC THEY STILL LIKE CUSTOM.... lol thats like to be MASOCHIST..
STICK to the stock.

danieldp1990 said:
Well, im 100% sure that problems on phone comes put when people root, change firmware, custom. etc all kind of (pirate stuff) not officilly from sony to the phone, i have always been stok official on every phone i had ( S2, S3, NOTE2, ZL) and nothing has happened to me with sudden death or sleep of death.
I just want to know WHY PEOPLE KNOWING ALL THIS ISSUES ON CUSTOM, LIKE BUGS ETC THEY STILL LIKE CUSTOM.... lol thats like to be MASOCHIST..
STICK to the stock.
Click to expand...
Click to collapse
I agreed with you, I always been stock, no root or unlocked bootloader. I rather be with a phone that have warranty just in case something happen, than been with a modified phone, death and not warranty if Sony found out.
Sent from my C6506 using xda app-developers app

Every phone I had I've modded the **** out of it. Yet I never had the problem that I've broken the phone. I don't know how people get their phone destroyed, the only reason I can think of is the fact that people don't read carefully and miss important details in a description or tutorial.
Sent from my C6503 using xda app-developers app

maclancer said:
I agreed with you, I always been stock, no root or unlocked bootloader. I rather be with a phone that have warranty just in case something happen, than been with a modified phone, death and not warranty if Sony found out.
Sent from my C6506 using xda app-developers app
Click to expand...
Click to collapse
Well that's good for ordinary people with ordinary stuff on their hand...other people doesn't like that and I'm one of it...well this is personal liking anyway...
I have used many android phone in range of model including iphone and all root and jailbreak...and some people love the change and love to put their phone to the limit...
Only recent phone I have problem with and old model don't have any problem...
Sent from my iPhone using Tapatalk Pro

einfachgaer said:
Every phone I had I've modded the **** out of it. Yet I never had the problem that I've broken the phone. I don't know how people get their phone destroyed, the only reason I can think of is the fact that people don't read carefully and miss important details in a description or tutorial.
Sent from my C6503 using xda app-developers app
Click to expand...
Click to collapse
I'm considered myself an experience on rooted phone...always double check when trying to flash or modded something....and always successful on it...if I brick it I always recover it again...only the current flagship I got problem with...I think this is a problem with some Sony phone that have problem on some of it...that something they miss...I work in Japanese factory and I know how they work....
Sent from my iPhone using Tapatalk Pro

martin132014 said:
I'm considered myself an experience on rooted phone...always double check when trying to flash or modded something....and always successful on it...if I brick it I always recover it again...only the current flagship I got problem with...I think this is a problem with some Sony phone that have problem on some of it...that something they miss...I work in Japanese factory and I know how they work....
Sent from my iPhone using Tapatalk Pro
Click to expand...
Click to collapse
bad luck you got a defective phone, cause mine is working like new with 0 issues.
I had rooted many other phones and also moding, but the truth is that nothing is much better than STOCK = 0 BUGS, and troubles.

danieldp1990 said:
bad luck you got a defective phone, cause mine is working like new with 0 issues.
I had rooted many other phones and also moding, but the truth is that nothing is much better than STOCK = 0 BUGS, and troubles.
Click to expand...
Click to collapse
Well that's true...I'm root and modded my phone always use stock rom...I am not a fan of custom rom but always modding to the limit...always trying to put something on to maximize it...
Bad luck or not, today I'm trying my luck again to go to Sony center to claim warranty on my defective phone...I have made a factory reset and relock my bootloader...so hoping Sony wont find out...if they did...moneys going down the drain...
Sent from my iPhone using Tapatalk Pro

I think we are to premature to say about issues with root, modified or custom roms because the Zl, Z ,Z1 they are babys come out few mounts ago and all the developers are trying hard to make it fly. I remember my HD2, I get that phone after 2 years of his release and I was flashing tons of roms everyday and I find many powerful and stable roms. So be patient.

eclyptos said:
I think we are to premature to say about issues with root, modified or custom roms because the Zl, Z ,Z1 they are babys come out few mounts ago and all the developers are trying hard to make it fly. I remember my HD2, I get that phone after 2 years of his release and I was flashing tons of roms everyday and I find many powerful and stable roms. So be patient.
Click to expand...
Click to collapse
Well, maybe but i think the problem is not in root or any roms...the phone is just defective..i got mine back from repair and work ok again...
And thats true about old phone...i used some HTC, and Sony's old phone, always flash something, and no problem occur...only todays phone, i always encounter many defects on it...great technology, but also fragile...
Sent from my C6502 using XDA Premium 4 mobile app

as far as i understand, its not because u rooted or unlocked but bcuz of a problem with the battery management syste(BMS).
there appears to be sum fault with battery or the bms, which causes the phone to shutdown.
unfortunately, the only solution is to change the battery. u will have to return ur phone to sony. but to claim warranty, u must unroot and relock the bootloader.
mind you, there is only a small number of phones with this problem.
this same issue happend with my ZL too. i returned and within one week, they returned a brand new phone to me.
mine was fully stock, locked bootloader and unrooted(the previous and the newer too)
new is working awesome.
hope this helps, if it does, u know where the thanks button is!

control freak said:
as far as i understand, its not because u rooted or unlocked but bcuz of a problem with the battery management syste(BMS).
there appears to be sum fault with battery or the bms, which causes the phone to shutdown.
unfortunately, the only solution is to change the battery. u will have to return ur phone to sony. but to claim warranty, u must unroot and relock the bootloader.
mind you, there is only a small number of phones with this problem.
this same issue happend with my ZL too. i returned and within one week, they returned a brand new phone to me.
mine was fully stock, locked bootloader and unrooted(the previous and the newer too)
new is working awesome.
hope this helps, if it does, u know where the thanks button is!
Click to expand...
Click to collapse
Was going to say I haven't experienced this issue... and my phone is rooted and unlocked...

5.1.1 ota rollout

Just received the 5.1.1 OTA. look at the kernel build date. this thing was cooked up YESTERDAY. device feels a lot snappier!! This is the T-Mobile branded one.
http://pasteboard.co/5Mu7cnk.jpg
NO, the bootloader is not locked with the 5.1.1 update that was leaked.
Rather, "Factory Reset Protection" (an Android thing - not a Samsung thing!) is now an option, which allows you to lock the bootloader yourself, protecting your device from someone installing a custom recovery, wiping your device and making it their own. It makes the device somewhat less valuable, and therefore (supposedly) less likely to be stolen.
--AOU

brand?

Gho57 said:
brand?
Click to expand...
Click to collapse
Tmobile. sorry

Okay guys so many people called me fake and I don't blame you..having 5.1.1 even when nexus devices don't have it is kinda suspicious but I need to clarify some things.. New boot loader is not locked like Verizon/ATT phones It's FRP, Factory Reset Protection. This is google's response to Icloud for stolen/lost devices.. I tried to flash twrp and cfroot and freaked out when i got the error about bootloader being locked...Now this doesn't mean Samsung/Tmobile will completely lock bootloaders in the future but we have to wait and see... phone seems to be really smooth and stable , however it looks like the camera needs some work done so I'm 100% this is not the final build and I guess I'm just lucky I got it this morning and be happy that Samsung has a build this stable with 5.1.1 which means official releases are not far.
http://pasteboard.co/5Mu7cnk.jpg
http://pasteboard.co/5S5yEQa.png
http://pasteboard.co/5S7rKOL.png
New Bootloader now has Factory Reset Protection aka Google "Icloud Lock"
http://pasteboard.co/5TQRnDJ.jpg
wont let you flash custom binaries anymore!
and a video for the non believers... https://www.youtube.com/watch?v=QehlPoP0X_0&feature=youtu.be
HERES LINK WITH SYSTEM.IMG and BOOT.IMG
http://www.mediafire.com/download/jz16ze63vzn0989
System entered a bootloop after using cfroot.

Woow 5.1.1
Sent from my LG-D802 using XDA Free mobile app

wow....even faster than the nexus devices (Nexus 5)

Wow...amazeballs!
Nothing on unlocked UK yet, gives me hope though
Anyone else had this yet?

wow..good news..thanks

how is the night clock issue..?

Would you be able to check if the Auto-Brightness setting is fixed (check to see if it stays on Auto-Brightness), and if the Night clock is only lighting up necessary pixels on the AMOLED display? I can't wait for the rollout to hit my T-Mobile Edge! I'm hoping they improved the battery life some more too, it definitely doesn't last long enough.

If this is a prank, I will find you, and I will kill you. Lol
Omg. How does it feel? Battery life, smoothness?

strange that T-Mobile is faster than European Samsung unbranded..no update ATM.. ?

Nice! Hopefully the full file will show up soon so that those of us that are rooted can update.

I got no update. show screen shot.
Sent from my SM-G925T using Tapatalk

shadowk91 said:
Would you be able to check if the Auto-Brightness setting is fixed (check to see if it stays on Auto-Brightness), and if the Night clock is only lighting up necessary pixels on the AMOLED display? I can't wait for the rollout to hit my T-Mobile Edge! I'm hoping they improved the battery life some more too, it definitely doesn't last long enough.
Click to expand...
Click to collapse
yes it seems to be fixed now

MacTheRipperr said:
I got no update. show screen shot.
Sent from my SM-G925T using Tapatalk
Click to expand...
Click to collapse
look at the link... i failed to grab the update file

It's a dead link
Sent from my SM-G925T using Tapatalk

MacTheRipperr said:
It's a dead link
Sent from my SM-G925T using Tapatalk
Click to expand...
Click to collapse
http://pasteboard.co/5Mu7cnk.jpg

Still shocked you got it....... Don't see it mentioned anywhere

MacTheRipperr said:
It's a dead link
Sent from my SM-G925T using Tapatalk
Click to expand...
Click to collapse
Link is good. Checked on PA and it works. I think when you click via tapatalk it fails. Some sort of issue with the tapatalk redirect.