Hi,
I a m triing to unlock the bootloader of my shield, i have always the message
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
FAILED (command write failed (No error))
finished. total time: 0.002s
I try all usb port of my PC but alwayds problem!The dirver is installed correctly
Help would be very apprediated
Thanks a lot
Do you have USB debugging on?
Yes it is on!
Thx
Related
I know this is 100% my fault but I was hoping that maybe the genius of XDA could help me out here.
1. Was using phone fine earlier.
2. Flashed Cyanogen 5.0.2
3. Flashed the newest radio version that Cyanogen linked in that thread
4. Didn't test
5. Started playing with 'fastboot oem' commands
6. Gave up tried to send a text message
7. No keybaord
8. Long press -> Input type -> nothing listed
9. Settings -> Keyboard and locale -> nothing about the keyboard.
10. Reflashed latest Cyanogen image
11. Still not working
I think during my fun of fastboot commands I screwed something up. The phone works perfect except I don't have a keyboard, the keypad in the dialer still works. Apparently somewhere along the line I lost my nandroid backup (yes, I know fail on me) I am currently looking for a keyboard app on the web that has a QR code so that I can install a 3rd party one from market. Will let you know how that goes.
Code:
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe devices
HT9CWP807414 fastboot
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot flash radio
Radio_20100203_2_Signed_PASSION.img
sending 'radio' (24960 KB)... OKAY
writing 'radio'... OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem -?
... INFO[ERR] Command error !!!
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem lock
... INFOPlease disable the security before lock
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem secu
rity
... INFO[ERR] Command error !!!
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem help
... INFO[ERR] Command error !!!
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem s=of
f
... INFO[ERR] Command error !!!
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem ?
... INFOcommand list
INFOkeytest
INFOheap
INFOboot
INFOreset
INFOpowerdown
INFOrebootRUU
INFOrtask
INFOtask
INFOenableqxdm
INFOunlock
INFOlock
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem task
... INFOtask: Parameter error
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem task
help
... INFOtask -1911570672 is not supported
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem task
32
... INFOtask 50 is not supported
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem task
50
... INFOtask 80 is not supported
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem help
... INFO[ERR] Command error !!!
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem ?
... INFOcommand list
INFOkeytest
INFOheap
INFOboot
INFOreset
INFOpowerdown
INFOrebootRUU
INFOrtask
INFOtask
INFOenableqxdm
INFOunlock
INFOlock
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem rtas
k 32
... OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem keyt
est
... INFOstart keypad testing ...
^C
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>a
'a' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem keyt
est
^C
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot oem ?
... ^C
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem rebo
ot
... FAILED (command write failed (Unknown error))
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe devices
???????????? fastboot
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe devices
HT9CWP807414 fastboot
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem ?
... INFOcommand list
INFOkeytest
INFOheap
INFOboot
INFOreset
INFOpowerdown
INFOrebootRUU
INFOrtask
INFOtask
INFOenableqxdm
INFOunlock
INFOlock
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem task
32
... INFOtask 50 is not supported
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem task
32
... INFO[ERR] Command error !!!
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem task
?
... INFOtask 8 is not supported
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem task
?
... INFO[ERR] Command error !!!
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem ?
... INFOcommand list
INFOkeytest
INFOheap
INFOboot
INFOreset
INFOpowerdown
INFOrebootRUU
INFOrtask
INFOtask
INFOenableqxdm
INFOunlock
INFOlock
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe oem lock
... INFOPlease disable the security before lock
OKAY
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe -p
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
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
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-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
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe -p passi
on
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe getvar
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
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
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-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
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe getvar 1
getvar:1 FAILED (remote: unknown command)
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe getvar 2
getvar:2 FAILED (remote: unknown command)
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe devices
HT9CWP807414 fastboot
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe getvar 3
2
getvar:32 FAILED (remote: unknown command)
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe devices
HT9CWP807414 fastboot
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe
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
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
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-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
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe getvar s
ecurity
security: on
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe getvar s
ecurit
getvar:securit FAILED (remote: unknown command)
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>fastboot.exe flash hb
oot hboot-0.33.2012.img
sending 'hboot' (768 KB)... OKAY
writing 'hboot'... INFOsignature checking...
FAILED (remote: signature verify fail)
C:\Users\PhunkMaster\Desktop\android-sdk-windows\tools>
Here are all of the commands that I have run since I last closed the CMD window.
Update: I have found the HTC Touch input APK and installed that on my phone. I can now long press input type and select touch input but whenever the keyboard should be coming up I get a force close. I know that on my G1 the HTC Touch input was iffy at best so I am still looking for another solution.
Another update: Got 'Better Keyboard' it works! (yay!) but when I goto click on the voice input it does not. I checked my search widget and the microphone icon is missing from there as well.
Someone posted their nandroid backup of a completely (rooted) stock n1 rom, search around for it and try installing it. I ran accross it while looking for tutorials on how to flash the stock N1 rom if that helps
Update: NOOOO!!!!!!! I did a full wipe from the bootloader (factory restore, dalvik-cache, rotate settings, and what ever that 4th one was and reinstalled cyanogen mod 5.0.2) bad news: all of my settings and applications are gone, as well as my customer ringtones. Very very sad day.
Oh yea, fixed the keyboard issue and the voice input issue. So I guess we can count this as win
Should have backed up your apps with astro or titanium
Oh I had a titanium backup, I just had to reinstall them all, and reset their locations on the home screens, and reset all of my ringtones and notification tones a process that takes a whole 5 - 10 min.
OK, here it goes:
What you need:
Kindle Fire rooted.
Android SDK Mac.
Platform Tools installed.
How to get it:
Kindle Fire rooted: http://androidadvices.com/root-amazon-kindle-fire-mac-os-linux/2/#axzz1hWEX4K8B
Android SDK Mac: http://developer.android.com/sdk/index.html
Platform tools installed: Go to the tools folder in the sdk. Make sure fastboot and adb are there. IMPORTANT: Check fastboot by doubling clicking it (make sure it doesn't say binary doesn't execute).
Installing TWRP:
Follow this guide to a T with a few adjustments.
http://rootzwiki.com/topic/12343-how-to-install-twrp-20-linux/
Adjustments: Make sure that you are using the ./ version of the commands. When it says to input SU, input su.
FAQ: Stuck at fastboot, and adb is not connecting? Depending on circumstances, answer may vary. In my case, here is the terminal log (AMA is my computer):
Last login: Sun Dec 25 23:10:54 on ttys001
AMA:~ Aidan$ cd /Users/Aidan/Android/android-sdk-mac/platform-tools
AMAlatform-tools Aidan$ ./adb devices
List of devices attached
AMAlatform-tools Aidan$ ./fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
< waiting for device >
downloading 'boot.img'...
OKAY [ 5.332s]
booting...
OKAY [ 0.004s]
finished. total time: 5.336s
AMAlatform-tools Aidan$ sudo ./fastboot oem idme bootmode 4000
...
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
finished. total time: 122.653s
AMAlatform-tools Aidan$ sudo ./fastboot oem idme bootmode 4000
< waiting for device >
Will update FAQ ask people ask questions XD
Yes please.
So I have tried to root this device for about 5 hours now and I am at the end of my rope... I have downloaded and used the tool provided by rootjunkie to root this device. I get to the point where it tried to inject the root and this is the result of that.... but the read out is telling me that the changes trying to be made to the SU is that the operation is not permitted.
Will post CMD prompt below..
ANY help would be lovely, as my kindle now has supersu but it says my binary needs to be updated and when I use root check it shows I am not rooted... Thanks for the help in advance from a noobie.
The following is in my CMD prompt:
[*] NOTE this will not work unless your fastboot drivers are installed[*] see option 1 ADB Driver install.[*] Once the screen is black and says fastboot in the corner[*] press and key to continue the script.
--------------------------------------------------------------------------------
< waiting for device >
...
(bootloader) APPEND KERNEL CMDLINE
OKAY [ 0.010s]
finished. total time: 0.010s
resuming boot...
OKAY [ -0.000s]
finished. total time: -0.000s
--------------------------------------------------------------------------------
[*] your device is rebooting and will inject root files.
--------------------------------------------------------------------------------
remount succeeded
2374 KB/s (170232 bytes in 0.070s)
1 KB/s (1976 bytes in 1.000s)
3679 KB/s (75364 bytes in 0.020s)
3453 KB/s (5904943 bytes in 1.670s)
1463 KB/s (29972 bytes in 0.020s)
mkdir failed for /system/app/SuperSU, File exists
mkdir failed for /system/bin/.ext, File exists
cp: /system/xbin/su: Operation not permitted
Unable to chmod /system/xbin/su: Operation not permitted
chcon: Could not label /system/xbin/su with ubject_r:system_file:s0: Operati
on not permitted
cp: /system/xbin/daemonsu: Text file busy
cp: /system/xbin/supolicy: Operation not permitted
Unable to chmod /system/xbin/supolicy: Operation not permitted
chcon: Could not label /system/xbin/supolicy with ubject_r:system_file:s0: O
peration not permitted
cp: /system/bin/app_process32_original: Text file busy
--------------------------------------------------------------------------------
[*] Once the screen is black and says fastboot in the corner[*] press and key to continue the script.
--------------------------------------------------------------------------------
...
(bootloader) APPEND KERNEL CMDLINE
OKAY [ 0.010s]
finished. total time: 0.010s
resuming boot...
OKAY [ 0.000s]
finished. total time: 0.000s
--------------------------------------------------------------------------------
[*] your device is rebooting and will finish the root process.
--------------------------------------------------------------------------------
remount succeeded
--------------------------------------------------------------------------------
[*] one last reboot to finish process
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
[*] process finished now just wait for your device to fully boot up[*] this will take some time if you are on the Optimizing system screen.[*] NOTE now that you have root please block ota updates option 4[*] so that you can keep it safe.
--------------------------------------------------------------------------------
Press any key to continue . . .[*] RootJunky OUT
hit ENTER to return to start:
hurddude said:
So I have tried to root this device for about 5 hours now and I am at the end of my rope... I have downloaded and used the tool provided by rootjunkie to root this device. I get to the point where it tried to inject the root and this is the result of that.... but the read out is telling me that the changes trying to be made to the SU is that the operation is not permitted.
Will post CMD prompt below..
ANY help would be lovely, as my kindle now has supersu but it says my binary needs to be updated and when I use root check it shows I am not rooted... Thanks for the help in advance from a noobie.
The following is in my CMD prompt:
[*] NOTE this will not work unless your fastboot drivers are installed
[*] see option 1 ADB Driver install.
[*] Once the screen is black and says fastboot in the corner
[*] press and key to continue the script.
--------------------------------------------------------------------------------
< waiting for device >
...
(bootloader) APPEND KERNEL CMDLINE
OKAY [ 0.010s]
finished. total time: 0.010s
resuming boot...
OKAY [ -0.000s]
finished. total time: -0.000s
--------------------------------------------------------------------------------
[*] your device is rebooting and will inject root files.
--------------------------------------------------------------------------------
remount succeeded
2374 KB/s (170232 bytes in 0.070s)
1 KB/s (1976 bytes in 1.000s)
3679 KB/s (75364 bytes in 0.020s)
3453 KB/s (5904943 bytes in 1.670s)
1463 KB/s (29972 bytes in 0.020s)
mkdir failed for /system/app/SuperSU, File exists
mkdir failed for /system/bin/.ext, File exists
cp: /system/xbin/su: Operation not permitted
Unable to chmod /system/xbin/su: Operation not permitted
chcon: Could not label /system/xbin/su with ubject_r:system_file:s0: Operati
on not permitted
cp: /system/xbin/daemonsu: Text file busy
cp: /system/xbin/supolicy: Operation not permitted
Unable to chmod /system/xbin/supolicy: Operation not permitted
chcon: Could not label /system/xbin/supolicy with ubject_r:system_file:s0: O
peration not permitted
cp: /system/bin/app_process32_original: Text file busy
--------------------------------------------------------------------------------
[*] Once the screen is black and says fastboot in the corner
[*] press and key to continue the script.
--------------------------------------------------------------------------------
...
(bootloader) APPEND KERNEL CMDLINE
OKAY [ 0.010s]
finished. total time: 0.010s
resuming boot...
OKAY [ 0.000s]
finished. total time: 0.000s
--------------------------------------------------------------------------------
[*] your device is rebooting and will finish the root process.
--------------------------------------------------------------------------------
remount succeeded
--------------------------------------------------------------------------------
[*] one last reboot to finish process
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
[*] process finished now just wait for your device to fully boot up
[*] this will take some time if you are on the Optimizing system screen.
[*] NOTE now that you have root please block ota updates option 4
[*] so that you can keep it safe.
--------------------------------------------------------------------------------
Press any key to continue . . .
[*] RootJunky OUT
hit ENTER to return to start:
Click to expand...
Click to collapse
which fire do you have?
Sent from my KFFOWI using Tapatalk
sd_shadow said:
which fire do you have?
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
Well under the device options it says:
Device model:
fire (5th generation) it's the 7 inch tablet sold this past Christmas.
&
I am running the Fire OS v5.1.1
Do you need any more info?
hurddude said:
Well under the device options it says:
Device model:
fire (5th generation) it's the 7 inch tablet sold this past Christmas.
&
I am running the Fire OS v5.1.1
Do you need any more info?
Click to expand...
Click to collapse
This is the link to correct forum
http://forum.xda-developers.com/amazon-fire/help
Also
[Videos] Tutorials on how to root, flash roms and more on the Amazon Fire 5th gen.
Sent from my XT1060 using Tapatalk
I am also looking to root these devices, I have been working very hard at replacing the default firelauncher with a third party one, without the need to root. If you're interested in collaborating take a peek at my thread:
http://forum.xda-developers.com/hd8...zon-fire-hd-8-10-remove-firelauncher-t3286646
If you need anything tested on my HD 8 device, please let me know and I will do so promptly.
I still have not been successful with this root, after installing the correct adb and the software to root still getting the same errors spitting out in the cmd prompt. Any idea as to why it not letting me replace the SU!?
hurddude said:
I still have not been successful with this root, after installing the correct adb and the software to root still getting the same errors spitting out in the cmd prompt. Any idea as to why it not letting me replace the SU!?
Click to expand...
Click to collapse
If you have the 7" display Fire you are in the wrong forum. If you have an HD 8/10 then there is currently no root available.
nexus 7 2013 wifi
not sure if it has been usb debug moded from within?
anyways it won't unlock the bootloader,just sits on erasing userdata.
factory reset and cache formatting bring up errors......
can't open cache
can't mount cache
can't flash another/same bootloader because cannot unlock this one :/
using minimal adb and fastboot
trying to use adb shell to check emmc also brings up an error....
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
error: no devices/emulators found
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
0a466df4 fastboot
stuck on what else to try
C:\Minimal ADB and Fastboot>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Minimal ADB and Fastboot>fastboot flash vendor vendor.img
target reported max download size of 494927872 bytes
sending 'vendor' (133768 KB)...
OKAY [ 2.896s]
writing 'vendor'...
FAILED (remote: buffer overreads occured due to invalid sparse header)
finished. total time: 6.581s
I've never seen this error before... this is what I'm getting when I try to flash the vendor.img from the dev preview of 7.1.1... any suggestions?