Database Info

[Q] Transformer TF101G unable to boot to recovery.

Hi all,
This may sound like an old problem but believe me, it's not. Let me explain.
I've rooted my Transformer TF101G (B90) last year sometime on 3.2.1. This works fine with no issues. I've flashed ClockworkMod after installing ROM Manager. This worked fine, I can boot normally, I can boot to recovery, no problem.
With the latest update available from ASUS via the web, I decided to to allow the annoying icon complaining about upgrading to download and run the upgrade. After downloading the update the Pad rebooted so if to install the new update. This landed me on the CWM with an error message that stated the verification (or something failed). After this, the Transformer wouldn't boot directly to Android, but ended up booting to the recovery partition every time. I had to use the fastboot option to "cold boot" into Android.
This was annoying, so I googled and found the solution on this forum to fix the issue with 5.5.0.4 that kept rebooting to recovery. This solved that problem and I was still able to boot to recovery whenever required.
I decided to update CWM to version 5.8.2.1 via ROM Manager. This seemed to work via ROM Manager, but restarting the transformer and going to recovery showed version 5.5.0.4 still. So I went back to ROM Manager and it showed that it was upgraded to 5.8.2.1. I decided to update this to ClockworkMod Touch by purchasing it via Google market to support the guys that do development on it. This claimed to install also. "Reboot into Recovery" from ROM Manager still showed version 5.5.0.4.
I was now very confused.
So I decided to downgrade CWM from the 5.8.2.1 version it stated was installed to version 5.8.1.9. This worked according to ROM Manager, but rebooting into recovery still showed 5.5.0.4. I mean, WTF!
In the meanwhile the freeken update icon on the task tray still complained about updating Android. I allowed it again to try and update. At the point it rebooted it left me stuck on the "EEE Pad" screen.
Booting up with Vol - and Power takes me to the screen that gives you an option to press Vol + to boot to RCK. Doing so the Pad freezes at "Booting Recovery Kernel Image". My PC then detects USB ADB interface but any adb commands respond with "error: device offline" or "error: device not found".
Booting up with Vol + and Power leaves the screen blank. My PC then detects an USB APX interface. Using "fastboot -i 0x0b05 flash recovery recovery-clockwork-touch-5.8.2.1-tf101.img" only responds with "waiting for device".
The only way to boot my tablet at the moment is to use the "cold boot" option.
I would like to think I've tried everything out there and would appreciated anybody that could point me to maybe something else I could try.
PS: In ROM Manager I get "An error occurred while attempting to run privileged commands" when I use the "Fix Permissions" option.

PeekNPoke said:
PS: In ROM Manager I get "An error occurred while attempting to run privileged commands" when I use the "Fix Permissions" option.
Click to expand...
Click to collapse
Fixed the privileged error by installing Busybox, but still unable to boot to recovery even when reinstalling CWM with the "Erase Recovery" option ticked.

PeekNPoke said:
Fixed the privileged error by installing Busybox, but still unable to boot to recovery even when reinstalling CWM with the "Erase Recovery" option ticked.
Click to expand...
Click to collapse
I had the same problem. It seems the 5.5.0.4 or whatever recovery has borked the transformer. First, I was just in a recovery loop and when I followed how to get out of it, I have no recovery at all now it seems. I need to find a recovery.img and fastboot to manually install it but I can't find a recovery.img that is current.

dragon_76 said:
I had the same problem. It seems the 5.5.0.4 or whatever recovery has borked the transformer. First, I was just in a recovery loop and when I followed how to get out of it, I have no recovery at all now it seems. I need to find a recovery.img and fastboot to manually install it but I can't find a recovery.img that is current.
Click to expand...
Click to collapse
I can't get fastboot to work either. I though I might reinstall ClockworkMod via
fastboot.exe -i 0x0b05 flash recovery recovery-clockwork-touch-5.8.2.1-tf101.img
but it never connects.
Is there no tool that could be used from the adb shell that could re-flash ClockworkMod or even the original recovery (if that is available somewhere)?

PeekNPoke said:
I can't get fastboot to work either. I though I might reinstall ClockworkMod via
fastboot.exe -i 0x0b05 flash recovery recovery-clockwork-touch-5.8.2.1-tf101.img
but it never connects.
Is there no tool that could be used from the adb shell that could re-flash ClockworkMod or even the original recovery (if that is available somewhere)?
Click to expand...
Click to collapse
Same problem here(tf101g): tried to update to ics.... stuck on cwm 5.5.0.4
Resolved problem using: echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
Now i can't access to cwm, even if i update to the last cwm touch....paying...any idea?

recovery
Sorry for my bad english,
I think I have the solution
First invites you down the driver and the nvflsh see appendix are the drivers are too large as a single file
2 go into the apx and the modern transformer connected to the PC
Third drivers instalation
4 instalation nvflasch
then you have a new recovery
This worked for me
ps I have a B60

mmarco80 said:
Same problem here(tf101g): tried to update to ics.... stuck on cwm 5.5.0.4
Resolved problem using: echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
Now i can't access to cwm, even if i update to the last cwm touch....paying...any idea?
Click to expand...
Click to collapse
I've solved The problem whit the gnufabio toolsto install recovery. Then Used "reboot to recovery"
Now i've manually installed official ics ....work fine!

Thomas Cardif said:
Sorry for my bad english,
I think I have the solution
First invites you down the driver and the nvflsh see appendix are the drivers are too large as a single file
2 go into the apx and the modern transformer connected to the PC
Third drivers instalation
4 instalation nvflasch
then you have a new recovery
This worked for me
ps I have a B60
Click to expand...
Click to collapse
I tried this combined with the instructions on android.modaco.com/topic/335416-nvflash-setup-instructions-drivers-links-active because I'd never used nvflash before.
I managed to boot my TF101 in APX-mode, but as soon as I do any nvflash-command (e.g. nvflash --sync) the connection to the TF is lost:
C:\Program Files (x86)\nvflash>nvflash --sync
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
Click to expand...
Click to collapse
After that I have to reboot the TF and shut it down again to be able to go into APX-mode again.
What do I miss? Mine is a B80.

hans_zelf said:
What do I miss? Mine is a B80.
Click to expand...
Click to collapse
You can't use nvflash with a B80

baseballfanz said:
You can't use nvflash with a B80
Click to expand...
Click to collapse
Oops. Fastbook doesn't seem to work either. Any ideas?

Yeah, I can't get fastboot to work either. I still have root access on the device. Is it not possible to flash the recovery from to root prompt on the device?

I tried using ADB. That way I actually can access the device and copy the recovery.img to the device using:
adb push recovery.img /data/local/recovery.img
adb shell
$ su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock2 /system
# cd /system
# cat /data/local/recovery.img > recovery.img
# flash_image recovery recovery.img
Click to expand...
Click to collapse
Works out until the last step. Then I get a message sh: flash_image: not found. Am I missing some files I have to flash first or have I forgotten something else?

Success!
Finally I succeeded!
Flashed recovery using Gnufabio's RecoveryInstaller. (After that the TF101 rebooted itself but still got stuck at the splashscreen. Did a cold Linux-boot).
Opened an ADB-session:
C:\Program Files\...\platform-tools>adb shell
/ # su
/ # echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
5+0 records in
5+0 records out
5 bytes transferred in 0.039 secs (128 bytes/sec)​/ # exit
Click to expand...
Click to collapse
Finally, using ROM-manager I downgraded to CWM 5.5.0.4.
After that I was able to boot into recovery, but not from ROM-manager. I had to hold Vol- but at least I have a working recovery and was able to upgrade to ICS.
I'm not sure if the first step was really necessary but this is how I did it.

Hey hans_zelf,
Wow, I'm glad you got it going. I'll give it a go aswell and give feedback here. By the way, where did you get the recovery.img file you originally tried to flash?

Not really sure. I did a search within the forum and found several img's and zips.
But in the end I didn't need it because both RecoveryInstaller and ROM-manager download their own.

Ok,
I did the following:
adb shell
su
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
exit
Used ROM Manager v5.0.0.6, selected "Erase Recovery" in the settings menu, then flashed ClockworkMod 5.5.0.4, and powered down.
I then tried to start with Vol + and Power, just a blank screen but the 0955:7820 usb driver loaded. Then I used Vol - and Power, it booted to the Eee screen with the blue progress bar, after this is booted normally to the OS.
I powered it down again, and this time booted with Vol - and Power. Got to the screen that says use Vol + to load Recovery. I did that, and Bobs-Your-Uncle !!!!! IT WORKS !!!
Thanks hans_zelf, I'd still be stuck if it wasn't for you !
PS: I think the trick might have been to flash the 5.5.0.4 back, I'm not sure, and I'm not trying this again

You're welcome, but all I really did was combine some very helpfull tips from this forum
In the meantime I flashed my recovery to repacked Touch CWM v5.8.1.8 by Roach2010. Works like a charm. Not only touch support but also keyboard!

Thanks hans_zelf & PeekNPoke. Got my tf101 back into recovery mode from following what you guys said. I had this problem because I upgraded CWM in Rom Manager. Is that what happened to you guys? If so I think this should be stickied because if was a easy mistake and this is the only thread I could find that helped get my recovery back. Thanks again

Yep. Mine was also barked after I upgraded CWM from ROM-Manager.

mike0122 said:
Thanks hans_zelf & PeekNPoke. Got my tf101 back into recovery mode from following what you guys said. I had this problem because I upgraded CWM in Rom Manager. Is that what happened to you guys? If so I think this should be stickied because if was a easy mistake and this is the only thread I could find that helped get my recovery back. Thanks again
Click to expand...
Click to collapse
me too, i've solved whit gnufabio recovery

[q] help please!!!!!

I just got my new asus transformer tf300t-bl and wanted to root and install either twrp or cwm on it,I unlocked it and when i went to reboot it i hit the volume up on the RCK and now its stuck on RCK and it didnt boot into the usb like it says it will on the forums. Now when i reboot it,it says " key driver not found.. booting os android cardhu-user bootloader < 1.00 e> released by "us_epad-10.6.1.8-20130225" a03 starting Fastboot usb download protocol. does anyone know what i can do? i would greatly appreciate ANYONES HELP THAT KNOWS IF THEY'VE DONE THIS TO THEIRS AND IF THIS IS FIXABLE. I USE THIS FOR COLLEGE AND JUST PAID $ 400 and cant afford to buy another one. Somebody please tell me i havent screwed the pooch and that it still can be flashed into recovery and rooted. Thanks you guys. As i rooted and flashed my transform ultra perfectly because of you guys and used the megatron 6 and love it.

No you haven't you need to download fastboot and connect the tablet to your computer, on that screen just let it sit their.
Download the asus firmware. Follow the flashing fastboot guides here. You need to flash the blob file.

flashing recovery/ ref: help me
sevenalive said:
No you haven't you need to download fastboot and connect the tablet to your computer, on that screen just let it sit their.
Download the asus firmware. Follow the flashing fastboot guides here. You need to flash the blob file.
Click to expand...
Click to collapse
im a lil new to doing this so would you please give me a detailed list of exactly what to do. and what firmware do i need to download from asus. And can all of this be done using a mac? and how do i flash it all to my comp. or from it to the tablet.

It should help you :https://www.google.pl/webhp?sourcei....r_qf.&bvm=bv.43828540,d.ZWU&biw=1274&bih=856

need your help plz
Hazard17 said:
It should help you :https://www.google.pl/webhp?sourcei....r_qf.&bvm=bv.43828540,d.ZWU&biw=1274&bih=856
Click to expand...
Click to collapse
i did everything it stated to do and when i get to the last steps to root my tf300t, it says adb cannot run as root in production builds. Im at a loss as to what to do at all. IM a noob, and i follow each command on terminal perfectly and everything executes till the last or itll say permission denied. What do i do or am i doing wrong. Im following the instructions of post forum.xda-developers.com/showthread.php?t=1720980

Hi, I have the exact same error message after installing the latest firmware from asus (ww_epad-10.6.1.8-20130225) and flashing cwm recovery.
Flashing via fastboot works fine and I have already reflashed the blob file and reflashed cwm recovery. still the same issue: "Key driver not found" and upon chosing entering RCK it freezes. OS boots fine, no issue here. Any clues? Should I flash the stock kernel from Asus?

re: help me
philmg said:
Hi, I have the exact same error message after installing the latest firmware from asus (ww_epad-10.6.1.8-20130225) and flashing cwm recovery.
Flashing via fastboot works fine and I have already reflashed the blob file and reflashed cwm recovery. still the same issue: "Key driver not found" and upon chosing entering RCK it freezes. OS boots fine, no issue here. Any clues? Should I flash the stock kernel from Asus?
Click to expand...
Click to collapse
how did you flash fastboot and cwm and reflashed the blob files to your asus? on my terminal on my mac itll say cant execute root on production models and requests a password. Have you had the same problems? can u give me a step by step how u flashed cwm and fastboot and the blob files. and how did you install the latest firmware

420Misfit said:
how did you flash fastboot and cwm and reflashed the blob files to your asus? on my terminal on my mac itll say cant execute root on production models and requests a password. Have you had the same problems? can u give me a step by step how u flashed cwm and fastboot and the blob files. and how did you install the latest firmware
Click to expand...
Click to collapse
well, I am using a win xp machine for fastboot. so I don't have the same issues. fastboot works fine, so that I use the normal fastboot process to flash the system and the recovery kernel.
I finally got it to work again by flashing the newest TWRP instead of CWM. It seems CWM does not yet work on the latest firmware.
I followed this guide for flashing TWRP with fastboot. This version actually also just asked me, if I want to root the device, I clicked yes and it was rooted. Perfect.
http://forum.xda-developers.com/showthread.php?t=2187982

philmg said:
Hi, I have the exact same error message after installing the latest firmware from asus (ww_epad-10.6.1.8-20130225) and flashing cwm recovery.
Flashing via fastboot works fine and I have already reflashed the blob file and reflashed cwm recovery. still the same issue: "Key driver not found" and upon chosing entering RCK it freezes. OS boots fine, no issue here. Any clues? Should I flash the stock kernel from Asus?
Click to expand...
Click to collapse
I am in EXACTLY the same boat as you. The only difference is that I flashed TWRP instead of CWM. I finally decided that it was time to root my tablet...got tired of the lag. IIRC I've gotten the "key driver not found.. booting OS" error message since doing the OTA update to 4.2 (I did this prior to rooting.) Everything SEEMS to be working okay, but this bugs the heck outta me, and I'm sure it can't be a good thing. Hoping somebody will chime in with a fix for this. I've searched and searched to no avail.

[Q] Brick - Can't get cold boot / broken cwm

NB/EDIT : I am pretty sure this is due to cmupdater requiring "next boot" to recovery. Is there any way to get through this?
NB/ EDIT : Now, I can cold boot. But the flash (DD/ fastboot seems not be working. hope better news next hours).
Dear all,
I've googled this unsuccessfully and haven't found any reference in the forum to that combination of two issues...
I have flashed through CWM on my TF700T the 10.6.1.14.4 bootloader. I was previously on CM10.0 stable.
Then, don't ask me why, I tried directly from cmupdater to update to the CM10.1 nightly.
But it seems that my CWM is broken saying
"E:Can't mount /cache/recovery/command"
"E:Can't mount /cache/recovery/log"
etc...
And I can't even get a cold boot since it seems cmupdater will always point to recovery...
Do you have any ideas or reference?
Thank you a lot...

http://forum.xda-developers.com/showthread.php?t=2287892
Are you using the button method or the power menu to access recovery? Read the above, may help.
florck said:
Dear all,
I've googled this unsuccessfully and haven't found any reference in the forum to that combination of two issues...
I have flashed through CWM on my TF700T the 10.6.1.14.4 bootloader. I was previously on CM10.0 stable.
Then, don't ask me why, I tried directly from cmupdater to update to the CM10.1 nightly.
But it seems that my CWM is broken saying
"E:Can't mount /cache/recovery/command"
"E:Can't mount /cache/recovery/log"
etc...
And I can't even get a cold boot since it seems cmupdater will always point to recovery...
Do you have any ideas or reference?
Thank you a lot...
Click to expand...
Click to collapse

Thank you elfaure, but I'm not really sure understanding.
I had a fully functional CM10.0 on my tablet. Then I used CWM to flash the newer boot loader and reboot.
Once I was in the system, through parameter, i requested an update of CM to 10.1 nightly.
It rebooted my tablet, and then, entered the CWM, but with the error messages I printed above.
Now, if I try a hard stop (power + volume up) and then a cold boot (power + volume down) then it doens't propose me the options, but directly goes to CWM. And in CWM, I can't move up and down in the menu, neither with my volume keys nor my finger. The only I can do is use power to reboot and then it come again and again to that broken cwm... Please tell me I don't need to return the tablet...
elfaure said:
http://forum.xda-developers.com/showthread.php?t=2287892
Are you using the button method or the power menu to access recovery? Read the above, may help.
Click to expand...
Click to collapse

florck said:
Thank you elfaure, but I'm not really sure understanding.
I had a fully functional CM10.0 on my tablet. Then I used CWM to flash the newer boot loader and reboot.
Once I was in the system, through parameter, i requested an update of CM to 10.1 nightly.
It rebooted my tablet, and then, entered the CWM, but with the error messages I printed above.
Now, if I try a hard stop (power + volume up) and then a cold boot (power + volume down) then it doens't propose me the options, but directly goes to CWM. And in CWM, I can't move up and down in the menu, neither with my volume keys nor my finger. The only I can do is use power to reboot and then it come again and again to that broken cwm... Please tell me I don't need to return the tablet...
Click to expand...
Click to collapse
Please take what I say here with a grain of salt as I have no experience with custom ROMs or custom recoveries. But your one saving grace I think would be if you left ADB enabled on your device and have already upgraded your SDK for privileged ADB connections [required for 4.2 only] (if not then you can still do this from the PC end).
If you can get into ADB then I would think you can fix it. If not, then I think you are bricked. From ADB you can push a new ROM or recovery.
http://forum.xda-developers.com/showthread.php?t=1667929
http://blog.twimager.com

elfaure said:
Please take what I say here with a grain of salt as I have no experience with custom ROMs or custom recoveries. But your one saving grace I think would be if you left ADB enabled on your device and have already upgraded your SDK for privileged ADB connections [required for 4.2 only] (if not then you can still do this from the PC end).
If you can get into ADB then I would think you can fix it. If not, then I think you are bricked. From ADB you can push a new ROM or recovery.
http://forum.xda-developers.com/showthread.php?t=1667929
http://blog.twimager.com
Click to expand...
Click to collapse
It seems I can't connect ADB as ClockWorkMod is running. But... I can't get anything else running...
I arrived to control with the physical keyboard the CWM, but can't do anything, since neither external nor internal sdcard is recognized...

florck said:
It seems I can't connect ADB as ClockWorkMod is running. But... I can't get anything else running...
I arrived to control with the physical keyboard the CWM, but can't do anything, since neither external nor internal sdcard is recognized...
Click to expand...
Click to collapse
At least with TWRP, a connection via adb shell is possible - either on Linux, or on Windows using the correct driver. I don't know about CWM though.

_that said:
At least with TWRP, a connection via adb shell is possible - either on Linux, or on Windows using the correct driver. I don't know about CWM though.
Click to expand...
Click to collapse
Unfortunately, i don't have twrp... I can't see the solution here... :crying:

florck said:
Unfortunately, i don't have twrp... I can't see the solution here... :crying:
Click to expand...
Click to collapse
Why doesn't adb work? Can you see any USB device on your computer?

_that said:
Why doesn't adb work? Can you see any USB device on your computer?
Click to expand...
Click to collapse
Oh ! I got and ADB shell.
but when I "ls /dev/block", I only get
loop0
loop1
loop2
loop3
loop4
loop5
loop6
loop7
mmcblk0
mmcblk0p1
mmcblk0p3
platform
Am not I missing some mmcblk0pX?
What should I do ? How can I flash recovery if no mmcblk0p4?

florck said:
Am not I missing some mmcblk0pX?
What should I do ? How can I flash recovery if no mmcblk0p4?
Click to expand...
Click to collapse
This looks like a hard brick. But I have one more idea that you can try:
Download this file and unzip it: View attachment bootit.zip
Then push it to your device:
Code:
adb push bootit.ko /
and run insmod on it:
Code:
adb shell
insmod /bootit.ko
If you are very lucky, your tablet should instantly reboot into Android.

_that said:
This looks like a hard brick. But I have one more idea that you can try:
Download this file and unzip it: View attachment 1985914
Then push it to your device:
Code:
adb push bootit.ko /
and run insmod on it:
Code:
adb shell
insmod /bootit.ko
If you are very lucky, your tablet should instantly reboot into Android.
Click to expand...
Click to collapse
Thank you a lot, but i was not very lucky.
It rebooted to the cwm once again.
I wanted also to share that strange point : my adb device name is 0123456789ABCDEF ...
Other ideas ? Way to try flashing a full system?

florck said:
Thank you a lot, but i was not very lucky.
It rebooted to the cwm once again.
I wanted also to share that strange point : my adb device name is 0123456789ABCDEF ...
Other ideas ? Way to try flashing a full system?
Click to expand...
Click to collapse
The funny serial number is normal for the recovery.
Try the procedure again and hold down volume-left immediately after pressing "Enter" in adb shell on the insmod command. Maybe you can get to the bootloader menu. If not, I'll try to build another kernel module.

That's so kind of you...
even holding the button volume left didn't worked.
I will send to you my jabber through MP if you do aggree to get this easyer. I promise if this works to make the full summary here.

florck said:
That's so kind of you...
even holding the button volume left didn't worked.
I will send to you my jabber through MP if you do aggree to get this easyer. I promise if this works to make the full summary here.
Click to expand...
Click to collapse
I don't use Jabber or Google Talk, but I have only one idea left anyway... try this module:
View attachment bootit-bootloader.zip
Same procedure as above (unzip, adb push, insmod). It should reboot into the bootloader, from which you can use fastboot if it worked. If not, I declare your tablet finally bricked.

_that said:
I don't use Jabber or Google Talk, but I have only one idea left anyway... try this module:
View attachment 1985941
Same procedure as above (unzip, adb push, insmod). It should reboot into the bootloader, from which you can use fastboot if it worked. If not, I declare your tablet finally bricked.
Click to expand...
Click to collapse
You're a genius, I can now fastboot and / or cold boot. When I cold boot I have my fully functional previous android. But unfortunately, with flashing with dd on block 4 the cwm, at reboot, i have exactly the same as before...
do you have a link to another bootloader ? or a way to directly flash something else ?
How can I deactivate once booted to android the fact that it boot first to bootloader?

florck said:
You're a genius, I can now fastboot and / or cold boot.
Click to expand...
Click to collapse
That's good news - until today your situation was considered an unrecoverable hard brick.
florck said:
But unfortunately, with flashing with dd on block 4 the cwm, at reboot, i have exactly the same as before...
do you have a link to another bootloader ? or a way to directly flash something else ?
How can I deactivate once booted to android the fact that it boot first to bootloader?
Click to expand...
Click to collapse
I don't know - I would now flash TWRP 2.5 via fastboot, make a backup, wipe data, and reinstall a ROM.

_that said:
That's good news - until today your situation was considered an unrecoverable hard brick.
I don't know - I would now flash TWRP 2.5 via fastboot, make a backup, wipe data, and reinstall a ROM.
Click to expand...
Click to collapse
Can I just be a very bad student? Can I request references to other pages and to the zip i should flash? I really fear doing another stupid action...

florck said:
Can I just be a very bad student? Can I request references to other pages and to the zip i should flash? I really fear doing another stupid action...
Click to expand...
Click to collapse
Get the TWRP blob and instructions for fastboot here: http://teamw.in/project/twrp2/105
Here's the official CM thread: http://forum.xda-developers.com/showthread.php?t=1957660
and here is the place to ask questions about it: http://forum.xda-developers.com/showthread.php?t=2249461

_that said:
That's good news - until today your situation was considered an unrecoverable hard brick.
I don't know - I would now flash TWRP 2.5 via fastboot, make a backup, wipe data, and reinstall a ROM.
Click to expand...
Click to collapse
_that said:
Get the TWRP blob and instructions for fastboot here: http://teamw.in/project/twrp2/105
Here's the official CM thread: http://forum.xda-developers.com/showthread.php?t=1957660
and here is the place to ask questions about it: http://forum.xda-developers.com/showthread.php?t=2249461
Click to expand...
Click to collapse
Hum... Unfortunately, this is not finished. When I flash through ADB or flashboot twrp, it changes nothing. I even tried a "fastboot boot" and got
C:\adb>fastboot boot recovery-jb-touch.img
creating boot image...
creating boot image - 7542784 bytes
downloading 'boot.img'...
OKAY [ 1.310s]
booting...
FAILED (remote: ()
finished. total time: 1.342s
I'm so frustrated...

florck said:
Hum... Unfortunately, this is not finished. When I flash through ADB or flashboot twrp, it changes nothing. I even tried a "fastboot boot" and got
C:\adb>fastboot boot recovery-jb-touch.img
creating boot image...
creating boot image - 7542784 bytes
downloading 'boot.img'...
OKAY [ 1.310s]
booting...
FAILED (remote: ()
finished. total time: 1.342s
I'm so frustrated...
Click to expand...
Click to collapse
Any other idea ? Something to flash in other blocks?

[Q] Power on/Reboot now goes into APX mode

Sorry, I'd thought I'd posted under Q&A/Help. Not sure if a moderator can move it where it belongs?
My tf300t (ICS v9.3.4.17) is unlocked, rooted, and has TWRP 2.6.3.0 installed. I also have created the nvflash backups so it's currently running on the AndroidRoot v9.4.3.30r01 bootloader. I've stayed with
ICS and not updated anything except TWRP, but was just about to update to either ICS v9.4.3.30 or jump and install the latest JB.
Earlier today I went into Terminal Emulator, typed su and reboot as I've always done. I thought my tablet had shutdown because the screen stayed blank. I tried the power button and nothing so thought
maybe my power button had given out. I then tried plugging in the charging/usb cable which normally would get it to boot and again blank screen. Last I tried connecting to my pc and found it was in
APX mode. I'm able to boot up from nvflash and function normally but I'm stuck once I shut off the tablet from ICS (have to rerun nvflash to boot up again).
When I power off from APX mode, it automatically restarts back into APX mode. I was able to get into TWRP and tried restoring my latest nandroid (System, Data, Recovery, & Boot partitions) but no
change. Also tried a factory reset but same results - booting into APX yet again...
Ack, at this point I'm about ready to punt. I have my backups (TB & Helium) and am thinking of trying to update to v9.4.3.30 to see if this clears up booting into APX mode. To do this, can I just install the single
zip using TWRP & then re-flash TWRP using adb (or fastboot assuming I get it back)? Or do it via nvflash? If by nvflash, are these the correct commands after unpacking the v9.4.3.30 blob:
nvflash -r --download 4 blob.EBT
nvflash -r --download 10 blob.APP
nvflash -r --download 6 blob.LNX
Thoughts or ideas are really appreciated!

APX Mode
wha2do said:
My tf300t (ICS v9.3.4.17) is unlocked, rooted, and has TWRP 2.6.3.0 installed. I also have created the nvflash backups so it's currently running on the AndroidRoot v9.4.3.30r01 bootloader. I've stayed with
ICS and not updated anything except TWRP, but was just about to update to either ICS v9.4.3.30 or jump and install the latest JB.
Earlier today I went into Terminal Emulator, typed su and reboot as I've always done. I thought my tablet had shutdown because the screen stayed blank. I tried the power button and nothing so thought
maybe my power button had given out. I then tried plugging in the charging/usb cable which normally would get it to boot and again blank screen. Last I tried connecting to my pc and found it was in
APX mode. I'm able to boot up from nvflash and function normally but I'm stuck once I shut off the tablet from ICS (have to rerun nvflash to boot up again).
When I power off from APX mode, it automatically restarts back into APX mode. I was able to get into TWRP and tried restoring my latest nandroid (System, Data, Recovery, & Boot partitions) but no
change. Also tried a factory reset but same results - booting into APX yet again...
Ack, at this point I'm about ready to punt. I have my backups (TB & Helium) and am thinking of trying to update to v9.4.3.30 to see if this clears up booting into APX mode. To do this, can I just install the single
zip using TWRP & then re-flash TWRP using adb (or fastboot assuming I get it back)? Or do it via nvflash? If by nvflash, are these the correct commands after unpacking the v9.4.3.30 blob:
nvflash -r --download 4 blob.EBT
nvflash -r --download 10 blob.APP
nvflash -r --download 6 blob.LNX
Thoughts or ideas are really appreciated!
Click to expand...
Click to collapse
WoW that is an old bootloder..... v9.3.4.17 What is the SKU of that bootloader??
Enter APX mode and bootstrap in, If thats the ways its done.. I don't know because, I did my nvflash after jb came out...Run this command
Code:
nvflash -r --go
It will not reboot your tablet but it is supposed to let the bootloader resume on go which should be the next boot....
Just long hold your power button and let your tablet boot normally... Let me know if this helps at all... Thx lj
O yeah just be aware that the newest version of TWRP is having some issues... Just a FYI

lj50036 said:
WoW that is an old bootloder..... v9.3.4.17 What is the SKU of that bootloader??
Enter APX mode and bootstrap in, If thats the ways its done.. I don't know because, I did my nvflash after jb came out...Run this command
Code:
nvflash -r --go
It will not reboot your tablet but it is supposed to let the bootloader resume on go which should be the next boot....
Just long hold your power button and let your tablet boot normally... Let me know if this helps at all... Thx lj
O yeah just be aware that the newest version of TWRP is having some issues... Just a FYI
Click to expand...
Click to collapse
Thanks for the reply. The bootloader is the original one loaded when I created the nvflash backups. When rebooting from nvflash and holding the vol down button, I see:
Android cardhu-user bootloader <2.10 e> released by "WW_epad-9.4.3.30-20120206"
This had to have been universal for all that ran it way back when, though the SKU on my tablet is US (US_epad-9.4.3.2012...) and no real issues in over the year I've had it.
The nvflash -r --go command is the same as nvflash --resume --go...both reboot the device (nvflash help verifies they're the same).
------> Back to the issue at hand *sigh* <-----
So... I'm still having to reboot from APX mode using nvflash and hold the volume down button. At that point I can either enter TWRP or leave it go and it'll cold boot - no icons
display for fastboot, etc. It just shows:
Platform Pre OS boot configuration...
Cold-booting Linux
And then it will boot into ICS, though found it may just go back into APX mode again. It can take several tries, but it'll finally boot properly.
Sooo...what's my next step? Have noticed TWRP 2.6.3.0 seems to be a bit flaky in the past. Should I try installing US_epad-user-9.4.3.30.zip using TWRP? I have
OTA Rootkeeper installed with SuperSU so root should either remain or be restorable (fingers crossed). Or do I need to use nvflash to flash each partition? Or finally go
back to my original nvflash blobs? I really don't want to move forward and screw up something worse than it is!
Side note: I've tried to install tried & true TWRP v2.3.1.0. Using adb, it appears to flash successfully, I reboot into ICS, and then nvflash boot into TWRP - but I'm still
on v2.6.3.0. Possibly not rebooting smoothly into ICS isn't allowing the img file to take? For now will deal continue using my installed version v2.6.3.0 I guess...
Thanks for direction on where to go next! And if can, spell out my steps to take in detail (sometimes I may be a tad dense and don't mind any eyestrain, lol).

wha2do said:
Thanks for the reply. The bootloader is the original one loaded when I created the nvflash backups. When rebooting from nvflash and holding the vol down button, I see:
Android cardhu-user bootloader <2.10 e> released by "WW_epad-9.4.3.30-20120206"
This had to have been universal for all that ran it way back when, though the SKU on my tablet is US (US_epad-9.4.3.2012...) and no real issues in over the year I've had it.
The nvflash -r --go command is the same as nvflash --resume --go...both reboot the device (nvflash help verifies they're the same).
------> Back to the issue at hand *sigh* <-----
So... I'm still having to reboot from APX mode using nvflash and hold the volume down button. At that point I can either enter TWRP or leave it go and it'll cold boot - no icons
display for fastboot, etc. It just shows:
Platform Pre OS boot configuration...
Cold-booting Linux
And then it will boot into ICS, though found it may just go back into APX mode again. It can take several tries, but it'll finally boot properly.
Sooo...what's my next step? Have noticed TWRP 2.6.3.0 seems to be a bit flaky in the past. Should I try installing US_epad-user-9.4.3.30.zip using TWRP? I have
OTA Rootkeeper installed with SuperSU so root should either remain or be restorable (fingers crossed). Or do I need to use nvflash to flash each partition? Or finally go
back to my original nvflash blobs? I really don't want to move forward and screw up something worse than it is!
Side note: I've tried to install tried & true TWRP v2.3.1.0. Using adb, it appears to flash successfully, I reboot into ICS, and then nvflash boot into TWRP - but I'm still
on v2.6.3.0. Possibly not rebooting smoothly into ICS isn't allowing the img file to take? For now will deal continue using my installed version v2.6.3.0 I guess...
Thanks for direction on where to go next! And if can, spell out my steps to take in detail (sometimes I may be a tad dense and don't mind any eyestrain, lol).
Click to expand...
Click to collapse
Ok so you are 100% sure that you have had a US SKU version bootloader from when you got it new????
Where are you getting the firmware zip file from??
And you think this all started because of a wrong recovery flash???

lj50036 said:
Ok so you are 100% sure that you have had a US SKU version bootloader from when you got it new????
Where are you getting the firmware zip file from??
And you think this all started because of a wrong recovery flash???
Click to expand...
Click to collapse
Thanks for the quick reply... I'm positive on the US SKU - I have a screenshot I took of the SW info when it was brand new - here it is:
http://i1331.photobucket.com/albums...delampSWinfo-2012-11-25-07-29_zps27ba6fc6.jpg
As for the earlier firmware zips I've got, they were provided in one of the XDA posts - possibly this one: http://forum.xda-developers.com/showpost.php?p=33883254&postcount=3
Nope, it just suddenly started while using the tablet normally. No flashing, restoring nandroids, etc in at least a week or two. I was playing one of my games on the tablet and sometimes the graphics will act
funny or it'll fc on me. So I either do a cold restart or reboot using Terminal Emulator to get the behaving normally again. In this case I rebooted using Android Terminal and suddenly only had a black
screen. Finally realized it wasn't powered down but was going into APX mode... Sorry, just tried flashing the older version of TWRP I'd always used since v2.6.3.0 has been flaky off and on. V2.6.3.0 was
originally flashed about 2-3 weeks ago and I'll just stick with it while working on fixing this!
The only thing I can think which may be unrelated. My daughter loaded a non-market game that was tagged as having Android:Fujacks by Avast! Being non-market, maybe foolishly? I let Avast
uninstall it. But I'm almost positive I rebooted a few times after without any issues. Also restoring an earlier nandroid didn't help, so don't think it's the system or data partitions messed up. Could it
be the boot partition that's gone funky?
That's why I'm wondering if an "upgrade" to v9.4.3.30 would clear this up - and if so, best/safest way to do it? Hope that helps fill in a little more!

wha2do said:
Thanks for the quick reply... I'm positive on the US SKU - I have a screenshot I took of the the SW info when it was brand new - here it is:
http://i1331.photobucket.com/albums...delampSWinfo-2012-11-25-07-29_zps27ba6fc6.jpg
As for the earlier firmware zips I've got, they were provided in one of the XDA posts - possibly this one: http://forum.xda-developers.com/showpost.php?p=33883254&postcount=3
Nope, it just suddenly started without having done any flashing or restoring nandroids. I was playing one of my games on the tablet and sometimes the graphics will act
funny or it'll fc on me. So I either do a cold restart or reboot using Terminal Emulator to get it back to normal. In this case I rebooted using Android Terminal and suddenly
a black screen. Finally realized it wasn't powered down but was going into APX mode.
The only thing I can think which may be unrelated. My daughter loaded a non-market game that was tagged as having Android:Fujacks by Avast! Being non-market, maybe
foolishly? I let Avast uninstall it. But I'm almost positive I rebooted a few times after without any issues. Also restoring an earlier nandroid didn't help, so don't think it's the system
or data partitions messed up. Could it be the boot partition that's gone funky?
That's why I'm wondering if an "upgrade" to v9.4.3.30 would clear this up - and if so, best/safest way to do it? Hope that helps fill in a little more!
Click to expand...
Click to collapse
Ok the .30 zip from them what is inside the zip??

lj50036 said:
Ok the .30 zip from them what is inside the zip??
Click to expand...
Click to collapse
It's the normal Stock v9.4.3.30 update from ASUS. It's the "US_epad-user-9.4.3.30.zip" which in turn contains the META-INF folder and the blob file. The blob file contains:
blob.APP ; system img
blob.EBT ; bootloader.bin
blob.LNX ; boot img
blob.PT ; partition table I presume
blob.SOS ; stock recovery img
The blob names are exact and I think I have each identified as to their purpose going from old notes. EBT, APP, and LNX are the three that I believe could/would be flashed using nvflash
if necessary (if can't just install the full update zip & reinstall TWRP over the stock recovery)...
Is that what you're looking for?

wha2do said:
It's the normal Stock v9.4.3.30 update from ASUS. It's the "US_epad-user-9.4.3.30.zip" which in turn contains the META-INF folder and the blob file. The blob file contains:
blob.APP ; system img
blob.EBT ; bootloader.bin
blob.LNX ; boot img
blob.PT ; partition table I presume
blob.SOS ; stock recovery img
The blob names are exact and I think I have each identified as to their purpose going from old notes. EBT, APP, and LNX are the three that I believe could/would be flashed using nvflash
if necessary (if can't just install the full update zip & reinstall TWRP over the stock recovery)...
Is that what you're looking for?
Click to expand...
Click to collapse
Ok so it just a blob binary and a META-INF folder in the zip??

lj50036 said:
Ok so it just a blob binary and a META-INF folder in the zip??
Click to expand...
Click to collapse
Yep...standard update zip inside a zip that comes from ASUS.

wha2do said:
Yep...standard update zip inside a zip that comes from ASUS.
Click to expand...
Click to collapse
We need to get to fastboot and verify that we can see your devices boot into the bootloader screen.. As I recall you should have a
usb icon you must select to enable fastboot... Can you get to this point??

lj50036 said:
We need to get to fastboot and verify that we can see your devices boot into the bootloader screen.. As I recall you should have a
usb icon you must select to enable fastboot... Can you get to this point??
Click to expand...
Click to collapse
No, the icons one normally sees are missing/not available to be selected. When I reboot from nvflash & hold the vol down button, I only have two options. Volume up to enter TWRP as expected, or it begins cold booting. Guess that got lost in my lengthy message above:
So... I'm still having to reboot from APX mode using nvflash and hold the volume down button. At that point I can either enter TWRP or leave it go and it'll cold boot - no icons
display for fastboot, etc. It just shows:
Platform Pre OS boot configuration...
Cold-booting Linux
And then it will boot into ICS, though found it may just go back into APX mode again. It can take several tries, but it'll finally boot properly.
Click to expand...
Click to collapse
So unfortunately, no fastboot - only ADB, APX, and Recovery (TWRP) modes available.

wha2do said:
No, the icons one normally sees are missing/not available to be selected. When I reboot from nvflash & hold the vol down button, I only have two options. Volume up to enter TWRP as expected, or it begins cold booting. Guess that got lost in my lengthy message above:
So unfortunately, no fastboot - only ADB, APX, and Recovery (TWRP) modes available.
Click to expand...
Click to collapse
Ok well we need a different version of twrp than what your on now I would highly recommend a version older that what your on now.. as the newer twrps are buggy 2.5.5.0 is a solid one... Make sure you get the one for your tablet...as there are a few different versions... Than rename it
Code:
twrp.blob
Make sure you don't rename it twrp.blob.blob as windows is good at doing still stuff like that.....
Move your twrp.blob to the root of your c drive than open a command window as admin and type
Code:
cd /
This will move you to the root of your c drive in your command window than type
Code:
dir
This will list all the files and folder in the root of your c drive make sure you see the twrp.blob if so your ready
Boot your tablet into APX mode bootstrap into nvflash mode and type
Code:
nvflash -r --download 5 twrp.blob
The output of this will look something like this
Code:
Nvflash v1.13.87205 started
[resume mode]
sending file: twrp.blob
- 8165480/8165480 bytes sent
twrp.blob sent successfully
Than
Code:
nvflash -r --go
Then try to enter recovery...
Let me know

lj50036 said:
Ok well we need a different version of twrp than what your on now I would highly recommend a version older that what your on now.. as the newer twrps are buggy 2.5.5.0 is a solid one... Make sure you get the one for your tablet...as there are a few different versions... Than rename it
Code:
twrp.blob
Make sure you don't rename it twrp.blob.blob as windows is good at doing still stuff like that.....
Move your twrp.blob to the root of your c drive than open a command window as admin and type
Code:
cd /
This will move you to the root of your c drive in your command window than type
Code:
dir
This will list all the files and folder in the root of your c drive make sure you see the twrp.blob if so your ready
Boot your tablet into APX mode bootstrap into nvflash mode and type
Code:
nvflash -r --download 5 twrp.blob
The output of this will look something like this
Code:
Nvflash v1.13.87205 started
[resume mode]
sending file: twrp.blob
- 8165480/8165480 bytes sent
twrp.blob sent successfully
Than
Code:
nvflash -r --go
Then try to enter recovery...
Let me know
Click to expand...
Click to collapse
Ok - picked up v2.5.0.0 (don't see a v2.5.5.0 on the TWRP website) and successfully installed the .blob file but... As soon as I hit the volume up button it went to cold boot instead. I remembered with the Prime that for some reason, the TWRP img file format needed to be used when on the AndroidRoot bootloader. So long story short, got the img file installed and I have TWRP 2.5.0.0 running at the moment.
So where to next? And thanks so far

wha2do said:
Ok - picked up v2.5.0.0 (don't see a v2.5.5.0 on the TWRP website) and successfully installed the .blob file but... As soon as I hit the volume up button it went to cold boot instead. I remembered with the Prime that for some reason, the TWRP img file format needed to be used when on the AndroidRoot bootloader. So long story short, got the img file installed and I have TWRP 2.5.0.0 running at the moment.
So where to next? And thanks so far
Click to expand...
Click to collapse
So you can get into recovery now??? if so, take the double zipped firmware......unzip it one time and the zip that is made move to.....O
Do you have a way to put that zip on an sdcard so we can get it on your tablet?? If not no big deal.... Just let me know if you can make that happen.....

lj50036 said:
So you can get into recovery now??? if so, take the double zipped firmware......unzip it one time and the zip that is made move to.....O
Do you have a way to put that zip on an sdcard so we can get it on your tablet?? If not no big deal.... Just let me know if you can make that happen.....
Click to expand...
Click to collapse
Sorry, I get over wordy (lol)... Yes, I have TWRP 2.5.0.0 installed and was able to get in. I'd already prepared for this - have the unzipped (once) file sitting in my tablet's root folder (/sdcard). Checked and checksum matched so it transferred without errors (used Airdroid, in case wondering).
Took a few extra minutes - wanted double check all was there as I thought. So yes, have the v9.4.3.30 zipfile (containing META files & blob) on tablet's "root" directory. Currently in TWRP v2.5.0.0 and ready to install it (figuring that's the next step)...
Just give me the greenlight, lol

One thing doing quickly is making a nandroid - never can be too safe, heh! Should be about another 5 minutes...

wha2do said:
One thing doing quickly is making a nandroid - never can be too safe, heh! Should be about another 5 minutes...
Click to expand...
Click to collapse
No worries at all you take your time.... Let me know....

lj50036 said:
No worries at all you take your time.... Let me know....
Click to expand...
Click to collapse
Good to go!

wha2do said:
Good to go!
Click to expand...
Click to collapse
??????

Still here - at this point have the zipfile unzipped once, on the tablet's root directory, and TWRP v2.5.0.0 installed. I assume going to install the zip file via TWRP Install? Tablet's got plenty of battery charge so good to go - just let me know!

[Q] Fastboot Brick (CM11 v.12)

Hi, I rooted my Froyo 2.2 Optimus One (LG-P500) with z4root (http://forum.xda-developers.com/showthread.php?t=833953) then I installed CWM with ROM manager.
I installed CM11 v.12 (http://forum.xda-developers.com/showthread.php?t=2589303) following AROMA installer steps; I rebooted my phone and I saw this:
http://3.bp.blogspot.com/-nl2aGm8NgoI/T4qw9y80_cI/AAAAAAAADvQ/w5IbpEFH-Yk/s1600/IMG_3388.JPG
I read this guide to unbrick the phone (http://forum.xda-developers.com/showthread.php?t=1088046&page=9) but it seems for people that have bricked their recovery while I can correctly run it. Have I to follow this guide anyway? Then? Where I'm wrong?
Thank you all!

steve281188 said:
Hi, I rooted my Froyo 2.2 Optimus One (LG-P500) with z4root (http://forum.xda-developers.com/showthread.php?t=833953) then I installed CWM with ROM manager.
I installed CM11 v.12 (http://forum.xda-developers.com/showthread.php?t=2589303) following AROMA installer steps; I rebooted my phone and I saw this:
http://3.bp.blogspot.com/-nl2aGm8NgoI/T4qw9y80_cI/AAAAAAAADvQ/w5IbpEFH-Yk/s1600/IMG_3388.JPG
I read this guide to unbrick the phone (http://forum.xda-developers.com/showthread.php?t=1088046&page=9) but it seems for people that have bricked their recovery while I can correctly run it. Have I to follow this guide anyway? Then? Where I'm wrong?
Thank you all!
Click to expand...
Click to collapse
Still can run recovery? Did you do a backup before attempting any of this? If so, restore it. If not, well, live and learn

Recovery is ok
Dovidhalevi said:
Still can run recovery? Did you do a backup before attempting any of this? If so, restore it. If not, well, live and learn
Click to expand...
Click to collapse
As I wrote, recovery is working fine; unfortunately, I have no backup.
EDIT: I tried flashing CM11-v.11, no way. Is the problem what I flash? Or it's nothing to do about it? (I'm thinking about flashing stock rom)

steve281188 said:
As I wrote, recovery is working fine; unfortunately, I have no backup.
Click to expand...
Click to collapse
Know for the next time
Here is a backkup of a older ROM http://forum.xda-developers.com/showthread.php?t=2711770
This runs new baseband. If you still have old baseband, find the old baseband fix and flash afterwards or adb push the three files to /system/lib/. No need to even reboot in this case.

CM10
Dovidhalevi said:
Know for the next time
Here is a backkup of a older ROM http://forum.xda-developers.com/showthread.php?t=2711770
This runs new baseband. If you still have old baseband, find the old baseband fix and flash afterwards or adb push the three files to /system/lib/. No need to even reboot in this case.
Click to expand...
Click to collapse
Thanks!
What if I just flash this? (http://forum.xda-developers.com/showthread.php?t=1811325)

steve281188 said:
Thanks!
What if I just flash this? (http://forum.xda-developers.com/showthread.php?t=1811325)
Click to expand...
Click to collapse
Can certainly try it. Newer ROMs do work better than this, however. If you were on Froyo, you will need the old baseband fix for any of these ROMs. It's OK, I use it myself.
Note that for KitKat, you need the newer recovery Clockwork 6.0.4.8. For others, the older 6.0.2.7, etc.
Maybe get your phone working again with that backkup before trying any other ROMs.

CWM
Dovidhalevi said:
Can certainly try it. Newer ROMs do work better than this, however. If you were on Froyo, you will need the old baseband fix for any of these ROMs. It's OK, I use it myself.
Note that for KitKat, you need the newer recovery Clockwork 6.0.4.8. For others, the older 6.0.2.7, etc.
Maybe get your phone working again with that backkup before trying any other ROMs.
Click to expand...
Click to collapse
OK thanks! I notice now that ROM manager installed me a 5.0.2.0 CWM recovery! Is this the problem?
How can I upgrade it?
Regards

steve281188 said:
OK thanks! I notice now that ROM manager installed me a 5.0.2.0 CWM recovery! Is this the problem?
How can I upgrade it?
Regards
Click to expand...
Click to collapse
Use this to flash ROMs up to Kitkat.
For Kitkat, need the 6.0.4.8 version which can be flashed using recovery. ROM manager does not download newer versions.

brick
I flashed CWMod-6.0.4.8-June04 "img" file (taken here "http://forum.xda-developers.com/showthread.php?t=2564767") through the command "fastboot flash recovery recovery.img" in fastboot mode, and now it's a total brick (black screen).
I'm not really lucky
EDIT = i can't enter fastboot mode neither. I'm not sure if it's because the back button is faulty (that is true but I succeded the first time) or even fastboot mode is broken (is it possible?)
Looking for a new phone, thanks all

steve281188 said:
I flashed CWMod-6.0.4.8-June04 "img" file (taken here "http://forum.xda-developers.com/showthread.php?t=2564767") through the command "fastboot flash recovery recovery.img" in fastboot mode, and now it's a total brick (black screen).
I'm not really lucky
EDIT = i can't enter fastboot mode neither. I'm not sure if it's because the back button is faulty (that is true but I succeded the first time) or even fastboot mode is broken (is it possible?)
Looking for a new phone, thanks all
Click to expand...
Click to collapse
You can get these phones dirt cheep in some places now.
Last try.
Take out battery, press home/volume-down/power, replacing battery. Or variations of this scheme. Since I have never succeded in running fastboot, this is how I got my phone back after similar mishaps. Try several times. (Make sure you have charge on that battery because that will to it as well!)
I flashed that image from adb shell: flash_image recover /sdcard/....img. There is also a normal zipped version that can be flashed from whatever recovery you have up, but not recommended. Using the adb method, if it fails, one can IMMEDIATELY flash an img that is known to work and not be bricked!

Dovidhalevi said:
Last try.
Take out battery, press home/volume-down/power, replacing battery. Or variations of this scheme.
Click to expand...
Click to collapse
is this the recovery combination? I tried but I'll try again.
Dovidhalevi said:
I flashed that image from adb shell: flash_image recover /sdcard/....img.
Click to expand...
Click to collapse
where I was wrong?
Dovidhalevi said:
There is also a normal zipped version that can be flashed from whatever recovery you have up, but not recommended.
Click to expand...
Click to collapse
are you talking about flashing a recovery with a recovery? why it's not recommended?
Dovidhalevi said:
Using the adb method, if it fails, one can IMMEDIATELY flash an img that is known to work and not be bricked!
Click to expand...
Click to collapse
sorry, I don't understand this part.

steve281188 said:
is this the recovery combination? I tried but I'll try again.
Click to expand...
Click to collapse
Yes, but more physical action. Sometimes manipulating the battery can get back into recovery. Cost nothing to try.
are you talking about flashing a recovery with a recovery? why it's not recommended? ...
sorry, I don't understand this part.
Click to expand...
Click to collapse
If the flash that recovery zip (overwriting the current one) and this fails. Brick.
If I am alive in adb and I flash_image the recovery .img and it fails, I now have no valid recovery but am still alive, and can then flash_image another that is known to succeed..
Problem is that our phones are restricted to a 5 meg recovery section. The dev worked hard to get the new CWM small enough (taking out some functionality such as partioning sdcards to do so), but it is right on the line. On some phones, unluckily maybe yours, it doesn't quite fit on. There is also a new TWRP recovery around, same restriction but maybe would be OK.

Dovidhalevi said:
Yes, but more physical action. Sometimes manipulating the battery can get back into recovery. Cost nothing to try.
If the flash that recovery zip (overwriting the current one) and this fails. Brick.
If I am alive in adb and I flash_image the recovery .img and it fails, I now have no valid recovery but am still alive, and can then flash_image another that is known to succeed..
Problem is that our phones are restricted to a 5 meg recovery section. The dev worked hard to get the new CWM small enough (taking out some functionality such as partioning sdcards to do so), but it is right on the line. On some phones, unluckily maybe yours, it doesn't quite fit on. There is also a new TWRP recovery around, same restriction but maybe would be OK.
Click to expand...
Click to collapse
I flashed the recovery that bricked the phone exactly through fastboot shell with the command above. So where I was wrong?
Is it possible I've "bricked" fastboot mode too? Or I can't enter fastboot anymore just because my back button is faulty?
thanks!!!

steve281188 said:
I flashed the recovery that bricked the phone exactly through fastboot shell with the command above. So where I was wrong?
Is it possible I've "bricked" fastboot mode too? Or I can't enter fastboot anymore just because my back button is faulty?
thanks!!!
Click to expand...
Click to collapse
I have never succeded in getting fastboot from my PC. Did it in an adb shell session (which means android or recovery was alive and kicking).
What messages did you see on the flash_image? Any error? Did it fit?
From the adb shell, if the flash_image fails, I can flash another img which I know is OK (must have that around on the sdcard). Then, no harm done. Otherwise, it is possible that the flash over-wrote the existing recovery, but failed. Thar's the problem.

recovery
When I flashed recovery from fastboot shell, everything was ok and no errors showed up.
From that moment, screen is always black.