So, here it is:
1: Download CM 9.1 and flash boot.img via fastboot http://forum.xda-developers.com/showthread.php?t=1706001 . I use the newest version of CM 9, and do NOT choose CM10, because it will not work.
2: Reboot and download root explorer or anything like that.
3: Download this http://forum.xda-developers.com/showpost.php?p=30382245&postcount=2 , take ICS multi DPI (I tested only stock Google Play, not inverted).
4: Put two .apk's from the .zip file (.zip/system/app) onto your SD-card
5: Put .apk's into /system/app, replace these with existing files
6: Open build.prop, and change:
ro.sf.lcd_density=320 to ro.sf.lcd_density=192
7: Reboot and enjoy tablet mode with Google play fully compatible! Also, I did a full wipe, so I recommend a full wipe after doing all these steps.
And as always, I do not take resposibility for bricks, but I will try to help.
You can do this in CM10 too dude
just change density to 170.
MeLViN-oNe said:
You can do this in CM10 too dude
just change density to 170.
Click to expand...
Click to collapse
Maybe, I did not try, but with DPI 192, everything is very small, and with 170, it will be microscopic
Sent from my Nokia 3310 using XDA App
Related
hey im not sure if i am the right section but i tried to search but none of the solutions i have found worked please help..
I apologize if i am in the wrong section
dr690n said:
hey im not sure if i am the right section but i tried to search but none of the solutions i have found worked please help..
I apologize if i am in the wrong section
Click to expand...
Click to collapse
1) Download the following file: http://xeno.bemaniso.ws/Launcher2.apk
2) Place file on the root of your SD Card.
3) Reboot into recovery, same method that you use to flash roms.
4) Under Clockwork, select Partitions.
5) Mount System through Clockwork
6) Unplug and Re-Plug in USB Cord to device or else you won't be able to continue.
7) Open a command prompt or whatever you use to use ADB, type adb shell
8) cd /system/app
9) rm ADWLauncher.apk
10) cp /sdcard/Launcher2.apk /system/app/
11) exit
12) Reboot phone normally.
Next time you flash a rom use winrar or 7zip to open the zip (do not unzip or extract it!!!). Go to system/app/adwlauncher.apk and delete it. Then drag and drop whatever launcher you want to use. Flash the new rom and you're done.
KCRic said:
Next time you flash a rom use winrar or 7zip to open the zip (do not unzip or extract it!!!). Go to system/app/adwlauncher.apk and delete it. Then drag and drop whatever launcher you want to use. Flash the new rom and you're done.
Click to expand...
Click to collapse
I thought stuff like that never works. ROM's and any other files such as apk's are usually signed. Therefore any modifications won't work and the package is corrupt unless you re-sign it. At least in my experience.
Hayzie said:
I thought stuff like that never works. ROM's and any other files such as apk's are usually signed. Therefore any modifications won't work and the package is corrupt unless you re-sign it. At least in my experience.
Click to expand...
Click to collapse
Clockwork let us flash unsingned .zip files, there is an option and you choose if you want clockwork to check if the files are singed or not, and as long as you dont screw and move stuff where is not supposed to be your not gonna get an "installaion aborted" message.... i always do that to remove apps i dont use from system/app before i flash the rom and i've never had a problem
but back on topic... yeah you can do what the second post says, or if you dont want launcher2 just install the launcher you want to use from the market or sdcard if you have the apk, set it to deafult home app then go to recovery and do steps 4 to 9 and reboot, adw should be gone.
Once you get everything set up, resigning is simple. Since you don't have to resign with this method though, that task it pointless.
Hayzie said:
I thought stuff like that never works. ROM's and any other files such as apk's are usually signed. Therefore any modifications won't work and the package is corrupt unless you re-sign it. At least in my experience.
Click to expand...
Click to collapse
I've never signed any of my rooms, ever. If you modify everything without unzipping it, using 7zip or the default package manager in ubuntu, there's no need to, regardless of what it is that you're replacing/modifying.
Hayzie said:
I thought stuff like that never works. ROM's and any other files such as apk's are usually signed. Therefore any modifications won't work and the package is corrupt unless you re-sign it. At least in my experience.
Click to expand...
Click to collapse
I just rename whatever I'm replacing it with to ADWLauncher and switch it out before I flash lol.
Hello,
I've removed the Gallery app (com.htc.album.apk) using the Titanium backup 'cause I wanted to replace it with another one. I do have the backup, but when I do a restore it just does the circle with restore in progress forever. Is there a way to restore the Gallery?
The only reason why I want to restore is that when I use the HTC Sense apps which cooperate with Gallery (for example the Camera), when I want to see the photos the apps crash - I thought it would be possible to choose another app like QuickPic for this photo browsing, but apparently not. Therefore I would be very grateful if somebody knows how to restore the app.
The phone has s-off and is rooted.
Thank you very much.
SOLUTION
OK, I've found a way how to do it, so just want to share with others, in case anybody gets into the same kinda trouble as I did ;-)
The steps:
1. Download the zipped RUU of the stock ROM and extract the APK and ODEX files of the app you want to restore (HTCAlbum.apk and HTCAlbum.odex in my case)
2. Using Root Explorer (or some other tool that can write into /system/app) copy the apk and odex files into it.
3. Again using the same tool set the permissions of the 2 files to rw-r--r-- and set the owner and group to 0 - root (both user and group)
4. What I did now was try to Install the apk in the /system/app, but it failed, so probably this step is not needed - just put it here in order to reproduce exactly all steps.
5. Reboot the phone -> after the reboot the app should appear in the app drawer and all HTC stock apps now work with using the Gallery.
Please if you try this method, write down your comment, whether you succeeded or not.
Cheers and good luck...
Didn't work for me. Tried apk and odex gallery from newest ruu.
I also accidentally removed the Gallery (com.htc.album.apk), and I've found a way out to do it.
First to do :
> Install the latest Java JDK.
> Install HTC Sync & drivers.
> Install the Android SDK.
> Open SDK Manager after installing the Android SDK successfully.
> Install every 'Available Packages' in SDK Manager.
> Edit 'Path' in Environmental Variables and put this behind the line
Code:
;C:\android-sdk-windows\platform-tools
> Enable USB Debugging on your HTC.
And after all this above..
1 -Connect your Wildfire to the PC.
2 -Reboot into CWM Recovery.
3 -Go to Mounts and Storage.
4 -Select Mount /system.
Then use adb :
Oh and make sure the HTCAlbum.apk is in the same map as adb.exe
Code:
adb push HTCAlbum.apk /system/app
-MAKE SURE YOUR DEVICE IS S-OFF- Otherwise it won't work.
Solar_ said:
MAKE SURE YOUR DEVICE IS S-OFF- Otherwise it won't work.
Click to expand...
Click to collapse
This doesn't need S-OFF. Just a Custom Recovery like Clockworkmod.
rocky7x said:
OK, I've found a way how to do it, so just want to share with others, in case anybody gets into the same kinda trouble as I did
The steps:
1. Download the zipped RUU of the stock ROM and extract the APK and ODEX files of the app you want to restore (HTCAlbum.apk and HTCAlbum.odex in my case)
2. Using Root Explorer (or some other tool that can write into /system/app) copy the apk and odex files into it.
3. Again using the same tool set the permissions of the 2 files to rw-r--r-- and set the owner and group to 0 - root (both user and group)
4. What I did now was try to Install the apk in the /system/app, but it failed, so probably this step is not needed - just put it here in order to reproduce exactly all steps.
5. Reboot the phone -> after the reboot the app should appear in the app drawer and all HTC stock apps now work with using the Gallery.
Please if you try this method, write down your comment, whether you succeeded or not.
Cheers and good luck...
Click to expand...
Click to collapse
It worked! Thank you:good:
Hello guys!!! After just receiving my amazing SGS2 i began flashing ROMs like a maniac just like any other of my phones xD and i was beginning to greatly fall deeply in love with both CM9 and AOKP but one thing which just really got under my skin was the DPI issues. Well ive done a bunch of research and i believe if you follow my steps all issues will be gone
Firstly, DO NOT SET DPI TO 160!!!!!!!
You must use a DPI of 161 or higher. I use 162.
Why? Well its cause anything lower and ICS thinks the phone is actually a tablet. Which is where a lot of the issues lie. But anyhow to the fix!
Easiest and permanent fix:
MARKET FIX
1. Download LCD Density Modder Pro from the market.
2. Set your desired DPI level
3. Click "Save as system DPI" allow device to reboot.
4. Once rebooted open up LCD Density Modder Pro again
5. Click "Fix Market Compatibility Issues"
6. Download both Modded play store AND GSF apk
7. Follow instructions....
8. Install both mods.
9. After a reboot everything should be working grand
PHONE FORCE CLOSE FIX
1. Simply visit ME and follow that thread to fix the phone. I used the latest phone.apk and have no issues
****VERY IMPORTANT FINAL STEP****
REBOOT TO RECOVERY, SELECT ADVANCED, SELECT FIX PERMISSIONS, REBOOT SYSTEM and enjoy!
Fix without LCD Modder Pro (For those who are cheap xD)
1. Change DPI using LCD Modder or editing build.prop
2. Download "hacked" market from attachment (I just googled this from when i had my HD2)
3. Using a root explorer or adb, navigate to /system/app and check to see what your market name is (Mine was Phonesky.apk) not sure if its universal though.
4. Rename attached file to whatever your market file is if not already Phonesky.apk
5. DELETE old Phonesky.apk
6. Copy the attached file to the /system/app directory
7. Reboot to recovery, and once again FIX PERMISSIONS (See above for a how to)
Well both methods work swell for me Its just the second method doesnt stick forever, and after awhile you must go into "Apps" setting and Clear the market cache. I guess there is something with the GSF mod that makes it stick. Not sure. But everything is working for me now and im a happy camper!
Any issues, feel free to post in here or PM me thanks all for looking! AND OF COURSE! HIT THANKS TO ANYONE WHO HELPS YOU!
I was browsing Galaxy S II xda thread when suddenly I found one thread started by paulobrien with very interesting app to RE- ODEX a DEODEXED stock / custom rom. I tried it with my phone which is running Perka's CompilationROM based on the leaked XXELK4 rom and it's working just fine till now. For more info about my setup, read my signature.
For step by step guide, follow the steps below (courtesy of theking_13. To go to the original HOW TO thread, click this)
"Odex Me" by Paulobrien! Here's the link to the original thread, all credit goes to him!
http://forum.xda-developers.com/show....php?t=1215271
Now here's where my part comes in, my step-by-step guide!
This will work on ANY DEODEXED ROM.
*Use this only AFTER you've made any changes to the framework or flashed .zips that change the framework.*
First and foremost, make a backup! You should always do this before messing with system files!
1) Make sure you have a rooted rom, without root the app won't do much but install.
2) Allow "Unknown sources" by going into Settings > Security > and scroll down.
3) Download the .apk either down below, or from the link above.
4) Install as a normal app.
5) Open the app, make sure you give it root access, and it will run.
6) Let it run, it will reboot your phone, take around 5-10 minutes, and then reboot again. You will be greeted by "Android is upgrading" which means its rebuilding your dalvik cache.
7) Once its at the lock screen, done! You can make sure it did its job by using a file explorer with root access (I use Root Browser, if that helps) and go to the root of your phone's memory, go to system > app, and you should see a bunch of "appnamehere".odex files.
Please show appreciation by pressing the thanks button for theking_13 and also paulobrien (without him, this easy-odex app simply won't exist)
I need an reverse tool ?
with this tool, can we re-odex this mod?
http://forum.xda-developers.com/showthread.php?t=2019109
No because it odexes only /system/app
Akshay (Aky) said:
I need an reverse tool ?
Click to expand...
Click to collapse
Me too +1
Sent from my GT-I9300 using Tapatalk 2
Does this also odex the framework files?
*************************SOLVED*****************************************************************************************************************************
Hi everyone!
I'm a noob. I got my Galaxy S3 T999V rooted and the boot (recovery?) runs clockworkmod. CyanogenMod 10 is running smoothly, except:
The camera doesn't work! Getting a "cannot connect to camera" error instantly upon launching the camera app (stock).
So from perusing the internet a little more, there are other phone models also suffering from this "can't connect to camera" error.
The fix involves: Booting into rooted stock. extracting the folder "cameradata" in system using a file explorer (AndroZip). Put them on the external sdcard or your computer. Then overwrite your CM10 flashed system/cameradata folder's .bin(s) and setting the permissions a certain way.
Does anyone have the stock Galaxy S3 cameradata files? And I have no idea how to change permissions!! HELP!!
*************************SOLVED*****************************I*TAKE*NO*RESPONSIBILITY*FOR*ANY*DAMAGES*OR*BRICKING*THAT*MAY*OCCUR***********
http://forum.xda-developers.com/showthread.php?t=2102981&page=2#post39859973
THOSE ARE THE FILES (or click here?)
1. Download the files, unzip them and place them somewhere on the phone (sdcard0 or sdcard1, in some separate, user-made folder)
2. Make sure you have CyanogenMod's built-in File Manager set to allow ROOT access
3. Using CyanogenMod's built-in File Manager, click the "parent folder" at the top until the top reader line says /
4. Look for a folder called system, enter it
5. Look for a folder called cameradata, enter it
6. With nothing selected, press the :: button in the bottom left, on-screen. Select "properties" and choose 'permissions', grant all properties to everything (except the S column). This allows you to copy the downloaded files into this folder.
7. Browse to where you have the files. On the left is a tick-box, tick them all.
8. Browse back to the /system/cameradata/
9. Select the :: again. Select "paste all items here". SELECT OVERWRITE.
10. Individually long-press each item and change it's properties. Select permissions and permit all except the S column again. This allows the app to be accessed, the user to change the app, and the app to save files.
11. Attempt to run the STOCK camera app. CHANGE THE SCENE "SCN" TO 'ACTION'. I've been told this keeps it from crashing again...
12. If the camera app is a bit laggy, try rebooting. If it persists (but camera app is functioning) may want to restore permissions using Recovery Boot (I use CWM).
The difference MAY be adding that one extra file (_ZH), but I recommend moving and overwriting all just to be safe.
Malumen said:
Hi everyone!
I'm new to the whole modding/cyanogen/clockwork thing. I got my Galaxy S3 T999V rooted and the boot (recovery?) runs clockworkmod. CyanogenMod 10 is running smoothly, except a few issues:
- The WiFi and mobile network connections fly between 20% and 60% (with the WiFi signal reaching 98%) when I am just sitting in my room and the phone is motionless. Do I need to update the radios to get better reception? (And how do I do that? I am on Mobilicity in Canada)
- What steps do I take to perform a restore? I've made a backup in the CWM boot/recovery of Cyanogen after I got everything working fine. If I messed some things up, what steps do I take to restore back to that point? Do I press Wipe Data/Factory Reset and Wipe Cache, or do I just select Restore and the file to restore using?
- THIS IS MY BIGGEST ISSUE: The camera doesn't work! None of the camera apps work in my CM10. Skype and Hangout using the front camera works, but no photo-taking apps work (they do not even run, just black then they back out to the Apps screen)
So how do I:
> Get more stable reception? Do I update the radios? If so, how?
> Perform a restore? What steps do I take to return to a backup I have of Cyanogen?
> Get my camera working?
Click to expand...
Click to collapse
try to reflash. wipe everything and make sure you didnt download nightly. nightlies can have some problems. are you sure you download the stable version?
KingKostas said:
try to reflash. wipe everything and make sure you didnt download nightly. nightlies can have some problems. are you sure you download the stable version?
Click to expand...
Click to collapse
May I ask quickly what steps are involved in "reflashing"? Just to make sure I don't do some extra step or miss something.
As far as the stable version goes, I looked for the d2tmo file on get.cm under the Stable tab. I'm assuming that would be the most stable build?
(Perhaps a nightly might fix it??)
Question: Is there not a way I can just install/add this "4.2" camera? I've seen videos and read that people are using that just fine on CM10. Alternately if I boot into recovery would "fix permissions" be any help?
re: odin flash
Malumen said:
Hi everyone!
I'm new to the whole modding/cyanogen/clockwork thing. I got my Galaxy S3 T999V rooted and the boot (recovery?) runs clockworkmod. CyanogenMod 10 is running smoothly, except a few issues:
- The WiFi and mobile network connections fly between 20% and 60% (with the WiFi signal reaching 98%) when I am just sitting in my room and the phone is motionless. Do I need to update the radios to get better reception? (And how do I do that? I am on Mobilicity in Canada)
- What steps do I take to perform a restore? I've made a backup in the CWM boot/recovery of Cyanogen after I got everything working fine. If I messed some things up, what steps do I take to restore back to that point? Do I press Wipe Data/Factory Reset and Wipe Cache, or do I just select Restore and the file to restore using?
- THIS IS MY BIGGEST ISSUE: The camera doesn't work! None of the camera apps work in my CM10. Skype and Hangout using the front camera works, but no photo-taking apps work (they do not even run, just black then they back out to the Apps screen)
So how do I:
> Get more stable reception? Do I update the radios? If so, how?
> Perform a restore? What steps do I take to return to a backup I have of Cyanogen?
> Get my camera working?
Click to expand...
Click to collapse
The very best advise is to do the following, doing anything else will most likely prolong
the problems you are having or making them even more difficult to resolve.
First thing you need to do is to install the stock Tmobile T999 rooted firmware.
Here are the exact step by step instructions with the download link for the firmware.
After you have followed these instructions your phone will be working properly and if
you like you will be able to flash any custom roms made for the Tmobile T999 phone
or restore any backups unless the the backup is corrupted in some way or another.
Here is the link to the Tmobile Stock & Rooted firmware you need:
http://www.androidfilehost.com/?fid=9390169635556426451
After downloading it make a folder on your desktop and unzip the file
using Winzip or 7zip so the .TAR file is in the new folder you just made.
Here is a link for ODIN which is required for flashing the stock rooted firmware
(a windows app) http://d-h.st/Q14
Download and extract Odin into the same folder you made containing the TAR file.
Here is a step by step guide for you.
Download the firmware of your choosing (use the root66 version if you want root)
Run Odin by double clicking the Odin.exe within the folder you extracted
Turn off your phone and boot into DOWNLOAD MODE (Volume Down + Home + Power Hold until phone powers up, then release and press Volume Up to enter Download Mode)
Once in Download Mode, connect the USB/Charger cable to the phone and plug into the USB port on your computer.
You should now see a COM** port listed toward the top-left of Odin (under ID:COM)
Click on the PDA button in the middle-right area of Odin.
Browse to and select the FW you downloaded (TAR file)
Make sure Auto-Reboot and F. Reset Time are the only options checked and that PDA is the only other thing checked.
TRIPLE CHECK your settings and that you have selected the correct firmware for your model phone and are using the correct options.
If you are using a laptop, make absolutely sure you are plugged in, or if on battery, that it is charged enough and will not go into sleep mode during flash.
Click Start to begin the flash. This will take a while, so be patient!
Once complete, in the top-left box in Odin, it will say PASS and the phone should have automatically rebooted.
You may unplug the phone and close Odin if you wish.
Wait at least 5-10 minutes for the system to boot the first time and then build its cache! (It may seem to hang during boot, this is normal and you must be patient!!!)
Misterjunky said:
The very best advise is to do the following, doing anything else will most likely prolong
the problems you are having or making them even more difficult to resolve.
Click to expand...
Click to collapse
I followed most of these directions the first time, using the guide from High On Android:
http://www.youtube.com/watch?v=QPeIZZVYHbY
I used Odin, got root, wiped and got CM10 working.
This seems to be a bit of a problem that has cropped up in other models (i747). The fix that was used was to get back to the Stock ROM, while rooted, and browse to the system folder /cameradata/. In there are files for permissions for the camera. Copy those to the external SD card or your computer, then get back into CM10. Replace the CyanogenMod system folder /cameradata/ with the files you got from the Stock ROM. Then change the permissions for these new files.
So does anyone have the Stock /cameradata/ files? I'd greatly appreciate it!
re: camera issue
Malumen said:
I followed most of these directions the first time, using the guide from High On Android:
http://www.youtube.com/watch?v=QPeIZZVYHbY
I used Odin, got root, wiped and got CM10 working.
This seems to be a bit of a problem that has cropped up in other models (i747). The fix that was used was to get back to the Stock ROM, while rooted, and browse to the system folder /cameradata/. In there are files for permissions for the camera. Copy those to the external SD card or your computer, then get back into CM10. Replace the CyanogenMod system folder /cameradata/ with the files you got from the Stock ROM. Then change the permissions for these new files.
So does anyone have the Stock /cameradata/ files? I'd greatly appreciate it!
Click to expand...
Click to collapse
Just download any of the custom rom zip files based on the jellybean v4.1.1 stock rom.
All of those custom roms will have the files you are looking for.
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
d2vzw
This also works on the sch-i535 as well. Thank you so much.
kingsugar said:
This also works on the sch-i535 as well. Thank you so much.
Click to expand...
Click to collapse
Yes, I tried all the other options for getting my camera back on track, but only going back to a full stock (rooted) ROM got my camera up and running again. FWIW, I was running an AOSP ROM for months without issue. What kicked my camera offline (the dreaded can't connect to camera) for some strange reason was when I updated to the most recent firmware VRBMF1. Now its straight back to AOSP for me! Thanks for creating this post! Very helpful!
My fix
I'm going around posting my fix to all the camera threads in hopes of helping people find a solution sooner. I created a thread over in d2vzw http://forum.xda-developers.com/showthread.php?t=2492304
fix camera error on i9300 with cm 9 (4.0.4)
Malumen said:
*************************SOLVED*****************************************************************************************************************************
Hi everyone!
I'm a noob. I got my Galaxy S3 T999V rooted and the boot (recovery?) runs clockworkmod. CyanogenMod 10 is running smoothly, except:
The camera doesn't work! Getting a "cannot connect to camera" error instantly upon launching the camera app (stock).
So from perusing the internet a little more, there are other phone models also suffering from this "can't connect to camera" error.
The fix involves: Booting into rooted stock. extracting the folder "cameradata" in system using a file explorer (AndroZip). Put them on the external sdcard or your computer. Then overwrite your CM10 flashed system/cameradata folder's .bin(s) and setting the permissions a certain way.
Does anyone have the stock Galaxy S3 cameradata files? And I have no idea how to change permissions!! HELP!!
*************************SOLVED*****************************I*TAKE*NO*RESPONSIBILITY*FOR*ANY*DAMAGES*OR*BRICKING*THAT*MAY*OCCUR***********
http://forum.xda-developers.com/showthread.php?t=2102981&page=2#post39859973
THOSE ARE THE FILES (or click here?)
1. Download the files, unzip them and place them somewhere on the phone (sdcard0 or sdcard1, in some separate, user-made folder)
2. Make sure you have CyanogenMod's built-in File Manager set to allow ROOT access
3. Using CyanogenMod's built-in File Manager, click the "parent folder" at the top until the top reader line says /
4. Look for a folder called system, enter it
5. Look for a folder called cameradata, enter it
6. With nothing selected, press the :: button in the bottom left, on-screen. Select "properties" and choose 'permissions', grant all properties to everything (except the S column). This allows you to copy the downloaded files into this folder.
7. Browse to where you have the files. On the left is a tick-box, tick them all.
8. Browse back to the /system/cameradata/
9. Select the :: again. Select "paste all items here". SELECT OVERWRITE.
10. Individually long-press each item and change it's properties. Select permissions and permit all except the S column again. This allows the app to be accessed, the user to change the app, and the app to save files.
11. Attempt to run the STOCK camera app. CHANGE THE SCENE "SCN" TO 'ACTION'. I've been told this keeps it from crashing again...
12. If the camera app is a bit laggy, try rebooting. If it persists (but camera app is functioning) may want to restore permissions using Recovery Boot (I use CWM).
The difference MAY be adding that one extra file (_ZH), but I recommend moving and overwriting all just to be safe.
Click to expand...
Click to collapse
thanks a lot, i read your post, i take your advice to copy "SlimISP" to built in (cm system) folder, its work for me perfectly.
Thanks a lottttttttttttttttttttttt, have a nice day.