Search results

TWRP version 3.3.1-0, required me to update the bootloader from 0x4111 to 0x411A. When I try to download any APK with Jelly browser, Jelly crashes. Anyone know a solution to this? I didn't install GAPPS. ---------- Post added at 05:01 AM ---------- Previous post was at 05:01 AM ----------...

It seems Lineage 14.1 uses boot loader 0x4111, instead of 0x411A. Edit: The following resolved it https://forum.xda-developers.com/moto-g/general/falcon-bootloader-upgrader-tool-t3093793

As soon as I select 'ADB sideload' on TWRP, the phone is no longer recognized by the desktop computer nor ADB.exe... But when I select cancel, the device is then recognized. This is version 3.3.1-0 Edit: It seems to only logical solution is to use 'adb push [image_name] /sdcard/.'

I'd like the assistant button to display the following screen. Any suggestion? [COLOR="Silver"]

If the phone wasn't a T-Mobile: May be able to flash v35.eng img onto the phone's abl_a partition (make sure this is backed up), then use fastboot commands to copy over the laf_a/_b files of the stock img. Then use download mode to revert back to Android 8/oreo. May need to use, fastboot boot...

I'd also like to add that Google Pay will not work, at retail brick and mortar stores. A pop up says device may be rooted or modified. I have magisk installed and it seems to trick Schwab banking app. Edit:

App name is unreadable due to the black font.

I have one of these phones, I got from eBay. I was able to root it and install the Pie '20e' firmware update manually. The ATT MVNO works on it, but the reception is really low, and worse than my 6 year old Motorola Moto G. I live in the Baltimore metro, 20 minute drive from the city's...

Thanks for the response. I was able resolve it with the following:

I was able to solve it. The magisk patched IMG file by this OP was flashed to both boot_a and boot_b, then executed 'fastboot reboot'; yeah boot_a and boot_b need to be flashed with an identical file. https://mega.nz/#!uqZFDKZQ!5dOCFKElmMOXnAMel7dSvyhGY5RkJjBsMwM-kH7eOGo The screen booted...

Anyone have a link to the LGUP_Common.dll file used in the video? My version is 1.0.31.9 instead of 1.0.36.10. Mine crashed after 91% on the phone's screen, nearly bricking me.

Anyone know the command line syntax to execute the following?

Does anyone know the cmd syntax to execute the following? I.e. 'partition dl' is selected, and every partition but boot_a/_b is selected for installation. LGUP 1.15 GUI asks for a login making it un-usable for most on here. Edit: This post may correspond with using the right version of LGUP...

Same here: According to multiple google searches LGUP is not properly patched. I then made the mistake of using an older version of LGUP, that doesn't give you the option to disable boot_a/_b partitions from being over written; which was a foolish mistake. I'd like to add that Pie LG stock...

Just to let everyone know, once you upgrade to Pie, QFIL can not be used to place files onto the partition, but to read or erase.

No. I rooted with QFIL and V35eng.img → abl_a (after backing up abl_a). Then did fastboot oem unlock, re-inserted the backed up abl_a.img file, then did the magisk patch up to boot_a/_b.

I successfully rooted my crossflashed spring LG G7 using the guide you linked, and this verizon guide. I never updated to 11g image. I manually patched the boot_a and boot_b image within Magisk GUI app, within the phone itself. Other guides mention disabling/erasing certain partitions: the...

At 7:28 of the following video, boot_a and boot_b are unchecked, AFTER the partition 'radio button' is selected at 7:19 https://www.youtube.com/watch?v=ylBSZk7EqcA May someone tell me why I'd install the boot_twrp-june.img over the patched_magisk.img located on boot_a & boot_b, if I have no...

You have to do one of the following: Edit: Disregard, doing the following will lock you out of download mode and stock Pie boot img don't support fastboot.. In ADB, according to this guide: Permit 'Shell' in Magisk superuser access AFTER executing the following: adb shell su dd if=/dev/zero...

Where did you dtbo.img from? I was able to obtain, system.img from the instructions here, vendor/vbmeta from here. BTW extract_android_ota_payload doesn't work for me: https://i.imgur.com/W6hjeus.png

Doesn't work for me. https://i.imgur.com/Mji8X7M.png The following worked for me, albeit a bit messy: https://androidmtk.com/extract-kdz-firmware

I placed sdat2img.py in the same directory as system.new.dat.br: https://i.imgur.com/5hJKw6M.png Then I executed the following: E:\HIS Documents\Computer guides\LG G7\Softwares\lineage\lineage zip extract>C:\ ProgramData\Python\python sdat2img.py system.transfer.list system.new.dat system .img...

How do I go about to un-zero the following? This is similar to the act of deletion. dd if=/dev/zero of=/dev/block/bootdevice/by-name/laf_a dd if=/dev/zero of=/dev/block/bootdevice/by-name/boot_b Edit: I had to place 'adb shell su' in front of dd if=.., AND I had to permit 'Shell' in Magisk...

You can get into fastboot mode to determine whether your phone uses abl_a or abl_b, AFTER flashing with v35eng.img, as seen in 3rd second of the following video: /watch?v=kN7oNBslgck

Got an error message saying, original abl_a.bin file is too large to download, it's only 1.0 MB i.imgur.com/oxh5vxk.png NVM, it was because of the space characters; I had to enclose the directory in quotation marks. Keep in mind MS Word uses 'smart quotes' instead of 'straight quotes'; “ vs "...

Thanks for the info. The one I got said it can't work on Sprint or Verizon networks, and is missing the serial #, as you said.

It seems the 'prog_ufs_firehose_Sdm845_lge.elf' is compatible for LG devices whose CPU is Snapdragon (SDM) 845? And thus the firehose file would be safe to use with 'LG G7'? Edit: It seems so, since I succeeded in extracting the partition files: abl_a (1 MB), boot_a & boot_b (64 MB each), and...

Is 'adb debugging in ULM11g', the same as 'USB debugging' under developer options? My phone currently has Oreo (8.1) installed and is model no. LMG710ULM Yeah, totally lost me at I guess we're supposed to have ADB cmd window open on the PC, similar to 3:30 of the following video...

I followed this instruction on the LG G7, a used model, and it got bricked. I.e. won't power on, even though battery was 100%. Edit: I got it to turn back on. I had to hold power + volume down button, then plug in the USB cable. I felt it wasn't totally bricked, since plugging in the USB cable...