Related
Hello, it is my first time trying to write a post on xda so excuse me if I do something wrong.
I've been playing with Roms a lot of time, installing, uninstalling, bricking and unbricking phones. so have a pretty good idea of how it works but now I just don't know what I did wrong and my phone is just ... in a black screen after boot image.
I was currently on DP5 android 9 by @joeyhuab and everything worked perfectly. Today was released android Pie and I just want to try it. So, I made the steps for DP5 to PR1 and everything runs well until I reboot from TWRP to the system. Now when I turn the phone on. it just appears the boot logo and later a black screen.
I can't restart the phone pressing the power button after some seconds but it goes to the boot image and later the black image screen (of the dead) appears.
1. I can't go to TWRP. (power+ Vol+)
2. I can't go to Fastboot. (power+ Vol-)
3. Charge Image is not displaying.
Windows sounds when i connected on the black screen state but fastboot don't.
This is my first time dealing with this kind of problem. I just don't know what would be the next step to try, Mi A1 is one of the best phones and I don't want to lose it.
Thank you for reading XDA, You are the best
hiddengoka said:
Hello, it is my first time trying to write a post on xda so excuse me if I do something wrong.
I've been playing with Roms a lot of time, installing, uninstalling, bricking and unbricking phones. so have a pretty good idea of how it works but now I just don't know what I did wrong and my phone is just ... in a black screen after boot image.
I was currently on DP5 android 9 by @joeyhuab and everything worked perfectly. Today was released android Pie and I just want to try it. So, I made the steps for DP5 to PR1 and everything runs well until I reboot from TWRP to the system. Now when I turn the phone on. it just appears the boot logo and later a black screen.
I can't restart the phone pressing the power button after some seconds but it goes to the boot image and later the black image screen (of the dead) appears.
1. I can't go to TWRP. (power+ Vol+)
2. I can't go to Fastboot. (power+ Vol-)
3. Charge Image is not displaying.
Windows sounds when i connected on the black screen state but fastboot don't.
This is my first time dealing with this kind of problem. I just don't know what would be the next step to try, Mi A1 is one of the best phones and I don't want to lose it.
Thank you for reading XDA, You are the best
Click to expand...
Click to collapse
Press vol+ vol- + power at the same time until phone vibrates
Sent from Mi A1 with Tapatalk Pro
hiddengoka said:
Hello, it is my first time trying to write a post on xda so excuse me if I do something wrong.
I've been playing with Roms a lot of time, installing, uninstalling, bricking and unbricking phones. so have a pretty good idea of how it works but now I just don't know what I did wrong and my phone is just ... in a black screen after boot image.
I was currently on DP5 android 9 by @joeyhuab and everything worked perfectly. Today was released android Pie and I just want to try it. So, I made the steps for DP5 to PR1 and everything runs well until I reboot from TWRP to the system. Now when I turn the phone on. it just appears the boot logo and later a black screen.
I can't restart the phone pressing the power button after some seconds but it goes to the boot image and later the black image screen (of the dead) appears.
1. I can't go to TWRP. (power+ Vol+)
2. I can't go to Fastboot. (power+ Vol-)
3. Charge Image is not displaying.
Windows sounds when i connected on the black screen state but fastboot don't.
This is my first time dealing with this kind of problem. I just don't know what would be the next step to try, Mi A1 is one of the best phones and I don't want to lose it.
Thank you for reading XDA, You are the best
Click to expand...
Click to collapse
I also had this issue I think it is because of any xposed modules or magisk modules.
When I flashed xposed uninstaller, the phone revived
hiddengoka said:
Hello, it is my first time trying to write a post on xda so excuse me if I do something wrong.
I've been playing with Roms a lot of time, installing, uninstalling, bricking and unbricking phones. so have a pretty good idea of how it works but now I just don't know what I did wrong and my phone is just ... in a black screen after boot image.
I was currently on DP5 android 9 by @joeyhuab and everything worked perfectly. Today was released android Pie and I just want to try it. So, I made the steps for DP5 to PR1 and everything runs well until I reboot from TWRP to the system. Now when I turn the phone on. it just appears the boot logo and later a black screen.
I can't restart the phone pressing the power button after some seconds but it goes to the boot image and later the black image screen (of the dead) appears.
1. I can't go to TWRP. (power+ Vol+)
2. I can't go to Fastboot. (power+ Vol-)
3. Charge Image is not displaying.
Windows sounds when i connected on the black screen state but fastboot don't.
This is my first time dealing with this kind of problem. I just don't know what would be the next step to try, Mi A1 is one of the best phones and I don't want to lose it.
Thank you for reading XDA, You are the best
Click to expand...
Click to collapse
I have the same problem, my Mi A1 dont boot and i cant open fastboot mode (and screen dont turn on when charging), how you solved it?
Stuck on black screen
i was on aex 6.1 flashed this build and stuck on black screen.and i am unable to go to twrp .. steps i used to flash this
-->clean wipe(system,dalvik,data)
-->flashed aex6.2
-->flashed twrp installer
-->reboot to recovery
but it didnt reboot to recovery.
i think it boots but it shows only black screen as when i am taking screenshots its making sound.
ideepeshtiwari said:
i was on aex 6.1 flashed this build and stuck on black screen.and i am unable to go to twrp .. steps i used to flash this
-->clean wipe(system,dalvik,data)
-->flashed aex6.2
-->flashed twrp installer
-->reboot to recovery
but it didnt reboot to recovery.
i think it boots but it shows only black screen as when i am taking screenshots its making sound.
Click to expand...
Click to collapse
im also having the same issue. while flashing aex v6.2 on my mi a1
help me out from the same problem
This morning i have flashed havoc 2.0 after that flashed TWRP recovery and then i reboot to recovery mobile gets rebooted and after the boot page the screen went black. I have rebooted the mobile so many times same issue facing i am receiving calls means mobile is ringing but i cant see anything on screen. Plz help me out
khadar709 said:
This morning i have flashed havoc 2.0 after that flashed TWRP recovery and then i reboot to recovery mobile gets rebooted and after the boot page the screen went black. I have rebooted the mobile so many times same issue facing i am receiving calls means mobile is ringing but i cant see anything on screen. Plz help me out
Click to expand...
Click to collapse
Flash the previous rom and everything will be back to normal.
Shilldas said:
Flash the previous rom and everything will be back to normal.
Click to expand...
Click to collapse
I am not able to do that I can't go to twrp mode here also same black black screen.I can go to fastboot mode but I am not enabled usb debugging mode and system is not recognising mobile.
Help me how can I solve this..
Thanks in advance. ?
Install 'scrcpy' in your PC. Try to flash twrp from PC using fastboot and adb method. (I hope fastboot shows up on your phone) if u can boot to twrp via PC then go ahead and install any other rom. If u can't then connect your phone to PC and open scrcpy.exe here you can control your screen. (Most custom roms come with usb debugging enabled, if not try " AEX V.6.1 rom)
Usb debugging is compulsory. Thanks a lot for the information I will try this.
So i had this exact same issue. It was booting to twrp but screen was just blank.
i was trying to root the devive so i flashed the zip file by following command through adb
adb shell twrp install /sdcard/Magisk-v23.0.zip
it flashed the magisk and it was done. Similarly you can flash any zip file. If zip file is not copied to internal memory you can copy it using following command
adb push Magisk-v23.0.zip /sdcard/
I hope it helps someone in need.
Thanks.
Hi similar problem. Phone was locked in bootloop. I use reset pin and flash latest fw, flash successful in 220sec. Then screen stays black. Holding any combination will power up phone with black screen... wonder if it burn resistor or it is a flash issue. Trying to reflash again, however it stays 1000sec and still flashing.
Hi have mine FIXED.
Tried again to flash with android 9. Not able to finish flash in 4hrs. Then disconnect. Screen show battery 100%, then again only black screen but powered. Also 3 buttons are lighting. So I start pushing them and the screen, got some feedback and sound from touching the screen. Then the phone restart, screen ON. Show the normal white screen and ENCRYPTING storage screen that should come after flash. Then again reboot itself and start installing android (just taking a lot of time). Now all work on android 9, not giving option for OEM update to android 10, however afraid to flash again... good enough for my son (either way will break it in an year).
p.s
Im Samsung S class user for 10 years, so it is quite unfriendly phone... (need debugging on to connect to PC, for file transfer )
At last I found a way to run TWRP on tissot correctly without black screen.
Just install oreo 3.2.1-2 on Mi A1 (tissot).
This file (recovery-3.2.1-2-oreo.img) is working well.
Download it from this site:
https://androidfilehost.com/?fid=818070582850498337
Reference:
https://forum.xda-developers.com/t/...2-1-2-oreo-touch-recovery-2018-03-06.3688472/
Download Android 13.00 unofficial ROM for Mi A1 and install it easily by TWRP oreo 3.2.1-2:
https://sourceforge.net/projects/lafactorial-tissot/files/
Good luck,
Sed
Releases · zignas/twrp_device_xiaomi_tissot_treble
android 9.0 Device tree for TWRP 3.5.2 with Tissot manager - zignas/twrp_device_xiaomi_tissot_treble
github.com
also working fiine
Hey! I hope this is the right forum section. I tried to root my OnePlus 2 (OxygenOS3.6.1, android 6.0.1) so that I would be able to spoof on Pokémon(yeah lol...). I'm quite a computer noob, so I looked for a guide and found this Indian guy's YouTube video: [can't post a link, but his name is Tech Matrix and the video is called "how to root the OnePlus 2 (unlock/custom recovery)] I followed the steps and using the 'run me' file I was able to unlock my bootloader and to 'instal' twrp. But that's where it didn't work. In the video at 3:45 when he goes into recovery modeby long pressing power and volume button, twrp opens, but for me the OnePlus logo loading screens stays on and I'm not able to install SuperSU like he does. Quite a bummer because I was carefully following him, but now I'm wondering what to do next? Since my phone is already 'unlocked' should I continue with another guide from there, but what about the twrp that was installed but of which I saw no effect? Can this be harmful and should I try to revert all the actions and start over completely (which I don't know how) or just continue a different guide starting from where the phone is unlocked?
What did the black terminal show when you ran this command to flash the TWRP recovery to your phone? OKAY 2 times or just once and the 2nd line showed an error?
fastboot flash recovery op2-twrp.img
EDIT: Thankfully I could resolve this issue on my own fairly easily. My battery drained relatively quickly, and the issue didn't repeat when I tried booting again.
Hi XDA developers community,
Using some of the guides on this fantastic website I flashed LineageOS on my A2017G a few months ago. Now I tried reverting back to stock by flashing the B03 Oreo zip file in EDL mode (this guide).
The first reboot was already successful: I powered the phone on via the power button, then went through "can't be checked for corruption" screen, then got into the screen with Tux (Linux penguin), pressed volume up to go to recovery just to be sure, and rebooted from there into Android.
Although instead of starting the setup process Android dropped my right into the lock screen. I assumed that was because I hadn't factory reset yet and my data partition still had garbage data (that was step 18 of the guide btw). So, I powered off, from Android, and tried booting into recovery mode again to do the factory reset. However, now, after the Android corruption warning screen, the Linux Tux screen just stays there. Recovery mode doesn't appear, neither did it boot into Android. I can't even force power off by pressing the button (I pressed 80 seconds straight, no effect). No combination of volume and power buttons does anything, even pressing and holding it.
Right now I plan to let the battery drain on its own to get the device to power off. That's probably gonna take some days because the battery is completely charged. Is there some other possibility to make it go faster? Maybe heat the battery up from the outside with a hair dryer? I would rather not open the phone up and take the battery out, because I don't have a heat gun and I'm also worried I'm gonna leave scratch marks or something (the process seems quite rough).
And also, when the battery is drained, is there any recommendation on what I should do? Simply try again, going into recovery mode? Flash the EDL file again?
Thank you for reading all this, and I'd be so glad for any help.
I'm having this screen too, I'm trying to gsi, but none works, only lineage 16, but it gives error and closes the system at 16, and at lineage 15 the battery is being drained very quickly
Any rom stock I try to flash via edl gets in bootloop on the penguin screen, I can do the flash via edl from a los rom with 15.1 with oki twrp, some bugs, but would like to return to stock, can anyone help us?
same issue
Hello there
I have the same issue, can you please help ?
Thank you in advance
prasnel
kangalioo said:
EDIT: Thankfully I could resolve this issue on my own fairly easily. My battery drained relatively quickly, and the issue didn't repeat when I tried booting again.
Hi XDA developers community,
Using some of the guides on this fantastic website I flashed LineageOS on my A2017G a few months ago. Now I tried reverting back to stock by flashing the B03 Oreo zip file in EDL mode (this guide).
The first reboot was already successful: I powered the phone on via the power button, then went through "can't be checked for corruption" screen, then got into the screen with Tux (Linux penguin), pressed volume up to go to recovery just to be sure, and rebooted from there into Android.
Although instead of starting the setup process Android dropped my right into the lock screen. I assumed that was because I hadn't factory reset yet and my data partition still had garbage data (that was step 18 of the guide btw). So, I powered off, from Android, and tried booting into recovery mode again to do the factory reset. However, now, after the Android corruption warning screen, the Linux Tux screen just stays there. Recovery mode doesn't appear, neither did it boot into Android. I can't even force power off by pressing the button (I pressed 80 seconds straight, no effect). No combination of volume and power buttons does anything, even pressing and holding it.
Right now I plan to let the battery drain on its own to get the device to power off. That's probably gonna take some days because the battery is completely charged. Is there some other possibility to make it go faster? Maybe heat the battery up from the outside with a hair dryer? I would rather not open the phone up and take the battery out, because I don't have a heat gun and I'm also worried I'm gonna leave scratch marks or something (the process seems quite rough).
And also, when the battery is drained, is there any recommendation on what I should do? Simply try again, going into recovery mode? Flash the EDL file again?
Thank you for reading all this, and I'd be so glad for any help.
Click to expand...
Click to collapse
My phone is like u "zte axon 7 a2017g " version oreo b03 please tell me the guide that u used to install lineage os and the tools please !!!
i just want to install unloack my bootloader , flash twrp , install lineage os so on ; please give me just the guide that u use !
afef said:
My phone is like u "zte axon 7 a2017g " version oreo b03 please tell me the guide that u used to install lineage os and the tools please !!!
i just want to install unloack my bootloader , flash twrp , install lineage os so on ; please give me just the guide that u use !
Click to expand...
Click to collapse
Sorry, I don't remember
kangalioo said:
Sorry, I don't remember
Click to expand...
Click to collapse
u don't remember if the guide is for marshmallow or naugat a 2017 g or i can use guide for a2017 u !
afef said:
u don't remember if the guide is for marshmallow or naugat a 2017 g or i can use guide for a2017 u !
Click to expand...
Click to collapse
what
kangalioo said:
EDIT: Thankfully I could resolve this issue on my own fairly easily. My battery drained relatively quickly, and the issue didn't repeat when I tried booting again.
Click to expand...
Click to collapse
Mine didn’t reboot at all after completely draining the battery several times. Same result, blocked on penguin screen, no way to get into a menu to flash anything ?
kangalioo said:
what
Click to expand...
Click to collapse
My phone is "zte axon 7 a2017g" version oreo b03 , i want to find guide make me unloack bootloader , flash twrp , install lineage os ; i just want for if u can remember if what can proch me i can use because the only guides exist are for a2017u or a 2017 g marshmallow or naugat
or if u can tell me if i can downgrading from oreo to marshmallow without unloack bootloader to use the guide exist for marshmallow !
afef said:
My phone is "zte axon 7 a2017g" version oreo b03 , i want to find guide make me unloack bootloader , flash twrp , install lineage os ; i just want for if u can remember if what can proch me i can use because the only guides exist are for a2017u or a 2017 g marshmallow or naugat
or if u can tell me if i can downgrading from oreo to marshmallow without unloack bootloader to use the guide exist for marshmallow !
Click to expand...
Click to collapse
As I said, I don't remember. I'm using a different phone altogether since half a year.
So because only a Tux logo appeared on the screen, my guess as to what happened is that while the Android Bootloader, also called "aboot" was booting the Linux kernel that Android runs off of, before the kernel could display the splash screen that appears when you power on the device, it encountered a critical error that either aborted the boot process, or caused the kernel to go into a kernel panic. Now as to why it displayed the Tux logo, it probably did that because when it crashed, it tried mapping the framebuffer to the display instead of keeping in hidden by default to show you the kernel buffer logs for you to troubleshoot the problem but instead, it shows the iconic Linux penguin that is usually hidden when the kernel boots.
So, i have dusted off my old Z2 tablet, and wanted to update it to LineageOS 15.1. iam following the guide on Cyoanomods site. (Cant link, since i am a new member)
I have "rooted" it with sonys own guide. No problem there.
I have installed the ADB and fastboot on my pc. Can connect to it no problem.
Boot to bootloader via ADB no problem. Then i try to flash TWRP to recovery , it says OKAY to both sending and writing.
But the device just boots as normal, no matter if i use the reboot recovery command or by using the devices buttons. Just a standard recovery seems to happen.
The only strange thing i can think of is that the flash goes fairly fast, both tasks finishes in 1.6 seconds. Dont know if that is normal.
Tried to search around almost all day, but nothing gets any clearer. Found something that TRWP may not even work on the xperia units since it uses some other kind of boot partition.
Any ideas?
hi possla,
I have also just brought my Z2 tablet out of the sink and now I want to flash it with LineageOS 15.1. First, a question, do you have a current link to LOS15.1 for me?
Apart from that, I still remembered my fights with the tablet a few years ago, I flashed TWRP for backups, but when I flashed a new system it did not work with TWRP, so I have the CWM recovery 6.0.4.6 (Touch) on that Flashed tablet, so it worked fine, just try it.
If you had a LOS15.1 link for me it would be great, thanks in advance!
Greeting Torsten
Z2 tablet
possla said:
So, i have dusted off my old Z2 tablet, and wanted to update it to LineageOS 15.1. iam following the guide on Cyoanomods site. (Cant link, since i am a new member)
I have "rooted" it with sonys own guide. No problem there.
I have installed the ADB and fastboot on my pc. Can connect to it no problem.
Boot to bootloader via ADB no problem. Then i try to flash TWRP to recovery , it says OKAY to both sending and writing.
But the device just boots as normal, no matter if i use the reboot recovery command or by using the devices buttons. Just a standard recovery seems to happen.
The only strange thing i can think of is that the flash goes fairly fast, both tasks finishes in 1.6 seconds. Dont know if that is normal.
Tried to search around almost all day, but nothing gets any clearer. Found something that TRWP may not even work on the xperia units since it uses some other kind of boot partition.
Any ideas?
Click to expand...
Click to collapse
Same problem for the past 2 years
Shut the device down. Switch it on. Wait until the led turns green. Now hit a volume button several times
Hi, i don't know if other thread's members encounter the same problem, but for me there is no light during boot form the device. Maybe it's only on this device but i can't get the solid green light during ADB mode. In this case i'm unable to enter Recovery Mode too after flash several times ...
Hello, any help would be appreciated as I have seemed to have gotten Myself stuck on the screen that warns Me about the bootloader being unlocked. I hope this is in the right section of the forum.
So I have enabled at least 10 Magisk Modules at the same time, carefully read the files attached to them within the app, tried to make sure they didn't do too much to the system where I'd have to worry about this sort of thing happening but of course, with My luck, it did anyway. I plugged My device into My laptop to try to just flash the magisk_patched.img and it just brought Me back to the same screen, sometimes it would reboot itself several times before stopping when plugged in to My laptop. I've read somewhere that the Miracast module might be the culprit so I sought to enter TWRP through fastboot and delete the module BUT IT'S NOWHERE TO BE FOUND. I have also tried all these button combinations I kept seeing people talk about on various forums, like pressing all 3, Power+Volume Up, etc and holding them for various amounts of time and none of this has gotten Me past the warning screen. I seen something about uninmod but I've heard that this doesn't work on v.19+ and I can't seem to even find the magisk folder anywhere at all to begin with. I couldn't backup My phone because Google kept saying "waiting to backup" so I'm screwed if I have to just restart and hope it doesn't have to come to that.
My questions are:
Is there any folders I may be missing?
Is there any way to backup My device through TWRP or fastboot now even though TWRP won't mount and I can't boot into the OS?
Is there a way to delete Magisk or the modules that I can try, that I haven't mentioned/don't know about?
Thanks in advance!
Sorry didn't see this until today. Did you end up giving up and starting over with a clean flash or still having issues?
Hw4ng3r said:
Sorry didn't see this until today. Did you end up giving up and starting over with a clean flash or still having issues?
Click to expand...
Click to collapse
It's all good. No I wasn't going to mess with it until I done enough research or someone had replied and I had the time. I was thinking about doing something today or this weekend. I read some things online that I bookmarked about using the "pull" command on ADB, being able to save the image from TWRP after using the fastboot command to boot into TWRP, and I seen some other post on XDA about a certain method they used to stop bootloops. Even though I don't have bootloops, I'm just stuck, maybe it'll be helpful information. At this point though I'm wondering if I even want to save anything, like will restoring it have Me stuck right back on the same screen? I'm sure I did something wrong because I have none of My old phones app DATA, and I think I thought the Google Backup or OnePlus Switch App was going to put the whole APK on My phone (which I don't want) or the data only, which is what I want. Any help would be appreciated because someone is trying to buy this S10+ but I'm still using it.
First questions: what phone are you trying to fix, s10+ or 7T Pro McLaren?
Second: If you answered 7T Pro McLaren, what mode (recovery, fastboot, etc) can you get into?
I'm trying to get off the Root Warning Screen for the 7T Pro McLaren. I can get into fastboot, recovery mode, and TWRP via fastboot command.
iAMe100XP said:
I'm trying to get off the Root Warning Screen for the 7T Pro McLaren. I can get into fastboot, recovery mode, and TWRP via fastboot command.
Click to expand...
Click to collapse
Are you referring to the bootloader unlocked warning? The only way to get that off is to relock the bootloader (will lose personal data when you do this).
Hw4ng3r said:
Are you referring to the bootloader unlocked warning? The only way to get that off is to relock the bootloader (will lose personal data when you do this).
Click to expand...
Click to collapse
I don't want to lock the bootloader or care to get rid of the warning atm. I just can't get past the screen and into the OS. There is possibly a Magisk module I flashed but I can't find the Magisk folder or the modules in TWRP via Fastboot.
iAMe100XP said:
I don't want to lock the bootloader or care to get rid of the warning atm. I just can't get past the screen and into the OS. There is possibly a Magisk module I flashed but I can't find the Magisk folder or the modules in TWRP via Fastboot.
Click to expand...
Click to collapse
Ah. You won't be able to access the Magisk folder in TWRP because TWRP can't decrypt the storage partition on the 7T pros.
One way you can try is by booting your stock boot.img from fastboot using
Code:
fastboot boot boot.img
Just make sure that the boot.img you're using is from the exact version of OOS you are currently running. This should boot the OS without Magisk/root.
The other method (source) is to place your phone into safe mode, then reboot normally, and it's supposed to boot up with all magisk modules disabled.
To put your phone into safe mode:
Make sure your phone is completely turned off
1. Press and hold power button to turn on device
2. As soon as 1+ logo pops up, release power button and press and hold volume down button until device finishes booting up. (Just hold through the bootloader unlocked screen and through the startup animations).
I just tested this on my 7T Pro (non mclaren) and it first booted into safe mode, then when I did a standard reboot via power button then selecting reboot, it started back up in "normal mode" with all magisk modules disabled.
That "source" link is from the Magisk github and has a "manual disable/uninstall of all modules" method using adb as well.
Hw4ng3r said:
Ah. You won't be able to access the Magisk folder in TWRP because TWRP can't decrypt the storage partition on the 7T pros.
One way you can try is by booting your stock boot.img from fastboot using
Code:
fastboot boot boot.img
Just make sure that the boot.img you're using is from the exact version of OOS you are currently running. This should boot the OS without Magisk/root.
The other method (source) is to place your phone into safe mode, then reboot normally, and it's supposed to boot up with all magisk modules disabled.
To put your phone into safe mode:
Make sure your phone is completely turned off
1. Press and hold power button to turn on device
2. As soon as 1+ logo pops up, release power button and press and hold volume down button until device finishes booting up. (Just hold through the bootloader unlocked screen and through the startup animations).
I just tested this on my 7T Pro (non mclaren) and it first booted into safe mode, then when I did a standard reboot via power button then selecting reboot, it started back up in "normal mode" with all magisk modules disabled.
That "source" link is from the Magisk github and has a "manual disable/uninstall of all modules" method using adb as well.
Click to expand...
Click to collapse
OK, I will check these things out and report back. I believe I flashed TWRP and the patched Magisk image but maybe I didn't do the original boot image. The problem with the one suggestion is I don't see a 1+ image at all, it just stays on the warning screen forever. I do have advanced boot or whatever turned on I believe where it gives Me more options when holding the power button, provided I can get into the OS but that's not the case. I will try to just hold the volume down when I see the warning screen.
Correction: I see a 1+ logo but no matter what I did, any button combination or booting in with the power button after getting into Safe mode, none of these things did anything but bring Me to the same screen...
Hw4ng3r said:
Ah. You won't be able to access the Magisk folder in TWRP because TWRP can't decrypt the storage partition on the 7T pros.
One way you can try is by booting your stock boot.img from fastboot using
Code:
fastboot boot boot.img
Just make sure that the boot.img you're using is from the exact version of OOS you are currently running. This should boot the OS without Magisk/root.
The other method (source) is to place your phone into safe mode, then reboot normally, and it's supposed to boot up with all magisk modules disabled.
To put your phone into safe mode:
Make sure your phone is completely turned off
1. Press and hold power button to turn on device
2. As soon as 1+ logo pops up, release power button and press and hold volume down button until device finishes booting up. (Just hold through the bootloader unlocked screen and through the startup animations).
I just tested this on my 7T Pro (non mclaren) and it first booted into safe mode, then when I did a standard reboot via power button then selecting reboot, it started back up in "normal mode" with all magisk modules disabled.
That "source" link is from the Magisk github and has a "manual disable/uninstall of all modules" method using adb as well.
Click to expand...
Click to collapse
Jesus Christ! All I had to do was use the original boot image and push it using fastboot? Omg. I'm in My phone now lol. I can't believe it was that simple. I'm sure I original I didn't do this because I thought that it would erase everything or do something dire but apparently everything is still here... wow. Thanks man, I really appreciate it! Now do I re-boot the Magisk patched image through fastboot or do I uninstall modules first or what?
iAMe100XP said:
Jesus Christ! All I had to do was use the original boot image and push it using fastboot? Omg. I'm in My phone now lol. I can't believe it was that simple. I'm sure I original I didn't do this because I thought that it would erase everything or do something dire but apparently everything is still here... wow. Thanks man, I really appreciate it! Now do I re-boot the Magisk patched image through fastboot or do I uninstall modules first or what?
Click to expand...
Click to collapse
I've never ran into any Magisk issues before so I don't know what to tell you from this point on. I'd like to say that you can probably go into Magisk manager and disable/delete your modules, but I don't know enough about the inner workings of Magisk.
You should probably back up all your data at this stage before you do anything further lol
Hw4ng3r said:
I've never ran into any Magisk issues before so I don't know what to tell you from this point on. I'd like to say that you can probably go into Magisk manager and disable/delete your modules, but I don't know enough about the inner workings of Magisk.
You should probably back up all your data at this stage before you do anything further lol
Click to expand...
Click to collapse
Will do, thanks. Do you know if OnePlus Switch transfers APKs or Data? I just want the data and I already used it from My S10+ and wonder if it will be confused by files that already exist or create duplicates. What's the best way to back up if Google keeps saying it's waiting to backup.
iAMe100XP said:
Will do, thanks. Do you know if OnePlus Switch transfers APKs or Data? I just want the data and I already used it from My S10+ and wonder if it will be confused by files that already exist or create duplicates. What's the best way to back up if Google keeps saying it's waiting to backup.
Click to expand...
Click to collapse
I'm not sure about 1+ Switch since I've never used it before.
Check this post for an app others have used.
Hw4ng3r said:
I'm not sure about 1+ Switch since I've never used it before.
Check this post for an app others have used.
Click to expand...
Click to collapse
Don't mean to revive this post at random but I've been really busy lately. I just wanted to update:
I could only turn the phone on by Fastboot and I didn't have much on the phone so I just wiped the device but your help definitely let Me get into the OS and back/upload/see if there was anything I wanted or needed so I really appreciate it. I'll definitely donate when I can, I'm grateful for your help!
iAMe100XP said:
Don't mean to revive this post at random but I've been really busy lately. I just wanted to update:
I could only turn the phone on by Fastboot and I didn't have much on the phone so I just wiped the device but your help definitely let Me get into the OS and back/upload/see if there was anything I wanted or needed so I really appreciate it. I'll definitely donate when I can, I'm grateful for your help!
Click to expand...
Click to collapse
It's great that you posted the final result. Not enough people do this IMO.
Sorry some of the suggestions didn't really work out, but at least you could get back into the phone without complete loss of data.
No need for donations; I'm just an enthusiast/ordinary user wanting to help!