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!
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:
EDIT:
In my way of trying to apply to warranty and flashing the stock package into the phone and Windows being Windows, I had problems using the batch script, it stopped for long time and didn't do nothing forcing me to restart the phone and restart the batch, until I uninstalled the driver and make Windows reinstall it automatically (manage devices) and it finally flashed it all, actually I flashed the package three times just to be sure lol. So, in the end I wanted to turn off the friggin phone because I was very done with it (what a PITA it has been) and wanted to apply for my warranty so as there is no command in fastboot to shutdown the phone I didn't know how to shut it down so I tried pressing Power button and releasing it the moment the screen goes off but I think I didn't do it right or the phone can't be shutdown that way (this is most probably the answer), well the phone rebooted and by the grace of Zeus it booted for the first time into MIUI and now is waiting for me to configure the phone, none of the times I flashed this packaged into the phone it booted into MIUI, never, and just when I want to turn the phone this thing boots, I don't know if I'm going to venture into flashing anything again being the phone how it is but goddamnit it was a real PITA, I had to use my old Redmi Note 3.
So, tl;dr: Flashed stock package, phone booted finally, all is OK for now.
====================================================================================================
====================================================================================================
Sooo, I was having problems with flashing stuff on this phone but I solved them and I was able to flash HavocOS, it was OK and I could use my phone kinda well (some reboots but nothing serious, or so I thought). So, until 12 hours ago my phone was having problems with the File Manager (I used FX app and also the stock one), it hanged and didn't respond and made the phone reboot itself a couple times, that was weird, actually the whole time I used this ROM I was having problems with my files, it used to took long time to read some files and I was thinking that maybe my SD was bad but apparently it's not. So, after the second reboot I was able to finally open the file manager but navigating through the SDCard was buggy and the app didn't show me any file (it show me an empty list) so I rebooted my phone manually (this time wasn't done by the phone itself) and now is when the phone never passed from the Havoc logo, I waited something close to 30 min and nothing, rebooted and waited 10 min and nothing, it still hanged on the logo, went into recovery to wipe everything and re-flash all and after doing all that and tried to boot to system my phone was booting to recovery and didn't past that, tried installing stock (flash_all script) and then installing recovery and everything again and nothing, it booted to recovery always. So there is when I realized I couldn't change anything in the slot A (at least to what boot refers), I can't install TWRP nor OrangeFox, I can do it in slot B, and even if I boot into recovery on slot B I can flash the zip installer, change the slot and try to boot to recovery from slot A but it boots to the bootloader, and yes, TWRP didn't output any error when flashing the installer.
Yes, the script flashes everything OK, well not everything, system and vendor partitions (A and B) I had to flash them manually because it gave me some errors with the script (reading errors, and yes I compared checksums so it was super weird) but in the end supposedly the stock ROM must have been installed, which I couldn't try because even after flashing everything on the script the phone was booting to bootloader, I didn't give importance to this because before I was able to flash and boot HavocOS I did the same thing because my phone was bootlooping into fastboot: I ran the script, flashed manually those images because it gave me the same errors, tried to boot to system and the phone booted to bootloader, didn't give a sheat, flashed OrangeFox recovery, ROM, recovery installer, GApps, nofde patch and then I was able to boot to HavocOS. But now this time I tried to install TWRP with fastboot command but it didn't worked, fastboot doesn't throw any errors while flashing, it reported:
Sending 'boot_a' (39780 KB) OKAY [ 1.042s]
Writing 'boot_a' OKAY [ 0.208s]
Finished. Total time: 1.263s
But if I try to boot into recovery it sends me to fastboot/bootloader, if I do this in the slot B I can successfully boot into recovery and, as I said, if I flash the installer, change the slot and reboot to recovery, my phone reboots to fastboot.
This has happened to someone else?
Does anybody knows of any solution?
I still have warranty (phone has less than 3 months) so I probably can flash the stock package and lock my bootloader so I can get my phone checked as probably it is a hardware failure, probably and hopefully .
Oh, and also I have to add that the recovery was also lagging sometimes (OrangeFox). Sometimes when I was looking into files on the SD, also when I pressed the "reboot system" button it hanged for half a minute and the it proceeded to reboot, and also once when I was flashing the nofde patch the phone also hanged and rebooted into recovery by itself. So this indicates that maybe is a hardware thing right? Because there is no way that the recovery could have gotten corrupted or something just out of the blue.
Yes. I'm another victim here... And now I can't install recovery on slot b either. Can't figure out what's wrong. This giving me such a hard time...
RthurPendragon said:
Yes. I'm another victim here... And now I can't install recovery on slot b either. Can't figure out what's wrong. This giving me such a hard time...
Click to expand...
Click to collapse
What I ultimately did was wipe everything on slot A, then wipe everything on slot B, then I proceeded to install the ROM on the slot A then re-flash the recovery and reboot to system and that's all. But I did had to wipe both slots A and B. If nothing works you can apply the original ROM (search for it on these forums) and go back to stock.
Jhon_Locke said:
What I ultimately did was wipe everything on slot A, then wipe everything on slot B, then I proceeded to install the ROM on the slot A then re-flash the recovery and reboot to system and that's all. But I did had to wipe both slots A and B. If nothing works you can apply the original ROM (search for it on these forums) and go back to stock.
Click to expand...
Click to collapse
In my case, I wiped system and installed Evolution X ROM (OSS version) with Custom Recovery (SHRP) Then when I want to reboot into recovery again to flash Magisk, There's no recovery... It always opens with fastboot mode. I tried flashing recovery.zip from slot b. Still no result.
Yes. I'm next victim here... And now I can't install recovery on slot b nor slot a. Can't figure out what's wrong. When i flash twrp recovery it flash successfully but when I boot into recovery it stuck in fastboot mode
Change slot and flash again but nothing worked it again stuck in fastboot mode even i flash different version of Twrp(3.2.1) but again it stuck in fastboot mode both a and b slot.
So i flashed stock rom and lock bootloader.
If have any solution how to install custom recovery please help me.
Thanks
Iamdchandan said:
Yes. I'm next victim here... And now I can't install recovery on slot b nor slot a. Can't figure out what's wrong. When i flash twrp recovery it flash successfully but when I boot into recovery it stuck in fastboot mode
Change slot and flash again but nothing worked it again stuck in fastboot mode even i flash different version of Twrp(3.2.1) but again it stuck in fastboot mode both a and b slot.
So i flashed stock rom and lock bootloader.
If have any solution how to install custom recovery please help me.
Thanks
Click to expand...
Click to collapse
Because there are 2 different twrp's.
One of which is for Android 9 and the other for Android 10. You are flashing the wrong one which is why you go to fastboot.
All documentation is on the applicable threads.
People need to stop blindly flashing stuff without reading the documentation or even know what they are doing.
So many people have bricked mi A3 because they don't read first
garylawwd said:
Because there are 2 different twrp's.
One of which is for Android 9 and the other for Android 10. You are flashing the wrong one which is why you go to fastboot.
All documentation is on the applicable threads.
People need to stop blindly flashing stuff without reading the documentation or even know what they are doing.
So many people have bricked mi A3 because they don't read first
Click to expand...
Click to collapse
I have flashed twrp latest 3.4.4 for Android 10 but it is stuck in fastboot mode either slot a or b.
What happened if i downgrade Android 10 to 9 and then flash twrp. Maybe it will successfully flashed.
Iamdchandan said:
I have flashed twrp latest 3.4.4 for Android 10 but it is stuck in fastboot mode either slot a or b.
What happened if i downgrade Android 10 to 9 and then flash twrp. Maybe it will successfully flashed.
Click to expand...
Click to collapse
Don't do it you will mess up your persist partition.
How are you flashing? You must be after typing something wrong
garylawwd said:
Because there are 2 different twrp's.
One of which is for Android 9 and the other for Android 10. You are flashing the wrong one which is why you go to fastboot.
All documentation is on the applicable threads.
People need to stop blindly flashing stuff without reading the documentation or even know what they are doing.
So many people have bricked mi A3 because they don't read first
Click to expand...
Click to collapse
garylawwd said:
Don't do it you will mess up your persist partition.
How are you flashing? You must be after typing something wrong
Click to expand...
Click to collapse
First if all reboot into fastboot mode then connect with pc then type command " fastboot flashing unlock" enter now again forcefully reboot into fastboot mode then type next command "fastboot flashing_critical unlock" now bootloader unlock.
Again reboot into fastboot mode then type command "fastboot getvar current-slot"
Now change current active slot and then type command " fastboot erase boot" . Now finally flashed twrp latest (3.4) for Android 10 with command "fastboot flash boot twrp.img" now it flash successfully then type command "fastboot reboot" and then press volume up then hit enter and it return in fastboot mode then i have again change slot and repeat all process with that slot but it again stuck in fastboot mode. After all i have changed twrp version but again same thing repeat so I flashed stock Android 10 through Mi flash and lock bootloader.
That's all whole process.
If do something wrong please help me to figure out.
Waiting for your reply ?.
Love
try sharp recovery
Sami Devo said:
try sharp recovery
Click to expand...
Click to collapse
I don't know installation process of sharp recovery.
Iamdchandan said:
I don't know installation process of sharp recovery.
Click to expand...
Click to collapse
install on the other slot... dont flash it on running rom slot... if rom running A.. chng it to B. then flash to B.. then goto recovery flash the sharp zip when sharp opens..then again chng slot to A.. running rom slot..
okk ur phn boots.
I was using Corvus OS (Android 10). After updating few apps on play store, one of them was maybe android framework related my phone stopped responding and got black screen errors. (I think a system UI crash). So i tried rebooting, got stuck on boot animation. when i went back to orangefox recovery, the phone was simply not responding to any touch even though i could see the files on my phone (orange fox homescreen). Please help ASAP. Thank You.
If someone is actually listening, i ended up clearing everything, installed new recovery, no luck. and sideloading rom returns with "error closed"
I really need some help guys. Please respond.
Sp_3ctr_3 said:
If someone is actually listening, i ended up clearing everything, installed new recovery, no luck. and sideloading rom returns with "error closed"
I really need some help guys. Please respond.
Click to expand...
Click to collapse
Did you format the data partition?
DarthJabba9 said:
Did you format the data partition?
Click to expand...
Click to collapse
#To format system partition
fastboot format system
#To format boot partition
fastboot format boot
#To format cache partition
fastboot format cache
#To format user data partition
fastboot format userdata
#To format recovery partition
fastboot format recovery
did all of these. thanks for responding almost lost all hopes.
DarthJabba9 said:
Did you format the data partition?
Click to expand...
Click to collapse
i managed to install twrp since i could only file .img of it. while trying to install my os using adb shell twrp sideload, the phone just disconnects when it starts installing vendor files after installing data ones.
Also, the adb shell returns Total Xfer 1.00x
Sp_3ctr_3 said:
i managed to install twrp since i could only file .img of it. while trying to install my os using adb shell twrp sideload, the phone just disconnects when it starts installing vendor files after installing data ones.
Also, the adb shell returns Total Xfer 1.00x
Click to expand...
Click to collapse
Yep, your system is well and truly messed up. Your best bet is to download a fastboot MIUI ROM and flash it with the Mi Flash tool. Just make sure that you don't accidentally lock your boot loader again (hint - after unpacking the fastboot ROM, first delete all .bat and .sh files with "lock" in their names before trying anything with Mi Flash).
https://play.google.com/store/apps/details?id=com.google.android.webview&hl=en_IN
I think this was the app that i update and later caused the crashes.
DarthJabba9 said:
Yep, your system is well and truly messed up. Your best bet is to download a fastboot MIUI ROM and flash it with the Mi Flash tool. Just make sure that you don't accidentally lock your boot loader again (hint - after unpacking the fastboot ROM, first delete all .bat and .sh files with "lock" in their names before trying anything with Mi Flash).
Click to expand...
Click to collapse
Alright, i will try that and respond. thanks for the reply.
DarthJabba9 said:
Yep, your system is well and truly messed up. Your best bet is to download a fastboot MIUI ROM and flash it with the Mi Flash tool. Just make sure that you don't accidentally lock your boot loader again (hint - after unpacking the fastboot ROM, first delete all .bat and .sh files with "lock" in their names before trying anything with Mi Flash).
Click to expand...
Click to collapse
Did this, succesfully flashed with Bootloader intact. Still touch is not responsive, all i can see is a black screen with "This Device is Locked, for security reasons you need to enter the password to verify the device" but i cant select any option since it wont respond to touch.
DarthJabba9 said:
Yep, your system is well and truly messed up. Your best bet is to download a fastboot MIUI ROM and flash it with the Mi Flash tool. Just make sure that you don't accidentally lock your boot loader again (hint - after unpacking the fastboot ROM, first delete all .bat and .sh files with "lock" in their names before trying anything with Mi Flash).
Click to expand...
Click to collapse
Woohoo thank you, my phone is working again t. Although i had to reinstall mi flash tool with bootloader back to off or locked, but atleast now i have a working phone. It seems during login screens sometimes the scree still remains unresponsive, but gets back to normal after 4-5 lock unlock screen routine. I will miss using root and other customization, but i guess it is what it is. Thanks again.
Have a nice day.
Sp_3ctr_3 said:
Woohoo thank you, my phone is working again t. Although i had to reinstall mi flash tool with bootloader back to off or locked, but atleast now i have a working phone. It seems during login screens sometimes the scree still remains unresponsive, but gets back to normal after 4-5 lock unlock screen routine. I will miss using root and other customization, but i guess it is what it is. Thanks again.
Have a nice day.
Click to expand...
Click to collapse
It is good that you have your device back! With regard to the bootloader, you can always go through the unlock procedure again.
PS: updating something from the Play Store should not cause a problem like this. It looks like corruption of the firmware, and/or the persist partition. Flashing a fastboot ROM via Mi Flash (the "flash all" option) should have solved the problem completely. If it didn't, then this might actually be a sign of impending hardware failure, rather than a mere corruption of partitions.
Which version of MIUI did you install?
due to my inexperience with rooting phones, i have managed to delete everything from my phone.
i mean everything.
the boot.img, recovery.img, system.img ... everything
the phone still boots to the bootloader but wont let me flash most partitions without booting into fastbootd.
fastbootd was part of the recovery image so i cant boot to it.
i can flash the boot partition for some reason and it will boot to it.
the phone bootloader was unlocked so it will boot anything from the boot partition.
due to me not knowing to change a setting in android, i cant flash the other partitions without first restoring the original software.
i cant do this without a recovery.
due to the same setting in android, i also cant boot any image through fastboot except the original stock boot image that is basicly useless to me.
i would think the solution to my problem would be to temporarily flash a recovery image to the boot partition and boot to fastbootd from there, but twrp and the stock image are both too large to fit in the boot partition.
is there some way i can get fastbootd in the boot partition?