On the attached photo you see my bootloader/fastboot screen . I am trying to re-flash to the original stock OS, and I keep getting the errors of ADB device not found. I have the proper device drivers, and adb installed, I don't know what is wrong.
If anyone can help me it would be greatly appreciated.
Just to be clear are you using adb or fastboot when trying to flash from that screen?
Sent from my SM-T530NU using Tapatalk
I was trying to use adb from that screen,
but I solved it, using this link here. https://forums.motorola.com/posts/3405fb59b3
It says to skip the gpt.bin part, because when I execute that command it would give me the following error
(bootloader) Preflash validation failed
FAILED (remote failure)
Related
I've followed all the guides to a T. and my SDK is able to run nicely. However, once I've made contact w/ my device in 'usb debugging mode', tested the connection w/ "adb devices" in command prompt, and set the device to bootloader w/ the "adb reboot bootloader" command, and finally I give it the command to "fastboot oem unlock", I get an unknown error!! Please help. I have all the path variables set, and my SDK is running good, and has all the newest updates.
This is a link to a video I made of the problem. Please watch. It'll help if you can see the problem! just copy and paste - youtube.com/watch?v=2bROUZh7GRI
Thanks for your responses. I hope they come quickly!
V0nice said:
I've followed all the guides to a T. and my SDK is able to run nicely. However, once I've made contact w/ my device in 'usb debugging mode', tested the connection w/ "adb devices" in command prompt, and set the device to bootloader w/ the "adb reboot bootloader" command, and finally I give it the command to "fastboot oem unlock", I get an unknown error!! Please help. I have all the path variables set, and my SDK is running good, and has all the newest updates.
This is a link to a video I made of the problem. Please watch. It'll help if you can see the problem! just copy and paste - youtube.com/watch?v=2bROUZh7GRI
Thanks for your responses. I hope they come quickly!
Click to expand...
Click to collapse
Ok. I'm unlocked now. New problem... >.< There's always something!! now when I try to flash the recovery image, I get an unknown error.
"C:\AndroidSDK\tools>fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.
img
sending 'recovery' (3998 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
C:\AndroidSDK\tools>"
Anyone recognize why it would do this?
V0nice said:
Ok. I'm unlocked now. New problem... >.< There's always something!! now when I try to flash the recovery image, I get an unknown error.
"C:\AndroidSDK\tools>fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.
img
sending 'recovery' (3998 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
C:\AndroidSDK\tools>"
Anyone recognize why it would do this?
Click to expand...
Click to collapse
just copy and paste the command from the OP's instructions. I used the new Clockwork in the thread and just renamed it... which method are you using. I just did mine last Thursday with no issues. I used this method http://forum.xda-developers.com/showthread.php?t=1078019
HTML:
adb reboot bootloader
fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
fastboot reboot
Make sure you have the latest fastboot.exe and if all else fails start from the beginning again. Now you are sure your fastboot is unlocked....
playya said:
just copy and paste the command from the OP's instructions. I used the new Clockwork in the thread and just renamed it... which method are you using. I just did mine last Thursday with no issues. I used this method http://forum.xda-developers.com/showthread.php?t=1078019
HTML:
adb reboot bootloader
fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
fastboot reboot
Make sure you have the latest fastboot.exe and if all else fails start from the beginning again. Now you are sure your fastboot is unlocked....
Click to expand...
Click to collapse
I did just copy and paste it, and i got that error message.
V0nice said:
I did just copy and paste it, and i got that error message.
Click to expand...
Click to collapse
Did you try to do the fastboot unlock again
How did you manage to get unlock to work? Perhaps if you gave us more info on what you did?
I've been looking around at different forums to see how to get my phone back to normal and there many ways to do it and I'm stuck.I'm able to use clockwork recovery,able to use fastboot but SD card is mounted and has an error everytime I try unmount , been trying to use the command propmt not that experienced I need some guidance to how to get another rom on phone
Try to flash the stock recovery, relock the bootloader with "fastboot oem lock" and flash a RUU.
Then try again from the beginning
Do I use the command propmt or Fastboot or clockwork
dannyzat said:
Do I use the command propmt or Fastboot or clockwork
Click to expand...
Click to collapse
Open cmd prompt. Navigate to folder where your fastboot program is (i.e. c:\android is where I put mine).
Plug in phone, boot into bootloader and click power to access fastboot.
Type in the "fastboot OEM lock" command in command prompt as suggested by torxx and that will relock the bootloader. Then flash ruu in bootloader
Sent from my HTC VLE_U using Tapatalk 2
I did all of that except for the last sentence how do I flash on command prompt
dannyzat said:
I did all of that except for the last sentence how do I flash on command prompt
Click to expand...
Click to collapse
Once u relock bootloader, you are done with command prompt... I think. I havemt done it on this phone, but usually you put ruu on root of sdcard (internal in this case) and reboot into bootloader and the ruu should begin flashing from there. Make sure its named properly. I'm sure there are threads regarding this
Sent from my HTC VLE_U using Tapatalk 2
still learning how to develope android phone's
Ok I'm on bootloader but idk. How to put the ruu on my sdcard if its mounted
dannyzat said:
Ok I'm on bootloader but idk. How to put the ruu on my sdcard if its mounted
Click to expand...
Click to collapse
try the adb command just go to this link http://forum.xda-developers.com/showthread.php?t=1667929 everything is there
ok i looked at the link and try to push the rom but the adb is not even detecting my device
this is what i get:C:\Documents and Settings\Jamal\Android>adb push rom.zip/sdcard
Android Debug Bridge version 1.0.29 and then all the information about adb about the options and commands
Im on fastboot right now and using the command prompt still, the bootloader is unlocked, and i dont think adb has dected my device beacause it does this for every command: C:\Documents and Settings\Jamal\Android>adb shell
error: device not found
C:\Documents and Settings\Jamal\Android>adb remount
error: device not found
C:\Documents and Settings\Jamal\Android>adb root
error: device not found
ps. my device is connected to the computer fastboot commands work but not adb
try installing the htc drivers for the One S then retry adb
ok so i just did this recently:C:\Documents and Settings\Jamal\Android>fastboot boot rom.zip
creating boot image...
creating boot image - 468381696 bytes
downloading 'boot.img'...
OKAY [946.172s]
booting...
FAILED (remote: reproduce boot image with on-flash ramdisk error)
finished. total time: 946.656s
Is this a good sign?
Plus how do you install drivers
dannyzat said:
ok so i just did this recently:C:\Documents and Settings\Jamal\Android>fastboot boot rom.zip
creating boot image...
creating boot image - 468381696 bytes
downloading 'boot.img'...
OKAY [946.172s]
booting...
FAILED (remote: reproduce boot image with on-flash ramdisk error)
finished. total time: 946.656s
Is this a good sign?
Plus how do you install drivers
Click to expand...
Click to collapse
download HTC sync make sure you read the steps right on that link and make you flash the recovery and download the Rom and push it
thank you all for helping me out
How do I get access to unmounting my sdcard cause it keeps having errors when I try to mount it in clockwork mod recoverybut still having errors
PS. Ek07 how do I use the HTC sync manager on my phone do I go to fastboot or clockwork
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.
My phone is not rooted, but the bootloader is UNLOCKED. I'm sure.
I'm trying to install a custom recovery, but am getting this message:
FAILED (remote: Command not allowed)
1) Why?
2) Do I need to root my phone in order to install a custom recovery?
are you using adb commands to install custom recovery, if so no root is required.
Yes, I'm using adb, but my problem is I'm getting this "FAILED (remote: Command not allowed)" error, which prevents me from installing the custom recovery.
BentoEspinosa said:
Yes, I'm using adb, but my problem is I'm getting this "FAILED (remote: Command not allowed)" error, which prevents me from installing the custom recovery.
Click to expand...
Click to collapse
Have you installed correct ADB Drivers for your phone
formipad said:
Have you installed correct ADB Drivers for your phone
Click to expand...
Click to collapse
Yes.
Finally got the Android P update and I hate it. I'm wanting to revert back to Android 8. I'm a complete noob and have never attempted to root or anything like this before. Can anyone help?
Also, I'm aware ill have to do a factory reset or something like that at some point. Can someone recommend a complete back up tool for android? I've obviously made back ups before but they've only ever been certain apps or call logs etc. Is there a (preferably free) tool that literally allows to me back up, reset, and restore and end up with my phone contents as if I never reset?
wiliestseven51 said:
Finally got the Android P update and I hate it. I'm wanting to revert back to Android 8. I'm a complete noob and have never attempted to root or anything like this before. Can anyone help?
Also, I'm aware ill have to do a factory reset or something like that at some point. Can someone recommend a complete back up tool for android? I've obviously made back ups before but they've only ever been certain apps or call logs etc. Is there a (preferably free) tool that literally allows to me back up, reset, and restore and end up with my phone contents as if I never reset?
Click to expand...
Click to collapse
Edit: Downgrading is not an easy task. My understanding is you will first need to downgrade your firmware, then flash a compatible RUU. I believe this requires you to be s-off.
As far as the backup you mentioned, well that's what TWRP is for. First you'll need to unlock your bootloader which you can do by following the instructions from the htcdev website (understand this will factory reset your phone). Then find the TWRP thread which will have instructions on how to temporarily boot TWRP or permanently install TWRP to your phone's boot partition. Within TWRP you can perform the backup you desire. There is a learning curve to all of this. Good luck.
RUU download here --> https://docs.google.com/spreadsheets/d/1wIRrVQawd5rD-t9VKPQ-SdRK20RcJVZhwD7lhmPIK8w/edit#gid=0
About backup,if you are rooted, use twrp recovery o titanium backup app,otherwise google drive backup
I'm having trouble unlocking the bootloader and using fastboot. Im following the instruction son the htcdev page and the code it wants me to enter just fails every single time. When I use the 'fastboot devices' I get the verification code that everything is working. I've attached an image of what the error code. Im thinking its a windows driver issue, I download the google usb driver direct and it makes me choose one of 3 modes? I've tried all 3 and get the same error code on all 3. I've tried other commands but pretty much anything than the 'fastboot devices' causes the error code. Any ideas?
Thanks for your help.
Couldn't attach the image links so ill just type the error:
FAILED (write to device failed (unknown error))
fastboot: error : command failed
and the 3 driver choices were :
Android ADB interface
Android Bootloader interface
Android Composite ADB interface
Maybe this could help though
https://forum.xda-developers.com/u12-plus/how-to/downgrade-s-t3930103
wiliestseven51 said:
I'm having trouble unlocking the bootloader and using fastboot. Im following the instruction son the htcdev page and the code it wants me to enter just fails every single time. When I use the 'fastboot devices' I get the verification code that everything is working. I've attached an image of what the error code. Im thinking its a windows driver issue, I download the google usb driver direct and it makes me choose one of 3 modes? I've tried all 3 and get the same error code on all 3. I've tried other commands but pretty much anything than the 'fastboot devices' causes the error code. Any ideas?
Thanks for your help.
Couldn't attach the image links so ill just type the error:
FAILED (write to device failed (unknown error))
fastboot: error : command failed
and the 3 driver choices were :
Android ADB interface
Android Bootloader interface
Android Composite ADB interface
Click to expand...
Click to collapse
I use HTC windows driver version 4.10 and the fastboot binaries from step 4 of the unlock bootloader process. I've never had to make the choice you are describing.
Sounds like you are basically on the last step of the procedure, no?
Hi guys, sorry for reply after such a long time I was busy with work.
So I downloaded those drivers and have managed to get futher through the HTC unlock process. I'm now stuck on the final step. I've got the unlock code bin from htc and the dev site is telling to me to enter the code: fastboot flash unlocktoken Unlock_code.bin
I copied and paste this into the command prompt and I get this:
PS C:\Users\Wilie\Downloads\platform-tools_r29.0.2-windows\platform-tools> .\fastboot flash unlocktoken Unlock_code.bin
Sending 'unlocktoken' (0 KB) OKAY [ 1.002s]
Writing 'unlocktoken' (bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: 'UnlockToken Verify Fail!!')
fastboot: error: Command failed
From what i can tell the command works for the first part and then fails near the end. I'm completely stumped here, any ideas?
wiliestseven51 said:
Hi guys, sorry for reply after such a long time I was busy with work.
So I downloaded those drivers and have managed to get futher through the HTC unlock process. I'm now stuck on the final step. I've got the unlock code bin from htc and the dev site is telling to me to enter the code: fastboot flash unlocktoken Unlock_code.bin
I copied and paste this into the command prompt and I get this:
PS C:\Users\Wilie\Downloads\platform-tools_r29.0.2-windows\platform-tools> .\fastboot flash unlocktoken Unlock_code.bin
Sending 'unlocktoken' (0 KB) OKAY [ 1.002s]
Writing 'unlocktoken' (bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: 'UnlockToken Verify Fail!!')
fastboot: error: Command failed
From what i can tell the command works for the first part and then fails near the end. I'm completely stumped here, any ideas?
Click to expand...
Click to collapse
You have got oem unlock & adb debugging set in developers option sliders on? Try "adb reboot" command, see if your adb has been authorised on yr PC. I had a dodgy lead, using usb3 port, using shell instead of cmd cause similar problems