Related
Hey Guys, could sure use your help... i updated my 10.1 le yesterday and that went thru fine. Later on i was playing and watching youtube and it sent my tablet into a boot loop and i cant seem to fix it. any help would be appreciated thanks in advance.
Mine did the same thing when i was streaming music. Not even Odin brought it back. I used adb to reboot into stock 3e recovery and wipe data/factory reset it, then used Odin to grt back to 3.0.1. Then i just redownloaded the 3.1 update. Hope that helps
LovellKid said:
Mine did the same thing when i was streaming music. Not even Odin brought it back. I used adb to reboot into stock 3e recovery and wipe data/factory reset it, then used Odin to grt back to 3.0.1. Then i just redownloaded the 3.1 update. Hope that helps
Click to expand...
Click to collapse
right now im having problems with adb listing the devices. adb is installed. it keeps saying that i need some APX drivers???
Drivers are here:
http://www.samsung.com/us/support/owners/product/GT-P7510UWYXAR
I had the same problem. This is what i did. Since I had already rooted my tablet, I already had in my laptop ADB and the driver for the tablet. If you don't have these 2 things, I suggest you go to the development section of this forum, look for the insrltructions on how to root, and download what you need.
I connected my tablet then went into cmd mode (DOS MODE), then typed adb reboot recovery. From there the tablet rebooted into recovery. I then wiped data and cache. Then I rebooted and it went fine, no more bootloop. In settings I noticed that it had reverted back to 3.0.1 so I just did update again. Since then my tablet has been smooth as butter.
Sent from my GT-P7510 using XDA Premium App
For those not too comfortable with ADB, I just installed PDAnet (for the fastboot drivers) and after booting to fastboot (holding power and the volume down button and selecting the USB symbol) I used the "fastboot -w" command in CMD.exe to wipe the device.
Its rather strange that a lot of people are having problems. Mine started after getting an error turning on the WIFI chip. Thank god for Titanium Backup's option to sync with Dropbox. Hope this helps.
kdietze3 said:
For those not too comfortable with ADB, I just installed PDAnet (for the fastboot drivers) and after booting to fastboot (holding power and the volume down button and selecting the USB symbol) I used the "fastboot -w" command in CMD.exe to wipe the device.
Its rather strange that a lot of people are having problems. Mine started after getting an error turning on the WIFI chip. Thank god for Titanium Backup's option to sync with Dropbox. Hope this helps.
Click to expand...
Click to collapse
THANK YOU!! Your suggestion of installing PDAnet saved me! I was having a hell of a time trying to get the right drivers so my computer would recognize the tablet has an adb device. After installing PDAnet, it was a cinch. Then I reflashed everything, wiped userdata and cache, and rebooted (I followed the instructions found here: http://forum.xda-developers.com/showpost.php?p=14600617&postcount=111) Now my tab is working again and I was getting ready to ship it off to Samsung so they could re-flash it for me.
Follow this steps
The steps are this:
http://forum.xda-developers.com/showpost.php?p=15084897&postcount=123
Obviously I have installed adroid-sdk and download fastboot from HTC page.
I'm one of the lucky ones who has had their I/O tab stuck in a boot loop on 3.1, and after trying the steps below, I am not getting it to work. I know I must be making a stupid mistake somewhere along the line, but essentially,
I downloaded the new image, boot, and recovery files into a directory on my hard drive;
I installed PDAnet;
I entered into fastboot on my GTab and plugged it into my PC;
I can tell that fastboot is now listed as a device (I suspect this means that the drivers are installed correctly and that it is recognizing a fastboot device);
Now when I try to run the fastboot commands suggested, I get 'fastboot' is not recognized as an internal or external command...
Stupid question, but I am supposed to run this command from cmd.exe, right? Any ideas what I am doing wrong so that the fastboot commands are not recognizable? I may need a dumbed down instruction set if there are steps I am missing somewhere...
engljeff said:
I'm one of the lucky ones who has had their I/O tab stuck in a boot loop on 3.1, and after trying the steps below, I am not getting it to work. I know I must be making a stupid mistake somewhere along the line, but essentially,
I downloaded the new image, boot, and recovery files into a directory on my hard drive;
I installed PDAnet;
I entered into fastboot on my GTab and plugged it into my PC;
I can tell that fastboot is now listed as a device (I suspect this means that the drivers are installed correctly and that it is recognizing a fastboot device);
Now when I try to run the fastboot commands suggested, I get 'fastboot' is not recognized as an internal or external command...
Stupid question, but I am supposed to run this command from cmd.exe, right? Any ideas what I am doing wrong so that the fastboot commands are not recognizable? I may need a dumbed down instruction set if there are steps I am missing somewhere...
Click to expand...
Click to collapse
Edit:
After trying just about everything, I have concluded there are two hurdles I still cannot pass. First, if I fastboot my device, and select the USB icon, my device is appearing in my windows device list. However, I cannot run any fastboot commands in cmd.exe window. Not sure why or what else is needed. Second, I successfully installed SDK and tried to enter recovery mode through ADB, but I cannot find the magic trick to have my device appear in ADB. ODINing back to stock did not make a difference. If I can get past either of these hurdles I am confident I can progress, so any suggestions are appreciated.
fastboot commands never seem to work for me. Always says waiting for device.
ericc191 said:
fastboot commands never seem to work for me. Always says waiting for device.
Click to expand...
Click to collapse
Which makes me wonder if I am doing something wrong. I can't even get fastbook command to be recognized. It's as if there is some fastboot software needed so that my pc knows what to do when I type fastboot. I hoped SDK was enough, took a stab with a fastboot.exe from htc I found on another forum, neither worked. How did you get your pc to look for your device from fastboot in the first place?
Sent from my SGH-T959 using XDA App
Hi .. I have the same problems before
I found out that the new ADB has moved the directory to "platform-tools"
This renders the fastboot useless "winapiadb.dll"(or something) file not found pop up window
I got that ridiculous bootloop issue right in the middle of the flight! thought I bought a $$$ junk lol
use the fastboot -w option to recover .. but it resets the whole tablet back to OE (original everything)
Hey guys,
So I have one of the Limited Edition Google IO Galaxy Tab 10.1's and I can't find a more updated thread than this. It seems this problem is isolated or mostly isolated to the Limited Edition tabs?
Anyways, I've read through the thread (as well as many other resources) and I just don't understand what I'm supposed to do to defeat the boot loop problem.
For me, pressing the Power and Volume up button (or Power and Volume down button) doesn't do a thing. The tablet does not respond at all. The only thing other than the boot loop is that I can get it into "upload mode" whatever that is.
This thread doesn't mention upload mode, so I don't know how to proceed. I can't seem to find anything in the manual about this sort of hard reset, nor can I find any information anywhere else.
Also, I've read this thread, and I do not have any familiarity with what the following software projects are: Odin, PDAnet, and APX Drivers. I also have not used the android SDK.
Also, in the third post chris eckman posted a link to some sort of Galaxy Tab drivers on samsung's site, which is now a broken link.
Anyways, while I'm a noob to the XDA community, I am a computer engineer, and I'm confident I won't have any trouble recovering this device. There's just so much conflicting information and alternatives methods that I'm not sure how to proceed.
It seems like a tutorial might exist out there that I have not yet found?
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Clyde_Frog said:
Hey guys,
So I have one of the Limited Edition Google IO Galaxy Tab 10.1's and I can't find a more updated thread than this. It seems this problem is isolated or mostly isolated to the Limited Edition tabs?
Anyways, I've read through the thread (as well as many other resources) and I just don't understand what I'm supposed to do to defeat the boot loop problem.
For me, pressing the Power and Volume up button (or Power and Volume down button) doesn't do a thing. The tablet does not respond at all. The only thing other than the boot loop is that I can get it into "upload mode" whatever that is.
This thread doesn't mention upload mode, so I don't know how to proceed. I can't seem to find anything in the manual about this sort of hard reset, nor can I find any information anywhere else.
Also, I've read this thread, and I do not have any familiarity with what the following software projects are: Odin, PDAnet, and APX Drivers. I also have not used the android SDK.
Also, in the third post chris eckman posted a link to some sort of Galaxy Tab drivers on samsung's site, which is now a broken link.
Anyways, while I'm a noob to the XDA community, I am a computer engineer, and I'm confident I won't have any trouble recovering this device. There's just so much conflicting information and alternatives methods that I'm not sure how to proceed.
It seems like a tutorial might exist out there that I have not yet found?
Click to expand...
Click to collapse
Ok, well if you are running a "stock" IO bootloader, then you should have fastboot and download modes accessible to you by using the volume down and power button combo.
Have you ever gotten to this menu before? If not, then you just aren't doing it right. Let go of the power button part of this combo once the samsung logo appears, and then you should see two icons appear. If you have an IO bootloader, then you are going to go into fastboot mode, and then use fastboot to get your recovery booted. Once you get CWM booted, you can flash a stock ROM, load up stock recovery and wipe this sucker back to factory, and then fastboot your CWM recovery and install Task650's latest rom and be bootloop free. Let me know if you need further help.
Alright, first things first. Yes, this tablet is 100% stock, and I've done one major Android update, but it was not the one that broke everyone's wireless.
----------
So going step by step:
you should have fastboot and download modes accessible to you by using the volume down and power button combo. Have you ever gotten to this menu before?
So, I did once get to what I believe was the "fastboot" menu. I had four options available to me, the first one was something like "repair boot process" which I selected, because I was having a boot problem. It did nothing, and now I cannot get back to that menu.
I did get to the USB upload screen once by accident, when I was trying to get back to the boot menu, but not knowing what to do at that point. I had to shut it off.
Let go of the power button part of this combo once the samsung logo appears, and then you should see two icons appear.
Which Samsung logo? If I press both the power button and volume up or down, I get nothing. Nothing happens. If I press the power button first and then two seconds later start holding down the volume button, then eventually I get the blue swirly samsung screen. At the end of that, the samsung logo is clear. But waiting a bit longer, after about 30 seconds of blank screen, a pulsing white Samsung logo comes up, and I've never known which samsung logo to stop holding the power button. I believe I've tried every combination imaginable, and none of them work.
If you have an IO bootloader Do you mean Google I/O Stock bootloader? If not, I have no idea what this is in reference to.
Once you get CWM booted No idea what that is.
you can flash a stock ROM Where do I get that?
-------------
My bootloop might be different from everyone else's. Everyone else says "shut off the device, and then turn it on with the volume down/up held down. The problem with mine is that it NEVER shuts off! So, I can only do about 2 tests per day, because the only way I can shut it off is to let the battery run dead.
Mine switches from boot loop, and if I force that off, by holding down the power button for 10-15 seconds, then it immediately boots back up into "going into upload mode, cause unknown" If I force that screen off, it boots into the boot loop, so I can never boot from a "powered off" mode, again, unless I let the battery run dead.
I've tried every button pressing boot sequence I can think of with no luck. Can't I just upload something to the device in "upload mode" ? I don't need any data off this device, I just want it to be reset back to day 1, so that I can turn it on and use it.
Thanks so much for your help. As you might imagine, this is a very frustrating problem.
bootloop
can someone please help me ,i have a samsung galaxy tab 2 10.1 ,and its on boot loop ,always showing smsung galaxy tab 2 logo,i've tried restoring factory settings ,,didn't work ,i tried to install receovery from internal sd card says not found ,some one pleeaaase send me the steps of what to do
Hello all. I'm a brand-noob (my phrase, thank you) here.
I have received a Verizon HTC Eris phone that boots to the red triangle with exclamation point (three droids on skateboards prior to the triangle screen). I have no information on what was done on this phone prior to my receiving it. I have read here that the three droids means that it has been rooted, and that the red triangle means a stock recovery is on it.
I can only "Up Volume + Power" to get this - "E:Can't open /cache/recovery/command". Other than that, I can't seem to get to anything else on the phone.
Now, upon connecting via usb to my computer (Windows 7), I can get Windows to recognize the "Android Phone", but not specifically an HTC Eris. I do not have HTC Sync installed. I have used ADB to root another phone (MyTouch), but this phone does not show up when I check for devices via "adb devices".
I am hoping someone can offer some simple steps that I can do to work towards fixing the phone. Thanks everyone for your time. !
This may help you:
http://forum.xda-developers.com/showthread.php?t=992916
Good luck.
Thanks for the reply phone_cell. I had already read/seen that post.
I cannot see any boot information at all, it shows the skateboarders, then the red triangle. The phone shows up on my computer, but only as an "android storage device". I'm not sure how I can check anything via my computer. I have installed PDAnet prior, and read that it should have installed the phone drivers. ? I installed HTCSync on a different computer and it doesn't see the phone.
If there is no way to fix this phone, then I understand. I would like to think that there are ways (standard methods ?) to check and/or re-install a phone (any phone) back from something like this. ? ...Thanks again for your time and expertise!
I was happy to try to help you. I recommend you send a PM to bftb0. If your Eris can be brought back to life, bftb0 will know what to do.
Bummer. bftb0 does not receive private messages, or at least not from me. Maybe someone could relay the forum post.
I am still digging and digging to try and figure something out. If I could get my computer to communicate properly with the phone, I'm sure I could re-install/fix the boot problem.
Anyone have ideas on how to install a usb device that's stuck in recovery?
As always, thanks thanks thanks. And thanks.
I made a post asking bftb0 to lend you a hand.
http://forum.xda-developers.com/showpost.php?p=15386610&postcount=33
Are you able to get it into fastboot mode? To do so, the phone needs to be completely off first...pulling the battery if needed. From there, first hold down the green send/call button then press and hold the red power/end button at the same time. Holding both should bring you to the fastboot screen which has three small skateboard andy's at the bottom and the word FASTBOOT highlighted in red. If you get there, post what the top two green lines say. Post #4 in the thread phone_cell gave shows an example of what you'll see. I would also try and follow bftb0's directions in post #5 about using the "Official" RUU utility to install usb drivers but make sure to stop before actually flashing anything to the phone. After that, download the fastboot tool and then with the phone connected through usb, see if the command "fastboot devices" lists your device ID.
Getting that far is promising and you can proceed with bftb0's directions in that thread to flash with HBOOT, load a recovery, hopefully eventually get a custom ROM flashed.
Hey MongooseHelix (great nick). Thanks for your reply.
No, the phone does not boot into fastboot, or anything else. There's plenty of resources here for all the different methods for booting and such. I've read hundreds of threads and pages. I've tried them all (and to success on other phones). It only gives me the recovery-stuck-ness.
The more I think about it, the more I think it has something to do with me not having this certain phone installed on my computer prior to receiving it. ? What would other people do to remedy something like that..? Find a working model to get the drivers working? Hmmm. Thanks and thanks again folks.
If you haven't already, how about installing the android-sdk(try the exe if on windows):
http://developer.android.com/sdk/index.html
Then run the SDK Manager.exe from the SDK directory. I'd download the latest SDK tools, SDK platform-tools, and the USB driver for Windows. Make sure to add the tools and platform-tools directories to your path...instructions at the end of Step 5:
http://developer.android.com/sdk/installing.html#sdkContents
With the phone on and connected through usb, see if running "adb devices" from the command prompt recognizes the Eris.
Yes, I had the android-sdk installed prior to receiving this phone. I did run it and update everything within it (per everything I researched online). But, the phone still doesn't show up via "adb devices". I feel like because the phone is stuck in recovery, it's not letting the computer do anything hardware-wise with it. ? Not sure.
Not sure what else to suggest. Without access to recovery, fastboot, or hboot along with not being able to connect through a comp, it unfortunately sounds like it might be hard-bricked. I'm certainly no expert at reviving an Eris so someone may know a way to to fix things...maybe bftb0 will come work his magic. Good luck and if I find or think of anything else I'll let you know.
The red triangle screen is indeed a splash screen for the stock recovery.
The next question is whether you are able to proceed beyond the "splash screen" and attempt to perform a "factory reset" procedure using the stock recovery menus.
There are two ways you get past the stock recovery splash screen, and it depends on which version of the stock recovery is installed on your phone have.
(1) press & hold Vol-Up+End simultaneously (with the "red triangle" splash screen showing)
or
(2) press the Home(soft-key)+End simultaneously (with the "red triangle" splash screen showing)
Do either of those cause the <2e> recovery menu to appear on the screen? If so, perform a "factory reset" using that menu, and THEN see if you can get alternate startup modes to occur (after powering off the phone before each trial):
End (only) => Does anything boot now?
VolDown+End => HBOOT
Send+End => FASTBOOT
VolUp+End => Recovery boot (red triangle screen again) **only works if HBOOT > 1.49.xxxx
Please do not say "I tried everything" in your reply. It is extremely non-specific, and conveys no information about what you actually attempted.
bftb0
Many thanks for the reply. !
With the recovery splash screen showing, upon holding "Volume Up + End (power)" I get = E:Can't open /cache/recovery/command Now, I am able to clear that message by pressing "Volume Up + End" again, however it just goes back to the recovery splash screen.
I held down Home (on the glass) + End (power) and nothing happened.
?? Any suggestions ?
Also... my reference to "tried them all" in my earlier post meant that I have tried just about every combination of simultaneous key pressing upon powering up (booting from no power) the phone. I am also familiar with the recovery menus on other phones - I have not seen it show up on this one (per my most recent post as well).
cjslugbug said:
I get = E:Can't open /cache/recovery/command
Click to expand...
Click to collapse
That message is quite normal. However, what usually happens is that the (stock) recovery <2e> menus appear immediately after that message.
I guess this suggests that there is something wrong with the phone (hardware) or the recovery.
I'll give it some thought (check this thread every so often), but I don't see an immediate way out of your situation.
bftb0
Well, I certainly appreciate the replies. Thanks!
Does
VolDown+Send+End
do anything interesting - either from a phone off condition, or when the "can't open /cache/recovery/command" message is on the screen?
Was there a (properly formatted) SD card in the phone when you performed all the prior button-pressing experiments?
Booted with "Volume Down + Send + End" = same, straight to recovery splash screen.
I then "Volume Up + End" to get "e:can't open /cache...." and tried "Volume Down + Send + End" = no changes.
I have an sd card in it that I used to root a MyTouchSlide recently. It has ClockworkMod recovery on it (update.zip). I have done every procedure I've mentioned in this thread with and without the sd card in the phone.
I just reread the whole thread.
I understand that you tried all the standard button-press-startup methods, and the only thing you can get to work (partially) is the first part of the standard recovery boot. What you didn't say explicitly is, what exactly happens when the standard button-press operations fail:
- nothing at all (screen stays black, not a single LED blips, etc)? or,
- every start sequence results in the recovery splash screen? or,
- the three skating droids appear but the screen freezes that way? or,
- other?
Here is what you are up against:
The standard recovery does not start up an "adbd" daemon, so worrying about drivers is not likely to get you anywhere: under normal circumstances, "adb" simply doesn't work with a standard recovery.
There are two exceptions to this:
(1) The (leaked) HTC "Root ROM" does start an adbd daemon (but "adb shell" won't work)
(2) The Leak-V2 recovery had a race condition that allowed less than 20% of the folks who tried it to get an adbd daemon to persist. (Search for "tereg" root). It's a huge long shot.
Whether either of these apply to you is indeterminate, as we know neither the bootloader version that is on your phone, nor the version ofthe (damaged?) recovery on the phone.
One more question, and then some straws to grasp at:
- when you plug the phone into the charger, do you see the amber/green LED light up?
- repeat every one of the "standard-button-press" sequences, but make sure that before each start sequence, you pull the battery, press all buttons, wait 10 secs, and then reinsert the battery. Long shot, but what have you got to lose?
bftb0
- what exactly happens when the standard button-press operations fail:
The three skating droids appear (for a few seconds, as per a normal-type boot is beginning) but then the screen freezes to the recovery splash screen.
- when you plug the phone into the charger, do you see the amber/green LED light up?
Yes, I see the amber/green light. The light seems to operate as if it is charging normally.
I will try your 10 + second-battery-pull-button-combinations method here in a while.
Really appreciate the thoughts/help on the matter. !!!
Hi guys, I was trying to flash a custom ROM for the first time onto my ASUS ME301T, as I was fairly sure ASUS was not going to update these devices anymore.
Anyway, now the device will not start. It will power on, and the first of the two ASUS start-up screens will appear (the non animated/static one). In the top corner, it reads "The Device is Unlocked" as was required when attempting to flash the 4.4.4 ROM. Beyond this, nothing happens. If I attempt to power down the device it simply reboots itself shortly after. The only way to turn it off is to insert a paperclip into the physical reset hole, or to let the device run out of battery.
Now before you tell me to go into recovery by holding power and volume down... I've tried that hundreds of times.. As well as power+vol up, although I don't know what that does. I cannot access recovery mode, as far as I know anyway. Further, the device is not detected by either of my computers (desktop or laptop, windows and mac) so I can't attempt to flash it through USB (unless there is a way to do this?).
The device does not heat up, the screen simply stays on the ASUS static logo. It doesn't power off unless I hold the button, and it quickly restarts. To provide context as to what I did to cause this issue.. It was working fine on its factory ROM, no issues, and I attempted to do another system reset to fix an issue I was having with TWRP. However, I accidentally selected the middle open, not RCK, not reset, but something like "boot into Linux" or something, I can't exactly remember. Anyway, like an idiot I freaked and powered off the device.. My guess is that this is was caused the issue?
Anyway, making this post here as this is my first time looking into/attempting to flash a device. Would appreciate some expert help before I use my tablet to prop up the books on my bookcase
Help me try to unbrick my tablet! (I'm not too hopeful though..)
Cheers
Hey guys im new to this thread and a website said to see if you guys could help me. Well basically I tried to make my music louder on my android and it didnt like that. Now it wont boot or go into recovery and to make things worse, i made it go into charge only mode a long time ago. Since i cant open it or view files since its on charge only mode. I think im screwed. Is there any way i can fix this? Thanks a lot for anything. I tried to hard reset and all of that but it goes into a black screen then just goes back to the LG loading screen. It basically just loops itself everytime i try to enter recovery. It gets stuck on the tracfone page. This is a straight talk phone. Its the LG Access LTE L31L. Ive looked everywhere and havent found anything that works and thought that you guys would hopefully help me. Is it just a paperweight or is it fixable? Thanks!
In the computer the phone isent reconized as anything??
I found one in a car I just bought, has the lock for PIN enabled and cannot enter phone.
Tried all the reset options found on web, nothing brings me to recovery, searched the forums here for this model phone, nothing found.
Tried Volume Down + Power, released Power when LG logo appeared for 3 seconds then pressed and held, it would reboot sometime long sometimes short, but would not enter recovery, tried both volumes up and down, volume down and home button, every combination I could find...
I had a SIM card for a tracfone that was active and wanted to see if this phone would accept it...
Any other tricks available? Computer dings that it sees the phone, but since I cannot get past PIN screen I cannot choose what function USB should be and nothing is seen in Windows Explorer.
Any LG master files to force open the phone through the PC when locked like this or ???
Sorry to hijack or open an older thread, but not much action here for this model phone...
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.