[Q] Had my GN died? - Samsung Galaxy Nexus

I was updating some apps in the market, as suddenly the phone reboots without any warnings.
OK, **** happens i thought and let it boot. But now the phone starts the ROMs boot animation for about 4-5 seconds and then reboots over and over again.
I pulled the battery and started into recovery. I made a nandroid and wiped cache and dalvik. Reboot with same behavior.
Recovery again: wiped everything and flashed a new AOKP M3 - result: reboot and loop again
Back to recovery: tried to flash the before made nandroid - MD5 checksum error
Flashed an older nandroid and got boot loops again.
So, i think this piece is for the service now...
What is the best way to reset this GN? Using ToolKit to put back stock recovery and lock the bootloader? Or should i try something else?
Update:
Flashed Stock Google Image via ToolKit 5.4 and after that the phone is booting normal?!?
I reflashed the touch recovery and pushed the AOKP build 27 back to the phone and flashed it.
So far so good - I have to start from the bottom now, because flashing the stock rom wiped the whole phone and EVERYTHING on sdcard is gone
Do you think there is a hardware failure? Perhaps some sort of memory malfunktion or something like that?

Same thing just happened to me, thi is the second time

lighthammerhh said:
I was updating some apps in the market, as suddenly the phone reboots without any warnings.
OK, **** happens i thought and let it boot. But now the phone starts the ROMs boot animation for about 4-5 seconds and then reboots over and over again.
I pulled the battery and started into recovery. I made a nandroid and wiped cache and dalvik. Reboot with same behavior.
Recovery again: wiped everything and flashed a new AOKP M3 - result: reboot and loop again
Back to recovery: tried to flash the before made nandroid - MD5 checksum error
Flashed an older nandroid and got boot loops again.
So, i think this piece is for the service now...
What is the best way to reset this GN? Using ToolKit to put back stock recovery and lock the bootloader? Or should i try something else?
Update:
Flashed Stock Google Image via ToolKit 5.4 and after that the phone is booting normal?!?
I reflashed the touch recovery and pushed the AOKP build 27 back to the phone and flashed it.
So far so good - I have to start from the bottom now, because flashing the stock rom wiped the whole phone and EVERYTHING on sdcard is gone
Do you think there is a hardware failure? Perhaps some sort of memory malfunktion or something like that?
Click to expand...
Click to collapse
Firstly when you get bootloops or any other problem do NOT do a nandroid as it backs up EVERYTHING, including the problem.
When you "wiped everything" did you go to mounts and storage and format system, cache and data?
If not then you didn't do a proper full wipe.

This is my own experience, but I want to warn you guys. I had a similar problem with my GNex. The first time it happened, my phone rebooted itself every 5 seconds. I completely restored it using factory image and it ran fine for 3 weeks, then one day, the phone just rebooted itself and got stuck at the boot image. I had to factory reset it again to make it work.
After the second time, I called Samsung and sent it in for repair last week. They are shipping me a replacement unit. It seems the problem was hardware related.

econometrician said:
This is my own experience, but I want to warn you guys. I had a similar problem with my GNex. The first time it happened, my phone rebooted itself every 5 seconds. I completely restored it using factory image and it ran fine for 3 weeks, then one day, the phone just rebooted itself and got stuck at the boot image. I had to factory reset it again to make it work.
After the second time, I called Samsung and sent it in for repair last week. They are shipping me a replacement unit. It seems the problem was hardware related.
Click to expand...
Click to collapse
For 3 weeks... exactly 3 weeks, 21 days?
I can tell you that my first boot loop brick was 20 days after I bought the phone. The second was later that day. But the third one was... again, 20 days after the last successful restore. Is there something magical about the 3-week mark???
I am currently taking nightly nandroid backups, so when I had my third boot loop brick my backup was just under a day old. If this is ultimately a hardware problem that can be warrantied, I guess I'll have to try that next time. I would have to make sure I return it with the bootloader locked, stock recovery, but without the wipe because it has to still be boot looping to prove there's an issue!
Anyway, things I will point out:
- It's the complete wipe in bootloader that blanks the internal storage.
- If you have CWM installed, you can back up the internal storage over USB via adb pull /sdcard/ ./sdcard/ (correct me if I got the syntax wrong)
- When the boot loop brick has happened, CWM is not capable of properly reformatting or restoring to the data partition. I have not found a way to repair it without blanking /sdcard (which on the GN is actually in /data/media), so if you don't want to lose those files the only way to keep them is to pipe them out, blank the phone, and then pipe them back in afterwards.
- After a complete wipe in bootloader (either by flashing userdata.img or by relocking/unlocking bootloader), you must boot the phone once into the OS in order to complete the reformatting of /data. If you try booting straight into recovery after a wipe in the bootloader, CWM cannot read or write from that partition.

Can't say for sure whether it's exactly 21 days but it's definitely around 3 weeks. Why don't u give Samsung a call? The phone is not supposed to behave this way. Plenty of people don't have this problem. My wild guess is that the internal flash memory is faulty.

econometrician said:
Can't say for sure whether it's exactly 21 days but it's definitely around 3 weeks. Why don't u give Samsung a call? The phone is not supposed to behave this way. Plenty of people don't have this problem. My wild guess is that the internal flash memory is faulty.
Click to expand...
Click to collapse
I'll warranty it through my carrier next time as they do exchanges on site. The trouble is, once I've recovered the phone, there's no evidence of the problem anymore. The best way to prove it is to show it fritzing out.
Sent from my Galaxy Nexus using Tapatalk

I think this is a known problem. You shouldn't have to prove it to them. They should be aware of it.

It bricked again today so I warrantied it in-store at my carrier. They gave me a brand new one after being unable to find a solution when fiddling with it. As a bonus, all the little hairline scratches on my screen are gone too
The store guy said he's never seen this issue, and it's one of only two warranty locations for my carrier in the Vancouver area. So I can only hope this was a rare hardware problem and not something that pervades every GN they're going to sell.
I can tell this one is from a different batch because it came preloaded with 4.0.2.

Good for you. hopefully my new phone will behave

Related

[Q] restore phone from recovery/hboot

Im having a problem with my phone booting. it does a variety of things from rebooting mid way through boot, hanging at the white HTC screen, getting to lock screen then rebooting...
point is, i cant get in to the system.. what i'd like to do is remove everything and get it to stock... the RUU would be nice, but it needs to be booted for that to happen. i've tried a couple of custom roms (vaelpak, synergy) but they all result the same way. cleared dalvik, data, .android_secure, cache with no impact..
RA 2.3 is what the recover console currently is...
what is the best way to recover the phone to stock?
im ok with working with the phone but not awesome so somewhat detailed directions would be appreciated.
hope i didnt leave anything out,
Thanks
What rom are you on? I am assuming you can get into recovery. May I recommend, fresh 4 rom by flipz to get everything back to normal first (Full wipe is necessary) ...then we can work on this further.
thanks for the response.
wiped data/secure/cache/dalvik
applied Fresh 4.2.0.0 rom
rebooted
showed HTC white screen for 2 seconds rebooted.. did this until it gave me the 3 vibrates and flashing green light..
reseated battery and powered on
HTC white hung for what seemed longer than normal than Fresh boots.. lock screen appears for a couple of sec and then it reboots.
thanks
Lets try a few more steps before concluding hardware issues.
1. wipe all
2. http://www.virusrom.com/Tools/VR_SUPERWIPE.zip (flash this)
3. Flash your favorite rom (try one of the newer ones if your SD is partitioned)
4. restart...and let the phone wait for 10 mins...before you unlock the screen
5. unlock screen and let it settle (DO NOT SET UP ACCOUNTS)
6. reboot recovery..wipe cache and dalvik and reboot
7. sign into market...
8. if it still reboots/FCs then flash latest radios http://forum.xda-developers.com/showthread.php?t=715485
cool i'll give that a try..
when you say wipe all, is the list i've provided "all"? i noticed with RA i can wipe system/boot and some others i believe... wasnt sure i should wipe the boot or system...
yes...start at format all factory reset...and then the list you've provided...dont wipe sdcard unless formatting it...and then follow from step 2
yeah basically what i listed was the factory reset + dalvik..
so, you mention if the SD card is partitioned (app2SD?) which i dont currently have setup, but its a new SDcard so i might.. but, if i put one of those newer roms on that assume App2SD (which i believe i did) then would the problems im having be a result of doing that??
no luck, still getting random reboots
what rom did you flash? But if you did all the steps from my earlier post, I am wondering if this is an hardware issue.Heres a thread about back to stock RUU . http://forum.xda-developers.com/showpost.php?p=7529500&postcount=1
here another for the latest froyo ruu
http://forum.xda-developers.com/showthread.php?t=874251
just in case you would want to root back
well that sucks... i just replaced the screen and LCD too....
thats the tool i was trying to use but couldnt keep the system up long enough to get it to run right... in order to run the RUU you need to be in android (is that right? sounds werid, like saying in windows, past boot, etc etc).. anyways.. it has to be loaded, the RUU then flashes a special boot loader to do the restore... i've gotten a handful of errors, some of which even say that i have the wrong version (i'll try the one you posted but i've used an RUU before and tried the same one again)
i'll keep screwing with it, or get a new phone i guess.. still a year left on my contact so i'll be hitting up ebay or something :-/
thanks for all your help, really apprecaite it

Phone Not Booting - Very Weird Issue

I'm having a weird issue with the phone not booting up, and wanted to see if anyone could offer some insight.
Got the S3 the beginning of the month, the only thing I did was use this guide to root the phone - http://forum.xda-developers.com/showthread.php?t=1739426 Have not put any custom rom on the phone, just the rooted stock. It was running smoothly till last week. Put my phone in my pocket leaving a building and got in my car pulled it out and I was faced with the dreaded "Glowing Samsung Logo." Nothing I did would get it to boot. I tried restarting (Holding Volume Up and Power,) then taking the battery out and restarting. No luck, get the ATT logo (droplets) and music, then the glowing samsung logo and nothing. I then tried taking the battery out and letting it out for the drive home. Get home, nothing still does the same thing. I then thought maybe it's the battery, so with the phone off I let it charge for an hour, tried to start it up and same deal no go.
I then did all the reading I could. I could get into Download Mode and Recovery, so I first tried wiping cache. That didn't work, glowing logo again. Then I bite the bullet, do a factory wipe and get the phone back up and running.
My first assumption through problem solving was that I did something wrong. Putting it in my pocket maybe the buttons got pressed in a weird manner. Maybe it's an app. But after setting the phone back up, it was running smoothly again - til last night. I set my phone down last night and when I come back to it I see the glowing logo again. Repeated all my steps again, no luck booting up, just a glowing logo. I figured I would take it to an ATT store to see what they can diagnose, but they are closed. So I used Odin again and tried just re-applying the rooted stock back on. No luck, bite the bullet wipe the phone and it's up and running again.
Can anyone give me any insight into what is happening. I have looked at the Sudden Death threads and it would seem that I don't have the issue. Maybe a bad assumption, but the fact that I can always get into Download Mode and Recovery leads me to think I don't have the Sudden Death issue. I'm perplexed and can't think of why this issue is happening or what the cause is. I would like to find the root cause of what is going on.
Anyone have any suggestions or things to investigate that would help me find out why it is happening?
OfficialDoughboy said:
I'm having a weird issue with the phone not booting up, and wanted to see if anyone could offer some insight.
Got the S3 the beginning of the month, the only thing I did was use this guide to root the phone - http://forum.xda-developers.com/showthread.php?t=1739426 Have not put any custom rom on the phone, just the rooted stock. It was running smoothly till last week. Put my phone in my pocket leaving a building and got in my car pulled it out and I was faced with the dreaded "Glowing Samsung Logo." Nothing I did would get it to boot. I tried restarting (Holding Volume Up and Power,) then taking the battery out and restarting. No luck, get the ATT logo (droplets) and music, then the glowing samsung logo and nothing. I then tried taking the battery out and letting it out for the drive home. Get home, nothing still does the same thing. I then thought maybe it's the battery, so with the phone off I let it charge for an hour, tried to start it up and same deal no go.
I then did all the reading I could. I could get into Download Mode and Recovery, so I first tried wiping cache. That didn't work, glowing logo again. Then I bite the bullet, do a factory wipe and get the phone back up and running.
My first assumption through problem solving was that I did something wrong. Putting it in my pocket maybe the buttons got pressed in a weird manner. Maybe it's an app. But after setting the phone back up, it was running smoothly again - til last night. I set my phone down last night and when I come back to it I see the glowing logo again. Repeated all my steps again, no luck booting up, just a glowing logo. I figured I would take it to an ATT store to see what they can diagnose, but they are closed. So I used Odin again and tried just re-applying the rooted stock back on. No luck, bite the bullet wipe the phone and it's up and running again.
Can anyone give me any insight into what is happening. I have looked at the Sudden Death threads and it would seem that I don't have the issue. Maybe a bad assumption, but the fact that I can always get into Download Mode and Recovery leads me to think I don't have the Sudden Death issue. I'm perplexed and can't think of why this issue is happening or what the cause is. I would like to find the root cause of what is going on.
Anyone have any suggestions or things to investigate that would help me find out why it is happening?
Click to expand...
Click to collapse
It's just a simple bootloop, do you have any recoveries installed? If yes then make a nandroid backup, do a factory reset, then restore data.
Ali7000 said:
It's just a simple bootloop, do you have any recoveries installed? If yes then make a nandroid backup, do a factory reset, then restore data.
Click to expand...
Click to collapse
Actually no custom recovery installed, had no intention to install a custom rom so I heeded the warning on the thread - " flashing a custom recovery will trip your counter no matter the method used." My most important data is sitting on the external SD, so I had that precaution in place.
I did start looking at the custom recoveries (CWM/TWRP,) know how they work (had CWM on my HTC Inspire) but in this case something is causing the phone to bootloop. I see the benefit of getting up and running quick, but I want to find the source of the problem.
Thanks for the response and taking time to answer.
OfficialDoughboy said:
Anyone have any suggestions or things to investigate that would help me find out why it is happening?
Click to expand...
Click to collapse
OfficialDoughboy said:
Actually no custom recovery installed, had no intention to install a custom rom so I heeded the warning on the thread - " flashing a custom recovery will trip your counter no matter the method used." My most important data is sitting on the external SD, so I had that precaution in place.
I did start looking at the custom recoveries (CWM/TWRP,) know how they work (had CWM on my HTC Inspire) but in this case something is causing the phone to bootloop. I see the benefit of getting up and running quick, but I want to find the source of the problem.
Click to expand...
Click to collapse
It could be your hardware. Of course this is not my area of expertise. You could try to install a custom recovery, wipe everything (system, data, cache, dalvik) and try reinstalling the rooted rom via ODIN. You can use Triangle Away later if needed. If you do not want to go through all of this, you can try going through warranty (just be sure you counter is not tripped and you have stock unrooted before you do).
aybarrap1 said:
It could be your hardware. Of course this is not my area of expertise. You could try to install a custom recovery, wipe everything (system, data, cache, dalvik) and try reinstalling the rooted rom via ODIN. You can use Triangle Away later if needed. If you do not want to go through all of this, you can try going through warranty (just be sure you counter is not tripped and you have stock unrooted before you do).
Click to expand...
Click to collapse
Thanks for the reply. I have all my apps now backed up with Titanium Backup just in case. I also checked for Sudden Death Syndrome with the eMMC Check app and it says I don't have an affected phone. I'm going to give it another week and see if the same thing happens again. If it does I'm going to go through warranty to get a replacement.
OfficialDoughboy said:
Thanks for the reply. I have all my apps now backed up with Titanium Backup just in case. I also checked for Sudden Death Syndrome with the eMMC Check app and it says I don't have an affected phone. I'm going to give it another week and see if the same thing happens again. If it does I'm going to go through warranty to get a replacement.
Click to expand...
Click to collapse
Honestly I suggest going into stock recovery and doing a factory reset and wiping cache. When you flash back stock with Odin you usually have to do a factory reset anyway because it will bootloop.
About tripping the flash counter is almost a non issue as all you have to do is use triangle away and Odin flash back to stock and its gone.
hednik said:
Honestly I suggest going into stock recovery and doing a factory reset and wiping cache. When you flash back stock with Odin you usually have to do a factory reset anyway because it will bootloop.
About tripping the flash counter is almost a non issue as all you have to do is use triangle away and Odin flash back to stock and its gone.
Click to expand...
Click to collapse
I actually did that, sorry I wasn't clear in my original post. This last time, I wiped the cache and rebooted the phone, that didn't work. Then I tried Odin to see if I could save internal data, re-flashed and again couldn't boot. Last thing I did was do a factory reset through stock recovery and got the phone to boot.

Internal Memory Damaged *FIX*

Hello
I do not know if anybody has had this problem with the note 8 but, I know I did so just in case anybody else has the same problem look in here.
OK so it at started when my Note 8 did not want to charge so I took it a part and inspected the battery and it was fine, of course I did this at work not at home. I could not use the original charger to see if that was he culprit which it turned out it was. Once it was charged and started the tab seemed to have a corrupted memory or something. How? do not ask I do not know how that happen. I went in to TWRP recovery and I could not mount internal sd card, data, and some other stuff so, definitely something is going on.( See Picture). The only thing you could do was reset the device as stated in the icon on the tab. By clicking the reset button on the screen the tab rebooted into recovery but, since I had a custom recovery the tab would reboot again. Now, the only thing that I was thinking that could fix this was restoring back to stock firmware which I didnt because damn downloads was taking to long. So, the other possible thing was restoring the stock recovery.(Some of you might have known this but, I just putting it here because there is people out there that do not) I downloaded the original stock recovery that I found and restored it via ODIN(search ODIN if you do not know what it is). I rebooted the tab and took me back to the rese device again and proceeded to restore. Now, it took me to recovery again and this time since it found the original samsung recovery, everything checked out and restarted the device. Everything was back to normal, all I did was just reflash the custom recovery in ODIN reboot to the recovery, restore my back up "if you have one " and done. All worked out.
Hope this helps anyone if they find themselves in this situation.
Thanks

Nexus 5X Suddenly freeze and stuck in boot loop

So while i was browsing around with Firefox on my 1 year old Nexus 5X, it suddenly froze and after about 20 secs automatically reboots.
After it shows the google boot logo for about 10 seconds it reboots again in a loop.
Bootloader is unlocked, its rooted and Cyanogenmod is installed. This worked fine for about 1 year. I havent done any updates since this CM install 1 year ago.
I can get into fastboot by pressing power and volume down. I can stay there forever but if I choose anything else from there, it goes into the reboot cycle again.
So I can not get into recovery mode from fastboot because it reboots before it gets there.
I can sometimes get into download mode by pressing power and volume up but after a few seconds it again reboots from there.
Is there any way to at least save my data? I do have some very important account data on it.
I assume from fastboot mode alone you cant save anything or is there a trick?
Thanks for any help!
sounds very similar to my situation, bought mine about a year ago as well, except I was running stock 7.1.2
It should be easy to save the phone, but for the data - that's going to be trickier.
As long as you have fastboot you can always just flash it back to stock but that will wipe your data.
So you could try to to:
fastboot erase cache and fastboot erase recovery and then reflash recovery and see if you can get into it now.
Once in recovery you should have adb access if you have the correct drivers installed and you can flash a full OTA image in ADB which will reflash every partition, but not wipe your data.
For both methods read this: https://developers.google.com/android/images
Once you have adb you could also just pull the entire content of your data partition. The question is if and how that account data is stored and if you could get it back that way.
If you really need that app data I would try to get the OS working by flashing the OTA image in adb, then reinstall the app and hope your account data is still there...
And then look into backup options. It's pretty risky to have important data not backed up or duplicated somewhere else on a mobile device that could be lost or stolen any second...
It sounds like the bootloop problem, its a problem that many people are facing
berndblb said:
It should be easy to save the phone, but for the data - that's going to be trickier.
As long as you have fastboot you can always just flash it back to stock but that will wipe your data.
So you could try to to:
fastboot erase cache and fastboot erase recovery and then reflash recovery and see if you can get into it now.
Once in recovery you should have adb access if you have the correct drivers installed and you can flash a full OTA image in ADB which will reflash every partition, but not wipe your data.
For both methods read this: https://developers.google.com/android/images
Once you have adb you could also just pull the entire content of your data partition. The question is if and how that account data is stored and if you could get it back that way.
If you really need that app data I would try to get the OS working by flashing the OTA image in adb, then reinstall the app and hope your account data is still there...
And then look into backup options. It's pretty risky to have important data not backed up or duplicated somewhere else on a mobile device that could be lost or stolen any second...
Click to expand...
Click to collapse
I dont know about the OP, but my 5X will not get into fastboot, no matter what option I pick, I see the Google screen then it goes black and back to the Google screen and then is unresponsive for hours
I'm having the same issue as of this morning. I find it a little suspicious that it happened on the same day that my billing restarted and they had just updated the app a few days ago...
But I am unable to get to recovery mode either. Just shows the Google logo and reboots.
It's happening to me right now, the exact same thing, guys, this is not a coincidence
Another one here, started Friday night 3 days ago. Really weird that all of a sudden so many 5X users are experiencing the same problem.
mine just started this today, but after about ten reboots it finally started. Its almost like someone took control of the phone to install something remotely... weird
Sent from my Nexus 5X using Tapatalk
I'm having the exact same issue. Was watching a youtube video and suddenly the screen froze and my phone rebooted. When i tried to get into the recovery i still only got the google logo and a reboot. Fortunately i have my bootloader unlocked. I was able to reflash android and it worked again. After an hour or two the same started to happen again. Extremely frustrating.
Best thing you can do is flash just the recovery and try to get your files out that way.
so even until now many Nexus 5x still got bootloop? nothing to fix it still?
planning to get an used Nexus 5x and afraid also got this bootloop problem, should I or shoudn't I get it?
after reading so much bootloop stories, seems the timing to bootloop is just matter of time? on how much the phone is used? heavy use got bootloop first and lighter use got bootloop last but still get it sooner or later?
I will not buy it
DON2003 said:
so even until now many Nexus 5x still got bootloop? nothing to fix it still?
planning to get an used Nexus 5x and afraid also got this bootloop problem, should I or shoudn't I get it?
after reading so much bootloop stories, seems the timing to bootloop is just matter of time? on how much the phone is used? heavy use got bootloop first and lighter use got bootloop last but still get it sooner or later?
Click to expand...
Click to collapse
Two days ago I was facing the same problem, I managed to reload the stock rom and relock the bootloader so I can claim the warranty. But even though they replace me the phone I am pretty sure that sooner or later you will face this problem. This is an amazing phone and for the time I buy it, I believe was a smart choice, now I believe you can find something at same range price with even better specs.
I am facing the exact same issue. I was watching a Youtube video when the phone suddenly froze and shutdown itself. Then impossible to boot again. Sometimes I can boot to fastboot (after few hours without touching the phone or 20 min in the freezer). I tried to flash factory images (https://developers.google.com/android/images) but it does not fix it.
Has anyone been able to fix this? I don't think it's a hardware issue as I replaced the screen (the last one had a small crack on it) as well as the battery...
Look in the general subfourm for BLOD. https://forum.xda-developers.com/showthread.php?t=3683926
Sent from my [device_name] using XDA-Developers Legacy app

Stuck on google logo boot screen after twrp recovery & then factory reset

Hi guys, bit of a saga here so bear with me...and also it should be mentioned I have little experience/understanding of tech stuff, so that isn't helpful either lol
I've had a Nexus 5x running 7.1.2 for not quite a week; it came with an unlocked bootloader (strangely). Tried to do the usual install twrp & root as I've done with previous phones (all pre-nougat) but all attempts failed. Couldn't boot into stock recovery from the bootloader at all, it would just boot into the system. OK, next thought was that an OTA upgrade to Oreo might work to restore a recovery - but got the BLOD (naturally lol). I found a fix in a modded 4-core Twrp 3.2.1 -0 fbe img + workaround injector zip from osm0sis & XCnathan32 which by some miracle worked.
So far, so good. Ffwd a few days and google play store keeps crashing on opening; I had the feeling that some glitch happened while it was updating, so I tried all the usual fixes like app cache/data wipes and uninstall updates/renistall google play, delete google account etc which failed. Next I tried a cache & data device wipe through twrp - also unsuccessful. Finally, I thought the only thing left to try would be to restore a backup I made on twrp - this led to the current issue of not booting, stuck on the google logo screen. I even thought what the hell! and attempted a factory reset with twrp - same result, where I am now. Google logo screen, however I still have an unlocked bootloader.
Would anyone be able to suggest where I might go from here? I'm pretty sure the version is N2G48C, if that helps.
Any suggestions very much appreciated...wouldn't mind getting to the 1 week mark with a functioning phone lol
Saga #2
Still no idea what's going on. I realised that I'd backed up and recovered the system and vendor .img files, which according to this thread would be a cause of the issue https://forum.xda-developers.com/nexus-6p/help/stuck-google-logo-twrp-backup-restore-t3320840/page3
So I made another backup without those images, did a full wipe and restored it - still does not boot, still only sitting on the google logo. Tried next to open a cmd terminal to see if I could reflash a stock image, but adb could not connect (maybe because the phone would have been on charging and not file transfer mode?)
Last resort as I saw it was to try the NRT, and see if it would flash stock via the bootloop/softbrick option. Process seemed to be OK, judging by the log - but it did not reboot to the system. Now there is a looping bootloop between the google logo and the unlocked bootloader warning.
Following wugfresh's instructions to factory reset from the recovery (the phone won't turn off via the power button so I just booted straight into the bootloader) Looked for the recovery option, selected....and nothing!!
So there isn't a stock recovery??? How does that work?
And what hope is there for this phone now? (I can't think of anything else )
Anyone have an idea? I've never heard of this before tbh!
Well, my problem has been sorted. In the absence of knowing what the hell I should do lol I managed to get a refund for the phone even though it was a refurb to begin with (something to be said for an honest seller who provides a 3 month warranty!) and I picked up a brand new N5x, which was unboxed on Tuesday. Not even 6 hours into setting it up, the phone started to get progressively hotter and then went into bootloop. Got into the bootloader and tried a factory reset - all seemed OK but halfway through the setup process it bootlooped again. Fortunately it was still within the 2 year warranty, and LG didn't argue about authorising a repair for a phone which didn't get even half a day's use on it lol
Authorised Wednesday, walked into the service centre Thursday and a 1 hour wait later had phone in hand with the PCB/motherboard replaced. Has been working fine (and cool!) ever since. Definitely feel lucky to have hopefully dodged a bullet on this one.
Bonus that they upgraded from 6.0 to 7.2.1 while they were at it; apparently LG considers nougat the "latest" stable version for the 5x.

Categories

Resources