I have a N950U device and I was trying to get twrp on it, though when I did it I went into the stock recovery mode and tried doing it through "Install updates through SD Card".
It didn't work (obviously) and now I keep getting the dm-verity verification failed, also I can't adb sideload or install through SD anymore.
I tried getting twrp through odin but I keep getting "SECURE CHECK FAIL: RECOVERY"
I tried re installing the stock rom through odin but I keep getting "SE REV CHECK FAIL: [abl]Fused 6 Binary 4"
Before the bootloop started happening I wasn't able to unlock the bootloader, though I got usb debugging enabled. If there is a fix to this please let me know, I've looked everywhere and I can't find an answer. Thanks
EDIT: I flashed the AP from the stock image and it worked. Not sure why, but it's working fine now.
Lazer_Lemon said:
I have a N950U device and I was trying to get twrp on it, though when I did it I went into the stock recovery mode and tried doing it through "Install updates through SD Card".
It didn't work (obviously) and now I keep getting the dm-verity verification failed, also I can't adb sideload or install through SD anymore.
I tried getting twrp through odin but I keep getting "SECURE CHECK FAIL: RECOVERY"
I tried re installing the stock rom through odin but I keep getting "SE REV CHECK FAIL: [abl]Fused 6 Binary 4"
Before the bootloop started happening I wasn't able to unlock the bootloader, though I got usb debugging enabled. If there is a fix to this please let me know, I've looked everywhere and I can't find an answer. Thanks
EDIT: I flashed the AP from the stock image and it worked. Not sure why, but it's working fine now.
Click to expand...
Click to collapse
Lmfao @ trying to unlock the Snapdragon bootloader and trying to flash twrp!!! Haha!! Apparently you don't bother to read NOTHING before just blindly flashing stuff.. You WILL brick it if you keep that up!! Learn to do research before doing stuff like that!
Related
I recently exchanged my Nexus One for another guy's N-1 which works on ATT 3G. I had done a nandroid backup of my phone, and used that same image to recover the "new" phone to exactly how it was before the switch. It failed first, but after I moved my BCDS folder to the new HTPXXX folder, it went through.
However, now when I try to flash a zip from recovery (Amon-RA 2.2.1), I always get the "Signature verification failed" error. I tried flashing newer radio, after verifying the MD5SUM. I tried flashing the 0.35.017 HBoot. Both of them failed. I am wondering if it's because of the mismatched nandroid recovery I did.
Any help would be greatly appreciated -- thanks!
Edit: Needless to say, after disabling signature verification, everything flashes correctly.
I doubt that it would be the ROM cause it shouldn't mater while your in recovery. So I would try reflashing your recovery through ROM manager, terminal or fastboot if your bootloader is unlocked.
Dude Random21 said:
I doubt that it would be the ROM cause it shouldn't mater while your in recovery. So I would try reflashing your recovery through ROM manager, terminal or fastboot if your bootloader is unlocked.
Click to expand...
Click to collapse
Thank you, nice idea -- I never thought about reflashing the recovery. I'll try this tonight! Thanks.
I am trying to flash the factory RUU so I can get the 4.3 update. The RUU kept failing, I was getting an error. Something to the effect of FAILED 12 signature verify fail. Well in an effort to figure this out I tried different roms and locking and unlocking my bootloader. Now the problem is I am stuck in a bootloop. I can boot into TWRP, but when I try to sideload a rom it says failed. If I try to factory reset it fails. I don't know how to get out of the problem I'm having.
EDIT: I am out of the bootloop, but I am still unable to run the Ruu. Feel free to delete this post and I will create a new one.
Hello, and thank you all for reading and trying to help. Let me explain the situation..
all working until i accidently went into dev options and forgot to turn the OEM Bootloader Unlock back on. Reboot and FRP fail. Yes rookie error.
So after trying to reflash stock firmware (U5), reboot into stock recovery and dm-verity error occurs. FRP lock is on so i cannot flash TWRP and im all out of ideas...
things ive tried.
tried multipule combinations of flashing boot.img, repacking stocks with and without certain img contents etc and reflashing. Maybe i havnt found the right combination?
reflashing stock firmware (N920IDVU5CRK2_N920ITEL5CRK1_TEL), and wiping DATA from recovery after ODIN PASS. Just noticed the other day if i do the recovery key combo after its first initial boot during the 'installing update' screen, it will pose a 'no command' screen, then after a few moments dumps me into the recovery with a dm-verity successfull. But if i reboot again it will dm-verity error. So i was thinking maybe i need to hit download mode after the successful dm-verity and flash without recovery.img. Not sure as my lack of understanding but id love to fix this.
any help, suggestions would be appreciated and if any further information is needed im more than happy to provide.
(phone is out of warrenty)
(currently binary 5 and using stocks from sammobile)
Try root with ctautoroot
Sent from my Redmi Note 8 using Tapatalk
I'm trying to flash TWRP on the phone.
I unlocked OEM bootloader and enabled USB debugging.
I also waited for the 7 days to be able to flash.
When I try to flash TWRP I get an error: "error validating footer (6)". It was going into a download mode loop so I reinstalled stock rom which is now running again.
Does anyone have advise on the error that I'm getting?
lintwurm said:
I'm trying to flash TWRP on the phone.
I unlocked OEM bootloader and enabled USB debugging.
I also waited for the 7 days to be able to flash.
When I try to flash TWRP I get an error: "error validating footer (6)". It was going into a download mode loop so I reinstalled stock rom which is now running again.
Does anyone have advise on the error that I'm getting?
Click to expand...
Click to collapse
Have you disabled auto reboot in odin? Always do that when flashing twrp.
Also do you have other twrp version to flash?
Also try redownloading twrp as your twro moght be corrupted.
LR7875 said:
Have you disabled auto reboot in odin? Always do that when flashing twrp.
Also do you have other twrp version to flash?
Also try redownloading twrp as your twro moght be corrupted.
Click to expand...
Click to collapse
Thank you so much for your reply! I did redownload TWRP and the same error occurred.
I tried with auto reboot disabled but get an error message: "Error validating footer (6)
CUSTOM RECOVERY
VBMETA " and then some numbers...
Thanks again!
I tried again with auto reboot disabled.
I then restarted the phone by pressing vol down+power.
As soon as the screen went black I then held vol up+power and got the error:
"Error validating footer (6)
CUSTOM RECOVERY
VBMETA " and then some numbers...
Maybe I'll try with an older version of TWRP...
Try this.
[GUIDE] Flash TWRP 3.4.0.0 and Root Android 10 ( Fix vbmeta error )
Disclaimer I'm not responsible if something went wrong on your phone(Usually nothing goes wrong). You are doing this on your own responsibility. Installing TWRP and Rooting may void warranty. The bootloader must be unlocked, if not watch this...
forum.xda-developers.com
LR7875 said:
Try this.
[GUIDE] Flash TWRP 3.4.0.0 and Root Android 10 ( Fix vbmeta error )
Disclaimer I'm not responsible if something went wrong on your phone(Usually nothing goes wrong). You are doing this on your own responsibility. Installing TWRP and Rooting may void warranty. The bootloader must be unlocked, if not watch this...
forum.xda-developers.com
Click to expand...
Click to collapse
I will try that later tonight thanks!
Tried updating the S8 to latest firmware and it failed. I am not stuck in a boot loop where attempting to get back into download mode results with
"An error has occurred while updating the device software"
I can't seem to do anything else. Does anyone know of a way to recover from this or am I SOL?
cbb77 said:
Tried updating the S8 to latest firmware and it failed. I am not stuck in a boot loop where attempting to get back into download mode results with
"An error has occurred while updating the device software"
I can't seem to do anything else. Does anyone know of a way to recover from this or am I SOL?
Click to expand...
Click to collapse
First you can try is wiping cache through stock recovery, and try to boot, if this doesn't solve it, you must need to factory reset (your data will be gone), try to boot, if this doesn't fix it, then flash the last firmware you had previously the failed update. Also, if you don't want to lose your data, you can try only the first step, and if this doesn't fix it, flash the latest firmware that was working previously to the failed update, and untick the userdata partition in Odin.
Ok, so it looks like I am back up and running. I did not realize that although I had this error, Odin was still able to communicate with the tablet. Thus I flashed the latest firmware again and now I am back up and running. Lost everything, but didn't have anything important, and what was semi-important, already had on the SD. I am at least happy I don't have an expensive paperweight.