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.
Help for a newbie.
I followed this procedure:
1 - Copied file to sd card and renamed to update.zip (in a windows computer)
2 - turned xoom on and wento to rom manager
3 - wiped user and dalvik cache
4 - Tried to load file from zip, but it was not possible to find the update .zip file.
I get the following message:
E: Can't open /sdcard/update.zip
(bad)
Tried also without renaming and got:
E: Can't open /sdcard/update_US-Xoom-Wifi-3.2_HTJ85B-from HMJ37_stachre-solarnz-boot-img_v05.zip
After many trials rebooted.
System info showed the same 3.1 and Tiamamat 1.4.4
Opened rom manager again.
seleced install rom from sdcard
System backed up info and rebooted.
Had to reload all apps from store.
System info shows I am running 3.1 and Tiamat 1.4.4.
Also I keep receiving a message that there is a system update available.
I can't understand what I did wrong.
I g
Can anyone help?
Thank you
rogerodd said:
Help for a newbie.
I followed this procedure:
1 - Copied file to sd card and renamed to update.zip (in a windows computer)
2 - turned xoom on and wento to rom manager
3 - wiped user and dalvik cache
4 - Tried to load file from zip, but it was not possible to find the update .zip file.
I get the following message:
E: Can't open /sdcard/update.zip
(bad)
Tried also without renaming and got:
E: Can't open /sdcard/update_US-Xoom-Wifi-3.2_HTJ85B-from HMJ37_stachre-solarnz-boot-img_v05.zip
After many trials rebooted.
System info showed the same 3.1 and Tiamamat 1.4.4
Opened rom manager again.
seleced install rom from sdcard
System backed up info and rebooted.
Had to reload all apps from store.
System info shows I am running 3.1 and Tiamat 1.4.4.
Also I keep receiving a message that there is a system update available.
I can't understand what I did wrong.
I g
Can anyone help?
Thank you
Click to expand...
Click to collapse
You may have the wrong version of CWM recovery installed. You need Tiamat v3.2.0.0 R4c. If you are trying to flash thru Rom manager it may have had you update to v4.0.0.4 which is not compatible with the external sdcard. If this is the case, re-install the correct recovery version, and then redo your backup so that it is on the external sdcard where it can be safe if you need to wipe/factory reset. You can use Rom manger just to reboot into recovery, or df Quick Boot from the market and use that instead.
Good luck!
okantomi said:
You may have the wrong version of CWM recovery installed. You need Tiamat v3.2.0.0 R4c. If you are trying to flash thru Rom manager it may have had you update to v4.0.0.4 which is not compatible with the external sdcard. If this is the case, re-install the correct recovery version, and then redo your backup so that it is on the external sdcard where it can be safe if you need to wipe/factory reset. You can use Rom manger just to reboot into recovery, or df Quick Boot from the market and use that instead.
Good luck!
Click to expand...
Click to collapse
Rom manager says it is 4.0.0.4 but when in recovery is say CWM recovery-Tiamat-R4c-100611-1150-cwm or Tiamat v3.2.0.0 R4c ( I don't remember exectly) and the error is the same.
Also, I tried reflash recovery-Tiamat-R4c-100611-1150-cwm.zip from the SD card and get an error.
I really don't have a clue of what to do.
Any help would be welcome.
rogerodd said:
Rom manager says it is 4.0.0.4 but when in recovery is say CWM recovery-Tiamat-R4c-100611-1150-cwm or Tiamat v3.2.0.0 R4c ( I don't remember exectly) and the error is the same.
Also, I tried reflash recovery-Tiamat-R4c-100611-1150-cwm.zip from the SD card and get an error.
I really don't have a clue of what to do.
Any help would be welcome.
Click to expand...
Click to collapse
The problem is that you can't flash anything from the external sdcard with v4.0.0.4. In rom manager, see if you can find"all clockwork recoveries" and find 3.2.0.0. If not, find 3.0.2.8 or 3.0.2.5 and flash one of them, preferably the latest of those I have listed. I think those will at least recognize your sdcard. If you can't do that, you will need to reflash the correct recovery the same way you did when you rooted. Remember, never flash a zip file through adb.
Good luck!
I tried to flash recovery-Tiamat-R4c-100611-1150-cwm.img via adb.
I could flash boot sector. Then I reboot into recovery and try to apply zip from card with file update_US-Xoom-WiFi-3.2-HTJ85B-from-HMJ37_stachre_solarnz-boot-img_v05.zip, but there is a NO at the end of the name of the file and I can't go on.
Trying to rename as update.zip and run apply zip from card results in same error:
E: Can't open /sdcard/update.zip
(bad)
what should I do?
Thank you
possible bad download... download again... also, don't think this would be an update... leave it as originally named, just choose the option to choose which zip file to install from the sd card
rogerodd said:
I tried to flash recovery-Tiamat-R4c-100611-1150-cwm.img via adb.
I could flash boot sector. Then I reboot into recovery and try to apply zip from card with file update_US-Xoom-WiFi-3.2-HTJ85B-from-HMJ37_stachre_solarnz-boot-img_v05.zip, but there is a NO at the end of the name of the file and I can't go on.
Trying to rename as update.zip and run apply zip from card results in same error:
E: Can't open /sdcard/update.zip
(bad)
what should I do?
Thank you
Click to expand...
Click to collapse
It sounds like you are flashing recovery ok, but you keep overwriting it with the stock recovery.
Here is some important information that should help a lot with making your new recovery "stick"and this was taken from the Idiot's guide to flashing...in the Development section, and originally written by publicanimal:
4. Install recovery image (CWM)
Download the recovery image file and save it to your computer
Boot into flash mode with 'adb reboot bootloader'
Install your downloaded recovery image
C:\Documents and Settings\Anders> fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
Restart the device with 'fastboot reboot'. Timing is essential here, so be alert when the device restarts, or you will have to redo this section
Enter CWM with the following procedure
Once the Motorola logotype is shown, start counting to 3. At 3, press the Volume Down button. This should result in the text 'Android Recovery' in the top left corner. If it does not work, experiment with the timing ...
When 'Android Recovery' is shown press the Volume Up button. This should invoke the CWM recovery menu. If that works, then congratulations for reaching this far .
Here is a potential pitfall. If you are unable to enter CWM *before* the device boots into Honeycomb, then the newly installed recovery image will be overwritten by the system default recovery. If that happens, or if you see "starting fastboot protocol " your timing wasn't right and you need to reflash the recovery image and try it again.
See original post,below for more information.
http://forum.xda-developers.com/showthread.php?t=1130996
i seem to have fubar'ed my nexus s (uk version) i updated to ics, didnt like it so tried to restore to a backup i made earlier today...
at the moment when i turn on my phone it shows
fastboot mode- No Boot or Recovery img
lock state - unlocked
I can enter recovery. but cannot restore.
tried wiping cache,dalvik etc.
When hitting restore it returns with:
... system.img not found. skipping restore of /system/
also does the same with
data.img
cache.img
sd-ext.img
i have no idea what to do... if you could help it would be greatly appreciated.
Try flashing a rom. U can mount SD card within recovery.
Sent from my Nexus S 4G using xda premium
yeah tried flashing ...
gets stuck on google screen
Do you have a One Click return to stock available for your model? It wouldn't hurt to start fresh. I did that on my NS4G last week. Does your PC recognize the phone?
Sent from my SPH-D710 using Tapatalk
looking into the unbrickable mod atm... my phone seems to have no .img files.
tried restoring to stock and still the same issue... it says it cant find .img so skips them then when i try to re boot it sticks on the google screen
After trying to apply from zip (cm7, that i have used numerous times before)
i get this ---
Installing update...
assert failed: getprop("ro.product.device") =="crespo" ll getprop("ro.build.Product") == "crespo" ll getprop("ro.product.board") == "crespo"
E:Error in /sdcard/update-cm-7.0.3-NS-signed.zip
(Status 7)
Installation aborted.
i havent the faintest idea what to do...
Tried re-flashing CWM recovery?
yup tried re flash,
i think i need to replace the .img files... i just dont know how
it says that
system.img not found
data.img not found
cache.img not found
sd-ext.img not found.
it skips the restore of these say restore complete. yet there is obviously nothing to restore.
there must be a way of fixing this???
Do you have the latest version of CWM flashed? (5.0.2.0)
yeah re installed/reflashed (5.0.2.0)
it seems to be working
*~~~~~~*
Facepalm
*~~~~~~*
Such a noob
I have had a similar problem before, and even advised on that exact thing.
lesson learned.
KEEP RECOVERY.IMG UP TO DATE
Thank you for pointing out the obvious.
I'm such a ****
No problem flex59, best way to learn is the long and hard way . I had a similar status 7 problem on my move up to ICS. Figured the latest recovery will save me wasted hours down the track eventually, and hopefully someone elses.
To downgrade from ICS, you need to flash the full GB 2.3.6 ROM first...
I downgraded from OTA ICS 4.0.3 due to battery, Wifi & lag issues as well. A NANDroid backup does NOT contain the bootloader and radio AFAIK. Here's what I did.
Find the appropriate FULL ROM here and download and copy to your SD card.
Download this flashable Superuser here and copy to your SD card.
Make sure you are familiar with and set up for fastboot and have the latest CWM recovery img file. You will have to reinstall CWM. These instructions are assuming that CWM recovery is already installed on your device.
1. Make sure the full ROM and SU zip are on the root your SD card.
2. I did a full wipe of data, cache, dalvik.
3. Go into CWM recovery and flash the full ROM. Now flash the SU zip.
4. At this point, the full ROM flashed GB2.3.6, stock recovery, bootloader and radio back. But you should be rooted due to step 3.
5. Boot into Android. I installed ES File Explorer from the market. In ES File Explorer settings, select both root settings “Root Explorer” and “Mount File System” to navigate and modify root files. Allow permissions in SuperUser.
6. Navigate to /system/etc and rename (tap&hold on file) install-recovery.sh to install-recovery.sh.bak (this file reinstalls the stock recovery at every boot)
7. Using fastboot on your computer, flash CWM recovery again.
8. NOW using CWM, restore your GB 2.3.6 NANDroid backup.
Like nothing ever changed.
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
Hello,
I am trying to update my H60-L12 from 6.1.1 to 6.1.16 (and then beyond) using OTA.
I have my phone rooted and with custom recovery. I know I have to unroot and restore stock recovery to get the OTA updates. Yesterday I learnt also that to get 6.1.16 I have to use TAPVPN to connect to the internet via Singapore (thanks to @bcostea for the hint).
Now I find that my phone downloads the update and when it tries to install there is an error in the process at the 6%.
I learnt that the update process logs its progress in the file /splash2/recovery_log
There I find this:
Code:
UI percent:5%.
file "/system/framework/com.google.widevine.software.drm.jar" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/framework/com.google.widevine.software.drm.jar", "6189c99c76c84310f35b967e768440088e140f78", "7b4afc644b4d388fe159120f434f769a635a8c5e")
str1:/system/framework/com.google.widevine.software.drm.jar, str2:6189c99c76c84310f35b967e768440088e140f78
[2016-02-11 16:04:21 903] int try_update_binary(const char*, ZipArchive*, int*),line=231: err_no = 34
[2016-02-11 16:04:21 903] int try_update_binary(const char*, ZipArchive*, int*),line=233: push binary errno 34
[2016-02-11 16:04:21 903] int try_update_binary(const char*, ZipArchive*, int*),line=238: assert info: assert_filename:/system/framework/com.google.widevine.software.drm.jar
E:assert failed: apply_patch_check(E:
It seems that my com.google.widevine.software.drm.jar is not the one expected by the process.
That makes some sense, as after I installed the full stock rom, I was not able to apply the pa_gapps (some error related to not being possible to install them in a system that did not had a previous version installed to avoid conflicts) (more details on this are available if anybody has a hint or is willing to trobuleshoot it).
Thing is that I applied open_gapps, which are working just fine, but seem to have a different com.google.widevine.software.drm.jar version.
Till 6.1.1, I was able to replace the com.google.widevine.software.drm.jar file in my phone with one from the system.img of the Stock ROM, and then the update was working.
With 6.1.1 I have not been able to find the right file (one with a SHA-1 hash of 7b4afc644b4d388fe159120f434f769a635a8c5e, seems to be necessary).
I have 3 files with hashes:
6189c99c76c84310f35b967e768440088e140f78
654d36de1c8e9e84979a67e897f36dc17a6f7565
bb6bfd30b3d6d03ecf9531e37bcdb0b5a8123e11
They come from stock, from pa_gapps and from open_gapps, but none of them work.
I put them in the \system\framework folder, but the update still fails with the same error.
Can anyone give me a hint? I am going to try by deleting the file, as I have seen that in the log there is one that is not found and the process does not complain that much.
Maybe someone has the right file in this phone and can send it to me. That would be great!!
Thanks in advance!
Well, it seems I managed to make it work.
Instructions below are without warranty. You know that. It's your phone, if you break it, it's your fault. Not mine. You acknowledge that.
Here is how I did it (if you don't know how to execute any of the steps, just google. Instructions have been provided a million times on how to boot in recovery, how to flash an image or how to do a full backup from custom recovery...):
1. I downloaded the full image of the release I had in my phone (I.e. 6.1.1)
2. Using Huawey Upgrade Extractor I extracted system.img and recovery.img
3. I restarted into custom recovery (TWRP) and took a full backup of my phone to the SD. I then removed the SD.
4. I restarted in fastboot mode and using fastboot.exe I flashed recovery.img and system.img (in my case that did not remove anything from my phone, but as I said before, I took a backup beforehand, just in case).
5. I rebooted the phone. Everything was working just fine.
6. I used TAPVPN app to connect through Singapore, so I could get the update to 6.1.16.
7. The update downloaded and installed as expected.
8. Then I used again TAPVPN to get 6.2.1.
9. Same result: download and installation as expected.
10. Then I rooted again and installed custom recovery by using Honor Multi-Tool.
I hope this helps.