Database Info

[Guide]How I tweak, mod and hack my Defy

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

[HOW TO] Flash FROYO properly with everything working

As there seems to be a bit of confusion about Froyo, maybe this quick step by step guide will help. I can't guarantee it will work on your Defy and I'm not responsible for bricked devices.
IMPORTANT: If your flash doesn't work before flashing this rom, you need to flash UK 2.21 ROM via RSD lite, wipe data and cache (VOL Down + Power Boot; click right corner) and do a factory reset (settings-> privacy). Now your flash should work and you can precced with this guide. Don't install any other cam apps as they may brick your flash.
Video of Quadrant benchmark:
http://www.youtube.com/watch?v=lIHFivjrM7w
Video of Market and Flashlight working:
http://www.youtube.com/watch?v=viyxqVLtZE4
Advantages of this guide:
+stable and fast Froyo with ROOT ([email protected])
+Camera works (no fix needed)
+Wifi works (no fix needed)
+Market works (no fix needed)
+Recovery works
+Everything deodexed
+Bloatware removed (optional)
+Black Notification Bar (optional)
Disadvantages:
-Not for Defys with 2.51
-Only 2 languages
-All your apps and settings will be gone
-You need to manually add your APN
-Guide not for beginners
UPDATE 19.Jan.2011
-It may cause problems to install google apps AFTER rooting. Guide updated.
-Minor update on point 8. Make sure "USB Connection" is set to "None".
-Added point 13 for people who suffer from the Flash bug.
UPDATE 20.Jan.2011
-Added point 14: miscellaneous tweaks.
UPDATE 21.Jan.2011
-Updated point 8 and 13.
-Fixed search_fix from point 9.
UPDATE 22.Jan.2011
-Added info about baseband switcher app to point 14.
UPDATE 22.Jan.2011
-Updated point 7 and 13
UPDATE 30.Jan.2011
-Updated point 12 with theme files for UK Froyo
1)
First Backup using Tenfar's recovery!!
2)
Download the official 2.2 ROM. Here is a mirror from Sorensiim(Thanks!)
3)
Turn on your Defy by holding VOL-UP + POWER, connect it to your PC and flash the ROM using RSD lite 4.9
4)
After flashing, turn your defy off and turn it on again by holding VOL-DOWN + POWER. When you've reached the screen with the exclamation mark, press the bottom right corner of your screen. WIPE everything.
5)
Boot into Froyo. When you've reached the red screen, click on the Chinese text in the center and choose ENGLISH. Press the menu button, click at the bottom right and skip creating a Motoblur account. Froyo might still feel slow. This is normal.
6)
Download google apps update.zip and save it on the root of your sdcard.
Start your phone holding VOL-DOWN + POWER. Press the bottom right corner of your screen again. Flash the update.zip on your sdcard and wipe everything again (this was the last time).
7)
Reboot. Turn usb debugging on. Set USB Mode to Moto Phone Portal.
Download SuperOneClickFor2.1.zip from this thread and root your device.
8)
Reboot. Download HIGGS's deodexed files from this thread. Extract system to the root of your sdcard. Make sure "USB Connection" is set to "None".
enter the following adb commands:
Code:
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/system/app/* /system/app/
cp /sdcard/system/framework/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
Note: after typing "su" for the first time, on your phone the app "Superuser" should pop up with a notification asking for root permissions. It's important to allow this.
9)
Optional: At this point "google search" was FCing. To fix it download the search_fix.zip attachement, extract it to the root of your sdcard and use adb:
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cp /sdcard/QuickSearchBox.apk /system/app/QuickSearchBox.apk
reboot
10)
Now everything should be working. Switch to the other keyboard (or install a new one). I recommend to uninstall Bloatware. Make sure to install a new Launcher before uninstalling "BlurHome.apk"! I uninstalled the following apps using adb:
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
rm /system/app/AdService.apk
rm /system/app/Alipay.apk
rm /system/app/ArcPhotoworkshop.apk
rm /system/app/ArcVideoEditorLite.apk
rm /system/app/AudioEffectSettings.apk
rm /system/app/BatteryManager.apk
rm /system/app/BingClient.apk
rm /system/app/BlurEmail.apk
rm /system/app/BlurHome.apk
rm /system/app/Dianping.apk
rm /system/app/DLNA.apk
rm /system/app/Dock.apk
rm /system/app/EventReminder.apk
rm /system/app/FileManager.apk
rm /system/app/Firewall.apk
rm /system/app/FMRadio.apk
rm /system/app/FMRadioService.apk
rm /system/app/Gobang.apk
rm /system/app/HomeSyncWizard.apk
rm /system/app/Landlord.apk
rm /system/app/MagicSmokeWallpapers.apk
rm /system/app/Mobee.apk
rm /system/app/MotoImeTutorial.apk
rm /system/app/MotoPhonePortal.apk
rm /system/app/MotoSmartHandWriting.apk
rm /system/app/MSExchangeService.apk
rm /system/app/Mynet.apk
rm /system/app/Palmebook.apk
rm /system/app/PerformanceManager.apk
rm /system/app/PhotoWidget.apk
rm /system/app/PicoTts.apk
rm /system/app/PimBackup.apk
rm /system/app/Pinyin.apk
rm /system/app/Protips.apk
rm /system/app/QQ.apk
rm /system/app/QuickContactWidget.apk
rm /system/app/QuickOffice.apk
rm /system/app/Shop4Apps.apk
rm /system/app/SimContactAdapter.apk
rm /system/app/SinaWeatherWidget.apk
rm /system/app/SinaWeibo.apk
rm /system/app/SocialShare.apk
rm /system/app/SpellingCheckService.apk
rm /system/app/StatusWidget.apk
rm /system/app/StickyNoteWidget.apk
rm /system/app/Stk.apk
rm /system/app/StraightFlush.apk
rm /system/app/Sudoku.apk
rm /system/app/Tilemaze.apk
rm /system/app/ToggleWidgets.apk
rm /system/app/VisualizationWallpapers.apk
rm /system/app/WindowsLiveClient.apk
rm /system/app/WorldClockWidget.apk
rm /system/app/WorkContacts.apk
rm /system/app/YoudaoDict.apk
rm /system/app/YoukuHD.apk
exit
11)
Optionally install Tenfar's recovery, choose "Install Recovery System", give it root access and finally boot into recovery. REMEMBER to deactivate usb debugging before booting into recovery or it won't work!
12)
Optional: Black Notification Bar. Download froyo_theme_files.zip and extract it to the root of your sdcard. For UK Froyo you need other files!!
adb:
Code:
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/framework-res.apk /system/framework/framework-res.apk
cp /sdcard/services.jar /system/framework/services.jar
reboot
13)
Optional: If your cam flash shouldn't work, try wiping camera data using titanium backup. If this still doesn't help. Install 2.21 UK via RSD Lite, wipe everything and do a factory reset (in settings -> privacy). Your flash should work again.
14)
Minor tweaks:
-To remove the Chinese text in your call history, go to Settings > Call Settings > Number Attribution Settings and deselect "Location"
-Install "autokiller" (it's NOT a task killer) from the market and set it to "ultimate" (as the Defy has plenty of RAM). Once you've done this, no need to ever open the app again (make sure "autokiller" is set to "apply at boot" though). For me this improves performance and battery life.
-If you should have problems with 2G or 3G, this app might help: ItfunzBaseBandSwitcher.apk
You need root. For T-Mobile usa:美版基带 For EU: 欧版基带 Click and reboot your phone.

Thanks for this useful guide.
Does the flash camera work "properly" following this method?

A question, is this guide for US or European users? Does 3G and stuff like that work in Europe?

ellendel said:
Thanks for this useful guide.
Does the flash camera work "properly" following this method?
Click to expand...
Click to collapse
Yes it works properly for both camera and camcorder.
pomah said:
A question, is this guide for US or European users? Does 3G and stuff like that work in Europe?
Click to expand...
Click to collapse
For European. I'm not sure about US and 3G.

Great i'll follow your guide. Thx again

one question
First, thanks for all the work doing this guide.
i have a problem when trying to apply update.zip from Tenfar's recovery, i get this error:
installing update...
assert failed: getprop("ro.product.model") == "ME525" && getprop("ro.build.version.sdk") == "8" E:Error in /sdcard/update.zip
(Status 7)
Installation aborted
i check twice the update.zip file, but always do the same, i downloaded twice and checked twice without errors...
what i'm doing wrong?
thanks in advance

koto2 said:
i have a problem when trying to apply update.zip from Tenfar's recovery, i get this error:
installing update...
assert failed: getprop("ro.product.model") == "ME525" && getprop("ro.build.version.sdk") == "8" E:Error in /sdcard/update.zip
(Status 7)
Installation aborted
Click to expand...
Click to collapse
I updated the guide (Point 6). Try point 6 before rooting. It should work.

And what do you do to fix the flash? The only difference between this and when I flash is the deodexed files... And my flash don't work.
Thanks!

tensan said:
And what do you do to fix the flash? The only difference between this and when I flash is the deodexed files... And my flash don't work.
Thanks!
Click to expand...
Click to collapse
Camera flash works with or without deodexed files. No fixes needed.
Did you flash this unrooted ROM from here? Other roms might not work properly.
Did you also wipe everything after flashing? This is important.

shamo42 said:
Camera flash works with or without deodexed files. No fixes needed.
Did you flash this unrooted ROM from here? Other roms might not work properly.
Did you also wipe everything after flashing? This is important.
Click to expand...
Click to collapse
Yes, both. I wipe and my flash works sometimes only. Have you tested the flash for many times?
Thanks!!

tensan said:
Yes, both. I wipe and my flash works sometimes only. Have you tested the flash for many times?
Thanks!!
Click to expand...
Click to collapse
I just tested it 10 times in a row. No problems.
edit:
Here is a video that shows flash working without problems:
http://www.youtube.com/watch?v=viyxqVLtZE4

quadrant score?

Kovyrshin said:
quadrant score?
Click to expand...
Click to collapse
~1250 @800Mhz
~1600 @1200Mhz:
{
"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"
}

Maybe my problem was that I install google apps after I root the.phone. I will try to do before.
Thanks a lot
Sent from my MB525 using XDA App

shamo42 said:
~1250 @800Mhz
~1600 @1200Mhz:
Click to expand...
Click to collapse
nice stats... gonna give it a try this weekend, if i wont drive away snowboarding.

shamo42 said:
...
Advantages of this guide:
...
+Wifi works (no fix needed)
+Market works (no fix needed)
...
Click to expand...
Click to collapse
Hi!
I follow all the great guide and works really fine, but I found a little bug. When I turn on the Wifi connection after 5mins of inactivity (or 10m) my motorola Defy doesn't reconnect by itself. I must disconnect, forget the password and re-type the password.
Anyone can test it, so I don't know if it's my problem or a real bug of this image.
Thanks!

I followed the guide, everything works well, except the camera. There's still the camera flash bug, works only for the first time.

After i unzip the deodexed system folder in the sdcard root, then i try to follow the adb commands posted in the guide, but when i type in the shell
"cp /sdcard/system/app/* /system/app/" it says "no such file or directory.
Any suggestion?

ellendel said:
After i unzip the deodexed system folder in the sdcard root, then i try to follow the adb commands posted in the guide, but when i type in the shell
"cp /sdcard/system/app/* /system/app/" it says "no such file or directory.
Any suggestion?
Click to expand...
Click to collapse
Sure, and it's easy I had the same issue!
Swift the notification bar, Press the Option "USB Connection" and select "None".
Tell me what about.

Muznyu said:
I followed the guide, everything works well, except the camera. There's still the camera flash bug, works only for the first time.
Click to expand...
Click to collapse
Yes, I have the same problem! :S maybe we can fix it with the patch of other thread? :S Shamo, did you apply this patch? :S

[Q] Please help translate some adb instructions into terminal emulator commands

Hi
I have Huawei u8150, Android 2.2, Rooted with z4root.
I want to give widgetsoid access to toggle data using the android apn toggle.
The instructions are:
____
Just put the Widgetsoid apk on /system/app folder
Work only with ADB connected to the phone (doesn't work if you use root explorer or other apps like this) :
* Remount /system as read/write
* adb push Widgetsoid.apk /system/app/Widgetsoid.apk
* Remount /system as read-only
_____
Can someone tell me what I can type in terminal emulator window to achieve this. I can't use adb as it won't recognise my u8150 (It worked fine with my i9000)
Thanks
Kiwi
Widgetsoid website - http://jaumard.android.free.fr/widgetsoid/help_widgetsoid.php?lang=en_EN
PS: Apologies if the wrong forum, but there were only 4 specific android forums, so i thought the general forum would be the best to post this type of question in.

http://android-tricks.blogspot.com/2009/01/mount-filesystem-read-write.html
http://www.reallylinux.com/docs/files.shtml

Thanks
I had tried
$ su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# CHMOD 777 /SYSTEM
the above works but if i try to push i get
# push
push: not found
I also tried the above then switched over to es-file explorer and was able to copy + pasted the widgetsoid.apk file from my sdcard into the /system/app directory. It correctly pasted the file, but when I clicked on widgetsoid.apk to install the apk i got an error.
"Parse Error: There is a problem parsing the package."

I wouldn't chmod /system ... just leave the permissions the same.
cp /sdcard/downloads/widgetsoid.apk /system/app/
Chmod 644 /system/app/widgetsoid.apk
No need to click install or anything like that... just reboot after copying it to /system/app.
Sent from my Droid using Tapatalk

push is an adb command. You'll want to put the apk on the sdcard then use:
cp /sdcard/Widgetsoid.apk /system/app/
That will copy it to the directory.
Nevermind, do what jeffv2 said.

THANKS! it's working now.
I had placed it in /system/app and did a reboot and it still hadn't installed
then i renamed the file from Widgetsoid2.x.apk to Widgetsoid.apk and also did chmod 644, after a reboot it has successfully installed.
I think it was the chmod 644 to the apk file that allowed it to be installed
Many thanks!

[ROOT available] [18-01-2015] Acer Liquid S1 / S510 / A10 with KK ROM!

Hi all,
*Q&A Thread is here*
Automatic process:
Please use the root from scratch method (only on UNIX!) from the Acer Iconia Toolkit thread
Manual process:
I have succeeded to root Acer Liquid S1 (S510 / A10). In the Acer Iconia Toolkit thread @Optimissimus99 mentioned to use the MTK Logger when using a Kitkat ROM. Using @vache's S1 root sources I figured out how root was done with JB using the Network Utility, so I tried doing the same steps using the MTK Logger.
Requirements:
Acer Liquid S1 (S510 / A10)
Being able to follow procedure to the step
Have an Ubuntu installation (I used 14.10)
Post screenshots, clear steps and results when asking for help
Getting root can be achieved with these steps:
Copy or download a busybox file (I used the one from the Iconia Toolkit) to your /sdcard
Using MTK Logger Util
Open engineering mode (for instance with MTK Engineering Mode)
Swipe to Log and Debugging screen
Open MTKLogger
Click on Settings
Click Run Command and execute the following commands:
cp /sdcard/busybox /data/local/tmp
chmod 755 /data/local/tmp/busybox
/data/local/tmp/busybox telnetd -l /system/bin/sh -p 1234
Using Terminal
ls -la /data/local/tmp/busybox
This should show correct execute permissions on busybox
/data/local/tmp/busybox telnet 127.0.0.1 1234
This should open Telnet correctly
cat /proc/dumchar_info | grep "android"
This should show the size of your system image. In my case:
"android 0x0000000040000000 0x0000000005d00000 2 /dev/block/mmcblk0p5”
so quickly calculating (using the code from Vache’s S1 Root tool)
l_seekBlocks = systemEndAddr / 4096; var endA = addrs[2]; endAddr = Convert.ToInt64(endA, 16); 0x0000000005d00000 97517568/4096 = 23808
l_countBlocks = systemStartAddr / 4096; var startA = addrs[1]; startAddr = Convert.ToInt64(startA, 16); 0x0000000040000000 1073741824/4096 = 262144
dd if=/dev/block/mmcblk0 bs=4096 skip=23808 count=262144 | gzip >/storage/sdcard1/system.img.gz
This should create your gzipped ROM dump on the external sdcard.
Within Ubuntu
Transfer the system.img.gz file to Ubuntu
Transfer extracted SuperSU (I used UPDATE-SuperSU-v2.40.zip)
Run the following code:
Code:
gunzip system.img.gz
sudo mkdir /media/iconia
sudo mount -o loop system.img /media/iconia
sudo mv /media/iconia/etc/install-recovery.sh /media/iconia/etc/install-recovery_original.sh
sudo mkdir /media/iconia/bin/.ext
sudo chmod 0777 /media/iconia/bin/.ext
sudo cp UPDATE-SuperSU-v2.40/common/Superuser.apk /media/iconia/app/Superuser.apk
sudo cp UPDATE-SuperSU-v2.40/common/install-recovery.sh /media/iconia/etc/install-recovery.sh
sudo cp UPDATE-SuperSU-v2.40/armv7/su /media/iconia/xbin/daemonsu
sudo cp UPDATE-SuperSU-v2.40/armv7/su /media/iconia/xbin/sugote
sudo cp UPDATE-SuperSU-v2.40/armv7/su /media/iconia/xbin/su
sudo cp UPDATE-SuperSU-v2.40/armv7/su /media/iconia/bin/.ext/.su
sudo cp /media/iconia/bin/mksh /media/iconia/xbin/sugote-mksh
sudo cp UPDATE-SuperSU-v2.40/armv7/supolicy /media/iconia/xbin/supolicy
sudo cp UPDATE-SuperSU-v2.40/armv7/libsupol.so /media/iconia/lib/libsupol.so
sudo chmod 0644 /media/iconia/app/Superuser.apk
sudo chmod 0755 /media/iconia/etc/install-recovery.sh
sudo chmod 0755 /media/iconia/xbin/daemonsu
sudo chmod 0755 /media/iconia/xbin/su
sudo chmod 0755 /media/iconia/bin/.ext/.su
sudo chmod 0755 /media/iconia/xbin/sugote
sudo chmod 0755 /media/iconia/xbin/sugote-mksh
sudo chmod 0755 /media/iconia/xbin/supolicy
sudo chmod 0644 /media/iconia/lib/libsupol.so
sudo ln -s /media/iconia/etc/install-recovery.sh /media/iconia/bin/install-recovery.sh
sudo umount /media/iconia
sudo rm -rf /media/iconia
mv system.img systemrooted.img
gzip systemrooted.img
Check for errors - if there is any, fix them
Next steps is to reload the system image with the following command:
copy systemrooted.img.gz to device
start mtklogger (see above 2.3 / 2.4)
start telnetdaemon (see above 2.5.3)
start terminal (see 3)
start telnet (see 3.2)
Run the command:
/data/local/tmp/busybox zcat /storage/sdcard1/systemrooted.img.gz | dd of=/dev/block/mmcblk0 bs=4096 seek=23808 count=262144
As I do not have much time, I am not sure when I can do this... will post progress in this thread.
Next steps in the development:
Add Xposed Framework
Thanks go to @vache @paugustin @Shreps @Optimissimus99 for providing some of the above info and helping me with this device!
Regards,
Nika.

Here's some screenshots:
{
"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"
}

You have done the hardest part, just need to push the su daemon service for KK ?
Envoyé de mon A1-840FHD en utilisant Tapatalk

Just in case anyone reads this thread and decides to try it on their own - the system.img wasn't mountable (yet). Looks like I used seek= instead of skip= when creating the new image... will try again later....

Yeah, rooting works!
Check first post for details...

Nice!!! Realy like your work So we now have root on Acer Liquid S1! Will there be a quick way to root it?
with a kinda batch tool for instance?

ARRRDJ said:
Nice!!! Realy like your work So we now have root on Acer Liquid S1! Will there be a quick way to root it?
with a kinda batch tool for instance?
Click to expand...
Click to collapse
Oh yeah, we sure will. I'll contact @entonjackson to know whether we can add it to his toolkit and @Chainfire to know whether we are allowed to include SuperSU in a kit this way...

nikagl said:
Oh yeah, we sure will. I'll contact @entonjackson to know whether we can add it to his toolkit and @Chainfire to know whether we are allowed to include SuperSU in a kit this way...
Click to expand...
Click to collapse
Nice!! Finally, root for S1
Will you keep us up to date with the latest developments? I cannot wait to run Xposed

ARRRDJ said:
Nice!! Finally, root for S1
Will you keep us up to date with the latest developments? I cannot wait to run Xposed
Click to expand...
Click to collapse
Sure. I will need @entonjackson for that though, otherwise I'll have to rewrite his code to suite S1, use the MTKLogger and add SuperSU. Adding Xposed is a good idea too - the problem with the /system on this device is that it's locked and we cannot unlock it. So adding stuff (or removing for that matter) always requires to use an existing /system dump and restore it to the device using dd. Recovery too, will only allow installation of signed zips and as we don't have the right keys, we won't be able to use (or change) it... In the end, doing a root from scratch will always require either Ubuntu (to do it with the ROM you have on your device) or restore a system.img from another device... It requires Ubuntu btw, because in Ubuntu you can mount a system.img and easily change it, which is not feasible from DOS/Windows...
So... for the time being, let's wait for @entonjackson and if he doesn't have the option, I'll try to write something. Just keep in mind I am not a developer, I can follow procedures and hack my way into existing stuff, but writing from scratch remains a bridge too far...

nikagl said:
Sure. I will need @entonjackson for that though, otherwise I'll have to rewrite his code to suite S1, use the MTKLogger and add SuperSU. Adding Xposed is a good idea too - the problem with the /system on this device is that it's locked and we cannot unlock it. So adding stuff (or removing for that matter) always requires to use an existing /system dump and restore it to the device using dd. Recovery too, will only allow installation of signed zips and as we don't have the right keys, we won't be able to use (or change) it... In the end, doing a root from scratch will always require either Ubuntu (to do it with the ROM you have on your device) or restore a system.img from another device... It requires Ubuntu btw, because in Ubuntu you can mount a system.img and easily change it, which is not feasible from DOS/Windows...
So... for the time being, let's wait for @entonjackson and if he doesn't have the option, I'll try to write something. Just keep in mind I am not a developer, I can follow procedures and hack my way into existing stuff, but writing from scratch remains a bridge too far...
Click to expand...
Click to collapse
Okay, let's hope @entonjackson can help! Oehw that's sad. So it's impossible to root this phone on the 'normal' way? Is it restricted in the software or in the hardware?
But once you've rooted it, can you use Xposed (or another rootapp), without having to restore a systemdump file?
Ubuntu is not a problem, since I develop in Ubuntu
No problem! I've a lot of respect that you came so far without having a lot of experience

ARRRDJ said:
Okay, let's hope @entonjackson can help! Oehw that's sad. So it's impossible to root this phone on the 'normal' way? Is it restricted in the software or in the hardware?
But once you've rooted it, can you use Xposed (or another rootapp), without having to restore a systemdump file?
Ubuntu is not a problem, since I develop in Ubuntu
No problem! I've a lot of respect that you came so far without having a lot of experience
Click to expand...
Click to collapse
It's in the software/signing of the zips. The keys are unavailable for "normal" people like us. Just Acer has them I guess.
Yes, as soon as Xposed is integrated, you can use it. With the integration I am a bit worried to do it though. I have looked at the current release of Xposed (de.robv.android.xposed.installer_v33_36570c) and it requires me to replace /system/bin/app_process with the one from Xposed. My S1 does not have USB access anymore so I am very hesitant to replace a file like that. If it gets into a bootloop, I won’t be able to recover it…
Also, the update-binary that Xposed uses to integrate itself into the framework replaces that app_process file, but also expects certain configuration (/data/data/de.robv.android.xposed.installer) of the APK to be available. I am afraid that the apk needs to be installed before actually introducing the new app_process file. As the installation of the APK is not part of /system and therefore the /data folders will not be created, I wonder how it behaves if the new file is introduced in the new /system...hopefully it won't cause bootloops....
Regards,
Nika.

I tried adding Xposed by changing the app_process file but it didn't work. I used the following commands:
Code:
sudo cp de.robv.android.xposed.installer_v33_36570c.apk /media/iconia/app/
sudo cp -a /media/iconia/bin/app_process /media/iconia/bin/app_process.orig
sudo cp de.robv.android.xposed.installer_v33_36570c/assets/arm/app_process_xposed_sdk16 /media/iconia/bin/app_process
sudo chmod 0755 /media/iconia/bin/app_process
It does see the new file version installed but Xposed is not running. Asked in some threads for extra help. Also no response yet from @entonjackson, so asked in the Iconia thread whether there's others that can help

nikagl said:
I tried adding Xposed by changing the app_process file but it didn't work. I used the following commands:
Code:
sudo cp de.robv.android.xposed.installer_v33_36570c.apk /media/iconia/app/
sudo cp -a /media/iconia/bin/app_process /media/iconia/bin/app_process.orig
sudo cp de.robv.android.xposed.installer_v33_36570c/assets/arm/app_process_xposed_sdk16 /media/iconia/bin/app_process
sudo chmod 0755 /media/iconia/bin/app_process
It does see the new file version installed but Xposed is not running. Asked in some threads for extra help. Also no response yet from @entonjackson, so asked in the Iconia thread whether there's others that can help
Click to expand...
Click to collapse
Ah okay, unfortunately!! I cant wait to run xposed! I hope you'll get some support from members with more experience, because I think we're really close to a more easier rooting way
Let me know if you make some progress

ARRRDJ said:
Ah okay, unfortunately!! I cant wait to run xposed! I hope you'll get some support from members with more experience, because I think we're really close to a more easier rooting way
Let me know if you make some progress
Click to expand...
Click to collapse
So do I and trust me - I tried it all. Also tried it on another device, it will simply not start and I don't know why
Regards,
Nika.

progress?
Any progress yet?

ARRRDJ said:
Any progress yet?
Click to expand...
Click to collapse
Nope, just root works. If you want I can add it to the rootfrom scratch method of the toolkit, but Xposed won't work. Simply do not get any help from anywhere to fix this and spent hours (if not days!) troubleshooting it, so i have given up...

thanks it's a wonderful job anyway u really deserve respect! :highfive:

Make sure to monitor the following thread for new versions:
http://forum.xda-developers.com/showthread.php?t=2240029
I am not yet sure when I get to make one, it's almost holiday week here in NL and with that and the preparations for it I don't have much time... more news soon.

I have created the first Acer Liquid S1 version of the toolkit. Let me know what you think.

First of all thank you very much for your efforts, I just downloaded your toolkit but it says "put prerooted system.img.gz... " etc. Question is where do I find prerooted system.img.gz?

[COMPLETE GUIDE]Root HD7/8/10(6th Gen 2016) and replace with SuperSU

FOR 2016(6th GEN) ON 5.3.1 AND 5.3.1.1 ONLY: Works on HD7, HD8 and HD10
You can downgrade from 5.3.2 by adb sideload the 5.3.1.1 bin file.
DO NOT downgrade from 5.3.2.1!! Hard-brick attention!!
This guide requires some ADB skills, read more from the forum, install it from here
Enable ADB and install apps from other sources in Developer Options
Download Kingoroot PC version at www.kingoapp.com or google mirror
Root your Kindle using Kingoroot, then reboot your device
Download a file explorer apk (ie. ES File Explorer) and sideload install the apk to your kindle
Download SuperSU apk at APKPure, but DON'T install it first
Download the attachment "Kingo.to.SuperSU" below then unzip and paste into your kindle, ie /sdcard/Kingo.to.SuperSU
Run ADB Shell and type
Code:
su
mount -w -o remount /system
Keep the root-accessed ADB shell open, then remove root by using Kingoroot
(If your kindle reboot at this step, you need to re-root it and try the above steps again)
In the ADB shell type
Code:
cd /sdcard/Kingo.to.SuperSU
cp ./su /system/xbin/daemonsu
chmod 0755 /system/xbin/daemonsu
daemonsu -d &
Still keep that root-accessed ADB shell opened, copy the SuperSU apk into your kindle and install it using the file explorer, DO NOT OPEN IT.
In the ADB shell type
Code:
cp ./su /system/xbin/su
chmod 0755 /system/xbin/su
rm /system/xbin/supolicy
rm /system/bin/install-recovery.sh
rm -rf /system/usr/iku
rm -rf /sdcard/Kingroot
(1 error with "No such file or directory" is okay I think)
Run SuperSU and update binary, choose the "normal" one, then it should ask you to reboot your kindle
Open up SuperSU and go to setting
Set the "Default Access" as [Grant]
{
"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"
}
Due to unknown reason, kindle cannot prompt the "Asking for root access", this step is to allow all access for all apps.
Install Root Checker and confirm you have root, run ADB shell to confirm you can su
Remove Kingolink and that Kingo battery app from kindle
Uninstall Kingo from PC via manual unins000.exe inside install directory in programs(x86)
ALL DONE! You may then want to install google play, do all the pm disable for OTA, firelauncher, and other amazon services you don't want.
References:
[Index] Amazon Fire HD 8 and HD 10 (5th Gen/2015)
[Working]Root Kindle Fire HD8 6th Gen
Tips, Tricks, and the Root!
[HOW-TO] Install Google Play Store (Fire OS 5.3.1.1) (No Root/ADB)
[Script] Replace KingoRoot with SuperSU
Credits:
@coltxL2717
@chemie99
@2ig2ag
@smokejumper76
@phpbb88 ME

phpbb88 said:
Code:
cp ./su /system/xbin/su
chmod 0755 /system/xbin/su
rm /system/xbin/supolicy
rm /system/bin/install-recovery.sh
rm -rf /system/usr/iku
rm -rf /sdcard/Kingroot
[*]Run SuperSU and update binary then it should ask you to reboot your kindle
[*]Open up SuperSU and go to setting
Click to expand...
Click to collapse
Getting error at Step 11:
After entering
rm /system/bin/install-recovery.sh
getting
No such file or directory
Then when updating binaries, SuperSU says "Installation successful! Reboot your device." On reboot, says that binaries are not installed and the app closes itself. Also, when initially updating SuperSU binaries, which option is to be chosen? The first "Normal" or the second "Custom/TWRP."
Here is my full log:
[email protected]:/ $ su
[email protected]:/ # mount -w -o remount /system
[email protected]:/ # cd /sdcard/Kingo.to.SuperSU
[email protected]:/sdcard/Kingo.to.SuperSU # cp ./su /system/xbin/daemonsu
[email protected]:/sdcard/Kingo.to.SuperSU # chmod 0755 /system/xbin/daemonsu
[email protected]:/sdcard/Kingo.to.SuperSU # daemonsu -d &
[1] 5542
[email protected]:/sdcard/Kingo.to.SuperSU # cp ./su /system/xbin/su
[1] + Done daemonsu -d
[email protected]:/sdcard/Kingo.to.SuperSU # chmod 0755 /system/xbin/su
[email protected]:/sdcard/Kingo.to.SuperSU # rm /system/xbin/supolicy
[email protected]:/sdcard/Kingo.to.SuperSU # rm /system/bin/install-recovery.sh
rm: /system/bin/install-recovery.sh: No such file or directory
1|[email protected]:/sdcard/Kingo.to.SuperSU # rm -rf /system/usr/iku
[email protected]:/sdcard/Kingo.to.SuperSU # rm -rf /sdcard/Kingroot
[email protected]:/sdcard/Kingo.to.SuperSU # reboot

imadiamond said:
Getting error at Step 11:
After entering
rm /system/bin/install-recovery.sh
getting
No such file or directory
Then when updating binaries, SuperSU says "Installation successful! Reboot your device." On reboot, says that binaries are not installed and the app closes itself. Also, when initially updating SuperSU binaries, which option is to be chosen? The first "Normal" or the second "Custom/TWRP."
Here is my full log:
[email protected]:/ $ su
[email protected]:/ # mount -w -o remount /system
[email protected]:/ # cd /sdcard/Kingo.to.SuperSU
[email protected]:/sdcard/Kingo.to.SuperSU # cp ./su /system/xbin/daemonsu
[email protected]:/sdcard/Kingo.to.SuperSU # chmod 0755 /system/xbin/daemonsu
[email protected]:/sdcard/Kingo.to.SuperSU # daemonsu -d &
[1] 5542
[email protected]:/sdcard/Kingo.to.SuperSU # cp ./su /system/xbin/su
[1] + Done daemonsu -d
[email protected]:/sdcard/Kingo.to.SuperSU # chmod 0755 /system/xbin/su
[email protected]:/sdcard/Kingo.to.SuperSU # rm /system/xbin/supolicy
[email protected]:/sdcard/Kingo.to.SuperSU # rm /system/bin/install-recovery.sh
rm: /system/bin/install-recovery.sh: No such file or directory
1|[email protected]:/sdcard/Kingo.to.SuperSU # rm -rf /system/usr/iku
[email protected]:/sdcard/Kingo.to.SuperSU # rm -rf /sdcard/Kingroot
[email protected]:/sdcard/Kingo.to.SuperSU # reboot
Click to expand...
Click to collapse
in step 10, install SuperSU but do not open it.
your log should have no problem, maybe try again from clean state? (clean 5.3.1./5.3.1.1 state)
PS. you should choose "normal" when update binary

Thanks for making this clear and concise guide! Well done.

phpbb88 said:
in step 10, install SuperSU but do not open it.
your log should have no problem, maybe try again from clean state? (clean 5.3.1./5.3.1.1 state)
PS. you should choose "normal" when update binary
Click to expand...
Click to collapse
Did cache wipe/format and reset to factory settings via device recovery (powering on and holding volume button.)
Went through the process again, and THOUGHT it worked, even though I got the same "No such file or directory" error. I didn't reboot on Step 12 and went into SuperSU setings to "Grant." Got Root Checker. Had root. Rebooted and opened Root Checker and had no root. So--
1) still getting same "No such file" error: how can I reset the device "clean" without that new .bin? Isn't there a way to "clean" the OS already on the device? On 5.3.1.1 On device did "wipe data/factory reset" then "wipe cache partition" and have also done them in the opposite order to make sure.
2) On step 12 do you reboot the device like SuperSu says, or do you just go straight into the settings. I was rebooting the device at this point for 3 or 4 tries. The last two times I did not and went straight into settings. Still same error of "No such file or directory." The file IS in the Kingo.to.SuperSU folder though, even downloaded and unzipped the attachment a few times.

Could I also install a customrom after root? with one?

meikschlenther said:
Could I also install a customrom after root? with one?
Click to expand...
Click to collapse
Not at this time... There are no ROMs as of yet, and if I'm not mistaken we would need a custom recovery and our bootloader is still locked.

imadiamond said:
Did cache wipe/format and reset to factory settings via device recovery (powering on and holding volume button.)
Went through the process again, and THOUGHT it worked, even though I got the same "No such file or directory" error. I didn't reboot on Step 12 and went into SuperSU setings to "Grant." Got Root Checker. Had root. Rebooted and opened Root Checker and had no root. So--
1) still getting same "No such file" error: how can I reset the device "clean" without that new .bin? Isn't there a way to "clean" the OS already on the device? On 5.3.1.1 On device did "wipe data/factory reset" then "wipe cache partition" and have also done them in the opposite order to make sure.
2) On step 12 do you reboot the device like SuperSu says, or do you just go straight into the settings. I was rebooting the device at this point for 3 or 4 tries. The last two times I did not and went straight into settings. Still same error of "No such file or directory." The file IS in the Kingo.to.SuperSU folder though, even downloaded and unzipped the attachment a few times.
Click to expand...
Click to collapse
Please download the official 5.3.1.1 bin, wipe cache, factory reset, then sideload the bin through recovery mode and follow the guide step by step strictly.
edited: please have a look at here, I somehow worked with 1 error, which is likely the "rm /system/bin/install-recovery.sh" command.

phpbb88 said:
Please download the official 5.3.1.1 bin, wipe cache, factory reset, then sideload the bin through recovery mode and follow the guide step by step strictly.
edited: please have a look at here, I somehow worked with 1 error, which is likely the "rm /system/bin/install-recovery.sh" command.
Click to expand...
Click to collapse
First problem was even though previously all drivers loaded and I was able to root/re-root and navigate adb.... when booting the device into recovery mode? Tablet not recognized by computer. Extremely frustrating. Read and read and read.... and finally came across something from @smokejumper76 -----answer was in Device Manager, tablet was showing up as KFGIWI with the error that drivers were not installed. Did "manually install drivers" "Search online" does not work) and chose ADB Composite Device, and now tablet is recognized in recovery mode.
Issue NOW is the process gets halfway through installation and then force closes with
E: failed to verify whole-file signature
E: signature verification failed
Man, I am ticked. What now? Been reading for the past hour++. People elsewhere are saying to change the .bin extension to .zip, but I haven't seen that here on the XDA forum.
---------- Post added at 01:48 AM ---------- Previous post was at 01:11 AM ----------
Install from ADB complete: went through. After multiple tries, did 2 things at once so not sure which one it was
1) ran cmd prompt as Administrator
2) deleted all 5.3.1.1 bin files from computer, just in case what was gotten previously was corrupt, and redownloaded fresh file onto the ADB computer, instead of the copy and paste version from another computer

Thanks for making this guide! Worked perfect 1st time on my hd8 2016. Used rootjunky supertool to disable ota, install nova, disable ads Lockscreen, install Google play.
Just a thought, in the guide, you state, you could get es file Explorer from Amazon appstore, which would imply you have wifi on...which could get you updated to 5.3.2.1 without you knowing? Should prolly stick to sideloading ES only until ota is disabled.
Thanks again
From the time I turned the hd8 on for 1st time, I kept wifi off until I was rooted and able to disable ota.

I hope all you guys are also donating some bux to Kingoroot (I did).
We want to keep those geniuses happy and cranking out rooting updates for the v5.3.2.x builds!

Thanks so much for the guide. It was pretty easy to get through!
I have Nova Launcher running now and it is way better.
However, Auto Rotate screen isn't working quite right. If it is in Portrait, it will flip to landscape if I turn the tablet, but then it gets stuck in landscape which is the wrong landscape that I need for my Fire cover/stand.
Anyone else experiencing this?

Dumbest question:
the root is supposed to stay after turning the tablet off and on again, right?
I say this because went through the whole process successfully. New .bin. No errors on any commands. SuperSU installed binaries and then downloaded Root Checker and verified. Then verified su in adb shell. Then did pm disable of amazon apps and services,
and then turned tablet off and back on and Root Checker says NO ROOT. Root is supposed to stay, correct??? Or is it to just get all of the Amazon items off and customize tablet. Have rooted at least 8 or 9 devices, LG, Samsung, HTC etc, and this one has been the absolute _____ .

el7145 said:
Thanks for making this guide! Worked perfect 1st time on my hd8 2016. Used rootjunky supertool to disable ota, install nova, disable ads Lockscreen, install Google play.
Just a thought, in the guide, you state, you could get es file Explorer from Amazon appstore, which would imply you have wifi on...which could get you updated to 5.3.2.1 without you knowing? Should prolly stick to sideloading ES only until ota is disabled.
Thanks again
From the time I turned the hd8 on for 1st time, I kept wifi off until I was rooted and able to disable ota.
Click to expand...
Click to collapse
Thanks for pointing out the mistake, cause I had disable ota update by OpenDNS method before, so I was not aware of this.

imadiamond said:
Dumbest question:
the root is supposed to stay after turning the tablet off and on again, right?
I say this because went through the whole process successfully. New .bin. No errors on any commands. SuperSU installed binaries and then downloaded Root Checker and verified. Then verified su in adb shell. Then did pm disable of amazon apps and services,
and then turned tablet off and back on and Root Checker says NO ROOT. Root is supposed to stay, correct??? Or is it to just get all of the Amazon items off and customize tablet. Have rooted at least 8 or 9 devices, LG, Samsung, HTC etc, and this one has been the absolute _____ .
Click to expand...
Click to collapse
did you change the default access in SuperSU from prompt to grant? or have you disabled the OTA service?
in normal case, root will not lose till the OS updated.

Need to type exit, exit in shell to save settings?
phpbb88 said:
did you change the default access in SuperSU from prompt to grant? or have you disabled the OTA service?
in normal case, root will not lose till the OS updated.
Click to expand...
Click to collapse
Good question. Thanks for asking phpbb88! Definitely changed the default access. Rebooting here was one of the problems earlier since SuperSU says to reboot, then you must hit "Ok"-- and then logically, you would reboot. But instructions don't say to *ignore* and stay in SuperSU. Previously was rebooting, since Step 13 says "Open up SuperSU"... but SuperSU is already open in Step 12, so no need to open it up.
Only connected to the internet with it once, in December. Saw that everything needed an Amazon account, so have had wireless off/airplane mode ever since. Bought it with sole purpose to root.
The only thing I can think of would be not typing "exit" twice to get out of the shell. First read that instruction at the end of the pm disabling tutorial. If that's important than it needs to be added to the instructions also. Otherwise, when finished people will just power down the device or pull the USB plug. It's got to be written so that someone not knowing anything- first-time Kindle buyer like me , can do it. Here is the log.
[email protected]:/ $ su
[email protected]:/ # mount -w -o remount /system
[email protected]:/ # cd /sdcard/Kingo.to.SuperSU
[email protected]:/sdcard/Kingo.to.SuperSU # cp ./su /system/xbin/daemonsu
[email protected]:/sdcard/Kingo.to.SuperSU # chmod 0755 /system/xbin/daemonsu
[email protected]:/sdcard/Kingo.to.SuperSU # daemonsu -d &
[1] 7590
[email protected]:/sdcard/Kingo.to.SuperSU # cp ./su /system/xbin/su
[1] + Done daemonsu -d
[email protected]:/sdcard/Kingo.to.SuperSU # chmod 0755 /system/xbin/su
[email protected]:/sdcard/Kingo.to.SuperSU # rm /system/xbin/supolicy
[email protected]:/sdcard/Kingo.to.SuperSU # rm /system/bin/install-recovery.sh
[email protected]:/sdcard/Kingo.to.SuperSU # rm -rf /system/usr/iku
[email protected]:/sdcard/Kingo.to.SuperSU # rm -rf /sdcard/Kingroot
[email protected]:/sdcard/Kingo.to.SuperSU #
C:\Users\COMPUTER\AppData\Local\Android\Sdk\platform-tools>

smokejumper76 said:
I used eu.chainfire.supersu_2.79-SR3-279_minAPI7(nodpi)_apkmirror.com.apk for superSU...that would be another thing to check
Click to expand...
Click to collapse
ROOOOOOOOOOOOOOOOOTEEEDDDDDDDDDDDDDDD.
Final piece of puzzle I think it was the SuperSU I had. Didn't do any other changes. Got it from appsapk.com . FOLKS, do not use any SuperSU you get from there (or anywhere else) at least for this process. You'll end up chasing squirrels. It *might* have gone through even with the other errors etc (like phpbb88 mentioned it did for him), but the wrong SuperSU probably killed everything in the end. Go to https://apkdot.com/apk/chainfire/sup...ersu-2-79-sr3/ and get your SuperSU there: thank you for the suggestion smokejumper76. For one, immediately noticed the app logo was different. Also took longer to load the binaries. Whatever the other SuperSU apk is I'm deleting it now: don't even want to know the version.
phpbb88, I see you added the answer to my question about which option to pick in SuperSU (Normal) to the instructions. Thanks! Would also suggest 1) to add a note NOT to reboot even though SuperSU asks to, since in the next line you say "Open SuperSU" but it's already open and 2) the link for the proper SuperSU in the credits at the end, or the file even.
This was Christmas gift for my gf... now she can use it. Was planning on getting a HD10 for myself, but it's been so long that unfortunately now it might ship with newer software. Might buy one from a retail store as they will have older stock, and the return will be a quick walk-in if it's got 5.3.+.+ .

imadiamond said:
ROOOOOOOOOOOOOOOOOTEEEDDDDDDDDDDDDDDD.
Final piece of puzzle I think it was the SuperSU I had. Didn't do any other changes. Got it from appsapk.com . FOLKS, do not use any SuperSU you get from there (or anywhere else) at least for this process. You'll end up chasing squirrels. It *might* have gone through even with the other errors etc (like phpbb88 mentioned it did for him), but the wrong SuperSU probably killed everything in the end. Go to https://apkdot.com/apk/chainfire/sup...ersu-2-79-sr3/ and get your SuperSU there: thank you for the suggestion smokejumper76. For one, immediately noticed the app logo was different. Also took longer to load the binaries. Whatever the other SuperSU apk is I'm deleting it now: don't even want to know the version.
phpbb88, I see you added the answer to my question about which option to pick in SuperSU (Normal) to the instructions. Thanks! Would also suggest 1) to add a note NOT to reboot even though SuperSU asks to, since in the next line you say "Open SuperSU" but it's already open and 2) the link for the proper SuperSU in the credits at the end, or the file even.
This was Christmas gift for my gf... now she can use it. Was planning on getting a HD10 for myself, but it's been so long that unfortunately now it might ship with newer software. Might buy one from a retail store as they will have older stock, and the return will be a quick walk-in if it's got 5.3.+.+ .
Click to expand...
Click to collapse
Glad to hear that you can finally root your fire.
In fact, I never typed exit twice in adb shell, I just close it...lol
1) After SuperSU updates its binary, I followed the reboot, still success to root my device.
2) I am using the SuperSU apk download from apkpure linked above, why don't you download it in the first try...?
I went to appsapk.com and have a look of the SuperSU, it is totally a different app.

Thanks for the Guide finally got root!

phpbb88 said:
in step 10, install SuperSU but do not open it.
your log should have no problem, maybe try again from clean state? (clean 5.3.1./5.3.1.1 state)
PS. you should choose "normal" when update binary
Click to expand...
Click to collapse
I had the exact same problem over and over finally tried this:
change this: rm /system/bin/install-recovery.sh
To this: rm install-recovery.sh