Related
Hello everyone, today I made a bull****, let's start from the beginning, my K10 2017 M250n had Android Oreo and I had come to know the exploit LGLAF, I tried, and did not work because I discovered that the flaw was patched on Android Oreo but I had the idea to downgrade to Nougat, after hours of problems due to drivers I can flashare nougat with LG UP in Download Mode, after doing the Downgrade, with the Dual-Boot to Linux on PC I used LGLAF on Linux, I made a backup of the LAF partition, I have the IMG file, a backup of the recovery, always an IMG I created, I did the wipe, I restarted and I tried to boot in fastboot, it does not boot, I tried to start in Download Mode, it does not work, all this to try to unlock the BootLoader, flash the TWRP and root.
Now how do I update and report the Download Mode?
I'm stuck without Fastboot, without Download Mode and with Android Nougat.
http://www.mediafire.com/file/y0d8sj4od5j3a34/laf.img/file
http://www.mediafire.com/file/179cr1b1y2d62cy/recovery.img/file
But you can boot it normally, I guess. Then hopefully Oreo ota update fixes it...
No, I can not find the updates anymore
XRed_CubeX said:
No, I can not find the updates anymore
Click to expand...
Click to collapse
i suggest that you try to update your phone via lg up by downloading the kdz of your exact phone model and without booting into download mode just by booting normal and i hope it solved
no warranty No promises... and no responsibility i take
abdoh01 said:
i suggest that you try to update your phone via lg up by downloading the kdz of your exact phone model and without booting into download mode just by booting normal and i hope it solved
no warranty No promises... and no responsibility i take
Click to expand...
Click to collapse
I tried and does not work, simply before Flash restarts you downloading and mode flash but I'm unloaded mode.
XRed_CubeX said:
No, I can not find the updates anymore
Click to expand...
Click to collapse
And you have done the factory reset? Then maybe laf is needed for the fota too??
At the end is the latest fota update, but no idea if it can be used similar way as before. [***]
https://forum.xda-developers.com/showpost.php?p=59103556&postcount=326
Now it probably should be named as dlpkgfile and placed in /data/fota/ or /cache/fota/ if smaller ...
But how to put it there, IDK... Also LGUP has some FOTA mode but haven't tested it.
LGM250nAT-V20b-EUR-XX-AUG-13-2018+0_fota.up
https://mega.nz/#!WpkERCgK!QiqndSPXG2aaaq7jqoG27IyBvhfd16bh6G2gNs7UoeA
edit: [***] hiddenmenu opens by calling *#546368#*250# and there you'll find that package select
mentioned in the first link. File in /storage/emulated/0/SoftwareUpdate/ shows but I don't want to update yet...
:good:
CXZa said:
And you have done the factory reset? Then maybe laf is needed for the fota too??
At the end is the latest fota update, but no idea if it can be used similar way as before. [***]
https://forum.xda-developers.com/showpost.php?p=59103556&postcount=326
Now it probably should be named as dlpkgfile and placed in /data/fota/ or /cache/fota/ if smaller ...
But how to put it there, IDK... Also LGUP has some FOTA mode but haven't tested it.
LGM250nAT-V20b-EUR-XX-AUG-13-2018+0_fota.up
https://mega.nz/#!WpkERCgK!QiqndSPXG2aaaq7jqoG27IyBvhfd16bh6G2gNs7UoeA
edit: [***] hiddenmenu opens by calling *#546368#*250# and there you'll find that package select
mentioned in the first link. File in /storage/emulated/0/SoftwareUpdate/ shows but I don't want to update yet...
:good:
Click to expand...
Click to collapse
Error RESULT_NOT_EXECUTED
XRed_CubeX said:
Error RESULT_NOT_EXECUTED
Click to expand...
Click to collapse
Pity... it then maybe use laf - although there is also fota tools on
the recovery. What about LGUP, is there fota option or have I dreamed it.
CXZa said:
Pity... it then maybe use laf - although there is also fota tools on
the recovery. What about LGUP, is there fota option or have I dreamed it.
Click to expand...
Click to collapse
The problem that I have formatted laf,i cant boot on download mode, how can I reboot in recovery mode?
XRed_CubeX said:
The problem that I have formatted laf,i cant boot on download mode, how can I reboot in recovery mode?
Click to expand...
Click to collapse
Some fota tools are there in the sbin, but I don't know how can they be activated.
Fota file must be in some default folder and recovery maybe booted having a
command somewhere....
You can reboot to recovery using adb, or in terminal "reboot recovery"
or "setprop sys.powerctl reboot,recovery"
I was thinking that maybe LGUP changes the mode like it does
before flashing kdz files. If in normal mode, that is.
And if it uses recovery mode with fota then it might work.
Just hoping not knowing...
CXZa said:
Some fota tools are there in the sbin, but I don't know how can they be activated.
Fota file must be in some default folder and recovery maybe booted having a
command somewhere....
You can reboot to recovery using adb, or in terminal "reboot recovery"
or "setprop sys.powerctl reboot,recovery"
I was thinking that maybe LGUP changes the mode like it does
before flashing kdz files. If in normal mode, that is.
And if it uses recovery mode with fota then it might work.
Just hoping not knowing...
Click to expand...
Click to collapse
The recovery mode says No Command.
XRed_CubeX said:
The recovery mode says No Command.
Click to expand...
Click to collapse
Press power and then vol up shortly. Same time that is.
CXZa said:
Press power and then vol up shortly. Same time that is.
Click to expand...
Click to collapse
When I try to do FOTA upgrade on LG UP it gives me the error "Error: 0x2000, Fail! MTP is not Running" but when in fact the device to recognize the port MUST be in MTP and I in MTP mode I have it put.
XRed_CubeX said:
When I try to do FOTA upgrade on LG UP it gives me the error "Error: 0x2000, Fail! MTP is not Running" but when in fact the device to recognize the port MUST be in MTP and I in MTP mode I have it put.
Click to expand...
Click to collapse
IDK. Are you using LGUP having a patched exe and the dll?
Is the dll our own? Does it matter if it's own or not? IDK.
Patching it is instructed somewhere...
edit: patching not needed as fota mode shows already.
edit22: have you the WPDAPI.exe in the LGUP\main\Common dir?
the LGUP_Common.dll might need it...
There is still that other way, using that "Activity Launcher" app,
or "am start -n com.lge.lgfota.permission/com.lge.lgfota.permission.DmcEzUpdateStart"
And what about a newer tool, LGBridge? I read somewhere at LGlaf github
that its or SupportTool's protocol data looks different compared to LGlaf.
https://github.com/Lekensteyn/lglaf/issues/7
What else is different...
CXZa said:
IDK. Are you using LGUP having a patched exe and the dll?
Is the dll our own? Does it matter if it's own or not? IDK.
Patching it is instructed somewhere...
edit: patching not needed as fota mode shows already.
edit22: have you the WPDAPI.exe in the LGUP\main\Common dir?
the LGUP_Common.dll might need it...
There is still that other way, using that "Activity Launcher" app,
or "am start -n com.lge.lgfota.permission/com.lge.lgfota.permission.DmcEzUpdateStart"
And what about a newer tool, LGBridge? I read somewhere at LGlaf github
that its or SupportTool's protocol data looks different compared to LGlaf.
https://github.com/Lekensteyn/lglaf/issues/7
What else is different...
Click to expand...
Click to collapse
How to get WPDAPI?
XRed_CubeX said:
How to get WPDAPI?
Click to expand...
Click to collapse
It's many times included in those hacked version packages.
I guess it was included with dll needed, but don't know for sure.
Here it's needed
https://forum.xda-developers.com/showpost.php?p=75677301&postcount=6
I don't when it will be needed in this long thread.
https://forum.xda-developers.com/lg-g5/how-to/unlocking-lgup-features-fun-profit-t3634650
Maybe it's said somewhere in it. The exe is mentioned in the dll though...
From where? See the attachment. The UI_Config.lgl in it gives more options.
No hacking and cracking needed. But is a hacked version better, IDK...
CXZa said:
It's many times included in those hacked version packages.
I guess it was included with dll needed, but don't know for sure.
Here it's needed
https://forum.xda-developers.com/showpost.php?p=75677301&postcount=6
I don't when it will be needed in this long thread.
https://forum.xda-developers.com/lg-g5/how-to/unlocking-lgup-features-fun-profit-t3634650
Maybe it's said somewhere in it. The exe is mentioned in the dll though...
From where? See the attachment. The UI_Config.lgl in it gives more options.
No hacking and cracking needed. But is a hacked version better, IDK...
Click to expand...
Click to collapse
Always the same error, but also the method of DmcEzUpdateStart remains with the words "FOTA EASY UPDATE" and then crash.
No solution?
There is a scatter file so you can flash it from SP Flash Tools??
XRed_CubeX said:
There is a scatter file so you can flash it from SP Flash Tools??
Click to expand...
Click to collapse
LG has made so much changes that I think that it doesn't work as mtk device anymore.
Anyway the MTK driver package IDs probably have to be changed... at least.
With LG drivers installed, the SP Flash Tool readback started, a text about
LG connection was shown, but it just failed - miserably...
If you uninstall the lg drivers and maybe mtk too. And then connect it
(without the battery?), you might see that it shows itself as MTK preloader
for a second or two. With lg drivers it shows as something else, I think...
When doing readback from a normal mtk device I think it is the preloader
which is used. When downloading a firmware, I don't remember does it
switch to another state that is used... serial or whatever the text says
in SP Flash Tool, but was it with or without the preloader text... ??? IDR...
Hello together,
after many tries to get my nokia 3.2 rooted, i end up now with a black screen.
Only the Qulacomm mode is working.
Get anyone managed to flash the stock firmware with QFIL provided from the rooting thread?
I always end up with "sahara fails".
Every help is welcome!
Thanks!!!!
After many tries I have finally put my phone back to life.
My instructions how to do it will come soon!
page1875 said:
After many tries I have finally put my phone back to life.
My instructions how to do it will come soon!
Click to expand...
Click to collapse
please do, i encountered a similar problem.
HowTo Flash STOCK 00WW
1. Trigger nokia 3.2 to edl-mode (https://forum.xda-developers.com/nokia-3-2/how-to/guide-how-to-trigger-nokia-3-2-to-edl-t3962841)
2. Flash the given image from this thread (https://forum.xda-developers.com/nokia-3-2/how-to/rooted-nokia-3-2-t3945206)
- This was the main problem. I never managed it to flash the image with the Windows Programmer QFIL. After more research in Internet, i found finally a Linux application called QDL that work directly without any problems. This application can be found here https://www.96boards.org/documentation/consumer/guides/qdl.md.html .
- Flashing the software ends up into a bootloop. Also i got a message on startup that the bootloader could not be trusted anymore. After a software-update, this message disappears.
3. Flash all the user images again manually with fastboot.
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash vendor vendor.img
flastboot flash vbmeta vbmeta.img
Whyever you have to flash this partitions only to the active partitions without the suffix _a or _b.
Then the bootloop is finished.
The phone boots normally to Android ONE.
The next problem which occurs on my phone is now that it is not able to connect to GSM network. I guess this happens because i deleted all the necessary partitions for the modem (modemst1, modemst2, fsg).
I get it managed to restore the imei, but still no service available.
In original my phone had the software 00EEA. Perhaps they use different drivers. My luck is that i got a cheap damaged phone from ebay with that firmware.
My next step is to modify the code from QDL that it can read the partitions from the damaged phone and save the software to computer.
Then i will flash this software to my phone and look if this software will run on my phone!
page1875 said:
1. Trigger nokia 3.2 to edl-mode (https://forum.xda-developers.com/nokia-3-2/how-to/guide-how-to-trigger-nokia-3-2-to-edl-t3962841)
2. Flash the given image from this thread (https://forum.xda-developers.com/nokia-3-2/how-to/rooted-nokia-3-2-t3945206)
- This was the main problem. I never managed it to flash the image with the Windows Programmer QFIL. After more research in Internet, i found finally a Linux application called QDL that work directly without any problems. This application can be found here https://www.96boards.org/documentation/consumer/guides/qdl.md.html .
- Flashing the software ends up into a bootloop. Also i got a message on startup that the bootloader could not be trusted anymore. After a software-update, this message disappears.
3. Flash all the user images again manually with fastboot.
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash vendor vendor.img
flastboot flash vbmeta vbmeta.img
Whyever you have to flash this partitions only to the active partitions without the suffix _a or _b.
Then the bootloop is finished.
The phone boots normally to Android ONE.
The next problem which occurs on my phone is now that it is not able to connect to GSM network. I guess this happens because i deleted all the necessary partitions for the modem (modemst1, modemst2, fsg).
I get it managed to restore the imei, but still no service available.
In original my phone had the software 00EEA. Perhaps they use different drivers. My luck is that i got a cheap damaged phone from ebay with that firmware.
My next step is to modify the code from QDL that it can read the partitions from the damaged phone and save the software to computer.
Then i will flash this software to my phone and look if this software will run on my phone!
Click to expand...
Click to collapse
Thank you for your reply, it seems that your problem is more complicated than mine.
I have a global variant with 00WW software and i attempt to root the phone. I successfully flash the patched boot.img and had root access. However wi-fi didn't work after that.
Since before flashing the patched boot.img my phone was running on a different firmware from the one that boot.img was extracted from, so i think that was the problem.
I attempted to use QFIL to flash my phone back to 00WW_15 and it failed half way, bricked my phone.
Normally you can use the EDL Mode every time.
My phone only showed black screen and it was always possible to connect in EDL Mode and flash again.
Did you try to flash again? What happens then?
Flash the given image from this thread (https://forum.xda-developers.com/nokia-3-2/how-to/rooted-nokia-3-2-t3945206)
Click to expand...
Click to collapse
What did you mean by Flash the given image ? Was it flash the firmware package with QFIL ?
My main problem is flashing, it always failed half-way and the error log reported that needed files were missing from the package.
Okay. I used the linux program QDL for flashing.
But i saw, that in the xml file rawprogram0.xml a few files are missing.
The linux programm jump over these files but perhaps QFIL do not.
For example is there a picture.img listed which is not available..
Try to remove them manually from the rawfile and test again.
page1875 said:
Okay. I used the linux program QDL for flashing.
But i saw, that in the xml file rawprogram0.xml a few files are missing.
The linux programm jump over these files but perhaps QFIL do not.
For example is there a picture.img listed which is not available..
Try to remove them manually from the rawfile and test again.
Click to expand...
Click to collapse
@update:
Also the files "demoapp.img", "dp_AP_signed.mbn" and "dp_MSA_signed.mbn" are missing.
Remove them from the XML file and try again!
@update
Okay QFIL still failed half-way but i manually flash the user images and my phone boots normally now
Hello,
my nokia 3.2 europe variant wont boot up its stuck in fastboot mode. What can i do to bring it back?
I get this: FAILED (remote: partition table doesn't exist)
P.S. if i do a fastboot reboot it boots back into bootloader
I also had this problems for many many times and don't know what went wrong when this happens.
The only thing that helped was flashing the complete firmware again in EDL-mode.
You can try first to flash only the 5 user-images with fastboot, which i mentioned before in this thread.
I uploaded this files for you, because you don't will find the europe files in internet yet.
Here is the link:
https://transfernow.net/81iti7q21s0s
Good luck!
Hi,
Thank you very much. Is this the complete Firmware? (All Images from Device) Another question: I couldnt Access the recovery System. Did you have the same Problem when your Nokia didnt boot up and was stuck in Bootloader? So is this normal that the recovery is unaccessible?
Yes, that also happens sometimes with my phone.
No, that are not all firmware files, which you need to do a full EDL-Flash.
But with this files you can first try a fastboot flash!
If it does not work, you can take all the other files from the Global-Stock-Firmware, given in the thread https://forum.xda-developers.com/nokia-3-2/how-to/rooted-nokia-3-2-t3945206.
Delete the 5 files with the same names, flash the Global-Stock-Firmware in EDL-Mode, with QFIL or QDL, (without the 5 files) and in the following flash the 5 europe-image files with fastboot.
Thanks, ive sent it in and got Friday a 00WW Variant of the device back. I will upload those User images for 00EEA to my Google drive so that anyone who needs those files can download them
hello
i wanted to install custom rom and i bricked my phone. i lost recovery mode and i have only fastboot mode .but can not write any img file for example twrp.img beacuse show this error : FAILED (remote: partition table doesn't exist). can please anyone help me.
thank you very much
thanks so much i was able to put my phone back to life. i had almost given up.
smure said:
thanks so much i was able to put my phone back to life. i had almost given up.
Click to expand...
Click to collapse
Hello to ervery one
how you flashed your phone. can you please guide?
i am also stucked in fastboot mode after rooting.
damn... I've been finding on how to restore the wifi and sound because I uninstalled magisk and it failed. I don't think I can thank you enough for this post.
Hi everybody,
I'm stuck in a pretty damn mess here. I have an Galaxy S20+ G985F device which is stuck in Download Mode with no ROM installed, a locked bootloader, and a changed recovery and vbmeta (one that came with a working TWRP image) image flashed. :/
Is thee any way to get out of this situation of which I don't know how exactly the phone got there? Seems like a mistakenly locked boot loader by long pressing the Vol Up button once in the Booloader Lock/Unlock menu.
When trying to flash with heimall the phone says, ie.:
Custom Binary (VBMETA) Blocked By OEM Lock
Any chance on recovering the device? There should actually no ROM be installed at the moment. Cannot boot anything, the device always goes into Download mode only showing an entry for "Vol Down + Side Key for 7 seconds: Cancel (restart phone)" which results in the device going to the screen again...
Flashing with "odin4" on Linux says:
odin4 -b BL_G985FXXU1ATD3_CL18335124_QB30559577_REV01_user_low_ship_MULTI_CERT.tar.md5 -a AP_G985FXXU1ATD3_CL18335124_QB30559577_REV01_user_low_ship_MULTI_CERT_meta_OS10.tar.md5 -c CP_G985FXXU1ATCT_CP15511927_CL18335124_QB30141694_REV01_user_low_ship_MULTI_CERT.tar.md5 -s CSC_OMC_OXM_G985FOXM1ATD3_CL18335124_QB30559577_REV01_user_low_ship_MULTI_CERT.tar.md5
Check file : BL_G985FXXU1ATD3_CL18335124_QB30559577_REV01_user_low_ship_MULTI_CERT.tar.md5
Check file : AP_G985FXXU1ATD3_CL18335124_QB30559577_REV01_user_low_ship_MULTI_CERT_meta_OS10.tar.md5
Check file : CP_G985FXXU1ATCT_CP15511927_CL18335124_QB30141694_REV01_user_low_ship_MULTI_CERT.tar.md5
Check file : CSC_OMC_OXM_G985FOXM1ATD3_CL18335124_QB30559577_REV01_user_low_ship_MULTI_CERT.tar.md5
/dev/bus/usb/001/054
/dev/bus/usb/001/054
Setup Connection
Set Partition
Receive PIT Info
success getpit
Upload Binaries
Binary arrange fail. Binary is invalid
Fail uploadBinaries
Kind regards and thanks for any help,
Marc
try with samsung smart switch with emergency software recovery
kosique said:
Hi everybody,
I'm stuck in a pretty damn mess here. I have an Galaxy S20+ G985F device which is stuck in Download Mode with no ROM installed, a locked bootloader, and a changed recovery and vbmeta (one that came with a working TWRP image) image flashed. :/
Is thee any way to get out of this situation of which I don't know how exactly the phone got there? Seems like a mistakenly locked boot loader by long pressing the Vol Up button once in the Booloader Lock/Unlock menu.
When trying to flash with heimall the phone says, ie.:
Custom Binary (VBMETA) Blocked By OEM Lock
Any chance on recovering the device? There should actually no ROM be installed at the moment. Cannot boot anything, the device always goes into Download mode only showing an entry for "Vol Down + Side Key for 7 seconds: Cancel (restart phone)" which results in the device going to the screen again...
Flashing with "odin4" on Linux says:
odin4 -b BL_G985FXXU1ATD3_CL18335124_QB30559577_REV01_user_low_ship_MULTI_CERT.tar.md5 -a AP_G985FXXU1ATD3_CL18335124_QB30559577_REV01_user_low_ship_MULTI_CERT_meta_OS10.tar.md5 -c CP_G985FXXU1ATCT_CP15511927_CL18335124_QB30141694_REV01_user_low_ship_MULTI_CERT.tar.md5 -s CSC_OMC_OXM_G985FOXM1ATD3_CL18335124_QB30559577_REV01_user_low_ship_MULTI_CERT.tar.md5
Check file : BL_G985FXXU1ATD3_CL18335124_QB30559577_REV01_user_low_ship_MULTI_CERT.tar.md5
Check file : AP_G985FXXU1ATD3_CL18335124_QB30559577_REV01_user_low_ship_MULTI_CERT_meta_OS10.tar.md5
Check file : CP_G985FXXU1ATCT_CP15511927_CL18335124_QB30141694_REV01_user_low_ship_MULTI_CERT.tar.md5
Check file : CSC_OMC_OXM_G985FOXM1ATD3_CL18335124_QB30559577_REV01_user_low_ship_MULTI_CERT.tar.md5
/dev/bus/usb/001/054
/dev/bus/usb/001/054
Setup Connection
Set Partition
Receive PIT Info
success getpit
Upload Binaries
Binary arrange fail. Binary is invalid
Fail uploadBinaries
Kind regards and thanks for any help,
Marc
Click to expand...
Click to collapse
And also you cannot turn off your phone? )
Prepare a recovery tar file with vbmeta and recovery in it. Flash with odin and reboot. Then disable encription.
Then redo the initial process of flashing tar file with or without the rest of the rom files.
If ur alao flashing rom files put your recovery tar file to others section in odin.
Hey guys,
I'm currently stuck in a fastboot loop after trying to install Magisk after flashing the Arrow ROM. I believe I messed up when choosing between boot_a and boot_b and flashing the patched img via QFIL. I initally patched boot_a, but when that didn't work I rebooted and patched boot_b. I did this because when I installed Arrow the instructions asked me to select the device slot that was inactive. I thought this meant it was swapping my device slot from A to B, but I probably got that very wrong. I did go into EDL mode and flash my original boot_a and boot_b in hopes it would reverse my mistake, but that did not work.
When I attempt booting the TWRP zip from the lineage guide archive I get this error "failed to load/authenticate boot image". I'm assuming this is because it wants an .img file and not a zip. If I try flashing the same zip file I get this error "Cannot flash this partition in unlocked state".
I did make a backup of all partitions via TWRP before this, but I'm unsure how I'd go about restoring everything. I do have access to EDL mode.
Any help is appreciated. This isn't a primary device though, so if it's bricked I'm not going to be that upset over it. Just something I wanted to try for fun. Haven't rooted a device in years. The G8 was a bit more difficult than I recall, so I'm sure I made a mistake somewhere.
Update 1
I flashed the ABL enginnering file and have some progress. Now fastboot shows my Active A/B Slot. It is set to B now, it was A originally, which I guess confirms that the Arrow OS instructions did switch from A to B. Maybe patching both through Magisk broke the boot image? If I'm understanding this correctly.
Update 2
While in fastboot (Phone was still looping) I entered the following command to change from Active Slot B to A, "fastboot --set-active=a". I've read this could potentially brick your device, but since my device was originally set to A and it was a brick at the moment already I took the risk. Booted into the recovery mode and selected factory reset. It took about five minutes, but I'm now back to the setup screen in the OS. Glad to be back to this point. Now I just need to figure out how to get Magisk Root working without repeating this process.
Update 3
Almost forgot to boot back into EDL, load up QFIL and push the original abl_a and abl_b files back to your phone. Otherwise you won't have any touch input.
Update 4
I seemed to have messed it up again. I tried locking the bootloader back, so I'd stop getting the error message upon bootup. I've decided there is no benefit to unlocking the bootloader and rooting for my purposes. Just wanted to try it out. After doing so I started getting an error stating the device failed security checks, so I pushed the abl engineering file back to the device to unlock it. After I went to push the stock abl_a and b files and decided to go ahead and push the stock boot_a and boot_b to make sure everything was back to normal. Which I didn't think was a big deal, but now I can't boot into the phone without using the abl engineering file.
At the moment I'm unsure what to do. If I push the abl_a and b stock files the phone goes into a fastboot bootloop again. Can't run any commands that way either. I have to boot the abl enginnering file to do so, which in turn allows me to get into the OS but disables touch input. So at the moment I think it's bricked.
If I could find a TWRP image file to flash with the abl enginnering file I could possibly perform a restore from the original backups I made, but I'm unsure where to find one since TWRP doesn't really exist for the G8. I just have a zip file.
Overall not too much of a loss, but the G8 was a great DAP. Hate to lose it. If anyone has any suggestions I'm all ears.
Absolutely the same issue. I wrote about it in arrowOS thread . But I did not try to flash engineering abl. I'm begging you, if your will find solution, please write here about it. I am also notice you here, if resolve this issue.
Jimmynidas said:
Hey guys,
I'm currently stuck in a fastboot loop after trying to install Magisk after flashing the Arrow ROM. I believe I messed up when choosing between boot_a and boot_b and flashing the patched img via QFIL. I initally patched boot_a, but when that didn't work I rebooted and patched boot_b. I did this because when I installed Arrow the instructions asked me to select the device slot that was inactive. I thought this meant it was swapping my device slot from A to B, but I probably got that very wrong. I did go into EDL mode and flash my original boot_a and boot_b in hopes it would reverse my mistake, but that did not work.
When I attempt booting the TWRP zip from the lineage guide archive I get this error "failed to load/authenticate boot image". I'm assuming this is because it wants an .img file and not a zip. If I try flashing the same zip file I get this error "Cannot flash this partition in unlocked state".
I did make a backup of all partitions via TWRP before this, but I'm unsure how I'd go about restoring everything. I do have access to EDL mode.
Any help is appreciated. This isn't a primary device though, so if it's bricked I'm not going to be that upset over it. Just something I wanted to try for fun. Haven't rooted a device in years. The G8 was a bit more difficult than I recall, so I'm sure I made a mistake somewhere.
Update 1
I flashed the ABL enginnering file and have some progress. Now fastboot shows my Active A/B Slot. It is set to B now, it was A originally, which I guess confirms that the Arrow OS instructions did switch from A to B. Maybe patching both through Magisk broke the boot image? If I'm understanding this correctly.
Update 2
While in fastboot (Phone was still looping) I entered the following command to change from Active Slot B to A, "fastboot --set-active=a". I've read this could potentially brick your device, but since my device was originally set to A and it was a brick at the moment already I took the risk. Booted into the recovery mode and selected factory reset. It took about five minutes, but I'm now back to the setup screen in the OS. Glad to be back to this point. Now I just need to figure out how to get Magisk Root working without repeating this process.
Update 3
Almost forgot to boot back into EDL, load up QFIL and push the original abl_a and abl_b files back to your phone. Otherwise you won't have any touch input.
Update 4
I seemed to have messed it up again. I tried locking the bootloader back, so I'd stop getting the error message upon bootup. I've decided there is no benefit to unlocking the bootloader and rooting for my purposes. Just wanted to try it out. After doing so I started getting an error stating the device failed security checks, so I pushed the abl engineering file back to the device to unlock it. After I went to push the stock abl_a and b files and decided to go ahead and push the stock boot_a and boot_b to make sure everything was back to normal. Which I didn't think was a big deal, but now I can't boot into the phone without using the abl engineering file.
At the moment I'm unsure what to do. If I push the abl_a and b stock files the phone goes into a fastboot bootloop again. Can't run any commands that way either. I have to boot the abl enginnering file to do so, which in turn allows me to get into the OS but disables touch input. So at the moment I think it's bricked.
If I could find a TWRP image file to flash with the abl enginnering file I could possibly perform a restore from the original backups I made, but I'm unsure where to find one since TWRP doesn't really exist for the G8. I just have a zip file.
Overall not too much of a loss, but the G8 was a great DAP. Hate to lose it. If anyone has any suggestions I'm all ears.
Click to expand...
Click to collapse
It's a little confusing to try to determine where you are with this, but I can tell you that for the G8, to get twrp 'injected' into the boot partition, you use magisk and flash the zip, you don't 'boot' it.
So to accomplish that, you need **your specific variant** boot partition with magisk injected into it. You can do that yourself by using the magisk manager, or by simply asking if anyone has that available.
But, you'd then have twrp, and you could flash backups, but, from what you say, it's hard to determine if that's going to help.
If you have one of the variants that has the kdz available, I'd suggest simply use LGUP and flash your kdz, and start from scratch.
Lastly, re locking the bootloader. Numerous people make this mistake, but you can't re-lock it unless you're on pure stock (no modifications at all). If you try to re-lock it and yer not on a freshly flashed stock kdz, you can end with 'edl mode only' device.
cheers
AsItLies said:
It's a little confusing to try to determine where you are with this, but I can tell you that for the G8, to get twrp 'injected' into the boot partition, you use magisk and flash the zip, you don't 'boot' it.
So to accomplish that, you need **your specific variant** boot partition with magisk injected into it. You can do that yourself by using the magisk manager, or by simply asking if anyone has that available.
But, you'd then have twrp, and you could flash backups, but, from what you say, it's hard to determine if that's going to help.
If you have one of the variants that has the kdz available, I'd suggest simply use LGUP and flash your kdz, and start from scratch.
Lastly, re locking the bootloader. Numerous people make this mistake, but you can't re-lock it unless you're on pure stock (no modifications at all). If you try to re-lock it and yer not on a freshly flashed stock kdz, you can end with 'edl mode only' device.
cheers
Click to expand...
Click to collapse
As of right now I have a kdz for my phone, I have a Verizon model. Where I'm having trouble with now is I can't get the phone into Download mode. When I do it says my device failed a routine safety check and then boots to fastboot mode.
I also have a couple patched magisk boot partitions from the initial install. I loaded them via QFIL and I can now get to the Verizon bootup screen, but it gets stuck in a loop.
Update:
I got into Download mode by going into the system recovery and doing a factory reset. Now I need to figure out LG UP.
Last Update (Hopefully) Lol:
I installed the kdz using LGUP and it seems to have worked! I'm back in the stock OS and touch input is working. I'm relieved. I hate leaving things like this in a broken state if it's possible to fix it.
Thank you @AsItLies for responding and helping out!
Pukkaras said:
Absolutely the same issue. I wrote about it in arrowOS thread . But I did not try to flash engineering abl. I'm begging you, if your will find solution, please write here about it. I am also notice you here, if resolve this issue.
Click to expand...
Click to collapse
What I did was put the phone back into EDL mode and open QFIL. I loaded my original magisk patched .img file. This got me out of the Fastboot loop. Then after holding volume down and power to reset the phone out of EDL mode I pressed volume down and power again to boot into the modified system recovery. This took a few attempts as it's really finicky.
Once I was in the modified system recovery I performed a factory reset. This seems to have resolved my "Failed routine security check" error when trying to access Download mode. Now that I was no longer getting that error I booted backup into the modified system recovery and hit power down. Make sure your phone is not plugged into your PC at this time or else it will just boot back up.
Once your phone is off and unplugged, hold volume up and then plug the phone back into the PC. Hold volume up until download mode starts. Now you can go go about installing the kdz of your phone.
Now I'm not sure what model your phone is, but since mine was Verizon I found a Verizon KDZ. Then downloaded LGUP. There are a lot of different variations of LGUP, but for my G8 I needed at least 1.16. So I download the Lab version (Probably not right. It scaled very small, but hey, it worked).
You also need to download the DLL for your phone and place it in your Program FIles (x86)/LG Electronics/LG UP/Model/Common folder. I did have to create the Common folder for some reason, but after I did everything worked fine. Make sure to rename the DLL "lgup_common" (without quotes).
You'll also need the LG Drivers for your phone as well, if you haven't installed them already.
I'll post a couple links for you below of where I got this information or files from. I hope this all helps. If you have any questions just let me know. I'm no expert, but I'll do my best to help.
Links:
This link has the DLL, LG Drivers, and a link to LG UP
G820UM20i:Verizon LG G8 ThinQ Firmware Update with December 2020 security Patch
G820UM20i:Verizon LG G8 ThinQ Firmware Update with December 2020 security Patch - Firmware Update
www.mylgphones.com
Link to KDZ: https://lg-firmwares.com/lg-lmg820um-firmwares/
If you have ATT or Sprint I do not believe there are KDZs available.
Please let me know if you have any questions or if I need to clarify anything.
Woo, thats great, that you resolve your problem! I will try to do all like in your manual.
imei.guru said, that for my imei i have :
Model: LGABCD
Region: ABC
LG LMG820N
With such region i did not find kdz at lg-firmwares.com
When my smartphone boot up (when it was worked) i see LG U+ when booting.
Also it was trying to set korean language. What do you think, which kdz should I take? And what version of android?
also solved my problems - here i described here how https://forum.xda-developers.com/t/...lg-g8-alphaplus-alphalm.4354847/post-86038237
Jimmynidas said:
What I did was put the phone back into EDL mode and open QFIL. I loaded my original magisk patched .img file. This got me out of the Fastboot loop. Then after holding volume down and power to reset the phone out of EDL mode I pressed volume down and power again to boot into the modified system recovery. This took a few attempts as it's really finicky.
Once I was in the modified system recovery I performed a factory reset. This seems to have resolved my "Failed routine security check" error when trying to access Download mode. Now that I was no longer getting that error I booted backup into the modified system recovery and hit power down. Make sure your phone is not plugged into your PC at this time or else it will just boot back up.
Once your phone is off and unplugged, hold volume up and then plug the phone back into the PC. Hold volume up until download mode starts. Now you can go go about installing the kdz of your phone.
Now I'm not sure what model your phone is, but since mine was Verizon I found a Verizon KDZ. Then downloaded LGUP. There are a lot of different variations of LGUP, but for my G8 I needed at least 1.16. So I download the Lab version (Probably not right. It scaled very small, but hey, it worked).
You also need to download the DLL for your phone and place it in your Program FIles (x86)/LG Electronics/LG UP/Model/Common folder. I did have to create the Common folder for some reason, but after I did everything worked fine. Make sure to rename the DLL "lgup_common" (without quotes).
You'll also need the LG Drivers for your phone as well, if you haven't installed them already.
I'll post a couple links for you below of where I got this information or files from. I hope this all helps. If you have any questions just let me know. I'm no expert, but I'll do my best to help.
Links:
This link has the DLL, LG Drivers, and a link to LG UP
G820UM20i:Verizon LG G8 ThinQ Firmware Update with December 2020 security Patch
G820UM20i:Verizon LG G8 ThinQ Firmware Update with December 2020 security Patch - Firmware Update
www.mylgphones.com
Link to KDZ: https://lg-firmwares.com/lg-lmg820um-firmwares/
If you have ATT or Sprint I do not believe there are KDZs available.
Please let me know if you have any questions or if I need to clarify anything.
Click to expand...
Click to collapse
Can you share the LGUP 1.16 that worked for you. The link you provided has LGUP 1.16 [Orignal from LG] – No patched – Lab Version and that does not work or not even opening after installation. Thanks.
indrajyoti_indra said:
Can you share the LGUP 1.16 that worked for you. The link you provided has LGUP 1.16 [Orignal from LG] – No patched – Lab Version and that does not work or not even opening after installation. Thanks.
Click to expand...
Click to collapse
I just tried installing it from scratch and other than it asking for the LG driver it launched on my end. Are you going into your start menu and opening LGUP?
Jimmynidas said:
I just tried installing it from scratch and other than it asking for the LG driver it launched on my end. Are you going into your start menu and opening LGUP?
Click to expand...
Click to collapse
I find out that Windows 11 is the problem. Something to do with stupid driver signature. Used Windows 10 and that worked. Thanks.
Bootloader is unlocked.
I was running nokia-tool.exe to restore it to stock. nokia-tool.exe crashed in the middle.
Now the screen never comes on (e.g. no Android One logo). However, oddly, the phone is working. For example, I can boot it and I hear the usual chime as it boots and when it's booted. I get the Nokia 6.1 appearing as an attached device. Also, I can get it into fastboot (even though the screen appears dead) and I can see the device in fastboot devices.
I have tried flashing boot.img, system.ing, vendor.img and then wiping userdata with fastboot -w option.
But the screen remains stubbonly dead. Oh and yes, it was working perfectly before nokia-tool.exe, so it's not a hardware issue.
Any ideas?
mossywell said:
Bootloader is unlocked.
I was running nokia-tool.exe to restore it to stock. nokia-tool.exe crashed in the middle.
Now the screen never comes on (e.g. no Android One logo). However, oddly, the phone is working. For example, I can boot it and I hear the usual chime as it boots and when it's booted. I get the Nokia 6.1 appearing as an attached device. Also, I can get it into fastboot (even though the screen appears dead) and I can see the device in fastboot devices.
I have tried flashing boot.img, system.ing, vendor.img and then wiping userdata with fastboot -w option.
But the screen remains stubbonly dead. Oh and yes, it was working perfectly before nokia-tool.exe, so it's not a hardware issue.
Any ideas?
Click to expand...
Click to collapse
Hi,
Did you try using the OSA Tool?
It worked for me quite successfully when my Nokia 6.1 device failed to boot and I was looking for ways to restore the STOCK ROM and the recovery.
However, I unlocked my Nokia 6.1 Bootloader before proceeding with the further steps.
I followed the techmesto guide to successfully unlock my boot loader.
Once boot loader is unlocked, you can use these web-links and I am hopeful that you will get your device functioning well in no-time:
Download the Stock Rom through this web link
Here's how you can use OST Tool to install STOCK ROM
Links to download OST Tool:
Alternate Link = https://androidmtk.com/use-ost-tool
Download OST Tool = https://androidmtk.com/ost-tool
Just follow the steps listed in the above guides properly and all will be fine.
Let know if this works out for you.
Cheers,
Manu
mAnN14 said:
Hi,
Did you try using the OSA Tool?
It worked for me quite successfully when my Nokia 6.1 device failed to boot and I was looking for ways to restore the STOCK ROM and the recovery.
However, I unlocked my Nokia 6.1 Bootloader before proceeding with the further steps.
I followed the techmesto guide to successfully unlock my boot loader.
Once boot loader is unlocked, you can use these web-links and I am hopeful that you will get your device functioning well in no-time:
Download the Stock Rom through this web link
Here's how you can use OST Tool to install STOCK ROM
Links to download OST Tool:
Alternate Link = https://androidmtk.com/use-ost-tool
Download OST Tool = https://androidmtk.com/ost-tool
Just follow the steps listed in the above guides properly and all will be fine.
Let know if this works out for you.
Cheers,
Manu
Click to expand...
Click to collapse
Thanks for the reply - I've hit a roadblock: the link to the ROM is only for the img files, not the nb0 files. (The author says "It is already advised that the Nokia Service Tool only supports firmware files in the .nb0 or the .mlf format. You can download them from the below-mentioned links" and then failed to link to them! Any ideas where the stock nb0 files are? I searched this forum and couldn't find them.
EDIT: Think I might have found one Googling...
EDIT2: I found PL2-354E-0-00WW-B01.nb0
When I run the OST tool and click the "Edit Phone Information", I get "Boot FTM Mode Fail!". If I OK that (I read that this error is OK to ignore) and carry on, if just hangs at "Checking device status...".
mossywell said:
Thanks for the reply - I've hit a roadblock: the link to the ROM is only for the img files, not the nb0 files. (The author says "It is already advised that the Nokia Service Tool only supports firmware files in the .nb0 or the .mlf format. You can download them from the below-mentioned links" and then failed to link to them! Any ideas where the stock nb0 files are? I searched this forum and couldn't find them.
EDIT: Think I might have found one Googling...
Click to expand...
Click to collapse
Glad to know that you found one yourself. Let know how that pans out for you. In case, you need any assistance, drop a reply and me / someone from the forum shall assist you.
Cheers,
Manu
mAnN14 said:
Glad to know that you found one yourself. Let know how that pans out for you. In case, you need any assistance, drop a reply and me / someone from the forum shall assist you.
Cheers,
Manu
Click to expand...
Click to collapse
I found PL2-354E-0-00WW-B01.nb0
When I run the OST tool and click the "Edit Phone Information", I get "Boot FTM Mode Fail!". If I OK that (I read that this error is OK to ignore) and carry on, if just hangs at "Checking device status...".
Been sitting at that for about 10 minutes.
mossywell said:
I found PL2-354E-0-00WW-B01.nb0
When I run the OST tool and click the "Edit Phone Information", I get "Boot FTM Mode Fail!". If I OK that (I read that this error is OK to ignore) and carry on, if just hangs at "Checking device status...".
Been sitting at that for about 10 minutes.
Click to expand...
Click to collapse
Don't click on the "Edit phone information" as many guides recommend.
Follow these steps instead:
Download your STOCK ROM and extract it in a new folder
Download OSA Tool (crack version) >> Install it on your system >> Paste the crack files in the default installation folder
Stay connected with your internet >> Run the tool and click on OK >> You will arrive at the first screen of the OSA Tool
Switch off your device >> Use "Power + Volume Down" key combination to boot into the "Fast boot mode."
Click on NEXT >> Locate your extracted STOCK ROM FILE >>> Add it to the tool and from the drop-down, select Emergency mode/ Normal mode depending on your situation.
Note: Emergency mode is useful if your device is dead and nothing works. It will erase your personal data completely.
The other mode i.e., "Normal mode" is useful if your device works fine, and you want to simply flash the STOCK ROM without erasing your personal data.
Once the mode is chosen, click NEXT >> Let the process begin
You will get a success message once the process gets finished
Close the OSA Tool and disconnect your device
In most cases, your device will auto-reboot >> If not, reboot it manually
Once booted up, you shall have your STOCK ROM installed successfully
Note:
I downloaded my STOCK ROM from this link - STOCK ROM for Nokia 6.1 (2018)
I used OSA Tool v6.2.8 Cracked version to bypass login issues. Use Google and you will find the software easily.
Let know if the above steps helped you, and reach out if you still get stuck anywhere.
Cheers,
Manu
mAnN14 said:
Don't click on the "Edit phone information" as many guides recommend.
Follow these steps instead:
Download your STOCK ROM and extract it in a new folder
Download OSA Tool (crack version) >> Install it on your system >> Paste the crack files in the default installation folder
Stay connected with your internet >> Run the tool and click on OK >> You will arrive at the first screen of the OSA Tool
Switch off your device >> Use "Power + Volume Down" key combination to boot into the "Fast boot mode."
Click on NEXT >> Locate your extracted STOCK ROM FILE >>> Add it to the tool and from the drop-down, select Emergency mode/ Normal mode depending on your situation.
Note: Emergency mode is useful if your device is dead and nothing works. It will erase your personal data completely.
The other mode i.e., "Normal mode" is useful if your device works fine, and you want to simply flash the STOCK ROM without erasing your personal data.
Once the mode is chosen, click NEXT >> Let the process begin
You will get a success message once the process gets finished
Close the OSA Tool and disconnect your device
In most cases, your device will auto-reboot >> If not, reboot it manually
Once booted up, you shall have your STOCK ROM installed successfully
Note:
I downloaded my STOCK ROM from this link - STOCK ROM for Nokia 6.1 (2018)
I used OSA Tool v6.2.8 Cracked version to bypass login issues. Use Google and you will find the software easily.
Let know if the above steps helped you, and reach out if you still get stuck anywhere.
Cheers,
Manu
Click to expand...
Click to collapse
Thanks for that. Will give it a try this evening and report back.
mossywell said:
Thanks for that. Will give it a try this evening and report back.
Click to expand...
Click to collapse
Happy to help.
Sure, will await your response.
mossywell said:
Thanks for that. Will give it a try this evening and report back.
Click to expand...
Click to collapse
OK, so following this to the letter:
Once the mode is chosen, click NEXT >> Let the process begin
At this point it says "The update process failed. Error: emergency download failed. Error = Device_Not_Configure (0x4000).
Oddly, if I type "fastboot devices" it does show me the device, so I know it's connected and visible to the laptop.
Weird!
mossywell said:
OK, so following this to the letter:
Once the mode is chosen, click NEXT >> Let the process begin
At this point it says "The update process failed. Error: emergency download failed. Error = Device_Not_Configure (0x4000).
Oddly, if I type "fastboot devices" it does show me the device, so I know it's connected and visible to the laptop.
Weird!
Click to expand...
Click to collapse
If, instead of emergency mode, I use normal mode, it does what it did before: just hangs at "Checking device status...."
Time to put it in the bin?
mossywell said:
If, instead of emergency mode, I use normal mode, it does what it did before: just hangs at "Checking device status...."
Time to put it in the bin?
Click to expand...
Click to collapse
also tried flashing twrp (again) using fastboot flash recovery twrp.img and it just said something like the recovery partition was not found. As I say, the phone boot both normally and into fastboot - just neither without a screen.
I appreciate your time trying to help me, but time to draw a line under it and chuck it in the bin. (There's a phrase here in the UK and maybe other places too: you can't polish a turd !)
mossywell said:
Thanks for the reply - I've hit a roadblock: the link to the ROM is only for the img files, not the nb0 files. (The author says "It is already advised that the Nokia Service Tool only supports firmware files in the .nb0 or the .mlf format. You can download them from the below-mentioned links" and then failed to link to them! Any ideas where the stock nb0 files are? I searched this forum and couldn't find them.
EDIT: Think I might have found one Googling...
EDIT2: I found PL2-354E-0-00WW-B01.nb0
When I run the OST tool and click the "Edit Phone Information", I get "Boot FTM Mode Fail!". If I OK that (I read that this error is OK to ignore) and carry on, if just hangs at "Checking device status...".
Click to expand...
Click to collapse
Try nokia NFT tool intead,...it works