Develop Bugs

Glitching and boot looping on splash screen

I am suddenly faced with glitching on splash screen, while the SAMSUNG GALAXY TAB displays when you switch on, it dims a bit, glitches ( shows lines on the screen ) and reboots continuously. I have reflashed stock firmware, cleared cache and wiped everything with no results. On TWRP recovery, the device works with no problem. I am currently charging it to 100% since I've heard it can be battery related.
Any help would be appreciated.
Regards to all.

in recovery, connect USB cable and do from PC:
adb shell cat /proc/last_kmsg > last_kmsg.txt
Click to expand...
Click to collapse
and send it here via attachment

gellmar said:
in recovery, connect USB cable and do from PC:
and send it here via attachment
Click to expand...
Click to collapse
Sorry to sound stupid, but can it be done from stock recovery or do I have to flash TWRP ? Also, is it run from CMD from Windows 10 ?

Ok got the file....how do I attach it? I've been a member here for years and never been able to attach files

@gellmar
Is this any good ?
https://drive.google.com/open?id=1nbL8TjLwm9fPPkG3a1yXSNbGzhteFZak

drowsy1982 said:
@gellmar
Is this any good ?
https://drive.google.com/open?id=1nbL8TjLwm9fPPkG3a1yXSNbGzhteFZak
Click to expand...
Click to collapse
Your EFS filesystem is corrupted, causing a reboot. You must try nandroid backuping it as is and extract all the data you can from it.

gellmar said:
Your EFS filesystem is corrupted, causing a reboot. You must try nandroid backuping it as is and extract all the data you can from it.
Click to expand...
Click to collapse
I can do Nandroid Back up from TWRP, but what's the next step ?

Found this EFS-Fix-regalstreak.tar.md5, to flash with Odin for currupted EFS.
Would it help ?

drowsy1982 said:
Found this EFS-Fix-regalstreak.tar.md5, to flash with Odin for currupted EFS.
Would it help ?
Click to expand...
Click to collapse
Probably not, but send me your EFS backup in PM - I can try restoring tge useful info from it and send you back the tar file and instructions.

gellmar said:
Probably not, but send me your EFS backup in PM - I can try restoring tge useful info from it and send you back the tar file and instructions.
Click to expand...
Click to collapse
As you said, the files mentioned didn't fix the problem. I managed to solve this however. I was flashing a single file stock firmware containing only the AP file. I tried another firmware containing AP, BL and CSC files with ODIN and booted without problems. Does the BL and CSC have anything to do with the corrupted EFS ?

drowsy1982 said:
As you said, the files mentioned didn't fix the problem. I managed to solve this however. I was flashing a single file stock firmware containing only the AP file. I tried another firmware containing AP, BL and CSC files with ODIN and booted without problems. Does the BL and CSC have anything to do with the corrupted EFS ?
Click to expand...
Click to collapse
BL is BootLoader aka S-BOOT. Usually, if this one becomes corrupted, your only option is to replace the NAND flash and flash the correct BL with JIG. Luckily this is not the case.
CSC is the carrier related info. Since you have T800, flashing this may have fixed the problem. Now chevk your device serial number in About Phone settings.

gellmar said:
BL is BootLoader aka S-BOOT. Usually, if this one becomes corrupted, your only option is to replace the NAND flash and flash the correct BL with JIG. Luckily this is not the case.
CSC is the carrier related info. Since you have T800, flashing this may have fixed the problem. Now chevk your device serial number in About Phone settings.
Click to expand...
Click to collapse
Still not botting fully.
In recovery now i'm getting failed to mount /efs (invalid argument)
The firmware I flashed was missing the CP file.

drowsy1982 said:
Still not botting fully.
In recovery now i'm getting failed to mount /efs (invalid argument)
The firmware I flashed was missing the CP file.
Click to expand...
Click to collapse
This is a dying NAND flash. Given that TWRP dumps efs as raw image, this is not a just filesystem issue.
I told you what to do in PM.

FIXED !
Followed the below guide, creates a generic EFS folder and then install an stock firmware.....ta daaaaaaaaa !!
http://zidroid.com/how-to-fix-failed-to-mount-efs-for-galaxy-s3-gt-i9300/

[Guide] US988 Oreo to H933 Pie Stock ROM Keeping Root

So I had a bit of a hiccup trying to go from US998 to H933. The plan was to go from US998 Oreo to H933 Oreo and then update to Pie with the TWRP zip. But I never made it that far. Many things happened before getting back to US998 Oreo, which was my original starting point, but they should be irrelevant.
General disclaimers apply. Do this at your own risk. I've only done this one time on my phone with help and advice from @cloud1250000. This hasn't been "tested" further then that and this guide was written after the fact.
Please read the entire guide first then go back and follow step by step.
Prerequisites:
adb installed - Follow 3rep, steps 1, 2 and 3. here to install.
LG drivers installed
LGUP dev patched installed - located here - Courtesy of @tecknight.
See "HOW TO INSTALL DEV PATCHED LGUP" to install
Needed Files:
Stable TWRP 3.2.3.7
Original Pie recovery aka "original-recovery-pie.img" - Courtesy of @cloud1250000
Original Pie laf aka "laf-pie.img" - Courtesy of @cloud1250000
H933 Pie kdz - H93330k_00_OPEN_CA_OP_0906.KDZ
You'll also need:
AnyKernel 3 RCTD Remover - Courtesy of @JohnFawkes
Disable_Dm-Verity_ForceEncrypt_08.18.2019 (encryption disabler) - Courtesy of @Zackptg5
Magisk - latest here or v19.3 direct link
Rename TWRP-3.2.3-7-default.img to TWRP.img
Place the following on the root of your microsd card (though you could put it on your internal sd, you would just have to adjust the paths)
TWRP.img
original-recovery-pie.img
laf-pie.img
You can put these anywhere you like on your sdcard
AK3_RCTD_Remover.zip
Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip
Magisk-v19.3.zip
0) WARNING - You will be formating the internal data partition. Backup/move files from the internal storage or you will lose them!
1) Start with a H933 phone that has been converted to US998 on an Oreo rom, with bootloader unlocked. I was on this kdz specifically: US99820a_04_0330.kdz
2)Boot into download (vol + and plug in cable) mode/connect phone to the computer. Then open up the dev patched LGUP.
3) Select this kdz H93330k_00_OPEN_CA_OP_0906.KDZ.
4)Flash with partition DL, select all EXCEPT recovery.
5)It should reboot into recovery/TWRP
6.a) WARNING, Following procedure might be risky. Please read up on flashing laf and see if it's ok with you. I don't really know how risky it is, but I figured I would put in this warning.
6.b) Open a command window on your computer and run the following commands with adb. This puts TWRP into the laf partition and the stock recovery back into the recovery partition. Meaning we won't have TWRP in recovery but we will have a backup of it in laf, which we'll need. *inspired by @runningnak3d from the H932 root*
Code:
shell adb
cd external_sd
dd if=TWRP.img of=/dev/block/bootdevice/by-name/laf
dd if=original-recovery-pie.img of=/dev/block/bootdevice/by-name/recovery
7)Power off phone, turn it on. Let it do its thing for a bit, there will be a reboot and it will stay on LG logo for awhile. It should eventually boot to a setup screen. Great Pie is installed, now we need to install a few things in TWRP. Turn off the phone.
8)Boot into download mode (vol + and plug in cable) it will boot into TWRP (this is expected)
9.a) Follow from step 7 from this post. There is some of step 6 that should be followed also.
If you followed all of that you should have installed Magisk, Disable_Dm-Verity_ForceEncrypt_08.18.2019, and AnyKernel 3 RCTD Remover and performed a factory reset and did a format of data.
9.b) The final step of the above should have had you boot into android, once you've done that you can turn off your phone
10) Boot into download mode (vol + and plug in cable) it will boot into TWRP (this is expected)
11) Flash TWRP back to recovery by running the following command
Code:
shell adb
cd external_sd
dd if=TWRP.img of=/dev/block/bootdevice/by-name/recovery
11.b)If you would like to restore laf (so you can use LGUP) then also run this to restore LG's download mode. *It can be desirable to leave in the laf partition also. By leaving it there if for some reason you lose TWRP in recovery then you can boot into download mode and you'll have TWRP there. This is a personal decision.*
Code:
dd if=laf-pie.img of=/dev/block/bootdevice/by-name/laf
You're done, you now should have a H933 phone on H933 Pie with root.
If your mobile data doesn't work or you're not getting LTE, check your apn setting and play around on your phone to see if it will pick it up. Check that mobile data is on etc. Remove sim, turn off phone, insert sim then turn on phone etc. If none of that works then:
Reboot to TWRP/recovery (you can do so in Magisk, modules, 3 dots, reboot recovery) and run:
Code:
adb shell
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2
Reboot and you should have data/LTE back
Big credit to @cloud1250000 who walked me through all of this, I was just a pawn. I can't thank Cloud1250000 enough!
Info and files taken from these posts:
https://forum.xda-developers.com/showpost.php?p=80363769&postcount=21
https://forum.xda-developers.com/showpost.php?p=80432411&postcount=135
Thanks to @cloud1250000 for the original-recovery-pie.img and laf-pie.img
Thanks to @ChazzMatt for all his help on the forums and I've linked to a lot of his stuff
Thanks to @runningnak3d for the inspiration for step 6b from his work on the H932 root. Please go here and click the THANK BUTTON!
Thanks to @tecknight for the DEV PATCHED LGUP! Please go here and click the THANK BUTTON!
Thanks to @Zackptg5 for the Disable_Dm-Verity_ForceEncrypt_08.18.2019 (encryption disabler)
I don't normally write guides but I had went through this and thought others would benefit from knowing the process. Please let me know if it needs some improvements.

nice guide!!
@ChazzMatt is it possible to move this guide to the guide section?

cloud1250000 said:
nice guide!!
@ChazzMatt is it possible to move this guide to the guide section?
Click to expand...
Click to collapse
Yeah, I'll ask mod to move it. I'll also reference it in the H933 Pie post #1.

Btw, this is mostly how I did it myself. so there's atleast 2 persons who followed this guide successfully..

I successfully updated to H93330k while retaining root/TWRP by mostly following these steps too. However, I skipped flashing TWRP to laf partition as it felt risky to me. I instead flashed Magisk zip to get root before flashing back stock recovery to get into OS. Once booted into Pie, I installed Magisk Manager, enabled ADB, then re-flashed TWRP using ADB with the command "dd if=TWRP.img of=/dev/block/bootdevice/by-name/recovery".

traybourne said:
I successfully updated to H93330k while retaining root/TWRP by mostly following these steps too. However, I skipped flashing TWRP to laf partition as it felt risky to me. I instead flashed Magisk zip to get root before flashing back stock recovery to get into OS. Once booted into Pie, I installed Magisk Manager, enabled ADB, then re-flashed TWRP using ADB with the command "dd if=TWRP.img of=/dev/block/bootdevice/by-name/recovery".
Click to expand...
Click to collapse
So you basically just followed this guide:
https://forum.xda-developers.com/showthread.php?p=78183349
I has started using that guide myself but I couldn't format my data partition in step 3. TWRP said it couldn't mount /data and reported it as 0KB.
While trying to fix that something got messed up and I had to try and get back to a working state. I finally got back to US998 Oreo and then did it this way.
If I understand correctly though, when I did the steps above, it's the same the as steps in this guide at the beginning. (Partition DL without recovery).Except in this guide you format data/factory reset before booting up. In my guide here you do it after.
I guess it's probably a good idea to suggest to people to try that guide/method first as it could be considered safer.
If users follow the guide linked in this post and they can format data in step 4 then they can continue with that guide. If formatting data doesn't work then they can jump to this guide and start at step 6.
Though I would also suggest if you can't format data to try and reboot back into recovery and try it again as even when I did this guide I think it might have had an error formatting data also but rebooting back into recovery allowed me to format data.
But I find LGUP kind of dangerous. It's not actually I'm sure but if used incorrectly it can go poorly. Thought that's true with anything.
I've actually left TWRP in laf as I don't see much negative. If I somehow loose custom recovery, I have a backup and if I need to use LGUP then I can always flash the original laf back while in TWRP from the laf partition. runningnak3d said flashing laf was fine and actually highlyrecommend it so that helps the decision (note that the suggestion was for people with a H932). He explains why its a good idea in the H932 thread.

bnevets27 said:
So you basically just followed this guide:
https://forum.xda-developers.com/showthread.php?p=78183349
I has started using that guide myself but I couldn't format my data partition in step 3. TWRP said it couldn't mount /data and reported it as 0KB.
While trying to fix that something got messed up and I had to try and get back to a working state. I finally got back to US998 Oreo and then did it this way.
If I understand correctly though, when I did the steps above, it's the same the as steps in this guide at the beginning. (Partition DL without recovery).Except in this guide you format data/factory reset before booting up. In my guide here you do it after.
I guess it's probably a good idea to suggest to people to try that guide/method first as it could be considered safer.
If users follow the guide linked in this post and they can format data in step 4 then they can continue with that guide. If formatting data doesn't work then they can jump to this guide and start at step 6.
Though I would also suggest if you can't format data to try and reboot back into recovery and try it again as even when I did this guide I think it might have had an error formatting data also but rebooting back into recovery allowed me to format data.
But I find LGUP kind of dangerous. It's not actually I'm sure but if used incorrectly it can go poorly. Thought that's true with anything.
I've actually left TWRP in laf as I don't see much negative. If I somehow loose custom recovery, I have a backup and if I need to use LGUP then I can always flash the original laf back while in TWRP from the laf partition. runningnak3d said flashing laf was fine and actually highlyrecommend it so that helps the decision (note that the suggestion was for people with a H932). He explains why its a good idea in the H932 thread.
Click to expand...
Click to collapse
Sort of, Step 8 of that guide did not work for me as I could not get into DL mode at that point, so I had to go back and dump the stock recovery, then flash it from within TWRP to get past that part. That guide also doesn't include the step to wipe modemst1 and modemst2 from TWRP, which was required for me to get data back.
I don't recall having issues with formatting data though, but honestly I was trying so many things I don't exactly recall what worked and what didn't. The whole process was a real pain lol.

cloud1250000 said:
Btw, this is mostly how I did it myself. so there's atleast 2 persons who followed this guide successfully..
Click to expand...
Click to collapse
Make that 3.
Tried LOS 17 and needed this to get back to somewhat normal state.
Kinda did it backwards as I wanted to retain on H93330k though.
Thanks!

You can't use lgup to replace the recovery with the original one because download mode won't work until you master reset.. and master reset is done by the original recovery lool.. so the original guide won't work because of that. (If you switch from us998 to another model)
Twrp in laf is good and I'm glad I reviewed the h932 root thread for that reason lol BUT you do lose download mode and lgup.. but you can easily revert it back with twrp with the laf I provided..
Anyway, it's very straightforward to do the switch.
Also do not go down to nougat for master reset.. since it remove twrp from laf (surprisingly they removed that in the pie master reset.. also pie does it master reset by itself.. it's just the best.)

christopherrrg said:
Make that 3.
Tried LOS 17 and needed this to get back to somewhat normal state.
Kinda did it backwards as I wanted to retain on H93330k though.
Thanks!
Click to expand...
Click to collapse
Make sure if you want to try customs roms to go with the h930 version (if available.. )

finally managed to.. convert an ls998+ to h933... sadly I lost my imei in the process lol
the only thing I had left was the meid on the back of the device... I think I figured how to get the imei from that (and it seems to be matching the right device :s) ... and I finally managed to restore it on the device..... following a bunch of different guide...
Sadly, the device lost its S/N number... not sure if it's important.. I think h933 phone doesn't have one.... atleast my original h933 doesnt...
Honestly big rookie mistake.. but now I got a fully working h933+ (volte )

cloud1250000 said:
finally managed to.. convert an ls998+ to h933... sadly I lost my imei in the process lol
the only thing I had left was the meid on the back of the device... I think I figured how to get the imei from that (and it seems to be matching the right device :s) ... and I finally managed to restore it on the device..... following a bunch of different guide...
Sadly, the device lost its S/N number... not sure if it's important.. I think h933 phone doesn't have one.... atleast my original h933 doesnt...
Honestly big rookie mistake.. but now I got a fully working h933+ (volte )
Click to expand...
Click to collapse
Did you brick your initial H933 or have you always been on ls998?

I`ve got 2
One h933 from bell and the other one is the ls998+ I got from ebay for 140usd...
when converting the ls998 to an h933... the lte would never work... tried deleting the modemst partition.. it would just kill data completely... so what I did was to take the working modemst1 and modemst2 from my h933 and flashed it on the ls998... it worked till a reboot... then data gone again... I've read somewhere that the fsg partition is the backup for modemst1.. so what I did is... flash on the ls998 the fsg, modemst1, modemst2 and op partition of my working h933...
very not a good idea.. turns out.. fsg, modemst1 and modemst2 is the EFS (where the imei is stored) :s so I basically lost my ls998 imei.. surprisingly tho.. lte was working fine and I could make calls lol... but the system didnt report the imei of my h933 phone.. it was just not displaying anything.. which is odd.. anyway.. after a couple of hour.. I found a way to restore the imei back

cloud1250000 said:
I`ve got 2
One h933 from bell and the other one is the ls998+ I got from ebay for 140usd...
when converting the ls998 to an h933... the lte would never work... tried deleting the modemst partition.. it would just kill data completely... so what I did was to take the working modemst1 and modemst2 from my h933 and flashed it on the ls998... it worked till a reboot... then data gone again... I've read somewhere that the fsg partition is the backup for modemst1.. so what I did is... flash on the ls998 the fsg, modemst1, modemst2 and op partition of my working h933...
very not a good idea.. turns out.. fsg, modemst1 and modemst2 is the EFS (where the imei is stored) :s so I basically lost my ls998 imei.. surprisingly tho.. lte was working fine and I could make calls lol... but the system didnt report the imei of my h933 phone.. it was just not displaying anything.. which is odd.. anyway.. after a couple of hour.. I found a way to restore the imei back
Click to expand...
Click to collapse
That's awesome! Great ending!

I have converted H933 to US998 Pie with bootloader unlocked and TWRP. Now my goal is to go back to H933 Pie, and keep the bootloader unlocked and TWRP. I have followed the post #1 in this site and post #2 in https://forum.xda-developers.com/lg...a-20g-twrp-t3868186/post78183349#post78183349, but phone doesn't boot to TWRP after Step #2 (Partition DL Canadian KDZ 30k). I tried several times and still couldn't succeed. I must miss some steps.
Can anybody please help provide what methods or link I should follow? Thanks in advance.

If it doesn't boot into TWRP, then what does it boot into?
Are you sure you're NOT flashing recovery?
BTW you might also find help in this telegram group
https://t.me/LGH933CAN

I've unlocked and rooted my H933 via the US 998 Nougat/Oreo firmware etc. however running into a snag in converting it back to the H933, as it seems despite de-selecting the recovery partition of the H933 pie firmware LGUP will still write over it along with TWRP.
I tried this again with the recovery backup partition also selected, then again by flashing TWRP to laf and laf to recovery yet the same patched LGUP I've been using throughout this entire process just writes over recovery/laf.
I've made sure to select PARTITION DL each time, is there a command line method to ensure these partitions are skipped? Running out of ideas honestly, I suppose I'll try refurbished US 998 Oreo to make sure the file system/partitions are untouched and try again...
traybourne said:
I successfully updated to H93330k while retaining root/TWRP by mostly following these steps too. However, I skipped flashing TWRP to laf partition as it felt risky to me. I instead flashed Magisk zip to get root before flashing back stock recovery to get into OS. Once booted into Pie, I installed Magisk Manager, enabled ADB, then re-flashed TWRP using ADB with the command "dd if=TWRP.img of=/dev/block/bootdevice/by-name/recovery".
Click to expand...
Click to collapse
Wondering how this is possible as wouldn't flashing the firmware overwrite the root required to access /dev/block/bootdevice/by-name/recovery? I was thinking maybe by skipping the boot partition so you retain the rooted boot.img from Magisk yet, flashed the H933 pie rom three times so far and de-selecting or not, it confirms immediately laf and recovery will be changed just the same.

fljanders said:
I've unlocked and rooted my H933 via the US 998 Nougat/Oreo firmware etc. however running into a snag in converting it back to the H933, as it seems despite de-selecting the recovery partition of the H933 pie firmware LGUP will still write over it along with TWRP.
I tried this again with the recovery backup partition also selected, then again by flashing TWRP to laf and laf to recovery yet the same patched LGUP I've been using throughout this entire process just writes over recovery/laf.
I've made sure to select PARTITION DL each time, is there a command line method to ensure these partitions are skipped? Running out of ideas honestly, I suppose I'll try refurbished US 998 Oreo to make sure the file system/partitions are untouched and try again...
Wondering how this is possible as wouldn't flashing the firmware overwrite the root required to access /dev/block/bootdevice/by-name/recovery? I was thinking maybe by skipping the boot partition so you retain the rooted boot.img from Magisk yet, flashed the H933 pie rom three times so far and de-selecting or not, it confirms immediately laf and recovery will be changed just the same.
Click to expand...
Click to collapse
See the H933 PIE KDZ thread. Has link to Instructions posted.
If that's what you've been following, sorry don't know...

ChazzMatt said:
See the H933 PIE KDZ thread. Has link to Instructions posted.
If that's what you've been following, sorry don't know...
Click to expand...
Click to collapse
It was, pretty sure there's nothing wrong with the guide, the concept makes sense it's just forcing LGUP to skip the recovery partition that's proving to be a challenge. I've got lgup_cmd installed though cannot find any info on how to specify Partition DL installation/skip recovery partition.
Following the guide I select Partition DL and the H933 pie kdz firmware, after selecting start I select all partitions and de-select Recovery however as below it seems to ignore that and flash the default recovery partition regardless:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

David X said:
I have converted H933 to US998 Pie with bootloader unlocked and TWRP. Now my goal is to go back to H933 Pie, and keep the bootloader unlocked and TWRP. I have followed the post #1 in this site and post #2 in https://forum.xda-developers.com/lg...a-20g-twrp-t3868186/post78183349#post78183349, but phone doesn't boot to TWRP after Step #2 (Partition DL Canadian KDZ 30k). I tried several times and still couldn't succeed. I must miss some steps.
Can anybody please help provide what methods or link I should follow? Thanks in advance.
Click to expand...
Click to collapse
Hey, not sure if anyone is still having issues with their devices not booting to TWRP after flashing 933 and therefore losing root + recovery, but after a day of trying to accomplish this on a non-Frankenstein US998 I realized how to force boot to recovery and preserve access.
Immediately when the phone reboots after flashing the .kdz...
Hold the power and volume down until you see the V30 logo, then release and reapply the power button.
Basically trying to master reset. Confirm repeatedly and it will boot to TWRP instead of wiping.
From there you can preserve TWRP, flash magisk, dm verity, etc. Golden :good:

can someone share the partition(s) that will get download mode working?

I deleted all the partitions on my g8 using qfil, now the phone has nothing but an edl mode. If someone could share a backup of the partitions that would get download mode working, I could flash a kdz I have with lgup.
Help would be appreciated

leopard_fist said:
I deleted all the partitions on my g8 using qfil, now the phone has nothing but an edl mode. If someone could share a backup of the partitions that would get download mode working, I could flash a kdz I have with lgup.
Help would be appreciated
Click to expand...
Click to collapse
So when u bring up 'manage partitions' in qfil, what do u see? Nothing? If that's the case u need the backed up partitions and the xml which has offsets etc of where to flash the images, not just the specific partitions.
cheers

AsItLies said:
So when u bring up 'manage partitions' in qfil, what do u see? Nothing? If that's the case u need the backed up partitions and the xml which has offsets etc of where to flash the images, not just the specific partitions.
cheers
Click to expand...
Click to collapse
there's nothin there in qfil, so I guess i'd need the xml also, anyone have this and could share?
i figure i can put a little work in before i throw in the cards and return the phone to amazon

leopard_fist said:
I deleted all the partitions on my g8 using qfil, now the phone has nothing but an edl mode. If someone could share a backup of the partitions that would get download mode working, I could flash a kdz I have with lgup.
Help would be appreciated
Click to expand...
Click to collapse
So I put together something that might help, but you'll probably have to make modifications to the xml to get it to work.
I don't know what the xml should look like for it to work with qfil. This is the xml generated by bkerler edl backup python scripts (with the bkerler scripts, you indicate, on the command line, where the bin files are, so it's not in the xml. But, I think the qfil interface needs that info to be in the xml. I could be wrong about that, you'll have to look at qfil and make changes to the xml if needed).
Also, the xml for luns 1 and 2 files are accurate, but not the xml for lun4. You would also need to edit out all the xml restore in rawprogram4 to only include the files for that lun (to get lgup - boot, abl, laf, and gpt*4).
Lastly, this is from a sprint backup, not sure that matters much except in that there is no kdz for sprint, so not sure how your device will respond in lgup if u use these and then try to lgup a vzw kdz (or any kdz), since there's no totc file to 'ID mismatch' with...
good luck

leopard_fist said:
there's nothin there in qfil, so I guess i'd need the xml also, anyone have this and could share?
i figure i can put a little work in before i throw in the cards and return the phone to amazon
Click to expand...
Click to collapse
wow, return the phone 'in the condition it was in when received' is usually a prerequisite right? In other words... not bricked?
good luck with that too.

AsItLies said:
wow, return the phone 'in the condition it was in when received' is usually a prerequisite right? In other words... not bricked?
good luck with that too.
Click to expand...
Click to collapse
thanks for your time - i'll give it a try when i get home from work this evening, even though it looks to be over my head maybe i can figure it out.
it's actually a sprint phone, though i know a way to crossflash anyway.
you figure i can't return the phone? i just spent 200 bucks on this phone a few days ago, i hope thats not the case

the thing is - my jobs getting ready to send me out of state for a new position. my present phones old, slow, and the screens cracked, so i thought id start things off by getting myself a decent phone and working on setting it up - at present though ive just got an unresponsive piece of plastic.
ive rooted many phones in my day, but this one got me, what can i say

leopard_fist said:
the thing is - my jobs getting ready to send me out of state for a new position. my present phones old, slow, and the screens cracked, so i thought id start things off by getting myself a decent phone and working on setting it up - at present though ive just got an unresponsive piece of plastic.
ive rooted many phones in my day, but this one got me, what can i say
Click to expand...
Click to collapse
Hey it's not my place to tell you what to do. But I can tell you, personally, if I screw up, I take responsibility for it.

leopard_fist said:
I deleted all the partitions on my g8 using qfil, now the phone has nothing but an edl mode. If someone could share a backup of the partitions that would get download mode working, I could flash a kdz I have with lgup.
Help would be appreciated
Click to expand...
Click to collapse
Just follow this thread.

netmsm said:
Just follow this thread.
Click to expand...
Click to collapse
netmsm, thanks for the reply - if I follow the instructions in the thread you linked, is it true that i'll have no imei and serial number on the phone after the process?
thanks again

leopard_fist said:
netmsm, thanks for the reply - if I follow the instructions in the thread you linked, is it true that i'll have no imei and serial number on the phone after the process?
thanks again
Click to expand...
Click to collapse
That's true. You lose IMEI when you erase all partitions. Except, you have crated a backup of Modemst(1 or 2) or FSG partitions so you can restore them, but after recovering from hard brick. So first recover phone following instructions then restore Modemst 1 and 2 or just the FSG.
If your phone is factory unlocked version and you have no backup maybe we can repair IMEI, maybe! Just recover the phone for now.

netmsm said:
That's true. You lose IMEI when you erase all partitions. Except, you have crated a backup of Modemst(1 or 2) or FSG partitions so you can restore them, but after recovering from hard brick. So first recover phone following instructions then restore Modemst 1 and 2 or just the FSG.
If your phone is factory unlocked version and you have no backup maybe we can repair IMEI, maybe! Just recover the phone for now.
Click to expand...
Click to collapse
I have backups of the following files - would the imei/serial info be contained in any of these?
thank you
ftm
modem_a
modem_b
op_a
op_b
sid_a
sid_b
abl_a
abl_b
boot_a
boot_b

leopard_fist said:
I have backups of the following files - would the imei/serial info be contained in any of these?
thank you
ftm
modem_a
modem_b
op_a
op_b
sid_a
sid_b
abl_a
abl_b
boot_a
boot_b
Click to expand...
Click to collapse
Nope, sorry to say. FTM keeps identity data as a temp place from which IMEI cannot be restored. However, you can find the original IMEI from FTM. You need a box to repair the IMEI. The only tool that can repair LG SDM855 phones' IMEI is Octopus. So, you know what to do, I guess ^_^

Question realme gt master edition dead phone (black screen and vibrating) when pressing buttons

My phone was stuck on fastboot But I followed these explanations and my phone was fixed
Then I tried to flash recovery and root But I ran into system problems
And I wanted to flash it again with the same explanations
But this second time nothing appeared on the phone no recovery no fastboot
Only black screen and vibration when I press buttons
And now the device just enters edi mode
Note: I tried to flash it several times, and the same problem. I feel like it died

Restore backup that you made before first flashing. For this go to QFilHelper folder and rename Backup folder to Flash. Then open QfilHelper.exe and enter 6

ogreee said:
Restore backup that you made before first flashing. For this go to QFilHelper folder and rename Backup folder to Flash. Then open QfilHelper.exe and enter 6
Click to expand...
Click to collapse
The problem is that I did not create a backup because my files were damaged from the ground up
I was looking for you, the Russian forum contains links that I cannot download from :3

Akame-iq said:
I was looking for you, the Russian forum contains links that I cannot download from :3
Click to expand...
Click to collapse
In that case, if you didn't make a backup, you shouldn't have flashed the phone at all. Now I don't know how to help you

ogreee said:
In that case, if you didn't make a backup, you shouldn't have flashed the phone at all. Now I don't know how to help you
Click to expand...
Click to collapse
Why don't you give me your backup 3336

Akame-iq said:
Why don't you give me your backup 3336
Click to expand...
Click to collapse
Because your pcb ( board ) number and IMEI will broken if you flash my backup
Make a backup at least now. Repeat the backup process exactly in the video, right up to the location of the files on the desktop.

ogreee said:
Because your pcb ( board ) number and IMEI will broken if you flash my backup
Make a backup at least now. Repeat the backup process exactly in the video, right up to the location of the files on the desktop.
Click to expand...
Click to collapse
I created a backup But I don't think this will help me
I was thinking of creating your own backup for me and i skipping your number and IMEI Am I right or not ؟
damn :3

Akame-iq said:
I was thinking of creating your own backup for me and i skipping your number and IMEI Am I right or not ؟
Click to expand...
Click to collapse
I don't know what partition contains your pcb number, so I asked you make your backup even for bricked phone . For imei it's modemst partition
When you download backup, copy lun5_modemst1.bin and lun5_modemst2.bin files from your backup folder to my backup folder
gtme_backup.zip
drive.google.com
Also, your bootloader must be unlocked because my backup have root

The bootloader is already unlocked
Can you tell me if this region is Russian or European?
ogreee said:
I don't know what partition contains your pcb number, so I asked you make your backup even for bricked phone . For imei it's modemst partition
When you download backup, copy lun5_modemst1.bin and lun5_modemst2.bin files from your backup folder to my backup folder
gtme_backup.zip
drive.google.com
Also, your bootloader must be unlocked because my backup have root
Click to expand...
Click to collapse
brooooooo i loveeee youuuuuu
It worked. Thank you from the bottom of my heart

Akame-iq said:
The bootloader is already unlocked
Can you tell me if this region is Russian or European?
brooooooo i loveeee youuuuuu
It worked. Thank you from the bottom of my heart
Click to expand...
Click to collapse
lun5_modemst1.bin and lun5_modemst2.bin did you change these files? I also didn't take backup of my rom

ogreee said:
I don't know what partition contains your pcb number, so I asked you make your backup even for bricked phone . For imei it's modemst partition
When you download backup, copy lun5_modemst1.bin and lun5_modemst2.bin files from your backup folder to my backup folder
gtme_backup.zip
drive.google.com
Also, your bootloader must be unlocked because my backup have root
Click to expand...
Click to collapse
How to restore this?

Question Can I get A325N vender image?

I root my devices with magisk and make chmod 555 to NVD_IMEI. because of magisk bug. Then I use few week(maybe 2 week?) with no problem. but I trid mount ext4 sdcard(because I want easy to recover with TWRP(but I did not install yet) but AP file is to big so can't use fat32) and it's successful. At next morning(January 28th), I saw signal was dead.(but, wifi is alive. ; I can't remember about Bluetooth, IMEI and is only signal dead or can't attach sim card.) So I reboot my phone( because I just think something crash it) but can't boot and get stuck. so I flash stock rom but can't boot. but only recovery(Normal and TWRP all) work well. So I do re-partition but also not work. I do NAND Erase with magisk patched AP and it booted. but IMEI disappear(of course because I do NAND Erase) and wifi did not work. I flash stock rom again but boot fail... when flash magisk patched AP it boot. I don't know why only magisk patched AP only boot, but I will use patched AP so not important yet.(I don't know what will happen future.) I think wifi error because I NAND Erase so vender partition broke. So I will flash vender image first. but sadly I have IMEI backup but I don't have vender partition backup... So I search internet but couldn't find vender image. Where can I get image? Is because of other problem? Then what and how can I fix it?
vendor.zip is vender folder(partition) backup after I NAND Erase it. TWRP backups of Vender partitions are also fine. If there's anything that needs to be changed for each device, please let me know as well.(ex.S/N, IMEI)

Broken partition after NAND erase? Sounds unlikely if flashing went successful. You cannot break NAND memory itself using software, and flashing with the "re-partition" option using external PIT file will re-partition everything unconditionally, so no broken partition may remain after that. Sounds more like you flashed wrong or incompatible stock firmware. And did you do Factory Reset after flashing?
P.S.: And I still don't understand why so many people need Magisk so badly. Root is needed only for a few quite low-level apps.

uluruman said:
Broken partition after NAND erase? Sounds unlikely if flashing went successful. You cannot break NAND memory itself using software, and flashing with the "re-partition" option using external PIT file will re-partition everything unconditionally, so no broken partition may remain after that. Sounds more like you flashed wrong or incompatible stock firmware. And did you do Factory Reset after flashing?
P.S.: And I still don't understand why so many people need Magisk so badly. Root is needed only for a few quite low-level apps.
Click to expand...
Click to collapse
NAND Erase is at odin option.
I do root for use "few quite low-level apps" and view and fix or backup app data.
I use "SM-A325N_2_20230113085551_pl06359zs5_fac.zip". It's compatible stock from samsung server. I use this stock to recover once, and I recover it.

Ok ) I have extracted vendor.img from your firmware: https://easyupload.io/vgzftz (if that's what you needed, I cannot understand your language clearly enough). Only I am not sure how you're going to flash it, because it's a dynamic partition inside the physical "super" partition and cannot be flashed directly besides (reportedly) using dd from the shell or using fastboot.

I still think you somehow mixed parts from different firmware versions. I never seen a situation when flashing a complete stock firmware with re-partition and NAND erase and then Factory Reset would not fix the booting. Try going into Recovery and do Factory Reset right after flashing, without allowing the system to try booting.

uluruman said:
Ok ) 귀하의 펌웨어에서 vendor.img를 추출했습니다: https://easyupload.io/vgzftz (필요한 경우 귀하의 언어를 충분히 이해할 수 없습니다). 물리적 "슈퍼" 파티션 내부의 동적 파티션이고 셸에서 dd를 사용하거나 fastboot를 사용하는 것 외에는 직접 플래시할 수 없기 때문에 어떻게 플래시할지 확신할 수 없습니다.
Click to expand...
Click to collapse
삼성에는 패스트부트가 없습니다. 그러나 다운로드 모드가 있습니다. 다운로드 모드에서 odin을 사용하여 펌웨어를 업로드하십시오. 또한 TWRP에서 img를 플래시할 수 있습니다.

uluruman said:
Ok ) I have extracted vendor.img from your firmware: https://easyupload.io/vgzftz (if that's what you needed, I cannot understand your language clearly enough). Only I am not sure how you're going to flash it, because it's a dynamic partition inside the physical "super" partition and cannot be flashed directly besides (reportedly) using dd from the shell or using fastboot.
Click to expand...
Click to collapse
At samsung, there is no fastboot. but, there is download mode. Use odin to flash at download mode. Also can flash img and zip at TWRP.

If you still need help please be a bit clearer what exactly is your problem, what you cannot achieve. I think a Korean-speaking person would be of much help here but it seems there is none