Database Info

LG G2 (VS980) can't update/flash

Hi all. I have been trying to update my VS980 to Lollipop for a week now; I've tried absolutely everything I can think of / find in the forums, and nothing works.
The basic problem is this: I have a rooted (via Stump Root) Verizon G2 running stock 4.4.2. I wanted to upgrade it to Lollipop, so I unrooted with SuperSU and tried to OTA update it, but somehow it still knows it was once rooted, so the OTA fails. I have tried MANY things to fix/work around this, but here are the highlights:
Hard reset. The hard reset procedure completed ok, but when I try to then install the OTA update, it fails with "Err: 1117008." Settings -> About Phone still shows "Status: Rooted," even though I don't actually have root control anymore.
Use LG FLash Tool to flash back to factory stock: VS980011A_01.tot. Tried two different computers, using both Vista and Windows 10. Failed because the proper LGE Mobile USB Serial Port driver was never found/installed by Windows (despite it clearly working in the video).
Copied a text file called RCT_security containing "forel.lee" onto the SD card, b/c somehow that's supposed to reset the status to "unrooted." It didn't.
Re-rooted with Stump Root, manually installed TWRP to try to flash a ROM that way. Phone is now rooted again, but attempts to boot into recovery result in "secure boot error," and no TWRP.
Installed Quick Boot to boot directly into recovery. Fails with same "secure boot error."
Installed FreeGee and TWRP Manager, b/c now I'm just grasping at straws. FreeGee hangs on a black screen and does nothing. TWRP Manager tells me that TWRP is already installed; haven't tried using it to flash a new ROM from here, b/c that feels brickish.
Use AutoRec to fix the "secure boot error." Fails b/c running AutoRec results in it hanging at "checking for loki....installing," When I backed out after many minutes, I got an error that said "Tried to install Loki Tool, no luck."
I am out of ideas. I am pulling my hair out. The phone is working fine, except that it's stuck on 4.4.2. When I started, all I wanted was a working version of Lollipop, even if it was stock/unrooted. At this point, I'm so mad at Verizon/LG/Android for making this process so painful that I really just want to flash the latest CyanogenMod just for spite. But really -- I'll take anything.
Help?

jackpurrton said:
Hi all. I have been trying to update my VS980 to Lollipop for a week now; I've tried absolutely everything I can think of / find in the forums, and nothing works.
The basic problem is this: I have a rooted (via Stump Root) Verizon G2 running stock 4.4.2. I wanted to upgrade it to Lollipop, so I unrooted with SuperSU and tried to OTA update it, but somehow it still knows it was once rooted, so the OTA fails. I have tried MANY things to fix/work around this, but here are the highlights:
Hard reset. The hard reset procedure completed ok, but when I try to then install the OTA update, it fails with "Err: 1117008." Settings -> About Phone still shows "Status: Rooted," even though I don't actually have root control anymore.
Use LG FLash Tool to flash back to factory stock: VS980011A_01.tot. Tried two different computers, using both Vista and Windows 10. Failed because the proper LGE Mobile USB Serial Port driver was never found/installed by Windows (despite it clearly working in the video).
Copied a text file called RCT_security containing "forel.lee" onto the SD card, b/c somehow that's supposed to reset the status to "unrooted." It didn't.
Re-rooted with Stump Root, manually installed TWRP to try to flash a ROM that way. Phone is now rooted again, but attempts to boot into recovery result in "secure boot error," and no TWRP.
Installed Quick Boot to boot directly into recovery. Fails with same "secure boot error."
Installed FreeGee and TWRP Manager, b/c now I'm just grasping at straws. FreeGee hangs on a black screen and does nothing. TWRP Manager tells me that TWRP is already installed; haven't tried using it to flash a new ROM from here, b/c that feels brickish.
Use AutoRec to fix the "secure boot error." Fails b/c running AutoRec results in it hanging at "checking for loki....installing," When I backed out after many minutes, I got an error that said "Tried to install Loki Tool, no luck."
I am out of ideas. I am pulling my hair out. The phone is working fine, except that it's stuck on 4.4.2. When I started, all I wanted was a working version of Lollipop, even if it was stock/unrooted. At this point, I'm so mad at Verizon/LG/Android for making this process so painful that I really just want to flash the latest CyanogenMod just for spite. But really -- I'll take anything.
Help?
Click to expand...
Click to collapse
VICTORY IS MINE. Here's what I did:
I decided to focus on the LG Flash Tool as my best potential for a successful outcome, and I further decided to focus on the LG drivers, which didn't seem be installing properly. So:
Nuked my computer and installed a fresh version of Windows 10, to ensure no errant drivers were present.
Installed LG United drivers from the top of this page: [link deleted b/c xda won't let me post it] (LG VZW_United_WHQL_v2.16.1.exe)
Connected the phone in Media Sync mode and waited while Windows installed some more drivers.
Connected the phone in Internet Connection -> Ethernet mode and waited while Windows installed yet more Drivers. (I think this may be the step I missed in all previous attempts; once this was done, the correct LG driver appeared in Device Manager.)
Installed LG Flash Tool 2014 (download link in the description of the below video).
Followed the instructions in this video: [link deleted b/c xda won't let me post it] ...
... to install VS98027A_05.kdz, which I found somewhere, but now can't remember where. But it's around.
Once all those elements were in place, it worked perfectly. Got a completely stock phone, just like the day I bought it. Immediately installed 3 software updates and am now on Lollipop.
I'm still not sure which parts of this puzzle mattered and which didn't, but I *think* the key was installing those specific drivers (and not the many other versions of the same that I came across while researching), and THEN connecting the phone in MTP mode (ethernet) -- because that's when I finally had the correct drivers appear in Device Manager. Once I got there, the LG Flash Tool worked the first time.
Right. I hope this helps someone. I lost two weeks of my life to this (and a perfectly good CentOS box).
Last thing: download mode for me doesn't work quite the way anyone describes it. I have to turn it off, hold the UP volume button, plug it in, then let go of the UP button briefly and then hold it down AGAIN. No one mentions that last part.

Lost WiFi and other features after switching from Slot B to Slot A

I am running stock ROM and have bootloader unlocked and TWRP already installed. The phone was rooted without problems. I was getting an error from Super SU, so I looked up how to fix it online and the suggestion was to install an older version and then try to upgrade it. It was hard to find a zip from a legitimate source but once I found it, TWRP did not show the directory I was looking for (this was previously available when I rooted it). This is where I did something stupid and looked around in the settings and found the Slot A / Slot B option. I switched from B to A and the phone got stuck on the boot animation for several minutes after rebooting. I decided to reboot into TWRP and switched the slot back to B. This brought the phone back but WiFi is off by default and whenever I try to turn it on, it doesn't change.
I have seen a couple of other people mention similar issues about losing wifi after a root or changing the slot. What's the fix? I am wondering if there is anything else "broken" after the slot change and if I should do a factory reset (I would hate to do that as I was almost finished setting up this device). I have also received the error message saying "Process System isn't responding" in the settings menu a few times. It also seems like the finger print scanner isn't recognizing fingerprints any more and face unlock isn't working

One possibility is, that SuperSU isn't that compatible anymore. Magisk does a wonderful job and no problems so far. Maybe you should give it a try and switch from using SuperSU to Magisk.

shagexpert said:
I am running stock ROM and have bootloader unlocked and TWRP already installed. The phone was rooted without problems. I was getting an error from Super SU, so I looked up how to fix it online and the suggestion was to install an older version and then try to upgrade it. It was hard to find a zip from a legitimate source but once I found it, TWRP did not show the directory I was looking for (this was previously available when I rooted it). This is where I did something stupid and looked around in the settings and found the Slot A / Slot B option. I switched from B to A and the phone got stuck on the boot animation for several minutes after rebooting. I decided to reboot into TWRP and switched the slot back to B. This brought the phone back but WiFi is off by default and whenever I try to turn it on, it doesn't change.
I have seen a couple of other people mention similar issues about losing wifi after a root or changing the slot. What's the fix? I am wondering if there is anything else "broken" after the slot change and if I should do a factory reset (I would hate to do that as I was almost finished setting up this device). I have also received the error message saying "Process System isn't responding" in the settings menu a few times. It also seems like the finger print scanner isn't recognizing fingerprints any more and face unlock isn't working
Click to expand...
Click to collapse
I had the same issue when I first got my 6 when I was playing around with the slots. Also my original TWRP install for some reason would crash and reboot whenever I plugged in the data cable while in TWRP. I ended up flashing back to stock OOS 5.1.5 through fastboot (used the flash-all command) and then reinstalled TWRP and everything has been working great since then.

MickyFoley said:
One possibility is, that SuperSU isn't that compatible anymore. Magisk does a wonderful job and no problems so far. Maybe you should give it a try and switch from using SuperSU to Magisk.
Click to expand...
Click to collapse
The instructions I followed already installed Magisk to the phone. I wanted Super SU because some of the other chainfire apps like Liveboot and rooted apps like Titanium backup said Super SU is needed (Titanium said Magisk will work but may not be reliable for some newer versions of the ROM). I can live without liveboot but really need Titanium to reliably transfer data from my older phone.
To be honest I didn't know they did the same thing (magisk and Super SU). I am curious now, what if I factory reset my phone and attempted to install Super SU instead of Magisk this time?
If I do a factory reset (let's say I want it just like it was out of the box and I format the data partition as well), will I need to root the phone again? I am asking because I don't know which part of the instructions I should ignore. I am sure TWRP will already be installed after the reset so I would only need to install the extra apps...

You don't have to format data. Just factory reset it. Then use "fastboot boot twrp.img", don't allow modifications, flash a kernel you want (if you want one - I really recommend ElementalX) and then the latest version of Magisk (16.4 BETA currently). Did so - all fine. And yes: Even Titanium Backup works without any issue with Magisk.

We had similar problems with TWRP on the Razer Phone when it was new. We solved the problem by using the TWRP boot image to flash the stock boot image and then flashing a TWRP zip. I just got the OnePlus 6 yesterday and haven't really messed with it yet but everything sounds the same to me so far.

I read more about TWRP and realized what I was doing wrong when the directory with zip files wasn't showing up. When TWRP showed up I was supposed type in my regular unlock password to decrypt storage. When I did that the folder I was looking for showed up. I made a backup through recovery (which took like an hour, may be because the external flash drive I attached was really slow - and the size of the backup was about 12GB). After that I installed the zip file for Super SU, just to see if it worked - it showed the installation was successful but the app was still missing from the app drawer. Now I wanted to factory reset the device and start over.
I went into wipe and there was nothing listed under the wipe screen. I went into Advanced wipe and wiped whatever was selected by default. The selected items were Dalvik / ART Cache, System, Data. There was also "Internal Storage and USB Storage" that wasn't selected.
I swiped to wipe, it wiped everything. Then asked reboot, I rebooted, got a blank screen with white LED for a long time. When I plugged it into the computer it recognized the device as Qualcomm HS-USB Diagnostics 900E (COM4). I rebooted it by holding Power + Volume Up + Volume Down. I tried to boot into boot loader next. This brought me to another blank screen. The computer still makes a noise when it reboots but screen stays black. The only message that shows up is the one saying boot loader is unlocked. Did I brick my phone? This keeps getting progressively worse.

shagexpert said:
I read more about TWRP and realized what I was doing wrong when the directory with zip files wasn't showing up. When TWRP showed up I was supposed type in my regular unlock password to decrypt storage. When I did that the folder I was looking for showed up. I made a backup through recovery (which took like an hour, may be because the external flash drive I attached was really slow - and the size of the backup was about 12GB). After that I installed the zip file for Super SU, just to see if it worked - it showed the installation was successful but the app was still missing from the app drawer. Now I wanted to factory reset the device and start over.
I went into wipe and there was nothing listed under the wipe screen. I went into Advanced wipe and wiped whatever was selected by default. The selected items were Dalvik / ART Cache, System, Data. There was also "Internal Storage and USB Storage" that wasn't selected.
I swiped to wipe, it wiped everything. Then asked reboot, I rebooted, got a blank screen with white LED for a long time. When I plugged it into the computer it recognized the device as Qualcomm HS-USB Diagnostics 900E (COM4). I rebooted it by holding Power + Volume Up + Volume Down. I tried to boot into boot loader next. This brought me to another blank screen. The computer still makes a noise when it reboots but screen stays black. The only message that shows up is the one saying boot loader is unlocked. Did I brick my phone? This keeps getting progressively worse.
Click to expand...
Click to collapse
OK good news! I tried one more time and fast boot showed up. I was able to get into recovery. I have the backup so I will try to restore that. I don't know what to do after that. I am thinking wiping without getting into advanced mode.

shagexpert said:
OK good news! I tried one more time and fast boot showed up. I was able to get into recovery. I have the backup so I will try to restore that. I don't know what to do after that. I am thinking wiping without getting into advanced mode.
Click to expand...
Click to collapse
When your phone booted straight into that mode with black screen and the led, then you bricked it. Same happened to me 2 days ago. The solution was to use the Msmtool from another thread and it worked great. Just follow the guide. But it will wipe your device. And you have to install oxygenos manually via "local upgrade". If you have a question, just ask

What I ended up doing was restoring from the backup I had. This was the "bad backup" without WiFi and broken finger print and facial recognition. After the restore, I did a normal wipe (not advanced). This reset the phone to factory settings. Once I configured WiFi and signed into my Google account, Google offered to recover from a cloud backup of my One Plus - I didn't know Google made these backups. It downloaded all the apps automatically. I don't know yet if I have sign into all of them all over again.
The bad back up saved my ass, I wasn't even planning on making it. I was just testing the backup feature. That's why you should always do a backup, even if the device isn't in ideal configuration.

shagexpert said:
The instructions I followed already installed Magisk to the phone. I wanted Super SU because some of the other chainfire apps like Liveboot and rooted apps like Titanium backup said Super SU is needed (Titanium said Magisk will work but may not be reliable for some newer versions of the ROM). I can live without liveboot but really need Titanium to reliably transfer data from my older phone.
Click to expand...
Click to collapse
I rooted my phone with Magisk and installed the 5.1.6 via OTA (and reroot via installed Magisk Manager). So no need to install TWRP so far.
Titanium Backup runs flawlessly with Magisk (already on my OP 3T and my OP 5).
So give Magisk a try, I never had such an easy and reliable update as the one from 5.1.5 to 5.1.6

Helium is a great alternative to titanium.

Help would be appreciated

Okay. I was messing around with my firmware which I've done in the past. I've had a few problems then due to my phone model being obscure (Samsung Galaxy S6: SM-S906L). I've always had a copy of the firmware saved to my computer in the event of a bootloop or a similar issue, I figured I could just flash it with Odin to fix it. I have also done this in the past. After accidently wiping my phone, I went to re-install Magisk, but noticed my phone trying to push an update. I let it go through without much though and after it finished saw it didn't change much. I carried on with re-installing Magisk when I figured I might as well fix some problems I had with booting the phone (I would have to boot it into download mode then recovery to get it out of a bootloop each time I turned it off). I carried on with flashing my saved firmware to fix the problem. Everything flashed fine except the bootloader. It's come to my understanding now that because I let the update carry through with my phone, my saved firmware is no longer compatiable dispite the fact that it didn't change my android version. So now I have a bootloader installed that is meant for a higher update without my known ability to downgrade. Due to the obscurity of my phone model, I can't find anything to bring my firmware up to what my bootloader is at. So now my phone is stuck in a bootloop with the ability to access download mode, but recovery mode simply gives me a "recovery is not seandroid enforcing" error. I would greatly appreciate it if someone has any advise they could give me.

Help with flashing stock ROM on Nokia 3.1 (Mediatek MT6750)

I got my Nokia 3.1 in a bit of a weird situation trying to flash the stock ROM. I feel like it's a lost cause, but since I can still boot in recovery mode, there may still be a solution, I will explain in case someone can help.
It started when I tried to update from Android 8.0 to 10.0 (none of the previous OTA updates had worked and would always reboot in Oreo 8.0). This time, it didn't work and got the phone stuck in a boot loop.
The phone is still under warranty, but because I bought it overseas and there's no Nokia care centre here is New Zealand, I had no option but trying to repair it myself.
A wipe/factory reset didn't help, but after changing the active slot from B to A (using fastboot), it booted again in Oreo 8.0. Only problem is that I could no longer start a fresh Oreo 8.0 install without updating first and since all updates failed, I was stuck.
I suspect slot B is damaged or corrupt, hence the impossibility to update. To check it, I switched back the active slot to B after a factory reset, and that was not a great idea, the phone wouldn't even boot and looked hard-bricked.
But I still managed to use SP tool to download firmware, so I did that with the original Nokia 3.1 stock ROM (ES2).
However, I could not flash all files, I'm not too sure why.
I had the error message:
ERROR: STATUS_SEC_INSUFFICIENT_BUFFER
Verified boot is enabled
Please download signed image (sutinfo-verified.img) or disable verified boot
I didn't know how to do either of these, so I skipped the three problematic files: sutinfo.img, systeminfo_a.img, and cda_a.img (not sure what they do?).
It worked and un-bricked the phone, but it now boots to recovery mode only. What puzzles me is that I also no longer have access to fastboot, even when I reboot to bootloader (as if it skipped bootloader and went straight to recovery). I suspect it is because it still boots on slot B but I don't know how I can check that or change it back to slot A without fastboot access.
I tried using adb: adb shell getprop ro.boot_suffix but although it can see the device, it failed because it says device is unauthorized. I've tried all the fixes for this I found, to no avail.
So that's where I am, able to boot to recovery (but with adb unauthorized), able to flash firmware (except those files that must be signed), and unable to access fastboot.
I'm giving up hope that it's repairable, but I'd love to at least understand what happened, if someone has any idea...
Sorry for the long story...

Stuck in bootloop, TWRP crashes

Hi,
Since yesterday, my phone suddenly went into a bootloop (I wasn't even using it, but it suddenly started vibrating every half a minute or so). I'm able to get into fastboot mode, but from there if I try to boot into TWRP, it just shows the splash screen for a bit, and then crashes and reboots again. I should say that this is my brother's old phone he gave to me, so I'm not exactly sure what he's done to it, and I'm also not particularly familiar with Android stuff myself.
Is there anything I could try to retrieve data from the device? I've managed to run a different recovery img (included in here: https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_One/), which allowed me to use ADB from my MacBook, and from there I tried to use the adb backup command, but this just gives me "Now unlock your device and confirm the backup operation..." without actually showing anything on the phone.
And even if I can't recover anything, is there anything I could try to bring the device back into a working state?

since your fastboot is working, you can try downloading the bacon roottoolkit and restore stock rom, before doing that install all the drivers like it mentions in the app. https://androidfilehost.com/?fid=95916177934555863;
Let me know if this works