Database Info

Safe to updated rooted and unlocked honor 6x on emui 4.1 via ota update?

Title says it all. I have a rooted and unlocked honor 6x on 4.1 and iust got a prompt for an update to 7.0/emui 5.
I've got the Chinese twrp version installed.

ctenc001 said:
Title says it all. I have a rooted and unlocked honor 6x on 4.1 and iust got a prompt for an update to 7.0/emui 5.
I've got the Chinese twrp version installed.
Click to expand...
Click to collapse
its ok you can, but make sure you have Stock recovery installed not the TWRP

ctenc001 said:
Title says it all. I have a rooted and unlocked honor 6x on 4.1 and iust got a prompt for an update to 7.0/emui 5.
I've got the Chinese twrp version installed.
Click to expand...
Click to collapse
Unroot it, flash stock boot.img and stock recovery.img and proceed wit OTA

shashank1320 said:
Unroot it, flash stock boot.img and stock recovery.img and proceed wit OTA
Click to expand...
Click to collapse
Not necessary!
You just have to flash stock recovery!

gaebzn said:
Not necessary!
You just have to flash stock recovery!
Click to expand...
Click to collapse
If you are rooted, it wont boot and go to erecovery with a prompt that your data partition was damaged. You can give it a go

shashank1320 said:
If you are rooted, it wont boot and go to erecovery with a prompt that your data partition was damaged. You can give it a go
Click to expand...
Click to collapse
Wasn't so on my last updates... what are you rooted with? Magisk or supersu?

gaebzn said:
Wasn't so on my last updates... what are you rooted with? Magisk or supersu?
Click to expand...
Click to collapse
It applies to both. SuperSu and Magisk. I am rooted with SuperSU. There is already a thread on Magisk which states for this. And being a SueprSu user for years, I have seen this myself on my BLN-AL10B375 to B379 and BLN-L21C185C360 to BLN-L21C185C365.

shashank1320 said:
It applies to both. SuperSu and Magisk. I am rooted with SuperSU. There is already a thread on Magisk which states for this. And being a SueprSu user for years, I have seen this myself on my BLN-AL10B375 to B379 and BLN-L21C185C360 to BLN-L21C185C365.
Click to expand...
Click to collapse
Just remembered I updated via dload...sorry...my fault...maybe thats why it worked.
But thank you! I will try the b368 with your guide!
I'm a bit ashamed now?
Edit: do you have stock boot.img for b365?

gaebzn said:
Just remembered I updated via dload...sorry...my fault...maybe thats why it worked.
But thank you! I will try the b368 with your guide!
I'm a bit ashamed now?
Edit: do you have stock boot.img for b365?
Click to expand...
Click to collapse
In repository thread you will get on main page or last 2-3 pages. @RedSkull23 has shared it.
Yes, dload replaces stock boot and recovery so that will work.
Been gone through many ups n down with 6X so i know many things now
No need to be ashamed, these are tricky and sometimes hard to remember as we try 10 things at a time
If need b367 then here
https://forum.xda-developers.com/ho...covery-boot-img-request-t3707216/post74649229

shashank1320 said:
In repository thread you will get on main page or last 2-3 pages. @RedSkull23 has shared it.
Yes, dload replaces stock boot and recovery so that will work.
Been gone through many ups n down with 6X so i know many things now
No need to be ashamed, these are tricky and sometimes hard to remember as we try 10 things at a time
If need b367 then here
https://forum.xda-developers.com/ho...covery-boot-img-request-t3707216/post74649229
Click to expand...
Click to collapse
Thank you mate!

shashank1320 said:
In repository thread you will get on main page or last 2-3 pages. @RedSkull23 has shared it.
Yes, dload replaces stock boot and recovery so that will work.
Been gone through many ups n down with 6X so i know many things now
No need to be ashamed, these are tricky and sometimes hard to remember as we try 10 things at a time
If need b367 then here
https://forum.xda-developers.com/ho...covery-boot-img-request-t3707216/post74649229
Click to expand...
Click to collapse
Got a weird problem. If i flash this boot.img for 365 I can't enter my phone. It boots up, i can enter my pin, but the encryption password doesn't work! It's very strange, cause I've never changed it since first setup! Any idea? Or do you have another boot img for b 365? Thanks

gaebzn said:
Got a weird problem. If i flash this boot.img for 365 I can't enter my phone. It boots up, i can enter my pin, but the encryption password doesn't work! It's very strange, cause I've never changed it since first setup! Any idea? Or do you have another boot img for b 365? Thanks
Click to expand...
Click to collapse
My boot.img provided in repository thread is for BLN-L21C432B365 build, as listed in OP and in my post there; what's your build number? An unmatching build could be the cause of this. For example, recovery for BLN-L21C432B365, differs from BLL-L21C130B365 - the B365 at the end is equal, but the build variant is different and so incompatible

RedSkull23 said:
My boot.img provided in repository thread is for BLN-L21C432B365 build, as listed in OP and in my post there; what's your build number? An unmatching build could be the cause of this. For example, recovery for BLN-L21C432B365, differs from BLL-L21C130B365 - the B365 at the end is equal, but the build variant is different and so incompatible
Click to expand...
Click to collapse
My buildnumber is exactly the same. Very strange. Can an installed busybox be responsible for those things?

gaebzn said:
My buildnumber is exactly the same. Very strange. Can an installed busybox be responsible for those things?
Click to expand...
Click to collapse
You may try uninstalling the busybox and then retry to see if it works.

[ROOT][TRIAL][MAGISK] P20 Pro - Try out on Rooting Method

Hi Guys,
Note : By doing this, you know that you're gonna do a modification to your phone, and im not in any way, responsible for what happen after. Escape Route for if something wrong happen is provided, but YOU DO THIS ON YOUR OWN RISK
since this phone is fairly new, at this moment a clear rooting method haven't established yet. This is what this thread for.
Based on information gathered from P20 Lite Forum (the rooting guide for that device even already up - here), it seems the old trick of rooting (from Mate 10 Pro) using Patched Boot Method is working fine. And Magisk is working
Basically this method need few pre-requisites :
1. Unlocked Bootloader (by getting the code here ) - and if you not sure how to do it, go here for the guide
2. Stock Boot (or RAMDISK to be precise for this phone) - I managed to extract it from 8.1.0.106 ROM version for CLT-L29 (download here)
3. Magisk Manager 5.5.4 (from Magisk Thread) to patch the .img above, or
4. Patched RAMDISK image (i patched it) from here
5. and of course computer with ADB & Fastboot installed (make sure you have latest SDK to prevent something not working)
Now, to Root it, all you need to do is,
1. Boot into bootloader
2. Type
Code:
fastboot flash ramdisk patched_boot.img
(patched_boot.img is the file you download from prerequisites number 4, placed it in the same directory with your adb & fastboot - i assume you know that already)
3. Reboot
4. You now should have root access, download Magisk Manager to manage modules and superuser
(you might need to flash this module if you failed to pass safetynet)
In case something go wrong, flash back the stock RAMDISK from pre-requistes number 2 above using same method as what u did to flash the patched one.

That way worked. Thanks.
Edit:
Just as a hint. To get magisk work as it should..
After boot into the system and installed Magisk Manager, install Magisk from there again, so you dont get any /data/magisk problems.
SafteyNet passed then.

Fingers crossed twrp is possible soon

Works on CLT-L09
I have a German single Sim from Vodafone tested the root yesterday and works very well

Would this method work on CLT-L09 model? Thanks

danifilth4king said:
Would this method work on CLT-L09 model? Thanks
Click to expand...
Click to collapse
The post before you just confirmed yourbquestion, LoL
Yes it does

This is awesome, thanks for sharing! I thought I could live without root but after only half a day, I've decided I can't!
Before I do this, I was wondering where you managed to get the stock rom (quote below)?
otonieru said:
2. Stock Boot (or RAMDISK to be precise for this phone) - I managed to extract it from 8.1.0.106 ROM version for CLT-L29 (download here)
Click to expand...
Click to collapse

fl4r3 said:
This is awesome, thanks for sharing! I thought I could live without root but after only half a day, I've decided I can't!
Before I do this, I was wondering where you managed to get the stock rom (quote below)?
Click to expand...
Click to collapse
It's from www.allrom.ir (its in persian) and there's another site, rusian one if am not mistaken, but i forget the exact address

Great, thanks for that! I managed to find it on allrom.ir

Hey guys, I need some help please! I unlocked bootloader through Huawei website which went fine and then when I flashed the patched boot.img through fastboot and tried to reboot my phone has told me there was a critical error while booting. It won't boot to system and just loops a few times and then boots to Huawei eRecovery. This is my first Huawei device and I'm clueless as to how to recover
Any ideas would be much appreciated! Thanks
**EDIT*** false alarm! I managed to boot to fastboot and restore the ramdisk from the first post

danifilth4king said:
Hey guys, I need some help please! I unlocked bootloader through Huawei website which went fine and then when I flashed the patched boot.img through fastboot and tried to reboot my phone has told me there was a critical error while booting. It won't boot to system and just loops a few times and then boots to Huawei eRecovery. This is my first Huawei device and I'm clueless as to how to recover
Any ideas would be much appreciated! Thanks
**EDIT*** false alarm! I managed to boot to fastboot and restore the ramdisk from the first post
Click to expand...
Click to collapse
What is your phone model ? CLT-L29 or L09 ? And what is your ROM version ?

otonieru said:
What is your phone model ? CLT-L29 or L09 ? And what is your ROM version ?
Click to expand...
Click to collapse
It's CLT-L09, build number 8.1.0.103(C782)
It's and EE UK handset. Any ideas why it wouldn't have worked? Thanks

danifilth4king said:
It's CLT-L09, build number 8.1.0.103(C782)
It's and EE UK handset. Any ideas why it wouldn't have worked? Thanks
Click to expand...
Click to collapse
The ramdisk.img was taken from .106 ROM, so its actually newer than what installed on your phone. That might become issue,
But, do you managed to revive the phone using the stock ramdisk from first post ?

otonieru said:
The ramdisk.img was taken from .106 ROM, so its actually newer than what installed on your phone. That might become issue,
But, do you managed to revive the phone using the stock ramdisk from first post ?
Click to expand...
Click to collapse
Yes thank you, the stock ramdisk from the first post allowed my phone to boot normally again. Do you think if I use magisk manager app to patch the stock ramdisk it will work for me? Or is that the same as what you did to make the patched boot.img anyway?

danifilth4king said:
Yes thank you, the stock ramdisk from the first post allowed my phone to boot normally again. Do you think if I use magisk manager app to patch the stock ramdisk it will work for me? Or is that the same as what you did to make the patched boot.img anyway?
Click to expand...
Click to collapse
If you have the 103 rom, and able to extract the ramdisk yourself, you can try patch it yourself.
Have you tried to flash the patch ramdisk one more time ? In case it just a bad flash.
Because if you manage to boot using stock one. It means your system has no problem using .106 boot image and the patched one should work as well

otonieru said:
If you have the 103 rom, and able to extract the ramdisk yourself, you can try patch it yourself.
Have you tried to flash the patch ramdisk one more time ? In case it just a bad flash.
Because if you manage to boot using stock one. It means your system has no problem using .106 boot image and the patched one should work as well
Click to expand...
Click to collapse
Ok I will try again and report back. How do you boot into fastboot from device off state by the way? I had difficulty doing it earlier. Thanks again!

danifilth4king said:
Ok I will try again and report back. How do you boot into fastboot from device off state by the way? I had difficulty doing it earlier. Thanks again!
Click to expand...
Click to collapse
Its better to do it from ON state, and use adb reboot bootloader command

otonieru said:
Its better to do it from ON state, and use adb reboot bootloader command
Click to expand...
Click to collapse
I mean if the patched boot.img still doesn't work again and the device won't boot to system? I did it before when I flashed back to stock ramdisk, but I don't know how I entered fastboot exactly lol

danifilth4king said:
I mean if the patched boot.img still doesn't work again and the device won't boot to system? I did it before when I flashed back to stock ramdisk, but I don't know how I entered fastboot exactly lol
Click to expand...
Click to collapse
Put the device off and hold power button and volume down. You should come directly into the rescue mode.

danifilth4king said:
I mean if the patched boot.img still doesn't work again and the device won't boot to system? I did it before when I flashed back to stock ramdisk, but I don't know how I entered fastboot exactly lol
Click to expand...
Click to collapse
Ah, sorry, i got it wrong. Yes, its power n volume down.

How To Root Oxygen 5.1.7

Oneplus updated the OnePlus 6's Bootloader and you may ask yourself 'Can i still root?'
The answer is yes. It is easy.
1. At first, your bootloader has to be unlocked
2. Just download the Twrp.img and the Twrp installer from twrp.me, then the latest magisk installer
3. Put the magisk.zip and twrp installer zip into the root of your device and boot into bootloader
4. Now you have to open a new shell or cmd window in your adb folder, then type "Fastboot devices" there
5. If your phone is recognized, then do this command: " fastboot boot .\twrp-3.2.1-0-enchilada.img"
6. The op6 should boot into the TWRP, there type in your pincode, pattern, or what so ever you have. If you get a message because of system modification, click 'Keep read only'
7. Go to 'Install', then flash the TWRP installer zip, then magisk right after it
8. Just reboot and enjoy
The procedure is the same as always. I can confirm it's working because i rooted a few minutes ago

Just keep in mind the kernels and custom roms haven't been updated to 5.1.7 base yet and may not work until they are.

iElvis said:
Just keep in mind the kernels and custom roms haven't been updated to 5.1.7 base yet and may not work until they are.
Click to expand...
Click to collapse
Forgot the mention that, thanks!

Edit: Screenshots

Flash kernel works. Btw please don't create threads on how to root if the method hasn't changed lol

joemossjr said:
Flash kernel works. Btw please don't create threads on how to root if the method hasn't changed lol
Click to expand...
Click to collapse
Sorry, I thought that would be helpful for people who are worried about root because of updated bootloader.
A Moderator can remove this thread then

joemossjr said:
Flash kernel works. Btw please don't create threads on how to root if the method hasn't changed lol
Click to expand...
Click to collapse
Based on how things have been going so far, people are going to be asking. Just saying.

i understand butttttttttttttttttttttt this forum is flooded with how to flash twrp, how to root with 5.1.6, how to install 5.1.5 with twrp ect ect ect lol just trying to reduce clutter and make things a tad bit simpler. No offense guys lol

So if I already have twrp and Magisk installed is the method still the same?
Will this update lock the bootloader back?
Pretty sure I swiped to allow system modifications on my first twrp installation so will that matter?

joemossjr said:
i understand butttttttttttttttttttttt this forum is flooded with how to flash twrp, how to root with 5.1.6, how to install 5.1.5 with twrp ect ect ect lol just trying to reduce clutter and make things a tad bit simpler. No offense guys lol
Click to expand...
Click to collapse
Yes I know. I mean, you're right. Thought something like "new bootloader, new confusions". I justed wanted to help people if they're worried of a brick

dgunn said:
So if I already have twrp and Magisk installed is the method still the same?
Pretty sure I swiped to allow system modifications on my first twrp installation so will that matter?
Click to expand...
Click to collapse
Don't worry. You can use TWRP and your phone itself as always

Sconny said:
Don't worry. You can use TWRP and your phone itself as always
Click to expand...
Click to collapse
So do I flash the update in twrp?
Must the bootloader be unlocked again?

dgunn said:
So do I flash the update in twrp?
Must the bootloader be unlocked again?
Click to expand...
Click to collapse
No you flash in system via local upgrade

joemossjr said:
No you flash in system via local upgrade
Click to expand...
Click to collapse
Flash with local upgrade, reboot to fastboot, run twrp.img, install twrp, flash Magisk and reboot? No unlocking bootloader again?
If not correct please tell me

Yup that's it

joemossjr said:
No you flash in system via local upgrade
Click to expand...
Click to collapse
Flash in system.. you mean through the system updates in settings? And then I have to reinstall TWRP?

BossNexusS said:
Flash in system.. you mean through the system updates in settings? And then I have to reinstall TWRP?
Click to expand...
Click to collapse
Yes

joemossjr said:
Yes
Click to expand...
Click to collapse
What were the steps you followed if you don't mind?

Maybe someone will upload the full rom?

anyone tried hiding system updates inside magisk hide ?
it now shows only 224 update (canadian vpn), hence don't know what it will do when you take that route, anyone ?

Oneplus 6 root qualcomm crash dump

So i recently updated to android pie. I rooted my Oneplus 6 a while ago, but it was removed with an OTA update. Now i'm in fastboot with an unlocked bootloader attempting to boot into twrp-3.2.3-0-enchilada.img using the command "fastboot boot twrp-3.2.3-0-enchilada.img". After doing this instead of taking me to the twrp menu it takes me to a qualcomm crash dump screen. Is there something i'm doing wrong. Thanks!

Giodude12 said:
So i recently updated to android pie. I rooted my Oneplus 6 a while ago, but it was removed with an OTA update. Now i'm in fastboot with an unlocked bootloader attempting to boot into twrp-3.2.3-0-enchilada.img using the command "fastboot boot twrp-3.2.3-0-enchilada.img". After doing this instead of taking me to the twrp menu it takes me to a qualcomm crash dump screen. Is there something i'm doing wrong. Thanks!
Click to expand...
Click to collapse
Use bluespark or black themed twrp

https://forum.xda-developers.com/showpost.php?p=77748695&postcount=7
another member is having the same issue, here's my recommendation. let me know if it helps please.

Giodude12 said:
So i recently updated to android pie. I rooted my Oneplus 6 a while ago, but it was removed with an OTA update. Now i'm in fastboot with an unlocked bootloader attempting to boot into twrp-3.2.3-0-enchilada.img using the command "fastboot boot twrp-3.2.3-0-enchilada.img". After doing this instead of taking me to the twrp menu it takes me to a qualcomm crash dump screen. Is there something i'm doing wrong. Thanks!
Click to expand...
Click to collapse
Same situation, same problem. I tried:
Code:
fastboot boot twrp-3.2.3-x_blu_spark_v9.85_op6.img
and still I end up in CrashDump Mode.

mackler said:
Same situation, same problem. I tried:
and still I end up in CrashDump Mode.
Click to expand...
Click to collapse
Use v9.86

yldlj said:
Use v9.86
Click to expand...
Click to collapse
Works. Thank you!! :victory:

yldlj said:
Use v9.86
Click to expand...
Click to collapse
Same, that was the issue, thanks!

Giodude12 said:
So i recently updated to android pie. I rooted my Oneplus 6 a while ago, but it was removed with an OTA update. Now i'm in fastboot with an unlocked bootloader attempting to boot into twrp-3.2.3-0-enchilada.img using the command "fastboot boot twrp-3.2.3-0-enchilada.img". After doing this instead of taking me to the twrp menu it takes me to a qualcomm crash dump screen. Is there something i'm doing wrong. Thanks!
Click to expand...
Click to collapse
actually, now my phone wont get past those spinning circles when it starts up. I can get into recovery. What can i do to fix this?
EDIT: I restored my old bootloader, but now my phone isn't rooted. I have twrp recovery. i tried flashing magisk 17.1, is there something here i shouldn't have done?

Giodude12 said:
actually, now my phone wont get past those spinning circles when it starts up. I can get into recovery. What can i do to fix this?
EDIT: I restored my old bootloader, but now my phone isn't rooted. I have twrp recovery. i tried flashing magisk 17.1, is there something here i shouldn't have done?
Click to expand...
Click to collapse
if you are on stock firmware, why do you want twrp? Unless you are going to aosp rom or want to decrypt the phone, twrp is not needed then.

MrSteelX said:
if you are on stock firmware, why do you want twrp? Unless you are going to aosp rom or want to decrypt the phone, twrp is not needed then.
Click to expand...
Click to collapse
Just looked into it. For whatever reason it doesn't work on Android p unless I run the uninstaller first. Thanks for the help though, I'm all good.

Use v9.86 of ... ??
yldlj said:
Use v9.86
Click to expand...
Click to collapse
Use v9.86 of what ??

dash_z1 said:
Use v9.86 of what ??
Click to expand...
Click to collapse
Blu spark twrp..

Thank you
whizeguy said:
Blu spark twrp..
Click to expand...
Click to collapse
thank you just reialized that i`m supposed to use blue spark version of twrp for my op6 although they provided the original twrp links which was misleading in the root post

unable to come in recovery

Hello,
I'm unable to come in recovery.
After English>Advanced>Boot in recovery
it always comes back in the main screen where you must choose language.
My OP6 seems to be encrypted (however I dit not choose for).
OS 10.3.5
I use Magisk 20.4
How to solve this?
Greetings,
Hans

hansare said:
Hello,
I'm unable to come in recovery.
After English>Advanced>Boot in recovery
it always comes back in the main screen where you must choose language.
My OP6 is decrypted (however I dit not choose for).
OS 10.3.5
I use Magisk 20.4
How to solve this?
Greetings,
Hans
Click to expand...
Click to collapse
I think you are in soft brick. Use the Tool AIO by mauro and flash recovery.img via fastboot.

Wrong place...this is roms and kernels section, next time post it in question's section...

Huh?
This is Q&A section.

hansare said:
Huh?
This is Q&A section.
Click to expand...
Click to collapse
Even made me go back and look! LOL ?

tiga016 said:
I think you are in soft brick. Use the Tool AIO by mauro and flash recovery.img via fastboot.
Click to expand...
Click to collapse
Fastboot means adb for me.
How does this work with AIO? I can't find a detailed instruction.
Thanks in advance.

hansare said:
Fastboot means adb for me.
How does this work with AIO? I can't find a detailed instruction.
Thanks in advance.
Click to expand...
Click to collapse
According to their website flashing stock recovery with AIO isn't possible for OP6.
Whatever the reason may be.
Moreover I miss general instructions how to use AIO.
Anyone a solution for my problem?

hansare said:
According to their website flashing stock recovery with AIO isn't possible for OP6.
Whatever the reason may be.
Moreover I miss general instructions how to use AIO.
Anyone a solution for my problem?
Click to expand...
Click to collapse
If you have adb,
Try 'adb reboot bootloader'
You'll get to fastboot
Download TWRP img on your pc and twrp zip on your phone
'fastboot boot twrp.img'
You'll be booted to TWRP
Flash twrp.zip to install twrp from booted twrp
Read Rooting n TWRP threads for more details.
Edit: My bad. I missed that you need stock recovery. TWRP may be better option though. IIRC, you can get stock recovery by flashing unmodified boot.img of whatever oos version you are on, but try at your own risk. Also if nothing works, you should backup your data and use msm download tool to restore your phone to factory state.

Thanks.
I want to have back the ability to go into recovery (stock or custom doesn't matter).
Are you sure you're suggestion is the solution?
Could it be an encryption problem which blocks whatever recovery?

hansare said:
Thanks.
I want to have back the ability to go into recovery (stock or custom doesn't matter).
Are you sure you're suggestion is the solution?
Could it be an encryption problem which blocks whatever recovery?
Click to expand...
Click to collapse
As you mentioned in the first post that you are already decrypted, then it shouldn't be a problem.
Anyways you can use mauronofrio TWRP for decryption support (it will ask you for pattern or pass).
As my solution is only valid if you can access your sdcard from twrp, you can try it risk free.
The command "fastboot boot twrp.img" only boots the recovery, doesn't flash it. So it's pretty safe to try.
And to save all the hassle, just backup all data and restore your phone to factory settings using MsmDownload Tool.

Thank you very much.
In first posting I made a stupid mistake. My OP6 seems to be encrypted as it asks for pass when I try to boot in recovery.
As I understand your last post AIO will ask for pass when I boot twrp, correct?
Then I'm booted in twrp and have to flash twrp.zip but is that possible with an encrypted device?
Basic question.
I did not permit for encryption. How is it possible that the device still is?

Deleted because twice.

hansare said:
Thank you very much.
In first posting I made a stupid mistake. My OP6 seems to be encrypted as it asks for pass when I try to boot in recovery.
As I understand your last post AIO will ask for pass when I boot twrp, correct?
Then I'm booted in twrp and have to flash twrp.zip but is that possible with an encrypted device?
Basic question.
I did not permit for encryption. How is it possible that the device still is?
Click to expand...
Click to collapse
Every Device is encrypted by default. It usually is your lockscreen password. Just enter the same password in twrp and you'll be able to access the files.
Aslo it's not AIO that asks password. It is twrp which will ask you password if you have one set i.e. your lockscreen password/pattern.