Related
I've seen a lot of people asking how folks have changed the Windows logo to the HTC one and so on. I am one of those people!
There's a thread over in the Diamond Forum here, http://forum.xda-developers.com/showthread.php?t=437307, that discusses altering the taskbar icons.
I've had a read of that but it doesn't appear to discuss the start button. I've currently got a cab installed that gave me coloured icons on the taskbar but also the 3d MS Office style start button. I like the icons but not that start button.
Is there anyway someone could provide an idiot/noob style guide for altering that icon. I'd love to have the Vista start button on my HD (attached image) but have no idea how to go about it aside from I think it has something to with .dll files.
Can anyone explain this? Anyone? I know there would be a lot of people grateful for it! I've Googled and used the search but just cannot seem to find anything!
I've attached a mock-up of my ideal; I've got the coloured icons, just the start button to go!
I think....
the explanation is to edit the shellres.192.dll file here:
http://forum.xda-developers.com/showpost.php?p=2791169&postcount=3
using the process here?
http://forum.xda-developers.com/showpost.php?p=2791165&postcount=1
No?
EDIT: I am going to try myself this evening with your very nice icon...will let you know how it goes, if you don't beat me to it!
I believe you can do it with Wisbar.
Wisbar is not free.
http://www.lakeridgesoftware.com/
sk806 said:
the explanation is to edit the shellres.192.dll file here:
http://forum.xda-developers.com/showpost.php?p=2791169&postcount=3
using the process here?
http://forum.xda-developers.com/showpost.php?p=2791165&postcount=1
No?
EDIT: I am going to try myself this evening with your very nice icon...will let you know how it goes, if you don't beat me to it!
Click to expand...
Click to collapse
you had a chance at it yet? did it work?
...........
This is the thread I used to alter the Windows logo to a HTC logo among other things in this thread. It's dead easy,
1) Unsign the file using Unsigner linked to in the thread further up (on page 2 of the Unsigner thread there's a .bat file that I found gave a better idea of whether it had worked or not).
2) Open the file in Reshacker and go to Icon on the left hand side and click it to expand it. Go to number 292, click it and it will expand to show 1033. Click 1033 and it should be the start menu icon. Right click on 1033 and select Replace Resource. Select Open File With New Icon and find your new (resized) icon. Double click it and it will show a preview of new and old. Click Replace in the bottom right corner.
3) Save the newly modified file.
4) Sign the modified file using Ssigner linked to in the thread above. CHECK THE TEXT FILE IT CREATES TO MAKE SURE IT SIGNED OK. Don't forget this bit as it will mean a hard reset if you do (as I learnt).
5) If you've not installed SDKCert.cab some time in the past. download it from here, copy it to the phone and install it.
6) Copy the file to the Windows directory on the phone using Resco Explorer or Total Commander.
7) Reboot the phone.
how did you copy shellres.192.dll? it says "Acces denied" even with resco. No chance to renaming also
To get the file in the first place you need a program called ROM Extractor on the phone to get the file from ROM. There are also different varients of the ROM for different locales. There's a description in the link above.
thanks for your efforts but seems a little complicated TotalCommander did the trick, resco seems to have some security check problems
anyway, unsigner doesn't work so i'm stuck
guap said:
anyway, unsigner doesn't work so i'm stuck
Click to expand...
Click to collapse
Try the .bat file in the second page of the Unsigner thread. Copy Unsigner, the .bat file and the file you want to unlock to the same directory and double click the .bat file. Also, because the file is from ROM make sure it's not marked as Read Only when you get it to your PC before unsigning it. If it's from ROM they're usually Read Only for a start.
frostywrath said:
you had a chance at it yet? did it work?
Click to expand...
Click to collapse
Not yet. Just got back from work. I need a different job...
I will try tomorrow. I have been meaning to give this s shot for a while now, and the icon you posted is what I have been looking for.
the bat only automize the process... It doesn't work anyway as it still use UnSigner
Do you have the cab to change the other icons? I had a quick look on the diamond thread but couldn't find the exact ones you have! Thanks.
guap said:
the bat only automize the process... It doesn't work anyway as it still use UnSigner
Click to expand...
Click to collapse
True, but when I tried Unsigner on it's own it didn't give any feedback as to what it was doing (or if it did I missed it) so I changed 150+ icons only to find it hadn't been unsigned and therefore couldn't be resigned. At least with the batch file I can check it's been properly unsigned before making changes.
Does it give you any error messages when you try Unsigner?
unclesomebody said:
Do you have the cab to change the other icons? I had a quick look on the diamond thread but couldn't find the exact ones you have! Thanks.
Click to expand...
Click to collapse
Do you mean me or someone else?
Prof. Yaffle said:
Does it give you any error messages when you try Unsigner?
Click to expand...
Click to collapse
that's the point: no errors from unsigner, but resourcehacker can't open my file (not valid bla bla bla)
In which case I'd say the file hasn't copied across properly from the phone. Reshacker should be able to open the file and allow editing even if it's still signed. I'd try ROM Extractor to copy the file from ROM to elsewhere on the phone and then copy that across to the PC.
unclesomebody said:
Do you have the cab to change the other icons? I had a quick look on the diamond thread but couldn't find the exact ones you have! Thanks.
Click to expand...
Click to collapse
Do you mean this cab?
http://cid-b6b1a627fbae21e5.skydrive.live.com/self.aspx/Public/Colored Top Bar.cab
Don't forget you'll need to install this first:
http://cid-b6b1a627fbae21e5.skydrive.live.com/self.aspx/Public/1SdkCerts.cab
Hope this helps.
Prof. Yaffle said:
In which case I'd say the file hasn't copied across properly from the phone. Reshacker should be able to open the file and allow editing even if it's still signed. I'd try ROM Extractor to copy the file from ROM to elsewhere on the phone and then copy that across to the PC.
Click to expand...
Click to collapse
uhm seems reasonable
but I don't want to extract all my whole rom for a stupid dll... I extracted with total commander, isn't supposed to work this way?
Nope, certain ROM files can't be copied using normal file copy programs. I've found that they try and copy, then say the "File already exists, do you wish to replace?" and then whatever you select you're left with a 0k file with nothing in it. The ROM extractor doesn't copy the whole ROM. When you launch it you get a list of all the ROM files. Double click the one you want to extract, give it a location (\ usually for the root directory of the phone) and a name and click Extract.
Ok, I will try. But how to replace when modified? If I can't even read it, how will I replace it?
Hi.
I made a quick and crude patch to the TilewavePanel.dll file to cruedly but effectively correct the Daylight savings problem that I and lots of others were having.
----------
To use this...
1. Download THIS - TilewavePanel.dll which is 920KB in size... or use the 355KB ZIP file attached to this post.
2. Copy the new TilewavePanel.dll file to My Device\Program Files\Panels\TilewavePanel. Replacing the original.
-----> You may need to rename the old file first as it is "in use" but it still lets you rename it.
-----> If you are using the basic File Explorer built in to Windows Mobile then you may need to go to the Menu and check Show all Files before the dll files become visible.
3. Go to the Registry using Resco or PHM... Navigate to, HKLM\Software\SonyEricsson\TilewavePanel\City\0, edit the DaylightSaving key and change it to 0.
3. Do a soft reset.
-----> If the time is still 1 hour fast, then go back to the registry and check that the DaylightSaving key is still set to 0.
----------
What this does is... Whenever the Tilewave Panel weather gets updated, instead of overwriting the DaylightSaving key in the registry it writes to a different key DaylighSavinX. But the Daylight Savings time is still read from the original key. So you can change it to 0 without it being overwritten.
Hope this is useful!
Wow, another potential person in XDA
thanks!!
after installing patched DLL panel manager hangs...
panel is not workin after copy .dll file bro
what happen??
Excellent, thanks allot for your updated dll file. It solved my problem with the wrong time and can now have the weather updated automatically
It freezes after a reset?
The patch is tested will all jerpelea's first 5 test ROM.
------------
EDIT: Just tested as working on Jerpelea's 6th test ROM too.
dave-ro-mex said:
It freezes after a reset?
The patch is tested will all jerpelea's first 5 test ROM.
------------
EDIT: Just tested as working on Jerpelea's 6th test ROM too.
Click to expand...
Click to collapse
working very well
i like the way you thinking, making the weather update false string and system still reading the original key XD
thanks!!
Now it works with the same time as on wm 6.5 thanks alot!!!
Works just fine. Cheers mate.
Very good work, mate.
Just like everything in coding, very simple fix. If I knew how to amend .dll files, I would have tried to make it not write to a key at all, and completely remove that line of code.
Thanks for this, makes the panel so much better!
Does not work for me :-(
Yeeeeeeeeees!!!! It works!!! Thank youuuuu!!!
papa Marco said:
Does not work for me :-(
Click to expand...
Click to collapse
Agreed. I can't get this fix to work either. It works until automatic update and reverts back to being one hour ahead.
augie7107 said:
Agreed. I can't get this fix to work either. It works until automatic update and reverts back to being one hour ahead.
Click to expand...
Click to collapse
Sounds like you are not actually replacing the original dll file correctly. As the patch works just fine.
Go to My Device\Program Files\Panels\TilewavePanel.
Make sure Show all Files is checked on the menu. Then rename the TilewavePanel file that is 918K in size to "Old" or "Backup" or something like that.
Then Copy the patched TilewavePanel file from your Storage Card or using ActiveSync to My Device\Program Files\Panels\TilewavePanel.
Soft-Reset the device.
Go to the Registry and Set DaylightSaving to 0.
-------
You can confirm if the patch is installed by... First updating the weather on the Tilewave. Then, going to HKLM\Software\SonyEricsson\TilewavePanel\City\0 in the registry. There should be a new DWord value called "DaylightSavinX". If that key isn't there, it is not installed.
dave-ro-mex said:
Sounds like you are not actually replacing the original dll file correctly. As the patch works just fine.
Go to My Device\Program Files\Panels\TilewavePanel.
Make sure Show all Files is checked on the menu. Then rename the TilewavePanel file that is 918K in size to "Old" or "Backup" or something like that.
Then Copy the patched TilewavePanel file from your Storage Card or using ActiveSync to My Device\Program Files\Panels\TilewavePanel.
Soft-Reset the device.
Go to the Registry and Set DaylightSaving to 0.
-------
You can confirm if the patch is installed by... First updating the weather on the Tilewave. Then, going to HKLM\Software\SonyEricsson\TilewavePanel\City\0 in the registry. There should be a new DWord value called "DaylightSavinX". If that key isn't there, it is not installed.
Click to expand...
Click to collapse
I'm sorry but my ignorance is frustrating me.
First download link is bad. Zip file can't be downloaded to device with IE because it opens straight to Total Commander and won't extract.
Opera 10 Beta keeps hanging up and I can't get it that way either.
Downloaded to PC, extracted dll and emailed it to my account.
Accessed with device and followed instructions. Still not working for me.
Extracted dll is 918.7kb just as original.
Can you possibly enlighten me?
After Hardrest my device it works - only the Mail-Button has no functionality right now.
very very good. thanks, now the panel is useful
Thank you. I love you, mon.
Simply changing the daylight saving time from 1 to 0 or vise versa wortked for me - did not need to change dll.
Ctrl+A said:
Simply changing the daylight saving time from 1 to 0 or vise versa wortked for me - did not need to change dll.
Click to expand...
Click to collapse
Do an update for your weather and check again.
I'm new to this and just need a tutorial on how to create custom splash screens on a Evo. If any one can show me or post a link that be great.
Download this and unzip it. (On your computer)
http://db.tt/YLmI87K
There's a how-to included in there that tells you how to use it.
Sent from my HTC EVO 4G with Tapatalk
there's also a program called nbIMG, along with the one mentioned above.
Thanx working great!!
These instructions work for anyone who rooted using the "UnrEVOked" method such as that given at HTCEvoHacks.com. I have not tested these instructions with any other root method out there.
For the sake of these instructions, all references and instructions dealing with PhotoShop are assuming you are using PhotoShop CS5. Cammands may be slightly different on older versions of PhotoShop, so it may take a few extra clicks to find what you're looking for.
1. You can download custom boot images from the web, or create your own in PhotoShop using ANY sort of photo, graphics, text, or combination. You MUST make sure that the image size is set as the same for the EVO's screen resolution (480x800). For this reason, I would double check any image file you try to use prior to converting it for use with your phone.
2. Open your image file in Photoshop and make whatever tweaks or enhancments you like. Remember to "flatten" the image prior to saving it out if you have multiple layers in your file. You can use the next step to resize the image first if you like, but depending on your current settings in PS it should not matter.
3. Right click the file window (the one that contains your image) and set the "Image Size" settings to a width of 480, and the height to 800. These measurements MUST be in pixels as well. If you have the "Constrain Proportions" box checked, you may not be able to tweak these individually without affecting the other. So uncheck that box and change the size settings. Click ok to close the box and the image will resize within Photoshop.
4. After you have finished creating your custom image, flattening the image, and resizing it to fit on your phone's screen, it is time to save the file. Navigate to the "file" menu and click "save as". Here, you can choose where to save it, name it, and choose the file format. It's probably easier to go ahead and save it as "splash" now, so that you wont have to rename it later. Either way, this file MUST be named "splash" when we are in the final stages. Save it as the "BMP" format, and you will get a pop-up window for the BMP options. "File Format" should be set to Windows... and choose the depth option of 24 Bit. The "compress" and "Flip row order" boxes should be unchecked, and you do not need to go into any advanced settings. Once you have saved the file, You can close PhotoShop.
Now the File needs to be converted from the BMP format into an IMG file. This is so that the bootloader in your phone will see it when you flash it to your phone.
There are a few conversion tools out there, but I have found Splash Screen Creator to be the EASIEST way to convert the file with a few clicks.
The link to download this small program is here... http://www.addictivetips.com/?attachment_id=43073 ... and it is FREE!!! (I did not create this program)
1. Download the .zip package from the link above.
2. Extract the files. I found that creating a folder on my desktop to secure these files (and these files only) to be less of a headache.
3. After you have extracted the files, you are ready to convert your "splash.bmp" file. You MUST move this file into the same directory that you unzipped the Splash Screen Creator to. It will only find the bmp file in the same directory, which is why having its own folder is easier. Move your "splash.bmp" file to the same folder and open "RUN THIS ONE". This will open the program in a command prompt.
4. Choose option 1 to convert your existing .bmp file into the required .img file. The next option will ask if you would like to flash the file to your phone. This option is not necessary for these instructions, but I have read of others being successful. You can try this option, but if it fails, go on to the remaining steps.
5. Go ahead and close the program by pressing another key to exit. You should see your new "Splash.img" file in this same directory. Rename this as "splash1.img"
Now that I think of it, naming the BMP file to "splash1" prior to converting to the .img format may solve the error when trying to flash the file to the phone
within Splash Screen Creator. The img file MUST be name "splash1" prior to updating it in the bootloader in the next steps so it makes sense that the program would come up with an error at this point. I have not tested this theory at this time, but you are welcome to. If someone does test this, please update these instructions
to save from many unnecessary steps below!
Your next steps require access to your original "PC36IMG.zip" file that you used during your root process. If you do not have your original "PC36IMG.zip" file, you
can try to download one here... http://forum.xda-developers.com/showpost.php?p=8913849&postcount=156 ... I have not tested this file yet, but worth a shot if you dont have it.
1. Make a COPY of your "PC36IMG.zip" file and move it to your directory where you have worked with the custom splash files. This saves from getting confused between files and flashing the wrong one to your phone. You're also making a copy so that your original "PC36IMG.zip" file is NOT altered.
2. DO NOT unzip the file! Simply drag your "splash1.img" file over to your zipped "PC36IMG.zip" folder and copy it in there. If you get a prompt to overwrite an existing "splash" file, go ahead. Afterall, you are working with a copy of the PC36IMG.zip.
3. After you have added the "splash1.img" file into the "PC36IMG.zip" folder, you can now move the zipped folder over to your sd card. Make sure that it is the ONLY copy on your sd card, and that you have not placed it in any other directories. BOOTLOADER WILL NOT FIND IT IF IT IS IN ANOTHER FOLDER!!!
4. AT THIS POINT YOU WANT TO BE SURE YOU HAVE BACKED UP YOUR ROM!!!! YOU WILL LOSE YOUR CURRENT ROM AND DATA AFTER THE NEXT STEP!!!!
5. Reboot the phone into Bootloader by holding the volume down button and pressing power. The bootloader will find your "PC36IMG.zip" and ask you if you want to update. Press the volume up button to say YES! Grab a coffee, chug a beer, or take a piss, cause this step takes a few minutes.
6. Once the bootloader has finished it's update, reboot your phone. it will now display your new custom splash screen!!! (but you're not done yet)
Because you updated your "PC36IMG.zip" files in the bootloader, you have in effect reflashed the stock rom (rooted of course) back to your phone.
Allow a few mintues for your phone to boot up, log into your g-mail account (so that you have access to the market), and download Rom Manager (or your favorite backup
manager), and restore back to your rom!
Like I said before, I have only done this on the HTC EVO that has been rooted using UnrEVOked through the process explained on HTCEVOHacks.com. I have no idea if
this process will work with other configurations, and I accept no responsibility for the outcome of your actions!!!!
Can't u flash these also ??
neno2323 said:
Can't u flash these also ??
Click to expand...
Click to collapse
They're "flashed" in the bootloader, as a PC36IMG with the file being respective to how you rooted. You can also "flash" them using fastboot, but that can only be done if you're on the .76 bootloader.
im trying to make my own rom trying to try new this out and i was going around taken lil apps tht other roms hads like hulu, mastermind mirror, ect and i dont think i zip it correctly cause when i check the inside of the zip folder the other file is still not zip and i am sure that is a problem right ??? ps im using cwm 3.0 is tht a problem ?
i use this meth...
ok, here it goes.
first, figure out where you want to push your file. i'd reccomend pushing manually in recovery to make sure the file itself works. then, using a tool like 7zip (pc) or betterzip (mac) create a file structure that matches the one on the phone. for example, if you wanted a boot animation to be put in system/customize/resource, make a folder system, customize in that, resource in that, and the bootanimation.zip inside that. now you have the main part. next, make a folder in the root of the zip called META-INF (caps counts) inside that, com, inside that, google, and inside that, android. thats /META-INF/com/google/android/. inside android, you need to place in an update-script. i'd reccomend taking one from another zip and just editing it becasue i still have not figured out a way to make that type of file (unix exec) from scratch. open it up in a .txt editor like notepad++ (pc) or coda (mac) and write your script. here is the baisic script for copying the directory system on the zip to system on the phone (like flashing a boot animation).
copy_dir PACKAGE:system SYSTEM:
CAPS COUNT AND MAKE SURE YOU HAVE AN ENTER AT THE END. IF YOU DO NOT HAVE AN ENTER AT THE END (TO MAKE IT TWO LINES INSTEAD OF ONE, LIKE ISSUEING A COMMAND) THEN IT WILL NOT WORK AT ALL ( E:SYNTAX ERROR IN UPDATE-SCRIPT IS THE ERROR YOU WILL GET)
so put this file into the folder android, and zip it. make sure it is in store only, compatibility mode, if you have such options. then, use an auto signer (or just say zip is not signed and make sure to put sig verification off) to sign the zip. flash, and watch your work magically appear.
the update-script i showed is written in amend. i have no idea how to write in edify bcuz it is much more complicated with the binary and stuff. so dont flash with cwm 3.0+.
i only have 1 thing to say first switch to amon ra amon ra is 1000 times better than clockwordmod
how do i switch?? lol also what if i unroot my phone would tht be a problem?
Jcki4 said:
how do i switch?? lol also what if i unroot my phone would tht be a problem?
Click to expand...
Click to collapse
go here and download the PC36IMG.zip and follow the directions
http://forum.xda-developers.com/showthread.php?t=705026.
as for setting up a rom unzip one to see how it's set up, i have changed a few things in some and zipped it back up and signed it but never built one, sorry couldnt be more help
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