Hi Everyone, In an attempt to fix my bricked device with all necessary flash files and drivers installed perfectly, my device is being detected under 'HUMAN INTERFACE DEVICE' as a 'USB INPUT DEVICE' in device manager, according to what i read, my device is suppose to display or be detected as "qulacom HS-USB qloader 9008" under com port. but that isn't happening, i repaired the drivers, re-installed them, formatted my pc and tried it on fresh windows installation. but still the problem is there. i even tried it on several computers but it still detects as USB INPUT DEVICE under Human Interface Devices in device manager. Now i am stuck here with my device dead for the past two weeks. please any one with an idea how to fix this issue?
i will be deeply grateful. Thanks!!
:crying:
Steps Parku said:
Hi Everyone, In an attempt to fix my bricked device with all necessary flash files and drivers installed perfectly, my device is being detected under 'HUMAN INTERFACE DEVICE' as a 'USB INPUT DEVICE' in device manager, according to what i read, my device is suppose to display or be detected as "qulacom HS-USB qloader 9008" under com port. but that isn't happening, i repaired the drivers, re-installed them, formatted my pc and tried it on fresh windows installation. but still the problem is there. i even tried it on several computers but it still detects as USB INPUT DEVICE under Human Interface Devices in device manager. Now i am stuck here with my device dead for the past two weeks. please any one with an idea how to fix this issue?
i will be deeply grateful. Thanks!!
:crying:
Click to expand...
Click to collapse
follow this
1. join in recovery mode (cwm)
2. go mounts and stroge and format system
3 reboot ur device ( Now the loop is eliminated, just a static imagen )
3. dowload drives, firmware , and QNCG
4. install drivers or repair it
5 when the step 4 is done, plug ur device on elife logo and wait for driver installation(like 10 min)
6 use winrar for descompress the firmware
7open GNQC select bp browser, and search in folder firmware a file called BP_imagen
8 try with genereal mode or emergency mode, and click dowload
i did it, its working
u must have patience dont worry
try it, its working
good luck
Still Not Helpful.
andresplata94 said:
follow this
1. join in recovery mode (cwm)
2. go mounts and stroge and format system
3 reboot ur device ( Now the loop is eliminated, just a static imagen )
3. dowload drives, firmware , and QNCG
4. install drivers or repair it
5 when the step 4 is done, plug ur device on elife logo and wait for driver installation(like 10 min)
6 use winrar for descompress the firmware
7open GNQC select bp browser, and search in folder firmware a file called BP_imagen
8 try with genereal mode or emergency mode, and click dowload
i did it, its working
u must have patience dont worry
try it, its working
good luck
Click to expand...
Click to collapse
Actually my device doesn't even come on for me to do all that you said, i tried repairing drivers and all that but it still detects as USB INPUT DEVICE under HUMAN INTERFACE DEVICES. i need my device to detect as qualcomm device before GNQC downloader can detect it. my issue is very different here. because GNQC can't see my device since my device is not being detected the rightful way after all. i will deeply appreciate the solution. Thanks
did u fix it??
U can fix ? I have the same problem since three weeks and nothing... this a a sh*t... only recognized by HID... In other ocassion before of this, i can flash my Gionee but now i cant:crying:
Another one here who saw how the phone bricked after being flashed with GnQc, now when I plug the Usb on the Pc or with wall charger, the red light keep lit and it seems like it will like this forever. I am thinking of trying to get out the screen and disconnect the battery, seems like the phone is stuck on some strange mode.
Thanks.
This feel that not have solution....
Can any one fix it ?
i also got stuck . have given to gionee care they are unable to figure what was the actuall problem
Steps Parku said:
Actually my device doesn't even come on for me to do all that you said, i tried repairing drivers and all that but it still detects as USB INPUT DEVICE under HUMAN INTERFACE DEVICES. i need my device to detect as qualcomm device before GNQC downloader can detect it. my issue is very different here. because GNQC can't see my device since my device is not being detected the rightful way after all. i will deeply appreciate the solution. Thanks
Click to expand...
Click to collapse
the problem for me is that it have recovery stock english(e3) and i can't do anything...
anyone fixed the problem? i have my gionee bricked....
Hello everyone, I tried very hard to root the HD6 but still have no clue. I knew all usual root exploits are not working on HD6, so I try another way. Fire HD6 uses MT8135 CPU from MediaTek, usually MediaTek CPU comes with PreLoader mode. You can use the SPFlash Tool to flash / read back the ROM under the PreLoader mode. I found out there is a similar tablet "teclast P983g" using similar specs and the SP Flash Tool is working well.
I setup the SP Flash Tool and It cannot detects the HD6. HD6 is using a different PreLoader VCOM usb pid, it is strange that as most of the MediaTek devices are using the same pid across all models. I modified the VCOM info file and also the SP Flash Tool usb_setting.xml, it detects the HD6, but the readback/flash is still not working.
I saw something similar.
If you are using windows, turn the fire off, turn it on and when the preloader devices flashes you can get the properties from it. It only shows for a short time but enough to grab the needed info. I cant remember right now what it is. I also downloaded the full rom to the P983G and tried booting both the recovery and the boot image but no luck. I wont have the fire back at my house until next weekend unfortunately.
You need preloader drivers. they are out there. turn you kindle off and open device manager.
senzhk said:
Hello everyone, I tried very hard to root the HD6 but still have no clue. I knew all usual root exploits are not working on HD6, so I try another way. Fire HD6 uses MT8135 CPU from MediaTek, usually MediaTek CPU comes with PreLoader mode. You can use the SPFlash Tool to flash / read back the ROM under the PreLoader mode. I found out there is a similar tablet "teclast P983g" using similar specs and the SP Flash Tool is working well.
I setup the SP Flash Tool and It cannot detects the HD6. HD6 is using a different PreLoader VCOM usb pid, it is strange that as most of the MediaTek devices are using the same pid across all models. I modified the VCOM info file and also the SP Flash Tool usb_setting.xml, it detects the HD6, but the readback/flash is still not working.
Click to expand...
Click to collapse
Can you modify the PID of the MT65 drivers to be the Kindle?
Like in the usb2ser_Win764.inf driver file...
%MTK_PRELOADER%=Reader, USB\VID_1949&PID_000F2
I tried the above and Windows complained about not having a compatible device. Any ideas?
Is this reliable?
Hello:
Has anybody seen this?
http: //www dot how-to-root dot club/mp3-0 /amazon- fire-hd-6-6688 dot html
That page is BS.
Hello. I have CX-919 with RK3188-T and RTL8723BS for bluetooth and wifi. I tried to flash the stock rom again using Rockchip Batch tool. The process succeded but after that ,the tv stick wont boot. I have to say that i didnt changed anything in the development menu such as usb debugging options . what can i do now? does the stick have to be connected to tv while flashing a new rom?
Hi.
I tried to unlock my fire hd 10 2017 using virtualbox ubuntu.
I was following the steps and I found that my device's firmware version was 5.6.4.0
I read downgrade was necessary but I didn't know how.
Luckily, I could find a way and downgraded firmware 5.6.4.0 to 5.6.2.0 using sideload.
It bricked as planned so I tried unbrick it using bootrom-step.sh
But it didn't work.
I think repeatedly connected and disconnected usb port is the problem.
I tried installing usb driver for amazon device and mediatek usb vcom driver.
But it didn't work, too.
What could be a problem?
Help me please. Thank you.
pdh4118 said:
Hi.
I tried to unlock my fire hd 10 2017 using virtualbox ubuntu.
I was following the steps and I found that my device's firmware version was 5.6.4.0
I read downgrade was necessary but I didn't know how.
Luckily, I could find a way and downgraded firmware 5.6.4.0 to 5.6.2.0 using sideload.
It bricked as planned so I tried unbrick it using bootrom-step.sh
But it didn't work.
I think repeatedly connected and disconnected usb port is the problem.
I tried installing usb driver for amazon device and mediatek usb vcom driver.
But it didn't work, too.
What could be a problem?
Help me please. Thank you.
Click to expand...
Click to collapse
Oh my god :facepalm:
The script downgrades automatically.... Now there's no solution until you open the device, short the bootrom point and execute the bootrom-step.sh..
Rortiz2 said:
Oh my god :facepalm:
The script downgrades automatically.... Now there's no solution until you open the device, short the bootrom point and execute the bootrom-step.sh..
Click to expand...
Click to collapse
Actually I opened the device and disconnected the battery and display cables.
But I don't have star-shaped screwdriver. And I don't know where the bootrom point is.
Can I short the bootrom point without screwdriver?
Thank you.
Hi there all, I have an old Android TV box which when powered up gets to the logo screen but doesn't load/boot, I have tried the reset button but it doesn't take me to the options menu or reboot the system..I have the correct .img file with firmware of the the device and I have tried unsuccessfully to flash it using Amlogic USB Burner via double male USB cable connecting the box and pc..I have also burnt the .Img file with firmware onto and SD card which was then plugged directly into the box..neither method has worked..I have faithfully followed the instructions for both methods and the software for USB burning and SD card burning are Amlogic tools...so fully compatible as the Android Box is Amlogic also...any help would be appreciated.