Related
Current state of phone:
bootloader = relocked tampered
S-ON
Hboot = 2.09.0000
radio = 1.12.11.1210
Phone has no OS/Rom all I have access to is bootloader and recovery TWRP
Unable to flash a rom in TWRP
Had freshly rooted replacement evo LTE (as of yesterday)
-unlocked HTCdev method
-installed superuser and gained root access
today, tried to install a custom sense based rom (located here: http://forum.xda-developers.com/showthread.php?t=1712618 )
Aroma install was unable to set up permissions and install failed and dropped me into a boot loop
tried installing several other sense roms and CM10 with no success before realizing that TWRP was not able to mount several aspects such as Cache and other import parts.
unable to fix
have since:
-relocked bootloader
-attempted to run RUU.exe files with no success
-attempted to gain s-off to use viperRUU and got the error message "FAILED (remote: 43 mail version check fail)"
I am at a loss... could someone please help, if you need me to check anything please just let me know what you need and how to get it.
Since you are S-ON you have to fastboot flash the boot.img/kernel and then the rom
Try MeanBean it is S-ON friendly it has a kernel installer
BTW you will have to unlock again
bigdaddy619 said:
Since you are S-ON you have to fastboot flash the boot.img/kernel and then the rom
Try MeanBean it is S-ON friendly it has a kernel installer
BTW you will have to unlock again
Click to expand...
Click to collapse
where can i find the files you are referring too? Sorry it has been a long several hours, thankyou for your help
Try MeanBean first at least it will get you back up and running
http://forum.xda-developers.com/showthread.php?t=2048229
1. put it on your sdcard
2. boot into twrp
3. click install and find the zip and swipe to install
bigdaddy619 said:
Try MeanBean first at least it will get you back up and running
http://forum.xda-developers.com/showthread.php?t=2048229
1. put it on your sdcard
2. boot into twrp
3. click install and find the zip and swipe to install
Click to expand...
Click to collapse
I cant do that.... i have tried several roms and TWRP is not mounting the things I need to flash... im going to try reflashing the recovery img and let you know here in a moment.... thanks for your help!!! ill be back in just a moment
After reflashing twrp type
fastboot erase cache
Also make sure you unlock your bootloader again
bigdaddy619 said:
After reflashing twrp type
fastboot erase cache
Also make sure you unlock your bootloader again
Click to expand...
Click to collapse
check check and check
unlocked, erased cache, reflashed twrp, and tried to install rom
I get the following in the TWRP logs:
E:Unable to mount /sdcard
E:Unable to mount /cache
E:Unable to mount /data
E:Unable to mount /sd-ext
unable to flash anything through recovery
idk what to do
shootin4aces said:
check check and check
unlocked, erased cache, reflashed twrp, and tried to install rom
I get the following in the TWRP logs:
E:Unable to mount /sdcard
E:Unable to mount /cache
E:Unable to mount /data
E:Unable to mount /sd-ext
unable to flash anything through recovery
idk what to do
Click to expand...
Click to collapse
Have you tried to sideload a rom thru twrp?
You may have to format your sdcards and start fresh (if you take this route backup the important stuff to your PC first)
bigdaddy619 said:
Have you tried to sideload a rom thru twrp?
You may have to format your sdcards and start fresh (if you take this route backup the important stuff to your PC first)
Click to expand...
Click to collapse
Im honestly not sure which route to take, what would you suggest as a sure proof method to resolve the issue, backing up everything now from sd card and then I have no data to lose.
I have never sideloaded really before, what exactly do I need to do
again, thanks so much for your help
bigdaddy619 said:
Have you tried to sideload a rom thru twrp?
You may have to format your sdcards and start fresh (if you take this route backup the important stuff to your PC first)
Click to expand...
Click to collapse
and since i cant mount anything really, how will I be able to sideload? nothing will mount through TWRP
shootin4aces said:
Im honestly not sure which route to take, what would you suggest as a sure proof method to resolve the issue, backing up everything now from sd card and then I have no data to lose.
I have never sideloaded really before, what exactly do I need to do
again, thanks so much for your help
Click to expand...
Click to collapse
If it's not a huge deal I would just format both sdcards and start fresh.
To sideload
Go into twrp
1. Select Advance
2. Select ADB Sideload
3. Check the boxes to wipe chache/dalvik cache and swipe to begin
4. Re-name the rom zip something easy to type haha and put it in your android-sdk/platform-tools folder(or wherever you have your ADB and Fastboot located)
5. Open a cmd window from that folder and type adb sideload filename.zip
Once it's done sideloading it will flash the zip
---------- Post added at 10:55 PM ---------- Previous post was at 10:55 PM ----------
shootin4aces said:
and since i cant mount anything really, how will I be able to sideload? nothing will mount through TWRP
Click to expand...
Click to collapse
Does it mount when you connect to your PC? Both sdcards?
---------- Post added at 11:02 PM ---------- Previous post was at 10:55 PM ----------
Also what version of twrp are you using? I would suggest 2.4.1.0
get it here
http://techerrata.com/browse/twrp2/jewel
in bootloader, choose “FASTBOOT”, hit the Power button, then plug-in your microUSB cable from your phone to computer.
type "fastboot flash recovery openrecovery-twrp-2.x.x.x-jewel.img" without the quotes and press enter (Replace the x's with the version you choose exp. 2.3.3.0)
Copy and paste is the easiest way to do this that way there are no typo's
Now type "fastboot erase cache" without the quotes and press enter
bigdaddy619 said:
If it's not a huge deal I would just format both sdcards and start fresh.
To sideload
Go into twrp
1. Select Advance
2. Select ADB Sideload
3. Check the boxes to wipe chache/dalvik cache and swipe to begin
4. Re-name the rom zip something easy to type haha and put it in your android-sdk/platform-tools folder(or wherever you have your ADB and Fastboot located)
5. Open a cmd window from that folder and type adb sideload filename.zip
Once it's done sideloading it will flash the zip
---------- Post added at 10:55 PM ---------- Previous post was at 10:55 PM ----------
Does it mount when you connect to your PC? Both sdcards?
Click to expand...
Click to collapse
when i mount Via usb it says it needs to format disk I:
when i select to format it opens up a format removable disk window that says capacity 9.93 GB.... should i tell it to reformat? or how should I go about it? I only see 1 item i can reformat
bigdaddy619 said:
If it's not a huge deal I would just format both sdcards and start fresh.
To sideload
Go into twrp
1. Select Advance
2. Select ADB Sideload
3. Check the boxes to wipe chache/dalvik cache and swipe to begin
4. Re-name the rom zip something easy to type haha and put it in your android-sdk/platform-tools folder(or wherever you have your ADB and Fastboot located)
5. Open a cmd window from that folder and type adb sideload filename.zip
Once it's done sideloading it will flash the zip
---------- Post added at 10:55 PM ---------- Previous post was at 10:55 PM ----------
Does it mount when you connect to your PC? Both sdcards?
---------- Post added at 11:02 PM ---------- Previous post was at 10:55 PM ----------
Also what version of twrp are you using? I would suggest 2.4.1.0
get it here
http://techerrata.com/browse/twrp2/jewel
in bootloader, choose “FASTBOOT”, hit the Power button, then plug-in your microUSB cable from your phone to computer.
type "fastboot flash recovery openrecovery-twrp-2.x.x.x-jewel.img" without the quotes and press enter (Replace the x's with the version you choose exp. 2.3.3.0)
Copy and paste is the easiest way to do this that way there are no typo's
Now type "fastboot erase cache" without the quotes and press enter
Click to expand...
Click to collapse
I have TWRP 2.6.0.0
That is you Internal sdcard which is probably where the problem lies
---------- Post added at 11:06 PM ---------- Previous post was at 11:05 PM ----------
shootin4aces said:
I have TWRP 2.6.0.0
Click to expand...
Click to collapse
Try going back to 2.4.1.0 and see what happens before you try formatting
bigdaddy619 said:
That is you Internal sdcard which is probably where the problem lies
---------- Post added at 11:06 PM ---------- Previous post was at 11:05 PM ----------
Try going back to 2.4.1.0 and see what happens before you try formatting
Click to expand...
Click to collapse
still unable to mount after going back to that version...gonna have to reformat... on the computer should I reformat as FAT32? and should I use the default allocation size of 8192 bytes?
shootin4aces said:
still unable to mount after going back to that version...gonna have to reformat... on the computer should I reformat as FAT32? and should I use the default allocation size of 8192 bytes?
Click to expand...
Click to collapse
It's been a while since I formatted my sdcards so I don't really remember so use your best judgement I'm pretty sure I just clicked format and didn't change anything
bigdaddy619 said:
It's been a while since I formatted my sdcards so I don't really remember so use your best judgement I'm pretty sure I just clicked format and didn't change anything
Click to expand...
Click to collapse
here goes nothing
Good luck
bigdaddy619 said:
It's been a while since I formatted my sdcards so I don't really remember so use your best judgement I'm pretty sure I just clicked format and didn't change anything
Click to expand...
Click to collapse
reformatted and sideloaded a rom... started to flash the zip afterwards but then said E:unable to mount /data
that was the only one this time though
shootin4aces said:
reformatted and sideloaded a rom... started to flash the zip afterwards but then said E:unable to mount /data
that was the only one this time though
Click to expand...
Click to collapse
Copy it to your phone from your PC and flash normally in twrp
STOCK ROM 6.0.1 (MMB29K)
Hello guys, here is the untoched flashable zip for our beloved Hammerhead. This will help peeps who use custom recovery to get their new update.
once again i remind you that this is pure flashable factory image
Instruction :
1. Download ROM, and move it in internal storage
2. Boot into TWRP recovery
3. Make Backup
4. Wipe (Dalvik cache, system, data, cache) and Factory reset
5. Flash zip
6. Reboot
I wipe cache dalvik system and try to instal, i got "error executing updater binary in zip N5_6.0.1_(MMB29K)_STOCK-flashable.zip"
your updater script failed to find system.transfer.list system.new.dat system.patch.dat!! Forgot to compress to .dat?
please fix this fast
---------- Post added at 04:52 PM ---------- Previous post was at 04:42 PM ----------
hocuspocus69 said:
your updater script failed to find system.transfer.list system.new.dat system.patch.dat!! Forgot to compress to .dat?
Click to expand...
Click to collapse
how can i fix this
Updater Script fail!!!.
Update please.
Thanks
Dirty flash ota zip pls..
Wrong subfolder to place this thread
Is there any difference between flashing through fastboot nexus image and flashing this via TWRP ?
Did anyone ever get this booting properly?
Sent from my Nexus 5 using Tapatalk
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
Sometimes Huawei releases an update package without approving it. For instance, my device (VIE-L29C636) is getting a B382 update, but the update isn't approved for installation. Here's how to update to those update packages.
NOTE: Using this method, you can also safely upgrade your device even if it is rooted, or has some files system partitions altered. (Of course after finished this process, your device will become unrooted and any alteration to the system partitions mentioned below will revert).
Prerequisites:
Your device is already running EMUI 5 (do not attempt this procedure on EMUI 4 ROM, as the partition layout may differ, and the various firmware (modem, sensor hub, etc.) may not compatible.
Unlocked Bootloader AND FRP.
Latest TWRP from OpenKirin (more on that, including download link, click here).
Huawei Update Extractor, for extracting UPDATE.APP.
imgtool, to convert the sparse android image into an ext4 raw image file.
Method:
Download your preferred update package from Firmware Finder app (Make sure to select the one which has 'FullOTA' designation on it. The package doesn't have to be a 'PV' package). Choose 'update.zip' and the other zip that has your region name on it (for instance, on my C636, look for the zip which has 'spcseas' on it's name). I will refer this 2nd zip as 'regional zip'.
Extract the 'UPDATE.APP' from both zip archive.
Using the Update Extractor on a Windows PC, Extract BOOT, SYSTEM, PRODUCT and VENDOR partitions from UPDATE.APP retrieved from 'update.zip', and extract CUST and VERSION from UPDATE.APP retrieved from your regional zip. You should end up with BOOT.IMG, SYSTEM.IMG, PRODUCT.IMG, VENDOR.IMG, CUST.IMG and VERSION.IMG.
Convert PRODUCT.IMG, VENDOR.IMG and VERSION.IMG to an ext4 image using imgtool, for example:
Code:
imgtool PRODUCT.IMG extract
Beware of overwriting the converted image. imgtool is hardcoded to output the converted file to 'extracted/image.img' folder. ALWAYS rename the image.img to something like 'product.ext4.img' after conversion.
Reboot your device to bootloader mode. Flash BOOT.IMG, SYSTEM.IMG and CUST.IMG via fastboot. For example:
Code:
fastboot flash boot BOOT.IMG
Reboot your device to recovery mode. Type
Code:
fastboot reboot
and hold the Vol Up button on your device to enter recovery mode.
Upload the *.ext4.img converted earlier to your device (doesn't matter where, but I recommend using a safe place like '/sdcard', or USB OTG or external micro SD card). you can use 'adb push', MTP or OTG to upload/copy the ext4.img files to your device.
for each *.ext4.img files, flash it to the appropriate named partitions in
Code:
/dev/block/platform/hi_mci.0/by-name/*
. You can use adb shell on your PC, and a command line program called dd on your device. For faster transfer, try to adjusting the block size to 8M. Example commands (execute from adb shell):
Code:
dd if=/sdcard/product.ext4.img bs=8M of=/dev/block/platform/hi_mci.0/by-name/product
dd if=/sdcard/vendor.ext4.img bs=8M of=/dev/block/platform/hi_mci.0/by-name/vendor
dd if=/sdcard/version.ext4.img bs=8M of=/dev/block/platform/hi_mci.0/by-name/version
Exit TWRP (reboot to system), wait for several minutes for the system to build up it's AOT cache, and enjoy your new EMUI 5 with newer security patch, newer kernel and various features and bug fixes .
EDIT: I apologize that IMGTOOL isn't available in binary form for windows. You can try to use Linux virtual machines to run the IMGTOOL. Any modern GNU/Linux distro should be able to run the IMGTOOL.
Be Alert, by follow this so called "Easy Upgrade", you need to full backup of your data. It is because after upgrade, all data will be reset.
jhleo1 said:
Be Alert, by follow this so called "Easy Upgrade", you need to full backup of your data. It is because after upgrade, all data will be reset.
Click to expand...
Click to collapse
In my case (upgrading from VIE-L29C636B370 to B382), it doesn't erase user data at all. And there is no reason it should erase the data.
But as always, backup your data before performing this procedure, in case something goes wrong.
How to extract product version Vendors use imgtool..
syaif fabian said:
How to extract product version Vendors use imgtool..
Click to expand...
Click to collapse
I'm sorry, I forgot to mention that IMGTOOL is only available as binary in GNU/Linux OS. I think you have to use a VM running a GNU/Linux distro to extract product.img, version.img and/or vendor.img using the IMGTOOL.
@jnakoda
Thank you so much my friend. I was in great trouble as my System Update, File Explorer and Huawei ID apps was deleted from phone due to some experiment. I followed your guide and successfully flashed rom again and boom I got all files back.
Now going to experiment this on B382 firmware
And for those who are curious about this, I successfully used this process for 'meafnaf' region on P9 Plus (VIE-L29)
Once again thanks a lot @jnakoda
---------- Post added at 09:15 PM ---------- Previous post was at 09:10 PM ----------
syaif fabian said:
How to extract product version Vendors use imgtool..
Click to expand...
Click to collapse
imgtool is for converting .img files to ext4 raw image files.
To extract files, you need to use "Huawei Update Extractor" which is mentioned in OP.
---------- Post added at 09:20 PM ---------- Previous post was at 09:15 PM ----------
jhleo1 said:
Be Alert, by follow this so called "Easy Upgrade", you need to full backup of your data. It is because after upgrade, all data will be reset.
Click to expand...
Click to collapse
I confirm in my case (reflashing VIE-L29C185B380), data was not removed. But its better to backup your data first.
faakher said:
@jnakoda
Thank you so much my friend. I was in great trouble as my System Update, File Explorer and Huawei ID apps was deleted from phone due to some experiment. I followed your guide and successfully flashed rom again and boom I got all files back.
Now going to experiment this on B382 firmware
And for those who are curious about this, I successfully used this process for 'meafnaf' region on P9 Plus (VIE-L29)
Once again thanks a lot @jnakoda
---------- Post added at 09:15 PM ---------- Previous post was at 09:10 PM ----------
imgtool is for converting .img files to ext4 raw image files.
To extract files, you need to use "Huawei Update Extractor" which is mentioned in OP.
---------- Post added at 09:20 PM ---------- Previous post was at 09:15 PM ----------
I confirm in my case (reflashing VIE-L29C185B380), data was not removed. But its better to backup your data first.
Click to expand...
Click to collapse
Good Evening i had tried the guide but in my VIE-L09 doesn't work. What can i do? Bootloop infinity
This is easier: https://forum.xda-developers.com/p9/development/eva-nocheck-recovery-flash-unapproved-t3705125
Image works on P9 Plus too. Used it for VIE-L09C432B380.
great post, but as a simple user, i have no idea how to do this steps.
i have a p9 plus c605 b361 and rooted, and i cant update to anything
Every time I want to update to a newer version do I need to repeat the steps?
Or I can directly install new updates from finder without confirmation?
maahmd said:
Every time I want to update to a newer version do I need to repeat the steps?
Or I can directly install new updates from finder without confirmation?
Click to expand...
Click to collapse
heeey...anyone here ?!!?
For Windows users, you can use https://github.com/KinglyWayne/simg2img_win (works great).
maahmd said:
Every time I want to update to a newer version do I need to repeat the steps?
Or I can directly install new updates from finder without confirmation?
Click to expand...
Click to collapse
AYahooo said:
For Windows users, you can use https://github.com/KinglyWayne/simg2img_win (works great).
Click to expand...
Click to collapse
what this is ?!
---------- Post added at 06:51 PM ---------- Previous post was at 06:45 PM ----------
Steve2016 said:
This is easier: https://forum.xda-developers.com/p9/development/eva-nocheck-recovery-flash-unapproved-t3705125
Image works on P9 Plus too. Used it for VIE-L09C432B380.
Click to expand...
Click to collapse
What version? EVA L09: eva_l09b391_nocheckrecovery.img, or EVA L19: eva_l19b391_nocheckrecovery.img ??
maahmd said:
What version? EVA L09: eva_l09b391_nocheckrecovery.img, or EVA L19: eva_l19b391_nocheckrecovery.img ??
Click to expand...
Click to collapse
If this Recovery by Atarii really work on VIE too - it's logical that you use for VIE-L09 the L09 version of this recovery
Steve2016 said:
This is easier: https://forum.xda-developers.com/p9/development/eva-nocheck-recovery-flash-unapproved-t3705125
Image works on P9 Plus too. Used it for VIE-L09C432B380.
Click to expand...
Click to collapse
Tecalote said:
If this Recovery by Atarii really work on VIE too - it's logical that you use for VIE-L09 the L09 version of this recovery
Click to expand...
Click to collapse
I know this but I have a version vie-l29c185 So I do not know which version I chose
maahmd said:
I know this but I have a version vie-l29c185 So I do not know which version I chose
Click to expand...
Click to collapse
If you would say earlier which version you have and if you would search a little bit, then you can find L29:
https://forum.xda-developers.com/showpost.php?p=75234976&postcount=62
Tecalote said:
If you would say earlier which version you have and if you would search a little bit, then you can find L29:
https://forum.xda-developers.com/showpost.php?p=75234976&postcount=62
Click to expand...
Click to collapse
i well try this or this now https://forum.xda-developers.com/p9-plus/how-to/easy-upgrade-to-unapproved-emui-5-update-t3649532
maahmd said:
i well try this or this now https://forum.xda-developers.com/p9-plus/how-to/easy-upgrade-to-unapproved-emui-5-update-t3649532
Click to expand...
Click to collapse
Try it with the Link I give you.
There's no risk. If it works is good, if not, nothing will be changed. (only Recovery, which can be changed after)
Tecalote said:
Try it with the Link I give you.
There's no risk. If it works is good, if not, nothing will be changed. (only Recovery, which can be changed after)
Click to expand...
Click to collapse
Ok i will do it now if it does not work ..do you have a download link RECOVRY bised for p9 plus ?
Or I will pull it out of the update file
I'll tell you the result
maahmd said:
Ok i will do it now if it does not work ..do you have a download link RECOVRY bised for p9 plus ?
Or I will pull it out of the update file
I'll tell you the result
Click to expand...
Click to collapse
I don't know what you mean now
Download the Nocheck Recovery for L29 from the Link I give you
https://forum.xda-developers.com/showpost.php?p=75234976&postcount=62
and do the instructions from the OP
https://forum.xda-developers.com/p9/development/eva-nocheck-recovery-flash-unapproved-t3705125
But with the RIGHT Firmware for your VIE-L29 device (3 zips from Firmware Finder /FullOTA)
After updating Firmware Bootloader is closed and Root is gone.
You have to open again (Factoryreset low-level wipe - if it doesn't do 100% do it manually from settings /advanced settings /backup restore /Factoryreset with wipe of internal storage - this is important! ) and flash TWRP and Root again
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.