Related
[Q] Tried to install Beatmod ICS, stuck on "screensaver" usb and recovery won't work
Hi guys,
I've watched the n00b video and been googling for the last few hours as well as reading through various pages on the XDA forum. I've found a lot of problems that are kinda similar and tried various solutions but don't seem to be quite getting there.
Basically I had Virtuous Affinity as the OS and clockworkmod installed (should be the most up to date versions of both, they were put on no more than a week ago) as well. I also had a backup of current OS and so on on the SD card, as well as the original zip of the rom.
I decide I want to give ICS a go and so I downloaded the betamod ICS and then loaded it. It asked me if I wanted to do a dalvik cache wipe, a dalvik cache + data wipe and a third option I don't recall. I went with the dalvik cache wipe (at the time I was under the impression that was the correct course of action) then put it back in my pocket while ICS installed.
I get my phone out of my pocket later and it's kinda stuck on what looks like (but logically isn't, I'm guessing it was meant to be a splash screen type thing while ICS installed or some such) a screensaver which just loops endlessly. The only thing you can really do is take the battery out and turn her on again, in which case you once again end up in the endless screensaver loop.
I've tried booting to recovery using volume - and the power button and unfortunately it just boots straight into the looping screensaver again.
Getting a bit worried and feeling adventurous I tried seeing what I could do with ADB, however the computer seemed unable to recognise that any device was connected with ADB devices not listing anything.
I've read up a lot and I'm at a loss as to what to do - there's a rom on the SD card and there also should have been a backup but I just can't get it into recovery.
I do have the ability to view the SD card on another device and interact with it, so if there's a potential SD fix, that's certainly not out the window.
But yeah, I'm clueless how to proceed here and very green at the whole rom business. Can anyone advise what I might try to do from here? I don't care what state I end up going back to, or if I lose my data, I can get all that back, I just want the phone in some semblance of basic operation.
I'll be keeping an eye on the thread, if I've left out any pertinent data ask away and thanks in advance for anyone with a clue how I can fix this mess .
EDIT: Post may be better off in ICS thread above and I do apologise if so, I would move it but I seem unable to delete it.
Remove battery for 5 seconds and then try again to boot into recovery using volume -and power button.
ik222 said:
Remove battery for 5 seconds and then try again to boot into recovery using volume -and power button.
Click to expand...
Click to collapse
I have, it doesn't work. I've left the battery out for a fairly long period. Volume - + power still just brings it back to the "screensaver" loop.
Thanks for the suggestion though.
Turn the phone off completely; pull the battery out for a bit then replace it and don't touch anything. Don't try to turn it on. Plug the phone by usb to your pc (still turned off). At the command prompt in the folder containing adb.exe type "adb reboot recovery" - the phone should power on and go to recovery where you can wipe properly and reflash whatever you want.
You should be able to boot to recovery using the volume down + power button combo (hold the volume-down key, then press and hold the power button and keep both held until you get to the bootloader menu); the only thing that's wrong with your phone is that you've flashed one ROM over another without wiping it first, so the ROM can't load but this shouldn't affect your bootloader or recovery.
Worst case you can flash a RUU which will restore it to the official firmware; you'll then need to re-root and re-install a recovery image to be able to flash custom ROMs again.
Very helpful post, thanks! I'll try all that and see how I go, I'll post if I still have trouble.
Yeah I dunno why I can't boot to recovery it's weird. The volume button wasn't working, so I removed it and am pressing in the volume down portion of the volume button with a pen while holding down the power button. It's possible perhaps I'm not successfully depressing volume down, but I'm 99% sure I am and that that's not it. I am however doing it as you and other guides advise, depress volume down, hold it and then depress power and hold both for about three seconds, no joy!
Anyway, as said, I'll try what you're recommending and see how I go. Thanks!
hopscotchjunkie said:
At the command prompt in the folder containing adb.exe type "adb reboot recovery"
Click to expand...
Click to collapse
Curious what you mean by this? Cause there's no command prompt in the folder ADB is in. Do you mean in command prompt, be in the folder, i.e. c:\abd kinda thing? I tried just loading command prompt and typing abd reboot recovery, no device detected - no joy.
Ethicistabdiel said:
Curious what you mean by this? Cause there's no command prompt in the folder ADB is in. Do you mean in command prompt, be in the folder, i.e. c:\abd kinda thing? I tried just loading command prompt and typing abd reboot recovery, no device detected - no joy.
Click to expand...
Click to collapse
Yeah that was what I meant; I've got a feeling that that only works when the phone is powered off if you had USB debugging activated on the phone beforehand, so if that's not working that might be why.
c:\adb
results in error: device not found.
ADB app itself is in C:\adb\platform-tools but when I try that it goes The System cannot find the path specified. I've tried cd/adb and I can get that far but I can't get to adb/platform-tools.
EDIT:
Okay, I managed to get to c:\adb\platform-tools but adb reboot recovery is still advising error: device not found. Guessing perhaps I didn't have usb debugging enabled. Are you able to suggest another work around at all? I'm happy to flash it to whatever, I don't mind losing data, just want to get it in working order again. I don't see how I can though when I seemingly don't have access to recovery or USB...hrmm, must be some way around.
Accidental double post, sorry.
You need to try get into recovery mode, where you can do a full wipe and see if that fixes anything.
Firstly, remove your battery then re-install it, your phone should still be turned off at this stage. Press and hold the volume down button, then additionally press and hold the power butter, until something appears on the screen. If the bootloader appears, you can then boot into recovery from there.
If the above fails to work, report back with your results and hopefully something else will be suggested.
Ethicistabdiel said:
c:\adb
results in error: device not found.
ADB app itself is in C:\adb\platform-tools but when I try that it goes The System cannot find the path specified. I've tried cd/adb and I can get that far but I can't get to adb/platform-tools.
EDIT:
Okay, I managed to get to c:\adb\platform-tools but adb reboot recovery is still advising error: device not found. Guessing perhaps I didn't have usb debugging enabled. Are you able to suggest another work around at all? I'm happy to flash it to whatever, I don't mind losing data, just want to get it in working order again. I don't see how I can though when I seemingly don't have access to recovery or USB...hrmm, must be some way around.
Click to expand...
Click to collapse
Your only other option to get into recovery is the volume-down/power-on combination. Like I said, I can't think why that's not working unless it's related to your missing volume button (maybe it's not maintaining a constant pressure on the button when you're using whatever to press through the hole).
If you still can't get that to work, I would suggest finding a stock RUU and flashing that. It's an .exe file that runs from your PC and will return your ROM, bootloader and radio back to stock. Obviously that means you'll lose root and your custom recovery so you'll need to do all that again from scratch. There's a sticky in the dev section with a link to a thread with various RUUs (it's named something along the lines of "shipped & test ROMs" - I'll check that and link to it once I've dragged myself out of bed to the computer). You'll lose all your data, but if you took a backup beforehand you can restore that once you're back up and running.
//sent from my Desire HD using Tapatalk; all errors entirely intentional.
Yeah I'm starting to think perhaps the down button is just broken.
What state should the phone be for the RUU, turned off with usb plugged in or turned on? Bearing in mind, that when on, all it will do is the "screensaver". Will it work in either of those states?
Thanks, will deffo research more when I get home. Appreciate the help immensely.
http://forum.xda-developers.com/showthread.php?t=824357&page=5
Guessing you mean that as far as the ruu thread. Am downloading a stock rom atm, with shaped internet till tomorrow, meh! Will see how I go. Have a feeling phone was probably Vodafone branded at stock though, so that could make for extra fiddling but yeah, fingers crossed.
If you are able too install a stock-rom you can work from their than install 4EXT recovery
touch than you doen't need the volume buttons.
I downloaded the most recent stock rom on the link above. When I try to install it though, phone off or on, it advises a USB connection error. Is this likely to be because I originally had vodafone stock and need to make a gold card, or should it still at least be recognising it? It does advise not to run any programs on the phone or anything when while installing the update, but of course, as long as my phones turned on it's stuck on the damned screensaver loop.
http://forum.xda-developers.com/archive/index.php/t-841890.html
Gonna give that a go, fingers crossed!
D'oh, just found out my mobile was Three at stock and not Vodafone, the search continues .
Gah, I'm about tearing my hair out here, I want my damned phone back . Stuck using a $79 Huwawei Vodafone thing at the moment and it's so so so awful.
Anyway. I was under the impression that making a goldcard would mean I could RUU a non-Three stock rom on the phone. I made a goldcard following these instructions; http://www.addictivetips.com/mobile/how-to-make-gold-card-for-htc-desire-hd/
Then I turned the phone on as the RUU advises, (meaning it's scrolling through the feckin' "screensaver") and start the process and once again get a USB connection error.
What's the better process at this stage, try and take it back to Three stock? I don't see how I can at the moment, the only Three stock I can find seems to be rom, not RUU, meaning I'd need to load from the phone, which I can't due to no recovery. Or should I keep trying to get the goldcard thing to work, maybe try some different RUU's or something?
I'm open to any other suggestions as well. Had a bit more of a fiddle around with my volume down button, no matter what I do though, I can't get recovery mode. Always boots first to the white HTC screen and then starts the infernal "screensaver" loop.
Ethicistabdiel said:
Yeah I'm starting to think perhaps the down button is just broken.
What state should the phone be for the RUU, turned off with usb plugged in or turned on? Bearing in mind, that when on, all it will do is the "screensaver". Will it work in either of those states?
Thanks, will deffo research more when I get home. Appreciate the help immensely.
Click to expand...
Click to collapse
How come the volume down button be broken. When you were using Affinity Rom weren't you able to use your volume button for music. Remove SD card from phone then press "First - Volume down gently for 2 sec" & press-hold power button when it goes into bootload place your sd card back select option "REBOOT RECOVERY". I think your panicking too much just be patient nothing is wrong, i think your just hurrying it up...
The volume button didn't work before either. I had to manually adjust volume from settings. I thought it was just because of the dodgy plastic button on top, but using a pen to depress the button underneath doesn't work either.
Believe me, I've been trying to fix this for days now, every different way of depressing volume down in order to get to recovery has not worked. Short of taking the phone apart and seeing if I can see what's wrong with the button (doubtful with my level of expertise) then it ain't happening via that method.
Got a little bit hopeful with this;
http://www.htcdev.com/bootloader/ruu-downloads
But that too requires my phone to be in usb debugging mode, which of course, it isn't.
Is there anyway to force the phone into usb debugging mode using some form of hack or some such? The thing is, it is powered and everything, I can turn it on, the screen works and all that jazz and indeed the phone will charge from USB and the computer makes a noise when I plug or unplug it, the phone itself however won't do anything other than the "screensaver" ICS installation loop. I guess I'm thinking where there's life there's hope and perhaps there's some way in that state I can get it to switch debugging on, though I think I'm reaching at this point .
Ethicistabdiel said:
The volume button didn't work before either. I had to manually adjust volume from settings. I thought it was just because of the dodgy plastic button on top, but using a pen to depress the button underneath doesn't work either.
Believe me, I've been trying to fix this for days now, every different way of depressing volume down in order to get to recovery has not worked. Short of taking the phone apart and seeing if I can see what's wrong with the button (doubtful with my level of expertise) then it ain't happening via that method.
Got a little bit hopeful with this;
http://www.htcdev.com/bootloader/ruu-downloads
But that too requires my phone to be in usb debugging mode, which of course, it isn't.
Is there anyway to force the phone into usb debugging mode using some form of hack or some such? The thing is, it is powered and everything, I can turn it on, the screen works and all that jazz and indeed the phone will charge from USB and the computer makes a noise when I plug or unplug it, the phone itself however won't do anything other than the "screensaver" ICS installation loop. I guess I'm thinking where there's life there's hope and perhaps there's some way in that state I can get it to switch debugging on, though I think I'm reaching at this point .
Click to expand...
Click to collapse
The only option i can think of is "Fix your volume button from your nearest Service centre". Without that you cant do anything. I am Sorry....
Hallo,
just now I was trying to open an app on my DHD but it kept force closing so I decided to Normaly restart it. When I did that it went to the Welcome Logo then got stuck and kept on turning on and Off.
Then I removed the battery and tried again. This time the Bootscreen appeared (I was glad since I could recover a backup version of the RAM) but to my amazement I couldn't navigate through the options. Even the power button didn't work. I tried several times but with the same results.
I was wondering is there a way to restore my mobile from my laptop (USB Debugging?) now after I reached this state?!
How could I solve this?
Any help would be appreciated
UPDATE: I noticed before the Bootscreen loads, there appears some messages quickly before they disappear. I kept on turning my phone on and off to see what they said eventually I came out with this
P98DIAG.ZIP
Image not found
.
.
P98DIAG.NBH
Image not found
.
.
ring any bell?
Reda88 said:
Hallo,
just now I was trying to open an app on my DHD but it kept force closing so I decided to Normaly restart it. When I did that it went to the Welcome Logo then got stuck and kept on turning on and Off.
Then I removed the battery and tried again. This time the Bootscreen appeared (I was glad since I could recover a backup version of the RAM) but to my amazement I couldn't navigate through the options. Even the power button didn't work. I tried several times but with the same results.
I was wondering is there a way to restore my mobile from my laptop (USB Debugging?) now after I reached this state?!
How could I solve this?
Any help would be appreciated
UPDATE: I noticed before the Bootscreen loads, there appears some messages quickly before they disappear. I kept on turning my phone on and off to see what they said eventually I came out with this
P98DIAG.ZIP
Image not found
.
.
P98DIAG.NBH
Image not found
.
.
ring any bell?
Click to expand...
Click to collapse
Can you navigate any menus? If you can't you probably have a volume key hardware issue. If you can, i would just put a p98diag.zip on the root and reflash (use the rooted one).
Sounds like you are booting into bootloader. You need recovery. Pull the battery, then reinsert and hold volume down + hit power. If that doesn't work if you have adb set up on computer, plug it in to computer and use adb reboot recovery.
Sent from my Inspire 4G using XDA
I guess that you have a PD98IMG.zip on sd card.
Remove it or everytime you reboot in bootloader it will ask you to update in a never ending story. Probably this is why all other commands are not working except reboot.
Then reboot bootloader and go to recovery.
No I can't navigate (the weird thing is the power button also dosen't respond) it's like it freezes as soon as it turns on... Could you give me the PD98IMG.zip in a separate link?
I tried reinst the battery while holding the volume + but it didn't work. It vibrated 4 times while the charge light turned green but that was it. It stayed green and the screen was off...
I've always had the volume keys issue even before it went crazy (they do not always respond to my press) but I just installed 3rd party apps as a workaround.
I couldn't find the p98diag.zip anywhere on the SD card (could you give me the path for it?)
I will try to reboot it through my laptop but could someone give me the commands I should write? I'm not that experienced in that field.
Btw I left it for a while before I turned it on again, it went into Safe Mode (no apps no nothing) then I turned it off and after several tries it finally turned on in the normal mode and was almost stable until I restarted it and it went to point 0 again and now I'm stuck with the bootscreen :S
Thanks for your help
Do you have adb set up on your computer? If so then connect phone to laptop. Open command prompt type "adb remount" then "adb reboot recovery"
Sent from my Desire HD using XDA
while looking through the files I used to root my phone when I bought it I found the p98diag.zip. I copied it to my SD Card and wanted to install it. It found it but then it said
Parsing...[SD ZIP]
[1] BOOTLOADER
[2] BOOT
....
but it's been like that for 2 hours now. I tried reinst the battery and pluging in the mobile to my laptop but it didn't recognize it. (I tried the adb and it gave me Device not found" error!
Is it normal for the phone to take long to parse the zip file? what should I do now?
Reda88 said:
while looking through the files I used to root my phone when I bought it I found the p98diag.zip. I copied it to my SD Card and wanted to install it. It found it but then it said
Parsing...[SD ZIP]
[1] BOOTLOADER
[2] BOOT
....
but it's been like that for 2 hours now. I tried reinst the battery and pluging in the mobile to my laptop but it didn't recognize it. (I tried the adb and it gave me Device not found" error!
Is it normal for the phone to take long to parse the zip file? what should I do now?
Click to expand...
Click to collapse
You shouldn't have installed pd98diag. I would suggest either trying to run the ruu to get back to stock, or find the stock rom in pd98img.zip form and place on root of sdcard. Then reroot and start over.
Edit: if you find the stock rooted in pd98img.zip form that should work too and you won't have to reroot.
Edit 2: be sure to remove the pd98diag.zip from your sd card.
Sent from my Desire HD using XDA
bcd420 said:
You shouldn't have installed pd98diag. I would suggest either trying to run the ruu to get back to stock, or find the stock rom in pd98img.zip form and place on root of sdcard. Then reroot and start over.
Edit: if you find the stock rooted in pd98img.zip form that should work too and you won't have to reroot.
Edit 2: be sure to remove the pd98diag.zip from your sd card.
Sent from my Desire HD using XDA
Click to expand...
Click to collapse
Good advice! I still have all the files I used to root (even the RUU)
And you're right I shouldn't have flashed the old pd98img because now my laptop can't recognize my mobile and I can't debug it from the command line (it says Device not found)
Can I still be able to root the img without using my phone? I used this guide to root my phone (http://www.addictivetips.com/mobile/how-to-downgrade-htc-desire-hd-to-root-it-after-ota-update/)
Where can I find the rooted img? and will it be possible for me to upload it here so that someone could root it for me on his device and give it to me rooted?
To boot into recovery
Hold down volume - button (not +) while pressing power button.
Let go of power button but continue pressing down on volume -.
Hey presto ... recovery.
It's a very easy mistake to make, I did it myself a few times when I first got into rooting and flashing ROM's.
lol!
no mate I wish it was like that.
Found this in the inspire section may be helpful. http://forum.xda-developers.com/showthread.php?t=986014
Sent from my Desire HD using XDA
A friend has asked me to look at his Wildfire, he said it was updating the Market and then blank screened. Since then it will not turn on, vibrates, then nothing.
I suspected screen (replaced a few wildfire ones now) but no sign of life from touch buttons, volume key, etc - so suspect it is bricked.
Tried to flash it with RUU but the phone will not go into the boot menu via volume down & power on. I've tried numerous times and it went into boot menu once, but you could not select anything, no keys working.
Hooked up to laptop and laptop could see it, but when you try to run the RUU you get Error 170, probably becaused it's not actualy in USB Boot mode.
Has anyone seen this? Any other tricks to get it into boot menu? Anything I can run from laptop or SD card to force it into a recovery or boot menu?
This is a stock ROM phone, not modified at all.
Any help much appreciated
Am sorry but this the Wildfire S forums not Wildfire , write above on find your device buzz and go to that phone , it is the Wildfire forum , those guys might answer ...
Oops, sorry, my mistake!!
A friend has asked me to look at his Wildfire, he said it was updating the Market and then blank screened. Since then it will not turn on, vibrates, then nothing.
I suspected screen (replaced a few wildfire ones now) but no sign of life from touch buttons, volume key, etc - so suspect it is bricked.
Tried to flash it with RUU but the phone will not go into the boot menu via volume down & power on. I've tried numerous times and it went into boot menu once, but you could not select anything, no keys working.
Hooked up to laptop and laptop could see it, but when you try to run the RUU you get Error 170, probably becaused it's not actualy in USB Boot mode.
Has anyone seen this? Any other tricks to get it into boot menu? Anything I can run from laptop or SD card to force it into a recovery or boot menu?
This is a stock ROM phone, not modified at all.
Any help much appreciated*
I have a way but I cant remember it lol
If I can remember when I get home, i'll re-post.
OK, cool
Made slight progress today, even though I had the boot menu come up once yesterday, but no response from keys, I did notice that even though I was trying to access boot menu, it was actually acting like it was in the menu, just blank screen, i.e. if I held power button afterwards I got no vibration, but if I did pull battery and hold power, I did, as if it was booting up.
I wonder if in actual fact the screen is dead, but also there is a software hang up, as if display was dead, you would still be able to swipe the screen, get touch keys to light up when pressed, etc.
Anyway, so I went into boot mode, blank screen, pressed power anyway which would be FASTBOOT - right?
Hooked up to PC, ran an RUU and it connected OK, went through process but failed on ID, because the phone has a T-Mobile ROM and I was trying to flash with non-branded one.
So I either need to find a T-MOB UK RUU, I found one but it wouldn't run, or I need to create a goldcard (can I do that with a semi bricked device?) and go down that route.
Either way, I'm pretty sure the LCD is dead, so for the sake of £7.50 I'll replace that first, even if it has got further issues, having a working LCD will help!!
yeah get the screen fixed first.
you will only have to fix the screen later and the hassle of trying to fix a phone with broken screen, to have to have it fixed later anyway isnt really the most logical way of doing things
Hello,
my wife got a S21 FE (SM-G990B/DS VD2). Yesterday it started to reboot over and over out of a sudden, showing the samsung logo first, followed by the knox logo, then shutting off and on again. Tried several guides to enter Recovery or Download Mode. The only thing that worked was entering download mode by pressing Vol up, down and power while a USB-Cable is plugged in, but as soon as i press the vol up button to pass the "warning screen", it shows some phone specs for a couple of seconds, shuts off and starts bootlooping again. After some hours, the phone once entered recovery mode when it lied next to me for about an hour. Tried to wipe cache, but just got an error I can't remember right now. Hoped it fixed itself when it made it to recovery and just rebooted to see if it works again, but then it just keept bootlooping again.
Since then I couldn't figure out why it once booted to recovery on it's own nor why I can't force it to enter recovery by pressing vol up + on.
Still hope it's just a faulty update or bug, but feels very much like it's a hardware related issue. Replacing the phone won't be an issue, but I'd really want to save data on the phone as my wife didn't make any backups and really wants to keep the photos.
As I just found guides that included recovery or DL-Mode, which are both no valid options for my case, I'd be thankful for any ideas to fix the phone or at least gain access to files before replacing it.
So.. did anyone come across similar issues and found a solution to revive the phone or are there any "unpopular" ways to recover samsung phones out of this state?
Edit:
Turned off completely overnight, booted once to system, looped again and now it's working like nothing ever happened. Got no clue what caused it or why it is working again. Saved everything for the case it happens again.
Wouldn't trust that device anymore, but my wife wants to keep it.
¯\_(ツ)_/¯
I would just like to reply here and add my own potential fix and also would like confirmation that it would work.
So I have a SM-G996B in a boot loop which returns a 'fs_mgr_mount_all' error. Possible to reboot into recovery mode, cleared cache and restarted bootloader etc with the same boot loop. Powered off and connected to PC for Download mode for ODIN recovery but upon pressing volume up, it then restarts again so Download mode recovery is impossible.
I know however that Developer options and USB debugging was enabled on the device as well as unlocked boot loader. I was able to download the correct original stock OS based on the PDA , CSC and Android version.
I have then installed the latest ADB software on my PC and Samsung USB drivers.
By then rebooting into recovery mode, I have the option of 'Apply update from ADB'. I have then confirmed the device connects using the ADB devices command.
I would like to clarify one thing however. I want to keep the user data at all costs. By using the stock firmware and renaming as update.zip, will it use the HOME_CSC and not the CSC file? If not would it work if I open the zip and remove the CSC before re-zipping to make sure?
Thanks
Reebee said:
Hello,
my wife got a S21 FE (SM-G990B/DS VD2). Yesterday it started to reboot over and over out of a sudden, showing the samsung logo first, followed by the knox logo, then shutting off and on again. Tried several guides to enter Recovery or Download Mode. The only thing that worked was entering download mode by pressing Vol up, down and power while a USB-Cable is plugged in, but as soon as i press the vol up button to pass the "warning screen", it shows some phone specs for a couple of seconds, shuts off and starts bootlooping again. After some hours, the phone once entered recovery mode when it lied next to me for about an hour. Tried to wipe cache, but just got an error I can't remember right now. Hoped it fixed itself when it made it to recovery and just rebooted to see if it works again, but then it just keept bootlooping again.
Since then I couldn't figure out why it once booted to recovery on it's own nor why I can't force it to enter recovery by pressing vol up + on.
Still hope it's just a faulty update or bug, but feels very much like it's a hardware related issue. Replacing the phone won't be an issue, but I'd really want to save data on the phone as my wife didn't make any backups and really wants to keep the photos.
As I just found guides that included recovery or DL-Mode, which are both no valid options for my case, I'd be thankful for any ideas to fix the phone or at least gain access to files before replacing it.
So.. did anyone come across similar issues and found a solution to revive the phone or are there any "unpopular" ways to recover samsung phones out of this state?
Edit:
Turned off completely overnight, booted once to system, looped again and now it's working like nothing ever happened. Got no clue what caused it or why it is working again. Saved everything for the case it happens again.
Wouldn't trust that device anymore, but my wife wants to keep it.
¯\_(ツ)_/¯
Click to expand...
Click to collapse
Similar issue with same phone. In a bootloop after trying to root. None of the button combinations have worked for me, for the past several days.
Tried powering the phone off for the whole night.
When connected to the PC shows phone is in recovery mode via adb (blank screen though).
Want to know how to get into DL-mode, guaranteed.
Got to DL mode by pressing vol up + down + power + usb cable connected in PC and phone. However, couldn't do anything there, but maybe you can
Also, phone is still working and I still have no clue what was the problem and what fixed it.