Would this be possible? If so, could the terminal command simply be fastboot flash splash1 splash.img as it is with certain phones?
Related
So I was able to easily unlock the bootloader but when trying to install recovery I get the following: "error cannot load recovery.img" Any idea what I'm doing wrong? I have fastboot and recovery.img in same folder so I'm not sure what the problem is. Any help would be greatly appreciated as I'd really like to install Kens rom and restore my phone to my liking.
First not a major issue your just not typing something right or not placed right
Lets do this !
2nd Please Remove install_recovery.sh located in your /system/etc/ ,so that the recovery will not be overwrite to stock one.
you dont HAVE to it will still work just wont have the stock recovery.
1st make sure the moto-fastboot or fastboot (they both work i have tested )file is in your c:\
you have to cd the drive first so make sure its in c:\ the commands on the guide for cwm needs
to be updated this will help you out.FYI make sure all the files are in one folder not the root drive
so name a folder (whatever) then cd that folder from cmd.
Dont use " " just showing you commands
Then go to cmd
"cd c:\moto-fastboot" or fastboot
click enter
then type "moto-fastboot flash recovery recovery-en-goapk-0630-1029.img" or fastboot
click enter
Should say writing\sending
Once your done and it completes
type moto-fastboot reboot or fastboot
enter
P.S. Depending on if your using fastboot or moto-fast boot
commands would be
"fastboot flash recovery recovery-en-goapk-0630-1029.img" Fastboot
"moto-fastboot flash recovery recovery-en-goapk-0630-1029.img" moto-fastboot
And if you were wondering
Moto-fastboot is for bigger files
fastboot is for smaller files
They both work because the recovery is in
the middle in size for both fastboots.
I know that with HTC devices we can use
Code:
fastboot flash splash1 image.img
to flash a different splash screen (the one before the boot animation)
Can we also do this with the Atrix?
Is it universal to all android devices, or only HTC?
I'd like to flash the PRI and the Radio.
Am I allowed to use the same commands as shown here for when flashing an hboot? or do I need to flash to a certain partition?
http://forum.xda-developers.com/showpost.php?p=32259533&postcount=60
To flash an HBOOT from fastboot while S-OFF:
1. Put your phone in "fastboot usb" mode
2. Type the following cmds into cmd prompt (windows) or terminal (linux):
fastboot devices <-- to verify connectivity to PC: it should return your serial number
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip new_hboot.zip
fastboot reboot
The hboot filename can be anything you want, and doesn't necessarily have to be "PG86IMG.zip" using this method.
If you need to flash another ROM before the reboot or do something else in recovery, you can issue the "fastboot boot recovery.img" command instead of "fastboot reboot" to go directly to your custom recovery since there is no "fastboot reboot-recovery" command.
Click to expand...
Click to collapse
rancur3p1c said:
I'd like to flash the PRI and the Radio.
Am I allowed to use the same commands as shown here for when flashing an hboot? or do I need to flash to a certain partition?
http://forum.xda-developers.com/showpost.php?p=32259533&postcount=60
Click to expand...
Click to collapse
I couldn't find the answer on XDA, but did find this thread on another site. Although it wasn't written for the Evo 3D/V, that user has worked with a lot of HTC phones and states at the beginning of the OP that he uses the technique on all his HTC phones.
Further down in the OP he states that once you've issued the "fasboot oem rebootRUU" command you can flash as many zip files as you want, including hboot, recovery, firmware, splash screen and RUU. My understanding is that command is equivalent to flashing PG86IMG.zip files from the bootloader except you don't have to mess with files in the root of your SD card.
After I learned about this method, I keep all my bootloaders in the ADB/fastboot directory on my PC and flash them from there. I still flash recoveries and splash screens using the partition specific flash commands ("fastboot flash recovery" and "fastboot flash splash1") but only when they are not packaged in zip files with the required android-info.txt file.
ramjet73
but only when they are not packaged in zip files with the required android-info.txt file.
ramjet73[/QUOTE]
This is my question, how do you make a PG86IMG.zip file? I've googled w no luck...
Sent from 3D A.W.E.S.O.M-O
Hi all,
I'm installing CM10.1 on a TF201. Extracting the rom.zip shows there's a boot.blob and a boot.img. I've fastboot'd the boot.img, and can boot into CM fine.
What does the boot.blob provide, do I need to flash it, and if so, does the command need a -i 0x0b05 argument? I've seen other threads which state that the command should be:
Code:
fastboot flash boot -i 0x0b05 boot.blob
rather than just
Code:
fastboot flash boot boot.blob
Was wondering if someone can explain the difference in the set of commands, as I see it on different guides in regards to flashing a new rom. does "Flashing" a partition technically erase it, overwrite it? Overwrite it leaving extra junk behind?
Code:
>fastboot erase boot
>fastboot erase recovery
>fastboot erase system
>fastboot flash system system.img
>fastboot flash boot boot.img
>fastboot flash recovery recovery.img
VS
Code:
>fastboot flash system system.img
>fastboot flash boot boot.img
>fastboot flash recovery recovery.img
Necro bump
morbid_bean said:
Was wondering if someone can explain the difference in the set of commands, as I see it on different guides in regards to flashing a new rom. does "Flashing" a partition technically erase it, overwrite it? Overwrite it leaving extra junk behind?
Code:
>fastboot erase boot
>fastboot erase recovery
>fastboot erase system
>fastboot flash system system.img
>fastboot flash boot boot.img
>fastboot flash recovery recovery.img
VS
Code:
>fastboot flash system system.img
>fastboot flash boot boot.img
>fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Lemme see if I can shed a little light...
>fastboot erase boot - Tells fastboot to erase the boot partition
>fastboot erase recovery - Tells fastboot to erase the recovery partition
>fastboot erase system
>fastboot flash system system.img - Tells fastboot to flash the system partition with system.img
>fastboot flash boot boot.img - Tells fastboot to flash the boot partition with boot.img
>fastboot flash recovery recovery.img
Flashing a partition overwrites the existing contents. I should mention that using fastboot to install a ROM is a slow way to go. Fastboot is typically used for quick simple flashes or repairs, like changing your kernel/boot image. Also, fastboot makes a device practically unbrickable.
Yes they are different, read:
The flash command shouldn't erase the partition unless the host fastboot tool sends an erase command first. This allows flashing a very large partition in multiple smaller chunks using multiple sparse images that start with a "skip" block to seek over the already-written area. Creating these images on demand is already handled by the fastboot host side tool.
This is from https:// source.android.com/devices/bootloader/images
(fill in the space, they wouldnt let me post a url)