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.
Related
I have a phone I am fixing for a friend, so I don't have a complete accurate history of what happened, so please bare with me.
Basically, you put the battery in and it boots right to download mode (Factory Mode), no power button required. I can then reboot it using the power, hold down the Vol-Down button and then I am prompted if I want to enter D/L mode, in which you can use Vol-Down to cancel and it boots like normal.
I have tried the following, nothing fixes it!
Factory Wipe
Root using CF-Auto Root
Every Key Combination Possible on Boot
Odin Stock Install
Kies Upgrade (just stalls on that)
It was not rooted when I got it, and now it is. I haven't installed any recovery yet, but am willing too. It has possible water damage, so it ain't going back to the store anytime soon. I can't even get USB Debugging to appear that it is connected, nor will ADB recognize it. But the USB is working and read/writing.
This isn't my first time working with this sort of stuff, I am just at my wits end, plus I'm a Sony/HTC/LG person, so if there is something I am missing with this wonderful(ly crappy) bootloader, let me know.
Thanks in advance!
shroomun said:
I have a phone I am fixing for a friend, so I don't have a complete accurate history of what happened, so please bare with me.
Basically, you put the battery in and it boots right to download mode (Factory Mode), no power button required. I can then reboot it using the power, hold down the Vol-Down button and then I am prompted if I want to enter D/L mode, in which you can use Vol-Down to cancel and it boots like normal.
I have tried the following, nothing fixes it!
Factory Wipe
Root using CF-Auto Root
Every Key Combination Possible on Boot
Odin Stock Install
Kies Upgrade (just stalls on that)
It was not rooted when I got it, and now it is. I haven't installed any recovery yet, but am willing too. It has possible water damage, so it ain't going back to the store anytime soon. I can't even get USB Debugging to appear that it is connected, nor will ADB recognize it. But the USB is working and read/writing.
This isn't my first time working with this sort of stuff, I am just at my wits end, plus I'm a Sony/HTC/LG person, so if there is something I am missing with this wonderful(ly crappy) bootloader, let me know.
Thanks in advance!
Click to expand...
Click to collapse
If you can hold the vol-down and home button when you boot it up and get into Odin mode you should be about to flash the stock MD5 for your phone. Stock Canadian Odin files here:
http://forum.xda-developers.com/showthread.php?t=2269304
Also make sure to use the lastest version of Odin, 3.07 I believe. After you are done flashing with Odin you will have to boot into Recovery (vol-up when booting) and do a factory reset. This has always fixed any boot problems with my phone.
Jdiesel87 said:
If you can hold the vol-down and home button when you boot it up and get into Odin mode you should be about to flash the stock MD5 for your phone. Stock Canadian Odin files here:
http://forum.xda-developers.com/showthread.php?t=2269304
Also make sure to use the lastest version of Odin, 3.07 I believe. After you are done flashing with Odin you will have to boot into Recovery (vol-up when booting) and do a factory reset. This has always fixed any boot problems with my phone.
Click to expand...
Click to collapse
So did you go into settings, more, developer mode to check usb/debug?
USB debugging isn't required to flash the Odin MD5. One thing I did notice is that you should boot into Odin download mode before connecting your USB cable. I was having issues with Odin not detecting my phone and waiting to connect the USB cable solved that.
Sent from my Nexus 7 using xda app-developers app
sloanster said:
So did you go into settings, more, developer mode to check usb/debug?
Click to expand...
Click to collapse
Duh...
I was referring going to adb fastboot
see the thing is that flashing did work fine, it just didn't fix the problem. I guess in Samsung terms I am stuck in Odin download mode when turning the phone on. This is why I wanted to see of I could push some standard reboot command via adb to see of it would "jig" it into place, but no matter what I try it always boots into download mode first.
and yes, I did turn on usb debugging
shroomun said:
see the thing is that flashing did work fine, it just didn't fix the problem. I guess in Samsung terms I am stuck in Odin download mode when turning the phone on. This is why I wanted to see of I could push some standard reboot command via adb to see of it would "jig" it into place, but no matter what I try it always boots into download mode first.
and yes, I did turn on usb debugging
Click to expand...
Click to collapse
Could you have bent pins maybe where you plug it in? Its doing exactly what a jig would do..
TheAxman said:
Could you have bent pins maybe where you plug it in? Its doing exactly what a jig would do..
Click to expand...
Click to collapse
Nothing is wrong with the pins, USB is working fine and can be used in any other mode. I got ADB finally, I guess it was just not playing nice with me before. However, still anything I try the bloody thing still insists on booting first into download mode.
Just an update, it is still booting into download mode, tried a couple different stocks and still no good result. Anyone suggest any of the options in Odin might help work? Like F Reset Time or Phone EFS Clear?
shroomun said:
Just an update, it is still booting into download mode, tried a couple different stocks and still no good result. Anyone suggest any of the options in Odin might help work? Like F Reset Time or Phone EFS Clear?
Click to expand...
Click to collapse
I have seen this elsewhere, one guy suggested, using Keis, and it took him 2-3 times to get the stock to stick.
As far as checking those items in odin, could brick the phone. he also said, he got nowhere using odin in this situation.
Have you tried maybe flashing a recovery via odin? could be the recovery is corrupt.
what does this mean: in which you can use Vol-Down to cancel and it boots like normal. <<< Can you boot to the OS?
I can imagine your frustration here...good luck.
I did try Kies and it would keep getting stuck at 10% (I let it sit overnight) so I had no luck with that...
Have you tried maybe flashing a recovery via odin? could be the recovery is corrupt.
what does this mean: in which you can use Vol-Down to cancel and it boots like normal. <<< Can you boot to the OS?
Click to expand...
Click to collapse
Yes, I have gone from stock recovery to CMW and back to Stock and still nothing. As for you other question, yes, I can boot into Android. The downside is I can't turn the phone off unless the battery is pulled out. This is why I bought an HTC One and not an S4 lol .. thank god this isn't my phone, but it is frustrating because of all the things I've tried to do to fix it.
Hi
I tried flashing CWM Recovery on my new G2
but after flashing my phone boots and I see on the screen:
fastboot mode started
udc_start()
And it's stuck like that.
I tried downloading SDK and replacing recovery by fastboot commands, but my pc doesn't seem to recognize the phone.
After installing a usb driver I see in device manager that the driver is still not installed correctly.
I guess it's because my phone isn't loading, right? maybe it needs to be installed when Android is running?
I even tried factory reset (boot in recovery - power + vol up) but still no change
Please help me if you have an idea how, I only bought it last week and now it's bricked!
Thanks
additional information
my phone's model: D802
I downloaded the CWM image from here:
http://forum.xda-developers.com/showthread.php?p=46837114
my pc runs windows xp
thanks all
zionzakay said:
Hi
I tried flashing CWM Recovery on my new G2
but after flashing my phone boots and I see on the screen:
fastboot mode started
udc_start()
And it's stuck like that.
I tried downloading SDK and replacing recovery by fastboot commands, but my pc doesn't seem to recognize the phone.
After installing a usb driver I see in device manager that the driver is still not installed correctly.
I guess it's because my phone isn't loading, right? maybe it needs to be installed when Android is running?
I even tried factory reset (boot in recovery - power + vol up) but still no change
Please help me if you have an idea how, I only bought it last week and now it's bricked!
Thanks
Click to expand...
Click to collapse
try holding the power down for 15 seconds. phone should be completely of now. now hold volume up while plugging in usb. this should get you in download mode. now read this thread. or maybe read this thread first.
http://forum.xda-developers.com/showthread.php?t=2432476
gentlemandroid17 said:
try holding the power down for 15 seconds. phone should be completely of now. now hold volume up while plugging in usb. this should get you in download mode. now read this thread. or maybe read this thread first.
http://forum.xda-developers.com/showthread.php?t=2432476
Click to expand...
Click to collapse
thank you, but my phone is varrient-free, and I don't think any rom will work.don't see anything on the list that seems fit.
also, isn't there a way to only recover boot, and not wipe the rom entirely?
That'sa the reason why. You flashed recovery for Verizon and yours is D802 International. If you can still go to download mode, try here http://forum.xda-developers.com/showthread.php?t=2471370&highlight=brick or http://forum.xda-developers.com/showthread.php?t=2432476.
http://storagecow.eu/index.php?dir=Xda/LG+G2/Stock/ Here, choose only D802.
i Was trying to get rid of the hissing noise on my
Lg g2 D802
i had TWRP installed
I read in a trhead that flashing the dorimanx kernel should fix that problem.
So i tried flash it, but instead of flashing the D802 i flashed the D800, i know i'm an idiot :/
I had a backup stock kernel but i think that's a wrong one too, again i'm an idiot
Now my phone boots into a black screen within the left top corner:
[2800] Fastboot mode started
[2850] udc_start()
i cannot boot into twrp anymore, it's basically bricked.
Can anyone help me recover my phone? i loved that thing, you will be my hero.
i promise when this is resolved i will never mess around with roms and kernels ever agian, i'm freaking out
henny420 said:
i Was trying to get rid of the hissing noise on my
Lg g2 D802
i had TWRP installed
I read in a trhead that flashing the dorimanx kernel should fix that problem.
So i tried flash it, but instead of flashing the D802 i flashed the D800, i know i'm an idiot :/
I had a backup stock kernel but i think that's a wrong one too, again i'm an idiot
Now my phone boots into a black screen within the left top corner:
[2800] Fastboot mode started
[2850] udc_start()
i cannot boot into twrp anymore, it's basically bricked.
Can anyone help me recover my phone? i loved that thing, you will be my hero.
i promise when this is resolved i will never mess around with roms and kernels ever agian, i'm freaking out
Click to expand...
Click to collapse
Try to flash back to stock with kdz, as far as I am hearing this you kinda soft bricked it but not hard so it's still recoverable, you could also maybe try to flash your recovery back with fastboot since your in fastboot mode but I never tried that so I suggest you to go back to stock with kdz flashing
ye try enter download mode and follow this (use search) i think its volum up and connect usb to pc
http://forum.xda-developers.com/showthread.php?t=2432476
wulsic said:
Try to flash back to stock with kdz, as far as I am hearing this you kinda soft bricked it but not hard so it's still recoverable, you could also maybe try to flash your recovery back with fastboot since your in fastboot mode but I never tried that so I suggest you to go back to stock with kdz flashing
Click to expand...
Click to collapse
thank you for your response, but i am kind of noob and have no idea how to do that correctly, could you link something or explain it?
henny420 said:
thank you for your response, but i am kind of noob and have no idea how to do that correctly, could you link something or explain it?
Click to expand...
Click to collapse
Try the link above mentioned by Overclocked
OverClockeD_GR said:
ye try enter download mode and follow this (use search) i think its volum up and connect usb to pc
http://forum.xda-developers.com/showthread.php?t=2432476
Click to expand...
Click to collapse
Thank you for your reply, i tried to get into download mode, but failed every time, i can only press the power button for 5 sec and the Lg logo apears, then i get the same screen.
did this way?
Your phone must be turned off before starting the steps from this guide.
So, press power button and select “power off”.
Then, press the volume up button on your LG G2.
While you are holding the volume up button, plug in your phone’s USB cable.
Keep pressing the Volume up button until the download mode is being displayed.
Now the phone will install some drivers – it should take around 10 minutes to complete; the best will be to let your device install the mentioned drivers.
OverClockeD_GR said:
did this way?
Your phone must be turned off before starting the steps from this guide.
So, press power button and select “power off”.
Then, press the volume up button on your LG G2.
While you are holding the volume up button, plug in your phone’s USB cable.
Keep pressing the Volume up button until the download mode is being displayed.
Now the phone will install some drivers – it should take around 10 minutes to complete; the best will be to let your device install the mentioned drivers.
Click to expand...
Click to collapse
the problem is, i can't turn it off (very weird) it instantly gives me the logo for 1sec and turns back to the same screen.
you can also try this.
http://forum.xda-developers.com/showthread.php?t=2477595
just use search mate like i do now... its soft brick i think relax and you will find it many had same prob before
henny420 said:
i Was trying to get rid of the hissing noise on my
Lg g2 D802
i had TWRP installed
I read in a trhead that flashing the dorimanx kernel should fix that problem.
So i tried flash it, but instead of flashing the D802 i flashed the D800, i know i'm an idiot :/
I had a backup stock kernel but i think that's a wrong one too, again i'm an idiot
Now my phone boots into a black screen within the left top corner:
[2800] Fastboot mode started
[2850] udc_start()
i cannot boot into twrp anymore, it's basically bricked.
Can anyone help me recover my phone? i loved that thing, you will be my hero.
i promise when this is resolved i will never mess around with roms and kernels ever agian, i'm freaking out
Click to expand...
Click to collapse
I did the same thing today by accident. I still can boot into recovery tho, TWRP. Copied the correct kernel file via OTG but it just reboots the recovery and doesn't install the kernel. Have you find any solutions?
EDIT: I actually managed to flash the right kernel and the problem is now fixed. Check everything before flashing something guys, caution
================================
Solution: http://forum.xda-developers.com/one...bootloader-locked-t3212187/page2#post63494201
================================
Hello,
This afternoon, I was preparing to flash Oxygen OS 2.1 through twrp but I wanted to make a backup first. Attempting to load up twrp by holding Vol- and Power, my OPT flashed the starting frame of the boot animation for half a second before turning off. This repeated every 5 seconds. I could still boot OOS normally at this stage.
I decided to reflash twrp so as to make the backups, but on attempting to flash it, I saw that my bootloader was locked. So into fastboot mode I went, but trying to unlock it, it did the same as trying to get into recovery. As soon as I sent the command, "fastboot oem unlock", the screen went dark, flashed the starting frame for the boot animation, and promptly when dark again.
I now can't boot up normally, nor can I enter recovery. I can access fastboot mode, but I can't seem to make any changes.
I've attempted to use this solution as well as several other similar ones with no success.
I've had my OPT since 17th of August with absolutely no signs of trouble until this afternoon.
To me, it seems like it could be a hardware issue, but I'd hope it would last more than 40 days.
Any suggestions?
Thanks.
----
x-post: whirlpool, reddit
The same just happened to me, wtf
Makrilli said:
The same just happened to me, wtf
Click to expand...
Click to collapse
What were you doing before it occurred? Perhaps we can work out the cause.
GusGold said:
What were you doing before it occurred? Perhaps we can work out the cause.
Click to expand...
Click to collapse
I'm not sure what I was doing, I was going to flash different ak kernel as my wifi didn't work.
HOWEVER
I read someone suggesting if you still have bootloop after trying the qualcomm recovery tool, try booting to fastboot and use: fastboot continue
my opt booted nicely to hydrogen os and after I shut it down it no longer bootlooped and I was able to get to recovery.
I'll post this to your reddit thread too, maybe it might help somebody one day, hopefully this works for you too
Makrilli said:
use: fastboot continue
Click to expand...
Click to collapse
Mate! that worked for me too!
However... It only seems to skip the bootloop for that power on. After power off, it returns to the boot loop. I also still can't unlock the bootloader and can't access recovery.
But at least it can boot into OS with fastboot continue!
Thank you.
Weird, after the first successful boot I rebooted and a chinese menu prompted me if I wanted to unlock the bootloader, and I did.
Maybe you should try different recovery packages.
But I'm glad to hear you at least got past the boot loop
Makrilli said:
Maybe you should try different recovery packages.
Click to expand...
Click to collapse
Can't flash a new one since the bootloader won't unlock :/
I guess the phone is in working order at the moment, I just can't let it get turned off without my computer next to me...
GusGold said:
Can't flash a new one since the bootloader won't unlock :/
I guess the phone is in working order at the moment, I just can't let it get turned off without my computer next to me...
Click to expand...
Click to collapse
Nono I mean different qualcomm recovery packages, the ones with MSM8994DownloadTool, I also replaced the stock recovery in the qualcomm package with twrp just in case if that matters
Makrilli said:
Nono I mean different qualcomm recovery packages, the ones with MSM8994DownloadTool, I also replaced the stock recovery in the qualcomm package with twrp just in case if that matters
Click to expand...
Click to collapse
Ahh, do you mind linking me to the one you used?
I think I used this: https://mega.nz/#!EsNQHKab!ifATzg4rxxBniPad0iyxANqlN8cZpUx2MVWaZgEhrD4
but it might have also been this: https://drive.google.com/file/d/0B14IjYN3PtxcSlJ5aGQxX3JERHM/view?usp=sharing
It's also worth mentioning I flashed both a few times before I tried the fastboot continue command so try both a few times and see if that helps, also I replaced the stock recovery with twrp in both recovery packages before flashing.
Edit: And best of luck, I'm rather confident your OPT is going to work properly again.
Boot Loop
I got the same problem.
Phone is rooted and i can't unlock it in cmd, just reboot itself when i try it.
The only way for me to even start the OPT is to (volume+ and power), to get to fastboot mode, then run "fastboot continue" twice in cmd.
If i reboot the phone it get cought in a boot loop where i can see the logo, reboots about every 2 sec.
Is there a solution for this? I've been searching 2 for two days now.
I don't care if i have to reset the entire phone.
p3wb said:
I got the same problem.
Phone is rooted and i can't unlock it in cmd, just reboot itself when i try it.
The only way for me to even start the OPT is to (volume+ and power), to get to fastboot mode, then run "fastboot continue" twice in cmd.
If i reboot the phone it get cought in a boot loop where i can see the logo, reboots about every 2 sec.
Is there a solution for this? I've been searching 2 for two days now.
I don't care if i have to reset the entire phone.
Click to expand...
Click to collapse
And I'm guessing you have tried the qualcomm recovery tool?
And I'm guessing you have tried the qualcomm recovery tool?[/QUOTE]
I got TWRP installed but its unreachable, volume- and power ends in boot loop.
I can´t install anything when the phone is locked.
I even tried a Factory reset, boot loop and no change when i got it up again.
p3wb said:
And I'm guessing you have tried the qualcomm recovery tool?
Click to expand...
Click to collapse
I got TWRP installed but its unreachable, volume- and power ends in boot loop.
I can´t install anything when the phone is locked.
I even tried a Factory reset, boot loop and no change when i got it up again.[/QUOTE]
Yeah but the qualcomm recovery tool that we discussed on the first page?
Sent from my OPT
Makrilli said:
I got TWRP installed but its unreachable, volume- and power ends in boot loop.
I can´t install anything when the phone is locked.
I even tried a Factory reset, boot loop and no change when i got it up again.
Click to expand...
Click to collapse
Yeah but the qualcomm recovery tool that we discussed on the first page?
Sent from my OPT[/QUOTE]
I finally got my OPT working again, tried Qualcomm recovery tool, wasn't able to complete the "MSM8994DownloadTool"
So i downloaded "A2001_14_A.03_150805" in a guide from technobuzz.net/unbrick-oneplus-2/
A similar but it does a entire wipe of the phone, nothing left at all. WARNING!
But i was okey with it.
Well the phone was in Chinese when it was all done but to change language was no problem.
I finally managed to solve it on mine. I had been cautious over the past weeks to not let it run out of battery or get turned off while away from my computer as
Code:
fastboot continue
was the only way I could get past the boot loop.
My core issue to solve was that I couldn't get it recognised as the USB Diagnostic 9006 under Ports in Device Manager. I installed the driver from here manually by right clicking the /qcser/x64/qcser.inf file and selecting install from the context menu. Then, I powered off my OP2. While only holding Vol+ (not power or Vol-), I plugged in my OP2 to the computer and it was finally recognised as the 9006. Then using the recovery tool from the prior link, it installed and rebooted my OP2. The moment of truth was when it rebooted and didn't enter a boot loop!
Then with the Chinese recovery prompt, I selected the top/first option and it brought me to the welcome/first setup screen of OOS.
It wiped the internal memory, and installed OSS 2.0.2 (don't know if coincidence or not as that was my prior OS as well). Now to install twrp and update to the latest OOS hopefully without a hitch.
Happy to finally know it wasn't a hardware issue like a failed eeprom or a dud nand controller as my prior phone (Samsung Note 10.1) died to a failed nand controller as well.
Will update with news of twrp and OOS, but I feel that should go smoothly now. Thanks to the others that helped in this thread too!
Yeap, all good!
Flashed official twrp through fastboot and batch installed OOS2 through 2.1.1 patches and SuperSU. Everything working like new!
Phew.
hi can one of you guys help me out? on teamviewer? mine is stock in the bootloop and i can only get it to boot up via fastboot continue. and i cant figure out how to get it to work. i would like to go back to complete stock and no root
best Martin
gamdiiii said:
hi can one of you guys help me out? on teamviewer? mine is stock in the bootloop and i can only get it to boot up via fastboot continue. and i cant figure out how to get it to work. i would like to go back to complete stock and no root
best Martin
Click to expand...
Click to collapse
Is it recognised as a USB Diagnostic 9006 in your device manager?
Hi GusGold No its 9008
when reinstalling a ROM earlier today, I got an error 7 ... no problem. probably TWRP problems... so, i go to reboot phone to recovery to begin fresh, and now, TWRP boots, but the screen flashes blank every couple seconds, for a second, then the TWRP splash screen comes back up. blank screen, then TWRP splash screen again. never gets further than that. because I dont have an OS installed, i cannot access debugging for adb. because i deleted my OS, i cannot allow fastboot, to flash a new recovery and begin again. ..
I am broke, and cannot afford to pay for a new replacement thru insurance or to just go buy a junker phone and make do with that.
am i ****ed, or is this recoverable...? ive been searching the forums, but cannot seem to find the answer, and im starting to get nervous enough that its sorta beginning to compound my problems more than i can deal with.
edited to add again: .... battery removed + volume dn then insert battery will not enter fastboot. im about to paperweight this ****.
again edited - Sprint LS997 is phone model. no TOT'ing for me.
What about if you remove the battery, put it back in, hold volume down and then plug the usb cable?
XblackdemonX said:
What about if you remove the battery, put it back in, hold volume down and then plug the usb cable?
Click to expand...
Click to collapse
tried this. still a no-go. phone screen does not power on when trying this or any other combo of steps. LAF works, which is vol+ and plug in USB cable. odd that vol- and plug in USB cable does nothing. maybe faulty vol+ button? never had a problem with that button functioning before now. i have access to: LAF (download mode), and TWRP. However, TWRP 'flashes' off n on... i see the splash screen for a second, then screen goes blank, but still powered on. then splash screen again. rinse, and repeat. no response to touch or vol/pwr buttons. tried pulling battery upon TWRP splash hoping this clears cache, but still just same story afterwards.
would having access to fastboot even matter, since I have no OS install with which to give fastboot/adb access anyway?
elijah420 said:
would having access to fastboot even matter, since I have no OS install with which to give fastboot/adb access anyway?
Click to expand...
Click to collapse
From fastboot you can reflash TWRP which from where you can reflash the OS which would unbrick the phone.
elijah420 said:
i have access to: LAF (download mode)
Click to expand...
Click to collapse
If you have access to download mode, can't you reflash your phone using the LGUP with the backup that did in the first place?(you did a backup of the original OS right?)
elijah420 said:
tried this. still a no-go. phone screen does not power on when trying this or any other combo of steps. LAF works, which is vol+ and plug in USB cable. odd that vol- and plug in USB cable does nothing. maybe faulty vol+ button? never had a problem with that button functioning before now. i have access to: LAF (download mode), and TWRP. However, TWRP 'flashes' off n on... i see the splash screen for a second, then screen goes blank, but still powered on. then splash screen again. rinse, and repeat. no response to touch or vol/pwr buttons. tried pulling battery upon TWRP splash hoping this clears cache, but still just same story afterwards.
would having access to fastboot even matter, since I have no OS install with which to give fastboot/adb access anyway?
Click to expand...
Click to collapse
Sounds like empty or bad battery to me. When did your phone start acting up upon ya? Right after root or you had it working with root etc before u ended up into such situation.
Also, as XblackdemonX pointed out, you can still use LGUP to stock.
I'm pretty sure that happened to me. And I fixed my H990DS by flashing kdz file in download mode with LG BRIDGE.
There's a guide about how to unbrick any v20 around here.
@elijah420 What software version were you on before this started? Why does it matter? If you were on ZV7 or earlier, then you can flash a VS995 KDZ in download mode, root it, and then fix your phone. If you were on ZV8 or later, then you still might be able to salvage your phone, but you will have to run firmware from another model since you will not be able to root and flash back to Sprint firmware if you were ARB 1 or later. Better than having a totally busted phone though.
Last possibility is to use the debug firehose that I have, but that is an even bigger unknown than running firmware from another model.
-- Brian