Hi all,
I've flashed CWM 6.0.2.3 instead of TWRP 2.5 to recovery partition after having unlocked the ASUS JB 4.2 bootloader using ASUS unlock tool V8. After that ASUS JB 4.2 was running well but not with root access AND i did the big mistake to use the wipe function in the bootloader ... since then i'm stuck in a boot loop with access only to CWM but i can't mount anything (internal or external sdcard) ! The good news is that i have still adb access under recovery => i run 'sudo adb reboot-bootloader' to access the bootloader menu which also provides me fastboot access ... the problem is than when i run 'sudo fastboot -w' in order to perform a wipe, the linux command hangs the tf300t after having erased and formatted the userdata partition (first one in the wipe process) !!!
Also, flashing system or recovery using fastboot works but i don't have the blue progress bar during the operation and the 'sudo fastboot reboot' command hangs the device ... for example if i run 'sudo fastboot flash recovery twrp.blob (i use the 42 version not JB or ICS one) i have a successfull output BUT fastboot is unable to reboot my device and when rebooted after pressing the power button for 8 secs i am back in CWM 6.0.2.3
I've noticed this output when booting the tablet to the bootloader menu : 'key driver not found booting os' and i've no clue about the meaning of this message => it seems that if i successfully flash TWRP this message will disappear ...
Any help would be greatly appreciated,
Have a nice day
I've exactly the same problem!
I tried to:
fastboot -i 0x0b05 flash system blob
fastboot says ok, but I can't reboot by:
fastboot -i 0x0b05 reboot
fastboot says ok, but nothing happend.
On reboot the pad show the CWM interface.
I tried this:
Reboot the pad. When the pad activates the usb port, I tried: adb reboot-bootloader
Then the bootloader interface is shown.
A cold boot does not work.
I need HELP
huebinger said:
I've exactly the same problem!
I tried to:
fastboot -i 0x0b05 flash system blob
fastboot says ok, but I can't reboot by:
fastboot -i 0x0b05 reboot
fastboot says ok, but nothing happend.
On reboot the pad show the CWM interface.
I tried this:
Reboot the pad. When the pad activates the usb port, I tried: adb reboot-bootloader
Then the bootloader interface is shown.
A cold boot does not work.
I need HELP
Click to expand...
Click to collapse
Hi, posting just to let you know that i had to make a RMA for my device which was still under warranty => Asus fixed it free of charge
Best regards
Sent from my ASUS Transformer Pad TF300T with Tapatalk HD
I can't think of any particular posts, but I've seen this scenario around in these forums before. Have a search around.
My tf 700t is stop in a restarting loop until the battery is finished.... i have tried booting into recovery but the logo of the recovery TwRP apear and the tablet restarts itself to that point ,until the battery is dead.
Any sugestions?
the tablet is rooted and i was on KatKiss rom on the moment of the crash for about 5 months.
Try this:
http://www.transformerforums.com/fo...my-transformer-tf700-boots-only-recovery.html
Sent from my Nexus 5X using Tapatalk
I'm having the exact same issue.
I can occasionally get into the bootloader, but when I try to get into TWRP it will show the logo page and will immediately restarts.
Following the link you sent, I tried the adb devices prompt, but it showed up blank. Do I need to be in TWRP for adb to work? When I try to get into TWRP it just restarts.
Not sure what my options are when the only screen I can get into is the fastboot.
wldtravel26 said:
I'm having the exact same issue.
I can occasionally get into the bootloader, but when I try to get into TWRP it will show the logo page and will immediately restarts.
Following the link you sent, I tried the adb devices prompt, but it showed up blank. Do I need to be in TWRP for adb to work? When I try to get into TWRP it just restarts.
Not sure what my options are when the only screen I can get into is the fastboot.
Click to expand...
Click to collapse
If you can get into fastboot yours is a very different situation. But let me answer your questions first.
The linked method works if you have adb access in TWRP - however briely. Even if TWRP loops you should have adb access at some point (open Device Manager and watch for changes).
If TWRP is just bootlooping very quickly you may be out of luck but I have seen cases where a little window of adb access and careful timing of the commands let people push the file to internal and insmod it. But that depends on the nature of the bootloop, the skill of the user and persistence.
Now, if you have fastboot access you don't need any of that. In fastboot you have a pretty powerful tool to wipe and format partitions, flash the Asus blob if all fails, but you quite a few options....
If you can get "only occasionally" into the bootloader I would not wait much longer but perform a full wipe of the major partitions and flash the Asus system blob, returning the tablet to stock basically and giving you a fresh start.
We call it a @Buster99
Download the latest Asus firmware from here: https://www.asus.com/support/Download/28/1/0/11/fq2B3oq64av1O95u/8/
Extract it twice and copy the blob into your fastboot directory.
Issue these commands in fastboot one by one:
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system blob
fastboot -i 0x0B05 reboot
Good luck!
Thanks Berndblb. I downloaded the Asus firmware and was able to get the blob file.
But I'm fine with totally starting over and trying Buster99, but I'm still unable to get the ADB to see the device.
I've gone through the beginners guide to root and flashing a custom rom again, but I still can't see the device when I type in "fastboot devices".
If you have any advice or a guide on what I need to do get where I can use ADB to erase everything and start over again.
i cant do anything the tablet starts - shows asus logo-go to TWRP logo screen - restarts (all in 32 seconds). Any other sugestion? if i dismantle the tablet ? or anithing else?
Thank You
wldtravel26 said:
Thanks Berndblb. I downloaded the Asus firmware and was able to get the blob file.
But I'm fine with totally starting over and trying Buster99, but I'm still unable to get the ADB to see the device.
I've gone through the beginners guide to root and flashing a custom rom again, but I still can't see the device when I type in "fastboot devices".
If you have any advice or a guide on what I need to do get where I can use ADB to erase everything and start over again.
Click to expand...
Click to collapse
Either you do not have the correct driver installed or your usb cable is not original but a cheap "charge only" knockoff or try a different usb port or you are not open the cmd prompt from the fastboot directory or your usb port is busted.....
I don't know how to troubleshoot that from here....
Please search the TF700 forum or google "fastboot driver problems". That problem is so common, I really do not know what to add to advice that's out there a hundred times over....
---------- Post added at 04:29 PM ---------- Previous post was at 04:25 PM ----------
mallasorte2000 said:
i cant do anything the tablet starts - shows asus logo-go to TWRP logo screen - restarts (all in 32 seconds). Any other sugestion? if i dismantle the tablet ? or anithing else?
Thank You
Click to expand...
Click to collapse
You can always install a new r used mainboard, but that's the only reason to open it up....
Sorry man, if you do not have adb while the recovery is looping or starting up and you cannot get into fastboot, there's nothing you can do.....
Except for the really crazy and desperate "throw away reason" stuff of course. Like stuffing the tablet into the freezer in an airtight bag for 30 min, then try to boot it......
Thanks Berndblb, I was able to get through the Buster 99 instructions above.
Per the last step I would have expected the tablet to reboot, but that did not happen.
When I restarted it I got the following error when I tried to load Andriod "unrecoverable bootloader error".
I used the following file from the Asus website US_epaduser10_6_1_14_10_UpdateLauncher, based on the fact that my bootloader shows the tablet as "US_epad-10.6.1.14.10-20130801". Hopefully I used the right file for the blob file.
I've attached what I have from adb for the system flash blob and reboot. I tried to screen shoot it in a better format, but that didn't work.
Hopefully someone will be able to take a look and direct me in the right way to get this working again.
C:\adb>fastboot devices
015d2a5086641a19 fastboot
C:\adb>fastboot - i 0x0B05 flash system blob
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if fou
nd,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing
partitions
flashing unlock unlocks the device. Allows user to
flash any partition except the ones
that are related to bootloader
flashing lock_critical Prevents flashing bootloader related
partitions
flashing unlock_critical Enables flashing bootloader related
partitions
flashing get_unlock_ability Queries bootloader to see if the
device is unlocked
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootlo
ader
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
C:\adb>fastboot - i 0x0b05 reboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if fou
nd,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing
partitions
flashing unlock unlocks the device. Allows user to
flash any partition except the ones
that are related to bootloader
flashing lock_critical Prevents flashing bootloader related
partitions
flashing unlock_critical Enables flashing bootloader related
partitions
flashing get_unlock_ability Queries bootloader to see if the
device is unlocked
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootlo
ader
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
wldtravel26 said:
Thanks Berndblb, I was able to get through the Buster 99 instructions above.
Per the last step I would have expected the tablet to reboot, but that did not happen.
When I restarted it I got the following error when I tried to load Andriod "unrecoverable bootloader error".
I used the following file from the Asus website US_epaduser10_6_1_14_10_UpdateLauncher, based on the fact that my bootloader shows the tablet as "US_epad-10.6.1.14.10-20130801". Hopefully I used the right file for the blob file.
I've attached what I have from adb for the system flash blob and reboot. I tried to screen shoot it in a better format, but that didn't work.
Hopefully someone will be able to take a look and direct me in the right way to get this working again.
Click to expand...
Click to collapse
You used the correct file but I see a mistake in your command.
You put a space between the dash and the "i" in your command: fastboot - i 0x0B05 which is a command fastboot does not understand so it shows you the help file so to speak.
It is supposed to be fastboot -i 0x0B05.
See the difference?
Try it again and welcome to the world of the command line
A thousand thanks Berndblb. I was able to get it flashed and it back to the original firmware. Thought for a while, it was a total loss, so your advise was a big help.
On another note, I was having this issue with multiple custom roms, which leads me to believe it a hardware issue.
If I press on the screen too hard or lift it in a different angle, it will freeze up and try to reboot.
I was just able to get past the initial setup, but once I lifted the tablet up again, it did the same thing and froze.
I had basically been stuck, just using the tablet for strictly steaming purposes and leaving in on a table.
If anyone has had similar issues or has any insight let me know.
My wife is asking for a new Ipad if we can't get it to work properly, I'm still trying to convince her to stick with Android but this tablet isn't helping my case.
wldtravel26 said:
A thousand thanks Berndblb. I was able to get it flashed and it back to the original firmware. Thought for a while, it was a total loss, so your advise was a big help.
On another note, I was having this issue with multiple custom roms, which leads me to believe it a hardware issue.
If I press on the screen too hard or lift it in a different angle, it will freeze up and try to reboot.
I was just able to get past the initial setup, but once I lifted the tablet up again, it did the same thing and froze.
I had basically been stuck, just using the tablet for strictly steaming purposes and leaving in on a table.
If anyone has had similar issues or has any insight let me know.
My wife is asking for a new Ipad if we can't get it to work properly, I'm still trying to convince her to stick with Android but this tablet isn't helping my case.
Click to expand...
Click to collapse
damn i feel so used
grats on getting it to work again.
in regard to the troubles you are still having: is it in the Keydock or without, also a possibility that the display has an issue with the digitizer and shortens out.
cheers
Buster
I typically use it without the dock. Haven't put it in the dock in a while. Yea I was thinking the same thing where maybe something is loose inside.
Short of changing out the whole digitizer, do you know of any trouble shooting I can do if I open it up? If it keeps doing this, the tablet itself isn't worth using often. I did have a gumdrop case on it most of the time. I've got a toddler, so wanted maximum protection for it. Maybe it overheated or something?
Check out some tear down videos on YouTube and iFixit, then open it up and check all connectors you can get your hands or tools on. It does sound as if you gave a connection shorting out.
Sent from my Nexus 5X using Tapatalk
berndblb said:
If you can get into fastboot yours is a very different situation. But let me answer your questions first.
The linked method works if you have adb access in TWRP - however briely. Even if TWRP loops you should have adb access at some point (open Device Manager and watch for changes).
If TWRP is just bootlooping very quickly you may be out of luck but I have seen cases where a little window of adb access and careful timing of the commands let people push the file to internal and insmod it. But that depends on the nature of the bootloop, the skill of the user and persistence.
Now, if you have fastboot access you don't need any of that. In fastboot you have a pretty powerful tool to wipe and format partitions, flash the Asus blob if all fails, but you quite a few options....
If you can get "only occasionally" into the bootloader I would not wait much longer but perform a full wipe of the major partitions and flash the Asus system blob, returning the tablet to stock basically and giving you a fresh start.
We call it a @Buster99
Download the latest Asus firmware from here: https://www.asus.com/support/Download/28/1/0/11/fq2B3oq64av1O95u/8/
Extract it twice and copy the blob into your fastboot directory.
Issue these commands in fastboot one by one:
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system blob
fastboot -i 0x0B05 reboot
Good luck!
Click to expand...
Click to collapse
I also got into a bootloop situation and was unable to connect via adb (adb usb gave me "error: device not found") but fastboot was ok. So I tried the @Buster99 rescue. Unfortunately it failed at the flash system blob step. It gave "FAILED (data transfer failure (unknown error))...".
It's been too long since I used adb and fastboot. Lately my TF700T had become erratic, unstable and experiencing sudden reboots so I wanted to format data and do clean re-install of KatshMallow #29. I also had discovered that the digitizer had developed a blind-spot, actually more of a whole blind column of about a quarter inch wide, giving me problems swiping a TWRP button to unlock the screen. So, I went to change TWRP's screen timeout setting (TWRP 2.8.4.0 Kang) to max when suddenly it rebooted into a system bootloop. Going to TWRP would go to bootloop again at the TWRP splash screen.
Alas, I must have forgotten to set the USB debug mode after the last flashing as I am now locked out of adb. That's how I got into this unfortunate situation.
Any ideas, short of replacing TF700T's mb? Looks like this is the end of a long journey with my TF700T! :crying:
Kraka said:
I also got into a bootloop situation and was unable to connect via adb (adb usb gave me "error: device not found") but fastboot was ok. So I tried the @Buster99 rescue. Unfortunately it failed at the flash system blob step. It gave "FAILED (data transfer failure (unknown error))...".
It's been too long since I used adb and fastboot. Lately my TF700T had become erratic, unstable and experiencing sudden reboots so I wanted to format data and do clean re-install of KatshMallow #29. I also had discovered that the digitizer had developed a blind-spot, actually more of a whole blind column of about a quarter inch wide, giving me problems swiping a TWRP button to unlock the screen. So, I went to change TWRP's screen timeout setting (TWRP 2.8.4.0 Kang) to max when suddenly it rebooted into a system bootloop. Going to TWRP would go to bootloop again at the TWRP splash screen.
Alas, I must have forgotten to set the USB debug mode after the last flashing as I am now locked out of adb. That's how I got into this unfortunate situation.
Any ideas, short of replacing TF700T's mb? Looks like this is the end of a long journey with my TF700T! :crying:
Click to expand...
Click to collapse
Did you ever get it fixed? I'm in the same situation. Can't enter recovery or fastboot. Well, I entered fastboot once, chose recovery, now it boot loops straight to recovery. This sucks. Tablet worked fine for months.
If you can't boot into fastboot and you do not have adb access when in recovery, you're done. Nothing left to do.
You did not mention if you are unlocked. With a locked bootloader you can't do anything even if you have adb in recovery or if you could boot to fastboot. Sorry
It is unlocked and rooted. I see something showing up in Device Manager, only it says Google Nexus ADB interface. I can also enter the other mode with Power and Vol Up. This mode holds, however, not sure if I can do much from there.
Now I got TWRP screen stuck, so at least it's not looping. But adb commands don't produce any effect.
xxhaimbondxx said:
It is unlocked and rooted. I see something showing up in Device Manager, only it says Google Nexus ADB interface. I can also enter the other mode with Power and Vol Up. This mode holds, however, not sure if I can do much from there.
Click to expand...
Click to collapse
What do you mean? APX? No, that does not help you
xxhaimbondxx said:
Now I got TWRP screen stuck, so at least it's not looping. But adb commands don't produce any effect.
Click to expand...
Click to collapse
With TWRP booted, do you see the adb recovery interface in device manager and what do you get with "adb devices"? Do you have the drivers installed?
berndblb said:
With TWRP booted, do you see the adb recovery interface in device manager and what do you get with "adb devices"? Do you have the drivers installed?
Click to expand...
Click to collapse
This is the only thing I see in Device Manager: Google Nexus ADB interface. I installed the Universal Drivers.
When I type adb devices, I get nothing.
Well, this one time I got this:
adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
this is not troll, i just forgot command, but i understand where is problem, i just need help in issuing command, and also keeping TWRP after booting in system
okay, this is not usuall getting stuck in twrp after flashing it via fastboot.
i just need help how to boot , system
because way i installed it, is via fastboot:
' fastboot flash recovery twrp.img '
done good
but i mistakenly followed tutorial , and executed what they said should be okay (i mean it is okay, to boot it into recovery, but my phone manufacturer is stupid and don't include proper fastboot)
so i typed command
' fastboot boot recovery '
which it booted into recovery, and when i reboot into 'system' from twrp it boots into system. i had same issue, but i forgot command how to do this (and link to that solution also)
i just know that, last command, my phone misinterpret it , to boot recovery as boot way. instead of kernel, boot.img
------------------------------------------
because we have beautifull documentation on fastbood issued by google, i don't know how to make it boot system, i mean, boot.img
and, i want it to keep twrp installed, suprisingly, when i go power + volume up , sometimes it brings stock recovery and sometimes twrp.
for now, help me how to issue command, to boot kernel and not recovery
- and phone is: Allview Viva H801 , android 5.0
yea, some no name, that's why i'm asking for help
---------------
EDIT:
i think i managed to permamently flash TWRP, which was purpose, because now I can, use power on + volume up , and it always brings up TWRP (yay)
but now, i don't know how i can access bootloader (fastboot) , if i need to issue commands you instruct me to issue. i can use only twrp
kraken-gz said:
this is not troll, i just forgot command, but i understand where is problem, i just need help in issuing command, and also keeping TWRP after booting in system
okay, this is not usuall getting stuck in twrp after flashing it via fastboot.
i just need help how to boot , system
because way i installed it, is via fastboot:
' fastboot flash recovery twrp.img '
done good
but i mistakenly followed tutorial , and executed what they said should be okay (i mean it is okay, to boot it into recovery, but my phone manufacturer is stupid and don't include proper fastboot)
so i typed command
' fastboot boot recovery '
which it booted into recovery, and when i reboot into 'system' from twrp it boots into system. i had same issue, but i forgot command how to do this (and link to that solution also)
i just know that, last command, my phone misinterpret it , to boot recovery as boot way. instead of kernel, boot.img
------------------------------------------
because we have beautifull documentation on fastbood issued by google, i don't know how to make it boot system, i mean, boot.img
and, i want it to keep twrp installed, suprisingly, when i go power + volume up , sometimes it brings stock recovery and sometimes twrp.
for now, help me how to issue command, to boot kernel and not recovery
- and phone is: Allview Viva H801 , android 5.0
yea, some no name, that's why i'm asking for help
---------------
EDIT:
i think i managed to permamently flash TWRP, which was purpose, because now I can, use power on + volume up , and it always brings up TWRP (yay)
but now, i don't know how i can access bootloader (fastboot) , if i need to issue commands you instruct me to issue. i can use only twrp
Click to expand...
Click to collapse
Connect to adb while booted into TWRP and type the command:
adb reboot bootloader
That "should" boot into fastboot
For future reference, when flashing TWRP via fastboot, immediately after you flash the TWRP.img, enter the command:
adb reboot recovery
That should boot straight into TWRP and keep TWRP. If you let the device boot into any other mode than recovery, it will revert back to stock recovery, you have to boot directly into TWRP immediately after flashing it in order to keep TWRP.