Hey guys. Iam trying 1 week to get Havoc Oreo.
I used this https://forums.oneplus.com/threads/oxygenos-9-0-ota-for-the-oneplus-6.909533/ to get base Oreo Rom on my OP6. This works.
But when i want to flash Havoc Oreo (Havoc-OS-20180904-enchilada-Official.zip) via TWRP (twrp-installer-enchilada-3.2.2-0.zip only this Version works for me) i get a loop in fastboot.
Can someone help me pls?
My instruction:
1. Flash downgrade
2. Go fastboot, boot TWRP
3. Flash TWRP via ADB SIDELOAD
4. Restart to recovery
5. Flash Havoc Oreo via ADB SIDELOAD
6. Restart
7. Bootloop Fastboot mode
thanks for any help.
RockstarLover said:
Hey guys. Iam trying 1 week to get Havoc Oreo.
I used this https://forums.oneplus.com/threads/oxygenos-9-0-ota-for-the-oneplus-6.909533/ to get base Oreo Rom on my OP6. This works.
But when i want to flash Havoc Oreo (Havoc-OS-20180904-enchilada-Official.zip) via TWRP (twrp-installer-enchilada-3.2.2-0.zip only this Version works for me) i get a loop in fastboot.
Can someone help me pls?
My instruction:
1. Flash downgrade
2. Go fastboot, boot TWRP
3. Flash TWRP via ADB SIDELOAD
4. Restart to recovery
5. Flash Havoc Oreo via ADB SIDELOAD
6. Restart
7. Bootloop Fastboot mode
thanks for any help.
Click to expand...
Click to collapse
OK, so I am not sure what exists in the OnePlus forums but lets start with:
1. You are aware there are two sets of partitions on this device correct? If not, please read here: https://forum.xda-developers.com/oneplus-6/how-to/guide-noobs-guide-to-b-partitions-op6-t3816123
2. What are you running now?
3. You need to update your TWRP to blu_spark but I am not sure if the latest (v9.91) works with Oreo... I know that v9.86 works with Oreo for sure. Read and download from here: https://forum.xda-developers.com/oneplus-6/development/kernel-t3800965
4. Get the appropriate OOS zip file from this thread: https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244
Specifically OOS 5.1.11: https://www.androidfilehost.com/?fid=1322778262903980680
The basic steps should be like this (all assumes you have and unlocked bootloader):
1. If you are running OOS 5.1.11, reboot to fastboot
2. Boot blu_spark TWRP.img - fastboot boot twrp.xxx.img
3. Flash OOS 5.1.11
4. Flash blu_spark TWRP.zip to get it on both slots
5. Reboot to RECOVERY
6. Flash OOS 5.1.11
7. Flash blu_spark TWRP.zip
8. Factory reset in TWRP
9. Flash Havoc Oreo zip
10. Flash blu_spark TWRP.zip
11. Reboot to RECOVERY
12. Flash GApps
13. Flash Magisk (optional if you want root)
14. Flash no-verity if you plan to run unencrypted. (optional)
My advice is to READ READ READ before going forward with anything. The A/B partition layout is far from the traditional days of a single partition layout with a recovery partition. Educate yourself or risk bricking your device and opening up a whole different set of problems.
i do this by step by step but now iam bricked. after all it want restart but it glows only the blue led
RockstarLover said:
i do this by step by step but now iam bricked. after all it want restart but it glows only the blue led
Click to expand...
Click to collapse
It does sound like you READ READ READ before proceeding... My steps were not intended as a step-by-step guide, which is why I said the steps "should look like this". You didn't answer any of my questions, so I have no idea where you started from or where things went wrong to get you into this state...
Can you get into fastboot mode?
If so, try this thread first: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
The fastboot restore method will ONLY work if you know which OOS you were running before you got bricked...
If you can't restore from fastboot images, try this thread: https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
I cannot stress enough, you MUST read all the steps and understand what you are doing before doing anything. If you have any questions, ASK before proceeding... Good luck.
thank u for ur help. i used the second method because the first didnt worked and now iam unbricked.
1. You are aware there are two sets of partitions on this device correct?
Click to expand...
Click to collapse
I know it
2. What are you running now?
Click to expand...
Click to collapse
Now iam running Oxygen OS 5.1.5 Android 8.1.0 and Device State is locked
Is this normal that in fastboot shows this bootloader and baseband empty ?
productname - xxx
variant -sdm ufs
bootloader version -
baseband version -
serialnumber - xxxxxxx
secure boot - yes
I want to try again to get havoc oreo. i will w8 for ur response.
RockstarLover said:
thank u for ur help. i used the second method because the first didnt worked and now iam unbricked.
I know it
Now iam running Oxygen OS 5.1.5 Android 8.1.0 and Device State is locked
Is this normal that in fastboot shows this bootloader and baseband empty ?
productname - xxx
variant -sdm ufs
bootloader version -
baseband version -
serialnumber - xxxxxxx
secure boot - yes
I want to try again to get havoc oreo. i will w8 for ur response.
Click to expand...
Click to collapse
You are back up and running, good work! Congrats!
When you say the device is 'locked', you mean the bootloader is locked again? It shows 'Locked' in fastboot? Obviously you need to unlock the bootloader again before proceeding if this is the case...
And 'Yes', it is normal for 'bootloader version' and 'baseband' to be blank. It shows the same on my device anyway, and I can flash custom ROMs with no issues, and everything works.
At this point, you should be able to follow the steps in my post, making sure you first unlock the bootloader (which will wipe all of your data). You might want to format data (not just wipe as well) to start fresh. I would also confirm that there are no issues running Havoc Oreo with encryption (I'd recommend asking the question in the Havoc OnePlus telegram channel, https://t.me/havoconeplus). After people ask to "Why are you running Oreo?!?!", you just might get an answer... I dumped being encrypted after about a week of having this device because it made moving between ROMs more difficult.
In step 14, I mention the no-verity file to remove force encryption. I have attached it to this post. Again, you may want to have /data encrypted (necessity, personal preference etc.) so this isn't mandatory but I found it made flashing different ROM's much easier (personal preference really).
do u know where u find the havoc oreo rom now ? they changed their download directory. and the overview is confusing me.
RockstarLover said:
do u know where u find the havoc oreo rom now ? they changed their download directory. and the overview is confusing me.
Click to expand...
Click to collapse
Looks like they removed Oreo builds, you might be out of luck. Check out XenonHD 8.1 thread if your set on running Oreo, was updated to Dec. Security patch.
hey brother. i have good news. i just want download again havoc oreo cause i deleted the old zip. i had thought maybe the oreo havoc zip was faulty. now i restored it with a restore tool. i tried again and now it works.
IAM ON HAVOC OREO . It starts but now i got a message.
"Android System
A vendor image mismatch has been detected. Typically this means your vendor image is out of date.Please ensure your vendor image matches OPM1.171019.011."
what is this now
RockstarLover said:
hey brother. i have good news. i just want download again havoc oreo cause i deleted the old zip. i had thought maybe the oreo havoc zip was faulty. now i restored it with a restore tool. i tried again and now it works.
IAM ON HAVOC OREO . It starts but now i got a message.
"Android System
A vendor image mismatch has been detected. Typically this means your vendor image is out of date.Please ensure your vendor image matches OPM1.171019.011."
what is this now
Click to expand...
Click to collapse
Did you flash OOS 5.1.11 on both slots? I know you said you were on OOS 5.1.5 when you did the MSM tool restore.
Unsure if the Havoc build you are running requires a certain FW. Usually the devs update the blobs on customer ROMs based on the latest releases of OOS. In this case, 5.1.11 was the last version of OOS Oreo.
i was on 5.1.5 and flashed 5.1.11 on both slots and then i flashed havoc rom
RockstarLover said:
i was on 5.1.5 and flashed 5.1.11 on both slots and then i flashed havoc rom
Click to expand...
Click to collapse
I'd recommend just going to Pie. I haven't run Havoc in over a month but the latest AEX is solid and battery life is excellent. The Pie ROMs have stabilized significantly in the last month.
i just flashed the latest havoc rom now. Really really thanks brother. ur a good boy.
have a good year
Related
I'm on unrooted, unlocked bootloader OnePlus 6 With open beta 3 on stock recovery.
Just want to shift to stable pie. How to do that? Because when i tried using local upgrade option in system updates i got it can't be downgraded. Refer screenshot for better understanding
I only know how to do this with twrp.
So: fastboot boot twrp.img (guide in forum) (use latest blu_spark)
Flash latest blu_spark twrp.zip
Reboot to twrp
Flash rom.zip
Flash blu_spark twrp again
Not booting do it one more time.
Dont want twrp at all? Don't flash it after the rom.. I would keep it atleast until you know it all works, then dirty flash rom.zip to get rid of it.. If that's your cup of tea
whizeguy said:
I only know how to do this with twrp.
So: fastboot boot twrp.img (guide in forum) (use latest blu_spark)
Flash latest blu_spark twrp.zip
Reboot to twrp
Flash rom.zip
Flash blu_spark twrp again
Not booting do it one more time.
Dont want twrp at all? Don't flash it after the rom.. I would keep it atleast until you know it all works, then dirty flash rom.zip to get rid of it.. If that's your cup of tea
Click to expand...
Click to collapse
Thanks buddy
But i didn't understand "Not booting do it one more time" thing
In youre screenshot you have ob03 or 9.0 stable (15.09.5018).
Ob04 date is 29.09.2018
harigavara said:
Thanks buddy
But i didn't understand "Not booting do it one more time" thing
Click to expand...
Click to collapse
If the phone doesn't boot... Start over from step 1 one more time
Is there anyway doing it without flashing twrp? Wouldn't flashing it avoid warranty?
gabris said:
Is there anyway doing it without flashing twrp? Wouldn't flashing it avoid warranty?
Click to expand...
Click to collapse
(Unlocking the bootloader, Flashing twrp, rooting.....) don't void warranty on oneplus devices
I want to do the same, go from Pie beta 4 to Original Pie version, but have no root, twrp ot whatever. I enabled Developer Option, enabled OEM Unlock(bootloader) , downloaded the official OxygenOS from OnePlus. I go to System Updates, click Local Upgrade and select the ZIP, but then it says it can't since this version is older than the one installed and downgrade is not possible. Now what?
Second question: what s better, has more latest updates and news stuff; beta or the stable?
Gee, really nobody has a clue?
There is a special downgrade image to move from the Pie betas back to Oreo.
Search XDA or the the OnePlus forums for the downgrade image (it should be in one of the announcement threads for the betas).
After the downgrade to Oreo you can use an OTA or full download to upgrade to official Pie.
olafd72 said:
Gee, really nobody has a clue?
Click to expand...
Click to collapse
Sent from my ONEPLUS A6003 using Tapatalk
Hi there, can someone enlighten me how yo flash custom roms?my device already unlocked bootloader and i know how to flash cuz i play with xiaomi mi5, sams galaxy3 , sony x8.
For now i dont have a twrp. Im going twrp by fastboot before this.
Im really sure that i already go through all of the post. But seems from OB10 is really complicated.
1.ready fastboot twrp, bluspark twrp,roms, gapps and magisk( if necessary) and custom kernel
2.fastboot twrp by cmd or else
3.wipe what here? Or just factory reset and leave internal storage?
*Here i confused, do i need to wipe for both slot. Im still new to a/b partition. And do i need to do that for both slot to flash as steps 4-10 as below?
4.flash roms then bluspark twrp
5.reboot to recovery
6.flash gapps,magisk? Then twrp back?
7.reboot to twrp
8.flash custom kernel then twrp again?
9.reboot system
10. End right?
Please help me here. I cant find the real and proper steps. The only way i found is from OB7 to custom roms as they share same security patch.
Thanks for any help.
1. Flash any strock rom.zip partition A.
2. After that recovery.zip
3. Reboot back to recovery
4. Confirm you are in another slot B
5. Flash stock rom.zip. Which slot first is not important.
6. After that flash recovery.zip and then reboot.
After that you can install whatever you want.
That what I do if im switching roms and trying new stuff.
Working everytime.
Until OB7 and stable 9.0.2 I used fasboot roms, flashed via AIO tool, but new fastboot roms working different and I got laggy video and audio.
Okeh thats clear for both slot. But for OB10 to any customs rom is it needed to flash OB7?
What do you mean by stock rom?bete rom or stable rom?
slayerliar said:
Okeh thats clear for both slot. But for OB10 to any customs rom is it needed to flash OB7?
What do you mean by stock rom?bete rom or stable rom?
Click to expand...
Click to collapse
Stock any offical rom for OP6
9.0.2 or 9.0.3 or any OB3,4,5,6,7,8,9,10
If you want custom rom, look instructions, there is mentioned what is base rom. That you need flash.
If there is custom rom based OB7 then you need flash OB7(probably working lower builds also)
Thank brotha. I think they need to state which firmware do we need to start from. Otherwise it will be like me that confusing as they will patch up more and more security.
slayerliar said:
Thank brotha. I think they need to state which firmware do we need to start from. Otherwise it will be like me that confusing as they will patch up more and more security.
Click to expand...
Click to collapse
Pie ROM, pie firmware. (Except pre release betas)
Oreo ROM, Oreo firmware.
ROM - always flash latest firmware of the OS you want pie or Oreo (I always go for latest and don't have any issues . Tho I'm back to oos ,debloated now.)
Twrp - Always after ROMs, before roboot.
Gapps - after twrp and reboot, to make sure it installs to the right slot, that's why you install twrp and then reboot.. this will change your slot from A to B or from B to A. Manual switch is never necessary
Flashing gapps flashes to the slot you are in right now, so flashing before the first reboot (after twrp flash) Will get it to the wrong slot.
Magisk - if you want root. After all.
After all this you can, if you want, flash decrypt ..if you don't need your device to be encrypted,this Will give you more to think of tho.. let's just not go into this now.
i understand the process, but get confused at which file to specifically flash twice when they say
"latest firmware of the OS". So lets say the custom ROM i want to flash needs a PIE firmware 9.0.2 or higher,
what file am i supposed to flash?
9.0.2-PIE-OnePlus6Oxygen_22_OTA_027_all_1810260000_d46787d2c9-FASTBOOT.zip
or
OnePlus6Oxygen_22_OTA_027_all_1810260000_d46787d2c9.zip
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
hello there.
sorry for making a new thread .. ive asked my question multiple times no one answered properly. so here's the situation:
just received the phone from china . i'm on android pie hos. and want to update to ob7 . having root and twrp is it the right way to do it? :
1. update to ob7 using local update and full zip file.
2. unlock the bootloader and flash twrp 70 (or 74 i'm not sure?) using adb
3. flash magisk and twrp installer in twrp recovery
4. done!
i heared its better to use twrp 70 and dont know the reason. whats wrong with the latest version?
Not sure if that will work, but locally upgrading from h2OS to OOS worked on my old op6 when I had it.
If it does not work;
Backup your files first then you need to unlock your bootloader.
Then boot twrp via command prompt. Once booted into twrp. Wipe data and do a factory reset there. Flash twrp installer then reboot into recovery.
Flash OB7, twrp installer and magisk then reboot to recovery again and flash ob7, twrp installer and magisk then reboot to system
I'm using .74
Not sure what the problem is/are.
Regards
Dark Fear said:
hello there.
sorry for making a new thread .. ive asked my question multiple times no one answered properly. so here's the situation:
just received the phone from china . i'm on android pie hos. and want to update to ob7 . having root and twrp is it the right way to do it? :
1. update to ob7 using local update and full zip file.
2. unlock the bootloader and flash twrp 70 (or 74 i'm not sure?) using adb
3. flash magisk and twrp installer in twrp recovery
4. done!
i heared its better to use twrp 70 and dont know the reason. whats wrong with the latest version?
Click to expand...
Click to collapse
It can be done but I wasn't happy with it there were loads of bugs.. Issues slowdowns etc.. I would suggest strictly against it..
theocdguy said:
It can be done but I wasn't happy with it there were loads of bugs.. Issues slowdowns etc.. I would suggest strictly against it..
Click to expand...
Click to collapse
so whats the right way to do it
Dark Fear said:
so whats the right way to do it
Click to expand...
Click to collapse
Which route you want to follow twrp or official? If its official i'd say try the msm tool.. That will put you on oldest pie and then you can do OTA..
Twrp is self explanatory..
theocdguy said:
Which route you want to follow twrp or official? If its official i'd say try the msm tool.. That will put you on oldest pie and then you can do OTA..
Twrp is self explanatory..
Click to expand...
Click to collapse
i'm already on oldest pie.. whats the difference of his method with the one i mentioned?
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