Can anyone please share MD5 or sha256sum of twrp-3.3.1-0-cepheus.img file by which they successfully installed and boot into twrp?
Yes, got it. It has been uploaded on the site as I yesterday requested.
Thanks.
Related
Please post an MD5 or SHA checksum with every file you post, or link to!
This will allow downloaders to verify that they received the file intact. Flashing corrupt files is a bad thing.
On Mac OS X and Linux, use /usr/bin/shasum, like so:
Code:
$ shasum motoboot.bin
fda1fdbfd70628cbf1c79361525168847a00830b motoboot.bin
On Windows, use a tool like one of the following:
http://corz.org/windows/software/checksum/
http://www.fastsum.com/press/md5-hash.php
Don't worry about what you use, computed checksums will match across platforms.
Thank you!
Hello,
maybe this is a feature request or bug report, I don't really know:
Can you ditch the full path inside the md5sum files found at: dl.omnirom.org?
eg, from:
Code:
c9ac67ba61c7e654c5891c693a50d931 /home/build/omni/out/target/product/flo/omni-4.4.2-20131225-flo-NIGHTLY.zip
to leaving only the filename:
Code:
c9ac67ba61c7e654c5891c693a50d931 omni-4.4.2-20131225-flo-NIGHTLY.zip
Since I always check the md5 sum before I flash a new ROM I'll have to edit the .md5sum files manually after each download.
Otherwise the commandline utility md5sum -c failes because the file could not be found.
Additionally, can you place the appropriate md5sum file along with the ROM Zip in the opendelta folder? TWRP would check the file if a md5sum file is found.
Happy Holidays!
seXneo said:
Hello,
maybe this is a feature request or bug report, I don't really know:
Can you ditch the full path inside the md5sum files found at: dl.omnirom.org?
eg, from:
Code:
c9ac67ba61c7e654c5891c693a50d931 /home/build/omni/out/target/product/flo/omni-4.4.2-20131225-flo-NIGHTLY.zip
to leaving only the filename:
Code:
c9ac67ba61c7e654c5891c693a50d931 omni-4.4.2-20131225-flo-NIGHTLY.zip
Since I always check the md5 sum before I flash a new ROM I'll have to edit the .md5sum files manually after each download.
Otherwise the commandline utility md5sum -c failes because the file could not be found.
Additionally, can you place the appropriate md5sum file along with the ROM Zip in the opendelta folder? TWRP would check the file if a md5sum file is found.
Happy Holidays!
Click to expand...
Click to collapse
OpenDelta already checks the MD5 when download/patching - if the MD5's don't match nothing will be flashed. Doing it again inside recovery would just be a waste of CPU. If secure mode is enabled, whole-file signature verification is also done inside recovery, which also guarantees the file to be correct.
In other words, it would not be any use.
However, if I download the rom zip, and am planing on hacking it before installing the updated image, having the edit the md5sum file before I can verify the download using it is still an issue, not to mention the simple case of initial install, and I like having a few installable zips around in case I need to reinstall.
Hi,
just had a bad experience with the updater today. Due to a bad connection the downloaded zip files were corrupt causing the updater to try and abort every time.
Why not let the OTA Upgrade also download a associated MD5 file for each Upgrade ZIP? TWRP's default action if a .md5 file present is to check the file CRC before trying to apply a upgrade. If md5 is wrong it will be skipped.
a little change for a better upgrade process.
Thanks
Best person to answer this one is @Chainfire
solarizde said:
Hi,
just had a bad experience with the updater today. Due to a bad connection the downloaded zip files were corrupt causing the updater to try and abort every time.
Why not let the OTA Upgrade also download a associated MD5 file for each Upgrade ZIP? TWRP's default action if a .md5 file present is to check the file CRC before trying to apply a upgrade. If md5 is wrong it will be skipped.
a little change for a better upgrade process.
Thanks
Click to expand...
Click to collapse
MD5 is already checked I think. Are you sure it aborts because of that? Have you tried turning off secure flashing thing?
XpLoDWilD said:
MD5 is already checked I think. Are you sure it aborts because of that? Have you tried turning off secure flashing thing?
Click to expand...
Click to collapse
What I mean is placing the MD5 file on download to the zip file. Currenty TWRP is lcearly stating "No md5 file" so the CRC check is skipped. The problem was that one of my downloaded zip files was corrupt but it still startet to unpack it unfortunately it broke at 80% and left my device in a unfinished update state. This should never happen. Luckily I was able to recover by installing the latest full omni download which was still on the SD Card.
So my post here is just a suggestion to also add a .md5 file for each automatically downloaded zip update. There is not much more to do then this because twrp will do the remaining work and check CRC before starting extraction.
solarizde said:
What I mean is placing the MD5 file on download to the zip file. Currenty TWRP is lcearly stating "No md5 file" so the CRC check is skipped. The problem was that one of my downloaded zip files was corrupt but it still startet to unpack it unfortunately it broke at 80% and left my device in a unfinished update state. This should never happen. Luckily I was able to recover by installing the latest full omni download which was still on the SD Card.
So my post here is just a suggestion to also add a .md5 file for each automatically downloaded zip update. There is not much more to do then this because twrp will do the remaining work and check CRC before starting extraction.
Click to expand...
Click to collapse
Hmm, did you disable secure mode?
That should NOT have happened in secure mode because ZIP signature verification would have failed.
Entropy512 said:
Hmm, did you disable secure mode?
That should NOT have happened in secure mode because ZIP signature verification would have failed.
Click to expand...
Click to collapse
Nope no playing with the secure mode here. TWRP 2.6.3.0
Afe redownloading it and rebooting the recovery it was installed fine.
Hi Guys
I already unlock my fone, but at firt time that I try to install a new room a error messagem shows like this:
Installing '/sdcar1/'......
checking for MD5 file.....
Skipping MD5 check: no MD5 file not found
Error flashing zip ''/sdcard1/'.....
updating partitions detais.....
E: unable to stat '/data/system/recent_tasks/16_task.xml
done.....
Failed!
BinhoDigital said:
Hi Guys
I already unlock my fone, but at firt time that I try to install a new room a error messagem shows like this:
Installing '/sdcar1/'......
checking for MD5 file.....
Skipping MD5 check: no MD5 file not found
Error flashing zip ''/sdcard1/'.....
updating partitions detais.....
E: unable to stat '/data/system/recent_tasks/16_task.xml
done.....
Failed!
Click to expand...
Click to collapse
What rom are u trying to flash?
Plz provide a link
Moto G User said:
What rom are u trying to flash?
Plz provide a link
Click to expand...
Click to collapse
I allready try with stock, cm12, paranoid android and pac man roms...
Im using TWRP 2.8.6.0, in other operations like Wipe data, cache and dalvik give the same message in red:
updating partitions detais.....
E: unable to stat '/data/system/recent_tasks/16_task.xml
done.....
I try to wipe all units, copy the rooms from sdcard again and the message error continue
Solved
Hello friends!!!
The newest version of TWRP ( 2.8.7.0 ) solve my problem!
TKS!
Hi everyone.
I need some help!
Some years ago I rooted my Kindle Fire HD 7" (2nd gen) and installed CM. Recently I was trying to update my CM and did something wrong (can't remember what).
Now y have my Kindle Fire getting into TWRP instead of booting, and can't install anything. I've tryed downloading and installinf diffrent ROMS, but y always get the same message "FAILED"
in the log i can read this:
E:Unknown File System: 'datamedia´
Updating partition details...
Running boot script...
Finished running boot script.
Installing ´/sdcard/cm-12.1-20160606-NIGHTLY-tat.zip´...
Checking for MD5 file...
Skipping MD5 check.: no MD5 file found.
Warning: No file_contexts
detected filesystem ext4 for /dev/block/platform/omap/...
detected filesystem ext4 for /dev/block/platform/omap...
ApplyParsedPerms: lsetfilecon of /system/etc/ppp/...
ApplyParsedPerms: removexattr of /system/etc/ppp/...
set_metadata_recursive: some changes failed
E:Error in /sdcard/cm-12.1-20160606-NIGHTLY-tate.zip
(Status 7)
Error Flashing zip ´/sdcard/cm-12.1-20160606-NIGHLTY-tate.zip´
Updating partition details ...
Failed
Does anybody knows what I'm doing wrong and how i can fix this?
Please!!! Help me!!!
THANK YOU!!!!
negrooblackk said:
Hi everyone.
I need some help!
Some years ago I rooted my Kindle Fire HD 7" (2nd gen) and installed CM. Recently I was trying to update my CM and did something wrong (can't remember what).
Now y have my Kindle Fire getting into TWRP instead of booting, and can't install anything. I've tryed downloading and installinf diffrent ROMS, but y always get the same message "FAILED"
in the log i can read this:
E:Unknown File System: 'datamedia´
Updating partition details...
Running boot script...
Finished running boot script.
Installing ´/sdcard/cm-12.1-20160606-NIGHTLY-tat.zip´...
Checking for MD5 file...
Skipping MD5 check.: no MD5 file found.
Warning: No file_contexts
detected filesystem ext4 for /dev/block/platform/omap/...
detected filesystem ext4 for /dev/block/platform/omap...
ApplyParsedPerms: lsetfilecon of /system/etc/ppp/...
ApplyParsedPerms: removexattr of /system/etc/ppp/...
set_metadata_recursive: some changes failed
E:Error in /sdcard/cm-12.1-20160606-NIGHTLY-tate.zip
(Status 7)
Error Flashing zip ´/sdcard/cm-12.1-20160606-NIGHLTY-tate.zip´
Updating partition details ...
Failed
Does anybody knows what I'm doing wrong and how i can fix this?
Please!!! Help me!!!
THANK YOU!!!!
Click to expand...
Click to collapse
Do you have the latest version of twrp installed? I see you're flashing cm12, what version were you coming from?
squ89r97 said:
Do you have the latest version of twrp installed? I see you're flashing cm12, what version were you coming from?
Click to expand...
Click to collapse
thanks for answering!
i´m flashing CM12 right now, buy already tried with other ROMS having the same problem. I really don´t care that much on what ROM to install, I just want my Kindle to come back to life again
regardin TWRP, I cant remember what version I´m using, but i don´t think its the latest one. Do you recommend me to try this? I´ll check and let you know.
any other suggestions?
thanks!!
negrooblackk said:
thanks for answering!
i´m flashing CM12 right now, buy already tried with other ROMS having the same problem. I really don´t care that much on what ROM to install, I just want my Kindle to come back to life again
regardin TWRP, I cant remember what version I´m using, but i don´t think its the latest one. Do you recommend me to try this? I´ll check and let you know.
any other suggestions?
thanks!!
Click to expand...
Click to collapse
Well, twrp tells you what version it is when it starts up, so that should be easy to report. And I know you're flashing cm12, I asked what you were running before that. It's possible that you need to update twrp in order to flash newer base versions of Roms. Especially after you say it was a few years ago when you rooted it.