Database Users

OK I'm sorry but I'm Having issues with Fastboot

I tried asking in the Boot Image thread but since that thread was originally posted in January, I dont think anyone even goes in there anymore. OK this is what Ive got.
Im not sure if it was the new radio update or the JF1.5 or 1.51 but ever since Ive upgraded from RC33 the fastboot screen has changed and I havent been able to change my Boot Image.
Instead of just connecting the phone to the computer and pressing back to get fastboot it now give me 4 options instead of just fastboot.Up top it says
FASTBOOT USB (highlighted in red) then
<CAMERA STEP2> HBoot Mode
<SEND> Reset Device
<ACTION> Restart to HBoot
<MENU> Power Down
Is there a new driver i have to download? or is it something else? because when i go to RUN/CMD and I type in the correct commands to change the Boot Image it does nothing it says <waiting for device>
I'm Sorry if this may seem like a dumb Q? but I figured maybe I wasn't the only one having this problem?

sorry I dont really know the answer man, sounds like you are using a new spl or some other bootloader. However, just to let you know, you really needed to post this in the dev section and not the theme section. you probably would get a better response over there.
Stericson

un install your phones drivers in device manager.
unplug your phone,
reboot your computer into safe mode.
plug your phone into usb.
a dialog box will pop up, navigate it to the sdk folder or wherever you have the g1 drivers. install them. wait till it finishes.
then unplug your phone and boot it into fastboot mode. the plug it back in again. and install the same drivers again
unplug your phone and reboot your computer. you should be able to access your phone in fast boot now.
dont push boot images in safe mode, it may be unstable

Thanx guys let me see what i can do
Editk i must have updated to another SPL so i went back to the Original HardSpl and it came back thanx stericson fo the Idea. back to normal
Message to MODS: you can close this if you want I'm sorry for wasting space

Hi,
There is a new driver for the usb connection.
Unzip this file to a folder and plug in your phone don't Mount .
The computer should ask for a driver.
if it doesn't look in control panel, system, usb controllers.
One of the devices will should a problem, update the driver with the files you downloaded and you should be ok.
The computer doesn't recognize the new bootloader until you update the driver.
When you then plug in your phone, it will say fastboot usb.
LatinSilEighty said:
Thanx guys let me see what i can do
Editk i must have updated to another SPL so i went back to the Original HardSpl and it came back thanx stericson fo the Idea. back to normal
Message to MODS: you can close this if you want I'm sorry for wasting space
Click to expand...
Click to collapse

LatinSilEighty said:
I tried asking in the Boot Image thread but since that thread was originally posted in January, I dont think anyone even goes in there anymore. OK this is what Ive got.
Im not sure if it was the new radio update or the JF1.5 or 1.51 but ever since Ive upgraded from RC33 the fastboot screen has changed and I havent been able to change my Boot Image.
Instead of just connecting the phone to the computer and pressing back to get fastboot it now give me 4 options instead of just fastboot.Up top it says
FASTBOOT USB (highlighted in red) then
<CAMERA STEP2> HBoot Mode
<SEND> Reset Device
<ACTION> Restart to HBoot
<MENU> Power Down
Is there a new driver i have to download? or is it something else? because when i go to RUN/CMD and I type in the correct commands to change the Boot Image it does nothing it says <waiting for device>
I'm Sorry if this may seem like a dumb Q? but I figured maybe I wasn't the only one having this problem?
Click to expand...
Click to collapse
the spl you have there is Haykuro's Custom SPL
I had the same trouble with getting fastboot to work
I did the same as you and went back to HardSPL
trying to find a way to get fastboot to work on the newer SPL tho
will update if i get it to work

Wrong SPL zip file. Now what? [SOLVED]

[SOLVED. READ BELOW FOR DETAILS]
HI all.
I've managed to brick my Hero (T-Mobile G2) by flashing the wrong SPL file.
To make things more difficult I've lost the USB cable.
I can still:
Power+Menu (three vibrations + blinking green)
Power+Back (Fastboot)
Power+Search (Storageclean)
Power+VolumeDown (HBOOT, SD checking ...)
Is there a way to reflash the right SPL with one of these menus?
I've not found any similar case here and in MoDaCo.
Thanks in advance.
[SOLUTION]
This case is particular as there is no system available to use the "adb shell" commands. Nonetheless it's recoverable.
At least in one case
Almost everything comes from MoDaCo.
Despite I would say I'm not a real newbie, this time was a little bit harder than with other embedded devices for some reasons I'll explain later.
What do you need?
1. A miniUSB cable. Now I know that any miniUSB can work.
2. A Windows XP PC. A Linux or Mac OS X should also work. Read below.
3. The right USB software driver (I used this one) otherwise it won't work.
4. A modified recovery image (I used this one) that has flashing capabilities from the SD.
5. A working SPL (Second Program Loader) image (I used this one, thanks to the enlightner.
6. A system ROM image (again, I used this one).
What was the problem?
I used to play also with a Magic and still had an SPL zip of its on my SD.
I already had rooted and modded my Hero with MoDaCo's mod.
By mistake I flashed that SPL zipped image into my Hero and since then nothing was working any more.
The boot process was simply stopping at the "G2 Touch T-Mobile" screen up to the complete battery drain.
The directions found here were ineffective due to the fact that there was no running system to execute the "adb shell" commands.
I am using 99.99% of the time a Linux laptop but decided to get a Windows XP PC in order to simplify the troubleshooting while asking people for help and hints.
Maybe in the future I'll dare to reproduce the problem and solution with Linux. Maybe,
But let's see a stepwise procedure.
How I solved it (impossible to me without MoDaCo's and englightner's help, kudos to them)!
0. Unpack the USB driver and the recovery image ZIP files somewhere into your PC. Put the SPL and the system ROM image zip files into the SD card. Use the root directory of the FAT partition in case you have already partitioned it.
1. Switch off the Hero (by pulling the battery out).
2. Turn it on again without the USB cable in by pressing the back and the power keys. I've noticed some different behaviour if you keep the cable plugged in.
3. A white screen (the Initial Program Loader aka IPL aka Fastboot) will pop up.
4. Plug the USB cable in both the Hero and the PC. The screen will now show in red "FASTBOOT USB".
5. Windows should warn you about some unknown hardware having been plugged (Android 1.0). Ask for a manual installation by browsing to the directory where you unpacked the USD driver. Install it. No reboot is required (unbelievable!).
6. Open a command line session on your PC (Start-->Execute-->CMD on Windows), change the current directory (cd) to where modified recovery image has been unpacked and where both the fastboot.exe and cm-hero-recovery.img files are located.
7. From the command line run this command (without the quotes): "fastboot boot cm-hero-recovery.img". You'll see a green progression bar rising on the right side of the Hero screen and after 1 second you'll see the modified recovery image running.
8. At this point I tried to recover a previously saved nandroid backup. But for some reason this time the recovery was complaining about a chown/chmod not being able to change the permissions on a system file! So it's useless to try it.
9. Instead I asked to flash the SPL zip file. It worked fine and I asked for a reboot.
10. the final step was to pop the recovery tool again (Home+power, keep the home pressed until you'll see the friendly black and green screen) and to slash the system ROM zip file.
I also reset all user data before doing it. I'm not sure whether this reset is required.
11. At the reboot the flashed system ROM was happily waiting for me to customise the settings.
12. As a last check, I rebooted once again the Hero to see whether the solution was permanent. And it was.
Few suggestions for seniors.
Please, please be patient with newbies. This could be the first time they hit the wall and panic and frustration can play an important and irritating role.
Please, please be as precise as possible. What a senior thinks is an implicit piece of information, can lead to hours of frustration for the newbie. For example, the SUB driver installation is not mentioned very often in any thread. It looks trivial. It's not.
Please, please be positive to newbies. By encouraging them they'll become less newbies than they are now.
And a few suggestions for juniors (like me).
Please, please don't panic! If there's a solution, you don't need to panic. If there's none, you don't need to panic as well.
Please, please be precise in describing the problem (I've not been myself). Small unseen details can matter a lot.
Please, please don't blame people for late answers. Very probably they are busy with their own job, life or hobbies.
Please, please remember that if you are in trouble is very probably due to your own mistakes. Not someone else's. You are playing with low level stuff, not just application settings.
If you decide to follow someone's directions, please do it carefully. If you take some decisions on your own, please document them in the thread.

If you can get to fastboot with power and back, then all is not lost. And most importantly it's not a 'brick'. A 'brick' is a device that won't turn on.
You can flash the recovery via fastboot (using this guide) then a new ROM (I suggest my custom ROM) but, er, you're obviously gonna need a USB cable!
P

I was already using your marvelous mod, though.
I only took the SPL file from the wrong directory (I have been playing also with Magic, aka G1).
The cable is a huge problem, now.
At the moment I'm using a mini-USB cable which is good for charging the battery, but has no effect on the communication side.
Can I put some file in the SD card from my PC in order to have it booted into?
I still have a couple of nandroid backups in the SD but have no idea whether this makes any difference.
Anyway, thanks not just for the hints. Your 1.5 (1.5.1 when I'll fix my problem) rocks!

A real miniUSB cable should work fine. Yours must be only wired for charging. Go and buy one.
There's no other way to do it unless power+home gets you into recovery (which it sounds like it should?)
P

The mini-USB comes from my USB 2.5" HD.
It works with cameras and other mini-USB devices for full dvice access.
But it does not work with the Hero.
The original cable looked different from this one because of the asymmetric shape (and possibly an extra pin or two).
The Hero cable looks like it's proprietary design and buying one seems quite difficult. Would any HTC USB cable work?
Now I'm not in the Netherlands anymore and here the HTC stuff looks quite uncommon to have a cable lent.

I never use my HTC cable, I use a standard mini USB cable.
P

OK.
I've bought a brand new mini-USB cable. It works with my Nokia phone, my digital camera dnd also my USB disk.
1. I've donwloaded the file from the guide MoDaCo referred previously.
2. I've unpacked the ZIP file, opened the CMD session, CDed to the directory containing the adb.exe file
3. I've booted the phone to the FASTBOOT (VOLUMEDOWN+POWER)
4. I've connected the phone to the cable.
5. The HERO screen says now "FASTBOOT USB"
6. I've run the command "adb shell reboot bootloader"
7. I get "error: device not found".
What's next?
P.S.
Steps 3 and 4 are not mentioned in the guide, though.

You can't use adb shell from the fastboot screen, you need to boot a recovery image using the "fastboot boot <filename>" command.
Just of curiousity. What is the HBOOT version displayed on your fastboot screen?
Could you type all the text it displays?
I might be able to help you out.

Try following the guide linked above.
You can't do ADB until you've done the 'fastboot boot cm-hero-recovery.img'.
Seriously... how hard can it be to read thru a handful of steps!
P

You are right! It's hard unless you already know how to.
I quote:
- download this file and extract it to your PC or mac
- open a command prompt to the directory containing the extracted files
- type the following commands (prefix each command with ./ if you're on a mac)
So far it's trivial ...
adb shell reboot bootloader (wait for device to reboot into bootloader)
fastboot boot cm-hero-recovery.img
adb shell mount /sdcard
adb push cm-hero-recovery.img /sdcard/cm-hero-recovery.img
adb shell flash_image recovery /sdcard/cm-hero-recovery.img
That could also be trivial if:
1. I knew about the driver installation (quite later in the thread)
2. I knew in which initial status the phone is to be
Of course, a bit at a time I find everything.
Maybe re-editing the original post to include all the bits in one single place would both boost the success rate of n00bs like me (really) and lower the amount of stupid questions (really) like mine.
Anyway, I need to thank you very much!!!

Hmm, bad news, ust spoken to an extremely knowledgeable friend of mine, and he says your device is knackered.
P

I'm impressed the SPL actually booted on a Hero.
It's is a "real" Hero you have right? aka T-Mobile G2 Touch?
Fastboot can be used when you are in HBOOT, with FASTBOOT USB being displayed.

So, if this doesn't work, you're screwed.
- download this and extract the rom.zip
- copy the .zip to your SD card and name it HEROIMG.zip
- turn on your device with volume down+ power
If it doesn't start flashing, buy a new Hero.
P

packetlss said:
You can't use adb shell from the fastboot screen, you need to boot a recovery image using the "fastboot boot <filename>" command.
Click to expand...
Click to collapse
Good to know. I have no idea about this specific device!
And the help is quite fragmented among a large number of threads.
packetlss said:
Just of curiousity. What is the HBOOT version displayed on your fastboot screen?
Could you type all the text it displays?
Click to expand...
Click to collapse
HERO CVT
HBOOT-1.33.2005 (HERO10000)
MICROP-010e
RADIO-6.35.05.15
Apr 20 2009,15:30:43
packetlss said:
I might be able to help you out.
Click to expand...
Click to collapse
I hope so.

Try doing what modaco suggested and see where that ends up.

modaco said:
So, if this doesn't work, you're screwed.
- download this and extract the rom.zip
- copy the .zip to your SD card and name it HEROIMG.zip
- turn on your device with volume down+ power
If it doesn't start flashing, buy a new Hero.
P
Click to expand...
Click to collapse
I hope to fix mine.
Anyway, is there any comprehensive guide about the booting (not rooting) process with the software stack and the "cheat codes"?
I don't think I'm really a n00b, but the fragmentation of information is quite large for these marveloous Android phones.

The HEROIMG.zip has been flashed, I presume, as a vertical blue bar appeared on top right screen.
After fre minuted the process ended ... with no news.
At the reboot everything is again as before.
Home+Power won't make the CyanogenMode+JF menu pop up.
The simple boot itself won't make my Hero botting in any system.
Only a big "G2 Touch T-Mobile" on the black background.
Now what?

That HEROIMG.zip contained a hboot. When you boot to bootloader is still the same?
You say 'fastboot boot recovery.img' (as per my instructions) didn't work?
P

'fastboot boot recovery.img' works.
It's the subsequent step that doesn't. I cannot mount /sdcard (error: device not found)!
And even recovering a previous nandroid backup won't help.
What I understand there's something in between the fastboot and the actual image (the SPL?) that is missing doe to my original error.

Does the bootloader still show the old version?
P

[Q] Required downloads seem offline

In short; I'm trying to bring back a phone (Magic with 32B) that was messed up, I have no prior knowledge on this topic so please bare with me.
I'm trying to follow the guide on this page:
Looks like I can't post links, but android-dls wiki page for magic rooting
However, the links for Haykuro's Magic "rootme" rom and Magic modified recovery seem to be offline / no longer available (including the mirror for the first of the two).
Are there any mirrors available for these files? Or alternatively, if anyone has them, if they could be uploaded to megaupload or something alike that'd also be very helpful. Alternatively if there is another guide that I could/should be following, I'd appreciate that as well.
A sort of sub-question; the "welcome" video has made me somewhat reluctant to ask for help on any specific issues, is that justified or should I just make a thread with any/all info that might be relevant for someone who might be willing to help?
[edit] I have also tried method 2 now, unfortunately I'm having a problem. Adb seems to be able to detect my device only when I boot it into "ClockworkMod Recovery 2.5.0.7". This was something installed by the previous owner (who also borked it before passing it on to me).
From here, I have ran update.zip, however that has not had the effect of making the phone work again (As in, the phone still gets stuck on the Vodafone logo screen).
[edit 2] From what my brother has told me, it's the radio that he screwed up. I've been trying to change that- but I'm not yet having much luck. When I use "adb shell", the "su" command doesn't work and returns:
/sbin/sh: su: not found
[edit 3] I think that I've managed to ruin my chances of getting this phone working, I can no longer get into ClockworkMod Recovery- and that was the only way I was able to get adb to recognize my phone.
I tried following "[Guide][ALL DEVICES]ROOT + flash custom recovery + fix perfected", had the above "su" problem however managed to work around that by (in step 9) pushing to /data/local instead of /data/local/tmp (since I was unable to access tmp without su). The steps that followed seemed to work, until I tried restarting the phone- which left me unable to access clockworkmod recovery.

Download my fastboot commander tool from my signature, version 1.51.
Past here all device info from the tool.
You must be in fastboot mode to use the tool.
Try to download HTC-sync app. It has the necessary drivers to make your device work with adb inside android OS.
Once i have your device info, then i can assess the problem :0)

mumilover said:
Download my fastboot commander tool from my signature, version 1.51.
Past here all device info from the tool.
You must be in fastboot mode to use the tool.
Try to download HTC-sync app. It has the necessary drivers to make your device work with adb inside android OS.
Once i have your device info, then i can assess the problem :0)
Click to expand...
Click to collapse
At first it didn't find my device, until I press the 'back' button to enter fastboot mode from inside hboot.
anyway:
Operating system: Windows.
Tools folder found.
Windows fastboot tools found.
The folder containing the IMG files was not found.
No Nandroid folder was not found - "Restore" button disabled.
STARTING PRINT OF DEVICE INFO.
-----------------------------------.
SPL/hboot version: 1.33.2009.
Radio version: 2.22.27.08.
Main software version: 1.91.172.1.
cid: vodape17.
cpld: 10.
product: sapphire.
mid: sapp10000.
security: off.
build-mode: eng.
-----------------------------------.
Print of device info SUCCESSFUL
Click to expand...
Click to collapse
I have installed HTC Sync, and adb was working before- until I tried following the guide in my 3rd edit

Download this:
https://rapidshare.com/files/621973966/1.91.172.1.nbh
Use fastboot commander, "FULL ZIP" tab.
Flash the downloaded file and your device should be full reset.
Then follow my guide found in my signature to root and flash custom recovery (if you want, also eng spl).
Good luck

Though the "Flash zip" appears to have been successful (during the process I saw the list of things being flashed on my phone all get checked off "ok"), adb still seems unable to detect my device.
Since I was previously only able to use adb while I was in recovery mode, I tried going there. When I start my phone with power+home, I get into a screen which has a "warning" triangle displayed diagonally with a phone laying under it. Adb however still does not see my phone at this point.
Also, in this guide- which steps am I meant to follow exactly? Steps 1-4 seem to assume that I have a working phone, so I'm guessing I can skip those. Steps 5 - 7 seem to detail flashing a recovery and 8 flashing spl/hboot.
Could I use the hboot,radio & recovery tab in fastboot commander to try and resolve this instead?
Also, in case you want to know what fastboot commander says about device info after the zip flash:
STARTING PRINT OF DEVICE INFO.
-----------------------------------.
SPL/hboot version: 1.33.0007.
Radio version: 2.22.19.26i.
Main software version: 1.91.172.1.
cid: vodape17.
cpld: 10.
product: sapphire.
mid: sapp10000.
security: on.
build-mode: ship.
-----------------------------------.
Print of device info SUCCESSFUL.
This device does not have s-off nor eng hboot.
ARE YOU SURE THAT THIS IS THE RIGHT TOOL FOR YOU?.
Click to expand...
Click to collapse
I'm guessing by the last 2 lines of that that the answer is no

I'm pretty sure its driver related. Once you have reset the device, the HTC-sync drivers should find the adb device.
Reinstall HTC-sync and it should make adb work again.
Unless you have bricked the usb connection (which is easy to repair).
A simple test would be to see if you can access the sdcard through android OS.

I tried re-installing HTC Sync again, but adv still can't find my phone. I thought maybe my download was corrupted or something alike, so I redownloaded and tried again- still can't find my phone.
Can you elaborate on "A simple test would be to see if you can access the sdcard through android OS."
You mean through an emulator?
Not sure if it's helpful- but in windows I don't see the "removable storage" with my phone plugged in, previously when I had access to clockworkmod, I could see it when I opened the mount menu, mounted sdcard and I think it was mounted USB- when I closed this again my computer would crash (bsod).

Do the following tests:
a) Check if your device works on another computer!
b) Try to mount the sdcard from your Android OS. Does it work?
If the mount thing does not work, maybe you are usb-bricked.
If you are usb-bricked, then we can fix it by flash a new misc partition.
Just let me know

mumilover said:
Do the following tests:
a) Check if your device works on another computer!
b) Try to mount the sdcard from your Android OS. Does it work?
If the mount thing does not work, maybe you are usb-bricked.
If you are usb-bricked, then we can fix it by flash a new misc partition.
Just let me know
Click to expand...
Click to collapse
I'm going to have dinner in a few minutes, after that I'll check if it works on another computer. However I still have no idea what you mean by "mount the sdcard from your Android OS", the phone does not start- so how do I check?
[edit] I've tried the phone on another computer, which also could not find it using adb.

I'm still hoping to fix this phone, any help further help would be (and all help provided so far is) very much appreciated. If the phone is doomed, I'd like to know that also.

Fastboot discussion.

I have searched and couldn't find a fastboot thread. So here it is.
I found out fastboot is working on Linux.
Bad news is Windows seems to need another driver for fastboot.
Please help look for a windows driver or make one.
The fastboot commands all seem to work fine.
Here you guys go! Enjoy.
Code:
[SIZE=5][SIZE=3][SIZE=5][SIZE=3]adb reboot-bootloader
fastboot -i 0x1949 command_here[/SIZE][/SIZE][/SIZE][/SIZE]
Just noticed pokey9000 said this but it was overlooked.
pokey9000 said:
That's it. And you're running fastboot as "fastboot -i 0x1949 your_command_here", and you have udev set to allow permissions for that VID (or are running as root) in Linux?
Click to expand...
Click to collapse
Thank you.
Still don't believe me, look at the last picture.
I'm having issues with some commands. Please test it out and enjoy!

shimp208 said:
In the Fire TV section a fastboot cable was created by splicing two USB A to B cables together, so that the A to A ends were together which when connected from your computer to the Fire TV on bootup put the device in fastboot mode, in the process then your computer recognized (Running Windows 8 was the example given) the device and installed the proper drivers. Since the devices are similar, a potential solution would be use the cable, have the computer recognize it and install the drivers, then backup the drivers, and share them here for others to use.
Click to expand...
Click to collapse
I'm quite sure the cable isn't the issue. Also that's just it, I can't get windows to recognize it or find much info about it. The adb driver for the device isn't enough I guess. The funny thing is windows says it's working properly as 'Kindle' for a little while when you plug it in (while in bootloader) then device manager refreshes and reports 'cannot start'. I tried launching 'fastboot devices' many times but still nothing. I think it needs a software fix and not a hardware one but I have no past experience using fastboot. So... noob alert.
btw the driver windows tries to use is ms_comp_mtp(Generic driver installed=true) and adb uses the Amazon one on the fourm here.
DevNode status Value:
01802400
DN_HAS_PROBLEM
DN_DISABLEABLE
DN_NT_ENUMERATOR
DN_NT_DRIVER
Also Bus reported device description Value:
fastboot
VID=1949 & PID=000C
(0x1949 && 0x000c)
Current Driver files:
\system32\DRIVERS\UMDF\WpdMtpDr.dll
\system32\DRIVERS\winusb.sys
\system32\DRIVERS\WUDFRd.sys
\system32\WpdMtp.dll
\system32\WpdMtpUS.dll
We need someone good on this.

I have a problem

I don't think there's ever been a question of getting into fastboot mode by using the adb reboot-bootloader command.
The issue is how to enter fastboot if the device is semi-bricked.
The device has source in the original bootloader to boot into fastboot mode if both volume buttons are pressed while powering on the device. But this has since been altered and now will only work if the device is unlocked.

Hashcode said:
I don't think there's ever been a question of getting into fastboot mode by using the adb reboot-bootloader command.
The issue is how to enter fastboot if the device is semi-bricked.
The device has source in the original bootloader to boot into fastboot mode if both volume buttons are pressed while powering on the device. But this has since been altered and now will only work if the device is unlocked.
Click to expand...
Click to collapse
Is flashing the stock .bin file any different than doing a factory reset?
I am bricked, have root, have adb, can get fastboot using adb reboot-bootloader in windows 8. I also have a Linux box if necessary.

saphi95 said:
I have a problem
Click to expand...
Click to collapse
I would recommend taking a look at this thread here, specifically the "Fixing No Permissions Error" section which should allow you to fix the problem your encountering.

dcoig1 said:
Is flashing the stock .bin file any different than doing a factory reset?
I am bricked, have root, have adb, can get fastboot using adb reboot-bootloader in windows 8. I also have a Linux box if necessary.
Click to expand...
Click to collapse
Fastboot works with win8? Not with win7.1 If you have fastboot working with win8 please go to device manager (when your in the bootloader) click properties on the device then look for what driver it uses.
Hashcode said:
I don't think there's ever been a question of getting into fastboot mode by using the adb reboot-bootloader command.
The issue is how to enter fastboot if the device is semi-bricked.
The device has source in the original bootloader to boot into fastboot mode if both volume buttons are pressed while powering on the device. But this has since been altered and now will only work if the device is unlocked.
Click to expand...
Click to collapse
My main reason is to get fastboot working with windows. I just can't. Linux seems to work with fastboot but I can't access it via windows.

Just uninstall the kindle driver and replace it with the generic fastboot one

hello all,
i've kindle fire hdx 7" , no adb, grey screen logo then shutdown and goes to black screen.
when connected using cable, it show new devices... QHSUSB_BULK and sometime unknown devices.
press hold power button and volume up only go to recovery mode, but cannot recovery the system..
always go to grey screen logo...
sorry for my bad english language...
hope all of you, understand what i mean here
i need solution for fix the problem soon. thanks

I think all that works is reboot into fastboot mode. Windows 8 says no drivers are loaded. I tried a command (can't remember what) and it just went out to lunch so... I guess windows 8 isn't working either. Only to put the device in fastboot.

there are three oem commands:
oem device-info
oem idme
oem relock
Click to expand...
Click to collapse
but it doesn't support oem unlock so there must be another way of unlocking the bootloader, when you try some of the commands the device returns "not allowed for locked hw". Does anyone know what the "hw" is ?

hw = hardware?

MaximilianOzora said:
hello all,
i've kindle fire hdx 7" , no adb, grey screen logo then shutdown and goes to black screen.
when connected using cable, it show new devices... QHSUSB_BULK and sometime unknown devices.
press hold power button and volume up only go to recovery mode, but cannot recovery the system..
always go to grey screen logo...
sorry for my bad english language...
hope all of you, understand what i mean here
i need solution for fix the problem soon. thanks
Click to expand...
Click to collapse
Read up on this bud.

Hi,
I have a bricked kindle hdx 8.9 that stops at "Kindle Fire" boot screen. I am a newbie at these things.
Just discovered that it still respond to some adb queries. Sounds like there is still hope to recover... Could it be the bootloader is messed up? Anyway to reload an image boot file to repair?
Also "fastboot reboot-bootloader" puts it into fastboot mode...with the status "ready"....and i just dont know how to proceed. Any one can help?

uhg
Facepalm

just back a little: was rooted in April but with subsequent amazon auto updates - didn't have su status. But I was able to load apps & files, installed vpns, quite a few docs,mp4 files, etc. Not really using much of the new freedom or whatever was left of it... Nothing exciting.
Was working well until one fine sunday afternoon, just 2 weeks ago when it just simply stopped after rebooting from a previous low battery charge. Was told it could be an interrupted routine update when the battery power just fell below threshold - but thot it wouldn't have erase the previous image before the new update is effective. Or it could possibly be a deleted file that is related to the booting process as I did a bit of clean up prior to the last reboot?
In the meantime, I did some adb shell/pull to explore or extract the files, photos,etc in /sdcard & other places back to my PC just in case they were not backup by the cloud. Maybe it was not bricked...but just lost a boot file or something...

In a bad situation, have absolutely zero ADB access as my build.prop is botched (bad permissions) and I did a factory reset in hopes of recovering. There is a "fastboot cable" on amazon that says it will reboot a hdx into fastboot mode, but I'm unsure of it's legitimacy. Help?

here try
Tumbtack said:
In a bad situation, have absolutely zero ADB access as my build.prop is botched (bad permissions) and I did a factory reset in hopes of recovering. There is a "fastboot cable" on amazon that says it will reboot a hdx into fastboot mode, but I'm unsure of it's legitimacy. Help?
Click to expand...
Click to collapse
This thread.read read read http://forum.xda-developers.com/showthread.php?t=2588608

I don't quite understand. Why is a special cable required for this? What makes it any different from the standard one that comes with the device?

I don't know if this will add anything to the discussion...but I can confirm fastboot is working on Ubuntu 14.04. I am using a kindle fire HDX 7" and it detects it on devices..and most commands work. Sometimes the terminal must be closed and reopened for commands to go through..
fastboot oem unlock works..or rather it says "Okay" but I'm unable to flash anything.

Flashing stock image error message help

Apologies for this being a bit long but hopefully this shall explain all issues.
I am trying to flash android 8.1 onto my RP2, I did flash pie onto the phone just to see if I could which it worked flawlessly first time no issues, I switched off my pc and that was it for a few months. When I went back to this to flash 8.1, I had to wipe my pc as the devices wasn't being found in fastboot only ADB, so done all of that, reinstalled ADB drivers and all running smoothly as it reboots from CMD, but when I tried flashing, it came up with a long list saying system.img not found, there was more lines like this around 15? But with different .imgs saying not found, I then moved the file into where my platform tools are, it then half worked as it just wiped the phone clean not going to older firmware, has anyone else come across this?? Any help would be much appreciated. I'd like to know what I'm doing wrong as I want to downgrade my RP1 back to either 7.1.1 or 8.1

would really love help aswell.

Simpson101 said:
Apologies for this being a bit long but hopefully this shall explain all issues.
I am trying to flash android 8.1 onto my RP2, I did flash pie onto the phone just to see if I could which it worked flawlessly first time no issues, I switched off my pc and that was it for a few months. When I went back to this to flash 8.1, I had to wipe my pc as the devices wasn't being found in fastboot only ADB, so done all of that, reinstalled ADB drivers and all running smoothly as it reboots from CMD, but when I tried flashing, it came up with a long list saying system.img not found, there was more lines like this around 15? But with different .imgs saying not found, I then moved the file into where my platform tools are, it then half worked as it just wiped the phone clean not going to older firmware, has anyone else come across this?? Any help would be much appreciated. I'd like to know what I'm doing wrong as I want to downgrade my RP1 back to either 7.1.1 or 8.1
Click to expand...
Click to collapse
Make sure you are running the command prompt from platform-tools and all up update files are in the platform-tools folder and not in a folder inside platform-tools ...also try. "fastboot flashing unlock_critical". Even if you have an unlocked bootloader then install the firmware by typing
"flash_all" and just wait even if it looks frozen

flashing stock rom CRITICAL ERROR Black screen
I followed all guidelines including fastboot flashing unlock_critical. Everything was flashing fine & it got to a point where it rebooted & now all i have is a black screen it will not turn on or go to fastboot at all screen is completely black. If I am hooked up to my pc and try the combo buttons for fastboot my computer makes a sound as it would with any device attached. Please tell me i didnt totally brick my phone. I would appreciate any help!
The phone shows up in the device manager as qualcom hs-usb qdloader 9008 (com 8). Theres gotta be something i can do.
Xinfuzemodz said:
Make sure you are running the command prompt from platform-tools and all up update files are in the platform-tools folder and not in a folder inside platform-tools ...also try. "fastboot flashing unlock_critical". Even if you have an unlocked bootloader then install the firmware by typing
"flash_all" and just wait even if it looks frozen
Click to expand...
Click to collapse

jessejamesd2i said:
I followed all guidelines including fastboot flashing unlock_critical. Everything was flashing fine & it got to a point where it rebooted & now all i have is a black screen it will not turn on or go to fastboot at all screen is completely black. If I am hooked up to my pc and try the combo buttons for fastboot my computer makes a sound as it would with any device attached. Please tell me i didnt totally brick my phone. I would appreciate any help!
The phone shows up in the device manager as qualcom hs-usb qdloader 9008 (com 8). Theres gotta be something i can do.
Click to expand...
Click to collapse
Try my guide https://forum.xda-developers.com/razer-phone-2/how-to/how-to-fix-fastboot-drivers-t4086479
To get drivers working, this happend to me also to get to boot loader when drivers are installed use "fastboot reboot bootloader"
And maybe have to spam it ...( After typing it once press arrow up and enter ) afew times to get in to bootloader. Hope this will help.