Hello good people i want to use custom rom !my device is idol 3 6045I as i am noob about this stuffs here is my query :
1. 1st i need to unlock bootloder using fastboot right ?
2. then i need twarp / custom recovery then my desire rom ?
3. what is the best rom currently available ? (my requirement is very good battery life, smooth & stable performance , don't play game that much tho ) i saw lineage 14 available in other sites but not @ xda! really love to use multi screen features ... @Unjustified Dev has 3 rom project i guess! which one should i get or should i try lineage 14! if i miss something please enlighten me ! TIA
1. Yes, Go Here
2. Flash TWRP and Flash the SuperSU ZIP IF ON LOLLIPOP Found Here.
3. 5.1 - PAC as I am currently using right now. Only minor problems are little to no freezes, And if you heavily modify the UI, prepare for some Double FC's here and there. Doesn't happen all the time. But if you feel uncomfortable CM 12.1 is the way to go.
6 - Lineage. Idk about the others.
(Oh, And by the way, do not forget to backup your modem! Some roms are not actually built on from your exact model but they all (6045 variant wise) work the same!)
Huskied said:
1. Yes, Go Here
2. Flash TWRP and Flash the SuperSU ZIP IF ON LOLLIPOP Found Here.
3. 5.1 - PAC as I am currently using right now. Only minor problems are little to no freezes, And if you heavily modify the UI, prepare for some Double FC's here and there. Doesn't happen all the time. But if you feel uncomfortable CM 12.1 is the way to go.
6 - Lineage. Idk about the others.
(Oh, And by the way, do not forget to backup your modem! Some roms are not actually built on from your exact model but they all (6045 variant wise) work the same!)
Click to expand...
Click to collapse
i am on android M ! should my procedure be change ?btw i tried to unlock bootloader but didn't succeeded! after giving this command ""fastboot -i 0x1bbb oem device-info"" its appear that "...failed <remote :unknown command" :/
ian25 said:
i am on android M ! should my procedure be change ?btw i tried to unlock bootloader but didn't succeeded! after giving this command ""fastboot -i 0x1bbb oem device-info"" its appear that "...failed <remote :unknown command" :/
Click to expand...
Click to collapse
Definitely. MM doesn't have fastboot commands.
Huskied said:
Definitely. MM doesn't have fastboot commands.
Click to expand...
Click to collapse
ok ! is there any complete guide about how to downgrade mm to lollipop ?
ian25 said:
ok ! is there any complete guide about how to downgrade mm to lollipop ?
Click to expand...
Click to collapse
Any Custom ROM should work fine, If you have a lollipop backup then that should work too.
Huskied said:
Any Custom ROM should work fine, If you have a lollipop backup then that should work too.
Click to expand...
Click to collapse
No i don't have any custom rom backup ! & if i don't use twrap then how should i install custom rom ! (pls don't mind as i said earlier that i am new in root & stuff thats why i ask for a proper guide TIA)
ian25 said:
No i don't have any custom rom backup ! & if i don't use twrap then how should i install custom rom ! (pls don't mind as i said earlier that i am new in root & stuff thats why i ask for a proper guide TIA)
Click to expand...
Click to collapse
Follow this then. You will need TWRP for downgrading to a Custom 5.1 ROM.
Huskied said:
Follow this then. You will need TWRP for downgrading to a Custom 5.1 ROM.
Click to expand...
Click to collapse
i tried bt after done with sahara & firehose my boot menu ( volume up + power button ) wont start @ all ! i have to switch off the phone to use it again & my phone performance is not super slow :/
Related
My Mi 4c arrived yesterday. I bought it using donations that I received from various project (Samsung Galaxy Tab 2, Tab 3, Tab 4, OnePlus One, Xiaomi Redmi 2). It's seems for Chinese market: a lot of Chinese apps, incomplete English translation, no Google services. Fortunately, TWRP port already available for this device, so rooting and installing GApps is easy. Somehow I still want to keep the original recovery.
1. Boot to fastboot mode (VOL DOWN + POWER) to fastboot TWRP:
Code:
fastboot boot twrp.img
2. Flash SuperSU in TWRP
3. Flash Open GApps nano in TWRP
As you know, loading touchscreen firmware need times in TWRP. Just do other thing while waiting for it :laugh: The possible cause is firmware "ping-pong" issue when in kernel touchscreen firmware different between recovery and normal boot. But why loading a firmware so that long?
My device come with MIUI 7.1.4.0, unlocked bootloader. I just upgrade it to 7.2.1.0 without firmware update to keep the bootloader unlocked but use 7.1.6.0 kernel to boot it because no go with the new kernel (incompatible firmware?), MIUI logo forever. BEWARE: Don't upgrade your device to 7.2.1.0 using a standard method, your bootloader will be locked!
Attached Hardware Info report for my future reference if I decide to develop custom ROM/kernel.
@emfox, I'm with you :laugh:
MIUI 7.2.1.0 without firmware update.
how can you update to 7.2.1.0 version without firmware update?
btw, I think I will wait for Xiaomi EU or sMIUI, so I can flash them via twrp....
tuanhung303 said:
how can you update to 7.2.1.0 version without firmware update?
btw, I think I will wait for Xiaomi EU or sMIUI, so I can flash them via twrp....
Click to expand...
Click to collapse
Backup /system/lib/modules, download 7.2.1.0, inject a modified updater-script, flash it in TWRP recovery, restore /system/lib/modules, reflash SuperSU, reflash GApps.
I hope you can make modified rom 7.2.1.0 without bootloader.
ahmaman said:
I hope you can make modified rom 7.2.1.0 without bootloader.
Click to expand...
Click to collapse
Uploading a big file always a problem for me. Maybe I'll create a proper instructions and script for it.
I confirm touchscreen "ping-pong" issue the source problem of TWRP touchscreen freeze on boot. If touchscreen driver found a different firmware version, it will flash a "proper" firmware and delayed touchscreen event initialization.
welcome aboard, my dear friend!
Looks to me, we got another developer. Good
ketut.kumajaya said:
Backup /system/lib/modules, download 7.2.1.0, inject a modified updater-script, flash it in TWRP recovery, restore /system/lib/modules, reflash SuperSU, reflash GApps.
Click to expand...
Click to collapse
omg... is that English? (j/k)
btw, welcome onboard , Xiaomi will release some kernel sources soon, looks like we will have more stable rom in future :laugh:
ketut.kumajaya said:
Uploading a big file always a problem for me. Maybe I'll create a proper instructions and script for it.
I confirm touchscreen "ping-pong" issue the source problem of TWRP touchscreen freeze on boot. If touchscreen driver found a different firmware version, it will flash a "proper" firmware and delayed touchscreen event initialization.
Click to expand...
Click to collapse
Thanks for documenting your findings.
I can tell you I've never experienced the touchscreen bug since day one, I flashed Team Superluminal's TWRP 2.8.7.3 and I can press all buttons soon as I see them
Logic_ said:
Thanks for documenting your findings.
I can tell you I've never experienced the touchscreen bug since day one, I flashed Team Superluminal's TWRP 2.8.7.3 and I can press all buttons soon as I see them
Click to expand...
Click to collapse
yes, the version 2.8 does not have that bug, the version 3.0.0.2 has
Happy to see Indonesian Developer who will contribute in Mi4C Section. really want to meet you in person if have any chance.
Greeting from Indonesia!
wind99 said:
Happy to see Indonesian Developer who will contribute in Mi4C Section. really want to meet you in person if have any chance.
Greeting from Indonesia!
Click to expand...
Click to collapse
Still slowly check Xiaomi changes line by line https://github.com/kumajaya/android_kernel_xiaomi_msm8992/commits/libra-l-oss-kumajaya :laugh:
I don't know what is going on but if i will flash zip with android 5.1 (like cm.12.1) or 6 (resurr remix) system doesn't boot. Phone is just turning off and thats all. When i'll flash any nougat it start working. Please help me what i have to do. I want to change Nougat because doesn't have support of Xposed, it's important for me...
sorry for bad english
Engelstrommeln said:
I don't know what is going on but if i will flash zip with android 5.1 (like cm.12.1) or 6 (resurr remix) system doesn't boot. Phone is just turning off and thats all. When i'll flash any nougat it start working. Please help me what i have to do. I want to change Nougat because doesn't have support of Xposed, it's important for me...
sorry for bad english
Click to expand...
Click to collapse
You have nougat bootloader so you can install only nougat roms.
If you want to install lollipop roms you have to do a downgrade to lollipop bootloader.
Sent from my Mi-4c using Tapatalk
@cezarmed2
That means now i have to download original firmware 5.1 and flash it through the fastboot and then i will have good bootloader for cm12.1 ? Maybe i can find it in internet and flash bootlader in TWRP? Adb sideload and fastboot still available
Where i can find that?
https://www.google.ro/amp/s/forum.x...-unlocking-mi4c-bl-verification-t3336779/amp/
Follow steps 2 to 9 and you'll be OK.
Sent from my Mi-4c using Tapatalk
@cezarmed2 thanks for help with the main issue
I did flashed right bootloader and i did flashed cm12.1 without gapps for test. It works fine but now i can't enter recovery mode. It's also interesting because i was trying to flash through the fastboot and android app (flashify) and still does't work :/
why this forums is not active ?
I was trying to root my device, i unlocked bootloader, whenever i was trying to install TWR my device go through the recovery only, couldn't go through OS, i solved it by installing stock firmware via flashtool, I want to install recovery to install custom Rom, is there any suggestion for a good custom Rom ?
flashing TWRP does cause some issue in the boot partition of the phone if you try to flash it via fastboot .
But if you really want that recovery as well as your rom try this method hope this solves your problem
https://forum.xda-developers.com/z3/general/recovery-root-mm-575-291-lb-t3435214
Thanks phone is Rooted
Tech core said:
flashing TWRP does cause some issue in the boot partition of the phone if you try to flash it via fastboot .
But if you really want that recovery as well as your rom try this method hope this solves your problem
https://forum.xda-developers.com/z3/general/recovery-root-mm-575-291-lb-t3435214
Click to expand...
Click to collapse
I tried it and i did root my device, but is it a temporarily to install TWRP then after root your device you can't boot in recovery again ?
2nd thing My model number is D6633
Build number :- 23.5.A.0.570
what is the best custom Rom regarding stability and bug free here, if you tried many custom Rom?
I know that it depends on everyone opinion and needs, but I want to know your experience
Ahmed.ragab said:
I tried it and i did root my device, but is it a temporarily to install TWRP then after root your device you can't boot in recovery again ?
2nd thing My model number is D6633
Build number :- 23.5.A.0.570
what is the best custom Rom regarding stability and bug free here, if you tried many custom Rom?
I know that it depends on everyone opinion and needs, but I want to know your experience
Click to expand...
Click to collapse
Personly i like Xkeita linage os 14.1 it is mostly stable but i dont mine having 60 fps video recording it is a good stable rom
Cause my Nokia 3 was bricked then I searched for some information about Nokia 3 firmware from gsmhosting
Here is Details >----
[Nokia3_MT6737M_Heart_7.0_alps-mp-n0.mp1-V1.0.2_fih6737m.35.n_P96.rar 18.7 days old 1.3 GB 2017-Jul-15
Link
"https*://drive*.google*.com/drive/folders/0B0oLdVAk2l5va1ZlR05EVk5DXzQ"] Google drive
Upload by @pijush das
How to unlock Nokia3?Ref the threads =)
https://forum.xda-developers.com/nokia-3/how-to/guide-unlock-bootloader-root-flash-twrp-t3726649
https://forum.xda-developers.com/nokia-3/how-to/guide-how-to-unlock-bootloader-nokia-3-t3699344
how to get the unlock code?
https://forum.xda-developers.com/nokia-3/how-to/getting-unlock-code-t3757899
If you got the bricked phone, flashing the rom to rescue ,
https://forum.xda-developers.com/nokia-3/development/nokia-3-official-firmware-india-uae-t3674320
Require: use Chinese Miracle 2mtk(cm2mtk)tool to flash.
Finally, you need 3rd recovery to flash the supersu.
Ref https:/*/1drv.ms/u/s!AsmTb5aqoY12mDZqDZbPOp47QVMV
twrp for nokia3
How to get the rooted phone
Maybe you can refer @JBData's tutorial like this:
After many fails, I root my Nokia3.
- You must be easy with adb and fastboot and accept a full reset of your phone (data + soft).
- USB driver ok on your PC to connect device (device is always USB connected when roadacting)
- Be developper on your device (7 click on the series number), select USB debugging.
- Unlock your device (thanks to the_lazer), so you have the orange warning when starting.
- No need of TWRP. So many attempt with it, never succed. I even try, via the shell, the install-super.sh...
- Get the stock rom archive with this excellent post.
Here is my roadacts:
/ Install MagiskManager apk (MagiskManager-v5.5.5.apk) on your device.
/ Upload the boot.img file from the stock archive on your device.
/ In MagiskManager install Magisk and select the patch method.
/ Select the boot.img uploaded.
/ Upload the boot_patch.img file created on your PC.
/ Boot your device in recovery (power + volume up)
/ Select the full reset (data + soft) : You gonna loose everything on your device ! 3 partitions are formated : /data /nvdata...
/ Boot your device in recovery (power + volume up)
/ Select bootloader.
On your PC : fastboot devices -l, so you can see the connexion.
/ Re-flash all with the patch.
fastboot flash recovery recovery.img (maybe it's not necessary, but I prefer full reset and del TWRP...)
fastboot flash system system.img
fastboot flash boot boot_patched.img
fastboot reboot
/ Your device is (re)born.
/ let the config do.
/ Unactivate android update in the developper menu
/ In MagiskManager select install Magisk
/ You can do the check SafetyNet and so everything is green (If I could upload image, you would see)
/ Install RootChecker to confirm that your device is well rooted...
Click to expand...
Click to collapse
Thanks @JakesDen
(at) THE_lazer
@SkaboXD @blackpanther0582
AND
Thank for all supports from Nokia3's users. =3
i don't think that is possible to flash twrp on locked bootloader, but i will try it.
EDIT: Nope didn't worked
confirmed, this TWRP recovery working on ta-1032 with unlocked bootloader
the_laser said:
confirmed, this TWRP recovery working on ta-1032 with unlocked bootloader
Click to expand...
Click to collapse
without bugs?
battery percentage seems to be wrong, can't decrypt originally encrypted USERDATA volume ( i'm believe it is okay ), but main things working - can install SR2-SuperSU-v2.79-SR2-20170103215521.zip and that all i want from it.
very important - not allow /system modification until supersu installation !
another note - can't enter recovery by combination volume-up + power button, if phone not connected to computer
How did you unlock it ?
Sent from my TA-1032 using Tapatalk
fastboot-android.exe -i 0x2e04 oem key <unlockcode>
fastboot-android.exe -i 0x2e04 oem unlock
Hi Volks!
I am new to Android - well, a bit late, lol. Could someone please clarify the procedure to root the TA-1032 with the assets provided in this thread?
Also, are there any caveats when using TWRP Recovery Firmware, like are official updates possible?
Swordfishx86 said:
Hi Volks!
I am new to Android - well, a bit late, lol. Could someone please clarify the procedure to root the TA-1032 with the assets provided in this thread?
Also, are there any caveats when using TWRP Recovery Firmware, like are official updates possible?
Click to expand...
Click to collapse
My advice is: DON'T do it ! At this moment there is no safe mode to have root on TA-1032 and the latest news
on the future OS on Nokia3 says the Oreo will be delivered and even Android P !! You will loose those if you proceed now with root and unlocking.
All the best !
So ... Wait and hope?
Swordfishx86 said:
So ... Wait and hope?
Click to expand...
Click to collapse
The Warranty is 2 years,the same time Nokia will provide updates to OS.So,why to rush damaging the phone ?
In 2 years will be enough time for the Wonderful guys from TeamWin to make a safe TWRP for Nokia 3.
confirmed, this TWRP recovery working on TA-1032 with locked bootloader
Petrica said:
My advice is: DON'T do it ! At this moment there is no safe mode to have root on TA-1032 and the latest news
on the future OS on Nokia3 says the Oreo will be delivered and even Android P !! You will loose those if you proceed now with root and unlocking.
All the best !
Click to expand...
Click to collapse
Lol and how slower the phone will get with all those updates ?
If there are phones with OS versions older then the latest Google Android,it is a good motiv to rush to install a custom ROM build from the newest version of Android.
But its NOT the case for Nokia series who will have the latest OS for 2 Years !
Also I remind you that NOT the Android OS(pure on Nokia) is slowing down the phone-Its the apps:look at Facebook who was 8MB at the beginning and now consume a lot of resources-is almost 300 MB and is doing the same thing as was 8Mb .
All the best LOL !
Petrica said:
If there are phones with OS versions older then the latest Google Android,it is a good motiv to rush to install a custom ROM build from the newest version of Android.
But its NOT the case for Nokia series who will have the latest OS for 2 Years !
Also I remind you that NOT the Android OS(pure on Nokia) is slowing down the phone-Its the apps:look at Facebook who was 8MB at the beginning and now consume a lot of resources-is almost 300 MB and is doing the same thing as was 8Mb .
All the best LOL !
Click to expand...
Click to collapse
but it's still better to have custom roms because they have a lot more customization, wider compatibility with apps (for example xposed), better performance, maybe better battery if greatly optimized for our devices.
Also if we flash some custom rom, data encryption will be automatically removed.
SkaboXD said:
but it's still better to have custom roms because they have a lot more customization, wider compatibility with apps (for example xposed), better performance, maybe better battery if greatly optimized for our devices.
Also if we flash some custom rom, data encryption will be automatically removed.
Click to expand...
Click to collapse
With encryption eliminated you'll have boost in performance but this boost is lost due to not so greatly optimization of unofficial roms.
Sent from my TA-1032 using Tapatalk
Max brackenz said:
confirmed, this TWRP recovery working on TA-1032 with locked bootloader
Click to expand...
Click to collapse
Did you actually get twrp with a locked bootloader or that was a typo?
redweaver said:
Did you actually get twrp with a locked bootloader or that was a typo?
Click to expand...
Click to collapse
yes. its true . i flashed with spflashtool.
Max brackenz said:
yes. its true . i flashed with spflashtool.
Click to expand...
Click to collapse
Which spflashtool did you use? The usual one or a specialised one
redweaver said:
Which spflashtool did you use? The usual one or a specialised one
Click to expand...
Click to collapse
usual one. i have a nokia 3 support DA file.
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