Error 1 Installing Zip File Twrp

0 views

Skip to first unread message

Edward

unread,

Aug 3, 2024, 4:46:57 PM8/3/24

to inerfaide

TWRP custom recovery allows rooted Fire TV owners to install custom ROMs and images, as well as allowing them to restore their device to working condition in case the operating system no longer boots up correctly. It is highly recommended for all rooted Fire TVs to have a custom recovery installed. This guide will show 1st-gen Fire TV owners who have ClockworkMod installed how to install TWRP and upgrade to Fire OS 5 without losing root. This guide also shows 1st-gen Fire TV owners on Fire OS 5, that rooted with KingRoot, how to install TWRP.

The Fire TV has to first be rooted. The guide above is not a guide for rooting. It is to install a custom recovery which helps you fix issues on a rooted device and allows you to update the OS without losing root.

Hey guys, I followed this guide on my AFTV1 rooted with Kingroot and everything seemed to work out fine.However after installing the latest preerooted Rom I did a factory reset to delete all the Kingroot stuff.

I installed twrp and 5.0.5.1 on my firetv which had 5.0.3 0n it,after installing new rom and wipping twice , I still had leftovers fromkingroot and when I installed kodi and ran it , it started as if it was starting for first time but when fully loaded it had the exact same build on it as I had before wiping ?

I will eventually get around to updating to the latest prerooted FireOS5 rom, but I am currently on the July 19,2015 Pre-Rooted 51.1.6.1 ROM. So I just want to confirm that I have to first update to 51.1.6.3 Rom before preceeding with the new guide on installing TWRP and latest prerooted rom.

I had the bootloop, i had to flash back to cwm, wiped / cleared everything ( system and all ) but not my /sdcard/ and then flashed latest 3.0.3 rom back, after it was done ( without rebooting ) I just adb back in ( still in cwm ) and wrote twrp recovery. After reboot back into recovery, twrp finally booted fine and i was able to install v5 of fire prerooted without any issues. There was obviously something left on some of our fire tvs that needs to be wiped or cleared before twrp works for us. I too had bootloop at start with twrp and tried 3 different monitors, all with different results but mainly team win would show up for fraction of second then go away.

Again, i fixed it by flahing back to cwm, clearing everything but /sdcard/ as it contained my zips but im sure you can clear it all if you want, the within the same session adb in and flash twrp recovery, reboot and twrp should work now. Wonder what old file/s are the culprit?

I am in the same boat. Stuck on TWRP boot screen.How do you go back to CWM? Can you provide the steps or link to the guide of what you did to fix this?Was able to press Ctrl+Alt+Delete on my keyboard to reboot and launch the kernel.

There is workaround for this though that is pretty simple. Last I was reading from the dev, he was at a loss on what was causing this, so it maybe sometime before a twrp is released to fix it (or the quickfix) but since you can fix it pretty easy, why not do that?

Got it! I installed 5.0.5.1 ROM with TWRP but after perform factory reset -advanced wipe my root was gone. I reinstalled pre-rooted ROM again now it has root. Thanks for the guide Elias and thanks for your hardwork RBox!

Not sure if this applies to you, but I was getting permission denied errors when running ABD either straight from a command line or opening a shell in abdFire2.03. Out of desperation I opened a shell from adbFire 2.00 and it worked like a charm. Go figure.

Any experienced an issue with TWRP whereby everything works fine but after a set period of time (I believe of inactivity) the aftv boots into twrp. I am finding that if i dont use the aftv during the day or over night, go to use it in the evening/morning and its in the twrp menu as opposed to kodi/aftv homescreen.

Hi,my firetv 1st gen is now rooted at 5.0.5. I have confirmed with busybox that my bueller-5.2.1.1-rooted_r1.zip is intact and md5 checksum is matching . However, after I su in Adb shell and ran the command I am getting these errors. Here is the results

I flashed TWRP on 5.0.5. I went fine then I used it to install the latest prerooted FireOS I noticed when it booted the screen to boot into twrp is no longer there and its stuck on the second amazon screen and wont boot. I tried the ALT+I+SCREEN PRINT and it does absolutely nothing. Any idea on anything else I can try?

There are a few different ways to install Magisk. If you're already rooted and you just want access to Magisk modules, you can use Magisk Manager to install the Magisk framework. Or, if you want to pass SafetyNet on a rooted device, you can switch from SuperSU to Magisk SU. But the best way to do it is to start fresh by installing Magisk on a non-rooted phone using TWRP.

The main reason we prefer this method is because it's the cleanest. No need to remove old root binaries, just flash the Magisk ZIP and you'll be good to go. In doing so, you'll actually root your phone and install Magisk in one shot, plus you're far more likely to pass SafetyNet's CTS Profile check this way.

This method works by flashing the Magisk ZIP in TWRP, so you'll need to install the custom recovery before you begin. Much like Magisk itself, there are multiple ways to install TWRP. If you're rooted, you can use this method, but note that you'll have to do a full unroot in SuperSU after you're done.

If your phone does not have a Fastboot interface, the instructions for installing TWRP will vary. We've covered many of these methods in separate tutorials that are linked out in the following guide, so this is a perfect place to start:

Once you've got TWRP installed successfully, boot into Android and install the Magisk Manager app. This isn't the Magisk framework, which provides root access and the ability to install Magisk modules. It's simply an app for downloading and updating the Magisk framework and managing modules.

The Magisk Manager app is no longer available on the Play Store, so you'll need to have "Unknown Sources" enabled to install it. Other than that, just head to the following link, which will show you all available versions of the Magisk Manager app. Download the newest version, then when that's finished, tap the Download complete notification to launch the APK. Finally, press "Install" when prompted.

Next, open the Magisk Manager app. You'll get a popup asking if you'd like to install the Magisk framework. Tap "Install" here, then hit "Download Zip Only" on the subsequent popup. Wait until you see a message at the bottom of the app's main menu stating that the file has been downloaded.

Next, boot your phone into recovery mode, then tap the "Install" button in TWRP's main menu. From there, navigate to your device's Download folder, then select the Magisk ZIP. After that, just swipe the slider at the bottom of the screen to install Magisk, then tap "Reboot System."

Next, go ahead and open the Magisk Manager app. If everything went off without a hitch, you'll see a message towards the top of the screen that says "MAGISKSU (topjohnwu)" with a green check mark next to it. This means your phone is now officially rooted, and since it was done with Magisk, it's a systemless root.

Aside from that, the main advantage of Magisk is that you can have root without tripping SafetyNet. To verify that your phone still passes Google's SafetyNet check, press the corresponding button towards the top of the screen. If you see two extra green check marks after this test is run, you're all set to go!

When I unroot with supersu, I am unable to then boot into twrp (just get the andoid bot with red triangle). Probably because it needs root to boot. I'm stuck......Was able to flash Supersu and twrp from adb and get root back. If you unroot though now, how to you get to twrp recovery?

I'm guessing after I flash TWRP with adb I need to boot to TWRP right away (and flash Magisk) where in this instruction it said to reboot phone. It did not work when I went to boot to TWRP to flash magisk, it did not boot to recovery (darn bot with red triangle). We'll see.

This sounds like you're having problems with permanently installing TWRP. Some new devices require you to temporarily boot off of a TWRP image file (IMG), then use the booted TWRP to permanently flash a separate TWRP ZIP file. You can see if that's required by looking at the install instructions for your device on its TWRP download page (at twrp.me). After doing that, make sure to swipe the slider to allow modifications (make TWRP your permanent recovery... otherwise the stock recovery with the red triangle will take back over after a reboot).

How can this method be used to root the Honor View 10. There was no mention above of having to unlock the Bootloader first?? (surely a prerequisite of any root) And mine is locked, with Huawei not providing codes anymore.. Any ideas please? Tnx

It doesn't look like there's a TWRP release for that model. So you'd have to get a copy of your stock boot image, then patch it in the Magisk Manager app. Then you could flash it in Download Mode with Odin. But definitely look into it some more, that's just the super short version.