Asus Stuck on restarting loop - Asus Transformer TF700
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 *
Related
Stuck in boot loop [adb & fastboot access OK]
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.
[Q] Cannot Reboot Recovery
I am running CM10.1, and wanted to upgrade to the new nightlies, Upon trying to get into recovery, I cannot use goo manager to installed recovery nor reboot to recovery. I did then try to push TWRP to my device using fastboot, that did not seem to work as any time i rebooted to recovery it would do a normal reboot. I can access fastboot, however when I volume up on "RCK" the following error comes up Key driver not found..Booting OS Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.14.4-20130329" A03 Starting Fastboot USB Download protocol Booting Recovery kernel image Booting Failed Unrecoverable bootloader error (0x00000000). I do not know if I have everything loaded into my PC correct, drivers, etc. Anyone who can help would be greatly appreciated. As i am now I can run CM 10.1 just fine, booting and everything, I just cannot get into recovery to upgrade or change roms.
ffalzone23 said: I am running CM10.1, and wanted to upgrade to the new nightlies, Upon trying to get into recovery, I cannot use goo manager to installed recovery nor reboot to recovery. I did then try to push TWRP to my device using fastboot, that did not seem to work as any time i rebooted to recovery it would do a normal reboot. I can access fastboot, however when I volume up on "RCK" the following error comes up Key driver not found..Booting OS Android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.14.4-20130329" A03 Starting Fastboot USB Download protocol Booting Recovery kernel image Booting Failed Unrecoverable bootloader error (0x00000000). I do not know if I have everything loaded into my PC correct, drivers, etc. Anyone who can help would be greatly appreciated. As i am now I can run CM 10.1 just fine, booting and everything, I just cannot get into recovery to upgrade or change roms. Click to expand... Click to collapse I don't know if this method will work on CM. You can give it a shot and report back. 1. Download the Asus firmware from Asus website and extract it once because there is anotherr zip in it. 2. Copy the second zip file to your root directory on your internal sd and reboot 3. If it works, you should see the notification on the lower right corner and click on it. You just follow the instruction to put your device back to the factory bootloader. Before you use this method, you need to move all your stuff to your computer as a back up because it will wipe everything that you have on your device.. There is another method that you could try if it does not work.. Good luck..:fingers-crossed:
I tried to download the US Firmware from the ASUS site, put it on the root of the internal, then rebooted. Did not see any notification What is this other method you speak of.... This isn't a huge deal, if I'm stuck on a RC of CM 10.1 I can deal with it. I just like to be up to date and like to reconfigure my tablets and phones from time to time. On a side note, isn't rom/recovery etc tasks with this tablet very difficult when compared to other tablets/phones?
ffalzone23 said: I tried to download the US Firmware from the ASUS site, put it on the root of the internal, then rebooted. Did not see any notification What is this other method you speak of.... This isn't a huge deal, if I'm stuck on a RC of CM 10.1 I can deal with it. I just like to be up to date and like to reconfigure my tablets and phones from time to time. On a side note, isn't rom/recovery etc tasks with this tablet very difficult when compared to other tablets/phones? Click to expand... Click to collapse Did you unzip it once? You need to have a different firmware version than the one on your system... I will find the other method and link for you..
Thanks Man. I appreciate the help!
ffalzone23 said: Thanks Man. I appreciate the help! Click to expand... Click to collapse I am still looking for the link. I forgot what it is called... I will post the link here when I find it..
LetMeKnow, Thanks for the update. Myp hone is a Droid Razr HD, and I know with that phone its possible through the bootloader to flash stock firmwear, is this possible at all with the Transformer tf700t? It would be great to have a simple tool to aid us in getting back to stock to start from square one!
ffalzone23 said: LetMeKnow, Thanks for the update. Myp hone is a Droid Razr HD, and I know with that phone its possible through the bootloader to flash stock firmwear, is this possible at all with the Transformer tf700t? It would be great to have a simple tool to aid us in getting back to stock to start from square one! Click to expand... Click to collapse By reading your post again, let me summarize it here. You know how to use fastboot, can't boot to your custom recovery (TWRP), want to flash stock recovery to fix your problem, and have try a few methods to put the stock back but it did not work. You still can get to your bootloader menu. Can you try to use this command to see if you can access to your custom recovery: fastboot boot-recovery Good luck and get back to you on the link...
this is what came up in command prompt.... C:\android-sdk\platform-tools>fastboot boot-recovery usage: fastboot [ <option> ] <command> commands: update <filename> reflash device from update.zip flashall flash boot + recovery + system flash <partition> [ <filename> ] write a file to a flash partition erase <partition> erase a flash partition format <partition> format a flash partition 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 reboot device normally 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 th an size. 0 to disable
I then did try below. but when I went to reboot, it just stayed in fastboot, so that leads me to believe there is some error there, either my bootloader is screwy or something related. I appreciate your help. At this point if anything can get me back to stock as bought, I dont care if its older versions of the firmware/bootloader/stock recovery, I'll take it from there. C:\android-sdk\platform-tools>fastboot -i 0x0B05 flash recovery recovery-jb.img sending 'recovery' (7746 KB)... OKAY [ 3.606s] writing 'recovery'... OKAY [ 2.414s] finished. total time: 6.022s C:\android-sdk\platform-tools>fastboot -i 0x0B05 reboot rebooting... finished. total time: 0.548s C:\android-sdk\platform-tools>fastboot reboot rebooting... finished. total time: 0.549s C:\android-sdk\platform-tools>fastboot reboot-bootloader rebooting into bootloader... FAILED (command write failed (Unknown error)) finished. total time: 0.636s
ffalzone23 said: I then did try below. but when I went to reboot, it just stayed in fastboot, so that leads me to believe there is some error there, either my bootloader is screwy or something related. I appreciate your help. At this point if anything can get me back to stock as bought, I dont care if its older versions of the firmware/bootloader/stock recovery, I'll take it from there. C:\android-sdk\platform-tools>fastboot -i 0x0B05 flash recovery recovery-jb.img sending 'recovery' (7746 KB)... OKAY [ 3.606s] writing 'recovery'... OKAY [ 2.414s] finished. total time: 6.022s C:\android-sdk\platform-tools>fastboot -i 0x0B05 reboot rebooting... finished. total time: 0.548s C:\android-sdk\platform-tools>fastboot reboot rebooting... finished. total time: 0.549s C:\android-sdk\platform-tools>fastboot reboot-bootloader rebooting into bootloader... FAILED (command write failed (Unknown error)) finished. total time: 0.636s Click to expand... Click to collapse I have not seen that before, so I don't know what to say... When I did fastboot TWRP recovery, I used blob file instead of img file. Do you want to download the blob file and try again? Edit: What version of TWRP did you fastboot? V2.6.3.0 is larger than our partition on the tf700. Therefore, you can not use it..
The .IMG was cwm recovery. I tried that after trying twrp most recent version. 2.6.3.1 I think. Sent from my XT926 using xda app-developers app
On a side note, when i fastboot the TWRP file to my device, the green blinking box stopped around "RCK" after that when i type in fastboot reboot to reboot the system, nothing happens. any thoughts? At this point in time, if there is a way to force stock recovery through fastboot or the stock firmware as well, i'd like to give that a try.
ffalzone23 said: On a side note, when i fastboot the TWRP file to my device, the green blinking box stopped around "RCK" after that when i type in fastboot reboot to reboot the system, nothing happens. any thoughts? At this point in time, if there is a way to force stock recovery through fastboot or the stock firmware as well, i'd like to give that a try. Click to expand... Click to collapse If fastboot doesn't work for you but you have a rooted Android, you can try installing a recovery using the dd method: Code: cd wherever/you/downloaded/twrp su dd if=openrecovery-twrp-2.6.3.1-tf700t.blob of=/dev/block/mmcblk0p4 then reboot - the bootloader should flash your new recovery with a blue progress bar and reboot again. On the second reboot, hold down volume-down to get to the bootloader menu and try entering RCK again.
ffalzone23 said: On a side note, when i fastboot the TWRP file to my device, the green blinking box stopped around "RCK" after that when i type in fastboot reboot to reboot the system, nothing happens. any thoughts? At this point in time, if there is a way to force stock recovery through fastboot or the stock firmware as well, i'd like to give that a try. Click to expand... Click to collapse You can try _that method. He always have good advices and know what he is talking about.....:good: Good luck....
_that. What screen do I have my tablet on when I run the dd command prompt ? Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app
ffalzone23 said: _that. What screen do I have my tablet on when I run the dd command prompt ? Click to expand... Click to collapse You mean the expected output? Something similar to: Code: 15836+1 records in 15836+1 records out 8108136 bytes (8.1 MB) copied, 0.152395 s, 53.2 MB/s (the above is from my PC - the TF700 is slower) Or do you mean where you enter those commands? Either via your PC in an adb shell (in this case you must first transfer the file to the TF700 with adb push or other means), or directly on your tablet with a terminal app under Android (I recommend the one from jackpal, search the Play Store)
I was able to get the same output, however when I rebooted after running the last dd code, it did not do anything, just rebooted as normal.
ffalzone23 said: I was able to get the same output, however when I rebooted after running the last dd code, it did not do anything, just rebooted as normal. Click to expand... Click to collapse What is the response when you use power and volume down buttons?
It takes me into fastboot or boot loader screen w the rck, android cold boot, and wipe data icons
[Q] Fastboot blues on the Moto X: is this the end?
Phone: Moto X / KitKat 4.4
Carrier: AT&T (XT1058)
Problem: Mysteriously stopped booting.
Good News: Fastboot is recognized.
Bad News: (bootloader) Flash write failure
Taking this guide as my playbook - http://forum.xda-developers.com/moto-x/moto-x-qa/kitkat-update-crashed-moto-x-t2535150 I tried to flash on a stock OS. Here's the main spot from the thread I'm working from-
-- Solution #2 - Medium --
1) Download the stock SBF firmware for your pre-KitKat ROM (sbf.droid-developers.org)
2) Unzip the ROM and copy the files to your fastboot directory
3) Go into Fastboot mode (power button and vol. down) and type in:
fastboot erase cache
fastboot erase customize
fastboot erase clogo
fastboot flash partition gpt.bin
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
Click to expand...
Click to collapse
The mission objective is simple: retrieve files off of sdcard and factory reset.
So with my mfastboot (not the android one), I'm trying to flash my stock OS back on so I can get a drive in windows and retrieve sdcard files. Actually, ANY OS back on at this stage of the game will be nice.
Things I have NOT done:
1. rooted the phone, or
2. unlocked the boot loader
If doing these will help, let me know.
So I get my download from sbf.droid-developers.org for 4.4.2 & ATT carrier and unpack the files.
flashing for 'partition' in gpt.bin actually works (yay), but I get the above error ("Flash write failure") for system.img and recovery.img
uh-oh
It seems others with this problem changed cables and USB ports, so I tried that. No dice.
Someone said something about permissions, so I started my command window with administrator privileges, also no luck.
Unless, of course, they meant permissions on the phone side of things? Would that actually help?
So at this juncture if my SDCard died I can go for warranty because I never did any unlocking.
However, if the SDCard can be saved, I am willing to void the warranty and unlock. The data on it is valueable to me and yes a lesson I learned here is I should start using dropbox or equivalent service. Noted.
Should I unlock the phone and try mfastboot flash system system.img, or am I already dead?
Factory reset doesn't even work, I get "no valid piv block in sp for system" I just ran mfastboot erase cache and at the command prompt I get: (bootloader) Failed to erase partition FAILED: Remote failure The phone screen says, 'Failed to erase partition cache' This doesn't sound good.... Is there anyway can get this thing booted?
Ah, nevermind, it just keeps getting errors flashing everything. Something with the phone itself is seriously wrong. I've decided to return it. I think my data is lost.
Unable to boot into recovery menu
Hey I just got a tf300 for cheap and decided to put a rom on it. I got twrp installed and got root access. The version of twrp was too old and when I updated it and got into twrp I was prompted for a password. I figured something was wrong with the version of twrp I installed and I could go go back to the previous version of twrp by using fastboot but I am unable to get into fast boot. I hold power and volume down but it boots right into twrp. I'm not able to get it to boot normally either it just boots into twrp. Has anybody run into this or have any ideas why I can't get power + volume down to bring up the recovery menu? EDIT: Oh and adb doesn't see any devices either. EDIT #2: It seems that my pc kind of recognizes that something is installed. It shows up on Device Manager as "Transformer" with the yellow exclamation point. I haven't been able to find any drivers that work with it. Anyone have a link? EDIT #3: Ok I forced the universal naked drivers to install and adb devices now shows tf300 in recovery. When I put in adb reboot bootloader it comes up with the rck android and wipe data. I used fastboot to load my original twrp blob that was working fine. I get: I:\tf300>fastboot -i 0x0b05 f sending 'recovery' (6448 KB). OKAY [ 1.895s] writing 'recovery'... OKAY [ 2.862s] finished. total time: 4.757s But when I go into recovery its still the version of twrp that was causing issues and it still asks for a password. I figured i'd do a fastboot erase of boot, cache, recovery, system, userdata and then fastboot the original twrp blob but I get: I:\tf300>fastboot erase boot < waiting for device > EDIT #4: It seems that adb recognizes by device but fastboot does not. Entering fastboot devices returns blank. Anyone know if this is an issue with the driver?
Anyone?
Ok after a couple of hours of hair pulling I figured it out. Fastboot was definitely not working witht tf300 due to drivers. Since I couldn't find any drivers for windows. I booted up my trusty linux server, installed android-tools-fastboot and voila sudo fastboot devices shows the tf300t. Reloading twrp did not work so I tried formatting the partitions by doing the following: fastboot erase system fastboot erase recovery fastboot erase userdata fastboot erase boot fastboot erase misc (The first couple of times I did this, I missed this one which caused bootloader to hang when installing twrp) fastboot erase cache I then installed the working version of twrp I had originally by: fastboot –i 0x0b05 flash recovery twrp.blob I then rebooted into recovery and twrp works great without any password prompt or errors that it could not access the partitions. I user twrp to flash 2.7.01 version of twrp and rebooted, I then used twrp to flash CM11 snapshot M7 and gapps, cleared cache and davlik and then rebooted. The CM spinning animation took a while but then it booted into CM. The topics I got all this info from are too numerous to mention. I hope this helps anyone that has ran into the same situation.
[Q] one won't start
Hi, my son's oneplus one mobile will not start up. When we press the "on" button, we see the first "1+ powered by android" screen, then the word "cyanogen" is written across the screen. This word continues to slowly blur and un-blur slightly, but the system never comes any further. (The phone is fully charged). We can also boot to a "cyanogen recovery" screen, where there are several options - where I guess a "factory reset" could be worth a try. If we do a factory reset, is there any way to maintain installed apps, and especially "progress" in these apps? Thanks for any help, Peter
You could try to use adb to backup the data, but you wont be able to save the progress in the apps I think, some apps have their progress stored online with your google account(Clash of clans for example)
ok, thanks (I don't know what "adb" is, but I'll google it). Otherwise, has anyone seen this startup problem before, and are there any good solutions? Thanks.
Hmm, seems that "adb" requires installation and/or enabling on the phone - as I can't start the phone, I don't think I can use this unfortunately.
You don't have access to adb unless it was previously enabled. Can you shed some light on what caused this situation please? It makes it a lot easier to troubleshoot. Do you know what build of Cyanogen OS was installed on the phone before this happened?
Hi, thanks for the reply. The phone's battery run out and the phone shut down. The power supply was attached, and it was attempted to turn the phone on - but this resulted in the current state where the phone stops at the "cyanogen" screen. The phone has since been charged over night, but will still not start. As to the current OS version - we are unfortunately not sure. My son says he last performed an OS update a few weeks ago.
xdzgor said: Hi, thanks for the reply. The phone's battery run out and the phone shut down. The power supply was attached, and it was attempted to turn the phone on - but this resulted in the current state where the phone stops at the "cyanogen" screen. The phone has since been charged over night, but will still not start. As to the current OS version - we are unfortunately not sure. My son says he last performed an OS update a few weeks ago. Click to expand... Click to collapse Ok, thanks. If you can get into the stock recovery you should try flashing the latest build from here, then reboot the phone.
Thanks for the suggestion - but what do you mean with "stock recovery"? We can get to a menu with these options: reboot system now apply update wipe data/factory reset wipe cache partition wipe media reboot to bootloader power down view recovery logs Can we use one of these to upload a new OS to the phone? "Apply update" gives the options: apply from ADB (does this mean adb *is* running on the phone?) choose from internal storage "Reboot to bootloader" results in a screen where it says "fastboot mode", but gets no further than this screen.
xdzgor said: Thanks for the suggestion - but what do you mean with "stock recovery"? We can get to a menu with these options: reboot system now apply update wipe data/factory reset wipe cache partition wipe media reboot to bootloader power down view recovery logs Can we use one of these to upload a new OS to the phone? "Apply update" gives the options: apply from ADB (does this mean adb *is* running on the phone?) choose from internal storage "Reboot to bootloader" results in a screen where it says "fastboot mode", but gets no further than this screen. Click to expand... Click to collapse That's the stock recovery. The "apply from adb' option is present whether you have adb enabled or not, so that's a no-go. I've just realised that you won't be able to use the recovery to flash the zip anyway, because there's no way to transfer the zip to the device without adb.. I think your only option will be to unlock the bootloader and flash the stock images with fastboot. Unfortunately this will erase all data on the phone, but right now you don't really have any other option. So what you'll need to do is this: 1. Install adb/fastboot onto your PC, the 15 seconds adb installer is probably the easiest option for this. 2. Use the reboot to bootloader option in recovery to put the phone in fastboot mode. 3. Navigate to where adb.exe and fastboot.exe are located on your PC, hold shift and right-click, then select open command prompt here. 4. Make sure your phone is connected to the PC via usb cable and (in the terminal window that popped up after the previous step) issue this command: Code: fastboot devices It should return the serial number of the device, if it does you have a working fastboot connection. If it doesn't return the serial number you might have to play around with drivers. 5. Once you know you've confirmed that you have a working fastboot connection you can check the status of the bootloader with this command: Code: fastboot oem device-info There will be a few lines of text. One of the lines will be 'bootloader unlocked: true/false". If it says true you can move on to step 6, if it says false you will need to unlock it with step 5a. 5a. Unlock the bootloader with this command: Code: fastboot oem unlock The phone will automatically go through the unlock process, and will probably try to boot into the OS. Get back into fastboot mode by using the option in recovery, or by shutting the device off by holding the power button and then using the fastboot mode button combo (hold power + volume up). 6. Once you know you have an unlocked bootloader you can now flash the stock images to the device: -Download the latest stock images to your PC from here. If you don't want the latest build you can find all stock images mirrored here thanks to @Spannaa. -Unzip the file you downloaded and put its contents into your fastboot folder (the same folder that you have adb.exe and fastboot.exe located in on your PC). -Open a command prompt from within your adb/fastboot folder (shift + right click, select open command prompt here). -Issue these fastboot commands: Code: fastboot flash modem NON-HLOS.bin Code: fastboot flash sbl1 sbl1.mbn Code: fastboot flash dbi sdi.mbn Code: fastboot flash aboot emmc_appsboot.mbn Code: fastboot flash rpm rpm.mbn Code: fastboot flash tz tz.mbn Code: fastboot flash LOGO logo.bin Code: fastboot flash oppostanvbk static_nvbk.bin Code: fastboot flash boot boot.img Code: fastboot flash cache cache.img Code: fastboot flash recovery recovery.img Code: fastboot flash system system.img Code: fastboot flash userdata userdata_64G.img or fastboot flash userdata userdata.img if you have the 16gb model) Please note: flashing the userdata will wipe your internal storage (your virtual sd card). It's possible to flash these images without that command if a full wipe isn't completely necessary in your situation. -Reboot your device with this command: Code: fastboot reboot -It's now safe to disconnect your usb cable. Click to expand... Click to collapse Hopefully the phone will boot up now.
Thanks heaps for the info. My son has now re-established his telephone - though he lost all his data/progress/photos etc.. Is there a recommended backup mechanism for the OnePlus One? (Maybe he can run a backup application on his PC once a week which takes a snapshot of his phone?)
xdzgor said: Thanks heaps for the info. My son has now re-established his telephone - though he lost all his data/progress/photos etc.. Is there a recommended backup mechanism for the OnePlus One? (Maybe he can run a backup application on his PC once a week which takes a snapshot of his phone?) Click to expand... Click to collapse The best way is by creating a backup with TWRP recovery. You'll find instructions on how to flash it (and how to make a backup) in my guide thread: http://forum.xda-developers.com/showthread.php?t=2839471