Database Users

hard bricked? vs980 NEED HELP PLEASE

hello all, im a noob and think my phone is good enough to throw in the garbage. you tell me!!
so i use my vs980 on tmobiles network and only get at best hspa so i tried to throw a tmobile stock rom on my vs980 to try and get 4g ive seen people doing it i was hesitant but did it anyway. i had a zip for a verizon kernel now the rom installed successfully but the kernel didnt i meant to try to restore a backup but accidentally hit reboot and now every time i power on my phone i get black screen
fastboot mode started
reset
portchange
reset
portchange
fastboot processing commands
cant get into twrp with two button combo cant do a factory reset, infact that has changed looks a bit different than it used to, assuming its a tmobile factory reset screen
i tried to do the kdz and tot method to return to stock aswell phones not recognized for either method
i installed ubuntu on virtual box to try and push recovery.img, laf.img, aboot.img. boot.img. etc but phones not recognized in terminals fastboot says <waiting for device> any way to get ubuntu to recognize my device? any special drivers i need?
ive searched high and low for a solution im so exausted and could really use some veterans help please help this noob out... thanks in advance for any help from you guys!!

anyone?

pete022682 said:
hello all, im a noob and think my phone is good enough to throw in the garbage. you tell me!!
so i use my vs980 on tmobiles network and only get at best hspa so i tried to throw a tmobile stock rom on my vs980 to try and get 4g ive seen people doing it i was hesitant but did it anyway. i had a zip for a verizon kernel now the rom installed successfully but the kernel didnt i meant to try to restore a backup but accidentally hit reboot and now every time i power on my phone i get black screen
fastboot mode started
reset
portchange
reset
portchange
fastboot processing commands
cant get into twrp with two button combo cant do a factory reset, infact that has changed looks a bit different than it used to, assuming its a tmobile factory reset screen
i tried to do the kdz and tot method to return to stock aswell phones not recognized for either method
i installed ubuntu on virtual box to try and push recovery.img, laf.img, aboot.img. boot.img. etc but phones not recognized in terminals fastboot says <waiting for device> any way to get ubuntu to recognize my device? any special drivers i need?
ive searched high and low for a solution im so exausted and could really use some veterans help please help this noob out... thanks in advance for any help from you guys!!
Click to expand...
Click to collapse
thats not even close to a hard brick it is in bootloader mode do not let it die keep it plugged in because if the battery dies then you have a real big problem im not sure what to do after this but i know you dont want the battery to die

well that's reassuring
Keeping phone plugged in. Now if I can get some tips as to why I cant get it to communicate with ubuntu in this bootloader mode to push the files I need. Any help anyone? Please. Where I go from here?

link - windows

Tried putting laf.IMG in your script folder bender it brought cmd to<waiting for device> my comp won't communicate with my phone for some reason. Am I missing any special drivers?

pete022682 said:
Tried putting laf.IMG in your script folder bender it brought cmd to<waiting for device> my comp won't communicate with my phone for some reason. Am I missing any special drivers?
Click to expand...
Click to collapse
Just install lg drivers - if it doesn't work then download adb drivers..
+please see the device manager for new devices and "not installed drivers"
+ look here

I will try when I get home thanks for your help so far at work no computer access. Thanks again bender I will let you know how everything goes.
bender_007 said:
Just install lg drivers - if it doesn't work then download adb drivers..
+please see the device manager for new devices and "not installed drivers"
+ look here
Click to expand...
Click to collapse

if you manage to install the driver the rest should go easy.
It's weird, on some systems it wont install the driver properly(adb) but google nexus driver installs fine.

i was hoping so
bender_007 said:
if you manage to install the driver the rest should go easy.
It's weird, on some systems it wont install the driver properly(adb) but google nexus driver installs fine.
Click to expand...
Click to collapse
so this is where were at bender....
got drivers installed, phone is being recognized...
pushed laf.img with your script...GOT DOWNLOAD MODE BACK!!yes, progress...
went to factory restore with .TOT method.....FAILED
shows PID#, IMEI#, MODEL,D801 DLL VS980 SBUV Xdabbeb's vs98024a 1.1.1 11 SWOV Xdabbeb's vs98024a 1.1.1 11 device doesn't match
ideally i would love to just turn this vs980 into a d801 stock kitkat by pushing all nessassary d801 files would that work what would be my options here?

How do i fastboot flash open recovery twrp IMG?

Ultra brick G2 vs980! T_T
Good night lords of XDA!
I come to you after exhausting all that I could find and try, hope you can enlighten me, you would save a new G2 that is about to become a gleaming brick:
Summary: I have in hand a Verizon LG G2 vs980, with the intention of using it in Spain. After a bad flash a ROM for a different model, you could not access recovery mode or download mode, only fastboot.
Thanks to this great tutorial, I could flash by ADB and fastboot files an official ROM for this G2, but after a correct process, the G2 restarted and only shows "Security error" before shutting ...
I still do not have access to recovery or download, and now not to fastboot. Only allows me to access the screen "Factory reset", but in doing nothing changes.
How could re-flash a recovery or something like that allows me relive my G2?
Thank you very much in advance. You are my salvation. XD
PS: I apologize for any clerical error or misused term. I do not usually write in English.
Click to expand...
Click to collapse
Sorry, wrong thread. XDD

Hard bricked my LG2, help?

Hi guys. I did something very stupid and by mistake flashed wrong version of AutoRec on my LGD802. No I am stuck od "fast mode started", what ever I do. Is there any help for that device or I just need to take it to service and pay the bill. Thanks. Very stupid mistake.

Tried going back to stock?
You know, there is not much we can do without details.

robogo1982 said:
Tried going back to stock?
You know, there is not much we can do without details.
Click to expand...
Click to collapse
(860) Fastboot mode started
(910) udc start
And that comes after everything, fastboot or download mode or white screen. Windows 7 cant recognise it, I installed drivers before connecting G2 but under SM buss controller there is nothing recognized.
I would try to going back to stock but I dont know how and I am afraid that that will be hard without windows recognizing G2. Sry my english is not so great. I am from Croatia. Thanks for very fast response.

roki4 said:
(860) Fastboot mode started
(910) udc start
And that comes after everything, fastboot or download mode or white screen. Windows 7 cant recognise it, I installed drivers before connecting G2 but under SM buss controller there is nothing recognized.
I would try to going back to stock but I dont know how and I am afraid that that will be hard without windows recognizing G2. Sry my english is not so great. I am from Croatia. Thanks for very fast response.
Click to expand...
Click to collapse
I tried few way to go back to stock but nothing works. G2 is recognized like Android phone but like USB Modem Phone ADB so I am stuck. I am not even sure that battery is charging and I could end up with paper weight soon.
I get in download mod for like half of the second and then Fastboot mod started takes over. Two big problems no download mod and G2 in windows 7 64. Hard reset doesn't work neither, Fastboot takes over again. How stupid i was not to look what file is downloading, first is the newest I thought in my stupid head.

if while plugged into the pc using adb devices it shows up we can save the phone

XxZombiePikachu said:
if while plugged into the pc using adb devices it shows up we can save the phone
Click to expand...
Click to collapse
Thanks for giving me some hope. I never planned to root that phone until I saw that great Xdabbebs Camera Mod. Rooted with no problems and that screwed it up like a overexcited 10 year old. I still got warn out GS3 for usage, works fine but looks like crap but that G2 screen all black hurts a lot.

roki4 said:
Thanks for giving me some hope. I never planned to root that phone until I saw that great Xdabbebs Camera Mod. Rooted with no problems and that screwed it up like a overexcited 10 year old. I still got warn out GS3 for usage, works fine but looks like crap but that G2 screen all black hurts a lot.
Click to expand...
Click to collapse
well like I mentioned if it is seen by adb devices we should be able to be fixed by flashing the correct partitions with fastboot

3 in the morning here. Thanks. I look info it tomorrow
Sent from my GT-I9300 using Tapatalk

roki4 said:
3 in the morning here. Thanks. I look info it tomorrow
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
ok then

Something new on the screen. I ve installed ADB drivers and no I have"fastboot OEM unlock" and "partition get size 104576 bytes" and it stands there. ADB still can find device and G2 is still shown as Android phone, USB modem ADB port.
Also got hardware key control mode

I ve got download mode thansk to this
http://uncle-yakuza.jouwweb.nl/lg-g2-fast-boot-menu-fix
Guys i really need tome help what to do next. How to flash from download mod, link please.. I got KDZ

back to stock guide
Sent from my Potato powered G2 D800

I did it after everything that could go wrong did. Thanks for your support.
Link I posted above works if someone is stuck in fastboot with nothing else..
On more thing. Phone is now unrooted. At least root checker says so. That is normal I suppose.

[Q] NEXUS 4 Stuck in bootloop + PC wont recognize phone

I changed a cracked screen on a Nexus 4. I have done this before with no problems. It is not rooted and locked to a carrier. Now it is stuck in bootloop.
Now the real problem is that even though the phone will take a charge, when I connect it to a PC it the PV doesnt see the phone and it doesn't show up in file folders or in Nexus Toolkit.
So I cannot access ADB either since the PC doesn't see the device and same with Nexus Toolkit.
I can boot into recovery mode but it goes to Android man on back with red flag and "No Command Found" message.
I have spent a week on this. Who out there knows what the hell I can do. I have thought about swapping out the charger port to see if thats why the pc isnt seeing the phone...I am stumped. Help would be very appreciated folks.
Thanks

Wallstud44 said:
I changed a cracked screen on a Nexus 4. I have done this before with no problems. It is not rooted and locked to a carrier. Now it is stuck in bootloop.
Now the real problem is that even though the phone will take a charge, when I connect it to a PC it the PV doesnt see the phone and it doesn't show up in file folders or in Nexus Toolkit.
So I cannot access ADB either since the PC doesn't see the device and same with Nexus Toolkit.
I can boot into recovery mode but it goes to Android man on back with red flag and "No Command Found" message.
I have spent a week on this. Who out there knows what the hell I can do. I have thought about swapping out the charger port to see if thats why the pc isnt seeing the phone...I am stumped. Help would be very appreciated folks.
Thanks
Click to expand...
Click to collapse
What happened to this? I have the same damn issue. Although I managed to get fastboot and adb functionality with great difficulty. But the device doesn't seem to be able to boot into anything. I've tried every single thing software by the book, and by the forums too. I suspect it might be hardware.
Any luck?

Damaged recovery, unable to ADB debugging, bootloop

[HELP] [URGENT]
//this is the story, skip if you prefer
so i was updating my cm 12.1 rom to rr 7.1 rom
everything was fine, no real mess just bad flash so i decided to reflash the rom (dunno why i did that actually, its just my tradition). Aaaaand the ROM went flawlessly
next step is install supersu, i checked that the rom is pre-rooted so i think its easier to get supersu via playstore. Installing supersu went flawlessly (again) and i rebooted ma phone.
//then everything starts to f***ed up
my phone bootlooped (not a big deal actually, done with this sh** all the time)
like a casual day, reflash my phone. but i cant go to recovery mode its stuck at logo i think that supersu binary damaged ma recovery.img (again not a big deal but i started to worry) i connect my phone to my pc, summon my adb, and hope the best, but my devices not listed there. then i remembered i forgot to turn on usb debugging on setting oh crap!
so here is my question:
is it possible to turn on usb debugging via pc or something else? if so how.
is it possible to use adb feature without my phone being turned on its usb debugging?
is it possible to repair my recovery <== i mean reflash beside using adb. if so how :crying:
and the last one, beside my phone not listed on adb device list. it wont showed or recognized in my pc (do i need something else beside usb and adb driver?)
any help will be appreciated :good:
this is my only phone so i put my hands on you guys, you're the superhero here
if i dont have any solution, my only way is send this phone to service centre :crying:
some info:
devices : lenovo a6k plus
old rom : cm 12.1 by ED300
new rom: rr nougat v5.8.0 (i dont remember who made this rom, sorry. by the way i found the rom somewhere in xda)
supersu ver: newest per 21 Feb 2k17 (playstore)
my pc: win 8 64x <== dunno if this info useful though
old recovey: twrp (forget the version, but im pretty sure the recovery made by russian developer and it has chicken logo during startup)
battery level when i discovered i cant go to recovery mode: somewhat near 16% <== maybe helpful
if you really care to help me just tell me what do you know, i would appreciate that really, i meant that because this phone is the only way i can contact all of my super important buddy for my business.
Thanks anyway, regards Tom

Well take out the battery and return it hold volum down + power button now you should be able to use fastboot commands go to the folder where you have your adb and fastboot there paste a recovery img file you want to use.Open cmd and type fastboot flash recovery nameofyourimg.img
And now you should be able to use recovery.If not try qfil debricking method that you can find on forum.Best of luck if somthing isnt clear enough feel free to PM me.Also download new recoveries that are now officialy developed

Thanks for replying JovanSijacki
unfortunate enough, i have done that and still dope and nope.
usually i can find my device in windows device manager named android with yellow triangle, but this one is different, my computer wont recognize my phone.
will try debricking method instead, thank you dude :smile:

Thank you for those who care to reply, friend of mine who are expert developer told me how to fix this. AS LONG AS YOU ABLE TO GET INTO FASTBOOT MODE YOU ARE SAFE. Im going to make separate thread to share the tutorial *insert smiley emoji*

Essential soft brick, any way to unlock flash from fastboot to sideload OTA?

Hello I am posting in Q&A because I'm a new XDA user, I was not allowed to post in the dev channel.
I have an Essential phone that has been working great for the past few years, no issues, and it was running standard build receiving OTA updates, until the very last update, which soft bricked the phone.
The phone was never enabled in developer mode while in Android, and now, I can't boot the phone into android at all. The only thing I can do is get into fastboot.
Fastboot state shows DEVICE STATE - locked
Any commands I try to unlock flashing, or change slots, anything at all, I get the error that the device is locked so all commands to unlock fail.
Is there any way to unlock device state from fastboot? I saw a youtube video showing a way to use a chopped USB cable to enter emergency / EDL mode for Qualcomm-based Android devices, but have not seen anyone post that this was successful with the Essential
Does anyone know of any method to be able to unlock flashing from fastboot? Or any other method to un-brick an essential? I've attempted everything, on both Mac and PC, nothing works.
On mac or PC, I can query the device in fastboot and get a response, I just can't do anything to unlock anything!!
Many thanks in advance for any suggestions!

Same problem
Same thing happened to me. Same day as you. I can get fastboot but not adb but since the device is locked I can't flash. I've only had the phone about 6 months so I contacted customer support and they offered to replace the phone.
It might be a known issue because they didn't even try to address the fact that I could get fastboot connected but not adb. They just offered to replace.

Thanks for the info! I am -at least in this case- unfortunately an early adopter. I bought two essentials at the beginning of the pre-release.
Essential support checked my serial number and said the phone was out of warranty.
Has anyone been able to force the Essential into EDL mode to recover that way? It looks like you have to latch one of the USB pins to ground, or 5V, but I haven't found any detailed instructions on how to make this work on the essential...
Thanks again
Justin

I'm sure things have changed and I'm wrong, but if you can get into the fastboot menu can't you just cycle through the options until you get to recovery and then flash an official release from Essential?
I may be thinking of LG or something but this should be possible as long as it's newer than the current software installed because it will see it as an official update and allow the flash.

Thanks but unfortunately, when I try and do that, the phone just does the same thing, it hangs forever on the initial boot screen white Android text with the circle/square logo...
That's why I've been looking into the more direct hardware version of forcing the phone into EDL mode, which is supposed to be possible with all Qualcomm based phones.
I've just not found the time yet to find a USB-C cable I'd be happy to cut in half and short the pins on! Which is why I was hoping someone might have tried this with an essential before to know if it was successful before I start trashing good cables
Thanks again for your reply!
JB

justinbaird said:
Hello I am posting in Q&A because I'm a new XDA user, I was not allowed to post in the dev channel.
I have an Essential phone that has been working great for the past few years, no issues, and it was running standard build receiving OTA updates, until the very last update, which soft bricked the phone.
The phone was never enabled in developer mode while in Android, and now, I can't boot the phone into android at all. The only thing I can do is get into fastboot.
Fastboot state shows DEVICE STATE - locked
Any commands I try to unlock flashing, or change slots, anything at all, I get the error that the device is locked so all commands to unlock fail.
Is there any way to unlock device state from fastboot? I saw a youtube video showing a way to use a chopped USB cable to enter emergency / EDL mode for Qualcomm-based Android devices, but have not seen anyone post that this was successful with the Essential
Does anyone know of any method to be able to unlock flashing from fastboot? Or any other method to un-brick an essential? I've attempted everything, on both Mac and PC, nothing works.
On mac or PC, I can query the device in fastboot and get a response, I just can't do anything to unlock anything!!
Many thanks in advance for any suggestions!
Click to expand...
Click to collapse
I have the exact same problem,
My phone is stuck on Essential log when I turned it on,
I can access Bootloader normally but the device is locked so I cannot flash it,
Recovery is corrupted, when I try to star it, it shows only the the Essential log and freeze so I can not format or wipe or sideload.
OEM Locked and unchecked
USB Debugging is unchecked
and I can't flash anything,
Did you managed to unlock it through Fastboot command or any other way ?
I wish I can just login to the recovery or unlock it so I can flash it clean,
Kindly help me if you found a way out
Thank you