"Fingerprint Hardware Not Available" and missing WiFi - Google Pixel 2 XL Questions & Answers

Yesterday I updated my Magisk to 15.3 and also decided that I wanted to flash a new Kernel too, so I did with The Flash. Once everything booted back up, when I try to unlock my phone I get the message at the bottom of my screen saying "Fingerprint Hardware Not Available" and then once I just unlock with my pattern, WiFi won't turn on, I can click and click and it just stays greyed out. I read somewhere that flashing to the Stock+Safetynet Kernel that it could fix those problem, but it didn't for me. Would anyone know of any other solutions other than Factory reset? Thanks in advance.

absoluthamm said:
Yesterday I updated my Magisk to 15.3 and also decided that I wanted to flash a new Kernel too, so I did with The Flash. Once everything booted back up, when I try to unlock my phone I get the message at the bottom of my screen saying "Fingerprint Hardware Not Available" and then once I just unlock with my pattern, WiFi won't turn on, I can click and click and it just stays greyed out. I read somewhere that flashing to the Stock+Safetynet Kernel that it could fix those problem, but it didn't for me. Would anyone know of any other solutions other than Factory reset? Thanks in advance.
Click to expand...
Click to collapse
Fastboot the stock boot.img and see if it boots up normally without the warning. That's pretty strange behavior after flashing the Flash kernel. Kindly post your installation method when you can :good:

Badger50 said:
Fastboot the stock boot.img and see if it boots up normally without the warning. That's pretty strange behavior after flashing the Flash kernel. Kindly post your installation method when you can :good:
Click to expand...
Click to collapse
When I get a chance I'll download the stock image and try fastbooting it.
As far as my install method, I flashed the kernel via TWRP, then flashed Magisk, then rebooted.
Thanks!

absoluthamm said:
When I get a chance I'll download the stock image and try fastbooting it.
As far as my install method, I flashed the kernel via TWRP, then flashed Magisk, then rebooted.
Thanks!
Click to expand...
Click to collapse
Just for the heck of it, if you want to try, go back to TWRP and flash...
Flash kernel
The twrp.zip
Then reboot back into TWRP and flash the magisk zip. Then we'll see if that fixes it.

Badger50 said:
Just for the heck of it, if you want to try, go back to TWRP and flash...
Flash kernel
The twrp.zip
Then reboot back into TWRP and flash the magisk zip. Then we'll see if that fixes it.
Click to expand...
Click to collapse
Haven't had a chance to download the stock boot.img yet, but I did try your suggestion here and the same result happens, no fingerprint, no wifi.

absoluthamm said:
Haven't had a chance to download the stock boot.img yet, but I did try your suggestion here and the same result happens, no fingerprint, no wifi.
Click to expand...
Click to collapse
Darn! Oh well, if your still having trouble after you fastboot the stock boot.img, you may have to dirty flash the factory image. If that doesn't work, then a factory reset or a clean flash of the factory image might be needed. If that doesn't work, then you may have to run it in safe mode for a while. Finally, if that doesn't work, your hardware/software may be hosed and RMA here you come. Lets hope it's not that serious

This happened to me on the Pixel 2 when updating to the January image, I had do a full image wipe in order to fix it.

bro i am worried i wiped data cache vendor and flashed RR rom now the sim is not inserting and wifi bluetooth fingerprint music everything is not working ..what should i do

Related

Can't boot into recovery after cm14.1 nightly official

So as the title says, after flashing cm14. 1 can't go into recovery anymore, it just a black screen. I tried to use flashify but nothing, a couple of apps show that I have twrp 3.0.2.1 but can't get into it... Help?
Cheers
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Which thread is this from please?
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Yeah man im in the same boat, if i get time ill try this twrp recovery. Where did that recovery come from?, it seems like the CM recovery for 14.1 nightly high jacks the recovery partition (i call it that,i dont know the term for it)
Sent from my ONEPLUS A3000 using Tapatalk
I believe the official 14.1 nightlies are based on the CB which requires the modified TWRP, which is what @JKMB888 has linked you to.
Hw4ng3r said:
I believe the official 14.1 nightlies are based on the CB which requires the modified TWRP, which is what @JKMB888 has linked you to.
Click to expand...
Click to collapse
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Thanks a lot guys, that did the trick, and done with flashify
JKMB888 said:
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Click to expand...
Click to collapse
@JKMB888 it does work 100% is as simple as flashing the TWRP. Actually, i installed it with CM 14.1 running just fine
Sent from my ONEPLUS A3000 using Tapatalk
Just re flash the TWRP image via Fastboot. Apps like flashify actually use TWRP or whatever recovery installed to flash image file AFAIK. I recommend using modified TWRP,Flashing some roms break the access. But the modified one can withstand almost every new rom installs.
Hope it helps.
Why i have always mount decrypt data when i boot in recovery mode which is TWRP 3.0.2-22 aand ask me to input a password?
Edit: I found the solution, i had a pattern lock screen and i removed it!
HC4Life said:
Why i have always mount decrypt data when i boot in recovery mode which is TWRP 3.0.2-22 aand ask me to input a password?
Click to expand...
Click to collapse
At some point your phone data became encrypted. While booted up if you search for encrypt in settings you'll see your phone is encrypted.
Same thing happened to me yesterday after flashing 3.2.7 and booting up for the first time before going back to TWRP to flash AICP. Only way to decrypt permanently, as far as I know, is to wipe all data including internal and completely start from scratch.
GrandMasterB said:
At some point your phone data became encrypted. While booted up if you search for encrypt in settings you'll see your phone is encrypted.
Same thing happened to me yesterday after flashing 3.2.7 and booting up for the first time before going back to TWRP to flash AICP. Only way to decrypt permanently, as far as I know, is to wipe all data including internal and completely start from scratch.
Click to expand...
Click to collapse
Look at my edited reply...
m4manusraj said:
Just re flash the TWRP image via Fastboot. Apps like flashify actually use TWRP or whatever recovery installed to flash image file AFAIK. I recommend using modified TWRP,Flashing some roms break the access. But the modified one can withstand almost every new rom installs.
Hope it helps.
Click to expand...
Click to collapse
actually flashify did the trick for me as I had no access to a pc for the time
http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Flash this recovery. Fixed the problem for me
JKMB888 said:
I would like to truly confirm that the direct link to recovery, along with the thread in which it can be found, repair the situation. I was able to restore the backup of Freedom OS and the return to CM14.1 backup. We should keep this one somewhere near, jsut in case.
Click to expand...
Click to collapse
i am facing just the same situation with cm14.1 nightly and can't boot into recovery
i tried flashing the recovery image provided by you i.e. twrp-3.0.2-22-oneplus3.img but i face the same problem again
when i go into the recovery all i see is a black screen with a white notification light on and it remains there untill i switch off my phone manually using the power button
i tried facing the problem when i installed the cm14.1 nightly
i was unable to login snapchat as i device was rooted as said by the message on snapchat
so i decided to unroot my device via supersu FULL UNROOT option
after a reboot i successfully logged into snapchat
then i tried to root it again
i went into recovery to flash the supersu zip
and since then i have been unable to see the twrp recovey
please help me
This thread is a life save. Tried everything and it drove me nuts not getting into recovery.
THANK YOU!
gangangan2 said:
http://forum.xda-developers.com/one...nity-build-t3461648/post68691560#post68691560
Flash this recovery. Fixed the problem for me
Click to expand...
Click to collapse
Thank you so much it's work for me now..
After I got the recovery back, I flashed CM13 again and ARM64 6.0 Nano Gapps for my Oneplus 3, but I'm getting an error after the "preparing apps' screen is loaded saying that - unfortunately the process android.process.media has stopped one plus 3 boot and then the phone switches off.
Any solution to this? I've already tried flashing different versions of CM13.
Thank you!! I was looking for hours.
This link fixed the problem!
JKMB888 said:
Same situation here. Neither booting the recovery via fastboot without flashing nor flashing the TWRP an then booting into it result in black screen. Flashify gives no results here. Please help.
EDIT; flashing this one via fastboot restores the access to TWRP, confirming it right now. http://forum.xda-developers.com/devdb/project/dl/?id=21065&task=get
Click to expand...
Click to collapse
Hey, guys. I'm pretty sure I bricked my phone and there's no way to get out.
So I was on CM13 official builds on my OP3. Then, on the OTA update system they have, I got moved onto the CM14.1. I downloaded from here and went into my twrp recovery to flash. I made a clean flash and then proceeded to go back to system. I thought everything was ok until I realised I hadn't flashed a gapps package which I pretty much need to survive as all my contacts backups etc. are on there. I powered off my phone and went to go back into the recovery after downloading gapps 7.1 micro. It went past the *You're device can not be trusted'* and then went to the oneplus screen. After that, it stayed like that for about 30 secs and powered off. At first, I thought I messed something up and tried again. I repeated that for about 3 times and it didn't work. I tried going into the normal system and coming back to recovery and it didn't work still. In fact, now I can't even get into system. Now, i can only boot up to fastboot, where my computer still doesn't realise my phone is plugged in.
Anyone got any ideas on how to fix this? I wouldn't say I'm a noob at this because I have flashed many times before but I'm relatively new to the scene. I didn't see this thread before i ripped my hair out and i think wrecked my phone @JKMB888
EDIT: I sorted it out with help from Naman Bhalla's unbrick thread and this. A certain combo works and now I'm on CM14.1 enjoying life

trying to flash twrp; it just hangs!

Hi all,
*I've unlocked bootloader
* Have tried fastboot boot TWRP.img, as well as tried flashing TWRP RC1 via the Skipsoft toolkit.
Every way I've tried the phone just sits at the TWRP boot screen and doesn't allow me to go any further..
Any help here would be truly appreciated!
Cheers,
I've been having the same issue tonight. Re-flash the stock image, go through the whole setup process and make sure you add a lockscreen pin, then flash TWRP. That is what worked for me. I still can't flash a Rom though for some reason. It's driving me insane.
dutchy716 said:
I've been having the same issue tonight. Re-flash the stock image, go through the whole setup process and make sure you add a lockscreen pin, then flash TWRP. That is what worked for me. I still can't flash a Rom though for some reason. It's driving me insane.
Click to expand...
Click to collapse
You're braver than me. I haven't had my Pixel XL long but this is the first phone I've ever owned where I am afraid to try and install a custom recovery and ROM. With the dual partitions and what I hear about TWRP still being buggy it just seems like Google didn't want people to run anything but pure Android on the Pixels.
dutchy716 said:
I've been having the same issue tonight. Re-flash the stock image, go through the whole setup process and make sure you add a lockscreen pin, then flash TWRP. That is what worked for me. I still can't flash a Rom though for some reason. It's driving me insane.
Click to expand...
Click to collapse
Same issue here, but no solution. Adding a lockscreen pin didn't change anything for me. I just get a teamwin image but it just sits there & doesn't actually open TWRP. My bootlocker is unlocked but thats as far as I can get 7.1.2 with May security. I have tried reloading everything and followed commonly recommended steps.
Any suggestions greatly appreciated. I would love to get this thing rooted and get some ROM flexibility - even to just get rid of the Nav Bar ....
mikefnz said:
Same issue here, but no solution. Adding a lockscreen pin didn't change anything for me. I just get a teamwin image but it just sits there & doesn't actually open TWRP. My bootlocker is unlocked but thats as far as I can get 7.1.2 with May security. I have tried reloading everything and followed commonly recommended steps.
Any suggestions greatly appreciated. I would love to get this thing rooted and get some ROM flexibility - even to just get rid of the Nav Bar ....
Click to expand...
Click to collapse
I have never had a problem. Make sure your using the rc1 fast boot TWRP. Should be fastboot boot twrp.img. I change file name to this or copy and paste. Then you install rc1 or rc2 zip.
I know you will have problems if you try to install the wrong file.
mac796 said:
I have never had a problem. Make sure your using the rc1 fast boot TWRP. Should be fastboot boot twrp.img. I change file name to this or copy and paste. Then you install rc1 or rc2 zip.
I know you will have problems if you try to install the wrong file.
Click to expand...
Click to collapse
I am doing exactly as you mentioned.. flash rc1.img, however the phone does not go beyond the boot screen, it just sits there.... Can I ask what steps you are taking prior to flashing twrp? Thanks!
mazubo said:
I am doing exactly as you mentioned.. flash rc1.img, however the phone does not go beyond the boot screen, it just sits there.... Can I ask what steps you are taking prior to flashing twrp? Thanks!
Click to expand...
Click to collapse
Hmm are you on may bootloader because i think modifying the boot partition causes bootloop without the boot signature?
XtraArrow said:
Hmm are you on may bootloader because i think modifying the boot partition causes bootloop without the boot signature?
Click to expand...
Click to collapse
Yes I am.. should I downgrade to 7.1.1? Tjere was no mention of that issue in the skipsoft toolkit thread... Weird!
mazubo said:
Yes I am.. should I downgrade to 7.1.1? Tjere was no mention of that issue in the skipsoft toolkit thread... Weird!
Click to expand...
Click to collapse
Sure, i guess.. or you could just manually flash the April bootloader. a lot easier.
XtraArrow said:
Sure, i guess.. or you could just manually flash the April bootloader. a lot easier.
Click to expand...
Click to collapse
Ok, would flashing just the bootloader wipe the phone? Also how would I find just the bootloader? Thanks for the suggestion, I haven't flashed just a bootloader before..
mazubo said:
I am doing exactly as you mentioned.. flash rc1.img, however the phone does not go beyond the boot screen, it just sits there.... Can I ask what steps you are taking prior to flashing twrp? Thanks!
Click to expand...
Click to collapse
That strange. I just flash a factory image from Google
Set up a security pattern
Enable adb debugging
Fastboot boot twrp 3.0.2-0 rc1 IMG
Make sure it asks for your security pattern if it doesn't reboot to bootloader and fastboot twrp again, and keep repeating until it does
Install twrp 3.1.0.0 rc2 or rc1 zip
If your using may bootloader's fish VBS 6 zip
And it should stick, if you flash. Anything else that messes with boot flash that VBS zip at the end again
mazubo said:
Ok, would flashing just the bootloader wipe the phone? Also how would I find just the bootloader? Thanks for the suggestion, I haven't flashed just a bootloader before..
Click to expand...
Click to collapse
If you download the offiial april firmware, you can manually extract it from the .zip then you would do this command in fastboot :--------- fastboot flash bootloader PUTFILEHERE.img
EDIT: Are you able to get into TWRP by any chance??
mac796 said:
That strange. I just flash a factory image from Google
Set up a security pattern
Enable adb debugging
Fastboot boot twrp 3.0.2-0 rc1 IMG
Make sure it asks for your security pattern if it doesn't reboot to bootloader and fastboot twrp again, and keep repeating until it does
Install twrp 3.1.0.0 rc2 or rc1
If your using may bootloader's fish VBS 6 zip
And it should stick, if you flash. Anything else that messes with boot flash that VBS zip at the end again
Click to expand...
Click to collapse
Hmm, maybe this is where I've gone wrong.. I thought the need to create a security pin/pattern was only if coming from a previously rooted state, or from a custom ROM. I will try this as well and report back.. thanks!
XtraArrow said:
If you download the offiial april firmware, you can manually extract it from the .zip then you would do this command in fastboot :--------- fastboot flash bootloader PUTFILEHERE.img
EDIT: Are you able to get into TWRP by any chance??
Click to expand...
Click to collapse
Unable to get into twrp as previously mentioned. I flash the IMG file, then it just hangs on the TWRP boot screen..
mazubo said:
Unable to get into twrp as previously mentioned. I flash the IMG file, then it just hangs on the TWRP boot screen..
Click to expand...
Click to collapse
Alright, try doing what I mentioned. Download April firmware, extract the bootloader.img from it and flash using command above.
XtraArrow said:
Alright, try doing what I mentioned. Download April firmware, extract the bootloader.img from it and flash using command above.
Click to expand...
Click to collapse
This seems likely to work. Thanks for the suggestions, and I'll report back! Cheers!
mazubo said:
This seems likely to work. Thanks for the suggestions, and I'll report back! Cheers!
Click to expand...
Click to collapse
I'm no expert but it's seems like a decent suggestion. Let us know how it goes.
@mazubo
You keep stating that you just flash the image. Are you flashing it from the bootloader then trying to boot to recovery?
You have to boot TWRP from your PC first. Then from TWRP you can then "flash" TWRP.
Just wanted to make sure that was a step you were taking!
Just wait. It will take little longer
Sent from my Pixel XL using Tapatalk
freddy0872 said:
@mazubo
You keep stating that you just flash the image. Are you flashing it from the bootloader then trying to boot to recovery?
You have to boot TWRP from your PC first. Then from TWRP you can then "flash" TWRP.
Just wanted to make sure that was a step you were taking!
Click to expand...
Click to collapse
Yes, I have tried fastboot to flash the TWRP img, as well as skipsofts toolkit. I guess I've been using the term "flash" for fastboot, as I haven't been able to use twrp yet.. I understand that you need to flash the TWRP img via pc and then flash the TWRP zip, then SuperSU or magisk, whatever your poison may be !

What is the CORRECT way to gain ROOT in PDP3?

I have attempted :
-Fastboot boot TWRP.img
-Reboot Recovery
-TWRP Flash Magisk v16.4
-Reboot into System
Am i missing a Kernel? If so, where is the Kernel for PDP3?
Am i missing a Patched_Boot.img? If so, where is the PDP3 Patched_Boot.img?
What is the correction instruction for gaining ROOT on PDP3?
What else may i be missing from the recipe?
I have searched and asked others via PM or in the Thread, and have received half-ass replies.... So would someone please lay it out, if not, i guess i will go back to 8.1.0....where i had ROOT, Recovery, and Viper4Android... Thank God I made a back-up....
Thanks in advance,
T
AndroidDevices said:
I have attempted :
-Fastboot boot TWRP.img
-Reboot Recovery
-TWRP Flash Magisk v16.4
-Reboot into System
Am i missing a Kernel? If so, where is the Kernel for PDP3?
Am i missing a Patched_Boot.img? If so, where is the PDP3 Patched_Boot.img?
What is the correction instruction for gaining ROOT on PDP3?
What else may i be missing from the recipe?
I have searched and asked others via PM or in the Thread, and have received half-ass replies.... So would someone please lay it out, if not, i guess i will go back to 8.1.0....where i had ROOT, Recovery, and Viper4Android... Thank God I made a back-up....
Thanks in advance,
T
Click to expand...
Click to collapse
I'm generally curious how many times, and in how many threads, you're going to ask this question.
1) Flash DP3. Let the device boot, log in, set it up, etc.. I do NOT enable a pin/pattern yet.
2) Reboot to the bootloader & fastboot TWRP.
3) Flash Magisk 16.4.
4) Boot into the system & have root.
I've done this process damn near 10x going between dp2/8.1/dp3. There is no special trick to it.
EvilDobe said:
I'm generally curious how many times, and in how many threads, you're going to ask this question.
1) Flash DP3. Let the device boot, log in, set it up, etc.. I do NOT enable a pin/pattern yet.
2) Reboot to the bootloader & fastboot TWRP.
3) Flash Magisk 16.4.
4) Boot into the system & have root.
I've done this process damn near 10x going between dp2/8.1/dp3. There is no special trick to it.
Click to expand...
Click to collapse
If he wants recovery, he needs to flash twrp-Pixel2XLinstaller-.zip before flashing magisk 16.4
Tulsadiver said:
If he wants recovery, he needs to flash twrp-3.2.1-2-taimen.zip before flashing magisk 16.4
Click to expand...
Click to collapse
OP didn't ask for recovery. OP asked how to get root. While you are 100% correct on how to get a static TWRP instance it is not relevant to the OP getting root.
EvilDobe said:
OP didn't ask for recovery. OP asked how to get root. While you are 100% correct on how to get a static TWRP instance it is not relevant to the OP getting root.
Click to expand...
Click to collapse
He did mention that he would want to go back because he had root and recovery.....
EvilDobe said:
OP didn't ask for recovery. OP asked how to get root. While you are 100% correct on how to get a static TWRP instance it is not relevant to the OP getting root.
Click to expand...
Click to collapse
I'll take TWRP as well, wasnt sure if there was an unofficial version for P or not...
Tulsadiver said:
He did mention that he would want to go back because he had root and recovery.....
Click to expand...
Click to collapse
Semantics. OP's post, and general boggle, is that they cannot obtain root on DP3. My response was directly related to the OPs post, and last like 10 comments across this sub. What OP had is presently irrelevant since the current goal is to obtain root. If the OP had an additional question as to how to obtain static TWRP I would have addressed that at a later date/time or your response would have been appropriate. Perhaps I took it for granted that the OP had an understanding on how to get static TWRP but, again, the point of this thread is getting root on DP3 which my response answers & yours does not.
Tulsadiver said:
If he wants recovery, he needs to flash twrp-Pixel2XLinstaller-.zip before flashing magisk 16.4
Click to expand...
Click to collapse
After i flash the TWRP Installer, do i reboot and change slots, or no?
EvilDobe said:
Semantics. OP's post, and general boggle, is that they cannot obtain root on DP3. My response was directly related to the OPs post, and last like 10 comments across this sub. What OP had is presently irrelevant since the current goal is to obtain root. If the OP had an additional question as to how to obtain static TWRP I would have addressed that at a later date/time or your response would have been appropriate. Perhaps I took it for granted that the OP had an understanding on how to get static TWRP but, again, the point of this thread is getting root on DP3 which my response answers & yours does not.
Click to expand...
Click to collapse
I appreciate BOTH of your help, no need to get all technical!
AndroidDevices said:
After i flash the TWRP Installer, do i reboot and change slots, or no?
Click to expand...
Click to collapse
No, flash Magisk unless you want to try a custom kernel. If so, flash it before Magisk, flash Magisk, then reboot.
After flashing magisk, the phone will not reboot, instead keeping me in a bootloop and sending me back into TWRP. Any ideas? Im happy to go back to stock if thatll make my phone work again!
Jameswebb97 said:
After flashing magisk, the phone will not reboot, instead keeping me in a bootloop and sending me back into TWRP. Any ideas? Im happy to go back to stock if thatll make my phone work again!
Click to expand...
Click to collapse
Hi James what exactly did you flash before magisk and I'm guessing you were flashing from stock and also not p?Also how did you flash?
all43 said:
Hi James what exactly did you flash before magisk and I'm guessing you were flashing from stock and also not p?Also how did you flash?
Click to expand...
Click to collapse
Hey,
I was installing from P (9.0 DP3)
I installed TWRP first by flashing the image and then installing the zip file on to the phone.
Next i installed magisk, the installation all went through absolutely fine.
When i hit reboot, it goes onto the white splash screen, then brings up a small progress bar that goes across. This lasts for a minute or two, then dumps me back into TWRP.
I attempted all ways listed, and i end up Booting into Stock Recovery with a corrupt message forcing me to Power Off or Factory Reset or i got stuck at the Loading "G". Ended up restoring my June 8.1.0 Back up. Thanks for trying to help... I'll wait till there is more info on the subject...
AndroidDevices said:
I attempted all ways listed, and i end up Booting into Stock Recovery with a corrupt message forcing me to Power Off or Factory Reset or i got stuck at the Loading "G". Ended up restoring my June 8.1.0 Back up. Thanks for trying to help... I'll wait till there is more info on the subject...
Click to expand...
Click to collapse
A complete wipe when going to P is the best way to ensure there are no problems but what has worked for me is after installing dp3, rebooting to fastboot, booting to TWRP and doing a factory reset in TWRP. You will not lose data but will have to set your phone up as new. Then, boot back to fastboot and following the instructions as stated in the prior posts to gain root and recovery.
Tulsadiver said:
A complete wipe when going to P is the best way to ensure there are no problems but what has worked for me is after installing dp3, rebooting to fastboot, booting to TWRP and doing a factory reset in TWRP. You will not lose data but will have to set your phone up as new. Then, boot back to fastboot and following the instructions as stated in the prior posts to gain root and recovery.
Click to expand...
Click to collapse
Thanks, i'll give it a try again with a Factory Reset 1st...
AndroidDevices said:
I attempted all ways listed, and i end up Booting into Stock Recovery with a corrupt message forcing me to Power Off or Factory Reset or i got stuck at the Loading "G". Ended up restoring my June 8.1.0 Back up. Thanks for trying to help... I'll wait till there is more info on the subject...
Click to expand...
Click to collapse
Which version of TWRP are you using (twrp-3.2.1-2 is the latest)? Are you seeing errors in the twrp gui while flashing? I'm not sure what you mean by "more info on it" because it's literally just flash the Magisk zip then reboot. The only things I can think of are that you're using an older version of twrp or the magisk zip is corrupt giving you a bad install.
EvilDobe said:
Which version of TWRP are you using (twrp-3.2.1-2 is the latest)? Are you seeing errors in the twrp gui while flashing? I'm not sure what you mean by "more info on it" because it's literally just flash the Magisk zip then reboot. The only things I can think of are that you're using an older version of twrp or the magisk zip is corrupt giving you a bad install.
Click to expand...
Click to collapse
Yes, always using the latest TWRP Official Builds. No errors in the script. What i mean by more info, is just that, when someone posts a thread, and i see it is working for users without issue, i will take the plunge if this doesnt work this time. And im using Magisk v16.4beta...
I think i am so use to Fastboot boot TWRP3212.img, then flashing the installer and rebooting to switch slots. I'm sure i am just not following something. Do i need to reboot after flashing Installer and before flashing Magisk, or NO reboot?
AndroidDevices said:
Yes, always using the latest TWRP Official Builds. No errors in the script. What i mean by more info, is just that, when someone posts a thread, and i see it is working for users without issue, i will take the plunge if this doesnt work this time. And im using Magisk v16.4beta...
I think i am so use to Fastboot boot TWRP3212.img, then flashing the installer and rebooting to switch slots. I'm sure i am just not following something. Do i need to reboot after flashing Installer and before flashing Magisk, or NO reboot?
Click to expand...
Click to collapse
Don't reboot, TWRP installer installs to both slots.
Flash installer, hit back button, find magisk.zip, flash it.
AndroidDevices said:
Yes, always using the latest TWRP Official Builds. No errors in the script. What i mean by more info, is just that, when someone posts a thread, and i see it is working for users without issue, i will take the plunge if this doesnt work this time. And im using Magisk v16.4beta...
I think i am so use to Fastboot boot TWRP3212.img, then flashing the installer and rebooting to switch slots. I'm sure i am just not following something. Do i need to reboot after flashing Installer and before flashing Magisk, or NO reboot?
Click to expand...
Click to collapse
What happens when you just do this:
Get DP flashed & configured. No passwords/patterns/security features.
fastboot boot TWRP3212.img
Flash your magisk 16.4 file.
Reboot.

Is there any way to remove the "Your device is corrupt" Message at Boot?

Had root for 3 days, No issues at all.
Just swapped a kernel to test, and started getting this.
Phone boots after pressing the power button, But wondering whether this can be removed ?
On Stock rom, Flash Kernel and Magisk.
JazonX said:
Had root for 3 days, No issues at all.
Just swapped a kernel to test, and started getting this.
Phone boots after pressing the power button, But wondering whether this can be removed ?
On Stock rom, Flash Kernel and Magisk.
Click to expand...
Click to collapse
Hmm I don't get that issue on flash kernel
If its that red error message,
Download the factory images from whatever security patch you're on, extract the second zip that contains all the .img files.
Then, fastboot flash the vbmeta image file and reboot. Message should be gone.
ram4ufriends said:
Hmm I don't get that issue on flash kernel
Click to expand...
Click to collapse
I didn't used to get it either. I flashed the stock patched kernel to test Safetynet and then flashed the flash kernel back again. While booting into the stock patched kernel, this message started to appear. But even after flashing the flash kernel, the message at boot didn't go away.
Safetynet still passes fine. So it's not a major issue. But.. Just annoying.
I believe this is/was an old bug of Magisk (something about verity or dm-boot or something...). It has since been patched, but it seems that installing the kernel and whatnot may have jumbled something "loose" -- I used to receive this sometimes even after the initial patc . If anything, I believe re-installing everything should fix this. If you really want to go "all out", I suggest using the magisk-uninstaller to get things completely out and clean, then reinstall...
Something to keep in mind, installing a kernel usually breaks/undo the Magisk patch/exploit on the boot image/partition; that's why you usually have to install Magisk last -- i.e. when I flash the monthly Full Factory image to update, I install twrp, kernel, and lastly magisk in that order...
Hopefully this helps....
Thanks a ton, Stock Image flash and then Kernal and Magisk again got rid of the Message.
Didn't lose any data!
I love this phone.
JazonX said:
Thanks a ton, Stock Image flash and then Kernal and Magisk again got rid of the Message.
Didn't lose any data!
I love this phone.
Click to expand...
Click to collapse
Glad I was able to help and it worked out for you! :good::highfive:

Device turns off randomly after root

Hi guys, I rooted my redmi note 8 yesterday. Everything went well except two things: on boot the error message said that "there is an internal problem" and the phone reboots/shuts down itself.
Any thoughts?
cicish said:
Hi guys, I rooted my redmi note 8 yesterday. Everything went well except two things: on boot the error message said that "there is an internal problem" and the phone reboots/shuts down itself.
Any thoughts?
Click to expand...
Click to collapse
You should explain the problem obviously if you want a help, if your phone still working you should flash twerp.img to be able to root it and solve any existing problem by flashing new rom
niceman2007 said:
You should explain the problem obviously if you want a help, if your phone still working you should flash twerp.img to be able to root it and solve any existing problem by flashing new rom
Click to expand...
Click to collapse
Hey thanks for answer.
Actually i did everything correctly, flashed latest twrp, tried several roms, oficial, unoficial etc., But still no result. After all these, ive flashed the stock rom which solved the problem but phone is no more rooted. So..
cicish said:
Hey thanks for answer.
Actually i did everything correctly, flashed latest twrp, tried several roms, oficial, unoficial etc., But still no result. After all these, ive flashed the stock rom which solved the problem but phone is no more rooted. So..
Click to expand...
Click to collapse
If you still want to root it again,after flasing new rom go to twero and then go to wipe then format,you should format your phone after rom flashing,try this and inform me
Yes yes! I want to root phone once again. So the steps are these:
1) booting into twrp with adb from pc.
2) from the twrp menu wiping and formating the data
3) instaling new rom
Is this true?
Thanks!
If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.
Leeban Joseph said:
If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.
Click to expand...
Click to collapse
You mean that its possible to have root access on stock rom?
Leeban Joseph said:
If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.
Click to expand...
Click to collapse
Hey, I was able to flash magical using twrp but can't flash dm-verity. It gives me some error 1 with no description. I could flash magisk. What can the problem be? Thanks!
cicish said:
Hey, I was able to flash magical using twrp but can't flash dm-verity. It gives me some error 1 with no description. I could flash magisk. What can the problem be? Thanks!
Click to expand...
Click to collapse
From your stock rom extract the boot.img and place it on your SD card. Flash the boot image using twrp or you can also flash in fastboot, then reboot. Now boot to twrp recovery and flash dm-verity first and then magisk zip. Worked for me I'm having root permission with stock rom.
Leeban Joseph said:
From your stock rom extract the boot.img and place it on your SD card. Flash the boot image using twrp or you can also flash in fastboot, then reboot. Now boot to twrp recovery and flash dm-verity first and then magisk zip. Worked for me I'm having root permission with stock rom.
Click to expand...
Click to collapse
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange
cicish said:
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange
Click to expand...
Click to collapse
UPDATE: after another custom rom install failure, i got back to stock miui 11 with miflash tool. the problem is now that when i unlock the bootloader and try to flash magisk and disable-dm-verity, the system refuses to boot. the redmi note 8 logo is sticked on boot. i dont understand what i am doing incorrectly. if there are any suggestions im ready to try.
cicish said:
UPDATE: after another custom rom install failure, i got back to stock miui 11 with miflash tool. the problem is now that when i unlock the bootloader and try to flash magisk and disable-dm-verity, the system refuses to boot. the redmi note 8 logo is sticked on boot. i dont understand what i am doing incorrectly. if there are any suggestions im ready to try.
Click to expand...
Click to collapse
Is your bootloader unlocked right now or did you lock it while flashing using miflash tool.
Leeban Joseph said:
Is your bootloader unlocked right now or did you lock it while flashing using miflash tool.
Click to expand...
Click to collapse
the bootloader was unlocked. everything went kinda fine, until i flashed youtube vanced from magisk: when i did that, the system was unable to boot. i don't know what's happening. is there anything to do with kernel or something? really interesting what i am doing wrong.
cicish said:
the bootloader was unlocked. everything went kinda fine, until i flashed youtube vanced from magisk: when i did that, the system was unable to boot. i don't know what's happening. is there anything to do with kernel or something? really interesting what i am doing wrong.
Click to expand...
Click to collapse
I think it may be because of YouTube vanced module. If you remove the module you might be able to boot. In twrp in the advanced option select file manager and then select data/adb/magisk/ in that you will find the list of installed modules, select the one which is causing the problem and delete that folder and try to reboot.
Leeban Joseph said:
I think it may be because of YouTube vanced module. If you remove the module you might be able to boot. In twrp in the advanced option select file manager and then select data/adb/magisk/ in that you will find the list of installed modules, select the one which is causing the problem and delete that folder and try to reboot.
Click to expand...
Click to collapse
I've already flashed the stock rom but this will help me next time! Thanks!
I'll stop trying for some days cause I'm really tired with tweaking so thanks and will get back!
cicish said:
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange
Click to expand...
Click to collapse
Your device reboots randomly on custom rom because probably it was made for tianma display and you have hauxing display
the_weird_aquarian said:
Your device reboots randomly on custom rom because probably it was made for tianma display and you have hauxing display
Click to expand...
Click to collapse
Hey, thanks for the answer. i've just googled about it and you are right. checked the TP version and it says that i have huaxing display. in the Lineage OS thread the moderator wrote that the next update will fix that bug. hopefully ill be able to install custom rom. also if you know, are there any custom roms for huaxing display? thank you man!
cicish said:
Hey, thanks for the answer. i've just googled about it and you are right. checked the TP version and it says that i have huaxing display. in the Lineage OS thread the moderator wrote that the next update will fix that bug. hopefully ill be able to install custom rom. also if you know, are there any custom roms for huaxing display? thank you man!
Click to expand...
Click to collapse
currently bootleggers rom,PE official and unofficial and drepfest all have reboot issues in huaxing display. Haven't tried any other rom yet..still on MIUI..waiting to get the issue fixed asap.
the_weird_aquarian said:
currently bootleggers rom,PE official and unofficial and drepfest all have reboot issues in huaxing display. Haven't tried any other rom yet..still on MIUI..waiting to get the issue fixed asap.
Click to expand...
Click to collapse
i've tried Lineage OS too and it also has reboot issue. i've checked a thread here https://forum.xda-developers.com/redmi-note-5-pro/development/derp-kernel-clang-4-4-138-t3804996 that flashing a different kernel when you have flashed a custom rom can fix the problem. idk if its safe to do
cicish said:
i've tried Lineage OS too and it also has reboot issue. i've checked a thread here https://forum.xda-developers.com/redmi-note-5-pro/development/derp-kernel-clang-4-4-138-t3804996 that flashing a different kernel when you have flashed a custom rom can fix the problem. idk if its safe to do
Click to expand...
Click to collapse
that thread is for redmi note 5 pro..and flashing different kernel probably won't solve it because I know few guys flashed genom kernel but still ended up with reboot in huaxing display. Maybe waiting for fix is better.

Categories

Resources