Related
I bought a LG V35 recently. When I got the phone, I found its rooted already and looks like bootloader is unlocked since the 1st screen shows the warning unlocked messages. See attachments.
After I got into the system, I could see magisk and used root permission without any problem.
I wanted to do a system backup in the customer recovery like twrp or CWM. (I thought it should be there, since phone is rooted) But after I clicked "reboot to recovery" with TaiBackup APP, I could not get into recovery and screen shows "erasing data" and then rebooted. When system was started up again, phone was done a factory reset and magisk did not work any more...(I checked, I still can see the unlocked bootloader messages at that time)
Then I had to send my phone to the seller and got rooted again. I really do not understand how the seller rooted this phone!!
Now I am wondering if I can flash any custom recovery like twrp? I do not see LG V35 in official twrp's support device list. Dare I try the twrp for LG G7 or LG V30 or others?
If I have to try twrp for LG G7, is there anybody knows how to do a recovery backup via ADB beforehand? Anything I can do to minimize the risk?
He probably dumped the boot image with LGUP, and manually patched it with Magisk on another device
crumbling9999 said:
He probably dumped the boot image with LGUP, and manually patched it with Magisk on another device
Click to expand...
Click to collapse
Yes, I searched with google about patching magisk boot img and now I agree with you.
Now, when I trying to install some modules in magisk, I will get "installation failed". See the attachment.
I googled and tried to find the solution. It is said that I could update/re-install the magisk manager apk to solve the problem. But the seller told me DO NOT touch the magisk and even update it.
Do you know if I can update the magisk manager when rooted in the patching boot img way?
Do you know if I can install xposed in the magisk in this case?
Are there some DONTs when rooted in the patching boot img way?
Thanks for your reply.
Mate just start first with a backup via LGUP than check if you can reboot to bootloader. Then read a bit G7 thread and if you are confident in your knowledge and skills continue - it is an easy job to firstly backup your both boot mages, patch them and flash them back to your phone if you have fastboot.
vlad48 said:
Mate just start first with a backup via LGUP than check if you can reboot to bootloader. Then read a bit G7 thread and if you are confident in your knowledge and skills continue - it is an easy job to firstly backup your both boot mages, patch them and flash them back to your phone if you have fastboot.
Click to expand...
Click to collapse
Please tell me how to backup both boot images? Thx
alex.coffen said:
Yes, I searched with google about patching magisk boot img and now I agree with you.
Now, when I trying to install some modules in magisk, I will get "installation failed". See the attachment.
I googled and tried to find the solution. It is said that I could update/re-install the magisk manager apk to solve the problem. But the seller told me DO NOT touch the magisk and even update it.
Do you know if I can update the magisk manager when rooted in the patching boot img way?
Do you know if I can install xposed in the magisk in this case?
Are there some DONTs when rooted in the patching boot img way?
Thanks for your reply.
Click to expand...
Click to collapse
Is there somebody can tell me how to solve the issue that i can not install any module in magisk?
Can i update the magisk framework to 18.1 when the root method is coming from the patching boot image?
Since you have full fastboot, grab a copy of TWRP for the G7 and try booting it. I verified today that laf from the G7 boots just fine on the V35, so TWRP should work until (yes I am being optimistic here) I can get the V35 rooted and build our own TWRP.
In case you are new, the command will be:
Code:
fastboot boot twrp.img
Where twrp.img is whatever the filename of TWRP is. If the touch screen works, and the rest of the functionality is there, you can use that for now. However, you will have to have a PC and fastboot boot it every time you want to get into TWRP.
On SD845 and later devices (which the G7 and V35 have), recovery is no longer a separate partition -- it is included in boot. So, you do NOT want to flash the G7 version because while the G7 kernel may work fine for laf, and TWRP, it probably wouldn't be ideal to use as a system kernel.
Let me know if you have any questions.
I do have a question for you. Where did you get your phone from? I have a hard time believing that there are so many V35s out there with engineering bootloaders -- so I would like to get my hands on one and figure out how they unlocked the bootloader.
-- Brian
runningnak3d said:
Since you have full fastboot, grab a copy of TWRP for the G7 and try booting it. I verified today that laf from the G7 boots just fine on the V35, so TWRP should work until (yes I am being optimistic here) I can get the V35 rooted and build our own TWRP.
In case you are new, the command will be:
Code:
fastboot boot twrp.img
Where twrp.img is whatever the filename of TWRP is. If the touch screen works, and the rest of the functionality is there, you can use that for now. However, you will have to have a PC and fastboot boot it every time you want to get into TWRP.
On SD845 and later devices (which the G7 and V35 have), recovery is no longer a separate partition -- it is included in boot. So, you do NOT want to flash the G7 version because while the G7 kernel may work fine for laf, and TWRP, it probably wouldn't be ideal to use as a system kernel.
Let me know if you have any questions.
I do have a question for you. Where did you get your phone from? I have a hard time believing that there are so many V35s out there with engineering bootloaders -- so I would like to get my hands on one and figure out how they unlocked the bootloader.
-- Brian
Click to expand...
Click to collapse
Thanks for your answers.
I bought this phone from taobao which is a bigest famous online shopping site in China. I do not know how they unlocked the bootloader and tell me if something I can help with.
I unlocked LG G2/G4/oneplus 5T myself so I know the basic knowledges about how to execute ADB command and the normal root process. But I do not know the one using patched magisk boot img way.
As far as I understand, you meant that we can temporarily boot into the G7 twrp to use its functions but we cannot actually flash the twrp to the phone. Booting to G7 twrp image, is it safe? (The "safe" I mean is that, if I encounter problems, at least I still can startup the phone with rooted. Otherwise, I need to send my phone to the seller who is 2000KM away to root it again...Last time I booted into its recovery, all my data was erased...) Anyway, I will try it as you suggested, but I will put it the 2nd priority.
The 1st priority is that, I truely want to solve the problem I met about installing magisk module failed. See my attachment. I want to know if I can fix the problem by updating the magisk framework. I need the "safe" way as I just said.
So if I click "yes" in the 33.jpg I attached, do you know which would happen?
A. brick the phone
B. restart and get a factory reset, then I cannot use root any more
C. nothing changed, still install module failed but root can work
D. Solve the problem and can install module successfully
If you press "Yes" it will just download Magisk setup which will fail doing anything it will reboot to the stock recovery which will perform security check and wipeout magisk from boot image.
To solve your problem and install the module properly you need to patch externally your boot image and and flash it back in fastboot mode overwriting both a and b slots.
So:
1. Dump boot via LGUP download mode.
2. Patch it via Magisk Manager.
3. Flash it back under fastboot mode.
4. Install your module and enjoy...
P.S.: If you are not confident on how to perform any of the listed steps above please do not start it at all because definitely you will need to travel 200 km again for restoring root...
vlad48 said:
If you press "Yes" it will just download Magisk setup which will fail doing anything it will reboot to the stock recovery which will perform security check and wipeout magisk from boot image.
To solve your problem and install the module properly you need to patch externally your boot image and and flash it back in fastboot mode overwriting both a and b slots.
So:
1. Dump boot via LGUP download mode.
2. Patch it via Magisk Manager.
3. Flash it back under fastboot mode.
4. Install your module and enjoy...
P.S.: If you are not confident on how to perform any of the listed steps above please do not start it at all because definitely you will need to travel 200 km again for restoring root...
Click to expand...
Click to collapse
Thanks for explaining. That is what I worry about. Some questions for you:
1. I have used LGUP to dump boot_a and boot_b. (Very slow, took 1 hour. I renamed them to boot_a_org.img and boot_b_org.img, they are no difference with cksum). So this is currently boot images patched by seller? So, no matter what problems I encounter, I can flash boot_a_org.img(boot_b_org.img) back to boot_a and boot_b to recover my phone anytime and still get rooted? If so, I can feel free to do anything no worrying about the 2000KM delivery...
2. You mentioned "Patch it via Magisk Manager". I can directly patch boot_a_org.img to do it? I think boot_a_org.img is already patched by seller. (I do not have the original unpatched and unlocked bootloader img for V35...)
3. "Patch it via Magisk Manager". can only be done in my V35 phone, or it is OK to do it in other phones?
4. Can I try to boot into G7 twrp then I can flash the newest magisk via twrp? In this way I can fix my problem?
Thank you very much in advance.
1. Download LGUP from HERE
(make sure you put it in the right place afterwards: C:\Program Files (x86)\LG Electronics\LGUP)
2. Shut down your phone and then press VOL+ button and connect it via USB cable to your computer (The phone will boot in download mode).
3. Start LGUP.exe and select DUMP mode. DUMP only those partitions (place checkbox):
abl_a
abl_b
boot_a
boot_b
xbl_a
xbl_b
This will finish our backup preparation, so report back once done.
(Also just come to a better idea - compress and upload somewhere your boot_a file I'll try to patch it with latest Magisk and upload it back to you)
vlad48 said:
If you press "Yes" it will just download Magisk setup which will fail doing anything it will reboot to the stock recovery which will perform security check and wipeout magisk from boot image.
To solve your problem and install the module properly you need to patch externally your boot image and and flash it back in fastboot mode overwriting both a and b slots.
So:
1. Dump boot via LGUP download mode.
2. Patch it via Magisk Manager.
3. Flash it back under fastboot mode.
4. Install your module and enjoy...
P.S.: If you are not confident on how to perform any of the listed steps above please do not start it at all because definitely you will need to travel 200 km again for restoring root...
Click to expand...
Click to collapse
Laf has new security that prevents reading for now. LG UP 1.14 and 1.15 can't read .. and I can't find a copy of 1.16.
-- Brian
@runningnak3d maybe you are mixing V40 with V35. Using this DUMP only version of LGUP bootloader unlocked phones are able to dump all (even non kdz partitions) so he will be able to perform this operation.
vlad48 said:
@runningnak3d maybe you are mixing V40 with V35. Using this DUMP only version of LGUP bootloader unlocked phones are able to dump all (even non kdz partitions) so he will be able to perform this operation.
Click to expand...
Click to collapse
This only works for v35 phones with unlocked bootloader?
Yes, I have already dumped those part:
abl_a
abl_b
boot_a ============> I rename this one to boot.img
boot_b
xbl_a
xbl_b
Could you teach me what is each one used for?
So boot.img is currently boot image patched by seller? So, no matter what problems I encounter, I can flash boot.img back to boot_a and boot_b to recover my phone anytime and still get rooted? If so, I can feel free to do anything no worrying about the 2000KM delivery...
You mentioned "Patch it via Magisk Manager". I can directly patch boot.img to do it? I think boot.img is already patched by seller. (I do not have the original unpatched and unlocked bootloader img for V35...)
alex.coffen said:
Yes, I have already dumped those part:
abl_a
abl_b
boot_a ============> I rename this one to boot.img
boot_b
xbl_a
xbl_b
Could you teach me what is each one used for?
So boot.img is currently boot image patched by seller? So, no matter what problems I encounter, I can flash boot.img back to boot_a and boot_b to recover my phone anytime and still get rooted? If so, I can feel free to do anything no worrying about the 2000KM delivery...
You mentioned "Patch it via Magisk Manager". I can directly patch boot.img to do it? I think boot.img is already patched by seller. (I do not have the original unpatched and unlocked bootloader img for V35...)
Click to expand...
Click to collapse
The files I dumped from LGUP are bin file or img file?
I try to patch the boot.img file but everytime I get error. See attachment.
@alex.coffen Yes if you backup your boot image and do not boot into RECOVERY everything will be safe.
It appears your DUMP was not done properly. Please if possible open your boot.img with HEX editor and take a look at it - if there are only 0-es there than it appears something is wrong with your dump.
vlad48 said:
@alex.coffen Yes if you backup your boot image and do not boot into RECOVERY everything will be safe.
It appears your DUMP was not done properly. Please if possible open your boot.img with HEX editor and take a look at it - if there are only 0-es there than it appears something is wrong with your dump.
Click to expand...
Click to collapse
Yes, all 0-es. What should I do? I have already re-installed the USB dirver 4.2.0. See attachment.
Since I failed to use LGUP dump boot img, I think about another way.
I installed termintor on my phone. Under directory /dev/block/bootdevice/by-name, I execute "ls -l" then I can find all partitions, for one example:
boot_a -> /dev/block/sde11
In this case, do you know if I can use "dd if=/dev/block/sde11 of=/storage/emulated/0/Download/boot_a.img" to get the boot img?
@runningnak3d， @vlad48
Since I failed to use LGUP to dump boot img, I think about another way.
I installed termintor on my phone. Under directory /dev/block/bootdevice/by-name, I execute "ls -l" then I can find all partitions, for one example:
boot_a -> /dev/block/sde11
In this case, do you know if I can use "dd if=/dev/block/sde11 of=/storage/emulated/0/Download/boot_a.img" to get the boot img?
@runningnak3d， @vlad48
So after you unlocked the boot loader ( see my previous post)
you can start rooting with magisk manager / patching the boot.img from the original firmware
I used this thread in order to get root ; i modified the contents so it would fit the moto phone a bit better:, but thnx goes to Ibolito over at the pixel 3 forums
1 ) Download the latest Android factory image for your device ("see this guide on where to find it.
2 ) Extract the "boot.img" file from the downloaded image and copy it to your phone.
Warning! Make absolutely sure the firmware is exactly the same as the installed one. If not, you might loose touch.
Be aware that LMSA will download the latest firmware, even if it is not yet installed. That might break your touchscreen
Click to expand...
Click to collapse
3 ) Download latest Magisk Manager application on your phone and install it :
Link
4 )Press on the Install Magisk button (the one on the top, not the Magisk Manager), then Install > Select and Patch a File and now select the Boot.img file you extracted earlier. When the process is done, just put the patched boot.img file on your computer in the same folder as your ADB and FASTBOOT tools, the file's name is magisk_patched.img
edit: i received a comment that the name might be something like Magisk_patched_somerandomletters_.img since the latest magisk update
5 ) Enable adb debugging on your phone and connect it to your computer via USB.
Open a command prompt on your computer and migrate to the folder where the ADB and Fastboot tools are located.
(for exemple, for me it's : cd C:\adb).
7 ) Reboot your phone to fastboot by typing adb reboot bootloader
8 ) Flash the Boot.img you just patched with magisk by typing fastboot flash boot magisk_patched.img
extra: You could test a single boot with that image by typing "fastboot boot magisk_patched.img"
if it boots fine you should have root for this single boot / magisk would show as installed.
9 ) When it's done, reboot by typing fastboot reboot
10 ) Open your Magisk Manager app and check if everything is good, and it should be
extra info:
I did worry a bit because the original boot.img is 64 megs , while the patched version is only 12
but i went with it, and it was fine.
good luck to you all
Edit: rewritten entire post so it would look more like a guide, and extra warning because a lot of people seem to loose touch if they don't have the exact same firmware downloaded as on their phone.
Thanks for posting this. I unlocked my bootloader and would like to root like you did.
Do you install magisk first on your phone, then get the magisk_patched file from your phone? Or is the magisk_patched file obtained somewhere else?
testtubebaby said:
Thanks for posting this. I unlocked my bootloader and would like to root like you did.
Do you install magisk first on your phone, then get the magisk_patched file from your phone? Or is the magisk_patched file obtained somewhere else?
Click to expand...
Click to collapse
You need to install the magisk manager
In magisk manager you can click on "install (magisk)"--> "by patching a file"
then you select the file to be patched ( extracted from the original rom )
after that you can copy the patched file from your phone back to the pc and install it via fastboot.
After that magisk is installed
i hope you succeed
pjottrr said:
You need to install the magisk manager
In magisk manager you can click on "install (magisk)"--> "by patching a file"
then you select the file to be patched ( extracted from the original rom )
after that you can copy the patched file from your phone back to the pc and install it via fastboot.
After that magisk is installed
i hope you succeed
Click to expand...
Click to collapse
The firmware I see is the EU firmware. I don't see the GB firmware in the link you posted (it's RETGB). Any idea where I can find the correct firmware?
Sorry, no idea, i found the provided link via google,
testtubebaby said:
The firmware I see is the EU firmware. I don't see the GB firmware in the link you posted (it's RETGB). Any idea where I can find the correct firmware?
Click to expand...
Click to collapse
https://mirrors.lolinet.com/firmware/moto/sofiar/official/
zuggi_m said:
https://mirrors.lolinet.com/firmware/moto/sofiar/official/
Click to expand...
Click to collapse
@zuggi_m , how does posting the same url help?
i don't see a retgb here ....
Maybe someone with more dev experience can tell if you need the exact same firmware or if the version numbers are the same it is ok to use that file ?
No fastbootd?
One Hyper needs fastbootd in order to flash boot and root
mingkee said:
No fastbootd?
One Hyper needs fastbootd in order to flash boot and root
Click to expand...
Click to collapse
i don't really understand the question i guess,
a magisk patched boot is flashed via fastboot. after that you have magisk installed and root access.
pjottrr said:
i don't really understand the question i guess,
a magisk patched boot is flashed via fastboot. after that you have magisk installed and root access.
Click to expand...
Click to collapse
Yours should be G8 Power (9)
Native Android 10 uses fastbootd to flash boot, dtbo, and recovery
mingkee said:
Yours should be G8 Power (9)
Native Android 10 uses fastbootd to flash boot, dtbo, and recovery
Click to expand...
Click to collapse
maybe i'm missing your point here, my description is just so people who have to figure it out can just use my steps to get root, it is indeed based on fastboot flashing . so i'm not sure what you are trying to say, or am i misinterpreting something?
https://forum.xda-developers.com/motorola-one-hyper/development/rom-omnirom-t4044405
I did root on One Hyper (shipped with Android 10) using fastbootd method
Used old method soft brick my One Hyper
That's why I'd like to know
pjottrr said:
so after you unlocked the boot loader ( see my previous post)
you can start rooting with magisk manager / patching the boot.img from the original firmware
I used this thread in order to get root
you need to download the firmware for our device,
That can be found here;
https://mirrors.lolinet.com/firmware/moto/sofiar/official/RETEU/
after that, extract, patch, fastboot install patched version, done.
I did have some issues with the current magisk manager ( from highonandroid, i did find another source, installed version 7.5.1 of the magisk manager from this source
and that one was able to patch the boot.img
I did worry a bit because the original boot.img is 64 megs , while the patched version is only 12
but i went with it, and it was fine.
good luck to you all
Click to expand...
Click to collapse
There's a head up
US version: Sofia
The rest: Sofiar
I will buy US G Power in May and let's the fun begin
Check out One Hyper general to install Dolby Atmos and it can be toggle on/off.
Has anyone tried copying something to the root of the phone or making build.prop edits? I have the Stylus and have achieved root using the same method, however there is something not quite right with the permissions. I cannot make changes to any root files.
CCivale said:
Has anyone tried copying something to the root of the phone or making build.prop edits? I have the Stylus and have achieved root using the same method, however there is something not quite right with the permissions. I cannot make changes to any root files.
Click to expand...
Click to collapse
So you should know G Stylus ROM is Sofiap.
Be aware the way Android 10 flashing is different.
Download and install the latest ADB in order to access fastbootd (fastboot reboot fastboot) and flash boot, recovery, dtbo, vbmeta, and super
Hmmmm, I will have to read more about fastbootd in your other thread.
I did use the boot.img for the sofiap.
Hello,
I followed all the instructions in the first post and was able unlock the bootloader, install magisk, and use it to make the magisk_patched.img file from a boot.img file.
The only variation, was that I got my boot.img file from mirrors.lolinet.com/firmware/moto/sofia/official/RETUS/XT2041-4_SOFIA_RETUS_10_QPM30.80-13-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip since my phone is a US retail model.
After flashing, the phone boots up properly but the touchscreen does not work.
The side buttons do work and I was able to reboot into recovery. In recovery, the build on the phone is indicated as QPM30.80-51. The build in the above indicated file is QPM30.80-13-2. Could this be the source of the problem?
I have tried flashing the original boot.img (from the file above) back and the touchscreen still does not work. I have also tried “wipe data/factory reset” in recovery.
hazd said:
Hello,
I followed all the instructions in the first post and was able unlock the bootloader, install magisk, and use it to make the magisk_patched.img file from a boot.img file.
The only variation, was that I got my boot.img file from mirrors.lolinet.com/firmware/moto/sofia/official/RETUS/XT2041-4_SOFIA_RETUS_10_QPM30.80-13-2_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip since my phone is a US retail model.
After flashing, the phone boots up properly but the touchscreen does not work.
The side buttons do work and I was able to reboot into recovery. In recovery, the build on the phone is indicated as QPM30.80-51. The build in the above indicated file is QPM30.80-13-2. Could this be the source of the problem?
I have tried flashing the original boot.img (from the file above) back and the touchscreen still does not work. I have also tried “wipe data/factory reset” in recovery.
Click to expand...
Click to collapse
maybe try with the "correct" firmware? ( not sure if the minor diference changes anything, but you could try....
i found it here:
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
pjottrr said:
maybe try with the "correct" firmware? ( not sure if the minor diference changes anything, but you could try....
i found it here:
rsdsecure-cloud.motorola.com/download/SOFIA_RETAIL_QPM30.80-51_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Thanks for finding this link.
Unfortunately i am not able to download this for some reason. I get an access denied error message.
edit:
I was able to find the most recent firmware here:
github.com/AndroidDumps/motorola_sofia_dump/tree/sofia_retail-user-10-QPM30.80-51-bd0b4-release-keys
I downloaded just the boot.img file and flashed it. That fixed the touchscreen issue. I then used magisk to batch the boot.img and I now have root.
Just to be clear, this worked on a US retail moto g power purchased unlocked from best buy. The phone model number is XT2041-4.
Hope this helps.
hazd said:
Thanks for finding this link.
Unfortunately i am not able to download this for some reason. I get an access denied error message.
edit:
I was able to find the most recent firmware here:
github.com/AndroidDumps/motorola_sofia_dump/tree/sofia_retail-user-10-QPM30.80-51-bd0b4-release-keys
I downloaded just the boot.img file and flashed it. That fixed the touchscreen issue. I then used magisk to batch the boot.img and I now have root.
Just to be clear, this worked on a US retail moto g power purchased unlocked from best buy. The phone model number is XT2041-4.
Hope this helps.
Click to expand...
Click to collapse
I downloaded the kernel and waiting for the unit.
I can flash full ROM with fastboot and fastbootd, but just flashing kernel would be much faster.
Moreover, check One Hyper general to get Dolby Atmos because you can turn on and off anytime you want.
Alexenferman is not responsible for any damages or bricks made to your device. Please do some research if you have any concerns about rooting, its features and downsides. You are choosing to make these modifications, you should blame yourself for any mistakes you make.
Rooting may require a factory reset, please backup your data. Rooting will void your device warrany. By rooting your device, you will not be able to install OTA updates on your phone.
US carrier specific devices such as Verizon and Sprint might not be bootloader unlockable, therefore, not rootable.[/B]
You will need:
Platform Tools (Download from here)
Motorola Drivers
Windows or Linux PC
Bootloader Unlocked Moto E 2020
Your phone must be bootloader unlocked. Rooting your phone and not unlocking the bootloader will result in a soft brick.
Download the latest Magisk Manager APK from Github: https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.0/MagiskManager-v8.0.0.apk
Install the APK file. Make sure to enable "Unknown Sources" in the Settings app
Patching the boot image
To retrieve the boot image in order to patch it, you will need to download the stock ROM for your specific variant.
Download the ROM from your variant from here: https://mirrors.lolinet.com/firmware/moto/ginna/official/
To check which region is your device, go to Settings > About Phone > Software Channel.
After downloading, open the ROM zip file with an archive manager.
Extract the boot.img file only.
Transfer the boot.img file on your phone.
On your phone, open the Magisk app.
Select "Install" > "Install" > "Select and Patch a File"
Locate the boot image in the internal storage on your phone. Select the boot.img file.
Transfer the magisk_patched.img file on your computer.
Rooting the device
Boot the device into fastboot mode by holding the [Volume Down] and [Power] buttons.
Connect your phone to your PC.
On your PC, open a fastboot console window.
Type:
Code:
fastboot devices
Your phone serial number should be displayed along with the word "fastboot" or "device" in the console.
Now, type the following commands:
Code:
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
Replace patched_boot.img with the path to your boot image we patched previously.
To reboot the device, type:
Code:
fastboot reboot
Once the device rebooted, open the Magisk app.
If you see the "Magisk is installed" message, you have successfully rooted your device!
You are done!
To view instructions with images, follow these instructions: https://www.alexenferman.com/articles/MotoE2020/root-moto-e-2020-magisk
I can confirm this works, I was about to give up on root or TWRP until I saw this. I'm now rooted, but I still can't find a download link for the latest TWRP for the Ginna model.
Hypercore said:
I can confirm this works, I was about to give up on root or TWRP until I saw this. I'm now rooted, but I still can't find a download link for the latest TWRP for the Ginna model.
Click to expand...
Click to collapse
Me neither, can anyone provide a TWRP for ginna?
I eventually found it after a ton of digging. I've uploaded it to my drive to assure the link stays active for anyone else who may need it.
For peace of mind, here's the VirusTotal scan HERE.
And here is the link to twrp-3.4.0-10_0-ginna HERE.
Hypercore said:
I eventually found it after a ton of digging. I've uploaded it to my drive to assure the link stays active for anyone else who may need it.
For peace of mind, here's the VirusTotal scan HERE.
And here is the link to twrp-3.4.0-10_0-ginna HERE.
Click to expand...
Click to collapse
Confirmed working. Tyvm!
Before I brick my phone. Can anyone confirm if the Tracphone version XT2052DL is rootable?
I'd like to know, too. Can we root our Tracfone XT2025DLs? Anyone successful?
dragonfire0501 said:
Before I brick my phone. Can anyone confirm if the Tracphone version XT2052DL is rootable?
Click to expand...
Click to collapse
Ranthalion75 said:
I'd like to know, too. Can we root our Tracfone XT2025DLs? Anyone successful?
Click to expand...
Click to collapse
I have one too and I've tried to unlock the bootloader however Motorola's website says the bootloader for this phone is not unlockable. It seems like this is what's preventing me from being able to install a different firmware like the stock one or root the device.
I do not know if there is any sort of workaround for this
For some reason on a Moto E, after rescuing using the Moto rescue assistant and then using
you guys can also use OFox Recovery and swipe magisk to root
Thank you. I used this guide to root my Moto E
QPGS30.82-135-2_Root.img
This method works well for QPGS30.82-135-2, but I just attempted it with QPGS30.82-135-9 and unfortunately the Magisk patched boot image will not work. I tried it 3 times, re-patching boot image each time. I suppose Motorola updated something in android to block this?
i can't get this to work at all, i cannot find a matching stock firmware being qpg30.82-135, there's no extra S and nothing else after the 135, got this phone from my motorola insiders rewards and now it's bootlooping after trying the 135-2 patched image
Has anyone been able to root and hopefully install a custom recovery on the lastest update? Mine is QPGS30.82-135-14, and so far I've only been able to get orangefox to boot but couldn't get it to decrypt my storage or install magisk. I tried twrp first, but to no avail, touch screen still doesn't work on it, so now I'm asking on a few different threads for this phone lol. Any help would be great!
Do you know of an updated method to get it to flash correctly? I was able to boot into ofox, but couldn't get it to properly flash. Ended up stuck on a screen that said my phone was unlocked and couldn't be trusted and that it'll reboot in 5 seconds. I don't know much about ofox either, been using twrp for years lol, it looks too different. Anyhow, any help would be appreciate much!
ace120ms said:
you guys can also use OFox Recovery and swipe magisk to root
Click to expand...
Click to collapse
You have to fastboot boot it anyway I don't have this phone anymore so idk
bouyakasha said:
This method works well for QPGS30.82-135-2, but I just attempted it with QPGS30.82-135-9 and unfortunately the Magisk patched boot image will not work. I tried it 3 times, re-patching boot image each time. I suppose Motorola updated something in android to block this?
Click to expand...
Click to collapse
I have the same problem with QPGS30.82-135-9. I can't get it to boot after Magisk patched boot image.
Hi forum readers,
I think about buying an A32 4G (SM-A325FZKGEUB). In two threads here it was mentioned that rooting was successful. But how about twrp? I found an article on unofficialtwrp.com with description and download of an unofficial twrp and vbmeta.img with another tool for also unencrypting the data partition.
1) With all previous phones I only used xda stuff. What do you think, is it safe to use unofficial twrp?
2) If that twrp fails, I think it is possible to get the original recovery back using Odin. Correct?
3) Is it safe to use the vbmeta.inf and tool to unencrypt the data? I don't need Knox and also not Safety Net. Would it be possible to revert to factory status using Odin?
4) Ist necessary to unlock the bootloader for only flashing the Magisk-patched boot image? How about encrypted data?
Many Greetings
Florian
To root you need bootloader unlocked, if it isn't your phone will fail to flash and it will boot on EDM. If twrp fails you can always flash a .tar as AP containing only recovery.img
@ZModder, thank you for your hint. I was already successfully unlocking and installing Magisk 23. Because of your hint I dared to flash TWRP from the above mentioned web site. It didn't boot. But I could successfully return to original recovery. So waiting for a real device specific TWRP.
fbalder18 said:
@ZModder, thank you for your hint. I was already successfully unlocking and installing Magisk 23. Because of your hint I dared to flash TWRP from the above mentioned web site. It didn't boot. But I could successfully return to original recovery. So waiting for a real device specific TWRP.
Click to expand...
Click to collapse
how did you install Magisk? could you tell?
kkintr0 said:
how did you install Magisk? could you tell?
Click to expand...
Click to collapse
1st: Download appropriate firmware for your region and version of Samsung.
2nd: Unlock your bootloader. This will wipe your data.
3rd. Download magisk manager from github.
4th. Open Magisk and check what Ramdisk says.
4th: Extract your downloader firmware. There should be AP.... File. Open it via 7zip. Inside there you should have boot.img.lz4. Extract that file. If Ramdisk Says NO. Do the same with recovery file.
5th: Zip your boot file to tar format and place it on your phone.
6th: Open Magisk. and Press first Install Button.
7th: Press Select and Patch File. Magisk should create a new file inside Downloads folder. Called magisk..patched...etc Insert that file inside your pc. Do the same with recovery file if needed.
8th. Get into Download mode. You can do this by first turning off your phone and pressing both volume keys as you insert your usb cable.
9th: Open Odin File. If you have recovery file uncheck autoreboot. Place your patched file inside AP section.
10th: Reboot your phone and wipe your data.
11th: Volia!
I just got into rooting and was watching a tutorial but got stuck on a command.
"fastboot recovery c:\motorola-flash.img"
err: "cannot load c:\motorola-flash.img since isnt file or directory"
Now i'm trying Iroot/VRoot but it says "not in support mode".
Could i get some help here?
Android 10 btw
(im on the bootloader, it was like a tutorial on unlocking it and so on)
please take care what you type. the above cmd is invalid. bootloader is unlocked already or not?
alecxs said:
please take care what you type. the above cmd is invalid. bootloader is unlocked already or not?
Click to expand...
Click to collapse
unlocked now, it keeps saying "Bad key" tho and TWRP isn't working when i try flashing it.
I'm gonna try installing Lineage OS.
Bad key is normal, you can find images to replace that image with other bin files on this forum.
Bad key = bootloader unlocked.
TWRP, I could never install.
I could never root stock & instead had to install SK experience rom after unlocking. SK is rooted.
If you want to root stock ROM, i recommend to use Magisk 25.2 Delta 5, i will attach it to you, then you need an boot.img of your rom, put magisk apk and boot.img into internal or external storage, patch it with magisk, then put magisk patched boot.img into your pc to fastboot folder and flash it into A and B slots
On Custom ROMs you only do need an flashable zip of Magisk then flash it