Related
Back story: I recently rooted my Droid Razr (it was my first time rooting an Android phone) and completed it without a hitch. However, the update that was released after I rooted downloaded automatically and I became annoyed with the prompt to install now or later. So I unrooted and installed the update. No problems occurred. Fast forward to this morning. A new update is available (it's been available for about a week now, I'd say) and I go to install it. The phone turns back on and says, "Software update has failed!". I am not currently rooted, I've been too busy to re-root the phone. Now I'd like to install this update. Does anyone have any suggestions on how I'd go about doing this?
Thank you for any replies.
Edit: I apologize in advance if this isn't the appropriate section.
Edit 2: I have another question. Is it possible to update a phone's firmware when they are no longer associated with a carrier. I have an older Android phone I'd like to use as a Wifi only phone for apps and such. Am I able to install updates? It seems like the answer would be no, because the phone wouldn't know where to search for the updates. Perhaps a manual install is available?
Questions belong in Q&A
I apologize in advance if this has been answered or if I have inadvertently offended. I did watch the video and have developed OSes for 30 years. I also have searched all over this site and the web for resolution and am making no progress, so I'm asking the 'oracle'
Got an ATT S4 (I337) a week ago - it was running UCUAMDL. I rooted it using Motochopper and was happily using Titanium Pro etc. I get notified of OTA update. OTA update downloads (357MB) yet fails during install at 30% consistsently.
I figure it is unhappy with my root - I unrooted and cannot remember which way I did it - I seem to recall SuperSU I was using did not have the built-in 'unroot' support so I grabbed the stock image and used ODIN to flash it.I also may have manually uninstalled the 'normal' way the SU app - I suspect this may be my real problem.
After flashing stock ROM for UCUAMDL phone was no longer rooted, did not say custom etc, and took the OTA upgrade just fine. This was for UCUAMF3 which did add App 2 SD support - BTW this update used another 1G of storage compared to UCUAMDL, and I could not recover the 1G by moving apps either, making it virtually worthless as far as adding support for apps in SD, lol.
The problem is now I cannot seem to get the device rooted again. Motochopper fails when installing su.apk. I suspect I have screwed the pooch - what do I need to do to get this thing rooted again?
Is it typical for an OTA update to fail 'because' the device is rooted?
Any advice is much appreciated.
TheKog said:
I apologize in advance if this has been answered or if I have inadvertently offended. I did watch the video and have developed OSes for 30 years. I also have searched all over this site and the web for resolution and am making no progress, so I'm asking the 'oracle'
Got an ATT S4 (I337) a week ago - it was running UCUAMDL. I rooted it using Motochopper and was happily using Titanium Pro etc. I get notified of OTA update. OTA update downloads (357MB) yet fails during install at 30% consistsently.
I figure it is unhappy with my root - I unrooted and cannot remember which way I did it - I seem to recall SuperSU I was using did not have the built-in 'unroot' support so I grabbed the stock image and used ODIN to flash it.I also may have manually uninstalled the 'normal' way the SU app - I suspect this may be my real problem.
After flashing stock ROM for UCUAMDL phone was no longer rooted, did not say custom etc, and took the OTA upgrade just fine. This was for UCUAMF3 which did add App 2 SD support - BTW this update used another 1G of storage compared to UCUAMDL, and I could not recover the 1G by moving apps either, making it virtually worthless as far as adding support for apps in SD, lol.
The problem is now I cannot seem to get the device rooted again. Motochopper fails when installing su.apk. I suspect I have screwed the pooch - what do I need to do to get this thing rooted again?
Is it typical for an OTA update to fail 'because' the device is rooted?
Any advice is much appreciated.
Click to expand...
Click to collapse
I do believe it's because of the latest OTA update. I know the OTA for Verizon patched our bootloader hack that we previously had and I think the same may have happened for AT&T. You might want to check through the AT&T forums section as you have an AT&T S4 and this is the Verizon section. Hope you find what your looking for!
TheKog said:
Any advice is much appreciated.
Click to expand...
Click to collapse
I'd begin with posting in the forum applicable to your device. That being said, in about sure at&t's update was on par with ours
Sent from my Nexus 7 using Tapatalk HD
Hi all,
I'm a bit of a n00b at this, so please forgive me.
I started with Android 4.1.2, Kernel 3.4.0-g298631f-02047-gec59411, build 10.1.C.0.370.
I rooted it using Doomlord's easy-root and then when attempting to flash custom recovery, I accidentally flashed some other .img and the tablet wouldn't even turn on. I cried. Like, a few good tears.
Went online, found out I wasn't screwed, and figured out how to flash SGP312_10.4.B.0.577_VMo DE_1273-3719_WIFI312G.
But, as I said, I lost root, and am confused about how to downgrade back to 4.1.2 properly without bricking.
Here is my current info:
Version 4.3, Kernel 3.4.0-g1b44cd5, build 10.4.b.0.577
In this thread, under "Downgrade your rom" and "back to 4.1.2 and rooting" it says "if you're in 4.3, Flash this SGP 351 4.1.2 FTF using Flash Tool and it will be booted in 4.1.2. if you have different Variant downgrade to your Variant FTF file"
What is a variant FTF file? Can I just use any SGP 312 4.1.2 FTF? Does anyone know a safe one to use?
Thanks!
Just wipe EVERYTHING on flashtools. Make sure that you have al wipe checked, and press start flashing.
But be careful, sometimes, bootloader is messed up with updates, not sure if it is your case because i don't have a SGP312. Instead i have the LTE variant, wich turned itself into an stubborn piece of technology LOL
Sent from my little big badass boy!
worf_1977 said:
Just wipe EVERYTHING on flashtools. Make sure that you have al wipe checked, and press start flashing.
But be careful, sometimes, bootloader is messed up with updates, not sure if it is your case because i don't have a SGP312. Instead i have the LTE variant, wich turned itself into an stubborn piece of technology LOL
Sent from my little big badass boy!
Click to expand...
Click to collapse
Thanks for the response!
Just not sure what you mean by "wipe everything". What am I flashing it with? Which firmware? And what's "al wipe"?
I tried posting a screenshot of the flash tools but as a new user I can't do it. Sorry for being a n00b.
UberBaumer said:
Thanks for the response!
Just not sure what you mean by "wipe everything". What am I flashing it with? Which firmware? And what's "al wipe"?
I tried posting a screenshot of the flash tools but as a new user I can't do it. Sorry for being a n00b.
Click to expand...
Click to collapse
I believe by "wipe everything" and "al wipe", they mean select to wipe APPSLOG, CACHE, and DATA during the flashing process. The flash tool you need can be downloaded from HERE. You can download a US version of the firmware from my post HERE.
Cat McGowan said:
I believe by "wipe everything" and "al wipe", they mean select to wipe APPSLOG, CACHE, and DATA during the flashing process. The flash tool you need can be downloaded from HERE. You can download a US version of the firmware from my post HERE.
Click to expand...
Click to collapse
THANK YOU, SIR.
I really appreciate it!
Back onto 4.1 and just rooted again. Now I just need to manage not screwing up installing CWM like I did last time!
Grrr...so I'm having trouble again.
When I try flashing CWM it keeps soft-bricking or whatever my tablet. It won't boot and I need to put it into fastboot mode and reflash the firmware.
I'm using the command fastboot flash boot TabZ_DooMLoRD_AdvStkKernel_FW-253-v01.img
Is there a better or another way to get CWM installed?
UberBaumer said:
Grrr...so I'm having trouble again.
When I try flashing CWM it keeps soft-bricking or whatever my tablet. It won't boot and I need to put it into fastboot mode and reflash the firmware.
I'm using the command fastboot flash boot TabZ_DooMLoRD_AdvStkKernel_FW-253-v01.img
Is there a better or another way to get CWM installed?
Click to expand...
Click to collapse
TabZ_DooMLoRD_AdvStkKernel_FW-253-v01.img is for the SGP321 running firmware 10.1.1.A.1.253.
You have a SGP312.
TabZ_DooMLoRD_AdvStkKernel_FW-344-v01.img is for the SGP312 running firmware 10.1.C.0.344.
You are running firmware 10.1.C.0.370.
You would probably have better luck trying to install Nut's XZDualRecovery.
Cat McGowan said:
TabZ_DooMLoRD_AdvStkKernel_FW-253-v01.img is for the SGP321 running firmware 10.1.1.A.1.253.
You have a SGP312.
TabZ_DooMLoRD_AdvStkKernel_FW-344-v01.img is for the SGP312 running firmware 10.1.C.0.344.
You are running firmware 10.1.C.0.370.
You would probably have better luck trying to install Nut's XZDualRecovery.
Click to expand...
Click to collapse
Jeez, dude, you're totally rocking my world. Thanks a ton for all your help.
I've successfully installed the XZ DualRecovery.
But now something weird is happening: when I try installing various roms (cm-10.2.0-pollux_windy or cm-11-20140418-nightly-pollux_windy) I get the error that it's for the wrong device. It tells me that I have a Pollux, but according to google, Pollux is the LTE version - I most definitely have the SG312 32GB WiFi version).
Did I go wrong somewhere here?
UberBaumer said:
Jeez, dude, you're totally rocking my world. Thanks a ton for all your help.
I've successfully installed the XZ DualRecovery.
But now something weird is happening: when I try installing various roms (cm-10.2.0-pollux_windy or cm-11-20140418-nightly-pollux_windy) I get the error that it's for the wrong device. It tells me that I have a Pollux, but according to google, Pollux is the LTE version - I most definitely have the SG312 32GB WiFi version).
Did I go wrong somewhere here?
Click to expand...
Click to collapse
I do not install custom ROMs. No ROM has ever impressed me enough to cause me to want to install it. However, I have read posts regarding your problem in the Xperia Tablet Z Original Android Development forum. Look there and perhaps you will find the answer you need.
Cat McGowan said:
I do not install custom ROMs. No ROM has ever impressed me enough to cause me to want to install it. However, I have read posts regarding your problem in the Xperia Tablet Z Original Android Development forum. Look there and perhaps you will find the answer you need.
Click to expand...
Click to collapse
Hmm, I see. I was excited to install Cyanogenmod because I have it on my Samsung Galaxy S3 and enjoy the customization and ability to remove all the bloatware.
According to your signature, I see that you're on 4.2... A few questions:
Did you do this through an official update?
Can I somehow flash 4.2 through recovery mode (so if I decide I don't like it, I can just load a system backup and go back to 4.1.2)?
If I were to update through the automatic system update, I'm assuming I'll lose my root access and won't be able to get back into recovery mode (in case I figure out a way to install a custom rom in the future)?
Is there a way to remove all the sony bloatware without root access (if I were to install an official system update)?
Sorry for all the questions. I'm just trying to get this all figured out before I start downloading all my apps and getting comfortable with the interface.
Thanks again so very much.
UberBaumer said:
Hmm, I see. I was excited to install Cyanogenmod because I have it on my Samsung Galaxy S3 and enjoy the customization and ability to remove all the bloatware.
According to your signature, I see that you're on 4.2... A few questions:
Did you do this through an official update?
Can I somehow flash 4.2 through recovery mode (so if I decide I don't like it, I can just load a system backup and go back to 4.1.2)?
If I were to update through the automatic system update, I'm assuming I'll lose my root access and won't be able to get back into recovery mode (in case I figure out a way to install a custom rom in the future)?
Is there a way to remove all the sony bloatware without root access (if I were to install an official system update)?
Sorry for all the questions. I'm just trying to get this all figured out before I start downloading all my apps and getting comfortable with the interface.
Thanks again so very much.
Click to expand...
Click to collapse
When I first received my XTZ, it was running 4.1.2. I gained root access using DooMLoRD's Easy Rooting Toolkit. I also installed SuperSU Pro and enabled its Survival mode and Install SuperSU into /system settings. Doing that allowed me to update firmware builds via OTA twice without losing root access. I have chosen not to update to 4.3 for various reasons; however, I did attempt updating to 4.3 via OTA like I have in the past, but the update failed to install. And from what I have seen of 4.4.2 on my son's Nexus 7, I may chose not to update to 4.4.2 also. My 4.2.2 install is working flawlessly and my XTZ does everything I need it to do, so I see no reason for updating yet. I live by the aphorism "If it's not broken, don't fix it."
If you install 4.2.2 (via flashing, you can no longer do it via OTA), you can use Vroot - English version to gain root access. Be aware that in the past, Vroot had a bad reputation regarding its loading unwanted apps during the root process, but I believe xda-developers and Mgyun-team (Vroot developers) had a talk and Mgyun-team has since changed their ways. In my opinion, Vroot is now safe to use. Many people have posted saying they have used it and have not experienced any problems.
I do not know of any way to remove bloatware without having root access.
Cat McGowan said:
When I first received my XTZ, it was running 4.1.2. I gained root access using DooMLoRD's Easy Rooting Toolkit. I also installed SuperSU Pro and enabled its Survival mode and Install SuperSU into /system settings. Doing that allowed me to update firmware builds via OTA twice without losing root access. I have chosen not to update to 4.3 for various reasons; however, I did attempt updating to 4.3 via OTA like I have in the past, but the update failed to install. And from what I have seen of 4.4.2 on my son's Nexus 7, I may chose not to update to 4.4.2 also. My 4.2.2 install is working flawlessly and my XTZ does everything I need it to do, so I see no reason for updating yet. I live by the aphorism "If it's not broken, don't fix it."
If you install 4.2.2 (via flashing, you can no longer do it via OTA), you can use Vroot - English version to gain root access. Be aware that in the past, Vroot had a bad reputation regarding its loading unwanted apps during the root process, but I believe xda-developers and Mgyun-team (Vroot developers) had a talk and Mgyun-team has since changed their ways. In my opinion, Vroot is now safe to use. Many people have posted saying they have used it and have not experienced any problems.
I do not know of any way to remove bloatware without having root access.
Click to expand...
Click to collapse
Damn, maybe I was a bit too hasty in rooting my tablet; why is it that I can no longer to OTA updates? If I were to buy SuperSU PRO (for survival mode) is there any benefit to me? I see that it allows for OTA updates.
I am currently rooted via Superuser (by clockworkmod).
When you say I'll need to install 4.2.2 by flashing, you mean through Flashtool, right? Which build should I get (and where, one of the development forums)?
Is the reason why one is advised to install custom roms via recovery mode in order to maintain root access (which I'm assuming doesn't happen if you flash through Flashtool)?
Something I forgot to mention earlier is that I did unlock the bootloader. I'm not sure if that helps or hinders me at this point.
Thanks again for taking the time to answer all my questions. I really love this new toy, and I'm so terrified of bricking it.
Cat McGowan said:
If you install 4.2.2 (via flashing, you can no longer do it via OTA), you can use Vroot - English version to gain root access.
I do not know of any way to remove bloatware without having root access.
Click to expand...
Click to collapse
If I were to say flash this version: http://android.sc/official-android-4-2-2-on-xperia-tablet-z/ I should still be able to install Vroot, right?
Also, do you just manually remove the bloatware yourself, or is there a particular script/app that goes in and cleans up all the unnecessary stuff?
UberBaumer said:
If I were to say flash this version: http://android.sc/official-android-4-2-2-on-xperia-tablet-z/ I should still be able to install Vroot, right?
Also, do you just manually remove the bloatware yourself, or is there a particular script/app that goes in and cleans up all the unnecessary stuff?
Click to expand...
Click to collapse
Android 4.2.2 Jelly Bean 10.3.1.A.0.244 is for the SGP321. You have a SGP312, so you need firmware 10.3.1.C.0.136 (same as mine), which you should be able to download from HERE (upload credit goes to user named spectre51). Flash it then gain root access using Vroot.
Regarding SuperSU Pro versus Superuser, I use Chainfire's SuperSU Pro because it has superior functionality and more options compared to ChainsDD's Superuser. And I use SuperSU Pro because it is more likely to retain root access rights after an OTA update than the free version of SuperSU; e.g., SuperSU Pro provides OTA survival mode, the free version does not.
Regarding uninstalling bloatware, that is something you need to be careful with. Some apps you want to keep have dependencies on apps you consider bloatware and want to uninstall, especially when it concerns system apps. So, investigate the app before you uninstall it. Most times, I use Titanium Backup Pro or ROM Toolbox Pro to uninstall apps that cannot be uninstalled via the Apps list found in the tablet's Settings. At other times, I have had to use a file explorer and text editor to uninstall an app.
Cat McGowan said:
Android 4.2.2 Jelly Bean 10.3.1.A.0.244 is for the SGP321. You have a SGP312, so you need firmware 10.3.1.C.0.136 (same as mine), which you should be able to download from HERE (upload credit goes to user named spectre51). Flash it then gain root access using Vroot.
Regarding SuperSU Pro versus Superuser, I use Chainfire's SuperSU Pro because it has superior functionality and more options compared to ChainsDD's Superuser. And I use SuperSU Pro because it is more likely to retain root access rights after an OTA update than the free version of SuperSU; e.g., SuperSU Pro provides OTA survival mode, the free version does not.
Regarding uninstalling bloatware, that is something you need to be careful with. Some apps you want to keep have dependencies on apps you consider bloatware and want to uninstall, especially when it concerns system apps. So, investigate the app before you uninstall it. Most times, I use Titanium Backup Pro or ROM Toolbox Pro to uninstall apps that cannot be uninstalled via the Apps list found in the tablet's Settings. At other times, I have had to use a file explorer and text editor to uninstall an app.
Click to expand...
Click to collapse
Thank you again my friend.
Is there a list of apps that are safe to uninstall, or, rather, a list of apps that I shouldn't tinker with (for fear of uninstalling an app that has a dependency on something critical)?
Also, I'm on the Google Play store and I see both Titanium Backup Pro and Rom Toolbox Pro. Should I buy both? If you had to buy just one, which would it be?
My main goal is to just make the smoothest experience possible. I want to take maximum advantage of the hardware in the tablet and have as few unnecessary programs running as possible.
I did root Amazon Kindle HDX THOR successfully with: [TOOL] HDX ToolKit v0.94:ROOT UPDATE
http://forum.xda-developers.com/showthread.php?t=2665683
And I disabled the air updates according to the instructions. Later I tried to reset the update to 13.3.1.0.
http://forum.xda-developers.com/showthread.php?t=2782159&page=10
It worked allright, until I tried to do the manuel update. But because I disabled air update earlier, Amazon Kindle couldn't find any update the manual update failed. How do I do to enable the update again, is there anything else I can do to solve this?
Is it possible to reset to 13.3.2.3.2 again?
Thanks!
umm
Atise said:
I did root Amazon Kindle HDX THOR successfully with: [TOOL] HDX ToolKit v0.94:ROOT UPDATE
http://forum.xda-developers.com/showthread.php?t=2665683
And I disabled the air updates according to the instructions. Later I tried to reset the update to 13.3.1.0.
http://forum.xda-developers.com/showthread.php?t=2782159&page=10
It worked allright, until I tried to do the manuel update. But because I disabled air update earlier, Amazon Kindle couldn't find any update the manual update failed. How do I do to enable the update again, is there anything else I can do to solve this?
Is it possible to reset to 13.3.2.3.2 again?
Thanks!
Click to expand...
Click to collapse
Rerun the tool kit it has a reenable option. Just out of curiosity did you ask this question back in the HDX utility thread? Nevermind it might not of let you post their.
Anyway if as long as you are using version .94 should work fine for you. And make sure that you have Wi-Fi disabled and even forget your network as you are planning on doing a manual update. If you plan on trying to rollback we advised not to at this time just wait till safestrap is updated and works with the newest firmware... Way too many people are breaking their devices by trying to do the build prop modifications necessary to do these manual updates.. If you want the latest firmware just let it up to Wi-Fi nHit check for updates then you can wipe it root it or whatever... But just to let you know currently safestrap does not work on newest firmware..yet. Just do your homework because there are a ton of brick devices right now that are getting sent in for BS warranty claims.. And I have to emphasize yet again there is no easy way to recover this device at this time if you mess something up unless you are using safestrap and on slot 1 ect...NO fastboot capabilities at this time..And bootloader is locked
Thanks
jimyv said:
Rerun the tool kit it has a reenable option. Just out of curiosity did you ask this question back in the HDX utility thread? Nevermind it might not of let you post their.
Anyway if as long as you are using version .94 should work fine for you. And make sure that you have Wi-Fi disabled and even forget your network as you are planning on doing a manual update. If you plan on trying to rollback we advised not to at this time just wait till safestrap is updated and works with the newest firmware... Way too many people are breaking their devices by trying to do the build prop modifications necessary to do these manual updates.. If you want the latest firmware just let it up to Wi-Fi nHit check for updates then you can wipe it root it or whatever... But just to let you know currently safestrap does not work on newest firmware..yet. Just do your homework because there are a ton of brick devices right now that are getting sent in for BS warranty claims.. And I have to emphasize yet again there is no easy way to recover this device at this time if you mess something up unless you are using safestrap and on slot 1 ect...NO fastboot capabilities at this time..And bootloader is locked
Click to expand...
Click to collapse
Thank you for your help!
Atise said:
Thank you for your help!
Click to expand...
Click to collapse
My advise, don't try rolling back, most likely you will brick your device. Search for an app called kindlefree if Google play is what you want.
btw, thank you for posting in Q&A.
Hello,
I have this Kindle Fire HDX with Fire O.S. 4.5.3
I can't see the firmware version in settings, any alternative in order to find it?.
What would the basic steps to follow in order to be able to install a ROM?
I'm not asking for instruction for each step, I can search for that, I'm just hoping to get a comprehensive step by step.
I'd guess I need to root first, but in order to root I need to have certain OS and/or firmware version, therefore I'll need to rollback?
Then what would be next?
peterpayne said:
Hello,
I have this Kindle Fire HDX with Fire O.S. 4.5.3
I can't see the firmware version in settings, any alternative in order to find it?.
What would the basic steps to follow in order to be able to install a ROM?
I'm not asking for instruction for each step, I can search for that, I'm just hoping to get a comprehensive step by step.
I'd guess I need to root first, but in order to root I need to have certain OS and/or firmware version, therefore I'll need to rollback?
Then what would be next?
Click to expand...
Click to collapse
I found how to rollback to version 13.3.2.8, and did the towelroot root... with the KFHDX ToolKit v0.95
But it seems there's no way currently to install a bootloader unless I have 13.3.1.0 and I haven't seen if there's a way to rollback further.
If I find a way, I'll post again I guess...
I for one have many of the same questions you are asking. I honestly have done a decent amount of research on this, having successfully rooted and installed custom ROMs and recovery on my HTC One M8, I feel I have the basics down.
So if you learn more please share, and I also would like to know how you found your firmware info?
, kk,
Sent from my SM-G355HN using XDA Free mobile app
I just got an HDX 7 (3rd gen) today for free, been mucking around with it for the past few hours (it's a piece of crap, really) and kinda pissed at Amazon (nothing new for me considering).
Here's what I've gleaned so far in a few hours of research... and please understand that since the OP said he's already on 4.5.3 this info is specifically related to what can be done with an HDX running 4.5.3.
What you can't do: If you're on 4.5.3 forget doing anything at all - you can't root it, you can't install custom ROMs (no Safestrap use at all), you can't unlock the bootloader, you can't do a damned thing, period. Well, you could use it like Amazon wants you to use it: a consumption device overall but that's not why we're here at XDA basically so there goes that ridiculous idea. (note this information applies to 4.5.3 specifically and nothing else)
What you can do: The only thing you CAN do if you're on 4.5.3 is to roll it back to 3.2.8 using the 3.2.8 firmware bin copied to the storage root (you can find that yourself someplace, I did but I don't have the particular link to that particular thread at the moment).
Once you're on 3.2.8 you CAN root it (I don't have the thread for that at the moment, I think the HDX Toolkit or whatever can do it using Towelroot or something). At that point you can stick with 3.2.8 and do whatever (disable OTA's, etc) - I believe you can install Safestrap as well and then install that Nexus ROM I see mentioned but that's Jelly Bean based and CM11 and CM12/12.1 cannot be used presently - the best you'll ever be able to do with 3.2.8 is running the Nexus ROM as I understand things (I could be wrong on that, someone else can chime in as needed).
Another thing you can do once you're on 3.2.8: you CAN update it to 4.5.2 using the 4.5.2 firmware bin copied to the storage root (again, you'll have to find this yourself) and 4.5.2 CAN be rooted but that's where you're stuck because you can't install Safestrap or any custom ROMs at all (not even the Nexus one), but you can kill off the OTA updates and stay with 4.5.2 as long as you want because if you don't it will update to 4.5.3 again the first chance it gets.
I didn't know all this about 6 hours ago, I got the HDX and it had 3.0.5 on it - I didn't know not to update it - well, yes, I did, but I forgot about the WiFi thing and as soon as I realized that the update had downloaded it was already too late - as soon as I rebooted it installed and I couldn't stop it from happening so that ruined my ability to do the bootloader unlock and potentially get CM12.1 on it. My fault, my mistake, but that's what happens sometimes.
As it stands I don't even want this piece of crap to be honest, I find it useless overall unless you can do custom ROMs 'cause Amazon and FireOS just flat out suck for me - if I can't do what I want with the device then I can't use it, basically, so it's listed on craigslist for sale at the moment and I hope someone grabs it quick.
That's the gist of what I've learned in the past few hours with respect to this HDX device and doing an awful lot of reading and research not only here at XDA but MobileRead and some other places.
Hope this helps...
br0adband said:
I just got an HDX 7 (3rd gen) today for free, been mucking around with it for the past few hours (it's a piece of crap, really) and kinda pissed at Amazon (nothing new for me considering).
Here's what I've gleaned so far in a few hours of research... and please understand that since the OP said he's already on 4.5.3 this info is specifically related to what can be done with an HDX running 4.5.3.
What you can't do: If you're on 4.5.3 forget doing anything at all - you can't root it, you can't install custom ROMs (no Safestrap use at all), you can't unlock the bootloader, you can't do a damned thing, period. Well, you could use it like Amazon wants you to use it: a consumption device overall but that's not why we're here at XDA basically so there goes that ridiculous idea. (note this information applies to 4.5.3 specifically and nothing else)
What you can do: The only thing you CAN do if you're on 4.5.3 is to roll it back to 3.2.8 using the 3.2.8 firmware bin copied to the storage root (you can find that yourself someplace, I did but I don't have the particular link to that particular thread at the moment).
Once you're on 3.2.8 you CAN root it (I don't have the thread for that at the moment, I think the HDX Toolkit or whatever can do it using Towelroot or something). At that point you can stick with 3.2.8 and do whatever (disable OTA's, etc) - I believe you can install Safestrap as well and then install that Nexus ROM I see mentioned but that's Jelly Bean based and CM11 and CM12/12.1 cannot be used presently - the best you'll ever be able to do with 3.2.8 is running the Nexus ROM as I understand things (I could be wrong on that, someone else can chime in as needed).
Another thing you can do once you're on 3.2.8: you CAN update it to 4.5.2 using the 4.5.2 firmware bin copied to the storage root (again, you'll have to find this yourself) and 4.5.2 CAN be rooted but that's where you're stuck because you can't install Safestrap or any custom ROMs at all (not even the Nexus one), but you can kill off the OTA updates and stay with 4.5.2 as long as you want because if you don't it will update to 4.5.3 again the first chance it gets.
I didn't know all this about 6 hours ago, I got the HDX and it had 3.0.5 on it - I didn't know not to update it - well, yes, I did, but I forgot about the WiFi thing and as soon as I realized that the update had downloaded it was already too late - as soon as I rebooted it installed and I couldn't stop it from happening so that ruined my ability to do the bootloader unlock and potentially get CM12.1 on it. My fault, my mistake, but that's what happens sometimes.
As it stands I don't even want this piece of crap to be honest, I find it useless overall unless you can do custom ROMs 'cause Amazon and FireOS just flat out suck for me - if I can't do what I want with the device then I can't use it, basically, so it's listed on craigslist for sale at the moment and I hope someone grabs it quick.
That's the gist of what I've learned in the past few hours with respect to this HDX device and doing an awful lot of reading and research not only here at XDA but MobileRead and some other places.
Hope this helps...
Click to expand...
Click to collapse
This is a reasonably accurate accounting of the current state for those starting at 4.5.3. A minor footnote is the ability to install Google Play Services on 4.5.2 once rooted. That makes the device a bit more intersting as most apps in the Play Store will happily run on Fire 4.5.2. However, there is both effort and risk going this route. A safer alternative is to utilize an alternative market such as 1mobile to secure free (and some paid) content offered in the Play Store.
br0adband said:
I just got an HDX 7 (3rd gen) today for free, been mucking around with it for the past few hours (it's a piece of crap, really) and kinda pissed at Amazon (nothing new for me considering).
Here's what I've gleaned so far in a few hours of research... and please understand that since the OP said he's already on 4.5.3 this info is specifically related to what can be done with an HDX running 4.5.3.
What you can't do: If you're on 4.5.3 forget doing anything at all - you can't root it, you can't install custom ROMs (no Safestrap use at all), you can't unlock the bootloader, you can't do a damned thing, period. Well, you could use it like Amazon wants you to use it: a consumption device overall but that's not why we're here at XDA basically so there goes that ridiculous idea. (note this information applies to 4.5.3 specifically and nothing else)
What you can do: The only thing you CAN do if you're on 4.5.3 is to roll it back to 3.2.8 using the 3.2.8 firmware bin copied to the storage root (you can find that yourself someplace, I did but I don't have the particular link to that particular thread at the moment).
Once you're on 3.2.8 you CAN root it (I don't have the thread for that at the moment, I think the HDX Toolkit or whatever can do it using Towelroot or something). At that point you can stick with 3.2.8 and do whatever (disable OTA's, etc) - I believe you can install Safestrap as well and then install that Nexus ROM I see mentioned but that's Jelly Bean based and CM11 and CM12/12.1 cannot be used presently - the best you'll ever be able to do with 3.2.8 is running the Nexus ROM as I understand things (I could be wrong on that, someone else can chime in as needed).
Another thing you can do once you're on 3.2.8: you CAN update it to 4.5.2 using the 4.5.2 firmware bin copied to the storage root (again, you'll have to find this yourself) and 4.5.2 CAN be rooted but that's where you're stuck because you can't install Safestrap or any custom ROMs at all (not even the Nexus one), but you can kill off the OTA updates and stay with 4.5.2 as long as you want because if you don't it will update to 4.5.3 again the first chance it gets.
I didn't know all this about 6 hours ago, I got the HDX and it had 3.0.5 on it - I didn't know not to update it - well, yes, I did, but I forgot about the WiFi thing and as soon as I realized that the update had downloaded it was already too late - as soon as I rebooted it installed and I couldn't stop it from happening so that ruined my ability to do the bootloader unlock and potentially get CM12.1 on it. My fault, my mistake, but that's what happens sometimes.
As it stands I don't even want this piece of crap to be honest, I find it useless overall unless you can do custom ROMs 'cause Amazon and FireOS just flat out suck for me - if I can't do what I want with the device then I can't use it, basically, so it's listed on craigslist for sale at the moment and I hope someone grabs it quick.
That's the gist of what I've learned in the past few hours with respect to this HDX device and doing an awful lot of reading and research not only here at XDA but MobileRead and some other places.
Hope this helps...
Click to expand...
Click to collapse
Thanks, but at what point can you actually unlock the bootloader? If you have 4.5.2 (never updated to 4.5.3), are you able to downgrade far enough to unlock the bootloader, or what? Is 4.5.3 essentially the cutoff point?
3.2.7 was the cutoff point. Sorry.
Sent from my KFTHWI using Tapatalk