New answers tagged rom-flashing
As it's obviously the stock recovery you've used to flash CM, that won't work as it will do a signature check and thus reject the ZIP as being invalid. So here's what you do instead: put cm-12.1-20151117-SNAPSHOT-YOG7DAO1K9-falcon.zip onto your device's SD card boot into bootloader now boot (not install) TWRP: fastboot boot twrp-3.0.2-0-falcon.img TWRP ...
Summing up the solution from the comments, as neither OP nor the "solution provider" posted an answer: Per Johnny Wrights recommendation I was trying to update TWRP to 126.96.36.199: Plug in the phone to the PC via USB and make sure the phone is in FASTBOOT USB mode from the bootloader menu. On the PC, I installed "Minimal ADB and Fastboot". Running that from ...
In my case, removing TWRP and reinstalling it solved the issue: install stock recovery to replace the installed TWRP install TWRP again so it replaces the stock recovery After that, my device booted up normally.
Issues like this this are often corrected by returning to a "known good configuration" before processing additional changes. I would suggest returning to the current official Google firmware via fastboot, then verify the device is booting and operating properly, then you can flash custom recovery and install a third party ROM such as CyanogenMod. ...
Download research download tools, load the pac file and go in settings there you must see alls files into the pac, now it's very important: double click on system location and copy, go in your file manager, enable hidden files and paste what you have copy in file location bar in your file manager you will see all needed files
This may help some folks: In my case the error was caused by a corrupt copy of the data file to the USB drive. On the offchance that I had yanked the USB out too early, I recopied, and after that the "whole-file signature" was OK and allowed the firmware update to complete.
Had the same poblem after updating from CM12 to CM13. Here is how I was able to fix it: I removed these two directories /data/user/0/com.android.providers.telephony /data/data/com.android.phone/ completly from my phone (Nexus 5). I used ES Explorer to do so, I had to turn on Root Mode and Show Hidden Files to be able to delete files in that directory. ...
Hey I had the same problem I tried everything. Then I did this - I downloaded ruu file for my m8 and it works like a charm now . You just have to run the ruu file on windows while your phone is connected. Beware finding the right ruu files takes time. And also it requires you to be on the correct mid and Cid that came with your phone (or the developer Cid ...
Odin is believed to be a leaked Samsung internal tool as you can see from Wiki . That's the reason you will not find a definitive,official website for downloading What is the ODIN tool? is a related answer and the point worth bearing in mind while choosing the right version is (....) you probably want to ensure someone else has tried it and succeeded ...
Don't do update. Do a command in the following syntax: fastboot flash [system/recovery/boot] /path/to/recovery/image.img Example: fastboot flash recovery /mnt/sdcard/Download/twrp.img I HIGHLY recommend not flashing images to system or boot partitions without a custom recovery first. You should only flash recoveries via fastboot.
I had the same problem here: archive does not contain android-info.txt. Tried google but can't find anything. Finally I copied the update.zip to my devices sdcard and "applied update from sdcard" – that worked.
Top 50 recent answers are included