Hi guys! I want to send my Nexus 7 (2013) to warranty service because it's bricked and I think the motherboard is destroyed. Will the service understand that the device is unlocked (bootloader) and rooted?
I could be wrong so wait for confirmation from someone else but if it won't even power on I don't think they would know, however if it powers on as far as the white Google logo you can see it is unlocked by the white padlock that is opened at the bottom, or closed lock for locked boot loader.
Sounds like it won't power on though if the main board is dead so I doubt they could know...
If it helps i had an iphone 4 that i jailbroke and it ended up bricked. It wouldnt connect to the computer or anything else. I had the same worry you have and when it was sent off i thought theyd find out. They didnt, and i got a replacement. If it doesnt connect to a computer they just dismantle them for parts. A repair engineer is more expensive to employ than a few idiots with screw drivers.
May be I am wrong about the mainboard. Yeah, I can turn it on, but I can go only to boatloader. It can be connected to computer (only fastboot mode) and there is unlocked padlock.
I guess need to lock the bootloader. But the device does not see any space (free or used) - I was connected it to computer and used a recovery mode with Skipsoft application. May be the memory is dead. It shows that cannot mount any partition. I don't know. Is there any way to lock the bootloader?
I am guessing you used Wug's root toolkit to unlock. I have seen others relock there's when there has been problems similar to yours, maybe check his thread out and ask in there.
Yep, I used his toolkit. But I tried every button in the application but nothing worked. I'll try to search deeper. I'm so afraid because I bought the device 1 month ago.
ryderbg said:
Yep, I used his toolkit. But I tried every button in the application but nothing worked. I'll try to search deeper. I'm so afraid because I bought the device 1 month ago.
Click to expand...
Click to collapse
Yeah I know the feeling
I am always worried about devices failing but after I have had it for about a year I wont be so scared and will take more risks with it usually. Only had mine for around 2 weeks and am also worried it could go off at anytime as mine is unlocked and rooted. Lots of people seem to have had problems with this device, my Xperia S never had problems
ryderbg said:
Yep, I used his toolkit. But I tried every button in the application but nothing worked. I'll try to search deeper. I'm so afraid because I bought the device 1 month ago.
Click to expand...
Click to collapse
Try this... http://www.android.gs/restore-un-br...4-3-jelly-bean-twrp-and-root-guides-included/
It might at least get it locked for you....
Thank you! I will try that as soon as I go home...
This is pretty much what danvee posted but still..
If you can use fastboot that's a good sign. You probably don't even need to send it in. Try this: http://forum.xda-developers.com/showthread.php?t=2469508&highlight=stock
You say something about no space? If the above link doesn't get you running again try this first: http://forum.xda-developers.com/showthread.php?t=2380913 Worked for me.
You can just flash twrp with "fastboot flash recovery recoveryname.img"(without quotes), wipe, then use the steps in the first link.
If that doesn't work it probably is some kind of hardware problem.
I just locked the bootloader. I used the command fastboot oem lock and there is no padlock now. Also Lock state changed to locked. I think now I can return the tablet in the shop.
ryderbg said:
I just locked the bootloader. I used the command fastboot oem lock and there is no padlock now. Also Lock state changed to locked. I think now I can return the tablet in the shop.
Click to expand...
Click to collapse
heres a funny story but what it resulted in and how i fixed it seem to apply to the problem you have.
i have a cracked screen on my nexus and it was registering a touch at intermittent intervals making the device unusable. i posted in here about the same time you did for help. while i was waiting to see if anyone knew if i could just disconnect the screen and use a bluetooth mouse with a hdmi adapter (slimport not mhl, thanks meekrawb) i connected a usb mouse with an otg cable. the mouse worked but i couldnt see how to turn off touch screen as an imput. as kitkat has been release and i hadnt updated i thought i would give it a try and see if that would reset the screen and stop the touch. It downloaded the update and when it rebooted it opened up a mod recovery screen (i forgot that i had rooted it). it asked me to slide a bar on the bootloader screen to continue. The usb mouse cursor was not present on this screen and the touch screen doesnt work so i couldnt get past it. i turned the device off and on again (what else do you do when your stuck) and it would open the google screen with the unlocked padlock but then just stay on a completely black screen. same as yours. I connected it to the computer and it recognised it. i opened wugfresh's root tool kit (old apple jb's sometimes had recovery abilities built into them so i thought this may aswell) i clicked on flash stock and unroot with the radial button on soft bricked and followed the instructions. now my device is unbricked and even the touch has stopped. Happy days hey. you'll need to unlock your boot loader again but its worth a try before going to the store, you can always lock the bootloader again if it doesnt work.
i know it didnt need all this to say "connect it to the root tool kit and try that" but i thought you would enjoy a laugh
Funny story. But my issue is hardware. The device doesn't show any space in it. No free nor used. I think the memory is dead. Also I relocked the bootloader, but now I cannot unlock it again because there is no space
Now when the tablet is with locked bootloader, it is unrooted, right?
Tommorow I will visit the warranty service and hope they don't understand about rooting and unlocking.
according to an email from "google play support India" , the device will be accepted under warranty as long as it has a stock firmware installed when you send in the device to claim the warranty.
Related
my verizon xperia is not recognized by either pc companion or seus. I am trying to do a hard reset due to the fact the lockscreen doesnt work. I have read that I can press and hold the back and search keys on front while powering on to factory reset the phone, however that does not seem to be the case. Can anyone give me some suggestions if the two button factory reset does work and that maybe I am just doing it wrong. And any suggestions as to how to get my phone to connect with seus so I can reset if teh 2 button trick is indeed not an option. Thank you to all in advance.
Doesnt anyone have an idea? I follow seus instructions. Power off wait 30 seconds, then plug in the usb cord to the pc, then press and hold the back button then inserting the usb cable into the phone... and then I wait for it to connect which it doesnt.
have you tried removing the battery wait a bit and put it back and then try again. I had something similar happen when I first got mine.
yes.... I waited beyond the 30 seconds it suggests. I eve waited about 2 hours once. Still nothing......I really want to get this device working.....it does power up. Everything seems like its supposed to work but it isn't. Thank you for helping me... I really really appreciate it.
hey, if youre comfortable, we can unlock the bootloader on it. if we do that, then you can just use fastboot and the files you can get off of my State of Development thread to return you back to stock. You could also root it. If that interests you, send me a pm with your ESN and Ill get you an unlock code.
Or do you still wanna try to figure out the **** fest that is SEUS?
I would love to unlock the bootloader. I have always had motorola android phones so even though i have never unlocked the bootloader I would love to.
Where would I find the ESN #? I am not able to get past the lock screen....so all I can do it make emergency calls
I have PM'd you my phones info. Thank you for your assistance
What is preventing you from passing the lock screen exactly? Programming?
the phone says that the pattern lock attempts has been exceeded... and the only way to unlock is to enter either a gmail info or answer the question. Neither of which I know.
Ahh! phew i thought it was more serious than that. Were you able to have the phone activated on your Verizon account okay? The esn wasnt blacklisted or anything?
And the funny thing is, even if you HAD got seus working, it would not have fixed that problem. SUES doesnt wipe the device as far as I know.
the *#06# in the emergency dialer doesnt show anything?
also the MEID is under the battery.
I have not activated the phone as I cant really use it in its current state. I did check with Verizon and the phone can be activated no problems.
I do have the MEID #, is it safe to list it here?
Also, the phone does not take the #* code, says its not an emergency number
K, i have successfully unlocked my bootloader on my phone..... I am trying to make sense of what to do next
YAY!!!!!. I unplugged and rebooted the phone after unlocking the bootloader and now my phone is back... I can sign into google now
you should use this command and reflash the stock system
fastboot flash system system.sin -w
this will erase usersettings and reinstall the stock rom.
make sure you have the rom downloaded.
edit- Never mind.
jgregoryj1 said:
YAY!!!!!. I unplugged and rebooted the phone after unlocking the bootloader and now my phone is back... I can sign into google now
Click to expand...
Click to collapse
Thats great! totally forgot that actually unlocking the bootloader performs a factory reset. So awesome! Go get you some root!
now that I have it restored, the screens touch sensitivity is all over, it keeps thinking I am trying to load up voice commands. I would like to flash a rooted ROM, and from what I have read on kernals for the r800x theres nothing worth flashing just yet. Can anyone point me in the right direction on how to flash a rooted stock rom?
Also, I am still not able to enter Flash mode with the whole back button while inserting usb cable. the light is still blue.... any suggestions?
You shouls be holding the search key.
sent from the original unlocked R800X.
i will try the search button instead. Also I flashed a kernal and now the phone is super slow. How do I flash the stock ROM and stock kernal. I am doing some reading but I am still lost. seems like I get routed to xperia arc pages...... can anyone give me some guidance. sorry to be a pain, but I am excited to learn
jgregoryj1 said:
i will try the search button instead. Also I flashed a kernal and now the phone is super slow. How do I flash the stock ROM and stock kernal. I am doing some reading but I am still lost. seems like I get routed to xperia arc pages...... can anyone give me some guidance. sorry to be a pain, but I am excited to learn
Click to expand...
Click to collapse
Hey, everything you need to know is in the many pages (and the initial post which is constantly updated) on my State of Development thread. Read through there and you will see that everyone else is also having problems with the kernels and roms making the phone unresponsively slow. The first post also has links for stock files that you might need.
Basically if you get your phone into fastboot mode (turn off, hold search key, plug in USB line, solid blue light turns on) you can do two commands to get you back to stock, and then follow the rooting instructions that I have on the R800x Rooting thread. Its linked in the state of development thread. Second item, i believe, below the link to Bin4rys.
The two commands would be "fastboot flash system system.sin" and "fastboot flash boot kernel.sin". the first command might not be necessary even, just the kernel one might fix you.
Hello I need a but of help my Nexus 7 is showing my nothing but the google logo and at the store earlier it showed the android with his chest up and a red triangle. it doesnt even show the moving colors after i turn it on it just sits and says google like a paper weight. i can turn it off and on but nothing more. the geek squad at best buy told me to ask for help here at Xda. last thing i was doing with it was opening deer hunter 2013 and next i go to see if it opened and it stuck on the google logo. can anyone help me fix my tablet? its not under store warranty only manufactures.
Well, sucks to be you.....just kidding...but that does suck. Now, on to more serious matters...
Do you have access to your bootloader? (hold the power button + the vol up button at the same time) If you do, you might want to look into rooting the tablet. Based on the content of your post, I am assuming that you haven't. There is plenty information about rooting the Nexus 7.2 tablet (and just about every other Android device). Simply Google "root Nexus 7 2013" and you will quickly find your answer.
Also, how much do you know about rooting and the sort? I want to know before I waste my time giving details about info that you are aware of.
aarsyl said:
Well, sucks to be you.....just kidding...but that does suck. Now, on to more serious matters...
Do you have access to your bootloader? (hold the power button + the vol up button at the same time) If you do, you might want to look into rooting the tablet. Based on the content of your post, I am assuming that you haven't. There is plenty information about rooting the Nexus 7.2 tablet (and just about every other Android device). Simply Google "root Nexus 7 2013" and you will quickly find your answer.
Also, how much do you know about rooting and the sort? I want to know before I waste my time giving details about info that you are aware of.
Click to expand...
Click to collapse
i dont know anything about rooting. i dont have access to the boot loader. i did a few days ago now it wont even show up, the guy and best buy tried to bring it up and its like it was showing a dead android or something chest open with a red triangle above it. he said someting about maybe have to flash a new or or something like that on to it, it wont show me anything just stays off or shows the google logo when its on
Sigh...that is the bootloader. Maybe...he could have booted into the stock recovery, which shows this or something similar for most devices. Please remember, they are reps...they may know about the software, but usually they speak from their experience or their perspective. I'm glad that he sent you here for a second opinion.
Hold the volume down button and power button to get into the bootloader. You should see some options at the top of the screen saying Start, Restart bootloader, Recovery Mode, Power Off. Not sure if those are the exact options, but it's pretty close.
Also, you need to look into rooting your device. You need to download some files first. You'll need adb, fastboot, and drivers for your Nexus.
And one last thing....what Computer OS do you use? The rooting process is slightly different for each one (Windows 7, 8/8.1, Mac OS, & Linux). If you are into computers, and you have Linux installed on a device, good for you. That is my preference when rooting, as Android is built from Linux, and naturally supported without the need for drivers.
I had similar problems when I first bought it. Going into recovery and resetting the tablet cured it. You will lost all your data BTW.
He's facing the loss of his entire tablet, so I'm sure that data loss isn't the biggest thing to worry about.
But yes, just about every solution involves a clean wipe of data.
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
_______________________________________
I'm stuck on the google logo too. I had my tablet plugged in over night and when I opened the cover this morning it woke up, but as soon I tried to access anything it rebooted and stuck.
I'm unlocked and have tried various thing. NRT doesn't recognize it as an ADB device so I don't think that will work. Fastboot works, but I keep getting "FAILED (remote: flash write failure)" when I try to use the factory flash all, or the instructions found here: http://forum.xda-developers.com/showthread.php?t=2381582
I can use fastboot to query the device and get it to return "flo" but it seems like the flash storage has failed.
if it's truly horked, can I use "fastboot oem lock" to relock it and attempt a warranty replacement?
sean67854 said:
I'm stuck on the google logo too. I had my tablet plugged in over night and when I opened the cover this morning it woke up, but as soon I tried to access anything it rebooted and stuck.
I'm unlocked and have tried various thing. NRT doesn't recognize it as an ADB device so I don't think that will work. Fastboot works, but I keep getting "FAILED (remote: flash write failure)" when I try to use the factory flash all, or the instructions found here: http://forum.xda-developers.com/showthread.php?t=2381582
I can use fastboot to query the device and get it to return "flo" but it seems like the flash storage has failed.
if it's truly horked, can I use "fastboot oem lock" to relock it and attempt a warranty replacement?
Click to expand...
Click to collapse
You can try Method 2 from this post: http://forum.xda-developers.com/showthread.php?t=2513701
I know it's for the N5, but I used this one for both my Galaxy Nexus, N5 and N7. Since they are all Nexuses (Nexi?), the same general procedures apply. I always prefer to do it all manually, step-by-step, which is why I went with Method 2 in the OP of that thread. Obviously, since this is the N7, just skip the radio flashing command. Everything else is the pretty much exactly the same. If this doesn't work in fastboot, then it's probably a hardware failure.
Hello,
So a couple of months ago I cracked the screen of my Nexus 7 2013 (32Gb), I requested a quote of a repair shop that wanted me to pay 200€ to repair it. That's about 70€ less than the price for a new one.
Instead I ordered a replacement screen from Ebay and did the repair myself which costed me about 71€. The screen was a genuine one, same type and all.
Now last week, I hadn't used the tablet for a while, I tried to turn it on but it refused. After booting it into recovery I noticed that my cache partition was corrupted. Wiping it didn't help, doing a factory reset didn't do it either.
After googling a bit I found forum threads saying the only thing you can do is having it repaired by Asus under warranty. Is this really so?
Although I didn't leave a scratch on the tablet, the two seals on the screws inside the tablet have been removed while I was repairing the screen.
So most probably I'm out of luck then? No JTAG or anything else I can try?
My tablet was running stock Android, non rooted, no unlocked bootloader, ADB was not enabled.
Best regards,
Jan
I suggest that you flash the factory image following the instructions in the sticky threads.
You flash it from you computer and I think there is a good chance that it will fix your tablet.
Yes, flashing the stock factory image is your best bet. I do believe that you must be unlocked, and that's very simple to do. Getting the Nexus drivers is more annoying that getting fastboot access.
Sent from my 831C using XDA Free mobile app
misteragony said:
Hello,
So a couple of months ago I cracked the screen of my Nexus 7 2013 (32Gb), I requested a quote of a repair shop that wanted me to pay 200€ to repair it. That's about 70€ less than the price for a new one.
Instead I ordered a replacement screen from Ebay and did the repair myself which costed me about 71€. The screen was a genuine one, same type and all.
Now last week, I hadn't used the tablet for a while, I tried to turn it on but it refused. After booting it into recovery I noticed that my cache partition was corrupted. Wiping it didn't help, doing a factory reset didn't do it either.
After googling a bit I found forum threads saying the only thing you can do is having it repaired by Asus under warranty. Is this really so?
Although I didn't leave a scratch on the tablet, the two seals on the screws inside the tablet have been removed while I was repairing the screen.
So most probably I'm out of luck then? No JTAG or anything else I can try?
My tablet was running stock Android, non rooted, no unlocked bootloader, ADB was not enabled.
Best regards,
Jan
Click to expand...
Click to collapse
Unlock your bootloader through ADB and than flash the factory image, make sure you flash the right one..
This LINK is a great guide that'll show you how to unlock the bootloader and flash a factory image through ADB (post 2).
Everything should get restored with a factory image flash, but if not you probably have a permanently bricked device because ASUS will most likely turn the device down if they notice any signs of the device being taken apart.
AarSyl said:
Yes, flashing the stock factory image is your best bet. I do believe that you must be unlocked, and that's very simple to do. Getting the Nexus drivers is more annoying that getting fastboot access.
Sent from my 831C using XDA Free mobile app
Click to expand...
Click to collapse
All I had to do was download the Google Driver from SDK and install it. ADB was able to recognize my device without a problem.
Well, I first installed SDK when rooting my HTC Evo, and boy did I have a grand time getting the right drivers! [/sarcarsm] By the time I was using my next HTC phone, I was using Ubuntu, and it doesn't require any device specific drivers.
USB debugging
Well the thing is: USB debugging was not enabled before I couldn't boot my Nexus anymore. Since I can't boot it, I can't enable USB debugging if I'm not mistaken.
So I boot into the bootloader (volume down + powerbutton), then select recovery mode and press the powerbutton.
Next I press the powerbutton and volume up and I'm in the recovery mode.
There I can see the error messages about my cache partition being corrupted, wiping/formatting it there does not help.
I can put the tablet in 'adb sideload' mode, but I guess since the tablet is not in debugging mode that won't do much good?
Using the Nexus 7 toolkit I always see the message: waiting for ADB mode but it detects the device though (it lists a serial number as well).
I tried to boot the tablet by holding up and down volume and then the powerbutton (this is supposed to be 'fastmode' no?).
The screen of the tablet remains black/ not active, my PC (under Win7) detects a new device at this point but it fails to load a driver.
When I try this under Linux I see a 'qualcom device when I do 'lsusb', and under /dev I see: /dev/ttyUSB0 appear.
I tried "fastboot oem unlock" but that doesn't work.
Well I found this thread:
http://forum.xda-developers.com/showthread.php?t=2602638&page=3
Seems some people have had the same issue with not being able to mount/format the cache partition.
So my only option would be a RMA, but since I repaired the screen myself that's a no-go as well (the warranty seals/stickers on the two screws on the inside are gone).
A new Nexus 7 it is then I guess...
misteragony said:
Well I found this thread:
http://forum.xda-developers.com/showthread.php?t=2602638&page=3
Seems some people have had the same issue with not being able to mount/format the cache partition.
So my only option would be a RMA, but since I repaired the screen myself that's a no-go as well (the warranty seals/stickers on the two screws on the inside are gone).
A new Nexus 7 it is then I guess...
Click to expand...
Click to collapse
You flash a stock image in fastboot. You hold volume down + power to enter it.
I tried to unlock: I chose yes using the vol buttons and pressed the powerbutton.
At that point the screen freezes on my tablet, and in the command line it gets stuck at this:
Device detected in FASTBOOT MODE
Device Serial Number is: 0xxxxx
...
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
I seem to be having tons of problems with this new phone =( HTCdev unlock failed work and now the phone has bricked while trying to do an update.
It is stuck on the "HTC powered by android" splash screen. The screen wont turn off and the phone does not change. Is there some way to fix this or am I farked? The phone is literally 3 days old and I hope there is a way to save it.
I can shut it down with Power and vol+ but when it restarts it just locks up. computer does not recognize it though it did install some form of driver.
Dlome said:
I seem to be having tons of problems with this new phone =( HTCdev unlock failed work and now the phone has bricked while trying to do an update.
It is stuck on the "HTC powered by android" splash screen. The screen wont turn off and the phone does not change. Is there some way to fix this or am I farked? The phone is literally 3 days old and I hope there is a way to save it.
I can shut it down with Power and vol+ but when it restarts it just locks up. computer does not recognize it though it did install some form of driver.
Click to expand...
Click to collapse
I would return it
Since I cant do anything until Monday I decided to mess with the phone a little more, I was able to get a custom recovery installed finally so hopefully all I need to do is install a new rom but the problem is the recovery is unable to mount my SD card to perform the install. I can read the sd card when it is in my old phone but not on the HTC One. Currently have Philz Touch installed as the recovery.
Is there any way to fix this or even bypass it all together?
Edit: I have been able to side load CM11 Nightly onto the phone so now it is functioning. I am having an issue with sound though so hopefully I can fix that.
clsA said:
I would return it
Click to expand...
Click to collapse
Warranty returns are for manufacturing defects, not botched mods done by the owner. The phone is completely recoverable.
redpoint73 said:
Warranty returns are for manufacturing defects, not botched mods done by the owner. The phone is completely recoverable.
Click to expand...
Click to collapse
This sounded like a hardware problem to me
I seem to be having tons of problems with this new phone =( HTCdev unlock failed work and now the phone has bricked while trying to do an update.
Click to expand...
Click to collapse
it's hard to mess the phone up when you can't even get the bootloader unlocked
clsA said:
it's hard to mess the phone up when you can't even get the bootloader unlocked
Click to expand...
Click to collapse
User error. The phone wasn't bricked (if the screen comes on, its not bricked) and 99% of the time when folks here say the phone is bricked, its just not booting. As you can see from his subsequent post, he was obviously able to get bootloader unlocked, custom recovery and custom ROM. Of course, you could have not known that when you made your previous post. But failed bootloader unlock, and then the phone won't boot, is a big red flag that the user just did something wrong.
redpoint73 said:
User error. The phone wasn't bricked (if the screen comes on, its not bricked) and 99% of the time when folks here say the phone is bricked, its just not booting. As you can see from his subsequent post, he was obviously able to get bootloader unlocked, custom recovery and custom ROM. Of course, you could have not known that when you made your previous post. But failed bootloader unlock, and then the phone won't boot, is a big red flag that the user just did something wrong.
Click to expand...
Click to collapse
Fair enough ... I read it wrong I guess
clsA said:
Fair enough ... I read it wrong I guess
Click to expand...
Click to collapse
Naw, really looks more like a matter of the OP needs being clear enough, and not giving enough info. If anything, best to get clarification before suggesting warranty service (especially once mods have been started - but again it was hard from the OP's description to know how far it got). Although if it was in fact a hardware defect, of course a warranty claim is valid.
So, My device got bricked. I didn't do root or anything. Recently the device got Android 7.1.2 update so I started the installation via OTA but (I DONT KNOW WHY) something gone wrong and the device gone into bootloop. My device was fully stock and had a locked bootloader but the device was still in 7.1.1 so I downloaded the 7.1.2 Update from the Google Developer page and sideloaded via ADB. The device finally rebooted into Home screen. So I was setting it up but suddenly it hanged and rebooted and the device was boot looped again but now its on a different case. Before, I was able to get the device back by Sideloading via ADB in recovery mode. But now when I tried to go into recovery mode the recovery mode DOESN'T EVEN APPEAR. It goes straight into the Google logo and goes to bootloop. Now I can't even access the recovery mode to sideload.
Please someone help
Dipto509 said:
So, My device got bricked. I didn't do root or anything. Recently the device got Android 7.1.2 update so I started the installation via OTA but (I DONT KNOW WHY) something gone wrong and the device gone into bootloop. My device was fully stock and had a locked bootloader but the device was still in 7.1.1 so I downloaded the 7.1.2 Update from the Google Developer page and sideloaded via ADB. The device finally rebooted into Home screen. So I was setting it up but suddenly it hanged and rebooted and the device was boot looped again but now its on a different case. Before, I was able to get the device back by Sideloading via ADB in recovery mode. But now when I tried to go into recovery mode the recovery mode DOESN'T EVEN APPEAR. It goes straight into the Google logo and goes to bootloop. Now I can't even access the recovery mode to sideload.
Please someone help
Click to expand...
Click to collapse
I believe you have the infamous bootloop issue.
Try to unlock bootloader if you can and flash everything manually. If that does not help, claim warranty or approach the place you purchased the device.
Dipto509 said:
So, My device got bricked. I didn't do root or anything. Recently the device got Android 7.1.2 update so I started the installation via OTA but (I DONT KNOW WHY) something gone wrong and the device gone into bootloop. My device was fully stock and had a locked bootloader but the device was still in 7.1.1 so I downloaded the 7.1.2 Update from the Google Developer page and sideloaded via ADB. The device finally rebooted into Home screen. So I was setting it up but suddenly it hanged and rebooted and the device was boot looped again but now its on a different case. Before, I was able to get the device back by Sideloading via ADB in recovery mode. But now when I tried to go into recovery mode the recovery mode DOESN'T EVEN APPEAR. It goes straight into the Google logo and goes to bootloop. Now I can't even access the recovery mode to sideload.
Please someone help
Click to expand...
Click to collapse
How did you manage to sideload without unlocking the bootloader?
Did you try just holding power and volume down while it was off until it booted and entered fastboot mode?
If you enter fastboot mode, use the arrow keys and power button to enter recovery mode.
ADB
Omnitrix4m3 said:
How did you manage to sideload without unlocking the bootloader?
Did you try just holding power and volume down while it was off until it booted and entered fastboot mode?
If you enter fastboot mode, use the arrow keys and power button to enter recovery mode.
Click to expand...
Click to collapse
I sideloaded via ADB in the recovery. But now the recovery wont even showing
indian84 said:
I believe you have the infamous bootloop issue.
Try to unlock bootloader if you can and flash everything manually. If that does not help, claim warranty or approach the place you purchased the device.
Click to expand...
Click to collapse
Ok the device suddenly boot up. I acted fast and unlocked the bootloader. But when everything is going fine. THE DEVICE BOOTLOOPED AGAIN. But now my bootloader is unlocked. So I flashed 6.0.1 it booted up and again bootlooped :crying:
Same here.
Are you part of the Beta program? Because I am, and after the latest "June 2017" update I suddenly started to have bootloops.
I can only reach bootloader but Recovery isn't starting at all, it just reboot and get into the loop again.
I've tried with the Nexus Root Toolkit, but the phone always get lost after the first reboot the toolkit requests to the device.
Any help here? It NEVER had any issues like that one, I've heard LG claimed it to be hardware related, but I got it after a software update.
This sounds like the infamous bootloop that many other people have encountered with the 5x. It is a problem with the actual hardware and isn't really permanently fixable by messing with the software. If your device is still under warranty, contact LG and they might be able to repair it. I had the infamous bootloop and they replaced the main board (free with warranty).
iSimon said:
Same here.
Are you part of the Beta program? Because I am, and after the latest "June 2017" update I suddenly started to have bootloops.
I can only reach bootloader but Recovery isn't starting at all, it just reboot and get into the loop again.
I've tried with the Nexus Root Toolkit, but the phone always get lost after the first reboot the toolkit requests to the device.
Any help here? It NEVER had any issues like that one, I've heard LG claimed it to be hardware related, but I got it after a software update.
Click to expand...
Click to collapse
LG never claimed it was a hardware issue for the 5X officially. Though due to some lawsuits they are extending the warranty on a case by case basis. The did acknowledge a hardware issue for the G4, which started production around the same time as the 5X.
What seems to happen is the later OS updates expose a hardware issue. Maybe by running a bit hotter. Some people, like me, had slightly reduced battery life after 7.1.2, which means the phone was drawing more power and heating up slightly more than before. My phone was on 7.1.2 for about 2 weeks before it just died while I was using it. Didn't seem to be a bootloop issue at first, but after fiddling around with it, and trying to fix it, that's what it ended up doing. Mine would never get into recovery either, until I used a hair dryer to heat the CPU on the motherboard since I didn't have a heat gun. I managed to reinstall the OS, but it took a heat gun to actually to get it to boot again. However, it lasted 9 hours then started bootlooping.
synesthete said:
This sounds like the infamous bootloop that many other people have encountered with the 5x. It is a problem with the actual hardware and isn't really permanently fixable by messing with the software. If your device is still under warranty, contact LG and they might be able to repair it. I had the infamous bootloop and they replaced the main board (free with warranty).
Click to expand...
Click to collapse
well I guess if it has been rooted ever then that voids any warranty. [excuse my language] god ****ing dammit then it's not fixable, christ LG are ****s.
aerolock said:
well I guess if it has been rooted ever then that voids any warranty. [excuse my language] god ****ing dammit then it's not fixable, christ LG are ****s.
Click to expand...
Click to collapse
I had mine fixed for free under warranty, so you should too, as long as it doesn't have significant other damage from drops or water, etc. I had rooted, unlocked and flashed many times. I did send it in stock, though, by flashing the stock factory images (mainly to clear personal data). I don't know what the official rules are about rooting and warranties, but I think that usually the Nexus phones allow you to unlock the bootloader and flash third party software without completely voiding the warranty. They are partly made as affordable developer units, anyway. Obviously, if you brick the phone by doing that stuff it is your fault, but if it is due to a defective part in your device, then they should be responsible to fix it. Even in the past I have been able to get an HTC phone repaired that was fully rooted/unlocked, because it had nothing to do with the hardware issue. Even if they say that your warranty is voided in the fine print from unlocking, sometimes companies will do the right thing and remedy issues that they are at fault for. Contact them, be polite, explain the problem/symptoms and ask if there is something they can do to help. When I contacted LG on their web chat system, I basically told them that the symptoms were most likely caused by a hardware issue and it seemed that the flash chip was failing. I told them that Google recognized the issue and has been refunding customers with the problem. I asked LG if they could repair, replace or refund my phone. The process went as smoothly as it could have gone for a situation like that (Other than unrelated issues with Fedex).
I would recommend just contacting LG, if you device is otherwise in good condition (aside from the bootloop). It can't hurt to try. Just know that the process of shipping it out, repairing, and shipping back might take about a week. Good Luck!
Ok, so when I went to the store I bought it from I said it was the nexus 5x bootloop issue thats with the hardware, then he asked me if I had done anything to the phone like rooting and I said I had rooted it once then removed the root, all he basically said then was dont waste our time asshole go somewhere else, so the previous root is the reason I can't get it fixed. But are you saying that if I call LG and dont mention anything about root then they'll fix it if I send it in? Luckily I found a spare phone so Im not handicapped but I love my 5x.
aerolock said:
Ok, so when I went to the store I bought it from I said it was the nexus 5x bootloop issue thats with the hardware, then he asked me if I had done anything to the phone like rooting and I said I had rooted it once then removed the root, all he basically said then was dont waste our time asshole go somewhere else, so the previous root is the reason I can't get it fixed. But are you saying that if I call LG and dont mention anything about root then they'll fix it if I send it in? Luckily I found a spare phone so Im not handicapped but I love my 5x.
Click to expand...
Click to collapse
I bought mine brand new on eBay. I rooted, Rommed, and otherwise tinkered with it unapologetically then ran into this bootloop issue almost a year later. I was able to contact LG support, send them a copy of my invoice from eBay showing that it was bought new and the date. I sent it off and they fixed it for free (replaced the main board) under warranty. Just go through LG support and they will almost certainly get you taken care of. It took a little over a week, but it sounds like you have a phone you can use during that time.
I purchased a 5x through Amazon over year ago and it is now bootlooping. I have tried all known fixes. I am in the US and I purchased the international version unknowingly. The LG US support site does not recognize my H791 version and I doubt that I can send it overseas. Am I out of luck getting this phone fixed?
Sent from my Nexus 6P using XDA-Developers Legacy app