Database Info

[Q] Nexus S goes into some sort of fault state

My two months old Nexus S started to behave in a way that renders it pretty much useless - Freezing / Locked U
Freeze/Delay Between Menu and basically the phone is dead.
Very often when the screen is off, pressing power button powers up the screen with the screen lock, but the phone is not responsive so the screen just goes off again as it is impossible to slide to unlock it.
On top of that, leaving the phone with the screen off for a half an hour or so brings up some sort of warning sign and a small android (can see the screen shot here: http://yfrog.com/h3apmgqj) and the phone is effectively dead. The only thing to do in any of the two cases is remove and reinsert the battery, but that is no solution to anything. All this is while the battery is fully charged.
Did anyone experienced this before? resetting phone does not help.
Here is more info on this topic: http://www.google.com/support/forum/p/Google+Mobile/label?lid=4e31a500f89fe575&hl=en

Are you using a custom recovery/ROM? That icon you posted isn't the stock image

Hi, no I do not - the image is actually from different phone but it looks exactly as it did on my Nexus S (little green guy with an exclamation mark). I never rooted my phone or done any custom mods to its system.
I actually sent it to Samsung and they are claiming that they found no problem, so they re-flushed the phone and are sending it back. I am seriously angry at samsung. It is arriving on the 11th so I'll let you know if that helped but I doubt it.
I believe this might be a faulty memory because I often received notification that the internal storage was unavailable or something of that nature as well, right before the problem would occur. Are the any tests I could perform for memory / storage?

just try to flash it back to stock
then do wipe data and wipe cache
see if that gets it back on its feet

Hey,
thank you, I thank that means I would have to root it first ehhh
Samsung told me they've done just that (flashed phone) so I am seriously hoping that my phone will work when it arrives on the 11th.
thanks!

Samsung supposedly is looking into this problem, please see link below:
http://www.google.com/support/forum...ad?fid=44db6d8e31129d4c00049e3b2a6db4d1&hl=en

Update:
I just received my phone from Samsung repair and of course, the phone is NOT fixed. On the side note, they also sent back my note that explains the problem meaning it was ignored completely.
I will be contacting @SamsungServic and calling but at this point I am not sure that they can fix the phone other then replace it.
Also,
I've spoken to Samsung and chat online and - yes they nice and throw back lots of promises and niceness back but they are NOT doing anything about it, for now at least.

I copy and paste the best answer on the google support topic to here:
I've been keeping a notebook to document my debugging of this problem. No app in particular is responsible, in my opinion. I have observed the phone lock up after a Factory Data Reset + USB wipe, and with no accounts configured. In fact, I have had it freeze after following this procedure:
1. Factory Data Reset + USB erase from Settings menu
2. Phone reboots.
3. Go through initial setup screens, skip account setup.
4. Power down phone.
5. Remove battery.
6. Remove SIM card.
7. Replace battery.
8. Power up phone.
9. Let phone sit for 15 minutes or more.
10. Phone freezes.
This is about as close to bare bones as I can get with this device.
I have also documented at least four freeze modes:
1. Phone is completely dark (both display and buttons). No combination of power button or other buttons can bring phone back. Battery removal required.
2. Phone display is dark, but the four "hard key" buttons are illuminated. No combination of power button or other buttons can bring phone back. Battery removal required.
3. Phone displays only a green android by a warning exclamation sign. Holding power button down, then volume up, then release volume up, will bring up the Android system recovery screen, from which phone can be rebooted.
4. Phone is frozen at the unlock screen. Sometimes this freeze occurs while swiping the unlock icon. No combination of power button or other buttons can bring phone back. Battery removal required.
I have observed the phone going from normal standby state (display and buttons dark) to state 2, and at other times to state 3, while it was sitting on my desk by the keyboard.
I'm just about ready to send it to Samsung. I just wanted to verify that the problem would be reproducible after a factory reset and without the SIM card.
I think it may be a hardware problem. It's also possible that part of the Android kernel or some device driver on my device has become corrupt. Unfortunately I can't reset the OS.
Click to expand...
Click to collapse
I did a factory reset from the stock recovery, too. Doesn't help either.
My phone arrived on Friday Samsung mobile repair in Texas. And like they did to ohter Nexus S devices from other users they will do the following to mine:
Reflashing the phone -> doing some functional tests ...
... and this is the crazy thing about it. The error we have is just appearing when the phone is in standby and because of this the phone passes the functional tests Samsung is doing at the end of the service. Phone goes back to user. A defective phone.
Some guy managed to keep the phone alive by setting the display turning off after 30mins. He is charging it twice a day
I got a reply from @SamsungSupport on twitter:
Thank you Fabian for again reaching out to us. We are aware of this issue as some of us have your same phone.
An evaluation is already being conducted to determine the fix. We don't have a timeframe of the resolution.
But understand it will be pushed to phones. We will advise once we have a timeframe.
Click to expand...
Click to collapse
The support team is friendly and to me it feels like they try to do anything they could.
Funny: One guy got a replacement device. But then no one other. Just reflash...
I think they will do something but on the other hand I'm worried that they will do nothing. But time will tell....
Maybe it would help us if Google will be aware of the problem, too. Ok maybe they allready know it, but I don't know that.
So if some of you here do have some connections... please do us a favor and forward this topic or the link to the google support topic. Feel free to forward this topic to any website you think it would write a news about it. Maybe Google will throw a eye on it. My phone is 8 weeks old and yeah this so anoying. And of course all my friends who are iHippster are trolling me like hell.
It don't want to flame or blame Samsung\Google for this.But our phones are in warranty. The error hits only a few devices and so they should replace it. My 50cent about it... this is not a Google expierence they talked about...

I also had the same problem and sent my phone into Samsung. They only re flashed it, which didn't fix the problem. I immediately called Samsung to inform them that the issue was not fixed and they just told me to send it back for "double checking." Do you think it is better to send it back in or just wait for fix to emerge?

I will be sending it back and demand replacing the phone, also making sure they just don't re-flash again. I guess anything but re-flashing could work.
Remember that I've mailed my phone with one page letter explaining the problem. Their response was flashing the phone and sending it back - with my letter.
Here is note from the support team:
----------------------------------------
Original Problem:
Technical Inquiry
Phone Freezing / Locked U
Freeze/Delay Between Menu
Problem found:
NO TROUBLE FOUND
SW,PRL,OTSL RESET
Solution:
Passed All Functional Testing
--------------------------------------
@Samsungservice did not even acknowledge it officially that this is a problem.

Yeah i wrote a letter too explaining the issue and how to recreate it (the first time). They told me that it passed their quality assurance inspection after re-flashing it, which must be very poor because my phone shut off again 15 minutes after receiving it. Just dropped it back off at UPS today. Can they replace the phone because of this issue? I know one person had success, but it doesn't seem anyone else has.

Nexus S faulty
Samsung may not be able to reproduce it after reflashing; as this issue does not seem to occur when connected to a PC/computer via USB. Their automated testing could be over USB.
Looks like more and more people are facing this issue as the day goes by.
Search for "Nexus S fault state" on google and you'll find the google support forum thread discussing it

Guys,
Did anyone have tried to flash a custom rom to see if this will solve the problem ?
cheers !

No, but this problem is not ROM related.

discr said:
Samsung may not be able to reproduce it after reflashing; as this issue does not seem to occur when connected to a PC/computer via USB. Their automated testing could be over USB.
Looks like more and more people are facing this issue as the day goes by.
Search for "Nexus S fault state" on google and you'll find the google support forum thread discussing it
Click to expand...
Click to collapse
I figured that was why they couldn't recreate the shutdown. Made sure they knew that it has to be unplugged. Mine always shuts off within 10-15 minutes if untouched.

I have same problem.Only remove battery helps. I have been having nexus s for 2 and half months and this problem just came last week. I don't know how to solve it. I tried reflash firmware but didn't help.

welcome to the club. you have to send it to USA to get it serviced (make a extreme detailed problem description and make sure the support worker writes it down 1:1 into their ticket system). they provide a 2day ups shippment label, BUT only to locations in USA.
I can recommend FedEx. They helped me a lot with this duty stuff for shipping to USA. That's not so easy . I paid €50 to get it shipped to a friend of mine in USA.
You have to send only the foreparts of the device. No battery and back panel, no charger and so on. But they will give you all informations at the end of the service request.
or: wait for a hotfix. which maybe never will come.

Update:
I just mailed my phone again... they told me they do not replace phones (not sure what that means yet). The Rep was arguing that if I want the phone replaced then I need to talk to T-Mobile - it does not make any sense.
Anyway, I explained the problem as much as I could and did not mail any notes this time as they obviously do not care for it. But I made sure he included every detail in his notes.
I am very skeptical but still hoping....
Also,
About the part when the phone does not freeze when plugged in or charging. I had my Nexus S charging overnight and it was frozen in the morning.

Update:
Also, I've contacted @SamsungServic via Twitter and asked if their team recognized it as a problem, but I've got no response.
On the other hand if you report the problem to them, they will respond that they will look into it - which means nothing, but if enough people asks the same question them they will have to.
-thanks

I've got some sort of responce via Twitter from @SamsungService, here is what they wrote back:
@SamsungService
Thank you for reaching out to us. We are aware of this issue as some of us have your same phone. An evaluation is already being conducted to determine the fix. We don't have a time frame of the resolution, but understand it will be pushed to phones. We will advise once we have a time frame. Thank you. ^Mary
@Keinam
Does this mean we should stop sending our phones back for repair and just wait for your OTA update? If it happens?
@SamsungService
Many issues can be resolved with warranty service. Regarding the issue you've referred to,It is my understanding that a fix if being worked on which would be sent out OTA. ^Mary

[Q] HTC Surround Frozen?

Okay, googled, and bing'd the crap out of this and it looks like so far everyone who's had this issue has had to send their phones in for repair, but before doing that I thought I'd ask here aswell to see if anyone has been able to solve this problem.
I've had my HTC Surround for about a month now and this morning when I went to use it I noticed I couldn't read my emails, it said something like "Oops we were not able to retrieve your email." I thought no problem I'll just restart my phone. I turned it off, and turned it back on. Ever since then the phone has been stuck on the white HTC start screen. I've pulled the battery four times and tried restarting it. I've restarted it holding the volume up and down buttons and I get a bootloader screen (no option to hard reset). I can plug it into my computer on the bootloader screen and the computer recognizes the device as an HTC SD card. (This is nice to know seeing as I can, if I ever get the phone working again, load files on the phone's SD card that Zune won't let me) however this is bad because Zune will not recognize the phone.
Sooo, anyone else had this problem and been able to fix it themselves? I don't want to have to send it to HTC because I have no warranty. I bought the phone used. Any thoughts would be appreciated!
And this is running 7004, I have no unlocked the phone or tampered with it in any way. (yet)

Have you looked in the development forum for your stock ROM and tried flashing it from the bootloader?

I couldn't find a rom to flash. Maybe I will just use this as an opportunity to switch to Sprint and buy an Arrive. That way I can be done with ATT's crappy service.

I'm on my third surround now, with both previous ones dead with the exact same situation you have described. I called ATT, had them replace them on warranty for free. I'm waiting for this third one to die so I can get a different model
P.S. I tried flashing the stock ROM, hard resetting, and everything else trying to get both phones back to life but I ended up just having to warranty them. Call up ATT and have them send you a new one.

Thanks, I was able to do a warranty claim. Technically I wasn't allowed to because I bought the phone outright (used) on craigslist. But since the person at ATT was lazy and didn't check when I went in the sent me to my local device support center and I was able to walk out with a new phone in 5 minutes.
Hope this doesn't keep occurring though. If they were to ever check how the phone was purchased I'd be screwed.

doejohn531 said:
Thanks, I was able to do a warranty claim. Technically I wasn't allowed to because I bought the phone outright (used) on craigslist. But since the person at ATT was lazy and didn't check when I went in the sent me to my local device support center and I was able to walk out with a new phone in 5 minutes.
Hope this doesn't keep occurring though. If they were to ever check how the phone was purchased I'd be screwed.
Click to expand...
Click to collapse
I had the same problem with my Surround a few months ago. Then I had another one that kept losing the data off the device. I'm on my third one now and it has been holding up for three months.
I also noticed in the store that all the display models of the phone were having the exact same issue.
I think they changed something up, as this new one seems to be hanging in there much better than the last two.

hi
i am new , post post post

[Q] Bricked S2 GTi900 help

Ok, I know lots of people brick their phones, and like in my case hard-bricked as well. But everycase is unique but I'd really appreciate if you guys could look over what I did and see if my plan of action is the right thing to do.
So, basically I came across ICS on youtube by chance and it looked to be really cool for my S2. I have no experience with romming and such and I'd only ever heard of it. Then after about only 3 hours of research I set to work to romming it. The instructions said I had to get a clockwork mod to flash the drive to get ICS. I think I messed this up as I'm not entirely sure I unzipped the folder properly to get the .tar. on pda.
So, my phone would turn on but only get to the samsung logo with the warning sign. By this time I was fed up and worried and such and decided it was too much effort and just wanted my phone back. So I set out to put the original firmware back on. I downloaded the stuff and put the in their respective slots, pit,pda and mobile I think. I pushed start and it was if odin had frozen (no progress bar either), I couldn't click anything and the log script in the corner showed nothing.
I was quite annoyed and closed odin and unplugged my phone,put it back in download and such to try again. This time the same thing happened and I unplugged the phone first, Big mistake! My phone went completely black and effectively hard bricked.
Okay that's what happened. I just want advice to see if what I'm going to do is right.
1- Imma try to go through the simple workarounds to try to get my phone back into download mode.
2- This will probably fail, so I will purchase a USB jig from amazon, this will give me 3 potential results
one. My phone will get back into download mode and there will be no warning sign under the samsung logo and custom counter at 0.
two. My phone will get back into download mode but there is still the warning sign and the custom counter is at 0
three. Nothing will happen or my counter will be at one
3- okay so if scenario one happens I will send my phone to samsung and they should repair as they have already told me through e-mail they believe it to be a motherboard problem
scenario two, I will send my phone to vodafone,as I've learnt from the forums their techies should not care as much about that kind of thing.
scenario three, I will send my phone to mobile tech videos in Texas from the UK as everyone seems to trust them and they look pretty legit.
Okay, so that's basically my plan of action. All I want is for you guys is to just go "yeah, good idea thats probably right" or show me what I've misjudged or if you are aware of another option for me.
Thanks,
Adam

Bump, please I know some of you guys can help me out

[Q] Hard Bricked? Sidekick 4g

Soo I have a big problem,
My sidekick 4g suddenly shut off and directly went into Download Bootloader. It would only stay in that window for about 3 seconds then restart. So I tried doing Odin but it would never stay in download mode long enough. After a while, the phone stopped turning on and now it does not even charge. I believe I have hard bricked the phone. When I leave it on the charger. I see no indication that it is charging but the battery gets warm. Is there any hope for me to fix this phone?
Please let me know ASAP. Thanks!

helodavelo said:
Soo I have a big problem,
My sidekick 4g suddenly shut off and directly went into Download Bootloader. It would only stay in that window for about 3 seconds then restart. So I tried doing Odin but it would never stay in download mode long enough. After a while, the phone stopped turning on and now it does not even charge. I believe I have hard bricked the phone. When I leave it on the charger. I see no indication that it is charging but the battery gets warm. Is there any hope for me to fix this phone?
Please let me know ASAP. Thanks!
Click to expand...
Click to collapse
Does the device even show up as a USB vendor/product id? See that with `lsusb` on Linux or the Device Manager on Windows.
It might be worth trying ayoteddy's FOOL PROOF WAY TO GET INTO DOWNLOAD MODE here:
http://forum.xda-developers.com/showthread.php?t=1186954
Perhaps if you trigger the phone to enter download mode that way, it won't just continually reboot...
Beyond that, I think you'll be looking at hardware-level fixes. If the phone isn't literally fried, it can almost certainly be repaired with JTAG. But that would involve a JTAG interface which I am guessing you don't already have.
You might be able to find someone who will JTAG for you for free, or for a fee. A local phone repair shop might have this capability.
If you're damn good with a soldering iron, or have a friend who is, there's also AdamOutler's "UnbrickableMod":
http://forum.xda-developers.com/showthread.php?t=1347984
That mod is not for the feint of heart, you need to take the phone almost entirely apart and do soldering work within the area of a grain of rice... but it is possible.
But all the options assume that the only problem with the device is a bad flash -- damaged boot loader, bad kernel/recovery, etc. The way you describe your phone's demise, a hardware failure certainly seems like a possibility.
Good luck, I hope your device is not dead.
FWIW, SK4G goes for ~$100-200 on eBay these days depending on condition. Locally you could probably find lower prices.

Wow thanks for all the info but i tried ayoteddy. Since the phone doesnt even power on , i cant do what teddy says. And no, after a few failed odins, the comp doesn't even see the phone. But that's also because the phone doesn't turn on. I even put a charged bat. Still no go

helodavelo said:
Wow thanks for all the info but i tried ayoteddy. Since the phone doesnt even power on , i cant do what teddy says. And no, after a few failed odins, the comp doesn't even see the phone. But that's also because the phone doesn't turn on. I even put a charged bat. Still no go
Click to expand...
Click to collapse
It really sounds like a hardware failure.
If you are committed to trying everything to rescue your particular device, you could double down and try a new battery. You risk wasting whatever money you spend on it, of course.
If I recall correctly, the SK4G can't operate properly without some battery current, even when plugged into USB. And the other symptoms seem to leave the door open on battery problems -- sudden power down, brief signs of life which eventually cease, hot battery. The sudden failure of a lithium battery would hardly be unusual.

I have seen an issue very similar to this before. It turned out to be a loose connection inside the phone. Might want to disassemble and reassemble carefully to ensure that the connections are secure. Youtube has dis-assembly videos to guide you. You don't have to completely disassemble the phone, just til you reach the main board and secure the connections to it. If you don't feel like you can hand the task of dis-assembly you could always search for a local phone repair business, or even computer repair shop (they often do some phone repairs). Hope this helps

Hey there, I am trying to fix a SK4G with the exact same problems... download mode will show up, but then the screen will go blank again. I'm gonna look into what blk2dr suggested... did you ever fix yours, OP?

root? so Warranty it, not saying its the most "ethical way"
out of curiosity what was the last, well as samsung would put it, hac...ERRRR unsupported warranty voiding modification known to us as upgrade/flash eg. via cwm odin rom app add on modem kernel etc. that was done to the ol SK? or is it just straight up faulty craftsmanship from samsung...nooooo on a SK4g??? is that possible? lol moving a rom around from folder to root of sd once (zip prev passed md5 check) my 2nd or was it 3rd t839 had a lil hiccup that i didnt realize at the time made my custom Roms zip like 47kb smaller then it previously was and should of been, when flashing is 2nd nature and ur just moving it within the same sd card its already checked out on the md5 sum and ur dealing with a 200+/-mb file, whos gonna notice that minor change? to make a really long story just kinda long, into voodoo cwm flash, let it marinate... phone ran great for 4 days, then i decided i was going to clear cache davlik fix permish and reboot...yea went into cwm wiped wiped and half way thru fix permish phone crashed rebooted back into recov, when i tried to reboot sys it had your same exact issue. DL mode for just a second...then all black yet slightly backlit screen. could never get it to stay long enuff to odin back to stock, fullproof DL mode was a no go and of course the battery died, wouldnt recharge. i played dumb went to tmo store dude tesed phone with new batt my batt in other sk etc etc...anyways he charged my battery up enuff it flared back into dl mode for a few sec...my fix? hours and days headin into weeks of jackin with this thing i went with my cure all root REUPwarranty fix...flash a bad freakin bootloader thru odin and kill it once ad for all, DL mode only needs to be on about 4 sec, not long enough to go back to stock rom but long enuff to kill that B. prefered bootloader is i9000 haha works like a champ everytime to every rooted phone that had issues i needed a warranty exchange on(only been 4) seeing how i get a new phone every 3months on avg and always pay full price the ratio is tiny. yeah i know the trickle down effect raising costs from manufacture in long run yadayada. all is true, but i figure ive been kicked in the groin so many times by samsung,lg,moto,htc etc they can eat 1 every now and then. as a tmo employee in 07/08 i paid 500 upfront for the mda that got back ordered for 6 months had 2 bad dead spots in the touch screen within a month and screen went completely white in 3mnths. some employee/warranty fine print screwed me out of a new phone. and dont even get me started on the sidekick. 399 bucks for a phone that basically got abandoned 3 months later cuz it was junk compared to what it should be and breaks in high quanities. theyll still tax u 20 bucks and make u keep ur old battery and cover charger etc so im not losin any sleep, for real kill it for good, run it to the store get ur new err rebuilt refurb SK4g in 2 days then save up for a t989 s2 dl gmote/spashtop and poweramp on ur SK4g and let her roll as a wireless keyboard/mousepad for ur pc and let the voodoo and Pamp rock as a killer mp3 player. thats all the T-urd-839 is really good for anyways, oh yea and a mediocre bt controller for playin games on my S2's lol do the warranty, its samsung/TMOs fault for lettin this junk product get released, abandoning it and overcharging so many of us. Just do it, do it lol

pull battery, connect usb, hold power, volume up, volume down, camera, and tackpad and insert battery. It should FORCE the phone into download mode.
try it lol~

Hard Bricked... Pls Help!!!

Recently, I bought the LG Stylo from Boost on Craigslist. Before the transaction was completed, I checked the IMEI and everything checked out clean. Like a lot of folks here on this site, as soon as I got home, I attempted to root. Prior to me rooting, I got an OS update to marshmallow and I went ahead and did it. Once the update was completed, I rooted with Kingo Root and root was achieved.
Not long after (within 24 hours), I noticed that my phone was getting very laggy and choppy so I decided to reboot. When I did that, the "LG Life's Good" boot image showed up like usual. Then the screen went blankb and turned back on to the boot image but the bottom said "SECURITY ERROR" then couple seconds later z the screen goes off again and it comes back on to the previous boot image. It pretty much is doing a boot loop. Initially, I was able to access the stock recovery and I did a hard reset but that didn't help because the outcome was the same. Then an hour or so afterwards, my access to the stock recovery was gone. Now when I try to boot recovery, it says LOADING RECOVERY but then instead of going to recovery, the Android guy pops up and right below him it says ERASING then it boots into the boot loop cycle.
At this point, all I can do is boot into download mode and from my understanding, all I can do is install the firmware. Since I was on Marshmallow, I looked online for days for the boost mobile 6.0 stock firmware. What I failed to realize is that what I found was completely not meant for the boost mobile 6.0 variant instead it was for T-Mobile 5.1.1. Yes, I made the mistake and flashed it the LG Support Tool and yeah... Stupid move because now my phone is completely bricked. Nothing comes up on the screen no matter what hard key combo I try BUT what's weird is when I try to power on my laptop makes the sound that it detects it but a box on the screen for my laptop pops up and say that I need to unplug and replug the USB cord to fix and if that doesn't work, then that means something is wrong with my device.
I really like this phone. Any one can drop knowledge, I'll be forever grateful. Please help.

Damn that's all bad I just gotta Stylo and I was thinking about using kingroot to root it right now too

poppyseeds said:
Recently, I bought the LG Stylo from Boost on Craigslist. Before the transaction was completed, I checked the IMEI and everything checked out clean. Like a lot of folks here on this site, as soon as I got home, I attempted to root. Prior to me rooting, I got an OS update to marshmallow and I went ahead and did it. Once the update was completed, I rooted with Kingo Root and root was achieved.
Not long after (within 24 hours), I noticed that my phone was getting very laggy and choppy so I decided to reboot. When I did that, the "LG Life's Good" boot image showed up like usual. Then the screen went blankb and turned back on to the boot image but the bottom said "SECURITY ERROR" then couple seconds later z the screen goes off again and it comes back on to the previous boot image. It pretty much is doing a boot loop. Initially, I was able to access the stock recovery and I did a hard reset but that didn't help because the outcome was the same. Then an hour or so afterwards, my access to the stock recovery was gone. Now when I try to boot recovery, it says LOADING RECOVERY but then instead of going to recovery, the Android guy pops up and right below him it says ERASING then it boots into the boot loop cycle.
At this point, all I can do is boot into download mode and from my understanding, all I can do is install the firmware. Since I was on Marshmallow, I looked online for days for the boost mobile 6.0 stock firmware. What I failed to realize is that what I found was completely not meant for the boost mobile 6.0 variant instead it was for T-Mobile 5.1.1. Yes, I made the mistake and flashed it the LG Support Tool and yeah... Stupid move because now my phone is completely bricked. Nothing comes up on the screen no matter what hard key combo I try BUT what's weird is when I try to power on my laptop makes the sound that it detects it but a box on the screen for my laptop pops up and say that I need to unplug and replug the USB cord to fix and if that doesn't work, then that means something is wrong with my device.
I really like this phone. Any one can drop knowledge, I'll be forever grateful. Please help.
Click to expand...
Click to collapse
1st off, kingroot won't root Marshmallow yet, it only goes up to Lollipop 5.1. You got the temp root we all got using the newest kingroot. I used it too and I've bricked and sent my phone back to LG twice, because of kingroot. There are many others with this problem. You are gonna have to take a chance and send it to LG. You'll have to lie, and tell them you had a bad MM- OTA update. I wouldn't say anything else and make up a receipt, unless you can get an original receipt, or don't include a receipt, even though it asks for one. Some one on Android forums sent theirs in without a receipt and it wasn't a problem, I guess since stylos are not out of warranty since they haven't been in production a year yet. Go online to lg repairs, and/ or call them. There is no custom recovery for a boost/sprint/virgin stylo because it has a locked bootloader, so you'll have to take a chance or wait forever. If you send it to LG they will send you a prepaid label and if they won't fix it they'll send it back, That's all I got, Good Luck

Thank you jmacie. After you said that many other have this exact issue including yourself, I felt that maybe this isn't something that an average person could fix on its own and that it needs the knowledge of an LG tech. I called LG and requested a repair and I've filled out the request form and now I'm just waiting on the stuff they'll send to customers so we can mail it in. They said it takes about 5 to 9 business days before I get it back. During those days, from your experience of sending it in 2 times already, do you get an email from them telling you whether they can fix it or not or do you find that out when you open the box once they mail it back to you?

poppyseeds said:
Thank you jmacie. After you said that many other have this exact issue including yourself, I felt that maybe this isn't something that an average person could fix on its own and that it needs the knowledge of an LG tech. I called LG and requested a repair and I've filled out the request form and now I'm just waiting on the stuff they'll send to customers so we can mail it in. They said it takes about 5 to 9 business days before I get it back. During those days, from your experience of sending it in 2 times already, do you get an email from them telling you whether they can fix it or not or do you find that out when you open the box once they mail it back to you?
Click to expand...
Click to collapse
If you don't get an email soon about shipping your phone to them, call them again.They should send an email titled "Mobile device repair instructions" That email will have a pdf with the label to print and instructions to take out your sd sim backcover, it doesn't say but take out the stylus. Take off your screen protector or they'll throw it away. The email has a tracking link that you can check the status from receipt to return. I'm sure you'll be nervous, I was but you have the new marshmallow update causing many people problems kind of covering you up. I don't know how they might evaluate your phone, but you know you don't have any other choice, none of us did, so keep positive. LG has been great to me and that fact keeps me considering buying my next phone from them too.

And that is exactly where I'm at in this whole process. I'm waiting for them to email me that pdf document for me to print out and off the LG Stylo. My quick question is since you mentioned that you've mailed your phone in TWICE already, do you remember exactly how long it took each time from the day you mailed it in to LG to the day you got it back from them?
And yes, the MM update is going to kind of cover me and my issue because I've read more negative things compared to the positive so fingers crossed. Hopefully all those positive experiences you've had would transfer to me and my case. I've wanted the phone for a while abd when I finally got it, within 48 hours, BAM! this happens. SMH

poppyseeds said:
And that is exactly where I'm at in this whole process. I'm waiting for them to email me that pdf document for me to print out and off the LG Stylo. My quick question is since you mentioned that you've mailed your phone in TWICE already, do you remember exactly how long it took each time from the day you mailed it in to LG to the day you got it back from them?
And yes, the MM update is going to kind of cover me and my issue because I've read more negative things compared to the positive so fingers crossed. Hopefully all those positive experiences you've had would transfer to me and my case. I've wanted the phone for a while abd when I finally got it, within 48 hours, BAM! this happens. SMH
Click to expand...
Click to collapse
It was 10 days total. After I filled out my form I called saying I couldn't wait around for a phone call as my contact # was my landline, and they immediately sent me the label. That live agent call did include questions about what happened. In my case I had told them that google services was stopping and after a hard reset I got a frozen on LG logo screen, which was the truth both times, but I'm certain the circumstances were aggravated by my messing with the build.prop and kingroot

lg g ls770 stylo boost mobile help need,
jmacie said:
It was 10 days total. After I filled out my form I called saying I couldn't wait around for a phone call as my contact # was my landline, and they immediately sent me the label. That live agent call did include questions about what happened. In my case I had told them that google services was stopping and after a hard reset I got a frozen on LG logo screen, which was the truth both times, but I'm certain the circumstances were aggravated by my messing with the build.prop and kingroot
Click to expand...
Click to collapse
need help please, i brick my phone after i've tried to used the lg flash tool, and now my goes black can't do anything or see anything any ideas please.

it took 4 days to get it back from broken usb port and bootloop i got stuck on
just send phone it self
No back cover
no stylus pen
no battery
no sim/sd card
they'll dispose of them all if you send anything but device itself
i made the mistake of not taking my pen stylus out of device and gotta order new one
but overall i got mine fixed for FREE and got it fixed and back within 4 days lucky me
but yea they'll fix it just depends on case by case i guess since my charge port had burn smell and marks gues that caused them to fix entire device and i sent it in with 5.1.1 and got it back with 6.0 so yea i say don't root till there safe proven method or till they let us unlock bootloader but till then just be happy with what you got

poppyseeds said:
Recently, I bought the LG Stylo from Boost on Craigslist. Before the transaction was completed, I checked the IMEI and everything checked out clean. Like a lot of folks here on this site, as soon as I got home, I attempted to root. Prior to me rooting, I got an OS update to marshmallow and I went ahead and did it. Once the update was completed, I rooted with Kingo Root and root was achieved.
Not long after (within 24 hours), I noticed that my phone was getting very laggy and choppy so I decided to reboot. When I did that, the "LG Life's Good" boot image showed up like usual. Then the screen went blankb and turned back on to the boot image but the bottom said "SECURITY ERROR" then couple seconds later z the screen goes off again and it comes back on to the previous boot image. It pretty much is doing a boot loop. Initially, I was able to access the stock recovery and I did a hard reset but that didn't help because the outcome was the same. Then an hour or so afterwards, my access to the stock recovery was gone. Now when I try to boot recovery, it says LOADING RECOVERY but then instead of going to recovery, the Android guy pops up and right below him it says ERASING then it boots into the boot loop cycle.
At this point, all I can do is boot into download mode and from my understanding, all I can do is install the firmware. Since I was on Marshmallow, I looked online for days for the boost mobile 6.0 stock firmware. What I failed to realize is that what I found was completely not meant for the boost mobile 6.0 variant instead it was for T-Mobile 5.1.1. Yes, I made the mistake and flashed it the LG Support Tool and yeah... Stupid move because now my phone is completely bricked. Nothing comes up on the screen no matter what hard key combo I try BUT what's weird is when I try to power on my laptop makes the sound that it detects it but a box on the screen for my laptop pops up and say that I need to unplug and replug the USB cord to fix and if that doesn't work, then that means something is wrong with my device.
I really like this phone. Any one can drop knowledge, I'll be forever grateful. Please help.
Click to expand...
Click to collapse
samething happened to me too, any help welcome

handyman509 said:
samething happened to me too, any help welcome
Click to expand...
Click to collapse
you have to send it to LG.This phone has a locked bootloader, so there is no custom recovery, so you can't just mess with trying to use tools made for tmobile unlocked phone. LG is very good about fixing and they have fixed mine. Also there is no permanent root for MM 6.0, so when you use kingroot that is ONLY made for up to Lollipop 5.1.1 you take a chance of bricking and there is only 1 way out , send to LG

Is there any news about this model.. I also have one bricked.. Can someone help me with this, please ?
Regards

cehajjic said:
Is there any news about this model.. I also have one bricked.. Can someone help me with this, please ?
Regards
Click to expand...
Click to collapse
Other than sending the device for repairs, or buying another phone: there's nothing else that could be done.

hard bricked ls770
Revenant Ghost said:
Other than sending the device for repairs, or buying another phone: there's nothing else that could be done.
Click to expand...
Click to collapse
https://lg-firmware-rom.com/downloads/unbrick-hard-bricked-lg-ls770-msm8916/