Related
I let my cousin borrow my prime while I went out of town for a few days and when I came back my tablet was completely wiped. All that it has on it is fastboot and fastboot only has two options wipe data or usb. My tablet won't show up in adb but when I use fastboot devices command I get 00000 fastboot. I don't know if fastboot is seeing my tablet or not I'm just hoping I can fix it. After taking with people in other forums I've been trying this method
http://forum.xda-developers.com/showthread.php?p=27354963&highlight=fastboot#post27354963
It seems to work until I get to where I have to flash Roach's modded CWM recovery. After inputting the command this is the result I get.
sending 'recovery' (5398 KB)... FAILED (command write failed (Unknown error)) finished
Does anyone here have any idea what's happening with my prime? If so please help, it will be very much appreciated.
Well, first I would make sure my PC recognizes my TPrime using "devices" command in ADB. If not, remove/uninstall any previous TPrime drivers and install Naked drivers. After that, test by using "devices" command again in ADB. After that, you can begin to utilize ADB and Fastboot commands. Also, I'd stay away from CWM and go with TWRP.
Sent from my Transformer Prime TF201 using Tapatalk 2
Second option, tell your cousin he owes you 500 bucks, go buy a new prime or infinity and give him the one he broke.
Skitsofrantik said:
I let my cousin borrow my prime while I went out of town for a few days and when I came back my tablet was completely wiped. All that it has on it is fastboot and fastboot only has two options wipe data or usb. My tablet won't show up in adb but when I use fastboot devices command I get 00000 fastboot. I don't know if fastboot is seeing my tablet or not I'm just hoping I can fix it. After taking with people in other forums I've been trying this method
http://forum.xda-developers.com/showthread.php?p=27354963&highlight=fastboot#post27354963
It seems to work until I get to where I have to flash Roach's modded CWM recovery. After inputting the command this is the result I get.
sending 'recovery' (5398 KB)... FAILED (command write failed (Unknown error)) finished
Does anyone here have any idea what's happening with my prime? If so please help, it will be very much appreciated.
Click to expand...
Click to collapse
it is highly unlikely it is bricked for good, you could try running through the steps to enable nvflash, and at the final step rather than booting into android (which you cant) run fastboot boot recovery
I've tried that but thanks for the input
SOTK said:
Well, first I would make sure my PC recognizes my TPrime using "devices" command in ADB. If not, remove/uninstall any previous TPrime drivers and install Naked drivers. After that, test by using "devices" command again in ADB. After that, you can begin to utilize ADB and Fastboot commands. Also, I'd stay away from CWM and go with TWRP.
I've tried every driver I could find. I just can't get it to show up in adb devices. going through fastboot seems to work though when i use the command for fastboot to reboot the tablet it reboots. I think I will try TWRP though.
Click to expand...
Click to collapse
lilstevie said:
it is highly unlikely it is bricked for good, you could try running through the steps to enable nvflash, and at the final step rather than booting into android (which you cant) run fastboot boot recovery
Click to expand...
Click to collapse
I'm gonna try this. Thanks for the tip.
Skitsofrantik said:
SOTK said:
Well, first I would make sure my PC recognizes my TPrime using "devices" command in ADB. If not, remove/uninstall any previous TPrime drivers and install Naked drivers. After that, test by using "devices" command again in ADB. After that, you can begin to utilize ADB and Fastboot commands. Also, I'd stay away from CWM and go with TWRP.
I've tried every driver I could find. I just can't get it to show up in adb devices. going through fastboot seems to work though when i use the command for fastboot to reboot the tablet it reboots. I think I will try TWRP though.
Click to expand...
Click to collapse
At one time, I had issues getting my PC to recognize my Prime too. You need to completely remove all prior device drivers and THEN install the naked drivers. There's a tutorial in that thread as well as a tool (I think) which you can run on your PC to help you remove previous drivers. Once you know they are gone, follow the directions to install the naked drivers. Its a little cumbersome but the process works. You're gonna keep having issues until you get your PC to recognize your Prime in ADB and Fastboot. You say Fastboot works kinda? So, in the device manager in Windows, it shows your Prime is connected as you're in Fastboot mode? If it doesn't or if it shows as an unrecognized device, I don't see how you're gonna be able to fix your issues.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Tried NVFlash
I tried NVFlash but I can't get past the first step. When I do this command fastboot -i 0x0b05 flash staging ebtblob.bin I get this result:
sending 'staging' (998 KB)...
OKAY [0.962s]
writing 'staging'...
FAILED (unknown status code)
finished. total time: 10970.597s
Anyone know what's going wrong?
SOTK said:
Skitsofrantik said:
At one time, I had issues getting my PC to recognize my Prime too. You need to completely remove all prior device drivers and THEN install the naked drivers. There's a tutorial in that thread as well as a tool (I think) which you can run on your PC to help you remove previous drivers. Once you know they are gone, follow the directions to install the naked drivers. Its a little cumbersome but the process works. You're gonna keep having issues until you get your PC to recognize your Prime in ADB and Fastboot. You say Fastboot works kinda? So, in the device manager in Windows, it shows your Prime is connected as you're in Fastboot mode? If it doesn't or if it shows as an unrecognized device, I don't see how you're gonna be able to fix your issues.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Where is the tutorial and tool? I went through it and didn't see it. Even when I completely remove the drivers, when I plug the tablet into the computer when there are no drivers it tries to install it's own drivers and sometimes they install and I get Asus android device in the device manager with Asus fastboot interface as the driver. other times it just fails to install drivers. I know if I get the drivers right I can limp this tablet back to life but it just seems like no matter what drivers i use i just cant get the tablet to show up in adb.
Click to expand...
Click to collapse
Skitsofrantik said:
SOTK said:
Where is the tutorial and tool? I went through it and didn't see it. Even when I completely remove the drivers, when I plug the tablet into the computer when there are no drivers it tries to install it's own drivers and sometimes they install and I get Asus android device in the device manager with Asus fastboot interface as the driver. other times it just fails to install drivers. I know if I get the drivers right I can limp this tablet back to life but it just seems like no matter what drivers i use i just cant get the tablet to show up in adb.
Click to expand...
Click to collapse
If you go into device manager and rightclick the asus android device then update drivers. Now do not let windows choose, do it manually and point windows to the naked driver... Also there are 2 drivers.. one for intel 86 and the other for amd... 64 the numbers are at the end of the file name if I remember correctly... be sure to choose the correct one for your pc chip otherwise yeah you can do it all day and get no where... When you try adb, I will assume you are in recovery mode and not fastboot because they are 2 different horses... If you only have fastboot then you should consider installing an older version of twrp like 2.1... I posted it somewhere in here.... that should get you into recovery where you can adb a rom to the prime.... check for posts by me, I have explained this a few times here.....
From a previous post.....
go here ....http://forum.xda-developers.com/show....php?t=1615990 this is twrp.... download then follow the fastboot install instructions
At this point you probably want to follow the nvflash instructions to install the custom bootloader since twrp says it needs it... go back here and follow instructions... http://forum.xda-developers.com/show....php?t=1774352
start again from ******now boot to recovery....
From the sounds of it you have no rom atm... no big deal... download a rom.. i suggest blackbean or eos...
blackbean found here... http://rootzwiki.com/index.php?/topi...ackbean-(8-15)
eos found here.. http://forum.xda-developers.com/show....php?t=1782413
Download and install http://forum.xda-developers.com/show....php?t=1426502 naked drivers.... follow the instructions...
I prefer blackbean... anyways.... now download nvflash from here http://androidroot.mobi/?p=452
Unzip the file.. put your rom where you find adb.exe shoudl be in C:\nvflash\tf201_nvflashpack if you put the file in C:
*******Now.... boot to recovery... connect tab to the pc.... with the windows open (nvflashpack) clcik in the window... press and hold shift button the right clcik mouse and select open command prompt here... this should give you the command prompt.
Now copy this adb devices right click in the command prompt window and paste... press enter... you should see your transformer...
now type adb push /name of rom you downloaded .zip/ sdcard
This should push the rom to your tab... it will take about 5 minutes be patient....
Install the zip through cwm....
After you accomplish this, you should complete the nvflash instructions and make your backups...
Click to expand...
Click to collapse
I installed R3 rom but my wifi cant be turned on. Latest I found that also my USB internet passthrough is not working. I got hint from one member but I absolutely dont know how to perform this.
flash the boot.img inside the R3's zip file using fastboot.
Commands:
fastboot erase cache
fastboot flash boot boot.img
How to flash something inside zip file? do I have to extract it and put it into root?
How to execute commands at all? Where to put them? What do I need to perform? I am total noob and every simple step I ever done took me a day. Now I am stuck. IF someone knows how to make this, please help.
Thank you.
First question do you have ADB installed?
Then you need to unpack boot.img from rom.zip.
When I get my answer we'll go further.
nlooooo said:
First question do you have ADB installed?
Then you need to unpack boot.img from rom.zip.
When I get my answer we'll go further.
Click to expand...
Click to collapse
I should have ADB, because I was rooting my phone month ago and ADB was required. How do I find out? I have SDK tools and i have adb.exe, adbwinapi.dll, fastboot.exe, recovery.img in C\Android. Actually I was trying to connect phone through USB and start adb.exe but it just popped out, scrolled down fast and closed (it was looking like command prompt- black window).
And I unpacked boot.img from R3.zip to my sdcard
Copy boot.img to android folder (where you have SDK platform tools installed), reboot phone to fastboot, connect it to PC and issue commands:
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot erase cache
And then reboot your phone.
Copy boot.img to android folder (where you have SDK platform tools installed), reboot phone to fastboot, connect it to PC and issue commands:
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot erase cache
And then reboot your phone.
Actually I tought this is the way, but let me tell you what is happening:
1.Turned phone off
2.entered fastboot on my phone
3.opened adb.exe in my Android-sdk/platform-tools folder
4.the adb window just opened for a 1second, everything scrolled down fast
5.adb window closed.
This is the reason why I need help, but really thank you for taking care
janickonajkrajsi said:
Copy boot.img to android folder (where you have SDK platform tools installed), reboot phone to fastboot, connect it to PC and issue commands:
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot erase cache
And then reboot your phone.
Actually I tought this is the way, but let me tell you what is happening:
1.Turned phone off
2.entered fastboot on my phone
3.opened adb.exe in my Android-sdk/platform-tools folder
4.the adb window just opened for a 1second, everything scrolled down fast
5.adb window closed.
This is the reason why I need help, but really thank you for taking care
Click to expand...
Click to collapse
You shouldn't click the adb. exe, open cmd and type the commands there.
Sent from my awesome fridge
I'm just wandering how did you manage to unlock bootloader at all.
MaartenXDA said:
You shouldn't click the adb. exe, open cmd and type the commands there.
Sent from my awesome fridge
Click to expand...
Click to collapse
yeah, I also did this according to this post http://forum.xda-developers.com/showthread.php?t=1752270
and this post http://forum.xda-developers.com/showthread.php?t=860421
but Cmd could not recognize this. I tried "fastboot devices" and this was not recognized too.
Then I reinstalled HTC drivers and then tried again. So then I was trying to open adb.exe and then you told me to issue command through cmd and here we are. sorry I am real noob in android things. I was using iphone and everything worked like magic
Isnt there a way to perform this "boot.img flashing" through recovery mod? I mean without the usb connection and without the cmd black hole
janickonajkrajsi said:
yeah, I also did this according to this post http://forum.xda-developers.com/showthread.php?t=1752270
and this post http://forum.xda-developers.com/showthread.php?t=860421
but Cmd could not recognize this. I tried "fastboot devices" and this was not recognized too.
Then I reinstalled HTC drivers and then tried again. So then I was trying to open adb.exe and then you told me to issue command through cmd and here we are. sorry I am real noob in android things. I was using iphone and everything worked like magic
Click to expand...
Click to collapse
First use the command "cd C:\Android"
After that do the commands again.
Be sure you've uninstalled HTC Sync (NOT the drivers) before doing this.
Sent from my awesome fridge
nlooooo said:
I'm just wandering how did you manage to unlock bootloader at all.
Click to expand...
Click to collapse
He didn't get your point...
Sent from my toaster using TapaToast HD
Thank you guys, now it is working.
Quote:
Originally Posted by nlooooo View Post
I'm just wandering how did you manage to unlock bootloader at all.
He didn't get your point...
Yeah it was meant like "hod did this stupid noob even managed to unlock bootloader at all. I got his point, and the right answer was "step by step guide" so actually You didnt got my point.
Dont forget that things that are automatic and obvious to you, are not obvious to everyone. My grandma is learning to work with computers and when she asks me how to send an email, I have to tell her "grab a mouse, then move it there........"
)))))))
Does not matter, thank you guys!
Once you learn to use adb and fastboot it's always the same, so my point was that you've never learned how to use it, you just typed what you saw, without any wish to learn.
Point is to try and learn, not to ask again.
Nobody said you're stupid, just lazy.
Cant get the R3 working. HTC Sense UI crashed error at lock screen
I flashed the sense revolution r3 today but could not get it working.
The following are the issues faced.
1) It starts without installing the mods package, but lacks the full sense widgets like htccontacts, htc calender etc.
2) when i flashed the r3 mod package, it gets stuck at the lock screen. The Sense UI crashes.
3) Without the mods, i faced another bug in people widget. it crashes when i click the phone dialer from it.
I am currently on sense r3.
Please help me install it in full.
When I plug my phone in fastboot on to my pc, fastboot detects it. When I then try to run a command, it says:
FAILED (command write failed (Unknown error))
finished. total time: 0.580s
After this, the screen of my phone just stays the same, except no button input works, not even holding down the power button for 10 seconds. The only way I can get out of this, is by actually pulling out the battery. After this, my phone works normally again.
How can i make the command of my PC get to my phone?
kayaven said:
When I plug my phone in fastboot on to my pc, fastboot detects it. When I then try to run a command, it says:
FAILED (command write failed (Unknown error))
finished. total time: 0.580s
After this, the screen of my phone just stays the same, except no button input works, not even holding down the power button for 10 seconds. The only way I can get out of this, is by actually pulling out the battery. After this, my phone works normally again.
How can i make the command of my PC get to my phone?
Click to expand...
Click to collapse
Do commands (like adb install .apk) work fine when phones turned on or does it freeze still ?
Will_Xda said:
Do commands (like adb install .apk) work fine when phones turned on or does it freeze still ?
Click to expand...
Click to collapse
adb will detect my phone, but as soon as I run a command, it freezes and no writing will come trough, so no they do not work.
Oh, and for some more info on my phone:
- The bootloader hasn't been unlocked;
- Running Android 4.1.1
- Already wiped it (backup gone wrong so I lost all stuff :/)
Could it be because my USB ports are just lame? (USB 2.0)
kayaven said:
adb will detect my phone, but as soon as I run a command, it freezes and no writing will come trough, so no they do not work.
Oh, and for some more info on my phone:
- The bootloader hasn't been unlocked;
- Running Android 4.1.1
- Already wiped it (backup gone wrong so I lost all stuff :/)
Could it be because my USB ports are just lame? (USB 2.0)
Click to expand...
Click to collapse
It will only work on USB2.0 for me and not on USB3.0. what operating system are you using ?
What are you trying or wish to do?
Which command?
Will_Xda said:
It will only work on USB2.0 for me and not on USB3.0. what operating system are you using ?
Click to expand...
Click to collapse
I'm using Windows 7 Ultimate x64, fastboot and adb are both running normal for the rest.
RuudM said:
What are you trying or wish to do?
Which command?
Click to expand...
Click to collapse
Well, i am trying to unlock my bootloader, but any command that writes to the phone will freeze it.
Unlocking bootloader: If I remember well, you need to have an unlock-code from HTC. Try the steps on this page from HTC Developer. Click on the picto 'unlock bootloader'.
Tutorial for the rest can be found here
RuudM said:
Unlocking bootloader: If I remember well, you need to have an unlock-code from HTC. Try the steps on this page from HTC Developer. Click on the picto 'unlock bootloader'.
Tutorial for the rest can be found here
Click to expand...
Click to collapse
I've already done that, but the command I need to run in order to get that code freezes it.
Sorry if the next is a bit 'low-profile' but it is difficult to tell where you are stuck
Just to be sure: I assume you have selected the right phone and downloaded the right fastboot-version (Windows, Linux or OsX) on HTC.com. Unpacked size of fastboot for Windows is (at this moment, from HTC) 183.651 bytes.
Phone: you are in the bootloader-screen, and (for Windows) you have a DOS-box opened on your desktop and able to execute the fastboot command.
What happens if you type in 'fastboot devices'? Does it respond?
If so, typing 'fastboot oem get_identifier_token' should respond as well. Or is that the part where you are getting stuck?
RuudM said:
Sorry if the next is a bit 'low-profile' but it is difficult to tell where you are stuck
Just to be sure: I assume you have selected the right phone and downloaded the right fastboot-version (Windows, Linux or OsX) on HTC.com. Unpacked size of fastboot for Windows is (at this moment, from HTC) 183.651 bytes.
Phone: you are in the bootloader-screen, and (for Windows) you have a DOS-box opened on your desktop and able to execute the fastboot command.
What happens if you type in 'fastboot devices'? Does it respond?
If so, typing 'fastboot oem get_identifier_token' should respond as well. Or is that the part where you are getting stuck?
Click to expand...
Click to collapse
I've got the original Android SDK fastboot, but that won't really matter, I suppose. The rest is the same. Furthermore, when i use the 'fastboot devices', it responds, but when i use something like 'fastboot oem get_identifier_token', it says FAILED (command write failed (Unknown error)), and the phone gets stuck.
I really have no idea why this is happening, i will now test if the official HTC fastboot works... :fingers-crossed:
-----------
Omg I'm an idiot, i just had it open on hboot and not fastboot >.<
I didn't know the difference Thanks a lot anyway everyone!
Q&A for [DEV] Bootloader unlock procedure and software
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [DEV] Bootloader unlock procedure and software. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
No unlock partition on KFSOWI
I tried to flash the unlock image on my KFSOWI.
This is the result:
target reported max download size of 1005584384 bytes
sending 'unlock' (0 KB)...
OKAY [ 0.006s]
writing 'unlock'...
FAILED (remote: partition does not exist)
finished. total time: 0.011s
I know this is the HDX forum - but perhaps you can help me out nevertheless
About Windows
Hey, I wanted to know if it's possible to execute the unlocking procedure entirely from Windows?.
Thanks!
pablo1036 said:
Hey, I wanted to know if it's possible to execute the unlocking procedure entirely from Windows?.
Thanks!
Click to expand...
Click to collapse
Yes
posted this in the dev section
i can see my kindle with adb... i ran the python commands and got my unlock code. when i reboot into bootloader i lose connection and can't send the fastboot commands. this is my device manager. tried uninstalling and reinstalling the drivers.
murso74 said:
posted this in the dev section
i can see my kindle with adb... i ran the python commands and got my unlock code. when i reboot into bootloader i lose connection and can't send the fastboot commands. this is my device manager. tried uninstalling and reinstalling the drivers.
Click to expand...
Click to collapse
I'm not sure how people got it on Windows, but I do know that the Linux drivers definitely work.
You can just download an Ubuntu image and create a bootable USB.
EncryptedCurse said:
I'm not sure how people got it on Windows, but I do know that the Linux drivers definitely work.
You can just download an Ubuntu image and create a bootable USB.
Click to expand...
Click to collapse
:: sigh :: i guess.. i just cant' for the life of me figure out why i can't find a damn windows fastboot driver for this thing
murso74 said:
:: sigh :: i guess.. i just cant' for the life of me figure out why i can't find a damn windows fastboot driver for this thing
Click to expand...
Click to collapse
you can try this one - working for me in win7 64 bit
- uninstall all your adb drivers
- reboot pc
- connect your kindle already waiting in fastboot mode with usb cable to pc
- check your device manager for device with yellow triangle (could/should be named fastboot (or not ))
- right click -> update driver software -> browse my pc for driver software -> search for driver software in this location -> point to uzipped folder with pdanet drivers -> next -> confirm security warning -> after successful instalation check device manager, you should see this (check attachment)
jeryll said:
you can try this one - working for me in win7 64 bit
- uninstall all your adb drivers
- reboot pc
- connect your kindle already waiting in fastboot mode with usb cable to pc
- check your device manager for device with yellow triangle (could/should be named fastboot (or not ))
- right click -> update driver software -> browse my pc for driver software -> search for driver software in this location -> point to uzipped folder with pdanet drivers -> next -> confirm security warning -> after successful instalation check device manager, you should see this (check attachment)
Click to expand...
Click to collapse
i actually did get it working... removed the device from the manager, unplugged and plugged it back it (showed up as fastboot device with the exclamation point) manually added the driver, using existing windows drivers, and used the adb driver for the fastboot driver.
unfortuantly it doesn't show up as a drive in explorer anymore, but i'll deal with that later
murso74 said:
:: sigh :: i guess.. i just cant' for the life of me figure out why i can't find a damn windows fastboot driver for this thing
Click to expand...
Click to collapse
I successfully unlocked my bootloader from Win 8.1 x64 using the method outlined here but not without some challenges. Like others I could not get my device to communicate at the fastboot prompt. Adb worked fine. Assuming it was driver related I deleted everything (included hidden devices), rebooted both devices multiple times and tried various adb/fastboot driver combinations and connection sequences. Nothing. My device knew when the USB cable was connected as evidenced by the 'ready' prompt but was otherwise unresponsive. Even tried a fastboot cable which of course didn't work. Then I tried rebooting into TWRP using power+volume-up+volume-down (three button salute) and from there rebooted the bootloader. Bingo! Everything has worked since. I restarted from TWRP many times as well via adb reboot. Hard to believe the three button salute did the trick but have no other explanation at this time. Maybe Murphy got distracted. Maybe I just got lucky.
murso74 said:
unfortuantly it doesn't show up as a drive in explorer anymore, but i'll deal with that later
Click to expand...
Click to collapse
As you probably discovered deleting the entry under "Android Devices" (can retain the driver) and then replugging your fully booted device restores the MTP driver and associated explorer mapping.
Hopefully this post will help others.
EncryptedCurse said:
I'm not sure how people got it on Windows, but I do know that the Linux drivers definitely work.
You can just download an Ubuntu image and create a bootable USB.
Click to expand...
Click to collapse
Gonna try this. got ubuntu on a usb. now got to find the linux commands.
Installed the latest Ubuntu on my other lappy. Im still very new to a linux environment. I don't remember where I saw the instructions for the commands on a linux box. I also need to know how to install the kindle drivers for linux? I do believe I have adb and fastboot installed as I can use those commands in term. Some help? Anyone. hehe. Thanks!
---------- Post added at 10:01 AM ---------- Previous post was at 09:13 AM ----------
So, i got the rules thing figured out in udev. Kindle is in fastboot and says "READY" typing in term lsub, it shows the device as device 005. Lab126, inc. I do believe that is correct as it shows as 1949. When I type fastboot 0x1949 devices, it continually just says waiting for device. Still at a stand still here. bah. Im not sure what to do next. ANyone?
holeshot77 said:
Installed the latest Ubuntu on my other lappy. Im still very new to a linux environment. I don't remember where I saw the instructions for the commands on a linux box. I also need to know how to install the kindle drivers for linux? I do believe I have adb and fastboot installed as I can use those commands in term. Some help? Anyone. hehe. Thanks!
---------- Post added at 10:01 AM ---------- Previous post was at 09:13 AM ----------
So, i got the rules thing figured out in udev. Kindle is in fastboot and says "READY" typing in term lsub, it shows the device as device 005. Lab126, inc. I do believe that is correct as it shows as 1949. When I type fastboot 0x1949 devices, it continually just says waiting for device. Still at a stand still here. bah. Im not sure what to do next. ANyone?
Click to expand...
Click to collapse
I unlocked my kindle BL with Ubuntu live on USB stick, and I must installed adb and fastboot by hand:
Code:
apt-get install android-tools-adb
apt-get install android-tools-fastboot
Its possible that versions which are on your Ubuntu preinstalled are outdated, also fastboot -i 0x1949 devices must return serial id of your kindle, and when it does, you know it recognizes your kindle and you can safely unlock kindle BL
jeryll said:
I unlocked my kindle BL with Ubuntu live on USB stick, and I must installed adb and fastboot by hand:
Code:
apt-get install android-tools-adb
apt-get install android-tools-fastboot
Its possible that versions which are on your Ubuntu preinstalled are outdated, also fastboot -i 0x1949 devices must return serial id of your kindle, and when it does, you know it recognizes your kindle and you can safely unlock kindle BL
Click to expand...
Click to collapse
Thanks Jeryll!
It is now showing the device with the fastboot -i 0x1949 devices command. So, with that, do I just follow the DEV OP?
---------- Post added at 11:22 AM ---------- Previous post was at 11:10 AM ----------
typed in adb shell and it shows error:device not found. but shows in fastboot command. hrmm? Did I miss something?
holeshot77 said:
Thanks Jeryll!
It is now showing the device with the fastboot -i 0x1949 devices command. So, with that, do I just follow the DEV OP?
---------- Post added at 11:22 AM ---------- Previous post was at 11:10 AM ----------
typed in adb shell and it shows error:device not found. but shows in fastboot command. hrmm? Did I miss something?
Click to expand...
Click to collapse
Yes, go for it! I suppose you have all prerequisites done and you have your signed unlock img ready, then all you need is working fastboot... :good: :highfive:
jeryll said:
you can try this one - working for me in win7 64 bit
- uninstall all your adb drivers
- reboot pc
- connect your kindle already waiting in fastboot mode with usb cable to pc
- check your device manager for device with yellow triangle (could/should be named fastboot (or not ))
- right click -> update driver software -> browse my pc for driver software -> search for driver software in this location -> point to uzipped folder with pdanet drivers -> next -> confirm security warning -> after successful instalation check device manager, you should see this (check attachment)
Click to expand...
Click to collapse
got fastboot working now i get this error
C:\Android>fastboot -i 0x1949 flash unlock xxxxxxxxxxx.unlock
target reported max download size of 536870912 bytes
error: cannot load 'xxxxxxxxunlock': No error
C:\Android>
davekaz said:
got fastboot working now i get this error
C:\Android>fastboot -i 0x1949 flash unlock xxxxxxxxxxx.unlock
target reported max download size of 536870912 bytes
error: cannot load 'xxxxxxxxunlock': No error
C:\Android>
Click to expand...
Click to collapse
If you are doing this in windows try open cmd, make sure you have working fastboot, then type
Code:
fastboot -i 0x1949 flash unlock
open explorer, find location of your xxxxxxxxxxx.unlock file and drag and drop it to cmd, then it should look like this
Code:
fastboot -i 0x1949 flash unlock path_to_your_xxxxxxxxxxx.unlock
then press enter and it should unlock (if the error is based on non defined path to your xxxxxxxxxxx.unlock file)
Working now I must of not spaced it correctly... I tried it again and unlocked ..green is beautiful
Sent from my Kindle Fire HDX using Tapatalk
syntax error
hey guys, i got a stupid syntax error... im doing everything exactly as it says in this thread http://forum.xda-developers.com/showpost.php?p=58897784&postcount=67
any way this is what i get:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\FBI>C:\Python27\python.exe
Python 2.7.9 (default, Dec 10 2014, 12:24:55) [MSC v.1500 32 bit (Intel)] on win
32
Type "help", "copyright", "credits" or "license" for more information.
>>> cuberhdx.py 0x*********
File "<stdin>", line 1
cuberhdx.py 0x*********
^
SyntaxError: invalid syntax
>>>
Click to expand...
Click to collapse
iv tried uppercase, lowercase, moving periods around, and various other things, but still no cigar. any help is appreciated
I think the syntax error is that the script is looking for your devices codes. Try the easy scripts from the regular dev section if you are on Windows. They are much simpler.
Sent from my KFTHWI using Tapatalk
I just waited 360 hours and unlocked a new Mi8 dipper as I have done with 5 Xiaomi phones previously. Everything looks normal. MiUI v10 says it is unlocked. With USB debugging activated the device code shows up with the 'adb devices' command. However when it comes to actually modifying the bootloader in Fastboot mode things look very locked in place. In the terminal console 'abd devices' command shows no devices. Similarly when trying to load TWRP with 'fastboot flash recovery TWRP. img' command it searches to find no device and ends with a fault. I have tried with 3 different USB-C cables on three different PC's. Two with Windows 10 with ADB tools and another on current ArchLinux with 4.20 kernel and ADB tools.
Incidentally, my wife has an untouched and therefore unlocked Pocophone F1. It does the same thing as above.
Has anyone heard of such a tbing? Is it possible that Xiaomi thinks this phone has been unlocked when in fact the bootloader is still locked?
As far as a fix goes,the unlock tool says its locked and won't try again to unlock it. This would be utterly painful were it not for Lawnchair launcher coming to the user experience rescue.
It is your computer, try to reinstall adn, driver, etc,..
If bootloader is locked, you still can type fastboot devices, but cannot flash anything with the error that you dont have permission to edit partiton.
khanhdx said:
It is your computer, try to reinstall adn, driver, etc,..
If bootloader is locked, you still can type fastboot devices, but cannot flash anything with the error that you dont have permission to edit partiton.
Click to expand...
Click to collapse
Thanks. Will try again in different variations. A few questions:
1. Is it advisable or not advisable to use a USBv3 or 3.1 port instead of USBv2 ?
2. I have tried a few different Windows 10 drivers from various sources. Can you recommend any specific driver for Xiaomi?
Thanks for helping. I will be very disappointed if I can't mod this phone.
p-we said:
Thanks. Will try again in different variations. A few questions:
1. Is it advisable or not advisable to use a USBv3 or 3.1 port instead of USBv2 ?
2. I have tried a few different Windows 10 drivers from various sources. Can you recommend any specific driver for Xiaomi?
Thanks for helping. I will be very disappointed if I can't mod this phone.
Click to expand...
Click to collapse
I think no different between USB2 and USB3 in this case.
Try uninstall all driver and app related to xiaomi.
Then Disable Signed Driver Enforcement.
Then install latest Miflash: http://en.miui.com/a-234.html (file at step 1)
Then open Mi Unlock folder (the one u found MiUnlock.exe), hold Shift + right click, select open PowerShell here.
Type cmd, enter.
Reboot phone to fastboot, connect to pc.
Type fastboot devices, enter.
khanhdx said:
I think no different between USB2 and USB3 in this case.
Try uninstall all driver and app related to xiaomi.
Then Disable Signed Driver Enforcement.
Then install latest Miflash: http://en.miui.com/a-234.html (file at step 1)
Then open Mi Unlock folder (the one u found MiUnlock.exe), hold Shift + right click, select open PowerShell here.
Type cmd, enter.
Reboot phone to fastboot, connect to pc.
Type fastboot devices, enter.
Click to expand...
Click to collapse
I think I'm close. I installed MIFlash and installed drivers. I now see the device ID in Windows PowerShell in fastboot mode which I did not have before:
C:\Users\wdirk\Downloads\miflash_unlock-en-3.3.827.31\miflash_unlock_en_3.3.827.31>fastboot devices
46265bfe fastboot
But when I enter 'fastboot flash recovery twrp.img' (the twrp.img file is in the same directory), the phone immediately goes to another mode (no fastboot logo with very small text on top left of screen) and nothing happens. So fastboot sees the device but will not write twrp recovery. Ideas?
So I tried Minimal ADB and Fastboot again. Positive that the device shows up:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
46265bfe fastboot
But goes into blank screen with very small text on top left with more inforation this time:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target didn't report max-download-size
sending 'recovery' (41796 KB)...
FAILED (command write failed (No error))
finished. total time: -0.000s
p-we said:
I think I'm close. I installed MIFlash and installed drivers. I now see the device ID in Windows PowerShell in fastboot mode which I did not have before:
C:\Users\wdirk\Downloads\miflash_unlock-en-3.3.827.31\miflash_unlock_en_3.3.827.31>fastboot devices
46265bfe fastboot
But when I enter 'fastboot flash recovery twrp.img' (the twrp.img file is in the same directory), the phone immediately goes to another mode (no fastboot logo with very small text on top left of screen) and nothing happens. So fastboot sees the device but will not write twrp recovery. Ideas?
So I tried Minimal ADB and Fastboot again. Positive that the device shows up:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
46265bfe fastboot
But goes into blank screen with very small text on top left with more inforation this time:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target didn't report max-download-size
sending 'recovery' (41796 KB)...
FAILED (command write failed (No error))
finished. total time: -0.000s
Click to expand...
Click to collapse
I never face any case like this. So maybe i can help you.
Try install different version of TWRP maybe can help..
ShafiX94 said:
Try install different version of TWRP maybe can help..
Click to expand...
Click to collapse
Very strange but I followed your steps on another PC in exactly the same way and now it has flashed TWRP successfully. It did require using blue USB3 port
Thank-you! :good:
Glade to hear you solved it.
For the record: I had the exact same problem as yours. If I recall correctly, the only thing I had to do was to rename the recovery file to: recovery.img then wait a minute or so. Which is strange, but worked.
First tried to boot Pitchblack recovery when it succeeded then tried it with TWRP (recovery.img).
If anyone finds themselves here. Go to https://forum.xda-developers.com/mi-8/how-to/guide-to-issues-flashing-unlocked-mi8-t3911389
p-we said:
If anyone finds themselves here. Go to https://forum.xda-developers.com/mi-8/how-to/guide-to-issues-flashing-unlocked-mi8-t3911389
Click to expand...
Click to collapse
I am glad that you sorted your issue.
But I can assure you that the issue was strictly caused by your PC. It truly should not matter which USB port you use. We have 3 Mi8 in our house and I have unlocked 2 of them using an older laptop with a broken usb 3.0 port.
For the benefit of others who may experience this issue.
Always. remove peripheral devices from the PC such as an external hard drive, when perform tasks such as unlocking the bootloader or unbricking a phone.
Windows should be up to date and I can tell you that professionally, we absolutely require that people temporarily disable windows defender and antivirus when attempting to resolve these kinds of issues, as you are indeed affecting the bootloader of the device.
Windows antivirus will often remove files that it miscategorises as a virus. In example, if you attempt to download and install the All In One Tool, windows defender will neuter the software 90% of the time.