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

[Galaxy Note2 TOOLKIT V4.1.0 TMOBILE] Drivers, Backup, Root, Recovery, Flash Stock

INTRODUCING THE SAMSUNG GALAXY NOTE2 TOOLKIT
GSM (GT-N7100) and LTE (GT-N7105) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=1923956
AUSTRALIAN GSM (GT-N7100T) and LTE (GT-N7105T) SUPPORTED. USE GSM THREAD
SPRINT (SPH-L900) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=1957155
TMOBILE (SGH-T889) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=1957720
MOBILICITY, VIDEOTRON, WIND [SGH-T889V] SUPPORTED. NO THREAD YET. USE TMOBILE THREAD
AT&T (SGH-L317) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=2052779
BELL, ROGERS, SASKTEL, TELUS [SGH-I317M] SUPPORTED. NO THREAD YET. USE AT&T THREAD
VERIZON ([SCH-I605]) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=2052788
US CELLULAR (SCH-R950) SUPPORTED. NO THREAD YET. USE ANY
KOREAN SK TELECOM [SHV-E250S] SUPPORTED. NO THREAD YET. USE ANY
NOTE: If you want a new build added to the Toolkit then download and install, Type 'A' in the Model Selection screen and follow the instructions.
HOW TO VIDEOS ARE ON POST#4 (THANKS TO WWJOSHDEW) MAKE SURE YOU HAVE A LOOK AT THEM AS A VIDEO IS WORTH A THOUSAND WORDS
FUNCTIONS OF SAMSUNG GALAXY NOTE2 TOOLKIT V4.1.0 [9TH APRIL 2013]
Install drivers automatically
Backup/Restore a single package or all apps, user data and Internal Storage
Backup your /data/media (virtual SD Card) to your PC for a Full Safe backup of data
Root any public build (different options)
Root with Superuser (ChainsDD) or SuperSU (Chainfire) via CWM (works on ANY build)
[*]Root+busybox+rename recovery restore files via Custom Recovery
[*]Unroot (delete root files and busybox)
[*]Many root/unroot options including adb, recovery and sideload via custom recovery
[*]Perform a FULL NANDROID Backup of your system via adb and save in Custom Recovery format on your PC
[*]Pull /data and /system folders, compress to a .tar file and save to your PC
[*]Auto Update ToolKit to latest push version on startup (donator feature)
[*]Dump selected Phone Partitions, compress to a .zip file with md5 and save to your PC
[*]Install BusyBox binary on phone
[*]Flash Stock Recovery
[*]Flash CWM Recovery (thanks to Clockworkmod Team) or TWRP Recovery (thanks to Team Win)
[*]Rename Recovery Restore files if present
[*]Flash Insecure Boot Image for adb mode
[*]Flash Stock Boot Image back to your phone
[*]Create tar file to flash via Odin (from upto 10 image files) with 1-click process
[*]Download, Extract and Flash Stock Rom (full DETAILED steps) ESSENTIAL FOR WARRANTY RETURNS
[*]Rip cache.img to zip file in CWM format for editing and flashing (thanks to Adam Lange)
[*]Install a single apk or multiple apk's to your phone (being worked on)
[*]Push Files from your PC to your phone
[*]Pull Files from your phone to your PC
[*]Set Files Permissions on your phone
[*]Dump selected LogCat buffers to your PC
[*]Dump BugReport to your PC (if installed)
[*]Help, Information Screen for various tasks
[*]Mods Section to Modify your phone (being worked on)
[*]Reboot Phone options in adb mode
[*]Change background, text colour in ToolKit
[*]Device Information screen which pulls info directly from device
[*]Activate Professional features from within the ToolKit
--------------------------------------------------------------
Mod edit: Download link removed
MD5 Sum for V4.1.0: 37360aabdf3869aad55d12dd2c2b0b07
NOTE: As the ToolKit.exe and ModsSection.exe files are not Digitally Signed with a Microsoft Certificate they 'may' get picked up as potentially harmful by Antivirus Programs and deleted on first run. If this happens restore the file and exclude it from future scans to use it. This seems to happen mostly on AVG Free and Norton which is why I switched to BitDefender which is much better.
IMPORTANT: ONLY FLASH ROMS THAT ARE SPECIFICALLY MADE FOR YOUR PHONES MODEL NUMBER AS FLASHING AN INCORRECT ROM CAN SOFT BRICK YOUR DEVICE!
Credits: ChainsDD for Superuser, Chainfire for SuperSU, Chenglu for modded cwm.
--------------------------------------------------------------
WHAT IS THE DIFFERENCE BETWEEN FREE (PUBLIC) AND DONATE (PROFESSIONAL) VERSIONS?
THE FREE PUBLIC VERSION OF THE TOOLKIT INCLUDES EVERYTHING YOU COULD POSSIBLY NEED TO MANIPULATE YOUR PHONE. NOTHING IS RESTRICTED. ACTIVATING THE DONATE VERSION WILL ADD THE ABILITY TO CHECK FOR UPDATES VIA THE TOOLKIT AND HAVE THEM PUSHED TO YOUR PC RIGHT AWAY AS SOON AS THEY ARE UPLOADED TO MY SERVER WITHOUT NEEDING TO DOWNLOAD THE WHOLE TOOLKIT EVERY TIME. THIS ALSO MEANS SMALLER UPDATES CAN BE SENT OUT MORE FREQUENTLY SUCH AS ADDING A SINGLE FUNCTION, FIXING A BUG OR ADDING COMPATIBILITY FOR A SINGLE VARIANT OR CARRIER SO DONATOR VERSIONS WILL BE UPDATED SOONER. IF YOU ARE NOT ABLE TO, OR DO NOT WANT THE AUTO UPDATE FEATURE THEN ALL UPDATES WILL BE COMPILED AND RELEASED TO THE XDA COMMUNITY AS A FULL DOWNLOAD VERSION AS SOON AS TIME ALLOWS AND THERE ARE ENOUGH UPDATES TO WARRANT IT. DONATORS WILL ALSO HAVE THE QUICK PICKS AND EXTRAS SECTIONS UNLOCKED AND THE 'NAG' SCREEN ON EXIT WILL BE DISABLED. NEW DONATOR FEATURES WILL ALSO BE ADDED TO THE TOOLKIT IN THE FUTURE.
AUTO REPLY LINKS FOR PAYPAL AND GOOGLE CHECKOUT TO GET A CODE INSTANTLY CAN BE FOUND AT http://goo.gl/nyGqv
AUTO UPDATES ARE BY FAR THE EASIEST WAY TO KEEP THE TOOLKITS UP TO DATE AS I HAVE LOTS OF OTHER TOOLKITS TO LOOK AFTER. IF ANYONE HAS ANY VIEWS ON THIS PLEASE PM ME OR CONTACT ME AT [email protected]. PLEASE DO NOT POST YOUR VIEWS IN THIS THREAD AS I WANT TO KEEP IT CLEAN FOR USER SUPPORT.
{
"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"
}
(Changelog at the Bottom of Post#1)
--------------------------------------------------------------
PLEASE READ THE *FAQ* IN POST#2 BEFORE ASKING QUESTIONS
--------------------------------------------------------------
1. INSTALLING GALAXY NOTE2 DRIVERS
The first thing you need to do is to install the drivers. These are needed so that you can communicate with the phone via the PC and perform the tasks that the ToolKit offers.
NOTE: If you have Kies installed then it is advisable to uninstall it first to avoid conflicts.
a. Make sure your phone is booted into Android and the USB cable is unplugged.
b. Select Option 1 in the ToolKit to install the Samsung USB Driver pack. This should install all the neccessary drivers you need.
C. While the drivers are installing make sure that USB Debugging is enabled on your phone via the Settings, Developer options Screen.
d. After the drivers have been installed connect the USB cable and the PC should detect the phone and install the correct drivers. This will also happen when you enter Download Mode and Recovery Mode for the first time.
e. If you want to check the drivers then go to your Control Panel on your PC and open the Device Manager. With the USB cable connected you should see a device listed as 'Samsung Android Phone' or something similar and a driver attached to it.
NOTE: If you are having trouble with your device being detected or the drivers installing correctly then you could try rebooting your phone, using a different usb port and making sure no other drivers are installed on your pc.
--------------------------------------------------------------
2. USING MSKIPS' SAMSUNG GALAXY NOTE2 TOOLKIT
a. Download the Samsung Galaxy Note2 ToolKit package and run to install the ToolKit to your PC. The installation will also create a Shortcut on your desktop for easy access. You have the option to include or exclude the drivers files at installation so if you already have your drivers set up and are just updating the ToolKit then you can untick the drivers if you wish.
b. Once the ToolKit is installed make sure your phone is booted and plugged in via USB cable and double click on the shortcut on your desktop to run it.
c. You will be asked if you want to check for an Update. If you type 'yes' this will download and check the latest version numbers against the versions in the ToolKit. If there is an update available then you will have the option to download and install it (professional feature).
d. You will now be presented with a Model Selection Screen to choose the Model/Build that you are currently on. Type the number that corresponds to your desired selection. For example type '12' for INTERNATIONAL GSM MODEL [GT-N7100] 4.1.1 [Build ALJ1-ALJ3]. If you cannot find the build your device is using then type 'h' to select the HELP option to get more info.
NOTE: If you have a new build that isnt covered by the Toolkit you can also type 'a' in the Model Selection screen to see instructions on how to pull your stock image and send it to [email protected] so support can be added.
e. The Toolkit will now locate and download the boot image pack for your chosen Model. This is a new feature so the Toolkit is not limited to how many Models can be added and it cuts down ALOT on the download size. After the zip file has finished downloading it will be extracted to the correct folders and the files checked to make sure everything is ok.
f. When you enter the Main Menu you will see 'Adb Mode' at the top. If you have installed your drivers correctly then you will see your devices serial number under the text with 'device' next to it. If you see this then your device is connected and you can carry on.
NOTE: If you haven't installed the drivers and don't see a serial number at the top then this is the FIRST thing you want to do so the Toolkit can operate properly.
g. Each option in the ToolKit has full information on what it is and how to use it.
--------------------------------------------------------------
3. FLASHING A ROM, RADIO OR KERNEL VIA CWM RECOVERY
a. Download your chosen Rom, Radio or Kernel from the Development Forum, then make sure your phone is booted up as normal and connect your usb cable so it goes into MTP Mode. Copy the .zip file (DO NOT UNZIP IT FIRST) to the 'Internal Storage' part on your phone. Do not copy it to a Sub Directory as it will be harder to find when flashing it.
b. Enter CWM Recovery (shut down the phone then hold down the 'HOME' + 'VOLUME UP' buttons and press the 'POWER' button for about 5 seconds).
c. Select 'Install zip from sdcard' and select 'choose zip from sdcard' if the file is on Internal Memory.
d. Scroll to your zip file and select. Then select 'Yes' in the list to start flashing.
e. When flashing is finished press the BACK Button to go back until you get to the Main Menu and then select 'reboot system now' to reboot your phone into Android.
--------------------------------------------------------------
4. FLASHING A ROM, RADIO OR KERNEL VIA DOWNLOAD MODE USING ODIN
Odin can be used to flash image files or parts of your phone. You can flash something as simple as a boot image or a complete system. Everything is packed in a tar or tar.md5 file on your PC and flashed via Odin which is a Windows OS program.
a. Make sure you have your tar file stored on your PC.
b. Reboot your phone to Download Mode [shut down your phone, then hold down the Home + Volume DOWN Buttons and press the Power Button for about 2 seconds until a Warning screen appears. Press Volume UP to continue to Download Mode.
c. Connect your phone via usb and the first box at the top under ID:COM should turn blue and have some text in it. If you are using Download Mode on your phone for the first time then you will notice drivers being installed to use it.
d. The site or page you downloaded the file from will usually give you instructions to set Odin but if not you want to load boot/recovery/system files to the PDA location and have 'Auto Reboot' and 'F.Reset Time' ticked and nothing else.
e. Click on 'Start' to start the flash. You can see what is happening in the text box in the lower left.
--------------------------------------------------------------
USEFUL INFORMATION
How to get into Recovery Mode
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME UP' buttons and press the 'POWER' button for about 5 seconds to enter Recovery Mode.
How to get into Download Mode (For Odin)
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME DOWN' buttons and press the 'POWER' button for about 2 seconds until a WARNING! Screen appears. Press the 'VOLUME UP' button to enter Download Mode.
--------------------------------------------------------------
ChangeLog
ToolKit v4.1.0 (9th April 2013)
+Updated complete Toolkit structure for easier support and faster updates
+Added GT-N7100T and GT-N7105T models to the support list
+Added 4.1.2 support for many models. See screenshot for full list
+Updated CWM and TWRP Recovery to the latest model specific version
+Added TWRP NAND backup/restore procedure to backups section
+Updated SuperSU Root procedure to V1.25
+Updated Samsung usb drivers to 1.5.18.0
+Added more error detection and updated many parts of the Toolkit procedures
+Added Activation option and support procedure for new builds to Model Screen
+Updated Stock firmware download section with new Samsung images
+Adb server is now shut down if you exit from Model Selection screen
+Added more error control Toolkit processes
+Updated mods section
ToolKit v3.0.0 (18th December 2012)
+Rewrote soo many parts its hard to list them all
+Changed the Model Selection screen
+Split up images for all supported models to make them easier to distinguish
+Added support for Verizon, GT-N7105 (lte), AT&T and Korean SK Telecom
+Added new options to Root/Unroot Screen
+Added root+busybox+rename recovery restore files via Custom Recovery
+Added Root/Unroot via Sideload feature in Recovery
+Updated CWM Recovery to 6.0.1.9
+Updated TWRP Recovery to 2.3.2.3 for all available Models
+Updated SuperSU to 0.99
+Added Device Information Screen
+Added instant reply donate link to Toolkit
+Soo many more behind the scene changes
ToolKit v2.0.0 (27th October 2012)
+Added FULL support for Sprint (SPH-L900)
+Added FULL support for TMobile (SGH-T889)
+Added FULL support for US Cellular (SCH-R950)
+Updated SuperSU Root zip file to V0.96
+Updated CWM Recovery to V6.0.1.5
+Added TWRP Recovery V2.3.1.1
+Added option on all Root procedures to root with Superuser (ChainsDD) or SuperSU (Chainfire)
+Added option in ALLINONE Root routine to flash cwm or twrp Recovery
+Improved Root procedure on all builds
+Made some edits for Toolkit stability
+More tweaks
ToolKit v1.0 (7th Oct 2012)
+First version of Samsung Galaxy Note2 ToolKit released
--------------------------------------------------------------
*DISCLAIMER*
I take no responsibility for any fault or damage caused by any procedures within this guide. No warranties of any kind are given.

**FAQ**
Q. What is ADB Shell?
Adb shell is a linux command line tool (because android is based on linux) used to send commands to your android device. For S-ON devices, this is crucial for modifying files in the /system partition (where the rom sits) as you cannot modify anything in /system when the rom is running without S-OFF (e.g removing system apps).
From Google:
Android Debug Bridge (adb) is a versatile tool lets you manage the state of an emulator instance or Android-powered device. It is a client-server program that includes three components:
A client, which runs on your development machine. You can invoke a client from a shell by issuing an adb command. Other Android tools such as the ADT plugin and DDMS also create adb clients.
A server, which runs as a background process on your development machine. The server manages communication between the client and the adb daemon running on an emulator or device.
A daemon, which runs as a background process on each emulator or device instance.
----------------------------------------------------------------------------
Q. I flashed CWM but each time I reboot the Stock Recovery is back
There is an auto recovery restore system on Android that will reflash the Stock Recovery if you flash CWM on a Stock Rom.
Use Root Explorer to Mount the system folder as R/W (or use a free app from the Market). Delete the file recovery-from-boot.p from /system. Now when you flash CWM Recovery it will NOT be overwritten after a reboot. You can also use the Toolkit to rename the files if you wish.
----------------------------------------------------------------------------
Q. What is the difference between Nandroid and Titanium backup?
A NANDROID will backup the whole system including boot, system, data and recovery partitions so you can restore a complete rom and all data and settings.
Essentially Titanium Backup is used to backup apps and associated user data. These could be restored AFTER a full wipe and a new Rom had been flashed on your phone.
The other option now which google added into the new adb command list is the adb backup which is in the ToolKit and can do the same job as Titanium Backup but will store the data on your PC rather than on the phone (where it takes up space and could be deleted).
----------------------------------------------------------------------------
Q. When would i perform a nandroid vs a titanium backup?
You would perform a nandroid backup to back up your entire system including boot image and data and system partitions so you can restore your entire system back to that particular point in the future.
You would use Titanium Backup mainly to back up your installed apps and settings so they could be reinstalled easily and quickly on any future roms. You can also choose individual apps to backup or restore on Titanium Backup whereas if you restore your boot partition via CWM Recovery you are stuck with the whole lot.
----------------------------------------------------------------------------
Q. When I try to open the ToolKit I get a box pop up for a split second and then it goes away. My AntiVirus program says the file may be harmful.
The exe files I compiled are not digitally signed with a Microsoft certificate (as they cost money) so certain AntiVirus programs (mainly Norton and AVG Free) will pick it up as potentially harmful when it is not. They pick up ANY file that doesnt contain a purchased Microsoft certificate in the same way. Restore the deleted file and exclude it from further scans and it will be fine.
----------------------------------------------------------------------------
Q. I have Windows 8 and cannot install the drivers
How to Disable Driver Signature Enforcement in Windows 8:
From the Metro Start Screen, open Settings (move your mouse to the bottom-right-corner of the screen and wait for the pop-out bar to appear, then click the Gear icon).
Click ‘More PC Settings’.
Click ‘General’.
Scroll down, and click ‘Restart now’ under ‘Advanced startup’.
Wait a bit.
Click ‘Troubleshoot’.
Click ‘Advanced Options’
Click ‘Windows Startup Settings’
Click Restart.
When your computer restarts, select ‘Disable driver signature enforcement‘ from the list. You can now load your modified driver. Reboot again once the driver is installed and all will be well.
----------------------------------------------------------------------------
Q. I flashed the Stock Firmware Image. Odin flashes the file successfully and the phone reboots but it stays stuck on the samsung logo
If the firmware tar file does not include a userdata image (which most Samsung firmware do not) then your userdata partition will be left from your previous setup. If this is incompatible with the new firmware because of build or something else then your system will freeze on boot up.
This is easily fixable by holding the Volume UP, Home and Power buttons all at the same time for about 10 seconds until the device reboots to the Stock Recovery screen. Use the Volume Down button to scroll down to 'wipe data/factory reset' and press the Home button to select it. Go down to yes to confirm and your userdata partition will be wiped. Your device should now boot fine.

**RESERVED FOR MANUAL INSTRUCTIONS**

Reserved for how to videos on this incredible toolkit!
http://www.youtube.com/playlist?list=PLwCVKEYxr_z7FBQYT32dbYw_kdSJmSDH2
How To Root
http://www.youtube.com/watch?v=M9zF6x1MURM
How To Flash Stock Recovery
http://www.youtube.com/watch?v=9CL5x84Tu_U
How To Manually Boot to Custom (or Stock) Recovery
http://www.youtube.com/watch?v=9m6Uugh8ps8&hd=1
Sent from my SPH-L710 using Tapatalk 2

Can i unroot with toolkit?.Many thank for awesome work..:good:

thank you! worked like a charm!!!

simplelife said:
Can i unroot with toolkit?.Many thank for awesome work..:good:
Click to expand...
Click to collapse
Yes you can.
Mark.

So does this add to the flash counter?

Tiffany84 said:
So does this add to the flash counter?
Click to expand...
Click to collapse
Flashing any custom firmware (boot, recovery) will add to the flash counter but im sure Chainfire will update his Triangle Away app to include the US variants.
Mark.

simplelife said:
Can i unroot with toolkit?.Many thank for awesome work..:good:
Click to expand...
Click to collapse
mskip said:
Yes you can.
Mark.
Click to expand...
Click to collapse
Just to be certain, I can unroot with this? How? We don't have a stock recovery since there is no stock firmware avail. Can you please clarify? Thanx bud.

GREAT work and thank you for getting this into an easy toolkit form, as many people will be helped out by this!! I was already rooted, as some others were too, but you created a tool that needs a BIG :good:

teshxx said:
Just to be certain, I can unroot with this? How? We don't have a stock recovery since there is no stock firmware avail. Can you please clarify? Thanx bud.
Click to expand...
Click to collapse
Well I keep asking for someone with adb root access to do an adb shell mount and send me the mount points so I can verify the partitions but noone is getting back to me.
If you or anyone else can send me the mount points then please do so asap. The unroot zip file will remove the su and superuser files along with busybox and cwm manager (if present) but it needs the correct system partition value to mount the system and run the script.
Mark.

Is TWRP supported on the TMo Note II?

mskip said:
Flashing any custom firmware (boot, recovery) will add to the flash counter but im sure Chainfire will update his Triangle Away app to include the US variants.
Click to expand...
Click to collapse
I will, I just need a stock recovery.img ! If you have it, please pass it to me (this goes for all US variants, btw).
I might get it to work as well if somebody can get me the stock kernel. Root first, then from a root shell:
Code:
dd if=/dev/block/mmcblk0p8 of=/data/local/tmp/kernel.img bs=4096
then from normal cmd:
Code:
adb pull /data/local/tmp/kernel.img
And post the kernel.img - should be 8mb
I will also need: Settings -> About device -> Build number

mskip said:
Well I keep asking for someone with adb root access to do an adb shell mount and send me the mount points so I can verify the partitions but noone is getting back to me.
If you or anyone else can send me the mount points then please do so asap. The unroot zip file will remove the su and superuser files along with busybox and cwm manager (if present) but it needs the correct system partition value to mount the system and run the script.
Mark.
Click to expand...
Click to collapse
Oh ok. I would, but I haven't rooted mine yet. Still deciding if I want to keep my grey one or exchange it for the white lolol. Hopefully, someone who is already rooted will be kind enough to do it for you.
Thanks for your effort and time.

Chainfire said:
I will, I just need a stock recovery.img ! If you have it, please pass it to me (this goes for all US variants, btw).
I might get it to work as well if somebody can get me the stock kernel. Root first, then from a root shell:
Code:
dd if=/dev/block/mmcblk0p8 of=/data/local/tmp/kernel.img bs=4096
then from normal cmd:
Code:
adb pull /data/local/tmp/kernel.img
And post the kernel.img - should be 8mb
I will also need: Settings -> About device -> Build number
Click to expand...
Click to collapse
PM sent w/ link for stock T889 kernel.img. build number is the file name. sorry i can't help with stock recovery.img since i already rooted and flashed CWM recovery.
---------- Post added at 11:43 AM ---------- Previous post was at 11:40 AM ----------
mskip said:
Well I keep asking for someone with adb root access to do an adb shell mount and send me the mount points so I can verify the partitions but noone is getting back to me.
If you or anyone else can send me the mount points then please do so asap. The unroot zip file will remove the su and superuser files along with busybox and cwm manager (if present) but it needs the correct system partition value to mount the system and run the script.
Mark.
Click to expand...
Click to collapse
hey mark, if u wanna post or PM me instructions i'll get u the mount points.

Chainfire said:
I will, I just need a stock recovery.img ! If you have it, please pass it to me (this goes for all US variants, btw).
I might get it to work as well if somebody can get me the stock kernel. Root first, then from a root shell:
Code:
dd if=/dev/block/mmcblk0p8 of=/data/local/tmp/kernel.img bs=4096
then from normal cmd:
Code:
adb pull /data/local/tmp/kernel.img
And post the kernel.img - should be 8mb
I will also need: Settings -> About device -> Build number
Click to expand...
Click to collapse
So nice to see you here. Thanks for all u do!!
Sent from my SGH-T889 using Tapatalk 2

I am getting issues with both TWRP and CWM. With TWRP, the data partition is unable to mount, making a full wipe a no go. With CWM, data partition can mount...but the external sd can't. Anyone else having these issues, or is it something on my end?

LvDisturbed1 said:
I am getting issues with both TWRP and CWM. With TWRP, the data partition is unable to mount, making a full wipe a no go. With CWM, data partition can mount...but the external sd can't. Anyone else having these issues, or is it something on my end?
Click to expand...
Click to collapse
I can use my extSD with CWM so it's something on your end. I used the toolkit for the N7100 but same stuff...

Chainfire said:
I will, I just need a stock recovery.img ! If you have it, please pass it to me (this goes for all US variants, btw).
I might get it to work as well if somebody can get me the stock kernel. Root first, then from a root shell:
Code:
dd if=/dev/block/mmcblk0p8 of=/data/local/tmp/kernel.img bs=4096
then from normal cmd:
Code:
adb pull /data/local/tmp/kernel.img
And post the kernel.img - should be 8mb
I will also need: Settings -> About device -> Build number
Click to expand...
Click to collapse
I just sent you a pm with the stock recovery.img from my device(T-Mobile Galaxy Note 2). My build number is JRO03C.T889UVALJ1. Hopefully this gives you what you need. Thanks again.
---------- Post added at 03:53 AM ---------- Previous post was at 03:43 AM ----------
mskip said:
Well I keep asking for someone with adb root access to do an adb shell mount and send me the mount points so I can verify the partitions but noone is getting back to me.
If you or anyone else can send me the mount points then please do so asap. The unroot zip file will remove the su and superuser files along with busybox and cwm manager (if present) but it needs the correct system partition value to mount the system and run the script.
Mark.
Click to expand...
Click to collapse
Just sent you a pm with the mount points for the T-Mobile Galaxy Note 2. Thanks for this tool. It's incredible.

[TOOLS] Command file install/check/repair

Hi!
I had several different files to automate and I decided to collect them into one.
I added the file to the message. The archive contains the latest version of Android SDK Tools pulled adb and fastboot and the batch file for automating the following tasks:
1) Flash stock firmware via Fastboot
2) Flash stock firmware via Fastboot with clearing the cache and user data
3) Flash custom recovery TWRP via Fastboot
4) Check /data partitions for errors
5) Check /data partitions for errors whis auto repair
6) Format /data partitions with fast check for bad blocks
7) Format /data partitions with full check for bad blocks
8) Full clear /data partitions (fill zero)
I created this file to not have to enter the commands manually. This archive should be unpacked in the root of drive C. Folder was adb-t.
In this folder, copy the file of custom recovery for your tablet model and its version of the Android, rename it to twrp.blob. And also copy to this folder the blob file of your stock firmware.
Then run the file Many_Task_en.cmd (or Many_Task_ru.cmd for Russian).
I hope that it will be useful to someone.

Wow, thanks! I thing it will be very useful in the future!

Added in the Index for TF300
Good job

I found a small error - incorrectly pasted from the clipboard. File replaced.

Updated. Now all the files in the archive are from the Android SDK Platform-tools 18.0.1.
Added a new menu item.

Nice Job! Thanks!
BrateloSlava said:
Updated. Now all the files in the archive are from the Android SDK Platform-tools 18.0.1.
Added a new menu item.
Click to expand...
Click to collapse
Just used this to successfully update TWRP from 2.5.0.0 to 2.6.0.0 on the 4.1.1 JB bootloader via fastboot usb.
Not bothering with the 4.2.2 variants now that 4.3 is pending (and because the hdmi out doesn't work properly on any 4.2.2 ROM, including stock).

[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?

Root guide (updated)

==== READ THIS POST BEFORE ROOTING ====​https://www.reddit.com/r/surfaceduo/comments/wn5joi/a_warning_to_wouldbe_developers_and_hobbyist/
(ORIGINAL GUIDE BELOW)​Since the last guy hasn't been updating his op, I figured I'd start a fresh thread with what we know and what to do for newcomers.
I will not be posting patched boot images in this thread, I'm a firm believer of "give you steps to follow from the top so you know what's going on and can do this yourself in the future". The more hands we have in the kitchen, the more we learn, and the better we are off as a community.
Walkthroughs for both fresh rooting and updating while rooted are both below:
==== FRESH ROOT ====​
0. make sure USB debugging is on in settings > developer options
0. make sure the phone's bootloader is actually unlocked, if the below doesn't work, back up all the data on your phone because we're about to wipe it
Code:
.\fastboot.exe flashing unlock
.\fastboot.exe flashing unlock_critical
I did both, but it might only require one of the two, if you only did one and it doesn't work you may not be fully unlocked and might have to do the other. Both of these commands from the bootloader will factory reset your phone. if you've already done this, go to step 1.
1. go here https://support.microsoft.com/en-us/surface-recovery-image put in your serial number (can be found in settings) and download the latest recovery image
2. download payload_dumper from here https://gist.github.com/ius/42bd02a.../48ffe1eee59af9a7da883d9ec7902d1507428dc4.zip
3. download the latest platform-tools from here https://developer.android.com/studio/releases/platform-tools
4. extract all three zips to the same folder, a folder on your desktop is fine, mine is just the name of the current MS zip archive (2021_314_91 at time of writing and used in the below examples)
5. open powershell, and cd to that folder.
6. from the folder, run it like this
Code:
PS C:\wherever\your\****\is\2021_314_91> python.exe -m payload_dumper ./payload.bin
(this will extract a bunch of stuff, boot.img is all we care about today)
6a. if you don't have python, get it from ninite https://ninite.com/pythonx3/ and go back to step 5/6 and try again, you will likely also need to do a "pip install protobuf" to get the required python libraries for payload-dumper
7. download the latest version of magisk manager (the new magisk app may work, but I've not tested it, this is the exact version I am using on the exact phone you are using. If you feel like trying the app please report in the thread below!) https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk
8. install magisk manager on your phone
9. make a text file, I called mine magisk_channel.txt and put this in it
Code:
https://raw.githubusercontent.com/Lethany/magisk_files/0755a7d5f596dc2a351270120b31b665fb561294/stable.json
this is the "custom" channel we are using to force an older version of magisk that doesn't choke on our device like newer versions do.
10. use usb data transfer mode to copy the boot.img file we extracted from step 6 and the text file we created in step 8 to your phone's internal storage, I have a folder on the root of the internal storage directory called Z_Phone, but anywhere is fine as long as you know where it is and remember it later.
11. in magisk manager, click the gear in the top right and then select "update channel" > "custom channel"
12. use your duo's dank duo mode to open a file browser on the other screen, open the text file we made in step 9
13. copy and paste the custom channel text into the custom channel field under update channel in magisk so it has the text from step 9 in it. (the text file just saves us typing it out by hand)
14. go back to the magisk main screen, and click install next to "magisk"
14b. click next
14c. click "select and patch a zip file"
14d. browse to the location we uploaded boot.img to in step 9 and select boot.img
14e. click let's go
(this will create the patched boot.img, it'll be named magisk_patched_[some garbage].img)
15. open the internal storage on your PC again, and go to your phone's "downloads" folder, it'll have that patched boot.img (if you've tried this a bunch of times and don't remember which one we just made, feel free to delete all the old ones and do 14-14e again) copy this patched_boot.img to your computer, I just put it in that same folder as step 4
16. in powershell, cd back to that same working folder we've been using and run
Code:
.\adb.exe reboot bootloader
The phone will reboot to the bootloader and we can now try booting the patched image
16. in powershell, run
Code:
.\fastboot.exe boot .\magisk_patched_[WHATEVER_YOURS_IS_NAMED].img
17. if your phone boots, that's a great sign and we're out of the woods, nothing else will probably go wrong from here, if it doesn't boot factory reset your phone and start at step 0.
18. open an adb shell prompt and make our boot partitions writable with the below 4 lines, run one by one. Right now we're "rooted" but we've booted off an image over usb, what we really want is to boot off the images on your phone so we need to.
Code:
.\adb.exe shell
su
chmod 777 /dev/block/by-name/boot_a
chmod 777 /dev/block/by-name/boot_b
19. write the patched boot image to your boot partitions with the below lines, again run one by one
Code:
adb shell
su
dd if=/sdcard/[PATH TO IMAGE]/[PATCHED BOOT].img of=/dev/block/by-name/boot_a
dd if=/sdcard/[PATH TO IMAGE]/[PATCHED BOOT].img of=/dev/block/by-name/boot_b
(my patched boot image is in a folder called "Z_Phone" and my patched image is called "magisk_patched_ks4OZ.img" so my commands look like:
Code:
dd if=/sdcard/Z_Phone/magisk_patched_ks4OZ.img of=/dev/block/by-name/boot_a
dd if=/sdcard/Z_Phone/magisk_patched_ks4OZ.img of=/dev/block/by-name/boot_b
)
20. reboot your phone via the power button menu and if all went well, you're now rooted!
==== UPDATE WHILE ROOTED ====​
1. go here https://support.microsoft.com/en-us/surface-recovery-image put in your serial number (can be found in settings) and download the latest recovery image
2. download payload_dumper from here https://gist.github.com/ius/42bd02a.../48ffe1eee59af9a7da883d9ec7902d1507428dc4.zip
3. download the latest platform-tools from here https://developer.android.com/studio/releases/platform-tools
4. extract all three zips to the same folder, a folder on your desktop is fine, mine is just the name of the current MS zip archive (2021_314_91 at time of writing)
5. open powershell, and cd to that folder.
6. from the folder, run it like this
Code:
PS C:\wherever\your\****\is\2021_314_91> python.exe -m payload_dumper ./payload.bin
(this will extract a bunch of stuff, boot.img is all we care about today)
7. boot off of your old magisk patched boot image
Code:
.\adb.exe reboot bootloader
.\fastboot.exe boot ..\[LAST VERSION'S FOLDER]\magisk_patched_[WHATEVER_YOURS_IS_NAMED].img
8. write the old, unpatched boot partition to your boot partitions with the below lines, again run one by one
Code:
adb shell
su
dd if=/sdcard/[PATH TO IMAGE]/boot.img of=/dev/block/by-name/boot_a
dd if=/sdcard/[PATH TO IMAGE]/boot.img of=/dev/block/by-name/boot_b
(my unpatched boot image is in a folder called "Z_Phone" and my unpatched image in this example is called "boot.img" so my commands look like:
Code:
dd if=/sdcard/Z_Phone/boot.img of=/dev/block/by-name/boot_a
dd if=/sdcard/Z_Phone/boot of=/dev/block/by-name/boot_b
)
9. reboot
10. run the OTA update on your now freshly stock phone
11. use magisk to patch the new boot image same as in the first root instructions (14a-14e)
12. copy this patched image off of the phone and into our working directory. leave a copy of this on the phone (I put it in my Z_Phone folder)
13. reboot to bootloader (in powershell, in that same working folder we've been using run)
Code:
.\adb.exe reboot bootloader
14. Boot your phone using the patched boot image (in powershell, run)
Code:
.\fastboot.exe boot .\magisk_patched_[WHATEVER_YOURS_IS_NAMED].img
15. write the patched boot image to your boot partitions with the below lines, again run one by one
Code:
adb shell
su
dd if=/sdcard/[PATH TO IMAGE]/[PATCHED BOOT].img of=/dev/block/by-name/boot_a
dd if=/sdcard/[PATH TO IMAGE]/[PATCHED BOOT].img of=/dev/block/by-name/boot_b
(my patched boot image is in a folder called "Z_Phone" and my patched image is called "magisk_patched_ks4OZ.img" so my commands look like:
Code:
dd if=/sdcard/Z_Phone/magisk_patched_ks4OZ.img of=/dev/block/by-name/boot_a
dd if=/sdcard/Z_Phone/magisk_patched_ks4OZ.img of=/dev/block/by-name/boot_b
)
16. reboot and you're updated and rooted!

special thanks to Perseu5 and his original thread!
Unlocking Bootloader/ Magisk Attempt
MAGISK FULL GUIDE (APK for install and other mods coming soon!) The bootloader unlock is pretty similar to any other phone. Go to settings>about> click on build number until developer options are enabled. Go back and select system>Developer...
forum.xda-developers.com

Nice work!

NTchrist said:
special thanks to Perseu5 and his original thread!
Unlocking Bootloader/ Magisk Attempt
MAGISK FULL GUIDE (APK for install and other mods coming soon!) The bootloader unlock is pretty similar to any other phone. Go to settings>about> click on build number until developer options are enabled. Go back and select system>Developer...
forum.xda-developers.com
Click to expand...
Click to collapse
my magisk still shows that theres an update pending for the framework. when i try to patch the stock boot or the custom, it doesnt boot past the windows logo. im guessing the update is for Magisk 21+?

LocBox said:
my magisk still shows that theres an update pending for the framework. when i try to patch the stock boot or the custom, it doesnt boot past the windows logo. im guessing the update is for Magisk 21+?
Click to expand...
Click to collapse
Magisk updates are based on the git channel it's fed. Best guess is you don't have the same git repo as in the guide. If you feed it a repo link to a static version it should never be aware of any updates ever. As far as the app is concerned you're on the latest version.

On vacation until Wed, then I'll push through the new patch and update the guide

update process works successfully and is unchanged from previous versions

update process for 2021.525.62 works successfully and is unchanged from previous versions

This is incredibly helpful! I didn't even know you could unpack the payload.bin lol. I'll be doing some work in the kitchen thanks to this!

For anyone who needs it, here is a patched boot.img for ATT Locked 2021_525_63

nevergrownup said:
For anyone who needs it, here is a patched boot.img for ATT Locked 2021_525_63
Click to expand...
Click to collapse
Can you send the link or tell me how you were able to get the boot.img? When I try to download the factory image from MS, it is still giving me 2021.419.71.
EDIT: The new "Surface Duo - 256GB - Android 10 - ATT - 2021.525.63" recovery image is available on the "Surface Recovery Image Download" page. Thanks nevergrownup for giving me the heads up on Reddit

Is anyone on 2021.525.63 having issues? I've followed the exact guide above, as well as using the newest Magisk version & attempting to boot the patched boot.img just leads my Duo to hang on the Microsoft logo. Just want to see if anyone else has an issue or it's just me.
Thanks.

Veritas06 said:
Is anyone on 2021.525.63 having issues? I've followed the exact guide above, as well as using the newest Magisk version & attempting to boot the patched boot.img just leads my Duo to hang on the Microsoft logo. Just want to see if anyone else has an issue or it's just me.
Thanks.
Click to expand...
Click to collapse
when flashing stock July, my lockscreen keypad is frozen. cant unlock t to use.

LocBox said:
when flashing stock July, my lockscreen keypad is frozen. cant unlock t to use.
Click to expand...
Click to collapse
That's on a fresh install or after flashing the Magisk-modified boot.img?
I'm about to restore with the recovery image & start this again, in case there's some different between OTA & recovery.
EDIT: Doing a factory reset, ADB sideload of the recovery image, creating the new Magisk boot.img, & booting still doesn't work. I'm going to try the guide's version one more time to use the older version of Magisk Manager & the custom channel, but based on previous experience, I'm not hopeful. I only bought this as a device to have fun with because it can be rooted, so I'm regretting this purchase right now =\

Veritas06 said:
That's on a fresh install or after flashing the Magisk-modified boot.img?
I'm about to restore with the recovery image & start this again, in case there's some different between OTA & recovery.
EDIT: Doing a factory reset, ADB sideload of the recovery image, creating the new Magisk boot.img, & booting still doesn't work. I'm going to try the guide's version one more time to use the older version of Magisk Manager & the custom channel, but based on previous experience, I'm not hopeful. I only bought this as a device to have fun with because it can be rooted, so I'm regretting this purchase right now =\
Click to expand...
Click to collapse
I do have the factory unlocked, not the ATT version. In my experience when your lockscreen touch input is not recognized, that happens when either the boot image doesn't match the factory image, or someone has used the factory unlocked boot on an ATT phone or vice-versa.
I'd try a dirty flash of the complete applicable factory images (not just boot/recovery) and then factory reset, then start again from the top. It's possible one of your updates didn't complete or something's become inconsistent between A/B

NTchrist said:
I do have the factory unlocked, not the ATT version. In my experience when your lockscreen touch input is not recognized, that happens when either the boot image doesn't match the factory image, or someone has used the factory unlocked boot on an ATT phone or vice-versa.
I'd try a dirty flash of the complete applicable factory images (not just boot/recovery) and then factory reset, then start again from the top. It's possible one of your updates didn't complete or something's become inconsistent between A/B
Click to expand...
Click to collapse
Thanks. I never even got far enough to see failed touch input, but may try rooting again this weekend. I wasn't able to ever get past the MS logo on boot, after attempting to fastboot boot the Magisk-modified boot.img.

I am in the same boat as Veritas is. My Duo is from ATT and hangs on the Microsoft logo as well. I am very new to rooting and what goes into it so a lot of this stuff I am seeing for the first time. How do I know if I have the correct boot? I went through the whole process of extracting the boot image from the recovery file for my phone off of the Microsoft website. Does that get me the right boot to use?

ThrowARoot said:
I am in the same boat as Veritas is. My Duo is from ATT and hangs on the Microsoft logo as well. I am very new to rooting and what goes into it so a lot of this stuff I am seeing for the first time. How do I know if I have the correct boot? I went through the whole process of extracting the boot image from the recovery file for my phone off of the Microsoft website. Does that get me the right boot to use?
Click to expand...
Click to collapse
It should, yes. Unfortunately I do not have an ATT phone to test against. You'd have to have someone else in the thread confirm it works on the ATT build. About the only thing you can do is boot to stock, and check that settings>about>build number matches the images you downloaded from microsoft (2021.525.62) at time of writing

Actually in checking my settings I noticed there was a new update available, so ignore the build number above just make sure the image you download matches the image on your device

NTchrist said:
Since the last guy hasn't been updating his op, I figured I'd start a fresh thread with what we know and what to do for newcomers.
I will not be posting patched boot images in this thread, I'm a firm believer of "give you steps to follow from the top so you know what's going on and can do this yourself in the future". The more hands we have in the kitchen, the more we learn, and the better we are off as a community.
Walkthroughs for both fresh rooting and updating while rooted are both below:
==== FRESH ROOT ====​
0. make sure USB debugging is on in settings > developer options
0. make sure the phone's bootloader is actually unlocked, if the below doesn't work, back up all the data on your phone because we're about to wipe it
Code:
.\fastboot.exe flashing unlock
.\fastboot.exe flashing unlock_critical
I did both, but it might only require one of the two, if you only did one and it doesn't work you may not be fully unlocked and might have to do the other. Both of these commands from the bootloader will factory reset your phone. if you've already done this, go to step 1.
1. go here https://support.microsoft.com/en-us/surface-recovery-image put in your serial number (can be found in settings) and download the latest recovery image
2. download payload_dumper from here https://gist.github.com/ius/42bd02a.../48ffe1eee59af9a7da883d9ec7902d1507428dc4.zip
3. download the latest platform-tools from here https://developer.android.com/studio/releases/platform-tools
4. extract all three zips to the same folder, a folder on your desktop is fine, mine is just the name of the current MS zip archive (2021_314_91 at time of writing and used in the below examples)
5. open powershell, and cd to that folder.
6. from the folder, run it like this
Code:
PS C:\wherever\your\****\is\2021_314_91> python.exe -m payload_dumper ./payload.bin
(this will extract a bunch of stuff, boot.img is all we care about today)
6a. if you don't have python, get it from ninite https://ninite.com/pythonx3/ and go back to step 5/6 and try again
7. download the latest version of magisk manager (the new magisk app may work, but I've not tested it, this is the exact version I am using on the exact phone you are using. If you feel like trying the app please report in the thread below!) https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk
8. install magisk manager on your phone
9. make a text file, I called mine magisk_channel.txt and put this in it
Code:
https://raw.githubusercontent.com/Lethany/magisk_files/0755a7d5f596dc2a351270120b31b665fb561294/stable.json
this is the "custom" channel we are using to force an older version of magisk that doesn't choke on our device like newer versions do.
10. use usb data transfer mode to copy the boot.img file we extracted from step 6 and the text file we created in step 8 to your phone's internal storage, I have a folder on the root of the internal storage directory called Z_Phone, but anywhere is fine as long as you know where it is and remember it later.
11. in magisk manager, click the gear in the top right and then select "update channel" > "custom channel"
12. use your duo's dank duo mode to open a file browser on the other screen, open the text file we made in step 9
13. copy and paste the custom channel text into the custom channel field under update channel in magisk so it has the text from step 9 in it. (the text file just saves us typing it out by hand)
14. go back to the magisk main screen, and click install next to "magisk"
14b. click next
14c. click "select and patch a zip file"
14d. browse to the location we uploaded boot.img to in step 9 and select boot.img
14e. click let's go
(this will create the patched boot.img, it'll be named magisk_patched_[some garbage].img)
15. open the internal storage on your PC again, and go to your phone's "downloads" folder, it'll have that patched boot.img (if you've tried this a bunch of times and don't remember which one we just made, feel free to delete all the old ones and do 14-14e again) copy this patched_boot.img to your computer, I just put it in that same folder as step 4
16. in powershell, cd back to that same working folder we've been using and run
Code:
.\adb.exe reboot bootloader
The phone will reboot to the bootloader and we can now try booting the patched image
16. in powershell, run
Code:
.\fastboot.exe boot .\magisk_patched_[WHATEVER_YOURS_IS_NAMED].img
17. if your phone boots, that's a great sign and we're out of the woods, nothing else will probably go wrong from here, if it doesn't boot factory reset your phone and start at step 0.
18. open an adb shell prompt and make our boot partitions writable with the below 4 lines, run one by one. Right now we're "rooted" but we've booted off an image over usb, what we really want is to boot off the images on your phone so we need to.
Code:
.\adb.exe shell
su
chmod 777 /dev/block/by-name/boot_a
chmod 777 /dev/block/by-name/boot_b
19. write the patched boot image to your boot partitions with the below lines, again run one by one
Code:
adb shell
su
dd if=/sdcard/[PATH TO IMAGE]/[PATCHED BOOT].img of=/dev/block/by-name/boot_a
dd if=/sdcard/[PATH TO IMAGE]/[PATCHED BOOT].img of=/dev/block/by-name/boot_b
(my patched boot image is in a folder called "Z_Phone" and my patched image is called "magisk_patched_ks4OZ.img" so my commands look like:
Code:
dd if=/sdcard/Z_Phone/magisk_patched_ks4OZ.img of=/dev/block/by-name/boot_a
dd if=/sdcard/Z_Phone/magisk_patched_ks4OZ.img of=/dev/block/by-name/boot_b
)
20. reboot your phone via the power button menu and if all went well, you're now rooted!
==== UPDATE WHILE ROOTED ====​
1. go here https://support.microsoft.com/en-us/surface-recovery-image put in your serial number (can be found in settings) and download the latest recovery image
2. download payload_dumper from here https://gist.github.com/ius/42bd02a.../48ffe1eee59af9a7da883d9ec7902d1507428dc4.zip
3. download the latest platform-tools from here https://developer.android.com/studio/releases/platform-tools
4. extract all three zips to the same folder, a folder on your desktop is fine, mine is just the name of the current MS zip archive (2021_314_91 at time of writing)
5. open powershell, and cd to that folder.
6. from the folder, run it like this
Code:
PS C:\wherever\your\****\is\2021_314_91> python.exe -m payload_dumper ./payload.bin
(this will extract a bunch of stuff, boot.img is all we care about today)
7. boot off of your old magisk patched boot image
Code:
.\adb.exe reboot bootloader
.\fastboot.exe boot ..\[LAST VERSION'S FOLDER]\magisk_patched_[WHATEVER_YOURS_IS_NAMED].img
8. write the old, unpatched boot partition to your boot partitions with the below lines, again run one by one
Code:
adb shell
su
dd if=/sdcard/[PATH TO IMAGE]/boot.img of=/dev/block/by-name/boot_a
dd if=/sdcard/[PATH TO IMAGE]/boot.img of=/dev/block/by-name/boot_b
(my unpatched boot image is in a folder called "Z_Phone" and my unpatched image in this example is called "boot.img" so my commands look like:
Code:
dd if=/sdcard/Z_Phone/boot.img of=/dev/block/by-name/boot_a
dd if=/sdcard/Z_Phone/boot of=/dev/block/by-name/boot_b
)
9. reboot
10. run the OTA update on your now freshly stock phone
11. use magisk to patch the new boot image same as in the first root instructions (14a-14e)
12. copy this patched image off of the phone and into our working directory. leave a copy of this on the phone (I put it in my Z_Phone folder)
13. reboot to bootloader (in powershell, in that same working folder we've been using run)
Code:
.\adb.exe reboot bootloader
14. Boot your phone using the patched boot image (in powershell, run)
Code:
.\fastboot.exe boot .\magisk_patched_[WHATEVER_YOURS_IS_NAMED].img
15. write the patched boot image to your boot partitions with the below lines, again run one by one
Code:
adb shell
su
dd if=/sdcard/[PATH TO IMAGE]/[PATCHED BOOT].img of=/dev/block/by-name/boot_a
dd if=/sdcard/[PATH TO IMAGE]/[PATCHED BOOT].img of=/dev/block/by-name/boot_b
(my patched boot image is in a folder called "Z_Phone" and my patched image is called "magisk_patched_ks4OZ.img" so my commands look like:
Code:
dd if=/sdcard/Z_Phone/magisk_patched_ks4OZ.img of=/dev/block/by-name/boot_a
dd if=/sdcard/Z_Phone/magisk_patched_ks4OZ.img of=/dev/block/by-name/boot_b
)
16. reboot and you're updated and rooted!
Click to expand...
Click to collapse
Ok I am not sure what I am doing wrong and before anyone says anything is not my first or 10th phone I have rooted, first the so called image that you download from Microsoft is nothing but folders of useless text docs. and the patched magisk image in this thread says it works. I went through the whole set up it says the boot image was successfully done yet upon rebooting my device is not rooted. Can anyone help with this.