Develop Bugs

[GUIDE][WIFI ONLY]Android 3.1 on Xoom WiFi, Root, via ClockworkMod Recovery

This guide may be obsolesced shortly, but it's still good reading for the curious. See [UPDATE][HC3.1] Wifi and 3G! Completely Flashable! No Fastboot Needed! No Data Loss. (thanks, bigrushdog)
WARNING: Following this procedure may damage or permamently destroy your device. This procedure is provided with NO WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Perform this procedure at your own risk.
COMPATIBILITY NOTE: I have personally tested this procedure ONLY ON THE US XOOM WIFI MZ604. If other devices (i.e., Euro Xoom WiFi) implement the same Android 3.1 update file, then this procedure *should* work; some users have reported success with UK and Canadian models (see this post for more info). Know, however, that you proceed at your own risk.
AWESOMENESS NOTE: Instead of copying files which you're going to adb push to the platform-tools directory every time, why not just add the directory to your PATH environment variable ("How to update your PATH")? That way, you can run adb from any directory you want.
3G GUINEA PIGS: I've edited the 3G version of the updater_script in the same way as the WiFi, but I don't have a 3G Xoom with which to test. IF YOU ARE FLASHING AND TROUBLESHOOTING SUPASTAH, please try the attached updater-script_UNTESTED_Xoom3G_Android3.1_Root_v03.zip(Updated!) with the MZ600 HRI66 stock images and Xoom 3G 3.1 Update ZIP. If it works, I'll update the guide to cover both devices. Please PM me your feedback, since a post might be easily buried in this thread. Thanks!
[size=+1]SUMMARY[/size]
Here's a run-down on the current procedure:
Updates the Xoom WiFi to Android 3.1 using ClockworkMod Recovery (update.zip)
Resolves issue in updater-script: get_prop ro.product.device wingray
Sets correct permission on su to enable functioning root
Flashes the recovery (version 03 persists CWM Recovery), boot (kernel), and system partitions to stock (required at this time)
Stock kernel means no SD Card in Honeycomb (still available in recovery), no overclocking until devs release 3.1 compatible kernels
Updates bootloader to include Recovery in the boot menu
Leaves user data intact
Outstanding Issues:
(FIXED in updater_script version 03) Recovery partition gets overwritten to stock on reboot: Edit updater-script to leave recovery partition intact
Too many steps: Include the edited updater-script, su, Superuser.apk in the update.zip
Now, without further ado...
[size=+1]ASSUMPTIONS[/size]
You've downloaded the Xoom WiFi Android 3.1 update from Google (thanks, pof)
You've downloaded and unzipped the stock Xoom WiFi MZ604 HWI69 images from Motorola
You've downloaded su and Superuser.apk (see WiFi Xoom Root Zip link at Xoom WiFi (MZ604) Root!!)
You've flashed a boot.img that enables adb remount (Xoom WiFi (MZ604) Root!!, custom kernels, etc.)
You've flashed ClockworkMod Recovery (thanks, bigrushdog, koush, et al)
You've installed a physical SDCard in your Xoom (required for ClockworkMod Recovery updates) and have it functioning properly
You've configured the Android SDK on your PC, with adb functioning properly
You've downloaded fastboot and have it functioning properly (usually alongside adb in platform-tools)
You've installed an archive program that lets you edit the contents of an existing ZIP file (7-Zip, WinRAR, etc.)
You've downloaded and unzipped the edited updater_script file attached to this post
[size=+1]PROCEDURE[/size]
Prepare the Android 3.1 Update file
The update file as-provided is not ready for use in ClockworkMod Recovery. This fixes it. I could just include a link to a prepared update.zip file, but this is safer than trusting some dude with less than 20 posts on XDA. I'll upload one when I hit 25.
Rename the Android 3.1 Update file to update.zip
Open the zip file in an archive program for editing
Navigate to the following directory: META-INF/com/google/android
Delete the following file: updater-script
Copy the updater-script file from the ZIP file attached to this post to META-INF/com/google/android
Flash stock system.img
Prior to performing the actual update, the update script checks a number of files (including bcm4329.ko, which is usually built with the kernel) in /system. If any file doesn't match what's expected, the update halts. Flashing the stock system.img ensures a smooth update.
Code:
adb reboot bootloader
fastboot flash system system.img
fastboot reboot
Reconfigure superuser
After flashing stock, we no longer have superuser/root access on our Xoom. By pushing and configuring these files, we restore our root capability without interfering with the pre-update checks. (thanks, Berzerker for catching missing symlink)
Code:
adb remount
adb push su /system/bin/
adb shell chown root.shell /system/bin/su
adb shell chmod 4755 /system/bin/su
adb shell ln -s /system/bin/su /system/xbin/su
adb push Superuser.apk /system/app/
adb shell chmod 644 /system/app/Superuser.apk
Flash stock boot.img
The pre-update checks also include the boot partition. We wait until now to flash the boot partition to stock because we need to perform adb remount earlier in the procedure, which we can't do with the stock boot.img. The actual update flashes this partition with a new kernel that implements the new 3.1 features.
Code:
adb reboot bootloader
fastboot flash boot boot.img
fastboot reboot
Perform update
Code:
adb reboot recovery
Note that in recovery, you use the hardware volume buttons to navigate up and down, and the power button to select.
In ClockworkMod Recovery, select "mounts and storage"
Ensure your Xoom is connected to your PC via USB, then select "mount USB storage"
On your PC, copy update.zip to the root of the Xoom's SDCard ("Removable Disk" in Windows)
In ClockworkModRecovery (still on the "USB Mass Storage device" screen) select "Unmount"
In the "Mounts and Storage Menu" screen, if the option "unmount /sdcard" is present, continue to the next step; if "mount /sdcard" is present, select it then continue
Select "+++++Go Back+++++"
Select "apply update from sdcard"
Select "Yes - Install /sdcard/update.zip"
"Install from sdcard complete." will indicate that the update is completed.
.
Select "reboot system now"
New bootloader will install. The message, "Congratulation! Your bootloader was successfully upgraded" will be immediately followed by an automatic reboot.
Enjoy your rooted Xoom WiFi, running on Android 3.1!
[size=+1]POST-UPDATE NOTES[/size]
Custom kernels: As of 0730 11 May 2011, there are no kernels/boot.img that are compatible with the Android 3.1 update, though the devs are undoubtedly on it. Do not flash a custom kernel after performing this procedure unless you know that it's compatible with the 3.1 update.
Recovery: updater_script v03 no longer flashes stock recovery. If you ran a previous version of the update, please see this post by Berzerker on getting ClockworkMod Recovery to persist (thanks, Berzerker)

NICE! Will be trying this out shortly.

trying it now.... will give feedback

Can someone confirm the filesize and md5 of the update zip file? (the actual update.zip, not the updater-script)

Do I need to be using the stock kernal before I start?

good post.... cant wait to try this when I get home.

here's the official update link for wifi xoom:
http://android.clients.google.com/p...signed-tervigon-HMJ37-from-HWI69.e379f0b9.zip

just one quick question why is it US only ? don't you think it should work on wifi only euro too ?

pof said:
here's the official update link for wifi xoom:
http://android.clients.google.com/p...signed-tervigon-HMJ37-from-HWI69.e379f0b9.zip
Click to expand...
Click to collapse
Yes, but the official update won't flash in ClockwordMod Recovery unless it is modified, like the one in the OP of this thread. Posting the official version on this thread just adds to the confusion.

publicanimal said:
Yes, but the official update won't flash in ClockwordMod Recovery unless it is modified, like the one in the OP of this thread. Posting the official version on this thread just adds to the confusion.
Click to expand...
Click to collapse
All he posted in the OP was a modified script, you still need to get the update.zip from Google.
The Google server is much much faster than the 3rd party download sites too.

le_pere_noel said:
just one quick question why is it US only ? don't you think it should work on wifi only euro too ?
Click to expand...
Click to collapse
Only because I don't have a test device. I'll update the post.

Just got done with this procedure, and it works perfectly.
I'm rooted on 3.1 on my WiFi Xoom.
Thanks OP!

stachre said:
[*]Flash stock system.img
Code:
adb reboot bootloader
fastboot flash system.img
fastboot reboot
Click to expand...
Click to collapse
fastboot flash system system.img

tony710 said:
All he posted in the OP was a modified script, you still need to get the update.zip from Google.
The Google server is much much faster than the 3rd party download sites too.
Click to expand...
Click to collapse
Ah my bad, I only saw the .zip at the end of the filename

Anyone know if this works in Canada?

tony710 said:
Just got done with this procedure, and it works perfectly.
I'm rooted on 3.1 on my WiFi Xoom.
Thanks OP!
Click to expand...
Click to collapse
So, maybe a stupid question, but did you have Tiamat kernel installed? Just wondering if that makes a difference. Thanks!
-edit- plus, will this wipe all userdata??

were do we find a boot.img that enables adb remount?

Thanks man! Can't wait to give this a try when I get home!
One general question though, what program do you guys use to edit the update.zip?
Thanks in advance for the help fellas!
Peace
Dan

mbroeders said:
So, maybe a stupid question, but did you have Tiamat kernel installed? Just wondering if that makes a difference. Thanks!
-edit- plus, will this wipe all userdata??
Click to expand...
Click to collapse
Yeah, I had Tiamat installed and all my userdata stayed.
I'm currently trying to see if I can flash the latest Tiamet back to see what happens.

dowenprs said:
Thanks man! Can't wait to give this a try when I get home!
One general question though, what program do you guys use to edit the update.zip?
Thanks in advance for the help fellas!
Peace
Dan
Click to expand...
Click to collapse
I used 7z to edit the zip file

[Q] [GUIDE] Back up DRM Keys and so on

Because it's my first post and that's why i'm not able to reply to the original thread in android development Forum i have to ask start a new thread here.
I received my d5503 few days ago and read the [GUIDE] Back up DRM Keys & unlock/relock Bootloader (Noob proof). I was wondering if i can flash instead of, as stated in step 15.Flash D5503_14.2.A.1.114_Generic UK.ftf in flashmode (boot phone in flashmode again) (select Wipe [Uncheck ALL] and Exclude [Check SYSTEM] (link deleted) my OWN original D5503_14.2.A.1.142_Telekom.de DE.ftf which i made today with the files downloaded today with the sony pc Software and flashtool and which is the newer FW? I mean to have my stock Firmware rooted and afterwards backup TA partititions/DRM Keys.
Thanks in advance

I think you can yes. But probably you also need to have a flashable zip of /system from the german rom (see step 19) (see also this: http://forum.xda-developers.com/showpost.php?p=50355068&postcount=34 ).
By the way we will appreciate if you upload the ftf and post it here: http://forum.xda-developers.com/showthread.php?t=2631291 !

zxz0O0 said:
I think you can yes. But probably you also need to have a flashable zip of /system from the german rom (see step 19) (see also this: http://forum.xda-developers.com/showpost.php?p=50355068&postcount=34 ).
By the way we will appreciate if you upload the ftf and post it here: http://forum.xda-developers.com/showthread.php?t=2631291 !
Click to expand...
Click to collapse
yep, after i read the guide again, i thought so too, but this is now the Point where my noobishness takes part. where do i have to type the
adb push busybox /data/local/tmp/
disconnect usb cable
open terminal emulator and do:
cd /data/local/tmp
chmod 755 busybox
./busybox tar pczvf /storage/removable/sdcard1/system.tar.gz /system
now you have full system backup in your external sdcard. Ater rooting, simple do:
cd /
busybox mount -o remount,rw /system
busybox tar xzvf /storage/removable/sdcard1/system.tar.gz
reboot
Click to expand...
Click to collapse
?? in Windows cmd or terminal Emulator on my phone?
ill upload my ftf asap

The first line is in windows cmd (in adb folder). Later on it's in terminal emulator (on the phone) as described. Then you can make a flashable zip of /system and use that in step 19.
And if you flash your own ftf in step 15, check if simlock.ta or preset1.ta is in the file list ("Content" in flashtool). If there is, exclude it.

zxz0O0 said:
The first line is in windows cmd (in adb folder). Later on it's in terminal emulator (on the phone) as described. Then you can make a flashable zip of /system and use that in step 19.
And if you flash your own ftf in step 15, check if simlock.ta or preset1.ta is in the file list ("Content" in flashtool). If there is, exclude it.
Click to expand...
Click to collapse
ok, i think i'll make it. i skipped all .ta files in my .ftf, because in the how to create .ftf guide it was mentioned. so no need to exclude. I'm uploading it at the Moment and post it to the thread you mentioned when upload is finished.

here's the link for the .ftf. hmm, still not able to post links...
another thing i have to ask is, where do i get the busybox from? for the adb push cmd from munjeni`s post?

You can find busybox inside the Z1C-lockeddualrecovery(...)installer.zip you downloaded on step 13
If you want you can pm me the link and I'll post it. I think you need 10 posts.

next problem, next question
if i try to set permissions for the busybox with the chmod cmd, i get a no permission for chmod error on my phone/terminal emulator. Do i have to make this system dump after step 15. of the Back up DRM Keys Guide, or does this method only work for already rooted devices?

Try this (all steps in adb on computer):
adb push busybox /data/local/tmp
adb shell
cd /data/local/tmp
chmod 777 busybox
./busybox tar pczvf /storage/removable/sdcard1/system.tar.gz /system
Copy system.tar.gz from your sdcard to your computer.

So the rooting guide was quiet good, no errors occurred and finaly i got a rooted uk .114 firmware and i coud backup my ta partitition. But, flashing my own or any other .ftf seems to make no sense, without flashing the corresponding system.zip in step 20 ;(.
I tried your adb cmd and it seemed to work in the first moment, but for the lost&found folder there was the error permission denied and in the end there was the following: tar: error exit delayed from previous errors
and theres no system.tar.gz on my external sd.
Any explanations?

Yes I said you also need a flashable zip of /system (see post #2 and #4 of this thread).
I just tested it and I also have the error "tar: error exit delayed from previous errors" but I do have the system.tar.gz on my sdcard.
Did you already flash something? Because then you overwrote /system partiton.
Another method is: extract system.sin with WinRar from the ftf file. Open flashtool => Tools => Sin Editor => Extract data. Then find a program to open ext4 file (e.g. Ext2Read), extract the data and make a flashable zip.

zxz0O0 said:
Another method is: extract system.sin with WinRar from the ftf file. Open flashtool => Tools => Sin Editor => Extract data. Then find a program to open ext4 file (e.g. Ext2Read), extract the data and make a flashable zip.
Click to expand...
Click to collapse
This is exactly what i'm doing atm and then i'm starting from the beginning...

euronaut said:
This is exactly what i'm doing atm and then i'm starting from the beginning...
Click to expand...
Click to collapse
I think if your phone is rooted now it should be enough to continue from step 15 (and use the german ftf and flashable system zip).

after trying a lot of things, i didn't get a flashable zip . i took my sytems folder and meta-inf folder of the uk flashable zip and made my Firmware.zip with winrar, but got always errors during the flashing in dual recovery. after that i tried with the original uk.flashable.zip and everything went well. probably i'm not good in making flashable zips . is there any trick? my flashable zip is 1.5gb in size?!

Open the uk flashable zip with WinRar and delete system.tgz (right click => Delete file). Then rename your system.tar.gz to system.tgz and drag and drop it into the WinRar window.

zxz0O0 said:
Open the uk flashable zip with WinRar and delete system.tgz (right click => Delete file). Then rename your system.tar.gz to system.tgz and drag and drop it into the WinRar window.
Click to expand...
Click to collapse
Finally, everything flashed properly and seemed to work. But now it stucks at the sony logo direct after switching it on . So back to original FW

Did you follow these steps:
Flash your german ftf in flashmode (boot phone in flashmode again) (select Wipe [Uncheck ALL] and Exclude [Check SYSTEM]
Go to the Recovery Menu. To do that, power off your phone. Then power it on again. After the vibrate and the green LED turns on, hold Volume Up (LED will turn violet)
Now format /system (located under Mounts & Storage) (Important: Do NOT reboot until advised so or you will have to start again)
[*]Do a factory reset
Install the following files in this order (Important) (see steps 4 - 6)
flashable german system zip
Z1C-lockeddualrecovery(...)flashable.zip
UPDATE-SuperSU-v1.(...).zip
If you created the system.tar.gz yourself, it's possible that the files don't have the correct permissions. You can try fixing permission in Recovery Menu. Not sure if it really helps. If it doesn't work I advise you to flash the german firmware (+ factory reset) and try these steps again http://forum.xda-developers.com/showpost.php?p=50559502&postcount=9 (you will lose root though).

what i did and how i did was exactly in this order:
1. I flashed my german .142 FTF to have my stock rom back.
2. i extracted a system.tar.gz according to http://forum.xda-developers.com/showpost.php?p=50559502&postcount=9
3. renamed that to system.tgz and did
4.
zxz0O0 said:
Open the uk flashable zip with WinRar and delete system.tgz (right click => Delete file). Then rename your system.tar.gz to system.tgz and drag and drop it into the WinRar window.
Click to expand...
Click to collapse
5. then i followed step 8 - 14 of your guide http://forum.xda-developers.com/showthread.php?t=2642081 with NO errors
and did these steps:
zxz0O0 said:
Did you follow these steps:
Flash your german ftf in flashmode (boot phone in flashmode again) (select Wipe [Uncheck ALL] and Exclude [Check SYSTEM]
Go to the Recovery Menu. To do that, power off your phone. Then power it on again. After the vibrate and the green LED turns on, hold Volume Up (LED will turn violet)
Now format /system (located under Mounts & Storage) (Important: Do NOT reboot until advised so or you will have to start again)
[*]Do a factory reset
Install the following files in this order (Important) (see steps 4 - 6)
flashable german system zip
Z1C-lockeddualrecovery(...)flashable.zip
UPDATE-SuperSU-v1.(...).zip
If you created the system.tar.gz yourself, it's possible that the files don't have the correct permissions. You can try fixing permission in Recovery Menu. Not sure if it really helps. If it doesn't work I advise you to flash the german firmware (+ factory reset) and try these steps again http://forum.xda-developers.com/showpost.php?p=50559502&postcount=9 (you will lose root though).
Click to expand...
Click to collapse
exactly as you described them here
after like doin your guide 5 or 6 times i'm pretty fast with it
now i'm back on my .142 FTF (flashed via flashtool) unrooted

Hm, sorry I don't know what the problem is then. Maybe @Darkimmortal can help you since he created the uk flashable zip I think.

zxz0O0 said:
Try this (all steps in adb on computer):
adb push busybox /data/local/tmp
adb shell
cd /data/local/tmp
chmod 777 busybox
./busybox tar pczvf /storage/removable/sdcard1/system.tar.gz /system
Copy system.tar.gz from your sdcard to your computer.
Click to expand...
Click to collapse
I get an error during this step:
tar: error delayed from previous errors
Click to expand...
Click to collapse
before i got
tar: /System'/lost+found: permission denied
Click to expand...
Click to collapse
Any ideas?

[GUIDE][FAQ][KK] How to Root, Boot Unlock & More

////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
FAQ
////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
MOTOROLA PATCHED THE FAKEID, FUTEX & TRUST ZONE EXPLOITS ON THE 182/183.46.15 RAZR M FIRMWARE & THE .10 MOTO LUGE FIRMWARE.
AS OF NOW, THERE IS NO KNOWN BOOTLOADER UNLOCK EXPLOIT FOR THE 182 / 183.46.15 RAZR M FIRMWARE OR THE .10 MOTO LUGE FIRMWARE.
----------------------------------------------------------------------------------
IMPORTANT
----------------------------------------------------------------------------------
If your device is on stock Jelly Bean 4.1.2 firmware, you have the JB Bootloader (JBBL) - If your device is on stock KitKat 4.4.2 firmware, you have the KK Bootloader (KKBL)
Once your bootloader is unlocked, it can not be re-locked - Say goodbye to any warranties you may have.
Once your bootloader is unlocked, you can accept any and all firmware updates.
Once your bootloader is unlocked, you can flash any and all Razr M / Moto Luge firmware.
In order to receive and install System Updates you will need to be using 100% stock untouched firmware. (Stock system & recovery)
You can not downgrade with a locked bootloader. You can only flash current or updated firmware.
-----------------------------------------------------------------------------------
UNLOCKING THE BOOTLOADER ALLOWS YOU TO
-----------------------------------------------------------------------------------
Use a custom recovery and make NANDroid back-ups.
Root your device by flashing Superuser through a custom recovery. - No exploits needed
Deodexed your system and use custom themes/mods.
Use custom ROMs/Firmware..
Downgrade firmware.
Use custom kernels.
Move updated system apps back to the system partition which saves user space.
Use and modify your device anyway you want.
////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
REQUIREMENTS
////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
Motorola Device Manager installed [DOWNLOAD] - This insures that you have all the proper drivers installed
Stock KitKat firmware
Windows PC or Laptop
OEM USB cable
USB 2.0 port
////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
EXTRAS
////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
----------------------------------------------------------------------------------
MFASTBOOT SETUP
----------------------------------------------------------------------------------
For easy use
Windows Set-Up
Mfastboot does work with both Linux & Mac
Download Mfastboot [MIRROR]
Extract contents into a folder and place it into your Local Disk (C
Code:
[COLOR="Red"]Example[/COLOR] - [I]C:/ANDROID/Mfastboot[/I]
Open start menu and type CMD
Right click on CMD > select copy
Paste into Mfastboot folder
Finished
----------------------------------------------------------------------------------
BOOTING OPTIONS
----------------------------------------------------------------------------------
Once rooted, you can use a app like Quick Boot to perform these actions.
Reboot
Code:
Power + Volume Down
Reboot AP Fastboot
Code:
During [COLOR="Blue"]Reboot[/COLOR] > press and hold Volume Down
Reboot Recovery
Code:
During [COLOR="blue"]Reboot[/COLOR] > press and hold Volume Up
Bootloader Menu
Code:
During [COLOR="blue"]Reboot[/COLOR] > press and hold Volume Up + Down
----------------------------------------------------------------------------------
DEBLOAT LIST
----------------------------------------------------------------------------------
MUST HAVE ROOT
These apps (APK/ODEX) are safe to delete, freeze or rename.
SYSTEM > APP
Code:
3c_main.apk
Amazon_Audible.apk
Amazon_IMDb.apk
Amazon_Mobile.apk
Amazon_mp3.apk
Amazon_zappos.apk
Amazon_Zipaligned.apk
atfwd.apk (Wireless Display - Razr M/HD doesn't support wireless display)
BasicDreams.apk
Books.apk
Bug2GoStub.apk
com.gotv.nflgamecenter.us.lite.apk
com.motorola.android.nativedropboxagent.apk
com.motorola.android.settings.diag_mdlog.apk
Facebook.apk
FaceLock.apk
FastDormancy.apk (CDMA, unsure about GSM)
Galaxy4.apk
GoogleEars.apk
GoogleEarth.apk
GooglePinyinIme.apk
HoloSpiralWallpaper.apk
HotspotLauncher.apk
HPLegacyPlugin.apk
Kindle.apk
LiveWallpapers.apk
Magazines.apk
MagicSmokeWallpapers.apk
ModemStatsService.apk
MotionTrigger.apk (SmartActions Requirement)
MotVzwLocationService.apk
PhaseBeam.apk
PlayGames.apk
PlusOne.apk
ProgramMenu.apk
ProgramMenuSystem.apk
Protips.apk
Quickoffice.apk (Abandon by Google)
SlackerRadio.apk
Street.apk
Videos.apk
VisualizationWallpapers.apk
VMwareReady.apk (Corprate Crapware)
VSuiteApp.apk
vznavigator.apk
VZWAPNLib.apk
vzwapnpermission.apk
VZWAPNService.apk
VzwSystemUiExt.apk
YouTube.apk
Zap.apk
SYSTEM > PRIV-APP
Code:
3c_checkin.apk
3c_devicemanagement.apk
3c_notification.apk
3c_ota.apk
3c_sso.apk
Amazon_Appstore.apk
android-syncservice-app.apk
cce.apk
CircleWidget3D.apk
Cmas.apk
DemoMode.apk
Favorites.apk
FileManager.apk
GuideMe.apk
HomeConfig.apk ([COLOR="Red"]Need a Home Launcher installed before removing[/COLOR])
Homescreen.apk ([COLOR="Red"]Need a Home Launcher installed before removing[/COLOR])
IlsVzW.apk
LMIRescueSecurity.apk
LocalWipePolicyManager.apk
MotoCare.apk
MotoCareInt.apk
MotoDockHelperService.apk
MotoEmail.apk
NotificationTutorial.apk
QuickView.apk (Homescreen notification badge handler)
Setup.apk
SetupWizard.apk
SmartActionFW.apk
SmartActionMFW.apk
SmartActions.apk
SmartCarDock.apk
SmartDock.apk
VerizonSSOEngine.apk (Needed for MyVerizon data widget)
Vvm.apk
VzwCbsLoader.apk
VzwController.apk
VzwDeviceSetup.apk
VzwEntitlementService.apk
VZWPackageInstaller.apk
vzwPhoneExt.apk
VzwPhoneService.apk
VzwSecureSettings.apk
VzwSettingsExt.apk
Weather.apk (Needed by CircleWidget3D)
WapPushSI.apk
----------------------------------------------------------------------------------
MOTOROLA FIRMWARE LINKS
----------------------------------------------------------------------------------
> http://www.drdevs.com/devs/FXZ-files/
> http://drdevs.com/devs/FXZ-files/XT907 (Droid RAZR M)/
> http://motofirmware.center/files/category/24-scorpionmini-all-variants/
----------------------------------------------------------------------------------
EFS BACK-UP & RESTORE - USE THIS NOW!
----------------------------------------------------------------------------------
- Thanks to @rahimali > http://goo.gl/IJuE9v
> Advanced backup and restore utility of your device's sensitive partition and NV data. - Created by lyriquidperfection
FEATURES:
Automatic detection and termination of SAMSUNG Kies application and ADB server instances on startup.
Backup and restore partition images to and from compressed archives (*.tar.gz format).
Detects backup archives automatically on the device and PC for hassle free restoring.
Device Filter support to help users identify which partitions are the important ones to backup.
Extract and read device's PIT file to ensure efficient and accurate backup and restore operations (Samsung devices only).
Check MD5 hash during backup and restore operations to verify integrity of data written.
Option to Format EFS to wipe all data and recreate partition.
Options to reset Battery Cable, SPen and Earphone Jack counters on supported Samsung devices.
Option to fix Samsung devices that are 'stuck' in Factory Mode with the on screen overlay.
Option to fix Samsung devices that have Lock Screen issues and missing Power Button Menu.
A full featured AT and QCDM Terminal for sending custom commands and/or bytes to the connected device.
Qualcomm device support allowing many new features such as backup and restore of the FULL NV Item range.
Generate ESN / MEID / IMEI in reversed HEX format for Qualcomm repair operations.
Read and write ESN / MEID / IMEI to and from Qualcomm devices and QPST 'QCN Backup' files.
Send Diagnostic Password (16 Digits Hex) to unlock secure operations.
Read / write / send SPC (Service Programming Code) on Qualcomm devices.
Read / write Lock Code on Qualcomm devices.
Skip NV items during backup based on a defined profile list to enable FULL backups.
Ability to backup a custom NV item range based on a user defined list.
Automatic detection and switching of USB settings when launching Qualcomm NV Tools.
Option to display various device, ROM and BusyBox related information at the click of a button.
Option to restore NV data from internal '*.bak' files if they exist to fix corrupt or incorrect IMEI number.
Option to repair NV data file ownership to fix 'Unknown baseband' and 'No signal' issues.
Supports backup and restore of 'fsg', 'fsc', 'backup' and other partitions that do not have a corresponding filename defined in the PIT file.
Enable / Disable 'HiddenMenu' on newer devices.
Launch PhoneUtil, UltraCfg and other built in hidden device menus straight from the application UI.
THREAD / DOWNLOAD:
> http://forum.xda-developers.com/gal...ol-updated-09-06-14-efs-professional-t1308546
////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
GUIDES
////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
----------------------------------------------------------------------------------
1a. ROOT - Locked Bootloaders
----------------------------------------------------------------------------------
-------------------------------------------------------------
HYDROGEN PEROXIDE ROOT:
-------------------------------------------------------------
For locked bootloaders with a kernel build date after June 3, 2014
Code:
[B][I]Settings > About phone > Kernel version[/I][/B]
Created by HydrogenXS & SERG_GANGUBAS
Based on Giefroot by zxz0O0 / Team Keen
Video Tutorial and Instructions by @sd_shadow > http://forum.xda-developers.com/droid-razr-m/general/root-droid-razr-m-xt907-183-46-15-t3137351
EXPLOIT SOURCES > http://forum.xda-developers.com/showpost.php?p=58916587&postcount=
ROOT THREAD > http://forum.xda-developers.com/droid-razr-m/general/root-droid-razr-m-xt907-183-46-15-t3137351 - sd_shadow's root thread.
-------------------------------------------------------------
TOWEL ROOT:
-------------------------------------------------------------
For locked bootloaders with a kernel build date before June 3, 2014
Code:
[B][I]Settings > About phone > Kernel version[/I][/B]
Download Towel Root [XDA] [WEBSITE]
Place on external SDcard
Install and run Towel Root
Follow any in-app prompts
Reboot
PROFIT!
----------------------------------------------------------------------------------
1b. ROOT - Unlocked Bootloaders
----------------------------------------------------------------------------------
Download and install a custom recovery (Instructions listed below - #3)
Download a Superuser flashable zip [SuperSU] [CWM Superuser]
Place on external SDcard
Enter Recovery
Flash Superuser.zip
Reboot
PROFIT!
----------------------------------------------------------------------------------
2. BOOTLOADER UNLOCKING
----------------------------------------------------------------------------------
KITKAT 182/183.46.10 FIRMWARE ONLY.
WILL NOT WORK ON THE 182/183.46.15 RAZR M FIRMWARE OR THE MOTO LUGE.
> Unlockable Firmware - forum.xda-developers.com/showpost.php?p=57339009&postcount=2
--------------------------------------------
APK
--------------------------------------------
Download Towel Root [XDA] [WEBSITE] - Disregard if you have previously rooted using Towel Root
Download Motopocalypse [WEBSITE] [DOWNLOAD]
Place both on external SDcard
Install and run Towel Root
Follow any in-app prompts
Reboot
Install and run Motopocalypse
Follow any in-app prompts
Reboot
PROFIT!
--------------------------------------------
DESKTOP / PC
--------------------------------------------
Head to djrbliss' (Dan Rosenburg) website to read the instructions and download.
> http://vulnfactory.org/blog/2013/04/08/motorola-bootloader-unlocking/
If successful, you will see the Unlocked Bootloader Warning when you reboot your device
{
"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"
}
After unlocking your bootloader, you may want to remove the "Unlocked BootLoader Warning" screen (Image above).
You can do this by flashing a boot logo. Head to the link below to choose and flash either the stock or a custom boot logo.
Custom Boot Logos > http://forum.xda-developers.com/droid-razr-m/themes-apps/themes-custom-boot-logos-t2824690
----------------------------------------------------------------------------------
3. CUSTOM RECOVERY
----------------------------------------------------------------------------------
MUST HAVE A UNLOCKED BOOTLOADER
Custom recoveries built and provided by dhacker29 & nobe1976
Download your choice of custom recovery, then proceed to installation.
[TWRP - XDA] [TWRP - DHACKER29][TWRP - DROIDRZR] [CWM - XDA]
[DOWNLOAD (MIRROR)]
XT907 KitKat compatible recoveries
TWRP
Code:
- TWRP - 2.7.1.0.img
- TWRP - 2.8.0.0.img
- TWRP - 2.8.1.0.img
- TWRP - 2.8.2.0.img
- TWRP - 2.8.3.0.img
CWM
Code:
- CWM - 6.0.4.9.img
-------------------------------------------------------------------------------------
INSTALLATION
-------------------------------------------------------------------------------------
-------------------------------
OPTION 1
-------------------------------
MUST HAVE A UNLOCKED BOOTLOADER
Download Mfastboot [MIRROR] - Refer to Mfastboot setup
Place recovery.img into mfastboot folder
Open CMD and [TYPE]
Replace >recovery-name< with the name of the recovery you downloaded. You my re-name the recovery.img to whatever you prefer. I re-named it to TWRPKK.img
Code:
mfastboot flash recovery [COLOR="Red"]>recovery-name<[/COLOR].img
Tap [ENTER]
When finished [TYPE]
Code:
mfastboot reboot
When you tap [ENTER] press and hold Volume Up (+) on your device until the phone boots into recovery to verify installation was successful
DONE!
-------------------------------
OPTION 2
-------------------------------
MUST HAVE A UNLOCKED BOOTLOADER
MUST HAVE ROOT
Download recovery
Place on external SD card
Download and install [Flashify] or [Rashr]
Follow in-app prompts
PROFIT!
----------------------------------------------------------------------------------
RECOVERY NOT WORKING?
----------------------------------------------------------------------------------
MUST HAVE ROOT
If the custom recovery isn't sticking, you will need to re-name recovery-from-boot.p
-------------------------------
OPTION 1
-------------------------------
Using a root explorer navigate to
Code:
/system/recovery-from-boot.p
Rename it to
Code:
recovery-from-boot.p[COLOR="RoyalBlue"].bak[/COLOR]
Reboot
Re-flash custom recovery
PROFIT!
-------------------------------
OPTION 2
-------------------------------
Manually in adb shell or Terminal Emulator
Open command prompt and [TYPE]
Code:
su
Tap [ENTER] then [TYPE]
Code:
mv /system/recovery-from-boot.p /system/recovery-from-boot.p.bak
Reboot
Re-flash custom recovery
PROFIT!
----------------------------------------------------------------------------------
4. RESTORING / UPGRADING STOCK FIRMWARE
----------------------------------------------------------------------------------
If you are having difficulties with RSD Lite, Please try one of these two programs.
Both are alternatives to RSD Lite.
House of Moto
http://www.droidrzr.com/index.php/topic/28162-house-of-moto-32/
RSD Flasher
http://www.droidrzr.com/index.php/topic/48904-rsd-flasher-beta-windows-only/
> If upgrading - be sure to flash the KDA20.62-10.1 firmware, so you could unlock your bootloader.
-------------------------------
OPTION 1
-------------------------------
Restoring/Upgrading with RSD Lite
Download current or updated firmware
[Moto Firmware Link #1]
[Moto Firmware Link #2]
[Alternative Download (4.4.2 KDA20.62-10.1)] - Thanks to @rahimali
Download RSD Lite [MIRROR] [GOOGLE]
Install and run RSD Lite
Boot Device into AP Fastboot - Refer to Booting Options
Connect your device via OEM USB cable in a USB 2.0 port
Select the [3 dot button] [...]
Navigate and select the downloaded firmware zip and click [OPEN].
Select [Decompress And Start Flashing].
When finished, reboot.
DONE!
-------------------------------
OPTION 2
-------------------------------
DO NOT UPGRADE WITH MFASTBOOT
Restoring with Mfastboot
Download current firmware [DOWNLOAD]
Download Mfastboot [MIRROR] - Refer to Mfastboot setup
Open the zip and extract these files to your Mfastboot folder
Code:
NON-HLOS.bin
system.img
boot.img
recovery.img [COLOR="Red"](OPTIONAL)[/COLOR]
Boot your device into AP Fastboot - Refer to Boot Options
Connect your device with the OEM USB cable in a USB 2.0 port
Open CMD and [TYPE]
Code:
mfastboot flash modem NON-HLOS.bin
Tap [ENTER]
When finished [TYPE]
Code:
mfastboot erase modemst1
Tap [ENTER]
When finished [TYPE]
Code:
mfastboot erase modemst2
Tap [ENTER]
When finished [TYPE]
Code:
mfastboot flash system system.img
Tap [ENTER]
When finished [TYPE]
Code:
mfastboot flash boot boot.img
Tap [ENTER]
When finished [TYPE] (OPTIONAL)
Code:
mfastboot flash recovery recovery.img
Tap [ENTER]
When finished [TYPE]
Code:
fastboot erase cache
Tap [ENTER]
When finished [TYPE] (OPTIONAL)
Code:
fastboot erase userdata
Tap [ENTER]
When finished [TYPE]
Code:
mfastboot reboot
Tap [ENTER]
PROFIT!
----------------------------------------------------------------------------------
5. DEODEXING
----------------------------------------------------------------------------------
MUST HAVE A UNLOCKED BOOTLOADER
MUST HAVE CUSTOM RECOVERY
Deodexing is basically repackaging of these APKs in a certain way, such that they are reassembled into classes.dex files. By doing that, all pieces of an application package are put together back in one place, thus eliminating the worry of a modified APK conflicting with some separate odexed parts.
So, Deodexed ROMs (or APKs) have all their application packages put back together in one place, allowing for easy modification such as theming. Since no pieces of code are coming from any external location, custom ROMs or APKs are always deodexed to ensure integrity. - R_a_z_v_a_n
--------------------------------------------------
DOWNLOAD - KitKat_Deodexer
--------------------------------------------------
Extract the contents of the Kitkat_Deodexer.rar to your PC
Plug in your device
Ensure that USB debugging is enabled
Code:
Settings > Developer options > USB debugging
Dont see developer options?
Code:
Settings > About phone > Tap "Build number" 7 times
Run main.bat
[TYPE 1] and tap [ENTER] - to create a working directory
[TYPE 2] and tap [ENTER] - to pull the System files for deodexing
When finished, [TYPE 3] and tap [ENTER] - to start deodexing
When finished, [TYPE 4] and tap [ENTER] - to create a flashable zip
Move [deodex_install.zip] to your external SD card
Unplug your device
Enter Recovery
Flash [deodex_install.zip]
Reboot
PROFIT!
----------------------------------------------------------------------------------
6. VZW HOTSPOT / WIRELESS TETHER HACK
----------------------------------------------------------------------------------
MUST HAVE ROOT
Thanks to Topsnake for the Mod [THREAD]
-----------------------------
STEP 1
-----------------------------
Using any [ROOT EXPLORER]
Navigate to
Code:
/ system / priv-app
Look for and delete (or rename)
Code:
VzwEntitlementService.apk
VZWEntitlementService.odex
Continue to step 2
-----------------------------
STEP 2
-----------------------------
Using a Root Explorer or Build.Prop editor
Navigate to
Code:
/ system / Build.Prop
Open in text editor and add to the bottom
Code:
ro.mot.tether_dun_required=0
ro.tether.denied=false
net.tethering.noprovisioning=true
Save and close
Reboot
PROFIT!
----------------------------------------------------------------------------------
7. DISABLING THE OTA POP-UP
----------------------------------------------------------------------------------
MUST HAVE ROOT
Using any [ROOT EXPLORER]
Navigate to
Code:
/ system / priv-app
Delete or rename
Code:
3c_ota.apk
Reboot
PROFIT!
----------------------------------------------------------------------------------
8. STUCK IN AP FASTBOOT
----------------------------------------------------------------------------------
Motorola uses the command fb_mode_set to insure that your device will reboot into AP fastboot to avoid any problems while flashing firmware.
To clear this we need to do the following:
While in AP fastboot, connect your device to your PC
Open mfastboot then [TYPE]
Code:
fastboot oem fb_mode_clear
Tap [ENTER]
When finished [TYPE]
Code:
mfastboot reboot
Tap [ENTER]
PROFIT!
////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
LINKS
////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
[INDEX] Motorola Droid Razr M (2015)
[HELP THREAD][Motorola Droid Razr M] Ask ANY Question. Noob Friendly
Motorola Official Change Log
[How-To][Tutorial] Downgrade Kit Kat 4.4.2 to JB 4.1.2
[KK] Add external SD Card writing for all apps
[DUMP][DEV][xt907] 4.4.2 OTA Partition Dump
[WORKAROUND] Access hidden settings menus
[MOD][4.4.2] Native Tether Exploit for XT907 Build 183.46.10/ Build 182.46.10
[HowTo] [VZW XT907/926 RAZR M/HD] Unlock US GSM Carriers Using RadioComm
[THEMES] Custom Boot Logos
[INDEX] Motorola USB Drivers, RSD Lite, Firmware Links & More
Universal ADB Drivers
--------------------------------------------------------------------------------------------------------------------------------------------
Did I miss something? Do you want me to add something? Let me know so I can add it to the guide/FAQ.
[*]This thread has been designed to be viewed on a Desktop and in XDA's 2015 layout. (looks terrible in Tapatalk)
[*]Being a Recognized Themer here at XDA, I have a ad-free template. So the thread layout may look different to me then for you. So, if you need me to adjust something, please let me know.

Finally an up to date, very well written, easy to follow guide.... Thank you kindly for putting this together ATTACK
We cannot teach people anything; we can only help them discover it within themselves.

Guys i can't see my backuped stoch kitkat rom in phome memory i am using cwm that you recommended in your post pls help. Backup is saved somewhere more than 1gb is unavailable after backup pls help.
Sent from my XT907 using XDA Free mobile app

taimur272 said:
Guys i can't see my backuped stoch kitkat rom in phome memory i am using cwm that you recommended in your post pls help. Backup is saved somewhere more than 1gb is unavailable after backup pls help.
Sent from my XT907 using XDA Free mobile app
Click to expand...
Click to collapse
Code:
/sdcard/ClockworkMod/Backup
OR
Code:
/mnt/shell/emulated/0/ClockworkMod/Backup
OR
Code:
/storage/emulated/0/ClockworkMod/Backup

Can i change that directory ! Can someone tell me a best kernel for stock kitkat rom and also doeas anyone phpne gets heatup while on 3g umts.
Sent from my XT907 using XDA Free mobile app

taimur272 said:
Can i change that directory ! Can someone tell me a best kernel for stock kitkat rom and also doeas anyone phpne gets heatup while on 3g umts.
Sent from my XT907 using XDA Free mobile app
Click to expand...
Click to collapse
I use TWRP, so I have no idea if you can change the directory in CWM. I think there maybe a option to backup to sdcard1 or something like that, but again I don't use CWM.
There are no kernels for Stock firmware unless you downgrade and use CM11_jbbl ROM. The heat issue has been reported multiple times, I dont have any heat issues but others do. You could try and disable FastDormancy.apk/odex. I read that it helps, but IDK.

My phone heated up with too many radios running at once service locations was the main beast but disabling allot of its permissions fixed that I have also noticed high battery loss when my phone is searching between 3g/4g ect which also penalty meant heat....
Sent from my XT907 using XDA Free mobile app

My phones heatups when i use 3g(signal 2 bars) on my phone and facebook simultaneously....... Can it be cpu that's heating up.... Can you tell me a good app to control cpu frequency and which supports dual core
Sent from my XT907 using XDA Free mobile app
---------- Post added at 09:37 PM ---------- Previous post was at 09:35 PM ----------
I also chanhed my stock kernel with recompiled kernel found in speaker popping thread it fixed my sound issue and also sleep issue
Sent from my XT907 using XDA Free mobile app

Can i update my device from the ota update
My device is unlucked but I decided to unroot my device
Any suggestions?
Sent from my XT907

What exactly is included in the update? Are there any features I will miss out on by not updating?
Sent from my XT907 using XDA Free mobile app

immadeofpixels27 said:
What exactly is included in the update? Are there any features I will miss out on by not updating?
Sent from my XT907 using XDA Free mobile app
Click to expand...
Click to collapse
No "new" features.
I'm still waiting on there official changelog, but what I do know is that they patched FakeID, Futex & TrustZone. Also SMS/MMS fixes.
Motorola official changelog > https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/87530/p/30,6720,8577

Rooted xt907, verizon pushing update
Hello,
I used the TowelRoot method on my XT907 a couple of months ago. Just wanted to get bloatware off, and add a couple of battery life apps.
It was successful, and I have enjoyed being rooted so far. However, saturday verizon tried to push an update, and I have rejected it the last couple of days. As i am unsure if i'm safe to accept this update. Also, since they have pushed this crap at me, my phone has been doing very weird things. It was completely fine before this. Now it blacks out randomly, and comes right back.
Anyhow, the question is should i unroot before accepting this update?
Thanks for any help, and sorry if i've posted in the wrong board.

centelred said:
Hello,
I used the TowelRoot method on my XT907 a couple of months ago. Just wanted to get bloatware off, and add a couple of battery life apps.
It was successful, and I have enjoyed being rooted so far. However, saturday verizon tried to push an update, and I have rejected it the last couple of days. As i am unsure if i'm safe to accept this update. Also, since they have pushed this crap at me, my phone has been doing very weird things. It was completely fine before this. Now it blacks out randomly, and comes right back.
Anyhow, the question is should i unroot before accepting this update?
Thanks for any help, and sorry if i've posted in the wrong board.
Click to expand...
Click to collapse
Unlock your boot loader before doing anything else ... If you have debloated you will probably have to use rsd to either flash directly to the update or to .10 then ota up to the update... But be sure to unlock your boot loader or it will be locked for good and there is not a way to root the update yet with out an unlocked boot loader...BTW mine has been doing this black out thing you describe after rejecting and deleting the update...
We cannot teach people anything; we can only help them discover it within themselves.

centelred said:
Hello,
I used the TowelRoot method on my XT907 a couple of months ago. Just wanted to get bloatware off, and add a couple of battery life apps.
It was successful, and I have enjoyed being rooted so far. However, saturday verizon tried to push an update, and I have rejected it the last couple of days. As i am unsure if i'm safe to accept this update. Also, since they have pushed this crap at me, my phone has been doing very weird things. It was completely fine before this. Now it blacks out randomly, and comes right back.
Anyhow, the question is should i unroot before accepting this update?
Thanks for any help, and sorry if i've posted in the wrong board.
Click to expand...
Click to collapse
Did you unlock your bootloader? If not I suggest you do so now before taking any update. If you update to 183.46.15 and do not have a unlocked bootloader you will NOT be able to root.
In order to update, you'll need to have a stock system (unaltered) and recovery. I would suggest you follow #4 option 2 to restore.
Or alternatively you could delete or rename this app to disable the OTA pop-up nag screen.
Code:
/ system / priv-app / [COLOR="Red"]3c_ota.apk[/COLOR]

Thanks for your help guys!! I'm not sure if i've unlocked the bootloader, but i'll do the research on how to do that. I just didn't want to accept the update, if it was going to cause further problems.

Hi!
Attack, I just want to say, absolutely fantastic and thorough thread! Covered anything and everything!
I just have one problem...towelroot says my phone is not supported!
xt907 running version 182.46.15. TR worked flawlessly on my razr HD, and since no one else had problems with it, I don't understand why I'm receiving this error! Any ideas? Thanks

xChowderrrx said:
Hi!
Attack, I just want to say, absolutely fantastic and thorough thread! Covered anything and everything!
I just have one problem...towelroot says my phone is not supported!
xt907 running version 182.46.15. TR worked flawlessly on my razr HD, and since no one else had problems with it, I don't understand why I'm receiving this error! Any ideas? Thanks
Click to expand...
Click to collapse
Moto patched the FakeID, Futex & TrustZone exploits on the .15 OTA. So unless your bootloader is unlocked, your stuck without root.

So I could use the FXZ and update to 183.46.10 and it should work?

xChowderrrx said:
So I could use the FXZ and update to 183.46.10 and it should work?
Click to expand...
Click to collapse
Is your bootloader unlocked?

ATTACK said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
No sir, I can't unlock until I root, correct? And Samurai's FXZ is for locked or unlocked razr M's. I could root and unlock once I get to that version (through RSD or HouseOfMoto), right?

The easiest way to get root and recovery on T2 ultra dual {5.1.1} {.182}

My this post may be considered as a sequel to my previous post about the easiest way to root t2 ultra dual {.472} {5.0.2}
Now the way to root our t2 ultra dual {5.1.1} {.182}:
Download the ftf file of latest firmware 19.4.A.0.182 (search on google)
Download latest version or V 0.8 of prf creator (search on google and get xda link)
Download SuperSU.zip (search on google)
Now put the prf creator somewhere in your PC (let's say on desktop) extract it there.
Add ftf file and superSU.zip in prf creator
Mark all the boxes on right side of prf creator window
Hit create. In 15-20 minutes you will get a zip file named "flashable" in prf folder
Copy this flashable zip and put it in root of SD card of your phone.
Now reboot your phone in recovery
after rebooting into recovery, follow in sequence:
Wipe
Advanced wipe
select:
cache
dalvik
system
data
internal memory
swipe to wipe
go back to recovery home
tap install
select external sd card
select that flashable zip
swipe to flash
wipe dalvik
reboot to system.
To install recovery:
Download latest nut's xzdr installer zip
Put it somewhere in your computer
Extract it, you will get a folder of same name
Connect your phone to pc in USB debugging mode
Open the extracted folder
Double click the windows installer batch file
Grant superuser access on your phone's screen
Follow the instructions on terminal
(press 1 on your pc as you have SuperSU in your phone)
After successful instalation of recovery, your phone will reboot into recovery.
Reboot the phone into system
.
.
Now you have a rooted 5.1.1 D5322 with latest Dual recovery.

This is not even close to simple dude..
This is what i did to root :
1. Copy SuperSU to sdcard
2. Flash DUAL_RECOVERY_D5322-LP.img
3. Install supersu then power off
4. Open flashtool and Flash STOCK KERNEL 5.1.1 ONLY KERNEL
5. REBOOT & VIOLA

there are few additions required for noob like me
To make work this method
Requirement :
Rooted D5322 with 4.x.x or 5.0.1 & working recovery installed.
To install recovery:
make sure that you have :
Enabled USB debugging
Enabled Unknown sources

r2rdcroix said:
This is not even close to simple dude..
This is what i did to root :
1. Copy SuperSU to sdcard
2. Flash DUAL_RECOVERY_D5322-LP.img
3. Install supersu then power off
4. Open flashtool and Flash STOCK KERNEL 5.1.1 ONLY KERNEL
5. REBOOT & VIOLA
Click to expand...
Click to collapse
When you tick all the boxes in prf creator, kernel gets added.
Sent from my D5322 using XDA Forums Pro.

rrd84 said:
there are few additions required for noob like me
To make work this method
Requirement :
Rooted D5322 with 4.x.x or 5.0.1 & working recovery installed.
To install recovery:
make sure that you have :
Enabled USB debugging
Enabled Unknown sources
Click to expand...
Click to collapse
Yeah I already said it's a sequel to my first post. In which you would see how to root D5322 on 5.0.2, and ofcourse recovery is needed. Thanks.
Sent from my D5322 using XDA Forums Pro.

Good work. But we know that this is not really easy. hehe

dropdan said:
Good work. But we know that this is not really easy. hehe
Click to expand...
Click to collapse
yeah!

Does this root 5.1.1 by 100%? Can we install Modded Play Store by this root method?

Need step by Step instructions please
Hello
I am a novice with many of the tools listed & the steps outlined, can somebody please help with step by step instructions,
maybe email me [email protected]
:good:

Thanks. For my XPERIA T2 ULTRA DUAL I had to made a change:
Instead of using the Recovery-Software you (rituraj_singh) offered I had to use the software (TWRP) recommended b abcdjdj in his post from 27th May 2014 ((D5322) Dual Recovery) on the XDA-Forum.
For the not-experienced Users of Androxyde Xperia Flash Tool: You can use the XperiFirm-Software (XI-Button in the Flash-Tool) and install the 5.0.1 (19.3.A.0.472)-Firmware from MELA Latin, but you have to overwrite also the Userdata and the Apps-Log, otherwise there are problems. After flashing use KingRoot to root your device, than replace kinguser using the batch-script of w0lfdroid.com (May 2015) placing the mrw-folder (included in the downloaded zip) on the intern memory (important) and executing it with Terminal Emulator. Than open SuperSu (installed by the script, not by you), and actualize the root-script. Afterwards reboot.
A Tip: After having installed the TWRP-Software on your phone you could have problems rebooting into the system, so prepare all and after having flashed the custom prf-rom on the device all would be function!

A step-by-step-Version (summary)
sachin.sachania said:
Hello
I am a novice with many of the tools listed & the steps outlined, can somebody please help with step by step instructions,
maybe email me [email protected]
:good:
Click to expand...
Click to collapse
Here comes a step-by-step-Version (summary) of all the "Posts"s needed for rooting Lollipop 5.1.1 on your Sony Xperia T2 Ultra (Dual).
The copyright is by the "Post"-authors like rituraj_singh and abcdjdj (I took the links to the posts nearby the description of the step) and by w0lfdroid.com, xperiafirmware.com and the software-producers.
I only wanted to create a step-by-step-summary. There is no garantuee which garantuees success using the summery! No responsability dad it does not destroy your mobilephone. Use it at your own risk! Thank you to the original "owners" of the posts. I hope the summary is ok for them! Otherwise contact me.
Time: maybe 1 hour or 2 hours
Tipp: if you until yet did not install Android 5.1.1 on your Xperia T2 Ultra Dual you do not have to follow the steps which are describing how to download the older Firmware via XperiFirm, but you should have installed the FlashTool just for the drivers (You won't use it directly). You can use the steps describing how to root the older Firmware using KingRoot, than continue with step 7.
1) Install the Androxyde FlashTool on your Computer: http://www.flashtool.net/downloads.php or found on the XDA-Forum, install the ADB-Packages (ADB, ADB-Drivers) on your Computer and make the ADB-Command part of the "path"-Variable of your Computers Terminal (see Google)
2) Install XperiFirm (cause easy for beginners): open the FlashTool and click on the "XF-button" near the "plus-in-a-square"-button and the "flash"-button.
3) After having installed the XperiFirm-Tool open it and click on "Xperia T2 Ultra (tianchi)" and select "D5322/XM50H (dual)"
4) Than click on the "Check-All"-Button over the Line "Latest Release"
5) Click on "MENA Latin" in the "Market"-Line and than on the "19.3.A.0.472 / R3C" and download it (having activated "unpack automatically")
6) Go to "xperiafirmware.com/8-firmware/58-sony-xperia-t2-ultra-dual-d5322" and download it (see chapter "1." on the website ), but do not flash it
7) Download the newest PRF-Creator (ZIP) from the following XDA-Forum-Link and unzip it: http://forum.xda-developers.com/crossdevice-dev/sony/tool-prfcreator-easily-create-pre-t2859904
8) Download the newest SuperSU-ZIP from chainfire (https://download.chainfire.eu/696/SuperSU). and paste the ZIP in the unzipped PRF-Creator-folder: https://download.chainfire.eu/696/SuperSU
9) Now copy the .ftf-file (Firmware) downloaded from xperiafirmware.com also in the unzipped PRF-Creator-folder and open the PRF-Creator.exe
10) The PRF-Creator asks for the .TFT-File (select the one you downloaded from xperiafirmware.com) and for the SuperSU-ZIP-File (select the one downloaded from chainfire)
11) Select in the "Include"-field: "Kernel"; "FOTA-Kernel"; "Modem" and "LTALable", also "Sign ZIP" and "Legacy Mode"
12) Click create and wait until finished
13) Copy the created "flashable-prerooted.zip" from your unzipped PRF-Creator-Folder to the external SD-Card of your Device
14) BackUp your mobilephone using the "Sony PC Companion" or simular software like Wondershare's "MobileGo"
14a) Control if you have unlocked your Boatloader (normally it's locked) and if it's locked, go to the "Sony Mobile Developers Unlock Bootloader Website" and follow the instructions there Important: You could have to install ADB and Sony's ADB-Drivers (find ADB using google) and the Sony FlashTool "Emma" will not work with the Xperia T2 Ultra Dual
15) Shut down your phone and start it holding the "Volume-down"-Button while plugging in the USB-Cable (it won't show more than a black screen)
16) Close "XperiFirm", wait until it finished and then click on the "Flash"-Button and select in the new window "Flashmode" and "OK" (obviously)
17) Select the Firmware you downloaded before with XperiFirm (19.3.A.0.472) and select in the "Wipe"-Field: "APPS_LOG" and "USERDATA" (!!!important!!! otherwise problems)
18) Click on the "Flash"-Button and wait until it's done (sometimes the flashtool has problems with the files - dont worry: shutdown the FlashTool and retry it once more)
19) Unplug the mobilephone from the USB-Cable, start it and follow the instructions
20) After having prepared the mobilephone go to "kingroot.net/wap/download" and download KingRoot (sometime trouble with the site, try it once more)
21) Afterwards enable the DeveloperMode (settings - About Phone - click "build number" 7 times) and enable the "unknown sources" (settings - Security - unknown sources)
22) Install KingRoot and root your Xperia T2 Ultra Dual
23) Install "Terminal Emulator" from the Google Play-Appstore to your device and open it
24) Go to "http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html" and download the newest "Replace KingUser with SuperSU.zip" and unpack it to your device's intern memory (!!!important!!! otherwise no function)
25) In the Terminal Emulator App enter "su" for gaining "root"-access ("Enter" obviously), than enter "sh /sdcard/mrw/root.sh" and wait until it finish (it will open SuperSU)
26) Actualize the file as requested by SuperSU and, after having had success, reboot your mobilephone
27) Install a Root-Checker-App from Google Play Store and control, if you see a window from "SuperSU", otherwise repeat the last steps
28) Go to "https://goo.gl/lg6I2t" or visit directly the XDA-Forum-Post of abcdjdj (http://forum.xda-developers.com/showthread.php?t=2764408) and download his "TWRP-KK-T2_DUAL-V3.img" or newer
29) Shut down your mobilephone. Afterwards hold the "Volume-Up"-Button while plugging in the USB-Cable (it shows only a black screen) and connect it to the Computer
30) Check if you have installed all fastboot drivers for your device, then open the "Command Line" of your Computer "as Administrator" and enter: "fastboot flash boot (path-to-the-file-downloaded-in-the-last-step)/TWRP-KK-T2_DUAL-V3.img" and click obviously "Enter"
31) Now unplug your mobilephone, than hold the "Volume-down"-Button and the "Power"-Button at the same time: TWRP-Recovery will start
32) Select "Wipe", than "Advanced Wipe", than select "intern. memory", "dalvik", "cache", "data" and "system"
33) Swipe to Wipe
34) Go to TWRP's home (twice times the "back"-Button) and select "Install", than "external SD-Card" and select "flashable-prerooted.zip" and confirm the warning, than SWIPE to INSTALL (flashing)
35) Wipe the Dalvik-Cache
36) Reboot into System and follow your mobilephone's instructions
37) Install a Root Checker App from Google Play Store and control if it's rooted, afterwards install the backup of your mobilephone made at the beginning
38) Install "Titanium Backup" and disinstall (after having done a backup of the app you want to delete) Apps you do not want
39) Install "Link-to-SD" from GooglePlay, prepare your external SD-Card with a partition manager (using your Computer) and copy all possible apps completly to the SD-Card

This works on T2 ULTRA D5306 Single SIM
theokon said:
Here comes a step-by-step-Version (summary) of all the "Posts"s needed for rooting Lollipop 5.1.1 on your Sony Xperia T2 Ultra (Dual).
Click to expand...
Click to collapse
Well my friend, first at all, this is a awsome guide, it really help me to load the 5.1.1 on my SP. I Must said that even if this looks
overwhelming at the begining, it's pretty easy to do it.
Just for the FeedBack, this method works in:
T2 Ultra D5306 Single SIM, TELCEL.
I use the US CUSTOM Stock ROM 5.1.1 ( 19.4.A.0.182 ), if ask for the FTF, look at the FTF MEGAPOST.
Thanks to @rituraj_singh for find this method and @theokon to make the Easy-Mode Guide.
This thread must being Sticky.
PS: You have to add one step: When you reboot after the Flash, it can take a while in start the smartphone, It is to prevent panic if they see it takes a lot time to start, they might think it is bricked and try to restart it. :good:

This works great for rooting the phone (D5322) but for me link2sd doesn't read the 2nd partition and keeps giving me unable to mount errors.

virgilone2 said:
This works great for rooting the phone (D5322) but for me link2sd doesn't read the 2nd partition and keeps giving me unable to mount errors.
Click to expand...
Click to collapse
You got the error when you try to mount on /dev/block/mmcblk1p2 ? it and said that the mount fail?
I had that error as well, maybe you have to try this @virgilone2:
1.- Uninstall the Link2SD.
2.- Install the SD MAID and run it, clean it up.
3.- Reinstall the Link2SD.
4.- Install the Recovery (I use this) [ XZDualRecovery 2.8.21 ] or the same you use in the guide.
5.- Run the Recovery, and go to Wipe > Advance Wipe > Davik Cache, Swipe to Wipe, after it ends go to Reboot > System.
6.- Before your smartphone start as usual, going to pop one little window with a counter, wait to end (Maybe take a while).
7.-Run you Link2SD, it have to Mount the ext2 partition and ask for reboot, if isnt the case, just recreate the mount script.
8.- Enjoy your Link2SD in Lollipop 5.1.1 :good:
This works for me, i hope works for you as well

Windows 10 Driver Problems
When having updated to Windows 10 driver problems could happen.
When entering "fastboot devices" in your computer's terminal and nothinh happens it is like this.
You can solve this easily:
1) Plug in your phone in fastboot mode into the computer (Volume Up + Plug-In of the USB-cable)
2) Go to the"Devices manager" (or called simular, as I don't know how to translate it correctly), where you will find the unknown S1 fastboot driver.
3) Download the official Sony flashing tool "EMMA" and reinstall the "Android Studio" in order to get the correct drivers
4) For security download also the "Universal ADB Drivers Package" from chip.de and install it
5) Back in the Device Manager reinstall the correct driver selecting it from the drivers list (!): Sony SA0110 - ADB Interface driver

rituraj_singh said:
My this post may be considered as a sequel to my previous post about the easiest way to root t2 ultra dual {.472} {5.0.2}
Now the way to root our t2 ultra dual {5.1.1} {.182}:
Download the ftf file of latest firmware 19.4.A.0.182 (search on google)
Download latest version or V 0.8 of prf creator (search on google and get xda link)
Download SuperSU.zip (search on google)
Now put the prf creator somewhere in your PC (let's say on desktop) extract it there.
Add ftf file and superSU.zip in prf creator
Mark all the boxes on right side of prf creator window
Hit create. In 15-20 minutes you will get a zip file named "flashable" in prf folder
Copy this flashable zip and put it in root of SD card of your phone.
Now reboot your phone in recovery
after rebooting into recovery, follow in sequence:
Wipe
Advanced wipe
select:
cache
dalvik
system
data
internal memory
swipe to wipe
go back to recovery home
tap install
select external sd card
select that flashable zip
swipe to flash
wipe dalvik
reboot to system.
To install recovery:
Download latest nut's xzdr installer zip
Put it somewhere in your computer
Extract it, you will get a folder of same name
Connect your phone to pc in USB debugging mode
Open the extracted folder
Double click the windows installer batch file
Grant superuser access on your phone's screen
Follow the instructions on terminal
(press 1 on your pc as you have SuperSU in your phone)
After successful instalation of recovery, your phone will reboot into recovery.
Reboot the phone into system
.
.
Now you have a rooted 5.1.1 D5322 with latest Dual recovery.
Click to expand...
Click to collapse
worat guide i ever seen in xda !!
no links !!

manojkumar8552 said:
worat guide i ever seen in xda !!
no links !!
Click to expand...
Click to collapse
Well thanks!! Links needed to perform the steps suggested are everywhere in the realm of Internet. Uploading same thing again and again is waste of space,data and everything. Hope you understand.
Ftf can be downloaded through xperi-firm and recovery can be downloaded from nut's Xperia files website. SuperSU is already available in more than 1000 places on Internet. And prf creator is created by a certain developer which is already available on xda. So reposting his item might be considered as kinda theft/plagiarism. And this is already mentioned in this post that it's a sequel of previous post. So please do your own bit of work/home work before posting negative comments.
Sent from my D5322 using XDA Forums Pro.

I did My HW. and that Why i m Saying You.
My one Frnd dont get anything from this Thread.
He is just trying to ROot.And says what the hell is going on thRead.
People Are Not Expert That You Are.
so make little comfortable Thread plz.
Sent from my Moto G 2014 using Tapatalk

manojkumar8552 said:
I did My HW. and that Why i m Saying You.
My one Frnd dont get anything from this Thread.
He is just trying to ROot.And says what the hell is going on thRead.
People Are Not Expert That You Are.
so make little comfortable Thread plz.
Sent from my Moto G 2014 using Tapatalk
Click to expand...
Click to collapse
This post is a sequel of previous post. To perform the steps mentioned you need to be on earlier versions of Android. Like 5.0.2 or earlier. And recovery must be installed in that. If you're on 5.0.2 follow my post about how to root on 5.0.2.
Sent from my D5322 using XDA Forums Pro.

manojkumar8552 said:
I did My HW. and that Why i m Saying You.
My one Frnd dont get anything from this Thread.
He is just trying to ROot.And says what the hell is going on thRead.
People Are Not Expert That You Are.
so make little comfortable Thread plz.
Sent from my Moto G 2014 using Tapatalk
Click to expand...
Click to collapse
Well.. You can use KingRoot v 4.5.2*to root 5.1.1 and for SuperSU follow my previous post.
Sent from my D5322 using XDA Forums Pro.

[Q]Lost XZDualRecovery after Busybox installation, no way to get it[solved]

Hi to all, i tried to find several topics but nothing helped me so...i will ask your help..
As in description,i lost XZDualRecovery after Busybox installation but root still working(Supersu).
My phone details are the following:
CURRENT DEVICE : Xperia Z1 Compact LP 5.1.1
BOOTLOADER STATUS : Locked
ROM : Stock Prerooted 14.6.A.0.368 Customized CE1 by Davka
KERNEL : Stock
MOD: Fly-On Mod App Beta6 / Serajr Xposed / [APP] [Z/Z1/Z2/Z3] [V4] Xperia Camera Unlocked
I wanted use Fly-on mod App and as in the topic said, it's necessary use busybox to enable it, so i downloaded it from Google playstore and installed it. After rebooted my phone i lost the recovery and there isn't way to get it .
I tried to:
Uninstall busybox,reboot and follow these steps:
"Make sure you have USB debugging turned ON.
download Z1C-lockeddualrecovery[VERSION]-BETA.installer.zip from http://nut.xperia-files.com
Windows:
unpack at C: or somewhere you will remember!
navigate to the resulting directory and look for install.bat, double click it to run;
Your phone WILL reboot when installation has completed and it will go into the default recovery for the first boot.
Reboot to system from recovery to allow the installer to clean up after installation (it is safe to skip this step).
Enjoy DUAL RECOVERY!"
but every time during the installation i got this:
http://imgbox.com/gallery/edit/kFiAdgje39/NM7oyQXhsQ4pj1WT
and phone never rebooted..
I tried to use "Z1C-lockeddualrecovery2.8.22-RELEASE.installer" because in the topic said it hasn't any issue with Busybox "XZDualRecovery 2.8.22 and newer do not suffer from this dependency, you can use whatever busybox updater app you like when you have 2.8.22 or newer installed."
i attach my log file from /cache/recovery ->https://www.dropbox.com/s/y356yfungd0uzja/last_log?dl=0
P.S.
Root with Supersu is still working, i lost only recovery.
i appreciate that everybody can help me
Thanks in advance,
Alex

Looks like you don't have necessary files, which should be sent to the phone by the ADB. Or ADB couldn't find these files. Just check it in the folder with unpacked xzd installer.
---
Sony Xperia A2 SO-04F (Japan version of Z1 Compact)

iamdude said:
Looks like you don't have necessary files, which should be sent to the phone by the ADB. Or ADB couldn't find these files. Just check it in the folder with unpacked xzd installer.
---
Sony Xperia A2 SO-04F (Japan version of Z1 Compact)
Click to expand...
Click to collapse
thanks to reply me, inside xzd installer i have all file..but why i can't install recovery in my z1c?
http://imgbox.com/gallery/edit/eZFQIcnwip/KrU0dP9VQmiZtrE3
UPDATE:
my pc has always recognized my phone but to be sure, during installation of recovery, i tried to install again ADB driver and after that i chose point 1 and flashed recovery on Z1C SUCCESSFULLY!
My question is...why every time i flash Busybox i lost recovery? i flashed xzd 2.8.22 that should be bug free as said in that topic.. i confused...i would like try Fly-on mode appBeta 6...

Do you have ADB installed system-wide on your computer?
Install cmd should use ADB.exe from this folder, not from other location on your computer.
You could edit install recovery cmd and specify a full path to the adb.exe located in this folder.
For example, if these files is stored in c:\xzdrecovery\ folder, then full path to adb.exe will be a c:\xzdrecovery\adb.exe
---
Sony Xperia A2 SO-04F (Japan version of Z1 Compact)

iamdude said:
Do you have ADB installed system-wide on your computer?
Install cmd should use ADB.exe from this folder, not from other location on your computer.
You could edit install recovery cmd and specify a full path to the adb.exe located in this folder.
For example, if these files is stored in c:\xzdrecovery\ folder, then full path to adb.exe will be a c:\xzdrecovery\adb.exe
---
Sony Xperia A2 SO-04F (Japan version of Z1 Compact)
Click to expand...
Click to collapse
at first i disabled and enabled usb debug from phone and chose option n° 4,adb drivers on pc but it said me that my driver was just upgrated., after that it has been possible install recovery choosing option 1(because i have supersu).
i haven't any adb syistem installed on my pc, i only installed again adb driver and after that it. all was ok