Related
Hi,
My rooted KF started behaving, weirdly so I decided to start from scratch and unroot it using the ClockworkMod recovery utility interface that was automatically loaded when I rooted it using Breakdroid. It started life with 6.2.2 but then updated itself to 6.3, so I downloaded the following file to do the unroot, and converted it into a .zip file called update.zip.
//kindle-fire-updates.s3.amazon...1E_4019920.bin
and went into the ClockworkMod recovery utility mounted my KF, did a factory reset, then applies sdcard update.zip which appeared to perform sucessfully, however when I rebooted, it launched the Stock KF screen, no fire fire fire, and has since stayed there. Can anyone please help! Many thanks.
Does KFU recognize it? If it does you are good to go.
Hi,
Nope. I'm using a Mac, so I use Breakdroid, and it's not picking it up.
http://forum.xda-developers.com/showthread.php?t=1644970
soupmagnet said:
http://forum.xda-developers.com/showthread.php?t=1644970
Click to expand...
Click to collapse
Keep up the good work soupmagnet!
Thanks soupmagnet,
I know it's the same question asked over and over again, I'll give it a shot and let you know if I sort it out. Appreciate your time.
All things point to a factory usb cable which I have ordered. Now I have to read books the old way...analogue!
nickvon said:
All things point to a factory usb cable which I have ordered. Now I have to read books the old way...analogue!
Click to expand...
Click to collapse
Actually a factory cable, while nice to have, doesn't seem necessary in your case. (Hint Read about the different bootmodes.
Hi again Soupmagnet,
So I eventually got hold of my factory cable which I ordered off Ebay from Hong Kong, so I plugged it in and hey presto, nothing happened. I'm still stuck on the Kindle Fire screen. I've been using a Mac and Breakdroid doesn't pick it up at all. I decided to see if a PC could pick it up using KFU, and it's still offline, although in My Computer I do see an external drive and device manager does call it Kindle. I have a feeling I am the 1% of bricked Kindle Fire users that have well and truly properly bricked their Kindle. Could it perhaps be the cable not in fact being a factory cable at all? I'm getting pretty desperate with this situation. Can you offer me advise.
Nickvon
Oh and further to my last I was changing boot modes but as it couldn't recognize the device, it was pointless.
nickvon said:
I have a feeling I am the 1% of bricked Kindle Fire users that have well and truly properly bricked their Kindle.
Click to expand...
Click to collapse
Take a breath, relax, and rest assured that you are more likely in the upper 90% range.
As I said before, the factory cable, while nice to have isn't usually required to fix most devices. All it does, is puts the device in fastboot mode and provides direct power to the device via usb in case of low or now power
Your problem is simply a matter of fixing your drivers so you can communicate with the device and change the bootmode.
[Edit:] It's been a while since this post was first started so I forgot you were using Mac instead of Windows.
Open your Terminal and enter the following:
Code:
cat ~/.android/adb_usb.ini
Your output should read:
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x1949
Anything other than would explain why you aren't able to change the bootmode normally.
Are you using Terminal commands to change the bootmode or are you using Breakdroid?
I rooted my Kindle Fire about a month ago with KFU. Everything was fine until I turned it on one day and I got stuck at the Triangle screen. None of the reboot tricks work. The interesting thing which I think is what is stopping me from being able to successfully use other methods is that when I plug my Kindle Fire into my computer via usb, it connects, and then disconnects (the USB) about 2 seconds later. I've tried different ports, etc. Any help on this issue would be greatly appreciated. I've read over multiple things, but don't see a mention to the kindle being disconnected via usb so quickly, thus stopping me from being able to do anything.
Care to elaborate on what "reboot tricks" you've used?
What version of Windows are you using?
soupmagnet said:
Care to elaborate on what "reboot tricks" you've used?
What version of Windows are you using?
Click to expand...
Click to collapse
I've tried the rebooting the Kindle while trying to reset the kindle to booting "normally" within the KFU. I've tried holding down the power button on a reset, then pushing it again until it is orange, none seem to work. I'm confident I could get it to work again if the kindle did not disconnect from my computer so quickly. By this I mean I hear the "usb chime" when I plug it in, then within seconds the disconnect chime plays. During the brief few seconds it is connected, it shows up on my devices list, but obviously when the usb disconnect chime plays, it disappears off of the device list.
edit: I'm using windows 7 Ultimate.
Can anyone help me? I may add that My Kindle Fire was originally rooted with the KFU and worked perfectly fine. I literally turned it on one day, and it got stuck at the triangle screen. The connection issue of it disconnecting so quickly is what is stopping me from fixing it I believe. Please help.
ErikV55 said:
Can anyone help me? I may add that My Kindle Fire was originally rooted with the KFU and worked perfectly fine. I literally turned it on one day, and it got stuck at the triangle screen. The connection issue of it disconnecting so quickly is what is stopping me from fixing it I believe. Please help.
Click to expand...
Click to collapse
Read the first 3 posts here...
http://forum.xda-developers.com/showthread.php?t=1552547
Figure out what device drivers are getting loaded when the connect "chimes" sound in Windows. If you confirm that they are correct based on the contents above, you must stop the temporary fastboot, set the bootmode to normal using fastboot, and restart the device.
I suspect you've got more issues than just getting stuck on the bootloader though... If you are getting disconnect tones in the bootloader, that means it's attempting to boot into something, but obviously unable to do so.
kinfauns said:
Read the first 3 posts here...
http://forum.xda-developers.com/showthread.php?t=1552547
Figure out what device drivers are getting loaded when the connect "chimes" sound in Windows. If you confirm that they are correct based on the contents above, you must stop the temporary fastboot, set the bootmode to normal using fastboot, and restart the device.
I suspect you've got more issues than just getting stuck on the bootloader though... If you are getting disconnect tones in the bootloader, that means it's attempting to boot into something, but obviously unable to do so.
Click to expand...
Click to collapse
The disconnect tones are from my computer, the same tone when you unplug a usb (since the kindle is plugged in via usb) I can't change the bootmode because the usb disconnect chime happens literally 2 seconds later, and the kindle is disconnected, all the while the kindle is still on and showing the triangle screen.
ErikV55 said:
The disconnect tones are from my computer, the same tone when you unplug a usb (since the kindle is plugged in via usb) I can't change the bootmode because the usb disconnect chime happens literally 2 seconds later, and the kindle is disconnected, all the while the kindle is still on and showing the triangle screen.
Click to expand...
Click to collapse
Have you checked to see what drivers are getting loaded? Do you know what device should appear in the device manager? Have you tried to stop the temporary fastboot countdown? Do you know how to stop the temporary fastboot countdown?
If you aren't willing to try out my suggestions, there's not much else I can do.
kinfauns said:
Have you checked to see what drivers are getting loaded? Do you know what device should appear in the device manager? Have you tried to stop the temporary fastboot countdown? Do you know how to stop the temporary fastboot countdown?
If you aren't willing to try out my suggestions, there's not much else I can do.
Click to expand...
Click to collapse
Yes to all those things. The device does indeed pop up in the device manager but only for the brief 2 second window before it disconnects. I've tried multiple usb ports on my pc with the same result. The kindle does not power off in any way when the it disconnects from the pc.
ErikV55 said:
Yes to all those things. The device does indeed pop up in the device manager but only for the brief 2 second window before it disconnects. I've tried multiple usb ports on my pc with the same result. The kindle does not power off in any way when the it disconnects from the pc.
Click to expand...
Click to collapse
What is the device name that comes up?
What command did you send to stop the countdown?
What did it output as a result of the command?
What makes you think that it should power off when you disconnect from the PC?
kinfauns said:
What is the device name that comes up?
What command did you send to stop the countdown?
What did it output as a result of the command?
What makes you think that it should power off when you disconnect from the PC?
Click to expand...
Click to collapse
I've tried to reset the bootmode via the KFU method recommended in the guide posted here (normal, 4000 and trying to reset when it says waiting for device) The device pops up in the device manager as an "unknown device" which may be a problem with the version of the drivers im DLing. I'm using KFU version 0.9.6
When I first DLed them it seemed as if the drivers were installing correctly, when I plugged in the Kindle is said drivers were being installed but it failed because the device disconnected after the 2 seconds.
Rapid disconnects are nothing unique, they're simply driver or USB problems. Any malfunctioning USB device will give you that same sequence. Anyways, it's difficult to get out of a boot-loop without ADB so let's try to get that USB working again.
First, do you have a bootloader (like FFF) or a recovery (like TWRP) loaded? I'm not sure the USB driver will work during boot without at least one of those installed.
Second, boot into TWRP, then try to fix the USB from the computer end. Uninstall the drivers, download a fresh batch, reinstall drivers, reboot. Use explorer to check %userprofile%\.android\adb_usb.ini and make sure 0x1949 is there. Also check Kindle Fire Utility\drivers\kindle\android_winusb.inf and make sure whatever hardware ID is showing up in device manager is in there.
BTW, what device IS showing in Device Manager after the disconnect? Use right click, scan for hardware changes.
Third, the USB cable or ports themselves may be at fault. Try a different cable, and try a different computer. Also, reboot often.
hunterhk said:
Rapid disconnects are nothing unique, they're simply driver or USB problems. Any malfunctioning USB device will give you that same sequence. Anyways, it's difficult to get out of a boot-loop without ADB so let's try to get that USB working again.
First, do you have a bootloader (like FFF) or a recovery (like TWRP) loaded? I'm not sure the USB driver will work during boot without at least one of those installed.
Second, boot into TWRP, then try to fix the USB from the computer end. Uninstall the drivers, download a fresh batch, reinstall drivers, reboot. Use explorer to check %userprofile%\.android\adb_usb.ini and make sure 0x1949 is there. Also check Kindle Fire Utility\drivers\kindle\android_winusb.inf and make sure whatever hardware ID is showing up in device manager is in there.
BTW, what device IS showing in Device Manager after the disconnect? Use right click, scan for hardware changes.
Third, the USB cable or ports themselves may be at fault. Try a different cable, and try a different computer. Also, reboot often.
Click to expand...
Click to collapse
Thanks for your response, I will go through these and report back when I get back home from class.
ok, now I have my kindle being recognized by my computer as "android phone" with the sub of "android adb interface." If I have read the guide correctly that means it is in fastboot mode. However when I open kfu it says the kindle is offline.
If someone would be willing to help me out through Skype I would gladly appreciate it. I'm really at a lose as to what to do at this point.
and no stupidly I do not have FFF or TWRP loaded, since I first rooted it when I was a super noob. The usb driver seems like it should be able to work according the the Kindle fire beginners guide, but KFU does not recognize the kindle even though my computer does.
I was attempting to root my friend's Kindle fire with the SuperOneClick method. You can google (kindle fire root) and it is like the second result I think. I would link it to you, but XDA tries to prevent spam by disallowing me to do so (good idea, just not working in my favor atm xD)
After completing all the steps and running the final program, it became stuck on step #7. I scrolled the comments and it seems like about half of them were of people getting stuck on step #7. So I thought nothing of it and tried to just switch to a different method which is Kindle Fire Utility. It had a problem with adb and couldn't get in touch with the device.
We tried to reboot the device, but it became stuck on the kindle fire boot screen. All it says is Kindle Fire and it stays on forever unless I press on the power button for over 20 seconds.
After fiddling with the drivers for what seemed to be an eternity, I finally gave up and went home (switched to Ubuntu 12.04 x64).
So after installing the JDK, Android SDK, and configuring everything the way they need to be configured, adb could still not even find the device.
adb_usb.ini
[email protected]:~/.android$ cat adb_usb.ini
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x1949
0x0006
0x181D
Click to expand...
Click to collapse
Android rules
[email protected]:/etc/udev/rules.d$ cat 51-android.rules
SUBSYSTEM=="usb", SYSFS{idVendor}=="1949", MODE="0666"
Click to expand...
Click to collapse
Here is some output I get from adb after I tried restarting it and starting it back up again with the above files the way they are.
[email protected]:~/Downloads/android-sdk-linux/platform-tools$ ./adb kill-server
[email protected]:~/Downloads/android-sdk-linux/platform-tools$ ./adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:~/Downloads/android-sdk-linux/platform-tools$ ./adb devices
List of devices attached
[email protected]:~/Downloads/android-sdk-linux/platform-tools$
Click to expand...
Click to collapse
I can't quite figure out what to do past this point. I am quite terrified that I bricked the damn thing .
I never really finished rooting it (I think). So I am quite stuck and would absolutely adore some help. I've went around google for many hours searching for even one person who has the same problem, but I never came close. I think I just never really knew how to word the problem correctly.
Thanks for the help in advance.
EDIT:
I would also like to note that I haven't a thing installed on it. I haven't gotten FFF on it or anything in the slightest. This seems like the epitome of fail when it comes to a rooting attempt. I thought it would be a simple process, but let me be the example of how bad things could possibly get messed up xD
Speaking from experience when I first rooted my Kindle, your looking at 3 options.
1) Use a factory cable to connect the device to a computer (A factory cable pins 1 and 4 at the Micro end while a normal cable doesn't use the 4 pin).
2) Pray you can time it right with ADB to change the boot mode back to normal. Seems like the window's pretty small on this though.
3) I assume the issue with working from Windows was drivers? If you can figure out the drivers in Windows so that it shows up as a Android phone under device manager (I had to use a virtual machine to get it there because of issues with previously installed drivers) then Kindle Fire Utility will do the timing for you and install Fire Fire Fire and fix the problem.
So I bricked my FireTV last night during an upgrade to rbox's latest fw...
Short story is, it got to the Amazon app optimization after the flash fine so I went back to the computer to start working on the second box while it did it's thing. I mistakenly sent the reboot recovery command to the box that was optimizing itself. I didn't notice I was sending the command to the wrong box until I saw that my second unit was not rebooting to recovery.
Needless to say, it now no longer boots to any logos, and does not turn on at all (no light when plugged in, not even for a split second).
What are my options to unbrick? I'm taking a guess that the SD reader/eMMC method is the only one. If so, is it possible to retain an unlocked bootloader/etc with this method? I've read you'd lose it, but I'm not familiar.
If someone could point me in the right direction that'd be awesome. I tried google but it's filled with loads of outdated or unrelated information (mostly debricking if the amazon logo appears) or info from when the initial hardware root method came out.
i am in the same boat. if you find anything let me know.
after following the downgrade tutorial, I executed the command as instructed adb reboot recovery
device reboots into recovery,
update starts..... after while reboots...
upon reboot
no light on device no logo on screen - black screen
connecting to win7 machine with USB cable it initially recognizes the box, but cannot connect with either ADB nor FASTBOOT - searching for device
sparkd said:
i am in the same boat. if you find anything let me know.
after following the downgrade tutorial, I executed the command as instructed adb reboot recovery
device reboots into recovery,
update starts..... after while reboots...
upon reboot
no light on device no logo on screen - black screen
connecting to win7 machine with USB cable it initially recognizes the box, but cannot connect with either ADB nor FASTBOOT - searching for device
Click to expand...
Click to collapse
At least you can connect with USB! I get no connection at all to the pc with a A-A cable.
I would suggest for you trying to get the timing right and initiate the fastboot commands right when the device is recognized.
You people need to reflash your partitions, this happened to me months ago. Can't search for the thread now, I think the steps were in the FireTV1 5.0.5.1 thread...
my device bootloader is not unlocked. I was following the steps to downgrade firmware in an attempt to unlock the bootloader.
in Win7 Control Panel > System > Device Manager the FireTV1 appears as QHSUSB_DLOAD - i think I am also going to try this ... http://forum.xda-developers.com/showpost.php?p=66961740&postcount=676
thanks for the advice ldeveraux, ill take a look.
Ordered the eMMC adapter from exploiteers. This is likely the only way I'll be able to fix this as the USB A-A cable is not detecting my FTV
Well I managed to get my device talking with an A-A USB cable while waiting for my eMMC adapter. So now to flash
Is there a way to recover with this method without losing the ability to unlock the bootloader? Bootloader was unlocked prior to the brick.
UPDATE: annnddd it didn't work for me. Was getting I/O errors while writing and now the device no longer gives me partitions in /dev/. The usb device still shows up however.
how did you get the /dev/ partition to appear ?
which linux distro did you download / install as I cannot see any partitions on my device
did you use the linux in a VM ? & did you have the windows drivers installed beforehand ?
thanks
Hi
I installed the German App Sky Ticket, unfortunately the program started.
I read that it is upgraded to root, wanted to make root returning and have
Uninstalled Magisk.
Unfortunately, the wrong way I have been stupid.
The stick is now in the bootlop for 20 minutes and then comes the Amazon login window
But unfortunately, the Firestick no longer recognizes connected devices.
And I can not enter any entry by keyboard or mouse.
Is there any hope or not?
Akki67 said:
Is there any hope or not?
Click to expand...
Click to collapse
Log-in there or wipe data and use the sticks setup...
Thanks @Sus_i Unfortunately, the remote control stops responding and also with
I do not come to a USB keyboard in the column of the username
and password.
So I can not log in.
If I want to be the Firestick 4k with Kamakiri-Mantis-V2.0.1, he does not find the stick, is always just "waiting of device" there and the script does not start.
Akki67 said:
If I want to be the Firestick 4k with Kamakiri-Mantis-V2.0.1, he does not find the stick, is always just "waiting of device" there and the script does not start.
Click to expand...
Click to collapse
You said something that you've uninstalled magisk in the first place, so the stick is already unlocked and you can use/try the boot-recovery.sh script in order to boot into twrp. Run the script then connect the stick via an usb cable. If you reach twrp, wipe data via commandline.
Thank you very much for your answer @Sus_i, the problem is yes if I connect the FIRETV 4K only with the USB data cable, it becomes aware of the Ganicht more perennous, the USB cable is only used as a power source.
Something must have disabled the USB socket, since yes zero commands arrive
And the FIRETV4K is no longer found as a medium.
I suspect that an update is transferred when uninstalling Magisk Amazon
has made the stick unusable.
Before I uninstalled Magisk, these 3 stuff installed on the 4K:
6.2.8.1_r3_4054_patched.zip
Patch - 6.2.
TZ Update - (TWRP) .zip8.1 (No Fota) .zip
Through this stupid action of, I have confirmed the emissions.
Akki67 said:
Thank you very much for your answer @Sus_i, the problem is yes if I connect the FIRETV 4K only with the USB data cable, it becomes aware of the Ganicht more perennous, the USB cable is only used as a power source.
Something must have disabled the USB socket, since yes zero commands arrive
And the FIRETV4K is no longer found as a medium.
I suspect that an update is transferred when uninstalling Magisk Amazon
has made the stick unusable.
Before I uninstalled Magisk, these 3 stuff installed on the 4K:
6.2.8.1_r3_4054_patched.zip
Patch - 6.2.
TZ Update - (TWRP) .zip8.1 (No Fota) .zip
Through this stupid action of, I have confirmed the emissions.
Click to expand...
Click to collapse
How did you uninstall Magisk?
@SweenWolf
Immediately after the start of Magisk was at the bottom of a yellow bar and there was uninstall, there was no error message.
As a result, I have given my Firestick 4k the death shock of great mis
Page out. The USB connection was thereby still laid down as I already
described.
The stick even appears on the network with IP address, but I can not help it.
Akki67 said:
@SweenWolf
Immediately after the start of Magisk was at the bottom of a yellow bar and there was uninstall, there was no error message.
As a result, I have given my Firestick 4k the death shock of great mis
Page out. The USB connection was thereby still laid down as I already
described.
The stick even appears on the network with IP address, but I can not help it.
Click to expand...
Click to collapse
You do not update/uninstall Magisk from Magisk Manager (App), if you do then it will cause the stick to not boot (if there are modifications made on the system).
I am unsure about the state of your system.
I think you should
Open TWRP
clean system, data, cache, Dalvik cache
Install ROM and start fresh.
If you can connect the stick with IP address then you can use SCRCPY to access your stick.
If the device is saying "Unauthorized" and you had installed "Launcher Manager" on it, then you can download "ADB_C.zip" from Launcher Manager page (If you haven't reset the stick)
If your TV supports CEC then you can use your TV to navigate around.
Thanks again to all helping.
@SweenWolf (do you understand German?)
Thank you for the good explanation, unfortunately I come with the tool scrcpy via IP
Not on the box, since ADB is still activated?
I do not come to the TWRP, Ganicht is displayed when booting
thus no newflash possible.
The stick always starts according to the same
Pattern c. 15 min. Always repeats the boot logo, then the screen is white
And then there is automatic login, see picture above.
No entry with the TV remote control possible despite CEC, otherwise that was
where the stick was still in order.
The only option would be about the IP address. There is a possibility ADB via WLAN
to activate at the Firestick 4k?
Slowly, I think the ideas and thank you again.
Akki67 said:
I do not come to the TWRP
Click to expand...
Click to collapse
Get an USB OTG cable, then you get a bootmenu at power on and you can select twrp. Use it together with a mouse/keyboard.
If your stick isn't recognized with the fireISO, you can also try ubuntu together with the boot-recovery.sh script.
If that won't work, you may unbrick with the bootrom-step + fastboot-step. How did you unlock the stick, with or without shorting? Kamakiri 2.0.1 works also without a short.
@Sus_i
When I had rooted him then with Fireiso Image then closed with wire short and the two
Files Bootrom-Step.sh and Fastboot-step.sh executed.
Unfortunately, this does not work if I put the wire on the contact and the USB cable
Pure corner, does not start the scripts and there is only the message there "Waiting for Device"
But no reaction.
As if the USB connection is death
I will now install Ubuntu on my computer and test again
thanks, Take me again
The Fire TV 4K Stick must be clinically death, I tried Ubuntu after 1 hour in the terminal Femster
Waiting for Device I canceled.
If you live in Germany @Sus_i I send you the deaths Firestick 4k and can try
Whether you manage to bring him back to life.
Thank you again for your help and thanks to SweenWolf
Akki67 said:
The Fire TV 4K Stick must be clinically death
Click to expand...
Click to collapse
Trade it in at amazon and get a new one...
Amazon.de: Fire Trade-In: Trade-In
Online-Einkauf von Fire Trade-In mit großartigem Angebot im Trade-In Shop.
www.amazon.de
Thanks for the link But the Fire TV Stick 4K is not listed in the trade in the program.
Will dispose of him or place on Ebay.
Akki67 said:
Thanks for the link But the Fire TV Stick 4K is not listed in the trade in the program.
Click to expand...
Click to collapse
I know this, but if you click at the 2gen stick and trade it in (only stick), probably no one cares... Worst case is they ship it back to you.
Ebay is also ok, I guess someone will pick it up and try the unbrick solution
Akki67 said:
Thanks for the link But the Fire TV Stick 4K is not listed in the trade in the program.
Will dispose of him or place on Ebay.
Click to expand...
Click to collapse
Try lsusb with watch and then attach the stick to your PC, and check if its getting detected or not, you can try changing your USB cable and make sure you the cable has wires for DATA in it.
I do not know german so its getting a bit confusing.
If its taking long time to boot then it can be caused by system services not starting due to some reasons.
If on windows check in Device Manager if its visible in it, and check if plugging/unplugging the stick is causing the console to refresh or not.
@SweenWolf and @Sus_i
I have followed your advice and called the device manager in Win 10. When I connected the FIRETV 4K Stick to the USB cables, this new entry "MT65xxPreloader" under other devices was gone again for 3 seconds.
Can you do something with it, there is something to save?
After 15 minutes this entry appears MTP-USB device, that looks good right?
Which driver or how would I have to proceed?
After 15 minutes this entry appears MTP-USB device, that looks good right?
Which driver or how would I have to proceed?
Have it again with Ubuntu and the KamakiriMantis-V2.0.1.zip on the USB 2 port, but he will find the stick from this error message:
[email protected]:~/Schreibtisch/test/kamakiri-mantis-v1.2/kamakiri$ sudo ./bootrom-step.sh
[sudo] Passwort für akki:
[2022-04-24 23:33:48.695287] Waiting for bootrom
[2022-04-24 23:33:58.244631] Found port = /dev/ttyACM0
[2022-04-24 23:33:58.245259] Handshake
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 501, in read
'device reports readiness to read but returned no data '
serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "main.py", line 119, in <module>
main(dev)
File "main.py", line 24, in main
load_payload(dev)
File "/home/akki/Schreibtisch/test/kamakiri-mantis-v1.2/kamakiri/modules/load_payload.py", line 45, in load_payload
dev.handshake()
File "/home/akki/Schreibtisch/test/kamakiri-mantis-v1.2/kamakiri/modules/common.py", line 97, in handshake
c = self._writeb(b'\xa0')
File "/home/akki/Schreibtisch/test/kamakiri-mantis-v1.2/kamakiri/modules/common.py", line 92, in _writeb
return self.dev.read()
File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 509, in read
raise SerialException('read failed: {}'.format(e))
serial.serialutil.SerialException: read failed: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
Why could it be?
Thanks for your help you since top !!!
Akki67 said:
@SweenWolf and @Sus_i
I have followed your advice and called the device manager in Win 10. When I connected the FIRETV 4K Stick to the USB cables, this new entry "MT65xxPreloader" under other devices was gone again for 3 seconds.
Can you do something with it, there is something to save?
After 15 minutes this entry appears MTP-USB device, that looks good right?
Which driver or how would I have to proceed?
After 15 minutes this entry appears MTP-USB device, that looks good right?
Which driver or how would I have to proceed?
Regards
Click to expand...
Click to collapse
https://developer.samsung.com/sdp/file/17a610e4-ce96-4291-8757-37f2134fb37e
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
15 seconds ADB Installer v1.4.3 ADB, Fastboot and Drivers What is this? This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in...
forum.xda-developers.com
Download these files and install (for Windows)
Reboot the Computer
Open "Terminal" or Command Prompt or PS
And type
Code:
adb devices
or
Code:
./adb devices
if running from PS
There should be a device, most likely unauthorized.
If you see "device" then you can use SCRCPY to control the device using ADB.
If you have used "Launcher Manager" and authorized its key then you can use
https://forum.xda-developers.com/attachments/adb_c-zip.5562577/
Simply extract and run the ADB_C.exe
And then run SCRCPY
After restarting the stick, the Bootsqenz ran for 20 minutes. Then stood down to the right is loaded And the Amazon Authoring Image Schrim came back.
In the device manager is re-available ontort portable devices MTP USB Device
But when I add ADB Devices no devices found, because before the Crash USB debugging
Not yet activated and I had not installed the Launcher Manager yet.
Scrcpy does not find anything.
The only way would be over Ubuntu, but there was this error message, what
Does that really say?
I think,
You have not enabled ADB debugging let alone authorized it.
When you uninstalled magisk it restored stock boot.img which restored the TWRP with stock one, so preloader exploit is gone now, and now because you have stock boot image with some system changes, (it should fail dm-verity) its not allowing system to boot.
You wrote you installed the Patch 6.2.8.1, in yhe post i wrote it requires a patched boot image, install magisk or flash my patched boot image, in this case i assume and am pretty sure you went with magisk only, which on installation caused this, you could have installed my patched boot.img then flash magisk on it.
In short:
Your TWRP is gone.
You cannot use OTG to fix your stick.
You may have cleared the /data and ADB is now turned off. So you will not be able to use ADB also.
If you efuse is intact then you WILL HAVE to follow unlock procedure to apply preloader exploit.