Related
I have what's probably a unique situation, though I hope not. For background info, I bought two I747s, one white and one blue, each with issues, but I intended to put parts together to end up with one good one.
When I did a factory reset on the blue one via the recovery menu, it returned a bunch of errors along the lines of "failed to mount /data." Then when it rebooted it would hang on the Samsung logo. Back in recovery mode it returns more of the same errors just booting into recovery mode, and factory reset still returns more of the same errors and doesn't fix anything. I flashed 4.3 with Odin in an attempt to fix it, but I got the boards mixed up, and that one had 4.4 on it, not 4.1 like I thought. I'm pretty sure it's hard bricked now (that whole can't downgrade thing) because it's unresponsive to everything. Though my computer does recognize that it's plugged in, more on that later.
So I figured, fine, I screwed up, I'll just use the other board with 4.1 on it from the white phone. Except when I did a factory reset on that one, it did the exact same thing! Same errors, same problem stuck at the Samsung logo. Except this time I'm not flashing sh*t until I know exactly what I need to do to fix it. In another post where the guy had the same issue with 4.1.1, it was solved by flashing 4.3 with Odin. And another post where the guy had no idea what version he had, he just knew it was lower than 4.3, his problem was also solved by flashing 4.3, But since my last efforts failed miserably, I'm very reluctant to try it until I get some knowledgeable input. I don't remember exactly which version is on there, it's 4.1.something. I'd also prefer not to upgrade beyond 4.1 because I'd like to unlock it and from what I'm reading you can only do it for free if you're on 4.1. So I guess I need a link to an Odin flashable 4.1 package?
As for the poor blue phone that used to have 4.4.something, and was mistakenly flashed with 4.3, I've heard about JTAG but I don't quite understand it, and I'm not sure it would work in my case since a lot of what I'm reading says that bricking which occurs from downgrading is often unfixable. However, Windows recognizes that a device is plugged in when I attach it via USB. It shows up in the Device Manager as QHSUSB_DLOAD. I am currently researching more on this and the method of booting from an SD card, except I don't have an SD card reader at the moment.
Any assistance, advice, links, information, and plain ole encouragement are always welcome and appreciated.
For the phone running 4.1, flash any stock rom in Odin. After flashing, boot into recovery and perform a factory reset, then boot the phone and use the free method to sim unlock. The important thing is to have the stock 4.1.1 dialler in order to access the hidden menu options?
For home hard bricked phone, you will have to try the debrick image method. If it doesn't work, a jtag service should be able to force flash a rom to the phone.
Wow, that was like a crazy fast reply!
What if the phone is 4.1.2? Can I still flash 4.1.1? I'm on the hunt for a 4.1.1 stock rom now.
Yes, you can flash 4.1.1 from 4.1.2.
audit13 said:
Yes, you can flash 4.1.1 from 4.1.2.
Click to expand...
Click to collapse
Apparently not always. I downloaded and flashed 4.1.1 with Oden 3.07, it rebooted, showed the android image like it was updating, progress bar finished, and then it just went blank. Now both phones are in the same condition of being hard bricked and showing QHSUSB_DLOAD in the device manager.
This is strange. I have downgraded approximately 10 i747m phones from 4.1.2 to 4.1.1, unlocked using the free method, and re-flashed back to 4.1.2 after unlocking.
http://forum.xda-developers.com/showthread.php?t=2371897
What options did you check in Odin? Where did you get the 4.1.1 ROM? I ask because the stock ATT 4.1.1 rom was apparently removed from sammobile.com.
How did you confirm that the phone was running 4.1.2?
I checked only auto reboot in Odin.
I found this link sammobile.com/firmwares/database/SGH-I747/ in this thread http://forum.xda-developers.com/galaxy-s3-att/help/downgrade-att-running-stock-4-4-2-rom-t3170938 , 7th post
The download was going absurdly slow, so I googled the exact file name being downloaded which was, I747UCDLK3_I747ATTDLK3_ATT, and found a google drive link at https://drive.google.com/file/d/0B_UTWXKFnZoNVFdSVjJEZlMwZjA/edit which was the first result after searching for the file name if that link doesn't work. I'm downloading the slow one now to compare it to the one I got from google drive.
I'm unsure if the phone was 4.1.1 or 4.1.2, that's why I asked if it's possible to flash 4.1.1 on top of 4.1.2. I was only trying to do a factory reset originally and had no intentions of flashing anything. I just wanted to wipe out all the crap on it from the previous user so I had only glanced at the version out of curiosity to see if it was unlockable via the free method. I remember it was 4.1.something.
I have an SD card reader on order. Hopefully I'll be able to unbrick one of them.
Do you, or anyone else, have any idea why a simple factory reset would cause errors like I described and then hang on reboot? At that point both phones were 100% factory and I hadn't done anything to them except put a battery in them to power them on. I've done a factory reset on four other S3s and this didn't happen.
It is definitely possible to flash 4.1.1 over 4.1.2 because the bootloader could not be downgraded until the mjb version.
That's what I've been reading. So where did I go wrong? Any idea why a factory reset would screw up like that?
Did you confirm the bootloader before flashing?
audit13 said:
Did you confirm the bootloader before flashing?
Click to expand...
Click to collapse
No, because I had no intentions of flashing it when I tried to do a factory reset. Then after that went bad it wouldn't boot, and I don't know how to check the boatloader when a phone will only go into recovery mode.
Where did you see reference to 4.1? It's possible that the modem or baseband was 4.1 but the bootloader was 4.3.
Under about device and then Android version. The one where if you tap it a lot you get the jellybean android that pops up. It wasn't the baseband version because that's a much longer number with the model number in it.
That screen doesn't tell you the bootloader.
As I said, I didn't check for the bootloader version before I ran into trouble because I only wanted to do a factory reset and I didn't intend to flash anything. I wouldn't imagine that it would have a different bootloader than the OS version unless that can happen without any user intervention because the previous owner was only concerned with selfies and games. She certainly didn't modify anything.
I cant explain what happened. This has never happened to me after flashing about 10 phones.
I believe it has something to do with the errors that were produced while trying to do a factory reset. What bothers me is that both phones did the exact same thing. Normally I'd say it was something I did, except that I didn't do anything but put a battery in them, boot up, find lots of junk installed, and then attempt a factory reset. On the first phone, I rebooted into recovery and tried it from there. On the second phone I tried it from inside the OS. Same results on both. The phones ran fine before that.
Any advice on how to do the boot from an SD card, or how to do the JTAG thing? I've been reading a lot but the information jumps around a lot. I'm comfortable with soldering and have an IT background if that helps.
It's possible that the recovery was corrupt or the partitions were corrupt.
Whenever I factory reset a phone, I always boot into recovery to do that, not from within the ROM.
Sounds to me like you did nothing wrong.
Did the previous owner have the phone from the time it was new?
Edit: for the phone that you flashed with 4.1.1, Odin said "pass" in the status window and the it auto rebooted?
audit13 said:
Did the previous owner have the phone from the time it was new?
Edit: for the phone that you flashed with 4.1.1, Odin said "pass" in the status window and the it auto rebooted?
Click to expand...
Click to collapse
I don't know for sure if she had it from new. Yes, for both phones Odin said pass in the window and then it rebooted. I had walked away when Odin finished with the first phone. I came back and it was dead. The second one I watched and it showed the android with the wireframe in his guts and the progress bar which moved across, and then it just went blank.
There were error messages about the partitions when I did the factory reset IIRC. Perhaps the recovery or the partition was corrupted like you said. It's just odd that both had the exact same identical problem with the exact same results. That's why I think that it must have been something I did, except that I didn't DO anything other than initiate a factory reset.
I took an i747m and reflashed stock the Telus 4.4.2 ROM.
In download mode, you should see the green Android guy with the words "Downloading...Do not turn off target" and a blue progress bar moving from left to right.
I did not check reset in Odin. Once it finished flashing the ROM, I removed the USB cable, removed the battery, replaced the battery, and booted the phone. I the Android guy with the wire frame for a few seconds, the screen went blank, and the phone started up with the Samsung logo.
Since you were getting errors with mounting the different partitions, you may have needed to flash the PIT and PDA files but I can't really say for sure as I have never encountered this problem.
I normally verify everything before I use Odin because phones that I have been given to fix have had all sorts of weird configurations.
You'll have to try the debrick guide. of use a jtag service. You could also do what I did and that is to look for people with phones that have a damaged screen and buy they at a steep discount.
Getting "Your device is corrupt. It can't be trusted and may not work properly"
Hey guys
I tried playign with the new magisk. Decided to factory reset and ran the script, and keep getting:
Getting "Your device is corrupt. It can't be trusted and may not work properly"
Any suggestions? I thought factory reset, literally reset everything...
Thanks in advance
docluv01 said:
Hey guys
I tried playign with the new magisk. Decided to factory reset and ran the script, and keep getting:
Getting "Your device is corrupt. It can't be trusted and may not work properly"
Any suggestions? I thought factory reset, literally reset everything...
Thanks in advance
Click to expand...
Click to collapse
A factory reset erases the partition where user data is stored. It does not touch any other partition. You're getting that message because the phone detects that the boot image is no longer stock. If you want to undo the changes you have made, you'll have to flash the stock Google image.
Ok, SO teh message is normal?
I flashed factory 8.0.0, and I get the same message,
TheSt33v said:
A factory reset erases the partition where user data is stored. It does not touch any other partition. You're getting that message because the phone detects that the boot image is no longer stock. If you want to undo the changes you have made, you'll have to flash the stock Google image.
Click to expand...
Click to collapse
docluv01 said:
Ok, SO teh message is normal?
After I did a factory reset, I got the message, clicked power when it asked to, then phone just sits at the google screen.
Click to expand...
Click to collapse
I haven't had a chance to test Magisk on this phone yet (I returned mine and am waiting on the replacement) but when I've used Magisk in the past, the first boot took a really long time. Give it like 10 minutes or so. If it never makes it past that, something went wrong and you should flash the stock image.
Oh wait, you get the same message if you flash the stock image? Well in that case, I'm not sure what's wrong. You may need to re-lock the bootloader before that message goes away, but make sure you're on 100% stock software before that happens. It might have something to do with the fact that Pixel devices have A and B firmware slots, so if you bring A back to stock, B might still have the Magisk patched image on it. Someone more familiar with Pixel devices should chime in.
TheSt33v said:
I haven't had a chance to test Magisk on this phone yet (I returned mine and am waiting on the replacement) but when I've used Magisk in the past, the first boot took a really long time. Give it like 10 minutes or so. If it never makes it past that, something went wrong and you should flash the stock image.
Click to expand...
Click to collapse
Well, to clarify...
I was able to get Magisk to run fine. But decided I wanted fresh stock image, so went to flash stock google image, flash went fine, but at reboot i get the same thing. could this be a slot issue?
docluv01 said:
Well, to clarify...
I was able to get Magisk to run fine. But decided I wanted fresh stock image, so went to flash stock google image, flash went fine, but at reboot i get the same thing. could this be a slot issue?
Click to expand...
Click to collapse
I'm thinking so. I'm not sure what the proper procedure is for designating which slot you're flashing to on the Pixel 2's, but it's possible that you now have 1 slot with stock firmware and 1 slot with the Magisk patched image. For the original Pixel devices, the partition names were boot_a and boot_b. So I think, and someone please correct me if I'm wrong, fastboot flash boot <file> will flash the file to whichever slot is active, but using boot_a and boot_b will flash to those designated slots. So to fix your issue, you need to make sure that both boot_a and boot_b contain stock images.
Keep in mind that I've never owned a Pixel before now (although I'm pretty comfortable with flashing other android devices), and I'm not 100% sure about this, so you might not want to take my advice.
relock the bootloader.
Here is what I did:
Fastboot flashing lock
fastboot flashing lock_critical
then tried running the flash-all.bat, got FAILED being it was locked
SO then I ran
Fastboot flashing unlock
fastboot flashing unlock_critical
ran flash-all.bat, seemed to have gone fine. Phone reboots, then after you get the circle, where it says "erasing", after about 10 seconds it reboots and says "your device is corrupt..."
Ughhh, I hope I didn't brick this thing???
sorry guys, im an ass, i thought i was using teh latest fastboot, but apparently, not
all is good. I wish I was able to delete this thread
docluv01 said:
sorry guys, im an ass, i thought i was using teh latest fastboot, but apparently, not
all is good. I wish I was able to delete this thread
Click to expand...
Click to collapse
What was the fix cuz i am getting this now after flashing the latest factory image...help!! Lol
canemaxx said:
What was the fix cuz i am getting this now after flashing the latest factory image...help!! Lol
Click to expand...
Click to collapse
relock your bootloader
canemaxx said:
What was the fix cuz i am getting this now after flashing the latest factory image...help!! Lol
Click to expand...
Click to collapse
Make sure you have the latest version of adb and fastboot from the developer site.
https://developer.android.com/studio/releases/platform-tools.html
I got the message as soon as I unlocked the bootloader. It's normal
I had this issue with old platform tools and could not get my device to boot no matter how many times I flash-all'ed or changed the current boot slot. Upgrade to the latest platform tools and run the flash-all from that directory. If it's still not working, I also unlocked critical: fastboot flashing unlock_critical , so that the flash-all could flash my bootloader as well.
Like some have said already. This message appears every time you boot after you unlock your bootloader, whether you are still running stock OS or not. Same thing happened on my 6P. Only way to get it to go away is relocking the bootloader. Don't worry though, your device isn't really corrupt. Just a scare tactic by Google.
charesa39 said:
Like some have said already. This message appears every time you boot after you unlock your bootloader, whether you are still running stock OS or not. Same thing happened on my 6P. Only way to get it to go away is relocking the bootloader. Don't worry though, your device isn't really corrupt. Just a scare tactic by Google.
Click to expand...
Click to collapse
This is somewhat true. There are 2 different messages. One that says you are running unsupported software and the color is orange. This message pops up on every boot while the bootloader is unlocked. The other message says your device is corrupt, in red. The phone will not boot. I just ran into this issue while trying to flash the november update
EDIT:
I was able to resolve this by updating adb/fastboot. I updated adb/fastboot before but i guess i did it on my other computer.
So was there any way to fix this without having to relook the bootloader? I've already had to set this phone up a second time after the longest marathon session of trying to get both TWRP and magisk to live happily together on this device, so I'd rather not do it again if it's avoidable.
Literally all I did to cause this is press the button in TWRP to switch to slot A, and after rebooting I immediately got the new scarier message that requires a power button press to boot, after which you get the regular nag about the unlocked BL. The device then hung at the Google padlock screen, so I used the buttons to reboot into BL then tried TWRP. TWRP then hung at the splash screen, so I hooked up to the PC and fastboot booted TWRP. When I tried to switch back to B, strangely, it said I already was. I pressed the button to switch to B anyway, then rebooted. The error happened again, but at least the device boots. I tried rebooting again to see if it had cleared up, but unfortunately not.
I would really like to be rid of this without having to start over. I do have a nandroid but I don't even know if I trust a restore to be successful and potentially make **** worse. Thanks in advance!
Fastboot setactive=_b
Double check exact command but this worked for me.
Make sure you flash boot.img first using
Fastboot flash boot XXX.img
Sent from my Pixel 2 XL using Tapatalk
matt1313 said:
Fastboot setactive=_b
Double check exact command but this worked for me.
Make sure you flash boot.img first using
Fastboot flash boot XXX.img
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
I was able to switch back and forth between the slots with fastboot. I thought maybe I was getting the error because they had two different boot images installed, so I backed up my boot on side B, and then restored it to slot A. No dice. I still get the error message.
IrocD said:
I was able to switch back and forth between the slots with fastboot. I thought maybe I was getting the error because they had two different boot images installed, so I backed up my boot on side B, and then restored it to slot A. No dice. I still get the error message.
Click to expand...
Click to collapse
Flash boot.img first. Don't select which slot
Then reboot bootloader and fastboot active slot b
Sent from my Pixel 2 XL using Tapatalk
I've had Google phones for years now, including previous Pixel, but I just got an XL 2 yesterday and I'm regretting it.
It's Google unlocked and running June's latest image. I've experienced various app crashing on stock, and random reboots.
Then there's the rooting and flashing. I unlocked the bootloader and installed the most recent, twrp (the one verified to work on xda for roms) but can't flash anything.
My twrp either hangs on the twrp start screen, or when it does load, the touch screen doesn't work. When I can get it going, every rom I flash gives me an error on the second step. I'm flashing on slot B by the way, that's what boots up when I boot to twrp.
Lastly, I am unlocked both for flashing and flashing_critical thru adb, so I'm at a loss and seriously confused.
When I FIRST unlocked everything, I was able to flash Nitrogen rom but I got stuck at the rom splash screen.
Tldr:
-What is the Correct install method/sequence for roms?
-do the slots matter?
-is random reboots and app crashing on stock a sign of a hardware issue?
I haven't installed a custom ROM on my P2XL, so I'm running rooted stock. Anyway, for rooted stock, this is what I did.
Entered bootloader mode.
Booted into recovery using the command "fastboot boot recovery.img", where "recovery.img" is the TWRP recovery iteslf. In my case, I renamed it "taimen.img".
Flashed the TWRP installer zip needed for the P2XL (Required if intending to replace the stock recovery).
Rebooted into recovery.
Flashed a custom kernel (Recommended - resolves touch issues in TWRP).
Flashed Magisk.
6. Rebooted.
If installing a custom ROM, flash it prior to the custom kernel. Slots only matter if running stock. Random reboots and app crashes are not signs of a hardware issue.
stevew84 said:
I've had Google phones for years now, including previous Pixel, but I just got an XL 2 yesterday and I'm regretting it.
It's Google unlocked and running June's latest image. I've experienced various app crashing on stock, and random reboots.
Then there's the rooting and flashing. I unlocked the bootloader and installed the most recent, twrp (the one verified to work on xda for roms) but can't flash anything.
My twrp either hangs on the twrp start screen, or when it does load, the touch screen doesn't work. When I can get it going, every rom I flash gives me an error on the second step. I'm flashing on slot B by the way, that's what boots up when I boot to twrp.
Lastly, I am unlocked both for flashing and flashing_critical thru adb, so I'm at a loss and seriously confused.
When I FIRST unlocked everything, I was able to flash Nitrogen rom but I got stuck at the rom splash screen.
Tldr:
-What is the Correct install method/sequence for roms?
-do the slots matter?
-is random reboots and app crashing on stock a sign of a hardware issue?
Click to expand...
Click to collapse
Ya know my friend, after our conversation yesterday, and your questions in the nitrogen thread, and now random reboots and app crashes, I think it's time to consider a factory reset. You shouldn't be having those problems on a stock setup. If that's not successful, then I would definitely consider an RMA. Just my 2 cents worth :good:
I agree. I got it used tho which is an issue.
Badger50 said:
Ya know my friend, after our conversation yesterday, and your questions in the nitrogen thread, and now random reboots and app crashes, I think it's time to consider a factory reset. You shouldn't be having those problems on a stock setup. If that's not successful, then I would definitely consider an RMA. Just my 2 cents worth :good:
Click to expand...
Click to collapse
Just so you know, I got the rom to flash finally, but it's stuck at the rom splash screen during first boot. I'm going to leave it and hope it eventually boots up.
stevew84 said:
Just so you know, I got the rom to flash finally, but it's stuck at the rom splash screen during first boot. I'm going to leave it and hope it eventually boots up.
Click to expand...
Click to collapse
If it doesn't after 5 minutes, do a hard restart with the power button. If that doesn't work, then reboot to twrp and flash the rom and twrp installer zip again.
Ok cool thanks. I relocked bootloader last night and went back to stock. Unlocked it all this morning from my work computer and different unlock app. So here's hoping.
Badger50 said:
If it doesn't after 5 minutes, do a hard restart with the power button. If that doesn't work, then reboot to twrp and flash the rom and twrp installer zip again.
Click to expand...
Click to collapse
I finally got everything to work. My vendor image is a mismatch but I could just flash junes and be done with it, right?
stevew84 said:
I finally got everything to work. My vendor image is a mismatch but I could just flash junes and be done with it, right?
Click to expand...
Click to collapse
What did you do to get it to work? You could just flash the June vendor.img to both slots. If you keep getting a vendor mismatch, probably nothing to worry about according to the Dev of nitrogen.
Different machine, cable and unlocking tool.
But I went to bone stock with locked bootloader, then flashed the newest twrp with the newest all in one tool. Was on slot A so wiped everything and flashed rom plus twrp again. I rebooted system to slot B, but then it just hung at the rom splash screen.
So I did it all over on slot A, ignored the "no os installed" message and booted anyway. Then it fired up. Rebooting into twrp from there took me to B, which is where I need to be for an image file or root.
So yea, thanks for the help.
I'm having this issue also. I tried flashing nitrogen, it hung. I tried to go back with factory reset Img and nothing happens in adb. Flashed the may img and it wouldn't boot all the way up. Now I'm stuck in bootloader trying to figure this all out. Seems like nothing in doing is working. I can get recovery to boot, but no files inside so idk. Tried to sideloadb nitrogen, but it said adb out of date for device when sdk is fully updated.
MatthewRobinson said:
I'm having this issue also. I tried flashing nitrogen, it hung. I tried to go back with factory reset Img and nothing happens in adb. Flashed the may img and it wouldn't boot all the way up. Now I'm stuck in bootloader trying to figure this all out. Seems like nothing in doing is working. I can get recovery to boot, but no files inside so idk. Tried to sideloadb nitrogen, but it said adb out of date for device when sdk is fully updated.
Click to expand...
Click to collapse
You didn't mention the out of date message in your other post, but uninstall SDK and then download the stand-alone adb/fastboot binaries from May of this year. Dump that in a folder (eg. c:\adb) and put that folder in your path statement. Manually flash the full factory image without modifying flash-all.bat. Post your screeen if you have any errors. :good:
stevew84 said:
I agree. I got it used tho which is an issue.
Click to expand...
Click to collapse
Google knows the date the phone was purchased based on imei number and honors their warranty by date, not owner. Unless it was blacklisted.
smartymcfly said:
Google knows the date the phone was purchased based on imei number and honors their warranty based on that.
Click to expand...
Click to collapse
Thanks. I might try to take advantage.
Not 100% sure of best place to post this, but I'm getting desperate now...
I'm pretty worried I've killed my device. After following the guide on how to root with Magisk, my phone is stuck on the white "loading" screen with a G logo. I've since tried to restart, but I can either go into fastboot mode or get the white screen when attempting to boot into android.
Tried to flash the latest factory image to fix it, but that couldn't get that to work. Now the phone isn't showing up on adb devices either. panicking a little bit here.
Does anyone know what to do?
ADB won't work unless the phone is booted into Android or in stock recovery for a sideload.
Does your computer recognize the device when you are in Fastboot mode and type "fastboot devices"? Try flashing the factory image again but make sure you have the most up to date platform tools from Google. Old versions are a common cause of issues.
Did you flash TWRP recovery or just boot to it to root? If you still have stock recovery you can try a factory reset from there but any modified images you installed might be the issue.
like Fury said, your platform tools need to be updated, same thing happened to me.
What didn't work when you flashed the factory image? Do you have the latest sdk tools version of fastboot and adb?
Sent from my [device_name] using XDA-Developers Legacy app
fury683 said:
ADB won't work unless the phone is booted into Android or in stock recovery for a sideload.
Does your computer recognize the device when you are in Fastboot mode and type "fastboot devices"? Try flashing the factory image again but make sure you have the most up to date platform tools from Google. Old versions are a common cause of issues.
Did you flash TWRP recovery or just boot to it to root? If you still have stock recovery you can try a factory reset from there but any modified images you installed might be the issue.
Click to expand...
Click to collapse
Thanks so much, this is where I was going wrong. Have gone into recovery and rescued it.
Tried the process again to get Magisk working, but ended up the same although this time the white screen only went on for a while before I got an error saying my data was corrupted. Tbh, after all the stress I'm just going to give up on this and live with the phone in stock. All my drivers and adb were installed and setup today, so everything is up to date.
edit...
Not out of the woods yet. After restarting the phone and going through the setup, it's not detecting the SIM card or any wifi networks. I've installed the OTA and wiped data once more after having this problem, still not resolved.
Nick676 said:
Thanks so much, this is where I was going wrong. Have gone into recovery and rescued it.
Tried the process again to get Magisk working, but ended up the same although this time the white screen only went on for a while before I got an error saying my data was corrupted. Tbh, after all the stress I'm just going to give up on this and live with the phone in stock. All my drivers and adb were installed and setup today, so everything is up to date.
Thanks again for helping.
Click to expand...
Click to collapse
It sounds like you are trying to install Magisk v17.1 like I tried. If so you need to use v17.3 beta. If you follow this thread you should be fine. It even tells you what to do for your original problem, just takes some reading and patience.
Misterxtc said:
It sounds like you are trying to install Magisk v17.1 like I tried. If so you need to use v17.3 beta. If you follow this thread you should be fine. It even tells you what to do for your original problem, just takes some reading and patience.
Click to expand...
Click to collapse
I tried it with both 17.1 and 17.3, so not sure what the issue is. Seem to have finally booted up properly with wifi and signal working, so hopefully it's all good now. Gonna give up on rooting.
Nick676 said:
Not 100% sure of best place to post this, but I'm getting desperate now...
I'm pretty worried I've killed my device. After following the guide on how to root with Magisk, my phone is stuck on the white "loading" screen with a G logo. I've since tried to restart, but I can either go into fastboot mode or get the white screen when attempting to boot into android.
Tried to flash the latest factory image to fix it, but that couldn't get that to work. Now the phone isn't showing up on adb devices either. panicking a little bit here.
Does anyone know what to do?
Click to expand...
Click to collapse
you may want to try to totally uninstalling Magisk frist with the official latest Magisk uninstaller and reboot and then do a complete factory reset. this has helped me in the past.
my new pixel 3XL will be the first Android phone that I owned that will not be rooted.
I got into a bootloop after disabling the settings app from the terminal emulator, using the command pm disable, am rooted using magisk. Now it is telling me to enter safe mode, but the safe mode is completely unusable. Anyone can tell how to undo so it boots up normally, besides factory reset
Bummer. If nothing works you could go to recovery and wipe phone clean from there. You'll need to look up the button combo to go to recovery, don't recall myself.
Can't believe you decided to proceed even people told you your device will brick. Nothing you can do other than factory reset your device from recovery. You also can flash ROM via odin. Next time listen to others. Otherwise, don't even ask in the first place
twinh3ad said:
Can't believe you decided to proceed even people told you your device will brick. Nothing you can do other than factory reset your device from recovery. You also can flash ROM via odin. Next time listen to others. Otherwise, don't even ask in the first place
Click to expand...
Click to collapse
Actually my phone was working just fine while the app was disabled ,but I forgot to to enable it again before reebooting my phone , simple mistake