Does anyone know of a stock miui rom for the Spes that has been debloated of ads and other crap and optimised? Don't mind whether it is a recovery rom or needs to be flashed with fastboot (or miflash).
I'm currently on v13 Android 11 the global version, quite happy to remain on that.
Can someone provide a link to the rom?
Thanks.
Look here: https://xiaomi.eu/community/threads/miui-13-stable-release.64441/
I have tested a lot of roms, and in the end I installed the official one and removed software through adb, today I don't have any bugs or strange problems, besides that I can use the camera in its entirety. I got bored with the custom ones, some games don't run, others are terrible and at the moment there is no fix for this.
Microsheepcl said:
I have tested a lot of roms, and in the end I installed the official one and removed software through adb, today I don't have any bugs or strange problems, besides that I can use the camera in its entirety. I got bored with the custom ones, some games don't run, others are terrible and at the moment there is no fix for this.
Click to expand...
Click to collapse
Ditto, I always appreciate the custom roms and appreciate the efforts developers go to because there are a lot on here that do nothing but complain about custom roms, however I think I'd prefer a stable daily driver. There is no sign of the kernel source being released which would be a big help for the devs.
I've just finished flashing the stock rom and will go about debloating. There are a number of "safe to remove" lists for miui roms so I will get to work.
Thanks the replies guys.
maritimesbob said:
Ditto, I always appreciate the custom roms and appreciate the efforts developers go to because there are a lot on here that do nothing but complain about custom roms, however I think I'd prefer a stable daily driver. There is no sign of the kernel source being released which would be a big help for the devs.
I've just finished flashing the stock rom and will go about debloating. There are a number of "safe to remove" lists for miui roms so I will get to work.
Thanks the replies guys.
Click to expand...
Click to collapse
Hi, may I ask how did you flashed stock ROM? I recently tried to flash 13.0.5 A12 on mine through TWRP, it probably refuses to boot because after the ROM has finished flashing I flashed TWRP next. I also know the fastboot + miflash method but everytime I do it, it gives me anti rollback check error
I downloaded the miui.eu rom which is debloated and allegedly more optimised. I went back A11 the same as I had before I unlocked my bootloader. I flashed the fastboot version and used the bat script inside the zip to flash it.
Alex Zander-kun said:
Hi, may I ask how did you flashed stock ROM? I recently tried to flash 13.0.5 A12 on mine through TWRP, it probably refuses to boot because after the ROM has finished flashing I flashed TWRP next. I also know the fastboot + miflash method but everytime I do it, it gives me anti rollback check error
Click to expand...
Click to collapse
Ok, that's strange, it shouldn't give an antirollback error when you have the same version of android and miui.
Try again with myflash
But surely when flashing the official rom by twrp you damaged something, if I remember correctly the twrp of spes does not have support for flashing a stock rom, even less if it goes as an update.
Anyway, if you want to make your rom boot, try taking the boot.img out of the fastboot rom and flashing that boot.img to your phone and see if it boots.
Microsheepcl said:
Ok, that's strange, it shouldn't give an antirollback error when you have the same version of android and miui.
Try again with myflash
But surely when flashing the official rom by twrp you damaged something, if I remember correctly the twrp of spes does not have support for flashing a stock rom, even less if it goes as an update.
Anyway, if you want to make your rom boot, try taking the boot.img out of the fastboot rom and flashing that boot.img to your phone and see if it boots.
Click to expand...
Click to collapse
My first guess was that it was because at that time I was on an Android 13-based custom ROM (Pixel Experience Plus 13 and CrDroid 9.0), but I was proven wrong after I flashed PE+12 shortly before trying MiFlash. Because it gave me the same error (Anti-rollback check)
Oh, I actually tried the flash-stock-ROM-via-TWRP method after I tried MiFlash method, so I doubt that's the issue. But all I can say is a few days ago I flashed 13.0.5 A12 firmware (latest at the time of writing), so could that be that issue?
I might wanna try what you said, thanks for the suggestion. But for now, I'm on EU and may stay for a few months
Alex Zander-kun said:
My first guess was that it was because at that time I was on an Android 13-based custom ROM (Pixel Experience Plus 13 and CrDroid 9.0), but I was proven wrong after I flashed PE+12 shortly before trying MiFlash. Because it gave me the same error (Anti-rollback check)
Oh, I actually tried the flash-stock-ROM-via-TWRP method after I tried MiFlash method, so I doubt that's the issue. But all I can say is a few days ago I flashed 13.0.5 A12 firmware (latest at the time of writing), so could that be that issue?
I might wanna try what you said, thanks for the suggestion. But for now, I'm on EU and may stay for a few months
Click to expand...
Click to collapse
Always that I need as a base a stock ROM flashed, I "simply" use the fastboot commands that are inside the ROM, I open my ADB/fastboot CMD/terminal, and drag and drop the flash_all.bat file while in Windows or the flash_all.sh file while on Linux. This method allows to me, to can follow the process while the scripts are running, and search for issues (if there are some)
As per the TWRP flashing the stock ROM, it worked fine too. You just need to flash the ROM, then boot to recovery once, you'll find the stock one, then format data from it, then you are ready, either to go straight to system, or if you prefer have TWRP (or any custom recovery), go to fastboot and follow the method to boot to, and then flash it permanently to the ramdisk.
Related
Let's say i got a rom that performs amazingly,super fast tab switch,good at multi tasking,25k in benchmark.
Then I want to try a new rom,so I flash the new rom after cleaning my devide,as i should do.
But I don't like it or whatever and I want to return to the old one. But after I flash the old rom the performance is extremely bad,getting random systemui FC ,reboots,etc.
Why is this happening? Right now I'm running out of roms that I can use on my phone,as I cannot go back to the ones that I really liked. Please help
It also happens when a developer posts a new build of a rom. If i got the previous build installed and i flash the new one,the rom is broken again.
darkkfruit said:
Let's say i got a rom that performs amazingly,super fast tab switch,good at multi tasking,25k in benchmark.
Then I want to try a new rom,so I flash the new rom after cleaning my devide,as i should do.
But I don't like it or whatever and I want to return to the old one. But after I flash the old rom the performance is extremely bad,getting random systemui FC ,reboots,etc.
Why is this happening? Right now I'm running out of roms that I can use on my phone,as I cannot go back to the ones that I really liked. Please help
It also happens when a developer posts a new build of a rom. If i got the previous build installed and i flash the new one,the rom is broken again.
Click to expand...
Click to collapse
I use Philz recovery and before flashing a new rom i just simply hit Clean up to install a new rom.
I never faced any of the issue that u mentioned. Try following what i said.
If u are using a lollipop rom then u may face systemui FC ,reboots as there is a bug which is experienced by some users.
I tried every recovery, twrp with full device wipe,cwm with their wipe,and philz with full wipe and the one you mentioned.
The issues happen in every rom,wether it's 3.2,4.4 or 5.x.
darkkfruit said:
I tried every recovery, twrp with full device wipe,cwm with their wipe,and philz with full wipe and the one you mentioned.
The issues happen in every rom,wether it's 3.2,4.4 or 5.x.
Click to expand...
Click to collapse
Return to stock by flashing ftf through flashtool and start from beginning.
Alright, I'm in need of some help, and I'm not sure if this is the right place to put this thread, so if it';s in the wrong place, I'm sorry for taking up space in the wrong section.
My issue is with my Nexus 6, the Verizon variant; I had a custom kernal, running 6.0, and was rooted. I wanted to upgrade to 6.0.1, and downloaded the newer version of the ElementalX kernal, the one I was using, as well as the necessary SuperSU files. I downloaded the new Android version, installed it, and before it went intoi the OS, I flashed the kernal and SuperSU upgrade, and now my phone either won't boot, or is taking the longest time for a phone to boot on the planet.
I need to download a 6.0.1 ROM that I can flash with TWRP. Any links or advice anyone could offer would be grately appreciated, because right now, I'm drawing a massive blank.
Many thanks!
Do you need to backup any data?
Could you not just flash a stock "like" rom such as this one by Danvdh http://forum.xda-developers.com/nexus-6/development/rom-5-1lightromstock-lmy47e-03-19-2015-t3059493 as it has already been rooted.
I have been running it for a while, very solid and stable rom.
Which SuperSU did you install?
Reflash the rom youre using and then flash Super su (asuming its not a pre-rooted rom) BEFORE flashing elemental x. Other kernels work the other way around
Question?
Are you trying to run systemless root wit EX? If so did you click on yes when TWRP asked you to root your rom?
That would would cause the rom not to boot.
http://forum.xda-developers.com/showthread.php?t=3252922 stock with root latest q
Don't flash anything else till you boot at least once.
Sent from my Nexus 6 using Tapatalk
joncy92 said:
Do you need to backup any data?
Click to expand...
Click to collapse
I decided to download and flash a custom CM13 build, but it's a bit finicky, kinda to be expected with an early release, though. I'm using that ROM, for now. I'd still prefer getting something from the CM team, something that's supported and I can download upgrades to.
joncy92 said:
Do you need to backup any data?
Click to expand...
Click to collapse
holeindalip said:
Which SuperSU did you install?
Click to expand...
Click to collapse
Pretty sure it was 2.61. I have a few versions of it on my phone, ready for flashing, but was careful, making sure I chose the right one.
swazii said:
Question?
Are you trying to run systemless root wit EX? If so did you click on yes when TWRP asked you to root your rom?
That would would cause the rom not to boot.
Click to expand...
Click to collapse
I'm not great with this stuff. Sorry4Noobishness. I'm not sure what systemeless rooting is.. Originally, I just flashed SuperSU and EX onto the stock ROM I was using. Worked fine. When I decided to upgrade, I downloaded the 6.0.1 ROM, installed it, but didn't boot into the OS. I booted into TWRP, and flashed the new EX and SuperSU stuff. The phone didn't boot after that. It was just stuck on the Google boot animation of all the interacting circles.
I decided to use a custom ROM, a CM13 ROM, but it isn't supported, which is why I'm not looking for a CM13 ROM I can use, because, well, I'd kinda like to be able to upgrade when an upgrade comes out.
Flashing a nightly build from their site did the same thing. I flashed the ROM, then gapps, then SuperSU, and it gets stuck on the boot animation. I let it sit for about half an hour, then restored the custom build I was using. I'm not really sure what to do to get a REAL CM13 build on this thing.
DaJesuZ said:
Pretty sure it was 2.61. I have a few versions of it on my phone, ready for flashing, but was careful, making sure I chose the right one.
Click to expand...
Click to collapse
2.61 is old now, 2.65 is the latest.
DaJesuZ said:
I'm not great with this stuff. Sorry4Noobishness. I'm not sure what systemeless rooting is.. Originally, I just flashed SuperSU and EX onto the stock ROM I was using. Worked fine. When I decided to upgrade, I downloaded the 6.0.1 ROM, installed it, but didn't boot into the OS. I booted into TWRP, and flashed the new EX and SuperSU stuff. The phone didn't boot after that. It was just stuck on the Google boot animation of all the interacting circles.
I decided to use a custom ROM, a CM13 ROM, but it isn't supported, which is why I'm not looking for a CM13 ROM I can use, because, well, I'd kinda like to be able to upgrade when an upgrade comes out.
Flashing a nightly build from their site did the same thing. I flashed the ROM, then gapps, then SuperSU, and it gets stuck on the boot animation. I let it sit for about half an hour, then restored the custom build I was using. I'm not really sure what to do to get a REAL CM13 build on this thing.
Click to expand...
Click to collapse
Sounds to me like you dont have the correct bootloader. Which bootloader are you currently using? try flashing the newest bootloader and radio then flash your rom again. It should then boot up fingers crossed.
Jnewell05 said:
http://forum.xda-developers.com/showthread.php?t=3252922 stock with root latest q
Don't flash anything else till you boot at least once.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Alright, I decided to go with this ROM, but now I'm stuck with an issue: It won't let me install any apps. Minimalist gapps was used, so I'm not sure what's wrong. Should I just flash stock gapps and see how it goes?
DaJesuZ said:
Alright, I decided to go with this ROM, but now I'm stuck with an issue: It won't let me install any apps. Minimalist gapps was used, so I'm not sure what's wrong. Should I just flash stock gapps and see how it goes?
Click to expand...
Click to collapse
Why did you flash gapps? It seems that this rom comes with gapps already.
blanco2701 said:
Why did you flash gapps? It seems that this rom comes with gapps already.
Click to expand...
Click to collapse
Wouldn't let me use the Play Store. Nothing would install, and it's kinda pointless to have an internet-capable device if it can't connect to what's supposed to provide me with that internet connectivity (downloading Chrome, for example). Had to flash stock gapps, but it all seems to be working now.
Hello everyone, I have sultanxda cm13 ROM on my oneplus 3t and i have a problem. When i try to flash a ROM( lineage 7.1.2, oxygenos and hydrogenos) twrp give me error 7. On other devices i can flash all type of rom from example 6.0.1>7.1.2 or 7.1.2>6.0.1 so, what can i do to flash a nougat ROM? Thanks.
You will have to clean data between ROM change as they're incompatible. You really should newer dirty flash between different ROMs, that's a certain way to get yourself troubles. Also, make sure you have the correct Radio firmware for the ROM you flash (usually the latest unless you of course flash an older oudated ROM).
And... Try an updated twrp.
Kollachi said:
And... Try an updated twrp.
Click to expand...
Click to collapse
Thanks. However i have the 3.1.1.0 twrp and i clean flash every time. Do you recommend me the blue spark twrp?
pitrus- said:
You will have to clean data between ROM change as they're incompatible. You really should newer dirty flash between different ROMs, that's a certain way to get yourself troubles. Also, make sure you have the correct Radio firmware for the ROM you flash (usually the latest unless you of course flash an older oudated ROM).
Click to expand...
Click to collapse
I clean flash every time. Also, what is the correct radio firmware?
Either OnePlus3T_4.1.6-(10-6-17)-FIRMWARE-flashable.zip or the latest Beta modem firmware found in this forum.
Ivanprince99 said:
Thanks. However i have the 3.1.1.0 twrp and i clean flash every time. Do you recommend me the blue spark twrp?
Click to expand...
Click to collapse
Don't know the difference between them. An old twrp can cause this error but I think it's because u haven't the right firmware installed right now.
OK Thanks a lot.
hallo guys, i have issues when i try to go back to a version of the stock rom because they wont boot
not sure what im doing wrong, i hope someone can tell me..
here the full story: when i got the device, i checked the stock rom which was ok.
my plan was to use lineageos, so i unlocked the bootloader,installed TWRP and flashed the global vendor, unofficial 17.1 and gappswhich.
this is working fine and i can always reinstall this lineage the way i mentioned above, but i saw that the finger unlock is not working in that rom as expected.
since i didnt test it in stock rom, i thought lets try this and now comes the issue, i can not find any solution to go back to stock rom which is working.
#1 tried to download rom from https://mi-globe.com/miui-firmware-rom-builder-features/19/ which should be flashed with TWRP (howto there).
when flashing, this is not finishing and looks like its stuck in twrp flashing. ok, since the download for other config was broken yesterday, there might be issues.
#2 downloaded stable rom from https://forum.xda-developers.com/k20-pro/how-to/rom-miui-11-xiaomi-eu-t3984691
flashing works, but device is in boot loop then. im sure i was missing something or doing wrong, so i searched for another option.
#3 found a youtubevide about BACK2STOCK https://www.youtube.com/watch?v=KBsWNrKNZzA
downloaded all the needed packages and did it like it was in the video.
result: all flashed like shown in the video, when system reboot is done MI logo is shown around 60seconds and then rebooting to TWRP
#4 i would go for the solution to flash via MIFLASH, but before i break something i thought i better ask here.
since there are so many issues, i would need your help to point me to the mistakes im doing here.
going back to lineage 17.1 is not a problem, i just did again and this is working.
so if you read this, please find time to explain me if you want to.
thank you
yeah, you are missing a step.
you have to format data partition.
check my guide on how to install roms: https://forum.xda-developers.com/k20-pro/how-to/simple-beginners-guide-to-raphaelin-t4020543
also, may I suggest EU/masik instead of stock, its a lot better
in #3 you can see that in the video data is also formated: https://youtu.be/KBsWNrKNZzA?t=190
of course i did this too....was also not working.
reading your simple beginners guide and downloading MIUI EU ROM (xiaomi.eu_multi_HMK20ProMI9TPro_V11.0.5.0.QFKCNXM_v11-10.zip)
flashed it, was also not working/booting. tried also with flashing vendor (the one from lineage) before, no change.....
what should i do?
motorh3ad said:
reading your simple beginners guide and downloading MIUI EU ROM (xiaomi.eu_multi_HMK20ProMI9TPro_V11.0.5.0.QFKCNXM_v11-10.zip)
flashed it, was also not working/booting. tried also with flashing vendor (the one from lineage) before, no change.....
what should i do?
Click to expand...
Click to collapse
Don't flash vendor, theirs no need, eu.miui has everything in the one zip file. Just to clarify have you formatted in twrp? The option where it requires you to type 'yes'? Everything gets wiped from your photos and apps all to the rom itself. Then just flash eu.miui and reboot. Works everytime for me without fail.
no i never formatted in TWRP wipe, only used the factory reset and swiped to wipe.
just did a format and flashed xiaomi.eu_multi_HMK20ProMI9TPro_V11.0.5.0.QFKCNXM _v11-10.zip
ITS BOOTING!!
first please let me thank you very much for this help, i was already quite desperate about nothing working except LINEAGE.
fingerprint in MIUI rom is working great, unbelievable!
can you please explain me why this FORMAT in WIPE is needed and what its used for? i was not aware and i can not find it in any of the howtos..
haha, glad it's working. Knew the problem was that you didn't format.
however since you posted on xda, I just assumed you knew format data is not the same as wiping data.
(literally, the most common beginners mistake for this phone)
it's cause of the encryption keys, when moving from MIUI to AOSP (and vice-versa) a format data partition is required.
I stated this in How To Change My ROM? I wanna Try them all!
section in the first post.
under there, FOR MIUI ROMS (since that is what you were trying to do)
you missed the 7th bullet point. (you can also text me on telegram)
(also, in the same guide, I inform people to flash their vendor first -4th bullet point- then in the 5th bullet point you wipe it.)
(this is cause often miui customs and some people are usually on a vendor that isnt there's. you have to be on your region vendor, then wipe it, then allow the miui custom's vendor to take over, else you will face fingerprint problems)
This is just another point most just don't follow.
Umm, if my guide needed anything to be included, or like... needed to be more easy to read and follow... I can edit that if you like.
(use can text me on telegram as well)
edit: just read the xiaomi.eu one, I'll edit it to make it more informative
motorh3ad said:
hallo guys, i have issues when i try to go back to a version of the stock rom because they wont boot
not sure what im doing wrong, i hope someone can tell me..
here the full story: when i got the device, i checked the stock rom which was ok.
my plan was to use lineageos, so i unlocked the bootloader,installed TWRP and flashed the global vendor, unofficial 17.1 and gappswhich.
this is working fine and i can always reinstall this lineage the way i mentioned above, but i saw that the finger unlock is not working in that rom as expected.
since i didnt test it in stock rom, i thought lets try this and now comes the issue, i can not find any solution to go back to stock rom which is working.
#1 tried to download rom from https://mi-globe.com/miui-firmware-rom-builder-features/19/ which should be flashed with TWRP (howto there).
when flashing, this is not finishing and looks like its stuck in twrp flashing. ok, since the download for other config was broken yesterday, there might be issues.
#2 downloaded stable rom from https://forum.xda-developers.com/k20-pro/how-to/rom-miui-11-xiaomi-eu-t3984691
flashing works, but device is in boot loop then. im sure i was missing something or doing wrong, so i searched for another option.
#3 found a youtubevide about BACK2STOCK
downloaded all the needed packages and did it like it was in the video.
result: all flashed like shown in the video, when system reboot is done MI logo is shown around 60seconds and then rebooting to TWRP
#4 i would go for the solution to flash via MIFLASH, but before i break something i thought i better ask here.
since there are so many issues, i would need your help to point me to the mistakes im doing here.
going back to lineage 17.1 is not a problem, i just did again and this is working.
so if you read this, please find time to explain me if you want to.
thank you
Click to expand...
Click to collapse
You're not installing stock ROMs. You are installing custom ROMs based on stock.
If you want to return to true stock grab a fastboot ROM from here and flash it with the Mi Flash Tool. After fully extracting the ROM delete the flash_all_lock.bat file before flashing. That way you cannot accidentally lock the bootloader.
Then choose the 'clean all' option in the Mi Flash Tool before you hit the flash button.
thank you.
my mistake, i didnt write clear. i just wanted to test a miui rom to see how the fingerprint is working there. im happy now with the custom rom based on stock.
but i also went for this solution you mentioned and noticed that on the https://www.xiaomiflash.com/ site only older xiaomi devices are mentioned as beeing compatible.
looks like this is not the point, so im happy to have this option too.
As per title, no other rom/recovery now works on my device.
Only reason I keep coming back to this rom is because my phone no longer boots MIUI due to me attempting to fix IMEI (Worked on BananaDroid).
I want to swap to another rom/recovery because this one is super laggy and keeps killing my apps when im using them, but the phone doesnt boot any other recovery/ROM.
Any idea why that would be? (Even re-installing stock rom through fastboot doesnt work.)
Since I didn't understand exactly which rom you currently have, I hope I can help you with my advice. Have you tried to install stock rom with mi flash? I've never had any problems this way.
boofiboi said:
As per title, no other rom/recovery now works on my device.
Only reason I keep coming back to this rom is because my phone no longer boots MIUI due to me attempting to fix IMEI (Worked on BananaDroid).
I want to swap to another rom/recovery because this one is super laggy and keeps killing my apps when im using them, but the phone doesnt boot any other recovery/ROM.
Any idea why that would be? (Even re-installing stock rom through fastboot doesnt work.)
Click to expand...
Click to collapse
I fixed it by flashing MIUI android 11 then doing all my custom rom stuff.. I have no idea why it doesnt work when you have android 12 MIUI, different vendors ig?