Related
My phone is stuck in a boot loop.
The Oneplus one toolbox says "waiting for device".
My phone is not recognised by windows. when i try to install the drivers again, "android phone" is not on the list. i dont have twrp installed.
Dont really care about the data at the moment. Can someone help me?
Shounak Gupte said:
My phone is stuck in a boot loop.
The Oneplus one toolbox says "waiting for device".
My phone is not recognised by windows. when i try to install the drivers again, "android phone" is not on the list. i dont have twrp installed.
Dont really care about the data at the moment. Can someone help me?
Click to expand...
Click to collapse
The first thing you need to do is get rid of the toolbox. Nothing but trouble. Plus, if you can't modify your phone without a toolbox you shouldn't be modifying it at all. Uninstall whatever drivers you have installed, reboot the PC, install these drivers, reboot PC again, connect phone, flash stock images (see section 8 of my guide thread).
Exactly how did your phone get into the boot loop?
Transmitted via Bacon
drivers
timmaaa said:
The first thing you need to do is get rid of the toolbox. Nothing but trouble. Plus, if you can't modify your phone without a toolbox you shouldn't be modifying it at all. Uninstall whatever drivers you have installed, reboot the PC, install these drivers, reboot PC again, connect phone, flash stock images (see section 8 of my guide thread).
Exactly how did your phone get into the boot loop?
Transmitted via Bacon
Click to expand...
Click to collapse
i've uninstalled the drivers and installed the ones you suggested. my PC still doesnt recognise the phone(check image attached). any solutions?
i was browsing something on chrome and the phone suddenly got stuck. i restarted the phone, but then was stuck on the loading screen.
Shounak Gupte said:
i've uninstalled the drivers and installed the ones you suggested. my PC still doesnt recognise the phone(check image attached). any solutions?
i was browsing something on chrome and the phone suddenly got stuck. i restarted the phone, but then was stuck on the loading screen.
Click to expand...
Click to collapse
Did you reboot the PC between each uninstall and install? Are you using the official OnePlus usb cable?
Transmitted via Bacon
timmaaa said:
Did you reboot the PC between each uninstall and install? Are you using the official OnePlus usb cable?
Transmitted via Bacon
Click to expand...
Click to collapse
Yes... i did. I was reading somewhere and someone suggested using a different cable or a different PC. i'll try both today at work and report back.
no luck
Shounak Gupte said:
Yes... i did. I was reading somewhere and someone suggested using a different cable or a different PC. i'll try both today at work and report back.
Click to expand...
Click to collapse
ok.. so another computer & cable worked.
I've followed your tutorial.
first unlocked the bootloader.
then section 8 all of it.
still nothing. i'm still on the oneplus loading screen. any other options?
Shounak Gupte said:
ok.. so another computer & cable worked.
I've followed your tutorial.
first unlocked the bootloader.
then section 8 all of it.
still nothing. i'm still on the oneplus loading screen. any other options?
Click to expand...
Click to collapse
Try this:
http://forum.xda-developers.com/showthread.php?t=2970390
Transmitted via Bacon
timmaaa said:
Try this:
http://forum.xda-developers.com/showthread.php?t=2970390
Transmitted via Bacon
Click to expand...
Click to collapse
awesome!! this worked. i lost all data though.
any tips on how to prevent the magical boot screen?
Shounak Gupte said:
awesome!! this worked. i lost all data though.
any tips on how to prevent the magical boot screen?
Click to expand...
Click to collapse
I'm pretty sure you just got unlucky and had a corrupt persist partition, it's a bug that has happened to a few people, that particular automated flash tool flashes the stock images plus it flashes the persist partition. There isn't really anything you can do it avoid it, but i don't think I've seen it affect the same phone twice.
Transmitted via Bacon
timmaaa said:
I'm pretty sure you just got unlucky and had a corrupt persist partition, it's a bug that has happened to a few people, that particular automated flash tool flashes the stock images plus it flashes the persist partition. There isn't really anything you can do it avoid it, but i don't think I've seen it affect the same phone twice.
Transmitted via Bacon
Click to expand...
Click to collapse
i think i spoke a bit too soon. everything worked fine, but now my phone is getting stuck when it boots. the screen it totally unresponsive. this was the same thing which happened when i restarted my phone. it might be some app i have installed.
i might have to redo the process.
is there a way to find out which one it is?
The only real way to find out would be to start fresh and introduce apps one at a time to see which one is the culprit. But I'd be surprised if an app was causing this.
timmaaa said:
The only real way to find out would be to start fresh and introduce apps one at a time to see which one is the culprit. But I'd be surprised if an app was causing this.
Click to expand...
Click to collapse
I did the whole process 2 times. the phone works fine for a few days and now its stuck in the boot loop again. I have already contacted OPO support, but waiting for them to get back to me.
any solutions in the mean time?
Shounak Gupte said:
I did the whole process 2 times. the phone works fine for a few days and now its stuck in the boot loop again. I have already contacted OPO support, but waiting for them to get back to me.
any solutions in the mean time?
Click to expand...
Click to collapse
Did you install your apps again or is this still happening without them?
timmaaa said:
Did you install your apps again or is this still happening without them?
Click to expand...
Click to collapse
i installed them one at a time. its all the usual apps. nothing special. the phone worked fine until today morning.
I think you'll need to talk to OnePlus support about this, it doesn't seem right especially after using their own reflash tool.
timmaaa said:
I think you'll need to talk to OnePlus support about this, it doesn't seem right especially after using their own reflash tool.
Click to expand...
Click to collapse
the OPO support cannot seem to fix the issue. they have asked me to send them the phone back and i might get a replacement.
the issue is, I'm in Australia. the nearest location I can ship to is HK. There's going to be a long wait for my replacement to arrive. any other solutions?
Shounak Gupte said:
the OPO support cannot seem to fix the issue. they have asked me to send them the phone back and i might get a replacement.
the issue is, I'm in Australia. the nearest location I can ship to is HK. There's going to be a long wait for my replacement to arrive. any other solutions?
Click to expand...
Click to collapse
I've gone through any potential solution that I know of. I'm in Australia too, it sucks, but we took a risk when buying this phone that something like this might happen.
Transmitted via Bacon
So I read other threads with similar issues but nothings seemed to work.
Basically my LG G3 (AT&T) started acting odd one day. Resetting every 3-5 minutes, overheating (more than usual), wouldn't connect to Wi-Fi. Eventually I reset it and the problems got worse. I downloaded a boot logger that can't figure out why, there's no physical damage (EDIT: when this first started, I noticed that the little pink water damage sticker on the battery was, well pink, however I never got it wet and could've been pink before but I don't know), I factory reset it again and nothing, swapped the battery and everything. I could've done more but it is still under warranty so I kinda gave up and decided to exchange it.
The new one is on the way and comes tomorrow or Wednesday however now my G3 won't even turn on, or rather it stays locked on the boot screen (the LG logo specifically) it won't go past that. I tried to hard reset it with the power button and it gets to the screen with the android logo with its chest open and just resets again.
I'm not trying to fix it anymore I just want advice on wiping it basically as I can't even wipe it through my computer. With my last phone what I did before selling it, and what I wanted to do again, is encrypt it, then factory reset to just be extra safe and I wanna know if there's anyway I can do this basically with the phone like this, or if I can get it to a state where I can do that again. I'm not all too familiar with android this low level so I want to know if I can basically "hard" wipe it because I can't even connect it to my computer (it keeps resetting).
Also one time on a boot it said the kernel crashed, don't know how relevant that is as it only happened once out of at least 1,000 times by this point.
Any help would be appreciated, super frustrated right now.
Thank you!
dan1229 said:
So I read other threads with similar issues but nothings seemed to work.
Basically my LG G3 (AT&T) started acting odd one day. Resetting every 3-5 minutes, overheating (more than usual), wouldn't connect to Wi-Fi. Eventually I reset it and the problems got worse. I downloaded a boot logger that can't figure out why, there's no physical damage (EDIT: when this first started, I noticed that the little pink water damage sticker on the battery was, well pink, however I never got it wet and could've been pink before but I don't know), I factory reset it again and nothing, swapped the battery and everything. I could've done more but it is still under warranty so I kinda gave up and decided to exchange it.
The new one is on the way and comes tomorrow or Wednesday however now my G3 won't even turn on, or rather it stays locked on the boot screen (the LG logo specifically) it won't go past that. I tried to hard reset it with the power button and it gets to the screen with the android logo with its chest open and just resets again.
I'm not trying to fix it anymore I just want advice on wiping it basically as I can't even wipe it through my computer. With my last phone what I did before selling it, and what I wanted to do again, is encrypt it, then factory reset to just be extra safe and I wanna know if there's anyway I can do this basically with the phone like this, or if I can get it to a state where I can do that again. I'm not all too familiar with android this low level so I want to know if I can basically "hard" wipe it because I can't even connect it to my computer (it keeps resetting).
Also one time on a boot it said the kernel crashed, don't know how relevant that is as it only happened once out of at least 1,000 times by this point.
Any help would be appreciated, super frustrated right now.
Thank you!
Click to expand...
Click to collapse
Just follow my G3 back to stock guide and use the tot method.
Sent from my iPhone using Tapatalk
If the guide don't work. Try this. every guide did not work for me. Look at post 5.
http://forums.androidcentral.com/ge...ricked-lg-g2-stuck-twrp-no-download-mode.html
Sent from my LG-D850 using XDA Free mobile app
hyelton said:
Just follow my G3 back to stock guide and use the tot method.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Thank you sososo much, I'm gonna give it a shot later tonight.
hyelton said:
Just follow my G3 back to stock guide and use the tot method.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
So I'm going through the tot method, however when I plug the phone in I get an error that "Windows malfunctioned the last time the device was plugged in" I plugged it in last night to see if I could do anything and it kept resetting. But in device manager it just shows up as an unknown USB device and there is now no ports section.
dan1229 said:
So I'm going through the tot method, however when I plug the phone in I get an error that "Windows malfunctioned the last time the device was plugged in" I plugged it in last night to see if I could do anything and it kept resetting. But in device manager it just shows up as an unknown USB device and there is now no ports section.
Click to expand...
Click to collapse
What's your OS? If windows 8/10 you'll need to unhide. But if your getting a windows malfunctioned the last time error that would be your computer problem.
Sent from my iPhone using Tapatalk
hyelton said:
What's your OS? If windows 8/10 you'll need to unhide. But if your getting a windows malfunctioned the last time error that would be your computer problem.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Windows 10. It seems like it can't recognize the device, it says under USB controllers: " Unknown USB Device (Device Descriptor Request Failed)"
dan1229 said:
Windows 10. It seems like it can't recognize the device, it says under USB controllers: " Unknown USB Device (Device Descriptor Request Failed)"
Click to expand...
Click to collapse
Yeah you would need to try another computer.
Sent from my iPhone using Tapatalk
hyelton said:
Yeah you would need to try another computer.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
I just tried it on another computer, exact same error. It says that there could be something wrong with the device.
dan1229 said:
I just tried it on another computer, exact same error. It says that there could be something wrong with the device.
Click to expand...
Click to collapse
Still windows 10? I've never even seen that error before. Try installing drivers from LGs site?
Sent from my iPhone using Tapatalk
hyelton said:
Still windows 10? I've never even seen that error before. Try installing drivers from LGs site?
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Do you know where I could find the driver files? Not the executable, I'm gonna try to "force" update the driver cause it just can't recognize the device but I need the drivers and can't find them.
And yea still Windows 10.
dan1229 said:
Do you know where I could find the driver files? Not the executable, I'm gonna try to "force" update the driver cause it just can't recognize the device but I need the drivers and can't find them.
And yea still Windows 10.
Click to expand...
Click to collapse
Just go to LGs website. The executable should work fine. Are you not trying the ones in the Op? You might want to use a different OS. Not that I'm blaming 10 but for a lot of reasons I had to downgrade.
Sent from my iPhone using Tapatalk
hyelton said:
Just go to LGs website. The executable should work fine. Are you not trying the ones in the Op? You might want to use a different OS. Not that I'm blaming 10 but for a lot of reasons I had to downgrade.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
I'm using the ones on your guide, they're on oceanhost
dan1229 said:
I'm using the ones on your guide, they're on oceanhost
Click to expand...
Click to collapse
Okay try the ones from LGs site and see what happens.
Sent from my iPhone using Tapatalk
hyelton said:
Okay try the ones from LGs site and see what happens.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
I think I figured it out, only issue (and this is the dumbest yet) is I can't find the .tot file? I downloaded the D850 stock image zip and it's not in there as far as i can tell.
dan1229 said:
I think I figured it out, only issue (and this is the dumbest yet) is I can't find the .tot file? I downloaded the D850 stock image zip and it's not in there as far as i can tell.
Click to expand...
Click to collapse
You extract the zip file... All TOT's are placed in zip files due to size to help people who download it.
hyelton said:
You extract the zip file... All TOT's are placed in zip files due to size to help people who download it.
Click to expand...
Click to collapse
I downloaded the wrong zip my bad XD. Also this doesn't void the warranty does it?
dan1229 said:
I downloaded the wrong zip my bad XD. Also this doesn't void the warranty does it?
Click to expand...
Click to collapse
Wait. What are you trying to do? Why are you needing to flash it if you haven't already voided your warranty? Rooting/Custom rom "voids warranty" in itself.
Flash a tot or kdz puts the phone 100% complete back to stock as you bought it.
hyelton said:
Wait. What are you trying to do? Why are you needing to flash it if you haven't already voided your warranty? Rooting/Custom rom "voids warranty" in itself.
Flash a tot or kdz puts the phone 100% complete back to stock as you bought it.
Click to expand...
Click to collapse
I have the warranty replacement device coming, I just wanted to totally wipe this device but I can't even get it to boot properly.
dan1229 said:
I have the warranty replacement device coming, I just wanted to totally wipe this device but I can't even get it to boot properly.
Click to expand...
Click to collapse
Why won't it boot properly? Also keep in mind this is the only method of going back stock. Also the method only requires you to be in download mode.
Sent from my iPhone using Tapatalk
Hi guys,
i have a pixel and i want to enrrol to the beta program, i just done the process but it seams that update is not arriving, its posible that verizon pixels can't enroll to beta program?
http://www.droid-life.com/2017/01/30/android-7-1-2-beta-download-update-nexus-pixel/
Regards
You can download the full image here
I dont have oem unlocked. I can sideloade it?
Yea even i didn't get it. I guess it not for the verizon phones.
Can anyone who has upgraded to 7.1.2 let us know if it appears stable enough for a daily driver and have they noticed any differences ? Thank you.....
Another locked bootloader VZW customer here who enrolled and is waiting for OTA. I think we'll get it, just have to wait for OTA's to start. Google let us enroll, and we seem to have gotten updates from Google and not VZW so far. I think it'll just take a day or 2 to start rolling.
I installed 7.1.2 briefly. No changes that I noticed besides radio and boot IMG. Seemed stable enough for daily, I went back to PN because of substratum.
I am a non VZW pixel user (Koodo - Canada) and have not received the OTA after signing up yesterday. They note that it may take 24 hours and looks like it's going to for me.
k.s.deviate said:
I installed 7.1.2 briefly. No changes that I noticed besides radio and boot IMG. Seemed stable enough for daily, I went back to PN because of substratum.
Click to expand...
Click to collapse
I know that the bootloader is what loads the Android filesystem to the boot image, I wonder if it can somehow be manipulated to unlock and root since you mention that the boot image is different? Does anyone know? Thanks
Just about 24 hours of enrollment here on my VZW Pixel with no OTA yet. Google support confirmed my device was eligible... Has ANYONE, regardless of carrier, received a beta OTA?
farfromovin said:
Just about 24 hours of enrollment here on my VZW Pixel with no OTA yet. Google support confirmed my device was eligible... Has ANYONE, regardless of carrier, received a beta OTA?
Click to expand...
Click to collapse
Signed up yesterday for both my Pixel (VZW sim) and Pixel XL (Project Fi sim) both bought direct from Google. Pixel XL rec'd update almost immediately not yet on Pixel so far.
If anyone gets the OTA, please pull and post it. OTA's can be flashed in TWRP, followed by a re-flash of TWRP to keep custom recovery. I'm too lazy to download the full firmware, edit it, and flash with a computer.
Sent from my Pixel using Tapatalk
joshw0000 said:
If anyone gets the OTA, please pull and post it. OTA's can be flashed in TWRP, followed by a re-flash of TWRP to keep custom recovery. I'm too lazy to download the full firmware, edit it, and flash with a computer.
Click to expand...
Click to collapse
The edit you mention. Is that just removing the -w command from the flash all script. Or is there more involved in updating from a factory image?
murryrulz said:
The edit you mention. Is that just removing the -w command from the flash all script. Or is there more involved in updating from a factory image?
Click to expand...
Click to collapse
Nope it's exactly that. Just remove -w so it doesn't wipe the device. It's how I update my Pixel and 5X since I'm impatient waiting for OTAs.
murryrulz said:
The edit you mention. Is that just removing the -w command from the flash all script. Or is there more involved in updating from a factory image?
Click to expand...
Click to collapse
Correct. And for some reason the flash-all.bat never works for me. It fails towards the end of the flash. I have to run it through one of those tool kits for it to accept it.
Flashing the OTA in TWRP is a smaller download, quicker, no PC, and it consistently works for me.
Like I said, I'm lazy lol.
Sent from my Pixel using Tapatalk
joshw0000 said:
Correct. And for some reason the flash-all.bat never works for me. It fails towards the end of the flash. I have to run it through one of those tool kits for it to accept it.
Flashing the OTA in TWRP is a smaller download, quicker, no PC, and it consistently works for me.
Like I said, I'm lazy lol.
Click to expand...
Click to collapse
I had the same problem a long time ago. Turns out I was using an old version of fastboot. Once I updated it I had no problem with the flashall.bat
OTA hasn't rolled for the pixel yet, likely "soon", my guess is today or tomorrow at the latest since XL has gone out. I am on project FI and got the pixel through the play store fyi
murryrulz said:
I had the same problem a long time ago. Turns out I was using an old version of fastboot. Once I updated it I had no problem with the flashall.bat
Click to expand...
Click to collapse
I've tried updating mine but that doesn't seem to help. I spent a considerable amount of time working on it one day with no luck. Mine is installed so that it'll work from any directory (I don't have to put my files in the same directory). I even tried putting the new adb/fastboot in the same folder as the flash-all.bat with the same results.
Sent from my Pixel using Tapatalk
I am also in the waiting for the OTA camp and use an unlocked Verizon Pixel and PIxel XL. I have had better luck using the TWRP sideload method and it installing to the other slot with each subsequent sideload appears to me a more consistent way to keep everything updated in the same way that the system OTA works.
joshw0000 said:
I've tried updating mine but that doesn't seem to help. I spent a considerable amount of time working on it one day with no luck. Mine is installed so that it'll work from any directory (I don't have to put my files in the same directory). I even tried putting the new adb/fastboot in the same folder as the flash-all.bat with the same results.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Get rid of windows, use Linux, no messing around with anything, it just works ?
-------- runs -----_ducks_---- runs ----
Sent from my Pixel using XDA-Developers Legacy app
Hello all,
I did a big mistake, I wanted to go back from DP 3 to Android 11 and once I was going to do the CMD steps, I downloaded the wrong Firmware for the Pixel 5
I didnt see that mistake until I started the steps and the phone turned off and did not turn on anymore.
I know I made a big mistake, but can I do to revert this? I try to restart the phone but nothing, not via power button for 10 or 20 or 30 sec.
Please help
vlc_marcos said:
Hello all,
I did a big mistake, I wanted to go back from DP 3 to Android 11 and once I was going to do the CMD steps, I downloaded the wrong Firmware for the Pixel 5
I didnt see that mistake until I started the steps and the phone turned off and did not turn on anymore.
I know I made a big mistake, but can I do to revert this? I try to restart the phone but nothing, not via power button for 10 or 20 or 30 sec.
Please help
Click to expand...
Click to collapse
No duplicated thread are permitted
Please help us to keep the forums neat
Thanks
vlc_marcos said:
I downloaded the wrong Firmware for the Pixel 5
Click to expand...
Click to collapse
So you used a firmware that was older or one that was for a different device?
Is the bootloader unlocked?
What exactly did you download?
Does the phone charge?
l7777 said:
So you used a firmware that was older or one that was for a different device?
Is the bootloader unlocked?
What exactly did you download?
Does the phone charge?
Click to expand...
Click to collapse
I used the firmware of pixel 4a 5g and I wanted to go from DP3 to android 11.
I cannot see the phone charging . I try long press in any of the buttons and different combinations and nothing. Zero signs of life
vlc_marcos said:
I used the firmware of pixel 4a 5g and I wanted to go from DP3 to android 11.
I cannot see the phone charging . I try long press in any of the buttons and different combinations and nothing. Zero signs of life
Click to expand...
Click to collapse
when its plugged into a computer does the computer see it at all?
thewraith420 said:
when its plugged into a computer does the computer see it at all?
Click to expand...
Click to collapse
not at all is there some kind of hard unbrick??
vlc_marcos said:
not at all is there some kind of hard unbrick??
Click to expand...
Click to collapse
Unfortunately i think your only option will be to send it in to google at this point.. wish you luck though maybe someone has an idea.
thewraith420 said:
Unfortunately i think your only option will be to send it in to google at this point.. wish you luck though maybe someone has an idea.
Click to expand...
Click to collapse
Mine bricked about a month ago and Google suggested uBreakiFix. They tried to do a force flash on it but it didn't work. They ended up replacing the motherboard which fixed it, but now my proximity sensor is always on. I don't know if they can fix that or if it will require another motherboard.
I have same problem, but i can go to bootloader. The problem my phone is locked bootloader and i don't have recovery mode. And when i try to flash it because of locked bootloader i can't do anything. Is there any solution for unbrick locked bootloader?
p_a_r_s_a7 said:
I have same problem, but i can go to bootloader. The problem my phone is locked bootloader and i don't have recovery mode. And when i try to flash it because of locked bootloader i can't do anything. Is there any solution for unbrick locked bootloader?
Click to expand...
Click to collapse
Did you use any special way to even turn on the phone or reach the bootloader?
vlc_marcos said:
Did you use any special way to even turn on the phone or reach the bootloader?
Click to expand...
Click to collapse
I did everything, unfortunately my bootloader is locked and that's problem. With locked bootloader i can't do anything. I had same problems with other phones before and i could unbrick. But for pixel devices i can't find some tool to unbrick.
p_a_r_s_a7 said:
I did everything, unfortunately my bootloader is locked and that's problem. With locked bootloader i can't do anything. I had same problems with other phones before and i could unbrick. But for pixel devices i can't find some tool to unbrick.
Click to expand...
Click to collapse
how did you end up with it like that with bootloader locked? what caused it?
I have the same issue like p_a_r_s_a7 with my Pixel 5.
Only fastboot mode: can't find valid operating system
After flashing the 'right' OTA image for Android 12 DP3 the device cannot be restored anymore.
The image was successfully flashed by 'adb sideload' as recommended.
Seems that a locked bootloader is not 100% save from 'flashed to death'
600 EURO paperwight.
I had this same issue on my 4a 5g and after many hours I managed to fix it. I don't recall exactly but I went through every option of flashing stock via fastboot and android flash tool it eventually worked this was 2 months ago
Cj719 said:
I had this same issue on my 4a 5g and after many hours I managed to fix it. I don't recall exactly but I went through every option of flashing stock via fastboot and android flash tool it eventually worked this was 2 months ago
Click to expand...
Click to collapse
But you could reach fastboot right?
Cj719 said:
I had this same issue on my 4a 5g and after many hours I managed to fix it. I don't recall exactly but I went through every option of flashing stock via fastboot and android flash tool it eventually worked this was 2 months ago
Click to expand...
Click to collapse
Android flash tool immediately detect the locked bootloader and stopped without flashing.
I've tried to check/uncheck every option but no luck. I've used Windows 10.
Did you used the common USB driver requested by Android flash tool ?
Anything else that could be special, eg Linux environment ( what distro, version .. )
Any detail could help..
speo said:
Android flash tool immediately detect the locked bootloader and stopped without flashing.
I've tried to check/uncheck every option but no luck. I've used Windows 10.
Did you used the common USB driver requested by Android flash tool ?
Anything else that could be special, eg Linux environment ( what distro, version .. )
Any detail could help..
Click to expand...
Click to collapse
Windows 10 laptop, adb minimal drivers, made sure device was detected, attempted through fastboot and android flash tool, that's the only things I remember my apologies.
speo said:
I have the same issue like p_a_r_s_a7 with my Pixel 5.
Only fastboot mode: can't find valid operating system
After flashing the 'right' OTA image for Android 12 DP3 the device cannot be restored anymore.
The image was successfully flashed by 'adb sideload' as recommended.
Seems that a locked bootloader is not 100% save from 'flashed to death'
600 EURO paperwight.
Click to expand...
Click to collapse
I send back to Google, i couldn't fix it
Cj719 said:
Windows 10 laptop, adb minimal drivers, made sure device was detected, attempted through fastboot and android flash tool, that's the only things I remember my apologies.
Click to expand...
Click to collapse
thank you anyway, it was a little light on the horizon at least ;-)
p_a_r_s_a7 said:
I send back to Google, i couldn't fix it
Click to expand...
Click to collapse
have you been charged ?
Mine is from another dealer, will see..
I am a very experienced ROM enthusiast and owned plenty of Xiaomi/Oneplus devices.. This is my first pixel device. I loved the phone, more than the other mentioned companies. My pixel 7 Pro was my prized possession.. I've came close a couple of times botching a ROM flash, even once with my p7p (installing evo with February firmware instead of Jan, phone would boot to bootloader for a total of 2 seconds before dying again, had to spam flash phone in pixel flasher app until it recognized and luckily it did) but this time, trying to go from latest feb build to jan before flashing evo, my ****ing cable did something in the middle of flashing the second partition (b partition) and was almost to system, the partition it flashes before booting.. it was flashing the product partition.. literally already flashed every other partition except partition and system on the b slot. A slot was fully flashed.. phone literally wont respond to plugging into computer, into charger, holding down every combination of buttons... doesn't matter. I'm stumped how flashing a factory rom could have gone this horribly.. especially so late into the flashing process..
Beware guys; Make sure the cable you're using to flash is stable!
attached in this post is the logs I have pulled from the pixel flasher app.. if someone could bounce some ideas off of me or somehow make this make sense to me, it would be gladly appreciated.
Holding down the down volume button when starting doesn't enter bootloader? If it does, use Google's online Android Flash tool to go back to stock.
Try a different cable.
Try a different USB port.
Try another computer as well.
If any of these prompt some response, I think there's hope. Also try booting into fastboot from bootloader as well as recovery.
Prob hard brick.
im wondering, since i am just flashing the feb factory image on my rooted pixel and read this thread here: if my laptop (from which i operate the flashing procedure) were to malfunction like it did last night (bsod) - would i hard brick my phone, too? isnt that, where the other slot comes into play?
does this mean, every time i flash, my pc/laptop should never run into any issues whilst flashing or otherwise my phone will be effed?
xflowy said:
im wondering, since i am just flashing the feb factory image on my rooted pixel and read this thread here: if my laptop (from which i operate the flashing procedure) were to malfunction like it did last night (bsod) - would i hard brick my phone, too? isnt that, where the other slot comes into play?
does this mean, every time i flash, my pc/laptop should never run into any issues whilst flashing or otherwise my phone will be effed?
Click to expand...
Click to collapse
If you device is flashing something like the bootloader, and connection breaks for any reason at all, or the problem closes, etc, it will be a hard brick. You may get lucky, and it may be something unessential.
Arealhooman said:
If you device is flashing something like the bootloader, and connection breaks for any reason at all, or the problem closes, etc, it will be a hard brick. You may get lucky, and it may be something unessential.
Click to expand...
Click to collapse
uff ok. is there any way to avoid this? i mean, even my desktop pc (which is stable) could suffer from a power shortage in the house for example.
xflowy said:
uff ok. is there any way to avoid this? i mean, even my desktop pc (which is stable) could suffer from a power shortage in the house for example.
Click to expand...
Click to collapse
Nope. Get a battery. If a flash fails, 75 percent chance ur ****ed (and yes, I am pulling these statistics out off my ass, but I doubt I’m too much off)
Arealhooman said:
Nope. Get a battery. If a flash fails, 75 percent chance ur ****ed (and yes, I am pulling these statistics out off my ass, but I doubt I’m too much off)
Click to expand...
Click to collapse
A battery for my desktop PC?
xflowy said:
A battery for my desktop PC?
Click to expand...
Click to collapse
Google for "uninterruptible power supply" ...
xflowy said:
A battery for my desktop PC?
Click to expand...
Click to collapse
Yeah, no idea.
Maybe I'm wrong, but although the whole flashing process can fail if communication with device breaks, it's hard to actually fail while flashing a partition? Because the system first pushes the whole file and only then does it begin actual flashing. So whatever partition you are pushing at any given moment, if it fails to push it in its entirety, then it won't flash it... Unless data is corrupted during transfer?
xflowy said:
im wondering, since i am just flashing the feb factory image on my rooted pixel and read this thread here: if my laptop (from which i operate the flashing procedure) were to malfunction like it did last night (bsod) - would i hard brick my phone, too? isnt that, where the other slot comes into play?
does this mean, every time i flash, my pc/laptop should never run into any issues whilst flashing or otherwise my phone will be effed?
Click to expand...
Click to collapse
Arealhooman said:
If you device is flashing something like the bootloader, and connection breaks for any reason at all, or the problem closes, etc, it will be a hard brick. You may get lucky, and it may be something unessential.
Click to expand...
Click to collapse
The real answer to this is why google and the android community as a whole is pushing away from having a supporting third party recovery menu (implementing new partitions like init_boot and vendor_boot for recovery, also no working twrp). Why do you think Evolution ROM pushes so hard to be different and when flashing their newest build you do it not through the usual scary tedious bootloader way (THE SAME WAY WE ARE SUPPOSED TO FLASH OUR FACTORY ROMS) to making their own recovery, which obviously means only flashing one partition, and adb sideloading the rom. its like google wants you to break your phone and they are making it more convenient for third party roms to package theirs the same way. i should have never left evo.. haha.
Oh, and sorry for the late reply. I thought I would leave my phone alone for a little to see if it would help; I'm accident prone and lose things constantly, and what do ya know I just lost my phone that I can't even call to find lmao. Ill keep updated on everyones opinions on what i should try whenever i find it
krakout said:
Maybe I'm wrong, but although the whole flashing process can fail if communication with device breaks, it's hard to actually fail while flashing a partition? Because the system first pushes the whole file and only then does it begin actual flashing. So whatever partition you are pushing at any given moment, if it fails to push it in its entirety, then it won't flash it... Unless data is corrupted during transfer?
Click to expand...
Click to collapse
Google uses sparse images... I think they're maxed at like 262MB? So like you'll see the flashing process go Product 1, Product 2, etc... It flashes after the full sparse image is transferred but if you don't have the full image when something goes wrong, you can still brick.
EtherealRemnant said:
Google uses sparse images... I think they're maxed at like 262MB? So like you'll see the flashing process go Product 1, Product 2, etc... It flashes after the full sparse image is transferred but if you don't have the full image when something goes wrong, you can still brick.
Click to expand...
Click to collapse
Ah I see, makes sense.
xflowy said:
uff ok. is there any way to avoid this? i mean, even my desktop pc (which is stable) could suffer from a power shortage in the house for example.
Click to expand...
Click to collapse
Oh brother, how often does that actually even happen?
HipKat said:
Oh brother, how often does that actually even happen?
Click to expand...
Click to collapse
Sure, not really often. But when it does..
Arealhooman said:
If you device is flashing something like the bootloader, and connection breaks for any reason at all, or the problem closes, etc, it will be a hard brick. You may get lucky, and it may be something unessential.
Click to expand...
Click to collapse
This is incorrect. The image is sent to the device memory (RAM) prior to actually being written. It won't write it to flash storage until AFTER the entire image is received.
zacattackkc said:
trying to go from latest feb build to jan before flashing....
Click to expand...
Click to collapse
It sounds like you may have tripped some anti-downgrade code.
EDIT: I can confirm that the bootloader version was changed in the FEB image as compared to the JAN image.
96carboard said:
This is incorrect. The image is sent to the device memory (RAM) prior to actually being written. It won't write it to flash storage until AFTER the entire image is received.
Click to expand...
Click to collapse
Well, I use Samsung, so I am assuming fastboot is similar…