Unable to restart - Xiaomi Poco F2 Pro (Redmi K30 Pro) Questions & Ans

Hello,
I am having a very big problem:
Yesterday evening I unlocked the bootloader of my Poco F2 Pro and I wanted to install a custom rom (I was thinking of installing One Os).
I followed the step by step but the installation did not work and I only had access to recovery.
I managed to reset the original rom via Mi Flash but having retried the same Mi flash procedure now blocks.
Since then I find myself without a phone, the recovery seems to work but it stops there, impossible by flashing it to launch a ROM, I have the impression that the system partion does not work
To be precise, this is an 8-256GB
Thank you in advance to the person who can help me relaunch it.

Actarus0013 said:
Hello,
I am having a very big problem:
Yesterday evening I unlocked the bootloader of my Poco F2 Pro and I wanted to install a custom rom (I was thinking of installing One Os).
I followed the step by step but the installation did not work and I only had access to recovery.
I managed to reset the original rom via Mi Flash but having retried the same Mi flash procedure now blocks.
Since then I find myself without a phone, the recovery seems to work but it stops there, impossible by flashing it to launch a ROM, I have the impression that the system partion does not work
To be precise, this is an 8-256GB
Thank you in advance to the person who can help me relaunch it.
Click to expand...
Click to collapse
so u cant flash with miflash? what errors gives miflash on flashing?

Good evening,
Thanks for trying to help me.
I managed to finally flash my F2 Pro via MiFlash.
So what is the precise method to flash a rom, I would like to install MiuiMix but I do not have a view on the system partition in TWRP and I am afraid of bricking my phone.
Small precision, I do not know if that changes anything but it is an F2 Pro 8-256Go
thank you in advance

Related

[Thread doubts] OnePlus 7 chinese version [GM1900]

Hi guys, I open this thread to solve problems / doubts of this chinese version of One Plus 7 GM1900 because I guess many will be in my place.
I tell you my case:
My intention is to open bootloader to be able to put custom recovery TWRP and root it with Magisk.
Once I have it, I have doubts:
1. If I want to remove TWRP and Root, and I will leave all stock, what steps should I take?
2. If I am in OOS (for example 9.5.2) with TWRP and root and want to upgrade to a new version of OOS (for example 9.5.6), what steps do I have to follow?
3. I would like to know if this is true, and if so, what would be the solution: I have read that when a Wipe System is made from Twrp, the bootloader can be closed or that the phone does not start in fastboot mode causing a crash. Is this true?. I thought about when I wanted to install a cleaner ROM stock, make a Wipe System, data, cache and dalvik and then flash the rom, and according to that it might not be possible.
Thank you.
Hi, are these Treble GSI roms compatible with the OnePlus 7 (not pro) Chinese version GM 1900 ???
Roms Treble GSI:
https://forum.xda-developers.com/project-treble/trebleenabled-device-development
hardware is the same, firmware also fits from EU/Indian devices. next time just use search.
tURkOsANsE said:
1. If I want to remove TWRP and Root, and I will leave all stock, what steps should I take?
Click to expand...
Click to collapse
Flash the stock ROM and reboot. You'll have a phone with stock recovery and ROM with no root access. It won't relock your bootloader though, so you'll have to do it with: fastboot oem lock
2. If I am in OOS (for example 9.5.2) with TWRP and root and want to upgrade to a new version of OOS (for example 9.5.6), what steps do I have to follow?
Click to expand...
Click to collapse
You always need to flash full ROM zips if you're rooted and want to update. However to keep the custom recovery (TWRP), you need to flash the TWRP installer along with the ROM. Then to not lose root access you'll have to reboot to TWRP and flash Magisk. Just follow these steps:
1. Boot to TWRP
2. Flash ROM
3. Flash TWRP installer
4. Reboot to TWRP
5. Flash Magisk
6. Reboot to system
3. I would like to know if this is true, and if so, what would be the solution: I have read that when a Wipe System is made from Twrp, the bootloader can be closed or that the phone does not start in fastboot mode causing a crash. Is this true?. I thought about when I wanted to install a cleaner ROM stock, make a Wipe System, data, cache and dalvik and then flash the rom, and according to that it might not be possible.
Click to expand...
Click to collapse
I haven't tried that yet. But since TWRP builds are official, I don't think there are bugs like that. Why don't you give it a try and let us all know?
@dewri21 Thank you very much for your answers, you have helped me a lot, thank you for your clear explanations, please like this, help those who are starting in this world.
dewri21 said:
I haven't tried that yet. But since TWRP builds are official, I don't think there are bugs like that. Why don't you give it a try and let us all know?
Click to expand...
Click to collapse
Hehehehe I dare not do it, I could run out of mobile phone and end up with a brick. At the moment if I want to put clean OOS I think I will use Fastboot mode. Let's see if a partner who knows how to get out of a brick does Wipe Sistem and confirms that.
FASTBOOT: https://forum.xda-developers.com/oneplus-7/how-to/rom-stock-fastboot-roms-oneplus-7-t3937478
Hi guys, I am writing to let you know that I have flashed the fastboot 9.5.6 BA ROM in my OnePlus 7 Chinese version GM 1900 and it worked perfectly. I was in TWRP, Root Margisk and Custom Kernel, and now I'm back in Stock. My device being a Chinese version came with ROM AA when removed from the box, and I confirm that the BA version can also be set up by Fastboot.
Add that as it is said, the first restart is slow, it stays a while in the warning screen of bootloader open, but it advances with the start. In my case I have not had to restore factory.
Very happy with this method to be able to return to Stock.
Hello, has anyone tried this on our OnePlus 7 to fix a brick? It seems that it is the MsMdonwloadsTools for our OnePlus 7. Someone who has a brick can try it and tell us if it works.
https://repairmymobile.in/flash/oneplus-7-flash-file/amp/
MsmDownloadTool For OnePLus 7: https://forum.xda-developers.com/oneplus-7/how-to/unbrick-tool-oneplus-7-msmtool-hydrogen-t3953240

[ROM][UNOFFICIAL] Resurrection Remix 5.8.5 for Cubot Cheetah + TWRP

Hello everyone, I was able to successfully port a RR Rom for this device.
Installation:
- Get SP Flash Tools (I used version 5.1512.0, like before)
- Download the RR ROM - https://mega.nz/#!swcRzAgB!fI4CbeHIfx_CdyPrmMNcGN4uQFy4YhaJohufU_DGxGI
- Download TWRP (scatter file included) - https://mega.nz/#!1xUjRIiA!0aFkvFOe0QP_f5SlMcBAPo0nCWNJbW0iagW0OlDaLlU
- Open the "RR 5.8.5 - 7.1.2" zip file, and put "boot.img" and "magisk_patched.img" into your phone's INTERNAL storage so you can find them later
- Flash the recovery through SP Flash Tools to "BOOT" partition! (If you flash it to "recovery" partition, the screen may not work)
- Reboot, it should boot into TWRP
- Wipe system, cache, data, dalvik cache
- Flash the ROM (you don't need to flash Gapps, they are pre-installed)
- After it's done, go back and click "Install", then "Install image".
- Flash either "boot.img" if you want no root access, or "magisk_patched" if you want the root access.
- Reboot.
- Wait for it to boot
Bugs
- No fingerprint is available to set-up
- Let me know if you find any?
Donate
If you like my work, please consider donating:
PayPal: https://www.paypal.com/donate?hosted_button_id=QYSZDSMUGQKWG
This is my 2nd attempt at porting, ever, sorry for not being straight-forward and making this overly complicated.
If this works well for people I might try MIUI next.
And let me know if your device reads/works properly with SD card inserted! I think it may be just my device that doesn't recognize any, but would be nice to get some confirmation.
All credits go to Cleopatra Bianchi for providing TWRP.
(https://www.needrom.com/download/cheetah-twrp-3-0-2-1/)
thank you. smooth and good Rom
Did you find/encounter any bugs?
Hello,
Nothing major problem. Only I can't play downloaded video but I can watch through youtube and facebook. Just blank screen only. Thank you for the rom. Better from the stock rom
hayati1 said:
Hello,
Nothing major problem. Only I can't play downloaded video but I can watch through youtube and facebook. Just blank screen only. Thank you for the rom. Better from the stock rom
Click to expand...
Click to collapse
Hmm, maybe try an app from play store that let's you play videos and see if it works? Like VLC, or something.
Sorry for extremely late reply
Hello friends, I know it's not the right topic, I apologize but I'm trying ... I have a new Cubot Note 20 Pro and I would like a TWRP image for it but I can't find it anywhere. Maybe someone knows an image compatible with my phone. Please, can anybody be so kindly to help me with an advice? Thank you.
Hellera said:
Hello friends, I know it's not the right topic, I apologize but I'm trying ... I have a new Cubot Note 20 Pro and I would like a TWRP image for it but I can't find it anywhere. Maybe someone knows an image compatible with my phone. Please, can anybody be so kindly to help me with an advice? Thank you.
Click to expand...
Click to collapse
You could try auto twrp porter. I used in on my Prestigio 3450DUO and worked LONG time ago. If it doesn't work let me know and I will try to help
Firmware Care
FirmwareCare is one of the ideal firmware download websites, serving Stock Firmware (ROM) for 343 Mobile brands in the World. The Stock Firmware shared on the website came with the Driver, Flash Tool, and How-to Flash Manual.
firmwarecare.com
kazkas1398 said:
You could try auto twrp porter. I used in on my Prestigio 3450DUO and worked LONG time ago. If it doesn't work let me know and I will try to help
Firmware Care
FirmwareCare is one of the ideal firmware download websites, serving Stock Firmware (ROM) for 343 Mobile brands in the World. The Stock Firmware shared on the website came with the Driver, Flash Tool, and How-to Flash Manual.
firmwarecare.com
Click to expand...
Click to collapse
Thank you @kazkas1398, I'll try it... I'll be back!
I understand all of these, I know to work with adb, fastboot commands but I cannot unlock bootloader on my device, Cubot Note 20 Pro. I was searching about 3 days for this, I found what I knew but it seems that no command works in fastboot:
fastboot oem unlock
fastboot oem unlock-go
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot oem unlock_critical
I must mention... Developer options, OEM-unlocking and USB-debugging checked, all MTK and ADB drivers installed, I'm not a begginer... but, of course, I don't know everything. So, I need a little help!
Nothing works, no command... it says "... command not supported in default implementation". I need unlock the bootloader first of all for rooting my device and other reasons.
I'm really frustrated, blocked in this situation! Can anybody help my to unlock bootloader, please? Thank you.
Ok friends, I managed to unlock bootloader, get root... and I tried to port the stock recovery with Mediatek Auto TWRP Recovery Porter.
Then, I flashed vbmeta and recovery images in fastboot mode...
After that, my Cubot Note 20 Pro is booting only in fastboot mode... until I flashed the stock recovery again.
Does anyone have any working solutions, suggestions other than waiting for an official TWRP? Thank you.
Edit:
I found this, I followed all the steps... but it stucked in TWRP logo... waited about 20 minutes... nothing... any solution please?! Thank you.
[MT6771][10]TWRP 3.4.0 Recovery for Cubot Note 20 Pro ~ Techswizz
This TWRP 3.4.0 Recovery For Cubot Note 20 Pro is working fully fine and can be used to flash custom ROMs and make full backups. Full touch is also working ok for easy navigation. For those who want to root by flashing SuperSu, this is a recommended custom recovery. Please find out more features...
www.techswizz.com
Hellera said:
Ok friends, I managed to unlock bootloader, get root... and I tried to port the stock recovery with Mediatek Auto TWRP Recovery Porter.
Then, I flashed vbmeta and recovery images in fastboot mode...
After that, my Cubot Note 20 Pro is booting only in fastboot mode... until I flashed the stock recovery again.
Does anyone have any working solutions, suggestions other than waiting for an official TWRP? Thank you.
Edit:
I found this, I followed all the steps... but it stucked in TWRP logo... waited about 20 minutes... nothing... any solution please?! Thank you.
[MT6771][10]TWRP 3.4.0 Recovery for Cubot Note 20 Pro ~ Techswizz
This TWRP 3.4.0 Recovery For Cubot Note 20 Pro is working fully fine and can be used to flash custom ROMs and make full backups. Full touch is also working ok for easy navigation. For those who want to root by flashing SuperSu, this is a recommended custom recovery. Please find out more features...
www.techswizz.com
Click to expand...
Click to collapse
You need to utilize the Hovatek forum.Its a Mediatek phone and they specialize in those phones.I know many of the standard processes we are accustomed to don't work.I have the same phone and with limited searching I was only able to find TWRP 3.4.0 but it freezes while in recovery.Im sure theres something out there more compatible

Workaround for CMI Mi 10 Pro 5G Global Custom ROM & Root eg MIU 12

There is a problem while rooting and installing TWRP recovery on the MI 10 Pro 5G (German-Version ROM Global). If you try to install TWRP you will not be able to get into the recovery. If you try (Vol up + Power) you`ll only able to start the MIU-Recovery.
Also I got some problems to get google pay to work, but this way works for me.
Before we start the disclaimer " I'm not responsible for any damage / bricking / ... If this way fails on your phone"
How to install MIU 12 EU CMI to get Dual-SIM, MIU Phone-App,...
You need:
- an unlocked boot loader
- a working ADB on Win / Mac / Linux
- TWRP I took this one HERE
- a custom ROM I took the weekly EU-ROM because I want Dual-Sim, the regular MI-Caller and the other cool stuff. You could find it HERE take the one for MI 10 Pro!! Alternativ MIU 12 ROM (tested)
MIU 12 EU stable Vers: 12-10 get it here
1 Step:
connect your phone to your computer and copy your "new" ROM to the device
2. Step:
Power off phone > hold Vol down + Power and reboot in Fastboot-Mode
3. Step start TWRP in a different way
fastboot boot "link to your TWRP Recovery"
EXAMPLE: fastboot boot C:\Users\neunzehn\Desktop\ADB\TWRP\recovery.img
now you boot TWRP from you computer without installing, so if anything goes wrong you are able to plug of and reboot in Fastboot.
4. Step flash ROM
DON`T UNPLUG YOUR PHONE!
choose your preferred language in TWRP and flash the ROM you put on the Phone before
5. Step
Reboot your Phone.. it will stuck /reboot (don't get nervous let it happen for e few times)
Press " Volume up + Power" you get the MIU Recovery choose " Wipe Data"
6.Step
Wait that your phone boot is complete , in my case it tooks 10 Min... after that you got your Custom-ROM
How to root without losing Bank-Apps, Safety-Net
You need:
- an unlocked boot loader
- a working ADB on Win / Mac / Linux
1. Step:
connect your phone to your computer and copy your Magisk v20.2 to your device IMPORTED only use Magisk 20.2 you can get it HERE
2. Step:
Power off phone > hold Vol down + Power and reboot in Fastboot-Mode
3. Step start TWRP in a diffrent way
fastboot boot "link to your TWRP Recovery"
EXAMPLE: fastboot boot C:\Users\neunzehn\Desktop\ADB\TWRP\recovery.img
4. Step flash root
DON`T UNPLUG YOUR PHONE!
choose your preferred language in TWRP and flash the Magisk.zip you put on the Phone before
5 Step reboot
Reboot your Phone. After Reboot start the Magisk-App and disable "automatic-update / search for update" and make the safety-net test.
Done...
PS: In 8 years of flashing I never have seen this behavior, don't ask me why this is actually the best way to get a stable CR on your phone. I tried this way on 3 MI 10 Pro 5G bought in Germany (Telekom, Media Markt, Ebay) with the awful Global ROM
CREDITS go to: XDA and MIU for ROM and TWRP
Article UPDATES:
06/25/20: Link to TWRP was broken > corrected
06/27/20 added workaround to root
07/02 added stable 12 MIU EU-ROM (all languages are supported)
Interesting, must then be specific to the German edition of the phone as I didn't get this with my (Global) Mi 10 Pro !
Following your description it seems as if flashing TWRP does not work, what are the commands you used ? It should be "fastboot flash recovery <twrp_file.img>"....
As an idea: what would happen if you boot TWRP as in your step 4, then copy the TWRP file to the phone and install TWRP from TWRP ?
Thanks, nice to know, i even got my phone from mediamarkt in germany.
Could you please tell me, is the phone encrypted after you've flashed Xiaomi.eu?
AND, is google pay working?
thx
s3axel said:
Interesting, must then be specific to the German edition of the phone as I didn't get this with my (Global) Mi 10 Pro !
As an idea: what would happen if you boot TWRP as in your step 4, then copy the TWRP file to the phone and install TWRP from TWRP ?
Click to expand...
Click to collapse
I also tired this, but it produced a boot loop an " Chinese-Letters"
Flash-User said:
Thanks, nice to know, i even got my phone from mediamarkt in germany.
Could you please tell me, is the phone encrypted after you've flashed Xiaomi.eu?
AND, is google pay working?
thx
Click to expand...
Click to collapse
You have to encrypt it at the first boot via your MI-Account , Yes Google Pay works for me and also Postbank, Moneese, and im able to "disable" the Exposure Notification Framework ( the discussion on SWR / WDR / NDR in Germany about GPRD / Security of the Covid-STuff)
neunzehn77 said:
If you try to install TWRP you will not be able to get into the recovery. If you try (Vol up + Power) you`ll only able to start the MIU-Recovery.
Click to expand...
Click to collapse
it's been like this for years now, just google "twrp replaced by stock recovery xiaomi reboot" you'll find lots of reddit posts of this happening.
i only do this once when buying a new device so sorry I don't remember exactly which one but there are two ways to reboot after installing the recovery and one of them prevents the device from overwrite the recovery, if I remember correctly
1- run "fastboot reboot" and hold volume up
2- hold power and vol up until the device reboots and boots to recovery
on another note, this section is for development not tutorials and general discussions
Won't happen if you follow my guide. My friend in Switzerland tried it with the Global Mi10Pro without issues
https://youtu.be/uM1dBptUBd8
Thank you neunhzehn77 !!! U saved my day
Now folks let me tell you something...
I´m not new to rooting phones anyway and i did try several ways to get the xiamomi.eu custom rom on my Mi 10 Pro.
I failed every single time.
Then asking neunzehn77 for specific help on my flashing situation in a private chat.
This guy explained to me some of the "super-partition-features-issues" and cleared his guide for me.
What can i say... i truly folled his guide step-by-step and i´m now on xiaomi.eu beta MIUI 12 rom in no time.
And again thank neunzehn77 for saving my MIUI-Rom-experience for good.:victory:
underlines said:
Won't happen if you follow my guide. My friend in Switzerland tried it with the Global Mi10Pro without issues
https://youtu.be/uM1dBptUBd8
Click to expand...
Click to collapse
If you follow your guide, you will lose essential-stuff like some Banking-Apps, Google-Pay,... and some more. I tried your way on a "German MI 10 Pro 5G" and get random boot-loops... maybe there is an unknown difference between CN ,EU, Global Versions. I don't know... for me your guide isn't working... but maybe that's a way for CN/US bought MI`s
In my case its better to leave the Super-Partition untouched, to get unwanted effects.
Thanx for sharing Mate...
neunzehn77 said:
If you follow your guide, you will lose essential-stuff like some Banking-Apps, Google-Pay,... and some more. I tried your way on a "German MI 10 Pro 5G" and get random boot-loops... maybe there is an unknown difference between CN ,EU, Global Versions. I don't know... for me your guide isn't working... but maybe that's a way for CN/US bought MI`s
In my case its better to leave the Super-Partition untouched, to get unwanted effects.
Thanx for sharing Mate...
Click to expand...
Click to collapse
Thanks for this valuable feedback. I have to put up a warning for EU users then.
Can you remember what exactly it was that lead to errors or problems? And which TWRP did you use? xiaomi.eu's modified one or LR.Team's?
Also, how exactly did you flash magisk?
On my CN CMI I also had all these problems, when touching the super partition. That's common as soon as you modify the super partition: https://xiaomi.eu/community/threads/twrp-and-system-problem.56103/
Do you remember what exactly you did differently from my guide in order for you to make it work? I could incorporate that into the AIO Guide on XDA.
underlines said:
Won't happen if you follow my guide. My friend in Switzerland tried it with the Global Mi10Pro without issues
https://youtu.be/uM1dBptUBd8
Click to expand...
Click to collapse
Hello, does your friend in Switzerland have 5G working ? I happen to be in Switzerland too (carrier : Sunrise), everything works smoothly but 5G... Thanks for your answer.
AFAIK all custom ROMs based on CN, so no 5g..
@neunzehn77 I have a question for you. I just unlocked the bootloader of my Mi 10 (yes not the pro, but the principle is the same). I bought it through Orange in Belgium and it is the Global version, I suppose it must be similar to yours. I see that you didn't format or wipe when flashing a new ROM and all other guides I find do format /data. Isn't this necessary when going from the official ROM to a Xiaomi.EU ROM? The problem with your workaround would then be that the ROM you put in your storage would be gone. I am used to flashing Oneplus devices, but this is something else... It really confuses me.
sithlord512589 said:
Now folks let me tell you something...
I´m not new to rooting phones anyway and i did try several ways to get the xiamomi.eu custom rom on my Mi 10 Pro.
I failed every single time.
Then asking neunzehn77 for specific help on my flashing situation in a private chat.
This guy explained to me some of the "super-partition-features-issues" and cleared his guide for me.
What can i say... i truly folled his guide step-by-step and i´m now on xiaomi.eu beta MIUI 12 rom in no time.
And again thank neunzehn77 for saving my MIUI-Rom-experience for good.:victory:
Click to expand...
Click to collapse
Hi, I'm on the verge of trying to flash xiaomi.eu ROM on my Mi 10 (Global - Belgium) and rooting it afterwards. The problem is that I'm a bit afraid of getting an error or a bootloop and not knowing how to recover from it. I'm not familiar with Xiaomi because I always had a Oneplus device before. How did you fix it? Did you format /data like other guides suggest? Or did you just "dirty flash" xiaomi.eu on top of the stock ROM like in this workaround guide?
Marcoziezo said:
Hi, I'm on the verge of trying to flash xiaomi.eu ROM on my Mi 10 (Global - Belgium) and rooting it afterwards. The problem is that I'm a bit afraid of getting an error or a bootloop and not knowing how to recover from it. I'm not familiar with Xiaomi because I always had a Oneplus device before. How did you fix it? Did you format /data like other guides suggest? Or did you just "dirty flash" xiaomi.eu on top of the stock ROM like in this workaround guide?
Click to expand...
Click to collapse
No no.. when you switch to custom you have to start all over. So wipe and format(make cloud backup ?)
marcel112 said:
No no.. when you switch to custom you have to start all over. So wipe and format(make cloud backup ?)
Click to expand...
Click to collapse
I used the latest LR team TWRP (3.4.2B wzsx150 from june 23) and it worked out fine with my global (European) version of the Mi 10. So this workaround is not needed anymore I guess.
1) I fastboot flashed this TWRP version
2) Booted to TWRP
3) Formatted /data
4) Rebooted to TWRP to be able to acces the internal storage
5) Transferred and flashed the Xiaomi.EU stable build of August 10th
6) Rebooted to system.
Everything is working fine, I am rooted using Magisk 20.4 with some modules and even swift installer is working great.
Cheers
Marcoziezo said:
I used the latest LR team TWRP (3.4.2B wzsx150 from june 23) and it worked out fine with my global (European) version of the Mi 10. So this workaround is not needed anymore I guess.
1) I fastboot flashed this TWRP version
2) Booted to TWRP
3) Formatted /data
4) Rebooted to TWRP to be able to acces the internal storage
5) Transferred and flashed the Xiaomi.EU stable build of August 10th
6) Rebooted to system.
Everything is working fine, I am rooted using Magisk 20.4 with some modules and even swift installer is working great.
Cheers
Click to expand...
Click to collapse
just remember, on android 11, you cant use normal magisk 20.4.
You need to use canary builds.
Also Android 11, twrp cant decrypt using pincode... you need to set up , gesture
Is imei repair and qcn file output for mi 10 pro?
badaas said:
AFAIK all custom ROMs based on CN, so no 5g..
Click to expand...
Click to collapse
Just saw this.
Maybe this is the reason that the EU rom does not have 5G working.

Android 11 Red Magic Rom [FLASHGUIDE]

Hello again!
I saw a post where leipnacht provides a link to the public beta of Android R. (I let you here a drive link to download it faster).
I flashed it and it's working properly on my device. There is some bugs, but the most part of the things works without problems (Personally, I didn't face any bug itself (only a low noise with the vibration by the moment), but there are some comments in the page of bbs nubia about some problems with other things.
The previous conditions from where I update to Android R Red Magic Rom were using a GSI in the Android 10 chinese version of the rom. So, the steps I followed are:
1. In the recovery, wipe data, cache and dalvik. Also, format data.
2. Flash in the Android 10 TWRP the Android R rom.
3. Flash this NikGapps Package , Magisk Debug and DFE (Encrypt disabler in order to be able decrypt data in the recovery). I also flashed Permissive_5 but I think there is no need to do it.
4. Boot and enjoy.
I will attach all the files and some screenshots for those who want to take a see to the rom. Personally, I feel no changes in this version, but, as always, the performance is great and it runs really smooth. It's a beta version, so I hope more changes in the future.
P.D. In order to get safetynet passing, I used HideProps Config magisk module. There is no big issues with it, and everything is fixable
P.d.2. This rom has antiroll-back active, so if you want to go back to previous version, you will have to use the unbrick tool
Perseo99 said:
Hello again!
I saw a post where leipnacht provides a link to the public beta of Android R. (I let you here a drive link to download it faster).
I flashed it and it's working properly on my device. There is some bugs, but the most part of the things works without problems (Personally, I didn't face any bug itself (only a low noise with the vibration by the moment), but there are some comments in the page of bbs nubia about some problems with other things.
The previous conditions from where I update to Android R Red Magic Rom were using a GSI in the Android 10 chinese version of the rom. So, the steps I followed are:
1. In the recovery, wipe data, cache and dalvik. Also, format data.
2. Flash in the Android 10 TWRP the Android R rom.
3. Flash this NikGapps Package , Magisk Debug and DFE (Encrypt disabler in order to be able decrypt data in the recovery). I also flashed Permissive_5 but I think there is no need to do it.
4. Boot and enjoy.
I will attach all the files and some screenshots for those who want to take a see to the rom. Personally, I feel no changes in this version, but, as always, the performance is great and it runs really smooth. It's a beta version, so I hope more changes in the future.
P.D. In order to get safetynet passing, I used HideProps Config magisk module. There is no big issues with it, and everything is fixable
P.d.2. This rom has antiroll-back active, so if you want to go back to previous version, you will have to use the unbrick tool
Click to expand...
Click to collapse
Thanks for the update.
I have been planning to upgrade my Red Magic 3 to Android 10 (CN rom) for quite a while now. And its good to know A11 beta has arrived too.
Have you tried fps games on this device like pubg mobile, cod etc? Do they work properly ?
Also, I haven't even unlocked bootloader on my device. Can you proivde a better guide, to completely switch from global rom (stock) to A11 (beta) or A10 CN rom (stable).
Need links / guide for following items -
- Unlock bootloader
- Link of working twrp and steps to flash (should I change recovery after installing this beta?)
- Gapps and Magisk link (As I can't run this device without Google services).
It will be a huge help for me to get started.
Take your time with it (no rush).
Thanks in advance!!!
nalin_s3 said:
Thanks for the update.
I have been planning to upgrade my Red Magic 3 to Android 10 (CN rom) for quite a while now. And its good to know A11 beta has arrived too.
Have you tried fps games on this device like pubg mobile, cod etc? Do they work properly ?
Also, I haven't even unlocked bootloader on my device. Can you proivde a better guide, to completely switch from global rom (stock) to A11 (beta) or A10 CN rom (stable).
Need links / guide for following items -
- Unlock bootloader
- Link of working twrp and steps to flash (should I change recovery after installing this beta?)
- Gapps and Magisk link (As I can't run this device without Google services).
It will be a huge help for me to get started.
Take your time with it (no rush).
Thanks in advance!!!
Click to expand...
Click to collapse
Hey!
No problem at all. I let you here two guides to migrate to the cn rom and even a gsi
Be careful and aware about what you are going to do, It's not specially difficult but you have to get ready all the files and tools in case of brick or bootloops.
Enjoy the flashing!
Perseo99 said:
Hey!
No problem at all. I let you here two guides to migrate to the cn rom and even a gsi
Be careful and aware about what you are going to do, It's not specially difficult but you have to get ready all the files and tools in case of brick or bootloops.
Enjoy the flashing!
Click to expand...
Click to collapse
Thanks for the links. I am planning to update to stable A10 version for now.
I have few questions it be a huge help you could clear some of my doubts -
1. After unlocking bootloader I have to install TWRP (for gapps to run). So should I install TWRP after flashing CN rom ? or before ?
I am asking this because I read in some guides that only CN rom is custom recovery capable.
2. If you have run A10 stables before, does OTA updates require to be installed via TWRP only ?
Will I loose Gapps and Root access if I updated the ota directly from settings? And will every rom flash with TWRP clear my installed apps ?
Thanks in advance for helping!!. ??
nalin_s3 said:
Thanks for the links. I am planning to update to stable A10 version for now.
I have few questions it be a huge help you could clear some of my doubts -
1. After unlocking bootloader I have to install TWRP (for gapps to run). So should I install TWRP after flashing CN rom ? or before ?
I am asking this because I read in some guides that only CN rom is custom recovery capable.
2. If you have run A10 stables before, does OTA updates require to be installed via TWRP only ?
Will I loose Gapps and Root access if I updated the ota directly from settings? And will every rom flash with TWRP clear my installed apps ?
Thanks in advance for helping!!. ?
Click to expand...
Click to collapse
Well, I will go in order:
1. You have to flash first in the stock recovery the Android 10 CN rom and then flash the custom recovery. There is no twrp avaible for global rom. Once in the custom recovery, you can flash Gapps and Magisk (in android 10 there is no need of DFE file, the recovery is able to decrypt data properly.
2. You don't need to get worried about OTAs, there is no a constant software update work by nubia for this device, but in case of update, you would flash the rom from the offcial page, with magisk and gapps again and be sure you keep the custom recovery.
Perseo99 said:
Hello again!
I saw a post where leipnacht provides a link to the public beta of Android R. (I let you here a drive link to download it faster).
I flashed it and it's working properly on my device. There is some bugs, but the most part of the things works without problems (Personally, I didn't face any bug itself (only a low noise with the vibration by the moment), but there are some comments in the page of bbs nubia about some problems with other things.
The previous conditions from where I update to Android R Red Magic Rom were using a GSI in the Android 10 chinese version of the rom. So, the steps I followed are:
1. In the recovery, wipe data, cache and dalvik. Also, format data.
2. Flash in the Android 10 TWRP the Android R rom.
3. Flash this NikGapps Package , Magisk Debug and DFE (Encrypt disabler in order to be able decrypt data in the recovery). I also flashed Permissive_5 but I think there is no need to do it.
4. Boot and enjoy.
I will attach all the files and some screenshots for those who want to take a see to the rom. Personally, I feel no changes in this version, but, as always, the performance is great and it runs really smooth. It's a beta version, so I hope more changes in the future.
P.D. In order to get safetynet passing, I used HideProps Config magisk module. There is no big issues with it, and everything is fixable
P.d.2. This rom has antiroll-back active, so if you want to go back to previous version, you will have to use the unbrick tool
Click to expand...
Click to collapse
Can you check your pm??
There's no problem in flashing but take note there's no going back i mean you cant downgrade it anymore using unbric tool even if you flash rom using cmd it will not work my rm3s now is bricked theres no tool or method that can fix it right now. Unless someone make a new unbrick tool
jepoyxxv said:
There's no problem in flashing but take note there's no going back i mean you cant downgrade it anymore using unbric tool even if you flash rom using cmd it will not work my rm3s now is bricked theres no tool or method that can fix it right now. Unless someone make a new unbrick tool
Click to expand...
Click to collapse
I already went to 11 and flash to 3.11
But how did you flash android 10 3.11 in rm3s no matter what tool i use i cant fix my rm3s from being bricked by flashing android 11 beta can you tell me what did you do did you flash it manually in command prompt please help me
jepoyxxv said:
But how did you flash android 10 3.11 in rm3s no matter what tool i use i cant fix my rm3s from being bricked by flashing android 11 beta can you tell me what did you do did you flash it manually in command prompt please help me
Click to expand...
Click to collapse
If you are in 11 beta and want to downgrade..just simple flash global version and again flash 3.11 done
What did you use to flash global rom lastweek i successfully installed android 11 beta and use unbrick tool to go back to global but i got bricked. And i cant fix it anymore.
jepoyxxv said:
What did you use to flash global rom lastweek i successfully installed android 11 beta and use unbrick tool to go back to global but i got bricked. And i cant fix it anymore.
Click to expand...
Click to collapse
I just flash global from otg and tham again 3.11
walkwitmeinhel said:
I just flash global from otg and tham again 3.11
Click to expand...
Click to collapse
Could you please tell me where to download the 3.11 rom. I am not aware that this rom exists. Is this a CN or global rom? Thanks for your reply.
[email protected] said:
Could you please tell me where to download the 3.11 rom. I am not aware that this rom exists. Is this a CN or global rom? Thanks for your reply.
Click to expand...
Click to collapse
http://ui.nubia.cn/rom/detail/64
Oh! Didn't expect that. I just post this for Red Magic 3 device users. I don't know how RM3S actually works. Have you tried the unbrick tool from chinese version? Or just flashing the global rom from recovery is enough?
Wait is there a chinese unbrick tool cn. version for red magic can you provide me a link.. unbrick tool 3/3s.global by jerry is not working anymore if you got brick by android 11 beta rom...
jepoyxxv said:
Wait is there a chinese unbrick tool cn. version for red magic can you provide me a link.. unbrick tool 3/3s.global by jerry is not working anymore if you got brick by android 11 beta rom...
Click to expand...
Click to collapse
Let's see. Here is a link for Red Magic 3S unbrick tool. Download the non-eu ones.
If you have a Red Magic 3 with Red Magic 3s software, I will provide you the link to the other unbrick tool.
Also, you can try flashing the global rom from the stock recovery included in the package of the A11 rom that you have download.
Thanks for replying my bro.. my device is rm3s i already use rm3 and rm3s unbrick tool.. downloading fire hose programmer and image was successfully but.. my phone is still corrupted... And one thingg i dont have twrp install in my rm3s thats why its hard for me to fix it.. can you please guide or teach me how to flash stock recovery using global rom i know how to use cmd and adb
jepoyxxv said:
Wait is there a chinese unbrick tool cn. version for red magic can you provide me a link.. unbrick tool 3/3s.global by jerry is not working anymore if you got brick by android 11 beta rom...
Click to expand...
Click to collapse
So then, It's not a problem of the unbrick tool, that is actually working properly. The thing is that you didn't know how to do a correct process to migrate from cm rom to global...
The first thing you should do is reboot the phone into fastboot mode (power+vol. Down). Then, connect the phone to the PC and type the next commands in the cmd:
Code:
fastboot devices
in order to see if your device is being recognized
Code:
fastboot oem nubia_unlock NUBIA_NX629J
to unlock the bootloader
Code:
fastboot flashing unlock
in order to make your phone able to boot with a modified software. In the moment you will enter this command, you will see a screen advising you about your data (it'll be erased once you accept to unlock flashing).
After that, you can reboot your phone, that will show you an screen advising you that the bootloader is open. Accept and continue without problems.
Tell me if you have been able to make your phone boot.
Perseo99 said:
Well, I will go in order:
1. You have to flash first in the stock recovery the Android 10 CN rom and then flash the custom recovery. There is no twrp avaible for global rom. Once in the custom recovery, you can flash Gapps and Magisk (in android 10 there is no need of DFE file, the recovery is able to decrypt data properly.
2. You don't need to get worried about OTAs, there is no a constant software update work by nubia for this device, but in case of update, you would flash the rom from the offcial page, with magisk and gapps again and be sure you keep the custom recovery.
Click to expand...
Click to collapse
Required in CN A10 + twrp A10, or maybe from CN A9 + twrp A9 to be able to flash

Help me with my P8 Lite 2017 please

Hi everyone, I'm new to this forum, I have been going crazy with a Huawei P8 Lite 2017 for two days, I was trying to install DarkJoker360's AOSP 11 I have already modded a P8 Lite (not 2017) and I had no problems, I managed to install TWRP recovery 3.2.1-0 (I can't find the recovery that DarkJoker recommends) via ADB on my Windows PC I did all the necessary wipes and tried to install this operating system in the partition (Image System) it is an .img file after doing this I restarted and the only thing it does is bring out the Android writing, as if it had installed the rom but then it ends up restarting after a few seconds of this writing, without even getting to the configuration screen, what could I have mistaken?
I apologize for any mistakes but I'm Italian and I might have something wrong
Chricap said:
Hi everyone, I'm new to this forum, I have been going crazy with a Huawei P8 Lite 2017 for two days, I was trying to install DarkJoker360's AOSP 11 I have already modded a P8 Lite (not 2017) and I had no problems, I managed to install TWRP recovery 3.2.1-0 (I can't find the recovery that DarkJoker recommends) via ADB on my Windows PC I did all the necessary wipes and tried to install this operating system in the partition (Image System) it is an .img file after doing this I restarted and the only thing it does is bring out the Android writing, as if it had installed the rom but then it ends up restarting after a few seconds of this writing, without even getting to the configuration screen, what could I have mistaken?
I apologize for any mistakes but I'm Italian and I might have something wrong
Click to expand...
Click to collapse
I thought huawei doesn't allow bootloader to be unlocked this proves Me wrong
Austinredstoner said:
I thought huawei doesn't allow bootloader to be unlocked this proves Me wrong
Click to expand...
Click to collapse
I unlocked the bootloader via "DC-Unlocker" so I don't think that's the problem
Chricap said:
I unlocked the bootloader via "DC-Unlocker" so I don't think that's the problem
Click to expand...
Click to collapse
If u still have twrp installed after flashing that custom Rom u can try flashing other custom rom like lineage os
Before flashing anything else try to make sure what your doing 1 mistake could make u ruined like forever if u flashed other custom rom still in bootloop but TWRP uninstalled well than your screwed
Austinredstoner said:
If u still have twrp installed after flashing that custom Rom u can try flashing other custom rom like lineage os
Before flashing anything else try to make sure what your doing 1 mistake could make u ruined like forever if u flashed other custom rom still in bootloop but TWRP uninstalled well than your screwed
Click to expand...
Click to collapse
Yes, I still have the TWRP installed, precisely version 3.4.0-0, since I could not find a working ROM I tried to debrand it (it was brand Tim) and I think I have done a damage to follow that guide, now I do not not even install the stock rom anymore. I don't know what to do at this point, I would leave the custom rom alone and reinstall its stock rom, at least debrand ...

Categories

Resources