First the facts:
I have a Transformer Prime TF201
-l have Cyanogen mod 10-20140104 installed
-I used to have CWM recovery installed (Cant remember witch version)
-I have followed this guide: http://androidroot.mobi/t3_nvflash/ to get nvFlash and AndroidRoot.mobi bootloader (v9.4.2.28r01)
After this i wanted to install TWRP as i had problems taking rom backups with cwm.
I followed this guide http://teamw.in/project/twrp2/93 and downloaded and installed "openrecovery-twrp-2.3.3.0-tf201-JB.img" using fastboot
The ".img" version of twrp seems to be for those who have AndroidRoot.mobi bootloader
after this i was unable to restart from fastboot, so i just did a manual restart with the power button
Now i expected the progress bar to appear, but android just started to boot.
After the boot i tried to boot to recovery using the power menu, just booted back to android again.
Then i tried getting inn to recovery by holding power and vol down, same thing then also. just booted in to android.
I have also tried to install cwm (recovery-clockwork-5.8.3.4-tf201.img) using fastboot with the same result.. no progress bar appears after reboot.
This is the result when installing CWM in fastboot:
C:\android-sdk\platform-tools>fastboot -i 0x0b05 flash recovery cwm.img
sending 'recovery' (5408 KB)...
OKAY [ 2.594s]
writing 'recovery'...
OKAY [ 2.132s]
finished. total time: 4.734s
C:\android-sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.553s
(The device is not restarting, i have to do this manualy)
I have also tried installing CWM in android terminal using "dd if=/sdcard/cwm.blob of=/dev/block/mmcblk0p4"
This is the result:
[email protected]:/ $ su
[email protected]:/ # dd if=/storage/sdcard0/cwm.blob of=/dev/block/mmcblk0p4
10816+1 records in
10816+1 records out
5537896 bytes transferred in 6.596 secs (839583 bytes/sec)
So now im left without a recovery at all
Anyone that might have some tips for me?
? I just read the part where you attempted to install from the os. your prime still boots? lucky. where is the nvidia on the splash screen at boot up bottom center or bottom right?
i have same problem also, my tf201 now have bootloader unlock and twrp 2.2.2.0 recovery, i try to upgrade it to the latest version following instuctions on http://teamw.in/project/twrp2/93
on my command prompt, it said that flashing recovery is success, but everytime i boot to recovery, it is still 2.2.2.0
Solved
I was able to get twirp on by flashing an older wersion of twrp (v 2.3.1.0)
svefro said:
I was able to get twirp on by flashing an older wersion of twrp (v 2.3.1.0)
Click to expand...
Click to collapse
you were actually fortunate you did not completely brick your prime. you did twice what you should never do. you tried to put a jellybean recovery on an ICS bootloader. then not knowing if you had jellybean bootloader or not you attempted to install cwm which is strictly for ics. Both of these things are what hard bricks the most primes here. When you do want to upgrade to Jellybean I suggest you go to post 2 of the androwook thread and follow the instructions there.
I assumed i had JB bootloader since i have android 4.1.2 installed.. guess not
is this the thread you are referring to? http://forum.xda-developers.com/showthread.php?t=1674827
and this is the official ASUS JB Bootloader? Update JB Bootloader.zip ?
can i just flash the jb bootloader and then twrp 2.3.3.0?
do i need to do a whipe and reinstall my rom afterwards?
I realy appreciate the help im getting here.
Hi, i have an unlocked tf201 and tried to install recovery-clockwork-touch-5.8.1.8-tf201.img which seemd to go fine:
Code:
sudo ./fastboot -i 0x0b05 flash recovery recovery-clockwork-touch-5.8.1.8-tf201.img
sending 'recovery' (5380 KB)...
OKAY [ 2.432s]
writing 'recovery'...
OKAY [ 7.011s]
finished. total time: 9.443s
hamlet:Console_Connection michael$ ./fastboot reboot
rebooting...
finished. total time: 0.001s
Thing is the recovery console will not load, after i select it (RCK) nothing happens? The message at top of screen says
Code:
Booting into recovery kernel image
If power off and on again it will boot fine into latest Asus jelly bean rom.
I have tried to re-flash, but now i can no longer find the device in OSX?
Code:
adb devices
List of devices attached
This is the same in both fastboot and when booted normally?
Any ideas?
many thanks
Seems i can find it as a device with adb when booted normally, but not when in fastboot?
ah seems it does not matter if not seen as device when in fastboot as i tried flash again it it seems to work
Code:
sudo ./fastboot -i 0x0b05 flash recovery recovery-clockwork-touch-5.8.1.8-tf201.img
Password:
sending 'recovery' (5380 KB)...
OKAY [ 2.427s]
writing 'recovery'...
OKAY [ 6.286s]
finished. total time: 8.713s
but still it will not boot into recovery?
Thanks
Even tried flashing openrecovery-twrp for jb, but still won't boot into recovery?
any help here would very much appriciated
carperman said:
Even tried flashing openrecovery-twrp for jb, but still won't boot into recovery?
any help here would very much appriciated
Click to expand...
Click to collapse
You are not saying what we need to know.
What bootloader are you on ? Where is the "NVIDIA" logo when you first power on the device? Bottom center or bottom right ?
flumpster said:
You are not saying what we need to know.
What bootloader are you on ? Where is the "NVIDIA" logo when you first power on the device? Bottom center or bottom right ?
Click to expand...
Click to collapse
flumpster said:
You are not saying what we need to know.
What bootloader are you on ? Where is the "NVIDIA" logo when you first power on the device? Bottom center or bottom right ?
Click to expand...
Click to collapse
Sorry thought i had made it clear?
Thanks for the reply i will try and be clearer.
In answer to your question about nvidia logo, it is bottom right.
What i have:
New TF201
unlocked when running ICS
Updated to latest Asus Jelly Bean rom
What i want to achieve:
I wish to root tablet (super user) and eventually install a custom rom.
What i need to do:
Flash clockwork-touch
install superuser.zip via recovery console
Results:
adb devices - report device
fastboot devices - shows no devices
boot to fastboot with 'power/vol ok
fastboot -i 0x0b05 flash recovery *.img - seems to work, see OP
fastboot reboot-bootloader works though recovery never loads
boot to recovery with 'power/vol never loads
For the last 2 it just says
Booting into recovery kernel image
I tried installing rtr_recovery-clockwork-touch which patched version, which again seems to work
Code:
fastboot -i 0x0b05 flash recovery rtr_recovery-clockwork-touch-5.8.1.8-tf201/recoveryblob
sending 'recovery' (5398 KB)...
OKAY [ 2.387s]
writing 'recovery'...
OKAY [ 6.398s]
finished. total time: 8.785s
Code:
fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
This worked, but as before nothing happens it just sits at B]
Booting into recovery kernel image[/B]
The two issue i have are:
fastboot cannot see devices (seem to work though)
recovery is not loading
I can only assume that even though fastboot seems to flashing device, blue load bar appears on tablet and reboot-bootloader commands works, it is not actually flashing the device?
thanks
carperman said:
Sorry thought i had made it clear?
Thanks for the reply i will try and be clearer.
In answer to your question about nvidia logo, it is bottom right.
What i have:
New TF201
unlocked when running ICS
Updated to latest Asus Jelly Bean rom
What i want to achieve:
I wish to root tablet (super user) and eventually install a custom rom.
What i need to do:
Flash clockwork-touch
install superuser.zip via recovery console
Results:
adb devices - report device
fastboot devices - shows no devices
boot to fastboot with 'power/vol ok
fastboot -i 0x0b05 flash recovery *.img - seems to work, see OP
fastboot reboot-bootloader works though recovery never loads
boot to recovery with 'power/vol never loads
For the last 2 it just says
Booting into recovery kernel image
I tried installing rtr_recovery-clockwork-touch which patched version, which again seems to work
Code:
fastboot -i 0x0b05 flash recovery rtr_recovery-clockwork-touch-5.8.1.8-tf201/recoveryblob
sending 'recovery' (5398 KB)...
OKAY [ 2.387s]
writing 'recovery'...
OKAY [ 6.398s]
finished. total time: 8.785s
Code:
fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
This worked, but as before nothing happens it just sits at B]
Booting into recovery kernel image[/B]
The two issue i have are:
fastboot cannot see devices (seem to work though)
recovery is not loading
I can only assume that even though fastboot seems to flashing device, blue load bar appears on tablet and reboot-bootloader commands works, it is not actually flashing the device?
thanks
Click to expand...
Click to collapse
First off, awesome report. Far more than I needed but I won't have to ask you another question along the way from now on.
You are on the jellybean bootloader. You should not even be flashing CWM while on that because that is how so many people hard brick their devices.
Can you please try downloading the custom TWRP I have in the following link that I have installed myself and made for the jellybean bootloader so I know this is where we are both at. The zip file has a bat file and you just run it and follow onscreen instructions.
http://forum.xda-developers.com/showpost.php?p=26595675&postcount=2
You want Hairybean TWRP Updater (normal).
Please do not try to install CWM at any point from now on.
flumpster said:
First off, awesome report. Far more than I needed but I won't have to ask you another question along the way from now on.
You are on the jellybean bootloader. You should not even be flashing CWM while on that because that is how so many people hard brick their devices.
Can you please try downloading the custom TWRP I have in the following link that I have installed myself and made for the jellybean bootloader so I know this is where we are both at. The zip file has a bat file and you just run it and follow onscreen instructions.
http://forum.xda-developers.com/showpost.php?p=26595675&postcount=2
You want Hairybean TWRP Updater (normal).
Please do not try to install CWM at any point from now on.
Click to expand...
Click to collapse
Thanks, will give it a try.
Must have done something as cannot get adb to find device when in fastboot now?
Tried rebooting workstation and tablet a few times, but no joy
and your bat file did not find device either?
carperman said:
Must have done something as cannot get adb to find device when in fastboot now?
Tried rebooting workstation and tablet a few times, but no joy
and your bat file did not find device either?
Click to expand...
Click to collapse
adb does not work in fastboot. Only the fastboot command does. The only places you can use adb is either while in the OS or while in recovery.
The .bat file would have tried to run a fastboot flash command.
Here is odd thing though, even though adb devices shows nothing and the .bat can't find connection the command fastboot reboot-bootloader works?
Note the error i get with .bat is
./HairyBean TWRP Recovery Flasher.bat: line 1: @echo: command not found
************************************************
HairyBean TWRP Jelly Bean Recovery Flasher
: command not foundcovery Flasher.bat: line 4: echo.
1. Turn OFF the device
./HairyBean TWRP Recovery Flasher.bat: line 6: syntax error near unexpected token `('
'/HairyBean TWRP Recovery Flasher.bat: line 6: `echo 2. Turn ON the device (hold power + vol down)
hamlet:HairyBean TWRP Updater 2.4.1.0 (normal) michael$ ./HairyBean\ TWRP\ Recovery\ Flasher.bat
./HairyBean TWRP Recovery Flasher.bat: line 1: @echo: command not found
************************************************
HairyBean TWRP Jelly Bean Recovery Flasher
: command not foundcovery Flasher.bat: line 4: echo.
1. Turn OFF the device
./HairyBean TWRP Recovery Flasher.bat: line 6: syntax error near unexpected token `('
'/HairyBean TWRP Recovery Flasher.bat: line 6: `echo 2. Turn ON the device (hold power + vol down)
hamlet:HairyBean TWRP Updater 2.4.1.0 (normal)
Just noticed that fastboot now find device though
fastboot devices
015d0787bf2fee07 fastboot
thanks
carperman said:
Here is odd thing though, even though adb devices shows nothing and the .bat can't find connection the command fastboot reboot-bootloader works?
Note the error i get with .bat is
./HairyBean TWRP Recovery Flasher.bat: line 1: @echo: command not found
************************************************
HairyBean TWRP Jelly Bean Recovery Flasher
: command not foundcovery Flasher.bat: line 4: echo.
1. Turn OFF the device
./HairyBean TWRP Recovery Flasher.bat: line 6: syntax error near unexpected token `('
'/HairyBean TWRP Recovery Flasher.bat: line 6: `echo 2. Turn ON the device (hold power + vol down)
hamlet:HairyBean TWRP Updater 2.4.1.0 (normal) michael$ ./HairyBean\ TWRP\ Recovery\ Flasher.bat
./HairyBean TWRP Recovery Flasher.bat: line 1: @echo: command not found
************************************************
HairyBean TWRP Jelly Bean Recovery Flasher
: command not foundcovery Flasher.bat: line 4: echo.
1. Turn OFF the device
./HairyBean TWRP Recovery Flasher.bat: line 6: syntax error near unexpected token `('
'/HairyBean TWRP Recovery Flasher.bat: line 6: `echo 2. Turn ON the device (hold power + vol down)
hamlet:HairyBean TWRP Updater 2.4.1.0 (normal)
Just noticed that fastboot now find device though
fastboot devices
015d0787bf2fee07 fastboot
thanks
Click to expand...
Click to collapse
I see a michael subfix in there. Are you running this zip from desktop or a link? Can you please try extracting the zip to a physical drive (e.g. make a folder on d: and call it wookie then extract the zip in it.
I have seen before this script failing on desktop.
edit... I have just looked back at your earlier outputs. Are you in linux because I presumed you was on windows when I started? The .bat file is for windows and it will probably not even work in linux because of the links.
ok sorted, checked the .bat and is for windows i am on OSX so did
fastboot -i 0x0B05 flash recovery fastboot/recoveryTWRP.blob
and it works
great many thanks, now to try your custom rom
carperman said:
ok sorted, checked the .bat and is for windows i am on OSX so did
fastboot -i 0x0B05 flash recovery fastboot/recoveryTWRP.blob
and it works
great many thanks, now to try your custom rom
Click to expand...
Click to collapse
Cool, glad you got it sorted.
Just know that you don't need to root first. Root is built into the roms and is not needed to flash.
Also please never try CWM again... From now on if you grab the official TWRP as needed make sure you get the JB version.
gl mate.
Awesome man this worked fine for me, had the same problem I guess koush needs to do his homework on the devices, or I do one..
Hi guys, my phone is Infocus M2 3G and I have rooted it earlier. Now I accidentally removed some services and now getting errors. I want to flash stock rom so it can be like previous one.
I installed ADB and fastboot in my system.
When I tried the command
Code:
fastboot flash recovery recovery.img
the following error came:
Code:
sending 'recovery' (10240 KB)...
OKAY [ 0.417s]
writing 'recovery'...
FAILED (remote:
Security deny - Err:0x2017
)
finished. total time: 0.430s
I searched and I got to know that this may be because of bootloader lock.
So I tried the command
Code:
fastboot oem unlock
and
Code:
fastboot flashing unlock
For oem unlock it showed unknown command and for flashing unlock it showed all options of fastboot.
I installed Rom Manager and select boot into recovery option, it took me to Android Recovery System 3e.
I have stock rom files downloaded and just want to put stock rom in my phone. Any Ideas that can help?
sumit77seo said:
Hi guys, my phone is Infocus M2 3G and I have rooted it earlier. Now I accidentally removed some services and now getting errors. I want to flash stock rom so it can be like previous one.
I installed ADB and fastboot in my system.
When I tried the command
the following error came:
I searched and I got to know that this may be because of bootloader lock.
So I tried the command and
For oem unlock it showed unknown command and for flashing unlock it showed all options of fastboot.
I installed Rom Manager and select boot into recovery option, it took me to Android Recovery System 3e.
I have stock rom files downloaded and just want to put stock rom in my phone. Any Ideas that can help?
Click to expand...
Click to collapse
You can try putting the stock ROM zip file on the root of your sdcard (As in not located in any sub folders) and renaming the ROM file to update.zip then use the stock recovery to flash the ROM. Let me know if you still have questions!
After reflash from 11.2.5.26 to 10.12.3.130 (yes, downgrade) phone stucks on logo. Recovery also doesn't boot - phone goes into fastboot. On try to flash boot or recovery I have:
Code:
D:\Soft\android-sdk-windows\platform-tools>fastboot flash boot D:\ASUS\boot.img
target reported max download size of 1879048192 bytes
sending 'boot' (8052 KB)...
OKAY [ 0.270s]
writing 'boot'...
FAILED (remote: Security is Enable, close 'flash' function !!)
finished. total time: 0.291s
On try to boot from image I have:
Code:
D:\Soft\android-sdk-windows\platform-tools>fastboot boot D:\ASUS\XDA\TWRP.img
downloading 'boot.img'...
OKAY [ 0.398s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.527s
Phone starts to boot with boot.img image from 10.12.3.130 but stucks like in ordinary boot.
Tried to boot from TWRP images for other phones - on old images there's no error but phone stucks. With new images - same error with dtb. As I see, I need recovery from JB version, but I can't find it not among stock on asus.com, nor TWRP or CWM. Another way is to unlock partitions, but I can't find, how I can do this too.
I'll be grateful for any help.
Hello and welcome to XDA Q&A section of the Forums.
I suggest you try to format "boot" and then re-flashing it. Do so by typing "fastboot erase boot", then follow standard procedures for flashing boot. You can even try doing so with the recovery partition and see what happens (I suggest you do this before erasing your boot).
If I helped, hit "thanks" .
RAZERZDAHACKER said:
Hello and welcome to XDA Q&A section of the Forums.
I suggest you try to format "boot" and then re-flashing it. Do so by typing "fastboot erase boot", then follow standard procedures for flashing boot. You can even try doing so with the recovery partition and see what happens (I suggest you do this before erasing your boot).
If I helped, hit "thanks" .
Click to expand...
Click to collapse
Thanks. I didn't write it, but I already erased recovery and then boot and then tried to reflash them in order. No difference, still "Security is Enable, close 'flash' function".
Hello,
I soft-bricked my Padfone A86 when I tried to flash my own kernel using TWRP 2.7.1.1. Before that I was running a rooted Android 5.0.2 (fw version WW-12.4.0.59) with TWRP recovery that I installed like described in an article at padfoneclub.com.
Installing the custom ROM damaged (at least) the boot and recovery partitions. That means I only have access to fastboot which I can not use to flash to those partitions:
Code:
fastboot flash recovery twrp-2.7.1.1-unofficial.img
target reported max download size of 1879048192 bytes
sending 'recovery' (10124 KB)...
OKAY [ 0.321s]
writing 'recovery'...
FAILED (remote: Security is Enable, close 'flash' function !!)
finished. total time: 0.338s
The remote: Security is Enable, close 'flash' function !! error must have been introduced by a patch to the bootloader because I don't recall having this issue when I first flashed TWRP back then when I was running some previous firmware version.
What I can do though is to boot the boot.img (only from fw versions 10.12.3.116 and 10.12.3.130) like this: fastboot boot boot.img
Using saferoot I managed to get root access which enables me to write to the recovery and boot partitions like this:
Code:
dd if=/sdcard/twrp-2.7.1.1-unofficial.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery bs=4096; sync;
Although I can confirm that the memory gets changed using the dd command the bootloader neither loads recovery nor the system on the boot partition.
I looked at a hexdump of the recovery partition and it seems like the only thing stored in it is the TWRP image followed by zeroes. Trying different block sizes didn't help neither.
Confusingly that method seemed to work for some people. Maybe TWRP requires to be written over some stock recovery and can't boot on its own?
I was only able to try to flash the stock recovery for fw versions above 10.12.3.13 as ASUS only included patch-files for the recovery partition before. That didn't work neither. I was assuming that the recovery is running on its own and does not depend on being the same version as the system (or the bootloader). Or might there be something on a different partition that prevents the recovery from working properly?
Booting into recovery results in getting into fastboot mode (fastboot continue doesn't help).
Booting the system stops at the bootloader which shows the error message: ERROR: Can not load Invalid boot image!!
The frustrating thing is that although I seem to have full access to the device memory I still don't manage to fix the recovery partition.
Any help or ideas would be greatly appreciated.
Thunder Storm said:
Hello,
I soft-bricked my Padfone A86 when I tried to flash my own kernel using TWRP 2.7.1.1. Before that I was running a rooted Android 5.0.2 (fw version WW-12.4.0.59) with TWRP recovery that I installed like described in an article at padfoneclub.com.
Installing the custom ROM damaged (at least) the boot and recovery partitions. That means I only have access to fastboot which I can not use to flash to those partitions:
Code:
fastboot flash recovery twrp-2.7.1.1-unofficial.img
target reported max download size of 1879048192 bytes
sending 'recovery' (10124 KB)...
OKAY [ 0.321s]
writing 'recovery'...
FAILED (remote: Security is Enable, close 'flash' function !!)
finished. total time: 0.338s
The remote: Security is Enable, close 'flash' function !! error must have been introduced by a patch to the bootloader because I don't recall having this issue when I first flashed TWRP back then when I was running some previous firmware version.
What I can do though is to boot the boot.img (only from fw versions 10.12.3.116 and 10.12.3.130) like this: fastboot boot boot.img
Using saferoot I managed to get root access which enables me to write to the recovery and boot partitions like this:
Code:
dd if=/sdcard/twrp-2.7.1.1-unofficial.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery bs=4096; sync;
Although I can confirm that the memory gets changed using the dd command the bootloader neither loads recovery nor the system on the boot partition.
I looked at a hexdump of the recovery partition and it seems like the only thing stored in it is the TWRP image followed by zeroes.
Confusingly that method seemed to work for some people. Maybe TWRP requires to be written over some stock recovery and can't boot on its own?
I was only able to try to flash the stock recovery for fw versions above 10.12.3.13 as ASUS only included patch-files for the recovery partition before. That didn't work neither. I was assuming that the recovery is running on its own and does not depend on being the same version as the system (or the bootloader). Or might there be something on a different partition that prevents the recovery from working properly?
Booting into recovery results in getting into fastboot mode (fastboot continue doesn't help).
Booting the system stops at the bootloader which shows the error message: ERROR: Can not load Invalid boot image!!
The frustrating thing is that although I seem to have full access to the device memory I still don't manage to fix the recovery partition.
Any help or ideas would be greatly appreciated.
Click to expand...
Click to collapse
Try getting rid of the bs part. Flash the image at it's normal size.
Sent from my XT1609 using Tapatalk
Thanks for your reply.
I flashed both TWRP and stock recovery without the bs parameter. Same results as before: it doesn't boot into recovery.