I'm on ICS and never upgraded to JB. I've just unlocked my bootloader so I can do NVFlash Backup and start flashing ROM's.
I unlocked without any problems. I've rebooted into bootloader and selected the USB icon. My computer found the drivers and correctly identified as 'ASUS Android Bootloader Interface'.
From the guide http://androidroot.mobi/pages/tegra3-guide-nvflash/
I ran the command
Code:
fastboot -i 0x0b05 flash staging ebtblob.bin
I got the following output from my Windows console
Code:
sending 'staging' (1002KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 7.935s
On my tablet appears
Code:
Failed to process command download:000fa98d error(0x120003)
Also the device now appears in my windows device manager with the following error
Code:
This device cannot start. (Code 10)
{Operation Failed}
The requested operation was unsuccessful.
I've not rebooted my tablet for fear of this question...
Have I bricked my tablet?
P.S. At this point I haven't attempted to reboot my device because I'm worried it might never come back.
So I've been crawling around the internet for anyone else who's had this problem and the only person with a similar issue is
http://forum.xda-developers.com/showpost.php?p=32222050&postcount=110
So since my OP, I've removed the USB cable from my laptop, plugged it back in and I can see my TF300.
When I run
Code:
fastboot devices
I get
Code:
00000 fastboot
Which I assume means my computer can see it?
At the moment I've still not rebooted. From what I've read Staging partition is applied at boot, which I assume means no changes have been made yet?
Because my transfer failed, will anything be applied from Staging on next reboot? Or should I run a command now to prevent any changes?
Thanks
Any help on this will be much appreciated.
Just to clarify, I've still not rebooted my device since I attempted the flash and seem to have access to Fastboot. I don't want to reboot unless I know it's safe to do so.
Thanks!
I thought this morning I'd try and change my drivers and run the command again.
I thought first I'd use Universal Naked Drivers, when I select the INF 'android_winusb.inf' file I get two options both called 'Asus Fastboot Interface'.
If I select either of these I get the following error
The hash for the file is not present in the specified catalogue file. The file is probably corrupt or has been tempered with.
The other option I do seem to have is under manufacturer 'Google, Inc.' I've got 'Android Bootloader Interface'. Is that any better?
So I eventually got the Universal Naked Drivers to work (after disabling Driver signature enforce from Windows boot options) and I could see my device in device manager and from 'fastboot devices'.
So I re-ran
Code:
fastboot -i 0x0b05 flash staging ebtblob.bin
And this time it also failed with another message. In my console showed
Code:
sending 'staging' (1002 KB)...
FAILED (remote: (AccessDenied))
finished. total time: 0.014s
And my TF300 displayed the line
Code:
Failed to process command download:000fa98d error(0x30010)
But this time, I can no longer see my device from device manager or 'bootloader devices'. Windows doesn't even make the 'device inserted' sound when I plug it in.
So I finally gave in and rebooted my tablet.
To my great relief it booted successfully!
I was so nervous about doing this before hand and this experience has really knocked my confidence down.
What I'd like to know is: Is it down to the driver I'm using that I'm getting my original error? Is it a problem with my PC or my tablet?
Thanks
psjw12 said:
So I finally gave in and rebooted my tablet.
To my great relief it booted successfully!
I was so nervous about doing this before hand and this experience has really knocked my confidence down.
What I'd like to know is: Is it down to the driver I'm using that I'm getting my original error? Is it a problem with my PC or my tablet?
Thanks
Click to expand...
Click to collapse
I've seen posts where problems similar to this have been solved by just using a different USB port, one at the back if you're using a PC. At least it might be worth a try.
daws said:
I've seen posts where problems similar to this have been solved by just using a different USB port, one at the back if you're using a PC. At least it might be worth a try.
Click to expand...
Click to collapse
I'll give that a try. I'm also gonna try updating my Android toolkit and using the Android Fastboot drivers (rather than the ASUS ones).
I'll let you know how I get on with that.
psjw12 said:
I'll give that a try. I'm also gonna try updating my Android toolkit and using the Android Fastboot drivers (rather than the ASUS ones).
I'll let you know how I get on with that.
Click to expand...
Click to collapse
Did you have luck with your device? The thing is i have a similiar problem with my device. The only difference might be that my mainboard has been exchanged during an RMA. But apart from that I also have a unlocked ics bootloader and when tried:
Code:
fastboot -i 0x0b05 flash staging ebtblob.bin
everything seemed to be ok, because i got the following message:
Code:
sending 'staging' (1002 KB)...
OKAY [ 0.257s]
writing 'staging'...
OKAY [ 0.293s]
finished. total time: 0.550s
However if I check for devices afterwards, using:
Code:
fastboot devices
I get the following wierd message:
Code:
???????????? fastboot
Luckily when I restart the device it is like nothing happend. It still says "The device is unlocked" on the top left corner of the screen and the fastboot commands work as usual. I really appreciate your help.
Jan
Claudii said:
Did you have luck with your device? The thing is i have a similiar problem with my device. The only difference might be that my mainboard has been exchanged during an RMA. But apart from that I also have a unlocked ics bootloader and when tried:
Code:
fastboot -i 0x0b05 flash staging ebtblob.bin
everything seemed to be ok, because i got the following message:
Code:
sending 'staging' (1002 KB)...
OKAY [ 0.257s]
writing 'staging'...
OKAY [ 0.293s]
finished. total time: 0.550s
However if I check for devices afterwards, using:
Code:
fastboot devices
I get the following wierd message:
Code:
???????????? fastboot
Luckily when I restart the device it is like nothing happend. It still says "The device is unlocked" on the top left corner of the screen and the fastboot commands work as usual. I really appreciate your help.
Jan
Click to expand...
Click to collapse
That's odd, it's like Fastboot says image was deployed but then it doesn't apply the change. Thank goodness there's a staging partition on Asus! I also had the problem of the device disconnecting whilst trying to flash and then not showing up.
How does the tablet show up in your device manager? As 'Asus Fastboot' or 'Android Fastboot'? Mine was ASUS and I was thinking of trying the Android driver instead.
I've not tried to flash mine again since trying, I'm going to wait for an appropriate time for me to have a heart attack if it all goes wrong
Edit: The next command it wants to issue is
Code:
fastboot -i 0x0b05 reboot
I wonder if that what makes it commit the changes? Hopefully someone can answer that for me.
Related
I believe I'm bricked, and when I installed the moto stock .img and tried to flash them, I get an <unknown error> in command prompt. Please help me! can anyone give me some step by step instructions for a fix? thanks!
This may be a dumb question but I need to ask, are you using adb and can you get into fastboot?
Sent from my Xoom using Tapatalk
This is how I unbricked my xoom it will take you back to stock 3.0, then you will have to wait for the over the air updates before you can root again. Any questions, please ask. I have bricked my xoom a few times. Lol.
tabletroms.com/forums/xoom-general-discussion/1268-how-unbrick-your-moto-xoom.html
Sent from my Xoom using Tapatalk
johnny0911 said:
This may be a dumb question but I need to ask, are you using adb and can you get into fastboot?
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Yes I'm using adb, and yes, I'm in fastboot.
you must be in bootloader for fastboot commands(adb reboot bootloader)
put 4 stock .img files in platform-tools or tools(from where you are running fastboot)
that should do it.
needless to say your your bootloader must be unlocked for fastboot commands.
.................
the commands are given at motodev website.
rohit3192 said:
you must be in bootloader for fastboot commands(adb reboot bootloader)
put 4 stock .img files in platform-tools or tools(from where you are running fastboot)
that should do it.
needless to say your your bootloader must be unlocked for fastboot commands.
.................
the commands are given at motodev website.
Click to expand...
Click to collapse
I am in Fastboot protocol support. I try flashing the 4 stock .img in platform-tools, and I get errors.
C:\AndroidSDK\platform-tools>fastboot flash boot boot.img
sending 'boot' (8192 KB)...
FAILED (status read failed (Too many links))
finished. total time: 0.253s
C:\AndroidSDK\platform-tools>fastboot flash system system.img
sending 'system' (262144 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.637s
See, it isn't working. any advice! I really hope I didn't pay $700 for a paper weight!!
I also get the OK, then it fails and says this...
C:\AndroidSDK\platform-tools>fastboot flash boot boot.img
sending 'boot' (8192 KB)...
OKAY [ 0.727s]
writing 'boot'...
FAILED (status read failed (Too many links))
finished. total time: 1.319s
C:\AndroidSDK\platform-tools>fastboot flash system system.img
sending 'system' (262144 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
C:\AndroidSDK\platform-tools>fastboot flash recovery recovery.img
sending 'recovery' (12288 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.637s
C:\AndroidSDK\platform-tools>fastboot flash userdata userdata.img
I expect that you have copied all contents of "tools" folder to platform-tools folder.
Your bootloader must be unlocked to accept commands.
check the result of fastboot oem unlock.
Second : when xoom is not in bootloader mode type adb devices and check whether serial no of xoom is displayed.
Also recheck that you have java dev kit.
You may uninstall and then reinstall android sdk.
More than that I can not think of problem.
May be someone else.
rohit3192 said:
I expect that you have copied all contents of "tools" folder to platform-tools folder.
Your bootloader must be unlocked to accept commands.
check the result of fastboot oem unlock.
Second : when xoom is not in bootloader mode type adb devices and check whether serial no of xoom is displayed.
Also recheck that you have java dev kit.
You may uninstall and then reinstall android sdk.
More than that I can not think of problem.
May be someone else.
Click to expand...
Click to collapse
I have copied all of "tools" into platform tools. However, I cannot check adb devices, because I cannot leave the "Dual Core technology" screen. It's stuck on that. I cannot even enter recovery mode! I will attempt to reinstal java dev kit, and android SDK. And I will post my reply on how that works. Thanks for your patience with me. I'm just quite frustrated nothing has worked so far...
V0nice said:
I have copied all of "tools" into platform tools. However, I cannot check adb devices, because I cannot leave the "Dual Core technology" screen. It's stuck on that. I cannot even enter recovery mode! I will attempt to reinstal java dev kit, and android SDK. And I will post my reply on how that works. Thanks for your patience with me. I'm just quite frustrated nothing has worked so far...
Click to expand...
Click to collapse
I'm in the same boat as you, and with no good help. I'm getting the same answers, although my errors are a bit different than yours. If you somehow find an answer, PLEASE let me know.
hocplyr98 said:
I'm in the same boat as you, and with no good help. I'm getting the same answers, although my errors are a bit different than yours. If you somehow find an answer, PLEASE let me know.
Click to expand...
Click to collapse
Got it to work. I Google'd my issue, and I came up with a few possible issues. 1 being the usb cable, and the other being the usb port. Mine was a stock cable, so that wasn't the issue. But when I plugged the usb cable into the back of my pc (directly to the motherboards usb's) it worked, and I did not encounter the "command write failed"! successfully flashed the boot and system... ect img. and now my xoom is working!
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
To get my OPO back to stock to sell it, I decided to flash the factory image through fastboot, since after seeing the options I had, it was what I was most familiar with having owned a Nexus device in the past. I'm on a Macbook Pro, using only the fastboot and ADB files I need, which I have done in the past and it worked perfectly. Everything from the latest factory image has flashed, except the system.img file, which comes back saying this:
sending 'system' (844889 KB)...
FAILED (remote: data too large)
finished. total time: 0.003s
What can I do to fix this without bricking my device? I'm freaking out right now and don't know what to do. I don't want to unplug or exit fastboot mode in fear of bricking or doing damage to the device.
That usually means your adb/fastboot is outdated, how did you install it?
Transmitted via Bacon
I had the same problem, updating sdk helps, but if you don't want to download the large size, I'd suggest downloading Minimal fastboot and adb which works fine
Aditya Srinidhi said:
I had the same problem, updating sdk helps, but if you don't want to download the large size, I'd suggest downloading Minimal fastboot and adb which works fine
Click to expand...
Click to collapse
Minimal Fastboot and ADB should fix your problem.
I cannot get fastboot mode to work under Windows 10. I see lots of posts regarding this issue but none of the suggestions have worked for me.
I am seeing my OPO with adb and can maipulate it and reboot it:
Code:
C:\adb>adb devices
List of devices attached
15b00da9 device
But when I reboot into fastboot, "fastboot devices" gives me nothing. The phone shows fastboot mode.
Some things I have tried:
Currently using Samsung drivers
Have manually switched USB driver in device manager to Samsung ADB
Have tried 15-second usb drivers and UniversalADBDriverSetup. Neither help. Same problem.
Have followed several suggestions on installing Google USB drivers. They don't seem to show up when manually switching USB drivers. Only the Samsung ADB drivers show up.
Currently have driver signing turned off.
Does anyone have any other suggestions?
Have you tired installing the drivers while in "Test mode" ? I currently have Windows 10 insider build 14965 and I have no issue, both adb and fastboot work.
I always use this installer on all PCs I need fastboot/adb. https://drive.google.com/file/d/0B9fZIF6vzIBzT2ZtZkNSVFI5ZHc/view?usp=drivesdk
It's an all-in-one pack of the drivers and fastboot+adb. Never had problems with it and always worked for me, it gets installed in system so you can run them from any CMD
Yup I tried adb-setup.1.4.3 with driver signing disabled. I tried uninstalling what I could find and then reinstalling.
The Google drivers are confusing. Selecting update driver and then navigating to the driver location yields "No drivers for your device could be found."
Just tried it again. These are the 15-second drivers I mentioned. I say yes to "install drivers". But attempting to change USB driver either gives the error mentioned in my last post. Or if I try to choose from drivers already installed, all I see are the Samsung drivers. I cannot see Google USB drivers.
This is kinda the summary of what I've tried:
http://android.stackexchange.com/questions/118823/how-to-install-adb-drivers-on-windows-10-opo
But I can't get the Google drivers to install. Again, Windows says no software found for your hardware.
Seems more of a Windows problem at this point, I usually install that, plug the phone and that's it, never had problems (on multiple computers and OS) I can only suggest you to refresh windows installation, either from the settings "Update and recovery" (you can chose between keeping data or full wipe) or from the CD if you have it.
Okay that was weird. I tried completely removing the Samsung drivers through Add/Remove Software then I reinstalled the 15-second drivers and rebooted. I happened to leave my phone in fastboot mode. When I went into device manager I saw "Kedacom USB Device | Android Bootloader Interface" but fastboot still gave nothing.
I manually changed that driver to "Marshall London Bootloader Interface" and viola:
Code:
C:\adb>fastboot devices
15b00da9 fastboot
Now adb isn't working but I'll try manually changing that driver too.
So ADB has now stopped working. Still manually selecting the Google drivers folder yields no software for your hardware. I will now try re-adding the Samsung drivers and see if the fastboot interface remains intact.
Before I get to the Samsung driver, with the phone in normal booting and PTP mode I now see that same Kedacom USB Device with three models listed:
#recovery
Android Bootloader Interface
Kedacom KDB Interface
None of them work with ADB.
[SOLVED] Fastboot Mode
I think I figured it out. All the help postings talk about manually selecting the driver. What I found out was that I had to do this *twice*: once for regular ADB mode and once for Fastboot mode. I set the ADB mode to the Samsung ADB drivers. To change the Fastboot driver I needed to boot the phone into Fastboot. I could then change that driver to the Marshall London Bootloader Interface.
I was then able to unlock the bootloader (remember to set the OEM Unlock option under Developer Options) and then install TWRP.
What a pain.
Edit: TWRP *said* it installed but I still have the OnePlus recovery software.
kbocek said:
Edit: TWRP *said* it installed but I still have the OnePlus recovery software.
Click to expand...
Click to collapse
https://dl.twrp.me/bacon/
You got the last image from here?
Code:
fastboot oem unlock
Then
Code:
fastboot flash recovery twrp-xxxxx.img
Yes, it's unlocked.
Code:
C:\adb>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ -0.000s]
finished. total time: -0.000s
Full disclosure time. I'm actually doing this on a OnePlus X. I was also testing with a OPO and so started posting here.
Two things I think were important. 1. I didn't rename the recovery file to recovery.img. Second, I didn't issue the fastboot boot command. However:
Code:
C:\adb>fastboot flash recovery twrp-3.0.2-0-onyx-OnePlusX.img
target reported max download size of 536870912 bytes
sending 'recovery' (14758 KB)...
OKAY [ 0.469s]
writing 'recovery'...
OKAY [ 0.281s]
finished. total time: 0.750s
I also tried renaming the file to recovery.img. TWRP still doesn't show up. So I tried the boot command after installing:
Code:
C:\adb>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.469s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.516s
I've tried several versions of TWRP, 3.0.2.0, 2.8.7.0 and some other ones supposedly for the OnePlus X. The fastboot boot command does not reboot the phone. Still can't figure out the "dtb not found" message.
This thread describes my problem exactly. It mentions a custom bootloader that's supposed to work from eng.stk. Trying to find it.
http://forum.xda-developers.com/oneplus-x/help/users-twrp-t3258756
Finally. I installed the custom bootloader from here:
http://forum.xda-developers.com/devdb/project/dl/?id=20236
Bluespark V41. *Now* the bootloader is replaced and works. So, yes, there is a problem with the standard Onyx TWRP images.
Edit:
I misspoke. It's the *recovery* image that is being replaced.
thanks
thank u so much...now its working
So I saw that timduru posted the files for Nougatella 7.1 and couldn't wait to join the club. It has been a while since my TF700T has been upgraded. I had TWRP 2.8.4.0 so I wanted to upgrade to the latest version. Mistake #1!!!! I went to TWRP and got the img file put in on my sd card and installed in through the TWRP recovery. Now I get the RED unrecoverable bootloader error 0x000000. I can't get into the recovery but the tablet boots up into KatKiss without issue. I tried the TWRP app as well with no luck. I also can't get fastboot with adb fast boot working.
Windows 10 32bit
Asus Sync installed
Minimal ADB and Fastboot installed
USB debugging checked in settings
Any help would be appreciated.
Thank you.
My apologies I just saw that this is in the TF700 General Thread not the Help and Questions section. Moderator is this something I can move or do you need to do this? I did a quick search and nothing came up, but also having IE issues loading this site right now. Again thank you all!
It took a good 8 hours but I was finally able to get my tablet up and running. I took the advice of several posts and used their concepts to find the solution.
No ADB/Fastboot issue. I uninstalled all instances of ADB and all the drivers that referenced the device. I also removed Asus Sync.
Post by Accord281 [solved] Need Help: Can't get ADB to recognize device, there was a reference that people had good luck with the Google Driver. I installed Android Studio with SDK manager. I went in and then installed the Google Driver as well as the SDK manager for the stock ROM version (JB).
This still didn't work, so I reread the post and several other as well. I noticed that the recommendation was to set the USB connection to Picture not File. So I did this and ADB was working. Problem #1 checked off.
TWRP error was next. In the post by kansasboy001 Help Unrecoverable bootloader error. He posted a solution form "Buster" which worked spot on. See below.
This is the ONLY solution for this problem, worked great for me.
My solution
I have the same on my TF300t and A700 - but it seems i just managed to get my TF300t back
i tried all fastboot (reflashing recovery, boot, system etc) no dice - especially since writing system was done after 3 secs all the time.
Here how i restored my TF300T JB
download your appropriate lates firmware from Asus (WW, US etc.) and extract the zip twice so you have your blob file
install your device drivers if needed (i used Google SDK ones) (and as a Tip Win8 sucks for Fastboot stuff so try to get Win7 Vista XP for this)
Reset your device with a paperclip/needle (about 2 cm down of your sdcard slot) and hold vol-down to enter fastboot
(the folowing i did at least 10 times already but didn't erase misc)
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
fastboot -i 0x0B05 reboot
* it also took a lot longer as it should:
C:\>fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
erasing 'system'...
OKAY [ 1.695s]
sending 'system' (800935 KB)...
OKAY [133.121s]
writing 'system'...
OKAY [153.973s]
finished. total time: 288.789s
im now setting my tab up to get back to CM (which initially caused this sh1theap due to autoupdate error, same as my A700 got bricked )
hope i could help you out!
cheers
-Buster
Finally I was able to flash TWRP 3.0.0 in ADB. I also followed the post from lj50036 [twrp 2.6.3.2] [read me]. This seems to still be an issue with TWRP and the TF700T. I followed the code and it took less than 10 mins to format data.
Thank you to timduru as well as I am enjoying your build as we speak.
Click to expand...
Click to collapse
Click to expand...
Click to collapse