I tried to re-flash my A50s with its original stock rom (from this website). I have tried these 2 roms :
A507FNXXU5DUG4 (Android 11)
A507FNXXU5CUB1 (Android 10)
Both failed to be flashed properly and sent me back to Download Mode with this error :
Code:
ODIN MODE (AVB Fail)
system : Error validating footer
Samsung System (installed rom series), (random number I don't understand)
VBMETA (installed rom series), (random number same as above)
As far as I understand, vbmeta failure is caused because Samsung fail to validate security on the rom. But my roms, both are original roms. If this information helps, I don't have TWRP installed because I was trying to go back to the unroot version. If even original stock roms fail, then I don't know where to go anymore from here. It's been hours and I'm frustrated. Any suggestion ?
Related
So, here is the problem i am facing with my moto E
I followed the tutorials from this site and had flashed my MOTO E to stock ROM 3-4 times due to different reasons, i was successfully able to do that using the STOCK ROM that i had for android kitkat 4.4.4. Last month i updated my moto E to android lollipop. After that it kept asking me to install a 12MB update which i tried installing quite some times but was not able to install. It showed some error while installing the same. So, i started ignoring that. A couple of days ago i once again tried to install that update and after installing the update when the phone turned on, it logged on into FASTBOOT MENU saying:
hab check failed for boot
failed to validate boot image
Fastboot reason: Fall-through from normal boot mode
So, i thought Flashing it once again might solve the issue. When i tried flashing it, on the command screen it gives ERROR for 4 files i.e. boot.img, system.img_sparsechunk.0, system.img_sparsechunk.1, system.img_sparsechunk.2 saying::
<bootloader> invalid signed image
<bootloader> preflash validation failed
And on my phone screen it says "Invalid PIV signed image"
For all other instructions it says OKAY
Now it is again and again turning ON into this fastboot mode only...
Since i already had flashed my moto using the same custom rom , i think the files must be okay...
PLEASE HELP :'(
Why did you flashed 4.4.4 and then ota updated to 5.1 ? This process should've bricked your device in the first place.
Anyway 5.1 stock image files are available, did you tried flashing them? (fastboot mode)
-z3r0- said:
Why did you flashed 4.4.4 and then ota updated to 5.1 ? This process should've bricked your device in the first place.
Anyway 5.1 stock image files are available, did you tried flashing them? (fastboot mode)
Click to expand...
Click to collapse
sorry, i didn't knew that i shouldn't update my phone after installing the stock rom. No i haven't tried flashing my phone with android 5.1 stock file, i thought maybe flashing my phone with android 4.4.4 will downgrade my phone back to kitkat. Will try it now...will be helpful to me if you could get me a link for android 5.1 stock file as well, i tried finding the same, but it says for moto e2 which comes originally with lollipop but mine comes with android 4.4, its so confusing for me which stock file to download....
thanks for the help
Here : http://forum.xda-developers.com/showthread.php?t=2755857
"RetailDSDS" - Is for Indian version
-z3r0- said:
Here : http://forum.xda-developers.com/showthread.php?t=2755857
"RetailDSDS" - Is for Indian version
Click to expand...
Click to collapse
tried it, still giving the same error, preflash validation error :'(
Hey there, i will try to write the essentials of my problem
At the moment i cant get TWRP installed no matter which way or which version at it seems....
Part 1 - How rooted the phone / installed TWRP at first
1) Updated Stock 8.2.10.0 to 8.5.4.0 (Android 7) via OTA update of the phone.
2) Found out after the update that my sim card does not work and could not find any solution to this
(only sms worked, the signal is at 100%, sometimes at "X", and cant use mobile internet or get/make calls + also tried other cards which did not work)
3) Decided to Unlock the Phone and Root it (Working at the moment).
4) Flashed TWRP (newsest version of official website).
Part 2 - How the Flashing of the Rom did end in boot-stuck
5) Backupped (Bugged) 8.5.4.0 Phone
6) Wiped System, Data, Cache, Dalvik. Then flashed official Qualcomm 8.2.10.0 Image.
7) Phone tried one hour to boot, then i decided it wont start ever / bugged and rebooted it.
8) Tried to install the rom several times, with more wipes, with many reboots and also with the new 8.5.4.0 rom again. But phone keeps hanging at Boot.
9) Finally i used the (bugged) full backup of 8.5.4.0and had my old phone back at least, but with the sim bug again ... and without custom recovery as u will read now.
Part 3 - Other approaches of rescuing the phone
9) Tried to flash an older TRWP version (Cofface or something) via Minimal ADB cause i read that maybe the twrp version is making troubles.
10) Restarting into Recovery brings only the Fastboot (Vol Up + Power AND Vol down + Power) ,,, so nothing installed
11) Tried like 10 different img of twrp - restarted -> no Recovery installed
12) Tried Flashify app -> No Recovery installed...
Part 4 - Errors i had while flashing recovery (only when using the "boot imgname.img" command)
i rmember one error (after typing the above command for the first time): "FAILED dtb not found"
and one time i receiverd (i think the 2nd time above command in a row): "FAILED: read failed - too many links"
The install of the recoveries itself never showed an error by the way. That worked regarding cmd log.
Update 1: Flashing stock recovery works. Only thing that worked so far...
Used a guide on the english miui site (cant post links cause i got a new account)
Basically just the same procedure but with stock img.
So im here now, with a 8.5.4.0 working, but not able to phone/mobile internet Redmi Note 4 Global.
And im getting out of ideas. Please help
I've been messing with root on my G965F and, after a few ROM changes a decided to return to One UI, but my camera simply doesn't work. I'de flashed the CSB3 vendor image in order to install pixel experience ROM.
At the time I did my One UI backup, but I didn't save the original vendor Image, and now I can't completely restore it. Therfor my camera refuses to function.
I've tried restoring my device using odin, but becouse I've TWRP installed it gave me an error (a very scary one), "an error has occurred while updating the device software s9+...". It prompet me to use Smart switch emergency recovery which failed to recognise my device. My solution was to flash TWRP again (Fortunately it worked, and I was back to TWRP).
I restored my one UI backup without the vendor image, and the camera still doesn't work.
If I understood this corectly, if I restore my vendor image the camera will fuction back again. But I'am open to sugestions.
Thanks
RichNoob said:
I've been messing with root on my G965F and, after a few ROM changes a decided to return to One UI, but my camera simply doesn't work. I'de flashed the CSB3 vendor image in order to install pixel experience ROM.
At the time I did my One UI backup, but I didn't save the original vendor Image, and now I can't completely restore it. Therfor my camera refuses to function.
I've tried restoring my device using odin, but becouse I've TWRP installed it gave me an error (a very scary one), "an error has occurred while updating the device software s9+...". It prompet me to use Smart switch emergency recovery which failed to recognise my device. My solution was to flash TWRP again (Fortunately it worked, and I was back to TWRP).
I restored my one UI backup without the vendor image, and the camera still doesn't work.
If I understood this corectly, if I restore my vendor image the camera will fuction back again. But I'am open to sugestions.
Thanks
Click to expand...
Click to collapse
Simply, copy your data and download the official pie from samfirm or where you want and flash it with the latest odin.. have a thread about latest pie for s9 plus you can chek it..
forkatar12 said:
Simply, copy your data and download the official pie from samfirm or where you want and flash it with the latest odin.. have a thread about latest pie for s9 plus you can chek it..
Click to expand...
Click to collapse
I already tried that. But when I attempt to flash it using odin it gives me an error on my phone "SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 4 BINARY: 3".
I might be wrong, but to my understanding from your last post you tried to install an original firmware image with bootloader v3 while your phone already has a bootloader v4. If I understand everything correctly you need to use a firmware version (for your region) containing a bootloader v4 for it to install correctly - otherwise it won't install since bootloaders aren't backwards compatible.
Hello everybody!
Unfortunately my cell phone has a softbrick and I don't know how to fix it.
Starting position (unlocked bootloader):
I was on 10.0.7 Xiaomi.eu ROM (worked very well) and installed LuckyPatcher. After patching a file in LuckyPatcher, a reboot came and it took a long time, after the reboot, both SIM cards no longer worked and no WLAN.
Then I installed the Xiaomi.eu ROM with TWRP again - same error, then the original FastbootROM - same error.
I entered + # 06 # in the phone app and lo and behold, the phone no longer has an IMEI.
I hope someone can help me.
I have a TWRP backup, I restored the EFS but nothing changed. HOW can I extract modemst1.bin and modemst2.bin from efs1.emmc.win and efs1.emmc.win.sha2?
Regards Mirakulixs
1. try flashing original boot image without magisk (idk... worth a try, that's what I do when I boot loop because of some crap I installed, though I didn't check if I somehow lost my IMEI)
2. try flashing stock rom using miflash
Hey (same error is no IMEI´s and no Mac-Adress and Baseband is unknown)
to point 1 - same error
to point 2 - same error
try to flash zip with twrp.. - same error
with mi flash fastbook rom - same error
After serveral flashing problems to lineageos, i want to go back with odin and the stock rom.
its stuck
and I get the error msg on the S9+ bootloader screen "Kernel Rev. Check Fail Device: 17, Binary: 6 (Recovery)"
i check this on other images, like userdata and i get the same error (Userdata)
i solved the problem w/ binary files
SOLVED