Database Info

Best Method to Re-flash & Re-root Plus Have Internal Storage Working

Hey Guys -
I have had my A9 for about 2 months and love it. When I first purchased it, I rooted it using the method pinned to this forum which seemed to work well. Soon afterwards, I found out that when I inserted and tried to format an SD card as "internal", it wouldn't work and result in it showing as "corrupted." I soon found out that this seemed to be due to the root replacing the original boot.img which messes with encryption. Since the root was posted, SuperSU has been updated and that step has changed supposedly.
Now that I have some time, I want to fix this issue. Before doing so, I've read through many posts and think I have a plan. I wanted to post the steps I need to follow as I understood them to make sure my plan is correct and will result in not only being able to format an SD internally and be rooted, but also a working phone Below are the specs of my phone, the steps I think it may take to resolve, and a few questions I have after reading through numerous posts. Any help is appreciated!
Phone Specs
Some as currently listed in Settings
- HTC One A9
- AT&T USA
- Rooted / s-off
- Android 6.0 / Sense 7.0g
Software Number: 1.10.502.3
Kernel: 3.10.73-perf-g28d66e0
Baseband: [email protected]_29.05_F
Build: 1.10.502.3 CL635081 release keys
Android Security Patch Level: 2015-10-01
Steps to Fix
1. Backup any data desired (I have a nightly Titanium backup)
2. Download RUU for same version (1.10.502.3) from http://forum.xda-developers.com/one-a9/general/wip-ruu-htc-one-a9-t3240344
Should I use newer version or are those for different carriers?
3. Apply RUU (via embedded EXE or try to extract and apply using adb/fastboot)
4. Once phone is restored, make a backup of boot.img from phone just in case it's needed later
5. Install TWRP via adb/fastboot
6. Install SuperSU via TWRP
At this point (if I can make it to this point), test and see if the phone's rooted and I can format the SD internally. If so, great. If not, continue with the following steps...
7. Download & flash modded boot.img from A9 Root post
8. Install TWRP via adb / fastboot
9. Install SuperSU via TWRP
10. Flash original boot.img backed up in step #4 to my phone (since modded one was only needed initially to install SuperSU) So that encryption keys match and I may successfully format sd cards for internal use
My Questions
1. Are the steps above basically the process i need to perform or is there a better / easier way? I don't know if I could flash a common boot.img from an RUU or if it needs to be flashed to phone first for encryption purposes. Even if I can, I've tried to extract it from ruu.zip before and could not
2. Should I use an RUU for a newer version (over 1.10.502.3) or are those for different carriers and not work with my AT&T phone?
3. Does it make a difference if I install the RUU via embedded EXE or extract and apply using adb/fastboot?
4. What versions of TWRP & SuperSU should I use?
Any additional suggestions would be appreciated - I just want to get this resolved once and for all! - Thanks!

bzowk said:
Hey Guys -
I have had my A9 for about 2 months and love it. When I first purchased it, I rooted it using the method pinned to this forum which seemed to work well. Soon afterwards, I found out that when I inserted and tried to format an SD card as "internal", it wouldn't work and result in it showing as "corrupted." I soon found out that this seemed to be due to the root replacing the original boot.img which messes with encryption. Since the root was posted, SuperSU has been updated and that step has changed supposedly.
Now that I have some time, I want to fix this issue. Before doing so, I've read through many posts and think I have a plan. I wanted to post the steps I need to follow as I understood them to make sure my plan is correct and will result in not only being able to format an SD internally and be rooted, but also a working phone Below are the specs of my phone, the steps I think it may take to resolve, and a few questions I have after reading through numerous posts. Any help is appreciated!
Phone Specs
Some as currently listed in Settings
- HTC One A9
- AT&T USA
- Rooted / s-off
- Android 6.0 / Sense 7.0g
Software Number: 1.10.502.3
Kernel: 3.10.73-perf-g28d66e0
Baseband: [email protected]_29.05_F
Build: 1.10.502.3 CL635081 release keys
Android Security Patch Level: 2015-10-01
Steps to Fix
1. Backup any data desired (I have a nightly Titanium backup)
2. Download RUU for same version (1.10.502.3) from http://forum.xda-developers.com/one-a9/general/wip-ruu-htc-one-a9-t3240344
Should I use newer version or are those for different carriers?
3. Apply RUU (via embedded EXE or try to extract and apply using adb/fastboot)
4. Once phone is restored, make a backup of boot.img from phone just in case it's needed later
5. Install TWRP via adb/fastboot
6. Install SuperSU via TWRP
At this point (if I can make it to this point), test and see if the phone's rooted and I can format the SD internally. If so, great. If not, continue with the following steps...
7. Download & flash modded boot.img from A9 Root post
8. Install TWRP via adb / fastboot
9. Install SuperSU via TWRP
10. Flash original boot.img backed up in step #4 to my phone (since modded one was only needed initially to install SuperSU) So that encryption keys match and I may successfully format sd cards for internal use
My Questions
1. Are the steps above basically the process i need to perform or is there a better / easier way? I don't know if I could flash a common boot.img from an RUU or if it needs to be flashed to phone first for encryption purposes. Even if I can, I've tried to extract it from ruu.zip before and could not
2. Should I use an RUU for a newer version (over 1.10.502.3) or are those for different carriers and not work with my AT&T phone?
3. Does it make a difference if I install the RUU via embedded EXE or extract and apply using adb/fastboot?
4. What versions of TWRP & SuperSU should I use?
Any additional suggestions would be appreciated - I just want to get this resolved once and for all! - Thanks!
Click to expand...
Click to collapse
First off, this isn't Development.
Secondly, I explained to you how to fix this in the very root thread you linked several times.
Thirdly, there's a newer, official RUU from HTC right on their ROM Downloads website. I'd start by installing that (though I also have a recovery-flashable version of that ROM in my Base ROM thread).
Fourthly, with access to an official RUU, and my ROM decrypt script, you have access to the stock boot.img (which is also in the firmware zip in my Base ROM thread), which you can use as your baseline for restoring the verity key to the ramdisk, thereby allowing you to use adopted storage without any issues. Note however that I was only able to use adopted storage with the "forceencrypt" flag enabled.
Fifthly, you can't just restore the stock boot image (at least not if you want to stay rooted). You can be both rooted and encrypted, but you have to first make sure SuperSU is flashed and set up prior to allowing the device to be encrypted again (adopted storage only works with an encrypted device, and then you won't be able to access your storage with TWRP).

OK, OK - sorry.... It had been a while since posting and honestly forgot about that thread - my fault.
I decided to start fresh so have already restored the phone to HTC's latest RUU (1.27.502.5 ATT) as I already had it downloaded. I've also flashed TWRP 2.8.8.1 to the phone, but am obviously prompted to enter a password when I try to enter recovery. Based off what I've read, the steps below seem to be what I need to do so that I may be rooted + still have encryption for internal sd formatting. Is it correct (or close to it)
Using an Ubuntu 14.04 x86 VM...
1. Download & extract your decrypt script to a temp folder in linux vm
2. In Windows, run same RUU I applied and copy out rom.zip from %temp%
3. Rename "rom.zip" to "rom_a9.zip"
4. Copy rom_a9.zip to the ""place_rom_zip_here" folder of your extracted script in the vm
5. Run ./decrypt-htc and wait for script to complete to get img files
On Phone (Currently has same RUU installed + TWRP but not rooted)
6. Root phone using original method of flashing modded boot.img, install SuperSU, and get rooted
7. Once done and rooted, flash boot.img I extracted using your script above to phone via adb
Once that's done, it should be rooted + have encryption thus allowing me to use internal sd card, right? Sorry to be such a bother - just want to get this fixed and done with
Thanks!

bzowk said:
OK, OK - sorry.... It had been a while since posting and honestly forgot about that thread - my fault.
I decided to start fresh so have already restored the phone to HTC's latest RUU (1.27.502.5 ATT) as I already had it downloaded. I've also flashed TWRP 2.8.8.1 to the phone, but am obviously prompted to enter a password when I try to enter recovery. Based off what I've read, the steps below seem to be what I need to do so that I may be rooted + still have encryption for internal sd formatting. Is it correct (or close to it)
Using an Ubuntu 14.04 x86 VM...
1. Download & extract your decrypt script to a temp folder in linux vm
2. In Windows, run same RUU I applied and copy out rom.zip from %temp%
3. Rename "rom.zip" to "rom_a9.zip"
4. Copy rom_a9.zip to the ""place_rom_zip_here" folder of your extracted script in the vm
5. Run ./decrypt-htc and wait for script to complete to get img files
On Phone (Currently has same RUU installed + TWRP but not rooted)
6. Root phone using original method of flashing modded boot.img, install SuperSU, and get rooted
7. Once done and rooted, flash boot.img I extracted using your script above to phone via adb
Once that's done, it should be rooted + have encryption thus allowing me to use internal sd card, right? Sorry to be such a bother - just want to get this fixed and done with
Thanks!
Click to expand...
Click to collapse
Re-read my post. If you flash the stock boot.img, you will no longer be rooted.
And as I said in the original thread, you need to pull the rooted boot.img and add the verity key from the stock one to it. Also you'll need to add the forceencrypt and verify flag back.
P.S. You also need to re-read the instructions in the decrypt thread. You don't have to rename anything anymore.

Good Afternoon -
OK - sorry to frustrate you, but I think I finally have it figured out. I started from scratch, re-read many posts, and took notes. I was a little confused on the last part so wanted to verify, please...
I've already unpacked the boot.img from the latest HTC A9 (AT&T) RUU and have the two folders. I restored the same RUU to my phone, flashed TWRP 2.8.8.1, backed up the boot.img, and unpacked it before realizing that I should have probably rooted it first.
Correct me if I'm wrong, but here's all I need to do to finish....
1. Download modified A9 boot.img from top of root thread
2. Flash modded boot.img using fastboot
3. Verify TWRP is still installed then use it to install SuperSU 2.67 (latest)
4. Back up boot partition just like I did before in TWRP
5. Unpack it on PC to create ramdisk and split_img folders
6. Copy verity_key from unpack of the actual RUU and overwrite one in rooted unpack
7. Edit the file fstab.qcom in the ramdisk folder of the rooted unpack in Notepad++ and add the "verify" flag after the wait flag on the fist uncommented line - save
8. Repack rooted boot.img
9. Flash phone with repacked boot.img using fastboot
10. Reboot & enjoy a rooted phone + encryption allowing sd internal formatting
Promise not to bug anymore if I can just get this resolved.
Thanks again for your assistance!
UPDATE
Hmm - was just prepping and went to download modded file from root thread's first post. Doesn't seem to have one that matches newest build of RUU I flashed - if I'm interpreting it correctly. Researching further, but if know of alternate method or another solution to get through steps 1 & 2 about (assuming they are correct), I'd appreciate it. Thanks

bzowk said:
Good Afternoon -
OK - sorry to frustrate you, but I think I finally have it figured out. I started from scratch, re-read many posts, and took notes. I was a little confused on the last part so wanted to verify, please...
I've already unpacked the boot.img from the latest HTC A9 (AT&T) RUU and have the two folders. I restored the same RUU to my phone, flashed TWRP 2.8.8.1, backed up the boot.img, and unpacked it before realizing that I should have probably rooted it first.
Correct me if I'm wrong, but here's all I need to do to finish....
1. Download modified A9 boot.img from top of root thread
2. Flash modded boot.img using fastboot
3. Verify TWRP is still installed then use it to install SuperSU 2.67 (latest)
4. Back up boot partition just like I did before in TWRP
5. Unpack it on PC to create ramdisk and split_img folders
6. Copy verity_key from unpack of the actual RUU and overwrite one in rooted unpack
7. Edit the file fstab.qcom in the ramdisk folder of the rooted unpack in Notepad++ and add the "verify" flag after the wait flag on the fist uncommented line - save
8. Repack rooted boot.img
9. Flash phone with repacked boot.img using fastboot
10. Reboot & enjoy a rooted phone + encryption allowing sd internal formatting
Promise not to bug anymore if I can just get this resolved.
Thanks again for your assistance!
UPDATE
Hmm - was just prepping and went to download modded file from root thread's first post. Doesn't seem to have one that matches newest build of RUU I flashed - if I'm interpreting it correctly. Researching further, but if know of alternate method or another solution to get through steps 1 & 2 about (assuming they are correct), I'd appreciate it. Thanks
Click to expand...
Click to collapse
You don't need anything from that root thread. Everything there is deprecated (which I've said several times).
If you already have the stock boot.img unpacked and ready to go, all you have to do is flash SuperSU, then back up the rooted boot.img that you now have on your device thanks to SuperSU. Unpack that boot.emmc.win and add the verity_key from the stock ramdisk and replace the fstab.qcom with the one from the stock ramdisk. Repack, flash to your device via fastboot or TWRP, and your device will encrypt on that first boot and you'll be good to go.
Just to make sure - you did a Format Data in TWRP prior to flashing SuperSU, correct?

Captain_Throwback said:
You don't need anything from that root thread. Everything there is deprecated (which I've said several times).
If you already have the stock boot.img unpacked and ready to go, all you have to do is flash SuperSU, then back up the rooted boot.img that you now have on your device thanks to SuperSU. Unpack that boot.emmc.win and add the verity_key from the stock ramdisk and replace the fstab.qcom with the one from the stock ramdisk. Repack, flash to your device via fastboot or TWRP, and your device will encrypt on that first boot and you'll be good to go.
Just to make sure - you did a Format Data in TWRP prior to flashing SuperSU, correct?
Click to expand...
Click to collapse
Thanks -
Well, that's the thing... One of the two unpacked boot.img I have currently is wrong. The two I have are:
- One unpacked boot.img extracted from latest RUU using your script in linux
- One unpacked boot.img backed up from unrooted phone which only had TWRP flashed
That was part of my question. I know that the 2nd unpacked boot.img above is worthless as the phone needed to be rooted prior to me backing it up. The question for me is how to flash superSU onto the phone (which currently has the same latest RUU + TWRP 2.8.8.1 installed) if I can only access TWRP is a read-only mode as I'm prompted for password upon booting to recovery. That's why I brought up the legacy root method as I don't know of an alternative... unless SuperSU doesn't require write permissions to whatever TWRP has locked down currently.
Once I can root it, backup it's boot, and unpack it; I just need to literally copy & overwrite the "verity_key" and "fstab.qcom" files (assuming the only difference is the fstab.qcom I'm overwriting doesn't have the verify flag), repack, then flash back to phone via fastboot, right?
Thanks for your patience!

bzowk said:
Thanks -
Well, that's the thing... One of the two unpacked boot.img I have currently is wrong. The two I have are:
- One unpacked boot.img extracted from latest RUU using your script in linux
- One unpacked boot.img backed up from unrooted phone which only had TWRP flashed
That was part of my question. I know that the 2nd unpacked boot.img above is worthless as the phone needed to be rooted prior to me backing it up. The question for me is how to flash superSU onto the phone (which currently has the same latest RUU + TWRP 2.8.8.1 installed) if I can only access TWRP is a read-only mode as I'm prompted for password upon booting to recovery. That's why I brought up the legacy root method as I don't know of an alternative... unless SuperSU doesn't require write permissions to whatever TWRP has locked down currently.
Once I can root it, backup it's boot, and unpack it; I just need to literally copy & overwrite the "verity_key" and "fstab.qcom" files (assuming the only difference is the fstab.qcom I'm overwriting doesn't have the verify flag), repack, then flash back to phone via fastboot, right?
Thanks for your patience!
Click to expand...
Click to collapse
Once you Format Data in TWRP and reboot recovery, you can flash SuperSU and you will be rooted. You just have to back up the boot.img after flashing SuperSU on the unencrypted device to re-enable verity so that adopted storage will work.
P.S. And no, the verify flag isn't the only difference. As I also said earlier (I'm constantly repeating myself), the device must be encrypted for Adopted Storage to work, so the forceencrypt flag from the stock fstab must also be present. That's why it's easier just to replace the whole file. The problem you have at the end of the day is that, while you'll be rooted and be able to use adopted storage in Android, you still won't be able to access said storage (or /data) in TWRP.

Captain_Throwback said:
Once you Format Data in TWRP and reboot recovery, you can flash SuperSU and you will be rooted. You just have to back up the boot.img after flashing SuperSU on the unencrypted device to re-enable verity so that adopted storage will work.
P.S. And no, the verify flag isn't the only difference. As I also said earlier (I'm constantly repeating myself), the device must be encrypted for Adopted Storage to work, so the forceencrypt flag from the stock fstab must also be present. That's why it's easier just to replace the whole file. The problem you have at the end of the day is that, while you'll be rooted and be able to use adopted storage in Android, you still won't be able to access said storage (or /data) in TWRP.
Click to expand...
Click to collapse
Great - Thanks!!
Just to make sure, below's my plan with a small question @ step #5. Does it get your stamp of approval?
Phone (A9) already had latest RUU restored (same RUU I ran against your script to pull boot.img from) and TWRP 2.8.8.1 flashed
1. Boot into TWRP & bypass initial screen prompting for password
2. Format Data
3. Reboot back into TWRP
4. Flash SuperSU 2.76 zip
5. Reboot to system then back to TWRP and backup boot partition? / Stay in TWRP and backup boot partition? / Reboot back into TWRP and backup boot partition?
6. Unpack backed up boot partition from phone
7. Copy "verity_key" & "fstab.qcom" files from ramdisk folder in unpacked RUU boot and paste into & overwrite same files in ramdisk folder of unpacked boot from rooted phone
8. Repack rooted phone boot (which includes both new files)
9. Flash newly packed boot.img to phone using fastboot
10. Enjoy
I really appreciate your help and patience with me!

bzowk said:
Great - Thanks!!
Just to make sure, below's my plan with a small question @ step #5. Does it get your stamp of approval?
Phone (A9) already had latest RUU restored (same RUU I ran against your script to pull boot.img from) and TWRP 2.8.8.1 flashed
1. Boot into TWRP & bypass initial screen prompting for password
2. Format Data
3. Reboot back into TWRP
Click to expand...
Click to collapse
Good so far . . .
bzowk said:
4. Flash SuperSU 2.76 zip
Click to expand...
Click to collapse
I'm sure this is just a typo, but that should be 2.67, not 76 (there is no 2.76).
bzowk said:
5. Reboot to system then back to TWRP and backup boot partition? / Stay in TWRP and backup boot partition? / Reboot back into TWRP and backup boot partition?
Click to expand...
Click to collapse
Bolded the correct one above (no need to leave TWRP as the necessary modifications have already been made).
bzowk said:
6. Unpack backed up boot partition from phone
7. Copy "verity_key" & "fstab.qcom" files from ramdisk folder in unpacked RUU boot and paste into & overwrite same files in ramdisk folder of unpacked boot from rooted phone
8. Repack rooted phone boot (which includes both new files)
Click to expand...
Click to collapse
Looks good . . .
bzowk said:
9. Flash newly packed boot.img to phone using fastboot
Click to expand...
Click to collapse
TWRP can also flash the new image, but fastboot is probably the most reliable way to do it.
bzowk said:
10. Enjoy
Click to expand...
Click to collapse
Hopefully . . . You'll likely get a reboot on the first boot (possible multiple reboots), as SuperSU needs a reboot to install the necessary files. Since your device will also encrypt on that initial boot, I'm not sure whether there will be a conflict or not.
bzowk said:
I really appreciate your help and patience with me!
Click to expand...
Click to collapse
Guess we'll see if it all works out . . .

Thanks!
I proceeded by formatting data, booting directly back intoTWRP, flashing SuperSU, backing up the boot partition, then mounting and copying it over to my PC. The boot.img size was 65,536kb - the same size as the one I unpacked from the RUU. Once unpacked, it was missing the verity_key file and the fstab.qcom file was different + missing the verify flag.
I replaced those two files, then ran repackimg.bat which created image-new.img which I renamed to boot.img. Interesting, though, that this file was only 45,890kb. If it's a repack, shouldn't it be the same or similar? Anyways, the phone was still in TWRP (hadn't booted to system since before the format data) so booted it into bootloader directly and tried flashing boot using my new 45mb boot.img.
If failed - but - my phone was only at 17% power. Don't know if that's why it failed or not so it's charging right now while still in the bootloader. Below is what was echoed when I tried flashing it:
Code:
c:\adb>fastboot flash boot boot.img
target reported max download size of 800000000 bytes
sending 'boot' (45890 KB)...
OKAY [ 3.488s]
writing 'boot'...
(bootloader) HOSD CL#656287
FAILED (remote: 4 RU_BATTERY_LOW please connect charger (17% < 30%))
finished. total time: 4.506s
The reason I didn't boot to system is that I thought that was when the encryption might take place. Going to wait until above 30% power then try flashing again. Powered down to charge, but plan to boot straight back into bootloader to flash. If you see anything that stands out or that I need to do otherwise, please let me know. Otherwise, I'll report back what the result was after getting above 30%.
Thanks again!

bzowk said:
Thanks!
I proceeded by formatting data, booting directly back intoTWRP, flashing SuperSU, backing up the boot partition, then mounting and copying it over to my PC. The boot.img size was 65,536kb - the same size as the one I unpacked from the RUU. Once unpacked, it was missing the verity_key file and the fstab.qcom file was different + missing the verify flag.
I replaced those two files, then ran repackimg.bat which created image-new.img which I renamed to boot.img. Interesting, though, that this file was only 45,890kb. If it's a repack, shouldn't it be the same or similar? Anyways, the phone was still in TWRP (hadn't booted to system since before the format data) so booted it into bootloader directly and tried flashing boot using my new 45mb boot.img.
If failed - but - my phone was only at 17% power. Don't know if that's why it failed or not so it's charging right now while still in the bootloader. Below is what was echoed when I tried flashing it:
Code:
c:\adb>fastboot flash boot boot.img
target reported max download size of 800000000 bytes
sending 'boot' (45890 KB)...
OKAY [ 3.488s]
writing 'boot'...
(bootloader) HOSD CL#656287
FAILED (remote: 4 RU_BATTERY_LOW please connect charger (17% < 30%))
finished. total time: 4.506s
The reason I didn't boot to system is that I thought that was when the encryption might take place. Going to wait until above 30% power then try flashing again. Powered down to charge, but plan to boot straight back into bootloader to flash. If you see anything that stands out or that I need to do otherwise, please let me know. Otherwise, I'll report back what the result was after getting above 30%.
Thanks again!
Click to expand...
Click to collapse
The repack is smaller because the backup uses "dd" to copy the entire block device. Not all that space is actually used after compression. That's nothing to worry about.
And these devices are very picky about flashing only when there's sufficient battery, so I'm sure that's the only reason it failed. TWRP, however, doesn't care how much battery you have, so you could always flash the new boot.img in recovery.

Captain_Throwback said:
The repack is smaller because the backup uses "dd" to copy the entire block device. Not all that space is actually used after compression. That's nothing to worry about.
And these devices are very picky about flashing only when there's sufficient battery, so I'm sure that's the only reason it failed. TWRP, however, doesn't care how much battery you have, so you could always flash the new boot.img in recovery.
Click to expand...
Click to collapse
Hey, hey, hey - think it worked!!
Once I got above 30%, I flashed without issue. I rebooted and was able to format an sd internally successfully, too. Now, I just need to verify it's rooted, but think it is. Thank you so much for your help! I'm going to write a guide for newbs like me to use in the future soon.
Thanks again!

bzowk said:
Hey, hey, hey - think it worked!!
Once I got above 30%, I flashed without issue. I rebooted and was able to format an sd internally successfully, too. Now, I just need to verify it's rooted, but think it is. Thank you so much for your help! I'm going to write a guide for newbs like me to use in the future soon.
Thanks again!
Click to expand...
Click to collapse
If your adopted storage doesn't show as corrupted, and you're able to open the SuperSU app in your app drawer and not get a message that no su binary is installed, you should be good to go .

bad topic

[Recovery] TWRP 3.0.2-0 for phicomm energy 2 e670 msm8909

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
CHANGELOGS :
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
CHANGELOG for 2.8.7.0:
-Initial ground work for software drawn keyboard (_that)
-Fix handling of wiping internal storage on datamedia devices (xuefer)
-Allow DataManager to set and read values from the system properties (xuefer)
-Fix crash when taking screenshots on arm64 devices (xuefer)
-Fix error message after an ORS script completes (Dees_Troy)
-Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
-Add system read only option – more details below (Dees_Troy)
-Add resize2fs and GUI option to run resize2fs (Dees_Troy)
-Fix crash loop caused by empty lines in AOSP recovery command file (_that)
-Prevent duplicate page overlays such as multiple lock screens (mdmower)
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
TWRP 3.0.2.0
E670 Recovery
How to install ? :
1. Extract The Zip File
2. Open Extracted folder and hold shift and right click and select "Open command window here"
3. Then connect your device to the System and make sure you have USB debugging enabled.
4. Type "adb devices" to check if the device is connected.
5. You will get a prompt in your device asking permission to allow USB debugging just click OK and allow.
6. Type "adb devices" again to see if ur device is connected or not and if its connected it will show something like this:
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
0123456789ABCDEF device
6. Make sure recovery.img is in the same adb and fastboot folder
7. Type "adb reboot bootloader" to boot into fastboot mode.
8. Use this command to flash the recovery:
Code:
fastboot flash recovery recovery.img
You will get something like this:
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 268435456 bytes
sending 'recovery' (12060 KB)...
OKAY [ 0.391s]
writing 'recovery'...
OKAY [ 0.250s]
finished. total time: 0.656s
9. Boot into the system by using this command:
"fastboot reboot"
10. To boot into TWRP using adb use this command:
"adb reboot recovery"
11. If you wanna use hardware button combination :
a. Power Off your device
b. Press and hold volume UP + Power button till you see the PHICOMM Bootlogo and leave power button while keep holding the volume UP button till you boot into TWRP.
12. Download SuperSU.zip and flash it on TWRP to root your device
Sources
- android_device_phicomm_e670-android-5.1
Bugs ?
- No Bug

Bro you have twrp for phicomm energy 653

nawazmomin said:
Bro you have twrp for phicomm energy 653
Click to expand...
Click to collapse
No

Bro help us
Plss build twrp for Phicomm Energy 653 (Energy ).
We hardly need this ...plss help us ..

Help to built recovery
Hello sid,
I am trying to port custom recovery for phicomm e653, stuck on very 1st step.
I need stock recovery for that, but unable to find it in system, guide me please.
Sent from my PHICOMM E653 using XDA Free mobile app

All files of Phicomm energy 653
navid.ans1988 said:
Hello sid,
I am trying to port custom recovery for phicomm e653, stuck on very 1st step.
I need stock recovery for that, but unable to find it in system, guide me please.
Sent from my PHICOMM E653 using XDA Free mobile app
Click to expand...
Click to collapse
here is all necessary files for porting Phicomm e653 recovery, files include boot.img recovery.img partitions info etc.
link 4shared.com/zip/1G7DwXnTba/Phicomm_Energy_E653_Files.html

Thankyou brother, I will have a look and report to you.
Sent from my PHICOMM E653 using XDA Free mobile app

sameerchapai said:
here is all necessary files for porting Phicomm e653 recovery, files include boot.img recovery.img partitions info etc.
link 4shared.com/zip/1G7DwXnTba/Phicomm_Energy_E653_Files.html
Click to expand...
Click to collapse
With your help ported custom recovery for e653, unfortunately unable to boot into fastboot. If i try from recovery there is an option "reboot to bootloader" after i select that device reboots and stuck to phicomm logo. secondly when i directly give commands from adb as " adb reboot bootloader" same thing happens, device stucks on phicomm logo. can you guide me how to see partitions. i want to learn this things.

Plss check 4shared link ..partitions files is there on zip ..jst extract zip.
Thnx
---------- Post added at 08:30 PM ---------- Previous post was at 08:26 PM ----------
navid.ans1988 said:
With your help ported custom recovery for e653, unfortunately unable to boot into fastboot. If i try from recovery there is an option "reboot to bootloader" after i select that device reboots and stuck to phicomm logo. secondly when i directly give commands from adb as " adb reboot bootloader" same thing happens, device stucks on phicomm logo. can you guide me how to see partitions. i want to learn this things.
Click to expand...
Click to collapse
If u have ported then plss provide me

I just tried , pulled out recovery.img from system, it was of 30mb. Have you figured out why I am not able to boot into bootloader or fastboot. Do you operate same handset ? .
Sent from my PHICOMM E653 using XDA Free mobile app

navid.ans1988 said:
I just tried , pulled out recovery.img from system, it was of 30mb. Have you figured out why I am not able to boot into bootloader or fastboot. Do you operate same handset ? .
Sent from my PHICOMM E653 using XDA Free mobile app
Click to expand...
Click to collapse
Yea i having same handset but unfortunately while updating xposed installer software got bricked and completely dead for many days. After searching lot finally found fastboot rom but it was Deutsche version ..flashed with qpst tools all working fine but network not working.
bro plss be careful ok ..dnt repeat anything wrong like me coz no official roms available and vry bad software support from phicomm service

sameerchapai said:
Yea i having same handset but unfortunately while updating xposed installer software got bricked and completely dead for many days. After searching lot finally found fastboot rom but it was Deutsche version ..flashed with qpst tools all working fine but network not working.
bro plss be careful ok ..dnt repeat anything wrong like me coz no official roms available and vry bad software support from phicomm service
Click to expand...
Click to collapse
Thankyou for advice , that means there are fastboot problems in this device.
Sent from my PHICOMM E653 using Tapatalk

navid.ans1988 said:
Thankyou for advice , that means there are fastboot problems in this device.
Sent from my PHICOMM E653 using Tapatalk
Click to expand...
Click to collapse
Plss can u send me ur stock boot and recovery files?

Do you want full stock rom, I have uploaded to drive, provide your email id
Sent from my PHICOMM E653 using Tapatalk

navid.ans1988 said:
Do you want full stock rom, I have uploaded to drive, provide your email id
Sent from my PHICOMM E653 using Tapatalk
Click to expand...
Click to collapse
My email [email protected] wr u got full stock rom?

I had some issues , so phicomm India page on Facebook shared it with me, I will add you to download it and will share a link to you.
Sent from my PHICOMM E653 using Tapatalk

Ohh i already tried with that rom update file ..not updating with my recovery yar ..plss provide me boot and recovery files from ur phone plss
---------- Post added at 09:31 PM ---------- Previous post was at 09:27 PM ----------
Is this same update file which is available on phicomm.in service center ?

Yes, I downloaded it from there, flash it via adb , I did it too it worked for me
Sent from my PHICOMM E653 using Tapatalk

Ok guide me how did u flashed?

sameerchapai said:
Ok guide me how did u flashed?
Click to expand...
Click to collapse
Download fastboot folder I just shared to you, put ROM package in fastboot folder, run adb.bat and fastboot.bat once. Then hold shift + right click anywhere in that folder(shift + right click on empty space), then click open command window here. After that cmd will open. Type adb devices, it will show device attached. Now put your device in recovery mode. Go to install via adb sideload. Then type adb sideload TF Update.zip in cmd window opened earlier .
Flashing will start, after you get succeeded, reboot device.
Sent from my PHICOMM E653 using Tapatalk

[ROOT]Root Guide for Huawei MediaPad M5

DISCLAIMER: I'm not responsible for anything that happens to your device. Use the steps below at your own risk . Be mindful of the facts unlocking bootloader voids your warranty and also hard resets your device - ALL YOUR DATA, SETTINGS, FILES AND APPS WILL BE DELETED. Rooting your device voids warranty as well. I own the Chinese SHT-AL09 8.4" LTE device and tested this root procedure ONLY WITH THIS MODEL. However, I believe there is a good chance the steps below will work for all other models of MediaPad M5, including WiFi only variants and 10" models. You MUST unlock your bootloader first. Do NOT use ramdisk image I provide in the steps below for any other model besides SHT-AL09 - doing so is guaranteed to render your device unusable. Ramdisk I provided is ONLY for SHT-AL09. You will need to extract your own ramdisk from stock firmware, specific to your device model
Credits:
@Wirmpolter - this root method largely based on his Magisk guide for Mate 9
@topjohnwu for creating the awesome Magisk Manager, which was used to patch ramdisk image with superuser binary
People, who created HuaweiUpdateExtractor
@magnumlove who pointed me in the right for developing root method in this post
This site, for hosting stock firmware for Huawei MediaPad M5
1. First, you will need to unlock the bootloader of your M5. Follow this guide
2. Transfer this patched ramdisk image to your device
Note for users with version of M5 other than SHT-AL09: Do NOT use the above ramdisk image. Download the full stock rom (update.zip) from the site I linked in the credits. Extract UPDATE.APP file from the zip. Then use HuaweiUpdateExtractor to extract ramdisk.img specific to your device. If you get errors in HuaweiUpdateExtractor - uncheck first 2 checkboxes for checksum verification on Settings tab and try again
3. Once bootloader is unlocked, install latest Magisk Manager from the official Magisk thread
4. Once Magisk Manager gives you a pop-up prompt to either download Magisk zip or patch the boot image file - chose to patch the boot image, but instead of boot.img select ramdisk.img from step 2. Magisk Manager should give you a message the image was successfully patched. It will be saved as patched_boot.img in MagiskManager folder on your sdcard. If it does not say success - do NOT proceed
5. Transfer the newly created patched_boot.img back to your PC
6. If you already have ADB and Fastboot tools installed on your PC you can just use what you've got. If not - get them from here
7. Connect your M5 to PC via USB cable
8. Run command prompt. If your ADB and Fastboot are installed as system app - you can do this from any path in CMD. If not - you need to switch in CMD to your ADB and Fastboot folder. Either way, the patched ramdisk patched_boot.img file must be in the same path, from which you will be running commands below in CMD window
9. Type "adb " in CMD window to start android debug bridge
10. Type "adb reboot-bootloader" and wait until your device restarts in Download mode
11. Once in Download mode, type "fastboot flash ramdisk patched_boot.img" - you should see some output from flash procedure, indicating successful flash
12. Once patched ramdisk is flashed, type "fastboot reboot"
That is it - you're done. Once your device reboots it will be rooted.
Note 1: Magisk Manager has it's own built-in superuser app and uses Systemless root, which works completely differently - you will not see external, standalone app like SuperSU or SU you might be familiar with in your App Drawer. The way to control the superuser app is from Magisk Manager itself: Settings->Superuser section
Note 2: I don't do tech support via PM, so don't PM me for help or with questions. Use the thread instead, and some other XDA members or myself will probably help you. Good luck!
Note 3: You may find some links to Huawei stock firmware in the 2nd post
UPDATE - August 6, 2018
Huawei officially approved 8.0.0.171 firmware with GPU Turbo for installation on SHT-AL09 devices. If you're doing first time root - just follow the original steps above. If you are already rooted and want to upgrade to 8.0.0.171 - follow the steps below:
1. Boot into download mode:
Code:
adb reboot-bootloader
from CMD window
2. Flash stock recovery from 8.0.0.171 to your device in fastboot:
Code:
fastboot flash recovery_ramdisk recovery_ramdis.img
3. Download and install the official OTA through Settings (full or just the update)
4. Boot into download mode again and flash patched ramdisk from 8.0.0.171
Code:
fastboot flash ramdisk patched_boot.img
5. OPTIONAL: If you were using TWRP or any custom recovery - you will need to reflash it back
Code:
fastboot flash recovery_ramdisk twrp.img
or whatever you named your custom recovery image
REMINDER: Do NOT use ramdisk image I provided for any other model besides SHT-AL09 - doing so is guaranteed to render your device unusable. This patched ramdisk is ONLY for SHT-AL09. You will need to extract your own ramdisk from stock firmware, specific to your device model
Needless to say, all the images you are going to flash must reside in the same directory, from which you are going to be running the CMD commands. If your ADB/Fastboot folder is not in your WIndows' PATH environmental variable - the images must be placed in the same folder where ADB/Fastboot binaries are, and CMD commands must be run from that folder.

C5Longhorn said:
Yes, they still work. I have the same model and build as you and I'm rooted.
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
I'm considering buying an SHT-W09 with firmware version 8.0.0.200 (C567), but I'd like to know if I can root it first. I do not know if the bootloader has been unlocked. Since you have the same version, can you confirm that it's possible to unlock and root, and if so, sketch out how it's done? I'm confused about whether it's possible with this firmware.

samiller said:
I'm considering buying an SHT-W09 with firmware version 8.0.0.200 (C567), but I'd like to know if I can root it first. I do not know if the bootloader has been unlocked. Since you have the same version, can you confirm that it's possible to unlock and root, and if so, sketch out how it's done? I'm confused about whether it's possible with this firmware.
Click to expand...
Click to collapse
Unlocking is possible *only* if you've gotten already your unlock code. As this service was suspended about 2 years ago there is no easy way to get it unlocked.

Small request to developers, or people with access to reliable file hosting: I don't have a developer account, so all the files I linked or referenced in the OP are hosted on free hosting sites. That file hosting has expiration date and max downloads limit, so the files will become inaccessible sooner rather than later. Please upload these files to reliable hosting and create a post with the links. I will link your post in the OP as a mirror.
In the meantime, mirror for SHT-W09 firmware: https://mega.nz/#!asVjmZrR!bW2OmXgTjnyVN4pqb9fA7OzAJ4bzil7YZxNW14qoCmk

I can confirm that this works on the 10.8" wifi model using the devices relevant ramdisk.img.

Hello, can somebody test sixaxis controller tool with root and magisk? There is a Trial in Google Play Store, that is called sixaxis compatibility checker without purchise the App. Maybe i want to buy the Tablet, but only with Dualshock 4 Support...

Just a heads up, been following threads on this forum for flashing a GSI. Now that you guys can root, you can also make backups of your own stock system image if you can't find one from Firmware Finder. Then you can safely try flashing the GSI.

@MishaalRahman well it's bit like chicken egg dilemma. As we do not have a stock system image for e.g. SHT-W09 we cannot patch the ramdisk.img and so we cannot get the stock system image ...

Thanks Apo11on, great to have root so soon for the M5! Do you know if there's a way to get Xposed working? I tried the Xposed Framework SDK 26 from inside Magisk, but it put me in a boot loop.

Question is, for those of us with the Non Pro version, can this still be done.

@OHP Yes. The OP did it with the 8.4" version which has no pro option.
I'm looking to buy the Chinese 10" wifi version myself but need Google Play Store + Services on it which I'm guessing the Chinese version doesn't have. Is one of the firmwares at the website you link to a global version of the firmware that will work on this model?

OHP said:
Question is, for those of us with the Non Pro version, can this still be done.
Click to expand...
Click to collapse
Doesn't matter what version you have as long as you have access to your device firmware and the ramdisk.img. You really need to reread the guide.

magnumlove said:
Doesn't matter what version you have as long as you have access to your device firmware and the ramdisk.img. You really need to reread the guide.
Click to expand...
Click to collapse
Problem I have is :
CMR-W09C432B123 (8.0.0.123) from download headlines.
notice the Bold letter.
my Firmware on device:
CMR-W09C432123 (8.0.0.123)
obliviously it could be nothing but I wouldn't want to brick my tablet :fingers-crossed:

OHP said:
Problem I have is :
CMR-W09C432B123 (8.0.0.123) from download headlines.
notice the Bold letter.
my Firmware on device:
CMR-W09C432123 (8.0.0.123)
obliviously it could be nothing but I wouldn't want to brick my tablet :fingers-crossed:
Click to expand...
Click to collapse
I have exactly the same tablet/firmware as you and it was fine. The additional letter also threw me a little. But if you are unsure, download Huawei Firmware Finder from Google play and it will automatically detect your tablets firmware (which you can download if you wish).

magnumlove said:
I have exactly the same tablet/firmware as you and it was fine. The additional letter also threw me a little. But if you are unsure, download Huawei Firmware Finder from Google play and it will automatically detect your tablets firmware (which you can download if you wish).
Click to expand...
Click to collapse
I took the plunge, and I am sucessfully rooted now :silly:

struggling with this part
2. Transfer this patched ramdisk image to your device
Note for users with version of M5 other than SHT-AL09: Do NOT use the above ramdisk image. Download the full stock rom (update.zip) from the site I linked in the credits. Extract UPDATE.APP file from the zip. Then use HuaweiUpdateExtractor to extract ramdisk.img specific to your device. If you get errors in HuaweiUpdateExtractor - uncheck first 2 checkboxes for checksum verification on Settings tab and try again
I have a CMR-W09 :s i can got the files downloaded and the huwai software not sure how i make a img

The good news is I followed these instructions yesterday and they worked perfectly (SHT-AL09).
The bad news is, I seem to have lost root overnight.
---------- Post added at 06:41 AM ---------- Previous post was at 06:22 AM ----------
And I figured out why I lost root; I was playing around with Developer options and switched the default GPU renderer from 'default' to 'Skia.' Apparently, this disables root access until you switch back. I regained root access on a reboot, lost it again after switching back to Skia, and then regained it after switching back to default.

I got the right image file from the site and huwai extract. I have googled how to use this app but what files do I extract as there appears to be. Alot ? I extracted all of them ? I don't have a ramdisk.img
Also thanks for writting this up. Without it I would be lost

Thanks for the efforts making this thread. Unfortunately my device is SHT-W09 and I'm still waiting for the right firmware. Is there anything I can help, considering I have the device?

@dkk6 I am in the same boat as you. Unfortunately I installed the update to 8.0.0 123 without having the Firmware Finder installed on the device. Do you have installed already the update to 8.0.0 123?
If not, you could install Firmware Finder and provide us with the ota url ...

This works perfectly no issues. i had some how maanged to download the wrong rom first. AND thankfully it did not have a ramdisk in. it is important that your firmware matches the firmware present on the site as explained. This was easy guide to follow now to flash it with somthing other then andriod

AndDiSa said:
@dkk6 I am in the same boat as you. Unfortunately I installed the update to 8.0.0 123 without having the Firmware Finder installed on the device. Do you have installed already the update to 8.0.0 123?
If not, you could install Firmware Finder and provide us with the ota url ...
Click to expand...
Click to collapse
I'm on 8.0.0.101

[Guide][Installation][Fix]Switching from stock ROM to custom ROMs + Installing stock ROM after a brick or other Failures ( Mi A2 Lite - Daisy)

This guide is general guide for the installation of custom ROMs. I will also include guide to install stock ROM on devices which have been bricked or for solving various problem which you may encounter in custom ROMs. There are other guides for the same purpose but most of them are outdated and many of you seem to ignore old guide despite the fact that those guides can be helpful.
This is guide is only relevant for installation of custom ROMs which were released up to the date of posting this guide or up to android version 11. Recovering a bricked device can be done in the same way as to this one but installation instruction for devices with android version greater than 11 may differ.
DISCLAMER
Code:
I am NOT responsible for bricked devices,
thermonuclear war or for you getting fired because your alarm app failed.
Make sure the bootloader is unlocked and never lock the bootloader
How to unlock bootloader ?
>See in this thread.
Hard Brick, Soft brick, Problems in custom rom due to bad base, installation of base for switching to custom roms: windows linux
Installation of stock ROM through fastboot : The reply below
Migration from stock base to custom ROM : CLEAN FLASH
Migration between different version of same custom ROM : DIRTY FLASH
FOR SPECIFIC THREADS
Oragne Fox For Daisy
TWRP For Daisy
Magisk
CREDITS:
LInkBoi for his previous guide and TWRP
DarthJabba9 for Orange Fox Recovery
Every pros in daisy telegram groups.

EDL FLASHING (For windows only)​
EDL flashing can be helpful when flashing every partition of device is needed either for clean stock base or after brick or after some failure.
EDL flashing can be the final resort when everything else fails.
PREREQUISITES
1) A good USB cable, your phone
2) A PC with either windows or linux
3) Fastboot drivers from google and edl drivers from qualcomm
4) Platform tools from google
5)Fastboot rom. This should be full rom in .tgz format.
6)Xiaomi flash tool (LATEST VERSION AVAILABLE)
Install the adb and fastboot drivers from google. If you are on windows 10 or greater then you can also use "windows update > optional updates" to update adb and fastboot drivers + edl drivers. For the installation of drivers always use trusted sources and don't turn of driver signature enforcement if you can.
Extract the platform tools in a convenient folder, we will be doing our operations from this folder for fastboot and adb opeartions. Extract the fastboot ROM and place that in convenient folder as well. And for xiaomi flash tool extract the zip and launch XiaoMiFlash.exe .
If you can access fastboot in you phone then the phone can be booted into edl mode through fastboot else you have to take out back cover and short the testpoint pins to make the device boot into edl mode (see the attached image ).
If you can access fastboot. Boot into fastboot and type the following command in terminal.
To check if device is connected properly and drivers are properly installed
If no devices is shown then connect device properly with good usb cable and check the drivers.
Code:
fastboot devices
To boot phone into edl mode. This is only possible if the bootloader is unlocked else testpoint-edl is the only option
Code:
fastboot oem edl
The device should be shown as COM device in device manager ( Windows ). If not then either drivers aren't installed properly or your phone isn't in edl mode.
Now click on refresh button in xiaomi flash tool. Your device should be recognized as com device. Set the path to the images folder ( extracted fastboot rom ). Select CLEAN ALL option . If everything is good then click
on FLASH. The flashing process should start now. After the process completes keep pressing power button to boot device into the currently installed ROM.
Just install the rom and setup once even if you're going to flash custom rom next. This reduces various problems which may come in custom ROMs.
If any error occurs then try the following:
Make sure you are using latest flash tool.
Good fastboot rom (shouldn't be corrupted )
Good USB cable and try different ports of the PC.
The flashing should be done immediately after booting to edl. If not then take out battery and reconnect it if you have back cover open(In case of hard brick). Or keep pressing power button and volume down to boot into fastboot and boot to edl mode again from the above instructions(If fastboot is accessible)
For booting to edl using testpoint:
> Take out backcover
> Disconnect battery
> Short the pins
> Flash
> Connect battery after flashing is complete
> Keep pressing power button to boot into system.

qdl flashing ( linux only )​
For very detailed guide github -> bkerler edl
Thanks to DEFXZ and LinkBoi for suggesting this alternative.
Make sure you have platform tools, fastboot rom and other prerequisites to detect device properly.
clone the repository in convenient place
Code:
git clone https://git.linaro.org/landing-teams/working/qualcomm/qdl.git --depth=1
change to qdl directory
Code:
cd qdl
Build qdl tool
Code:
make
Finally flash the rom
Code:
./qdl --storage emmc --include /path/to/stock/images /path/to/stock/images/prog_emmc_firehose_8953_ddr.mbn /path/to/stock/images/rawprogram0.xml /path/to/stock/images/patch0.xml
The paths are the paths to various files inside the images folder which will be obtained after fastboot rom is extracted.
For further informations:
Original github link
qdl discussion in XDA

FASTBOOT FLASHING​
PREREQUISITES
FASTBOOT DRIVERS
PLATFORM TOOLS
FASTBOOT ROM
GOOD USB CABLE
PC WITH WORKING USB PORT
See this for meeting prerequisites.
Install fastboot drivers, connect device to PC via USB.
Extract platform tools into a convenient folder.
Extract fastboot ROM into a convenient folder.
Go to platform tools folder ( this will contain files and executable like fastboot.exe) and open powershell or any terminal window there
[ shift + right click and select open (powershell) window here ]
Type this command to see everything worked correctly.
Code:
fastboot devices
If not then check every step properly.
Now execute the script to flash the ROM.
Execute flash_all.bat script for windows PC.
Execute flash_all.sh script for linux PC.
If platform tools cannot be accessed system wide then.
Code:
./fastboot devices
will provide fastboot devices information.
For flashing drag and drop flash_all.bat or flash_all.sh file into the terminal.
Code:
'/media/user001/user/daisy/stock_roms/daisy_global_images_V10.0.18.0.PDLMIXM_9.0/flash_all.sh'
It will look something like this in linux and similar in windows.
If any error occurs the search for particular error. Most of the times the error is due to corrupted fastboot ROM or bad connection between phone and PC.

FINALLY! FLASHING CUSTOM ROM​
STEP 0
Flash(if not flashed already) the stock base recommended by particular ROM, if the ROM doesn't recommend a specific stock base flash 10.0.18.0 from the above instructions.
PREREQUISITES
TWRP or ORANGE FOX RECOVERY
Fastboot drivers and platform tools (details above )
The ROM which you want to flash, choose from here
GAPPS package if rom is vanilla and you want to install it.
Magisk if you want to root.
As you may have known by experience, our device doesn't have recovery partition so, flashing recovery through fastboot isn't possible. For flashing recovery first we need to boot recovery image and then only we can flash it.
If you want to use twrp:
Download both twrp*.zip and twrp*.img and place it in a convenient place.
If you want to use orange fox recovery:
Download orangeFox*.zip and extract it.
Keep both the .zip and .img file in convenient place.
If you have sdcard then copy ROM file, gapps, magisk, twrp or orange fox files into sdcard.
If not then there will be further instructions.
Now, connect the phone to the PC via USB and enable usb debugging. And open terminal in the platform tools folder as in above instructions.
Check device connectivity:
Code:
adb devices
Reboot into fastboot:
Code:
adb reboot bootloader
Check device connectivity:
Code:
fastboot devices
Lets check if the bootloader is unlocked:
Code:
fastboot oem device-info
If bootloader isn't unlocked you won't be able to flash custom recovery into the device. So, first unlock the bootloader. This should be allowed in the developers option of your phone first. This will factory reset the device.
Code:
fastboot oem unlock
Now if everything is good then it's time to boot into custom recovery:
Code:
fastboot boot recovery.img
recover.img is name of image of whichever custom recovery you want to use.
Code:
fastboot boot '/media/user001/storage (1)/daisy/twrp/twrp-3.5.2_9-2-daisy-unofficial.img'
It's like this in my case. You can drag and drop after typing fastboot boot
The phone should now boot into custom recovery. If it ask for decryption then your lockscreen password should work there.
if you want to flash recovery only then find the recovery.zip you want and flash it.
The steps further is also valid for moving between different custom roms. The term used for such process is CLEAN FLASH.
For Flashing custom ROMS :
SOMETIMES FLASHING INSTRUCTIONS MAY DIFFER SO, BE SURE TO CROSS CHECK FOR INSTRUCTION IN ROM SPECIFIC XDA THREAD OR TELEGRAM GROUP
The following action will wipe userdata if not wiped already. Be sure to backup data before these steps. Also if you encounter any future problems full backup from custom recovery may be able to solve most of the problems. So, be sure to keep full backup(including every partition) of your device.
Go to main menu > wipe > select all except internal storage and microSD.
Swipe right to perform wipe.
Install custom recovery by flashing recovery.zip
(This is done in case adb push doesn't work below and sdcard isn't available for flashing)
Again go to main menu > wipe > format data
Type yes and press enter.
If you don't have files in your sdcard then:
push rom file + gapps + other files into your device through adb push.
The command will be something like this:
Code:
adb push '/media/user001/storage (1)/daisy/posp/potato_daisy-11-20210919-dumaloo.v4.2.3+20.Community.zip' /sdcard
If adb push fails to work then you can reboot recovery and simply copy the files through file explorer.
Reboot to recovery only if you had installed recovery after wiping system else the device will soft brick
Now flash the rom.zip by selecting the file and swiping right.
Flash custom recovery if the ROM doesn't contain recovery
We have to change current slot even if we don't want to flash anymore things.
Latest recoveries changes slot automatically So, go to main menu > reboot > recovery
Now flash files which you want to flash i.e. gapps and magisk.
Again, Don't flash gapps if the ROM is of Gapps variant
Most of the roms now have implemented FBE (File Based Encryption ). So, you need to format data before rebooting to system. Again, check for specific ROM installation instruction if that is required or not. If you keep data from previous ROM that won't be considered a clean flash so, for proper clean flash format data before rebooting to system.
reboot system

MOVING BETWEEN DIFFERENT VERSION OF SAME CUSTOM ROM
Dirty flash or OTA ​
Most of the newer ROMs have seamless update ( even the unofficial ones ). The OTA update is simple. Just go to updater ( in settings > system or native app, depends upon the rom). If your ROM is of vanilla version then make sure gapps and/or magisk which you have installed, your ROM and custom recovery all support addon.d survival script. If they don't then you may have to flash everything again after update process is complete.
If custom recovery itself doesn't support update then you may need to choose different recovery or dirty flash ROM from the recovery. Don't worry most of the roms and both the recoveries for daisy support OTA and addon.d survival.
DIRTY FLASH​The process of flashing a ROM on top of existing one keeping the /data partition intact is known as dirty flashing. Such flashing must be done only on different builds of same ROM and it isn't recommended to flash build of lower version on top of higher version.
The steps for dirty flashing:
Download the update package.
Reboot to recovery
Enter password for decryption if encrypted.
Flash the update.zip package.
Reboot recovery, if recovery/rom doesn't support survival of recovery then flash recovery before rebooting to recovery.
If gapps and/or magisk survival isn't supported then flash gapps and magisk, make sure gapps is of the same type which was flashed before.
reboot system

Hi @user-001 thanks for this.
I'm on a stock A2 lite thats never had anything done to it , am i right in thinking i follow the clean flash section ?
You mention in there
We have to change current slot even if we don't want to flash anymore things.
Click to expand...
Click to collapse
I'm not fully sure what that involves could you break it down the steps a little for me.
I've downloaded all the files and am set up but i'm unsure on the Flashing fastbbot section where you say to use these files..
Execute flash_all.bat script for windows PC.
Click to expand...
Click to collapse
Is this a section i can bypass ? if not where can i get them from ?
Cheers

steve.loveday said:
Hi @user-001 thanks for this.
I'm on a stock A2 lite thats never had anything done to it , am i right in thinking i follow the clean flash section ?
You mention in there
I'm not fully sure what that involves could you break it down the steps a little for me.
I've downloaded all the files and am set up but i'm unsure on the Flashing fastbbot section where you say to use these files..
Is this a section i can bypass ? if not where can i get them from ?
Cheers
Click to expand...
Click to collapse
1) Yes you should follow clean flash instructions.
2)Changing of slot is done in custom recovery. Precisely in the reboot menu. But newer recoveries automatically switch the slot after flashing the rom , just be sure to reboot to recovery after flashing the recovery zip file.
3) the flash_all.bat script will be inside the extracted rom(fastboot rom) folder. You can use xiaomiflash too for flashing through fastboot.

user-001 said:
1) Yes you should follow clean flash instructions.
2)Changing of slot is done in custom recovery. Precisely in the reboot menu. But newer recoveries automatically switch the slot after flashing the rom , just be sure to reboot to recovery after flashing the recovery zip file.
3) the flash_all.bat script will be inside the extracted rom(fastboot rom) folder. You can use xiaomiflash too for flashing through fastboot.
Click to expand...
Click to collapse
Hi thanks for the reply,
I'm getting confused with all the various guides all seem to want you to do it a different way.
As i'm wanting Lineage thier instructions are...
Installation:
Download the latest build from here
Download LinkBoi00's version of TWRP here
Reboot to bootloader (adb reboot bootloader)
Fastboot into TWRP recovery (fastboot boot twrp*.img)
Do a factory reset in TWRP
Flash the latest build of Lineage OS
Boot into your new phone
Click to expand...
Click to collapse
Theres no mention of the edl or fastboot flashing and also the fastbot rom i downloaded doesnt have the flash_all.bat script in the zip file.
So do i follow thier instructions or these ones ?
Cheers

steve.loveday said:
Theres no mention of the edl or fastboot flashing and also the fastbot rom i downloaded doesnt have the flash_all.bat script in the zip file.
So do i follow thier instructions or these ones ?
Cheers
Click to expand...
Click to collapse
This guide deals with how to do something rather than what to do, meaning you should always do what particular rom suggests but the way to do this is mentioned here.
edl or fastboot flashing comes under clean flashing with new base, most of the time you aren't required to do this.
The script should be clean_all.bat or something similar just don't execute script with lock in the name(it will lock the bootloader)
And if you're already on the recommended base you don't have to flash the fastboot rom.

First of all, thank you very much for the detailed guide. What you have done here took a lot of work to do but it will help a lot of people (including me) to understand, albeit rudimentarily, the structures and functions of the devices etc.
For all that, thanks again.
When I start using the guide, I will update this post with any questions, such as :
fastboot boot '/media/user001/storage (1)/daisy/twrp/twrp-3.5.2_9-2-daisy-unofficial.img'
why not doing below? (For those who, like me, are not very familiar with linux.)
1. > adb push <twrp.img> /sdcard or same adb push "C:\platform-tools\twrp-3.5.2_9-2-daisy-unofficial.img" /sdcard
( which means push <file> from "adb|platform-tools\ folder" (eg. C:\platform-tools\)
into the root of <internal storage> | /storage/emulated/0 )
2. Reboot from adb to fastboot:
> adb reboot bootloader
3. Boot the image from <internal storage>:
> fastboot boot /sdcard/twrp-3.5.2_9-2-daisy-unofficial.img
What is the "Red" pointed and "Yellow" addresses"?
fastboot boot '/media/user001/storage (1)/daisy/twrp/twrp-3.5.2_9-2-daisy-unofficial.img'

I followed your "EDL FLASHING" post (#2) and it worked exactly as you mention!
In short, I was comming from unsuccessful flashing... but this is out of topic.
For me, did not worked the first time (after restarts) but the other day worked perfect.
The point is, most of times, it's becase windowz drivers.
We have to point that windowz needs their time to take the drivers in place. So, be patient and leave windowz to (not forced) restart(s).

AntonyMan said:
What is the "Red" pointed and "Yellow" addresses"?
fastboot boot '/media/user001/storage (1)/daisy/twrp/twrp-3.5.2_9-2-daisy-unofficial.img'
Click to expand...
Click to collapse
That must be your terminal representing different type of character in different colors.
Or, Are you talking about something else ?

steve.loveday said:
Theres no mention of the edl or fastboot flashing and also the fastbot rom i downloaded doesnt have the flash_all.bat script in the zip file.
So do i follow thier instructions or these ones ?
Cheers
Click to expand...
Click to collapse
For future references, the extracted fastboot ROM should be like this and you need to execute flash_all.bat or flash_all.sh script depending upon your OS or terminal.

user-001 said:
That must be your terminal representing different type of character in different colors.
Or, Are you talking about something else ?
Click to expand...
Click to collapse
Of course I'm talking about something else. lol
I was talking about that 'strange' address. fastboot boot '/media/user001/storage (1)/daisy/twrp/twrp-3.5.2_9-2-daisy-unofficial.img' (explained in post #11)
There is not such a directories in my miA2Lite phone. Obviously, it's because you are on Linux or Mac (UNIX). On Windowz 'command prompt' syntax it's slightly different.
Thus, I typed fastboot boot "/sdcard/twrp-3.5.2_9-2-daisy-unofficial.img"
* /sdcard is the root of <internal storage> directory.
** On Windows, double quote the address, if it's include spaces.

AntonyMan said:
Of course I'm talking about something else. lol
I was talking about that 'strange' address. There is not such a directories in my miA2Lite phone.
Thus, I typed fastboot boot "/sdcard/twrp-3.5.2_9-2-daisy-unofficial.img"
* /sdcard is the root of <internal storage> directory.
** On Windows, double quote the address, if it's include spaces.
Click to expand...
Click to collapse
The twrp image was on my pc(linux) i was booting directly from pc's terminal. And if you use only adb(or fastboot) then the paths are pc's absolute paths.

Question Switch from Xiaomi.eu ROM to another custom rom?

Hello xda community, i have a poco x4 pro running on latest xiaomi.eu stable rom and i would like to flash a other custom rom like evolution x, but i can't get it to run.
If i try to do "fastboot flash boot <file>" and "fastboot flash vendor_boot <file>" then it returns ok but if i switch to recovery the old MIUI Recovery 5.0 is still present.
How can i finally flash a other recovery like twrp and flash another rom using adb flash? What steps do i have to do?

sebastian5594 said:
Hello xda community, i have a poco x4 pro running on latest xiaomi.eu stable rom and i would like to flash a other custom rom like evolution x, but i can't get it to run.
If i try to do "fastboot flash boot <file>" and "fastboot flash vendor_boot <file>" then it returns ok but if i switch to recovery the old MIUI Recovery 5.0 is still present.
How can i finally flash a other recovery like twrp and flash another rom using adb flash? What steps do i have to do?
Click to expand...
Click to collapse
You put a recovery from this topic
[SHARED][RECOVERY][UNOFFICIAL] TWRP 3.7.0_12 for VEUX/PEUX
Hello everyone, one user under the nickname yurxxl from the site 4 PDA, at my request, will assemble a recovery for us, it was his assembly that I posted in the topic...
forum.xda-developers.com
You download the custom you like, transfer it to a USB flash drive, download it there (to a USB flash drive) and place the recovery from the post above, you will also need to save it on the vendor_boot flash drive, you can take it from the firmware for fastboot or make a backup of it in the recovery.
Well, then you load into the recovery, do the data format, flash the custom, then switch to the recovery slot, download the recovery (twrp) and vendor_boot, and that's it, you load into the new firmware

arraki said:
You put a recovery from this topic
[SHARED][RECOVERY][UNOFFICIAL] TWRP 3.7.0_12 for VEUX/PEUX
Hello everyone, one user under the nickname yurxxl from the site 4 PDA, at my request, will assemble a recovery for us, it was his assembly that I posted in the topic...
forum.xda-developers.com
You download the custom you like, transfer it to a USB flash drive, download it there (to a USB flash drive) and place the recovery from the post above, you will also need to save it on the vendor_boot flash drive, you can take it from the firmware for fastboot or make a backup of it in the recovery.
Well, then you load into the recovery, do the data format, flash the custom, then switch to the recovery slot, download the recovery (twrp) and vendor_boot, and that's it, you load into the new firmware
Click to expand...
Click to collapse
I already downloaded your referenced twrp image, but obtained always the same results as i described in my first post.
I don't get your point with the usb flash drive. I mean it does not make any difference if i store the required files on my pc internal storage or on a usb flash drive.

sebastian5594 said:
I already downloaded your referenced twrp image, but obtained always the same results as i described in my first post.
I don't get your point with the usb flash drive. I mean it does not make any difference if i store the required files on my pc internal storage or on a usb flash drive.
Click to expand...
Click to collapse
You're doing something wrong.Download the archive below, unzip it, copy the downloaded recovery to the platform-tool folder, there is a file there START.exe (I added it there for convenience), run it and get right where you need to, then write: fastboot flash boot (the name of the recovery).img
And about the sd card, you can also use internal memory, but you will first do format data, and accordingly you will erase everything from internal memory, so you need to have all the files for firmware on the sd card, well, or on a flash drive if you flash through OTG

sebastian5594 said:
I already downloaded your referenced twrp image, but obtained always the same results as i described in my first post.
I don't get your point with the usb flash drive. I mean it does not make any difference if i store the required files on my pc internal storage or on a usb flash drive.
Click to expand...
Click to collapse
I'll add, if you haven't watched the spoilers, this is how the installation log should look like.