bootloop, footer is wrong, signature verification fail, device: lenovo YT3-X50L - Android Q&A, Help & Troubleshooting

Hi.
I've tried to install TWRP by Flashy (rooted by kingoroot), unfortunately device stuck on bootloop and only thing i can run is a stock recovery, but i can't install any zip because of signature fail, sam situation with adb flashing, what shall i do to abort looped "update" process or just reflash device ( Qcom is not finding my tablet) and i cant find any flash compatibile with SP_Flash).
Maybe there is some way to force memory format to erase whole flash or some other way?

Related

file system changed after LinageOS - HELP

friends
i have Redmi3 and i installed lineage OS 14 via twrp3.0.2
I didnt not enjoy much and when i tried flashing miui8.1 ( android 5.1.1 ) back to redmi3 via twrp. it gives signature error Or sometimes it give internal storage cannot mount error.
is there a way to install miui8 now?
- miflash also gives invalid partion directory error. the device don't go in to DOWNLOAD mod any more via pressing volumeup+power key...
EDL
I'm having trouble with this too, can anyone help?
What miui version you try to flash? Official, xiaomi.eu?
I had trouble too...
Yes, this problem doing me Lineage too. I can´t boot or instal MIUI, whole phone is bricked, no TWRP, locked again...
I must flash fastboot ROM in EDL mode with MiFlash and doing all again, unblock bootloader, install TWRP and install some good ROM...

problem with TWRP ZCX flashing

So guys this is my scenario....
1)i was using slimrom 7.1.2 before a week
2)then came back to the final MIUI 8 dev rom(7.8.something) (marshmallow)to try out xposed again
3)then today i flashed AOSP oreo
4)on booting it asked for my previous screen lock password...when i entered it, it gave an error stating "ur password is correct but ur data is corrupt so u need to format ur phone to continue"
5)as i had some files on internal i force restarted it to TWRP and tried to flash the same version of slimrom again but it ended with an error "ZIP signature verification"....
6)this same error shows up when trying to flash any custom rom
7)currently i have disabled "zip signature verification" option in ZCX twrp settings
Can anyone tell me what is causing the ZIP SIGNATURE VERIFICATION FAILED error??....
I face this password error from official miui developer to MCaosp oreo rom.
I tried some twrp recovery like zcx and inline and red wolf. but no result.
how can I flash oero roms?
solved: I did Format data (not wipe data) and I pass enter password error.
I had the same problem but with official twrp, try flashing another recovery or,
You can copy your to pc while in TWRP and then format data, format system, install custom rom,
If it didn't work, flash latest stable miui firmware, unlock bootloader, install twrp, install custom rom, It'll work.
Thanks guys....but I can't even flash any nougat or marshmallow based ROMs...always ends up with ZIP SIGNATURE VERIFICATION error...any idea what caused this error....previously I was able to flash without this error...only solution I found so far is to disable the zip signature verification setting in twrp menu
Bootloader Locked
So basically the problem is that the bootloader has been locked or the data has been encrypted by the previous rom so to solve this problem and the signature error what you need to do is go twrp and hit wipe->format data ..then it will ask you to type "yes"....
BY PRESSING THE "YES " IT WILL FORMAT EVERYTHING IN THE STORAGE...I REPEAT DO TAKE A BACKUP OF DATA BEFORE DOING THIS...
after the wiping process is done the encryption is removed so now the internal storage is empty so make sure you have rom in SD card so flash the ROM and the gapps and you are good to go..
Hope this solved your problem..
Thanks vamskiri....will try it
Here read this.
You flashed miui dev (official) so what offcial dev roms do is they encrypt your phone (idk why) but it automatically decrypts while updating through OTA. And as it is encrypted and it automatically decrypts in OTA updates, so to use another custom roms you've to decrypt it by yourself but neither you or I know the decryption password. So the only option you have now is to format data / factory reset. (IT WILL WIPE EVERY LAST FILE EXCLUDING SYSTEM) :good:

REDMI NOTE 4X MTK / Issu with trying to flash TWRP

Hello everyone,
I have a redmi note 4X with MTK soc
The bootloader is unlocked.
I want to flash TWRP recovery. I use adb, the "nickel " TWRP, and message in the cmd window was "ok"
but when i reboot, whatever the way (buttons or adb reboot), it still reboot on the stock recovery.
I've tryed many times, even with a "moly" TWRP (with my MI 4S, the "aqua" didn't work and I had to flash the "libra" one and it was all effective)
Tryed to re install adb, etc. Wathever, it's always "ok" in adb but still reboot on the stock recovery.
Can't try with flashtool or that kind of (Mitool Flash atc) because I can't find the right "scatter" files....
Does anyone have a clue? what is blocking?
Thanks for help
You must reboot back to recovery, not to system, after installing TWRP.
1. Install TWRP
2. Reboot to Recovery (not to system) - this means you will see TWRP screen again
3. Now you can reboot to System
This is only done for the first time installing TWRP. Next time, TWRP will always be there.
Hello,
Well please I need new help !!
Now I'm fighting a new issu !! Now that I at last managed to flash TWRP, and enter in this custom recovery, my phone don't boot system anymore !! stay stuck on the MI logo (
Do I need to flash the boot.img ? But why the hell would a recovery flashing would have change the boot partition??
And if so, where please could I find the boot.img for MIUI 10.1 stable?
Hello,
For those who have the same issu.
I've flashed a boot.img file found in unzipped miui rom zip.
- download from xiaomi.eu the right rom
- unzip
- find the boot.img file
- flash it with adb / fastboot
Well, So now I have my phone and datas back, and can boot on a custom recovery; but TWRP don't work well. Doesn"t keep the settings, can't install anything (it doesn't find any file when exploring ) and can't wipe cache (as if it can't read partition). That's all I tryed by now, I despair a little and that's a lot of time for an easy thing (was very easy on other phones)
Well, this time I'm flooded, i' ll take somme time but don't give up trying to root that phone
Start again, and I recommend ZCX-TWRP-3.0.2-X-REDMI_NOTE4-MTK_Nikel-16.11.18.img and Magisk instead of SuperSU
https://xiaomifirmware.com/downloads/twrp-custom-recovery-redmi-note-4-mtk/

Cannot do OTA update. Flashing stock boot.img causes error

It's a tale as old as time. I have a functioning A3 with TWRP and magisk installed. OTA Jan security update failed. "Installation problem" was all it said. I expected this. I think all my magisk mods are systemless but I did flash a custom kernel in TWRP to get kcal.
Ok I'd gone through this for the December update. I downloaded fastboot ROM and extracted the boot.img. I made sure it was correct. Laurel sprout V10.3.13.0.PFQEUXM. But flashing it with either TWRP or fastboot I got the dreaded error screen on reboot where your options are try again or factory reset. Yes I flashed into the active slot. Even when I chose to factory reset and started fresh, I still got the same error when I tried to update.
I also tried to flash boot+system but also got same corrupted error. I tried using flash_all_except_data_storage but got an antirollback error. I've gone back to a nandroid backup for now but obviously I need to get this sorted out before the Android 10 update.
Any ideas? Thanks
Mi A3 doesn't have anti rollback mechanism as far as I know. If you installed TWRP, you also most probably enabled "allow system modifications" (there is a one time prompt on the first start of TWRP, pretty much everyone just dismisses it without reading). TWRP remembers this setting and for each subsequent boot into TWRP it automatically mounts system as R/W, breaking OTA even if you don't flash anything.
You need to reflash stock fastboot images for boot and system with the same version as you're currently running. If you are getting data corruption error, it usually happens when you flash system image from incorrect region or versions differ too much (you're flashing too old image).
Don't install TWRP (or make sure that you delete its settings first and then do NOT allow system modifications).
As you already performed a factory reset, I'd start from fresh state again - switch to active slot A and reflash whole ROM from fastboot, including data wipe (flash_all.bat if I'm not mistaken, but I don't have it in front of me, so double-check its content that it doesn't lock your bootloader).

Can't install TWRP without rooting; need... better drivers...?

Followed the instructions on several websites such as this one here at XDA:
https://www.xda-developers.com/how-to-install-twrp/
All goes well until I get to this line:
fastboot flash recovery recovery.img (latest TWRP image, renamed)
The command prompt window just sits there and says "(waiting for any device)"...
Most websites and forum threads seem to indicate that this is a problem with the drivers. Can anyone confirm?
FWIW, I did a total reflash of the latest stock ROM from this thread:
https://forum.xda-developers.com/ga...icial-stock-fw-update-odin-thread-xx-t3825204
so I currently have only the "stock" recovery.
I'd rather not root it quite yet. Help please?
P.S. The phone shows up in Device Manager and for "adb devices"; the phone's bootloader has been unlocked... can't see what I'm missing... I'm using a Windows 10 computer... I removed any screen locking mechanisms (PIN, fingerprint, etc.)...
Follow this instructions https://forum.xda-developers.com/galaxy-note-9/development/recovery-twrp-galaxy-note9-exynos-t4097441
Most samsung device use odin to install twrp
ACC18 said:
Follow this instructions https://forum.xda-developers.com/galaxy-note-9/development/recovery-twrp-galaxy-note9-exynos-t4097441
Most samsung device use odin to install twrp
Click to expand...
Click to collapse
Thanks. I'm trying it with 3.4.0-0
Do I flash this file while I'm still in TWRP? Or do I reboot the phone and go back *into* TWRP to flash it?
>After booting in TWRP download and flash no-verity-opt-encrypt-6.1 zip to disable data partition encryption
Edit: I tried flashing no-verity-opt while still in TWRP. Got the dreaded:
"Verification failed.
Unable to restart your device. The integrity verification has failed. You need to reset your device to factory default settings. This will erase all your data."​
I *really* tried to follow the instructions exactly, and think I did.
Was it because I tried to flash 3.4.0-0...?
I am currently re-flashing the stock firmware again.
Dougmeister said:
Thanks. I'm trying it with 3.4.0-0
Do I flash this file while I'm still in TWRP? Or do I reboot the phone and go back *into* TWRP to flash it?
>After booting in TWRP download and flash no-verity-opt-encrypt-6.1 zip to disable data partition encryption
Edit: I tried flashing no-verity-opt while still in TWRP. Got the dreaded:
"Verification failed.
Unable to restart your device. The integrity verification has failed. You need to reset your device to factory default settings. This will erase all your data."​
I *really* tried to follow the instructions exactly, and think I did.
Was it because I tried to flash 3.4.0-0...?
I am currently re-flashing the stock firmware again.
Click to expand...
Click to collapse
You need to format data after install twrp. This is avoiding internal data encrypted.
After twrp installed, do format data from twrp. Of course all of ur data on internal erased. And then take custom rom. I suggest devbase rom, this have "no verity encrypt" when u install this rom. Devbase is stock firmware for easy upgrade for rooted phone. And this is easy to install for beginner
Sorry for bad English
ACC18 said:
You need to format data after install twrp. This is avoiding internal data encrypted.
After twrp installed, do format data from twrp. Of course all of ur data on internal erased. And then take custom rom. I suggest devbase rom, this have "no verity encrypt" when u install this rom. Devbase is stock firmware for easy upgrade for rooted phone. And this is easy to install for beginner
Sorry for bad English
Click to expand...
Click to collapse
No worries. Thank you for your help.
I use Odin to install the Devbase ROM, right? Or can I use TWRP?
Edit: apparently it works just fine to install it with TWRP.
Thank you so much. This time TWRP works just fine for me and the new ROM is great.

Categories

Resources