Hello, recently I started reading comics and found my old tab lying around so ill give it a go
First thing first it wont boot becaue it had no charge obviously (been there for like some years), then I tried to plug the charger but to no avail
I cleaned the contacts of the charger with a dry brush and start charging which then my tab starts charging!
when I booted, I think it was CM 12 (or 13? the one with andy I believe) and everything is force stopping.
I then tried to go to recovery mode and wipe data, but when i rebooted it it just stuck with the splash screen (the one before bootanimation)
I turned the tab off and tried to boot to download/recovery mode but it would just boot me right to the splash screen again, which mean i cant go to TWRP or ODIN.
And it doesn't always want to turn on, sometimes it just stuck there with black screen (not turned on) even if i press power/combo button, sometimes it pop up to the splash screen. what i notice is that i should wait for the charging indicator to show up before i can try to boot again (i got enough juice now, 56% the last time it turned on)
also one thing i remember is something about F2FS but im not sure what that is, but that might be a clue to my situation so ill just write this down here
Hi
Same here with P5110 and Slim7. I can't start it anymore....
I didn't use it for some time and then i charged it to 100% and it started but everything seemed to lag. Then i turned it off and wanted to look for another rom or a newer build. But i can't start it anymore. when i plug in the charger i can see the charging screen but beside of that i can do nothing. It has no effect when i push the on/off button or anything else...and it has to be at nearly 100%...
Related
Hello,
I’ve got a One S (S4 version) that’s driving me crazy. Can you help me please?
I bought this phone second hand – hoping that I could fix it up and give it to my mum for her birthday. It looks immaculate, but it was sold because the previous owner couldn’t get it out of a boot loop.
When I received the phone, the first thing I did was to hook it up to the charger. As soon as the charger was connected, the charging LED came on, but then after about 5 seconds (without pressing the power button), the device turned its self on and begin rebooting at the “Quietly Brilliant” screen. It wasn’t the usual “Quietly Brilliant” screen though… There was a progress bar in the top right hand corner, indicating that it was trying to flash something. The progress bar went from 0-100% twice, then after a pause of about 20 seconds – it rebooted again. This process would repeat endlessly
After a lot of messing around, I managed to get into the bootloader. The status was “Tampered – Relocked”. At this point, I downloaded and flash the latest RUU (2.31). However, even though the RUU flashed successfully, it still boot loops. The only difference is that the “Quietly Brilliant” screen no longer has the progress bar in the top right corner (it’s just the normal boot screen now).
After this, I unlocked the bootloader via HTCDev and flashed CWM recovery. The flash was successful , but trying to access recovery also fails. It just sits on a screen with the “for development purposes only” warning for a few seconds, then reboots and follows the same boot loop sequence as before.
Does anyone know whether I’m wasting my time on the phone? At this point I’m very worried about flashing things, because I never know how much juice is left in the battery. If I hook up the charger, the charging LED does come on, but only for a matter of seconds. After 5-10 seconds, the charge LED goes out and the device automatically fires up into a boot loop. It’s impossible to power down the device when it’s connected to the charger. It will turn its self back on again! The best I can do is to leave the phone sat in the bootloader, but there is no indication that it’s charging (no LED).
:crying:
I've just read over my last message and I think the clue is in the way this thing turns on by its self when connected to power. I bet some water has got into the phone and caused a mess inside. I think it might be time to get the screwdrivers out.
Hi all,
I have been given a tablet to try and recover by a friend who seems to have semi-bricked it. I heard that he ticked the wrong buttons in Odin and then it all went downhill from there...
See the attachment: This graphical screen is displayed all the time. I cant actually shut the tablet down, even if I boot into CWM and choose shutdown from there. It will turn the entire screen of for 2 seconds and then then go into the attached funky graphics screen and stay there.
There is no battery charge at the moment so the odd time I do get it to boot properly, it shuts down straight away. Im leaving it chargin as we speak to rule that out.
I've tried flashing a stock ROM and get an error7. I have wiped and reset the tablet and wiped both caches too.
My next move is to (after its charged) download and apply a ROM from the samsung website and see if I can return it to normal.
I really want to know why I cant shut it off and what's the deal with the weird graphics screen? Any step by step instruction on how to reset properly and what I should do would be SUPERB.
Hi!
Very weird situation. Before that everything was stock and OK (no custom ROM or anything).
- If the phone is unplugged, nothing works at all (key combinations,...)
- The battery is charged, at some point, when totally off, it showed the battery charging, 60% at least. But have not been able to go back into this mode.
- When connected, it starts booting, but keeps rebooting very fast (1-2 s after Samsung splash screen).
- Unable to boot into Recovery mode (UP+HOME+PWR, for wiping cache,...). Just does nothing, howerver long I wait
- Unable to boot "directly" into Maintenance Mode (all buttons), more on that later
- Can boot into Download (ODIN) mode (DOWN+HOME+PWR) very easily. I was able to flash stock ROM, but nothing changed.
- From ODIN mode I can boot into Maintenance mode (all buttons). I can navigate the menu, but any choice, even Factory Reset, gets me directly back to the reboot loop...
As I can not even turn it off, I cannot drain the battery (at least not quick). As soon as I disconnect the cable it goes dark (whatever mode I am in).
Anything I missed that I could try before throwing the phone?
Thanks!
SOLVED
Just to leave a trace on what happened:
- Left the phone alone, un plugged, for 8-10 hours.
- Just to see, tried to reboot it normally,
- It booted on a blue/cyan display, with "installing updates".
- At one point before I had that screen, but after 10 seconds it rebooted into the loop cycle. And after playing with the recovery reboots, I had never managed to get this special boot again.
- This time it stayed on "installing updates" for 1-2 mn, then rebooted, and Voilà!!!
So apart from my magic touch of doing nothing, don't really know what happened... So much for the recovery recipe!
A fairly similar thing happened to my girlfriend's g920v yesterday. We haven't been that lucky that it got fixed.
The situation is slightly different though, it boots for about 3 seconds, makes the low battery sound, battery indicator says 0%, then shuts back down.
Tried flashing stock in odin a few times, a few factory resets, nothing.
It seems like an OTA update failed and now the stupid locked bootloader won't let me or the or OS fix it.
Sorry you were not as lucky... But as you said the problem seems a little bit different, as I never had an empty battery warning. I agree though that it looks as a bad update stuck somewhere.
guimou_qc said:
Sorry you were not as lucky... But as you said the problem seems a little bit different, as I never had an empty battery warning. I agree though that it looks as a bad update stuck somewhere.
Click to expand...
Click to collapse
There's got to be some connection of some sort, yours is the 4th post I've seen here or on Reddit this month about bootloops probably related to updates
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
Ok, here's the deal....
My S7 isn't my main phone, switched to a S10 some mths ago, been using it as a secondary phone to stream music to a bluetooth speaker, anyway i let it discharge naturally last time i used it & i noticed the blue led had stayed on, tried turning it on & it wouldn't come on, so proceeded to try & charge it - upon doing so the standard charging screen comes up, but it never gets to the % charge bit whereupon you can turn the phone on, also after a while it displays a download screen, saying don't turn off target, even if you try & boot the phone now it doesn't get very far, just the initial samsung loader screen! Anyone any ideas?
Anyone at all?
ShinySY said:
Anyone at all?
Click to expand...
Click to collapse
If you don't care about keeping data.
Charge phone, boot into recovery, factory reset.
If you want to keep data.
Charge phone, boot into download, flash firmware with Odin use Home_csc. Let phone reboot.