Hi guys,
first - sorry for my bad english - but I'll give my best
Here's my problem:
I tried to install a custom Image, with this guide: http://forum.xda-developers.com/showthread.php?t=2271909. After I followed the instructions my Kindle Fire HD startet all the time the TWRP. I forgot to pload my CM on the the Sd Card -so I could'nt install the image. It was not possible to boot the system. Mount USB does not worked as well. After that I tried to boot via "Reboot" Recovery and now my new kindle fire hd 7" is black all the time and when I plug in my cable - windows always plays sound for "plugged in" USB device and a second after that "plugged off" and so on... No ADB connect is possible
Code:
C:\Users\xxxx\root\stuff>adb devices
List of devices attached
I'll hope that my device isn't bricked... Thanks for help!
Greetings from germany - Sebi
I doubt it's bricked. It doesn't sound like you did anything to brick it.
Are you sure it's just not locked up?
Try holding down the power button for an extended amount of time then when powering on attempt to enter recovery?
Sent from my XT907 using xda app-developers app
mrkhigh said:
I doubt it's bricked. It doesn't sound like you did anything to brick it.
Are you sure it's just not locked up?
Try holding down the power button for an extended amount of time then when powering on attempt to enter recovery?
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
No - nothing happens. I tried to hold down power button a couple of times for a about 20-30 seconds. The screen stays black. I flashed the roms with fireflash with the help of the guide...
Any other ideas?
Hiniakel said:
Hi guys,
first - sorry for my bad english - but I'll give my best
Here's my problem:
I tried to install a custom Image, with this guide: http://forum.xda-developers.com/showthread.php?t=2271909. After I followed the instructions my Kindle Fire HD startet all the time the TWRP. I forgot to pload my CM on the the Sd Card -so I could'nt install the image. It was not possible to boot the system. Mount USB does not worked as well. After that I tried to boot via "Reboot" Recovery and now my new kindle fire hd 7" is black all the time and when I plug in my cable - windows always plays sound for "plugged in" USB device and a second after that "plugged off" and so on... No ADB connect is possible
Code:
C:\Users\xxxx\root\stuff>adb devices
List of devices attached
I'll hope that my device isn't bricked... Thanks for help!
Greetings from germany - Sebi
Click to expand...
Click to collapse
It's a TWRP bootloop. Nothing major, you just need to get a ROM onto your internal SD. Search the forums on how to push a ROM using ADB using fastboot. Either that or restore your KFHD using kindle Fire FirstAide and redo the process.
Sent from myAmazon Kindle Fire HD running CM 10.2 using xda app-developers
Ok, thx - I understand. So my problem is now to get access to the device via ADB. I'm totally n00b with flashing Kindle or other tablets. I downloaded the first aid kit, but I didn't find any explaination how it works, or what shall I do.
Actually the device is all the time black (no logo - nothing) and I cannot access it via USB because its looping and USB device is on/off/on/off all the time...
I'll hope you can explain it to me to rescue my device.
Thanks a lot...
Hiniakel said:
Ok, thx - I understand. So my problem is now to get access to the device via ADB. I'm totally n00b with flashing Kindle or other tablets. I downloaded the first aid kit, but I didn't find any explaination how it works, or what shall I do.
Actually the device is all the time black (no logo - nothing) and I cannot access it via USB because its looping and USB device is on/off/on/off all the time...
I'll hope you can explain it to me to rescue my device.
Thanks a lot...
Click to expand...
Click to collapse
You need a factory fastboot cord. Your USB is useless until you restore. Cord is about 10 USD. Try eBay or their is a guy on here that sells them too. Hold the power button down for 30 seconds until it powers down and leave until fastboot cord arrives. Nothing you can do ast this point. This should be recoverable though.
Here is the link with details on KFFA usage http://forum.xda-developers.com/showthread.php?t=2096888 You will have to set up ADB drivers as well. There's a great video about it that has it's link posted a few places on here. I can post it a little later if you can't find it.
Sent from my Amazon Kindle Fire HD running CM 10.2 using xda app-developers
Thank u you for ur help. I ordered a factory cable in UK. After it's arrived, I will post my progress. I'll hope that it works.
Sebi
One last questen before: Amazon Kindle Fire hd 7" = otter2? - Which CM 10.2 should I flash to my device - if this works with factory cable...
ACHTUNG!
It is NOT otter2
but
TATE!
You'll get the right cm10.2 version here:
http://forum.xda-developers.com/showthread.php?t=2388341
Good luck!
Hiniakel said:
One last questen before: Amazon Kindle Fire hd 7" = otter2? - Which CM 10.2 should I flash to my device - if this works with factory cable...
Click to expand...
Click to collapse
CM 10.2 on Hashcode's thread posted above.
Sent from my Amazon Kindle Fire HD running CM 10.2 using xda app-developers
LinearEquation said:
CM 10.2 on Hashcode's thread posted above.
Sent from my Amazon Kindle Fire HD running CM 10.2 using xda app-developers
Click to expand...
Click to collapse
Thank u all - now waiting for my cable
So - here we go. Factory cable arrived - Frist Aide installed (C:\KFFirstAide) [Kindle Fire First Aide Revision 4.1.66-Beta for Windows 64-bit Version] running on Windows 8 64bit - but now, don't now what to do. I don't get a connection via ADB?! Is there a trick or something else?!
thx
You don't use adb commands with fastboot, you use fastboot commands. I think I heard kffa will pop a window open with adb that says waiting for device when you try to restore, just close that and let the main window continue. On another note, make sure the drivers for the device are installed for fastboot in the device manager, if they aren't it would be noted by a yellow triangle on the device, just checking because windows 8 is a pain with the driver signature enforcement on, so if it doesn't have the drivers installed, and you have a error about the signature while trying to install them, you would have to turn then driver signature enforcement off to fix the problem.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Hiniakel said:
So - here we go. Factory cable arrived - Frist Aide installed (C:\KFFirstAide) [Kindle Fire First Aide Revision 4.1.66-Beta for Windows 64-bit Version] running on Windows 8 64bit - but now, don't now what to do. I don't get a connection via ADB?! Is there a trick or something else?!
thx
Click to expand...
Click to collapse
You want to make sure your ADB drivers and KFFA have a proper path set. Once the tablet is in fast boot click on the KFFA run bat. A window will pop up. Select 'Y' for yes, then 3 to return to 7.2.3, now press any key to continue, Now click 'Y' to confirm 7.2.3 restore, click 'Y' to confirm your cord, now click NO to have KFFA boot you into fastboot as you are already in fastboot. Now sit back and wait an hour or so while KFFA restores your Kindle Fire HD.
Below is the what the file you will click on looks like.
LinearEquation said:
You want to make sure your ADB drivers and KFFA have a proper path set. Once the tablet is in fast boot click on the KFFA run bat. A window will pop up. Select 'Y' for yes, then 3 to return to 7.2.3, now press any key to continue, Now click 'Y' to confirm 7.2.3 restore, click 'Y' to confirm your cord, now click NO to have KFFA boot you into fastboot as you are already in fastboot. Now sit back and wait an hour or so while KFFA restores your Kindle Fire HD.
Below is the what the file you will click on looks like.
Click to expand...
Click to collapse
Of course - I know what I do and I have to do. I'm a system/server adminstrator. But my knowledge about flashing android tablets is not the best
Code:
***********************************************************
*The Kindle Fire HD 7 Will Now Reboot In Fastboot Mode! *
* This Process Will Fail If You Do Not Have Root *
*Installed On The Kindle Or If The Bootloader Is Damaged *
* Be Sure To Pay Attention To The Kindle For A Superuser *
* Popup, Please Click Grant Or Allow, Otherwise This *
* Process Will Fail! *
***********************************************************
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
No Connect
Hiniakel said:
Of course - I know what I do and I have to do. I'm a system/server adminstrator. But my knowledge about flashing android tablets is not the best
Code:
***********************************************************
*The Kindle Fire HD 7 Will Now Reboot In Fastboot Mode! *
* This Process Will Fail If You Do Not Have Root *
*Installed On The Kindle Or If The Bootloader Is Damaged *
* Be Sure To Pay Attention To The Kindle For A Superuser *
* Popup, Please Click Grant Or Allow, Otherwise This *
* Process Will Fail! *
***********************************************************
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
No Connect
Click to expand...
Click to collapse
When using your fastboot cord you are suppose to select N for no when asked to reboot into fastboot mode. I think you selected Y for yes. At least this is what I think is going on because I can get it to download the files from the DropBox account and get to "waiting for device" with nothing hooked up to my computer. Recheck your process and let me know.
LinearEquation said:
When using your fastboot cord you are suppose to select N for no when asked to reboot into fastboot mode. I think you selected Y for yes. At least this is what I think is going on because I can get it to download the files from the DropBox account and get to "waiting for device" with nothing hooked up to my computer. Recheck your process and let me know.
Click to expand...
Click to collapse
So - here we go:
Code:
*********************************************************
*This Option Will Use Fastboot To Flash Software To The *
*Kindle Fire HD. This Option Will Flash Software Version*
* 7.2.3 To The Following Three Partitions Boot *
* Recovey And System Then, We Will Wrap Up The *
* Process By Clearing The User Data And Davlik Cache. *
*********************************************************
Drücken Sie eine beliebige Taste . . .
Would You Like To Restore The Kindle Fire HD 7 To 7.2.3?[y/n]?y
************************************************
*You Have A Kindle Fire HD 7 Plugged In To USB*
* Using Either The Original USB Cable Or The *
* Factory USB Cable Correct ??????? *
************************************************
Drücken Sie eine beliebige Taste . . .
************************************************
*You Have A Kindle Fire HD 7 Plugged In To USB*
* Using Either The Original USB Cable Or The *
* Factory USB Cable Correct ??????? *
************************************************
Drücken Sie eine beliebige Taste . . .
Are You Sure You Want To Proceed? This Operation Wipes The User Data![y/n]?y
****************************************************
*Do You Need Us To Reboot The Kindle Into Fastboot?*
****************************************************
Would You Like Us To Reboot The Kindle Into Fastboot?[y/n]?n
--2013-10-10 22:29:31-- http://dl.dropboxusercontent.com/u/54456659/kfhd-7.2.3/images/rec
overy.img
Resolving dl.dropboxusercontent.com... 54.243.255.237
Connecting to dl.dropboxusercontent.com|54.243.255.237|:80... connected.
HTTP request sent, awaiting response... 302 FOUND
Cookie coming from dl.dropboxusercontent.com attempted to set domain to dropbox.com
Cookie coming from dl.dropboxusercontent.com attempted to set domain to dropbox.com
Location: https://dl.dropboxusercontent.com/u/54456659/kfhd-7.2.3/images/recovery.img [fol
lowing]
--2013-10-10 22:29:31-- https://dl.dropboxusercontent.com/u/54456659/kfhd-7.2.3/images/re
covery.img
Connecting to dl.dropboxusercontent.com|54.243.255.237|:443... connected.
ERROR: cannot verify dl.dropboxusercontent.com's certificate, issued by `/C=US/O=DigiCert
Inc/OU=www.digicert.com/CN=DigiCert High Assurance CA-3':
Unable to locally verify the issuer's authority.
To connect to dl.dropboxusercontent.com insecurely, use `--no-check-certificate'.
Unable to establish SSL connection.
**********************************************************************
*I Have Fetched The recovery.img - 1 More To Download................*
**********************************************************************
--2013-10-10 22:29:31-- http://dl.dropbox.com/u/54456659/kfhd-7.2.3/images/system.img
Resolving dl.dropbox.com... 23.21.78.151
Connecting to dl.dropbox.com|23.21.78.151|:80... connected.
HTTP request sent, awaiting response... 302 FOUND
Location: http://dl.dropboxusercontent.com/u/54456659/kfhd-7.2.3/images/system.img [follow
ing]
--2013-10-10 22:29:32-- http://dl.dropboxusercontent.com/u/54456659/kfhd-7.2.3/images/sys
tem.img
Resolving dl.dropboxusercontent.com... 54.243.255.237
Connecting to dl.dropboxusercontent.com|54.243.255.237|:80... connected.
HTTP request sent, awaiting response... 302 FOUND
Cookie coming from dl.dropboxusercontent.com attempted to set domain to dropbox.com
Cookie coming from dl.dropboxusercontent.com attempted to set domain to dropbox.com
Location: https://dl.dropboxusercontent.com/u/54456659/kfhd-7.2.3/images/system.img [follo
wing]
--2013-10-10 22:29:32-- https://dl.dropboxusercontent.com/u/54456659/kfhd-7.2.3/images/sy
stem.img
Connecting to dl.dropboxusercontent.com|54.243.255.237|:443... connected.
ERROR: cannot verify dl.dropboxusercontent.com's certificate, issued by `/C=US/O=DigiCert
Inc/OU=www.digicert.com/CN=DigiCert High Assurance CA-3':
Unable to locally verify the issuer's authority.
To connect to dl.dropboxusercontent.com insecurely, use `--no-check-certificate'.
Unable to establish SSL connection.
******************************************************************************************
*
*We Have Downloaded The Recovery - We Are Ready To Flash The 3 Images.....................
*
******************************************************************************************
*
Drücken Sie eine beliebige Taste . . .
< waiting for device >
Thats the way it goes....
Hiniakel said:
So - here we go:
Code:
*********************************************************
*This Option Will Use Fastboot To Flash Software To The *
*Kindle Fire HD. This Option Will Flash Software Version*
* 7.2.3 To The Following Three Partitions Boot *
* Recovey And System Then, We Will Wrap Up The *
* Process By Clearing The User Data And Davlik Cache. *
*********************************************************
Drücken Sie eine beliebige Taste . . .
Would You Like To Restore The Kindle Fire HD 7 To 7.2.3?[y/n]?y
************************************************
*You Have A Kindle Fire HD 7 Plugged In To USB*
* Using Either The Original USB Cable Or The *
* Factory USB Cable Correct ??????? *
************************************************
Drücken Sie eine beliebige Taste . . .
************************************************
*You Have A Kindle Fire HD 7 Plugged In To USB*
* Using Either The Original USB Cable Or The *
* Factory USB Cable Correct ??????? *
************************************************
Drücken Sie eine beliebige Taste . . .
Are You Sure You Want To Proceed? This Operation Wipes The User Data![y/n]?y
****************************************************
*Do You Need Us To Reboot The Kindle Into Fastboot?*
****************************************************
Would You Like Us To Reboot The Kindle Into Fastboot?[y/n]?n
--2013-10-10 22:29:31-- http://dl.dropboxusercontent.com/u/54456659/kfhd-7.2.3/images/rec
overy.img
Resolving dl.dropboxusercontent.com... 54.243.255.237
Connecting to dl.dropboxusercontent.com|54.243.255.237|:80... connected.
HTTP request sent, awaiting response... 302 FOUND
Cookie coming from dl.dropboxusercontent.com attempted to set domain to dropbox.com
Cookie coming from dl.dropboxusercontent.com attempted to set domain to dropbox.com
Location: https://dl.dropboxusercontent.com/u/54456659/kfhd-7.2.3/images/recovery.img [fol
lowing]
--2013-10-10 22:29:31-- https://dl.dropboxusercontent.com/u/54456659/kfhd-7.2.3/images/re
covery.img
Connecting to dl.dropboxusercontent.com|54.243.255.237|:443... connected.
ERROR: cannot verify dl.dropboxusercontent.com's certificate, issued by `/C=US/O=DigiCert
Inc/OU=www.digicert.com/CN=DigiCert High Assurance CA-3':
Unable to locally verify the issuer's authority.
To connect to dl.dropboxusercontent.com insecurely, use `--no-check-certificate'.
Unable to establish SSL connection.
**********************************************************************
*I Have Fetched The recovery.img - 1 More To Download................*
**********************************************************************
--2013-10-10 22:29:31-- http://dl.dropbox.com/u/54456659/kfhd-7.2.3/images/system.img
Resolving dl.dropbox.com... 23.21.78.151
Connecting to dl.dropbox.com|23.21.78.151|:80... connected.
HTTP request sent, awaiting response... 302 FOUND
Location: http://dl.dropboxusercontent.com/u/54456659/kfhd-7.2.3/images/system.img [follow
ing]
--2013-10-10 22:29:32-- http://dl.dropboxusercontent.com/u/54456659/kfhd-7.2.3/images/sys
tem.img
Resolving dl.dropboxusercontent.com... 54.243.255.237
Connecting to dl.dropboxusercontent.com|54.243.255.237|:80... connected.
HTTP request sent, awaiting response... 302 FOUND
Cookie coming from dl.dropboxusercontent.com attempted to set domain to dropbox.com
Cookie coming from dl.dropboxusercontent.com attempted to set domain to dropbox.com
Location: https://dl.dropboxusercontent.com/u/54456659/kfhd-7.2.3/images/system.img [follo
wing]
--2013-10-10 22:29:32-- https://dl.dropboxusercontent.com/u/54456659/kfhd-7.2.3/images/sy
stem.img
Connecting to dl.dropboxusercontent.com|54.243.255.237|:443... connected.
ERROR: cannot verify dl.dropboxusercontent.com's certificate, issued by `/C=US/O=DigiCert
Inc/OU=www.digicert.com/CN=DigiCert High Assurance CA-3':
Unable to locally verify the issuer's authority.
To connect to dl.dropboxusercontent.com insecurely, use `--no-check-certificate'.
Unable to establish SSL connection.
******************************************************************************************
*
*We Have Downloaded The Recovery - We Are Ready To Flash The 3 Images.....................
*
******************************************************************************************
*
Drücken Sie eine beliebige Taste . . .
< waiting for device >
Thats the way it goes....
Click to expand...
Click to collapse
I'm assuming you are using Windows 7. Open up command and type fastboot and enter, do you get a line of data? now type ADB. Do you get a lot of data?
This may sound redundent but watch this video and insure you have your ADB drivers in the correct path and up to date. https://www.youtube.com/watch?v=oaNM-lt_aHw This is the main reason you are getting the 'waiting for device' Remove the old ones and redownload to insure no corruption from initial download.
Also, this is very iomportant. Make sure you are physically logged into the admin profile of your computer. Running elevated on a different user profile will not work.
me too!
I know it has been 5 years since you posted this but in 2018 I was trying to do the same thing! Did anything you do work? including the fast boot cable?
Hiniakel said:
Hi guys,
first - sorry for my bad english - but I'll give my best
Here's my problem:
I tried to install a custom Image, with this guide: http://forum.xda-developers.com/showthread.php?t=2271909. After I followed the instructions my Kindle Fire HD startet all the time the TWRP. I forgot to pload my CM on the the Sd Card -so I could'nt install the image. It was not possible to boot the system. Mount USB does not worked as well. After that I tried to boot via "Reboot" Recovery and now my new kindle fire hd 7" is black all the time and when I plug in my cable - windows always plays sound for "plugged in" USB device and a second after that "plugged off" and so on... No ADB connect is possible
Code:
C:\Users\xxxx\root\stuff>adb devices
List of devices attached
I'll hope that my device isn't bricked... Thanks for help!
Greetings from germany - Sebi
Click to expand...
Click to collapse
Me too, but for Amazon Fire Tablet 5th gen.
Any solution works?
How to recover your Galaxy Ace's baseband
ONLY FOR WORKING DEVICES, THIS IS NOT A GUIDE ON HOW TO UNBRICK
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards, thermonuclear
* war, etc. Please do some research if you have any concerns about the
* topics included in this guide before following it! YOU are choosing to
* follow these steps, and if you point the finger at me for messing up your
* device, I will laugh at you.
*
* For any further assistance, please reach an authorized technical service.
*/
a)Pay close attention to the way the commands are shown below, i.e. it's BML not BM1, but not in caps, in minus: bmlXX where XX is the corresponding number.
b)Make sure there is enough space on /sdcard/ at least 50 megabytes to be sure no app will take over that space
c)Use extreme caution when following this guide, you're messing with the bootloader here, if you are doing it wrong, you'll kill your phone with no chance of easy-homemade-recovery like Odin or a USB Jig.
d)If you definitely did it wrong, and no recovery method helps, prepare your pocket to take your phone to a specialized tech center.
This is a very simple tutorial for those of us you who after a really, really bad brick had been seen in the need to flash a determined firmware which is not the corresponding to your phone's country. Well, fear not for I have come to save your 3G!!!
Steps:
Get a phone of the exact same model as yours, in stock (this is important because that will determine if the settings being applied are the actual facotry ones). We will refer to this as the Source phone
Root the source phone, if it's not already rooted (again, this is important, 'cause a non-rooted phone might not allow us to read /dev/bml partitions and/or execute dd command well, although I have to investigate that)
Install terminal emulator on the source phone, if it's not already installed. Alternatively, you can enable USB Debugging and use ADB instead
input the following commands (mind the caps):
Code:
# dd if=/dev/bml1 of=/sdcard/Boot_img/BcmBoot.img
# dd if=/dev/bml13 of=/sdcard/Boot_img/sysparm_dep.img
# dd if=/dev/bml14 of=/sdcard/Boot_img/HEDGE_NVRAM8_RF_LE.bin
I have used the directory "Boot_img/" for this case, you can use whatever you want lol :cyclops: but it's important to have these 3 files by themselves as we're putting them into a tar file
Perform the command (For the example I've used BOOT_S5830CVJKL4, but you should use the model name for the boot from the Source phone):
Code:
# cd /sdcard/Boot_img/
# tar -cf BOOT_S5830CVJKL4.tar ./*
Dismiss the Source phone, and ready up the "Target" phone, the one to have the newly created boot image applied.
Place the Target phone in download mode
Grab Odin3_V3.07 (Proven to work best with the Ace-i)
Once your phone's been detected, select the PIT file and the Bootloader file (I'm not telling you how to do it here, there are good ODIN tutorials for the Ace-i and I assume you search for them)
Start flashing
?????????????
PROFIT!
There is no need to revert to stock actually, although it *might* be a better idea to flash this over stock rom lol, there's less chance of bricking.
Credits:
@lyriquidperfection for the PIT Magic application, which has perfect and wonderfully helped me determine the necessary partitions to pick.
@feetsonfire for an awesome guide on flashing via ODIN
Anyone else who I may have missed, you can mention them below
Nice guide, dude! It will help all peoples, who got same like this one.
Pretty one but, i'm don't get this same problem like this guide.
I might add that use EXTREME caution using dd command and write the EXACT words as here because flashing a simple wrong partition can easily hard brick your phone.
DO NOT CONFUSE l with 1
And whichever path you choose in your sdcard, mind that it doesn't have space (you know it breaks the command)
iamareebjamal said:
I might add that use EXTREME caution using dd command and write the EXACT words as here because flashing a simple wrong partition can easily hard brick your phone.
DO NOT CONFUSE l with 1
And whichever path you choose in your sdcard, mind that it doesn't have space (you know it breaks the command)
Click to expand...
Click to collapse
Adding these details to OP, as small they may be, they are certainly true and very important
Hey guys i saw a fix on general android here on xda. It works for me on windows 8.1
Hope it works for you, maybe this can get stickied so we dont get more questions about fastboot on windows 8,1.
http://forum.xda-developers.com/showthread.php?t=2598155
As you all may now, Microsoft pushed the new driver stack in Windows 8.1 so ALL (not only USB 3.0) devices must provide a BOS descriptor. Sony ADB and Fastboot doesn't, so Windows fails to enumerate the device which is reported in Device Manager as error code 43.
This also may help if you have a USB drive or mouse and it stopped working after you upgraded from Windows 8 to Windows 8.1.
Microsoft said that the fix will come in February but for people who don't want to wait I prepaired a dirty solution:
proof - see attachment.
HTML Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
I repeat this is a REALLY DIRTY solution that may harm your system, personal data, hardware and/or cat.
Here are the steps:
0. Have a Linux or Windows LiveCD just in case something goes wrong
1. Download and extract files from attachment
2. Navigate to the folder corresponding to your system version (x86 = 32-bit, x64 = 64 bit)
3. Right-click franken-usb.bat and click "Run as Administrator"
5. Wait for it to finish and reboot the system. If everything went fine, you will boot your system successfully
6. Install ADB/Fastboot drivers just like on Windows 8
7. Connect your phone in Fastboot mode to your USB 2.0 port and check if it works
8. Enjoy and wait for official fix
How does it work:
It's not any kind of magic - it just replaces Windows 8.1's usbhub.sys and usbport.sys with Windows 8's ones.
Old files don't check for BOS descriptor so Fastboot can work.
Script updated - it should now actually copy the files but please double check if files were copied to C:\Windows\system32\Drivers!
Hope it helps you!
Regards!
Click to expand...
Click to collapse
can u help me with win8
hhamzah49 said:
Hey guys i saw a fix on general android here on xda. It works for me on windows 8.1
Hope it works for you, maybe this can get stickied so we dont get more questions about fastboot on windows 8,1.
http://forum.xda-developers.com/showthread.php?t=2598155
Click to expand...
Click to collapse
i cannot entre fastboot mode in win8
any suggestions
austinrajiv26 said:
i cannot entre fastboot mode in win8
any suggestions
Click to expand...
Click to collapse
1.) Bring up Charms by mousing over to the right of the screen
2.) Go to Settings
3.) Change PC Settings
4.) General
5.) Scroll down to Advanced Startup > Restart Now
6.) Trouble shoot
7.) Advanced options
8.) Windows startup options
9.) Restart
10.) Choose F7 (I believe) or click on "Disable driver signature enforcement"
11.) Reboot
12.) Use Flashtool drivers and install fastboot and flashmode drivers.
Its easier on windows 8 than on windows 8.1 kinda
i already tried this method but still dont get the result i want.
[GUIDE] Root Acer Iconia Tab 8 - One 8
#include /* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features...
forum.xda-developers.com
i read also some article regarding to root that the last update dont let you root the device. (maybe some kind of marketing instead of recycling the device thru custom rom. you need to buy new one)
hope someone there who know to root this greek old device