Database Develop

Phone stuck on color lines at bootup

Hello i tried to flash new roms but i think my phone is bricked now. i have tried to unbrick. Every time i flash a rom it says done after 1 second. So i know its not flashing properly. before i go buy a new phone can someone help me out please.
Thank you so much

lonster27 said:
Hello i tried to flash new roms but i think my phone is bricked now. i have tried to unbrick. Every time i flash a rom it says done after 1 second. So i know its not flashing properly. before i go buy a new phone can someone help me out please.
Thank you so much
Click to expand...
Click to collapse
Tell us what exactly you did and what exactly fastboot is outputting

Benjamin_L said:
Tell us what exactly you did and what exactly fastboot is outputting
Click to expand...
Click to collapse
i unlocked it which worked and i could still get back into the phone. Then i installed twrp recovery on the phone and then installed from there DM verity disabler. after that is was bricked. now i can not even get back into twrp i just freezes. i am still able to get into fastboot that is all.

lonster27 said:
i unlocked it which worked and i could still get back into the phone. Then i installed twrp recovery on the phone and then installed from there DM verity disabler. after that is was bricked. now i can not even get back into twrp i just freezes. i am still able to get into fastboot that is all.
Click to expand...
Click to collapse
Then you can still flash the fastboot roms. Guides are found here. Or use the included script.
Why would I want to disable dm verity after all?

Benjamin_L said:
Then you can still flash the fastboot roms. Guides are found here. Or use the included script.
Why would I want to disable dm verity after all?
Click to expand...
Click to collapse
thanks can you please maybe provide a link for me please for both methods.

i got the same result when i rebooted the phone after trying to clear the cache in chrome browser ...

{SOLVED}PLEASE READ Bricked My phone. A help please **URGENT**

**URGENT** i have my p20 pro 6/128 with 9.0 last version ROOTED somehow i found a article.. the root was success. Tried to flash official twrp with twrp app and then everything was like HELL.
If i let my phone boot says error! func no: 10 boot image. error no :2 load failed. i faced something simillar when trying to get into recovery sometimes.
I can get into erecovery cant format or download official firmware. I can get into fastboot, download mode. I am gonna tell you everything . every program i tried AND FAILED!
TRIED: multi tool for huawei ( i download a version i think its 165 something when i press flash selected the program closed)
TRIED: to FLASH like 10 times ramdisks, recoverys, CANT FIND BOOT.IMG.
TRIED: Re-flash 9.0 says missing zip files THATS IMPOSIMPLE NOTHING IS MISSING I AM SURE
TRIED: a guide that said to download firmware and i would find a folder named DLOAD. i did everything. COULDNT FLASH SOMETHING ON DOWNLOAD SAYS ERROR
TRIED: ALMOST EVERYTHING
PLEASE HELP ME, HOW TO FIX IT? its very important for me and for everyone who is facing the same problem
Phone infos From Multi tool program http://prntscr.com/min398
and the firmwares i tried 1) http://prntscr.com/min3tn
2) http://prntscr.com/min40j
SEE SOME POSTS BELLOW TO SEE HOW I FIXED IT SUCCESS AFTER MANY ERRORS

1 found this post, and flashed all of them BUT there is not ramdisk on the files. i looked on two different firmwares which should i flash over ramdisk which doesnt exist?
first i run the command fastboot flash kernel kernel.img and i could boot into TWRP for first time. now i cant.
there are not errors for now. only if i boot my phone says phone keeping booting.
when i got to twrp and tried to reboot into system said there is no OS.
How and which os i should flash? since Multi tool program kicks me
HELP
https://forum.xda-developers.com/honor-9/help/help-softbricked-h9-oreo-t3750282

So you're typing a little erratic.
Can you get to eRecovery? This is your best option..
If not then you'll need to reflash all the parts of the OS back to the phone manually..
Beyond that you'll need a recovery method, not sure if it's a device of a program but it can usually help, depends on what is borked.

dladz said:
So you're typing a little erratic.
Can you get to eRecovery? This is your best option..
If not then you'll need to reflash all the parts of the OS back to the phone manually..
Beyond that you'll need a recovery method, not sure if it's a device of a program but it can usually help, depends on what is borked.
Click to expand...
Click to collapse
i can get into erecovery i cannot download the official and flash it throught there says error.. what else i can do
I cant understand what yyou saying here Beyond that you'll need a recovery method, not sure if it's a device of a program but it can usually help, depends on what is borked.
I get into Erecovery if i press download latest version and recovery after some times when i put the wifi pass says error. Error i got also on HIsUite when i tried to format from there and download the latest versio. So we go manually but HOW? i tried almost everything

i tried this https://forum.xda-developers.com/huawei-p20/how-to/how-to-how-to-unbrick-clt-l29c432-t3878714
success all command went trhough the phone
the problem is i cannot flash twrp
my phone has unlocked bl

well i did a lot of search if you ask me i download 5-7 different programs that can flash stock firmware. ONE seems to be legit for 9.0 RE-flash 9.0 which has commands on its script like this guy says and he helped me too
https://forum.xda-developers.com/huawei-p20/how-to/how-to-how-to-unbrick-clt-l29c432-t3878714
also if someone cant boot into twrp after the frist steps and see the erecovery just format everything from erecovery and then it will boot to twrp.
also now says installing update.
i hope imeis serial numbers etc wont lost..
Thats the script i found i dont remeber where
http://prntscr.com/mitvum
but i can upload somewhere the files
if you run FLASH.bat and says MISSING ZIPS then remove the update."zip" {ZIP PREFIX FROM THE NAME OF THE FILES ONLY} and run again the bat
the procedure may take 10-30 mins

What about the otg method?
Also I would never use a tool like this.

StonebridgeGr said:
**URGENT** i have my p20 pro 6/128 with 9.0 last version ROOTED somehow i found a article.. the root was success. Tried to flash official twrp with twrp app and then everything was like HELL.
If i let my phone boot says error! func no: 10 boot image. error no :2 load failed. i faced something simillar when trying to get into recovery sometimes.
I can get into erecovery cant format or download official firmware. I can get into fastboot, download mode. I am gonna tell you everything . every program i tried AND FAILED!
TRIED: multi tool for huawei ( i download a version i think its 165 something when i press flash selected the program closed)
TRIED: to FLASH like 10 times ramdisks, recoverys, CANT FIND BOOT.IMG.
TRIED: Re-flash 9.0 says missing zip files THATS IMPOSIMPLE NOTHING IS MISSING I AM SURE
TRIED: a guide that said to download firmware and i would find a folder named DLOAD. i did everything. COULDNT FLASH SOMETHING ON DOWNLOAD SAYS ERROR
TRIED: ALMOST EVERYTHING
PLEASE HELP ME, HOW TO FIX IT? its very important for me and for everyone who is facing the same problem
Phone infos From Multi tool program http://prntscr.com/min398
and the firmwares i tried 1) http://prntscr.com/min3tn
2) http://prntscr.com/min40j
SEE SOME POSTS BELLOW TO SEE HOW I FIXED IT SUCCESS AFTER MANY ERRORS
Click to expand...
Click to collapse
dladz said:
What about the otg method?
Also I would never use a tool like this.
Click to expand...
Click to collapse
like i said in the first post the otg method with the dload folder failed.
Why you wouldnt try it?

StonebridgeGr said:
like i said in the first post the otg method with the dload folder failed.
Why you wouldnt try it?
Click to expand...
Click to collapse
Because I've got no need to mate, manual is always safer.
Have you asked in the thread where you got the tool?
I'm not sure what else to suggest pal

dladz said:
Because I've got no need to mate, manual is always safer.
Have you asked in the thread where you got the tool?
I'm not sure what else to suggest pal
Click to expand...
Click to collapse
now everything is fine but i cant root..

StonebridgeGr said:
now everything is fine but i cant root..
Click to expand...
Click to collapse
Everything is fine? What did you do?
With root Judy follow the instructions that have worked for other people. Don't rush things.

dladz said:
Everything is fine? What did you do?
With root Judy follow the instructions that have worked for other people. Don't rush things.
Click to expand...
Click to collapse
i post i early post a link that helped me a little bit i think i edited the .bat script
also i made a video and post about rooting and everything is fine.
the problem is you can have twrp and magisk root both:/
either you have root and not twrp or either you have twrp and not root

Mi 8 soft brick

Hi guys
Sorry for my bad English
My device was running Android 10
miui 11
After I accidentally used an application to raise the screen frequency to 84Hz
The devics did a reboot and then stopped on the fastboot logo
I tried to enter recovery mode but was back to fastboot mode
I tried to flash twrp via adb and fastboot but the method did not work and the device returned to fastboot mode
Finally I downloaded the ROM file global Version Android 9
miui 11 and when i flashed the system via "xiaomi flash tool " the operation was successful until it reached the end of the process it showed me an error and the flash failed
I restarted the process and noticed that the flashing process gives me the error when the download arrives at "flashing boot"
I searched a lot for the version of Android 10 miui 11 but I did not find
What is the problem!
Can anyone explain what the problem is?
Thank you very much
Edit : solved With the help of my friend and brother @tsongming thanks bro

You likely damaged the phone, myself and others have posted numerous warning about flashing mods to increase the refresh rate.
I would recommend trying the Flashall.bat method.
Follow my instructions here : https://forum.xda-developers.com/showpost.php?p=80825243&postcount=2

tsongming said:
You likely damaged the phone, myself and others have posted numerous warning about flashing mods to increase the refresh rate.
I would recommend trying the Flashall.bat method.
Follow my instructions here : https://forum.xda-developers.com/showpost.php?p=80825243&postcount=2
Click to expand...
Click to collapse
When i flash device with edl mod in xiaomi mi tool i got these error
What i can due

ahmadbasher said:
When i flash device with edl mod in xiaomi mi tool i got these error
What i can due
Click to expand...
Click to collapse
See this thread : https://c.mi.com/thread-2121755-1-0.html
Also, I read about some people getting past these recent issues by using a USB hub extender. These decrease the amount of power to the port which may be causing a conflict. Try other ports and only use a usb 2 port. Further, I would recommend temporarily disabling firewall and antivirus if all else fails. Worst case use another computer.
If this helps come back and let us know what finally resolved it.

tsongming said:
See this thread : https://c.mi.com/thread-2121755-1-0.html
Also, I read about some people getting past these recent issues by using a USB hub extender. These decrease the amount of power to the port which may be causing a conflict. Try other ports and only use a usb 2 port. Further, I would recommend temporarily disabling firewall and antivirus if all else fails. Worst case use another computer.
If this helps come back and let us know what finally resolved it.
Click to expand...
Click to collapse
I solved and my device life agin
I flash these rom http://bigota.d.miui.com/V9.5.11.0....EACNFA_20180703.0000.00_8.1_cn_64c55c8438.tgz
With mi flash tool older version (2016)
In fastboot mode
But now i need back to global rom and after i flash latest global rom in fastboot the device bricking again
And stay in fastboot
What is the problem

ahmadbasher said:
I solved and my device life agin
I flash these rom http://bigota.d.miui.com/V9.5.11.0....EACNFA_20180703.0000.00_8.1_cn_64c55c8438.tgz
With mi flash tool older version (2016)
In fastboot mode
But now i need back to global rom and after i flash latest global rom in fastboot the device bricking again
And stay in fastboot
What is the problem
Click to expand...
Click to collapse
You still have encryption on your device, use the tool all in one and install TWRP ( You may need to use a different/maybe older computer, I think possibly windows 10 is part of the issue. ( Because I have had this exact issue that you are having)
Install the tool, and update ADB but not the tool itself, there will be a popup, asking to update. ignore it or the update will be flagged a sbeinga virus ( Actually a Windows issue) However, yes the program is unsigned.
Use all in One tool to remove encryption from device and flash TWRP
Boot to recovery, immediately flash root, Flash Su if you must.
Reboot to recovery, then flash a recovery rom. the boot to system , may take up to 10 minutes.
use ports from the back of the PC and you may need to use a usb hub.

tsongming said:
You still have encryption on your device, use the tool all in one and install TWRP ( You may need to use a different/maybe older computer, I think possibly windows 10 is part of the issue. ( Because I have had this exact issue that you are having)
Install the tool, and update ADB but not the tool itself, there will be a popup, asking to update. ignore it or the update will be flagged a sbeinga virus ( Actually a Windows issue) However, yes the program is unsigned.
Use all in One tool to remove encryption from device and flash TWRP
Boot to recovery, immediately flash root, Flash Su if you must.
Reboot to recovery, then flash a recovery rom. the boot to system , may take up to 10 minutes.
use ports from the back of the PC and you may need to use a usb hub.
Click to expand...
Click to collapse
thanks for replay bro i will tri it

tsongming said:
You still have encryption on your device, use the tool all in one and install TWRP ( You may need to use a different/maybe older computer, I think possibly windows 10 is part of the issue. ( Because I have had this exact issue that you are having)
Install the tool, and update ADB but not the tool itself, there will be a popup, asking to update. ignore it or the update will be flagged a sbeinga virus ( Actually a Windows issue) However, yes the program is unsigned.
Use all in One tool to remove encryption from device and flash TWRP
Boot to recovery, immediately flash root, Flash Su if you must.
Reboot to recovery, then flash a recovery rom. the boot to system , may take up to 10 minutes.
use ports from the back of the PC and you may need to use a usb hub.
Click to expand...
Click to collapse
I tri it and no change
Again reboot to fastboot

ahmadbasher said:
I tri it and no change
Again reboot to fastboot
Click to expand...
Click to collapse
While its possible that you have a hardware issue. Unless the phone has been exposed to moisture, or exposed to a great deal of force I doubt that you have a hardware problem. Again, I too have had a similar issue, it's just took a while to finally get it working, in my case my computer was part of the problem, since you have fastboot the number one goal at the moment should be with getting TWRP recovery installed, and then root.
Did you happen to make any TWRP backups?
Hopefully so, specifically if you have a TWRP backup that includes the persist image files, you need to try flashing those to the persist partition. If you can successfully restore the persist image then try the flashall.bat method again.
Another option is to use QPST, but try the above first.
Edit
Finally, After re-reading you initial post. I had forgotten that you attempted to improve the refresh rate of the display. If all you can get is fastboot after following all of the steps that I have mentioned than I am certain that you have a burned chip. Ignore the people who claim that you can't fry the chip they have no idea what they are talking about. The chip can absolutely be fried. It's still worth trying a few more times, you could have just simply corrupted partition images. When you flash the stock rom, or even when using the flashall.bat method not every partition is over written.
@ahmadbasher
When you flashed the file to increase the refresh rate you likely overwrote a partition called DTBO, See if you can flash a Mi8 DTBO image to the DTBO partition. If you have the full recovery backup, you can extract the file from there. i need to research exactly how that file works and I will try to help you will getting the image if you don't have it in a backup.

tsongming said:
While its possible that you have a hardware issue. Unless the phone has been exposed to moisture, or exposed to a great deal of force I doubt that you have a hardware problem. Again, I too have had a similar issue, it's just took a while to finally get it working, in my case my computer was part of the problem, since you have fastboot the number one goal at the moment should be with getting TWRP recovery installed, and then root.
Did you happen to make any TWRP backups?
Hopefully so, specifically if you have a TWRP backup that includes the persist image files, you need to try flashing those to the persist partition. If you can successfully restore the persist image then try the flashall.bat method again.
Another option is to use QPST, but try the above first.
Edit
Finally, After re-reading you initial post. I had forgotten that you attempted to improve the refresh rate of the display. If all you can get is fastboot after following all of the steps that I have mentioned than I am certain that you have a burned chip. Ignore the people who claim that you can't fry the chip they have no idea what they are talking about. The chip can absolutely be fried. It's still worth trying a few more times, you could have just simply corrupted partition images. When you flash the stock rom, or even when using the flashall.bat method not every partition is over written.
@ahmadbasher
When you flashed the file to increase the refresh rate you likely overwrote a partition called DTBO, See if you can flash a Mi8 DTBO image to the DTBO partition. If you have the full recovery backup, you can extract the file from there. i need to research exactly how that file works and I will try to help you will getting the image if you don't have it in a backup.
Click to expand...
Click to collapse
All thanks to you my friend, I do not know how I can give all thanks and gratitude to you for helping me ? But my friend unfortunately I do not have a backup of it Will wait for you
Thanks again

Is it possible that this is part of the problem..!
I can't check it
@tsongming

ahmadbasher said:
All thanks to you my friend, I do not know how I can give all thanks and gratitude to you for helping me But my friend unfortunately I do not have a backup of it Will wait for you
Thanks again
Click to expand...
Click to collapse
No problem, after reading some various post on GitHub, CNX, and source android.com, I found out that the Mi8 DTBO is in the boot. Image.
So you should be able to flash a boot image, root, and then recovery and hopefully boot to TWRP.
If that doesn't work then send me a pm and I will share my personal dtbo with you privately. But again you shouldn't need mine since dtbo is nothing more than the device tree and the boot image should suffice, because it has the exact same file.
ADB command : fastboot flash boot c:\boot.img

ahmadbasher said:
Is it possible that this is part of the problem..!
I can't check it
@tsongming
Click to expand...
Click to collapse
No that is just encryption, if the issue was related to encryption the flashall.bat method would have resolved it.
If you had a persist issue, you would see specific messages about not being able to mount the persist partition.

tsongming said:
No problem, after reading some various post on GitHub, CNX, and source android.com, I found out that the Mi8 DTBO is in the boot. Image.
So you should be able to flash a boot image, root, and then recovery and hopefully boot to TWRP.
If that doesn't work then send me a pm and I will share my personal dtbo with you privately. But again you shouldn't need mine since dtbo is nothing more than the device tree and the boot image should suffice, because it has the exact same file.
ADB command : fastboot flash boot c:\boot.img
Click to expand...
Click to collapse
Thank you I will now try to do this
Yesterday I flashed the pixle rom on the device and I took off the device without problems but every period of time the device was doing a reboot, I do not know if it is the problem of the ROM or there is something wrong with the device
I tell you so that you know only that
Now I will flash the latest version of miui 11 android 9 global version, and flash the boot.img and then Root and finally Recovery True ?

ahmadbasher said:
Thank you I will now try to do this
Yesterday I flashed the pixle rom on the device and I took off the device without problems but every period of time the device was doing a reboot, I do not know if it is the problem of the ROM or there is something wrong with the device
I tell you so that you know only that
Now I will flash the latest version of miui 11 android 9 global version, and flash the boot.img and then Root and finally Recovery True ?
Click to expand...
Click to collapse
Hey sorry for the delay in getting back to you, I sent you the link for the file via PM.
Also, I would strongly suggest using the stock miui initially. Just until you know it's resolved. Also while Miui is installed make a full TWRP backup and save it to your desktop. This way you always have a full backup to resolve any serious issues.
Then once you know everything is working as it should then go back to what you prefer..

For the record this issue was solved. Anyone reading this, make sure that you have a full working TWRP backup of your working device, it will save you a lot of headaches. The solution for the refresh rate is issue is restoring stock DTBO, and then flashing Miui Stock.

Bootloop Help!

Hello. I restored the stock images in magisk, I thought. I tried to do a complete uninstall but it failed. So I fastbooted the April update and it's stuck in a bootloop. I fear I might not have uninstalled magisk. Is there help for me? I tried flashing stock boot image, factory reset, flash all stock. I'm in a pickle. Somebody help me. Thanks

madmuthertrucker said:
Hello. I restored the stock images in magisk, I thought. I tried to do a complete uninstall but it failed. So I fastbooted the April update and it's stuck in a bootloop. I fear I might not have uninstalled magisk. Is there help for me? I tried flashing stock boot image, factory reset, flash all stock. I'm in a pickle. Somebody help me. Thanks
Click to expand...
Click to collapse
If you don't care about the data on the phone, just do a full flash with wipe.

madmuthertrucker said:
Hello. I restored the stock images in magisk, I thought. I tried to do a complete uninstall but it failed. So I fastbooted the April update and it's stuck in a bootloop. I fear I might not have uninstalled magisk. Is there help for me? I tried flashing stock boot image, factory reset, flash all stock. I'm in a pickle. Somebody help me. Thanks
Click to expand...
Click to collapse
Do #4 'keep data' to install April factory image. Do #9 to reroot. Use this guide.

I have tried reinstalling stock images with -w without -w it doesn't boot up even still. It boots to stock recovery. That has always worked for me before.
Edit: I got it! It boots into this weird Fastbootd mode it looks like recovery. I thought it wasn't taking the install. I was doing something else and it kept installing even though it was in a recovery looking mode. Shoot I erased all my data and probably didn't need to. Thanks for the help!

madmuthertrucker said:
I have tried reinstalling stock images with -w without -w it doesn't boot up even still. It boots to stock recovery. That has always worked for me before.
Click to expand...
Click to collapse
Did you try flashing the OTA with the recovery?
Are you using SDK Platform-tools r29.0.6?
---------- Post added at 08:46 PM ---------- Previous post was at 08:41 PM ----------
madmuthertrucker said:
I have tried reinstalling stock images with -w without -w it doesn't boot up even still. It boots to stock recovery. That has always worked for me before.
Edit: I got it! It boots into this weird Fastbootd mode it looks like recovery. I thought it wasn't taking the install. I was doing something else and it kept installing even though it was in a recovery looking mode. Shoot I erased all my data and probably didn't need to. Thanks for the help!
Click to expand...
Click to collapse
You're welcome, keep the guide it explains the fastbootd

Here it is. This threw me off. I just needed to be more patient.

Homeboy76 said:
You're welcome, keep the guide it explains the fastbootd
Click to expand...
Click to collapse
Thanks. I like the guide! I've been reading it. I wish I would have started there. Well now I have it to preview and fall back on.

madmuthertrucker said:
I have tried reinstalling stock images with -w without -w it doesn't boot up even still. It boots to stock recovery. That has always worked for me before.
Edit: I got it! It boots into this weird Fastbootd mode it looks like recovery. I thought it wasn't taking the install. I was doing something else and it kept installing even though it was in a recovery looking mode. Shoot I erased all my data and probably didn't need to. Thanks for the help!
Click to expand...
Click to collapse
A few months back the EXACT same thing happened to me.

bigmatt503 said:
A few months back the EXACT same thing happened to me.
Click to expand...
Click to collapse
Thanks that makes me feel better. It looked like recovery. I thought I messed up. It's nice to know I'm not alone.

guys help please i'm stuck and fastbootstd is not working for me i'm stuck with only fastboot and its using slot b to boot i can't even flash the stock firmware

medo411 said:
guys help please i'm stuck and fastbootstd is not working for me i'm stuck with only fastboot and its using slot b to boot i can't even flash the stock firmware
Click to expand...
Click to collapse
Did you uninstall modules? Restore stock boot.img? Fastboot devices gives you a proper response? Try everything they suggested that I do in previous posts. Change the cable you use. The guide from the previous post has a lot of good information. Tell us more.

bigmatt503 said:
A few months back the EXACT same thing happened to me.
Click to expand...
Click to collapse
Happened to me recently when I tried to flash dtbo.img back to stock
For some reason the fastbootd menu wouldn't let me use other fastboot commands, saying it wasn't unlocked, but going fastboot reboot bootloader then using fastboot commands worked successfully.
Very odd

madmuthertrucker said:
Did you uninstall modules? Restore stock boot.img? Fastboot devices gives you a proper response? Try everything they suggested that I do in previous posts. Change the cable you use. The guide from the previous post has a lot of good information. Tell us more.
Click to expand...
Click to collapse
Thanks a lot i 've tried restarting and changing the cables weird thing it worked previously it was saying remote partition not found bc boot slot is B

medo411 said:
Thanks a lot i 've tried restarting and changing the cables weird thing it worked previously it was saying remote partition not found bc boot slot is B
Click to expand...
Click to collapse
So did you get it?

Yes

I still refer to the guide every time there is an update.

medo411 said:
Yes
Click to expand...
Click to collapse
how'd ya fix the bootloop?

Rootmaster906 said:
how'd ya fix the bootloop?
Click to expand...
Click to collapse
If it is from a bad magisk module:
adb wait-for-device shell magisk --remove-modules

Tulsadiver said:
If it is from a bad magisk module:
adb wait-for-device shell magisk --remove-modules
Click to expand...
Click to collapse
Nope...mine is deeper than that

HELP! My device is corrupt

I tried re-rooting after updating and now it says Your device is corrupt. It cant be trusted and may not work properly.
It freezes on the Google if I continue. Not sure what happened.
Any remedy for this?

features99 said:
I tried re-rooting after updating and now it says Your device is corrupt. It cant be trusted and may not work properly.
It freezes on the Google if I continue. Not sure what happened.
Any remedy for this?
Click to expand...
Click to collapse
Need more specific details, like specific method of rooting, version of Magisk, updating to what?, etc...

Unfortunately you may have to flash the factory image and start all over again if no one else can help you with it. At least you have the option. Sucks when that happens.

I mean... the first message just sounds like the bootloader unlocked message which would show up even if you could fully boot in.
I wouldn't factory reset over just this though. Flash the factory image without the -w parameter in flash-all.bat

jljtgr said:
I mean... the first message just sounds like the bootloader unlocked message which would show up even if you could fully boot in.
I wouldn't factory reset over just this though. Flash the factory image without the -w parameter in flash-all.bat
Click to expand...
Click to collapse
I agree. Flashing the factory image without the -w would likely allow him to boot up again. But it would be helpful for that person to tell us exactly what they did so we can help them avoid it in the future, e.g. maybe they flashed the stable version of Magisk instead of Beta or Canary, or maybe they tried a direct install instead of patching the boot image, etc...

Ok guys sorry for not giving more details.
So I rooted awhile back when I got the phone, havent updated in a long time so I thought it was time.
I updated to Android 11 with the latest security updates and tried to re-root.
I updated Magisk to the latest version and patched the matching boot image, but Im pretty sure I used the stable version.
I should of researched it more as Im reading the beta method is the way to go.
I opened the command prompt with the following commands:
cd Downloads
cd fastboot
fastboot flash boot magisk_patched.img
fastboot reboot
Seems like everything went ok...
Then afterwards got the corrupted message and Google hang.
I can still load to fastboot but recovery or rescue doesnt work.
So where can I go from here? I only rooted a few phones in the past so Im still learning and reading lots of posts.
Also I didnt modify my own boot image, but one I downloaded from a matching build.
I really appreciate the help

features99 said:
Ok guys sorry for not giving more details.
So I rooted awhile back when I got the phone, havent updated in a long time so I thought it was time.
I updated to Android 11 with the latest security updates and tried to re-root.
I updated Magisk to the latest version and patched the matching boot image, but Im pretty sure I used the stable version.
I should of researched it more as Im reading the beta method is the way to go.
I opened the command prompt with the following commands:
cd Downloads
cd fastboot
fastboot flash boot magisk_patched.img
fastboot reboot
Seems like everything went ok...
Then afterwards got the corrupted message and Google hang.
I can still load to fastboot but recovery or rescue doesnt work.
So where can I go from here? I only rooted a few phones in the past so Im still learning and reading lots of posts.
I really appreciate the help
Click to expand...
Click to collapse
I would try fastboot flashing the stock boot image first.

If Magisk says you're on a version before 21.0, the patched image won't work for Android 11. Stable is currently 20.4 released in March.

Lughnasadh said:
I would try fastboot flashing the stock boot image first.
Click to expand...
Click to collapse
tried that..it didnt work

features99 said:
tried that..it didnt work
Click to expand...
Click to collapse
Then I would flash the December factory image using fastboot but with the -w removed from the flash-all.bat file so it won't erase your data.

Lughnasadh said:
Then I would flash the December factory image using fastboot but with the -w removed from the flash-all.bat file so it won't erase your data.
Click to expand...
Click to collapse
Yes that worked, didn't know about edited the .bat to remove the the -w and saving all data. Back in business for now...
Thank you all for expertise, much appreciated!

features99 said:
Yes that worked, didn't know about edited the .bat to remove the the -w and saving all data. Back in business for now...
Thank you all for expertise, much appreciated!
Click to expand...
Click to collapse
No problem. Glad you got it going. As I see you've already found out, Magisk Beta 21.1 is a good way to go. Canary as well but then you may run into problems in the future when Canary gets updated since those are "cutting edge" builds.