What update file does fastboot update command flash
i am not sure what you are asking but the command
fastboot update
flashes an update.zip file
here is some documentation:
Code:
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall 'flash boot' + 'flash system'
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
Hope that helps....
Using Fastboot, is there a way to apply the custom ROM zip files?
My goal: Apply a new ROM to the phone, without having to use the phone itself. IE: boot it into recovery, and drop to a shell, then use ADB to wipe/format the proper partitions, and flash the new ROM. If I can't flash the ROM (IE: Intension-v1.3.zip) that way, perhaps via Fastboot...I am not sure if there is a way, but if there is, could someone point me in the right direction?
Code:
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall 'flash boot' + 'flash system'
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
For more fastboot Commands go - Here
I am quite capable of reading the output of the fastboot command. But that talks about update.zip files and such (including in the link you posted)...but, for a file such as Intension-v1.3.zip only contains a boot.img...no data.img, or system.img as the link you posted discusses.
You could rename the Intension-v1.3.zip into update.zip and try 'fastboot flash update update.zip' But I'm not sure though...
BoomBoomPOW said:
You could rename the Intension-v1.3.zip into update.zip and try 'fastboot flash update update.zip' But I'm not sure though...
Click to expand...
Click to collapse
I Have thought of trying that, but afraid that if that is not the correct way to do it, that I might end up bricking my phone.
I am currently working on a solution to fix 4.4 with more stable results.
I have created a flashable zip that works in an aftermarket recovery. It replaces the platform.xml file with modified file that has the necessary permission line to make the sd card writable now. That is the only thing changed. I added the under WRITE_EXTERNAL_STORAGE.
You need to be on a custom recovery. This update only applies to I9505G. If you do not have an S4 GOOGLE EDITION PHONE, then please disregard and move on.
Warning; You are flashing this at your own risk. I am not responsible for broken devices, deleted memory cards, phones thrown from raging, or WW3.
Download the flashable from here: http://d-h.st/Eif
Download the modified platform.xml to replace the original from here if you would rather push it: http://d-h.st/ooU
(this is not needed with zip, already included)
1. Place the zip the on your internal or external drive.
2. Reboot to your custom recovery, ie ( twrp, cwm)
3. Create a backup, have a restore point if it does not work.
4. Wipe dalvik and cache
5. Install the zip file
6. Wipe the dalvik and cache just to be sure.
7. Reboot phone.
Test to make sure it worked by using any file explorer, ie(solid explorer, root explorer, etc.) and creating a new folder, text document, or whatever. Do this through the phone, not a p.c. If it does not work, reboot to recovery, restore back to previous point and let me know asap.
I like it
Sent from my SGH-I317 using Tapatalk 2
cdshepherd said:
I like it
Sent from my SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
Thanks I will incorporate this on the 4.3 if you don't mind with credit.
Sent from my GT-I9505G using Tapatalk 2
I don't mind at all. Use what ya need.
Sent from my GT-I9505G using Tapatalk 4
I did use Samurai's Odin package to update to mh5. I figures it would revert the permissions. My zip still works.
And TWRP 2.6.3.0 is out.
Sent from my GT-I9505G using Tapatalk 4
occupational_hazard said:
I have created a flashable zip that works in an aftermarket recovery. It replaces the platform.xml file with modified file that has the necessary permission line to make the sd card writable now. That is the only thing changed. I added the <group gid="media_rw"/> under WRITE_EXTERNAL_STORAGE.
You need to be on a custom recovery. This update only applies to I9505G. If you do not have an S4 GOOGLE EDITION PHONE, then please disregard and move on. This is only for the MH1 4.3 firmware that does not allow you to write to the sdcard.
Warning; You are flashing this at your own risk. I am not responsible for broken devices, deleted memory cards, phones thrown from raging, or WW3.
Download the flashable from here: http://d-h.st/Eif
Download the modified platform.xml to replace the original from here if you would rather push it: http://d-h.st/ooU
(this is not needed with zip, already included)
1. Place the zip the on your internal or external drive.
2. Reboot to your custom recovery, ie ( twrp, cwm)
3. Create a backup, have a restore point if it does not work.
4. Wipe dalvik and cache
5. Install the zip file
6. Wipe the dalvik and cache just to be sure.
7. Reboot phone.
Test to make sure it worked by using any file explorer, ie(solid explorer, root explorer, etc.) and creating a new folder, text document, or whatever. Do this through the phone, not a p.c. If it does not work, reboot to recovery, restore back to previous point and let me know asap.
Click to expand...
Click to collapse
You're welcome.
http://forum.xda-developers.com/showthread.php?p=44370296
When dialog fails, it's time for violence.
Really I would have never thought of doing that. That's ground breaking. Extraordinary!
Now do more research and you will see people have trouble writing to that file with root and trying a multitude of file explorers. And mounting system r/w. I still couldn't. Hence the links to the flashable in the op.
So....
Your welcome.
Sent from my GT-I9505G using Tapatalk 4
occupational_hazard said:
Really I would have never thought of doing that. That's ground breaking. Extraordinary!
Now do more research and you will see people have trouble writing to that file with root and trying a multitude of file explorers. And mounting system r/w. I still couldn't. Hence the links to the flashable in the op.
So....
Your welcome.
Sent from my GT-I9505G using Tapatalk 4
Click to expand...
Click to collapse
My sincere apologies. I'm having a bad day. I'm glad I could contribute to your work.
When dialog fails, it's time for violence.
Its all good and understandable.
Sent from my GT-I9505G using Tapatalk 4
That worked great, thank you!
Sent from my GT-I9505G using Tapatalk 2
apollokid said:
That worked great, thank you!
Sent from my GT-I9505G using Tapatalk 2
Click to expand...
Click to collapse
Works well on 4.4 also.
This is good to know
Sent from my GT-I9505G using Tapatalk
wilbarger said:
Works well on 4.4 also.
Click to expand...
Click to collapse
I had read that some folks were having troubles with the 4.4 update, can you update and then edit that file again the same way as before?
Prior to updating, I was running CM 10.2. I flashed back to stock 4.3 from here http://forum.xda-developers.com/showthread.php?t=2442445 and then flashed 4.4 from here http://forum.xda-developers.com/showthread.php?t=2544056. After that (which went flawlessly), I copied the SD card fix from this thread and then installed it. No issues at all and everything works perfectly.
We are lucky to have SamuriHL and MJHawaii helping us out with our phones. Sorry, left out occupational_hazard. No disrespect meant.
Below is the text from the platform.xml that is on my phone after I updated. There shouldn't be any need to flash on 4.4. But please let me know if I am wrong. I also can make the original 4.3 platform.xml file to flash so you can update through recovery of that is the issue
<?xml version="1.0" encoding="utf-8"?>
<!-- Copyright (C) 2008 The Android Open Source Project
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<!-- This file is used to define the mappings between lower-level system
user and group IDs and the higher-level permission names managed
by the platform.
Be VERY careful when editing this file! Mistakes made here can open
big security holes.
-->
<permissions>
<!-- ================================================================== -->
<!-- ================================================================== -->
<!-- ================================================================== -->
<!-- The following tags are associating low-level group IDs with
permission names. By specifying such a mapping, you are saying
that any application process granted the given permission will
also be running with the given group ID attached to its process,
so it can perform any filesystem (read, write, execute) operations
allowed for that group. -->
<permission name="android.permission.BLUETOOTH_ADMIN" >
<group gid="net_bt_admin" />
</permission>
<permission name="android.permission.BLUETOOTH" >
<group gid="net_bt" />
</permission>
<permission name="android.permission.BLUETOOTH_STACK" >
<group gid="net_bt_stack" />
</permission>
<permission name="android.permission.NET_TUNNELING" >
<group gid="vpn" />
</permission>
<permission name="android.permission.INTERNET" >
<group gid="inet" />
</permission>
<permission name="android.permission.READ_LOGS" >
<group gid="log" />
</permission>
<permission name="android.permission.READ_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
</permission>
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
</permission>
<permission name="android.permission.ACCESS_ALL_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="sdcard_all" />
</permission>
<permission name="android.permission.WRITE_MEDIA_STORAGE" >
<group gid="media_rw" />
</permission>
<permission name="android.permission.ACCESS_MTP" >
<group gid="mtp" />
</permission>
<permission name="android.permission.NET_ADMIN" >
<group gid="net_admin" />
</permission>
<!-- The group that /cache belongs to, linked to the permission
set on the applications that can access /cache -->
<permission name="android.permission.ACCESS_CACHE_FILESYSTEM" >
<group gid="cache" />
</permission>
<!-- RW permissions to any system resources owned by group 'diag'.
This is for carrier and manufacture diagnostics tools that must be
installable from the framework. Be careful. -->
<permission name="android.permission.DIAGNOSTIC" >
<group gid="input" />
<group gid="diag" />
</permission>
<!-- Group that can read detailed network usage statistics -->
<permission name="android.permission.READ_NETWORK_USAGE_HISTORY">
<group gid="net_bw_stats" />
</permission>
<!-- Group that can modify how network statistics are accounted -->
<permission name="android.permission.MODIFY_NETWORK_ACCOUNTING">
<group gid="net_bw_acct" />
</permission>
<permission name="android.permission.LOOP_RADIO" >
<group gid="loop_radio" />
</permission>
<!-- ================================================================== -->
<!-- ================================================================== -->
<!-- ================================================================== -->
<!-- The following tags are assigning high-level permissions to specific
user IDs. These are used to allow specific core system users to
perform the given operations with the higher-level framework. For
example, we give a wide variety of permissions to the shell user
since that is the user the adb shell runs under and developers and
others should have a fairly open environment in which to
interact with the system. -->
<assign-permission name="android.permission.MODIFY_AUDIO_SETTINGS" uid="media" />
<assign-permission name="android.permission.ACCESS_SURFACE_FLINGER" uid="media" />
<assign-permission name="android.permission.WAKE_LOCK" uid="media" />
<assign-permission name="android.permission.UPDATE_DEVICE_STATS" uid="media" />
<assign-permission name="android.permission.UPDATE_APP_OPS_STATS" uid="media" />
<assign-permission name="android.permission.ACCESS_SURFACE_FLINGER" uid="graphics" />
<!-- This is a list of all the libraries available for application
code to link against. -->
<library name="android.test.runner"
file="/system/framework/android.test.runner.jar" />
<library name="javax.obex"
file="/system/framework/javax.obex.jar"/>
</permissions>
Sent from my GT-I9505G using Tapatalk
I think you may be mistaken. After flash, it is as you stated. From what I understand, you will need to add (either by editing or by using your file in this thread) to change platform.xml to have <group gid="media_rw" /> statement under WRITE_EXTERNAL_STORAGE
Are you saying that you can store to external SD without this statement? I could not until I made the change.
occupational_hazard said:
Below is the text from the platform.xml that is on my phone after I updated. There shouldn't be any need to flash on 4.4. But please let me know if I am wrong. I also can make the original 4.3 platform.xml file to flash so you can update through recovery of that is the issue
<?xml version="1.0" encoding="utf-8"?>
<!-- Copyright (C) 2008 The Android Open Source Project
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<!-- This file is used to define the mappings between lower-level system
user and group IDs and the higher-level permission names managed
by the platform.
Be VERY careful when editing this file! Mistakes made here can open
big security holes.
-->
<permissions>
<!-- ================================================================== -->
<!-- ================================================================== -->
<!-- ================================================================== -->
<!-- The following tags are associating low-level group IDs with
permission names. By specifying such a mapping, you are saying
that any application process granted the given permission will
also be running with the given group ID attached to its process,
so it can perform any filesystem (read, write, execute) operations
allowed for that group. -->
<permission name="android.permission.BLUETOOTH_ADMIN" >
<group gid="net_bt_admin" />
</permission>
<permission name="android.permission.BLUETOOTH" >
<group gid="net_bt" />
</permission>
<permission name="android.permission.BLUETOOTH_STACK" >
<group gid="net_bt_stack" />
</permission>
<permission name="android.permission.NET_TUNNELING" >
<group gid="vpn" />
</permission>
<permission name="android.permission.INTERNET" >
<group gid="inet" />
</permission>
<permission name="android.permission.READ_LOGS" >
<group gid="log" />
</permission>
<permission name="android.permission.READ_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
</permission>
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
</permission>
<permission name="android.permission.ACCESS_ALL_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="sdcard_all" />
</permission>
<permission name="android.permission.WRITE_MEDIA_STORAGE" >
<group gid="media_rw" />
</permission>
<permission name="android.permission.ACCESS_MTP" >
<group gid="mtp" />
</permission>
<permission name="android.permission.NET_ADMIN" >
<group gid="net_admin" />
</permission>
<!-- The group that /cache belongs to, linked to the permission
set on the applications that can access /cache -->
<permission name="android.permission.ACCESS_CACHE_FILESYSTEM" >
<group gid="cache" />
</permission>
<!-- RW permissions to any system resources owned by group 'diag'.
This is for carrier and manufacture diagnostics tools that must be
installable from the framework. Be careful. -->
<permission name="android.permission.DIAGNOSTIC" >
<group gid="input" />
<group gid="diag" />
</permission>
<!-- Group that can read detailed network usage statistics -->
<permission name="android.permission.READ_NETWORK_USAGE_HISTORY">
<group gid="net_bw_stats" />
</permission>
<!-- Group that can modify how network statistics are accounted -->
<permission name="android.permission.MODIFY_NETWORK_ACCOUNTING">
<group gid="net_bw_acct" />
</permission>
<permission name="android.permission.LOOP_RADIO" >
<group gid="loop_radio" />
</permission>
<!-- ================================================================== -->
<!-- ================================================================== -->
<!-- ================================================================== -->
<!-- The following tags are assigning high-level permissions to specific
user IDs. These are used to allow specific core system users to
perform the given operations with the higher-level framework. For
example, we give a wide variety of permissions to the shell user
since that is the user the adb shell runs under and developers and
others should have a fairly open environment in which to
interact with the system. -->
<assign-permission name="android.permission.MODIFY_AUDIO_SETTINGS" uid="media" />
<assign-permission name="android.permission.ACCESS_SURFACE_FLINGER" uid="media" />
<assign-permission name="android.permission.WAKE_LOCK" uid="media" />
<assign-permission name="android.permission.UPDATE_DEVICE_STATS" uid="media" />
<assign-permission name="android.permission.UPDATE_APP_OPS_STATS" uid="media" />
<assign-permission name="android.permission.ACCESS_SURFACE_FLINGER" uid="graphics" />
<!-- This is a list of all the libraries available for application
code to link against. -->
<library name="android.test.runner"
file="/system/framework/android.test.runner.jar" />
<library name="javax.obex"
file="/system/framework/javax.obex.jar"/>
</permissions>
Sent from my GT-I9505G using Tapatalk
Click to expand...
Click to collapse
Are you sure about this? I think this is wrong and that the platform.xml file does not have that line in 4.4
That's the platform.XML I have after updating to 4.4 with no sdcard fix.
Sent from my GT-I9505G using Tapatalk
You can check it under /etc/permissions/platform.xml
Sent from my GT-I9505G using Tapatalk
Maybe since I did not use your file on 4.3 and did the text edit of the file instead, it didn't carry forward when I upgraded. I do know that when I flashed your file, it changed the statement to "media" instead of <group gid="sdcard_r" />.
Here is what I now have <permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_rw" />
<groud gid="media_rw" />
</permission>
Just to clarify, you can create a new folder on the SD card without the "media" statement??
Code:
usage: fastboot [ <option> ] <command>
commands:
update <filename> Reflash device from update.zip.
Sets the flashed slot as active.
flashall Flash boot, system, vendor, and --
if found -- recovery. If the device
supports slots, the slot that has
been flashed to is set as active.
Secondary images may be flashed to
an inactive slot.
flash <partition> [ <filename> ] Write a file to a flash partition.
flashing lock Locks the device. Prevents flashing.
flashing unlock Unlocks the device. Allows flashing
any partition except
bootloader-related partitions.
flashing lock_critical Prevents flashing bootloader-related
partitions.
flashing unlock_critical Enables flashing bootloader-related
partitions.
flashing get_unlock_ability Queries bootloader to see if the
device is unlocked.
flashing get_unlock_bootloader_nonce Queries the bootloader to get the
unlock nonce.
flashing unlock_bootloader <request> Issue unlock bootloader using request.
flashing lock_bootloader Locks the bootloader to prevent
bootloader version rollback.
erase <partition> Erase a flash partition.
format[:[<fs type>][:[<size>]] <partition>
Format a flash partition. Can
override the fs type and/or size
the bootloader reports.
getvar <variable> Display a bootloader variable.
set_active <slot> Sets the active slot. If slots are
not supported, this does nothing.
boot <kernel> [ <ramdisk> [ <second> ] ] Download and boot kernel.
flash:raw <bootable-partition> <kernel> [ <ramdisk> [ <second> ] ]
Create bootimage and flash it.
devices [-l] List all connected devices [with
device paths].
continue Continue with autoboot.
reboot [bootloader|emergency] Reboot device [into bootloader or emergency mode].
reboot-bootloader Reboot device into bootloader.
oem <parameter1> ... <parameterN> Executes oem specific command.
stage <infile> Sends contents of <infile> to stage for
the next command. Supported only on
Android Things devices.
get_staged <outfile> Receives data to <outfile> staged by the
last command. Supported only on Android
Things devices.
help Show this help message.
options:
-w Erase userdata and cache (and format
if supported by partition type).
-u Do not erase partition before
formatting.
-s <specific device> Specify a device. For USB, provide either
a serial number or path to device port.
For ethernet, provide an address in the
form <protocol>:<hostname>[:port] where
<protocol> is either tcp or udp.
-c <cmdline> Override kernel commandline.
-i <vendor id> Specify a custom USB vendor id.
-b, --base <base_addr> Specify a custom kernel base
address (default: 0x10000000).
--kernel-offset Specify a custom kernel offset.
(default: 0x00008000)
--ramdisk-offset Specify a custom ramdisk offset.
(default: 0x01000000)
--tags-offset Specify a custom tags offset.
(default: 0x00000100)
-n, --page-size <page size> Specify the nand page size
(default: 2048).
-S <size>[K|M|G] Automatically sparse files greater
than 'size'. 0 to disable.
--slot <slot> Specify slot name to be used if the
device supports slots. All operations
on partitions that support slots will
be done on the slot specified.
'all' can be given to refer to all slots.
'other' can be given to refer to a
non-current slot. If this flag is not
used, slotted partitions will default
to the current active slot.
-a, --set-active[=<slot>] Sets the active slot. If no slot is
provided, this will default to the value
given by --slot. If slots are not
supported, this does nothing. This will
run after all non-reboot commands.
--skip-secondary Will not flash secondary slots when
performing a flashall or update. This
will preserve data on other slots.
--skip-reboot Will not reboot the device when
performing commands that normally
trigger a reboot.
--disable-verity Set the disable-verity flag in the
the vbmeta image being flashed.
--disable-verification Set the disable-verification flag in the vbmeta image being flashed.
--unbuffered Do not buffer input or output.
--version Display version.
-h, --help show this message.
.
I've installed magisk and gapps on Slot B then i went to Slot A just bootloops?
Go to fastboot and type fastboot set_active b
Reiyn_ said:
Go to fastboot and type fastboot set_active b
Click to expand...
Click to collapse
There's no command?
Reiyn_ said:
Go to fastboot and type fastboot set_active b
Click to expand...
Click to collapse
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing partitions
flashing unlock unlocks the device. Allows user to flash any partition except the ones that are related to bootloader
flashing lock_critical Prevents flashing bootloader related partitions
flashing unlock_critical Enables flashing bootloader related partitions
flashing get_unlock_ability Queries bootloader to see if the device is unlocked
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootloader
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable