yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 Original Android Development] Clueless&GlutenFree:
Problem, exec: No such file or directory

Hello everyone, am new to the xda forums:) It's a pleasure to meet you. Please bear with me if my first post is messy. Am a newbie and I need some help rooting and unlocking my tablet.

I own a Amazon Fire HD 10 2017 currently running FIRE OS 5.6.2.0 . I believe I was successful using "Rapid Temporary Root". Please bear in mind that I download the "amd64" version of it. Because I got

UID: 0 cap: 3fffffffff selinux: permissive

as the final line I think I was successful temporarily rooting my device. That's not the issue though, afterwards I used k4yoz's script but I can't seem to make it past

sudo ./step-1.sh

Here is my problem:

home@home ~ $ adb devices
List of devices attached
G000N60774340EDW	device

home@home ~ $ sudo cd /home/home/Downloads/amonet/
[sudo] password for home:
sudo: cd: command not found
home@home ~ $ cd /home/home/Downloads/amonet/
home@home ~/Downloads/amonet $ sudo ./step-1.sh
Testing root access...

Trying to use mtk-su to get temp root...
No mtk-su found, you can get it here: https://xdaforums.com/hd8-hd10/orig-development/experimental-software-root-hd-8-hd-10-t3904595
home@home ~/Downloads/amonet $

So I did some lurking and found out that many have recommended here in other posts that I copy the "mtk-su" file from the "amd64 folder" directly into the bin folder of the amonet folder.

I managed to get different results after I did that:

home@home ~/Downloads/amonet $ cd /home/home/Downloads/amonet/
home@home ~/Downloads/amonet $ sudo ./step-1.sh
Testing root access...

Trying to use mtk-su to get temp root...
Pushing root files
1040 KB/s (42832 bytes in 0.040s)
7782 KB/s (1048576 bytes in 0.131s)
8342 KB/s (989184 bytes in 0.115s)
exec: No such file or directory
exec: No such file or directory
exec: No such file or directory
exec: No such file or directory
exec: No such file or directory
exec: No such file or directory
Found an invalid address: 0x0000000000000200
exec: No such file or directory
exec: No such file or directory
exec: No such file or directory
exec: No such file or directory
exec: No such file or directory

It just goes on and on and on repeating the same thing(exec: No such file or directory). I don't know what am missing and I feel I've hit a wall. I've installed and updated all the necessary software and packages to the best of my ability . Could it be a faulty usb cable or perhaps something I did wrong along the way? Any help would be appreciated on the matter.
[Fire HD 8 and HD 10 Original Android Development] LivinOne:
Guys... running sudo ./step-2.sh doesnt do anything for me.

Step-1.sh ran fine (factory reset).

I enabled ADB then ran Temp Root getting... "UID: 0 cap: 3fffffffff selinux: permissive"

Am I supposed to leave the ADB window open, then run step-2.sh ... or close ADB first?

If I leave ADB open I get "No mtk-su found" when running step-2.sh

If I kill ADB then run step-2.sh I get a msg saying "daemon started successfully"; then it just hangs ... Why would step-2 just hang without any action?

thx for the help!
[Fire HD 8 and HD 10 Original Android Development] Thibor69:
What a CLOWN you are. If you can not help dont waste your time or our's.

...[ignore legitsu]... 'CLICK'

.
[Fire HD 8 and HD 10 Original Android Development] stolirocks:
I'm pretty sure you have to open it and short. I did for the previous version from that one.

---------- Post added at 11:30 PM ---------- Previous post was at 11:27 PM ----------

Well I had to open mine and short. Just do that its very easy. Put tape on the speaker wires so they wont come off
[Fire HD 8 and HD 10 Original Android Development] Clueless&GlutenFree:
It looks like the both of us are experiencing the same issue. I ran adb devices first and once I saw that my Fire HD 10 was connected I ran the TempRoot script. It was successful so in a different window I ran the first script ( sudo ./step-1.sh) and it gave me the same error you are getting now. If you go back to previous post in this thread other members discuss having the same problem. The solution is to copy the binary for Temp root (mtk-su) into the bin folder that is inside of the amonet folder. I hope it works for you buddy.

However although this solution has worked for others, it doesn't seem to work for me:eek::D:crying:. It starts pushing the root files to the device and then all of a sudden it says

exec: No such file or directory

Here is the full code of my issue:

home@home ~/Downloads/amonet $ cd /home/home/Downloads/amonet/
home@home ~/Downloads/amonet $ sudo ./step-1.sh
Testing root access...

Trying to use mtk-su to get temp root...
Pushing root files
1040 KB/s (42832 bytes in 0.040s)
7782 KB/s (1048576 bytes in 0.131s)
8342 KB/s (989184 bytes in 0.115s)
exec: No such file or directory
exec: No such file or directory
exec: No such file or directory
exec: No such file or directory
exec: No such file or directory
exec: No such file or directory
Found an invalid address: 0x0000000000000200
exec: No such file or directory
exec: No such file or directory
exec: No such file or directory
exec: No such file or directory
exec: No such file or directory

If anyone reading this is willing to help us then maybe we can solve both of our problems at once.:fingers-crossed::angel:
[Fire HD 8 and HD 10 Original Android Development] Thibor69:
Yes I am sure you are correct. Thank you for your input :) :good:

Cheers

.
[Fire HD 8 and HD 10 Original Android Development] LivinOne:
Got past Step-2, TWRP installed and then I flashed Magisk-v20.1.zip ... BUT got Amazon logo boot loops. I can easily launch recovery / TWRP. I ended up flashing Lin 12.1 and no more boot loop

So questions...

1. Did flashing Magisk in TWRP cause the boot loop?

2. Is there a stock FireOS image I can flash back? I need to have the wired headset.. this is for my kids to use.

thx!

[MENTION=7104332]k4y0z[/MENTION] ... please put this info in the first post to help others on the install process. I solved the below issue by rebooting my FireTab and redoing Temp Root, then ran Step-2 again.

thx for the awesome work guys!

I
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Everything is already explained in OP:
[Fire HD 8 and HD 10 Original Android Development] correct horse:
failed critical init step 4

i cant get passed the first ./step-1.sh command. everytime i try terminal starts looping "failed critical init step 4" ive tried on vmware and actual linux device and still nothing. am i missing something?
[Fire HD 8 and HD 10 Original Android Development] robobub:
I got that message with version 5.6.4.0. As others have indicated, you have to brick and open up the device.
[Fire HD 8 and HD 10 Original Android Development] robobub:
Right now Amazon is actually hosting the last temp-rootable version, 8520. I assume since you were able to get Lineage, you had at most that version and shouldn't be roll-back protected, but I could be wrong.

https://amazon.com/gp/help/customer/display.html?nodeId=G2JXLC4L34GX73TE&sa-no-redirect=1
[Fire HD 8 and HD 10 Original Android Development] michi1051:
My Fire HD 10 don't like me.

Installed Version is 9820, but i think it don't take the brick.

Reboot with:

"adb reboot bootloader"

Flash brick

"bin/fastboot flash brick ./bin/brick-9820.img"

target reported max download size of 114294784 bytes

Sending 'brick' (111616 KB)...

OKAY [ 7.816s]

Writing 'brick'...

FAILED (status read failed (No such device))

Finished. Total time: 38.933s

->fire does a reboot

"bin/fastboot flash brick ./bin/brick.img"

target reported max download size of 114294784 bytes

Sending 'brick' (112090 KB)...

FAILED (data write failure (Cannot send after transport endpoint shutdown))

Finished. Total time: 9.954s

-> shutdown

any ideas?

solution is from here

https://xdaforums.com/hd8-hd10/orig-development/unlock-fire-hd-8-2017-douglas-t3962846/post81166313#post81166313
[Fire HD 8 and HD 10 Original Android Development] Sus_i:
Why you wan't flash a brick script for the fire HD8? Isn't the HD10 a different device? ;)

Take a look here (unlock HD10 on 9820 is possible, ofcourse without opening).
[Fire HD 8 and HD 10 Original Android Development] michi1051:
ohh, ok. thank you.

i have started at https://xdaforums.com/hd8-hd10/orig-development/unlock-fire-hd-10-2017-suez-t3913639

but my os is to high.

I understud from

that i have to brick my device, but i can't find an totorial.

At the end after klicking 10-15 further links of your link i ended at my page.

Have you any instructions for bricking my hd10 2017 with 9820 ?

Regards Michael
[Fire HD 8 and HD 10 Original Android Development] Sus_i:
No. You don't need brick the tablet yourself, since the only way to unbrick is post 2 from OP (with opening). ;)

OK. I'll try to explain the steps a bit...

Ok, you say your OS is to high, that means that mtk.su is patched. You have to root your tablet as a first step, with one of the few older methods or oneclicktools.

Goal is to achieve propper root su access, in order to follow the OP.

This explains the process, if the OS is to high. I'll try to explain that with the next step.

This needs to be done before you run the scripts.

At this point you can run the first step.

You see, the first script from op called 'step-1.sh' needs root to run.

It checks your OS and if it finds unexploitable PL/LK/TZ versions, it wants to downgrade this to a somewhat older version.

Also the script prepares the preloader for the second step called 'bootrom-step-minimal, i.e. the first script deletes a few blocks from the preloader (this is your brick), in order to get into bootrom without opening the tablet.

You have to confim this with YES... before the script does all that for you.

That means that if the first script is done, disconnect the device, start the bootrom-step-minimal.sh. This step flashs a new preloader (over the bricked one) and completes the unlock.

Connect the device and if the script finds the bootrom, press enter.

If the script waits forever, press/hold the power button until the script finds the bootrom.

Thats the last step... the device always boot into hacked fastboot, until this step is finshed.

Remember always the OP initial words:

PS: This isn't a guide, only some additional hints to explain the steps from OP a bit for you.
[Fire HD 8 and HD 10 Original Android Development] Nosepull:
Thanks for the explanation. Maybe I'm completely missing something, however, as I cannot understand this opening remark.

I read the instructions, and your additional remarks, as if I can unlock even current fw revisions if I only use another initial root variant - without having to open the device. This includes bricking and unbricking with scripts.

But why do you start off with the remark that the tablet has to be opened to unbrick? In your additional informations I don't see that necessity.

Maybe a stupid question, but I fail to find a clear statement for this essential part of the process, sorry.
[Fire HD 8 and HD 10 Original Android Development] Sus_i:
Hi. I'm sure k4y0z could explain it better, but I'll try it...

If you follow the OP, i.e. run the step-1.sh + type YES, the applied brick gets repaired with the next script bootrom-step-minimal.sh.

You may see this as a exception from the always working unbrick solution explained in post 2.

I said this in my last post, because michi1051 tried to brick the HD10 with scripts for the HD8 and I think this isn't supposed at all.

In other words, if you start with a somehow bricked tablet, virtually any other brick than thru step-1, there is no way to run step-1, as step-1 needs a fully functional working rooted tablet.

Is this the case, the only working unbrick solution is explained in post 2.
[Fire HD 8 and HD 10 Original Android Development] Rortiz2:
The user bricked the tablet when restored his backup. He could unbrick the tablet if he could enter the hacked fastboot mode but when he tries to enter the hacked fastboot mode, he starts the amazon fastboot mode and can not execute commands. I think @ k4y0z would have to configure that to access the hacked fastboot mode you have to turn on the tablet with volume - and power and remove the amazon fastboot mode. But I do not know if it can be done.

Enviado desde mi Mi A2 mediante Tapatalk
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
If TWRP doesn't work you could use my modified handshake2.py to get into "hacked fastboot", this will only work as long as the boot-exploit is still working though.

But I'd think it's rare, that your TWRP is not working, but the boot-exploit still is. (Still worth a shot, should you get yourself in that situation)

On the HD8 this feature will not work, as it's not implemented in the HD8-amonet.

In [MENTION=8165603]DragonFire1024[/MENTION]s case this will not work either, since he doesn't even get the amazon logo.

EDIT:
[MENTION=8978978]Rortiz2[/MENTION] Using the fastboot button-combination to access hacked fastboot cannot be done, since at that point the exploit isn't even executed.
[Fire HD 8 and HD 10 Original Android Development] Wall.swe:
I downloaded 5.6.0.3 for the Fired HD10 7th generation from here, https://www.amazon.com/gp/help/customer/display.html?nodeId=202194760 but what is up with the weird file name? update-kindle-40.6.2.6_user_626533320 is this the correct file?

I pushed the file to the tablet and changed the file ending to a .zip.

Do I now use the install button in TWRP and install the image or do I need to do something else before, like activating something in the settings of TWRP or am I good to go?

I'm very thankful for all the help!
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
Give me a few. I actually did a mashup script from the fire 7 Nexus rom then used a tool to do the leg work. Then I had to work out the rest of the formatting myself based off research and various other scripts. So far as I know, I made sure nothing was touching anything related to the LK or boot. The only thing that might get me is the step for /system in recovery or flashing SuperSU within the system, like [MENTION=5749760]ggow[/MENTION] rom, somehow spread beyond those partitions. This is very likely user error. I just got home. So I'll upload a copy of the last zip, but I don't know if I still have any left.

---------- Post added at 05:48 PM ---------- Previous post was at 05:45 PM ----------

Well if we had a full source for that tablet....I still think mtboot.exe is a Honeypot. Now that we are unlocked, we should try and build this kernel for real (HD 10).

---------- Post added at 05:53 PM ---------- Previous post was at 05:48 PM ----------

If returning to total stock, installing it will put you back to fresh FireOS. If you just want a system update, edit the updater script and delete all the lines that flash anything besides the system partition. Also remove the line that unpacks the boot.img. you can then delete the folder that says images, and delete the boot.img file as well, then flash. You have to use 7zip or the likes to edit. Right click the zip and open as archive. Or pull the script edit it and replace it the same way; right click zip drop and drag script to folder. Just don't create a new zip.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Yes, that is the correct one.

You may have to uncheck "mount system read-only" under "mount".

Then just use install in TWRP.

That isn't necessary when you use this TWRP, as it will prevent the update-bin from overwriting lk/preloader/tz.
[Fire HD 8 and HD 10 Original Android Development] Wall.swe:
Thank you so much for clarifying, I will try it in a bit.

Will I loose TWRP?
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
No.
[Fire HD 8 and HD 10 Original Android Development] Wall.swe:
Thank you very much it worked, and my tablet is now updated to 5.3.6.4.

So how do I continue? Should I follow the guide again or do I only need to root using the mtk-su file? My bootloader is already unlocked right?
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Just install Magisk from TWRP...
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
Ok so when I got home I went and grabbed the tablet. It was definitely on as the heat shield was quite warm. I didn't look in a dark enough spot to see if the screen was just black or not on at all. That's as far as I've gotten for the moment. Sorry I've had a very busy couple days.
[Fire HD 8 and HD 10 Original Android Development] bibikalka:
[MENTION=8978978]Rortiz2[/MENTION] - you are very right! I am actually wondering what the heck were those users trying to restore in TWRP ... It feels that it was a backup from some other device, not a Fire, since they had little chance to have a proper backup of Fire so soon, so no wonder there is bricking going on! There must have been a bunch of other partitions in those "backups", at least, /recovery for sure. How can we warn noobs not to try to get too fancy too quickly ? :confused:

[MENTION=8165603]DragonFire1024[/MENTION] - /boot & /system go hand in hand. There are pretty serious misconceptions in what you wrote above. I urge you to refrain for now from trying to flash ROMs into your Fires - you may be creating bricks faster than you can acquire new devices from Amazon! Aim to get a proper understanding of how things are supposed to be first if you want to make real progress.

[MENTION=7104332]k4y0z[/MENTION] - Man, we do need to get you an HD8 device !!! :D There is definitely plenty of room for improvement in the earlier work by xyz`, so a bit of contemporary clean up will be very beneficial. Everybody with an HD8, feel free to pitch in over here - link. It's a good cause!
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
So I keep getting this error when I try to run the script to unbrick. I have seen similar posts, but none that reference the HD 10. Modemmanager has been long uninstalled. All packages are installed.

Edit...This comes up in Ubuntu when I run lsusb

Bus 006 Device 008: ID 0e8d:0003 MediaTek Inc. MT6227 phone

dragon@dragonfire:~/unbrick_suez$ sudo ./bootrom.sh
[2019-03-24 16:24:25.684675] Waiting for bootrom
[2019-03-24 16:24:53.058376] Found port = /dev/ttyACM0
[2019-03-24 16:24:53.061324] Handshake
[2019-03-24 16:24:53.068550] Disable watchdog

* * * Remove the short and press Enter * * *

[2019-03-24 16:24:58.206359] Init crypto engine
[2019-03-24 16:24:58.533604] Disable caches
[2019-03-24 16:24:58.537458] Disable bootrom range checks
[2019-03-24 16:24:58.726588] Load payload from ../brom-payload/build/payload.bin = 0x45D0 bytes
[2019-03-24 16:24:58.730983] Send payload
[2019-03-24 16:25:07.671589] Let's rock
[2019-03-24 16:25:07.679454] Wait for the payload to come online...
Traceback (most recent call last):
File "main.py", line 92, in <module>
main()
File "main.py", line 57, in main
load_payload(dev, "../brom-payload/build/payload.bin")
File "/home/dragon/unbrick_suez/modules/load_payload.py", line 143, in load_payload
dev.wait_payload()
File "/home/dragon/unbrick_suez/modules/common.py", line 171, in wait_payload
raise RuntimeError("received {} instead of expected pattern".format(data))
RuntimeError: received b'' instead of expected pattern
dragon@dragonfire:~/unbrick_suez$
[Fire HD 8 and HD 10 Original Android Development] Rortiz2:
Dragonfire read please:

https://xdaforums.com/showpost.php?p=79097575&postcount=10
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Just to make sure, you're running the script from this thread (amonet-suez-v1.0.zip), not from retyres thread, yes?

From the folder in your log it looks like your running [MENTION=3497316]retyre[/MENTION]s unbrick-script.

Also you are running bootrom.sh there is only bootrom-step.sh in amonet-suez-v1.0.zip
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
I have updated Post #2 with unbricking instructions.
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
I've tried every USB port I have. I only have 1 set of 3.0, maybe 2 sets. But I did try nearly every port. I may have missed one but I'll try them again.

---------- Post added at 01:01 AM ---------- Previous post was at 01:01 AM ----------

Yes the other unbricking procedure. I wasn't aware I could use the procedure here.

---------- Post added at 01:04 AM ---------- Previous post was at 01:01 AM ----------

Will try tomorrow
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
I told you here.
[Fire HD 8 and HD 10 Original Android Development] GuyInDogSuit:
So.... are the people that are bricking, were they just trying to restore backups? Backups of what, userdata? So I'm guessing we should avoid restoring that, then, and just start fresh regardless?
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
I've no idea what caused my brick. It just happened. I know better than to try and restore data. Anything I need in regards to that type of data, is all cloud based. The only thing that would kill me is losing the valuable work and software on my windows, turned Linux machine.
[Fire HD 8 and HD 10 Original Android Development] DB126:
Yes - aside from individual (personal) files and folders. Restoring partitions via TWRP or other means is just asking for trouble.
[Fire HD 8 and HD 10 Original Android Development] Nosepull:
Ok, thanks a lot for the explanation.
[Fire HD 8 and HD 10 Original Android Development] michi1051:
ok, now i think i got it. I thought this is included.

could you please give me a link to the old method, or a name of a oneclicktool?

I've spend another 2 hourse of my live, after switching to my windos 10 pc, to kingoroot, it crashes at 3% or 7% with messages like no connection to server...

One Click Root should cost 40$

other tools are only vor samsung....

sorry for my stupid questions.

regards Michael
[Fire HD 8 and HD 10 Original Android Development] Sus_i:
Take a look here
[Fire HD 8 and HD 10 Original Android Development] Thibor69:
I would be interested if you got that to work ... I tried that method with kingroot and allthough it did not hurt anything, it also did NOT give me root :(

@Sus_i - I am confused now also ... you say that we do NOT need to brick our device ? But the OP clearly says that if you are on 5.6.4.0 or higher you must open it and short it.

I am sorry if I dont understand ... I am running a higher version so dont I need to open my device and short it ( brick it ) ? :confused:

One other thing ... I also was under the assumption that this proccess from the OP will gain us root, but I think now you are saying that we need root befor we start the proccess from OP ?

Again I am not trying to be a pain ... I only am trying to clear this up first because if I screw it up, I do not have money to buy another one.... this one was a gift from my wife.

Thank you for all your time and help.