So for starters. I was on the latest Android 11 rooted with magisk and LSposed along with GB.
I decided to sideload the Android 12 DP. So i floashed the stock boot image to both slots and then sideloaded 12DP. Everything went fine and i was testing A12. Tried to root A12 with magisk by the standard patch boot.img and fastboot flash to both slots. The phone hung on the bootscreen for like 10 minutes so i figured it best to flash back to A11. Back to BL mode and flashed theboot.img to both slots and then flash-all A11. Hit start when finished and it just flashed the white google screen for a few seconds then back to bootloader. Strange. Tried again, while changing active slots to ensure its flashing the system to both slots. Will not boot. Straight back to bootloader.
I can flash individual partions and i have no errors other than when wiping data it says it cant. Cant remeber exactly the error. But this is where it gets even more weird. I can flash android 9 and have no issues, I can take OTA updates with not issue. I can and am rooted and my phone is back to A11 via OTA. It will not boot if i flash or sideload any other version of Android other than A9. I believe this has something to do with encrytion. My phone was encrypted when i started this whole proccess and i believe thats why i get the error when trying to wipe data. In A9 recovery, when i factory data reset. it wipes with no errors. If i try to factory data reset in A10 or A11 Recovery i get the error E: can't send spi message: Try again .
So in closing, my phone is working and running fine but i can not flash-all any Android version other than A9 and have the phone boot.
So if anyone knows the proper steps to get this phone right, I would greatly appreciate it.
If not, i guess i will only be taking OTA's until i can figure it out.
Happy flashing!
Quick edit
Yes i pass safetynet and all banking apps work.
so is doing anything at all really necessary. I will leave that for the community to decide.
My opinion is, There is something wrong that needs fixing here. But its not crucial.
On A10-11 did you try "fastboot erase userdata" ?
wangdaning said:
On A10-11 did you try "fastboot erase userdata" ?
Click to expand...
Click to collapse
I did and it gives an error. Wish I wrote down the error like I did the other one. It's the same error at the end of flash-all when I don't remove -w
Try fastboot format userdata.
Just to add.... I can flash PixelDust (custom rom) and it boots and works great but can not flash-all or sideload android 10 or 11. Can only flash Android 9 and take OTA's up to Android 11.
Damn, should have caught this before. Your Platform Tools are out of date. Update adb and fastboot to latest.
wangdaning said:
Damn, should have caught this before. Your Platform Tools are out of date. Update adb and fastboot to latest.
Click to expand...
Click to collapse
I wish it were that simple. Unfortunately i actually updated it and also added the Android S Preview SDK and restarted my PC before even attempting this whole thing. And to make sure, just now checked for updates and its up to date.
What do you get with "fastboot --version" ?
I have see it where people have multiple versions on their computer.
wangdaning said:
What do you get with "fastboot --version" ?
I have see it where people have multiple versions on their computer.
Click to expand...
Click to collapse
You may be onto something here.....thoughtts?
And i think i have fixed that part on my PC. This is now what i get. I had that all-in-one tool installed so it made my system wide fastboot/adb look at its program folder instead of my default installation folder. Thats uninstalled and all folders and registry keys associated with it and my system is looking at my android sdk installation folder as it should.
This may very well have been the issue. I haven't tried to flash anything yet as i'm a bit gun shy after this fiasco lol
Maybe i will try flash-all with -w removed to see what happens.
Fastboot erase data?
jjgvv said:
Fastboot erase data?
Click to expand...
Click to collapse
That may likely work now as one of my issues was my fastboot was the wrong version because of the all-in-one tool i had installed. Haven't tried it yet and may not need to loose data if the flash-all command will work past android 9 which it should now thats its using the proper fastboot/adb version.
wangdaning said:
Try fastboot format userdata.
Click to expand...
Click to collapse
jjgvv said:
Fastboot erase data?
Click to expand...
Click to collapse
that finishes wothout any error....good start
is this how -w should work......sidenote, i can now flash-all android 11 and boot to system
Thank you @wangdaning for suggesting checking my fastboot version! That lead me to see i had 2 version and was defaulting to the wrong version. Removing that version and fixing my system path in windows variables fixed my issues. It was fastboot version the whole time. Again thank you @wangdaning!!
Edit to thank all who replied to this thread. I used everyones ideas
Glad you got it working.
Related
" SOLVED - System was using 19.99 gb's required user data format. " Cant flash any of 3 factory images ? Anyone have a clue why ? I have a verizon pixel Xl with unlocked bootloader rooted with the newest supersu and every time I try to flash any of the three factory images for pixel XL my adb tools gives me the error " error: failed to load 'image-marlin-nde63l.zip': Not enough space " I flashed images just fine a couple weeks ago on both my Nexus 6 and my Nexus 9 but for some reason I keep getting this problem.
I have tried using flash-all.bat and that is what I get. I never have had any luck using flash-all.bat in the past with my Nexus 6 & 9 so I would use the manual method which I"am listing below but there are a lot more things to flash on these pixel XL. So hopefully someone can list how to manually flash an image on the pixel XL because its totally different. Hopefully someone can tell me what is the problem ?
Run fastboot commands
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Add next step for Nexus 9
fastboot flash vendor vendor.img
I have also tried the following steps and on the last step flashing the image I still get " error: failed to load 'image-marlin-nde63l.zip': Not enough space "
Steps I tried are:
fastboot flash bootloader bootloader-marlin-8996-012001-1608281716.img
fastboot reboot-bootloader
fastboot flash radio radio-marlin-8996-012511-1609150631.img
fastboot reboot-bootloader
fastboot -w update image-marlin-nde63l.zip
I just checked my setting and I have 19.99 gb's used by the system. That seems way too much. Could that be the problem ?
M9guy said:
I just checked my setting and I have 19.99 gb's used by the system. That seems way too much. Could that be the problem ?
Click to expand...
Click to collapse
Yeah sounds like it to me might have to wipe userdata that will wipe your phone completely
When I flash the images I use the flash-all.sh.
This works for me "sudo sh flash-all.sh"
I had same issue. I have sideloaded the update zip temporarily. I still wonder what's wrong in flashing zip file. I dont think its the issue with size because i had almost 90GB space left.
M9guy said:
I just checked my setting and I have 19.99 gb's used by the system. That seems way too much. Could that be the problem ?
Click to expand...
Click to collapse
When I flash the images I use the flash-all.sh.
This works for me "sudo sh flash-all.sh"
M9guy said:
I have a verizon pixel Xl with unlocked bootloader rooted with the newest supersu and every time I try to flash any of the three factory images for pixel XL my adb tools gives me the error " error: failed to load 'image-marlin-nde63l.zip': Not enough space "
Click to expand...
Click to collapse
You don't use ADB to flash factory image. You use fastboot, from your bootloader...
cam30era said:
You don't use ADB to flash factory image. You use fastboot, from your bootloader...
Click to expand...
Click to collapse
I was in bootloader fastboot mode and i saw same issue.
rootSr. said:
I was in bootloader fastboot mode and i saw same issue.
Click to expand...
Click to collapse
Just to confirm, you unzipped the factory image and did: fastboot flash system system.img?
If so, you might need to update your Android SDK...
cam30era said:
You don't use ADB to flash factory image. You use fastboot, from your bootloader...
Click to expand...
Click to collapse
I put phone in bootloader mode and held down shift button and righted clicked on my folder with my adb tool that I extracted all files to.
http://androiding.how/flash-firmware-factory-image-google-pixel/
jaythenut said:
Yeah sounds like it to me might have to wipe userdata that will wipe your phone completely
Click to expand...
Click to collapse
The method at the link below I had tried it previously and it did format my data but now each time I boot the phone I get " There"s an internal problem with your device. Contact your manufacturer for details. "
http://androiding.how/flash-firmware-factory-image-google-pixel/
zaksimmermon said:
When I flash the images I use the flash-all.sh.
This works for me "sudo sh flash-all.sh"
Click to expand...
Click to collapse
I have windows 10, which for windows your supposed to use flash-all.bat which that gave me the same error on the last step flashing the system image.
rootSr. said:
I had same issue. I have sideloaded the update zip temporarily. I still wonder what's wrong in flashing zip file. I dont think its the issue with size because i had almost 90GB space left.
Click to expand...
Click to collapse
I have the update downloaded to the phone it just wont install it think because I was rooted, even after formatting user data starting over it still would not install the update with no supersu installed.
Do you remember where the update was downloaded to on your phone what folder, or did you download the update somewhere else to your computer ?
cam30era said:
Just to confirm, you unzipped the factory image and did: fastboot flash system system.img?
If so, you might need to update your Android SDK...
Click to expand...
Click to collapse
It makes sense, I will update and verify. Thanks for quick reply Cam
rootSr. said:
It makes sense, I will update and verify. Thanks for quick reply Cam
Click to expand...
Click to collapse
I just tried updating my Minimal ADB and Fastboot [10-22-16] and still same error. I thought I had already updated but I tried again anyway and still no go, and that was updated on 10-22-16
http://forum.xda-developers.com/showthread.php?t=2317790
M9guy said:
I have windows 10, which for windows your supposed to use flash-all.bat which that gave me the same error on the last step flashing the system image.
Click to expand...
Click to collapse
What version is your pixel running now? I'm on NDE63P.
zaksimmermon said:
What version is your pixel running now? I'm on NDE63P.
Click to expand...
Click to collapse
I"am on NDE63L
You need to try updating the SDK through the SDK manager. It'll have a box to check of to update SDK 25.
Sent from my Pixel XL using Tapatalk
rootSr. said:
It makes sense, I will update and verify. Thanks for quick reply Cam
Click to expand...
Click to collapse
It did work without any issues. I have cleared old SDK and downloaded new. Worked flawless. Thanks. :good:
Last night i bricked my phone and accidently deleted system partitions i think from slot A and slot B when i was trying to install twrp. I always try to figure out how to fix it from reading helpful guides and without asking questions. I flashed full image a couple of times because i was getting bootloops everytime. In the last try, i flashed full image then gave me a bootloop again. So what i did, i adb sideload ota and it booted fine. Now im rooted and it seems i installed twrp correctly, i currently have nde63v build. At the moment i have supposedly used 22.71gb of 29.70gb.
So can someone let me know what i did wrong or point me out how to get those gbs back please.
ls2power said:
Last night i bricked my phone and accidently deleted system partitions i think from slot A and slot B when i was trying to install twrp. I always try to figure out how to fix it from reading helpful guides and without asking questions. I flashed full image a couple of times because i was getting bootloops everytime. In the last try, i flashed full image then gave me a bootloop again. So what i did, i adb sideload ota and it booted fine. Now im rooted and it seems i installed twrp correctly, i currently have nde63v build. At the moment i have supposedly used 22.71gb of 29.70gb.
So can someone let me know what i did wrong or point me out how to get those gbs back please.
Click to expand...
Click to collapse
I just did a factory reset and it fixed it. I also was stock without twrp though.
seshaz said:
I just did a factory reset and it fixed it. I also was stock without twrp though.
Click to expand...
Click to collapse
I tried factory reset already but still shows system using 19.9gbs.
Have you tried doing a complete full flash of nde63v without installing TWRP or root to see if it goes back to normal?
cambunch said:
Have you tried doing a complete full flash of nde63v without installing TWRP or root to see if it goes back to normal?
Click to expand...
Click to collapse
yes i did a few times, it would just bootloop. Until i sideloaded ota nde63v on top of full system img then it booted fine
ls2power said:
I tried factory reset already but still shows system using 19.9gbs.
Click to expand...
Click to collapse
Mine shows system using 19.9 gigs also. I posted this on another thread as I thought it seemed high but no one said weather it was high or was not so I assumed it was normal to use 19.9 gigs of space on my verizon pixel xl. I"am rooted on the x software but I couldnt get twrp working and I figured what good was TWRP if there was no supersu that was working with it and I decided to wait for TWRP to get out of beta to try again.
ls2power said:
yes i did a few times, it would just bootloop. Until i sideloaded ota nde63v on top of full system img then it booted fine
Click to expand...
Click to collapse
If you are getting a bootloop after flashing a factory image, I would assume it isn't flashing correctly. Can you post the output of what happens when you run the flashall.bat?
cambunch said:
If you are getting a bootloop after factory a factory image, I would assume it isn't flashing correctly. Can you post the output of what happens when you run the flashall.bat?
Click to expand...
Click to collapse
im able to flash every single img, but when i try to flash flashall.bat it doesnt seem to work. I will give it a try once i get home from work. The only thing bugging me is that the system shows using 19.9gb of space.
Mine is only using 6.79GB. Something is definitely off with yours.
Sent from my Pixel XL using XDA-Developers mobile app
Neomage84 said:
Mine is only using 6.79GB. Something is definitely off with yours.
Click to expand...
Click to collapse
yes there is. When you reboot your phone, which slot does it have? And do you have twrp installed and root?
M9guy said:
Mine shows system using 19.9 gigs also. I posted this on another thread as I thought it seemed high but no one said weather it was high or was not so I assumed it was normal to use 19.9 gigs of space on my verizon pixel xl. I"am rooted on the x software but I couldnt get twrp working and I figured what good was TWRP if there was no supersu that was working with it and I decided to wait for TWRP to get out of beta to try again.
Click to expand...
Click to collapse
I fixed it, i flashed full system image while i was on slot A. Now system is using 5.39gb, im on V build.
i have the same problem with a 128GB version not sure whats up but to fix it i just flashed over and over and one of them just worked would be nice to know the cause so i dont have to flash many times to get it to show full space again.
How do you select slot a while stock? I can select it in twrp but need to know how to get stock images to flash to a
theycallmerayj said:
How do you select slot a while stock? I can select it in twrp but need to know how to get stock images to flash to a
Click to expand...
Click to collapse
I figured out how to fix it by selecting slot a through twrp, booting into fastboot and flashing stock images. However, I am curious how it even ended up on slot b when I went from stock to unlocked and simply flashed the factory images. I never intended to switched from a to b.
theycallmerayj said:
How do you select slot a while stock? I can select it in twrp but need to know how to get stock images to flash to a
Click to expand...
Click to collapse
theycallmerayj said:
I figured out how to fix it by selecting slot a through twrp, booting into fastboot and flashing stock images. However, I am curious how it even ended up on slot b when I went from stock to unlocked and simply flashed the factory images. I never intended to switched from a to b.
Click to expand...
Click to collapse
whenever you flash a factory img or an OTA, or any firmware, the slots will switch unless told not to, i believe this is to keep them in sync aka the seamless updates. here is some info on that - http://www.androidpolice.com/2016/1...-partition-changes-and-new-fastboot-commands/
Quick Tip - while in cmdlne for ADB and Fastboot, and fully updated, just type
Code:
adb
to get all the ADB commands available, and likewise for fastboot, just type
Code:
fastboot
And to switch active slots type
Code:
fastboot set_active -a
or
Code:
fastboot set_active -b
. Then to activate slot
Code:
fastboot reboot bootloader
I believe with TWRP installed you have to switch slots in TWRP.
Click to expand...
Click to collapse
Moving on, I found this to be pretty helpful, it's not the exact answer you are looking for, but i think it will come in handy.
All dual-booting credit in this thread goes to hucqym, this wasn't my idea, im just a messenger.
hucqym said:
so I successfully have the dual boot running on my pixel (verizon edition) with the same configuration you are trying (one is NDE63X image rooted and one is NDE63X image stock/unrooted). Here were my steps:
-> dePixel8 to unlock bootloader (because verizon edition pixel)
-> download NDE63X image from google and modified flash_all.sh to flash stock images to both slots manually
using the --slot _a/_b and --skip-secondary flags. Modified scripts below. At this point I confirmed that I could boot to both slots. I also verified bootloader lock/unlock again to make sure it was stock image on both slots
-> TWRP alpha2 to get recovery on both slots
-> with slot _b selected as active in TWRP, i installed the SuperSU v2.78 SR4 zip
-> with slot _a as active in TWRP, installed ElementalX-P-1.00 zip for the kernel patch to pass SafetyNet
voila, I now have non-rooted on slot _a and rooted on slot _b
Note that TWRP is not really a requirement for doing this. I had the same dual boot configuration working with SuperSU v2.78 SR3 rooting one slot directly. The only reason I needed TWRP is so that I can switch slots easily on the device and don't need a cable and a laptop just to switch the bootloader flag
Although, I got this to work it still falls short of what I really wanted to do. For my use-case I would really want an isolated userdata for the two slots so I can use the rooted slot as a complete sandbox. and then perhaps have a shared folder mechanism between the two. ...so if somebody has an idea on this, I'm all ears.
[UPDATE]: Note that the unrooted slot is still limited in the sense that safetynet checks fail and so AndroidPay etc.. that use that API will still not work. This, however, has little to do with the dual boot setup and more because SafetyNet now fails on just unlocked bootloader and we do need it unlocked. On Conchors' suggestion, I installed ElementalX kernel on slotA from TWRP and now my 'otherwise-stock' non-rooted image on slotA passes SafetyNet while slotB is successfully rooted
flash_all_slot-a.sh
Code:
fastboot flash --slot _a bootloader bootloader-sailfish-8996-012001-1608281716.img
fastboot reboot-bootloader
sleep 5
fastboot flash --slot _a radio radio-sailfish-8996-012511-1609191801.img
fastboot reboot-bootloader
sleep 5
#fastboot -w update image-sailfish-nde63x.zip
fastboot update --slot _a --skip-secondary image-sailfish-nde63x.zip
flash_all_slot-b.sh
Code:
fastboot flash --slot _b bootloader bootloader-sailfish-8996-012001-1608281716.img
fastboot reboot-bootloader
sleep 5
fastboot flash --slot _b radio radio-sailfish-8996-012511-1609191801.img
fastboot reboot-bootloader
sleep 5
#fastboot -w update image-sailfish-nde63x.zip
fastboot update --slot _b --skip-secondary image-sailfish-nde63x.zip
Click to expand...
Click to collapse
I switched it up a bit, and to be perfectly honest, the script is easier, this is just an alternate way of doing it
I did this for both slot_a and slot_b (not sure if it is needed for the flrst one, but that is what i did), both ways are correct, this way is much longer, but it gives some control, plus it's a nice learning process as it is pretty easy going.
If you are going to erase, erase first before you start anything, because you know...science.
Code:
fastboot erase boot
fastboot erase cache
fastboot erase system
fastboot erase vendor
the cache partition, i dont remember if this worked or not, I'm too tired to verify
Code:
fastboot flash --slot _b --skip-secondary bootloader "name-of-bootloader.img"
fastboot reboot-bootloader
fastboot flash --slot _b --skip-secondary radio "name-of-radio.img"
fastboot reboot-bootloader
fastboot flash --slot _b --skip-secondary system system.img
fastboot flash --slot _b --skip-secondary boot boot.img
fastboot flash --slot _b --skip-secondary vendor vendor.img
If you want to wipe everything, use the following commands next:
Code:
fastboot erase userdata
fastboot flash userdata userdata.img
fastboot reboot
system.img and userdata.img take time to flash— the command prompt appears to stop. Let it do it's thing, when it's done the cursor will begin blinking again.
All dual-booting credit goes to hucqym; again, not my idea.
Slightly Off Topic -
Has anyone tried this on a specific slot, does it make any difference?) I haven't actually even thought of this till now
something like:
Code:
fastboot erase --slot _(a/b) --skip-secondary userdata
fastboot flash --slot _(a/b) --skip-secondary userdata userdata.img[/B]
theycallmerayj said:
I figured out how to fix it by selecting slot a through twrp, booting into fastboot and flashing stock images. However, I am curious how it even ended up on slot b when I went from stock to unlocked and simply flashed the factory images. I never intended to switched from a to b.
Click to expand...
Click to collapse
ls2power said:
Last night i bricked my phone and accidently deleted system partitions i think from slot A and slot B when i was trying to install twrp. I always try to figure out how to fix it from reading helpful guides and without asking questions. I flashed full image a couple of times because i was getting bootloops everytime. In the last try, i flashed full image then gave me a bootloop again. So what i did, i adb sideload ota and it booted fine. Now im rooted and it seems i installed twrp correctly, i currently have nde63v build. At the moment i have supposedly used 22.71gb of 29.70gb.
So can someone let me know what i did wrong or point me out how to get those gbs back please.
Click to expand...
Click to collapse
I was noticing quite a bit of space missing as well. what i did was boot into the slot I wanted as secondary (do this in TWRP), and i wiped just the system (which includes cache) and reflashed the system.img directly pulled from factory.zip. I noticed twice as much space had been gained then what was actually said to be there. I was a little surprised...it was over 5 gb I had gained while the system only said 2.5ish gb. (perhaps there was a second other_system.img wrapped up in it, I don't know. Then i went back to the primary slot and booted back up.
It's possible I got off course, I'm tired.
II am attempting to get back to full stock on my Pixel XL and I am okay with wiping it. I am coming from Rooted, TWRP, custom Kernel, and WETA Rom. I was having some issues with it acting up, and I want now to return to the full factory image. In order to do so, I attempted to run the flash-all.bat script from the Google page, and it seems as if all is going well, then, when it tries to flash the system.img, it fails and throws an error which says "FAILED (Remote: Partition [bootb] does not exist)" I have also tried flashing the factory image in pieces and get the same issue, and also when I try to do it through TWRP. I just want to go back to the way the phone came so I can start fresh. Any input on how to do so would be greatly appreciated. Note: the same error goes when I try to flash-all on slot a.
What version of adb are you running?
Make sure you have 1.0.36. Ref post http://forum.xda-developers.com/showthread.php?t=2932160
Try manually flashing to partition _a or _b. Such as fastboot flash system_a system.img.
I ran into the same issue and was able to flash everything to slot a manually by adding _a to the commands
harmohn said:
What version of adb are you running?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
The latest minimal adb fastboot
gettingerr said:
The latest minimal adb fastboot
Click to expand...
Click to collapse
Okay, just to be sure can you type "adb version" and then "fastboot --version" (without quotes) in a command line console. What were the outputs?
Android Debug Bridge version 1.0.35
Revision fc2a139a55f5-android
fastboot version fc2a139a55f5-android
Zavon said:
Try manually flashing to partition _a or _b. Such as fastboot flash system_a system.img.
I ran into the same issue and was able to flash everything to slot a manually by adding _a to the commands
Click to expand...
Click to collapse
I think that worked! Do I need to flash anything besides boot, system, and vendor? There are a lot of .img files in this folder from google. Do I do them all or just these three? Also, do I need to flash the radio?
Odd that Google wouldn't update their flash-all script to deal with the two slot setup..
gettingerr said:
Android Debug Bridge version 1.0.35
Revision fc2a139a55f5-android
fastboot version fc2a139a55f5-android
Click to expand...
Click to collapse
Right, you need to be on 1.0.36 for fastboot to "see" the partitions correctly. Refer to my initial comment for a download link.
gettingerr said:
I think that worked! Do I need to flash anything besides boot, system, and vendor? There are a lot of .img files in this folder from google. Do I do them all or just these three? Also, do I need to flash the radio?
Odd that Google wouldn't update their flash-all script to deal with the two slot setup..
Click to expand...
Click to collapse
I didn't flash any of the other stuff. Only boot, system, and vendor.
Not sure what causes the mismatch in names of the partitions.
Download the free Unified Toolkit. It works across a large number of Android devices. It takes the hassle out of a lot of ****, including this. It will flash the entire factory package by itself. I had to do this to fix my phone from a recovery bootloop after flash-all.bat failed me too.
Hey all,
I was on android P and wanted to go back to Oreo so i booted twrp and wiped system/data and then afterwards, fastboot is giving me errors and i cant even boot twrp to my phone it just says remote: unknown command. Heres a pic https://imgur.com/a/odn4w
edit: i was able to get the feb image to flash but now im stuck at the loading G screen. If i open fastboot and try fastboot boot twrp i get unknown command. See here https://imgur.com/a/Ropme
Hold the power button while at no command. Then hit volume up and release both. That will give you the menu.
Get rid of minimal adb and fastboot. I don't understand why people are using something made before even the original pixels were released. It doesn't understand dual partitions or handle the larger sizes of our partitions. Get adb and fastboot from Google.
joedajoester said:
Hey all,
I was on android P and wanted to go back to Oreo so i booted twrp and wiped system/data and then afterwards, fastboot is giving me errors and i cant even boot twrp to my phone it just says remote: unknown command. Heres a pic https://imgur.com/a/odn4w
edit: i was able to get the feb image to flash but now im stuck at the loading G screen. If i open fastboot and try fastboot boot twrp i get unknown command. See here https://imgur.com/a/Ropme
Click to expand...
Click to collapse
Try a different USB port.
Ensure you have USB drivers installed first.
TonikJDK said:
Hold the power button while at no command. Then hit volume up and release both. That will give you the menu.
Get rid of minimal adb and fastboot. I don't understand why people are using something made before even the original pixels were released. It doesn't understand dual partitions or handle the larger sizes of our partitions. Get adb and fastboot from Google.
Click to expand...
Click to collapse
Problem is for sure the Minimal setup.
Only setup to use (ever) is here: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Updated regularly.
michaelbsheldon said:
Problem is for sure the Minimal setup.
Only setup to use (ever) is here: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
Updated regularly.
Click to expand...
Click to collapse
I am using that platform tools and i still get the remote:unknown command error. Any idea what i should do? I already factory reset and relocked and unlocked the bootloader and critical. I cant even boot twrp to flash magisk. it broke when i was on android p i booted twrp and wiped system data cache from slot a and b. Reboot and then fastboot was wonky like it still is now.
joedajoester said:
I am using that platform tools and i still get the remote:unknown command error. Any idea what i should do? I already factory reset and relocked and unlocked the bootloader and critical. I cant even boot twrp to flash magisk. it broke when i was on android p i booted twrp and wiped system data cache from slot a and b. Reboot and then fastboot was wonky like it still is now.
Click to expand...
Click to collapse
Just curious, but when your in the OS, and open a command prompt on the platform-tools folder and type...adb devices...do you see your device ID?? Same thing for when your in bootloader mode and type...fastboot devices...??? ?
did you fix this? im in the same boat, on p beta tried to flash factory image back to 8.1 and getting "target didn't report max download size".
Im using platform tools
OP, have you managed to solve the issue?
I ran into a lot of trouble updating June OTA and had the same error. Tried to change ports, USB cables, etc. and just when I was about to give up, I decided to restart my PC and tried again, this time things worked fine without any issue whatsoever.
This is likely not your issue, but if your computer has less than 4 gigs of RAM, or you are trying to flash a file larger than your available RAM you will get this message.
This (i.e. rebooting PC) worked
DanteXXL said:
OP, have you managed to solve the issue?
I ran into a lot of trouble updating June OTA and had the same error. Tried to change ports, USB cables, etc. and just when I was about to give up, I decided to restart my PC and tried again, this time things worked fine without any issue whatsoever.
Click to expand...
Click to collapse
This indeed worked when I rebooted my pc.
Hello I have an urgent request. My phone isn't working currently because I tried to switch kernels but ended up flashing the wrong boot.img and was stuck on boot. With g logo.
Now whenever I try to boot system it goes to TWRP. due to bank of America app not allowing developer options, I had it turned off but I know USB debugging was on. When I used Tool All in one, it did recognize my phone but typing adb devices on command prompt doesn't show anything. Please help!!!
Flash magisk
@trizzv: There should be two ways for you to resolve your issue. The first and arguably the least painful is to change your slot and reboot, which you can do in the reboot menu of TWRP. The second is to download the latest full OTA image from Google and flash it through TWRP. And yes, flashing the OTA through TWRP will work, although you will end up losing TWRP and will need to reinstall it after fully booting the system.
@akellar: His boot.img is the wrong one. Flashing Magisk won't help here, based upon what trizzv has said.
Flash flactory image if all else fails. Don't panic. I got into a similar situation.
Strephon Alkhalikoi said:
@trizzv: There should be two ways for you to resolve your issue. The first and arguably the least painful is to change your slot and reboot, which you can do in the reboot menu of TWRP. The second is to download the latest full OTA image from Google and flash it through TWRP. And yes, flashing the OTA through TWRP will work, although you will end up losing TWRP and will need to reinstall it after fully booting the system.
@akellar: His boot.img is the wrong one. Flashing Magisk won't help here, based upon what trizzv has said.
Click to expand...
Click to collapse
I can't drag any files to my phone and right now it doesn't have anything-- magisk, TWRP file, or boot.img
azpatterson3 said:
Flash flactory image if all else fails. Don't panic. I got into a similar situation.
Click to expand...
Click to collapse
What would be the steps? Fastboot? Tried that but I couldn't get it to work
trizzv said:
What would be the steps? Fastboot? Tried that but I couldn't get it to work
Click to expand...
Click to collapse
https://developers.google.com/android/images
If for some reason it won't write and ends with an error. Open the flash script and remove the "-w" on the last line before it says "update"
I wonder, since you can boot into TWRP, if sideloading an OTA image won't fix your boot partition -- as I understand it, OTA's would overwrite and essentially reinstall/reinitialize the boot partition... If others concur or you decide you wish to try this route, say so and I could lay out steps to take...
But, if anything, reboot into Bootloader (can be done from TWRP), open up a command prompt (elevated, or powershell if you're more familiar with), have it directed at your platform-tools folder (or whatever folder you have adb.exe and fastboot.exe), and input the commands
Code:
fastboot --version
and
Code:
adb devices
*to load emulator and such...
if, after all of this, those two commands return info without an error, that should establish that you would be good to go in re-flashing the boot partition (as well as the system, vendor, modem, etc.) without losing any data and, at the very least, confirm that you have fastboot working...
do these and get back to us/me and can take steps from there towards repairing your pixel...
use Deuces Bootloop-Recovery & Flashing Script and just follow instruction :good:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
simplepinoi177 said:
I wonder, since you can boot into TWRP, if sideloading an OTA image won't fix your boot partition -- as I understand it, OTA's would overwrite and essentially reinstall/reinitialize the boot partition... If others concur or you decide you wish to try this route, say so and I could lay out steps to take...
But, if anything, reboot into Bootloader (can be done from TWRP), open up a command prompt (elevated, or powershell if you're more familiar with), have it directed at your platform-tools folder (or whatever folder you have adb.exe and fastboot.exe), and input the commands and *to load emulator and such...
if, after all of this, those two commands return info without an error, that should establish that you would be good to go in re-flashing the boot partition (as well as the system, vendor, modem, etc.) without losing any data and, at the very least, confirm that you have fastboot working...
do these and get back to us/me and can take steps from there towards repairing your pixel...
Click to expand...
Click to collapse
Please let me know what the steps are. Will try it today.
trizzv said:
Please let me know what the steps are. Will try it today.
Click to expand...
Click to collapse
...the suggestion @goti(0) actually gave is rather simpler, but do require pretty much the same steps (downloading factory image, extracting, placing the files in correct place, etc.)...
What did the commands return when you entered them? I am not reluctant to give you the steps, rather I gave you those commands to narrow down where your issues might be; if your fastboot and emulator aren't set up properly, giving you further steps might carry you down a less-stable and "skewed" path because things would be "based" at it's source incorrectly...
Let us/me know what those commands return and I'll get those steps to ya right away!
goti(0) said:
use Deuces Bootloop-Recovery & Flashing Script and just follow instruction :good:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
THIS WORKED!!!!! THANK YOU so much for the suggestion.
trizzv said:
THIS WORKED!!!!! THANK YOU so much for the suggestion.
Click to expand...
Click to collapse
it was a great suggestion...I'm glad it worked out for you! :victory:
Also you can just reflash corrupt boot.img the original for what image you have. You can load on flash drive through your type c .
There's a lot of ways to fix your stuff