Related
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.
Extracting ROM files from HTC RUU
Official HTC ROM updates are released as RUU (ROM Update Utility), which you run on your (Windows) PC to get the target device updated automatically.
Some of the big brains in the Android community release RUUs re-packaged into signed update files,
which in turn allow for whatever ROM customization you can imagine.
In this how to I will explain how to extract ROM files from a RUU image,
which you can then customize and use to flash your device without the fear of a new bootloader possibly making your device unrootable.
Requirements :
Windows PC,
Microsoft Process Monitor,
File Archiver capable of extracting ZIP files(eg, 7ZIP),
Official HTC RUU for your Android device.
The process of extracting ROM files from a RUU is really straightforward.
The idea behind it is that the self-contained update utility first needs to unpack the update payload into a temporary folder before pushing it onto the device.
This is when we grab the ROM file...
1. download the official RUU
2. start Process Monitor.
3. press CTRL+L
4. change "Architecture" to "Process Name"
5. leave the "is" field as it is
6. in the empty field copy and paste the name of your
RUU file (eg, RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1_Radio_12.65.60.29_26.14.04.28_M_release_225512_signed.exe)
7. click "Add"
8. change "Process Name" to "Path"
9. change "is" to "Contains"
10. in the blank field type "rom.zip" (without quotes)
11. click add
Click "OK" to set the filter and then run the RUU file.
Once the utility starts switch back to Process Monitor and look for an entry in the "Path" column that ends with "\rom.zip".
Right click on that line and select "Jump to..."
this will open a Windows Explorer window in the folder which contains the zipped ROM files
Copy the "rom.zip" file to some other folder, outside of the temp RUU folder tree (eg, desktop)
Once copied, close Process Monitor and the RUU utility.
The copied "rom.zip" file contains the following files:
android-info.txt - list of CIDs this RUU will flash to,
boot.img - root file system image,
hboot (followed by a version string) - boot-loader update,
radio.img - radio driver update,
recovery.img - recovery partition image,
splash1_Hero_320x480.nb0 - boot loader splash image,
system_rel.img - system partition image,
userdata.img - data partition image.
You can now, among many other things, root the ROM
and then flash the updated boot.img and all the other image files on to your device using Recovery
it doesnt work... the process monitor colum is all blank after running RUU... there are no processes listed
munnibhai said:
it doesnt work... the process monitor colum is all blank after running RUU... there are no processes listed
Click to expand...
Click to collapse
you mst be doing something wrong i double checked the method and it still works fine for me..
make sure your environment is set up correctly and run everything as administrator or disadle uac in windows..
thanks for the reply, let me check it again...
i will post back to u
rom.zip corrupted
I followed the directions and like another post in here procmon shows a blank screen. I went to task manager and opened processes and saw when it ran then clicked open file location and found it. I did this twice and both zips are corrupt. (used winzip)
error [D:\android apps\EVO root\EVO\rom.zip]: start of central directory not found; Zip file corrupt.
Possible cause: file transfer error
when I close the RUU all the files in that folder disappear so you have to leave the RUU running while you copy the zip file or it's gone.
At least that's what I saw.
update to last post
I found a zip repair tool and was able to repair and extract the 1.10.653.2 RUU rom capture. I will have to try to run it later. If anyone gets corrupted zip error, Zip Repair pro will repair it.
To get the rom zip without any errors just run the ruu.exe file, when the box with a picture of a phone pops up, click start on pc, type in "run" and click on run then in that box that pops up, type in %temp% and click ok. Another window pops up then just scroll down to the most recent folder and rom.zip will be in there, if not it will be in the next folder.
Hi,
when I try to open the rom.zip I get an error message, it just said it cannot open with 7zip and with windows it says its invalid.
I tried downloading the RUU multiple times but still the same error. I rune the RUU as administrator.
Tried copying it over to different locations and then open it.
RUU_ENRC2B_U_JB_45_O2_UK_1.14.206.13_Radio_3.1204.167.31_release_289474_signed
HTC ONE X+
Thank you
Update:
I used Zip Repair Pro.. however there is no boot.img inside the repaired zip -_-
For those which have problem with making Process Monitor detect RUU temp folder, make sure You add whole file name of RUU including .exe at the end.
Jmcclue's steps, work perfectly, Thank you post #7
htc RUU Rom
Inside 4ndroid said:
Extracting ROM files from HTC RUU
Official HTC ROM updates are released as RUU (ROM Update Utility), which you run on your (Windows) PC to get the target device updated automatically.
Some of the big brains in the Android community release RUUs re-packaged into signed update files,
which in turn allow for whatever ROM customization you can imagine.
In this how to I will explain how to extract ROM files from a RUU image,
which you can then customize and use to flash your device without the fear of a new bootloader possibly making your device unrootable.
Requirements :
Windows PC,
Microsoft Process Monitor,
File Archiver capable of extracting ZIP files(eg, 7ZIP),
Official HTC RUU for your Android device.
The process of extracting ROM files from a RUU is really straightforward.
The idea behind it is that the self-contained update utility first needs to unpack the update payload into a temporary folder before pushing it onto the device.
This is when we grab the ROM file...
1. download the official RUU
2. start Process Monitor.
3. press CTRL+L
4. change "Architecture" to "Process Name"
5. leave the "is" field as it is
6. in the empty field copy and paste the name of your
RUU file (eg, RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1_Radio_12.65.60.29_26.14.04.28_M_release_225512_signed.exe)
7. click "Add"
8. change "Process Name" to "Path"
9. change "is" to "Contains"
10. in the blank field type "rom.zip" (without quotes)
11. click add
Click "OK" to set the filter and then run the RUU file.
Once the utility starts switch back to Process Monitor and look for an entry in the "Path" column that ends with "\rom.zip".
Right click on that line and select "Jump to..."
this will open a Windows Explorer window in the folder which contains the zipped ROM files
Copy the "rom.zip" file to some other folder, outside of the temp RUU folder tree (eg, desktop)
Once copied, close Process Monitor and the RUU utility.
The copied "rom.zip" file contains the following files:
android-info.txt - list of CIDs this RUU will flash to,
boot.img - root file system image,
hboot (followed by a version string) - boot-loader update,
radio.img - radio driver update,
recovery.img - recovery partition image,
splash1_Hero_320x480.nb0 - boot loader splash image,
system_rel.img - system partition image,
userdata.img - data partition image.
You can now, among many other things, root the ROM
and then flash the updated boot.img and all the other image files on to your device using Recovery
Click to expand...
Click to collapse
this is good working 100% thank you :good:
i_4_u89 said:
this is good working 100% thank you :good:
Click to expand...
Click to collapse
no problem and please instead of saying thanks please remember to hit the thanks button on threads first post..
works great, to bad you cant open the zip file
jpwhre said:
works great, to bad you cant open the zip file
Click to expand...
Click to collapse
You can open the zip. Go back a page n try the way i said.
jmcclue said:
You can open the zip. Go back a page n try the way i said.
Click to expand...
Click to collapse
note path is desktop (last post showed from temp folder) and i still get same results. did some searching and aperantly htc now signs their zip files and they can't be opened anymore. having usb issues that causes fastboot force close errors and need to be able to flash boot.img thru flashify app to return it to stock. ran the htcguru reset rom that uses aroma installer to return to stock that lets me take ota's but i get qualcom location force close and other custom roms give me issues forcing me to reset phone to stock every few days with guru installer. flashing recovery in fastboot is a chore as well. I have s-off and can keep it, but doing fastboot oem lock wont relock the bootloader, even though it shows success in cmd line. i can cid and super cid with fastboot.
it leaves me at a point where i really need to pull everything out of the rom.zip file and it wont open.
pic 1, 7zip wont open archive on desktop
pic 2, how i get recovery to flash
pic 3, results from running RUU
i have to reboot device, set comand to reboot bootloader, set command to flash recovery all faster than phone will do all commands to get it to flash, and RUU doesnt work that fast. i know im on sprint with htc one m7, but google search "extract htc zip" "extract rom.zip" both lead to this thread as top result. no other searches will tell me how to open the archive, except one that resulted in "htc signed zips can no longer be opened"
you're more than welcome to give it a go
http://forum.xda-developers.com/showthread.php?t=2795856 Sprint_HTC_One_m7wls_5.05.651.2_RUU.exe
Did HTC change the way they create the exe? I don't find it, the biggest file is data1.cab file that I can't extract.
I'm trying to extract the stock rom for an ATT HTC One Mini (m4) because RUU keeps crashing on me and won't install. I am also rooted with S-off.
If anybody can help me get the stock m4 rom so I can go back to stock, I would really appreciate it.
SyPete said:
Did HTC change the way they create the exe? I don't find it, the biggest file is data1.cab file that I can't extract.
I'm trying to extract the stock rom for an ATT HTC One Mini (m4) because RUU keeps crashing on me and won't install. I am also rooted with S-off.
If anybody can help me get the stock m4 rom so I can go back to stock, I would really appreciate it.
Click to expand...
Click to collapse
No they didn't change it. Some ruu's use a different format requiring the use of a tool called unruu instead of trying to capture the zip file when using the exe (I just learned this today). I've gone ahead and used unruu and the resulting zips have been put in a single tar file. you can download it from here for about 30 days after which ill have to delete the file. also i dont know which zip has what in it.
hi
master how to open Zip firmware !!?
i want to open zip firmware (PM60IMG.zip Desire 400)with 7zip ! but shows below error :
"can not open file PM60IMG.zip az archive "
how to pass this encryption ?
gandolf007 said:
hi
master how to open Zip firmware !!?
i want to open zip firmware (PM60IMG.zip Desire 400)with 7zip ! but shows below error :
"can not open file PM60IMG.zip az archive "
how to pass this encryption ?
Click to expand...
Click to collapse
https://github.com/kmdm/ruuveal/tree/f4936338f19841c75edafbe7e622242105cb39aa
Hey everyone, I've made this thread to help people like me who face "(assert failed: getprop("ro.product.device" =="GT-S5360" error)" aka Status 7 error" while flashing custom roms/kernels.
Before we begin, here is a little introduction about it :-
Basically, Status 7 error is caused while the updater script of the Custom Rom/Kernel checks to see if the phone model of your phone is compatible with the ROM/Kernel you are installing, called “asserts”.
In a nutshell, "Asserts" is a safety valve which prevents you from installing a Rom/Kernel meant for another device on your phone. Say, a Galaxy S rom on Galaxy Y and vice versa.
A Status 7 error generally arises due to the carelessness of the developer of the Rom/Kernel.
Now, moving onto how to fix it. There are a no. of methods on internet about fixing Status 7 errors. Here, i'm going to list the one's that i think are easy and work most of the times.
Method 1 :-
Here, i'm going to cover the most common method of removing the asserts from updater script. This method works almost 100% of the times.So, lets start right away !
Step 1. Copy the ROM zip file to your
computer and extract it using your favorite unzipping software (WinRar recommended)
Step 2. Once unzipped, browse to the
META-INF/com/google/android
directory. You will find two files called
“update-binary” and “updater-script”.
Step 3. Rename “updater-script” to
“updater-script.txt” and open with your
favorite text file editor.
Step 4. Get rid of the line starting with “assert” to next semi-colon. Usually
this is the first line or one of the first
lines at the top of the text file.
Step 5. Save file.
Step 6. Rename “updater-script.txt”
back to “updater-script”.
Step 7. Rezip all the files you’ve
unzipped.
Step 8. Copy the new, edited zip file to your phone.
Step 9. Try re-installing ROM, now it
should install fine without Status 7 error.
You can do this even on your phone with root explorer
Method 2 :-
Now this method is tricky one ! This method can be helpful for people who are willing to try out custom roms/kernels but have regional varaiants of a phone. For example, Seven variations of the model Galaxy y exist:
S5360 L , S5360 B (Brazil), S5360 T ,
S536 3, S536 7 , S536 8 , and S536 9 .
So, basically this method is based on editing the build.prop of your phone.
However,this method is still untested so try it on your own risk and responsibility !
Open your build.prop.Search the following lines in build.prop having the model name and change them as shown below :-
ro.product.model=GT-S5360
ro.product.name=GT-S5360
ro.product.device=GT-S5360
ro.build.product=GT-S5360
Save the changes.Set the permissions and Reboot and now you may be able to install the rom !
NOTE :- Incase you're using this guide for flashing cm11, you'll have to change your device name to totoro.
Hello guys...
We all know that a custom recovery is far more important thing i rooted phone. But since we're talking about mediatek,its hard to find a suitable recovery.
Now these days,its very easy to create CWM based recovery through Mtkdroidtools. But,CWM is quite a oldschool yo!!
But TWRP is awesome!! Cuz its touch based and far more easy to use...but its so hard to find mediatek TWRP,so this guide will be helpfull i guess!!
~~Requirements~~
1.A computer with Windows 7 32 bit
2.The stock recovery.img[it can be found in your phone's stock rom]
3.TWRP script>>
Download link>> htt p://www .me diafire.com/folder/ca6 n5bb8 ocu87/TWRP_an d_CWMR
Download "Port-TWRP-V2.4.4.0-MT6589.7z" file from that link!!!
Now extract that 7z file and put the folder in your computer's C:// drive.....and put your stock recovery.img in C:// too.
Now open That extracted folder and you'll see a .exe file. Run that file as administration and a command window will appear.
Now it'll ask you to put your recovery.img in C:// and that is already done. So press Enter and follow the next steps. It'll ask you too put your device's chipset,resolution....so enter correctly.
When it is all done, close that Window and you'll see a folder is created called "Ported TWRP" open it and you'll get your newly created TWRP recovery.img. Copy that in your sdcard and flash it via latest Mobile Uncle Tools and voila!! You'll be rebooted to your TWRP custom recovery!!!!!
N.B>> this process is only for mt6577,mt6589 and mt6575.
Hit thanks if you like it.
Android Devilzz[root n stuffs]
Click to expand...
Click to collapse
This seems so easy I will try it
bro it shows error found please help me
Hello Guys,
i opened the thread in the Question&Answer Forum but somehow i have an different approach now that i learned how to rollback an firmware version with an locked bootloader. i dont know if it is possible, i more want to open like a discussion about it if this would be an thing someone could possibly do (and thats the reason im opening another thread for it, since it is not the same question anymore as in the other thread).
well, you can flash an image like EML-L29 8.1.0.129 to the device via the dload method. this image installs just fine, great. but now.. in my understanding the interesting part is this update.app. this update.app as far as my knowledge goes contains all this img files. you know, kernel system boot recovery etc.. wouldnt it be possible to simply replace the recovery.img with an twrp recovery.img, put the update.app back together, zip it in the necessary update_sdcard file and try to install it? i read about the tool "HuaweiUpdateExtractor", and this handy nice tool is showing the files.
another thought of me is: the installer is *verifying* the update.app somehow. but if it is verifying this file, there must be like a crc-file, some way of telling "this file is original" or "this file is okay". so maybe this is another part of the problem that i would have to take care of. but still i would need to know a lot more about the way the eRecovery works.
my ultimate goal is to solve the bootloader code problem since tackling it with dc-unlock and hcu wont work cause the security patch level seems already too high in the first versions of this phone. im basically search now ways around it - i know, there is actually no way to do it, but this is the reason why im opening this thread in hope to get some clues or ideas - and telling my own. oh and im pretty sorry if this is maybe annoying, i surely dont have any intention of spam the forums or stress too much on this topic (but it got me very interested).
Edit: i read in another board that it is nearly Impossible to switch the img files because they are encrypted. I guess it is not possible with this method so basically.. just ignore this thread. I guess there is really no way.
Also I think they have to do some checksum when flashing, so it's really impossible to just switch files...
About dload, i'm on 9.0.0.293 on EML-L29C432
I try the dload method to rollback to android 8.1, no success
i use an usb otg, created dload folder to root and place update.app extracted zip in dload folder
Also i created an "EML-L29_hw_eu" folder inside dload with again extracted from the hw zip file
When i use the dialer method, phone recognize the update.app file and reboot
after reboot to recovery, i have an error and i can't downgrade
What i did wrong ?
thanks
bender8125 said:
About dload, i'm on 9.0.0.293 on EML-L29C432
I try the dload method to rollback to android 8.1, no success
i use an usb otg, created dload folder to root and place update.app extracted zip in dload folder
Also i created an "EML-L29_hw_eu" folder inside dload with again extracted from the hw zip file
When i use the dialer method, phone recognize the update.app file and reboot
after reboot to recovery, i have an error and i can't downgrade
What i did wrong ?
thanks
Click to expand...
Click to collapse
well the biggest problem may be the image itself that you are trying to flash. if you take it from firmwarefinder, you will get most likely absolutely no success. you need to take one from androidhost.ru, the ones there worked for me. there you just put everything in the dload folder on your USB-Stick. oh and better use an full-OTA, not just an simple ota update, because that wont work (you cant just update a few files when you are already on EMUI 9). and on top of that: backup your phone first, because it is possible that after your downgrade you lose all data on your phone.
oh and another thing if you just want to get back to EMUI 8.1 (not a specific version you wish for), just use hisuite, because they are allowing the downgrade even more easily. the method i mentioned above is if you try to flash a specific version like i did with 8.1.0.120