OK so I've looked through the forum (admittedly the Galaxy Nexus specific one only) and tried some searches but may not be able to articulate this problem in clear way. Basically, I'm continuously crashing - started with a stock, but unlocked/rooted install. Now it won't boot and crashes in the boot loader as well after a few seconds (thus not allowing any non-trivial actions to actually complete.)
The first crash was after enabling face unlock for the first time. When I hit the power button to shut things off, the display "tore" and then went totally dark. Phone was completely unresponsive till I pulled the battery for a few minutes (found that one from search.) Couldn't complete a boot sequence though - would go to the animation, then display would go wonky and then shut down. Would usually have to pull battery again to get any response from that.
Went to recovery mode and wiped data - which completed - same problem on boot. Only thing I'd done was unlock and root (for eventual root apps, none of which had been run) so decided to undo that (using "Galaxy Nexus Root Toolkit 1.3.") On the factory restore there are several steps (boot loader, radio, etc.) and I haven't been able to complete that process.
I suspect it might even be bad hardware at this point, but can't go back to VZW with the phone still showing unlocked. Phone is a recent eBay purchase to replace a lost device but seemed fine for the 2-3 days I used before this all started.
Anyone seen something like this before?
So your able to get into recovery still? If it doesn't boot into the os it's probably a compatibility error between the kernel and rom your using (Just clearning data in recovery won't fix this).
So what rom/kernel combination were you using at the time?
Also have you tried flashing a completely different custom rom to the one your having issues with.
And any nandroid backups you have made in the past?
What's weird is that I was in stock kernel / rom at the time. (At least I'm nearly sure - it did come from eBay after all...)
I'll also try changing the ROM, that could be it. The big question is if that can complete before the thing melts. If I boot to recovery and wait, doing nothing, the system crashes in a minute or two.
My current thinking is that I might have a bad recovery / clockwork mod install.
can you still get to the bootloader and is it stable to sit on the bootloader?
I can get to the boot loader but it is not stable there (I think I was conflating the two.)
does your bootloader look like this? i want to make sure you and i are talking about the same thing.
{
"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"
}
Yep, that's the one (before it crashes. I have a pic of the amusing video display when it does that I'll put up when I hit the magic 8 posts...)
try using ODIN to restore your phone. instructions are found here: http://forum.xda-developers.com/showthread.php?t=1394051
also, how long can you sit on the bootloader before it crashes?
I'll try that as tonight - thanks!
Varies on time to crash, but no less than 30 seconds and no more than 5 minutes so far. Requires a battery pull and wait to come back after that.
i would like to see the picture of the crash you are talking about.
also, you can relock the bootloader real fast before you take it to VZW. only takes 1 command once you get to the bootloader
fastboot oem lock
Wow, same crash while in download mode. That can't be good...
yeah thats not good at all. i'd lock the bootloader and return it
http://dulinor.smugmug.com/photos/i-XkKWCrg/0/S/i-XkKWCrg-S.jpg
This is the crash I'm seeing
Yeah return to the store and show them this, the board is probably bad.
thats rough, but since you got it on ebay returning it may be a hassle and if the phone is not a north american model samsung might not even accept it for warranty.
did you try to flash the stock google image using fastboot instead of using the toolkit? it will only take a few mins. when you display crash like that does it still take commands from fastboot? you can test it when the display crash like that type in fastboot devices and see if you get the id number in command prompt. if your build was yakju then you can get the factory images from here http://code.google.com/android/nexus/images.html
Just got back from the store - they issued a replacement, none on hand so one should ship out today. (Thanks for the tip on re-locking it - not sure if they checked, but was happier having that.)
So of course, it actually completed booting (for the first time) but crashed during activation. Once they saw it crash on the Odin screen, they were happy to do the swap.
I had been trying to re-flash OEM Google - which it should have been all along.
Thanks everybody for your help.
Related
I'm sure this has been asked a bunch of times, but I don't know what this screen is called, therefore I can't search for a solution.
When I first looked at my phone (used) before I bought it, it didn't do this. And then I brought it to the Verizon store to get a new SIM card. The salesperson reset the phone for me. The battery died on the way home while I was using it and it shut down. Now, every time I turn on the phone it shows this screen. If I pull the battery and boot into upgrade mode (volume down + power) it will boot, but it resets data (all of my stuff is gone). It will do this every time. I suspect the file system has become corrupted due to the improper shut down.
So, how can I solve this? Do I need to reflash everything through Odin, or can I sort of just push /system and /data to it via adb? I'd like to stick with stock ICS for now.
I'm coming from a Samsung Fascinate. I've owned a Galaxy Nexus before, but only for a few weeks. I have quite a bit of experience with all of this stuff, so any basic info should be easy for me to understand. I just don't know what this screen is and why it's appearing.
EDIT: It would probably help if I posted the photo
{
"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"
}
jmattp said:
I'm sure this has been asked a bunch of times, but I don't know what this screen is called, therefore I can't search for a solution.
When I first looked at my phone (used) before I bought it, it didn't do this. And then I brought it to the Verizon store to get a new SIM card. The salesperson reset the phone for me. The battery died on the way home while I was using it and it shut down. Now, every time I turn on the phone it shows this screen. If I pull the battery and boot into upgrade mode (volume down + power) it will boot, but it resets data (all of my stuff is gone). It will do this every time. I suspect the file system has become corrupted due to the improper shut down.
So, how can I solve this? Do I need to reflash everything through Odin, or can I sort of just push /system and /data to it via adb? I'd like to stick with stock ICS for now.
I'm coming from a Samsung Fascinate. I've owned a Galaxy Nexus before, but only for a few weeks. I have quite a bit of experience with all of this stuff, so any basic info should be easy for me to understand. I just don't know what this screen is and why it's appearing.
EDIT: It would probably help if I posted the photo
Click to expand...
Click to collapse
Its the stock Recovery screen. I would just do a fresh install using Odin
Sent from my Galaxy Nexus using XDA
That's the stock recovery screen? Funny.. I've never seen it. I've seen fastboot a bunch of times, and Clockwork recovery (and other recoveries) but I assumed that was some kind of looping loading screen or something.
I'm resetting it to stock through the terminal, pushing everything in fastboot. I want the OTA 4.0.4 update. I should be able to get that with the stock ROM and OEM locked bootloader right?
Thanks for telling me what that screen was. I had no idea.
EDIT: Oh, I was also wondering if the improper shutdown caused this problem, or if something could be wrong with the device that I should be worried about.
jmattp said:
That's the stock recovery screen? Funny.. I've never seen it. I've seen fastboot a bunch of times, and Clockwork recovery (and other recoveries) but I assumed that was some kind of looping loading screen or something.
I'm resetting it to stock through the terminal, pushing everything in fastboot. I want the OTA 4.0.4 update. I should be able to get that with the stock ROM and OEM locked bootloader right?
Thanks for telling me what that screen was. I had no idea.
EDIT: Oh, I was also wondering if the improper shutdown caused this problem, or if something could be wrong with the device that I should be worried about.
Click to expand...
Click to collapse
If you can get into fastboot and recovery then you don't have any serious problems.
Sent from my Galaxy Nexus using XDA
Thanks. After returning to stock, everything seems fine. I guess the battery dying borked something. I hope this doesn't happen every time the battery dies. (I don't plan on letting it die... but in the event that it does, it will suck)
jmattp said:
Thanks. After returning to stock, everything seems fine. I guess the battery dying borked something. I hope this doesn't happen every time the battery dies. (I don't plan on letting it die... but in the event that it does, it will suck)
Click to expand...
Click to collapse
It must've been something else, I've had the battery die a few times, its booted up fine. Glad you fixed it.
Sent from my Galaxy Nexus using XDA
Ok i have a verizon gnex with latest ota. At times if i reboot or turn off the phone then turn it back on the phone will get stuck at the google splash screen. One time i pulled the lte sim card and then after a few tries it booted without the lte sim.. then i powered it down and placed the lte sim card in and it started back up... other times that does not work.... Twice today i had to turn it off and wait like 20 minutes or so and then turn it back on with the lte sim in and then it booted. I did use nrt nexus root toolkit and redid the phone but still have the issue.... should i try a custom rom and wipe the system or did the nexus root tool when i used that also wiped the system?
rezoundness said:
Ok i have a verizon gnex with latest ota. At times if i reboot or turn off the phone then turn it back on the phone will get stuck at the google splash screen. One time i pulled the lte sim card and then after a few tries it booted without the lte sim.. then i powered it down and placed the lte sim card in and it started back up... other times that does not work.... Twice today i had to turn it off and wait like 20 minutes or so and then turn it back on with the lte sim in and then it booted. I did use nrt nexus root toolkit and redid the phone but still have the issue.... should i try a custom rom and wipe the system or did the nexus root tool when i used that also wiped the system?
Click to expand...
Click to collapse
use the tootkit to flash the latest stock image and see if that fixes your problem
k786 said:
use the tootkit to flash the latest stock image and see if that fixes your problem
Click to expand...
Click to collapse
i am trying that now nexus tool klit 1.5.5
http://www.droidforums.net/forum/galaxy-nexus-development/192031-toolkit-nexus-root-toolkit-v1-5-5-updated-11-04-12-a.html
i selected the recovery / unroot with the checkbox of softbrick/bootloop....
So far so good... I have isntalled a few apps and now listening to ihart radio and will reboot the phone in a little bit and see what happens. Also is this nexus root kit 1.5.5 the best to root it as well...
Still doing the stuck at google logo... gonna leave it their for a bit and see what happens. It took about a minute or two... to get passed the google screen...
Don't use a toolkit because if something goes wrong (which it seems to be ) you won't know what, where or why it happened. Read the stickies, learn ADB and never have this problem again. Ever. It only takes a few minutes to learn.
I mean you wouldn't hoist your engine out of your car and begin to take it apart without having any idea what you're doing, would you? Go read the stickies..... seriously
{
"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"
}
RoyJ said:
Don't use a toolkit because if something goes wrong (which it seems to be ) you won't know what, where or why it happened. Read the stickies, learn ADB and never have this problem again. Ever. It only takes a few minutes to learn.
I mean you wouldn't hoist your engine out of your car and begin to take it apart without having any idea what you're doing, would you? Go read the stickies..... seriously
Click to expand...
Click to collapse
you mean the mr fusion engine wont work in my DeLorian....
http://blogs.discovermagazine.com/discoblog/files/2008/04/mr-fusion.jpg
My gnex was doing the same thing every time I rebooted I had to pull the battery for it to start up. I actually just left it one day for like 30 mins on the splash screen and I guess it just took its time cause now it starts up normally
Sent from my Galaxy Nexus using xda app-developers app
My phone has done this twice. Both times, I solved it by pulling the battery for about 30 seconds, popping it back in, and letting it boot like normal.
Card83 said:
My phone has done this twice. Both times, I solved it by pulling the battery for about 30 seconds, popping it back in, and letting it boot like normal.
Click to expand...
Click to collapse
i wonder if it has something to do with automatically zip aligning at boot or something? I hate to waite as i did pull the battery at times for 3 or 4 minutes and still had to wait a few minutes at boot...
rezoundness said:
i wonder if it has something to do with automatically zip aligning at boot or something? I hate to waite as i did pull the battery at times for 3 or 4 minutes and still had to wait a few minutes at boot...
Click to expand...
Click to collapse
When running JellyBean, the Nexus can sometimes run a filesystem check (similar to Windows' chkdsk or *nix fsck) if it wasn't booted properly or for other random reasons. That check can take a few minutes, up to 10 minutes or so on some devices after certain actions. If anything, pulling the battery during this is doing more harm than good.
Hi,
I'm looking for some help with my currently unusable HTC One M8 on EE in the UK. I have done no rooting or making my phone S-OFF to date (and don't have the appetite for it if I'm honest) but it is now stuck in a boot loop and I don't know how to fix it.
On Monday, I accepted an OTA update which seemed to go fine but the reboot then triggered off an update to HTC Lock Screen App. This requested permission to reboot the phone and since then, the phone has been in a constant boot loop. I have tried various options including going into the menu system and selecting 'Recovery' and 'Factory Reset'. None of these options appear to do anything as the screen blanks for a moment and comes back up with the HTC initial screen and then goes into its loop. What does seem odd is that when I go into the recovery area, the menu system is unresponsive to the volume buttons until a series of code lines come up (IMAG1838.jpg)
{
"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"
}
which takes some time to cycle through. Once completed, I can then select things like 'FASTBOOT' (IMAG1840.jpg) . Picture IMAG1839.jpg is the only screen I see if i try and reboot/recover anything. I don't know if it means anything to anyone but I also took a pic of the 'IMAGE CRC' (IMAG1841.jpg) .
Can anyone help me resolve this without rooting or voiding my warranty? EE suggested speaking to HTC as they didn't have any ideas or they could send my phone away for repair. This is an option but would rather resolve myself (with help!) if I can.
Although I'm reasonably clued up on general operations of phones, the bare bones of software is a different planet so any assistance will need to be in baby steps and spoon fed (sorry).
Hope the pictures are ok? If not, I can type out the various messages.
Thanks in advance.
Phil
did you Factory Reset while at fastboot mode?
Factory Reboot
aM- said:
did you Factory Reset while at fastboot mode?
Click to expand...
Click to collapse
Hi,
Yes - I did try a factory reset but this didn't resolve the problem and it literally rebooted immediately without appearing to do anything.
Thanks
Phil
PhillipLegg said:
Hi,
I'm looking for some help with my currently unusable HTC One M8 on EE in the UK. I have done no rooting or making my phone S-OFF to date (and don't have the appetite for it if I'm honest) but it is now stuck in a boot loop and I don't know how to fix it.
On Monday, I accepted an OTA update which seemed to go fine but the reboot then triggered off an update to HTC Lock Screen App. This requested permission to reboot the phone and since then, the phone has been in a constant boot loop. I have tried various options including going into the menu system and selecting 'Recovery' and 'Factory Reset'. None of these options appear to do anything as the screen blanks for a moment and comes back up with the HTC initial screen and then goes into its loop. What does seem odd is that when I go into the recovery area, the menu system is unresponsive to the volume buttons until a series of code lines come up (IMAG1838.jpg) View attachment 2966734 which takes some time to cycle through. Once completed, I can then select things like 'FASTBOOT' (IMAG1840.jpg) View attachment 2966736. Picture IMAG1839.jpg View attachment 2966735is the only screen I see if i try and reboot/recover anything. I don't know if it means anything to anyone but I also took a pic of the 'IMAGE CRC' (IMAG1841.jpg) View attachment 2966747.
Can anyone help me resolve this without rooting or voiding my warranty? EE suggested speaking to HTC as they didn't have any ideas or they could send my phone away for repair. This is an option but would rather resolve myself (with help!) if I can.
Although I'm reasonably clued up on general operations of phones, the bare bones of software is a different planet so any assistance will need to be in baby steps and spoon fed (sorry).
Hope the pictures are ok? If not, I can type out the various messages.
Thanks in advance.
Phil
Click to expand...
Click to collapse
Try powering down, then holding power up+power for 20 seconds. This is the equivalent of a battery pull.
Might work, might not. Give it a shot.
Then report back. I/someone might come up with a different solution if it doesn't work for you.
Battery Pull
xunholyx said:
Try powering down, then holding power up+power for 20 seconds. This is the equivalent of a battery pull.
Might work, might not. Give it a shot.
Then report back. I/someone might come up with a different solution if it doesn't work for you.
Click to expand...
Click to collapse
Hi, it was a good idea - but unfortunately this hasn't resolved the problem. Sounds like it's going away for repair unless any other forum users have a stroke of inspiration. It does feel like something has overwritten or corrupted the bootup code somehow!! At least it doesn't feel like anything I've done so warranty is still in place
Thanks for your help.
Two weeks back I tried to manually update my phone to 2.40.168, since i am missing the "system update" option in the settings. I installed a new recovery.img boot.img and droidboot.img and it update the recovery to WW-2.40.168 :good:. I still couldn't update the firmware though and decided to quit trying.
Now I want to put CM13 on it and wanted to change the recovery. BUT when i press Power Up + Volume Up, release the power up this shows up.
{
"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"
}
I can restart it by long pressing the power button but that is about it.
Also i searched for fixes but didn't find anything hence made a post.
Ok so basically what he is saying is that his phone does NOT even have recovery mode. Where we get the dead android guy he gets this and is thus unable to flash his phone with new recovery or system.
That happened to a friend of mine a long time ago but he threw away his phone ( sold it for cheap ) without trying much.
Are there any ACTUAL solutions ?
Again Power + vol up keys DO NOT bring up recovery mode/fastboot or however you want to call it.
Anyone ?
yeah - think this is just a soft brick afaik
you should be able to see the device as moorefied in windows and go from there
debully said:
yeah - think this is just a soft brick afaik
you should be able to see the device as moorefied in windows and go from there
Click to expand...
Click to collapse
"moorefied" ?? Can you explain ?
xRanker said:
"moorefied" ?? Can you explain ?
Click to expand...
Click to collapse
just read some soft/hard brick threads - download the shizzle, install it properly on your machine and follow the instructions.
you have a good chance.
Personally I have no chance as the device wont even turn on. Asus support are absolutely useless and I WILL NEVER, EVER BUY ANOTHER PRODUCT FROM THEM AGAIN - and I'd advise you to do the same. These forums are littered with soft/hard bricks.
debully said:
just read some soft/hard brick threads - download the shizzle, install it properly on your machine and follow the instructions.
you have a good chance.
Personally I have no chance as the device wont even turn on. Asus support are absolutely useless and I WILL NEVER, EVER BUY ANOTHER PRODUCT FROM THEM AGAIN - and I'd advise you to do the same. These forums are littered with soft/hard bricks.
Click to expand...
Click to collapse
That is mostly because people touch where they are not supposed to ^^
But um thanks for reply.
With respect, you don't know what you're talking about.
I've been flashing since the HTC canary. I've never once had a bad flash. Nor here. The phone is prone to hard bricking way in excess of the norm and you only need to look at these forums to see that.
But thanks, your response was greatly valued and added to the weight of knowledge.
debully said:
With respect, you don't know what you're talking about.
I've been flashing since the HTC canary. I've never once had a bad flash. Nor here. The phone is prone to hard bricking way in excess of the norm and you only need to look at these forums to see that.
But thanks, your response was greatly valued and added to the weight of knowledge.
Click to expand...
Click to collapse
Not so sure of that, I really think its more user error than anything else, especially when it comes to fastboot. Copy and paste isn't your friend and it seems most people overwrite their boot or fastboot partitions with system files because they use the same command but change the img file name.
Have never had an unrecoverable brick, and those soft bricks I've had were my fault by not reading properly or skipping through steps quickly.
XepouH said:
Two weeks back I tried to manually update my phone to 2.40.168, since i am missing the "system update" option in the settings. I installed a new recovery.img boot.img and droidboot.img and it update the recovery to WW-2.40.168 :good:. I still couldn't update the firmware though and decided to quit trying.
Now I want to put CM13 on it and wanted to change the recovery. BUT when i press Power Up + Volume Up, release the power up this shows up.
I can restart it by long pressing the power button but that is about it.
Also i searched for fixes but didn't find anything hence made a post.
Click to expand...
Click to collapse
Find your answer here
Hi!
On 24th of April, 2017 I just bought a bricked LG G3 D855 from a guy who said it was caused by updating firmware while on low battery, died during processing and that's it. Bought it for $60.
I've got some experience over bricked devices and stuff, Galaxy S2, S3, S5 and other chinaphones.
Anyways, managed to put 4.4.2 on it, worked decent, I think, laggy (laggier than my s2/s3) but bearable. Updated to 5.1 or 5.0 but couldn't get 6.0. So flashed .kdz as recommended on forums using LGUP. The process went smooth but the phone was just rebooting, freezing and got very hot; pretty much unusable.
I thought it was time to flash custom roms; finally managed to get root running on MM, but when to get AutoRec to do it's job, the kernel just crashed and crashed. Had to learn about debricking using QDLoader method... Managed to finally get back to 4.4.2 but it was waaaaay worse than my first attempt using it. Started behaving like 6.0: rebooting, freezing and got very hot. Always leading to get bricked and doing the QDLoad method again and again.
Finally, root got installed and flashed Bump! twrp to 'unlock' it. TWRP 2.8 was pretty ... meh. Couldn't install fulmics using this twrp, so had to move to 3.0, right? Well right after getting TWRP 3.0, the phone get really hot into recovery, even over 90 degrees C and all the partitions fail to mount and randomly, at LG logo boot get failed certificate verification, kernel crashes etc. and having a really difficult time reflashing .tot file to phone, using LGFlashTool 1.8. I've got about 20 tries per day and about half lead to QDLoader brick ...
What to do?
Could the mainboard be corrupted? BoardDiag said it passed AP, EMMC and SDRAM tests.
Tried using different USB ports; tried my PC and my laptop; tried windows 8.1 and 7, everything up to date. The cable is brand new from a samsung.
Tried lg 4.2 driver and 3.12.
While flashing no sdcard/sim were inserted.
In LGFlashTool I've got the main .dll for the firmware and also the LGUP8974.dll from the forum (model check failed)
Also gave it a try with LGUP flashing .tot file, hangs at 99% most of the time and it's a slow process.
Also, while flashing .tot file phone randomly reboots again into Firmware Update and have to redo the process again and again.
Please, help! Anything else you're interested about, ask. I've lost about half of week worth of hours trying to make this thing work.
AKAndrew41 said:
Please, help! Anything else you're interested about, ask. I've lost about half of week worth of hours trying to make this thing work.
Click to expand...
Click to collapse
I had a similar problem with a G3 and - for me - it turned out to be a hardware/solder issue on one of, or mutiple chips; the skydragon and PMIC chips specifically.
What worked for me - only temporarily - was using a heat gun on the bottom rt corner of the chip that has an orange square around it(skydragon), and the unmarked chip directly to the right(PMIC) in between the yellow and blue chips in this pic:
{
"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"
}
After I heated that area the phone was able to take a full download, stopped rebooting, and worked great...for about 2 days. But then the kernel crashes, BSOD, and qualcomm9008 mode all came back eventually. Maybe I simply didn't use enough heat, but at that point I had a replacement phone and just gave up on it. There are other posts about people baking their motherboards (which scares the hell out of me so I refuse to do it), but hey - if you're desperate that may be a way to go. There are some other posts about using a heat gun as well; read up on what temps to use if you need to go that route.
How I came to the conclusion of where to heat the board was done by me pushing on those spots on the board while trying to power up/charge/flash the phone. For ex: NOT pushing on that area of the board the phone would lose downlaod mode and be seen as qualcomm9008 in device manager; by unplugging the phone, then pushing on the chips and plugging the phone in again download mode would start working and the phone would charge normally again.
So give your phone a healthy fingerbang in the right place and it may show you where your problem is. Hopefully it isn't a hardware issue, but it sounds like you've exhausted all of your software options so it just may be.
Good luck:good:
*Here's some info on G3 issues/fixes; you'll see a common theme(bad solder)...https://forum.xda-developers.com/lg-g3/general/g3-hardware-problems-solved-bsod-screen-t3597086
*G3 motherboard link for reference...https://www.ubreakifix.com/blog/lg-g3-teardown
*Try a non-samsung cable too; G3's can be finicky with cables sometimes.
Recovery errors
After hours and hours trying to get into recovery, I am welcomed by those beautiful errors:
http://imgur.com/63cd8iy
http://imgur.com/9pFyRZs
And wiping data takes forever, if ever happens... http://imgur.com/pZjLsNP Stays here for a good half hour.
Please, help?!
AKAndrew41 said:
After hours and hours trying to get into recovery, I am welcomed by those beautiful errors:
http://imgur.com/63cd8iy
http://imgur.com/9pFyRZs
And wiping data takes forever, if ever happens... http://imgur.com/pZjLsNP Stays here for a good half hour.
Please, help?!
Click to expand...
Click to collapse
You could had use lg flash tool to flash the 4.4.2 update and then a quick factory reset