Develop Bugs

[Q] Stuck In a Bootloop and can't flash stock ROM

Foolishly, I was messing around in build.prop and obviously it put me into a bootloop. I can get into download mode, but not recovery or fastboot.
I planned on just flashing a stock ROM back onto the phone and followed this guide: http://forum.xda-developers.com/showthread.php?t=2420219
However, after I've put the device into download mode, the LGMobile Support Tool gets stuck at "waiting for connection". If I try to proceed with flashing the stock ROM, the installation gets stuck at this: http://imgur.com/yFSOZJe.jpg
(If I try update recovery like it suggests, it's unable to find the device)
I believe the software is not properly recognizing my phone, however all drivers seem to be properly installed. In the Device Manager, it recognizes the phone as this: http://i.imgur.com/PWWqbc1.jpg
This is what the R&D Test tool reads on my device: http://i.imgur.com/zxFiCFh.jpg
Since this is my only phone, I'd very much like it back any suggestions on how to fix this?
Thanks!

What model is it?

Try using the LGflashtools method, there is a guide in the q&a section. I would recommend you find and use the nov 22 tot file because the one in guide had a non responsive touch screen.
Sent from my LG-E980 using XDA Free mobile app

[Q] Unable to root Sprint G2

I restored a TOT file using lgflashtool to go back to stock ZVE (previously rooted with TWRP), then ADB sideloaded to ZVG. Everything is working fine, but I can't root. I have tried the LG One Click Root (both 1.2 and 1.3) and one from highonandroid but it didn't work either. I have followed the directions exactly, enabling USB debugging and I run as admin. I am succesfully able to get the phone into download mode as well, so that is not a problem. Any ideas? I have searched this forum and didn't see anybody having problems with it so sorry if this is repeated information.

try the script method?
Hey I too have been struggling with the root via one click .. I would be good until the script would be waiting for device and download mode. I eventually uninstalled all the lg drivers and root programs I had installed. Then rebooted computer, reinstalled lg driver and ran the lg root script version 1.2, run the program and be patient. it may take up to five minutes then it will tell you to put the phone in down load mode and reconnect. It recognized the phone immediately and then I waited and waited and waited, then finally the su script completed and then the prompt was to press control+C and then N and reboot. maybe it will work for you but this is where im getting stuck.. good luck if any of this helps.

The graphic interface version worked for me. In download mode make sure it finds it on the correct Port.
If not change it in device settings.
Mine would progress to 90%and stick. After 5 minutes I disconnect, reboot phone and root was there.

Do you know what port the gui looks for the device on by default? Maybe i can assign the port befor executing the gui script.

Did you try stump root? That one worked for me on ZVE.

i
I was able to gain root by one click it would detect my phone try to reboot it in download mode but It wouldn't go into download mode if it makes it that far let it sit there rebooted and ui on computer will ask u to put it in dl mode manually. As for the port I used 41 as if I was doing a tot. Restore I can go into more detail if this is the same issue u r having

Yup. Stump dosent work on zvg. I've installed it despite what I've read and tried it. It tells me. Out says I'm already rooted, but super user tells me I'm not rooted.

Dopamin3 said:
I restored a TOT file using lgflashtool to go back to stock ZVE (previously rooted with TWRP), then ADB sideloaded to ZVG. Everything is working fine, but I can't root. I have tried the LG One Click Root (both 1.2 and 1.3) and one from highonandroid but it didn't work either. I have followed the directions exactly, enabling USB debugging and I run as admin. I am succesfully able to get the phone into download mode as well, so that is not a problem. Any ideas? I have searched this forum and didn't see anybody having problems with it so sorry if this is repeated information.
Click to expand...
Click to collapse
Maybe you should try this method. Restore to ZVE and rootz it with Lg one click v1.2. Once you confirmed it's rooted, then adb sideload on stock recovery to upgrade to ZVG. When you upgraded to zvg, try the Lg one click root v1.2 again Usually, that Lg One click root v1.2 will stuck on and take awhile, but it did it's job. Also to change the port number after used the LgFlashtool. Alot time, the port 41 don't work with Lg one click root.

Port 41works for mine

My OnePlus 3 is a brick

Dear XDA Community,
in past 2 months i've been using CM13, constantly having some trouble with apps involving the camera, such as the camera app(surprise) and e.g. snapchat.
So yesterday I decided to update my CM Build, not knowing it would be to CM14 and with this Android 7.
So resulting from this I experienced a lot of issues with different apps, especially the google ones and for example Instagram. I DID NOT Upgrade my twrp, which was pretty stupid as I found out.
So this morning I checked again for CM Updates and Updated to Version Nightly...25 I think... but because I did not update my TWRP it did absolutely nothing except bricking my phone.
I already followed through the Guide for Hard Bricked OP3s (both steps) "http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700"
Though it sadly did not work for me. The Recovery tool and all works but when I want to boot my Phone the md5checksum pops up after the OP3 Logo and it tells me that everythings fine except "boot: failed".
I tried the procedure of the Hard Brick fix over and over again but nothing seems to work. I am fairly new to this whole Custom Rom stuff so I have absolutely no clue what do to.
Does anyone have any idea that could help?
Best Regards
Aliasalex

Try fastboot flashing the whole rom.

how? i dont have a factory img.
i tried flashing CM14 again and OxygenOs OTA. Currently i am getting Cache, Boot and System Failed.
In the meanwhile I managed to get twrp installed, but trying to install OS or CM via twrp didnt work either
//edit: ran the msm download tool again. Now only Boot is failing. tried flashing a boot.img via fastboot but didnt work
//edit2: when flashing the boot.img via fastboot my phone boots and works. When restarting without PC it still has cache and boot failure in md5checksum

try the 1st method you mentioned in the OP but flash https://www.androidfilehost.com/?fid=24591020540821926 . from what I understand, you need to full write all your partitions since they seems corrupted.

aliasalex said:
how? i dont have a factory img.
i tried flashing CM14 again and OxygenOs OTA. Currently i am getting Cache, Boot and System Failed.
In the meanwhile I managed to get twrp installed, but trying to install OS or CM via twrp didnt work either
//edit: ran the msm download tool again. Now only Boot is failing. tried flashing a boot.img via fastboot but didnt work
//edit2: when flashing the boot.img via fastboot my phone boots and works. When restarting without PC it still has cache and boot failure in md5checksum
Click to expand...
Click to collapse
I'll help you when I'm home
Connect your phone to Fastboot. Go to device manager on Windows. Do you see something with OnePlus or kedacomm. I had this issue as well managed to solve it after 2 days.

Demian3112 said:
I'll help you when I'm home
Connect your phone to Fastboot. Go to device manager on Windows. Do you see something with OnePlus or kedacomm. I had this issue as well managed to solve it after 2 days.
Click to expand...
Click to collapse
Yes a Kedacom USB Device "Android ADB Interface" is listed.

aliasalex said:
Yes a Kedacom USB Device "Android ADB Interface" is listed.
Click to expand...
Click to collapse
I'm not home atm. But can you change it by any chance to Oneplus? Your almost there! Maybe the video can explain something, I don't have a pc close.
https://youtu.be/maLWScgXflk

Demian3112 said:
I'm not home atm. But can you change it by any chance to Oneplus? Your almost there! Maybe the video can explain something, I don't have a pc close.
https://youtu.be/maLWScgXflk
Click to expand...
Click to collapse
I installed the adb setup, still shows my OP3 as Kedacom -> android adb device..
my phone has been working for the past few days flawlessly, but it still doesnt boot on its own

aliasalex said:
I installed the adb setup, still shows my OP3 as Kedacom -> android adb device..
my phone has been working for the past few days flawlessly, but it still doesnt boot on its own
Click to expand...
Click to collapse
You can't access Fastboot because of that Kedacom driver, if you right click it you should be able to change the driver.
https://support.hidemyass.com/hc/en...ow-to-disable-Driver-Signing-check-on-Windows try to boot into this. Also try to install Oneplus drivers. It's in the unbrick post.

Demian3112 said:
You can't access Fastboot because of that Kedacom driver, if you right click it you should be able to change the driver.
https://support.hidemyass.com/hc/en...ow-to-disable-Driver-Signing-check-on-Windows try to boot into this. Also try to install Oneplus drivers. It's in the unbrick post.
Click to expand...
Click to collapse
But I can access fastboot!?
Also I disabled Driver Signing Check when first trying to unbrick my phone.
I installed the drivers given in the Unbrick Test, it showed something like Qualcomm [something] 9003. There was something in between.

aliasalex said:
But I can access fastboot!?
Also I disabled Driver Signing Check when first trying to unbrick my phone.
I installed the drivers given in the Unbrick Test, it showed something like Qualcomm [something] 9003. There was something in between.
Click to expand...
Click to collapse
Nice, whdn you boot you still get those errors in red letter something with "failed boot". Then manually flash the boot. Img provided in the folder where you ran the Unbrick tool from. Command for Fastboot "fastboot devices", then "fastboot flash boot boot.img". Make sure that Kedacom is not in device manager when you are accessing Fastboot.

Rooting help: bootloop, possible soft-brick

Hey all; first post and 100% green with rooting. This is my first attempt and i'm hitting a stumbling block.
First off, I've been using the guide on "theandroidsoul"(can't post a link due to post count, but a quick google search should bring you to the exact one)
I have successfully setup ADB, unlocked the bootloader, flashed TWRP 3.2.3-1 and have been able to boot into it using ADB.
However on step 10 of the guide i'm using, it's not too clear if i should skip formatting the device memory or go ahead and do it. I did it. I suspect this might be where i went wrong.
Regardless, i'm able to move Magisk onto the internal storage and TWRP is able to install it successfully.
Once i try to reboot, the "bootloader unlocked" warning screen shows, then the oneplus boot screen appears. It shuts down and reboots like this a second time, then the screen goes black and the front LED illuminates white and nothing happens. I can shut down the phone by holding the power button, then boot into fastboot manual using power + volume up. However if i try to boot the phone normally or boot into recovery mode, it repeats the same symptoms.
I'm unaware if I've soft or hard bricked the device. Like i mentioned i'm able to boot it into fastboot just fine and can get TWRP to come up with a boot command via ADB. But no matter how many times i try to install Magisk(I tried both v18 the guide mentions and the latest v19 from their site) i can't get it to boot.
I'm aware i also used an outdated version of TWRP(the one the guide mentions). i tried to flash twrp-3.3.0-1(latest version for dumpling) but cannot. I believe because a version of TWRP is already flashed on the device?
Can anyone help me out?

Hi all,
I'm facing the same issues as Josh and came seeking help, as well, so any help would be greatly appreciated! This is my first foray into Android coming from Windows 10 Mobile, which I'm still using two weeks after purchasing the 5T because of these issues. No matter what I do, I cannot get it to work and am now stuck in the same loop as mentioned above.
I'm attempting to install LineageOS and followed the instructions on its official site to a T, but have never been able to get it to boot into the OS. The only difference from the original poster's issue is that I'm not trying to root the device.
Thanks again for any help!

Josh Hex said:
....
I'm unaware if I've soft or hard bricked the device. Like i mentioned i'm able to boot it into fastboot just fine and can get TWRP to come up with a boot command via ADB.
....
i tried to flash twrp-3.3.0-1(latest version for dumpling) but cannot. I believe because a version of TWRP is already flashed on the device?
Can anyone help me out?
Click to expand...
Click to collapse
Hi, on my search how to flash TWRP revovery ROM I stumbled upon your post. With my first attempts, I did not even manage to get the official TWRP to run on my op5T - got always blue led - basically the same symptoms without trying to root. Meanwhile LOS works fine on my OP5T (I updated to the latest OOS then flashed and booted twrp-3.3.0-0-20190427-codeworkx-dumpling.img.).
ANYWAY my solution to unbrick and reinstall OxygenOS again was the...
... official unbrick tool - can be found in this forum when searching after (still cannot post links): OnePlus 5T Unbricking Tool
There is also another page here on the forum collecting different unbricking tools - although I am not aware how they are - since I used another source by googling for "How to Unbrick OnePlus 5T with OnePlus 5T Unbrick Tool (Unroot/Fix bootloop)".
Hope you get it running again, like I did.

Amix73 said:
Hi, on my search how to flash TWRP revovery ROM I stumbled upon your post. With my first attempts, I did not even manage to get the official TWRP to run on my op5T - got always blue led - basically the same symptoms without trying to root. Meanwhile LOS works fine on my OP5T (I updated to the latest OOS then flashed and booted twrp-3.3.0-0-20190427-codeworkx-dumpling.img.).
ANYWAY my solution to unbrick and reinstall OxygenOS again was the...
... official unbrick tool - can be found in this forum when searching after (still cannot post links): OnePlus 5T Unbricking Tool
There is also another page here on the forum collecting different unbricking tools - although I am not aware how they are - since I used another source by googling for "How to Unbrick OnePlus 5T with OnePlus 5T Unbrick Tool (Unroot/Fix bootloop)".
Hope you get it running again, like I did.
Click to expand...
Click to collapse
Thank you. I'll give it a shot and will let you guys know how it works out!

[Solved] Was updating to Lineage OS 17 but now I'm stuck on stock Android 8

I have the G710EMW variant. As the title states, I was trying to install Lineage OS following sirbow2's thread 'Lineage OS 16/17/GSI Install Guide for LG G7 ULM'. Using the universal unlock method, I unlocked my phone. Next step was installing 21d ULM firmware; this is where I am stuck. When I begin the installation using LGUP, the phone boots into the rooted fastboot mode instead of the download mode. I even tried switching slots but it still boots up in fastboot mode.
Also, when I am able to load the download mode, it stays at the download mode screen & doesn't actually proceed further & neither is the device detected in device manager when it is connected in the download mode.
I've rooted quite a few phones in the past but this one has troubled me a lot. It is very difficult to find time for all this when you're working a full-time job. Please help me fix this. I'm happy even just to return to the stock LG ROM (which reminds me that the same thing happens when I try using the LG Bridge tool).
Thank you!

use this thread to flash stock https://forum.xda-developers.com/lg-g7-thinq/how-to/cross-flash-oreo-pie-firmwares-lg-g7-g7-t3915303.

sinkoo1979 said:
use this thread to flash stock https://forum.xda-developers.com/lg-g7-thinq/how-to/cross-flash-oreo-pie-firmwares-lg-g7-g7-t3915303.
Click to expand...
Click to collapse
Already tried that method. Everything works fine until the phone boots to start installation. Ideally it should start in download mode but in my case, it boots into the rooted bootloader.

@Awesomeslayerg was kind enough to message me this link (https://forum.xda-developers.com/lg...to-recover-hardbrick-9008-mode-boxes-t4052841) which helped me fix my problem.
Not only was I able to revert to stock; I went ahead to install LineageOS 17 which is amazing!
Thank you, Awesomeslayerg.
This thread can be marked as fixed now.