Database Info

[Q] HELP - NVFlash Bootloader failed

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.

[Q] Huawei Ascend G6-L11 Unlocked. Error on system img flashing.

Hi, so I got this phone about a month ago, with stock rom and filled up with bloat and unnessecary crap. So being the fundamentalist I am, I rooted this phone too (5th android phone I've had), and started playing with it.
By default, the bootloader is locked, so I unlocked it using Huawei's website unlock helper and fastboot.
I have no memory card to go with this phone, so I've had to try out the fastboot/adb way of doing this, and so far it's been a hit and miss.
I've been testing with SlimStock KK, and with Ascend G6 Mod, and I'm able to flash the boot and recovery successfully, but when it comes to flashing the system, it fails. Here's the output of that:
Code:
Karls-MBP% fastboot devices
90587873 fastboot
Karls-MBP% fastboot flash system /Volumes/ODIN/karleirik/Downloads/Firefox/Huawei_Ascend_G6-L11_Modded_B370_ROM/SYSTEM.img
target reported max download size of 1073741824 bytes
erasing 'system'...
OKAY [ 0.039s]
sending 'system' (1048576 KB)...
ERROR: usb_write failed with status e00002ed
FAILED (data transfer failure (Undefined error: 0))
finished. total time: 26.000s
So right now my device is softbricked. Does anyone know how to get around this problem ? Or have another approach to flashing it?
Edit: I might add that I've tried different system images, and different hardware USB ports on my laptop to no avail. I have also tried the flashall, which fails due to no product ID and adb sideload <zip> fails because of a timeout:
Code:
* failed to write data 'protocol fault (couldn't read status length): Connection reset by peer' *
- Phossk

Phossk said:
Hi, so I got this phone about a month ago, with stock rom and filled up with bloat and unnessecary crap. So being the fundamentalist I am, I rooted this phone too (5th android phone I've had), and started playing with it.
By default, the bootloader is locked, so I unlocked it using Huawei's website unlock helper and fastboot.
I have no memory card to go with this phone, so I've had to try out the fastboot/adb way of doing this, and so far it's been a hit and miss.
I've been testing with SlimStock KK, and with Ascend G6 Mod, and I'm able to flash the boot and recovery successfully, but when it comes to flashing the system, it fails. Here's the output of that:
So right now my device is softbricked. Does anyone know how to get around this problem ? Or have another approach to flashing it?
Edit: I might add that I've tried different system images, and different hardware USB ports on my laptop to no avail. I have also tried the flashall, which fails due to no product ID and adb sideload <zip> fails because of a timeout:
- Phossk
Click to expand...
Click to collapse
Try putting the .zip file inside your adb and fastboot files and just type the .zip file name when flashing instead of the whole path to the .zip
Hope this will solve your problem.

Fastboot Mode Not Working in Windows 10

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

[Help!]ADB devices not listed

Hi,
I'm tring to flash this twrp https://twrp.me/oneplus/oneplus6.html after unlocked the bootloader on my new OP6 but this is what I get from ADB:
D:\Trash\ADB>fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (26748 KB)...
OKAY [ 0.562s]
writing 'recovery'...
FAILED (remote: (recovery_a) No such partition)
finished. total time: 0.578s
Any hints??
Thx in advance!
Edit: First time I got in fastboot mode (to unlock bootloader), when I sent command "ADB devices" I saw the usual serial. Now after unlocked the bootloader, once I go in fastbode mode, there's no more devices listed.
What went wrong??

zappomax said:
Hi,
I'm tring to flash this twrp https://twrp.me/oneplus/oneplus6.html after unlocked the bootloader on my new OP6 but this is what I get from ADB:
D:\Trash\ADB>fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (26748 KB)...
OKAY [ 0.562s]
writing 'recovery'...
FAILED (remote: (recovery_a) No such partition)
finished. total time: 0.578s
Any hints??
Thx in advance!
Edit: First time I got in fastboot mode (to unlock bootloader), when I sent command "ADB devices" I saw the usual serial. Now after unlocked the bootloader, once I go in fastbode mode, there's no more devices listed.
What went wrong??
Click to expand...
Click to collapse
I don't get it. The TWRP site you posted said to fastboot into TWRP image, then flash recovery from TWRP itself. It seems like you tried to flash the image directly. As the TWRP site you posted explains, this is not how it works anymore.
Just follow the instructions from the site.
The OnePlus 6 uses the newer AB partition scheme first introduced on the Pixel 1. As such there is no recovery partition. Instead, the recovery is part of the boot image. You will temporarily boot TWRP to perform and later perform a more permanent TWRP installation. First download the TWRP zip file directly on your device. If you don't download the zip file to your device first for any reason, you will need to adb push the zip to the device because MTP is not currently working on the OnePlus 6 in TWRP. If you are unable to use adb, you can also use a USB stick with an OTG cable, if you have those handy. Power off the device. Hold volume up to get into fastboot mode. Run this command on your computer: fastboot boot twrp-3.2.1-0-enchilada.img
In TWRP, tap on Install and browse to the zip and install it (the zip will probably be in /sdcard/Downloads). TWRP will now be installed to both slots. TWRP is now installed and you can reboot and use your device as normal.
Click to expand...
Click to collapse

Command is "fastboot boot recovery.img" and when you're in twrp flash twrp zip
Envoyé de mon ONEPLUS A6003 en utilisant Tapatalk

After unlocking the bootloader (and subsequent factory reset) did you reenable the developer menu and the USB debugging? Does your device asks for debugging permission?

akxak said:
After unlocking the bootloader (and subsequent factory reset) did you reenable the developer menu and the USB debugging? Does your device asks for debugging permission?
Click to expand...
Click to collapse
Sure

zappomax said:
Sure
Click to expand...
Click to collapse
Sounds like your usb drivers are faulty. Try a different computer. Happened to me before with a Pixel XL.

Sometimes it helps just to reconnect the phone.

Sorry to all...
I just needed to read the instructions carefully on TWRP site...
So stupid and hasty

There's no recovery on this device, it's included in the boot partition. So fastboot boot the image, and then flash the installer zip.

I have a similar problem.
My phone is rooted, bootloader unlocked, TWRP and magisk installed, oxygen is ver 10.3.12. fastboot devices detects my OP6 but adb can't.
I have usb debugging enabled, all necessary drivers installed in my computer. I also tried different usb preferences like MIDI, PTP, tethering etc but all in vain. never faced such problem earlier. Earlier I could all adb commands on this devices even after rooting and installing TWRP, but now I can't !
I tested my oneplus one and OnePlus 7 also. adb commands are properly working on them, but not on OP6. What can be the reason?
Now, after trying different drivers from Google, samsung and oneplus, I am sure that the problem is from phone's end because in all cases my oneplus1 and oneplus7 are detected in adb devices without fail. Request you to read carefully before replying, since i am out of options now, tried almost all remedies available elsewhere.

ashish_jha said:
I have a similar problem.
My phone is rooted, bootloader unlocked, TWRP and magisk installed, oxygen is ver 10.3.12. fastboot devices detects my OP6 but adb can't.
I have usb debugging enabled, all necessary drivers installed in my computer. I also tried different usb preferences like MIDI, PTP, tethering etc but all in vain. never faced such problem earlier. Earlier I could all adb commands on this devices even after rooting and installing TWRP, but now I can't !
I tested my oneplus one and OnePlus 7 also. adb commands are properly working on them, but not on OP6. What can be the reason?
Now, after trying different drivers from Google, samsung and oneplus, I am sure that the problem is from phone's end because in all cases my oneplus1 and oneplus7 are detected in adb devices without fail. Request you to read carefully before replying, since i am out of options now, tried almost all remedies available elsewhere.
Click to expand...
Click to collapse

ADB Driver Installer v6.0 for Windows 10 64 Bit (2023)
ADB Driver Installer v6.0 Latest for Windows 10> It helps you to connect Android Smartphones and Tablets to Windows 7/ 8/ 10/ XP/Vista x64/ x86
www.driversforum.net

Razer bootloader unlock

Hi,
I'v got used Razer phone today with Oreo 8.1, tried to unlock boot but it failed. Commands I've ran so far (debug and oem unlock both on)
adb reboot bootloader
got the download mode
android bootloader interface version 11 driver from google.
fastboot -i 0x1532 devices
xxx40xxxx fastboot (xx are numbers)
then
fastboot -i 0x1532 flashing unlock
...
FAILED (command write failed (No error))
finished. total time: 0.004s
on the phone download mode words disappeared and no driver appear in the PC
also tried another root method with posted here in XDA for Oreo but still not working.
Please I need help as I bought the phone to root and enjoy it
Majed

NeverMind, used another laptop and i was able to do it... I think AMD has some usb filters or something