I have lg g2 sprint version. I have unlocked it by following a tutorial on youtube. On the ui there was a message that there is software update and i tapped to install it, but it was stuck on fastboot mode started udc_start() so i followed tutorial from a forum and fastfbooted boot aboot recovery and laf, but forgot to run fastboot reboot and turned off and on the phone. Now when I try to start the phone it shows the lg logo and after that only the led is flashing no matter if it's charging or not. Any ideas what to do? I have plugged it in to power it, but I am not sure whether it's charging now.
I can enter in download mode by pressing volume up and power button, but I don't have pc near me to try to flash to stock.
lolopopolo said:
I have lg g2 sprint version. I have unlocked it by following a tutorial on youtube. On the ui there was a message that there is software update and i tapped to install it, but it was stuck on fastboot mode started udc_start() so i followed tutorial from a forum and fastfbooted boot aboot recovery and laf, but forgot to run fastboot reboot and turned off and on the phone. Now when I try to start the phone it shows the lg logo and after that only the led is flashing no matter if it's charging or not. Any ideas what to do? I have plugged it in to power it, but I am not sure whether it's charging now.
I can enter in download mode by pressing volume up and power button, but I don't have pc near me to try to flash to stock.
Click to expand...
Click to collapse
The situation after a couple restarts is:
When I put to charge the lg logo appears and the led is flashing from yellow to blue
if I hold down and power button it says "Recovery mode. Loading..." and nothing happens
If I hold up and power button it enters download mode
Can I charge the phone in order to flash it to stock?
p.s. I am turning it off by holding the power button for ~20 sec
Ok so here's what happened.
Couple days ago I mistakenly selected "install now" while attempting to postpone the OTA on my VS980. Phone was rooted on stock ROM via stump root and I had not installed a custom recovery yet.
Phone then would only show the LG screen and display an error. No download mode or recovery.
So I utilized a VM running Ubuntu and pushed the sdl1, aboot, rpm, tz and TWRP 2.7 to the phone.
upon restart of the phone It would only start up into fastboot mode. The only other thing it would do is bring up the hardware key mode ( done by pressing vol-, pwr, vol+ at the same time)
Phone would report two errors upon being plugged into the computer and the computer only recognizes the phone as an adb device in device manager
"EP1/out FAIL nfo=40pg0=f910700"
"usb_read() transaction failed"
So I installed the adb on windows and in terminal on Ubuntu. I also installed the unified LG drivers, SDK and the google USB drivers. I now get the same error messages but the fastboot mode now constantly resets.
here is what it goes through
"fastboot mode started"
"reset"
"portcharge"
"fastboot: processing commands"
"reset"
"EP1/out FAIL nfo=40pg0=f910700"
"portcharge"
"usb_read() transaction failed"
"fastboot: oops!"
"fastboot: processing commands"
"reset"
"EP1/out FAIL nfo=40pg0=f910700"
"portcharge"
"usb_read() transaction failed"
"fastboot: oops!"
"fastboot: processing commands"
this goes on and on....
any ideas on where to go from here?
You could try pushing fal.img like you've pushed those other files, rather than using the fastboot.
Id love too, but my comp isn't recognizing the phone when plugged in
Were you in bulk mode originally when you wrote the partitions to the phone? If so, i'm surprised you can't enter twrp. Just to rule out and error, be sure you're holding down power for no less than 15 seconds to power off the phone all the way. Then press and hold both volume down and power simultaneusly until the lg logo comes up. Then quickly release both buttons and immediatly press and hold them both again until the factory reset screen comes up. Accept factory reset to enter twrp.
If that is all a rehash, so be it. Just want to make sure you're using the correct method. Many people fail to hold down power long enough on the initlal shutdown making all the steps after that a moot point. Also you don't want to be connected to usb when doing the above procedure.
I was using CM 13, and flashed "twrp-0.8.9.5-d802-bump-blastagator-signed.zip" over 2.8.7.3 for my LG G2 D802, then I rebooted into recovery, got new theme and all those stuff as 0.8.9.5 should have. Everything was OK, but right after flashed "bootstack-d802-LP_30d-Bump-signed" for install Cloudy G3 3.3, my phone turns off, so i decided to enter in recovery mode again. Got this: "Permanently Erase User Data & Reset Settings? Press Power key to confirm, and any other key to cancel". So I pressed power button and this message came "Are you sure you want to continue with erase? Press Power key to confirm, and any other key to cancel". Pressed power again and "Facory reset processing..." message appears for a second, then my screen turned black (not off, just black). Now i can't boot into recovery, just download mode, but can't install firmware via kdz because flash tool stuck at 2%. What should I do to fix this? Please help!
PS: Sorry for my bad english.
Edit: When I try to enter in recovery mode (failing into that black screen) and connects phone to my pc through usb, pops up multiple windows asking to format all my "corrupted mobile partitions" (screenshot: i.imgur.com/gMX2f7u.png).
7Potters said:
I was using CM 13, and flashed "twrp-0.8.9.5-d802-bump-blastagator-signed.zip" over 2.8.7.3 for my LG G2 D802, then I rebooted into recovery, got new theme and all those stuff as 0.8.9.5 should have. Everything was OK, but right after flashed "bootstack-d802-LP_30d-Bump-signed" for install Cloudy G3 3.3, my phone turns off, so i decided to enter in recovery mode again. Got this: "Permanently Erase User Data & Reset Settings? Press Power key to confirm, and any other key to cancel". So I pressed power button and this message came "Are you sure you want to continue with erase? Press Power key to confirm, and any other key to cancel". Pressed power again and "Facory reset processing..." message appears for a second, then my screen turned black (not off, just black). Now i can't boot into recovery, just download mode, but can't install firmware via kdz because flash tool stuck at 2%. What should I do to fix this? Please help!
PS: Sorry for my bad english.
Edit: When I try to enter in recovery mode (failing into that black screen) and connects phone to my pc through usb, pops up multiple windows asking to format all my "corrupted mobile partitions" (screenshot: i.imgur.com/gMX2f7u.png).
Click to expand...
Click to collapse
try SKRTOOLS click on my signature and go into tools sections .
Hi,
I have a nexus 4 that is stuck on opening animation and won't go to fastboot\recovery.
(a weight fell on it a long time ago. Worked for the next 3 days then died.)
Situation now is that it is stuck on the opening animation (lollipop) when turned on.
When trying to go to fastboot using volume up+down+power I get a blinking red light (volume up\down only with power button only resets the device or turns it off.)
Computer recognizes the device and I can see it in ADB devices while stuck on opening animation, but it says "unauthorized" so I can't use "adb reboot recovery" command.
Trying to press up+down+power while connected to computer gives solid red light and repetitive "device connected" sound from the computer every 1 sec.
Phone was never rooted or flashed in any way.
Any idea what I can do? I don't mind restoring factory image or factory reset.
Thanks to anyone who tries to help in advance
Well, I did it this time.
In a valiant attempt to install a custom ROM, I erased every partition using fastboot,
Code:
fastboot erase system
fastboot erase boot
fastboot erase userdata
fastboot erase recovery
fastboot erase cache
Now what I meant to do here was flash a recovery, using
Code:
//fastboot flash recovery TWRP.img
but repeating this so many times over the last 48 hours, I did not do above and instead went quickly right into below,
Code:
fastboot reboot
The system rebooted as I told it to ... right into a black void of nothing. Now their is no 'recovery' image and no 'bootloader' image ... the phone is hard bricked, won't turn on at all, dead. I was so close to getting to the custom ROM! Is there any chance to get it back into recovery mode? or have I learned a $350 lesson?
Edit: Further research indicates it may be possible to force the system into fastboot using a USB jig. Has anyone tried this method?
apsommer said:
Well, I did it this time.
In a valiant attempt to install a custom ROM, I erased every partition using fastboot,
Code:
fastboot erase system
fastboot erase boot
fastboot erase userdata
fastboot erase recovery
fastboot erase cache
Now what I meant to do here was flash a recovery, using
Code:
//fastboot flash recovery TWRP.img
but repeating this so many times over the last 48 hours, I did not do above and instead went quickly right into below,
Code:
fastboot reboot
The system rebooted as I told it to ... right into a black void of nothing. Now their is no 'recovery' image and no 'bootloader' image ... the phone is hard bricked, won't turn on at all, dead. I was so close to getting to the custom ROM! Is there any chance to get it back into recovery mode? or have I learned a $350 lesson?
Edit: Further research indicates it may be possible to force the system into fastboot using a USB jig. Has anyone tried this method?
Click to expand...
Click to collapse
When you plug it in while holding volume up what happens?
TheVan28 said:
When you plug it in while holding volume up what happens?
Click to expand...
Click to collapse
Nothing. LED flashes red every few seconds. The same response if plugging it in without holding volume up. Along these same lines, holding the power button on for a few seconds causes the small vibration haptic feedback to occur as if it is turning on normally ... but nothing happens the phone remains dead. Similarly, holding volume down and the power key causes a small vibration haptic feedback as it was booting into recovery ... but nothing happens the phone remains dead. I haven't seen anything on the screen appear, or the phone turn on it any way, since executing the fastboot sequence previously described.
Whatever you did, you should still be able to enter in flash mode and flash a stock firmware. And by this I mean full stock firmware, not a ROM.
Sent from my E5823 using Tapatalk
Ilko said:
Whatever you did, you should still be able to enter in flash mode and flash a stock firmware. And by this I mean full stock firmware, not a ROM.
Sent from my E5823 using Tapatalk
Click to expand...
Click to collapse
Ok, that would be great. I would be thrilled to get the stock ROM back, at this point getting the phone to turn on at all would be a victory! Would you please describe precisely how to do enter flash mode with the phone in the current state? To reiterate, the phone will not turn on in any way (normally, or volume down + power to boot into recovery). The only life in the device is a slow blinking red LED when it's plugged in, and a quick vibration after holding the power button. The screen has not turned on in any way, or the LED shown any color other than red, since executing the fastboot sequence previously described.
hold power button + volume up and to force shutdown
and then hold volume up (or down, i don't quite remember) while connecting it to a pc (hold the button while connecting the usb cable).
If the led turns green or blue, congrats
The power key has nothing to do in this context. It is used only to boot into recovery or force OFF.
While holding VOL ↑, plug the USB cable to your PC to enter into fastboot mode (blue light)
While holding VOL ↓, plug the USB cable to your PC to enter into flash mode (green light, or maybe nothing)
TheVan28 said:
hold power button + volume up and to force shutdown
and then hold volume up (or down, i don't quite remember) while connecting it to a pc (hold the button while connecting the usb cable).
If the led turns green or blue, congrats
Click to expand...
Click to collapse
Nothing. Device still unresponsive as described.
does your PC detect the device ? (new device sound notification)
Ilko said:
does your PC detect the device ? (new device sound notification)
Click to expand...
Click to collapse
No, the PC does not currently detect the device. All drivers are correctly installed as the phone was recognized accurately prior to the described fastboot sequence.
This is weird. I already erased everyting via fastboot too a while ago, and I could still flash it.
Just to be sure.... unplug all other "smart device" before anything (drivers can't handle more than one device at a time when it comes to FB or flash mode). Open the device manager and let it to the foreground. While you hold the vol down key, plug it and keep holding it until the device is detected. Don't expect any reaction on phone's screen, it remains OFF in both fastboot and flash mode. So, if the device manager reacts, you win.
Ilko said:
This is weird. I already erased everyting via fastboot too a while ago, and I could still flash it.
Just to be sure.... unplug all other "smart device" before anything (drivers can't handle more than one device at a time when it comes to FB or flash mode). Open the device manager and let it to the foreground. While you hold the vol down key, plug it and keep holding it until the device is detected. Don't expect any reaction on phone's screen, it remains OFF in both fastboot and flash mode. So, if the device manager reacts, you win.
Click to expand...
Click to collapse
I'm getting something here which is very encouraging! Executing your sequence causes the device manager to blink (refresh) as if it sees something, however no new devices are recognized in the tree. The phone LED goes to a solid green, reminiscent of a fully charged battery, stays on for about 30 seconds, briefly blinks red and then back to green, etc. The device manager is certainly reacting here it just doesn't recognize the device.
So here we are, you win. Because you have the "two", detection and green led. And if this state goes off after a certain time, it is normal. There is a kind of countdown and the device quits that mode if nothing is sent to it. You should be able to flash a firmware now with flashtool software.
Just ensure you have proper drivers installed properly (WinUSB drivers need to turn signature verification OFF before or Windows will block the installation)
Ilko said:
So here we are, you win. Because you have the "two", detection and green led. And if this state goes off after a certain time, it is normal. There is a kind of countdown and the device quits that mode if nothing is sent to it. You should be able to flash a firmware now with flashtool software.
Just ensure you have proper drivers installed properly (WinUSB drivers need to turn signature verification OFF before or Windows will block the installation)
Click to expand...
Click to collapse
Unbelievable! You saved me! I'm back up with the stock ROM and peace of mind to attempt the custom ROM process again. Saved me $350 ... thank you!!
That's great : )
It is almost impossible to hard brick a Xperia. If something goes wrong, remember flashtool ^^