[GUIDE] Unlocked BL, Installed TWRP and Rooted but cannot install custom ROM... - Realme 5 Pro Guides, News, & Discussion

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.

Related

Can't get back to miui rom

OK so I flashed aospa/los they are working fine. Wanted to try miui 9 so did advance wipe including data wipe. Now after flashing miui it says no is found in twrp. Restoring miui 8 its stuck on boot logo.
Flashing aospa/los is fine but can't get back to miui.
What can I do?
ermacwins said:
OK so I flashed aospa/los they are working fine. Wanted to try miui 9 so did advance wipe including data wipe. Now after flashing miui it says no is found in twrp. Restoring miui 8 its stuck on boot logo.
Flashing aospa/los is fine but can't get back to miui.
What can I do?
Click to expand...
Click to collapse
I'd try fastboot flashing with the MiFlash tool
On the MIUI forum they seem to use this as the best way to get back to stock.
It even has a "clean and lock" option to set the phone back to clean ROM and locked bootloader.
Pretty good actually.
Can grab the fastboot firmwares from en.miui.com and then tool as well.
Guides are easy to find on there as well.
Just extract the fastboot package (.tgz)
Then unpack the file from there (yeah I know twice ergh)
And then point the flash tool to the folder this creates.
Then you should be safe to flash.
That will get you back to clean device then you can install TWRP with fastboot again.
I'd go for the Global Developer ROM it's so much better than Stable.
And here's a tip for free: in developer settings disable "MIUI optimization" and set the memory optimization to "off". Makes it so much smoother and battery lasts longer as tasks aren't killed every 5 mins....
So I flashed a global v8 ROM and that worked. Had to install twrp again. Now when I flashed v9 eu ROM after standard wipe, its just on the boot logo with powered by android.
ermacwins said:
So I flashed a global v8 ROM and that worked. Had to install twrp again. Now when I flashed v9 eu ROM after standard wipe, its just on the boot logo with powered by android.
Click to expand...
Click to collapse
I think you need to use fastboot.
I think normally it would work but one of your partitions must be messed up from another Rom.
It's rare but it does happen and full flashes are needed.
At least MIUI 8 worked
Dobsgw said:
I think you need to use fastboot.
I think normally it would work but one of your partitions must be messed up from another Rom.
It's rare but it does happen and full flashes are needed.
At least MIUI 8 worked
Click to expand...
Click to collapse
I'm gonna try 1 more time with this weeks EU rom but eventually will be on a non miui rom
ermacwins said:
I'm gonna try 1 more time with this weeks EU rom but eventually will be on a non miui rom
Click to expand...
Click to collapse
Tbh it may be a complete waste of time.
If you like pure android feel then you won't like MIUI much.
It was okay but its basically what iOS would be if Apple got their sh*t together and gave users more control.
I think that's what Xiaomi was aiming for really as they copy a lot of Apple design types.
Which for is means good hardware and choice of softwares so its definitely a plus.
BL unlock was a dream
Dobsgw said:
Tbh it may be a complete waste of time.
If you like pure android feel then you won't like MIUI much.
It was okay but its basically what iOS would be if Apple got their sh*t together and gave users more control.
I think that's what Xiaomi was aiming for really as they copy a lot of Apple design types.
Which for is means good hardware and choice of softwares so its definitely a plus.
BL unlock was a dream
Click to expand...
Click to collapse
Miui was very good a few days then it started to get bloated so I moved away from it. They get some things right but pure android has improved a lot.
Which rom you rocking now?
ermacwins said:
Miui was very good a few days then it started to get bloated so I moved away from it. They get some things right but pure android has improved a lot.
Which rom you rocking now?
Click to expand...
Click to collapse
LineageOS Nougat.
Not so amazing for visual customisation, but definitely the most stable which means creating mods or adding them isn't as likely to cause issues.
I just want a ROM close to AOSP with all the features of the phone working like fast charging.
AOSPA looks good too.
Just flash again with fastboot ROM and mi-flash tool.
So I just got the OnePlus 5T and wanted to do a speed test comparison for my YouTube channel. I noticed temple run 2 exits. So want to try EU ROM but it gets stuck on bootlogo. Does anyone have a link to the fastboot ROM? Can only find an old one. I can flash the global ROM through with twrp which works fine. Flashing EU ROM fails.
Also will flashing through fastboot lock the bootloader?
I think you should wipe everything and wipe data if you have fbe because it messes up things
So I flashed a stock rom (sagit_global_images_V8.2.2.0.NCAMIEC) with mi flash tool. Unlocked it, installed twrp. Now flashed latest rom eu rom and its stuck on bootlogo still
ARGHHHHHH
Finally worked
After flashing EU ROM, enter fastboot mode and type
fastboot format userdata
(This will format all the data on your phone)
Reboot. Done.
Click to expand...
Click to collapse
https://xiaomi.eu/community/threads...mi-logo-after-flash-eu-rom.39979/#post-398231

Oldtimer turned NUBE question

Hey everyone,
I have been rooted for a LONG time, but have been gone for a year or 2. I have the OnePlus 3 that IS rooted with:
Experience OS R11.0 with
Kernel 3.18.31-perf+
[email protected] #1
7.1.1
OP3_o2_open_18
This one has served me well, but may be a bit obsolete.
What rom and kernel can I use now from 7.1.1 What must I do? I see 8.0 and such, and a host of others. Will I lose everything if I upgrade to a new version? I always do a nandroid, and I have Titanium Backup, which I THINK keeps apps, etc...
I remember having trouble installing Roms way back when. Not sure if it was a TWRP issue, as I also had Philz at one point. ( I Have TWRP now, but not sure which version) I had to use what i have (Which IS a GREAT ROM) because I was afraid to brick my phone, because I had so much trouble getting a rom to load. I constantly remember the little android falling over saying "Leave me the **** alone. If I boot to recovery, I just get the TWRP screen 3.1.0.0 that never opens. It just stays on that page and never opens, so I have to turn off the phone to reboot to turn on
I sincerely apologize for not remembering or keeping up.
Have a great day
wascapsfan said:
Hey everyone,
I have been rooted for a LONG time, but have been gone for a year or 2. I have the OnePlus 3 that IS rooted with:
Experience OS R11.0 with
Kernel 3.18.31-perf+
[email protected] #1
7.1.1
OP3_o2_open_18
This one has served me well, but may be a bit obsolete.
What rom and kernel can I use now from 7.1.1 What must I do? I see 8.0 and such, and a host of others. Will I lose everything if I upgrade to a new version? I always do a nandroid, and I have Titanium Backup, which I THINK keeps apps, etc...
I remember having trouble installing Roms way back when. Not sure if it was a TWRP issue, as I also had Philz at one point. ( I Have TWRP now, but not sure which version) I had to use what i have (Which IS a GREAT ROM) because I was afraid to brick my phone, because I had so much trouble getting a rom to load. I constantly remember the little android falling over saying "Leave me the **** alone. If I boot to recovery, I just get the TWRP screen 3.1.0.0 that never opens. It just stays on that page and never opens, so I have to turn off the phone to reboot to turn on
I sincerely apologize for not remembering or keeping up.
Have a great day
Click to expand...
Click to collapse
Wow.. Not one answer. What happened to the days where you ask a question, you get ridiculed, then many come out of the woodwork to get you on track...
Oh well........
wascapsfan said:
Hey everyone,
I have been rooted for a LONG time, but have been gone for a year or 2. I have the OnePlus 3 that IS rooted with:
Experience OS R11.0 with
Kernel 3.18.31-perf+
[email protected] #1
7.1.1
OP3_o2_open_18
This one has served me well, but may be a bit obsolete.
What rom and kernel can I use now from 7.1.1 What must I do? I see 8.0 and such, and a host of others. Will I lose everything if I upgrade to a new version? I always do a nandroid, and I have Titanium Backup, which I THINK keeps apps, etc...
I remember having trouble installing Roms way back when. Not sure if it was a TWRP issue, as I also had Philz at one point. ( I Have TWRP now, but not sure which version) I had to use what i have (Which IS a GREAT ROM) because I was afraid to brick my phone, because I had so much trouble getting a rom to load. I constantly remember the little android falling over saying "Leave me the **** alone. If I boot to recovery, I just get the TWRP screen 3.1.0.0 that never opens. It just stays on that page and never opens, so I have to turn off the phone to reboot to turn on
I sincerely apologize for not remembering or keeping up.
Have a great day
Click to expand...
Click to collapse
Make sure you have the latest TWRP by Bluspark, it just works flawless for me and alot of other people.
Take a full backup. Wipe system and both cache partitions. Then flash the latest Experience ROM. For the open beta releases I should stick with stock kernel. Otherwise Franco and Flash kernel would be interesting. For root I should go with Magisk. Everyone uses it nowadays and the modules are super handy.
Twrp issues
I have rooted the One Plus 3. I loaded TWRP about a year and a half ago. Now when I try to go into recovery, TWRP comes up, but never opens. I tried removing it, but it wont remove, and I try to reinstall it using several methods including apps, but to no avail. The bootloader is unlocked and the debugging is on. Any suggestions. I can't do a backup or anything.
Thanks
Dave
wascapsfan said:
I have rooted the One Plus 3. I loaded TWRP about a year and a half ago. Now when I try to go into recovery, TWRP comes up, but never opens. I tried removing it, but it wont remove, and I try to reinstall it using several methods including apps, but to no avail. The bootloader is unlocked and the debugging is on. Any suggestions. I can't do a backup or anything.
Thanks
Dave
Click to expand...
Click to collapse
Boot into fastboot, then connect it to your pc and use fastboot flash recovery. Get the latest TWRP.
I tried that, but it won't take. If I had a tar file, I could try it with Odin, but no matter what I do, when I go into bootloader, it says I'm unlocked, then I try to go into recovery, and TWRP shows up, but typically you get the different choices like backup, install, etc... I stay stuck on the TWRP page, that does not do anything, nor does it give me any choices. I have to shut the phone down each time just to get it back to working mode. I tried the adb method using the cmd prompt, and everything works up to trying to actually flashing TWRP...
wascapsfan said:
I tried that, but it won't take. If I had a tar file, I could try it with Odin, but no matter what I do, when I go into bootloader, it says I'm unlocked, then I try to go into recovery, and TWRP shows up, but typically you get the different choices like backup, install, etc... I stay stuck on the TWRP page, that does not do anything, nor does it give me any choices. I have to shut the phone down each time just to get it back to working mode. I tried the adb method using the cmd prompt, and everything works up to trying to actually flashing TWRP...
Click to expand...
Click to collapse
You may have to flash the original recovery by oneplus , you can find it on one plus downloads in google , make sure before you do anything that you backup anything important like photos , videos to a computer , then download the ROM of choice along with the correct gapps for that ROM and the correct firmware ( most ROMs will include the recommended firmware in their post ) , also download the latest twrp recovery from twrp.me and magisk ( if not included in the ROM ) then its just a matter of wiping system , data , cache and dalvick whilst in twrp , install the ROM with the gapps let the ROM boot and setup a few of your settings then go back into twrp and flash magisk manager and you should be good to go , good luck and make sure you fully read the instructions on the ROM page that you want ...

Advice/suggestions on best stable custom rom for new Moto G5 Cedric (XT1671)

Hi, I'm replacing a lost Moto G3 TE with a Moto G5 (xt1671 dual sim) that should be coming in the mail on Monday. I'd like to do whatever mods I want to my phone right away, before activating my google account on it and everything. So, I'd really like any advice any of you can give as to preferred custom rom with root that I should put on my new phone, so I can get to it right away. I've already found the thread to unlock it (same process as in past mostly), and I've found the guides for putting on TWRP (either 32-bit or 64-bit). So, now I just need to decide which custom ROM to use. Please advise!
I've also had a Moto G2 in the past. I've unlocked and used custom roms and root on all my phones so far, from Cyanogenmod 12.1 to AOSP Extended, ViperOS, and LineageOS. My wife's Moto G2 has Oreo on it (through AEX) and we're enjoying it (I had her add me as an account until I get my new phone). So, I'd like to continue using an Oreo system if possible, and I'd even prefer AEX, but it seems that it's discontinued for the Moto G5. Is that correct?
My overall goals for a custom rom are, in order of priority: reliability, speed/performance, battery life, and customization options. I found that AEX balanced all of that well on our past phones. Is the discontinued AEX for this phone reliable, or not? I've also seen the LineageOS thread and the KAOSP thread and have glanced at a few others. I use google accounts and half their apps for sure (so I'll want to install a GApps package with it). And I see there's a possibility to unlock RAW/DNG files for the camera, which I'd really like to try (as I prefer raw file editing instead of JPGs). And the customizations I like (if still possible) are mainly involving the way the launcher responds - I like having the navigation buttons hide, or to swipe up to get them back, I like being able to modify the status bar, etc.... typical customizations that were usually available in AEX that I've used. I also use root for file explorer and a few other functions - I used to always use SuperSU in the past, but just recently started using Magisk (on the Moto G2) and it seems good, though I'm open to any recommendation about which root to use.
So, please fire away! Please give your suggestion as to which currently available custom ROMs are stable, have good performance, good battery life, and offer standard customization, plus which I can root. I appreciate any suggestions and any advice you can give, especially regarding if there's a recommended rom but if it has known issues and any known workarounds. Also, I'd appreciate advice anytime today or tomorrow (since it'll likely be the afternoon or evening of Monday +3 GMT time - Madagascar - that I'm able to start working on unlocking it, installing custom recovery, etc.). But even if the advice is late, I might still be able to use it. I know this is a bit much to ask, but please give your own opinions freely!
Oh, by the way, do I need updated Motorola drivers, or will the motorola drivers and adb/fastboot I installed last time (for the Moto G3 TE) keep working with the new phone? The unlock thread I've found here doesn't say anything about motorola drivers or adb/fastboot. Thanks in advance!
the best stable rom is stock rooted
woozie.2007 said:
the best stable rom is stock rooted
Click to expand...
Click to collapse
Thanks for the response! Is there a stock oreo available? And is stock rooted still customizable (like with AEX or something - can I install some sort of thing to let me customize it more?). And is there a debloated version of the stock rom available? I saw one thread on here about a debloated stock rom, but it looked like it was still nougat.
If it's possible to customize the stock rom further, please point me in the right direction. And if not possible to customize it further... then are you suggesting that any of the custom roms available aren't very stable to be used well for a daily driver?
Again, thanks for your response and also for any more feedback you can give!
So, I have my phone now and it came with stock Nougat. I've unlocked it, and I'm currently working on getting TWRP, Dm-verity thing on it, and then magisk. After that can I still update it to Oreo or not? Please advise. Thank you!
madagascaradam said:
So, I have my phone now and it came with stock Nougat. I've unlocked it, and I'm currently working on getting TWRP, Dm-verity thing on it, and then magisk. After that can I still update it to Oreo or not? Please advise. Thank you!
Click to expand...
Click to collapse
no, you have to update oreo first, after that install twrp and magisk for root it
woozie.2007 said:
no, you have to update oreo first, after that install twrp and magisk for root it
Click to expand...
Click to collapse
Crud, that sucks! I was already finished rooting and everything on magisk, then I let the OTA update download and when it restarted my phone, it just automatically sends it into recovery (TWRP) every time now! I tried to install this TWRP stock Oreo (dirtying flashing it) hoping it would fix the boot-loop-to-TWRP-recovery problem, but it didn't. So now I need to figure out a way to get back to the original, so I can start over and try again.
I'm trying to do a factory reset and try again, but in TRWP it says ""Failed to mount '/data' (Device or resource busy)'" This sucks! Any ideas where I can go or what I can do (such as some fastboot commands or something) to get it all working again?
EDIT: It does reboot to bootloader though, so it's not hardbricked. Just need to figure out what to do from here. Thanks for any help!
try to flash via fastboot only boot, recovery, oem and system from oreo, then aply update, then root
Thanks! I downloaded the firmware (for latest Nougat) from this thread: https://forum.xda-developers.com/g5/development/stock-upgrade-to-official-stock-oreo-8-t3823598
Then I flashed everything they said through fastboot (ignoring the modem stuff) because I'm still downloading the oreo firmware right now anyway (my connection is quite slow). At first the bootloader got stuck and said "error" and I was freaking out thinking I'd hard-bricked it. But I turned it off and on again anyway and it loaded fine back into nougat for that latest version.
So now I'm downloading the latest stock Oreo and I'll probably try to ADB sideload it.
Which root do you recommend? I have the Magisk I did for nougat that worked great - 11.6 But there's this thread here (https://forum.xda-developers.com/g5/how-to/guide-how-to-root-stock-oreo-8-1-soak-t3832347) that talks about what seems like a complicated way of doing Magisk 15.3 and then getting it up to 16. What do you suggest?
magisk 17.1 its ok, but you have to flash only partition that i said, not full firmware, and DONT flash the bootloader and GPT partition
---------- Post added at 06:11 PM ---------- Previous post was at 06:10 PM ----------
better let the phone to update ota for latest security patch, dont flash via fastboot
OK, I installed the stock oreo through ADB sideload (it wouldn't read my storage for some reason).... then I reinstalled TWRP, no problem... then installed Magisk 17.1 (per your suggestion) and then the apk for the manager. Everything's working great! Didn't even need that dm-verity thing.
I'm still looking into the mods I can do to it now that it's rooted (such as changing boot logo and boot animation, adding that 'camera 2' setting, etc.) So I'm not sure I'm at a finished product yet, but I'm definitely at a stable rooted oreo with all my regular stuff installed, so that's a good place to start! I've made a nandroid backup here in case any of my further experimenting messes it up.
Thanks again for your help! And if you can give any suggestions towards the best way to customize the look (for example - is nova launcher still the best way to do that?) or other aspects of the system UI, while still being on this stock rom, then please let me know. I'll look up how to get that better camera mode working.
woozie.2007 said:
magisk 17.1 its ok, but you have to flash only partition that i said, not full firmware, and DONT flash the bootloader and GPT partition
---------- Post added at 06:11 PM ---------- Previous post was at 06:10 PM ----------
better let the phone to update ota for latest security patch, dont flash via fastboot
Click to expand...
Click to collapse
Could you help me with this: if I backup my system (everything) with TWRP.... can I then switch to a custom rom to try it out (in case I want a different user interface, more tweaks, etc.) and if I don't like it can I easily switch back to the stock rom nandroid backup I have saved in TWRP (thus restoring my previous state, but without having to start from factory reset)? Or would it be difficult to switch back - like would I have to redo it through fastboot or something and factory reset, etc.?
I'm asking because in the past I never used the stock rom much and I definitely never switched between a custom rom and the stock rom. Once I went for custom rom, I didn't go back - so I don't know if it's as simple as restoring a nandroid backup or if it's much more effort. Please let me know. Thanks a lot!
you must be very carefully because most of the custom roms need twrp on 64 bits, now you have official twrp 32. When you come back from custom roms 64bit to previous nandroid backup, you must install 32 bits twrp, otherwise you may lose the imei of the phone, just read very well when you want to do something risky
woozie.2007 said:
you must be very carefully because most of the custom roms need twrp on 64 bits, now you have official twrp 32. When you come back from custom roms 64bit to previous nandroid backup, you must install 32 bits twrp, otherwise you may lose the imei of the phone, just read very well when you want to do something risky
Click to expand...
Click to collapse
OK, thanks a lot for that helpful info! So just to clarify to be sure: basically, if I want to switch back and forth, I'll install the 64-bit twrp first, then the custom rom(s). Then if I want to come back to my stock image backup, I re-install the 32-bit twrp (like the one I'm currently using) and then I can just restore my nandroid backup I took of the stock and all is well? And it's not risky if I do it like that?
yes, its correct that

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

Clean ROOT ready to install ROMS REDMI NOTE 8 PRO [GLOBAL] ONLY Guide

So I've read enough posts to get this first - GLOBAL ONLY I got my phone on Amazon its a global unlocked NOTE8PRO. Any of you with something else like China or India try this method and brick your phone don't cry to me over it. After trial and error, bricking my device and paying some guy in Spain 30EUR to unbrick it (thanks brother you rock) I thought I'd share my final experience and how you can get your GLOBAL RN8P to a stable place to install the ROMS available at this time. I will include at the end my thoughts on the 2 ROMS I installed and used over the past week. Honestly if you're on a global version I'm not sure it's worth it although as I type this I kinda want to flash Pixel Experience again, I really liked it. But more on that later. I compiled this guide from sources here, if I don't give you credit I apologize in advance please just let me know.
First let's make sure we don't brick this mofo.
Hit the MEGA thread if you haven't read it then you shouldn't be flashing your phone, and do this from a clean install of MIUI-V11.0.6.0PGGMIXM and do yourself a favor and get it from Xiaomi or a reliable source, not everyone on here has good intentions. There are some "official" ROMS out there that have been played with and will break your phone.
1. Do it how you want I did this from fastboot. Dump the official MIUI global ROM in a folder, and (I'm on linux box so adjust yourself if you're sadly using Windows) I executed this command from FASTBOOT in the MIUI ROM folder with ADB and FASTBOOT installed for my system.
./flash_all.sh (I think its flash_all.bat for Windows)
This going to wipe your stuff out, have it backed up. I'm dedicated to Google and GDRIVE I don't care I get everything back when I wipe including sms and phone records etc, but to each his own.
It's going to wipe and restore to factory image on that ROM version and you're going to go throught setup again, tedious (I say that having done it 4 times this week) but none the less it is what it is. After you are up and running on that ROM version keeping in mind if you're going to flash a new ROM like PE then don't set it up all the way because you're going to do it all over again anyways move to the next step.
2. From the MEGA thread flash this and reboot. Read the thread download the files and do what Agent_fabulous (awesome guy btw) says. Reboot. Make sure you can reboot to SYSTEM and all is well, don't worry about recovery or bootloader yet.
Code:
fastboot flash preloader preloader_begonia.bin
fastboot flash lk lk.img
fastboot flash lk2 lk.img
3. OK kids we're almost there, now you need to install TWRP and there are MANY versions floating around. Honestly the official version sucks IMHO. go to this thread and download TWRP and do exactly what it says in the thread. Assuming you're device is unlocked already and if its not then come back later follow EXACTLY steps 2 and 3. From there you will update MAGISK after the reboot and be fully rooted and pass SaftyNet checks.
You are stable and rooted. All you do next is enjoy your rooted device and or install a custom ROM. If you do install a custom ROM - READ READ READ and FOLLOW directions I hate to add to the confusuion but there are so many threads on this phone (becasue it sucks to MOD it) and it's frustrating because all of it assumes you know everything or they just don't give you all the steps and you end up bricking your phone. I have never by the way rooted or flashed a phone in my life before this one.
At this time all the custom ROMS need to be flashed after flashing the Indian Vendor image, this is in fact the only way I know and it worked for me everytime. So at this point if you're flashing a new ROM first flash the India Vendor image then flash the new from all from TWRP. But in my experience just follow what it says because Agent_fabulous and friends may crack this tomorrow and it won't be the same. What I am giving you is a VERY stable platform to start flashing ROMS from or just to be rooted and happy. As an FYI from this you can install RIRU and EdXposed if you want to do that, I wasn't impressed other than dark mode in GMail on A9 and ad-blocking in YouTube, I get the ads in YouTube but Google no dark mode in GMail on A9? WTF??
Happy rooting and ROMing.
DC.
Hi, I would want to ask you some questions. Is it completely fine to flash ROMs? And by it, would it help out fix battery usage? Eg: Android system. Pretty much why I am looking forwards by flashing custom ROM's. And, have you tried Pixel Experience on the global version of redmi note 8 pro? I am looking forward to it.
Auerox said:
Hi, I would want to ask you some questions. Is it completely fine to flash ROMs? And by it, would it help out fix battery usage? Eg: Android system. Pretty much why I am looking forwards by flashing custom ROM's. And, have you tried Pixel Experience on the global version of redmi note 8 pro? I am looking forward to it.
Click to expand...
Click to collapse
Given how aggressive the battery optimizer is on stock, I doubt you'll get more juice out of it.
Auerox said:
Hi, I would want to ask you some questions. Is it completely fine to flash ROMs? And by it, would it help out fix battery usage? Eg: Android system. Pretty much why I am looking forwards by flashing custom ROM's. And, have you tried Pixel Experience on the global version of redmi note 8 pro? I am looking forward to it.
Click to expand...
Click to collapse
It's fine to flash ROMs I felt PE was way faster the audio was better over Bluetooth and it was pretty stable. Battery improvement was negligible.
@dcindallas glad you had such a nice experience. have you tried flashing miui 12 on it? seems there are some beta versions for it. seems to bring a lot of eye candy, privacy and performance fixes. give it a go.
@dcindallas hi, can you please add a portion for updating miui rom through twrp (when new version available) the procedure. thanks.
I've not flashed anything but custom ROMS I had to wipe go back to A9 stock ROM due to Pixel Experience dropping wifi constantly.
Well, I appreciate all the effort going into this thread and this device. Thru all the reading I've done on this simple project with different advice, it almost seems there's too much info on it. Anyway, I'm having a dickens of a time with it, just getting it to load up TWRP! I thought I followed all the directions.. y'know... hold this button, dont hold this one, release this one, then repress that one... but I got a bootloop just from flashing TWRP. I had to re-flash the whole MIUI (an older one even) with Mi Flash, the only one I could find that had a flash-all script in it.
I'm a little gun shy, but I'd sure like to give it a go again.
I flashed twrp-3.3.1-0-begonia.img, then rebooted. Any advice why I bootlooped? Was it the TWRP version or did I mess up the button press?
Cheers

Categories

Resources