Updating Kindle Fire HDX 7 Android 4.4.4 to Android 6+ - Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot

Hello, I have a rooted Kindle with Safestrap 4.01 (TWRP v2.7.1.0) and Android 4.4.4 (KitKat). I did that some time ago.
Now I want to update Android 4.4.4 to Android 6 or higher to run some apps on it.
I tried it with Lineage 14.1 Thor.
I wiped the device in Safestrap, installed the new firmware lineage-14.1-20200705-UNOFFICIAL-thor.zip, wiped Dalvik after it was done flashing and rebooted.
I also tried it with other Lineage versions but after rebooting it's only showing a black screen for 20+ minutes (the only one that seemed to work was Lineage 11 but it didn't update my Android version).
Am I doing something wrong? Maybe I go about it totally wrong but all tutorials tell me that's the way to go.
EDIT:
I almost bricked my system twice and I think I found the culprit. It might be Safestraps fault.
Now I'm trying to get a twrp recovery mode update but the fastboot mode doesn't let me use .img files
(doesn't recognize any devices and I already manually updated my Android ADB Interface driver a few dozen times but it still won't work - still a question mark above the device).
Is there a twrp zip file which I can use to install from Safestrap?

Related

flashing TWRP 2.8.7.0 on android M

well i updated my nexus 9 through OTA update to android 6.0 couple days ago, then i had some battery issue.
So then i tried to flash cm12.1
what i did was, i unlock my device flash TWRP 2.8.7.0, then i got this corrupted message upon rebooting my device.
i did some research(i should've done it before doing anything:silly, it seems like it's something about the force encryption?
i tried almost every guide on xda here, flash de-crypted boot, flash stock recover, flash stock rom, adb sideload function is not working, nothing seems to work?
it seems like nothing can write onto my device as long as it's encrypted?
it works fine now, just wondering if there's a way i can properly de-crypt my device in this state and go back to 5.1.1 or CM12.1
Thanks
TWRP has just been update to 2871 and can now read encrypted partitions. Install this new TWRP.
Sent from my Nexus 9

One plus X - Working CM13-2016/10/15 - TWRP 2.8.7.0 Stuck - Recovery not working

Hello!
This is my first post. I've searched for hours. Visited over 200 sites and forums tried multiple things installed all available android tools you can find online and i am seriously stuck.
Setup before problem : One Plus X - Cm13 - Version 2016 - Oct - 10. This is updated from the cyanogen website and its treated as the stable version.
Downloaded the latest version which is the 15th and got stuck at bootloop. After some searching i discovered that i had to updated my bootloader as it was the same since November 2015. In the website that i got the new version i was also given the new TWRP version 3.0.2 . So i went into my recovery flashed the new bootloader , then the TWRP , then the new ROM. Mobile boots up shows completly empty fresh install CM 13 without gapps or any of my previously installed programs. Everything is still in the storage. All installation folders from the various programms i had.
My recovery mode refuses to Boot. It just stays on the one plus logo. Tried TWRP manager from the OS but the old version 2.8.7.0 refuses to be unistalled. Adb command lines : I've been trying on windows 10 , 8 , 7 with the appropriate drivers and the only thing that i can make the phone do is go to either FASTBOOT or normal boot. Flashed the TWRP multiple times and no changes what so ever. I can make the mobile show up with ADB device, Fastboot device it shows success and when i try to boot into recovery it just gets stuck. I also got the MTP package from Windows. Basically i bricked my phone within a glass. OS works but Recovery not. Fastboot is supposignly working but i see no changes.
Thank you in advance!
Install original stock recovery then 2.2.3. If you want to use ashwins cm13,cm14 from here on out and a couple other ROMs required updated bootloader. You achieve this by flashing 3.1.3 Oxygen OS. After you updated your bootloader only twrp you can use is blusparks latest v41 or Nichets twrp. On a side note 2.8.7 twrp is old 3.0.2 is latest.
Exodusche said:
Install original stock recovery then 2.2.3. If you want to use ashwins cm13,cm14 from here on out and a couple other ROMs required updated bootloader. You achieve this by flashing 3.1.3 Oxygen OS. After you updated your bootloader only twrp you can use is blusparks latest v41 or Nichets twrp. On a side note 2.8.7 twrp is old 3.0.2 is latest.
Click to expand...
Click to collapse
Thank you i managed yesterday from a program to flash twrp as kernel and was rebooted into a working twrp and fixed everything from there.

Bricked hdx 8.9 by thor twrp

My fire hdx 8.9 is unlocked and was installed with cm 13 rom. I wanted to flash the same cm 13 again, so I wiped data. After that, ALL roms I tried to install was ERROR 7.
I heard that this is due to an error recovery, so I tried to install a new one by ADB. However, I installed a wrong thor one, and now I can't use the touch screen even if I install an Apollo one.
To make matter worse, it is also ERROR 7 whatever I try to install. So what should I do? THX a million!
Neko_nyan said:
My fire hdx 8.9 is unlocked and was installed with cm 13 rom. I wanted to flash the same cm 13 again, so I wiped data. After that, ALL roms I tried to install was ERROR 7.
I heard that this is due to an error recovery, so I tried to install a new one by ADB. However, I installed a wrong thor one, and now I can't use the touch screen even if I install an Apollo one.
To make matter worse, it is also ERROR 7 whatever I try to install. So what should I do? THX a million!
Click to expand...
Click to collapse
- place device in fastboot mode via <power>+<vol-down>
- connect cable; look for ready prompt on device (if not check drivers)
- grab TWRP build 3.0.0-1 from this thread (that build - NOT the latest)
- use fastboot command in OP of above thread to install TWRP

Moto G5s Plus Hard Brick

Hi guys, I have a Motorola G5s Plus XT1802.
I was with a battery problem, the cell phone did not load, so I made a flash for twrp sanders for a version 8.1 Lineage Os, and then I came across a version SacredOs 9.0 Pie, I installed it, but I was having a lot of problems, and I decided to go back for version 8.1 oreo, but I cleaned the cache, dalvik, date, and the internal storage, and made the adb of twrp, and now all the roms that I try to install of error 7, being that before it did not, I tried several versions of twrp, all compatible with the roms, I tried to make a flash of the original image and also did not work, of the following error: Image is too large
the cell phone is totally bricked now, does anyone recommend something to me?
Thank ALL
Erase everything with the help of the twrp and flash the original image of the stock Android 8.1 through adb and the twrp is better boot the image.
If it does not work do it several times because there is a corruption with the security patches.
After that you can install other roms.

MI A3 unable to install custom rom

Hi,
I know I must be doing something dumb, but I am unable to install any rom on my MI A3. I unlocked my bootloader and installed TWRP. I tried installing the havoc os rom on my phone and it wouldn't boot after that (kept going straight into fastboot). So I went back to TWRP and wiped my internal storage and tried installing it again but the same problem kept happening. Now I cannot install any rom ( I have tried Lineage OS and crDroid). I performed the following steps to install a rom:
1. Copy the zip file to internal storage from my laptop
2. Clicked on install
3. Chose the file I just transferred
4. Did the swipe to confirm flash thing
5. It does the flash process without any errors, but then says do you really want to reboot, there is no OS installed.
Even if I try to reboot, it goes straight to fastboot. Checking my internal storage through TWRP, I can see that my system folder is empty.
EDIT: I realised that I need to flash it twice because of the A/B partition thing. I tried doing that too. Now, TWRP no longer says that there is no OS installed and I can see that there are some files in system/. However, I still cannot boot into the OS. It goes straight to fastboot.
EDIT AGAIN: I am able to boot after flashing the stock fastboot rom. So at least I can use my phone for now. However, I would still like to use Havoc OS. Any help is appreciated.
I tried a couple more ROMs. Pixel experience also gets stuck at fastboot and Lineage OS gets stuck in a boot loop
pranav-dahiya said:
Hi,
I know I must be doing something dumb, but I am unable to install any rom on my MI A3. I unlocked my bootloader and installed TWRP. I tried installing the havoc os rom on my phone and it wouldn't boot after that (kept going straight into fastboot). So I went back to TWRP and wiped my internal storage and tried installing it again but the same problem kept happening. Now I cannot install any rom ( I have tried Lineage OS and crDroid). I performed the following steps to install a rom:
1. Copy the zip file to internal storage from my laptop
2. Clicked on install
3. Chose the file I just transferred
4. Did the swipe to confirm flash thing
5. It does the flash process without any errors, but then says do you really want to reboot, there is no OS installed.
Even if I try to reboot, it goes straight to fastboot. Checking my internal storage through TWRP, I can see that my system folder is empty.
EDIT: I realised that I need to flash it twice because of the A/B partition thing. I tried doing that too. Now, TWRP no longer says that there is no OS installed and I can see that there are some files in system/. However, I still cannot boot into the OS. It goes straight to fastboot.
EDIT AGAIN: I am able to boot after flashing the stock fastboot rom. So at least I can use my phone for now. However, I would still like to use Havoc OS. Any help is appreciated.
Click to expand...
Click to collapse
My problem is that I can't install havoc os. I tried all the methods....
Same for me, first time I installed Pixel Experience like you did and worked well, then I tried again and I can't install no more custom ROMs, always getting error 1 in recovery, or not installing TWRP at all. I was able to boot phone again by fastbooting Stock Android 10 v11.0.11.0 April.
But I really enjoyed PE and I wanted to install it.

Categories

Resources