This thread is for those who have troubles but have no idea what to try. If you're new in playing with Android Roms, you'd better read this. No exact operation would be introduced here, because only directions are provided and further work should be searched by yourself as I'm not Mr. Knowall.
Here, trouble means problems except the cases you can boot to system (they're issues) or hardware damage. Make sure your phone has been charged or any battery related problem is considered to hardware side.
Besides, if you are holding a T-Mobile H932, you should be extremely careful with anything below, because any mistake may push your phone into hell. Especially, there is currently no usable 9008 firehose file for it even you ask a professional repairman.
First, backup everything important regularly to a secure place instead of phone storage, especially private files and EFS partition which contains IMEI, MEID, etc. If possible, write down the IMEI, MEID, S/N, WiFi MAC address, Bluetooth MAC address of your phone for potential future need of restoration.
Then I assume you have unlocked bootloader. If not, go to (WTF...!) LG V30/V30+/V30S Bootloader Unlock & Root Method (With Clear Instructions) when you can still boot to system. If you cannot boot to system already with bootloader locked and cannot perform unlocking introduced there, maybe you can jump to the section of download mode or 9008 mode and give it a trial, BUT I CANNOT ensure your phone would return normal.
There are four important modes related to our topic: Recovery, Fastboot, Download and Qualcomm 9008 (Preload for MTK). Risky and inconvenience is increasing in order. Read this: Collection of mode entries with hardware key combination (maybe for most LG models) to learn how to enter them without booting to system.
Recovery is stored in the partition with the same name. You need custom builds like TWRP or OrangeFOX to flash in, or you only have a stock one with the single function of master reset. For most cases, if you can enter all the four modes, use this first. Make a backup before flashing anything with Rec, and if the thing you flashed in leads to bootloop or anything abnormal, you can easily get the original partitions back. But if you performed incorrect operations and such a restoration doesn't work, you should consider wipe cache, dalvik cache and data (backup if not yet). If not work still, try to flash in fresh rom packages. If not work again, go to the section of download mode.
Fastboot is mainly used to flash in some partitions like recovery, boot and unlock. There is some limitations that many partitions cannot be flashed in here. If you have never used this mode before, you may need to manually update the corresponding driver on your computer (caution that if you're facing the problem of "waiting for device", it's usually driver issue). Some firmwares miss this function, so it's often recommended to switch firmware for custom rec installing.
Download mode is mostly used to deal with kdz files. You need LG phone driver and dev patched LGUP (or some other tools with similar functions). If LGUP cannot recognize a phone already in download mode, it's usually the problem of driver or LGUP patcher. Be careful when using LGUP. If any interrupt during the process of downloading firmware, you need go to 9008 mode. Do not use chiperase unless you know what to do after that. Here again dump can backup partitions. Refurbish and partition dl are most widely used. This mode can solve most troubles unless you cannot enter here. If that really happens, move on to the ultimate mode, 9008.
9008 is the last chance before sending your phone to repair. Only recommend to recover other modes, but if you're familiar with it, you can do almost everything in this mode as in other modes. Again driver and tool are needed. Recommend QPST since it's made by Qualcomm, but it's not released publicly. Search and download from some reliable sources. The driver needed should be contained in the package with the tool. Somebody may tell to use QFIL, but if you have not installed it please install QPST and use the built-in QFIL instead of a standalone one, or problems would probably find you. To use this mode, you need the corresponding firehose file. See this: LG V30 Unbrick guide (Qualcomm EDL 9008 Mode, Hardbirck, with no download mode) for file download (none for H932 yet). You do not need XML file if the partition table is not broken. To verify it, open QFIL built in QPST, set configuration to UFS mode, open Tools -> Partition Manage and see if it's correctly displayed. If yes, only flash in partitions related to bootloader and recovery to get other modes back. The partitions can be found in twrp flashable stock firmware or early backups, or you can extract from kdz using LG firmware extractor. Only the worst damage to storage needs full download with XML generated from kdz using extracting tools.
If all modes above cannot save your phone, you may consider hardware damage and that needs professional knowledge, so our forum cannot help.
Good luck.
Related
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.
Hello XDA Forum
I have a little problem with my Red Magic 5G
I accidentally deleted the parameter files and also other important files out of stupidity and wanted to ask whether someone has a red magic 5g and can make a backup via twrp and send it to me? < I really don't know what to do anymore >
I have flashed new software with edl on it and installed all 3 rom versions but I still have the same problem non of them worked i can't even install custom rom anymore.
Best Regards
Akizuma
Has really no one a backup for me left for the red magic 5g ?
Hello, what parameters are missing in your red magic5g, can I help you? I use red magic5s
(I think everthing)
I need a twrp backup from a red magic 5g where everthing still works i destroyed to much,
Not even touch working anymore in twrp.
Edit ( I think not that 5s works on 5g or ? )
you don't need anything from someone else's device.
if you ****ed something up. then you need to use the unbrick tools. and set them up correctly and follow the directions to unbrick.
they will erase all your data. but form what I've read, you lost all that already.
there are unbrick tools for both devices. 5S or 5G on either forum for those devices make sure you're using the correct unbrick tool. 5g does not work correctly with 5S devices, and vice versa.
the unbrick tools will format and restore every single parition on the phone. restoring it to factory settings.
its very possible though if you were messing with partitions that you erased your IMEI.
if thats gone, its beyond the scope of the unbrick tools. you'll have to contact warranty services.
the unnofficial unbrick tools by Johnny in my opinion better.
just make sure your drivers are correctly installed, and up to date. .. this includes windows updates.
(recently there has been a google ADB driver that needs updating thats available through winodws update)
so make sure thats installed too.
set your phone to EDL mode and follow the direction on Johnny's thread.
it will restore your phone as long as you can get to Fastboot mode. (vol down and power)
PM me if you need more help. but that should be enough to get your back to stock.
Problem Fixed ! #closed
@Akizuma it would be kind to post what you did to fix the issue, so others in the future who are faced with the same issue can use your solution.
We are a community here to help others.
If we mention that our problems are sorted, without posting how, it only helps the direct user and other searching for solutions to fix their issues will continue.
Please post what it was you did to fix your issue. It would be very appreciated.
If you're having any of these issues, this option may be able to fix it.
Problem: black screen after boot up, touch not working (TWRP) or automatic booting in EDL mode
First download the Unbrick EDL Tool
(I chose EU)
Download here:
[Tool] Nubia Red Magic 5G Unbirck Tool
So.......It's finally here, the unbrick tool for RedMagic 5G. This tool can help you to unbrick the phone. It will restore the phone to the oldest version, you need to update the system software by yourself. This tool is based on Qualcomm...
forum.xda-developers.com
Then follow the instructions in the folder and install an operating system on it through edl mode
Then you start the installation again but this time you don't run it because I noticed that the tool doesn't flash important image files but skips them (you can even find it in the log)
First go to \ AppData \ Local \ Temp \ is-K4OSH.tmp \ NubiaEmergencyDownload \ software
(name can be different)
And copy
persist.img
boot.img
odm.img
recovery.img
system.img
vendor.img
And put it in a new folder
After that go to the bootloader again and unlock the oem via
(fastboot oem nubia_unlock NUBIA_NX659J)
Then execute following commands for the files like
(Command (Fastboot flash persist [file.img])
(Command (Fastboot flash boot [file.img])
(Command (Fastboot flash odm [file.img])
(Command (Fastboot flash recovery [file.img])
(Command (Fastboot flash system [file.img])
(Command (Fastboot flash vendor [file.img])
It can be that most of them give out an error, execute them anyway in case the folder still exists
Then the cell phone should start again normally.
P.s ( Sorry for my poor english ^^ )
System, Vendor, and odm, are all partitions flashed during the "super" partition.
this is why you didn't see them exactly written in the log they all go under "super" and get assigned a dynamic partition when flashed.
you cna see here how they changed the partitions and how they're written now.
Implementing Dynamic Partitions | Android Open Source Project
either way. thank you for your effort to your solution.
I tried using the XDA Discord server to get a quick response, but apparently, some people just ignore me or don't even know how to help me. So I will try here...
I was following that tutorial so that I can use Joycon Droid on my phone. I installed TWRP Recovery and gone in his recovery mode. I wiped what the tutorial asked to wipe and began the flash process. Unfortunately, I mistakenly downloaded the flash files on the computer. I tried removing my SD Card and putting inside it the files I need, but TWRP was not able to read any data for the SD Card. So I tried to find a way to cancel the recovery menu, and I did by clicking Reboot System. Since then, my phone was locked in the logo screen. After many attempts, I've gone from the charging screen and finished by the "An error occurred while updating the device software.". I can enter the download mode, but nothing else. My phone is an A520W and I think the root was not properly installed. I researched everywhere without any solution, so I came to this discord server, hoping someone would save my phone. I tried flashing the official A520W OS, but Odin always does a FAIL message or freezes. I later tried to use another firmware file, reinstalled the Samsung USB driver and Odin, and know it says on the Download Mode screen:
SV REV. CHECK FAIL(BOOTLOADER) DEVICE: 9, BINARY 7. (it failed)
Can someone help me? I really need help!
Your phone partition table is crushed probably!
Use emmc programmer to repairing your partitions! (ask from someone expert)
Also, "easy-jtag" may be useful(search this)
matkali said:
Your phone partition table is crushed probably!
Use emmc programmer to repairing your partitions! (ask from someone expert)
Also, "easy-jtag" may be useful(search this)
Click to expand...
Click to collapse
Kay I'll try the easy-jtag, but if it doesn't work, who is an expert at emmc programming stuff?
Is there a way to fix the crushed partition table without buying stuff?
Ok so, I used a certain program that added galaxy s6 data and now it is stuck in bootloop
Akurio64 said:
Ok so, I used a certain program that added galaxy s6 data and now it is stuck in bootloop
Click to expand...
Click to collapse
better than the error screen right? the program name is fonepaw
Akurio64 said:
Ok so, I used a certain program that added galaxy s6 data and now it is stuck in bootloop
Click to expand...
Click to collapse
It is dangerous for your phone, because every phone have different partition table and different architecture!
Pit file in a520w stock firmware have partition table structures information. (use PIT_Magic.exe to see)
In old architecture of Samsung(e.g. s3) when partition table cleaned from emmc (phone internal storage), they use micro sdcard to boot from it! (to identity correct info for Odin) (same boot from USB when you are installing windows.) then by going to download mode they flash stock Rom!
But I suggest to you find one knows enough information and requirements stuffs.
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.
Hello everyone, I'm new on the forum. Sorry to bother you, I've been reading most of the threads about the G8 thinq. My problem is that I can't extract LG's kdz firmware properly. I already tried with the Lg extract, with the CMD, with Power Shill. None manage to extract the '.DZ' Please share me a rom that is already extracted, thanks in advance.
CloudStrife97 said:
Hello everyone, I'm new on the forum. Sorry to bother you, I've been reading most of the threads about the G8 thinq. My problem is that I can't extract LG's kdz firmware properly. I already tried with the Lg extract, with the CMD, with Power Shill. None manage to extract the '.DZ' Please share me a rom that is already extracted, thanks in advance.
Click to expand...
Click to collapse
So a couple of things, the kdz extractor tools are plentiful, some work under windows and some under linux. I've used the linux version and it does work, no issues. The DZ file is basically the KDZ uncompressed. It's a large single file.
The DZ is then further broken down by the utility into various forms due to the command you use, you can get partition images and chunks of images etc etc.
2nd, you ask for a 'rom that is already extracted'? That's a lot of images, about 5 gig worth, what **exactly** are you trying to do? Maybe you only need a few files? Maybe you need files from a specific rom version? Maybe you need a kdz rom that doesn't even exist? Like at&t and sprint?
you might want to fill in some details for anyone to help.
AsItLies said:
So a couple of things, the kdz extractor tools are plentiful, some work under windows and some under linux. I've used the linux version and it does work, no issues. The DZ file is basically the KDZ uncompressed. It's a large single file.
The DZ is then further broken down by the utility into various forms due to the command you use, you can get partition images and chunks of images etc etc.
2nd, you ask for a 'rom that is already extracted'? That's a lot of images, about 5 gig worth, what **exactly** are you trying to do? Maybe you only need a few files? Maybe you need files from a specific rom version? Maybe you need a kdz rom that doesn't even exist? Like at&t and sprint?
you might want to fill in some details for anyone to help.
Click to expand...
Click to collapse
Hello, thanks for answering. I will begin to tell my story. I have an Lg G8 ThinQ Sprint with Android 10. It is network unlocked because I can use it here in Honduras. I did the Crossflash tutorial ( https://forum.xda-developers.com/t/tutorial-crossflash-bypass-opid-mismatched-error.4345963/ )
While using the QFIL I deleted flash from one of the 7 partitions the tutorial says. My phone no longer exits EDL mode ( Qualcomm HS-USB QDloader 9008 (COM5)) So I went to this tutorial: (https://forum.xda-developers.com/t/lg-g8-stuck-in-qualcomm-hs-usm-qdloader-9008.4050197/).
I followed the steps to load the ¨Lun¨, I did it in PowerShell, because in CMD it didn't work for me. Apparently the ¨Lun¨ were installed well. Now the problem is that I can't install the necessary partitions, because I can't unzip the .DZ ROM
Help, what do I do? My cell phone is only in Qualcomm HS-USB QDloader 9008 mode, it does not go to download mode
CloudStrife97 said:
Hello, thanks for answering. I will begin to tell my story. I have an Lg G8 ThinQ Sprint with Android 10. It is network unlocked because I can use it here in Honduras. I did the Crossflash tutorial ( https://forum.xda-developers.com/t/tutorial-crossflash-bypass-opid-mismatched-error.4345963/ )
While using the QFIL I deleted flash from one of the 7 partitions the tutorial says. My phone no longer exits EDL mode ( Qualcomm HS-USB QDloader 9008 (COM5)) So I went to this tutorial: (https://forum.xda-developers.com/t/lg-g8-stuck-in-qualcomm-hs-usm-qdloader-9008.4050197/).
I followed the steps to load the ¨Lun¨, I did it in PowerShell, because in CMD it didn't work for me. Apparently the ¨Lun¨ were installed well. Now the problem is that I can't install the necessary partitions, because I can't unzip the .DZ ROM
Help, what do I do? My cell phone is only in Qualcomm HS-USB QDloader 9008 mode, it does not go to download mode
Click to expand...
Click to collapse
So honestly I'm confused by where you are or what the situation is. But no matter.
This link is for the Lun4 partitions of sprint a10 backup. It has the rawprogram xml needed to flash it.
My understanding is that should be all you need to get LGUP to work. So flash that with qfil and then go directly to LGUP with the key combo.
Then, in lgup, do whatever you want, crossflash etc. Once you reinstall a kdz with lgup you should be back to the beginning and can start again.
good luck
AsItLies said:
So honestly I'm confused by where you are or what the situation is. But no matter.
This link is for the Lun4 partitions of sprint a10 backup. It has the rawprogram xml needed to flash it.
My understanding is that should be all you need to get LGUP to work. So flash that with qfil and then go directly to LGUP with the key combo.
Then, in lgup, do whatever you want, crossflash etc. Once you reinstall a kdz with lgup you should be back to the beginning and can start again.
good luck
Click to expand...
Click to collapse
Thanks for the files and information. I just did the flash in QFIL. look what it tells me.
What could be wrong with my cell phone? It no longer wants to enter power on or enter download mode.
The screenshots from 1 to 5 are those of the QFIL flash process.
Then see how is the partition manager. From screenshot 6 to 13.
Do you find any problem?
I still can access Download mode.
Thank you again for your dedication and availability to help me
Hmmm, wasn't sure if that would work or not. That rawprogram xml was created with bkerler edl utilities, I know it can be used to restore with those utilities but thought it would work with qfil, guess not.
seems your only other option would be to flash ea partition manually with qfil.
AsItLies said:
Hmmm, wasn't sure if that would work or not. That rawprogram xml was created with bkerler edl utilities, I know it can be used to restore with those utilities but thought it would work with qfil, guess not.
seems your only other option would be to flash ea partition manually with qfil.
Click to expand...
Click to collapse
ok i'll try it that way.
how can i use bkerler edl utilities to load the rawprogram xml ?
Hi, I also tried this tutorial:https://forum.xda-developers.com/t/tutorial-rescue-from-hard-brick.4351389/.
According to him, since my device is Sprint, I have to flash all partitions. You can successfully do part C. But I haven't been able to do part E yet because I don't have all those partitions.
AsItLiesshare me the full firmware backup so I can restore mine, please
CloudStrife97 said:
AsItLiesshare me the full firmware backup so I can restore mine, please
Click to expand...
Click to collapse
I don't have the full backup, sorry. Pretty sure if you look though someone has posted a link to it.
Keep in mind though, if you have chip erased your device, restoring a backup will not restore your imei, for that it will cost $ to pay someone with an octoplus box to do it.
AsItLies said:
So honestly I'm confused by where you are or what the situation is. But no matter.
This link is for the Lun4 partitions of sprint a10 backup. It has the rawprogram xml needed to flash it.
My understanding is that should be all you need to get LGUP to work. So flash that with qfil and then go directly to LGUP with the key combo.
Then, in lgup, do whatever you want, crossflash etc. Once you reinstall a kdz with lgup you should be back to the beginning and can start again.
good luck
Click to expand...
Click to collapse
Do you have an AT&T one?
PHANX0M said:
Do you have an AT&T one?
Click to expand...
Click to collapse
no
My device stuck in edl mode it's nothing show no download mode no restart no turn off only edl mode please help