Related
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
Recently, as I was trying to update to the latest version of ICS 4.0.4, I found myself having to manually update to 4.0.3. I'm new to the Android platform and this 9020T Nexus S is my first Android phone, but I did manage to previously manually update to 2.3.6 from the 2.3.4 that was in the phone (apparently me and OTA updates are like oil and water). Unfortunately, I soon found out that I was working on erroneous information, and if I wanted to move to 4.0.4 while in 4.0.3, I would need to root the device, which is something that has been on my to-do list for a while now so I thought it'd be something I'd try.
Unfortunately, I'm finding that with ICS, I'm finding that it's a lot harder to access the bootloader than before. Holding the up volume key while also holding the power button while the phone is off tends to just tend on the phone, not get me to the bootloader interface. That's not to say that getting to the bootloader is impossible, but it seems that about 4 times out of 5 I just end up turning on the phone. I have put the thing inside a cheap case for protection, but I don't think that's the culprit, as the buttons are still clearly accessible. I imagine that the extra overhead from ICS 4.0.3 is perhaps enough that getting to the bootloader is rather difficult somehow now, so to that end, has anyone encountered this problem before? What did you do to try to sort this issue out?
What kind of case is it? I bought some argyle case from Amazon that made it damn near impossible to access the BL when I needed to. I bought a cheap silicone case and I can use the buttons no problem. I had the official OTA and flashed custom recovery and didn't have any problems rebooting into the bootloader. I would at least try to boot into the BL without the case just to rule it out. Also make sure you hold the volume button down until the screen for the bootloader actually loads up. I've let the button go a few seconds early and just booted up normally.
It's one of those cheap ebay hard cases that I bought online, can't post the link here thanks to anti-spam protections. I doubt that's the culprit though, I can reach the buttons on my Nexus S pretty easily since there are cutouts for the buttons. If all else fails, I'll try to see if I have an easier time with the case removed though.
Are you holding the volume key first? This has nothing to do with android, updates, rooting, etc. Maybe your power up key is biting the dust?
I think I'm mainly trying to press both at once, though I have tried pressing the volume first. Will try again to be sure.
As for the power button going, I doubt it, this is a relatively new device that hasn't given me any trouble power button wise before. Will have to try again specifically with that step though.
Ok, just tried this again. I didn't get anything conclusive out of it, though I did manage to get to the bootloader screen twice in a row. I think what's going on is that I'm not pressing enough of the (really rather cheap feeling) volume rocker to access the bootloader. Those two times stemmed from me pressing the entire upper half of the rocker rather than just the tip, so maybe it's not quite registering with the phone.
Unfortunately for this experiment, right after this experiment I checked for an update on a whim and it found a 4.0.4 OTA update . Been waiting to get that done for about a week now, so I'm glad even though my technical abilities have failed in my this case. Will continue to see if I can't get this thing rooted though!
you may try using fastboot via your computer...
Code:
fastboot reboot-bootloader
I'm actually trying to root this thing with one of those one-click root programs. I think I've got the bootloader unlocked but it's giving me a "device not found error", even though I've got the phone rebooted for a while now.
Kinda scared that I'll brick the thing if I disconnect the USB cable connected to it.
My Infinity's bootloader is unlocked and I was rooted. It was running a little slowly so I decided to do a factory reset. It rebooted and just froze on the ASUS booting screen.
Tried rebooting it and it just froze on ASUS screen again.
So I tried starting while holding power + vol down and the recovery options were there. I went over to Wipe data and it said "wiping data" then it just froze on "initiating bootloader" so I had to force a reboot.
Now it just stays stuck on the ASUS boot screen. When I attempt to hold power and vol down the recovery options never even come up now. It just stays stuck on the ASUS screen.
When I hold down the power button the device never stays off. The screen will turn off, it'll vibrate, and then just try to boot up again.
I tried putting a paper clip in the hard reset hole to press the button and it will reset the device but my issues are still the same.
Is there some way to recover the device either with a computer or by putting files on the MicroSD card or something? I heard something about that but can't find any solid info on what to do. Any help is appreciated.
wushdishmeen said:
My Infinity's bootloader is unlocked and I was rooted. It was running a little slowly so I decided to do a factory reset. It rebooted and just froze on the ASUS booting screen.
Tried rebooting it and it just froze on ASUS screen again.
So I tried starting while holding power + vol down and the recovery options were there. I went over to Wipe data and it said "wiping data" then it just froze on "initiating bootloader" so I had to force a reboot.
Now it just stays stuck on the ASUS boot screen. When I attempt to hold power and vol down the recovery options never even come up now. It just stays stuck on the ASUS screen.
When I hold down the power button the device never stays off. The screen will turn off, it'll vibrate, and then just try to boot up again.
I tried putting a paper clip in the hard reset hole to press the button and it will reset the device but my issues are still the same.
Is there some way to recover the device either with a computer or by putting files on the MicroSD card or something? I heard something about that but can't find any solid info on what to do. Any help is appreciated.
Click to expand...
Click to collapse
Not looking too good, possible bricked and need to send in. Give it another try, as soon as the device turn off, hold volum down and power button, see if some how magically boot back into recovery?
Edit: is your pc detecting your device?? just plug in the usb and let it boot up.
buhohitr said:
Not looking too good, possible bricked and need to send in. Give it another try, as soon as the device turn off, hold volum down and power button, see if some how magically boot back into recovery?
Edit: is your pc detecting your device?? just plug in the usb and let it boot up.
Click to expand...
Click to collapse
If that's true then this thing is pretty crappy. I've only had it for a few months and I never flashed any custom ROMs to it and all I did was the factory reset which is a stock feature. I unlocked the bootloader with ASUS's official tool.
My Galaxy S3 is nearly impossible to brick... there's always a way to boot into either stock or custom recovery. Then you always have the option to flash it back to stock using Odin.
It's not showing up in My Computer either. Isn't there some way to force a flash by loading some files onto the MicroSD card? There has to be some last resort option other than sending it back.
wushdishmeen said:
If that's true then this thing is pretty crappy. I've only had it for a few months and I never flashed any custom ROMs to it and all I did was the factory reset which is a stock feature. I unlocked the bootloader with ASUS's official tool.
My Galaxy S3 is nearly impossible to brick... there's always a way to boot into either stock or custom recovery. Then you always have the option to flash it back to stock using Odin.
It's not showing up in My Computer either. Isn't there some way to force a flash by loading some files onto the MicroSD card? There has to be some last resort option other than sending it back.
Click to expand...
Click to collapse
There are but I don't think any one of these options apply:
1. Do you have nvflash backup? --nope
2. Do you have recovery ?--nope (probably corrupted bootloader due to factory wipe)
3. Can you pc see your device through ADB or fastboot ?-- I don't think so either.
So without the 3 mentioned above, your device is bricked. Just curious, what kind and what version of your recovery?? also what bootloader version you're using before the crash?
buhohitr said:
There are but I don't think any one of these options apply:
1. Do you have nvflash backup? --nope
2. Do you have recovery ?--nope (probably corrupted bootloader due to factory wipe)
3. Can you pc see your device through ADB or fastboot ?-- I don't think so either.
So without the 3 mentioned above, your device is bricked. Just curious, what kind and what version of your recovery?? also what bootloader version you're using before the crash?
Click to expand...
Click to collapse
I had the latest jellybean firmware and my device was up to date. I don't know what version my bootloader is... I'm guessing the latest version since I updated to jellybean? My recovery WAS working... I went into the settings and chose "Wipe data" and it said it was wiping data... but then froze on initializing boot or something.
I can get my computer to recognize it in APX mode if I start with Power button and Vol Up. But my computer doesn't have the drivers so it says "installing device" and APX driver is missing. Plus the screen on my tablet is just pitch black when I boot it in APX mode. Can I do anything with APX mode? Maybe use somebody else's NVflash backup? There has to be a way if ASUS is able to "repair" it when they get it. If someone here can figure it out for me I'll pay them $50 via PayPal or something.
This is such bullcrap. I'm always able to recover from a brick with any other android device. Why is this thing basically programmed to force a repair? I contacted ASUS and somehow the customer service rep knew my device's bootloader was unlocked. I'm guessing when you use the ASUS Bootloader tool it sends ASUS your serial number so they know you unlocked the device.
So the guy is claiming I am going to be charged $200 for the repair/replacement because my device is unlocked??? Are you kidding me? I rather just throw this thing out the window for fun.
ASUS entices you with an official bootloader unlock tool then clearly makes it so the device will brick if you basically try any sort of factory wipe. Plus the bootloader tool doesn't offer the option to re-lock the bootloader like every other device and third party unlock app does. Clearly making it so once you take the plunge you're screwed if you ever run into issues.
wushdishmeen said:
I had the latest jellybean firmware and my device was up to date. I don't know what version my bootloader is... I'm guessing the latest version since I updated to jellybean? My recovery WAS working... I went into the settings and chose "Wipe data" and it said it was wiping data... but then froze on initializing boot or something.
I can get my computer to recognize it in APX mode if I start with Power button and Vol Up. But my computer doesn't have the drivers so it says "installing device" and APX driver is missing. Plus the screen on my tablet is just pitch black when I boot it in APX mode. Can I do anything with APX mode? Maybe use somebody else's NVflash backup? There has to be a way if ASUS is able to "repair" it when they get it. If someone here can figure it out for me I'll pay them $50 via PayPal or something.
This is such bullcrap. I'm always able to recover from a brick with any other android device. Why is this thing basically programmed to force a repair? I contacted ASUS and somehow the customer service rep knew my device's bootloader was unlocked. I'm guessing when you use the ASUS Bootloader tool it sends ASUS your serial number so they know you unlocked the device.
So the guy is claiming I am going to be charged $200 for the repair/replacement because my device is unlocked??? Are you kidding me? I rather just throw this thing out the window for fun.
ASUS entices you with an official bootloader unlock tool then clearly makes it so the device will brick if you basically try any sort of factory wipe. Plus the bootloader tool doesn't offer the option to re-lock the bootloader like every other device and third party unlock app does. Clearly making it so once you take the plunge you're screwed if you ever run into issues.
Click to expand...
Click to collapse
Yes, I feel you man, did you had CWM custom recovery? When you did the factory reset, did you do it in the system settings or you did it through recovery (wipe data icon)? APX mode is for nvflash backup recovery and nvflash is specific per device, so you can't use someone else nvflash. I know you're mad, but it's still cheaper to get it repair than to buy another device with the same amount of money for the same meat.
ASUS Infinity Won't Boot Into Recovery BRICK ($50 IF YOU CAN HELP FIX IT)
buhohitr said:
Yes, I feel you man, did you had CWM custom recovery? When you did the factory reset, did you do it in the system settings or you did it through recovery (wipe data icon)? APX mode is for nvflash backup recovery and nvflash is specific per device, so you can't use someone else nvflash. I know you're mad, but it's still cheaper to get it repair than to buy another device with the same amount of money for the same meat.
Click to expand...
Click to collapse
Yea I am seriously baffled by this. ASUS just lost another customer. I was doing the reset so I could sell the device and put the money towards something else. It figures this happens...It's almost like the ASUS gods are trying to screw me over so I am stuck with their crap device. This is shady business considering all my other android devices are so easily recoverable and they don't even offer a tool to unlock the bootloader. You have to do it via a third party method and somehow even that is recoverable easily. You don't find it strange that ASUS offers the tool themselves and it's the only tablet that is unbrickable?
Again... $50 to the first person who can help me unbrick this thing. I will send it via PayPal for sure. The money is not the issue it's the principle of giving ASUS $200 more of my money when I know for a fact they programmed this thing to brick so they could pick my pockets. I'm getting really angry just thinking about it and I am close to smashing this thing with a hammer and filming it for YouTube.
Here is the exact chain of events.
1) I went into Android settings, backup/restore, and then choose Factory Reset. It restarted the tablet and just froze on the ASUS screen where it says "the device is unlocked" in the top left corner.
2) I waited 15 minutes and nothing happened. So I was forced to hard reset. After resetting the same crap happened and it just stayed on the ASUS logo screen.
3) I tried booting it with Power + Vol Down and got the recovery options. (i seriously wish I stopped here and checked the forum because I could of possibly fixed it). Figuring it would help, I went over to the WIPE DATA option in the recovery menu.
4) It said "wiping data.." and then said it was initializing bootloader or something and it just froze at that point.
5) Waited another 15 minutes and nothing happened. At this point I wasn't worried because every other device I have I would have ODIN as the last resort and it ALWAYS works.
6) Reboot the device again and that's where I'm at now. It stays on the ASUS boot screen and goes nowhere. I've tried getting back into recovery with Power + Vol Down but the options never appear again. Just goes to the normal boot screen no matter what I do and hangs there. It's clearly setup to brick itself which is incredibly ridiculous.
Do you think a method to fix it will come out eventually or is it impossible to unbrick this thing? Would replacing the motherboard from another tablet that was never unlocked fix the issue? I see the motherboard for this tablet selling for $175 and the iFixit teardown shows how to take it apart. It doesn't look too difficult.
I just cannot believe that an hour ago I had a $500 tablet and now the thing is worthless unless I want to shell out another $200. I seriously wish I didn't buy this thing. Maybe I can take it apart and sell the parts separately as is and hope to salvage my money back.
buhohitr said:
Yes, I feel you man, did you had CWM custom recovery? When you did the factory reset, did you do it in the system settings or you did it through recovery (wipe data icon)? APX mode is for nvflash backup recovery and nvflash is specific per device, so you can't use someone else nvflash. I know you're mad, but it's still cheaper to get it repair than to buy another device with the same amount of money for the same meat.
Click to expand...
Click to collapse
Also I did have CWM because I remember going through a tutorial and it being different than all my other devices. I had the RCK icon as the first option when I booted with Power + Vol Down.
The options were an RCK icon, a USB icon, something else I don't remember, and then Wipe Data/reset icon. I chose the wipe data icon and that's when my device was bricked. But FIRST I used the factory reset in the android settings under Backup/restore and it froze during that which is what caused me to try the factory wipe in the recovery options.
Would not having CWM improve my options to unbrick it? Or is having CWM a good thing?
It's bricked in my opinion.
You possibly had an old version of cwm that was incompatible with the JB bootloader. You asked the bootloader to wipe which asked the incompatible recovery to do it and it has corrupted the bootloader partition.
Without nvflash backups which you don't have you have no other choice other than to pay Asus to fix it (they will probably switch the motherboard) or sell it for scrap.
I don't think anyone on here can get you unbricked. There is always a risk something can go wrong when unlocked with custom recoveries which is why Asus make you agree to a waiver.
Sorry.
I've decided the best course of action is to part out the tablet. The digitizer alone goes for $130 on eBay and I could make $200 if I just sell the front panel, LCD, and digitizer as one assembly. It would actually be super useful to someone with a cracked screen since mine is flawless and you can remove a screen by simply popping a few clips inside the hinge holes for the keyboard dock and then a few around the device. Then they would just have to take mine, connect a ribbon cable, and then snap it into place.
Then I can probably sell the rest of the parts here or there for at least $100 and that's 80% of my money back already. The only other option is to just hold onto the thing and hope that someone here figures out a fix for this issue in the future. But I rather have the money now and just be done with this crappy product. Never buying ASUS again and I'm steering everyone else I know away from them as well.
If I paid ASUS the $200 to replace the motherboard and then sold the fully functional repaired tablet I would only get about $390 if I'm lucky. Newegg sells them brand new for $450 now already and I paid $490 for it not even 6 months ago. So I'd actually LOSE money if I sold it brand new even if I didn't need the repair. Fact is people need parts for their tablet more than they need the tablet itself.
sbdags said:
It's bricked in my opinion.
You possibly had an old version of cwm that was incompatible with the JB bootloader. You asked the bootloader to wipe which asked the incompatible recovery to do it and it has corrupted the bootloader partition.
Without nvflash backups which you don't have you have no other choice other than to pay Asus to fix it (they will probably switch the motherboard) or sell it for scrap.
I don't think anyone on here can get you unbricked. There is always a risk something can go wrong when unlocked with custom recoveries which is why Asus make you agree to a waiver.
Sorry.
Click to expand...
Click to collapse
Don't be sorry it's not your fault. It's ASUS' fault for releasing a bootloader tool that voids your warranty and then sets your device up to brick by removing your recovery options after a normal factory wipe. Why else would they release a tool that they are fully aware could brick your device with no chances of recovery? Especially since it doesn't let you re-lock the bootloader. Your serial number is sent to them the minute you unlock your device so it's not like someone would try to re-lock it to hide the fact that they locked it. So the only reason could be to make money off repairs.
Thanks for the attempted help guys it is very much appreciated. ASUS left a bad taste for sure. I own a lot of their products and I'm just really disappointed.
wushdishmeen said:
I've decided the best course of action is to part out the tablet. The digitizer alone goes for $130 on eBay and I could make $200 if I just sell the front panel, LCD, and digitizer as one assembly. It would actually be super useful to someone with a cracked screen since mine is flawless and you can remove a screen by simply popping a few clips inside the hinge holes for the keyboard dock and then a few around the device. Then they would just have to take mine, connect a ribbon cable, and then snap it into place.
Then I can probably sell the rest of the parts here or there for at least $100 and that's 80% of my money back already. The only other option is to just hold onto the thing and hope that someone here figures out a fix for this issue in the future. But I rather have the money now and just be done with this crappy product. Never buying ASUS again and I'm steering everyone else I know away from them as well.
If I paid ASUS the $200 to replace the motherboard and then sold the fully functional repaired tablet I would only get about $390 if I'm lucky. Newegg sells them brand new for $450 now already and I paid $490 for it not even 6 months ago. So I'd actually LOSE money if I sold it brand new even if I didn't need the repair. Fact is people need parts for their tablet more than they need the tablet itself.
Don't be sorry it's not your fault. It's ASUS' fault for releasing a bootloader tool that voids your warranty and then sets your device up to brick by removing your recovery options after a normal factory wipe. Why else would they release a tool that they are fully aware could brick your device with no chances of recovery? Especially since it doesn't let you re-lock the bootloader. Your serial number is sent to them the minute you unlock your device so it's not like someone would try to re-lock it to hide the fact that they locked it. So the only reason could be to make money off repairs.
Thanks for the attempted help guys it is very much appreciated. ASUS left a bad taste for sure. I own a lot of their products and I'm just really disappointed.
Click to expand...
Click to collapse
Unfortunately it's not Asus, unlocking or the bootloader that is the problem - it's the older incompatible version of CWM that has caused the issue. It didn't understand what you asked it to do as it is not compatible with Jelly Bean. You need to get this part clear. Many people wipe successfully from Android or the bootloader from ICS and JB regularly. Asus don't write code into their bootloader to deliberately brick your device when wiped. They also don't support custom recoveries that are not compatible with their bootloaders.
It is a documented issue that has caused others like yourself to brick your device when wiping JB when still essentially on an ICS recovery. Unfortunately there is no way you would know this without some research and Asus can't be held responsible for it as you waived your warranty when you unlocked for this very reason. Why should they pay for something you did that they don't support?
I know that doesn't help solve your problem but in this case it is not Asus who is at fault.
Re: ASUS Infinity won't boot into recovery or startup ($50 to person who helps fix it
sbdags said:
Asus can't be held responsible for it as you waived your warranty when you unlocked for this very reason. Why should they pay for something you did that they don't support?
I know that doesn't help solve your problem but in this case it is not Asus who is at fault.
Click to expand...
Click to collapse
Asus should really give us our SBK when we unlock our devices - the we could fix this ourselves using nvflash.
_that said:
Asus should really give us our SBK when we unlock our devices - the we could fix this ourselves using nvflash.
Click to expand...
Click to collapse
Yes but I can totally understand why they don't as it would be a nightmare to support. It's a shame it cannot be reverse engineered.
sbdags said:
Yes but I can totally understand why they don't as it would be a nightmare to support. It's a shame it cannot be reverse engineered.
Click to expand...
Click to collapse
They don't support an unlocked device anyway. It would be as easy as returning the SBK from the server together with the unlock token.
As I said I understand the idea of the warranty being voided by using the unlock tool. But ASUS certainly has programmed the device to brick when using custom recoveries which is something you just said yourself. They are being irresponsible by offering this tool and not telling customers that a custom recovery would brick the device for good. You honestly think they don't know this will happen?
My Galaxy S3 has an unlocked bootloader (through a third party method nonetheless), is rooted, has CWM recovery, is on Jellybean, and the recovery options never disappear with a factory wipe. So clearly it's possible. Even if the device won't boot into android it will still be recognized by Odin because it has download mode built in as a start up option. Holding power + vol up will allow me to enter download mode and I can flash the stock ROM again.
Unlike APX mode I don't need some encrypted nvflash backup just to recover my device. I can simply use the stock ROM to recover my device back to stock no matter what ROM or recovery I'm running. I maybe gave you the impression that I didn't know what I was doing. This issue is something that anyone could fall into and frankly ASUS should be telling people not to use factory wipe if they install a custom recovery. Why would they offer a bootloader unlock for any other reason than to cater to people who want to install custom recoveries and flash ROMs? There's no other use for it to a typical consumer.
The ASUS Infinity loses it's ability to communicate with your computer when this happens. That's the problem here. They need to either need to make it impossible to flash a custom recovery altogether or put a warning on their website near the download that says "Custom recoveries could brick your device when doing a factory wipe". Seeing as it's a well documented issue like you claim.
We are all entitled to our opinion. I'm not buying ASUS products anymore. It's not like I did something wrong and screwed it up. I did something that's possible on every other modern android device and was kicked in the nuts for it.
_that said:
Asus should really give us our SBK when we unlock our devices - the we could fix this ourselves using nvflash.
Click to expand...
Click to collapse
So you're saying that it is actually possible to fix it if you had access to something that ASUS is voluntarily withholding from TF700T owners? So here is my question then. Why is it that ASUS is charging customers for motherboard replacements in order to fix this issue rather than simply reprogramming the existing motherboard?
I have never in my 18 years of working with computers seen a software issue corrupt or destroy a piece of hardware, whether directly or indirectly related to it. Whether we as consumers have the tools available to recover from the software issue is not the point. Nor am I saying that ASUS should fix it for free, since they clearly state that using the tool will void your warranty. My point is that ASUS should certainly have the ability to simply reprogram our motherboards for a reasonable fee, rather than forcing a motherboard replacement and charging 50% of the tablet's price to fix it.
To claim that the motherboard needs to be replaced is the same as me saying your computer's motherboard needs to be replaced because your Windows installation was corrupted. It just doesn't happen and Windows certainly also has it's share of bootloader errors. There is always a way to recover from software issues and salvage the hardware, unless it's some incredibly rare series of failures that lead to an electrical problem that fries the hardware. Which is certainly not the case here or anything remotely close to it.
MOD EDIT: DELETED
What I said was they should not be charging $200 for a replacement motherboard for a software related issue. They should be charging a reasonable fee to reprogram the existing component. From what I hear they also permanently lock the boot loader on the replacement motherboard. This is not helpful at all considering you lose the ability to customize your device now that you've learned what not to do.
Also warning people that a custom recovery can brick your device is not that crazy even though you seem to think it is. It's a well documented issue and the only thing that bricks the device. Not to mention the only purpose of unlocking the boot loader is so you can flash custom recoveries. So it's not like they have to run through a long list of possible problems like your over exaggeration implies.
Anyway... I managed to disassemble the tablet without breaking anything.
Question: Does anyone know if there is any way to reprogram the motherboard? Even with some sort of software or tool to connect it to a computer? Does swapping the motherboard with one that was never unlocked give the device a new serial status or will ASUS still think it's an unlocked device?
I'm assuming not obviously but I might as well ask. I guess my choices are to either spend $160 on a new motherboard and swap it out and sell it, or further disassemble and sell the parts. If anyone needs a flawless brand new digitizer and LCD panel let me know.
Thought I'd share some photos so others in the same situation feel more comfortable taking it apart. It was actually really easy. The motherboard is the long dark green component running along the top.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
wushdishmeen said:
So you're saying that it is actually possible to fix it if you had access to something that ASUS is voluntarily withholding from TF700T owners?
Click to expand...
Click to collapse
From my understanding of the situation, after all that I read about the Tegra 3, APX mode, NVFlash etc.: yes, it would be possible if you knew the unique 128 bit AES "secure boot key" that is burnt into the fuses of your Tegra 3 chip. This key together with NVFlash enables you to write arbitrary partitions or blocks to the eMMC.
wushdishmeen said:
So here is my question then. Why is it that ASUS is charging customers for motherboard replacements in order to fix this issue rather than simply reprogramming the existing motherboard?
Click to expand...
Click to collapse
I can only guess that their service centers do not have access to the database that stores the mapping from serial numbers to SBKs, and that they are generally unorganized - which shows because so many people have problems unlocking their tablets.
wushdishmeen said:
I have never in my 18 years of working with computers seen a software issue corrupt or destroy a piece of hardware
Click to expand...
Click to collapse
It happens... https://bugs.launchpad.net/ubuntu-cdimage/+bug/1040557
wushdishmeen said:
To claim that the motherboard needs to be replaced is the same as me saying your computer's motherboard needs to be replaced because your Windows installation was corrupted.
Click to expand...
Click to collapse
I agree - it's ridiculous and only the consequence of trying to lock users out of their own devices. I think the whole crap is due to DRM, to make media companies happy.
wushdishmeen said:
Also warning people that a custom recovery can brick your device is not that crazy even though you seem to think it is. It's a well documented issue and the only thing that bricks the device.
Click to expand...
Click to collapse
For Asus, there are no "well documented issues". They don't even document the issues they fix with firmware updates. Their customer service is a joke. And they don't need it - they are a big company. Big companies do not succeed by providing good customer service, they succeed by sucking slightly less than other big companies.
wushdishmeen said:
Question: Does anyone know if there is any way to reprogram the motherboard? Even with some sort of software or tool to connect it to a computer?
Click to expand...
Click to collapse
The "official" way is simply via USB in APX mode, but that's impossible without the SBK due to the encryption. The low-level way would be JTAG, but I have read that it is disabled on encrypted devices, and I don't even know where the connector is.
If you didn't know yet, here are more pictures of the internals:
http://www.ifixit.com/Teardown/Asus+Transformer+Infinity+TF+700+Teardown/10306/1
wushdishmeen said:
Does swapping the motherboard with one that was never unlocked give the device a new serial status or will ASUS still think it's an unlocked device?
Click to expand...
Click to collapse
Every Tegra 3 has a unique chip serial number. And the Asus serial number is stored on the eMMC.
Thanks for actually reading my post and providing all that useful info. I appreciate that you took the time and also understood where I was coming from. My first few posts were a reaction to the realization that it was bricked and I might have to pay $200 to fix it. But everything after that was a legitimate concern for the way ASUS is choosing to handle this issue. Hopefully anyone else who ends up in this situation will see this thread and it'll help them. I went through the motions for them and will hopefully end up with a good result either by swapping the motherboard myself or selling the parts for a good profit. I'll let everyone know the outcome either way.
_that said:
It happens... https://bugs.launchpad.net/ubuntu-cdimage/+bug/1040557
Click to expand...
Click to collapse
I didn't read what the entire issue was. But I can make a guess that this is an issue that can be resolved and the problem is just that the common consumer doesn't have the tools to fix it themselves. My actual point was not that we should be able to fix the ASUS tablet ourselves, but that ASUS should be able to fix it without needing to replace the motherboard.
_that said:
The "official" way is simply via USB in APX mode, but that's impossible without the SBK due to the encryption. The low-level way would be JTAG, but I have read that it is disabled on encrypted devices, and I don't even know where the connector is.
If you didn't know yet, here are more pictures of the internals:
http://www.ifixit.com/Teardown/Asus+...ardown/10306/1
Click to expand...
Click to collapse
When you said JTAG I was thinking of the tools I have for my XBOX to JTAG and flash the NAND. That's unfortunate that it's not possible.
I'm aware of the iFixit article. I looked at it before taking the tablet apart and it helped me avoid breaking the side clips like he did. The reason I took the pictures wasn't because I thought there were none. It was basically just visual proof to instill confidence and encourage people to take theirs apart as well. I figure if they see a regular person like me take it apart with no hesitation they might opt to replace their own motherboard rather than pay ASUS $200.
_that said:
Every Tegra 3 has a unique chip serial number. And the Asus serial number is stored on the eMMC.
Click to expand...
Click to collapse
Is the eMMC part of the motherboard or separate? I'm just curious if I could continue the warranty of whatever motherboard I install in the tablet. If I could even figure out the serial number to it.
wushdishmeen said:
I'm aware of the iFixit article.
...
Is the eMMC part of the motherboard or separate?
Click to expand...
Click to collapse
Read the whole article, there are pictures of the motherboard with the chips explained - one of them is the eMMC.
wushdishmeen said:
I'm just curious if I could continue the warranty of whatever motherboard I install in the tablet. If I could even figure out the serial number to it.
Click to expand...
Click to collapse
I don't think you have any warranty on a "naked" motherboard at all except if it was installed by an authorized service center.
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/
I have had extremely bad luck and all sorts of dramas including frying the mainboard of my T-865 while attempting to flash TWRP on my way to get it rooted. I will get my tablet back a few days later after paying 550 bucks for the repair on top of the purchase price of the tablet itself 10 days ago (of course of out warranty since I unlocked the bootloader and tried to install "unauthorized software" according to their warranty terms)
My simple question now is, is there is a way to get the T-865 rooted without having to install a custom recovery (which under no circumstances I will attempt again)? All I need is root, nothing else.
Thanks for the advice
@VeEuzUKY may I ask how your motherboard got fried?
Did you follow the steps mentioned in this thread https://forum.xda-developers.com/galaxy-tab-s6/development/recovery-twrp-3-3-1-t3975587?
Usually if something goes wrong while attempting root, Odin flashing stock rom will bring back the device to working condition..
jaidev.s said:
@VeEuzUKY may I ask how your motherboard got fried?
Did you follow the steps mentioned in this thread https://forum.xda-developers.com/galaxy-tab-s6/development/recovery-twrp-3-3-1-t3975587?
Usually if something goes wrong while attempting root, Odin flashing stock rom will bring back the device to working condition..
Click to expand...
Click to collapse
Dearest jaidev.s.. it's quite of a long story (and a surprising one at that) as I have been flashing, testing and even helping build several custom ROMs for Samsung deviced in the past 12 years without ever getting stuck in a truly unforeseen situation.
To make a very long story short, after doing all my homework through all the available threads and feedback I could find on the matter, I ventured to unlock the bootloader, install TWRP custom recovery, required custom kernel and magisc root files for my T865. And yes, I followed precisely the available guides on it from our community. Things all went pretty much as planned and I eventually booted into a successful fully rooted session on my tablet. I tested all of the tablet's native apps and functionality, installed Root Explorer and a few other apps that I had backed-up APKs for. My session was about 30 minutes long, I never connect to any data in stayed always offline, after which I decided to reboot the tablet. And then, meltdown.
The tablet immediately refused to restart again, completely bypassing the initial standard Samsung splash screen, and going directly into a warning screen that it had been locked due to the "installation of unauthorised software". From that point on any attempt to get the tablet from that state or to simply flash the stock firmware, failed completely. With the help of some other developers we all ventured together if my firmware was actually from another region, all of which I tried without any success. Eventually the tablet got stuck in a state that would not even turn off anymore even if I forced it via the volume down and power button commands. I eventually just waited out until the battery exhausted itself and then that was that.
Upon taking it to Samsung for repair where within seconds they realised that I had unlocked the bootloader and had tried to install a custom recovery, they came back about half an hour later explaining me that the hardware itself would not read or write any data any more despite their efforts, for which they would have to replace the mainboard.
I am yet to try and understand how the the tablet stopped functioning upon a reboot when up to that point everything had been flashed correctly and I had managed to do a session with everything properly configured. This said, I'm facing a $550 repair to what was an $800 tablet purchased just 10 days ago. I will obviously now not venture to try to install custom recovery again. I believe my tablet might have been a one-off with some sort of a preexisting hardware glitch that got ignited by the custom flashing that I did.. I really don't know and it really doesn't matter. At this point as I am about to collect the repaired tablet in a couple of days, the only thing I am interested in doing (a must for me on any device) is to achieve root and let it be. I don't want custom recoveries, kernel overrides or anything else other than having root. Thus my search on what will be be the best venue I have how to get the tablet safely rooted without messing with TWRP again or trying to mod the bootloader. And that's pretty much it..
And let me state, I have received nothing other than truly overwhelming support and help from lots of members of the community on my particular case for which I am extremely thankful and appreciative.
PS - I also have a Note 10 plus, recently purchased to finally replace my daily driver Note 8 that I've had for almost 3 years. Needless to say that I am absolutely dreading about the thought of installing a custom recovery on it as well and achieving root, and having again any kind of bad luck to get myself stuck in another nightmare again. I will first deal with the tablet, and if that eventually goes well, I will try to gain the necessary courage to get myself to flash TWRP and root on it without destroying it next. More than 12 years doing these things with nothing but success on dozens of devices, and suddenly here I am.
Part of me is wondering if Knox's eFuse tripping could have been the reason the board got fired? Perhaps a fault in that. Can't see any other reason reason why modifying software would cause a catastrophic hardware failure.
Anyway, as far as I'm aware the only other way to achieve root is to patch your stock OS in Magisk, then flash the modified file as detailed in this thread...
https://forum.xda-developers.com/galaxy-note-10+/how-to/guide-how-to-root-note-10-t3960031
Which is originally linked from This Thread
I've not tried it myself and it's a process from before TWRP was developed for the Tab S6 - So, you should do further research on it before jumping in to ensure nothing has changed.
Precisely why I am not installing twrp. The threads pages are having so many varied info and people getting bricks following steps, i feel discouraged to try root.
Tab s6 gonna be my first phone in 10 years that m gonna not root. I am using android since éclair and rooting.
"Samsung splash screen, and going directly into a warning screen that it had been locked due to the "installation of unauthorised software". From that point on any attempt to get the tablet from that state or to simply flash the stock firmware, failed completely. "
I had the same experience. I installed everything and rebooted to see this. Was only annoyed that oem unlock won't be an available instantly but it was. I went to download mode flashed stock, installed twrp again and it was fine. If you couldn't go to download mode (with cable inserted into pc! I assume you must know it because you flahed it, thie was another new idiotic introductement by gnus, i thought i have broken tablet because i couldn't get into download mode, when i found out cable must be in not mentioned anywhere in the instructions, just like we must know it, when it never in the universe been the case) then it's weird bug. Because what you are describing sound like standard behavior for these tablets, but why you couldn't get out of it right away i don't kno, because i could. Moreover i had the same on s9 snap. On s9 i also has issues when oem unlock will never appear, until i run some command checking it status and it got instantly unlocked. I shared it tp developer but he only laughed. When i knio there is nothing to laugh, sung's firmware has millions of such unexplainelable behaviors, a lot of people are faced with it. If you had another tablet and got the same result then just pick up non tgy one and it will be good, i promise. Also who knows why you want note 10 and t s6
Extreemator said:
"Samsung splash screen, and going directly into a warning screen that it had been locked due to the "installation of unauthorised software". From that point on any attempt to get the tablet from that state or to simply flash the stock firmware, failed completely. "
I had the same experience. I installed everything and rebooted to see this. Was only annoyed that oem unlock won't be an available instantly but it was. I went to download mode flashed stock, installed twrp again and it was fine. If you couldn't go to download mode (with cable inserted into pc! I assume you must know it because you flahed it, thie was another new idiotic introductement by gnus, i thought i have broken tablet because i couldn't get into download mode, when i found out cable must be in not mentioned anywhere in the instructions, just like we must know it, when it never in the universe been the case) then it's weird bug. Because what you are describing sound like standard behavior for these tablets, but why you couldn't get out of it right away i don't kno, because i could. Moreover i had the same on s9 snap. On s9 i also has issues when oem unlock will never appear, until i run some command checking it status and it got instantly unlocked. I shared it tp developer but he only laughed. When i knio there is nothing to laugh, sung's firmware has millions of such unexplainelable behaviors, a lot of people are faced with it. If you had another tablet and got the same result then just pick up non tgy one and it will be good, i promise. Also who knows why you want note 10 and t s6
Click to expand...
Click to collapse
Thanks for all the info. The Note 10+ is my girlfriend's phone. I use sometimes as well when I don't feel like holding the tablet. The Galaxy A 8" with S-Pen is the perfect device.. not too small, not too big and has the pen. Unfortunately stupid Samsung decided to make it ridiculously low-end with atrocious specs, can't use it for any productivity.
VeEuzUKY said:
Thanks for all the info. The Note 10+ is my girlfriend's phone. I use sometimes as well when I don't feel like holding the tablet. The Galaxy A 8" with S-Pen is the perfect device.. not too small, not too big and has the pen. Unfortunately stupid Samsung decided to make it ridiculously low-end with atrocious specs, can't use it for any productivity.
Click to expand...
Click to collapse
and now Samsung has 11 and 12 inch tablet versions for the s7...lol (next thing will be maybe a 14 inch or 17 inch 'tablet') 8 to 8.9 is the right size for a tablet. Anything bigger is basically looking at an old-school tv screen from the '70s or '80s just 6 inches or so away from your eyes with your entire face lit up by the screen lol
mac231us said:
and now Samsung has 11 and 12 inch tablet versions for the s7...lol (next thing will be maybe a 14 inch or 17 inch 'tablet') 8 to 8.9 is the right size for a tablet. Anything bigger is basically looking at an old-school tv screen from the '70s or '80s just 6 inches or so away from your eyes with your entire face lit up by the screen lol
Click to expand...
Click to collapse
Haha, I absolutely agree with you
I'd love a 17" Tablet. Lol. Personally, I don't like any Tablet less than 10" - If I want something small, I'll use my phone.
@VeEuzUKY did you get your Tab rooted?