Related
Hello,
Today, while I was using my phone, it restarted itself and has been stuck at a boot loop almost entirely since then. It has successfully booted up 2-3 times but will usually restart itself within 30-45 seconds of booting and then will be stuck in a boot loop again. When it has started up its usually after it has been bootlooping for a while. I have an H811 , I'm rooted and using xTreme Rom v2.0. I have had occasional random reboots here and there before but the phone always booted right up again without any issues. I haven't done anything with root/recovery since early September.
I've tried doing a factory hard reset without any luck. My phone booted up after I tried the hard reset and it was like the reset didn't happen. I can't boot into TWRP. I can boot into download mode and I tried to reset using kdz. It got to 100% but the the phone restarts and is back in the boot loop (then the lg flash tool gets an error and force quits). I've tried removing my sd and sim cards, I've tried swapping to a different battery, I've tried leaving the battyer out and letting the phone cool down. Nothing is working. I have noticed that when the phone is going to boot up correctly the full LG animation plays. When the phone is going to boot loop I only get a static LG Powered by android image.
Since I tried and failed to reset to stock using kdz, the phone no longer boots up past the LG screen. I've redownloaded the kdz file and tried to reset again with the same results. When I have it in download mode Windows recognizes the phone but it says there's an issue with the MTP driver. I've reinstalled the drivers and I still get that the MTP function isn't working correctly.
Any suggestions?
Hey man u r just having my problem. There is a thread already for this http://forum.xda-developers.com/showthread.php?t=3233160
Did u do CSE flash? If not, try to connect via adb.
Sent from my LG-H815 using Tapatalk
I am having the same issue. I have T-Mobile G4 that is NOT rooted. I bought it on release day. I too would get random reboots, particularly after the recent security update. I also noticed that the operating temperature was really high, a lot lately. I thought it was a rogue app (clean master). Anyway, I updated a few apps and installed a few watch faces. Suddenly, my phone was drained prematurely. Plugged it into a quick charge charger when all the fun begins. Early on it would boot to the home screen but would reboot a minute or two later. Then it stopped booting to home. On two occasions that I caught, it was starting up like a firmware update just installed with the "Android is starting 1 of 143 apps" type of line. After seeing that and still not getting to home, I figured I might as well factory reset it. Well I was amazed to discover that a factory reset yields the same boot loop. All I get is the LG logo.
Defeated. I go to my local TMo retailer where I bought the phone only to find out that I have to wait for delivery of a replacement. I'm in Jump btw. I did notice that when the phone will boot to home screen for whatever length of time, the LED would work. The LED does not work during a boot loop. My research on this issue uncovered an alarming trend on the Internet. No solution other than replacement. No cause has been identified either. Without proof, these are my top suspicions: Quick charge, 128G SD, apps moved to SD. My hunch is quick charge. All of my chargers are Qualcomm certified quick chargers. and I use them 95% of the time. I would hate to add LG to my list of boycotted Android vendors under Samsung.
IrieBro said:
I am having the same issue. I have T-Mobile G4 that is NOT rooted. I bought it on release day. I too would get random reboots, particularly after the recent security update. I also noticed that the operating temperature was really high, a lot lately. I thought it was a rogue app (clean master). Anyway, I updated a few apps and installed a few watch faces. Suddenly, my phone was drained prematurely. Plugged it into a quick charge charger when all the fun begins. Early on it would boot to the home screen but would reboot a minute or two later. Then it stopped booting to home. On two occasions that I caught, it was starting up like a firmware update just installed with the "Android is starting 1 of 143 apps" type of line. After seeing that and still not getting to home, I figured I might as well factory reset it. Well I was amazed to discover that a factory reset yields the same boot loop. All I get is the LG logo.
Defeated. I go to my local TMo retailer where I bought the phone only to find out that I have to wait for delivery of a replacement. I'm in Jump btw. I did notice that when the phone will boot to home screen for whatever length of time, the LED would work. The LED does not work during a boot loop. My research on this issue uncovered an alarming trend on the Internet. No solution other than replacement. No cause has been identified either. Without proof, these are my top suspicions: Quick charge, 128G SD, apps moved to SD. My hunch is quick charge. All of my chargers are Qualcomm certified quick chargers. and I use them 95% of the time. I would hate to add LG to my list of boycotted Android vendors under Samsung.
Click to expand...
Click to collapse
Yah mine was also on charge while it happened. But it was on LG provided charger.
nipun1110 said:
Hey man u r just having my problem. There is a thread already for this http://forum.xda-developers.com/showthread.php?t=3233160
Did u do CSE flash? If not, try to connect via adb.
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
Thanks. I'll try reposting this there. I did use CSE flash. Oddly enough it booted up once this morning for about a minute then got stuck and rebooted. Now its back in the boot loop.
IrieBro said:
I am having the same issue. I have T-Mobile G4 that is NOT rooted. I bought it on release day. I too would get random reboots, particularly after the recent security update. I also noticed that the operating temperature was really high, a lot lately. I thought it was a rogue app (clean master). Anyway, I updated a few apps and installed a few watch faces. Suddenly, my phone was drained prematurely. Plugged it into a quick charge charger when all the fun begins. Early on it would boot to the home screen but would reboot a minute or two later. Then it stopped booting to home. On two occasions that I caught, it was starting up like a firmware update just installed with the "Android is starting 1 of 143 apps" type of line. After seeing that and still not getting to home, I figured I might as well factory reset it. Well I was amazed to discover that a factory reset yields the same boot loop. All I get is the LG logo.
Defeated. I go to my local TMo retailer where I bought the phone only to find out that I have to wait for delivery of a replacement. I'm in Jump btw. I did notice that when the phone will boot to home screen for whatever length of time, the LED would work. The LED does not work during a boot loop. My research on this issue uncovered an alarming trend on the Internet. No solution other than replacement. No cause has been identified either. Without proof, these are my top suspicions: Quick charge, 128G SD, apps moved to SD. My hunch is quick charge. All of my chargers are Qualcomm certified quick chargers. and I use them 95% of the time. I would hate to add LG to my list of boycotted Android vendors under Samsung.
Click to expand...
Click to collapse
Sounds like the boot loop issue is a decent sized one- quite a few others, from different variants, having all having a similar issue. For me I was walking with my phone checking facebook when it restarted and got stuck. I definitely notice the LED issue too. I'm not on jump but will likely go into T-Mobile today and see what they tell me.
HappyPessimist said:
Sounds like the boot loop issue is a decent sized one- quite a few others, from different variants, having all having a similar issue. For me I was walking with my phone checking facebook when it restarted and got stuck. I definitely notice the LED issue too. I'm not on jump but will likely go into T-Mobile today and see what they tell me.
Click to expand...
Click to collapse
They will give u a replacement. that's all. but noone will say what's causing it.
Sent from my LG-H815 using Tapatalk
HappyPessimist said:
Thanks. I'll try reposting this there. I did use CSE flash. Oddly enough it booted up once this morning for about a minute then got stuck and rebooted. Now its back in the boot loop.
Click to expand...
Click to collapse
Exactly what happened to me. now after CSE flash of KDZ, it won't start at all. just boot looping. also after hard reset.
Last night I tried turning on my Pixel C only to see a screen saying enter android password ive never seen this screen before so i figured i would try my Google password and i got a second message saying "the password you entered is correct but unfortunately your hard drive is corrupted and you will have to factory reset your device" or something along those lines so i hit factory reset where the open android appears and it had text in the bottom saying something like erasing hard drive i left it like that since i had somewhere to go and when i came back the pixel c was completely dead so i connected it to the charger and tried turning it on and it would boot to the google logo then the four dots and just reboot all the time i was not able to even leave it turned off i did try factory resetting the pixel through android manager but still had the same problem. has anyone else experienced this problem? i have contacted google and they are sending me a replacement just wondering if anyone knows whats wrong with it and why it messed up like this
yes, i am aware of the screen and the factory reset erase sequence. but the reset sequence occured while full charge and plugged into a pc . if the battery on yours was near discharged during the erase sequence it might have completely discharged before completing the factory reset which usually results in somewhat unknown issue. best to plug it in to charger before erase sequence if this happens again. good to hear that another unit is on its way.
xm0is3sx said:
Last night I tried turning on my Pixel C only to see a screen saying enter android password ive never seen this screen before so i figured i would try my Google password and i got a second message saying "the password you entered is correct but unfortunately your hard drive is corrupted and you will have to factory reset your device" or something along those lines so i hit factory reset where the open android appears and it had text in the bottom saying something like erasing hard drive i left it like that since i had somewhere to go and when i came back the pixel c was completely dead so i connected it to the charger and tried turning it on and it would boot to the google logo then the four dots and just reboot all the time i was not able to even leave it turned off i did try factory resetting the pixel through android manager but still had the same problem. has anyone else experienced this problem? i have contacted google and they are sending me a replacement just wondering if anyone knows whats wrong with it and why it messed up like this
Click to expand...
Click to collapse
Exactly the same thing happened to me, it was fully charged back then and after I reset the tablet it went in to boot loop. I got the new replacement now and it is working better now
damjan006 said:
Exactly the same thing happened to me, it was fully charged back then and after I reset the tablet it went in to boot loop. I got the new replacement now and it is working better now
Click to expand...
Click to collapse
Tell us please, how the replacement device. Because I am from Russia and I detail it is important to find out how things are going.
dkryder said:
yes, i am aware of the screen and the factory reset erase sequence. but the reset sequence occured while full charge and plugged into a pc . if the battery on yours was near discharged during the erase sequence it might have completely discharged before completing the factory reset which usually results in somewhat unknown issue. best to plug it in to charger before erase sequence if this happens again. good to hear that another unit is on its way.
Click to expand...
Click to collapse
im guessing the battery was around 80% when it decided to mess up so i think it got stuck formatting the hard drive and just died from there
damjan006 said:
Exactly the same thing happened to me, it was fully charged back then and after I reset the tablet it went in to boot loop. I got the new replacement now and it is working better now
Click to expand...
Click to collapse
any guess why this happened to yours? im thinking it might have to do with the magnets inside the pixel C i did stick it on the fridge to see if it was pretty strong (dumb yeah i know) lol it did work fine while stuck to fridge but messed up a few hours after that
This just happened to me. Here is the sequence of events that led up to it.
1. Fully charged and unplugged it. ( I did pull the unit off the keyboard as it was propped up but this shouldn't affect the storage right? )
2. It did a random reboot after taking it off the charger.
3. It asked for my password in a "pre-boot" screen
4. The message I get is : "Decryption unsuccessful" "The password you entered is correct but unfortunately your data is corrupt.
"To resume using your tablet you need to perform a factory reset. When you set up your tablet after this reset you'll have an opportunity to restore any data that was backed up to your google account."
jlcutler said:
This just happened to me. Here is the sequence of events that led up to it.
1. Fully charged and unplugged it. ( I did pull the unit off the keyboard as it was propped up but this shouldn't affect the storage right? )
2. It did a random reboot after taking it off the charger.
3. It asked for my password in a "pre-boot" screen
4. The message I get is : "Decryption unsuccessful" "The password you entered is correct but unfortunately your data is corrupt.
"To resume using your tablet you need to perform a factory reset. When you set up your tablet after this reset you'll have an opportunity to restore any data that was backed up to your google account."
Click to expand...
Click to collapse
thats the same message i got also after turning on the display I also have a keyboard and took it off to put the tablet on the fridge and put it back on the keyboard afterwards and it still worked fine until i turned the screen off and tried to turn it on later
jlcutler said:
This just happened to me. Here is the sequence of events that led up to it.
1. Fully charged and unplugged it. ( I did pull the unit off the keyboard as it was propped up but this shouldn't affect the storage right? )
2. It did a random reboot after taking it off the charger.
3. It asked for my password in a "pre-boot" screen
4. The message I get is : "Decryption unsuccessful" "The password you entered is correct but unfortunately your data is corrupt.
"To resume using your tablet you need to perform a factory reset. When you set up your tablet after this reset you'll have an opportunity to restore any data that was backed up to your google account."
Click to expand...
Click to collapse
yup, this has happened to mine several times but except for one time, i just pressed vol dn & power to get to the options screen and rebooted. so i did not have to reset but one time. but mine has not died yet. i also think the magnets might be causing this and some other issues
I've just had the same thing this morning and I'm in the process of a truly awful conversation with Google support during which I had to explain to them what "stuck in a bootloop" meant...
I've had this one since a week after launch, working fine - I assume there weren't any recent updates that changed any of the memory partitions?
You guys could always try to unlock your bootloader from fastboot and reflash the stock images.
PriyanPhoenix said:
I've just had the same thing this morning and I'm in the process of a truly awful conversation with Google support during which I had to explain to them what "stuck in a bootloop" meant...
I've had this one since a week after launch, working fine - I assume there weren't any recent updates that changed any of the memory partitions?
Click to expand...
Click to collapse
God I hate dealing with non-technical customer service reps, the devs from Dolphin Browser didn't understand portrait vs landscape, I ended up stopping the conversation because I'd rather beat my head against the wall. Same thing goes for Wizards of the Coast and Magic 2015, I asked then why all my data on my tablet didn't sync to the cloud since it was using Google Play games so I could continue the game on my phone and they just kept on saying "It's not meant for phones so that's why it doesn't work" even though it actually worked perfectly on my phone, they also kept calling me by the wrong name, even after multiple corrections.
Sent from my Pixel C using Tapatalk
I have the EXACT same problem on my 32GB píxel c, i am returning it.
Enviado desde mi XT1039 mediante Tapatalk
Same here
Okay, same boat here. Just received my Pixel C two days ago. Pretty neat to use, put always fully charged. Several unresponsive(freeze) occurs to me, especially when I tried Lens Blur feature in Google Camera. But overall I'm pretty satisifed with the experience and design.
Today I got onboard of a airplane. I guess it's after X ray security check machine... then I opened the tablet it prompted me with password. And the following with sort of "your drive is corrupt but we can restore it from Google backup" things. I clicked next (it's fully charged by now) and the looping restart begins. I can't even turn it off until I find the vol down + power trick to enter the recovery menu. But right now it's completely unusable. I think I'll request a order returning when I'm back...
I've just had the same experience on a third Pixel C, this time after about a week. I think this time I'm just going to demand a refund. They've failed to send me a single working device and don't seem to have any fix for this. I can't go through a continual process of RMA-ing and losing any data not yet backed up indefinitely.
What country are you guys from for those of you having issues? I'm in the USA and bought mine as soon as it launched and haven't had a single issue with it, meanwhile I see a bunch of people are having random QA issues which seems to be pretty odd.
Sent from my Nexus 6 using Tapatalk
I'm in the UK. I bought at launch so I'm well outside the 30-day window, but I've gone through three different units. On the plus side, they agreed to a refund with no hassle at all so I assume this isn't an isolated issue. Thanks to Amazon Prime I'm already setting up a Sony Xperia Z4 and, whilst I'd still prefer stock Android and the Pixel C 's aspect ratio, I'm actually pretty impressed with it so far...
Same thing here.
Did your replacement function?
Some premium tablet
Screw Google for not sending a USB C to USB A 3.0 cable so I could at least attempt a ADB factory flash.
God I hate dealing with non-technical customer service reps,
Click to expand...
Click to collapse
You know "boot loop" isn't a technical term right??
My Note4 has developed a weird issue where it will be on just fine for like 5-10 hours then all of a sudden it will show the Verizon logo full-screen with nothing else and be unusable. I need to pull the battery to fix it.
Q1: What the heck would cause this? Only changes Ive made were using the new GearVR and sideloadVR, not sure if related. But seemed to have happened several days after installing them, not at the same time.
- I use synapse and have tried undervolting thinking it might be overheating. No change. Put it back to normal.
- Happens with both the standard battery and Zero Lemon battery.
- Happens when in or out of power save mode (black and white screen etc)
Q2: If I factory reset, will I lose root? Note: A software update has been downloaded and its been asking me every day to install it and I always decline.
Both yesterday and today, in the morning my phone while on the charger still randomly reset twice. I'm guessing it is due to an app update, although the phone has been a little weird since the last T-mobile update. Is there an app that can tell me what is causing this problem? Since it only happens occasionally and when the phone isn't being used, putting it in Safe Mode won't work, and I can't delete million apps, especially important ones.
Hello all,
I need some serious help here. I was using my Samsung Galaxy S20 Ultra when DURING USAGE, the phone decided to reboot. It is rare but it happens. But the problem escalated when it refused to reboot again. It has constantly been in a boot loop ever since. It did fully RESTART TWICE in the middle but before I could unlock the phone it slipped back into its boot loop coma.
Everything on the phone is stock, updated to the latest versions for all I know. No combination of power and volume buttons help. What it only does it switch it from boot loops to a static boot screen.
ANY HELP OR EXPLAINATION WILL BE APPRECIATED !!
Sincerely,
SRV
These phones should never spontaneously reboot. That indicates a potentially severe problem; always take any sign of system instability seriously. Often it's the only warning you get before a boot loop.
You need to get into safe mode or the boot menu to do a factory reset. Make sure you're using the proper sequence and timing matters. Try holding the power button down for at least 30 seconds.
Poorly written apps can do this. It may be the firmware was corrupted (possibly a single event upset) or a hardware failure. Play with it...
@blackhawk
I have tried:
power button hold for long
power button + volume up
power button + volume down
all three
The current situation is:
It is stuck on boot screen for 5~10 random minutes then starts cycling again. What do you figure could be the reason for it to have fully restarted (then gone back bootlooping) when the situation was fresh ?
Do you think i should let it drain out ? (How long would it take lol)
Perhaps try unplugging the battery/ removing SD card WHILE its still booting ?
Don't know, not normal behavior. Maybe someone else has seen this before.
Try pulling the SD card* and sim card.
Try hooking up to the PC. Let it drain out ie hard reboot. Anything to break the cycle.
*it's backed up, right?
My S20U had the exact same issue last year. I had to send it in for repair and they replaced the motherboard.
planeinmountain said:
My S20U had the exact same issue last year. I had to send it in for repair and they replaced the motherboard.
Click to expand...
Click to collapse
You weren't able to get it in recovery at all right ? and how much did it end up costing you ?
blackhawk said:
Don't know, not normal behavior. Maybe someone else has seen this before.
Try pulling the SD card* and sim card.
Try hooking up to the PC. Let it drain out ie hard reboot. Anything to break the cycle.
*it's backed up, right?
Click to expand...
Click to collapse
I let it drain to zero, it calmly powers off and saves a tiny amount of battery just to display the 0% battery image when I try to turn it on. The the moment I plug it back in, bootloop.
Though I'm sure you mean let it drain dead zero, I've left it to do that.
panzer27 said:
I let it drain to zero, it calmly powers off and saves a tiny amount of battery just to display the 0% battery image when I try to turn it on. The the moment I plug it back in, bootloop.
Though I'm sure you mean let it drain dead zero, I've left it to do that.
Click to expand...
Click to collapse
The last really good flagship Samsung made was the N10+ snap. Everything that followed has had hardware issues, mostly the displays. The only way you know there are issues though is when people post about them on forums. Who knows what the actual number is? Only Samsung and those wimps won't owe up to it.
It may still be a firmware issue and not hardware.
If it is hardware it may be an issue with a ribbon cable or other module, and not the mobo. A Samsung Experience center at Best buy may be able to help and reflash it. Don't give up quit yet.
Yes drain it until it won't try to boot and the battery auto shuts down. You probably saw a "robound" effect where the battery recovered enough to have enough power to boot.
If it needs a mobo consider the repair price vs the price of a new (still available) or used N975U1/N975U. In my opinion this is a better Note in spite of some of the missing features. Just a rock solid work horse that's form factor is superb, well balanced with perhaps the best display in terms of color/gamma accuracy and calibration. I have two of them... no regrets. They are a joy to use.
The 3 yo one has over 8k hours on it and it looks, feels and runs like new, zero display degradation.
Only repair has been a battery replacement. A new one will be loaded with Android 10 which I prefer over 11/12. Pie though is still my favorite and the oldest one is still running on Pie.
I'm not pleased with Samsung's flagships since the N10+... Samsung just keeps dropping balls and lives on hype rather than solid performance.
Sammy, you suck elephant balls bad now.
My wife and I also experienced a similar issue with our S20 Ultra 5G. Except ours was an update that literally just killed the device. We tried every combination of buttons to get into recovery or bootloader mode with no success. Ultimately we had to send the device to a Samsung service center to have the LCD, battery and motherboard switched out.
blackhawk said:
The last really good flagship Samsung made was the N10+ snap. Everything that followed has had hardware issues, mostly the displays. The only way you know there are issues though is when people post about them on forums. Who knows what the actual number is? Only Samsung and those wimps won't owe up to it.
It may still be a firmware issue and not hardware.
If it is hardware it may be an issue with a ribbon cable or other module, and not the mobo. A Samsung Experience center at Best buy may be able to help and reflash it. Don't give up quit yet.
Yes drain it until it won't try to boot and the battery auto shuts down. You probably saw a "robound" effect where the battery recovered enough to have enough power to boot.
If it needs a mobo consider the repair price vs the price of a new (still available) or used N975U1/N975U. In my opinion this is a better Note in spite of some of the missing features. Just a rock solid work horse that's form factor is superb, well balanced with perhaps the best display in terms of color/gamma accuracy and calibration. I have two of them... no regrets. They are a joy to use.
The 3 yo one has over 8k hours on it and it looks, feels and runs like new, zero display degradation.
Only repair has been a battery replacement. A new one will be loaded with Android 10 which I prefer over 11/12. Pie though is still my favorite and the oldest one is still running on Pie.
I'm not pleased with Samsung's flagships since the N10+... Samsung just keeps dropping balls and lives on hype rather than solid performance.
Sammy, you suck elephant balls bad now.
Click to expand...
Click to collapse
Thanks for your inputs...
I let the battery drain condiderably, then with that low battery, I just pressed power button. Voila, recovery screen.
I have wiped the cache partition and am waiting for it to reboot (which the command line the screen says)
Does it say "rebooting..." for a long time or am I screwed further ?
panzer27 said:
Thanks for your inputs...
I let the battery drain condiderably, then with that low battery, I just pressed power button. Voila, recovery screen.
I have wiped the cache partition and am waiting for it to reboot (which the command line the screen says)
Does it say "rebooting..." for a long time or am I screwed further ?
Click to expand...
Click to collapse
Go for safe mode at the most. Normal mode will likely loop you again.
If you don't need to recover data> factory reset most rikky tik. Clearing the cache for this won't do squat.
The user data partition is corrupted at the least. If a factory reset clears the boot loop, be careful what you reload... or you'll be doing this again.
This is assuming the loop was caused by a 3rd party app or malware. A definite possibility.
Remember if you encrypted the SD card a factory reset will wipe that key and your access.
blackhawk said:
Go for safe mode at the most. Normal mode will likely loop you again.
If you don't need to recover data> factory reset most rikky tik. Clearing the cache for this won't do squat.
The user data partition is corrupted at the least. If a factory reset clears the boot loop, be careful what you reload... or you'll be doing this again.
This is assuming the loop was caused by a 3rd party app or malware. A definite possibility.
Remember if you encrypted the SD card a factory reset will wipe that key and your access.
Click to expand...
Click to collapse
I am dead sure it is Malware.
I got it up and running and looping a few times now. The battery draining probably cleared some flags that prevented a normal reboot.
Phone has survived a minute in safe mode. Let's see
blackhawk said:
Go for safe mode at the most. Normal mode will likely loop you again.
If you don't need to recover data> factory reset most rikky tik. Clearing the cache for this won't do squat.
The user data partition is corrupted at the least. If a factory reset clears the boot loop, be careful what you reload... or you'll be doing this again.
This is assuming the loop was caused by a 3rd party app or malware. A definite possibility.
Remember if you encrypted the SD card a factory reset will wipe that key and your access.
Click to expand...
Click to collapse
Current status is that it stays on for 2~5 minutes.
There is a software update should I go for it ?
panzer27 said:
Current status is that it stays on for 2~5 minutes.
There is a software update should I go for it ?
Click to expand...
Click to collapse
Negative. Keep the playing field level. An update now could brick it.
Factory reset if you can. No known rootkits can worm out of the user data partition on Android 9 or higher. A factory reset will purge it if that's the cause. Kill the intruder.
Delete your Samsung and especially Google accounts in settings first if possible. Reset your Google account password after you factory reset, write it down. If it was malware try to figure out when, where and how it breached the device. Any odd behavior that signaled the event.
blackhawk said:
Negative. Keep the playing field level. An update now could brick it.
Factory reset if you can. No known rootkits can worm out of the user data partition on Android 9 or higher. A factory reset will purge it if that's the cause. Kill the intruder.
Delete your Samsung and especially Google accounts in settings first if possible. Reset your Google account password after you factory reset, write it down. If it was malware try to figure out when, where and how it breached the device. Any odd behavior that signaled the event.
Click to expand...
Click to collapse
I should have read this on time, I wen for the software update Wont go beyond 25%. Boot looping
blackhawk said:
Negative. Keep the playing field level. An update now could brick it.
Factory reset if you can. No known rootkits can worm out of the user data partition on Android 9 or higher. A factory reset will purge it if that's the cause. Kill the intruder.
Delete your Samsung and especially Google accounts in settings first if possible. Reset your Google account password after you factory reset, write it down. If it was malware try to figure out when, where and how it breached the device. Any odd behavior that signaled the event.
Click to expand...
Click to collapse
I am in download mode. Can I flash a stock firmware using odin ? and will that Still keep my phone legit ?
panzer27 said:
I should have read this on time, I wen for the software update Wont go beyond 25%. Boot looping
Click to expand...
Click to collapse
Did it completely download the update?
If not try to get into boot menu again. Factory reset. Otherwise it will need to be reflashed.
panzer27 said:
I am in download mode. Can I flash a stock firmware using odin ? and will that Still keep my phone legit ?
Click to expand...
Click to collapse
As long as you flash the correct stock rom. Make sure it's the right one!!!
Not sure about the best method. Make sure you find out what is the best shot as you could hard brick the phone if you goof this up.
Throw it to Samsung if in doubt.
I've been fortunate and never had to do this. One reason I leave the Android firmware alone, avoiding even upgrades and updates. Android firmware flashing is the most complicated I've seen. A PC bios or a Canon Pro shooter, router are a snap to do by comparison.
blackhawk said:
Did it completely download the update?
If not try to get into boot menu again. Factory reset. Otherwise it will need to be reflashed.
Click to expand...
Click to collapse
It downloaded everything, rebooted and started installing the update. Reached 30% then slipped to bootlooping vigorously. To get to the boot menu I would have to discharge the phone again. Because of the installation process, do you think draining the battery could brick the phone ? I could leave it to discharge if this is not a risk and 30% will be rolled back.
Do advise.
panzer27 said:
It downloaded everything, rebooted and started installing the update. Reached 30% then slipped to bootlooping vigorously. To get to the boot menu I would have to discharge the phone again. Because of the installation process, do you think draining the battery could brick the phone ? I could leave it to discharge if this is not a risk and 30% will be rolled back.
Do advise.
Click to expand...
Click to collapse
Update or reflashing the stock rom?
You should never interrupt when it's flashing. Yeah it could definitely at least soft brick it.