Database Info

[RECOVERY][DESIRE S] TWRP 2.8.7.0

TWRP
2.8.7.0
UNOFFICIAL
Just as the title says this is an unofficial build of TWRP recovery v2.8.7.0 for the HTC DESIRE S (Saga).
*** I DO NOT OWN A DESIRE S*** This has been tested on by numerous users previously and I test all my releases on the nearly identical Desire HD. It has been tested with both Sense roms and current KK/LP AOSP roms. I have put it to the test and not found any issues so far. If you find any bugs please report with an attached recovery log.
DOWNLOAD
Current Version for ODP Saga builds
<<HERE>>
Current Version for ODP Saga-opt builds
<<TWRP for SAGA-OPT>>
For more info on SAGA-OPT see the original release notes for ace-opt cm-12.1 HERE
Special thanks to @Mustaavalkosta & @kylon for all his work keeping this device alive for so long.
SOURCES
Recovery built in a CM-12.1 environment using device trees/kernel
from Mustaavalkosta's OpenDesireProject github
My modified trees/kernel are HERE and HERE
TWRP source from Omnirom​
Code:
Changelog:
7/30/15
-2.8.7.0
4/14/15
- 2.8.6.0
2/28/15
- fix reboots
2/27/15
- 2.8.5 release
- LP cm-12.0 based
- updated offmode blobs
1/10/2015
- 2.8.1.2 release
- MTP support is back on, no more USB mount. CM-12.0 went this direction and so shall recovery
- by-name partition mount support. Needed for 1/10 nightly and beyond.
1/5/2015
- 2.8.1.1 release (i know i'm falling behind)
- /sd-ext support
- f2fs support
11/15/2014
- 2.8.1 release
- Performance profiles in recovery, should speed up backup/restore just a bit
- Offmode charging images are back!!! Thanks to @mdmower for the guidance from 8960 series HTC's
6/13/2014
- fixed adb in recovery
6/12/2014
- fixed ability to use encryption
6/11/2014
- initial release
XDA:DevDB Information
TWRP-Desire S, Tool/Utility for the HTC Desire S
Contributors
jrior001, jrior001
Source Code: https://github.com/OpenDesireProject
Version Information
Status: Stable
Created 2015-11-23
Last Updated 2015-11-22

I've been requested to create my own thread since i sort of took over maintaining TWRP builds for the time being. These are the same builds I've been providing in the older TWRP thread.

jrior001 said:
I've been requested to create my own thread since i sort of took over maintaining TWRP builds for the time being. These are the same builds I've been providing in the older TWRP thread.
Click to expand...
Click to collapse
Thank you very much for your kind contribution to the community. I am very appreciated.

Thank you for keeping this device alive for all these years!!!
Having a problem lately though. When I try to connect my phone via fastboot, I just get a USB device not recognized. I have tried to install HTC USB drivers (official and forum downloads) and on my other android devices I have no issues to use fastboot or adb (meaning that it's set up correctly?). Any ideas on how to use fastboot on Windows 10?
Thanks for any help!

moesus said:
Thank you for keeping this device alive for all these years!!!
Having a problem lately though. When I try to connect my phone via fastboot, I just get a USB device not recognized. I have tried to install HTC USB drivers (official and forum downloads) and on my other android devices I have no issues to use fastboot or adb (meaning that it's set up correctly?). Any ideas on how to use fastboot on Windows 10?
Thanks for any help!
Click to expand...
Click to collapse
It might be possible by using Fastboot.reg method as it is working for me.

Hi,
I've recently found my ds and i thought i'd try out CM12.1 or even CM13. however i'm stuck at installing TWRP-saga-2.8.7.0-unofficial.img.
I can get twrp-2.6.3.0-saga.img to work OK.
Basically, after flashing the latest recovery via fastboot (looks to work OK) and then reboot into recovery, it just hangs on the startup flash screen. I have to pull the battery to get back into the bootloader again.
i have
HBOOT 2.00.2002
S-OFF (unlocked)
RADIO 3822.10.08.04_M
thanks

stehaworth said:
I've recently found my ds and i thought i'd try out CM12.1 or even CM13. however i'm stuck at installing TWRP-saga-2.8.7.0-unofficial.img.
Click to expand...
Click to collapse
CM13 uses the opt version, for 12.1 you might also want to go for the opt version. It will mean that you have to format your sd-card as ext4... If you go that way, you need 2.8.7.1.
stehaworth said:
Basically, after flashing the latest recovery via fastboot (looks to work OK) and then reboot into recovery, it just hangs on the startup flash screen. I have to pull the battery to get back into the bootloader again.
Click to expand...
Click to collapse
Maybe there was an error downloading the file? Check the file size just to see if it's offside...
TWRP-saga-2.8.7.0-unofficial.img - 7.4 MB
TWRP-recovery-sagaopt-2.8.7.1.img - 7.3 MB

i23098 said:
CM13 uses the opt version, for 12.1 you might also want to go for the opt version. It will mean that you have to format your sd-card as ext4... If you go that way, you need 2.8.7.1.
Maybe there was an error downloading the file? Check the file size just to see if it's offside...
TWRP-saga-2.8.7.0-unofficial.img - 7.4 MB
TWRP-recovery-sagaopt-2.8.7.1.img - 7.3 MB
Click to expand...
Click to collapse
i think i might have remembered something from when i originally was playing with this phone. it has a screen by Hitachi..... i think this stops me from doing anything CM12.1 +...

stehaworth said:
i think i might have remembered something from when i originally was playing with this phone. it has a screen by Hitachi..... i think this stops me from doing anything CM12.1 +...
Click to expand...
Click to collapse
Yeah, if you have an Hitachi panel you can't run a recent CM... It shouldn't affect the recovery, though... I think

lool, I flashed TWRP-recovery-sagaopt-2.8.7.1.img and issued factory reset... and it formatted my SD card (coz it takes it as internal memory)... I already recovered files most of files, but was "a bit" surprised... was it also like that in previous versions?

Unauthorized
i recently got to stupid situation - i wanted to try cm13 so i used tweaked twrp 2.8.7.1 for saopt sm13 and formated my sd card, loosing everything - i had to load the rom to the phone by using ./adb push. the rom was not stable enough to be used, so i wanted to go back - flashed back twrp 2.8.7.0 formated again my card and finding that i cannot mount phone to my macbook (dunno why?) and that ./adb push returns with info that device is unauthorized. i had to use different phone to put rom on sd card to be able to install it.
tweaked version or older version of twrp did not have this problem.

Hi, where can I read Step by Step instalation proces of TWRP

Hi,
how can i change from v2.8.7.0-saga to 2.8.7.1-sagaopt? every try within twrp quits with [IMAGE FLASH COMPLETED], but after reboot to recovery i'm still on v2.8.7.0-saga???
c_kay

c_kay said:
Hi,
how can i change from v2.8.7.0-saga to 2.8.7.1-sagaopt? every try within twrp quits with [IMAGE FLASH COMPLETED], but after reboot to recovery i'm still on v2.8.7.0-saga???
c_kay
Click to expand...
Click to collapse
Same problem

mentodsman said:
Same problem
Click to expand...
Click to collapse
use Rashr - Flash Tool apk to flash the img

[ROM][7.1.2][v521][OFFICIAL] LineageOS 14.1 LG G-Pad X 8.0 v521[Nightly]

LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device.
All the source code for Lineage OS is available in the Lineage OS Github repo.
Install instructions:
* Reboot into recovery
* Wipe data, system and cache if it's a fresh install (any rom which is not official Lineage, including Cyanogenmod).
* No wipes required if you're updating from a previous official build of Lineage (wipe cache and dalvik cache recommended).
* Flash ROM and, optionally, Gapps and Root. Reboot.
Download links:
* OfficialROM: https://download.lineageos.org/v521 [nightly]
* Gapps: Open GApps
* Root: https://download.lineageos.org/extras [su (arm)]
Source Code: https://github.com/LineageOS
Version Information
Status: Nightly
Last Updated 2017-04-28

I have flashed your build and all is well so far except for the Developer Options isn't accessable. I only use this for the Advanced reboot options and root access options. Any way to get this accessable or should I wait for the next build? Thanks

Hawksronny said:
I have flashed your build and all is well so far except for the Developer Options isn't accessable. I only use this for the Advanced reboot options and root access options. Any way to get this accessable or should I wait for the next build? Thanks
Click to expand...
Click to collapse
The past couple of builds somehow broke the Developer Options. Im going to guess and say it has something to do with the code for 7.1.2 being merged as there have been a lot of things changed in the Settings repo. Ive been trying to use older Settings and Developer apks but none have worked.

I have narrowed down the boot issue to the sepolicy file inside the ramdisk.

On the latest build developer options is just a white blank screen. . Now I can't figure out how to get into recovery mode, I usually just boot into recovery through adb but I can't use adb without turning on USB debugging

pdxmark78 said:
On the latest build developer options is just a white blank screen. . Now I can't figure out how to get into recovery mode, I usually just boot into recovery through adb but I can't use adb without turning on USB debugging
Click to expand...
Click to collapse
no need to wipe if coming from previous nightly. if u dnt wipe u can keep ur adb and root options without needing to go into developer settings.
to get into recovery hold vol. down and power until the LG screen appears
then let go of the power button ,while still holding the vol dwn. count 1sec then press and hold power again.
you will be brought to a screen asking if u want to favtory reset press yes then yes again.
it will not wipe anything but it will then reboot in recovery

New build up. Going to work you magic

Munns86 said:
New build up. Going to work you magic
Click to expand...
Click to collapse
Unfortunately the older ramdisk isn't going to work with the new builds as they're 7.1.2. We're going to have to wait until the issue is found and fixed in the source. Ive tried every workaround i can think of ive gotten it as far as a bootloop with the device being recognized in adb, monitor etc. going to try and debug see if i can figure out why its looping.
Looks like the last workung nightly is going to be 04/14, for now.

HighRidas said:
Unfortunately the older ramdisk isn't going to work with the new builds as they're 7.1.2. We're going to have to wait until the issue is found and fixed in the source. Ive tried every workaround i can think of ive gotten it as far as a bootloop with the device being recognized in adb, monitor etc. going to try and debug see if i can figure out why its looping.
Looks like the last workung nightly is going to be 04/14, for now.
Click to expand...
Click to collapse
Well thanks all the same. You've done great work. We've pretty much handed the answer to the maintainer that you've found and they still have done nothing.

i'm keep getting update error. update completes around 45%.. then E:unknown command in red... anyone knows what to do? it goes to boot screen, then blank screen... does not boot.

alphakp295 said:
i'm keep getting update error. update completes around 45%.. then E:unknown command in red... anyone knows what to do? it goes to boot screen, then blank screen... does not boot.
Click to expand...
Click to collapse
Try re-downloading sounds like a corrupted file.

Well some possible good news. The next build should be fixed. The problem was cleared on the regression tracker.

New build is up on the official site and is confirmed working

Developer options still freezes. but, if you do not wipe, your settings should remain

v521-Resurrection-Remix-N-v5-8-x-OMS-LG-G-Tab-X-8.0

Recently acquired this nifty little tablet. I've toyed around and upgraded to stock Nougat (v52120f).
I've followed the dirtycow method for rooting and installing TWRP. I am able to successfully sideload latest nightlies of LOS (lineage-14.1-20170505-nightly-v521-signed) and/or Resurrection (RR-N-v5.8.3-20170509-v521-Nightly). After the flash, both my wifi and bluetooth MAC addresses have changed from the original. Restoring back to stock restores the original MAC addresses.
Stock - 5c:af:06:xx:xx:xx
LOS - 00:0a:f5:23:47:54
RR - 00:0a:f5:23:47:54
Anyone else seen this issue?

Hi is there a way to have irda blaster (infrared) working with this ROM? Thanks

jotade said:
Hi is there a way to have irda blaster (infrared) working with this ROM? Thanks
Click to expand...
Click to collapse
if you want to try this kernel out. flash image in recovery. can't guarantee it will work as i don't have anything to test it on but i enabled everything, that I could find, IR-rc related
https://www.mediafire.com/file/07397adkju2on9g/boot.img

HighRidas said:
if you want to try this kernel out. flash image in recovery. can't guarantee it will work as i don't have anything to test it on but i enabled everything, that I could find, IR-rc related
https://www.mediafire.com/file/07397adkju2on9g/boot.img
Click to expand...
Click to collapse
Thanks i will try but flash via fastboot flash boot boot.img? O how. Please let me know

jotade said:
Thanks i will try but flash via fastboot flash boot boot.img? O how. Please let me know
Click to expand...
Click to collapse
in twrp recovery select install image then select the downloaded .img file and select boot.

No OS installed in TWRP

Hi guys
I was trying some of custom rom on my OP6 and I wanted to go back to Oxygen OS. So i did a clean installation with system wipe and i flashed the last full OTA update. But since i can't boot to system anymore, TWRP always displays that there is no OS installed despite the fact that I've tried several rom . Is this the first time it's done this to me how can I fix it?

raptax said:
Hi guys
I was trying some of custom rom on my OP6 and I wanted to go back to Oxygen OS. So i did a clean installation with system wipe and i flashed the last full OTA update. But since i can't boot to system anymore, TWRP always displays that there is no OS installed despite the fact that I've tried several rom . Is this the first time it's done this to me how can I fix it?
Click to expand...
Click to collapse
The best suggestion I can give you is to flash stock oos with TWRP, reboot to stock recovery, without flashing anything else, wipe data from stock recovery and startup system.. if it is working you can flash back TWRP and magisk if you need it
Just be careful because at your point is easy to lose all of your stored data

Hitman478™ said:
The best suggestion I can give you is to flash stock oos with TWRP, reboot to stock recovery, without flashing anything else, wipe data from stock recovery and startup system.. if it is working you can flash back TWRP and magisk if you need it
Just be careful because at your point is easy to lose all of your stored data
Click to expand...
Click to collapse
I tried your solution ..... and it worked thx man
I don't know why there was a problem with TWRP but the important thing is that my phone is alive again

raptax said:
I tried your solution ..... and it worked thx man
I don't know why there was a problem with TWRP but the important thing is that my phone is alive again
Click to expand...
Click to collapse
Exactly! I'm glad to had help you sometimes if something is done wrong TWRP is dangerous

raptax said:
I tried your solution ..... and it worked thx man
I don't know why there was a problem with TWRP but the important thing is that my phone is alive again
Click to expand...
Click to collapse
If you wipe system, then flash oos ROM, TWRP will think there is no os. You can just ignore and boot.

Wiping system then flashing any time will make twrp display "no os installed" it does this because it hasn't created files for twrp to check if you have a ton installed. Flashing twrp then rebooting to twrp fixes it.

Reboot to stock recovery?
Hitman478™ said:
The best suggestion I can give you is to flash stock oos with TWRP, reboot to stock recovery, without flashing anything else, wipe data from stock recovery and startup system.. if it is working you can flash back TWRP and magisk if you need it
Just be careful because at your point is easy to lose all of your stored data
Click to expand...
Click to collapse
Hi, need a little bit of support, since I'm new to this as well. I was in a working OOS open beta 25/28, but then I think I flashed the wrong zip (OOS 9.0.9?), and I was not able to boot to system. It kept going to "bootloader unlocked" screen and custom recovery. Currently in TWRP blu_spark 3.3.1-x v. 9.109, and it's showing me no OS installed when I attempt to reboot. I haven't rebooted to system yet.
All the folders in my /sdcard is gibberish... if I try to push a file to it, it says "Required key not available." I did remove all security/passwords from my phone before doing any updates/backups.
I completed a wipe cache/dalvik/system via TWRP, and flashed the OOS OTA stable Android 10 zip downloaded directly from OnePlus Support. Considering this situation, do you still think it's safe for me to reboot to system? Then how do I get to stock recovery from there--is that by holding down the buttons?

5xonlineage said:
Hi, need a little bit of support, since I'm new to this as well. I was in a working OOS open beta 25/28, but then I think I flashed the wrong zip (OOS 9.0.9?), and I was not able to boot to system. It kept going to "bootloader unlocked" screen and custom recovery. Currently in TWRP blu_spark 3.3.1-x v. 9.109, and it's showing me no OS installed when I attempt to reboot. I haven't rebooted to system yet.
All the folders in my /sdcard is gibberish... if I try to push a file to it, it says "Required key not available." I did remove all security/passwords from my phone before doing any updates/backups.
I completed a wipe cache/dalvik/system via TWRP, and flashed the OOS OTA stable Android 10 zip downloaded directly from OnePlus Support. Considering this situation, do you still think it's safe for me to reboot to system? Then how do I get to stock recovery from there--is that by holding down the buttons?
Click to expand...
Click to collapse
No, your internal storage Is like trash cause the last rom you flashed has older security patch than oos10. Your device Is now encrypted and wont boot to system. I Guess you have to erase all via MSN tool or fastboot signed rom. Even if you wiped what mentioned above, your problem still be the data.

Fastboot method?
°Washy said:
No, your internal storage Is like trash cause the last rom you flashed has older security patch than oos10. Your device Is now encrypted and wont boot to system. I Guess you have to erase all via MSN tool or fastboot signed rom. Even if you wiped what mentioned above, your problem still be the data.
Click to expand...
Click to collapse
Thank you for replying. I'm relieved that you know of a couple methods to try.
Is using "Format Data" in TWRP an option for dealing with the encryption??
For the MSN tool, can I use this one? Tried looking around, but it's unclear. "[TOOL] MsmDownloadTool V4.0 International (Oxygen OS 5.1.5)" https://forum.xda-developers.com/on...wnloadtool-v4-0-international-t3798892/page10
I would be more comfortable with using fastboot, but am I at any risk of having lost fastboot, or can I just turn off my device from TWRP right now and hold down the buttons to get there? Afraid to move out of TWRP right now, in case I can't get back. I do have twrp-3.3.1-18-enchilada-Q-mauronofrio.img that I can run from fastboot if needed.
By "signed rom," do you mean I can simply flash one of the zips here from fastboot? "[OnePlus 6][ROM][OTA][Oxygen OS] Mirrors for official Oxygen OS ROMs and OTA updates" https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244
Thanks again.

5xonlineage said:
Thank you for replying. I'm relieved that you know of a couple methods to try.
Is using "Format Data" in TWRP an option for dealing with the encryption??
For the MSN tool, can I use this one? Tried looking around, but it's unclear. "[TOOL] MsmDownloadTool V4.0 International (Oxygen OS 5.1.5)" https://forum.xda-developers.com/on...wnloadtool-v4-0-international-t3798892/page10
I would be more comfortable with using fastboot, but am I at any risk of having lost fastboot, or can I just turn off my device from TWRP right now and hold down the buttons to get there? Afraid to move out of TWRP right now, in case I can't get back. I do have twrp-3.3.1-18-enchilada-Q-mauronofrio.img that I can run from fastboot if needed.
By "signed rom," do you mean I can simply flash one of the zips here from fastboot? "[OnePlus 6][ROM][OTA][Oxygen OS] Mirrors for official Oxygen OS ROMs and OTA updates" https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244
Thanks again.
Click to expand...
Click to collapse
I hardbricked my device about 10 times and i was able to recovery It even from a blank screen. Btw format data Will erase all your data but also the internal storage. About fastboot dont be afraid, go under twrp reboot section and reboot to bootloader. Then go under xda op6 guide section and search for mirrors for fastboot rom guide by Mauronofrio. He pushed my ass out the **** a lot of time.
P.s. Sorry but I dunno how to paste a link via xda app. Yes, ik! It's a vert newbie thing.

5xonlineage said:
Thank you for replying. I'm relieved that you know of a couple methods to try.
Is using "Format Data" in TWRP an option for dealing with the encryption??
For the MSN tool, can I use this one? Tried looking around, but it's unclear. "[TOOL] MsmDownloadTool V4.0 International (Oxygen OS 5.1.5)" https://forum.xda-developers.com/on...wnloadtool-v4-0-international-t3798892/page10
I would be more comfortable with using fastboot, but am I at any risk of having lost fastboot, or can I just turn off my device from TWRP right now and hold down the buttons to get there? Afraid to move out of TWRP right now, in case I can't get back. I do have twrp-3.3.1-18-enchilada-Q-mauronofrio.img that I can run from fastboot if needed.
By "signed rom," do you mean I can simply flash one of the zips here from fastboot? "[OnePlus 6][ROM][OTA][Oxygen OS] Mirrors for official Oxygen OS ROMs and OTA updates" https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244
Thanks again.
Click to expand...
Click to collapse
Do you solve, man?

Fastboot ROM
°Washy said:
I hardbricked my device about 10 times and i was able to recovery It even from a blank screen. Btw format data Will erase all your data but also the internal storage. About fastboot dont be afraid, go under twrp reboot section and reboot to bootloader. Then go under xda op6 guide section and search for mirrors for fastboot rom guide by Mauronofrio. He pushed my ass out the **** a lot of time.
P.s. Sorry but I dunno how to paste a link via xda app. Yes, ik! It's a vert newbie thing.
Click to expand...
Click to collapse
That's awesome, I'm starting to grasp how much of a genius Mauronofrio is, after so many people referencing his work.
In his guide, he says, "These ROMs can't be used to update or downgrade your phone but just to restore your phone, so don't use them to come back to oreo or to update from oreo to pie." This may be a dumb question, but how do I know which zip/OOS version to flash, when I don't have a functioning OS on my phone?

5xonlineage said:
That's awesome, I'm starting to grasp how much of a genius Mauronofrio is, after so many people referencing his work.
In his guide, he says, "These ROMs can't be used to update or downgrade your phone but just to restore your phone, so don't use them to come back to oreo or to update from oreo to pie." This may be a dumb question, but how do I know which zip/OOS version to flash, when I don't have a functioning OS on my phone?
Click to expand...
Click to collapse
I talked with Mauronofrio in pm and he said me that you could solve your issue simply flash the ROM you want and format data after flash that one. Remember that your internal will be wiped but it would happen in any scenario we talked.

Magisk, boot img?
°Washy said:
I talked with Mauronofrio in pm and he said me that you could solve your issue simply flash the ROM you want and format data after flash that one. Remember that your internal will be wiped but it would happen in any scenario we talked.
Click to expand...
Click to collapse
That worked! And starstruck that you were able to check that with him. I flashed Mauronofrio's fastboot ROM for 10.3.2 and it rebooted (WOW). I clicked through the Google setup pages and checked that my data and wifi worked.
I then went back into fastboot, booted M's twrp img, fomatted data, and then installed twrp-3.3.1-x_blu_spark_v9.109_op6.zip, rebooted into recovery.
Then I think I made a mistake, because I installed Magisk-v20.4.zip. It succeeded, but now I can't boot into system anymore. Is it too late to flash the 10.3.2 boot.img?

5xonlineage said:
That worked! And starstruck that you were able to check that with him. I flashed Mauronofrio's fastboot ROM for 10.3.2 and it rebooted (WOW). I clicked through the Google setup pages and checked that my data and wifi worked.
I then went back into fastboot, booted M's twrp img, fomatted data, and then installed twrp-3.3.1-x_blu_spark_v9.109_op6.zip, rebooted into recovery.
Then I think I made a mistake, because I installed Magisk-v20.4.zip. It succeeded, but now I can't boot into system anymore. Is it too late to flash the 10.3.2 boot.img?
Click to expand...
Click to collapse
No. Just flash stock boot image if magisk broke something.

Rooted
°Washy said:
No. Just flash stock boot image if magisk broke something.
Click to expand...
Click to collapse
I ended up following the guide to Magisk Root without TWRP for OnePlus 6 Oxygen OS https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853 since it was referenced by Mauronofrio's post for having issues getting his TWRP to work with latest Magisk.
Someone posted a patched boot.img for 10.3.2, so now I'm rooted without TWRP. Priorities. Now all I need is for special characters and emojis to work Will keep an eye on other threads.
I'm learning a lot, thanks so much for all your help. You pointed me in the right direction when I was not sure what the hell to do!

5xonlineage said:
I ended up following the guide to Magisk Root without TWRP for OnePlus 6 Oxygen OS https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853 since it was referenced by Mauronofrio's post for having issues getting his TWRP to work with latest Magisk.
Someone posted a patched boot.img for 10.3.2, so now I'm rooted without TWRP. Priorities. Now all I need is for special characters and emojis to work Will keep an eye on other threads.
I'm learning a lot, thanks so much for all your help. You pointed me in the right direction when I was not sure what the hell to do!
Click to expand...
Click to collapse
I followed that thread for the first A10 release cause there wasn't a worked twrp yet. You are welcome man, when I feel myself usefull I always try to help.

Redmi 9A bootloop

Hello, I have a Redmi 9A in the default stock state (no unlocked bootloader and default recovery, no TWRP).
After a random shutdown while using it normally, it's stuck in a bootloop in the default recovery.
I've read other threads, and I think I can try to recover it by using SP Flash Tool (please confirm if this is correct), but I'm more concerned about the data inside the device.
Can I somehow recover the data before flashing it, or is it impossible to do that since my bootloader is locked?
Thanks.

Well I don't think you can recover data I guess, maybe if you only select download not format + download in sp flash tool but maybe you brick again your phone.

it boots to recovery, so use adb or mount internal storage. you can also dirtyflash ROM

yaro666 said:
it boots to recovery, so use adb or mount internal storage. you can also dirtyflash ROM
Click to expand...
Click to collapse
Sorry for the delay, been doing some reading on these things.
By using adb, do you mean using adb pull to get the files? In the recovery, Connect to MI Assistant only gets the device in sideload, so I don't think that's possible. Don't have the option to mount storage either.

You have sideload?? If yes open adb in pc and type : adb sideload file.zip ( your rom ** btw you need recovery rom not fastboot**) idk if you will delete data or no

I tried that, but without success apparently. The rom is loading for some time, and then reports the error:
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
From what I've read, it might be due to a bad driver installation, I will look at it and update

madafaka7 said:
I tried that, but without success apparently. The rom is loading for some time, and then reports the error:
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
From what I've read, it might be due to a bad driver installation, I will look at it and update
Click to expand...
Click to collapse
Ok

Reinstalled drivers, still returns the same error.

try older ROMs - either you have faulty hardware or some minor bug

yaro666 said:
try older ROMs - either you have faulty hardware or some minor bug
Click to expand...
Click to collapse
I've tried to sideload the latest recovery ROMs for 12.0 and 12.5, the device was 12.5 when it "crashed". Should I try MIUI 11, or is it enough with older 12 versions?

madafaka7 said:
I've tried to sideload the latest recovery ROMs for 12.0 and 12.5, the device was 12.5 when it "crashed". Should I try MIUI 11, or is it enough with older 12 versions?
Click to expand...
Click to collapse
Try 12.0.20, the 12.5 have a lot of bugs and yeah

Rares6567 said:
Try 12.0.20, the 12.5 have a lot of bugs and yeah
Click to expand...
Click to collapse
That's the one I've tried already, it's the latest 12.0 version.
I guess I'll try to use SP Flash Tool, but it looks like the hardware is messed up...

Ok, a bit late but I'm going to update just in case anyone faces the same problem.
After trying every option with no success, I gave up on recovering user data and wiped all data from the stock recovery menu, and that solved the bootloop somehow. I'm guessing an app was messing up the system, but I don't know.
Thanks @Rares6567 and @yaro666 for your help.

madafaka7 said:
Ok, a bit late but I'm going to update just in case anyone faces the same problem.
After trying every option with no success, I gave up on recovering user data and wiped all data from the stock recovery menu, and that solved the bootloop somehow. I'm guessing an app was messing up the system, but I don't know.
Thanks @Rares6567 and @yaro666 for your help.
Click to expand...
Click to collapse
Happy to hear that

Question [HELP] I keep failing trying to flash a custom Android 12 ROM on the Redmi Note 11 Pro (veux). Can someone help me figure out what I'm doing wrong?

I've owned Samsung, Lenovo and Moto phones before, and I never had any problems unlocking them and flashing custom recoveries and ROMs. This is my 2nd Xiaomi phone and like the 1st I keep bricking and unbricking it. The only thing I can manage to do is sometimes get TWRP on it, or the normal ROM.
- Version: European version of the Redmi Note 11 Pro, codename veux.
- TWRP: https://forum.xda-developers.com/t/twrp-3-7-0_12-for-veux-peux.4520689/
- ROM: https://forum.xda-developers.com/t/rom-13-veux-peux-official-evolution-x-11-09-22.4497785/
___
1st attempt:
1 - After unlocking the bootloader it reinstalled a clean ROM. I then forgot to turn USB debugging on so that was my fault. Because after that I went into fastboot and flashed this TWRP with fastboot flash boot name.img
2 - On this first try I then rebooted to recovery, but it sent me to the normal one instead. In essence I bricked it so I followed this guide to reset it
___
2nd attempt:
1 - I enable USB debugging
2 - go into fastboot: fastboot flash boot name.img
3 - reboot to recovery
4 - in TWRP I try to flash the ROM from the internal storage. It fails after around 33% or something. Errors about not being able to mount certain folders
___
3rd attempt:
1 - reboot to recovery
2 - try and sideload the ROM from my laptop with the command adb sideload name.zip
3 - fails around 40% with similar errors
___
4th attempt:
1 - reboot to bootloader
2 - try instead fastboot boot name.zip to flash the ROM. It gives me the error: requested download size is more than max allowed fastboot
___
In between these tries TWRP sometimes loses touchscreen functionality. I notice when I flash OrangeFox and then TWRP again, I get touchscreen functionality back. I know this is a well known issue but it's interesting I can back TWRP working again when doing the above.
Another interesting is that when I flash OrangeFox and reboot to recovery, it's still TWRP.

When you flash a new ROM, you need to format the userdata and the cache partitions.
EDIT:
Btw, i'm curious to know where you found your OrangeFox build. ^^

Sneilas said:
When you flash a new ROM, you need to format the userdata and the cache partitions.
EDIT:
Btw, i'm curious to know where you found your OrangeFox build. ^^
Click to expand...
Click to collapse
I believe I did format data, cache and dalvik cache as usual. Hm, will check again.
I forgot where I got the OrangeFox from. Might be nothing though.

kerelberel said:
I believe I did format data, cache and dalvik cache as usual. Hm, will check again.
I forgot where I got the OrangeFox from. Might be nothing though.
Click to expand...
Click to collapse
Btw, i do not recommand to flash unofficial images if the maintainer not released it's device tree on GitHub and not linked it on his thread.
We can't know what's inside the recovery.
The recovery can be infected by a malicious code.

Sneilas said:
When you flash a new ROM, you need to format the userdata and the cache partitions.
EDIT:
Btw, i'm curious to know where you found your OrangeFox build. ^^
Click to expand...
Click to collapse
So I made sure to format everything this time. But because I am stoopid I then accidentally sideloaded a MIUI ROM instead of Evolution. I copy/pasted the wrong file name in the cmd window, lol. I was surprised to see the Evolution logo after rebooting, so I got the ROM I wanted by accidentally flashing the other one.
Do I have MIUI on one partition and Evolution on the other? Is that even possible?

kerelberel said:
So I made sure to format everything this time. But because I am stoopid I then accidentally sideloaded a MIUI ROM instead of Evolution. I copy/pasted the wrong file name in the cmd window, lol. I was surprised to see the Evolution logo after rebooting, so I got the ROM I wanted by accidentally flashing the other one.
Do I have MIUI on one partition and Evolution on the other? Is that even possible?
Click to expand...
Click to collapse
From here, i recommand you to ask the maintainer of the Evolution X ROM of your device.
Send him your device infos (code name, processor, etc...).
If you can't access to these info on from phone, contact the reseller of your phone.
Maybe your specific device is not compatible with the ROM.
I'm not enough experienced to help you more.

I don't know if twrp works on veux.
I flashed the boot.img and vendor_boot.img provided by the custom ROM.
The custom ROM was updated using the sideload in recovery mode.
It must be unlocked. USB debug doesn't matter.

Sneilas said:
From here, i recommand you to ask the maintainer of the Evolution X ROM of your device.
Send him your device infos (code name, processor, etc...).
If you can't access to these info on from phone, contact the reseller of your phone.
Maybe your specific device is not compatible with the ROM.
I'm not enough experienced to help you more.
Click to expand...
Click to collapse
I'm fine now, the ROM works, afterwards I also installed Magisk successfully so TWRP works as expected too.
osebee said:
I don't know if twrp works on veux.
I flashed the boot.img and vendor_boot.img provided by the custom ROM.
The custom ROM was updated using the sideload in recovery mode.
It must be unlocked. USB debug doesn't matter.
Click to expand...
Click to collapse
It does, the one I linked in my first post is the one from this specific subforum.
If you need help you can PM me.

Seems like you've managed to fix the problem, and USB debugging only works when you're booted inside the rom, it doesn't do anything in recovery/fastboot.

kerelberel said:
I'm fine now, the ROM works, afterwards I also installed Magisk successfully so TWRP works as expected too.
It does, the one I linked in my first post is the one from this specific subforum.
If you need help you can PM me.
Click to expand...
Click to collapse
Oh ok, i thought you still had problems. ^^

Ritik17 said:
Seems like you've managed to fix the problem, and USB debugging only works when you're booted inside the rom, it doesn't do anything in recovery/fastboot.
Click to expand...
Click to collapse
USB debugging works in some stock/custom recoveries, but in stock recoveries it is limited to sideloading updates signed by the device manufacturer.