stuck in bootloop and flash tool dont work solution

stuck in bootloop and flash tool dont work solution - G3 Q&A, Help & Troubleshooting

i really screwed up my d850 att g3. found this on a forum. and it fixed my bootloop. flash tool didnt work for me.
Found this on AndroidCentral: Saved my life – it got my phone back to original. Hope this helps others.
*****************************************************************************************************************
What worked for me was from the TWRP terminal command was to type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit enter
type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit enter and reboot.
it booted up to last rom i put on phone.

jaybird38 said:
i really screwed up my d850 att g3. found this on a forum. and it fixed my bootloop. flash tool didnt work for me.
Found this on AndroidCentral: Saved my life – it got my phone back to original. Hope this helps others.
*****************************************************************************************************************
What worked for me was from the TWRP terminal command was to type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit enter
type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit enter and reboot.
it booted up to last rom i put on phone.
Click to expand...
Click to collapse
I belive your commands are incomplete.
dd command basically copies something. "if" stands for input file. What you miss is "of" which stands for output file. Could you provide me with a link to your source thread?

i copied it exactly and my phone booted up right after reboot. i tried flash tool around 50 times on 2 computers and different cables and ports

http://lgg3root.com/lg-g3-root/how-to-unrootunbrick-lg-g3/
comment about half way down

If you say so... You could look up dd command or test it for yourself. What you or that guy copied is incomplete, idk how it worked.
Found that comment as well, he says he found it somewhere, no source thread there either.

it did work for me. thats all i can say. i don't know anything about command files.i was trying to get phone out of bootloop for 8 hours. seen this comment tried it and now my phone is working with my last rom i put on it which is cyanide.

found the original post.
http://forums.androidcentral.com/ge...ricked-lg-g2-stuck-twrp-no-download-mode.html
comment #5.

Related

[GUIDE] Backing up a phone with broken display

I have seen several of threads asking about how to recover data from a phone that has a broken display.
Backing up a phone with broken display
Prerequisites
Rooted phone with broken display/digitizer/etc. Display is nonfunctional for whatever reason.
ADB for your platform. Downloads for Windows, Mac, and Linux can be found at my dev-host.
Drivers installed (Windows), rules file set up (Linux + Mac). Drivers for windows can be found here. Rules file for Linux can be found here.
Recovery file attached to this post. (twrp.img)
External sdcard with at least 2 GB free space inserted in your broken phone.
openrecoveryscript.txt file attached to this post.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Backing up your broken device
Extract the ADB zip somewhere convenient.
Move the twrp.img recovery file into the ADB extracted directory.
Move the openrecoveryscript.txt file into the ADB directory.
Open a command prompt / terminal window in the ADB directory.
Windows: Windows Key + R => Type in "cmd" then click "RUN".
Linux: Open a terminal window by selecting it from your applications.
ALL:
Code:
cd /path/to/ADB/directory
Pull the battery from your phone, place it back in and boot into recovery (VolUp + Home + Power).
Connect your phone to your computer
Make sure that the following command returns "XXXXXX recovery" before proceeding to the next step.
Code:
./adb devices
Expected output:
Code:
List of devices attached
XXXXXXX recovery
Now to install TWRP recovery to your device. Type the following commands ( after each line). Linux users: Make sure you prepend each command with "./", as in "./adb ...". ALL Make sure you type the commands in CAREFULLY.
Code:
adb push twrp.img /tmp/twrp.img
adb shell dd if=/tmp/twrp.img of=/dev/block/mmcblk0p18
Wait until the last command above returns an output similar to below before proceeding to the next step:
Code:
12916+0 records in
12916+0 records out
6612992 bytes (6.3MB) copied, 1.094278 seconds, 5.8MB/s
Now pull your phones battery and reboot into recovery once again.
Run the following command to make sure your phone has booted into recovery completely.
Code:
adb devices
Expected output
Code:
List of devices attached
XXXXXXX recovery
Type the following to set up a script that will backup your phone to your external sdcard.
Code:
adb push openrecoveryscript.txt /cache/recovery/openrecoveryscript
Reboot your phone once more. This time, TWRP will begin backing up your ROM.
Wait for the backup to finish. You will know it is finished when you feel your phone reboot once more.
Optionally, you can check the state of your backup by running the following command and reading the last couple lines of it's output.
Code:
adb shell cat /tmp/recovery.log
Click to expand...
Click to collapse
Click to expand...
Click to collapse
That's it! Your entire system (/system, /data, /cache, and boot) will be backed up to your external sdcard. Just pop the sdcard in your replacement phone and you're good to go.
Enjoy and donate to the TWRP devs! This would not be possible if TWRP did not use the OpenRecoveryScript scripting engine!

Hellua nice guide :thumbup:
TEAM MiK
MikROMs Since 3/13/11

Man Cnexus! You are everywhere! Lol.
Nice guide. This will save lots of people :thumbup:
------------------------
Sprint Galaxy S3 "Supernexus" Thanks To Cyanogenmod
Whiplashh Rom
Look it up.

Is this method specific to the S3? I have an old S2 that I need to recover some photos from.

Hmm...boot your S2 into recovery, then connect it to your computer, run the following command and post the output for me.
Code:
adb shell ls

Hopefully I never need this guide but I think it should be a sticky. Good job!

This seems very helpful thank you.
This is a good option as well
https://code.google.com/p/androidscreencast/

CNexus said:
I have seen several of threads asking about how to recover data from a phone that has a broken display.
Backing up a phone with broken display
Click to expand...
Click to collapse
Thanks so much for the how-to.
I have a rooted Sprint Galaxy S3 with a broken display. I'm having a problem with getting it into recovery mode.
I believe when I hold down VolUp+Home+Power and reboot, it's loading a menu that's prompting me to select one of the boot options. It otherwise just sits there and never actually boots.
I've tried to use adb to boot it into recovery mode, but it also just sits there until I press the home key, at which point it just boots into normal mode.
Is there a way I can bypass any menus or does anyone with a working system know which option I should select at the menu?
Thanks,
Alex

Is your display broken? What does "adb devices" show when you're in that mode?

SM-T320 Hard Brick Recovery

Could someone run
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/unbrick.img bs=512 count=524288
and upload it? Flashing unbrick in a 'raw' fashion will allow you to hard brick most Qualcomm devices. Unfortunately I lost my backup and I can't boot my device. This file will allow me to recover. Thanks!

I can
Will it safe to run and guide me how to run it ??? Dont know where it goes............ I also have my stock recovery file saved by flashify https://drive.google.com/file/d/0B3i0YJU831QXTHctYWphX2Y0aE0/view?usp=sharing

vincowoo said:
Will it safe to run and guide me how to run it ??? Dont know where it goes............ I also have my stock recovery file saved by flashify https://drive.google.com/file/d/0B3i0YJU831QXTHctYWphX2Y0aE0/view?usp=sharing
Click to expand...
Click to collapse
I messed up, here's the correct command
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/unbrick.img bs=512 count=524288
Thank you very much!

Still not found .... run the command without error ... dont know where required file goes ... checked the root of both external and internal sd...

vincowoo said:
Still not found .... run the command without error ... dont know where required file goes ... checked the root of both external and internal sd...
Click to expand...
Click to collapse
Make sure you're running as root, from adb shell or terminal emulator. Try this one instead
Code:
dd if=/dev/block/mmcblk0 of=/storage/extSdCard/unbrick.img bs=512 count=31250
That command should have created 'unbrick.img' on your external SD card. I am extremely thankful for you doing this. My device is bricked and sitting in QHSUSB_BULK mode. You may want to save this file in case you ever need it! Thanks again, it is very much appreciated!

It is my pleasure. this forum helped me many times m trying to return something.That command completed successfully i am uploading it ?
https://docs.google.com/file/d/0B3i0YJU831QXUmViWGMyMGE1eHM/edit?usp=docslist_api

Need help, Note 4 SM-N910A

ok here we go, i have a Note 4 sm-n910a and i update to 5.1.1 but when its finish send me a message: "Android is starting... optimizing app 1 of 23" and on 12 of 23 boop, and restart again and again. I try put AP file in ap slot, BL on BL slot, cp on cp and CSC on csc, and finish ok, but when restart do that again and again, even i try puting the pit file but the same, i don´t no what happen (i can´t do downgrade)
There is a solution , or blockage stayed forever? :crying:

One time when I was messing with a hidden menu this happened to me. Phone would only boot loop to the exact spot you're saying. I replied to you in the other thread. If what I said doesn't work you will have to take it in for warranty. I had to take mine in for warranty because of messing with the wrong options in the hidden menu. ATT tried everything including reflashing with their utility and it couldn't fix the issue. So, they gave me a new phone right there. I don't know where you are but if you go to the nearest ATT store they should give the steps on how to get it replaced. Hopefully you have a ATT service center near you so you can just get it replace then and there. Btw, don't mention anything about flashing with Odin. I don't think it violates the warranty since you didn't use custom firmware you just used the official firmware and used Odin which is Samsung software. However don't mention ever using Odin, just say that you had tried upgrading your phone and after the upgrade this happened.

tonys.94 said:
One time when I was messing with a hidden menu this happened to me. Phone would only boot loop to the exact spot you're saying. I replied to you in the other thread. If what I said doesn't work you will have to take it in for warranty. I had to take mine in for warranty because of messing with the wrong options in the hidden menu. ATT tried everything including reflashing with their utility and it couldn't fix the issue. So, they gave me a new phone right there. I don't know where you are but if you go to the nearest ATT store they should give the steps on how to get it replaced. Hopefully you have a ATT service center near you so you can just get it replace then and there. Btw, don't mention anything about flashing with Odin. I don't think it violates the warranty since you didn't use custom firmware you just used the official firmware and used Odin which is Samsung software. However don't mention ever using Odin, just say that you had tried upgrading your phone and after the upgrade this happened.
Click to expand...
Click to collapse
but if I buy used for ebay, i don have a contract with att, can i change the phone?, its never fixed and on knox 0x0

Sent from my SAMSUNG-SM-N915A using XDA Free mobile app
Talking [GUIDE] Fix N910A Boot Loop - Unknown Baseband (step by step)
Hello friends
I have a few people asking questions on solution for N910 boot-loop, I want to make step-by-step guide to answer all questions.
Problem caused by changing *#9090# and possibly downgrade as well.
Takes time, several tries, don't worry.
I had the same problems and this method solved it.
1. Downgrade to 4.4.4 via Odin. Extract OC4, extract Odin, open Odin, select four files into correct position (BL, AP, CP, CSC) 4.4.4 OC4 Odin 3.09 (Samsung Mobile drivers required)
2. Once on 4.4.4 or below, enable developer options by tapping "build version" several times, enable USB debugging & mock location, and install KingRoot 4.0.0.233 to phone. Caution, newer versions did not work for me.
3. Open "Command Prompt" and type "adb version" should reply with "Android Debug Bridge version x.x.x", if does not, change to the correct directory where adb is installed via "cd" command. Need ADB? Here
4. These next two steps can be a little tricky as the phone often reboots before completed, must work quickly, I suggest copying the long command, then paste when ready.
5. Connect to working WiFi. Turn off your phone, reboot, or wait for it to reboot itself. Soon as phone turns on, open KingRoot, soon as WiFi connected notification appears, touch button in center of KingRoot app, soon as KingRoot reaches 30%, began adb commands.
6. ADB commands: first command "adb shell", second command "su", third command "dd if=/dev/zero of=/dev/block/mmcblk0p10 | dd if=/dev/zero of=/dev/block/mmcblk0p13 | dd if=/dev/zero of=/dev/block/mmcblk0p14 | dd if=/dev/zero of=/dev/block/mmcblk0p15 | dd if=/dev/zero of=/dev/block/mmcblk0p16" phone will reboot or you can reboot and after reboot boot-loop and unknown baseband will be fixed! Can now write new IMEI via "Write Cert" and possibly "Write QCN" if any network troubles, then all good to go!
7. Any questions feel free to contact me on skype: brandon.sisco or phone: 949.482.7058 I'm happy to walk you through any steps.
Once you see results, I have worked hard on this complete solution for many weeks, I would appreciate any donation. Secure paypal donate here
Thank you ecs87 for the help with adb wipe efs commands
---------- Post added at 08:28 AM ---------- Previous post was at 08:26 AM ----------
Sent from my SAMSUNG-SM-N915A using XDA Free mobile app
This is the Web address I used
http://forum.gsmhosting.com/vbb/f684/guide-fix-n910a-boot-loop-unknown-baseband-step-step-1961415/

lamarwallace said:
Sent from my SAMSUNG-SM-N915A using XDA Free mobile app
Talking [GUIDE] Fix N910A Boot Loop - Unknown Baseband (step by step)
Hello friends
I have a few people asking questions on solution for N910 boot-loop, I want to make step-by-step guide to answer all questions.
Problem caused by changing *#9090# and possibly downgrade as well.
Takes time, several tries, don't worry.
I had the same problems and this method solved it.
1. Downgrade to 4.4.4 via Odin. Extract OC4, extract Odin, open Odin, select four files into correct position (BL, AP, CP, CSC) 4.4.4 OC4 Odin 3.09 (Samsung Mobile drivers required)
2. Once on 4.4.4 or below, enable developer options by tapping "build version" several times, enable USB debugging & mock location, and install KingRoot 4.0.0.233 to phone. Caution, newer versions did not work for me.
3. Open "Command Prompt" and type "adb version" should reply with "Android Debug Bridge version x.x.x", if does not, change to the correct directory where adb is installed via "cd" command. Need ADB? Here
4. These next two steps can be a little tricky as the phone often reboots before completed, must work quickly, I suggest copying the long command, then paste when ready.
5. Connect to working WiFi. Turn off your phone, reboot, or wait for it to reboot itself. Soon as phone turns on, open KingRoot, soon as WiFi connected notification appears, touch button in center of KingRoot app, soon as KingRoot reaches 30%, began adb commands.
6. ADB commands: first command "adb shell", second command "su", third command "dd if=/dev/zero of=/dev/block/mmcblk0p10 | dd if=/dev/zero of=/dev/block/mmcblk0p13 | dd if=/dev/zero of=/dev/block/mmcblk0p14 | dd if=/dev/zero of=/dev/block/mmcblk0p15 | dd if=/dev/zero of=/dev/block/mmcblk0p16" phone will reboot or you can reboot and after reboot boot-loop and unknown baseband will be fixed! Can now write new IMEI via "Write Cert" and possibly "Write QCN" if any network troubles, then all good to go!
7. Any questions feel free to contact me on skype: brandon.sisco or phone: 949.482.7058 I'm happy to walk you through any steps.
Once you see results, I have worked hard on this complete solution for many weeks, I would appreciate any donation. Secure paypal donate here
Thank you ecs87 for the help with adb wipe efs commands
---------- Post added at 08:28 AM ---------- Previous post was at 08:26 AM ----------
Sent from my SAMSUNG-SM-N915A using XDA Free mobile app
This is the Web address I used
http://forum.gsmhosting.com/vbb/f684/guide-fix-n910a-boot-loop-unknown-baseband-step-step-1961415/
Click to expand...
Click to collapse
Thank´s man, but when you are on 5.1.1, can´t do a downgrade, i have my phone brick, i´m fu.... :crying:

How to flash a backup radio.img?

hi everyone i was trying to test a radio and i installed one radio that didnt work i already make a backup of my radio using this:
adb shell
su
dd if=/dev/block/mmcblk0p20 of=/sdcard/radio.img
exit
Click to expand...
Click to collapse
and got the radio.img
now when im trying to flash the backup i made using this...
adb shell
su
dd if=/storage/sdcard0/radio.img of=/dev/block/mmcblk0p20
exit
Click to expand...
Click to collapse
i got this... (dd: /storage/sdcard0/radio.img: No such file or directory)
how can i flash my radio.img... HELP

Put the image in your adb fastboot on your computer where you have adb set up. Connect phone to computer. Open command window and type: adb reboot bootloader / fastboot flash radio Name_Of_File_.img then reboot phone.

For the love of god, stop making new threads.
I already told you to stop doing this. You already have 3 (now 4) threads all related to the same original issue. Should have all been discussed in one thread.
I was already helping you in another thread(s). I suggested running Asia or Euro RUUs. You never responded if that worked or not.
You should not be messing with the radio using adb commands (as its clear form past communications that you don't have the proper knowledge to do so). This is really dangerous, and can easily damage the phone permanently. Depending on what radio you flashed (that "didn't work) you may already have.
I've already advised the safest way to change the radio.

Trouble Restoring Backed Up Stock ROM & WiFi Won't connect using LOS 15.1

Most of my the question/topic was explained here.
@steadfasterX
Re the WiFi pls share also the boot logs (see LOS faq).
Click to expand...
Click to collapse
I couldn't pull a boot log from TWRP, I'd get "Sbin/sh: adb: not found". That output seems to be haunting a lot of my adb attempts, it appears when I try "adb sync" as well.
Ok the choose "format" data in twrp and try to boot first without your userdata backup into stock. Lemme know if that works.
Click to expand...
Click to collapse
I tried, I unfortunately get a solid wall of bootloop. I still have everything from my SALT backup in case anything may or may not be needed. I just had a though, could the problem be that this backup was from before I USUed my phone (I can't remember if I said that in the first place)?

emperordogma said:
Most of my the question/topic was explained here.
@steadfasterX
I couldn't pull a boot log from TWRP, I'd get "Sbin/sh: adb: not found". That output seems to be haunting a lot of my adb attempts, it appears when I try "adb sync" as well.
I tried, I unfortunately get a solid wall of bootloop. I still have everything from my SALT backup in case anything may or may not be needed. I just had a though, could the problem be that this backup was from before I USUed my phone (I can't remember if I said that in the first place)?
Click to expand...
Click to collapse
The confusing part is we talk about 2 different things here:
1) WiFi. This is related to LOS and so when asking for logs l always assume you're on LOS. TWRP must match the LOS version.
2) booting stock. To make TWRP work it must be the matching TWRP installed of your stock release. Is that the case? If not do that first.
So re stock. Its strange that it does not boot with formatted data. Could you also flash magisk here and then try to boot?

steadfasterX said:
The confusing part is we talk about 2 different things here:
1) WiFi. This is related to LOS and so when asking for logs l always assume you're on LOS. TWRP must match the LOS version.
2) booting stock. To make TWRP work it must be the matching TWRP installed of your stock release. Is that the case? If not do that first.
So re stock. Its strange that it does not boot with formatted data. Could you also flash magisk here and then try to boot?
Click to expand...
Click to collapse
1) I'll worry about the WiFi if/when I can get stock up and running. But I was/am using LOS 15.1 (here's the version "lineage-15.1-20210608-UNOFFICIAL-h812_usu"), and my TWRP was "twrp-3.4.0-PREVIEW-230_g4_O".
2) I downgraded my TWRP to "twrp-3.3.1-PREVIEW-196_g4_MM", and same result, I get to the LG screen and the notification light stays on, then nothing. When inputting these dd commands:
Code:
adb shell
dd if=/external_sd/boot.img of=/dev/block/bootdevice/by-name/boot bs=512
dd if=/external_sd/system.img of=/dev/block/bootdevice/by-name/system bs=4096
dd if=/external_sd/userdata.img of=/dev/block/bootdevice/by-name/userdata bs=4096
adb shell sync
When I put "adb shell sync" in I get "/sbin/sh: adb: not found"
I tried clearing the cache after I put it in, then tried formatting, as well as tried installing Magisk. And when mounting the data partition, everything seem to be there (hard to tell exactly since it's not the way I'm used to seeing it).
Edit: I just tried getting a boot log using:
Code:
adb pull /cache/debug/boot_lc_crash.txt
adb pull /cache/debug/boot_lc_full.txt
adb pull /cache/debug/boot_lc_kernel.txt
And the first one comes back with /sbin/sh: adb: not found

emperordogma said:
1) I'll worry about the WiFi if/when I can get stock up and running. But I was/am using LOS 15.1 (here's the version "lineage-15.1-20210608-UNOFFICIAL-h812_usu"), and my TWRP was "twrp-3.4.0-PREVIEW-230_g4_O".
2) I downgraded my TWRP to "twrp-3.3.1-PREVIEW-196_g4_MM", and same result, I get to the LG screen and the notification light stays on, then nothing. When inputting these dd commands:
Code:
adb shell
dd if=/external_sd/boot.img of=/dev/block/bootdevice/by-name/boot bs=512
dd if=/external_sd/system.img of=/dev/block/bootdevice/by-name/system bs=4096
dd if=/external_sd/userdata.img of=/dev/block/bootdevice/by-name/userdata bs=4096
adb shell sync
When I put "adb shell sync" in I get "/sbin/sh: adb: not found"
I tried clearing the cache after I put it in, then tried formatting, as well as tried installing Magisk. And when mounting the data partition, everything seem to be there (hard to tell exactly since it's not the way I'm used to seeing it).
Edit: I just tried getting a boot log using:
Code:
adb pull /cache/debug/boot_lc_crash.txt
adb pull /cache/debug/boot_lc_full.txt
adb pull /cache/debug/boot_lc_kernel.txt
And the first one comes back with /sbin/sh: adb: not found
Click to expand...
Click to collapse
Ok so first of all: adb shell sync must be executed from without the shell you're in. That wasn clear described. So in other words after the dd command you just need to write "sync". That's it. It will not give any output when finished.
So here the next steps:
Try to mount system in TWRP and browse with the file manager if there are any files in /system/apps .
Use bs=512 for all dd commands.
Share your stock boot img here.
What data do you need exactly btw? App data like settings etc? Or just specific files?

steadfasterX said:
Ok so first of all: adb shell sync must be executed from without the shell you're in. That wasn clear described. So in other words after the dd command you just need to write "sync". That's it. It will not give any output when finished.
So here the next steps:
Try to mount system in TWRP and browse with the file manager if there are any files in /system/apps .
Use bs=512 for all dd commands.
Share your stock boot img here.
What data do you need exactly btw? App data like settings etc? Or just specific files?
Click to expand...
Click to collapse
Ahhhh, I assumed everything I saw was in a "copy/paste" format so, I didn't think to even try to exclude the adb from it.
I was able to mount system, and browse apps, there was stuff in there.
I used the "bs=512" method, and it gave the same result. I'm starting to think I'm just boned honestly. I'll upload my boot.img here in a few (in case you see this before I do).
I was hoping I could back up my texts/call logs (I was able to salvage a few, but I'm missing about a months worth), properly backup WhatsApp, get my Nova settings, and make sure I'm not missing anything else (I had a list, but can't think of it now). And I was hoping by doing it, it would fix the annoying Wifi bug.
Edit 1: I don't think it's "bootlooping", because I read that you could boot into TWRP while it's doing it (if your timing is good), I tried and couldn't get into TWRP at all, it's "stone walling" at the LG screen.
Edit 2: My stock Boot.img

ok so .. the boot image you send is not from the STOCK ROM. That is from LOS it seems. Pls upload the stock one which you are trying to flash with dd

steadfasterX said:
ok so .. the boot image you send is not from the STOCK ROM. That is from LOS it seems. Pls upload the stock one which you are trying to flash with dd
Click to expand...
Click to collapse
Huh, I am not sure how that happened. I'm starting to wonder if after the first try with adb push if I was even using my Stock Boot.img, magisk must've messed with me (they said the recommend way to to patch a boot.img) and I got them mixed up? Or at least that's the only thing I can think of.
Anyways, this should be the right one. Boot.img

@steadfasterX
I was able to boot back to Stock using the correct boot.img, unfortunately I lost some very important WhatsApp texts because it had to "re-verify", but other than that, everything seems to be in order. My apologies for confusing us both with the wrong boot.img. When I was messing around with Magisk, I must've gotten the two confused. I won't know if the wifi is fixed in LOS until later (I have to wait a while before I can use WhatsApp again).

emperordogma said:
@steadfasterX
I was able to boot back to Stock using the correct boot.img, unfortunately I lost some very important WhatsApp texts because it had to "re-verify", but other than that, everything seems to be in order. My apologies for confusing us both with the wrong boot.img. When I was messing around with Magisk, I must've gotten the two confused. I won't know if the wifi is fixed in LOS until later (I have to wait a while before I can use WhatsApp again).
Click to expand...
Click to collapse
yea that was my assumption after seeing that wrong boot.img.. all users were able to boot STOCK this way so it was either a mistake or bad flash. glad you figured it out.
when your WiFi does not come back on LOS later attach the boot logs then.
cheers

steadfasterX said:
yea that was my assumption after seeing that wrong boot.img.. all users were able to boot STOCK this way so it was either a mistake or bad flash. glad you figured it out.
when your WiFi does not come back on LOS later attach the boot logs then.
cheers
Click to expand...
Click to collapse
Everything appears to be working fine now, including the WiFi (you were right about fixing it by going back to stock), which appears to be better than it was before! I decided to upgrade to Lineage 16, because you had just updated it recently so, best to stay where the active development is (or at least last update), in case anything goes wrong. Thank you so much for your assistance, sorry about mixing up the boot.imgs. And thank you continuing support for the G4 (in some capacity).
I also just found out my phone had "OEM Unlock" in the developer settings, so I don't think I needed to use USU (if I read about that tight), pretty annoyed with myself for not paying attention properly.

emperordogma said:
Everything appears to be working fine now, including the WiFi (you were right about fixing it by going back to stock), which appears to be better than it was before! I decided to upgrade to Lineage 16, because you had just updated it recently so, best to stay where the active development is (or at least last update), in case anything goes wrong. Thank you so much for your assistance, sorry about mixing up the boot.imgs. And thank you continuing support for the G4 (in some capacity).
I also just found out my phone had "OEM Unlock" in the developer settings, so I don't think I needed to use USU (if I read about that tight), pretty annoyed with myself for not paying attention properly.
Click to expand...
Click to collapse
If your device is not a h811 or h815 international(!) then this option in dev settings will just do.....nothing. If it would be THAT easy there were never the need for UsU so you did it all right

steadfasterX said:
If your device is not a h811 or h815 international(!) then this option in dev settings will just do.....nothing. If it would be THAT easy there were never the need for UsU so you did it all right
Click to expand...
Click to collapse
Then what the heck is the point of that button/switch??? I figured because mine was a frankenstien device that maybe almost all of them had it, or I just got "lucky".

emperordogma said:
Then what the heck is the point of that button/switch??? I figured because mine was a frankenstien device that maybe almost all of them had it, or I just got "lucky".
Click to expand...
Click to collapse
Its just there by mistake. Not by LG but the OEMs. The OEMs like verizon, etc are not doing a good job but that's not new..

Develop Bugs

welcome