[Q] boot.blob and vendor IDs? - Android Q&A, Help & Troubleshooting

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

Related

[Q] fastboot help

hi im getting fastboot mode started
udc_start()
i tried using fast boot reviving post but
im erasing recovery successful
but when i execute fastboot flash recovery recovery.img
im getting an error that not loading recovery.img heip me.......
Try typing the entire path to the recovery file.
follow this to flash custom recovery http://forum.xda-developers.com/showthread.php?t=1318750
for the command "fastboot flash recovery recovery.img", recovery.img refers to the file of your recovery. try doing either:
a) make sure that the name of the recovery file is "recovery.img".
b) change the command "fastboot flash recovery recovery.img" to "fastboot flash recovery (name of the file).img", where (name of the file).img is the actual name of the recovery file (for example, if the name of the file is thunderg.img, the command would be "fastboot flash recovery thunderg.img)

Bricked ASUS Transformer Prime (still have fastboot/nvflash)

So, my ASUS Transformer Prime (unlocked bootloader, had CWM Recover + Cyanogenmod 9) is bricked after:
(a) following the instructions here (which flashed AndroidRoot to the "staging" partition) and then,
(b) flashing a bad kernel on the "boot" partition.
The tablet is now only displaying the AndroidRoot text when booting and then freezes -- holding the power button just reboots it. Power+vol_down can put it into fastboot, or vol_up during the reboot takes it into APX mode (where it seems I can use nvflash through wheelie, as mentioned in those instructions).
Also, when I power it up holding power+vol_down, I have two choices: wipe data & fastboot mode, the 3rd one about booting the system normally, is gone.
My question is: can I reflash the staging/boot/recovery partitions using fastboot/nvflash with suitable data to revert the tablet to working condition?
I also have the following files:
blob.bin blob.log bootloader.ebt create.bct recovery.bct
and blob.log describes them as follows:
===================
Generating encrypted EBT file 'bootloader.ebt'...done.
Generating encrypted recovery BCT file 'recovery.bct'...done.
Generating encrypted create BCT file 'create.bct'...done.
Generating blob file 'blob.bin'...done.
Adding create BCT to blob file [wheelie]...done.
Adding recovery BCT to blob file [wheelie]...done.
Adding bootloader to blob file [wheelie]...done.
Adding odmdata to blob file [wheelie]...done.
Adding chip id to blob file [wheelie]...done.
===================
For androidroot bootloaders, You'll have to do the following:
1. Download recovery of choice, unzip the recovery if it is zipped.
2. Once you have the blob file, use a tool called blobunpack found in xda, and unpack the blob file.
http://forum.xda-developers.com/showthread.php?t=1068548
3. You should end up with a file with an SOS extention. Now you should be able to fastboot flash the recovery with this file.
Code:
fastboot -i 0x0b05 flash recovery twrp.SOS
4. Once you have recovery, you will need to adb push the rom to the internal sd, and install through recovery, or in your case, you could unzip the rom, blobunpack the blob, and flash the kernel/ramdisk img to the boot partition using fastboot. In the case of the boot, the file will have an LNX extention.
Code:
fastboot -i 0x0b05 flash boot boot.blob.LNX
Hope it all goes well!
Sent from my SO-01C using xda app-developers app
kokopuphz said:
For androidroot bootloaders, You'll have to do the following:
1. Download recovery of choice, unzip the recovery if it is zipped.
2. Once you have the blob file, use a tool called blobunpack found in xda, and unpack the blob file.
http://forum.xda-developers.com/showthread.php?t=1068548
3. You should end up with a file with an SOS extention. Now you should be able to fastboot flash the recovery with this file.
Code:
fastboot -i 0x0b05 flash recovery twrp.SOS
4. Once you have recovery, you will need to adb push the rom to the internal sd, and install through recovery, or in your case, you could unzip the rom, blobunpack the blob, and flash the kernel/ramdisk img to the boot partition using fastboot. In the case of the boot, the file will have an LNX extention.
Code:
fastboot -i 0x0b05 flash boot boot.blob.LNX
Hope it all goes well!
Sent from my SO-01C using xda app-developers app
Click to expand...
Click to collapse
kokopuphz, thank you very much for your help! I finally unbricked the device by unpacking the boot.blob of the cyanogenmod version (which was already installed) and flashing the .LNX file to the "boot" partition.
I also flashed the CWM recovery to the "boot" partition, but rebooting from inside Cyanogenmod to it doesn't work: it just shows the AndroidRoot message and then the tablet reboots again and continues loading Cyanogenmod. To boot into CWM recovery without using the Cyanogenmod reboot menu, I had to use the instructions here.
Extremely helpful, I have a habit of erasing everything from fastboot and erased the boot. I already had the recovery flashed but need the boot as well.
Thanks
boot loader locked
I have a similar situation but my bootloader is still locked. The damage was done by
fastboot -i 0x0b05 erase cache
fastboot -i 0x0b05 erase userdata
fastboot -i 0x0b05 erase recovery
fastboot -i 0x0b05 erase staging
fastboot -i 0x0b05 erase system
Any help?

[Q] move to CWM from TWRP

I flashed TWRP to my tablet using the ADB/dd commands mentioned in the TWRP website. Now I wanna use the CWM that is included in the boot.img of cyanogenmod.
How do I do it? Do I just boot into fastboot and run fastboot to flash CWM?
Here's the adb commands use to flash TWRP
Code:
Download the above file. Copy the file to /sdcard/fotakernel.img and run the following commands using terminal emulator or in adb shell:
su
dd if=/sdcard/fotakernel.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Here's the fastboot commands use to flash CWM according to cyanogenmod.
Code:
fastboot -i 0xfce flash boot boot.img
fastboot -i 0xfce reboot
thanks!
anyone? thanks

Fastboot Flash vs Fastboot Erase

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)

Installing freexperia aosp rom - help

Guys i really wanna try this rom!
But which commands do i have to use to install it? I know that i have to do "fastboot flash boot boot.img" etc.
I tried to install once but it got stuck sending system (fastboot flash system system.img).
What do i do wrong?
Anyone with an input?
Do twrp backup first.
fastboot -S 256M flash boot boot.img
fastboot -S 256M flash system system.img
fastboot -S 256M flash userdata userdata.img

Categories

Resources