Hey guys, first time posting, hoping I can get some help with these very frustrating problems. My device is an XT1952-4 running Android 10 with bootloader unlocked. I'll break this in to two sections for simplicity:
Magisk
I got a stock firmware img from the Rescue and Smart Assistant. (I had to use it to save my device after almost ruining it on a prior attempt with an incorrect img.) I installed the latest Magisk Manager (8.0.4 (4768)), and got it read to install Magisk 20.4 (20400). I used this to patch the stock img. I grabbed the patched img off my phone and put it into my adb folder. I then rebooted into fastboot. Here's how the flash command line went:
fastboot flash boot_a magisk_patched_x2DRE.img
(bootloader) is-logical:boot_a: not found
Sending 'boot_a' (17629 KB) OKAY [ 0.423s]
Writing 'boot_a' (bootloader) Image signed with key
I then tried to reboot to recovery, which resulted in an android screen saying, "No command." I was able to subsequently get to the regular recovery menu by using power + volume up, but after rebooting again, Magisk still says, "Installed: N/A". I've tried this like a dozen times and can't get it to install.
TWRP
With this one, I've tried using two different TWRP builds. (Or at least I presume they're two different TWRP builds.) One is a 3.3.0-0 River custom for G7 Play, the other is from this thread: https://forum.xda-developers.com/t/how-to-successfully-install-twrp-for-g7-play.3979701/
I used the DTBO from the above-listed thread.
I get the same result with trying to fastboot either TWRP img from my adb folder. I get the following command line:
fastboot flash dtbo dtbo.img
(bootloader) is-logical:dtbo_a: not found
Sending 'dtbo_a' (965 KB) OKAY [ 0.186s]
Writing 'dtbo_a' OKAY [ 0.054s]
Finished. Total time: 0.287s
fastboot boot recovery.img
Sending 'boot.img' (22156 KB) OKAY [ 0.486s]
Booting OKAY [ 0.163s]
Finished. Total time: 0.687s
After this, I get to the Team Win splash page showing the version of TWRP, but it hangs indefinitely on that screen. I am able to shutdown by holding the power button. Again, I've tried this about a dozen times with the same result.
I'd really appreciate any help with either of these issues, or even suggestions of other ways to root a G7 Play. Thanks!
TWRP I can't help you with as I haven't tried installing it.
Magisk is partially solved in the thread here.
Check the posts by myself and M47Z.
The short version is that the Moto boot image needs some, rather difficult, manual massaging before you can install Magisk to it.
Curmudge0n said:
Hey guys, first time posting, hoping I can get some help with these very frustrating problems. My device is an XT1952-4 running Android 10 with bootloader unlocked. I'll break this in to two sections for simplicity:
Magisk
I got a stock firmware img from the Rescue and Smart Assistant. (I had to use it to save my device after almost ruining it on a prior attempt with an incorrect img.) I installed the latest Magisk Manager (8.0.4 (4768)), and got it read to install Magisk 20.4 (20400). I used this to patch the stock img. I grabbed the patched img off my phone and put it into my adb folder. I then rebooted into fastboot. Here's how the flash command line went:
fastboot flash boot_a magisk_patched_x2DRE.img
(bootloader) is-logical:boot_a: not found
Sending 'boot_a' (17629 KB) OKAY [ 0.423s]
Writing 'boot_a' (bootloader) Image signed with key
I then tried to reboot to recovery, which resulted in an android screen saying, "No command." I was able to subsequently get to the regular recovery menu by using power + volume up, but after rebooting again, Magisk still says, "Installed: N/A". I've tried this like a dozen times and can't get it to install.
TWRP
With this one, I've tried using two different TWRP builds. (Or at least I presume they're two different TWRP builds.) One is a 3.3.0-0 River custom for G7 Play, the other is from this thread: https://forum.xda-developers.com/t/how-to-successfully-install-twrp-for-g7-play.3979701/
I used the DTBO from the above-listed thread.
I get the same result with trying to fastboot either TWRP img from my adb folder. I get the following command line:
fastboot flash dtbo dtbo.img
(bootloader) is-logical:dtbo_a: not found
Sending 'dtbo_a' (965 KB) OKAY [ 0.186s]
Writing 'dtbo_a' OKAY [ 0.054s]
Finished. Total time: 0.287s
fastboot boot recovery.img
Sending 'boot.img' (22156 KB) OKAY [ 0.486s]
Booting OKAY [ 0.163s]
Finished. Total time: 0.687s
After this, I get to the Team Win splash page showing the version of TWRP, but it hangs indefinitely on that screen. I am able to shutdown by holding the power button. Again, I've tried this about a dozen times with the same result.
I'd really appreciate any help with either of these issues, or even suggestions of other ways to root a G7 Play. Thanks!
Click to expand...
Click to collapse
when TWRP hangs like that after booting i've found in my own experiences that is usually caused from the version of TWRP you are using. Or you could have just downloaded a bad file of TWRP if you didn't use the official website. I currently use twrp-3.5.1 for my g7 play xt1952-t channel. hope this helps a little.
Related
I took the Dec 2019 OTA, by uninstalling Magisk, took the OTA ( did not reboot) and where I think i went wrong was when re-patching the boot.img i choose to install on inactive slot.
I have since tried many other things to recover from this. Is it possible to fix it without wiping and losing my data?
I have myself at No vaild slot to boot
EDIT: No I am on Enter Reason: error boot prepare
=========================================
After 10hrs of throwing crap at the wall and having nothing stuck. I just started over with the Dec 2019 factory image.
Androider4Life said:
I took the Dec 2019 OTA, by uninstalling Magisk, took the OTA ( did not reboot) and where I think i went wrong was when re-patching the boot.img i choose to install on inactive slot.
I have since tried many other things to recover from this. Is it possible to fix it without wiping and losing my data?
I have myself at No vaild slot to boot. EDIT: No I am on Enter Reason: error boot prepare
Click to expand...
Click to collapse
What happens when you flash the stock boot.img? Have you tried fastboot flashing the full image (not OTA) removing the wipe flag (-w) from the flash-all.bat? If that doesn't work, your data may already be gone or corrupt. Next step, flash full image and allowing data wipe.
v12xke said:
What happens when you flash the stock boot.img? Have you tried fastboot flashing the full image (not OTA) removing the wipe flag (-w) from the flash-all.bat? If that doesn't work, your data may already be gone or corrupt. Next step, flash full image and allowing data wipe.
Click to expand...
Click to collapse
============================================================
boot.img flash, Phone reboots to White G Screen and sits there. If I hold the power button till it reboots it goes back to the White G Screen and sits there.
C:\Users\Clint\Desktop\Pixel\December\platform-tools>fastboot flash boot boot.img
Sending 'boot_a' (65536 KB) OKAY [ 2.835s]
Writing 'boot_a' OKAY [ 0.595s]
Finished. Total time: 3.705s
C:\Users\Clint\Desktop\Pixel\December\platform-tools>fastboot reboot
Rebooting OKAY [ 0.045s]
Finished. Total time: 0.052s
Androider4Life said:
============================================================
boot.img flash, Phone reboots to White G Screen and sits there. If I hold the power button till it reboots it goes back to the White G Screen and sits there.
C:\Users\Clint\Desktop\Pixel\December\platform-tools>fastboot flash boot boot.img
Sending 'boot_a' (65536 KB) OKAY [ 2.835s]
Writing 'boot_a' OKAY [ 0.595s]
Finished. Total time: 3.705s
C:\Users\Clint\Desktop\Pixel\December\platform-tools>fastboot reboot
Rebooting OKAY [ 0.045s]
Finished. Total time: 0.052s
Click to expand...
Click to collapse
Assuming that was the stock boot.img extracted from the Google image, you could also try flashing the same to both slots before trying flashing the full factory image, removing the wipe flag first. Some people like to update using OTA's. I ALWAYS flash the full image every month on my Pixel devices and have never had an issue.
v12xke said:
Assuming that was the stock boot.img extracted from the Google image, you could also try flashing the same to both slots before trying flashing the full factory image, removing the wipe flag first. Some people like to update using OTA's. I ALWAYS flash the full image every month on my Pixel devices and have never had an issue.
Click to expand...
Click to collapse
======================================================================================
Back to setting on the White G screen.
C:\Users\Clint\Desktop\Pixel\December\platform-tools>fastboot flash boot --slot all boot.img
Sending 'boot_a' (65536 KB) OKAY [ 2.635s]
Writing 'boot_a' OKAY [ 0.623s]
Sending 'boot_b' (65536 KB) OKAY [ 3.126s]
Writing 'boot_b' OKAY [ 0.618s]
Finished. Total time: 7.624s
C:\Users\Clint\Desktop\Pixel\December\platform-tools>fastboot reboot
Rebooting OKAY [ 0.033s]
Finished. Total time: 0.071s
C:\Users\Clint\Desktop\Pixel\December\platform-tools>
Flashing the December Full image (removing the -w) I am back to the Error Reason: no valid slot to boot. I have attached the log
See my thread a couple of posts down about the December update for the fix.
DOMF said:
See my thread a couple of posts down about the December update for the fix.
Click to expand...
Click to collapse
I have read thru it and tried somethings with no luck..which part fixed it for you?
If I could just get to a point that I can access my internal storage to back up some stuff, I'd be ok full wiping after that.
After 10hrs of throwing crap at the wall and having nothing stuck. I just started over with the Dec 2019 factory image.
flash-all.sh without -w, adb rebbot bootloader, fastboot boot image-newpixel3xlRemove.img, adb reboot bootloader, fastboot flash boot magisk-patched.img
DOMF said:
flash-all.sh without -w, adb rebbot bootloader, fastboot boot image-newpixel3xlRemove.img, adb reboot bootloader, fastboot flash boot magisk-patched.img
Click to expand...
Click to collapse
Having the same issue.
What is ''image-newpixel3xlRemove.img''
Hello,
I have some problem on my phone (AOSP 9) but I didn't know why (I didn't download any new apps, last thing was Magisk update). Now more than the half of the apps don't work, battery drain very fast and I can't restart and shutdown the phone (or I need to do soft reset).
I tried to do a factory reset directly from Android but it doesn't work.
I tried to flash TWRP and and I got this message.
Code:
Y:\Download>fastboot flash recovery twrp.img
(bootloader) has-slot:recovery: not found
(bootloader) is-logical:recovery: not found
Sending 'recovery' (15864 KB) OKAY [ 0.512s]
Writing 'recovery' (bootloader) Image not signed or corrupt
OKAY [ 0.204s]
Finished. Total time: 0.919s
According to other subjects it's not a big deal so I decided to restart in bootloader but now I'm stuck on TWRP logo. I waited more than 1h30 and nothing happens.
Have you got an idea ?
Thank you
Do a clean flash of the stock ROM.
Thank you, it works, and I was able to reinstall AOSP.
Thank you again
I am new to flashing custom roms, and I got lineage running but I wanted to try Evo X, when I tried flashing through lineage Recovery it booted back into lineage, ok, so I erased all datat through lineage recovery and installed TWRP. I got that on but within a few clicks of messing around I found myself with no recovery or OS and im only stuck in fastboot, I have no idea how to get out of it. mods take this post down if posted in the wrong community. I just though this would be the best place to post it. I am new to XDA, I have these ADB logs from the command I was trying to run
C:\Users\user\Desktop\platform-tools_r31.0.3-windows\platform-tools>fastboot boot C:\Users\user\Desktop\platform-tools_r31.0.3-windows\platform-tools\TWRP-3.5.1-lemonadep-Nebrassy-2.img
Sending 'boot.img' (196608 KB) OKAY [ 4.500s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
fastboot: error: Command failed
I have no idea why it keep failing, I would greatly appreciate any help to get my phone working again.
Try the following command :
fastboot flash boot lineage-recovery.img
Once that is done, boot to recovery from fastboot and try flashing the rom you were trying to.
oddlyspaced said:
Try the following command :
fastboot flash boot lineage-recovery.img
Once that is done, boot to recovery from fastboot and try flashing the rom you were trying to.
Click to expand...
Click to collapse
I tried this and when I click to restart into recovery it just boots back into fastboot, this is what ADB says after I use the flash boot command
C:\Users\user\Desktop\platform-tools_r31.0.3-windows\platform-tools>fastboot flash boot lineage-18.1-20210803-recovery-lemonadep.img
Sending 'boot_a' (196608 KB) OKAY [ 4.541s]
Writing 'boot_a' OKAY [ 0.556s]
Finished. Total time: 5.848s
I don't see why it is not going into recovery
eltryyyy said:
I tried this and when I click to restart into recovery it just boots back into fastboot, this is what ADB says after I use the flash boot command
C:\Users\user\Desktop\platform-tools_r31.0.3-windows\platform-tools>fastboot flash boot lineage-18.1-20210803-recovery-lemonadep.img
Sending 'boot_a' (196608 KB) OKAY [ 4.541s]
Writing 'boot_a' OKAY [ 0.556s]
Finished. Total time: 5.848s
I don't see why it is not going into recovery
Click to expand...
Click to collapse
I guess you should try msm tool then
Go for msm tool. You can find a tutorial for 8pro on YouTube. Follow the same steps( obviously with the correct op9 pro firmware.
RazOne said:
Go for msm tool. You can find a tutorial for 8pro on YouTube. Follow the same steps( obviously with the correct op9 pro firmware.
Click to expand...
Click to collapse
I have gotten msm tool and my firmware, but nothing is showing up in msm when my device is connected
ive linked a screenshot of what my msm tool looks like, im just so desperate to get my phone back
Power off phone, position mouse cursor o er start button on msm tool, hold down vol up and down simultaneously, plug phone into computer wait a quick second and press start. That should work.
eltryyyy said:
I tried this and when I click to restart into recovery it just boots back into fastboot, this is what ADB says after I use the flash boot command
C:\Users\user\Desktop\platform-tools_r31.0.3-windows\platform-tools>fastboot flash boot lineage-18.1-20210803-recovery-lemonadep.img
Sending 'boot_a' (196608 KB) OKAY [ 4.541s]
Writing 'boot_a' OKAY [ 0.556s]
Finished. Total time: 5.848s
Click to expand...
Click to collapse
Instead of going for msm tool, when your stuck in fastboot, after successfully flashing an .img (Twrp, losrecovery ) use:
"fastboot --set-active=b" (when you're active in slot a)
Then reboot to recovery.
Basically it flashes okay but to the other slot. Happened to me too. I am now booted into the system on slot b. Hope it helps
IamTheBRAVE said:
Instead of going for msm tool, when your stuck in fastboot, after successfully flashing an .img (Twrp, losrecovery ) use:
"fastboot --set-active=b" (when you're active in slot a)
Then reboot to recovery.
Basically it flashes okay but to the other slot. Happened to me too. I am now booted into the system on slot b. Hope it helps
Click to expand...
Click to collapse
I LITERALLY CANNOT THANK YOU ENOUGH, YOU ARE LIKE THE DAD I NEVER HAD.
Lol, i'm not that old found the answer myself in a forum after 2 days of being stuck in fastboot.
IamTheBRAVE said:
Instead of going for msm tool, when your stuck in fastboot, after successfully flashing an .img (Twrp, losrecovery ) use:
"fastboot --set-active=b" (when you're active in slot a)
Then reboot to recovery.
Basically it flashes okay but to the other slot. Happened to me too. I am now booted into the system on slot b. Hope it helps
Click to expand...
Click to collapse
hello guys i am facing that same issue but my own show slot_b and then i try to use your step but still not work help me plizzz
Googled the error you have. Check this post (and following ones)
[SOLVED] - Bootloop with completely new OPO9pro after oem unlock
Hello, just received the phone (EU), updated latest online udpate. (no Google account etc added, just fast setup) Enabled developer options, OEM unlocking and USB debugging. After update, 1*reboot. then another reboot to bootloader, and executed...
forum.xda-developers.com
I think you should start over and use "fastboot flashing unlock" instead of fastboot oem unlock.
Follow the link in that thread. Droidwin has the best tutorials for oneplus you'll find. Never had this error myself, so can't say for sure what to do.
So, here I was thinking things couldn't hurt to do some customisation.
This evening, I flashed a custom logo... using fastboot. (fastboot flash logo logo.bin)
That was the last thing I saw on my device, it won't show anything anymore.
Any advice on how to get any connection to my device again?
Right... So as before I found the solution myself.
I used the BROM to reflash the logo with the proper image.
For whoever wants to know. I used the MTK bypass utility to bypass the authentication stuff, and the SP Flash tool to flash.
I did have to use libusb-win32 for the python part, took me some hours to figure that one out. All sources told me UsbDK would work for that.
Kind of relieved I actually managed to unbrick my phone.
Did you get solution?
As mentioned in the post right before you; yes.
Hello,
I'm a beginner in the field of flasing custom roms but I would really like to abandon using google on my phone and find your work here really awesome. So yeah, I hope my question doesn't sound stupid but I'm seriously stuck and hope I didn't completely break my phone.
I am using a Redmi Note 8 (2021) and wanted to flash lineageOS. So I unlocked the bootloader via my mi account, booted into fastboot mode (usb-debugging was of course enabled) and tried to flash twrp to recovery using the cmd-window via platform-tools.
This didn't work because when I typed:
./fastboot flash recovery twrp.img
I got the reply:
Sending 'recovery' (65536 KB) OKAY [ 1.743s]
Writing 'recovery' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
I therefore started googling and found a threat on xda where someone had solved the problem by replacing 'recovery' with 'boot':
./fastboot flash boot twrp.img
What I got was:
Sending 'boot_a' (65536 KB) OKAY [ 1.818s]
Writing 'boot_a' OKAY [ 0.827s]
Finished. Total time: 2.681s
After that my phone was bricked. I cannot enter recovery mode anymore and even fastboot mode appears a bit different (I don't see the bunny anymore, all I see is the word 'fastboot' in orange letters on a black screen). When I enter fastboot mode, the device is detected by my computer - the only sign that still gives me an inch of hope. When I'm not in fastboot mode my phone keeps vibrating and then turning of, then suddenly it vibrates again and turns on, the logo 'redmi' appears and then it suddenly turns off again - and it just keeps repeating this procedure.
I downloaded the mi flash tool and tried to flash the Xiaomi ROM, but that didn't work either - after about five minutes of waiting I get an error. I tried different versions of MIUI but keep getting errors. When I try to flash the Xiaomi ROM via cmd-window, as suggested here ( https://www.droidwin.com/unbrick-redmi-note-8-fastboot-commands/ ) I get this:
fastboot flash xbl_a xbl.elf
Sending 'xbl_a' (3449 KB) OKAY [ 0.105s]
Writing 'xbl_a' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
Is there anything left for me to do or should I give up and save money for a new phone?
I would be very, very grateful for help
You could try this: fastboot --set-active=b
Hello,
I'm a beginner in the field of flasing custom roms but I would really like to abandon using google on my phone and find your work here really awesome. So yeah, I hope my question doesn't sound stupid but I'm seriously stuck and hope I didn't completely break my phone.
I am using a Redmi Note 8 (2021) and wanted to flash lineageOS. So I unlocked the bootloader via my mi account, booted into fastboot mode (usb-debugging was of course enabled) and tried to flash twrp to recovery using the cmd-window via platform-tools.
This didn't work because when I typed:
./fastboot flash recovery twrp.img
I got the reply:
Sending 'recovery' (65536 KB) OKAY [ 1.743s]
Writing 'recovery' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
I therefore started googling and found a threat on xda where someone had solved the problem by replacing 'recovery' with 'boot':
./fastboot flash boot twrp.img
What I got was:
Sending 'boot_a' (65536 KB) OKAY [ 1.818s]
Writing 'boot_a' OKAY [ 0.827s]
Finished. Total time: 2.681s
After that my phone was bricked. I cannot enter recovery mode anymore and even fastboot mode appears a bit different (I don't see the bunny anymore, all I see is the word 'fastboot' in orange letters on a black screen). When I enter fastboot mode, the device is detected by my computer - the only sign that still gives me an inch of hope. When I'm not in fastboot mode my phone keeps vibrating and then turning of, then suddenly it vibrates again and turns on, the logo 'redmi' appears and then it suddenly turns off again - and it just keeps repeating this procedure.
I downloaded the mi flash tool and tried to flash the Xiaomi ROM, but that didn't work either - after about five minutes of waiting I get an error. I tried different versions of MIUI but keep getting errors. When I try to flash the Xiaomi ROM via cmd-window, as suggested here ( https://www.droidwin.com/unbrick-redmi-note-8-fastboot-commands/ ) I get this:
fastboot flash xbl xbl.elf
Sending 'xbl' (3449 KB) OKAY [ 0.105s]
Writing 'xbl' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
Is there anything left for me to do or should I give up and save money for a new phone? I am also wondering why the command-window keeps talking about 'boot_a'. Is there a 'boot-b' also? And should I write something onto it? When I try to boot the twrp.img by typing:
fastboot boot twrp.img
I get:
Sending 'boot.img' (65536 KB) OKAY [ 1.592s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
I would be very, very grateful for help
Norah1838 said:
Hello,
I'm a beginner in the field of flasing custom roms but I would really like to abandon using google on my phone and find your work here really awesome. So yeah, I hope my question doesn't sound stupid but I'm seriously stuck and hope I didn't completely break my phone.
Click to expand...
Click to collapse
Use this tool:
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
First off: don't go punching in commands you don't understand.
You literally flashed an incompatible image to your boot_a.
You could try and set the active partition to b using: fastboot --set-active=b.
Other option, if you have the firmware image for your boot partition, flash that image to boot_a.
you only need to flash the original boot.img from firmware lol it's so easy