Related
Hi...
i want to know if is possible unbrick this phone. I've already tried:
- KDZ Flash (LG Flash Tool 2014), can't downlaod the lastest KDZ firmware for it because the page doesn't exist anymore, so i just dowloaded a previous version. Then when it start the upgrade procedure an error ocurred: "Upgrade stop due to an error"
- With the LG original mobile tool.
P.S. My phone was rooted before the brick.
Thanks!
undon3 said:
Hi...
i want to know if is possible unbrick this phone. I've already tried:
- KDZ Flash (LG Flash Tool 2014), can't downlaod the lastest KDZ firmware for it because the page doesn't exist anymore, so i just dowloaded a previous version. Then when it start the upgrade procedure an error ocurred: "Upgrade stop due to an error"
- With the LG original mobile tool.
P.S. My phone was rooted before the brick.
Thanks!
Click to expand...
Click to collapse
Have you downloaded the lg mobile united drivers, because without it the flash tool will not flash the firmware You can download the drivers from the following url
http://www.mediafire.com/download/g31hbcdmh14io89/LGUnitedMobileDriver_S50MAN311AP22_ML_WHQL_Ver_3.11.3.exe
And if you have missed some step you can see from the following url
http://forum.xda-developers.com/optimus-l3-l5-l7-l9-ii/general/method-unbricking-lg-l5ii-t3056008
I had some trouble to root the Elephone S7 7.1.1 Stock Rom. Therefore here is the short HowTo...
*** Root and TWRP for Elephone S7 4GB 7.1.1 Stock Rom http://bbs.elephone.hk/thread-12886-1-1.html
* SP_Flash_Tool download latest version e.g.: SP_Flash_Tool_v5.1720_Win.zip from http://spflashtools.com/category/windows
* SuperSU download latest version e.g.: SuperSU-v2.82-201705271822.zip from http://www.supersu.com/download
* Stock Rom download latest version e.g.: s7_4g_20170517133805_v2.3.zip from https://mega.nz/#!Z4AmRRTK!XLyd4O8HaS4B_XVNMdSn5OPX76rXDkOYXVekvn-9lMM
* TWRP 3.0.3 by Jemmini download latest version e.g.: recovery.img from https://www.dropbox.com/s/b7u3k1mgpppxlyx/recovery.img?dl=0
* create two folders, one for Stock Rom and one for TWRP
* unpack Stock Rom and copy MT6797_Android_scatter.txt into TWRP directory
optional:
* OpenGAps arm64 / 7.1 / stock download latest version e.g.: open_gapps-arm64-7.1-stock-20170629.zip http://opengapps.org/
* in OpenGAps zip delete from \GApps\ folder whatever you don't want
optional:
* AdAway v2.3 download latest apk from https://labs.xda-developers.com/store/app/org.adaway discussion https://forum.xda-developers.com/showthread.php?t=2190753
* AdAway systemless hosts download latest version e.g.: AdAway_systemless_hosts_v2.zip from https://www.androidfilehost.com/?fid=24438995911977059
optional:
* my_bootanimation.zip
* change your favorite boot animation in my_bootanimation.zip\system\media\
* add your own tweaks in my_bootanimation.zip\system\tweaks.prop
SP_Flash_Tool for Stock Rom:
* select Download-Agent: SP_Flash_Tool_v5.1720_Win\MTK_AllInOne_DA.bin
* select Scatter-Loading-File: Stock Rom\MT6797_Android_scatter.txt
* Firmware Upgrade
* switch phone off
* click Download and press "Power" to connect the phone
* after "Download OK" unplug USB and press "Power" to start phone
SP_Flash_Tool for TWRP:
* select Download-Agent: SP_Flash_Tool_v5.1720_Win\MTK_AllInOne_DA.bin
* select Scatter-Loading-File: TWRP\MT6797_Android_scatter.txt
* Download Only
* switch phone off
* click Download and press "Power" to connect the phone
* !!! after "Download OK" unplug USB and press "Home + Power" (about 10 seconds) until enter recovery !!!
* on phone select "recovery" with "Home" and "Vol -" for OK
* in TWRP select and install
SuperSu
optional Open Gaps
optional AdAway systemless hosts
optional my_bootanimation.zip
* reboot (may loop some times)
tip:
* "adb reboot recovery" doesn't work
* therefore switch phone off and press "Home + Power" (about 10 seconds) until enter recovery
* select "recovery" with "Home" and "Vol -" for OK to enter TWRP
*** restore wrong IMEI's after update to 7.1.1 Stock Rom http://bbs.elephone.hk/thread-13641-1-1.html
* Maui META download latest version e.g.: MauiMETA_exe_v9.1724.0.rar from https://www.needrom.com/download/maui-meta-3g-ver-7-1444-0-0/
* IMEI's from phone box
Maui META:
* switch phone off and unplug USB
* press and hold the "Vol- + Power" Button and connect USB, release the "Vol- + Power" Button and click "Reconnect" (wait until the ball turns yellow)
* !!! retry if it not works !!!
* in the selection box scroll to the IMEI download option and select (it will open a new window)
* copy !!! only the first 14 digits !!! of the 1st IMEI and paste in the IMEI field
* click the "Download To Flash" button and wait until message "Download IMEI to flash successfully"
* repeat this two steps for SIM_2
* close the window, click "Disconnect", unplug USB and restart phone
* check IMEI's in Settings > About Phone > Status
*** restore rotating MAC after update to 7.1.1 Stock Rom https://androidrookies.com/how-to-change-wlan-mac-address-on-mtk/
* in Playstore install "Root Explorer"
* HxD Hex Editor for Windows download latest version https://mh-nexus.de/downloads/HxDSetup.zip
* in Root Explorer copy \nvdata\APCFG\APRDEB\WIFI to \sdcard
* now copy WIFI file to Windows and edit with HxD Hex Editor
* for Your last MAC e.g.: 00:08:22:a8:e3:fb write it in Offset (h) 04 to 09
00 01 02 03 04 05 06 07 08 09
06 01 00 00 00 08 22 A8 E3 FB
* copy WIFI back to \sdcard
* in Root Explorer copy \sdcard\WIFI to \nvdata\APCFG\APRDEB\ and set permission to 660 (rw-rw—)
Have Fun
Thanks
I have problems, this is what I do, for twrp:
- Connect USB to phone
- Start Smart phone flash
- Select scatter file
- Click on download
- Press power in the phone
There, it doesnt download anything. The phone just boots up normally. It could be a driver problem since when it boots it says that the device couldnt not be recognized but where I can find the drivers?
Edit: finally i got it to work but not in a nice way. I tried to turn driver signature off, installing new VCOM drivers for S7 but nothing. So I just went to my other computer with Windows 7 64 bit and it worked all fine the first time. In this computer I have Windows 10 64 bit and always have problems with these things related to phones and flashing.
Thanks for the instructions.
Some comments:
You never mention that you should create a TWRP folder, so that confused me for a while.
You explicitly refer to Windows versions of files in your instructions, even though it's unnecessary. I did the process on Linux and it worked perfectly fine.
The recovery is not fixed for OTA updates. The first OTA update I got bricked my system and I had to reinstall everything. Is there a fixed version of the TWRP available for this phone? I know there's a fixed version for the Elephone P7000 here: bbs.elephone.hk/thread-5332-1-30.html
OpenGApps gave me many issues with crashing services and apps not starting. I decided to leave it out entirely, since the necessary apps are available in the Stock ROM. (I tried all GApps variants from pico to stock)
Even with a rooted system, I could not remove some OEM apps (such as the OTA app that will break the system). Is there a way to remove those anyway?
Hi. TWRP installed on my s7 (X25 - 4/64 G} but can't reboot (hanging logo). Pls. help me to fix it. Thanks
d1237 said:
Hi. TWRP installed on my s7 (X25 - 4/64 G} but can't reboot (hanging logo). Pls. help me to fix it. Thanks
Click to expand...
Click to collapse
Please try to install original Stock Rom with SP_Flash_Tool. And then retry to install TWRP.
Ghostbird said:
Thanks for the instructions.
Some comments:
You never mention that you should create a TWRP folder, so that confused me for a while.
You explicitly refer to Windows versions of files in your instructions, even though it's unnecessary. I did the process on Linux and it worked perfectly fine.
The recovery is not fixed for OTA updates. The first OTA update I got bricked my system and I had to reinstall everything. Is there a fixed version of the TWRP available for this phone? I know there's a fixed version for the Elephone P7000 here: bbs.elephone.hk/thread-5332-1-30.html
OpenGApps gave me many issues with crashing services and apps not starting. I decided to leave it out entirely, since the necessary apps are available in the Stock ROM. (I tried all GApps variants from pico to stock)
Even with a rooted system, I could not remove some OEM apps (such as the OTA app that will break the system). Is there a way to remove those anyway?
Click to expand...
Click to collapse
Hi Ghostbird, thank You for Your support!
* I have added the TWRP folder in the HowTo.
* Do You have tested the HypoTurtle TWRP? Works OTA update now?
* OpenGApps working without any problems, but i never tried to remove OEM apps.
* I have installed Stock Rom, updated OTA and then installed TWRP. No problems since then.
below You find my GApps folder:
batteryusage-all.tar.lz
calculatorgoogle-all.tar.lz
calendargoogle-all.tar.lz
calsync-all.tar.lz
cameragoogle-arm64.tar.lz
cameragoogle-common.tar.lz
cameragooglelegacy-arm.tar.lz
cameragooglelegacy-common.tar.lz
chrome-arm64.tar.lz
clockgoogle-all.tar.lz
contactsgoogle-all.tar.lz
dialerframework-common.tar.lz
dialergoogle-all.tar.lz
exchangegoogle-all.tar.lz
gmail-all.tar.lz
hangouts-arm64.tar.lz
keyboardgoogle-arm64.tar.lz
messenger-arm64.tar.lz
newsstand-all.tar.lz
newswidget-all.tar.lz
pixelicons-all.tar.lz
pixellauncher-all.tar.lz
storagemanagergoogle-all.tar.lz
taggoogle-all.tar.lz
Hi everyone
Link for twrp is down
Someone can post in attachement please ?
Regard
Bradco said:
Hi everyone
Link for twrp is down
Someone can post in attachement please ?
Regard
Click to expand...
Click to collapse
This should work for you. Used on my S7.
bluiis48 said:
This should work for you. Used on my S7.
Click to expand...
Click to collapse
thank you very much for the file, it does not work for me. it starts well on the recovery but can not start the system, still block on the logo.
I'm on s7_4g_20170814163417_v2.4.
Ah, I am still on the July release, have been holding off on the August ROM waiting to see if anything showed up for September but it looks like that might be game over for updates. Thanks for letting me know, saves me some time. I find the July one not too bad. Roll back for root ?
bluiis48 said:
Ah, I am still on the July release, have been holding off on the August ROM waiting to see if anything showed up for September but it looks like that might be game over for updates. Thanks for letting me know, saves me some time. I find the July one not too bad. Roll back for root ?
Click to expand...
Click to collapse
you're welcome , for root it's all good with magisk.
you install the latest version of magisk manager, you get the file boot.img from your rom, you patch this file via magisk manager and you just flash the new boot.img via flashtool. After root is functional.
Y'll try this : https://forum.xda-developers.com/android/software/twrp-porter-maker-mediatek-mt67xx-32-t3681861
Thanks, I will give that a try when I finally decide to load the 0814 update (or newer if one becomes available). Can I ask why you were needing TWRP ? Also did you notice any improvement with the 0814 update? I have an S8 in transit and will be passing this S7 on to my wife but the S8 could be a while yet when Canada Post gets it. Magisk may work on that also, same X25 and ram.
bluiis48 said:
Thanks, I will give that a try when I finally decide to load the 0814 update (or newer if one becomes available). Can I ask why you were needing TWRP ? Also did you notice any improvement with the 0814 update? I have an S8 in transit and will be passing this S7 on to my wife but the S8 could be a while yet when Canada Post gets it. Magisk may work on that also, same X25 and ram.
Click to expand...
Click to collapse
of course a custom recovery is always useful, nandroid backup and flash some .zip.
for it is the first version of android 7 that I test and I find it very stable without problems.
Ha yes I wonder the purchase of a s8 tell me if it great
Yes I will give you my opinion but it will be a while because our customs and mail is very slow. As I remember I had a hard time with TWRP when I loaded the 20170517 stock rom. I finally did a full format with SPflashtool and when it seemed stuck at the boot animation I left it alone for maybe half an hour and it finally came to life so that version of TWRP does work for 7.1.1 for me.
bluiis48 said:
Yes I will give you my opinion but it will be a while because our customs and mail is very slow. As I remember I had a hard time with TWRP when I loaded the 20170517 stock rom. I finally did a full format with SPflashtool and when it seemed stuck at the boot animation I left it alone for maybe half an hour and it finally came to life so that version of TWRP does work for 7.1.1 for me.
Click to expand...
Click to collapse
ok I understand, little question about SP flash tool to make a full format you used which option DOWNLOAD ONLY / FIRMWARE UPGRADE or the other so I no longer remember the name ?
Bradco said:
ok I understand, little question about SP flash tool to make a full format you used which option DOWNLOAD ONLY / FIRMWARE UPGRADE or the other so I no longer remember the name ?
Click to expand...
Click to collapse
The other is format all + download and that may work for you. It was a while ago, when I went from Android 6 to 7 and I do not want to steer you in the wrong direction. From what I remember I used the format tab on SP Flashtool and pretty much formatted everything. Yesterday I tried for the 0814 OTA by using the clean option in Super SU (which basically uninstalls it ) and flashing the stock recovery for the existing ROM version using SP Flashtool. The OTA would not complete because of a sector mismatch so I flashed TWRP recovery again, which actually rebooted pretty fast then reinstalled the Super SU zip using TWRP. If you want TWRP recovery maybe try it again without formatting anything and give the boot more time. I am not going to bother flashing the complete 0814 ROM until I pass on the phone to my wife because I don't want to go through the app and user credential reloads and fixing the IMEI's and WIFI mac. The Google backup to Drive feature is not available in settings - same for many who are on 7.1.1 even the "name brand" phones.
bluiis48 said:
The other is format all + download and that may work for you. It was a while ago, when I went from Android 6 to 7 and I do not want to steer you in the wrong direction. From what I remember I used the format tab on SP Flashtool and pretty much formatted everything. Yesterday I tried for the 0814 OTA by using the clean option in Super SU (which basically uninstalls it ) and flashing the stock recovery for the existing ROM version using SP Flashtool. The OTA would not complete because of a sector mismatch so I flashed TWRP recovery again, which actually rebooted pretty fast then reinstalled the Super SU zip using TWRP. If you want TWRP recovery maybe try it again without formatting anything and give the boot more time. I am not going to bother flashing the complete 0814 ROM until I pass on the phone to my wife because I don't want to go through the app and user credential reloads and fixing the IMEI's and WIFI mac. The Google backup to Drive feature is not available in settings - same for many who are on 7.1.1 even the "name brand" phones.
Click to expand...
Click to collapse
With each new installation of rom, I start all (long but more stable).
For the problem of wifi and IMEI for having 5 elephone I have never encountered this problem even with version 0814. For the recovery custom it is weird that the start of the phone is long. this afternoon I tried to make a port of TWRP with base on TWRP 3.1 (compatible android 7 for p9000) with stock recovery, but I'm not sure it is functional. i'm not understand everything .
I just saw that the thread be updated, even tuto with the rom s7_4g_20170517133805_v2.3.zip I'm not sure that it works.
I followed the tutorial on first page and it works for me but I am using the 0517 stock rom. I don't think you need to Port TWRP because it does work with the one I posted. If you have time try starting with the 0517 and follow steps on page one. If that works you can try the same with 0814.
IMPORTANT THOUGHT do you have OEM unlocking (allow the bootloader to be unlocked) enabled in developer options ? This is the first phone where I found that to be necessary.
bluiis48 said:
I followed the tutorial on first page and it works for me but I am using the 0517 stock rom. I don't think you need to Port TWRP because it does work with the one I posted. If you have time try starting with the 0517 and follow steps on page one. If that works you can try the same with 0814.
IMPORTANT THOUGHT do you have OEM unlocking (allow the bootloader to be unlocked) enabled in developer options ? This is the first phone where I found that to be necessary.
Click to expand...
Click to collapse
I just look into the options for developers and OEM unlocking is turned off. do you think I'll have to activate it ?
Ps : I never needed it
EDIT 1 :
at this stage :
SP_Flash_Tool for Stock Rom:
* select Download Agent: SP_Flash_Tool_v5.1720_Win \ MTK_AllInOne_DA.bin
* select Scatter-Loading-File: Stock Rom \ MT6797_Android_scatter.txt
* Firmware Upgrade
Before doing firmaware upgrade in what version of rom do I have to?
So today i decided to update magisk to its latest versio, it all whet well,i did within android. later on in the day i decided to reboot myphone, and to my surprise it got stuck o thelgv30 thinq scree, after decide 10m was enough i rebooted and the it was stuck in bootloop, so i decided to restore my nanddroid , after it was done i hit reboot to system, and now it will only noot to fastootmode,, its as if there is nothing flashed to boot or system. any help will greatly appreciated.
EDIT: VERY OLD POST; WE CAN NOW USE NEWER MAGISK
____________
By "latest" you mean Magisk beta? You can only use stable 16.0 Magisk. Stated in the bootloader unlock/TWRP/root instructions that beta Magisk will mess up your phone.
Download Magisk or SuperSu. Magisk 16 (Use stable Magisk -- which right now is 16.0! Magisk "beta" will mess up your phone.)
Click to expand...
Click to collapse
You may need to Master Reset (wipe everything), reflash TWRP, etc. Good luck.
ChazzMatt said:
By "latest" you mean beta Magisk. You can only use stable 16.0 Magisk. Stated in the bootloader unlock instructions that beta Magisk will mess up your phone.
You may need to Master Reset (wipe everything), reflash TWRP, etc. Good luck.
Click to expand...
Click to collapse
yea that what i did fml. what do i do reflash the oreo kdz?
siulmagic said:
yea that what i did fml. what do i do reflash the oreo kdz?
Click to expand...
Click to collapse
Probably. First Master Reset to clear everything. SEE if that works. Post 101 of the Frankenstein thread.
If that doesn't work, then go into download mode manually, then open dev patched LGUP and reflash Oreo KDZ.
Then use ADB to reinstall TWRP, and go from there. Your bootloader will already be unlocked so you'll continue to get the "scary" bootloader unlock warning. But you'll otherwise be following the instruction of the bootloader unlock thread, except for the bootloader unlock part.
ChazzMatt said:
Probably. First Master Reset to clear everything. SEE if that works. Post 101 of the Frankenstein thread.
If that doesn't work, then go into download mode manually, then open dev patched LGUP and reflash Oreo KDZ.
Then use ADB to reinstall TWRP, and go from there. Your bootloader will already be unlocked so you'll continue to get the "scary" bootloader unlock warning. But you'll otherwise be following the instruction of the bootloader unlock thread, except for the bootloader unlock part.
Click to expand...
Click to collapse
Isint the master reset disabled with twrp? master reset only boots twrp, when you have twrp installed, i will try to wipe with lgup.
Thanks for the help man, phone is backup and running.
siulmagic said:
Thanks for the help man, phone is backup and running.
Click to expand...
Click to collapse
I've tried using LgUP to try and get me back onto an OS, but it will not boot into the OS, only into fastboot. Anything I can do?
If you were using Trebel TWRP you have to use normal TWRP and restore the backup GPT in order for a stock nandroid to work or a stock based clean flash...
jmej88 said:
I've tried using LgUP to try and get me back onto an OS, but it will not boot into the OS, only into fastboot. Anything I can do?
Click to expand...
Click to collapse
To fix stuck in fastboot or download mode
Connect phone in download mode
go in patched LGUP flash h93320f_00_open_ca_op_0612.kdz
With partition dl option
(not working go in device manager select modem
Then lge mobile usb modem right click disable driver try again)
help me:,(
ChazzMatt said:
Probably. First Master Reset to clear everything. SEE if that works. Post 101 of the Frankenstein thread.
If that doesn't work, then go into download mode manually, then open dev patched LGUP and reflash Oreo KDZ.
Then use ADB to reinstall TWRP, and go from there. Your bootloader will already be unlocked so you'll continue to get the "scary" bootloader unlock warning. But you'll otherwise be following the instruction of the bootloader unlock thread, except for the bootloader unlock part.
Click to expand...
Click to collapse
I had the same problem but I tried many different versions but it was still stuck in fastboot i'm so scared help me pls
Im stuck in fastboot mode too after chip reset. Tried kdz us998 10 with no luck.
Anybody have other suggestions?
....edit.
Fixed flashing Canadian kdz.
mines wont go into download mode just keeps going to fastbootloader
r3m3dy478 said:
mines wont go into download mode just keeps going to fastbootloader
Click to expand...
Click to collapse
Flash twrp and flash rom.
Sent from my VS996 using Tapatalk
r3m3dy478 said:
mines wont go into download mode just keeps going to fastbootloader
Click to expand...
Click to collapse
Download kdz flashable zip then extract it. Flash the system.img and boot.img file via fastboot
This just happened to me today. It was either from the newest Magisk (v22) or from the newest YouTube Vanced. Those were the only things that changed recently on my phone. Rebooted today and it will only go to Fastboot mode and that's it.
Master Reset will get me into TWRP, but I think my USB port on the phone is damaged, it will charge but neither my Windows nor Linux PCs will recognize that it's plugged in. So it's like only USB charging works but not USB data. So I think I'm screwed, idk if it's fixable. Sad day.
Am also stack here qhile trying to unlock my bootloader using @bilong9 thread on my v300l .please help
This also happened to me while trying to update to Magisk 22. First I had an error with Magisk in a restart cycle, then when I tried to update manually from the APK I got stuck in a fastboot loop with no ADB access. I was able to boot to TWRP from fastboot on my PC, then re-flash the Pie image. My settings were all lost, but I did get my phone back at least. BEWARE of Magisk 22, or at least until it's fixed for the V30!
edit: I found that I COULD install Magisk 22.0.zip while following these instructions for restoring my phone:
LG V30/V30+/V30S Bootloader Unlock & Root Method (With Clear Instructions)
(WTF...!) LG V30/V30+/V30S Bootloader Unlock & Root Method (With Clear Instructions) WTF...! LG V30,V30+,V30S (MOST VARIANTS) BOOTLOADER UNLOCK, TWRP, ROOT INSTRUCTIONS HERE >>>CLICK HERE TO POST #193
forum.xda-developers.com
after a few extra prompts from the Magisk app, v22 now works.
I've had no issues using Magisk v22 with an LOS 17.1 (Android 10) based ROM. It could just be that there's a problem with it on either LG stock or Pie ROMs.
UPDATE
* Variant: US998 US Cellular/Carrier Unlocked
* ROM: Rooted Stock Pie (US99830b)
* Magisk: v21.4
So it seems the issue is not that it "soft bricks", but something about the new installation process of Magisk v22 goes wrong with the /boot partition, causing the phone to only be able to boot into Fastboot mode.
After getting my phone fully recovered and restored from the last failed attempt (and making a new TWRP backup), I attempted the v22 update again. First Magisk attempted to download and install the new v22 app, and then a popup notification said "additional setup is required for your device, press OK to reboot". So I hit okay, and that's when once again I got stuck in Fastboot with no other options.
If you have a TWRP/nandroid backup, you can easily fix this by performing the Master Reset process in order to boot into TWRP, and then just Restoring the /boot partition from your TWRP backup. This will get you back to Magisk v21.4 where you were before, which is where I'm currently at.
At this time, unless Magisk releases a TWRP-flashable .zip for v22, or unless there's a way to update to v22 via Fastboot, it doesn't look like updating to v22 will be possible, at least for the Stock Pie ROM.
I've seen on both reddit and XDA that several people are saying they updated to v22 without issue, but it's unclear if they were on Stock or Custom ROM. My guess would be that Custom ROMs are probably working fine and it's the Stock ROM that's having the issue.
At this time, unless Magisk releases a TWRP-flashable .zip for v22, or unless there's a way to update to v22 via Fastboot, it doesn't look like updating to v22 will be possible, at least for the Stock Pie ROM.
Click to expand...
Click to collapse
I simply renamed the available .apk to .zip and it flashed in TWRP.
edit: the ROM I'm using is from this thread, which says it is 99% stock, whatever that means.
Help!! My LG V30 V300L Can't Boot
Boot Show LG LOGO alway.
can't boot entrance.
i try Press hold Power+Volum down = restart.
i try Press hold Power+Volum up = notrespone.
i try Press hold Volum up+put charge = notrespone.
i need to off device.
:crying::crying::crying::crying::crying:
Same problem here buddy!
I have bricked my LG V30 purchased on eBay by following this guide: https://forum.xda-developers.com/lg-v30/how-to/wtf-lg-v30-t3790500
It has a booloop and I can't go to fastboot, download or recovery. When I go to download the screen goes black and Windows detects it as Qloader 9008
At the time of purchase I made sure it was the us998 version but it is refurbished and maybe not its real model. I have two possible causes in mind. The first one that the flashing model does not correspond to my model. The second one that flashes the latest version of Magisk from its website and not from the post
Is there any solution I can reach? I have been reading to extract the dkz and flash the images of the partitions with LG Flash Tool but I don't know if that would work in my case
A greeting!!
mariets said:
Same problem here buddy!
I have bricked my LG V30 purchased on eBay by following this guide: https://forum.xda-developers.com/lg-v30/how-to/wtf-lg-v30-t3790500
It has a booloop and I can't go to fastboot, download or recovery. When I go to download the screen goes black and Windows detects it as Qloader 9008
At the time of purchase I made sure it was the us998 version but it is refurbished and maybe not its real model. I have two possible causes in mind. The first one that the flashing model does not correspond to my model. The second one that flashes the latest version of Magisk from its website and not from the post
Is there any solution I can reach? I have been reading to extract the dkz and flash the images of the partitions with LG Flash Tool but I don't know if that would work in my case
A greeting!!
Click to expand...
Click to collapse
What stage were you at, when it bootlooped? What were you flashing at the time?
Have you tried Master Reset?
https://forum.xda-developers.com/showpost.php?p=76429682&postcount=101
Yes you should use the Magisk in the instructions. You can update later.
Qualcomm 9008 in Device Manger needs Octoplus box to JTAG flash your device to recover. Ebay service has 2 offerings (one from Florida and another from Moldova). I used the guy from Florida (Tennolee) and he did a great job. He messaged me via Ebay and asked me to install Teamviewer. Once my PC has that and my phone is hooked up to USB 2.0, he remotely logged in and install needed software to JTAG this sucker remotely. He had all the KDZ's and you can ask for any versions for your phone you want. He can't do H932 though (no one can apparently)
ChazzMatt said:
What stage were you at, when it bootlooped? What were you flashing at the time?
Have you tried Master Reset?
https://forum.xda-developers.com/showpost.php?p=76429682&postcount=101
Yes you should use the Magisk in the instructions. You can update later.
Click to expand...
Click to collapse
You are a light of hope along the way, friend. These are the points that I followed. Looking at it with perspective. It was an installation disaster. Anything could have failed.
OK * flash twrp: fastboot flash TWRP.img (TWRP-3.2.3-7-default.img re-named as just "TWRP.img")
OK * boot twrp: fastboot boot TWRP.img (TWRP-3.2.3-7-default.img re-named as just "TWRP.img")
OK* swipe to allow modifications (do NOT leave read-only, TWRP NEEDS to be able to make changes to your system.)
OK* select WIPE data
Really I did a full wipe. I know. No sense. * wipe caches
OK * flash Magisk
OK * flash encryption disabler
I did not install it because de official github was down - * flash root check disabler
OK * FORMAT DATA, type yes
OK * reboot to TWRP
OK * re-flash Magisk
DEAD * reboot to system
EDIT: I tried frankenstein. I'm on twrp now and ****ing freaking out!!!! I will keep informing
EDIT: I only haved flash a firmware like the one I had initially (in my case March 8, 2018) prepared for twrp and and followed the WTF guide step by step with calm and has worked. I'm now in HavocOS!! I had a little scare when the twrp has entered bootloop after flash gapps. I've solved it by simply forcing reboot pressing vol +, vol- and power on
Thanks a lot ChazzMatt, i'm blessed and I learned a valuable lesson about material things and flash calmly
God luck, @Ritazizy
A greeting
mariets said:
You are a light of hope along the way, friend. These are the points that I followed. Looking at it with perspective. It was an installation disaster. Anything could have failed.
OK * flash twrp: fastboot flash TWRP.img (TWRP-3.2.3-7-default.img re-named as just "TWRP.img")
OK * boot twrp: fastboot boot TWRP.img (TWRP-3.2.3-7-default.img re-named as just "TWRP.img")
OK* swipe to allow modifications (do NOT leave read-only, TWRP NEEDS to be able to make changes to your system.)
OK* select WIPE data
Really I did a full wipe. I know. No sense. * wipe caches
OK * flash Magisk
OK * flash encryption disabler
I did not install it because de official github was down - * flash root check disabler
OK * FORMAT DATA, type yes
OK * reboot to TWRP
OK * re-flash Magisk
DEAD * reboot to system
EDIT: I tried frankenstein. I'm on twrp now and ****ing freaking out!!!! I will keep informing
EDIT: I only haved flash a firmware like the one I had initially (in my case March 8, 2018) prepared for twrp and and followed the WTF guide step by step with calm and has worked. I'm now in HavocOS!! I had a little scare when the twrp has entered bootloop after flash gapps. I've solved it by simply forcing reboot pressing vol +, vol- and power on
Thanks a lot ChazzMatt, i'm blessed and I learned a valuable lesson about material things and flash calmly
God luck, @Ritazizy
A greeting
Click to expand...
Click to collapse
OK, glad you got it figured out!
This Guide will explain how to root your LG G8X
* Disclaimer*
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed. Please do some research
* YOU are choosing to make these modifications, and if
* you blame me in any way for what happens to your device, I will laugh at you.
*Wait, what? No. Me or somebody else will help you
Click to expand...
Click to collapse
Prerequisites
Unlock phone using the guide here: https://forum.xda-developers.com/t/guide-how-to-unlock-bootloader-of-lg-g8x.4198025/
Do not restore abl before rooting.
Magisk Patched Boot (20e, Indian Variant): https://drive.google.com/file/d/1s2A7RUOptXer5LGMtbGV9SKg0kcyL_NP/view?usp=drivesdk
1. Download the magisk patched boot.
2. Copy it over to your fastboot directory.
3. Connect phone in fastboot mode.
How to put phone to fastboot mode?
#1: Using Button Combination
Power off phone, press and hold Vol- and insert usb cable. You’ll be in fastboot
#2: Using ADB
Connect phone to pc, enable USB Debugging. Then run this command
Code:
adb reboot fastboot
4. Now run the command
Code:
fastboot flash boot Magisk_Patched.img
fastboot reboot
5. Download and install Magisk Manager
6. Done! Your phone is rooted now.
To restore Network follow the guide in bootloader unlock thread...
If you have a different G8X variant or are on a different firmware
1.Backup boot_a or boot_b using QFIL (Partition Manager>Read Data, Check Bootloader unlock guide for more details)
2. Install Magisk Manager
3. Click on Install and use Patch image function.
4. Save the boot image to pc.
5. Flash it in Fastboot using the command given above.
Known Issues: FP is broken
Thankyou
(copypasta'ed from the other thread)
For those who have yet to do this, I suggest extracting boot_a/b at the same time you flash the abl image. Prior to doing the fastboot oem unlock, use the Magisk patch file option (installed on the same or another device, and doesn't need to be rooted) to create a rooted boot image using adb push/pull. Once you fastboot oem unlock, go back into the bootloader and instead of fastboot flash boot, you can fastboot boot magisk_patched.img.
Once you go through the setup, you can open Magisk, which will download and install the full Manager app, at which point it will most likely reboot. You will need to fastboot boot again, and you should be able to do a normal Magisk install. I've usually found that as long as the patched boot is of the same Android version and within a few month of the patch level, it'll boot happily enough to do this. Afterwards, you can restore your abl image as you no longer need to use fastboot commands.
Doing this allows Magisk to save the stock boot image, and also allows you to get OTA updates by restoring the stock image right before any updates. Otherwise you will never be able to do an OTA update as it checks if the boot partition has been modified before installing the updates. Since there are no kdz for the US carrier models, your only other option would be to "brick" your device to try get your carrier's service center to restore a working firmware image.
-- Starfox
Sorry I posted in the wrong thread. I've deleted the contents, but wasn't able to delete the post itself
Guys, I am trying to follow this guide using the "different variant" method, but as soon as I boot after flashing boot.img the touchscreen doesn't work. Only way to get it back is to flash the boot_a.bin and boot_b.bin using QFIL. What am I doing wrong?
Is there a magisk patched image for the g850u20i
Is there an update for magisk patch image for 20b (unlocked US variant)?
Edit: Got my 20b version rooted.
Downloaded stock rom for the G850QM20b, extracted the kdz file to dz to .img grabbed the stock boot_a.img file and ran it in Magisk manager app, took the converted .boot.a.img (now renamed magisk_patched_clT14.img) and dropped it in platform tools, went fast boot, then flashed it. Came back up great, no issues and root access is clear.
Dapeplezchamp said:
Is there a magisk patched image for the g850u20i
Click to expand...
Click to collapse
I have 20j and I can't even get into edl or fastboot... Can you get into fastboot mode? I've tried adb and button combos
robnitro said:
I have 20j and I can't even get into edl or fastboot... Can you get into fastboot mode? I've tried adb and button combos
Click to expand...
Click to collapse
I cannot.I've tried everything I know to do.I'm so cautious with this phone because I got it at a steal off of eBay and would hate to brick it.
Dapeplezchamp said:
I cannot.I've tried everything I know to do.I'm so cautious with this phone because I got it at a steal off of eBay and would hate to brick it.
Click to expand...
Click to collapse
follow the video here, I got it to work
hold power and vol down , itll countdown to reboot.... as soon as it does that- while holding down and power tap the up button
How to Unlock Bootloader and Root Lg G8x + (also a Video Guide)
All fix avilable (no network solved) Watch it carefully do it step by step as showen in my video you will never brick if you follow my video :):love: All required files are in the video description This guide Tested on the firmware (20e...
forum.xda-developers.com
Is there a image for the g850UM20g?
edit:
I have a copy of boot_a but in the fastboot it tells me that I am using abl_b and I don't know if boot_a is compatible with abl_b and i can't enter EDL mode
So my understanding is you can have a rooted phone, but FP will be broken no matter what and possibly audio as well. You can fix this by reinstalling a Pie version from KDZ, fix it then reinstalling a 10, but then the root will be gone (but the bootloader remains unlocked). Is this correct?
zdanee said:
So my understanding is you can have a rooted phone, but FP will be broken no matter what and possibly audio as well. You can fix this by reinstalling a Pie version from KDZ, fix it then reinstalling a 10, but then the root will be gone (but the bootloader remains unlocked). Is this correct?
Click to expand...
Click to collapse
Yes, rooting will be gone and Bootloader remains unlocked forever. You have to root it again in A10
For anyone in the future: you can have both root and fingerprint. Follow the bootloader unlock guide up to the point where you have to backup your boot_a. After that you don't use the patched boot_a in the instructions, instead patch your own version with magisk and flash that instead with QFIL. I now have a working V20h EU version with root, fingerprint and working audio.
Anu one have LMG850UM 20f magisk patched boot file?
Country china
Lg g8x
Kanhei015 said:
Anu one have LMG850UM 20f magisk patched boot file?
Country china
Lg g8x
Click to expand...
Click to collapse
I do. But it's an EU version, so I'm not sure it would work for you. However it's easy to just make your own!
- Install Magisk manager on the phone. You don't need open bootloader or anything for that
- Get your own 20f boot_a using QFIL
- Copy your own boot_a to the phone or on an SD card
- In Magisk Manager you choose to install magisk, select patching an IMG file method and give it the boot_a
- If Magisk reports success you'll now have a magisk_patched_boot_a file. Copy that back to your PC
- Using QFIL flash that in place of your original boot_a
- Keep a copy of your original boot_a thou, you can go back with QFIL at any time.
- If you mess up royally and the phone doesn't boot, you can still recover it by re-flashing your firmware with LGUP 1.17. You'll have to download your region's firmware for that and you'll loose all data, so make a backup beforehand!
edit: double post
zdanee said:
For anyone in the future: you can have both root and fingerprint. Follow the bootloader unlock guide up to the point where you have to backup your boot_a. After that you don't use the patched boot_a in the instructions, instead patch your own version with magisk and flash that instead with QFIL. I now have a working V20h EU version with root, fingerprint and working audio.
Click to expand...
Click to collapse
Hi, thanks for sharing the steps!
I followed your steps but don't have audio/network/fingerprint after flashing patched boot. Later I also tried to restore abl_a/b, then I had audio and network working, but still no fingerprint.
In my case, fingerprint stopped working once bootloader is unlocked, before even flashing the patched boot.
Did you have working fingerprint right after you flash patched boot? Did you restored abl_a/b?
I also tried to follow another post to get fingerprint working, but I can only find 10b kdz of my variant (twn), I downgraded to android 9 using that kdz, still cannot get fingerprint to work.
james508959 said:
Hi, thanks for sharing the steps!
I followed your steps but don't have audio/network/fingerprint after flashing patched boot. Later I also tried to restore abl_a/b, then I had audio and network working, but still no fingerprint.
In my case, fingerprint stopped working once bootloader is unlocked, before even flashing the patched boot.
Did you have working fingerprint right after you flash patched boot? Did you restored abl_a/b?
I also tried to follow another post to get fingerprint working, but I can only find 10b kdz of my variant (twn), I downgraded to android 9 using that kdz, still cannot get fingerprint to work.
Click to expand...
Click to collapse
I also messed up at first, since there were no ready-made boot_a for my region/version I just grabbed the indian one for 20e, and yes, that did break my audio, fingerprint and possibly network, I didn't test that one. I did have a KDZ for my region thou, so I flashed back a 10c version, I needed the 1.17 tool, not the 1.14 or 1.16 one (those did not work) and in my case I needed the second version of 10c, not the first one to fix the fingerprint. After flashing 10c I did all the steps and regained my fingerprint reader without an issue (so no, it did not work right away, I did need to go into the service menu and do the test), audio and network also worked right away. After that I flashed my latest KDZ (20h) and using magisk manager made my own boot_a and was able to root with a working fingerprint. I did not dare to update Magisk after this thou, I only needed it to grant root for my adblocker, and it's hidden from everything else, I don't think I'll ever even start magisk again, so I don't really want to update it either.
Did you restore abl_a/b at all? I can only get into download mode (to use LGUP) after I restore abl_a/b.
Anyways, I think flashing using LGUP overrided the abl, and that's why audio and network worked right away (to my understanding)
My LGUP tool worked fine, but there only 10b for my TWN variant, I couldn't find 10c anywhere... (only 10b, 20a, 20b available)
I never flashed other's patched boot, I used QFIL to get my boot_a.bin and patched it using Magisk on another phone. Then I used fastboot to flash boot. (I did this right after unlocked BL, all before I restored abl).
Did you also use QFIL to get boot_a or did you use KDZ extractor? I'm having problem with my KDZ extractor tool, encoding issue or sth.
My variant is G850EMW, should I try the indian 10c kdz (which is also G850EMW)? Would that work? Not sure what risk cross region flashing poses, or even if LGUP would let me flash it at all.
james508959 said:
Did you restore abl_a/b at all? I can only get into download mode (to use LGUP) after I restore abl_a/b.
Anyways, I think flashing using LGUP overrided the abl, and that's why audio and network worked right away (to my understanding)
My LGUP tool worked fine, but there only 10b for my TWN variant, I couldn't find 10c anywhere... (only 10b, 20a, 20b available)
I never flashed other's patched boot, I used QFIL to get my boot_a.bin and patched it using Magisk on another phone. Then I used fastboot to flash boot. (I did this right after unlocked BL, all before I restored abl).
Did you also use QFIL to get boot_a or did you use KDZ extractor? I'm having problem with my KDZ extractor tool, encoding issue or sth.
My variant is G850EMW, should I try the indian 10c kdz (which is also G850EMW)? Would that work? Not sure what risk cross region flashing poses, or even if LGUP would let me flash it at all.
Click to expand...
Click to collapse
No, I did not restore abl_a/b, and after KDZ the bootloder remained open, so there is no need to, the phone still reports an open bootloader at boot. If it _does_ override it thou it seems it's not neccessary to have, as I could root the phone and could keep the open bootloader anyways.
I used QFIL to get my own boot_a, and used it again to flash it back too.
My EU (Hungarian T-mobile) version is also G850EMW. My understanding is that if LGUP lets you flash a KDZ it's probably gonna work, but in the worst case scenario as long as you have a known good KDZ for your model you can always come back to that, so I guess you can experiment?
I've also only found a 20b version of KDZ for TWN, but it's release date is similar to 20h in the EU, so maybe these numbers doesn't mean they are the same KDZ, only that 20x meant it's Android 10 and the letter is the revision. Based on this it's possibe you don't need a 10c to restore your fingerprint, just try the earliest 10x KDZ you can get your hands on (for me the 10c was the earliest one). Alternatively you can try the 10c I used for mine, it's EU Hungarian, but the default language is still English and you'll re-flash it anyways: https://lg-firmwares.com/downloads-file/21667/G850EMW10c_00_OPEN_EU_DS_OP_1122