This thread is mostly to remind myself what needs to be done after a reflash. I reflash a lot. Tinkering, coding and hacking does *not* mate well with my ADHD (Attention Deficit ahh whatever), so I often find myself having to, pardon my french, unfuck my gear. Most of this thread will be links to the great work others have done, I'm just piling together the stuff I use. If you like your android experience to be nice and snappy, you might like these mods too. These steps work for me, your mileage may vary. If you screw something up, it's your own fault for taking advice from strangers over the Internet. But try asking for help here on XDA, somebody will most likely be able to help you.
So, either you've just unpacked your Defy or you have just had to flash an SBF after screwing something up.
Edit: 01/01/2011: Have added a few bits so the stuff below now applies to the 2.34.1 rom as well
0) Install LauncherPro
- Or ADW.Launcher, HELauncher or whatever you prefer. Press the Home button and set the new launcher as default.
1) Root the damn thing! Download Z4Root.apk here. You'll need to allow installation of non-market apps, as well as enabling USB debugging. Go to Settings -> Applications, tick the box for "Unknown sources" and go to Development to enable USB debugging. A file manager should be included in the stock rom, otherwise get one (I prefer ES File Explorer) from the Market. Once you have your file manager, dig up the z4root.apk you just downloaded, install it and run the app, press the appropriate button to root the phone and watch it reboot.
2) Get recovery!
The custom recovery for the Defy is described here. Mad props to Tenfar for his work, please buy him a beer, he's earned it. Here's the APK you'll need. Using the same process as for the Z4Root app, install and run the recovery system app. Press the "Install recovery system" button.
3) Get JIT'tery and deodexed
Superb work by Higgsy and Antibyte! They've not only gotten JIT (jfgi, mate) to run on the Defy, they've zipped it up nicely with the deodexed /system files from Paul at Modaco.com so you can all just install them as a zip file in one go. 2.21 Roms: Download the nicely packaged zip here, if you're running the 2.34.1 rom, get this version instead. Save the file to your SD card and remember where you put it.
4) Backup everything we've done so far
Start the System Recovery App and do a Recovery Boot. When booting into recovery, select Backup/restore and do a backup. I you have installed a bunch of apps, made a lot of changes to your settins, you might want to do a seperate backup of that (but not the rom), using Titanium backup from the Market.
5) Apply the coolness from step 3
After doing a backup, wipe all user settings as well as the Dalvik cache. Then select "Install zip from SD card" and install the zip you downloaded in step 3. Wipe alle settings and the cache again. Reboot when done. Note: The wiping may not be necessary, but not doing it could screw something up and have you back at re-flashing an SBF to your phone...
5.1) Re-root, using Z4Root.
Fire up the app and press "permanent root".
6) Weed out the bloat
This bit assumes that you have ADB or MotoDev studio installed and can connect to your Defy. If not? Search the forums. - Or read the US guide for trimming the Defy, tons of info right there, thanks a lot to Rob-T for elaborating many of the steps!
Assuming you have ADB fired up (or MotoDev Studio, which I prefer):
Gain root access:
Code:
su
Mount the /system partition with write access:
Code:
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
Switch to the /system/app dir:
Code:
cd /system/app
Now rename the apps you don't want: Thanks to NaeNee for proof-reading this hideous blob of commands!
Code:
mv AdService.apk AdService.rem; mv ArcPhotoworkshop.apk ArcPhotoworkshop.rem; mv ArcVideoEditorLite.apk ArcVideoEditorLite.rem; mv BlurEmail.apk Bluremail.rem; mv revolver_2_0_0012_embed_Signed_2010-04-13_11-07-08.apk revolver_2_0_0012_embed_Signed_2010-04-13_11-07-08.rem; mv BlurSNMessagingEngine.apk BlurSNMessagingEngine.rem; mv FBAndroid-1.3.2.apk FBAndroid-1.3.2.rem; mv Kindle-1.0.2-OEM-SingleSign.apk Kindle-1.0.2-OEM-SingleSign.rem; mv MySpace.apk MySpace.rem; mv StickyNoteWidget.apk StickyNoteWidget.rem; mv SocialMessaging.apk SocialMessaging.rem; mv Swype.apk Swype.rem; mv BlurUpdater.apk BlurUpdater.rem; mv CarDock.apk CarDock.rem; mv ContactsUnconnected.apk ContactsUnconnected.rem; mv amazonmp3_1.8.19_signed_zipaligned.apk amazonmp3_1.8.19_signed_zipaligned.rem; mv esmusica_2_0_0012_embed_Signed_2010-04-13_11-05-17.apk esmusica_2_0_0012_embed_Signed_2010-04-13_11-05-17.rem; mv Fota.apk Fota.rem; mv FriendFeed.apk FriendFeed.rem; mv HelpCenter.apk HelpCenter.rem; mv hiphopofficial_2_0_0012_embed_Signed_2010-04-13_11-08-31.apk hiphopofficial_2_0_0012_embed_Signed_2010-04-13_11-08-31.rem; mv truecountry_2_0_0012_embed_Signed_2010-04-13_11-06-12.apk truecountry_2_0_0012_embed_Signed_2010-04-13_11-06-12.rem; mv KPT.apk KPT.rem; mv HomeSyncWizard.apk HomeSyncWizard.rem; mv LiveWallpapers.apk LiveWallpapers.rem; mv LiveWallpapersPicker.apk LiveWallpapersPicker.rem; mv MagicSmokeWallpapers.apk MagicSmokeWallpapers.rem; mv MessagesWidget.apk MessagesWidget.rem; mv NewsWidget.apk NewsWidget.rem; mv Protips.apk Protips.rem; mv QuickContactWidget.apk QuickContactWidget.rem; mv Quickoffice_BasicViewer_2.0.42.apk Quickoffice_BasicViewer_2.0.42.rem; mv Quickoffice_BasicViewer_2.0.52.apk Quickoffice_BasicViewer_2.0.52.rem; mv revolver_2_0_0012_embed_Signed_2010-04-13_11-07-08.apk revolver_2_0_0012_embed_Signed_2010-04-13_11-07-08.rem; mv SocialMessaging.apk SocialMessaging.rem; mv StatusWidget.apk StatusWidget.rem; mv Stk.apk Stk.rem; mv ToggleWidgets.apk ToggleWidgets.rem; mv VisualizationWallpapers.apk VisualizationWallpapers.rem; mv UniversalInbox.apk UniversalInbox.rem; mv WeatherWidget.apk WeatherWidget.rem; mv WorkContacts.apk WorkContacts.rem
EDIT: NaeNee experienced a problem with the messaging app just closing (no FC or errors) after this... Update: This is caused by deleting or renaming BlurEmailEngine.apk, so it is no longer removed/renamed in the command above.
In case you want to undo the above rename:
Code:
mv AdService.rem AdService.apk; mv ArcPhotoworkshop.rem ArcPhotoworkshop.apk; mv ArcVideoEditorLite.rem ArcVideoEditorLite.apk; mv BlurEmail.rem Bluremail.apk; mv revolver_2_0_0012_embed_Signed_2010-04-13_11-07-08.rem revolver_2_0_0012_embed_Signed_2010-04-13_11-07-08.apk; mv BlurSNMessagingEngine.rem BlurSNMessagingEngine.apk; mv FBAndroid-1.3.2.rem FBAndroid-1.3.2.apk; mv Kindle-1.0.2-OEM-SingleSign.rem Kindle-1.0.2-OEM-SingleSign.apk; mv MySpace.rem MySpace.apk; mv StickyNoteWidget.rem StickyNoteWidget.apk; mv SocialMessaging.rem SocialMessaging.apk; mv Swype.rem Swype.apk; mv BlurUpdater.rem BlurUpdater.apk; mv CarDock.rem CarDock.apk; mv ContactsUnconnected.rem ContactsUnconnected.apk; mv amazonmp3_1.8.19_signed_zipaligned.rem amazonmp3_1.8.19_signed_zipaligned.apk; mv esmusica_2_0_0012_embed_Signed_2010-04-13_11-05-17.rem esmusica_2_0_0012_embed_Signed_2010-04-13_11-05-17.apk; mv Fota.rem Fota.apk; mv FriendFeed.rem FriendFeed.apk; mv HelpCenter.rem HelpCenter.apk; mv hiphopofficial_2_0_0012_embed_Signed_2010-04-13_11-08-31.rem hiphopofficial_2_0_0012_embed_Signed_2010-04-13_11-08-31.apk; mv truecountry_2_0_0012_embed_Signed_2010-04-13_11-06-12.rem truecountry_2_0_0012_embed_Signed_2010-04-13_11-06-12.apk; mv KPT.rem KPT.apk; mv HomeSyncWizard.rem HomeSyncWizard.apk; mv LiveWallpapers.rem LiveWallpapers.apk; mv LiveWallpapersPicker.rem LiveWallpapersPicker.apk; mv MagicSmokeWallpapers.rem MagicSmokeWallpapers.apk; mv MessagesWidget.rem MessagesWidget.apk; mv NewsWidget.rem NewsWidget.apk; mv Protips.rem Protips.apk; mv QuickContactWidget.rem QuickContactWidget.apk; mv Quickoffice_BasicViewer_2.0.42.rem Quickoffice_BasicViewer_2.0.42.apk; mv Quickoffice_BasicViewer_2.0.52.rem Quickoffice_BasicViewer_2.0.52.apk; mv revolver_2_0_0012_embed_Signed_2010-04-13_11-07-08.rem revolver_2_0_0012_embed_Signed_2010-04-13_11-07-08.apk; mv SocialMessaging.rem SocialMessaging.apk; mv StatusWidget.rem StatusWidget.apk; mv Stk.rem Stk.apk; mv ToggleWidgets.rem ToggleWidgets.apk; mv VisualizationWallpapers.rem VisualizationWallpapers.apk; mv UniversalInbox.rem UniversalInbox.apk; mv WeatherWidget.rem WeatherWidget.apk; mv WorkContacts.rem WorkContacts.apkk
I've noticed that some APK's change depending on the rom, these work for the UK 2.21 rom after applying the JIT/Deodex trick. If you get any errors, please check the exact names of the apk's in your rom:
Code:
ls
It simply renames all the app's I don't want to .rem instead of .apk. Want something back? Rename from .rem to .apk, say if you miss the weather widget:
Code:
mv WeatherWidget.rem WeatherWidget.apk
Update: Pretty slick way of listing the apps in your particular rom can be found here, props to Rob-T for that!
When you're done, reboot:
Code:
reboot
7) Overclocking time!
Install Milestone Overclock from the market and fire it up. Load the module and Press the menu button, go to settings and enter "1000000" as Custom rate and "54" as custom vsel. After pressing OK, pull the slider all the way to the right, so the selected frequency shows up as "1000MHz, 52vsel (Custom)". Click Apply and tick the box for "Autoload on boot"
8) Scaling
Install SetCPU from the market and start it up. Set scaling to "Ondemand" and tick the box for "Autoload on boot" and exit the program. Now it's time to make the vsel correspond to the cpu frequency and save some power, as explained so brilliantly by Higgsy. Buy the man a beer! My setscaling.sh is here, Higgsy's excellent startup script is here. Download both to the root of your SD card. Then connect your phone to your pc and fire up ADB/MotoDev Studio. Once connected to your phone, here's what you need to do:
Code:
su
Code:
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
Code:
cp /sdcard/setscaling.sh /system/xbin/setscaling.sh
Code:
cp /sdcard/install-recovery.sh /system/etc/install-recovery.sh
Code:
chmod 755 /system/etc/install-recovery.sh
Code:
chmod 755 /system/xbin/setscaling.sh
Code:
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
Reboot your phone, and it should now be humming along nicely at 300-1000mhz, sipping only the power it needs, without being held down by Motobloat. Again, I didn't come up with any of this, I just wrapped it up
After doing all this, feel free to restore your apps and settings with Titanium backup, but ONLY user apps, don't re-install the old non-optimized system apps. Here's a few screenshots with all my stuff (including locale, pure calendar and other always-running apps) is installed, after running the above tweaks and mods:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The above is at 1ghz. The phone is nice and snappy, while still getting two days use from a single charge. Here's how 1.2ghz looks:
Happy hacking!
Nice man Someone should buy you a beer for taking the time to package all this together
Very nice try !
I started yesterday something similar but in document way (PDF guide or equivalent).
Maybe to avoid reading the long posts your linking to with fixes of issues and so on, you could maybe just detail a little bit more certain parts...
To give an example of my try with table of content and rooting part:
Table of content:
* How to Root the Defy
- Gain admin access
- Different methods for different versions of ROMs
* How to over clock the defy
- increase processor speed
* How to backup/install recovery
- allow installation of custom ROMs
- allow backup/restore of points of your Defy
* How to clean up system/apps
- uninstall not wanted apps or components
* How to add a theme
- make you phone look better
* How to deblur/deodexe your phone
- remove the installed moto blur to improve performance
* How to factory reset
- remove traces of what you have done
-understand the limits of the factory reset
All contributions are more than welcome to allow the completeness and improvement of this guide!
How to Root the Defy
All changes are done at own risk. I'm not responsible for a bricked phone. If you don't know what you do, stop reading here.
Default Root method for the Defy
This method was originally found by jboogie3 here urlOn modmobile 557910-motorola-defy-root-droid2method.html/url
let’s get started:
1. Put the phone in Debug Mode: Go to Settings > Applications > Development and check USB debugging box.
2. Extract the files from the zip below, connect the phone via USB, and copy them to the phone via ADB like this:
Code:
Code:
adb push Superuser.apk /sdcard/Superuser.apk
adb push su /sdcard/su
adb push busybox /sdcard/busybox
adb push exploit.bin /data/local/tmp/exploit.bin
3. Now we enter the phone's internal shell, also using ADB:
Code:
Code:
adb shell
4. Then we take advantage of the "fake" root exploit:
Code:
Code:
cd /data/local/tmp
chmod 0755 exploit.bin
./exploit.bin
5. Now after that last command you should be back to your normal console, not the phone one, so we need to connect to it again, and doing so we should now see that we have root permissions since the "#" symbol is displayed instead of "$".
Code:
Code:
adb shell
6. Now we mount the /system partition as writable and copy the necessary files there, and set them with the right permissions:
Code:
Code:
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/Superuser.apk /system/app/Superuser.apk
cp /sdcard/su /system/bin/su
cp /sdcard/busybox /system/bin/busybox
chmod 4755 /system/bin/su
chmod 4755 /system/bin/busybox
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
exit
7. Restart the phone and check if you have ROOT in a terminal by typing the "su" command, or by installing any other app that requires ROOT, and seeing it the SuperUser app pops up.
Rooting.zip > urlexternal url/url
Contains the fake root exploit, SuperUser version 2.3.6.1 and busybox
Alternative easy Root method
1. Download the z4root application on the market or elsewhere, install it
Apply the root / permanent root, that’s all !
Note: not working for all versions of phone, but dramatically easy to do.
Specific UK 2.51 ROM as of 29th of Dec 2010
1. Download attatched files
defy_2.21_boot_only.sbf
2.21boot.zip
defy_2.51_boot_only.sbf
2.51boot.zip
2. Flash the defy_2.21_boot_only.sbf via rsd lite then reboot in to system
Note: Power off DEFY. Then press 'Volume Up' and 'Power' together to boot to loader before you flash the SBF to your DEFY. Debug: If you RSD Lite did not recognize your DEFY, download the USB driver here:
urlmotorola docstools USB_Drivers/url
3. Open you phone's usb debug mode(settings>application>development>usb debug mode), then follow the standard process the root the Defy. When finished, your phone is rooted with superuser
4. Flash back the defy_2.51_boot_only.sbf via rsd lite.
Without links since iam newbee here.
Cheers,
Kribou
Good guide
Kribou said:
To give an example of my try...
...Without links since iam newbee here.
Cheers,
Kribou
Click to expand...
Click to collapse
That's one hell of a long example
yes sorry !
In fact you did a very nice work (that you tested a lot) and I wanted to do a bit the same with different options possible to save newbees from reading hours and hours of forums...
Cheers,
Kribou
Do you use a custom text-messaging application? After renaming some of the apks you suggest, the default text-messaging app closes after opening. Not a force-close, just a open and close without any error.
I'm putting everything back as it was until I've narrowed down the problem.
One more note:
You are suggesting users who want to follow your instructions, buy SetCPU from the market?
naenee said:
Do you use a custom text-messaging application? After renaming some of the apks you suggest, the default text-messaging app closes after opening. Not a force-close, just a open and close without any error.
I'm putting everything back as it was until I've narrowed down the problem.
Click to expand...
Click to collapse
I've had that error before, but not after applying the steps listed in the guide - running the UK 2.21 rom. No custom stuff here, so you've got me worried.
Here's the command to undo the renames:
Code:
mv AdService.rem AdService.apk; mv ArcPhotoworkshop.rem ArcPhotoworkshop.apk; mv ArcVideoEditorLite.rem ArcVideoEditorLite.apk; mv Bluremail.rem Bluremail.apk; mv revolver_2_0_0012_embed_Signed_2010-04-13_11-07-08.rem revolver_2_0_0012_embed_Signed_2010-04-13_11-07-08.apk; mv BlurSNMessagingEngine.rem BlurSNMessagingEngine.apk; mv StickyNoteWidget.rem StickyNoteWidget.apk; mv SocialMessaging.rem SocialMessaging.apk; mv Swype.rem Swype.apk mv BlurUpdater.rem BlurUpdater.apk; mv CarDock.rem CarDock.apk; mv ContactsUnconnected.rem ContactsUnconnected.apk; mv amazonmp3_1.8.19_signed_zipaligned.rem amazonmp3_1.8.19_signed_zipaligned.apk; mv esmusica_2_0_0012_embed_Signed_2010-04-13_11-05-17.rem esmusica_2_0_0012_embed_Signed_2010-04-13_11-05-17.apk; mv Fota.rem Fota.apk; mv FriendFeed.rem FriendFeed.apk; mv HelpCenter.rem HelpCenter.apk; mv hiphopofficial_2_0_0012_embed_Signed_2010-04-13_11-08-31.rem hiphopofficial_2_0_0012_embed_Signed_2010-04-13_11-08-31.apk; mv truecountry_2_0_0012_embed_Signed_2010-04-13_11-06-12.rem truecountry_2_0_0012_embed_Signed_2010-04-13_11-06-12.apk; mv KPT.rem KPT.apk; mv HomeSyncWizard.rem HomeSyncWizard.apk; mv LiveWallpapers.rem LiveWallpapers.apk; mv LiveWallpapersPicker.rem LiveWallpapersPicker.apk; mv MagicSmokeWallpapers.rem MagicSmokeWallpapers.apk; mv MessagesWidget.rem MessagesWidget.apk; mv NewsWidget.rem NewsWidget.apk; mv Protips.rem Protips.apk; mv QuickContactWidget.rem QuickContactWidget.apk; mv Quickoffice_BasicViewer_2.0.42.rem Quickoffice_BasicViewer_2.0.42.apk; mv revolver_2_0_0012_embed_Signed_2010-04-13_11-07-08.remmv SocialMessaging.rem SocialMessaging.apk; mv StatusWidget.rem StatusWidget.apk; mv Stk.rem Stk.apk; mv ToggleWidgets.rem ToggleWidgets.apk; mv TtsService.rem TtsService.apk; mv VisualizationWallpapers.rem VisualizationWallpapers.apk; mv UniversalInbox.rem UniversalInbox.apk; mv WeatherWidget.rem WeatherWidget.apk; mv WorkContacts.rem WorkContacts.apk
Edit: Just added the undo-rename command to the original guide.
I've put back the package you linked to and messaging no longer closes. I'll stick to renaming only those APKs I know exactly of what their purpose is and only when I'm sure I do not need them - mainly Amazon MP3/DLNA and a few others.
Thank you for the prompt reply
Soren, good guide mate.. Thumbs up.. Just a small point: delete one of your noughts from para 7
Sent from my MB525 using XDA App
elblackmo said:
Soren, good guide mate.. Thumbs up.. Just a small point: delete one of your noughts from para 7
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
Fixed!
Thanks for the heads up, 10 ghz might need a higher vsel...
Thinking about turning this whole thing into a rom... Maybe I should wait until the jit/deodex mod is working for the 2.34 or 2.51 releases?
I'm a bit of a newbie... so does this guide effectively hide MotoBLUR? (as well as prevent it from running to save resources..)
Looks good though. My Defy arrives in a few hours so I'll probably follow your instructions, this is my first Android phone.
Passa91 said:
I'm a bit of a newbie... so does this guide effectively hide MotoBLUR? (as well as prevent it from running to save resources..)
Looks good though. My Defy arrives in a few hours so I'll probably follow your instructions, this is my first Android phone.
Click to expand...
Click to collapse
The first step (0) will hide Motoblur, the rest of the steps will tweak and tune up the phone, making it run nice and smooth
Hi,
I see for JIT you use the Frozen Eclair package does that work with the JRDNEM_U3_2.34.1_DEBLUR Firmware? And hast it German Language?
mfG
good guy and good guide...
the|gamer said:
Hi,
I see for JIT you use the Frozen Eclair package does that work with the JRDNEM_U3_2.34.1_DEBLUR Firmware? And hast it German Language?
mfG
Click to expand...
Click to collapse
So far, the JIT/Deodex mod is only for the 2.21 firmware, but it works fine with the German/Austrian/Swiss rom. (Ich habe mein Defy aus www.getgoods.de gekauft )
The main difference between the 2.34 Central European rom and the 2.21 roms os that 2.34 has less Motobloat, but since we get rid of that in the guide, I don't think it'll make that much of a difference. As soon as the JIT/Deodex mod is available for 2.34 or 2.51, rest assured that I'll give it a try, though!
tenfar said:
good guy and good guide...
Click to expand...
Click to collapse
Thanks - I wouldn't have been possible without your great work!
Hm. Even though removing some of the apk files will free up (a fraction of the available) space on the Defy itself and while some of them not being there will decrease the amount of running services, I am wondering whether there is a real benefit.
Perhaps I should not make the comparison, but on Windows, there is something that a lot of users do - change the default state of services. However, nothing real is gained, while there is the potential to break something that users may need in the future, without realizing it at the time - being caught up in the thrill of 'tweaking'.
Amongst people who know what they're doing, it's generally accepted that the defaults are sensible nowadays and they should not be 'fixed', unless proven something is broken because of it.
I understand that many users here enjoy tinkering - I myself included, but since I prefer stability/usability to gaining a possible negligible increase in performance, especially in real-world situations compared to benchmarking, I'll stick to mainly default settings unless I can point to something and say 'That package there, it's the source of that feature not performing as well as it would do without it'.
That said, I do welcome and appreciate threads such as this, it gets people to try things out, weed out what is safe and what will break a system.
Hi,
Thanks for you Answer, you what
JIT/Deodex mod is available for 2.34
Click to expand...
Click to collapse
in Combination with Overclock mean?
That means whooopie!
Regards
Related
UPDATED 5/16/2010
I followed these steps. Originaly for the milestone android phone but it worked.
It should work with any of the 2.1 roms based of the sprint leak. I have tested and confirmed it working on.
DC v2.05
DC v2.07
DC v2.07.2
Fresh Toast v1 - v1.1 - v2.0b
EDIT:This does not currently work with the newest 2.1.1(or what you call it) rom. Might be changed eventually, ill keep it updated.
Before enabling
*Change home laucher
*Delete htc lock screen
see below if you dont no how
Jit does not work with htc sense, it will give you many problems. I suggest using Helix launcher from market (free and its what i use daily with no issues). You can also try GDE and nexus launcher, or really anything other then sense.
To change launchers go to setting>applications>manage apps>htc sense And clear defaults. Press home and choose a different launcher.
OR download "Home Switcher" from market.. Its a free app that lets you change between launchers.
JIT does not like any HTC apps.. So delete your HtcLockScreen by doing this.
Code:
adb remount
adb shell rm /system/app/HtcLockScreen.apk
Here is the htc lock screen if you want it back
View attachment HtcLockScreen.apk
JIT is in no way perfect on our htc hero's so MAKE A BACKUP before trying.
And you could very well run into TONS of problems, its just something to test out.
Though if used right, you wont have any problems. I use this daily.
THIS IS FOR JIT
Download: *View attachment vmlibs.zip*
Then follow these steps:
•Create 2 folders on your sdcard: “jit” & “dalbk”
•Extract the vmlibs.zip to the “jit” folder on your sdcard
•Using ADB pull your build.prop
Code:
adb remount
ADB pull /system/build.prop build.prop
-It will place the file in your c:/android/tools folder
-Edit this using notepad or similiar program.
•Add the following line to the end of the build.prop: dalvik.vm.execution-mode=int:jit
-Save the changes
•Push it back to your “jit” folder on the sdcard
Code:
ADB push build.prop /sdcard/jit/build.prop
This will back up your current files. So you can disable jit.
Code:
ADB shell
su
cp /system/build.prop /sdcard/dalbk/
cp /system/bin/dalvikvm /sdcard/dalbk/
cp /system/lib/libdvm.so /sdcard/dalbk/
cp /system/lib/libnativehelper.so /sdcard/dalbk/
This will enable jit on your phone.
Code:
cd /sdcard/jit/bin
cp -f dalvikvm /system/bin/
busybox chmod 755 /system/bin/dalvikvm
cd /sdcard/jit
cp -f libdvm.so /system/lib/
cp -f libnativehelper.so /system/lib/
cat build.prop >/system/build.prop
chmod 644 /system/lib/libdvm.so
chmod 644 /system/lib/libnativehelper.so
chmod 666 /system/build.prop
sync
reboot recovery
Now while in recovery, wipe dalvik cache, not everything, just dalvik. It will help from being stuck in a boot loop. After that you can reboot your phone and it will take awhile since dalvik is being rebuilt.
TO DISABLE:
This should disable JIT and return phone back to defualt
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /sdcard/dalbk/
cat build.prop >/system/build.prop
cp -f dalvikvm /system/bin
busybox chmod 755 /system/bin/dalvikvm
cp -f libdvm.so /system/lib/
cp -f libnativehelper.so /system/lib/
chmod 644 /system/lib/libdvm.so
chmod 644 /system/lib/libnativehelper.so
chmod 666 /system/build.prop
sync
reboot
Post For help if the disabling gives you any problems.. If it does you can always do back up of your rom that you should of made.
Original site http://sholes.id.au/how-to/
Jus10o said:
I followed these steps. Originaly for the milestone android phone but it worked.
It will work on htc sense but it force closes alot, you cant swipe so you have to press home and change screens that way.
I am using it on the helix launcher with no problems and its running very smooth so far.
Download:View attachment 305272
Then follow these steps:
•Create 2 folders on your sdcard: “jit” & “dalbk”
•Extract the vmlibs.zip to the “jit” folder on your sdcard
•Using ADB pull your build.prop
ADB pull /system/build.prop C:\build.prop
•Add the following line to the end of the build.prop: dalvik.vm.execution-mode=int:jit
•Save it & push it back to your “jit” folder on the sdcard
ADB push C:\build.prop /sdcard/jit/build.prop
ADB shell
$ su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock6 /system
# cp /system/build.prop /sdcard/dalbk/
# cp /system/bin/dalvikvm /sdcard/dalbk/
# cp /system/lib/libdvm.so /sdcard/dalbk/
# cp /system/lib/libnativehelper.so /sdcard/dalbk/
# cd /sdcard/jit/bin
# cp -f dalvikvm /system/bin/
# busybox chmod 755 /system/bin/dalvikvm
# cd /sdcard/jit
# cp -f libdvm.so /system/lib/
# cp -f libnativehelper.so /system/lib/
# cat build.prop >/system/build.prop
# chmod 644 /system/lib/libdvm.so
# chmod 644 /system/lib/libnativehelper.so
# chmod 666 /system/build.prop
# sync
# mount -o remount,ro /dev/mtd/mtdblock6 /system
# reboot
Original site http://sholes.id.au/how-to/
Click to expand...
Click to collapse
whats your linpack benchmark?
and how well does launcher work?
mrchu001 said:
whats your linpack benchmark?
and how well does launcher work?
Click to expand...
Click to collapse
Before jit: 2.4 mflops
Jit enabled: 3.45 mflops
And its running very smooth, havent had a single problem yet, but I it hasnt been on for that long. I post it so others can test it out.
ill post a screen shot in a sec.. posted them in main post
hmmm i might just have to try this..
let me know if you run into any problems.
mrchu001 said:
hmmm i might just have to try this..
let me know if you run into any problems.
Click to expand...
Click to collapse
The only one iv had so far is when unlocking the phone. It will do a small reboot of the phone and then it loads and goes back to working fine. When sense was my home screen it did it way more often. With the helix launcher it rarely does it.
Edit: Using the menu button to unlock the phone instead of sliding seems to not give me the issue. Or it hasnt so far that is.
hmmm.. alright.
how are apps running?
have you tried neocore?
mrchu001 said:
hmmm.. alright.
how are apps running?
have you tried neocore?
Click to expand...
Click to collapse
I just loaded almost every app i have with no problems and test a view like yellow pages(with google nav) and many others. They are all very snappy so far.
And i did benchmark pi, i posted in main post the scores.
Ill try to find neocore, i wasnt familiar with it.
If its not a problem, could you run the few benchmarks I have so I can compare them to the stock. Other then my stock scores.
hey sorry for taking so long..idk if your still on but here are my benchmarks
i'm running fresh 2.0d with darkstar theme, auto killer on strict.
Test 1: 1.858 MFLOPS
Test 2: 2.015 MFLOPS
Test 3: 1.999 MFLOPS
Test 4: 2.281 MFLOPS
Test 5: 2.07 MFLOPS
mrchu001 said:
hey sorry for taking so long..idk if your still on but here are my benchmarks
i'm running fresh 2.0d with darkstar theme, auto killer on strict.
Test 1: 1.858 MFLOPS
Test 2: 2.015 MFLOPS
Test 3: 1.999 MFLOPS
Test 4: 2.281 MFLOPS
Test 5: 2.07 MFLOPS
Click to expand...
Click to collapse
Im still on..
I got auto killer about 30mins ago and this is what im getting now..
Linpack:
1: 3.49 mflops
2: 3.45 mflops
3: 3.529 mflops
4: 3.571 mflops
5: 3.595 mflops
benchmark pi:
1. 9339
2. 9251
3. 9156
4. 9320
Jus10o said:
Im still on..
I got auto killer about 30mins ago and this is what im getting now..
Linpack:
1: 3.49 mflops
2: 3.45 mflops
3: 3.529 mflops
4: 3.571 mflops
5: 3.595 mflops
benchmark pi:
1. 9339
2. 9251
3. 9156
4. 9320
Click to expand...
Click to collapse
my neocore scores were
Test 1: 22.7 FPS
Test 2: 23.0 FPS
Test 3: 23.2 FPS
Average: 22.97
mrchu001 said:
my neocore scores were
Test 1: 22.7 FPS
Test 2: 23.0 FPS
Test 3: 23.2 FPS
Average: 22.97
Click to expand...
Click to collapse
Ok awesome..
My neoscores were anywhere from 23 to 27.5 averaged around 26 fps.
I was comparing it to flips benchmark test, but your scores make alot more sense.
anything else you want me to test before i attempt JIT?
Oh and I can also add, I figured out how to get it to run error free, with the way I personaly use my phone. Could change for others.
The lock screen is htc using Lock 2.0 I avoid htc and it runs perfectly fine.
Im going to run this rom with jit as my everyday rom and see what error i come across.
so if i use an app like lockbot pro instead of the htc lockscreen...it's pretty much error free?
mrchu001 said:
anything else you want me to test before i attempt JIT?
Click to expand...
Click to collapse
No, everything else i still have records of.
Try it, i want to see if it works as well for you.
I would try using helix (downloadable from market) or nexus launcher if you already have it. (idk if anyone got it working in v2.0)
And use the menu key to unlock phone.
The bootscreen might take awhile, but as long as it doenst freeze, its still working.
mrchu001 said:
so if i use an app like lockbot pro instead of the htc lockscreen...it's pretty much error free?
Click to expand...
Click to collapse
Yea, its the htclockscreen it doenst like. I have Lock 2.0 pro working good with it.
It will load your htc sense, but it might reboot it a couple times, from there press menu to unlock the phone then menu again to clear the default of htc sense.
well i'm running launcher as my default homescreen so i'll be okay right?
mrchu001 said:
well i'm running launcher as my default homescreen so i'll be okay right?
Click to expand...
Click to collapse
Yeah as long as its not the droid rosie launcher. All it is, is the htc sense with a different look.
The one i meant was the nexus launcher. Was common in dc 1.0
If your launcher doesnt have any htc things on it, like the clock, power control, so on then you are fine.
The helix launcher is a very clean simple home launcher and you can change the amount of screens to 7 and so on.
hey when i go to pull the build prop from /system it says its not there..
mrchu001 said:
hey when i go to pull the build prop from /system it says its not there..
Click to expand...
Click to collapse
Uh it should be, try typing
adb remount
adb pull /system/build.prop build.prop
it will put it into your c:/android/tools folder (Or your android folder path)
This is intended to be a list of useful tweaks and many other useful pieces of information.
Kernel modules:
tun.ko for android 2.1
Useful for: getting OpenVPN to work
mediafire.com/?59c1c15pfyt61d7
Tweaks:
Uninstall Swype
Useful for: freeing more RAM memory, removing it if you're not using it
How to do it:
1) root using androot
2) install android terminal emulator
3) in android terminal emulator run:
rm /system/app/Swype.apk
4) in manage applications, remove the 50-200KB app which has "input" in its name
Note: This removes Swype for good from your ROM
Development:
I'm looking for help on getting a kernel built for this device. I need to get a diff between the kernel from the released "GT-I5500 OpenSource" from Samsung and a clean unpatched samsung kernel. Any help would be appreciated.
I'd also like to port CM to GT-I5500.
update: I built a patched kernel with all the patches one applies against the sources to improve performance and stability. Flashing it failed.
i can't thank you enough... i'll try this one thanx
Edited: Oh, it's you flying_dutchman, i thought that someone else want to port cm
good man!
ive tried building the kernel from samsung but just wouldnt play nice for some reason, gonna have another stab at it tonight if i can
think i may have thought up a way to flash this in theory too...
from what i saw when i flashed froyo using odin, when your flashing "one package" files there doesnt appear to be any checks or anything. so replacing the files already in a tar could work...?
Sc0pEz said:
good man!
ive tried building the kernel from samsung but just wouldnt play nice for some reason, gonna have another stab at it tonight if i can
think i may have thought up a way to flash this in theory too...
from what i saw when i flashed froyo using odin, when your flashing "one package" files there doesnt appear to be any checks or anything. so replacing the files already in a tar could work...?
Click to expand...
Click to collapse
Not really. It still checks the signatures.
Don't flash anything you build just yet. There are quite a few unsolved issues regarding the flashing process. Once I have the full process, we can flash.
yea found that out already, tried it last night and failed, just thought about it since when loading up the package it didnt check like it does with individual firmware files
has anyone had any luck with the recovery image? make life hellish easier if we can get a custom recovery on there
Waiting for your CM Port
A little info... for unnistalling Swype.. we can use titanium backup...
Waiting the port...
Hello!
I am very glad to hear about the port.
Here's a simple tweak for the I5500. It's easy to do with adb shell but requires a rooted device. The tweak is for skipping the boot/shutdown animation, and it provides quite a speedup.
Code:
su
mount -o remount,rw /dev/mtdblock3 /system
cd system/media
mv bootani.qmg _bootani.qmg
cd video/shutdown
mv shutdown_1.png _shutdown_1.png
mv shutdown_2.png _shutdown_2.png
mv shutdown_3.png _shutdown_3.png
mv shutdown_4.png _shutdown_4.png
mv shutdown_5.png _shutdown_5.png
mv shutdown_6.png _shutdown_6.png
mv shutdown_7.png _shutdown_7.png
mv shutdown_8.png _shutdown_8.png
mv shutdown_9.png _shutdown_9.png
mv shutdown_10.png _shutdown_10.png
mv shutdown_11.png _shutdown_11.png
mv shutdown_12.png _shutdown_12.png
mv shutdown_13.png _shutdown_13.png
mv shutdown_14.png _shutdown_14.png
mv shutdown_15.png _shutdown_15.png
mv shutdown_16.png _shutdown_16.png
mv shutdown_17.png _shutdown_17.png
mv shutdown_18.png _shutdown_18.png
mv shutdown_19.png _shutdown_19.png
mv shutdown_20.png _shutdown_20.png
mv shutdown_21.png _shutdown_21.png
mv shutdown_22.png _shutdown_22.png
mv shutdown_23.png _shutdown_23.png
mv shutdown_24.png _shutdown_24.png
mv shutdown_25.png _shutdown_25.png
mv shutdown_26.png _shutdown_26.png
mv shutdown_27.png _shutdown_27.png
mv shutdown_28.png _shutdown_28.png
mv shutdown_29.png _shutdown_29.png
mv shutdown_30.png _shutdown_30.png
mv shutdown_31.png _shutdown_31.png
mv shutdown_32.png _shutdown_32.png
mv shutdown_33.png _shutdown_33.png
mv shutdown_34.png _shutdown_34.png
mv shutdown_35.png _shutdown_35.png
mv shutdown_36.png _shutdown_36.png
mv shutdown_37.png _shutdown_37.png
mv shutdown_38.png _shutdown_38.png
mv shutdown_39.png _shutdown_39.png
mv shutdown_40.png _shutdown_40.png
cd /system/etc
mv poweron.snd _poweron.snd
Edit: I also have a tweak for calibrating the accelerometer, but I'm quite lazy right now. I'll return in case anyone requests that.
Version 2.2 is out for I5500L.
I'm a beginner Java coder, and have that phone.
If i can do anything to help you, just let me know.
Any news?
Sent from my GT-I5500L using XDA App
I assume this phone doesn't have custom recovery. I am willing to port it, just need you all to follow the steps on http://www.androidtablets.net/forum.../3607-porting-clockwork-recovery-tablets.html and reply here or there.
btw, I know its not a tablet but its the same steps and I made the guide, don't feel like pasting it here and there
Also, froyo won't boot on a 2.6.29 kernel without some patches and even then cm won't boot without some extra changes in kernel...
there is no /proc/mtd directory on SG5
i think on the galaxy 5 it is /proc/stl
i may be wrong though and cant check right now as dont have my phone to hand
News?
Sent from my GT-I5500L using XDA App
Any news yet ?
I have sucefully compiled a cyanogen port for the i5500
Now i have to wait for my device to come back from the repair since i managed to erase the bios by using my recovery
I decided to avoid playing with the recovery and flashing cyanogen directly via ODIN
If any one wants to try out my compilation send me an email : motafoca at alquest.com.br
motafoca said:
I have sucefully compiled a cyanogen port for the i5500
Now i have to wait for my device to come back from the repair since i managed to erase the bios by using my recovery
I decided to avoid playing with the recovery and flashing cyanogen directly via ODIN
If any one wants to try out my compilation send me an email : motafoca at alquest.com.br
Click to expand...
Click to collapse
Before you erased your bios, did everything worked, like wifi, camera...?
I didnt manage to test it
But there some people testing it as we speak
Boogie manzor or anyone, can you share the kernel+the patches you built?
I have a way to test it
Thanks
Ok so I Overclocked/undervolted via Milestone Overclock - no problems, however it got me thinking, all we are doing with this app is changing the maximum frequency and the maximum vsel.
I was looking for some extra oomph but also wanted to maximise battery life. My current set up is a 900mhz/46vsel maximum, but what about the other available frequencies - 600/300mhz - we ain't touching the vsel on these - are we getting the most out of this??
I did a bit of delving around so firstly I found the following when performing a cat /proc/overclock/mpu_opps with my overclock in place:
mpu_opps[3] rate=900000000 opp_id=3 vsel=46
mpu_opps[2] rate=600000000 opp_id=2 vsel=48
mpu_opps[1] rate=300000000 opp_id=1 vsel=33
So this is showing that the vsel for 600mhz is actually higher than 900mhz - not very economical! so how can we change this, well delving around various forums i got the jist of how to change this so here's a tutorial
IMPORTANT READ THIS!!! Disclaimer: I will not be held responsible for any damage to your phone, your PC or indeed your life from following this guide. The steps in this guide worked for me. Doing this kind of thing could affect your warranty and all that so have a long hard think about it before you go ahead. If anything goes wrong and your phone freezes or reboots spontaneously, remove the sdcard and boot the phone which will disable the overclock module and enable you to reverse whatever you did! As always I would always recommend a backup using Clockworkmod recovery. This is hacking and bad things can happen so be prepared. This is only tested on a stock/rooted 2.21 UK Generic/2.34 Deblur ROM with no apps removed - I have no idea if this works on other ROMs like JBoogie's (stock roms should be ok), because I don't know what changes/tweaks the Dev has done - If you try it and find it does/doesn't work then report back, but I can't offer any support for that
1) Create a setscaling.sh (I have attached mine as a base) script, this is what mine looks like. You can change frequencies/vsels, but it MUST stay in the format below.
echo 46 > /proc/overclock/max_vsel
echo 900000 > /proc/overclock/max_rate
echo 1 300000000 28 > /proc/overclock/mpu_opps
echo 2 600000000 38 > /proc/overclock/mpu_opps
echo 3 900000000 46 > /proc/overclock/mpu_opps
echo 0 900000 > /proc/overclock/freq_table
echo 1 600000 > /proc/overclock/freq_table
echo 2 300000 > /proc/overclock/freq_table
Lines 1/2 are your custom vsel/freq as loaded into Milestone Overclock
Lines 3/4/5 are your freq's and the custom vsels you want to use at those freq's (you can see they are much less than what they were originally!)
Lines 6/7/8 are your frequency table
I can't stress enough you must keep the format the same, and make sure you use the corect number of. It is possible to for example add an extra step/Frequency in - I haven't tested this so just be careful. Also bear in mind if you lower the vsels too much then you will cause the phone to fall over. However if you do get this just pull the SD card an it will boot the phone with the overclock module disabled
when you have set your setscaling.sh up you then need to do the following.
copy it to your sdcard, then via adb (you can also use root explorer)
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/setscaling.sh /system/xbin/setscaling.sh
chmod 755 /system/xbin/setscaling.sh
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
Then to after this to execute via adb you can just type:
setscaling.sh
Seriously though guys get root explorer as that will enable you to edit you setscaling.sh on the fly as you do your testing (finding optimum vsel), once edited you can then execute it by simply clicking on the file.
Once you have got your setscaling.sh just the way you want it, you can then get it to initialise automatically after boot - this had me stumpted for a while as the script was executing before the overclock module had loaded hence the settings weren't taking effect and I was having to start it manually. I'm more windows orientated and this actually turned out to be a really easy fix.
the key is another script called install-recovery.sh (again I have attached this to the post) and it contains the following info
#!/system/bin/sh
sleep 80
setscaling.sh
So what this does is it waits 80 secs before executing setscaling.sh - which gives the system more than enough time to boot up and load the overclock module. Intall this as per below after plaing on sdcard:
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/install-recovery.sh /system/etc/install-recovery.sh
chmod 755 /system/etc/install-recovery.sh
reboot
Once rebooted do a cat /proc/overclock/mpu_opps and check your setscaling.sh has applied ok (i.e it is displaying your custom vsels)
Jobs a good un - enjoy!
##If you are reporting problems with it not working please post the exact steps of what you have done, otherwise I won't be able to assist##
Reserved...............
I've searched for an hour how to use Motorola Overclock. I've put the kernelmodule.tar.gz on the sdcard...
But i don't understand how to load it. Or where to place it...
The wiki on the googlecode page leaves me without a clue.
vanloque said:
I've searched for an hour how to use Motorola Overclock. I've put the kernelmodule.tar.gz on the sdcard...
But i don't understand how to load it. Or where to place it...
The wiki on the googlecode page leaves me without a clue.
Click to expand...
Click to collapse
mate just download milestone overclock from the market!
Higgsy said:
mate just download milestone overclock from the market!
Click to expand...
Click to collapse
That's what i did... And then i can't do anything in the app...
Oh Hey, i did forget to Re-Root after FrozenEclairing!
vanloque said:
That's what i did... And then i can't do anything in the app...
Click to expand...
Click to collapse
Do you have root?
after you apply this how do you tell if its worked?
edit: wow im retarded ignore this post -.-
A one right here
thanks, needed this for my overclock
I use gscript lite, and this info is perfet A 1
thanks for the idea and this should work with just adb; no need to download the scripts...
Code:
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
echo "#!/system/bin/sh
echo 46 > /proc/overclock/max_vsel
echo 900000 > /proc/overclock/max_rate
echo 1 300000000 28 > /proc/overclock/mpu_opps
echo 2 600000000 38 > /proc/overclock/mpu_opps
echo 3 900000000 46 > /proc/overclock/mpu_opps
echo 0 900000 > /proc/overclock/freq_table
echo 1 600000 > /proc/overclock/freq_table
echo 2 300000 > /proc/overclock/freq_table" > /system/xbin/setscaling.sh
chmod 755 /system/xbin/setscaling.sh
setscaling.sh
echo "#!/system/bin/sh
sleep 80
/system/xbin/setscaling.sh" > /system/etc/install-recovery.sh
chmod 755 /system/etc/install-recovery.sh
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
really glad others are using this and liking it, everyone who is using milestone overclock should be using it!
Hey Higgsy,
i installed your scripts through Root Explorer (incl. executing + rebooting), but checking the mpu_opps file still gives me standard frequencies. You got an idea for this?
Greets, Jack
basshamster said:
Hey Higgsy,
i installed your scripts through Root Explorer (incl. executing + rebooting), but checking the mpu_opps file still gives me standard frequencies. You got an idea for this?
Greets, Jack
Click to expand...
Click to collapse
is the milestone overlock installed and module loaded?
Custom setting in milestone overclock set to 900mhz/46vsel?
Did you set the permissions? (ie the chmod bit).
- Milestone Overclock installed and loaded (incl. startup-load)
- i use different settings 1000/50 (300/30, 600/40 -> in setscaling-script), but 1000/50 is also set in custom settings so it seems equal to me
- permissions of both scripts are "rwxr-xr-x"
hmmm....
little edit: mpu_opps gives me 300/33, 600/48, 1000/50 so it#s not completely standard
basshamster said:
- Milestone Overclock installed and loaded (incl. startup-load)
- i use different settings 1000/50 (300/30, 600/40 -> in setscaling-script), but 1000/50 is also set in custom settings so it seems equal to me
- permissions of both scripts are "rwxr-xr-x"
hmmm....
little edit: mpu_opps gives me 300/33, 600/48, 1000/50 so it#s not completely standard
Click to expand...
Click to collapse
yeah it is standard apart from the max overclock you set in Milestone Overclock.
Please attach your exact setscaling.sh so I can take a look at it.
Thx for helping!
basshamster said:
Thx for helping!
Click to expand...
Click to collapse
hmm looked ok on the face of it, however when I recreated the file it was 355bytes as opposed to yours that was 353bytes
anyway, i think I might know the problem, in root explorer, open setscaling.sh in text editor - look at the end of each line - is there a little box? If there is the delete them - save and then execute.
Your permissions were ok
This is working ok on my phone now
Unfortunately still not working ... don't know what's the problem. Maybe someone else joins us with another solution. Thx for your help anyway!
I posted on the google forum bugreport.
When i click LOAD that reboots the phone and when i relaunch the app the clocks are still empty, so i click load again and it reboots again... Etc.
I just rooted the A2, lets say something breaks on the phone and I have to take it back to AT&T. How can you unroot? Not that I will but just in case.
They really cannot tell if the phone is rooted. It's when the device has Bootloader unlocked that they can notice easier. Although I have taken back two OG Atrixes with bootloaders unlocked and Just returned an Atrix 2 Rooted with No issues from anyone. Although I would like to know regardless anyway as I am having issues with my root at the moment.
Not sure, but if you find out let us know.
Its also so I can receive over the air updates down the road.
OTA updates weren't affected by root on my backflip and actually the update unrooted the phone. Idt theres anything to worry about there.
1) all you really need to do is remove the SU apk from the /system/app folder and thats it. (i have not rooted this phone yet, myself. but thats all you should have to do)
2) rooting should not affect OTA updates BUT it I think it depends on the root method. If rooting requires you to flash a new kernel (like on the SGS2), it may break OTA updates. There's no definitive answer to that question.
Thank you for the answers. Just wanna stay up to date on software without having to manually do everything.
Sent from my MB865 using xda premium
To completely un-root, one would need to do the following:
adb shell
su
cd /system/xbin
mkdir tmp
mv * tmp
cd tmp
mv ssmgrd ../
mv run_restore ../
mv run_backup ../
mv backup ../
mv dexdump ../
mv drm1_func_test ../
cd ..
rm -rf tmp
cd /
rm /system/bin/busybox
rm /system/app/Superuser.apk
rm /data/local/tmp/*
rm /data/local/zerg
rm /data/local/su
rm /data/local/Superuser.apk
rm /system/xbin/su
exit
adb reboot
If you then wipe data / factory reset, PROVIDED you followed the root thread in the dev forum and haven't messed with anything else, you will be back to a bone stock device.
Now works on non-DE phones too.
Installation instructions, with ro.boot.write_protect=0:
Code:
adb push VzwEntitlementService.apk /sdcard/VzwEntitlementService.apk
adb shell
su
mount -o remount,rw /system
mv /system/priv-app/VzwEntitlementService.apk /system/priv-app/VzwEntitlementService.apk.bak
mv /system/priv-app/VzwEntitlementService.odex /system/priv-app/VzwEntitlementService.odex.bak
cp /sdcard/VzwEntitlementService.apk /system/app/VzwEntitlementService.apk
chmod 644 /system/app/VzwEntitlementService.apk
Now tap "Portable Wi-Fi hotspot". You will experience a force close, this is expected.
Code:
mv /system/app/VzwEntitlementService.apk /system/priv-app/VzwEntitlementService.apk
mount -o remount,ro /system
exit
exit
Now you will be able to tether.
For the geeks:
Code:
.method public startEntitleCheck()V
.locals 2
.prologue
const/4 v0, 0x1
iput-boolean v0, p0, Lcom/motorola/service/vzw/entitlement/EntitlementDialogActivity;->mEntitlementCheckState:Z
const-string v1, "1"
iput-object v1, p0, Lcom/motorola/service/vzw/entitlement/EntitlementDialogActivity;->mStatusCode:Ljava/lang/String;
return-void
.end method
cj64 said:
Installation instructions:
Code:
adb push VzwEntitlementService.apk /sdcard/VzwEntitlementService.apk
adb shell
su
mount -o remount,rw /system
mv /system/app/VzwEntitlementService.apk /system/app/VzwEntitlementService.apk.bak
mv /system/app/VzwEntitlementService.odex /system/app/VzwEntitlementService.odex.bak
cp /sdcard/VzwEntitlementService.apk /system/app/VzwEntitlementService.apk
chmod 644 /system/app/VzwEntitlementService.apk
Now tap "Portable Wi-Fi hotspot". You will experience a force close, this is expected.
Code:
mv /system/app/VzwEntitlementService.apk /system/priv-app/VzwEntitlementService.apk
mount -o remount,ro /system
exit
exit
Now you will be able to tether.
Click to expand...
Click to collapse
Hi there! I'm definitely not in the "geek" category. But, I'm extremely interested in this. I'm curious, are all of the above items individual adb commands. Do each? (I've not done anything with ADB since Droid X days and then just followed very precise directions).
Any possibility this could be put into some kind of flashable zip (through recovery)...that might have scripts that take care of the "grunt" work?
If I only had the time and knowledge to get further into these things, I wouldn't even make the suggestion.
Still yet, GREATLY APPRECIATED!!
cj64 said:
Installation instructions:
Code:
adb push VzwEntitlementService.apk /sdcard/VzwEntitlementService.apk
adb shell
su
mount -o remount,rw /system
mv /system/app/VzwEntitlementService.apk /system/app/VzwEntitlementService.apk.bak
mv /system/app/VzwEntitlementService.odex /system/app/VzwEntitlementService.odex.bak
cp /sdcard/VzwEntitlementService.apk /system/app/VzwEntitlementService.apk
chmod 644 /system/app/VzwEntitlementService.apk
Now tap "Portable Wi-Fi hotspot". You will experience a force close, this is expected.
Code:
mv /system/app/VzwEntitlementService.apk /system/priv-app/VzwEntitlementService.apk
mount -o remount,ro /system
exit
exit
Now you will be able to tether.
Click to expand...
Click to collapse
Thx, works great for me!
cj64 said:
Installation instructions:
Code:
...
[STRIKE]mv /system/app/VzwEntitlementService.apk /system/app/VzwEntitlementService.apk.bak
mv /system/app/VzwEntitlementService.odex /system/app/VzwEntitlementService.odex.bak[/STRIKE]
mv /system/priv-app/VzwEntitlementService.apk /system/priv-app/VzwEntitlementService.apk.bak
mv /system/priv-app/VzwEntitlementService.odex /system/priv-app/VzwEntitlementService.odex.bak
...
Click to expand...
Click to collapse
Made a correction to the paths in the installation instructions.
will this work on non DE vz moto x after 4.4 root is achieved?
Yes.
cj64 said:
Yes.
Click to expand...
Click to collapse
VERY cool, thank you
cj64 said:
Installation instructions:
Code:
adb push VzwEntitlementService.apk /sdcard/VzwEntitlementService.apk
adb shell
su
mount -o remount,rw /system
mv /system/priv-app/VzwEntitlementService.apk /system/priv-app/VzwEntitlementService.apk.bak
mv /system/priv-app/VzwEntitlementService.odex /system/priv-app/VzwEntitlementService.odex.bak
cp /sdcard/VzwEntitlementService.apk /system/app/VzwEntitlementService.apk
chmod 644 /system/app/VzwEntitlementService.apk
Now tap "Portable Wi-Fi hotspot". You will experience a force close, this is expected.
Code:
mv /system/app/VzwEntitlementService.apk /system/priv-app/VzwEntitlementService.apk
mount -o remount,ro /system
exit
exit
Now you will be able to tether.
Click to expand...
Click to collapse
What does that chmod 644 do? Is this required to be done on the system or could you use root explorer to put the .zip file into the priv-app file on they system.
TheDonXR said:
What does that chmod 644 do? Is this required to be done on the system or could you use root explorer to put the .zip file into the priv-app file on they system.
Click to expand...
Click to collapse
Sets the permissions to be the same as the original entitlement files.
http://www.draac.com/chmodchart.html
Do the equivalent with root explorer if that is what you are going to use.
cj64 said:
Yes.
Click to expand...
Click to collapse
Assuming you can get writable /system, which isn't a sure thing. Didn't the first 4.2.2 root not achieve that and you still had to boot into a faux recovery to write to /system in any sticky way?
SQFreak said:
Didn't the first 4.2.2 root not achieve that and you still had to boot into a faux recovery to write to /system in any sticky way?
Click to expand...
Click to collapse
Yes. The same technique works on 4.4.
this worked great. Thanks!
Hi there! Any way this can be made into a flashable zip through TWRP? I've not had much luck lately with ADB, etc. I am sitting on 4.4 DE, unlocked, rooted, with the new TWRP. I was hoping to do this all on the phone if it were possible and not too difficult.
And, just so you know, I am always extremely appreciated for all the mods and development on these devices. You guys who have learned these skills just rock! (getting older here with less time on my hands to always dig in and figure it out on my own, unfortunately)
I'm travelling in 2 wks and just want to make sure my Moto X is up and fully functional (as was my gNex).
Thanks!
Dburgessme2 said:
Hi there! Any way this can be made into a flashable zip through TWRP? I've not had much luck lately with ADB, etc. I am sitting on 4.4 DE, unlocked, rooted, with the new TWRP. I was hoping to do this all on the phone if it were possible and not too difficult.
And, just so you know, I am always extremely appreciated for all the mods and development on these devices. You guys who have learned these skills just rock! (getting older here with less time on my hands to always dig in and figure it out on my own, unfortunately)
I'm travelling in 2 wks and just want to make sure my Moto X is up and fully functional (as was my gNex).
Thanks!
Click to expand...
Click to collapse
I did most of the work on my phone using root explorer, I didn't know how to set the permissions when I did it and used ADB for that. I found out later how to do that and here's what the process should be without using ADB:
1. Download Root Explorer by Jrummy in the Play store.
2. Download VZWEntitlementServices.apk from OP on your moto x.
3. Go into Root Explorer and find System folder, find priv-app, inside priv-app long press VZWEntitlementServices.apk and VZWEntitlementServices.odex rename to VZWEntitlementServices.apk.bak and VZWEntitlementServices.odex.bak and back out to first folder.
4. Go to sdcard folder, download and find VZWEntitlementServices.apk that you downloaded from step 2 copy it and back out to the home folder enter the system folder and paste it.
5. Long press on the file and hit permissions in the menu. change permissions to look like screenshot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(should show rw-r--r--)
6. Exit out of root explorer and try to enable your tether it will FC.
7. Go back to root explorer and move the VZWEntitlementServices.apk that you put in the system folder to the priv-app folder.
8. Check the tether it should work.
9. PROFIT!
Let me know if it works!
I will definitely give that a shot in the next day or so. Thanks!
This is great, thanks so much!
I noticed that unlike the native tether solution for 4.2.2 this one still shows the "Checking subscription status" toast notification when activating tether - does this mean that Verizon is being notified everytime I am activating tether even though the check is ultimately being bypassed? Even if not I'd prefer not to see this.
TheDonXR said:
I did most of the work on my phone using root explorer, I didn't know how to set the permissions when I did it and used ADB for that. I found out later how to do that and here's what the process should be without using ADB:
1. Download Root Explorer by Jrummy in the Play store.
2. Download VZWEntitlementServices.zip from OP on your moto x.
3. Go into Root Explorer and find System folder, find priv-app, inside priv-app long press VZWEntitlementServices.zip and VZWEntitlementServices.odex rename to VZWEntitlementServices.zip.bak and VZWEntitlementServices.odex.bak and back out to first folder.
4. Go to sdcard folder, download and find VZWEntitlementServices.zip that you downloaded from step 2 copy it and back out to the home folder enter the system folder and paste it.
5. Long press on the file and hit permissions in the menu. change permissions to look like screenshot.
(should show rw-r--r--)
6. Exit out of root explorer and try to enable your tether it will FC.
7. Go back to root explorer and move the VZWEntitlementServices.zip that you put in the system folder to the priv-app folder.
8. Check the tether it should work.
9. PROFIT!
Let me know if it works!
Click to expand...
Click to collapse
Well, this is just awesome! Evidently it worked. I'm making this post with my Nexus 7 tethered to my DE 4.4 Moto X on my unlimited data plan.
Sent from my Nexus 7 using Tapatalk 4
did it on my non DE and it works lovely. goodjob
publicanimal said:
does this mean that Verizon is being notified everytime I am activating tether even though the check is ultimately being bypassed?
Click to expand...
Click to collapse
No, it's just cosmetic. There is a useful internet connection check which was left alone.