Database Info

[SOLVED] TWRP 3.0.2 bootloop

Hello everyone.
I had a problem flashing TWRP on my Google Nexus 5, or better the problem comes when I try to enter the recovery.
I followed this pattern from stock android 6.0.1 with august security patch:
1) unlock bootloader
2) downloaded lastest TWRP (3.0.2 hammerhead) recovery from the official website
3) flash it with "fastboot flash recovery recovery.img"
Until this point everything's alright but then when I unplug my phone from the laptop and click on enter recovery something strange happens.
I can see the TWRP boot image but as soon as I go in I see tons of errors related to "cannot mount ..." and some partitions name like /data, /cache, and then starts the bootloop without let me any chance to do something. Sorry but I can't see every error beacuse this happen too fast.
Any idea on what is going on?
I've tried the TWRP 3.0.1 but is the same shuold I go down or maybe I have to change it beacuse of compatibily issues with the monthly patches?
Thank you for your help, I hope I explained my problem clearly.

After unlocking the bootloader, phone wipe all data? Did you reboot after unlocking bootloader?

audit13 said:
After unlocking the bootloader, phone wipe all data? Did you reboot after unlocking bootloader?
Click to expand...
Click to collapse
No I've just unlocked and then tryied to flash the recovery without wipe.
But data is already wiped by unlocking the bootloader isn't it?
Anyway thanks for your reply as soon as I can I'll try what you have written.

Yes, the data should be automatically wiped. Try TWRP 2.87. If the phone still doesn't boot into TWRP, reflash stock recovery, flash userdata.img, immediately boot into stock recovery using the button combo without rebooting, perform a factory wipe, reboot into fastboot, and flash TWRP again.

audit13 said:
Yes, the data should be automatically wiped. Try TWRP 2.87. If the phone still doesn't boot into TWRP, reflash stock recovery, flash userdata.img, immediately boot into stock recovery using the button combo without rebooting, perform a factory wipe, reboot into fastboot, and flash TWRP again.
Click to expand...
Click to collapse
Thank you so much for telling me to flash the 2.8.7, i've choosen the 2.8.7.1 without success (it did't flash i don't know why) but then after another wipe all I've flashed the 2.8.7.0 and it seems to work.
The only thing I would like to ask now is: I'm going to flash superSU and elementalX over stock AOSP (I don't want custom ROM for now) and can this recovery cause problem because of it is not the last update?
Thank you again for the answer!

I have not tried 2.87 with Elemental X. The only way to determine whether it will work would be to try it. I recommend creating a nandroid backup before flashing Elemental so you can restore if something goes wrong.

TWRP Restore problem
Hi, I have an issue with the resotre of TWRP...
Here's what I did:
-Downloaded the latest OTA image https://developers.google.com/android/nexus/ota
-Downloaded latest SuperSU http://download.chainfire.eu/supersu-stable
-Downloaded latest ElementalX http://elementalx.org/devices/nexus-5/
-reboot to TWRP
Choose OTA, then SuperSU, then ElementalX
Luunch the restore..
And my screen is "blocked" from 5 hours on Install Zip 1 of 3.
"blocked" means doesn't move to the Zip2 but the clock is moving... the screen is locking itself after few seconds and I am able to unlock it...
Any idea how to exit properly ?

I have rebooted...deleted all my music... (I think that the issue may come from insufficient disk space) and relaunched...
Will see...

download Nexus Root Toolkit-type in google Nexus Root Toolkit - and watch from yuotoube how it work's
good luck

hunter-dz said:
download Nexus Root Toolkit-type in google Nexus Root Toolkit - and watch from yuotoube how it work's
good luck
Click to expand...
Click to collapse
My N5 was already rooted... and it's the second time that I update the OTA using directly TWRP... and for the August patch it has worked fine.
I don't know what's happen now...

kevtuning said:
My N5 was already rooted... and it's the second time that I update the OTA using directly TWRP... and for the August patch it has worked fine.
I don't know what's happen now...
Click to expand...
Click to collapse
Download thé nrt and i Will teach how to root ur n5
And type in Google nrt n5 xda

audit13 said:
I have not tried 2.87 with Elemental X. The only way to determine whether it will work would be to try it. I recommend creating a nandroid backup before flashing Elemental so you can restore if something goes wrong.
Click to expand...
Click to collapse
Now I can confirm that I was able to flash the lastest SuperSU and ElementalX with TWRP 2.8.7.0 without any problem, so thank you again for your help.

kevtuning said:
Hi, I have an issue with the resotre of TWRP...
Here's what I did:
-Downloaded the latest OTA image https://developers.google.com/android/nexus/ota
-Downloaded latest SuperSU http://download.chainfire.eu/supersu-stable
-Downloaded latest ElementalX http://elementalx.org/devices/nexus-5/
-reboot to TWRP
Choose OTA, then SuperSU, then ElementalX
Luunch the restore..
And my screen is "blocked" from 5 hours on Install Zip 1 of 3.
"blocked" means doesn't move to the Zip2 but the clock is moving... the screen is locking itself after few seconds and I am able to unlock it...
Any idea how to exit properly ?
Click to expand...
Click to collapse
Hi, I've have successfully installed the last OTA update but not with zip file, instead I downloaded the factory image and flashed with fastboot boot.img and system.img (also vendor.img if you have one) then rebooted into TWRP and installed the lastest ElementalX and SuperSU.
I'm not sure but I think that factory image zip file are not installable via recovery but only with the flash-all that comes with them. This script use fastboot to flash everything you need of the factory image
You can find this procedure on the ElementalX website, here is the link hope it can help out: http://elementalx.org/how-to-install-android-monthly-security-updates/

Finally... I installed CM13 and ElementalX... in some minutes ...
I suppose the the problem was in my zip file...

In need of help! TWRP!

first some back story:
it's been a long time since i did a lot of rooting so i lost a lot of knowledge.
I got the phone close to release in the EU.
There was only BETA stage twrp at the time.
So i flashed this unstable twrp and rooted with magisk.
And i run stock Oxy Rom.
But the main problem is, whenever i boot into recovery, twrp ask me for a password. (i have none) so i press continue.
And it then ask for unmodified system partition. (not sure what to select here)
But when i swipe to allow modification, i can't find the root of the phone? i cannot find the download folder where i flash updates or other modified apk's.
It's all just numbers and random letter. i have no idea on how to proceed or how to update twrp safely without falling into boot loop and other problems.
Some help would be appriciated. Thank you.

saitek1911 said:
first some back story:
it's been a long time since i did a lot of rooting so i lost a lot of knowledge.
I got the phone close to release in the EU.
There was only BETA stage twrp at the time.
So i flashed this unstable twrp and rooted with magisk.
And i run stock Oxy Rom.
But the main problem is, whenever i boot into recovery, twrp ask me for a password. (i have none) so i press continue.
And it then ask for unmodified system partition. (not sure what to select here)
But when i swipe to allow modification, i can't find the root of the phone? i cannot find the download folder where i flash updates or other modified apk's.
It's all just numbers and random letter. i have no idea on how to proceed or how to update twrp safely without falling into boot loop and other problems.
Some help would be appriciated. Thank you.
Click to expand...
Click to collapse
Boot to bootloader, flash original boot img than follow the guide to flash original twrp

Hitman478™ said:
Boot to bootloader, flash original boot img than follow the guide to flash original twrp
Click to expand...
Click to collapse
and which of my problems does this solve?

First of all flash official TWRP now. Makes no sense to use the unofficial version because its not stable.
Enter PW -> decrypt data for TWRP
No PW -> hieroglyphs

I successfully used official twrp, version 3.2.2 and then did a "format data" and then used fastboot again to install the full rom.

Kollachi said:
First of all flash official TWRP now. Makes no sense to use the unofficial version because its not stable.
Enter PW -> decrypt data for TWRP
No PW -> hieroglyphs
Click to expand...
Click to collapse
ok i figured it out, added a password. and now it shows correct folder names etc. thanks.

saitek1911 said:
first some back story:
it's been a long time since i did a lot of rooting so i lost a lot of knowledge.
I got the phone close to release in the EU.
There was only BETA stage twrp at the time.
So i flashed this unstable twrp and rooted with magisk.
And i run stock Oxy Rom.
But the main problem is, whenever i boot into recovery, twrp ask me for a password. (i have none) so i press continue.
And it then ask for unmodified system partition. (not sure what to select here)
But when i swipe to allow modification, i can't find the root of the phone? i cannot find the download folder where i flash updates or other modified apk's.
It's all just numbers and random letter. i have no idea on how to proceed or how to update twrp safely without falling into boot loop and other problems.
Some help would be appriciated. Thank you.
Click to expand...
Click to collapse
U have corrupted u r data partation u have to factory reset along with wiping internal storage and then transfer u r rom File through MTP in sd card of phone and then flash rom.
Or u can flash fastboot flashable rom via fastboot mode.
Then install your official twrp via fastboot mide after installing rom.
Now twrp will detect all data from sd card

pankspoo said:
U have corrupted u r data partation u have to factory reset along with wiping internal storage and then transfer u r rom File through MTP in sd card of phone and then flash rom.
Click to expand...
Click to collapse
Thank you, all i did was add a four digit code when twrp asked me for a password. now the folders are showing up correctly. not just random numbers and letters.
still need to update twrp safely. can i flash a new twrp within twrp or do i need to update via computer?

saitek1911 said:
Thank you, all i did was add a four digit code when twrp asked me for a password. now the folders are showing up correctly. not just random numbers and letters.
still need to update twrp safely. can i flash a new twrp within twrp or do i need to update via computer?
Click to expand...
Click to collapse
U can directly flash new twrp installer in current recovery no problem

saitek1911 said:
and which of my problems does this solve?
Click to expand...
Click to collapse
All of your problems i presume

Can Anyone help me, please? I have somehow the same problem. The phone literally itself without doing anything started doing a download(odin) mode loop. So I deleted data, dalvik, cache, system partitions without internal storage since it has very very important files for me and a lot of projects for the university!!! and before and after the folders in internal storage in twrp shows as random numbers and letters. I don't know why since when the phone was working normally I was protecting it by fingerprint and a password. And when I installed a stock ROM after it without wiping the internal storage. The storage is showing in negative. If anyone can help me this would be super appreciated and helpful. Thank you!

Hitman478™ said:
Boot to bootloader, flash original boot img than follow the guide to flash original twrp
Click to expand...
Click to collapse
Can you help please?

Madara818181 said:
Can Anyone help me, please? I have somehow the same problem. The phone literally itself without doing anything started doing a download(odin) mode loop. So I deleted data, dalvik, cache, system partitions without internal storage since it has very very important files for me and a lot of projects for the university!!! and before and after the folders in internal storage in twrp shows as random numbers and letters. I don't know why since when the phone was working normally I was protecting it by fingerprint and a password. And when I installed a stock ROM after it without wiping the internal storage. The storage is showing in negative. If anyone can help me this would be super appreciated and helpful. Thank you!
Click to expand...
Click to collapse
If it is already showing folders with random file names in the internal storage it means it needs to format data (to remove file encryption) which deletes all files in the internal storage.
Don't wipe system because it removes your OS.
Always secure backup before messing your device.
Hitman478™ said:
Boot to bootloader, flash original boot img than follow the guide to flash original twrp
Click to expand...
Click to collapse
You may try this boot.img just rename to boot.img only.
Credits to RR10 TG channel by Enzo #CatGang.

tiga016 said:
If it is already showing folders with random file names in the internal storage it means it needs to format data (to remove file encryption) which deletes all files in the internal storage.
Don't wipe system because it removes your OS.
Always secure backup before messing your device.
You may try this boot.img just rename to boot.img only.
Credits to RR10 TG channel by Enzo #CatGang.
Click to expand...
Click to collapse
Thanks Man. All my university stuff is in the phone's internal storage so wiping it is no no for me and I need the files today!!! I flashed the boot.img file you attached using TWRP but now the phone is in a boot loop and it did not solve anything!!! Sorry for this but what the f**k should I do man. All my important files are on the phone!!!

Madara818181 said:
Thanks Man. All my university stuff is in the phone's internal storage so wiping it is no no for me and I need the files today!!! I flashed the boot.img file you attached using TWRP but now the phone is in a boot loop and it did not solve anything!!! Sorry for this but what the f**k should I do man. All my important files are on the phone!!!
Click to expand...
Click to collapse
Sorry I thought you are also literally same issues with OP but then it's not. Are you able to reboot to twrp? And what is the whole story of you device? I mean if you are rooted, what ROM you came from and all that you did before the issues occur. And did you tried to switch slot? Since you wiped everything with system included then you have no OS installed. Did you tried to flash OS via OTG? Or flash via fastboot.

I flashed another os without deleting the internal storage but the storage is now showing in negative values. Story is The phone literally itself without doing anything started doing a download(odin) mode loop. So I deleted data, dalvik, cache, system partitions without internal storage since it has very very important files for me and a lot of projects for the university!!! and before and after the folders in internal storage in twrp shows as random numbers and letters. I don't know why since when the phone was working normally I was protecting it by fingerprint and a password. And when I installed a stock ROM after it without wiping the internal storage. The storage is showing in negative and yes I can still boot into twrp

tiga016 said:
Sorry I thought you are also literally same issues with OP but then it's not. Are you able to reboot to twrp? And what is the whole story of you device? I mean if you are rooted, what ROM you came from and all that you did before the issues occur. And did you tried to switch slot? Since you wiped everything with system included then you have no OS installed. Did you tried to flash OS via OTG? Or flash via fastboot.
Click to expand...
Click to collapse
This is the story

Madara818181 said:
This is the story
Click to expand...
Click to collapse
I know that but it seems incomplete. It did not mention what I ask recently. It is always a need for detailed story.

Teclast M89 problem installing TWRP

Hi folks. As the title suggest I'm having problems installing TWRP recovery on teclast M89 tablet. I've tried a few different tutorials with no success. When I do it with fastboot it says that its installed, after that when I try to reboot the device, I'm stuck in bootloop. I've tried to do it a few times and its always the same problem. Does anyone have a solution? Thanks.

Hello, the same for me with my M89, I'm going crazy.... Help us please!!!! Thanks!!!

Teclast M89 TWRP 3.3.1
Teclast M89 TWRP 3.3.1
TWRP 3.3.1 for Teclast M89
The archive includes:
ZIP file for flashing via stock recovery
IMG file for flashing via fastboot
TWRP source code
Teclast M89 uses well-known firmware signature Android keys (test keys), that's why you can flash TWRP without unlocking the bootloader and erasing user data.
Installation instruction is inside the archive.
https://www.androidfilehost.com/?fid=6006931924117883832
My small Teclast M89 website: https://teclast-m89.neocities.org/

M89 TWRP Worked!
ValdikSS said:
Teclast M89 TWRP 3.3.1
TWRP 3.3.1 for Teclast M89
The archive includes:
ZIP file for flashing via stock recovery
IMG file for flashing via fastboot
TWRP source code
Teclast M89 uses well-known firmware signature Android keys (test keys), that's why you can flash TWRP without unlocking the bootloader and erasing user data.
Installation instruction is inside the archive.
https://www.androidfilehost.com/?fid=6006931924117883832
Click to expand...
Click to collapse
This TWRP worked like a charm for me. I had already rooted via Magisk- but was really looking for a working TWRP for backing up before I really went crazy with mods.
Thanks so much!!

Jmlanner said:
This TWRP worked like a charm for me. I had already rooted via Magisk- but was really looking for a working TWRP for backing up before I really went crazy with mods.
Thanks so much!!
Click to expand...
Click to collapse
Make sure to backup nvram, nvdata, private partitions.

ValdikSS said:
Make sure to backup nvram, nvdata, private partitions.
Click to expand...
Click to collapse
Will do. I did bkk nvdata, will double check if I bkk privdata. again TK!

stuck
Hi, i tried this method but couldnt boot in system, only twrp all the time. after initial install this TWRP 3.3.1, it bootlooped in twrp but storage wasnt seen in pc, so i formatted data and restarted in twrp. from there it couldnt restart system anymore. actually i managed to flash magisk 19.3 . i flased another version of twrp 3.2.3 that seemed to work fine, to see if it was the version, and it bootloops (restarts until logo) all the time. Any hint please?
It says in little print "your device now unlocked...your device will boot in 5 seconds" but restart. Cant get it into fastboot by volume up; unresponsive at all. just bootloops in logo.
Any help is very much appreciated. thanks

voland34 said:
Hi, i tried this method but couldnt boot in system, only twrp all the time. after initial install this TWRP 3.3.1, it bootlooped in twrp but storage wasnt seen in pc, so i formatted data and restarted in twrp. from there it couldnt restart system anymore. actually i managed to flash magisk 19.3 . i flased another version of twrp 3.2.3 that seemed to work fine, to see if it was the version, and it bootloops (restarts until logo) all the time. Any hint please?
It says in little print "your device now unlocked...your device will boot in 5 seconds" but restart. Cant get it into fastboot by volume up; unresponsive at all. just bootloops in logo.
Any help is very much appreciated. thanks
Click to expand...
Click to collapse
Hi
I think you are going to have to reflash the original Rom using SPFlahtool. Then you must install Magisk Manage on tabletr. Copy the boot image from the ROM files to Your phone. Then use Magisk Manager to Patch the copied boot image. Transfer modified boot image to PC. Use fastboot to flash modified boot image back onto the tablet. The long and the short of it is - you need to find a way to patch the boot image with Magisk before any TWRP will work.

Right. The problem was accesing the tablet enough time as it stayed connected and recognized by pc only 3-5 secs, and then permanent unresponsive through buttons, but i used then sp flash to just flash boot, then preloader, then recovery from stock at every reboot. From there i could turn it off, It got out of the loop, and accesible to reflash whole stock rom. In the end i only flashed magisk through fastboot, as twrp is not so useful to me as no custom rom, so better no risks.
Thanks for your reply though

voland34 said:
Right. The problem was accesing the tablet enough time as it stayed connected and recognized by pc only 3-5 secs, and then permanent unresponsive through buttons, but i used then sp flash to just flash boot, then preloader, then recovery from stock at every reboot. From there i could turn it off, It got out of the loop, and accesible to reflash whole stock rom. In the end i only flashed magisk through fastboot, as twrp is not so useful to me as no custom rom, so better no risks.
Thanks for your reply though
Click to expand...
Click to collapse
I am glad you got your tablet running again. I had originally started out with just Magisk as root also. I do like to have a working TWRP for backing up though. You should be able now to flash the above mentioned TWRP now via SpFlashtool or fastboot.

voland34 said:
Hi, i tried this method but couldnt boot in system, only twrp all the time. after initial install this TWRP 3.3.1, it bootlooped in twrp but storage wasnt seen in pc, so i formatted data and restarted in twrp. from there it couldnt restart system anymore. actually i managed to flash magisk 19.3 . i flased another version of twrp 3.2.3 that seemed to work fine, to see if it was the version, and it bootloops (restarts until logo) all the time. Any hint please?
It says in little print "your device now unlocked...your device will boot in 5 seconds" but restart. Cant get it into fastboot by volume up; unresponsive at all. just bootloops in logo.
Any help is very much appreciated. thanks
Click to expand...
Click to collapse
It seems OEM unlock fills "para" partition with some data which forces it to boot into recovery. Stock recovery reads this data and perform data partition wipe or something similar, but TWRP does not handle this data and you get a boot loop. You can fix that by cleaning "para" partition. Execute the following command while booted into TWRP, either from TWRP terminal itself or from adb shell:
Code:
dd if=/dev/zero of=/dev/block/platform/mtk-msdc.0/11230000.MSDC0/by-name/para

ValdikSS said:
It seems OEM unlock fills "para" partition with some data which forces it to boot into recovery. Stock recovery reads this data and perform data partition wipe or something similar, but TWRP does not handle this data and you get a boot loop. You can fix that by cleaning "para" partition. Execute the following command while booted into TWRP, either from TWRP terminal itself or from adb shell:
Code:
dd if=/dev/zero of=/dev/block/platform/mtk-msdc.0/11230000.MSDC0/by-name/para
Click to expand...
Click to collapse
Ok, i'll try. Thanks!

Does anybody know if this guide also works for the new Teclast M89 PRO-model???

gizmo862 said:
Does anybody know if this guide also works for the new Teclast M89 PRO-model???
Click to expand...
Click to collapse
No, most probably it won't. PRO model has different SoC/CPU.

gizmo862 said:
Does anybody know if this guide also works for the new Teclast M89 PRO-model???
Click to expand...
Click to collapse
No. It won't. I bricked my ****ing tablet. It refuses to reboot once it's unlocked because (as the screen say) it is now untrusted. There is no way to relock the bootloader again and the the tablet is stuck in a bootloop.
Teclast is ****.

Hello i'm new in XDA, i have this tablet althougth i can't conect the hdmi port to the tv, the screen keep in black, i think it's because of the display format (4:3) can the root solve this problem?
Thank You!!

w1nst0n sm1th said:
No. It won't. I bricked my ****ing tablet. It refuses to reboot once it's unlocked because (as the screen say) it is now untrusted. There is no way to relock the bootloader again and the the tablet is stuck in a bootloop.
Teclast is ****.
Click to expand...
Click to collapse
The bootloop is not because you've unlocked the bootloader, but most probably because the firmware is designed to perform userdata partition setup in the recovery upon first boot, and you don't have stock recovery, that's why it can't finish formatting procedure.
This could be fixed by flashing stock recovery and booting once.
You can ask for a firmware from Teclast (I used to ask them on vkontakte because they didn't respond my mails), they will provide it.
OR you can write zeros to "para" partition using fastboot, it should do the trick too.
---------- Post added at 16:58 ---------- Previous post was at 16:56 ----------
Edgaralanmx said:
Hello i'm new in XDA, i have this tablet althougth i can't conect the hdmi port to the tv, the screen keep in black, i think it's because of the display format (4:3) can the root solve this problem?
Thank You!!
Click to expand...
Click to collapse
Try to unplug/plug again HDMI cable several times. It seems that the HDMI controller or drivers are buggy.
To change the resolution I use "SecondScreen" software (requires root).

Hi guys,
I´m looking for a working rooting method for my Teclast M89 Pro model ??
Any idea ?? What about the "One Click Root" Program ???
Thank´s a lot

The device was trying to root.
I get the following information when restarting:
orange state
the device has been unlocked and can't be trusted
your device will boot in 5 seconds
Click to expand...
Click to collapse
When I try TWRP via sideload or recovery menu I get the following:
Supported API:3
-- Install /sdcard/teclast_m89_twrp_311.zip ...
Finding update packacke ...
Opening update package ...
Verifying update package ...
Update package verification took 0.5 s (result 0).
Installing update ...
E:Failed to find META-INF/com/android/metadata in update package.
Installing Teclast M89 TWRP Recovery
script succeeded: result was [1.000000]
Install from SD Card complete.
Click to expand...
Click to collapse
But TWRP is not installed.
Where is the problem?

kumpi said:
But TWRP is not installed.
Where is the problem?
Click to expand...
Click to collapse
Are you trying to enter recovery right after flashing it, without booting the OS first? I think you need do enter TWRP right after flashing it.

TWRP asking Dcrypt password

I didn't do any password or tried to do encryption for my data, because of that reason i cant see any files on twrp but i have no issues on booting into system, what i cant do is not able to backup files and i cant see any files if i look through twrp. How to get rid of this issues please

Maybe you set before a password when you firs setup the phone, but even if you remove it later, i think in the twrp it still needs it

use USB-C stick, save to it twrp instalation zip, in running twrp change storage source to USB, flash twrp from USB, then reboot to recovery
this happened to me after the last update

You can try to disable the password from the phone settings & then reboot in twrp, it won't ask for the password.
Sent from my ONEPLUS A6003 using Tapatalk

jabs said:
use USB-C stick, save to it twrp instalation zip, in running twrp change storage source to USB, flash twrp from USB, then reboot to recovery
this happened to me after the last update
Click to expand...
Click to collapse
i did same already .still not solved
sam180881 said:
You can try to disable the password from the phone settings & then reboot in twrp, it won't ask for the password.
Click to expand...
Click to collapse
i didnt use any password or lock screen

Chinaroad said:
Maybe you set before a password when you firs setup the phone, but even if you remove it later, i think in the twrp it still needs it
Click to expand...
Click to collapse
jabs said:
use USB-C stick, save to it twrp instalation zip, in running twrp change storage source to USB, flash twrp from USB, then reboot to recovery
this happened to me after the last update
Click to expand...
Click to collapse
sam180881 said:
You can try to disable the password from the phone settings & then reboot in twrp, it won't ask for the password.
Sent from my ONEPLUS A6003 using Tapatalk
Click to expand...
Click to collapse
Suppose if we swt password or lock screen the entire data on TWRP will Encrpted?

Yep

Chinaroad said:
Yep
Click to expand...
Click to collapse
Then what is benifit of flashing no-dm verity zip?

i never tried it, but as i know you need to flash that zip to decrypt the phone each time you flash a rom , not only one, ( that's what i know, and as i told you i never tried it)

@alwynjoshy
you need a new fresh TWRP installation, if you tried my procedure via USB-C and didn't work, install twrp * .img from your computer via fastboot procedure

Just boot into UI then remove any security options like face lock, fingerprint, pattern And pin.

jabs said:
@alwynjoshy
you need a new fresh TWRP installation, if you tried my procedure via USB-C and didn't work, install twrp * .img from your computer via fastboot procedure
Click to expand...
Click to collapse
Even after flashing dm verity zip am I able to use screenlock or pin without being effected of encryption

Problem with flashing custom ROM (error 255)

Hey guys,
after searching through different websites and guides you are my last resort to get a custom ROM running on my Redmi S2.
Everytime i try to flash a custom ROM i get the error 255. Here is what i tried until now (bootloader is unlocked):
- flashing twrp(twrp-3.2.1-0-ysl) to recovery using fastboot
- wiping phone (first wipe to disable encryption since miui puts some kind of password on the hard drive that i dont know, second wipe to ensure partitions are clean for new OS)
- mounting phone to pc to transfer OS image (tried Lineage and Havoc, both modified for S2 (ysl version)) and GApps
- finally, installing OS zip (after which i get error message 255, telling me that twrp wasnt able to install the zip file)
please help me out, ask away if something's not clear

flying_shitnugget said:
Hey guys,
after searching through different websites and guides you are my last resort to get a custom ROM running on my Redmi S2.
Everytime i try to flash a custom ROM i get the error 255. Here is what i tried until now (bootloader is unlocked):
- flashing twrp(twrp-3.2.1-0-ysl) to recovery using fastboot
- wiping phone (first wipe to disable encryption since miui puts some kind of password on the hard drive that i dont know, second wipe to ensure partitions are clean for new OS)
- mounting phone to pc to transfer OS image (tried Lineage and Havoc, both modified for S2 (ysl version)) and GApps
- finally, installing OS zip (after which i get error message 255, telling me that twrp wasnt able to install the zip file)
please help me out, ask away if something's not clear
Click to expand...
Click to collapse
change your recovery..

Baim alif said:
change your recovery..
Click to expand...
Click to collapse
Mind elaborating? What do you mean exactly?

flying_shitnugget said:
Mind elaborating? What do you mean exactly?
Click to expand...
Click to collapse
use this recovery
https://files.orangefox.download/OrangeFox-Stable/ysl/OrangeFox-R10.0-1-Stable-ysl.zip

Baim alif said:
use this recovery
https://files.orangefox.download/OrangeFox-Stable/ysl/OrangeFox-R10.0-1-Stable-ysl.zip
Click to expand...
Click to collapse
so... i first tried taking the recovery.img out of the zip and flashing it via fastboot, didnt worked. after that i tried first flashing my old twrp and then (after wiping) installing the whole zip. the install finished successfully, sayed it will restart to recovery in 5 seconds... aaaand got stuck on the android screen. now it wont boot to recovery at all anymore, unless i flash the old twrp again. suggestions?

flying_shitnugget said:
so... i first tried taking the recovery.img out of the zip and flashing it via fastboot, didnt worked. after that i tried first flashing my old twrp and then (after wiping) installing the whole zip. the install finished successfully, sayed it will restart to recovery in 5 seconds... aaaand got stuck on the android screen. now it wont boot to recovery at all anymore, unless i flash the old twrp again. suggestions?
Click to expand...
Click to collapse
try to boot recovery with power button and volume up

Baim alif said:
try to boot recovery with power button and volume up
Click to expand...
Click to collapse
yes, that's what i did. i also tried booting into from fastboot and still nothing.

flying_shitnugget said:
yes, that's what i did. i also tried booting into from fastboot and still nothing.
Click to expand...
Click to collapse
hmmm... try this bro..
https://androidfilehost.com/?fid=6006931924117927913

flying_shitnugget said:
yes, that's what i did. i also tried booting into from fastboot and still nothing.
Click to expand...
Click to collapse
Try this, you have to flash first this in fastboot https://files.orangefox.download/OrangeFox-Beta/ysl/ the R10.0-1 RC1 .img file
And THEN flash this https://orangefox.download/en/device/ysl once you are in the recovery.
Then it worked for me, finally, hope this helps.

celephrn said:
Try this, you have to flash first this in fastboot https://files.orangefox.download/OrangeFox-Beta/ysl/ the R10.0-1 RC1 .img file
And THEN flash this https://orangefox.download/en/device/ysl once you are in the recovery.
Then it worked for me, finally, hope this helps.
Click to expand...
Click to collapse
so i tried this approach. i first installed how you told me to (orangefox R10.0-1 RC1 .img first), but factory reset nor installing the second recovery img worked because of the encryption miui puts on the phone. So i flashed twrp, wiped memory, flashed first orange fox img and from then installed the second img (as a zip). until here everything worked, orange fox told me that he's going to reboot to new recovery -- and i got stuck on the boot logo again. :c

flying_shitnugget said:
so i tried this approach. i first installed how you told me to (orangefox R10.0-1 RC1 .img first), but factory reset nor installing the second recovery img worked because of the encryption miui puts on the phone. So i flashed twrp, wiped memory, flashed first orange fox img and from then installed the second img (as a zip). until here everything worked, orange fox told me that he's going to reboot to new recovery -- and i got stuck on the boot logo again. :c
Click to expand...
Click to collapse
Did you flash the firmware? https://github.com/XiaomiFirmwareUpdater/firmware_xiaomi_ysl/releases/tag/stable-16.03.2020
Other thing you could try is flash the other .img files from https://files.orangefox.download/OrangeFox-Beta/ysl/ and the flash in there the same .zip file you did as before.

celephrn said:
Did you flash the firmware? https://github.com/XiaomiFirmwareUpdater/firmware_xiaomi_ysl/releases/tag/stable-16.03.2020
Other thing you could try is flash the other .img files from https://files.orangefox.download/OrangeFox-Beta/ysl/ and the flash in there the same .zip file you did as before.
Click to expand...
Click to collapse
im currently on MIUI V.10.3.1.0.OEFMIXM | Stable 654M, is it important to flash newer firmware?

flying_shitnugget said:
im currently on MIUI V.10.3.1.0.OEFMIXM | Stable 654M, is it important to flash newer firmware?
Click to expand...
Click to collapse
Could solve the issue, I'd give it a shot!

celephrn said:
Could solve the issue, I'd give it a shot!
Click to expand...
Click to collapse
i suppose you flash it using MiFlash right? If so, i have a problem with flashing new roms using it because my Mi account isnt allowed to do that, i unlocked the bootloader using a tool (dont know if this has something to do with the custom rom problem)

flying_shitnugget said:
i suppose you flash it using MiFlash right? If so, i have a problem with flashing new roms using it because my Mi account isnt allowed to do that, i unlocked the bootloader using a tool (dont know if this has something to do with the custom rom problem)
Click to expand...
Click to collapse
As long as the bootloader is unlocked it should be fine. And no, you should flash the firmware just as you would flash the rom, i. e. from OrangeFox Recovery.

celephrn said:
As long as the bootloader is unlocked it should be fine. And no, you should flash the firmware just as you would flash the rom, i. e. from OrangeFox Recovery.
Click to expand...
Click to collapse
so i flashed the firmware as you said, now neither orangefox or twrp throw me the error "unable to locate storage device", i cant mount the storage to the pc and cant copy the custom rom stuff as well

celephrn said:
As long as the bootloader is unlocked it should be fine. And no, you should flash the firmware just as you would flash the rom, i. e. from OrangeFox Recovery.
Click to expand...
Click to collapse
UPDATE: i finally ****ing did it. So here are the steps that i took (incase anyone has to go through this **** as well)
1. flash MIUI on mobile device using MiFlash (at least i did this by shorting 2 pins on the back)
2. (VERY IMPORTANT!!!) instantly boot to fastboot using Power button + Volume down. this has to be before android starts setting up the phone
3. flash recovery with the image that celephrn provided in this thread
4.boot to recovery by holding Volume up + Power button
5. install the miui update that celephrn provided in this thread
6. reboot to recovery
7. install orange recovery zip that celephrn provided in this thread (phone reboots to recovery)
8. now you can reboot to system (Do NOT (!!!) set the phone up, just let it work its things until you see the MIUI setup screen)
9. Now, finally you can dirty flash your custom rom (and GApps)
10. after flashing the new rom android will throw you alot of errors so you will have to wipe Dalvik/Cache, System, Data and Internal Storage.
11. now you can flash your Rom clean and you're good to go
(huge thanks to celephrn, helped me out after me struggling for a few good weeks with this damn phone)

Baim alif said:
use this recovery
https://files.orangefox.download/OrangeFox-Stable/ysl/OrangeFox-R10.0-1-Stable-ysl.zip
Click to expand...
Click to collapse
bro please help me i have the same issue error 255 on 3.2.1-0 ysl twrp.please help

Farrellclay said:
bro please help me i have the same issue error 255 on 3.2.1-0 ysl twrp.please help
Click to expand...
Click to collapse
so far, what have you done