Develop Bugs

[Q] TWRP Update path for One M8

Hello everyone and have a Merry Christmas,
I'm trying to update my TWRP recovery because I want to go 100% stock. I'm still running TWRP 2.7.0.2. The most recent version of TWRP is 2.8.3.0.
I downloaded the TWRP manager app from the Play store and easily selected the last available version of the recovery to install.
After downloading the .img file, I get a pop up that looks like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The pop up says: "Be sure that the listed path is correct for your device. An uncorrect check may result in bricking your device. You can't flash a recovery directly on Android on some devices. If you can't flash through Android, please choose a different method".
It looks like a "routine" alert, but nonetheless it sounds very alarming. How can I say if the listed path is the correct one for my device (HTC One M8 unbranded GSM international version)?
Thank you for helping.

why update twrp ? twrp is not stock ! and you can also fastboot flash it. oldskool way

Because the procedure to go stock requires some flashing and it was adviced to have the latest version running.
I'm not such an expert, I'm more the type who tries to read as much as possible before trying anything, and upgrading TWRP was a sort of "pre-step".
Also I'm not very keen to use fastboot: I got that it is great, but it is not very straightfoward for beginners.
The tool from the Play store seemed to do the job pretty good and easily.

Mr Hofs said:
why update twrp ? twrp is not stock ! and you can also fastboot flash it. oldskool way
Click to expand...
Click to collapse
What if I flash a custom recovery over a custom recovery? Is it possible to simply flash it and overwrite an already existing custom recovery?

there is no other way, the recovery will always overwrite the old one. its impossible to run 2 recoveries

Bricked OP3 - MD5 Checksum System: Failed

Hi All,
First off, this is what I did that led to this problem:
*** Beforehand, phone is unlocked, rooted, and updated to latest OTA OOS version (I think 3.2.7)
*** Unlock, recovery, root and NFS backup was implemented using this guide
*** OEM unlocking was turned off in the Developer Options
1. DPI was changed using the [email protected]_radaideh as recommended by some in Reddit -- this was OK
2. DPI was changed again using Le DPI Changer (found in play store), but used "EDIT BUILD.PROP" option
3. When phone rebooted, it was either stuck on OP logo, or just looping on OP logo (can't remember)
4. Booted into TWRP, and restored NFS backup (pre-root) and it was successful according to TWRP
5. When phone rebooted, it was either stuck on OP logo, or just looping on OP logo (can't remember)
Now after this moment, I tried Method 1 of the mega unbrick guide, but I encountered multiple md5 check failures upon boot. I then tried Method 2, and the md5 check failures were reduced to just one: system: failed.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can boot into fastboot, but I can't boot into recovery and system because of said error. Please help!

flash stock system.img

I already tried that using:
system.img from FULL unbrick tool -- doesn't work
system.img from 3.2.5 found somewhere here in XDA -- doesn't work
As mentioned above, the OOS version was at 3.2.7. I couldn't find it in the OP downloads site, but I did download the 3.2.6 image. That, however, did not contain any system.img.

did you find a solution

Try method 2 unbrick tool as per what they said, again. No other choice.

Hi, did you find a solution for this ? I have a similar issue and even after several flashes, i still have the failed md5 failure on system.img.

HTC One M8s TWRP Install Issue.

Hello there I'm trying to flash my M8 to the LineageOS.
However when I try to boot into recovery with TWRP my phone just hangs on the HTC logo.
The bootloader is unlocked and the phone is currently on the stock OS.
I've flashed TWRP via ADB and the OneM8AllInOneKit, but still get the same issue.
My phones information is below if it helps anyone out.
Thanks for any help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

OneM8AllInOneKit won't work on your device. Anything made for M8 like twrp, LineageOS won't work on your M8s
Check here for anything that you need - https://forum.xda-developers.com/htc-one-m8/one-m8s-general

Use htc_fastboot, not fastboot when flash. There is twrp for m8s, look at the threads.

I've tried the htc_fastboot and got the right twrp for masrhmellow and the cwmod one also and it still hangs on boot to recovey any ideas?

xpgdark said:
I've tried the htc_fastboot and got the right twrp for masrhmellow and the cwmod one also and it still hangs on boot to recovey any ideas?
Click to expand...
Click to collapse
There is no clockworkmod recovery for the M8s, that I know of (only for the M8, which is a different phone - different recoveries). So this leads me to believe you are still not flashing the right recoveries for the M8s; including the TWRP specifically for the M8s.

Reset
xpgdark said:
I've tried the htc_fastboot and got the right twrp for masrhmellow and the cwmod one also and it still hangs on boot to recovey any ideas?
Click to expand...
Click to collapse
Try install stock rom and start all over again. You can find it here at xda. Can send you links later. Sitting on phone now.

Here is the link to stock rom.
https://ruu.lalleman.net/HTC_M8S(QL...1_20.05_018_F_release_479349_combined_signed/
And the twrp,
http://src.voidzero.net/TWRP_recovery/

NukerB52 said:
Here is the link to stock rom.
https://ruu.lalleman.net/HTC_M8S(QL...1_20.05_018_F_release_479349_combined_signed/
Click to expand...
Click to collapse
Wrong version number, it doesn't match the OP's version. It will fail by version check.
He was able to get the phone working on Lineage, based on his other thread here: https://forum.xda-developers.com/htc-one-m8/one-m8s-general/htc-one-m8s-flash-boot-issues-t3736680
I'm guessing he had wrong version TWRP (not the one for M8s) and/or wrong LineageOS.

Did I Brick my 2XL?

After a bunch of research I finally decided to take the plunge to try and move to Lineage OS.
Phone is a Google unlocked 128GB 2 XL.
I was able to get through the unlock portion but after that all the guides went different directions. I was following the process from TWRP and at one point had the TWRP recovery app showing via fastboot but now all I get is the "device is corrupt" warning which then ends up in the white screen with Google logo and small unlocked icon.
Any chance I can get back to scratch or press forward to LineageOS/other ROM or is this thing a brick?
*Update* Not sure what key combination I used but I can get to the following TWRP screen. However the touchscreen does not respond and after the screen hibernates any key returns it to this state:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Download the last Google ROM image, enter the bootloader, and install it using the flash-all batch file included in the zip file. That will get you back to factory so you can proceed.

Strephon Alkhalikoi said:
Download the last Google ROM image, enter the bootloader, and install it using the flash-all batch file included in the zip file. That will get you back to factory so you can proceed.
Click to expand...
Click to collapse
Not sure how I can do that.
I can get to the default green START option. If I selection that the system boot to a white screen adn stops.
If I select BOOTLOADER the device pops back to the green START.
If I select RECOVERY it gets to the TWRP screen but the touchscreen nor buttons work.
I've tried connecting the phone via USB to my PC but no matter what mode I put it in ADB never detects it.

The "green Start" is where you want to be here. That's the bootloader. You need to make sure the driver - assuming Windows - is set to ADB Bootloader Interface in Device Manager as well as make sure you have the latest version of the ADB / Fastboot package.

Question Help I failed when trying to flash a room

As the title says... I messed up when I was trying to flash the EUR version on my Global Pad 5... I did't check and the boot loader got loked and now I can't start the tablet....
Is there a way to fix this...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Hello, you can now restore only the bootloader and the system via fastboot. To do this, download the rom ,, https://xiaomirom.com/en/download/xiaomi-pad-5-nabu-stable-V13.0.4.0.RKXMIXM/#global-fastboot ".
You must have previously unlocked the bootloader via MI unlock tool before you can flash the Global rom .
Then you will have the normal Global MIUI Android on again.

tobyw121 said:
Hello, you can now restore only the bootloader and the system via fastboot. To do this, download the rom ,, https://xiaomirom.com/en/download/xiaomi-pad-5-nabu-stable-V13.0.4.0.RKXMIXM/#global-fastboot ".
You must have previously unlocked the bootloader via MI unlock tool before you can flash the Global rom .
Then you will have the normal Global MIUI Android on again.
Click to expand...
Click to collapse
Thanks, but the problem is that I flashed a different rom using the flash tool and accidentally looked the boot loader, after this it won't start, the boot loader is locked and I'm not able to do anything.

You should be able to unlock it again using the xiaomi unlock tool, because it should keep oem unlock setting open.

You must boot at fastboot and Unlovk with the Tool. You dosnt wait 7 days. It works Instant and then you can flash fastboot Rom of your choice

You mean you unlocked a global one and flashed a Europe official rom and locked it and it got stuck?? I'm in the same boat, i have TR and i want to flash EU. I'm waiting the 7 days at the moment to unlock the bootloader. Advice pls
TDrkKnight said:
Thanks, but the problem is that I flashed a different rom using the flash tool and accidentally looked the boot loader, after this it won't start, the boot loader is locked and I'm not able to do anything.
Click to expand...
Click to collapse

Update... The bad I wasn't able restore it (I'm not up to date with all the "new" locks on android). The Good, I was able to return it, thats how I resolved the issue...