Hi,
I'm following the instructions for how to prepare my Magic to load a new ROM from the Wiki (http://wiki.xda-developers.com/index.php?pagename=HTC_Sapphire_Hacking) but I'm having problems with ADB not recognising the device.
If I boot into Fastboot mode, and use fastboot devices my phone is listed, but adb devices returns no results.
1) is it necessary to have adb working?
2) If so, any suggestions as to why it's not?
I've followed the instructions to the letter so far, and I'm worried that my phone might be a pre-production model (I review phones for a magazine - I want to try new ROMs so I can report on the new features in 1.6 and later as they come out.)
When booted normally, in Device Manager under Device Instance Path I see:
USB\VID_0BB4&PID_0C02&MI_01\6&29B48A3A&0&0001
Dunno if this helps, but the Wiki says something about changing the driver .ini file - I can't find this .ini file either, where would I look?
BTW I'm running Windows 7 release.
bpdlr said:
Hi,
I'm following the instructions for how to prepare my Magic to load a new ROM from the Wiki (http://wiki.xda-developers.com/index.php?pagename=HTC_Sapphire_Hacking) but I'm having problems with ADB not recognising the device.
If I boot into Fastboot mode, and use fastboot devices my phone is listed, but adb devices returns no results.
1) is it necessary to have adb working?
2) If so, any suggestions as to why it's not?
I've followed the instructions to the letter so far, and I'm worried that my phone might be a pre-production model (I review phones for a magazine - I want to try new ROMs so I can report on the new features in 1.6 and later as they come out.)
When booted normally, in Device Manager under Device Instance Path I see:
USB\VID_0BB4&PID_0C02&MI_01\6&29B48A3A&0&0001
Dunno if this helps, but the Wiki says something about changing the driver .ini file - I can't find this .ini file either, where would I look?
BTW I'm running Windows 7 release.
Click to expand...
Click to collapse
I had this problem and what I had to do was:
be sure no USB drives/memory cards were connected
connect the phone
uninstall USB Mass storage device from device manager under usb controllers
disconnect/reconnect the phone
install the driver from the sdk/usb_driver folder
Thanks, but...
I tried this, but still not luck with adb. I now see a new "ADB Interface" section in Device Manager, and an "HTC Dream Composite ADB Interface" device underneath, but adb devices command still returns no devices.
Sorted!
Well, I'm not sure how but I managed to get it to work, and am now the proud owner of a Magic running Cyanogen mod
Following the steps from the thread http://forum.xda-developers.com/showthread.php?p=24124828#post24124828, I lost my device on fastboot command (I followed correctly all the steps).
The device freezes on the startup screen and the PC can't recognize it properly. So the next fastboot command stays awaiting the device indefinetly.
The Android ADB Interface still remains untouchable on devices panel, but as an unspecified device. So, Windows doesn't mount the internal storage and consequently it is apparently impossible to change the damages.
Does anyone know something that can be useful?
install the correct drivers for fastboot and go ahead:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
i had the same problem
used this link helped get my device up again
http://forum.xda-developers.com/showthread.php?t=1422832
I will start at the begining
I rooted My Kindle Fire HD 2012 7, Then follow the instructions to install google maps, and amazon store stopped workings, i did a factory reset.
Now My Kindle Fire is Stuck on The Welcome Screen, I select the language and then setup wizard stoppeds working.
I have tried ADB commands
ADB devices
daemon not running. starting on port 5037
daemon started sucessfully
Listed of Devices attached
c:\adb
No devices are showing under Listed of Devices Attached
have used the drivers from
http://dl.xda-developers.com/attach.../1/3/3/1/7/6/6/Kindle_Fire_HD_ADB_Drivers.zip.
I have gone to device manager an looked at the kindle
looked at the hardware id and it displays this
USB\VID_1949&PID_0007&REV_0216
USB\VID_1949&PID_0007.
Please Help!!!
If there is anyone in the UK that in the 100 Miles of Northampton im quite willing to drive up or down to get this fixed!!!
SOVED - REFLASHED DEVICE WITH FASTBOOT CABLE AND KDF SOFTWARE
Hi,
I'm trying to repair a friend's Iconia A500 which is stuck on ACER logo.
My friend doesn't know the Android version of this tablet.
My tests have been done under Windows 7 64 and XP Pro, no antivirus, no firewall, UAC disabled on Win7 (always in run as admin mode).
All boot tricks have been tested (wipe / reset / hard reset... : power / vol - / vol+ / lock button...)
I tried to update with following files (renamed / extracted / decrypted if needed) on a FAT32 micro SD card :
Acer_A500_0.000.00_1.013.01_EMEA_GEN1_1300336887417_befd43a1
Acer_A500_0.000.00_4.010.42_EMEA_GEN3_1311244577711_036d89ae
Acer_A500_0.000.00_4.017.07_EMEA_CUS7_1311771237783_253e5e46
Acer_A500_1.031.00_WW_GEN1
Acer_A500_4.010.42_7.006.01_COM_GEN1_1316486539113_b52eab29
Acer_A500_7.014.01_041.203.01_COM_GEN1_1333444043393_2fe1ad59
Acer_A500_7.014.14_041.203.01_COM_GEN1_1333444737199_8ec8b991
Acer_A501_0.000.00_4.037.01_EMEA_TMPL_1316069683762_98ed1d97
Acer_AV041_A500_1.041.00_WW_CUS1
downgrade_not_stable
PB_G100W_4.010.01_COM_GEN1-HC3.2.1
RE-FLEXxx-ShellSHOCK-Rev7.0-CuZ-Edition
SD_PB_G100W_1.007.03_COM_GEN1
Always the same result :
ACER Logo
Erasing cache before SD update
update_package SDCARD:update.zip
SD update cmd : recovery
Booting recovery kernel image
Android logo standing up with a rotating blue "ball" in front of him.
Android logo lying down with a red triangle (containing an excalamtion mark in it) above it.
I tried the APX mode on my PCs (with reset pushed down...), tablet is recognized as APX (USB eject displays : "Eject APX"), but "apx devices" and "fastboot devices" command doesn't display any device.
adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
My tablet Vendor ID / product ID :VID_0955&PID_7820
I tried official Android drivers (adt-bundle-windows-x86_64-20131030) and others from another ZIP (root-3.2.1-V4) :
recognized as "Acer Picasso USB Boot-recovery driver".
I modified the .inf in each driver package to re-install the driver in each possible mode in order to obtain the following device name :
Android Bootloader Interface
Acer Composite ADB Interface
ADB Interface
Still unable to display my device via "adb devices"...
Any idea ?
Guys,
I'm on 9920 and need to Brick it. I cant get the tablet into Fastboot mode but then its not responding and the PC (Ubuntu and Windows 10) doesnt 'see' it on the USB port (tried different ports).
ADB sees it fine on both OSes -- I can run any ADB command, like "adb reboot bootloader" and screen goes black and at the bottom I see "=> Fastboot mode..." -- I can also run isusb, etc and it sees the device fine (its the only one on the system)
When I run 'brick-9820.sh' and the script waits at "< waiting for any device > " and nothing ever happens until I break out of it (CTRL-C).
-- rebooting the tablet boots into the OS just fine. I even tried Factory Reset from Recovery mode... did not help
I can run STEP-1.SH but I just get "Platform Not Supported" over and over until I break out of it (I think this is to be expected since I don't have root)
Any help is HIGHLY appreciated!
LivinOne said:
Guys,
I'm on 9920 and need to Brick it. I cant get the tablet into Fastboot mode but then its not responding and the PC (Ubuntu and Windows 10) doesnt 'see' it on the USB port (tried different ports).
ADB sees it fine on both OSes -- I can run any ADB command, like "adb reboot bootloader" and screen goes black and at the bottom I see "=> Fastboot mode..." -- I can also run isusb, etc and it sees the device fine (its the only one on the system)
When I run 'brick-9820.sh' and the script waits at "< waiting for any device > " and nothing ever happens until I break out of it (CTRL-C).
-- rebooting the tablet boots into the OS just fine. I even tried Factory Reset from Recovery mode... did not help
I can run STEP-1.SH but I just get "Platform Not Supported" over and over until I break out of it (I think this is to be expected since I don't have root)
Any help is HIGHLY appreciated!
Click to expand...
Click to collapse
Try it to factory reset by using secret code from Amazon search ;oobe
Try this to use exploit package for Douglas from @k4y0z: https://forum.xda-developers.com/hd8-hd10/orig-development/unlock-fire-hd-8-2017-douglas-t3962846. Follow the steps carefully.
Can anyone help?
I've Factory Reset the HD8 twice and am using @k4y0z Douglas exploit package. I've ran exploits on many older HD8s (2016) & HD10s (2017) but never needed to Brick any... this HD8 2107 firmware is 9920 and I want to let my kid use it and put a custom ROM on it so I can run Google Family Link (which FireOS cannot).
thx for the help!
What device shows is it on lsusb?
Michajin said:
What device shows is it on lsusb?
Click to expand...
Click to collapse
tablet ID shows properly in both Windows 10 & Ubuntu in ADB (and can accept commands just fine too). When in Fastboot mode, it does not show up at all, or accept commands.
Should the tablet show as a USB device when in Fastboot mode? ... and if it should, what would cause it to not show up in FB mode, but work properly in ADB
LivinOne said:
tablet ID shows properly in both Windows 10 & Ubuntu in ADB (and can accept commands just fine too). When in Fastboot mode, it does not show up at all, or accept commands.
Should the tablet show as a USB device when in Fastboot mode? ... and if it should, what would cause it to not show up in FB mode, but work properly in ADB
Click to expand...
Click to collapse
You said it shows up.... What device does it say it is when you do a lsusb at the teminal in ubuntu?
LivinOne said:
Can anyone help?
I've Factory Reset the HD8 twice and am using @k4y0z Douglas exploit package. I've ran exploits on many older HD8s (2016) & HD10s (2017) but never needed to Brick any... this HD8 2107 firmware is 9920 and I want to let my kid use it and put a custom ROM on it so I can run Google Family Link (which FireOS cannot).
thx for the help!
Click to expand...
Click to collapse
Did you update all of the repositories the post calls out?
Also, how are you accessing Ubuntu?
Lastly, I'm sure you've checked this, but make sure it is a Douglas.
Michajin said:
You said it shows up.... What device does it say it is when you do a lsusb at the teminal in ubuntu?
Click to expand...
Click to collapse
It shows the ID. When sending ADB commands it works perfectly.
Kctucka said:
Did you update all of the repositories the post calls out?
Also, how are you accessing Ubuntu?
Lastly, I'm sure you've checked this, but make sure it is a Douglas.
Click to expand...
Click to collapse
Yes, I updated all repo's. I even killed my install and rebuilt the Ubuntu, under Windows Linux Subsystem. I used this exact setup, on the same PC, for 2 other Fire Tablets (HD8 2016 & HD10 2017) and it worked 100% smooth.
using... amonet-douglas-v1.2 and brick-douglas
The issue is the OS does not see the tablet once in Fastboot mode.
LivinOne said:
It shows the ID. When sending ADB commands it works perfectly.
Yes, I updated all repo's. I even killed my install and rebuilt the Ubuntu, under Windows Linux Subsystem. I used this exact setup, on the same PC, for 2 other Fire Tablets (HD8 2016 & HD10 2017) and it worked 100% smooth.
using... amonet-douglas-v1.2 and brick-douglas
The issue is the OS does not see the tablet once in Fastboot mode.
Click to expand...
Click to collapse
Does anything show up in lsusb in fastboot mode or do you see anythign like...
When you say it is in Fatboot mode, but nothing works, but you see a device in lsusb, what is the device called?
Like..
ID 0e8d:2000 MediaTek Inc. MT65xx Preloader
ID 0e8d:0003 MediaTek Inc. MT6227 phone
What is it being called?
---------- Post added at 12:36 PM ---------- Previous post was at 12:34 PM ----------
From my understanding you are trying to downgrade to unlock (which will temp brick your device), is this correct? I can try to help...
LivinOne said:
It shows the ID. When sending ADB commands it works perfectly.
Yes, I updated all repo's. I even killed my install and rebuilt the Ubuntu, under Windows Linux Subsystem. I used this exact setup, on the same PC, for 2 other Fire Tablets (HD8 2016 & HD10 2017) and it worked 100% smooth.
using... amonet-douglas-v1.2 and brick-douglas
The issue is the OS does not see the tablet once in Fastboot mode.
Click to expand...
Click to collapse
Does it recognize your other devices in fastboot mode?
If I recall correctly WLS doesn't work with fastboot. Something related to USB devices without storage.
I'd try booting Ubuntu using a USB stick with persistent storage.
Kctucka said:
Does it recognize your other devices in fastboot mode?
If I recall correctly WLS doesn't work with fastboot. Something related to USB devices without storage.
I'd try booting Ubuntu using a USB stick with persistent storage.
Click to expand...
Click to collapse
Here is a nice live disk pre-set up for the firestick 4k. I have used this on a few tablets.... But seems like it would still show up in fastboot in windows, if that was his issue...
https://github.com/amonet-kamakiri/fireiso/releases
Michajin said:
Here is a nice live disk pre-set up for the firestick 4k. I have used this on a few tablets.... But seems like it would still show up in fastboot in windows, if that was his issue...
https://github.com/amonet-kamakiri/fireiso/releases
Click to expand...
Click to collapse
Does the ISO run in Virtual Box, or something else? I've only been using the Windows Linux Subsystem as I rarely need to use Linux other than for my Synology NAS. Thx for the help!
LivinOne said:
Does the ISO run in Virtual Box, or something else? I've only been using the Windows Linux Subsystem as I rarely need to use Linux other than for my Synology NAS. Thx for the help!
Click to expand...
Click to collapse
It is a live disk. Burn it to a USB and boot from it...
Guys,
I noticed that in Windows 10 vs Ubuntu (Windows Linux Subsystem / WLS), they both work great with ADB... but they seem to be loading different versions...
Windows: adb server version (39) doesn't match this client (41); killing...
Ubuntu WLS: adb server version (41) doesn't match this client (39); killing...
Could this be an issue where Fastboot is a problem due to version?
thx
LivinOne said:
Guys,
I noticed that in Windows 10 vs Ubuntu (Windows Linux Subsystem / WLS), they both work great with ADB... but they seem to be loading different versions...
Windows: adb server version (39) doesn't match this client (41); killing...
Ubuntu WLS: adb server version (41) doesn't match this client (39); killing...
Could this be an issue where Fastboot is a problem due to version?
thx
Click to expand...
Click to collapse
No
Looking through the unlock thread, The OP says it is a fastboot issue and recommends using the live disk i sent a link for see posts #265 and #268
https://forum.xda-developers.com/hd...unlock-fire-hd-8-2017-douglas-t3962846/page27
Everything points to your computer not recognizing the fastboot device- Try the live disk....
I fixed it! Windows will not load the driver when I try to do it in Device Manager, manually. I used this installer THEN I opened Device Manager, right-clicked the unknown item under Android, and pointed it to root of the C Drive! It found and installed the driver.
Hope this helps someone in the future.
thx guys!