LG G Vista VS880 Brick Please Help!!!!! - Android Q&A, Help & Troubleshooting

I don't know if anyone else has posted anything similar, if they have, please point me in the direction of their thread and I will piggyback off of it. I have a LG G Vista VS880 that I rooted with Kingroot. My next step was to nuke the LAF, go into fast boot and use fastboot oem unllock to unlock the bootloader so I could install custom recovery. I got as far as nuking the LAF when I had to stop and fix dinner for the kids. When I got back to the computer I forgot that I hadn't unlocked the bootloader yet and flashed the custom recovery and a magisk patched boot.img using flashify. Now it will not boot into system or recovery. I can get it to boot into fastboot mode by holding the volume up button while plugging it in but all my fastboot commands are locked. I have searched the forums and have found nothing except some info on getting into QHUSB mode by shorting out the test point but that post was for the G3 and when I took off the back plate the configuration was different and I didnt want to mees my phone up any worse than I already had. I just want to get back to stock and start over. Can someone please help or at least point me in the right direction?!?!?!? I would welcome any assistance!

Related

Random (Hard?) Brick

Hey everyone, so I woke up Saturday morning to a wonderful surprise, and am just getting around to letting everyone know and maybe throw their suggestions my way!
Device: Tmo LG V10, H901
Recovery: [TWRP] Recovery: V10_H901_pplus [V3.0.2-0] [08/16/2016]
ROM: [ROM] [STOCK] [H901] V10_H901_V20J_Stock_Custom_2e [08/15/2016]; V10_H901_V20J_Stock_Custom_2e-signed
Root: Systemless Instructions - How to - 08/08/2016
Xposed: Systemless Xposed, see root guide above
Friday night, I was using my T-Mobile V10 like normal. No recent modifications, no new apps, adjustments, etc... Plug it into the charger and go to bed for the night. No issues right?
I wake up Saturday and the screen is blank. The phone isn't responding to the power button, so I hold the Vol-Down+Vol-Up+Power down to reboot it.
The phone won't reboot. So I pull the battery, and throw it back in.
Phone hits the LG logo, yey!
But it never moves from the LG logo
So at this point, I try booting into Recovery (TWRP) and the phone seems to not be responding to my button commands. It hits the boot logo and never does anything else.
I tried to boot into Download mode, nothing, just sitting on the logo.
After messing with the phone, with and without a USB cable attached to my laptop, I finally get the device into Fastboot.
In fastboot, I can run commands, but since I am on V20J, I am unable to flash or boot TWRP
I was also able to get into download mode when plugged into my PC only.
So down below, I will go over all the stuff I have tried.
Modes I can enter-
Fastboot
Download Mode (USB)
Stuff I tried-
LG Bridge Update
Update says it succeeds
Still does not boot
When I reconnect LG Bridge again, it says an error occurred and wants to update again
Direct .img flash via Fastboot
Using the steps from this post
Unable to flash, FAILED (remote:unknown command) due to V20J I believe
Flash V20J .tot via LGUP
It seems to flash successfully, but the phone still doesn't boot
So I left for the T-Mobile store Saturday, phone not booting, just stuck on the logo.
They are Warrantying the phone, so I am just waiting on a back-ordered replacement now.
EDIT: The Plot Thickens....
So I thought I would fire up the phone this morning, maybe try some other updates/flashes again, maybe something will happen.
Now I cant even get into Download Mode (USB) anymore.
It shows Download Mode on the screen, then the phone just reboots.
Additionally, on first boot I received some sort of error on the screen, but it went away so fast I couldn't read it.
Now I can't get that error to come back for the life of me...
I am just so confused now. The phone has a mind of its own.
My brother had 2 V10's that did that. Replaced under warranty.
Exact thing happened to me back on pre mm.. I got into twrp after many many many tries.. Flashed an old back up and phone booted. I was able to get into the phone long enough to relock bootloader before it started the same crap... Warrantied it out and that was that..
Yikes. Making me scared once this warranty is up.... Would hate to just lose a phone randomly for no reason!
Swizzle82 said:
Exact thing happened to me back on pre mm.. I got into twrp after many many many tries.. Flashed an old back up and phone booted. I was able to get into the phone long enough to relock bootloader before it started the same crap... Warrantied it out and that was that..
Click to expand...
Click to collapse
Can you plz guide how you relocked bootloader? I am rooted and using custom rom. Should I first install stock kdz and then give command via fastboot or it must be done with root? Thanks
Waxim1 said:
Can you plz guide how you relocked bootloader? I am rooted and using custom rom. Should I first install stock kdz and then give command via fastboot or it must be done with root? Thanks
Click to expand...
Click to collapse
You can relock via fastboot using the command
Code:
fastboot oem lock
Use the below command to check your current status
Code:
fastboot getvar unlocked
I believe it even says these commands on the screen when in fastboot.
Fenopy said:
You can relock via fastboot using the command
Code:
fastboot oem lock
Use the below command to check your current status
Code:
fastboot getvar unlocked
I believe it even says these commands on the screen when in fastboot.
Click to expand...
Click to collapse
Thnks I jav read these but need to know if i should b on stock rom before locking or what? And any known issue while trying relocking it?

T-Mobile V10 Bootloop mismatch_sig_len

I am stuck in a bootloop "mismatch_sig_len" and I have tried putting it into download mode, factory reset and a couple of recovery tools that can't find my device. I have read something about having to "short out" two pins with tweezers or copper, to get out of this. Are there any successful methods anyone knows of? Thanks in advance.
james86 said:
I am stuck in a bootloop "mismatch_sig_len" and I have tried putting it into download mode, factory reset and a couple of recovery tools that can't find my device. I have read something about having to "short out" two pins with tweezers or copper, to get out of this. Are there any successful methods anyone knows of? Thanks in advance.
Click to expand...
Click to collapse
Yeah homie mismatched Sig lens I've been there. Only way I found to get out of it was to go to LG pick yourself up a fresh kdz file X. Extract the DZ files. You're going to need to hook up or download the LG kdz flash tool there is a thread about this stuff somewhere in the forums. Yeah I'm not sure about like parsing URL things or anything like that then I was lucky hey I got to flash a couple of partitions and then hook it up to the LG Bridge specifically the software update recovery. I found it most beneficial if I requested the recovery update without the phone hooked up to the USB just off battery out then once you plug in your specific model number and name I think it ask you for plug in your phone or with the battery in and just your volume up button that should give you firmware update download mode. Just the volume down button from off plugging in the USB cord will put you into fastboot mode. Yeah from fastboot mode you can Flash partitions fastboot flash recovery recovery image whatever I hope this helps you out. Give me a thumbs up or something I think I got a few of those I might be able to actually say URL for you. LOL whatever you do take it easy bro that fast-food erase system and then hook up to the LG Bridge flashable zip

biig trouble lg v10 h901 please help

hi all i have lg v10 h901 21j
i tried to root it i download tot file LGH901AT-01-V20j-310-260-JUL-12-2016-ARB02+0ROOTTWRP
when i flashed it phone off and cant on please help
stock rom H901 21j please and how can i flash it cause phone is dead please please help
please guys help the tot file from here https://forum.xda-developers.com/tmo...-h901-t3382819
when flash finish phone off and cant turn on please help
my phone model H901 21j
same issue . ihave h901 running on 5.1 update it via lg up to 6.0 20e then its bricked . pc read it as qualcom hs-usb 9008 . any help/ solution
Is there a reason this thread has been ignored? I also have a LG V10 H901 21J MM/6.0 stock firmware.
I have not as of yet flashed a .tot file to it, because I am not sure that the .tot files for other H901 phones is correct. I have heard different things, regarding this particular version, which I have heard is a Korean version of the phone, I am not sure if this is applicable or true, but apparently this may mean the phone has a different board than other H901s out there.
What I can say for certain is that I was unable to unlock my bootloader, due to the inability to reach Fastboot/Bootloader moder from this phone using any of the normal methods which work on my other LG V10 901. The procedures I have followed to get into Fastboot/Booloader mode are: (a) Shutting down phone; --> Pressing Power-Off, and Volume Down at the same time, holding for 5-6 seconds after the LG screen appears, which just causes the phone to boot normally, (b) running <adb reboot bootloader>, which again just boots normally, it does not go into the bootloader/fastboot mode; and (c) Power down /turn off the phone, once off, hold down Volume Down, while you plugin a USB cable into the phone(that is already plugged into a computer with good drivers on the phone), continuing to hold down the Volume Down until you reach Fastboot, again same results and this does assume that the USB cable is plugged into a computer with good drivers.. Just for the record for the methods listed that involve having the phone attached to the computer, I have tried this with the phones USB in both Multi-Media Mode, and PTP mode, without a difference being made, and it should be mentioned that I have successfully performed all 3 methods on my LG V10 H901 20L running stock MM, which was successfully rooted using the Dirtycow exploit. Yes, debugging is enabled on the phone, and although it does not effect getting into Fastboot mode itself, OEM UNLOCK is enabled.
If I could get into Fastboot on this phone, and get it unlocked, then I should be able to use the Dirtycow exploit in order to get temporary root, that would of course allow me to then flash TWRP recovery directly to the recovery partition, and solve the issue.
rabahallia I know that this is almost a year late, but can you tell me if your phone was unlocked when you flashed the .tot file, and if so, how did you go about unlocking it? Also, I can tell you based on the chipset that the phone runs, that you should be able to image a microSD card using a ROM designed for the phone, and then boot using the flashed sdcard image. If you are not able to do that, then can you tell me if now that your phone is bricked, is the phone turning on at all, or just not booting fully? Can you attempt to get it into Fastboot mode now, using the methods I described above? You will have the highest chance of success using the 3rd method in terms of being straight forward, and of course the fact that your phone is not booting again that involves: plugging a USB cable into your PC, then, shutting down your phone which is not a problem in your case with your phone off, hold down the Volume Down button on your phone, while still holding down the Volume Down plug the USB cable into your phone, and continue holding Volume Down until your phone reaches the fastboot/bootloader menu. If you are able to do this, and you DID NOT unlock your phone before you flashed the .tot with the modified recovery onto your phone, then unlocking the bootloader at this point may allow your phone to boot. To do this, after you have reached Fastboot/Booloader, you will use the command <fastboot oem unlock> wait for it to finish, and it should inform you that your phone is now unlocked, then you can reboot your phone using <fastboot reboot>. Please let me know if this worked, or if you still have the phone, if you could try this. I am interested to know if flashing the .tot to a phone that can not be unlocked due to inability to reach the bootloader/Fastboot mode, as you may have done, would allow that mode to be reached after bricking the phone, and if so, if unlocking the phones bootloader after the fact, fixes the issue. If this does not fix the issue, but you were able to reach fastboot/bootloader, then you should be able to reboot back into Fastboot mode, and then flash a recovery, which would in turn allow you to flash a new ROM to the phone. If anyone else out there has any information SPECIFICALLY ON THE 21J version of H901 stock MM, please provide any information you may have. Or if you have any information about what board is running on this phone, if it is not the same board running on every other version of the H901 such as the 20J, 20e, 20L.

[RS988] Help with brick phone

A few years ago, I ended up bricking my LG G5 RS988 variant, by trying to flash a stock rom, so I can remove the root, and everything else to give the phone to my brother. However, by flashing the wrong rom, I ended up being in a loop where the phone would start up, and 2 minutes into the set up screen, it would restart and be in a never ending loop. I remember trying to fix this problem, and made it worse by probably erasing access to my twrp recovery(can't access the recovery anymore don't remember what I did), then I gave up. I decided to try again to see if I can bring back this phone from the grave so I was wondering if someone could lead me into the right direction. I have the uppercut tool, the lg flash tool, and the drivers. Also in the uppercut tool I do see the version of my phone is RS98821d and I am trying to flash a RS98811c_00_ARB01.kdz. Also another thing to note, my phone automatically boots into firmware update mode(download mode I believe?). Also I have looked into the all in one lg g5 forums, and other forums of restoring their phones, but nothing works with what I tried on my rs988, is their someone that can lead me to the right direction?
Can you do this when you start the phone to get into fastboot?
Code:
adb reboot bootloader
If so, you should be able to get TWRP back up and running:
Code:
fastboot flash recovery [path to twrp image on your pc]

Question Help! My Oneplus Nord N200 5G cellphone is bricked.

I am currently trying to install LineageOS on my phone. I personally have never unlocked or reinstalled a new operating system on my phone. I looked on some XDA forums for some guides and i found one and followed the steps. I unlocked my phone and I installed a custom TWRP because I was trying to downgrade the phone back to android 11. Once i was done flashing the file to the phone and rebooted it doesn't boot anymore and only gives me a booting screen for a few seconds after I hold down the power and volume up button for a few seconds nothing else works. I have use the MSM tool and put my phone into EDL mode and it detected the phone with a black screen. Every time I use the tool it works till about 18% then it gives me a Sahara communication failed error and then my phone gets out of EDL mode.. I installed all the drivers needed on my PC and used multiple USB 2.0 slots but it still fails. Any help would be appreciated.
There are warnings in the TWRP thread for the N200 that it is broken and should not be flashed.
I have written an easy to follow guide here to downgrade to A11 with Fastboot Enhance.
Unfortunately, now that you have used MSMTool on the phone, it is now bootloader LOCKED. This tool should be the last resort only if you are already hard bricked. You could have gotten the phone into fastboot if either boot.img was still intact and re-flashed the rom with a still unlocked bootloader. The phone will change slots after so many failed boots.
Now that your boot loader is locked, the only tool that can modify the phone is MSMTool. If you can get into Recovery, do delete user data and try again.
Otherwise, you will need to get an RMA and send phone back to OP.
scanman0 said:
There are warnings in the TWRP thread for the N200 that it is broken and should not be flashed.
I have written an easy to follow guide here to downgrade to A11 with Fastboot Enhance.
Unfortunately, now that you have used MSMTool on the phone, it is now bootloader LOCKED. This tool should be the last resort only if you are already hard bricked. You could have gotten the phone into fastboot if either boot.img was still intact and re-flashed the rom with a still unlocked bootloader. The phone will change slots after so many failed boots.
Now that your boot loader is locked, the only tool that can modify the phone is MSMTool. If you can get into Recovery, do delete user data and try again.
Otherwise, you will need to get an RMA and send phone back to OP.
Click to expand...
Click to collapse
Sorry I should have written more details but I currently have a hard bricked device. It will not boot and It failed to boot like 20 times. It will not enter fastboot or even get past the logo when you first turn it on. I did use MSM tool after it wasn't letting me into fastboot. Thanks for the help and I will send it back.
z67gp said:
Sorry I should have written more details but I currently have a hard bricked device. It will not boot and It failed to boot like 20 times. It will not enter fastboot or even get past the logo when you first turn it on. I did use MSM tool after it wasn't letting me into fastboot. Thanks for the help and I will send it back.
Click to expand...
Click to collapse
Fix Sahara communication failed error in MSM Download Tool
In this tutorial, we will show you how to fix the Sahara communication failed and other related MSM Download Tool errors.
www.droidwin.com

Categories

Resources