So, my friend came down to visit in FL from GA.. Her phone ended up snapping in half, but she found an older one in her car. We have since been trying to fix said phone, but nothing has worked. I've used Odin to try and install an OG firmware (which is nearly impossible to find, might I add) and that didn't work. It only made the bootloop issue worse. I also tried to use Odin to put TWRP on it, which showed signs of hope, but gave no real progress to the issue. The recovery menu doesn't exist. The power + vol up + home button doesn't boot to recovery which is why I figured I'd try a custom one. ADB doesn't work because USB debugging wasn't turned on before the phone got destroyed. Idk what happened to the phone before to cause this, neither does she. We simply found it in her car this way. She's going back tomorrow, but has no GPS to find her way, so I'm in desperate need of help. I've tried almost everything I can think of and this stupid phone still won't boot to recovery. I know if I can get it to recovery, I can fix it. Google hasn't been much help either. Everyone always suggests recovery mode, but I can't get to recovery.
Thanks for any help, guys.
Edit: Model # - SM-S920L
Related
Alright, so I've got an LG E617G from Bell Aliant, a mobile carrier in Canada. I know it's rooted and it's the most up-to-date OS I could possibly get for this phone, stock, but I can't check the OS at the moment, or at least in a way I know of. I went to reset the phone to factory default settings and it gets stuck in this boot loop. I shut down, boot it back up. Now the boot screen sound doesn't finish properly and it just is stuck in a loop.
I tried to do a hard reset/forced recovery mode thing (Volume Down + Power then go to holding Home only when the LED on the bottom of the screen light up) and that didn't work. Same broken sound and stuck loop. Thinking that the charge might have something to do with it (It was at about 7% when I tried to do the initial reset. Stupid, I know, but I was drunk).
I just tried to do the same hard reset/forced recovery mode thing and that didn't work, same boot screen problem. I searched on the forums here as well as online and the only information that I've gotten is that the L5 is the closest well known representation of the LG E617g so I'm hoping you guys can help.
It should also be known, I did give ES File Explorer root access the day prior to the reset in an attempt to change the actual font. That didn't work so I tried 2 different applications that I found information on. iFont and Font Installer. I tried something with Font Installer and it didn't work so I installed iFont (without uninstalling Font Installer) and installed a font there. That didn't seem to work so I just ignored it. Then I noticed that the font had changed but only on Facebook apps. This was why I wanted to do the reset, to get rid of this font nonsense. Now I think I may have just ****ed it all up.
Any help would be greatly appreciated. Ask what you need of me, if you do need anything, and tell me a quick way of possibly finding that information or linking to a tutorial how and I will get back to you ASAP. Thank you for the patience and help guys.
********
I have since solved the problem. I downloaded and installed all drivers again, ran the LG Mobile Support Tool and on the top menu bar I went Customer Support > Recovery and put my IMEI in and hit check. Got my info and another pop up came up. Downloaded the data for my phone (I had to run it in Download mode. I took out battery, held up and down volume while plugging it in the PC, run this recovery mode. I'd fail the recovery mode but then I'd just run the program part again on the computer while keeping it in plugged in.) and installed it. Worked fine after that.
Thanks a lot for this detailed solution!
need4steer said:
Thanks a lot for this detailed solution!
Click to expand...
Click to collapse
Ah, no problem. I spend most of my time looking at forums that talk about my exact problem but never a solution. Just wanted to make sure that if anyone ends up with my problem that my fix worked.
TL;DR The title
Hey XDA,
So about a month or two ago, I decided to check out xdabbeb's VS982.5 rom because i felt like a bit of fresh air after all the lollipop roms was in order. So I grabbed his bumped bootstack+recovery, and flashed over to the rom.
What I didn't anticipate(and what I really shoule have) was the issues I would have getting back over to a lollipop rom because of the compatibility problems between loki'd and bumped roms and recoveries.
This is where my memory gets fuzzy because this was so long ago, and I apologize if that causes issues with fixing my problem. I do remember trying several different recoveries and bootstacks and none of them would flash because of the bumped recovery. Eventually I found a way to get back to my backup (The January 11th build of BlissPop). However, I still could not flash roms because of the bumped recovery I could not get off of. I tried several different recoveries, and several different methods of flashing them.
Eventually I downloaded flashify off the play store and downloaded the a recovery from there and flashed it from there, which to my recollection broke both my download mode and my recovery. The rom still works, but I can't access recovery or download mode to flash any new roms or do anything besides what is in the rom.
I would appreciate any suggestions anybody has for me, and am willing to totally revert to stock to fix this.
Much thanks!
EDIT: I was using/flashing TWRP builds for all of this in case it was unclear
check if you can get download mode using the mae way (vol up + power) but with usb cable pluged in, plug the usb cabe, presse the combo (up+pwr) and keep pressing until it reboots into downloadmode *always with usb plugged.
If you genuinely can't access recovery or download mode, you can enable usb debugging, adb shell, then dd write aboot, boot and laf to ensure the restoration of download mode. Might want to also write twrp recovery at that time so you have a bailout plan.
rafaelsartori said:
check if you can get download mode using the mae way (vol up + power) but with usb cable pluged in, plug the usb cabe, presse the combo (up+pwr) and keep pressing until it reboots into downloadmode *always with usb plugged.
Click to expand...
Click to collapse
Ah, trying this got me into DL mode safely. Thanks a ton, I'll make my way back to stock now.
LtZKilla said:
Ah, trying this got me into DL mode safely. Thanks a ton, I'll make my way back to stock now.
Click to expand...
Click to collapse
good to be usefull, we are here to help each other. thanks buton make that be more cool.
In my case I couldn't get into download mode.
This happened after flashing rpm, tz, boot and recovery partitions.
The screen doesn't show any logo and seems to be rebooting in a loop.
What can I do ?
Have you tried pressing volume down+ power an as soon as LG logo appears let both buttons off and press volumw down+volume up
Sometimes it works for goung into recovert
If asks for hard reset press YES YES YES and here you go
Hope it helps
Sadly my phone is not showing the logo, or anything on screen.
I can see that the screen is On because it has a weak glow, but it loops as if it was failing to boot the device.
When plugged to a macbook, I get this msg in dmesg:
hidd[65]: MultitouchHID: device bootloaded
kernel[0]: USBMSC Identifier (non-unique): 1234567890ABCDEF 0x5c6 0x9006 0x0, 2
kernel[0]: AppleUSBMultitouchDriver::message - kIOUSBMessagePortHasBeenReset.
kernel[0]: AppleUSBMultitouchDriver::checkStatus - received Status Packet, Payload 2: device was reinitialized
That repeats with the loop I mentioned previously.
This started happening after I I used 'fastboot' to flash partitions. I have tried many combinations to reset it, but none work, the screen never shows logos or error msgs...... that is really really disappointing about the device....
Has anybody found a fix for this? I'm in the same boat now, flashed CM12, went to update my outdated TWRP recovery and now its just a blank screen when I boot into recov, the ROM works fine. I'm afraid to do the aboot method because it seems like a lot of people are bricking.
At least I'm lucky I'm on a somewhat stable ROM at the moment.
I have a GALAXY S5 ive never used custom roms or installed them, for phones atleast. I tried to install one today, and for some reason my 3ds is like BRICKED before i even got to install it. When you turn it on it says "you meed to download this " press y, or b to shut down. After pressing y I ended up at a screen that does nothing. picture of green android, and non moving text.
anyone know amy quick fixes, and suggetions forr the cfw?
fatedblizzard said:
I have a GALAXY S5 ive never used custom roms or installed them, for phones atleast. I tried to install one today, and for some reason my 3ds is like BRICKED before i even got to install it. When you turn it on it says "you meed to download this " press y, or b to shut down. After pressing y I ended up at a screen that does nothing. picture of green android, and non moving text.
anyone know amy quick fixes, and suggetions forr the cfw?
Click to expand...
Click to collapse
Same exact sht been happening to me today, id suggest using odin, as well as rooting it, I also tried to flash bootloader with a recovery thing, it worked but didnt fix the issue. The fked screen is a recovery screen not a bootloader i guess. Im still working on fixing mine. Going to see if flashing a rom will get rid of it. good luck
Try flashing stock ROM in ODIN, followed by clearing cache in recovery mode (volume up+home+power key).
If that doesn't help, a factory reset/wipe data may be necessary which can also be done in recovery mode.
If you don't understand what I'm going on about, I'd suggest to read up before continuing
Ok so before I started writing this I had only one problem now I'm worried my problem has gone from bad to worse.
I updated my 6T to 10.3.2 from the latest Beta after the process it prompted for a restart, upon restarting it got stuck in the boot animation. I tried going into Recovery and Download mode unsuccessfully so I went through the forums a bit and saw that someone who had the same problem successfully entered Recovery mode by pressing VOLUME UP+DOWN+POWER buttons simultaneously, I tried to do the same and my phone turned off and now it doesn't turn on! :crying:
Has anyone experienced this or know how to fix this? Any help will be much appreciated. Tia!
theDUD3 said:
Recovery mode by pressing VOLUME UP+DOWN+POWER buttons simultaneously, I tried to do the same and my phone turned off and now it doesn't turn on!
Click to expand...
Click to collapse
These should be clarified:
Volume Up + Power while turning on will boot to fastboot.
Volume Down + Power while turn on will boot to recovery.
Holding Volume Up + Power should force the phone to turn off.
Volume Up + Volume Down should put your phone in Download mode for the MSM Tool.
Turn the phone off, let it sit. Then try turn it back on. Any response?
try to shutdown phone ...hold vol+ and power button for like 15 sec and restart your phone if this didnt work then u can try MSM tool
Thanks guys, got it working using MSM Tool!
regarding oneplus 6 got stuck on logo screen and recovery mode not working
was just going through some random stuff on my phone and suddenly my device automatically restarted and not it is stuck on logo screen. i and when i tried to open recovery mode, nope its is just not working either. i even tried the fastboot menu to open recovery settings but still no progress help me here...its urgent going though lockdown in country so no service either cant communicate with the fam also. HELP...!!!!
frankynehemimah said:
was just going through some random stuff on my phone and suddenly my device automatically restarted and not it is stuck on logo screen. i and when i tried to open recovery mode, nope its is just not working either. i even tried the fastboot menu to open recovery settings but still no progress help me here...its urgent going though lockdown in country so no service either cant communicate with the fam also. HELP...!!!!
Click to expand...
Click to collapse
You are likely going to lose your data. Know that going in if its not already backed up.
If you have the fastboot menu you can use the fastboot roms.
Or my least favorite option or what I would try last, MSM Tool (Tmobile 6Ts use a different tool).
IMPORTANT if you want to try and recover and data off your phone first, go to fastboot, and try and "boot" the TWRP img (not the installed one, one from your PC using the fastboot command). If that works you might be able to recover data. If that does worm, try dirty flashing the last ROM you were running and see if it boots.
No worries!
frankynehemimah said:
was just going through some random stuff on my phone and suddenly my device automatically restarted and not it is stuck on logo screen. i and when i tried to open recovery mode, nope its is just not working either. i even tried the fastboot menu to open recovery settings but still no progress help me here...its urgent going though lockdown in country so no service either cant communicate with the fam also. HELP...!!!!
Click to expand...
Click to collapse
Hello, I am sorry to hear of you having this issue, I just went through 3 1/2 days (off and on) of recovering my T-Mobile OnePlus 6t which I found a way to get my unlock code within 2 weeks of having it, so I rooted it and put a custom kernel on it, stuck on 9.0 never let me update as I was not familiar with A/B partitioning, yet! The answers I saw to your questions were spot on, I just had a little to add to it and I'm sure I am not alone. Real quick let me list what has gone wrong on the rare occasion it hit the fan with the 6t...
- When I would accidentally and rarely let my battery die it seemed like it took forever to get it to reboot, I mean it sat on my desk of DOA devices for 2 weeks!
- It often seems like the buttons do not always respond properly and never have when I needed them to. Been through this before, I've bricked and unbricked and flashed and re-flashed and wiped all weekend and I like Android 10 and all but seems everything is different for every build, and everything seems to have to go in the right order with the exact right file or you wind up in a jam, period..
- That said, the previous person that answered your question has likely encountered similar, I've heard of right down to the buttons not physically working, but I have been a Smart Device Master III Technician for over 5 years, i know my buttons were not broken.
- Most likely culprit that I just handled and worked, i did have to use the MSM tool, several times - and re-unlock the BL, several times I would not even get the chance to get to fastboot, just a screen saying Build and Hardware not a match"" in yellow letters and it just bootlooped. No fastboot is no good, but when you said the tool would show some signs of working but then not, I have 2 solutions that I needed on diffrent occcasions.
1 - As mentioned fully try other USB cables, and ports, if you pull the usb-c out of the port and hold <power + vol up + vol down> eventually it will do something, very picky, sometimes gotta move your fingers to different spots on the buttons and also after 15-20sec let go of power and hit and hold it again... after a few seconds before it vibrates stick the cable in connected to your PC and the screen will be black (obv) but the msm tool will pick up on it. I know about the cables because I take good care of my phones and cables and charging ports, however on my final fix today it showed in msm tool it was connected but waiting for device.... Fed up i put the phone down and moved the usb cable a little bit and it picked up on it and did its thing! That part was just the cable, getting into qualcomm mode or w.e. is a bit tricky sometimes.
- Also someone said set it down for a while and come back to it.. THAT WORKS!! Let it fully charge and often just plugging in charger turns it on, bootloop soft brick or however have you, very simiilar to an Apple device and their DFU (don't f up mode cause screen is black..)
I hope that helps you get in touch with your family and friends.. Whatever you do, don't give up bc if you have not got it yet, you will! One other note, there are a few different msm tools available and they look the same some same size, but the one that supposed to work on my phone didn't and one that they say only a fool would attempt to try actually saved me, so if all else fails, use a different msm tool/usb cable and you will get it! I don't think I can post links yet I am on here very rarely, but plan on more! I have received so much help from XDA throughout the years on thousands of phones with just software issues alone, aas well as guides to my own phones. I would be honored to give back as I also have some extensive knowledge on many devices but I am a noob in comparison to many! Stay safe, good luck and please update and let us/ me know how it worked out for you. If i can help further I will, I have every firmware file for the OP6t, recovery, tools, software, this is not new to me but I feel your frustration!
Hi!
I used my S7 Edge for a couple of years and now I am afraid it may have died on me. As always, backups of f.e. pictures are not up to date.
During the night, it lay on my Qi charger. When I took it in hand, the screen was extremely dark and stuck in the "loading Lineage" screen. I tried to reboot. It was stuck on the "Samsung Galaxy" screen.
I wanted to boot into recovery and wipe the cache and see if it works again. But I can't boot into recovery mode. No matter if I connect it to a USB cable, the button command does not work.
Switching the device off also isn't possible. The only way to switch it off is disconnecting the battery (I have opened it to do so).
The only thing I can do is booting into download mode (so I know my volume up button works...).
Several times the screen was stuck on the "empty battery" symbol - which did not change no matter how long I had it in the charger. I can't really replicate how I got to the battery screen. I installed another battery just to see if if by some magic this would change something, but nothing changed about my issue. No boot possible and no booting into recovery.
I thought to myself: Well, maybe if I reinstall TWRP I can get into Recovery again. But when I try Odin I get the error message: "there is no PIT partition"
I know you will want additional info:
sadly, I cant' say which version of lineage I had running. I would have to look into my phone - which I can't.
I installed Lineage a couple of years ago, the phone was rooted and had TWRP recovery. I changed my USB port and Audio port several months ago.
But everything was running fine - I did not change or do anything recently. It happened overnight.
Do you have any ideas what I can do? I am brooding for two days now over this issue and I am at the end of the line here.
Did my memory just die on me? Is it an unfixable hardware issue?
Or software-related and potentially salvageable?
thanks in advance for anybody that bothers with my problem.
PinkElf said:
Hi!
I used my S7 Edge for a couple of years and now I am afraid it may have died on me. As always, backups of f.e. pictures are not up to date.
During the night, it lay on my Qi charger. When I took it in hand, the screen was extremely dark and stuck in the "loading Lineage" screen. I tried to reboot. It was stuck on the "Samsung Galaxy" screen.
I wanted to boot into recovery and wipe the cache and see if it works again. But I can't boot into recovery mode. No matter if I connect it to a USB cable, the button command does not work.
Switching the device off also isn't possible. The only way to switch it off is disconnecting the battery (I have opened it to do so).
The only thing I can do is booting into download mode (so I know my volume up button works...).
Several times the screen was stuck on the "empty battery" symbol - which did not change no matter how long I had it in the charger. I can't really replicate how I got to the battery screen. I installed another battery just to see if if by some magic this would change something, but nothing changed about my issue. No boot possible and no booting into recovery.
I thought to myself: Well, maybe if I reinstall TWRP I can get into Recovery again. But when I try Odin I get the error message: "there is no PIT partition"
I know you will want additional info:
sadly, I cant' say which version of lineage I had running. I would have to look into my phone - which I can't.
I installed Lineage a couple of years ago, the phone was rooted and had TWRP recovery. I changed my USB port and Audio port several months ago.
But everything was running fine - I did not change or do anything recently. It happened overnight.
Do you have any ideas what I can do? I am brooding for two days now over this issue and I am at the end of the line here.
Did my memory just die on me? Is it an unfixable hardware issue?
Or software-related and potentially salvageable?
thanks in advance for anybody that bothers with my problem.
Click to expand...
Click to collapse
Hi, try to flash the stock firmware otherwise I really don't know :/
I guess I will lose my data when I install stock firmware, don't I?
What I ask myself is: Is the reason for not being able to boot into recovery that my device always thinks my battery is empty?
Is the fact that I can boot into download mode a sign that my memory and/or motherboard is still intact?
PinkElf said:
I guess I will lose my data when I install stock firmware, don't I?
What I ask myself is: Is the reason for not being able to boot into recovery that my device always thinks my battery is empty?
Is the fact that I can boot into download mode a sign that my memory and/or motherboard is still intact?
Click to expand...
Click to collapse
Are you using Lineage OS? If yes, then definitely yes. On my Xiaomi, I couldn't get into fastboot mode or into recovery, I don't know why and somehow I got there, I don't even know how I think I held the power mode for a long time and when the phone turned on I held the volume up button to get into recovery finally succeeded on the umpteenth attempt and from recovery I restarted the phone in fastboot mode and flashed the stock firmware. And yes, being able to boot your phone into fastboot is a good sign. It would be worse if it wasn't possible.
I am still stuck with the problem. I can boot into download mode. I can't find a way to boot into recovery.
Is there anything I can do in download mode?
If I find the lineage version I originally installed on my device, could I install it via ODIN and get my phone back without data loss? I have only ever installed ROMs via TWRP.
Just an idea, but as of now I get the error "could not find PIT partition" anyway while trying to reinstall TWRP.
PinkElf said:
I am still stuck with the problem. I can boot into download mode. I can't find a way to boot into recovery.
Is there anything I can do in download mode?
If I find the lineage version I originally installed on my device, could I install it via ODIN and get my phone back without data loss? I have only ever installed ROMs via TWRP.
Just an idea, but as of now I get the error "could not find PIT partition" anyway while trying to reinstall TWRP.
Click to expand...
Click to collapse
Yes, you can use download mode to install the firmware via Odin. Look
That means giving up hope for my personal data...
But even if I want to do this, I run into the problem, that I can't install anything due to "could not find PIT partition"...