Develop Bugs

T-Mobile OEM unlock

Has anyone tried unlocking a T-Mobile g7 bootloader from the developer options? I've turned on developer options and OEM unlock option is in there but I haven't connected it to pc to check with ADB.

only the EU bootloader has been unlocked, something to do with TMO releasing some keys or something for the secuity, I believe. I know on HTCs I used to have TMO had certain encryption on wifi calling and a few signatures that were broken by touching the security partition needed to gain root and install custom OSs. Once LG updates their bootloader unlock page to include TMO version G7 (I have one, too) then we'll see a KDZ thread and then root

cohan1219 said:
Has anyone tried unlocking a T-Mobile g7 bootloader from the developer options? I've turned on developer options and OEM unlock option is in there but I haven't connected it to pc to check with ADB.
Click to expand...
Click to collapse
Root is unlikely on the T-Mobile variant due to T-Mobile using different RSA Encryption keys compared to every other carrier, also the development for this phone is basically one guy. I hope I'm wrong about it being unlikely but from what I've been reading and what I've been told it's a slim chance it's going to happen

Joe199799 said:
Root is unlikely on the T-Mobile variant due to T-Mobile using different RSA Encryption keys compared to every other carrier, also the development for this phone is basically one guy. I hope I'm wrong about it being unlikely but from what I've been reading and what I've been told it's a slim chance it's going to happen
Click to expand...
Click to collapse
Thanks for the update, I guess if there's not root by November its time to switch to the OnePlus 6T.

sharpknight said:
Thanks for the update, I guess if there's not root by November its time to switch to the OnePlus 6T.
Click to expand...
Click to collapse
I think the 6T is going to be on TMobile if that's the case I shall be doing the same, I do love this phone don't get me wrong but I've always wanted a one plus device and having root again would be great as well

that one guy is checking the bootloader again and trying to help us ive been taking to him hope he's right about them locking it the same way give it a little time he thought bootloader was unlocked he doesn't have the device there's others we can't give up man adb root is possible prob hacking laf maybe possible and there's a way someone will get it anyone trying to I'll also help to

Joe199799 said:
I think the 6T is going to be on TMobile if that's the case I shall be doing the same, I do love this phone don't get me wrong but I've always wanted a one plus device and having root again would be great as well
Click to expand...
Click to collapse
Tell me something. What's the real use for root now-a-days? My z2 force is rooted and is super buggy. Hardly any Xposed apps are even working anymore. This phone is super solid and reliable. It's also a lot further ahead than the one+ 6T will be.

20degrees said:
Tell me something. What's the real use for root now-a-days? My z2 force is rooted and is super buggy. Hardly any Xposed apps are even working anymore. This phone is super solid and reliable. It's also a lot further ahead than the one+ 6T will be.
Click to expand...
Click to collapse
Honestly I just want it for viper4android literally that's it and maybe greenify and adaway other than that I'm good.
Honestly I probably won't switch over I'll just deal with it

20degrees said:
Tell me something. What's the real use for root now-a-days? My z2 force is rooted and is super buggy. Hardly any Xposed apps are even working anymore. This phone is super solid and reliable. It's also a lot further ahead than the one+ 6T will be.
Click to expand...
Click to collapse
Greenify was the biggie to me particularly with the Xposed module. Titanium Backup. Disabling system apps that the UI wouldn't let me disable. (Maybe that can be done via adb w/o root. I should try.) BootManager. MinMinGuard. Worthwhile system-wide font replacement w/o bloat. (No apps, no junk, no "apps that don't support <thing> or <favorite font>", just replacing files in /system/fonts.)
Lots of other little things that -- added together -- made my phone just that much nicer to me.
I'm really happy with my G7 all around (except for the WiFi stability, that still sucks). I just wish I had all those little tweaks back.

I made a post about a week ago but never got any replies. Has anyone else ran the "fastboot flash unlock_critical" command? My phone restarts and shows the erasing screen but no actual bootloader unlock.

Any updates?

I'll try out when I make it back home sorry was flooded here we either need to mod kernel or laf aand github has a repo on some I'm checking on I'll be able to check more sorry and package disable pro will freeze apps or use autoprimes way on rooted you can use twrp file manager to delete system apps on moto z2 oem can't be touched but there's ways

the aristo 2 has different commands has anyone tried that way and we still need a twrp to flash their is thread about making one we can get somewhere this would be a great phone with root without it sucks

ecompton59 said:
the aristo 2 has different commands has anyone tried that way and we still need a twrp to flash their is thread about making one we can get somewhere this would be a great phone with root without it sucks
Click to expand...
Click to collapse
What are the different commands?

Okay I've tried the fastboot critical command same went to erase screen with the circle but fastboot flashing get_unlock_ability comes back 1 I've extracted kdz to dz still playing around trying

sign the petition to LG
https://www.change.org/p/lg-electro...ion&utm_term=b1c99c243f314531935fa8ffc92c4c4f

There is an option for the T-Mobile version. Can someone actually try continuing with the progress?
I can't since I don't have the T-Mobile version.

LGM710TM is LG G7 from Italian provider TIM.
It has nothing to do with T-Mobile.

awww

umminkug said:
https://www.change.org/p/lg-electro...ion&utm_term=b1c99c243f314531935fa8ffc92c4c4f
Click to expand...
Click to collapse
There's been petitions for like every locked-down LG device since the beginning of time. Never has it been effective, never will it be. LG doesn't reverse its bootloader locking policy.

Moto G7 Play bootloader unlock issues - "bad key", not OTA, no way to roll back?

Moto G7 Play bootloader unlock issues - "bad key", not OTA, no way to roll back?
My plan was to unlock the bootloader before configuring the new phone - just in case I might need it later, then use the phone as out-of-box. I unlocked the bootloader for the new Moto G7 Play, following the official procedure via the Motorola Accounts page, resulting in:
- Fastboot page shows: "flashing unlocked"
- When booting up, I see a black page with the words "bad key", then the phone boots
- The updater sais that the phone is corrupt and no (OTA) updates can be done
- I could not try TWRP, as there is no TWRP for the G7 Play yet (so not sure if flashing would work)
My concerns now are that I will not be able to update the phone, and that the "bad key" issue might cause other problems.
So my plan would be to roll back and lock the phone again, to use it as out-of-box (not worrying about warranty loss that might already have happened - I did accept these terms). However, that does not work, too:
- Locking bootloader requires factory images, which are not available for the G7 Play
- Locking bootloader with fastboot OEM lock will not work without complete images
Any suggestions how bring the phone back to normal? I am disappointed by Motorola, as they officially offer the unlock procedure - which then does not produce the expected outcome, breaks updating, and provides no way to go back? Mind you, I did not apply any "hacks", nothing but the official Motorola unlocking steps.
Thanks for advice

I have the same problem and i cannot fix it.

I tried to get advice from Motorola support - but replies are very generic, referring to the bootloader unlock page (we obviously found that) or to the Motorola Forum (where the answer isn't). Will now just live with the unlocked phone and hope for the opportunity to OTA / update in a while

CoffeeMachineSwitch said:
- When booting up, I see a black page with the words "bad key", then the phone boots
- The updater sais that the phone is corrupt and no (OTA) updates can be done
Click to expand...
Click to collapse
Unlocking any Motorola bootloader will cause the bootscreen to display "Bad Key". This is normal. It is a warning that the bootloader has been unlocked and the phone may not be "safe". Once you root a Motorola phone, it will display "N/A" instead of "Bad Key". Again, this is normal behavior. There are image makers that can replace the "splash" image and "hide" the "N/A", but since this phone doesn't have TWRP yet, you'll have to live with it for now.
As far as not being able to receive OTA updates, I have no knowledge. In my opinion it shouldn't matter that the bootloader has been unlocked...only if you've modified or deleted system files. I've never worried about system updates as I've always rooted and run custom ROMs, or Xposed (which negates eligibility for OTA).

mn1968 said:
Unlocking any
As far as not being able to receive OTA updates, I have no knowledge. In my opinion it shouldn't matter that the bootloader has been unlocked...only if you've modified or deleted system files. I've never worried about system updates as I've always rooted and run custom ROMs, or Xposed (which negates eligibility for OTA).
Click to expand...
Click to collapse
Thanks for clarifying. And yes, learnt from Moto Support that OTA was disabled for 7 generation

CoffeeMachineSwitch said:
Thanks for clarifying. And yes, learnt from Moto Support that OTA was disabled for 7 generation
Click to expand...
Click to collapse
That would be an unfortunate change if true. Prior devices could be unlocked and still get OTA updates. They won't install if certain changes are made but still get notified of updates.

You still can install full ROM using fastboot commands and regain root by patching boot.img from updated ROM
I did it on both G6 and G7

Where did you get the ROM images from. I understand there are no officials?

CoffeeMachineSwitch said:
Where did you get the ROM images from. I understand there are no officials?
Click to expand...
Click to collapse
Have you tried the LMSA tool? It's a tool you download from Motorola. There is a discussion here about it. It has a rescue button with which, I understand that you can download stock images directly from Motorola, but I haven't used it myself.

umbrisle said:
Have you tried the LMSA tool? ....
Click to expand...
Click to collapse
Yes I have - the last time I tried, however, it said that it would not support the G7 (Play) and did not provide any images/ROMs

CoffeeMachineSwitch said:
Yes I have - the last time I tried, however, it said that it would not support the G7 (Play) and did not provide any images/ROMs
Click to expand...
Click to collapse
I was thinking of buying a G7 Play myself, but I am now leaning more towards a G6 Play, because there are more tools available like a working TWRP.

Should've read the thread here before i go buy g7 play, not my phone get softbricked.
Unblocked bootloader successfully following the official doc but failed to install magisk by copying the wrong build number of boot.img of OTA from here mirrors.lolinet.com/firmware/moto
now my g7 says
Code:
failed to load kernel, no Bootable A/B slot,
Failed to book Linux
falling back to fastboot.
I downloaded `RIVER_RETAIL_9.0_PPO29.80-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC` which i think this is the right build number when i see error like
Code:
river/retail corrupted
(can't remember exactly, but it's RETAIL not RETUS)
and make my own version of fastboot command stemming from servicefile.xml, still with unlucky.
there is no recovery.img and google has limited resource to make g7 play back to stock orm, i'd like to see if community has any idea or i have to give it to moto to fix it.
========================update=================================
update: i finally get the correct stock ORM which is exactly matching my build number "XT1952-4_CHANNEL_AMZ_9.0_PPY29.105-36_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC" i was an idiot thinking that mismatch one letter or two will be find, but turns out this is very strict, "second time rooting in my life".
not i has flash all of the original orm into my phone then fastboot reboot works, it give me the original error like
Android Recovery
motorola/channel_retail/channel9/PPY29.105-36/d7abeuser/release-keys
Use volum up/down and power
can't load Android system. Your data may be corrupt.
If you continue to get this message, you may need to perform a factory data
reset and erase all user data stored on this device
=====
Try again
Factory data reset
Click to expand...
Click to collapse
now i need to figure out what to do next
===============update=========
lol, turns out just press Factory data reset will bring the brick back to life!!!!!
just want to post my process for anyone having my issue.
the key point to find the correct build number

umbrisle said:
I was thinking of buying a G7 Play myself, but I am now leaning more towards a G6 Play, because there are more tools available like a working TWRP.
Click to expand...
Click to collapse
.
The G6 Play is really slow, at least the Boost one. I was kind of sorry I bought one to put on Sprint's free unlimited plan. At least Sprint unlocked it for me after 60 days.
Give the G7Play some time, it just came out.
As for you guys complaining of no updates once unlocked, it's not the only phone to require flashing the stock boot.img and relocking to get OTAs.

gedster314 said:
.
As for you guys complaining of no updates once unlocked, it's not the only phone to require flashing the stock boot.img and relocking to get OTAs.
Click to expand...
Click to collapse
Yeah, but there is inconsistency in Motorolas communication, they actively offer the option to unlock the bootloader (with T&C and all) incl. a link to a rollback feature. Which then does not work. So in a scenario where a developer buys the device because it actively offers this features, they dont get what they paid for. Mind you, we are not discussing hacking a device here or jailbraking - we are discussing features that Motorola actively promotes with a dedicated webpage.

wallace_mu said:
was an idiot thinking that mismatch one letter or two will be find, but turns out this is very strict
Click to expand...
Click to collapse
You completely missed the wrong code name "river" in RIVER_RETAIL_9.0_PPO29.80-61_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC it is for another device, while "channel" is the right one

Where did you get the correct Rom from? Thanks

I don't own Moto G7 Play and can not confirm, however this one worked for wallace_mu
wallace_mu said:
XT1952-4_CHANNEL_AMZ_9.0_PPY29.105-36_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC
Click to expand...
Click to collapse

I could successfully lock / unlock / lock the bootloader...
Unlock: fastboot oem unlock [CODE FROM MOTOROLA]
Lock it down:
* first I have to reflash the 'boot.img' from the correct firmware file - fastboot flash boot boot.img
* then I can lock the bootloader clean again with 'fastboot oem lock'. "bad key" is gone, SafetyNet test passed and OTA is working again.
Unlocking / locking again works by the way also. Maybe this will help?

realsine said:
I could successfully lock / unlock / lock the bootloader...
Unlock: fastboot oem unlock [CODE FROM MOTOROLA]
Lock it down:
* first I have to reflash the 'boot.img' from the correct firmware file - fastboot flash boot boot.img
* then I can lock the bootloader clean again with 'fastboot oem lock'. "bad key" is gone, SafetyNet test passed and OTA is working again.
Unlocking / locking again works by the way also. Maybe this will help?
Click to expand...
Click to collapse
yes it does! was waiting for this. 2 quick questions:
- will lock/unlock require factory reset / data loss?
- where to get the (official?) boot.img from (am always careful to flash img from the wild)
thanks!

CoffeeMachineSwitch said:
yes it does! was waiting for this. 2 quick questions:
- will lock/unlock require factory reset / data loss?
- where to get the (official?) boot.img from (am always careful to flash img from the wild)
thanks!
Click to expand...
Click to collapse
Hello,
I'm glad to read that I could help.
I have "my" image of 'https :// mirrors.lolinet.com/firmware/moto/channel/official/RETEU/'. There are also some others - just have a look. And please remove the spaces around '://'. I'm currently not allowed to post (external) links, so this way.
* Every 'LOCK' deletes all data and the system is "clean" again.
* The same applies (unfortunately) to EVERY 'UNLOCK'.
I don't care at the moment because I haven't set up my smartphone yet. But it's not nice.
Best regards

Test Device with unlocked bootloader - now what?

Hi guys
I do have an unusual situation here. Got a Honor View 20 Test device (or presample) directly from a Honor guy. I'm really happy about it as the bootloader is already unlocked. Okay, I honestly don't know what's the plus about it as I can't find a TWRP for this one.
Anyway, my main issue is the installed test ROM:
It shows:
Model: VNA-L29
EMUI Version 8.1
Android Version 8.0
Internal Memory 32GB
RAM 4GB
Using DevCheck System Info App it shows the truth:
Android Version 9.0
Internal Memory 128GB
RAM 6GB
There are some testing apps on it which I can't uninstall. One of them locks the phone after some days if I'm logging in. I have to do a hard reset to make it work again.
Updating the ROM in Recovery doesn't work. Uninstalling the app doesn't work. I'm thinking about trying to update to an official ROM thru DLOAD or HiSuite but this would lock the bootloader I guess - if it's even possible. So if I would be able to install TWRP and an official ROM to use with TWRP I should be able to update it.
Any idea? Every help is appreciated! Thank you!
---------------------
Update: I took the risk and just flashed the actual ROM 238 from androidhost.ru thru DLOAD. Phone works like charm and device still has an unlocked bootloader.
Thanks!

dude010 said:
Hi guys
I do have an unusual situation here. Got a Honor View 20 Test device (or presample) directly from a Honor guy. I'm really happy about it as the bootloader is already unlocked. Okay, I honestly don't know what's the plus about it as I can't find a TWRP for this one.
Anyway, my main issue is the installed test ROM:
It shows:
Model: VNA-L29
EMUI Version 8.1
Android Version 8.0
Internal Memory 32GB
RAM 4GB
Using DevCheck System Info App it shows the truth:
Android Version 9.0
Internal Memory 128GB
RAM 6GB
There are some testing apps on it which I can't uninstall. One of them locks the phone after some days if I'm logging in. I have to do a hard reset to make it work again.
Updating the ROM in Recovery doesn't work. Uninstalling the app doesn't work. I'm thinking about trying to update to an official ROM thru DLOAD or HiSuite but this would lock the bootloader I guess - if it's even possible. So if I would be able to install TWRP and an official ROM to use with TWRP I should be able to update it.
Any idea? Every help is appreciated! Thank you!
Click to expand...
Click to collapse
Send it back and ask for an actual phone

Hamza5682 said:
Send it back and ask for an actual phone
Click to expand...
Click to collapse
Thanks for the advice :laugh: :laugh:
I got this one for free so I wanna make the best out of it.

Huawei/Honor devices cannot be unlocked. So there is no active community with CFW developements so there is no point whatsoever of going in to shady sites and trying to 'unlock' your device bootloader.
You can try to update with download method(as it is the only way) If you brick the phone just recycle it and be done with it. There is not many options.

looneylv said:
Huawei/Honor devices cannot be unlocked. So there is no active community with CFW developements so there is no point whatsoever of going in to shady sites and trying to 'unlock' your device bootloader.
You can try to update with download method(as it is the only way) If you brick the phone just recycle it and be done with it. There is not many options.
Click to expand...
Click to collapse
Thanks for your feedback. As I wrote at the end of my first post I updated with the regular firmware. Everything works smooth and the bootloader is still unlocked.
I'll try this at the weekend with the manual I found on XDA. There are CFW for a lot of Honor and Huawei devices but the firmware is quite old so I'll not even try .
https://openkirin.net/devices/
Maybe it's just fake

looneylv said:
Huawei/Honor devices cannot be unlocked. So there is no active community with CFW developements so there is no point whatsoever of going in to shady sites and trying to 'unlock' your device bootloader.
You can try to update with download method(as it is the only way) If you brick the phone just recycle it and be done with it. There is not many options.
Click to expand...
Click to collapse
Why would you say that when it is clearly possible? My Honor View 20 is unlocked and has Magisk running on it. There are other people with an unlocked bootloader, just look at the "Root Guide" Thread.
The problem is getting the unlock code. As far as i know there are no trustworthy providers at the moment so please be carfeful!
Regards

garris_bibop said:
Why would you say that when it is clearly possible? My Honor View 20 is unlocked and has Magisk running on it. There are other people with an unlocked bootloader, just look at the "Root Guide" Thread.
The problem is getting the unlock code. As far as i know there are no trustworthy providers at the moment so please be carfeful!
Regards
Click to expand...
Click to collapse
Because there is no official way to unlock phones bootloader(you cannot get unlock code, at least officially) If you are willing to give your personal info in shady sites, that is your own risk and fault if your IMEI get's in to wrong hands....
So basicly im guessing there is 90% locked vs 10% unlocked Huawei/Honor phones in the world. :good: Congrats if you are 'geek' enough and went true the shady process to get in those 10%. BUT there is no active developements of CFW. Yes there is some but they are unstable...
Oh yeah and official security apps(like banking, to pay with nfc) for security reasons check phones bootloader and if it is rooted/unlocked then you cannot start them. I dont know if it is worth the trouble anymore to bang on your chest and root your android just because of ''freedom''....

Again, it IS possible, thats what i'm saying. Nothing more, nothing less. So if you say 'its is not possible to unlock bootloader' then thats just plain wrong. Everyone should be able to make an informed decision for themselves, we're not children anymore. I definitely agree that you shouldn't give your data to some shady site.
In addition, i'm not sure what unlocking and rooting yout phone has to do with 'banging on your chest'.
Although the advantages may be minor nowadays, they are still there. The banking apps (i'm using) work just fine. If you are used to rooting your phone then its hard to accept all the restrictions
Regards

Previously ive rooted all my androids aswell. But ive stopped on my last main device(4years ago) because when you have full official support, whats the point? The hustle of manually flashing weekly because of updates and bug fixes... Meehh. Its not 2010 anymore when it was 'cool' to have a rooted phone(thats why the chest expression. )
If the device is like 3years old and dosent have update support anymore from the manufacturer
then it is a different story. Then you can flash newer custom android version and play with the device more to extend phone pocket life.
Ehmm i guess it is in country's security law or something. Because here where i live none of the banking apps work if you have rooted phone, when you open it just sayes that security check failed and error code(that you have a rooted phone)
neither lot of cupon apps where there is your sensitive info. ???Even mcdonalds app dosent let to use cupons on my rooted phone.
I have older rooted android to play on in my spare time. ?

Think we're on the same page anyway, right?
Guess i am lucky that i have rooted phone with apps and updates working. Though, i have to mention this again, i'm not sure what that has to do with being cool. Ppl are not bragging about it (at least no one i know ever has), its just that i like to have as many customization options as possible. Coming from a Xiaomi device i felt pretty restricted at the beginning
Doesn't matter, have a nice day!
Regards

Call Recording and Indonesia ROM

Just got a Redmi Note 8 Pro with Global ROM and discovered that call recording won't work due to Google/Android Pie limitations.
After some searching, I found (on this forum) that the Indonesia ROM supports call recording on this phone.
Here are my questions:
1. Will burning a different ROM affect my warranty?
2. Will I lose any functionality by switching from Global to Indonesia ROM, and if so, what? Specifically, will NFC functionality be affected?
3. If I ever do a factory reset, will the phone revert to Global ROM?
4. I found the Indonesia ROM files here. There are three files called Recovery, OTA, and Fastboot. Do I need them all? If so, do they need to be burned in any specific order?
5. Where can I find complete instructions for burning the Indonesia ROM? I am new to Xiaomi, and the last time I burned a ROM to a phone was 5 years ago (Samsung); I don't remember anything, so I'd like instructions that assume nothing and don't skip any steps (instructions for intelligent dummies). I found these instructions for installing TWRP, but there's nothing about what to do next, and there's a list of pre-requisites with no explanations (Unlocked Bootloader, Phone Drivers, ADB and Fastboot Drivers), making the instructions insufficient for a noob like me.
Thanks much.

yossidme said:
Just got a Redmi Note 8 Pro with Global ROM and discovered that call recording won't work due to Google/Android Pie limitations.
After some searching, I found (on this forum) that the Indonesia ROM supports call recording on this phone.
Here are my questions:
1. Will burning a different ROM affect my warranty?
2. Will I lose any functionality by switching from Global to Indonesia ROM, and if so, what? Specifically, will NFC functionality be affected?
3. If I ever do a factory reset, will the phone revert to Global ROM?
4. I found the Indonesia ROM files here. There are three files called Recovery, OTA, and Fastboot. Do I need them all? If so, do they need to be burned in any specific order?
5. Where can I find complete instructions for burning the Indonesia ROM? I am new to Xiaomi, and the last time I burned a ROM to a phone was 5 years ago (Samsung); I don't remember anything, so I'd like instructions that assume nothing and don't skip any steps (instructions for intelligent dummies). I found these instructions for installing TWRP, but there's nothing about what to do next, and there's a list of pre-requisites with no explanations (Unlocked Bootloader, Phone Drivers, ADB and Fastboot Drivers), making the instructions insufficient for a noob like me.
Thanks much.
Click to expand...
Click to collapse
Hey,
Before going any further you first need to make sure what region is your phone. Is it a Chinese phone (bought from AliExpress for example) or a real Global phone (bought from a local store/official retail). Because you could very well own a Chinese phone shipped with a Global Rom flashed on it and this could result in some problems for you in terms of what you can do with it and how you can do it.
If you bought/received a phone with already unlocked bootloader, you should return it.
Unlocking bootloader should only be done by you when you need it.
1. Technically unlocking bootloader, ESSENTIAL step prior flashing anything, void your warranty.
However and that's what is interesting, if at some point you decide to flash back your original region rom (here Global) and lock back bootloader, none will know but Xiaomi servers you once unlocked this device certainly not a local reseller. So in term of warranty you should be safe, that is of course unless you brick your phone doing stuff you were not supposed to do with a locked bootloader if you are following.
2. If not mistaking, I think you loose NFC. Indian phones for sure do not have NFC at all, for their version, the chip was replaced with a 2nd SIM card tray (not shared). Not sure if you read the functionality afterward using rooted tricks.
3. No that does not work this way. When you are running a Rom, any version, if you factory reset that room, you just return to installation screen of that given Rom.
To return to Global Rom, you will need to reflash that Global Rom using the same method you did successfully flashing the Indonesian Rom (or any other rom) for example.
Would be wise to first download the exact version of the Rom you are currently using on your phone for archives purpose (BURN IT on good quality medias!) to revert back to it when/if needed. You can also archives OTA updates of that version you may not have taken yet to apply them manually if you ever revert back to that Global Rom and want to.
4. Different versions depends on what you are doing. In your case Fastboot version is what you need at the moment. You can find all different kind of versions of Roms for your RN8PRO on that site
As for the way to flash them, order and everything, you will need to look for guides online,
I dont think any order matters, just make sure to flash them all before rebooting disconnecting device. But if you are unsure of what you are doing, you'd be probably best using a tool such as MiFlash.
5. Here you can find one from the MIUI community website guiding you through the use of MiFlash to flash a stock Rom on your device.
Just note you do not have to use any tools to flash the .images of all partitions, you can easily doing it from command line using fastboot flash command one after an other.
Also note that installing TWRP is usually not needed to flash stock Roms (unlike flashing custom roms). Trying to mess up with the recovery partition is actually what seem to brick most of the devices.
However please note UNLOCKING your BOOTLOADER is MENDATORY.
Hope this helps.
Regards,

doesnt matter if you switch to any rom variant .i have switched mine to indonesian ,europe and indian and alll worked fine execpt indian version felt a bit laggy .just download the fastboot version of the rom and flash it through mi flash tool xiaomiflash .your bootloader needs to be unlocked and dont forget to check cleann all button in mi flash and dont check clean and lock

I have got global version and changed imei with unlocked bootloader. Can i flash indonesian rom without lose f my imei?
Thanks in advance for your answers

Muad.Dib,
Thanks for your detailed reply.
If I understand correctly, unlocking the bootloader voids the warranty just the same as rooting the phone, so if all I want is to get call recording, I may as well just root the phone and save the bother of flashing a different ROM.
Does that make sense to you, or do you see any advantage to flashing a different stock ROM instead of just rooting the phone? From past experience I've seen that rooting has additional benefits anyway.
BTW, I bought my phone on Banggood. It was advertised as Global ROM, and that appears to be what it has. As soon as I turned the phone on it updated to MIUI Global 11.0.2.1; I don't know what version it was before the update.
Muad.Dib said:
Hey,
Before going any further you first need to make sure what region is your phone. Is it a Chinese phone (bought from AliExpress for example) or a real Global phone (bought from a local store/official retail). Because you could very well own a Chinese phone shipped with a Global Rom flashed on it and this could result in some problems for you in terms of what you can do with it and how you can do it.
If you bought/received a phone with already unlocked bootloader, you should return it.
Unlocking bootloader should only be done by you when you need it.
1. Technically unlocking bootloader, ESSENTIAL step prior flashing anything, void your warranty.
However and that's what is interesting, if at some point you decide to flash back your original region rom (here Global) and lock back bootloader, none will know but Xiaomi servers you once unlocked this device certainly not a local reseller. So in term of warranty you should be safe, that is of course unless you brick your phone doing stuff you were not supposed to do with a locked bootloader if you are following.
2. If not mistaking, I think you loose NFC. Indian phones for sure do not have NFC at all, for their version, the chip was replaced with a 2nd SIM card tray (not shared). Not sure if you read the functionality afterward using rooted tricks.
3. No that does not work this way. When you are running a Rom, any version, if you factory reset that room, you just return to installation screen of that given Rom.
To return to Global Rom, you will need to reflash that Global Rom using the same method you did successfully flashing the Indonesian Rom (or any other rom) for example.
Would be wise to first download the exact version of the Rom you are currently using on your phone for archives purpose (BURN IT on good quality medias!) to revert back to it when/if needed. You can also archives OTA updates of that version you may not have taken yet to apply them manually if you ever revert back to that Global Rom and want to.
4. Different versions depends on what you are doing. In your case Fastboot version is what you need at the moment. You can find all different kind of versions of Roms for your RN8PRO on that site
As for the way to flash them, order and everything, you will need to look for guides online,
I dont think any order matters, just make sure to flash them all before rebooting disconnecting device. But if you are unsure of what you are doing, you'd be probably best using a tool such as MiFlash.
5. Here you can find one from the MIUI community website guiding you through the use of MiFlash to flash a stock Rom on your device.
Just note you do not have to use any tools to flash the .images of all partitions, you can easily doing it from command line using fastboot flash command one after an other.
Also note that installing TWRP is usually not needed to flash stock Roms (unlike flashing custom roms). Trying to mess up with the recovery partition is actually what seem to brick most of the devices.
However please note UNLOCKING your BOOTLOADER is MENDATORY.
Hope this helps.
Regards,
Click to expand...
Click to collapse

Did you check if NFC works with Indonesian ROM?
maanni said:
doesnt matter if you switch to any rom variant .i have switched mine to indonesian ,europe and indian and alll worked fine execpt indian version felt a bit laggy .just download the fastboot version of the rom and flash it through mi flash tool xiaomiflash .your bootloader needs to be unlocked and dont forget to check cleann all button in mi flash and dont check clean and lock
Click to expand...
Click to collapse

yossidme said:
Muad.Dib,
Thanks for your detailed reply.
If I understand correctly, unlocking the bootloader voids the warranty just the same as rooting the phone, so if all I want is to get call recording, I may as well just root the phone and save the bother of flashing a different ROM.
Does that make sense to you, or do you see any advantage to flashing a different stock ROM instead of just rooting the phone? From past experience I've seen that rooting has additional benefits anyway.
BTW, I bought my phone on Banggood. It was advertised as Global ROM, and that appears to be what it has. As soon as I turned the phone on it updated to MIUI Global 11.0.2.1; I don't know what version it was before the update.
Click to expand...
Click to collapse
You're welcome, I am happy if I was useful to you in any kind of ways.
Well yes and no. Yes apparently you 'could' achieve call recording when rooted (yet I still fail doing so even if I installed the default MUI apps module I got from Telegram group. The setting to automatic recording is set to on yes, but I dont see recordings in the supposed destination folder nor I can see a simple button to record any voicecall I used to have on older versions of Android. Me failing to make it work - I did not try very hard to be honest - does not mean you cannot find someone who succeeded into doing so in that telegram group for RN8PRO).
That said it would not be a 'native' solution, just a patch/workaround. If it works well great, if not, well...
On an other hand by flashing to a Rom which does support it natively, well you are covered for the use you need.
So the advantage I see (with the included disadvantages) is better support for the function which is not supported for privacy reasons en Glob/EU market.
Does that come at a price?
Probably.
For example are you ready to trade off NFC for native call recording support? That may be a choice you have to make in the end. Again that said, if you root your phone on that new Rom, install NFC drivers manually as root (I see no reasons why that would not be possible after all) you may be able to patch NFC on that other Rom since unlike Indonesians market phone, you do have NFC hardware.
For example, myself, I wish I could have made that kind of bargain/trade off, giving up that NFC feature I have no need for, to get 8GB or Ram + 2x Sims + SD and not an hybrid tray. Unfortunately that's not the kind of trade I could make here in EU unless I would have ordered directly from Amazon.in (assuming that would have been possible) or third party website, but that was not possible for warranty reasons among other things.
Hope this helps.
Regards,

yossidme said:
Did you check if NFC works with Indonesian ROM?
Click to expand...
Click to collapse
Yes it does as it is officially available in every variant expect indian variant.

UPDATE:
I finally had the time to test the MIUI-default-apps Magisk module available for download on Telegram group, originally made for MIUI 11.0.1.0, and it works properly on MIUI 11.0.2.0 EEA. Does not require changing Rom.
Hope this helps.

Well, I have finally started the process, but got stymied by the Bootloader Unlock tool (Couldn't unlock. Please unlock 168 hours later.). Quite frustrating. I see that a lot of people have this problem and had to try again more than once, waiting a week between attempts.
Is there a workaround or do I just have to wait a week and hope for the best?
Also, assuming all goes well and I eventually manage to unlock the bootloader and flash the Indonesia ROM, do I use the same tool to re-lock the bootloader (in order to restore the security of the phone)?
And if I want to unlock again in the future, will I again possibly get the "wait and try again next week" message, or does that only happen the first time?
Thanks.
Muad.Dib said:
UPDATE:
I finally had the time to test the MIUI-default-apps Magisk module available for download on Telegram group, originally made for MIUI 11.0.1.0, and it works properly on MIUI 11.0.2.0 EEA. Does not require changing Rom.
Hope this helps.
Click to expand...
Click to collapse

yossidme said:
Well, I have finally started the process, but got stymied by the Bootloader Unlock tool (Couldn't unlock. Please unlock 168 hours later.). Quite frustrating. I see that a lot of people have this problem and had to try again more than once, waiting a week between attempts.
Is there a workaround or do I just have to wait a week and hope for the best?
Click to expand...
Click to collapse
No workaround, you just have to wait (and yes I know how freaking frustrating it was for me...). You can even start meditation classes meanwhile it helps
yossidme said:
Also, assuming all goes well and I eventually manage to unlock the bootloader and flash the Indonesia ROM, do I use the same tool to re-lock the bootloader (in order to restore the security of the phone)?
Click to expand...
Click to collapse
It depends on what your the flavor of the phone you got. You may want to have a look at that other thread Relock bootloader after flashing ROM Indonesia where we actually covered this exact subject
The good thing about that 7 days wait period is you can gather all the intel you need to be 100% ready when the time come to seriously mess up with things.
So you know, once your bootloader is unlocked, first thing you will want to do BEFORE anything else, is blow off that security which needed Auth Account to unbrick account (ONLY WORKS FOR PIE, ANDROID 9 MIUI VERSION BEWARE).
All information is here: [GUIDE][INFO][PSA] Redmi Note 8 Pro - Megathread
yossidme said:
And if I want to unlock again in the future, will I again possibly get the "wait and try again next week" message, or does that only happen the first time?
Thanks.
Click to expand...
Click to collapse
The waiting time is for one time only (THANKS GOD!).
So if you relock, beside having to get your hands on the unlock tool once again and have added the same infos as for the first time in the phone, you will be able to unlock right away.
That's at least a good news
Hope this helps,
Regards,

Muad.Dib said:
UPDATE:
I finally had the time to test the MIUI-default-apps Magisk module available for download on Telegram group, originally made for MIUI 11.0.1.0, and it works properly on MIUI 11.0.2.0 EEA. Does not require changing Rom.
Hope this helps.
Click to expand...
Click to collapse
My friend,
Would you like be so kind and share that magisk module with others or maybe just indicate the spot where I can get it? I would love to try this out. THX

kamyk70 said:
My friend,
Would you like be so kind and share that magisk module with others or maybe just indicate the spot where I can get it? I would love to try this out. THX
Click to expand...
Click to collapse
Yes of course.
It is a module you can find on the Telegram group called "Redmi Note 8 Pro | OFFICIAL".
Like me you will have to go in there even if you do not use Telegram.
Once there and you got the /notes it is called the default apps.
I cannot share it myself here because I am not the developer of that module, as you can understand that's against forums policies.
All I can tell you is it works correctly on EEA MIUI 11.0.2.0.
Good luck!
Hope this helps.

Muad.Dib said:
Yes of course.
It is a module you can find on the Telegram group called "Redmi Note 8 Pro | OFFICIAL".
Like me you will have to go in there even if you do not use Telegram.
Once there and you got the /notes it is called the default apps.
I cannot share it myself here because I am not the developer of that module, as you can understand that's against forums policies.
All I can tell you is it works correctly on EEA MIUI 11.0.2.0.
Good luck!
Hope this helps.
Click to expand...
Click to collapse
Thanks man, I got it! ?

I have disovered that there are different NGC protocols and that my Redmi Note 8 Pro does not read NFC cards of some protocols. I'm wondering if it might not be a driver issue. where would I look for NFC drivers?
Thanks
Muad.Dib said:
For example are you ready to trade off NFC for native call recording support? That may be a choice you have to make in the end. Again that said, if you root your phone on that new Rom, install NFC drivers manually as root (I see no reasons why that would not be possible after all) you may be able to patch NFC on that other Rom since unlike Indonesians market phone, you do have NFC hardware.
Regards,
Click to expand...
Click to collapse

kamyk70 said:
Thanks man, I got it!
Click to expand...
Click to collapse
You are much welcome, glad I could help
Regards
---------- Post added at 10:21 ---------- Previous post was at 10:20 ----------
yossidme said:
I have disovered that there are different NGC protocols and that my Redmi Note 8 Pro does not read NFC cards of some protocols. I'm wondering if it might not be a driver issue. where would I look for NFC drivers?
Thanks
Click to expand...
Click to collapse
Sadly I have no idea. I think you should make a new thread about this to get more visibility and probably more answers from people who actually knows the answer.
Hope this help.
Regards.

Muad.Dib said:
UPDATE:
I finally had the time to test the MIUI-default-apps Magisk module available for download on Telegram group, originally made for MIUI 11.0.1.0, and it works properly on MIUI 11.0.2.0 EEA. Does not require changing Rom.
Hope this helps.
Click to expand...
Click to collapse
Hi can you share more details???IS IT SAFE?? I want miui message and call apps not Google's one... How can i have them without changing ROM to Indonesian??? Now i have global ROM.

yossidme said:
Did you check if NFC works with Indonesian ROM?
Click to expand...
Click to collapse
yup it is working perfectly fine on indonesian rom as i am still using it

Alisoofi said:
Hi can you share more details???IS IT SAFE?? I want miui message and call apps not Google's one... How can i have them without changing ROM to Indonesian??? Now i have global ROM.
Click to expand...
Click to collapse
Hey,
Sorry was AFK for a while. In case you still need answer, going to reply just in case.
Well there is not much to add, you simply install the module from within Magisk once it installed, you reboot, and it works out of the box, you go in the settings and you set it as you like.
Good luck!

Do i need to root before installing it ?
Do i need to root before installing it ?

How To Guide After Update Bootloop Fix

Since the inception of Android getting stuck in a bootloop after updating is a common problem. The Red Magic 6 Pro is no exception. For the purposes of this guide I'm referring to the global, or as known in the USA, the US version of the Red Magic 6 Pro. After receiving my device directly from Red Magic's website, I of course wanted to toy with it and see what I could and couldn't do with it. I downloaded the official global Rom from Red Magic's website for future possible fixes if anything went wrong unlocking the bootloader and rooting. I unlocked my bootloader and rooted via patching stock boot with Magisk as outlined in @chocolote4444 thread. After screwing around with Magisk modules and doing all I wanted to do, I decided to unroot and relock the bootloader. This is where the fun began.
After unrooting and relocking the bootloader, I placed the full update zip in root directory of internal storage and ran the local update. It wasn't necessary, but just to make myself feel better i did it anyway. After the update was complete and I rebooted it was stuck in boot animation bootloop. Factory resetting via recovery did nothing to alleviate the bootloop. Here's what I did to fix the bootloop:
1: Hold down power and volume down to reboot in to fastboot.
2:
Code:
fastboot getvar all
This will tell you what your current active slot is. Just look through the lines returned and you'll see it.
3: Once you see what your active slot is you're going to change the active slot to the opposite slot. If you're slot a you're going to change it to b and vice versa.
4: In order to change active slots you have to be bootloader unlocked if you aren't already. I won't detail here how to unlock because if you don't already know how to do it you shouldn't be doing this anyway.
5:Now to set your active slot,
Code:
fastboot --set-active=a
if you're on slot b or
Code:
fastboot --set-active=b
if you're on a.
6: At this point you can reboot. If all goes well you should reboot and the bootloop is gone. After rebooting and assuming everything has been done correctly, you should boot into system. After rebooting and you boot into system, you can reboot again into fastboot and relock the bootloader if you so wish.
The reason you're getting stuck in bootloop after update is it's not switching slots correctly after update. This is purely speculation on my part but it seems to fit. Thats it! You should now be up and running. I hope this helps someone whos stuck and as aggravated as I was.

Dang thank you for the guide, but rippers to people who still have their bootloader locked

CyberWolf92 said:
Dang thank you for the guide, but rippers to people who still have their bootloader locked
Click to expand...
Click to collapse
it makes me cry that we cant get solution for this locked bootloader

Fastboot flashing unlock worked for me with no adverse consequences. Not sure why it wouldn't work for everyone else. I've unlocked and relocked a couple times with zero ill effects

bob24260 said:
Fastboot flashing unlock worked for me with no adverse consequences. Not sure why it wouldn't work for everyone else. I've unlocked and relocked a couple times with zero ill effects
Click to expand...
Click to collapse
it just that ours oem unlock option didn't checked when the phone still alive, the update brick it then tadaaaa......

I see what you’re saying now. On my version, the US model, OEM unlock is enabled by default. Mine came turned on by default which surprised me.
Nocturne Seigneur said:
it just that ours oem unlock option didn't checked when the phone still alive, the update brick it then tadaaaa......
Click to expand...
Click to collapse

bob24260 said:
I see what you’re saying now. On my version, the US model, OEM unlock is enabled by default. Mine came turned on by default which surprised me.
Click to expand...
Click to collapse
Not my US variant, I told myself I wasn't gonna mess this phone up yet coz I had just gotten it so I didn't even toggled dev settings, guess that's my bad.
My BL is locked tighter than Fort Knox, when using fastboot flashing unlock, it returns:
FAILED (remote: 'Flashing Unlock is not allowed
')

CyberWolf92 said:
Not my US variant, I told myself I wasn't gonna mess this phone up yet coz I had just gotten it so I didn't even toggled dev settings, guess that's my bad.
My BL is locked tighter than Fort Knox, when using fastboot flashing unlock, it returns:
FAILED (remote: 'Flashing Unlock is not allowed
')
Click to expand...
Click to collapse
Do you have the 6 or 6 Pro?

bob24260 said:
Do you have the 6 or 6 Pro?
Click to expand...
Click to collapse
It's the 6 Pro

CyberWolf92 said:
It's the 6 Pro
Click to expand...
Click to collapse
Mines the 6 Pro as well. Screenshot your about section in settings and we can compare. Make sure you block out any personal information. I don’t understand why yours is different.

CyberWolf92 said:
It's the 6 Pro
Click to expand...
Click to collapse
Sorry I feel like an idiot. Yours is soft bricked?

bob24260 said:
Sorry I feel like an idiot. Yours is soft bricked?
Click to expand...
Click to collapse
Yes lmfao I was just gonna reply that its a brick. But yeah if it was unlocked I would be back up n running by now

CyberWolf92 said:
Yes lmfao I was just gonna reply that its a brick. But yeah if it was unlocked I would be back up n running by now
Click to expand...
Click to collapse
Their recovery is totally different. Most stock recoveries have a way to flash stock zips. Just for sh*ts and giggles have you tried adb sideload? Probably won’t work with locked bootloader but you never know. Try it in stock recovery.

The recovery is strange on these models, only gives you a wipe, reboot and power off option but unfortunately there isn't any adb access that I'm aware of, only thing that can be used for sideloading is fastboot or EDL and with a locked bootloader, that just leaves EDL

CyberWolf92 said:
The recovery is strange on these models, only gives you a wipe, reboot and power off option but unfortunately there isn't any adb access that I'm aware of, only thing that can be used for sideloading is fastboot or EDL and with a locked bootloader, that just leaves EDL
Click to expand...
Click to collapse
I know the option isn’t present as far as what’s listed in the recovery options but it never hurts to try anyways. It’s weird because even after wiping data I was still able to unlock bootloader. For some odd reason my oem unlock was enabled without me have ever touching it.

bob24260 said:
I know the option isn’t present as far as what’s listed in the recovery options but it never hurts to try anyways. It’s weird because even after wiping data I was still able to unlock bootloader. For some odd reason my oem unlock was enabled without me have ever touching it.
Click to expand...
Click to collapse
I had already tried it a couple days ago lol, adb doesn't exist in this world of Nubia. The OEM Unlock option in dev settings typically survives simple factory resets which is all this wipe option in recovery does.

CyberWolf92 said:
I had already tried it a couple days ago lol, adb doesn't exist in this world of Nubia. The OEM Unlock option in dev settings typically survives simple factory resets which is all this wipe option in recovery does.
Click to expand...
Click to collapse
That’s strange because every Android device I’ve ever owned would set the oem toggle back to off if you even looked at the reset button lol. As sad as it is to say, I’m already bored with mine and am probably going to either trade it off or sell it. I want to try that Lenovo Legion Duel 2 or whatever it’s called. I also want the Xiaomi Mi 11 Ultra. I’ve had several Xiaomi phones and they’ve all been excellent. Normally I’ll look at what’s currently hot in China and give that a try. If a phone is selling well in the land of electronics aka China then it’s probably a fairly decent device.

bob24260 said:
That’s strange because every Android device I’ve ever owned would set the oem toggle back to off if you even looked at the reset button lol. As sad as it is to say, I’m already bored with mine and am probably going to either trade it off or sell it. I want to try that Lenovo Legion Duel 2 or whatever it’s called. I also want the Xiaomi Mi 11 Ultra. I’ve had several Xiaomi phones and they’ve all been excellent. Normally I’ll look at what’s currently hot in China and give that a try. If a phone is selling well in the land of electronics aka China then it’s probably a fairly decent device.
Click to expand...
Click to collapse
I see lol my experiences are mainly from Samsung/LG lmao so I thought it would be the same case since dev settings are pretty much mirrored across devices with a few regional/hardware exceptions. I haven't had a chance to get bored with mine yet, had to crawl back to one of my back up phones in the meantime xD But the Dual 2 does look really cool but at a $1.2k price tag and then with how picky Verizon is in what they support, it's a tough one. Never had an Xiaomi before but that's a good rule of thumb though that if it sells well over there, it's decent.

Edit: Mod please remove.

CyberWolf92 said:
I see lol my experiences are mainly from Samsung/LG lmao so I thought it would be the same case since dev settings are pretty much mirrored across devices with a few regional/hardware exceptions. I haven't had a chance to get bored with mine yet, had to crawl back to one of my back up phones in the meantime xD But the Dual 2 does look really cool but at a $1.2k price tag and then with how picky Verizon is in what they support, it's a tough one. Never had an Xiaomi before but that's a good rule of thumb though that if it sells well over there, it's decent.
Click to expand...
Click to collapse
Verizon can be a huge pia. I used them for quite a few years but got tired of 400-500$ bills. I highly recommend Xiaomi. I've had several of their devices and for the money you can't beat them. A good entry level device of theirs is the Mi 10T. On paper they look sort of meh but having had one I can attest to their overall decency.