Related
So I was rockin' my 4.1 rom earlier and listening to music when my headphone cord got stuck on my chair and my phone fell off my desk to the ground. Everything was still going but my touch screen stopped working. I hit the unlock (power) button and it would show the correct unlock screen but I could not slide to unlock.
I pulled the battery and ever since then my phone would not boot. Stuck in boot loops, etc. I tried restoring from Nandroid (even back to my 4.0.4 image) and it would get stuck on unable to load /data at the end. I eventually went back and installed Nexus Toolkit 7.0 on my home pc and proceeded to load the stock 4.0.2 back on and root. However, it still is stuck in a boot loop. I'm now at a loss of what to do. My sd card has already been wiped and my phone is still not booting.
I'm at your mercy if anyone can give me any direction - please!
jedil1c1ous said:
So I was rockin' my 4.1 rom earlier and listening to music when my headphone cord got stuck on my chair and my phone fell off my desk to the ground. Everything was still going but my touch screen stopped working. I hit the unlock (power) button and it would show the correct unlock screen but I could not slide to unlock.
I pulled the battery and ever since then my phone would not boot. Stuck in boot loops, etc. I tried restoring from Nandroid (even back to my 4.0.4 image) and it would get stuck on unable to load /data at the end. I eventually went back and installed Nexus Toolkit 7.0 on my home pc and proceeded to load the stock 4.0.2 back on and root. However, it still is stuck in a boot loop. I'm now at a loss of what to do. My sd card has already been wiped and my phone is still not booting.
I'm at your mercy if anyone can give me any direction - please!
Click to expand...
Click to collapse
Try restoring using ODIN
the process wipes all data, but since you said its already wiped that shouldnt be a problem for you.
IF it still doesnt work, then it isnt software, but rather hardware, and you should probably go get that fixed
good Luck
Return To Stock Using Odin:
http://forum.xda-developers.com/showthread.php?t=1620036
I have Verizon GN, can I still use ODIN?
jedil1c1ous said:
I have Verizon GN, can I still use ODIN?
Click to expand...
Click to collapse
Yes you can still use ODIN,
as ODIN is software for samsung phones,
just make sure you use the zerizon file ratehr than the sprint..
or there could be dragons ahead
but there will always be a way to return to stock
Although, i would use this, because it is mostly aimed towards Verizon Users..
http://www.galaxynexusforum.com/forum/rescue-squad/4707-how-return-stock-using-odin-vzw-gsm.html
Sorry for assuming you had sprint..
I dont know what was going on in my head
I found the correct VZW version within XDA... thanks for the tip... I actually have it running right now (fingers crossed).
Good Luck,
hopefully you get your phone back online
Wolfbeef123 said:
Good Luck,
hopefully you get your phone back online
Click to expand...
Click to collapse
Unfortunately, even after using ODIN I'm stuck in the boot loop. It must be busted hardware. Guess I will have to use the Samsung warranty service. Stink.
jedil1c1ous said:
Unfortunately, even after using ODIN I'm stuck in the boot loop. It must be busted hardware. Guess I will have to use the Samsung warranty service. Stink.
Click to expand...
Click to collapse
If you got your phone from Verizon, try them first. Easier than dealing with Samsung directly
harveydent said:
If you got your phone from Verizon, try them first. Easier than dealing with Samsung directly
Click to expand...
Click to collapse
I actually bought it through Amazon and called them and they said go to Verizon even without the purchased insurance.
My phone looks mint though so I'm very hopeful that I will receive service from the Verizon store.
Does the lock icon show while looping? You might think about a shot in the microwave for 3 seconds (don't take me seriously.....well maybe)
good day.
chopper the dog said:
Does the lock icon show while looping? You might think about a shot in the microwave for 3 seconds (don't take me seriously.....well maybe)
good day.
Click to expand...
Click to collapse
I did flash lock it with ODIN... so the unlock icon does not show. It boots to the animation and then restarts after it shows for 5 seconds. I think the touch screen is malfunctioning and causing it to reboot.
Can you turn it off and then turn it on while holding volume down and up at the same time (i.e., can you boot into fastboot/bootloader?)
If so... it's not over yet.
However, if you dropped it it's probably hardware. But if you can get into the bootloader, at least you can lock it before bringing it in.
looks like your nand chip failed. had the same problem with my S2 and even a JTAG didnt fix it, had to send it to warranty to have the board replaced
Just got my used t-mobile note 2 on monday.I am having issues with the phone where the screen will start scrolling on it's own and keep trying to launch media hub or the weather widget and then the screen eventually freezes and won't respond.I have downloaded the emmc program and my phone doesn't have the defective chips.I have done 2 factory resets and the problem still persists and happens as it is being reset.Any one know what could be going on?If i leave the sim out the phone works fine though.
Best guess water damage. Check the tabs. Also get a new sim.
travispittman said:
Best guess water damage. Check the tabs. Also get a new sim.
Click to expand...
Click to collapse
Did another factory reset but before that deleted some apps i had downloaded and made sure to disable samsung media hub,gps and the weaqther widget and so far the phone has been fine.
Is it factory rom and kernel or has it been messed with? I originally bought an s4. Connected it to a shady charger and changed the polarity of the board. It was hard to get to take a charge and wouldn't hold a charge for very long. Went to have it looked at by a tech. Before he knew what I was there for he offered to trade me for a note 2. He looked my phone over and we swapped. Usually when people get rid of a phone it is not because they upgraded but because something is wrong. I dislike buying used for that reason. I have had ppl try and pass off water damaged stuff and all kinds of randomness. I always boot reboot and reboot and used phone before buying, Keep them there as long as possible to see if something is wrong. Ask a lot of questions. Usually when you purchase a used phone especially an expensive one such as the note2 you want to get what you are paying for and not duped into paying a lot of money for some ones broken mess.
It's factory original rom and kernel.
same here
dukenukems said:
Just got my used t-mobile note 2 on monday.I am having issues with the phone where the screen will start scrolling on it's own and keep trying to launch media hub or the weather widget and then the screen eventually freezes and won't respond.I have downloaded the emmc program and my phone doesn't have the defective chips.I have done 2 factory resets and the problem still persists and happens as it is being reset.Any one know what could be going on?If i leave the sim out the phone works fine though.
Click to expand...
Click to collapse
This may seem silly, but have you tried to clean the screen with a microfiber cloth? This same problem happened to me (except the weather widget part), and after a spray n' clean, it all got fixed.
Well huys i was able to root my phone pretty easily but am still on the stock rom it came with.Will using other roms and stuff be a bit easy for me to install or will it be tough since this is my first rooting adventure.
dukenukems said:
Well huys i was able to root my phone pretty easily but am still on the stock rom it came with.Will using other roms and stuff be a bit easy for me to install or will it be tough since this is my first rooting adventure.
Click to expand...
Click to collapse
It's simple as long as you have the ability to read through threads prior to flashing. 98% of problems with custom software installs is due to lack of patience by the flasher. Read alot, flash a little is a safe way to get started.
Hastily spouted for your befuddlement
I've rooted it and have tryed 2 different roms already.Just sad that my note 2 still has the screen lock up allthough using spen remains fine.
Well guys my hone had started to lovk up even at the boot screen and didn't want to respond to the spen either so i went into recovery mode and dids factory reset with cwmr but after i rebooted my phone it was stuck in infinite boot loop.Just reflashed phone with it's stock rom image from this site using odin but my phone will only boot to the t-mobile 4glte screen and won't go any further.I have gone back into recovery mode and factory reset but still the same problem.Is my phone bricked?
dukenukems said:
Well guys my hone had started to lovk up even at the boot screen and didn't want to respond to the spen either so i went into recovery mode and dids factory reset with cwmr but after i rebooted my phone it was stuck in infinite boot loop.Just reflashed phone with it's stock rom image from this site using odin but my phone will only boot to the t-mobile 4glte screen and won't go any further.I have gone back into recovery mode and factory reset but still the same problem.Is my phone bricked?
Click to expand...
Click to collapse
Not sure if I am allowed to post links to other sites, but check out: galaxynote2root.com. max has a tutorial for almost everything! Also did you do a full wipe? Whenever installing a new ROM if you get stuck in a boot loop go back to recovery and do a wipe again, also wipe cache, and dalvik as well. Hope this helps!
Flashed thw original rom image with odin but the original will jsut hang at the tmobile splash screen and never fully boot.I was able to flash the phone with twrp with odin and was able to use twrp from my phone to reinstall the jedix20 rom which does install and been working since.No matter what i do with the original factory image it will always refuse to boot past the tmobiole splash screen.
I've had my Samsung Galaxy Tab S 8.4 (SM-T705Y) for just over two years now and it has worked brilliantly beside the odd issue here and there, including the device freezing from time-to-time. Each time that particular freezing issue has happened, I've used the 'Power and Volume Down buttons' technique and it has successfully fixed the issue.
Now, a few days ago, I was using my tablet for normal morning things; music app playing in the background, YouTube opened on the side, using the preinstalled Browser and Google Chrome apps, etc. I am not sure if it was updating any Google or Samsung apps at the time. The screen froze up so I left it for a few minutes, seeing if it would unfreeze. When it didn't, I used the same Power and Volume Down technique, which successfully forced-restarted the tablet. There was a small mistake I made doing this; I was holding down both the Power button and Volume Up button. It took me around thirty seconds to realise why the screen wasn't turning off and switched to the Volume Down button. At the time, both my earphones and the charging cord were connected.
However, upon the loading screen, I noticed that it did not pass the Samsung logo screen with the little explosion of blue circles and just kept replaying the same animation repeatedly. The Application History and Back buttons did not light up and the device did not vibrate as it normally does when it boots up. I repeated the Power-Volume Down technique to see if that would fix the issue. Once again, the tablet rebooted normally but was stuck at the logo screen playing the animation. I tried this same force-restart again, this time without the charger plugged in. No change.
So, I left it running through the animation while doing Google searches through forums and getting into contact with Samsung as to what the issue could be. I'll list down below what my tablet can and can't do at the moment and hopefully someone will have a clue as to what is going on and how to fix it. I will point out now that it was not going through a firmware update at the time, the device is not rooted and nor do I plan on taking that path with it, and I have not made any changes to it that can void the warranty.
It can:
- Recharge (The battery icon will show up if it is force-restarted and the charger is plugged in at the time.)
- Reboot (It's not exactly stuck in a bootloop, more of just the 'explosion' animation replaying over-and-over.)
- Enter Recovery Mode
It cannot:
- Enter Safe Mode
- Be Shut Down without the charger attached (As stated above, the device will only turn off with the Power-Volume Down buttons held for about 30 seconds and that causes the device to restart, not turn off. The only way for it to completely shut down is to have the charger connected and then unplug it after the battery icon appears.)
I have tried removing the SD card and placing it back in, power-cycling it, letting it run on the animation until the battery runs out and then letting it recharge to 100% before turning it on again, connecting it to Samsung Smart Switch (which recognises that there is a Samsung device connected, but not being able to register the device itself), and wiping the Partition Cache (Also note; the Recovery Mode has the 'No Command' sign with the android laying down and the red triangle with the exclamation point above it. Clearing the Partition Cache seemed to go smoothly, however when I chose the 'reboot device now' option, the 'No Command' sign changed to 'Error!' and rebooted the device anyway.) I am now currently trying another technique written on a different website (though since I am a new user, I cannot post up URLs at the moment). So far, plugging in the earphones alone hasn't worked and the device is currently connected to my laptop - which is shut off - and still has the earphones connected, but the animation is the only thing the screen is still showing.
I have important files saved in the internal storage of my Tab S and I do not have them backed up, which is the only issue that's stopping me from just going ahead and doing a Factory Reset as I cannot lose these files.
I am unsure if my Tab S is soft-bricked or if this is another issue entirely and I just missed something that could have already fixed it.
Yes, this is a long and detailed post, but hopefully with these details, someone will be able to help with this issue. If I can restore my Tab S to its condition before the freeze, that would be amazing, but I can definitely settle with only being able to salvage my files from the internal storage and then performing a Factory Reset on it.
Thank you in advance~
It might be a corrupt partition. The way i know involve rooting or the other one might format your device to factory setting.
edan1979 said:
It might be a corrupt partition. The way i know involve rooting or the other one might format your device to factory setting.
Click to expand...
Click to collapse
Really? I might look into that a bit more, thanks! With the second method you mentioned, how likely are the chances of it formatting the device to the factory settings?
AussieMouse said:
Really? I might look into that a bit more, thanks! With the second method you mentioned, how likely are the chances of it formatting the device to the factory settings?
Click to expand...
Click to collapse
download the official firmware and flash it via odin. it usually fix this type of problem. but usually the files on the internal storage/sdcard will be intact. only the data apps will be gone. this will not break your warranty (its already 2 yo device... no more warranty anyway ^_^)
edan1979 said:
download the official firmware and flash it via odin. it usually fix this type of problem. but usually the files on the internal storage/sdcard will be intact. only the data apps will be gone. this will not break your warranty (its already 2 yo device... no more warranty anyway ^_^)
Click to expand...
Click to collapse
Alright, I'll try that and let you know how it goes. Is there any specific website I should download the firmware (4.4.2 KitKat) from? (Yeah, I agree with you there! Still, just to be on the safe side~)
KIT KAT? ok that's old... hahaha... why dont you try MM. I think you can search for it at fw.updato.com probably can see all related firmware there.
edan1979 said:
KIT KAT? ok that's old... hahaha... why dont you try MM. I think you can search for it at fw.updato.com probably can see all related firmware there.
Click to expand...
Click to collapse
Haha Yeah, I'm not too fond of installing software updates due to past experiences~ I'll have a look around.
AussieMouse said:
Haha Yeah, I'm not too fond of installing software updates due to past experiences~ I'll have a look around.
Click to expand...
Click to collapse
MM is ok. I dont have any problem with it.
edan1979 said:
MM is ok. I dont have any problem with it.
Click to expand...
Click to collapse
Thank you so much for your help! I managed to find the KitKat 4.4.2 firmware on SamMobile and flashing it restored everything~
Have had this problem for about two weeks now. Every time I get the phone able to boot (either by reflashing a rom or odin) it will work for a few hours then it'll freeze in the middle of use or idle and restart. After restarting a few times the phone will no longer boot and I have to reflash it with odin or TWRP. It's happened so much though that as of today even if I get it to start it'll end up freezing up shortly after booting, get stuck on the black start screen and hang there until I pull the battery. At that point the phone will only boot into download or recovery. I'm at the end of what I can do and out of ideas.
So far I have tried
Odin to:
N910PVPS4COK1_N910PSPT4COK1_N910PVPS4COK1_HOME.tar.md5
N910PVPU4DPH4_N910PSPT4DPH4_N910PVPU4DPH4_HOME.tar.md5
and flashing multiple different roms to try to fix it.
Sometimes it won't even mount data, cache, system, etc within twrp.
I've also tried to format each individual partition when it wouldn't start no matter what and that did make it so it was able to start but the same problems were there after it did start.
I've searched and I cannot find a solution to anything similar to the problem I'm having. If anyone has any ideas they'd be greatly appreciated.
justintworley said:
Have had this problem for about two weeks now. Every time I get the phone able to boot (either by reflashing a rom or odin) it will work for a few hours then it'll freeze in the middle of use or idle and restart. After restarting a few times the phone will no longer boot and I have to reflash it with odin or TWRP. It's happened so much though that as of today even if I get it to start it'll end up freezing up shortly after booting, get stuck on the black start screen and hang there until I pull the battery. At that point the phone will only boot into download or recovery. I'm at the end of what I can do and out of ideas.
So far I have tried
Odin to:
N910PVPS4COK1_N910PSPT4COK1_N910PVPS4COK1_HOME.tar.md5
N910PVPU4DPH4_N910PSPT4DPH4_N910PVPU4DPH4_HOME.tar.md5
and flashing multiple different roms to try to fix it.
Sometimes it won't even mount data, cache, system, etc within twrp.
I've also tried to format each individual partition when it wouldn't start no matter what and that did make it so it was able to start but the same problems were there after it did start.
I've searched and I cannot find a solution to anything similar to the problem I'm having. If anyone has any ideas they'd be greatly appreciated.
Click to expand...
Click to collapse
Try falsh repair firmware with pit file in odin.
Do factory reset immediately from recovery after flash firmware to get clean OS.
You can download repair firmware from here
https://www.androidfilehost.com/?fid=24591020540821805
Extract firmware you will get pit file inside of it.
Trex888 said:
Try falsh repair firmware with pit file in odin.
Do factory reset immediately from recovery after flash firmware to get clean OS.
You can download repair firmware from here
https://www.androidfilehost.com/?fid=24591020540821805
Extract firmware you will get pit file inside of it.
Click to expand...
Click to collapse
I used both of them for a restore and did a factory reset and things looked good for about 30 minutes and now its back to the random freezes that turn into a restart
justintworley said:
I used both of them for a restore and did a factory reset and things looked good for about 30 minutes and now its back to the random freezes that turn into a restart
Click to expand...
Click to collapse
I suppose this is a long shot, but are you running on the original or an old battery? It's possible that a bad battery is causing the reboots. I was back and forth to the Sprint store about 4 times in one week. They first tried flashing the firmware. (Yeah, I could have done it, but I have insurance.) They sent me home and on the way my phone rebooted itself. I got a replacement Note 4, but it started getting hot, then also rebooting. They "let" me upgrade to a Note7, which I loved. I had to give it back even though it was from the new, supposedly safe batch. At this point, I couldn't even get the Note 4 to boot at all. Boot loops, or would boot into download mode. Couldn't do anything with it, except pull the battery. Got a third Note 4, but also ordered a new battery pack from Sprint. They were and still are, only $24.95, with free shipping! You get a new battery, an external charging unit and a carrying case for the battery. (You have to use your own charger.) This finally fixed the problem. I had two batteries when I ordered the new one. I'm pretty sure one of the older batteries was defective, even though it wasn't bulging. I'm still using the other one that's also older, even though it is bulging a bit. It charges and runs fine. No over-heating. So, my problem was a combination of a defective battery and a couple of bad phones. The other thing was some of the previous firmware seemed to make some Note 4s run hot or get hot while charging. Things are much better since PG1. YMMV.
I had this issue and sent my phone back to Samsung THREE TIMES, I thought I bricked my phone from custom rom.
Turns out it was my battery. Sounds dumb, but true. Strangely even with battery out, I was having issue. Once I put in new good battery issue resolved.
I had that issue on my pc and my note. I had a creepy stalker in full control of my device (which basically was a virtual machine). I could tell when I was on the right track to get rid of him because it shut me down. I can't say that's what's going on with you but it is a thing.
Sent from my SM-N910P using Tapatalk
Note 4 batteries are dying for lots of people anywhere from 18 months to just over 2 years, and the symptom is often fail to boot, boot loops, etc. As piggynuts said, it's not logical, but it's true. It happened to me, and when I replaced the battery, everything was fine.
I decided to apply heat to the CPU using a heat gun for 15 seconds. It was extremely hot. I tapped the CPU a few times with another object to see if that would help. Once I put my phone back together, the phone finally turned on, however it would not boot.
So while I can actually fire my phone on now without putting it into the freezer and I can even get into recovery without any issue, the phone will not boot into the system. I have completely backed up all of my files, moved around many files, left the phone in recovery for an hour, and successfully flashed several roms in an attempt to boot into the system, none of this has worked. Instead my phone hangs on "life's good", it does not reboot itself, it stays on this screen for an eternity.
I would like to hear any ideas! I want to test updating the bootloader by flashing the stock rom, but I don't remember which firmware I last flashed and this could brick if flashed in the wrong order, does anyone know how to check the firmware? Another idea, is there any way to debug the boot or is there a boot log to see where it is hanging?
Thanks!
RandomUSA said:
I decided to apply heat to the CPU using a heat gun for 15 seconds. It was extremely hot. I tapped the CPU a few times with another object to see if that would help. Once I put my phone back together, the phone finally turned on, however it would not boot.
So while I can actually fire my phone on now without putting it into the freezer and I can even get into recovery without any issue, the phone will not boot into the system. I have completely backed up all of my files, moved around many files, left the phone in recovery for an hour, and successfully flashed several roms in an attempt to boot into the system, none of this has worked. Instead my phone hangs on "life's good", it does not reboot itself, it stays on this screen for an eternity.
I would like to hear any ideas! I want to test updating the bootloader by flashing the stock rom, but I don't remember which firmware I last flashed and this could brick if flashed in the wrong order, does anyone know how to check the firmware? Another idea, is there any way to debug the boot or is there a boot log to see where it is hanging?
Thanks!
Click to expand...
Click to collapse
Just flash V20p, is good to fix and to downgrade from Nougat.
Maybe you didn't heat only the CPU... the audio chip don't like to heated.
Try vol- + Power, when you see the logo release power for a second and press and keep it, maybe you're able to factory reset.
If it doesn't work, take out battery and put it back again, turn on the phone (even if is stuck on LG logo) and leave it for about 10 minutes.
RuedasLocas said:
Just flash V20p, is good to fix and to downgrade from Nougat.
Maybe you didn't heat only the CPU... the audio chip don't like to heated.
Try vol- + Power, when you see the logo release power for a second and press and keep it, maybe you're able to factory reset.
If it doesn't work, take out battery and put it back again, turn on the phone (even if is stuck on LG logo) and leave it for about 10 minutes.
Click to expand...
Click to collapse
I am certain I did not exclusively heat up the CPU, the board is very small and the output of the heatgun is relatively large. Anyway, I couldn't find anything through google that would indicate heating up the audio chip would cause boot issues, if you have any more information on this I would appreciate it.
The vol-+power allows me to get to my TWRP install, I have an unlocked bootloader and TWRP installed as my recovery. I have completely wiped the device before attempting to install various roms. I have not tried installing 20p as it seems you need to be either on 20o or 20p and I am not sure if downgrading is safe (assuming I am on a later version).
I am shooting in the dark even trying to install a new ROM, the one I had should work obviously. I would really like to check what firmware I am on before upgrading/risking permanently bricking the device. Any boot debugging would be extremely useful if possible
RandomUSA said:
I am certain I did not exclusively heat up the CPU, the board is very small and the output of the heatgun is relatively large. Anyway, I couldn't find anything through google that would indicate heating up the audio chip would cause boot issues, if you have any more information on this I would appreciate it.
The vol-+power allows me to get to my TWRP install, I have an unlocked bootloader and TWRP installed as my recovery. I have completely wiped the device before attempting to install various roms. I have not tried installing 20p as it seems you need to be either on 20o or 20p and I am not sure if downgrading is safe (assuming I am on a later version).
I am shooting in the dark even trying to install a new ROM, the one I had should work obviously. I would really like to check what firmware I am on before upgrading/risking permanently bricking the device. Any boot debugging would be extremely useful if possible
Click to expand...
Click to collapse
I got a very delayed boot up when I thought that my problem with one of the microphones was related with bad welding also. So, I heat it (Qualcomm WCD9330 Audio Codec) and it took a lot for the phone 1st boot after that.
The V20p is flashable no matter what version you have before, just need the right "8994.dll" file to be installed without problems. You can extract it from the v20p.kdz.
Good luck!
RuedasLocas said:
I got a very delayed boot up when I thought that my problem with one of the microphones was related with bad welding also. So, I heat it (Qualcomm WCD9330 Audio Codec) and it took a lot for the phone 1st boot after that.
The V20p is flashable no matter what version you have before, just need the right "8994.dll" file to be installed without problems. You can extract it from the v20p.kdz.
Good luck!
Click to expand...
Click to collapse
I might try playing with the audio chip, but there's currently no indication that the phone will progress past the boot screen. Instead of updating my phone via TWRP, I decided to get set up with LGUP following your advice. I have tried refurbish/upgrade without luck. The process seems to complete entirely and successfully, however my phone still hangs on the boot screen. Perhaps noteworthy, at the boot screen the phone is in standby mode and windows identifies the device as "LGE AndroidNet USB Serial Port (COM4)". This is the same as when it is put into download mode.
Do you know if this is normal behavior?
RandomUSA said:
I might try playing with the audio chip, but there's currently no indication that the phone will progress past the boot screen. Instead of updating my phone via TWRP, I decided to get set up with LGUP following your advice. I have tried refurbish/upgrade without luck. The process seems to complete entirely and successfully, however my phone still hangs on the boot screen. Perhaps noteworthy, at the boot screen the phone is in standby mode and windows identifies the device as "LGE AndroidNet USB Serial Port (COM4)". This is the same as when it is put into download mode.
Do you know if this is normal behavior?
Click to expand...
Click to collapse
Try to don't mess with the audio chip!
Turn ON the phone with no cable connected.
Mine have that long boot only the 1st time, after that behaves normally.
Mine when I connect to PC (USB2), option "Only Charge" on the phone and turn ON, is shown in Device manager as "Android device/ Android Sooner Single ADB Interface"
Also as "Device/G4"
After change the option "Only Charge" to "Multimidia Devica (MTP)", is shown as "Android Device/LGE Mobile ADB Interface".
Also as "Portable Device/G4", and, "Modems/LGE Mobile USB Modem".
Of course that until your phone boot completly you can't do any changes...
In "Firmware Update" mode, comes as "LGE AndroidNet USB Serial Port (COM4)" and also as "Modems/ LGE AndroidNet USB Modem".
BTW... you install "LGUSBModemDriver_Eng_WHQL_Ver_4.9.4_All" and "LGMobileDriver_WHQL_Ver_4.2.0" ? Maybe it helps to have those installed before flash.
Maybe it is the same in some devices (also depending on the phone Firmware version) to have those or others but, mine only work with those two installed.
Try this:
Re-flash with LGUP using the v20p again.
After the process is done and the long boot starts (wait 5 minutes or so), take out the battery, let the phone cool down for 10 minutes.
Insert the battery back on the phone and turn it ON.
Leave it until boot finish, go for a walk, watch some TV, forget about the phone.
Of course that if after 30 minutes stills without boot up, you can consider that you have a problem. And me out of ideas... sorry.
Wish you all the best luck on that, regarrds.
RandomUSA said:
I decided to apply heat to the CPU using a heat gun for 15 seconds. It was extremely hot. I tapped the CPU a few times with another object to see if that would help. Once I put my phone back together, the phone finally turned on, however it would not boot.
So while I can actually fire my phone on now without putting it into the freezer and I can even get into recovery without any issue, the phone will not boot into the system. I have completely backed up all of my files, moved around many files, left the phone in recovery for an hour, and successfully flashed several roms in an attempt to boot into the system, none of this has worked. Instead my phone hangs on "life's good", it does not reboot itself, it stays on this screen for an eternity.
I would like to hear any ideas! I want to test updating the bootloader by flashing the stock rom, but I don't remember which firmware I last flashed and this could brick if flashed in the wrong order, does anyone know how to check the firmware? Another idea, is there any way to debug the boot or is there a boot log to see where it is hanging?
Thanks!
Click to expand...
Click to collapse
first of all: what model? we have 11 models for the g4 and not all behave the same way.
second: use SALT. SALT shows your previously installed firmware
third: try flashing custom ROMs instead of STOCK
fourth: I guess you know about http://bit.do/ilapofixg4 ?
.
steadfasterX said:
...
third: try flashing custom ROMs instead of STOCK
...
.
Click to expand...
Click to collapse
Hi @steadfasterX!
I have a question... apart "bugs", what else have a custom ROM that can make a device with hardware issues run better?
I'm asking because I never had/saw a custom ROM working 100%, even without hardware issues, at least on LG.
There's always something that doesn't work, or, with quality/performance issues.
My doubt is, if a device have problems to boot with the firmware that was exclusively made for it, won't have the same or more issues with another one?
In case of faulty hardware, firmware (stock or not) will make any difference?
Don't think that I'm kind of messing with you. I really have those doubts.
Regards
RuedasLocas said:
Hi @steadfasterX!
I have a question... apart "bugs", what else have a custom ROM that can make a device with hardware issues run better?
I'm asking because I never had/saw a custom ROM working 100%, even without hardware issues, at least on LG.
There's always something that doesn't work, or, with quality/performance issues.
My doubt is, if a device have problems to boot with the firmware that was exclusively made for it, won't have the same or more issues with another one?
In case of faulty hardware, firmware (stock or not) will make any difference?
Don't think that I'm kind of messing with you. I really have those doubts.
Regards
Click to expand...
Click to collapse
I do not say a custom ROM is running better... but for debugging issues its easier to run custom ROMs and they do not have many of the dependencies a STOCK ROM has (like several partitions we never need on custom ROMs but on stock) which can prevent from booting.
.
steadfasterX said:
I do not say a custom ROM is running better... but for debugging issues its easier to run custom ROMs and they do not have many of the dependencies a STOCK ROM has (like several partitions we never need on custom ROMs but on stock) which can prevent from booting.
.
Click to expand...
Click to collapse
Thanks for responding! I have a t-mobile h811 variant, LGUP/SALT currently shows my firmware as 20p, I decided to try updating to 20x using lg bridge, but the firmware is still listed as 20p despite the process being completed 'successfully'.
I know that flashing the KDZ worked because it overwrote my recovery and I no longer have access to TWRP. Before flashing the KDZ I tried several ROMS (stock 20p, aokp, lineage OS).
Now the phone is bordering on being a paperweight because I have no means of installing TWRP. I have an unlocked bootloader but there is no way for me to enter the bootloader. Is it possible to repackage a KDZ with a custom boot image or custom recovery?
Before flashing the KDZ and losing access to TWRP, I tried modifying the system boot.img to limit the number of cores that could be used to 4, and even 2 cores without any luck.
Right now, I don't think the phone has any bootloop issue or heat related problem because powering on the phone has become perfectly functional, the phone does not reboot itself (just stays at "Life's Good" with the blue blinking LED), recovery worked fine and handled a lot of load for hours reaching 40C+ on the CPU and with no issue.