TWRP and MD5 Checking during flashing - Samsung Galaxy Nexus

Anyone familiar with how TWRP goes about checking for MD5SUM matching on a file that is being flashed?
Like, do you need to have a .md5 with the same name as the .zip you're flashing? or what is the structure required?
I've tried googling this, but i haven't gotten anywhere, mainly just stuff about md5 and nandroids.

Not sure about your question but the Md5 can be checked with root explorer -long press package of choose-tap properties

After a little research and testing, this is what worked for me.
If all you have is the MD5 hash, then put it in a text file in the same directory as the zip you want to flash. The format should look like this:
Code:
1234567890abcdef1234567890 *app-20120905-final.zip
If the zip is named, for example:
app-20120905-final.zip
Click to expand...
Click to collapse
then that is what goes in the file after the asterisk ( * ).
Also, in this case, the text file you create should be named:
app-20120905-final.zip.md5
Click to expand...
Click to collapse
Hope this helps.
Edit: I just realized how old this thread was. However, I did not find any answers to this question when searching, so hopefully this is still of use to someone.

Thanks for the reply.
I ended up a few weeks ago going to #twrp or #openrecovery (can't remember which) and asked them, and was pointed to a guide:
md5sum some_file.zip > some_file.zip.md5
Sent from my Galaxy Nexus using Tapatalk 2

Yeah. My method was for those not comfortable at terminal, let alone in Linux at all. Glad you got it figured out
Sent from my LTEvo using XDA Premium.

THANKS FOR THIS!!!
i can finally make use of TWRP's MD5 check!

bilbo524 said:
After a little research and testing, this is what worked for me.
If all you have is the MD5 hash, then put it in a text file in the same directory as the zip you want to flash. The format should look like this:
Code:
1234567890abcdef1234567890 *app-20120905-final.zip
If the zip is named, for example:
then that is what goes in the file after the asterisk ( * ).
Also, in this case, the text file you create should be named:
Hope this helps.
Edit: I just realized how old this thread was. However, I did not find any answers to this question when searching, so hopefully this is still of use to someone.
Click to expand...
Click to collapse
Thanks for this, helped me a lot making sure my file was correct and not responsible for the bootloop!

Also, the MD5 hash must be lowercase.

Is the asterix * compulsory?
Otherwise I have a simple one-liner using the Microsoft File Checksum Verifier tool to generate the same file that md5sum does.
Code:
fciv [file] | more +3 > [file].md5
Or in a quick 5-minute batch file I threw together (which allowed me to process the asterix in it):
Code:
@echo off
for %%f in (*.zip) do (
echo Processing [%%~nf.zip] ...
fciv "%%~nf.zip" | more +3 > %%~nf.zip.md5
set LINEONE=1
for /f "tokens=1" %%A in (%%~nf.zip.md5) do (
if %LINEONE% EQU 1 (
echo md5: %%A
echo | set /p mdfive=%%A *%%~nf.zip > %%~nf.zip.md5
) else (
set /a LINEONE = %LINEONE% + 1
)
)
)
echo Done.
pause

Whosat said:
Is the asterix * compulsory?
Click to expand...
Click to collapse
The asterisk indicates the file to be checked is a binary file (as opposed to a text file).
From `man md5sum`:
The sums are computed as described in RFC 1321. When checking, the
input should be a former output of this program. The default mode is
to print a line with checksum, a character indicating input mode ('*'
for binary, space for text), and name for each FILE.
Click to expand...
Click to collapse

Related

[REF] How to restore original product code!

Hi,
So i coulden't wait and had to try out JPC firmware. Personally i didn't like it at all, so i went back to JM7. 1 thing i did not like is my product code changed from XEN to KOR.
And here is how to fix that easly:
I tested this on 2.1 cause i was on JM7 when i found this out, but this works with JPC/JPH also.
this fix is for those who do not have (correct) .bak files in the /efs/ directory!
- First make sure you are ROOT and install a Terminal Emulator (can be found in the market)
- Now open the Terminal, enter ''su'' to gain root access
- Enter: cp /efs/nv_data.bin /sdcard/
- Connect you're SGS to the usb and download ''nv_data.bin'' to your computer
- Open ''nv_data.bin'' with notepad or wordpad and search for ''KOR'' change this to the product code matching your country (red marked text should be changed). Im dutch, so mine is XEN. The line looks like this:
Code:
ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿMP 0.800 ÿ[COLOR="Red"]KOR[/COLOR] GT-I9000HKD[COLOR="Red"]KOR[/COLOR]
- Now simply save your changes.
- Connect your SGS with usb, upload ''nv_data.bin'' to internal sdcard.
- Disconnect USB !
- Open Terminal Emulator and enter ''su''
- Now enter: cp /sdcard/nv_data.bin /efs/nv_data.bin
Also enter: rm -rf /efs/nv_data.bin.md5
- Close terminal, Reboot Phone. And Voila!!! Product Code restored!!
**IF YOUR SIMCARD DOESN'T WORK AFTER THIS, EXECUTE THE FOLLOWING**
- adb shell
- su
- busybox chown 1001:1001 /efs/nv_data.bin
- reboot
You can also do this from the Terminal Emulator if you don't have ADB on your PC! Like this:
-su
-chown 1001:1001 /efs/nv_data.bin
-reboot
I hope it's easy to follow my steps, it works guaranteed.
UPDATE - 13/09
Some people say you don't have to create a new md5, just remove the old one on the phone. kaffre and i tested this, the phone recreates the md5 file for you. So i've updated the steps in my tutorial, to make it even more easy!
UPDATE - 15/09
Simcard fix added. Thanks to tokinux
I`d suggest using a hex editor instead of any wordpad/notepad editor ...
Methyldioxide said:
Hi,
So i coulden't wait and had to try out JPC firmware. Personally i didn't like it at all, so i went back to JM7. 1 thing i did not like is my product code changed from XEN to KOR.
So f*ck that and here is how to fix that easly:
I tested this on 2.1 cause i was on JM7 when i found this out, but im 99% sure this works with JPC also.
- First make sure you are ROOT and install a Terminal Emulator (can be found in the market)
- Now open the Terminal, enter ''su'' to gain root access
- Enter: cp /efs/nv_data.bin /sdcard/
- Connect you're SGS to the usb and download ''nv_data.bin'' to your computer
- Open ''nv_data.bin'' with notepad or wordpad and search for ''KOR'' change this to the product code matching your country. Im dutch, so mine is XEN. The line looks like this:
Code:
ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿMP 0.800 ÿKOR GT-I9000HKDKOR
- Now simply save your changes.
- Download a md5 creator tool, i use MD5SUMMER
- Create a MD5 file using ''nv_data.bin" and save this as ''nv_data.bin.md5''
- Open ''nv_data.bin.md5'' with notepad and delete all the lines beside the line wich is similar to this one: 4ba37998243f14158884c5f464933398 (ofcourse your line of numbers is different ! ) Save the md5 file.
- Now your md5 file should be exactly 32bytes (this is the same size of the md5 file used by samsung, so please follow this step carefully)
- Connect your SGS with usb, upload ''nv_data.bin.md5'' and ''nv_data.bin'' to internal sdcard.
- Disconnect USB !
- Open Terminal Emulator and enter ''su''
- Now enter: cp /sdcard/nv_data.bin.md5 /efs/nv_data.bin.md5
cp /sdcard/nv_data.bin /efs/nv_data.bin
- Close terminal, Reboot Phone. And Voila!!! Product Code restored!!
I hope it's easy to follow my steps, it works guaranteed.
Click to expand...
Click to collapse
editing those files is there a risk of changing the IMEI in 004999010640000 ??
i think something similar happened to me and now i'm with XXXXXXX as product code and that fake IMEI.......
Narcissus85 said:
editing those files is there a risk of changing the IMEI in 004999010640000 ??
i think something similar happened to me and now i'm with XXXXXXX as product code and that fake IMEI.......
Click to expand...
Click to collapse
My imei did never change, also not after product code restore
For me it seems to be easier to do it with the *#272*hhmm#* solution.
Read about this here: http://forum.xda-developers.com/showthread.php?t=779580
Its doing also a hardreset.. so backup you data!
In case you dont want a hard-reset, this manual solution is much better! So Thx, Methyldioxide for your work and sharing with us!
Donald Nice said:
For me it seems to be easier to do it with the *#272*hhmm#* solution.
Read about this here: http://forum.xda-developers.com/showthread.php?t=779580
Its doing also a hardreset.. so backup you data!
In case you dont want a hard-reset, this manual solution is much better! So Thx, Methyldioxide for your work and sharing with us!
Click to expand...
Click to collapse
but his doesnt change the product code! i did it and still is KOR.
what is true is that putting the right csc is making my phone act like a normal one so at the end having a KOR phone gives me no problems at the moment...
Donald Nice said:
For me it seems to be easier to do it with the *#272*hhmm#* solution.
Read about this here: http://forum.xda-developers.com/showthread.php?t=779580
Its doing also a hardreset.. so backup you data!
In case you dont want a hard-reset, this manual solution is much better! So Thx, Methyldioxide for your work and sharing with us!
Click to expand...
Click to collapse
*#272*hhmm#* only changes the CSC settings indeed, not the actual product code. With warrenty this can be an issue. So i preffer my original product code
Did this actually change the product code or did your Galaxy S replace the changed nv_data.bin file from the backup .nv_data.bak file?
The default action is to use the bak file to write a new nv_data.bin if the original is missing or corrupt. If your original .nv_data.bak still had the original code in it this could be what happened.
I´ve copied my original nv_data.bin and nv_data.bin.md5 to my pc und used md5summer to check if the md5 hash stored in nv_data.bin.md5 is a normal md5 hash of the filesize.
The Hash generated with md5summer didn´t match!!!
Seems to be not an normal md5 hash of the filesize. There must be more.
If i do steps from OP the product code of my phone changes to XXXXXXXX.
Have used an Hex Editor and md5summer. Also tried WinMD5, same ****.
Aery said:
I´ve copied my original nv_data.bin and nv_data.bin.md5 to my pc und used md5summer to check if the md5 hash stored in nv_data.bin.md5 is a normal md5 hash of the filesize.
The Hash generated with md5summer didn´t match!!!
Seems to be not an normal md5 hash of the filesize. There must be more.
If i do steps from OP the product code of my phone changes to XXXXXXXX.
Have used an Hex Editor and md5summer. Also tried WinMD5, same ****.
Click to expand...
Click to collapse
You dont read proper, plz read the steps carefully and you will create the correct md5 hash. I think your problem is that you did not open nv_data.bin.md5 after you generated it and deleted all lines beside the HASH line. This all is stated clearly in my steps, and you shouldent have any issue.
EDIT: The nv_data.bin.md5 you generated should be exactly 32bytes! else you did not follow my steps properly
ghostgull said:
Did this actually change the product code or did your Galaxy S replace the changed nv_data.bin file from the backup .nv_data.bak file?
The default action is to use the bak file to write a new nv_data.bin if the original is missing or corrupt. If your original .nv_data.bak still had the original code in it this could be what happened.
Click to expand...
Click to collapse
Nope, i wish it was that easy for me This works only if you backup up your rom with Clockworks for example.
Methyldioxide said:
You dont read proper, plz read the steps carefully and you will create the correct md5 hash. I think your problem is that you did not open nv_data.bin.md5 after you generated it and deleted all lines beside the HASH line. This all is stated clearly in my steps, and you shouldent have any issue.
EDIT: The nv_data.bin.md5 you generated should be exactly 32bytes! else you did not follow my steps properly
Click to expand...
Click to collapse
I´ve much knowledge about computers, linux (running a lenny root server) and so on. I´m not stupid. ;-)
In nv_data.bin.md5 there is only the hash code and its 32 bytes.
Will try hashing the file under ubuntu or debian and report back. Maybe windows is doing **** here.
This is very crazy.
My original files:
nv_data.bin -> DBT
hash in nv_data.bin.md5 -> 3012f56623f1a296c1ecd33ee8f0819b
Hash of nv_data.bin (windows, md5summer) -> 1e44ea7702c0e6b603c01ef0bf5508b0
Hash of nv_data.bin (ubuntu, md5sum) -> 1e44ea7702c0e6b603c01ef0bf5508b0
With my original Files Product Code of Phone is DBT.
If i use the md5 Hash generated by md5summer, put it in nv_data.bin.md5 Phone says XXXXXXXX.
Pretty strange.
Aery said:
This is very crazy.
My original files:
nv_data.bin -> DBT
hash in nv_data.bin.md5 -> 3012f56623f1a296c1ecd33ee8f0819b
Hash of nv_data.bin (windows, md5summer) -> 1e44ea7702c0e6b603c01ef0bf5508b0
Hash of nv_data.bin (ubuntu, md5sum) -> 1e44ea7702c0e6b603c01ef0bf5508b0
With my original Files Product Code of Phone is DBT.
If i use the md5 Hash generated by md5summer, put it in nv_data.bin.md5 Phone says XXXXXXXX.
Pretty strange.
Click to expand...
Click to collapse
I've been looking to correctly generate the .md5 file as well. As you can see Samsung uses more than just the file contents for generating the MD5 hash. An interesting thing is that when the phone recreates the nv_data.bin file based on the .nv_data.bak file it also regenerated the md5 file. The hash in this file was different from the one in the backup (original and backup were exactly the same nv_data with the same product code). So I suspect at least the timestamp of the file is also taken into account. I already tried diffenent scenario's but did not manage to generate a correct hash yet.
Aery said:
This is very crazy.
My original files:
nv_data.bin -> DBT
hash in nv_data.bin.md5 -> 3012f56623f1a296c1ecd33ee8f0819b
Hash of nv_data.bin (windows, md5summer) -> 1e44ea7702c0e6b603c01ef0bf5508b0
Hash of nv_data.bin (ubuntu, md5sum) -> 1e44ea7702c0e6b603c01ef0bf5508b0
With my original Files Product Code of Phone is DBT.
If i use the md5 Hash generated by md5summer, put it in nv_data.bin.md5 Phone says XXXXXXXX.
Pretty strange.
Click to expand...
Click to collapse
i was talking about this in my post....check ur imei too...
THANKS
Using the steps in 1st post, I could change my Product code from KOR to INU after updating to JPC thro kies.
Thanks.
Its not working. cant generate a correct md5 file.
Is the Imei stored in the nv_data.bin too????
Imei is not on that file, but /efs/imei/bt.txt if i recall that correctly.
And my fix does work great, if you cannot create a correct md5 then it's prolly cause you do it wrong. I bet if you send me your modified file and i make the md5 for you it will work.
Sent from my GT-I9000 using XDA App
At that location there's the bluetooth mac aaddress.
I think your product code reverted to the original because you damaged your nv_data.bin and nv_data.bin.md5 files and the phone recreated them from the backup.
If you don't have backups don't try this.
Sent from my GT-I9000 using XDA App
Methyldioxide said:
Hi,
So i coulden't wait and had to try out JPC firmware. Personally i didn't like it at all, so i went back to JM7. 1 thing i did not like is my product code changed from XEN to KOR.
And here is how to fix that easly:
I tested this on 2.1 cause i was on JM7 when i found this out, but im 99% sure this works with JPC also.
- First make sure you are ROOT and install a Terminal Emulator (can be found in the market)
- Now open the Terminal, enter ''su'' to gain root access
- Enter: cp /efs/nv_data.bin /sdcard/
- Connect you're SGS to the usb and download ''nv_data.bin'' to your computer
- Open ''nv_data.bin'' with notepad or wordpad and search for ''KOR'' change this to the product code matching your country. Im dutch, so mine is XEN. The line looks like this:
Code:
ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿMP 0.800 ÿKOR GT-I9000HKDKOR
- Now simply save your changes.
- Download a md5 creator tool, i use MD5SUMMER
- Create a MD5 file using ''nv_data.bin" and save this as ''nv_data.bin.md5''
- Open ''nv_data.bin.md5'' with notepad and delete all the lines beside the line wich is similar to this one: 4ba37998243f14158884c5f464933398 (ofcourse your line of numbers is different ! ) Save the md5 file.
- Now your md5 file should be exactly 32bytes (this is the same size of the md5 file used by samsung, so please follow this step carefully)
- Connect your SGS with usb, upload ''nv_data.bin.md5'' and ''nv_data.bin'' to internal sdcard.
- Disconnect USB !
- Open Terminal Emulator and enter ''su''
- Now enter: cp /sdcard/nv_data.bin.md5 /efs/nv_data.bin.md5
cp /sdcard/nv_data.bin /efs/nv_data.bin
- Close terminal, Reboot Phone. And Voila!!! Product Code restored!!
I hope it's easy to follow my steps, it works guaranteed.
Click to expand...
Click to collapse
I did it!!!!
but, if I can , there's a small error,you 've to correct the red line ''nv_data.bin.md5'' in "nv_data.md5" .... this worked for me....
very helpfull guide, greetings mate

[GUIDE] How to check md5sums on files

This information may be old news for experienced users but those new to android may find it useful.
When downloading a new ROM that you would like to flash, it is always possible for corruption to occur. Either in the download itself or in storing it to the SD card. In order to address this issue, most ROMs put out by developers also include an MD5SUM for that ROM. This MD5SUM is used to verify that all of the bits in the file came across right.
Below are instructions on how to verify if the file that you have on your SD card on the phone is not corrupted.. These instructions assume that the file is located at the root of the SD card (as would be needed for flashing ROMs but not necessarily for Recovery Images).
All lines will automatically start with the $ symbol, you need not type this in. Every line ends by pressing the enter key, do not include the quotation marks. The command to show a directory is ls (lower case L and lower case S). this is done in the example to make sure that you use the correct file name when calling the md5sum command.
Open Terminal Emulator
Type "cd /sdcard" and press Enter
Type "ls" or "ls *.zip" to only show zip files and press Enter
This will provide a list of files at the root of the sd card.
Type "md5sum <filename>" substituting the name of the file listed in the ls command for <filename>.
An MD5SUM value will be calculated and displayed. Verify this value against what is published by the developer. If it is correct, go ahead and flash, if not try redownloading the file and repeat. If you continue to get a different MD5SUM value, try downloading it from a different (perhaps mirrored) site
In my example below, I combined the ls command to show only zip files (so that you can see it all on one screen)
http://twitpic.com/39cc3y
Alternatively, you can call the md5sum command with the *.zip or *.img argument and get an md5sum for all files of those types.
For additional information on md5sums, check out this link http://forum.xda-developers.com/showthread.php?t=706705
awesome!
Thank you for helping new people like me who are just entering the Android game.
Sent from my HTC Glacier using XDA App
check md5 file on pc
download a program called teradata
can be found here:
http://www.codesector.com/teracopy.php
install program
open md5 file
ta-da, this will tell you if the files are ok or not
QMAN101 said:
This information may be old news for experienced users but those new to android may find it useful.
When downloading a new ROM that you would like to flash, it is always possible for corruption to occur. Either in the download itself or in storing it to the SD card. In order to address this issue, most ROMs put out by developers also include an MD5SUM for that ROM. This MD5SUM is used to verify that all of the bits in the file came across right.
Below are instructions on how to verify if the file that you have on your SD card on the phone is not corrupted.. These instructions assume that the file is located at the root of the SD card (as would be needed for flashing ROMs but not necessarily for Recovery Images).
All lines will automatically start with the $ symbol, you need not type this in. Every line ends by pressing the enter key, do not include the quotation marks. The command to show a directory is ls (lower case L and lower case S). this is done in the example to make sure that you use the correct file name when calling the md5sum command.
Open Terminal Emulator
Type "cd /sdcard" and press Enter
Type "ls" or "ls *.zip" to only show zip files and press Enter
This will provide a list of files at the root of the sd card.
Type "md5sum <filename>" substituting the name of the file listed in the ls command for <filename>.
An MD5SUM value will be calculated and displayed. Verify this value against what is published by the developer. If it is correct, go ahead and flash, if not try redownloading the file and repeat. If you continue to get a different MD5SUM value, try downloading it from a different (perhaps mirrored) site
In my example below, I combined the ls command to show only zip files (so that you can see it all on one screen)
http://twitpic.com/39cc3y
Alternatively, you can call the md5sum command with the *.zip or *.img argument and get an md5sum for all files of those types.
For additional information on md5sums, check out this link http://forum.xda-developers.com/showthread.php?t=706705
Click to expand...
Click to collapse
Wow, thank you for that! I've been wondering wtf an md5sum is. Now I know.
missing info
Thanks for posting this information - very well written and appears to leave no steps out.
One thing I have to say about a lot of the instructions that are posted about modding - they leave out important step(s) that would be needed to complete the process. Usually it's something that's easily overlooked; what the screen should look like after completing a step, prior to starting the next step. One example, that messed me up (in the past), is partitioning: many instructions gave examples on partitioning, but don't say how to configure the partition (primary, extended, etc)... I had to figure out why my android G1 wasn't working exactly as advertised, because the instructions I found were incomplete.
I think that's why video instructions are awesome - although through bad editing they can suck too.
It's hard work writing instructions, and I thank the people who do, but please write down everything.
This post is just a tangent brought on by reading the original, very well written post.
How did I miss your great post!!! Nice little write up for me checking files on the go.
-John
And for the mac users out there you simply need to open a terminal and type:
md5 <filename>
Or you can get afv (android file verifyer) from the market and just click on the file to generate the md5. Easier if you do it all the time
ahh thanks for spilling the beans
i keep getting "error checking md5sums" when restoring a nandroid back up
I think my SD card is buggered. Its nearly 18 months old and a hell of a lot of transfers on and off it. Maybe time to replace.
i use mand5 and it has an option to google search that checksum. Makes it convenient when devs post the checksum in the OP of their thread because then the search will find it and i can clearly see it's right, 4ext recovery also calculates md5s as well
Another excellent program for verifying checksums on Windows based PCs is Hashcheck. After installation, you'll find a new tab in the properties window of any file which will generate many different types of checksums and contains a box you can type or paste an existing checksum such as one posted with the download. It integrates cleanly with most versions of Windows. You can even use it to create a .md5 checksum file that can be opened to verify the file at any time. This is one of the first applications I install on a clean Windows installation.
And whoever suggested teracopy, it seems to run quite buggy on certain PC setups with mid-transfer freezes and such even on.a fresh Windows installation. SuperCopier is another alternative free file copy/transfer application that I've never seen fail on any of the systems I've used and which has quite similar.functionality to teracopy. Granted, I've only tried a limited number of PCs, but that number continues to grow as I'm basically the technical go-to guy in my family and neighborhood due to my background as a current software programming major.
Sent from my HTC Glacier using Tapatalk
Sorry, double post. My fat fingers hit quote instead of modify.
Sent from my HTC Glacier using Tapatalk
Hash Droid
The app called Hash Droid works perfect for me.
If I helped please press thanks.

[REF][GUIDE]CWM md5 mismatch problem solved

So, many of you probably faced the issue, when you tried to restore your CWM backup, that the recovery says MD5 mistmach, and will do nothing. The problem is now solved, and was solved, so I'm not the one, who made thing possible, I'm just porting this to the V.
So, the problem (in my iterations at least) are based on the /cache/ cannot be mounted error, which is common in the V. For why is that, I simply don't have a clue, but it is present. Because of this, the backup won't be full, and thus, the md5 image won't be made for the recovery, so cannot be recovered as is.
But happily you can make an md5 image from the backup yourself, and thus recover your backup.
WARNING!​
I'm no dev, just someone, that knows linux.
If you follow this path, you do it on your own. I'm not responsible for bricked devices, lost data or whatsoever, including the future the past and the present.​
Click to expand...
Click to collapse
There are three ways for you, to make an md5 sum of the img files, the good and the bad one and also the quoted one:
One (the good)
For this, you will need adb, root, and a working android. Yo don't have it? Here you go.
Go to the directory, were you have adb (or have extracted adb.exe, suggested c:\htc\), then plug in your phone (just for charge, no data connection), open terminal (syntax: cmd) then type in:
adb shell
this will get you to the phone's terminal
if you have # at the end of the line, you are good to go, if not, then type su
The syntaxes needed:
cd /sdcard/clockworkmod/backup/{recovery_timestamped_directory} <- this is from your backup, so you need to fill in appropirate data
md5sum *img > nandroid.md5
Click to expand...
Click to collapse
This will make an md5 image with the name that cwm acknowledges.
Two (the bad one)
So, you'we fired your ROM, cannot even boot, but cwm comes in. Than this is for you. There are programs (e.g. total commander) which can make md5 images. So if you have your backup folder, just go into it (sd card reader is preferred). You will see something like this in it:
.android_secure.vfat.tar
boot.img
data.ext4.tar
{nandroid.md5}
recovery.img
system.ext4.tar
Click to expand...
Click to collapse
sidenote:
If you have the nandroid.md5 and you cannot recover, don't try to recover from it!!!
The image itself is corrup, you have no luck, try RUU. (you can recover if you delete the md5 and create a new, but it is not really recommended)
1.
So, there are 2 .img files, highlight them in totalcommander. go to file->create checksum files
2.
tick in md5, then ok
3.
No, you're not done
open the md5 file in text editor, and remove the * 's from before the file names.
4.
Rename the file to nandroid.md5
5.
Now you're done, go to cwm, then recover.
Three (the quoted one)
Also on the 2nd page you will find an alternative solution for the problem which can help you if you have got busybox installed on your device.
The solution resembles the One type of fix, so with quotes here's the one (thanx for Meeshka for it).
Meeshka said:
For those who keep getting "md5sum not found" both in adb and in android terminql on device:
try instead
# busybox md5sum *img > nandroid.md5
worked for me
Click to expand...
Click to collapse
If I helped, don't hesitate to push the Thanks button.
Thanks... a very useful guide. Bookmarked
WORKED!!! Tho I'm from a different device the first (adb) method saved my AOKP backup!!! Daysaver I'd say!!
I keep getting "md5sum: not found"
Put this in the general android section as it works across most devices. ..
Sent from my One V
Nevell said:
I keep getting "md5sum: not found"
Click to expand...
Click to collapse
if you send me the 2 img files i can create an appropirate md5 image of them, but send the one you did, so I can guess what the problem is.
send them to the email of my usr here, or in pm. and mainly, the md5 image has the name "nandroid.md5" like small caption all the way, even the md5? If it is there where it must, it must work, ad absurd it will be "wrong checksum error", but that is another version.
General android section has this, I have learned this from there, but it had only 1st option, and was "discovered" when cwm had generated wrong md5s, the V, in the V the problem is a tad bit different, but the solution is the same.
I fixed it in adb
Sent from my SPH-L710 using xda premium
Nevell said:
I fixed it in adb
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Can you explain what did you do to fix md5sum: not found error??
please i need it!
thatsgamer said:
Can you explain what did you do to fix md5sum: not found error??
please i need it!
Click to expand...
Click to collapse
Just created an md5sum manualy from the img files with the name of nandroid.md5, because on the V the recovery doesn't creates them because of cache mount problem.
The recovery process will end in an error message, because cache cannot be recovered, but the main thing will be recovered this way.
i have one x and i can't put sdcard in to card reader because one x dose not have sd card... and i cant fix it whit first solution because i cant acces my phone
haky1988 said:
i have one x and i can't put sdcard in to card reader because one x dose not have sd card... and i cant fix it whit first solution because i cant acces my phone
Click to expand...
Click to collapse
See : http://forum.xda-developers.com/showpost.php?p=32248108&postcount=7
unfortunately none of the methods described in the first post have worked for me, at the first one i got an "unable to write, source is read-only" error, and the second one failed from the first try
after almost giving up and beginning to deal with the idea of loosing my backups, i found this topic and in 10 secs it got the job done, now i'm back on my latest cwm backup
CWM showing different versions
-Delete-
maranello69 said:
unfortunately none of the methods described in the first post have worked for me, at the first one i got an "unable to write, source is read-only" error, and the second one failed from the first try
after almost giving up and beginning to deal with the idea of loosing my backups, i found this topic and in 10 secs it got the job done, now i'm back on my latest cwm backup
Click to expand...
Click to collapse
You do know that the first method is exactly like the one you linked right?
Aside that, I'm happy that the community could help you out
Loir can u help me. I can't locate the boot.img inside the downloads for cyanogen mod u provided. Forgive me but can you post a directory to this kernel file? Tks
Sent from my HTC Desire X using xda app-developers app
Thank you so much. You saved my phone.
For those who keep getting "md5sum not found" both in adb and in android terminql on device:
try instead
# busybox md5sum *img > nandroid.md5
worked for me
no * 's
Ken-Shi_Kun said:
So, many of you probably faced the issue, when you tried to restore your CWM backup, that the recovery says MD5 mistmach, and will do nothing. The problem is now solved, and was solved, so I'm not the one, who made thing possible, I'm just porting this to the V.
So, the problem (in my iterations at least) are based on the /cache/ cannot be mounted error, which is common in the V. For why is that, I simply don't have a clue, but it is present. Because of this, the backup won't be full, and thus, the md5 image won't be made for the recovery, so cannot be recovered as is.
But happily you can make an md5 image from the backup yourself, and thus recover your backup.
​
There are two ways for you, to make an md5 sum of the img files, the good and the bad one:
One (the good)
For this, you will need adb, root, and a working android. Yo don't have it? Here you go.
Go to the directory, were you have adb (or have extracted adb.exe, suggested c:\htc\), then plug in your phone (just for charge, no data connection), open terminal (syntax: cmd) then type in:
adb shell
this will get you to the phone's terminal
if you have # at the end of the line, you are good to go, if not, then type su
The syntaxes needed:
This will make an md5 image with the name that cwm acknowledges.
Two (the bad one)
So, you'we fired your ROM, cannot even boot, but cwm comes in. Than this is for you. There are programs (e.g. total commander) which can make md5 images. So if you have your backup folder, just go into it (sd card reader is preferred). You will see something like this in it:
sidenote:
If you have the nandroid.md5 and you cannot recover, don't try to recover from it!!!
The image itself is corrup, you have no luck, try RUU. (you can recover if you delete the md5 and create a new, but it is not really recommended)
1.
So, there are 2 .img files, highlight them in totalcommander. go to file->create checksum files
2.
tick in md5, then ok
3.
No, you're not done
open the md5 file in text editor, and remove the * 's from before the file names.
4.
Rename the file to nandroid.md5
5.
Now you're done, go to cwm, then recover.
If I helped, don't hesitate to push the Thanks button.
Click to expand...
Click to collapse
in 3. it says to remove the * *'s, but i don't see any, so i was wondering should i leave that be or if im doing something wrong.
Beastben13 said:
in 3. it says to remove the * *'s, but i don't see any, so i was wondering should i leave that be or if im doing something wrong.
Click to expand...
Click to collapse
I have done the thing with a legacy tcmd, so there is a probability, that they have modified the md5sum algorithm, so if you don't se the stars don't panic. (also it should do the trick even with stars in the file, but wanted to be sure at the time I wrote the post)
plz provide touch recovery for karbon a9+ plz and ther is bugs in cwm recovery 5.0.2.8 plz

How to make a .tar into a .tar.md5 in Windows?

I am trying to make my own .tar that I can use in Odin. I have the gsm Galaxy Nexus. I already have 4.1.2 and installed it via fastboot from https://developers.google.com/android/nexus/images#takjujzo54k. But just in case I would love to have a .tar to flash with Odin just in case. I downloaded the Takju and extracted all the .img and made a .tar with 7-zip and when I try and flash it through Odin it hangs at nand write start.
So I looked around and found a pre made .tar Yakju here http://forum.xda-developers.com/showthread.php?t=1827685. Since this was for Maguro phones I flashed it through odin with no problems at all.
That Yakju .tar is actually a .tar.md5, so is this the problem with my tar that I made? I've been reading up on md5 and what it actually is but can't find a way to add it to my file name. If someone can point me in the right direction I would really appreciate it. I would like to be able to do this on my Windows 7 rig if possible. Thanks!!
Md5 is just a hash check on the file to make sure it is downloaded correctly. You compare the md5 with the same code that is posted on the download site/location. If it match your download is 100% correct.
Swype'ed on my CM10 Galaxy Nexus
Herman76 said:
Md5 is just a hash check on the file to make sure it is downloaded correctly. You compare the md5 with the same code that is posted on the download site/location. If it match your download is 100% correct.
Swype'ed on my CM10 Galaxy Nexus
Click to expand...
Click to collapse
just install cygwin
Code:
md5sum filename.fileextension > filename.fileextension.md5
to check
Code:
md5sum -c filename.fileextension.md5
example:
valhalla% md5sum -c full_maguro-user-15102012v2-JZO54K-bk201.zip.md5
full_maguro-user-15102012v2-JZO54K-bk201.zip: OK
Click to expand...
Click to collapse
bk201doesntexist said:
just install cygwin
Code:
md5sum filename.fileextension > filename.fileextension.md5
to check
Code:
md5sum -c filename.fileextension.md5
example:
Click to expand...
Click to collapse
can someone make this a bit more noob friendly?
Installed Cygwin..do I need any packages to install?
Where do I put my .tar file
Why when I press Enter at the end of a command in the terminal nothing happens, the cursor just goes to the next line...
for just adding the md5 there is no easier way? something with GUI? maybe something on the android device even...
dataman said:
can someone make this a bit more noob friendly?
Installed Cygwin..do I need any packages to install?
Where do I put my .tar file
Why when I press Enter at the end of a command in the terminal nothing happens, the cursor just goes to the next line...
for just adding the md5 there is no easier way? something with GUI? maybe something on the android device even...
Click to expand...
Click to collapse
install cygwin (install only zip files, no need to install all files)
open cygwin ------>Home------->(user name) and create a folder named "work".
put all images files of stock firmware of your gnex downloaded from google site (radio, bootloader, boot, recovery, system, userdata) in "work" folder.
open cmd by clicking on cygwin .bat file and enter the following commands:
Code:
cd ./work
tar -H ustar -c boot.img bootloader.img radio.img recovery.img system.img userdata.img > name-of-odin-flashable.tar
md5sum -t name-of-odin-flashable.tar >> name-of-odin-flashable.tar
mv name-of-odin-flashable.tar name-of-odin-flashable.tar.md5
(images must be written in command exactly as they are written in "work" folder)
go to "work" folder, and BOOM you have a ready flashable odin .tar.md5 file for your Gnex!

[SCRIPT][17.04.22][v1.2.0] MIUI Power Menu Patcher - add recovery & fastboot reboot

[SCRIPT][17.04.22][v1.2.0] MIUI Power Menu Patcher - add recovery & fastboot reboot
This patch your system to have got recovery & fastboot reboot from power menu.
Download latest release
Changelog
-Added visual menu
-Added function to restore backups
-Added ability to supply environment directory as argument with `-d <dir>`
-Added a lot of code improvements
-Fixed correct build number in backup folder
-Fixed some Busybox issues
Thanks to @DarthJabba9 for all the work of this update.
All releases and changelogs
Source code on Github
How-To
This script is to use from Android, need a terminal app as Terminal Emulator for example and a rooted device. Tested in Redmi Note 2 with Xiaomi EU & MultiROM
Run from terminal this
Code:
su
sh DIR/miui-powermenu-patcher.sh
Change "DIR" to the location where is the script.
Pro tip: move the script to /data and rename to mpp for example to have easy access from terminal.
Example (click image)
Patch sh no such, following dir change it, any solution?
Sent from my Redmi Note 2 using Tapatalk
if i move file to /data so what command..still DIR?
rockadz9 said:
View attachment 4095317
Patch sh no such, following dir change it, any solution?
Sent from my Redmi Note 2 using Tapatalk
Click to expand...
Click to collapse
The problem is that tail search for $0 variable and in your case is miuipm.sh, so as in the script the current directory is changed and the script isn't in it, occurs that.
Thanks for report it, I will fix it. ATM run as: sh $(pwd)/miuipm.sh
harizamzi said:
if i move file to /data so what command..still DIR?
Click to expand...
Click to collapse
Run from terminal this
Code:
su
sh DIR/miui-powermenu-patcher.sh
Change "DIR" to the location where is the script.
Click to expand...
Click to collapse
Please read...
Updated to v1.1.1
Deic said:
The problem is that tail search for $0 variable and in your case is miuipm.sh, so as in the script the current directory is changed and the script isn't in it, occurs that.
Thanks for report it, I will fix it. ATM run as: sh $(pwd)/miuipm.sh
Please read...
Click to expand...
Click to collapse
Yes mate my ROM 7.3.23 xiaomi.eu, this file change name & directory same problem. (Miui-powermenu-patcher.sh =old version / mpp.sh =new version)
Any solution?
Sent from my Redmi Note 2 using Tapatalk
rockadz9 said:
Yes mate my ROM 7.3.23 xiaomi.eu, this file change name & directory same problem. (Miui-powermenu-patcher.sh =old version / mpp.sh =new version)View attachment 4096809
Any solution?
Sent from my Redmi Note 2 using Tapatalk
Click to expand...
Click to collapse
Did you try run as "sh /data/mpp.sh" (add "/" before "data") or "cd /data" and after "sh mmp.sh"?
Deic said:
Did you try run as "sh /data/mpp.sh" (add "/" before "data") or "cd /data" and after "sh mmp.sh"?
Click to expand...
Click to collapse
I try run as "sh data/mpp.sh" and run as "sh /data/mpp.sh"
Sent from my Redmi Note 2 using Tapatalk
rockadz9 said:
I try run as "sh data/mpp.sh" and run as "sh /data/mpp.sh"
Sent from my Redmi Note 2 using Tapatalk
Click to expand...
Click to collapse
and the result is the same? that is strange... what is your busybox version? and you can provide miui-powermenu-patcher.log under /data/miui-powermenu-patcher folder? looks like you have not got proper unzip busybox built-in command...
@Deic There seem to be 2 problems:
1. wget.zip - it seems that it does not get decoded properly with base64; in any case, the error log shows that it cannot be unzipped
2. The call to patch.sh - you might want to provide the full pathname
Edit: I think the wget problem is that the zip file is corrupt - probably a result of a wrong START_LINE
DarthJabba9 said:
@Deic There seem to be 2 problems:
1. wget.zip - it seems that it does not get decoded properly with base64; in any case, the error log shows that it cannot be unzipped
2. The call to patch.sh - you might want to provide the full pathname
Edit: I think the wget problem is that the zip file is corrupt - probably a result of a wrong START_LINE
Click to expand...
Click to collapse
The START_LINE is good in all versions released, I tested before of release them and all is fine... And the output of no patch.sh is because, no wget = no patch.sh. I will wait to @rockadz9 to see what is the issue, I maybe due to bad unzip or that seems.
Deic said:
and the result is the same? that is strange... what is your busybox version? and you can provide miui-powermenu-patcher.log under /data/miui-powermenu-patcher folder? looks like you have not got proper unzip busybox built-in command...
Click to expand...
Click to collapse
Yes results is the same, version Busybox1.26-2_arm64. and patch log attch
Sent from my Redmi Note 2 using Tapatalk
@rockadz9 Open the script file with a text editor, and add these lines near the top of the file
Code:
alias basename="busybox basename"
alias dirname="busybox dirname"
alias tail="busybox tail"
alias base64="busybox base64"
alias unzip="busybox unzip"
alias sed="busybox sed"
alias awk="busybox awk"
Then add 7 to the value of START_LINE, save the file, and run the script again.
1.2.0 released!
All the nice stuff of this update is thanks to @DarthJabba9, I did almost nothing.
Go to OP to download!
It's work for me, first one i run as 'sh data/mpp.sh and i got message no such....
and second time i run as 'sh /data/mpp.sh its work fine. thx bro
I'm trying to get this to work on stable EU version 7.0.6. After running the script the menu can be displayed but only the reboot option works. Both the fastboot and recovery cause the screen to become blurred and nothing happens. Pressing the back button clears the screen and I'm back at the point prior to pressing the power button. I've attached the script log. Can anyone tell me what's wrong ?
Cannot show text bellow addition icon
MIUI 9 7.9.7 global dev
worked great
thanks a lot

Categories

Resources