Bricked ASUS Transformer Prime (still have fastboot/nvflash) - Asus Eee Pad Transformer Prime

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?

Related

[HowTo] [WIP] Fastboot for linux

Hi there,
I noticed yesterday that there are still no download sources for fastboot binaries that actually work with tegra devices (at least I did not find any). I compiled fastboot for linux (see downloads). Also there seem to be a bunch of people having problems to get fastboot running. This thread will hopefully help them.
It is still WORK IN PROGRESS! If you have ideas/questions/etc. just post them.
1) Get adb working:
- Follow instructions on http://developer.android.com/sdk/installing.html
- create /etc/udev/rules.d/51-android.rules containing:
Code:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0955", MODE="0666"
2) Get the correct binary from the download section below.
3) Copy the binary to yout platform-tools folder /...PathToAndroidSdk.../platform-tools/ and do a "chmod +x /...PathToAndroidSdk.../platform-tools/fastboot"
4) Make sure /...PathToAndroidSdk.../platform-tools/ is in your $PATH
Get your Folio into fastboot mode:
1) Power on
2) On first boot screen press 3 times Power followed by VolumeUp
3) Connect USB
WARNING: NEVER PRESS 4 TIMES POWER FOLLOWED BY VOLUMEDOWN!!! THIS WILL BRICK YOUR DEVICE!!!
Now you are all set up. Here are the commands you will need:
Flashing syntax:
Code:
fastboot flash <partition> <image>
Code:
#fastboot flash linux boot.img
#fastboot flash system system.img
#fastboot flash system system.img -w (This will wipe data after flashing the image)
#fastboot flash recovery recovery.img
Booting an image (recovery.img or boot.img) to try before flashing:
Code:
fastboot boot <bootable_image>
Code:
#fastboot boot boot.img
#fastboot boot recovery.img
Also useful:
Code:
#fastboot reboot
#fastboot devices (lists ???????? if Folio is connected, outputs nothing if not)
#fastboot erase %PartitionToErase%
DOWNLOADS:
Fastboot for linux-x86 and 64
%reserved%
Moved to general as not development
Ok it sounds really easy... but what will do every step ??
Cleaned Folio100 dust
Thanks mblaster! I was around with a Folio100 trying to install Dexter_nlb FolioMod1.4
(http://forum.xda-developers.com/showthread.php?t=846199) but got stuck at the "Verification
Signature Failed" when trying to install the update.zip.
Your direct method ruled out all barriers! It is quite simple do be done from a unix command line.
Nevertheless, "booting an image (recovery.img or boot.img) to try before flashing" did not
work for me. Anyway I took the risk, flashed directly and it worked!
I am here in fastboot usb mode, and how can I locate a ROM filename? I don't know how to access my phone and its SD card with fastboot.
Many thanks,

[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)

[Q] Urget Help: Erased Default Recovery but unable to Load CWM revocery

Dear Member,
I'm new to rooring and flashing custom ROMS...
i have a folio 100 and after a lot of googling and hardwork i finally managed to root my device on windows XP.. then i tried to install Jelly Bean / CM10 (4.1.1) Alpha 2 - 27.09.2012 from http://forum.xda-developers.com/showthread.php?t=1864774 and followed the instructions.
initially when i typed fastboot devices i was getting "? fastboot" and rest of the commands returned 0x2 error.
then i treid
fastboot -i 0x955 erase userdata
fastboot -i 0x955 erase system
fastboot -i 0x955 erase cache
fastboot -i 0x955 erase linux
fastboot -i 0x955 erase recovery
till now everything worked like a charm but when i tried to run the last command
fastboot -i 0x955 flash recovery recovery-cwm-6.0.1.4.img
i'm getting error message "unable to load recoveryxxxx.img"
now i treid to reboot the device and its saying "magic value mismatch" please help me out..
Nonlxpe Menteur
leaderrocks said:
Dear Member,
I'm new to rooring and flashing custom ROMS...
i have a folio 100 and after a lot of googling and hardwork i finally managed to root my device on windows XP.. then i tried to install Jelly Bean / CM10 (4.1.1) Alpha 2 - 27.09.2012 from http://forum.xda-developers.com/showthread.php?t=1864774 and followed the instructions.
initially when i typed fastboot devices i was getting "? fastboot" and rest of the commands returned 0x2 error.
then i treid
fastboot -i 0x955 erase userdata
fastboot -i 0x955 erase system
fastboot -i 0x955 erase cache
fastboot -i 0x955 erase linux
fastboot -i 0x955 erase recovery
till now everything worked like a charm but when i tried to run the last command
fastboot -i 0x955 flash recovery recovery-cwm-6.0.1.4.img
i'm getting error message "unable to load recoveryxxxx.img"
now i treid to reboot the device and its saying "magic value mismatch" please help me out..
Click to expand...
Click to collapse
First, download the latest & most stable ROM (at the moment), including the ROM, GAPPS, recovery-cwm-CM10-A3.img & formatsd.zip
http://forum.xda-developers.com/showthread.php?t=1864774
Actually, you just need to flash the recovery through fastboot, other else can done in the recovery.
1. Copy all the ROM, GAPPS & formatsd.zip into your memory card. Then insert it into your Folio.
2. Run command prompt, make sure your tablet is connected with your PC in fastboot mode.
To erase existing/stock recovery. In command prompt, go into the fastboot program folder and type the following commands
Code:
fastboot erase recovery
3. Copy the CWM Recovery into your fastboot adb folder.
To flash CWM Recovery
Code:
fastboot flash recovery recovery-cwm-CM10-A3.img
fastboot reboot
4. Enter Recovery. Before you begin, wipe everything (except external_sd) in the CWM Recovery, after wiped, you can install the 3 zip files one by one. After finish, just reboot system.
Full procedure also stated in the link I provided, please scroll down.
Hope that helps you.
So did above solution help? I had a similar issue, and I resolved it by just booting the recovery image from fastboot, i.e.
Code:
fastboot boot recovery.img
Once you get into recovery you can flash an image which will in most cases flash a recovery image along with it. If not, you can try to flash the recovery image again once you've done a full wipe from the booted recovery.

[Q] boot.blob and vendor IDs?

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

Flash recovery partition through the init.rc script (Android) [SOLVED]

Hello everyone, a year ago a I had installed a custom recovery on my Lenovo S5000-F and it caused a bootloop and I lost the recovery, fastboot is working fine but it only allow me flash boot, system, userdata and cache partitions. I already tried do:
1-Unpack boot.img
2-Edit default.prop to allow adb debugging and then create a custom OTA update to install by adb sideload.
But when I boot the system I get device offline. So looking through system.img I found an interesting thing, a flash recovery script: install-recovery.sh
Bash:
#!/system/bin/sh
echo 1 > /sys/module/sec/parameters/recovery_done #tony
if ! applypatch -c EMMC:recovery:6156288:b1d3582729e0f954b16931a7a87d4c09b6854396; then
log -t recovery "Installing new recovery image"
applypatch -b /system/etc/recovery-resource.dat EMMC:boot:5781504:94079a17dc0e061e417363e4d44d7d8d0e609f16 EMMC:recovery b1d3582729e0f954b16931a7a87d4c09b6854396 6156288 94079a17dc0e061e417363e4d44d7d8d0e609f16:/system/recovery-from-boot.p
if applypatch -c EMMC:recovery:6156288:b1d3582729e0f954b16931a7a87d4c09b6854396; then #tony
echo 0 > /sys/module/sec/parameters/recovery_done #tony
log -t recovery "Install new recovery image completed"
else
echo 2 > /sys/module/sec/parameters/recovery_done #tony
log -t recovery "Install new recovery image not completed"
fi
else
echo 0 > /sys/module/sec/parameters/recovery_done #tony
log -t recovery "Recovery image already installed"
fi
This script means to replace any recovery installed by the user to the original one, but for some reason its not working.
So I would like to know if there is any way to flash a recovery partition through a script, so I can write this script to init.rc to install the stock recovery and fix bootloop.
EDIT: The install-recovery.sh had installed the stock recovery but I didn't noticed lol, the cause of bootloop is because the recovery and logo partitions its in the same file so when I flashed TWRP with a size bigger than my recovery partition it wrote to logo partition too.
Solved by creating a custom script using the same "applypatch" binary to flash the logo partition and worked fine
I know you want init rc... but...
Flashing stock bootloader SHOULD restore your ability to RESTORE recovery, which in turn will be used to get you to flash an update or restore.
You also need to re-enable fastboot keys ((fastboot) device offline, need to grant adb keys in gui )
And then again, I've seen in my phone that with adb keys set in gui of fone, does not mean fastboot keys were registered, only seen this since android 10, never seen it in 9, or less...?
I dont help with custom roms because there is too many, but flashing
Pachacouti said:
I know you want init rc... but...
Flashing stock bootloader SHOULD restore your ability to RESTORE recovery, which in turn will be used to get you to flash an update or restore.
You also need to re-enable fastboot keys ((fastboot) device offline, need to grant adb keys in gui )
And then again, I've seen in my phone that with adb keys set in gui of fone, does not mean fastboot keys were registered, only seen this since android 10, never seen it in 9, or less...?
I dont help with custom roms because there is too many, but flashing
Click to expand...
Click to collapse
But I can't flash stock booloader, fastboot only flash boot, system, userdata and cache partitions, since I can flash boot I can make a modified init.rc script to flash the stock recovery during boot time, but I don't know how to do this :/
Me neither, I dont think init.rc (the app.apk) is going to be much use soon either.
You say:
But I can't flash stock booloader,
fastboot only flash boot, system, userdata and cache partitions, ...
So I'm kinda confused, because where you say 'But I cant flash stock bootloader' then say 'fastboot only flash boot' tells me you SHOULD be able to flash stock bootloader with this:
fastboot reboot bootloader
( lets me know your actually in the bootloader's fastboot, and not custom recovery (twrp style, mb with no twrp gui,) fastboot, which can be confusing, because your then using the recovery's fastboot, and not the bootloader that loads BEFORE the recovery VERSION of fastboot, which MAY be out of date..)
fastboot erase/format bootoader ( erase/format=whichever works, do not reboot )
fastboot -w
fastboot flash boot YOUR_STOCK_BOOTLOADER.img
fastboot -w
fastboot reboot
Then do:
fastboot -w
fastboot erase/format recovery ( again, whichever wipes recovery)
fastboot -w
then
fastboot flash recovery YOUR_STOCK_RECOVERY.img
Fastboot -w (so many huh? but makes sure things get wiped that may contain any hidden cache)
fastboot reboot
That should be it lol, apart from the fact I dont know if you are a/b partition in which case, try booting fone with
fastboot boot slot_a OR slot_b
After this, I cant add, cause I cant speak for custom roms, but the above would work for me.
Pachacouti said:
Me neither, I dont think init.rc (the app.apk) is going to be much use soon either.
You say:
But I can't flash stock booloader,
fastboot only flash boot, system, userdata and cache partitions, ...
So I'm kinda confused, because where you say 'But I cant flash stock bootloader' then say 'fastboot only flash boot' tells me you SHOULD be able to flash stock bootloader with this:
fastboot reboot bootloader
( lets me know your actually in the bootloader's fastboot, and not custom recovery (twrp style, mb with no twrp gui,) fastboot, which can be confusing, because your then using the recovery's fastboot, and not the bootloader that loads BEFORE the recovery VERSION of fastboot, which MAY be out of date..)
fastboot erase/format bootoader ( erase/format=whichever works, do not reboot )
fastboot -w
fastboot flash boot YOUR_STOCK_BOOTLOADER.img
fastboot -w
fastboot reboot
Then do:
fastboot -w
fastboot erase/format recovery ( again, whichever wipes recovery)
fastboot -w
then
fastboot flash recovery YOUR_STOCK_RECOVERY.img
Fastboot -w (so many huh? but makes sure things get wiped that may contain any hidden cache)
fastboot reboot
That should be it lol, apart from the fact I dont know if you are a/b partition in which case, try booting fone with
fastboot boot slot_a OR slot_b
After this, I cant add, cause I cant speak for custom roms, but the above would work for me.
Click to expand...
Click to collapse
Oh I got it now, you mean flashing stock bootloader into boot partition so when I turn on the device it will be on bootloader, I can try it but there's another problem, I don't have the stock bootloader lol
GO get it then lol...
Pachacouti said:
GO get it then lol...
Click to expand...
Click to collapse
Unfortunately I didn't found the bootloader, but I tried flash the stock recovery into boot partition, but when I reboot the device boots into grey screen and then shutdown. I have no idea why this not worked :/ I already tried boot the recovery through fastboot but its just transfer the recovery.img and not boot.

Categories

Resources