[Q] basic question on safestap (apollo 3.2.5) - Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot

Okay, I managed to get root, supersu, and whatnot up and running (thanks to people in these forums). I then went for the safestrap route.
My new issue is this - I click on "install recovery" - and that seems to work fine. I get notification that it's been installed, and the "State: Installed" status updates. It appears the next step would be to reboot so I have a boot menu, or at least another set of options. The only choice available in safestrap itself is "reboot to recovery". If I choose this, the device reboots to the grey logo, then the screen goes mostly black (powered up, back lit, but dark), and stays that way. I can hold power to turn off and then re-power up to reset (I assume to reboot into the stock rom slot).
Obviously I'm missing something, but I'm not sure what step I might have skipped. To anticipate some questions, I'm on 14.3.2.5, and I used HDX Toolkit v0.95 to root and install safestrap. I did have some difficulty in getting my system to recognize the device as an android adb one, but eventually I got a driver installed that worked.

begalund said:
Okay, I managed to get root, supersu, and whatnot up and running (thanks to people in these forums). I then went for the safestrap route.
My new issue is this - I click on "install recovery" - and that seems to work fine. I get notification that it's been installed, and the "State: Installed" status updates. It appears the next step would be to reboot so I have a boot menu, or at least another set of options. The only choice available in safestrap itself is "reboot to recovery". If I choose this, the device reboots to the grey logo, then the screen goes mostly black (powered up, back lit, but dark), and stays that way. I can hold power to turn off and then re-power up to reset (I assume to reboot into the stock rom slot).
Obviously I'm missing something, but I'm not sure what step I might have skipped. To anticipate some questions, I'm on 14.3.2.5, and I used HDX Toolkit v0.95 to root and install safestrap. I did have some difficulty in getting my system to recognize the device as an android adb one, but eventually I got a driver installed that worked.
Click to expand...
Click to collapse
Thanks documenting so clearly. Unfortunately, having never used Safestrap (know just enough to be dangerous ...) I can't confidently answer your question but I'm sure someone with more experience will jump in.
Question: Why did you opt for Safestrap instead of twrp? It is a simple matter to downgrade to 14.3.1.0, reroot and then install twrp. From there you can stick with stock or install several different roms including nexus and CM11/12. Now, if you prefer rooted stock Fire OS then 3.2.5 and safestrap makes sense (although safestrap isn't necessary it does offer a more robust recovery...albeit not as rich/powerful as twrp). Thanks for taking time to respond; just trying to better understand people's choices as it may help others in similar circumstances.

Davey126 said:
Question: Why did you opt for Safestrap instead of twrp? It is a simple matter to downgrade to 14.3.1.0, reroot and then install twrp. From there you can stick with stock or install several different roms including nexus and CM11/12. Now, if you prefer rooted stock Fire OS then 3.2.5 and safestrap makes sense (although safestrap isn't necessary it does offer a more robust recovery...albeit not as rich/powerful as twrp). Thanks for taking time to respond; just trying to better understand people's choices as it may help others in similar circumstances.
Click to expand...
Click to collapse
Well, since I'm just learning, the SS route seemed easier to not screw up - I had less to do, so I had far fewer chances of ending up with a shiny paperweight. It also seemed to be reversible, so I could learn and then maybe go with the option you quoted above.
However, if I can't seem to make this part work, maybe I'll just skip the in-between step.

begalund said:
Well, since I'm just learning, the SS route seemed easier to not screw up - I had less to do, so I had far fewer chances of ending up with a shiny paperweight. It also seemed to be reversible, so I could learn and then maybe go with the option you quoted above.
However, if I can't seem to make this part work, maybe I'll just skip the in-between step.
Click to expand...
Click to collapse
Yep - makes a ton of sense. Wish everyone acted with your restraint. You'll do fine. Keep reading, watch for gotchas, post questions. Sorry for your Safestrap troubles. It works well for many/most so it sounds like a unique problem with (hopefully) an easy fix.

While I awaited a further reply, I decided to at least see about starting the next steps towards your approach. I downloaded the apollo gapps apks, got them installed, got my account loaded, but the app just keeps stopping immediately after start up. Makes it difficult to grab the prop editor to do a rollback unless there is another way to install that.
I'm currently looking into fixes for gapps, but not finding what I need yet. And yes, this is just the apks and not the rom - since I haven't gotten safestrap fixed, and haven't (obviously) moved on to the alt version, I haven't attempted flashing roms yet.
Update:
So, nevermind. I figured that part out. I was dumb and installed the apks as r/o and not r/w. live and learn (and don't brick I guess).

Related

[Q] Prompted daily for same OTA update?

I have a stock rom evo 4g LTE, rooted, with Android 4.0.3 on it.
I forget the root app I used, some one click thingy, I guess my bootloader is unlocked
because I get a boot menu every time I reboot, on that screen that says **TAMPERED**.
Anyway, I ignored the notification icon in my taskbar for OTA updates, for a very long time.
Since the day I bought it over a year ago.
Finally I decided "eh, screw it, why not." ...I'm sure I'll regret that.
I told it to do the OTA update, and it downloaded (I think??) and rebooted.
The icon went away. Seemed to be a done deal.
But once per day since then, my phone rings, and I see a prompt saying
there's an OTA update, and would I like to install it now?
I think it's the same OTA update being prompted repeatdly,
because the filesize is always the same (~42 megs).
What should I do? I can choose install, reboot, and be fine for the rest of the day,
or choose cancel, reboot, and be fine for the rest of the day.
Doesn't seem to matter. But would be nice to fix it for good.
Well, considering that you are about 4-5 OTAs behind the rest of the community, I would say that the notification is probably correct. HOWEVER, of you are not using the stock recovery, then the OTA did not flash. Yes, the phone rebooted, but that's because it is installed entirely through recovery, and the phone has to reboot to get into recovery mode in the first place.
Now, for the more important question at hand....why exactly are you still using ICS? Furthermore, if you are still using ICS, then why are you rooted? As far as I'm concerned, the OTAs are actually necessary updates for the phone. I'm sure that you will love Jelly Bean if you have never used it before.
And please, for the sake of us all who are cringing at the sight of the first sentence....PLEASE UPDATE your phone! If you have a good reason not to, please share.
Hi, thanks for the reply... Maybe they were all different updates after all.
I haven't been prompted to update again since my post.
Maybe I grabbed the 3 or 4 OTA updates that I needed to catch up on.
I do think I'd like Jelly Bean too, seeing some of the features is what prompted me to finally catch up.
Can you explain this part to me? I'm not familiar with this stuff.
HOWEVER, of you are not using the stock recovery, then the OTA did not flash.
Yes, the phone rebooted, but that's because it is installed entirely through recovery,
and the phone has to reboot to get into recovery mode in the first place.
Click to expand...
Click to collapse
So, there's more than one recovery mode, the stock one, and ...whatever else you can install?
When I see the white screen that says **TAMPERED** (looks basically like this screen)...
should I have chosen Recovery instead of the usual reboot option?
If I no longer see the notification, does that mean the updates worked? My Android version still shows 4.0.3.
why exactly are you still using ICS? Furthermore, if you are still using ICS, then why are you rooted?
Click to expand...
Click to collapse
Well, I had no compelling reason to upgrade. I still don't really, the phone does what I want,
I just saw some of the features in the next version and thought "huh, that sounds pretty cool".
I'm rooted for all the usual reasons... I want to be able to browse, copy, move, rename files (including system files)
without incident... use nandroid for backups... wifi tether (still can't get that to work actually)... install unapproved apps...
tweak the OS, and so on.
Ok, my friend...let me educate you. Instead of giving you the simplest, fastest solution, I will actually try to answer all of your questions, since you did ask.
I do think I'd like Jelly Bean too, seeing some of the features is what prompted me to finally catch up.
Can you explain this part to me? I'm not familiar with this stuff.
Click to expand...
Click to collapse
To give a very superficial explanation of Jelly Bean, it is everything that ICS does, and more. It just does it smoother. It also brings Google Now, which was – and still is – the selling point of Jelly Bean. The Sense launcher got a few changes, too, but you will have to explore those changes on your own (mainly because I don’t remember them off hand, and this post is beginning to become lengthy).
Maybe I grabbed the 3 or 4 OTA updates that I needed to catch up on.
If I no longer see the notification, does that mean the updates worked? My Android version still shows 4.0.3.
Click to expand...
Click to collapse
If the first update didn’t update properly, then the phone is simply downloading and trying to install the same update over and over. When you boot back into Android after a successful update, you will be greeted by a welcome message congratulating you for installing the new version.
If you are rooted, odds are, you are using a custom recovery, such as TWRP or CWM. OTAs are only installed through the stock recovery & a locked bootloader. The stock recovery doesn’t make nandroids, or do anything of the sort. To install the stock recovery, go here:
http://downloadandroidrom.com/file/HTCEvo4GLTE/rooting/Evo4GLTERoot2.zip
Click to expand...
Click to collapse
The stock recovery is located somewhere within the zip file.
So, there's more than one recovery mode, the stock one, and ...whatever else you can install?
When I see the white screen that says **TAMPERED** (looks basically like this screen)...
should I have chosen Recovery instead of the usual reboot option?
Click to expand...
Click to collapse
You can flash install the stock recovery by using fastboot commands from the bootloader (which is the screen that shows the TAMPERED status on the top), or you can use Flash Image GUI. It is a paid app on the Play Store, or you can get it from XDA (the dev let XDA users download it for free…Google it).
Lastly, there are a few things that I suggest that you do. First, obtain S-Off (Google, Google, Google...very simple), so you can install the new firmwares directly, instead of using OTAs. Otherwise, if you accept the OTA, you will lose root, and you will have to root your phone again and again. Installing the firmware, then the new rom is the same as accepting the OTA, then rooting.
Another alternative is to get S-Off, then accept the OTA (after installing the stock recovery). Your bootloader does not need to be locked, and there are recovery zips floating around here that can be installed through the bootloader (therefore, you will not be stuck rooting the phone the hard way, just boot into recovery and flash SuperSU). I highly suggest achieving S-Off.
If you want to jump straight to the latest version (Android 4.3, Sense 5.0) by installing the RUU located somewhere in this forum. I actually suggest that you try Sense 4 with Jelly Bean first, but that is completely up to you. Keep in mind that using the RUU will wipe your internal memory, so back up what needs to be backed up. This doesn’t require you to be rooted, and the state of the bootloader does not matter. It will lock the bootloader, load the stock recovery, and you will lose root. You won’t be able to downgrade without S-Off.
Other Notes:
When using the 4.3 RUU, make sure that Android USB Debugging is enabled.
Bookmarking for later but I wanted to say thanks for the thorough reply!
I can confirm the update never worked, because I never got the confirmation message
and I got prompted again a few hours after I posted.
Are you willing to answer just a few more things?
Based on what I've read, it sounds like this is what I ought to do:
- Back up anything I need to. Just to confirm, updating firmware and flashing a new rom wipes out everything in the phone's internal memory, but not external SDcard? Or both?
Are apps considered "on the cloud" and I can reinstall by just redownloading, without paying again?
Except sideloaded apps? Or will I need to find all those APK files and save them somewhere else?
Is it safe to say they're all in \data\app and \system\app? Or would system\app be unwanted since it's what came with the old phone OS?
- Get my phone into S-OFF status.
- Update firmware (this is a separate process from updating the rom? Where do I get this firmware? Google google google?)
- Install a new ROM (stock or otherwise) which will have these updates built in, so I won't need to regain root.
- Not sure what my bootloader is, maybe TWRP, does it matter? Do the above steps affect it? Should I change it to stock anyway?
- You suggested trying Sense 4 rather than Sense 5 first... any special reason?
Are you willing to answer just a few more things?
Click to expand...
Click to collapse
As always, I'm open for questions. Not to sound egotistic, but I enjoy sharing my opinion.
Based on what I've read, it sounds like this is what I ought to do:
- Back up anything I need to. Just to confirm, updating firmware and flashing a new rom wipes out everything in the phone's internal memory, but not external SDcard? Or both?
Updating to the 4.3 firmware wipes your internal memory, not your sd card (although, that may be a very unfortunate circumstance, so it should be backed up as well). The other firmware updates do not affect your memory.
Are apps considered "on the cloud" and I can reinstall by just redownloading, without paying again?
Technically, yes they are "on the cloud." The fact that you paid is saved somewhere within your main Google account that you downloaded the app with. It is possible to pay for apps with your secondary gmail account, which can be switched within the Play Store app.
Except sideloaded apps? Or will I need to find all those APK files and save them somewhere else?
Use Titanium Backup if you can't find the apks. I do save my apks that I download, and I also upload them to Google Drive, since I have multiple Android devices, and I also have a faulty micro sd card that I am yet to replace. I can lose my data at any given moment, but everything is backed up, so I'm not worried.
Is it safe to say they're all in \data\app and \system\app? Or would system\app be unwanted since it's what came with the old phone OS?
Everything within the /system folder is wiped when you flash new roms. That data is NOT backed up while flashing between roms. Also, since it is from an older Android version, it's best to leave them alone. You may back up the data if you like, but I would refrain from restoring the apks along with the data.
The /data directory may be wiped, depending on the dev who built the rom zip. If they added the superwipe script, then /data will be wiped as well. Most devs do not include this, since many people "dirty flash," which is flashing new roms or updates of the current rom without wiping /data first.
- Get my phone into S-OFF status.
You will save yourself a LOT of headaches in the future. It was my S-Off status that allowed me to reflash my firmware when I lost the function of my data/voice antennas while carelessly flashing a port of a phone on a different carrier. Also, if you feel curious to try AOSP roms, then you do not need to do any extra steps to flash them.
- Update firmware (this is a separate process from updating the rom? Where do I get this firmware? Google google google?)
Yes, the firmware handles manages how the hardware of the phone operates. Updating the rom changes how the software looks and behaves. The kernel is sort of a bridge between the firmware and the software, since it manages the firmware (like battery life, processor speed, antennas, etc.), but the kernel is dependent on the software version. The firmware is not dependent on the software version, just as the software version is not dependent on the firmware version.
The only exception of the firmware/software independence is the 4.3 update, which requires a complete update of the firmware, and the older software cannot run on the new firmware without being modded by a dev.
- Install a new ROM (stock or otherwise) which will have these updates built in, so I won't need to regain root.
- Not sure what my bootloader is, maybe TWRP, does it matter? Do the above steps affect it? Should I change it to stock anyway?
Your bootloader is the white screen that shows the TAMPERED status on the top, and little Androids on skateboards on the bottom. With the exception of the firmware information in the top left corner, this screen does not change...ever.
TWRP is your recovery image, which is accessible through the RECOVERY option in your bootloader, or you can boot directly into it through different apps in Android - Titanium Backup is one of them (yes, that's one of the options, even for the free version).
The only reason to return your recovery to stock is to accept OTAs, and also to bring your phone back to the complete factory settings, just as the day when it was first purchased (for the sake of selling the phone, or returning back to Sprint for service}. Otherwise, don't bother with it. You may want to update your version of TWRP, though. If you update to 4.3, you will have to update it. I'm not going to take the time to get into that right now. I've given you enough homework.
- You suggested trying Sense 4 rather than Sense 5 first... any special reason?
I am a very patient person. To me, exploring Android takes time. I enjoy reading before I test, and testing before I settle (which I'm yet to "settle"). All of that being said, I suggested Sense 4 before Sense 5 because I wanted you to experience the both of them. They are truly two different versions of Sense, which one might not realize, as their version numbers are differentiated by one integer (in other words, 4 to 5). Sense 3 was a small step above Sense 2, and Sense 4 was a bigger step from Sense 3. Sense 5 is a complete overhaul of the Sense UI, save the flip clock.
I just feel that skipping from 4.0 to 4.3 is missing out on a great experience, but that is mainly if you actually want to try out different roms. Until the Sense 5 RUU, I still visiting ICS on occassion, but I usually didn't last more than 3 hours before I jumped back to JB.
Click to expand...
Click to collapse
Whew...you're making me work. But I like it. Anymore questions? Feel free to ask.
OK I've been working on this all afternoon and I'm at an impasse.
You've been a huge help so far and I hope you can guide me through this part.
I want to S-OFF and am following a tutorial: http://www.thefortressofnerditude.com/s-off-your-sprint-htc-evo-4g-lte/
Step 3 says root and install recovery. So I decide I need TWRP.
Already have nandroid and titanium backups both completed.
And I copied the whole SDcard to my computer after.
Annoyingly, TWRP's install page suggests that I need to be in S-OFF.
TWRP says I need S-OFF. S-OFF guide seems to suggest I need TWRP working.
I installed "TWRP Manager". Realize that might not be the same thing as TWRP.
Googled and found it on the TeamWin page.
The page asks first to input my device. I choose Evo 4G LTE (Jewel).
That brings me to this page: http://teamw.in/project/twrp2/98
They suggest I do the android app install method. I follow the first link (Market Link)
and install GooManager, and follow their steps.
Install the app and open it. Tap menu then hit Install OpenRecoveryScript. Tap Yes. Verify that the filename displays your device's code name and hit Yes. The file will download and your device will reboot and install the recovery automatically.
This all goes smoothly, but here's my issue.
It doesn't reboot automatically, or install anything automatically.
I see in the comments a recommendation to reboot into recovery mode.
I choose that in GooManager's menu, and after rebooting I get my bootloader screen with 4 menu options:
Bootloader
Reboot
Reboot Bootloader
Power Down
The only one that sounds sensible to me is bootloader so I pick that.
Now I get some new options:
Fastboot
Recovery
Factory Reset
Clear Storage
Simlock
Image CRC
Show Barcode
So, the only one that makes sense is Recovery. I choose it. The phone reboots.
Now I'm back at the first menu. So I'm in a loop.
Nothing I do in this loop seems to install anything.
So I just rebooted the phone normally and I'm back to my OS.
Where to go from here?
CreeDo said:
OK I've been working on this all afternoon and I'm at an impasse.
You've been a huge help so far and I hope you can guide me through this part.
I want to S-OFF and am following a tutorial: http://www.thefortressofnerditude.com/s-off-your-sprint-htc-evo-4g-lte/
Step 3 says root and install recovery. So I decide I need TWRP.
Already have nandroid and titanium backups both completed.
And I copied the whole SDcard to my computer after.
Annoyingly, TWRP's install page suggests that I need to be in S-OFF.
TWRP says I need S-OFF. S-OFF guide seems to suggest I need TWRP working.
I installed "TWRP Manager". Realize that might not be the same thing as TWRP.
Googled and found it on the TeamWin page.
The page asks first to input my device. I choose Evo 4G LTE (Jewel).
That brings me to this page: http://teamw.in/project/twrp2/98
They suggest I do the android app install method. I follow the first link (Market Link)
and install GooManager, and follow their steps.
Install the app and open it. Tap menu then hit Install OpenRecoveryScript. Tap Yes. Verify that the filename displays your device's code name and hit Yes. The file will download and your device will reboot and install the recovery automatically.
This all goes smoothly, but here's my issue.
It doesn't reboot automatically, or install anything automatically.
I see in the comments a recommendation to reboot into recovery mode.
I choose that in GooManager's menu, and after rebooting I get my bootloader screen with 4 menu options:
Bootloader
Reboot
Reboot Bootloader
Power Down
The only one that sounds sensible to me is bootloader so I pick that.
Now I get some new options:
Fastboot
Recovery
Factory Reset
Clear Storage
Simlock
Image CRC
Show Barcode
So, the only one that makes sense is Recovery. I choose it. The phone reboots.
Now I'm back at the first menu. So I'm in a loop.
Nothing I do in this loop seems to install anything.
So I just rebooted the phone normally and I'm back to my OS.
Where to go from here?
Click to expand...
Click to collapse
Did you unlock your boot loader first? You don't need to be S-off to install a custom recovery. Unlock your bootloader at htcdev.com then install twrp.
Read here for more info:
http://forum.xda-developers.com/showthread.php?t=2420916
Also, I suggest learning how to use fastboot commands. Install twrp using fastboot.
Sent from my EVO using XDA Premium 4 mobile app
OK, so I'm semi-bricked but not panicking yet.
Here's where I'm at.
• Unlocked boot loader successfully
• Installed TWRP using fastboot.
• Followed instructions as closely as I could on moonshine.io to get S-OFF working.
Several times during the process I got "installing device driver software" in my win7 system tray.
Not sure if that's normal. But the drivers seemed to install fine. At first.
But then, during this part of the process:
Moonshining .................(1)
Windows prompted me that it was installing some drivers again, But it failed to install the MTP driver.
After ten tries with the "Moonshining" step, I got "ERROR: don't drink and moonshine!" or something like that.
So, it seems like I need to get this MTP driver going. First I tried solutions on the computer:
• Uninstalled all HTC software, unplugged phone, rebooted,
installed HTC Sync Manager (setup name setup_3.0.52.0_htc.exe), then uninstalled it...
because a tutorial said this would keep the drivers but remove the software. Still no luck on the MTP driver though.
• Found "Mass Storage Device" (my phone) under device manager, removed it, unplugged, rebooted, replugged.
• Plugged cord into back of PC, so I'm using USB 2.0 rather than USB 3.0.
• One suggestion said a certain registry section might have an upperfilter key that shouldn't be there.
But I don't have that upperfilter key so that's not the issue.
Some fixes require getting into my phone (one guy suggests turning off USB debugging)...
but I no longer have a working OS. I can get into my bootloader, I tried Factory Reset.
But after choosing this I go into TWRP and I have no TWRP backups that I can restore.
So my next guess is, I need to get a recovery ZIP (is that basically a ROM?) that TWRP can install.
If that's correct, what ZIP should I get? I was on Android 4.0.3 Sense 4.0, can I download jellybean with Sense 5.0,
and install it via TWRP?
That was my goal all along, but I'm determined to get S-OFF working, so if doing that means my phone gets wiped again,
I guess I just want whatever ROM/recovery/whatever that allows me to change this USB debugging setting,
and try other phone-related fixes to the MTP driver issue.
First of all, flash an ICS rom. I'm assuming that you are still using the same ICS firmware, and you will want to have your phone operational (to enable USB debugging). The link for MeanRom ICS still works. http://old.androidfilehost.com/main/EVO_3D_Developers/mikeyxda/LTEvo/MeanROM-ICS-v65-jewel-ltevo.zip
Ok....since you are on the old HBoot, I think that you need to use the older S-Off methods (LazyPanda or DirtyRacun), if I'm not mistaken. You can not download and flash Sense 5.0 through TWRP as of yet, because you need to be using the new firmware to do so. You may want to pay http://unlimited.io/jewel.htm a visit. Also, to use LazyPanda or DirtyRacun, you need to be using Ubuntu. Another option that you have is to use the regular RUU and update directly to Sense 5.0. You will be stock, unrooted, but you can easily use the latest S-Off method.
Lastly, for your rooting/S-Off needs, you can also use a handy-dandy toolkit from @WindyCityRockr that can handle everything that you need to do. I usually encourage manual labor, but there are some exceptions. http://forum.xda-developers.com/showthread.php?t=2436217
Thanks again for jumping in.
I'm getting somewhere, but still so many difficulties.
Fix one thing, break two more.
I finally have a new working rom, but almost against my will it ended up
being CyanogenMod.
The short version:
- unlocked bootloader, got TWRP going, finally got ADB working (don't think it's the right driver,
but whatever, ADB commands work fine), wiped everything... factory reset, Dalvik, external storage.
- Didn't wipe Internal storage, I wiped only /data/ per some post's recommendation.
- I used ADB PUSH to get a few possible roms onto /sdcard/
PJ75IMG_1.13.651.1.zip (failed with "unable to open zip")
(ROM)_Stock_Rooted_OTA_(3.16.651.3)V2.zip (failed with "unable to execute updater binary in zip")
cm-10.2.0-jewel.zip (cyanogenmod) - success!
So, the phone works. It appears to be at least based on android 4.3... and I'm guessing CM, which updates
frequently, has all those OTA updates bundled into it. Any downsides to CyanogenMod?
I could just proceed from here to reinstall my old apps etc.
I'm still not "S-OFF" which annoys me, but I read a post suggesting it's not really that necessary.
The way they put it is, s-off allows you to access partitions so they can be modded,
but nobody is developing anything interesting for those partitions. Like nobody's doing custom radios and such.
Should I still pursue S-OFF anyway?
If so, is there a way to do it with CyanogenMod?
That awesome app (Windroid Universal Toolkit) doesn't recognize the phone.
Last question, how should I go about restoring everything?
I had titanium and nandroid backups copied to my computer.
Can it restore to such a wildly different version of the OS?
Can I get back not just apps, but stuff like my keyboard preferences, texting history, etc.?
Should I still pursue S-OFF anyway?
Click to expand...
Click to collapse
Yes! Being S-On is a complete pain in the BUTT when switching AOSP roms. Have you tried to flash the rom that I posted, MeanRom ICS? I'm really trying to get you to stay on Sense, because S-Off and other different tools work so much better while using Sense. AOSP is better after S-Off. But that's up to you.
If so, is there a way to do it with CyanogenMod?
Click to expand...
Click to collapse
I am not sure. You can try if you have the time. I suggest making a nandroid of your CM rom, and try to flash a Sense ICS rom, not JB...yet.
That awesome app (Windroid Universal Toolkit) doesn't recognize the phone.
Click to expand...
Click to collapse
CM might be the issue here, as well as it might not.
Last question, how should I go about restoring everything?
I had titanium and nandroid backups copied to my computer.
Can it restore to such a wildly different version of the OS?
Click to expand...
Click to collapse
Yes, TB will still work. There are some apps that might cause the restoration process to freeze, so I suggest killing TB and skipping over the app that froze the process when you return.
Can I get back not just apps, but stuff like my keyboard preferences, texting history, etc.?
Click to expand...
Click to collapse
If your keyboard preferences was not backed up, then no. If you were using the stock Sense keyboard, then that is a no as well. As long as your texting history was backed up, it can be restored. Texts are not like apps...their data is typically stored in XML files which are readable through any version of Android (2.3+).
I'm still soliciting my help if you need it.
I'm for sure going to need it, so thanks very much for the ongoing support!
I got discouraged after all the failures but I'll download Meanrom now.
The thing is... now that Cyanogen mod works, I hesitate to wipe it and try a new one.
Especially since several other roms I tried mysteriously failed to install.
I like that it's jellybean and don't wanna move backwards to ICS.
And I like their goal of cutting out the fluff.
I still want S-OFF, will I end up having to wipe everything again to get it?
Also, I really don't feel confident I have the right drivers for my windows machine.
I can transfer files in USB mode, go into USB debugging, and do the usual ADB commands.
But the phone shows up as a nexus in device manager, but it's definitely evo 4G lte.
I tried installing an executable RUU and it failed after a bit saying it can't detect the device.
And there's that issue where Windroid doesn't detect it.
So I have the feeling that without the right USB drivers, tools like Moonshine will still fail.
I specifically got errors every time when anything tried to install MTP usb drivers. Do I really need them?
You think LazyPanda or DirtyRacun's tools will work even if I never get the MTP thing installed?
CreeDo said:
I'm for sure going to need it, so thanks very much for the ongoing support!
I got discouraged after all the failures but I'll download Meanrom now.
The thing is... now that Cyanogen mod works, I hesitate to wipe it and try a new one.
Especially since several other roms I tried mysteriously failed to install.
I like that it's jellybean and don't wanna move backwards to ICS.
And I like their goal of cutting out the fluff.
I still want S-OFF, will I end up having to wipe everything again to get it?
Also, I really don't feel confident I have the right drivers for my windows machine.
I can transfer files in USB mode, go into USB debugging, and do the usual ADB commands.
But the phone shows up as a nexus in device manager, but it's definitely evo 4G lte.
I tried installing an executable RUU and it failed after a bit saying it can't detect the device.
And there's that issue where Windroid doesn't detect it.
So I have the feeling that without the right USB drivers, tools like Moonshine will still fail.
I specifically got errors every time when anything tried to install MTP usb drivers. Do I really need them?
You think LazyPanda or DirtyRacun's tools will work even if I never get the MTP thing installed?
Click to expand...
Click to collapse
Feel free to try the facepalm S-off method as well. Works on devices with older software and is super easy. Look here:
http://forum.xda-developers.com/showthread.php?t=2163013
Sent from my Nexus 5 using XDA Premium 4 mobile app
Evolution_Freak said:
Feel free to try the facepalm S-off method as well. Works on devices with older software and is super easy. Look here:
http://forum.xda-developers.com/showthread.php?t=2163013
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Cheers, it does look pretty straightforward.
Of course that's what I thought hours ago when I tried moonshine haha.
I'll give it a go.
To be clear, does this method wipe anything?
They don't actually say.
CreeDo said:
Cheers, it does look pretty straightforward.
Of course that's what I thought hours ago when I tried moonshine haha.
I'll give it a go.
To be clear, does this method wipe anything?
They don't actually say.
Click to expand...
Click to collapse
Can't remember if it wipes or not. Best thing to do is make a backup with TWRP and keep the backup on your external SD card. If it wipes you can always restore your backup.
Sent from my HTC device
Thanks for the help so far guys. I am currently really enjoying Cyanogenmod. I suspect it's eating battery more,
but then against I am on the phone for hours redoing everything that got changed/removed.
Does anyone know if there's a simple way (or even a difficult way) to restore my texts?
Because the app is totally different, and the old text app was the one that came
with the stock rom, I cannot restore it in titanium. But if I could extract even the raw text that'd be helpful.
Get back to Sense, or get someone with Sense to restore it for you, and save it using a different app. Or maybe try using SMS Backup & Restore from the Play Store. I'm not sure if it can read the backups saved through Sense, but it's worth a try. You just have to navigate to the location of the old backup.
It looks like I can import an XML in this messaging app so maybe if sense offers an export to XML option, I'll be set.
Sense is sort of an OS on top of the OS, right?
Can sense be loaded without flashing a new rom? or is it too integrated with the OS?

Attempting rollback 3.2.5 to 3.1.0 - assistance request

So following Davey126's advice, I started looking into doing a rollback on my apollo 3.2.5. I managed to get the play store up and running after some work, and grabbed the latest prop editor following the instructions in http://forum.xda-developers.com/showthread.php?t=2782159 So far so good. I then edited the four lines in question, and allowed the device to reboot.
The changes didn't seem to take. After the reboot I ended up on the same version as where I started, and the four lines I changed were back to their unedited versions. Since I have run into a problem with r/w permissions before, I suspect I'm missing them here as well - but I haven't seen the thread/entry on how to change those. Any help would be appreciated.
If, those aren't the issue, then I'm lost again.
begalund said:
So following Davey126's advice, I started looking into doing a rollback on my apollo 3.2.5. I managed to get the play store up and running after some work, and grabbed the latest prop editor following the instructions in http://forum.xda-developers.com/showthread.php?t=2782159 So far so good. I then edited the four lines in question, and allowed the device to reboot.
The changes didn't seem to take. After the reboot I ended up on the same version as where I started, and the four lines I changed were back to their unedited versions. Since I have run into a problem with r/w permissions before, I suspect I'm missing them here as well - but I haven't seen the thread/entry on how to change those. Any help would be appreciated.
If, those aren't the issue, then I'm lost again.
Click to expand...
Click to collapse
Stop!! You are following the wrong procedure and could brick your device! Don't reboot again. I will post further info shortly (on a call at the moment...).
EDIT: Sorry for the earlier drama; you were headed for a cliff ...
Recheck the guide (post #1) from the thread you linked. Note there are two sections: One for devices below 3.2.5 and a second for 3.2.5-3.26. You want the second section. There is no need to mess with build prop. You should immediately restore that file to its previous state (hopefully you have/made a backup). Then follow the rest of the instructions. Again, sorry for sounding like an alarmist worry wort. A quick check of the forums will surface many hdx carcases in the sad hands of those who didn't follow instructions or made simple mistakes (we all make mistakes).
Davey126 said:
Stop!! You are following the wrong procedure and could brick your device! Don't reboot again. I will post further info shortly (on a call at the moment...).
EDIT: Sorry for the earlier drama; you were headed for a cliff ...
Recheck the guide (post #1) from the thread you linked. Note there are two sections: One for devices below 3.2.5 and a second for 3.2.5-3.26. You want the second section. There is no need to mess with build prop. You should immediately restore that file to its previous state (hopefully you have/made a backup). Then follow the rest of the instructions. Again, sorry for sounding like an alarmist worry wort. A quick check of the forums will surface many hdx carcases in the sad hands of those who didn't follow instructions or made simple mistakes (we all make mistakes).
Click to expand...
Click to collapse
No worries!
1. Yes, I had a backup.
2. Nothing got broken, so everything is peachy.
3. The way that post is written, there is absolutely no easy way to tell (for the average user) that you still don't edit the file with build prop. All it appears is that you need a different roll back file for 3.2.5 and 3.2.6 variants instead of the earlier versions.
Someone should likely edit that post - or at least add something to it to make it more clear. I know I read every entry in that thread and I never caught anything that told me "hey, you are on one of these two versions. Skip the build prop step and just push the update. it'll work fine from there."
However, I thank you for the added information. I'll give it a whirl and see if that works. It would be nice to get beyond at least point C so I can get to the steps I want to do. I keep getting stuck at the point just before where things get nice.
begalund said:
No worries!
Nothing got broken, so everything is peachy.
Click to expand...
Click to collapse
Glad nothing got busted!
begalund said:
Someone should likely edit that post - or at least add something to it to make it more clear. I know I read every entry in that thread and I never caught anything that told me "hey, you are on one of these two versions. Skip the build prop step and just push the update. it'll work fine from there."
Click to expand...
Click to collapse
It's an old post created before 3.2.5+ was released. I do not know if the OP is still around. As many others have commented the hdx forums are generally a mess (with a few notable exceptions) as the landscape is continually changing. No one has the time/energy to create and validate step-by-step guides given the number of permutations/combinations and high risk of bad outcomes given a touchy device with limited recovery options...especially for those who can't install twrp and/or unlock their bootloader.
Note to newbies: Many tinkerers come to these forums thinking all the cautions are the byproduct of excessive hand wringers blowing smoke out of a certain orifice. Hey, if I create a brick I'll just whip out my magical fastboot cable, arsenal of fastboot commands and make everything right again. Err, no. Fastboot cables don't work on the HDX nor to most other recovery techniques. Tread carefully...respect the kindle. Rewards will come soon enough.
Hey, already pushed the thank you, for all of your help, but I've got one more fundamental question that might seem kind of stupid, but what exactly does this mean?
"4. Put "update-kindle-1X.3.1.0_user_310079820.bin" in SAME folder,
. . . . .
7. put update-kindle-1X.3.1.0_user_310079820.bin" in internal storage."
I skipped steps 5 and 6, because they make sense to me. But step 4 loses me. which "same" folder? None of the previous steps mention anything about a folder where anything is being stored. Likely this is referring back to that same previous post you referenced above.
I have no trouble with step 7 - that makes sense - but I'm suddenly worried about this mysterious step 4, especially since "SAME" is in all caps.
begalund said:
Hey, already pushed the thank you, for all of your help, but I've got one more fundamental question that might seem kind of stupid, but what exactly does this mean?
"4. Put "update-kindle-1X.3.1.0_user_310079820.bin" in SAME folder,
. . . . .
7. put update-kindle-1X.3.1.0_user_310079820.bin" in internal storage."
I skipped steps 5 and 6, because they make sense to me. But step 4 loses me. which "same" folder? None of the previous steps mention anything about a folder where anything is being stored. Likely this is referring back to that same previous post you referenced above.
I have no trouble with step 7 - that makes sense - but I'm suddenly worried about this mysterious step 4, especially since "SAME" is in all caps.
Click to expand...
Click to collapse
Tanks for the thanks. As a new comer I struggled a bit and got help from some kind souls in these forums. Giving back ...
It is a tethered operation as you probably gathered. Step 4 means you need to put the .bin file in the same folder on Windows where install.bat lives. If you edit the batch file you'll see it generates a signed flashable image from the bin file and then issues a bunch of adb commands on your behalf. For Step 7 copy the bin file to root (not sdcard) on your hdx. Then reboot.
Footnotes:
- when you download the batch file be sure to use the blue "download now" button. Filename should be "rollback.zip" .The orange button yields an executable called "rollback.zip.exe". Probably fine but since I can't see into it can't tell for sure. Also, make sure to download the file appropriate for your device (7"/Thor or 8.9"/Apollo).
- be sure to immediately disable wifi after performing the update; otherwise Amazon may push a nasty update of their own. As a precaution I would advise deleting all existing wifi profiles and make sure you are not within range of an open hotspot. Don't want the Kindle to auto connect and update while you are sleeping.
- I would strongly recommend flashing twrp immediately after, test and backup of you stock rom from within twrp. Leave the image on your kindle if you have room.
- Once everything is working to your satisfaction flash the nexus rom (v2.0.5) and optionally the 3.2.3 bootloader update as described in earlier posts. Read up on any caveats.
- (optional) Unlock your bootloader. This not necessary to run Nexus and CM11 but is for some CM12 builds. An unlocked bootloader also opens additional recovery options should you loose twrp. That said, unlocking the bootloader is not for the faint of heart and carries its own set of risks.
Davey126 said:
For Step 7 copy the bin file to root (not sdcard) on your hdx. Then reboot.
- be sure to immediately disable wifi after performing the update; otherwise Amazon may push a nasty update of their own. As a precaution I would advise deleting all existing wifi profiles and make sure you are not within range of an open hotspot. Don't want the Kindle to auto connect and update while you are sleeping.
Click to expand...
Click to collapse
Okay. New headaches.
First part of the rollback happened. I'm now on 14.3.0.0. That worked okay. I grabbed the 14.3.1.0 update and loaded it on but then nothing happened. No further updates.
At this point I figure 1 of 3 things happened. Either:
A. I put it in the wrong place - I stuck it in Internal Storage (/storage/emulated/0), I would move it to either / or /root, but I can't - "no space available" error when I attempt to move it via es file explorer
B. I could keep turning OTA off and on and hope it eventually takes, but how many times exactly?
or C. I'm missing something with wireless needing to be on (or off but in some weird mode) or whatever. I'm just worried about having an automatic update to another newer version that I can't fix.
So what am I missing?
begalund said:
Okay. New headaches.
First part of the rollback happened. I'm now on 14.3.0.0. That worked okay. I grabbed the 14.3.1.0 update and loaded it on but then nothing happened. No further updates.
At this point I figure 1 of 3 things happened. Either:
A. I put it in the wrong place - I stuck it in Internal Storage (/storage/emulated/0), I would move it to either / or /root, but I can't - "no space available" error when I attempt to move it via es file explorer
B. I could keep turning OTA off and on and hope it eventually takes, but how many times exactly?
or C. I'm missing something with wireless needing to be on (or off but in some weird mode) or whatever. I'm just worried about having an automatic update to another newer version that I can't fix.
So what am I missing?
Click to expand...
Click to collapse
Hum. Everything seems ok. Bin file is in the correct location (/storage/emulated/0). Make sure OTA is enabled using the same tool/technique you originally used to disable (there are several methods) and reboot. Some posters claim they had to toggle it on/off a few times. While my device recognized the update fairly quickly (minutes) others mentioned it took a while. Keep checking settings->device->system updates. Some say the update did not take until WiFi was disabled. Might want to try that first. I recall seeing something about airplane mode but can't immediately find the post.
btw, you can mitigate the automatic update risk by making sure there are NO WiFi profiles on your device and you are not in range of any open hotspots (if possible).
Well, still no dice.
I've reset OTA (cycled off then on) and rebooted about 10 times now. I've also attempted various options of wifi on, off, and in airplane mode. The only thing I haven't done is connected to an actual network and pushed the check now button (I'm not quite that dumb). The lovely device just keeps taunting me with 14.3.0.0 and refusing to do anything else.
Very frustrating.
I'm gonna head for bed and look at it fresh sometime tomorrow. Maybe it will miraculously fix itself while I ignore it (but I really doubt that will be the case).
begalund said:
Well, still no dice.
I've reset OTA (cycled off then on) and rebooted about 10 times now. I've also attempted various options of wifi on, off, and in airplane mode. The only thing I haven't done is connected to an actual network and pushed the check now button (I'm not quite that dumb). The lovely device just keeps taunting me with 14.3.0.0 and refusing to do anything else.
Very frustrating.
I'm gonna head for bed and look at it fresh sometime tomorrow. Maybe it will miraculously fix itself while I ignore it (but I really doubt that will be the case).
Click to expand...
Click to collapse
Sorry for your troubles. One or more of the following are likely culprits:
- OTA capability not fully restored (try HDX Toolkit if you haven't already)
- ensure the .bin file name matches exactly and is located in the proper folder
- Verify .bin MD5 on the device (use a tool like hash droid) MD5=0F2BC5278C057E7A6B4823B0F68D0727
- use notepad to view the batch file; make sure all the files made it to respective directories on your HDX
- repeat the preliminary steps with your device tethered
If everything checks out then the real fun begins. You'll need to comb threads for others who have experienced a similar problem. You are looking for some morsel that may provide a path forward. Frustrating - yes! One reason there are not step-by-step tutorials as everyone's device seems to respond differently; too many uncontrolled variables. Not sure anyone really knows what all those variables are.
Remain calm and don't do anything crazy. Be wary of fixes that involve manually modifying build.prop or flashing via adb. Both are legitimate tools/techniques in skilled hands. Used incorrectly they can (and usually do) yield a brick.
So I was attempting to write a nice long message about how I was using the right toolkit, and how to check on OTA messages to verify whether it was performing correctly, when all of a sudden I look down at my device and it suddenly stopped being obstinate.
No idea what I did. It just started playing nice.
14.3.1.0 now installed. I'm going to go get a drink.
begalund said:
So I was attempting to write a nice long message about how I was using the right toolkit, and how to check on OTA messages to verify whether it was performing correctly, when all of a sudden I look down at my device and it suddenly stopped being obstinate.
No idea what I did. It just started playing nice.
14.3.1.0 now installed. I'm going to go get a drink.
Click to expand...
Click to collapse
Funny how some devices take their time processing update files. Would love to know the criteria for checking and if processing can be manually triggered. Don't forget to disable OTA or keep WiFi off as long as there is a version of stock os in the system partition. One you load nexus or some other rom OTA worries will be history.
Edit: Enjoy that drink; you earned it
So I thought I would just report back with a final update as of 20 minutes ago:
Finally got the device rolled forward to 14.3.2.4
Re-rooted
Re-safestrapped
Backedup
Partitioned
And Nexus 4.2.2 running perfectly fine in Rom slot 1.
I'll go add a few apps later to personalize and make it wife-friendly. Thanks to everyone here and especially Davey126 for the patient assistance. I'll probably be back at some point in the near future to figure out the next step, but for now I'm gonna go enjoy an ad-free device for awhile.
begalund said:
So I thought I would just report back with a final update as of 20 minutes ago:
Finally got the device rolled forward to 14.3.2.4
Re-rooted
Re-safestrapped
Backedup
Partitioned
And Nexus 4.2.2 running perfectly fine in Rom slot 1.
I'll go add a few apps later to personalize and make it wife-friendly. Thanks to everyone here and especially Davey126 for the patient assistance. I'll probably be back at some point in the near future to figure out the next step, but for now I'm gonna go enjoy an ad-free device for awhile.
Click to expand...
Click to collapse
Glad to hear you are back in business! An interesting choice to upgrade to 3.2.4 vs 3.2.3. Native twrp requires 3.2.3 or lower so no CM11/12 or bootloader unlock. I do not believe there are meaningful differences between Nexus v1.0.1 (safestrap edition) and v2.0.5 (native) so nothing lost at this point. Plus you still have access to stock with a simple reboot which can be an advantage. But it is unlikely other roms will be adapted to run under safestrap. Btw, downgrading from 3.2.4 is a bit tricker than 3.2.5/3.2.6. You many need to upgrade first.
Don't forget to reblock OTA if you haven't already. Enjoy your 'new' device
Davey126 said:
Glad to hear you are back in business! An interesting choice to upgrade to 3.2.4 vs 3.2.3. Native twrp requires 3.2.3 or lower so no CM11/12 or bootloader unlock. I do not believe there are meaningful differences between Nexus v1.0.1 (safestrap edition) and v2.0.5 (native) so nothing lost at this point. Plus you still have access to stock with a simple reboot which can be an advantage. But it is unlikely other roms will be adapted to run under safestrap. Btw, downgrading from 3.2.4 is a bit tricker than 3.2.5/3.2.6. You many need to upgrade first.
Click to expand...
Click to collapse
So it turns out I may have done myself a big favor by going the safe route. I'm not positive of course since I haven't tried the "non-safe route", but I'm guessing I'm right. I recently obtained a bluetooth KB to use with the fixed device - specifically the bear motion KB/case - cause I figured if I only spent $40 on the tablet, I'm not going to spend more than that on the KB. Since one of the purposes for this is to allow me to use it for remote work options, I wanted a better KB than pulling up the native one - especially if I'm running teamviewer, the screen is small enough as it is.
In any event, the Nexus SS edition has troubles pairing up with the KB (already logged a bug report on it), so I'm probably going to have to swap over to a different rom. Since I've already been through the process, and I've seen your updated posts in another thread, I'll just upgrade, rollback, and follow the twrp, cm11/12 route instead.
I just need to check and see if anyone has used this combination of hardware with another rom and made them work out.
begalund said:
So it turns out I may have done myself a big favor by going the safe route. I'm not positive of course since I haven't tried the "non-safe route", but I'm guessing I'm right. I recently obtained a bluetooth KB to use with the fixed device - specifically the bear motion KB/case - cause I figured if I only spent $40 on the tablet, I'm not going to spend more than that on the KB. Since one of the purposes for this is to allow me to use it for remote work options, I wanted a better KB than pulling up the native one - especially if I'm running teamviewer, the screen is small enough as it is.
In any event, the Nexus SS edition has troubles pairing up with the KB (already logged a bug report on it), so I'm probably going to have to swap over to a different rom. Since I've already been through the process, and I've seen your updated posts in another thread, I'll just upgrade, rollback, and follow the twrp, cm11/12 route instead.
I just need to check and see if anyone has used this combination of hardware with another rom and made them work out.
Click to expand...
Click to collapse
Have you tried stock Fire OS yet? Should be an easy test given you are on Safestrap with (presumably) stock in the base slot. That would help rule out any native compatibility issues.
If you opt for a different rom might try the native version of Nexus first (v2.0.5) after you get twrp loaded as it's an easy test. Possible (albeit unlikely) Safestrap is interfering. Of the two CM varients CM11 would see the better choice today as the latest CM12 build still seems to have some issues with BT. As always, watch the forums for updates.
Davey126 said:
Have you tried stock Fire OS yet? Should be an easy test given you are on Safestrap with (presumably) stock in the base slot. That would help rule out any native compatibility issues.
If you opt for a different rom might try the native version of Nexus first (v2.0.5) after you get twrp loaded as it's an easy test. Possible (albeit unlikely) Safestrap is interfering. Of the two CM varients CM11 would see the better choice today as the latest CM12 build still seems to have some issues with BT. As always, watch the forums for updates.
Click to expand...
Click to collapse
Second thing I did. Rebooted into the stock rom and retested. KB works fine on that slot. So it doesn't appear to be a safestrap issue - more than likely a problem with the SS version of Nexus - else it might be a Nexus compatibility issue with the KB itself.
I haven't had time to do any more playing with the tablet - Wife's birthday, but I'll retest once I know more. Should probably make a new thread however....
begalund said:
So it doesn't appear to be a safestrap issue - more than likely a problem with the SS version of Nexus - else it might be a Nexus compatibility issue with the KB itself.
Click to expand...
Click to collapse
Well, that's verified. :good: Although on the plus side, I did have a completely problem free rollback to 14.3.1.0, got twrp installed, and then cycled through a couple of the roms available looking for one that worked with the KB. Again, much thanks for all the assistance - including the assistance you lent to another user in the main thread - it helped immensely with getting twrp working on the first attempt. :victory:
Native Nexus - no go. It had the same issue. Eventually found it, but never recognized any key strokes. :crying:
Swapped to CM11 and at first it appeared to not work either (more on this), as the rom never got past the boot stage, so I bootloaded and realized I made an error (forgot to mount). Then the rom loaded but everything crashed on opening (rebooted again, wiped and reinstalled) now everything worked but the KB - I'll come back to this one.
Was about to try magic beans when I read something about the KB being "finicky" - so I swapped back to native nexus and played with the BT a bit. after 20 minutes of trying it never synced up, so I went back to CM11.
Turns out it does actually recognize it. You need to turn the KB on, then press its BT pair button, and then have the system search for new BT devices (in that order). It still has an issue where certain apps like titanium backup (or anything else that makes root calls) cause the system's BT to drop the KB - but it does find it and it works just fine 90% of the time. And when it does drop, it can be reset pretty easily in settings by removing the pairing and going through those steps again. You'll also have to do this every time the system is first turned on and you want to use it. A bit aggravating, but better than not having it any functionality or needing to swap back to FireOS.
Plus it appears that CM11 works just slightly better than nexus for the apps I tend to use anyway - so that's another bonus.
begalund said:
Plus it appears that CM11 works just slightly better than nexus for the apps I tend to use anyway - so that's another bonus.
Click to expand...
Click to collapse
Thanks for posting your BT findings with various HDX roms (below). Helpful to others who may be experiencing similar issues. I agree Nexus (based on Jellybean) is getting a bit long in the tooth. I stick with it given overall stability for the apps and and devices that I use including a AmazonBasics keyboard which pairs fine. I have been monitoring the HDX CM11/12 threads and will likely move there as the few remaining issues of concern to me are hammered out. Been running CM11 on another device (HD) for 15+ months; great rom that brought new life to an aging device.

[Q] Anyone got a step-by-step for getting from a rooted HDX 8.9 (14.3.2.6) to...

a stock android ROM (recommendations?)?
I've searched, but not found anything that can handily take me from having a rooted 14.3.2.6 HDx 8.9 (Apollo, right?) to a ROM. There's so much confusion about downgrading to an earlier version (for what?), having/not having safestrap, having TWRP, etc.
Anyone got a place where I can simply follow a 1-2-3 guide to go from root to ROM? Thanks!
BRPW said:
a stock android ROM (recommendations?)?
I've searched, but not found anything that can handily take me from having a rooted 14.3.2.6 HDx 8.9 (Apollo, right?) to a ROM. There's so much confusion about downgrading to an earlier version (for what?), having/not having safestrap, having TWRP, etc.
Anyone got a place where I can simply follow a 1-2-3 guide to go from root to ROM? Thanks!
Click to expand...
Click to collapse
There are no 1-2-3 guides. However, the steps required are not complicated but do require carefully reading and attention to detail. As you are probably aware Kindles in general and HDX models in particular are easy to 'brick' with limited/no recovery options. Many folks have killed their device with a simple mistake. Stakes are high with an Apollo given the device's value. Think hard before moving forward; even if you do everything right you can end up with an expensive paperweight. If you're an 'android expert' be aware many recovery techniques used on other devices simply will not work on an HDX. Fastboot cables are useless.
Preliminary questions:
- have you blocked OTA (if so via which method) or otherwise taken steps to isolate your device from automatic updates?
- do you have safestrap or Xposed Framework installed?
- have you enabled adb?
Davey126 said:
There are no 1-2-3 guides. However, the steps required are not complicated but do require carefully reading and attention to detail. As you are probably aware Kindles in general and HDX models in particular are easy to 'brick' with limited/no recovery options. Many folks have killed their device with a simple mistake. Stakes are high with an Apollo given the device's value. Think hard before moving forward; even if you do everything right you can end up with an expensive paperweight. If you're an 'android expert' be aware many recovery techniques used on other devices simply will not work on an HDX. Fastboot cables are useless.
Preliminary questions:
- have you blocked OTA (if so via which method) or otherwise taken steps to isolate your device from automatic updates?
- do you have safestrap or Xposed Framework installed?
- have you enabled adb?
Click to expand...
Click to collapse
Hi,
thanks for the response; I understand 100%.
I have blocked OTA (but weirdly keep getting "kindle is upgrading" messages every time I restart my Kindle)
I have Xposed Framework installed
ADB is enabled.
On another note, I've installed the four Gapps APKs, but my google play store won't work. Any idea why? When I install them, the play store opens and displays apps just fine, but won't download them. I reboot, and when I do I get "Google play store has stopped" and "Google play services has stopped working" messages, and Google Play crashes instantly.
I can't figure out why. Any idea? Apologies for bombarding you with queries.
Your play store issue is probably Google play services. Download version .99 from the internet or the general thread.
As for your next steps.
It depends on how involved you want to go.
You can use safestrap and run the nexus Rom. Some people feel that is less risky because you are not modifying the system as much or recovery at all. However, if something goes wrong, you have almost no way to fix it (it is possible to brick with safestrap).
Or,
Downgrade to 2.3.2 (you have to do this because the 2.6 bootloader will not load any other recoveries or roms. Then put twrp on and use cm11 or similar. This gives you a working recovery to fix some issues which could go wrong.
Finally, you could rollback and unlock your bootloader. If you do that, it is the most involved, and a little risky. However, if you succeed. You will be able to put more rooms on it and this gives you the most options to recover from an error.
Many people are playing with cm12 after this.
It all depends on how you are willing to take your risks. It will all require a lot of reading on the forums.
Good luck.
Sent from my KFTHWI using Tapatalk
BRPW said:
Hi,thanks for the response; I understand 100%.
I have blocked OTA (but weirdly keep getting "kindle is upgrading" messages every time I restart my Kindle)
I have Xposed Framework installed
ADB is enabled.
On another note, I've installed the four Gapps APKs, but my google play store won't work. Any idea why? When I install them, the play store opens and displays apps just fine, but won't download them. I reboot, and when I do I get "Google play store has stopped" and "Google play services has stopped working" messages, and Google Play crashes instantly.
I can't figure out why. Any idea? Apologies for bombarding you with queries.
Click to expand...
Click to collapse
You need to clean up your device before going further. Yes, some folks have successfully rolled back with baggage in tow. With limited data points my observation is previously unsurfaced add-ons and tweaks (usually revealed only after someone fubars their device) are contributors to unfavorable outcomes. Take that for what it's worth.
Recommendations:
- Identify and discard the update file that is triggering the "Kindle is upgrading" message. Best guess is a 14.x upgrade that can't progress due to OTA block. You are looking for a large (500 MB+ file) .bin file with a name similar to "update-kindle-14.4.5.3_user_453011120.bin". Reboot to make sure the upgrade message goes away.
- Tether your device. Download HDX Toolkit to a Windows box and make sure it can see your Kindle. Don't take any actions other than confirming root.
- Disable wifi and delete all existing wireless profiles. Then remove the existing OTA blocker reversing whatever technique was previously used.
- Use HDX toolkit to block OTA (this is the only method I trust for Fire OS 3.0.x-3.2.x)
- Uninstall Xposed framework and all associated modules (module portion isn't technically necessary as they won't run with framework disabled)
- Remove play store, services, framework (via services) and all Google apks. Reboot to make sure your device is 'clean'. You should still have root, of course.
- Come clean on any other tweaks previously made including modifications to build.prop, failed root attempts, safestrap, etc. Anything that deviates from stock.
Post back when complete. I'll then help you through the roll back process and installation of twrp. From there you can install Nexus (excellent, stable rom but Jellybean based) or CM11 (KitKat). Save bootloader unlocking for another day.
Davey126 said:
You need to clean up your device before going further. Yes, some folks have successfully rolled back with baggage in tow. With limited data points my observation is previously unsurfaced add-ons and tweaks (usually revealed only after someone fubars their device) are contributors to unfavorable outcomes. Take that for what it's worth.
Recommendations:
- Identify and discard the update file that is triggering the "Kindle is upgrading" message. Best guess is a 14.x upgrade that can't progress due to OTA block. You are looking for a large (500 MB+ file) .bin file with a name similar to "update-kindle-14.4.5.3_user_453011120.bin". Reboot to make sure the upgrade message goes away.
- Tether your device. Download HDX Toolkit to a Windows box and make sure it can see your Kindle. Don't take any actions other than confirming root.
- Disable wifi and delete all existing wireless profiles. Then remove the existing OTA blocker reversing whatever technique was previously used.
- Use HDX toolkit to block OTA (this is the only method I trust for Fire OS 3.0.x-3.2.x)
- Uninstall Xposed framework and all associated modules (module portion isn't technically necessary as they won't run with framework disabled)
- Remove play store, services, framework (via services) and all Google apks. Reboot to make sure your device is 'clean'. You should still have root, of course.
- Come clean on any other tweaks previously made including modifications to build.prop, failed root attempts, safestrap, etc. Anything that deviates from stock.
Post back when complete. I'll then help you through the roll back process and installation of twrp. From there you can install Nexus (excellent, stable rom but Jellybean based) or CM11 (KitKat). Save bootloader unlocking for another day.
Click to expand...
Click to collapse
I can't find anything resembling that type of file name, after doing a ES file explorer search. I also tried ordering by size and going through folders and files, but still couldn't find anything.
BRPW said:
I can't find anything resembling that type of file name, after doing a ES file explorer search. I also tried ordering by size and going through folders and files, but still couldn't find anything.
Click to expand...
Click to collapse
Don't have an immediate explanation but suggests something is amiss that could muck-up roll back efforts. It could be OTA is only partially blocked so your Kindle sees there is an update but can't download or process it. Do you know what method was used to block updates?
Davey126 said:
Don't have an immediate explanation but suggests something is amiss that could muck-up roll back efforts. It could be OTA is only partially blocked so your Kindle sees there is an update but can't download or process it. Do you know what method was used to block updates?
Click to expand...
Click to collapse
Yeah, I used the KFHDX Toolkit 0.95, and once I'd installed Xposed Framework, I installed the HDXposed module, which also blocks OTA updates.
BRPW said:
Yeah, I used the KFHDX Toolkit 0.95, and once I'd installed Xposed Framework, I installed the HDXposed module, which also blocks OTA updates.
Click to expand...
Click to collapse
HDXposed is likely part of the problem. Uninstall that (make sure wifi is off), reboot then reapply the OTA blocker integrated into KFHDX Toolkit 0.95. Reboot again and see if update message goes away. Might not if a bit got set somewhere indicating that an update is available. That in itself shouldn't be an issue unless information about the update version is also stored (don't believe it is).
Disclaimer: Anytime you muck with OTA blocking there is a chance it won't get set properly resulting in an unwanted update when wifi is restored. Recently this has been the case with renaming the otacerts file...at least on some versions of Fire OS. That said, I have yet to have the OTA blocker in KFHDX Toolkit fail. Once you ditch Fire OS this worry goes away.
Davey126 said:
HDXposed is likely part of the problem. Uninstall that (make sure wifi is off), reboot then reapply the OTA blocker integrated into KFHDX Toolkit 0.95. Reboot again and see if update message goes away. Might not if a bit got set somewhere indicating that an update is available. That in itself shouldn't be an issue unless information about the update version is also stored (don't believe it is).
Disclaimer: Anytime you muck with OTA blocking there is a chance it won't get set properly resulting in an unwanted update when wifi is restored. Recently this has been the case with renaming the otacerts file...at least on some versions of Fire OS. That said, I have yet to have the OTA blocker in KFHDX Toolkit fail. Once you ditch Fire OS this worry goes away.
Click to expand...
Click to collapse
Tried that; deactivated HDXposed, reboot. Enabled OTA, then re-disabled it, and rebooted again. Message still pops up briefly.
Should I continue with the steps you've listed above?
BRPW said:
Tried that; deactivated HDXposed, reboot. Enabled OTA, then re-disabled it, and rebooted again. Message still pops up briefly.
Should I continue with the steps you've listed above?
Click to expand...
Click to collapse
Yes - still need to prep the device. I'll be out-of-pocket for the next 8-10 hours; will look for an update then.
Davey126 said:
Yes - still need to prep the device. I'll be out-of-pocket for the next 8-10 hours; will look for an update then.
Click to expand...
Click to collapse
Okay, I'll complete the list of things you've recommended; again, thanks for your help so far. Really appreciate it.
Edit: All Google apps/APKs removed, Xposed Framework's gone also. Rebooted and clean as stock (apart from root, of course), and zero custom apps apart from SuperSU and towelroot; interestingly, after reboot, there's no 'upgrading' message. So seems that's also disappeared.
BRPW said:
Okay, I'll complete the list of things you've recommended; again, thanks for your help so far. Really appreciate it.
Edit: All Google apps/APKs removed, Xposed Framework's gone also. Rebooted and clean as stock (apart from root, of course), and zero custom apps apart from SuperSU and towelroot; interestingly, after reboot, there's no 'upgrading' message. So seems that's also disappeared.
Click to expand...
Click to collapse
Have a look here for next steps. You are following instructions for 3.2.5-3.2.6 which is at the bottom of the post shaded in grey. To be clear you do not need to modify build.prop (if anything suggests that and/or installing Safestrap you're in the wrong section). You can get everything ready following the post and move forward if you feel comfortable. Remember you will need to reroot and block OTA once the rollback completes; use HDX toolkit for both. An outline of further actions can be found here.
Ok - now i really do have to go ...
Davey126 said:
Have a look here for next steps. You are following instructions for 3.2.5-3.2.6 which is at the bottom of the post shaded in grey. To be clear you do not need to modify build.prop (if anything suggests that and/or installing Safestrap you're in the wrong section). You can get everything ready following the post and move forward if you feel comfortable. Remember you will need to reroot and block OTA once the rollback completes; use HDX toolkit for both. An outline of further actions can be found here.
Ok - now i really do have to go ...
Click to expand...
Click to collapse
Haha thanks; I have the update file downloaded, but getting suspicious about the update.prop file download link. Got phishing warnings and malicious warnings all over the place. May wait and see what you say once you're back.
Edit: Did some research; was clicking the wrong damn button. For anyone who comes across this, click the BLUE 'download now' button. I was clicking the green (read: advert) button. I've rolled my update back all fine; one question.
The update file says: 14.3.1.0, yet my Kindle firmward says 14.3.0.0. Is that supposed to be like that? Anyhow, I'm rerooted, OTA updates blocked. I think I'm going to wait to proceed with the next part. Thanks again (so far)!
BRPW said:
Haha thanks; I have the update file downloaded, but getting suspicious about the update.prop file download link. Got phishing warnings and malicious warnings all over the place. May wait and see what you say once you're back.
Edit: Did some research; was clicking the wrong damn button. For anyone who comes across this, click the BLUE 'download now' button. I was clicking the green (read: advert) button. I've rolled my update back all fine; one question.
The update file says: 14.3.1.0, yet my Kindle firmward says 14.3.0.0. Is that supposed to be like that? Anyhow, I'm rerooted, OTA updates blocked. I think I'm going to wait to proceed with the next part. Thanks again (so far)!
Click to expand...
Click to collapse
Not sure the rollback completed successfully. It is normal for your Kindle to report 14.3.0.0 just after executing the batch file. Fire OS normally won't downgrade so the script 'tricks' the system into thinking it's at 14.3.0.0. Your device then sees the 14.3.1.0 file as an update and processes it. You are essentially leveraging Amazon's update process to execute a rollback.
I'm guessing your forgot to transfer the bin file to your device after executing the upgrade script. If accurate your Kindle is in a someone dangerous state. You'll want to disable OTA blocking, copy the bin file to 'internal storage' and then check for updates via Fire OS settings. It may take a few minutes for your Kindle to recognize the update file. Also note the original bin file needed to reside in the same windows directory as the batch file when it was executed.
Side note: We are experiencing a rare power outage in my area. I'm penning this from a secondary system. Won't be staying on long to conserve battery. Will check for updates once power is restored.
Davey126 said:
Not sure the rollback completed successfully. It is normal for your Kindle to report 14.3.0.0 just after executing the batch file. Fire OS normally won't downgrade so the script 'tricks' the system into thinking it's at 14.3.0.0. Your device then sees the 14.3.1.0 file as an update and processes it. You are essentially leveraging Amazon's update process to execute a rollback.
I'm guessing your forgot to transfer the bin file to your device after executing the upgrade script. If accurate your Kindle is in a someone dangerous state. You'll want to disable OTA blocking, copy the bin file to 'internal storage' and then check for updates via Fire OS settings. It may take a few minutes for your Kindle to recognize the update file. Also note the original bin file needed to reside in the same windows directory as the batch file when it was executed.
Side note: We are experiencing a rare power outage in my area. I'm penning this from a secondary system. Won't be staying on long to conserve battery. Will check for updates once power is restored.
Click to expand...
Click to collapse
Hey Davey,
hope your power problems get sorted soon. As for the update, I did in fact pull the file both into the "rollback89v2" folder (containing the install.bat) and into the 'internal storage' area of the kindle, so should be no problem there. Got up this morning, headed to the 'Device' section to find my Kindle says 'update available'.
Bear in mind that OTA is disabled, and I've not enabled my WiFi since I began the process yesterday, so there should be ZERO chance of that being a normal OTA; I'm guessing it's the 'update' to 14.3.1.0?
BRPW said:
Hey Davey,
hope your power problems get sorted soon. As for the update, I did in fact pull the file both into the "rollback89v2" folder (containing the install.bat) and into the 'internal storage' area of the kindle, so should be no problem there. Got up this morning, headed to the 'Device' section to find my Kindle says 'update available'.
Bear in mind that OTA is disabled, and I've not enabled my WiFi since I began the process yesterday, so there should be ZERO chance of that being a normal OTA; I'm guessing it's the 'update' to 14.3.1.0?
Click to expand...
Click to collapse
Sorry for the delay. Yes, accept the update if you have not done so already. You will probably need to re-enable OTA (keep wifi off) for processing to complete. After reboot the device should report it's on 14.3.1. You can then reroot and block OTA via HDX toolkit.
Next step is to install twrp. If you are comfortable issuing adb commands you can use the method outlined here which is also where you grap the custom apk. Alternatively, sideload flashify (here or elsewhere; copy apk via tether). I recommend the latter as flashify simplifies future efforts and contains some nice backup/recovery features.
Test twrp by powering down your device then restarting by pressing power + vol-up. Release the power button when the grey Kindle logo appears. Release the volume button a few seconds later. You should eventually enter the twrp environment. Familiarize yourself with the options but don't take any actions. When complete hit the reboot button from the main screen (lower right corner).
Then update your bootloader to 3.2.3.2. This is listed as a prerequisite for twrp but the order is not important provided both get done. Personally I prefer to get twrp installed early in the sequence as it offers vastly improved recovery options should something go wrong. You can flash the updated bootloader from twrp or flashify.
Once this is done you are ready for a custom rom! Post when complete and I will briefly outline your options.
As always, think through each step before proceeding. Make sure you have the right files. Verify MD5s once copied to your device (I use Hash Droid). Installing twrp and the bootloader update involve flashing code directly to your device. A mistake can be non-recoverable.
Davey126 said:
Sorry for the delay. Yes, accept the update if you have not done so already. You will probably need to re-enable OTA (keep wifi off) for processing to complete. After reboot the device should report it's on 14.3.1. You can then reroot and block OTA via HDX toolkit.
Next step is to install twrp. If you are comfortable issuing adb commands you can use the method outlined here which is also where you grap the custom apk. Alternatively, sideload flashify (here or elsewhere; copy apk via tether). I recommend the latter as flashify simplifies future efforts and contains some nice backup/recovery features.
Test twrp by powering down your device then restarting by pressing power + vol-up. Release the power button when the grey Kindle logo appears. Release the volume button a few seconds later. You should eventually enter the twrp environment. Familiarize yourself with the options but don't take any actions. When complete hit the reboot button from the main screen (lower right corner).
Then update your bootloader to 3.2.3.2. This is listed as a prerequisite for twrp but the order is not important provided both get done. Personally I prefer to get twrp installed early in the sequence as it offers vastly improved recovery options should something go wrong. You can flash the updated bootloader from twrp or flashify.
Once this is done you are ready for a custom rom! Post when complete and I will briefly outline your options.
As always, think through each step before proceeding. Make sure you have the right files. Verify MD5s once copied to your device (I use Hash Droid). Installing twrp and the bootloader update involve flashing code directly to your device. A mistake can be non-recoverable.
Click to expand...
Click to collapse
Having issues with the first part. I have 'update failed'. I keep trying wifi on/OTA disabled, OTA enabled/Wifi disabled. Sometimes I get 'update now', but having trouble. It wants OTA and Wifi enabled. Any workaround?
BRPW said:
Having issues with the first part. I have 'update failed'. I keep trying wifi on/OTA disabled, OTA enabled/Wifi disabled. Sometimes I get 'update now', but having trouble. It wants OTA and Wifi enabled. Any workaround?
Click to expand...
Click to collapse
Suggestions (in priority order):
- remove all existing wifi profiles (so your device can't connect), move away from open hotspots, enable wifi and retry. Some report this solves the problem.
- if above fails shut down device and boot into recovery via power + vol-up. From there perform a factory reset. Then see if the update takes.
There is a small risk of crashing your device with the second method. I used to recommend against it but others report it is a necessary step. Suspect it depends on how OTA has been disabled in the past. Factory resets only cause problems if your device has unusual mods that prevent the reset from fully completing.
Davey126 said:
Suggestions (in priority order):
- remove all existing wifi profiles (so your device can't connect), move away from open hotspots, enable wifi and retry. Some report this solves the problem.
- if above fails shut down device and boot into recovery via power + vol-up. From there perform a factory reset. Then see if the update takes.
There is a small risk of crashing your device with the second method. I used to recommend against it but others report it is a necessary step. Suspect it depends on how OTA has been disabled in the past. Factory resets only cause problems if your device has unusual mods that prevent the reset from fully completing.
Click to expand...
Click to collapse
First option worked. Right, I side-loaded flashify. I'm guessing Im choosing the recovery image option, which then asks me to choose a recovery option; I choose TWRP, which then takes me to a device option. I don't see HDX 8.9 anywhere there. Which device am I choosing?
Edit: Scratch that; figured out what I had to do. Right, everything is done. TWRP's installed and working fine; bootloader is installed (though I don't know how to check it installed correctly). I think I'm ready for ROMs unless there are more checks to do?
Second edit: After some research, I think I've decided on CM11 (That's KitKat, right?). It seems that everything works on that; wifi works nicely, the Kindle app works nicely (had a HD7 that had issues after I flashed an Android ROM), even the camera works nicely. Just need a clear guide on how to flash it, so will wait for you to come back. It's things like "do I wipe dalvik cache, etc" that I'm confused about also. I'd rather not mess it up on the last hurdle trying to rush into it.
To specify, I'm looking at this one: http://forum.xda-developers.com/kin...rom-cm-11-20150228-unofficial-apollo-t3042776
Does it come pre-installed with gapps or no? Can't quite figure that out, since some ROMs specifically mention that they have gapps already loaded in.
Thanks.

Can you work this one out?

Hi all,
Putting it briefly....
Factory reset of hdx 7" on 4.5.2
Stuck at Kindle Fire logo
Shows in PC as Internal Storage but just empty folders Music, DCIM etc...
Can get ADB connection (good news?)
That's it....now here's the interesting bit.....
If I use Kindle Fire Utility and try to root using Towelroot the device goes straight go lock screen. I slide to open and am confronted with Towelroot app. Click on Make It Rain but nothing happens.
If I try other things like installing SU it returns with permission errors.
I can also get to the devices settings too. No other apps installed just HDXPOSED and TOWELROOT.
Got me baffled... Any ideas how to fix?
You can NOT use Towelroot for 4.5.2! You must use Kingroot. Read about this, I've no experience with it. From what I've read it's possible it requires internet connection, I also read this could be for optional download of some browser or whatever, so try to disable such options, if available. You should avoid internet connection, or have it as short as possible, to avoid OTA upate from Amazon to 4.5.4.
Yep I get that I can't use TOWELROOT. I'm just pointing out that installing it gets me past the stuck Kindle Logo into the devices settings. Just no other apps or home scree though. Can't lock screen and if I restart the device it sticks at logo again....
myotai said:
Yep I get that I can't use TOWELROOT. I'm just pointing out that installing it gets me past the stuck Kindle Logo into the devices settings. Just no other apps or home scree though. Can't lock screen and if I restart the device it sticks at logo again....
Click to expand...
Click to collapse
Nothing comes to mind. Generally being stuck at the grey Kindle logo is terminal on a device with stock recovery and a locked bootloader. For future reference HDXPOSED is obsolete and may have contributed to your woes. It was never designed for FireOS v4 and doesn't work well on later versions of FireOS v3.
Thanks,
Yet I can get as far as 'Settings'. Isn't there a way I can push an update via ADB and flash....I guess I'd need to install root first? Is either possible?
P.s its not the grey logo its the coloured orange animated one.
myotai said:
Thanks,
Yet I can get as far as 'Settings'. Isn't there a way I can push an update via ADB and flash....I guess I'd need to install root first? Is either possible?
P.s its not the grey logo its the coloured orange animated one.
Click to expand...
Click to collapse
Assume you tried another factory reset. Being stuck at the orange logo offers some hope but there is no Rx that I know of.
Obtaining root is obviously desirable. You can try installing Kingroot via adb install and hope it executes (like towelroot apparently does) and continues to completion. If successfully you could try to repair the damage that is preventing FireOS from fully booting.
I recall someone saying installing a different launcher (eg: Nova) allowed their Kindle to boot.
Another path is to place the 3.2.8 rollback file into the root of sdcard and hope it takes.
Thanks - I have had a look but can't see a specific guide to installing Kingroot via adb. There are generic tips and pointers but I want to salvage what I have and not completely brick it - does anyone know where the thread is?
Thanks...
myotai said:
Thanks - I have had a look but can't see a specific guide to installing Kingroot via adb. There are generic tips and pointers but I want to salvage what I have and not completely brick it - does anyone know where the thread is?
Thanks...
Click to expand...
Click to collapse
You probably won't find that (not aware of any forum postings). Here's the deal. You are operating in uncharted waters trying to revive an unlocked/unrooted device that got borked for unknown reasons. You are going to have to a bunch of research and take some chances. FireOS can be a bxxch to repair. If the device is under warranty your best course of action is to engage Amazon for an exchange.
Kingroot is a longshot idea which I would not have mentioned if not for your experience with Towelroot. I have no idea if it will work.
Google (or another search engine) is your friend. A couple representative links below that popped up on the first attempt. I have no experience with either site an can not vouch for the content. Just a starting point ...
- Kingroot
- ADB Info
Thanks for your feedback!
I guess nothing ventured n all that!
Its a paper-weight at the moment so can't get much worse.....I'll wander around those un-charted lands and see what I come up with!
Ok, so I've managed to root using Kingroot. Installed Su too. But that's as far as I've got - I'm hoping that there is some way of salvaging this machine now I have root enabled and can get as far as the settings menu?
Thanks...
myotai said:
Ok, so I've managed to root using Kingroot. Installed Su too. But that's as far as I've got - I'm hoping that there is some way of salvaging this machine now I have root enabled and can get as far as the settings menu?
Thanks...
Click to expand...
Click to collapse
So you're on 4.5.2 rooted & OTA disabled now? Then try to install Safestrap v4. If it works, backup your stock slot (even if it doesn't work, who knows what it'll be good for), and move it to your PC. As the secondary slots won't work with WLAN atm anyway, you can install one of the Safestrap v4 compatible ROMs, e.g. Nexus, or CM11 in the stock slot, don't create any secondary Slots (yet).
myotai said:
Ok, so I've managed to root using Kingroot. Installed Su too. But that's as far as I've got - I'm hoping that there is some way of salvaging this machine now I have root enabled and can get as far as the settings menu?
Thanks...
Click to expand...
Click to collapse
To confirm you are now on rooted 4.5.2 but can get beyond the FireOS settings menu. If you install an apk via adb can you retain enough control to launch the app UI? You can do this via an adb shell command; unfortunately, the specifics are beyond my knowledge. Hopefully someone else can jump in or you can research on your own (if needed).
There is no safe way to repair FireOS directly with a locked bootloader. On many Android devices you would simply reflash/reinstall the ROM. Unfortunately, Amazon neutered the stock recovery environment as you discovered. If something goes wrong you are in a world of hurt. I think there is a very good chance your device can be revived. Just need to proceed carefully and not bork things to the point were you don't get past the grey logo. That generally means you own a door stop.
Thoughts (sorry if these are obvious):
- Keep in mind OTA is probably enabled on your device. Stay off wifi if you get that far; best to use a tether for file transfer, etc. until the problem is fixed. You can also rename the OTA apk via adb ... but your focus should be elsewhere at this point.
- It appears the FireOS launcher is hanging during initial setup (as you did a factory reset). You may find joy by installing another launcher (eg: Nova via adb) which often set themselves as the default when installed. Once you regain some control you can then install Safestrap v4 which is the pathway to other roms or repairing 4.5.2. Be aware FireOS will try to reset the default launcher on reboot. If this method works don't mess around trying to fix stuff. Install Safestrap v4 immediately (you also need to open the app and install Safestrap recovery) so you retain some control over your device during further troubleshooting.
- If a different launcher does not work try going for Safestrap v4. You will probably need to get smart around adb shell commands as you have to launch the UI to install the Safestrap recovery environment.
Thanks all taken in - my knowledge of ADB and its various commands are being added to as the hours go by - never really used it before.
Determind though........!
So, its looking better. Managed to get Safestrap installed and using a VERY convoluted method got into Recovery. After four attempts installed CM11 and have a working tablet now.
What I want to do now is somehow get a stock Kindle ROM running....any ideas?
Thanks again for your help everyone!
myotai said:
So, its looking better. Managed to get Safestrap installed and using a VERY convoluted method got into Recovery. After four attempts installed CM11 and have a working tablet now.
What I want to do now is somehow get a stock Kindle ROM running....any ideas?
Thanks again for your help everyone!
Click to expand...
Click to collapse
Yep - just flash 4.5.2 rom from here (don't use any other - you'll be rewarded with a brick). I strongly suggest you backup your existing stock slot (containing CM11) and reflash that to a secondary slot that you'll need to create. You won't be able to use wifi on the secondary slot but it will give you a rom to boot into in the event something goes wrong with the FireOS flash. Once you get FireOS working in the stock slot you should be able uninstall Safestrap. The operative word is 'should' as the system and recovery partitions need to be consistent for FireOS to boot properly. From what you have shared there is no reason to believe this is not the case - but the risk can not be dismissed. The other option is to leave Safestrap installed which only adds an annoying splash screen on boot but otherwise does not impact performance. What it does do is give you a pseudo-recovery environment which can be quite handy as you have discovered! It's also the vehicle for installing other roms such as CM11, Nexus v4, etc.
Take note of the cautions in the linked OP, in particular OTA. After flashing 4.5.2 you'll need to root and rename the OTA apk before enabling wifi. Amazon is aggressively pushing 4.5.4 which can not be rooted. Don't ruin your day - block OTA (yea - that was stupid).
Thanks so much. Its worth listing the procedures that got me this far...
I think installing TOWELROOT via ADB despite the fact I knew it wouldn't work was oddly the only thing that got me as far as 'settings' from a stuck Kindle logo. Then I had to resgiter the device in order to go to 'new offers' in the books setting to access the browser.....emails......Kingroot......finally Safestrap....boom!

Apollo acting weird

Ok so at first it wouldn't let me in until I plugged it into a computer or a fancy USB outlet. And it wouldn't let me go T the home screen. Now it wont let me on at all, after the home screen suddenly swooped in and ate this post on my Apollo, thus ****ing it. So now I can't get in at all. And I just rooted after I suddenly got this update, the newish one, and I renamed ota and ota contracts on accident. Is that a problem? Please help me...
Leafen said:
Ok so at first it wouldn't let me in until I plugged it into a computer or a fancy USB outlet. And it wouldn't let me go T the home screen. Now it wont let me on at all, after the home screen suddenly swooped in and ate this post on my Apollo, thus ****ing it. So now I can't get in at all. And I just rooted after I suddenly got this update, the newish one, and I renamed ota and ota contracts on accident. Is that a problem? Please help me...
Click to expand...
Click to collapse
Renaming OTA contracts is a problem! Given device is rooted it may be fixable via ADB. Also possible you can go further and unlock bootloader which yields complete control to repair/replace FireOS. I am travelling today and can not immediately help with details. Will check back later (24 hours) to see if help is still needed.
Thanks for the reply. However, I am unsure how to do what you suggested since its on a bootloop because I renamed the file apparently.
Thanks for the reply. However, I am unsure how to do what you suggested since its on a bootloop because I renamed the file apparently.
Leafen said:
Thanks for the reply. However, I am unsure how to do what you suggested since its on a bootloop because I renamed the file apparently.
Click to expand...
Click to collapse
Bootloop further complicates matters. How much time passes before the device restarts? Does it ever make it to the login screen?
While there is still a glimmer of hope the situation is dire. Pretty good chance the device can not be recovered. I say that not to be negative but rather recognizing Apollo is not a cheap gadget. Amazon crippled native recovery capabilities making simple fixes impossible to apply. Akin to making tires a non replaceable item (brilliant). Just want to prepare you for an unpleasant outcome...
Davey126 said:
Bootloop further complicates matters. How much time passes before the device restarts? Does it ever make it to the login screen?
While there is still a glimmer of hope the situation is dire. Pretty good chance the device can not be recovered. I say that not to be negative but rather recognizing Apollo is not a cheap gadget. Amazon crippled native recovery capabilities making simple fixes impossible to apply. Akin to making tires a non replaceable item (brilliant). Just want to prepare you for an unpleasant outcome...
Click to expand...
Click to collapse
Oi. Uh. It's normal procedure up to the colored Kindle logo. Goes off the same amount of time as usual. And it never makes it to the put in your password screen. Not yet anyways.
Scratch that I'm in. Changing Ota contracts back
It worked. I'm able to get back in the home screen. But now I need safestrap again for the ROM I already have partitioned on this device.
Leafen said:
It worked. I'm able to get back in the home screen. But now I need safestrap again for the ROM I already have partitioned on this device.
Click to expand...
Click to collapse
Great! Assuming a factory reset did the trick (I didn't immediately suggest that course of action as it can sometimes make things worse; other things to try first).
If you install Safestrap v4 choice of ROMs is limited to Fire Nexus and CM11 - both KitKat based. Unlocking the bootloader opens the door to a wider selection of Lollipop and Marshmallow based ROMs. Unlocking is not risky but does require a bit of technical knowledge and some patience. An unlocked device is also easier to recover in the event of a ROM crash or bootloop.
Assuming you want to proceed with Safestrap download the app from here. Make sure you get the build appropriate for your device. Install/launch the app and then select the option that installs Safestrap recovery. Please note this is not a true recovery environment and has none of the special powers associated with TWRP. Its singular purpose it to support the two custom ROMs noted above on a locked device. Unlocked devices do not need to use Safestrap.
Once Safestrap recovery is installed reboot your device. After the grey Amazon logo you will be presented with a 'robot' screen where you can choose to continue booting into FireOS or enter Safestrap recovery mode. Choose the latter. After a few moments device will enter Safestrap recovery which emulates TWRP.
Do you know what to do from here?
Warning: Once Safestrap v4 recovery is installed you should NEVER perform a factory reset via the stock recovery menu. Doing so will brick the device.
Oh! Well. Id like to know about unlocking my boot whatever. Now Marshmallow and lollipop are Android 4. S.omething right? Oh um. Do you mind telling me how to do it, especially since I got jammed into the new update, breaking my safestrap I already had and leaving the slot out to dry? That would be appreciated!
Leafen said:
Oh! Well. Id like to know about unlocking my boot whatever. Now Marshmallow and lollipop are Android 4. S.omething right? Oh um. Do you mind telling me how to do it, especially since I got jammed into the new update, breaking my safestrap I already had and leaving the slot out to dry? That would be appreciated!
Click to expand...
Click to collapse
Well you got "jammed" into a FireOS update because Safestrap was improperly configured. Details matter. Suggest proceeding with reinstalling Safestrap and forget about unlocking the bootloader thingy. Do not create or attempt to use a secondary slot. Custom ROM overwrites FireOS in the stock slot. Lots of posts outlining Safestrap best practices that apparently were not read or ignored.
Bootloader unlock thread: http://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982
No the reason I was booted out was because i was having to be stuck on the FireOS because I have to have it for well.. Showing reasons. Don't worry about that. But Safestrap was done perfect, I had it going on for A long while. I successfully used two or more ROMs with perfect functionality.
Leafen said:
I successfully used two or more ROMs with perfect functionality.
Click to expand...
Click to collapse
If using multiple/secondary slots worked well enough for you, great!
Full functionality can not be achieved in secondary slots with Safestrap v4 which is an adaptation specific to this device and was never intended to support dual boot capability. Issues impacting ROMs operating in secondary slots:
- restricted BT/WiFi radio functionality (less of an issue w/CM11)
- only 2 of 4 CPU cores available (other two disabled)
- the two active cores run at 100% regardless of load
- device will not enter deep sleep when secondary slot is active
- poor performance and lousy battery life resulting from above
If you only use the secondary slot on occasion and radios work then it's obviously a personal call if the limitations are problematic.
Davey126 said:
If using multiple/secondary slots worked well enough for you, great!
Full functionality can not be achieved in secondary slots with Safestrap v4 which is an adaptation specific to this device and was never intended to support dual boot capability. Issues impacting ROMs operating in secondary slots:
- restricted BT/WiFi radio functionality (less of an issue w/CM11)
- only 2 of 4 CPU cores available (other two disabled)
- the two active cores run at 100% regardless of load
- device will not enter deep sleep when secondary slot is active
- poor performance and lousy battery life resulting from above
If you only use the secondary slot on occasion and radios work then it's obviously a personal call if the limitations are problematic.
Click to expand...
Click to collapse
I only had the battery thing. Otherwise I used my secondary rom pretty much all the time.
Leafen said:
I only had the battery thing. Otherwise I used my secondary rom pretty much all the time.
Click to expand...
Click to collapse
And ½ the CPUs disabled. So why not install the custom rom in the stock slot?
Davey126 said:
And ½ the CPUs disabled. So why not install the custom rom in the stock slot?
Click to expand...
Click to collapse
I have o keep up appearances pretty much. The reason why I dont really need to tell you. But its for appearences sake
Leafen said:
I have o keep up appearances pretty much. The reason why I dont really need to tell you. But its for appearences sake
Click to expand...
Click to collapse
Yep - I get it. Not specifics (obviously) but understand optics. As an aside unlocking the bootloader offers no significant benefit given your situation. Enjoy.
Davey126 said:
Yep - I get it. Not specifics (obviously) but understand optics. As an aside unlocking the bootloader offers no significant benefit given your situation. Enjoy.
Click to expand...
Click to collapse
Crap. Safestrap isnt working for this update. Dang. Gotta wait for ggow or someone to make it.
Leafen said:
Crap. Safestrap isnt working for this update. Dang. Gotta wait for ggow or someone to make it.
Click to expand...
Click to collapse
Must be on FireOS 4.5.2.0 or 4.5.5.1 to run Safestrap v4. Rollback/upgrade options are available but ugly. Pretty sure Safestrap won't be receiving any further updates now that the HDX bootloader can be unlocked on any rooted 3rd gen device.

Categories

Resources