Related
Well, after spending almost 11 hours trying to boot into recovery or download, I know for sure that there is something going on with my phone re: hardware locked. The date on my box is 7-16. It is an early Vibrant. But no matter what I do, I cannot get into download or recovery which means my ****ing phone is literally worthless.
I have tried all possible thousands of combination's of buttons, batteries, and cords while booting and nothing happens.
The Vibrant logo shows, then it shows the pink, annoying as hell T-mobile logo, than goes to the Galaxy S logo which loads for a little bit and then just leads me to a black screen. Eventually the 4 buttons on the front of the phone turn on and then nothing else happens. It will just sit like this forever.
I know all I need to do is get a working ROM loaded but it is literally impossible to do so.
Can anyone offer any suggestions? Or are anyone else having the same problem?
I guess the only way I can get a working phone is to get in touch with T-mobile and do a Warranty exchange. That's a damn shame too, because I will be without a working phone for a week.
What about using adb?
adb reboot recovery -or- adb reboot download ?
I had a hw locked vibrant, never tried the adb reboot download, recovery did work.. I added another line on my account last night for somone, who got a vibrant, theirs wasn't hw locked, so I traded 'em ;P
Agree with the above poster I have been stuck on the vibrant screen or dark screen and adb still worked to save me
when i try to use adb, it just tells me that it cant find the device. i'm not able to boot into android OS at all.... screen just hangs. so my computer is never getting a chance to see my phone hence why i cant use adb to reboot it into recovery or download.
I believe your device has to go into recovery mode then check with and devices and if you see a device I THINK it is and reboot download, I am 90% certain
Sent from my SGH-T959 using Tapatalk
have you installed the drivers? phone DOES NOT have to boot into android for adb to read it.
98classic said:
have you installed the drivers? phone DOES NOT have to boot into android for adb to read it.
Click to expand...
Click to collapse
i do believe i have the correct drivers installed. i was able to use adb to run lagfixes before i was having this problem. when i boot my phone, i get a sound from my computer saying that it recognizes a usb device. the two drives in the vibrant show up in My Computer but i cannot access them as windows says they are not accessable at the moment.
at what point will adb be able to recognize my phone when booting? no matter what i do when i try adb shell i get error: device not found
It could be the phone not bring in debugging mode, either because it's been turned off or the os isn't getting far enough to turn it on. I think I've been able to get adb to recognize my phone even while it was booting up (at the white vibrant screen). Maybe you can try adb then?
Same problem here. I probably just have to sell it fast on ebay or something. Hopefully some kind of fix starts by the end of the week. First phone in my smartphone life to brick from a simple Voodoo lag fix. Please XDA gods find a solution.
crazycaveman said:
It could be the phone not bring in debugging mode, either because it's been turned off or the os isn't getting far enough to turn it on. I think I've been able to get adb to recognize my phone even while it was booting up (at the white vibrant screen). Maybe you can try adb then?
Click to expand...
Click to collapse
nope, no go. adb will not recognize my device no matter what. and the device isnt loading the OS so i cannot turn debugging on. i guess this is a real "brick" then.
This sounds like a rant rather than a question. Just sayin'.
DKYang said:
This sounds like a rant rather than a question. Just sayin'.
Click to expand...
Click to collapse
fixed that. my bad.
Check my thread in the dev section... I can get ADB working when you are stuck at the vibrant screen... MIGHT... just might work in your situation...
My thread is probably fallen back a few pages now... its a [Guide] [Think Tank]
renocivik said:
Check my thread in the dev section... I can get ADB working when you are stuck at the vibrant screen... MIGHT... just might work in your situation...
My thread is probably fallen back a few pages now... its a [Guide] [Think Tank]
Click to expand...
Click to collapse
thanks for the suggestion. i found your thread and went through the steps in the OP... still no luck. no matter what i do, i cannot get passed the black screen the loads after the galaxy s logo. i also cannot get into download mode or recovery no matter what combination of button presses i use.
just do the following , i used to have the problem of going into the download mode and this is what realy worked to me :
1- turn off the phone.
2- plug in the USB cable.
3- wait until the battery green charging start.
4- press the vol + , vol - , the power botton together.
5- when the screen gose black release the power botton only.
you should now be in the downloading mode
core99 said:
just do the following , i used to have the problem of going into the download mode and this is what realy worked to me :
1- turn off the phone.
2- plug in the USB cable.
3- wait until the battery green charging start.
4- press the vol + , vol - , the power botton together.
5- when the screen gose black release the power botton only.
you should now be in the downloading mode
Click to expand...
Click to collapse
this isnt working either. :-(
I just fixed this on my phone. Your phone will go into download mode. Plug the phone in and wait for the battery symbol to fully load. Hold Vol + and _ and PWR until it goes black, then release the PWR button only. It will go into DL mode. Fire up Odin, and flash the "Froyo that does not brick" ROM. It will boot into the i9000 recovery mode and give you an error. Hold the Vol + and - and PWR again and release PWR when the phone goes black. It will go into DL mode again. Now with Odin, flash the factory firmware, making sure to click re-partition this time. After the phone reboots, it will fire right up into the factory ROM.
atoz350 said:
I just fixed this on my phone. Your phone will go into download mode. Plug the phone in and wait for the battery symbol to fully load. Hold Vol + and _ and PWR until it goes black, then release the PWR button only. It will go into DL mode. Fire up Odin, and flash the "Froyo that does not brick" ROM. It will boot into the i9000 recovery mode and give you an error. Hold the Vol + and - and PWR again and release PWR when the phone goes black. It will go into DL mode again. Now with Odin, flash the factory firmware, making sure to click re-partition this time. After the phone reboots, it will fire right up into the factory ROM.
Click to expand...
Click to collapse
this is exactly the method i want to try. but unfortunately i cannot get the phone into recovery or download mode. i have tried at least 100 times now with many different combination's of plugging the usb cord in and pressing the volume and power buttons.
two ideas: one, is it possible that i wiped recovery and download mode from my phone on accident? the reason why i ask is that i was super tired and flashing roms and kernels to my phone. i flashed back to my original stock rom and then i flashed the kernel. for some reason, i selected wipe date/cache in Rom Manager before flashing the kernel. i have no idea why i did this. seriously. totally noob move. so im assuming i have a kernel flashed but now there is no ROM installed for the phone to boot into.
two, if above is not the issue, than im going to assume that the phone is not recognizing any button presses while its off, so when i turn it on it just recognizes that the power was pressed and ignores the volume presses, thus not booting the phone into recovery or download.
edit: i should mention again that at no time does adb recognize my device. so i cannot use adb to reboot the phone into the mode i need.
just a comment for the OP - the vibrant isnt worthless, it is something that YOU did to get the phone into its current state. So dont blame the phone for something that it didnt do on its own.
/end rant
byt3b0mb said:
just a comment for the OP - the vibrant isnt worthless, it is something that YOU did to get the phone into its current state. So dont blame the phone for something that it didnt do on its own.
/end rant
Click to expand...
Click to collapse
I understand what you mean. I appreciate your criticism of my original post. Let me say that I wrote it while frustrated. But I know that isn't an excuse.
The device is fantastic. I know that I did this to it myself. It's unfortunate.
Anyways, I received a replacement phone. I will be more careful this time.
Recently my DNA has been getting laggy and restarting occasionally, and yesterday after sending a simple text message it decided to enter a reboot-loop that I think is probably fatal.
When I plug it in to any power, it turns on, shows the white/green HTC screen, and then immediately shuts down, and repeats the cycle. I have not been able to get it to turn off (while on power), and cannot turn it on (even into the loop) while off power. HOWEVER, I CAN use the vol - shortcut to get to the bootloader screen BUT I cannot select anything, as it immediately shuts down when I try to do something.
My DNA is running the latest stock software (OTA from Verizon, i think 4.4.2), and i have not modified it (S-ON, unrooted etc...).
Any and all help would be appreciated!
Bonus: on the 95% chance it is dead, should i go moto x/droid turbo or stick with a *gasp* iphone 5 for 2 months until gs6/htc m9?
androidnj7 said:
Recently my DNA has been getting laggy and restarting occasionally, and yesterday after sending a simple text message it decided to enter a reboot-loop that I think is probably fatal.
When I plug it in to any power, it turns on, shows the white/green HTC screen, and then immediately shuts down, and repeats the cycle. I have not been able to get it to turn off (while on power), and cannot turn it on (even into the loop) while off power. HOWEVER, I CAN use the vol - shortcut to get to the bootloader screen BUT I cannot select anything, as it immediately shuts down when I try to do something.
My DNA is running the latest stock software (OTA from Verizon, i think 4.4.2), and i have not modified it (S-ON, unrooted etc...).
Any and all help would be appreciated!
Bonus: on the 95% chance it is dead, should i go moto x/droid turbo or stick with a *gasp* iphone 5 for 2 months until gs6/htc m9?
Click to expand...
Click to collapse
At any point can you get it to answer
Fastboot devices
?
dottat said:
At any point can you get it to answer
Fastboot devices
?
Click to expand...
Click to collapse
I can not get it to receive any signals from me in the bootloader as it shuts down immediately. I tried connecting it to my computer for use with adb, but fastboot WAS enabled and developer tools were DISABLED (i think), plus it cannot keep a constant connection, so that wasn't working.
After doing some research I think I can save it IF I can get it to a stable state from the one it is currently in, and then using the bootloader screen to do a factory reset ( or use
"adb reboot recovery"), but like I said that is depenednet on getting it to stop the boot loop.
I also tried doing something called an RUU (I have limited knowledge of this, i sued the dottat one), but since it cannot establish a constant connection, it did not work.
Im open to any suggestions at this point! Thanks
I seem to have posted my reply in haste.
I have installed the "minimal adb and fastboot" tool that was suggested for basic fastboot use. Fastboot will not recognize it when I use "fastboot devices".
I did install the HTC drivers a while ago, but I suspect they may not work, could that be the issue? I am running win 8.1.
Thanks
androidnj7 said:
I seem to have posted my reply in haste.
I have installed the "minimal adb and fastboot" tool that was suggested for basic fastboot use. Fastboot will not recognize it when I use "fastboot devices".
I did install the HTC drivers a while ago, but I suspect they may not work, could that be the issue? I am running win 8.1.
Thanks
Click to expand...
Click to collapse
Possibly. What does the device show up as in device manager?
dottat said:
Possibly. What does the device show up as in device manager?
Click to expand...
Click to collapse
For the 5-10 seconds its "on" every cycle, it shows up as a CD Drive (not the HTC6435 etc etc that it usually does)
androidnj7 said:
For the 5-10 seconds its "on" every cycle, it shows up as a CD Drive (not the HTC6435 etc etc that it usually does)
Click to expand...
Click to collapse
Hold volume up and power until the screen flickers and immediately switch to volume down only. Get it right and you will land in boot loader. Need boot loader to show fastboot usb
dottat said:
Hold volume up and power until the screen flickers and immediately switch to volume down only. Get it right and you will land in boot loader. Need boot loader to show fastboot usb
Click to expand...
Click to collapse
Yes I have gotten into the bootloader before but as soon as it shows up (and i try to select using the vol +/-) it shuts down and restarts right away. Basically, I cant even get the bootloader in a stable state.
androidnj7 said:
Yes I have gotten into the bootloader before but as soon as it shows up (and i try to select using the vol +/-) it shuts down and restarts right away. Basically, I cant even get the bootloader in a stable state.
Click to expand...
Click to collapse
Fastboot usb is going to be your only option. If you aren't able to stay there it's hardware. Any chance a button is stuck?
dottat said:
Fastboot usb is going to be your only option. If you aren't able to stay there it's hardware. Any chance a button is stuck?
Click to expand...
Click to collapse
You are right unfortunately, I can absolutley not stay in the bootloader with any sort of stability. I read on another thread that opening it up and disconnecting the battery from the motherboard would help, so thats what I did. As soon as I sealed it back up, the reboot-loop started right up again. My guess is that the motherboard is fried, its either that or the battery is holding no charge whatsoever.
If the board is fried, im done right?
if its the battery, is there any way to manually charge not going through the board?
Thanks for all your help btw!
Hi everyone,
While trying to return to stock using the LG Flash Tool .tot method, my phone got disconnected from my PC during the firmware update. Now, I just get the LG screen in a boot loop without the ability to get into download mode or recovery. I've looked around for a good half hour and couldn't find a thread describing a similar problem, so if it's a noob question, my bad. I have insurance for physical damage, so it might accidentally get run over at some point today. Any last ditch efforts available before it happens?
Appreciate any and all input!
jhajj33 said:
Hi everyone,
While trying to return to stock using the LG Flash Tool .tot method, my phone got disconnected from my PC during the firmware update. Now, I just get the LG screen in a boot loop without the ability to get into download mode or recovery. I've looked around for a good half hour and couldn't find a thread describing a similar problem, so if it's a noob question, my bad. I have insurance for physical damage, so it might accidentally get run over at some point today. Any last ditch efforts available before it happens?
Appreciate any and all input!
Click to expand...
Click to collapse
If you pull the battery, then put it back in, it should be off.
Then press and hold vol dn while plugging it in it should go into DL mode. Flashtool should work then.
It might be vol up. I can't remember off hand.
It's Vol Up (and hold it) + plug into the computer to get to Download Mode, but if the OP was already in a flash process that got interrupted it's entirely possible the phone won't go back into Download Mode again. It should be able to get back into that mode given how it works but, it's all relative given how far along the process was the first time when it was interrupted.
Pull the battery for 30 seconds, re-insert it, then hold Vol Up + plug it into the computer and see what happens. If it will absolutely not jump back into Download Mode then yep, it's pretty much hosed and would need LG to do something to resolve it.
Good luck...
jhajj33 said:
I have insurance for physical damage, so it might accidentally get run over at some point today.
Click to expand...
Click to collapse
Thanks for that good laugh, almost spit out my coffee with that one.
engine95 said:
If you pull the battery, then put it back in, it should be off.
Then press and hold vol dn while plugging it in it should go into DL mode. Flashtool should work then.
It might be vol up. I can't remember off hand.
Click to expand...
Click to collapse
That was the first thing I tried doing, it completely ignores my button presses no matter what I do. Held uo/down while plugging it in, , tried power+up, power+down to get into recovery mode, nothing. Just keeps showing the splash screen over and over again. This isn't my first, or even 10th rodeo as far as restoring phones back to stock, but I've never seen something like this before. Starting to think it's a lost cause.
When it is at the LG screen try running:
fastboot reboot-bootloader hopfuly that will boot you into download mode. The next thing you can try is to download the twrp image and then run this command: fastboot flash boot <namehere>. I know its not the same device but I did the same thing ony kindle fire and that boot command worked. It just booted me into twrp and I flashed a new rom.
So i was using RessurectionRemix (a version from last month) and recovery twrp 3.1.0-0 and the phone was working great!
Yesterday i left my phone charging over night and in the morning i wake up to my phone bootlooping!
So i tried different things including everything it says here https://forum.xda-developers.com/le-max-2/how-to/guide-hard-brick-fix-qualcomm-hs-usb-t3492949 without luck
I can get it into recovery and fastboot but as soon as i let the key combination go the phone stops and just shows a black screen (screen is on) and i cant get into qualcomm recovery to flash!
And the only way to shut off the phone is by holding power + vol up + vol down!
Any solution or suggestions?
Use flashone method to unbrick
md07 said:
Use flashone method to unbrick
Click to expand...
Click to collapse
As i already mentioned i cant get into qualcomm recovery so i cant use flashone
try to flash fastboot rom from cucoco's.
Tsoler said:
As i already mentioned i cant get into qualcomm recovery so i cant use flashone
Click to expand...
Click to collapse
connect phone to computer, try force shutdown phone by hard button, ater phone shutdown, immediately release power but keep both volume. Phone maybe will enter Qualcomm flash dead mode, and Flashone will regconize com phone (refresh nedded)
Hope you success ! And believe, if a phone can flash with Qfil or Flashone, almost that phone never die (software)
Are you able to connect to the phone via Vysor, either via Chrome browser or as a standalone app on Windows PC when you do not see anything on the phone screen? Please post if Vysor install goes thru successfully. Hope your developer options/USB debugging are on. I assume your phone boots but may have display issues either hw or sw.
md07 said:
connect phone to computer, try force shutdown phone by hard button, ater phone shutdown, immediately release power but keep both volume. Phone maybe will enter Qualcomm flash dead mode, and Flashone will regconize com phone (refresh nedded)
Hope you success ! And believe, if a phone can flash with Qfil or Flashone, almost that phone never die (software)
Click to expand...
Click to collapse
Did what you said but nothing happens
kayyappan said:
Are you able to connect to the phone via Vysor, either via Chrome browser or as a standalone app on Windows PC when the you do not see anything on the phone screen? Please post if Vysor install goes thru successfully. Hope your developer options/USB debugging are on. I assume your phone boots but may have display issues either hw or sw.
Click to expand...
Click to collapse
Phone gets recognized but not long enough to do anything (windows makes sound but doesn't install anything and doesn't show up in device manager)
try this guide
https://www.gizmochina.com/2016/11/20/leeco-x820-max-2-super-unbrick-guide/
You have mentioned that you are able to see the device in recovery and fastboot till you release the buttons - does this mean if the buttons are held say in fastboot mode you are able to see the device via "fastboot devices" or in recovery the twrp screen or nothing ever shows up at all? Are the buttons clicking properly? Check individually to make sure - particularly the power button. Does it vibrate at any point of time when you press and hold the power button? Are you able to see any backlight when you say the screen is on?
If there no backlight shine a torch or sunlight from the side of the screen to see anything at all on the screen.
Vysor reports apk not installed when it attempts to download from PC to phone but fails. With Vysor you will have two windows one showing status of phone - this is the main window. The other is the mirrored one - that of the phone when you click view on the main window. I forgot that the phone requires approval to install the apk. Please see the attached thumbnails. Keep touching the screen about 3 cms up from the bottom of the screen (not the phone) to see any change. Hope your touch works.
I know it is quite frustrating to try a number of things. I recently went thru the same on Galaxy S4 to make sure the phone but for the screen works OK prior to ordering the screen. Besides in my case developer options was disabled and touch also did not work. It took about a week of learning and trying to see something on Vysor. I never have used a Sam phone till that time this broken phone was handed over to me.
After a lot of trying i found out that when i keep pressed power + vol down or vol up while connected to pc and device is off it gets recognized as
qualcomm hs-usb qdloader 9008 long as i keep the keys pressed so i tried the flashone method but it just says could not connect
Are Qualcomm drivers loaded on your computer? I have not used flashone. I used QPST to see if phone is connected. I am not sure if they are same.
kayyappan said:
You have mentioned that you are able to see the device in recovery and fastboot till you release the buttons - does this mean if the buttons are held say in fastboot mode you are able to see the device via "fastboot devices" or in recovery the twrp screen or nothing ever shows up at all? Are the buttons clicking properly? Check individually to make sure - particularly the power button. Does it vibrate at any point of time when you press and hold the power button? Are you able to see any backlight when you say the screen is on?
If there no backlight shine a torch or sunlight from the side of the screen to see anything at all on the screen.
Vysor reports apk not installed when it attempts to download from PC to phone but fails. With Vysor you will have two windows one showing status of phone - this is the main window. The other is the mirrored one - that of the phone when you click view on the main window. I forgot that the phone requires approval to install the apk. Please see the attached thumbnails. Keep touching the screen about 3 cms up from the bottom of the screen (not the phone) to see any change. Hope your touch works.
I know it is quite frustrating to try a number of things. I recently went thru the same on Galaxy S4 to make sure the phone but for the screen works OK prior to ordering the screen. Besides in my case developer options was disabled and touch also did not work. It took about a week of learning and trying to see something on Vysor. I never have used a Sam phone till that time this broken phone was handed over to me.
Click to expand...
Click to collapse
It doesn't stay long enough in recovery or fastboot to do anything it shuts off after a few seconds even with the buttons pressed after that it just shows a black screen
Phone vibrates when i press power and shows leeco logo (not os logo) and after 1-2 seconds screen goes black and phone vibrates again and shows leeco logo again and just continues looping
if i try to press power + vol up normally it goes into recovery but as soon as recovery is loaded screen goes black (screen on just doesn't show anything) the same goes for fastboot if i press power + vol down it loads fastboot but after 1-2 seconds screen goes black
if i keep pressing keys the phone just stays longer in recovery/fastboot but only 4-5 seconds
I assume you have adb and fastboot. Since you say the screen remains on when booting to recovery open a command prompt at the directory where adb is and issue a command "adb devices" without quotes. Does it just exit without showing any device or throws up some error? Try this irrespective of the black screen.
Have you looked at and tried what is given by @HTC-TYTN2 at post #8? It is for Le Max 2 and you will find a link to Quallcomm drivers too. Do not bother that the link mentions X820 even your Max 2 is 821, 829, etc.
since it happened after charging, you might want to check your cable and battery. best is to get a cheap usb multimeter.
Gesendet von meinem LEX820 mit Tapatalk
I too thought it could be the battery based on that's the screen goes off. But he also mentioned that the screen remains on but nothing to be seen after a short while. Wanted to suggest slow speed charging probably via a laptop usb as I'm not sure if he used high speed charging resulting in battery issue.
Did you solve the problem?
My phone just died completely! No response at all anymore. I'm contacting the seller now to send the phone back.
Looks like it is a hardware defect! A pretty odd one but nothing i can do anymore. I send it back and post what the problem is as soon as get any information.
Thanks to everyone who tried to help!
Tsoler said:
My phone just died completely! No response at all anymore. I'm contacting the seller now to send the phone back.
Looks like it is a hardware defect! A pretty odd one but nothing i can do anymore. I send it back and post what the problem is as soon as get any information.
Thanks to everyone who tried to help!
Click to expand...
Click to collapse
Try this:
https://www.androidfilehost.com/?w=files&flid=136823
download file, unzip, open folder, connect phone to USB via fastboot ( phone off phone + hold volume -) . Click to the flash app in your PC. The app should find the phone. Confirm TWRP problem -NO and start flash.
Drivers must be installed.
Drivers here.
https://uloz.to/!A6B4AmEVx87S/adbdriverinstaller-exe
I can, pass the cuoco rom by qfil? Another type of flash, because I can not access recovery and twrp ?, only by fastboot
RaphaBraga23 said:
I can, pass the cuoco rom by qfil? Another type of flash, because I can not access recovery and twrp , only by fastboot
Click to expand...
Click to collapse
Try this via fastboot mode.:
https://www.androidfilehost.com/?w=files&flid=136823
download file, unzip, open folder, connect phone to USB via fastboot ( phone off phone + hold volume -) . Click to the flash app in your PC. The app should find the phone. Confirm TWRP problem -NO and start flash.
Drivers must be installed.
Drivers here.
https://uloz.to/!A6B4AmEVx87S/adbdriverinstaller-exe
Noticed quite a few threads re this, have had the prob myself.
Found a simple fix, while trying different things...
Hold ALL buttons down at once (vol dn + vol up + pwr button). Keep them held down for about a min or two. Phone will respond and you'll be able to shut it off. It takes a while to respond.
Cheers
Thank you!
I've added this to the US998 Pie KDZ thread. That KDZ is very wonky. It's the only Pie people have problems flashing. Probably because LG has not yet released Open Market US998 and the one we are using is technically for U.S. Cellular US998.
I had no trouble flashing it myself -- on my backup V30+(former LS998) going straight from Nougat (never updated, it was my backup phone) to Pie through Dev Patched LGUP Refurbish mode. But lots of other people seem to have problems.
On my daily phone, I'm still on rooted stock Oreo with Magisk and Xposed mods.
AsItLies said:
Noticed quite a few threads re this, have had the prob myself.
Found a simple fix, while trying different things...
Hold ALL buttons down at once (vol dn + vol up + pwr button). Keep them held down for about a min or two. Phone will respond and you'll be able to shut it off. It takes a while to respond.
Cheers
Click to expand...
Click to collapse
Hi, @AsItLies, I have tried but my phone still keeps bootloop, so could you please describe it more detailed? Can you enter fastboot or rec then? If possible, please come to see this: Help! bootloop per 5 sec, cannot enter rec, download or fastboot
zacox123 said:
Hi, @AsItLies, I have tried but my phone still keeps bootloop, so could you please describe it more detailed? Can you enter fastboot or rec then? If possible, please come to see this: Help! bootloop per 5 sec, cannot enter rec, download or fastboot
Click to expand...
Click to collapse
I think it's pretty clear, what I did and it worked in my situation(s):
There are 3 buttons right? Vol up, Vol dwn, and pwr.
Press all 3, at the same time, keep them pressed until the phone responds. It can take quite a while.
The last time I used this was after flashing LOS17, but then flashed a 19.x version of Magisk... (that's the wrong version of Magisk for Q Roms btw), resulting in phone stuck on boot logo, wouldn't budge.
I honestly have never tested exactly 'how long' it takes to respond, just that it does eventually respond and are then able to get to recovery etc. I can say time wise, if you hold them down and no response after a few minutes, then it's probably not going to work in your situation.
good luck
AsItLies said:
I think it's pretty clear, what I did and it worked in my situation(s):
There are 3 buttons right? Vol up, Vol dwn, and pwr.
Press all 3, at the same time, keep them pressed until the phone responds. It can take quite a while.
The last time I used this was after flashing LOS17, but then flashed a 19.x version of Magisk... (that's the wrong version of Magisk for Q Roms btw), resulting in phone stuck on boot logo, wouldn't budge.
I honestly have never tested exactly 'how long' it takes to respond, just that it does eventually respond and are then able to get to recovery etc. I can say time wise, if you hold them down and no response after a few minutes, then it's probably not going to work in your situation.
good luck
Click to expand...
Click to collapse
Oh, I'm just a little confused if you are talking about powering off/shutting down the phone entirely or instead changing the status of logo sticking and then shutting off with extra operation. My phone was suffering automatic reboot per 5 second, so I cannot recognize any other response than that. Thanks for your patience, but I just want to know something more to see if this method works when the phone is almost bricked. It seems you could enter rec or at least download mode, so maybe you had performed force reboot.
Hope further confirmation.
zacox123 said:
Oh, I'm just a little confused if you are talking about powering off/shutting down the phone entirely or instead changing the status of logo sticking and then shutting off with extra operation. My phone was suffering automatic reboot per 5 second, so I cannot recognize any other response than that. Thanks for your patience, but I just want to know something more to see if this method works when the phone is almost bricked. It seems you could enter rec or at least download mode, so maybe you had performed force reboot.
Hope further confirmation.
Click to expand...
Click to collapse
Hmmm I think you may be over thinking this a bit. All that happens (for me) is the phone responds (it gets out of the loop). Then, do whatever you want (shut down, recovery, etc etc).
I wouldn't suggest trying to reboot system again, as you already know that won't work...
All I can say is, if you tried the above and held the buttons, and nothing happened, then I don't know what else you can do. Sorry. Hopefully you can find a way.
Just in case someone is having problems entering download mode while in this bootloop, I'll explain how I applied AsltLies method:
First I held all buttons at the same time, no matter how many times the phone restarted, I still held them
After a while, a white screen with the MEID or IMEI info showed up, this is when the phone stopped bootlooping and I released the buttons.
Then, I CONNECTED the phone to the pc, after that I held VOL UP+POWER BUTTON, this would make the screen go black eventually, and when that happened, I inmediately released the power button but not the VOL UP button, and the phone entered into fully working download mode.
I hope this helps someone.
Dr_Roo said:
Just in case someone is having problems entering download mode while in this bootloop, I'll explain how I applied AsltLies method:
First I held all buttons at the same time, no matter how many times the phone restarted, I still held them
After a while, a white screen with the MEID or IMEI info showed up, this is when the phone stopped bootlooping and I released the buttons.
Then, I CONNECTED the phone to the pc, after that I held VOL UP+POWER BUTTON, this would make the screen go black eventually, and when that happened, I inmediately released the power button but not the VOL UP button, and the phone entered into fully working download mode.
I hope this helps someone.
Click to expand...
Click to collapse
Thanks. Added your notes to the Recovery Post in US998 Pie KDZ thread.
https://forum.xda-developers.com/showpost.php?p=81728547&postcount=641
dr_roo said:
just in case someone is having problems entering download mode while in this bootloop, i'll explain how i applied asltlies method:
First i held all buttons at the same time, no matter how many times the phone restarted, i still held them
after a while, a white screen with the meid or imei info showed up, this is when the phone stopped bootlooping and i released the buttons.
Then, i connected the phone to the pc, after that i held vol up+power button, this would make the screen go black eventually, and when that happened, i inmediately released the power button but not the vol up button, and the phone entered into fully working download mode.
I hope this helps someone.
Click to expand...
Click to collapse
thank you so much omg lifesafer