Related
Yesterday I recieved my phone and I unlocked the bootloader as well as rooted using CF. Today I tried to flash the OTA LRX21O (I'm on LNX07M) in TWRP but I'm getting the error "Package expects build fingerprint of google/shamu/shamu:5.0/LNX07M/1543455: user/release-keys or google/shamu/shamu : 5.0/LRX210/1570415 : user/release-keys; this device has Android/aosp_shamu/shamu:5.0LRX21M/dees_troy11191312:userdebug/test-keys"
What the heck does this mean? I also tried flashing back to stock recovery but it just ended up with an android image with "error" below it. I'm assuming it ran into the same problem. Do I need to wipe and start all over??
RandoTheKing said:
Yesterday I recieved my phone and I unlocked the bootloader as well as rooted using CF. Today I tried to flash LRX21O in TWRP but I'm getting the error "Package expects build fingerprint of google/shamu/shamu:5.0/LNX07M/1543455: user/release-keys or google/shamu/shamu : 5.0/LRX210/1570415 : user/release-keys; this device has Android/aosp_shamu/shamu:5.0LRX21M/dees_troy11191312:userdebug/test-keys"
What the heck does this mean? I also tried flashing back to stock recovery but it just ended up with an android image with "error" below it. I'm assuming it ran into the same problem. Do I need to wipe and start all over??
Click to expand...
Click to collapse
You can't install the OTA if you rooted. You'll probably need to just install the factory images via fastboot.
akellar said:
You can't install the OTA if you rooted. You'll probably need to just install the factory images via fastboot.
Click to expand...
Click to collapse
I thought you could always just flash them manually? When did this change? No point in rooting if I'm going to stay stock, it seems.
RandoTheKing said:
I thought you could always just flash them manually? When did this change? No point in rooting if I'm going to stay stock, it seems.
Click to expand...
Click to collapse
5.0 essentially makes it break OTA when you root/modify anything. This has been known for a bit now (which is why I downloaded the update before I did any rooting/unlocking on my device).
Dr Faustus said:
5.0 essentially makes it break OTA when you root/modify anything. This has been known for a bit now (which is why I downloaded the update before I did any rooting/unlocking on my device).
Click to expand...
Click to collapse
well what will you do for future updates? Full wipe?
RandoTheKing said:
well what will you do for future updates? Full wipe?
Click to expand...
Click to collapse
http://www.androidpolice.com/2014/1...e-means-update-will-fail-system-modified-way/
not really - you can just flash the "old" stock system image file and then install the update (or just flash the "new" system file)
Dr Faustus said:
5.0 essentially makes it break OTA when you root/modify anything. This has been known for a bit now (which is why I downloaded the update before I did any rooting/unlocking on my device).
Click to expand...
Click to collapse
jj14 said:
http://www.androidpolice.com/2014/1...e-means-update-will-fail-system-modified-way/
not really - you can just flash the "old" stock system image file and then install the update (or just flash the "new" system file)
Click to expand...
Click to collapse
Any instructions on how to do that? I'm assuming I can still get the update that way
RandoTheKing said:
Any instructions on how to do that? I'm assuming I can still get the update that way
Click to expand...
Click to collapse
It should be the same as the "back to stock" process
Download new (or old) factory images
Unzip and extract the IMG files
Take nandroid backup on phone
Reboot to recovery
Connect to PC (assuming drivers are installed)
Use fastboot to flash the necessary images
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase cache
Edit - flash the cache.img instead of just erasing cache
I had trouble flashing the factory image initially. I kept getting an error so I used this method and it worked perfectly. Hope it helps. http://www.ibtimes.co.uk/how-fix-er...roid-5-0-factory-images-nexus-devices-1474865
So i am root and have done a bit of work on my Nexus 6 (changing system sounds, setting it up and a few other things) If i want to install LRX21O, what is the step by step to do that and after i install it if i do a Nandroid Backup, can i restore the backup on LRX21O? I am currently on LNX07M.
I am curious as well. Also do you happen to have a link to the file to just update.?
EDIT... Found it. Will flash when home
Sent from my Nexus 6 using XDA Free mobile app
jj14 said:
It should be the same as the "back to stock" process
Download new (or old) factory images
Unzip and extract the IMG files
Take nandroid backup on phone
Reboot to recovery
Connect to PC (assuming drivers are installed)
Use fastboot to flash the necessary images
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase cache
Click to expand...
Click to collapse
Should that be `fastboot format cache`?
jm77 said:
Should that be `fastboot format cache`?
Click to expand...
Click to collapse
Actually, you should just flash the cache.img
jj14 said:
It should be the same as the "back to stock" process
Download new (or old) factory images
Unzip and extract the IMG files
Take nandroid backup on phone
Reboot to recovery
Connect to PC (assuming drivers are installed)
Use fastboot to flash the necessary images
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase cache
You don't reboot into recovery if you are using fas boot. You boot into boot loader at least that's how I've done it on every Nexus that I've had.
Edit - flash the cache.img instead of just erasing cache
Click to expand...
Click to collapse
jm77 said:
Should that be `fastboot format cache`?
Click to expand...
Click to collapse
You can use both commands to first format, then flash the new one it doesn't really matter. I've used both methods
jj14 said:
Actually, you should just flash the cache.img
Click to expand...
Click to collapse
Hi there.
I have been flashing ROMS since ICS (Ice Cream Sandwich) but for the last 18 months I have been a bit disconnected from it.
I am also new to everything Huawei.
I find a lot of times people referring to the eRecovery.
Where does this terminology (eRecovery) differ from the normal recovery, be it stock recovery or TWRP?
Is this eRecovery a Huawei thing or am I missing something?
Thanks in advance.
It is nothing to really worry or even think about. I don't think you can get rid of it or even if you could there is no reason. It's just second recovery which does a different things than the normal stock recovery. I think the eRcovery is needed for the stock update, but normal recovery isn't(not completely sure about this).
It is just good to know that device also has eRecovery, because there are some users who install TWRP and then they boot to eRecovery and then they think the TWRP installation failed.
I don't know is it just huawei thing.
Hope this helps a bit, even though it's a bit messy info.
keikari said:
It is nothing to really worry or even think about. I don't think you can get rid of it or even if you could there is no reason. It's just second recovery which does a different things than the normal stock recovery. I think the eRcovery is needed for the stock update, but normal recovery isn't(not completely sure about this).
It is just good to know that device also has eRecovery, because there are some users who install TWRP and then they boot to eRecovery and the they think the TWRP installation failed.
I don't know is it just huawei thing.
Hope this helps a bit, even though it's a bit messy info.
Click to expand...
Click to collapse
Thanks for the information.
It has definitely given me a much better idea regarding what is eRecovery.
Much appreciated.
it's basically useless on this phone. it will never fetch any package nor restore your device. most people either just keep it and dont bother using it or flash TWRP over it. by having stock recovery as 'recovery' and TWRP as 'recovery2' you can have access to official OTA updates yet still being able to do everything you could do with TWRP
Carkai said:
...by having stock recovery as 'recovery' and TWRP as 'recovery2' you can have access to official OTA updates yet still being able to do everything you could do with TWRP
Click to expand...
Click to collapse
Nice! I am interested in that!
Keeping both recoveries and not loosing OTA sounds good to me.
Have you any idea how to accomplish this please? Any link or for that matter where could I download stock recovery for PRA-LX1?
Thank you!
droidbits said:
Nice! I am interested in that!
Keeping both recoveries and not loosing OTA sounds good to me.
Have you any idea how to accomplish this please? Any link or for that matter where could I download stock recovery for PRA-LX1?
Thank you!
Click to expand...
Click to collapse
flash this as recovery (fastboot flash recovery RECOVERY.img) and this as recovery2 (fastboot flash recovery2 twrp-3.1.1-2-v1-prague.img)
Carkai said:
flash this as recovery (fastboot flash recovery RECOVERY.img) and this as recovery2 (fastboot flash recovery2 twrp-3.1.1-2-v1-prague.img)
Click to expand...
Click to collapse
Thank you!
I was really trying to find the stock recovery for PRA-LX1 from somewhere. Very handy!
Now, having both recoveries flashed, I gather that there will be also the need to unroot when I want to receive OTA or not?
droidbits said:
Thank you!
I was really trying to find the stock recovery for PRA-LX1 from somewhere. Very handy!
Now, having both recoveries flashed, I gather that there will be also the need to unroot when I want to receive OTA or not?
Click to expand...
Click to collapse
nope! you can install OTAs with root and unlocked bootloader (although you have to download and install FULL-OTA packages. basically just clicking three dots when you've received an update and selecting 'download full package' or something like that)
Hello! My Y9 2018 FLA-LX3 uses fastboot flash recovery_ramdisk for TWRP, but it removes stock recovery. Can I flash TWRP to the recovery2/erecovery slot? And if so, what is the command? I have ramdisk, so to flash TWRP I'd use recovery_ramdisk instead of recovery. So, do I use recovery2_ramdisk? Thx!
RustyBl0ck said:
Hello! My Y9 2018 FLA-LX3 uses fastboot flash recovery_ramdisk for TWRP, but it removes stock recovery. Can I flash TWRP to the recovery2/erecovery slot? And if so, what is the command? I have ramdisk, so to flash TWRP I'd use recovery_ramdisk instead of recovery. So, do I use recovery2_ramdisk? Thx!
Click to expand...
Click to collapse
Yes, you can flash TWRP over eRecovery.
Since A8 and above you can not install TWRP over eRecovery from fastboot, only from TWRP:
- Copy TWRP file to the SD card
- Boot in TWRP, select storage - SD Card, select "Install image", find TWRP file and mark eRecovery, swipe.
- reboot .
-Alf- said:
Yes, you can flash TWRP over eRecovery.
Since A8 and above you can not install TWRP over eRecovery from fastboot, only from TWRP:
- Copy TWRP file to the SD card
- Boot in TWRP, select storage - SD Card, select "Install image", find TWRP file and mark eRecovery, swipe.
- reboot .
Click to expand...
Click to collapse
Oh thx! But I don't like it bc my goal is to leave stock recovery INTACT. So, I've been also trying to use fastboot to use fastboot boot "TWRP".img That's my goal, even though it hasn't worked. That is my ideal solution. Thx"!
RustyBl0ck said:
Oh thx! But I don't like it bc my goal is to leave stock recovery INTACT. So, I've been also trying to use fastboot to use fastboot boot "TWRP".img That's my goal, even though it hasn't worked. That is my ideal solution. Thx"!
Click to expand...
Click to collapse
And what's stopping you from installing TWRP instead of eRecovery and then installing Recovery back?
No matter what your ideal solution is, this is the only way.
Okay. So, I can an have tried to install TWRP just normally using fastboot flash recovery_ramdisk twrp.img That works, but the issue is that I can't find the stock/original recovery.img to replace it with when I'm finished. I extracted the UPDATE.APP and found a recovery_ramdisk.img. I am kinda scared to try to flash it using the same command for twrp, so I haven-t tried it. Can u pls tell me if I shall do it So in theory, fastboot flash recovery_ramdisk recovery_ramdisk.img
Oh and FYI, that image was extracted from a working UPDATE.app I used for my particular phone and it has always worked, just that it restores EVERYTHING. I just want the recovery back when I finish with TWRP. I-m giving it away and dont want the new owners messing with TWRP, since it can do harm to the phone if misused. Thx!!!
RustyBl0ck said:
. I am kinda scared to try to flash it using the same command for twrp, so I haven-t tried it. Can u pls tell me if I shall do it So in theory, fastboot flash recovery_ramdisk recovery_ramdisk.img
Click to expand...
Click to collapse
Sure, you can flash recovery_ramdisk using command
RustyBl0ck said:
fastboot flash recovery_ramdisk recovery_ramdisk.img
Click to expand...
Click to collapse
Or, you can flash it in TWRP ("install image" option).
How do I uninstall TWRP and unroot my Honor 9 Lite so i can update the phone to LLD-L31 8.0.0.128(C432) with face unlock?
I have already locked bootloader.
When i reboot the phone it automatically brings me to eRecovery and when i "Download latest version and recovery" it says "Getting package info failed". Please help
OmaroOmaro said:
How do I uninstall TWRP and unroot my Honor 9 Lite so i can update the phone to LLD-L31 8.0.0.128(C432) with face unlock?
I have already locked bootloader.
Click to expand...
Click to collapse
Looks like you "played" a bit to much with your phone. There is no official TWRP yet and no official Firmware Image. So, this looks very bad for you to get out of this again.
Maybe try HiSuite from Huawei or MultiTool
https://forum.xda-developers.com/devdb/project/dl/?id=28734
Probably this could help as long as you can connect via ADB or HDB from HiSuite.
Good luck...
Hey, I've faced the exact same issue. After playing even a bit more, I manged to revert my device (LLD-L31) back to stock.
I've uploaded all the files I used, for you.
It passes SafetyNet check successullfy!
Download required files here
Here is was I did:
Format data using TWRP (Wipe -> Format data)
Enter fastboot mode (Connect to PC, power+ VolDown)
fastboot flash ramdisk ramdisk.emmc.win
fastboot flash kernel kernel.emmc.win
fastboot flash system SYSTEM.img
fastboot reboot
Click to expand...
Click to collapse
Please tell me, if it worked!
Note:
The SYSTEM.img is extracted from the UPDATE.APP from this site.
Kernel and ramdisk are from a LOS-15.1 TRWP backup. Not sure if they're required, but it didn't work for me without flashing them.
error while extracting update.app
hello sir, I'm getting this error while extracting update.app.. recovery ramdisk.img invalid header crc - Expected: 18707 Got:56582
creativeanand said:
hello sir, I'm getting this error while extracting update.app.. recovery ramdisk.img invalid header crc - Expected: 18707 Got:56582
Click to expand...
Click to collapse
Why exactly do you need to extrac the update.app? I've already uploaded all required files and linked them in my previous post.
Also, which program did you use? Which operating system did you use?
now my phone is looping
MateUserHHTT said:
Why exactly do you need to extrac the update.app? I've already uploaded all required files and linked them in my previous post.
Also, which program did you use? Which operating system did you use?
Click to expand...
Click to collapse
now my phone is looping on off, on of
and i can't go to fastboot
creativeanand said:
now my phone is looping on off, on of
and i can't go to fastboot
Click to expand...
Click to collapse
In order for me to help you, I need to know exactly what you did.
So what did you do before your phone went into bootloop? (And don't worry, my Honor 9 lite has been in bootloops 100 of times, we can fix that! )
And how did you try to enter fastboot?
Make sure your phone is connected to a computer via USB!
Then press and hold Volume DOWN and Power button until phone reboots.
Release power when you see the blue honor screen.
Release volume down key, when you are in fastboot.
MateUserHHTT said:
In order for me to help you, I need to know exactly what you did.
So what did you do before your phone went into bootloop? (And don't worry, my Honor 9 lite has been in bootloops 100 of times, we can fix that! )
And how did you try to enter fastboot?
Make sure your phone is connected to a computer via USB!
Then press and hold Volume DOWN and Power button until phone reboots.
Release power when you see the blue honor screen.
Release volume down key, when you are in fastboot.
Click to expand...
Click to collapse
after flash shall i wipe data/ factory reset?
creativeanand said:
after flash shall i wipe data/ factory reset?
Click to expand...
Click to collapse
Again, I need to know whay you did!
You don't necessarily need to factory reset after a flash. But it probably won't make things worse.
But if you are switching the ROM (stock to a custom Rom) you indeed have to format data in twrp.
MateUserHHTT said:
Again, I need to know whay you did!
You don't necessarily need to factory reset after a flash. But it probably won't make things worse.
But if you are switching the ROM (stock to a custom Rom) you indeed have to format data in twrp.
Click to expand...
Click to collapse
i unlocked my phone bcoz the sound of h9l was lower then Redmi note 5 so i wanted to boost the sound with aris sound system and dolby atmos app.
after flashing 'SUPERSU' phone was not starting freeze at honor logo and then i wiped & rested in twrp...
now i did fastboot as you said now eRecovery is asking download latest version, wipe data/ f rest, reboot, shoutdown what shall i do now,,....thank you for helping
creativeanand said:
i unlocked my phone bcoz the sound of h9l was lower then Redmi note 5 so i wanted to boost the sound with aris sound system and dolby atmos app.
after flashing 'SUPERSU' phone was not starting freeze at honor logo and then i wiped & rested in twrp...
now i did fastboot as you said now eRecovery is asking download latest version, wipe data/ f rest, reboot, shoutdown what shall i do now,,....thank you for helping
Click to expand...
Click to collapse
Ok, now I can help you.
First of all, install TWRP. Use img2 (the experimental test build) if img #1 just stucks at the TWRP screen and won't enter the recovery.
Tell me when you succeed
You can get TWRP from here
https://forum.xda-developers.com/9-lite/development/recovery-twrp-3-2-1-0-t3789306
MateUserHHTT said:
Ok, now I can help you.
First of all, install TWRP. Use img2 (the experimental test build) if img #1 just stucks at the TWRP screen and won't enter the recovery.
Tell me when you succeed
You can get TWRP from here
https://forum.xda-developers.com/9-lite/development/recovery-twrp-3-2-1-0-t3789306
Click to expand...
Click to collapse
i did now?
creativeanand said:
i did now?
Click to expand...
Click to collapse
Great!
Now just follow my instructions from my earlier post
Make sure to put the files you download in the same folder as you run fastboot commands, so fastboot can find these files.
Good luck!??
MateUserHHTT said:
Great!
Now just follow my instructions from my earlier post
Make sure to put the files you download in the same folder as you run fastboot commands, so fastboot can find these files.
Good luck!
Click to expand...
Click to collapse
i did as you said .. now phone is not starting stoped at huawei eRecovery
whan i go to twrp phone reboots itshalf after 10sec
If you can boot to bootloader
and bootloader = unlocked
and FRP = unlock
then you can reset the phone to stock-rom
you need download with HuaweiFirmwareFinder 1 FULL-Update from YOUR build
i see in FF "LLD-L31C432B131 FullOTA-MF
download the 3 files, extract with HuaweiUpdateExtractor
- ramdisk.img
- recovery_ramdis.img
- system.img
the extractor do automatik for all *.img 1 *.img.header
copy this 6 files to your ADB-Folder
For reset to stock-rom
- fastboot flash ramdisk ramdisk.img
- fastboot flash recovery_ramdisk recovery_ramdis.img
- fastboot flash system system.img
after this reboot the phone, eRecovery format low-level "data", phone reboot and start as "new" phone (initial settings)
before you do this you can do 1 test :
- fastboot flash recovery_ramdisk recovery_ramdis.img
why?
format low-level "data" work ONLY with stock-recovery, NOT with TWRP
after this is your "data" encrypt !
Only 1 TWRP work with encrypt/decrypt : https://forum.xda-developers.com/9-lite/development/recovery-twrp-3-2-1-0-t3789306
if phone work set PIN for Screen-open (this PIN need TWRP by start for encrypt/decrypt "data")
if you need, you can now flash recovery_ramdisk TWRP.img
if you need install OTA-Updates : if OTA-Update on your phone "install update now ?" answer "NO, later" and
- fastboot flash recovery_ramdisk recovery_ramdis.img (stock-recovery)
and install Update now.
if all work and you need : flash TWRP
i hope you understand this "way"
the advantage : you can install with TWRP OR flash developer-system.img and if anything not work - reset phone to stock-rom
i use ONLY TWRP with encrypt. this is security-question. if phone lost - data is encrypt !
TWRP without encrypt work only
- boot to TWRP
- format data
- boot from TWRP to TWRP
- data have now NO encrypt
Doesn't Android use FBE by default since Android O, so the data is always encrypted no matter what TWRP was used?
JamesBott said:
If you can boot to bootloader
and bootloader = unlocked
and FRP = unlock
then you can reset the phone to stock-rom
you need download with HuaweiFirmwareFinder 1 FULL-Update from YOUR build
i see in FF "LLD-L31C432B131 FullOTA-MF
download the 3 files, extract with HuaweiUpdateExtractor
- ramdisk.img
- recovery_ramdis.img
- system.img
the extractor do automatik for all *.img 1 *.img.header
copy this 6 files to your ADB-Folder
For reset to stock-rom
- fastboot flash ramdisk ramdisk.img
- fastboot flash recovery_ramdisk recovery_ramdis.img
- fastboot flash system system.img
after this reboot the phone, eRecovery format low-level "data", phone reboot and start as "new" phone (initial settings)
before you do this you can do 1 test :
- fastboot flash recovery_ramdisk recovery_ramdis.img
why?
format low-level "data" work ONLY with stock-recovery, NOT with TWRP
after this is your "data" encrypt !
Only 1 TWRP work with encrypt/decrypt : https://forum.xda-developers.com/9-lite/development/recovery-twrp-3-2-1-0-t3789306
if phone work set PIN for Screen-open (this PIN need TWRP by start for encrypt/decrypt "data")
if you need, you can now flash recovery_ramdisk TWRP.img
if you need install OTA-Updates : if OTA-Update on your phone "install update now ?" answer "NO, later" and
- fastboot flash recovery_ramdisk recovery_ramdis.img (stock-recovery)
and install Update now.
if all work and you need : flash TWRP
i hope you understand this "way"
the advantage : you can install with TWRP OR flash developer-system.img and if anything not work - reset phone to stock-rom
i use ONLY TWRP with encrypt. this is security-question. if phone lost - data is encrypt !
TWRP without encrypt work only
- boot to TWRP
- format data
- boot from TWRP to TWRP
- data have now NO encrypt
Click to expand...
Click to collapse
sir shall i go to service center i have warrenty
creativeanand said:
sir shall i go to service center i have warrenty
Click to expand...
Click to collapse
By unlocking the bootloader you've void your warranty.
They will probably charge you for the repair.
What happens if you install this version of TWRP?
It's on Chinese, click the little icon in the top right corner and select "English".
If it doesn't crash, try this one.
Make sure to follow the correct steps for flashing.
fastboot flash recovery_ramdisk [filename.img]
fastboot flash reboot
QUICKLY unplug USB and before it fully reboots, hold press Volume up key
If it fails, check out this guide:
https://forum.xda-developers.com/9-lite/how-to/guide-unbrick-device-recover-bootloop-t3772563
My hon or 9 lite is in teaming page and it won't open I have tried to update via erecOvery but it won't work and I cannot go to recovery mode please help me.
@Prabin99
what you build ?
what have you do before start the update ?
have you anything flashed ?
I was rooted through Magisk on firmware .255, but I saw an approved update for firmware .280 which I wanted, and I also wanted to go back to stock for a while. I downloaded the update.zip, extracted the .img needed and flashed accordingly; cust, erecovery, system, cache, kernel, recovery, userdata, etc, all I could.
I now can't get it to boot no matter what I try. I always end up on the screen "Your device has been unlocked and can't be trusted" and then stuck on "Your device is booting now". I can get into eRecovery and/or flash TWRP.
I've tried the below;
Flashing dload folder on a USB OTG
Flashing update zip in TWRP
Flashing update zip with Huruupdater in TWRP
Flashing through fastboot update (update.app extracted)
Flashing through fastboot update_full_base (update.app extracted)
Going through HiSuite - it sees the recovery but then says "No recovery packages found for your phone"
Wipe data etc.
I did forget to remove fingerprint security before I did this, my bootloader is unlocked and FRP.
Genuinely never bricked a phone before! Any help would be appreciated.
I think it's because I need to flash boot.img but I can't see that when I extract from update.app
Does anyone have one please?
Don't make me buy a pixel tomorrow!
belloni said:
I think it's because I need to flash boot.img but I can't see that when I extract from update.app
Does anyone have one please?
Click to expand...
Click to collapse
it because there's no boot.img for EMUI 9, it's recovery_ramdis.img and kernel.img did you flash that ?
try to pull recovery_ramdis.img from the Update.app and patch it using latest magisk 19.4 and flash it then try to boot again
otonieru said:
it because there's no boot.img for EMUI 9, it's recovery_ramdis.img and kernel.img did you flash that ?
try to pull recovery_ramdis.img from the Update.app and patch it using latest magisk 19.4 and flash it then try to boot again
Click to expand...
Click to collapse
Yeah I've flashed those two.
How can I patch it if I can only get into TWRP?
belloni said:
Yeah I've flashed those two.
How can I patch it if I can only get into TWRP?
Click to expand...
Click to collapse
EDIT: I've found the old magisk_patched.img but when I flash it says "FAILED (remote: partition length get error)
belloni said:
Yeah I've flashed those two.
How can I patch it if I can only get into TWRP?
Click to expand...
Click to collapse
from other phone with magisk installed.
other thing you might want to try is enter stock recovery (not TWRP) and wipe /data and cache from there
just a heads up though,
your way of updating the OS is totally dangerous, you could.messed up partition,
you should use EMUI Flasher instead
I have a guide to fix this in the guides section. Follow it and you'll be fine.
Find somebody that had a p20 pro rooted to send you a backup of their software (with the data partition wiped).
https://forum.xda-developers.com/showpost.php?p=79107368&postcount=82
Leaving this here as i ended up boot looping from installing custom kernel, and it being a new release i was pulling my hair trying to figure this out.
Flashed through fastboot with "fastboot flash boot_a XX.img, fastboot flash boot_b XX.img"
Magisk included as thats the one i ended up using.
Save yourself the headache if you are planning on installing a custom kernel for now, and wait till the kinks have been ironed out.
I found a workaround. Firstly go to fastboot mode and flash stable.img from here https://forum.xda-developers.com/t/...os11-open-beta-2-3-and-stable-latest.4316563/ and boot into recovery. Now download TWRP and magisk and transfer to internal storage. Now flash TWRP and then download full OTA from here And put in storage https://www.xda-developers.com/oneplus-6-6t-oxygenos-11-1-1-1/
and flash it. Don't reboot once it says done. Go back and re install twrp.zip. Now reboot. Go to recovery and install magisk and clear dalvik. Now reboot and enjoy.
Thanks to
KizuYuna and Skanda Hazarika for providing stable.img and OTA respectively.
235anders15 said:
Leaving this here as i ended up boot looping from installing custom kernel, and it being a new release i was pulling my hair trying to figure this out.
Flashed through fastboot with "fastboot flash boot_a XX.img, fastboot flash boot_b XX.img"
Magisk included as thats the one i ended up using.
Save yourself the headache if you are planning on installing a custom kernel for now, and wait till the kinks have been ironed out.
Click to expand...
Click to collapse
So I just flash the Magisk Patched into a and b slots and that should get me root using fastboot flash commands mentioned above? Sorry just wanted to double-check given that I had almost bricked my phone y'day :-D
sam_htc_touch said:
So I just flash the Magisk Patched into a and b slots and that should get me root using fastboot flash commands mentioned above? Sorry just wanted to double-check given that I had almost bricked my phone y'day :-D
Click to expand...
Click to collapse
Thats what worked for me, had to improvise as the OTA was brand new when I installed it, and bricked it with a new kernel, and had tried to fix it by flashing an old boot img but ended up complicating things even more.
You could always grab the stock 11.1.1.1 boot img and patch it in magisk manager yourself but procedure would be the same in fastboot
235anders15 said:
Thats what worked for me, had to improvise as the OTA was brand new when I installed it, and bricked it with a new kernel, and had tried to fix it by flashing an old boot img but ended up complicating things even more.
You could always grab the stock 11.1.1.1 boot img and patch it in magisk manager yourself but procedure would be the same in fastboot
Click to expand...
Click to collapse
Thanks a bunch for confirming, this gives me confidence and will go with patching mine as well
sam_htc_touch said:
Thanks a bunch for confirming, this gives me confidence and will go with patching mine as well
Click to expand...
Click to collapse
Thanks a bunch @235anders15 I can confirm that I used your patched magisk image file and flashed it in both slots and have root back ..yayy! Simple process
sam_htc_touch said:
Thanks a bunch @235anders15 I can confirm that I used your patched magisk image file and flashed it in both slots and have root back ..yayy! Simple process
Click to expand...
Click to collapse
Just for the benefit of all (if it matters), noticed that Magisk wasn't passing the Safety Net check and was showing failed for all 3. Used this fix and all is well now (Used the Sept 13 update on the page)
previously patching with stable 11.1.1.1 and broke some major functionality (eg: wifi crash, mess up video player and codec), now try to patch with magisk version, will update later
abhi0039 said:
I found a workaround. Firstly go to fastboot mode and flash stable.img from here https://forum.xda-developers.com/t/...os11-open-beta-2-3-and-stable-latest.4316563/ and boot into recovery. Now download TWRP and magisk and transfer to internal storage. Now flash TWRP and then download full OTA from here And put in storage https://www.xda-developers.com/oneplus-6-6t-oxygenos-11-1-1-1/
and flash it. Don't reboot once it says done. Go back and re install twrp.zip. Now reboot. Go to recovery and install magisk and clear dalvik. Now reboot and enjoy.
Thanks to
KizuYuna and Skanda Hazarika for providing stable.img and OTA respectively.
Click to expand...
Click to collapse
stable.img from there (and the other ones) dont fastboot boot on my OSS 1.1.1.1 fastboot mode.
I followed 235anders15 post and flashed both a and b slots, but it ended with endless boot logo (red dot with spinning white dot).
I can't go to fastboot mode, nothing.... please help!
F5:ed said:
I followed 235anders15 post and flashed both a and b slots, but it ended with endless boot logo (red dot with spinning white dot).
I can't go to fastboot mode, nothing.... please help!
Click to expand...
Click to collapse
Press and hold vol up, down , power at the same time for a while it will boot to fastboot.
I got boot loop after updating to 11.1.2.2
Any new boot img?
izik.avi said:
I got boot loop after updating to 11.1.2.2
Any new boot img?
Click to expand...
Click to collapse
Haven't tested yet but here you go
rippledrums said:
Haven't tested yet but here you go
Click to expand...
Click to collapse
This one works great. Thank you.
The attached file in #13 above worked, thank you!
In case someone would like to now "How to do it" until next time this is how I did it:
How to install OOS update and root via created patch.img file in the Magisk app
1. Download the full version eg the OOS 11.x.x.x.zip file on the computer, and copy the file to the phone's internal memory as well.
2. Run the payload_dump program (https://androidfilehost.com/?fid=1899786940962605222) to extract a boot.img from the computer. You have to extract the payload.bin file from the OOS 11.x.x.x.zip file and place it in the Input folder, then run the exe-file and wait for payload to complete, then copy over the boot.img file found in the Output folder to the phone.
3. Go to Magisk app on the phone, click on the top install "Magisk", click "Select and patch a file", search for the boot.img file you created.
4. Now, Magisk will create a patched magic.img file from the boot.img file (can be called eg magic_patched-23000_xt8QR.img)
5. Copy the magisk_patched-xxxxxxx.img to your computer's "Root folder" where you have stored ADB files, etc
6. Now install the OOS 11.x.x.x zip file (should be in the mobile's Internal memory) via Settings> System> System updates and the "gear"> Local upgrade
7. When done, DO NOT reboot but go directly to Fastboot mode + connect cable to the computer
8. On the computer, type from your "Root folder":
fastboot flash boot magisk_patched-xxxxxxx.img
9. Reboot the phone - you are rooted!
rippledrums said:
Haven't tested yet but here you go
Click to expand...
Click to collapse
Is this magiskpatched.img for oneplus 6t?? Can I flash this in fastboot mode to root my oneplus 6t?
raymund08 said:
Is this magiskpatched.img for oneplus 6t?? Can I flash this in fastboot mode to root my oneplus 6t?
Click to expand...
Click to collapse
Yes
rippledrums said:
Yes
Click to expand...
Click to collapse
Thank you
Can confirm OP fastboot commands and patched boot img are working for 11.1.1.1.I uninstalled magisk by mistake and could regain root, quick and painless
Can anyone help me? flashed patched boot to A and B Slot. But Magisk is N/A. Any idea?