So recently, my phone has started acting up. Sometimes, the phone would overheat, lag, and freeze. Usually, a quick boot into the bootloader via physical buttons would fix the problem.
However, as I tried to boot into the bootloader, my phone just stayed at a black screen throughout. I found that odd, and connected to my laptop running Ubuntu, opened up a Terminal window, and tried adb devices. Oddly, the device wasn't there. (fastboot showed nothing, as well) However, a bunch of windows labeling different volumes opened as I plugged into the phone. Normally, the phone would only load up the SD Card and External Storage. Charging it doesn't show its amber light.
I currently have a Verizon HTC One (M8) bootloader unlocked and S-OFF'd.
Any help would be appreciated.
EDIT: The battery died and phone started to boot up normally. Still confused on why it showed up 30+ volumes, though.
Related
Now I'm posting this because my issue isn't like the ones I'm seeing here. I've done absolutely nothing to my device as far as tweaking goes, the device isn't even rooted. Randomly on a drive when I pulled up my map for directions, my phone's audio began skipping, the phone froze, & then crashed. Now I can't get past boot.
When I try to get into recovery mode via Fastboot, it just goes to a black screen.
I've allowed the device to die fully & then charge, but no dice. The status of the battery is showing as OK. My PC will not recognize the device in Fastboot either.
Any advice?
Used Windroid Universal Android Toolkit to unlock bootloader and flash twrp. All went fine.
Then I tried to gain root by flashing supersu, also with the same toolkit.
Then I got a android figure with a warning sign.
Can't remember exactly what happened then, but after that I can't power on, screen stays black whatever I do.
Charging I going fine though, charging led is green.
My desktop recognizes when the tablet is connected with usb, but I can't login with the toolkit.
Any idea what I could do or is the diagnosis: bircked?
Can you get into the bootloder? If so you are not bricked you can reflash the firmware
No, I'm not able to get into the bootloader, screen stays black, whatever I try.
Some change now.
While charging the battery, don't know how it became empty, the display shows a charging battery...
Wait till the battery is full, and then try some things again.
So happy! My problem is solved.
Here is what I did what resulted in my problem solving.
First I opened the back panel to see if the battery was all right.
After that my battery was empty, and I started loading my battery with the Nvidia adapter.
The screen showed a loading battery figure. After that I was able to boot into android as well as in the bootloader.
Back story:
My beloved tablet ran down on power as I was using it today (note to self - change warning percentage from 5% to something like 15%)! I tried shutting it down, but it died before the shutdown was finished. I put it on the charger and let it charge until about 65%, took it off the charger, powered it up. It started coming up, got to the the PIN screen, then nothing. Couldn't do anything, touch screen wasn't doing acknowledging anything. I think things got corrupted as it was powering off...
Powered it down, waited a few minutes, then powered back up. Took about 10 minutes to start after I entered my PIN, and it was behaving strangely:
1. WiFi said it was off, but I was getting e-mails (sent one to myself from another device to confirm it)
2. Settings would start, but got nothing, just a white screen.
3. Most apps would start but really slow, then suddenly shut down
4. Tried booting into TWRP 3.1.1 - got the initial screen, there it sat for the next 20 minutes before I rebooted.
5. I can get into bootloader, but fastboot from my Linux laptop doesn't work - can't find any devices when the tablet is plugged in.
6. "adb devices -l " shows the tablet is connected, but get no prompt on the tablet screen about adb starting
6. "adb reboot bootloader" and "adb reboot recovery" from my laptop just sits there - nothing happens on the tablet.
I'm on Lineage OS 14.1 (latest weekly for the SMP-900) and TWRP 3.1.1 on the tablet, and Fedora 25 on the laptop. Rebooting is iffy - sometimes it starts, sometimes it doesn't and just sits on the Lineage boot animation. I also have my 128Gb SD card set up as part of the internal memory (i.e., can't pull it and stick it into another device) Every reboot takes longer, and I fear the next power on will have me just sitting there, staring at the Lineage boot screen forever.
I have Nandroids from TWRP, but doesn't do me much good if I can't get into TWRP to use them. I have TWRP image and tar files, but jodin (a Java based Odin type of program that works in Linux) doesn't get a response from the tablet and therefore won't flash.
If I could get the tablet back to the point where I can get TWRP working again, I can reload from the TWRP backup. I also don't have a Windows computer available at all, but I do have Windows XP in a VMware virtual machine as an absolute last resort on my laptop.
Does anyone have any ideas or pointers to get me running again? Right now, it's powered off and charging...
Thanks for any help....
Patience, patience, patience ...
I'm answering this myself - just so there is an answer.
If you ever run into this problem, read the heading above! I got the tablet to boot up finally by pulling the 128 Gb SD card first, then powering up the tablet. I plugged in the SD card back in and it started slowing down, but checking under Storage, it indicated it was checking the encrypted card. I set it aside, checked it 2 hours later - still checking the card. Plugged it into the charger and went to bed, got up this morning and it was shut off. Powered it up, it booted up, this time around it recognized the encrypted card as part of internal storage and Life is good again.
My assumption is that when the tablet died, the card was marked dirty (I.e., not shut down properly.) When I tried TWRP, it noticed that the card was flagged dirty and started checking it before it would give me the home screen - same thing with Lineage when it tried to boot. And yes, I changed the battery power warning to 15%.
Thanks for your update on that problem.
So I was just doing some hardware tuning using Kernel Adiutor to save battery, restarted, and it booted up (I was using apply on boot obviously) and was running very slowly. I tried to change the settings, but the phone froze. "No problem", I thought as I rebooted via adb command. It reboots and I cancel the apply on boot, and it freezes after five minutes. I reboot again, freezes again. Reboot, freeze. This happens about 6 or 7 times , each time freezing sooner than the last. Then, it freezes one last time, then the screen goes black. I try reboot and reboot to bootloader/recovery with hardware buttons with no success. So I assume it powered off, but I should check adb first. I ran the devices command and it showed up as active. I ran all basic reboot commands and those just sit there and never complete (I sat here for 20 minutes waiting for it).
I also thought it may be stuck in Android with no display, which I've had happen before on another S7, but it doesn't respond to touch or hardware buttons, and doesn't show up in file explorer (I have screen lock off so it shows up even when off normally).
So then I thought it may be stuck in bootloader with no display. I open up Odin and it recognizes the device, but won't flash anything at all.
Also, this device has never been dropped to my knowledge, and has no cracks, so I doubt it's hardware damage.
I've tried everything I can think of, and Google yielded no results thus far
TL;DR
Messed up with Kernel Adiutor and the screen went black after multiple reboots and freezes
Tried hardware reboots and adb reboots
The device shows up in adb and Odin, but not in file explorer (no screen lock, usually shows up even with screen off)
Odin cannot flash anything, so it's not in bootloader
Other Info:
It's obviously a Galaxy S7
It was originally a Sprint phone (G930P)
It now has Unlocked firmware (G930U)
It is also running engboot for root permissions
I have some previous experience with engboot with my other S7 and have had no problems after 2 years rooted
Any help at all is appreciated
Edit:I'm an actual idiot and didn't know about force reboot (power and vol. down for 10 sec.) and that worked :/
Hey everyone, I'll start by saying I'm new to these forums, so go easy...
I've had an S7 (Verizon SM-G930V) for probably 3 years, recently it randomly glitched/locked up (screen had strange color bars through what I was looking at) phone restarted and then was stuck in a boot loop. It's never been wet or dropped hard and is in really good shape. I shut it off and attempted to re-start with the same results... Got a new S20+ so I at least have a device, but I'm determined to get the lost month on the old S7 back since I had a backup from early Feb.
I tried a new battery since that was mentioned, didn't change anything, however in messing with trying to get the phone to boot have discovered a few strange message screens and behavior...
1. Phone will eventually stop responding to key presses, have to pull battery connector, wait, then it will re-boot, but every time the blue 'Recovery Mode...' is displayed. If I touch nothing, it will boot and start 'installing updates' but eventually lock and restart. At one point it made it as far as the Verizon screen, then died.
2. I can get the phone to to into the recovery menu and it will respond to commands. I've tried restart normally, boot to safe mode, and shut down phone normally, all of which result in the same restart and recovery mode message and then the lock during the update.
3. I have successfully made it to the download mode screen a few times, but don't have the knowledge of what needs to be done there and which files I would need to upload to it to make that work. (phone was totally stock rom) It had recently updated to the latest version available from Verizon which I think was 8.0?
4. Now I have found a new error screen which I have not seen before... The little Android guy has X's in his eyes and a large yellow sign with ! in it says 'No Command' and then the phone restarts? It also during that finally responded to being plugged in via USB charging, however normally it shows no signs of charging other than being warm and actually charging the battery (verified with a meter)
5. When the phone is on, it gets warm quite quickly (it's still split open and the tin covers are warm, but not hot)
Hopefully someone can help out. I wouldn't say there's anything too critical on there, but there are some pics I'd really like to have back :crying:
Thanks everyone!
bigblkyj said:
Hey everyone, I'll start by saying I'm new to these forums, so go easy...
I've had an S7 (Verizon SM-G930V) for probably 3 years, recently it randomly glitched/locked up (screen had strange color bars through what I was looking at) phone restarted and then was stuck in a boot loop. It's never been wet or dropped hard and is in really good shape. I shut it off and attempted to re-start with the same results... Got a new S20+ so I at least have a device, but I'm determined to get the lost month on the old S7 back since I had a backup from early Feb.
I tried a new battery since that was mentioned, didn't change anything, however in messing with trying to get the phone to boot have discovered a few strange message screens and behavior...
1. Phone will eventually stop responding to key presses, have to pull battery connector, wait, then it will re-boot, but every time the blue 'Recovery Mode...' is displayed. If I touch nothing, it will boot and start 'installing updates' but eventually lock and restart. At one point it made it as far as the Verizon screen, then died.
2. I can get the phone to to into the recovery menu and it will respond to commands. I've tried restart normally, boot to safe mode, and shut down phone normally, all of which result in the same restart and recovery mode message and then the lock during the update.
3. I have successfully made it to the download mode screen a few times, but don't have the knowledge of what needs to be done there and which files I would need to upload to it to make that work. (phone was totally stock rom) It had recently updated to the latest version available from Verizon which I think was 8.0?
4. Now I have found a new error screen which I have not seen before... The little Android guy has X's in his eyes and a large yellow sign with ! in it says 'No Command' and then the phone restarts? It also during that finally responded to being plugged in via USB charging, however normally it shows no signs of charging other than being warm and actually charging the battery (verified with a meter)
5. When the phone is on, it gets warm quite quickly (it's still split open and the tin covers are warm, but not hot)
Hopefully someone can help out. I wouldn't say there's anything too critical on there, but there are some pics I'd really like to have back :crying:
Thanks everyone!
Click to expand...
Click to collapse
If what you've described is correct, all of the solutions involve flashing the stock firmware which will of course wipe the device.
Were your photos not stored in a folder on the SD card?
There is a chance you can recover the device using Samsung Kies with the emergency recover option but if you've encountered the "no command" screen it's not looking good.
Unfortunately I did have an SD card installed, but I normally kept my camera pics on the phone's memory, since I have had an SD card fail as well and lost everything on there.
So this took an unexpected turn yesterday pretty much right after posting this... I've been messing with the phone, unplugging the battery each time, and have managed to get into different menus which kept making me think that something still had to be working if I could do that. Well, after leaving the No Command message on the screen it magically booted into the Recovery menu with (finally) the option to wipe the cache partition, which I did and rebooted normally. Believe it or not, it booted normally and into the OS like nothing ever happened?!
I instantly plugged it into my PC and ran Smart Switch which started taking a backup! About 25% though the device restarted again and was really warm to the touch on the RF covers inside. Bummer...
So I figured heat was now the issue for some reason... I waited for it to cool and then reinstalled the SD card and figured, if I could get it to boot long enough, the SD card is a quicker transfer and I'd just use ES File Explorer to try and do a photo dump to the SD card and see how far it would get. It actually made it all the way through and gave me enough time to grab some other stuff before getting hot and restarting again.
I believe the overheating is being caused by my opening of the device though... Currently I have the antennas removed and the speaker so that I'm able to quickly access the battery connector (which BTW seems to be the trick here to this working) But inadvertently, without the larger wireless charging coil in place, it relieved the pressure on the motherboard and broke the thermal paste connection between the chipset and the copper heatsink (I didn't tear it down further to check, but I can hear the 'sticking and peeling' when you press down on it).
I think what I'm going to do is apply pressure with a chip clip or something similar (non conductive) and see if I can grab a backup again before it restarts. After the cache wipe the phone seems to understand that it's plugged in and charging now which is a new thing as well...
Sorry for the long winded posts, but if this at all helps even one person with the same situation as I have, maybe that'll be worth getting lost in here