Hi, I am reading that TWRP will not even work with this device, I keep getting a fail every time I try to install it. I have the US Beckham model T1929. I see that Magisk can be installed with TWRP, but there are no details on how this is done. I am kind of rusty and have not done any rooting since I got my moto G5 a couple of years ago.
So I quick walk through would be awesome. I would love to get this phone ready to go and put my sim in it, but for now I wait.
I tried to do the systemless install, from the magisk manager and got this error in my log.
- Copying image to cache
- Device platform: arm64-v8a
- Existing zip found
- Extracting files
MagiskBoot v18.0(18000) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
- Unpacking boot image
No boot image magic found!
! Unable to unpack boot image
! Installation failed
Click to expand...
Click to collapse
I guess I did not understand, you can run the TWRP image but can't install TWRP.
I will try this tomorrow.
https://forum.xda-developers.com/z3-play/how-to/official-twrp-moto-z3-play-released-t3848414
TWRP should be booted on A/B phones, a separate installer can inject it (not available yet).
Edit: The non-VZ Z3 can use Magisk.
After unlocking the BL you can do "fastboot boot twrpfile.img". Do not use fastboot flash. You've been warned.
Ace42 said:
TWRP should be booted on A/B phones, a separate installer can inject it (not available yet).
Edit: The non-VZ Z3 can use Magisk.
After unlocking the BL you can do "fastboot boot twrpfile.img". Do not use fastboot flash. You've been warned.
Click to expand...
Click to collapse
I tried to use the fastboot boot twrpp.img and got an error?
C:\Program Files (x86)\ClockworkMod\Universal Adb Driver>fastboot boot twrp-3.2.3-1-beckham.img
Downloading 'boot.img' OKAY [ 0.846s]
booting (bootloader) permission denied!
FAILED (remote: '')
Finished. Total time: 1.106s
Click to expand...
Click to collapse
Finally got it, I had to get the bootloader unlock code from Motorola, funny I did not see a mention of this anywhere. Good thing it was not my first Moto, and I had a vague idea that I might need the code.
Thanks for the help, and hopefully this will help someone else.
Use this link https://support.motorola.com/us/en/solution/MS87215
Droid_Nut said:
Finally got it, I had to get the bootloader unlock code from Motorola, funny I did not see a mention of this anywhere. Good thing it was not my first Moto, and I had a vague idea that I might need the code.
Thanks for the help, and hopefully this will help someone else.
Use this link https://support.motorola.com/us/en/solution/MS87215
Click to expand...
Click to collapse
Great that you could do it . Usually that error appears when BL is locked.
I'm trying the same but on a Z3 (messi XT1929-15). Booting TWRP goes fine, but for any reason I'm having bootloop after flashing Magisk v18, I think it could have to do with encripted data partition..
Could you finally install Magisk? If so, could you please share the steps you did?
Thanks!
Matiascx said:
Great that you could do it . Usually that error appears when BL is locked.
I'm trying the same but on a Z3 (messi XT1929-15). Booting TWRP goes fine, but for any reason I'm having bootloop after flashing Magisk v18, I think it could have to do with encripted data partition..
Could you finally install Magisk? If so, could you please share the steps you did?
Thanks!
Click to expand...
Click to collapse
If you made it to TWRP, you are almost there, you must have the magisk.zip downloaded to your phone, then you install it with install through TWRP. When its all done perform clear cache and delvik cache, and reboot. I only root every couple of years when I get a new phone, so I am not a wealth of knowledge, but I am a survivor. Only thing I ever perma bricked was a cheap tablet and a Sony SW3. You might want to be sure that you have no security locks on you phone, such as fingerprint, pin, etc.
I have a beckham Z3, so not the same version as you.
Damn.
My Moto Z3 doesn't qualify for bootloader unlock. That's a shame because my old Shamu qualified 2 days after I signed on with a contract. :/
I successfully rooted mine after updated to Pie, and flashed boot.img patched with Magisk
Shadow Death said:
Damn.
My Moto Z3 doesn't qualify for bootloader unlock. That's a shame because my old Shamu qualified 2 days after I signed on with a contract. :/
Click to expand...
Click to collapse
I want to root my moto z play without computer which application to use, please thanks
mingkee said:
I successfully rooted mine after updated to Pie, and flashed boot.img patched with Magisk
Click to expand...
Click to collapse
Moto Z3 Play LOST IMEI'S AND MAC WIFI NUMBERS;
and now ?:rolar os olhos:
Shadow Death said:
Damn.
My Moto Z3 doesn't qualify for bootloader unlock. That's a shame because my old Shamu qualified 2 days after I signed on with a contract. :/
Click to expand...
Click to collapse
I just went through this, over and over it kept telling me my phone wasn't eligible but I knew better. For me it was the spaces.
.Try Pasting it into notepad first, remove spaces, then copy and past it.
---------- Post added at 03:27 PM ---------- Previous post was at 03:22 PM ----------
Anyone know how to cover the Bootloader unlocked warning? On Z2-play you could flash a logo file. does that work on Z3?
thanks.
I'm having a problem rooting my Z3 Play with Magisk. My procedure:
1. unlocked the bootloader after getting the code from Motorola (success)
2. downloaded the firmware image from lolinet and extracted boot.img (success)
3. patched boot.img in Magisk Manager and got magisk_patched.img, then copied it to my iMac (success)
4. booted the phone to fastboot mode, ran "fastboot flash boot magisk_patched.img" and got this output (looks normal, not sure about the "is-logical:boot_a:not found" part):
(bootloader) is-logical:boot_a: not found
Sending 'boot_a' (24421 KB) OKAY [ 0.808s]
Writing 'boot_a' OKAY [ 0.713s]
Finished. Total time: 1.524s
5. rebooted phone, Magisk Manager says "Magisk is not installed". Phone otherwise behaves normally.
Any suggestions?
Mcdan333 said:
I'm having a problem rooting my Z3 Play with Magisk. My procedure:
1. unlocked the bootloader after getting the code from Motorola (success)
2. downloaded the firmware image from lolinet and extracted boot.img (success)
3. patched boot.img in Magisk Manager and got magisk_patched.img, then copied it to my iMac (success)
4. booted the phone to fastboot mode, ran "fastboot flash boot magisk_patched.img" and got this output (looks normal, not sure about the "is-logical:boot_a:not found" part):
(bootloader) is-logical:boot_a: not found
Sending 'boot_a' (24421 KB) OKAY [ 0.808s]
Writing 'boot_a' OKAY [ 0.713s]
Finished. Total time: 1.524s
5. rebooted phone, Magisk Manager says "Magisk is not installed". Phone otherwise behaves normally.
Any suggestions?
Click to expand...
Click to collapse
same here. any tips? I had root before, but a magisk/xposed update made me lose root status, and haven't been able to root it again ever since!
saaber.shoyeb said:
same here. any tips? I had root before, but a magisk/xposed update made me lose root status, and haven't been able to root it again ever since!
Click to expand...
Click to collapse
Hmm, that is interesting. Did you try going back to the previous version of Magisk that actually worked? Do you remember what version it was? Maybe I'll try that.
saaber.shoyeb said:
same here. any tips? I had root before, but a magisk/xposed update made me lose root status, and haven't been able to root it again ever since!
Click to expand...
Click to collapse
I think it's the A/B slot things. Possibly, you're installing on the wrong slot. Maybe "b" is active, when "a" was before?
kewlzter said:
I think it's the A/B slot things. Possibly, you're installing on the wrong slot. Maybe "b" is active, when "a" was before?
Click to expand...
Click to collapse
New information: magisk is actually installed, and magiskd is running as root, but something is wrong with the permissions. From an ADB shell,
beckham:/ $ ps -A|grep magisk
root 1060 1 19356 1480 0 0 S magiskd
beckham:/ $ magisk -c
20.3:MAGISK (20300)
beckham:/ $ magisk --list
su
resetprop
magiskhide
130|beckham:/ $ magisk su ls
Permission denied
13|beckham:/ $
Mcdan333 said:
New information: magisk is actually installed, and magiskd is running as root, but something is wrong with the permissions. From an ADB shell,
beckham:/ $ ps -A|grep magisk
root 1060 1 19356 1480 0 0 S magiskd
beckham:/ $ magisk -c
20.3:MAGISK (20300)
beckham:/ $ magisk --list
su
resetprop
magiskhide
130|beckham:/ $ magisk su ls
Permission denied
13|beckham:/ $
Click to expand...
Click to collapse
Problem solved! In the Magisk Manager app settings, I had storage set to use the SD card. When I switched it to internal storage, magisk works fine now!
kewlzter said:
I think it's the A/B slot things. Possibly, you're installing on the wrong slot. Maybe "b" is active, when "a" was before?
Click to expand...
Click to collapse
i tried flashing the A/B partitions copy zip from twrp, tried flashing magisk.zip (different versions), tried the boot.img (patched both from pc and twrp), magisk app & terminal show no root status.
Google Pay, however, insists that my phone is rooted, so it won't work on my device. Certain other apps still have root privileges!
Update: success flashing magisk 17.0 from twrp-3.3.1-v4-z3p-SEPT.img... but updated magisk from the manager right now (direct install), and hit reboot: phone says "factory reset..." and now waiting for it to come back up again...
Related
Hola Party People,
I'm sorry, but what I am missing here, my device isn't rooted per Root Checker, WHY?
I've unlocked the boot loader, it's now saying *unlocked and tampered* Twrp openrecovery-twrp-2.7.1.0-m7.img has been added to my fastboot folder, even though the .img file never unzipped in my WinRaR, however still boots up on the phone. I've installed super user removed it and have tried the other SU, but after all of this, I'm still not ROOTED, per root checker? Why is this, and what am I missing? I feel like it's something super tiny, and i'm so close but yet so far! Do I need to make it S-OFF? Do I need to throw the phone out of the window? I
I don't want to use the toolkit since I like putting in the commands, and I've already done all of this work. I have the HTC ONE T Mobile PN07130. Please someone wave their magic wand and tell me what i'm missing, because I feel like i'm so close. I"M JUST TRYING TO TETHER, and I"m loosing my hair over this. Oh, did I mention that I'm a noob and joined this forum for the help of my comrades.
DeviceJunkie said:
Hola Party People,
I'm sorry, but what I am missing here, my device isn't rooted per Root Checker, WHY?
I've unlocked the boot loader, it's now saying *unlocked and tampered* Twrp openrecovery-twrp-2.7.1.0-m7.img has been added to my fastboot folder, even though the .img file never unzipped in my WinRaR, however still boots up on the phone. I've installed super user removed it and have tried the other SU, but after all of this, I'm still not ROOTED, per root checker? Why is this, and what am I missing? I feel like it's something super tiny, and i'm so close but yet so far! Do I need to make it S-OFF? Do I need to throw the phone out of the window? I
I don't want to use the toolkit since I like putting in the commands, and I've already done all of this work. I have the HTC ONE T Mobile PN07130. Please someone wave their magic wand and tell me what i'm missing, because I feel like i'm so close. I"M JUST TRYING TO TETHER, and I"m loosing my hair over this. Oh, did I mention that I'm a noob and joined this forum for the help of my comrades.
Click to expand...
Click to collapse
are you flashing superSU in TWRP or how are you installing it?
you never mention actually flashing recovery just putting it in the fastboot folder
I'm Dumb
clsA said:
are you flashing superSU in TWRP or how are you installing it?
you never mention actually flashing recovery just putting it in the fastboot folder
Click to expand...
Click to collapse
You are correct Senor Member clsA - I'm on the phone in fastboot, I boot into Recovery - While in Twrp I download/ go to thesuperuser file from the Twrp install button, then swipe across for the installation.Once that is completed, I reboot system and check to see if the AP is installed. It is. Prior to doing that, I moved over the Super user file the fastboot folder on the computer into the internal storage so that it would be available in the twrp software.
Also - Did I mentioned that Spain is getting their gluts kicked once again, but this time it's by Chile? COME ON ESPANA -
DeviceJunkie said:
You are correct Senor Member clsA - I'm on the phone in fastboot, I boot into Recovery - While in Twrp I download/ go to thesuperuser file from the Twrp install button, then swipe across for the installation.Once that is completed, I reboot system and check to see if the AP is installed. It is. Prior to doing that, I moved over the Super user file the fastboot folder on the computer into the internal storage so that it would be available in the twrp software.
Also - Did I mentioned that Spain is getting their gluts kicked once again, but this time it's by Chile? COME ON ESPANA -
Click to expand...
Click to collapse
did you start superSU on the phone ? did it prompt you for an update ?
Che che Check it out
clsA said:
did you start superSU on the phone ? did it prompt you for an update ?
Click to expand...
Click to collapse
I did good sir - After downloading from twrp - I rebooted the system, and checked to see if SU was on the phone, and it was, so I opened it, but nothing happened, not upate request I mean. When I look in the changelog it seems that I have the updated version. I go to Root Check Basic and it says in red Sorry! This device does not have proper root access, then the phone grows a arm and hand then slaps me across the face.
DeviceJunkie said:
I did good sir - After downloading from twrp - I rebooted the system, and checked to see if SU was on the phone, and it was, so I opened it, but nothing happened, not upate request I mean. When I look in the changelog it seems that I have the updated version. I go to Root Check Basic and it says in red Sorry! This device does not have proper root access, then the phone grows a arm and hand then slaps me across the face.
Click to expand...
Click to collapse
maybe another bug with TWRP 2.7
try flashing 2.6.3.3 and try again
http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot
Kinda hot in these Rhinos
clsA said:
maybe another bug with TWRP 2.7
try flashing 2.6.3.3 and try again
ALLLLLLLLLLLLLRIIIGHTTTY THEN -
So I tried again - I now have the aforementioned TWRP on my phone and superuser - Still not rooted properly per Root checker- However couple things changed this time around.
I tried again but this time with SuperSU, with the newer TWRP. The first thing that changed was that my command screen was different. Instead of saying the normal
"""" \Users\Documents\OneDr
t flash recovery openrecovery
target reported max download
sending 'recovery' (9184 KB).
OKAY [ 1.162s]
writing 'recovery'...
OKAY [ 0.715s]
finished. total time: 1.882s "" it said the below -
Users\\Documents\OneDrivers_Fastboot\OneDrivers_Fastboot\Fastb
t recovery flash
usage: fastboot [ <option> ] <command>
commands:
update filename> reflash device from update
flashall flash boot + recovery + sy
flash <partition> [ filename ] write a file to a flash pa
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader varia
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloa
help show this help message
This led me to believe that it was going to work this time around with the SuperSU - However when I got back into TWRP and installed the SuperSU and booted the phone the SuperSU gave me a "binary error code" I forgot the exact working, but it said that "this was a problem" So I went through the process again, with TWRP this time again with SuperUser , but still not root and the command didn't have the newer flash information. I'm so close I can feel it! any thought amigos - that means friend in spanish. Oh and Crotia beating Cameron 4-0 is just pathetic - Okay then bye bye now.
Click to expand...
Click to collapse
Hello ALL
Any feedback from the many experience developers out there. Can you please let me know what Im missing?
Install suprsu 1.93
I picked up a BLU R2 LTE (16g/2GB version) for dirt, Build: BLU_R0170WW_V7.0.04.01. Is it even remotely possible to unlock and root this thing or am I stuck with a bone stock android?
DaGoo_Balls said:
I picked up a BLU R2 LTE (16g/2GB version) for dirt, Build: BLU_R0170WW_V7.0.04.01. Is it even remotely possible to unlock and root this thing or am I stuck with a bone stock android?
Click to expand...
Click to collapse
It apparently is.
https://forum.xda-developers.com/r1-hd/development/unofficial-lineageos-14-1-t3689435/post75020813
Thanks. Looks like I have plans for NYE
I managed to root the phone by unlocking the bootloader with fastboot, then using Magisk in conjunction with the boot image file dumped by ipdev in this post.
Unlock your bootloader by running
Code:
fastboot oem unlock
Copy the blur2-boot.img file available here to your phone.
Install Magisk Manager, then generate a patched version of the blur2-boot.img file using the app.
Copy the patched version back to your computer and flash it to the boot partition with
Code:
fastboot flash boot /path/to/patched_boot.img
After this you should have root via the Magisk Manager app.
somed4ze said:
I managed to root the phone by unlocking the bootloader with fastboot, then using Magisk in conjunction with the boot image file dumped by ipdev in this post.
Unlock your bootloader by running
Copy the blur2-boot.img file available here to your phone.
Install Magisk Manager, then generate a patched version of the blur2-boot.img file using the app.
Copy the patched version back to your computer and flash it to the boot partition with
After this you should have root via the Magisk Manager app.
Click to expand...
Click to collapse
You would be better off to patch my boot image and fastboot boot it.
Then backup your boot image, patch it with magisk, and flash that one back to the device.
Code:
adb shell su -c "dd if=/dev/block/mmcblk0p7 of=/sdcard/blur2-boot.img"
This keeps things clean, just incase you are using a boot image that is different from your own device. Plus you have a "stock" boot image backup if you ever need it.
Not a bad idea to grab recovery also.
Code:
adb shell su -c "dd if=/dev/block/mmcblk0p8 of=/sdcard/blur2-recovery.img"
Sent from my ford using XDA Labs
BLU R2 LTE files. Link
somed4ze said:
I managed to root the phone by unlocking the bootloader with fastboot, then using Magisk in conjunction with the boot image file dumped by ipdev in this post.
Unlock your bootloader by running
Code:
fastboot oem unlock
Copy the blur2-boot.img file available here to your phone.
Install Magisk Manager, then generate a patched version of the blur2-boot.img file using the app.
Copy the patched version back to your computer and flash it to the boot partition with
Code:
fastboot flash boot /path/to/patched_boot.img
After this you should have root via the Magisk Manager app.
Click to expand...
Click to collapse
Does it matter if I get the 1gb ram/16gb flash or 2gb ram/32gb flash, or will this work on both? I was planing on ordering this one. Thanks!
bobsmithy said:
Does it matter if I get the 1gb ram/16gb flash or 2gb ram/32gb flash, or will this work on both? I was planing on ordering this one. Thanks!
Click to expand...
Click to collapse
The size of memory "shouldn't" matter.
Braunish said:
Hi there, am trying to root this phone also. Stumbled upon your thread and had a question. If I take the 3 image files (recovery, boot, system) that are included at mediafire site (that you included in your post) and replace the same 3 image files in stock rom, would that work to root the phone? Thank you for any help, I've tried kingoroot, kingroot, and framaroot to no avail.
Click to expand...
Click to collapse
Read back few post on this thread. They discuss successful root method.
Basically unlock bootloader and use majisk manager to patch boot.img and flash patched image with fastboot.
Root R2 Plus w/ BLU R0190WW V7.0.04.01 GENERIC 11-02-2018
DaGoo_Balls said:
Thanks. Looks like I have plans for NYE
Click to expand...
Click to collapse
Hi there, I recently got a Blu R2 Plus and am aiming to root. I used the boot-sign.img that came with that ROM version in title (9447 KB) when patching with Majisk Manager and came up with a patched file of 9.57 MB size. Is there a way to test this ROM, or can you verify that is the same sizes you dealt with when you went through this process. Thank you for any information. It took me a while and a factory reset before I could get majisk manager installed to patch the correct boot-sign.img file.
Hi There copy img file to where on phone
To where do I copy the image file on the phone that gets "patched" by Majisk?
"Copy the blur2-boot.img file available here to your phone."
Thank you very much,
Michael
somed4ze said:
I managed to root the phone by unlocking the bootloader with fastboot, then using Magisk in conjunction with the boot image file dumped by ipdev in this post.
Unlock your bootloader by running
Code:
fastboot oem unlock
Copy the blur2-boot.img file available here to your phone.
Install Magisk Manager, then generate a patched version of the blur2-boot.img file using the app.
Copy the patched version back to your computer and flash it to the boot partition with
Code:
fastboot flash boot /path/to/patched_boot.img
After this you should have root via the Magisk Manager app.
Click to expand...
Click to collapse
Braunish said:
To where do I copy the image file on the phone that gets "patched" by Majisk?
"Copy the blur2-boot.img file available here to your phone."
Thank you very much,
Michael
Click to expand...
Click to collapse
If I understand correctly.
You have adb and fastboot installed.
You have a boot image that works for your device and tested it by using fastboot to boot it. let's call it working_boot.img
You have MagiskManager installed.
The next steps:
adb push working_boot.img /sdcard Doesn't really matter where you put it.
Open MagiskManager
Tap on Install
Select Install
Select Patch Boot Image File
Tap on Internal storage Note: If Internal storage is not displayed. Tap on the 3-dot menu (upper right corner) and select Show SD card.
Scroll down and tap on working_boot.img
When Magisk is done patching the image file, select CLOSE
You can close MagiskManager as well.
adb pull /sdcard/magiskmanager/patched_boot.img
Reboot to bootloader and fastboot boot patched_boot.img
Open MagiskManager. You should see that Magisk is installed and active.
Now that you have temporary root, you have some options.
The easiest way would be to open MagiskManager and use the Direct install option. This will pull, patch and install a patched boot.img to the device.
Unless the the original working_boot.img used is the correct one for your device.
The safer way, pull the stock_boot.img I normally grab recovery also from the device.
For BLU R2 LTE
Code:
adb shell su -c "dd if=/dev/block/mmcblk0p7 of=/sdcard/BLUR2-boot.img"
adb shell su -c "dd if=/dev/block/mmcblk0p8 of=/sdcard/BLUR2-recovery.img"
adb pull /sdcard/BLUR2-boot.img
adb pull /sdcard/BLUR2-recovery.img
Then patch it and fastboot boot it to make sure it works.
After that you can either use MagiskManager Direct install or fastboot to flash the new patched_boot.img.
Bricked my device, used SP Flash Tool to update - Now no OTA?
I hope this is on topic enough to not start a new thread and dirty up the R1 forum
I ended up bricking my Blu R2 LTE by messing with a core APK causing it to boot loop. I didn't have a backup, so I had to resort to using SP Flash Tool to flash back to the only stock rom I could find online. Linked from the post here: www[.]getdroidtips[.]com/nougat-firmware-blu-r2-lte/
The reflash went just fine, but now I noticed I seem to be "stuck" at the January patch level / v01 build, and I'd like to bring it back up to the latest build and use the latest dump you provided w/ Magisk to re-root it again. I've tried all the tricks to get it to try to discover the updates, but nothing is working. It's been about 5 days now with no update offered.
Any idea how I can get it to either accept new OTA releases or where I could find a newer stock rom to reflash?
Thanks for your great work!
Oryx
Just got this phone and should have checked the mediafire link posted by ipdev. -_- Does anyone still have a copy or willing to share a link for me to get it or another method, theres really not much when it comes to this model. I would greatly appreciate it. Must have root to use a blu.
8milerd said:
Just got this phone and should have checked the mediafire link posted by ipdev. -_- Does anyone still have a copy or willing to share a link for me to get it or another method, theres really not much when it comes to this model. I would greatly appreciate it. Must have root to use a blu.
Click to expand...
Click to collapse
These links do not work? Link Direct download links are from MediaFire. Click on the name of the file.
I try to use direct download links from MediaFire. There servers can normally handle it. You do not have to navigate ads and redirects with direct download links.
---------- Post added at 04:58 AM ---------- Previous post was at 04:35 AM ----------
HornyOryx said:
I hope this is on topic enough to not start a new thread and dirty up the R1 forum
I ended up bricking my Blu R2 LTE by messing with a core APK causing it to boot loop. I didn't have a backup, so I had to resort to using SP Flash Tool to flash back to the only stock rom I could find online. Linked from the post here: www[.]getdroidtips[.]com/nougat-firmware-blu-r2-lte/
The reflash went just fine, but now I noticed I seem to be "stuck" at the January patch level / v01 build, and I'd like to bring it back up to the latest build and use the latest dump you provided w/ Magisk to re-root it again. I've tried all the tricks to get it to try to discover the updates, but nothing is working. It's been about 5 days now with no update offered.
Any idea how I can get it to either accept new OTA releases or where I could find a newer stock rom to reflash?
Thanks for your great work!
Oryx
Click to expand...
Click to collapse
A while back , I had to do a factory reset to get an OTA. Then I had to un-root it to get the OTA to flash.
Steps on my Xiaomi Mi A2:
Started the OTA from Oreo to Pie, officially being offered via settings.
While the OTA was downloading / installing, I uninstalled Magisk 17 (“restore images”). Note that after uninstalling Magisk, I did not see an option to install it again. In fact, the Magisk app still reported Magisk as being installed.
In the meantime, the OTA showed the restart button. This I did not tap, since I want Magisk to work.
I went back into the Magisk app. So far I had ignored the popup window offering an upgrade to Magisk 18. Now I accepted it, and I selected to install Magisk to the other slot (A/B). As advertised, this was followed by an automatic reboot.
The device at first continuously reset itself, i.e. it was in a boot loop. Eventually, I think I disconnected it from power or I pressed the power button. Now the boot process would move on to the boot animation with the colored horizontal stripe. There is got stuck. I waited for perhaps half an hour, then accepted that something is broken.
What could’ve gone wrong? Any idea what to do now or how to diagnose the issue? (there is data on the device that I don’t want to lose, text messages and other stuff)
Modifications that I did later:
Code:
fastboot set_active a
fastboot reboot
This enters a boot loop. Another time, I think after disconnecting the USB cable, it went back into Fastboot mode. Weird.
And:
Code:
fastboot set_active b
fastboot reboot
This boots to the colored stripe animation mentioned in the last of the steps above. So I assume slot b is the one that was last active.
I also tried booting other images, but to no avail:
Code:
fastboot boot boot.img
Among the images that I tried booting was Xiaomi’s 9.6.16.0 Oreo image as well as the images from the 10.0.1 built that Ricardo linked to in another post.
Bootloop usually occurs when you uninstall Magisk without uninstalling modules first.
Try installing Magisk via adb sideload with TWRP.
Sent from my Mi A2 using Tapatalk
hank81 said:
Bootloop usually occurs when you uninstall Magisk without uninstalling modules first.
Click to expand...
Click to collapse
Had no modules installed. But there was something odd about the upgrade process, especially that at first I didn’t get an option to install Magisk again.
Try installing Magisk via adb sideload with TWRP.
Click to expand...
Click to collapse
Thanks for the suggestion! Have to look into TWRP.
Anyhow, at the moment I would be happy for the phone to boot again, even without Magisk. Can install Magisk later.
feklee said:
Had no modules installed. But there was something odd about the upgrade process, especially that at first I didn’t get an option to install Magisk again.
Thanks for the suggestion! Have to look into TWRP.
Anyhow, at the moment I would be happy for the phone to boot again, even without Magisk. Can install Magisk later.
Click to expand...
Click to collapse
If you can access TWRP, I hope that you can search for the OTA firmware zip that the System Updater downloaded & you can try manually flashing that zip using TWRP. It would restore the Pie boot image which would make the device boot up.
Sent from my #FlagshipKiller3T using Tapatalk
DarkSJ1998 said:
If you can access TWRP, I hope that you can search for the OTA firmware zip that the System Updater downloaded & you can try manually flashing that zip using TWRP.
Click to expand...
Click to collapse
OK, so I booted into TWRP 3.2.3-0:
Code:
# fastboot boot TWRP-3.2.3-jasmine-20181201.img
I played with the command line in TWRP. However, I didn’t find the zip. Cache was not mounted, and it was not possible to mount it. Then I read a little bit about A/B (Seamless) System Updates. This is a cool concept, but somehow it failed miserably here. Neither slot does boot.
Slot B:
It looks like the Android version is still Oreo:
Code:
# grep version.i /system/system/build.prop
[…]
ro.build.version.incremental=V9.6.17.0.0DIMIFE
So I obtained the image files for that version. There is a post with links to dumps. I then tried to boot the V9.6.17.0 boot image:
Code:
fastboot boot boot.img
Again, booting hangs at the animation with the horizontal colored stripe.
SLOT A:
As mentioned before, booting that doesn’t work either: The system enters a boot loop, repeatedly reseting itself before it even gets to the horizontal colored stripe animation.
This one has Pie:
Code:
# grep version.i /system/system/build.prop
[…]
ro.build.version.incremental=V10.0.2.0.PDIMIFJ
As above, I obtained the image files for that version, and I did:
Code:
$ fastboot set_active a
Setting current slot to 'a'...
OKAY [ 0.017s]
Finished. Total time: 0.020s
$ fastboot boot boot.img
Downloading 'boot.img'
OKAY [ 2.633s]
booting
Boot loop!
I repeated:
Code:
$ fastboot boot boot.img
Downloading 'boot.img'
OKAY [ 2.633s]
booting
It’s always like that: When you’re not expecting anything anymore, it works! The A2 booted into Pie.
Noteworthy:
It’s weird that explicitly selecting the slot made it not work, or maybe it required another reboot.
Magisk remained installed: After the initial boot into Pie, I rebooted the phone, and it booted into Pie again although I did not flash boot.img.
Perhaps the phone didn’t do the initial boot into Pie because Magisk was still installed.
feklee said:
OK, so I booted into TWRP 3.2.3-0:
Code:
# fastboot boot TWRP-3.2.3-jasmine-20181201.img
I played with the command line in TWRP. However, I didn’t find the zip. Cache was not mounted, and it was not possible to mount it. Then I read a little bit about A/B (Seamless) System Updates. This is a cool concept, but somehow it failed miserably here. Neither slot does boot.
Slot B:
It looks like the Android version is still Oreo:
Code:
# grep version.i /system/system/build.prop
[…]
ro.build.version.incremental=V9.6.17.0.0DIMIFE
So I obtained the image files for that version. There is a post with links to dumps. I then tried to boot the V9.6.17.0 boot image:
Code:
fastboot boot boot.img
Again, booting hangs at the animation with the horizontal colored stripe.
SLOT A:
As mentioned before, booting that doesn’t work either: The system enters a boot loop, repeatedly reseting itself before it even gets to the horizontal colored stripe animation.
This one has Pie:
Code:
# grep version.i /system/system/build.prop
[…]
ro.build.version.incremental=V10.0.2.0.PDIMIFJ
As above, I obtained the image files for that version, and I did:
Code:
$ fastboot set_active a
Setting current slot to 'a'...
OKAY [ 0.017s]
Finished. Total time: 0.020s
$ fastboot boot boot.img
Downloading 'boot.img'
OKAY [ 2.633s]
booting
Boot loop!
I repeated:
Code:
$ fastboot boot boot.img
Downloading 'boot.img'
OKAY [ 2.633s]
booting
It’s always like that: When you’re not expecting anything anymore, it works! The A2 booted into Pie.
Noteworthy:
It’s weird that explicitly selecting the slot made it not work, or maybe it required another reboot.
Magisk remained installed: After the initial boot into Pie, I rebooted the phone, and it booted into Pie again although I did not flash boot.img.
Perhaps the phone didn’t do the initial boot into Pie because Magisk was still installed.
Click to expand...
Click to collapse
Great to see you fixed your issue
Maybe your post will help somebody else
Sent from my #FlagshipKiller3T using Tapatalk
I couldn't find any guide for rooting the V40, so I thought I'd write down the steps I took to root my new EUR V40 - LMV405EBW. Maybe it will help others. Sorry if this is somewhat confusing, I didn't have time to make a polished version. It's basically made from my notes during the process with the commands copied from bash history.
-First, unlock the bootloader following LG's instructions here: https://developer.lge.com/resource/mobile/RetrieveBootloader.dev
There's no TWRP for the V40 and the one made for G7 doesn't work. I don't have the time and knowledge to even attempt to compile TWRP for the V40, so I proceeded with just patching an original boot image with Magisk.
You can get the patched boot images that I used from here:
Oreo 10e: boot_a_magisk_patched_10e.img
Oreo 20f: boot_a_magisk_patched_10f.img
Pie 20a: boot_a_magisk_patched_20a.img
Pie 20b: boot_a_magisk_patched_20b.img
Pie 20f: boot_a_magisk_patched_20f.img
Pie 20g: boot_a_magisk_patched_20g.img
Q 30b: boot_a_magisk_patched_30b.img (this requires flashing to the active boot partition).
Q 30c: boot_a_magisk_patched_30c.img (this requires flashing to the active boot partition)
Q 30d: boot_a_magisk_patched_30d.image (this may or may not work with "fastboot boot" and could require flashing to the active boot partition. I haven't tested if live boot still works. I just did fastboot flash boot_x img_file).
You can try to boot it with with fastboot if you have a LNV405EBW and skip the KDZ extraction part.
Installing Magisk:
Flashing this image isn't necessary, just straight boot should be sufficient and safe.
First install Magisk Manager 7 on the phone then connect the phone to the PC and run:
Code:
adb reboot bootloader
fastboot boot boot_a_magisk_patched_10e.img
After the phone boots the OS with the external boot image, open Magisk Manager and tap on Install. Select the option to Direct install to the active slot. I played it safe and decided to NOT flash also on the inactive slot. I've left it alone so I can use it in case of need of recovery.
You'll probably notice that you don't have a connection to the carrier. Just ignore it, it will back once the phone is booted normally.
Reboot and you will have permanent root until you switch the A/B slots.
In case my patched boot image doesn't work, you can just make your own.
Tools needed:
Magisk Manager 7.0.0 installed on the phone
LG Bridge installed on a Windows machine.
a Linux machine or VM (I used the latest ubuntu desktop), python3 with the zstandard module installed and kdztools from steadfasterX's repo. Maybe kdztools would work on Windows too, I haven't tried it.
adb, fastboot
You need to procure an original ROM file for your phone model. It can be downloaded easily with LG Bridge. Just connect the phone to a Windows PC, start LG bridge, go to the Software update tab and click on Update error recovery. Wait for the download to start and disconnect the phone. Ignore LG Bridge complains about not being able to flash after the downloading stage is completed. Don't click anything in Bridge and before closing it go to C:\Users\<your_username>\AppData\Local\LG Electronics\LG Bridge\SWUpgrade and copy your KDZ somewhere else. Preferably send it to the Linux VM to the LG work folder, it'll be needed there.
On Linux open a terminal:
Code:
cd ~/Documents
mkdir LG
cd LG
git clone https://github.com/steadfasterX/kdztools.git
cd kdztools
nano undz.py -c
For kdztools to be able to extract the V40 images, I needed to edit undz.py and comment the lines 88-90. So, this block should all be commented or undz will fail to extract the boot partitions.
Code:
#if len(dz_item['pad']) != 0:
# print("[!] Error: pad is not empty", file=sys.stderr)
# sys.exit(1)
To extract, with the KDZ copied to ~/Documents/LG/
Code:
cd ~/Documents/LG/kdztools
./unkdz.py -f ../V405EBW10e_00_OPEN_EU_DS_OP_0109.kdz -x
cd kdzextracted/
List the partitions contents and look for the IDs of boot_a and/or boot_b. In my case they were 44 for boot_a and 63 for boot_b
Code:
../undz.py -f V40510e_00.dz -l
Extract boot_a or boot_b or both, they're identical:
Code:
../undz.py -f V40510e_00.dz -s 44
../undz.py -f V40510e_00.dz -s 63
You can find the extracted boot images in the dzextracted subfolder. Get boot_a.image or boot_b.image or both from there and send them to the phone in a location accessible by Magisk Manager. The Download folder should do fine.
Open Magisk Manager and tap Install, select Patch Boot Image file and patch the image file(s) you extracted. Get the patched_boot.img that Magisk Manager saves in the Download folder and send it to a PC where you have adb and fastboot.
Go to the beginning of the post to the Installing Magisk section.
Damned tempting, but I'll wait until after Pie drops.
Sent from my LM-V405 using Tapatalk
Glad to see this, hopefully it's a start for all of us.
If anything, at least a way to unlock the bootloader via legitimate channels! Gonna be generating that string, next chance I get, to be ready.
Sent from my LM-V405 using Tapatalk
Once runningnak3d gets a hold of this, we should be good with the v40. Cool beans.
Hey do the unlock codes online work for $ 12-15 on sprint? I used to flash phones back in the day and got a great deal on a bad IMEI sprint lg v40, but so far I can see there isn’t a way yet. On top off all that I m in Europe and don’t want to get the error message that I m out of the Region. I would have to go to USA just to unlock the phone.
@runningnak3d
Can't I install the firmware on a different device?
V version can not unlock BL, so envious
Getting a boot image like that works but I find it stupid to not upload it so that the others don't have to do it. Besides only one model can be bl unlocked so there won't be any model mismatch (except firmware versions but keeping up with them is not that hard)
LameMonster82 said:
Getting a boot image like that works but I find it stupid to not upload it so that the others don't have to do it. Besides only one model can be bl unlocked so there won't be any model mismatch (except firmware versions but keeping up with them is not that hard)
Click to expand...
Click to collapse
Or I could find you stupid for not noticing the patched image is in my first post.
DLS123 said:
I find you stupid for not noticing the patched images are in my first post.
Click to expand...
Click to collapse
I recommend labeling the boot images with their firmware since future firmwares won't be able to run the same boot image but other than that I'm really sorry.
LameMonster82 said:
I recommend labeling the boot images with their firmware since future firmwares won't be able to run the same boot image but other than that I'm really sorry.
Click to expand...
Click to collapse
I mentioned in the description 1 line below the link that it's for 10e. There was no other update in a long time. I don't think there can be any confusion for now. I can edit and label the file when there's will be another fw update.
It looks like unlocking the bootloader breaks Widevine L1 on the V40 and downgrades is to L3. No more HD or UHD Netflix.
I couldn't find any other solution than to re-lock the bootloader to restore L1.
This doesn't happen on the V30.
@DLS123
Thank you for all!
I ask you for more details; i'm stuck at flashing first image in adb; it returns an error; have LMV405EBW with 10f. unlocked bootloader of course
Thx again for your support!
@daphix what do you mean by flashing the first image? You're not supposed to flash my patched boot image. Just boot it without flashing and Direct install Magisk from it with Magisk Manager.
DLS123 said:
@daphix what do you mean by flashing the first image? You're not supposed to flash my patched boot image. Just boot it without flashing and Direct install Magisk from it with Magisk Manager.
Click to expand...
Click to collapse
Thx for answer; i not have too much experience in working with Magisk;
i just folowed your steps:
First install Magisk Manager 7 on the phone then connect the phone to the PC and run:
adb reboot bootloader
fastboot boot patched_boot_a.img
when i run fastboot comand for flash, is runing, but is returning "an error at line x"
i suppose is something wrong in this instructions.
daphix said:
Thx for answer; i not have too much experience in working with Magisk;
i just folowed your steps:
First install Magisk Manager 7 on the phone then connect the phone to the PC and run:
adb reboot bootloader
fastboot boot patched_boot_a.img
when i run fastboot comand for flash, is runing, but is returning "an error at line x"
Anyway; understand now what to do;
Steps are below:
- first install magisk manager
- download magisk zip from magisk site or from magisk manager himself on phone
- download patched_boot_a.img to phone from our good contributor
- use magisk manager and select inslall image of patched_boot_a.img from phone
- magisk manager will generate a magisk patched image
- transfer this magisk patched image (not patched_boot_a.img) to pc in ADB folder
- flash with Adb this magisk patched image from pc to phone.
Thx to our friend!
---------- Post added at 09:53 AM ---------- Previous post was at 09:21 AM ----------
DLS123 said:
@daphix what do you mean by flashing the first image? You're not supposed to flash my patched boot image. Just boot it without flashing and Direct install Magisk from it with Magisk Manager.
Click to expand...
Click to collapse
Hi;
using Magisk mamanger and your file was generated a file: magisk_patched.img
pls support; trying to flash that image from PC with adb not work:
fastboot flash partition_a magisk_patched.img
Click to expand...
Click to collapse
@daphix
Whatver you're trying to do, is nowhere in the procedure I used. If you already booted with my boot image why are you making another boot image with Magisk and why are you trying to flash that? I never wrote anything of the sort.
if you booted with my patched image you already have temporary root and can use Magisk Manager to Direct install Magisk itself.
DLS123 said:
@daphix
Whatver you're trying to do, is nowhere in the procedure I used. If you already booted with my boot image why are you making another boot image with Magisk and why are you trying to flash that? I never wrote anything of the sort.
if you booted with my patched image you already have temporary root and can use Magisk Manager to Direct install Magisk itself.
Click to expand...
Click to collapse
Hi , thank you for reply;
I tried many combinations of your commands;
maybe due that am noob, but succesion below simply is not working:
First install Magisk Manager 7 on the phone then connect the phone to the PC and run:
adb reboot bootloader
fastboot boot patched_boot_a.img
Tools needed: boot.img extractor. I recommend the one created by osm0sis from this thread:
https://forum.xda-developers.com/showthread.php?t=2073775
The first method was developed by osm0sis and removes magisk and all modules.
1. Unpack magisk_patched.img
2. Unzip overlay.dremove1.zip and place overlay.d folder in ramdisk folder.
3. Repack IMG
4. fastboot boot image-new.img created by repacking img
This method is an offshoot of osm0sis version but boots core-only mode. Afterwards, remove the .disable-magisk file from the /cache folder for modules to work.
1. Same as above but use the overlay.dcoreonly1.zip
2. You will boot with root but modules disabled. Once the bad module is removed, delete the .disable_magisk file in your /cache folder. Dot files are hidden files so if your root explorer can't see hidden files, run the bat file in ADB.
For both methods you must be rooted for it to work. These are not cure all's for all bootloops.
***************************************
Here is a fastboot bootable image to boot you into Magisk core-only mode, in case you bootloop due to flashing a bad module, in fastboot:
fastboot boot image-newpixel4.img
You will boot with root but modules disabled. Once the bad module is removed, delete the .disable_magisk file in your /cache folder. Dot files are hidden files so if your root explorer can't see hidden files, run the bat file in ADB.
(You must have root so if you don't, flash your magisk_patched.img and reboot first)
Remove .disable_magisk bat file
https://www.androidfilehost.com/?fid=4349826312261684994
Boot Image core-only uploaded 6-17-20
https://www.androidfilehost.com/?fid=4349826312261824031
Boot image Remove Magisk 6-17-20
https://www.androidfilehost.com/?fid=8889791610682872348
Is this for 007 or 011? Thanks for this! I see you're active in xl, but glad you're helping us with the straight 4.
Could have used this, flashed the active edge mod twice and had to re-setup
dubt17 said:
Is this for 007 or 011? Thanks for this! I see you're active in xl, but glad you're helping us with the straight 4.
Could have used this, flashed the active edge mod twice and had to re-setup
Click to expand...
Click to collapse
I would think it would work with either. The 4 and 4 XL might even share boot.img but you are just booting it anyway.
Thanks for your help! I believe lots of people will benefit from your img before TWRP comes out!
Thanks for this one... definitely a must have in the toolbox.
I got bootloop after installing edxposed
I have installed magisk canary, and gpay sql fix
Stuck on booltoop, even after fastboot with this image
spahi4 said:
I got bootloop after installing edxposed
I have installed magisk canary, and gpay sql fix
Stuck on booltoop, even after fastboot with this image
Click to expand...
Click to collapse
Try this one. Made with latest magisk.
https://www.androidfilehost.com/?fid=4349826312261639511
Tulsadiver said:
Try this one. Made with latest magisk.
https://www.androidfilehost.com/?fid=4349826312261639511
Click to expand...
Click to collapse
Any idea what im doing wrong?
PS C:\Users\Sam\Downloads> fastboot boot "C:\Users\Sam\Downloads\image-newpixel4 (1).img"
downloading 'boot.img'...
OKAY [ 1.173s]
booting...
FAILED (remote: Error verifying the received boot.img: Invalid Parameter)
finished. total time: 5.795s
1dopewrx05 said:
Any idea what im doing wrong?
PS C:\Users\Sam\Downloads> fastboot boot "C:\Users\Sam\Downloads\image-newpixel4 (1).img"
downloading 'boot.img'...
OKAY [ 1.173s]
booting...
FAILED (remote: Error verifying the received boot.img: Invalid Parameter)
finished. total time: 5.795s
Click to expand...
Click to collapse
Try making your own.
https://forum.xda-developers.com/pixel-4-xl/themes/magisk-modules-disabler-booting-magisk-t3990557
thanks for the guide but I cant seem to get this working right for me.
the img file provided gives me this error on the fastboot command : FAILED (remote: Error verifying the received boot.img: Invalid Parameter)
when i create my own it boots via fastboot but then goes back to the boot loop state of the G logo and a progress bar
the stock boot img lets me boot up without root
I got into this state by trying to install gravity box, but now im just trying to get core magisk back. any input?
StephenMilone said:
thanks for the guide but I cant seem to get this working right for me.
the img file provided gives me this error on the fastboot command : FAILED (remote: Error verifying the received boot.img: Invalid Parameter)
when i create my own it boots via fastboot but then goes back to the boot loop state of the G logo and a progress bar
the stock boot img lets me boot up without root
I got into this state by trying to install gravity box, but now im just trying to get core magisk back. any input?
Click to expand...
Click to collapse
Upload a current magisk_patched.img
Tulsadiver said:
Upload a current magisk_patched.img
Click to expand...
Click to collapse
https://www.dropbox.com/s/zgd83bjtvbravuo/magisk_patched.img?dl=0
here you go - thanks!!
StephenMilone said:
https://www.dropbox.com/s/zgd83bjtvbravuo/magisk_patched.img?dl=0
here you go - thanks!!
Click to expand...
Click to collapse
Sorry it took so long. I had some things I had to do.
Core only
https://www.androidfilehost.com/?fid=4349826312261694121
Remove
https://www.androidfilehost.com/?fid=4349826312261694123
Tulsadiver said:
Sorry it took so long. I had some things I had to do.
Core only
https://www.androidfilehost.com/?fid=4349826312261694121
Remove
https://www.androidfilehost.com/?fid=4349826312261694123
Click to expand...
Click to collapse
do not apologize at all! and it worked!! thank you so very very much.
any idea what was i doing wrong trying to package it myself?
StephenMilone said:
do not apologize at all! and it worked!! thank you so very very much.
any idea what was i doing wrong trying to package it myself?
Click to expand...
Click to collapse
Hard to say. Pretty straight forward. Just drop the overlay.d folder in the ramdisk folder and repack.
Not sure what i'm doing wrong but this doesn't work for me, I used the img that you sent to StephenMilone but it doesn't work even when I use that. I installed a magisk module and I got stuck in a bootloop but nothing I have tried has worked. Any help would be appreciated, thanks!
Thank you SO MUCH for this. I once again forgot to disable/delete Active Edge Mod on my Pixel 3 before updating the system via OTA, and this just saved me.
March boot fix images uploaded.
I might be doing something wrong... But I had gotten this to work for two months in a row,so couldn't be too much off
June 2020 patch... I can't figure it out... I did the overlay.d and I can't get the phone to boot properly.
Stock boot.img is fine, but patched and asking it to disable isn't working.... Can you generate one for June @Tulsadiver ? Thanks in advanced
sylikc said:
I might be doing something wrong... But I had gotten this to work for two months in a row,so couldn't be too much off
June 2020 patch... I can't figure it out... I did the overlay.d and I can't get the phone to boot properly.
Stock boot.img is fine, but patched and asking it to disable isn't working.... Can you generate one for June @Tulsadiver ? Thanks in advanced
Click to expand...
Click to collapse
Core-only
https://www.androidfilehost.com/?fid=4349826312261824031