Custom Recovery and mpdecision on stock ROM - Xiaomi Mi Max Questions & Answers

I tried every ROM for Mi Max Helium on this forum for knowing the best ROM for battery. I saw also that there is a way to add mpdecision feature on stock ROM, but for doing that, I need to have custom recovery on stock ROM. Everytime I try to flash custom ROM, this causes bootloop.
(I flash recovery by fastboot, and it works, but I only go in recovery, I can't turn on phone, because this one goes into a bootloop).
Can someone help me? Unfortunately, mpdecision files, are only for MIUI 8.1.3.0 and not for rooted MIUI on this forum.

Successfully TWRP installed an Official Chinese ROM together with a patched boot image from mi-globe.com just as an experiment. I am on EU ROM now. Official ROM seems dangerous for me when changing ROMs as it encrypts partition which I can't access anymore and even a TWRP backup of Official ROM becomes useless as it suddenly doesn't accept the secret pattern to access the phone.

Did you installed twrp on stock MIUI? without bootloop? You should do a guide in this case.

I've done guys! I rooted stock Chinese rom, fixed WhatsApp delayed notifications (and others apps notifications). I use my mi max from this morning (08:00 am) and now my phone is on 79%, I called two times, used YouTube, played to Clash Royale (5 matches), and used WhatsApp! This is the best combo Rom!

Related

Max 3 help with ROM

So I love this phone. However, prior to flashing the correct Chinese ROM, I wiped the System. I feared this fake ROM could corrupt the actual official ROM and I didn't want anything left on the phone, except TWRP.
I have the Chinese ROM Xiaomi advises to flash, but I am wondering if this ROM will be complete??? According to Xiaomi forums, they need the original system in place to flash ROMs. So did these yo-yo's with the fake ROM keep that essential info and flash their custom, or did they wipe everything anyway???
It's my understanding that usually, you can wipe everything and restart with a new ROM, but it sounds like Xiaomi has some inherent info in the system that needs to be retained. They are the ones promoting users remove the fake ROM, but they also say not to wipe the system.
Anyway, I will flash tonight using TWRP and see how it goes.
If this is the case, will I be stuck flashing to custom ROMs??? Whenever they come out. Or will I be stuck forever unless I can get a complete Xiaomi ROM. OR will I have a 7" screen to look at TWRP on?
Have the same doubts. Please report here your progress. Thanks
Ald47 said:
So I love this phone. However, prior to flashing the correct Chinese ROM, I wiped the System. I feared this fake ROM could corrupt the actual official ROM and I didn't want anything left on the phone, except TWRP.
I have the Chinese ROM Xiaomi advises to flash, but I am wondering if this ROM will be complete??? According to Xiaomi forums, they need the original system in place to flash ROMs. So did these yo-yo's with the fake ROM keep that essential info and flash their custom, or did they wipe everything anyway???
It's my understanding that usually, you can wipe everything and restart with a new ROM, but it sounds like Xiaomi has some inherent info in the system that needs to be retained. They are the ones promoting users remove the fake ROM, but they also say not to wipe the system.
Anyway, I will flash tonight using TWRP and see how it goes.
If this is the case, will I be stuck flashing to custom ROMs??? Whenever they come out. Or will I be stuck forever unless I can get a complete Xiaomi ROM. OR will I have a 7" screen to look at TWRP on?
Click to expand...
Click to collapse
Inviato dal mio NX531J utilizzando Tapatalk
Last night I got back and I decided to see what I could do using the ROMs that are out there. I found the phone completely dead. I charged it, but it would only boot to Fastboot mode. I could not get into TWRP. I moved the Chinese ROM to the SD in hopes of using TWRP, but even after a few hours I was still stuckin only Fastboot.
I searched for devices with similar chipsets to the Max 3 and decided to use the official Note 5 Pro ROM. I was able to use the Mi Flash tool. Actually, both Fastboot and the Mi Flash tool see the device. I attempted to flash the Redmi ROM and, although I got the error "device mismatch" everything seemed to function properly.
It's my guess that I'm stuck waiting on a Fastboot ROM for my device.
There is a newer version of the China Stable fastboot ROM available, but I couldn't lay my hands on it at the moment. If you just want to get your device up and running you can use the original China Stable fastboot ROM (link below) and then you should be able to update using the automatic updater in Settings.
http://bigota.d.miui.com/V9.6.7.0.O...EDCNFD_20180705.0000.00_8.1_cn_7c9a1a57f8.tgz
frcraig said:
There is a newer version of the China Stable fastboot ROM available, but I couldn't lay my hands on it at the moment. If you just want to get your device up and running you can use the original China Stable fastboot ROM (link below) and then you should be able to update using the automatic updater in Settings.
http://bigota.d.miui.com/V9.6.7.0.O...EDCNFD_20180705.0000.00_8.1_cn_7c9a1a57f8.tgz
Click to expand...
Click to collapse
Another use have me the newest link. I will try it tonight and let you know.
Thank you!!!
Success!!! Had to charge the phone for two days to get to 2% battery!!! Then I used the Mi flash tool and the 9.6.11 ROM since the .12 wouldn't work.
Had to work in Chinese on the screen lock but got in and now it's 100% making phone calls etc!!!

Having trouble flashing custom ROM

Hi everyone
I have tried flashing a custom ROM. TWRP3.3.1 is installed and therefore bootloader unlocked. I tried flashing resurrection remix as per this guide:
1)Full wipe (system,data,vendor, dalvik,cache,internal storage) + format data.
2)Flash No-verity-opt patch + xiaomu.eu developer on Oreo or xiaomi.eu 10.2.1 Stable
3)Factory reset
4)Reboot to recovery
5)Flash Resurrected Kernel v3.3
6)Flash POST-sGSI_3_v0.6 .zip
7)Flash RR System.img
8)Flash Magisk 18.0 (if you get an error that /vendor can't be mounted then just reboot recovery and flash Magisk again)
9)Reboot to system
10)Setup system
11)Reboot to recovery
12)Flash BiTGApps or OpenGapps + Magisk 18.0
13)Reboot to system
Although I used Kernel 5.1 PIE
Before this attempt I tried Havoc and I tried lineage and it's always the same... flashing the system.img takes only seconds and declares success. Then the boot screen of the respective ROM stays forever.
I just flashed xiaomi.eu ROM 10.2.1 and that boots fine.
What am I missing here?
Thanks!
Also I don't seem to have anti rollback protection enabled (or I guess I would have bricked the phone anyway by now):
getvar:anti FAILED (remote: GetVar Variable Not found)
Looks like nobody has this phone seeing as there is no official custom ROM development... interesting considering the thread about the 6GB version has 13k views....
Marco2G said:
Looks like nobody has this phone seeing as there is no official custom ROM development... interesting considering the thread about the 6GB version has 13k views....
Click to expand...
Click to collapse
Custom Rom development seems to have started very recently after the statement of XIAOMI that there will not be a MAX 4 this year.
But from what I've seen so far, most people are on some kind of MIUI Custom Rom and only a few went the route of trying a more AOSP like Custom Rom.
Regarding your statement that you don's seem to have Anti Rollback Protection, I am 100% sure this is wrong. I've seen threads about that topic that asked why they can't get the ARP value anymore with the method you used and if I recall correctly there was a different way of doing it.
Cheers
I just managed to solve my issues.
I installed the patched TWRP for Nitrogen https://forum.xda-developers.com/mi-max-3/development/recovery-twrp-3-2-3-1-nitrogen-t3866084
Interestingly enough, installing a custom ROM image still only takes about ten seconds or so. But now the stuff actually boots.
The Xiaomi.eu ROM that Tradingshenzhen packaged in their tutorial does not have ARB yet. I believe the latest ROMs do.
Look inside your ROM for antiroll the same say to me not found but the beta stock ROM have the 4. This is stopping me to do anything on this phone. Never buy xiaomi again. They add this stupid antiroll they stop betas they make always year after year the phones cheaper.. I mean they remove custom led rgb only white then they make it so small you can't see it. To have the phones cheap they go down on quality

Installing GSI ROMs on Mi8 Pro

The below is a guide to installing GSI images on the Mi 8 Pro. I specifically have experience with the PixelExperience 9.0 (Unofficial) but have had other GSI ROMs booting and working. I hope this is useful for some.
GSI (Generic System Image) ROMS can be flashed to any Project Treble enabled device. These devices have either an A/B partition layout (these allow for seamless updating as the system can boot from A or B partition) or just an A only partition layout. The Mi 8 Pro is an arm64 a only device and support project treble ROMs. You can choose from suitable ROMs listed here and here.
The instructions given below are for Android Pie (9.0). The same basic setup can be used for Android Oreo (8.0, 8.1) ROMs, but the Mi 8 Pro should be flashed with the appropriate Xiaomi base ROM first before flashing any 8 based GSI ROM
As the ROM development for the Mi 8 Pro is basically dead, I decided to buy a OnePlus 6T and sell my Mi 8 Pro. However, due to having my new OnePlus 6T stolen, and due to a lack of funds to buy a new device, I have revived my Mi 8 Pro to try to get something other than MIUI working on it. I now have The PixelExperience (Unofficial) GSI ROM running very smoothly on my Mi 8 Pro.
As the PixelExperience team has stated they will be delivering GSI images again, if there are enough of us asking, we could get better support for things like the fingerprint sensor, for a more complete experience.
Some of the below steps may be unnecessary, but are there for a complete beginner's guide to doing this and getting the right results.
Working:
WiFi
Bluetooth (with APTX)
NFC (Including Google Pay)
RIL
Mobile data (LTE / HSPDA / 3G / EDGE)
GPS
Camera (with camera built in to ROM, as well as some GCAM implementations)
Video Camera (not working on GCAM implementations tested so far - only working on Camer built in to ROM)
Flashlight
Sound / Vibrations
Face Unlock
Hotspot
Not Working:
VoLTE (I have had it working, but unable to end phone calls and problems receiving SMS messages, so reverted)
Fingerprint (There is some support. The fingerprint area of the screen lights up when trying to enrol a new fingerprint. The screen dims when a finger is placed on the sensor, and a green light us emitted from the sensor area, but it does not register the fingerprint and this is not currently working.)
Notification LED
You Tell Me
How to install
Flash the latest Fastboot Global Stable Android PIE (9.0) ROM for the Mi 8 Pro. (eg. equuleus_global_images_V10.3.4.0.PECMIXM_20190712.0000.00_9.0_global_9a181f79c1.tgz) using the Xiaomi Tool.
Update: Use the latest MIUI system. The contents of the vendor partition are important. The most compatible vendor partition as of 2019-08-19 is from equuleus_global_V10.3.5.0.PECMIXM. You can download and flash that vendor independantly, if you have already set up your GSI image.
Reboot and finish basic MIUI setup.
Reboot to recovery.
[*]Format data (Wipe - Advanced - format data - confirm by typing yes)
DO NOT FORMAT DATA. Just perform a factory reset. Formatting data can cause issues and prevent booting.
Wipe Cache - Dalvik Cache and System
Reboot recovery
Use adb to push PixelExperience GSI image (img file extracted from download) and latest version of Magisk to root of SDCard. (Empty due to formatting data).
("adb push c:\path\system.img /sdcard/" and then "adb push c:\path\Magiskv19.3.apk /sdcard/")
Flash the image to system partition by taping INSTALL and then on the "Install Image" button (to toggle between flashing zip and img files). Do not reboot yet.
Flash magisk zip in the normal way (hit the same button as in previous step to show zip files to flash. (This is necessary to avoid bootloops)
Reboot, and enjoy.
You can now set up your "PixelExperience" device with your apps and settings, including registering a face for face unlock.
To pass cts validation for the safetynet and to allow service such as Google Pay to work
In Magisk, under settings - Find “Magisk Hide” and toggle the switch on
Magisk restarts. Go to Magisk Hide from the Magisk menu and ensure that...
Google Pay
Google Play
Google Play Services
Google Service Framework
Any Banking Apps
...are checked so that they cannot see Magisk (canont see phone as rooted).
Now go to downloads and install the SafetyPatch v3 module (created by hackintosh5).
Reboot.
Open settings - go to apps and notifications - and find the above apps to clear all data.
Enjoy your rooted safetynet compliant, as close to stock as possible Xiaomi Mi 8 Pro.
nice work thanks for this great notice, i will test PixelExperience, how work the face unlock? i use the finger print very much, all day, but not work i will use the facial unlock. Then i wanna know how work this.
thanks!!
axelgrox said:
nice work thanks for this great notice, i will test PixelExperience, how work the face unlock? i use the finger print very much, all day, but not work i will use the facial unlock. Then i wanna know how work this.
thanks!!
Click to expand...
Click to collapse
Face unlock works fine. I have it paired with Pick to wake phone - so when I pick it up it wakes up to allow face unlock.
However, be prepared for some investment of time (not for face unlock).... I am a bit stuck now and cannot reproduce the above to get this working. Sometimes the results are different depending on base ROM etc.
Share how you get on and anything you may need to do to get this working.
Thanks
Nice work, i will try it .
The mi8 pro 's fingerprint is so bad which can be ignored, and the face unlock is the mostly used, hahahah
thank you very much for your work
Hi, I am waiting to unlock bootloader. Need 148hrs. Will install this. Thanks for sharing.
Quick update: There are some issues with GSI ROMs and the Mi 8 Pro. SOe of these relate to the SIMcard settings - and selection of preferred SIM for data, calls etc.
My experience shows that the vendor image from equuleus_global_V10.3.5.0.PECMIXM fixes many of these. The vendor image from the original MIUI ROM is used with the GSI system image to make the whole Project treble stuff work. I advise flashing this latest vendor image for maximum compatibility.
Do you know what issues remain after flashing the latest vendor image?
Does the face unlock on Pixel Experience work with IR camera or front cam?
I tried installing this and it got stuck on the loading screen with the Google logo. I tried following your instructions and a few other ways and couldn't get it to work at all i'm also not able to root my phone at all. When ever I try rooting my phone just reboots to twrp until I reflash the ram or flash the magisk uninstaller.
Do you have any tips, tricks, or suggestions I might try?
Thanks!
eremeya said:
I tried installing this and it got stuck on the loading screen with the Google logo. I tried following your instructions and a few other ways and couldn't get it to work at all i'm also not able to root my phone at all. When ever I try rooting my phone just reboots to twrp until I reflash the ram or flash the magisk uninstaller.
Do you have any tips, tricks, or suggestions I might try?
Thanks!
Click to expand...
Click to collapse
Have experienced this on occasion also.
What GSI image have you tried? after my multiple efforts, I would recommend... in this order: Omni. HavocOS, Descendant(no future updates), PIxelExperience. I am hopeful about the PixelExperience team who have made an announcement that as of August they will no longer produce CAF versions of PixelExperience, and that they will maintain regular GSI builds also. PE official GSI - I am full of hope.
Anyway, back on topic: Try this.
Follow the instructions - a few precisions:
Use XiaoMiFlash to flash the equuleus_global_images_V10.3.4.0 as a base. You can update the vendor partition once you have GSI up and running, but don't let the MIUI update to 10.3.5. Ensure you define a PIN to make sure that data partition is encrypted. (everyone should use encryption nowadays, and besides, I have had bad experiences whn using a xiaomi eu or mi-globe ROM (unencrypted) as the base
Reboot and finish basic MIUI setup. - What I mean here is to let the ROM boot, don't have to sign in to Google or Mi, but get to the home screen after the initial setup.
Then reboot fastboot and flash TWRP 3.3.0. Search for TWRP-3.3.0-0504-XIAOMI8UD-CN-wzsx150.zip.
Boot to TWRP. Make sure that you are able to decrypt the data partition with the PIN you set earlier. If TWRP does not ask you for the passcode / PIN - something is wrong. Try again. ONce all is OK in TWRP, perform factory reset. (DO NOT FORMAT DATA for the aforementioned encryption reason).
adb push the img file.
adb push the Magisk 19.3 zip.
Flash both in TWRP
Reboot TWRP
Reboot system. If it appears to hang, after 5 minutes you can force restart with the power button. I have had the ROM boot OK after second boot only?
Pretty sure that if you strictly follow the above you should get a working GSI image on Mi 8 Pro. Let me know...
It's a bit flaky to set up, but once set up, apart from fingerprint sensor not working, very stable and lovely to have the stock ish android system on a MIUI phone!
Be careful with preferred network type for mobile network as some selections have messed up incoming SMS messages for me... a dealbreaker.
What happens when you flash Magisk? What does TWRP say? Have you tried flashing Magisk, rebooting TWRP, and flahing Magisk again? It may be a TWRP version issue?
Thanks for your reply!
The version of twrp you mention is what I have used. I have not tried installing then rebooting to twrp so I try that.
When flashing magisk it usually flashes fine (I have had a couple times where it just throws an error) then when I reboot the phone will boot past the Mi logo the the Android boot logo then after 10-15 sec. it just reboots to twrp.
I was finally able to get the twrp to stick across boots by flashing twrp, signing boot image, removing twrp then reboot to Miui.
Do I need to adb push the GSI image or should it be fine to install from a USB drive?
The SMS issue isn't really a big deal for me as I use Google Fi routed through hangouts for one sim and a local sim where I'm living for mostly data and a few phone calls for the second one
Thanks so much for this post. I was completely oblivious to the fact that the Mi 8 Pro would actually be different to the Mi 8 when it comes to custom roms. When I decided on my next phone, I read the positive reviews and saw enough Mi 8 roms to be willing to make a switch to Xiaomi. Until I read your post I was close to despairing as I don't want a Xiaomi rom on my phone for various reasons (among them is the fact that I don't trust them and the way they have decided to collect user data).
I've tried to follow your guide in every step (I've also flashed the updated vendor.img), but unfortunately I have not been able to install the Pixel Experience rom on my device. I do see the boot animation but it never stops, I'm forever stuck with the Google-G and the progress bar below it. Has anyone else managed to install the Pixel Experience rom on the Mi 8 Pro? If yes, did you follow the guide here or did you do something else?
Also, in your initial post you write that we should wipe the system in TWRP but as far as I can tell GSI roms need you to wipe data, cache and dalvik cache but not the system partition (if you do it, you also don't get asked for your PIN code in TWRP any more, which - as you said - indicates that something went wrong).
Did you install a particular version of the Pixel Experience rom? Maybe that might be part of my issue?
I have try many times installing it. Didn't manage to boot it up.
Finally, tested with Miroom ROM as base then flash the system.img manage to boot up.
Don't know why it didn't boot but at lease any one who have issue booting may want to try using Miroom rom as base.
tllim73 said:
I have try many times installing it. Didn't manage to boot it up.
Finally, tested with Miroom ROM as base then flash the system.img manage to boot up.
Don't know why it didn't boot but at lease any one who have issue booting may want to try using Miroom rom as base.
Click to expand...
Click to collapse
What did you do to install miroom? I've been trying to install it and it just stays on the boot screen. The only non-official from I've been able to install and boot is the unofficial LineageOS rom by fenix-UK.
eremeya said:
What did you do to install miroom? I've been trying to install it and it just stays on the boot screen. The only non-official from I've been able to install and boot is the unofficial LineageOS rom by fenix-UK.
Click to expand...
Click to collapse
I install it using twrp 3.3.0 version. Build 0503. But before that I have install the stock rom goble stable version 10.3.5.0. update FW & Vendor using the same twrp.
tllim73 said:
I install it using twrp 3.3.0 version. Build 0503. But before that I have install the stock rom goble stable version 10.3.5.0. update FW & Vendor using the same twrp.
Click to expand...
Click to collapse
Thanks.
Is your phone a Chinese version or EU version? Were you able to root global stock rom?
eremeya said:
Thanks.
Is your phone a Chinese version or EU version? Were you able to root global stock rom?
Click to expand...
Click to collapse
Hi, I am using a Chinese version. But once you unlock it you will be able to flash any version with the twrp.
I try rooting it with magisk but unable to boot up. That's why I turn to Miroom Rom. They have done something which can boot it up.
tllim73 said:
Hi, I am using a Chinese version. But once you unlock it you will be able to flash any version with the twrp.
Click to expand...
Click to collapse
I'm also using the Chinese version but no matter what I try I cannot root the global version of the rom. I can root the Chinese version fine.
eremeya said:
I'm also using the Chinese version but no matter what I try I cannot root the global version of the rom. I can root the Chinese version fine.
Click to expand...
Click to collapse
Might be the developer version is only for the Chinese Rom. Anyway I am happy now running with GSI Rom.
eremeya said:
I'm also using the Chinese version but no matter what I try I cannot root the global version of the rom. I can root the Chinese version fine.
Click to expand...
Click to collapse
What version of TWRP are you using?

Back to Stock ROM

Hey guys,
can somebody help me to go back to the original firmware of the Galaxy Y?
I have model number GT-5363 (German 02 version, but same hardware as the normal GT-5360).
I tried to flash Lineage 9 and CM9, but it didn´t work, because I couldn´t install TWRP or the Custom Roms because of "wrong model number".
I asked afaneh92 and he told me to change the updater-script, which I did. Now I was able to install TWRP and the ROMs, but both Custom ROMs don´t go further than the bootscreen. One time I reached the Lockscreen with Lineage, but the phone seemed to be frozen then.
Since I still want to use my phone, I want to go back to Stock Rom or another (working) Custom Rom.
By the way: I wasn´t able to restore my backup with Clockworkmod 5.0.2.8. It seems to be a well known bug in this version.
Can somebody please help?

[GUIDE] Unlocked BL, Installed TWRP and Rooted but cannot install custom ROM...

This info is for people who are finding it difficult to install a custom ROM or who are just waiting for the right time to experiment. This method is fail-safe. Any support needed, I am here to help .
To start with:
I unlocked my RM5P bootloader was able to install custom recovery and even root my phone, but I was not able to install a custom ROM ----- till yesterday night (I am on EVO X now).
Failed attempts:
I was able to downgrade to RMX1971EX_11_OTA_0170 with stock recovery but after loading the ROM, I cannot load into FASTBOOT.. Again to get into fastboot, I needed to upgrade to CO1 (Android 10).
Then from fastboot mode, I tried installing ROM (very old version) thus maintaining the TWRP and Fastboot.
I tried to install custom ROM, it gave me error 7. This error is because the Firmware was too old for the custom ROM to be installed.
Success:
I then installed color os V 170 from TWRP (it can decrypt OZIP files-it will covert that to zip and install). Used just common sense, as all custom ROMs at present need color os (specifically version ...170), so after installing ROM using TWRP and staying in the recovery (because if I load ROM now, I will lose FB and TWRP), I Dirty Flashed (just to be on the safe side) custom ROM (EVO X) , and then format data (might still give you error, there is a workaround) and restart. That's it.
I am in Evolution X latest build.
ADVICE:
Whatever experiments you want to do on your mobile, do it while you are in WARRANTY (after confirming you have your service center nearby and working). If your phone ends up bricked (like me-before) get it fixed free of cost. BECOME A PRO WITHIN THE WARRANTY PERIOD.
Oh well that's extremely nice of you and useful. You're helping the community of this device a great deal with your informational and technical guides. I can safely thank you in the name of all users.
Though I'm feeling kind of sorry and bad for you. You really weren't able to use custom ROMs till 14th of May? Geez... That must've been horrible. I'm a fan of pure and stock like, simple, well modable/shapeable Android since I was a kid and got my Samsung Galaxy phone with Android 2.1 back in 2009. Since then I can't stand any limitation brought by Android skins like Miui or Color OS. I was on GSI ROM on the third day of having my Realme Q back in October of 2019. Not like warranty did count anything since there's no Realme in Hungary and it was an import device from AliExpress. So many testing and experience, lots of adventure. Can't even imagine what would I have done if I couldn't get rid of COS till now. Even the thought is maddening to me ? You've got my respect.
greenys' said:
Oh well that's extremely nice of you and useful. You're helping the community of this device a great deal with your informational and technical guides. I can safely thank you in the name of all users.
Though I'm feeling kind of sorry and bad for you. You really weren't able to use custom ROMs till 14th of May? Geez... That must've been horrible. I'm a fan of pure and stock like, simple, well modable/shapeable Android since I was a kid and got my Samsung Galaxy phone with Android 2.1 back in 2009. Since then I can't stand any limitation brought by Android skins like Miui or Color OS. I was on GSI ROM on the third day of having my Realme Q back in October of 2019. Not like warranty did count anything since there's no Realme in Hungary and it was an import device from AliExpress. So many testing and experience, lots of adventure. Can't even imagine what would I have done if I couldn't get rid of COS till now. Even the thought is maddening to me You've got my respect.
Click to expand...
Click to collapse
I appreciate your time and message.
I have only dared once in my lifetime to experiment on a tablet i bought online on the first day, that time i restored it with another rom, and even replaced that gadget after 2 days for another one because it didn't have multi touch, many years ago.
With realme, i was kind of scared to experiment till some months back and i even had to visit service centre thrice to restore. Now i have learned a bit on how we can BRICK our phone.
One important thing i learned is, STOCK rom is the best, and i am back on it.
Thank you.
jijojamie said:
I appreciate your time and message.
I have only dared once in my lifetime to experiment on a tablet i bought online on the first day, that time i restored it with another rom, and even replaced that gadget after 2 days for another one because it didn't have multi touch, many years ago.
With realme, i was kind of scared to experiment till some months back and i even had to visit service centre thrice to restore. Now i have learned a bit on how we can BRICK our phone.
One important thing i learned is, STOCK rom is the best, and i am back on it.
Thank you.
Click to expand...
Click to collapse
Ah I see! That's indeed a whole adventure. Thank you for sharing. It was worth reading
jijojamie said:
This info is for people who are finding it difficult to install a custom ROM or who are just waiting for the right time to experiment. This method is fail-safe. Any support needed, I am here to help .
To start with:
I unlocked my RM5P bootloader was able to install custom recovery and even root my phone, but I was not able to install a custom ROM ----- till yesterday night (I am on EVO X now).
Failed attempts:
I was able to downgrade to RMX1971EX_11_OTA_0170 with stock recovery but after loading the ROM, I cannot load into FASTBOOT.. Again to get into fastboot, I needed to upgrade to CO1 (Android 10).
Then from fastboot mode, I tried installing ROM (very old version) thus maintaining the TWRP and Fastboot.
I tried to install custom ROM, it gave me error 7. This error is because the Firmware was too old for the custom ROM to be installed.
Success:
I then installed color os V 170 from TWRP (it can decrypt OZIP files-it will covert that to zip and install). Used just common sense, as all custom ROMs at present need color os (specifically version ...170), so after installing ROM using TWRP and staying in the recovery (because if I load ROM now, I will lose FB and TWRP), I Dirty Flashed (just to be on the safe side) custom ROM (EVO X) , and then format data (might still give you error, there is a workaround) and restart. That's it.
I am in Evolution X latest build.
ADVICE:
Whatever experiments you want to do on your mobile, do it while you are in WARRANTY (after confirming you have your service center nearby and working). If your phone ends up bricked (like me-before) get it fixed free of cost. BECOME A PRO WITHIN THE WARRANTY PERIOD.
Click to expand...
Click to collapse
Can you guide me please , currently i am on realme ui c.04 latest update , wanna go back to color os ( for flashing custom roms ) how can i safely downgrade without loosing fastboot and custom recovery ( as of now bl is locked and everything is stock )
Here's the step i am thinking to follow
Unlocking bl and flashing twrp while in realme ui and from twrp flashing color os 6 zip file and and without booting , flashing the custom rom and then wipe data and then reboot
Will j have bootloader and recovery accessible then ?
grand2SD said:
Can you guide me please , currently i am on realme ui c.04 latest update , wanna go back to color os ( for flashing custom roms ) how can i safely downgrade without loosing fastboot and custom recovery ( as of now bl is locked and everything is stock )
Here's the step i am thinking to follow
Unlocking bl and flashing twrp while in realme ui and from twrp flashing color os 6 zip file and and without booting , flashing the custom rom and then wipe data and then reboot
Will j have bootloader and recovery accessible then ?
Click to expand...
Click to collapse
Correct. I had only twrp and no bootloader after installing custom ROM. Please avoid DIRTY FLASHING.
Gud luck.
jijojamie said:
Correct. I had only twrp and no bootloader after installing custom ROM. Please avoid DIRTY FLASHING.
Gud luck.
Click to expand...
Click to collapse
You saying avoid dirty flash then how to flash custom after color os ( assuming not booting into color os , staying in recovery )
Please help with steps after flashing color os through recovery
Andyou had no bootloader after custom rom , then how did you managed to get bootloader back
grand2SD said:
You saying avoid dirty flash then how to flash custom after color os ( assuming not booting into color os , staying in recovery )
Please help with steps after flashing color os through recovery
Andyou had no bootloader after custom rom , then how did you managed to get bootloader back
Click to expand...
Click to collapse
Avoid installing custom roms using duty flash, i mean the second custom rom should be done as clean install. I said that specifically because, i tried three roms in a span of 1 hour, the third duty flash (derpfest rom) gave me indefinite boot. Had to go to service centre because phone was not bootng to twrp.
I went back to custom rom, Android 10 to get BL back. Anyways, i was not that satisfied with the present custom roms available.
But that's me, you can go ahead and try roms.
jijojamie said:
Avoid installing custom roms using duty flash, i mean the second custom rom should be done as clean install. I said that specifically because, i tried three roms in a span of 1 hour, the third duty flash (derpfest rom) gave me indefinite boot. Had to go to service centre because phone was not bootng to twrp.
I went back to custom rom, Android 10 to get BL back. Anyways, i was not that satisfied with the present custom roms available.
But that's me, you can go ahead and try roms.
Click to expand...
Click to collapse
Thanks for help , but in any case , I don't wanna mess up to such extent that i have to go service center ,
Can scenario get that bad ?
I mean fastboot gone , twrp not booting up
Also you just flashed custom 10 rom from twrp n got bootloader
And one more thing i wanna try derpfest rom android 10 version
So please have a look at these steps
Color os zip flash by twrp , then wipe data without booting and flashing derpfest 10.0
How will that go , i mean will i have bootloader
grand2SD said:
Thanks for help , but in any case , I don't wanna mess up to such extent that i have to go service center ,
Can scenario get that bad ?
I mean fastboot gone , twrp not booting up
Also you just flashed custom 10 rom from twrp n got bootloader
And one more thing i wanna try derpfest rom android 10 version
So please have a look at these steps
Color os zip flash by twrp , then wipe data without booting and flashing derpfest 10.0
How will that go , i mean will i have bootloader
Click to expand...
Click to collapse
I suggest you check this with another derpfest user, please. I never got to boot to derpfest.
I downloaded Evolution X 4.7 Rom zip file and followed the instructions given in thread to flash zip file. But after flashing when I tried to reboot in system, it gave me a message on swipe screen that OS is not installed but still I swiped to boot in system. My device tried to boot a couple of time and ended up in fastboot again. Fortunately I had already made backup so I restored my backup.
As per your post I should have flashed color os 6 ozip file with twrp before flashing evox rom.
Every thing ok.i think you are not flash Vebeta after flash recovery.

Categories

Resources