Hi, I followed thew rooting instructions and got to the part where you flash the recovery after flashing I've tried to boot into recovery and all I get is your device software cannot be checked screen then it reboots or loads the factory reset screen and resets back to factory settings.
I have checked the phone is unlocked and it says it is
Jonnibravo said:
Hi, I followed thew rooting instructions and got to the part where you flash the recovery
after flashing I've tried to boot into recovery and all I get is your device software cannot be checked screen
then it reboots or loads the factory reset screen and resets back to factory settings.
I have checked the phone is unlocked and it says it is
Click to expand...
Click to collapse
Ignore the scary bootloader unlock warning. That's not preventing you from booting to TWRP.
What's preventing you from booting to TWRP is you didn't fully install TWRP and activate it. You still have stock recovery because you flashed TWRP but didn't finish the TWRP installation/activation process. So TWRP didn't stick and you have stock recovery still.
Read the instructions again. Post #193 of the WTF bootloader unlock and root thread.
WHICH instructions did you follow? Because with my instructions I cleary tell how to immediately boot to TWRP with fastboot flash commands after installing it -- and to NOT do any anything else (even rebooting the phone) before finishing TWRP installation and activation. You either didn't use my instructions or didn't carefully follow them?
People should really PRINT out the instructions before starting the process so they can carefully read it. It's very easy to skip over an important part or skip over a part you don't think is important?
It's all there for a reason.
Sent via open market LG US998 V30/V30+
ChazzMatt said:
Ignore the scary bootloader unlock warning. That's not preventing you from booting to TWRP.
What's preventing you from booting to TWRP is you didn't fully install TWRP and activate it. You still have stock recovery because you flashed TWRP but didn't finish the installation process. So TWRP didn't stick and you have stock recovery still.
Read the instructions again. Post #193 of the WTF bootloader unlock and root thread.
WHICH instructions did you follow? Because with my instructions I cleary tell how to immediately boot to TWRP with fastboot flash commands after installing it -- and to NOT do any anything else before finishing TWRP installation and activation. You either didn't use my instructions or didn't carefully follow them?
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
I have installed using fastboot command and used the boot twrp.img command, the corruption message shows then the screen goes blank and it goes from the lg v30 logo back to corruption logo then reboots. What stage have I missed.
Jonnibravo said:
I have installed using fastboot command and used the boot twrp.img command, the corruption message shows then the screen goes blank and it goes from the lg v30 logo back to corruption logo then reboots. What stage have I missed.
Click to expand...
Click to collapse
From my instructions:
TLDR:
flash twrp: fastboot flash TWRP.img (TWRP-3.2.1-joan-v0.1.img re-named as just "TWRP.img")
boot twrp: fastboot boot TWRP.img (TWRP-3.2.1-joan-v0.1.img re-named as just "TWRP.img")
swipe to allow modifications (do NOT leave read-only, TWRP NEEDS to be able to make changes to your system.)
select WIPE, then FORMAT DATA, then write yes
wipe cache, dalvik, data
flash magisk
flash encryption disabler
flash root disabler
reboot
STRONG SUGGESTION: After successfully doing all this, when you finally boot back to LG Oreo, install an app like this to easily facilliate rebooting to TWRP recovery in the future: Recovery Reboot
Even if you didn't actually install TWRP, you would still be able to boot to TWRP using the boot command ( fastboot boot TWRP.img) as long as you were connected to your computer and had TWRP.img in your ADB folder.
I've done it to make TWRP backups of "stock" systems where TWRP is not installed on purpose.
People who never finished activating TWRP have been able to do it, as they really don't have TWRP installed --- they are booting to "temporary" TWRP from their computer using fastboot boot TWRP.img. If they try to boot to TWRP from their phone, using an app they get the Android on his back which is a clue they REALLY don't have TWRP installed... but they are still able to fastboot boot TWRP.img when connected from their computer.
If you can't do that, something is very wrong. It's just that's the easiest way to get into TWRP after flashing it, so you can then "activate" it, make the installation stick.
Thanks for that its installed and I have installed a rom however I still cant boot into recovery, I have to reflash to get back in, and is there any way to get rid of the corruption message
Jonnibravo said:
is there any way to get rid of the corruption message
Click to expand...
Click to collapse
Not really. The "corruption message" is just LG's scary bootloader unlock warning to discourage you from rooting your phone. It's really a sign of freedom. Ignore it.
It's going to show up when you boot to TWRP or even when to boot to regular OS. It's just an image, a picture for LG to try to scare you. It stays up a few seconds then goes away.
Some Verizon users have found if they flash part of the Verizon firmware back it replaces the bootloader unlock warning with a few seconds of black:
datechnerd said:
I did have to wipe to reflash US998. But while I was fighting that I discovered what partition holds the bootloader warning!!!! It's rawresources. I moved the VS996 rawresources over to my US998 /dev/block/bootdevice/by-name/ and no longer have the warning. Granted it's a short black screen pause,
Click to expand...
Click to collapse
While that is very interesting, for now I would just ignore the warning. It's not preventing you from booting to TWRP. What's preventing you from booting to TWRP is somehow you haven't finished the entire TWRP installation/activation process.
Jonnibravo said:
Thanks for that its installed and I have installed a rom however I still cant boot into recovery, I have to reflash to get back in
Click to expand...
Click to collapse
If you installed the Recovery Reboot app I recommended (requires root access) you can boot to TWRP from there on your phone, IF you REALLY have TWRP installed. If you are having to boot to "temp" TWRP via ADB from your computer every time, then TWRP is not really installed on your phone. If you use that Recovery Reboot app, and it boots to Android on his back, then you still have stock recovery installed.
You need to reflash (reinstall) TWRP, then boot to TWRP immediately and go through the steps I posted to make it writable -- so it will stick as your custom recovery.
RTFM Myself
ChazzMatt said:
Ignore the scary bootloader unlock warning. That's not preventing you from booting to TWRP.
What's preventing you from booting to TWRP is you didn't fully install TWRP and activate it. You still have stock recovery because you flashed TWRP but didn't finish the TWRP installation/activation process. So TWRP didn't stick and you have stock recovery still.
Read the instructions again. Post #193 of the WTF bootloader unlock and root thread.
WHICH instructions did you follow? Because with my instructions I cleary tell how to immediately boot to TWRP with fastboot flash commands after installing it -- and to NOT do any anything else (even rebooting the phone) before finishing TWRP installation and activation. You either didn't use my instructions or didn't carefully follow them?
People should really PRINT out the instructions before starting the process so they can carefully read it. It's very easy to skip over an important part or skip over a part you don't think is important?
It's all there for a reason.
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
I just had the same issue, had it all ready went to Pie, lost Magisk root, played with it until lost it all.. so had to start again.. missed the important part after intalling TWRP.. thanks again :good::good::good:
Related
No matter how I try to flash the TWRP recovery image to the recovery partition, TWRP gets replaced by the crappy stock recovery!! This is absolutely maddening!
Specifically, it seems that no matter what method to use to flash the TWRP recovery, it gets overriden by the stock loader when the phone reboots.
My bootloader is UNLOCKED and I've installed a custom rom just fine by using the command fastboot boot twrp.img to boot into the twrp image. This is the only way I'm able to use TWRP at all.
I've tried:
fastboot flash recovery twrp.img
Booting into TWRP, and flashing the image over the recovery partition
Flashify to flash the TWRP over the recovery partition from within the rom
Trying to flash cyangenmod's recovery from within the rom (was pretty desperate at this point..)
I've also tried many different versions of TWRP, I can boot into them just fine but none of them stick when I flash them to the recovery partition.
It always says it's successful when I try to flash it, I reboot into recovery, and it boots into the piece of crap EmUI stock recovery screen every time
Anyone have any pointers here? It's not the end of the world but it's pretty aggravating having a completely useless recovery if I'm not near a computer,.
Try using Flashify or Flashfire.
Sadly didn't work. It doesn't seem to matter how I flash the recovery, the bootloader replaces it with the stock recovery when it boots. I'll update the OP to clarify, but thank you
I am having same issue have you found a fix
Have you tried starting completely over? Like, downloading the official MM build (b331, C564D003) from Huawei (Assuming you're on L24)?
On the new, freshly installed ROM, make sure that USB Debugging is and enable OEM Unlock are on in the developer settings.
Then, try flashing this build of TWRP again.
Before rebooting, do a Cache/Dalvik Wipe.
Boot up into the stock rom, then use 'adb reboot recovery' to see what happens next. It should work...
Hi mate,
It'd be easier to help you if you could post a screenshot of your FASTBOOT screen. There will be a line that will say FRP=LOCKED/UNLOCKED something like this.
if it is locked,
you have to install stock rom & enable OEM unlock from setting.
Then relock the boot loader. Then again unlock the boot loader.
For myself, I unlocked my BL unofficially, & this problem occurred . I solved it this way...
Hope it helps.
Cheers!
I have used LGUP to install software (Nougat) and it's working fine..
I then install TWRP as normal, no issues reported during install (I can see via cmd screen).
I then proceed to reboot to recovery using methods I have been using for months, and it goes to yes, yes selection.
It then doesn't load TWRP but carries on wiping my phone to basics again.
Have tried various methods of putting TWRP on but does anyone think is something to do with Nougat as the bootloader unlocked screen is different, larger text etc
Have now tried a KDZ for marshmallow and recovery still won't go to TWRP.
It's almost like the recovery area is now not accessible?
Any suggestions please?
alienex said:
I have used LGUP to install software (Nougat) and it's working fine..
I then install TWRP as normal, no issues reported during install (I can see via cmd screen).
I then proceed to reboot to recovery using methods I have been using for months, and it goes to yes, yes selection.
It then doesn't load TWRP but carries on wiping my phone to basics again.
Have tried various methods of putting TWRP on but does anyone think is something to do with Nougat as the bootloader unlocked screen is different, larger text etc
Have now tried a KDZ for marshmallow and recovery still won't go to TWRP.
It's almost like the recovery area is now not accessible?
Any suggestions please?
Click to expand...
Click to collapse
Hmm strange. Have you tried rebooting using "adb reboot recovery" ?
I would suggest you flash recovery and boot straight into it not allowing the phone to boot into android. So flash recovery, remove battery, then try booting into recovery. Im pretty sure recovery can be lost if you boot into android before flashing SUPERSU (https://download.chainfire.eu/696/supersu/)
But i could be wrong
You have to do the following:
1) Flash the TWRP trouch Fastboot, don't reboot
2) Remove the battery, put it back, don't turn on the phone normally!
3) Use the button combination to enter in recovery
Ok have flashed again and it has "Stuck" this time after pulling battery before reboot so TWRP back!
Now to flash again and chill
Thanks both
Hi,
I unlocked my Honor 9 bootloader using the "fastboot oem unlock 'unlock key'" method.
After that it did low level reset or something of the sort and booted to Android.
After that I wanted to install TWRP using fastboot, the problem is that every time I do "adb reboot bootloader" I get a message the device cannot be trusted (see pic) and it boots to android.
I tried pressing power button, up button (this gets me to the recovery), but it always gets back to Android and not to fastboot.
What can I do???
Thank you
Return fully stock, then try again
PalakMi said:
Return fully stock, then try again
Click to expand...
Click to collapse
How do I do that, use the original recovery?
OK, I managed to get to the bootloader by turning off the phone, pressing the volume down button and connecting the USB cable.
I flashed twrp and somehow booted to the recovery I wanted to flash the supersu.zip but all the folders and file names in the sdcard were gibberish.
I rebooted and everything was ok (not gibberish) but instead of having twrp I got the original recovery back.
Since then even if I flash using fastboot the twrp recovery I keep getting the original recovery.
In the fastboot screen there's a message "Android reboot reason: bootloader NA reboot_enter_fastboot_common_func" is it normal? (see pic)
And one last question, should I use SuperSU-v2.82-201705271822.zip or Magisk-v14.0.zip to root?
UPDATE:
I managed to get twrp working.
I did fastboot oem relock, and then unlocked the bootloader again, and it booted to twrp (without re-flashing twrp).
When I tried to flash supersu all the files were gibberish (see pic), what am I missing?
If I wipe data it seems fine, but then I boot to system to copy the supersu file and once I load twrp it is gibberish again.
Also should I use SuperSU-v2.82-201705271822.zip or Magisk-v14.0.zip to root?
Appreciate any help I can get.
This mate is called encryption
Put the SuperSU zip on a SD card and you should be able to flash it without any problems if you use the latest beta release.
Magisk is another story.
Midhon58 said:
This mate is called encryption
Put the SuperSU zip on a SD card and you should be able to flash it without any problems if you use the latest beta release.
Magisk is another story.
Click to expand...
Click to collapse
yeah I figured as much.
Didn't think of using external SD, thanks, was about to try adb sideload, I assume it would have worked too.
Many thanks, the external sd did the trick
So I'm pretty new to the forums, and pretty new to the rooting scene in general, but I'd like to think I have a general idea what I'm doing (barely)
I'm trying to flash LineageOS on to my Pixel, and each time after flashing the ROM, I get stuck in a bootloop and can only access the bootloader, or I can access TWRP if I use "fastboot boot twrp.img"
Here's the tutorial I've followed to get root, I've followed it to a T:
-Flash stock image from google of whatever version you are going to be running (I went with ppr2 sailfish (as i have the pixel 1))
-Fastboot to twrp (I used version 3.2.3-1-sailfish)
-Flash TWRP.zip (NEXT STEPS ARE WHAT MADE THE DIFFERENCE)
-Do not just hit reboot after installing. Press the back button and go to the home screen of twrp again.
-Clcik the reboot there and click "Do Not Install" this is in reference to the TWRP application with which you don't want to install
-Now turn back off your device and go into twrp again
-Flash magisk 16.7 (NEXT STEPS ARE ALSO WHAT MADE THE DIFFERENCE)
-Do not hit reboot right after you intsall it or will be in a boot loop
-Go back to home screen, hit reboot then hit power off
-Wait a few seconds thens turn that ***** on.
Click to expand...
Click to collapse
And I've followed the directions directly from Lineage on how to flash the ROM. I've also tried flashing the verified boot signer afterwards, I've tried installing a different kernel that supposedly disables "dm-verity" (which seems like it might be the issue but I'm not sure)
I've tried changing the boot parameters from 'b' to 'a' with "fastboot set_active a"
I've tried numerous different steps and each time it's the same process. I get stuck in the bootloop with the bootloader, so I flash the stock image, then reinstall TWRP, Reinstall Magisk / Root, then try to install Lineage and get bootloops, rinse and repeat for the last 2 days. I'm completely at a loss. Any advice? It's much appreciated.
dylanfitz32 said:
So I'm pretty new to the forums, and pretty new to the rooting scene in general, but I'd like to think I have a general idea what I'm doing (barely)
I'm trying to flash LineageOS on to my Pixel, and each time after flashing the ROM, I get stuck in a bootloop and can only access the bootloader, or I can access TWRP if I use "fastboot boot twrp.img"
Here's the tutorial I've followed to get root, I've followed it to a T:
And I've followed the directions directly from Lineage on how to flash the ROM. I've also tried flashing the verified boot signer afterwards, I've tried installing a different kernel that supposedly disables "dm-verity" (which seems like it might be the issue but I'm not sure)
I've tried changing the boot parameters from 'b' to 'a' with "fastboot set_active a"
I've tried numerous different steps and each time it's the same process. I get stuck in the bootloop with the bootloader, so I flash the stock image, then reinstall TWRP, Reinstall Magisk / Root, then try to install Lineage and get bootloops, rinse and repeat for the last 2 days. I'm completely at a loss. Any advice? It's much appreciated.
Click to expand...
Click to collapse
i cant seem to flash any stock firmware on mine. keeps mentioning something about user data. i have tired ota and even factory images. did you get yours resolved? thanks
I recently bought an unlocked Moto G Play 2021 with the intent of learning how to flash custom rom's etc. The steps I've done so far are below.
Went to Motorola's site and got the code to unlock the bootloader
Waited for the "OEM Unlock" button to be available in the Developer Options menu.
Followed the directions Here to try to get an unofficial version of TWRP installed.
when I type fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img Using the vbmeta.img from the link above, I get some kind of anti-rollback error and can't boot to recovery.img
So far, what I've found says I need to be on Android 10 for this to work but I can't find a stock rom of Android 10 for this device. Electimon posts AOSP builds for this phone Here so I assume there's a way to get this to work, I just don't know what it is and I've gone through these threads a few times now and can't piece it together. Any assistance would be greatly appreciated.
Additionally, thanks Electimon for doing those AOSP builds.
Try to download Miracle Thunder Modified (Withouth Box) like there are other tools, but if not, just try to root. kind of for you to root, download the TWRP app and install or use Flashify to flash img using root
Luiz Vinicius said:
Try to download Miracle Thunder Modified (Withouth Box) like there are other tools, but if not, just try to root. kind of for you to root, download the TWRP app and install or use Flashify to flash img using root
Click to expand...
Click to collapse
I'm not sure entirely what happened, but after I used the TWRP app my phone bricked and I had to use the Lenovo rescue app on my pc to factory reset it.
First update your phone
Then download twrp from
https://forum.xda-developers.com/t/...st-port-but-everything-works-amazing.4330775/
Then adb reboot bootloader
Then fastboot flash recovery MotoGuamnaFixed2.img
then you have twrp installed then you can go thru the steps at
https://forum.xda-developers.com/t/rom-12-0-guamna-aosp-12-0-monthly-builds.4392303/#post-86610039
to get Android 12 couatom rom
svoc said:
First update your phone
Then download twrp from
https://forum.xda-developers.com/t/...st-port-but-everything-works-amazing.4330775/
Then adb reboot bootloader
Then fastboot flash recovery MotoGuamnaFixed2.img
then you have twrp installed then you can go thru the steps at
https://forum.xda-developers.com/t/rom-12-0-guamna-aosp-12-0-monthly-builds.4392303/#post-86610039
to get Android 12 couatom rom
Click to expand...
Click to collapse
Thank you for the response!
I made sure my phone was on wi-fi and checked for updates. I then rebooted to fastboot and flashed recovery to the MotoGuamnaFixed2.img. I still got a blank screen when I tried to reboot to recovery. I then rebooted to fastboot manually and did
fastboot flash recovery_a MotoGuamnaFixed2.img
fastboot flash recovery_b MotoGuamnaFixed2.img
It said ok both times, and when I try to reboot to recovery, I get a blank screen that I can't interact with. Pressing the power and volume buttons does nothing. Rebooting and letting the phone go through the boot process, to include waiting for the warning about the unlocked bootloader to go away results in a blank screen.
I also tried booting to fastboot and selecting "Recovery Mode" from the fastboot menu. Same result. That being said, I followed the instructions in the second link anyway, which are
fastboot -w
fastboot update (filename).zip
Now my phone has a blank screen I cannot interact with, but when I type "adb devices" I see the phone. Typing "adb shell ls -l" shows there is definitely a file structure there.
Just download the rom for the version that your device is unzip it and manual flash each one to the correct spot except recovery flash the twrp and then reboot and let me know look at flash file.xml to see where to flash each IMG and bin to make shur you download your rom and not another one for the same device but different carrier what it sounds like to me is happening is you downloaded the wrong ROM when you tried to do a force update
Send me a screenshot of your about device screen please I might need to make a change to a few things to get it working
I'm stuck in a boot loop right now. WIll the output from fastboot getvar work?
What carrier do you have
Download your rom first then follow my last post to get it back out of a bootloop
svoc said:
What carrier do you have
Click to expand...
Click to collapse
It's an unlocked phone, no carrier, no SIM. I did the factory reset with the Lenovo rescue tool and sent you the screen shot of the device info page.
Update - svoc has spent a crap ton of his personal time trying to help me with this. I've learned a bunch and wanted to publicly acknowledge his willingness to go way above and beyond trying to get this working.
I don't understand why I can't get twrp to boot I'm not for shut what the problem is if any one has any idea please let me and I will try
Big thanks to svoc for all the phone calls and troubleshooting my device, that is apparently possessed by at least 3 demons and a donkey. There are two links below. The first is the link to the intstructions that worked.
The second is to the compressed file that gave me a degoogled android. It's really, really basic and you'll have to side load the app store of your choice onto the device but it works.
*NOTE* I have not used a sim card or tested the cellular capability. If you do the things below and it doesn't work, reboot to bootloader and flash the radio.img with the one from your stock rom, which can be obtained from lolinet.
Any custom ROMs out there for Moto g play 2021 (guamna)?
Can't find any custom ROMs for this device. I guess it is too early. I'll probably have to get another phone. Can't even find a twrp for it. New to this. Any suggestions?
forum.xda-developers.com
https://github.com/phhusson/treble_experimentations/releases/download/v412/system-squeak-arm64-ab-vanilla.img.xz