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
Related
idk if anyone would want this but here is a clean jellybean nandroid backup of a cricket wireless Htc One SV with newest update already applied. http://www.filefactory.com/file/5u395y1qavzr/Clean_JB_Crkt_2.04.1050.3.rar
Ok, i've downloaded this backup and made a zip file for flashing in recovery from it.
Credits:
- ironhide602 for the backup
- dsixda for his kitchen
Download:
JB_Crkt 2.04.1050.3_stock_odexed.zip
Notice:
As i don't have a cricket phone i could not test but one tester reported it's working.
Anyway, flash this on your own risk. Don't do this, if you are not experienced enough!
This files are for flashing in recovery.
I will not work on bugs, if you find some (as i could not test myself)!
Kernel source code can be found at htcdev.com.
How to install:
First of all: make a nand backup in recovery, so you can easily go back if you don't like it!!!
Download the zip file that match to your device and copy to sd card.
Wipe/format data/system/cache/dalvik cache, factory reset.
Flash the zip through recovery.
Htcdev.com unlocked users who are not S-Off have to extract boot.img from the zip file and flash it afterwards over fastboot with the command:
Code:
fastboot flash boot boot.img
Then reboot.
- There is no superuser/su inside, if you wanna root, flash superuser from here.
old.splatterhand said:
Ok, i've downloaded this backup and made a zip file for flashing in recovery from it.
Credits:
- ironhide602 for the backup
- dsixda for his kitchen
Download:
JB_Crkt 2.04.1050.3_stock_odexed.zip
Notice:
As i don't have a cricket phone i could not test but one tester reported it's working.
Anyway, flash this on your own risk. Don't do this, if you are not experienced enough!
This files are for flashing in recovery.
I will not work on bugs, if you find some (as i could not test myself)!
Kernel source code can be found at htcdev.com.
How to install:
First of all: make a nand backup in recovery, so you can easily go back if you don't like it!!!
Download the zip file that match to your device and copy to sd card.
Wipe/format data/system/cache/dalvik cache, factory reset.
Flash the zip through recovery.
Htcdev.com unlocked users who are not S-Off have to extract boot.img from the zip file and flash it afterwards over fastboot with the command:
Code:
fastboot flash boot boot.img
Then reboot.
- There is no superuser/su inside, if you wanna root, flash superuser from here.
Click to expand...
Click to collapse
Hellow , Please can u Upload this file in other server ill try multiple times
& stuck in the final byte .
Regards
I have no fast internet and i'm trying since days to upload a big file, so not before the other one is finished.
old.splatterhand said:
I have no fast internet and i'm trying since days to upload a big file, so not before the other one is finished.
Click to expand...
Click to collapse
sorry sorry ... not server ,,its my own pc,, ill try in other & everythin ok
thanks
Regards
Hi,
I'm about to install CM11 (cm-11-20141008-SNAPSHOT-M11-hammerhead.zip) on my Nexus 5, but wanted to be sure I'm not about do something obviously stupid. I tried using the CM Installer, but it said 'firmware not supported'.
I have
- Minimal experience.
- LG Nexus 5, hammerhead
- unlocked and rooted. (it did a factory reset on unlocking)
- Fresh Android 5.1.1 with bootloader version HHZ12h.
- TWRP 2.8.7.1 (took a backup and copied the whole TWRP folder to my laptop), flashed manually using fastboot flash recovery twrp.img.
- Latest TWRP manager installed from Play Store.
- standalone adb and fastboot installed on my Windows 7 laptop. No SDK. 'adb devices' lists the phone when connected.
- cm-11-20141008-SNAPSHOT-M11-hammerhead.zip downloaded to my phone under /sdcard/.
- cm-11-20141008-SNAPSHOT-M11-hammerhead.zip is also present in same folder as adb.exe and fastboot.exe.
Questions are:
- Hope this build of CM is compatible with my Nexus 5 & the bootloader version and whatever else there might be compatibility issues.
- How should I do this: According to "official CM installation on Nexus 5 guide" on wiki.cyanogenmod.org it seems like I'm supposed to push the zip file to /sdcard/0, but /sdcard seems to be a link to /sdcard/emulated/legacy, which contains no folder named '0'. Should I create it and put it there?
If you're coming from a ROM with Android 4.2 or newer to CyanogenMod 10.1 or newer: adb push update.zip /sdcard/0/
Click to expand...
Click to collapse
OR
Given that "cm-11-20141008-SNAPSHOT-M11-hammerhead.zip downloaded to my phone under /sdcard/", can I just: boot to recovery, click on Install, select the zip file and swipe to flash?
Finally a general query: Is there any reason I have to connect the phone to my laptop and run any adb, fastboot commands except to transfer the zip file from laptop to phone and to boot into bootloader or recovery with fastboot command? I already have TWRP running.
Thanks
Kashyap
Edit - before you flash, create a backup in twrp, including your efs, and copy it to your laptop for peace of mind.
I don't use cm, but that sounds like the right file. It doesn't matter which location the zip file is on your sdcard as far as I know, I think they've just said /sdcard/0 to make it easy to find from within twrp. Sounds to me like you've covered all your bases, nice to see someone manually flashing a nexus as a start. I'd go ahead and flash the zip, don't forget to factory reset if you're coming from stock. Also, you may want to find a gapps package if you haven't already. Since you seem to have taught yourself the right way, and your PC is setup for fastboot already, it should be easy to flash back to stock/restore under twrp. You don't even need adb to push files to your phone, you can just download them straight to the device. I generally only use my PC for fastboot flashing to stock,or transferring large amounts of data. Good luck, enjoy your nexus - first boot will generally take just long enough that you'll start wondering if its broken.
Thanks for the quick response.
scissors_cut_paper said:
don't forget to factory reset if you're coming from stock.
Click to expand...
Click to collapse
Just curious why?
If i do a factory reset, will it not delete /sdcard/cm-11-20141008-SNAPSHOT-M11-hammerhead.zip? Do I just copy it from laptop to phone after reset and proceed to flashing? Or there is some way to not wipe 'sdcard' during factory reset?
scissors_cut_paper said:
Edit - before you flash, create a backup in twrp, including your efs, and copy it to your laptop for peace of mind.
Click to expand...
Click to collapse
I did do a TWRP backup, but selected what to backup in the TWRP manager app, there is no option called EFS. Anyway, I'm creating a new using the recovery UI, where there is a check box called EFS. Thanks!
scissors_cut_paper said:
nice to see someone manually flashing a nexus as a start.
Click to expand...
Click to collapse
Didn't know there was any other more automated option/way. , is there? Only thing I knew was the CM Installer, which said the firmware isn't supported. .
scissors_cut_paper said:
Also, you may want to find a gapps package if you haven't already.
Click to expand...
Click to collapse
Yes, I was planning to, but taking it step at a time. .
I was planning to get gapps-kk-20140606-signed.zip from cyanogenmod.org, but lets see. I'll probably post another question here asking which is the compatible one.
Factory reset just wipes data/cache/dalvik, it should leave your sdcard storage intact. Just out of interest,why cm11? KitKat is pretty long in the tooth, and I've always found aosp based ROMs to perform better than cm on nexus 5. The problem with having no gapps will be no access to play store/google account services, so you'll have to get apps from less trustworthy sources.
Worked
Thanks.
It worked fine. Though it was totally useless without either the play store or basic CM apps. Couple of notes:
- After wipe/factory-reset (from TWRP Recovery UI) /sdcard was untouched.
- Installed the ROM using TWRP Recovery UI -> Install -> Select the zip file from /sdcard and swipe.
- CM Installer on Windows 7 laptop worked fine once the CM was installed. But it downgraded the build from Nov to Aug-2014.
- Also CM Installer removed my TWRP and replaced it with CWM. Not happy.
So actually all that's needed is:
- Unlock the bootloader and root.
- Install TWRP Manager
- Try to use the TWRP Manager's "Install TWRP" to install the TWRP Custom Recovery. If that doesn't work then do it manually. Download twrp.img
- Install ADB and fastboot, you don't need the whole 1GB Android SDK. Just search for "ADB Fastboot without SDK".- Enable USB debug, connect the phone and ensure that 'adb.exe devices' prints a device.- fastboot flash recovery twrp.img- Download the ROM zip file you wanna install on the phone itself, no need to involve the laptop.
- Boot into recovery (e.g. using TWRP Manager -> Reboot options) and do what I did above.
Once you've installed Cyanogenmod, DO NOT use CM Installer. This is written in July'2015. May be things would improve in future.
Before we begin, make sure you have the latest TWRP and superSU installed. OK, on to the steps:
1. Download the OTA zip from here, and the images zip from here.
**IMPORTANT! Use everything but the system image from the OTA, and only the system image from the images zip. **
2. Extract the images and copy them to a micro SD card. (format it to Exfat, the system image is 5.86GB, too big for fat32)
3. In TWRP, install the system, persist, boot, modem and recovery images to the corresponding partitions.
4. Reboot to bootloader.
5. In bootloader, fastboot oem lock.
6. fastboot reboot, and you will be back to locked stock!
Please let me know if you have any issues! ^
cool! Are there any parts of this that would work with the H910 (or even the H996)?
kibmikey1 said:
Before we begin, make sure you have the latest TWRP and superSU installed. OK, on to the steps:
1. Download the OTA zip from here, and the images zip from here.
**IMPORTANT! Use everything but the system image from the OTA, and only the system image from the images zip. **
2. Extract the images and copy them to a micro SD card. (format it to Exfat, the system image is 5.86GB, too big for fat32)
3. In TWRP, install the system, persist, boot, modem and recovery images to the corresponding partitions.
4. Reboot to bootloader.
5. In bootloader, fastboot oem lock.
6. fastboot reboot, and you will be back to locked stock!
Please let me know if you have any issues! ^
Click to expand...
Click to collapse
what's the difference between the system image from the OTA and from the images.zip?
dimm0k said:
what's the difference between the system image from the OTA and from the images.zip?
Click to expand...
Click to collapse
Bump for the answer to this question. I'd like to keep this method of returning to complete stock in my back pocket. Still on software version 10d rooted, suited and booted.
sciencedude100 said:
cool! Are there any parts of this that would work with the H910 (or even the H996)?
Click to expand...
Click to collapse
If you search, I have a back to stock zip for the H910. Just flash it in TWRP and it restores your phone to stock.
came out today. bricked my lg v20 h918
come up showing red text with number of times bootloader is unlocked and will not boot further..
tried direct install.
had to hold button down like going into recovery then select yes twice then getg into twrp then restore boot and lafs etc.
then when all working i tried to install the same version via twrp install same issue. apparently installing to wrong partition..
reinstalling the older 20.1 (hopefully you have it downloaded) from twrp worked fine.
Thanks for the info! Little late for me. Just wanted to post the last known good Magisk for anyone that needs it.
Search for download-magisk-20-1-stable
What did you do after booting into TWRP?
same issue, unfortunately, saw this post too late
same and now im screwed how can we recover this?
it says warranty void !!
number of times bootloader unlocked : 2 (in red
*Welcome to Fastboot mode:
* HOW TO EXIT fastboot mode
use 'fastboot reboot' command if the fastboot is available
i tried to install magisk 18 and then 20.1. they install but im still bricked at this same issue above.
HELP
h918
I was able to get up and running again by flashing H91820h.zip in TWRP, then flash Magisk-v20.1.zip and finally TWRP 3.3.1-0 2019-05-17 .img
Phone booted normally after this process. Hope this helps!
Similar situation. Fortunately, I did a nandroid backup first, so I restored it to get the phone up and running again.
My Success Story
For those of you who, like me, didn't have a known good backup to work with, here's what I did:
Determine ROM version installed if you don't know what it is (I was able to check the /system/build.prop file from TWRP under ro.lge.swversion)
Grab the appropriate ROM .zip file (I got my h910-10r zip file from the H910 Root Post)
Unzip the ROM file
Grab the "boot" file from the ROM and place on an SD card as boot.img
Flash boot.img to the boot partition using the TWRP install function (you'll have to toggle it to show Images in the install screen)
Reflash Magisk v20.1 (you can download it from github)
Wipe Dalvik and Cache
Reboot
Wait for the LONG boot process which will go through the nerve-wracking android is staring screen with the percentage bar as it rebuilds the Dalvik cache (I think that's what it's doing)
As a note, this did not clear any of my data.
Good luck, YMMV.
For anyone with this issue run the latest magisk uninstaller in twrp and restart the phone. If that doesn't work boot back into twrp and install magisk 20.1
---------- Post added at 08:47 PM ---------- Previous post was at 08:45 PM ----------
James.ptrsn said:
For those of you who, like me, didn't have a known good backup to work with, here's what I did:
Determine ROM version installed if you don't know what it is (I was able to check the /system/build.prop file from TWRP under ro.lge.swversion)
Grab the appropriate ROM .zip file (I got my h910-10r zip file from the H910 Root Post)
Unzip the ROM file
Grab the "boot" file from the ROM and place on an SD card as boot.img
Flash boot.img to the boot partition using the TWRP install function (you'll have to toggle it to show Images in the install screen)
Reflash Magisk v20.1 (you can download it from github)
Wipe Dalvik and Cache
Reboot
Wait for the LONG boot process which will go through the nerve-wracking android is staring screen with the percentage bar as it rebuilds the Dalvik cache (I think that's what it's doing)
As a note, this did not clear any of my data.
Good luck, YMMV.
Click to expand...
Click to collapse
Thanks so much, you really saved me. I was panicking for sure. These directions need to be stickied!
---------- Post added at 08:49 PM ---------- Previous post was at 08:47 PM ----------
BadToThePhone said:
For anyone with this issue run the latest magisk uninstaller in twrp and restart the phone. If that doesn't work boot back into twrp and install magisk 20.1
Click to expand...
Click to collapse
Tried didn't work, but thanks, the one above worked for sure, no lost data
lgkahn said:
came out today. bricked my lg v20 h918
come up showing red text with number of times bootloader is unlocked and will not boot further..
tried direct install.
had to hold button down like going into recovery then select yes twice then getg into twrp then restore boot and lafs etc.
then when all working i tried to install the same version via twrp install same issue. apparently installing to wrong partition..
reinstalling the older 20.1 (hopefully you have it downloaded) from twrp worked fine.
Click to expand...
Click to collapse
Unfortunately i wasn't lucky with this.. got stuck in fastboot, my sd and internal storage are both wiped, Rip years of data on that sd.. Can't get a system on the SD or internal storage, Fastboot isn't helping, ADB sideload won't load in twrp, LG Bridge won't detect my phone Am i screwed with this? I can boot to twrp but thats about it
texas7412 said:
Unfortunately i wasn't lucky with this.. got stuck in fastboot, my sd and internal storage are both wiped, Rip years of data on that sd.. Can't get a system on the SD or internal storage, Fastboot isn't helping, ADB sideload won't load in twrp, LG Bridge won't detect my phone Am i screwed with this? I can boot to twrp but thats about it
Click to expand...
Click to collapse
TWRP on my US996 automatically made the phone a usb drive when it got plugged in. Have you looked for it as a usb drive? also have you checked your usb drivers?
James.ptrsn said:
For those of you who, like me, didn't have a known good backup to work with, here's what I did:.......................
Click to expand...
Click to collapse
Fortunately there is even more easy way to recover.
My H990DS has been also affected by Magisk update. Luckily I discovered that Magisk itself makes a backup of the boot image during update from previous Magisk version. It is located in the /data/magisk_backup_<very long sequence of characters and digits>. The name of the backup archive file is boot.img.gz
So I booted to TWRP, unziped the file boot.img from the above archive and flashed it to the boot partition using TWRP. Then rebooted to system.
And that's all folks! No data loss, no need to look for original ROM.zip, no need to look for and re-flash Magisk 20.1 (the system has been restored automatically to Magisk 20.1), no need to wipe Dalvik and Cache!
I think that this solution is the most simple and easy, so need to be in sticky post.
I'm in the TWRP Recovery file manager and I can't see magisk backup folder.
pendgy said:
Fortunately there is even more easy way to recover.
My H990DS has been also affected by Magisk update. Luckily I discovered that Magisk itself makes a backup of the boot image during update from previous Magisk version. It is located in the /data/magisk_backup_<very long sequence of characters and digits>. The name of the backup archive file is boot.img.gz
So I booted to TWRP, unziped the file boot.img from he above archive and flashed it to the boot partition using TWRP. Then rebooted to system.
And that's all folks! No data loss, no need to look for original ROM.zip, no need to look for and re-flash Magisk 20.1 (the system has been restored automatically to Magisk 20.1), no need to wipe Dalvik and Cache!
I think that this solution is the most simple and easy, so need to be in sticky post.
Click to expand...
Click to collapse
Thank you. This helped a lot. Can't remember ever being without my phone for this long. Very stressful. This worked for my LG V20. Few things to add. I was super nervous to boot into twrp using the hardware "factory reset" option. Normally it just asks to wipe data once before booting into TWRP but after this happened, it asked two times. Was worried the magisk "update" wiped out my twrp and I was going to actually wipe all of my data using the recovery option. After unsuccessfully trying multiple ways to install twrp via fastboot as a safety net, I bit the bullet and did the double factory reset. Thankfully, it brought me to TWRP. Those of you worried, hope this helps ease your mind that twrp is intact after this debacle.
Next, using @pendgy help, I found the boot.img.gz but was unable to unzip in twrp. I copied the file to the internal sd so I could view on my pc. Connected to pc while in twrp and unzipped the boot.img.gz folder. Then extracted the boot.img into the internal sd. Was then able to install image to boot partition. Rebooted and everything was exactly as it was 17 hours ago when my heart sank. Yay!
Thanks to everyone for the reports and warnings. I saw the update to Magisk Manager yesterday on my Shield K1 and allowed that to update. I didn't update Magisk itself because I don't trust the direct install method through Manager. I saw the notification on my sandbox V20 this morning and dismissed it. My daily V20 hasn't received an update notification yet, but I think I disabled status bar notifications for Magisk on my daily. I'll be sure to not install 20.2 on either phone.
Magisk Manager's update notifications are pretty annoying to be honest. My devices are already rooted. An updated version of Magisk isn't going to make them rooted better.
Oh boy. Learning a lot of hard lessons this morning.
Apparently my TWRP install has been broken/corrupted for who knows how long. I'm now several hours into restoring my phone from basically scratch (had to retry a bunch of times because I'm a dumbdumb and haven't poked around at Android recoveries in ages).
Moral of the story: BACK UP EARLY and BACK UP OFTEN. If you don't have a backup (any kind of backup), the day will inevitably come when you wish you did. Sigh.
Oh well, maybe my phone will run a bit smoother now. Good luck everyone.
pendgy said:
Fortunately there is even more easy way to recover.
My H990DS has been also affected by Magisk update. Luckily I discovered that Magisk itself makes a backup of the boot image during update from previous Magisk version. It is located in the /data/magisk_backup_<very long sequence of characters and digits>. The name of the backup archive file is boot.img.gz
So I booted to TWRP, unziped the file boot.img from the above archive and flashed it to the boot partition using TWRP. Then rebooted to system.
And that's all folks! No data loss, no need to look for original ROM.zip, no need to look for and re-flash Magisk 20.1 (the system has been restored automatically to Magisk 20.1), no need to wipe Dalvik and Cache!
I think that this solution is the most simple and easy, so need to be in sticky post.
Click to expand...
Click to collapse
How did you unzip the archive with TWRP?
Edit: Nevermind, copied the archive to external SD und unzipped it with 7z on my computer.
fatappel said:
...............................
Next, using @pendgy help, I found the boot.img.gz but was unable to unzip in twrp. I copied the file to the internal sd so I could view on my pc. Connected to pc while in twrp and unzipped the boot.img.gz folder. Then extracted the boot.img into the internal sd. Was then able to install image to boot partition. Rebooted and everything was exactly as it was 17 hours ago when my heart sank. Yay!
Click to expand...
Click to collapse
In fact I did the same I didn't menioned all the stuff with connecting to PC, copying files to PC, extracting archives and copying back to the phone the boot.img file for subsequent flashing via TWRP. This is because I know the forum members here are experienced guys
The lesson learned is that TWRP is rock solid and we shall trust to it
---------- Post added at 23:37 ---------- Previous post was at 23:36 ----------
Attila17 said:
How did you unzip the archive with TWRP?
Click to expand...
Click to collapse
See my last post. I didn't. I used a PC to do that.
I got really ****ed by magisk.
Did the recommended update and now I`m stuck at the fastboot screen
I can fastboot reboot but nothing else
how do I boot into twrp (power vol button down only brings fastboot)
I tried flashing twrp via fastboot but i get failed remote (unknow command)
any help please ?
Hey there,
I am currently struggeling with my Samsung Galaxy S7 (Exynos) device, running on superman rom (Android 8).
What happened?
For root I´m using Magisk Manager and for banking apps I have Magisk hide running. Then the program told me that there is an update (Magisk App) available. So, as always and recommended, I choosed "Direct Install" but that failed for some reason. OK I thought´, no problem. Later I wanted to reboot my phone but it didn´t. The screen says "Downloading.... Do not turn off device!". I only can enter "Download Mode" and "Recovery Mode via TWRP".
What I tried so far:
1) Wipe cache/dalvik --> not successful
2) Tried to do a factory reset via twrp --> not successful
3) Tried to flash BL via Odin --> not successful
At this time I realised that the same problem occured to my Galaxy Tablet SM-T580. So I came to the point that I did something wrong with updating magisk on both devides.
What I also tried next:
4) Tried to delete magisk modules via twrp --> not successful
5) Tried to uninstall magisk through twrp by downloading the latest Magisk app and rename it to "uninstall.zip" as recommended in installation guide --> Not successful because of Error installing zip file: Unsupported /Unknown image format (unpacking image format)
What can I do next?
Can anyone please help me, since I have two bricked devices now????
A simple kernel flashing would fix the problem, extract the original boot.img of your current ROM, and flash it via TWRP.
Cause it is clearly a problem with your boot.img, if that didn't work (I'm sure it will), then just dirty flash your current ROM.
P.S. If you are encrypted, you might encounter an error doing a simple factory reset, you'll have to format the whole data partition.
Hi @Mohamedkam000,
many thanks for your help. After hours of browsing the web and trying various methods I was able to get my 2nd device (Samsung Galaxy Tab A from 2016) back to life.
What I did: I installed the latest samsung mobile phone drivers on my PC then I connected the tablet to it. I was able to access the internal memory and in the folder "data" Magisk put a backup of the original boot.img. So I installed this "boot.img" via TWRP and voila.......everything works fine again
I´m very happy now.
But unfortunately this method didn´t work with my Samsung Galaxy S7. I just couldn´t find any boot.img file on the phone.
Mohamedkam000 said:
A simple kernel flashing would fix the problem, extract the original boot.img of your current ROM, and flash it via TWRP.
Cause it is clearly a problem with your boot.img, if that didn't work (I'm sure it will), then just dirty flash your current ROM.
Click to expand...
Click to collapse
How do I have to do this? Sorry I´m a little unexperienced so could I get a kind of an step by step guide please?
Mohamedkam000 said:
P.S. If you are encrypted, you might encounter an error doing a simple factory reset, you'll have to format the whole data partition.
Click to expand...
Click to collapse
Don´t understand this. Could you please explain again?
Thank you so much already.
Kind regards,
cap.
capitarider said:
Hi @Mohamedkam000,
many thanks for your help. After hours of browsing the web and trying various methods I was able to get my 2nd device (Samsung Galaxy Tab A from 2016) back to life.
What I did: I installed the latest samsung mobile phone drivers on my PC then I connected the tablet to it. I was able to access the internal memory and in the folder "data" Magisk put a backup of the original boot.img. So I installed this "boot.img" via TWRP and voila.......everything works fine again
I´m very happy now.
But unfortunately this method didn´t work with my Samsung Galaxy S7. I just couldn´t find any boot.img file on the phone.
How do I have to do this? Sorry I´m a little unexperienced so could I get a kind of an step by step guide please?
Don´t understand this. Could you please explain again?
Thank you so much already.
Kind regards,
cap.
Click to expand...
Click to collapse
Glad your tablet revived again.
Magisk creates a backup of the boot.img found just before flashing magisk, it is compressed in gzip format, so you need to pull it, extract it, and push it back to the phone, then flash it.
The file is usually in /data/stock_boot_${SHA1}.img.gz
You can extract it using the built-in terminal of TWRP, if PC is not accessible at the moment by writing and executing the following command:
gunzip {stock-boot-name}.gz
Replace {stock-boot-name} with your backed-up boot name (without the curleybrackets), or you can use the following command:
gunzip *.gz
That'll extract the gzip archive, and the boot.img will be in /data of which you can navigate to it and flash it.
There's another guaranteed method, if you have the file of the ROM you're using right now, you can just open it (it's just a zip archive) and search for the boot.img of your specific phone model and flash it.
Another guaranteed method will be by flashing a custom kernel compatible with your current ROM, like Moro AiO kernel, of which has a wide support for ROMs starting from Oreo, and up to Q, AOSP, or stock-based, just in one file.
Moro's thread: Moro Kernel
you can't access kernel backup because TWRP does not support encryption and Magisk Manager might removed encryption in boot
aIecxs said:
you can't access kernel backup because TWRP does not support encryption and Magisk Manager might removed encryption in boot
Click to expand...
Click to collapse
Doesn't seem like he's encrypted, he found the boot backup of his tablet in /data so he has probably searched for a similar file on his S7, but since it is compressed, he won't find it solely.
Also he would've told us that his /data is empty or something.
start from scratch with older magisk, current 22 has bug
https://github.com/topjohnwu/Magisk/issues/4008
Thank you for your help.
I had a n old twrp backup on another external hard drive. I extracted the boot file and repached it with 7zip to boot.img and flashed through twrp. That also didn´t work for various times. TWRP always said "failed".
In the end I didn´t manage it to bring my phone back to live. Anyway, I decided to flash the latest LineageOS (Android 11) and now its running smooth again.
Thanks again.
Try using sp flash tools flashing the boot.img