Followed the instructions here for Rooting and fastbooting to TWRP. Could not locate the Download folder where I put Magisk, so rebooted and put it in a few other folders. Rebooted back to TWRP image and still cannot the Magisk zip or extracted files anywhere. Switched to the B partition and looked around there with no luck. Then went to reboot in TWRP. Now I have a spinning white screen with the "scrolling G" ...15 minutes and counting.
How do I get it out of this stuck boot.
Why can I not find the Download or Android folders in TWRP File Manager where I put Magisk?
Thanks
Downloads from your phone should be in /sdcard/downloads.
If you are stuck with a non-booting system, you need to flash the factory image, you can try to flash it and remove the '-w' from flash-all.bat to keep your data.
Edit: btw to root stock, simply boot twrp image and flash magisk.zip, then reboot system. You can then boot twrp and flash twrp.zip if desired.
boostedduece said:
Downloads from your phone should be in /sdcard/downloads.
If you are stuck with a non-booting system, you need to flash the factory image, you can try to flash it and remove the '-w' from flash-all.bat to keep your data.
Edit: btw to root stock, simply boot twrp image and flash magisk.zip, then reboot system. You can then boot twrp and flash twrp.zip if desired.
Click to expand...
Click to collapse
From what I recall, in the /sdcard/ I had 2 folders /0/ and /00b/? Both had "scrambled" folder names within, nothing that was Download or the like.
So, it's been at least an hour and I still have the scrolling boot screen. In hindsight I recall I went to B before restarting. Can't see device from ADB. Tried the previous Nexus methods of holding power and up/down keys...still white screen G with scroll. Edit: I tried again holding Power and it will now shut off. Holding volume down and power I can get to the boot menu and see Fast Mode. It won't boot on it's own, but I can get to the boot menu. So I'll try connecting again in the morning. Edit #2: after trying recovery and power button a few times the phone booted.
So it looks like I am back to finding Magisk in the Download folder-which I copied from my computer to the Download folder on the 3xl. I installed ES File Explorer and see the zips are in storage/emulated/0/Download but I do not see Download after I reboot with the TWRP image.
There is one /sdcard folder, the other 2 in /storage/emulated/.. have different attributes, but I recommend dealing with /sdcard.
Sounds like it did not decrypt the partition in twrp, that's why the names were garbled.
Holding both volume buttons and power for a while should hard shutdown the device.
You should be able to get to bootloader from power + volume down, flash-all.bat should work from here, you are definitely not bricked though.
Still unable to locate Download Folder
So, I can get the phone to boot and reboot.
From a command prompt:
adb devices (device is available)
adb reboot bootloader
fastboot boot twrp-3.2.2-3-crosshatch.img
Boots to TWRP asking for password, I hit cancel.
It then asks if I want write protection. Initially, I went this route, but tried again allowing full access.
I can see /sdcard/ and 2 folders /0/ and /0bb/, /0bb/ is empty.
when I go into /0/ the folder names are scrambled. Some have sub-folders that are also scrambled.
Why are the names scrambled? Where is my Download folder with my .zip and unzip files?
vette8t7 said:
So, I can get the phone to boot and reboot.
From a command prompt:
adb devices (device is available)
adb reboot bootloader
fastboot boot twrp-3.2.2-3-crosshatch.img
Boots to TWRP asking for password, I hit cancel.
It then asks if I want write protection. Initially, I went this route, but tried again allowing full access.
I can see /sdcard/ and 2 folders /0/ and /0bb/, /0bb/ is empty.
when I go into /0/ the folder names are scrambled. Some have sub-folders that are also scrambled.
Why are the names scrambled? Where is my Download folder with my .zip and unzip files?
Click to expand...
Click to collapse
You have to enter your password that unlocks your phone when you first boot into TWRP so that it can decrypt your phone. Don't hit cancel
vette8t7 said:
So, I can get the phone to boot and reboot.
From a command prompt:
adb devices (device is available)
adb reboot bootloader
fastboot boot twrp-3.2.2-3-crosshatch.img
Boots to TWRP asking for password, I hit cancel.
It then asks if I want write protection. Initially, I went this route, but tried again allowing full access.
I can see /sdcard/ and 2 folders /0/ and /0bb/, /0bb/ is empty.
when I go into /0/ the folder names are scrambled. Some have sub-folders that are also scrambled.
Why are the names scrambled? Where is my Download folder with my .zip and unzip files?
Click to expand...
Click to collapse
TWRP is failing to decrypt your phone. This used to be a big issue, but has been solved for some time. What version of TWRP are you using?
@vette8t7 if you haven't figured this out yet, as others have said, twrp is not decrypting your device. If you haven't you'll need to boot into your system and enable a pin security. Without that twrp doesn't have any info to decrypt your device.
Sent from my [device_name] using XDA-Developers Legacy app
hatdrc said:
You have to enter your password that unlocks your phone when you first boot into TWRP so that it can decrypt your phone. Don't hit cancel
Click to expand...
Click to collapse
Oh man, THAT makes sense. I thought it was wanting me to create one and I didn't want to have to track ANOTHER password.
Okay, I'm in, see Downloads and .zip files!!:good:
hatdrc said:
You have to enter your password that unlocks your phone when you first boot into TWRP so that it can decrypt your phone. Don't hit cancel
Click to expand...
Click to collapse
vette8t7 said:
Oh man, THAT makes sense. I thought it was wanting me to create one and I didn't want to have to track ANOTHER password.
Okay, I'm in, see Downloads and .zip files!!:good:
Click to expand...
Click to collapse
Geez, back in the day I unlocked and rooted my Galaxy Nexus without issue and did most of the same on a Note 4. Didn't really have a need to do either on my Nexus 6p-which I have gone back to using while I straighten out the 3XL. I'd leave the 3XL alone except I need to unlock and root to run the commands to prevent the service check for hotspot on my Verizon GUDP. The 6p has gotten sluggish as of late, thus the 3XL upgrade.
So...I found my Magisk-v18.0.zip (the non-beta) in TWRP after entering the passcode. Hit install. It went through to restart adn white screen scrolling G and now I keep landing on an Android Recovery page:
google/crosshatch/crosshatch
9/PQ1A.181205.006/5108886
user/release-keys
Use volume up/down and power.
Can't load Android System. Your data may be corrupt. If you continue to get this message, you may need to perform a factory reset and erase all user data stored on this device.
Try again
Factory data reset.
So after trying the "Try again" and it try to load and then reboots and tries to load and I come to the same screen above.
I finally tried selecting "Factory data reset" only to come to the same menu.
I was able to run fastboot from the cmd and run twrp-3.2.3-3-crosshatch.img again.
In /sdcard/ I have an empty /obb/ and an empty /TWRP/ folder.
Performed an adb push of magisk.zip and twrp.zip to /0bb/directory and this time performed magisk followed by twrp install and now I get the Google setup window..I don't see Magisk installed.
vette8t7 said:
Geez, back in the day I unlocked and rooted my Galaxy Nexus without issue and did most of the same on a Note 4. Didn't really have a need to do either on my Nexus 6p-which I have gone back to using while I straighten out the 3XL. I'd leave the 3XL alone except I need to unlock and root to run the commands to prevent the service check for hotspot on my Verizon GUDP. The 6p has gotten sluggish as of late, thus the 3XL upgrade.
So...I found my Magisk-v18.0.zip (the non-beta) in TWRP after entering the passcode. Hit install. It went through to restart adn white screen scrolling G and now I keep landing on an Android Recovery page:
google/crosshatch/crosshatch
9/PQ1A.181205.006/5108886
user/release-keys
Use volume up/down and power.
Can't load Android System. Your data may be corrupt. If you continue to get this message, you may need to perform a factory reset and erase all user data stored on this device.
Try again
Factory data reset.
So after trying the "Try again" and it try to load and then reboots and tries to load and I come to the same screen above.
I finally tried selecting "Factory data reset" only to come to the same menu.
Any ideas what I did now and how I get out of it?
Click to expand...
Click to collapse
I'd start fresh by flashing the factory image by running the flash-all batch file. BUT, edit it first to remove the -w you'll see a number of times down. If you don't your device will be wiped. Then boot twrp with fastboot boot, don't flash it. Then install magisk within twrp. If you want to keep twrp permanently then install the twrp zip file. I generally install twrp, then boot back into recovery and then install magisk.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
I'd start fresh by flashing the factory image by running the flash-all batch file. BUT, edit it first to remove the -w you'll see a number of times down. If you don't your device will be wiped. Then boot twrp with fastboot boot, don't flash it. Then install magisk within twrp. If you want to keep twrp permanently then install the twrp zip file. I generally install twrp, then boot back into recovery and then install magisk.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I've gotten to the point where TWRP is installed. If I install TWRP.zip I can get the phone to boot to an image that doesn't appear to have Magisk installed. So I installed the Magisk Manager. It indicates Magisk isn't installed. So I reboot into TWRP select Magisk v18 and install, then reboot system. The phone will go to the Google white screen spin for a bit and then reboot to TWRP. If I install the twrp.zip I can get back into the phone and see Magisk still isn't installed. Ihave tried combinations of installing TWRP.zip then Magisk.zip and vice versa, but I never seem to get Magisk installed.
I've seen mention of the flash-all batch, but I don't seem to have it in anything I have downloaded from these two guides:
https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
I see it in #4 here: https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-xl-android-9-0-pie-unlock-t3857195
so I'll try what you suggest.
vette8t7 said:
I've gotten to the point where TWRP is installed. If I install TWRP.zip I can get the phone to boot to an image that doesn't appear to have Magisk installed. So I installed the Magisk Manager. It indicates Magisk isn't installed. So I reboot into TWRP select Magisk v18 and install, then reboot system. The phone will go to the Google white screen spin for a bit and then reboot to TWRP. If I install the twrp.zip I can get back into the phone and see Magisk still isn't installed. Ihave tried combinations of installing TWRP.zip then Magisk.zip and vice versa, but I never seem to get Magisk installed.
I've seen mention of the flash-all batch, but I don't seem to have it in anything I have downloaded from these two guides:
https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
I see it in #4 here, so I'll try what you suggest.
Click to expand...
Click to collapse
I assume you've found the factory image and extracted the zip file. In there is the flash-all.bat. Edit that, notepad++ is a good editor. Save the file after you've edit it and run that. Make sure you save it or you'll run the unedited version. Then start the process of booting twrp and installing magisk.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
I assume you've found the factory image and extracted the zip file. In there is the flash-all.bat. Edit that, notepad++ is a good editor. Save the file after you've edit it and run that. Make sure you save it or you'll run the unedited version. Then start the process of booting twrp and installing magisk.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yes, found the factory image and extracted the zip. Is started to take the -w out and yes, Notepad++), but decided to leave it in to start fresh. I put the phone in Fastboot. Ran the flash-all, it worked for a while and then indicated there waasn't a recovery.img and a few other things and then "ended" with any key to exit. So I restarted to find everything was still there. So I rebooted to TWRP and installed the Magisk.zip, only to result in the same boot and restart into TWRP. So, convinced the factory image didn't wipe I performed that step again. Boot phone to Fastboot. Opened a command prompt in the image directory. flash-all. It ran for a while complained about the few .img files, but seemed to do more than it did the first time. This time I reloaded the boot loader and fastboot boot twrp.img only to go in and find I still had file in the Download folder (I was expecting to push them from a wipe). So of course when I install magisk.zip and restart it goes to the white google spinning rescreen and eventually restarts back into TWRP.
Your instructions lineup with #4 and 7 or 8 here: https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-xl-android-9-0-pie-unlock-t3857195
For some reason I can't seem to wipe for 1 and ever get Magisk to install 2. Of course my phone has the December OTA update if that has added any new variables here?
I reran this flash-all again to a log file (attached).
vette8t7 said:
Yes, found the factory image and extracted the zip. Is started to take the -w out and yes, Notepad++), but decided to leave it in to start fresh. I put the phone in Fastboot. Ran the flash-all, it worked for a while and then indicated there waasn't a recovery.img and a few other things and then "ended" with any key to exit. So I restarted to find everything was still there. So I rebooted to TWRP and installed the Magisk.zip, only to result in the same boot and restart into TWRP. So, convinced the factory image didn't wipe I performed that step again. Boot phone to Fastboot. Opened a command prompt in the image directory. flash-all. It ran for a while complained about the few .img files, but seemed to do more than it did the first time. This time I reloaded the boot loader and fastboot boot twrp.img only to go in and find I still had file in the Download folder (I was expecting to push them from a wipe). So of course when I install magisk.zip and restart it goes to the white google spinning rescreen and eventually restarts back into TWRP.
Your instructions lineup with #4 and 7 or 8 here: https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-xl-android-9-0-pie-unlock-t3857195
For some reason I can't seem to wipe for 1 and ever get Magisk to install 2. Of course my phone has the December OTA update if that has added any new variables here?
I reran this flash-all again to a log file (attached).
Click to expand...
Click to collapse
- first, make sure you have the latest SDK Platform-tools r28.0.1 (see guide 'Prerequisites c.' for link).
- extract the December factory image in the Platform-tools folder.
- Open a command prompt in the Platform-tools folder.
- type flash-all at the prompt.
- when it finishes, do #8 for root.
Homeboy76 said:
- first, make sure you have the latest SDK Platform-tools r28.0.1 (see guide 'Prerequisites c.' for link).
- extract the December factory image in the Platform-tools folder.
- Open a command prompt in the Platform-tools folder.
- type flash-all at the prompt.
- when it finishes, do #8 for root.
Click to expand...
Click to collapse
I have the r28.0.1
I was researching the Image and I had downloaded and used the A1.docomo, which, as jd1639 pointed out in another thread is for japanese phones. I've just finished downloading the non-docomo for December and see where I get.
Oh, now I see what I am doing wrong. The image .zip needs to be extracted into the platform folder. I noticed you said run the command from "platform-tools" folder.
vette8t7 said:
I have the r28.0.1
I was researching the Image and I had downloaded and used the A1.docomo, which, as jd1639 pointed out in another thread is for japanese phones. I've just finished downloading the non-docomo for December and see where I get.
Click to expand...
Click to collapse
If you have r28.0.1 where is the Platform-tools folder?
---------- Post added at 05:54 AM ---------- Previous post was at 05:50 AM ----------
vette8t7 said:
I have the r28.0.1
I was researching the Image and I had downloaded and used the A1.docomo, which, as jd1639 pointed out in another thread is for japanese phones. I've just finished downloading the non-docomo for December and see where I get.
Oh, now I see what I am doing wrong. The image .zip needs to be extracted into the platform folder. I noticed you said run the command from "platform-tools" folder.
Click to expand...
Click to collapse
Yes, the Factory image zip needs to be extracted to the Platform-tools folder.
Homeboy76 said:
If you have r28.0.1 where is the Platform-tools folder?
C:\adb\platform-tools_r28.0.1-windows\platform-tools
Within that is adb, fastboot, twrp-pixel-installer-crosshatch-3.2.3-3.img (renamed twrp.img), december factory image (extracted) as well as the Magisk-v18.0.zip and twrp.zip (for copying or pushing)
---------- Post added at 05:54 AM ---------- Previous post was at 05:50 AM ----------
Yes, the Factory image zip needs to be extracted to the Platform-tools folder.
Click to expand...
Click to collapse
So once the factory image is done, I go through setup (skipping through most for later) to get the usb debugging enabled and copy Magisk.zip and twrp.zip.
adb reboot bootloader
fastboot boot twrp.img
put in passcode
Swiped to allow for modifications
First time I just installed the magisk.zip only to have it reboot twice into the loop of my #10 post again.
The second time I repeated the whole factory image process up to fastbooting twrp.img and this time installed twrp.zip, reboot recovery, install Magisk-v18.0.zip. Reboot system. It boots and No Magisk in the app tray! Err...well now it is there and it shows Magisk installed!
Holy Moly what a PITA!! On a positive note, I kind of refreshed some of this stuff I hadn't done in years :good:
I got stuck a couple of months back when my wife's nexus 6p died (not battery-which I later swapped into mine), something with the processor board. I got a Verizon 3XL with the locked bootloaderL...so if anything ever develops there, I can root that phone for the GUDP hotspot as well.
I followed the steps here: https://forum.xda-developers.com/pixel-3-xl/how-to/how-to-native-tethering-rooted-pixel-3-t3858662
So far, so good. Great Success! Thanks for your help!
homeboy76 said:
If you have r28.0.1 where is the Platform-tools folder?
Click to expand...
Click to collapse
vette8t7 said:
C\adb\platform-tools_r28.0.1-windows\platform-tools
Within that is adb, fastboot, twrp-pixel-installer-crosshatch-3.2.3-3.img (renamed twrp.img), december factory image (extracted) as well as the Magisk-v18.0.zip and twrp.zip (for copying or pushing)
Click to expand...
Click to collapse
"twrp-pixel-installer-crosshatch-3.2.3-3.img (renamed twrp.img)"
I think you mean 'twrp-3.2.3-3-crosshatch.img (renamed twrp.img)
vette8t7 said:
...The second time I repeated the whole factory image process up to fastbooting twrp.img and this time installed twrp.zip, reboot recovery, install Magisk-v18.0.zip. Reboot system. It boots and No Magisk in the app tray! Err...well now it is there and it shows Magisk installed!...
Click to expand...
Click to collapse
@vette8t7
Yes
Related
I have a nexus 7 2013 LTE build KOT49H
I initially managed to unlock and root using nrt 1.8...everything was perfect...there was some confusion getting adb setup though..
(for WugFresh...your instructions are fantastic but you should add a line to "check your device for the message to accept a connection for adb and select ok"...I found myself waiting and waiting, staring at my computer screen thinking that the nrt was hanging when all I needed to do was press "ok" on my device.)
Like I said...everything was perfect but I had to go one step further...
I then installed cyanogenmod 10.2 using twrp...tihs also went fine but I hated it and wanted to get back to my original google os. I had a really hard time getting adb set up once cyanogen was installed but once I finally did I was able to get back to stock again using nrt 1.8.
So now I'm back to stock image KOT49H. Everything runs fine and I see the unlocked logo when I boot so I assume I'm still unlocked.
Here's the problem..
When I try to root now, (I always run the NRT driver test until I get "success" message first) my device hangs on the "Booting modified boot.img to enable..." message.
And I mean hangs...can't even power it down without popping the cover and disconnecting the battery! Thankfully this gets me back to a running device but I still want to root this thing.
Any idea what might be wrong or where I should go to from here?
Thanks for any help you can suggest!
Did you re-enable USB debugging? Another thing is to switch to PTP mode instead of MTP. If none of that is the issue, it may be drivers, fire up wugs toolkit, hook up your device, and click the button "Full Driver Installation Guide", skip to Step 3 tab, and run the "Full Driver Test", if it fails then you're going to need to run through the steps in that "Full Driver Installation Guide, going through each step.
Well all you need to do for root is flash supersu.zip binary. If you have twrp on your device, boot to recovery. When you power on, hold down the volume down button also. When in boot loader mode, select recovery. If its not booting, you could just wipe to factory reset. Flash your supersu zip you'll be good.
Sent from my Nexus 7 using xda app-developers app
mdamaged said:
Did you re-enable USB debugging? Another thing is to switch to PTP mode instead of MTP. If none of that is the issue, it may be drivers, fire up wugs toolkit, hook up your device, and click the button "Full Driver Installation Guide", skip to Step 3 tab, and run the "Full Driver Test", if it fails then you're going to need to run through the steps in that "Full Driver Installation Guide, going through each step.
Click to expand...
Click to collapse
Thanks for the response...
All these check...I do have to switch to PTP to get adb functional and I do get success on the full driver test before I try rooting...device still hangs at "Booting modified boot.img to enable running privileged commands" message and then wont power down without disconnecting battery...
Which recovery are you on stock or still on twrp? If still on twrp, you might want to try flashing the supersu.zip yourself, just get the latest SuperSU put it on your device, and boot into twrp and manually flash it like datallboy suggests, this eliminates the PC/drivers/usb connection as a possible issue.
If you are on stock recovery either flash twrp, or if you want to keep stock recovery, you can boot into twrp temporarily without replacing the stock recovery.
datallboy said:
Well all you need to do for root is flash supersu.zip binary. If you have twrp on your device, boot to recovery. When you power on, hold down the volume down button also. When in boot loader mode, select recovery. If its not booting, you could just wipe to factory reset. Flash your supersu zip you'll be good.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the suggestions...
I lost twrp when I went back to stock build.
Sorry...I'm real green at all of this...
You think I should:
power up to fastboot mode...select boot loader mode...then select recovery to see if it boots?
You need to be real clear for me, I'm a total newb
I would need a link to thorough instructions for wiping to factory reset and flashing the supersu.zip...I do have adt installed and have my path modified so that I can run instructions like "adb devices" in a command window but I'm unclear as to where to place files so they will be seen if I try to flash them via adt. (like I say...this is all new to me and I'm not even sure if that last sentence makes sense)
mdamaged said:
Which recovery are you on stock or still on twrp? If still on twrp, you might want to try flashing the supersu.zip yourself, just get the latest SuperSU put it on your device, and boot into twrp and manually flash it like datallboy suggests, this eliminates the PC/drivers/usb connection as a possible issue.
If you are on stock recovery either flash twrp, or if you want to keep stock recovery, you can boot into twrp temporarily without replacing the stock recovery.
Click to expand...
Click to collapse
Thanks for responding!
TWRP was wiped when I went back to stock build...I'm assuming I have stock recovery now but when your device freezes in fastboot mode and wont power down without pulling the battery you cable you gotta wonder if you have any recovery at all!!!
I'll need instruction on how to flash twrp again...but I believe that this is the step that WugFresh's NRT is trying to do when the device freezes.
SMELZBAD said:
Thanks for responding!
TWRP was wiped when I went back to stock build...I'm assuming I have stock recovery now but when your device freezes in fastboot mode and wont power down without pulling the battery you cable you gotta wonder if you have any recovery at all!!!
I'll need instruction on how to flash twrp again...but I believe that this is the step that WugFresh's NRT is trying to do when the device freezes.
Click to expand...
Click to collapse
I typed this up on the fly so pardon any mistakes, there's more than one way to do this, but I'm basing this on already having wugs toolkit installed and updated and configured for your device on the PC you're going to do this on.
Plug device in, enable USB debugging mode, connect to PC, verify you can access your device through the PC, get the latest UPDATE-SuperSU-v1.XX zip, save it to your device (in the root of the sdcard).
EDIT: OR, even better, you can just boot the device and download it with chrome or whatever and save it to the sdcard, then you can continue:
Open windows explorer and navigate to (assuming you picked the default install directory):
C:\Program Files (x86)\WugFresh Development\data
...in that window, hold down shift, right click, select "Open command windows here", in it, type:
adb devices
...if nothing shows up post back (screenshot would be nice), if your device shows up, then open another windows explorer window and navigate to:
C:\Program Files (x86)\WugFresh Development\data\Recovery_Custom\TWRP\
...and copy the img (mine is openrecovery-twrp-2.6.3.1-flo.img) file you see in there to the other explorer window I told you to open earlier, now assuming you put the SuperSU file on your device in the root folder of the device, you should be able to do:
fastboot boot openrecovery-twrp-2.6.3.1-flo.img
This should reboot your device and boot twrp (this method does not replace whatever recovery you have on there now).
If you want to flash twrp and replace your current recovery you'd want to do:
fastboot flash recovery openrecovery-twrp-2.6.3.1-flo.img
Then once in twrp recovery you can select flash file, navigate to the UPDATE-SuperSU-v1.XX.zip file on your device, select it, and swipe to flash, reboot, run/install busybox and see what happens..it will let you know if there is a problem with root.
mdamaged said:
I typed this up on the fly so pardon any mistakes, there's more than one way to do this, but I'm basing this on already having wugs toolkit installed and updated and configured for your device on the PC you're going to do this on.
Plug device in, enable USB debugging mode, connect to PC, verify you can access your device through the PC, get the latest zip, save it to your device (in the root of the sdcard).
Open windows explorer and navigate to (assuming you picked the default install directory):
C:\Program Files (x86)\WugFresh Development\data
...in that window, hold down shift, right click, select "Open command windows here", in it, type:
adb devices
...if nothing shows up post back (screenshot would be nice), if your device shows up, then open another windows explorer window and navigate to:
C:\Program Files (x86)\WugFresh Development\data\Recovery_Custom\TWRP\
...and copy the img (mine is openrecovery-twrp-2.6.3.1-flo.img) file you see in there to the other explorer window I told you to open earlier, now assuming you put the SuperSU file on your device in the root folder of the device, you should be able to do:
fastboot boot openrecovery-twrp-2.6.3.1-flo.img
This should reboot your device and boot twrp (this method does not replace whatever recovery you have on there now).
If you want to flash twrp and replace your current recovery you'd want to do:
fastboot flash recovery openrecovery-twrp-2.6.3.1-flo.img
Then once in twrp recovery you can select flash file, navigate to the UPDATE-SuperSU-v1.XX.zip file on your device, select it, and swipe to flash, reboot, run busybox and see what happens.
Click to expand...
Click to collapse
Thanks a ton for the instruction!
I'm starting to make sense of this.
Found some other instruction for getting twrp back on the device which I think I'll try before flashing the superSU:
They're exactly what you're describing. I've also figured out where the flashboot.exe stuff is on my computer and added twp.img file there. I'' try getting twrp on and then I'll flash the superSU via twrp.
It'll probably be tomorrow before I get a chance to try all this but I'll be sure to post back once I do.
I'm still in the dark as to why missing this superSU thingy would be causing the device to freeze up the way it does when I try to root using WugFresh's NRT...I thought that flashing twrp and superSU is what the NRT is trying to do when it tries to root my device???
Anyway gtg...thanks all for assisting...I'll post back after the flash attempts...hopefully with happy news!
SMELZBAD said:
Thanks a ton for the instruction!
I'm starting to make sense of this.
Found some other instruction for getting twrp back on the device which I think I'll try before flashing the superSU:
They're exactly what you're describing. I've also figured out where the flashboot.exe stuff is on my computer and added twp.img file there. I'' try getting twrp on and then I'll flash the superSU via twrp.
It'll probably be tomorrow before I get a chance to try all this but I'll be sure to post back once I do.
I'm still in the dark as to why missing this superSU thingy would be causing the device to freeze up the way it does when I try to root using WugFresh's NRT...I thought that flashing twrp and superSU is what the NRT is trying to do when it tries to root my device???
Anyway gtg...thanks all for assisting...I'll post back after the flash attempts...hopefully with happy news!
Click to expand...
Click to collapse
Wug's toolkit is doing exactly that, the main difference in doing it manually is we get to see where the problem is.
If this fails then I would probably say you should backup anything on your device you don't want wiped, and try one click restore and try rooting again.
Good luck.
mdamaged said:
I typed this up on the fly so pardon any mistakes, there's more than one way to do this, but I'm basing this on already having wugs toolkit installed and updated and configured for your device on the PC you're going to do this on.
Plug device in, enable USB debugging mode, connect to PC, verify you can access your device through the PC, get the latest UPDATE-SuperSU-v1.XX zip, save it to your device (in the root of the sdcard).
EDIT: OR, even better, you can just boot the device and download it with chrome or whatever and save it to the sdcard, then you can continue:
Open windows explorer and navigate to (assuming you picked the default install directory):
C:\Program Files (x86)\WugFresh Development\data
...in that window, hold down shift, right click, select "Open command windows here", in it, type:
adb devices
...if nothing shows up post back (screenshot would be nice), if your device shows up, then open another windows explorer window and navigate to:
C:\Program Files (x86)\WugFresh Development\data\Recovery_Custom\TWRP\
...and copy the img (mine is openrecovery-twrp-2.6.3.1-flo.img) file you see in there to the other explorer window I told you to open earlier, now assuming you put the SuperSU file on your device in the root folder of the device, you should be able to do:
fastboot boot openrecovery-twrp-2.6.3.1-flo.img
This should reboot your device and boot twrp (this method does not replace whatever recovery you have on there now).
If you want to flash twrp and replace your current recovery you'd want to do:
fastboot flash recovery openrecovery-twrp-2.6.3.1-flo.img
Then once in twrp recovery you can select flash file, navigate to the UPDATE-SuperSU-v1.XX.zip file on your device, select it, and swipe to flash, reboot, run/install busybox and see what happens..it will let you know if there is a problem with root.
Click to expand...
Click to collapse
Followed your instructions...everything went as it should until I got to:
fastboot boot openrecovery-twrp-2.6.3.1-deb.img
instead of rebooting the device I only got waiting for device message in command window...
is device supposed to be put in bootloader mode before entering this instruction maybe???
okay I got twrp to flash...took like .7 seconds so I guess it was already on there...
when I tried to flash UPDATESuperSU (and by flash I assume you mean install???)
I get:
Updating partition details...
E: Unable to open zip file.
Error flashing zip ' /sdcard/UPDATE-SuperSU-v1.89.zip
Updating partition details...
and the in red underneath: Failed
and the 3 twrp button choices of home Wipe cache/davlik and Reboot System
I selected reboot system and then got message "this device is not rooted swipe to install SuperSU now
I swiped...and the system has rebooted and I now have SuperSU installer app icon in apps bit after running root checker I get device is not properly rooted message
I then ran the SuperSU installer app and it gave me an option to update via the play store...which I did...then ran SuperuserSU which was now updated and installed and it completed rooting...after rebooting the device Root Checker now shows device properly rooted!
THANKS A TON GUYS!!!
SMELZBAD said:
okay I got twrp to flash...took like .7 seconds so I guess it was already on there...
when I tried to flash UPDATESuperSU (and by flash I assume you mean install???)
I get:
Updating partition details...
E: Unable to open zip file.
Error flashing zip ' /sdcard/UPDATE-SuperSU-v1.89.zip
Updating partition details...
and the in red underneath: Failed
and the 3 twrp button choices of home Wipe cache/davlik and Reboot System
I selected reboot system and then got message "this device is not rooted swipe to install SuperSU now
I swiped...and the system has rebooted and I now have SuperSU installer app icon in apps bit after running root checker I get device is not properly rooted message
I then ran the SuperSU installer app and it gave me an option to update via the play store...which I did...then ran SuperuserSU which was now updated and installed and it completed rooting...after rebooting the device Root Checker now shows device properly rooted!
THANKS A TON GUYS!!!
Click to expand...
Click to collapse
Curious. It sounds like a permissions problem, not sure if fix permissions would have helped (no need to try if it's working as it should).
Oh well, glad to help and that it's sorted.
mdamaged said:
Curious. It sounds like a permissions problem, not sure if fix permissions would have helped (no need to try if it's working as it should).
Oh well, glad to help and that it's sorted.
Click to expand...
Click to collapse
Ya...something likely still abit wacky...I'll be sure to post if anything weird starts happening but for now all is good...I'm definitely rooted though...I was just able to mount a flash drive via Stick Mount and run a video off of it!
Hello to all. I have just unlocked bootloader, installed twrp and su. After everything booted up properly, I went to install an adblocker zip file, however once it booted into twrp it had no download folder, as well as when I went to reboot system it told me I had no os installed.. I'm a bit confused as to what to do now.. My apologies for clogging the thread if this has been answered before..
Edit: do I adb side load an image file or OS? I'm afraid of bricking this phone as I don't know how to continue from this point..
Which guide did you use to do all of this? I will help us understand where you started
Mrbobrowitz said:
Which guide did you use to do all of this? I will help us understand where you started
Click to expand...
Click to collapse
Hi thanks for the reply. This link right here:
http://www.androidsage.com/2016/11/...timate-guide-root-twrp-and-bootloader-unlock/
Steps I followed:
1 unlocked bootloader
2 Download the below files TWRP and Root files for Google Pixel & Pixel XL
Official TWRP for Pixel phones → Download |
Files: twrp-pixel-installer-sailfish-3.0.2-0-alpha1.zip 7.6M
twrp-3.0.2-0-alpha1-fastboot-sailfish.img 25M
Flash SuperSU 2.78 SRF4 → Download | File: SR4-SuperSU-v2.78-SR4-20161115184928.zip
Twrp install instructions:
Step 1: Download the TWRP recovery and latest SuperSU zip file for your Google Pixel and Pixel XL devices. There are 2 TWRP files with .zip and .img extensions. You will need both. You don’t need to extract the files, just place all the files on your PC as well as your Android phone’s internal storage where you can easily locate it.
Step 2: Make sure that you setup ADB and Fastboot on your PC and gone through all the prerequisites from above.
Step 3: Now plug in the Pixel device to the computer and open a command prompt or terminal on your PC to the window where TWRP.zip file is located. (See above to know how to open cmd)
Step 4: Boot your Android device into the bootloader or Fastboot mode. To do so, issue the following command through cmd or terminal. You can also manually boot into it using the hard key combination like Power+Volume Down while the device is turned off. Meanwhile, use code:
adb reboot-bootloader
Step 5: Now issue the following command in the command prompt to check your device connectivity
fastboot devices
Step 6: Now issue the following command to temporarily boot up the TWRP image.
fastboot boot path/to/twrp.img
Note: If you have installed our recommend quick 15 second ADB & fastboot installer, you do not need to insert the complete file path. Simply go to where the TWRP image file is and issue command “fastboot boot twrp.img” Otherwise, note that “path/to/” is the actual directory for the TWRP image file. Use fastboot boot and not fastboot flash and that the file you are booting is not the zip file.
Simply After that, TWRP will be accessible to you no matter which active partition slots are being used.
Step 7: After that fastboot command, you will be rebooted into a temporary TWRP recovery interface. To make it permanent, use the TWRP interface to navigate to and install the TWRP.zip file. This is just like using TWRP to flash custom ROMS and SuperSU.
Once the installation completes, you can now enjoy your new firmware. Alternatively, while, on Mac OS, you can issue “./fastboot boot path/to/twrp.img” command or on Linux type “sudo fastboot path/to/twrp.img” to flash the TWRP. For detailed tutorial and alternate methods to flash the TWRP recovery, click here.
Now it’s time to root your Google Pixel with latest SuperSU 2.78 SR4.
How to root :
Place the latest SuperSU 2.78 SR4 package onto your device’s internal storage or SDcard.
Boot your device into the custom TWRP recovery and tap install. For that, turn off your device completely and hold volume down and power buttons for a few seconds.
Once into TWRP tap the install button and select the SuperSU file.
Swipe the confirmation action below to start flashing.
Once done. reboot to system.
You can boot into the TWRP recovery by issuing the following command:
adb reboot recovery
There is an alpha 2 for twrp now. I would try installing this and seeing if it works. If not, you can simply flash the latest factory image and "start over". Granted you would lose any data that you might have had not backed up on your device, but youre not out of luck!
I wouldn't waste your time. Just flash the factory image and start all over. You managed to wipe the Rom off your device
Smallsmx3 said:
I wouldn't waste your time. Just flash the factory image and start all over. You managed to wipe the Rom off your device
Click to expand...
Click to collapse
Mrbobrowitz said:
There is an alpha 2 for twrp now. I would try installing this and seeing if it works. If not, you can simply flash the latest factory image and "start over". Granted you would lose any data that you might have had not backed up on your device, but youre not out of luck!
Click to expand...
Click to collapse
Thanks guys, I actually have installed the alpha 2 twrp. I guess my question is how do I proceed? I'm in twrp and my PC does not see the device when typing adb devices.. Within twrp it says no os installed... What do I do here?
So how do I "start over" or "flash factory image" from the state that I'm in?
mazubo said:
Thanks guys, I actually have installed the alpha 2 twrp. I guess my question is how do I proceed? I'm in twrp and my PC does not see the device when typing adb devices.. Within twrp it says no os installed... What do I do here?
So how do I "start over" or "flash factory image" from the state that I'm in?
Click to expand...
Click to collapse
You should be able to boot into fastboot
Smallsmx3 said:
You should be able to boot into fastboot
Click to expand...
Click to collapse
Ok, and if that works then flash 7.1.1? Then twrp alpha then root via SuperSU flash?
A side question here is how did I wipe the os/from off the phone? I'm stumped on that one..
mazubo said:
Ok, and if that works then flash 7.1.1? Then twrp alpha then root via SuperSU flash?
A side question here is how did I wipe the os/from off the phone? I'm stumped on that one..
Click to expand...
Click to collapse
I couldn't tell you! I've had it happen to me before a couple times. But yes if you can get into fastboot you should be able to fastboot flash a factory image. Then go and flash TWRP and root
Smallsmx3 said:
I couldn't tell you! I've had it happen to me before a couple times. But yes if you can get into fastboot you should be able to fastboot flash a factory image. Then go and flash TWRP and root
Click to expand...
Click to collapse
Ok thanks. I've been able to reboot to bootloader...
I've figured it out via fast boot. The phone is back in action, however not sure how it got wiped initially.. Thanks everyone!
mazubo said:
Ok, and if that works then flash 7.1.1? Then twrp alpha then root via SuperSU flash?
A side question here is how did I wipe the os/from off the phone? I'm stumped on that one..
Click to expand...
Click to collapse
mazubo said:
I've figured it out via fast boot. The phone is back in action, however not sure how it got wiped initially.. Thanks everyone!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Off the top of my head... Probably selected the wrong "slot" maybe?
Remember on this device there are two locations for the ROM. Slot A and B. If you select the wrong one it will show no OS.
As far as the download folder missing... I know its mute at this point, but that has to do with the FBE (File Based Encryption). Make sure TWRP asks you for your Pattern Password. If you do not have one I would consider setting one. That way you know for fact that the File system will get decrypted properly. Also reports say you may have to reboot TWRP twice to get it to decrypt as well.
Hello everyone,
So today is the day (at least for me) that I want to try applying the Jan OTA to my Pixel 2 XL. I am currently using Magisk and ElementalX kernel and was wondering if anyone has tried this yet (I know, the OTA just came out)?
If someone has an idea on the process to do this please let me know.
Thanks!
ilatimer1 said:
Hello everyone,
So today is the day (at least for me) that I want to try applying the Jan OTA to my Pixel 2 XL. I am currently using Magisk and ElementalX kernel and was wondering if anyone has tried this yet (I know, the OTA just came out)?
If someone has an idea on the process to do this please let me know.
Thanks!
Click to expand...
Click to collapse
Kernel, TWRP and Magisk get overwritten by the OTA. You need to reinstall.
Also I'd recommend to disable all Substratum themes before flashing - for me this led to a Bootpool...
ilatimer1 said:
Hello everyone, So today is the day (at least for me) that I want to try applying the Jan OTA to my Pixel 2 XL. I am currently using Magisk and ElementalX kernel and was wondering if anyone has tried this yet (I know, the OTA just came out)? If someone has an idea on the process to do this please let me know. Thanks!
Click to expand...
Click to collapse
I recommend using the full image (not OTA) downloaded from Google. Extract the files from the zip into your ADB folder, open up flash-all.bat with a text editor and remove the -w (wipe) switch from the script. Save. Then just execute that file from a fastboot prompt. You will not lose data or settings, but you will lose TWRP, kernel & Magisk. When the script finishes running, boot back into fastboot mode (bootloader) and from your PC, fastboot boot twrp. When it loads queue up (add zips) TWRP.zip, Kernel.zip, Magisk.zip and let her rip. Reboot to system and everything will be normal. Just make sure you have those three files (latest versions) on your phone AND the twrp.img on your PC so you can boot to it. Takes about 3 minutes if you have all the files in place before starting.
v12xke said:
I recommend using the full image (not OTA) downloaded from Google. Extract the files from the zip into your ADB folder, open up flash-all.bat with a text editor and remove the -w (wipe) switch from the script. Save. Then just execute that file from a fastboot prompt. You will not lose data or settings, but you will lose TWRP, kernel & Magisk. When the script finishes running, boot back into fastboot mode (bootloader) and from your PC, fastboot boot twrp. When it loads queue up (add zips) TWRP.zip, Kernel.zip, Magisk.zip and let her rip. Reboot to system and everything will be normal. Just make sure you have those three files (latest versions) on your phone AND the twrp.img on your PC so you can boot to it. Takes about 3 minutes if you have all the files in place before starting.
Click to expand...
Click to collapse
What's the difference between this step and sideloading the OTA?
Edit: nevermind. Realized you'd flash-all without the -w if you have TWRP.
peoplesindian said:
What's the difference between this step and sideloading the OTA?
Edit: nevermind. Realized you'd flash-all without the -w if you have TWRP.
Click to expand...
Click to collapse
Yes, OTA's fail to execute if you have modified the boot or system partition. An OTA is an incremental only update that selectively writes certain files and is (usually) much, much smaller. This is appropriate for a stock, unmodified device. Lots of people get tired of waiting for the OTA to come, and so they just update manually by sideloading the OTA through the stock recovery (over adb). Nothing wrong with that, and it this will sometimes bring a phone back from bootlooping or other serious problems like FC's and crashing.
A full image contains the full partition images and they are written to the device fully and unconditionally via fastboot. You can only flash a full image if your bootloader is unlocked. It essentially erases the partitions by overwriting the entire contents from beginning to end. Some would argue this more "complete" method is less likely to result in errors, or corrupt files. Removing the -w switch from the batch file script prevents the script from overwriting the userdata partition where all your media, user apps and settings are. Some call this "dirty" flashing.
v12xke said:
I recommend using the full image (not OTA) downloaded from Google. Extract the files from the zip into your ADB folder, open up flash-all.bat with a text editor and remove the -w (wipe) switch from the script. Save. Then just execute that file from a fastboot prompt. You will not lose data or settings, but you will lose TWRP, kernel & Magisk. When the script finishes running, boot back into fastboot mode (bootloader) and from your PC, fastboot boot twrp. When it loads queue up (add zips) TWRP.zip, Kernel.zip, Magisk.zip and let her rip. Reboot to system and everything will be normal. Just make sure you have those three files (latest versions) on your phone AND the twrp.img on your PC so you can boot to it. Takes about 3 minutes if you have all the files in place before starting.
Click to expand...
Click to collapse
did exactly this, and all is fine.
otonieru said:
did exactly this, and all is fine.
Click to expand...
Click to collapse
Same
trim81 said:
Same
Click to expand...
Click to collapse
Interesting that Google seems to claim that updating with the OTA should create less problems with this January update:
https://9to5google.com/2018/01/02/psa-google-pixel-2-users-lag-sideload-jan-sec-update-fix/
xclub_101 said:
Interesting that Google seems to claim that updating with the OTA should create less problems with this January update:
https://9to5google.com/2018/01/02/psa-google-pixel-2-users-lag-sideload-jan-sec-update-fix/
Click to expand...
Click to collapse
That article is quite dubious with no source about google confirming the issue :silly:
v12xke said:
Then just execute that file from a fastboot prompt.
Click to expand...
Click to collapse
REALLY dumb question, but how do you execute a .bat from fastboot? Or do you mean with the phone in bootloader/fastboot mode, run the modified .bat?
EDIT: Never mind... put the phone in Bootloader/fastboot mode. Ran the modified .BAT from command prompt within the Platform-tools folder.
I did it last night with no issues. The process is pretty simple.
1) adb reboot bootloader
2) fastboot flash boot /location/of/december/boot.img
3) fastboot flash dtbo /location/of/december/dtbo.img
4) reboot
5) allow the OTA to install
6) adb reboot bootloader
7) fastboot boot twrp
8) install TWRP then custom kernel then Magisk
7) reboot
v12xke said:
I recommend using the full image (not OTA) downloaded from Google. Extract the files from the zip into your ADB folder, open up flash-all.bat with a text editor and remove the -w (wipe) switch from the script. Save. Then just execute that file from a fastboot prompt. You will not lose data or settings, but you will lose TWRP, kernel & Magisk. When the script finishes running, boot back into fastboot mode (bootloader) and from your PC, fastboot boot twrp. When it loads queue up (add zips) TWRP.zip, Kernel.zip, Magisk.zip and let her rip. Reboot to system and everything will be normal. Just make sure you have those three files (latest versions) on your phone AND the twrp.img on your PC so you can boot to it. Takes about 3 minutes if you have all the files in place before starting.
Click to expand...
Click to collapse
I followed this and everything is installed perfectly with root.
Thank you ??
sn0warmy said:
I did it last night with no issues. The process is pretty simple.
1) adb reboot bootloader
2) fastboot flash boot /location/of/december/boot.img
3) fastboot flash dtbo /location/of/december/dtbo.img
4) reboot
5) allow the OTA to install
6) adb reboot bootloader
7) fastboot boot twrp
8) install TWRP then custom kernel then Magisk
7) reboot
Click to expand...
Click to collapse
Slow internet here, you mind uploading the boot and dtbo.img?
sn0warmy said:
I did it last night with no issues. The process is pretty simple.
1) adb reboot bootloader
2) fastboot flash boot /location/of/december/boot.img
3) fastboot flash dtbo /location/of/december/dtbo.img
4) reboot
5) allow the OTA to install
6) adb reboot bootloader
7) fastboot boot twrp
8) install TWRP then custom kernel then Magisk
7) reboot
Click to expand...
Click to collapse
I like this idea better than the flash all, but forgive me as I haven't flashed any Android 8.1 devices yet.
Is dtbo the new name for what used to be called system?
Long story short, I bought my awesome Pixel 2 XL back in December, right away I unlocked the bootloader, installed TWRP Recovery and rooted it. Since then I have done nothing to the phone , besides app updates, but never updated top the latest security patches pr anything. Partly because being rooted can't take OTA updates, and didn't want to wipe anything flashing new updates.
Tonight, I wanted to get on the latest, I was currently on 3.2.1.0, so I downloaded the 3.2..1.2 zip, rebooted into Recovery, and flashed the zip, and rebooted into Recovery again, all good, on the latest current TWRP version.
I press reboot system, but it keeps going back into Recovery, every time, always reboots back into Recovery for some strange reason ? Doesn't load the system. So I select the other partition A, I was on B, I put it in A, select reboot system, and it just hangs on the white Goggle screen FOREVER. I then get back into Recovery, now I can't even get into Recovery, the swipe right feature not working, acting like it's not registering my input, I can't swipe the arrow to move it. Now it's just stuck on the opening page in Recovery.
Now what ?
Zorachus said:
Long story short, I bought my awesome Pixel 2 XL back in December, right away I unlocked the bootloader, installed TWRP Recovery and rooted it. Since then I have done nothing to the phone , besides app updates, but never updated top the latest security patches pr anything. Partly because being rooted can't take OTA updates, and didn't want to wipe anything flashing new updates.
Tonight, I wanted to get on the latest, I was currently on 3.2.1.0, so I downloaded the 3.2..1.2 zip, rebooted into Recovery, and flashed the zip, and rebooted into Recovery again, all good, on the latest current TWRP version.
I press reboot system, but it keeps going back into Recovery, every time, always reboots back into Recovery for some strange reason ? Doesn't load the system. So I select the other partition A, I was on B, I put it in A, select reboot system, and it just hangs on the white Goggle screen FOREVER. I then get back into Recovery, now I can't even get into Recovery, the swipe right feature not working, acting like it's not registering my input, I can't swipe the arrow to move it. Now it's just stuck on the opening page in Recovery.
Now what ?
Click to expand...
Click to collapse
Fastboot the boot.img from whatever build your on now and let it boot up. That will remove twrp, then you can go back and fastboot twrp again.
[delete
Badger50 said:
Fastboot the boot.img from whatever build your on now and let it boot up. That will remove twrp, then you can go back and fastboot twrp again.
Click to expand...
Click to collapse
Where do I get the December boot.img ?
Zorachus said:
Where do I get the December boot.img ?
Click to expand...
Click to collapse
Go here....https://developers.google.com/android/images
Download the December factory image, extract it, then extract the other zip you'll find, and in there you'll find the boot.img. Then place that in your platform-tools folder and run...fastboot boot boot.img
Then type fastboot reboot, and let the phone boot up. Then go back and fastboot the twrp.img
Once in twrp, flash the twrp installer zip, then custom kernel if you want, and then magisk for root if you want. Question, why are you still on the December build???
I think if you just flash magisk it will boot again. If you were rooted. Someone posted on the twrp thread. To get touch back on twrp just have to adb reboot recovery. Might worth a try.
Sent from my Pixel 2 XL using Tapatalk
Badger50 said:
Go here....https://developers.google.com/android/images
Download the December factory image, extract it, then extract the other zip you'll find, and in there you'll find the boot.img. Then place that in your platform-tools folder and run...fastboot boot boot.img
Then type fastboot reboot, and let the phone boot up. Then go back and fastboot the twrp.img
Once in twrp, flash the twrp installer zip, then custom kernel if you want, and then magisk for root if you want. Question, why are you still on the December build???
Click to expand...
Click to collapse
Ok I am downloading the 1.6GB December file. I will then extract that, and only need to grab the boot.img file from there ? What do you mean when you say "then extract the other zip you'll find" ?
And then connect my phone to my PC, and open Command Prompt, and run these lines. I need to be in fastboot mode I assume ?
"
Zorachus said:
Ok I am downloading the 1.6GB December file. I will then extract that, and only need to grab the boot.img file from there ? What do you mean when you say "then extract the other zip you'll find" ?
And then connect my phone to my PC, and open Command Prompt, and run these lines. I need to be in fastboot mode I assume ?
"
Click to expand...
Click to collapse
There's another large zip that you'll find after you extract the factory image. It is in that zip that you'll find the boot.img. And yes, you'll need to be in fastboot mode to install the boot.img :good:
Badger50 said:
There's another large zip that you'll find after you extract the factory image. It is in that zip that you'll find the boot.img. And yes, you'll need to be in fastboot mode to install the boot.img :good:
Click to expand...
Click to collapse
Ok so I extracted that 1.6gb December file. Inside the file I see the large 1.5GB file, I open that and see the boot.img, only like 40mb. or do I need to extract this 1.5GB file too ?
Zorachus said:
Ok so I extracted that 1.6gb December file. Inside the file I see the large 1.5GB file, I open that and see the boot.img, only like 40mb. or do I need to extract this 1.5GB file too ?
Click to expand...
Click to collapse
Yes, extract that file, then you can move the boot.img out of it :good:
Badger50 said:
Yes, extract that file, then you can move the boot.img out of it :good:
Click to expand...
Click to collapse
In Command Prompt I am typing " fastboot boot boot.img " and it says cannot load 'boot.img' : No such file or directory
Zorachus said:
In Command Prompt I am typing " fastboot boot boot.img " and it says cannot load 'boot.img' : No such file or directory
Click to expand...
Click to collapse
Ah crud, I messed up. How bout..fastboot flash boot boot.img
Does that work? And, is that boot.img in the platform-tools folder?
Badger50 said:
Ah crud, I messed up. How bout..fastboot flash boot boot.img
Does that work? And, is that boot.img in the platform-tools folder?
Click to expand...
Click to collapse
I moved that boot.img file into the Downloads section of my PC, and in Command Prompt typed cd Downloads, then once there the "fastboot boot boot.img" line, which that worked, and finished in 1.023s, and the phone rebooted, but now I'm back on that white G screen, and still just sitting there.
I have the "platform-tools" folder inside the Downloads folder, but now sure how to direct the Command Prompt to go there ?
EDIT: Silly me, easy to get Command Prompt to the platform-tools, just typed ' cd platform-tools ' and it's there. LOL. So I did that, and then 'fastboot boot boot.img' and the phone rebooted, but it's still hanging in that white G screen
Badger50 said:
Ah crud, I messed up. How bout..fastboot flash boot boot.img
Does that work? And, is that boot.img in the platform-tools folder?
Click to expand...
Click to collapse
Make sure your boot.img is in Android Tools folder along with fastboot.exe.
Then with phone in bootloader, type:
fastboot flash boot boot.img
---------- Post added at 07:31 PM ---------- Previous post was at 07:26 PM ----------
Zorachus said:
I moved that boot.img file into the Downloads section of my PC, and in Command Prompt typed cd Downloads, then once there the "fastboot boot boot.img" line, which that worked, and finished in 1.023s, and the phone rebooted, but now I'm back on that white G screen, and still just sitting there.
I have the "platform-tools" folder inside the Downloads folder, but now sure how to direct the Command Prompt to go there ?
EDIT: Silly me, easy to get Command Prompt to the platform-tools, just typed ' cd platform-tools ' and it's there. LOL. So I did that, and then 'fastboot boot boot.img' and the phone rebooted, but it's still hanging in that white G screen
Click to expand...
Click to collapse
This should cure your sticking at white screen: (wipes phone)
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Zorachus said:
I moved that boot.img file into the Downloads section of my PC, and in Command Prompt typed cd Downloads, then once there the "fastboot boot boot.img" line, which that worked, and finished in 1.023s, and the phone rebooted, but now I'm back on that white G screen, and still just sitting there.
I have the "platform-tools" folder inside the Downloads folder, but now sure how to direct the Command Prompt to go there ?
Click to expand...
Click to collapse
What happens if you do a hard restart using the power button?
Your platform-tools folder is where? I just leave mine in the SDK folder, then move my stuff from my files from the download folder. But hey, if it works, that's cool :good:
michaelbsheldon said:
Make sure your boot.img is in Android Tools folder along with fastboot.exe.
Then with phone in bootloader, type:
fastboot flash boot boot.img
Click to expand...
Click to collapse
Ok the boot.img is in there, in my CD:\Downloads section in the folder named "platform-tools" , in that folder is all the fastboot.exe, and boot.img, adb stuff, etc...
I go back to Command Prompt typed in 'fastboot flash boot boot.img; phone rebooted, and still hanging in the white G screen
Ran that [TOOL] Deuces thing, unlocked bootloader and erased data, and other stuff, it does all this in fastboot mode it seems.
So after it's done, I am in fastboot mode still, I press the power button on the Green Start arrow. It boots up, then a black screen and bright circle animation and underneath says erasing, it reboots and goes to the white G screen, then reboots again, and I am in some weird screen now ?
Android Recovery, but this sure the hell isn't TWRP Recovery. It's some strange super tiny lettering hard to barely read, gives me two options;
-Try again
-Factory data reset
Above that it says "Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory reset, and erase all your data stored on this device"
Zorachus said:
Ran that [TOOL] Deuces thing, unlocked bootloader and erased data, and other stuff, it does all this in fastboot mode it seems.
So after it's done, I am in fastboot mode still, I press the power button on the Green Start arrow. It boots up, then a black screen and bright circle animation and underneath says erasing, it reboots and goes to the white G screen, then reboots again, and I am in some weird screen now ?
Android Recovery, but this sure the hell isn't TWRP Recovery. It's some strange super tiny lettering hard to barely read, gives me two options;
-Try again
-Factory data reset
Above that it says "Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory reset, and erase all your data stored on this device"
Click to expand...
Click to collapse
I don't mess with tool kits, so may want to post it in that thread. That's the stock android recovery. Your best bet is to factory reset. Then hopefully it'll boot up.
Looks like I'm ****ed. I pressed Factory Data Reset, it rebooted, went to the white G screen, then rebooted back again to that stock Android recovery, with the same options.
Zorachus said:
Looks like I'm ****ed. I pressed Factory Data Reset, it rebooted, went to the white G screen, then rebooted back again to that stock Android recovery, with the same options.
Click to expand...
Click to collapse
That sounds like outdated Android Tools.
Have you tried to flash the March image from Google yet?
If not, download newest Tools, https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Then download March image and follow these instructions: https://developers.google.com/android/images#taimen.
I see a lot of people have this same problem for different reasons and the solutions are seemingly all over the place if any
My phone recently lagged out and i had to restart it, which is when my issue happened.
I know my space was running low so im assuming that may have something to do with why it happened.
my Pixel 2xl is stuck at the G loading screen and my goal is to recover the data over all else. I am new to this and have absolutely no idea what im doing. So ive googled as much as i could but some things arent making sense, id appreciate some help or a step by step
some info
my phone is 100% stock aside from my nova home launcher.
I dont not have custom bootloaders
my phone has a password, idk if that matters but just in case
my phone is not jailbroken (i think is the term?)
I did have USB debugging set already, and I BELIEVE i had developer mode enabled
thats about it for the phone info
In the bootloader main scree, it stats im in fastboot mode, secure boot yes, device state, locked
What ive tried
-I have tried the manual OTA install via the adb stuff
i got success 0 but upon restart, nothing changed and i was still stuck
-i tried the flash steps
but i get "flashing is not allowed in lock state pixel 2"
ive tried to use a pull command via adb, but it said some strings were incorrect? I just copy pasted a command from a similar post, it may not have been catered to my situation fully so i dont know about that
Is there any steps i can take to simply either recover my photos before i factory reset, or reset without wiping, or even maybe delete some files to make space via something somehow?? I just need my data, the phone itself i can replace
Most of your photos should be automatically backed up in Google photos already. I'd just factory reset and hope for the best.
Sometimes booting to bootloader then boot system does the trick, or long pressing the power button.
Download the full factory image
Unzip the image
Open the flash-all.bat in editor and delete "-w" and close the editor (save)
Add fastboot.exe (you have to download adb-files) to the image folder
Boot into bootloader
Run flash-all.bat
Edmontonchef said:
Most of your photos should be automatically backed up in Google photos already. I'd just factory reset and hope for the best.
Sometimes booting to bootloader then boot system does the trick, or long pressing the power button.
Click to expand...
Click to collapse
i turned that off initially but checked the site just in case, theyre not backed up ):
Sui77 said:
Download the full factory image
Unzip the image
Open the flash-all.bat in editor and delete "-w" and close the editor (save)
Add fastboot.exe (you have to download adb-files) to the image folder
Boot into bootloader
Run flash-all.bat
Click to expand...
Click to collapse
when following your directions exactly, i get an error for not having the rest of the adb files in the image folder.
I downloaded the full factory image, (NOT the Full OTA), extracted it, edited the .bat file so it wouldnt wipe, and placed the fastboot .exe (from the platform tools folder) inside of the folder, booted into bootloader and ran the file by double clicking on it.
I then tried putting the factory imagine files inside of the platform tools folder and running the flash that way just in case, and instead get "waiting for any device"
buninthesun said:
when following your directions exactly, i get an error for not having the rest of the adb files in the image folder.
I downloaded the full factory image, (NOT the Full OTA), extracted it, edited the .bat file so it wouldnt wipe, and placed the fastboot .exe (from the platform tools folder) inside of the folder, booted into bootloader and ran the file by double clicking on it.
I then tried putting the factory imagine files inside of the platform tools folder and running the flash that way just in case, and instead get "waiting for any device"
Click to expand...
Click to collapse
You can't flash factory images with fastboot unless your bootloader is unlocked and you establish an adb connection but you can sideload the ota without wiping userdata
Edmontonchef said:
You can't flash factory images with fastboot unless your bootloader is unlocked and you establish an adb connection but you can sideload the ota without wiping userdata
Click to expand...
Click to collapse
the OTA sideload has a success of 0 but nothing happens beyond that, the phone still gets stuck at loading
does 0 mean it should have worked? Any idea why nothing changed?
Sorry for the problems.
My bootloader is unlocked, so that might be the reason.
buninthesun said:
my Pixel 2xl is stuck at the G loading screen and my goal is to recover the data over all else.
Click to expand...
Click to collapse
Try the following.
1. Download the latest ADB and Fastboot binaries from the links at this page.
2. Extract the zip file you just downloaded to a directory on the root of a drive. For example, I have my copies of ADB and Fastboot stored at a directory I created, D:\ADB.
3. Open a command prompt, not a powershell window, and navigate to that directory using DOS commands.
4. Enter the bootloader on your device and connect your device to your PC.
5. Type "fastboot devices" to make sure the P2XL appears.
6. If it does, type the following commands:
fastboot getvar all
fastboot --set-active=a/b
fastboot reboot
The idea here is to get you into the device by using the second partition. To do this, you need to find out which slot you are currently using, A or B, and set the active slot to the OTHER partition. "fastboot getvar all" will tell you which slot is currently active. "fastboot --set-active=a/b" will change the active partition to the currently unused one. For example, if the active slot is currently a, you would issue the command "fastboot --set-active=b" to switch to the other partition, and then reboot.
Moral of the story here is unlock your bootloader and leave it that way.
So much easier getting out of trouble