Related
Just a heads up. I've got my RMP since today. As a usual nexus user as I was, the first thing was to unlock the bootloader and flash whatever I can. My destination was -> unlocked bootloader -> smiui with root.
What happened it the following:
1) I unlocked my bootloader following guides (unofficial way)
2) Installed TWRP
3) Flashed SMIUI
And welcome brick. I was in emergency port (9003), and the only way to get the device running was the disasembe way. Well it worked. Now I'm on 7.2.3 with root, but guys - watch what you are flashing. This is my 3rd device (Desire HD, Nexus 4, and now RMP), and this was the first time that I had such a headaches.
SMIUi contains the locked bootloader file, so if by any chance you decide to unlock it by the unofficial way - don't flash it.
Read...read....read and one more time read there are many threads explaining how to do it without getting bricked .
Yup already lernt my lesson. Deleting emmc_appsboot.mbn from the archive before flashing is the right way.
Anyway, SMIUI is totally unusable on our devices. Flashed 6.4.21 and 6.4.14 - on both of them I get no sim/no wifi. Can't connect the device to the PC in file transfer mode also. Now I'm running xiaomi.eu 6.4.21 without issues.
ktomov said:
Yup already lernt my lesson. Deleting emmc_appsboot.mbn from the archive before flashing is the right way.
Anyway, SMIUI is totally unusable on our devices. Flashed 6.4.21 and 6.4.14 - on both of them I get no sim/no wifi. Can't connect the device to the PC in file transfer mode also. Now I'm running xiaomi.eu 6.4.21 without issues.
Click to expand...
Click to collapse
Hello ktomov,
I made the same mistake. I couldn’t wait 10 days for the official unlock so I used the unofficially unlocked bootloader. Then I flashed TWRP and a Xiaomi EU ROM thinking that it’s probably gonna be OK since that’s not an official Xiaomi ROM. Nope! Bricked my device and had to use the testpoint method.
Now my question for you is what to do if want to flash a Xiaomi EU ROM again in case I don’t get the official unlock permission (is it even possible that I don’t get it?). Do I just need to replace the emmc_appsboot.mbn in the ROM’s ZIP file? I’m asking because there is a huge thread on this forum on how to maintain future OTA updates with unofficial unlock and I’d rather just stick with a TWRP-compatible ROM.
just refer to this thread if you flash anything on a unofficially unlocked bloader and ALWAYS DELETE emmc_appsboot.mbn
http://forum.xda-developers.com/redmi-note-3/how-to/creating-modified-boot-img-enabling-adb-t3359916
oh and as far as sMiui goes, dunno bout you, but it worked for me. it lags like hell, but it works. I had no issues with sim/wifi, and as far as MTP mode goes, disable adb in developer opts, that will trigger MTP mode. kinda annoying, but should work. same thing is happening on xiaomi eu and global roms too.
sikica133 said:
just refer to this thread if you flash anything on a unofficially unlocked bloader and ALWAYS DELETE emmc_appsboot.mbn
http://forum.xda-developers.com/redmi-note-3/how-to/creating-modified-boot-img-enabling-adb-t3359916
Click to expand...
Click to collapse
Thanks. That should make sure I don’t hardbrick my phone and retain access to EDL mode. But my question is whether replacing the emmc_appsboot.mbn is all I need to do when flashing a TWRP compatible ROM. No other scripts or changes are necessary?
Hvala u svakom slučaju.
sikica133 said:
just refer to this thread if you flash anything on a unofficially unlocked bloader and ALWAYS DELETE emmc_appsboot.mbn
http://forum.xda-developers.com/redmi-note-3/how-to/creating-modified-boot-img-enabling-adb-t3359916
oh and as far as sMiui goes, dunno bout you, but it worked for me. it lags like hell, but it works. I had no issues with sim/wifi, and as far as MTP mode goes, disable adb in developer opts, that will trigger MTP mode. kinda annoying, but should work. same thing is happening on xiaomi eu and global roms too.
Click to expand...
Click to collapse
Don't know what is going on with those roms, but for me sMiui 6.4.14 and 6.4.21 gives no-sim/no-wifi. Disabling dev still didn't got me to mtp. Haven't got such issues with xiaomi.eu roms though. 6.4.14 and 6.4.21 works like they should.
Filip013 said:
Thanks. That should make sure I don’t hardbrick my phone and retain access to EDL mode. But my question is whether replacing the emmc_appsboot.mbn is all I need to do when flashing a TWRP compatible ROM. No other scripts or changes are necessary?
Hvala u svakom slučaju.
Click to expand...
Click to collapse
Don't replace it. Just delete it from the archive prior flashing.
ktomov said:
Don't know what is going on with those roms, but for me sMiui 6.4.14 and 6.4.21 gives no-sim/no-wifi. Disabling dev still didn't got me to mtp. Haven't got such issues with xiaomi.eu roms though. 6.4.14 and 6.4.21 works like they should.
Don't replace it. Just delete it from the archive prior flashing.
Click to expand...
Click to collapse
Roger that!
So if you have unlocked the bootloader the unofficial way is there any way to flash a locked bootloader later on if for example you wish to give in you phone for repair at the service center?
devtherockstar said:
So if you have unlocked the bootloader the unofficial way is there any way to flash a locked bootloader later on if for example you wish to give in you phone for repair at the service center?
Click to expand...
Click to collapse
unlocking bootloader does not void your warranty
Hello everyone,
tl;dr version
What's the best way to install a custom rom on the Redmi Note 3 out of the box with a locked bootloader. What is the best rom to use for maximum functionality.
I have been following these forums for a while, but haven't got around to creating an account and posting. I'm new to flashing roms, and my experience goes as far as following guides to flash a Samsung S4, and a Samsung S2. The Samsung phones were really easy to flash, and I just followed guides in a robotic way without ever actually learning anything. For the record, CM12 on the Samsung S2, which I'm using because I smashed my S4, is absolutely unbelievable in regards to the increase of performance.
One of my work friends was telling me that he has a mate who bought a Chinese phone really cheap and flashed it. Getting excited, knowing exactly where I need to look to flash a phone, I impulsively researched these phones and bought a Redmi Note 3 for $173 AUD. It's on the way in the mail. Having looked at the hardware specs, this price is absolutely ridiculous. I was more swayed to buy the Redmi Note 3, because multiple sites reported that the second sim slot can hold a micro SD card. The only downside I can see to this phone is the bloatware and stock rom that it comes with, and the reason for this post is to discuss the best way in which to flash a new rom. If you have managed to read this far, thanks for reading my life story!
Having limited experience in the phone flashing world, from researching it looks like the flashing process is something like:
Unlock the bootloader
Flash a recovery program
Use the recovery to flash rom/app
My understanding of the bootloader and why it needs to be unlocked is limited. I've done some research around it, and this is what I have found. The bootloader is the first thing that runs when the phone starts up, loads the kernel and the rom, and verifies that you have a legit recovery program. It needs to be unlocked so you can put a custom recovery on to your phone. Once you have that sorted, flashing roms from the recovery is a pretty straight forward process. If I'm wrong, please correct me, because this is what I have understood from looking around and I'm not confident about my understanding.
Unlocking the Bootloader On The Redmi Note 3
Having read on multiple sites, this looks like the biggest constraint when trying to flash a custom rom on the Redmi Note 3. This is because Xiaomi have locked the bootloader for this device, when most other phones do not have this problem. Most flashing guides for the Redmi Note 3 assume that the boodloader is unlocked or list it as a pre-requisite, so I'm unsure what path to take here. From research, it looks like there are 3 possible ways to move forward from here:
Official Bootloader Unlock
Unofficial Bootloader Unlock
Bypassing The Bootloader Unlock
Because my account is new, the following links aren't hyperlinked and in a good format due to permissions. Sorry! It'd be sweet if a mod could edit it.
1. Official Bootloader Unlock
This seems like the most legit way to unlock the bootloader. Apparently you just go to: endotmiuidotcom/unlock/ and apply for an unlock by using google translate and creating an account. People have reported response times taking over a month, not getting a successful application, or the unlocking process getting stuck at 50%. To me this doesn't sound appealing and I'm not too keen on waiting a month to find I'm unsuccessful in applying.
2. Unofficial Bootloader Unlock
This process is found here: endotmiuidotcom/thread-253680-1-1.html and looks to be a bit tedious. Apparently there is a high chance for a brick using this method, and some custom recoveries don't work well with it. My other concern is that if the brickrate is high, and this method was released around april, it could be possible that Xiaomi has made some further updates, further increasing the chance for a brick.
3. Bypassing The Bootloader Unlock
I found this process on a post from these forums, which then sourced a reddit post. The reddit post is pretty straight forward and can be found here: wwwdotredditdotcom/r/Xiaomi/comments/5611tg/psa_you_can_flash_twrp_and_subsequently_cm13/ .This process works by flashing a legit miui rom, but by flashing it with a modified recovery image, in particular, a custom recovery like TWRP. Having considered the three methods, this looks like the easiest way of getting it done.
My questions are: has anyone done any of these three methods successfully? What method do you recommend? Have I missed anything? Are there any other methods?
My understanding is once the bootloader is unlocked, you install TWRP. Then once that is installed you flash whatever rom you want, which leads into my next question. What is the best ROM to use?
It looks like the most viable roms are the CM roms. I've seen CM 13 and CM 14, are people running CM 13 instead of 14. Why? Is it more stable? Ideally I'm after the most functionality possible. Are there any other roms that you'd recommend flashing? When flashing roms are you supposed to do all the standard things that you would on other phones, factory wipe/cache wipe/davlik cache wipe, flash rom, flash gapps? I've also seen that CM needs firmware flashed before the rom, will this mess anything up and can it brick? Can you do all this stuff from TWRP with a locked bootlader (method 3)? I really like having notification badges too, what will I need to do for this to happen?
If you have read all of this, I really appreciate you taking the time. I hope I haven't broken any forum rules in the process.
dude,it's too much to read for people. I can't believe i read it,anyway.
about unlocking the bootloader process(I'm telling you about my experience):
---step 1 : you sign up for a mi account,choose your country and verify your phone number>login to your mi account on your device(remember to enable every feature on your mi account on your device,you can disable backup)> go to https://i.mi.com and check your device,it should be there> go to http://en.miui.com/unlock/ , write for example dear sir or madam, I'm an austrailian developer and I want to try and work on projects like cyanogen mods and other custom roms. sincerely,JaFranchise - alright,after finishing the writing go to translate.google.com and translate it to chinese,then paste on the form,then apply,you will confirm your request by entering the code that was sent to you via mi message --- for me it took about 3 to 4 hours to receive my confirmation.
---step 2 : first try this,if you stuck on 50% error,you will try step 3,so here is the instruction,
sign in to your mi account on your device(enable find device),also on i.mi.com(to check your device). enable developer options,OEM unlocking and USB debugging. > download the latest version of MIFlashUnlock tool and log into your account link : http://bigota.d.miui.com/miflashunlock/MiFlashUnlock_1.1.0317.1_en.zip> turn off your device and go to fastboot (press and hold volume - and power button at the same time), connect your device to your PC, click unlock(on MIFlashUnlock tool), after your bootloader successfully unlocked, click on reboot.
---step 3 : this is for kenzo devices(redmi note 3 pro - snapdragon650) - if you're using redmi note 3(mediatekX10), you should download the roms(stable and developer) according to your device
you need to switch from global stable to global developer rom, download the latest global developer rom on android lollipop(5.1). link : http://bigota.d.miui.com/6.8.18/miui_HMNote3ProGlobal_6.8.18_d0da79d09e_5.1.zip> after downloading the rom,rename the file name to Update.zip then copy to internal storage(in downloaded_rom folder).> open updater app, select choose update package, go to downloaded_rom folder and select Update.zip. It will verify your rom and install it. > download the latest global developer rom from en.miui.com/download-301.html , repeat the instruction or just simply download via updater > then follow step 2
I think,It's better you first unlock bootloader,then mention me in the comments to go through that(about cm and aosp roms and flashing instructions) process.
goodluck.
Thanks for your reply and for reading it all. So your advice is unlock the bootloader the official way. I know it's too much to read, that's why I put a tl;dr section, because I probably wouldn't read that much! The last thing I want to do is annoy people.
Cheers for specifically telling me what I'd need to write in the application, massive help. Maybe some people have been unsuccessful because they haven't said the right things.
JaFranchise said:
Thanks for your reply and for reading it all. So your advice is unlock the bootloader the official way. I know it's too much to read, that's why I put a tl;dr section, because I probably wouldn't read that much! The last thing I want to do is annoy people.
Cheers for specifically telling me what I'd need to write in the application, massive help. Maybe some people have been unsuccessful because they haven't said the right things.
Click to expand...
Click to collapse
It's alot easier than it sounds. The hardest part is probably getting the drivers on your computer installed properly to unlock bootloader/miflash. The good thing about this device is if you brick it, it's fairly simple to unbrick via the edl method but yea, official unlock bootloader - flash zcx twrp - make a backup - flash away
Hemphiz said:
It's alot easier than it sounds. The hardest part is probably getting the drivers on your computer installed properly to unlock bootloader/miflash. The good thing about this device is if you brick it, it's fairly simple to unbrick via the edl method but yea, official unlock bootloader - flash zcx twrp - make a backup - flash away
Click to expand...
Click to collapse
So it looks like official unlock is the way to go about things. Why ZCX version of TWRP?
ZCX is essentially the official TWRP, but with some extra stuff in it to allow it to support F2FS, if I'm not mistaken. Since you've decided to unlock your bootloader the official way, both ZCX and the official twrp are fine.
JaFranchise said:
Thanks for your reply and for reading it all. So your advice is unlock the bootloader the official way. I know it's too much to read, that's why I put a tl;dr section, because I probably wouldn't read that much! The last thing I want to do is annoy people.
Cheers for specifically telling me what I'd need to write in the application, massive help. Maybe some people have been unsuccessful because they haven't said the right things.
Click to expand...
Click to collapse
you're welcome,yes if you officially unlock the bootloader,everytime you face an issue,for example got your bootloader locked again,you can use miflashunlock with ease.about the version of the twrp,i should say ZCX_TWRP_0917 is the way to go,it got everything you'll ever needed except for encryption you need lazyflasher-I don't want to go into details to make you confused-for more info about twrp and other roms check these links :
1- ⋆⋆ NEWBIE GUIDE ⋆⋆ [UPDATED] Available TWRPs, Add-On Zips, Root, Flash, Restore, FAQ
http://forum.xda-developers.com/redmi-note-3/how-to/guide-redmi-note-3-available-twrps-t3406708
2-step by step instructions for zcx twrp
http://forum.xda-developers.com/redmi-note-3/how-to/zcx-twrp-install-twrp-flash-supersu-t3462448
3- comprehensive guide for unlocking bootloader process
http://en.miui.com/thread-246705-1-1.html
Something really weird happened while I was installing roms. Someone how my OEM got locked and I flashed and voila stuck on the oneplus logo. I have my fastboot working properly also got twrp installed. The thing is that my bootloader is locked so i cant flash and I cant unlock bootloader because I cant flash and set oem unlock. I know this is ****ed up and also my volume up key is not working so we have to work without that. . Whenevr i turn on the device the powered by android quickly disappears and i am in the fastboot. If I do oem unlock it sends me to the recovery. I am not sure why i can't OEM unlock in fastboot. I don't care about data and stuff. Just want the phone working. The unbrick guide wants me to press the volume up key to get to the qualcomm flashing. Unfortunately i can't do that. Need of dire help please ;_;
I kind of have the same problem as of 2 days (see https://forum.xda-developers.com/android/help/bricked-oneplus-x-unlock-bootloader-t3816387), which is kind of strange, as I haven't read anywhere else about it on the internet.
I'll be following this topic.
Japeroen said:
I kind of have the same problem as of 2 days (see https://forum.xda-developers.com/android/help/bricked-oneplus-x-unlock-bootloader-t3816387), which is kind of strange, as I haven't read anywhere else about it on the internet.
I'll be following this topic.
Click to expand...
Click to collapse
I've solved it bud. IF you have a working recovery and bootloader. Flash the stock OS. It'll flash even though the bootloader is locked and then your can oem unlock and do whatever.
KenSha105 said:
I've solved it bud. IF you have a working recovery and bootloader. Flash the stock OS. It'll flash even though the bootloader is locked and then your can oem unlock and do whatever.
Click to expand...
Click to collapse
That's good news! But I think I've tried that, but had no succes. Can you link me the ROM you've flashed?
Japeroen said:
That's good news! But I think I've tried that, but had no succes. Can you link me the ROM you've flashed?
Click to expand...
Click to collapse
https://downloads.oneplus.com/oneplus-x/oneplus_x_oxygenos_3.1.4/
There.
KenSha105 said:
https://downloads.oneplus.com/oneplus-x/oneplus_x_oxygenos_3.1.4/
There.
Click to expand...
Click to collapse
Thank you. I've tried it, but the problem is that I'm stuck with the Oneplus recovery, as I've mentioned in my post. From there, I have 2 options to flash:
1) from internal memory. When I click this, nothing happens (no new screen or anything, nothing)
2) from USB (adb sideload). When I try to sideload the ROM using this option, it starts promising, but after a few seconds, it just says 'Installation failed' without any reason why. Just like for all other ROMS.
So... No progress here. I've also tried to flash the stock recovery (even though it should be on my phone already, maybe another version) using fastboot, but my OPX won't take it because the bootloader is still locked.
Last resort: I'll try the Oneplus live chat tomorrow, but I do not expect any useful information from that...
Japeroen said:
Thank you. I've tried it, but the problem is that I'm stuck with the Oneplus recovery, as I've mentioned in my post. From there, I have 2 options to flash:
1) from internal memory. When I click this, nothing happens (no new screen or anything, nothing)
2) from USB (adb sideload). When I try to sideload the ROM using this option, it starts promising, but after a few seconds, it just says 'Installation failed' without any reason why. Just like for all other ROMS.
So... No progress here. I've also tried to flash the stock recovery (even though it should be on my phone already, maybe another version) using fastboot, but my OPX won't take it because the bootloader is still locked.
Last resort: I'll try the Oneplus live chat tomorrow, but I do not expect any useful information from that...
Click to expand...
Click to collapse
Well guess what, they could solve it.
Or at least partly. It appears that Oneplus has an updated version of the tool used in the mega unbrick guide: MSMDownloadTool V2.1 instead of V2.0. This tool did it's job perfectly, OOS was also installed, in contrast to V2.0 of the tool. I ****ed it up again after that (oops), but found the tool V2.1 online here (https://github.com/finlayacourt/Oneplus-X-Recovery). Some files are missing here like the system.img, but I just copied them from the folder of tool V2.0 found in the mega unbrick guide. It didn't work as perfectly as Oneplus's tool, but at least I was able to install OOS from the Oneplus bootloader, which I wasn't able to before. So knowing that, in the end, the result is the same as for their tool. A working OS again, perfect! So now I can unlock the bootloader again and continue the adventure.
Now, what I've found is that the mainboard I have on my OPX is a newer version (if you search on Google for 'oneplus E1003_15', you'll find some things about it, not much though). I'm 99% positive that this caused all the problems I've encountered. It is why TWRP couldn't see any storage, why the stock Oneplus recovery couldn't see any storage, why the tool V2.0 didn't work and why V2.1 did work. If I wanted a working TWRP, I had to install a modified version of TWRP which is compatible with the newer version, from here: https://www.android-hilfe.de/forum/...-1-oreo-rom-unofficial-onyx-8-1-x.867374.html (yes, once you're relying on German sites, you know you went very deep). After that, I could install LineageOS 14.1 again. I was unable to install the unofficial LineageOS 15.1 however, but knowing where I came from, what I've gone through and how much time I've lost on all of this, I think I'll just stick with LineageOS 14.1 until this baby can retire...
Got to say I only have very positive experiences with Oneplus and it's customer support, and this only adds to it!
Hello very friendly helping people!
Im a 10 year iPhone user, but over time i came to hate all the restrictions and so i got myself a K30 Ultra and later today it should finally arrive!
Unfortunately i found out that it doesnt check the Google SafetyNet thingy and i can't use Google Pay with it. That kinda sucks, I never thought about stuff like this on iOS, but I'm confident there is a solution for it.
I found out about rooting my device, but it somehow isn't possible because of the Mediatek chip. But then I also found out that apperenty there IS a way to use the program/thingy that makes the phone pass SafetyNet (Magisk) without the need of a custom ROM.
I'm sorry if im confusing words like rooting im very noobish about all this.
So here are my questions in short form:
1. Can I make Google Pay Work in any way on my Redmi K30 Ultra?
2. Does this also affect my banking apps (I'm using DKB and Kontist) and can this be solved, too?
3. Could you link me some guides how to do it?
4. Is there any danger doing it (like deleting my phone if it doesnt work) and is there a possibility to safe my device on the PC or something like this to be safe?
5. Are their any safety concerns doing "it" (not sure what the solution will be) and should I install an anti virus program on the device? I just read about the cerberus trojan and its kinda scary. I think iOS systems were always pretty safe against those.
6. Anything else i need to know?
Thank you so much! I appreciate it a lot that there is a place where i can go to get help on those things! <3
Google Pay and any other banking apps refuse to work when a rooted Android gets detected by them. BTW: SafetyNet API doesn't purely check whether the device's Android is rooted, as the API is designed to check the overall integrity of device's Android.
jwoegerbauer said:
Google Pay and any other banking apps refuse to work when a rooted Android gets detected by them. BTW: SafetyNet API doesn't purely check whether the device's Android is rooted, as the API is designed to check the overall integrity of device's Android.
Click to expand...
Click to collapse
Hey, thanks for your post!
Are you implying that there is no way around that and its doomed to forever not work on my device?
To clarify things: SafetyNet is run by an app that has implemented this API, it's not run by Android OS itself. Yes, Magisk allows you to lever out this test by manipulating device's fingerprint so you will possibly be able to use Google Pay etc.pp
FYI: Any app not having SafetyNet API implemented easily can check whether Android got rooted / tampered or not. The app simply runs functions like
Code:
isRootNative
isDetectedDevKeys
isDetectedTestKeys
isFoundBusyboxBinary
isFoundDangerousProps
isFoundHooks
isFoundResetprop
isFoundSuBinary
isFoundWrongPathPermission
isFoundXposed
isNotFoundReleaseKeys
isPermissiveSelinux
isSuExists
isMagiskSUExists
isFoundMagisk
isFoundRootCloakingApps
what can't get prevented by Magisk.
jwoegerbauer said:
Yes, Magisk allows you to lever out this test by manipulating device's fingerprint so you will possibly be able to use Google Pay etc.pp
Click to expand...
Click to collapse
Ok, perfect. Would you be able to link me to a guide that shows me how to install Magisk on my device? It has a Mediatek chip so a custom ROM isn't possible (as far as I understand).
Mirardt said:
Ok, perfect. Would you be able to link me to a guide that shows me how to install Magisk on my device? It has a Mediatek chip so a custom ROM isn't possible (as far as I understand).
Click to expand...
Click to collapse
How to install Magisk without a Custom ROM is explained here.
If a Custom ROM like TWRP isn't officially made public for your device then you have to compile TWRP at your own.
This is TWRP and Magisk for the latest firmware on the K30 Ultra. https://mifirm.net/downloadtwrp/166
---------- Post added at 07:39 PM ---------- Previous post was at 07:37 PM ----------
Google Pay on a rooted device with Magisk installed /is/ possible, my Galaxy Note 9 with Dr. Ketan's ROM works with Google Pay and I believe it's due to the CTS Profile fix which is available in its ROM Tool app. So there's going to be some way to make it work with the K30 Ultra.
JaboJG said:
This is TWRP and Magisk for the latest firmware on the K30 Ultra. https://mifirm.net/downloadtwrp/166
Click to expand...
Click to collapse
Oh wow how cool is that, that is custom for the K30 ultra
And do I install that with the guide linked above or do I need some certain skill and experience to do that. It says it isn't tested yet. If I do a mirror of my phone before nothing really bad can happen right?
Google Pay on a rooted device with Magisk installed /is/ possible, my Galaxy Note 9 with Dr. Ketan's ROM works with Google Pay and I believe it's due to the CTS Profile fix which is available in its ROM Tool app. So there's going to be some way to make it work with the K30 Ultra.
Click to expand...
Click to collapse
Nice!!!
Yeah the only think that failed SafetyNet Test is the "CTS profile match". But I can't use those roms for my K30 ultra, right, so I just do it with Magisk?
Thanks so much!!
You need to unlock your bootloader with the Mi Unlock tool then flash TWRP over fastboot, and in TWRP make the appropriate backups and flash Magisk. There's many guides and it's relatively straight forward.
K30 Ultra is basically a brand new phone, it's like a month old. It'll be a while but keep an eye on XDA Forums, on the internet, and on YouTube. Somebody will eventually describe or figure out how to fix the CTS Profile.
I think I'm not gonna modify mine and I'll just wear my Apple Watch to use it for contactless payments.
JaboJG said:
You need to unlock your bootloader with the Mi Unlock tool then flash TWRP over fastboot, and in TWRP make the appropriate backups and flash Magisk. There's many guides and it's relatively straight forward.
K30 Ultra is basically a brand new phone, it's like a month old. It'll be a while but keep an eye on XDA Forums, on the internet, and on YouTube. Somebody will eventually describe or figure out how to fix the CTS Profile.
I think I'm not gonna modify mine and I'll just wear my Apple Watch to use it for contactless payments.
Click to expand...
Click to collapse
Alright, so I read 12384 guides and had a very tiny sense of it. The Mi Unlock tool stopped me, though, and now I'll have to wait another 6 days.
As I understood it, my data will be erased, but can be just be restored by MIUI if backed up before. I'm gonna let you know how it worked after I'll do it in about a week.
Probably I won't have to patience to wait. Google Pay is a really nice to have, but neither voLTE, nor voWifi works on my device, so I for sure have do hack that some weird way, because i have no mobile network at all at home and absolutely need voWifi.
Thank you very much for your kind help! <3
No problem at all.
I'm not sure if Wifi-Calling (voWifi) works with my carrier as I've turned it on with the carrier and in the phone, and it doesn't seem to be making calls over wifi. Not a big deal for me though as I've got Unlimited calls with my carrier.
Please let us know if and when you do flash the TWRP as I'd like feedback before flashing it myself.
Do your banking apps refuse to work or is it only google pay that fails due to the safetynet fail?
JaboJG said:
No problem at all.
I'm not sure if Wifi-Calling (voWifi) works with my carrier as I've turned it on with the carrier and in the phone, and it doesn't seem to be making calls over wifi. Not a big deal for me though as I've got Unlimited calls with my carrier.
Please let us know if and when you do flash the TWRP as I'd like feedback before flashing it myself.
Click to expand...
Click to collapse
Yeah, me too, but I have a very bad connection in my flat so I do need voWifi anyway. I will let you know and hope I won't brick my device. But as I understand it, bricking the device just by flashing twrp is very unlikely, right?
MerlijnD said:
Do your banking apps refuse to work or is it only google pay that fails due to the safetynet fail?
Click to expand...
Click to collapse
Only Google Pay, both of my banking apps work perfectly. I couldnt scan the security bar code though, some internal google app wouldn't allow it. So i had to put in both the (very long) idendification and security numbers in manually.
Alright thanks. Another thing im interested in is if Snapchat works when safetynet fails. Did you do any tests regarding that?
MerlijnD said:
Alright thanks. Another thing im interested in is if Snapchat works when safetynet fails. Did you do any tests regarding that?
Click to expand...
Click to collapse
Not using Snapchat, but I just installed it and it starts without problems. Didn't made an account though.
So I'm gonna be able to flash twrp and Magisk in exactly 14 hours and have some questions i would really appreciate an answer to <3
Using this: https://mifirm.net/downloadtwrp/166
1. The thing i want to flash first is twrp and it is the file called "recovery.img" in the downloaded folder, is that correct?
2. Just flashing twrp is "relatively" safe and if I do a backup and the device bricks by installing Magsik after, i can recover it through twrp, correct?
3. Should I not install todays new security update to MIUI or does that not matter at all?
edit: 4. Do I need/want to have "USB debugging", "Install via USB" and "USBebugging (Security Settings)" enabled or just "OEM unlocking"?
Thank you so much! I'm very nervous since i didn't read any experiences of rooting the K30 Ultra before and I'm scared of killing it.
Hey Mirardt, good luck. Let us know how you get on!
1. Yeah, you'll use fastboot to flash the recovery.img for TWRP.
2. Do a full backup with TWRP and you should be safe.
3. Doesn't matter, it's just the September Android security update.
4. Yeah turn on USB Debugging and connect your phone to your computer - it will ask you if you want to allow this computer to debug your phone, choose accept and always (or something similar to those words.) Do this before flashing TWRP.
Mirardt said:
So I'm gonna be able to flash twrp and Magisk in exactly 14 hours and have some questions i would really appreciate an answer to <3
Using this: https://mifirm.net/downloadtwrp/166
1. The thing i want to flash first is twrp and it is the file called "recovery.img" in the downloaded folder, is that correct?
2. Just flashing twrp is "relatively" safe and if I do a backup and the device bricks by installing Magsik after, i can recover it through twrp, correct?
3. Should I not install todays new security update to MIUI or does that not matter at all?
edit: 4. Do I need/want to have "USB debugging", "Install via USB" and "USBebugging (Security Settings)" enabled or just "OEM unlocking"?
Thank you so much! I'm very nervous since i didn't read any experiences of rooting the K30 Ultra before and I'm scared of killing it.
Click to expand...
Click to collapse
JaboJG said:
Hey Mirardt, good luck. Let us know how you get on!
1. Yeah, you'll use fastboot to flash the recovery.img for TWRP.
2. Do a full backup with TWRP and you should be safe.
3. Doesn't matter, it's just the September Android security update.
4. Yeah turn on USB Debugging and connect your phone to your computer - it will ask you if you want to allow this computer to debug your phone, choose accept and always (or something similar to those words.) Do this before flashing TWRP.
Click to expand...
Click to collapse
Hey Jabo, nice, I'm gonna do just that! Just for clarification, I use Mi Unlock Tool first, THEN twrp, then backup, then magisk?
I'll let you know and thanks for the good luck!
edit: so the command would be "fastboot flash recovery recovery.img", right?
I'm VERY sorry for the noobish questions.
I'm going to quickly use this thread to ask how to actually unlock the K30 Ultra Bootloader. I did everything the guides said, but Mi Unlock still doesn't recognize the phone when it's plugged in. Any Advice?
Hey guys (especially JaboJG). quick update: Flashing twrp and Magsik both just worked perfectly. no brick. Thanks for your help!!
The only issue is that it didnt help in passing Google Safety Check. I tried almost everything there is and will post my logs of MagiskHide Props in their thread soon.
Also, now some apps don't work anymore because they detect the root. I hope we will find a fix.
macrett said:
I'm going to quickly use this thread to ask how to actually unlock the K30 Ultra Bootloader. I did everything the guides said, but Mi Unlock still doesn't recognize the phone when it's plugged in. Any Advice?
Click to expand...
Click to collapse
No idea, sorry. It just worked for me.
I updated my smartphone to A12 C10 and now it's impossible to enter BROM mode with MTKgui. Do you have a solution ? Why does OnePlus block this function? For me it was the ideal backup solution. Thanks for your feedback.
Quercy said:
I updated my smartphone to A12 C10 and now it's impossible to enter BROM mode with MTKgui. Do you have a solution ? Why does OnePlus block this function? For me it was the ideal backup solution. Thanks for your feedback.
Click to expand...
Click to collapse
They deactivated / removed it. Period.
OnePlus under OPPO converted user unfriended. Time to switch to others.
Who installed custom ROM before, made a wise decision, imho.
Maybe edl exploit for the C10 become available, but very improbable.
Btw, there is a app in play store which make backup of every partition ( some need root ) but cannot remember the name.
Cheers.
No, my smartphone is not rooted. I had too much bootloop with this Nord2. I relocked boot and removed root. With even more reason now that BROM mode no longer exists. There is no longer an easy solution to recover a broken phone
C.01 has BROM mode still active. Unfortunately keeping the preloader and lk while update to C.10 is not possible.
Rooted here from 1st day. More than year. No bootloop, neither rare behavior. Just need to know what is ok for this device and what is ko.....
So does that mean if I updated to C10, it is now impossible to root, custom rom or anything ? I cant access bootloader either...
If you have a solution please don't hesitate :/
Many thanks,
Julien
DPJulien said:
So does that mean if I updated to C10, it is now impossible to root, custom rom or anything ? I cant access bootloader either...
If you have a solution please don't hesitate :/
Many thanks,
Julien
Click to expand...
Click to collapse
Exactly.
The OPPO dev team decided to drop any possibility to customize as done with the other brands. C.01 Still has BROM enabled, not sure fastbootd.
To be able to customize further i stuck with A11 which has BROM and fastbootd and works just fine like old school Oxygen OS.
Cheers.
Hey found THE solution to have fastboot and BROM. There is a rollback package to OOS 11 here. It works for all versions after C.05
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
community.oneplus.com
follow instructions from this video but use package from oneplus community
you need to have enabled developer options to see the local update button
Great share for those who trusted OP and upgraded to OOS12. Now is time to find the best working custom ROM, although almost all based a phh's build.