Hey all,
So I updated my pixel xl to Android O, and then used the modified TWRP to flash Super Su, SUhide. The phone booted up and everything was perfect. It was a little sluggish so I decided to do a full factory reset... again, phone reset, booted perfectly. I then restored all my apps from the google play store cloud... phone was functioning fine.
I went to reboot the phone after a while... and now the phone is stuck on the G logo after the bouncing dots... and just continues to load.
It's been like that for over 20 minutes.
Is this normal? Anyway I can fix this?
Thanks!
8.0.0 rooting nightmare
gaw54 said:
Hey all,
So I updated my pixel xl to Android O, and then used the modified TWRP to flash Super Su, SUhide. The phone booted up and everything was perfect. It was a little sluggish so I decided to do a full factory reset... again, phone reset, booted perfectly. I then restored all my apps from the google play store cloud... phone was functioning fine.
I went to reboot the phone after a while... and now the phone is stuck on the G logo after the bouncing dots... and just continues to load.
It's been like that for over 20 minutes.
Is this normal? Anyway I can fix this?
Thanks!
Click to expand...
Click to collapse
I have the same exact issue after following the exact process described above. After a weekend of frustration, I was thrilled to see this post, but then bummed there are no suggestions. There is no way I can get it back to recovery, no matter what power/volume combination I try. The phone is not detectable by ADB either, so unless a kind soul has a suggestion, there seems to be nothing to do except let the battery die and hope.
Umm boot into bootloader and flash stock boot.img and system.img?
george241312 said:
Umm boot into bootloader and flash stock boot.img and system.img?
Click to expand...
Click to collapse
I would love to do that, but how is it possible if there is no power or volume button combination that can get me off of the Google boot screen and into bootloader?
Have you tried Power + volume down ? It'll turn off after release power button only. That or let the battery die and when you try to plug it up next time leave vol down pressed.
george241312 said:
Have you tried Power + volume down ? It'll turn off after release power button only. That or let the battery die and when you try to plug it up next time leave vol down pressed.
Click to expand...
Click to collapse
I have tried that, thank you. I will let battery die and do the Volume Down method you suggest, and report back.
edjanx said:
I have tried that, thank you. I will let battery die and do the Volume Down method you suggest, and report back.
Click to expand...
Click to collapse
That did the trick. Back to stock 8.0.0, and hoping to find a stable root method that doesn't hang-up on the first reboot. Thanks for the help!
First of all. Hold the power button for about 20 secs and the phone will reboot.
Hold vol - and you are straight to bootloader.
Second flash full factory to both slots.
And third stop using the - w solution when you are coming from another rom or a different stock version. We had this problems on other forums and it was every time - w or not flashing both slots. I know for many people there will be no problem but some apps are just misbehaving when you do so. And they are causing reboots and bootloops.
mikaole said:
First of all. Hold the power button for about 20 secs and the phone will reboot.
Hold vol - and you are straight to bootloader.
Second flash full factory to both slots.
And third stop using the - w solution when you are coming from another rom or a different stock version. We had this problems on other forums and it was every time - w or not flashing both slots. I know for many people there will be no problem but some apps are just misbehaving when you do so. And they are causing reboots and bootloops.
Click to expand...
Click to collapse
OK, thank you! I am not familiar with the -w method. This is a new Pixel XL I received from Google to replace a nexus 6p with a bootloader issue. I made the mistake of not attempting this before it updated from 7.1.2 to 8.0.0, or it may have been a different story.
So I have the the phone restored to 8.0.0 and was going to attempt root. But I didn't realize there are two slots to flash. I simply ran flash-all.bat and the phone came back up. So I guess I'd have to move the Sept security stock image over to the phone along with the SU, SU Config (which may not be needed if on 8.0.0?), and Su Hide. Then I boot up TWRP 3.1.1 and flash stock image to both slots, reboot, then get back into TWRP and run the SU, then SU Hide on *both* slots?
Thanks!
Janx
Run flashall.bat on the slot you are now in. Reboot to system
Back to bootloader. Switch slots through fastboot
fastboot --set-active=_b
fasboot reboot bootloader
Now you should be on the other slot
Flashall.bat
Reboot to system
Back to bootloader
fastboot boot twrp.img (latest)
In twrp put latest su or in my case magisk 14.2, twrp zip on device.
If you use su just flash it
If you use magisk. Flash magisk, flash twrp.zip and magisk again. With magisk twrp will stick.
Reboot and you are good to go.
If you want a kernel you have to flash twrp and magisk after again.
mikaole said:
Run flashall.bat on the slot you are now in. Reboot to system
Back to bootloader. Switch slots through fastboot
<SNIP>
If you want a kernel you have to flash twrp and magisk after again.
Click to expand...
Click to collapse
Thank you! I will be able to perform this sequence in a few hours and will report back. :good:
Ok. Will be in bed than. If you have any problems give me a PM and we can do it together via hangouts.
Update: I successfully flashed A & B, got to the step where I flash Magisk 14.2. It finished unmounting partitions, but when updating partition details fails, "failed to mount '/system' (device or resource busy)...done
It said successfully installed, so I flashed twrp to the boot image, flashed magisk again, and it is now rebooting endlessly. Wrong place to flash the twrp image I'm guessing?
EDIT: Just noticed your message, good night - thanks again. I'm working through it and will take you up on your kind offer should I not find success.
I did a 'flash-all.sh' on both A and B again, copying over my old phone, then will attempt to gain root by booting into TWRP 3.1.1, installing "SR3-SuperSU-v2.82-SR3-20170813133244", reboot bootloader, go into TWRP again and then install "UPDATE-suhide-v1.08-20170815171034"
EDIT #2: EDIT #2: Stable root achieved using newer versions of files "SR5-SuperSU-v2.82-SR5-20171001224502" & after booting, applying "UPDATE-suhide-v1.09-20171001222116". So far it has survived several reboots, so I'm hoping it's all good now.
Related
Long story short installed substratum and it was working fine, had a navbar theme already running and installed another one. Few hours later rebooted phone and when it booted back up systemui crashed and it went into bootlooping into that over and over again. Now it bootloops a few times and goes into a recovery menu that only gives me the options to try rebooting again or a factory data reset.
The phone boots into bootloader/fastboot just fine and I can get into recovery but the only options I have are 'try again' and 'factory data reset' I know that FDR is basically my only option and so be it. BUT IF POSSIBLE I want to try and backup the internal data or at least as much of it as possible.
So, is it possible to backup any internal data with only having access to bootloader/fastboot.
I've spent over an hour searching to this answer but either I was searching wrong or simply was not able to find the answer. Pixel XL is 100% stock. Never modded, never rooted, stock recovery, stock latest official Oreo from OTA update.
So again. Absolutely no access to the OS. Only access bootloader/fastboot and a form of the recovery menu and I would like to somehow backup the internal data. I don't care about apps or any app data, specifically just the user data if at all possible. If not well then I'm screwed and that's that.
Hello,
Happened to me also something like this. The phone rebooted and the only option were those presented to you also. But, I pressed the "Try again". If this still doesn't work, when the device is rebooting, and the white screen appears, try and hold on to the power button until the moving dots appear.
Also, this didn't wipe anything on my device.
Hope this is useful to you.
moraritza1 said:
Hello,
Happened to me also something like this. The phone rebooted and the only option were those presented to you also. But, I pressed the "Try again". If this still doesn't work, when the device is rebooting, and the white screen appears, try and hold on to the power button until the moving dots appear.
Also, this didn't wipe anything on my device.
Hope this is useful to you.
Click to expand...
Click to collapse
Does nothing. Just reboots back into recovery. I've tried Try Again probably 100 times and nothing ever changes. Even safe mode does not work. The SystemUI is completely dead.
I'm 90% sure there is no way to fix the phone other than factory data reset and I'm fine with that. I just want to know if I can backup anything from bootloader/fastboot before I do that.
Have you tried using ADB to boot ( not flash ) a custom recovery, and from there to backup the phone, and after if it's possible, to use the USB-OTG to copy that backup to an USB memory stick?
Looking at the Substratum FAQ in the app it says that if you experience a bootloop you should be able to flash /storage/emulated/0/substratum/SubstratumRescue.zip in recovery and it should fix the boot loop.
matt0720 said:
Looking at the Substratum FAQ in the app it says that if you experience a bootloop you should be able to flash /storage/emulated/0/substratum/SubstratumRescue.zip in recovery and it should fix the boot loop.
Click to expand...
Click to collapse
As Matt already mentioned, there's a rescue zip file which comes by default with substratum. It's purpose is to remove all overlays which you've currently installed.
In case you don't have a custom recovery installed you can simply boot into twrp via adb (without having flash the recovery)
Android-xp said:
As Matt already mentioned, there's a rescue zip file which comes by default with substratum. It's purpose is to remove all overlays which you've currently installed.
In case you don't have a custom recovery installed you can simply boot into twrp via adb (without having flash the recovery)
Click to expand...
Click to collapse
What if you're bootloader locked? Is there a way to recover from a bad overlay?
You could try to flash the factory image if you've unlocked the BL, just remove the -w from the flash all script
bobby janow said:
What if you're bootloader locked? Is there a way to recover from a bad overlay?
Click to expand...
Click to collapse
If you have checked the option to potentially allow unlocking your bootloader in dev-settings you can use fastboot to unlock your bootloader and boot into the bootable recovery image
Magisk v20 worked stable on Galaxy A50 but If you want to use Magisk v19.3 you can patch and downgrade it using Magisk Manager - Custom Channel Update https://www.youtube.com/watch?v=vcF0pfdQyW8
-----------------------------------------------------------
Complete Guide for Rooting Samsung Galaxy A50 using Magisk v20 / v19.3 ( tested on SM-A505F ):
* Download the firmware Galaxy A50 (SM-A505F).
* Unzip the firmware and copy the AP tar file to your device. It is normally named as AP_[device_model_sw_ver].tar.md5. Copy AP tar file and MagiskManager apk to your phone.
* Install Magisk Manager on your phone.
* In Magisk Manager: Install → Install → Select and Patch a File
* Select the AP tar file. Magisk Manager will patch the whole firmware file and store the output to [Internal Storage]/Download/magisk_patched.tar. Copy magisk_patched.tar the tar file to your PC
* Enter Download Mode : Turn Power Off. Press and hold Volume Up key + Power Key,* When Samsung Logo appears release Power Key only, keep pressing Volume Up key until Android Recovery Mode Appears.
* Select Wipe data / Factory reset, Select Reboot to bootloader.* Connect your Samsung Galaxy to PC using USB Cable.
*Flash magisk_patched.tar as AP in ODIN, together with the BL, CP and HOME_CSC files. Never flash only an AP file, as Odin can shrink your /data file-system if you do. Checked "Auto Reboot" and "F. Reset Time" only in options.
* Magisk is now successfully flashed to your device and Rebooting!
* After the device is booted up, do the usual initial setup. It need more time and patient.
* Connect the phone to Internet copy Magisk Manager apk to your phone and Install it
* Open Magisk Manager. It will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
* Done! You can use Root Checker to check it, Enjoy!
New video Install and Root with Magisk v20 / v19.3 https://youtu.be/ILvgki0pFHE
To prevent loosing magisk root after reboot. Reboot the phone from Magisk or Fully Power Off, you can watch this video https://youtu.be/Ea8s16usBOM
Rooting with TWRP+Magisk ( ASH2 baseband version only ), you can watch this video https://youtu.be/kYwJAKBzX1E
well donw
thanks i rooted latest stock F2 firmware
it works
FYI: To prevent loosing magisk root after reboot. Reboot the phone from Magisk or Fully Power Off, you can watch this video https://youtu.be/Ea8s16usBOM
Oh I wish I could get magisk on my phone. Unfortunatly I can't find the firmware, for my phone, anywhere on the internet (A505W). Will do directly once I can!
I had it finally rooted like this since yesterday thanks to this process. Got it in root mode running today all day. THE PROBLEM IS: It doesnt stay on anymore after i reboot once again. It starts, I can put in the pincode of sim, but after 10 seconds it reboots. Without sim also reboots after 10 secs. This goes on and on and on. I read on web delete cache can help. I can sometimes boot normally once thanks to that. Root mode is hopeless, then it always reboots. I used the right stock rom. Didnt make changes of system apps etc. I havent tried factory reset yet, but i'm tired of reinstalling all apps and settings again and i asume it just will happen again. Who knows what is causing this?
Edit: It kept rebooting in any way. Used the factory reset at the end. Booted it up once without root. Set up Wifi and google account. Tried to reboot in root mode and voila: stuck in bootscreen with red letterd 'custom binnary not allowed'. Can't startup, can't go to recovery, can't flash the magisk patched zip (same red letters). Flashed stock rom and wait for the possibility to flash magisk patched again.
Edit 2: Booting in the stock rom probably registers something to let u flash something else again. Magisk patched flashed again. Booted normally, magisk up to date and working. Just gonna install fake gps, smali and magisk hide app again. Not in the mood to test reboot then again. It probably fails again. But i can spoof again for now.
Edit 3: After trying some more things, I think the conclusion is: U can only use Root mode once with this, until it reboots.
I wonder if I'm the only one with this.
jarno389 said:
I had it finally rooted like this since yesterday thanks to this process. Got it in root mode running today all day. THE PROBLEM IS: It doesnt stay on anymore after i reboot once again. It starts, I can put in the pincode of sim, but after 10 seconds it reboots. Without sim also reboots after 10 secs. This goes on and on and on. I read on web delete cache can help. I can sometimes boot normally once thanks to that. Root mode is hopeless, then it always reboots. I used the right stock rom. Didnt make changes of system apps etc. I havent tried factory reset yet, but i'm tired of reinstalling all apps and settings again and i asume it just will happen again. Who knows what is causing this?
Click to expand...
Click to collapse
Have you attempted to change your IMEI recently?
Ertogrul said:
Have you attempted to change your IMEI recently?
Click to expand...
Click to collapse
Nope, the only thing i want root for is spoofing with gps joystick.
jarno389 said:
I had it finally rooted like this since yesterday thanks to this process. Got it in root mode running today all day. THE PROBLEM IS: It doesnt stay on anymore after i reboot once again. It starts, I can put in the pincode of sim, but after 10 seconds it reboots. Without sim also reboots after 10 secs. This goes on and on and on. I read on web delete cache can help. I can sometimes boot normally once thanks to that. Root mode is hopeless, then it always reboots. I used the right stock rom. Didnt make changes of system apps etc. I havent tried factory reset yet, but i'm tired of reinstalling all apps and settings again and i asume it just will happen again. Who knows what is causing this?
Click to expand...
Click to collapse
I have tried everything but failed, I have tested on some device but it's only happen to A50
will this work with a505gn?
redymedan said:
I have tried everything but failed, I have tested on some device but it's only happen to A50
Click to expand...
Click to collapse
That's seem pretty unstable as it is right now. Was tempting to try this on my A505W, but I'm reluctant now.
Now I'm just wondering why the heck my root is still active with 2 random reboots. Last 20 runs the random reboots made it lose root and got stuck with constant rebooting.
When i started the recovery of samsung backup, it rebooted again (3rd time) (again root is somehow still active). Screw it, gonna forget about the backup and keep it like this. I think the random rebooting seems to happen often when installing much apps.
jarno389 said:
I had it finally rooted like this since yesterday thanks to this process. Got it in root mode running today all day. THE PROBLEM IS: It doesnt stay on anymore after i reboot once again. It starts, I can put in the pincode of sim, but after 10 seconds it reboots. Without sim also reboots after 10 secs. This goes on and on and on. I read on web delete cache can help. I can sometimes boot normally once thanks to that. Root mode is hopeless, then it always reboots. I used the right stock rom. Didnt make changes of system apps etc. I havent tried factory reset yet, but i'm tired of reinstalling all apps and settings again and i asume it just will happen again. Who knows what is causing this?
Edit: It kept rebooting in any way. Used the factory reset at the end. Booted it up once without root. Set up Wifi and google account. Tried to reboot in root mode and voila: stuck in bootscreen with red letterd 'custom binnary not allowed'. Can't startup, can't go to recovery, can't flash the magisk patched zip (same red letters). Flashed stock rom and wait for the possibility to flash magisk patched again.
Edit 2: Booting in the stock rom probably registers something to let u flash something else again. Magisk patched flashed again. Booted normally, magisk up to date and working. Just gonna install fake gps, smali and magisk hide app again. Not in the mood to test reboot then again. It probably fails again. But i can spoof again for now.
Edit 3: After trying some more things, I think the conclusion is: U can only use Root mode once with this, until it reboots.
I wonder if I'm the only one with this.
Click to expand...
Click to collapse
Read my First post, I have updated it for fixing lost magisk root after reboot
I cannot pass through the flashing of image modified by Magisk. During the flash some red text appears on top saying that custom binary (VBMETA) blocked ... then there is a front camera, so I can not read it all and then "Lock" word. The flashing stops and odin waits forever. The only thing I can do is to interrupt and then reflash the whole firmware with odin since it ends up at the "error has occured while updating the device software".
My device is SM-A505FN, firmware XEZ-A505FNXXU1ASE3, OEM unlocked, tried Magisk Manager 7.3.2.
(w) said:
I cannot pass through the flashing of image modified by Magisk. During the flash some red text appears on top saying that custom binary (VBMETA) blocked ... then there is a front camera, so I can not read it all and then "Lock" word. The flashing stops and odin waits forever. The only thing I can do is to interrupt and then reflash the whole firmware with odin since it ends up at the "error has occured while updating the device software".
My device is SM-A505FN, firmware XEZ-A505FNXXU1ASE3, OEM unlocked, tried Magisk Manager 7.3.2.
Click to expand...
Click to collapse
Flash whole stock rom. Boot and login. Connect to wifi. Wait few minutes. Flash magisk rom again.
(w) said:
I cannot pass through the flashing of image modified by Magisk. During the flash some red text appears on top saying that custom binary (VBMETA) blocked ... then there is a front camera, so I can not read it all and then "Lock" word. The flashing stops and odin waits forever. The only thing I can do is to interrupt and then reflash the whole firmware with odin since it ends up at the "error has occured while updating the device software".
My device is SM-A505FN, firmware XEZ-A505FNXXU1ASE3, OEM unlocked, tried Magisk Manager 7.3.2.
Click to expand...
Click to collapse
You need to unlock the bootloader from Download Mode, Watch this video https://youtu.be/o1xZ-E3jhUg
redymedan said:
You need to unlock the bootloader from Download Mode, Watch this video https://youtu.be/o1xZ-E3jhUg
Click to expand...
Click to collapse
Oh, thanks, I was not able to find this trick, there are lot of infos everywhere and it's hard to find out. Thanks. So both volumes holding and plugin cable.
Thanks again
redymedan said:
Solved: Lost Magisk Root After Reboot
To prevent loosing magisk root after reboot. Reboot the phone from Magisk or Fully Power Off, you can watch this video https://youtu.be/Ea8s16usBOM
Click to expand...
Click to collapse
So what would happen if, by a mistake of mine, my battery dies. Do I have to reflash magisk again and factory wipe everytime? Or is the problem occur only with the "reboot" function of android since it work while fully powering it off.
AliasGprime said:
So what would happen if, by a mistake of mine, my battery dies. Do I have to reflash magisk again and factory wipe everytime? Or is the problem occur only with the "reboot" function of android since it work while fully powering it off.
Click to expand...
Click to collapse
Mine is still rooted since friday. It sometimes reboots randomly. Then i have to reset with volume down and power button or else is keeps restarting. Root is still active then. Battery also died yesterday. Could start up with power key only and root is still active. I still don't understand why but im good.
(I used the root mode function with volume up and power key till logo popsup only once after the flashing of magisk patcher to let it install magisk manager. )
I'm still wondering if I'm the only one with random reboots or constant reboots
Worked great for my SM-A505G.
In summary, after installing Magisk:
(Powering up normally) → (System with NO Magisk)
(Volume UP + Power) → (Splash screen) → (Release all buttons) → (System with Magisk)
(Volume UP + Power) → (Splash screen) → (Keep pressing volume up) → (Actual recovery)
Hi there,
Yesterday I rooted my A505W (Canadian Variant) and got random reboots like almost every one else. It got so bad, I decided to go back to un rooted stock. Before flashing stock firmware I took a look in build.prop file, hoping I might find something that does not belong there after rooting. And I think I found it. At the very end there is line like this:
ro.expect.recovery_id=0xf1dee4214a6ffec6b8
2cec9a13222d4f34c7fd10000000000000000
000000000
Comment it out to lool like this:
#ro.expect.recovery_id=0xf1dee4214a6ffec6b8
#2cec9a13222d4f34c7fd10000000000000000
#000000000
Wanted to delete it, but it was enough to comment it out whit #
Since last night I don’t have any reboots, it looks like commenting it out did the trick. So try it for yourself an see if it helps.
One more thing, if you need to reboot your device do not do it from Magisk, because it will keep rebooting, just power down and boot with the key combination. As I said since last night I have no random reboots.
I just noticed after doing a clean install of the C3 factory image using -w that I am unable to boot to the stock recovery. It seems to be missing from my installation. Any ideas why I may be unable to boot to recovery? All I get is a dead Android logo with "No command" or it boots up my system after restarting. I've tried booting from the bootloader numerous times and never seems to work. Is it possible that the stock recovery was never installed? I did no perform a --slot all when installing Android 10 so maybe that's the issue? Any suggestions would be great as I can't seem to find a solution to this in the forums or Google searching. Thanks.
You have to go one step beyond the no recovery screen to see the recovery commands. If presented with an image of a broken Android with “No Command” printed on the screen, press and hold the Power button. Press the Volume Up button once. Then release the Power button.
Seems I can't even get to the broken Android screen now. In the bootloader if I select boot recovery it just boots my system and never shows the broken Android anymore. Very odd. I'm stumped.
rspkt said:
Seems I can't even get to the broken Android screen now. In the bootloader if I select boot recovery it just boots my system and never shows the broken Android anymore. Very odd. I'm stumped.
Click to expand...
Click to collapse
I am not sure what you are referring to "boot recovery." Are you entering the bootloader in some way other than volume down +power? The option when using the up/down in bootloader is Recovery mode. That will get you to the broken android and no command. At worst though, you can flash boot.img and get your stock recovery/kernel back/unroot.
sliding_billy said:
I am not sure what you are referring to "boot recovery." Are you entering the bootloader in some way other than volume down +power? The option when using the up/down in bootloader is Recovery mode. That will get you to the broken android and no command. At worst though, you can flash boot.img and get your stock recovery/kernel back/unroot.
Click to expand...
Click to collapse
I can enter the bootloader via adb or with the power + volume down no problem. When I select recovery from the bootloader it boots to the Google logo then blank screen and seems to reboot again straight to my system. I may have to try to revert to the stock boot.img like you suggested and see if that solves the issue.
rspkt said:
I can enter the bootloader via adb or with the power + volume down no problem. When I select recovery from the bootloader it boots to the Google logo then blank screen and seems to reboot again straight to my system. I may have to try to revert to the stock boot.img like you suggested and see if that solves the issue.
Click to expand...
Click to collapse
I get the same thing where it won't boot to recovery from the bootloader, but goes back to booting to system. It's because I'm rooted. Flash the stock boot image and you'll be fine.
rspkt said:
I can enter the bootloader via adb or with the power + volume down no problem. When I select recovery from the bootloader it boots to the Google logo then blank screen and seems to reboot again straight to my system. I may have to try to revert to the stock boot.img like you suggested and see if that solves the issue.
Click to expand...
Click to collapse
OK, that makes better sense. You are pretty clearly in a bootloop. Just confirming the terminology. Flashing stock boot might get you out of the loop, but after rereading your initial message it sounds as if some info is missing. After the flash-all, did it ever get to the setup screen where you enter your gmail account name, etc. Did it get through that to the actual OS, and if so what else did you do that got you into the bootloop? Root attempt?
sliding_billy said:
OK, that makes better sense. You are pretty clearly in a bootloop. Just confirming the terminology. Flashing stock boot might get you out of the loop, but after rereading your initial message it sounds as if some info is missing. After the flash-all, did it ever get to the setup screen where you enter your gmail account name, etc. Did it get through that to the actual OS, and if so what else did you do that got you into the bootloop? Root attempt?
Click to expand...
Click to collapse
Ya my phone setup fine through all the initial setup steps as if it was a new device and the system works perfectly. I did root and install Kirisakura kernel but only after few days of using stock. Just noticed after setting everything up the recovery seems to be missing when I tried to boot into it. I may try and start from scratch again cuz obviously something got broken during the factory image installation using -w.
rspkt said:
Ya my phone setup fine through all the initial setup steps as if it was a new device and the system works perfectly. I did root and install Kirisakura kernel but only after few days of using stock. Just noticed after setting everything up the recovery seems to be missing when I tried to boot into it. I may try and start from scratch again cuz obviously something got broken during the factory image installation using -w.
Click to expand...
Click to collapse
I missed the post by @jd1639 while I was replying. It doesn't sound like anything got messed up as a result of the -w. Because stock recovery is part of boot now, you just need to stay out of there unless you flash boot.img first. Not doing the --slot all wouldn't have any impact unless you install a custom ROM, an OTA or do a manual slot change. Since it was the first time I had done a completely clean wipe in a while when I flashed 10 (after custom ROMs, OTAs, etc), I actually did flash-all (with -w) to both slots. I did a flash-all on B and finished setup, and then booted back to BL, changed slots manually to A and did a second flash-all. Only after that did I start gettin gthe phone ready for daily function. Not sure it helped anything but my OCD, but it was fun to watch the fastbootd thing run a few times. :silly:
jd1639 said:
I get the same thing where it won't boot to recovery from the bootloader, but goes back to booting to system. It's because I'm rooted. Flash the stock boot image and you'll be fine.
Click to expand...
Click to collapse
I never would have assumed having root could cause this issue.
Brand new Pixel 3 XL
Enabled OEM Unlocking
Enabled USB Debugging
Unlocked Bootloader
Copied twrp-pixel3-installer-crosshatch-3.2.3-5.zip to my phone
Rebooted into bootloader
fastboot boot c:\...\twrp-3.3.1-3-crosshatch.img
Flashed twrp-pixel3-installer-crosshatch-3.2.3-5.zip
Wiped system/data/cache
Flashed AOSiP-9.0-Official-crosshatch-20190722.zip
Flashed twrp-pixel3-installer-crosshatch-3.2.3-5.zip
Rebooted
When the system rebooted, it brought me into bootloader. I selected Start and then it rebooted into Bootloader again. I then figured something went wrong with installing AOSiP, so I booted into recovery.... from TWRP, I wiped system/data/cache/storage/data in attempt to start over and flash the ROM again. This time, I rebooted the system after the wipe and upon rebooting, the phone never turned back on. Pressing and holding the power button for long periods of time doesn't seem to do anything. Any ideas where I went wrong and more importantly if I bricked my phone? Thx.
EDIT: Tried holding volume down and power button for 10+ seconds and it booted into bootloader. Not really sure where to go from here.
EDIT 2: I tried booting into Recovery. It went back to the black screen. I had to use volume down and power button to get back into bootloader. Fastboot devices does detect the phone. I'm guessing this is a softbrick and I can follow the softbrick tutorial from here? Either way, it'd be nice to know where I took a wrong turn if anybody knows. Thanks.
EDIT 3: It may also be worth mentioning that I confirmed all the md5sum's before flashing the zips or booting the img.
thex2 said:
Brand new Pixel 3 XL
Enabled OEM Unlocking
Enabled USB Debugging
Unlocked Bootloader
Copied twrp-pixel3-installer-crosshatch-3.2.3-5.zip to my phone
Rebooted into bootloader
fastboot boot c:\...\twrp-3.3.1-3-crosshatch.img
Flashed twrp-pixel3-installer-crosshatch-3.2.3-5.zip
Wiped system/data/cache
Flashed AOSiP-9.0-Official-crosshatch-20190722.zip
Flashed twrp-pixel3-installer-crosshatch-3.2.3-5.zip
Rebooted
When the system rebooted, it brought me into bootloader. I selected Start and then it rebooted into Bootloader again. I then figured something went wrong with installing AOSiP, so I booted into recovery.... from TWRP, I wiped system/data/cache/storage/data in attempt to start over and flash the ROM again. This time, I rebooted the system after the wipe and upon rebooting, the phone never turned back on. Pressing and holding the power button for long periods of time doesn't seem to do anything. Any ideas where I went wrong and more importantly if I bricked my phone? Thx.
EDIT: Tried holding volume down and power button for 10+ seconds and it booted into bootloader. Not really sure where to go from here.
EDIT 2: I tried booting into Recovery. It went back to the black screen. I had to use volume down and power button to get back into bootloader. Fastboot devices does detect the phone. I'm guessing this is a softbrick and I can follow the softbrick tutorial from here? Either way, it'd be nice to know where I took a wrong turn if anybody knows. Thanks.
EDIT 3: It may also be worth mentioning that I confirmed all the md5sum's before flashing the zips or booting the img.
Click to expand...
Click to collapse
Nevermind, @sliding_billy has the answer.
I
thex2 said:
Brand new Pixel 3 XL
Enabled OEM Unlocking
Enabled USB Debugging
Unlocked Bootloader
Copied twrp-pixel3-installer-crosshatch-3.2.3-5.zip to my phone
Rebooted into bootloader
fastboot boot c:\...\twrp-3.3.1-3-crosshatch.img
Flashed twrp-pixel3-installer-crosshatch-3.2.3-5.zip
Wiped system/data/cache
Flashed AOSiP-9.0-Official-crosshatch-20190722.zip
Flashed twrp-pixel3-installer-crosshatch-3.2.3-5.zip
Rebooted
When the system rebooted, it brought me into bootloader. I selected Start and then it rebooted into Bootloader again. I then figured something went wrong with installing AOSiP, so I booted into recovery.... from TWRP, I wiped system/data/cache/storage/data in attempt to start over and flash the ROM again. This time, I rebooted the system after the wipe and upon rebooting, the phone never turned back on. Pressing and holding the power button for long periods of time doesn't seem to do anything. Any ideas where I went wrong and more importantly if I bricked my phone? Thx.
EDIT: Tried holding volume down and power button for 10+ seconds and it booted into bootloader. Not really sure where to go from here.
EDIT 2: I tried booting into Recovery. It went back to the black screen. I had to use volume down and power button to get back into bootloader. Fastboot devices does detect the phone. I'm guessing this is a softbrick and I can follow the softbrick tutorial from here? Either way, it'd be nice to know where I took a wrong turn if anybody knows. Thanks.
EDIT 3: It may also be worth mentioning that I confirmed all the md5sum's before flashing the zips or booting the img.
Click to expand...
Click to collapse
If you can get to BL and fastboot devices is recognizing it, you are only soft bricked. Do a flash-all of the factory image. You will be starting over with the exception of OEM unlock and BL unlock. Once you are up and running, go back to BL, change slots and do the flash-all again. Of course, you will be setting up again but you should be clean. Be sure to use the last Android 9 factory image for flash-all if you are not intending to go to 10 yet. There is one rock solid custom ROM for 10 (Havoc). Take a read of the install instructions as it doesn't use TWRP (not available for 10 yet). It does need the flash-all of November factory image done to both slots, so if you are looking at that do it immediately IMO since you will have to wipe anyways.
If you wipe system in TWRP then you have to flash a ROM from there. That is why it went blank when you rebooted. You have nothing to boot up on.
ADB a stock file and start over...it's not bricked.
Thank you for the help guys. I will work on fixing the issue tonight. Also, thanks for the suggestion on the Havoc ROM, but I'm staying with Android 9 because of the menu navigation button at the bottom right of the older apps... https://www.androidpolice.com/2019/...utton-has-finally-been-retired-in-android-10/
thex2 said:
Thank you for the help guys. I will work on fixing the issue tonight. Also, thanks for the suggestion on the Havoc ROM, but I'm staying with Android 9 because of the menu navigation button at the bottom right of the older apps... https://www.androidpolice.com/2019/...utton-has-finally-been-retired-in-android-10/
Click to expand...
Click to collapse
Havoc also had pie builds if you wanted to try.
I'm rooted. Sideloaded the newest OTA.
Usually at this step I would reboot and it would say I've lost root, then I would go to the bootloader and flash the (newest) patched boot.img and be good to go.
But this time, instead of booting first, I went straight to the bootloader and flashed the patched boot.img after flashing the OTA.
Now I'm stuck in a bootloop. It boots to the G logo, has the loading bar, and then eventually just reboots and repeats.
How do I get out of this bootloop?
Thanks in advance for any help!!
_________
EDIT: Now when I boot it says your device is corrupted, and then goes to the Google logo (not the G) and just sits there for a couple minutes then turns the device off.
Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own)
finshan said:
I'm rooted. Sideloaded the newest OTA.
Usually at this step I would reboot and it would say I've lost root, then I would go to the bootloader and flash the (newest) patched boot.img and be good to go.
But this time, instead of booting first, I went straight to the bootloader and flashed the patched boot.img after flashing the OTA.
Now I'm stuck in a bootloop. It boots to the G logo, has the loading bar, and then eventually just reboots and repeats.
How do I get out of this bootloop?
Thanks in advance for any help!!
_________
EDIT: Now when I boot it says your device is corrupted, and then goes to the Google logo (not the G) and just sits there for a couple minutes then turns the device off.
Click to expand...
Click to collapse
Did you leave any modules installed before you updated?
Tulsadiver said:
Did you leave any modules installed before you updated?
Click to expand...
Click to collapse
Ya I did. I got past the bootloop by reflashing the OTA, but are things broken now? Is the fix now to disable any modules, reflash the patched boot.img, and be good to go?
EDIT: can't disable any modules, because there technically aren't any because it's not rooted. I reflashed the patched boot.img, we'll see what happens...
finshan said:
Ya I did. I got past the bootloop by reflashing the OTA, but are things broken now? Is the fix now to disable any modules, reflash the patched boot.img, and be good to go?
Click to expand...
Click to collapse
When rebooting after rooting again, at the Google logo, hold volume down, it'll vibrate and boot to safe mode. Afterwards, just reboot your phone. Modules will be disabled.
Tulsadiver said:
When rebooting after rooting again, at the Google logo, hold volume down, it'll vibrate and boot to safe mode. Afterwards, just reboot your phone. Modules will be disabled.
Click to expand...
Click to collapse
Thank you!
So the patched boot.img did cause it to bootloop again, but doing what you said allowed it to boot normally and keep root. Thanks!!