Database Develop

[Q] Brick Help vs980 LG G2

Currently irate because I already typed all this then hit enter to be told I can only register once from this ip.
Any way...
Rooted vs98027a Android 4.4.2 via Stump Root
Used AutoRec which installed TWRP 2.7.00
Backed up Stock Rom
Mount button is missing
Rebooted into Stock to transfer backup to PC and place "cm-12-20150603-NIGHTLY-vs980.zip" as well as Lp gapps.
Rebooted back into TWRP
Wiped, then Installed the CM Nightly, wiped cache and rebooted.
Stuck in LG Boot loop.
Use buttons to boot back into TWRP, open Restore and It's just a blank navigation window.
TWRP just became ****ing worthless
Tried to wipe and possibly install same CM again. Still boot looping.
Tried getting to download mode, but it reboots before installing driver.
I have not a clue as to what to do next.
I can't get it to mount.
ADB Sideload Fails.
Terminal Command lets me select a blank navigation window.
And my original file structure is in like sdcard/0/0/0/0/0/0/0/0/ etc.
Please help, or at least redeem CM and TWRP's value somehow, because this is bs.

I sort of fixed it.
Restore showed up blank, because within the many /0/0/0/0/0/0/0/0 a new TWRP folder would be made or course containing nothing.
I also learned the adb is this magnificent goddess that can do things even when your phone can't.
Throughout further reading I glimpsed upon something about "loki" files that aren't compatible with specific versions of twrp or something. So If you've also been through this and still feel brave enough to flash a custom, then make sure you get the newest version of twrp...
As for the Restore issue, assuming you have a backup saved on pc, wipe everything then adb push the whole file (TWRP/BACKUPS/BLAHBLAH/BLAUGHESDIHF) to /sdcard/.... then it should show up in restore, if it doesn't then use file manager to place it in the right TWRP directory... You can also use the file manager to move the restore folder to the "correct" twrp folder if you don't have it backed up.

Lost root on Xiaomi Mi A1 after updating to Magisk 19.2

Hello everyone,
So this is the first time i had issue with magisk after the update.
Magisk Manager proposed for me to install new version of Magisk, so i did, after installation finished, it advised to reboot, so i did
After reboot, phone came back up just fine but Magisk was not installed. I tried to download zip 19.2 (19200) from Magisk Manager then installing that zip - also from Magisk Manager, but it would say this:
Code:
- Device platform: arm64-v8a
- Existing zip found
- Copying image to cache
- Unpacking boot image
! Unsupported/Unknown image format
! Installation failed
So now i don't know what do to.
I did notice however, that after the Magisk update, it seem to have installed newest OTA update (with security patches from May), which usually it fails to install, i guess due to unlocked bootloader.
Any help would be greatly appreciated!
EDIT:
Managed to figure it out, it's been a long time since I've done this so i forgot that method I've tried is used to patch boot image, not to install zip file, my bad.
I booted into TWRP and extracted my current boot.img.
Booted back into the system and using Magisk Manager, I've patched the boot.img
Downloaded the magisk_patched.img to PC and from fastboot, flashed the patched boot.img.
Booted back into the system and *BAM*, got my root back!
Magisk is still the best! Thank you!

maretodoric said:
Hello everyone,
So this is the first time i had issue with magisk after the update.
Magisk Manager proposed for me to install new version of Magisk, so i did, after installation finished, it advised to reboot, so i did
After reboot, phone came back up just fine but Magisk was not installed. I tried to download zip 19.2 (19200) from Magisk Manager then installing that zip - also from Magisk Manager, but it would say this:
So now i don't know what do to.
I did notice however, that after the Magisk update, it seem to have installed newest OTA update (with security patches from May), which usually it fails to install, i guess due to unlocked bootloader.
Any help would be greatly appreciated!
EDIT:
Managed to figure it out, it's been a long time since I've done this so i forgot that method I've tried is used to patch boot image, not to install zip file, my bad.
I booted into TWRP and extracted my current boot.img.
Booted back into the system and using Magisk Manager, I've patched the boot.img
Downloaded the magisk_patched.img to PC and from fastboot, flashed the patched boot.img.
Booted back into the system and *BAM*, got my root back!
Magisk is still the best! Thank you!
Click to expand...
Click to collapse
I'm also getting same error how did you managed to find the solution...

maretodoric said:
Magisk Manager proposed for me to install new version of Magisk, so i did, after installation finished, it advised to reboot, so i did
After reboot, phone came back up just fine but Magisk was not installed. I tried to download zip 19.2 (19200) from Magisk Manager.
[...]
Booted back into the system and using Magisk Manager, I've patched the boot.img
Downloaded the magisk_patched.img to PC and from fastboot, flashed the patched boot.img.
Click to expand...
Click to collapse
Similar problem here, but with Magisk 19.3.
Could you pass a link to patched boot image,you used? Can´t find it...
Thanks

I didn't download boot.img, it's best that you extract it yourself by using ADB.
Download adb software, there should be some tutorial here on forums how to find and get it (possibly https://forum.xda-developers.com/mi-a1/how-to/computer-setup-rooting-gcam-setup-t3731526) , but Windows 10 SHOULD natively have it (at least i did, i didn't have to install anything, already had ADB).
Now here comes the tricky part. I didn't remember this and i didn't write it down. When this happens again to me, i will be in huge .......
I'm sorry i can't help you, but try to google for info on how to extract boot.img from current installation using fastboot or adb.. not sure which, possibly fastboot.
Then you will have clean untouched boot.img from official repo. No need to wait for it to appear on xiaomi site.
If i find a tutorial, i will post it here. Please do the same if you find it before me.
GOT IT!!!
- Follow the previous tutorial if you do not have adb and fastboot, so you can install them. There should be plenty of tutorials how to install both of them
- After you installed it, download this version of TWRP https://dl.twrp.me/tissot/twrp-3.3.0-2-tissot.img.html to your desktop
- Connect your phone to your PC via USB cable
- Open command prompt (in Windows, hit CTRL+R then type in cmd)
- Change directory to desktop, for example type cd C:\Users\<username>\Desktop - replace "<username>" with your username ofcourse.
- Type adb reboot bootloader - it will boot to fastboot mode
- Once the phone is in fastboot mode, type fastboot boot twrp-3.3.0-2-tissot.img (keep cmd prompt open)
- It will boot into recovery, click on "Backup"
- Select "Boot"
- Click on Select Storage and there choose Internal Storage, click on OK
- Then on the bottom part of the screen, just swipe to right to extract boot.img (It should literally say "Swipe to Backup"). Pay attention to messages, it will display the directory where it will place the boot.img, but it will not be strictly named boot.img
- In my case, it's in Internal Storage/TWRP/BACKUPS/00bf23cc0904/2019-06-20-14-25-3_PKQ1/boot.emmc.win
You can either rename it to boot.img or just leave that name. But either way, open new magisk manager, select "Install" next to Magisk (not magisk manager), click on "Select and Patch a file", point to your new boot.img or boot.emmc.win.
Magisk will patch that image and show you the new location. Just download that file to your PC, on desktop, cmd again "adb reboot bootloader", and when it gets to fastboot mode, type "fastboot flash boot magisk_patched.img".
You should be good to go!

Moto G7 plus TWRP installation issues/confusion

Hello. Newbie here trying to install TWRP onto my G7+ (xt1965-T, moto not Revlry). I've been following the twrp.me instructions, among others. I've got the bootloader unlocked, adb & fastboot devices both return what they should, I've copied the twrp-3.5.0_9-0-lake IMG & ZIP files to my platform-tools folder and am running powershell from there. I copied the zip file to the internal memory of the phone as well as the ASC file with basic copy/paste commands in windows.
I temporarily boot the TWRP image and try to install the zip file, only to have it fail signature verification. I tried it without sig verification but still failed on some error. I've searched, but I haven't been able to find anything to get me past this.
Confusion comes with conflicting instructions. I see here that there is a method that differs from the instructions linked above, AFIAK.
There is a note on the bottom of the 1st instructions stating " If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest firmware for your device and reflash the boot image." I did ignorantly initially type the command fastboot flash recovery TWRPxxx.img. Would this have anything to do with my issues?
Are there multiple ways to achieve installation of TWRP & something like LineageOS and I'm just getting confused between instructions for each?
Thanks

I just tried to install the zip file without signature verification, and it failed to unpack the image
Updater process ended with ERROR: 1
Error installing zip file '/external_sd/twrp-installer-3.5.0_9-0-lake.zip'
I've downloaded this a couple of times with the same result.

timsch75 said:
I just tried to install the zip file without signature verification, and it failed to unpack the image
Updater process ended with ERROR: 1
Error installing zip file '/external_sd/twrp-installer-3.5.0_9-0-lake.zip'
I've downloaded this a couple of times with the same result.
Click to expand...
Click to collapse
Did you go in to TWRP Advanced and try to sideload TWRP ?

timsch75 said:
Hello. Newbie here trying to install TWRP onto my G7+ (xt1965-T, moto not Revlry). I've been following the twrp.me instructions, among others. I've got the bootloader unlocked, adb & fastboot devices both return what they should, I've copied the twrp-3.5.0_9-0-lake IMG & ZIP files to my platform-tools folder and am running powershell from there. I copied the zip file to the internal memory of the phone as well as the ASC file with basic copy/paste commands in windows.
I temporarily boot the TWRP image and try to install the zip file, only to have it fail signature verification. I tried it without sig verification but still failed on some error. I've searched, but I haven't been able to find anything to get me past this.
Confusion comes with conflicting instructions. I see here that there is a method that differs from the instructions linked above, AFIAK.
There is a note on the bottom of the 1st instructions stating " If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest firmware for your device and reflash the boot image." I did ignorantly initially type the command fastboot flash recovery TWRPxxx.img. Would this have anything to do with my issues?
Are there multiple ways to achieve installation of TWRP & something like LineageOS and I'm just getting confused between instructions for each?
Thanks
Click to expand...
Click to collapse
I fought this same model G7+ (XT1965-T) for several days, trying to install LineageOS for microG. Here are the instructions I used here ....I used the same recovery image (twrp-3.5.0_9-0-lake .img) as you. Download the copy-partitions-20200903_1329.zip from here. To sideload copy-partitions zip in TWRP go to Advanced tab, ADB sideload tab, then I sideloaded lineage-17.1-20210202-microG-lake.zip here.

chuck8812 said:
I fought this same model G7+ (XT1965-T) for several days, trying to install LineageOS for microG. Here are the instructions I used here ....I used the same recovery image (twrp-3.5.0_9-0-lake .img) as you. Download the copy-partitions-20200903_1329.zip from here. To sideload copy-partitions zip in TWRP go to Advanced tab, ADB sideload tab, then I sideloaded lineage-17.1-20210202-microG-lake.zip here.
Click to expand...
Click to collapse

I've regressed. I had previously been ably to temporarily boot into TWRP with the fastboot boot x.img command, at least in windows, but for some reason now it hangs up and will not show the TWRP screen. I had this same issue in Linux, but it worked in Windows, but now it fails the same in both. I run the command above and it shows the typical splash screen that it would if booting the stock android system, but goes no further. Previously, it would flash this , but then go to the TWRP screen. I can't get any feedback from adding the verbose flag to the fastboot command. Any way to track down this problem?
effin 'ell I hate regressions, 'specially the ones that come out of nowhere.
p.s. I don't know what happened with the previous blank post. I was trying to reply in Windows, but it wouldn't let me enter text. I rebooted into Linux for this post, and I see that something got posted previously. I'd delete it if I could.... gremlins

Module brick

I get in a bootloop after a module is installed, pixel-fy soft bricked my phone and I had to reflash my phone. Im using a redmi note10S.
Any fix? Thanks!
Edit : Im testing some things out seeing what bootloops my phone.
Edit : Anything that repacks the boot image, flashes it, changes it, will get stuck on the Redmi screen, first MIUI logo, then redmi after I restart, then it will boot into recovery.
I have to flash, or factory reset, wipe data/calvichk and userdata reset
if it doesnt boot well..

Hope ur device had adb enabled.
Turn off ur phone and type
Code:
adb wait-for-device shell magisk --remove-modules
Now turn on ur phone.
Another method is to goto /data/adb/modules and remove desired folder using custom recovery

Worked! Thanks!

what I always do is to have the patched boot.img somewhere
if that happens I go into recovery mode, then the file explorer /data/adb/modules and delete the last one I installed
that should fix the bootloop in most cases
anyways, it's better to reflash the patched boot.img just in case just after deleting the problematic module

Question Easiest way to just modify etc/hosts.

For digital wellbeing reasons* I'd like to lock myself out a handful of websites by redirecting them to local.
I've tried to follow the guideline using Magisk, only to nearly brick my phone (a friend had to flash the original image). What is the easiest way to simply modify the hosts file without changing too much?
lg lngo

I've been using this Magisk module for a long to block Ads. Just edit etc/hosts and install!

That means you recommend to simply follow this guideline and install Magisk including this plugin?

It may be that the websites you are concerned about are blocked in the hostlist that AdAway would install. If your phone is rooted, consider installing AdAway. I think it can only be installed using F-Droid.

@Rafiul Bari Chowdhury: I edited the hosts file in your zipped module, run it in Magisk: worked fine, after restart I saw the changes (shell cat /etc/hosts). However, after locking it again the device is bricked. I'm looking how to flash the factory image again.
Any ideas what went wrong? Is it not possible to edit root files and relock the phone again so it seems "normal"?
Edit: re-unlocked the phone and it works again. Reset OS (and hosts file), but works. When locked again: "Can't find valid operating system". Any ideas?

Fnokrer said:
@Rafiul Bari Chowdhury: I edited the hosts file in your zipped module, run it in Magisk: worked fine, after restart I saw the changes (shell cat /etc/hosts). However, after locking it again the device is bricked. I'm looking how to flash the factory image again.
Any ideas what went wrong? Is it not possible to edit root files and relock the phone again so it seems "normal"?
Edit: re-unlocked the phone and it works again. Reset OS, but works. When locked again: "Can't find valid operating system". Any ideas?
Click to expand...
Click to collapse
i doubt the phone is bricked. it is either locked up that you can force off by holding down power + vol up + vol down all 3 at the same time for 15 to 30 seconds to force off. you can get into boot loader by power + vol down. then flash the stock image from https://developers.google.com/android/images#barbet
make sure you have the google usb drivers and use chrome installed or nothing work when trying to flash back to stock.
it pretty hard to mess up the bootloader section of the phone. it can be done but you would have to flash a corrupt image to the boot partition.
i use to use adaway https://github.com/AdAway/AdAway/releases/tag/v5.12.0 if i remember right you can modify the host file using that apk

I did id all over again: Flashed latest firmware (barbet-sp2a.220305.012), installed Magisk acc. to Guideline here in the forum. Same result.
Phone wasn't bricked, Boot loader worked fine all the time, sorry for unprecise description. Editing the hosts file simply doesn't last (maybe I have to change the file on partition A and b??!) and 2nd, if locked again the phone won't find the OS.
Gives me two questions:
1.) how actually does the script from Rafiul Bari Chowdhury work, how can it replace the hosts file while I can't do it manually due to read-only partition.
2.) If I change both partitions, A and B, would the change last after I lock the phone again? Then how do I do it and how do I make sure the OS is found.
Is it even possible to change system files and go back into "locked" mode again without any other impacts?

Fnokrer said:
I did id all over again: Flashed latest firmware (barbet-sp2a.220305.012), installed Magisk acc. to Guideline here in the forum. Same result.
Phone wasn't bricked, Boot loader worked fine all the time, sorry for unprecise description. Editing the hosts file simply doesn't last (maybe I have to change the file on partition A and b??!) and 2nd, if locked again the phone won't find the OS.
Gives me two questions:
1.) how actually does the script from Rafiul Bari Chowdhury work, how can it replace the hosts file while I can't do it manually due to read-only partition.
2.) If I change both partitions, A and B, would the change last after I lock the phone again? Then how do I do it and how do I make sure the OS is found.
Is it even possible to change system files and go back into "locked" mode again without any other impacts?
Click to expand...
Click to collapse
did you try adb shell then su ? you can try chmod -R 775 or 777 a file to give full permisions. you probably could get away with just 660 for read and write without execute command. so chmod -R 660 (filename) should allow you to change the file permisions and allow you to write to the file.
as for relocking. i usually leave mine unlocked. i think if you relock it does a verification process of the rom. not sure on that one. maybe a developer can answer that question.

Hey I am trying to figure this out. did OP ever find an answer?
For me, I am on a pixel 5 with android 13, a phone I got from Backmarket. It is an "Unlocked" pixel 5. I thought this would make things easier. According to an article, pixel 5 is "one of the easiest phones to root"
:/
The phone is not A/B, only A
I pulled the magisk image using adb to the file with platform tools
I tried sideloading a hosts file through ADB but I got Error 21.
I have tried rooting the phone with Magisk boot.img but it fails because in Fastboot "Remote: failed to write to partition not found" and in FastbootD there is also an error.
SU is not found when I attempt to use the adb shell. It is Greyed out in the Magisk App
I have mounted the /system with Recovery but then I receive "Remote: no such file or directory"
I am using the most current Platform tools.
Any advice? Really I just want to edit the hosts file

Gnome_chomsky said:
Hey I am trying to figure this out. did OP ever find an answer?
For me, I am on a pixel 5 with android 13, a phone I got from Backmarket. It is an "Unlocked" pixel 5. I thought this would make things easier. According to an article, pixel 5 is "one of the easiest phones to root"
:/
The phone is not A/B, only A
I pulled the magisk image using adb to the file with platform tools
I tried sideloading a hosts file through ADB but I got Error 21.
I have tried rooting the phone with Magisk boot.img but it fails because in Fastboot "Remote: failed to write to partition not found" and in FastbootD there is also an error.
SU is not found when I attempt to use the adb shell. It is Greyed out in the Magisk App
I have mounted the /system with Recovery but then I receive "Remote: no such file or directory"
I am using the most current Platform tools.
Any advice? Really I just want to edit the hosts file
Click to expand...
Click to collapse
Don't do this method...
Once you're rooted with Magisk, open Magisk and go to settings and tap Systemless hosts. This installs the Systemless Hosts module. Then you can just use an app like AdAway (https://f-droid.org/en/packages/org.adaway/) and block the domains you want there.