Related
Here's a friendly guide for all the people with 1.33.0010 SPL INDIAN VERSION AIRTEL and who would like to switch over to the 1.33.2010 Engineering SPL with Amon_RA's ROM. This has been tested on my Indian HTC Magic, but I do think it will work for other Magics with the same SPL. Remember, this is for 32A only.I tried different options given in xda forum but this method is full proof and now I have a working hero rom on my HTC MAGIC AIRTEL ASIA.
1. Download the latest Android SDK from http://developer.android.com/. Create a folder called "AndroidSDK" on your C drive and extract the contents of the zip file to the folder such that the folders called "tools", "usb_driver" and all are within the "AndroidSDK" folder.
2. On Windows XP : Go to Control Panel->System, Choose the 'Advanced' tab and then click 'Environment Variables' To do this on Vista/Windows7: Simply go to Control Panel->System and choose 'Advanced System Settings' and then 'Environment Variables'
Now that you've got here locate Path under System Variables and click Edit, then add the following to the end of the string displayed:
;C:\AndroidSDK\tools\
Then click OK until you get out of the menus.
3. Enable Debugging mode on the phone by going to
Menu > Settings > Applications > Developement > USB Debugging
4. Go to http://dl.google.com/android/android_usb_windows.zip and download the ADB drivers for windows.Not needed in HTC Sync 2.04 version as drivers are embedded in it.
5. Connect your Android device via USB. When the Found New Hardware Wizard appears, you'll be asked if you'd like Windows Update to search for software, select No, not this time and click Next.
Select Install from a list or specified location and click Next.
Select Search for the best driver in these locations. Browse and select the unzipped folder. Click Finish.
6. Go to "Run" in Start and type in "cmd". This is the standard procedure for invoking the Command Prompt. Remember this. Type "cd\" hit enter and then enter "cd AndroidSDK", hit enter. Then cd\tools ,hit enter The command prompt should look like :
C:\AndroidSDK\tools>
Now type in "adb devices" and hit enter. You should see something like this :
C:\AndroidSDK>adb devices
List of devices attached
XXXXXXXXXXXX device
If you do, everything is great. Disconnect your device.
7. Now go to HTC's global site and download the latest version of HTC Sync(2.04 Version), unzip and install. When you connect your device now, HTC Sync should recognize your phone.
8. Now comes the Gold Card part. Go to http://forum.xda-developers.com/show...99&postcount=1 and follow the guide to create your Gold Card. The 2GB Sandisk one which comes in the box works just fine. If you don't have Android Market, don't fret. Forget about the Steps 3 & 4. Instead, connect your device with the card in it. Invoke command prompt and cd to "AndroidSDK" as told before. Type in "adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid". You will get the CID. Follow the rest of the steps from the guide to create a Gold Card.
9. Time for action. Now you gotta get Engineering SPL 1.33.2010(find it on xda forum)- MD5 : 865020FBDFBD9C08950076A701A8A003 Flash this Rom in Hboot mode.
# Copy the required file zip file and rename it sappimg.zip (Do not add zip only rename as sappimg as it is already a zip file.) and copy it to the Goldcard.
# Boot your phone while holding the VOLUME-DOWN key.
# Press the ACTION KEY (=trackball) to start the update.
# Wait until the update completes and press the ACTION KEY (=trackball) to reboot your phone.
10. Now time to create a Nandroid Backup. Download • RAv1.2.1H – (Find it on xda forums) MD5Sum: E08D0A38BCCADAE416F644EE9D370D8B Put it in the "AndroidSDK\tools" folder. Switch off your phone. Hold the Back button and Switch it on. This takes you to the Fastboot mode. Standard procedure. Remember this. Connect the phone to the PC. Invoke the command prompt, cd to "AndroidSDK\tools" and type :
fastboot boot recovery-RAv1.2.1H.img
The recovery image will boot and you'll see the recovery screen in green colour. Wait for 2 minutes. Select the Nandroid Backup option and follow the on-screen instructions to create a backup. Reboot device. And copy over the "nandroid" folder on you sd card to a safe place.
11. Time to flash the HERO ROM Go to myhero-1.12 (find it on XDA forum) I tried flashing other roms but the screen jams at start so this particular rom is working well on my HTC AIRTEL ASIA Rename the file to "update.zip" and copy over to the sd card. Switch off your phone. Hold the Back button and Switch it on. This takes you to the Fastboot mode. Connect the phone to the PC. Invoke the command prompt, cd to "AndroidSDK\tools" and type :
fastboot boot recovery-RAv1.2.1H.img
The recovery image will boot and you'll see the recovery screen. Wait for 2 minutes. Select the Wipe Data option, and follow instructions to Wipe your present ROM. If you don't do this, your phone might not boot after flashing the ROM. Select the Apply sdcard:update.zip option. Follow onscreen instructions to flash the ROM. Reboot. All done. Welcome to Android.....
All credits go to XDA FORUM , and everybody else for their respective contributions.....
PS. Please do chip in with a Thanks if you found this guide helpful and any corrections are welcome.....
PPS. After you flash the ROM, if HTC Sync isn't working, use Google Sync, since the ROM is a Google ION based one.
Hello, I got the Huawei 651F watch yesterday (bought from amazon.de) and I wonder which is the latest software version?
I'm running on Android Wear 1.3.0.2421912, Google Play Services 9.4.52, Android OS 5.1.1 . I think there is a new version out (which supports speaker and keyboard), but when I click on "System Update" it says my system is up-to-date!
Any ideas?
Mine is running on Android Wear 1.5.0.xxxxx, Google play services 9.4.52 and Android OS 6.0.1
I've had some trouble to get it updated when I bought it, but it was just a matter of time (I guess until the phone wear app downloaded the wear update)
But, for the keyboard it's only available in Android Wear 2 developer preview...
Thanks for your reply. It seems that I run an older version.
So you just waited until the update? How long?
I don't have to do anything and the watch will update itself? No wi-fi on, no other setting etc?
Make sure watch is fully charged and better put watch on charger when checking for updates and have WiFi enabled
That worked for me...
Thanks for your reply.
Tried it and didn't work for me. It still says system is up to date.
No idea if there is meaning in just waiting. It's an old update right?
Be patient, it will come.
Sent from my Nexus 10 using Tapatalk
Other solution if you don't want to wait is to flash the latest stock version with adb/fastboot
I just wanted to know if there's a meaning in waiting.
In addition after I restart my phone the watch loses the recent contacts list (2 swipes right). How can I get it back?
EDIT: Nevermind, I turned on Bluetooth debugging on the phone only (not in the watch) and restarted the phone and contacts are back. I'm not sure I understand what Bluetooth debugging is or if it had anything to do with it.
I've tried restoring to factory defaults in order to get the 1.5 update with no luck. How can I update from 1.3 to 1.5 manually? Any link would be appreciated.
Here you can find the preview image (android wear 2.0 developer preview) and the original image (named : Non-preview image (for after testing)). Make sure you download Huawei watch image and not the LG one : https://developer.android.com/wear/preview/downloads.html
You'll have to flash the "non-preview image" with adb/fastboot
Still no update, despite checking while charging etc. Is there meaning in waiting?
Could you give me the latest "stable" version, with a detailed guide? I remind you that I have version 1.3, so I need a full version to 1.5, not incremental. Right? I think I need to make changes in the phone too, not only download the version and toolkits.
Don't know why you still don't have the update...
For the latest stable version, it's the one I gave you in my last post. The guide to flash it is detailed under the links. Don't worry, it's a full 1.5 version.
You need to have SDK manager (in order to install and use adb/fastboot), but nothing have to be done on your phone (just unpair the watch) : everything else is done from the charger connected to your computer
Thanks.
I meant the watch, not the phone.
So I download the non preview image? The links you provided are for some version 2.0 of wear, not 1.5?
Yes the non-preview is wear 1.5 : Google give this image as a way to revert back to a stable release after testing the wear 2.0 developer preview. In your case, you can just flash it to manually update to official wear 1.5
Sorry for my persistance but I have no experience with android wear plus flashing a watch. Could you check the versions in the screenshots and tell me if it's ok to proceed?
I have to download and flash the following image?
sturgeon-mec23l-factory-48003078.tgz
MD5: 417b5cbddb29a2262bce133e283d2732
SHA-1: 4800307843580f818557dd7c43d8ba2161e289b2
I believe the guide is missing some instructions, in example it says to download and unzip the image, but it doesn't say copy the file in the watch. Don't I have to download the file in my computer, unzip it there, then transfer it to the root directory of the watch? Or like in the phones, you have to transfer the zip file to the device you want to upgrade?
Thanks again.
No problem, but you'll see that in fact, phone or watch, it's very similar !
Yes, this is the good one to download : sturgeon-mec23l-factory-48003078.tgz
About your screenshots, it's ok : it's not an update, it's a full system image which will wipe everything during install (so you could install it on the top of every wear version). I just read again the guide, there is nothing missing : the "flash-all" script is in fact composed of several "adb" commands which will push and install bootloader, rom, recovery, ... as you would had done with a nexus device (exactly the same process).
I think you was thinking about installing it with TWRP, but it's not a zip file as a custom rom.
So I download the file and unzip it in the watch or in my pc?
Furthermore, I don't undestand the following:
"Confirm installation of the fastboot tool
To flash a device using one of the system images, confirm that you have the fastboot tool in the platform-tools/ directory of the Android SDK. Be sure that you have the latest version of the Android SDK Platform-tools from the SDK Manager.
After you confirm that you have the fastboot tool, add the tool to your PATH environment variable so the tool can be found when you flash the watch."
I've download ANDROID STUDIO 2.1.3, but can't find where the platform-tools/directory is? I clicked on Configure -> SDK Manager and installed Android 7, 6, 5.1, 5. I don't know if it was needed...
The part that you don't understand is about adb/fastboot utility which are needed to push the file and install them on your watch. Anyway, you said that you installed Android Studio (it was not really needed) but adb/fastboot is automaticaly installed with it ! So it's a good point.
First, you'll have to search for your sdk folder. Usually it's located in : "C:\Users\<--user name-->\AppData\Local\Android\sdk". There is inside a folder "platform-tool" which contain among all the files adb.exe and fastboot.exe
Then, unzip the tarball (sturgeon-mec23l-factory-48003078.tgz) in this folder. Then Shift + Right-click in the background of the folder and select "open a command window there" (or something like that, my computer is not in english).
Finaly, follow the guide :
2. Attach the watch charger to the watch and plug the USB cord (from the charger) into your computer.
3. Use the following adb command to confirm that the watch is available for flashing: adb devices
4. Use the following adb command to start the device in fastboot mode: adb reboot bootloader
5. Unlock the device's bootloader. This step erases all data on the device: fastboot oem unlock
On the watch, select the Unlock option.
6. Issue the command: flash-all.bat
7. Optionaly, you can lock again your bootloader by the command: fastboot oem lock
Found it thanks.
Frixx_x said:
The part that you don't understand is about adb/fastboot utility which are needed to push the file and install them on your watch. Anyway, you said that you installed Android Studio (it was not really needed) but adb/fastboot is automaticaly installed with it ! So it's a good point.
First, you'll have to search for your sdk folder. Usually it's located in : "C:\Users\<--user name-->\AppData\Local\Android\sdk". There is inside a folder "platform-tool" which contain among all the files adb.exe and fastboot.exe
Then, unzip the tarball (sturgeon-mec23l-factory-48003078.tgz) in this folder. Then Shift + Right-click in the background of the folder and select "open a command window there" (or something like that, my computer is not in english).
Finaly, follow the guide :
2. Attach the watch charger to the watch and plug the USB cord (from the charger) into your computer.
3. Use the following adb command to confirm that the watch is available for flashing: adb devices
4. Use the following adb command to start the device in fastboot mode: adb reboot bootloader
5. Unlock the device's bootloader. This step erases all data on the device: fastboot oem unlock
On the watch, select the Unlock option.
6. Issue the command: flash-all.bat
7. Optionaly, you can lock again your bootloader by the command: fastboot oem lock
Click to expand...
Click to collapse
Frixx_x thanks a lot mate, I've updated the phone as described. Still the version in the link you gave me is Android Wear 1.4 (6.0.1 Android), not 1.5. If I don't see it updating in the next days is there a way for 1.5?
Hello
Yesterday I tried (Xperia XZ2 Compact H8324) to flash on the new Android 9.
My device was built in Hong Kong.
I went like this:
First I downloaded the current German Android 9 Stock Rome via Xperifirm. H8324_Customized DE_1313-6204_52.0.A.3.84_R2B
Before the flash, I created the * .ftf file in flash tool 0.9.25.0, as shown in a Youtube video. The whole thing worked fine.
Then I put my device into Flash mode and integrated the latest drivers into my PC.
Before I could start the flash process, I had to move the *. Fsc script from the folder "devices \ H83XX" in the folder "my devices" and rename in the current firmware. Since he gave me the message when starting the flash process that no update script would be available.
Then the flash process started asking if he should skip certain things stored in the script. Of course I confirmed that.
The flash process ran without any further error message and ended with the message that the flash was successful.
However, after starting the Xperia, the message "Your device is corrupted - it can not be trusted" was displayed. The device shuts down after 5 seconds.
Fortunately, I was able to recover my original firmware through the PC Companion.
Can someone tell me where I might have made a mistake on the way and how can I fix this? I would like to have Android 9, but that has not arrived in Hong Kong yet.
This is my first tutorial, hope you enjoy it and take you further.
Thank you first to juandiazmora
So you get Android 9 on your smartphone without any regional restrictions.
The following programs are required: Xperifirm, flashtool 0.9.25.0
1. Download the Rome at Xperifirm which is compatible with your device and you want it. For me, the firmware was unpacked directly by Xperifirm otherwise uses Flashtool Tools> Bundles> FILESET Decrypt
!!! Important with the downloaded files the "fwinfo.xml delete" !!!
2. In the Flash tool go to Tools> Bundles> Create
2.1 There you choose the folder in which the firmware is located.
2.2 Then select your device at Device.
2.3 When branding enter your country version. In my case Germany.
2.4 In version your firmware version you want to install.
2.5 Now important and careful. With folders list you add all files except * .ta files to the firmware content.
2.6 Then click Create and wait.
3. Adapt Flashtool. Go to the folders "Users" \ flashTool \ devices \ H82XX and the
"User". \ Flash tool \ devices \ H83XX
3.1 Copies the 52.fsc from the H82XX to the H83XX
Deletes the 51.1.fsc
3.2 Then copy the complete folder H83XX into the folder "User" \. FlashTool \ mydevices
4. Connect the mobile phone in Flash mode to the PC. Do not forget to install the appropriate driver. Flashtool also provides drivers and Xperia Companion.
4.1 If everything is ready then go to step 5.
*
5. Flashing
5.1 Click on the flash symbol in the flash tool.
5.2 Select flash mode
5.3 For Source folder, select the folder with the previously created firmware file in * .ftf.
5.4 Select Device for Device Filter.
5.5 At Firmwares, select your created firmware.
5.6 For Wipe Sin, select APPSLOG / USERDATA
5.7 Select Disable final verification.
5.8 Flash
6. When flashing, he asks if he should use the 52.fsc.
Simply confirm everything then works well.
For me it all worked out but of course I take no guarantees. Everything at your own risk.
Double that. I havent flashed pie too, requesting a little guide how to do it properly to have full stock firmware.
I think you should use a fsc for 52 firmware, not just remane the 51.1. On github page is available the data for create that specific file. Also you can use xperifirm to download the firmware easily and safely
52.fsc
juandiazmora said:
I think you should use a fsc for 52 firmware, not just remane the 51.1. On github page is available the data for create that specific file. Also you can use xperifirm to download the firmware easily and safely
Click to expand...
Click to collapse
Hi, I need help on the flashscript thingie.
Don't have a clue where to get it from.
Thanks in advance.
I'm with Customized CE1 in my H8314 and I'm still in Oreo. It would be possible do this steps with my same firmware without doing wipe? Only deleting the country restricion.
Regards
Why can't we just flash using the downloaded and unpacked firmware from Xperiafirm? Why this need to exclude some specific .ta files and disable final verification checks?
Quarzkopf said:
Hello
Yesterday I tried (Xperia XZ2 Compact H8324) to flash on the new Android 9.
My device was built in Hong Kong.
I went like this:
First I downloaded the current German Android 9 Stock Rome via Xperifirm. H8324_Customized DE_1313-6204_52.0.A.3.84_R2B
Before the flash, I created the * .ftf file in flash tool 0.9.25.0, as shown in a Youtube video. The whole thing worked fine.
Then I put my device into Flash mode and integrated the latest drivers into my PC.
Before I could start the flash process, I had to move the *. Fsc script from the folder "devices \ H83XX" in the folder "my devices" and rename in the current firmware. Since he gave me the message when starting the flash process that no update script would be available.
Then the flash process started asking if he should skip certain things stored in the script. Of course I confirmed that.
The flash process ran without any further error message and ended with the message that the flash was successful.
However, after starting the Xperia, the message "Your device is corrupted - it can not be trusted" was displayed. The device shuts down after 5 seconds.
Fortunately, I was able to recover my original firmware through the PC Companion.
Can someone tell me where I might have made a mistake on the way and how can I fix this? I would like to have Android 9, but that has not arrived in Hong Kong yet.
This is my first tutorial, hope you enjoy it and take you further.
Thank you first to juandiazmora
So you get Android 9 on your smartphone without any regional restrictions.
The following programs are required: Xperifirm, flashtool 0.9.25.0
1. Download the Rome at Xperifirm which is compatible with your device and you want it. For me, the firmware was unpacked directly by Xperifirm otherwise uses Flashtool Tools> Bundles> FILESET Decrypt
!!! Important with the downloaded files the "fwinfo.xml delete" !!!
2. In the Flash tool go to Tools> Bundles> Create
2.1 There you choose the folder in which the firmware is located.
2.2 Then select your device at Device.
2.3 When branding enter your country version. In my case Germany.
2.4 In version your firmware version you want to install.
2.5 Now important and careful. With folders list you add all files except * .ta files to the firmware content.
2.6 Then click Create and wait.
3. Adapt Flashtool. Go to the folders "Users" \ flashTool \ devices \ H82XX and the
"User". \ Flash tool \ devices \ H83XX
3.1 Copies the 52.fsc from the H82XX to the H83XX
Deletes the 51.1.fsc
3.2 Then copy the complete folder H83XX into the folder "User" \. FlashTool \ mydevices
4. Connect the mobile phone in Flash mode to the PC. Do not forget to install the appropriate driver. Flashtool also provides drivers and Xperia Companion.
4.1 If everything is ready then go to step 5.
*
5. Flashing
5.1 Click on the flash symbol in the flash tool.
5.2 Select flash mode
5.3 For Source folder, select the folder with the previously created firmware file in * .ftf.
5.4 Select Device for Device Filter.
5.5 At Firmwares, select your created firmware.
5.6 For Wipe Sin, select APPSLOG / USERDATA
5.7 Select Disable final verification.
5.8 Flash
6. When flashing, he asks if he should use the 52.fsc.
Simply confirm everything then works well.
For me it all worked out but of course I take no guarantees. Everything at your own risk.
Click to expand...
Click to collapse
@Quarzkopf I know this thread is a bit old but I ran into similar "Your device is corrupted..." error when trying to flash US customization to my UK Xperia 1 ii. I was wondering how you got resolved this to a clean flash without this error at the end? Wasn't clear from instructions. Much appreciate your help
Prerequisites:
You must bootloader unlock your XT2041-4.
Unlocking the Bootloader | Motorola Support US
Visit the customer support page to view user guides, FAQs, bluetooth pairing, software downloads, drivers, tutorials and to get repair and contact us information.
motorola-global-portal.custhelp.com
As far as I'm aware, this only applies to XT2041-4 on Verizon Wireless.
To be clear, the XT2041-4 is the "US Retail" or "Unlocked" (carrier unlocked) version of the Moto G Power. It's available from Best Buy, Amazon, etc. If you bought your Moto G Power from a Verizon store (or the Verizon website) you have the XT2041-7 and you should already have WiFi and HD Voice and Video calling. It's found here:
Settings -> Network & Internet -> Advanced Calling
The XT2041-4 does not have this menu available, so we're going to flash the Verizon ROM onto the Retail phone. Here we go.
Download and install the latest Motorola drivers:
Where can I download the USB drivers for my device?| Motorola Support US
Visit the customer support page to view user guides, FAQs, bluetooth pairing, software downloads, drivers, tutorials and to get repair and contact us information.Where can I download the USB drivers for my device?
support.motorola.com
Plug your phone into your PC with the factory USB cable and make sure you get all the necessary drivers installed. From your phone, select "Android System - Charging" in the notifications bar and change to "File Transfer". This should prompt Windows to install another driver.
Make sure you have the latest platform tools. This includes the latest adb.exe and fastboot.exe for use with fastbootd:
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Download the latest Verizon image for the XT2041-7 from Lolinet:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Once downloaded, extract the zip file, so you're left with a file folder something like ths:
XT2041-7_SOFIA_VZW_10_[version]_subsidy-VZW_RSU_QCOM_regulatory-DEFAULT_CFC.xml
We'll call it your rom folder.
To make life easy, lets copy the required android utilities into this folder for flashing. Open up your platform-tools folder and copy the following to your rom folder:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
With your rom folder open, grab the entire folder location from the address bar and copy to your clipboard.
Click your start menu and type cmd, and open up Command Prompt.
Once you have the command prompt open, change directory to your rom folder:
Code:
cd [rom folder location]
All you have to do is type "cd", then space, then right click your mouse button to paste the folder location that you copied in the last step.
Hit enter to change directory.
Now your Command Prompt can call files from within your rom directory.
Now type:
Code:
adb devices
Watch your phone for the authorization dialog. Check the box and grant authorization. If it doesn't work, try unplugging your phone and plugging back in to get the drivers installed, then try again. The Command Prompt should return the serial number of your Moto G Power.
Now type:
Code:
adb reboot bootloader
And make sure your device reboots into bootloader mode.
Now type:
Code:
fastboot reboot fastboot
Make sure your device reboots into fastbootd. If this command doesn't work, you don't have the latest version of android platform tools.
Now type:
Code:
fastboot reboot bootloader
Your device should reboot back to bootloader mode. If everything is working so far, proceed to this thread and follow steps 4-7.
Moto G Power flashing guide
This guide also applies on other Moto phones shipping with Android 10 (not compatible with phone updated from Android 9) Requirements: * Adb must be up to date. You will use new fastbootd interface. You can toggle between bootloader and...
forum.xda-developers.com
Ignore steps 1-3 since you're using a different rom. Wiping userdata is optional - this will reset your phone to factory settings. Follow step 8 at your own risk - this resulted in a boot loop for me.
That's it! Once your phone boots up, you should have Advanced Calling in the Network & Internet settings menu. To gain root access, it seems as though Magisk doesn't work properly on the Moto G Power (someone correct me if I'm wrong). When attempting to patch the boot image, Magisk says "Downloading" then "Download Complete" instead of the typical "Flashing...". It still outputs some kind of image file, but flashing this file resulted in a bootloop for me. Maybe I'll try to patch the boot image from another device at some point, but for now I have WiFi Voice and Video calling on my (my wife's) XT2041-4. And she probably doesn't need root access anyway...
@clevertrevor777
Thank you for the guide. Is it possible to relock the bootloader afterwards or does this brick it?
Good question. Someone else would have to chime in on that. Why lock it anyway?
@nu_ninja
I got a Moto G Power from Google Fi and I was able to relock the bootloader right after following this guide. I did so before I booted it up initially. OEM Unlocking was still checked in developer options even after I locked the bootloader, so I can unlock it again later as needed.
Thank you Mr. Clever Trevor for figuring this out and sharing.
I have unlocked bootloader for my 2041-4. I have tried several VZW roms but it says boot failed each time. My question is when I type adb devices it says listing devices, but says "List of devices attached ___" and nothing happens with my phone. Thanks for the guide I hope I can get it working. Should I be using android 10 or 11 ROMs??
You really don't need to flash another rom just to enable volte and wifi calling, there just a few build.prop edits if you have root or this twrp flashabe zip: https://github.com/khrj/volte-fix
For manual method root or no root, open up /system/build.prop with root explorer or adb pull it to your pc add this snippet to the end and save it or adb push back making sure it has read/write permissions and voila volte and wifi calling will be enabled in the settings, works for custom roms as well.
Code:
# volte
persist.dbg.ims_volte_enable=1
persist.dbg.volte_avail_ovr=1
persist.dbg.vt_avail_ovr=1
persist.dbg.wfc_avail_ovr=1
persist.data.iwlan.enable=true (disable if problems with wifi calls)
persist.radio.rat_on=combine
persist.radio.data_ltd_sys_ind=1
persist.radio.data_con_rprt=1
persist.radio.calls.on.ims=1
Reboot the phone and check the settings or you can then dial *#*#4636#*#* and under phone information see if you have VOLTE provisioned.
==== 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.