If you followed instructions in this thread and device was previously stable I doubt the unlock was done incorrectly or is influencing the symlink errors. Likely FireOS is being a bird of a different feather (again) along with a possible permissions issue as you surmised.
I finally was able to flash the stock rom if downloaded directly to the tablet. I was using mtp to transfer the zip file from my pc and for some reason these zip files from the stock roms were more sensitive than the one from other roms.
These are old images that are no longer maintained. You'd be better off going with a custom ROM and using Underground to get Amazon specific content.I keep getting Unknown_Error and License_Error. Any idea how to fix? I read someone said something about trying Amazon Underground but doesn't show as compatible with my Fire HDX. I installed this ROM to a Thor LTE model with unlocked bootloader and TWRP.
I had same issue when moving back from LineageOS 14.1 to stock rom 4.5.5.2 and I think it's not related to mtp transfer. Update always stopped with that symlink error no matter if image was transferred with mtp or downloaded from web. I found out that flashing CM12 first and then without booting the device flashing the modified TWRP compatible stock rom, the update process goes thru successfully. Then I wiped all other partitions except System (& External partition). After booting the FireOS for the first time you might need to skip the Kindle Fire registration, otherwise it might end up into endless loop that keeps asking for language settings for device all and all over again. If that happens you can wipe all partitions except System again with TWRP and boot -> set language -> skip Kindle Fire registration -> you have working device again. You can register your device afterwards without any problems.
My TWRP version is 3.0.3-1
The repackaged zips in the OP if this thread are the latest available that have been tested in the wild. You can also try a different build here (link toward bottom of post) but I would expect a similar result. I don't know if FireOS v4 supported full HD streaming from the integrated Amazon app. We're going back 2-3 years when HD streams was still the norm for mobile devices.Hi,
quick Question, where did you get the stock ROM from?
I tried 2 version available here but both do not play prime video in full HD only in HD.
Something seems to be broken as downloading and playing in full HD works.
It's not a 100% dealbreaker but as the display is still stellar it would be a pitty.![]()
The procedure/tools to create a flashable "real" stock 4.5.5.2 ROM are discussed in post #77 of this thread. That said, I'm not sure this will solve your problem as untouched HDX devices running stock FireOS seem to possess some unique capabilities relative to video playback. I'm sure the mystery is solvable for someone willing to invest the time/effort to peal back the onion.With real stock 4.5.5.2 the videos were played in full HD!
Did someone tried to upHDX a 4.5.5.2 ROM?
Or is there a way to use TWRP to flash real stock ROM?
Saw some thraeds that it dowes not work right away as the device is now a cm_thor and not a thor... -)
As Kingroot works now gapps should be no issue.
Original poster is no longer active in this thread. Which build are you looking for (Apollo or Thor)?Can not download form MEGA , can please mirror it to Android file host ? Many thanks
Original poster is no longer active in this thread. Which build are you looking for (Apollo or Thor)?
Tanks for your rely.
I bought a used Thor and it comes with CM rom, so I have't tried stock fire os and just want aTWRP flashable stock fire os for Thor
how to register device? I can not finish it. The serial number is 0000, and amazon can not help me.I had same issue when moving back from LineageOS 14.1 to stock rom 4.5.5.2 and I think it's not related to mtp transfer. Update always stopped with that symlink error no matter if image was transferred with mtp or downloaded from web. I found out that flashing CM12 first and then without booting the device flashing the modified TWRP compatible stock rom, the update process goes thru successfully. Then I wiped all other partitions except System (& External partition). After booting the FireOS for the first time you might need to skip the Kindle Fire registration, otherwise it might end up into endless loop that keeps asking for language settings for device all and all over again. If that happens you can wipe all partitions except System again with TWRP and boot -> set language -> skip Kindle Fire registration -> you have working device again. You can register your device afterwards without any problems.
My TWRP version is 3.0.3-1
Answered here: https://forum.xda-developers.com/ki...8-rollback-ota-captured-t3046204/post73810224how to register device? I can not finish it. The serial number is 0000, and amazon can not help me.
Unlikely anyone has repackaged 4.5.5.3. Best fallbacks are flashable FireOS 4.5.2 or Fire Nexus KTU84Q (preferred). You can also backup your current FireOS install from TWRP.Someone has will plan upload last 4.5.5.3 Repacked ROM? Just in case if custom rom's doesnt work fine for my daily driver, with fireOS4 i almost covered all the missing things, versus a stock rom, but always fun try custom roms.
Tanks for your rely.
I bought a used Thor and it comes with CM rom, so I have't tried stock fire os and just want aTWRP flashable stock fire os for Thor
Same I was just curious. I was on v4 and loving it but google services updated and started crashing continually so im on slim and besides Bluetooth issues its great. Thanks for reply
Sent from my Kindle Fire HDX using XDA Premium 4 mobile app
Just FYI @Davey126 flashing TWRP from fastboot is the easiest task that can be done with working fastboot (plus in case of HDX with unlocked bootloader, which is necessary). I did flash TWRP several times via fastboot just to confirm to me that I have unlocked bootloader...
Code:fastboot flash recovery recovery_image_name.img
Obviously there is a lot of space for user error (faulty usb cable, corrupt download, drunk dude trying to do something he seen, hear, watched somewhere, etc.), and that is what is really dangerous here... irresponsible peoples trying to do something they do not understand (at least partially)...
Sorry, I often include screenshots to prove my assertions, but right now I am not in the mood to fight again with fastboot drivers for windows, which are probably live their own life thinking "G**O user, we are not going to flash ANYTHING today!"![]()
Great! Glad it worked.Success! I guess the factory reset did the trick, but I now have this ROM successfully working. After double checking that the correct files were renamed to hopefully prevent an OTA update, I turned airplane mode back off, went into settings and restarted the registration and everything went smoothly! Only problem was since I had sideloaded ES File Explorer, it said it had to be updated because the original one was not signed (it was a newer version than the latest one available in the Amazon store). So,..... I think it is working okay. If any issues arise, or if I get OTA'ed I will report back.
Next to try GAPPS.