Database Info

Help please mate 9 bricked after successful Oreo update

Hi everyone, I have the mha-l29 and successfully updated to the latest Oreo for the US version. I then unlocked the bootloader, flashed TWRP, flash Superuser and everything was working fine. I then got an error message while doing a backup in TWRP and foolishly edited a file which caused the system to not boot. I then Flashed the hwoa7 instead of 8 to fix it and now my phone is bricked. The only thing I can do is get into fastboot. Everything else throws an error. Is ee a func no: 11 error. Please see attached pictures. Please let me know how I can fix it. I've already tried reflashing the ramdisk as well as TWRP bet I can't boot into TWRP.
Thanks so much
C:\>fastboot oem lock-state info
(bootloader) FB LockState: LOCKED
(bootloader) USER LockState: UNLOCKED
OKAY [ 0.008s]
finished. total time: 0.012s

Do you mean you flashed RECOVERY_nocheck from Nougat to Recovery of Oreo?
If so you should only need to flash recovery_ramdisk.
I guess you could extract ramdisk, recovery_ramdisk and kernel and flash to the partitions of the same name.
See what error it gives after you flash back stock recovery_ramdisk

Thank you for your help ante. I ended up fixing it by using DC unlocker. That Basically got me to where I could boot into erecovery. It also allowed me to use ADB to flash TWRP. From there I just flashed the entire hwota8 package. I'm back up and running thankfully. Once again, I really appreciate you and people like you who help others on this forum.

saw this to late , TWRP caused this i had the same thing earlier and reinstalled different TWRP

seti007 said:
Thank you for your help ante. I ended up fixing it by using DC unlocker. That Basically got me to where I could boot into erecovery. It also allowed me to use ADB to flash TWRP. From there I just flashed the entire hwota8 package. I'm back up and running thankfully. Once again, I really appreciate you and people like you who help others on this forum.
Click to expand...
Click to collapse
DC-Unlockr allowed you to use adb to flash twrp? How were you able to do that exactly?

I was able to flash the entire update package using DC Unlocker. That should have gotten me up fully but it did not. Before using DC unlocker, I was not able to even boot into TW RP or erecovery. I was able to get into fastboot but could not install anything. I did not get any errors in ADB and installations were successful but I could not boot into TWRP. After using DC Unlocker, I went back into fastboot and used ADP to install TW RP. I was then able to boot into TW RP. So the difference that DC unlocker made was that it allowed me to use ADB to successfully install TWRP.

I had the very same issue previously with another device. It was running an old version of TWRP. Regardless of what I flashed, it would give errors, etc.
However, using ADB, I flashed the very latest recovery and voila! Flashed a rom successfully as well as other apps without any issues.
It's always best to use the latest possible recovery to avoid issues with flashing.
Glad you solved your problem

Wirmpolter said:
DC-Unlockr allowed you to use adb to flash twrp? How were you able to do that exactly?
Click to expand...
Click to collapse
Good sir, can you link me to a working twrp? I tried several twrps, but i cant seem to boot into recovery. TIA

marktheripper said:
Good sir, can you link me to a working twrp? I tried several twrps, but i cant seem to boot into recovery. TIA
Click to expand...
Click to collapse
Were you running Android Nougat or Oreo? I've just used the TWRP's found here on the xda forums. However, I didn't use TWRP nor dc-unlockr to fix my issue. Have you tried the hardware button combo of volume up And power to boot into it?

Oreo. I tried using the twrps available, but i cant seem to boot into twrp. It goes directly to error mode. Im using the power + vol up btw.

[Recovery][TWRP][EMUI8.x] [P20 Lite] Testing

Disclaimer​This software comes wth no warranty,XDA staff ,myself or TeamWin staff can't be hold responsible for any damage it may cause to your device.
Note: Currently Oreo 8.1 custom roms are not supported,only stock EMUI 8.x .
Download and Installation​
* Download twrp recovery
* Start your device in fastboot mode
* Install the recovery using the following command:
Code:
fastboot flash recovery_ramdisk [filename].img --> ex: fastboot flash recovery_ramdisk twrp_p20_lite_0.1.img
* Restart with this command:
Code:
fastboot reboot
* As soon as you execute the restart command,remove the USB cable and keep pressing Volume UP,so the device will boot to TWRP.This is to avoid that the device boot to OS,overwritting TWRP recovery.
Features​
Internal storage decryption = working
MTP and OTG connection = working
Backup&Restore = working
Note: There are no sources for this yet,because is based on the work of @zxz0O0 ,from Honor 9.
Contributors
**** Pretoriano80
**** @zxz0O0 - This wouldn't be possible without this guy,so big big thank to him.I used his base to make this recovery work ,so in sign of respect his nick will also be on the TWRP boot screen.Thank again buddy!
**** TeamWin project ,obviously.
**** Team OpenKirin - thanks for the "Oem Path wipe esclusion" code
Download links
twrp_p20_lite_0.1.img - initial release

Bootloader says:
PHONE Unlocked
FRP Lock
I get writing to ramdisk error:
sending 'recovery_ramdisk' (24952 KB)...
OKAY [ 0.624s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.640
Update: nevermind, forgot to enable oem unlock to remove FRP. (I will leave the original message for other users)
Update 2: Works.
- Data decryption and backup were successful
- MTP works
- Zip flashing successful
- OTG connection works

fabio87 said:
Bootloader says:
PHONE Unlocked
FRP Lock
I get writing to ramdisk error:
sending 'recovery_ramdisk' (24952 KB)...
OKAY [ 0.624s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.640
Update: nevermind, forgot to enable oem unlock to remove FRP. (I will leave the original message for other users)
Update 2: Works. Data decryption and backup were successful. MTP works. Zip flashing successful.
Click to expand...
Click to collapse
Thank you for testing Fabio, i will edit the OP in this case. If you can, please also test OTG connection.

Pretoriano80 said:
Thank you for testing Fabio, i will edit the OP in this case. If you can, please also test OTG connection.
Click to expand...
Click to collapse
OTG Works. I updated my test reply.
Needless to say. THANK YOU!

fabio87 said:
OTG Works. I updated my test reply.
Needless to say. THANK YOU!
Click to expand...
Click to collapse
No problem.Can you get me the recovery.log and dmesg ,please?

@Pretoriano80
YOU ARE THE BEST !!!
my test
flash twrp
twrp/Backup data + system to internal storage : work
twrp/Backup data + system to external_sd : work
reboot to system
install test-app
reboot to twrp
twrp/Restore data + system : work
reboot to system
phone work and test-app is out
NOW is this phone a very good phone
NOW can i test other rom and "short restore" (if i use new phone i need minimum 1h for settings and app install, now twrp/restore = 2..3 minutes)
Many thank's for your good work (and your helping friends) !!!
Excuse me, with my joy i forgot recovery.log View attachment recovery.log

Thanks for testing! A recovery.log would also be useful.
Beware that this recovery might not work with custom roms. However, it can still be used to restore your data after testing custom roms, in case you want to go back to EMUI.

Pretoriano80 said:
No problem.Can you get me the recovery.log and dmesg ,please?
Click to expand...
Click to collapse
Here are the logs.
I installed a zip file containing a titanium backup app+data to test it out and it jammed and reverted back to stock recovery.
I flashed the recovery again and works, but I'm not sure what happened.

fabio87 said:
Here are the logs.
I installed a zip file containing a titanium backup app+data to test it out and it jammed and reverted back to stock recovery.
I flashed the recovery again and works, but I'm not sure what happened.
Click to expand...
Click to collapse
Thanks, logs look fine.
Try to flash that titanium backup and then reboot to recovery instead of android system.

@Pretoriano80
excuse me : if you need - in post #6 recovery.log appended
excuse my bad english inside PM. shame on me
i hope this is what you need (twrp setting to english)
View attachment dmesg.txt.gz View attachment recovery.log

Thanks a lot for this !
If i wanna go back to stock recovery, should i flash "recovery_ramdis.img" ? (no typo error this is the dump i get from the stock firmware)

mchtt said:
Thanks a lot for this !
If i wanna go back to stock recovery, should i flash "recovery_ramdis.img" ? (no typo error this is the dump i get from the stock firmware)
Click to expand...
Click to collapse
Yes, just flash that with fastboot and your stock recovery will be back.

Thx a lot, it's time to flash !
edit: fastboot reboot not working on my device, but a Power+Volume Up did the job.
Is the "Failed to unmount /system" normal ?
---------- Post added at 02:58 PM ---------- Previous post was at 02:30 PM ----------
Also got a "Unable to locate /boot partition for backup calculations"
View attachment recovery.log.zip

Pretoriano80 said:
Thanks, logs look fine.
Try to flash that titanium backup and then reboot to recovery instead of android system.
Click to expand...
Click to collapse
It wouldn't let me. TWRP just gets stuck at 'Done!' and nothing happens, when I hard reset it just goes back into system and when I reboot into recovery it is back to stock.
Anyway, it's really not a big deal at the moment, I was just pointing out some sort of bug.

After a twrp backup, i flashed a rom, then went back to twrp to do a wipe but it is stuck at the TWRP logo.

mchtt said:
After a twrp backup, i flashed a rom, then went back to twrp to do a wipe but it is stuck at the TWRP logo.
Click to expand...
Click to collapse
Have you tried to flash twrp again?

yes, same. i cannot boot into twrp anymore...

fabio87 said:
It wouldn't let me. TWRP just gets stuck at 'Done!' and nothing happens, when I hard reset it just goes back into system and when I reboot into recovery it is back to stock.
Anyway, it's really not a big deal at the moment, I was just pointing out some sort of bug.
Click to expand...
Click to collapse
Well, it might be an issue with the updater script that Titanium Backup is using.
mchtt said:
After a twrp backup, i flashed a rom, then went back to twrp to do a wipe but it is stuck at the TWRP logo.
Click to expand...
Click to collapse
Custom Roms are not supported for now, some may work, others not.

Yes i reverted to stock rom and now TWRP boots again....
I tried a treble rom by the way.
---------- Post added at 04:11 PM ---------- Previous post was at 04:05 PM ----------
But i can confirm that backup / restore functions are working

mchtt said:
Yes i reverted to stock rom and now TWRP boots again....
I tried a treble rom by the way.
---------- Post added at 04:11 PM ---------- Previous post was at 04:05 PM ----------
But i can confirm that backup / restore functions are working
Click to expand...
Click to collapse
Yes, but it would be great to have the same functionality with custom roms, too.
If anyone is testing custom roms, please provide me the /system/build.prop and /vendor/build.prop.

Need help for soft brick (eRecovery not working)

What I have done
I unlocked the bootloader of my Honor 6x using the testpoint method
I installed TWRP and Magisk
I decided that I was not satisfied with the stock OS and wanted to install a custom ROM
I forgot to make a backup using TWRP before flashing
I tried to flash LineageOS but it did not work and caused a bootloop (the boot animation shows for about 5 minutes and then reboots)
Using Huawei eRecovery to restore the device was not possible, and it returns the message of "Getting package info failed".
This is likely due to the website "http://update.hicloud.com/" being down
Cannot download any stock ROMs as the downloads I found are all from "http://update.hicloud.com/"
This is the only thread I found about the website being down: link
After some digging I found an old ROM (EMUI 4) that I can use, and flashed it using TWRP
The system booted up just fine after that, but the system looked really old and I wanted to update it
I found an update file and tried to install it using the dload method, which installed through the Huawei recovery just fine.
The phone rebooted and now bootloops to the Huawei eRecovery everytime.
I thought of flashing TWRP again so that maybe I can flash the old rom again, but it does not work and returns the following errors.
command: fastboot flash recovery twrp.img
error: Writing 'recovery' FAILED (remote: 'image verification error')
fastboot flash recovery_ramdisk twrp.img
error: Writing 'recovery_ramdisk' FAILED (remote: 'partition length get error')
Questions
What can I do in this situation with only have access to fastboot commands and the Huawei eRecovery?
Should I just wait for the update website to come back up so that the eRecovery will work and I can install the latest OS from there? Will that ever happen?

hey i can help ! which version of twrp are you trying to flash ?

lmaohelp said:
What I have done
I unlocked the bootloader of my Honor 6x using the testpoint method
I installed TWRP and Magisk
I decided that I was not satisfied with the stock OS and wanted to install a custom ROM
I forgot to make a backup using TWRP before flashing
I tried to flash LineageOS but it did not work and caused a bootloop (the boot animation shows for about 5 minutes and then reboots)
Using Huawei eRecovery to restore the device was not possible, and it returns the message of "Getting package info failed".
This is likely due to the website "http://update.hicloud.com/" being down
Cannot download any stock ROMs as the downloads I found are all from "http://update.hicloud.com/"
This is the only thread I found about the website being down: link
After some digging I found an old ROM (EMUI 4) that I can use, and flashed it using TWRP
The system booted up just fine after that, but the system looked really old and I wanted to update it
I found an update file and tried to install it using the dload method, which installed through the Huawei recovery just fine.
The phone rebooted and now bootloops to the Huawei eRecovery everytime.
I thought of flashing TWRP again so that maybe I can flash the old rom again, but it does not work and returns the following errors.
command: fastboot flash recovery twrp.img
error: Writing 'recovery' FAILED (remote: 'image verification error')
fastboot flash recovery_ramdisk twrp.img
error: Writing 'recovery_ramdisk' FAILED (remote: 'partition length get error')
Questions
What can I do in this situation with only have access to fastboot commands and the Huawei eRecovery?
Should I just wait for the update website to come back up so that the eRecovery will work and I can install the latest OS from there? Will that ever happen?
Click to expand...
Click to collapse
The update website isn't going to come back anytime soon. But if you just don't mind opening your device again(you need to access the test point), there's a fix. this method doesn't just need anything. even if your device is hard bricked, it can get you back running. This was described in a youtube video with working links based on a forum on xda.
link : click here
I got a similar problem recently but I flashed update.zip of emui 8 - > Bootlooped - > factory reset with twrp - > successfully booted but doesn't get past the setup screen. Fix : flashed a gsi treble image(based on android 10) - > working perfect except for camera and volte.

Venkata Lochan Nune said:
The update website isn't going to come back anytime soon. But if you just don't mind opening your device again(you need to access the test point), there's a fix. this method doesn't just need anything. even if your device is hard bricked, it can get you back running. This was described in a youtube video with working links based on a forum on xda.
link : click here
I got a similar problem recently but I flashed update.zip of emui 8 - > Bootlooped - > factory reset with twrp - > successfully booted but doesn't get past the setup screen. Fix : flashed a gsi treble image(based on android 10) - > working perfect except for camera and volte.
Click to expand...
Click to collapse
The update website is there. Its https://www.firmfinder.ml/ . No need to install any gsi

King_of_Android said:
The update website is there. Its https://www.firmfinder.ml/ . No need to install any gsi
Click to expand...
Click to collapse
My bad , I thought the update website to be huawei's official one(something like update.hicloud and all isn't it?). Well, thanks for the information but I still prefer gsi. It's buttery smooth .
And one more thing, if you follow the youtube video I mentioned, you don't need any gsi. You can get your device back on stock EMUI 5.

King_of_Android said:
hey i can help ! which version of twrp are you trying to flash ?
Click to expand...
Click to collapse
Hey I have a doubt... Will the recoveries we find in twrp official website / app work on EMUI 8? I wanted to try them but I'm afraid I might brick my device again. Getting it back is a hectic thing and I already had to face it thrice. LOL .

King_of_Android said:
The update website is there. Its https://www.firmfinder.ml/ . No need to install any gsi
Click to expand...
Click to collapse
Hi, thanks for trying to help! I am using the website to install the firmware but I am having problems with it currently, and I made a post about it, if you could help me with that it would be greatly appreciated.

lmaohelp said:
Hi, thanks for trying to help! I am using the website to install the firmware but I am having problems with it currently, and I made a post about it, if you could help me with that it would be greatly appreciated.
Click to expand...
Click to collapse
I tried using that website but I wasn't able to figure out how to use it. So just left it. Did you try the method which I described earlier?

Venkata Lochan Nune said:
I tried using that website but I wasn't able to figure out how to use it. So just left it. Did you try the method which I described earlier?
Click to expand...
Click to collapse
I haven't tried to use the method you posted yet, because it is a bit more lengthy and complicated. If the method I was using does not work I'll use the video and let you know how it goes. Thanks!

lmaohelp said:
I haven't tried to use the method you posted yet, because it is a bit more lengthy and complicated. If the method I was using does not work I'll use the video and let you know how it goes. Thanks!
Click to expand...
Click to collapse
Well, just clear these things:
Is your bootloader still unlocked?
Did you try using another recovery image instead of the one you are getting error for?

Venkata Lochan Nune said:
Well, just clear these things:
Is your bootloader still unlocked?
Did you try using another recovery image instead of the one you are getting error for?
Click to expand...
Click to collapse
My bootloader is still unlocked, yes. However, I did not try to flash another recovery image, as I was not sure where I could find one that worked. I forgot which image I used at first but it had worked the first time, so that was why I did not bother finding a different recovery. Do you have a suggestion for a recovery to install?

lmaohelp said:
My bootloader is still unlocked, yes. However, I did not try to flash another recovery image, as I was not sure where I could find one that worked. I forgot which image I used at first but it had worked the first time, so that was why I did not bother finding a different recovery. Do you have a suggestion for a recovery to install?
Click to expand...
Click to collapse
I'm attaching one that works with emui 8 try using it (Remember you have to flash it to recovery_ramdisk).

Well after reading your post 1 again, I think there's no such partition as recovery_ramdisk(because it will be there only from android 8). So find a recovery in google which works on hi6250 devices with emui 4. That should work. Update me with the result

lmaohelp said:
What I have done
I unlocked the bootloader of my Honor 6x using the testpoint method
I installed TWRP and Magisk
I decided that I was not satisfied with the stock OS and wanted to install a custom ROM
I forgot to make a backup using TWRP before flashing
I tried to flash LineageOS but it did not work and caused a bootloop (the boot animation shows for about 5 minutes and then reboots)
Using Huawei eRecovery to restore the device was not possible, and it returns the message of "Getting package info failed".
This is likely due to the website "http://update.hicloud.com/" being down
Cannot download any stock ROMs as the downloads I found are all from "http://update.hicloud.com/"
This is the only thread I found about the website being down: link
After some digging I found an old ROM (EMUI 4) that I can use, and flashed it using TWRP
The system booted up just fine after that, but the system looked really old and I wanted to update it
I found an update file and tried to install it using the dload method, which installed through the Huawei recovery just fine.
The phone rebooted and now bootloops to the Huawei eRecovery everytime.
I thought of flashing TWRP again so that maybe I can flash the old rom again, but it does not work and returns the following errors.
command: fastboot flash recovery twrp.img
error: Writing 'recovery' FAILED (remote: 'image verification error')
fastboot flash recovery_ramdisk twrp.img
error: Writing 'recovery_ramdisk' FAILED (remote: 'partition length get error')
Questions
What can I do in this situation with only have access to fastboot commands and the Huawei eRecovery?
Should I just wait for the update website to come back up so that the eRecovery will work and I can install the latest OS from there? Will that ever happen?
Click to expand...
Click to collapse
hi
can you boot into recovery (must be TWRP) at the moment? then try the following...click the link in post 3 and in youtube expand the info...then click the unbrick link and download the oeminfo.
on the phone (TWRP) recovery flash the oeminfo in to the oeminfo partion...reboot to erecovery and then download the stock rom....after this reboot into system
i had unbrick some huawei devices with this method and it helps e´very time
solong
speedson

speedson said:
hi
can you boot into recovery (must be TWRP) at the moment? then try the following...click the link in post 3 and in youtube expand the info...then click the unbrick link and download the oeminfo.
on the phone (TWRP) recovery flash the oeminfo in to the oeminfo partion...reboot to erecovery and then download the stock rom....after this reboot into system
i had unbrick some huawei devices with this method and it helps e´very time
solong
speedson
Click to expand...
Click to collapse
His problem us with twrp.
He can only access fastboot but isn't able to flash twrp...

Venkata Lochan Nune said:
Well after reading your post 1 again, I think there's no such partition as recovery_ramdisk(because it will be there only from android 8). So find a recovery in google which works on hi6250 devices with emui 4. That should work. Update me with the result
Click to expand...
Click to collapse
So I have tried many different recoveries, such as ones for EMUI 4 and 5 and flashing directly to recovery, which gave me an error "image verification failed", and flashing an EMUI 8 to ramdisk would give me the same error as before. I think the partitions on this device is really messed up lol. Also, when I type fastboot reboot recovery, it would just get stuck at the loading screen, so does that mean there is no working recovery installed?

lmaohelp said:
So I have tried many different recoveries, such as ones for EMUI 4 and 5 and flashing directly to recovery, which gave me an error "image verification failed", and flashing an EMUI 8 to ramdisk would give me the same error as before. I think the partitions on this device is really messed up lol. Also, when I type fastboot reboot recovery, it would just get stuck at the loading screen, so does that mean there is no working recovery installed?
Click to expand...
Click to collapse
Maybe yes. Did you try directly booting the image without flashing?
Code:
fastboot boot recovery.img

Venkata Lochan Nune said:
Maybe yes. Did you try directly booting the image without flashing?
Code:
fastboot boot recovery.img
Click to expand...
Click to collapse
Yup, I tried that as well, and it told me "invalid command"

lmaohelp said:
Yup, I tried that as well, and it told me "invalid command"
Click to expand...
Click to collapse
Well as you said, you partitions must have been really messed up. I have no other ideas except the test point method.
Are you trying anything else?

Ok we have some option that could help you...
Im read in the 4PDA (the russian XDA xD) forum that it should be possible to flash the oeminfo by fastboot command. So just download the HWOTA_BLN_Eng and expand it. Then go to 7 or 8 Folder and there you go to oeminfo folder. There you choose the right one for your Device and local area...for example BLN-L21 (Device) C432 (European Area)
Extract the file to your desktop and rename it to BLN-L21C432.img
--->be sure that you have the right Device driver installed and the right ADB driver for your device to<---
ok now Copy and Paste the BLN-L21C432.img to ADB folder and start command with admin rights
start the phone into fastboot mode
--->bootloader must be unlocked<---
in the command
fastboot flash oeminfo BLN-L21C432.img
wait for the result and it can not hurt to pray a bit in this moment...hihi
if this have success...you type in command
fastboot reboot
wait to the screen you can press 3 seconds Vol+ to go into erecovery....connect to wlan and it should work step by step like it should.
after download and recover the stock rom reboot and go again to erecover by press Vol+ for 3 seconds and now go to the second option...wipe data/factory reset and write yes+enter
in stock recovery wipe Data after that wipe Cache...reboot and wait that system boot the initial boot for first setup.
If this will not working...tell me what honor 6x you have and wich local area you are from and wich firmware you stock had before you doing wronng
good luck bro
solong
speedson

Getting root

Im on 11.02
if i boot a twrp via fastboot my phone hangs on fastboot and if i flash a patched bootfile the booting process does not end. It hangs on the bootanimation, though i can login te phone with adb shell and even get root. Im looking for a twrp that boots up in fastboot i guess. Anyone outhere that recognizes this and knows how to deal with this?

Zobat said:
Im on 11.02
if i boot a twrp via fastboot my phone hangs on fastboot and if i flash a patched bootfile the booting process does not end. It hangs on the bootanimation, though i can login te phone with adb shell and even get root. Im looking for a twrp that boots up in fastboot i guess. Anyone outhere that recognizes this and knows how to deal with this?
Click to expand...
Click to collapse
Hello, you should mention what TWRP exactly you're trying to boot

strongst said:
Hello, you should mention what TWRP exactly you're trying to boot
Click to expand...
Click to collapse
I'm away from my computer now but i tried 2
The latest 3.5 or something like that and 3.3 something
Is there a version recommended version?

Zobat said:
I'm away from my computer now but i tried 2
The latest 3.5 or something like that and 3.3 something
Is there a version recommended version?
Click to expand...
Click to collapse
I'm only aware of 3.4-10, maybe you have another one, please check the guide and the links to TWRP images which you have to boot: https://forum.xda-developers.com/t/...tloader-twrp-root-with-magisk-update.3954559/

strongst said:
I'm only aware of 3.4-10, maybe you have another one, please check the guide and the links to TWRP images which you have to boot: https://forum.xda-developers.com/t/...tloader-twrp-root-with-magisk-update.3954559/
Click to expand...
Click to collapse
Unfortunately the same result. If i boot this via fastboot my phone hangs on fastboot.

Zobat said:
Unfortunately the same result. If i boot this via fastboot my phone hangs on fastboot.
Click to expand...
Click to collapse
Which TWRP did you used in the past or is this the first time you want to install TWRP permanently?

strongst said:
Which TWRP did you used in the past or is this the first time you want to install TWRP permanently?
Click to expand...
Click to collapse
I upgraded to android 11. I lost twrp somewhere in the process. I miss the option to directly patch the running kernel/bootimage in magisk-manager. Maybe i should look for an older version of MagiskManager.

Zobat said:
I upgraded to android 11. I lost twrp somewhere in the process. I miss the option to directly patch the running kernel/bootimage in magisk-manager. Maybe i should look for an older version of MagiskManager.
Click to expand...
Click to collapse
Can you post the console output of your PC which shows the steps to boot the TWRP?
Which magisk version do you have in place?
Are you asked to enter a pin from the lockscreen security?

strongst said:
Can you post the console output of your PC which shows the steps to boot the TWRP?
Which magisk version do you have in place?
Are you asked to enter a pin from the lockscreen security?
Click to expand...
Click to collapse
downloading 'boot.img'...
OKAY [ 1.214s]
booting...
OKAY [ 0.123s]
finished. total time: 1.337s
Then it hangs in fastboot. I just removed the pinlock and flashed my magisk patched image again. I can login via adb and get root, but the setup does not finish.
I flash my unpatched boot.img again and all is well. No root off course.
Im using the latest magisk app: 22.1

Zobat said:
downloading 'boot.img'...
OKAY [ 1.214s]
booting...
OKAY [ 0.123s]
finished. total time: 1.337s
Then it hangs in fastboot. I just removed the pinlock and flashed my magisk patched image again. I can login via adb and get root, but the setup does not finish.
I flash my unpatched boot.img again and all is well. No root off course.
Im using the latest magisk app: 22.1
Click to expand...
Click to collapse
You used the command
Code:
fastboot boot twrp-3.4.0-10--guacamole-unified-Q-mauronofrio.img
?

strongst said:
You used the command
Code:
fastboot boot twrp-3.4.0-10--guacamole-unified-Q-mauronofrio.img
?
Click to expand...
Click to collapse
Code:
~/android$ fastboot boot twrp-3.4.0-10-guacamole-unified-Q-mauronofrio.img
downloading 'boot.img'...
OKAY [ 1.151s]
booting...
OKAY [ 0.123s]
finished. total time: 1.274s

I'm thinking about moving this discussion to: https://forum.xda-developers.com/t/...l-twrp-for-oneplus-7-7-pro-5g-stable.3932943/

Hey can someone share the Cons of root, because this is very first time when I will install Custom ROOM on my mobile phone, or another thing I wanna ask, is it compulsory to install custom ROOM after rooting my device, I just need root permission for some sort of APPS that needs root access. jbbattery spain

imranhashmi76 said:
Hey can someone share the Cons of root, because this is very first time when I will install Custom ROOM on my mobile phone, or another thing I wanna ask, is it compulsory to install custom ROOM after rooting my device, I just need root permission for some sort of APPS that needs root access.
Click to expand...
Click to collapse
Hey brp about the cons i don't have much idea but the second question, If you don't wanna install custom root then no problem you can still with your original Software, there is no any condition to install custom rom with root file.

Help With Lineage OS 18.1 Install -- stuck at first step(!)

Greetings,
Recently picked up this Pixel 3 and I like it hardware-wise but want to degoogle as much as I can (only want the bare minimum Play store to ensure I can use all my usual apps [nothing from Google - let me know if you need a list]).
Think that means I'll want to end up with Lineage OS 18.1 (Android 11?) + OpenGApps (Pico) + Magisk (for root?) does this seem correct?
Been reading a mishmash of this: https://forum.xda-developers.com/t/the-complete-pixel-3-how-to-guide-newbie-friendly.3922269/page-2 and other guides and I'm a bit confused.
I've rooted and imaged my previous Moto phone but it's been a while. From what I gather so far, the general plan for this Pixel is: oem unlock, usb debugging, unlock bootloader, boot recovery, install recovery, install lineage, install opengapps, install magisk, ????, profit.
However in the guide I linked, I see that the TWRP section is all red and strikethrough. And have read (perhaps old info?) that Android 10 and up TWRP doesn't work/support?
Yet every guide I've seen says to install TWRP and also the date on this OP is updated November 2020...? Plus, there are notes on the twrp page that just say mtp isn't working but otherwise that means it should work, right?: (https://twrp.me/google/googlepixel3.html)
I've unlocked the bootloader oem unlock, got the USB drivers and platform-tools installed (via most up-to-date Android Studio), see my device (Google Pixel 3) with adb devices, and can issue commands like adb reboot fastboot... I have everything this guide mentions ready to go, but I am stuck at temporarily booting recovery image:
Error output:
C:\Users\Nate\AppData\Local\Android\Sdk\platform-tools>fastboot boot twrp-3.3.0-0-blueline.img
Sending 'boot.img' (65536 KB) OKAY [ 0.232s]
Booting FAILED (remote: 'Unrecognized command boot')
fastboot: error: Command failed
C:\Users\Nate\AppData\Local\Android\Sdk\platform-tools>fastboot boot twrp-3.3.0-0-blueline.img
Sending 'boot.img' (65536 KB) OKAY [ 0.263s]
Booting FAILED (remote: 'Error verifying the received boot.img: Invalid Parameter')
fastboot: error: Command failed
The first command I realized failed because it was in 'fastbootd'... so I made sure to have it on the 'regular' fastboot, and get the second error. Invalid parameter... what's invalid?
This is what my screen looks like which makes me believe I've done right so far (attachments).
Feel incredibly humbled to be stuck at the first stage
Can anyone please tell me what I'm doing wrong or what I missed? Your assistance is much appreciated.
Thank you in advance.

TWRP has not worked on the Pixel 3 for a couple of years. I have not tried installing Lineage on my Pixel 3, but the process described at https://wiki.lineageos.org/devices/blueline/install should work. Basically use Lineage Recovery instead of TWRP.

dcarvil said:
TWRP has not worked on the Pixel 3 for a couple of years. I have not tried installing Lineage on my Pixel 3, but the process described at https://wiki.lineageos.org/devices/blueline/install should work. Basically use Lineage Recovery instead of TWRP.
Click to expand...
Click to collapse
Ok, thank you for the reply. I will go ahead and use the Lineage Built in recovery.
I wanted to use TWRP since before I actually start changing things, wanted to do a full and complete backup, basically a complete image of all files and partitions as is before I start changing things. I'll check the lineage wiki, but to your knowledge can you do a complete backup from lineage recovery?

nasch007 said:
Ok, thank you for the reply. I will go ahead and use the Lineage Built in recovery.
I wanted to use TWRP since before I actually start changing things, wanted to do a full and complete backup, basically a complete image of all files and partitions as is before I start changing things. I'll check the lineage wiki, but to your knowledge can you do a complete backup from lineage recovery?
Click to expand...
Click to collapse
Sorry, I have not used Lineage Recovery, so I don't know what backup capability it has.

Lineage recovery is just a modified stock recovery, it has no backup ability, only what is in stock.

wangdaning said:
Lineage recovery is just a modified stock recovery, it has no backup ability, only what is in stock.
Click to expand...
Click to collapse
Roger that. Thanks to dcarvil's guidance (pointing me to the correct instructions) I was able to successfully install and root.
I have some follow up questions, probably best suited for another thread. But while I have your attention, could you tell me where to report bugs or get general usage support? There's a few things that I don't think are working the way they're supposed to or features that seem missing. If you don't know, I respect that and a mod can close this thread.
Thanks again!