how to install GSI on Pixel 3a - Google Pixel 3a Questions & Answers

i couldn't install phh-treble 10 AOSP on my Pixel 3a runing android 10 through the bootloader or fastbootd ,
on the bootloader it says it should be done through fastbootd and on fastbootd it says it can't resize the partition ,
is there a third way i don't know about ??

Did you ever get an answer to this? I was running into the same problem.

I never tried this myself but you just reminded me of this from Googles page:
On Android 10 devices that have smaller system partitions, the following error message might appear when flashing the GSI:
Resizing 'system_a' FAILED (remote: 'Not enough space to resize partition')
fastboot: error: Command failed
Use the following command to delete the product partition and free up space for the system partition. This provides extra space to flash the GSI:
$ fastboot delete-logical-partition product_a
The postfix _a should match the slot id of the system partition, such as system_a in this example.
I never tried it but I am probably going to now. I didn't know you had to flash in fastbootd, i was flashing in bootloader and the rom had no data connection so now I'm excited to try in in fastbootd

I was running into problems with getting most GSI to boot or talking about it being corrupt. I got frustrated and went back to Bliss.

Related

Softbrick - possible solution for you

Hey,
since apparently a lot have a softbrick for whatever reason i thought i post my findings here as well since it worked for both my TF300t and A700
Originating Thread: http://forum.xda-developers.com/showpost.php?p=44244313
and here my steps:
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
My solution
I have the same on my TF300t and A700 - but it seems i just managed to get my TF300t back
i tried all fastboot (reflashing recovery, boot, system etc) no dice - especially since writing system was done after 3 secs all the time.
Here how i restored my TF300T JB
download your appropriate lates firmware from Asus (WW, US etc.) and extract the zip twice so you have your blob file
install your device drivers if needed (i used Google SDK ones) (and as a Tip Win8 sucks for Fastboot stuff so try to get Win7 Vista XP for this)
Reset your device with a paperclip/needle (about 2 cm down of your sdcard slot) and hold vol-down to enter fastboot
(the folowing i did at least 10 times already but didn't erase misc)
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
fastboot -i 0x0B05 reboot
* it also took a lot longer, as it should:
C:\>fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
erasing 'system'...
OKAY [ 1.695s]
sending 'system' (800935 KB)...
OKAY [133.121s]
writing 'system'...
OKAY [153.973s]
finished. total time: 288.789s
im now setting my tab up to get back to CM (which initially caused this sh1theap due to autoupdate error, same as my A700 got bricked )
hope i could help you out!
Click to expand...
Click to collapse
cheers
-Buster
Buster99 said:
Hey,
since apparently a lot have a softbrick for whatever reason i thought i post my findings here as well since it worked for both my TF300t and A700
Originating Thread: http://forum.xda-developers.com/showpost.php?p=44244313
and here my steps:
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
cheers
-Buster
Click to expand...
Click to collapse
At this part:
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
Click to expand...
Click to collapse
you put the instructions fo the TF300t, but you said this method also worked for the Acer a700. I know to change the code after -i to 0x0502, for the a700 device ID, but I'm not sure what to use for the system. I've been unable to find a system.img that works, as well. What should I do after erasing the partitions?
Also, usually when I try to flash anything, when fastboot begins the write process (or just before,) the tablet screen starts to slowly jitter (the Acer logo and Bootloader text in the top-left go down about 10 pixels for about a half-second then go back to their original positions.) I've tried multiple guides (can't fastboot boot recovery.img, Magic Value Mismatch error,) and I can't get into adb. Any ideas? It looks like your fix might work somehow.
OMIGHTY1 said:
At this part:
you put the instructions fo the TF300t, but you said this method also worked for the Acer a700. I know to change the code after -i to 0x0502, for the a700 device ID, but I'm not sure what to use for the system. I've been unable to find a system.img that works, as well. What should I do after erasing the partitions?
Also, usually when I try to flash anything, when fastboot begins the write process (or just before,) the tablet screen starts to slowly jitter (the Acer logo and Bootloader text in the top-left go down about 10 pixels for about a half-second then go back to their original positions.) I've tried multiple guides (can't fastboot boot recovery.img, Magic Value Mismatch error,) and I can't get into adb. Any ideas? It looks like your fix might work somehow.
Click to expand...
Click to collapse
When in doubt, disconeect all android devices and issue the command without the ID (usually fastboot/adb use the default id when only 1 device is connected.
"fastboot flash system c:\blob"
The erase worked on my TF300t/A700/Galaxy Nexus.
If you are having flashing probs make shure to switch cable and usb ports &/or try a linux to test.
gl
-Buster
Here's the input and output from that:
C:\android>fastboot flash system c:\blob
error: cannot load 'c:\blob': No error
Click to expand...
Click to collapse
Would I need the stock image in the blob folder, or should it be empty? Should I create it at all?
The screen problem is identical to the problem in this post:
http://forum.xda-developers.com/showthread.php?t=1976209
OMG - Thought My Prime was Dead In The Water...Thanks Buster!
Buster99 said:
Hey,
since apparently a lot have a softbrick for whatever reason i thought i post my findings here as well since it worked for both my TF300t and A700
Originating Thread: http://forum.xda-developers.com/showpost.php?p=44244313
and here my steps:
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
cheers
-Buster
Click to expand...
Click to collapse
Was getting the dreaded Option 2 - Unrecoverable Bootloader Error that was supposed to be the ultimate death sign. As a last resort, I tried the steps Buster provided and my Prime is up and running again!
When i turn on tablet, goes straight to recovery, even after have tried rebooting into system, i followed the button combinations to boot into RCK. The version installed of CWM was based in Recovery v6.0.2.3 occurs that after opening CWM immediately below error messages are displayed.
E:Can’t mount /cache/recovery/command
E:Can’t mount /cache/recovery/log
E:Can’t open /cache/recovery/log
E:Can’t mount /cache/recovery/last_log
E:Can’t open /cache/recovery/last_log
And now can’t grab any rom in SD card when I’m forced into recovery. I tried with two kind of SD, 1Gb Sandisk, 4Gb Kingston HC-(4). when I try to mount any partition like /data and /sdcard from “mounts and storage” obtain:
Error mounting /sdcard!, Error mounting /sdcard!, Error mounting /emmc!
Also i download android tools and installed adb universal drivers, from recovery mode, If I type "adb devices" shows a proper reorganization.
List of device attached
0123456789ABCDEF recovery
So every time when start up, even without hitting vol+power key, it goes into the recovery mode.when i type "adb reboot-bootloader",it goes power off.Nothing happen.Please help me.

Aosp e6653

I've managed to compile 5.1.1 aosp,
here is my problem, fastboot doesn't seem to recognize the command i'm typing in '-S 256M' as stated on the sony site.
If i try and flash them the normal way, for example "fastboot flash system system.img"
it doesn't flash like this, i have tried on linux and windows.
I've attached screenshots to show my problem.
Edit- I should of said first, I can flash boot, recovery and userdata the normal way, but system.img hangs. Fastboot won't let me use the command listed on the sony site when flashing any of the partitions.
My compiled system.img seems fine and I can view and extract the files so I don't think it's corrupted.
issue '-S 265M' after 'flash'..!!!
SO it should be 'fastboot flash -S 265M system system.img'
And you need to specify memory breakdown for the system image only, as it has a massive size, for the rest skip using '-S 265M'
P.S.: You certainly seem to be new at Android compilation.. I would advice you to try checking other forums first... checking out what works and what doesn't before experimenting! Just saying!
Cheers

Need help! Willing to pay!

XDA Friends,
WOULD YOU LIKE TO MAKE A LITTLE MONEY TODAY???
I am calling out to you in DIRE need. I have royally screwed up my brand new Razer phone (US) and as far as I can tell there is only one way back and that is to get one of you gracious souls to do me a very big favor. What I need is a SD Card that has been formatted to work on a Razor phone and that contains, an ENTIRE cheryl-global-3005.zip. One that has not only the boot.img but the system.img. The reason I need to get this from one of you is that while I was in TWRP I accidentally flashed boot.img in System instead of Boot. This overwrote System and so now I cannot boot into the main system, it essentially goes into a boot loop. So that means I cannot get adb to work which means I cannot move files onto the SD Card (that is specially formatted for that phone and cannot be used to move files physically). And I failed to get the entire image onto the sd card prior to this happening so I do not have a system.img file on the phone in any capacity with which to flash to at least get back to factory.
So I'm thinking that if I can get someone to send me a formatted sd card that contains the full cheryl zip then I can put that card in my phone flash the system.img file from it that should get me back.
If you are willing to help me out with this I WILL PAY YOU.
PLEASE send me a private message here so we can arrange this as soon as possible. I'm phoneless without this fix.
You forgot to mention where are you from, my friend.
My advice comes free of charge:
Hold the power key until the device shuts off. Then download the system images from https://developer.razerzone.com/razer-phone-dev-tools/factory-images/
Unzip this file and run the flash_all.bat file. (I assume you have fastboot set up already considering you've flashed TWRP). Once this completes you should see it booting up to a stock system.
You also have the option of manually flashing the system.img from this factory image using fastboot. No SD card required
Unfortunately, I cannot get to the download mode anymore in order to use fastboot. The only thing I can get to is TWRP. Any other attempt just sends it into bootloop.
@Kimbaroth I'm from North Carolina, United States.
Unfortunately, I cannot get to the download mode anymore in order to use fastboot. The only thing I can get to is TWRP. Any other attempt just sends it into bootloop.
@Kimbaroth I'm from North Carolina, United States.
OK scratch that I am able to get into download mode now. @Flippy125 thanks for the advice. I'll give that a try.
Ok, I am able to run fastboot devices and I can see that it recognizes the device. However, when i try to run "fastboot flash flash_all.bat" I get the following error message: unknown partition 'flash_all.bat'
error: cannot determine image filename for 'flash_all.bat'
I also tried "fastboot push cheryl-global-3005.zip" and that failed with error: unknown command push
I also tried "fastboot flash system.img" and that failed with error: unknown partition 'system.img'
error: cannot determine image filename for 'system.img'
Not sure what I'm doing wrong here. Any thoughts?
lostnsound said:
Ok, I am able to run fastboot devices and I can see that it recognizes the device. However, when i try to run "fastboot flash flash_all.bat" I get the following error message: unknown partition 'flash_all.bat'
error: cannot determine image filename for 'flash_all.bat'
I also tried "fastboot push cheryl-global-3005.zip" and that failed with error: unknown command push
I also tried "fastboot flash system.img" and that failed with error: unknown partition 'system.img'
error: cannot determine image filename for 'system.img'
Not sure what I'm doing wrong here. Any thoughts?
Click to expand...
Click to collapse
I think you meant "fastboot flash system_a system.img"
And you don't need to do "fastboot flash flash_all.bat", you just double click flash_all.bat that is inside the folder and it should work, as long as you have fastboot correctly installed
EDIT: I'm not sure, but I think "flash_all.bat" would erase all your files. Can anyone confirm this?
lostnsound said:
Ok, I am able to run fastboot devices and I can see that it recognizes the device. However, when i try to run "fastboot flash flash_all.bat" I get the following error message: unknown partition 'flash_all.bat'
error: cannot determine image filename for 'flash_all.bat'
I also tried "fastboot push cheryl-global-3005.zip" and that failed with error: unknown command push
I also tried "fastboot flash system.img" and that failed with error: unknown partition 'system.img'
error: cannot determine image filename for 'system.img'
Not sure what I'm doing wrong here. Any thoughts?
Click to expand...
Click to collapse
fastboot flash system system.img
@el4nimal and @waiflih
What is the difference between system and system_a?
Also, can you explain what slot A and slot B are? I have not run into those terms before when rooting other phones (previous was a Nexus 6p).
Thanks for the help guys! I really appreciate it. I'm at work right now so I will try your suggestions at lunch when I can run home for bit.
lostnsound said:
@el4nimal and @waiflih
What is the difference between system and system_a?
Also, can you explain what slot A and slot B are? I have not run into those terms before when rooting other phones (previous was a Nexus 6p).
Thanks for the help guys! I really appreciate it. I'm at work right now so I will try your suggestions at lunch when I can run home for bit.
Click to expand...
Click to collapse
I'm not sure, but I think those are partitions like C:/ and D:/ on a PC.
"System_a" would flash system.img only on Slot A, "System_b" on Slot B, I don't know what "system" does....i think it flashes both
IT'S ALIVE!
So "fastboot flash system system.img" is what worked. Appears that running that command updated system_a based on what I could see in the cmd prompt logging. But it worked as I am now able to boot into the operating system. THANK YOU GUYS SO MUCH!!! You saved me $700. What can I do to support you?
lostnsound said:
IT'S ALIVE!
So "fastboot flash system system.img" is what worked. Appears that running that command updated system_a based on what I could see in the cmd prompt logging. But it worked as I am now able to boot into the operating system. THANK YOU GUYS SO MUCH!!! You saved me $700. What can I do to support you?
Click to expand...
Click to collapse
I'm glad that it worked. Just enjoy it!
Reading this brought a warm feeling to my heart. Have fun with the phone. It's great!
Glad this got sorted. I think I can speak for all of us tinkerers when I say we've all been in this situation before and called upon the forum for advice. Pay it forward ^_^

Temporary install of TWRP on Q

Hello,
So I've just read this in another thread:
"Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. Use ADB or MTP to transfer the zip onto your device."
So far, my understanding that I can't install twrp when using android Q, but can I follow the above instructions to temporarily boot into twrp in order to make a backup?
I know Google have changed some partitioning stuff with the pixels so I don't want to screw anything up is all
Many thanks
mofaker33 said:
C:\Users\X\Desktop\platform-tools_r29.0.6-windows\platform-tools>fastboot boot C:\Users\X\Desktop\platform-tools_r29.0.6windows\platform-tools\twrp.img
fastboot: error: cannot load 'C:\Users\x\Desktop\platform-tools_r29.0.6-windows\platform-tools\twrp.img': too short
C:\Users\x\Desktop\platform-tools_r29.0.6-windows\platform-tools>fastboot boot twrp.img
fastboot: error: cannot load 'twrp.img': too short
Click to expand...
Click to collapse
Check your download...
Here's what I get, not much more useful...
Code:
> fastboot boot TWRP/twrp-3.4.0-0-sargo.img
Sending 'boot.img' (65536 KB) OKAY [ 2.187s]
Booting FAILED (remote: 'Error verifying the received boot.img: Invalid Parameter')
fastboot: error: Command failed
captain sideways said:
Hello,
So I've just read this in another thread:
"Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. Use ADB or MTP to transfer the zip onto your device."
So far, my understanding that I can't install twrp when using android Q, but can I follow the above instructions to temporarily boot into twrp in order to make a backup?
I know Google have changed some partitioning stuff with the pixels so I don't want to screw anything up is all
Many thanks
Click to expand...
Click to collapse
TWRP Is not *working* on Android 10 ... beside only booting you can also install it on your device but you will not be able to do a backup.
Ah OK, thanks for that, appreciate it. ? I'll stay tuned. I'm coming over from S7 stock oreo so I'm just relearning what's going on currently.
C:\Users\X\Desktop\platform-tools_r29.0.6-windows\platform-tools>fastboot boot C:\Users\X\Desktop\platform-tools_r29.0.6windows\platform-tools\twrp.img
fastboot: error: cannot load 'C:\Users\x\Desktop\platform-tools_r29.0.6-windows\platform-tools\twrp.img': too short
C:\Users\x\Desktop\platform-tools_r29.0.6-windows\platform-tools>fastboot boot twrp.img
fastboot: error: cannot load 'twrp.img': too short

unsupported file system error "raw"

Hey, i messed up my phone by installing something via magisk. Now im trying to install a new rom.
When i open the phone (lenovo p2a42), i get encryption error. For able to fix that problem i have to use "fastboot format userdata" command but i get raw file system error. How can i fix this? Disk manager doesn't see the phone.
Code:
adb reboot bootloader
error: no devices/emulators found
fastboot devices
ZY223TNMLC fastboot
fastboot format userdata
(bootloader) has-slot:userdata: not found
fastboot: error: Formatting is not supported for file system with type 'raw'.
edit ok i figure it out. power button, adv setting, recovery than continued to next step, there is no need to format
Jhumsmt said:
continued to next step
Click to expand...
Click to collapse
You mean continue to regular boot or continue to recovery?

Categories

Resources