Related
I'm having a problem with my nexus 5x. Yesterday, I decided I would factory restore my nexus from it being custom ROMd. I booted it into fastboot mode and relocked the bootloader, which wiped all the data. Then, when I went to flash the nought factory image, CMD and fastboot kept telling me my device is locked and I cannot flash to it. Because I locked the bootloader when the custom rom was still on it, it wont start up. I've downloaded older marshmallow builds from google too but they all give the same messages when flashing any of the files, including running the flash all command, saying that my device is locked and I cannot flash to it. Can anyone please help?
Jeez man! Locking the bootloader is the very last thing you do - if you do it at all because there's no good reason for it!
Cross my fingers: Do you have stock recovery installed?
If yes, you can adb sideload a OTA image.
If no, you're toast
https://developers.google.com/android/nexus/ota
berndblb said:
Jeez man! Locking the bootloader is the very last thing you do - if you do it at all because there's no good reason for it!
Cross my fingers: Do you have stock recovery installed?
If yes, you can adb sideload a OTA image.
If no, you're toast
https://developers.google.com/android/nexus/ota
Click to expand...
Click to collapse
Not toast. @arx160le would only have to flash the TOT to get it working again. He could do that regardless if he didn't feel like sideloading.
PiousInquisitor said:
Not toast. @arx160le would only have to flash the TOT to get it working again. He could do that regardless if he didn't feel like sideloading.
Click to expand...
Click to collapse
I cant seem to find a tot for 16 gb nexus 5x. Things arent look too good rn lmao.
arx160le said:
I cant seem to find a tot for 16 gb nexus 5x. Things arent look too good rn lmao.
Click to expand...
Click to collapse
Flash the 32. Boot to stock recovery and sideload the OTA. Problem solved.
Sent from my XT1650 using Tapatalk
PiousInquisitor said:
Flash the 32. Boot to stock recovery and sideload the OTA. Problem solved.
Sent from my XT1650 using Tapatalk
Click to expand...
Click to collapse
I just saw post 123 and thats what I did aha. It's working. Thank you so much.
Please help. I can not get to recovery. I can get to fastboot, but it is unrecognizable when i plug it in to a windows machine. It will recognize it when i plug it into MacOS. However the bootloader is locked, it will not allow me to unlock the bootloader from fastboot.
Caligula36 said:
Please help. I can not get to recovery. I can get to fastboot, but it is unrecognizable when i plug it in to a windows machine. It will recognize it when i plug it into MacOS. However the bootloader is locked, it will not allow me to unlock the bootloader from fastboot.
Click to expand...
Click to collapse
Follow the same guide that was just posted above. It's the only fix. Make sure you install all the drivers and boot the phone into download mode.
Windows tends to be a bugger sometimes when it comes to driver installs. My business laptop has 7 professional, my personal laptop has Windows 10. I never know which one will load the drivers I need.
You might just want to try a different computer if one is available. Or you could just delete any LG drivers you already have loaded and start fresh.
Sent from my Nexus 5X using Tapatalk
Has anyone who has unlocked their bootloader successfully flashed a different factory image other than the image on their phone. I've tried numerous ways and have had no success after unlocking my bootloader. Thanks to anyone who may chime in
Sent from my Pixel XL using XDA-Developers mobile app
treIII said:
Has anyone who has unlocked their bootloader successfully flashed a different factory image other than the image on their phone. I've tried numerous ways and have had no success after unlocking my bootloader. Thanks to anyone who may chime in
Sent from my Pixel XL using XDA-Developers mobile app
Click to expand...
Click to collapse
Could you be more specific about how you flashed (flash_all or each individual image file), and what happened? Error or what?
cam30era said:
Could you be more specific about how you flashed (flash_all or each individual image file), and what happened? Error or what?
Click to expand...
Click to collapse
I've tried flashing the entire P factory image and it fails. I've tried with adb and fast boot on my PC. I also tried with skipsoft toolkit to see if that would work. It also fails. I have posted screen shots in that thread if you'd like to see the error. Thanks
treIII said:
I've tried flashing the entire P factory image and it fails. I've tried with adb and fast boot on my PC. I also tried with skipsoft toolkit to see if that would work. It also fails. I have posted screen shots in that thread if you'd like to see the error. Thanks
Click to expand...
Click to collapse
I'd suggest fastboot flash each image file separately (boot, sys, etc)
cam30era said:
I'd suggest fastboot flash each image file separately (boot, sys, etc)
Click to expand...
Click to collapse
I tried that and it seems to work but nothing changes
treIII said:
I tried that and it seems to work but nothing changes
Click to expand...
Click to collapse
What is it that you are expecting to change?
cam30era said:
What is it that you are expecting to change?
Click to expand...
Click to collapse
The build number and for OEM unlocking to be pickable. My bootloader is already unlocked so I thought flashing a different factory image would make it possible in developer options
treIII said:
The build number and for OEM unlocking to be pickable. My bootloader is already unlocked so I thought flashing a different factory image would make it possible in developer options
Click to expand...
Click to collapse
I agree. That's very strange. Does fastboot indicate success after flashing each image?
cam30era said:
I agree. That's very strange. Does fastboot indicate success after flashing each image?
Click to expand...
Click to collapse
Yes for some but the system image fails. Look in skipsoft tool thread and you'll see it. There are pictures
treIII said:
Yes for some but the system image fails. Look in skipsoft tool thread and you'll see it. There are pictures
Click to expand...
Click to collapse
If you don't use skipsoft, and in fastboot do:
fastboot flash system system.img
You still get this partition error?
cam30era said:
If you don't use skipsoft, and in fastboot do:
fastboot flash system system.img
You still get this partition error?
Click to expand...
Click to collapse
Yes
treIII said:
Yes
Click to expand...
Click to collapse
Very strange. I'm at a loss.
cam30era said:
Very strange. I'm at a loss.
Click to expand...
Click to collapse
So u have Verizon version? I'd like to see someone else try to flash a factory image to know where this goes
treIII said:
So u have Verizon version? I'd like to see someone else try to flash a factory image to know where this goes
Click to expand...
Click to collapse
No. Considering buying one. That's why I'm interested in this.
cam30era said:
No. Considering buying one. That's why I'm interested in this.
Click to expand...
Click to collapse
Yeah I wish someone else would chime in and try. I can't figure it out after trying for 4 hours last night and about two today. So I gave up and posted
I flashed the google factory image. . oem unlock will stay greyed out but that is not a big deal. bunch of people did this and discussion in this other thread. http://forum.xda-developers.com/pixel-xl/how-to/verizon-pixel-xl-unlocking-discussions-t3484497
zanoli99 said:
I flashed the google factory image. . oem unlock will stay greyed out but that is not a big deal. bunch of people did this and discussion in this other thread. http://forum.xda-developers.com/pixel-xl/how-to/verizon-pixel-xl-unlocking-discussions-t3484497
Click to expand...
Click to collapse
Not until you want to update to newer firmwares and there is no unlock method on those bootloaders. Converting to a GPS Pixel would be ideal if it is even possible.
joderme said:
Not until you want to update to newer firmwares and there is no unlock method on those bootloaders. Converting to a GPS Pixel would be ideal if it is even possible.
Click to expand...
Click to collapse
If you unlock now and update later your bootloader will remained locked unless Google finds a way to push a bootloader update with the coming OTA's that locks your bootloader after unlocking but that's highly unlikely. Plus, if you jump the gun and install the OTA before knowing the results of the OTA, you're kind of asking for something like this to happen. Hopefully Google doesn't find a deceitful way of pushing bootloader updates to lock us back up as you know they have already learned that a backdoor was found to unlock the Verizon bootloaders. They're not stupid and Jcase already said the sunshine guys were sending the exploit to Google so they would patch it. Vulnerabilities are too common these days on Android and these exploit seekers are quick to submit patches for them.
OK. Finally was able to flash the latest pixel factory image on my PXL. Minimal and fastboot and latest drivers from Google.
i sorta need help in this department as well... do i unzip the zip inside the zip??
im getting missing recovery.img and missing boot.sig i would like to make this a non verizon device. the flash-all.bat didnt work and i tried modifying it by removing -w but still same errors. spoon feed me please or teamview? its been 2 days
Had a bit of a roller coaster ride over the past 12 hours trying to flash lineageos onto my phone. Let me try to give an idea of what has happened so you guys know what's up:
To start off:
I downloaded the unlock apk from the asus website and ran it last night
Afterwards, I loaded into fastboot and installed twrp
I made a backup using twrp and then I wiped the internal storage
Tried to flash the lineageos rom and got error 7
I thought I would restart the phone and try again. Not being able to get back into bootloader I thought I bricked my phone. It was late night so I decided to sleep and come back to it.
Woke up this morning and got into bootloader (I assume I was just pressing the buttons incorrectly)
Restored my backup and used my phone for a bit
After googling, found that I needed to modify some files in the lineageos zip to fix the errror 7. Proceeded to do so by wiping again and flashing the modified rom along with gapps.
Got into bootloop. So I turned the phone off and booted into boot loader hoping to get into twrp again, and try once more. Now, when I select recovery mode, it doesnt work and puts me back to bootloader.
So this is where I am now. And I've tried a couple of things, that may or may not have messed this phone up.
First off I've tried to, reinstall twrp.
https://www.youtube.com/watch?v=vM0ODzSb1y4 ( wrong link )
https://youtu.be/BJPEc1NG_k8
Using this link I ran the file that he has given while in bootloader. Nothing changed. So I also tried to just download the latest twrp and flash that. Resulting with the same situation as before.
With a little more google I figured I would flash some stock images.
http://www.android.gs/how-to-unbrick-asus-zenfone-2-and-go-back-to-stock-android-os/
With this website. I went and downloaded firmware from asus website. Extracted it and went about flashing each item. That is when I realized that the file doesnt contain a system.img. ****.
At this point I also had a system.img from:
https://forum.xda-developers.com/zenfone2/help/enter-recovery-551ml-z00a-t3345633/page2
And I just proceeded to try and flash that in replacement for what I did not have. But I got an error:
http://imgur.com/a/TldyG
Now from what I see here. It wiped it without adding anything. So now I'm a little scared.
I found this video:
https://www.youtube.com/watch?v=q5BNfaU_O9o
With links to various files. Now I'm not sure if I can just download one and flash each file like before.
TL;DR: I've tried to flash lineageos. It put me into bootloop. I can't get back into recovery. I tried to flash some img files I found and I messed up (check imgur link above). Not sure where to go from here.
Thanks for any help guys.
noobsauce47 said:
Had a bit of a roller coaster ride over the past 12 hours trying to flash lineageos onto my phone. Let me try to give an idea of what has happened so you guys know what's up:
To start off:
I downloaded the unlock apk from the asus website and ran it last night
Afterwards, I loaded into fastboot and installed twrp
I made a backup using twrp and then I wiped the internal storage
Tried to flash the lineageos rom and got error 7
I thought I would restart the phone and try again. Not being able to get back into bootloader I thought I bricked my phone. It was late night so I decided to sleep and come back to it.
Woke up this morning and got into bootloader (I assume I was just pressing the buttons incorrectly)
Restored my backup and used my phone for a bit
After googling, found that I needed to modify some files in the lineageos zip to fix the errror 7. Proceeded to do so by wiping again and flashing the modified rom along with gapps.
Got into bootloop. So I turned the phone off and booted into boot loader hoping to get into twrp again, and try once more. Now, when I select recovery mode, it doesnt work and puts me back to bootloader.
So this is where I am now. And I've tried a couple of things, that may or may not have messed this phone up.
First off I've tried to, reinstall twrp.
https://www.youtube.com/watch?v=vM0ODzSb1y4
Using this link I ran the file that he has given while in bootloader. Nothing changed. So I also tried to just download the latest twrp and flash that. Resulting with the same situation as before.
With a little more google I figured I would flash some stock images.
http://www.android.gs/how-to-unbrick-asus-zenfone-2-and-go-back-to-stock-android-os/
With this website. I went and downloaded firmware from asus website. Extracted it and went about flashing each item. That is when I realized that the file doesnt contain a system.img. ****.
At this point I also had a system.img from:
https://forum.xda-developers.com/zenfone2/help/enter-recovery-551ml-z00a-t3345633/page2
And I just proceeded to try and flash that in replacement for what I did not have. But I got an error:
http://imgur.com/a/TldyG
Now from what I see here. It wiped it without adding anything. So now I'm a little scared.
I found this video:
https://www.youtube.com/watch?v=q5BNfaU_O9o
With links to various files. Now I'm not sure if I can just download one and flash each file like before.
TL;DR: I've tried to flash lineageos. It put me into bootloop. I can't get back into recovery. I tried to flash some img files I found and I messed up (check imgur link above). Not sure where to go from here.
Thanks for any help guys.
Click to expand...
Click to collapse
What were you on before you started? Usually the error 7 is because you weren't on the right bootloader. In this case you need the MM bootloader. If you were coming from Lollipop that would explain it.
Sent from my ASUS_Z00A using Tapatalk
---------- Post added at 05:46 PM ---------- Previous post was at 05:44 PM ----------
Oh and what model zf2 do you have
Sent from my ASUS_Z00A using Tapatalk
kenbo111 said:
What were you on before you started? Usually the error 7 is because you weren't on the right bootloader. In this case you need the MM bootloader. If you were coming from Lollipop that would explain it.
Sent from my ASUS_Z00A using Tapatalk
---------- Post added at 05:46 PM ---------- Previous post was at 05:44 PM ----------
Oh and what model zf2 do you have
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
My bad I should have also included the model number in the post, I'm using the ZE551ML. Yeah, I believe I was on 5.0 when I started. If I hadn't all of this would have been solved? I'm so sad.
MM bootloader? (Sorry, I'm a newbie at this) So where would I go from here? Finding the MM bootloader and installing it with fastboot as well as trying to get twrp working again?
Thanks for the quick reply.
edit: realized i also linked the wrong youtube video in the first post, if you want to check it out again
noobsauce47 said:
My bad I should have also included the model number in the post, I'm using the ZE551ML. Yeah, I believe I was on 5.0 when I started. If I hadn't all of this would have been solved? I'm so sad.
MM bootloader? (Sorry, I'm a newbie at this) So where would I go from here? Finding the MM bootloader and installing it with fastboot as well as trying to get twrp working again?
Thanks for the quick reply.
edit: realized i also linked the wrong youtube video in the first post, if you want to check it out again
Click to expand...
Click to collapse
I would go to this thread
https://forum.xda-developers.com/showthread.php?t=3448966
And download the 4.21.40.184 raw image and the asus flash tool. (Google how to use it) use the tool to flash the raw image. That will give you stock marshmallow. Then go get the modder tool from
https://forum.xda-developers.com/showthread.php?t=3458145
Use that to unlock and install TWRP.
Then you should be good to go to flash LinOS
Sent from my ASUS_Z00A using Tapatalk
kenbo111 said:
I would go to this thread
https://forum.xda-developers.com/showthread.php?t=3448966
And download the 4.21.40.184 raw image and the asus flash tool. (Google how to use it) use the tool to flash the raw image. That will give you stock marshmallow. Then go get the modder tool from
https://forum.xda-developers.com/showthread.php?t=3458145
Use that to unlock and install TWRP.
Then you should be good to go to flash LinOS
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
When trying to install the asus flash tool, it tells me that it failed to install drivers and that I should do them manually. Is that necessary?
I really do appreciate the help. Thanks so much.
noobsauce47 said:
When trying to install the asus flash tool, it tells me that it failed to install drivers and that I should do them manually. Is that necessary?
I really do appreciate the help. Thanks so much.
Click to expand...
Click to collapse
It sounds from your first post that the drivers should already be installed. Fastboot commands worked for you before right?
Sent from my ASUS_Z00A using Tapatalk
kenbo111 said:
It sounds from your first post that the drivers should already be installed. Fastboot commands worked for you before right?
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Yes, they were working. So it's talking about asus usb drivers?
Yes
Sent from my ASUS_Z00A using Tapatalk
Thanks
Thank you. Thank you. I am downloading the raw right now. Will update when I use the flash tool and try the modder.
For the modder it looks like I will:
-unlock bootloader
-install twrp
-root
and there is an option of installing xposed. Seems like it gives you more versatility when flashing roms. Do you think it is stable and has enough support to be used with the zenfone? Are updates done automatically and does the framework stay when updating/flashing roms?
kenbo111 said:
I would go to this thread
https://forum.xda-developers.com/showthread.php?t=3448966
And download the 4.21.40.184 raw image and the asus flash tool. (Google how to use it) use the tool to flash the raw image. That will give you stock marshmallow. Then go get the modder tool from
https://forum.xda-developers.com/showthread.php?t=3458145
Use that to unlock and install TWRP.
Then you should be good to go to flash LinOS
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Getting an error now running the asus flash tool. Any idea? http://imgur.com/a/gOqf2
Also, is it safe to turn the device off? After flashing the imgs I'm scared to turn it off. If I accidentally boot into os will the phone break?
If you plan on installing LinOS. You don't need to root first. (you can if you want, but it would be a waste of time). Xposed is great but I don't think it works with LinOS yet. (at least that was the case when I was on that rom) LinOS does have weekly Ota updates. Just need to have twrp 3.0.3 or higher for the update process to work
Sent from my ASUS_Z00A using Tapatalk
---------- Post added at 08:06 PM ---------- Previous post was at 07:32 PM ----------
noobsauce47 said:
Getting an error now running the asus flash tool. Any idea? http://imgur.com/a/gOqf2
Also, is it safe to turn the device off? After flashing the imgs I'm scared to turn it off. If I accidentally boot into os will the phone break?
Click to expand...
Click to collapse
Do you have the phone in bootloader (fastboot mode)?
Sent from my ASUS_Z00A using Tapatalk
kenbo111 said:
---------- Post added at 08:06 PM ---------- Previous post was at 07:32 PM ----------
[/COLOR]
Do you have the phone in bootloader (fastboot mode)?
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Yea it's in fastboot mode with the android figure and his stomach open.
edit: i restarted bootloader and now its in the usb icon mode
noobsauce47 said:
Yea it's in fastboot mode with the android figure and his stomach open.
edit: i restarted bootloader and now its in the usb icon mode
Click to expand...
Click to collapse
I haven't personally seen that error before. But they discussed it in this thread. https://forum.xda-developers.com/showthread.php?t=3418046
Sent from my ASUS_Z00A using Tapatalk
alright thanks for all the help ive seen this around the internet as well so i will have to go figure it out.
noobsauce47 said:
alright thanks for all the help ive seen this around the internet as well so i will have to go figure it out.
Click to expand...
Click to collapse
The guy, timbernot, that's helping them in that last thread is really good with this. If you can get ahold of him.
Sent from my ASUS_Z00A using Tapatalk
I read a comment in one of the 2 XL thread where someone always flashed the Google factory image on their device, but fastbooted the Verizon radio and modem images from the VZE factory image.
So I pulled the VZW radio.img and modem.img and when I flashed the radio I got an error saying something like -maximum space req not specified/given-
here are the steps I followed:
d/l Nov VZW factory image
copied the radio.img and modem.img to my fastboot folder
connected device to PC and verified fastboot devices (my device serial number came up)
ran fastboot flash radio radio-vzw radio file name.img
fastboot found the right file, then error stated maximum space required not specified
failed.
attempted again, ensuring proper filename, spacing, all were correct.. same error...
Any ideas what would cause a simple radio.img flash to fail?
Once I get home, I'll try again, and I'll have be sure to capture the exact error message this time
My current device environment:
Google unlocked 2XL
Nov Google factory image
Magisk patched_boot.img flashed via fastboot
Flash Taimen kernel 1.01 flashed via fastboot
busybox installed 1.27.2 installed (latest Stericson via Play)
Adaway installed
TWRP never installed
TIA
Az Biker said:
I read a comment in one of the 2 XL thread where someone always flashed the Google factory image on their device, but fastbooted the Verizon radio and modem images from the VZE factory image.
So I pulled the VZW radio.img and modem.img and when I flashed the radio I got an error saying something like -maximum space req not specified/given-
here are the steps I followed:
d/l Nov VZW factory image
copied the radio.img and modem.img to my fastboot folder
connected device to PC and verified fastboot devices (my device serial number came up)
ran fastboot flash radio radio-vzw radio file name.img
fastboot found the right file, then error stated maximum space required not specified
failed.
attempted again, ensuring proper filename, spacing, all were correct.. same error...
Any ideas what would cause a simple radio.img flash to fail?
Once I get home, I'll try again, and I'll have be sure to capture the exact error message this time
My current device environment:
Google unlocked 2XL
Nov Google factory image
Magisk patched_boot.img flashed via fastboot
Flash Taimen kernel 1.01 flashed via fastboot
busybox installed 1.27.2 installed (latest Stericson via Play)
Adaway installed
TWRP never installed
TIA
Click to expand...
Click to collapse
So you did fastboot flash modem modem.img?
And fastboot flash radio radio.img?
Both gave the same error?
Sent from my Pixel 2 XL using Tapatalk
bryantjopplin said:
So you did fastboot flash modem modem.img?
And fastboot flash radio radio.img?
Both gave the same error?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
I did fastboot flash radio radio-filename.img ... two times and received the same error
I did not try the modem.img as I wasn;'t sure if flashing only the VZW modem, and not the VZW radio would cause any issues.
Thanks for the quick reply!
Az Biker said:
I did fastboot flash radio radio-filename.img ... two times and received the same error
I did not try the modem.img as I wasn;'t sure if flashing only the VZW modem, and not the VZW radio would cause any issues.
Thanks for the quick reply!
Click to expand...
Click to collapse
It should not. The modem is most likely the same.
Sent from my Pixel 2 XL using Tapatalk
bryantjopplin said:
It should not. The modem is most likely the same.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
I kinda thought that as the radio file had a recent date, and the modem a 2009 date.
I'll try again this afternoon and get the exact error message if it comes up.
Any idea, regardless of the error message, why a simply radio flash wouldn't take?
Patched_boot.img from Magisk?
I've been fastbooting radios, bootloaders regularly on my 6P for nearly 2 years, so I'm not new to fastboot.
Az Biker said:
I kinda thought that as the radio file had a recent date, and the modem a 2009 date.
I'll try again this afternoon and get the exact error message if it comes up.
Any idea, regardless of the error message, why a simply radio flash wouldn't take?
Patched_boot.img from Magisk?
I've been fastbooting radios, bootloaders regularly on my 6P for nearly 2 years, so I'm not new to fastboot.
Click to expand...
Click to collapse
Assuming you have the newest fastboot and drivers correct? Maybe check and see in device manager
Sent from my Pixel 2 XL using Tapatalk
Do you have current fastboot/adb files?
Did you unlock critical when you unlocked?
bryantjopplin said:
Assuming you have the newest fastboot and drivers correct? Maybe check and see in device manager
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
arcanexvi said:
Do you have current fastboot/adb files?
Did you unlock critical when you unlocked?
Click to expand...
Click to collapse
I uninstalled all my old SDK tools from my pc first,then rebooted the pc
Downloaded/installed latest from SDK tools last week when I updated to Nov factory image and flash kernel.
Originally only ran unlock, then prior to flashing Nov update I did critical_unlock
Az Biker said:
I uninstalled all my old SDK tools from my pc first,then rebooted the pc
Downloaded/installed latest from SDK tools last week when I updated to Nov factory image and flash kernel.
Originally only ran unlock, then prior to flashing Nov update I did critical_unlock
Click to expand...
Click to collapse
Maybe flash a smaller partition and see if it works.
Sent from my Pixel 2 XL using Tapatalk
bryantjopplin said:
Maybe flash a smaller partition and see if it works.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Haven't flashed 'partitions' before other than in TWRP on the 6P selecting boot, vendor, etc...
I know there is a 1 and 2 partition with the 2 XL, but haven't mess with them at all.
Is there a 'how to' or instructions on choosing partitions for this device?
Az Biker said:
Haven't flashed 'partitions' before other than in TWRP on the 6P selecting boot, vendor, etc...
I know there is a 1 and 2 partition with the 2 XL, but haven't mess with them at all.
Is there a 'how to' or instructions on choosing partitions for this device?
Click to expand...
Click to collapse
Not slot. I meant img. Which is basically different partitions. Try flashing dtbo or another smaller one.
Sent from my Pixel 2 XL using Tapatalk
bryantjopplin said:
Not slot. I meant img. Which is basically different partitions. Try flashing dtbo or another smaller one.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Oh okay, got it. I'll try that too tonight.
try a usb 2.0 port and perhaps a different cable, or even plug the usb-c portion of the cable in the "other way" (rotate)
you may also want to try a full flash, i made a tool: https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
So I tried a different cable, not sure if it's USB 2 or 3, but radio flashed first try!
I'd totally get it, if "fastboot devices" turned up nothing, yeah, try a new cable. But when fastboot devices sees your device, how can it not flash a file?
Looks like I'll be using this cable from here on out
Thanks for the input and help everyone!
Az Biker said:
So I tried a different cable, not sure if it's USB 2 or 3, but radio flashed first try!
I'd totally get it, if "fastboot devices" turned up nothing, yeah, try a new cable. But when fastboot devices sees your device, how can it not flash a file?
Looks like I'll be using this cable from here on out [emoji14]
Thanks for the input and help everyone!
Click to expand...
Click to collapse
Imo the aylee cables on Amazon are top quality and with great.
Sent from my Pixel 2 XL using Tapatalk
Is there a list if radios for pixel 2xl that can be fast boot flashed? TIA
wooddale said:
Is there a list if radios for pixel 2xl that can be fast boot flashed? TIA
Click to expand...
Click to collapse
Not that I've seen. You'll likely have to extract them from the factory images.
Coming from Havoc Is, and wanted to try beta 5 so I used fastboot method to flash latest stock image so I would receive beta 5 OTA. In fastboot I did flash-all and it started to do its thing but after a while fastboot said no boot and no recovery image in the file. After a minute or two, it continued to flash the rest. After everything was done, my phone was in bootloop so I formated data with twrp and the phone booted up but it was still on Havoc Os. Can anyone help me with this problem please
Try using this tool.
https://forum.xda-developers.com/pixel-2-xl/development/tool-deuces-bootloop-recovery-flashing-t3704761
Make sure you put the files on your primary hard-drive to avoid errors.
MaleSamus said:
Try using this tool.
https://forum.xda-developers.com/pixel-2-xl/development/tool-deuces-bootloop-recovery-flashing-t3704761
Make sure you put the files on your primary hard-drive to avoid errors.
Click to expand...
Click to collapse
Thanks will give it a try
MaleSamus said:
Try using this tool.
https://forum.xda-developers.com/pixel-2-xl/development/tool-deuces-bootloop-recovery-flashing-t3704761
Make sure you put the files on your primary hard-drive to avoid errors.
Click to expand...
Click to collapse
Works great except that I've relock the bootloader and when the phone starts it says that the phone is not running the stock image andwhen I try to install beta 5, it's giving me an error when installing.
Just to confirm, you are using image from here to go back to stock and not the OTA image?
https://developers.google.com/android/images
Once you've flashed with this image, you should then be able to sideload the beta using the beta OTA image from here:
https://developer.android.com/preview/download-ota.html
coco1476 said:
Works great except that I've relock the bootloader and when the phone starts it says that the phone is not running the stock image andwhen I try to install beta 5, it's giving me an error when installing.
Click to expand...
Click to collapse
I'm not picking on you, but this needs to be said again and again. Everyone Stop Locking Your BootLoaders!! NOW!!
People are destroying their phones at record pace lately and it's all completely unnecessary. There are literally a dozen thread recently that all end the same way. A bricked phone and another warning about the danger of relocking the bootloader.
Sent from my Pixel 2 XL using XDA Labs
CyberpodS2 said:
I'm not picking on you, but this needs to be said again and again. Everyone Stop Locking Your BootLoaders!! NOW!!
People are destroying their phones at record pace lately and it's all completely unnecessary. There are literally a dozen thread recently that all end the same way. A bricked phone and another warning about the danger of relocking the bootloader.
Sent from my Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
Thanks for the info, I just thought it was best to lock the bootloader to get OTA betas instead of sideloading. I'm up and running beta 5 now
MaleSamus said:
Just to confirm, you are using image from here to go back to stock and not the OTA image?
https://developers.google.com/android/images
Once you've flashed with this image, you should then be able to sideload the beta using the beta OTA image from here:
https://developer.android.com/preview/download-ota.html
Click to expand...
Click to collapse
Thanks it's all running good now with your help