Develop Bugs

Boot loop - flashing via fastboot works, adb does not.

Okay, so I tried my best to search the forums and read the Q+A first, but the suggestions I've found so far didn't help me solve my problem.
I started with Hasoon200's tool kit and successfully unlocked the boot loader. Then, however, I got stuck at installing CWRM (it just wouldn't boot into recovery after installing). So I gave it a try with the "One X one Click" tool kit. I downloaded the n3okernel v34 and -modules as well as the newest nightly build of Cyanogen Mod (cm-10.1-20130414-NIGHTLY-endeavoru).
Now my HOX is caught in a boot loop. No matter which option I choose (fastboot / hboot, recovery, factory reset), it'll always go to the white HTC screen and stay there. Since Q+A's Q11 mentions it: yes, the last time I could boot into the OS (then still the stock image) I disabled fast boot in power settings.
Currently I can only access my HOX via fastboot, I already got a stock image and extracted the boot + recovery images, which I then flashed with the fastboot utility, as suggested in the Q+A's Q9. I erased the cache and rebooted to no avail. I also tried the firmware executable (RUU_ENDEAVOR_U_ICS_40_O2_DE_1.26.207.2_Radio_1.1204.90.13_release_251288_signed) to no avail.
Q+A's Q15 suggests sideloading via adb, but adb won't recognize my device.
I've also relocked the bootloader, this was suggested in another online ressource after flashing the stock boot+recovery images.
The phones HBOOT Version is 1.36.0000. I've noticed a different radio version than the one mentioned in my downloaded RUU; phone says 5.1204.162.29, downloaded file says 1.1204.90.13. I've not yet found a working download link with the right version number.
Please help.

Unlock it, make a full wipe in the custom recovery, install cm10.1, install gapps, flash the boot.img from the cm10.1 Rom and reboot.
So
Unlock it, flash a custom recovery (if you havent got one). If you still have trouble entering it you do this command in the bootloader
Fastboot erase cache

Mr Hofs said:
Unlock it, make a full wipe in the custom recovery, install cm10.1, install gapps, flash the boot.img from the cm10.1 Rom and reboot.
So
Unlock it, flash a custom recovery (if you havent got one). If you still have trouble entering it you do this command in the bootloader
Fastboot erase cache
Click to expand...
Click to collapse
Unlocking the bootloader works, but I'm not able to enter the recovery mode. It only shows a black screen (see attached picture).
EDIT: ok, wait... after flashing the clockwork recovery, I'm now getting into recovery mode. Will now try the next steps you suggested and give feedback later. Thanks a lot so far!

Press the Power and Volume down buttons which will take you the the hboot screen. From there select fastboot and flash a custom recovery like CWM via fastboot.
Now select hboot again and then select recovery!

Okay, so I successfully flashed CWM. I'm now able to boot into recovery. I also succeeded in flashing a boot.img which i took from cm-10.1-20130414-NIGHTLY-endeavoru.zip
c:\One\One\Data>fastboot flash boot boot.img
sending 'boot' (4960 KB)...
OKAY [ 0.684s]
writing 'boot'...
(bootloader) Format partition LNX done
OKAY [ 0.498s]
finished. total time: 1.186s
Now - when selecting hboot - the phone gets to another screen, the one where it displays the "HTC One" logo; I tried flashing the CM-image using fastboot (adb still doesn't work), but got following error message:
c:\One\One\Data>fastboot flash /sdcard update.zip
sending '/sdcard' (200098 KB)...
OKAY [ 25.507s]
writing '/sdcard'...
FAILED (remote: not allowed)
finished. total time: 25.716s
So close, yet so far...

So you have a working CWM installed right?
After flashing the boot.img... do "fastboot erase cache"
now go to CWM(recovery) and mount your sd card... copy the CM10ROM.zip and the gapps.zip to your HOX...
after that select wipe data and then wipe dalvic and cache...
Now select install zip from SD and install the ROM and then the gapps... reboot!

The problem is that I can't - or could'nt - transfer files any other way than using fastboot. However, I've now flashed Team Win TWRP2, and finally I'm able to access my phone over adb or just mount it and access it via explorer. Phew.

FINALLY!
So, if another noob like me finds this thread in the future...
After installing the TWRP2 recovery with flashboot flash twrp2.img, then booting into recovery and mounting my device, I was able to copy the CM-ROM-zip file onto the HOX. Then I rebooted into fastboot again and flashed the boot.img from aforementioned zip-file using "fastboot flash boot boot.img".
Booted again, selected the recovery system, installed ROM from zip file.
I'm getting too old for this ****. Almost had a heart attack when I thought I had bricked my phone. Thanks everyone for holding my hand, I appreciate it.

Good mate !
CASE CLOSED !

Soft bricked and can't flash any ROM

So , I was helping my buddy out with his Roger branded HTC One M8... He had the latest OTA, unlocked the bootloader, installed a custom recovery, and finally tried to flash ARHD 10.2.....
ARHD won't flash because it says it's a corrupt .ZIP.....
The Backup we made before flashing, recovers, then reboots back into recovery ( fails )
Any other ROM also says corrupt .ZIP...
Have never had an issue like this before, and I have no idea what to do from this point on....
Already tried recovering the backup & flashing a different ROM.
I can't find the RUU for the latest rogers ROM ( Firmware 2.23.631.2 ) so I haven't tried to flash a stock ROM.... Can you install a stock ROM from before the OTA, if you did the OTA? Or will that just lead to more issues?
Any help would be greatly appreciated! ( PHONE MODEL M8_UL )

What recovery and what version?
My first hunch would be fastboot erase cache, and re-flash recovery using fastboot. Often clears up lots of flashing issues like this. Also make sure you are using an up to date version of recovery.
Also, you can try to put the ROM on a different location such as the removeable SD and flash from there.
tutchthesky7 said:
I can't find the RUU for the latest rogers ROM ( Firmware 2.23.631.2 ) so I haven't tried to flash a stock ROM.... Can you install a stock ROM from before the OTA, if you did the OTA? Or will that just lead to more issues?
Click to expand...
Click to collapse
Rogers often does not issue RUUs, so I would not be surprised if this is the case for the M8 as well. Although I personally can't say, as its not my carrier.

redpoint73 said:
What recovery and what version?
My first hunch would be fastboot erase cache, and re-flash recovery using fastboot. Often clears up lots of flashing issues like this. Also make sure you are using an up to date version of recovery.
Also, you can try to put the ROM on a different location such as the removeable SD and flash from there.
Rogers often does not issue RUUs, so I would not be surprised if this is the case for the M8 as well. Although I personally can't say, as its not my carrier.
Click to expand...
Click to collapse
Using TWRP 2.7.0.1
I did the exact same thing as he did , except with my phone, and I never had any of these issues, same recovery, same ROM, same phone model, so weird :S

tutchthesky7 said:
Using TWRP 2.7.0.1
I did the exact same thing as he did , except with my phone, and I never had any of these issues, same recovery, same ROM, same phone model, so weird :S
Click to expand...
Click to collapse
That version is 2 iterations old.
But just might be a bad recovery install, it happens (and as you mentioned, or works on your phone, so why not your buddy's?). adb erase cache and install newest TWRP (2.7.1.0).

redpoint73 said:
That version is 2 iterations old.
But just might be a bad recovery install, it happens (and as you mentioned, or works on your phone, so why not your buddy's?). adb erase cache and install newest TWRP (2.7.1.0).
Click to expand...
Click to collapse
Will try that and report back

redpoint73 said:
That version is 2 iterations old.
But just might be a bad recovery install, it happens (and as you mentioned, or works on your phone, so why not your buddy's?). adb erase cache and install newest TWRP (2.7.1.0).
Click to expand...
Click to collapse
tutchthesky7 said:
Will try that and report back
Click to expand...
Click to collapse
Successfully flashed TWRP (2.7.1.0)
Attempted Recovery of the backup made right after installing TWRP for the first time, failed.
Attempted to flash the same ARHD Rom as tutchthesky7, see log:
<<<Log Start>>>
E:Unable to mount '/cache'
Full SELinux support is present.
E:Unable to mount '/cache'
E:Unable to mount zip file.
Error flashing zip '/external_sd/Android_Revolution_HD-One_M8_1-.2.zip'
Updating partition details...
E:Unable to mount '/cache'
[Restore Started]
Restore folder: '/external_sd/TWRP/BACKUPS/SH45WM01930/1M8PostRoot_Recovery_2014-08-19--01-04-57'
Skipping MD5 check based on user setting. ("I'd personally verified the checksum prior to all this")
E:No partitions selected for restore.
E:Unable to open zip file.
Error flashing zip '/external_sd/Android_Revolution_HD-One_M8_1-.2.zip'
Updating partition details...
E:Unable to mount '/cache'
<<<Log End>>>
Tried flashing the sideloaded ROM, and failed with the same resulting log as seen above.

Did you fastboot erase cache before installing TWRP, as I suggested?

Sir_Kato said:
Successfully flashed TWRP (2.7.1.0)
Attempted Recovery of the backup made right after installing TWRP for the first time, failed.
Attempted to flash the same ARHD Rom as tutchthesky7, see log:
<<<Log Start>>>
E:Unable to mount '/cache'
Full SELinux support is present.
E:Unable to mount '/cache'
E:Unable to mount zip file.
Error flashing zip '/external_sd/Android_Revolution_HD-One_M8_1-.2.zip'
Updating partition details...
E:Unable to mount '/cache'
[Restore Started]
Restore folder: '/external_sd/TWRP/BACKUPS/SH45WM01930/1M8PostRoot_Recovery_2014-08-19--01-04-57'
Skipping MD5 check based on user setting. ("I'd personally verified the checksum prior to all this")
E:No partitions selected for restore.
E:Unable to open zip file.
Error flashing zip '/external_sd/Android_Revolution_HD-One_M8_1-.2.zip'
Updating partition details...
E:Unable to mount '/cache'
<<<Log End>>>
Tried flashing the sideloaded ROM, and failed with the same resulting log as seen above.
Click to expand...
Click to collapse
the log got me thinking, after updating TWRP and then clearing the cache the mounting issue seemed wierd, so I tried sideloading to sdcard0 after clearing the cache once more then installing from sideload.zip on sdcard0, which entered the ARHD install GUI. so now I just need a confirmation on whether installing from sdcard0 is dangerous as a reformat mid install will erase the zip im trying to install from. soft brick is bad enough, really want to avoid an expensive paperweight.
I'm still in the menu, waiting for more seasoned minds to respond before I go through with it.
---------- Post added at 02:37 PM ---------- Previous post was at 02:29 PM ----------
redpoint73 said:
Did you fastboot erase cache before installing TWRP, as I suggested?
Click to expand...
Click to collapse
I did indeed. Just got the confirmation on the go ahead from OP. Better safe than sorry. Will post the outcome.

It worked beautifully, **** is so Cash. Thanks guys. you've been of great help.

[Q&A] Semi bricked Desire

Hey Folks!
After the dead of my desire (7 buzzes / vibrates -> indicates a broken soc/motherboard) and the new rising (got a motherboard of a desire with a broken screen) the old lady worked again!
I got the s/n and system from the one with the broken screen - this is normal because it's stored on the mainboard. It was a CM v7 as I remember.
Here as a list of things I did and where I stuck now:
flashed an up-to-date recovery TWRP -> worked
tried to install a new rom with a new hboot which -> didn't worked out
Since here I only can access the recovery
All attempts to flash something (via recovery or fastboot) -> doesn't work
also tried to use revolutionary (even it's already unlooked and s-off) -> but the app stucks
I could only flash the boot logo via fastboot the rest results in different errors like:
CID incorrect (pb99img.zip method)
Error (When trying to flash a .zip via recovery)
And an other Error i forgott (when flash via fastboot)
Also i can't get an information via fastboot (-getvar all). There is always a errormessage.
Here is my hboot-screen
Code:
*** AlphaRev***
BRAVO PVT1 SHIP S-OFF
HBOOT-0.93.0001
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.17.05.23
I'm not sure if something went wrong while trying to put a new hboot (partition-layout).
I have no idea what to do. Read about the half of the internet....
Anyone any idea?

Here is an other error message i get when running this fastboot command
Code:
fastboot getvar all
getvar:all FAILED (status malformed (1 bytes))
finished. total time: 0.001s
I'm realy appreciate any help!
BTW: I'm not a robot!

Des!re said:
CID incorrect (pb99img.zip method)
Error (When trying to flash a .zip via recovery)
And an other Error i forgott (when flash via fastboot)
Also i can't get an information via fastboot (-getvar all). There is always a errormessage.
Here is my hboot-screen
Code:
*** AlphaRev***
BRAVO PVT1 SHIP S-OFF
HBOOT-0.93.0001
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.17.05.23
I'm not sure if something went wrong while trying to put a new hboot (partition-layout).
I have no idea what to do. Read about the half of the internet....
Anyone any idea?
Click to expand...
Click to collapse
So good news is that it's not bricked if you can reach bootloader and recovery screen. Sounds like a driver issue or bad download of ROM, or both.
A few things to note:
- You haven't changed hboot because it still says 'Alpharev' on top of the bootloader screen. It should say the name of the hboot e.g. Alpharev CM7R2 if successful.
- CID incorrect happens when you try to flash a different region RUU. You should have tried the 2.3.3 GB WWE RUU, many threads in Q&A cover this.
- You should always try 'fastboot devices' command before flashing anything via fastboot, this will tell you straight away if you have driver issues.
This info I must have learnt reading the other half of the internet ...
What I would do:
- Confirm that fastboot is working first, check your drivers. Did you flash the recovery using fastboot? Flashing an hboot is largely the same method.
- Verify that the md5sum of the ROM.zip is correct on PC before flashing. Test several ROMs to be sure.
- Verify that the ROM is also compatible with the hboot as well or it won't boot.
- Make sure you nandroid backup if you have anything to save, then full wipe (wipe data/factory reset) before flashing the ROM.
- Make sure your sd card is correctly partitioned if the ROM requires one., as some put parts of the ROM on the partition. You will need a partition to install more than a few apps anyway.
- Post / research the exact error message if it's still not working, and at least state which ROMs you've tried.

eddiehk6 said:
So good news is that it's not bricked if you can reach bootloader and recovery screen. Sounds like a driver issue or bad download of ROM, or both.
A few things to note:
- You haven't changed hboot because it still says 'Alpharev' on top of the bootloader screen. It should say the name of the hboot e.g. Alpharev CM7R2 if successful.
- CID incorrect happens when you try to flash a different region RUU. You should have tried the 2.3.3 GB WWE RUU, many threads in Q&A cover this.
- You should always try 'fastboot devices' command before flashing anything via fastboot, this will tell you straight away if you have driver issues.
This info I must have learnt reading the other half of the internet ...
Click to expand...
Click to collapse
Thanks for your reply. Some things I forgot to mention in the thread above.
I successfully rooted, s-off, and flashed a new hboot & rom to my old desire.... all before she died. I remembered I needed some tries for the hboot... but it worked out fine in the end.
I also need to say that I tried (with the new/repaired one) different clients (hardware and os, win & linux) and different cables. Just to be sure.
I also went sure that fastboot is working (fastboot devices) and there always was my serial -> so it's good for sure
I read something about that the Alpharev hboot (with the repaired phone there was also the bootsplash with 'alpha-rev s-off / why so serious?' before I flashed it away to the stock 'htc') is somehow write-protected itself which can cause issues???
I tried to flash the "Alpha Jelly (250/5/182) hboot" to be able to install CarbonRom 1.0 (4.4.4) by spezi77 (http://forum.xda-developers.com/showthread.php?t=2658853). But I didn't succeeded at all.
eddiehk6 said:
What I would do:
- Confirm that fastboot is working first, check your drivers. Did you flash the recovery using fastboot? Flashing an hboot is largely the same method.
Click to expand...
Click to collapse
I think I flashed the recovery via fastboot, it just worked once. When I tried to flash CWM it didn't worked anymore.
eddiehk6 said:
- Verify that the md5sum of the ROM.zip is correct on PC before flashing. Test several ROMs to be sure.
Click to expand...
Click to collapse
I did checked the md5sum's and I tested a couple of Roms (more than 3)
eddiehk6 said:
- Verify that the ROM is also compatible with the hboot as well or it won't boot.
Click to expand...
Click to collapse
My old devices was a PVT4 and the repaired one is a PVT1 - there should be no difference for the hboot i guess?
eddiehk6 said:
- Make sure you nandroid backup if you have anything to save, then full wipe (wipe data/factory reset) before flashing the ROM.
Click to expand...
Click to collapse
This I should have done straight after I repaired the hardware and I was able to boot in CM7.... To late for now but if I have a working state I definitely do this!! :good:
eddiehk6 said:
- Make sure your sd card is correctly partitioned if the ROM requires one., as some put parts of the ROM on the partition. You will need a partition to install more than a few apps anyway.
Click to expand...
Click to collapse
I don't have a booting system yet so I need to postpone this. To be able to do the pb99img.zip method i formatted the whole sd-card with one partition as fat32. But when I have (hopefully) soon a working system I need to partion it correctly - easy!
eddiehk6 said:
- Post / research the exact error message if it's still not working, and at least state which ROMs you've tried.
Click to expand...
Click to collapse
I'm the resarcher! I'm going down to reasearch - I will report!
Thanks for your help so far!

I'm the resarcher! I'm going down to reasearch - I will report!
Click to expand...
Click to collapse
I went down to research!
I tried to flash hboot 'Bravo Stock' by Alpharev.
Code:
fastboot flash hboot bravo_alphaspl.img
sending 'hboot' (512 KB)...
OKAY [ 0.104s]
writing 'hboot'...
OKAY [ 0.160s]
finished. total time: 0.264s
looks good for me!
the bootscreen changed from
Code:
*** AlphaRev***
BRAVO PVT1 SHIP S-OFF
HBOOT-0.93.0001
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.17.05.23
to
Code:
--- AlphaRev ---
BRAVO PVT1 SHIP S-OFF
HBOOT-6.93.1002
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.17.05.23
so first and third line changed!
And because it's so nice to flash hboot i also flashed AlphaRev Jelly successfully!!
I try flash a rom now :fingers-crossed:

After I successfully flashed my hboot (twice!)....
I'm not able to wipe or install stuff....
Team Win Recovery Project v2.7.1.0
WIPE -> Factory Reset (Wipe Data, Cache and Dalvik)
Code:
Factory Reset Complete
Failed
E:Find_File: Error opening '/sys/class/backlight'
E:Unable to recreate and-sec folder.
Updating partition details...
E:Unable to mount storage
E:Unable to mount /sdcard during GUI startup.
Full SELinux support is present.
E:Unabke to mount /sdcard/TWRP/.twrps when trying to read settings file.
MTD Formatting "cache"
Done.
MTD Formatting "userdata"
Done.
Updatting partition details...
E:Unable to mount storage.
### FAILED ###
Team Win Recovery Project v2.7.1.0
Install -> ZIP
Code:
Zip Install Complete
Failed
E:Find_File: Error opening '/sys/class/backlight'
Updating partition details...
Full SELinux support is present.
Installing '/sdcard/roms/CARBON-KK-UNOFFICIAL-20140914-1119-bravo.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
E:Could not create file for updater extract in '/tmp/updater'
Error flashing zip '/sdcard/roms/CARBON-KK-UNOFFICIAL-20140914-1119-bravo.zip'
Updatting partition details...
### FAILED ###
Maybe there is something "broken" with the filesystem?
As always I appreciate any help

Did a 'clear userdata' in the boot menu and then a wipe via TWRP.
Now it was successful but with this errors in the console:
Code:
Factory Reset Complete
Successful
E:Find_File: Error opening '/sys/class/backlight'
Updating partition details...
Full SELinux support is present.
MTD Formatting "cache"
Done.
MTD Formatting "userdata"
Done.
Wiping Android Secure
Formatting SD-Ext using make_ext4fs function.
Updating partition details...
But I wonder where are these errors from
Installing a rom still doesn't work. I think the problem is this line:
Code:
E:Could not create file for updater extract in '/tmp/updater'

There is BIG FAT BUG in the newest TWRP (v2.7.1.0)
You can't install anything before manually create the tmp directory
You have to do the following steps to flash any files :
- boot into recovery mode
- choose 'Advanced'
- choose 'Terminal Command'
- You're now on the '/' (root of the file system). Choose 'Select'
- Type : 'mkdir tmp' without quotes, then Hit the enter key of your keyboard.
- Return to the main screen (Go back 3 times)
- Choose 'Install' and select the file.
Click to expand...
Click to collapse
>>> http://forum.xda-developers.com/showthread.php?t=2595654&page=12
This is to bad - it's the most recent version and the recovery has a bug like this!
Code:
Installing Carbonrom 4.4.4. for HTC Desire
Homemade by spezi77
Next shot should be Lollipop :victory:
[ROM/WIP] [5.0.2] [Jan-17] [UNOFFICIAL] ParanoidAndroid 5.0 Alpha
>>> http://forum.xda-developers.com/htc-desire/development/rom-paranoidandroid-5-0-alpha-t3002046

Des!re said:
There is BIG FAT BUG in the newest TWRP (v2.7.1.0)
You can't install anything before manually create the tmp directory
>>> http://forum.xda-developers.com/showthread.php?t=2595654&page=12
This is to bad - it's the most recent version and the recovery has a bug like this!
Code:
Installing Carbonrom 4.4.4. for HTC Desire
Homemade by spezi77
Next shot should be Lollipop :victory:
[ROM/WIP] [5.0.2] [Jan-17] [UNOFFICIAL] ParanoidAndroid 5.0 Alpha
>>> http://forum.xda-developers.com/htc-desire/development/rom-paranoidandroid-5-0-alpha-t3002046
Click to expand...
Click to collapse
I've personally never used TWRP on the Desire.
I recommend trying with 4EXT Recovery, never had any issues with it.
If you can successfully flash an hboot, you should be able to flash the recovery.img using the same method.

Stuck in bootloop, can access twrp, download and bootloader

my m9 randomly rebooted, and now its stuck in a bootloop, i'm able to get out of it and into download, and from there into twrp and the bootloader, but whenever i try to flash any of the Europe RUU's i get multiple errors
I am -
unlocked, but cant relock for some reason
s-on
have the latest 1.40.401.8 software
have twrp, but cant wipe data or do anything in it, just says failed to mount for data, cache etc
trying to reflash 1.40.401.8
i tried -
htc_fastboot flash zip (zip name).zip but results in the fail90 with please flush immediately text, it just repeats this oer an over with no other result even if i leave it for a while
fastboot oem lock just says failed, too many links and reboots
fastboot flash recovery recovery.img, stock recovery, says its succeeded but it still boots twrp
fastboot boot reocvery .img says booting but does nothing
tried to flash a different ruu but just says zip read error, cant open the zip
-
thanks in advance for you help, much appreciated

eggyfish said:
my m9 randomly rebooted, and now its stuck in a bootloop, i'm able to get out of it and into download, and from there into twrp and the bootloader, but whenever i try to flash any of the Europe RUU's i get multiple errors
I am -
unlocked, but cant relock for some reason
s-on
have the latest 1.40.401.8 software
have twrp, but cant wipe data or do anything in it, just says failed to mount for data, cache etc
trying to reflash 1.40.401.8
i tried -
htc_fastboot flash zip (zip name).zip but results in the fail90 with please flush immediately text, it just repeats this oer an over with no other result even if i leave it for a while
fastboot oem lock just says failed, too many links and reboots
fastboot flash recovery recovery.img, stock recovery, says its succeeded but it still boots twrp
fastboot boot reocvery .img says booting but does nothing
tried to flash a different ruu but just says zip read error, cant open the zip
-
thanks in advance for you help, much appreciated
Click to expand...
Click to collapse
Did you try the sd-card method? Rename the RUU to 0PJAIMG.zip, copy it into the root directory of a sd-card that is formatted to fat32 and not bigger than 32gb, put the card into your phone, boot into download mode and follow the instructions on the phone's screen. (Where did you actually get the 1.40.401.8 RUU? The sources I know provide the OTA update and not the RUU. So maybe you know a source I haven't heard of before.)
The output during relocking my old One S and/or my fathers One SV always stated the "too many links" error, too. Nevertheless the bootloader was always relocked after the reboot. (I've never relocked my M9 because there was no need to do so since I bought it.)
Fastboot boot recovery doesn't work on the M9. That's the reason why we need to grab the stock recovery from RUUs or OTAs instead of backing it up before we start flashing.
What TWRP version are you running? I think that error only existed in one of the older versions and is fixed in the newest one.
To replace TWRP with the stock recovery you can try this: Make a backup with only "recovery" checked. Rename the stock recovery to recovery.emmc.win. Replace the recovery.emmc.win in your TWRP backup with the renamed stock recovery and restore the backup. If you now reboot your phone TWRP will be replaced.

Flippy498 said:
Did you try the sd-card method? Rename the RUU to 0PJAIMG.zip, copy it into the root directory of a sd-card that is formatted to fat32 and not bigger than 32gb, put the card into your phone, boot into download mode and follow the instructions on the phone's screen. (Where did you actually get the 1.40.401.8 RUU? The sources I know provide the OTA update and not the RUU. So maybe you know a source I haven't heard of before.)
The output during relocking my old One S and/or my fathers One SV always stated the "too many links" error, too. Nevertheless the bootloader was always relocked after the reboot. (I've never relocked my M9 because there was no need to do so since I bought it.)
Fastboot boot recovery doesn't work on the M9. That's the reason why we need to grab the stock recovery from RUUs or OTAs instead of backing it up before we start flashing.
What TWRP version are you running? I think that error only existed in one of the older versions and is fixed in the newest one.
To replace TWRP with the stock recovery you can try this: Make a backup with only "recovery" checked. Rename the stock recovery to recovery.emmc.win. Replace the recovery.emmc.win in your TWRP backup with the renamed stock recovery and restore the backup. If you now reboot your phone TWRP will be replaced.
Click to expand...
Click to collapse
i'm running 2.8.7.0 twrp and neither the sd card method nor backup method worked for me, and bootloader is still unlocked with that output, twrp just says failed when i try and do a backup, and reboots when i try to flash a rom, do you think the phones memory is corrupted or something?, i just cant seem to do anything

eggyfish said:
i'm running 2.8.7.0 twrp and neither the sd card method nor backup method worked for me, and bootloader is still unlocked with that output, twrp just says failed when i try and do a backup, and reboots when i try to flash a rom, do you think the phones memory is corrupted or something?, i just cant seem to do anything
Click to expand...
Click to collapse
There is a newer version (2.8.7.1-CPTB-B1) which can be found in the beta version section here. Furthermore there is a stock backup provided in this thread that corresponds to your firmware version. Try to update TWRP and then to restore the backup.
Edit (Just to answer my own question from my previous post): The second Link provides a 1.40.401.8 RUU, too.

Flippy498 said:
Did you try the sd-card method? Rename the RUU to 0PJAIMG.zip, copy it into the root directory of a sd-card that is formatted to fat32 and not bigger than 32gb, put the card into your phone, boot into download mode and follow the instructions on the phone's screen. (Where did you actually get the 1.40.401.8 RUU? The sources I know provide the OTA update and not the RUU. So maybe you know a source I haven't heard of before.)
The output during relocking my old One S and/or my fathers One SV always stated the "too many links" error, too. Nevertheless the bootloader was always relocked after the reboot. (I've never relocked my M9 because there was no need to do so since I bought it.)
Fastboot boot recovery doesn't work on the M9. That's the reason why we need to grab the stock recovery from RUUs or OTAs instead of backing it up before we start flashing.
What TWRP version are you running? I think that error only existed in one of the older versions and is fixed in the newest one.
To replace TWRP with the stock recovery you can try this: Make a backup with only "recovery" checked. Rename the stock recovery to recovery.emmc.win. Replace the recovery.emmc.win in your TWRP backup with the renamed stock recovery and restore the backup. If you now reboot your phone TWRP will be replaced.
Click to expand...
Click to collapse
oh and my internal storage is reading as zero, i cant reformat it either, every action i preform in twrp just fails
and i still cant flash twrp
i get this -
writing 'recovery'...
(bootloader) HOSD CL#549783
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 2.078s]
finished. total time: 5.047s

eggyfish said:
oh and my internal storage is reading as zero, i cant reformat it either, every action i preform in twrp just fails
Click to expand...
Click to collapse
Well, that definitely sounds like your phone's memory is corrupted. I don't know whether there is another method to help you than sending it to HTC's repair service. Are you sure your storage isn't just full (since the flashing output seems to be ok [see below])?
Edit:
eggyfish said:
i get this -
writing 'recovery'...
(bootloader) HOSD CL#549783
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 2.078s]
finished. total time: 5.047s
Click to expand...
Click to collapse
I actually don't see any error in that output. Everthing is the way it should be.

Flippy498 said:
Well, that definitely sounds like your phone's memory is corrupted. I don't know whether there is another method to help you than sending it to HTC's repair service. Are you sure your storage isn't just full (since the flashing output seems to be ok [see below])?
Edit:
I actually don't see any error in that output. Everthing is the way it should be.
Click to expand...
Click to collapse
hmm, thats strange as it didnt update, i get the same readout when i flash stock, but it stsys on twrp. sureley it cant be full as a ruu flash wipes your data, i think i'll try get a repair from htc, thanks for your help

New MIUI Update does not update (reboots into TWRP)

Hi guys,
I have a rooted mi10t lite on MIUI.
Got an update today (miu v12.0.2.0.RJSEUXM) so downloaded it via phone and pressed 'reboot now'.
Issue is the phone reboots into TWRP recovery and when I boot back to system the phone still tells me to update the phone by rebooting it which goes back to TWRP.
I tried to install the update via TWRP > Install>
The internal storage is encrypted though so I moved the updated .zip file to my SD Card (root of SD card folder).
I go back into TWRP after a reboot and flash the install but get an error when trying to install the update. Not sure why?
Code:
E: Unble to decrypt FBE device
Updating partition details...
...done
Updating partition details...
...done
MTP Enabled
Installing zip file '/external_sd/miuupdatenumberetc.zip'
Checking for Digest file...
Error installing zip file ''/external_sd/miuupdatenumberetc.zip'
Updating partiion details...
...done
Any ideas please? I don't really want to update the phone if it results in me losing everything and having to install magisk and TWRP again, etc.
Thanks

1. to install OTA update from system, you have to have stock recovery
2. installed TWRP can not decrypt data partition
I would:
1. restore stock recovery
2. install OTA update
3. hotboot TWRP so you can decrypt data partition (fastboot boot twrp.img), install Magisk
Your Magisk modules and all data will remain intact.

i have the same problem. if i want to restore stock recovery, is it the right way to flash via fastboot the recovery.img from the fastboot rom, or i will get issues?