Related
I'm desparate, please help!!!!
I had to do a hard reset after failing to Root my A500, that's a long story.
After the Hard Reset it has come up with a APKInstaller (All pre-install processes complete). I click OK and then it has asked me to enter your password (with the Android logo on the left had side.
I have tried all the passwords I can think of, including my Gmail password, and it just says that it is wrong.
Can someone please put me out of my misery and help????
Feel free to mock me, as long as you come up with a solution that doesnt involve taking the device back to get fixed.
Thanks in advanced
had this happened before when i tried to do the factory reset through the method of HOLDING DOWN POWER + RIGHT VOLUME BUTTON (in landscape mode) + SWITCHING THE ROTATION LOCK BUTTON. easy solution to this would perform the factory reset one more time and it'll go away
Having this issue too..
Ok.. simplified version of long (2-wk) history:
1) Initially 3.0.1 device "bricked" attempting to do a direct 3.0.1 to 3.2.1 update.. bad move and stupid of me.
2) Successfully unbricked using EUUs_SBK_Acer_A500_1.016.05_COM_GEN1
3) 3.0.1 rooted, custom recovery, and updated to a 3.2.1 stock with root.. and stable for about 5 days.
4) I installed ES Task Manager and played with some settings. Shut down the device for the day (early afternoon).
5) Restarted device, boot, and was asked for a Password. -- One that I never set. None of the account (google) passwords that were on the device worked.
6) Being still somewhat fresh, I did the "unbrick" flash again and proceeded with root, recovery, and update again... stable for about 3 days.. before the Password prompt returned.
I'm now at the state that I've attempted multiple ROMs.. there is *something* not getting wiped. Now, even when I use the EUU "unbrick", the first boot is fine.. as soon as I restart though, Password.
Massive frustration.. but I'm hoping someone here might be of some help on this.
I figure the worst case.. I literally break the thing and have to use my "accident" warranty.. but I'd really rather not do that.
Any ideas?
MoonHowler said:
Ok.. simplified version of long (2-wk) history:
1) Initially 3.0.1 device "bricked" attempting to do a direct 3.0.1 to 3.2.1 update.. bad move and stupid of me.
2) Successfully unbricked using EUUs_SBK_Acer_A500_1.016.05_COM_GEN1
3) 3.0.1 rooted, custom recovery, and updated to a 3.2.1 stock with root.. and stable for about 5 days.
4) I installed ES Task Manager and played with some settings. Shut down the device for the day (early afternoon).
5) Restarted device, boot, and was asked for a Password. -- One that I never set. None of the account (google) passwords that were on the device worked.
6) Being still somewhat fresh, I did the "unbrick" flash again and proceeded with root, recovery, and update again... stable for about 3 days.. before the Password prompt returned.
I'm now at the state that I've attempted multiple ROMs.. there is *something* not getting wiped. Now, even when I use the EUU "unbrick", the first boot is fine.. as soon as I restart though, Password.
Massive frustration.. but I'm hoping someone here might be of some help on this.
I figure the worst case.. I literally break the thing and have to use my "accident" warranty.. but I'd really rather not do that.
Any ideas?
Click to expand...
Click to collapse
Do a clean flash directly to 3.2.1 rooted. Then don't install anything for a few days and see if your problem is gone. It should be fixed.
I've never had any problems like yours. I always use CWM to do full WIPES + FORMATS. I have used windows Directly to do about 3-4 Flashes that way. About 20-30 Flashed ROM's thru CWM Recovery (20-30 -not ever cuz of problems).
Best i can say is Next Time do it THRU CWM Recovery and WIPE (3) + FORMAT (4) = 7 commands to say "YES" to before Installing a CUSTOM ROM. I've messed arround a lot and have hard time BRICKING or having any messed up ROM INSTALLS.
amateurandroid said:
I'm desparate, please help!!!!
I had to do a hard reset after failing to Root my A500, that's a long story.
After the Hard Reset it has come up with a APKInstaller (All pre-install processes complete). I click OK and then it has asked me to enter your password (with the Android logo on the left had side.
I have tried all the passwords I can think of, including my Gmail password, and it just says that it is wrong.
Can someone please put me out of my misery and help????
Feel free to mock me, as long as you come up with a solution that doesnt involve taking the device back to get fixed.
Thanks in advanced
Click to expand...
Click to collapse
No problem, but, I have to "mock" you a little Because in over 350+ flashings for testings, etc, I have never had this happen, nor have I ever had to use the "pinhole" (knock on wood)
And that "password".... hint, there is no password that will work. The issue, is that you have a big mess internally when booting, and the OS doesn't know what else to do, so it gives you that dialog.
And you're not the first person to have this happen to.
My question, is WTH did you do to get yourself into this mess? And the reason I ask, is that others have done the same thing. So perhaps it would be best to give the "Long Story". This may be useful to others and serve as a reference point.
TimmyDean has a tool for unbricking devices. From what I've seen, it works well 90% of the time. So you should listen to him. There's also one other unbrick master, but haven't seen him around for awhile.
I have been running CM (currently CM11) on my SGS4 since I bought it from Sprint in summer 2013. However, Sprint changed their international partners pretty seriously in the past 2 years, so I *really* need a PRL update for international travel. Normally the easiest way to do this is to reboot to stock or TriForce, run the "update PRL" and "update Profile" options from in TriForce, and go on with my life.
But I encrypt my phone. So I had to boot into TWRP, wipe and format *everything* and make sure the phone came up unencrypted in CM. All is OK.
So I reboot, flash TriForce 5.4 custom with stock (not KK) kernel. Flash works fine, I reboot... and am prompted to decrypt the device before I can do anything. None of the decryption passwords I've used in the past (I checked my password safe) are working. When I flash back to CM, it boots fine, and the settings says that the device is not encrypted.
I downloaded and tried TriForce 5.2 and 4.0, both are giving the same problem. I have used TriForce in the past on this phone, so it SHOULD be fine....?
Someone in #twrp said that the location of the encryption key changed from Android 4.4 to 5.0. So my only remaining thought now is that there was also a change from 4.3 to 4.4, and the encryption key for 4.3 didn't get removed in the wipe, and since the partition is NOT encrypted, the decryption, even if I have the right key, fails, so I can't get into the phone. Hope that makes sense.
Anyone have any guess better, or, if I'm right, know what I need to move/edit to fix this?
Followup: IRC #sgs4 suggested a full install of stock via odin, so I'll be trying that on Saturday, after I can get a new stock rom downloaded overnight. if there are thoughts before then, I'd love 'em.
docsmooth said:
Followup: IRC #sgs4 suggested a full install of stock via odin, so I'll be trying that on Saturday, after I can get a new stock rom downloaded overnight. if there are thoughts before then, I'd love 'em.
Click to expand...
Click to collapse
Followup - this was never solved before I dropped the phone and shattered the screen (literally days after this post). So if someone runs into the same thing... good luck.
docsmooth said:
Followup - this was never solved before I dropped the phone and shattered the screen (literally days after this post). So if someone runs into the same thing... good luck.
Click to expand...
Click to collapse
Thanks for the update, I was actually going to suggest stock ODIN instead of TriForce, but you are saying it did not work ? It's good to know for the future. I was initially going to encrypt my phone a long time ago, but I had concerns about decryption when switching ROMs.
My question is why the encryption was not removed after the format ? I've used TWRP to pretty much hose out everything inside the phone, so it's possible the encryption location is located somewhere else. I came across this article:
http://money.cnn.com/2015/05/21/technology/resell-android-phone/
So I guess even after a complete wipe everything ISN'T removed. Maybe your encryption was also stuck as well.................................... What new phone are you getting ?...................................
mikeprius said:
Thanks for the update, I was actually going to suggest stock ODIN instead of TriForce, but you are saying it did not work ? It's good to know for the future. I was initially going to encrypt my phone a long time ago, but I had concerns about decryption when switching ROMs.
My question is why the encryption was not removed after the format ? I've used TWRP to pretty much hose out everything inside the phone, so it's possible the encryption location is located somewhere else. I came across this article:
So I guess even after a complete wipe everything ISN'T removed. Maybe your encryption was also stuck as well.................................... What new phone are you getting ?...................................
Click to expand...
Click to collapse
I was never able to get the stock odin download. The whole problem came up because I was going overseas... I got around it by just buying a local SIM rather than using the Sprint roaming (again, I was doing all this just to update the PRL. new GSM SIM = no PRL update needed). On the way home less than a week later, I cracked the screen so bad the LCD and backlight wouldn't even go on.
I replaced it with a Nexus 6. A bit big, but it doesn't suffer Samsung software awfulness, so I didn't have to flash it with CM to make it usable.
So I have android nougat [rooted] but when I reboot or turn Wi-Fi off then back on it doesn't have my Wi-Fi networks saved. I have already set ro.securestorage.support to false and it still will not work. Have a screwed something up? I just installed this a few days ago..
CreeperPVP said:
So I have android nougat [rooted] but when I reboot or turn Wi-Fi off then back on it doesn't have my Wi-Fi networks saved. I have already set ro.securestorage.support to false and it still will not work. Have a screwed something up? I just installed this a few days ago..
Click to expand...
Click to collapse
It is a known bug with the eng root method, i can't remember the fix. Search the root thread and you'll probably find it
Part 3 is what you're looking for.
https://forum.xda-developers.com/ve...de-flashing-sm-935u-firmware-verizon-t3415145
I know my replies can be long, but would rather give too much info, than not enough.
OK so it's all fixed but now i get 3 reboots before i even get into the system.. Any pointers?
CreeperPVP said:
OK so it's all fixed but now i get 3 reboots before i even get into the system.. Any pointers?
Click to expand...
Click to collapse
Not sure if it'll work on stock rooted but on some roms you need to boot into recovery, wipe system/data, once rebooted and set up run the latest supersu root.bat. i belive the latest version is 2.79.
dirtydodge said:
Not sure if it'll work on stock rooted but on some roms you need to boot into recovery, wipe system/data, once rebooted and set up run the latest supersu root.bat. i belive the latest version is 2.79.
Click to expand...
Click to collapse
I figured out what the rebooting was from. What happened was 'master.sh' was rebooting after the sh files did their jobs, but i guess one of them wasn't doing it's job so it kept rebooting. The 'master.sh' file has a 'failsafe' where if it reboots 3 times (defined by 'reboot.count') it will cancel the reboot. I thought it was just some issue with 7.0, but while it very well could've been, i flashed the stock AP again but this time put the engboot in CP and it fixed itself after i reinstalled su.img essentially.. Can't imagine how Android 8.0 would react to EngBoot and su..
2 days ago, for no apparent reason, my phone suddenly became extremely slow. I rebooted it, and it was fine for a few minutes, then it became slow again. I was running stock 8.1 rooted. I uninstalled any recently installed apps, and ran a virus scan. The thing that seemed really odd to me was that the boot animation was slow. I wiped the phone and installed LineageOS, which was not any faster. I have now wiped and installed the latest factory image, downloaded from essential's website, and it is still so slow as to be unusable. Anybody have any thoughts on this? I purchased the phone on prime day 2018, so it's like 3 months past it's warranty.
Well, @thesomnambulist after using speed reading techniques to carefully read that foreign policy and about 12.2 seconds there Ali I immediately inclined to tell you that your phone is not bricked. Message me.
thesomnambulist said:
2 days ago, for no apparent reason, my phone suddenly became extremely slow. I rebooted it, and it was fine for a few minutes, then it became slow again. I was running stock 8.1 rooted. I uninstalled any recently installed apps, and ran a virus scan. The thing that seemed really odd to me was that the boot animation was slow. I wiped the phone and installed LineageOS, which was not any faster. I have now wiped and installed the latest factory image, downloaded from essential's website, and it is still so slow as to be unusable. Anybody have any thoughts on this? I purchased the phone on prime day 2018, so it's like 3 months past it's warranty.
Click to expand...
Click to collapse
Did you get the Essential resources & services updates last week via Google? Several people on the news forum threads related to the Android 10 update have also experienced very slow phones. Could it be related? Eg conflict with another app or the network you are connected to etc?
Though yours could be hardware issue.
At the time it happened, I was on 8.1, and not taking any updates. I'm leaning towards a a hardware issue since it persisted past a wipe and re-image on stock Android 8.1, Lineage OS 16.0, and stock Android 10.
I've been getting slowdowns with my essential since Android 10 update. I'm also rooted with Magisk and did the updates with the momentary restoring of stock image, then OTA with patching the OTA partition prior to reboot method (Magisk OTA method).
I keep thinking it's the Nova beta launcher slowing me down. But I did get the slowdown once with QuickStep 10 launcher. It's mostly been Nova beta updates; 6.2.2 update seemed much better for just a day and started slowing until I just couldn't launch any apps again. Weird! Reboot and switch home default again.
I haven't been aggressive with wiping user data or trying other Android versions. I did freeze a few apps with no significant result. Currently, I'm hoping things are stable and fast with the stock launcher. That's only been since last night though.
I mentioned this in one of the Android 10 threads but not getting much feedback there. I've sent txt files to Nova development through the Nova beta app but got no response yet.
And I have diagnostics sharing disabled for essential and Nova. Thinking about reenabling those.
Sent from my PH-1 using Tapatalk
samep said:
I've been getting slowdowns with my essential since Android 10 update. I'm also rooted with Magisk and did the updates with the momentary restoring of stock image, then OTA with patching the OTA partition prior to reboot method (Magisk OTA method).
I keep thinking it's the Nova beta launcher slowing me down. But I did get the slowdown once with QuickStep 10 launcher. It's mostly been Nova beta updates; 6.2.2 update seemed much better for just a day and started slowing until I just couldn't launch any apps again. Weird! Reboot and switch home default again.
I haven't been aggressive with wiping user data or trying other Android versions. I did freeze a few apps with no significant result. Currently, I'm hoping things are stable and fast with the stock launcher. That's only been since last night though.
I mentioned this in one of the Android 10 threads but not getting much feedback there. I've sent txt files to Nova development through the Nova beta app but got no response yet.
And I have diagnostics sharing disabled for essential and Nova. Thinking about reenabling those.
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
Magisk 19.3 or canary? 19.3 doesn't play well with Android 10. If you are on 19.3, Update to canary or Banks version:
https://forum.xda-developers.com/showthread.php?p=80249962
Sent from my PH-1 using Tapatalk
freshlysqueezed said:
Magisk 19.3 or canary? 19.3 doesn't play well with Android 10. If you are on 19.3, Update to canary or Banks version:
https://forum.xda-developers.com/showthread.php?p=80249962
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
Magisk 19.3 carried over from Pie is what I'm using.
Doesn't play nice, how? I've not lost root but the slowness I've experienced seems to be with Nova beta launcher.
Thanks in advance. I'm looking for clarification is all. I have read what you're saying elsewhere but not understanding the issue.
Also I see that Banks doesn't support OTA; right there in your link. Does Canary? Not sure how to switch either? I was even considering no root for a while but steady so far with QuickStep 10 launcher. If I give it minimum of two days without the slowdown, I may just leave it as is longer to see if I'm the clear with the slowness. But I can read up on the Magisk issues in the meanwhile too.
I have a good ad blocker; it didn't require root. The things I'm patching seem to be things to just have root. I've ran out ideas for root I guess. I haven't had gravity box since nougat. Stock ROM and kernel and a desire to update security patches quickly without having to plug in is where I've been since finally abandoning nougat.
I even had a banking app tell me to disable developer options to securely sign in. I uninstalled the app and went online to sign in. Unlocks were done in adb so disabling developer mode and rebooting shouldn't lock them back down, should it? It just concerns me because oem unlock is in developer settings. I see Essential phone bricks in these threads so I'm not going to forcibly lock my bootloader. I'd rather avoid things that may jeopardize my phone. And I'd rather wait another year before upgrading.
Sent from my PH-1 using Tapatalk
samep said:
Magisk 19.3 carried over from Pie is what I'm using.
Doesn't play nice, how? I've not lost root but the slowness I've experienced seems to be with Nova beta launcher.
Thanks in advance. I'm looking for clarification is all. I have read what you're saying elsewhere but not understanding the issue.
Also I see that Banks doesn't support OTA; right there in your link. Does Canary? Not sure how to switch either? I was even considering no root for a while but steady so far with QuickStep 10 launcher. If I give it minimum of two days without the slowdown, I may just leave it as is longer to see if I'm the clear with the slowness. But I can read up on the Magisk issues in the meanwhile too.
I have a good ad blocker; it didn't require root. The things I'm patching seem to be things to just have root. I've ran out ideas for root I guess. I haven't had gravity box since nougat. Stock ROM and kernel and a desire to update security patches quickly without having to plug in is where I've been since finally abandoning nougat.
I even had a banking app tell me to disable developer options to securely sign in. I uninstalled the app and went online to sign in. Unlocks were done in adb so disabling developer mode and rebooting shouldn't lock them back down, should it? It just concerns me because oem unlock is in developer settings. I see Essential phone bricks in these threads so I'm not going to forcibly lock my bootloader. I'd rather avoid things that may jeopardize my phone. And I'd rather wait another year before upgrading.
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
I would suggest no root then.
Sent from my PH-1 using Tapatalk
That's interesting, as I was initially rooted with Magisk as well, using Novo launcher. I'm not sure either of those are related to my issue though, since I've installed LineageOS without root or Novo launcher as well as stock Android 10 without root or Novo launcher, and the problem has persisted with all of them. Essential support has been absolutely no help, and as much as I liked this phone, I will not be doing business with them again simply because of their attitude in responding to me. That being said, I think I'm going to try to wipe everything manually, and go through the flashing process one partition at a time, and see if I can get anything working.
Just as an update, I've gone back and flashed stock android 8.1. The only errors I'm seeing in flashing this is when I go to format the userdata partition, I get the following:
sudo fastboot format userdata
Couldn't parse erase-block-size '0x'.
Couldn't parse logical-block-size '0x'.
mke2fs 1.44.1 (24-Mar-2018)
/tmp/TemporaryFile-snLbLs: Unimplemented ext2 library function while setting up superblock
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata
Click to expand...
Click to collapse
I've gone into the stock recovery and wiped/factory reset the partitions there, which I believe does the same thing, and it still is running so slow as to be entirely unusable.
At this point, I'm about to call it dead, but I'm open to any suggestions anyone might have.
thesomnambulist said:
Just as an update, I've gone back and flashed stock android 8.1. The only errors I'm seeing in flashing this is when I go to format the userdata partition, I get the following:
I've gone into the stock recovery and wiped/factory reset the partitions there, which I believe does the same thing, and it still is running so slow as to be entirely unusable.
At this point, I'm about to call it dead, but I'm open to any suggestions anyone might have.
Click to expand...
Click to collapse
Didn't the bootloader change in Android 10? I've seen partitions change with bootloaders but bootloaders aren't downgradeable for security reasons. Maybe that's ok but wiping partitions in another Android version may throw those errors?
Maybe our problems were similar with Android 10? I was using Magisk 19.3 and waited it out for 19.4 but I likely should have been on Canary build or switched immediately to Magisk 19.4 Slowdown with Nova until I couldn't launch apps anymore. With QuickStep 10, I only got to the point that I couldn't launch apps. Either case, reboot was a temporary fix that would restore UI speed.
I eventually realized I couldn't update BusyBox module with Magisk 19.3 so I updated to 19.4 through beta channel. Besides, I was having a similar issues getting to a point that I couldn't launch apps and having to reboot even with the QuickStep 10 launcher. BusyBox module updated without issue after Magisk beta update.
I'm hoping other issues may be resolved. I know I read many were using Canary build for across Android Q beta builds.
I'm just getting started with Magisk 19.4 so I may have more to add later. In your case, have you Android 10 again and see if the recovery wipes are still returning errors? If my phone doesn't improve, I may be upgrading sooner than expected. But there is a spare unlocked Essential PH-1 on my account now.
Sent from my PH-1 using Tapatalk
samep said:
Didn't the bootloader change in Android 10? I've seen partitions change with bootloaders but bootloaders aren't downgradeable for security reasons.
Click to expand...
Click to collapse
That's a good question. I don't think this is the case, as part of my flashing process was to flash the bootloader (for 8.1) to both slot_a and slot_b, neither of which had any errors. I believe this means that I successfully downgraded to the older bootloader (assuming that it changed in 10). I know very little about filesystems, but the error message I'm getting appears to be some kind of conflict between ext2 and f2fs. At one point in this process, I know I formatted the partitions in TWRP, and I wonder if that formatted the userdata partition with the wrong filesystem. All of that being said, I have my doubts about whether the slowness is at all related to the userdata partition, as a reboot does nothing to help. The thing that really makes me think it's not software related is that the boot animation is extremely slow, and has been regardless of what rom I have installed.
@thesomnambulist, Are you confusing the boot.img with the bootloader?
ktmom said:
@thesomnambulist, Are you confusing the boot.img with the bootloader?
Click to expand...
Click to collapse
I might be. I guess I always assumed that the boot.img was the bootloader. Please educate me.
thesomnambulist said:
I might be. I guess I always assumed that the boot.img was the bootloader. Please educate me.
Click to expand...
Click to collapse
The boot.img is also referred to as the kernel. This is the central control center for an actively booted OS (or ROM).
The bootloader is the initial bit of firmware that manages the startup up from the power off state. You go through the bootloader to get to recovery or to the system/OS/ROM.
https://forum.xda-developers.com/wiki/Bootloader
https://forum.xda-developers.com/wiki/ROM-VS-Kernel
ktmom said:
The boot.img is also referred to as the kernel. This is the central control center for an actively booted OS (or ROM).
The bootloader is the initial bit of firmware that manages the startup up from the power off state. You go through the bootloader to get to recovery or to the system/OS/ROM.
https://forum.xda-developers.com/wiki/Bootloader
https://forum.xda-developers.com/wiki/ROM-VS-Kernel
Click to expand...
Click to collapse
Awesome! Thanks for that clarification. I'm not new to Android, but I have a lot to learn!
It's been more than 2 days since upgrading Magisk to 19.4 beta on Android 10 for me.
No slowdowns or freezes. Magisk Log appears error free since update but date changed from 09-24 to 10-29? Maybe not a MM-DD date?
The last error only showed the apps I was last running before it wouldn't launch another app. But did note: beginning of crash...
Anyway, my data was kept from the OTA update from Pie to Android 10, including Magisk 19.3 until beta update. Only issue appeared to be the need to update Magisk through beta channel or switch to Canary. I said I'd have more to say later.
Next step is to switch back to Nova beta launcher and see if that remains fluid and doesn't bring back any slowness I was experiencing before the crashes. Hopefully no slowness and crashes have ceased.
Sent from my PH-1 using Tapatalk
new screen
the screen itself is likely the issue. just fixed my brothers ph-1 that started taking minutes to do anything with a new screen. hopefully this helps.
blap017 said:
the screen itself is likely the issue. just fixed my brothers ph-1 that started taking minutes to do anything with a new screen. hopefully this helps.
Click to expand...
Click to collapse
I'm not thinking my issue was the display but using the wrong Magisk version for Android 10. This issues weren't present in Pie.
Initially I did suspect Nova launcher because the app switcher was slow and Nova just lagged until I couldn't launch apps. Stock launcher wasn't so slow but eventually I kept getting to a point no apps would launch. Magisk log did record one crash but only showed the apps I was trying to launch.
Updated Magisk and the issues were totally gone with the stock launcher for nearly 3 days. Not that I saw any issue but switched back to Nova beta launcher. Not long after that, the phone did a soft reboot (SystemUI reboot). I didn't give up on Nova but stuck with it anyway. It's been fluid since and Magisk log is clear.
Not sure if you meant my phone or OP. But consider it an update on my issue. My display glass is pristine and phone hasn't been dropped. Maybe displays go bad but I've never lost one or had it go bad.
One last issue I had with Android 10 on stock ROM, I posted my simple solution here:
https://forum.xda-developers.com/showthread.php?p=80434297
I haven't had anyone issues with Nova beta launcher since I posted last in this thread. Happily, I think all issues are resolved for me now!
Sent from my PH-1 using Tapatalk
I can tell you that "formatting data" is the only option to fix the issue that slow boot happens after system upgraded.
I had attempted to install Evolution X, and after installing Magisk I had an issue with WiFi not working.
After reading another thread where a user had success installing PQ1A.190105.090 from fastboot, I decided to do the same myself.
After installing PQ1A.190105.090 it does not go through the setup process, and instead asks for PIN. Entering the PIN causes the phone to crash right back to the lockscreen.
I even tried wiping Data from TWRP (Which also asks for PIN and says it is incorrect)
I think I managed to mess up my phone, can someone be of assistance? Thanks!
but2002 said:
I had attempted to install Evolution X, and after installing Magisk I had an issue with WiFi not working.
After reading another thread where a user had success installing PQ1A.190105.090 from fastboot, I decided to do the same myself.
After installing PQ1A.190105.090 it does not go through the setup process, and instead asks for PIN. Entering the PIN causes the phone to crash right back to the lockscreen.
I even tried wiping Data from TWRP (Which also asks for PIN and says it is incorrect)
I think I managed to mess up my phone, can someone be of assistance? Thanks!
Click to expand...
Click to collapse
No expert here but I am pretty sure I read on here of others having had issues and thus advise to disable PIN lock on the phone before attempting. Might want to try a search on here for that and it should point you to how to fix it.
Hopefully others that have rooted already will chime in for you. I am still stock 10 due to the whole A-B slot thing that has me scared.
https://forum.xda-developers.com/showpost.php?p=83458899&postcount=5