Related
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
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 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
Hello,
I have a P20 Pro with unlocked bootloader, i decided to updated the phone trought OTA by flashing original recovery and instal OTA of Android 10.
After that i wanted to get back to TWRP then root my phone, but i get surprised that the phone bootloader get locked again after update.
I need to unlock my bootloader again in order to use my phone. the command in fastboot : fastboot oem unlock **************** (i put my old unlocking code which already worked 2 years ago)
but i get as a result :
...
FAILED (remote: invalid command)
finished. total time : 0.027s
can anyone help me getting back my bootloader unlocked and twrp installed please ? i dont want loose my phone
NB : i confirm again that my code was working before on android 9 and had bootloader unlocked
Rovyo said:
Hello,
I have a P20 Pro with unlocked bootloader, i decided to updated the phone trought OTA by flashing original recovery and instal OTA of Android 10.
After that i wanted to get back to TWRP then root my phone, but i get surprised that the phone bootloader get locked again after update.
I need to unlock my bootloader again in order to use my phone. the command in fastboot : fastboot oem unlock **************** (i put my old unlocking code which already worked 2 years ago)
but i get as a result :
...
FAILED (remote: invalid command)
finished. total time : 0.027s
can anyone help me getting back my bootloader unlocked and twrp installed please ? i dont want loose my phone
NB : i confirm again that my code was working before on android 9 and had bootloader unlocked
Click to expand...
Click to collapse
You idiot EMUI 10 cannot be bootloader unlocked, downgrade to EMUI 9.0!!!
If you want android 10 or even 11 you need something called a GSI, which I can inform you about it.
jjgvv said:
You idiot EMUI 10 cannot be bootloader unlocked, downgrade to EMUI 9.0!!!
If you want android 10 or even 11 you need something called a GSI, which I can inform you about it.
Click to expand...
Click to collapse
i'm really an idiot i can confirm that, how to downgrade please ? my bootloader in locked right now
Rovyo said:
i'm really an idiot i can confirm that, how to downgrade please ? my bootloader in locked right now
Click to expand...
Click to collapse
HISUITE
jjgvv said:
HISUITE
Click to expand...
Click to collapse
You saved me mate, was really a dumb move to go thought OTA without checking this point. Didn't now Huawei become that ******
Any advice for a good custom rom based on android 10 ?
And thanks again for your precious help
Rovyo said:
You saved me mate, was really a dumb move to go thought OTA without checking this point. Didn't now Huawei become that ******
Any advice for a good custom rom based on android 10 ?
And thanks again for your precious help
Click to expand...
Click to collapse
I can get you Android 11 actually, though there are a few bugs on both 10 and 11.
jjgvv said:
I can get you Android 11 actually
Click to expand...
Click to collapse
even better if it is android 11, i will try it
also have another dumb question : if i install TWRP on the EMUI 9.1 with unlocked bootloader, can i flash the emui 10 rom thought TWRP ? or this will brick the phone ?
Rovyo said:
even better if it is android 11, i will try it
also have another dumb question : if i install TWRP on the EMUI 9.1 with unlocked bootloader, can i flash the emui 10 rom thought TWRP ? or this will brick the phone ?
Click to expand...
Click to collapse
Yes, system will be 'destroyed', as you modded the recovery.
jjgvv said:
Yes, system will be 'destroyed', as you modded the recovery.
Click to expand...
Click to collapse
that what i was thinking also, so bye Emui 10 for ever i guess.
what was the rom base on android 11 you are referring to ?
GSI Project treble rom.
The definition is https://source.android.com/setup/bu...tem image (GSI,or higher can run successfully.
Google's Offical GSI will not boot on huaweis though.
After unlock bootloader download this https://github.com/phhusson/treble_...v300.l/system-roar-arm64-aonly-vanilla.img.xz
use 7zip(https://www.7-zip.org/a/7z1900-x64.exe) to extract the file once and rename it to system.img and move to C drive WITHOUT under any folders.
Then go to recovery and factory reset, do not advance wipe, wipe>factory reset only
Then go to fastboot and
fastboot flash system C:\system.img
Failing to follow will result in rage!
Backup System, Vendor, Data and Internal storage in TWRP before doing anything will be a wise choice, in case anything is wrong.
Forgot to mention you must flash magisk in TWRP before installing rom, to disable AVB(Android Vertified Boot) so that a custom rom can be loaded.
jjgvv said:
Backup System, Vendor, Data and Internal storage in TWRP before doing anything will be a wise choice, in case anything is wrong.
Click to expand...
Click to collapse
Yeah for sur, i'm rolling back, unlocking BL then TWRP in order to get a full backup. I ll check the rom after that
A senior member refer to for EMUI 10 upgrading :
"Don't update system via OTA when phone is rooted or bootloader unlock. Flash firmware via erecovery and rooted again"
i think this is incorrect right ? he cant root again while on EMUI 10 ?
jjgvv said:
Forgot to mention you must flash magisk in TWRP before installing rom, to disable AVB(Android Vertified Boot) so that a custom rom can be loaded.
Click to expand...
Click to collapse
thanks for the proper advice
Rovyo said:
Yeah for sur, i'm rolling back, unlocking BL then TWRP in order to get a full backup. I ll check the rom after that
A senior member refer to for EMUI 10 upgrading :
"Don't update system via OTA when phone is rooted or bootloader unlock. Flash firmware via erecovery and rooted again"
i think this is incorrect right ? he cant root again while on EMUI 10 ?
Click to expand...
Click to collapse
https://github.com/SkyEmie/huawei-honor-unlock-bootloader
Read troubleshooting part, EMUI 10 cannot unlock bootloader
jjgvv said:
https://github.com/SkyEmie/huawei-honor-unlock-bootloader
Read troubleshooting part, EMUI 10 cannot unlock bootloader
Click to expand...
Click to collapse
the lasted TWRP release cant decrypt the data, trying to find a working one and the phone don't want to boot to recovery anymore even with volume up + power bouton or via command adb reboot recovery. seems a good day hahaha
Still boots fastboot? Otherwise you are screwed
jjgvv said:
Still boots fastboot? Otherwise you are screwed
Click to expand...
Click to collapse
what do you mean ? yes i still can go on fastboot and already rolled back to Emui 9.1
just want to boot on damn recovery hahaha and if it can decrypt daba will be great
jjgvv said:
Still boots fastboot? Otherwise you are screwed
Click to expand...
Click to collapse
well i'm stuck with twrp not decrypting my data
i managed to install TWRP (several version), boot on them and so nothing to do
also can get root easily and magisk as i sideload zip from crypted TWRP version (worked)
tried the version twrp_clt_0.1.img from XDA stuck on TWRP starting screen
i'm almost giving up
Extract Android 11 Gsi, rename to system.img and move to C drive , not under any folders.
Go to fastboot then
Fastboot erase data
Fastboot erase cache
Fastboot flash system C:\system.img
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 ...