Hello all,
I'm at my wits end. Been trying for hours to unlock my new kindle fire hd 8 8th gen. Tried to do the mtk-su method which didn't work because my firmware is 6.3.1.4 Also tried the short circuit method and for some reason everytime I run the ./bootrom-step.sh nothing happens. I know I'm being very thorough with the instructions but I get stuck at this step. The prompt always starts at "Waiting for bootrom" I have no idea why it's being difficult with the HD8 when hours ago I unlocked the kindle fire 7 9th gen just fine using the short circuit method as well. Am I doing something wrong? Please help. Thanks in advance
Yes i have one of these too...
Are you running the bootrom-step, then shorting the clk to ground (shield), while plugging in the usb? When you plug it in, does it just boot up or does it go blank screen?
Just to clarify, you should have
"waiting for bootrom" on the PC
Then short the clk to ground
Plug in USB
Seems like a few people had to use a different USB port sometimes
Michajin said:
Yes i have one of these too...
Are you running the bootrom-step, then shorting the clk to ground (shield), while plugging in the usb? When you plug it in, does it just boot up or does it go blank screen?
Just to clarify, you should have
"waiting for bootrom" on the PC
Then short the clk to ground
Plug in USB
Seems like a few people had to use a different USB port sometimes
Click to expand...
Click to collapse
I run the bootrom-step, short the CLK while plugging the usb. When plugged, it doesn't boot up it just goes black screen. Every so often it will boot up but it's rather rare (while im performing the short)
Other than that, the kindle will boot up normally but not when I NEED it to :crying:
Reiixas said:
I run the bootrom-step, short the CLK while plugging the usb. When plugged, it doesn't boot up it just goes black screen. Every so often it will boot up but it's rather rare (while im performing the short)
Other than that, the kindle will boot up normally but not when I NEED it to :crying:
Click to expand...
Click to collapse
It should stay black when in the bootrom. What linux are you using? is it a live disk or Virtual disk? run lsusb (you should see MediaTek Inc. MT6227 phone) I have seen issues with this. I personally have been using this ...
https://github.com/amonet-kamakiri/fireiso/releases
It was developed for the firestick 4k but is all set up to run.
It could be a driver issue that isn't recognizing your hd8
Michajin said:
It should stay black when in the bootrom. What linux are you using? is it a live disk or Virtual disk? run lsusb (you should see MediaTek Inc. MT6227 phone) I have seen issues with this. I personally have been using this ...
https://github.com/amonet-kamakiri/fireiso/releases
It was developed for the firestick 4k but is all set up to run.
It could be a driver issue that isn't recognizing your hd8
Click to expand...
Click to collapse
I'm using Linux Mint live disk. Will look into that and let you know. Thank you for your help
Michajin said:
It should stay black when in the bootrom. What linux are you using? is it a live disk or Virtual disk? run lsusb (you should see MediaTek Inc. MT6227 phone) I have seen issues with this. I personally have been using this ...
https://github.com/amonet-kamakiri/fireiso/releases
It was developed for the firestick 4k but is all set up to run.
It could be a driver issue that isn't recognizing your hd8
Click to expand...
Click to collapse
Sorry to bother again, kind of a noob. What am I supposed to do with that fireiso?
Reiixas said:
Sorry to bother again, kind of a noob. What am I supposed to do with that fireiso?
Click to expand...
Click to collapse
Burn it to a USB flash drive. I use etcher to make a live disk...
https://www.balena.io/etcher/
Once complete reboot select removable media as a boot device.
---------- Post added at 11:38 AM ---------- Previous post was at 11:29 AM ----------
BTW, if you run lsusb from a command prompt you should see "MediaTek Inc. MT6227 phone" this is the bootrom, if you see "MediaTek Inc. MT65xx Preloader" you need to short it again. If the screen is black after you plug in, chances are you in preloader or the bootrom.
Michajin said:
Burn it to a USB flash drive. I use etcher to make a live disk...
https://www.balena.io/etcher/
Once complete reboot select removable media as a boot device.
---------- Post added at 11:38 AM ---------- Previous post was at 11:29 AM ----------
BTW, if you run lsusb from a command prompt you should see "MediaTek Inc. MT6227 phone" this is the bootrom, if you see "MediaTek Inc. MT65xx Preloader" you need to short it again. If the screen is black after you plug in, chances are you in preloader or the bootrom.
Click to expand...
Click to collapse
Hello,
Thank you for the help. I'm running the FireOS iso you sent. However, I'm stuck now on the fastboot step. Whenever I run ./fastboot-step.sh I get this output:
[[email protected] ~/Downloads/amonet]# ./fastboot-step.sh
fastboot: core/libsparse/sparse.cpp:131: int write_all_blocks(struct sparse_file *, struct output_file *): Assertion `pad >= 0' failed.
./fastboot-step.sh: line 5: 2468 Aborted (core dumped) fastboot flash boot bin/recovery-inj.img
[[email protected] ~/Downloads/amonet]#
Also, the kindle has the amazon logo , nothing else.
Reiixas said:
Hello,
Thank you for the help. I'm running the FireOS iso you sent. However, I'm stuck now on the fastboot step. Whenever I run ./fastboot-step.sh I get this output:
[[email protected] ~/Downloads/amonet]# ./fastboot-step.sh
fastboot: core/libsparse/sparse.cpp:131: int write_all_blocks(struct sparse_file *, struct output_file *): Assertion `pad >= 0' failed.
./fastboot-step.sh: line 5: 2468 Aborted (core dumped) fastboot flash boot bin/recovery-inj.img
[[email protected] ~/Downloads/amonet]#
Also, the kindle has the amazon logo , nothing else.
Click to expand...
Click to collapse
I've fixed this by running a debian based linux. I'm officially rooted. THANK YOU!
By any chance is there any lineage OS thread for this HD8 8th gen?
Reiixas said:
I've fixed this by running a debian based linux. I'm officially rooted. THANK YOU!
By any chance is there any lineage OS thread for this HD8 8th gen?
Click to expand...
Click to collapse
LineageOS for Fire HD 8 (2018):
7.1.2 Nougat: https://forum.xda-developers.com/hd8-hd10/orig-development/lineageos-14-1-fire-hd8-2018-t3936242
9 Pie: https://forum.xda-developers.com/hd8-hd10/orig-development/rom-lineage-16-0-t3981685
Can you flash it from TWRP.
Reiixas said:
I've fixed this by running a debian based linux. I'm officially rooted. THANK YOU!
By any chance is there any lineage OS thread for this HD8 8th gen?
Click to expand...
Click to collapse
Awesome.. Give me a few thanks for the help please...
I would recommend for stable build
[ROM][unlocked][karnak] Lineage-14.1 [02 JAN 2020]
https://forum.xda-developers.com/hd8-hd10/orig-development/lineageos-14-1-fire-hd8-2018-t3936242
I wouldn't do anything with 16.0 as the OP is getting close to having a good LOS 17.1 and 16 is still pretty buggy.
Don't forget- Make a backup before you do anything to give you a safe place to restore to.
Help for root/ unlock HD8
Hi! I am newbie in here. I am find the way how to root HD8 ( 8th generation) fire os 6.3.1.4 and Install Android OS. Can anyone help me?
Thank you very much!
Alesksel said:
Hi! I am newbie in here. I am find the way how to root HD8 ( 8th generation) fire os 6.3.1.4 and Install Android OS. Can anyone help me?
Thank you very much!
Click to expand...
Click to collapse
Start here
Fire HD 8 (2018 ONLY) unbrick, downgrade, unlock & root
https://forum.xda-developers.com/hd...fire-hd-8-2018-downgrade-unlock-root-t3894256
You will have to do the hardware method (it's easy)
Software method - Amazon Fire HD 8 2018 -- up to Fire OS 6.3.0.1 only
Read the thread if you have questions, I can try and help if you need it....
<Yet another snip>
Related
Hi,
Just recently I had an issue with my kindle where it had entered the OMAP4430 USB BOOT MODE.
Nothing would show up on the screen and when plugging it into windows it came up as a OMAP4430 device. However, I couldn't install drivers or anything because it was in a constant loop of disconnecting and reconnecting. However thanks to the Developers on the IRC and a response in my thread by pokey9000 (Creator of the utility we are going to use).
1. Download the rekindle utility from this thread:
http://forum.xda-developers.com/showthread.php?p=20565446
2. You need to be running a flavour of linux such as Ubuntu or Debian (You can install using Wubi).
3. Follow the steps in that guide. If you are on a 64bit linux you need to type in:
apt-get install ia32-libs (as a root user using sudo or su root)
4. Your Kindle should now be ressurected.
XperiaPlayer said:
Hi,
Just recently I had an issue with my kindle where it had entered the OMAP4430 USB BOOT MODE.
Nothing would show up on the screen and when plugging it into windows it came up as a OMAP4430 device. However, I couldn't install drivers or anything because it was in a constant loop of disconnecting and reconnecting. However thanks to the Developers on the IRC and a response in my thread by pokey9000 (Creator of the utility we are going to use).
1. Download the rekindle utility from this thread:
http://forum.xda-developers.com/showthread.php?p=20565446
2. You need to be running a flavour of linux such as Ubuntu or Debian (You can install using Wubi).
3. Follow the steps in that guide. If you are on a 64bit linux you need to type in:
apt-get install ia32-libs (as a root user using sudo or su root)
4. Your Kindle should now be ressurected.
Click to expand...
Click to collapse
help me
My kindle fire fails the same. I did follow the instructions
my PC screen
waiting for OMAP44xx device...
sending 2ndstage to target...
waiting for 2ndstage response...
sending image to target...
<waiting for devices>
Then I tried fastboot to no avail... Can you help? I did the shorting trick for many times and it all ended up the same way.
kindlef said:
help me
My kindle fire fails the same. I did follow the instructions
my PC screen
waiting for OMAP44xx device...
sending 2ndstage to target...
waiting for 2ndstage response...
sending image to target...
<waiting for devices>
Then I tried fastboot to no avail... Can you help? I did the shorting trick for many times and it all ended up the same way.
Click to expand...
Click to collapse
same here stucked aT WAITING 4 DEVICE
Adeel1234 said:
same here stucked aT WAITING 4 DEVICE
Click to expand...
Click to collapse
same here
Just recently I had an issue with my kindle where it had entered the OMAP4430 USB BOOT MODE.
"Nothing would show up on the screen and when plugging it into windows it came up as a OMAP4430 device. However, I couldn't install drivers or anything because it was in a constant loop of disconnecting and reconnecting."
kindlef said:
same here
Just recently I had an issue with my kindle where it had entered the OMAP4430 USB BOOT MODE.
"Nothing would show up on the screen and when plugging it into windows it came up as a OMAP4430 device. However, I couldn't install drivers or anything because it was in a constant loop of disconnecting and reconnecting."
Click to expand...
Click to collapse
i think rekindle utility and firekit should be made up again for cm9 or latest amazon updates bcoz the given version is of dec 2011.when cm9 didnt come up..
Mr.Kindlef i think we have wasted our kindles because no one is helping us in this thread or anywhere
ok i had just that issue.
are you trying to run it through your desk top ubuntu or are you using livecd/usbpendrive? sorry wrong thread.
but ive just performed this and it works perfect. just keep it shorted until it finishes scripts
Cool
Sent from my iPhone using Tapatalk
Hello, i have the following problem, just after have rooted my 6.2.1 Kindle Fire and tryed to install TWRP, when i rebooted my device it remains stuck at the KINDLE FIRE logo.
Adb doesn't recognize the device anymore and keep telling me there are no devices connected.
I tryed on Macbook and Windows too.
Can anyone help me?
any one help me??? i try kindle fire utility, kindle fire unbrick but nothing happens
please help me......
tobyax said:
Hello, i have the following problem, just after have rooted my 6.2.1 Kindle Fire and tryed to install TWRP, when i rebooted my device it remains stuck at the KINDLE FIRE logo.
Adb doesn't recognize the device anymore and keep telling me there are no devices connected.
I tryed on Macbook and Windows too.
Can anyone help me?
Click to expand...
Click to collapse
Sure can bud... Here is a link to my guide that you should follow.... If you did you would not have this problem. There are two ways that you can fix it manually and automatically. The automatic way was just updated onto my guide today but is for windows only. The manual way is right under that update for individuals that want to do it to understand things better or on a different os on their pc... Good luck and if you have anymore problems, you can feel free to pm me and I can either walk you through it on irc or teamviewer....
DONT FORGET TO HIT THE THANKS BUTTON IF I HELPED YOU PLEASE!!!!
here is a link to my guide:
http://forum.xda-developers.com/showthread.php?t=1417234
I'll try to install an other version of windows on vmware to try to fix the kinlde fire. Thanks for now
now the kindle fire with usb attached lights and turns off all the time, without usb does not turn on..
sorry for my bad english
tobyax said:
I'll try to install an other version of windows on vmware to try to fix the kinlde fire. Thanks for now
now the kindle fire with usb attached lights and turns off all the time, without usb does not turn on..
sorry for my bad english
Click to expand...
Click to collapse
Which version of kindle fire utility did you use? You have to be sure that it is ver.0.9.1 because the version before that there was a problem with the twrp file in older versions of the kindle fire utility.
Also are you sure that your battery was charged before you started to do this?
Like I said if you continue to have problems I can get on teamviewer with you and show you how to reinstall the drivers manually so that you can access your adb shell to change fastboot. Just pm me if you have anymore problems and need someone to do it for you..
i used the last version of kindle fire utility 0.9.1 and the battery was charging, I believe that now is completely discharged
I'm installing latest version of Windows XP on vmware, if you want to help me after I would be grateful...
sorry again for my bad english
tobyax said:
i used the last version of kindle fire utility 0.9.1 and the battery was charging, I believe that now is completely discharged
I'm installing latest version of Windows XP on vmware, if you want to help me after I would be grateful...
sorry again for my bad english
Click to expand...
Click to collapse
I sure will make sure that you get teamviewer if you do not already have it. When you are using windows xp make sure your .android folder is in the proper place
C:\Documents and Settings\YourUserName\
Just making sure that your .android folder is in the correct place. It should be though if you installed root and android market already though.
nothing, now the kindle fire don't start enymore i think the battery is over.....
tobyax said:
Hello, i have the following problem, just after have rooted my 6.2.1 Kindle Fire and tryed to install TWRP, when i rebooted my device it remains stuck at the KINDLE FIRE logo.
Adb doesn't recognize the device anymore and keep telling me there are no devices connected.
I tryed on Macbook and Windows too.
Can anyone help me?
Click to expand...
Click to collapse
I have same problem and I was tried all knowed "guides and How to" for unbricking my Kindle Fire... . But solution is so easy!
Let's try http://forum.xda-developers.com/showthread.php?t=1428428 ... choose option 1-Stuck at boot logo... and after that when the app ask you "Does you have FIREFIREFIRE" reply no... .
I must use this app twice because at first try app doesn't do anything... . But now my Kindle finaly works!
tobias,
io ho il tuo stesso problema: hai risolto??? Se si mi dici cosa hai fatto?
Hi, i got my kindle fire 3 days ago. The first day I installed ice cream sandwich, the March 19th ICS CM9 Kang ROM, everything was running excellent and smooth. Last night, before going to sleep I plugged it. This morning i press the power button and it wakes up, but after 2 minutes of use the screen started to flash in gray tones, I though it had crashed and reboot it(press the power button for 25 secs), after I turn it back on it shows the FIREFIREFIRE triangle for 1 sec and started to flash this awful gray screen. And after that it didn't show any image, the back light turns on but it doesn't show nothing.
I know its booting into ICS because I still get the email alert sound.
I'm thinking on returning it as i bought it at a local walmart. I'm just concern about the fact its flashed to ICS. I know the way on how to take it back to stock, the thing is i just can't see anything on the screen and I'm not sure if the touch sensors still work.
Also when i plug it to the pc and run the KFU it show the status as offline and the power button turn orange.
I really don't know what to do right now, i guess it's just bad luck for getting a defective one. Any tip, advice or suggestion will be appreciated.
Is adb working? Use adb or fastboot to install the stock room
Sent from my Amazon Kindle Fire using Tapatalk
ammubarak said:
Is adb working? Use adb or fastboot to install the stock room
Sent from my Amazon Kindle Fire using Tapatalk
Click to expand...
Click to collapse
Hey thank you for your answer, Excuse me but I'm not that experienced with android and adb, can you tell me how to check if adb is working. Also how to install the stock rom through it.
gustavosuarez4 said:
Hey thank you for your answer, Excuse me but I'm not that experienced with android and adb, can you tell me how to check if adb is working. Also how to install the stock rom through it.
Click to expand...
Click to collapse
OK, plug kindle into computer, go to cmd, change directory to android-sdk/platform-tools, type:
Code:
adb
adb remount
adb devices
then your kindle serial should popup in cmd... report back and I can help.
BiteBlaze said:
OK, plug kindle into computer, go to cmd, change directory to android-sdk/platform-tools, type:
Code:
adb
adb remount
adb devices
then your kindle serial should popup in cmd... report back and I can help.
Click to expand...
Click to collapse
I did that but when i type remount it says "error: device not found" and on adb devices it doesn't show any device. :/ Is the any other possibility?
PD: The touch screen is working, and I wanna try to do the stock restoration through the kindle. Right now i'm able to unlock to the main screen. I just need to mount the usb storage to copy the official update in the kindle's sd card root and then try to restore using TWRP it being blind wow. Any other ideas?
PD: How can i check if the drivers are working properly?
gustavosuarez4 said:
I did that but when i type remount it says "error: device not found" and on adb devices it doesn't show any device. :/ Is the any other possibility?
PD: The touch screen is working, and I wanna try to do the stock restoration through the kindle. Right now i'm able to unlock to the main screen. I just need to mount the usb storage to copy the official update in the kindle's sd card root and then try to restore using TWRP it being blind wow. Any other ideas?
PD: How can i check if the drivers are working properly?
Click to expand...
Click to collapse
Look for the drivers in KFU... if not u can Google kindle fire drivers
Sent from my Kindle Fire with CM9
BiteBlaze said:
Look for the drivers in KFU... if not u can Google kindle fire drivers
Sent from my Kindle Fire with CM9
Click to expand...
Click to collapse
would you do me a favor? please, if you have cm9 can you upload screenshots of this specific screens on your kindle?
-locked screen on portrait mode.
-screen when you plug your kindle to your computer and it ask you to mount as USB massive storage on portrait mode.
I will try to restock it this way cuz i already tried with the KFU drivers and is not working and i dont know if i have adb enabled on the kindle.
http://db.tt/dPqw4dTv
Here... hope this helps!
Keep in mind that this is a custom version of Cm9 I am working on
Sent from my Kindle Fire with CM9
Sorry, forgot other link http://db.tt/BUdgrORZ
Sent from my Kindle Fire with CM9
BiteBlaze said:
Here... hope this helps!
Keep in mind that this is a custom version of Cm9 I am working on
Sent from my Kindle Fire with CM9
Click to expand...
Click to collapse
Thank you, believe it or not that picture helped me a lot, i was able to access the sd card and copy the original update, now I'm charging the kindle in order to restore it being blind. God help me, I've been watching lots of videos. Wish i could use adb.
gustavosuarez4 said:
Thank you, believe it or not that picture helped me a lot, i was able to access the sd card and copy the original update, now I'm charging the kindle in order to restore it being blind. God help me, I've been watching lots of videos. Wish i could use adb.
Click to expand...
Click to collapse
Well, its good that you figured it out
Sent from my Kindle Fire with CM9
Not working anymore.
Sorry.
Do you mean that you had your old tablet already killed, and then you recovered it following these steps?
You can see it here, in my Twitter
https://twitter.com/victorcangil16/status/642389331768942592
Can anyone confirm this on a separate dead tablet? if so its a pretty damn good find.
Hi Victorcangil 16,
Could you exactly discribe how did you make this miracle (which drivers...) ?
Thanks
jo2e said:
Hi Victorcangil 16,
Could you exactly discribe how did you make this miracle (which drivers...) ?
Thanks
Click to expand...
Click to collapse
I used Windows 10 with the NVIDIA Family USB Drivers. I made the process I described in the first post
Victorcangil 16 said:
I used Windows 10 with the NVIDIA Family USB Drivers. I made the process I described in the first post
Click to expand...
Click to collapse
Ok,
Thx for your reply Victorcangil 16.
But how did your device was recognized by windows before done this process ? APX or something else
It was reconized as normal device by Windows, like if I plug my phone to the PC. And the drivers I had to configure them manually, if not, It gives me error when doing FastBoot
Victorcangil 16 said:
It was reconized as normal device by Windows, like if I plug my phone to the PC. And the drivers I had to configure them manually, if not, It gives me error when doing FastBoot
Click to expand...
Click to collapse
It stay on :"<waiting for device>"
And my tablet is not reconized as normal device but as "APX"
What does APX mean?
Change the ADB drivers interface using the next process:
Search in Windows: Device Manager
If the ADB interface has a Yellow alert, Right Click, Update Drivers, Select from Computer, Use Disk, Use all, and then select the file in the NVIDIA Drivers folder (in my case, Downloads). Accept,
Victorcangil 16 said:
What does APX mean?
Click to expand...
Click to collapse
I don't known. My tablet appears like that in the peripherics manager ...
If you hace skype, I can help you easily
Victorcangil 16 said:
If you hace skype, I can help you easily
Click to expand...
Click to collapse
Yes i have skype.
But i think i got the problem : my tablet wasn't rooted and the bootloader was locked...
I think you saved your shield because it was rooted...
I thinks is that. If is has not unlocked bootloader, you can't change nothing. But to unlock it, just type in Fastboot: "fastboot oem unlock" (tablet will Factory Reset)
Victorcangil 16 said:
I thinks is that. If is has not unlocked bootloader, you can't change nothing. But to unlock it, just type in Fastboot: "fastboot oem unlock" (tablet will Factory Reset)
Click to expand...
Click to collapse
Same thing with this command : <waiting for device>
:/ I think something is going on with Drivers
Hi, one question for such kind of reactivation - root is required ?
Yes, Root and Unlocked Bootloader are required ro recover the "killed" Tablet
Just bought by mistake deactivated Shield...is it possible to make root via fastboot ?
Hello, intelligent readers,
I own a tablet. My tablet is an Amazon Fire HD 10 7-generation
My problem is I've been trying to "root/en" it with the "One Click Root" method
and it failed at 98% with the error message (Fail).
After a reboot (Loop/t)( it's the "Fire" logo all the time but I still get into the "Amazon system recovery <3e>")
with the following selectable options;
1. (reboot system now)
2. (apply update from ADB)
3. (wipe data/factory reset)
4. (wipe cache partition)
5. (reboot to bootloader)
Six. (power down)
7th (view recovery logs)
Important information:
Linux and Windows 7 64-bit "I can follow all instructions, trust me"
"E:Battery level is too low to perform update or factory reset" Do I need a cable with transistors?
Phone is not recognized via USB (you may need the correct driver) (Manual)
I hope and pray to God that you can help me with my problem.
BrainAtWork said:
Hello intelligent teachers,
I hope and pray to God you can help me with my problem.
My phone is a "Amazon Fire HD 10 7generation"
I was rooting with (one click root) it failed at 98% and now it's looping the fire logo for eternity.
I can boot the recovery mode but;
"low battery state" won't go away after 10hours charging.
Phone is not recognized per usb (maybe right driver needed)
got Linux and Windows 7 64bit (I am able to do all instructions trust me)
Is there hope to do something by myself ?
Click to expand...
Click to collapse
Reflash the firmware using fastboot
Link for tutorial : https://wheresmykeyboard.com/2020/01/how-to-restore-amazon-fire-hd-8-10-to-stock-firmware/
(Don't use the firmware on tutorial website)
Download the firmware from here : https://www.amazon.com/gp/help/customer/display.html?nodeId=G2JXLC4L34GX73TE (select ur device Amazon fire hd 10 2017)
Don't forget to install fastboot driver
Tell me if it works
Amazon drivers Installed.
Adb + fastboot Installed.
C:\adb>adb devices
List of devices attached
*daemon not running. starting it now on port 5037
*daemon started successfully *
C:\adb>adb devices "if again"
List of devices attached
C:\adb> sideload update-kindle-40.6.5.0_user_650601220.bin
loading: 'update-kindle-40.6.5.0_user_650601220.bin'
error: device '<null>' not found
please help me
BrainAtWork said:
Amazon drivers Installed.
Adb + fastboot Installed.
C:\adb>adb devices
List of devices attached
*daemon not running. starting it now on port 5037
*daemon started successfully *
C:\adb>adb devices "if again"
List of devices attached
C:\adb> sideload update-kindle-40.6.5.0_user_650601220.bin
loading: 'update-kindle-40.6.5.0_user_650601220.bin'
error: device '<null>' not found
please help me
Click to expand...
Click to collapse
You got any other android phone? Try to plug the phone while it's on fastboot mode..does ur pc detects it..
Roowz said:
You got any other android phone? Try to plug the phone while it's on fastboot mode..does ur pc detects it..
Click to expand...
Click to collapse
Same error in fastboot mode.
Next step is help me to detect the device.
https://forum.xda-developers.com/amazon-fire/general/unbrick-amazon-fire-7in-2015-5th-gen-t3285294
This thread has some good info on getting driver's set up correctly. Helped me out when I had a similar issue.
Obviously you'd use the correct firmware for your device instead.
Kctucka said:
https://forum.xda-developers.com/amazon-fire/general/unbrick-amazon-fire-7in-2015-5th-gen-t3285294
This thread has some good info on getting driver's set up correctly. Helped me out when I had a similar issue.
Obviously you'd use the correct firmware for your device instead.
Click to expand...
Click to collapse
Still Device not detected by device manager. Can you help me specify the driver packages or etc.
Please do not tell me I have to pay 50€ (in my country) for a repair. Tell me what the professionals do. Only as long as the equipment costs less than 50€. Because I have 2 devices that are even worse bricked.
BrainAtWork said:
Please do not tell me I have to pay 50€ (in my country) for a repair. Tell me what the professionals do. Only as long as the equipment costs less than 50€. Because I have 2 devices that are even worse bricked.
Click to expand...
Click to collapse
Well your tablet is just soft bricked.. Don't send it to repair yet.. Does your cable support data transfer? Try to plug ur tablet to different pc..
Roowz said:
Well your tablet is just soft bricked.. Don't send it to repair yet.. Does your cable support data transfer? Try to plug ur tablet to different pc..
Click to expand...
Click to collapse
Yes my cable support data transfer (before failed root it was detected)
Tell me more about a special factory cable with transistor.
I got 2 operating Systems Windows 7 and Linux it's like a different pc.
BrainAtWork said:
Yes my cable support data transfer (before failed root it was detected)
Tell me more about a special factory cable with transistor.
I got 2 operating Systems Windows 7 and Linux it's like a different pc.
Click to expand...
Click to collapse
Since ur another phone isn't detected on fastboot mode.. I think there's something wrong with either the usb port, cable,drivers or your laptop.. Special factory cable isn't necessary in this case.. Lemme try to search if there's other people getting this problem... Btw can u factory reset?
BrainAtWork said:
Hello, intelligent readers,
I own a tablet. My tablet is an Amazon Fire HD 10 7-generation
My problem is I've been trying to "root/en" it with the "One Click Root" method
and it failed at 98% with the error message (Fail).
After a reboot (Loop/t)( it's the "Fire" logo all the time but I still get into the "Amazon system recovery <3e>")
with the following selectable options;
1. (reboot system now)
2. (apply update from ADB)
3. (wipe data/factory reset)
4. (wipe cache partition)
5. (reboot to bootloader)
Six. (power down)
7th (view recovery logs)
Important information:
Linux and Windows 7 64-bit "I can follow all instructions, trust me"
"E:Battery level is too low to perform update or factory reset" Do I need a cable with transistors?
Phone is not recognized via USB (you may need the correct driver) (Manual)
I hope and pray to God that you can help me with my problem.
Click to expand...
Click to collapse
Here is a full method to unbrick your Fire tablet using exploit:
Unbrick from anti-rollback (needed to take off the back cover of your device and motherboard):
https://forum.xda-developers.com/hd...-fire-hd-10-unbricking-anti-rollback-t3896616
Unbrick/Unlock/Root/TWRP (doesn't needed to take off your device. Unbrick method is in post 2):
https://forum.xda-developers.com/hd8-hd10/orig-development/unlock-fire-hd-10-2017-suez-t3913639
You have to use Linux (not Windows) on your PC to use an exploit packages.
AmznUser444 Dev said:
Here is a full method to unbrick your Fire tablet using exploit:
Unbrick from anti-rollback (needed to take off the back cover of your device and motherboard):
https://forum.xda-developers.com/hd...-fire-hd-10-unbricking-anti-rollback-t3896616
Unbrick/Unlock/Root/TWRP (doesn't needed to take off your device. Unbrick method is in post 2):
https://forum.xda-developers.com/hd8-hd10/orig-development/unlock-fire-hd-10-2017-suez-t3913639
You have to use Linux (not Windows) on your PC to use an exploit packages.
Click to expand...
Click to collapse
Well actually i think this isn't necessary.. Since his phone is just soft bricked(that method is for hardbrick, however it can fix softbrick but its more complicated than the fastboot method that i told him.. And his pc doesn't detect his tablet while it's on fastboot mode.. And both method requires fastboot mode..
---------- Post added at 03:08 AM ---------- Previous post was at 03:05 AM ----------
I got bootloop before on my tablet (2-3 months ago) and i fixed it by reinstalling the firmware using adb push(fastboot method) ..my tablet was detected on fastboot mode and the tablet is back alive..
deleted
deleted