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.
Related
Hi guys,
I want to go back to stock since 4.4 is coming. However, when I try to flash the stock rom+ with Nexus Root Toolkit 1.7.3, I get stuck at the whole fastboot part. Fastboot IS working on my Nexus, but the drivers cause a lot of trouble. Installing the drivers when my device is running normally ( so no fastboot mode or whatsoever) works fine.
I have followed the Full driver installation guide where I tried options 1 till 4 but they all get stuck at the point where my device reboots into fastboot mode. At this point, my computer doesn't recognize my device and gives me an error. My nexus is shown in the device manager as unknown device and updating the drivers manually by redirecting my computer to the NRT drivers does not work. It says it cannot find drivers for the device. Does anyone know what I might have done wrong?
Or is it possible to flash a stock rom through twrp? like this one? http://forum.xda-developers.com/showthread.php?t=2376881
TL;DR: use a machine with Windows 7 installed. Or boot ubuntu from a usb stick.
I've researched a lot about this, I had to downgrade my dad's phone with Flashtool (for Xperias), and after trying about every tutorial I encountered (removing drivers, installing different drivers, changing ports, disabling driver signature verification in Windows, I installed android studio, adb separately, running everything in administrator mode), I remembered I have a W7 machine on the other desk, it worked like a charm.
W8 (or 8.1, it's the same thing) is bad for flashing, I don't know when they're going to fix it.
issak42 said:
TL;DR: use a machine with Windows 7 installed. Or boot ubuntu from a usb stick.
I've researched a lot about this, I had to downgrade my dad's phone with Flashtool (for Xperias), and after trying about every tutorial I encountered (removing drivers, installing different drivers, changing ports, disabling driver signature verification in Windows, I installed android studio, adb separately, running everything in administrator mode), I remembered I have a W7 machine on the other desk, it worked like a charm.
W8 (or 8.1, it's the same thing) is bad for flashing, I don't know when they're going to fix it.
Click to expand...
Click to collapse
Yeah, I tried the same things you did, including disabling driver signature verification but it won't work. I'll try a windows 7 machine.
Thanks for your answer!
Hi,
I am trying to flash my watches, but I have a problem with recognizing COM ports.
I have MTK drivers installed for WIN10.
I have tried debug mode via startup options.
I have tried to run SP flash tool on 3 different laptops.
I have tried to run SP flash tool under admin rights and under different compatibility (7, XP)
But it is always the same - Options/COM Port is always greyed out, so I can not select the com port, the sub-navigation will not even roll out.
Using SP flash tool 5.1516
I have also tried newer SP flash tool, but the new one will not accept any scatter file and I have not found, how to alter scatter files to make them work.
Tried v5.1624
So - any advice/idea, why I can not see connected device in com ports?
Hey i have the same problem and I have not found the solution yet. If you find one you can share .
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.
I managed to identify the test point on the motherboard.
This allows the tablet to switch from Qualcomm HS-USB Diagnostics 900E driver mode to Qualcom HS-USB QDLoader 9008 mode.
My tablet could not be booted into bootloader, recovery or system.
Button vibration did not work.
The tablet only logged on to a PC with the Qualcomm HS-USB Diagnostics 900E driver.
The EDL cable did not help and the buttons of the 900E driver only restarted.
Photos and brief instructions I posted on the Russian forum here:
http://4pda.ru/forum/index.php?s=&showtopic=849554&view=findpost&p=90398828
I attach the photo here.
Only one hidden test point is connected to the metal frame (needle).
My tutorial on the Russian forum has been updated, missing the source file for MiFlash.
Today it was added.
Downgrade from Android 8.1 to 7.1.1 is possible!
Applies to tablets with unlocked bootloader.
The entire factory clean version must be reinstalled.
Use the same installation and tools as in the introductory link.
It is necessary to install in EDL mode.
To start EDL mode (driver 9008) from a working tablet, follow these steps:
1) Turn off the tablet
2) run the device manager in windows - ports
3) run and set up MiFlash (firmware path,option "save user data")
4) connect tablet to computer (USB)
5) hold all three buttons on the tablet (power+volumeUP+volumeDown) until the 9008 driver loads in the windows manager
6) run "refresh" in MiFlash without delay and immediately afterwards "flash"
It is important to start recording as soon as the driver is loaded, otherwise the input will close even if the driver remains loaded!
If there is a delay in recording, the EDL mode may close and the recording will not work.
In this case, you must start by disconnecting the tablet and turning it off.
The restored tablet remains unlocked (if you have unlocked it previously) while Lenovo updates work.
Hello i want to contact you are you still alive
I want to unbrixk my tab i accidentally deleted aboot.img
Hello i want to contact you
I want to unbrick my tab are you available???
Just to clarify, the test points on the board are the points you see on the board labeled "FORCE, VDD, TX, RX" and can be different sizes.
One such point was hidden under a folded out frame and that is the correct one. Connect this point with a needle to the metal frame and follow the order of operations in the instructions.
MiFlash - recommended:
Download in progress... | Xiaomi Tips
Thank you for downloading. Your download should start automatically in a few seconds.. Download FAQs Broken download link? Let us know. Is the file safe
xiaomitips.com
System:
TB-X304L_S000035_170703_ROW_QFIL.rar | by yulianto adikragil for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Follow the procedure.
After loading 9008, release the checkpoint as soon as possible.
I used XiaoMiFlash (beta).
You need to prepare XiaoMiFlash before taking action.
"Refresh" and "flash" should start immediately after disconnecting the breakpoints.
The path to the XiaoMiFlash firmware should only be "bat" files, not "images".
The fact that the 9008 driver loads in Windows indicates a functional boot.
You "only" need to complete the remaining steps correctly and on time.
If unsuccessful, repeat the procedure by disconnecting the battery.
If you changed the drivers manually, uninstall them first.
Let them download automatically.
There is a risk that this is not the 9008 driver.
You'll still need this:
The files contained in the image folder TB-X304L_S000035_170703_ROW_QFIL.rar need to be put into the inage folder X304L and then use this folder for MiFlash.
I have to thank You a lot. You saved my good old Lenovo. First when I read Your tutorial, I thought that could never ever work. I was exactly same problem as You were. I tried everything, even raindance. Nothing not helped. Two weeks with drivers, softwares, thousand tutorials...etc. But that did the trick! Now when I know How to unbrick totally dead Lenovo, it is actually only 10 minutes and lenovo fired up again.
Actually it is really easy do with linux by using QDL. No driver hassles or timing when connect or similar. I've linux installed, so if someone gonna try this, Live linux from USB stick working as well. User friendly could be for example Linux Mint Mate, Ubuntu...
1. Install Linux Your USB device and boot it by using Your PC.
2. Get QDL flash tool for Your PC (free and very easy to use).
3. Install QDL depencies: libxml2 and libudev (fastboot is optional, if unlocking bootloader same time).
sudo apt-get install libxml2 libudev fastboot
4. Stop modem manager: sudo systemctl stop ModemManager
5. Start flashing : ./qdl --storage emmc --include <Your Whole Stock firmware path> <Firehose path> <RAW program path (xml format)> <patch0 path (xml format)>
Enter and QDL start waiting for EDL device....
Next open second terminal for monitoring: dmesg and as You can see it is coursed 900e mode.
Next disconnect battery and leave it disconnected whole process time. Now it is time to short testpoint. reconnect device to PC when testpoint is shorted and check dmesg . When You'll see it changing 9008 mode. You're ready to start flashing. At this moment QDL still waiting EDL device > Ctrl+C and start over again ./qdl ...etc and flashing starting.
This is how easily You can hard unbrick Lenovo X304F Tab4 10 or X304L.
In my case I accidently Flashed X704 firmware to my device. It went just fine. But when booting, You know. I tought that's it! But It wasn't. Thanks again @StaryMuz.
I'm glad you found my advice helpful. The Linux tutorial is useful and it's good that you posted it.
i ended up bootlooping on the lenovo logo (tbx304L) and locked bootloader
and is it necessary to be on stock 8.1 to downgrade? @StaryMuz
the recovery shows 7.1.1 but still bootlooping
StaryMuz said:
I managed to identify the test point on the motherboard.
This allows the tablet to switch from Qualcomm HS-USB Diagnostics 900E driver mode to Qualcom HS-USB QDLoader 9008 mode.
My tablet could not be booted into bootloader, recovery or system.
Button vibration did not work.
The tablet only logged on to a PC with the Qualcomm HS-USB Diagnostics 900E driver.
The EDL cable did not help and the buttons of the 900E driver only restarted.
Photos and brief instructions I posted on the Russian forum here:
http://4pda.ru/forum/index.php?s=&showtopic=849554&view=findpost&p=90398828
I attach the photo here.
Only one hidden test point is connected to the metal frame (needle).
Click to expand...
Click to collapse
Many of the links for the rescue files are now missing but I will share how I rescued my TB-X304F in 2023. I followed your photo indicating the test point location/ trick along with the Lenovo Rescue and Smart Assistant program.
Rescue and Smart Assistant (RSA) - Lenovo Support US
support.lenovo.com
1) open the tablet
2) Remove the metal cover
3) Carefully Peel/bend the metal frame around the chip on the right in order to find the hidden test point. It is right under the frame. (the frame should gently move away from the chip, the frame is not difficult)
Now be sure to install the Lenovo Rescue and Smart Assistant program on your PC. Launch it, and look up the tablet's firmware by either S/N or manually looking it up. Download the necessary firmware files within the program until you get to the point of start rescue. Click Proceed, ok, ok, until you get to the screen that says: Find QDLoader COM Port which is asking you to hold the volume +&- but we have already tried that and didn't work so at this point then do the following:
- disconnect the battery
- connect the USB cable to the phone and computer
- Connect the test point with a needle (touch) to the frame and hold
- connect the battery and watch the driver in the windows manager
- as the 9008 driver loads, disconnect the point and let the Lenovo Rescue and Smart Assistant do its thing.
Tablet rescued!
Hello! I was wondering if someone could give me a hand. I have researched and tried several things to unbrick my TV box but no luck so far. I was using PhoenixSuit to flash a firmware to my Vontar V6 (H616) box and during the process Windows crashed. After the PC reboot, I noticed Windows 10 recognize the TV box (Device Manager) as Universal Serial Bus controllers -> USB Device (VID_1f3a_PID_efe8) but PhoenixSuit is unable to recognize it again as a device. I tried also flashing the firmware via PhoenixCard as well as accessing the box via adb and fastboot but no luck at all. Based on what I have researched, I believe the bootloader of the box is damaged. So any help or guidance to fix it would be mega appreciated. Thanks in advance, Marcello.