Question Flashing Factory Images - Google Pixel 5a

I am trying to flash 11.0.0 (RD2A.211001.002, Oct 2021) factory image in windows using the flash-all bat file. I updated my fastboot drivers in windows update and downloaded the latest platforms tools from google's website. I get this error while running the bat file.
FAILED (remote: Failed to write to partition Not Found)
finished. total time: 3.254s
Press any key to exit...
Any idea as to why?

Do you have your platform-tools folder in your PATH Variables?

kingofnice said:
Do you have your platform-tools folder in your PATH Variables?
Click to expand...
Click to collapse
I'm sorry what are the PATH Variables? Are you talking about the directory of my platform tools folder and my factory image?

On Windows 10, type in the search bar "system environment variables" and open that settings menu.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click on Environment Variables...
Edit
Add the location to your folder. Press Ok and Apply if you need.
Now try your adb and fastboot commands from a new command prompt window. They should be working from any directory you are using command prompt in.
I think that is why your flash failed, though I don't know. It sounds like it couldn't connect because it couldn't utilize fastboot to find a device/partition.
Test "fastboot devices" and if you see your device try flashing again. Also, "fastboot -w update image-xxx-xxx.zip" is in the flash-all bat. remove "-w" to stop it from wiping data. That's your call as you might need a fresh install.

Klimon5 said:
I'm sorry what are the PATH Variables? Are you talking about the directory of my platform tools folder and my factory image?
Click to expand...
Click to collapse
Did that help at all?

kingofnice said:
Did that help at all?
Click to expand...
Click to collapse
I ended up using Windows 10 to adb sideload the most recent android 11 OTA zip from google. I performed a factory data reset in recovery after I booted into the update first. I then was able to unlock the bootloader, re-enable the oem unlocking setting in dev options, & install the official lineage os recovery and rom for barbet. I will try your steps and see if I can flash a factory image. When I had my nexus 6p, I removed the -w prefix and immediately rebooted into recovery to factory data reset. It then booted just fine. For me I think that my platforms tools for Ubuntu are out of date.
I ran this command on my ubuntu machine.
$ adb version
Android Debug Bridge version 1.0.39
Version 1:8.1.0+r23-5ubuntu2
The lineage os installation instructions warns about issues with out of date platform tools.
Install LineageOS on barbet | LineageOS Wiki
wiki.lineageos.org
"Note: Outdated fastboot releases dropped legacy A/B support, so it might attempt to flash to boot__a / boot__b rather than boot_a / boot_b if you try to flash boot. In this case, you must update fastboot to a release newer than or equal to 31.0.2. Alternatively, you can manually specify which slot to flash to based on what slot fastboot failed to flash to. For example, if fastboot fails to flash to boot__a, you must flash to boot_a.
I want to try this on linux manjaro on my laptop. The platform tools built in are the latest version from google. I'll have to do some experimenting to see what works.

Klimon5 said:
For me I think that my platforms tools for Ubuntu are out of date.
The platform tools built in are the latest version from google. I'll have to do some experimenting to see what works.
Click to expand...
Click to collapse
This is the problem. Using outdated Platform Tools causes problems. Latest release is 31.0.3, Aug '21. Many other users have run into similar problems because they were using outdated Platform Tools.

Related

Cannot install CM 10.2 via ADB Sideload

Hi all,
I've been combing this forum to try and find the answer to my specific question, and I can't seem to find the answer.
I'm in the process of rooting/flashing a custom ROM to my KFHD7. I've gone through all the steps up until installing a ROM via TWRP. I've been following Seokhun's guide located here.
I downloaded Hashcode's CM 10.2 ROM here.
Once I booted into TWRP, I realized that somehow I had accidentally flashed /sdcard and I had no bootable ROM. Thus, I followed Seokhun's steps to sideload a ROM file:
6. Wiped /sdcard, can't reboot from recovery: You thought you had the ROM file on the sdcard, but you didn't, and wiped everything, so without a ROM image, you can't boot into system.
Solution: Put the ROM file where your ADB binary is (usually inside platform-tools folder in Android SDK directory) and rename it rom.zip. On the device, boot into TWRP, select Advanced, then ADB Sideload. Connect device to PC. From here, run "adb" and hit Enter to check for your binary version, if it's anything lower than 1.0.3.0, you need to update the binaries by re-installing the latest Android SDK. Once the device is in sideloading mode and is connected to the PC, type "adb sideload rom.zip" and hit Enter. Now you'll find the ROM on the sdcard, flash, and you're done.
Click to expand...
Click to collapse
I checked my ADB version:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and then moved Hashcode's CM 10.2 ROM from "downloads" to the folder where my ADB exe is located and renamed it "rom.zip" as the guide instructed:
Next, I boot into TWRP -> Advanced -> ADB Sideload via my fastboot cable
On that screen i see "Wipe Dalvik Cache" and "Wipe Cache" as check boxes along with "Swipe to Start Sideload" slider.
From there, i enter the command "adb sideload rom.zip" into the CMD prompt and it returns this:
UPDATED:
After thinking about it, I went in and changed the zipped folder name to "rom" realizing that the ".zip" should be understood as the file extension and not a part of the actual file name.
So, after changing the name, I went into TWRP -> Advanced -> ADB Sideload -> Swipe to begin sideload
I enter the command "adb sideload rom.zip" and it shows that Daemon starts successfully but then returns this error message:
and my KFHD7 does not download the ZIP file successfully.
So, after all of that, any ideas from the XDA community? Sorry this was so long. I'm new to the forums and wanted to make sure I was very specific to my individual problem. Thanks for the help in advance!
UPDATED:
I was able to find a solution here
I ran "adb usb" before running "adb sideload rom.zip" and it worked like a charm.
My KFHD7 is now successfully flashed with Hashcode's CM 10.2 mod!
I decided not to delete this thread in case anyone else had this very specific issue. However, if one of the mods feel it necessary to delete, then please do so.
for anyone else that comes along to this thread seeking salvation after a moment of forgetfulness and / or misguided recklessness, you can use Restore2Stock. took me a good while to find it but eventually stumbled across is and it solved everything, an exe that can fix everything as long as you can boot to TWRP:
http://n2aos.com/forum/restore2stock-r2s/890-kindle-fire-hd-7-wiped-operating-system.html
the above link is a brief explanation of how to use it. the download link is on the main page.
happy restoring

HTC One Bootloop after rooting

i Have the HTC One (m7ul) . it is free of any carriers
i am relatively new to all of this .
so i unlocked the boot loader via HTCDev and put in latest twrp.
i got cyanogen mod version 10.2 since its the latest STABLE version.
upon trying to install the ROM from twrp , it showed me -
Checking for MD5 file...
Skipping MD5 check: No MD5 file found.
Veryfying zip signature...
assert failed: getprop("ro.product.device") ==
getprop("ro.product.device") == "m7ul" |
E:Error executing updater binary in zip '/sdcard/'
Error flashing zip '/sdcard/airdroid/upload/cm-
Updating partition details...
Failed (under the box)
and i had already done a wipe so i have no OS
so it gets stuck on the *HTC-quietly brilliantly* screen
i have a mac running 10.9 on Intel i5 (if that helps in any way)
so i tried pushing the files after seeing some tutorials but was unsuccessful with the errors in terminal saying that the command is incorrect
later i got another tutorial - http://forum.xda-developers.com/showthread.php?t=1917237
and i followed the steps and used the files this user has uploaded and got this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please help me.
To be honest, it just sounds like you got a bad download.
Download the rom again on your computer, and push it to your phone in fastboot mode. Make sure that the phone says "fastboot usb" as that ensures that the phone can be seen by the computer when you plug it in.
Then try flashing it again.
Also, when you push the newly downloaded rom, just put it on the root of your sd card and flash it from there.
Sent from my HTC One using Tapatalk
Hi pardoned
the problem I'm facing is that I'm unable to push the file from my laptop (mac osx10.9)
sparsh436 said:
Hi pardoned
the problem I'm facing is that I'm unable to push the file from my laptop (mac osx10.9)
Click to expand...
Click to collapse
adb devices must return one device before you can use adb push.
Not familiar with Mac, but try:
1. another usb port (direct to motherboard, no hubs)
2. restarting computer
3. reinstalling adb-sdk
* adb is not available in fastboot / hboot / bootloader
sparsh436 said:
Hi pardoned
the problem I'm facing is that I'm unable to push the file from my laptop (mac osx10.9)
Click to expand...
Click to collapse
I am on osx 10.9.1 and use homebrew for my android-sdk needs ... Are you familiar with homebrew? if not, head over to brew.sh and carry out the installation of the script. I suggest you remove all previous android sdk installations from your mac prior to installing homebrew.
Once you have installed homebrew, run 'brew install android-sdk' from within terminal and connect your device then run 'adb devices' to view the connected devices and finally run 'adb push FileNameYouWantToPush.xxx /sdcard/LocationYouWantToSaveTheFileInOnYourDevice'
FYI - to keep your new android sdk installation up 2 date simply run 'brew update'
However, If you prefer to use android transfer from google, then follow the instructions here
Hope this helps!

Soft BRICKED A2 (bootloop)

I have bricked my A2 today. I first unlocked the bootloader then insatlled GCAM.
everything was fine, but i tried to install XPOSED (sdk 27) from Magisk module, then rebooted from magisk. My set is stuck at android one animation.
I downloaded official firmware of A2 and tried to flash via mi flash tool, always gets an error of "FLASH_DEVCFG_A ERROR" . Then i tried by clicking on "flash_all_except_data.bat" file, cmd just opened and closed very soon, Same thing happended with "flash_all_lock.bat" ,again cmd just opened and closed.
Still my phone is stuck at Android one animation, and i cant flash or boot my set.
EDIT :: USED. /FASTBOOT -W TO UNBRICK PHONE
Just follow this instructions on the link bellow.
https://forum.xda-developers.com/showpost.php?p=77302899&postcount=4
minnuss said:
Just follow this instructions on the link bellow.
https://forum.xda-developers.com/showpost.php?p=77302899&postcount=4
Click to expand...
Click to collapse
should i flash only those images? because i have some more image files than the llist, kindly check the screen shot
minnuss said:
Just follow this instructions on the link bellow.
https://forum.xda-developers.com/showpost.php?p=77302899&postcount=4
Click to expand...
Click to collapse
Now stuck at devcfg
PS C:\Users\KSN\Desktop\platform-tools> fastboot flash devcfg_b C:\Users\KSN\Desktop\images_V9.6.10.0.ODIMIFE_8.1\images\devcfg.img
target reported max download size of 536870912 bytes
sending 'devcfg_b' (47 KB)...
OKAY [ 0.005s]
writing 'devcfg_b'...
FAILED (remote: Flashing is not allowed for Critical Partitions
)
finished. total time: 0.007s
bluetooth_a , bluetooth_b was flashed successfully
try fastboot flashing unlock_critical
munchy_cool said:
try fastboot flashing unlock_critical
Click to expand...
Click to collapse
This appears everytime . :/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Syed Shahriar said:
This appears everytime . :/View attachment 4581400
Click to expand...
Click to collapse
xposed would have not messed with those partitions. did you flash system partition yet?
if not just flash system, vendor and boot
once you have flashed those, do fastboot -w (will loose all data).
and then reboot
fastboot reboot
munchy_cool said:
xposed would have not messed with those partitions. did you flash system partition yet?
if not just flash system, vendor and boot
once you have flashed those, do fastboot -w (will loose all data).
and then reboot
fastboot reboot
Click to expand...
Click to collapse
i just flashed bluetooth_a, bluetooth_b, and then went to devcf_a, failed , and did nothing else.
and what will be the command to flash system, vendor and boot ? kindly give me an example please
Syed Shahriar said:
i just flashed bluetooth_a, bluetooth_b, and then went to devcf_a, failed , and did nothing else.
and what will be the command to flash system, vendor and boot ? kindly give me an example please
Click to expand...
Click to collapse
GOT THESE ERROR::
PS C:\adb> fastboot flash system_a C:\adb\images\system.img
error: cannot load 'C:\adb\images\system.img'
my system iso is there in that location
but successfuly done fastboot flash vendor_b C:\adb\images\vendor.img
and fastboot flash vendor_a C:\adb\images\vendor.img
What are you even doing with all those commands
You need to download latest ADB, that is the first that you need to do, and second, copy all of the images from stock rom to your adb folder, it will be easier for commands to work.
And then start your cmd.exe with administrative privileges (right click on cmd in search bar of windows start, and "run as administrator").
Then move yourself from directory to your adb directory with commands from DOS, like "cd.." for going back from directory, and "cd nameofdir" to go into directory.
So move yourself in adb directory, then type the commands from the upper link to flash those .img one by one.
Oh yes, one other thing, you need to check if you see your mobile device in fastboot, did you install correct drivers.
When you are in adb folder, in cmd type fastboot devices, and you should see your mobile connected, if not, then you can type all you want, the phone is not recognized with pc connection.
Right, so... follow this guide to make sure you've unlocked your bootloader successfully. After you've finished, also add in the command "fastboot flashing unlock_critical". I'm not sure why it didn't work for you in the first place - but I know for a fact it works, because I did it to my own A2.
Make sure you've installed adb/drivers as attached by that link above. Why? 'Cause that's what I did, so I know it should work.
Then go here, extract the files to the same folder as platform-tools (the adb and fastboot tools folder), and run flash-all.bat.
Hey bro i do it too, tô solve, just do a fastboot unlock_critical
https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585
I had the same issue, no OS installed.
Adb Sideload and OTG didn't worl no matter what I tried.
I followed this thread, and it worked properly without errors, not even one.
It took me 5 minutes to recover my dead MiA2 device to a smooth original/official ROM built.
Locled OEM, rebooted the device and everything is working perfectlt.
Thank you all for the info.

Is it possible to root SM-A600FN without wiping/removing data?

It would be great if there's a way to root without the need to resetting
pruh said:
It would be great if there's a way to root without the need to resetting
Click to expand...
Click to collapse
Bootloader must be unlocked to root. Any time bootloader is unlocked, phone is wiped.
e
Tulsadiver said:
Bootloader must be unlocked to root. Any time bootloader is unlocked, phone is wiped.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
pruh said:
e
View attachment 5238617
Click to expand...
Click to collapse
Looks like your bootloader is at least ticked to unlock bootloader (or did you do that?). Make sure usb debugging is also ticked. Do you have a windows pc??
If you haven't already, install sdk platform tools on your pc.
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
You will need the boot.img for the firmware you are running. If you can't get it, send give a link to that exact firmware and I'll extract it.
You will also need the canary magisk app here:
https://github.com/topjohnwu/Magisk. Get the canary one.
Steps
Pur boot.img on phone sdcard
Install magisk canary app
Open app. Inside app, at top find and click on install magisk.
Select patch file. Find and select boot.img, hit "lets go". It'll patch file and put in your download folder (magisk_patched***.img).
Put this .img on your pc in the folder where you unzipped the sdk platform tools Rename just magisk_patched.img for simplicity. Open command window in that folder.
Boot your phone to bootloader mode (fastboot).
Plug phone into pc.
In your command window first type "fastboot devices". You should see your phones serial number. If not, there's a problem and the pc doesn't see your phone.
After you see your serial number, next type "fastboot flash boot magisk_patched.img"
Reboot and you should be rooted.
These are the steps for my phone, anyway. No data lost.
Tulsadiver said:
Looks like your bootloader is at least ticked to unlock bootloader (or did you do that?). Make sure usb debugging is also ticked. Do you have a windows pc??
If you haven't already, install sdk platform tools on your pc.
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
You will need the boot.img for the firmware you are running. If you can't get it, send give a link to that exact firmware and I'll extract it.
You will also need the canary magisk app here:
https://github.com/topjohnwu/Magisk. Get the canary one.
Steps
Pur boot.img on phone sdcard
Install magisk canary app
Open app. Inside app, at top find and click on install magisk.
Select patch file. Find and select boot.img, hit "lets go". It'll patch file and put in your download folder (magisk_patched***.img).
Put this .img on your pc in the folder where you unzipped the sdk platform tools Rename just magisk_patched.img for simplicity. Open command window in that folder.
Boot your phone to bootloader mode (fastboot).
Plug phone into pc.
In your command window first type "fastboot devices". You should see your phones serial number. If not, there's a problem and the pc doesn't see your phone.
After you see your serial number, next type "fastboot flash boot magisk_patched.img"
Reboot and you should be rooted.
These are the steps for my phone, anyway. No data lost.
Click to expand...
Click to collapse
Thanks!

[GUIDE]Xiaomi.EU ROMs Flashing Guide All Devices [Linux-Only]

Requirements:
Your device's bootloader must be unlocked.
Prerequisites:
Ubuntu/Debian/Ubuntu-Based Distros:
Open terminal
Type sudo apt install adb
Once that is installed.
Type sudo apt install fastboot.
Done.
Fedora:
Open terminal.
Type sudo dnf install android-tools.
Let it install and done.
OpenSUSE:
Download this official package from here according to your version :
https://software.opensuse.org/download.html?project=hardware&package=android-tools
(Use either one the add repository and install manually or grab binary packages directly options.)
Click to expand...
Click to collapse
MIUI 12 (Weekly And Stable)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Go to the sourceforge link of the rom and see the date of your rom. In this case it's alioth.
See the date of your rom . Now go to xiaomiformwareupdater.com and select your device. Then click download.
New page will appear. Type fastboot in the searchbar of the page. Now see global rom the date closest to the release of the xiaomi.eu rom and download.
Unzip the rom file to the root of home directory and connect your device to fastboot mode and open a terminal in the rom folder and run the command:
./flash_all.sh
A terminal window will popup and close after 15-20 min approx when flashing is done.This will delete your data.
Let the device boot into MIUI.
Once it boots power it off . Then press the vol down + power button until fastboot in orange letters appear.
TWRP method:
Flash twrp using fastboot.
Boot into twrp.
Go to wipe and format data.
Then factory reset in wipe.
Do not wipe anything in advanced wipe !
Copy the zip file to a fat32 formatted sdcard or usb.
Connect sdcard or usb to device.
Go to install , select storage , sd/usb, select rom zip and flash.
Once flashing done , wipe dalvik.
Reboot to recovery.
Reboot to system.
Done.
Fastboot:
Unzip rom file to root of home directory.
Go into folder.
Run fastboot installation script in folder
Open terminal window in the folder
If updating from older rom.
Run command in terminal:
./linux_fastboot_update_rom.sh
Done.
If installing first time.
Run command in terminal:
./linux__first_install_with_data_format_.sh
NOTE(For Stable And Recovery ROMs):
CHECK THE XIAOMI.EU THREAD FOR KNOWING IF YOUR ROM IS FASTBOOT OR RECOVERY.
Alternatively If you want you can flash india , eea , turkey , etc variants of stock rom instead of global , then flash xiaomi.eu according to the instructions above. But keep in mind that the release date of stock rom that you are flashing should be closest to the release date of xiaomi.eu weekly rom.
Install magisk after first boot and reboot after installing magisk to get rid of system lags.

Categories

Resources