Related
Alright, so I screwed up my watch a few days ago and it ended up not getting past the splash screen and going straight to recovery. Thanks to @z0mghii, I was able to get a TWRP backup of the system, boot, and data. I replaced this backup with my own so none of his data (if possible) could be taken advantage of. However, after flashing it, I was still unable to boot up. Here are the steps I took in order to get everything back to working order. Keep in mind this is for WREN, the small version. Some steps may be unnecessary.
1. Boot to TWRP
2. Go to advanced wipe
3. Wipe everything
4. Go to the link below and download the TWRP Backup
5. Create a backup of a small partition (like boot) on your watch to create the folder.
6. Plug watch into PC while in TWRP
7. Go to the watch's internal storage
8. Go to the TWRP folder
9. Go to the subfolder
10. Paste the downloaded backup folder into this folder, this should be with the one you created earlier
11. Restore this backup on your watch, be sure to check all the boxes
12. Reboot to the bootloader
13. Install ADB if you haven't already, I recommend the 15 second one
14. While the watch is in the bootloader and it is plugged in, type the following commands
fastboot erase cache
fastboot erase misc
fastboot reboot
https://drive.google.com/drive/folders/0B_HUnwYIrFskUW10UDZ0dXdHQzg (You might have to download each item and put them in a folder instead, unless I'm oblivious to something, sorry )
After this, your watch should boot up, then power back down, then boot back up again. This will be followed up by the boot animation and go to the welcome screen.
If any of you guys could provide me with the latest stock rom version TWRP backup or a stock recovery.img, it would be greatly appreciated. (Unless June patch is the latest). The recovery would be great no matter what. Getting the stock recovery can be done by typing the following commands into the command prompt on a PC. Hopefully they work. It should be copied onto the /sdcard.
Via adb shell (make sure ADB debugging is on in developer options, then type adb shell in CMD on PC) type: cat/proc/mtd and press enter
You will see which is recovery partition and then type: dd if=/dev/mtd/mtd1 of=/sdcard/recovery.img (note that mtd1 you must replace with number which is recovery partition)
I hope I helped somebody with this. Again, huge thanks to @z0mghii for making this possible. I'm sorry for bad formatting.
I'm really new to this. I'm also by no means a developer/hardcore android person. These commands were all taken from google. I take 0 responsibility for your device being ruined. This is just what worked for me.
Reserved
HOLY CRAP IT WORKED!! You just don't know how much this means to me, words can't express!
cland216 said:
HOLY CRAP IT WORKED!! You just don't know how much this means to me, words can't express!
Click to expand...
Click to collapse
Hell yeah. Glad I could help somebody! I've been wanting to give back to the wonderful XDA community for a while as a long time lurker. Also, I'm hoping to get a newer version of the stock rom and a stock recovery.img so you can go back to 100% factory stock for an OTA. I'm pretty proud of myself (being noobish) figuring this out.
Thanks a lot!! My watch was kept in a drawer because it was useless and it has now returned to life, I just have a problem restoring the recovery, the command to locate the recovery folder do not work me, have any idea how located the recovery folder?
klaudio_tv said:
Thanks a lot!! My watch was kept in a drawer because it was useless and it has now returned to life, I just have a problem restoring the recovery, the command to locate the recovery folder do not work me, have any idea how located the recovery folder?
Click to expand...
Click to collapse
Are you referring to "extracting" the recovery img? You only need to do it if you're running the stock recovery.
If so, I think I have screwed the command. Make sure you're in adb shell (in recovery on the watch) and then type "cat /proc/mtd" (with the space in front of cat) without the quotes in order to locate the recovery partition.
You will see which is recovery partition and then type: dd if=/dev/mtd/mtd1 of=/sdcard/recovery.img (note that mtd1 you must replace with number which is recovery partition)
Hopefully this works
Hi, my watch now works well, but I was not able to install updates, when I try to install updates from the watch, watch reboots and go to TWRP recovery. Anyone knows how install the updates?
klaudio_tv said:
Hi, my watch now works well, but I was not able to install updates, when I try to install updates from the watch, watch reboots and go to TWRP recovery. Anyone knows how install the updates?
Click to expand...
Click to collapse
Since the OP helped me, here's my chance to give back..
By no means do I know what hell I'm doing, but I know enough to be dangerous. If you're ready to live dangerously, follow these steps (which worked for me):
1. Go into TWRP on the watch and connect it usb to your computer. Using TWRP file manager, copy the update.zip from CACHE to sdcard\Download.
2. On the computer, browse to Zenwatch internal memory Downloads folder and copy the update.zip file to your computer.
3. Unzip the file on your computer using 7zip.
4. Navigate to \META-INF\com\google\android\ and look for updater-script.
5. Edit updater-script in Notepad++.
6. Delete the lines starting with getprop. This turned out to be lines 2 thru 5.
7. Delete the lines starting with apply_patch_check. This turned out to be lines 10 thru 176
8. Save changes to updater-script then in Windows Explorer highlight all of the files and folders that you unzipped, right-click them and click on 7zip --> Add to update.zip
9. Copy the new update.zip to the Zenwatch internal memory, Downloads folder, overwriting the original update.zip
10. Flash the update.zip file with TWRP.
11. Reboot TWRP to Bootloader.
12. On your computer, goto adb folder where you have fastboot files, and using command prompt type:
fastboot erase cache
fastboot erase misc
fastboot reboot
These steps worked as I was stuck on the June 1, 2016 Android security patch on my Wren Zenwatch. These steps helped me get to the September 1, 2016 security patch.
I managed to update my watch to the September 1 security patch using Cland216's method. But I am unable to update further using the method above. Does anyone have any info on how to update further? Or has any zip files to flash?
If we could get someone to upload the watches stock recovery that would solve all issues.....Why has noone done this for this model yet?
Sent from my OnePlus X using XDA Labs
I'm unable to create a backup file
5. Create a backup of a small partition (like boot) on your watch to create the folder.
6. Plug watch into PC while in TWRP
TWRP :
Could not mount /data
When I try to mount /data , I unable to /data
HOLY ****
Dude.. Let me just say...
YOU ARE THE ****ING ABSOLUTE BEST.
I am now going to make a backup, and save it to my computer, google drive, dropbox, icloud, and every other ****in place I can to make sure this never happens again. Thank you!!!!
Nicholas6706 said:
Alright, so I screwed up my watch a few days ago and it ended up not getting past the splash screen and going straight to recovery. Thanks to @z0mghii, I was able to get a TWRP backup of the system, boot, and data. I replaced this backup with my own so none of his data (if possible) could be taken advantage of. However, after flashing it, I was still unable to boot up. Here are the steps I took in order to get everything back to working order. Keep in mind this is for WREN, the small version. Some steps may be unnecessary.
1. Boot to TWRP
2. Go to advanced wipe
3. Wipe everything
4. Go to the link below and download the TWRP Backup
5. Create a backup of a small partition (like boot) on your watch to create the folder.
6. Plug watch into PC while in TWRP
7. Go to the watch's internal storage
8. Go to the TWRP folder
9. Go to the subfolder
10. Paste the downloaded backup folder into this folder, this should be with the one you created earlier
11. Restore this backup on your watch, be sure to check all the boxes
12. Reboot to the bootloader
13. Install ADB if you haven't already, I recommend the 15 second one
14. While the watch is in the bootloader and it is plugged in, type the following commands
fastboot erase cache
fastboot erase misc
fastboot reboot
https://drive.google.com/drive/folders/0B_HUnwYIrFskUW10UDZ0dXdHQzg (You might have to download each item and put them in a folder instead, unless I'm oblivious to something, sorry )
After this, your watch should boot up, then power back down, then boot back up again. This will be followed up by the boot animation and go to the welcome screen.
If any of you guys could provide me with the latest stock rom version TWRP backup or a stock recovery.img, it would be greatly appreciated. (Unless June patch is the latest). The recovery would be great no matter what. Getting the stock recovery can be done by typing the following commands into the command prompt on a PC. Hopefully they work. It should be copied onto the /sdcard.
Via adb shell (make sure ADB debugging is on in developer options, then type adb shell in CMD on PC) type: cat/proc/mtd and press enter
You will see which is recovery partition and then type: dd if=/dev/mtd/mtd1 of=/sdcard/recovery.img (note that mtd1 you must replace with number which is recovery partition)
I hope I helped somebody with this. Again, huge thanks to @z0mghii for making this possible. I'm sorry for bad formatting.
I'm really new to this. I'm also by no means a developer/hardcore android person. These commands were all taken from google. I take 0 responsibility for your device being ruined. This is just what worked for me.
Click to expand...
Click to collapse
I spoke just a bit too soon, now it is hanging on that animation with the 4 dots. Any suggestions?
NEVERMIND, I AM UP AND RUNNING!! WOOHOOOO
This guide is to help anyone who wants to use Android Pay but his XC phone is unlocked and rooted. It begins with an unlocked phone with a valid backup of the TA partition as well as an unrooted /system partition.
Prerequisites:
1. A backup of TA partition (https://forum.xda-developers.com/crossdevice-dev/sony/universal-dirtycow-based-ta-backup-t3514236)
2. Unlocked bootloader
3. Working fastboot driver and command
4. Clean /system partition without any trace of su. Systemless root is fine because it will be overwritten by the new kernel. If needed, flash the stock system partition again.
5. TWRP image for XC (https://drive.google.com/open?id=0B0j3VJ1Xp5N8M1ZGbzBBMTdyRnM)
6. Stock kernel image (Extract kernel.sin from official FTF)
7. Trim Area Proof Of Concept (https://forum.xda-developers.com/crossdevice-dev/sony/poc-real-trim-instead-drm-fix-t3552893)
8. Tobias kernel repack tool (https://forum.xda-developers.com/xp...oot-automatic-repack-stock-kernel-dm-t3301605)
9. Magisk v12.0 flashable zip, not Manager app (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445)
Procedures:
1. Run TA PoC (DOUBLECLICKME.bat). You'll be asked to select your kernel image (kernel.sin) and TA backup (your TA backup file). Choose also to disable DM-Verity, Sony RIC but keep Force-encrypt (my data partition is encrypted, your choice). At the end a new file new_boot.img will be created.
2. Copy the new_boot.img in step 1 to Tobias tool folder. In the same folder, execute the following command. Again, disable Sony RIC, don't install TWRP, don't install DRM fix and don't install Busybox. At the end, another file boot.img will be created.
Code:
rootkernel.cmd new_boot.img boot.img
3. Power off your phone. Power on again while holding volume up rocker to enter fast boot mode. Execute the following command to flash the new boot image. Replace boot.img with your new image in step 2 with full path.
Code:
fastboot.exe flash boot [I]boot.img[/I]
4. Reboot your phone. No root or SuperSU app should be found.
5. Copy Magisk zip file into phone internal storage.
6. Dial *#*#7378423#*#*, followed by Service Test > Security to check if DRM is detected properly. At this point of time, your phone should be su free and DRM working properly.
7. Power off your phone. Power on again while holding volume up rocker to enter fast boot mode. Execute the following command to boot TWRP. Replace twrp.img with your TWRP image with full path.
Code:
fastboot.exe boot [I]TWRP.img[/I]
8. In TWRP, flash Magisk zip
9. Reboot your phone. Install Magisk Manager app (no long available in Play Store) (http://tiny.cc/latestmanager)
10. Run Magisk Manager and turn on Magisk Hide. You should see Magisk installed successfully and properly rooted with MagiskSU. Tap SafetyNet button to check if it can be passed.
11. (optional) Install Xposed using Magisk app, not official method. Xposed will break Safety Net again. But you can always disable it in Magisk Manager easily.
Remarks:
1. Trim Area Proof Of Concept is required to restore full DRM functionality so that Safety Net thinks the phone is still locked.
2. /system partition must be clean and free of any trace of previous su installation.
3. Magisk Manager app cannot be used to install Magisk because it requires root in the first place. Even with systemless root, after Magisk is installed this way, trace of su can be found in /vendor partition.
4. Tobias tool has to be used to repack the boot image because I found that if PoC image is used directly, phone will reboot unexpectedly after Magisk is installed.
This is the clearest guide I found so far for rooting x compact :good: (Your old guide also help me understand some of the concept)
I get most of the steps but want to confirm whether I understand it correctly
itandy said:
1. Run TA PoC (DOUBLECLICKME.bat). You'll be asked to select your kernel image (kernel.sin) and TA backup (your TA backup file). Choose also to disable DM-Verity, Sony RIC but keep Force-encrypt (my data partition is encrypted, your choice). At the end a new file new_boot.img will be created.
Click to expand...
Click to collapse
TA PoC modify the boot image and the modified boot image will mount the TA backup image during boot and "trick" the system/kernel into thinking that is the original TA Partition, and it is untouched.
itandy said:
2. Copy the new_boot.img in step 1 to Tobias tool folder. In the same folder, execute the following command. Again, disable Sony RIC, don't install TWRP, don't install DRM fix and don't install Busybox. At the end, another file boot.img will be created.
Click to expand...
Click to collapse
- Drm fix is not needed because of the trick in step 1. This step is only needed because of incompatibility of boot image generated from step 1 with magisk (mentioned in the remarks section.).
- TWRP is not needed because in this guide TWRP will be booted by fastboot through PC without actually installing it on the phone (Step 7)
- Busybox is now included in magisk I think?
itandy said:
6. Dial *#*#7378423#*#*, followed by Service Test > Security to check if DRM is detected properly. At this point of time, your phone should be su free and DRM working properly.
Click to expand...
Click to collapse
- This is to prove the TA PoC mount trick above is working. No kernel fix is done.
The advantage of this method instead of kernel drm fix is that you can have completely stock kernel/system and only have modified boot image (and some extra data in data partition). Can you theoretically update the system and exclude the boot and data partition and still have the root intact? Or is that not recommended as new update might have some change in the boot partition as well?
I still need to do more reading about magisk and why the manager need to be installed manually (and what does it do)
trewelu said:
This is the clearest guide I found so far for rooting x compact :good: (Your old guide also help me understand some of the concept)
I get most of the steps but want to confirm whether I understand it correctly
TA PoC modify the boot image and the modified boot image will mount the TA backup image during boot and "trick" the system/kernel into thinking that is the original TA Partition, and it is untouched.
- Drm fix is not needed because of the trick in step 1. This step is only needed because of incompatibility of boot image generated from step 1 with magisk (mentioned in the remarks section.).
- TWRP is not needed because in this guide TWRP will be booted by fastboot through PC without actually installing it on the phone (Step 7)
- Busybox is now included in magisk I think?
- This is to prove the TA PoC mount trick above is working. No kernel fix is done.
The advantage of this method instead of kernel drm fix is that you can have completely stock kernel/system and only have modified boot image (and some extra data in data partition). Can you theoretically update the system and exclude the boot and data partition and still have the root intact? Or is that not recommended as new update might have some change in the boot partition as well?
I still need to do more reading about magisk and why the manager need to be installed manually (and what does it do)
Click to expand...
Click to collapse
Your understanding is correct. As for busybox, I didn't install it because I don't use it. You can try and see if it affects Safety Net detection.
Yes, system partition can be updated without losing root.
trewelu said:
This is the clearest guide I found so far for rooting x compact :good: (Your old guide also help me understand some of the concept)
I get most of the steps but want to confirm whether I understand it correctly
TA PoC modify the boot image and the modified boot image will mount the TA backup image during boot and "trick" the system/kernel into thinking that is the original TA Partition, and it is untouched.
- Drm fix is not needed because of the trick in step 1. This step is only needed because of incompatibility of boot image generated from step 1 with magisk (mentioned in the remarks section.).
- TWRP is not needed because in this guide TWRP will be booted by fastboot through PC without actually installing it on the phone (Step 7)
- Busybox is now included in magisk I think?
- This is to prove the TA PoC mount trick above is working. No kernel fix is done.
The advantage of this method instead of kernel drm fix is that you can have completely stock kernel/system and only have modified boot image (and some extra data in data partition). Can you theoretically update the system and exclude the boot and data partition and still have the root intact? Or is that not recommended as new update might have some change in the boot partition as well?
I still need to do more reading about magisk and why the manager need to be installed manually (and what does it do)
Click to expand...
Click to collapse
Just found that you can actually enable busybox in Magisk Manager so you don't have to pack it into the boot image.
Sent from my F5321 using Tapatalk
Done the step above and gained root and pass safety check in magisk.
Is there a way to disable the bootloader unlocked message during boot? I don't mind the message but it delay booting process I
trewelu said:
Done the step above and gained root and pass safety check in magisk.
Is there a way to disable the bootloader unlocked message during boot? I don't mind the message but it delay booting process I
Click to expand...
Click to collapse
I'm not aware anyone is able to do that so far.
itandy said:
I'm not aware anyone is able to do that so far.
Click to expand...
Click to collapse
You would need to alter bootloader....
Remark for Android 7.0 Users
If you will use this guide on Nougat, you will need to DISABLE force-encrypt, because data partition is encrypted by default on Nougat. On top of that, you will need to first boot to TWRP, wipe DATA partition without decrypting / mounting it and then reboot system to re-create unencrypted data partition. Only then you can flash Magisk..
ondrejvaroscak said:
If you will use this guide on Nougat, you will need to DISABLE force-encrypt, because data partition is encrypted by default on Nougat. On top of that, you will need to first boot to TWRP, wipe DATA partition without decrypting / mounting it and then reboot system to re-create unencrypted data partition. Only then you can flash Magisk..
Click to expand...
Click to collapse
Just curious, I'm on MM and my data partition is encrypted. But I didn't have to decrypt it first before installing Magisk. Is there anything on Nougat that makes it different?
itandy said:
Just curious, I'm on MM and my data partition is encrypted. But I didn't have to decrypt it first before installing Magisk. Is there anything on Nougat that makes it different?
Click to expand...
Click to collapse
Yes, quite substantially .... the TWRP does NOT support /data decryption on Nougat. On MM it works, on Nougat there is no way, until someone compiles TWRP with support for Nougat encrypted /data. The workaround is to DISABLE force-encrypt, wipe /data to force re-create unencrypted /data, install anything you need and then encrypt in Settings/Security. Once you do it, there is no way to get into /data in recovery...
ondrejvaroscak said:
Yes, quite substantially .... the TWRP does NOT support /data decryption on Nougat. On MM it works, on Nougat there is no way, until someone compiles TWRP with support for Nougat encrypted /data. The workaround is to DISABLE force-encrypt, wipe /data to force re-create unencrypted /data, install anything you need and then encrypt in Settings/Security. Once you do it, there is no way to get into /data in recovery...
Click to expand...
Click to collapse
And why is data partition decryption support needed in TWRP in this case? Flashing Magisk requires modification on data partition?
itandy said:
And why is data partition decryption support needed in TWRP in this case? Flashing Magisk requires modification on data partition?
Click to expand...
Click to collapse
I don't think so. I just re-did the step (accidentally locked back my bootloader when trying to remove the unlocked message). On twrp, it ask for password which I don't even know as after BL unlock wipe, I haven't set my screen lock yet. I skip that part, mount the sd card and flash magisk. Magisk modify the boot image and I can have root and safety net working.
Ps: You might need to update the step, the magisk manager stub will force you to download the app from play store, but it is already pulled. I need to download the app directly from magisk thread and side load it.
Edit: I was wrong. Magisk do use /data for magisk.img, but it have workaround instalation in case it is inaccessible during flashing install script. See #15
trewelu said:
Ps: You might need to update the step, the magisk manager stub will force you to download the app from play store, but it is already pulled. I need to download the app directly from magisk thread and side load it.
Click to expand...
Click to collapse
Updated. Thanks!
itandy said:
And why is data partition decryption support needed in TWRP in this case? Flashing Magisk requires modification on data partition?
Click to expand...
Click to collapse
Magisk installs file magisk.img into /data. This file is than mounted as /magisk. I am not sure, how Magisk handles installation if /data is not accesible/mountable during flashing, did not try it.
ondrejvaroscak said:
Magisk installs file magisk.img into /data. This file is than mounted as /magisk. I am not sure, how Magisk handles installation if /data is not accesible/mountable during flashing, did not try it.
Click to expand...
Click to collapse
I'm not good with script, but here is my understanding,
In case of inaccessible data during flash, magisk will flash magisk.img temporarily in cache partition. During booting (after data is unencrypted), magisk check if the workaround image in cache exist and move it to data
scripts/flash_script.sh
Code:
if (is_mounted /data); then
IMG=/data/magisk.img
else
IMG=/cache/magisk.img
ui_print "- Data unavailable, use cache workaround"
fi
jni/daemon/bootstages.c
Code:
// Merge images
if (merge_img("/cache/magisk.img", MAINIMG))
goto unblock;
if (merge_img("/data/magisk_merge.img", MAINIMG))
goto unblock;
jni/magisk.h
Code:
#define MAINIMG "/data/magisk.img"
trewelu said:
I'm not good with script, but here is my understanding,
In case of inaccessible data during flash, magisk will flash magisk.img temporarily in cache partition. During booting (after data is unencrypted), magisk check if the workaround image in cache exist and move it to data
Click to expand...
Click to collapse
Cool, very clever. I did not make the effort to study in in depth, but expected some sort of solution to exist when users succesfully installed Magisk even when they can not mount /data in TWRP. This temporary /cache mount is just nice example of clever programming
Hey, I think I pseudo-bricked my device while following these steps. I used fastboot to boot into TWRP, without disabling encryption, on Nougat 7.1. I didn't notice the requirement to disable encryption in Post #8 until afterwards.
Now the device appears to be on (my computer detects an unknown device when I plug it in), but it doesn't show any LEDs or react to any buttons. Is my only recourse to wait till the battery dies in a few days and try again, or is there another way?
HAHA, I found if I hold EVERY button (power, vol up, vol dn, and camera), the phone restarts and I have access again. w00t!
Just wondering if somebody tried this with Nougat 7.1? I can't get TA_POC to work, security test displays error and sim card is not detected.
baz1 said:
Just wondering if somebody tried this with Nougat 7.1? I can't get TA_POC to work, security test displays error and sim card is not detected.
Click to expand...
Click to collapse
Yes this works with 7.1 the same as with 7.0. How did you perform the update to 7.1?
I followed the guide to perfection, and everything works perfectly...but...If I want to turn a user app into system apps, link2sd gives me this error: mount: '/dev/block/bootdevice/by-name/system'->'/system': Device or resource busy" and system app mover gives me this error : "could not remount /system".
is system read only? why? I've already tried to enable "rw" "ro" through the command line without success...
Can anyone help me?
p.s. I have granted root permissions to the applications mentioned above at their opening
Please help! I am a noob here. i was using resurrection remix 5.8.3 then I flashed xiaomi.eu without making a backup. Now when I tried to boot my phone, it ask for the decryption pattern but my pattern is 6x6 and it only shows 3x3. So I went back to twrp and then I made several mistakes in putting the decryption pattern. When I put the correct pattern it doesn't decrypt. Please help I need to recover my files because the data for my research is in my phone
Try to pass out your Google account.
Easy Fix
If you have TWRP or any Custom Recovery Easy Job !
Boot to TWRP
Go to advanced>filemanager to access the files in your phone.
Go to the /data/system folder. Scroll down and find the two files with the .key extension. Delete both of them (by tapping on the file and then tapping the �Delete� button). Then, delete all the files containing the word
locksettings.
password.key
pattern.key
locksettings.db
locksettings.db-shm
locksettings.db-wal
Make sure you deleted them ! Reboot with no lock
credit - adithyan25
OK to start off this thread is meant to continue the work done in the thread here huawei-ascend-xt2-h1711 their were some good people working on stuff their but most seem to have moved on.
I decided to pick up the Elate this week from Best Buy and thought it might be time to start a new thread on rooting and restoring the Cricket version of this phone.
Rooting the H1711z Huawei Elate
First step is to unlock your bootloader at Huawei here > https://emui.huawei.com/en/unlock_detail
Well it seems Huawei is no longer unlocking the bootloader so you need to pay DC Unlocker to unlock your bootloader
follow the instructions posted here >> https://forum.xda-developers.com/honor-7x/how-to/how-to-unlock-huawei-bootloader-removal-t3780903
Also please make a backup of your own boot.img as soon as you flash TWRP before flashing the patched _boot.img provided
~Huge thanks to @aslezak for these instructions~
Root instructions: (I used Magisk Manager v5.5.3 boot.img patching to create the boot.img)
here is the stock boot.img for the Elate H1711z
I am not responsible if you brick your device. I didn't brick mine, but if you don't type the correct commands you could be in trouble
Copy this patched_boot.zip to your sdcard. You can download it from the device directly if that's easier. Insert the sdcard into the phone if it wasn't there already (e.g. if you downloaded from a computer).
Reboot phone into fastboot. The easiest way is, if phone is on, unplug phone from USB, hold power button / select "Power Off". Hold VolDown+Power. Phone will boot into fastboot mode.
(skip this step if you've already flashed TWRP) Flash TWRP into your recovery partition. The link was provided in an earlier post by yuweng twrp-xt2-v3.img
plug usb cable in (from phone to computer). From your computer / cmd.exe window, cd \adb:
fastboot devices #make sure computer adb/fastboot sees your device
fastboot flash recovery twrp_xt2_v3.img
Boot into TWRP. From the above step, you should "fastboot reboot", immediately unplug phone from USB, then
With the phone unplugged from the computer, hold VolUp+Power. Release power after the device reboots. It might take a couple tries .. select reboot from eRecovery if that starts instead. Alternatively you can boot into recovery through adb via "adb reboot recovery".
Tap "Keep Read Only" when TWRP starts.
Tap "Install", then tap "Install Image" at the bottom. Browse (Up a Level) then "external_sd"
If you unzipped the patched_boot.zip you will see patched_boot.img here. Select it.
Select "boot" (uncheck "recovery") partition to flash.
Swipe to confirm Flash
Tap "Reboot" once it's completed.
You should be rooted!
Note: if Magisk Manager does not appear in your list of installed applications, download & install it from here latest Magisk Manager. Without this, you won't be prompted to allow root!
Click to expand...
Click to collapse
Note: Magisk Manager will update you to version 16 on first run, it's OK to update in fact feel free to flash it in recovery before you reboot if you want it.
A couple notes about twrp_xt2_v3.img
when you start TWRP choose keep system read only - Unless your planing to restore a backup then choose to make system writable
You cannot backup or restore /data (it's encrypted so don't even try)
Do not use Wipe / factory reset or format data unless you have a good working backup of your userdata partition that you dd to your external_sd yourself see below
From TWRP / adb shell
paste these commands
dd if=/dev/block/bootdevice/by-name/userdata | bzip2 -9f > /external_sd/userdata.img.bz2
to restore--> bzip2 -dc /external_sd/userdata.img.bz2 | dd of=/dev/block/bootdevice/by-name/userdata
dd if=/dev/block/bootdevice/by-name/system | bzip2 -9f > /external_sd/system.img.bz2
to restore--> bzip2 -dc /external_sd/system.img.bz2 | dd of=/dev/block/bootdevice/by-name/system
again thanks go to aslezak
When choosing a backup always prefer the image instead of the stock files (system image - custom image - vendor image are best )(Never choose both system and system image at the same time it's too big and a waste of time and space)
when you exit TWRP do not choose to install the twrp app
Also be sure and thank aslezak for his post here > https://forum.xda-developers.com/showpost.php?p=75115521&postcount=286
Notes on booting up the phone (from power off)
Bootloader (fastboot) = power + volume down + USB hooked to pc
eRecovery = power + volume up + USB hooked to PC
TWRP = power + volume up
Restoring your phone to Stock
We now have the B120 Stock dload update See here >> https://forum.xda-developers.com/showthread.php?p=76902495&highlight=dload#post76902495
I've created a Stock Rom to easily return your phone to Stock Factory Settings (b120)
Warning this will completely Wipe your phoneTo Install
1) Download and copy the H1711z_stock_ROM_v2.zip to your external_sd
2) Boot to TWRP recovery
3) Go to Settings check Use rm -fr instead of formatting / Wipe / Format Data / Type "yes" to confirm
4) Choose Home / Install /Select storage Micro sd / H1711z_stock_ROM_v2.zip / swipe to install
5) when it finishes choose the wipe cache button and then reboot and choose Do not Install
Your phone is now back to stock
Extra's By Request
Here's the XT2_Stock_Rom and XT2_Magisk_ Rom here > https://androidfilehost.com/?w=files&flid=266256
If you like to try my CleanRom for the Elate I uploaded it here >> Elate.CleanRom.v2.zip
flashing instructions are the same as the stock file above
here's whats added/removed
Apps deleted from /Data/hwinit/:
Google Editor Slides
Google Editor Sheets
Google Editor Docs
Apps deleted from Cust:
the entire h1711 folder
AT&T Remote Support
myAT&T
AT&T Visual Voicemail
AT&T Hot Spots
Google Talkback
OMACP
Apps deleted from System:
Amazon shopping
App select
Call Protect
CricketWiFiManager
Device Help
Deezer
Facebook
Facebook App Installer
Facebook app manager
Gmail
Google Duo
Google Chrome
Google Drive
Google Maps
Google Play Photos
Google Play Video
Google Play Music
Google Text to Speech Engine
Ignite
Lookout
myCricket
Protect Plus
Setup & Transfer
Added
FX Root File Manager (as a system App)
Magisk V16 (as a system App)
QuickBoot Reboot (as a system App)
I didn't include Xposed because it's useless without a decrypted Data partition
Note: To remove the Cricket bootanimation, use the FX File Manager with root permission and rename
..\system\version\special_cust\H1711z\cricket\us\media\bootanimation.zip" to bootanimation.zi_ and reboot
I got tired of seeing the error in twrp_v3 about not mounting patch_hw and fixed it ->> Here
you can unzip it and flash it to recovery with TWRP or fastboot
NOTE: added by scrungydoolittle I had a problem with the bz2 image. I prefer to not run it through bz2
dd if=/dev/block/bootdevice/by-name/userdata /external_sd/userdata.img
to restore--> dd if=/external_sd/userdata.img of=/dev/block/bootdevice/by-name/userdata
dd if=/dev/block/bootdevice/by-name/system /external_sd/system.im
to restore--> dd if= /external_sd/system.img of=/dev/block/bootdevice/by-name/system
Of course, the downside is you need a fairly large external sd card.
@scrungydoolittle Please edit you post and remove the Quote of the first post
also the file you posted is not for this phone please remove the link
as to you having problems with the bz2 image they work fine if you follow the instructions
I instructed the user to create their OWN backup of userdata before they format / wipe their data partition
this file most likely contains the users IMEI and should not be shared.
clsA said:
@scrungydoolittle Please edit you post and remove the Quote of the first post
also the file you posted is not for this phone please remove the link
as to you having problems with the bz2 image they work fine if you follow the instructions
I instructed the user to create their OWN backup of userdata before they format / wipe their data partition
this file most likely contains the users IMEI and should not be shared.
Click to expand...
Click to collapse
O.k. I removed the link. It was for the H1711 AT&T phone as it turns out.
And I don't think that image has the IMEI in it, because it is clearly the /system image, and I don't think that data is stored in that partition.
Otherwise all of the posted system images would have the same issue...
scrungydoolittle said:
O.k. I removed the link. It was for the H1711 AT&T phone as it turns out.
And I don't think that image has the IMEI in it, because it is clearly the /system image, and I don't think that data is stored in that partition.
Otherwise all of the posted system images would have the same issue...
Click to expand...
Click to collapse
Thanks ...yeah the userdata contains the IMEI not the system.img
Sent from my LG-H910 using Tapatalk
I would not share a userdata backup unless it was after a factory reset and before I entered any personal account information or data. Agree with you on that
I'd love to see a reliable reference that says userdata contains the IMEI or if you know specifically where it's stored, because l thought IMEI is stored in a totally different partition.
clsA said:
Thanks ...yeah the userdata contains the IMEI not the system.img
Sent from my LG-H910 using Tapatalk
Click to expand...
Click to collapse
divineBliss said:
I would not share a userdata backup unless it was after a factory reset and before I entered any personal account information or data. Agree with you on that
I'd love to see a reliable reference that says userdata contains the IMEI or if you know specifically where it's stored, because l thought IMEI is stored in a totally different partition.
Click to expand...
Click to collapse
IMEI is stored in data/data/com.android.phone
Thank you
Found the IMEI in
/data/data/com.android.phone/shared_prefs/
com.android.phone_preferences.xml on my H1611 after your post.
I'm guessing the IMEI is copied from another partition, but the fact that it's in /data is news to me.
I wonder if the IMEI is in the above file after a factory reset , but I'm not planning to find out anytime soon .
People, be careful sharing your userdata partition backups and other sensitive data containing partition backups out there - unless of course you don't give a crap about security - which you should preface up front so as to not mislead uninformed people of the risks involved in sharing those sensitive data partitions.
clsA said:
IMEI is stored in data/data/com.android.phone
Click to expand...
Click to collapse
It sure would be nice to get one of these stock flash zip's for the H1711 XT2. Would this zip work on it?
clsA said:
Restoring your phone to Stock
I've created a Stock Rom to easily return your phone to Stock Factory Settings (b120)
Warning this completely Wipe your phoneTo Install
1) Download and copy the H1711z_stock_ROM_v2.zip to your external_sd
2) Boot to TWRP recovery
3) Go to Settings check Use rm -fr instead of formatting / Wipe / Format Data / Type "yes" to confirm
4) Choose Home / Install /Select storage Micro sd / H1711z_stock_ROM_v2.zip / swipe to install
5) when it finishes choose the wipe cache button and then reboot and choose Do not Install
Your phone is now back to stock
Click to expand...
Click to collapse
freedomwarrior said:
It sure would be nice to get one of these stock flash zip's for the H1711 XT2. Would this zip work on it?
Click to expand...
Click to collapse
Nice.
What partitions does this install?
And can you make this for the H1711 At&T phone?
freedomwarrior said:
It sure would be nice to get one of these stock flash zip's for the H1711 XT2. Would this zip work on it?
Click to expand...
Click to collapse
No don't use this on the XT2
I / you need system/boot/recovery/ and cust.img files from a XT2 to build it.
Sent from my LG-H910 using Tapatalk
clsA said:
No don't use this on the XT2
I / you need system/boot/recovery/ and cust.img files from a XT2 to build it.
Sent from my LG-H910 using Tapatalk
Click to expand...
Click to collapse
If I send you (or point you to )
system
boot
recover
and cust images could you create one?
The image for system is available, a patched bootloader that installs magisk, an unpatched boot loader, the recovery and e recovery are the same.
I'd like to see 2 flashable zips.
1. that does stock
2. that installs twrp and magisk.
I have all those, but I'm not sure how to make the zip. Is it simply a matter of opening it in a zip prgram and replacing the mentioned image files
with appropriate ones?
scrungydoolittle said:
If I send you (or point you to )
system
boot
recover
and cust images could you create one?
The image for system is available, a patched bootloader that installs magisk, an unpatched boot loader, the recovery and e recovery are the same.
I'd like to see 2 flashable zips.
1. that does stock
2. that installs twrp and magisk.
I have all those, but I'm not sure how to make the zip. Is it simply a matter of opening it in a zip prgram and replacing the mentioned image files
with appropriate ones?
Click to expand...
Click to collapse
I have the Stock system.img and erecovery.img
put the others in a google drive and I'll build them
clsA said:
I have the Stock system.img and erecovery.img
put the others in a google drive and I'll build them
Click to expand...
Click to collapse
Here is the cust.img I just pulled from my XT2 using the dd command.
https://drive.google.com/open?id=1euUHZiJrzfyUVNqgOT76rTk45clPwv9F
Here is a copy of the stock boot I have had sitting on my hard drive.
https://drive.google.com/open?id=1-dAJuwgYdM9F3fBn4dU3x9s74SucocBP
And here is a copy of patched boot (with magisk) if you need it.
https://drive.google.com/open?id=1Tfb7zkcX6auoYEVnMLKDN6tibfzHSPEW
And thank you in advance for doing this! :good:
freedomwarrior said:
Here is the cust.img I just pulled from my XT2 using the dd command.
https://drive.google.com/open?id=1euUHZiJrzfyUVNqgOT76rTk45clPwv9F
Here is a copy of the stock boot I have had sitting on my hard drive.
https://drive.google.com/open?id=1-dAJuwgYdM9F3fBn4dU3x9s74SucocBP
And here is a copy of patched boot (with magisk) if you need it.
https://drive.google.com/open?id=1Tfb7zkcX6auoYEVnMLKDN6tibfzHSPEW
And thank you in advance for doing this! :good:
Click to expand...
Click to collapse
Files are uploading now > https://www.androidfilehost.com/?w=files&flid=257749
Instructions are the same
Backup anything on internal storage it will be wiped
To Install
1) Download and copy the Rom to your external_sd
2) Boot to TWRP recovery
3) Go to Settings check Use rm -fr instead of formatting / Wipe / Format Data / Type "yes" to confirm
4) Choose Home / Install /Select storage Micro sd / your_rom.zip / swipe to install
5) when it finishes choose the wipe cache button and then reboot and choose Do not Install
Your phone is now back to stock
Click to expand...
Click to collapse
after flashing the Magisk rom install the magisk manager and update to v16 (or whatever the newest is)
Awesome! Thank you so much for these. They will definitely come in handy! Much Appreciated!! :good::
clsA said:
OK to start off this thread is meant to continue the work done in the thread here huawei-ascend-xt2-h1711 their were some good people working on stuff their but most seem to have moved on.
Does this wipe out the recovery, and relock the bootloader, or will the bootloader remain unlocked, and twrp remain in place?
Thanks for the XT2 versions.
I decided to pick up the Elate this week from Best Buy and thought it might be time to start a new thread on rooting and restoring the Cricket version of this phone.
Rooting the H1711z Huawei Elate
First step is to unlock your bootloader at Huawei here > https://hwid5.vmall.com/CAS/portal/...ndex&loginChannel=22000000&reqClientType=2023
Also please make a backup of your own boot.img as soon as you flash TWRP before flashing the patched _boot.img provided
~Huge thanks to @aslezak for these instructions~
Note: Magisk Manager will update you to version 16 on first run, it's OK to update in fact feel free to flash it in recovery before you reboot if you want it.
A couple notes about twrp_xt2_v3.img
when you start TWRP choose keep system read only - Unless your planing to restore a backup then choose to make system writable
You cannot backup or restore /data (it's encrypted so don't even try)
Do not use Wipe / factory reset or format data unless you have a good working backup of your userdata partition that you dd to your external_sd yourself see below
From TWRP / adb shell
paste these commands
dd if=/dev/block/bootdevice/by-name/userdata | bzip2 -9f > /external_sd/userdata.img.bz2
to restore--> bzip2 -dc /external_sd/userdata.img.bz2 | dd of=/dev/block/bootdevice/by-name/userdata
dd if=/dev/block/bootdevice/by-name/system | bzip2 -9f > /external_sd/system.img.bz2
to restore--> bzip2 -dc /external_sd/system.img.bz2 | dd of=/dev/block/bootdevice/by-name/system
again thanks go to aslezak
When choosing a backup always prefer the image instead of the stock files (system image - custom image - vendor image are best )(Never choose both system and system image at the same time it's too big and a waste of time and space)
when you exit TWRP do not choose to install the twrp app
Also be sure and thank aslezak for his post here > https://forum.xda-developers.com/showpost.php?p=75115521&postcount=286
Notes on booting up the phone (from power off)
Bootloader (fastboot) = power + volume down + USB hooked to pc
eRecovery = power + volume up + USB hooked to PC
TWRP = power + volume up
Restoring your phone to Stock
I've created a Stock Rom to easily return your phone to Stock Factory Settings (b120)
Warning this will completely Wipe your phoneTo Install
1) Download and copy the H1711z_stock_ROM_v2.zip to your external_sd
2) Boot to TWRP recovery
3) Go to Settings check Use rm -fr instead of formatting / Wipe / Format Data / Type "yes" to confirm
4) Choose Home / Install /Select storage Micro sd / H1711z_stock_ROM_v2.zip / swipe to install
5) when it finishes choose the wipe cache button and then reboot and choose Do not Install
Your phone is now back to stock
By request I have also added the XT2_Stock_Rom and XT2_Magisk_ Rom here > https://www.androidfilehost.com/?w=files&flid=257749
Click to expand...
Click to collapse
Does this wipe out the recovery, and relock the bootloader, or will the bootloader remain unlocked, and twrp remain in place?
Thanks for the XT2 versions.
scrungydoolittle said:
Does this wipe out the recovery, and relock the bootloader, or will the bootloader remain unlocked, and twrp remain in place?
Thanks for the XT2 versions.
Click to expand...
Click to collapse
Really ?? You quoted the first post again
Flashing a Rom will never relock your bootloader
All 3 roms wipe TWRP
Sent from my LG-H910 using Tapatalk
@scrungydoolittle,
I was going to say the same.. .. The reason for clsAs comment is.. .
It's considered bad practice to post the OP or any other long posts unnecessarily. It makes it extremely difficult and annoying for others to wade past the huge quoted post to see what you said.
You can just quote the relevant part of a post (as I did below), refer to post 1 as the OP, or put a link to the post you are referring to.
Hopefully this explanation will get you to edit your last post and reconsider quoting long posts in the future.
Thanks
PS: Consider the fact that some of us read forums via email, XDA forum app, and browsers on mobile devices which have limited screen real estate and require more scrolling than a large desktop monitor.
clsA said:
Really ?? You quoted the first post again
...
Click to expand...
Click to collapse
I'm hoping for some help in rooting my Elate. I was able to get the unlock code from Huawei. I downloaded the ADB and Fastboot drivers from the Android Tutorials page.
ADB recognizes my device when in normal mode. But when I reboot into Bootloader mode, the device is not recognized. It does not show up in Windows device manager and the command "adb devices" is null. I can't get past this point which is clearly a driver problem.
I also have installed and uninstalled Hi-suite a number of times.
Does anyone have any advice? Thanks.
Every time I try to install a custom rom, my device gets bricked. I'm stuck in a bootloop and TWRP tells me, that /data is unusable and /system can't be unmounted.
Right now I get I back to life, if I change the filesystem in TWRP for /data from f2fs to ext4 and back. After that /data is empty, but usable again. To get /system back to work, I erase it with "fastboot erase system". Then I reboot TWRP and reinstall STF-L09 8.0.0.360(C432) with zxz0O0s HuRUpdater. The logfile for the installation is attached with the title "Log during installation.zip".
After the installation I do a reboot and go through all the setup stuff of Android (WLAN, do you want to use..., etc.). Then everything seems to work fine. I can use the phone and reboot without a problem. But if I start TWRP, there are error messages about it can't unmount /system. I attached that logfile with the title "Log after Installation.zip". If I try to install an OTA update it gets bricked again.
No matter, how I try to install the custom rom, or how I reset my phone after it gets bricked, seems to make a difference. To me it seems like, either a problem with the file system, or a driver problem. But I'm not sure, because I'm more experienced with PCs. If I would have such a problem with a PC, I would erase everything and do a fresh start. But I don't know how to handle this here.
Please help me, to get out of this bricking cycle, before I can build a wall.
Status Update 1:
I went back to STF-L09C432B120 (Android 7) with this method: https://forum.xda-developers.com/showpost.php?p=75084955&postcount=17
All credits to gaguga:
Rollback from 8 android to 7
1. Place the firmware files of ?any? android 7 update.zip, update_data_public.zip and update_all_hw.zip in the HWOTA8 / repack folder. (I used STF-L09C432B120)
2. Run the bat file "repack" to repackage the zip files. This will prepare our firmware
I had a problem with this and had to update the file META-INF\com\google\android\update-binary by hand.
3. Create the folder "HWOTA8" on the SD card. (Without quotes)
4. Place the archive hwota8_update.zip, STF_RECOVERY8_NoCheck.IMG (from the HWOTA8 folder) and the three update archives (update.zip, update_data_public.zip and update_all_hw.zip (from the repack folder after repackaging)) to the "HWOTA8" folder on the sd card.
5. Boot into the TWRP
6. Install the hwota8_update.zip file which lies in the HWOTA8 folder on the sd card. The phone will reboot into the recovery mode and install the update automatically.
7. After the rollback, boot into recovery and make a reset
This was the first time, that I was able use the original recovery without problems.
I think I will try to do a rebrand at the weekend.