I'm trying to install Lineage OS on my phone and I have followed all the steps (plus many more they just assume you'll know) from this site, up to configuration because adb no longer discovers my phone.
.\adb devices
.\adb fastboot bootload
literally anything to do with adb doesn't work but it did an hour ago. Now I'm worse off because my phone will only upload to bootload and not to the actual homescreen so there's no going in and double checking if my USB debugging is on (it was before the reset) and I can't access my phone at all, nor can I get things configured. I've updated the drivers via web, deleted and retried the drivers, and restarted the computer. I don't know what I'm supposed to have on my computer that would better upload the drivers. I don't have a clue what any of this is supposed to mean, I was forced to do all of this **** because of the recent Adroid 12 update that I couldn't get rid of without just getting a different OS. Please please please make it dumb for me and tell me how I can get my phone back and download this OS.
Try fastboot commands in bootloader
yesca213 said:
Try fastboot commands in bootloader
Click to expand...
Click to collapse
Yes fastboot commands work but I need to copy this in the command prompt
.\adb sideload copy-partitions-20210323_1922.zip
The tutorial says it isn't an optional step. When I try doing this with fastboot, it tells me:
fastboot: usage: unknown command sideload
Try "fastboot reboot" or "fastboot reboot bootloader"
yesca213 said:
Try "fastboot reboot" or "fastboot reboot bootloader"
Click to expand...
Click to collapse
Thanks! I tried it with no change. adb can still not discover my phone and it doesn't start back up, only brings me to FastBoot mode screen.
If it's Windows your using it may be a driver issue.
yesca213 said:
If it's Windows your using it may be a driver issue.
Click to expand...
Click to collapse
Yes I'm on Windows 10. I have uninstalled and reinstalled the Android and Portable devices drivers with no luck. Do you know what I might be able to do to fix it from that end?
johnmtrowbridge said:
Yes I'm on Windows 10. I have uninstalled and reinstalled the Android and Portable devices drivers with no luck. Do you know what I might be able to do to fix it from that end?
Click to expand...
Click to collapse
hi, bro.
once you connected phone on fastboot mode, check device manager if any device is not recognized - try to manually install it from HERE.
if you still have any problems - contact me on telegram terry_222
heyhowyoudoin said:
hi, bro.
once you connected phone on fastboot mode, check device manager if any device is not recognized - try to manually install it from HERE.
if you still have any problems - contact me on telegram terry_222
Click to expand...
Click to collapse
So I checked in device manager and didn't see any exclaimation points anywhere which is what I assume you meant. Nothing out of the ordinary and Android looks fine. I'd like to message you on telegram and I guess I will in a few hours but it's blocked on my work wifi and I don't have a VPN and my hotspot it obviously bricked at the moment
johnmtrowbridge said:
So I checked in device manager and didn't see any exclaimation points anywhere which is what I assume you meant. Nothing out of the ordinary and Android looks fine. I'd like to message you on telegram and I guess I will in a few hours but it's blocked on my work wifi and I don't have a VPN and my hotspot it obviously bricked at the moment
Click to expand...
Click to collapse
just i'm sure what i can fix all that thing fast and want to help you
i have signal too
heyhowyoudoin said:
just i'm sure what i can fix all that thing fast and want to help you
i have signal too
Click to expand...
Click to collapse
Yeah I'm gonna just have to try in a few hours because the only way Signal works on my desktop is if I verify it on my phone lol. Again, the phone is completely stuck on FastBoot mode and anytime I restart it it takes me right back, which I think is probably because of the recovery mode I just installed.
bro, I just read what you wrote, if you had version 12 of android, then you already ruined everything and there is nothing left but to reinstall the firmware using MSM tool
heyhowyoudoin said:
bro, I just read what you wrote, if you had version 12 of android, then you already ruined everything and there is nothing left but to reinstall the firmware using MSM tool
Click to expand...
Click to collapse
I had the most recent update from last week. I didn't catch the name specifically, I assumed it was Android 12. I already did a factory reset on my phone last week trying to get rid of the update or at least revert back to the previous one but that didn't help and it was because my phone version is the wrong one for the revert package they had or something like that. So with that info, you're saying I have to reinstall everything all over again and try again? There's no way to get Lineage on this phone at all?
i
if you were on version 12, then you need to flash to version 11 using the MSM TOOL program, then upgrade to the latest 11.2.10.10, and only then open the bootloader, flash the recovery and then flash the firmware
heyhowyoudoin said:
i
if you were on version 12, then you need to flash to version 11 using the MSM TOOL program, then upgrade to the latest 11.2.10.10, and only then open the bootloader, flash the recovery and then flash the firmware
Click to expand...
Click to collapse
There wasn't a recovery version of 11 at the time that I could find, not for the 9 Pro. So what do I do now, do you know how I at least get my phone off of FastBoot mode to try this **** all over again?
johnmtrowbridge said:
I had the most recent update from last week. I didn't catch the name specifically, I assumed it was Android 12. I already did a factory reset on my phone last week trying to get rid of the update or at least revert back to the previous one but that didn't help and it was because my phone version is the wrong one for the revert package they had or something like that. So with that info, you're saying I have to reinstall everything all over again and try again? There's no way to get Lineage on this phone at all?
Click to expand...
Click to collapse
if you flashed the boot file through a fastboot being on the 12th version of android, you will never be able to do anything but very tricky manipulations that a small number of people own, so you have one path that I indicated above. and by the way, I do not advise you lineageos 11 version, better derpfest 12 version, 11 version is obsolete and you will understand it yourself
can you tell me which version your phone have? IN/CN/GLOBAL/INDIA
Index of /list/Unbrick_Tools/OnePlus_9_Pro
or download version for your phone from link above
heyhowyoudoin said:
if you flashed the boot file through a fastboot being on the 12th version of android, you will never be able to do anything but very tricky manipulations that a small number of people own, so you have one path that I indicated above. and by the way, I do not advise you lineageos 11 version, better derpfest 12 version, 11 version is obsolete and you will understand it yourself
Click to expand...
Click to collapse
Ok dude what I hear you saying is that 1.) Android 12 can't have Lineage OS installed because the version doesn't jive well with the OS, 2.) the instructions will only help on version 11 that I have to get first and 3.) I don't want Lineage anyways because derpfest 12 is better. Is that what you're saying?
heyhowyoudoin said:
can you tell me which version your phone have? IN/CN/GLOBAL/INDIA
Click to expand...
Click to collapse
NA I'm in America
johnmtrowbridge said:
Ok dude what I hear you saying is that 1.) Android 12 can't have Lineage OS installed because the version doesn't jive well with the OS, 2.) the instructions will only help on version 11 that I have to get first and 3.) I don't want Lineage anyways because derpfest 12 is better. Is that what you're saying?
NA I'm in America
Click to expand...
Click to collapse
yes, that's what I mean. is your phone linked to t mobile?
at the moment it is not possible to install any custom OS from version 12 of android, not only lineageos
Related
Hi,
When I connect my ZF2 to the PC, I get an error saying USB device not recognized.
Here are some of the troubleshooting steps I've done:
Tried another cable
Tried another pc
Made sure USB debugging is enabled
Select USB configuration is set to MTP
Made sure ASUS drivers are installed an up to date
Uninstalled drivers from device manager
Updated drivers from device manager
Charging port works (even fast charges when I use the right cable)
SD card slot works
Had a technician replace the entire charging board (pcb board)
Specs:
ZOOA 2gb/16gb
Running 6.0.1
CM13 20161219 Nightly
Also, i'm thinking of restoring my phone back to original stock (that's why I would like to be able to connect it to pc) but if there is a way to put it back to stock without the need of a pc, i'm all ears for it. I'd like to give the stock ASUS updates and software a chance now cause ever since I got the phone, I have been on custom ROMs.
I'm running out of ideas.
Message me here or on facebook or maybe even on battlenet. Just please help me.
KyleGerard said:
Hi,
When I connect my ZF2 to the PC, I get an error saying USB device not recognized.
Here are some of the troubleshooting steps I've done:
Tried another cable
Tried another pc
Made sure USB debugging is enabled
Select USB configuration is set to MTP
Made sure ASUS drivers are installed an up to date
Uninstalled drivers from device manager
Updated drivers from device manager
Charging port works (even fast charges when I use the right cable)
SD card slot works
Had a technician replace the entire charging board (pcb board)
Specs:
ZOOA 2gb/16gb
Running 6.0.1
CM13 20161219 Nightly
Also, i'm thinking of restoring my phone back to original stock (that's why I would like to be able to connect it to pc) but if there is a way to put it back to stock without the need of a pc, i'm all ears for it. I'd like to give the stock ASUS updates and software a chance now cause ever since I got the phone, I have been on custom ROMs.
I'm running out of ideas.
Message me here or on facebook or maybe even on battlenet. Just please help me.
Click to expand...
Click to collapse
hello , can you install a fresh copy of cm13 from around October ?
Obviously do a back up of your current set up first , then test.
Adb , USB enabled etc ?
Nothing in fastboot showing either ?
******WARNING !!! Only flash this below if you have 0094.0183 ifwi version in boot loader. !!!!*******
http://theflamingskull.com/downloads/z00a/MM_BL_STUFF/
also , just to test this , even though developer options is showing ... do the tap on build number numerous times again
I had that bug a few times after a restart let me know
KyleGerard said:
Hi,
When I connect my ZF2 to the PC, I get an error saying USB device not recognized.
Here are some of the troubleshooting steps I've done:
Tried another cable
Tried another pc
Made sure USB debugging is enabled
Select USB configuration is set to MTP
Made sure ASUS drivers are installed an up to date
Uninstalled drivers from device manager
Updated drivers from device manager
Charging port works (even fast charges when I use the right cable)
SD card slot works
Had a technician replace the entire charging board (pcb board)
Specs:
ZOOA 2gb/16gb
Running 6.0.1
CM13 20161219 Nightly
Also, i'm thinking of restoring my phone back to original stock (that's why I would like to be able to connect it to pc) but if there is a way to put it back to stock without the need of a pc, i'm all ears for it. I'd like to give the stock ASUS updates and software a chance now cause ever since I got the phone, I have been on custom ROMs.
I'm running out of ideas.
Message me here or on facebook or maybe even on battlenet. Just please help me.
Click to expand...
Click to collapse
You may have to update the driver from device manager. I was alsofacing the same issue..
1. Go to device manager.
2.Right click on MTP DEVICE and Select UPDATE DRIVER SOFTWARE
3.Then select BROWSE MY COMPUTER FOR DRIVER SOFTWARE
4.Then select LET ME PICK FROM A LIST..................
5.Uncheck SHOW COMPATIBLE HARDWARE
6.SELECT (STANDARD MTP DEVICE)
7. In the 2nd panel Select MTP DEVICEAND THEN CLICK NEXT.
hope this will solve the problem.
If not send me a screenshot at this email id: [email protected]
Devc100 said:
You may have to update the driver from device manager. I was alsofacing the same issue..
1. Go to device manager.
2.Right click on MTP DEVICE and Select UPDATE DRIVER SOFTWARE
3.Then select BROWSE MY COMPUTER FOR DRIVER SOFTWARE
4.Then select LET ME PICK FROM A LIST..................
5.Uncheck SHOW COMPATIBLE HARDWARE
6.SELECT (STANDARD MTP DEVICE)
7. In the 2nd panel Select MTP DEVICEAND THEN CLICK NEXT.
hope this will solve the problem.
If not send me a screenshot at this email id: [email protected]
Click to expand...
Click to collapse
I'll do this when i get home later.. I'll keep you posted bro.
timbernot said:
hello , can you install a fresh copy of cm13 from around October ?
Obviously do a back up of your current set up first , then test.
Adb , USB enabled etc ?
Nothing in fastboot showing either ?
---------- Post added at 01:12 AM ---------- Previous post was at 01:06 AM ----------
http://theflamingskull.com/downloads/z00a/MM_BL_STUFF/
also , just to test this , even though developer options is showing ... do the tap on build number numerous times again
I had that bug a few times after a restart let me know
Click to expand...
Click to collapse
Hi, Yes.. adb and usb enabled.. I did the tap on build number thing and it just said developer options already enabled.. Will try the cm13 install later andI'll also check if fastboot detects it. keep you posted bro.
timbernot said:
hello , can you install a fresh copy of cm13 from around October ?
Obviously do a back up of your current set up first , then test.
Adb , USB enabled etc ?
Nothing in fastboot showing either ?
---------- Post added at 01:12 AM ---------- Previous post was at 01:06 AM ----------
http://theflamingskull.com/downloads/z00a/MM_BL_STUFF/
also , just to test this , even though developer options is showing ... do the tap on build number numerous times again
I had that bug a few times after a restart let me know
Click to expand...
Click to collapse
Hi,
Can you point me to an instructional video on how to install a fresh copy of cm13? I just wanna make sure that I do the right steps.
Also, am just curious. Are you also using a zf2 right now? Are you on stock or custom ROM? Since CM13 has been discontinued, i was thinking of switching ROMs. Any particular ROM that you would recommend?
Devc100 said:
You may have to update the driver from device manager. I was alsofacing the same issue..
1. Go to device manager.
2.Right click on MTP DEVICE and Select UPDATE DRIVER SOFTWARE
3.Then select BROWSE MY COMPUTER FOR DRIVER SOFTWARE
4.Then select LET ME PICK FROM A LIST..................
5.Uncheck SHOW COMPATIBLE HARDWARE
6.SELECT (STANDARD MTP DEVICE)
7. In the 2nd panel Select MTP DEVICEAND THEN CLICK NEXT.
hope this will solve the problem.
If not send me a screenshot at this email id: [email protected]
Click to expand...
Click to collapse
Hi,
I tried the instructions but when I get to step # 6, i do not have standard MTP device on the choices.
KyleGerard said:
Hi,
Can you point me to an instructional video on how to install a fresh copy of cm13? I just wanna make sure that I do the right steps.
Also, am just curious. Are you also using a zf2 right now? Are you on stock or custom ROM? Since CM13 has been discontinued, i was thinking of switching ROMs. Any particular ROM that you would recommend?
Click to expand...
Click to collapse
You install like normal , like you did with your current cm13.
What is your ifwi version in Boot loader ?
KyleGerard said:
Hi,
I tried the instructions but when I get to step # 6, i do not have standard MTP device on the choices.
Click to expand...
Click to collapse
what choices do you have?
send me a screenshot.
timbernot said:
You install like normal , like you did with your current cm13.
What is your ifwi version in Boot loader ?
Click to expand...
Click to collapse
How do I check what IFWI version I have?
Its been a year since i unlocked bootloader and switched to CM13, i just do the OTA updates so i forgot how to flash.
Apologies.
Devc100 said:
what choices do you have?
send me a screenshot.
Click to expand...
Click to collapse
Attached the screenshot.
Interesting thing here is under developer options, when i try to change the select usb configuration, it does not let me choose anything aside from charging.
KyleGerard said:
How do I check what IFWI version I have?
Its been a year since i unlocked bootloader and switched to CM13, i just do the OTA updates so i forgot how to flash.
Apologies.
Click to expand...
Click to collapse
reboot to bootloader and what ifwi version is it ?
If over a year ago you will have LP version .
I will link you to the appropriate thread soon as we determine the correct ifwi.
Just as a side not , lots of people have had the same bug
I think its a driver issue that windows update have blocked
..
timbernot said:
reboot to bootloader and what ifwi version is it ?
If over a year ago you will have LP version .
I will link you to the appropriate thread soon as we determine the correct ifwi.
Just as a side not , lots of people have had the same bug
I think its a driver issue that windows update have blocked
..
Click to expand...
Click to collapse
LP? Lollipop? I'm at Marsh 6.0.1
KyleGerard said:
Attached the screenshot.
Interesting thing here is under developer options, when i try to change the select usb configuration, it does not let me choose anything aside from charging.
Click to expand...
Click to collapse
ZF2 Driver
Download, and install it..
Then in in the driver list search for asus...hope you will find mtp device
KyleGerard said:
LP? Lollipop? I'm at Marsh 6.0.1
Click to expand...
Click to collapse
KyleGerard said:
How do I check what IFWI version I have?
Its been a year since i unlocked bootloader and switched to CM13, i just do the OTA updates so i forgot how to flash.
Apologies.
Click to expand...
Click to collapse
This is the 3rd time i ask for your IFWI version ?
You said its been a year since you installed CM13 , and the chances of you having M BL is virtually none existant
You probably have the LP version of M :good:
Unless someone magically sneaked in your home whilst asleep about July and upgraded your bootloader and installed 3.0.2M twrp.
The reason i asked for your IFWI version.
reboot to bootloader and what ifwi version does it say it is there ??????????
If over a year ago you will have LP version .
I will link you to the appropriate thread soon as we determine the correct ifwi version
Just as a side not , lots of people have had the same bug
I think its a driver issue that windows update have blocked
This IS the last time i ask you
timbernot said:
This is the 3rd time i ask for your IFWI version ?
You said its been a year since you installed CM13 , and the chances of you having M BL is virtually none existant
You probably have the LP version of M :good:
Unless someone magically sneaked in your home whilst asleep about July and upgraded your bootloader and installed 3.0.2M twrp.
The reason i asked for your IFWI version.
reboot to bootloader and what ifwi version does it say it is there ??????????
If over a year ago you will have LP version .
I will link you to the appropriate thread soon as we determine the correct ifwi version
Just as a side not , lots of people have had the same bug
I think its a driver issue that windows update have blocked
This IS the last time i ask you
Click to expand...
Click to collapse
Apologies. I do not know how to what IFWI version I have. How do I check?
You probably have the LP version of M -- I probably have the lollipop version of Marshmallow?
I am not really well versed with the terminologies now but if you could show me how to check the IFWI version, that'd be great.
......
timbernot said:
......
Click to expand...
Click to collapse
IFWI version is 0094.0173
KyleGerard said:
IFWI version is 0094.0173
Click to expand...
Click to collapse
Thank you - that is LP unlocked bootloader -- if your device is recognised in fastboot ? (was a question i asked you a few days ago but never got a reply to), please follow this :-
There are a few methods to get you back to stock and updated -- i choose the most simplest for you:good:
https://forum.xda-developers.com/showpost.php?p=70096075&postcount=19
timbernot said:
Thank you - that is LP unlocked bootloader -- if your device is recognised in fastboot ? (was a question i asked you a few days ago but never got a reply to), please follow this :-
There are a few methods to get you back to stock and updated -- i choose the most simplest for you:good:
https://forum.xda-developers.com/showpost.php?p=70096075&postcount=19
Click to expand...
Click to collapse
Thank you.
To check if my device is recognized in fastboot, I should connect phone to PC via cable and then reboot to bootloader, correct? I'll do that when I get home.
Would you recommend STOCK or a CUSTOM ROM yourself?
Hey guys.
Yesterday, I swapped out my Oneplus 6T, and got a new Pixel 3 XL 64GB.
I managed to have no issues unlocking the bootloader, and I do have relative familiarity with adb tools.
I'm running a Dell XPS 13 which has a USB Type C port which I have been using for cmd through Windows 10 in the beginning much to my own success.
After unlocking the bootloader, I had opt'd in for the ota update for Android Q and downloaded without hesitation.
I booted into TWRP, and when attempting to flash through the USB OTG cable it failed. I do not recall, and didn't think to use the webcam on my PC at the time to screenshot the errors.
I can get into the bootloader, however now when I run adb devices nothing appears.
If I boot a TWRP img, go to advanced > adb sideload and run a session. I can then proceed to run adb devices and successfully it reports back my serial number of the device. ( can provide screenshots of this if it's of any assistance )
However, no way have I been able to flash the Factory images, from as early as September 2018 to the latest for Android 9.0, nor have I have been able to reflash the Android Q factory images using cmd and the flash-all.bat
I've also followed this guide step by step uninstalling every ADB and Android related driver prior to installing the "lastest google drivers" https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849/page6
Sending sparse 'vendor_a' 2/2 (193888 KB) FAILED (Error reading sparse file) is where it hangs, and I'm absolutely at a stand still I wouldn't be posting if I hadn't searched and tried everything I could find any way related to it.
Also seems to be missing multiple sig files when running the flash-all.
If anyone can be of assistance it would be greatly appreciated I do not want to have to RMA to Google.
Thanks guys!
You can not adb sideload an ota in TWRP. It has to be the factory recovery.
When you are in the bootloader you need to do fastboot devices to see your device.
Did you get Q running? If you did I would download the factory image for it and edit the flash-all.bat to remove the -w.
Also make sure you have the latest platform-tools. I think they got updated when Q came out.
I've never had a problem but I know a lot of people have problems with C to C cables. May want to try an A to C cable if you can.
hatdrc said:
You can not adb sideload an ota in TWRP. It has to be the factory recovery.
When you are in the bootloader you need to do fastboot devices to see your device.
Did you get Q running? If you did I would download the factory image for it and edit the flash-all.bat to remove the -w.
Also make sure you have the latest platform-tools. I think they got updated when Q came out.
I've never had a problem but I know a lot of people have problems with C to C cables. May want to try an A to C cable if you can.
Click to expand...
Click to collapse
Sadly, I can't get to a USB A to C cable for 6 more days.
I did manage to get to Q, and I don't know what rushed me to thinking I could be flashing twrp on the beta.
I have been using factory images, I haven't sideloaded with adb, as I can't quite seem to figure out the flashing process for TWRP. Is there a method you could recommend we try?
I have the latest tools, and I'm 99.9% positive in one of the 20+ flashes I tried Today of various factory images, flashing the last factory with Q did not solve the trick with or without the -w.
If you are trying to flash from within TWRP, make sure everything is properly mounted.
Sent from my Pixel 3 XL
I think your using an old android Windows platform tools.
The newest version is r28.0.2, that should fix your problem.
Also in android Q with the pixel 3 xl, you can't flash anything with TWRP, the storage is not mounted.
Eudeferrer said:
If you are trying to flash from within TWRP, make sure everything is properly mounted.
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
As the other user has mentioned, I may be at a loss at being able to flash with TWRP after installing Q.
Gordietm said:
I think your using an old android Windows platform tools.
The newest version is r28.0.2, that should fix your problem.
Also in android Q with the pixel 3 xl, you can't flash anything with TWRP, the storage is not mounted.
Click to expand...
Click to collapse
Could you give me a detailed step by step, perhaps with the url's for the drivers & SDK tools.
I've used the links provided in the Soft Brick guide, and got the drivers direct from google themselves.
Although when I currently plug in my phone, it does install "Lemobile Android Drivers", the Google Drivers remove this but appear to be older drivers?
Download from here the latest platform tools, then flash all the factory image.
https://developer.android.com/studio/releases/platform-tools
Eudeferrer said:
If you are trying to flash from within TWRP, make sure everything is properly mounted.
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
Gordietm said:
Download from here the latest platform tools, then flash all the factory image.
https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
Okay will do, please confirm if this is correct.
Extra Android platform-tools, and factory image to the same folder, then extract the zip file found within the folder itself with the zip found from the Factory Image
I erase system a & b, and boot a & b
Flash-All should work start to finish right?
What are the odd's I'm going to be stuck with a RMA?
I'm sure I've exhausted myself trying this exact process so many times yesterday.
Download platform tools, vr28.0.2
Extract it and put the contents in a folder you'll remember
Download the factory image and extract it.
Put the bootloader, radio, system image zip and flash all.bat files in the same folder as the platform tools.
Connect your phone and put in bootloader mode.
Double click flash all.
Gordietm said:
Download platform tools, vr28.0.2
Extract it and put the contents in a folder you'll remember
Download the factory image and extract it.
Put the bootloader, radio, system image zip and flash all.bat files in the same folder as the platform tools.
Connect your phone and put in bootloader mode.
Double click flash all.
Click to expand...
Click to collapse
This sounds identical to what I've be doing, which has been causing the vendor_a issue, but I will give it another run for you shortly here. Just woke up, and rather be fully awake before I go tackling this.
If you can think of any other method, or even an explanation why the vendor img doesn't seem to work that would be awesome.
Also, there is threads I found through google here on XDA with users have a similar issue hanging at vendor, but not due to the same mistake. I'll find you the URL's shortly here.
It's because you were using r28.0.1 before, download r28.0.2
Gordietm said:
Download platform tools, vr28.0.2
Extract it and put the contents in a folder you'll remember
Download the factory image and extract it.
Put the bootloader, radio, system image zip and flash all.bat files in the same folder as the platform tools.
Connect your phone and put in bootloader mode.
Double click flash all.
Click to expand...
Click to collapse
Gordietm said:
It's because you were using r28.0.1 before, download r28.0.2
Click to expand...
Click to collapse
I've been using r28.0.02 just confirmed by looking at everything I had downloaded for trying to fix this yesterday :/
Ok, go back and flash the march android p factory image. Let it boot up and setup. Enroll the q beta program and update to q with your phone. Try that.
Gordietm said:
Ok, go back and flash the march android p factory image. Let it boot up and setup. Enroll the q beta program and update to q with your phone. Try that.
Click to expand...
Click to collapse
Was on the newest 9.0, updated through Q with the opt in, boot into twrp, flashed it, broke the phone ever since. That's the simplified issue, following the soft brick guide with updated tools & drivers using C to C cable no factory image has worked. All breaking at different points, closest an image got was the newest 9.0 failing at the Vendor img,
Gordietm said:
Ok, go back and flash the march android p factory image. Let it boot up and setup. Enroll the q beta program and update to q with your phone. Try that.
Click to expand...
Click to collapse
I have access to another phone here, and can make a video of what I'm exactly doing?
Would this be of any use to troubleshoot, I really don't want to end up on the path to an RMA.
At this point, you're probably best to talk to someone else who has more experience at this than I do.
Good luck!
Gordietm said:
Ok, go back and flash the march android p factory image. Let it boot up and setup. Enroll the q beta program and update to q with your phone. Try that.
Click to expand...
Click to collapse
Gordietm said:
At this point, you're probably best to talk to someone else who has more experience at this than I do.
Good luck!
Click to expand...
Click to collapse
Haha, well that's def not Google either, they straight up said RMA it.
Thanks for trying bro.
XZeeWhy said:
Haha, well that's def not Google either, they straight up said RMA it.
Thanks for trying bro.
Click to expand...
Click to collapse
The only other thing I can think of is wither the cable or the usb-c port on the computer. You said you can't get to an A to C cable but do you have another computer you could use?
XZeeWhy said:
Was on the newest 9.0, updated through Q with the opt in, boot into twrp, flashed it, broke the phone ever since. That's the simplified issue, following the soft brick guide with updated tools & drivers using C to C cable no factory image has worked. All breaking at different points, closest an image got was the newest 9.0 failing at the Vendor img,
Click to expand...
Click to collapse
After failing on the Vendor image, you can sideload the OTA and that should get you back up and running......for some strange reason I always seem to fail there and sideload the OTA at that point has ALWAYS fixed me.
GL!!
hatdrc said:
The only other thing I can think of is wither the cable or the usb-c port on the computer. You said you can't get to an A to C cable but do you have another computer you could use?
Click to expand...
Click to collapse
There is another PC here, but it doesn't have a Type C port, and I don't have an adapter on hand either.
Certainly willing to give Windows a clean install or do a live boot or install of linux to see if a fresh install or another operating system may help resolve it.
So stock factory images can not be flashed via TWRP?
It does seem to change various images on the device when rebooting to bootloader after using Flash All so I feel like it's getting quite a large amount of the partial install.
If I have boot loader & TWRP, I mean there has got to be a way right?
My phone arrived last night. I immediately, following the instructions I found here, magisk'd it. As soon as I flashed the patched image and rebooted... I found that the touch screen had stopped working.
So I booted into recovery (which was hard, because I can't figure out any way to shut my phone down), and wiped data / factory reset. The bootloader is still showing as unlocked. And the touch screen is still not working.
Does anybody know why this might be or what I should do about it? Note that I didn't buy from Google, I bought new from a well-reputed ebay seller...
Send it back. It sounds like a hardware issue.
sic0048 said:
Send it back. It sounds like a hardware issue.
Click to expand...
Click to collapse
Alright.
Problem number 2: if I lock the bootloader, it tells me there's no valid operating system on the phone and won't start up. It only starts up while the bootloader is locked. So... do I send it back with the bootloader unlocked and hope they don't mind?
DanHakimi said:
Alright.
Problem number 2: if I lock the bootloader, it tells me there's no valid operating system on the phone and won't start up. It only starts up while the bootloader is locked. So... do I send it back with the bootloader unlocked and hope they don't mind?
Click to expand...
Click to collapse
If they are a reputable seller on ebay they probably wouldn't want to sell you a broken phone as it hurts their reputation; I'm not saying it didn't happen, but individual sellers are usually careful on that end.
Have you at least tried fastboot flashing the stock "bonito" image yet and see if that restores your touch? https://developers.google.com/android/images
*Also, keep in mind that Q is supposed to be coming out pretty soon(which may or may not help you situation). Pixel phones supposedly get official Q on Sep 3rd or you can join the beta program if you can't wait until then.
good luck:good:
Reflash the factory image and relock the bootloader... It is an official process from Google, if that fails contact the seller and RMA the unit.
Hey buddy! I was in the same boat as you, so maybe your situation was the same as mine. My problem was that I had flashed the incorrect boot image. What I'd suggest is what I did: use a mouse to navigate through the phone and check the system version, then download the exact same OS version from google, extract, and flash that stock boot image. If it works, you can patch that same stock boot image with magisk and flash that one to get root and keep the touch screen working.
I hope this works out for ya. Cheers!
As it's new and you've got nothing to worry about saving I'd just flash the latest factory image via fastboot and once it's up extract the boot from that image and patch it. The fellow above is probably correct but there is one other thing, use an A to C cord, not the C to C cord for all your flashing.
Bob nesta said:
If they are a reputable seller on ebay they probably wouldn't want to sell you a broken phone as it hurts their reputation; I'm not saying it didn't happen, but individual sellers are usually careful on that end.
Have you at least tried fastboot flashing the stock "bonito" image yet and see if that restores your touch? https://developers.google.com/android/images
*Also, keep in mind that Q is supposed to be coming out pretty soon(which may or may not help you situation). Pixel phones supposedly get official Q on Sep 3rd or you can join the beta program if you can't wait until then.
good luck:good:
Click to expand...
Click to collapse
Yes, I've tried multiple versions of the bonito image, and none of them would flash properly. I'm really just trying to figure out if they're going to blame me because I unlocked the bootloader.
Will Q actually release tomorrow? Like, stock images up and everything? Oh, well, I might as well wait until tomorrow while I try to figure out their return policy.
DanHakimi said:
Yes, I've tried multiple versions of the bonito image, and none of them would flash properly. I'm really just trying to figure out if they're going to blame me because I unlocked the bootloader.
Will Q actually release tomorrow? Like, stock images up and everything? Oh, well, I might as well wait until tomorrow while I try to figure out their return policy.
Click to expand...
Click to collapse
You can relock the bootloader. Instructions are in the link I provided earlier. How would they know you unlocked it?
As far as Q - maybe? That's why I said "supposedly" it comes out the 3rd (https://www.theverge.com/platform/a...ndroid-10-pixel-september-3-release-leak-date) , but there are no guarantees in life (except death & taxes).
Again, just to be sure, you are using a USB A to C and not a C to C, correct?
DarkShadowMX said:
Hey buddy! I was in the same boat as you, so maybe your situation was the same as mine. My problem was that I had flashed the incorrect boot image. What I'd suggest is what I did: use a mouse to navigate through the phone and check the system version, then download the exact same OS version from google, extract, and flash that stock boot image. If it works, you can patch that same stock boot image with magisk and flash that one to get root and keep the touch screen working.
I hope this works out for ya. Cheers!
Click to expand...
Click to collapse
I don't have a USB-C mouse, but I guess I could keep trying images until one of them works...
krabman said:
Again, just to be sure, you are using a USB A to C and not a C to C, correct?
Click to expand...
Click to collapse
Yes, A to C.
Bob nesta said:
You can relock the bootloader. Instructions are in the link I provided earlier. How would they know you unlocked it?
Click to expand...
Click to collapse
No, again, like I said, I can't. I tried fastboot OEM lock. And I tried flashing multiple stock images. Nothing seems to be working. I can try again and get you the exact error messages...
DanHakimi said:
No, again, like I said, I can't. I tried fastboot OEM lock. And I tried flashing multiple stock images. Nothing seems to be working. I can try again and get you the exact error messages...
Click to expand...
Click to collapse
Please do. I'm no dev & can probably offer little to no help, but if you post your errors someone else may be able to help you out.
It could just be a cable/driver/fastboot issue & not the phone, so please provide error info.
Ok, do the full smash. This assumes a basic familiarity with flashing mechanics.
1. Download and install the latest fastboot package.
2. Download the latest image from google again.
3 Use a known good A to C usb cord
4 Before flashing the image type all the following commands one by one in fastboot...
fastboot erase system_a
fastboot erase system_b
fastboot erase boot_a
fastboot erase boot_b
fastboot reboot-bootloader
5 Flash the image using the flash all script.
6 Once you're up extract the boot from the image you flashed and patch it in magisk.
7 Flash the patched boot image.
DanHakimi said:
I don't have a USB-C mouse, but I guess I could keep trying images until one of them works...
Click to expand...
Click to collapse
I don't either. I used a USB OTG cable
Had a **** ton load of issues trying to go from rooted and TWRP with custom rom to Android 10.. Every time I ran the flash-all.bat it would fail at one stage or another.. Finally grabbed the Pie Ota from the site, sideloaded it through TWRP then wiped everything through stock recovery and then took the Android 10 update. My point is, use the OTA and sideload it
I was rooted on Android 10 beta 6 and trying to download the OTA through the phone update failed every time. I uninstalled magisk and restored images..but still failed. I finally had to sideload the OTA image and it finally updated. That was the only way to get mine to work. Then I took the boot image from beta 6 that was already patched through magisk and re-flashed it because the boot image from Android 10 official patched through magisk would not give root...kept failing. Then when I re-flashed last months beta 6 image, upon reboot the screen would freeze and no apps would load. I then booted into recovery and did a factory reset and upon reboot magisk was identified and root was acquired....phone worked perfectly after that and no issues....weird. I then just reloaded all of my apps from backup and was on Android 10 official, rooted through magisk.
I used the dongle included with the phone to make my usb-wireless mouse work. The OS is currently showing the July 5 version of Android 9. When I try flashing that specific version, I see what I attached in my screenshot. Other versions show similar bugs, although perhaps a few more. I haven't tried Android 10 yet...
DanHakimi said:
I used the dongle included with the phone to make my usb-wireless mouse work. The OS is currently showing the July 5 version of Android 9. When I try flashing that specific version, I see what I attached in my screenshot. Other versions show similar bugs, although perhaps a few more. I haven't tried Android 10 yet...
Click to expand...
Click to collapse
I suspect you are running out of hard disk space on the computer that you are using to try to flash all this with. I ran into a similar issue once when the C drive of my computer was nearly full. The system file ends up needing a lot of disk space in order for it to be unpacked. The error you are getting is that you are running out of space and it cannot unpack it. Again, this isn't phone memory space, this is actual computer hard drive space.
Hi all.
Maybe someone came across.
I update by ota to Android 13, the phone starts to reboot or gets stuck in the bootloop, stops entering the recovery and fastbootd. The bootloader from 13 is flashed on both slots, the full factory image does not get up due to the inability to boot into fastbootd. And even if the firmware still succeeds, the phone either boots into the firmware for 5 minutes and goes into reboot, or even hangs on the Google logo.
Moreover, if after that you flash it via fastboot to the 12.1 developer for the new bootloader, the phone loads and works completely properly, enters all partitions, does not reboot.
If i run Android 13 using DSU through the 12.1 developer, everything also works fine, without any problems
I tried all options of flashing android 13. And the full image, and ota by air, and ota through sideload recovery - always the same result.
What could be the reason, has anyone encountered and how can this problem be solved?
Delete the cache in recovery if all else fails it should fix whatever the conflict is
Shipoftheline said:
Delete the cache in recovery if all else fails it should fix whatever the conflict is
Click to expand...
Click to collapse
I can't enter to recocery after flashing android 13
Kirya27 said:
Hi all.
Maybe someone came across.
I update by ota to Android 13, the phone starts to reboot or gets stuck in the bootloop, stops entering the recovery and fastbootd. The bootloader from 13 is flashed on both slots, the full factory image does not get up due to the inability to boot into fastbootd. And even if the firmware still succeeds, the phone either boots into the firmware for 5 minutes and goes into reboot, or even hangs on the Google logo.
Moreover, if after that you flash it via fastboot to the 12.1 developer for the new bootloader, the phone loads and works completely properly, enters all partitions, does not reboot.
If i run Android 13 using DSU through the 12.1 developer, everything also works fine, without any problems
I tried all options of flashing android 13. And the full image, and ota by air, and ota through sideload recovery - always the same result.
What could be the reason, has anyone encountered and how can this problem be solved?
Click to expand...
Click to collapse
First make sure you don't have any other/older versions of adb/fastboot tools on your computer, just the latest Platform Tools. Also try using an A to C cable using USB 2.0 port. Then try flashing the factory image again or using Android Flash Tool.
Lughnasadh said:
First make sure you don't have any other/older versions of adb/fastboot tools on your computer, just the latest Platform Tools. Also try using an A to C cable using USB 2.0 port. Then try flashing the factory image again or using Android Flash Tool.
Click to expand...
Click to collapse
How is a bad cable connected or an old version platform-tools with the fact that after flashing the bootloader and some more files of the 13th version, my recovery, fastbootd and system stops loading and constantly reloading?
Kirya27 said:
How is a bad cable connected or an old version platform-tools with the fact that after flashing the bootloader and some more files of the 13th version, my recovery, fastbootd and system stops loading and constantly reloading?
Click to expand...
Click to collapse
You need the latest Platform Tools to properly flash everything. Many people have found that when having problems flashing that switching to an A to C cable using USB 2.0 solved their problems.
Lughnasadh said:
You need the latest Platform Tools to properly flash everything. Many people have found that when having problems flashing that switching to an A to C cable using USB 2.0 solved their problems.
Click to expand...
Click to collapse
This doesn't solve my problem. I always use the latest version of platform-tools or flash through Android FlashTool. I tried different cables, and think logically how this could be the case if Android 12.1 installed and working without any problems?
Kirya27 said:
This doesn't solve my problem. I always use the latest version of platform-tools or flash through Android FlashTool. I tried different cables, and think logically how this could be the case if Android 12.1 installed and working without any problems?
Click to expand...
Click to collapse
Well, you didn't mention you were using the latest Platform Tools, so I suggested it as that's one of the 1st steps of troubleshooting in these situations. You also didn't specifically mention using Android Flash Tool, so I suggested that as well.
Are you flashing BOTH SLOTS with the flash tool? Use Pixel Flasher and force flash both slots SEPARATELY don't choose the "both slots" button, it usually bricks for me. But see if thay fixes your problem. I couldn't use the android flash tool since about February of this year.
And since you did the OTA it might be a good time to bite the bullet and wipe if you haven't.
Gytole said:
Are you flashing BOTH SLOTS with the flash tool? Use Pixel Flasher and force flash both slots SEPARATELY don't choose the "both slots" button, it usually bricks for me. But see if thay fixes your problem. I couldn't use the android flash tool since about February of this year.
And since you did the OTA it might be a good time to bite the bullet and wipe if you haven't.
Click to expand...
Click to collapse
This sounds interesting. I'll try it today when I get home and post the results here.
Gytole said:
Are you flashing BOTH SLOTS with the flash tool? Use Pixel Flasher and force flash both slots SEPARATELY don't choose the "both slots" button, it usually bricks for me. But see if thay fixes your problem. I couldn't use the android flash tool since about February of this year.
And since you did the OTA it might be a good time to bite the bullet and wipe if you haven't.
Click to expand...
Click to collapse
I tried the method that you described and indeed, for some time the phone worked on Android 13 (however, when it was turned on, it wrote that this device was suddenly damaged due to something, photo below). True, after 15-20 minutes of use, phone rebooted into the bootloop, just for no reason at all. I flashed exactly as you said, separately in each slot ...
I have had this screen when I soft bricked after flashing lineage os. I fixed it with flashtool. My exact setup is windows 11, flashtool through Microsoft edge with the options to force flash and wipe device checked in flashtool. Flashtool has rescued my p6pro many times with this setup.
fil3s said:
У меня был этот экран, когда я завис после прошивки Lineage OS. Починил флештулом. Моя точная настройка — это Windows 11, flashtool через Microsoft Edge с параметрами принудительной прошивки и очистки устройства, отмеченными во flashtool. С помощью этой настройки Flashtool много раз выручал мой p6pro.
Click to expand...
Click to collapse
I've tried this method many times. Exactly the same as you described. Either the phone simply did not start, or it loaded, but rebooted into an eternal reboot after 15 minutes
Kirya27 said:
I've tried this method many times. Exactly the same as you described. Either the phone simply did not start, or it loaded, but rebooted into an eternal reboot after 15 minutes
Click to expand...
Click to collapse
If it happened to me. Idk. I think I'd fastboot -w in fastboot then try while still in fastboot
fil3s said:
If it happened to me. Idk. I think I'd fastboot -w in fastboot then try while still in fastboot
Click to expand...
Click to collapse
I tired fastboot -w many times
Kirya27 said:
I tired fastboot -w many times
Click to expand...
Click to collapse
Sorry if it sounds stupid.. but have you tried flashing a custom rom? Fastboot -w, fastboot update "customrom.zip" to see if they boot? Try paranoid android
fil3s said:
Sorry if it sounds stupid.. but have you tried flashing a custom rom? Fastboot -w, fastboot update "customrom.zip" to see if they boot? Try paranoid android
Click to expand...
Click to collapse
Tried. It turns out the same as on the stock firmware
I have faced this issue and the only solution is by sending it to the service center. They said it is the system issue and they replaced mainboard with a new one. And yeah. They said it is not related to android 13 update
apis903 said:
I have faced this issue and the only solution is by sending it to the service center. They said it is the system issue and they replaced mainboard with a new one. And yeah. They said it is not related to android 13 update
Click to expand...
Click to collapse
They clearly designed these phones to fail. They implied they would be usable for 6 years, but like all previous google phones, it will brick itself within 2. This 6 Pro is definitely the last product I buy from Google. I've had 3 other Nexus/pixel phones, none of which lasted. My sister is still using my hand-me-down iPhone 7 that I dropped off a cliff.
I can't do iphones though, and I don't want to support slave labor.. so my options are extremely limited. I'm only going to buy smartphones produced in the USA. It's dangerously cheap to produce phones using the less strict labor and material laws of foreign countries, phones are being treated as disposable, which is unacceptable. My modified Nexus 5X is perfectly usable despite having half the CPU disabled and being a 7 year old phone, thanks to overclocking. Companies should not release a new device unless it is a worthy upgrade over the previous one. It should happen every 3 years, not every year.
I just hope other nerds wake up and stop supporting Google. We have to boycott Google until they create desirable products. Pixel is so undesirable that they spend their ad money on woke bull**** that no one cares about except the sheep, but they like iPhones. Google is just burning our money and ignoring our needs.
Edit: I'm just salty that I got scammed by Google. They lost all of their people who cared. Google is full of corrupt people who want to make a buck. Pixel 7 is essentially the exact same as Pixel 6. The lack of a pro mode in the camera app perfectly represents Google's priorities. It would take one developer a couple days to add such a feature to the app. Google is not doing ANYTHING good.
good evening. hopefully someone can help. i jodated to android 14 ( Bad idea ) and was having a lot of problems so went to go back to 13 and then asked me to format. i deleted and cleared everything including the data. completely empty. i can get into fastboot and recovery though. thats it. tried to put factory 13 build on but nothing. cant get past fast boot. any help would be greatly appeciated
use flash.android.com
Faszfreddy said:
good evening. hopefully someone can help. i jodated to android 14 ( Bad idea ) and was having a lot of problems so went to go back to 13 and then asked me to format. i deleted and cleared everything including the data. completely empty. i can get into fastboot and recovery though. thats it. tried to put factory 13 build on but nothing. cant get past fast boot. any help would be greatly appeciated
Click to expand...
Click to collapse
Druboo666 said:
use flash.android.com
Click to expand...
Click to collapse
^^^this...exactly what I was going to suggest. This will get you back up and running...
Or one can also use pixel flasher... Right?
amritpal2489 said:
Or one can also use pixel flasher... Right?
Click to expand...
Click to collapse
Flash.andriod.com can do more than pixel flasher. have had the same issue with my phone seemingly dead being brought back to life using that website. (note i haven't tried andriod 14 it was when a rom flash went wrong)
amritpal2489 said:
Or one can also use pixel flasher... Right?
Click to expand...
Click to collapse
PixelFlasher does have a lot of the same capabilities as Android Flash Tool, but PF is more for rooting/kernel/ROM flashing than it is for recovery purposes -- which is the primary reason for AFT. PF has various different checks and protocols, while AFT has protocols more for properly flashing/resetting device to stock or recovery repair.
So while PF can flash the stock Full Factory image (to both slots and/or platform-tools checks and/or adding various arguments [without wiping, disabling verity&verification, etc.]), AFT links directly to Google's developers page that holds the Full Factory images and works just on flashing those.
Flash Tool saved my butt after I flashed the wrong kernel...
Visit this site on a PC, edit the settings and check the boxes 'wipe' and 'force flash partitions'
Android Flash Tool
flash.android.com
simplepinoi177 said:
^^^this...exactly what I was going to suggest. This will get you back up and running...
Click to expand...
Click to collapse
i tried this it cant find anything to install
Faszfreddy said:
i tried this it cant find anything to install
Click to expand...
Click to collapse
It's not a tool you install...it's all "run" through what browser you are using (Chrome, Firefox, Edge, etc.).
You click "Get Started", make sure you download and install the USB Drivers it suggests you should (if you have already, you can click "Already installed"), allow the browser "ADB access", click "Add new device" and then it will wait until you connect your device to the computer and the tool (within the browser) will detect it and continue on from there...
Try to particularly read & pay close attention to any steps or suggestions the site states as it will assist in connecting and/or any problem/troubleshooting you might need to do to get it working with the tool...
simplepinoi177 said:
It's not a tool you install...it's all "run" through what browser you are using (Chrome, Firefox, Edge, etc.).
You click "Get Started", make sure you download and install the USB Drivers it suggests you should (if you have already, you can click "Already installed"), allow the browser "ADB access", click "Add new device" and then it will wait until you connect your device to the computer and the tool (within the browser) will detect it and continue on from there...
Try to particularly read & pay close attention to any steps or suggestions the site states as it will assist in connecting and/or any problem/troubleshooting you might need to do to get it working with the tool...
Click to expand...
Click to collapse
this is all it will do. keeps trying to find a build to flash
Faszfreddy said:
this is all it will do. keeps trying to find a build to flash
Click to expand...
Click to collapse
Had you checked what's under that pull-down option (down arrow) on the right of your device ("Pixel 6 Pro (raven)")? or searching "raven" in the search box?
In any case, I went ahead and searched the latest (non-Verizon) build number for your device (raven), and you should be able to find the latest (May Full Factory Image) as: TQ2A.230505.002.
If you are using your device on Verizon's network, the "build" would be: TQ2A.230505.002.G1
These will update it to Android 13 (latest); in case you are still on Android 12 and/or do not wish to upgrade (for whatever reason).
simplepinoi177 said:
It's not a tool you install...it's all "run" through what browser you are using (Chrome, Firefox, Edge, etc.).
You click "Get Started", make sure you download and install the USB Drivers it suggests you should (if you have already, you can click "Already installed"), allow the browser "ADB access", click "Add new device" and then it will wait until you connect your device to the computer and the tool (within the browser) will detect it and continue on from there...
Try to particularly read & pay close attention to any steps or suggestions the site states as it will assist in connecting and/or any problem/troubleshooting you might need to do to get it working with the tool...
Click to expand...
Click to collapse
thank you. Android Flash Tool fixed it thanks again guys