Hi to all, I need help with my Thinq G8x G85ßEMW with 10 V20d-eea-xx.
I unlocked bootloader, installed magisk via boot_a and boot_b and all was fine for 3 weeks.
Now I made a reboot and i am stuck at the LG logo, which is spinning.
I can press "power" + "volDwn" and it restarts but always stuck at LG logo.
I also can enter EDL mode sucessfully and start the partition manager.
I reflashed abl_a and abl_b and also BootA and BootB, but I still have a spinning LG " Life´s Good".
What can I do ?
Maybe it did an ota update without my knowledge? I was on 10d when I did all the unlocking.
When flashing the original boot_a and boot_b phone boots again.
I then patched via magisk (20005) the both img files and reflashed them via QFIL but then I have again the boot stuck in LG Logo.
So it seems as soon as I use the magisk boot files I can not boot anymore.
Also with the initial 22.0 apk Magisk and Patching I can not get it to boot past the LG Logo again.
I do have to patch both boot_a and boot_b, right ?
I also just patched boot_b and flashed with qfil but still no joy.
Any ideas to use magisk again? Or is there an alternative to root when the bootloader has been unlocked?
Does ANYONE have a working bootB with magisk for my model ?
THANKS !!!
bambi007 said:
I unlocked bootloader, installed magisk via boot_a and boot_b and all was fine for 3 weeks.
Click to expand...
Click to collapse
So, you've BL Unlocked in the device. Just flash the kdz (stock ROM) of your device with LG UP, see whether it gets booted to home screen. Then go for the rightly patched boot image of your device. Seems the patched boot image is the culprit, get that straight.
Flashing KDZ Using Lg up LG g8x (Guide)
Download required file : http://www.mediafire.com/folder/4mqovbes4jvvw/lg+UP In order, unzip the three zip files Install Lg USb driver. Install Lab first Install the DLL again Finally put UI_Config.lgl in the C:\Program Files (x86)\LG...
forum.xda-developers.com
Related
Hello everyone, I have a problem, maybe someone will be able to assist me.
I have a phone Samsung Galaxy A20e (SM-A202F) with unlocked bootloader (Yes, in developer settings it says "Bootloader already unlocked" and the "OEM unlocking" option is grayed out).
I am trying to root the device and for that I have modified boot.img that I repacked with Magisk Manager, and an empty vbmeta.img that makes the device ignore verify. So far no guides I found worked. When i try to flash modified AP (with the modified boot.img inside) with Odin (including the rest of the files) it flashes successfully but I get "Error verifying vbmeta image" on the device screen and device is stuck on Download mode. If I re-flash unmodified AP with Odin, it works and device is like new.
All the small details aside, the problem is that I can't boot the device into fastboot mode. Whenever I do "adb reboot fastboot" it always boots into Download mode and fastboot commands don't work. Same goes with stock recovery, when I click "Reboot to bootloader", device boots into Download mode.
On the Magisk website I read something about "VaultKeeper" but I was sure i connected to Wi-Fi during setup and then enabled Developer mode. Link What I might be missing here?
tomasxp said:
Hello everyone, I have a problem, maybe someone will be able to assist me.
I have a phone Samsung Galaxy A20e (SM-A202F) with unlocked bootloader (Yes, in developer settings it says "Bootloader already unlocked" and the "OEM unlocking" option is grayed out).
I am trying to root the device and for that I have modified boot.img that I repacked with Magisk Manager, and an empty vbmeta.img that makes the device ignore verify. So far no guides I found worked. When i try to flash modified AP (with the modified boot.img inside) with Odin (including the rest of the files) it flashes successfully but I get "Error verifying vbmeta image" on the device screen and device is stuck on Download mode. If I re-flash unmodified AP with Odin, it works and device is like new.
All the small details aside, the problem is that I can't boot the device into fastboot mode. Whenever I do "adb reboot fastboot" it always boots into Download mode and fastboot commands don't work. Same goes with stock recovery, when I click "Reboot to bootloader", device boots into Download mode.
On the Magisk website I read something about "VaultKeeper" but I was sure i connected to Wi-Fi during setup and then enabled Developer mode. Link What I might be missing here?
Click to expand...
Click to collapse
Samsung don't support fastboot as Odin mode is what is used. You'll need to edit the fstab under /vender/etc.. and no you can't replace it with fastboot because you'll hard brick the device
Unfortunately I'm unsure if what's going on so you may not be able to root your device
TheExploitedOne said:
Samsung don't support fastboot as Odin mode is what is used. You'll need to edit the fstab under /vender/etc.. and no you can't replace it with fastboot because you'll hard brick the device
Unfortunately I'm unsure if what's going on so you may not be able to root your device
Click to expand...
Click to collapse
Thank you, I didn't know new Samsung devices don't support fastboot (or at least this one specifically).
On the other hand, when you said it, I tried other thing. I repacked AP image with Magisk modified boot.img and empty vbmeta.img I had from other tutorial and after flashing with Odin and factory resetting it stopped showing the boot error and booted the Android up. Long 1st boot tho, about 6 minutes. So far the device appears to work fine, will update if I manage to complete the root process.
EDIT1: The phone appears to be working with patched boot.img and vbmeta.img but Magisk can't detect that boot.img is pached. It only gives me the option to download zip (which I can't install because I don't have TWRP installed) and patch the boot.img again. Well atleast we are getting somewhere with this, I'll try to figure it out later.
EDIT2: I successfully rooted the phone. I had once again to extract the modified boot.img from the AP, modify it the second time with Magisk. Then I put it back into the AP file, deleting all other images, leaving only boot.img and META-DATA folder. Flashed it through Odin once again and this time Magisk waited 30s at launch and showed that everything is ok. Root checker is also showing that device is rooted as superuser asks for permissions.
tomasxp said:
Thank you, I didn't know new Samsung devices don't support fastboot (or at least this one specifically).
On the other hand, when you said it, I tried other thing. I repacked AP image with Magisk modified boot.img and empty vbmeta.img I had from other tutorial and after flashing with Odin and factory resetting it stopped showing the boot error and booted the Android up. Long 1st boot tho, about 6 minutes. So far the device appears to work fine, will update if I manage to complete the root process.
EDIT1: The phone appears to be working with patched boot.img and vbmeta.img but Magisk can't detect that boot.img is pached. It only gives me the option to download zip (which I can't install because I don't have TWRP installed) and patch the boot.img again. Well atleast we are getting somewhere with this, I'll try to figure it out later.
EDIT2: I successfully rooted the phone. I had once again to extract the modified boot.img from the AP, modify it the second time with Magisk. Then I put it back into the AP file, deleting all other images, leaving only boot.img and META-DATA folder. Flashed it through Odin once again and this time Magisk waited 30s at launch and showed that everything is ok. Root checker is also showing that device is rooted as superuser asks for permissions.
Click to expand...
Click to collapse
That's good to hear that root was successful!
I tried to upgrade magisk to latest from magisk manager and device boot loop at Tmobile logo. I can get into download mode, fast boot, and twrp recovery.
However, I do not wanna to reinstall the kdz from download mode .So, flashing the stock boot img from fastboot will fix it ?
Please attach stock boot img or magisk patched boot img . Thanks
i know there are other threads on this topic. But after going through them I cant find the fix.
I unlocked bootloader and tried to root. Its seems to have worked, but the touchscreen no longer works.
I used lmsa to download the stock rom. installed magisk and ran the boot.img to get the patched boot. Then flashed the patched boot and when i rebooted the device...no touchscreen.
I tried to reflash the original boot.img but that didnt help.
I tried to use LMSA to rescue. but when i connect the phone it says "unable to match firmware. Some key information cannot be read from device."
The original adb fastboot was old. So I did update to the r30 version and tried flashing everything again. but it still boots up and no touchscreen.
Im obviously at a loss here. so any help would be appreciated. Just to even get it back to stock would be fine.
Or do I try to install twrp and throw a custom rom on? would that work. Again, at a loss...
TIA
UPDATE: ive gotten everything sorted. no more bootloop. touchscreen working. connecting to lmsa. and rooted. Thank you for all the responses.
I think what happened is that when i started all this i was not using the latest adb. That seemed to not be an issue for unlocking bootloader, but a major issue for rooting. When i tried to root,i got the no touchscreen. So I followed directions and went to manually flash the stock firmware. I didnt know how to do this and couldnt find instructions for the g power. but did find instructions for the g8 power and assumed it would be the same...its almost the same, but not, so i got the bootloop.
These are the instructions:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot flash super super.img_sparsechunk.10
fastboot flash super super.img_sparsechunk.11
fastboot flash super super.img_sparsechunk.12
fastboot flash super super.img_sparsechunk.13
fastboot flash super super.img_sparsechunk.14
fastboot flash super super.img_sparsechunk.15
I added fastboot flash super super.img_sparsechunk.15, because the g8 power only has 14 sparsechunks and thats why i kept getting the bootloop. very stupid mistake that was driving me nuts! Once i added that 15th line the phone booted up and touchscreen worked again.
Then i installed magisk manager. Took the boot.img file from my stock rom and put it on my phone. back in magisk i clicked on install a patch file, chose the boot.img and created a magisk_patched.img which i put back into the adb folder i previously used to flash the firmware.
Then went back to fastboot and flashed the magisk_patched.img and the phone is now working and rooted...THANK GOD
cnoevl21 said:
i know there are other threads on this topic. But after going through them I cant find the fix.
I unlocked bootloader and tried to root. Its seems to have worked, but the touchscreen no longer works.
I used lmsa to download the stock rom. installed magisk and ran the boot.img to get the patched boot. Then flashed the patched boot and when i rebooted the device...no touchscreen.
I tried to reflash the original boot.img but that didnt help.
I tried to use LMSA to rescue. but when i connect the phone it says "unable to match firmware. Some key information cannot be read from device."
The original adb fastboot was old. So I did update to the r30 version and tried flashing everything again. but it still boots up and no touchscreen.
Im obviously at a loss here. so any help would be appreciated. Just to even get it back to stock would be fine.
Or do I try to install twrp and throw a custom rom on? would that work. Again, at a loss...
TIA
Click to expand...
Click to collapse
Flash stock ROM manually, it will fix the problem
riyan65 said:
Flash stock ROM manually, it will fix the problem
Click to expand...
Click to collapse
The US stock ROM does not have a 'flash all' option. So i have no idea how to flash it. ugh
cnoevl21 said:
The US stock ROM does not have a 'flash all' option. So i have no idea how to flash it. ugh
Click to expand...
Click to collapse
I just ran into the same problem and asked you about it in the other thread. Right after, I tried the boot from XT2041-4_SOFIA_RETUS_10_QPMS30.80-51-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC and got my touchscreen back.
https ://mirrors.lolinet.com/firmware/moto/sofia/official/RETUS/
I found out more of what's going on and posted in the other thread:
I just did the same exact thing. LMSA gave me SOFIA_RETAIL_QPMS30.80_51_8. Lost touchscreen with the patched boot. Used the stock 30.80_51_8 boot and didn't fix it. Also tried the older QPMS30.80-51-3, no dice.
Oh and LMSA can't rescue... key information cannot be read from device.
I'd appreciate any help. Thanks.
UPDATE - found the boot from XT2041-4_SOFIA_RETUS_10_QPMS30.80-51-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC got the screen working again.
UPDATE 2 - patching -5 still left me no touchscreen. Went back to stock -5 and didn't work. Tried -8 and works again... I'm confused.
UPDATE 3 - when phone booted up, it notified me -8 was just installed... Patched -8 boot again and everything appears to be working fine. Moral of story - LMSA downloads the correct firmware if you give the phone enough time to finish auto-updating before rooting. SMH
haanjamin said:
I found out more of what's going on and posted in the other thread:
I just did the same exact thing. LMSA gave me SOFIA_RETAIL_QPMS30.80_51_8. Lost touchscreen with the patched boot. Used the stock 30.80_51_8 boot and didn't fix it. Also tried the older QPMS30.80-51-3, no dice.
Oh and LMSA can't rescue... key information cannot be read from device.
I'd appreciate any help. Thanks.
UPDATE - found the boot from XT2041-4_SOFIA_RETUS_10_QPMS30.80-51-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC got the screen working again.
UPDATE 2 - patching -5 still left me no touchscreen. Went back to stock -5 and didn't work. Tried -8 and works again... I'm confused.
UPDATE 3 - when phone booted up, it notified me -8 was just installed... Patched -8 boot again and everything appears to be working fine. Moral of story - LMSA downloads the correct firmware if you give the phone enough time to finish auto-updating before rooting. SMH
Click to expand...
Click to collapse
good info to know. but now ive gone i screwed my phone up even worse. cuz now im stuck in boot loop. i was trying 105-5, but ill try 51-5, then -8. maybe one of them is the right stupid firmware for my phone
Do not panic.
Follow this guide to flash correct ROM, and patch boot from the ROM to get root
https://forum.xda-developers.com/moto-g-power/how-to/moto-g-power-flashing-guide-t4159301
mingkee said:
Do not panic.
Follow this guide to flash correct ROM, and patch boot from the ROM to get root
https://forum.xda-developers.com/moto-g-power/how-to/moto-g-power-flashing-guide-t4159301
Click to expand...
Click to collapse
ive tried this. i either dont have (and dont know) which is the correct rom. or some other issue. i can get into fastboot mode, no problem. but when i type fastboot reboot fastboot i get that long list of commands, as if im typing in a bad command. and it does not go into fastbootd. i can, however, get into fastbootd through recovery. but every time i try to flash something there, it fails (no file or directory).
And i cant use LMSA cuz when i try to connect, it says the phone has incorrect firmware.
I unlocked the bootloader succesfully then i tried to root the phone so i downloaded a relame 7 rom and patched boot.img with magisk then i did a fastboot then i typed in my pc cmd (fastboot flash magisk_patched.img) then (fastboot reboot) then i stucked at bootloop and i can't go to fastboot or recovery , Even the pc don't detect my phone, I think its because i downloaded a rom of newer version that i didn't update to it before flashing the patched boot or maybe i typed wrong cmd , Please any help guys there isn't any realme support center in my country, Thanks in advance.
you should have flashed vbmeta.img so that you don't get in bootloop
You mean your phone wouldn't go into bootloader by "Vol. down button + power button" holding from power off state?
T59y9 said:
fastboot flash magisk_patched.img
Click to expand...
Click to collapse
Do you mean "fastboot flash recovery magisk_patched.img"??
the correct command is fastboot flash boot magisk_patched.img
Maybe he wrote fastboot flash magisk_patched .img
but I think it would have returned an error
T59y9 said:
I unlocked the bootloader succesfully then i tried to root the phone so i downloaded a relame 7 rom and patched boot.img with magisk then i did a fastboot then i typed in my pc cmd (fastboot flash magisk_patched.img) then (fastboot reboot) then i stucked at bootloop and i can't go to fastboot or recovery , Even the pc don't detect my phone, I think its because i downloaded a rom of newer version that i didn't update to it before flashing the patched boot or maybe i typed wrong cmd , Please any help guys there isn't any realme support center in my country, Thanks in advance.
Click to expand...
Click to collapse
Maybe the rom you downloaded and the base rom running on your device is not the same version, that may cause the error. {Mod edit}
@T59y9
Hi
did you solve in some way?
My realme 7 5G is not rooted.
Just arrived me friday, I udated to new firmware trought recovery. After the reboot did not woke up anymore.
Black screen. no realme logo. nothing.
tried all button combinations, nothing. no boot, no logo, recovery, no fastboot.
tried also with charger attached, with usb on PC.
Nothing...
Any idea to solve my problem?
thank you.
how did you unlock the bootloader?
in depth test app says my model does not support in-depth test
if you are asking me, I did not unlock anything.
just flashing new OS update trought recovery. after that device dead. not buttons combinations to get fastboot or anything else...
gannjunior said:
if you are asking me, I did not unlock anything.
just flashing new OS update trought recovery. after that device dead. not buttons combinations to get fastboot or anything else...
Click to expand...
Click to collapse
oh sorry
any idea how to solve?
T59y9 said:
I unlocked the bootloader succesfully then i tried to root the phone so i downloaded a relame 7 rom and patched boot.img with magisk then i did a fastboot then i typed in my pc cmd (fastboot flash magisk_patched.img) then (fastboot reboot) then i stucked at bootloop and i can't go to fastboot or recovery , Even the pc don't detect my phone, I think its because i downloaded a rom of newer version that i didn't update to it before flashing the patched boot or maybe i typed wrong cmd , Please any help guys there isn't any realme support center in my country, Thanks in advance.
Click to expand...
Click to collapse
same anyone know how to solve this pls :/
First you all. Say the Model Number. You talk about Realme 7/Pro or 5G...
This issues is fixable. Just need extra tools to bypass Google FRP and a factory images ROM versions. Fixed few devices with the same situation!
T59y9 said:
I unlocked the bootloader succesfully then i tried to root the phone so i downloaded a relame 7 rom and patched boot.img with magisk then i did a fastboot then i typed in my pc cmd (fastboot flash magisk_patched.img) then (fastboot reboot) then i stucked at bootloop and i can't go to fastboot or recovery , Even the pc don't detect my phone, I think its because i downloaded a rom of newer version that i didn't update to it before flashing the patched boot or maybe i typed wrong cmd , Please any help guys there isn't any realme support center in my country, Thanks in advance.
Click to expand...
Click to collapse
T59y9 said:
I unlocked the bootloader succesfully then i tried to root the phone so i downloaded a relame 7 rom and patched boot.img with magisk then i did a fastboot then i typed in my pc cmd (fastboot flash magisk_patched.img) then (fastboot reboot) then i stucked at bootloop and i can't go to fastboot or recovery , Even the pc don't detect my phone, I think its because i downloaded a rom of newer version that i didn't update to it before flashing the patched boot or maybe i typed wrong cmd , Please any help guys there isn't any realme support center in my country, Thanks in advance.
Click to expand...
Click to collapse
did you find soultion of this at now because i also have same problem?
I've done the same thing I accidently typed "fastboot flash recovery magisk_patched.img" and now I cannot get out of the boot loop as there is no way due to messed up recovery + boot. I have been reading about finding and downloading a firmware in zip format that can be flashed with "SP Flash Tool" but when I try I cannot get it to work. The Firmware should be for the Realme 7 5G [RMX2111].
If anyone else can figure it out.... Please help!
martinbrettphilo said:
I've done the same thing I accidently typed "fastboot flash recovery magisk_patched.img" and now I cannot get out of the boot loop as there is no way due to messed up recovery + boot. I have been reading about finding and downloading a firmware in zip format that can be flashed with "SP Flash Tool" but when I try I cannot get it to work. The Firmware should be for the Realme 7 5G [RMX2111].
If anyone else can figure it out.... Please help!
Click to expand...
Click to collapse
It'll be kinda hard. You're gonna have to find a stock ROM - not an OTA update - and you're gonna need to use python to extract the contents from the .OFP file. This should be it. https://firmwarefile.com/oppo-realme-7-5g-rmx2111
basically you can follow this tutorial
the only difference is you have to use realme 7 firmware not C3. this is ofp file for rmx2151 you can extract it with ofp extractor. also I link this guide for RMX2155. its bootloader unlock guide for RMX2155, but you also follow that guide to revive RMX2151 (until step 10 is sufficient, unless you want unlocked bootloader too)
SF Flash tool is a quite useful for flashing/unbrick Mediatek phones. just read instruction more carefully from now
immns said:
basically you can follow this tutorial
the only difference is you have to use realme 7 firmware not C3. this is ofp file for rmx2151 you can extract it with ofp extractor. also I link this guide for RMX2155. its bootloader unlock guide for RMX2155, but you also follow that guide to revive RMX2151 (until step 10 is sufficient, unless you want unlocked bootloader too)
SF Flash tool is a quite useful for flashing/unbrick Mediatek phones. just read instruction more carefully from now
Click to expand...
Click to collapse
good. this for Realme 7 :
- Textguide : https://telegra.ph/Hard-Brick-Fix-for-Realme-7-01-25
hello guys, i'm having a problem here, I just installed a pixel plus ui and then installed the magisk app, then I renamed it to a zip file as mentioned in the website and went to flash it on my phone (Realme 7) after flashing successfully completed I pressed the reboot to system option, now it's stuck on the realme logo and doesn't budge anymore... I'm really worried please help me.
I flashed a Magisk patched A.16 global rom boot to my boot, but I mistakenly didn't add the boot_a code to it making my phone bootloop. I've tried flashing the myogui boot.img again to try fixing it, but it didn't work. I downloaded the A.16 firmware, extracted the OFP, and took the boot.img. I flashed that one in both partitions but it didn't work, my phone is still boot looping.
What can I do to fix this? I'm so confused and angry over this. I just wanted to root my device.
Wrong post sorry
Can you boot to bootloader manually with vol down and power keys?
Then rerun boot.img flash to current partition. Make sure the patched boot.img is for the correct version currently on phone.
If you already tried this, then maybe other files didn't flash right. You can reflash myogui global A.10 and repeat the process
It took me a few tries to get it working. Not sure why but eventually it booted