[Q] Asus TF300T Does Not Start Because Of The Clockwork Recovery - Transformer TF300T Q&A, Help & Troubleshooting

Tablet: ASUS TF300T, Unlocked.
SO: Cyanogen 10
Old (working) Recovery ROM: “recovery-jb.img”
New (NOT working) Recovery ROM: “recovery-clockwork-5.5.0.4-tf300t.img”
Keys combination don’t work, just the APX one.
Symptom: the cyanogen didn’t work well so I changed the recovery ROM. As the new Recovery locks when executing from the bootloader, I decided to restart in recovery directly from the cyanogen (power button –>Reset -> Reset into Recovery). VERY BAD IDEA: Now the tablet always tries to start in recovery and gets stuck on the start screen. I can only enter the APX with keys combination. I cant enter boot loader and ATX doesn’t recognize fastboot & adb instructions.

Hi, I believe cyanogen 10 uses a jellybean bootloader and CWM 5.5.0.4 is for an ICS bootloader, so you will need to flash CWM 6.0.2.3 which is for jellybean bootloader.
Have a look at link below and download 'recovery-jb.img' & follow the how to flash.
http://forum.xda-developers.com/showthread.php?t=1668173
Hope this helps.

santdiego said:
Hi!
I have cyanogen 10 installed, but I tried to change my Tf300T Clockwork Recovery with this rom: "recovery-clockwork-5.5.0.4-tf300t.img"
Click to expand...
Click to collapse
Why?

pjc21 said:
Hi, I believe cyanogen 10 uses a jellybean bootloader and CWM 5.5.0.4 is for an ICS bootloader, so you will need to flash CWM 6.0.2.3 which is for jellybean bootloader.
Have a look at link below and download 'recovery-jb.img' & follow the how to flash.
http://forum.xda-developers.com/showthread.php?t=1668173
Hope this helps.
Click to expand...
Click to collapse
Hi! the problem is that I am stuck in the first screen when I turn on the tablet. The keys don't respond, the USB dont work , I cant go into bootloader and cyanogen dont start. It is just in the first screen since it try to boot from recovery always.

NixZero said:
Why?
Click to expand...
Click to collapse
My cyanogen didn't work fine. When I saw this article I thought that maybe I had installed a wrong ROM so i change it with the instructive one.... bad idea...

Have a look here
http://forum.xda-developers.com/showthread.php?t=2034866

pjc21 said:
Have a look here
http://forum.xda-developers.com/showthread.php?t=2034866
Click to expand...
Click to collapse
I think it goes into APX mode, holding "vol +", the screen remains off but the USB recognizes the APX. What should I do at this point to re install the ROM CWM or enter bootloader? when I go out the APX mode all remains the same, the tablet is still stuck .

Ok I no expert here so anyone else please correct me if I'm wrong.
When you say the USB recognizes APK, do you mean (assuming your running windows) that you can see your tab in device manager - something like 'Asus Android Device - Asus Android Bootloader Interface'
If so try this, open cmd (I always run as admin, don't know if it makes a difference) navigate to your /android-sdk/platform-tools and type
'fastboot -i 0x0B05 device' and hopefully you will get a response about your device (tab). If you do I would assume you could then flash recovery, ie put recovery-jb.img in your platform-tools folder and in cmd type 'fastboot -i 0x0B05 flash recovery recovery-jb.img' once done type 'fastboot -i 0x0B05 reboot' and hopefully all will be good, you may then need to reflash you rom not sure.
If your tab does not show in device manager then I have no idea sorry.
Hope this helps.

pjc21 said:
Ok I no expert here so anyone else please correct me if I'm wrong.
When you say the USB recognizes APK, do you mean (assuming your running windows) that you can see your tab in device manager - something like 'Asus Android Device - Asus Android Bootloader Interface'
If so try this, open cmd (I always run as admin, don't know if it makes a difference) navigate to your /android-sdk/platform-tools and type
'fastboot -i 0x0B05 device' and hopefully you will get a response about your device (tab). If you do I would assume you could then flash recovery, ie put recovery-jb.img in your platform-tools folder and in cmd type 'fastboot -i 0x0B05 flash recovery recovery-jb.img' once done type 'fastboot -i 0x0B05 reboot' and hopefully all will be good, you may then need to reflash you rom not sure.
If your tab does not show in device manager then I have no idea sorry.
Hope this helps.
Click to expand...
Click to collapse
Hi! thx for your help. fastboot and adb don't recognize the tablet in APX mode. My PC recognize APX mode. I installed the drivers for APX and I have nvflash ready to work, but it seems to be useless without access to fastboot.

pjc21 said:
'fastboot -i 0x0B05 device'
Hope this helps.
Click to expand...
Click to collapse
respond "< waiting for device >"

You have to wait for NVflash for JB bootloader.

Hazard17 said:
You have to wait for NVflash for JB bootloader.
Click to expand...
Click to collapse
Hi I have NVflash from here: http://androidroot.mobi/t3_nvflash/ butt this method also use fastboot and i cant access to it.

Hi, sorry to say after alot of searching and reading looks like the only soluation is to send it to Asus for repair.

Related

Can't load fastboot??

I'm trying to get into fastboot
reboot while holding vol down
select the USB icon and press vol up
but I am stuck at "Starting Fastboot USB download protocol"
am i doing something wrong?
xdeslitx said:
I'm trying to get into fastboot
reboot while holding vol down
select the USB icon and press vol up
but I am stuck at "Starting Fastboot USB download protocol"
am i doing something wrong?
Click to expand...
Click to collapse
No you are doing it right. THAT IS IS FASTBOOT. If you run the fastboot commands from your pc you will see it working on the pc.
xdeslitx said:
I'm trying to get into fastboot
reboot while holding vol down
select the USB icon and press vol up
but I am stuck at "Starting Fastboot USB download protocol"
am i doing something wrong?
Click to expand...
Click to collapse
sbdags said:
No you are doing it right. THAT IS IS FASTBOOT. If you run the fastboot commands from your pc you will see it working on the pc.
Click to expand...
Click to collapse
The above is correct, you are in fastboot if you see this (similar to download mode on samsung devices for use with ODIN).
Be sure to add path to environmental variables so that you can use fastboot commands at prompt (if in NT (windows) environment)
sbdags said:
No you are doing it right. THAT IS IS FASTBOOT. If you run the fastboot commands from your pc you will see it working on the pc.
Click to expand...
Click to collapse
i tried running the command " fastboot devices" and it doesnt see my tf700
i have all drivers loaded
Poser said:
The above is correct, you are in fastboot if you see this (similar to download mode on samsung devices for use with ODIN).
Be sure to add path to environmental variables so that you can use fastboot commands at prompt (if in NT (windows) environment)
Click to expand...
Click to collapse
i added the path to environmental variables.
Fastboot works fine for me.
Suggest you go over to the nvflash thread and download the windows drivers.
---------- Post added at 07:54 PM ---------- Previous post was at 07:52 PM ----------
xdeslitx said:
i tried running the command " fastboot devices" and it doesnt see my tf700
i have all drivers loaded
Click to expand...
Click to collapse
Isn't that adb commands you are trying to run. I.e., adb devices. I think you are confusing fastboot.
What are you trying to do?
sbdags said:
Fastboot works fine for me.
Suggest you go over to the nvflash thread and download the windows drivers.
---------- Post added at 07:54 PM ---------- Previous post was at 07:52 PM ----------
Isn't that adb commands you are trying to run. I.e., adb devices. I think you are confusing fastboot.
What are you trying to do?
Click to expand...
Click to collapse
fastboot devices is also a fastboot command from what i understand...i was trying to run that command to see if the computer can even see my tablet in fastboot...which it doesnt.
and i actually did get the drivers from the nvflash thread because that's what i am trying to accomplish
what does your tablet look like when you are in fastboot mode?
because i am doubting the fact that mine is even in that mode...i get the feeling that it gets stuck when trying to load fastboot
xdeslitx said:
fastboot devices is also a fastboot command from what i understand...i was trying to run that command to see if the computer can even see my tablet in fastboot...which it doesnt.
and i actually did get the drivers from the nvflash thread because that's what i am trying to accomplish
what does your tablet look like when you are in fastboot mode?
because i am doubting the fact that mine is even in that mode...i get the feeling that it gets stuck when trying to load fastboot
Click to expand...
Click to collapse
It just says starting Fastboot mode. It never changes from that.
im going to try and uninstall/reinstall the drivers to see if thatll work
finally got it to work...had to reload my drivers
haha so i did the whole nvflash thing but i dont really know how it works
all i know is that itll keep me from bricking my tf700
xdeslitx said:
finally got it to work...had to reload my drivers
haha so i did the whole nvflash thing but i dont really know how it works
all i know is that itll keep me from bricking my tf700
Click to expand...
Click to collapse
You can still brick your device but it's 100% recoverable, at least if it's not a hardware failure. Just make sure to keep your backup files safe.
Pretoriano80 said:
You can still brick your device but it's 100% recoverable, at least if it's not a hardware failure. Just make sure to keep your backup files safe.
Click to expand...
Click to collapse
are there any instructions on how to recover using these files in case of brick?
i didnt see any on the thread under development
xdeslitx said:
are there any instructions on how to recover using these files in case of brick?
i didnt see any on the thread under development
Click to expand...
Click to collapse
There's no guide so far, but i'm sure you would get some help from xda users when needed.
cool thanks for the replies
I'm stuck at fastboot mode with my TF700. Windows XP recognizes my device but the command "fastboot devices" doesn't show up my TF700. I tried to reinstall drivers from univeral naked drivers package 0.7 with success - tried it three times. Bootet up TF700 in fastboot mode but still fastboot doesn't see my device.
Has anyone an idea what I can do? I tried it also in my virtual linux machine without succes. I want to flash new CWM recovery over old TWRP recovery to update to JB and after this to get proprietary files needed to build CM10 from sources.
As I understand, without fastboot, I can't update my bootloader to JB. Not a nice device...
thunderger said:
I'm stuck at fastboot mode with my TF700. Windows XP recognizes my device but the command "fastboot devices" doesn't show up my TF700. I tried to reinstall drivers from univeral naked drivers package 0.7 with success - tried it three times. Bootet up TF700 in fastboot mode but still fastboot doesn't see my device.
Has anyone an idea what I can do? I tried it also in my virtual linux machine without succes. I want to flash new CWM recovery over old TWRP recovery to update to JB and after this to get proprietary files needed to build CM10 from sources.
As I understand, without fastboot, I can't update my bootloader to JB. Not a nice device...
Click to expand...
Click to collapse
Try to use this command to check if fastboot it's working : " fastboot -i 0x0b05 reboot ". If your device reboot after sending that command it means you can use fastboot just fine.
To be honest i've seen many bricks reports from people that tried to only flash the JB bootloader so imo the best way to get the JB bootloader is to flash the official JB firmware, then install the latest TWRP OR CWM recovery via fastboot, use the custom recovery to make a backup of the stock rom. Once you've did all that you can install CM10 just fine but also you will have the opportunity to go back to stock JB in case you need to.
thunderger said:
I'm stuck at fastboot mode with my TF700. Windows XP recognizes my device but the command "fastboot devices" doesn't show up my TF700. I tried to reinstall drivers from univeral naked drivers package 0.7 with success - tried it three times. Bootet up TF700 in fastboot mode but still fastboot doesn't see my device.
Has anyone an idea what I can do? I tried it also in my virtual linux machine without succes. I want to flash new CWM recovery over old TWRP recovery to update to JB and after this to get proprietary files needed to build CM10 from sources.
As I understand, without fastboot, I can't update my bootloader to JB. Not a nice device...
Click to expand...
Click to collapse
Fastboot devices does not work on this device. I've used fastboot to swap recovery images several times and update to the JB bootloader by itself. It definitely works as a whole.
Pretoriano80 said:
Try to use this command to check if fastboot it's working : " fastboot -i 0x0b05 reboot ". If your device reboot after sending that command it means you can use fastboot just fine.
To be honest i've seen many bricks reports from people that tried to only flash the JB bootloader so imo the best way to get the JB bootloader is to flash the official JB firmware, then install the latest TWRP OR CWM recovery via fastboot, use the custom recovery to make a backup of the stock rom. Once you've did all that you can install CM10 just fine but also you will have the opportunity to go back to stock JB in case you need to.
Click to expand...
Click to collapse
I've tried this command many times, and all I ever get is < waiting for device > and nothing else. This is getting annoying as hell. I've tried so many different things, all with the same result. I guess I'll just have to wait until there is an exploit found to root the JB firmware without having to use fastboot, then use TWRP from Goomanager, and hopefully by then there will be a zip of CWM Recovery.

Fastboot not working anymore?

Hi all.
I went to update my Recovery today to a new TWRP.
I have not had problems in the past.
When I boot into fastboot it just says "Starting Fastboot USB download protocol".
The drivers are properly installed and made sure under device manager.
Any idea's guys?
When I type fastboot devices I don't get anything.
Thanks for the help!
Also tried in Ubuntu still no luck >_<
are you using pc or mac, kinda dumb queston but alas it makes a difference
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
bige914 said:
are you using pc or mac, kinda dumb queston but alas it makes a difference
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
I am using a Asus Laptop. Thanks for the response!
im getting the same problem here, i want to install twrp but it shows Starting Fastboot USB download protocol on my tablet and < waiting for device > on my windows pc
sjj1991 said:
im getting the same problem here, i want to install twrp but it shows Starting Fastboot USB download protocol on my tablet and < waiting for device > on my windows pc
Click to expand...
Click to collapse
got the same issue guys
Anyone get anywhere with this? I just unlocked, then went to flashing a recovery but get the same "fastboot usb download protocol" message..
We are all stuck with this unless we send it to asus for RMA
Sent from my VS840 4G using xda premium
SpyFi said:
Also tried in Ubuntu still no luck >_<
Click to expand...
Click to collapse
Let's talk about ubuntu a minute since fastboot worked before. It appears no one else has said fastboot worked earlier.
Are you running ubuntu on a different computer?
Same computer through virtualbox or something similar?
Same computer different drive or partition?
Try " adb devices " before you reply and include that info as well.
I should have also asked if fastboot previously worked on ubuntu?
tobdaryl said:
Let's talk about ubuntu a minute since fastboot worked before. It appears no one else has said fastboot worked earlier.
Are you running ubuntu on a different computer?
Same computer through virtualbox or something similar?
Same computer different drive or partition?
Try " adb devices " before you reply and include that info as well.
I should have also asked if fastboot previously worked on ubuntu?
Click to expand...
Click to collapse
the problem is not the computer itself, the real problem is that the tablet doesn't get in fastboot mode...
Thank you for the update.
SpyFi said:
Hi all.
I went to update my Recovery today to a new TWRP.
I have not had problems in the past.
When I boot into fastboot it just says "Starting Fastboot USB download protocol".
The drivers are properly installed and made sure under device manager.
Any idea's guys?
When I type fastboot devices I don't get anything.
Thanks for the help!
Click to expand...
Click to collapse
sjj1991 said:
im getting the same problem here, i want to install twrp but it shows Starting Fastboot USB download protocol on my tablet and < waiting for device > on my windows pc
Click to expand...
Click to collapse
matt95 said:
got the same issue guys
Click to expand...
Click to collapse
partypage said:
Anyone get anywhere with this? I just unlocked, then went to flashing a recovery but get the same "fastboot usb download protocol" message..
Click to expand...
Click to collapse
tobdaryl said:
Let's talk about ubuntu a minute since fastboot worked before. It appears no one else has said fastboot worked earlier.
Are you running ubuntu on a different computer?
Same computer through virtualbox or something similar?
Same computer different drive or partition?
Try " adb devices " before you reply and include that info as well.
I should have also asked if fastboot previously worked on ubuntu?
Click to expand...
Click to collapse
Try this:
-use unlock tool
-boot tablet into USB MODE
(it will say fastboot mode,waiting)
-using the steps,copying over the fastboot files to one folder, with TWRP as the recovery, run fastboot command.
-done successfully,you be good
Click to expand...
Click to collapse
I'm not the author of this process, but apparently it works.
I haven't tried, because I use terminal emulator for my adb command
I decided to automate the process of entering commands. Post
philos64 said:
Try this:
I'm not the author of this process, but apparently it works.
I haven't tried, because I use terminal emulator for my adb command
Click to expand...
Click to collapse
thank you, i'll try this out tomorrow! :good:
no way, i can't get it to fastboot damn it
---------- Post added at 11:45 PM ---------- Previous post was at 11:16 PM ----------
ok i solved the problem just now...
1-reboot the tablet in bootloader while connected to usb
2-use vol down to navigate to the usb mode and then vol up
3-the tablet won't show nothing but actually it is connected
4-proceed to any fastboot command
hope this helps
I had this issue when I first started flashing stuff (although I was flashing CWM not TWRP)
In my experience, if you don't see anything listed in fastboot devices, it doesn't matter because it still flashes.
Just try using the flash command (fastboot -i 0x0b05 flash blah blah blah.blah) and see if it works.
You -should- be able to see your device in "adb devices", and that's really what matters.
Also, what matt95 said is exactly what I do. Whether it shows anything or not, I just flash my stuff. Works fine, but I also don't use fastboot alot because with the new changes to the bootloader, one can flash stock through CWM now without having to fastboot flash it.
I'm having the same problem here with fast boot. I want to run NV Flash so I can update to the JB bootloader for CM updates. I've tried simple commands like reboot and nothing works. Any other thoughts?
jm700wx said:
I'm having the same problem here with fast boot. I want to run NV Flash so I can update to the JB bootloader for CM updates. I've tried simple commands like reboot and nothing works. Any other thoughts?
Click to expand...
Click to collapse
my solution above didn't help?
matt95 said:
my solution above didn't help?
Click to expand...
Click to collapse
I'm in the same wagon as all you guys, I just tried that and I can't get into fastboot still. Still waiting for device
---------- Post added at 01:10 PM ---------- Previous post was at 01:02 PM ----------
I'm sorted now, I didn't realise that we needed a different command
I was using
Code:
fastboot flash recovery recovery-jb-touch.img
instead of the correct method of using
Code:
fastboot -i 0x0B05 flash recovery recovery-jb-touch.img
This worked perfectly
it's same as this:
== Part 3 - Install recovery and rooting ==
Let's start with installing the recovery
1) Download these 2 files:
- Jellybean recovery with fastboot files: Fastboot files + JB recovery
- Root files => Root files
- You can also download the new CWM Touch recovery if you don't like TWRP: CWM Touch recovery thread or TWRP recovery and download this file : openrecovery-twrp-2.3.1.0-tf300t-JB.blob
2) Extract the recovery with fastboot files zip and open a command prompt in the same folder of the adb and fastboot files (Shift + Right mouse)
3) Reboot into the bootloader of your tablet, type: adb reboot bootloader
4) When your tablet has reached the bootloader navigate with volume down to the usb icon and press volume up to confirm.
5) To flash the recovery type:
- TWRP: fastboot -i 0x0b05 flash recovery twrp.blob
- CWM: fastboot -i 0x0b05 flash recovery CWM-Touch.blob
6) A blue bar will appear and the recovery will be installed, when the blue bar is filled press volume up + power button to reboot into the tablet.
Now we will root the tablet
7) Copy Superuser-3.2-RC3-arm-signed to the internal storage of your tablet. then reboot into the bootloader again.
8) This time you need to select the RCK icon with volume up to enter the recovery image.
9) In recovery flash Superuser-3.2-RC3-arm-signed and reboot into the system
10) Install Supersu from Google Play
11) Open up Supersu, it will ask you to update the binary, choose yes.
12) Now your tablet should be rooted
Click to expand...
Click to collapse

[Q] ROM manager clockworkmod update bricked tf700

Hello there!
I have a TF700T pad, I installed free rom manager application, from within that application I chose to install clockworkmod recovery, the application loaded the clockworkmod recovery from the internet (there was an indicator on top of the application screen).
After finished, I rebooted into recovery, but it doesn't reboot to recovery, it loads android normally, then I tried to boot to recovery manually by pressing and holding the the power button along with the volume down button it loads nothing and stays there for ever!! I did this several times then it it changed and now it doesn't even load the android normally.
And when I boot into APX mode, the adb can't find it!
In short, I can't access recovery nor system!
When I try to boot to recovery
(power + volume down) It freezs and the following shows on the screen:
"The device is unlocked.
Android cardhu-user bootloader <2.10 e> release by "CN_epad-9.4.5.30-20120907" A03
Checking for android ota recovery
Booting recovery kernel image"
- I downloaded the firmware from ASUS and renamed it to "EP201_768_SDUPDATE" and copied to the root of a formated FAT32 micro SD card and tried to boot, but still freezing on above mentioned screen.
- The PC recognizes it (drivers are correct, i downloaded them and installed them) but the adb can not find the pad and tells me to install tap's specific drivers!
- I tried to flash the recovery image image.img through adb, but same problem, it stays there for ever showing the message "waiting for device".
Please, help me with a solution for that situation!
Thank you.
shreef said:
Hello there!
I have a TF700T pad, I installed free rom manager application, from within that application I chose to install clockworkmod recovery, the application loaded the clockworkmod recovery from the internet (there was an indicator on top of the application screen).
After finished, I rebooted into recovery, but it doesn't reboot to recovery, it loads android normally, then I tried to boot to recovery manually by pressing and holding the the power button along with the volume down button it loads nothing and stays there for ever!! I did this several times then it it changed and now it doesn't even load the android normally.
And when I boot into APX mode, the adb can't find it!
In short, I can't access recovery nor system!
When I try to boot to recovery
(power + volume down) It freezs and the following shows on the screen:
"The device is unlocked.
Android cardhu-user bootloader <2.10 e> release by "CN_epad-9.4.5.30-20120907" A03
Checking for android ota recovery
Booting recovery kernel image"
- I downloaded the firmware from ASUS and renamed it to "EP201_768_SDUPDATE" and copied to the root of a formated FAT32 micro SD card and tried to boot, but still freezing on above mentioned screen.
- The PC recognizes it (drivers are correct, i downloaded them and installed them) but the adb can not find the pad and tells me to install tap's specific drivers!
- I tried to flash the recovery image image.img through adb, but same problem, it stays there for ever showing the message "waiting for device".
Please, help me with a solution for that situation!
Thank you.
Click to expand...
Click to collapse
Do you have nvflash backup? if not, I believe you're done. You need to send out for repair.
Thank you for your quick response!
Isn't there any other way I could repair it without sending to ASUS repair?? i originally bought it from CHINA and now i am here in EGYPT!!!
shreef said:
Thank you for your quick response!
Isn't there any other way I could repair it without sending to ASUS repair?? i originally bought it from CHINA and now i am here in EGYPT!!!
Click to expand...
Click to collapse
I'm assuming you've unlocked the bootloader. Can you get the device into fastboot and push a new recovery through that?
shreef said:
Thank you for your quick response!
Isn't there any other way I could repair it without sending to ASUS repair?? i originally bought it from CHINA and now i am here in EGYPT!!!
Click to expand...
Click to collapse
ArmyAg08 said:
I'm assuming you've unlocked the bootloader. Can you get the device into fastboot and push a new recovery through that?
Click to expand...
Click to collapse
That would be the only remaining option, but ROM Manager is known to do this. If a user cannot even read on a forum before doing stuff, I'm not sure this is going to work out very well.
OK. I'll go back to my hermit cave now.
No, I can only boot in APX mode!
Isn't there any way we can make the adb reconize and access the PAD?
I can bring the recovery image and put in the root of the SD card, but what should I name it so the boot can reconize it and update? (the device says "checking for android ota recovery" !!
shreef said:
No, I can only boot in APX mode!
Isn't there any way we can make the adb reconize and access the PAD?
I can bring the recovery image and put in the root of the SD card, but what should I name it so the boot can reconize it and update? (the device says "checking for android ota recovery" !!
Click to expand...
Click to collapse
APX is NOT adb -- you need to issue commands using fastboot. Did you use the manufacturer's switch? "adb devices" won't return anything, even on a perfectly healthy 700. Take a look here:
http://forum.xda-developers.com/showthread.php?t=1926286
and don't forget to use that switch: -i 0x0B05, as in
fastboot -i 0x0B05 <command>
For example, fastboot -i 0x0B05 devices or fastboot -i 0x0B05 reboot
EDIT: APX = FASTBOOT, for clarity.
MartyHulskemper said:
That would be the only remaining option, but ROM Manager is known to do this. If a user cannot even read on a forum before doing stuff, I'm not sure this is going to work out very well.
OK. I'll go back to my hermit cave now.
Click to expand...
Click to collapse
I only asked because I thought ROM manager was known to brick this tablet if you tried to install a recovery with it. I may be mistaken though.
Sent from my ASUS Transformer Pad TF700T
MartyHulskemper said:
APX is NOT adb -- you need to issue commands using fastboot.
Click to expand...
Click to collapse
APX is also NOT fastboot - in APX mode you can *only* use nvflash, but for that you'd need to have created the blob before bricking.
I am sorry, I didn't really understand what you are trying to say!!
What does "manfacturer's switch" mean?
Also, what does APX = FASTBOOT ?
shreef said:
I am sorry, I didn't really understand what you are trying to say!!
What does "manfacturer's switch" mean?
Also, what does APX = FASTBOOT ?
Click to expand...
Click to collapse
shreef, the short answer is that only ASUS can help you now. I believe that is your only solution.
I'm so sorry.
OK, I have sent it to ASUS!
Thank you guys for your care and help.
Regards
ArmyAg08 said:
I only asked because I thought ROM manager was known to brick this tablet if you tried to install a recovery with it. I may be mistaken though.
Sent from my ASUS Transformer Pad TF700T
Click to expand...
Click to collapse
You're right. I wasn't mad/annoyed at your post. I just wanted to point out it has been known for a while now that ROM Manager does funky things on the 700. I'd just stay away from it -- iIn the sense that if one aspect of a program is broken by a device's particulars, changes are relatively high that some other aspect(s) is/are broken as well and you might get to know which one(s) that is/are by first-hand experience.
_that said:
APX is also NOT fastboot - in APX mode you can *only* use nvflash, but for that you'd need to have created the blob before bricking.
Click to expand...
Click to collapse
You're right. I was cutting the curve. I'm sorry for the confusion.
okantomi said:
shreef, the short answer is that only ASUS can help you now. I believe that is your only solution.
I'm so sorry.
Click to expand...
Click to collapse
That is quite the accurate summary.
@OP: hope ASUS treats your device nicely and you can get back in our midst with a 700 working well for you, soon.

[Q] help, i think i bricked my tablet

hi, first of all, i'd like to tell you i'm quite a noob
i have a tf300tg and i tried to flash the jb 4.2.2 that's only available for the 300t.. i'm dumb, i know.. and now in stead of booting it goes directly to the cwm menu and i can't do anything.. i keep getting the error E:Can't mount /cache/recovery/command , .../log and .../last_log
is there anything i can do or should i just throw it in the trashbin ?
iostu said:
hi, first of all, i'd like to tell you i'm quite a noob
i have a tf300tg and i tried to flash the jb 4.2.2 that's only available for the 300t.. i'm dumb, i know.. and now in stead of booting it goes directly to the cwm menu and i can't do anything.. i keep getting the error E:Can't mount /cache/recovery/command , .../log and .../last_log
is there anything i can do or should i just throw it in the trashbin ?
Click to expand...
Click to collapse
Unless you can go into fastboot (Power + volume down) there isn't much to do but to sign a petition & wait...
XDA member HAZARD17 has been running a petition
Sign NVflash petition for Transformer TF300T, Prime & Infinity!
https://www.change.org/petitions/asus-nvidia-revert-changes-in-jb-bootloader-that-prevent-nvflash
vconceicao said:
Unless you can go into fastboot (Power + volume down) there isn't much to doo but to wait...
Click to expand...
Click to collapse
i can't do that either.. it just loads the CWM menu..
wait ? wait for what ? :silly:
iostu said:
i can't do that either.. it just loads the CWM menu..
wait ? wait for what ? :silly:
Click to expand...
Click to collapse
For someone to come up with a solution, Like a NVflash utility for Tf300...
Yeah, but if you want add NVflash support to your tablet, it can't be bricked I'm not quite sure, but you try unpack blob from offical update, and flash all files from unpacked blob (LNX etc.).
Hazard17 said:
Yeah, but if you want add NVflash support to your tablet, it can't be bricked I'm not quite sure, but you try unpack blob from offical update, and flash all files from unpacked blob (LNX etc.).
Click to expand...
Click to collapse
i can't flash anything :| in adb it sais <waiting for device> i've tried everything and i can't get it to work.. can you pleeeeeease help me ?
ok, i reinstalled the adb drivers for the transformer, and it goes into bootloader but there is no usb icon.. only RCK, the android and wipe data.. when i type adb devices i get 123456789ABCDEF recovery. although i can't do much else, i can't do anything in adb shell, i can't even flash the twrp.. any suggestions ? plese please please
iostu said:
ok, i reinstalled the adb drivers for the transformer, and it goes into bootloader but there is no usb icon.. only RCK, the android and wipe data.. when i type adb devices i get 123456789ABCDEF recovery. although i can't do much else, i can't do anything in adb shell, i can't even flash the twrp.. any suggestions ? plese please please
Click to expand...
Click to collapse
The USB icon is gone. I sugguest downloading the correct firmware and flashing it with fastboot.
fastboot flash system blob
Download the correct system firmware, open the zip, open the zip, extract the blob to the same directory as fast boot.
iostu said:
ok, i reinstalled the adb drivers for the transformer, and it goes into bootloader but there is no usb icon.. only RCK, the android and wipe data.. when i type adb devices i get 123456789ABCDEF recovery. although i can't do much else, i can't do anything in adb shell, i can't even flash the twrp.. any suggestions ? plese please please
Click to expand...
Click to collapse
4.2 bootloader does not have USB icon, just plug in USB..
i can get to the bootloader menu but only after typing adb reboot bootloader. and then i tryed flashing the blob using adb fastboot -i 0x0b05 flash system blob and then i get "sending 'system' <799764 KB>..." and it's stuck there.. i left it over 30 mins and still nothing
edit: i somehow managed to flash teh system blob (i tried with te 4.1.1 and the 4.2.2) but after flashing it did the exact same thing.. went to CWM ! i even managed to flash the TWRP.blob, and still the CWM showed up.. i can't figure out how is this even possible :| and from the bootloader menu if i go to boot the android firmware, it almost boots (it goes to the lockscreen for about 2 secs) and then reboots again.. am i wasting my time or should i throw it in the garbage ?
thanks again for trying to help me on this one i really appreciate it !
iostu said:
i can get to the bootloader menu but only after typing adb reboot bootloader. and then i tryed flashing the blob using adb fastboot -i 0x0b05 flash system blob and then i get "sending 'system' <799764 KB>..." and it's stuck there.. i left it over 30 mins and still nothing
edit: i somehow managed to flash teh system blob (i tried with te 4.1.1 and the 4.2.2) but after flashing it did the exact same thing.. went to CWM ! i even managed to flash the TWRP.blob, and still the CWM showed up.. i can't figure out how is this even possible :| and from the bootloader menu if i go to boot the android firmware, it almost boots (it goes to the lockscreen for about 2 secs) and then reboots again.. am i wasting my time or should i throw it in the garbage ?
thanks again for trying to help me on this one i really appreciate it !
Click to expand...
Click to collapse
Sounds like you're in the same boat as the rest of us...
http://forum.xda-developers.com/showthread.php?t=2179874
iostu said:
ok, i reinstalled the adb drivers for the transformer, and it goes into bootloader but there is no usb icon.. only RCK, the android and wipe data.. when i type adb devices i get 123456789ABCDEF recovery. although i can't do much else, i can't do anything in adb shell, i can't even flash the twrp.. any suggestions ? plese please please
Click to expand...
Click to collapse
OK. The bootloader menu you now are seeing is the new 4.2 version. RCK - Android - Wipe Data(do not use wipe data).
When you get into this menu if you leave everything alone your tablet should auto into fastboot - watch the screen - upper left.
With fastboot flash the latest (proper) JB blob for your unit.
Good Luck!
iostu said:
i can get to the bootloader menu but only after typing adb reboot bootloader. and then i tryed flashing the blob using adb fastboot -i 0x0b05 flash system blob and then i get "sending 'system' <799764 KB>..." and it's stuck there.. i left it over 30 mins and still nothing
edit: i somehow managed to flash teh system blob (i tried with te 4.1.1 and the 4.2.2) but after flashing it did the exact same thing.. went to CWM ! i even managed to flash the TWRP.blob, and still the CWM showed up.. i can't figure out how is this even possible :| and from the bootloader menu if i go to boot the android firmware, it almost boots (it goes to the lockscreen for about 2 secs) and then reboots again.. am i wasting my time or should i throw it in the garbage ?
thanks again for trying to help me on this one i really appreciate it !
Click to expand...
Click to collapse
You can't flash anything using adb commands. You need to use fastboot. Look in the forum for the proper procedure and follow the instructions.
Nowhere does it say type "adb fastboot ... anything...."
hgoldner said:
You can't flash anything using adb commands. You need to use fastboot. Look in the forum for the proper procedure and follow the instructions.
Nowhere does it say type "adb fastboot ... anything...."
Click to expand...
Click to collapse
Here is an example of an adb command that does work to flash twrp with slight modification it will flash stock blob as well.
adb shell
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4 Then reboot to complete installation.
adb reboot
I don't know where you are getting your information but you need a new source.
No one said type adb fastboot they are two different things and each has a specific structure to follow.
If the op can get either fastboot or adb to work I'll gladly provide the proper commands.
then you have the same problem as me and a bunch of other people. The bootloader freezes on the flash command, even though it will show success and stuff. It never flashes.
I can push files with ADB and on reboot the files on gone. Since we can't flash with fastboot. We have to send it in to asus at this point. I got quoted $87 + shipping.
sorry, i meant to say just fastboot. i didn't write adb fastboot.. i've tried everything you guys said, but with no success my last resort is to send it to asus for re-softing. It costs about $80 + shipping. It doesn't sound like a lot of money, but it's a price to pay for stupidness or noobness i just hope they can repair it or otherwise i'll have a very expensive thing on whch to chop onions
thanks again guys for helping me

[Q] help to get back to stock

tf300t unroot with android 4.2.1
running in 10.6.1.15.3
system always boot to cwm
from pc using cmd using adb reboot-bootloader
in the fastboot mode
with no usb icon
unable to flash with anything
not even able to cold boot
just only able to boot to cwm v6.0.2.3
each time need to cmd to boot to fastboot but no usb icon
any idea
question is this mean im in brick
Sheena0220 said:
tf300t unroot with android 4.2.1
running in 10.6.1.15.3
system always boot to cwm
from pc using cmd using adb reboot-bootloader
in the fastboot mode
with no usb icon
unable to flash with anything
not even able to cold boot
just only able to boot to cwm v6.0.2.3
each time need to cmd to boot to fastboot but no usb icon
any idea
question is this mean im in brick
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=42011887#post42011887 - read this post and let me know if you have any questions.
it doesnt work for me
i did exactly how you say
place the unzip file to sdcard
place the sd card to the side of the mmsd slot
reboot the tablet
nothing happen
even try to reboot in the fastboot mode and press the up button at he rck mode
still no go
i just have no idea how i got to the point that the bootloader fail went i in the fastboot->rck
show that fail bootloader with (0x000000000)
i can only get to APX mode and Fastboot using pc (but i cant do nothing to it) it doesnt show the usb icon
i can read the tablet
but i cant write anything to it
im still waiting for something happen
hope one of this master
have a software and about to bring back to live
Sheena0220 said:
it doesnt work for me
i did exactly how you say
place the unzip file to sdcard
place the sd card to the side of the mmsd slot
reboot the tablet
nothing happen
even try to reboot in the fastboot mode and press the up button at he rck mode
still no go
i just have no idea how i got to the point that the bootloader fail went i in the fastboot->rck
show that fail bootloader with (0x000000000)
i can only get to APX mode and Fastboot using pc (but i cant do nothing to it) it doesnt show the usb icon
i can read the tablet
but i cant write anything to it
im still waiting for something happen
hope one of this master
have a software and about to bring back to live
Click to expand...
Click to collapse
The previous link you were provided only works with stock recovery not cwm or twrp.
The 4.2 bootloader (10.6.?.?.?) does not have a usb icon. When you get to the bootloader press no buttons and wait for notification in the upper left - entering fastboot.
Sheena0220 said:
it doesnt work for me
i did exactly how you say
place the unzip file to sdcard
place the sd card to the side of the mmsd slot
reboot the tablet
nothing happen
even try to reboot in the fastboot mode and press the up button at he rck mode
still no go
i just have no idea how i got to the point that the bootloader fail went i in the fastboot->rck
show that fail bootloader with (0x000000000)
i can only get to APX mode and Fastboot using pc (but i cant do nothing to it) it doesnt show the usb icon
i can read the tablet
but i cant write anything to it
im still waiting for something happen
hope one of this master
have a software and about to bring back to live
Click to expand...
Click to collapse
http://www.androidauthority.com/transformer-pad-tf300t-restore-stock-firmware-108016/ = try this method. this is the fastboot method. FYI, as sheena said, you dont need to see the usb icon. immediately u boot into the bootloader, the tablet enters fastboot mode. if you need more detailed instructios, add me on skype or facebook. i'll be glad to help.
crazynitro said:
http://www.androidauthority.com/transformer-pad-tf300t-restore-stock-firmware-108016/ = try this method. this is the fastboot method. FYI, as sheena said, you dont need to see the usb icon. immediately u boot into the bootloader, the tablet enters fastboot mode. if you need more detailed instructios, add me on skype or facebook. i'll be glad to help.
Click to expand...
Click to collapse
thx for the instruction
i will try it tonight
i think i see somewhere before and try it before with the code in the cmd
at fastboot
while the tablet still flashing with the 3 icon (rck, android, and wipe data)
in pc i type this code as follow
fastboot device
come out the sn #
fastboot -i 0x0b05 flash system blob
then the tablet freeze but the cmd is say success
but i try only one or two time
at this moment i only able to boot in to fastboot by hard reset and the APX
in APX mode the pc didnt recognize the driver
also i try couple at fastboot mode in tablet i hit the upper vol at RCK
it return message as follow
bootloader fail
code is 0X 00000000
i know it is not in brick
the system has no os to boot too
and the tablet has no wait to write anything into it
but i will try the method you have instruct tonight at see any chance
hope no need to send back to the shop to fix it
Sheena0220 said:
thx for the instruction
i will try it tonight
i think i see somewhere before and try it before with the code in the cmd
at fastboot
while the tablet still flashing with the 3 icon (rck, android, and wipe data)
in pc i type this code as follow
fastboot device
come out the sn #
fastboot -i 0x0b05 flash system blob
then the tablet freeze but the cmd is say success
but i try only one or two time
at this moment i only able to boot in to fastboot by hard reset and the APX
in APX mode the pc didnt recognize the driver
also i try couple at fastboot mode in tablet i hit the upper vol at RCK
it return message as follow
bootloader fail
code is 0X 00000000
i know it is not in brick
the system has no os to boot too
and the tablet has no wait to write anything into it
but i will try the method you have instruct tonight at see any chance
hope no need to send back to the shop to fix it
Click to expand...
Click to collapse
i had try the method
tablet freeze as soon as i start the code of
fastboot -i 0x0B05 flash system blob
i do see in cmd say finish and ok
i try code of fastboot -i 0x0B05 reboot
tablet didnt response
try fastboot devices
come back will
??????????????????? list
i just dont know what to do
it freeze all the time as i write something into tablet
Sheena0220 said:
i had try the method
tablet freeze as soon as i start the code of
fastboot -i 0x0B05 flash system blob
i do see in cmd say finish and ok
i try code of fastboot -i 0x0B05 reboot
tablet didnt response
try fastboot devices
come back will
??????????????????? list
i just dont know what to do
it freeze all the time as i write something into tablet
Click to expand...
Click to collapse
which firmware did you download? have you tried flashing a recovery img like twrp?
crazynitro said:
which firmware did you download? have you tried flashing a recovery img like twrp?
Click to expand...
Click to collapse
i use us one and get the blob out
i think i got what you mean now
i have to have the right blob before i can get the flash work if not i will freeze it
the problem is i cant even boot to android
so i have no clue on will firmware i using
all i can see from now is at the fastboot that only is us ...10.6....
is that the firmware i have to flash if do so i will try
i cant even flash the twrp into the tablet
i try blob and img
it wont work
i try the version is the 2.5......4.2.blob or img
it just got no luck at all
thx thx thx
Sounds like you flashed the incorrect twrp for your bootloader, flashing a non-4.2 twrp on a 4.2 bootloader can cause a fastboot flash brick.
Here's a little info about the changes from a 4.1 to a 4.2 bootloader as there have been quite a few bricks here over the last few months.
Still not sure of the exact issue here but seems there was a change in some or all of the partition tables with the 4.2 bootloaders for both 10.6.1.8 & 10.6.1.15.3 and as a result after updating to 4.2 and then flashing TWRP (non-4.2 version) or CWM recovery would give the following outcome when you boot to recovery.
TWRP would ask for a password on boot, you can hit cancel but are left not being able to mount any partition including external apart from possible system.
CWM was the same, unable to mount any partition.
The device will now also likely boot strait to recovery, and if you have not wiped system you will now have to cold boot andriod from now on.
Now the bad part - In about 90% of cases flashing TWRP (non-4.2 version) or CWM would also result in a fastboot flash brick, meaning that some other fastboot commands will work ok, however any fastboot flash command will look to go ok on the command prompt but you will no longer get the blue progress bar on the tablet and nothing will flash to the tablet. So your either stuck with the current os and have to cold boot or if you wiped your system your just stuck.
Only solution so far to this issue is to replace your motherboard. Here's a thread on the issue http://forum.xda-developers.com/show....php?t=2179874
And thus the -4.2 versions of TWRP were made for the 4.2 bootloaders
JB 4.2 bootloaders require the -4.2 versions of twrp
- JB 4.2.1 - 10.6.1.8 = twrp 2.4.4.0-4.2
- JB 4.2.1 - 10.6.1.15.3 = twrp 2.5.0.0-4.2
So if you do not get the blue progress bar on tablet when running a fastboot flash command then sorry to say you have the fastboot flash brick.
There are many many threads/posts on this issue with the above info but still people are not reading, bricking there tablets and creating duplicate upon duplicate threads on this issue, so please look through the threads first, read, read and read some more and if still not sure ask as many questions as you need.
Hope this helps explain what has happened and why the fastboot flash command freezes your tablet.
ok thx for everyone that give a great advice
i just change a new motherbooard
and now the tablet is in a unroot and unlock
i just want a instruction on how to do the unlock and root correctly
i read so many post
i just confuse
im in a android 4.2.1
and us 10.6.1.15.3
any suggestion before i got mess up

Categories

Resources