Related
Well I have just rooted my device by installing ES File Explorer from the Apps Store and then using Silk browser to download towelroot from towelroot.com. Install it using ES File Explorer and run. Click make it rain and the tablet is rooted. Open ES File Explorer again, top left open the menu, select tools and turn Root Explorer ON.
Now I just need to find what to do next and see what roms are available!
Help!?!
well
reconminicon said:
Well I have just rooted my device by installing ES File Explorer from the Apps Store and then using Silk browser to download towelroot from towelroot.com. Install it using ES File Explorer and run. Click make it rain and the tablet is rooted. Open ES File Explorer again, top left open the menu, select tools and turn Root Explorer ON.
Now I just need to find what to do next and see what roms are available!
Help!?!
Click to expand...
Click to collapse
you could have accomplished most of that by one of the utilities in the development section and use same. 95 utility to disable updates. From that point on start reading there are all kinds of new things that are coming out and lots and lots and lots of information.
from what I read, after you have been rolled back BY Amazon you no longer need to OTA updates ?
jimyv said:
you could have accomplished most of that by one of the utilities in the development section and use same. 94 utility to disable updates. From that point on start reading there are all kinds of new things that are coming out and lots and lots and lots of information.
Click to expand...
Click to collapse
It does work with that firmware. Installed Safestrap and the thor 202 rom with gapps and all works fine.
reconminicon said:
It does work with that firmware. Installed Safestrap and the thor 202 rom with gapps and all works fine.
Click to expand...
Click to collapse
Edit: Just received a reply in another thread, it isn't currently possible to rollback 13.3.2.7. Hopefully it's not too far away though. =( If you did find a way too do it with 13.3.2.7 be sure to tell us how you did it then.
reconminicon said:
It does work with that firmware. Installed Safestrap and the thor 202 rom with gapps and all works fine.
Click to expand...
Click to collapse
just trying to clarify here what worked on your firmware?
The utility for the HDX?
did the rep also tell you you would not be eligible for further OTA updates?so no need to use that utility to block them?
Not a further rollback correct?
which safestrap version? operating on which firmware?
after your roll back down to .7. From what firmware?
as far as I have read there is currently not a way to roll back any further than .7 from .5.1 \.5.2 ...=BRICK
so please explain what you are saying here so you are not confusing people into attempting the wrong things
jimyv said:
just trying to clarify here what worked on your firmware?
The utility for the HDX?
did the rep also tell you you would not be eligible for further OTA updates?so no need to use that utility to block them?
Not a further rollback correct?
which safestrap version? operating on which firmware?
after your roll back down to .7. From what firmware?
as far as I have read there is currently not a way to roll back any further than .7 from .5.1 \.5.2 ...=BRICK
so please explain what you are saying here so you are not confusing people into attempting the wrong things
Click to expand...
Click to collapse
I bought it for my mother for Christmas and thought would be better with Andriod.
Got it out the box connected to the internet and it automatically updated to 4.5.1. I contacted Amazon using the SOS app and told them what I wanted to do and they rolled it back. They told me I would not get any future updates and customer service might be hard in the future as it would be running different software version. They requested TS to do it and said it would take two days. The update automatically came through and updated/backdated.
The SafeStrap version would of been the most recent as I think I downloaded it from their site.
The 2.0.2 Thor Rom I mentioned worked fine. The other one would not install. Cannot remember the message I was given but when going onto the Play Store Iand trying to download the daily newspaper it was saying designed for mobile. So I guess it was based on a mobile Rom. This was no good for me and thought my mother was getting along with the Amazon OS quite good. (As she is 67 and its her first device) so I ended up installing the Amazon OS from SafeStrap.
I ended up taking it back to Argos for an exchange, said it was switching itself of as I didnt know how to get rid of SafeStrap on boot and wanted the updates back. My mother loves it.
Amazon also removed the adverts free of charge but after the emplacement they are back. Need to SOS them again.
Hope this helps as I am no pro.
Sorry. Ignore it. Was 13.3.2.6 not 13.3.2.7
kindle fire hdx 14.3.2.8 (apollo 8.9)
greetins,
I received rollback update to 14.3.2.8, is possible to install any other rom instead on this? Tablet is rooted via towelroot, what is next step, what is necessary to do (is possible to install safestrap? may I after this rollback to previous version where is bootloader unlocked?
Thank you very much for your answer.
dont try to rollback you will brick your device
undulus said:
greetins,
I received rollback update to 14.3.2.8, is possible to install any other rom instead on this? Tablet is rooted via towelroot, what is next step, what is necessary to do (is possible to install safestrap? may I after this rollback to previous version where is bootloader unlocked?
Thank you very much for your answer.
Click to expand...
Click to collapse
Well right now you cant do much:
1. Download safestrap and try to install it (should work)
2. If you can enter safestrap make a backup for stock so you can restore if something goes wrong
3. Make a new slot
4. Switch to new slot
5. Install previously downloaded Nexus 2.0.2 rom to created slot (not stock!!!)
6. Reboot and enjoy your kindle
7. Tell us if you succeeded, its possible that safestrap or later nexus wont work because of 3.2.8 kernel
Dont try to roll back you most probably brick your device
jeryll said:
Well right now you cant do much:
1. Download safestrap and try to install it (should work)
2. If you can enter safestrap make a backup for stock so you can restore if something goes wrong
3. Make a new slot
4. Switch to new slot
5. Install previously downloaded Nexus 2.0.2 rom to created slot (not stock!!!)
6. Reboot and enjoy your kindle
7. Tell us if you succeeded, its possible that safestrap or later nexus wont work because of 3.2.8 kernel
Dont try to roll back you most probably brick your device
Click to expand...
Click to collapse
Thank you very much, installation of safestrap and after this rom Nexus 2.0.2 was without problem, all is working, thank you again. But is any way howto rollback to previous firmware - I am not sure version, but as I read, is possible to rollback into version where the bootloader was open and is not necessary to use safestrap ( Safestrap is good, but I have to modifed my partition )
How big partition for system is necessary? Default value was mayby 2.5GB.
And thank you again
Well
undulus said:
But is any way howto rollback to previous firmware - I am not sure version, but as I read, is possible to rollback into version where the bootloader was open and is not necessary to use safestrap ( Safestrap is good, but I have to modifed my partition )
How big partition for system is necessary? Default value was mayby 2.5GB.
And thank you again
Click to expand...
Click to collapse
I am glad you have working Nexus...
For downgrading using known method you must be on firmware xx.3.2.6, xx.3.2.5, xx.3.2.4. Several peoples reported that they bricked their device trying downgrade from xx.3.2.7! You can check here, but you have been warned, dont try that on your device!!! If you brick your device I cant help you, dont know how...
Default size for system partition is fine, I think...
undulus said:
Thank you very much, installation of safestrap and after this rom Nexus 2.0.2 was without problem, all is working, thank you again. But is any way howto rollback to previous firmware - I am not sure version, but as I read, is possible to rollback into version where the bootloader was open and is not necessary to use safestrap ( Safestrap is good, but I have to modifed my partition )
How big partition for system is necessary? Default value was mayby 2.5GB.
And thank you again
Click to expand...
Click to collapse
Hi,
which version of Safetrap you installed? All links I see are for Apollo (in the thread linked above), and my device is Thor. I assume i sould install Safestrap-Thor-3.75-os3.2.4-B02.apk (not Apollos) ?
Also, once installed, is there a way to revert back everything (fire recovery and etc)?
johim said:
Hi,
which version of Safetrap you installed? All links I see are for Apollo, and my device is Thor. I assume i sould install Safestrap-Thor-3.75-os3.2.4-B02.apk (not Apollos) ?
Also, once installed, is there a way to revert back everything (fire recovery and etc)?
Click to expand...
Click to collapse
Safestrap actually doesn't replace the original recovery like TWRP.
All you need to do is uninstall it through that same app, but remember to remove any additional ROM slots or else they'll still be taking up space.
EncryptedCurse said:
Safestrap actually doesn't replace the original recovery like TWRP.
All you need to do is uninstall it through that same app, but remember to remove any additional ROM slots or else they'll still be taking up space.
Click to expand...
Click to collapse
I understand. Its all working now. Its more slow than usual thou.
Another question, once installed Nexus 2.0.2, do I need to root it? Any recommended method? I'm guessing I only need to flash supersu from safetrap, tried searchin in the safetrap topic, but its huge.
Hey, so I purchased a Kindle Fire HDX 7" that came with the 13.3.0.5 firmware.
From what I was able to gather on here I was able to root, and disable the OTA , also installed xposed and HDxposed.
I might have got a little ahead of myself seeing I really want to get the bootloader unlock, twrp installed, and get a proper android OS rom installed.
All the posts I can find seem to be updated to only work on firmware .3.2.3.2 , and by flashing a rom using adb or a third party app to get twrp installed. From there it's smooth sailing to installing a custom rom.
So my question is , how the heck to I upgrade to firmware .3.2.3.2 without twrp already installed, and where can I find these .bins to get there?
Thanks for the help in advance.
Darmoktalk said:
Hey, so I purchased a Kindle Fire HDX 7" that came with the 13.3.0.5 firmware.
From what I was able to gather on here I was able to root, and disable the OTA , also installed xposed and HDxposed.
I might have got a little ahead of myself seeing I really want to get the bootloader unlock, twrp installed, and get a proper android OS rom installed.
All the posts I can find seem to be updated to only work on firmware .3.2.3.2 , and by flashing a rom using adb or a third party app to get twrp installed. From there it's smooth sailing to installing a custom rom.
So my question is , how the heck to I upgrade to firmware .3.2.3.2 without twrp already installed, and where can I find these .bins to get there?
Thanks for the help in advance.
Click to expand...
Click to collapse
While 3.2.3.2 is the recommended base you don't need it to flash twrp. Suggested path with links (assumes FireOS < xx.3.3.x, root and OTA block):
- (recommended): remove Xposed and HDXposed as they are not needed and may present complications. If you used HDXposed to block OTA remove the block before uininstalling (make sure your device is in airplane mode!) and use HDX toolkit instead (here) which is a tethered solution that offers root and OTA blocking along with other capabilities.
- (optional): sideload ES File Explorer which can be used to locate/manage downloaded files and verify checksums along with a host of other capabilities.
- (optional): sideload Flashify which can be used to back-up your current recovery and flash various components from within a functioning ROM. Back-up your existing recovery and leave on device (small).
- flash twrp (here) using the adb commands shown in the post or Flashify from within FireOS. Be sure to grab the version appropriate to your device. Restart device using power+<vol-up> to validate twrp is working.
- (recommended): from within twrp take a full backup and copy to an external host (just in case ...)
- from twrp upgrade bootloader to 3.2.3.2 (here)
- from twrp backup your device and copy to an external host (very important; don't skip this step)
- (recommended): from twrp flash Nexus v2.0.5 (Jelly Bean) and associated gapps package over FireOS which will give you full access to Google Play and a more flexible platform to work through the bootloader unlock procedure. FireOS is fickle beast; best to remove it from the equation early. Also verifies all is well with twrp.
Bounce back when the above is working and we'll turn to bootloader unlocking. A word of caution: while the above steps are relatively safe any flash gone bad can yield a a non-recoverable brick. Follow the procedures carefully, verify checksums on downloaded images, think twice before acting and don't go off script. Ask questions if unsure. Good luck.
Davey126 said:
While 3.2.3.2 is the recommended base you don't need it to flash twrp. Suggested path with links (assumes FireOS < xx.3.3.x, root and OTA block):
- (recommended): remove Xposed and HDXposed as they are not needed and may present complications. If you used HDXposed to block OTA remove the block before uininstalling (make sure your device is in airplane mode!) and use HDX toolkit instead (here) which is a tethered solution that offers root and OTA blocking along with other capabilities.
- (optional): sideload ES File Explorer which can be used to locate/manage downloaded files and verify checksums along with a host of other capabilities.
- (optional): sideload Flashify which can be used to back-up your current recovery and flash various components from within a functioning ROM. Back-up your existing recovery and leave on device (small).
- flash twrp (here) using the adb commands shown in the post or Flashify from within FireOS. Be sure to grab the version appropriate to your device. Restart device using power+<vol-up> to validate twrp is working.
- (recommended): from within twrp take a full backup and copy to an external host (just in case ...)
- from twrp upgrade bootloader to 3.2.3.2 (here)
- from twrp backup your device and copy to an external host (very important; don't skip this step)
- (recommended): from twrp flash Nexus v2.0.5 (Jelly Bean) and associated gapps package over FireOS which will give you full access to Google Play and a more flexible platform to work through the bootloader unlock procedure. FireOS is fickle beast; best to remove it from the equation early. Also verifies all is well with twrp.
Bounce back when the above is working and we'll turn to bootloader unlocking. A word of caution: while the above steps are relatively safe any flash gone bad can yield a a non-recoverable brick. Follow the procedures carefully, verify checksums on downloaded images, think twice before acting and don't go off script. Ask questions if unsure. Good luck.
Click to expand...
Click to collapse
Hey, thanks. I was able to get TWRP 2.8.7.0 flashed, and I made a backup first thing.
I ran into a problem however after installing the bootloader upgrade zip, I did a reboot after, and I'm only getting a black screen :/
I managed to get back in TWRP, should I restore that backup, or just move forward with installing the custom rom since I'll be overwriting fireOS anyway?
Thanks.
Ok, so I figured it was just a conflict with the version of FireOS since the recovery seemed to be functioning correctly.
I went ahead and installed the Nexus 2.0.5 rom and gapps. Success.. Boots into the rom fine, I tested some of the google apps, all is nice.
It appears to be working well, so I guess I'd be looking at installing a more updated roms, which needs an unlocked bootloader, yes?
Thanks again.
Darmoktalk said:
Ok, so I figured it was just a conflict with the version of FireOS since the recovery seemed to be functioning correctly.
I went ahead and installed the Nexus 2.0.5 rom and gapps. Success.. Boots into the rom fine, I tested some of the google apps, all is nice.
It appears to be working well, so I guess I'd be looking at installing a more updated roms, which needs an unlocked bootloader, yes?
Thanks again.
Click to expand...
Click to collapse
Great! Was a bit nervous (but not overly worried) after your first response. You took the path I would have recommended (flashing Nexus v2).
Suggestions before moving on to bootloader:
- make a backup of your system w/Nexus (just in case ...)
- reflash 3.2.3.2 bootloader update. There is no test for bootloader version; want to make sure you are on 3.2.3.2
Next step is to make sure you can access fastboot via Windows host. Linux and OSX also work (and are somewhat easier) but most of the tools/tips assume Windows. Take a peek at this post; expand to see full discussion if needed. Bounce back when everything is working. I am on the hunt for a very nice post from @Cl4ncy that details the bootloader unlock procedure. There are several other resources--just though s/he did a good job filling in detail. Stay tuned ...
Edit: A couple bootloader resources for you to ponder:
- procedure including links to various resources (here)
- post from @Cl4ncy referenced above (here)
You'll probably find the material a bit confusing at first. It's easier to answer specific questions than attempt to cover all the nuances. A lot depends on your experience with Android, Windows and the other tools referenced.
BTW - if you are using a 64-bit version of Windows > 8.0 (eg: 8.1, 10) you may need to disable the signed driver check. Bounce back if you have trouble installing the Kindle drivers referenced above.
Good luck - ask for help/clarification if needed!
---------- Post added at 04:00 PM ---------- Previous post was at 03:42 PM ----------
Darmoktalk said:
It appears to be working well, so I guess I'd be looking at installing a more updated roms, which needs an unlocked bootloader, yes?
Click to expand...
Click to collapse
Correct; bootloader needs to be unlocked for HDX variants of CM11, CM12 and Nexus v4 (and probably anything newer that comes along). See previous post for info on BL unlock procedure.
Davey126 said:
Great! Was a bit nervous (but not overly worried) after your first response. You took the path I would have recommended (flashing Nexus v2).
Suggestions before moving on to bootloader:
- make a backup of your system w/Nexus (just in case ...)
- reflash 3.2.3.2 bootloader update. There is no test for bootloader version; want to make sure you are on 3.2.3.2
Next step is to make sure you can access fastboot via Windows host. Linux and OSX also work (and are somewhat easier) but most of the tools/tips assume Windows. Take a peek at this post; expand to see full discussion if needed. Bounce back when everything is working. I am on the hunt for a very nice post from @Cl4ncy that details the bootloader unlock procedure. There are several other resources--just though s/he did a good job filling in detail. Stay tuned ...
Edit: A couple bootloader resources for you to ponder:
- procedure including links to various resources (here)
- post from @Cl4ncy referenced above (here)
You'll probably find the material a bit confusing at first. It's easier to answer specific questions than attempt to cover all the nuances. A lot depends on your experience with Android, Windows and the other tools referenced.
BTW - if you are using a 64-bit version of Windows > 8.0 (eg: 8.1, 10) you may need to disable the signed driver check. Bounce back if you have trouble installing the Kindle drivers referenced above.
Good luck - ask for help/clarification if needed!
---------- Post added at 04:00 PM ---------- Previous post was at 03:42 PM ----------
Correct; bootloader needs to be unlocked for HDX variants of CM11, CM12 and Nexus v4 (and probably anything newer that comes along). See previous post for info on BL unlock procedure.
Click to expand...
Click to collapse
Ok, so I've got adb+fastboot in a folder, booted the HDX into fastboot mode via TWRP restart>bootloader, got the PDAnet drivers installed, issued a fastboot -i 0x1949 devices command, and got a response "D0FBA0A034520HL7 fastboot" .. So it seems like it's talking to my device correctly?
EDIT:
Ok, so I had the eye of tiger and decided to go through with the unlock using CuberHDX.py, mashed my serials together to get my unlock, rebooted to fastboot, issued the flash unlock command for the .unlock file.. All green on my kindle screen "unlock code ok" .. Rebooted, and all is good.
I think.. It's done? Custom recovery, unlocked bootloader.
Darmoktalk said:
Ok, so I've got adb+fastboot in a folder, booted the HDX into fastboot mode via TWRP restart>bootloader, got the PDAnet drivers installed, issued a fastboot -i 0x1949 devices command, and got a response "D0FBA0A034520HL7 fastboot" .. So it seems like it's talking to my device correctly?
EDIT:
Ok, so I had the eye of tiger and decided to go through with the unlock using CuberHDX.py, mashed my serials together to get my unlock, rebooted to fastboot, issued the flash unlock command for the .unlock file.. All green on my kindle screen "unlock code ok" .. Rebooted, and all is good.
I think.. It's done? Custom recovery, unlocked bootloader.
Click to expand...
Click to collapse
TWRP & unlocked bootloader, you're ready for the wonderland of HDX ROMs then.
Be sure to install the correct one for your device, i.e. don't mix up Thor and Apollo ROMs.
Now you can decide, Nexus, CM11 or CM12 - your choice. Read the Installation notes and requirements carefully!
Cl4ncy said:
TWRP & unlocked bootloader, you're ready for the wonderland of HDX ROMs then.
Be sure to install the correct one for your device, i.e. don't mix up Thor and Apollo ROMs.
Now you can decide, Nexus, CM11 or CM12 - your choice. Read the Installation notes and requirements carefully!
Click to expand...
Click to collapse
Darmoktalk said:
Ok, so I've got adb+fastboot in a folder, booted the HDX into fastboot mode via TWRP restart>bootloader, got the PDAnet drivers installed, issued a fastboot -i 0x1949 devices command, and got a response "D0FBA0A034520HL7 fastboot" .. So it seems like it's talking to my device correctly?
EDIT:
Ok, so I had the eye of tiger and decided to go through with the unlock using CuberHDX.py, mashed my serials together to get my unlock, rebooted to fastboot, issued the flash unlock command for the .unlock file.. All green on my kindle screen "unlock code ok" .. Rebooted, and all is good.
I think.. It's done? Custom recovery, unlocked bootloader.
Click to expand...
Click to collapse
Congrats! You're ready to roll. Don't forget the occasional backup; don't flash anything not specifically customized for your device as you can still brick the puppy (although recovery is easier/possible with an unlocked bootloader). ROMs can be snagged from the top of the page (full xda site) or from appropriate threads in the HDX Android development forum. Have fun!
Thank you so much for the help. I came late to the game, and spent a few days reading through all the posts trying to piece together a starting point , and path to make it happen.
Learned a lot, thanks Davey126 for the walktrough and patience, and thanks Cl4ncy for the bootloader unlock instructions.
:good::good::good:
Hopefully this thread will also help others down the line.
Great job, keep it up
Could this be stickied? as it is a great how to/information spot.
Hi Davey126-
I tried following your procedure on a Thor with 13.3.2.8:
Davey126 said:
While 3.2.3.2 is the recommended base you don't need it to flash twrp. Suggested path with links (assumes FireOS < xx.3.3.x, root and OTA block):
- (recommended): remove Xposed and HDXposed as they are not needed and may present complications. If you used HDXposed to block OTA remove the block before uininstalling (make sure your device is in airplane mode!) and use HDX toolkit instead (here) which is a tethered solution that offers root and OTA blocking along with other capabilities.
- (optional): sideload ES File Explorer which can be used to locate/manage downloaded files and verify checksums along with a host of other capabilities.
- (optional): sideload Flashify which can be used to back-up your current recovery and flash various components from within a functioning ROM. Back-up your existing recovery and leave on device (small).
- flash twrp (here) using the adb commands shown in the post or Flashify from within FireOS. Be sure to grab the version appropriate to your device. Restart device using power+<vol-up> to validate twrp is working.
- (recommended): from within twrp take a full backup and copy to an external host (just in case ...)
- from twrp upgrade bootloader to 3.2.3.2 (here)
Click to expand...
Click to collapse
I'm fine until I try to flash TWRP; using Flashify or ADB seems to work but the unit will not boot into recovery. If I flash the stock recovery back all is well.
Looking at the TWRP download page, there's a note that the bootloader must be unlocked. I used the 1-Click unlocker, and it fails with Unlock Code is NOT correct. I guess my bootloader is not 3.2.3.2
I'm kind of stymied at this point, I'm guessing that I can't start with 13.3.2.8? Any advice on how to proceed would be really appreciated
Bob_in_RI said:
Hi Davey126-
I tried following your procedure on a Thor with 13.3.2.8:
I'm fine until I try to flash TWRP; using Flashify or ADB seems to work but the unit will not boot into recovery. If I flash the stock recovery back all is well.
Looking at the TWRP download page, there's a note that the bootloader must be unlocked. I used the 1-Click unlocker, and it fails with Unlock Code is NOT correct. I guess my bootloader is not 3.2.3.2
I'm kind of stymied at this point, I'm guessing that I can't start with 13.3.2.8? Any advice on how to proceed would be really appreciated
Click to expand...
Click to collapse
You can't unlock or flash TWRP on a tablet with FireOS 3.2.8.
Your only options would be to stay on 3.2.8 and install Safestrap 3, or manually upgrade to 4.5.2 and install Safestrap 4.
Thanks! I was able to install a ton with safestrap.
Davey126 said:
While 3.2.3.2 is the recommended base you don't need it to flash twrp. Suggested path with links (assumes FireOS < xx.3.3.x, root and OTA block):
Click to expand...
Click to collapse
Will this method also work starting from 13.3.2.4 Firmware or do I have to downgrade somehow first? Thanks.
Nana99 said:
Will this method also work starting from 13.3.2.4 Firmware or do I have to downgrade somehow first? Thanks.
Click to expand...
Click to collapse
You must downgrade first. Good news is you can use the downgrade images provided by @ggow, check page 2 here (page 1 is for 3.2.5/3.2.6 users who can NOT use those images!).
Is your HDX rooted and Safestrap installed? It won't get any easier then.
Any questions ask before you brick your HDX!
After the downgrade you can install TWRP, update the bootloader to 3.2.3.2, then unlock - try the one-click-solution first.
Be sure to create a backup of your current Fire OS via TWRP and move it to your PC before you flash any custom ROM!
Cl4ncy said:
You must downgrade first. Good news is you can use the downgrade images provided by @ggow, check page 2 here (page 1 is for 3.2.5/3.2.6 users who can NOT use those images!).
Is your HDX rooted and Safestrap installed? It won't get any easier then.
Any questions ask before you brick your HDX!
After the downgrade you can install TWRP, update the bootloader to 3.2.3.2, then unlock - try the one-click-solution first.
Be sure to create a backup of your current Fire OS via TWRP and move it to your PC before you flash any custom ROM!
Click to expand...
Click to collapse
Thanks. Yes my HDX is rooted and safestrap als well as Xposed and HDXposed is installed. I did all this over year ago shortly after I bought the device and never really touched it since then. However over time many things have stopped working correctly so I do want to upgrade to a more stabel version with gapps working or to a custom rom.
Please tell me which Firmware I have to downgrade to. Is it 3.1.0 or 3.2.3.2?
Thanks again for your support.
Nana99 said:
Thanks. Yes my HDX is rooted and safestrap als well as Xposed and HDXposed is installed. I did all this over year ago shortly after I bought the device and never really touched it since then. However over time many things have stopped working correctly so I do want to upgrade to a more stabel version with gapps working or to a custom rom.
Please tell me which Firmware I have to downgrade to. Is it 3.1.0 or 3.2.3.2?
Thanks again for your support.
Click to expand...
Click to collapse
The downgrade image is a modified 3.2.4 which claims to be 3.0.9, so you can "update" to 3.1.0, which is enough to install TWRP 2.8.7.0 (I'm not sure about TWRP 3.0.0-0, so install 2.8.7.0 and update to 3.0.0-0 via TWRP itself later, if you want to). There's no need to update to 3.2.3.2 then, as you can just update the bootloader (see above), which you should do via TWRP to solve a screen grafic issue.
Keep WLAN off/flight mode active during the procedure, you don't want to get updated by Amazon!
Cl4ncy said:
The downgrade image is a modified 3.2.4 which claims to be 3.0.9, so you can "update" to 3.1.0, which is enough to install TWRP 2.8.7.0 (I'm not sure about TWRP 3.0.0-0, so install 2.8.7.0 and update to 3.0.0-0 via TWRP itself later, if you want to). There's no need to update to 3.2.3.2 then, as you can just update the bootloader (see above), which you should do via TWRP to solve a screen grafic issue.
Keep WLAN off/flight mode active during the procedure, you don't want to get updated by Amazon!
Click to expand...
Click to collapse
Thanks once again. Everything worked perfectly. I downgraded with 3.2.4_rollback and "upgraded" to 3.1.0, rooted and installed twrp. Then updated the bootloader and installed nexus 2.05. Then unlocked the bootloader with 1-click. I then installed the nexus 4.0.5 rom along with the gapps. After that I installed CM13 together with open gapps and super-su.
Couldn't have done it without your help!!!:good::good::good:
Nana99 said:
Thanks once again. Everything worked perfectly. I downgraded with 3.2.4_rollback and "upgraded" to 3.1.0, rooted and installed twrp. Then updated the bootloader and installed nexus 2.05. Then unlocked the bootloader with 1-click. I then installed the nexus 4.0.5 rom along with the gapps. After that I installed CM13 together with open gapps and super-su.
Couldn't have done it without your help!!!:good::good::good:
Click to expand...
Click to collapse
Great! Enjoy your "free" HDX.
I am on rooted Thor with 13.3.2.4, with the Nexus Rom installed via safestrap. I have been reading all the threads on unlocking the bootloader and find all of the steps to be very scary. I would like to wait until there was some kind of "toolkit" for this rather than having to first downgrade and then use python through adb etc which I am somewhat uncomfortable with. Will there ever be such a simpler solution?
The bootloader unlock procedure is a no brainer, can't mess up anything there. Downgrading is a little risky, but you're on 3.2.4, thus you can even use the rollback images for Safestrap, take a look at this thread (page 1 is about 3.2.5/3.2.6 users who can NOT use the downgrade images). I'm afraid it won't get any easier than that.
If you don't want to use Python, just execute the adb commands to get your ID and serial (post them here, or PM me if you don't want anyone to see them), I'll create the .unlock file for you then. Downgrading and (actual) unlocking are tasks you have to do yourself though.
I think I might try it this weekend. Thanks for the help.
Cl4ncy said:
The bootloader unlock procedure is a no brainer, can't mess up anything there. Downgrading is a little risky, but you're on 3.2.4, thus you can even use the rollback images for Safestrap, take a look at this thread (page 1 is about 3.2.5/3.2.6 users who can NOT use the downgrade images). I'm afraid it won't get any easier than that.
If you don't want to use Python, just execute the adb commands to get your ID and serial (post them here, or PM me if you don't want anyone to see them), I'll create the .unlock file for you then. Downgrading and (actual) unlocking are tasks you have to do yourself though.
Click to expand...
Click to collapse
I have successfully downgraded to 13.3.1.0, but I am confused about how to install TWRP. Since I have not enabled wifi and registered, I can't install flashify or cwm, or even install a file explorer apk to access my storage, and I don't know how to get the twrp.img file (which I guess I can only install via adb?) Where do I get the correct twrp.img file? I'm kind of stuck....
kbs24 said:
I have successfully downgraded to 13.3.1.0, but I am confused about how to install TWRP. Since I have not enabled wifi and registered, I can't install flashify or cwm, or even install a file explorer apk to access my storage, and I don't know how to get the twrp.img file (which I guess I can only install via adb?) Where do I get the correct twrp.img file? I'm kind of stuck....
Click to expand...
Click to collapse
I am by no means an expert but I just went through this process myself yesterday and it was relatively simple. Check this thread. It has a number of helpful posts in it, including my questions from yesterday.
The correct TWRP image is here. Just follow the instructions in that thread. It's super simple if you use the minimal adb and fastboot linked by Cl4ncy in the first thread I linked. If you have any other questions I'll do my best to help you.
kbs24 said:
I have successfully downgraded to 13.3.1.0, but I am confused about how to install TWRP. Since I have not enabled wifi and registered, I can't install flashify or cwm, or even install a file explorer apk to access my storage, and I don't know how to get the twrp.img file (which I guess I can only install via adb?) Where do I get the correct twrp.img file? I'm kind of stuck....
Click to expand...
Click to collapse
Sorry for the late reply, @muunkin pointed you in the right direction already.
Be sure to (re-)root 3.1.0 and disable OTA via HDX ToolKit, and enable USB debugging in Fire OS, hope you installed minimal adb and fastboot, then copy the TWRP image for your HDX (Thor = 7", Apollo = 8.9") to the root of the sdcard (which is the directory you'll see in Explorer after connecting the HDX to your PC, i.e. don't open another directory), open a DOS box, change dir to the adb directory (enter cd\adb) and enter the commands mentioned in the TWRP thread. This will flash the TWRP image to the recovery parition.
Do a backup of your Fire OS in TWRP before you flash any custom ROM, and copy it to your PC, also look for the TWRP backup of the stock recovery (I think TWRP does a backup somewhere), and move that to your PC as well.
In case you don't know how to access TWRP: with the HDX powered off, you press and hold volume up, then press and hold the power button, release both when the grey Kindle Fire logo appears on screen. Some ROMs (e.g. CM12) offer the advanced reboot in developer options, this will add options to reboot into recovery, bootloader or a soft (quick) reboot to the power menu.
Cl4ncy said:
Sorry for the late reply, @muunkin pointed you in the right direction already.
Be sure to (re-)root 3.1.0 and disable OTA via HDX ToolKit, and enable USB debugging in Fire OS, hope you installed minimal adb and fastboot, then copy the TWRP image for your HDX (Thor = 7", Apollo = 8.9") to the root of the sdcard (which is the directory you'll see in Explorer after connecting the HDX to your PC, i.e. don't open another directory), open a DOS box, change dir to the adb directory (enter cd\adb) and enter the commands mentioned in the TWRP thread. This will flash the TWRP image to the recovery parition.
Do a backup of your Fire OS in TWRP before you flash any custom ROM, and copy it to your PC, also look for the TWRP backup of the stock recovery (I think TWRP does a backup somewhere), and move that to your PC as well.
In case you don't know how to access TWRP: with the HDX powered off, you press and hold volume up, then press and hold the power button, release both when the grey Kindle Fire logo appears on screen. Some ROMs (e.g. CM12) offer the advanced reboot in developer options, this will add options to reboot into recovery, bootloader or a soft (quick) reboot to the power menu.
Click to expand...
Click to collapse
Thank you both @muunkin and @Cl4ncy for guiding me through this. It is clear now that I have to flash TWRP via adb. Unfortunately I did, however, last night briefly turn on wifi in order to get es file explorer, and very quickly the OS ugraded itself to 13.3.2.3. Then, stupidly, I decided to go back to Nexus rom 2.0.2, which I did by reinstalling safestrap. And, Nexus rom is installed on the Stock Rom slot, and I did NOT backup the 13.3.2.3 stock rom. SO, since I am on Nexus rom, do I understand correctly that I need to begin again by downgrading to 13.3.1.0? Right? (After printing out all of these threads and printing out a lot of it and carefully reading, it looks to me like if I had stayed on stock 13.3.2.3 I would not have had to downgrade.....but too late now anyway.) I do have the minimal adb and fastboot installed, and my device is recognized, so eventually this will work I'm pretty sure. I appreciate the help!
kbs24 said:
Thank you both @muunkin and @Cl4ncy for guiding me through this. It is clear now that I have to flash TWRP via adb. Unfortunately I did, however, last night briefly turn on wifi in order to get es file explorer, and very quickly the OS ugraded itself to 13.3.2.3. Then, stupidly, I decided to go back to Nexus rom 2.0.2, which I did by reinstalling safestrap. And, Nexus rom is installed on the Stock Rom slot, and I did NOT backup the 13.3.2.3 stock rom. SO, since I am on Nexus rom, do I understand correctly that I need to begin again by downgrading to 13.3.1.0? Right? (After printing out all of these threads and printing out a lot of it and carefully reading, it looks to me like if I had stayed on stock 13.3.2.3 I would not have had to downgrade.....but too late now anyway.) I do have the minimal adb and fastboot installed, and my device is recognized, so eventually this will work I'm pretty sure. I appreciate the help!
Click to expand...
Click to collapse
No, 13.3.2.3 is ok for both TWRP and unlocking the bootloader, i.e. no need to flash 3.1.0 again - a firmware below 3.2.4 is enough.
Cl4ncy said:
No, 13.3.2.3 is ok for both TWRP and unlocking the bootloader, i.e. no need to flash 3.1.0 again - a firmware below 3.2.4 is enough.
Click to expand...
Click to collapse
Even if I am not running on the stock rom? I can adb install TWRP while on Nexus rom?
kbs24 said:
Even if I am not running on the stock rom? I can adb install TWRP while on Nexus rom?
Click to expand...
Click to collapse
Hm, I'm not exactly sure about this - @ggow's answer here seems to point out that you really have to do it all over again.
Why did you install Safestrap again anyway? ADB-flashing TWRP and unlocking the bootloader before you install a custom ROM would've been the next steps. Also I told you to create a backup of your stock slot before you flash any custom ROM, didn't I?
Cl4ncy said:
Hm, I'm not exactly sure about this - @ggow's answer here seems to point out that you really have to do it all over again.
Why did you install Safestrap again anyway? ADB-flashing TWRP and unlocking the bootloader before you install a custom ROM would've been the next steps. Also I told you to create a backup of your stock slot before you flash any custom ROM, didn't I?
Click to expand...
Click to collapse
Yes you sure did, and that's why I said "stupidly" about me putting safestrap back and nexus rom. I was overanxious and acted impulsively, not having a recovery installed was freaking me out. Bad habit. About doing the backup, there did not appear to be enough room on the internal storage. Sorry. We'll start over no problem. Again thanks.
kbs24 said:
Yes you sure did, and that's why I said "stupidly" about me putting safestrap back and nexus rom. I was overanxious and acted impulsively, not having a recovery installed was freaking me out. Bad habit. About doing the backup, there did not appear to be enough room on the internal storage. Sorry. We'll start over no problem. Again thanks.
Click to expand...
Click to collapse
I'm also not sure how to do this now. You don't have any Safestrap 3.2.3 Fire OS backup to restore, you shouldn't use the 3.2.4 rollback image, as you're not on 3.2.4, so what do you want to flash to the stock slot now? Or did I miss anything?
Cl4ncy said:
I'm also not sure how to do this now. You don't have any Safestrap 3.2.3 Fire OS backup to restore, you shouldn't use the 3.2.4 rollback image, as you're not on 3.2.4, so what do you want to flash to the stock slot now? Or did I miss anything?
Click to expand...
Click to collapse
I was going to look for a stock 3.2.3 to flash. If can't find, I do have a backup of stock 3.2.4 on the card which I would flash, thus requiring the downgrade.
kbs24 said:
I was going to look for a stock 3.2.3 to flash. If can't find, I do have a backup of stock 3.2.4 on the card which I would flash, thus requiring the downgrade.
Click to expand...
Click to collapse
I haven't seen a 3.2.3 Safestrap flashable Image, good luck. Regarding the 3.2.4 backup I'm not sure whether it works with the 3.2.3 bootloader.
Cl4ncy said:
I haven't seen a 3.2.3 Safestrap flashable Image, good luck. Regarding the 3.2.4 backup I'm not sure whether it works with the 3.2.3 bootloader.
Click to expand...
Click to collapse
Yeah, I am probably screwed. But we'll see. I'm pretty sure I understand what the process should be at least.
kbs24 said:
Yeah, I am probably screwed. But we'll see. I'm pretty sure I understand what the process should be at least.
Click to expand...
Click to collapse
Not sure how far you got with this but you *should* be able to flash TWRP from Nexus provided the version of FireOS was 3.2.3.2 or lower prior to the installation of Safestrap v3. The customized version of twrp leverages a vulnerability in the HDX bootloader that is installed with FireOS. Neither Safestrap nor Nexus mess with the bootloader so the prerequisites should remain intact. I say should as interactions are complex - further complicated by a fussy device with limited recovery capability should something go wrong. To the best of my knowledge no one has attempted a twrp flash from Nexus while Safestrap v3 is installed.
Thoughts:
- grab flashify from the play store or here; make a backup of your current recovery environment (this step will also help to familiarize you with flashify)
- download the HDX customized version of twrp (here); use ES File Explorer to verify MD5
- use flashify to install twrp (can also be done via adb commands as shown in the twrp op)
Options:
- unlock the bootloader before attempting other remedial steps. Unlocking is a frustrating but low/no risk activity that yields substantially improved recovery capabilities once completed. Yep - you can do this without twrp (unlocking before flashing twrp is the recommended path according to several devs - although I prefer the opposite).
[-or-]
- flash 3.1.0 from here to the stock slot and then attempt to remove Safestrap v3. If successful you can proceed with flashing twrp unlocking, etc in the normal manner. As with any flash there is a risk something will go wrong or FireOS will not start up properly. To help mitigate the latter suggest installing a fallback version of Nexus v2 in a secondary slot. Don't forget to remove this slot before uninstalling SS.
The above is only an outline. Give it some thought and post any questions BEFORE taking action. I also suggest you let this post sit for a few days in case some of the rational is fatally flawed. Lots of smart people in the community who will jump in if my guidance is misdirected (which it has been shown to be on occasion). Don't risk a brick by acting too quickly. Proper preparation is essential for a successful outcome.
Sorry for sounding like your mum ... :angel:
Davey126 said:
Not sure how far you got with this but you *should* be able to flash TWRP from Nexus provided the version of FireOS was 3.2.3.2 or lower prior to the installation of Safestrap v3. The customized version of twrp leverages a vulnerability in the HDX bootloader that is installed with FireOS. Neither Safestrap nor Nexus mess with the bootloader so the prerequisites should remain intact. I say should as interactions are complex - further complicated by a fussy device with limited recovery capability should something go wrong. To the best of my knowledge no one has attempted a twrp flash from Nexus while Safestrap v3 is installed.
Thoughts:
- grab flashify from the play store or here; make a backup of your current recovery environment (this step will also help to familiarize you with flashify)
- download the HDX customized version of twrp (here); use ES File Explorer to verify MD5
- use flashify to install twrp (can also be done via adb commands as shown in the twrp op)
Options:
- unlock the bootloader before attempting other remedial steps. Unlocking is a frustrating but low/no risk activity that yields substantially improved recovery capabilities once completed. Yep - you can do this without twrp (unlocking before flashing twrp is the recommended path according to several devs - although I prefer the opposite).
[-or-]
- flash 3.1.0 from here to the stock slot and then attempt to remove Safestrap v3. If successful you can proceed with flashing twrp unlocking, etc in the normal manner. As with any flash there is a risk something will go wrong or FireOS will not start up properly. To help mitigate the latter suggest installing a fallback version of Nexus v2 in a secondary slot. Don't forget to remove this slot before uninstalling SS.
The above is only an outline. Give it some thought and post any questions BEFORE taking action. I also suggest you let this post sit for a few days in case some of the rational is fatally flawed. Lots of smart people in the community who will jump in if my guidance is misdirected (which it has been shown to be on occasion). Don't risk a brick by acting too quickly. Proper preparation is essential for a successful outcome.
Sorry for sounding like your mum ... :angel:
Click to expand...
Click to collapse
Thanks for your input. I am still on the nexus rom, but I am fairly sure that Safestrap was installed while on 13.3.2.4. Is there a way to tell? It is safestrap 3.75, based on twrp 2.7.
I had some time today to work on this, and after looking over the ideas from all of you (thank you very much!) it seemed that my only option is to restore my backup which will get me back to the Nexus 2.0.2 rom. So I did this successfully. Being on Nexus rom, I was then able to use the 13.3.2.4 rollback file to get back to 13.3.0.9. Then ran into trouble......the system update to 13.3.1.0 was not successful. the .bin file was located, but all that happened was a "validating update file" followed by forced reboot. I remain stuck on 13.3.0.9. There are threads discussing editing build.prop but I know I did not have to do this when I first did a rollback a few days ago. Not sure whether to give up or maybe someone has another idea how to get the system to use that .bin file? Should I turn on wifi and wait for an ota or is that too risky, will it jump me all the way up to the most current build? Will it maybe go incrementally?
kbs24 said:
Thanks for your input. I am still on the nexus rom, but I am fairly sure that Safestrap was installed while on 13.3.2.4. Is there a way to tell? It is safestrap 3.75, based on twrp 2.7.
Click to expand...
Click to collapse
(Also as you suggested, I did try flashing the zip 3.1.0 and it did not work, never rebooted successfully. So went back again to 3.0.9.)
kbs24 said:
I had some time today to work on this, and after looking over the ideas from all of you (thank you very much!) it seemed that my only option is to restore my backup which will get me back to the Nexus 2.0.2 rom. So I did this successfully. Being on Nexus rom, I was then able to use the 13.3.2.4 rollback file to get back to 13.3.0.9. Then ran into trouble......the system update to 13.3.1.0 was not successful. the .bin file was located, but all that happened was a "validating update file" followed by forced reboot. I remain stuck on 13.3.0.9. There are threads discussing editing build.prop but I know I did not have to do this when I first did a rollback a few days ago. Not sure whether to give up or maybe someone has another idea how to get the system to use that .bin file? Should I turn on wifi and wait for an ota or is that too risky, will it jump me all the way up to the most current build? Will it maybe go incrementally?
Click to expand...
Click to collapse
Glad you were able to make some progress. I believe you could have flashed twrp from Nexus as I believe you successfully downgraded/upgraded to 13.3.2.3 which would then be the base version when you reininstalled Safestrap. But you found another path which is just fine.
It is possible the 13.3.1.0 is invalid (possibly corrupt). You can use ES File Explorer to validate the MD5 (c49c0363de4d8dfa5c87c1bdb88aa2ba) or download a fresh copy here. You can also upgrade directly to 13.3.2.3 instead of hopscotching through 13.3.1.0 and then applying the 13.2.3.3 bootloader update.
I strongly suggest you NOT connect to WiFi as it is unpredictable if/when you will receive at OTA and what version will be downloaded. Options for getting files onto you device:
- use HDX toolkit to root and block OTA on 13.3.0.9; you can then enable WiFi
- tether your device and drop files into "Internal Storage"
- use 'adb push' to transfer files
You should not need to mess with build.prop as the 3.2.4->3.0.9 rollback should have handed that. It's quite easy to brick your device if you get any of the edits or permissions wrong.
Hello,
My rooted Transformer Prime was becoming so slow, I eventually unlocked the bootloader and flashed it … at first with Android 5 KatKiss. But it growed slow quite rapidly.
So I flashed it again with the latest build of KatshMallow 6 but after a few months, Google Play entered in a login loop so I could not update my apps nor install new ones.
So I flashed it once more with KatKiss 7.1.2 #26, a few weeks ago. From the start it was really unresponsive and quite slow (being two different symptoms). I tried to tweak it with Kernel Adiutor but to no avail.
Two days ago, it would not update one of my apps (but updated the others). And today the updates stalled in the "download pending" state.
What can I do to troubleshot my TF201 and give her a youth treatment against what seems like planned obsolescence (I didn't know Asus was following this trend)?
Many thanks in advance!
What version of TWRP are you using?
Are you doing a full wipe (not including the recovery partition)?
Are you changing the /DATA file system partition to F2FS ?
A few things that might be mucking up the flash.
NP
Ok, here are the info:
— bootloader 1.00e released by ww_epad_10.6.1.27-20130711 A03
— TWRP 2.8.7.4 @area51
— I formated /data in f2fs
— I wiped Dalvik Cache, System, Cache, Data AND Internal Storage
— last time I flashed, I followed the instruction from point 8 of https://forum.xda-developers.com/tr...uide-tutorial-asus-transformer-prime-t3486237
Does this help? Any tool or other ways to help diagnose my problems?
I would update the TWRP to the latest version found here;
https://androidfilehost.com/?fid=457095661767150802
NP
The only advice I can offer is to follow these instructions to the letter: https://forum.xda-developers.com/showthread.php?t=2407248
Install that ROM and don't install all your apps for 24h or so. If it's still slow then it might be on the way out. These things are getting old.
If you're happy after a day or so then proceed to install the ROM of your choice.
I don't see where you do a [FORMAT];
Go to twrp/wipe/format data then type yes
This is the 1st step after you boot into the recovery console.
NP
Nektopoli said:
I would update the TWRP to the latest version found here;
https://androidfilehost.com/?fid=457095661767150802
NP
Click to expand...
Click to collapse
I tried this but to no avail
Nektopoli said:
I don't see where you do a [FORMAT];
Go to twrp/wipe/format data then type yes
This is the 1st step after you boot into the recovery console.
NP
Click to expand...
Click to collapse
Yes, I did it.
I wonder if it's "slow" like the rest of our tablets, compared with new devices, my TF201 is no speed demon by any stretch of the imagination, but it can run KODI and other
apps under 7.1.2 that it couldn't under 4.1.1. I find I'm waiting a few seconds after tapping on the app button for it to open but it's not a long pause.
NP
djmcnz said:
The only advice I can offer is to follow these instructions to the letter: https://forum.xda-developers.com/showthread.php?t=2407248
Install that ROM and don't install all your apps for 24h or so. If it's still slow then it might be on the way out. These things are getting old.
If you're happy after a day or so then proceed to install the ROM of your choice.
Click to expand...
Click to collapse
Okay, so I downgraded to AndroWook Prime HairyBean v2.31, as suggested by djmcnz. Great move :good: as I recovered the responsiveness I was used to: now, when I click something, the related event happens without delay (these few-seconds delays were happening when opening an app, like Nektopoli said, but unfortunately also whenever I interacted with anything, in any app). Sure, I would not say it really "unleashed the beast": I know our TF201 are not in the same league as more recent devices. Still, it's also way faster than it became with the flashing explained in my original post. Moreover, in more than a month, I had no problem updating apps. So in a way, original problem solved. Thanks all! :highfive:
But … now my problem is I need a newer Android to be able to install some apps/games, mostly turn-based boardgames (I have no need for realtime 3D on my tablet).
What would be your recommendations for my next step?
robotneg said:
What would be your recommendations for my next step?
Click to expand...
Click to collapse
Install KattKiss now: https://forum.xda-developers.com/transformer-prime/development/rom-katkiss-nougat-t3459313
Next step, like the rest of us is waiting for Oreo 8
https://www.android.com/versions/oreo-8-0/
NP
djmcnz said:
Install KattKiss now: https://forum.xda-developers.com/transformer-prime/development/rom-katkiss-nougat-t3459313
Click to expand...
Click to collapse
Any how-to guide to follow in order to have the cleanest installation possible?
robotneg said:
Any how-to guide to follow in order to have the cleanest installation possible?
Click to expand...
Click to collapse
What version of TWRP are you currently running?
NP
Nektopoli said:
What version of TWRP are you currently running?
NP
Click to expand...
Click to collapse
Right now, the one that's provided to install Androwook, ie. 2.5.0.0
Here's TWRP 2.8.5.1: https://androidfilehost.com/?fid=95916177934539154
Flash this, once you get into TWRP v2.8.5.1 working you can flash 3.1.0-1 it's an IMG file and 2.5.0.0 won't flash IMG files so you have to upgrade in steps.
TWRP 3.1.0-1 is here: https://androidfilehost.com/?fid=457095661767150802
NP
Nektopoli said:
Here's TWRP 2.8.5.1: https://androidfilehost.com/?fid=95916177934539154
Flash this, once you get into TWRP v2.8.5.1 working you can flash 3.1.0-1 it's an IMG file and 2.5.0.0 won't flash IMG files so you have to upgrade in steps.
TWRP 3.1.0-1 is here: https://androidfilehost.com/?fid=457095661767150802
NP
Click to expand...
Click to collapse
So I did flash TWRP 2.8.5.1 and reboot: okay.
Then I flashed TWRP 3.1.0-1 but now I get a "Unrecoverable bootloader error (0x00000000)" message when I try to reboot in recovery :crying:
What can I do now as I cannot use TWRP anymore to flash anything
robotneg said:
So I did flash TWRP 2.8.5.1 and reboot: okay.
Then I flashed TWRP 3.1.0-1 but now I get a "Unrecoverable bootloader error (0x00000000)" message when I try to reboot in recovery :crying:
What can I do now as I cannot use TWRP anymore to flash anything
Click to expand...
Click to collapse
Tried to use fastboot to flash it again and it worked. Now, going on wiping, formating and flashing the rom.
I had the same problem. Just typing ten letters in a text entry box could take a minute to complete.
Fix was to run Trimmer (fstrim) by AdminseHow from the play store. Sorry I can't link because my account is too new. App is totally free, no ads, no purchases, no begging for donations. It does require root.
It trimmed 185 MB on first run which doesn't sound like a lot but the difference was huge. Can actually use a web browser now. It has an auto-trim feature; be sure to enable this. The default interval (weekly) is fine.
Bloopbloopson, I'm giving fstrim a try.
NP
As usual, this WILL void your warranty and I am NOT responsible for anything you do with this. Installing it properly won't brick your Fire TV, but doing stupid things with it might.
First, you must be unlocked. You can follow the instructions here for making that happen.
If you are first starting, you should first unlock, then install this ROM, and THEN install Magisk for root or any other addons. This rom uses addon.d to preserve Magisk and any other addons, but any system modifications like Magisk, gapps, etc, that you have installed prior to this ROM will NOT be preserved.
If you've already unlocked and installed Magisk, then after installing this ROM you need to reinstall Magisk in TWRP.
Starting with 6.2.6.6, Magisk is always installed.
Beyond that, Magisk and any other addons will be preserved as you flash newer roms. Consequently, if you would like to remove root, you will need to wipe /system in TWRP prior to installing this ROM. That will prevent it from being restored when installing the ROM.
Thanks to @k4y0z and @xyz` for the unlock.
NEVER FLASH A STOCK ROM >= 6.2.8.0 AFTER FLASHING 6.2.8.1_r2 OR LATER! THIS WILL BLOW AN EFUSE.
Changelog and Downloads:
October 24, 2021 - 6.2.8.1_r3 (md5sum: 3795edc2d640932a88da39da8a0811c5)
July 17, 2021 - 6.2.8.1_r2 (md5sum: e9e37a2d485a3397df041938818421e9)
This includes updated tz firmware to fix the device locking up when trying to play video.
April 3, 2021 - 6.2.8.0_r1 (md5sum: 2efdfc5728caba2953a351a082023a59)
December 26, 2020 - 6.2.7.7_r1 (md5sum: b835e29bb29458004063121a422c1bf7)
May 3, 2020 - 6.2.7.1_r1 (md5sum: 56ec885e5bd258682c90e8f08371301d)
November 10, 2019 - 6.2.6.8_r1 (md5sum: 8cdc16239df36c8640004232918c5477)
October 19, 2019 - 6.2.6.6_r1 (md5sum: df8f3d033fddf66a1b4aa3a6b228196b)
Starting with this version, Magisk will always be installed.
This includes updated tz firmware to fix LICENSE_ERROR with Prime video.
October 13, 2019 - 6.2.6.5_r1 (md5sum: bdde0303d8db5495ac6dc2aaf476d2f4)
Awesome!! Thanks!!
@rbox,
Quick question,
Initial unlocking and rooting was successful. However, I did what I usually do which is update Magisk using the manager and after the reboot, it is looping @ the amazon image. Any idea?
vasir13 said:
@rbox,
Quick question,
Initial unlocking and rooting was successful. However, I did what I usually do which is update Magisk using the manager and after the reboot, it is looping @ the amazon image. Any idea?
Click to expand...
Click to collapse
From the unlock page:
Important information
Don't flash boot/recovery images from FireOS (FlashFire, MagiskManager etc.)
rbox said:
From the unlock page:
Important information
Don't flash boot/recovery images from FireOS (FlashFire, MagiskManager etc.)
Click to expand...
Click to collapse
Yes .... I know ... called selective reading .... I got into TWRP and will try your image now ...
Happy to see the pre-rooted roms from you on mantis! It's starting to feel like the good old days again
Thank you, I feel safer already.
Any idea what version of gapps would work on this? Also, any idea if installing nanodroid, patched playstore & patching the ROM for signature spoofing be dangerous (as in bugger up the BL/TWRP)?
Awesome. This community is great.
Does this work for european (Italian) Sticks? (Prime video, Alexa etc etc).
Regards and Thanks a bunch!
Hi,
I successfully installed the hacked bootloader and TWRP a few days ago, but I did not do anything else. I was still on the original 6.2.5.8 version.
Today I wanted to flash the prerooted 6.2.6.5 and I can't manage to boot it (and since I did not expect problems, I did not make a backup of the old system). I cannot go past the "firetv" boot logo and in this stage "adb logcat" is not yet working, so I don't see any logs.
First boot was just installing the ROM. Second boot with previously wiping Cache / Dalvik. Finally I wiped also data (and Cache/Dalvik again). I cannot get past the boot logo.
So what can I do? Was there a firmware update between 6.2.5.8 and 6.2.6.5, which I need and is not included in the prerooted image? I'm just guessing since I cannot explain anything else...
Thanks Tim
tehlers said:
So what can I do? Was there a firmware update between 6.2.5.8 and 6.2.6.5, which I need and is not included in the prerooted image? I'm just guessing since I cannot explain anything else...
Click to expand...
Click to collapse
Have you compared the md5 of the download (push the md5file + ROM and let TWRP check this during install)?
Sus_i said:
Have you compared the md5 of the download (push the md5file + ROM and let TWRP check this during install)?
Click to expand...
Click to collapse
Yes, I have checked MD5 on my notebook after download, but not after pushing the file to the stick. I will do that now and post it here (with edit). But I doubt this being the issue.
EDIT: MD5 of the zip in the stick is also ok.
tehlers said:
EDIT: MD5 of the zip in the stick is also ok.
Click to expand...
Click to collapse
Ok. The prerooted Rom should be a full stock update, rbox said that a few days ago.
Any hardware damages or missing parts on your stick?
Edit: Have you flashed the magisk.zip behind the ROM?
Sus_i said:
Ok. The prerooted Rom should be a full stock update, rbox said that a few days ago.
Any hardware damages or missing parts on your stick?
Click to expand...
Click to collapse
The hardware is fully ok. The installation of hacked BL worked very smoothly and the stick did work with the original firmware until I flashed the prerooted one today. I have two guesses, but I don't know how to proceed:
1. I know there are sometimes firmware updates on specific fire OS versions, which need to be installed for later versions (for example version 5.2.6.7 on fireTV 2 [sloane]). So if I need a firmware update for 6.2.6.5 (from 6.2.5.8) I should probably flash 6.2.5.8 back and let the fire OS do the first update.
2. Or there is something left from the old version (in one of the partitions) which prevents this version from booting. This would mean that you need to be already on 6.2.6.5 (or at least on a higher version than me), that this ROM works.
In both cases, I would probably recover when getting the original firmware version 6.2.5.8 from somewhere.
EDIT: As I said in the first post, I did not do anything with the original ROM, except flashing the hacked BL and TWRP, no Magisk or whatever.
Best
Tim
tehlers said:
The hardware is fully ok. The installation of hacked BL worked very smoothly and the stick did work with the original firmware until I flashed the prerooted one today. I have two guesses, but I don't know how to proceed:
1. I know there are sometimes firmware updates on specific fire OS versions, which need to be installed for later versions (for example version 5.2.6.7 on fireTV 2 [sloane]). So if I need a firmware update for 6.2.6.5 (from 6.2.5.8) I should probably flash 6.2.5.8 back and let the fire OS do the first update.
2. Or there is something left from the old version (in one of the partitions) which prevents this version from booting. This would mean that you need to be already on 6.2.6.5 (or at least on a higher version than me), that this ROM works.
In both cases, I would probably recover when getting the original firmware version 6.2.5.8 from somewhere.
Best
Tim
Click to expand...
Click to collapse
OK :good:
Have you installed the magisk.zip behind the rom? May be it won't start without that? You may try that...
May be that dm-verity and/or SELinux enforcing is a problem without magisk, as magisk take care of that automatically...
No mouse Emulator support in TWRP with the 4K stick?
How do you install the rom if you don't have USB OTG cable?
Sus_i said:
OK :good:
Have you installed the magisk.zip behind the rom? May be it won't start without that? You may try that...
May be that dm-verity and/or SELinux enforcing is a problem without magisk, as magisk take care of that automatically...
Click to expand...
Click to collapse
Yes, that's it. Magisk needs to be installed after the "prerooted" image! Now the stick boots up!
Amazing, thank's!
I thought a prerooted image is prerooted.
@rbox: It would be nice, if you could mention this in the first post.
T1inkering said:
No mouse Emulator support in TWRP with the 4K stick?
How do you install the rom if you don't have USB OTG cable?
Click to expand...
Click to collapse
for example with ADB / TWRP Commands, something like that...
Code:
adb push ~/Desktop/mantis-6.2.6.5-rooted_r1.zip /sdcard/
adb push ~/Desktop/Magisk-v19.3.zip /sdcard/
adb reboot recovery
adb shell
twrp install /sdcard/mantis-6.2.6.5-rooted_r1.zip
twrp install /sdcard/Magisk-v19.3.zip
twrp wipe cache
twrp wipe dalvik
reboot -p
tehlers said:
Yes, that's it. Magisk needs to be installed after the "prerooted" image! Now the stick boots up!
Amazing, thank's!
I thought a prerooted image is prerooted.
@rbox: It would be nice, if you could mention this in the first post.
Click to expand...
Click to collapse
It is mentioned.. but not thats an issue without flashing magisk
Sus_i said:
It is mentioned.. but not thats an issue without flashing magisk
Click to expand...
Click to collapse
That's what I mean. It's not mentioned that you need Magisk in any case (to boot the image as such *and* probably also to get root [which is not prerooted then?]).
Thanks again!
puppinoo said:
Awesome. This community is great.
Does this work for european (Italian) Sticks? (Prime video, Alexa etc etc).
Regards and Thanks a bunch!
Click to expand...
Click to collapse
I reply to myself and happy to confirm I installed this "generic" image to my US Stick 4K and after I accept terms of use *Italian* Alexa and Prime video seem to wotk fine.
If I remember well my previous image was the 6.2.5.8 (basically the one I installed when the exploit for Fire TV Stick 2 (Tank) was released but can't be 100% sure.
Now I have to try it on my *Italian* Stick 4k (bought on amazon.it).
Amazing and thanks a lot again.
Puppinoo.
So great to see @rbox 'es prerooted roms for the Fire TV Stick 4k
There are some things that I am not familiar with:
1. What is magisk for and what if I don't install it?
2. Does root not work without magisk?
On the older Fire TV Devices we did never have to install magisk or so and it was prerooted with rboxes roms and root was working. Why is everybody talking about magisk? Can magisk break anything or be critical like xposed was on the Fire TV 2 box? I remember that xposed framework was a pretty messy issue for recent Fire TV 2 (Sloane) pre-rooted roms. Magisk seems to go deeply into the system, similar to xposed framework, isn't it?