Can't OTA - HTC One Mini

Hi.
i tried to s-off my device, but no success :/
then recovered stock from twrp, after this i check OTA update and found OTA_M4_UL_K44_SENSE60_MR_HTC_Europe_4.09.401.3-3.10.401.6_release_383386.zip
did factory reset, flashed boot.img and recovery.img from this package: https://docs.google.com/file/d/0B1a-JXNXbe8wbkNxbnhncEZDdUU/edit?pli=1
tried to update, it,s failed.
my device:
tempered
relocked
s-on
h-boot 2.22
radio-1.24.40e.00.26
OS-3.10.401.6 (4.09.401.3)---> red color?????
eMMC-boot 1024MB
Jun 24 1014, 15:21:25.0
any help?
tried flash zip via fastboot oem rebootRUU
FAILED: (remote: 12 signature verify fail)

nicniewid said:
Hi.
i tried to s-off my device, but no success :/
then recovered stock from twrp, after this i check OTA update and found OTA_M4_UL_K44_SENSE60_MR_HTC_Europe_4.09.401.3-3.10.401.6_release_383386.zip
did factory reset, flashed boot.img and recovery.img from this package: https://docs.google.com/file/d/0B1a-JXNXbe8wbkNxbnhncEZDdUU/edit?pli=1
tried to update, it,s failed.
my device:
tempered
relocked
s-on
h-boot 2.22
radio-1.24.40e.00.26
OS-3.10.401.6 (4.09.401.3)---> red color?????
eMMC-boot 1024MB
Jun 24 1014, 15:21:25.0
any help?
tried flash zip via fastboot oem rebootRUU
FAILED: (remote: 12 signature verify fail)
Click to expand...
Click to collapse
im not sure but i think it failed because you didnt have s off when you tried to flash it

The OTA's will fail if you have changes files that the OTA wants to patch, or if those files are missing.
If you are purely stock (or odex stock root dump from somewhere) the update should work (it did for me at least).
Also, make sure you are on 3.10.401.6 (note the 6 at the end), there is a rom here somewhere with 3.10.401.4 which will not take the OTA towards 4.09.xxx.
The most likely files that are 'changed' on which the 4.09 OTA is failing, are the 'stock apps' that are on the _data_ partition (not /system). Since your /data partition is wiped when you htcdev-unlock, you lose some of the stock apps (like flashlight, sound recorder, etc..). Since this 4.09 OTA patches two of them, the OTA checks if the files are there and are still the same.
Take a look in the OTA package you had the recovery.img and boot.img from. You'll see there is a /data folder in it. Make sure the files in this folder are in your /data folder (you can use 'adb push' from TWRP, or place them on your internal storage and then move them over from TWRP if you know some linux cmdline commands). A root-file-explorer app can also work.
In a nutshell, take the /data/preload folder from the 3.10.401.6 OTA and make sure the files from there are in a /data/preload folder on your device. Then try the OTA towards 4.09.401 again.

dipje said:
The OTA's will fail if you have changes files that the OTA wants to patch, or if those files are missing.
If you are purely stock (or odex stock root dump from somewhere) the update should work (it did for me at least).
Also, make sure you are on 3.10.401.6 (note the 6 at the end), there is a rom here somewhere with 3.10.401.4 which will not take the OTA towards 4.09.xxx.
The most likely files that are 'changed' on which the 4.09 OTA is failing, are the 'stock apps' that are on the _data_ partition (not /system). Since your /data partition is wiped when you htcdev-unlock, you lose some of the stock apps (like flashlight, sound recorder, etc..). Since this 4.09 OTA patches two of them, the OTA checks if the files are there and are still the same.
Take a look in the OTA package you had the recovery.img and boot.img from. You'll see there is a /data folder in it. Make sure the files in this folder are in your /data folder (you can use 'adb push' from TWRP, or place them on your internal storage and then move them over from TWRP if you know some linux cmdline commands). A root-file-explorer app can also work.
In a nutshell, take the /data/preload folder from the 3.10.401.6 OTA and make sure the files from there are in a /data/preload folder on your device. Then try the OTA towards 4.09.401 again.
Click to expand...
Click to collapse
Everytfing works fine, i'm very thankful Do You know how to restore stock apps like flashlight or calc?

nicniewid said:
Everytfing works fine, i'm very thankful Do You know how to restore stock apps like flashlight or calc?
Click to expand...
Click to collapse
Depends for which ROM you are using now. There are some threads around, and you can find in them in _some_ of the OTA packages.
If you are on the latest 4.4.2 with Sense6, there is this thread: http://forum.xda-developers.com/showthread.php?t=2696399 but I have no clue if they work alright.
Also, if you download the OTA file from here (http://forum.xda-developers.com/showthread.php?t=2575766) inside that .zip file is a /data/preload folder which contains Calculator and Flashlight (and maybe some other needed files).
If you are on 4.3 with Sense 5.5, there is a link to the stock rom here (http://forum.xda-developers.com/showthread.php?t=2575766) that in the first post at the bottom has a Mega downlink link to 'the missing apps'.
The original files were in /data/preload on your device, and since doing the htcdev-unlock thing clears the entire /data, you will lose them. If you made a proper backup your original files maybe in there. Most OTA packages include these files as well, or maybe patches to the existing files (which are useless if you don't have the originals).
I gave some links by quickly searching, if you need more and for another version do please use the search function, they are around here.

Related

How to flash back to original RC29? I've flash back my recovery and boot image

How to flash back to signed-kila-ota-115247-prereq.TC4-RC19+RC28.zip?
I've flashed my mtd1 and mtd2 which I backed up before I apply the modified recovery.img.
But when I do the reboot and update, It said:
"E: No signature (376 files)"
"E: Verification failed"
It seems I dont get my images flashed correctly, be I'm sure the boot image was flashed..
fluke.l said:
How to flash back to signed-kila-ota-115247-prereq.TC4-RC19+RC28.zip?
I've flashed my mtd1 and mtd2 which I backed up before I apply the modified recovery.img.
But when I do the reboot and update, It said:
"E: No signature (376 files)"
"E: Verification failed"
It seems I dont get my images flashed correctly, be I'm sure the boot image was flashed..
Click to expand...
Click to collapse
I'm assuming you have the modified recovery.img installed. Run SignApk.jar on the signed-kila-ota-115247-prereq.TC4-RC19+RC28.zip. Rename it to update.zip and put it on the sdcard (taking care to unmount the usb mass storage before unplugging). Boot into recovery menu (Home+Red) and Alt+S to flash. When it's done press Home+Back as prompted. That should do it.
Isn't the official RC29 update.zip signed with google's private key?
How could I sign it?
I'm just recovered to the offcial boot.img and recovery.img, which were backed up by myself from mtd1 and mtd2.
The way signing works with java archives is rather than encrypting the files themselves, the signing process simply adds a list of filehashes encrypted with the priv key. Resigning simply overwrites this list with your own (in this case the test private keys).
If you want to install with the original stock ota update then flash the original recovery.img (you can extract it from the stock ota update).
jashsu said:
The way signing works with java archives is rather than encrypting the files themselves, the signing process simply adds a list of filehashes encrypted with the priv key. Resigning simply overwrites this list with your own (in this case the test private keys).
If you want to install with the original stock ota update then flash the original recovery.img (you can extract it from the stock ota update).
Click to expand...
Click to collapse
Thanks. I got it.
I'll do this soon.
I've failed with log into google account many times with the unofficial update package.
Everytime when I finished log in, the com.google.setupwizard throws exception.
Right I have the modified RC30 and the modded recovery & boot image.
I'm going to return my G1 for a new one but before i do, i need to flash it back so it can install the OTA updates. (Phone keep shutting off when i close my screen) I want to make sure what I'm going to do is correct so i don't brick my phone.
Download the RC29 patch and extract the recovery & boot img.
Flash the images into the phone.
Is this correct ?
Thanks for the help
You don't need to reflash recovery or boot. Use SignApk.jar on the official RC29 or RC30 and put it in the root of memcard. Reboot and flash. Should be official. You have to sign it with test keys or the modified recovery will reject it.
jashsu said:
You don't need to reflash recovery or boot. Use SignApk.jar on the official RC29 or RC30 and put it in the root of memcard. Reboot and flash. Should be official. You have to sign it with test keys or the modified recovery will reject it.
Click to expand...
Click to collapse
Alright thanks a lot.

[701] Latest update for JBAcer_A701_AV051.RV03RC02_AV051.RV05RC07_WW_GEN1

Ok, here's the latest update for the 701 JB Acer_A701_AV051.RV03RC02_AV051.RV05RC07_WW_GEN1
Should update to build .051
From the looks inside, looks like touchscreen changes and boot.img changes via a patch.
File is decrypted already. For stock 701 users, probably rename the file to "update.zip", copy to Ext SD, reboot tab holding Vol+ and PWR. Should work.
For others, through a JB CWM.
NOTE: This contains a new bootloader.blob file, and the usual recovery sh. So, if you don't edit the blob file and the recovery part out of the installscript and zip, it will probably overwrite your unlocked bootloader and CWM. Also, it patches all apks and odex's in /system and /system/framework.
Also, if you are running my hacked fully RW boot.img, might want to fastboot the stock one back before running the patch.
No, I haven't installed it yet. Probably tomorrow. Am on a beer party right now.
DOWNLOAD
MD

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

TWRP always says 'permission denied' & filenames are completely different

Hi,
I have a Mate 9 , Build No. MHA-L09C432B182
Baseband is 21.516.00.00.010
Kernel: 4.1.18-g0ad0fb3
I unlocked bootloader, it is defenetely unlocked. I am able to install TWRP.
I installed twrp-3.0.2 and also twrp-3.1.0 versions but have same problems in both versions:
filenames/folder names in /sdcard (internal storage) are broken, I mean their original names are gone, all files and folders are named like imbj9yf1fATc4Tvm5zt+ and so on instead of Screenshots for example.
So I cannot find my supersu.zip but however I think it would not install, because of this error:
Also I cannot run a TWRP backup, it shows:
Backup started
Backup Folder /data/media/0/TWRP/Backups/UGM2171100001069/2017-07-21-13-11-39_NRD90M...
Can not create '/data/media/0/TWRP' folder (Permission denied)
Failed to make backup folder
I tried to CHMOD 755 this folder/path, did not work/help
Can anybody help me here?
Thx and best!
/data is encrypted by default using file based encryption. That's why you see those files in /sdcard (/data/media/0/). You can remove encryption by using Wipe - 'Format Data' button.
This will remove everything in /data including your files in /sdcard.
To flash stuff you can use an external SD card or remove encryption or flash this twrp: https://mega.nz/#!xg9hWbpJ!dNOWJVUuD_4JL8N8PiDXYsj3SnvaOfKxBndvWc_4wgo
and adb push (adb push file.zip /cache/file.zip) to /cache and flash from there. /cache is added as storage with that twrp.
If you want to remove encryption, flash official SuperSU 2.82 SR1: https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Or Magisk 13.3: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Both require at least twrp 3.1.0.
If you chose to remove encryption you will also have to flash public and HW zips after Format Data, because files in /data/hw_init are removed which are needed for themes to work and 'System Update' and a few Huawei apps.
Public zip for L09C432B182:
http://update.hicloud.com:8180/TDS/...55/f1/full/public/update_data_full_public.zip
Hw zip for L09C432B182: http://update.hicloud.com:8180/TDS/...04/v84355/f1/full/hw/eu/update_full_hw_eu.zip
Flash public first then hw. Both will give errors but install fine.
If you don't want to remove encryption you won't be able to backup /data.
If so use this SuperSU: https://mega.nz/#!18FW1QTQ!3DCA3KrIUSRqEu4L-expci4HcKtk6F25fE1u6ecJV9Q
Or magisk 13.3: https://mega.nz/#!I4FQzbyA!gBZelHmD3lGGwzGISUXkf7GQTUAq5i785d_qPHQOaVE
thanks for all your info.
Can you suggest what to do? Acutually I just want to install root to get titanium to work because I have older backups I want to look into to. After that I want to unroot again.
Not sure if i need encryption or if ishould decrypt now
Whats the best way for me now?
ante0 said:
/data is encrypted by default using file based encryption. That's why you see those files in /sdcard (/data/media/0/). You can remove encryption by using Wipe - 'Format Data' button.
This will remove everything in /data including your files in /sdcard.
To flash stuff you can use an external SD card or remove encryption or flash this twrp: https://mega.nz/#!xg9hWbpJ!dNOWJVUuD_4JL8N8PiDXYsj3SnvaOfKxBndvWc_4wgo
and adb push (adb push file.zip /cache/file.zip) to /cache and flash from there. /cache is added as storage with that twrp.
If you want to remove encryption, flash official SuperSU 2.82 SR1: https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Or Magisk 13.3: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Both require at least twrp 3.1.0.
If you chose to remove encryption you will also have to flash public and HW zips after Format Data, because files in /data/hw_init are removed which are needed for themes to work and 'System Update' and a few Huawei apps.
Public zip for L09C432B182:
http://update.hicloud.com:8180/TDS/...55/f1/full/public/update_data_full_public.zip
Hw zip for L09C432B182: http://update.hicloud.com:8180/TDS/...04/v84355/f1/full/hw/eu/update_full_hw_eu.zip
Flash public first then hw. Both will give errors but install fine.
If you don't want to remove encryption you won't be able to backup /data.
If so use this SuperSU: https://mega.nz/#!18FW1QTQ!3DCA3KrIUSRqEu4L-expci4HcKtk6F25fE1u6ecJV9Q
Or magisk 13.3: https://mega.nz/#!I4FQzbyA!gBZelHmD3lGGwzGISUXkf7GQTUAq5i785d_qPHQOaVE
Click to expand...
Click to collapse
thanks for all your info.
Can you suggest what to do? Acutually I just want to install root to get titanium to work because I have older backups I want to look into to. After that I want to unroot again.
Not sure if i need encryption or if ishould decrypt now
Whats the best way for me now?
tobyffm said:
thanks for all your info.
Can you suggest what to do? Acutually I just want to install root to get titanium to work because I have older backups I want to look into to. After that I want to unroot again.
Not sure if i need encryption or if ishould decrypt now
Whats the best way for me now?
Click to expand...
Click to collapse
Then don't bother with decryption.
So you basically just have to place the root of your choice (of the mega ones I linked, because the official ones will remove encryption in your boot image and you will boot loop if you flash the official ones) on an external SD or transfer to /cache with adb after flashing the linked twrp. Then flash root and you're good to go.
I think you can sideload root zip, I haven't tried it. But that's another possibility if you don't have an external SD.
ante0 said:
Then don't bother with decryption.
So you basically just have to place the root of your choice (of the mega ones I linked, because the official ones will remove encryption in your boot image and you will boot loop if you flash the official ones) on an external SD or transfer to /cache with adb after flashing the linked twrp. Then flash root and you're good to go.
I think you can sideload root zip, I haven't tried it. But that's another possibility if you don't have an external SD.
Click to expand...
Click to collapse
Yes, it worked, i flashed supersu and got root acccess now, thx very much.
About unrooting later on, i understand I need to download the full stock rom, create a dload folder and copy update.app into it and reboot phone to download mode. It then will install stock rom and stock recovery, correct?
Will this erase internal storage again same like when unlocking bootloader?
thx!
tobyffm said:
Yes, it worked, i flashed supersu and got root acccess now, thx very much.
About unrooting later on, i understand I need to download the full stock rom, create a dload folder and copy update.app into it and reboot phone to download mode. It then will install stock rom and stock recovery, correct?
Will this erase internal storage again same like when unlocking bootloader?
thx!
Click to expand...
Click to collapse
No need (dload doesn't work anyway, except for AL00C00B115 and L29C636B136). You can uninstall using the SuperSU app or manually by removing /data/SuperSU.apk and restoring stock boot image. Boot image can be extracted from update.app for your model using Huawei Update extractor. Same goes for recovery. If you want to lock bootloader you have to install an update/same build number, you could use Firmware Finder for that or this tool: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
In my experience it will not remove apps, but data seems to go poof (as in app settings and data). Unlocking bootloader again will remove apps though as it does a factory reset.
ante0 said:
/data is encrypted by default using file based encryption. That's why you see those files in /sdcard (/data/media/0/). You can remove encryption by using Wipe - 'Format Data' button.
This will remove everything in /data including your files in /sdcard.
To flash stuff you can use an external SD card or remove encryption or flash this twrp: https://mega.nz/#!xg9hWbpJ!dNOWJVUuD_4JL8N8PiDXYsj3SnvaOfKxBndvWc_4wgo
and adb push (adb push file.zip /cache/file.zip) to /cache and flash from there. /cache is added as storage with that twrp.
If you want to remove encryption, flash official SuperSU 2.82 SR1: https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Or Magisk 13.3: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Both require at least twrp 3.1.0.
If you chose to remove encryption you will also have to flash public and HW zips after Format Data, because files in /data/hw_init are removed which are needed for themes to work and 'System Update' and a few Huawei apps.
Public zip for L09C432B182:
http://update.hicloud.com:8180/TDS/...55/f1/full/public/update_data_full_public.zip
Hw zip for L09C432B182: http://update.hicloud.com:8180/TDS/...04/v84355/f1/full/hw/eu/update_full_hw_eu.zip
Flash public first then hw. Both will give errors but install fine.
If you don't want to remove encryption you won't be able to backup /data.
If so use this SuperSU: https://mega.nz/#!18FW1QTQ!3DCA3KrIUSRqEu4L-expci4HcKtk6F25fE1u6ecJV9Q
Or magisk 13.3: https://mega.nz/#!I4FQzbyA!gBZelHmD3lGGwzGISUXkf7GQTUAq5i785d_qPHQOaVE
Click to expand...
Click to collapse
hi,
thx for your last reply!
I am still on root status. I needed to decrypt now, thus I selected format data.
After that, files and folders are named correctly and I am able to create a backup.
I flashed public ziip, the other one was corrupt, mayve because of failed download, however as I understand it is not the reason why it always goes back to encryption, isn't it?
But: Once I reboot to Android and go back to recovery it is encrypted again?
My current problem is: I need to move a TWRP backup to internal storage and run TWRP restore feature from recovery, but it is encrypted. Once I format data it is decrypted but internal storage empty again. So I reboot to Android (because mounting from within TWRP does not work )and put TWRP backup folder to internsal storage, but then I go back to recovery and see it is encrypted again :S like driving in a circle ...
And I cannot put backup folder to external micro sd as it is too large for my small micro sd I have.
Do I need to flash a decrypted bootimage? If yes, which one?
Can you help me on this maybe?
tobyffm said:
hi,
thx for your last reply!
I am still on root status. I needed to decrypt now, thus I selected format data.
After that, files and folders are named correctly and I am able to create a backup.
I flashed public ziip, the other one was corrupt, mayve because of failed download, however as I understand it is not the reason why it always goes back to encryption, isn't it?
But: Once I reboot to Android and go back to recovery it is encrypted again?
My current problem is: I need to move a TWRP backup to internal storage and run TWRP restore feature from recovery, but it is encrypted. Once I format data it is decrypted but internal storage empty again. So I reboot to Android (because mounting from within TWRP does not work )and put TWRP backup folder to internsal storage, but then I go back to recovery and see it is encrypted again :S like driving in a circle ...
And I cannot put backup folder to external micro sd as it is too large for my small micro sd I have.
Do I need to flash a decrypted bootimage? If yes, which one?
Can you help me on this maybe?
Click to expand...
Click to collapse
'Format Data', flash official Magisk 13.3 or SuperSU 2.82 SR1 (mine from mega doesn't remove encryption), flash public zip, flash HW zip. It should now stay decrypted. You might have to go back to TWRP start screen after Format, then select 'Reboot' - 'Reboot Recovery' if it doesn't want to mount /data after Format.
Rebooting to system after formatting but not flashing magisk or supersu will encrypt again.
I can make a decrypted boot image if it doesn't want to stay decrypted.
ante0 said:
'Format Data', flash official Magisk 13.3 or SuperSU 2.82 SR1 (mine from mega doesn't remove encryption), flash public zip, flash HW zip. It should now stay decrypted. You might have to go back to TWRP start screen after Format, then select 'Reboot' - 'Reboot Recovery' if it doesn't want to mount /data after Format.
Rebooting to system after formatting but not flashing magisk or supersu will encrypt again.
I can make a decrypted boot image if it doesn't want to stay decrypted.
Click to expand...
Click to collapse
ok thx.
I redownloaded HW zip and checked md5 sum with the file from first attempt, same md5. However this is what i did:
Format data, tried to flash Magisk, but did not work, there was an error, this is why I flashed SuperSU 2.82 SR1 which worked with no errors. I flashed public zip right away, after that I flashed HW zip, but again, it did not work there were errors. However, encryption seems to be gone anyway. and yes, it keeps being decrypted.
I managed to get TWRP seeing an old TWRP Backup, which I pushed onto internal storage. I started restore of /data/ of that TWRP backup because I want to get the WhatsApp incl. data from data backup.
I booted up to Android and now I am faced with the next fuc*in problem: lock pattern of Dec 16. I cant remember and after few attemps devices is locked for 10 minutes, then for another 30 minutes ...
After google research it should be able to use Android device manager from a browser and to lock device and set a new pin/password to unlock the device. It is communicating as I can let the phone ring with no problem, but all how_tos show me this screen in android device manager interface
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Of course it is me, who dont get this mask to set a new pin/password ( (
I only can enter an optional phone no and message from browser
Any idea what to do?
Update: I extracted whatsapp from backup with nandroid manager app but it did not restore my data correctly, best way would be to get done the pattern problem when restopring the twrp backup
redaring locking bootloader again:
I went to your link https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
they say to download file for own device here: http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=
I only find:
DUK-L09C432B182
But mine is MHA-L09C432B182, can I go forward with DUK-L09C432B182 anyway? Actually I dont understand what to do, their description is curios.
tobyffm said:
ok thx.
I redownloaded HW zip and checked md5 sum with the file from first attempt, same md5. However this is what i did:
Format data, tried to flash Magisk, but did not work, there was an error, this is why I flashed SuperSU 2.82 SR1 which worked with no errors. I flashed public zip right away, after that I flashed HW zip, but again, it did not work there were errors. However, encryption seems to be gone anyway. and yes, it keeps being decrypted.
I managed to get TWRP seeing an old TWRP Backup, which I pushed onto internal storage. I started restore of /data/ of that TWRP backup because I want to get the WhatsApp incl. data from data backup.
I booted up to Android and now I am faced with the next fuc*in problem: lock pattern of Dec 16. I cant remember and after few attemps devices is locked for 10 minutes, then for another 30 minutes ...
After google research it should be able to use Android device manager from a browser and to lock device and set a new pin/password to unlock the device. It is communicating as I can let the phone ring with no problem, but all how_tos show me this screen in android device manager interface
Of course it is me, who dont get this mask to set a new pin/password ( (
I only can enter an optional phone no and message from browser
Any idea what to do?
Update: I extracted whatsapp from backup with nandroid manager app but it did not restore my data correctly, best way would be to get done the pattern problem when restopring the twrp backup
redaring locking bootloader again:
I went to your link https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
they say to download file for own device here: http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=
I only find:
DUK-L09C432B182
But mine is MHA-L09C432B182, can I go forward with DUK-L09C432B182 anyway? Actually I dont understand what to do, their description is curios.
Click to expand...
Click to collapse
L09C432B156 firmware: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1366/g104/v84355/f1/full/update.zip
L09C432B182 public data zip:
http://update.hicloud.com:8180/TDS/...55/f1/full/public/update_data_full_public.zip
L09C432B182 hw data zip:
http://update.hicloud.com:8180/TDS/...04/v84355/f1/full/hw/eu/update_full_hw_eu.zip
You might as well update to B190 while you're at it..
L09C432B190: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1366/g104/v89786/f1/full/update.zip
L09C432B190 public data zip:
http://update.hicloud.com:8180/TDS/...86/f1/full/public/update_data_full_public.zip
L09C432B190 hw data zip: http://update.hicloud.com:8180/TDS/...l/MHA-L09_hw_eu/update_full_MHA-L09_hw_eu.zip
Rename public data zip to update_data_public.zip.
Rename hw data zip to update_all_hw.zip
ok, to summarize:
1) I download these 3 files:
full update.zip:
L09C432B190: http://update.hicloud.com:8180/TDS/d...ull/update.zip
L09C432B190 public data zip:
http://update.hiclod.com:8180/TDS/d...ull_public.zip
L09C432B190 hw data zip:
http://update.hicloud.com:8180/TDS/d...-L09_hw_eu.zip
2) I extract recovery img file from update zip
3) I uninstall root from within super su app.
4) I rename zip files and flash public zip as well as hw zip from within twrp recovery
5) i put extraced recovery img to device by using "fastboot flash recovery "
Will it work like this? Or do I need to flash public and hw first and after that uninstall root from supersu?
and then in the end "fastboot oem lock" ? to get the bootloader locked and to switch off the boot message "your device cant be trusted" ?
and: I couldnt flash hw zip before as it ended up with errrors, is this why I dont have Search for updates in EMUI 5.0 anymore?
tobyffm said:
ok, to summarize:
1) I download these 3 files:
full update.zip:
L09C432B190: http://update.hicloud.com:8180/TDS/d...ull/update.zip
L09C432B190 public data zip:
http://update.hiclod.com:8180/TDS/d...ull_public.zip
L09C432B190 hw data zip:
http://update.hicloud.com:8180/TDS/d...-L09_hw_eu.zip
2) I extract recovery img file from update zip
3) I uninstall root from within super su app.
4) I rename zip files and flash public zip as well as hw zip from within twrp recovery
5) i put extraced recovery img to device by using "fastboot flash recovery "
Will it work like this? Or do I need to flash public and hw first and after that uninstall root from supersu?
and then in the end "fastboot oem lock" ? to get the bootloader locked and to switch off the boot message "your device cant be trusted" ?
and: I couldnt flash hw zip before as it ended up with errrors, is this why I dont have Search for updates in EMUI 5.0 anymore?
Click to expand...
Click to collapse
No. Follow the guide you linked, that's where you use those files.
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
You could relock but it will say Bootloader Relocked instead of Bootloader Lock.
And if you don't plan on updating to B190 using the guide I suggest you download public and HW Data for B182 and flash those in twrp.
Can cause problems otherwise.
Flash public first. They will give errors because you're not supposed to flash them in twrp, they're official Huawei zips that are flashed using stock recovery.
ante0 said:
No. Follow the guide you linked, that's where you use those files.
https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
You could relock but it will say Bootloader Relocked instead of Bootloader Lock.
And if you don't plan on updating to B190 using the guide I suggest you download public and HW Data for B182 and flash those in twrp.
Can cause problems otherwise.
Flash public first. They will give errors because you're not supposed to flash them in twrp, they're official Huawei zips that are flashed using stock recovery.
Click to expand...
Click to collapse
OK and why i currently dont see menue point "search for updates" in EMUI 5.0 ? Maybe i will stay rooted as I see that xposed has now been released.
But I want to receive official OTAs anyway, but currently the full menue point for searching for updates is gone. Any idea?
tobyffm said:
OK and why i currently dont see menue point "search for updates" in EMUI 5.0 ? Maybe i will stay rooted as I see that xposed has now been released.
But I want to receive official OTAs anyway, but currently the full menue point for searching for updates is gone. Any idea?
Click to expand...
Click to collapse
Did you flash back public and HW Data for B182?
ante0 said:
Did you flash back public and HW Data for B182?
Click to expand...
Click to collapse
I was not sure which was the last I flashed during last days, B182 or B190.
However, just redownload B182 files and flashed, first public, then hw zip.
Rebooted device, "search for updates" is available again, thank you very much
But it says B182 is latest update, so OTA not available for me so far yet. How can I manually flash to latest version B190 without loosing 'Search for Update' section?
tobyffm said:
I was not sure which was the last I flashed during last days, B182 or B190.
However, just redownload B182 files and flashed, first public, then hw zip.
Rebooted device, "search for updates" is available again, thank you very much
But it says B182 is latest update, so OTA not available for me so far yet. How can I manually flash to latest version B190 without loosing 'Search for Update' section?
Click to expand...
Click to collapse
You can with that guide i linked a couple of posts back. You can't flash update.zip in twrp, you have to use that guide to flash it. It's pretty straightforward. Download HWOTA BASE, HWOTA WINDOWS and HWOTA MHA (Mate 9), extract all to the same folder (C:\hwota is a good location). Download the files for B190 i linked a couple of posts back. Rename public data zip to update_data_public.zip.
Rename hw data zip to update_all_hw.zip, place them and update.zip in the update folder, run bat (if windows) or sh (Linux) then do what the prompts say. When it asks pick same brand update, then script update folder. It will transfer files for you. Bootloader will be locked when you're done.
ante0 said:
You can with that guide i linked a couple of posts back. You can't flash update.zip in twrp, you have to use that guide to flash it. It's pretty straightforward. Download HWOTA BASE, HWOTA WINDOWS and HWOTA MHA (Mate 9), extract all to the same folder (C:\hwota is a good location). Download the files for B190 i linked a couple of posts back. Rename public data zip to update_data_public.zip.
Rename hw data zip to update_all_hw.zip, place them and update.zip in the update folder, run bat (if windows) or sh (Linux) then do what the prompts say. When it asks pick same brand update, then script update folder. It will transfer files for you. Bootloader will be locked when you're done.
Click to expand...
Click to collapse
Did like described, when it comes to "update should install automatically" it reboots into erecovery, but Software install failed!
The update package does not exists please download the package again
But all 3 files are within the script folder and named correctly i think, pls see my attached screenshot
tobyffm said:
Did like described, when it comes to "update should install automatically" it reboots into erecovery, but Software install failed!
The update package does not exists please download the package again
But all 3 files are within the script folder and named correctly i think, pls see my attached screenshot
Click to expand...
Click to collapse
Are they in the update folder? I think I see the update.bat file there.
Put them in the update folder (for example c:\hwota\update\)
ante0 said:
Are they in the update folder? I think I see the update.bat file there.
Put them in the update folder (for example c:\hwota\update\)
Click to expand...
Click to collapse
yes, that was my fault.
Put to update folder and run again, update was running and finished with 100%. phone rebooted loaded very long. Now android is broken. I see my background image, but cannot do anything it is like hanging hanging hanging, everyhting very slow, like it is loading much of information. rebooted phone and waited some more time. seems now it is working and I am on B190. Now, i have to unlock bootloader again and install supersu again =)
thx for your help so far.
btw: u dont have any solution for my previous posted problem with my twrp backup, dont you? restoring twrp backup ends up in lock screen with pattern which I cant remember. Android Device Manager from PC browser can communictae with the phone but it does not offer me to set a new pin. Do you have any other method in mind how I can go on?

OTA Update without loosing root and wiping data possible?

I rooted my HTC U11+ using Magisk without having TWRP installed. I can't find the link anymore, but I think it was through fastboot and if I remember correctly, I had to format /data after installing Magisk due to the device encryption. Everything is working fine.
Today I got a notification that a new firmware with the version number 1.24.401.2 is available (current version is 1.10.401.23). I'm pretty sure if I install it, i I will loose root and I would have to install Magisk again to gain root back which would require to format /data. I would like to prevent that since I've spend ages to configure and adjusting everything to my needs and I'm not keen to do that again.
Is there a way of installing the OTA update without loosing root and having to wipe /data?
midiwidi said:
I rooted my HTC U11+ using Magisk without having TWRP installed. I can't find the link anymore, but I think it was through fastboot and if I remember correctly, I had to format /data after installing Magisk due to the device encryption. Everything is working fine.
Today I got a notification that a new firmware with the version number 1.24.401.2 is available (current version is 1.10.401.23). I'm pretty sure if I install it, i I will loose root and I would have to install Magisk again to gain root back which would require to format /data. I would like to prevent that since I've spend ages to configure and adjusting everything to my needs and I'm not keen to do that again.
Is there a way of installing the OTA update without loosing root and having to wipe /data?
Click to expand...
Click to collapse
Would the following be helpful?
Haven't tried myself yet.
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
Thank you for the link DanteGR. It looks promising.
I'll have to find out if my HTC U11+ is supported by FlashFire. It most likely doesn't have two partitions (A/B).
So if somebody knows if the U11+ is working with FlashFire, please let me know!
Is there a way of backing everything up in case something goes wrong with with the OTA update using FlashFire? I'm not keen on loosing all the adjustments and settings I made in the last couple of weeks (I even modified files in /data/data to fix App issues). As far as i know Nandroid backups are not possible because the currently available TWRP recovery for the U11+ doesn't support data decryption. I have backups to Google Drive enabled (with all options including App data), but I don't know if that is enough to bring the system back into the current state afterwards.
midiwidi said:
Thank you for the link DanteGR. It looks promising.
I'll have to find out if my HTC U11+ is supported by FlashFire. It most likely doesn't have two partitions (A/B).
So if somebody knows if the U11+ is working with FlashFire, please let me know!
Is there a way of backing everything up in case something goes wrong with with the OTA update using FlashFire? I'm not keen on loosing all the adjustments and settings I made in the last couple of weeks (I even modified files in /data/data to fix App issues). As far as i know Nandroid backups are not possible because the currently available TWRP recovery for the U11+ doesn't support data decryption. I have backups to Google Drive enabled (with all options including App data), but I don't know if that is enough to bring the system back into the current state afterwards.
Click to expand...
Click to collapse
No problem.
AFAIK unfortunately there isn't a way for a full backup without a completely functioning TWRP.
If rooted, Titanium would be your best bet but not for everything obviously.
midiwidi said:
I rooted my HTC U11+ using Magisk without having TWRP installed. I can't find the link anymore, but I think it was through fastboot and if I remember correctly, I had to format /data after installing Magisk due to the device encryption. Everything is working fine.
Today I got a notification that a new firmware with the version number 1.24.401.2 is available (current version is 1.10.401.23). I'm pretty sure if I install it, i I will loose root and I would have to install Magisk again to gain root back which would require to format /data. I would like to prevent that since I've spend ages to configure and adjusting everything to my needs and I'm not keen to do that again.
Is there a way of installing the OTA update without loosing root and having to wipe /data?
Click to expand...
Click to collapse
As you, I have root but no TWRP installed. I did the OTA update and I didn't lost my data. I lost root during the process but it was very easy to install it back without loosing or wipe data.
If you have installed Magisk via patched boot.img, here is what I have done :
-Go in Magisk, choose uninstall and then "restore image"
-Then, go check for update on your phone and start it.
-At the same time, download stock RUU rom (the same as the OTA, here for European version : https://forum.xda-developers.com/htc-u11/development/htc-u11-stock-rom-ruu-t3741849) and extract boot.img from it with RUUdecrypttool (https://forum.xda-developers.com/chef-central/android/tool-universal-htc-ruu-rom-decryption-t3382928). It can be long.
-When update is complete and you have extracted boot.img, put it in your phone and patch it with magisk : install, patch boot image. Then you will have a "patched_boot.img" in your magiskmanager folder. Copy this file on your PC.
-Go to download mode on your phone and flash patched_boot.img via Flashtool.
Root is back, no data lost :good:
Kidy973 said:
As you, I have root but no TWRP installed. I did the OTA update and I didn't lost my data. I lost root during the process but it was very easy to install it back without loosing or wipe data.
If you have installed Magisk via patched boot.img, here is what I have done :
-Go in Magisk, choose uninstall and then "restore image"
-Then, go check for update on your phone and start it.
-At the same time, download stock RUU rom (the same as the OTA, here for European version : https://forum.xda-developers.com/htc-u11/development/htc-u11-stock-rom-ruu-t3741849) and extract boot.img from it with RUUdecrypttool (https://forum.xda-developers.com/chef-central/android/tool-universal-htc-ruu-rom-decryption-t3382928). It can be long.
-When update is complete and you have extracted boot.img, put it in your phone and patch it with magisk : install, patch boot image. Then you will have a "patched_boot.img" in your magiskmanager folder. Copy this file on your PC.
-Go to download mode on your phone and flash patched_boot.img via Flashtool.
Root is back, no data lost :good:
Click to expand...
Click to collapse
Just a heads up.
I think for OTAs only (NOT RUUs) you don't even have to use the decrypt tool.
The zip is already decrypted so just extract the boot.img.
EDIT: Not 100% sure though will try it out this evening.
DanteGR said:
Just a heads up.
I think for OTAs only (NOT RUUs) you don't even have to use the decrypt tool.
The zip is already decrypted so just extract the boot.img.
EDIT: Not 100% sure though will try it out this evening.
Click to expand...
Click to collapse
That is correct.
I have done it many times.
m3johan said:
That is correct.
I have done it many times.
Click to expand...
Click to collapse
Oh well.
Last night I downloaded a random OTA for the HK version and the firmware.zip inside it could not be opened I guess due to encryption.
Are you sure about that?
DanteGR said:
Oh well.
Last night I downloaded a random OTA for the HK version and the firmware.zip inside it could not be opened I guess due to encryption.
Are you sure about that?
Click to expand...
Click to collapse
I can not be 100% sure, but all I have unpacked including this 1.24.401.2 ota were no problem.
Can you give me the link to the HK-ota?
m3johan said:
I can not be 100% sure, but all I have unpacked including this 1.24.401.2 ota were no problem.
Can you give me the link to the HK-ota?
Click to expand...
Click to collapse
This is the one I tried to extract without success.
Just to make it clear. I had no problem extracting the actual OTA. The problem was trying to extract the firmware.zip inside it.
Thank you for your input.
https://www.androidfilehost.com/?fid=962187416754455026
DanteGR said:
This is the one I tried to extract without success.
Just to make it clear. I had no problem extracting the actual OTA. The problem was trying to extract the firmware.zip inside it.
Thank you for your input.
https://www.androidfilehost.com/?fid=962187416754455026
Click to expand...
Click to collapse
You are right. I could not unpack firmware from that one either.
Deleted
m3johan said:
You are right. I could not unpack firmware from that one either.
Click to expand...
Click to collapse
The decrypt tool doesn't seem too bad after all though.
I'll have to try it shortly.
For those who are using Taiwan model, what is your software number?
Mine is 1.23.709.9
RUU decrypt tool
DanteGR said:
The decrypt tool doesn't seem too bad after all though.
I'll have to try it shortly.
Click to expand...
Click to collapse
RUU_decrypt_tool works like a charm
the command on the command line is (in windows) RUU_decrypt_tool -f RUU file name (use TAB for name completion or rename to RUU.zip) (for firmware files) which gets you (see thumbnail)
The tool automatically has a output as "OUT" in the folder where it resides; I've put my RUU file in the ADB folder together wit the RUU_decrypt_tool
You'll find the RUU_decrypt_tool here
btw: I am 70 years young, so if I can do it most people can as well.....
If none of the required arguments are supplied a simple Yes/No interface will be presented.
Required arguments (and/or):
-s, --system extract the system.img and boot.img (for ROM)
-f, --firmware extract the firmware files
-z, --sdruuzip copy and rename rom.zip for SD-Card flashing
Note: this will create a duplicate if the input is already a rom.zip
Keyfile Updater arguments:
-o, --offline disable down/upload of keyfiles
--no-upload do not upload if a new keyfile is generated
--sync-keyfiles sync entire keyfile folder (download & upload)
when used without a RUU the tool will only synchronize the
keyfiles, otherwise it will download new keyfiles before decrypting
and upload only if a new keyfile is generated
Click to expand...
Click to collapse
When I used to have htc 10 s-on I could update the fw using a zip file(perhaps firmware. Zip) inside the OTA file for my cid and flash it in RUU mode, of course I had to use a custom rom based on the same fw to complete it
Finally, after a couple of month and being annoyed of the update message popping up all the time, I got some time to proceed with the update.
I found that what I've said in my first post isn't true. I had a non-official TWRP (without decryption support) installed and now remember that I have installed Magisk through that.
I've started the update procedure with clicking "uninstall" and "restore image" in the Magisk app. After downloading the OTA, I clicked on install now. My phone rebooted into recovery (TWRP) and prompted to enter my unlocking pattern. I entered it, but TWRP said something like can't mount, wrong password.
I thought it's because TWRP doesn't support decryption yet and I need to go back to the stock recovery to be able to apply the OTA. I extracted the recovery_signed.img from here (from the same software version I'm currently running 1.10.401.23) and flashed it using fastboot. If I boot into recovery now, I see it's the stock one, but it shows a red exclamation mark in a red triangle. I can press power button + volume up and get into the normal recovery menu. I've tried to wipe the cache there, but it didn't made a difference. I still get that red exclamation mark. If I download the OTA and click on install now, my phone restarts and shows the normal picture of applying the update until about 24% of progress and then it shows the red exclamation mark again. If I press power + volume up now, nothing happens.
If I manually boot into recovery and use power + volume up to get into the recovery menu, there are two options to apply an update. One using the sdcard and one using ADB. I have the hope that the red exclamation mark is gone once I installed the update manually.
The sdcard option doesn't work. The recovery shows the message can't mount /sdcard. The ADB sideload option causes problems too.
If I use a older version of ADB I get the error "cannot read OTA.zip" in my command window on the PC. I've tried it with a small text file and that worked. I read that it has something to do with the address space which is too small and that I should use the newest version from googles platform tools. I installed version 27.0.1 and used the contained ADB to do the sideload. This time I got an error message like "adb server version (31) doesn't match this client (36)", but it didn't say that it can't read the file.
I'm kind of stuck now. Has somebody a suggestion how to proceed, to get rid of the red exclamation mark so that I can normally apply the OTA update and gain root again afterwards by flashing a Magisk patched boot.img through fastboot?
midiwidi said:
...shows the normal picture of applying the update until about 24% of progress and then it shows the red exclamation mark again....
Click to expand...
Click to collapse
You have a modified /system partition. You will need to restore stock system partition of the version you are running to get past this.
You have a modified /system partition. You will need to restore stock system partition of the version you are running to get past this.
Click to expand...
Click to collapse
Thank you very much for this hint. I will do a
fastboot flash system system.img
tonight and let you know how it went.
I did flash the original system.img. Here the output of the command window
C:\Users\midiwidi\Downloads\HTC_U11+\Original_HTC_Firmware_Europe\OUT_2Q4D_1.10.401.23\system>fastboot.exe flash system system.img
sending 'system' (16384 KB)...
OKAY [ 1.651s]
writing 'system'...
(bootloader) HOSD CL#991677
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 3.461s]
finished. total time: 5.111s
Unfortunately that didn't change anything. I still get the red exclamation mark if I boot into recovery
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
.
Is there a log file or something similar to find out what the recovery is complaining about? This is the output after bypassing the red exclamation mark with power + volume up
.
Any other ideas how to proceed?

Categories

Resources