[Q] (Help: Can't boot) Lollipop + eager urge for Xposed - T-Mobile LG G3

I'm going to be away soon and won't have easy access to a non-professional PC (meaning any computer I may have access to - I won't have admin rights with). I didn't want to wait for a root+TWRP dev package for Lollipop to be released. I wanted to just get it done, (I was having bad problems with KitKat on some select apps because of LG's 4.4 coding, long story, but I won't even go there...)
I saw that I can go to the LG support site via a link from Android Central and manually upgrade to Lollipop way before the OTA rollout even begins. I had heard rumors of people having problems, read posts, and learned how to avoid it all. I reset everything before upgrading. I did many factory resets after getting Lollipop, (I know, a lot). I got rooted and set mostly everything up.
I wanted to get Xposed loaded, BADLY. I looked it up for Lollipop and realized that I'd have to flash a custom recovery. I expected as much. When I looked that up, I realized that I would have to either use a downgrade-upgrade method (which I didn't feel like going through) or a mandatory requirement of factory reset though a process. I had already set up all of the system stuff and restored from Titanium backup most of my apps. There was no way I would factory reset because I hate resetting-up the system stuff. - - - - - BIG MISTAKE 1
So I found a thread for the D850 (AT&T) version (no I didn't flash a bad radio or anything, I thought I knew what I was doing because I was only flashing recovery stuff for Lollipop, not an AT&T rom or radio.) This was to install TWRP without downgrading or resetting. The instructions said to copy files from an aboot.img and other boot images and such (to replace the recovery) on to the internal memory and use a terminal to type in code. I did it and rebooted it.
I made a horrible mistake.
When I held the power button on the phone, nothing happened. I found out that when plugging it in to the PC, it seems to be in download mode. It was fully charged. When using the restore/brick recovery software, I have tried different cables, different computers, checking to see if anything is corrupt, different USB ports, etc. with the files... Nothing will work. I keep getting an error with a red box about the model or something. "Model Information Check Fail"
So basically I have broken boot images on my device. I need to fix these.
Where do I go from here? All because I wanted Xposed on Lollipop without resetting.
Click to expand...
Click to collapse
I have this situation. I messed up with laf.img and aboot.img too (from D850, thinking it was harmless since trying to install custom recovery only) and device won't turn on but PC recognizes as download mode but can't flash. Please read above. I'm bricked and all restore methods have failed so far.
Source from u/nicksteron on reddit.

I'm having this issue now too. It seems the thing I downloaded and tried broke my boot images.
Have you been able to fix this?
I'm trying the LG Flash Tool but it stops me at the model check fail as well. Gonna try a kdz method next.
EDIT: I tried the KDZ method with LG Flash Tool 2014 using both a KitKat and Lollipop based ROMs and I get an error. The S/W Upgrade progress gets to 4% and then the error shows up. I need my phone. Help?!

Related

Bootloop on LG G Pad II 8.0 LTE (V497)

Hi!
Little background: I've had about every Nexus device that has been released and I've rooted them all, changed all their custom recovery, installed XPosed and fiddled around with ROMs all manually using adb and fastboot (never used a 1-click tool). Of course this is all relatively easy, since you can just go back and flash the original image if you mess something up.
Problem is, I messed up the LG G Pad and I'm kinda stuck. What I did to mess it up:
- No way I'm going without root and there's no way to flash a custom recovery
- Install Kingroot apk, ran it, got root
- Install supersu-me to remove kingroot and replace with SuperSU (the one I usually use and install via a zip in custom recovery)
- Reboot device....bootloop
- Find out the magical sequence to factory reset, do it
- Same bootloop
So it's now just stuck at the LG Life's Good (no it's not!!!) and I can't seem to be able to get adb to work anywhere, I've also gone into download mode, but I can't do much in there.
I'm open to all suggestions
Solution found?
Have you found a solution yet?
WarpedMonkeys said:
Hi!
Little background: I've had about every Nexus device that has been released and I've rooted them all, changed all their custom recovery, installed XPosed and fiddled around with ROMs all manually using adb and fastboot (never used a 1-click tool). Of course this is all relatively easy, since you can just go back and flash the original image if you mess something up.
Problem is, I messed up the LG G Pad and I'm kinda stuck. What I did to mess it up:
- No way I'm going without root and there's no way to flash a custom recovery
- Install Kingroot apk, ran it, got root
- Install supersu-me to remove kingroot and replace with SuperSU (the one I usually use and install via a zip in custom recovery)
- Reboot device....bootloop
- Find out the magical sequence to factory reset, do it
- Same bootloop
So it's now just stuck at the LG Life's Good (no it's not!!!) and I can't seem to be able to get adb to work anywhere, I've also gone into download mode, but I can't do much in there.
I'm open to all suggestions
Click to expand...
Click to collapse
Sadly my solution was to send it back. I said it stopped working after a Factory Reset, which isn't totally false. They accepted the RMA and I'm not going to root the new one I received.
Got stuck on my 495. Unfortunately I bought it second hand so I don't know if they will warranty my repair. err.... I'm hoping to find a solution. Did you ever try the LG Bridge software? I've had no luck with it.
PHP:
Hello. To root an lg-v497 simply use the mobile go trial on pc. To reset the tablet if it is in a boot loop simply use the lg support tool. You need to install the v500 driver for it to connect to the tablet. Factory reset will not fix it. You must re-flash firmware in this way.
Of course this may not be of use to many but it is what i have found works best. Hope this helps somebody. I went through that exact same scenario as you did, OP, and that is how i solved it. BUT now i am trying to find a way to crack the bootloader because i want to fix or get rid of 5.0.
Any Chance you could put links to the support tool and the driver? If I have KingRoot on already, should I restart or just uninstall before rooting with Mobile Go?
My account is apparently too new to post the links but just google the lg mobile usb driver and go to lg support page for the tool
To do a fresh flash you go to update recovery in the top menu when connected.You may have to fiddle with it a bit, good luck.
Flash it before using mobilego. Kingroot is a plague and you should get rid of it first.

VK810 Root and ROM Successful

I felt compelled to register here and post my success on getting LineageOS installed on my Verizon VK810 4G Altev LG G Pad tablet. It would not have been possible without this forum and the users who contribute, both with information and with uploads. I initially tried rooting with KingRoot and the OTA updated OS I had from Verizon but the app said there were 63 requests for rooting my device. Forget that idea. After also trying iRoot which wasn't working, I used the LG Flash Tool to downgrade to VK81035A and then was successfully able to root that. SuperSu definitely helped with the process. My guess is, even though both were Android 5.0.2, mine had OTA patches that I guess caused issues for rooting. Installing TWRP was a hassle though. None of the v500 TWRP images worked for me and many of the custom TWRP versions that I found on here did not work for me. You would not imagine the number of times I thought I bricked my device because I kept getting "Secure Booting Error! Cause: boot certification verify" errors. However, what did work for me was, using Platform-tools and VK810_twrp_2.7.0.1.zip for TWRP. For some reason, the other versions posted here did not work for me. It did take me a while to figure out how to get into TWRP because I kept using the Power-VolUp key combinations and it kept bringing me to what looked like LG's recovery menu. I didn't realize that the screen is actually fake and you have to click "Factory Reset/Wipe" on there to get into TWRP. It actually took me a long time to figure that out. With TWRP installed, I searched for ROMs that I could use that were newer than Android 5.0.2 and ended up downloading LineageOS as it came up for the VK810 and since VS500 ROMs weren't allowed to be installed. Now to be fair, the LineageOS Rom that I used (lineage-14.1-20171228_233442-UNOFFICIAL-vk810.zip) is pretty glitchy. The display likes to blink a lot, many apps crash on it and there is no cellular data working for me, but I assume that will possibly be fixed in the future and at least now, I can customize more than I could on stock. On first install, I also lost my root and forgot to install the GApps package from the Lineage website. Anyway, hope this helps at least one person here. Nothing was one-click for me, but I did learn a lot about the process of rooting and flashing, and now better than to automatically allow OTA updates. I do hope LineageOS or another ROM keeps updating for the VK810 because this tablet does not seem that popular and I would like to see Oreo. Thank you everyone for your help!
XDAnonymous said:
I felt compelled to register here and post my success on getting LineageOS installed on my Verizon VK810 4G Altev LG G Pad tablet. It would not have been possible without this forum and the users who contribute, both with information and with uploads. I initially tried rooting with KingRoot and the OTA updated OS I had from Verizon but the app said there were 63 requests for rooting my device. Forget that idea. After also trying iRoot which wasn't working, I used the LG Flash Tool to downgrade to VK81035A and then was successfully able to root that. SuperSu definitely helped with the process. My guess is, even though both were Android 5.0.2, mine had OTA patches that I guess caused issues for rooting. Installing TWRP was a hassle though. None of the v500 TWRP images worked for me and many of the custom TWRP versions that I found on here did not work for me. You would not imagine the number of times I thought I bricked my device because I kept getting "Secure Booting Error! Cause: boot certification verify" errors. However, what did work for me was, using Platform-tools and VK810_twrp_2.7.0.1.zip for TWRP. For some reason, the other versions posted here did not work for me. It did take me a while to figure out how to get into TWRP because I kept using the Power-VolUp key combinations and it kept bringing me to what looked like LG's recovery menu. I didn't realize that the screen is actually fake and you have to click "Factory Reset/Wipe" on there to get into TWRP. It actually took me a long time to figure that out. With TWRP installed, I searched for ROMs that I could use that were newer than Android 5.0.2 and ended up downloading LineageOS as it came up for the VK810 and since VS500 ROMs weren't allowed to be installed. Now to be fair, the LineageOS Rom that I used (lineage-14.1-20171228_233442-UNOFFICIAL-vk810.zip) is pretty glitchy. The display likes to blink a lot, many apps crash on it and there is no cellular data working for me, but I assume that will possibly be fixed in the future and at least now, I can customize more than I could on stock. On first install, I also lost my root and forgot to install the GApps package from the Lineage website. Anyway, hope this helps at least one person here. Nothing was one-click for me, but I did learn a lot about the process of rooting and flashing, and now better than to automatically allow OTA updates. I do hope LineageOS or another ROM keeps updating for the VK810 because this tablet does not seem that popular and I would like to see Oreo. Thank you everyone for your help!
Click to expand...
Click to collapse
Wow thank you so much I thought it was me having issues. I have a 410vk and as you said nothing was one click. I hope to continue to try and get root on the G Pad. Still an awesome device.
Sent from my LG-H932 using Tapatalk
XDAnonymous said:
I felt compelled to register here and post my success on getting LineageOS installed on my Verizon VK810 4G Altev LG G Pad tablet. It would not have been possible without this forum and the users who contribute, both with information and with uploads. I initially tried rooting with KingRoot and the OTA updated OS I had from Verizon but the app said there were 63 requests for rooting my device. Forget that idea. After also trying iRoot which wasn't working, I used the LG Flash Tool to downgrade to VK81035A and then was successfully able to root that. SuperSu definitely helped with the process. My guess is, even though both were Android 5.0.2, mine had OTA patches that I guess caused issues for rooting. Installing TWRP was a hassle though. None of the v500 TWRP images worked for me and many of the custom TWRP versions that I found on here did not work for me. You would not imagine the number of times I thought I bricked my device because I kept getting "Secure Booting Error! Cause: boot certification verify" errors. However, what did work for me was, using Platform-tools and VK810_twrp_2.7.0.1.zip for TWRP. For some reason, the other versions posted here did not work for me. It did take me a while to figure out how to get into TWRP because I kept using the Power-VolUp key combinations and it kept bringing me to what looked like LG's recovery menu. I didn't realize that the screen is actually fake and you have to click "Factory Reset/Wipe" on there to get into TWRP. It actually took me a long time to figure that out. With TWRP installed, I searched for ROMs that I could use that were newer than Android 5.0.2 and ended up downloading LineageOS as it came up for the VK810 and since VS500 ROMs weren't allowed to be installed. Now to be fair, the LineageOS Rom that I used (lineage-14.1-20171228_233442-UNOFFICIAL-vk810.zip) is pretty glitchy. The display likes to blink a lot, many apps crash on it and there is no cellular data working for me, but I assume that will possibly be fixed in the future and at least now, I can customize more than I could on stock. On first install, I also lost my root and forgot to install the GApps package from the Lineage website. Anyway, hope this helps at least one person here. Nothing was one-click for me, but I did learn a lot about the process of rooting and flashing, and now better than to automatically allow OTA updates. I do hope LineageOS or another ROM keeps updating for the VK810 because this tablet does not seem that popular and I would like to see Oreo. Thank you everyone for your help!
Click to expand...
Click to collapse
Can you link where you got the ROM? Is anyone actively working on it? Really too bad the vk810 never got much love, great little device. Been awhile since I've done anything with it, it's my dad's so I got it rooted on 5.0.2 and just kinda left it alone. What prompted me to come back to this forum is screen mirroring won't work. The tablet sees TV and vice versa, it tries to connect but never completes the connection, just kicks back to satellite TV after a couple of seconds of black screen. Don't suppose you tried casting on that lineage build?
AirForceOnes0010 said:
Can you link where you got the ROM? Is anyone actively working on it? Really too bad the vk810 never got much love, great little device. Been awhile since I've done anything with it, it's my dad's so I got it rooted on 5.0.2 and just kinda left it alone. What prompted me to come back to this forum is screen mirroring won't work. The tablet sees TV and vice versa, it tries to connect but never completes the connection, just kicks back to satellite TV after a couple of seconds of black screen. Don't suppose you tried casting on that lineage build?
Click to expand...
Click to collapse
I got the ROM from the Invisiblek ROMS site under /roms/lineage-14.1/vk810/ (Can't post the link as I'm currently under 10 posts)
It's definitely a start. There is screen glitching, and no LTE service (Wi-Fi only), so it definitely limits the tablet. I have not done much with it as it was a hassle just to get the root within the OS to work correctly. Some apps aren't detecting root when the OS is trying to give it to them.
XDAnonymous said:
I got the ROM from the Invisiblek ROMS site under /roms/lineage-14.1/vk810/ (Can't post the link as I'm currently under 10 posts)
It's definitely a start. There is screen glitching, and no LTE service (Wi-Fi only), so it definitely limits the tablet. I have not done much with it as it was a hassle just to get the root within the OS to work correctly. Some apps aren't detecting root when the OS is trying to give it to them.
Click to expand...
Click to collapse
It'll have to wait until/if LTE is ever functional then, my parents don't have internet other 4g out in the sticks lol. Google took me right to it, thanks. Will keep it bookmarked just in case
I'd like to write about my experience too as it took me some time to finally get the device up and running.
I will describe what I wanted to do, what mistakes I've made and what should've been the correct way.
The device itself is LG G Pad 8.3, Verizon LTE variant aka vk810
Initally I received it in a bricked state, on launching it showed the "Secure booting error" message and that's it.
1) Unbricking
The goal was to install an official LG system image and restore the tablet to a working state.
Basically, I did everything according to the steps outlined here: https://forum.xda-developers.com/lg-g-pad-83/general/vk810-4g-reliable-to-root-install-t3283027
Installed LG drivers
Downloaded the LG Flash Tool 2104
Downloaded a KDZ image
Plugged the device in the download mode into the PC and installed the KDZ using the flash tool
At that point I got a fancy idea to install a non-stock Android on this tablet.
2) Lineage OS
I chose this OS for my tablet, because it seems to be the current standard for non-stock Android installations.
I followed these installation instructions: https://wiki.lineageos.org/devices/v500/install
BEWARE: that page is for v500, so it won't work for vk810.
Lineage doesn't support vk810 officially. A mistake I've made was assuming that I can just roll along with a v500 installation. Actually, you kinda can, but for me it resulted in Wi-Fi not working and my device's MAC address being 02:00:00:00:00:00.
3) Rooting
I was quite confused here too: there are different rooting methods, and some of them can be applied in different ways.
Ultimately I found Stump to be the most comfortable for me: https://forum.xda-developers.com/lg...root-stump-root-lg-g3-sprint-verizon-t2850906
It works fine on this device and uses a very straightforward process: download APK to your PC, connect the tablet to the PC, "adb install <filename>.apk", then launch the app and that's it. It had to go through the bruteforce process to root, which took several minutes.
4) TWRP
I don't remember what exact TWRP I installed initially, but it was a 3.x version, and I encountered an issue where it couldn't mount any of the tablet's partitions. That was quite a pain in the ass.
For a while I resorted to using an older version, 2.7.x, and it worked fine.
Ultimately what I'm the most happy with is this: https://forum.xda-developers.com/lg-g-pad-83/general/vk810-twrp-3-1-1-0-unofficial-t3691551
The lesson learned here is that, again, you need to make sure stuff you install is compatible with your device.
Ultimately, after making mistakes at each step of the process, I figured out everything, and just followed the installation instructions on the Lineage page I linked earlier.
* Flash stock rom
* Root using Stump
* Enable USB debugging on the tablet, install Stump via adb and root the device
* Install vk810 variant of TWRP 3.2.1-0 via adb
* Reboot to recovery (turn off the tablet -> hold Volume Down + Power -> you should get a factory reset menu after the LG logo -> select factory reset, then confirm it and you'll be booted into TWRP. That factory reset is fake after you have TWRP installed)
* Wipe everything
* adb push the lineage / lineage's su / opengapps onto the device
* Install lineage, then su and opengapps and you're good to go
Main lesson learned: it is CRUCIAL to make sure stuff you install is compatible with your particular device. Do not assume that you can use another version, even if it is made for a device of the same family.
Just to provide an update here, this is where the ROM that I used came from: https://updater.invisiblek.org/vk810
The latest version at this time seems to be this: lineage-17.1-20200329-UNOFFICIAL-vk810.zip
XDAnonymous said:
Just to provide an update here, this is where the ROM that I used came from: https://updater.invisiblek.org/vk810
The latest version at this time seems to be this: lineage-17.1-20200329-UNOFFICIAL-vk810.zip
Click to expand...
Click to collapse
Thanks for all the great information, but I have the VK810 that has usb connection problems. It will connect, but it keeps dropping (it cannot be trusted with usb cord). I have wanted to root, twrp, magisk and other things just to play around to see what it can do or how far I can go with it. I am not afraid to trash it. Have you or anyone else had this problem? I have reset it, wiped it out, factory settings, but nothing seems to help that usb port. I was thinking that reflashing the rom might help. Any advice is appreciated.

[HELP][G3][VS985]issue connecting to PC on fastboot, need to reflash TWRP & SuperSU

[HELP][G3][VS985]issue connecting to PC on fastboot, need to reflash TWRP & SuperSU
Hello, thank you for this great forum with helpful members, I'm having an issue with an LG G3 VS985, fastboot won't recognize it while in bootloader, I need to reflash TWRP.
First of all, thank you for reading this long testament [most important details in bold if TL;TR], wanted to be as detailed as possible, maybe it will help you help me better hehe sorry about that.
Let me give you the event sequence if it helps.
> Phone had Cloudy G3 2.5 rooted with SuperSU and TWRP 2.8.6.0 since I rooted it back in 2016.
I was having some issues with phone not recognizing micro sd card and OTG-USB after messing around with encrypting it, I was curious but didn't need it, anyways. Although I dropped the phone in water a couple weeks prior so there is a chance the issue is hardware related.
That was like 4-5 months ago.
Finally decided to do a file backup and reinstall everything yesterday apr-5-2019.
> Rebooted into TWRP and erased everything (data, cache, dalvik, system, even internal storage) because I wanted a new install on everything.
> Flashed the latest official TWRP version for my device (3.0.2.0)
> Had a lot of issues flashing crDroid, found out I downloaded the wrong build, although I had to edit updater-script on the right one to make it work.
> Flashed crDroid 5.2_20190326 with open GApps for Android 9.0 Stock
> First issue encountered, I couldn't charge the phone turned off, because the battery logo appears but but doesn't do the animation and reboots the phone, I read it might be an issue with TWRP.
> Tried to flash SuperSU 2.82 SR5 with TWRP but had a LG secure boot error and couldn't boot up android.
> RE-flashing android and open GApps fixed this issue.
> Re-attempted the process several times, even wiping everything down more than a couple times, including re-flashing android several times to no avail, I was not able to flash SuperSU successfully.
I even flashed an old tool "MR.Bump" but system kept unrooted so unsuccessful.
> Reflashed Android for the last time and start reading again (after 8 hours attempting to do it well), I read that TWRP version might be the problem to flash SuperSU, so
HERE is where I have the current issue:
> Downloaded the official TWRP version 3.1.0 and flashed it.
There is no official support for 3.1.0 for the VS985 so I'm guessing it was a generic .img, of course I messed up TWRP.
> Downloaded and installed official LGMobile Drivers 4.2.0 (latest), downloaded android drivers (15 second ADB installer 1.4.3) and Android platform tools 28.0.2 on windows.
> When conected in PTP and transfer files in win7 it recognizes all the drivers well, was able to reboot the phone into bootloader from android platform tools successfully, means there is good communication between the device and PC.
The issue is once the phone is in the bootloader and trying to flash TWRP, win7 has issues installing CDC serial drivers, in the end in device manager all drivers seems installed but win notification center says there was a problem installing LGE AndroidNet for VZW USB Modem, seems to be issues with CDC Serial or something, when trying to access the properties on the VZW USB Modem it freezes so there's an issue here.
That means when doing adb devices or fastboot devices command, doesn't find anything.
Tried the same in win10, had different driver problems but in the end everything gets installed after rebooting. Same issue, no response from phone when in bootloader.
Message is "Waiting for any device".
Maybe there is an issue with some low-level driver/kernel/firmware that is creating this issue, I would even consider to flash stock LG Android to start from scratch, if you have any guide on how to do it please provide the links!
Additional note: When connecting the phone in USB Tethering win7 gives bluescreen.
> FORTUNATELY I messed TWRP but the phone can still boot android so it's not rendered unusable (yet lol).
I must admit I wasn't super careful downloading some stuff, I did it old school (trial and error) and most of the times it works, I consider myself being a little tech savvy, but right now I'm stuck, I guess I could continue using the phone like this but if I have any issues it would be difficult to resolve and I would lose functionality without root (I could live unrooted though but I wanna resolve this) and honestly I love the G3 so why change it? haha.
BTW I found these on the net, do you recommend it? what TWRP do you recommend for the VS985?
I downloaded and wanted to install this one https://forum.xda-developers.com/lg-g3/development/recovery-unofficial-multirom-twrp-artx-t3657524
and found this one supposedly 3.2.1 for the vs985 here: https://basketbuild.com/devs/yshalsager/TwrpBuilder/lge/vs985
Any help will be greatly appreciated.
Cheers.
I posted it on a different area and got no response, so here it is the G3 area.
@disrupted_mind, wow, that was a great detailed post. Alas, can't think of anything much to suggest at the moment. Just a few things come to mind.
Make sure to use a USB 2.0 port on the computer. I've heard of issues with USB 3.0.
Use a good cable but I assume yours is good or original.
There's another TWRP from @HardStyl3r, v3.2.3. Since he's one of our last ROM devs I'm sure it might be the one to use, especially if you're trying Pie.
https://forum.xda-developers.com/showthread.php?t=3813552
[RECOVERY][3.2.3.0][UNOFFICIAL] TeamWin Recovery Project for LG G3
Let us know if that one works or not.
LG G3 D851, AOSPA-L ROM, Nebula Rev9.3 Kernel, microG (NoGapps), MultiROM, XDA Legacy
marcdw said:
@disrupted_mind, wow, that was a great detailed post. Alas, can't think of anything much to suggest at the moment. Just a few things come to mind.
Make sure to use a USB 2.0 port on the computer. I've heard of issues with USB 3.0.
Use a good cable but I assume yours is good or original.
Click to expand...
Click to collapse
Thank you for replying, now that you mention it, all the ports on the PC's I've tried are USB 3.0, I think I have an older lappy with USB 2.0 and I will try that next. If that doesn't work I was planning on rooting the phone temporarily with kingroot or kingoroot, so I can use flashify and re-flash TWRP (just thought about it last night hehe) and then re-flash the ROM since according to this thread, kingroot and kingoroot might be malware.
marcdw said:
There's another TWRP from @HardStyl3r, v3.2.3. Since he's one of our last ROM devs I'm sure it might be the one to use, especially if you're trying Pie.
https://forum.xda-developers.com/showthread.php?t=3813552
[RECOVERY][3.2.3.0][UNOFFICIAL] TeamWin Recovery Project for LG G3
Let us know if that one works or not.
LG G3 D851, AOSPA-L ROM, Nebula Rev9.3 Kernel, microG (NoGapps), MultiROM, XDA Legacy
Click to expand...
Click to collapse
Thanks, yes, precisely yesterday I kept reading trying to find a solution and bumped into @HardStyl3r's version, already downloaded it
I like Pie very much by the way, but I think it drains the battery a little faster than CloudyG3 (android 5), maybe the old hardware struggles too much haha, but I will keep using it for some time. By the way, do you think AppOps is still necessary with Android integration to allow/deny permissions (sorry, noobie question since I'm just transitioning from old to newer android with that feature).
Any ideas on the charging the phone off issue?
I will update the thread with any news
Cheers.
I have good news and bad news.
I was able to reflash stock KitKat using TOT method, only way it could work since I had no connection to PC with fastboot commands on cmd.
Updated android over the air and PC, it update to 5.0.1 over the air and wanted to go faster so tried to do it from PC, what a mistake, when I was downloading Marshmallow info on xda I found that it might be difficult to root android 6, so cancelled the operation from LG Update Software on PC. That went "fine", didn't update to Marshmallow.
Rooted the phone using the One-Click root method, worked fine apparently. Installed flashify and flashed the Unofficial 3.2.3 TWRP, that didn't go well, I dont have access to Recovery mode nor Bootloader/Download mode now. "Recovery" ("vol-" + "Power Button") mode gives "certificate/secure boot error", Regular "Bootloader/Download mode" is non-existant or I can't access it in any given way, tried "vol+" while off + "Power Button", tried to reboot to it from Rashr, nope, it just continues to boot android, the other "Download mode ("Vol+" + "Connect USB cable to PC")" (don't know if it's the same as Bootloader) gives "certificate/secure boot error". I even flashed the latest official TWRP for vs985 and 2.8.6 that I knew definately worked before, didn't work.
I was able to boot into fastboot following "this" thread but it doesn't perform commands.
When booting to Android I kept receiving notification that I had a pending update, I managed to wipe /data and /dalvik from adb shell, that resolved that issue.
Attempted to reflash stock KitKat again, but I can't, since phone doesn't have bootloader or recovery no more.
At least I still have working rooted 5.0.1 Lollipop, but have the other issues. I want to attempt to re-flash aboot.img, laf.img and sbl1.img to fix those issues but since its my main phone don't want to hard brick it right now.
Any input is welcome and appreciated, will keep reading a lot, think I might open a different thread for this.
Cheers.

Soft Bricked LG G3, trying to get LineageOS on it. (Success!)

I was needing a new phone and saw a Linus Tech Tips video where he took an LG G3 and put LineageOS on it. So I thought I'd try it out for myself following his guidelines at https://linustechtips.com/main/topic/1058206-lg-g3-lineageos-tutorial/
I bought an LG G3 D851 (T-Mobile version) off EBay for this. It's my first Android phone (yes, experimenting on my first Android Phone), I've always used Windows phones. This is what I've done to the LG G3 so far:
I reverted back to KitKat. Everything seemed to have gone just fine.
Then I downloaded the the Full Purple Drake Root and ran that after I figured out that .gz files are a compressed file and that can be decompressed. Everything seemed to have worked fine.
Then I downloaded the TWRP app on the phone and tried to backup the recovery via the TWRP app, which I'm not sure if it worked correctly. But anyhow.
Now that I'm writing this I see I missed this step:
number seven: Select the TWRP file we copied over earlier in the app, flash it to recovery, and then reboot to recovery
Click to expand...
Click to collapse
I guess I just didn't understand what was meant by flashing it over and has just copied it to the phone's memory which I later wiped.
Well then I went into TWRP recovery and tried to do a recovery backup, which it seemed to do just fine. I rebooted and tried copying it over to the computer, which seems to not have worked. I just have an empty folder on my computer as we speak.
Then back in the TWRP recovery, I selected Wipe>Advanced Wipe, and select Dalvik, Cache, Data, Internal Storage, and System – then swipe to wipe.
Then I downloaded the latest version and nightly of LineageOS zip file and the Opengapps zip file but then had a hard time figuring how to get them to the phone.
I figured out that I could stick them on an SD card and slip it into the LG G3 that I'm working on and could see the files from the TWRP recovery menu.
So I tried to install the LIneageOS zip file several times and it didn't work. I'm guessing it's because I forgot to flash a certain file to TWRP recovery and am not sure how to do that, especially now with the phone only booting into recovery mode with the TWRP menu since it's wiped clean and will just display the LG logo and turn the LED different colors if I try to normal boot the phone.
Well I still want to try to fix the phone and go for LineageOS. I spent nearly all night working on it so I may give it a rest for a few days. But any help or pointers would be greatly appreciated.
Now that I think about it, I didn't do what I mentioned ok #4 above about flashing the TWRP recovery because TWRP recovery was installed with the full Purple Drake root. However, the Linus Tech Tips instructions point to them rooting the phone with the lite version of Purple Drake (root only) and then flashing the newest version of TWRP recovery. So I wonder if my problem has to do with my having the latest version of TWRP recovery on my phone.
Ok. So I think I'm making progress, although that's just a feeling I have since I'm not suite what I'm really doing.
Anyhow the error code was something like "Unknown Error, Error Executing Updater Binary in Zip, Zip is for LG G3 D851, this phone is...(blank)". So I found an article in DroidThunder.com talking about this very problem. It suggested unzipping the rom on my computer and looking for the updater-script file and erasing some lines that apparently only have to do with verification. Then re-zip and retry.
Now I'm getting a "No MD5 file" message followed by an "Error flashing zip" message.
Edit: After reading this I take it I have an older version of TWRP, that is, v2.7.1.0, whereas the newet versio (for this phone?) is apparently 3.3.1-0. That seems to have an effect on this. I wonder if it's possibly to flash a newer version of TWRP onto this bricked phone. Anyhow, I'll have to look into that later. It's time to call it a day.
So recently I've been focusing on these two threads:
[GUIDE] LG G3 D851 Unbrick Qualcomm 9008 Fully Working... Unbrickable D851! by Omar-Avelar
And:
[GUIDE][FIX][DISCUSSION] LG G3 Hard Brick Recovery by l33tlinuxh4x0r
But I can't get either of them to work. I guess the only other thing would be to try to find a ROM, preferably the original KitKat that came with the phone, and hope and pray that I can get TWRP recovery v2.7 to install it.
I have the original as a tot file. But as far as I understand, I need a zip file that's set up for TWRP recovery.
Anyhow, trying to get this phone running hasn't been easy and has made other problems. Now every time I turn on my Surface 3 I have to go through BitLocker authentication. Hopefully turning bcd Test Signing off will stop that. But I'm getting to the point that I'm feeling like giving up.
Well that's it. Last night I found a zip file for the original Marshmallow ROM for my G3. I got it onto the SD card, went into TWRP recovery, saw it install, restarted and...
Now it's hard bricked. I cannot even get into TWRP recovery. The screen won't show a thing. I tried several times to get it into any mode possible, normal boot, TWRP recovery boot, download mode, and that jumping the pins trick, and I can't get it to where I can do something with the phone.
So I'm giving up on all this rooting, custom recoveries and custom ROM stuff. It all seems like a good idea, and I'd love to be a part of it all. But I take it this isn't for me. So I give up.
Thanks to all who have worked on this and have made the helpful forums about these phones! Maybe if I were more competent I would have figured it out.
Well, I said I was giving up. But maybe not. I did give up trying to recover the phone from being bricked and sent it out to a JTAG shop. For about $40 the phone is supposedly fixed and on it's way back.
But when it's back, do I just leave it alone this time, or should I try to get Lineage OS back on it again? Well, this is something that I haven't made my mind up yet. I see where I had made several mistakes when I first tried to get LineageOS on it. Maybe I know enough now that it won't happen again. But at the same time there's no guarantee that I won't me it up again, and have to pay some $40 again to have it unbricked.
SUCCESS!!!
So I got my phone back with stock Marshmallow working. Then I carefully went through every step on the Linus Tech Tips site, including installing the latest version of TWRP, and the next thing I know I'm running LineageOS 16 on my phone!
This is great! It's my first Android Phone and I've got it setup just about perfect! The only thing I kind of miss is Wi-Fi calling. But that didn't work so well on the Alcatel Window's phones I had anyway. But I got all the apps and most of the music I need installed and am ready to go! I also have two batteries, and the original isn't too bad, so I might carry that around as a backup until I'm sure how much battery I'll be using.
I'll be coming back and thanking all the ones who's posts and work have helped me individually. But if you read this and are one of those who have worked on TWRP, LineageOS and anything else that has helped me, Thank You!

Question Bricked for Days and usable WiFi is $$$ for vanlife, help!

I was ALL good with my Pixel 6 pro, rooted and hours of tweaks in. My idiotic mistake here was I did not make a flashable backup before flashing the magisk-rooted despair kernel. Instead, because of laziness to find a nandroid backup method, I made a half-assed backup by dragging and dropping on my pc, and this has cost me.
Immediately after flashing via the 99 cent kernel flash app (can't remember the name) I was getting caught in the G loading screen bootloop.
Since then, I've tried everything. Every combination of every fastboot command I have found, on Windows and Ubuntu, multiple cables, etc. This has worked for me in every version of Android since 4.0 or earlier, as I've gone this whole time without really gaining understanding of any of the back end.
Now I cannot enter fastbootd. I get errors in fastboot that the "/system" partition does not exist. I have no stock recovery and can only enter Fastboot bootloader mode. GrapheneOS will not install due to an error at the final step indicating that fastboot is too old, despite the updates I keep reinstalling (Graphene web installer failing on download portion). Stock Recovery Flash Tool never works for me, always an error on the download. When manually flashing Stock, I am hit with the missing system partition error, the error that the image is too large for the partition, cannot determine image filename, etc.
Now, fastboot reboot bootloader doesn't even work until i unplug and replug the phone back in. And no flashing commands are attempted until the phone is unplugged/replugged. My bootloader is still unlocked as confirmed by the fastboot oem unlock command response.
Essentially I believe I am in need of a complete wipe, beyond anything I've done yet. I think I need to create new partitions before flashing? Someone please help me I'm dead in the water and on motel wifi to try and fix this stubborn beast.
When I first got my pixel 6 pro, I didn't let the update fully install and ended up using the web flasher to get it working again. Have you tried that? It'll be a full wipe but at least you would have your device.
bigdog1459 said:
When I first got my pixel 6 pro, I didn't let the update fully install and ended up using the web flasher to get it working again. Have you tried that? It'll be a full wipe but at least you would have your device.
Click to expand...
Click to collapse
Oh I've wiped it along the way already, since the "incident" of the kernel flash. Multiple ways. I would love to use the web flasher, but it just doesn't work for me. The download never completes, and I suspect even if it did that at this point it would get stuck right away and throw me an error message, likely deleting the whole download along with it.
nastyneighbor said:
Oh I've wiped it along the way already, since the "incident" of the kernel flash. Multiple ways. I would love to use the web flasher, but it just doesn't work for me. The download never completes, and I suspect even if it did that at this point it would get stuck right away and throw me an error message, likely deleting the whole download along with it.
Click to expand...
Click to collapse
Damn. I'm sure you have tried some of the manual flashing guides out there too?
nastyneighbor said:
I was ALL good with my Pixel 6 pro, rooted and hours of tweaks in. My idiotic mistake here was I did not make a flashable backup before flashing the magisk-rooted despair kernel. Instead, because of laziness to find a nandroid backup method, I made a half-assed backup by dragging and dropping on my pc, and this has cost me.
Immediately after flashing via the 99 cent kernel flash app (can't remember the name) I was getting caught in the G loading screen bootloop.
Since then, I've tried everything. Every combination of every fastboot command I have found, on Windows and Ubuntu, multiple cables, etc. This has worked for me in every version of Android since 4.0 or earlier, as I've gone this whole time without really gaining understanding of any of the back end.
Now I cannot enter fastbootd. I get errors in fastboot that the "/system" partition does not exist. I have no stock recovery and can only enter Fastboot bootloader mode. GrapheneOS will not install due to an error at the final step indicating that fastboot is too old, despite the updates I keep reinstalling (Graphene web installer failing on download portion). Stock Recovery Flash Tool never works for me, always an error on the download. When manually flashing Stock, I am hit with the missing system partition error, the error that the image is too large for the partition, cannot determine image filename, etc.
Now, fastboot reboot bootloader doesn't even work until i unplug and replug the phone back in. And no flashing commands are attempted until the phone is unplugged/replugged. My bootloader is still unlocked as confirmed by the fastboot oem unlock command response.
Essentially I believe I am in need of a complete wipe, beyond anything I've done yet. I think I need to create new partitions before flashing? Someone please help me I'm dead in the water and on motel wifi to try and fix this stubborn beast.
Click to expand...
Click to collapse
Not sure when you said you used "Stock Recovery Flash Tool" if you meant the "Android Flash Tool". But just in case you didn't, that can force flash partitions with it. Probably your best shot.
Android Flash Tool
flash.android.com
Android Flashing Tool online unbricked me the other day. You have to be patient with the tool as it took me several tries. It will totally wipe your phone, but at this point you just need to rescue your device. Keep us posted.
thanks for the tip. i'm trying the android flash tool again now. and will keep trying it until it at least passes the download stage. and yes i tried all the manual flashing guides out there...and hybrid combos of all as well. i mean i'm positive its my fault for missing SOMEthing somewhere but many hours have been spent with overall negative progress.
my track record is still zero hard bricked devices or soft ones I couldn't fix over all these years so i'm not too worried but i could use my phone back haha
will keep posted as requested. ty again.
I know this doesn't help your immediate situation, but when flashing anything like custom kernels, I would advise not to use some random app to flash it with, just follow the directions in the OP of the kernel's thread, and make sure you have up to date Platform Tools and driver. CleanSlate and many or all the custom kernels also require flashing more than just the boot.img.
Good luck, I hope you get it back working for you.
Hey guys, the Android Flashing Tool finally worked for me and I am up and running again. Thanks for your help and tips. Hacking phones is more important every year and thus I truly value your skills and advice. This community must survive the new world order. much love folks

Categories

Resources