This is a request to all ROM developers to add their ROMS to ROM Manager.
This will make installing ROMS very easy and efficient for users without even touching the computers.
GUIDELINES:
FOR USERS:
1)You need to download and install the latest recovery from this page:
http://forum.xda-developers.com/showthread.php?t=1243133
2)Download ROM Manager from the market.
3)Open ROM Manager >Options>Manual Flash Override>Spice Mi700,Commitiva N700 and more>Clockwork Mod 3.x.
4)To download ROMS go to the download ROMs page.
FOR DEVELOPERS:
Go to the Developer Portal on:http://www.clockworkmod.com/
P.S.-I have already added a ROM on ROM Manager.
Feel free to download and try it.
GH - Keep up the excellent work & thanks.
My Vpad7 (ITE - Hwv 1.7) has been on CWM 3.0.2.8 and I upgraded to 5.0.2.6 - easy & simple with posted instructions in linked site - was running TJ_Style's ROM patched with non-OC kernel before but running EU.V1.7b ITE now.
Once I rebooted Recovery and navigated to Advanced/Debug Menu to Check Log, etc. - there's no "Go Back" option or menu item available, pressing the device's "Back" button does not work (tried other variations too.) Reset via the pin hole and reboot again into Recovery, check the newly reformatted card with partition/ext, and no "Go Back" option or menu item to Cancel/Undo or Escape.
Perhaps I missed the changes and I re-read the latest info posted ....
Otherwise, this is really & truely great - please kindly check and advise, much appreciated.
P.S. Looking forward to get it partner with ROM Manager and to reflash the EU V1.7b ITE ROM, etc. to the device as I've issues with the (DT's A2SD) scripts associated with the SD-Ext3 configuration.
The reason the back button is not working is because i build this ROM usings TJstyle's kernel which is not compatible with your device input hardware
The kernel was built using the source provided by FIH.
This source does not have the touchsreen input driver for the latest Viewpad7.
Only solution to this problem and all other ITE hardware related problems is to contact Viewsonic and ask them to provide the updated kernel source or borrow the driver from a similar Viewsonic device such a Viewpad10.
If you have a root file manager
open the file :sys/devices/virtual/input/input1/name
and post me the contents
googlehome said:
The reason the back button is not working is because i build this ROM usings TJstyle's kernel which is not compatible with your device input hardware
The kernel was built using the source provided by FIH.
This source does not have the touchsreen input driver for the latest Viewpad7.
Only solution to this problem and all other ITE hardware related problems is to contact Viewsonic and ask them to provide the updated kernel source or borrow the driver from a similar Viewsonic device such a Viewpad10.
Click to expand...
Click to collapse
Thanks, understood & it make sense to me. I will contact VS's tech. support with a request & see what they can provide or offer, etc. and post back results. Also, will search around for drivers from VPad10 ....
P.S. Even without the working "Back" button in Recovery, I managed to use it to format the mSD card, wipe & install new ROM, etc. - it's a bit tricky but manageable. And, the EU v1.7b ROM with ITE hardware support loaded ext3 nicely .... Kudo's
googlehome said:
If you have a root file manager
open the file :sys/devices/virtual/input/input1/name
and post me the contents
Click to expand...
Click to collapse
Used Astro File Manager to take a screenshot (attached) and to try to open the "name" file - it appeared to be a blank one, file size 0 or zero. Used ES File Explorer and getting the same ?? Is there anything specific to look for, or should I just try to extract/copy the file and upload it, kindly let me know. Thanks.
Letitride said:
Used Astro File Manager to take a screenshot (attached) and to try to open the "name" file - it appeared to be a blank one, file size 0 or zero. Used ES File Explorer and getting the same ?? Is there anything specific to look for, or should I just try to extract/copy the file and upload it, kindly let me know. Thanks.
Click to expand...
Click to collapse
Uploading the file would be great.
googlehome said:
Uploading the file would be great.
Click to expand...
Click to collapse
Here's the file saved in zip format. If this isn't it and/or you need another file or folder, just let me know or PM. Thanks.
in sys/devices/virtual/input/
how many folders do you have?
can you upload the name file of each folder?
googlehome said:
in sys/devices/virtual/input/
how many folders do you have?
can you upload the name file of each folder?
Click to expand...
Click to collapse
Checking under ....
there are 3 folders - input0, input1, input2
there is a "name" file in each of them, extracted each "name" file & zipping them together for upload.
Big thanks for looking into this for a possible resolution.
** Attached zip file has 3 name file:
name.input00 (renamed from name - for the input0 folder)
name.input01 (renamed from name - for the input1 folder)
name.input02 (renamed from name - for the input2 folder)
Changing them back to just name & putting them where they belong should do it. Please let me know if this isn't working and/or you need something else. Thanks.
I did some searching online and checked the kernel config of both the ITE and non ITE and came to the conclusion that:
The ITE and the non ITE devices differ by only one aspect i.e. touchscreen.
all other aspects are the perfectly the same.
The driver source file for the ite touchscreen hardware which should have a name similar to ite_i2c.c
is not being used by any other device.(Yet to confirm)
The only solution is to ask viewsonic to release the driver source file which they should under the GNU General Public License
googlehome said:
.... solution is to ask viewsonic to release the driver source file which they should under the GNU General Public License
Click to expand...
Click to collapse
Thanks for looking into the ITE driver issues, I will do a live chat with support on Monday - requesting the source file, and let's see what happen next. There's an Escalation Survey that I can fill out in email format for their reference & resolution/followup - will provide them with my Vpad7's serial number. Their download library & database on device drivers, ec. aren't the best - and is actually blank, zero for the Vpad7 here in the U.S. market. Well, one can ask & wish for it.
I reformatted my 16G mSD card & put it back in the pad, formatted it & set up a 1MB partition with zero swap file size, checked it to confirm that ext3 is present - before rebooting it again, then enable USB support, transferred zip files back and proceeded to flash the custom ROM file. I only use the pin method to reset or exit the sub/menu with the "Go Back" button not available, so it's fine. DT's A2SD installed & so forth, but the scripts not loading/running so did the A2SD check, A2SD reinstall and, A2SD cachepart - ran these from terminal, su enabled & all is good. Free of both internal space and memoryfor the pad to run. Most users (since many seemed to be using non-ITE hardware) will not run into problems but a few of us will, hopefully these info will be useful to the newbies ....
Ext4 partition is not supported in the ite kernel and im guessing even ext3 is not.
Try formatting the sd-ext partiton to ext2.
ITE Screendriver
Hello!
I have used es file manager to view the content of sys/devices and in folder
virtual/input1 the "name" file shows "ITE TOUCHSCREEN".
Now i think it would be helpful to zip the whole folder devices because there must be the screendriver in it ?!
Hello everyone
I am facing a serious problem, if fixed, then it will be a big acomblishment
I am trying to make RTL patches (for arabic,hebrew) on odexed ROMs. The problem is I couldn't apply the patch ( which is made for deodex only) to these ROMs but just in one case: Deodex the whole ROM using kitchen then applying the patch then reodex the whole ROM using a tool by TearsDontFalls. That way it worked.( mentioning that the patch got files of the /lib folder and these files are: libandroid_runtime.so,libwebcore.so, and new generated files lib__bcore,libicuuc-arabic.so
but the Problem that if I want to deodex just a specific file (in my case framework.jar) and reodex again using the guide from this link , The patch works fine in the apps, but some apps are not working. The browser open then after 2 seconds force close, and the Samsung keyboard doesn't appear, but instead a graphical image that can be pressed, then the keys apear and just writes it!!!!!!
In my opinion, the problem is related to these Lib files which seems share a work with the framework file (.odex or .jar)
If anyone solved this for me, then you will made my day and be my hero
note: I am using i9000 with cutom ROM GamerzRom v11 jw5, I did everything correctly and tried it many many times!!
thanks alot.
Can anyone tell me how to deodex Xperia Z2 6.0.1 firmware step by step? Thanks in advance....
+1
I am also looking for the same. On MM rom, Sony is using symlinks to link odex files.
A step by step guide would be highly appreciated.
Thank you
I'm not gonna go into deep details, but this should help.
- flash MM rom for your device, make sure it is ROOTED as you'll need to use an explorer with root access,it's better if you do this on a clean install, but this is just me
- boot your device and go through the setup process
- once done, install a browser with root access, I recommend MiXplorer, root explorer
- browse into /system folder
- check your /app, /framework, /priv-app, they should have odex files inside them (this was the case for me)
- copy these folders, plus build.prop file into sd card or the phone memory
- connect phone to pc and copy files over
- look up and download SVADeodexerForArtx(32 or 64 based on your system), you also need to have java installed on your machine.
- extract the SVADeodexerForArtxxx to your c: drive, and create a folder named /system insides, and post the files from your phone inside that
- your final folder will look something like this : c:/SVADeodexerForArtxxx/system/ (app, framework,priv-app) and build.prop file
- remember to move the Semcxxx app folder from /framework into /app folder or it won't be deodexed
- run SVADeodexerForArtxxx and point it to your /system folder, it will show you your android version, tick the checkbox for app, framework, priv-app, hit the start button
- it'll run and once done the log file will open and tell you how many were deodexed.
- the deodexed folders will be in the base folder, make sure to return the Semcxxx folder from the /apps to /framework
- create a flashable zip and flash these folders back on your rom
now your rom is deodexed
install Rom eXistenZ MM, rom is rooted and deodex
lokitooxd said:
install Rom eXistenZ MM, rom is rooted and deodex
Click to expand...
Click to collapse
The intention of this post was to learn how to do it. I know there is existenz and ultraslim deodexed roms. Thanks anyway.
@ticktock666
Thanks for the steps.
These steps looks to be from older version. Anybody with 6.0 Sony MM steps?
@ticktock666
There are certain other folders such as odex.app, odex.framework, odex.priv-app...what about these? These folders also contains similar odex files for app, framework and pri-app...
AlanDS said:
These steps looks to be from older version. Anybody with 6.0 Sony MM steps?
Click to expand...
Click to collapse
I deodexed my MM rom about a week ago, so I'm saying this from experience : it is up-to-date.
vikrant7027 said:
@ticktock666
There are certain other folders such as odex.app, odex.framework, odex.priv-app...what about these? These folders also contains similar odex files for app, framework and pri-app...
Click to expand...
Click to collapse
I'm not sure, but here's some of the stuff I noticed during the deodex process :
- I used to get the files using adb pull command directly to pc after a fresh rom install (remember to install a pre-rooted rom), but I did not get any odex files with the apps this way, so deodexing didn't work.
- after pulling the files from the device using a root explorer, each app had the odex files with them inside the correct folders.
- about odex.xxx folders and odex.xxx.sqsh files : they contain an exact duplicate of the odex files, no idea why (you can extract the sqsh files, they're basically special compressed odex file container sort of thing), which means the rom contains 3 versions of the same odex file, makes no sense.....
after deodexing and flashing the deodexed rom/files, I deleted odex.xxx folders and odex.xxx.sqsh files, and my rom works fine, fully rooted and with xposed. My current issue is that now if I browse into /data/app on the root of the drive I'll find an odexed version of every app I have installed, be it a user app or system app, and it's driving me crazy.
ticktock666 said:
I deodexed my MM rom about a week ago, so I'm saying this from experience : it is up-to-date.
I'm not sure, but here's some of the stuff I noticed during the deodex process :
- I used to get the files using adb pull command directly to pc after a fresh rom install (remember to install a pre-rooted rom), but I did not get any odex files with the apps this way, so deodexing didn't work.
- after pulling the files from the device using a root explorer, each app had the odex files with them inside the correct folders.
- about odex.xxx folders and odex.xxx.sqsh files : they contain an exact duplicate of the odex files, no idea why (you can extract the sqsh files, they're basically special compressed odex file container sort of thing), which means the rom contains 3 versions of the same odex file, makes no sense.....
after deodexing and flashing the deodexed rom/files, I deleted odex.xxx folders and odex.xxx.sqsh files, and my rom works fine, fully rooted and with xposed. My current issue is that now if I browse into /data/app on the root of the drive I'll find an odexed version of every app I have installed, be it a user app or system app, and it's driving me crazy.
Click to expand...
Click to collapse
Can u make a deodex rom for Xperia z2 mm rom d6502 indian version and post it on gdrive?? thanku in advance..? @ticktock666
Silverstarjigar said:
Can u make a deodex rom for Xperia z2 mm rom d6502 indian version and post it on gdrive?? thanku in advance..? @ticktock666
Click to expand...
Click to collapse
sorry buddy, but although just the deodexed files from my rom should work perfectly (it's only the apks, no other settings from the rom are included), it is near impossible for me to upload anywhere due to slow & unstable connection and power situation, since none of the hosting services support upload resume on their apps/sites.
ticktock666 said:
sorry buddy, but although just the deodexed files from my rom should work perfectly (it's only the apks, no other settings from the rom are included), it is near impossible for me to upload anywhere due to slow & unstable connection and power situation, since none of the hosting services support upload resume on their apps/sites.
Click to expand...
Click to collapse
Okk.. I will give it a try then!
Is there any script or something that we can flash through recovery ?
do you mean a script to deodex the rom on the phone ? if so then the answer is no
You can try this
ticktock666 said:
I'm not gonna go into deep details, but this should help.
- flash MM rom for your device, make sure it is ROOTED as you'll need to use an explorer with root access,it's better if you do this on a clean install, but this is just me
- boot your device and go through the setup process
- once done, install a browser with root access, I recommend MiXplorer, root explorer
- browse into /system folder
- check your /app, /framework, /priv-app, they should have odex files inside them (this was the case for me)
- copy these folders, plus build.prop file into sd card or the phone memory
- connect phone to pc and copy files over
- look up and download SVADeodexerForArtx(32 or 64 based on your system), you also need to have java installed on your machine.
- extract the SVADeodexerForArtxxx to your c: drive, and create a folder named /system insides, and post the files from your phone inside that
- your final folder will look something like this : c:/SVADeodexerForArtxxx/system/ (app, framework,priv-app) and build.prop file
- remember to move the Semcxxx app folder from /framework into /app folder or it won't be deodexed
- run SVADeodexerForArtxxx and point it to your /system folder, it will show you your android version, tick the checkbox for app, framework, priv-app, hit the start button
- it'll run and once done the log file will open and tell you how many were deodexed.
- the deodexed folders will be in the base folder, make sure to return the Semcxxx folder from the /apps to /framework
- create a flashable zip and flash these folders back on your rom
now your rom is deodexed
Click to expand...
Click to collapse
But with file odex.app.sqsh format...are that no need to extract
Sent from my D6503 using XDA-Developers mobile app
A1nur said:
But with file odex.app.sqsh format...are that no need to extract
Sent from my D6503 using XDA-Developers mobile app
Click to expand...
Click to collapse
sorry for the late reply, haven't been checking much recently.
now about those sqsh files, I've tried extracting them, and they seem to contains a 2nd copy of the odex files, not sure how they work, but after deodexing my rom I simply deleted them, and everything worked normally.
ticktock666 said:
sorry for the late reply, haven't been checking much recently.
now about those sqsh files, I've tried extracting them, and they seem to contains a 2nd copy of the odex files, not sure how they work, but after deodexing my rom I simply deleted them, and everything worked normally.
Click to expand...
Click to collapse
In new build fw 291 i try deodex that rom sir, n i do not extract sqsh.file...all normally work but if i delete boot.art n boot.oat it butlop....
How to i delete that sir
A1nur said:
In new build fw 291 i try deodex that rom sir, n i do not extract sqsh.file...all normally work but if i delete boot.art n boot.oat it butlop....
How to i delete that sir
Click to expand...
Click to collapse
I don't have the latest rom yet (not released for 6502), but when you go into your /system/app folder using a root explorer, do you see "arm" folder inside any of the installed apps ? maybe they changed something in 291, and now they only use sqsh files, also what does the log from the app says when you deodex the rom says ? it should say something like "300 apps deodexed, 10 apps already deodexed" or something like that.
ticktock666 said:
I don't have the latest rom yet (not released for 6502), but when you go into your /system/app folder using a root explorer, do you see "arm" folder inside any of the installed apps ? maybe they changed something in 291, and now they only use sqsh files, also what does the log from the app says when you deodex the rom says ? it should say something like "300 apps deodexed, 10 apps already deodexed" or something like that.
Click to expand...
Click to collapse
Thanks sir for your answered...
Sent from my Sony Xperia Z2 using XDA Labs
Hi!
Thanks, for good instructions!
It is also working for Xperia Z3 Compact on MM .291. I failed in the past, cause of forgetting 'semcxxx' in framework.
Greetz, brockn