Database Develop

Can't load recovery after flashing Stock image 5.1.1

Hi all-so I decided to flash back to stock since my 32GB Nexus was down to about 14GB from flashing ROMS and such.Everything seems to have gone smoothly however when I try the oem unlock command I am told that the device is already unlocked.I proceeded to root and then I tried to flash TWRP but I get permission denied.
Also,my Play Store just crashed when I try and type in an app to search for.
The question is-how do I know which factory image is right for my device?
There are a number of 5.1.1 images,I selected the one marked for all carriers except T-Mobile.Could I have selected the wrong image to be causing some of these problems?
Or should I just go ahead and jump up to 6.0.1-there is only 1 image for that release.
I would't think the image mattered that much but something is wrong here.
I got the phone last week from the Amazon sale and I activated it no problem on Verizon and flashed several ROMS no issue.
Advice is much appreciated.

I really don't understand why anyone would flash to an old version of a ROM. I appreciate that people have different tastes (e.g. don't like material design) or perceive different characteristics (e.g. better battery life) but in general each new ROM brings advantages, stability, security, improvements, so why stick with an old one when you can have new?
Me, I'd definitely go for a full clean install of MMB29K.
And if you insist on root, be aware of the issues with Marshmallow - you need a different kernel (Elementalx is popular) or alternatively flash TWRP and install Chainfire's SuperSU 2.62. I say 2.62 rather than 2.65 because there are numbers of people reporting that root doesn't work with 2.65, which isn't the case with 2.62, and from personal experience 2.62 works absolutely fine on my 6.0.1 N6.

dahawthorne said:
I really don't understand why anyone would flash to an old version of a ROM. I appreciate that people have different tastes (e.g. don't like material design) or perceive different characteristics (e.g. better battery life) but in general each new ROM brings advantages, stability, security, improvements, so why stick with an old one when you can have new?
Me, I'd definitely go for a full clean install of MMB29K.
And if you insist on root, be aware of the issues with Marshmallow - you need a different kernel (Elementalx is popular) or alternatively flash TWRP and install Chainfire's SuperSU 2.62. I say 2.62 rather than 2.65 because there are numbers of people reporting that root doesn't work with 2.65, which isn't the case with 2.62, and from personal experience 2.62 works absolutely fine on my 6.0.1 N6.
Click to expand...
Click to collapse
Thanks for the detailed response. I was running 5.1 initially because that is what the phone booted with and I like full-featured ROMS like BlissPop. I guess I'll give 6.0.1 a whirl.It just seemed like it was too new to be rock solid. I had as many features on my old S3 running 4.4.2 as I have seen since then if not more actually. I am curious about Google Now On Tap however.
Hopefully this gets me fixed up.Cheers.

chiadrum said:
Hi all-so I decided to flash back to stock since my 32GB Nexus was down to about .......
Click to expand...
Click to collapse
It is possible that the issue is caused because you downgraded the bootloader by flashing 5.1.1.
Flash the complete latest stock 6.0.1 images.

Flashing 6.0.1 now. Both times the CMD window has showed me archive does not contain boot.sig and recovery.sig. I am guessing that is normal?
The 5.1.1 started working fine after an update all but I still couldn't install TWRP fyi.
Let's see how Marshmallow tastes!

The "does not contain boot.sig and recovery.sig" is standard. I have no idea why it continues to appear version after version, but it has no effect on the installation.

chiadrum said:
Flashing 6.0.1 now. Both times the CMD window has showed me archive does not contain boot.sig and recovery.sig.
Click to expand...
Click to collapse
Same on my N6 when flashing 6.0.1. When 6.0.1 is running, you can flash TWRP recovery in fastboot mode.

NLBeev said:
Same on my N6 when flashing 6.0.1. When 6.0.1 is running, you can flash TWRP recovery in fastboot mode.
Click to expand...
Click to collapse
Thanks guys.

chiadrum said:
Thanks guys.
Click to expand...
Click to collapse
Ok more strangeness.pPhone is working fine,no issues.However I am unable to unlock bootloader using the fastboot OEM unlock command.
The message is "Not supported command in current status".
Yes,OEM unlock is allowed in Dev Options.I tried turning that off in case the indicator was faulty and then I couldn't even attempt to unlock,immediate failure.
Tried this several times after reboots as well.
Build MMB29K.
Any ideas?

Would it be too simple an answer to say that it's because the phone is already unlocked? You couldn't install a new ROM with a locked bootloader.
I myself have been a bit surprised by the peremptory & derogatory comments of some of the very senior members in these forums when people ask what seem to be questions with obvious answers, and I'm beginning to see their point...
Still, I also recognise that an "easy" question is one that you know the answer to, and I don't want to put people off asking questions. Being knocked back myself several times hasn't stopped me asking.

That's actually a very good point.Perhaps the image came boitloader unlocked.I'll see if I can flash TWRP and install something. I haven't loaded any roms since the initial flash,I was following protocol to unlock,root and then flash.Appreciate the help.Sometimes obvious seems too easy.

chiadrum said:
That's actually a very good point.Perhaps the image came boitloader unlocked.I'll see if I can flash TWRP and install something. I haven't loaded any roms since the initial flash,I was following protocol to unlock,root and then flash.Appreciate the help.Sometimes obvious seems too easy.
Click to expand...
Click to collapse
Confirmed I am an idiot.Device is unlocked already. Wasn't expecting that.The people way smarter than me who prepared that image took care of it for me.

Not an idiot at all. Like I said, an easy question is one that you know the answer to. Experience counts...
It's not the image that is unlocked - it's the device. Once unlocked, you have to specifically lock it again, but it's neither simple nor a good idea. An unlocked device gives you a far better chance to recover from errors.

Got new One+ 3T Some questions

I have received today my new mobile 1+ 3t a3010
oxygen 4.1.3
where should i start ?
tweaking kernel, roms...
please refer me to the right threads
thanks in advance.

- Unlock bootloader first: https://forums.oneplus.net/threads/...wrp-root-nandroid-efs-backup-and-more.448149/
- Flash OOS 4.1.5 or the newest Openbeta (or Freedom OS if you understand what you do)
- if you need root: flash supersu or magisk
- if you want: Flash Kernel (ElementalX, Franco, Blu, Flash, etc)
- very optional: https://forum.xda-developers.com/oneplus-3/how-to/advanced-interactive-governor-tweaks-t3476589

How one decides to mod the phone (custom ROMs, kernels, etc.) is completely up to personal preferences and tastes. Everyone will give you a different answer to your questions, and many owners of this phone will never mod it at all, and be completely happy. Read up on existing threads, and you'll figure out what are the best options for you. There are also plenty of existing threads with suggestions and favorites regarding ROMs, etc. so no need to start another such discussion.
So really, my advice on where to start, is to read read read. Understand the methods and steps before you begin (and that goes with any of these devices). The previous answer had some good resources, for a start. And you'll find many more useful threads in the "Guides" forum section. My additional suggestion would be to know how to return to stock with the full zips: https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
Along similar lines (and in agreement with the prevous answer) I would recommend updating to latest OOS 4.1.5 or Open Beta, to ensure you are on the latest firmware and modem, before doing other mods.

Thank you both for great answers,
i did successfully bootloader unlocked and twrp flashed
Now which is oos 4.1.5 you talking about ?
like https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
and this https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
is ok to flash now ?

You posted the same thread twice. But yes, that is correct. You'll want the full zip from Post #2 of that thread. Then follow the instructions in Post #3, using second method, for users with TWRP. It also says for root users, but it's irrelevant whether you are rooted or not, as long as you have TWRP installed you'll need to use the full zip; as stated at the bottom of Post #3, if you use the OTA with TWRP, it will fail or you will soft brick!
Also, if you root, TWRP will stick (this is what I always do after flashing the updates). If you choose not to root after installing 4.1.5, you might find that TWRP is removed. But you might be able to avoid this by booting back to TWRP after installing 4.1.5, butbefore rebooting to OS. Otherwise, if you find TWRP is gone, just flash again using fastboot.

Tell me please,
can i flash custom kernel being on stock 3.1.5 with stock recovery?

Just stick with stock. LineageOS is kind of awful. Theres a million bugs that affect daily usage even on a perfect install and setup. Its just not worth it. I'd go with freedomOS CE 2.10. Very solid rom with nice extra options to remove useless google apps like photos and google music youtube and the like. It even allows magisk which is a fantastic rooting systemless method. I would also add the adblocked youtube module or app from a thread by Master_T. Just stick with basic rooting function and your experience will be superb. The more advanced you go with this phone the more prone to breaking something you get.

You were already advised how to mod the phone, back up in Post #2 above. I assume you mean locked bootloader along with stock recovery. I believe what you suggest won't work, and the stock recovery will not let you flash an unsigned zip. You need to unlock your bootloader and flash custom recovery TWRP. Then you can flash a custom kernel. But again, it's already been described by another back up on Post #2.
Also, I'm pretty sure you mean 4.1.5 (not 3.1.5), as you already stated the phone came with 4.1.3 (so 3.1.5 wouldn't make much sense). So please proofread before posting, to avoid confusion (and I was really confused by the number 3.1.5 at first).

Zenfone Go Oreo help

Hi someone with an account on 4dpa with 30 posts could please download this rom and share it here? I don't know Russian so it's impossible for me to write 30 posts.
I have a Zenfone Go (Z00VD) and the stock ROM it's terrible (crash in the camera, 1 Gigabyte of app space already full....)
In case you can't, could you provide an alternative ROM with as less bugs as possible?
Thank you
Original Thread 4pda
Translated Google

Guess we're on the same boat buddy. Have you tried the other ROMs on their forum like the nougat ones? They seem nice.
I personally prefer to use the RR 5.5.9 lollipop rom provided by 4pda since for some reason the nougat and marshmallow roms on their site just give me bootloops. It may be different for you though.

JustAnormalGuy said:
Guess we're on the same boat buddy. Have you tried the other ROMs on their forum like the nougat ones? They seem nice.
I personally prefer to use the RR 5.5.9 lollipop rom provided by 4pda since for some reason the nougat and marshmallow roms on their site just give me bootloops. It may be different for you though.
Click to expand...
Click to collapse
Hi, not yet, it's not my phone so I'm searching a stable ROM. I saw the nougat thread here but it's not very clear what works and what not, there seems to be a nougat rom on 4dpa which should work well except the videocamera with the stock app, but the Oreo one seems almost bug free although more complex to install. Unfortunately I can't access it.

Hello,
From what I can tell, both Oreo and Nougat ROMs were unstable and/or sluggish for me, so I'd recommend to stick to Marshmallow based ROMs(for now). My personal preference is ResRemix 5.7.4, but if you decide to try any of them, keep in mind that ROMs with kernel 3.18.19(as far as I've seen most of ROMs in that thread) all have these two issues that I was able to find so far:
Notification LED doesn't work
Bluetooth audio doesn't work either
Other than that, the ROM is super-stable and somehow better than 5.1.1 ROMs from official dev thread there.
And for JustAnormalGuy, bootloops in later ROMs seem to happen because of unwiped internal storage(basicly needs entire /data partition wiped somewhy). Try marking the 'Internal SD' option when wiping partitions for ROM installing.
Good luck!

aurismat said:
Hello,
From what I can tell, both Oreo and Nougat ROMs were unstable and/or sluggish for me, so I'd recommend to stick to Marshmallow based ROMs(for now). My personal preference is ResRemix 5.7.4, but if you decide to try any of them, keep in mind that ROMs with kernel 3.18.19(as far as I've seen most of ROMs in that thread) all have these two issues that I was able to find so far:
Notification LED doesn't work
Bluetooth audio doesn't work either
Other than that, the ROM is super-stable and somehow better than 5.1.1 ROMs from official dev thread there.
And for JustAnormalGuy, bootloops in later ROMs seem to happen because of unwiped internal storage(basicly needs entire /data partition wiped somewhy). Try marking the 'Internal SD' option when wiping partitions for ROM installing.
Good luck!
Click to expand...
Click to collapse
Those 2 bugs are not a deal breaker for me, would you mind linking to the ResRemix 5.7.4 rom that you used?

Sure, buut since I can't post links(thanks XDA for 10 post restriction, love ya!), I'll have to send one another way.
PM me your Discord handle(if you have one) or something else. I should be able to send you the link there.

aurismat, and what version of twrp do you use ?

I use TWRP 3.0 by Jemmini. It's been a *long* time since I installed it though, so if you have something different, I'm afraid I won't be of much help unless I'll be able to pull my recovery .img file.

Actually, i use the same version. Problem is most probably my method of root. The common method of rooting for our device didn't include any flashing with sp flash tool. But for my situation, my bootloader is locked even after downgrading. So i did the other method (also found on the forum) in which includes flashing.

Hmm, it *may* be the root method, may be also the locked bootloader.
If I recall right(and this might be THE common way), I used the fastboot method from XDA, and I knew it'd work cause I rooted more phones that way. I remember downgrading the stock ROM down to version 39(i think that one still had the bootloader check in dev options) and then trying to unlock the bootloader and obviously go through flashing the recovery image.
Dunno what might be the issue with your way of flashing, though. AFAIK might be anything from leftover files to bootloader giving the finger.

@aurismat i think the problem might be that i used the "format all + download" option on sp flash tool. Does that affect the phone in any way that deprives my phone from using 6.0 - 7.0 roms? (Besides the "null" imei effect)

@JustAnormalGuy I don't think it should be a problem, because the ROM .zips install their own stuff to the partitions AFAIK, so even if Flashtool wipes everything, it should still be fine. Try doing one of them ROMs(previously said ResRemix worked for me), but remember to wipe the Internal Storage partition if you can.
Oh and remember to take a backup of your current ROM, should it bootloop again at least you won't have to do the hassle of reinstalling everything back(learned that the hard eay haha).
EDIT: was it just Nougat ROMs that you were trying or was it both Nougat and Marshmallow? Not sure what might be the cause, but the ROMs developed under the same kernel from ska-vova in 4PDA worked for me. Just a thought.

well actually i already tried various roms from Marshmallow to Nougat all of which gave me bootloops. I've already followed the steps of installation as written. However, i tried once installing a Marshmallow rom from the facebook group named "ASUS Zenfone Go Indonesia" and it surpisingly worked for me (numerous bugs present however), as well as most of the marshmallow (and only marshamallow roms) on their group.
The thing is I also might think one of the reasons why i get the bootloops in the roms from the 4pda forum is the kernel used in them. (just speculation) Should it be correct to assume that ?
As I recall:
Working rom shows "kernel version > [email protected]"
Not working rom - "kernel version > [email protected]"

Hmm, I'm using [email protected] kernel version 3.18.19.
All the ROMs there seem to be by mosly nik-kst's kernel. ska-vova seems to just build ROMs with the kernel.
Besides, take note from the working ROM - it's also from 4PDA.
Only thing I can speculate is that your device is somewhat different(maybe different hardware, not sure) and hence why it gives you BLs.
Dunno, this case is a tough cookie to be honest - only thing I can recommend at this point is to flash literally EVERYTHING back to stock and try using fastboot method to get recovery and root back.

Hey @Darkorn,
Over the span of a few days, I've tried installing 4PDA's Oreo ROM.
It took me a good couple of headaches to make out what translated Russian meant in the instructions, but I've managed to repartition the entire device to the guide.
Seems to work properly so far, hell even Bluetooth and Notification LED issues from older ROMs seem to be fixed!
Though one thing that annoys me *personally* is that it's impossible to install SuperSU, so you're stuck with Magisk. It's not the end of the world, though, as long as you don't care about SafetyNet's BS.
Oh and @JustAnormalGuy, try repartitioning your device according to the Oreo instructions in 4PDA, that might be the solution for ya.
If I ever get up to 10 posts I'll ask those guys permission to let me post the tutorial here with all the links(hopefully).
Until then, good luck to both of ya!

aurismat said:
Hey @Darkorn,
Over the span of a few days, I've tried installing 4PDA's Oreo ROM.
It took me a good couple of headaches to make out what translated Russian meant in the instructions, but I've managed to repartition the entire device to the guide.
Seems to work properly so far, hell even Bluetooth and Notification LED issues from older ROMs seem to be fixed!
Though one thing that annoys me *personally* is that it's impossible to install SuperSU, so you're stuck with Magisk. It's not the end of the world, though, as long as you don't care about SafetyNet's BS.
Oh and @JustAnormalGuy, try repartitioning your device according to the Oreo instructions in 4PDA, that might be the solution for ya.
If I ever get up to 10 posts I'll ask those guys permission to let me post the tutorial here with all the links(hopefully).
Until then, good luck to both of ya!
Click to expand...
Click to collapse
Nice! Resurrection Remix is working too well to bother, but who knows in a few months!

That would be great man, thanks !!

Good low effort way of keeping a rooted stock Mi 9T Pro up to date?

Hello,
I bought a 9T Pro in Europe for my wife and until it arrives I'm trying to research and come up with a low effort process of keeping the stock ROM up to date and rooted for her. I'm confident in manually installing and updating custom ROMs, rooting and dealing with custom ROM issues, but she is not. Therefore I thought the best thing is to use the stock ROM - not custom - since it may be the most stable experience and for me to update and re-root it for her regularly. root is mandatory because we need AdAway and other things. As I understand it, as soon as we unlock and root the phone, OTA updates for stock are impossible and maybe even dangerous. I've tried researching here but am bit struggling to come up with the right infos and I'd be glad for any advice.
Of course I have seen the great thread about unlocking, rooting, etc, but It seems that that deals with non-standard Chinese firmware pre-installed, which is probably not the case on our device. Since it's bought in Europe, I think it will probably come with some Global or EU ROM. And it doesn't answer some of my other questions.
So far my idea is roughly like this:
Phone arrives
Immediately update it via built-in OTA to latest official stock ROM
Unlock, install TWRP, root with Magisk
Use the phone
Whenever a new stock ROM comes out, download it from XDA
Flash new ROM in TWRP and root again with Magisk
Repeat 4-6 as new stock ROM versions are released
Of course regularly backup with Titanium Backup and TWRP
First of all, would this work or did I misunderstand something fundamental?
How does low level firmware / modem update come into play? Would that be included in the stock ROM packages I find here? Or do I need to manually update that separately? How do I know when I have to, since there is no custom ROM maintainer telling me when it's needed?
Is there an easier way of doing this? This process requires me to regularly check for a new stock ROM, then borrow the phone from the wife for some time to backup, update, re-root and so on. Not that convenient but it would work if there is no better way.
Sorry for the long post, but I'd be very thankful for any advice or ideas. I did quite some research, but if all this info is already available and I missed it, my sincere apologies. It's a lot of info about a new device to take in. :silly:

derfraenk said:
Hello,
I bought a 9T Pro in Europe for my wife and until it arrives I'm trying to research and come up with a low effort process of keeping the stock ROM up to date and rooted for her. I'm confident in manually installing and updating custom ROMs, rooting and dealing with custom ROM issues, but she is not. Therefore I thought the best thing is to use the stock ROM - not custom - since it may be the most stable experience and for me to update and re-root it for her regularly. root is mandatory because we need AdAway and other things. As I understand it, as soon as we unlock and root the phone, OTA updates for stock are impossible and maybe even dangerous. I've tried researching here but am bit struggling to come up with the right infos and I'd be glad for any advice.
Of course I have seen the great thread about unlocking, rooting, etc, but It seems that that deals with non-standard Chinese firmware pre-installed, which is probably not the case on our device. Since it's bought in Europe, I think it will probably come with some Global or EU ROM. And it doesn't answer some of my other questions.
So far my idea is roughly like this:
Phone arrives
Immediately update it via built-in OTA to latest official stock ROM
Unlock, install TWRP, root with Magisk
Use the phone
Whenever a new stock ROM comes out, download it from XDA
Flash new ROM in TWRP and root again with Magisk
Repeat 4-6 as new stock ROM versions are released
Of course regularly backup with Titanium Backup and TWRP
First of all, would this work or did I misunderstand something fundamental?
How does low level firmware / modem update come into play? Would that be included in the stock ROM packages I find here? Or do I need to manually update that separately? How do I know when I have to, since there is no custom ROM maintainer telling me when it's needed?
Is there an easier way of doing this? This process requires me to regularly check for a new stock ROM, then borrow the phone from the wife for some time to backup, update, re-root and so on. Not that convenient but it would work if there is no better way.
Sorry for the long post, but I'd be very thankful for any advice or ideas. I did quite some research, but if all this info is already available and I missed it, my sincere apologies. It's a lot of info about a new device to take in. :silly:
Click to expand...
Click to collapse
I didn't keep stock MIUI long enough to know definite answers, but from what I remember, this is my understanding.
OTA will still work and shouldn't cause any issues, just that you will lose TWRP and root whenever you do this.
The steps you give are the normal way to update with TWRP and root.
However, OrangeFox recovery (a heavily modified version of TWRP) is often used instead of TWRP in this circumstance. It is built specifically for MIUI devices and with a little bit of work, I believe that it is able to survive OTA updates. Have another dig around for OrangeFox in this forum section and hopefully you'll find details on how to set it up so that you can still take OTA updates.
Edit:
Found this guide https://forum.xda-developers.com/k2...efox-recovery-mi-9t-pro-t3980579/post80480669
It seems OrangeFox it's a bit hit and miss.
Also Xiaomi.eu ROMs are another alternative to look into.

Robbo.5000 said:
I didn't keep stock MIUI long enough to know definite answers, but from what I remember, this is my understanding.
OTA will still work and shouldn't cause any issues, just that you will lose TWRP and root whenever you do this.
The steps you give are the normal way to update with TWRP and root.
However, OrangeFox recovery (a heavily modified version of TWRP) is often used instead of TWRP in this circumstance. It is built specifically for MIUI devices and with a little bit of work, I believe that it is able to survive OTA updates. Have another dig around for OrangeFox in this forum section and hopefully you'll find details on how to set it up so that you can still take OTA updates.
Edit:
Found this guide https://forum.xda-developers.com/k2...efox-recovery-mi-9t-pro-t3980579/post80480669
It seems OrangeFox it's a bit hit and miss.
Also Xiaomi.eu ROMs are another alternative to look into.
Click to expand...
Click to collapse
Wow, that's a lot of helpful info, thanks a lot for pointing me into these directions. I will definitely look into Xiaomi.eu, I that sounds promising!

Get phone. Apply for unlock. Unlock.
You can use my guide bit.do/raphaelguide
Use orangefox 10.8 use magisk.
You can flash eu ROM. Stable version. From xiaomi.eu
Eu rom installs official twrp after install. You are familiar with that
Once you have eu ROM ( same as stock, better performance, minimal bloat, no ads, no tracking)
Eu ROMs gets OTA, keeps root. This is exactly what you want. Just press update in settings as normal ota. It'll do normal ota update by itself, no titanium, migrate hassle.
Join telegram group if you want or on me for any help.

Sandeeep Kiran said:
Get phone. Apply for unlock. Unlock.
You can use my guide bit.do/raphaelguide
Use orangefox 10.8 use magisk.
You can flash eu ROM. Stable version. From xiaomi.eu
Eu rom installs official twrp after install. You are familiar with that
Once you have eu ROM ( same as stock, better performance, minimal bloat, no ads, no tracking)
Eu ROMs gets OTA, keeps root. This is exactly what you want. Just press update in settings as normal ota. It'll do normal ota update by itself, no titanium, migrate hassle.
Join telegram group if you want or on me for any help.
Click to expand...
Click to collapse
Amazing, I have taken a look at Xiaomi.eu already and decided to try that. But what you're saying sounds even much better than what I expected. Thank you very much too, I will definitely go that route.

from xiaomi eu beta to global stable / custom rom (PE)

Hi, im currently on xiaomi.eu beta 20.1.2. From what I learnt the firmware is updated to 20.1.2. If I want to flash Pixel Experience, which recommends 9.11.7 or higher. Should i downgrade my firmware? I heard downgrading will brick the device.

No ARB, isn't enforced by Xiaomi...not yet.
Make a local backup and save it to your desktop so when you come back to Xiaomi.EU you can restore much faster.
Instructions here: https://xiaomi.eu/community/threads...om-restored-in-eu-rom-after.52880/post-510238
As far as the firmware, you can try a simple factory reset and try flashing, it may work since 9.17 is probably just the minimum firmware needed. But I am not sure because I haven't used that Rom recently. On the other hand, I can tell you that I tried some other roms recently out of boredom and for me they do not yet equal the current Xiaomi.EU in overall stability.

tsongming said:
No ARB, isn't enforced by Xiaomi...not yet.
Make a local backup and save it to your desktop so when you come back to Xiaomi.EU you can restore much faster.
As far as the firmware, you can try a simple factory reset and try flashing, it may work since 9.17 is probably just the minimum firmware needed. But I am not sure because I haven't used that Rom recently. On the other hand, I can tell you that I tried some other roms recently out of boredom and for me they do not yet equal the current Xiaomi.EU in overall stability.
Click to expand...
Click to collapse
thank you very much for the swift reply! Yeah because some roms have firmwares built to them at a older version, i dont know whether flashing them will brick the phone or not. I'm just itching to try out the other roms at this state. I went from global stable to pe and many roms then ended up with EU. But as time goes by, needed to check out them at present state

steveeekong said:
thank you very much for the swift reply! Yeah because some roms have firmwares built to them at a older version, i dont know whether flashing them will brick the phone or not. I'm just itching to try out the other roms at this state. I went from global stable to pe and many roms then ended up with EU. But as time goes by, needed to check out them at present state
Click to expand...
Click to collapse
Just be sure to get a full TWRP backup. I recommended the version on my Persist thread. if you have the full backup you will never need to worry.
Also, I certainly understand wanting to see what else it is out there. Unfortunately, many roms do not provide good how to install instructions. As long as you use the recommended firmware along with DM Verity if needed, you should not have any issues, and bricking your phone is very unlikely.
Before attempting to install any rom read the OP and the last few pages at the end of the post.