Hi!
I had several different files to automate and I decided to collect them into one.
I added the file to the message. The archive contains the latest version of Android SDK Tools pulled adb and fastboot and the batch file for automating the following tasks:
1) Flash stock firmware via Fastboot
2) Flash stock firmware via Fastboot with clearing the cache and user data
3) Flash custom recovery TWRP via Fastboot
4) Check /data partitions for errors
5) Check /data partitions for errors whis auto repair
6) Format /data partitions with fast check for bad blocks
7) Format /data partitions with full check for bad blocks
8) Full clear /data partitions (fill zero)
I created this file to not have to enter the commands manually. This archive should be unpacked in the root of drive C. Folder was adb-t.
In this folder, copy the file of custom recovery for your tablet model and its version of the Android, rename it to twrp.blob. And also copy to this folder the blob file of your stock firmware.
Then run the file Many_Task_en.cmd (or Many_Task_ru.cmd for Russian).
I hope that it will be useful to someone.
Wow, thanks! I thing it will be very useful in the future!
Added in the Index for TF300
Good job
I found a small error - incorrectly pasted from the clipboard. File replaced.
Updated. Now all the files in the archive are from the Android SDK Platform-tools 18.0.1.
Added a new menu item.
Nice Job! Thanks!
BrateloSlava said:
Updated. Now all the files in the archive are from the Android SDK Platform-tools 18.0.1.
Added a new menu item.
Click to expand...
Click to collapse
Just used this to successfully update TWRP from 2.5.0.0 to 2.6.0.0 on the 4.1.1 JB bootloader via fastboot usb.
Not bothering with the 4.2.2 variants now that 4.3 is pending (and because the hdmi out doesn't work properly on any 4.2.2 ROM, including stock).
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
How to unbrick your ouya as long as adb is on and you have a clockwork mod recovery installed
I bricked my ouya recently so i just thought i would share this,it's going to work even if you completely erased all data and all caches in your clockworkmod recovery,this includes erasing sd card and even if you have boot menu and it won't show your nand as green lit but red lit,the nand is the chip that has the firmware on it if your not sure what it is.
This is for xp but i think it will work in other windows versions but don't quote me?It took 48hrs of perseverance for me to figure this out, And then to write this, i had to flit from page to page online copying links and reading it all over again,some comes from memory,other bits of the tutorial i made up my self and sussed it out on my own with no help,i had to click rename and copy file names in places in this tutorial.But it works and it rebuilds the ouya no mater what you did.
You could have erase the memory in clockworkmod completely,even if you wiped the dalvick cache and/or thesd card patition at the same time and/or clicked full factory reset after, no matter what you erased or how you did it even if you used the whole lot of every erase option applied from clockworkmod recovery on your ouya,
This restores it to factory,it even removes the boot menu software that i added and found [email protected] up my ouya completely after trying to add a boot img for the cynagenmod i put on over the top of my system by accident, then killed all data caches erasing them all i even erased my sd card data leaving my ouya completely bare of anything.
This is for others like me that only have the OUYA? next to device in the device manager in windows xp,i had so much trouble getting it going and i found a very quick easy couple of click fix for it,i could then adb command the ouya over a micro usb cable and rebuild it,You need to have the adk bundle for windows installed and the sets of tools needed for the current platforms this maybe api's not sure? just have the ones i use which are 14,16,17,18,19 and the google usb driver you may not need them all i may have more than needed but i don't know so best use what i have as it works for me,i am not going in depth on adding this but you can look here https://devs.ouya.tv/developers/docs/setup for info on the sdk install procedure just get the platforms i have as well as the guides listed platforms to install you'll see a picture of the sdk on this page so just use that as a guide.
So on with the guide then:
STEPS
STEP 1.Turn on ouya and go into clocklworkmod recovery menu and select install from zip then select sideload adb option and leave the console running in this mode please.Go here http://visualgdb.com/UsbDriverTool/ copy and paste that link in a new tab into the address bar and head down the page a little to the bit that says Downloading click the link that says UsbDriverTool-sfx.exe,you then get a page asking to save the file so save it where you can remember.Leave the page open and move onto step 2.
STEP 2. Open a new tab in the browser and paste this link: http://visualgdb.com/tutorials/android/ouya/ into the address bar and hit enter (return key).Now connect the ouya to the pc via micro usb cable and follow step 2. and step 3. from the current webpage you are on.You should now have Ouya ADB device or similar in the device manager meaning it works now.
STEP 4.install powertoy for windows xp don't ask me for a link this is going to be something you have to do as can't remember,it allows command on right clicking a folder this is a much needed thing for this job.
STEP 3. open a new tab in the browser and go here http://forum.xda-developers.com/showthread.php?t=2266629 and download the file named 1.0.68-r1 Download Changelog click the orange changelog writing to download and copy the downloaded file called RC-OUYA-1.2.995-r1_ota.zip by opening c:/ adt-bundle-windows-x86-20140321 or simlarily named folder residing in c: drive and then go into sdk folder then go into platform tools folder and paste the RC-OUYA-1.2.995-r1_ota.zip file in there, return to the c: drive ,then go to the folder called adt-bundle-windows-x86-20140321 or similarily named folder againand then into sdk folder again then highlight the platform tools folder with right click and click on open command window here leave this window open now.
STEP 4. Provided the command window is now open and the ouya was correctly set and enabled from STEP 1 and STEP 2. earlier,and STEP 3.. is completed you should now have the ouya on micro usb with the adb mode enabled and showing up as such in device manager, and you should now be sitting in the clockworkmod recovery in adb sideload mode on your ouya console ,go to the command window you left open in STEP 3. and simply type adb sideload RC-OUYA-1.2.995-r1_ota.zip ,this should now install the zip and after it is done you reboot the console from restart option in clockworkmod recovery and you should boot up fine and will have successfully repaired (unbricked) the ouya.
JOB DONE PHEW!
PHYSC-1 said:
How to unbrick your ouya as long as adb is on and you have a clockwork mod recovery installed
I bricked my ouya recently so i just thought i would share this,it's going to work even if you completely erased all data and all caches in your clockworkmod recovery,this includes erasing sd card and even if you have boot menu and it won't show your nand as green lit but red lit,the nand is the chip that has the firmware on it if your not sure what it is.
This is for xp but i think it will work in other windows versions but don't quote me?It took 48hrs of perseverance for me to figure this out, And then to write this, i had to flit from page to page online copying links and reading it all over again,some comes from memory,other bits of the tutorial i made up my self and sussed it out on my own with no help,i had to click rename and copy file names in places in this tutorial.But it works and it rebuilds the ouya no mater what you did.
You could have erase the memory in clockworkmod completely,even if you wiped the dalvick cache and/or thesd card patition at the same time and/or clicked full factory reset after, no matter what you erased or how you did it even if you used the whole lot of every erase option applied from clockworkmod recovery on your ouya,
This restores it to factory,it even removes the boot menu software that i added and found [email protected] up my ouya completely after trying to add a boot img for the cynagenmod i put on over the top of my system by accident, then killed all data caches erasing them all i even erased my sd card data leaving my ouya completely bare of anything.
This is for others like me that only have the OUYA? next to device in the device manager in windows xp,i had so much trouble getting it going and i found a very quick easy couple of click fix for it,i could then adb command the ouya over a micro usb cable and rebuild it,You need to have the adk bundle for windows installed and the sets of tools needed for the current platforms this maybe api's not sure? just have the ones i use which are 14,16,17,18,19 and the google usb driver you may not need them all i may have more than needed but i don't know so best use what i have as it works for me,i am not going in depth on adding this but you can look here https://devs.ouya.tv/developers/docs/setup for info on the sdk install procedure just get the platforms i have as well as the guides listed platforms to install you'll see a picture of the sdk on this page so just use that as a guide.
So on with the guide then:
STEPS
STEP 1.Turn on ouya and go into clocklworkmod recovery menu and select install from zip then select sideload adb option and leave the console running in this mode please.Go here http://visualgdb.com/UsbDriverTool/ copy and paste that link in a new tab into the address bar and head down the page a little to the bit that says Downloading click the link that says UsbDriverTool-sfx.exe,you then get a page asking to save the file so save it where you can remember.Leave the page open and move onto step 2.
STEP 2. Open a new tab in the browser and paste this link: http://visualgdb.com/tutorials/android/ouya/ into the address bar and hit enter (return key).Now connect the ouya to the pc via micro usb cable and follow step 2. and step 3. from the current webpage you are on.You should now have Ouya ADB device or similar in the device manager meaning it works now.
STEP 4.install powertoy for windows xp don't ask me for a link this is going to be something you have to do as can't remember,it allows command on right clicking a folder this is a much needed thing for this job.
STEP 3. open a new tab in the browser and go here http://forum.xda-developers.com/showthread.php?t=2266629 and download the file named 1.0.68-r1 Download Changelog click the orange changelog writing to download and copy the downloaded file called RC-OUYA-1.2.995-r1_ota.zip by opening c:/ adt-bundle-windows-x86-20140321 or simlarily named folder residing in c: drive and then go into sdk folder then go into platform tools folder and paste the RC-OUYA-1.2.995-r1_ota.zip file in there, return to the c: drive ,then go to the folder called adt-bundle-windows-x86-20140321 or similarily named folder againand then into sdk folder again then highlight the platform tools folder with right click and click on open command window here leave this window open now.
STEP 4. Provided the command window is now open and the ouya was correctly set and enabled from STEP 1 and STEP 2. earlier,and STEP 3.. is completed you should now have the ouya on micro usb with the adb mode enabled and showing up as such in device manager, and you should now be sitting in the clockworkmod recovery in adb sideload mode on your ouya console ,go to the command window you left open in STEP 3. and simply type adb sideload RC-OUYA-1.2.995-r1_ota.zip ,this should now install the zip and after it is done you reboot the console from restart option in clockworkmod recovery and you should boot up fine and will have successfully repaired (unbricked) the ouya.
JOB DONE PHEW!
Click to expand...
Click to collapse
Quick follow up,you can sideload over adb if it's turned on,this applies to standard recovery as wel.So you can unbrick using the adb sideload method above even with a stock ouya to unbrick it guys/gals.
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
In the past, for e.g. my 3-4 year old Samsung galaxy tab, I was able to extract those firmware files (the ones you flash with Odin), by using the trick described in many places... Unzip, run sgs2toext4.jar on the .img file, then mount resulting .img.ext4 in Linux Reader.
On the files for Tab S, sgs2toext4.jar is failing. Like it has done for other devices, see e.g. post #48 at link below. (it endlessly loops the file name dropped into the program window).
http://forum.xda-developers.com/showthread.php?t=2138885&page=5
What's the way to read these files, on Windows?
Thanks!
You need simg2img to convert to a raw image.
Here is the windows version, rename your .img file to system.img then run convert.bat. You can view the files with ext2explorer.exe or Linux reader.
simg2img
Thanks very much.
That worked like a treat.