[Solved]Bricked my tablet. Can only enter download mode. - Galaxy Tab S Q&A, Help & Troubleshooting

Model: SM-T800
Current ROM: LineageOS 14.1
Current recovery: twrp-3.1.1-0
So I was trying to edit the boot logo on my tablet. I found the logo.jpg in an archive (/dev/block/platform/dw_something0/by-name/PARAM).
I backed up the PARAM archive, extracted it, edited the image slightly, repackaged it and put it back. Then I restarted the tablet and whoops black screen.
I guess some permissions didn't end up as they should have.
I can't get in to recovery by button combination and I can't boot the system. I can however get in to download mode.
Edit: What I ended up doing was flashing a stock bootloader with odin that contained param.bin.
Now I can continue what i was doing. SOLVED

Related

Reinstalling OS after accidental delete

While attempting to install 6.0.1 on my SM-T705 I accidentally deleted the OS leaving me with the black screen of death (Samsung Tablet S logo and powered by Android). As I have only recently moved to Android and am still learning the ropes so any idiot-proof instructions to resurrect my tablet would be appreciated.
Thanks.
Glenn
Just flash the stock firmware with odin. Available at sammobile or youmobile.
Next time don't be silly and use TWRP to make that all important backup.
Here is how to flash firmware on your device:
1) Obtain the firmware. I find the most trustworthy place to DL it to be SamMobile. (You will need an account and it is a very slow download)
2) Download Odin3. It can be downloaded from here.
3) Download SAMSUNG_USB_Driver_for_Mobile_Phones.zip from here
4) Extract the zip and install the drivers
5) Power off your device. Once it is fully powered off, hold POWER+VOLUME DOWN+HOME until you reach the "Custom OS" screen. Once you reach this screen, press Volume Up.
6) Plug your device into your computer and extract the Odin zip. Now run the Odin EXE.
FOLLOW THE INSTRUCTIONS FROM THIS POINT ON VERY CAREFULLY
8) Extract the .tar.md5 from the firmware zip you downloaded from SamMobile earlier.
7) In Odin, select "AP" and select the .tar.md5. Odin will appear to hang, but give it a few minutes to finish processing the file.
8) Click "Start" in Odin.
9) Once the firmware download is complete, your device will reboot. It should work after this. If not, reboot back into Recovery mode to factory reset.
Thanks to you both for the help. I'm back up and running and the tablet has already been backed up with TWRP just in case I do something dumb like this again.

[RECOVERY][UNOFFICIAL] TWRP 3.3.1-7 Magisk Prepatched ONLY FOR (ROOTED S10+EXYNOS)

After flashing this there is no need to press that key combo (VOL up key + Power + Bixby) to boot into Magisk mode. Just after flashing this image your S10+ will automatically boot up in the Magisk mode. And that key combo (VOL up key + Power + Bixby) will be used to boot your phone directly into recovery mode.
Download : PrePatched TWRP S10+http://www.mediafire.com/file/uq378oaeb6s80hc/Prepatched_Twrp_S10%2B.zip/file
DISCLAIMER : FLASH AT YOUR OWN RISK AND I AM NOT RESPONSIBLE FOR ANY DAMAGE TO YOUR PHONE.
IF MY POST IS USEFUL FOR YOU THEN KINDLY PRESS THE THANKS BUTTON
Special Thanks To : All credit goes to @ianmacd For his amazing Work for Twrp and Latest unofficial magisk for S10 family & TWRP Team &
@topjohnwu for his work for Magisk
Installation Instructions for the Rooted Users : Before Installing Kindly Make a Backup Of Your Phone and Internal storage
1. Requires Root : Download The Image File From The Above Download Link. Place It In The Root Of Your /sdcard folder .
2. Run The Following Commands Via Adb Shell
3. After Installation Do Wipe Your Internal storage and Do Not Factory Reset Your Phone Otherwise It Will Cause BOOTLOOP
su
dd if=/sdcard/twrp.img of=/dev/block/platform/13d60000.ufs/by-name/recovery
Click to expand...
Click to collapse
S10+ Exynos or Snapdragon ? or work for both ?
for s10 + exynos version
Just 3 things i wanna ask.
1. But you didnt mention twrp version?
2. Even if we already are on twrp' latest version we need to wipe because its prepatched?
3. We shouldnt ever factory reset or just after first installation? But we can factory reset from settings?
1. Latest Twrp 3.3.1-7
2. if you have a twrp installed then kindly do not flash it.
3. Kindly make a backup from twrp recovery before making a factory reset in case any thing goes wrong
Sorry for such a rudimentary question but are the adb commands done individually after "su" or is that one command line too long to fit in the box? Sorry, I've just been fighting with getting twrp on my phone since last night. Root works fine but after flashing patched img file I can never get it to go into twrp. Always goes to stock recovery even though flash is successful. I originally thought I was messing up the key combo but I have my suspicions. Any help would be greatly appreciated. Thanks
jtford said:
Sorry for such a rudimentary question but are the adb commands done individually after "su" or is that one command line too long to fit in the box? Sorry, I've just been fighting with getting twrp on my phone since last night. Root works fine but after flashing patched img file I can never get it to go into twrp. Always goes to stock recovery even though flash is successful. I originally thought I was messing up the key combo but I have my suspicions. Any help would be greatly appreciated. Thanks
Click to expand...
Click to collapse
UPDATE××Got TWRP to boot the first time. First time system booted fine but I lost root. Did a fresh root per magisk install guide and reflashed twrp.img in root shell. Got twrp to boot again but it continues to boot loop. I only wiped internal with no factory reset. I know it's probably something I'm doing. Any suggestions?
jtford said:
UPDATE××Got TWRP to boot the first time. First time system booted fine but I lost root. Did a fresh root per magisk install guide and reflashed twrp.img in root shell. Got twrp to boot again but it continues to boot loop. I only wiped internal with no factory reset. I know it's probably something I'm doing. Any suggestions?
Click to expand...
Click to collapse
It seems magisk not installed properly. Download latest firmware from Carotix folder Here it have prepatched recovery prepatched ap you need not to do anything you need to reflash recovery n system ...use odin flash patched ap cp bl and use HOME_CSC (you will not use any data apps or anything) Just flash using odin everything will work fine.
also download multidisabler from ian's multidisabler thread HERE put it in phone as need to flash after boot into Twrp!
instructions copied from Carotix thread
Download 4 files from OTA/ODIN FILES then follow this guide:
and put the last Multidisabler in your phone
1- Turn off the device and put it in download mode with the bixby / vol down button and inserting the cable to the PC at this point open Odin remove the check mark from autoreboot
2- Load the AP .tar file downloaded from OTA together with the BL the CP and the HOME_CSC .... if you put the CSC you lose all the data
3- Start the flash and wait
4- At the end you disconnect the phone from the cable and with the power / vol down keys force the switch off as soon as the screen goes black press vol + / bixby / power to go in recovery and don't leave the keys until you see the twrp screen, continue to keep the 3 keys pressed and wait for the recovery to start again
5- Flash the multidisabler then from the main screen choose recovery reboot to boot rooted/magisk system.
comsite said:
It seems magisk not installed properly. Download latest firmware from Carotix folder Here it have prepatched recovery prepatched ap you need not to do anything you need to reflash recovery n system ...use odin flash patched ap cp bl and use HOME_CSC (you will not use any data apps or anything) Just flash using odin everything will work fine.
also download multidisabler from ian's multidisabler thread HERE put it in phone as need to flash after boot into Twrp!
instructions copied from Carotix thread
Download 4 files from OTA/ODIN FILES then follow this guide:
and put the last Multidisabler in your phone
1- Turn off the device and put it in download mode with the bixby / vol down button and inserting the cable to the PC at this point open Odin remove the check mark from autoreboot
2- Load the AP .tar file downloaded from OTA together with the BL the CP and the HOME_CSC .... if you put the CSC you lose all the data
3- Start the flash and wait
4- At the end you disconnect the phone from the cable and with the power / vol down keys force the switch off as soon as the screen goes black press vol + / bixby / power to go in recovery and don't leave the keys until you see the twrp screen, continue to keep the 3 keys pressed and wait for the recovery to start again
5- Flash the multidisabler then from the main screen choose recovery reboot to boot rooted/magisk system.
Click to expand...
Click to collapse
Thanks for your help. I had to do it a little unconventional to get it working. None of the prepatched recoveries that are included in all these firmware downloads would work for me using Odin. Only flashing this twrp.img in a root shell would work. I finally just flashed Beyond rom zip after getting into twrp along with the disabler zip. Boots into rooted system with no problems and I can boot into twrp with no problems as well. Oh yea, I flashed Beyond over ASG8 also. Not sure why I could never get ASH6 to work.
[RECOVERY] TWRP 3.3.1 Changelog
v3.3.1-9_ianmacd for G97[035]F [inc. ASH6 kernel (which also works with ASH1 firmware)] (2019-09-17)
Restore working MTP functionality to TWRP. With thanks to bigbiff for the reference and to Geiti for his commit embodying the same fix.
v3.3.1-8_ianmacd for G97[035]F [inc. ASH6 kernel (which also works with ASH1 firmware)] (2019-09-06)
Kernel rebased on Samsung's ASH6 source code.
[System-as-root] MultidisablerChange log
v1.6 (2019-09-18)
Add support for more variants of A50: A505([YG]N|G).
Fix A205G detection.
Hello kkrraazzyy,
can you please explain how to install your twrp.
I already habe twrp installed. an this rom. --> https://forum.xda-developers.com/s10-plus/development/rom-carhdrom-1-t3938987
But a want to install your twrp to boot always with Magisk without to press any key.
I need your help please.
Any proper YouTube guide video for these things, as flashing/rooting became so complicated with so many steps.... Thank you!
So from my understanding this is the first and only way to have the phno boot into the patched recovery automatically without needing top physically press the button combo? Or have I missed something Was just expecting there to have been a lot more attention that's all.
This has actually what has been one of the main reasons holding me back from rooting as it reminds me back in the day of tethered and untethered jailbreaks for iPhones.
Except that this is just a inconvenience while tethered would make the phone practically unusable.
Is there an app i can use to backup and restore my kik chats? I got a new phone, a Samsung Galaxy 10+ and want to tramsfer my kik chats and save data for Digimon Heroes! to my new galaxy 10+ i dont have root on either phones is there a app (apk) or one i can downlod on my laptop to make the backup of them so i can bring them over. Please i only have a dew days left to transfer my number over and have my old phone shut dwn by my previous provider. I need to do it on the next 2 days.
qaz015393 said:
Is there an app i can use to backup and restore my kik chats? I got a new phone, a Samsung Galaxy 10+ and want to tramsfer my kik chats and save data for Digimon Heroes! to my new galaxy 10+ i dont have root on either phones is there a app (apk) or one i can downlod on my laptop to make the backup of them so i can bring them over. Please i only have a dew days left to transfer my number over and have my old phone shut dwn by my previous provider. I need to do it on the next 2 days.
Click to expand...
Click to collapse
Use Smart Switch by Samsung, it includes the possibility of transferring all your data and settings using a USB cable. I transferred everything from my old phone to this one (S10+ SM-G975F). I don't know if it will work on non-Samsung devices, but it's worth a try.
I have android 10 on my s10+, will this twrp work with android q?
possible to boot without root permissions too?
:good:
Hi @kkrraazzyy , could you show us how you did it?
because @ianmacd https://forum.xda-developers.com/ga...covery-twrp-3-3-0-galaxy-s10-exynos-t3924856/
latest version does not seem to provide this awesome function.

samsung a505f stuck on logo

hi i wanted to flash magisk using twrp so i had to install twrp first using odin i followed all instructions in there androidweblog.com/samsung-galaxy-a50-sm-a505f-root-install-twrp-recovery
and flashed that twrp zip file
mega.nz/#!SWYwAQAb!bbLnex8yhT7tyBTdTMr2wIS-tzITjg5VMJ_p1msXenQ
but after flashing
the phone is stuck in samsung a50 logo and i can do nothing except opening download mode
and i get error this phone's bootloader is unlocked and its software integrity can't be verified any data on this phone maybe un vulnerable to attackers don't software any important or sensitive information on this phone
what should i do to bring it back and uninstall flashed twrp
thanks in advance
1) Find you firmware [https://www.sammobile.com/firmwares/search/a505/]
-Clicking on your model will present you with firmware downloads
-Find yours and download it [country and network or just the country should work]
-Extract it somewhere.
2) Get Odin [https://dl2018.sammobile.com/Odin3-v3.14.4.zip]
-Extract it somewhere
-Load it
-Add the files from the firmware folder into the correct sections (i.e/ ap, bl, csc - I cant remeber them all of the top of my head)
3) Get into download mode
-Power off device or if its boot looping Press and hold power + vol down to force a restart
-Press and hold both vol buttons and connect it to your computer with usb
-Odin should now say added in the log
4) press start and wait

SM-G986B - BTJ4 to DUF9 now unable to install Magisk ?

I just upgraded my phone from BTJ4 to DUF9 and everything seems to be correct except when I try to re-install Magisk to get root again .. after patching the boot.img.lz4 file(via boot.tar) and installing it via Odin AP the phone just enter a bootloop with the black screen and Samsung logo on it.
I've tried everything I can come up with but I get nowhere.. I've tried Magisk v22 and v23 - same result, tried installing with BL+CP+CSC/BL+CP+CSC with vbmeta_disable in USER and the patched magisk boot image in AP .. still no luck.
Magisk seem happy patching both with v22 and v23 so that seems correkt. The file grows from ~20k as boot.tar to ~60k as magisk_patched tar - which I guess is ok..
Would appreciate any help in getting this to work.
hochocnua said:
New version for SM-G985F with region/firmware DBT/G985FXXU6DUB5
Guide firmwares update and file here
Downloads for : Samsung Galaxy S20 | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Thanks @ianmacd and @afaneh92 for help and guide
1. Select the BL, AP, CP and HOME_CSC files (save data)
** don't run the firmware yet
2. Download Ian's latest TWRP (twrp-z3s-3.5.0_10-A11_x_ianmacd.img) containing TWRP + patched vbmeta.img into USERDATA slot in Odin.
twrp-z3s-3.5.0_10-A11_6+vbmeta_DUB5.tar | by LEAKs Việt Nam for Galaxy S20
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
3. Uncheck the automatic reboot option in Odin
4. run the flashing
5. When the firmware is finished (leave USB connected !!!), hold the Vol Down + Power buttons, and then, as soon as the screen turns black, hold the Vol Up + Power buttons to boot into recovery
*, keep in mind that the first time you boot into recovery, it initializes and then reboots, so just keep the Vol Up + Power buttons pressed for longer than
6. TWRP - Multi-Disabler Firmware
7. Reboot TWRP - Flash Magisk (stable)
8. Flash Fix_warning_up_param_S20 +
9. RESTART.
Click to expand...
Click to collapse
You have to use this method.
Try using canary version of magisk.
Hmm chieco’s post explains pretty much everything
Tried Canary build of Magisk - didn't help.
Installed TWRP according to above .. didn't work at all. Now the phone is completely dead, only thing that boots i TWRP Recovery.
Correction - without flashing anything at all with TWRP I can actually boot into the phone ..
Correction 2 - when I flash the multidisabler-samsung-3.1.zip it stops the phone from booting.
Correction 3 - so after finally trying just about everything I can come up with it seems as when anything at all touches the boot or system partitions it stops the phone from booting normally.
If I just install the rom with twrp+vbmeta everything works as it should. If I then flash anything at all, doesn't matter what, it stops working. If I flash a magisk patched image - it stops booting.
So.. now I'm stuck.. I have no more ideas.
I even installed the previous release DUE4 with the same result.
I tried patching the complete AP file with magisk - same result.. phone refuses to boot normally.
If I do the Magisk patch file patching before doing the first system boot after upgrading it does the optimize apps thingie but then after rebooting it stops with a bootloop. And by the way under all this TWRP gets replaced with the default Android recovery .. no matter what I do - the internal SD card is no longer encrypted tho so I guess the multidisabler has done its thing.
Only thing I have NOT tried yet is a complete factory reset.. but I don't know if that would make any difference ?
So ended up with a full wipe and installing BeyondROM .. now the phone is rooted and booting with twrp functioning.
O well.. the fun begins restoring everything again..

Fastboot Loop

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.

Categories

Resources